System information

Troubleshooting 5-5
Isolating Faults
If you have local access to the Endurance Configuration, check the following in the order that
they are listed:
If you only have access to a Endurance Configuration using the Endurance Manager remotely,
check the following:
Step Action Notes
1 Using the main window in the Endurance
Manager, note any components that are not
Good, or Transitioning.
2 Because the two CoServers may have slightly
different error messages, depending on the
state of the Endurance Configuration, check
the Windows Event Viewer for Endurance
messages beginning with
or on both
Coservers.
Examine those event descriptions (in
Endurance FTvirtual Server Messages) for
information and corrective action.
3 Review the CoServers’ event logs for non-
Endurance messages that indicate a problem
with a device connected to a CoServer.
For example, check for messages logged
by the SCSI adapter driver.
Step Action Notes
1 Using the main window in the
Endurance Manager, note any
components that are not Good or
Transitioning.
2 Check the Windows Event Viewers to
which you have access. Look for
Endurance messages that begin with
or
.
Examine those event descriptions (in
Endurance FTvirtual Server Messages) for
information and corrective action.
The FTvirtual Server event logs are accessible
from the network when the FTvirtual Server is
operating, even if it is in a vulnerable condition.
If the CoServers are on a network, examine the
CoServer event logs first. If the CoServers are
not available, you can examine the FTvirtual
Server event logs even when the FTvirtual
Server is not operating.