Filter
Top Products
3-34
McDATA Sphereon 4300 Fabric Switch Installation and Service Manual
Maintenence Analysis Procedures
a. At the Event Log, examine the first five bytes (0 through 4) of
event data.
b. Byte 0 specifies the E_Port reporting the problem. Byte 4
specifies the port fence code as listed in Table 3-13.
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:
Table 3-13 Port Fence Codes and Actions
Byte 4 Port Fence Code Action
01 Protocol error. Go to step 17.
02 Link-level hot I/O. Go to step 18.
03 Security violation. Go to step 19.