IBM SAN32M-2, Инструкция по установке и обслуживанию

Страница: 129 / 312

103 Chapter 3: Maintenance analysis procedures
Is a failure indicated?
NO YES
↓
A CRU failure, power-on self-test (POST) failure, link
incident, interswitch link (ISL) problem, fenced E_Port, or
segmented E_Port is indicated. To obtain event codes that
identify the failure,
go to step 10 .
8
A link incident may have occurred, but the LIN alerts option is not
enabled and the yellow triangle (attention indicator) does not appear.
Inspect the
Link Incident Log :
a. For the product reporting the problem:
— EFCM Basic Edition - Select Link Incident from the Logs
menu at any view. The Link Incident Log displays.
— Element Manager - Select Link Incident Log from the Logs
menu at any view. The Link Incident Log displays.
b. If a link incident occurred, the 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 a listed message appear?
NO YES
↓
A Fibre Channel link incident is indicated. Go to MAP 0500:
Port failure or link incident analysis . Exit MAP.
Perform a data collection and contact the next level of support. Refer
to
Collect maintenance data (EFCM Basic Edition) or Collect
maintenance data (Element Manager). Exit MAP.