Service manual
3
MAP 0000: Start MAP
3-11
Maintenance Analysis Procedures (MAPS)
— 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
(
Collecting Maintenance Data
on page 4-32). Exit MAP.
9
If an incident occurs on the Fibre Channel link between the product
and attached OSI server, a link incident record is generated and sent
to the server console using the reporting procedure defined in
T11/99-017v0.
Was a link incident record generated and sent to the OSI server?
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
(
Collecting Maintenance Data
on page 4-32). Exit MAP.
10
Inspect the
Event Log
to obtain failure reason codes:
a. For the product reporting the problem: