IBM SAN32M-2, Installation And Service Manual

Page: 169 / 312

143 Chapter 3: Maintenance analysis procedures
17
An E_Port is fenced because of a protocol error. Depending on failure
cause, additional information and event codes are available at the
product or attached switch. Perform one of the following:
• The E_Port is segmented and accompanied by primary event
code
070 . Go to step 7 .
• The fiber-optic cable is disconnected, the cable failed or is
degraded, or the port optical transceiver failed. The failure is
accompanied by a primary event code indicating the failure type.
Go to
MAP 0000: Start MAP and perform fault isolation for the
primary event code. Exit MAP.
• The E_Port is fenced because of persistent incomplete
operations (ISL bouncing). Go to
MAP 0000: Start MAP and
perform fault isolation at the attached switch. Exit MAP.
• The E_Port is fenced because of application-layer protocol
errors. Go to
MAP 0000: Start MAP and perform fault isolation at
the attached switch. Exit MAP.
18
An E_Port is fenced because devices connected to the attached
fabric element are flooding the ISL with frames (hot I/O). These
link-level problems are typically associated with legacy devices,
arbitrated loop devices, or magnetic tape drives. Perform one of the
following:
• Disconnect the ISL. Exit MAP.
• Refer to the manufacturer’s documentation and perform fault
isolation at the attached device or fabric element.
Exit MAP.
• Change port fencing threshold settings to more lenient values.
Go to step 20 .
19
An E_Port is fenced because of persistent firmware-related security
violations (SANtegrity binding or SANtegrity authentication failures).
a. At the EFCM Basic Edition interface, SAN management
application, or Element Manager, change binding membership
lists or authentication parameters as directed by the customer:
— EFCM Basic Edition - Refer to the EFCM Basic Edition
User Manual (620-000240) for instructions.