Chapter 8: Troubleshooting
345
Controller Enters Maintenance Mode
For VTraks with two controllers, one of the controllers will enter maintenance
mode in the event of a problem with the controller. When a controller enters
maintenance mode, it goes offline and it displays N/A (not accessible) under
Readiness Status.
You must take the following actions:
• Find and correct the cause of the problem (see below)
• Take the controller out of maintenance mode (see page 346)
Finding and Correcting the Cause of the Problem
Make the following external checks to your VTrak system. Be sure that:
• Both controllers are present, fully inserted into their slots, and locked into
place.
• The controllers match, meaning both are Fibre Channel or both are SAS.
• All data cables to external JBOD enclosures in good condition and are
securely attached.
A disconnected data cable to an external JBOD enclosure causes the two
controllers to see a different set of configured drives. This condition is the
most common cause of a controller entering maintenance mode.
If all external checks are OK, take the following actions:
1. Shut down the VTrak.
2. Remove one of the controllers.
3. Restart the VTrak.
4. After the VTrak is fully booted, access the CLI, the CLU, or WebPAM PROe.
5. Observe and record the following information about the first controller:
• Memory size
• Hardware version
• Firmware version
To view this information in WebPAM PROe, click the Controller icon,
Information tab.
6. Shut down the VTrak.
7. Remove the first controller and install the second controller.
8. Repeat steps 3 through 6.
9. Compare your records.
10. Correct any differences between the two controllers.
To Next Page
Loading...
Need help?
General
