13-10
Cisco ONS 15454 SDH Reference Manual, R5.0
April 2008
Chapter13 Alarm Monitoring and Management
13.5 Alarm Severities

13.4.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, condition s, 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, an d 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.
13.5 Alarm Severities
ONS 15454 SDH alarm severities follow the ITU-T G.783 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 ITU-T G.783 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 “13.6 Alarm Profiles”
section on page 13-10.) For example, in a custom alarm profile, the default severity of a carrier loss
(CARLOSS) alarm on an Ethernet port could be changed fr om 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:
•In a protection group, if the alarm is on a standby entity (side not carrying traffic)
•If the alarmed entity has no traffic provisioned on it, so no service is l ost
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.
13.6 Alarm Profiles
The alarm profiles feature allows you to change default alarm severities by creating unique a larm profiles
for individual ONS 15454 SDH ports, cards, or nodes. A created alarm profile ca n be applied to any node
on the network. Alarm profiles can be saved to a file and imported elsewhere in the network, but the
profile must be stored locally on a node before it can be applied to the node, its cards, or i ts cards’ ports.
CTC can store up to ten active alarm profiles at any time to apply to the node. Custom profiles can take
eight of these active profile positions. Two other profiles, Default profile and Inherited profile, are
reserved by the NE, and cannot be edited.The reserved Default profile contains ITU-T G.783 severities.
The reserved Inherited profile allows port alarm severities to be governed by the card-level severities, or
card alarm severities to be determined by the node-level severities.