IBM SAN32M1, Installation And Service Manual

Page: 299 / 626

267 Chapter 3: Diagnostics
17
A link incident may have occurred, but the LIN alerts option is not
enabled for the port and the attention indicator does not appear.
At the Hardware View, click Logs and select Link Incident Log. The
Link Incident Log displays. If a link incident occurred, the affected port
number is listed with one of the following messages.
Link interface incident - implicit incident.
Link interface incident - bit-error threshold exceeded.
Link failure - loss of signal or loss of synchronization.
Link failure - not-operational primitive sequence (NOS)
received.
Link failure - primitive sequence timeout.
Link failure - invalid primitive sequence received for the
current link state.
Did one of the listed messages appear in the Link Incident Log?
YES NO
↓
The switch appears operational. Exit MAP.
Go to step 34 .
18
As indicated by a message or event code 507, a Fibre Channel port
failed an internal or external loopback test.
a. Reset each port that failed the loopback test.
1. At the Hardware View, right-click the port. A pop-up menu
appears.
2. Select Reset Port. A This operation will cause a link reset
to be sent to the attached device message displays.
3. Click OK. The port resets.
b. Perform an external loopback test for all ports that were reset.
Refer to Perform loopback tests on page 334.
Did resetting ports solve the problem?
NO YES
↓
The switch appears operational. Exit MAP.