Diagnostics
2
The following table lists event codes, brief explanations of the codes, and associated steps that describe fault isolation procedures.
Event |
|
|
Code | Explanation | Action |
|
|
|
011 | Login server database invalid. | Go to step 7. |
|
|
|
021 | Name server database invalid. | Go to step 7. |
|
|
|
051 | Management server database invalid. | Go to step 7. |
|
|
|
052 | Management server internal error. | Go to step 7. |
|
|
|
061 | Fabric controller database invalid. | Go to step 7. |
|
|
|
062 | Maximum interswitch hop count | Go to step 8. |
| exceeded. |
|
|
|
|
070 | E_Port is segmented. | Go to step 9. |
|
|
|
071 | Switch is isolated. | Go to step 9. |
|
|
|
072 | E_Port connected to an unsupported | Go to step 10. |
| switch. |
|
|
|
|
3
Is fault isolation being performed at the HAFM server?
YES NO
↓Fault isolation is being performed through the embedded web server interface. Go to step 17.
4
Does a yellow triangle (attention indicator) appear to overlay the port graphic at the Hardware View?
YES NO
↓The problem is transient and the
5
Inspect the port state and LED status for the port.