Product manual

VTrak E-Class Product Manual
312
Controller Problems
Controller problems include:
• Maintenance Mode (page 312)
• Finding and Correcting the Cause of the Problem (page 312)
• Taking a Controller out of Maintenance Mode (page 313)
• Unsaved Data in the Controller Cache (page 314)
Controller problems occur when one of the controllers goes into maintenance
mode.
Maintenance Mode
For VTraks with two controllers, one of the controllers enters 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 313)
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