Cisco ONS 15454 Troubleshooting Manual page 288

2.7.100 EXT
2.7.100 EXT
A Failure Detected External to the NE alarm occurs because an environmental alarm is present. For
example, a door could be open or flooding could have occurred.
Clear the EXT Alarm
In node view double-click the AIC-I card to open the card view.
Step 1
Step 2 Double-click the Maintenance > External Alarms tab.
Step 3 Follow your standard operating procedure to remedy environmental conditions that cause alarms. The
alarm clears when the situation is remedied.
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport
Step 4
for more information or call Cisco TAC 1 800 553-2447.
2.7.101 EXTRA-TRAF-PREEMPT
An Extra Traffic Preempted alarm occurs on OC-N cards in two-fiber and four-fiber BLSRs when
low-priority traffic directed to the protect system has been preempted by a working system protection
switch.
Clear the EXTRA-TRAF-PREEMPT Alarm
Verify that the protection switch has occurred by checking the Conditions tab.
Step 1
If a ring switch has occurred, clear the ring switch on the working system by following the appropriate
Step 2
alarm in this chapter. For more information about protection switches, refer to the
Switching, Lock Initiation, and Clearing" section on page 2-262
the Cisco ONS 15454 Procedure Guide.
If the alarm occurred on a four-fiber BLSR and the span switch occurred on this OC-N, clear the span
Step 3
switch on the working system.
Step 4 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport
for more information or call Cisco TAC 1 800 553-2447 in order to report a Service-Affecting (SA)
problem.
2.7.102 FAILTOSW
Cisco ONS 15454 Troubleshooting Guide, R8.5
2-94
Default Severity: Minor (MN), Non-Service-Affecting (NSA)
SONET Logical Object: ENVALRM
Default Severity: Major (MJ), Service-Affecting (SA)
SONET Logical Object: OCN
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
Chapter 2 Alarm Troubleshooting
"2.9.2 Protection
or the "Maintain the Node" chapter in
November 2009