13-11
Cisco ONS 15454 SDH Reference Manual, R5.0
April 2008
Chapter13 Alarm Monitoring and M anagement
13.6.1 Creating and Modifying Alarm Profiles
If one or more alarm profiles have been stored as files from elsewhere in the network onto the local PC
or server hard drive where CTC resides, you can utilize as many profiles as you can physically store by
deleting and replacing them locally in CTC so that only eight are active at any given time.
13.6.1 Creating and Modifying Alarm Profiles
Alarm profiles are created in the network view using the Provisioning > Alarm Profiles ta bs. A default
alarm profile following ITU-T G.783 is preprovisioned for every alarm. After lo ading the default profile
or another profile on the node, you can use the Clone feature to create custom profiles. After the new
profile is created, the Alarm Profiles window shows the original profile—frequently Default—and the
new profile.
Note The alarm profile list contains a master list of alarms that is used for a mixed node network. Some of
these alarms might not be used in all ONS nodes.
Note The Default alarm profile list contains alarm and condition severities that correspond when applicable
to default values established in ITU-T G.783.
Note All default or user-defined severity settings that are Critical (CR) or Major (MJ) are demoted to Minor
(MN) in non-service-affecting situations.
Tip To see the full list of profiles including those available for loading or cloning, click the Available button.
You must load a profile before you can clone it.
Note Up to ten profiles, including the two reserved profiles—Inherited and Default—can be stored in CTC.
Wherever it is applied, the Default alarm profile sets severities to standard ITU-T G.783 settings. The
Inherited profile sets alarm severity to inherited (I) so that alarms inherit, or copy, severities from the
next-highest level. For example, a card with an Inherited alarm profile copies the severities used by the
node housing the card. If you choose the Inherited profile from the network view, the severities at the
lower levels (node and card) be copied from this selection.
You do not have to apply a single severity profile to the node-, card-, and port-level alarms. Different
profiles can be applied at different levels. You could use the inherited or default profile on a node and
on all cards and ports, but apply a custom profile that downgrades a n alarm on one particular card. For
example, you might choose to downgrade an STM-N unequipped path alarm (HP-UNEQ) from Cr itical
(CR) to Not Alarmed (NA) on an optical card bec ause this alarm raises and then clears every time you
create a circuit. HP-UNEQ alarms for the card with the custom profile would not display on the Alarms
tab. (But they would still be recorded in the Conditions and History tabs.)
When you modify severities in an alarm profile, the following rules apply:
•All Critical (CR) or Major (MJ) default or user-defined severity settings are demoted to Minor (MN)
in Non-Service-Affecting (NSA) situations.
•Default severities are used for all alarms and conditions until you create a new profile and apply it.