- Preface
- Overview of Cisco MNM
- Configuring Network Devices for Management
- Getting Started with Cisco MNM
- Setting Up Cisco MNM Security
- Deploying Your Network in Cisco MNM
- Managing Faults with Cisco MNM
- Managing the Performance of Cisco MNM Devices
- Other Network Management Tasks
- Cisco MNM System Administration
- Alarm Message Reference
- Performance Measurements Reference
- Troubleshooting Cisco MNM
- Index
- Overview of Cisco MNM Alarm Management
- Looking Up Cisco PGW 2200 Softswitch and Cisco BAMS Alarm Messages
- Cisco PGW 2200 Softswitch Host Alarm Messages
- Cisco BAMS Alarm Messages
- Cisco HSI Server Alarm Messages
- Cisco PGW 2200 Softswitch Host and Cisco BAMS Resource Alarms
- Cisco ITP-L Alarm Messages
- Cisco LAN Switch Alarm Messages
Alarm Message Reference
This section provides reference information about alarm messages displayed in the Cisco Media Gateway Controller (MGC) Node Manager (MNM) Event Browser. Specifically:
•
For the Cisco PGW 2200 Softswitch and the Cisco Billing and Measurements Server (BAMS), this section provides:
–References from which you can navigate to the relevant document to find the message you are interested in (see the "Cisco PGW 2200 Softswitch Host Alarm Messages" section and the "Cisco BAMS Alarm Messages" section). A short description of each document is included.
–Instructions for looking up the desired message in the referenced document (see the "Looking Up Cisco PGW 2200 Softswitch and Cisco BAMS Alarm Messages" section).
–A list and short description of application-related alarm messages (see the "Cisco PGW 2200 Softswitch Host and Cisco BAMS Resource Alarms" section).
•For the Cisco ITP-L and Cisco LAN Switches, this section lists messages and provides short descriptions (see the "Cisco ITP-L Alarm Messages" section).
Note Cisco IP Transfer Point LinkExtender (ITP-L) is the new name for Cisco Signaling Link Terminal (SLT). Over time, ITP-L will replace SLT in publications and the product.
Overview of Cisco MNM Alarm Management
Cisco MNM converts traps received from managed devices to alarms which are displayed in the Event Browser. For the Cisco ITP-L and the Cisco LAN switches, each trap has a corresponding Cisco MNM alarm. For example, the linkDown trap from the Cisco ITP-L corresponds to the "Link down" event description in the Cisco MNM Event Browser. For the Cisco BAMS and the Cisco PGW 2200 Softswitch, the trap serves as an envelope that can carry any one of numerous alarm messages.
Note Cisco MNM does not handle every possible trap that can be generated from each of the network elements, only those traps that are used for management of the devices as they are deployed to support the Cisco PGW 2200 Softswitch node configuration.
In addition to device-specific traps, Cisco MNM generates internal alarms. Appendix C, "Troubleshooting Cisco MNM" provides an explanation of these internal messages.
Looking Up Cisco PGW 2200 Softswitch and Cisco BAMS Alarm Messages
Use this procedure to locate information for a specific alarm message.
Step 1 In the Event Browser, check the Object Name to determine the network object that generated the event, and note the event description.
Step 2 In this document, go to the section that applies to that object.
Step 3 Click the name of the document or section (displayed in blue to indicate a link) that contains the information you want. The linked document opens.
Step 4 Press Ctrl-F for your browser's Find dialog box.
Step 5 In the dialog box, enter some of the initial text of the event description, and click OK.
Note If your search text is not found, it means that the Event Browser description does not match exactly the generated message. You can search on a different part of the description string, or scroll through the document to find the message.
Cisco PGW 2200 Softswitch Host Alarm Messages
Cisco MNM handles the traps in Table A-1 from the Cisco PGW 2200 Softswitch hosts. Each trap is used as an envelope for alarms of that type.
For system messages information, see the Cisco PGW 2200 Softswitch Release 9 Messages Reference at
http://www.cisco.com/en/US/docs/voice_ip_comm/pgw/9/system/message/errmsg.html
The alarm documentation includes the following information on each event:
•Alarm category—Alarm/event message, corresponding to the event description in the Cisco MNM Event Browser.
•Description—Brief description of the alarm/event.
•Severity level—The severity of the alarm/event.
•Event reporting—Whether the event is reported to the management interface and can be obtained using SNMP. (The Event Browser lists only those events that are reported.)
•Alarm/event cause—The condition causing the alarm/event.
•SNMP trap type—Which SNMP trap type pertains to the event, displayed with a numeric code for the trap type:
–0 = Do not send an SNMP trap
–1 = Communication alarm
–2 = Quality of service alarm
–3 = Processing error alarm
–4 = Equipment error alarm
–5 = Environment error alarm
•Suggested Action—Recommendations for resolving the problem.
Cisco BAMS Alarm Messages
All Cisco BAMS alarms are carried on a single trap, the AlarmTrap, as shown in Table A-2.
|
|
|
nusageAlarmTrap |
ACECOMM-NUSAGE-MIB |
The BAMS captures alarms and minor, major, or critical events and forwards them to network management systems such as Cisco MNM. The severity level for message forwarding defaults to minor and above but may be changed by the BAMS system administrator.
The Cisco Billing and Measurements Server User's Guide at http://www.cisco.com/en/US/docs/voice_ip_comm/pgw/bams/3.30/guide/330_ug.html includes an appendix (Appendix A. Troubleshooting) that provides a discussion of these messages and their use in troubleshooting. Messages are related to the tasks the BAMS performs, and the appendix also includes an explanation of the BAMS tasks. The message documentation is organized by task.
The following categories of information are provided for each system message:
• Message ID—A six-character label that uniquely identifies each message. The first three characters are the application task ID, which identifies the application task that generated the message. (For example, MGR denotes the Manager task and MSC denotes the Mass Storage Control task.) The second three characters are the message number; for example, 013 or 122.
• Text—The verbal part of the message that appears in the system log file, which generally corresponds to the event description in the Cisco MNM Event Browser.
• Arguments—Variable parts of the message, enclosed in angle brackets.
• Description—An explanation of the event that generated the message.
• Action—What you should do as a result of the event described in the message. In some cases; for example, informational messages, no action may be required. Actions for error messages (manual, warning, minor, major, and critical) may include steps that should be followed to identify and correct problems. Error actions might also describe how the BAMS responds to the specified error condition.
Note The BAMS File Rename Failure alarm (POL115) must be manually cleared not only in Cisco MNM but also on the BAMS before new alarms of that type can be generated.
Cisco HSI Server Alarm Messages
The Cisco HSI adjunct generates autonomous messages, or events, to notify you of problems or atypical network conditions. Depending on the severity level, events are considered alarms or informational events. The Cisco HSI adjunct captures minor, major, and critical events and forwards them to the Cisco MNM.
The Cisco H.323 Signaling Interface User Guide at http://www.cisco.com/en/US/docs/voice_ip_comm/pgw/hsi/4.3/guide/43ug.html provides details on these messages and their use in troubleshooting. The following information is provided for each alarm message:
•Description
•Severity Level and Trap Type
•Cause
•Troubleshooting Procedure
Cisco PGW 2200 Softswitch Host and Cisco BAMS Resource Alarms
Cisco MNM traps application-related events that occur on the Cisco PGW 2200 Softswitch host or the Cisco BAMS, as shown in Table A-3.
Note You can also monitor the performance of the following Cisco PGW 2200 Softswitch host and Cisco BAMS system components: fixed disk storage used, processor load, RAM, and virtual memory used. See Appendix B, "Performance Measurements Reference," "Performance Data Collected for System Components" section on page B-11.
Cisco ITP-L Alarm Messages
Cisco LAN Switch Alarm Messages
Catalyst 5500 and 6509 Alarms
Catalyst 2900XL Alarms
Cisco PGW 2200 Softswitch Alarm Messages
The Cisco PGW 2200 Softswitch generates messages, or events, to notify you of problems or atypical network conditions. Depending on the severity level, events are considered alarms or informational events. Events with a severity level of critical, major, or minor are classified as alarms, and then reported to the built-in alarm relay unit (ARU). The alarms can be retrieved through MML and a Simple Network Management Protocol (SNMP) manager.
Alarms and informational events follow the Telcordia Transaction Language 1 (TL1) message format.
Alarms and informational events produce different system responses. An alarm is reported when an alarm state changes (assuming the alarm does not have a non-reported severity). It is a significant violation of existing management systems to report consecutive state changes, active or clear, for a particular alarm on a single entity.
An informational event is reported without a state change being required. It is a warning that an abnormal condition has occurred that does not require corrective action by the management center. An invalid protocol call state transition is an example of an informational event. The event needs to be reported, and if it is transient, there is no corrective action that can be initiated by the management center to fix the problem.
An informational event is reported once, upon occurrence, through the MML and SNMP interfaces. The MML interface must be in the RTRV-ALMS::CONT mode for the event to be displayed; it is not displayed in subsequent RTRV-ALMS requests.
Table A-7 defines the Cisco PGW 2200 Softswitch message components that are displayed by means of the RTRV-ALMS::CONT command in its state of listening for alarm events.
Feedback