Special Considerations
MPE documents | |
 Complete PDF | |
| Table of Contents | |
| E0803 Edition 2 | |
| E1100 Edition 1 ♥ |
Rebooting After a HAFO Event
Rebooting the system after a HAFO event has occurred is a special situation, especially if the event occurred on the path for ldev 1. HAFO is not active during boot, and the boot process has no knowledge of HAFO. This means that the system will attempt to mount ldev 1 based on the system primary path, and all other disk volumes based on the configuration of the ldevs done in the io> section of SYSGEN. (i.e., NOT based on anything done in the ha> section of SYSGEN.) If the primary path to any of the ldevs is broken, then those ldevs will NOT mount at boot time and will NOT be available after the system is up. For information on how to deal with these types of situations, please see the Special Considerations for Failed Paths section in Chapter 6 "Recovering From a Failover"
 |
NOTE: All primary and alternate paths are validated near the end of the boot process. If any paths are broken, an error message will be issued. |
Corrupt or Problem HAFOCONF File
If the HAFOCONF file becomes corrupt, there are two ways to deal with it. One way to fix it is to purge the file and restore a good file from a backup. Another way is to purge it, then enter SYSGEN. If there is no HAFOCONF file when SYSGEN is entered, it will build a new (empty) one automatically. Use addconf to configure ldevs for HAFO. Do not perform HAFO configuration when a path is broken. No HAFO configuration changes should be made unless all paths are functioning properly and all ldevs are operating on their primary path.
|
EXIT (ex) |
Chapter 5 Monitoring Status |