-
Cisco ONS 15310-CL Reference Manual, Release 6.0
-
Chapter 1, Shelf Assembly Hardware
-
Chapter 2, Card Reference
-
Chapter 3, Card Protection
-
Chapter 4, Cisco Transport Controller Operation
-
Chapter 5, Security
-
Chapter 6, Timing
-
Chapter 8, SONET Topologies
-
Chapter 7, Circuits
-
Chapter 10, Alarm Monitoring and Management
-
Chapter 9, Management Network Connectivity
-
Appendix A, Specifications
-
Appendix B, Administrative and Service States
-
Appendix C, Network Element Defaults
-
About this Manual
-
Feedback
Table Of Contents
Alarm Monitoring and Management
10.2.1 Viewing Alarms With Each Node's Time Zone
10.2.2 Controlling Alarm Display
10.2.4 Viewing Alarm-Affected Circuits
10.2.6 Controlling the Conditions Display
10.4.1 Creating and Modifying Alarm Profiles
10.4.6 Applying Alarm Profiles
10.6 External Alarms and Controls
10.6.2 External Control Output
Alarm Monitoring and Management
This chapter describes Cisco Transport Controller (CTC) alarm management. To troubleshoot specific alarms, refer to the Cisco ONS 15310-CL Troubleshooting Guide. Chapter topics include:
10.1 Overview
Cisco Transport Controller (CTC) detects and reports SONET alarms generated by the Cisco ONS 15310-CL and the larger SONET network. You can use CTC to monitor and manage alarms at the card, node, or network level. Default alarm severities conform to the Telcordia GR-253 standard, but you can set alarm severities in customized alarm profiles or suppress CTC alarm reporting. For a detailed description of the standard Telcordia categories employed by Optical Networking System (ONS) nodes, refer to the Cisco ONS 15310-CL Troubleshooting Guide.
Note
ONS 15310-CL alarms can also be monitored and managed through Transaction Language One (TL1) or a network management system (NMS).
10.2 Viewing Alarms
You can use the Alarms tab to view card, node, or network-level alarms. The Alarms window shows alarms in conformance with Telcordia GR-253. This means that if a network problem causes two alarms, such as loss of frame (LOF) and loss of signal (LOS), CTC only shows the LOS alarm in this window because it supersedes the LOF and replaces it.
The Path Width column in the Alarms and Conditions tabs expands upon alarmed object information contained in the access identifier (AID) string (such as "STS-4-1-3") by giving the number of synchronous transport signals (STSs) contained in the alarmed path. For example, the Path Width will tell you whether a Critical alarm applies to an STS1 or an STS48c. The column reports the width as a 1, 3, 6, 12, 48, etc. as appropriate, understood to be "STS-N."
Table 10-1 lists the Alarms tab column headings and the information recorded in each column.
Table 10-1 Alarms Column Descriptions
New
Indicates a new alarm. To change this status, click either the Synchronize button or the Delete Cleared Alarms button.
Date
Date and time of the alarm.
Node
Node where the alarm occurred (appears only in network view).
Object
TL1 AID for the alarmed object. For an STSmon or VTmon, this is the monitored STS or VT object, which is explained in Table 10-3.
Eqpt Type
Card type in this slot.
Slot
Slot where the alarm occurred (appears only in network and node view).
Port
Port where the alarm is raised. For STSTerm and VTTerm, the port refers to the upstream card it is partnered with.
Path Width
Indicates how many STSs are contained in the alarmed path. This information compliments the alarm object notation, which is explained in Table 10-3.
Sev
Severity level: CR (Critical), MJ (Major), MN (Minor), NA (Not-Alarmed), NR (Not-Reported).
ST
Status: R (raised), C (clear).
SA
When checked, indicates a service-affecting alarm.
Cond
The error message/alarm name. These names are alphabetically defined in the "Alarm Troubleshooting" chapter of the Cisco ONS 15310-CL Troubleshooting Guide.
Description
Description of the alarm.
Num
Num (number) is the quantity of alarm messages received and is increments automatically as alarms occur to display the current total of received error messages.
Ref
Ref (reference) is a unique identification number assigned to each alarm to reference a specific alarm message that is displayed.
Table 10-2 lists the color codes for alarm and condition severities. In addition to the severities listed in the table, CTC alarm profiles list inherited (I) and unset (U) severities. These are only listed in the network view Provisioning > Alarm Profiles tab and are not currently implemented.
In network view, CTC identifies STS and VT alarm objects using a TL1-type AID, as shown in Table 10-3.
Table 10-3 STS and Alarm Object Identification
OC3/OC12 STS
Syntax: STS-<Slot>-<Ppm>-<Port>-<STS>
Ranges: STS-{2}-{1-2}-{1}-{1-n}1Example: STS-2-1-1-6
OC3/OC12 VT
Syntax: VT1-<Slot>-<Ppm>-<Port>-<STS>-<VT Group>-<VT>
Ranges: VT1-{2}-{1-2}-{1}-{1-n1}-{1-7}-{1-4}Example: VT1-2-1-1-6-1-1
EC1 STS
Syntax: STS-<Slot>-<Port>-<STS>
Ranges: STS-{2}-{1-3}-{1-n}1Example: STS-2-1-6
EC1 VT
Syntax: VT1-<Slot>-<Port>-<STS>-<VT Group>-<VT>
Ranges: VT1-{2}-{1-3}-{1-n}1-{1-7}-{1-4}Example: VT1-2-1-6-1-1
(Electrical)T1 STS
Syntax: STS-<Slot>-<STS>
Ranges: STS-{2}-{1-n}1Example: STS-2-6
T1 VT
Syntax: VT1-<Slot>-<STS>-VT Group>-<VT>
Ranges: VT1-{2}-{1-n}1-{1-7}-{1-3}Example: VT1-2-6-1-1
T3 STS
Syntax: STS-<Slot>-<Port>-<STS>
Ranges: STS-{2}-{1-3}-{1-n}1Example: STS-2-1-6
T3 VT
VT not supported
1 The maximum number of STSs depends on the rate and size of the STS.
10.2.1 Viewing Alarms With Each Node's Time Zone
By default, alarms and conditions are displayed with the time stamp of the CTC workstation where you are viewing them. But you can set the node to report alarms (and conditions) using the time zone where the node is located by clicking Edit > Preferences, and clicking the Display Events Using Each Node's Timezone check box.
10.2.2 Controlling Alarm Display
You can control the display of the alarms shown in the Alarms window. Table 10-4 shows the actions you can perform in the Alarms window.
10.2.3 Filtering Alarms
The alarm display can be filtered to prevent the display of alarms with certain severities or alarms that occurred between certain dates. You can set the filtering parameters by clicking the Filter button at the bottom-left of the Alarms window. You can turn the filter on or off by clicking the Filter tool at the bottom-right of the window. CTC retains your filter activation setting. For example, if you turn the filter on and then log out, CTC keeps the filter active the next time you log in.
10.2.4 Viewing Alarm-Affected Circuits
To view which ONS 15310-CL circuits are affected by a specific alarm, right-clicking an alarm in the Alarm window. A shortcut menu appears (Figure 10-1). When you select the Select Affected Circuits option, the Circuits window opens to show the circuits that are affected by the alarm.
Figure 10-1 Select Affected Circuits Option
10.2.5 Conditions Tab
The Conditions window displays retrieved fault conditions. A condition is a fault or status detected by ONS 15310-CL hardware or software. When a condition occurs and continues for a minimum period, CTC raises a condition, which is a flag showing that this particular condition currently exists on the ONS 15310-CL.
The Conditions window shows all conditions that occur, including those that are superseded. For instance, if a network problem causes two alarms, such as LOF and LOS, CTC shows both the LOF and LOS conditions in this window (even though LOS supersedes LOF). Having all conditions visible can be helpful when troubleshooting the ONS 15310-CL. If you want to retrieve conditions that obey a root-cause hierarchy (that is, LOS supersedes and replaces LOF), you can exclude the same root causes by checking a check box in the window.
Fault conditions include reported alarms and Not-Reported or Not-Alarmed conditions. Refer to the trouble notifications information in the Cisco ONS 15310-CL Troubleshooting Guide for more information about alarm and condition classifications.
10.2.6 Controlling the Conditions Display
You can control the display of the conditions on the Conditions window. Table 10-5 shows the actions you can perform in the window.
10.2.6.1 Retrieving and Displaying Conditions
The current set of all existing conditions maintained by the alarm manager can be seen when you click the Retrieve button. The set of conditions retrieved is relative to the view. For example, if you click the button while displaying the node view, node-specific conditions appear. If you click the button while displaying the network view, all conditions for the network (including ONS 15310 nodes and other connected nodes) appear, and the card view shows only card-specific conditions.
You can also set a node to display conditions using the time zone where the node is located, rather than the time zone of the PC where they are being viewed. See the "Viewing Alarms With Each Node's Time Zone" section for more information.
10.2.6.2 Conditions Column Descriptions
Table 10-6 lists the Conditions window column headings and the information recorded in each column.
Table 10-6 Conditions Column Description
New
Indicates a new condition.
Date
Date and time of the condition.
Object
TL1 AID for the condition object. For an STSmon or VTmon, this is the monitored STS or VT object, which is explained in Table 10-3.
Eqpt Type
Card type in this slot.
Slot
Slot where the condition occurred (appears only in network and node view).
Port
Port where the condition occurred. For STSTerm and VTTerm, the port refers to the upstream card it is partnered with.
Sev1
Severity level: CR (Critical), MJ (Major), MN (Minor), NA (Not-Alarmed), NR (Not-Reported).
SA1
Indicates a service-affecting alarm (when checked).
Cond
The error message/alarm name; these names are alphabetically defined in the Cisco ONS 15310-CL Troubleshooting Guide.
Description
Description of the condition.
Node
Node where the alarm occurred (appears only in network view).
1 All alarms, their severities, and service-affecting statuses are also displayed in the Condition tab unless you choose to filter the alarm from the display using the Filter button.
10.2.6.3 Filtering Conditions
The condition display can be filtered to prevent the appearance of conditions (including alarms) with certain severities or that occurred between certain dates. You can set the filtering parameters by clicking the Filter button at the bottom-left of the Conditions window. You can turn the filter on or off by clicking the Filter tool at the bottom-right of the window. CTC retains your filter activation setting. For example, if you turn the filter on and then log out, CTC keeps the filter active the next time you log in.
10.2.7 Viewing History
The History window displays historic alarm or condition data for the node or for your login session. You can chose to display only alarm history, only events, or both by checking check boxes in the History > Node window. You can view network-level alarm and condition history, such as for circuits, at that level. At the node level, you can see all port (facility), card, STS, and system-level history entries. For example, protection-switching events or performance-monitoring threshold crossings appear here. If you double-click a card, you can view all port, card, and STS alarm or condition history that directly affects the port.
The ONS 15310-CL can store up to 640 Critical alarm messages, 640 Major alarm messages, 640 Minor alarm messages, and 640 condition messages. When any of these limits is reached, the ONS 15310-CL discards the oldest events in that category.
Note
Different views of CTC display different kinds of history:
•
•
•
Tip
If you check the History window Alarms check box, you display the node history of alarms. If you check the Events check box, you display the node history of Not Alarmed and transient events (conditions). If you check both check boxes, you retrieve node history for both.
10.2.7.1 History Column Descriptions
Table 10-7 lists the History window column headings and the information recorded in each column.
Table 10-7 History Column Description
Num
An incrementing count of alarm or condition messages. (The column is hidden by default; to view it, right-click a column and choose Show Column > Num.)
Ref
The reference number assigned to the alarm or condition. (The column is hidden by default; to view it, right-click a column and choose Show Column > Ref.)
Date
Date and time of the condition.
Object
TL1 AID for the condition object. For an STSmon or VTmon, this is the monitored STS or VT object, which is explained in Table 10-3.
Sev
Severity level: Critical (CR), Major (MJ), Minor (MN), Not-Alarmed (NA), Not-Reported (NR).
Eqpt Type
Card type in this slot (only displays in network view and node view).
ST
Status: raised (R), cleared (C), or transient (T).
Description
Description of the condition.
Port
Port where the condition occurred. For STSTerm and VTTerm, the port refers to the upstream card it is partnered with.
Cond
Condition name.
Slot
Slot where the condition occurred (only displays in network view and node view).
SA
A service-affecting alarm (when checked).
10.2.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, 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.
10.3 Alarm Severities
The ONS 15310-CL alarm severities follow the Telcordia GR-253 standard, so a condition may be Alarmed at a severity of Critical (CR), Major (MJ), or Minor (MN) with a severity of Not Alarmed (NA) or Not Reported (NR). These severities are reported in the CTC software Alarms, Conditions, and History windows at all levels: network, node, and card.
ONS equipment provides a standard profile named "Default" that lists 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 needed. (See the "Alarm Profiles" section for more information.) For example, in a custom alarm profile, the default severity of a carrier loss (CARLOSS) alarm on an Ethernet port can be changed from Major to Critical.
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:
•
•
Because the alarm might be raised at two different levels, the alarm profile pane shows Critical as "CR / MN" and Major as "MJ / MN."
10.4 Alarm Profiles
The alarm profiles feature allows you to change default alarm severities by creating unique alarm profiles for individual ONS 15310-CL 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, cards, or 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 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.
If one or more alarm profiles is stored as files from elsewhere in the network onto the local PC or server hard drive where CTC resides, you can use 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.
10.4.1 Creating and Modifying Alarm Profiles
Alarm profiles are created in the network view using the Provisioning > Alarm Profiles tabs. A default alarm severity following Telcordia GR-253 standards is preprovisioned for every alarm. After loading 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
Tip
Wherever it is applied, the Default alarm profile sets severities to standard Telcordia GR-253 settings. In the Inherited profile, alarms inherit, or copy severity 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) are 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. For example, you could use the inherited or default profile on a node and on all cards and ports, but apply a custom profile that downgrades an alarm on one particular card. Or you might choose to downgrade an OC-N unequipped path alarm (UNEQ-P) from Critical (CR) to Not Alarmed (NA) on an optical card because this alarm is raised and then clears every time you create a circuit. UNEQ-P alarms for the card with the custom profile would not display on the Alarms tab (but they would still be recorded on the Conditions and History tabs).
When you modify severities in an alarm profile:
•
•
10.4.2 Alarm Profile Buttons
The Alarm Profiles window displays six buttons at the bottom. Table 10-8 lists and describes each of the alarm profile buttons and their functions.
10.4.3 Alarm Profile Editing
Table 10-9 lists and describes the five profile-editing options available when you right-click an alarm item in the profile column (such as Default).
10.4.4 Alarm Severity Options
To change or assign alarm severity, left-click the alarm severity you want to change in the alarm profile column. Seven severity levels appear for the alarm:
•
•
•
•
•
•
•
Inherited and Use Default severity levels only appear in alarm profiles. They do not appear when you view alarms, history, or conditions.
10.4.5 Row Display Options
In the network view, the Alarm Profiles window displays two check boxes at the bottom of the window:
•
•
10.4.6 Applying Alarm Profiles
In CTC node view, the Alarm Behavior window displays alarm profiles for the node. In card view, the Alarm Behavior window displays the alarm profiles for the selected card. Alarm profiles form a hierarchy. A node alarm profile applies to all cards in the node except cards that have their own profiles. A card alarm profile applies to all ports on the card except ports that have their own profiles.
At the node level, you can apply profile changes on a card-by-card basis or set a profile for the entire node. At the card view, you can apply profile changes on a port-by-port basis or set alarm profiles for all ports on that card. Figure 10-2 shows the CE-100T-8 card alarm profiles.
Figure 10-2 Alarm Profiles for a CE-100T-8 Card
10.5 Alarm Suppression
ONS 15310 nodes have an alarm suppression option that clears raised alarm messages for the node, chassis, one or more slots (cards), or one or more ports. After they are cleared, these alarms change appearance from their normal severity color to white and they can be cleared from the display by clicking Synchronize. Alarm suppression itself raises an alarm called AS-CMD that is shown in applicable Alarms windows. Node-level suppression is shown in the node-view Alarms window, and card or port level suppression is shown in all views. The AS-CMD alarm itself is not cleared by the suppress command. Each instance of this alarm indicates its object separately in the Object column.
A suppression command applied at a higher level does not supersede a command applied at a lower level. For example, applying a node-level alarm suppression command makes all raised alarms for the node appear cleared, but it does not cancel card level or port level suppression. Each of these conditions can exist independently and must be cleared independently.
Suppression causes the entity alarm to behave like a Not-Reported event. This means that the alarms, having been suppressed from view in the Alarms window, are now only shown in the Conditions window. The suppressed alarms are displayed with their usual visual characteristics (service-affecting status and color-coding) in the window. The alarms still appear in the History window.
Note
10.6 External Alarms and Controls
External alarm physical connections are made with the 15310-CL ALARM port. However, the alarms are provisioned using the 15310-CL-CTX card view for external sensors such as an open door and flood sensors, temperature sensors, and other environmental conditions. External control outputs on the 15310-CL-CTX card allow you to drive external visual or audible devices such as bells and lights. They can control other devices such as generators, heaters, and fans.
Provision external alarms in the 15310-CL-CTX card view Provisioning > External Alarms tab and provision controls in the 15310-CL-CTX card view Provisioning > External Controls tab. Up to 32 alarm contact inputs and 8 alarm contact outputs are available with the CTX2500 cards and 15310-CL-CTX cards report some of these alarms.
10.6.1 External Alarm Input
You can provision each alarm input separately. Provisionable characteristics of external alarm inputs include:
•
•
•
•
•
Note
Note
10.6.2 External Control Output
You can provision each alarm output separately. Provisionable characteristics of alarm outputs include:
•
•
•
•
–
–
–
