23-7
Cisco ONS 15454 DWDM Installation and Operations Guide, R6.0
August 2005
Chapter 23 Alarm Management Reference
23.4 Alarm Severities
23.3.6.2 Retrieving and Displaying Alarm and Condition History
You can retrieve and view the history of alarms and conditions, including transient conditions (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.
23.4 Alarm Severities
ONS 15454 alarm severities follow the Telcordia GR-253-CORE 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-CORE 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
“23.5 Alarm Profiles” section on page 23-7.) For example, in a custom alarm profile, the default
severity of a carrier 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:
• 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, no service is lost
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.
23.5 Alarm Profiles
The alarm profiles feature allows you to change default alarm severities by creating unique alarm profiles
for individual ONS 15454 ports, cards, or nodes. A created alarm profile can 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 its 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 Telcordia GR-253-CORE
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.
To Next Page
Loading...
