Datasheet

14-10
Cisco ONS 15454 SDH Reference Manual, R7.0
October 2008
Chapter 14 Alarm Monitoring and Management
14.3.8 Alarm History and Log Buffer Capacities
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.
14.3.8 Alarm History and Log Buffer Capacities
The ONS 15454 SDH alarm history log, stored in the TCC2/TCC2P RSA memory, contains four
categories of alarms. These include:
• CR severity alarms
• MJ severity alarms
• MN severity alarms
• the combined group of cleared, Not Alarmed severity, and Not Reported severity alarms
Each category can store between 4 and 640 alarm chunks, or entries. In each category, when the upper
limit is reached, the oldest entry in the category is deleted. The capacity is not user-provisionable.
CTC also has a log buffer, separate from the alarm history log, that pertains to the total number of entries
displayed in the Alarms, Conditions, and History windows. The total capacity is provisionable up to
5,000 entries. When the upper limit is reached, the oldest entries are deleted.
14.4 Alarm Severities
ONS 15454 SDH alarm severities follow the ITU-T G.733 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.733 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 “14.5 Alarm Profiles”
section on page 14-10.) 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 a 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 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.
14.5 Alarm Profiles
The alarm profiles feature allows you to change default alarm severities by creating unique alarm profiles
for individual ONS 15454 SDH 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.