Retrieving And Displaying Alarm And Condition History; Alarm Severities - Cisco ONS 15454 DWDM Installation And Operation Manual

20.4 Alarm Severities

Table 20-4 History Column Description (continued)
Column
Cond
Description
Eqpt Type

20.3.7.2 Retrieving and Displaying Alarm and Condition History

You can retrieve and view the history of alarms and conditions, as well as transients (passing
notifications of processes as they occur) in the CTC history window. The information in this window is
specific to the view where it is shown (that is, network history in the network view, node history in the
node view, and card history in the card view).
The node and card history views are each divided into two tabs. In node view, when you click the
Retrieve button, you can see the history of alarms, conditions, and transients that have occurred on the
node in the History > Node window, and the history of alarms, conditions, and transients that have
occurred on the node during your login session in the History > Session window. In the card-view
history window, after you retrieve the card history, you can see the history of alarms, conditions, and
transients on the card in the History > Card window, or a history of alarms, conditions, and transients
that have occurred during your login session in the History > Session window.
You can also filter the severities and occurrence period in these history windows.
20.4 Alarm Severities
ONS 15454 alarm severities follow the Telcordia GR-253 standard, so a condition might be Alarmed (at
a severity of Critical [CR], Major [MJ], or Minor [MN]), Not Alarmed (NA), or Not Reported (NR).
These severities are reported in the CTC software Alarms, Conditions, and History windows at all levels:
network, shelf, and card.
ONS equipment provides a standard profile named Default listing all alarms and conditions with severity
settings based on Telcordia GR-253 and other standards, but users can create their own profiles with
different settings for some or all conditions and apply these wherever desired. (See the
Profiles" section on page
loss (CARLOSS) alarm on an Ethernet port could be changed from major to critical. The profile allows
setting to Not Reported or Not Alarmed, as well as the three alarmed severities.
Critical and Major severities are only used for service-affecting alarms. If a condition is set as Critical
or Major by profile, it will raise as Minor alarm in the following situations:
•
•
Because of this possibility of being raised at two different levels, the alarm profile pane shows Critical
as CR / MN and Major as MJ / MN.
Cisco ONS 15454 DWDM Installation and Operations Guide, R4.7
20-8
Information Recorded
Condition name.
Description of the condition.
Card type in this slot.
20-9.) For example, in a custom alarm profile, the default severity of a carrier
In a protection group, if the alarm is on a standby entity (the side not carrying traffic)
If the alarmed entity has no traffic provisioned on it, so no service is lost
Chapter 20 Alarm Monitoring and Management
"20.5 Alarm
September 2004