Product manual

VTrak E-Class Product Manual
350
SAS Connections
Faulty SAS connections are suspected when the link port counter reports a large
number of bad link errors. See “Viewing SAS Port Statistics” on page 91 or
page 215.
Link errors can be caused by:
• Debris blocking the SAS cable connector
• A faulty SAS cable
• A faulty controller or I/O module SAS connector
Blocked Cable Connectors
To check for debris blocking the SAS cable connector:
1. Power down the RAID head and JBOD subsystems.
2. Remove the SAS cable and check all SAS connectors for debris.
3. Clean the connectors as required and reconnect the SAS cable.
4. Power up the subsystems and monitor the link port counter for changes in
the rate of link error accumulation.
Faulty Cable
To check for a faulty SAS cable:
1. Power down the RAID head and JBOD subsystems.
2. Replace the SAS cable with a new one.
3. Power up the subsystems and monitor the link port counter for changes in
the rate of link error accumulation.
Faulty Controller or I/O Module Connector
To check for a bad controller or I/O module SAS connector:
1. With the subsystems online and I/Os running, access the CLI via serial or
Telnet.
See “Initial Connection” on page 166.
2. At the administrator@cli> prompt, type the following command and press
Enter.
sasdiag -a errorlog -l expander -e 1 -i 1
3. At the administrator@cli> prompt, type the following command and press
Enter.
sasdiag -a errorlog -l c2cport
By interpreting the two error logs, you can verify which controller or I/O
module SAS port is accumulating link errors.