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

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

SAN32M-2 Installation and Service Manual 104
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. Refer
to
Collect maintenance data (EFCM Basic Edition) or Collect
maintenance data (Element Manager). Exit MAP.
10
Inspect the Event Log to obtain failure reason codes:
a. For the product reporting the problem:
— EFCM Basic Edition - Select Event from the Logs menu at
any view. The Event Log displays.
— Element Manager - Select Event Log from the Logs menu
at any view. The Event Log displays.
b. Record the event code and associated date, time, and severity
( Informational , Minor , Major , or Severe ).
c. If multiple event codes are found, record all codes and severity
levels. Record the date, time, and sequence, and determine if all
codes are related to the reported problem. Begin fault isolation
with the most recent event code with the highest severity level.
Other codes may accompany this event code, or may indicate a
normal indication after a problem is recovered.
Were one or more event codes found?
NO YES
↓
Go to Table 7 to obtain event codes. Exit MAP.
Return to step 1 and perform fault isolation again. If this is the
second time at this step, 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.