Quantum QXS G2 Series, Руководство по установке и обслуживанию оборудования

Страница: 150 / 246

138 QXS G2 Hardware Installation and Maintenance Guide
• Warning . A problem occurred that may affect system stability, but not data integrity. Evaluate the
problem and correct it if necessary.
• Informational . A configuration or state change occurred, or a problem occurred that the system
corrected. No immediate action is required.
NOTE: Some events also have a Resolved severity that indicates that a previously logged
non-Informational condition has been resolved. See the Event Descriptions Reference Guide for
information about specific events.
The event logs record all system events. It is very important to review the logs, not only to identify the
fault, but also to search for events that might have caused the fault to occur. For example, a host
could lose connectivity to a disk group if a user changes channel settings without taking the storage
resources assigned to it into consideration. In addition, the type of fault can help you isolate the
problem to either hardware or software.
Isolate the Fault
Occasionally, it might become necessary to isolate a fault. This is particularly true with data paths,
due to the number of components comprising the data path. For example, if a host-side data error
occurs, it could be caused by any of the components in the data path: controller module, cable, or
data host.
If the Chassis Does Not Initialize
It may take up to two minutes for all chassis to initialize. If an chassis does not initialize:
•
Perform a rescan
•
Power cycle the system
•
Make sure the power cord is properly connected, and check the power source to which it is
connected
•
Check the event log for errors
Correcting Chassis IDs
When installing a system with drive chassis attached, the chassis IDs might not agree with the
physical cabling order. This is because the controller might have been previously attached to chassis
in a different configuration, and it attempts to preserve the previous chassis IDs, if possible. To correct
this condition, make sure that both controllers are up, and perform a rescan using the disk
management utility (GUI) or the CLI. This will reorder the chassis, but can take up to two minutes for
the chassis IDs to be corrected.
To perform a rescan using the CLI, type the following command:
rescan
To perform a rescan using the disk management utility (GUI):
1 Verify that both controllers are operating normally.
2 Do one of the following:
a Point to the System tab and select Rescan Disk Channels .
b In the System topic. select Action > Rescan Disk Channels .
3 Click Rescan.