Specifications

8-9
Cisco MGX 8260 Command Line Interface Guide
Release 1.2, Part Number 78-10987-01 Rev. B0, January, 2002
Chapter 8 Troubleshooting
Clearing Alarms
Clearing Fast Ethernet Alarms
The MGX 8260 Media Gateway monitors the Fast Ethernet trunks for conditions that can cause service
interruption. To view Fast Ethernet line state, enter the lsethlns command.
The system displays a summary of the trunk status, including the Operational Status for each line.
Respond to alarms depending on the displayed alarm indication as shown in the following table:
Clearing SONET Alarms
The MGX 8260 Media Gateway continuously monitors lines for defect conditions and integrates alarm
events over time. An alarm is declared when the defect persists for 2 seconds, and is cleared when the
alarm is absent for 10 seconds. Alarm changes generate traps that notify managers of the state change.
To view alarms, use the lssonetstat command.
Respond to major alarms according to the guidelines in the following table:
Displayed Information Possible Cause and Corrective Action
Failed The Fast Ethernet failed. Make sure the SCC is in the standby mode and
replace the card.
Link down in active state The Fast Ethernet carrier is down. Try the following possible remedies:
• Check the corresponding Fast Ethernet cable at the rear of the
MGX 8260 chassis. It should be fully inserted and snapped in place.
• Trace the Fast Ethernet network, checking for faults in other network
components.
Link down in inactive state The Fast Ethernet carrier is down, but the link is inactive. Try the
following possible remedies:
• Check for network administration or maintenance activity on the
Fast Ethernet.
• Check the corresponding Fast Ethernet cable at the rear of the
MGX 8260 chassis. It should be fully inserted and snapped in place.
• Trace the Fast Ethernet network, checking for faults in other network
components.
Major Alarm Corrective Action
LOS
• Verify the physical connection (cables, connectors) in the receive
direction
• Verify that the OC3 line on remote node is transmitting
OOF
• Verify that incoming signal is OC3
• Verify that the MGX8260 and remote node use to the same clock source
LOP-P
• Verify that the incoming signal is OC3 with STS3c frame structure
• Verify that the SONET frame scrambling is enabled on both sides