Alarm History And Log Buffer Capacities - Cisco ONS 15454 DWDM Reference Manual

16.3.7 Alarm History and Log Buffer Capacities

The node and card history views are each divided into two tabs. In node view (single-shelf mode) or shelf
view (multishelf mode), 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.
16.3.7 Alarm History and Log Buffer Capacities
The ONS 15454 alarm history log, stored in the TCC2/TCC2P RSA memory, contains four categories
of alarms. These include:
•
•
•
•
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.
16.4 Alarm Severities
ONS 15454 alarm severities follow the Telcordia GR-474-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-474-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
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 Reference Manual, R8.5
16-8
CR severity alarms
MJ severity alarms
MN severity alarms
the combined group of cleared, Not Alarmed severity, and Not Reported severity alarms
16-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, no service is lost
Chapter 16 Alarm and TCA Monitoring and Management
"16.5 Alarm
78-18343-02