- Preface
- Chapter 1, Shelf and Backplane Hardware
- Chapter 2, Common Control Cards
- Chapter 3, Electrical Cards
- Chapter 4, Optical Cards
- Chapter 5, Ethernet Cards
- Chapter 6, Storage Access Networking Cards
- Chapter 7, Card Protection
- Chapter 8, Cisco Transport Controller Operation
- Chapter 9, Security
- Chapter 10, Timing
- Chapter 11, Circuits and Tunnels
- Chapter 12, SONET Topologies and Upgrades
- Chapter 13, Management Network Connectivity
- Chapter 14, Alarm Monitoring and Management
- Chapter 15, Performance Monitoring
- Chapter 16, SNMP
- Appendix A, Hardware Specifications
- Appendix B, Administrative and Service States
- Appendix C, Network Element Defaults
Alarm Monitoring and Management
This chapter describes Cisco Transport Controller (CTC) alarm management. To troubleshoot specific alarms, refer to the Cisco ONS 15454 Troubleshooting Guide. Chapter topics include:
14.1 Overview
CTC detects and reports SONET alarms generated by the Cisco ONS 15454 and the larger SONET network. You can use CTC to monitor and manage alarms at the card, node, or network level. Alarming conforms to Telcordia GR-253 standard. Severities conform to Telcordia GR-474, 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 15454 Troubleshooting Guide.
Note 
ONS 15454 alarms can also be monitored and managed through Transaction Language One (TL1) or a network management system (NMS).
14.2 LCD Alarm Counts
You can view node, slot, or port-level alarm counts and summaries using the buttons on the ONS 15454 LCD panel. The Slot and Port buttons toggle between display types; the Slot button toggles between node display and slot display, and the Port button toggles between slot and port views. Pressing the Status button after you choose the display mode changes the display from alarm count to alarm summary.
The ONS 15454 has a one-button update for some commonly viewed alarm counts. If you press the Slot button once and then wait eight seconds, the display automatically changes from a slot alarm count to a slot alarm summary. If you press the Port button to toggle to port-level display, you can use the Port button to toggle to a specific slot and to view each port's port-level alarm count. Figure 14-1 shows the LCD panel layout.
Figure 14-1 Shelf LCD Panel
14.3 Alarm Information
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 LOF. (The LOF alarm can still be retrieved in the Conditions window.)
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 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 14-1 lists the column headings and the information recorded in each column.
Note When an entity is put in the OOS,MT administrative state, the ONS 15454 suppresses all standing alarms on that entity. All alarms and events appear on the Conditions tab. You can change this behavior for the LPBKFACILITY and LPBKTERMINAL alarms. To display these alarms on the Alarms tab, set the NODE.general.ReportLoopbackConditionsOnPortsInOOS-MT to TRUE on the NE Defaults tab.
Table 14-2 lists the color codes for alarm and condition severities. The inherited (I) and unset (U) severities are only listed in the network view Provisioning > Alarm Profiles tab.
Note Major and Minor alarms might appear yellow in CTC under certain circumstances. This is not due to a CTC problem but to a workstation memory and color utilization problem. For example, a workstation might run out of colors if many color-intensive applications are running. When using Netscape, you can limit the number of colors used by launching it from the command line with either the -install option or the -ncols 32 option.
14.3.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.
14.3.2 Controlling Alarm Display
You can control the display of the alarms shown on the Alarms window. Table 14-3 shows the actions you can perform in the Alarms window.
14.3.3 Filtering Alarms
The alarm display can be filtered to prevent display of alarms with certain severities or alarms that occurred between certain dates and times. 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.
14.3.4 Viewing Alarm-Affected Circuits
A user can view which ONS 15454 circuits are affected by a specific alarm by positioning the cursor over the alarm in the Alarm window and right-clicking. A shortcut menu appears (Figure 14-2). When the user selects the Select Affected Circuits option, the Circuits window opens to show the circuits that are affected by the alarm.
Figure 14-2 Select Affected Circuits Option
14.3.5 Conditions Tab
The Conditions window displays retrieved fault conditions. A condition is a fault or status detected by ONS 15454 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 15454.
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 15454. 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 "Exclude Same Root Cause" 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 15454 Troubleshooting Guide for more information about alarm and condition classifications.
14.3.6 Controlling the Conditions Display
You can control the display of the conditions on the Conditions window. Table 14-4 shows the actions you can perform in the window.
14.3.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 are displayed. If you click the button while displaying the network view, all conditions for the network (including ONS 15454 nodes and other connected nodes) are displayed, 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.
14.3.6.2 Conditions Column Descriptions
Table 14-5 lists the Conditions window column headings and the information recorded in each column.
|
|
|
|---|---|
Date |
Date and time of the condition. |
Node |
Shows the name of the node where the condition or alarm occurred. (Visible in network view.) |
Object |
TL1 AID for the condition object. For an STSmon or VTmon, the object. |
Eqpt Type |
Card type in this slot. |
Shelf |
For DWDM configurations, the shelf where the alarmed object is located. Visible in network view. |
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. |
Path Width |
Width of the data path. |
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 "Alarm Troubleshooting" chapter of the Cisco ONS 15454 Troubleshooting Guide. |
Description |
Description of the condition. |
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. |
14.3.6.3 Filtering Conditions
The condition display can be filtered to prevent display 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 your user ID is activated.
14.3.7 Viewing History
The History window displays historic alarm or condition data for the node or for your login session. You can choose to display only alarm history, only events, or both by checking check boxes in the History > Shelf window. You can view network-level alarm and condition history, such as for circuits, for all the nodes visible in network view. At the node level, you can see all port (facility), card, STS, and system-level history entries for that node. 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 card.
Note In the Preference dialog General tab, the Maximum History Entries value only applies to the Session window.
Different views of CTC display different kinds of history:
•The History > Session window is shown in network view, node view, and card view. It shows alarms and conditions that occurred during the current user CTC session.
•The History > Shelf window is only shown in node view. It shows the alarms and conditions that occurred on the node since CTC software was operated on the node.
•The History > Card window is only shown in card view. It shows the alarms and conditions that occurred on the card since CTC software was installed on the node.
Tip Double-click an alarm in the History window to display the corresponding view. For example, double-clicking a card alarm takes you to card view. In network view, double-clicking a node alarm takes you to node view.
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.
14.3.7.1 History Column Descriptions
Table 14-6 lists the History window column headings and the information recorded in each column.
14.3.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 > Shelf 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.
14.3.8 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:
•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 alarm severities follow the Telcordia GR-253 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 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 "Alarm Profiles" section.) 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 (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 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-474 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 have been 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.
14.5.1 Creating and Modifying Alarm Profiles
Alarm profiles are created in the network view using the Provisioning > Alarm Profiles tabs. Figure 14-3 shows the default list of alarm severities. 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 clone a profile to create custom profiles. After the new profile is created, the Alarm Profiles window shows the original profile (frequently Default) and the new profile.
Figure 14-3 Network View Alarm Profiles Window
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.
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 10 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 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 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 an alarm on one particular card. For example, 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 raises 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:
•All Critical (CR) or Major (MJ) default or user-defined severity settings are demoted to Minor (MN) in Non-Service-Affecting (NSA) situations as defined in Telcordia GR-474.
•Default severities are used for all alarms and conditions until you create a new profile and apply it.
The Load and Store buttons are not available for Retrieve and Maintenance users.
The Delete and Store options will only display nodes to delete profiles from or store profiles to if the user has provisioning permission for those nodes. If the user does not have the proper permissions, CTC greys out the buttons and they are not available to the user.
14.5.2 Alarm Profile Buttons
The Alarm Profiles window displays six buttons at the bottom of the window. Table 14-7 lists and describes each of the alarm profile buttons and their functions.
14.5.3 Alarm Profile Editing
Table 14-8 lists and describes the five profile-editing options available when you right-click an alarm item in the profile column.
14.5.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:
•Not Reported (NR)
•Not Alarmed (NA)
•Minor (MN)
•Major (MJ)
•Critical (CR)
•Use Default
•Inherited
Inherited and Use Default severity levels only appear in alarm profiles. They do not appear when you view alarms, history, or conditions.
14.5.5 Row Display Options
The Alarm Profiles window (from network view) or the Alarm Profile Editor (from node view) displays three check boxes at the bottom of the window:
•Only show service-affecting severities—If unchecked, the editor shows severities in the format <sev1>/<sev2> where <sev1> is a service-affecting severity and <sev2> is not service-affecting. If checked, the editor only shows <sev1> alarms.
•Hide reference values—Highlights alarms with non-default severities by clearing alarm cells with default severities. This check-box is normally greyed out. It becomes active only when more than one profile is listed in the Alarm Profile Editor window. (The check box text changes to "Hide Values matching profile Default" in this case.
•Hide identical rows—Hides rows of alarms that contain the same severity for each profile.
14.5.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-level alarm profile applies to all cards in the node except cards that have their own profiles. A card-level 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-level view, you can apply profile changes on a port-by-port basis or set alarm profiles for all ports on that card. Figure 14-4 shows the DS1 card alarm profile.
Figure 14-4 DS1 Card Alarm Profile
14.6 Alarm Suppression
The following sections explain alarm suppression features for the ONS 15454.
14.6.1 Alarms Suppressed for Maintenance
When you place a port in OOS,MT administrative state, this raises the alarm suppressed for maintenance (AS-MT) alarm in the Conditions and History windows1 and causes subsequently raised alarms for that port to be suppressed.
While the facility is in the OOS,MT state, any alarms or conditions that are raised and suppressed on it (for example, a transmit failure [TRMT] alarm) are reported in the Conditions window and show their normal severity in the Sev column. The suppressed alarms are not shown in the Alarms and History windows. (These windows only show AS-MT). When you place the port back into IS,AINS administrative state, the AS-MT alarm is resolved in all three windows. Suppressed alarms remain raised in the Conditions window until they are cleared.
14.6.2 Alarms Suppressed by User Command
In the Provisioning > Alarm Profiles > Alarm Behavior tabs, the ONS 15454 has an alarm suppression option that clears raised alarm messages for the node, chassis, one or more slots (cards), or one or more ports. Using this option raises the alarms suppressed by user command, or AS-CMD alarm. The AS-CMD alarm, like the AS-MT alarm, appears in the Conditions, and History1 windows. Suppressed conditions (including alarms) appear only in the Conditions window--showing their normal severity in the Sev column. When the Suppress Alarms check box is unchecked, the AS-CMD alarm is cleared from all three windows.
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 to be cleared, but it does not cancel out card-level or port-level suppression. Each of these conditions can exist independently and must be cleared independently.
Use alarm suppression with caution. If multiple CTC or TL1 sessions are open, suppressing the alarms in one session suppresses the alarms in all other open sessions.
14.7 External Alarms and Controls
External alarm inputs can be provisioned on the Alarm Interface Controller-International (AIC-I) card for external sensors such as an open door and flood sensors, temperature sensors, and other environmental conditions. External control outputs on these two cards 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.
You provision external alarms in the AIC-I card view Provisioning > External Alarms tab and controls in the AIC-I card view Provisioning > External Controls tab. Up to 12 external alarm inputs and four external controls are available. If you also provision the alarm extension panel (AEP), there are 32 inputs and 16 outputs.
14.7.1 External Alarms
You can provision each alarm input separately. Provisionable characteristics of external alarm inputs include:
•Alarm Type—List of alarm types.
•User Defined Alarm Types
•Severity—CR, MJ, MN, NA, and NR.
•Virtual Wire—The virtual wire associated with the alarm.
•Raised When—Open means that the normal condition is to not have current flowing through the contact, and the alarm is generated when current does flow; closed means that the normal condition is to have current flowing through the contact, and the alarm is generated when current stops flowing.
•Description—CTC alarm log description (up to 63 characters).
Note If you provision an external alarm to raise when a contact is open, and you have not attached the alarm cable, the alarm will remain raised until the alarm cable is connected.
Note When you provision an external alarm, the alarm object is ENV-IN-nn. The variable nn refers to the external alarm's number, regardless of the name you assign.
14.7.2 User Defined Alarm Types
User Defined Alarm Types allows you to dynamically add and delete the alarm types. In addition to the existing hard coded alarm type attributes, you can define up to 50 alarm types. These dynamically added alarm types can be associated, or disassociated, to any external alarm input and the added alarm type can use the same behavior as hard coded alarm type attributes.
The following limits and guidelines apply:
•An AIC or AIC-I card must be installed
•Up to 50 Alarm Types can be defined
•The User Defined name can be up to 20 alphanumeric characters (upper case).
•The User Defined name can not contain special characters or spaces (Hyphen (-) is allowed)
14.7.3 External Controls
You can provision each alarm output separately. Provisionable characteristics of alarm outputs include:
•Control type.
•Trigger type (alarm or virtual wire).
•Description for CTC display.
•Closure setting (manually or by trigger). If you provision the output closure to be triggered, the following characteristics can be used as triggers:
–Local NE alarm severity—A chosen alarm severity (for example, major) and any higher-severity alarm (in this case, critical) causes output closure.
–Remote NE alarm severity—Similar to local NE alarm severity trigger setting, but applies to remote alarms.
–Virtual wire entities—You can provision an alarm that is input to a virtual wire to trigger an external control output.
Feedback