Cisco NCS 2000 series Troubleshooting Manual page 158

Trouble Characterizations
Note For a description of CTC-view terminology, refer to the
Alarm Characteristics
The DWDM system uses standard alarm entities to identify what is causing trouble. All alarms stem from
hardware, software, environment, or operator-originated problems whether or not they affect service. Current
alarms for the network, CTC session, node, or card are listed in the Alarms tab. (In addition, cleared alarms
are also found in the History tab.)
Condition Characteristics
Conditions include any problem detected on a shelf. They can include standing or transient notifications. A
snapshot of all current raised, standing conditions on the network, node, or card can be retrieved in the CTC
Conditions window or using TL1's set of RTRV-COND commands. (In addition, some but not all cleared
conditions are also found in the History tab.)
For a comprehensive list of all conditions, refer to the TL1 Command Guide. For information about transients,
see Transient Conditions, on page
Note
When an entity is put in the OOS,MT administrative state, the NCS suppresses all standing alarms on that
entity. You can retrieve alarms and events on the Conditions tab. You can change this behavior for the
LPBKFACILITY and LPBKTERMINAL alarms. To display these alarms on the Alarms tab, set the
NODE.general.ReportLoopbackConditionsOnPortsInOOS-MT to TRUE on the NE Defaults tab.
Severity
The system uses Telcordia-devised standard severities for alarms and conditions: Critical (CR), Major (MJ),
Minor (MN), Not Alarmed (NA), and Not Reported (NR). These are described below:
• A Critical (CR) alarm generally indicates severe, Service-Affecting trouble that needs immediate
correction.
• A Major (MJ) alarm is a serious alarm, but the trouble has less impact on the network.
• Minor (MN) alarms generally are those that do not affect service. For example, the automatic protection
switching (APS) byte failure (APSB) alarm indicates that line terminating equipment (LTE) detects a
byte failure on the signal that could prevent traffic from properly executing a traffic switch.
• Not Alarmed (NA) conditions are information indicators, such as for free-run synchronization state
(FRNGSYNC) or a forced-switch to primary (FRCSWTOPRI) timing event. They could or could not
require troubleshooting, as indicated in the entries.
• Not Reported (NR) conditions occur as a secondary result of another event. For example, the alarm
indication signal (AIS), with severity NR, is inserted by a downstream node when an LOS (CR or MJ)
alarm occurs upstream. These conditions do not in themselves require troubleshooting, but are to be
expected in the presence of primary alarms.
Severities can be customized for an entire network or for single nodes, from the network level down to the
port level by changing or downloading customized alarm profiles. These custom severities are subject to the
Cisco NCS 2000 series Troubleshooting Guide, Release 11.0
112
CTC Enhancements, Operations, and
465.
Alarm Troubleshooting
Shortcuts.