Technical information

Troubleshooting and Repair
125
Troubleshooting
Flowchart 5: Continued
F
Table 25: Status of Redundant File System
FILE STAT
REDUN on
the active
Plane
FILE STAT
REDUN on
the inactive
Plane
Interpretation Action to Take
ISOLATED ISOLATED The system is likely partitioned.
You can check this status by
entering the WHERE command
on each plane. An asterisk at the
end of the first line in the display
indicates that the controller is
partitioned. Systems are usually
only partitioned during software
upgrades when it is necessary to
isolate the different software
streams on the two main
controllers.
The redundant file system could
be disabled because someone
has previously entered the FILE
DISABLE REDUN command, or
because it is a new system and
the redundant file system has
never been enabled.
Enter the JOIN command first
on the inactive side, then on
the active side. Only enter this
command if you are sure that
the operating system software
is identical on both planes. Use
the WHERE command on both
planes to verify that the
software is identical.
Enter the FILE ENABLE
REDUN command on the
active plane. (You can verify
communication between the
active controller and the
inactive plane’s HDM by
entering the LOGS R OTHER
<log name> MATCH xxxx
command).
IN SYNCH OUT OF
SYNCH
The active controller is in the
process of copying the database
from its RAM to both hard disks.
The inactive controller will not
report “IN SYNCH” until the
copying is complete.
If the inactive controller remains
OUT OF SYNCH for more than
20 minutes, the redundant file
may be corrupted.
Wait for the active controller to
finish the copying, and then
check for an “IN SYNCH” on
the inactive side.
If you suspect redundant file
corruption, see page 133
IN SYNCH IN SYNCH The databases on both the active
and inactive planes are identical.
No action to take. This is how
the system should be.
G