Whenever possible, the maintenance approach instructs service personnel to perform
fault isolation and repair procedures without degrading or interrupting operation of the
switch, attached devices, or associated applications. Switch fault isolation begins
when one or more of the following occur:
System event information displays at the attached HAFM server, a remote
workstation communicating with the HAFM server, or the embedded web server
LEDs on the switch front panel or FRUs illuminate to indicate a hardware
An unsolicited SNMP trap message is received at a management workstation,
indicating an operational state change or failure.
Notification of a significant system event is received at a designated support
center through an e-mail message or the call-home feature.
System events can be related to one of the following:
Switch or HAFM server failure (hardware or software).
Ethernet LAN communication failure between the switch and HAFM server
Link failure between a port and attached device.
ISL failure or segmentation of an E_Port.
Fault isolation and service procedures vary depending on the system event information
provided. Fault isolation and related service information is provided through
maintenance analysis procedures (MAPs) documented in Chapter 3. MAPs consist of
step-by-step procedures that prompt service personnel for information or describe a
specific action to be performed. MAPs provide information to interpret system event
information, isolate a switch failure to a single FRU, remove and replace the failed
FRU, and verify switch operation. The fault isolation process normally begins with
MAP 0000: Start MAP
Ensure the correct switch is selected for service (if the HAFM server manages
multiple switches or other HA Fabric Directors and Edge Switches) by enabling unit
beaconing at the failed switch. The amber system error LED on the switch front panel
blinks when beaconing is enabled. Instructions to enable beaconing are incorporated
into MAP steps.
edge switch 2/24 service manual
" on page 2-6.