Download Back - Support On Line

3.1.2
Fabric Diagnostics
Diagnostic is recommended in the following cases:
•
•
•
•
•
3.1.3
During Fabric installation and during startup.
Before running an application.
Performance problems (by locating discarded packets and link integrity problems).
MPI job run problem, to locate malfunctioning nodes and get the overall fabric
structure.
Additional problems related to fabric stability, blocking or other.
Debugging Tools
Tools available to perform diagnostic:
•
•
•
•
•
3.1.4
High-Level Diagnostic Tools
Note
3-2
Use the Topology Map to see current problems.
The Error Log.
The Bad Ports Log.
The Current Alarms Table.
The Fabric Statistics portcounters.csv file.
1.
Enable the SM Fabric Inspect preferences for debugging Fabric Failure.
2.
Use the VFM/VDM Port Counters Information and Graph window to check a specific
port counter’s health.
3.
Use the Event Log to discover that there is a problem in the fabric. In the VFM, right
click and select View Event to get information to help identify where problem is
located. Alternatively, you can show the Event Log from the CLI.
4.
Use the Current Alarms Table to see current problems. In the VFM, right click and
select Alarm Data to get information to help identify where the problem is located.
5.
Use the Topology Map to identify nodes with a current alarm.
6.
Proactively look for increasing error counters using the statistics feature and running
the Diagnostic scripts using the CLI.
See the Voltaire Switch User Manual ISR 9024, ISR 9096, and ISR 9288/2012 Switches
for full details on using these tools.
BAS5 for Xeon - Maintenance Guide