Table Of Contents
Obsolete Autonomous System Messages
Autonomous System Messages
Revised: September 28, 2009, OL-1117-08This chapter lists autonomous system messages generated by the Cisco PGW 2200 Softswitch software, including Man Machine Language (MML) responses, alarms, and events. The Cisco PGW 2200 Softswitch software also includes a logging system that writes messages to log files determined during the client initialization period. For a listing of these log messages and for information on using and working with log messages, see Chapter 2, "Log Messages" of this manual. See the Cisco PGW 2200 Softswitch MML Command Reference Guide for more information about MML commands. This chapter contains the following sections:
•
Autonomous Message Components
•
Some ISUP alarms do not generate corresponding traps. You can identify these alarms by checking the following files or monitoring real-time alarms:
•
•
–
–
Example: The alm_20030328052312_012345.log file has a timestamp of 2003/03/28 05:23:12 and a sequence number of 12345.
For more information on alarm log files, see Appendix A, Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
•
Autonomous Message Components
The Cisco PGW 2200 Softswitch 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. Events with a severity level of critical, major, or minor are classified as alarms; are reported to the built-in alarm relay unit (ARU); and can be retrieved through MML and a Simple Network Management Protocol (SNMP) manager.
Alarms and informational events follow the Telcordia TL1 autonomous 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 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 1-1 defines the message components that are displayed by means of the RTRV-ALMS::CONT command in its state of listening for alarm events.
Note
Figure 1-1 shows an example of an alarm message from RTRV-ALMS.
Figure 1-1 Sample Alarm Message
This example shows a signaling channel configuration failure on component DC-1-1 and indicates that the message is an alarm with a major severity level.
To determine the meaning of the alarm or event, locate the alarm/event description in the sections that follow.
Alarm/Event Categories
This document uses the following format to describe autonomous system messages:
Alarm/Event Category—The alarm/event message text as it is displayed in MML.
Description
A brief description of the alarm or event.
Severity
The severity level of the alarm or event.
•
Critical alarms cause failover (the active server switches processing to the standby server).
Critical alarms should be cleared immediately.•
Major alarms differ from critical alarms in that they do not cause failovers.
Major alarms should also be cleared immediately.•
•
Reported
Whether the event is reported to the management interface and can be obtained using SNMP.
•
•
Note
Cause
Description of the condition causing the alarm or event.
SNMP Trap Type
The Cisco PGW 2200 Softswitch software generates an SNMP trap for autonomous messages of SNMP trap type 1 through 5. SNMP traps are not generated for SNMP trap type 0 messages. SNMP trap types are:
•
•
•
•
•
•
Action
Recommendations for resolving the problem.
Note
Autonomous System Messages
Autonomous system messages and informational events that are reported by the Cisco PGW 2200 Softswitch are described in this section in alphabetical order.
Active and standby machines have different license files
Description
License files are mismatched between active and standby Cisco PGW 2200 Softswitches. Local files are used.
Severity
Major (service affecting)
Cause
License files are different on both machines.
SNMP Trap Type
3 (Processing error alarm)
Action
Check the license files on the active and standby machines to ensure that they use the same license files, and then run the license reload script to load the new license files.
Admin State Locked
Description
Component has been placed in administrative state of locked. The lock procedure gracefully takes down the calls and marks bearer channels as locked.
Severity
Informational
Cause
Generated when the MML command SET-ADMIN-STATE is used to lock a component. The engine for MGC, GWAY, SIGPATH and TRUNKGROUP components generates this event to mark the start of the lock procedure. The lock process marks bearer channels as locked and allows calls to terminate gracefully.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
No action necessary. For more information, see the Admin State Unlocked event, below, and the Cisco PGW 2200 Softswitch Release 9 MML Command Reference Guide.
Admin State Reset
Description
Component has been placed in administrative state of reset.
Severity
Informational
SNMP Trap Type
0 (Do not send an SNMP trap.)
Cause
This alarm is raised after the user runs the MML command:
set-admin-state:target:reset,confirmThe Cisco PGW 2200 Softswitch releases calls, clears any local blocking and sends out this alarm.
Action
None required. This alarm is for informational purposes only.
Admin State Unlocked
Description
Component has been placed in the administrative state of Unlocked. The unlocked procedure marks bearer channel as available for call processing.
Severity
Informational
Cause
Generated when the MML command SET-ADMIN-STATE is used to unlock a component. The engine for MGC, gateway, sigpath, and trunk group components generate this event to mark the start of the Unlock process. The Unlock process unblocks bearer channels and allows bearer channels to be available for call processing.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
No action necessary. For more information, see the Admin State Locked event, above, and the Cisco PGW 2200 Softswitch Release 9 MML Command Reference Guide.
All C7 IP Links Fail
Description
All links transporting MTP3 messages to the signal terminal failed.
Severity
Major
Note
Cause
Generated when MTP2 is terminated on a series of Cisco SLTs, and MTP3 is backhauled to the Cisco PGW 2200 Softswitch over the Ethernet. This event is reported when communication is lost to all Cisco ITP-Ls.
SNMP Trap Type
1 (Communication alarm)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
All Conn Cntl Links Fail
Description
All links transporting connection control messages failed.
Severity
Major
Cause
Generated when the MGCP or SGCP session loses a heartbeat, indicating that the session is down.
SNMP Trap Type
1 (Communication alarm)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
All ISDN BRI IP Conn Fail
Description
All IP connections supporting an QSIG/Q.931 Over BRI Backhaul signaling service have failed.
Severity
Major
Cause
This alarm is reported when all IP connections supporting an QSIG/Q.931 Over BRI Backhaul signaling service have failed.
SNMP Trap Type
1 (Communication alarm)
Action
See the All ISDN BRI IP Conn Fail section.
All ISDN IP Conn Fail
Description
All IP connections supporting ISDN have failed.
Severity
Critical
Note
This property should be set to true if your Cisco PGW 2200 Softswitch hosts are in separate geographic locations. You can also set this parameter to true if your system is not processing SS7 calls and you want your system to perform an automatic switchover should all of the ISDN IP connections fail.Cause
Generated when ISDN layer 2 is terminated on a series of Cisco access servers and backhauled to the Cisco PGW 2200 Softswitch over the Ethernet. This event is reported when communication is lost to all access servers, defaulting to a critical alarm and causing a failover if standby is present.
SNMP Trap Type
1 (Communication alarm)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
All M3UAKEY Acks Pending
Description
All acknowledgements for an M3UAKEY associated with this SS7PATH have not been received
Severity
Major
Cause
The Cisco PGW 2200 Softswitch cannot send or receive traffic for the SS7PATH
SNMP Trap Type
1 (Communication alarm)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
All M3UA Assoc Fail
Description
All M3UA associations transporting SS7 signaling have failed.
Severity
Major
Note
Cause
All M3UA associations transporting SS7 signaling have failed.
SNMP Trap Type
1 (Communication alarm)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
All SUAKEY Acks Pending
Description
All acknowledgements for an SUAKEY associated with this SS7SUBSYS have not been received.
Severity
Major
Cause
The Cisco PGW 2200 Softswitch cannot send or receive traffic for the SS7SUBSYS.
SNMP Trap Type
1 (Communication alarm)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
All SUA Assoc Fail
Description
All SUA associations transporting SS7 signaling have failed.
Severity
Major
Note
Cause
All SUA associations transporting SS7 signaling have failed.
SNMP Trap Type
1 (Communication alarm)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
ANAL: ALoopCtrExceeded
Description
A loop counter was exceeded.
Severity
Informational
Cause
Indicates that the A-number analysis has gone into an infinite loop. The purpose of the alarm is to limit the number of passes spent in the analysis tree to 30.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
ANAL: ATableFail_GetDigMod
Description
A-number failed getting modification table.
Severity
Informational
Cause
Indicates that retrieval of a modification string failed during A-number analysis. The problem occurs if the modification table is not loaded or a pointer to a nonexistent location in the modification table is given.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
Check the logs to ensure that there have been no errors in loading the dial plan. Ensure that the dial plan was imported into the system using either MML commands or the SNMP manager.
ANAL: ATableFail_GetResult
Description
A-table failed getting result table.
Severity
Informational
Cause
The access to the result table failed during A-number analysis. The problem occurs if the result table is not loaded or a pointer to a nonexistent location in the result table is given. If trapped in the pre-analysis stage, the alarm "ANAL:Prof_GetFail_RsltTbl" is generated, whereas if trapped at the formal analysis stage (main analysis), this alarm is generated.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
ANAL: ATableFlt_DgtRangeError
Description
A-Number analysis digit tree accessed with a digit out of range
Severity
Major
Cause
The A-number analysis digit tree has been accessed with a digit that is out of range for the digit tree table. This event could occur if the system was incorrectly configured expecting a base 10 dial plan and an overdecadic digit was received from the line and passed to analysis.
SNMP Trap Type
3 (Processing error alarm)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
ANAL: ATableFlt_IdxRangeError
Description
A-number analysis Digit tree accessed with a start-index out of range
Severity
Major
Cause
The A-number analysis digit tree has been accessed with a start-index that is out of range. This event could occur if there was a problem with the start-index pointing to an undefined location in the dial plan.
SNMP Trap Type
3 (Processing error alarm)
Action
Contact the Cisco TAC for assistance in resolving this problem.
ANAL: BLoopCtrExceeded
Description
B-loop counter exceeded.
Severity
Informational
Cause
Indicates that the B-number analysis has gone into an infinite loop. The purpose of the alarm is to limit the number of passes spent in the analysis tree to 30.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
ANAL: BNum_GetFail_SrvcTbl
Description
B-number analysis was unable to read the service table.
Severity
Informational
Cause
Occurs during B-number analysis when a screening result is encountered, and an attempt to read the service table to determine the name of the service performing the screening fails, due to corruption of either the result table or the service table.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
ANAL: BNum_MdfyBFail_ AnnounceID
Description
The B-number analysis failed to modify B-number to include AnnounceID as last 4 digits.
Severity
Informational
Cause
Occurs during B-number analysis when an announcement result is encountered and the analysis is unable to replace the last four digits of the B-number with the announcement ID. This event is commonly caused by an out-of-range announcement ID (it should be 0 to 9999) or a B-number less than four digits long.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
ANAL: BTableFail_GetDigMod
Description
B number failed getting modification table.
Severity
Informational
Cause
Retrieval of a modification string failed while performing B-number analysis. The problem occurs if the modification table is not loaded or a pointer to a nonexistent location in the modification table is given.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
ANAL: BTableFail_GetResult
Description
B table failed getting result table.
Severity
Informational
Cause
Access to the result table failed while performing B-number analysis. The problem occurs if the result table is not loaded or a pointer is given to a nonexistent location in the result table. If trapped in the pre-analysis stage, the alarm "ANAL:Prof_GetFail_RsltTbl" is generated, whereas if trapped at the formal analysis stage (main analysis) this alarm is generated.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
ANAL: BTableFlt_DgtRangeError
Description
B-Number analysis digit tree accessed with a digit out of range.
Severity
Major
Cause
During a B-number digit tree analysis, the tree has been accessed with a digit that is out of range for the digit tree table. This event could occur if the system was incorrectly configured expecting a base 10 dial plan and an overdecadic digit was received from the line and passed to analysis.
SNMP Trap Type
3 (Processing error alarm)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
ANAL: BTableFlt_IdxRangeError
Description
B-number analysis digit tree accessed with a start-index out of range
Severity
Major
Cause
The B-number analysis digit tree has been accessed with an out of range start-index. This event could occur if there was a problem with the start-index pointing to an undefined location in the dial plan.
SNMP Trap Type
3 (Processing error alarm)
Action
Contact the Cisco TAC for assistance in resolving this problem.
ANAL: Cause_GetFail_CauseTbl
Description
The cause analysis was unable to read the cause table.
Severity
Informational
Cause
Occurs during cause analysis when the cause table is unreadable. This event can be due to the cause table being corrupted, a failure in the underlying software, or the cause table being built without all the existing call context cause values
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
ANAL: Cause_GetFail_DigModTbl
Description
The cause analysis was unable to read the digit modification string.
Severity
Informational
Cause
Occurs during cause analysis when a B-number modification result is encountered, and the digit modification string is unreadable. This event can be due to the digit modification table being corrupted or an incorrect digit modification index being stored in the B-number modification result data.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
ANAL: Cause_GetFail_InvldRsltType
Description
The cause analysis encountered a result that is not valid during cause analysis.
Severity
Informational
Cause
Occurs during cause analysis when a result is encountered that is not supported in cause analysis. This event is due to corruption of the cause or location tables or the result table.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
ANAL: Cause_GetFail_LocTbl
Description
The cause analysis was unable to read the location table.
Severity
Informational
Cause
Occurs during cause analysis when the location table is unreadable. This event can be due to the location table being corrupted, a failure in the underlying software, or the location table not being fully populated with all possible references from the cause table.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
ANAL: Cause_GetFail_RsltTbl
Description
The cause analysis was unable to read the result table.
Severity
Informational
Cause
Occurs during cause analysis when the result table is unreadable. This event can be due to the result table being corrupted, a failure in the underlying software, or the result table not being fully populated with all possible references from the cause and location tables.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
ANAL: Cause_InvldRslts_CauseTbl
Description
The values returned to cause analysis from the cause table are logically invalid.
Severity
Informational
Cause
Occurs when cause analysis successfully reads the cause table, but the value returned is logically invalid. Cause analysis gets two values from the cause table: an immediate result index and a location index. The immediate result index indicates that analysis should start reading results now, but the location index indicates that another table read is required to find the correct result table index. These results are logically incompatible and most likely result from a software failure or a corrupt cause table.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
ANAL: Cause_MdfyBFail_AnnounceID
Description
The cause analysis is unable to modify the B-number to include AnnounceID as the last 4 digits.
Severity
Informational
Cause
Occurs during cause analysis when an announcement result is encountered, and analysis is unable to replace the last 4 digits of the B-number with the announcement ID. This event is commonly caused by an out-of-range announcement ID (it should be 0 to 9999) or a B-number less than 4 digits long.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
ANAL: Cause_MdfyBFail_AppPtInvld
Description
The cause analysis is unable to perform a B-number modification.
Severity
Informational
Cause
Occurs during cause analysis when a B-number modification result is encountered, and the specified application point (where digits are inserted) is beyond the end of the digit string. This event is caused by an incorrect application point being specified in the result data, a corrupt result table, or incorrectly constructed cause analysis values.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
ANAL: Cause_Rte_Loop Detected
Description
The cause analysis has detected a routing loop.
Severity
Informational
Cause
Occurs during cause analysis when a route or announcement result is encountered. In these cases, the indicated route identifier is checked against a list of previously provided results. If a match is found, this alarm is raised and an error is returned to call processing. This is done to prevent calls from endlessly routing to a single route or series of routes infinitely due to cause analysis interactions.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
ANAL: CustID/StartIdx Missing
Description
The required property CustId or StartIdx is not present.
Severity
Informational
Cause
The property CustGrpId or BOrigStartIndex is not present on the originator. Both properties are required to find the correct place to begin analysis.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
ANAL: DataBaseAccessFail
Description
Access to the on-board database failed.
Severity
Minor
Cause
Access to the on-board database (for example, for screening) has failed. This alarm will be set any time there is a database access failure, regardless of the query being made.
SNMP Trap Type
3 (Processing error alarm)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
ANAL: Data Failure Rcvd
Description
Received ExtDataFailure from Routing Engine
Severity
Informational
Cause
The analysis module found a data failure in the external routing engine.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
ANAL: dpselection_table_fail
Description
Error reading the dial plan selection table.
Severity
Minor
Cause
The correct dial plan selection could not be determined.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
ANAL: getDialPlanBase_fail
Description
Failed to get dial plan.
Severity
Minor
Cause
The Cisco PGW 2200 Softswitch could not load or generate the dial plan.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
ANAL: InvalidtrkGrpType
Description
Invalid trunk group type.
Severity
Informational
Cause
The analysis module has not provided a valid trunk group type. The problem occurs if the route analysis table specifies an invalid trunk group type.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
ANAL: Prof_GetFail_CPCTbl
Description
Generic analysis was unable to read the calling party category (CPC) table.
Severity
Informational
Cause
This alarm is reported when generic analysis cannot access the CPC table.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
An internal processing error has occurred. Capture traces and provisioning data, and contact the Cisco TAC for assistance in resolving this problem.
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
ANAL: Prof_GetFail_DigModTbl
Description
Profile analysis is unable to read the digit modification string.
Severity
Informational
Cause
Occurs during profile analysis when a B-number modification result is encountered, and the digit modification string is unreadable. This event can be due to the digit modification table being corrupted or an incorrect digit modification index being stored in the B-number modification results data.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
ANAL: Prof_GetFail_InvldRslt
Description
Profile analysis encountered a result that is not valid during profile analysis.
Severity
Informational
Cause
Occurs during profile analysis when a result is encountered that is not supported in profile analysis. This event is due to corruption of either the NOA or NPI tables or the result table.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
ANAL: Prof_GetFail_NOATbl
Description
Profile analysis was unable to read the NOA table.
Severity
Informational
Cause
Occurs during profile analysis when the NOA table is unreadable. This event can be due to the NOA table being corrupted, a failure in the underlying software, or the NOA table being built without all the existing call context NOA values.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
ANAL: Prof_GetFail_NOATbl_A
Description
Profile analysis was unable to read the A-number NOAcg table.
Severity
Informational
Cause
This error occurs during Profile analysis when the NOAcg table is unreadable. This can be due either to the NOAcg table being corrupted, or to a failure in the underlying software.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
This alarm typically points to an internal processing error. Capture traces and provisioning data, contact your Cisco support representative and provide this information.
ANAL: Prof_GetFail_NPITbl
Description
Profile analysis was unable to read the NPI table.
Severity
Informational
Cause
Occurs during profile analysis when the NPI table is unreadable. This event can be due to the NPI table being corrupted, a failure in the underlying software, or the NPI table not being fully populated with all the possible references from the NOA table.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
ANAL: Prof_GetFail_NPITbl_A
Description
Profile analysis was unable to read the A-number NPIcg table.
Severity
Informational
Cause
This error occurs during Profile analysis when the NPIcg table is unreadable. This can be due either to the NPIcg table being corrupted, or to a failure in the underlying software.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
This alarm typically points to an internal processing error. Capture traces and provisioning data, contact your Cisco support representative and provide this information.
ANAL: Prof_GetFail_RsltTbl
Description
Profile analysis was unable to read the result table.
Severity
Informational
Cause
Occurs during profile analysis when the result table is unreadable. This event can be due to the result table being corrupted, a failure in the underlying software, or the result table not being fully populated with all the possible references from the NOA or NPI tables.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
ANAL: Prof_GetFail_TMRTbl
Description
Generic analysis is unable to read the transmission medium requirements (TMR) table.
Severity
Informational
Cause
This alarm is reported when generic analysis cannot access the TMR table.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
An internal processing error has occurred. Capture traces and provisioning data, and contact the Cisco TAC for assistance in resolving this problem.
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
ANAL: Prof_GetFail_TNSTbl
Description
Generic analysis is unable to read the calling transit network selection (TNS) table.
Severity
Informational
Cause
This alarm is reported when generic analysis cannot access the TNS table.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
An internal processing error has occurred. Capture traces and provisioning data, and contact the Cisco TAC for assistance in resolving this problem.
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
ANAL: Prof_InvldNPAValue
Description
Profile analysis encountered an invalid NPA value for the originating trunk group.
Severity
Informational
Cause
Occurs during profile analysis when a 7-digit B-number is encountered, and the NPA property is set against the originating trunk group. An NPA string of more or less than 3 characters is invalid. This event is most likely caused by data corruption.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
ANAL: Prof_InvRslts_NOATbl
Description
The values returned to profile analysis from the NOA table are logically invalid.
Severity
Informational
Cause
Occurs when profile analysis successfully reads the NOA table, but the value returned is logically invalid. Profile analysis gets two values from the NOA table: an immediate result index and an NPI index. An immediate result index indicates that analysis should start reading results now, but an NPI index indicates that another table read is required to find the correct result table index. These results are logically incompatible. Most likely this event results from a failure of the underlying software or a corruption of the NOA table.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
ANAL: Prof_InvRslts_NOATbl_A
Description
The values returned to profile analysis from the NOA table are logically invalid.
Severity
Informational
Cause
This error occurs when profile analysis successfully reads the NOAcg table but the value returned is logically invalid. Profile analysis gets two values from the NOAcg table—an immediate result index and an NPI index.
The immediate result index indicates that analysis should start reading results now but the NPI index indicates that another table read is required to find the correct result table index. These results are logically incompatible. Most likely, this alarm results from a failure of the underlying software or a corruption of the NOAcg table.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
This alarm typically points to an internal processing error. Capture traces and provisioning data, contact your Cisco support representative and provide this information.
ANAL: Prof_MdfyBFail_AppPtInvld
Description
Profile analysis was unable to perform a B-number modification.
Severity
Informational
Cause
Occurs during profile analysis when a B-number modification result is encountered, and the specified application point (where digits are inserted) is beyond the end of the digit string. This event is caused by an incorrect application point being specified in the result data, a corrupt result table, or incorrectly constructed Profile analysis values.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
ANAL: RedirectingNbrFail
Description
Redirecting number is being used during A-number tree analysis, and a result type other than Blacklist has been encountered.
Severity
Informational
Cause
Screening via the A digit tree has started with the redirecting number. Result type Blacklist is not configured, so A number analysis will continue using the calling number instead.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
No action is required. Processing will continue using the calling number. See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
ANAL: RteStartIndexInvalid
Description
Route start index invalid.
Severity
Informational
Cause
The start index for the route analysis table is invalid.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
ANAL: RteTableFail_GetRteList
Description
Route table file failed getting route list.
Severity
Informational
Cause
Access to the route list failed. The problem occurs if the index to the route list is not valid or if the route list is not loaded.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
ANAL: RteTableFail_GetTrkAttrdata
Description
Route table failed getting trunk attribute data.
Severity
Informational
Cause
Access to the trunk group attribute data table failed. The event occurs if the index to the trunk group attribute data table is not valid or if the table is not loaded.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
ANAL: RteTableFail_GetTrkGrpdata
Description
Route table failed getting trunk group data.
Severity
Informational
Cause
Access to the trunk group data failed. The event occurs if the index to the trunk group data is not valid or if the trunk group data table is not loaded.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
ANAL: RteTableFail_GetTrunkList
Description
Route table failed getting trunk list.
Severity
Informational
Cause
Access to the trunk group list failed. The problem occurs if the index to the trunk group list is not valid or if the trunk group list is not loaded.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
ANAL:Rte_TableHopCtrExceeded
Description
Generic analysis has encountered excessive analysis table hops.
Severity
Informational
Cause
This alarm is reported when the number of analysis table hops is exceeded during generic analysis.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
An internal processing error has occurred, or a routing loop has been introduced during provisioning. Capture traces and provisioning data, and contact the Cisco TAC for assistance in resolving this problem.
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
ANAL: SerialCountExceeded
Description
Serial triggering counter exceeded.
Severity
Informational
Cause
The number of serial IN triggers encountered for a call have exceeded the maximum allowed value. The call has been released, and there may be a loop in the local dial plan or remote SCP database.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
None required. This alarm is for informational purposes only.
ANAL:TableFail_BearerCapTable
Description
Generic analysis is unable to read the bearer capacity data table.
Severity
Informational
Cause
This alarm is reported when generic analysis cannot access the bearer capacity data table.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
An internal processing error has occurred. Capture traces and provisioning data, and contact the Cisco TAC for assistance in resolving this problem.
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
ANAL:TableFail_CondRouteDescTable
Description
Generic analysis is unable to read the conditional route description table.
Severity
Informational
Cause
This alarm is reported when generic analysis cannot access the conditional route description table.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
An internal processing error has occurred. Capture traces and provisioning data, and contact the Cisco TAC for assistance in resolving this problem.
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
ANAL: TableFail_CondRouteTable
DescriptionGeneric analysis was unable to read the conditional routing table.
SeverityInformational
CauseThis alarm is reported when the conditional routing table is not available during generic analysis.
SNMP Trap Type0 (Do not send an SNMP trap.)
ActionAn internal processing error has occurred. Rebuild the dial plan. Contact the Cisco TAC for assistance in resolving this problem.
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
ANAL:TableFail_PercRouteTable
Description
Generic analysis is unable to read the percentage route table.
Severity
Informational
Cause
This alarm is reported when generic analysis cannot access the percentage route table.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
An internal processing error has occurred. Capture traces and provisioning data, and contact the Cisco TAC for assistance in resolving this problem.
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
ANAL: TableFail_RouteHolTable
Description
Failure to read the route holiday table.
Severity
Informational
Cause
Generic analysis was unable to read the route holiday table.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
Capture traces and provisioning data to be forwarded to your Cisco support representative. See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
ANAL: TrunkGrpRsltCtrExceeded
Description
Trunk group result counter exceeded.
Severity
Informational
Cause
The analysis module has provided the maximum number of candidate trunk groups allowed (20).
The purpose of the alarm is to limit the time spent searching for candidate trunk groups.SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
ANAL: VPNid_GetFail_VPNidTbl
Description
The analysis module cannot read the VPNid table.
Severity
Informational
Cause
This alarm indicates that the analysis module failed to read the VPNid table.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
An internal processing error has occurred. Capture traces and provisioning data, and contact the Cisco TAC for assistance in resolving this problem.
Anumber Label is not found
Description
The location label of A number is not found in the location label table.
Severity
Informational
Cause
This alarm indicates the location label of A number is not defined in the location label table.
SNMP Trap Type
3 (Processing error alarm)
Action
Check the location label definition of the A number.
Association Fail (Release 9.4(1))
Description
The SCTP association has failed.
Severity
Major
Cause
This alarm is reported when the destination node is out of service or there is an IP connectivity failure.
SNMP Trap Type
1 (Communication alarm)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
Association Fail (Release 9.6(1))
Description
The SCTP association has failed.
Severity
Major
Cause
This alarm is reported when the destination node is out of service or there is an IP connectivity failure.
SNMP Trap Type
1 (Communication alarm)
Action
See Association Fail.
Association Degraded (Release 9.4(1))
Description
A destination address of the association has failed, and the association is still in an UP state.
Severity
Minor
Cause
This alarm is reported when one of the association destination addresses has failed.
SNMP Trap Type
1 (Communication alarm)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
Association Degraded (Release 9.6(1))
Description
A destination address of the association has failed, and the association is still in an UP state.
Severity
Minor
Cause
This alarm is reported when one of the association destination addresses has failed.
SNMP Trap Type
1 (Communication alarm)
Action
See Association Degraded.
Base license line missing in license files
Description
The base license line is missing in license files.
Severity
Major (service affecting)
Cause
This alarm could happen if the license file containing the base license has been removed.
SNMP Trap Type
3 (Processing error alarm)
Action
Check whether the license file that contains the base license line is at /opt/CiscoMGC/license. If it is not there, copy that license file to /opt/CiscoMGC/license.
Bnumber Label is not found
Description
The location label of B number is not found in the location label table.
Severity
Informational
Cause
This alarm indicates the location label of B number is not defined in the location label table.
SNMP Trap Type
3 (Processing error alarm)
Action
Check the location label definition of the B number.
C7DPC CONGESTION
Description
Destination point code is congested.
Severity
Major
Cause
The channel manager received a message indicating that the congestion level is greater than zero, or the channel controller has received an MTP3 TFC message.
SNMP Trap Type
1 (Communication alarm)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting the Cisco PGW 2200 Softswitch Node chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
C7LNK ALGNMT LOST
Description
C7 link alignment lost
Severity
Major
Cause
This alarm occurs when the MTP2 for the C7 link between a Cisco SLT and an associated APC has lost alignment.
SNMP Trap Type
1 (Communication alarm)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
C7LNK BLOCKED
Description
C7 link blocked
Severity
Major
Cause
An SS7 link is blocked from the remote end.
SNMP Trap Type
1 (Communication alarm)
Action
None required. This alarm is removed when the far end unblocks the MTP2 link.
C7LNK CONGESTION
Description
C7 link congestion.
Severity
Major
Cause
The SS7 MTP2 link has encountered congestion, and it cannot receive any more messages.
SNMP Trap Type
2 (Quality of service)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
C7LNK INHIBIT
Description
C7 link inhibit.
Severity
Major
Cause
The C7 link has been inhibited for maintenance.
SNMP Trap Type
1 (Communication alarm)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
C7LNK INHIBIT DENY
Description
C7 link inhibit deny.
Severity
Major
Cause
An SS7 link inhibit request has been denied. An inhibit request will be denied on critical links within a linkset.
SNMP Trap Type
1 (Communication alarm)
Action
None. This is an informational event
C7SLTLnkCong
Description
SS7 SLT link is congested.
Severity
Minor
Cause
Generated when an SS7 link on the SLT side becomes congested.
SNMP Trap Type
2 (Quality of service alarm)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
Call Back feature insertion failure
Description
A call back feature entry insertion in the main memory database fails.
Severity
Informational
Cause
This alarm occurs when an attempt to insert a call back feature entry in the main memory database fails. When this insertion fails, the call back feature does not work.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
The problem identified by this alarm can only be resolved by the Cisco TAC.
Call Back feature deletion failure
Description
A call back feature entry deletion from the main memory database fails.
Severity
Informational
Cause
This alarm occurs when an attempt to delete a call back feature entry from the main memory database fails. When this deletion fails, the call back feature does not work.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
The problem identified by this alarm can only be resolved by the Cisco TAC.
CAS: Leg1RQNTTimeOutError
Description
The originating leg fails to receive an acknowledgement to a notifyRequest message.
Severity
Major
Cause
The originating leg fails to receive an acknowledgement to a notifyRequest message.
SNMP Trap Type
1 (Communication alarm)
Action
Use packet sniffer tools to get network trace files on the Cisco PGW 2200 Softswitch or start the debug function on the gateway. Then contact Cisco TAC.
CAS: Leg2RQNTTimeOutError
Description
The terminating leg fails to receive an acknowledgement to a notifyRequest message.
Severity
Major
Cause
The terminating leg fails to receive an acknowledgement to a notifyRequest message.
SNMP Trap Type
1 (Communication alarm)
Action
Use packet sniffer tools to get network trace files on the Cisco PGW 2200 Softswitch or start the debug function on the gateway. Then contact Cisco TAC.
CHAN BAD TOT 15
Description
Signal channel TCA total frame errors—15 min.
Severity
Minor
Cause
The number of bad high-level data link control (HDLC) frames received on this channel (DS-0 time slot) has exceeded the threshold value set in the thresholds.dat table for the last 15-min. period. This alarm is generated if the value of the "SC: RCV BAD TOT" measurement counter exceeds the "upper" value of the 15 minutes (900 seconds) threshold.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
The alarm is cleared when the value of the "SC: RCV BAD TOT" measurement counter goes below the "lower" value of the 15 minutes threshold. The threshold values can be obtained by browsing the thresholds.dat file. This alarm is informational only and does not affect the normal working of an "in-service" link.
CHAN BAD TOT 24
Description
Channel TCA total frame errors—24 hours.
Severity
Minor
Cause
The number of bad HDLC frames received on this DS-0 time slot exceeded the threshold value set in the thresholds.dat file for the last 24-hour period. The channel remains in an in-service state. The value of the "SC: RCV BAD TOT" counter exceeds the "upper" value of the 24 hours (86400 seconds) threshold.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
The alarm is cleared when the value of the "SC: RCV BAD TOT" measurement counter goes below the "lower" value of the 24 hour threshold. The threshold values are set in the thresholds.dat file.
This event is informational only and does not require an immediate response; however, the condition should be monitored closely to ensure that the service level does not degrade further.
CHAN BAD TOT 60
Description
Channel TCA total frame errors—60 min.
Severity
Minor
Cause
The number of bad HDLC frames received on this DS-0 time slot exceeded the threshold value set in the thresholds.dat file for the last 60-minute period. The channel remains in an In-Service state. The value of the "SC: RCV BAD TOT" measurement counter exceeds the "upper" value of the 60 minute threshold.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
The alarm is cleared when the value of the "SC: RCV BAD TOT" measurement counter goes below the "lower" value of the 60 minutes threshold. The threshold values are set in the thresholds.dat file.
The high error rate indicated by this alarm does not prevent adequate transmission, but might indicate that the line or circuit is degrading and could result in transmission failure in the future. The only suggested action is to be alert for additional alarms.
CHAN LINK ESTAB 15
Description
Channel TCA link established—15 min.
Severity
Informational
Cause
The number of resets on this channel (DS-0) has exceeded the threshold value set in the thresholds.dat file for the last 15-minute period. The channel remains in an in-service state.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
This event is informational only and does not require an immediate response; however, the condition should be monitored closely to ensure that the service level does not degrade further.
CHAN LINK ESTAB 24
Description
Channel TCA link established—24 hours.
Severity
Informational
Cause
The number of resets on this channel (DS-0) has exceeded the threshold value set in the thresholds.dat file for the last 24-hour period. The channel remains in an in-service state.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
No immediate response is required; however, the condition should be monitored closely.
CHAN LINK ESTAB 60
Description
Channel TCA link established—60 min.
Severity
Informational
Cause
The number of resets on this channel (DS-0) has exceeded the threshold value set in the thresholds.dat file for the last 60-minute period. The channel remains in an in-service state.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
This event is informational only and does not require an immediate response; however, the condition should be monitored closely to ensure that the service level does not degrade further.
Charge Table Access Failure
Description
Failed to access the charge table.
Severity
Informational
Cause
The Cisco PGW 2200 Softswitch could not access the charge table.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
Charge Table Load Failure
Description
Failed to load the charge table.
Severity
Major
Cause
An Cisco PGW 2200 Softswitch process has been unable to load the charge table.
SNMP Trap Type
3 (Processing error alarm)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
Chkpt Synch Inprogress
Description
Active and standby synchronization is in progress.
Severity
Informational
Cause
Checkpointing is active, and the standby synchronization process is in progress.
SNMP Trap Type
3 (Processing error alarm)
Action
This event does not require an immediate response.
Comm Srvc Creation Error
Description
Failed to create communication service.
Severity
Minor
Cause
There has been an error creating or opening a communication service.
SNMP Trap Type
1 (Communication alarm)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
Configuration time port discrepancy period expired
Description
The discrepancy period expired. The license will be enforced at run time.
Severity
Informational
Cause
The allowed configuration time TDM port and SIP and H.323 call legs discrepancy period expired.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
None required. This alarm is for informational purposes only.
Config Fail
Description
Configuration has failed.
Severity
Informational
Cause
The configuration has failed. Generated when an RUDP session between the Cisco PGW 2200 Softswitch and the Cisco ITP-L goes out of service due to a fault configuration
SNMP Trap Type
3 (Processing error alarm)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
Conn Cntl Link Fail
DescriptionThe link that transporting connection control messages failed.
Severity
Minor
Cause
Generated when the MGCP session loses a heartbeat, indicating that the session is down.
SNMP Trap Type
1 (Communication alarm)
Action
Check if there is a network issue between the Cisco PGW 2200 Softswitch and the MGCP media gateway for the link in trouble. If not, check if the peer MGCP media gateway is reachable.
Conn Cntl Service Lost
DescriptionThe Cisco PGW 2200 Softswitch loses the ability to provide service for connection control.
Severity
Critical
Cause
Generated when the connection control ability was lost on Cisco PGW 2200 Softswitch.
SNMP Trap Type
1 (Communication alarm)
Action
Check if there is a network issue between the Cisco PGW 2200 Softswitch and the MGCP media gateway for the link in trouble. If not, check if the peer MGCP media gateway is reachable.
CPM: Leg1chanDeletedUnpackError
Description
Fault in data received from the engine.
Severity
Informational
Cause
Indicates an MDL source code issue.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
CPM: Leg1chanFailed
Description
Resource failure in the engine.
Severity
Informational
Cause
Indicates an MDL source code issue.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
No action is required. The Cisco TAC can use this information to troubleshoot call-processing problems.
CPM: Leg1chanModifiedUnpackError
Description
Fault in data received from the engine.
Severity
Informational
Cause
Indicates an MDL source code issue.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
No action is required. The Cisco TAC can use this information to troubleshoot call-processing problems.
CPM: Leg1chanOpFailed
Description
A resource failure in the engine.
Severity
Informational
Cause
Indicates an MDL source code issue.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
No action is required. The Cisco TAC can use this information to troubleshoot call-processing problems.
CPM: Leg1chanSeizedUnpackError
Description
Some fault in data received from the engine.
Severity
Informational
Cause
Indicates an MDL source code issue.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
No action is required. The Cisco TAC can use this information to troubleshoot call-processing problems.
CPM: Leg1ConfigError
Description
Inconsistent VirtualSwitch and oConPlaneCtrl.
Severity
Informational
Cause
Indicates an MDL source code issue.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
No action is required. The Cisco TAC can use this information to troubleshoot call-processing problems.
CPM: Leg1CotStateError
Description
Requested action is incompatible with CPM COT state.
Severity
Informational
Cause
Indicates an MDL source code issue.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
No action is required. The Cisco TAC can use this information to troubleshoot call-processing.
CPM: Leg1DeleteChanPackError
Description
Some required call context data was not available.
Severity
Informational
Cause
Indicates an MDL source code issue.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
No action is required. The Cisco TAC can use this information to troubleshoot call-processing problems.
CPM: Leg1ExtCOTPropError
Description
Prop is neither Loop nor Transponder.
Severity
Informational
Cause
Indicates an MDL source code issue.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
No action is required. The Cisco TAC can use this information to troubleshoot call-processing problems.
CPM: Leg1ModifyChanPackError
Description
Required call context data was not available.
Severity
Informational
Cause
Indicates an MDL source code issue.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
No action is required. The Cisco TAC can use this information to troubleshoot call-processing problems.
CPM: Leg1RMXmitCotError
Description
RMXmitCot returned false.
Severity
Informational
Cause
Indicates an MDL source code issue.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
No action is required. The Cisco TAC can use this information to troubleshoot call-processing problems.
CPM: Leg1RqntChanPackError
Description
A call-context variable is not available.
Severity
Informational
Cause
Indicates an MDL source code issue.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
No action is required. The Cisco TAC can use this information to troubleshoot call-processing problems.
CPM: Leg1SeizeChanPackError
Description
Some required call context data was not available.
Severity
Informational
Cause
Indicates an MDL source code issue.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
No action is required. The Cisco TAC can use this information to troubleshoot call-processing problems.
CPM: Leg1StateError
Description
Requested action is incompatible with CPM leg state.
Severity
Informational
Cause
Indicates an MDL source code issue.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
No action is required. The Cisco TAC can use this information to troubleshoot call-processing problems.
CPM: Leg1TestLineLoopError
Description
Test line loop back error.
Severity
Informational
Cause
Indicates an MDL source code issue.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
No action is required. The Cisco TAC can use this information to troubleshoot call-processing problems.
CPM: Leg1TestLineResourceError
Description
A brief description of the alarm or event.
Severity
Informational
Cause
Indicates an MDL source code issue.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
No action is required. The Cisco TAC can use this information to troubleshoot call-processing problems.
CPM: Leg1TestLineTableError
Description
Error reading the Test Line Table.
Severity
Informational
Cause
Indicates an MDL source code issue.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
No action is required. The Cisco TAC can use this information to troubleshoot call-processing problems.
CPM: Leg1TestLineToneError
Description
Test line tone error.
Severity
Informational
Cause
Indicates an MDL source code issue.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
No action is required. The Cisco TAC can use this information to troubleshoot call-processing problems.
CPM: Leg1Timeout
Description
No response received from the engine.
Severity
Informational
Cause
This event denotes an MDL source code issue.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
No action is required. The Cisco TAC can use this information to troubleshoot call-processing problems.
CPM: Leg2chanDeletedUnpackError
Description
Some fault in data received from the engine.
Severity
Informational
Cause
Indicates an MDL source code issue.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
No action is required. The Cisco TAC can use this information to troubleshoot call-processing problems.
CPM: Leg2chanFailed
Description
A resource failure in the engine.
Severity
Informational
Cause
Indicates an MDL source code issue.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
No action is required. The Cisco TAC can use this information to troubleshoot call-processing problems.
CPM: Leg2chanModifiedUnpackError
Description
Some fault in data received from the engine.
Severity
Informational
Cause
Indicates an MDL source code issue.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
No action is required. The Cisco TAC can use this information to troubleshoot call-processing problems.
CPM: Leg2chanOpFailed
Description
A resource failure in the engine.
Severity
Informational
Cause
Indicates an MDL source code issue.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
No action is required. The Cisco TAC can use this information to troubleshoot call-processing problems.
CPM: Leg2chanSeizedUnpackError
Description
Some fault in data received from the engine.
Severity
Informational
Cause
Indicates an MDL source code issue.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
No action is required. The Cisco TAC can use this information to troubleshoot call-processing problems.
CPM: Leg2ConfigError
Description
Inconsistent VirtualSwitch and tConPlaneCtrl.
Severity
Informational
Cause
Indicates an MDL source code issue.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
No action is required. The Cisco TAC can use this information to troubleshoot call-processing problems.
CPM: Leg2CotStateError
Description
Requested action is incompatible with CPM COT state.
Severity
Informational
Cause
Indicates an MDL source code issue.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
No action is required. The Cisco TAC can use this information to troubleshoot call-processing problems.
CPM: Leg2DeleteChanPackError
Description
Some required call context data was not available.
Severity
Informational
Cause
Indicates an MDL source code issue.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
No action is required. The Cisco TAC can use this information to troubleshoot call-processing problems.
CPM: Leg2ExtCOTPropError
Description
Prop is neither loop nor transponder.
Severity
Informational
Cause
Indicates an MDL source code issue.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
No action is required. The Cisco TAC can use this information to troubleshoot call-processing problems.
CPM: Leg2ModifyChanPackError
Description
Some required call context data was not available.
Severity
Informational
Cause
Indicates an MDL source code issue.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
No action is required. The Cisco TAC can use this information to troubleshoot call-processing problems.
CPM: Leg2RMXmitCotError
Description
RMXmitCot returned false.
Severity
Informational
Cause
Indicates an MDL source code issue.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
No action is required. The Cisco TAC can use this information to troubleshoot call-processing problems.
CPM: Leg2RqntChanPackError
Description
Required call context information is not available.
Severity
Informational
Cause
This alarms indicates that the required call context information is not available.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
Collect the MDL trace for the call for which the Cisco PGW 2200 Softswitch generates this alarm and then contact Cisco TAC.
CPM: Leg2SeizeChanPackError
Description
Some required call context data was not available.
Severity
Informational
Cause
Indicates an MDL source code issue.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
No action is required. The Cisco TAC can use this information to troubleshoot call-processing problems.
CPM: Leg2SeizeConnectionPackError
Description
Some required call context data was not available.
Severity
Informational
Cause
Indicates an MDL source code issue.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
No action is required. The Cisco TAC can use this information to troubleshoot call-processing problems.
CPM: Leg2StateError
Description
Requested action is incompatible with CPM leg state.
Severity
Informational
Cause
Indicates an MDL source code issue.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
No action is required. The Cisco TAC can use this information to troubleshoot call-processing problems.
CPM: Leg2Timeout
Description
No response received from the engine.
Severity
Informational
Cause
Indicates an MDL source code issue.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
No action is required. The Cisco TAC can use this information to troubleshoot call-processing problems.
CPM: NotifyUnexpected
Description
An unsolicited chanNotify has been received.
Severity
Informational
Cause
Indicates an MDL source code issue and is informational only.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
No action is required. The Cisco TAC can use this information to troubleshoot call-processing problems.
CPM: UnknownLeg
Description
LCM has requested action, not Leg1 or Leg2.
Severity
Informational
Cause
Indicates an MDL source code issue and is informational only.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
No action is required. The Cisco TAC can use this information to troubleshoot call-processing problems.
CPM: UnknownNotifyType
Description
ISDN User Part T28 has expired.
Severity
Informational
Cause
Indicates that a chanNotify message with unknown notify type has been received.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
No action is required. The Cisco TAC can use this information to troubleshoot call-processing problems.
Crash Information Collected
Description
A process core dumped and the core dump was saved.
Severity
Informational
Cause
Raised by ProcM when a process has core dumped and the core dump is saved. When a process exits and produces a core dump, this alarm indicates that the core file is saved for troubleshooting. The alarm will have an associated component ID identifying the process that produced the core dump.
SNMP Trap Type
3 (Processing error alarm)
Action
No action is required. The Cisco TAC can use this information to troubleshoot the problem.
CRITICAL M-OOS
Description
Critical process manually out of service.
Severity
Critical
Cause
Indicates that a software process critical to normal system operation has been requested manually out of service.
SNMP Trap Type
3 (Processing error alarm)
Action
Return the process to the in-service state.
CTI connection failed
Description
The CTI connection to the Cisco CallManager cluster has failed.
Severity
Major
Cause
This alarm occurs when the CTI connection to the Cisco CallManager cluster has failed.
SNMP Trap Type
1 (Communication alarm)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
CTI version mismatch
Description
The configured CTI Manager version on Cisco PGW 2200 Softswitch is not compatible with the version on the CTI Manager.
Severity
Minor
Cause
This alarm occurs when the CTI version of the CTI Manager component configured on Cisco PGW 2200 Softswitch is not compatible with the version on the CTI Manager.
SNMP Trap Type
1 (Communication alarm)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
Database Connection Failure
DescriptionFailed to establish the connection to the database.
SeverityInformational
Cause
This alarms indicates that the database connection is not established.
SNMP Trap Type
3 (Processing error alarm)
Action
Collect the database log and contact Cisco TAC for assistance.
Dial Plan Loading Failed
Description
Failed to load a dial plan.
Severity
Major
Cause
Indicates that a dial plan has not been loaded.
SNMP Trap Type
3 (Processing error alarm)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
DISK
Description
Low disk space.
Severity
Major
Cause
Indicates that the system disk is running out of space.
SNMP Trap Type
4 (Equipment error alarm)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
EISUP: Tunneled QSIG data received over a tunneling disabled interface
Description
The HSI is configured for tunneled QSIG but the Cisco PGW 2200 Softswitch interface is not.
Severity
Informational
Cause
This alarm is reported by EISUP when a tunneled QSIG message is received on an EISUP interface that is configured as tunneling disabled.
SNMP Trap Type
2 (Quality of service alarm).
Action
The craftsperson should verify that the data configuration consistency on the Cisco PGW 2200 Softswitch and HSIs.
EISUP: Unexpected Msg/Par
Description
The EISUP module has received an unsupported message or parameter.
Severity
Informational
Cause
This alarm occurs when the EISUP module has received an unsupported message or parameter.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
Engine Config Fail
Description
Engine configuration failed.
Severity
Major
Cause
Engine configuration failure.
SNMP Trap Type
3 (Equipment error alarm)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
EQPT M-OOS
Description
Equipment manually out of service.
Severity
Major
Cause
Indicates that a card or shelf has been requested manually out of service.
SNMP Trap Type
4 (Equipment error alarm)
Action
Restore the equipment to in-service state.
Ext Node Interface Fail
Description
SRCP link failure.
Severity
Major
Cause
Generated when an SRCP session loses heartbeats with the remote gateway, indicating that the link to the gateway is down.
SNMP Trap Type
1 (Communication alarm)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
Note
FAIL
Description
Non-specific failure.
Severity
Major
Cause
Indicates that the referenced component has failed. The failure may be service affecting, in which case other alarms will be raised.
SNMP Trap Type
3 (Processing error alarm)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
FailoverPeerLost
Description
Lost communication with failover peer.
Severity
Major
Cause
The peer failover daemon is not reachable.
SNMP Trap Type
3 (Processing error alarm)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
FailoverPeerOOS
Description
Failover peer is out of service.
Severity
Major
Cause
Raised when the peer failover daemon goes to out of service (OOS) state.
SNMP Trap Type
3 (Processing error alarm)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
FailoverToInit
Description
Failover daemon is in initializing state.
Severity
Informational
Cause
Indicates that a failover daemon is initializing.
SNMP Trap Type
3 (Processing error alarm)
Action
This is an informational alarm only. No action is required.
FailoverToMaster
Description
Failover daemon is in the active state.
Severity
Informational
Cause
Indicates that a failover daemon is in the active state.
SNMP Trap Type
3 (Processing error alarm)
Action
This is an informational alarm only. No action is required.
FailoverToOOS
Description
Failover daemon is out of service.
Severity
Major
Cause
A critical alarm has occurred in the system due to not receiving a response from the process manager or going to the OOS state.
SNMP Trap Type
3 (Processing error alarm)
Action
Contact the Cisco TAC for assistance in resolving this problem.
FailoverToSlave
Description
Failover daemon is in standby state.
Severity
Informational
Cause
Indicates that a failover daemon is in standby state.
SNMP Trap Type
3 (Processing error alarm)
Action
This is an informational alarm only. No action is required.
FAIL REMOTE STANDBY
Description
Failed to process a fault tolerance message with remote standby Cisco PGW 2200 Softswitch.
Severity
Minor
Cause
Generated when the standby Cisco PGW 2200 Softswitch fails to acknowledge synchronization messages from the active Cisco PGW 2200 Softswitch.
SNMP Trap Type
2 (Quality of service alarm)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
FORCE NODE RESTART
Description
Restart the standby node due to a new configuration.
Severity
Critical
Cause
Generated only on the standby node when a new IOCC is added dynamically. The standby node is restarted automatically; this alarm does not affect operations on the active node.
SNMP Trap Type
3 (Processing error alarm)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
Gateway Trunk Held
Description
Gateway Trunk held without associated call.
Severity
Informational
Cause
Indicates that a gateway trunk has been held even though there is no associated call.
SNMP Trap Type
3 (Processing error alarm)
Action
No action required. The application clears itself through an automatic audit.
Gen Fail
Description
General process failure or Session between the Cisco PGW 2200 Softswitch and Cisco ITP-L has failed.
Severity
Informational
Cause
There has been a failure caused by resource exhaustion or configuration problems, including:
•
•
•
•
•
•
SNMP Trap Type
3 (Processing error alarm)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
H323 call rejected due to wrong provision
Description
An H.323 call was rejected because the HSI EISUP interface is provisioned as an inter-Cisco PGW 2200 Softswitch EISUP interface.
Severity
Major
Cause
An H.323 call was rejected because it was incorrectly provisioned.
SNMP Trap Type
3 (Processing error alarm)
Action
Correct the HSI EISUP interface provision.
H323: FAIL ORIG 15
Description
Failed calls originating in H323 has exceeded the 15 minute threshold.
Severity
Minor
Cause
The number of failed calls originating in H323 has exceeded the "upper" threshold for a 15 minute (900 seconds) period.
SNMP Trap Type
2 (Quality of service alarm)
Action
None required. This alarm is for informational purposes only.
H323: FAIL ORIG 24
Description
Failed calls originating in H323 has exceeded the 24 hour threshold.
Severity
Minor
Cause
The number of failed calls originating in H323 has exceeded the "upper" threshold for a 24 hour period.
SNMP Trap Type
2 (Quality of service alarm)
Action
None required. This alarm is for informational purposes only.
H323: FAIL ORIG 60
Description
Failed calls originating in H323 has exceeded the 60 minute threshold.
Severity
Minor
Cause
The number of failed calls originating in H323 has exceeded the "upper" threshold for a 60 minute (3600 seconds) period.
SNMP Trap Type
2 (Quality of service alarm)
Action
None required. This alarm is for informational purposes only.
H323: FAIL TERM 15
Description
Failed calls terminating in H323 has exceeded the 15 minute threshold.
Severity
Minor
Cause
The number of failed calls terminating in H323 has exceeded the "upper" threshold for a 15 minute period.
SNMP Trap Type
2 (Quality of service alarm)
Action
None required. This alarm is for informational purposes only.
H323: FAIL TERM 24
Description
Failed calls terminating in H323 has exceeded the 24 hour threshold.
Severity
Minor
Cause
The number of failed calls terminating in H323 has exceeded the "upper" threshold for a 24 hour period.
SNMP Trap Type
2 (Quality of service alarm)
Action
None required. This alarm is for informational purposes only.
H323: FAIL TERM 60
Description
Failed calls terminating in H323 has exceeded the 60 minute threshold.
Severity
Minor
Cause
The number of failed calls terminating in H323 has exceeded the "upper" threshold for a 24 hour period.
SNMP Trap Type
2 (Quality of service alarm)
Action
None required. This alarm is for informational purposes only.
Holiday Table Access Failure
Description
Failed to access the charge holiday table.
Severity
Informational
Cause
The charge holiday table could not be accessed.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
Holiday Table Load Failure
Description
Failed to load holiday table.
Severity
Major
Cause
An Cisco PGW 2200 Softswitch process has been unable to load the holiday table.
SNMP Trap Type
3 (Processing error alarm)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
INVALID M3UA RC
Description
An invalid M3UA routing context was received from the Signaling Gateway. Indicates a mismatch between M3UA routing keys on the Cisco PGW 2200 Softswitch and the Signaling Gateway
Severity
Informational
Cause
Generated against a signaling gateway external node when an M3UA message is received from the signaling gateway with a routing context that has not been provisioned on the Cisco PGW 2200 Softswitch.
SNMP Trap Type
1 (Communication alarm)
Action
Compare the routing context of the M3UA routing keys on the Cisco PGW 2200 Softswitch and the Signaling Gateway and reprovision them to achieve a match.
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
INVALID SUA RC
Description
An invalid SUA routing context was received from the Signaling Gateway.
Severity
Informational
Cause
There is a mismatch between SUA routing keys on the Cisco PGW 2200 Softswitch and the Signaling Gateway.
SNMP Trap Type
1 (Communication alarm)
Action
Compare the routing context of the SUA routing keys on the Cisco PGW 2200 Softswitch and the Signaling Gateway and reprovision them to achieve a match.
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
Invalid Virtual Address
Description
The Virtual_IP_Addr1 configured doesn't belong to either the IP_Addr1 or IP_Addr2 network.
Severity
Major
Cause
This alarm is reported when the virtual_IP_Addr1 configuration is incorrect.
SNMP Trap Type
3 (Processing error).
Action
Configure the Virtual_IP_Addr1 as part of either the IP_Addr1 or IP_Addr2 network. See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
locLabelNotFound
This alarm is raised at any point in the call if the a collected location label is missing from the internal location label table. This could point to a label being removed while still being assigned in analysis or at the trunk group or SigPath level. Logs are also raised to indicate the labels involved.
Description
The location label was not found in the internal table.
Severity
Informational
Cause
This alarm can occur when the Cisco PGW 2200 Softswitch reads its internal label to check or update counters for a label. If the label is not found, this alarm is generated.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
This typically points to a provisioning error where a label has been removed, but references to it are not removed from Analysis, the trunk group, or SigPath. Check provisioning for the presence of the label concerned.
locTableAcessFail
This alarm is raised at any point in the call if the engine cannot access the local location label table to make a call limiting request or to decrement counters. It is a sign of possible counter corruption, and the system user needs to be made aware of the situation. Logs are also raised to indicate the labels involved.
Description
The Cisco PGW 2200 Softswitch failed to access the location label table.
Severity
Informational
Cause
This alarm is reported when the Cisco PGW 2200 Softswitch is trying to access its internal location label table to make a call limiting check or to update active call counters. If it indicates a failure in executing the counter decrement for one or more labels, associated logs identify the labels involved. Failure to carry out this counter decrement could later lead to false rejection of calls and possible traffic handling problems.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
This typically points to an internal processing error. Capture traces and engine logs where possible, and forward them to your Cisco support representative. If an urgent traffic handling situation occurs, with constant call limiting rejections, the Call Limiting feature can be disabled so service can be restored.
IP_Add1 Mismatch
Description
IP_Addr1 and ipAddrLocalA are different or invalid in the configuration.
Severity
Major
Cause
IP_Addr1 and ipAddrLocalA are different or invalid in the configuration.
SNMP Trap Type1 (Communication alarm)
ActionCheck the configuration of IP_Add1 and ipAddrLocalA in XECfgparm.dat. The IP addresses configured for these two parameters must be same. The IP address value must be valid.
IP_Add2 Mismatch
Description
IP_Addr2 and ipAddrLocalB are different or invalid in the configuration.
Severity
Major
Cause
IP_Addr2 and ipAddrLocalB are different or invalid in the configuration.
SNMP Trap Type1 (Communication alarm)
ActionCheck the configuration of IP_Add2 and ipAddrLocalB in XECfgparm.dat. The IP addresses configured for these two parameters must be same. The IP address value must be valid.
IP CONNECTION FAILED
Description
IP connection to the Cisco Signaling Link Terminal (SLT) failed.
Severity
Major
Cause
Triggered when the Cisco PGW 2200 Softswitch loses network (IP) connectivity to a Cisco SLT device. The alarm is triggered on each SS7 link (signal channel) supported by the Cisco SLT. At the same time, the SS7 links will generate A-OOS state alarms. When the alarm is generated, it indicates the component ID of a signaling channel (SS7 link) that has gone A-OOS because of the loss of IP connectivity.The most likely causes of this alarm are:
•
•
•
•
•
SNMP Trap Type
1 (Communication alarm)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
IP RTE CONF FAIL (Release 9.4(1))
Description
IP route is out of service due to a configuration failure.
Severity
Informational
Cause
Indicates that an IP route is out of service because of a configuration failure.
Starting with Cisco PGW 2200 Softswitch software release 9.4(1), this alarm is now generated against IP route components instead of signal channel components.SNMP Trap Type
1 (Communication alarm)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
IP RTE CONF FAIL (Release 9.6(1))
Description
IP route is out of service due to a configuration failure.
Severity
Minor
Cause
This existing alarm is now generated against the IP route components instead of against signal channel components Indicates that an IP route is out of service because of a configuration failure.
SNMP Trap Type
1 (Communication alarm)
Action
See IP RTE CONF FAIL.
IP RTE FAIL (Release 9.4(1))
Description
IP route is out of service.
Severity
Informational
Cause
Indicates that an IP route is out of service.
Starting with Cisco PGW 2200 Softswitch software release 9.4(1), this alarm is now generated against IP route components instead of signal channel components.SNMP Trap Type
1 (Communication alarm)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
IP RTE FAIL (Release 9.6(1))
Description
IP route is out of service. This existing alarm is now generated by IP route objects instead of by the signal channel components.
Severity
Minor
Cause
Indicates that an IP route is out of service.
SNMP Trap Type
1 (Communication alarm)
Action
See IP RTE FAIL.
ISUP: ABNORM CGBA
Description
Severity
Informational
Cause
The range and status received in a CGBA message do not match the range and status sent in the circuit group blocking (CGB) message.
SNMP Trap Type
1 (Communication alarm)
Action
For more information, see the appropriate specification for the protocol concerned.
ISUP: ABNORM CGUA
Description
ISDN User Part circuit group unblocking acknowledgment (CGUA) received with nonmatching range or status.
Severity
Informational
Cause
The range and status received in a CGUA message do not match the range and status sent in the circuit group unblocking (CGU) message.
SNMP Trap Type
1 (Communication alarm)
Action
For more information, see the appropriate specification for the protocol concerned.
ISUP: ABNORM CQR
Description
ISDN User Part CQR received with nonmatching CQM range.
Severity
Informational
Cause
The range and status received in a CQR message do not match the range and status sent in the CQM.
SNMP Trap Type
1 (Communication alarm)
Action
For more information, see the appropriate specification for the protocol concerned.
ISUP: CGB Processed
Description
Indicates a CGB request has been processed from far-end.
Severity
Informational
Cause
Indicates that the far-end switch has blocked a range of CICs. The alarms for receiving CGB from the far end are supported in ANSI and Q767. This is not supported for all protocols.
SNMP Trap Type
1 (Communication alarm)
Action
No action required. For more information, see the appropriate specification for the protocol concerned.
ISUP: CGU Processed
Description
Indicates a CGU request has been processed from far-end.
Severity
Informational
Cause
Indicates that the far-end switch has unblocked a range of CICs. The alarms for receiving CGU from the far end are supported in ANSI and Q767. This is not supported for all protocols.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
No action required. For more information, see the appropriate specification for the protocol concerned.
ISUP: COT FAILURE
Description
ISDN User Part initial and subsequent COT failed.
Severity
Informational
Cause
Occurs when a COT message was received indicating a failed continuity test.
SNMP Trap Type
1 (Communication alarm)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
ISUP: CQR UNEQUIPPED CIC
Description
The far end is unequipped.
Severity
Informational
Cause
Generated when the far end is unequipped.
SNMP Trap Type
1 (Communication alarm)
ActionEquip the CIC in the far end.
ISUP: Error Indication CRGA
Description
An error indication was received in a CRGA message.
Severity
Informational
Cause
Signifies that an error has been indicated in a CRGA (Charging Acknowledgement Information) message received by the ingress protocol in response to the sending of a CRGT (Charging Tariff Information) message
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
No action required, as this is an informational message only.
ISUP: FE Parameter Drop
Description
ISDN User Part incoming FE parameter dropped.
Severity
Informational
Cause
An incoming FE in a backward message has been dropped according to the terminating message map (rule 1).
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
For more information, see the appropriate specification for the protocol concerned.
ISUP: T13 Expired
Description
ISDN User Part T13 has expired.
Severity
Informational
Cause
Raised when a blocking message has been sent and the T13 timer has expired because no blocking acknowledgment message was received in response.
SNMP Trap Type
1 (Communication alarm)
Action
For more information, see the appropriate specification for the protocol concerned.
ISUP: T15 Expired
Description
ISDN User Part T15 has expired.
Severity
Informational
Cause
Raised when an unblocking message has been sent and the T15 timer has expired because no unblocking acknowledgment message was received in response.
SNMP Trap Type
1 (Communication alarm)
Action
For more information, see the appropriate specification for the protocol concerned.
ISUP: T17 Expired
Description
ISDN User Part T17 has expired.
Severity
Informational
Cause
Raised when a reset unavailable message has been sent, and the T17 timer has expired because no acknowledgment message was received in response.
SNMP Trap Type
1 (Communication alarm)
Action
For more information, see the appropriate specification for the protocol concerned.
ISUP: T18 Expired
Description
ISDN User Part T18 has expired.
Severity
Informational
Cause
Raised when a group blocking message has been sent, and the T18 timer has expired because no acknowledgment message was received in response.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
For more information, see the appropriate specification for the protocol concerned.
ISUP: T19 Expired
Description
ISDN User Part T19 has expired.
Severity
Informational
Cause
Raised when a group blocking message has been sent, and the T19 timer has expired because no group blocking acknowledgment message was received in response.
SNMP Trap Type
1 (Communication alarm)
Action
For more information, see the appropriate specification for the protocol concerned.
ISUP: T21 Expired
Description
ISDN User Part T21 has expired.
Severity
Informational
Cause
Raised when a group unblocking message has been sent and the T21 timer has expired because no group unblocking acknowledgment message was received in response.
SNMP Trap Type
1 (Communication alarm)
Action
For more information, see the appropriate specification for the protocol concerned.
ISUP: T23 Expired
Description
ISDN User Part T23 has expired.
Severity
Informational
Cause
Raised when a group reset message has been sent, and the T23 timer has expired because no acknowledgment message was received in response.
SNMP Trap Type
1 (Communication alarm)
Action
For more information, see the appropriate specification for the protocol concerned.
ISUP: T28 Expired
Description
ISDN User Part T28 has expired.
Severity
Informational
Cause
Raised when a circuit query message has been sent, and T28 expires because no circuit query response message was received in response.
SNMP Trap Type
1 (Communication alarm)
Action
For more information, see the appropriate specification for the protocol concerned.
ISUP: T33 Expired
Description
ISDN User Part T33 has expired.
Severity
Informational
Cause
This alarm indicates that the Cisco PGW 2200 Softswitch has not received the INF message after it sends an INR message.
SNMP Trap Type
1 (Communication alarm)
Action
For more information, see the appropriate specification for the protocol concerned.
ISUP: T34 Expired
Description
ISDN User Part T34 has expired.
Severity
Informational
Cause
This alarm indicates that the Cisco PGW 2200 Softswitch has not received a segmentation message.
SNMP Trap Type
1 (Communication alarm)
Action
For more information, see the appropriate specification for the protocol concerned.
ISUP: T4 Expired
Description
The ISUP T4 timer has expired
Severity
Informational
Cause
When MTP STATUS primitive with cause "remote user unavailable" is received, UPT message is sent and T4 timer is started. When T4 timer expires UPT message is sent and T4 timer is started again. Alarm is generated every time T4 expires.
If UPT is requested by MML, UPT message is sent and T4 timer is started. When timer expires UPT message is sent again and T4 timer is started second time. When T4 timer expires a second time alarm is generated and UPT message is not sent anymore.
SNMP Trap Type
0
Action
No action required
ISUP: T5 Expired
Description
ISDN User Part T5 has expired.
Severity
Informational
Cause
Raised when a release message has been sent and the T5 timer has expired because no release complete message was received in response.
SNMP Trap Type
1 (Communication alarm)
Action
For more information, see the appropriate specification for the protocol concerned.
ISUP: TCVT Expired
Description
ISDN User Part CVT timer expired twice.
Severity
Informational
Cause
When a circuit validation test (CVT) message is sent out, a timer named T_CVT starts. If a circuit validation response message is not received, the timer expires and a second CVT message is sent. The timer is started again. If the timer expires a second time, the alarm is be raised.
SNMP Trap Type
1 (Communication alarm)
Action
For more information, see the appropriate specification for the protocol concerned.
ISUP: UNEQUIPPED CIC
Description
ISDN User Part message received on unequipped CIC.
Severity
Informational
Cause
Raised when a message is received on an unequipped circuit identification code (CIC).
SNMP Trap Type
1 (Communication alarm)
Action
For more information, see the appropriate specification for the protocol concerned.
ISUP: UNEX ACM
Description
ISDN User Part unexpected ACM.
Severity
Informational
Cause
Raised when an ACM message has been received and an ACM/ANM message has already been sent.
SNMP Trap Type
1 (Communication alarm)
Action
For more information, see the appropriate specification for the protocol concerned.
ISUP: UNEX ANM
Description
ISDN User Part unexpected ANM.
Severity
Informational
Cause
Raised when an ANM message has been received and an ACM/ANM message has already been sent.
SNMP Trap Type
1 (Communication alarm)
Action
For more information, see the appropriate specification for the protocol concerned.
ISUP: UNEX BLA
Description
ISDN User Part BLA received with local status unblocked.
Severity
Informational
Cause
Raised when a BLA message has been received and the local status is unblocked.
SNMP Trap Type
1 (Communication alarm)
Action
For more information, see the appropriate specification for the protocol concerned.
ISUP: UNEX CGBA
Description
ISDN User Part CGBA received with local status blocked.
Severity
Informational
Cause
Raised when a CBGA message is received and local status is already unblocked.
SNMP Trap Type
1 (Communication alarm)
Action
For more information, see the appropriate specification for the protocol concerned.
ISUP: UNEX CGUA
Description
ISDN User Part CGUA received with local status unblocked.
Severity
Informational
Cause
Raised when a CGUA message has been received and local status is blocked.
SNMP Trap Type
1 (Communication alarm)
Action
For more information, see the appropriate specification for the protocol concerned.
ISUP: UNEX UBA
Description
ISDN User Part UBA received with local status unblocked.
Severity
Informational
Cause
Raised when a UBA message has been received and the local status is blocked.
SNMP Trap Type
1 (Communication alarm)
Action
For more information, see the appropriate specification for the protocol concerned.
ISUP: UNMATCHED STATUS
Description
Circuit Grp Blocking (Unblocking) Ack status unmatched.
Severity
Informational
Cause
Raised when the circuit group blocking/ unblocking and Acknowledgement status are not matching.
SNMP Trap Type
1 (Communication alarm)
Action
For more information, see the appropriate specification for the protocol concerned.
Kill Call
Description
The kill-call MML command has been manually issued.
Severity
Informational
Cause
An operator has manually entered this command to force the disconnection of a hung or dangling call.
SNMP Trap Type
1 (Communication alarm)
Action
This alarm is generated for informational purposes only; no action is required.
LCM: Ta3ExpiryACR
Description
Ta3 timer has expired while waiting for a response to an ApplyChargingReport operation.
Severity
Informational
Cause
This alarm is reported by the LCM when no response has been received from the SCF to an ApplyChargingReport operation during the processing of an IN prepaid service call.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
No action is required. The call will be released and there is no further communication with the SCF.
LCM: Ta3ExpiryERBCSM
Description
Ta3 timer has expired while waiting for a response to an EventReportBCSM operation.
Severity
Informational
Cause
This alarm is reported when no response has been received from the SCF to an EventReportBCSM operation during the processing of an IN prepaid service call.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
No action is required. The call will be released and there is no further communication with the SCF.
LCM: Ta3ExpiryIDP
Description
Ta3 timer has expired while waiting for a response to the InitialDP operation.
Severity
Informational
Cause
This alarm is reported by the LCM when no response has been received from the SCF to an InitialDP operation during the processing of an IN prepaid service call.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
No action is required. The call will be released and there is no further communication with the SCF.
LCM: Invalid destination for RO/PR routing number
Description
This alarm occurs when the RO request routing number does not translate to a DPNSS trunk group.
Severity
Informational
Cause
This alarm is reported by UCM when a RO or PR routing number fails to be translated by generic analysis into a destination that enables the feature to be performed.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
To correct the problem identified by this alarm, you should verify that the dial plans associated with the DPNSS incoming trunk group match up with the routing numbers in the PBX network.
If the dial plans are correct, contact the Cisco TAC to further analyze the problem and determine a solution.
LCM: No Response from Call Instance
Description
This alarm occurs when LCM has not received a message response within the expected time period from another related call.
Severity
Informational
Cause
This alarm is reported by LCM when a keep-alive message or some other call processing message has not received a response from another related call.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
The problem identified by this alarm can only be resolved by the Cisco TAC.
LCM: Take back and transfer, Invalid target for DTMF collection
Description
The request to collect midcall DTMF events cannot be performed because the target user has an incompatible protocol such as H.323.
Severity
Informational
Cause
This alarm is reported by LCM when the ICM erroneously requests the Cisco PGW 2200 Softswitch for midcall event reporting against an H.323 user.
SNMP Trap Type
2 (Quality of service alarm)
Action
Verify that the data provisioned in the Cisco PGW 2200 Softswitch and ICM is consistent with the configured agent interfaces.
License server unreachable
Description
This alarm appears if the license server is unavailable. The Cisco PGW 2200 Softswitch looks at the local license files to retrieve the configuration time TDM ports/ the run time license information. At the same time, a timer is started.
If the license server is still unreachable after 1 week, the license number will be half of the license number in license files.
If the license server is still unreachable after 8 weeks, the license number will be demo license number.
Severity
Major (service affecting)
Cause
The LMAgent reports that the TCP connection to the license server is lost. The license server might be down, or there might be something wrong with the network connection to the license server.
SNMP Trap Type
1 (Communication alarm)
Action
Verify that the network connection to the license server is up and ensure that the license server is running. For troubleshooting instructions, see the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
License server unreachable for more than a week
Description
The license server has been unreachable for more than a week. The license period is cut down by half.
Severity
Major (service affecting)
Cause
The LMAgent reports that the TCP connection to the license server is lost. The license server might be down, or there might be something wrong with the network connection to the license server.
SNMP Trap Type
3 (Processing error alarm)
Action
Verify that the network connection to the license server is up and ensure that the license server is running.
License server unreachable for more than 8 weeks
Description
The license server has been unreachable for more than 8 week. Now Cisco PGW 2200 Softswitch is using the demo license.
Severity
Major (service affecting)
Cause
The LMAgent reports that the TCP connection to the license server is lost. The license server might be down, or there might be something wrong with the network connection to the license server.
SNMP Trap Type
3 (Processing error alarm)
Action
Verify that the network connection to the license server is up and ensure that the license server is running.
License to expire in a week or less
Description
The license will expire in a week or less.
Severity
Major (service affecting)
Cause
The given License will expire in a week or less.
SNMP Trap Type
Processing error alarm.
Action
Contact the account team for a formal license.
LIF FAIL (Release 9.4(1))
Description
Line interface failure.
Severity
Major
Cause
The line interface (LIF) has failed. All physical lines to the Cisco PGW 2200 Softswitch can raise this alarm.
Starting with Cisco PGW 2200 Softswitch software release 9.4(1), this alarm is now generated against local interface components. All physical lines to the Cisco PGW 2200 Softswitch and local interface components can raise this alarm.SNMP Trap Type
4 (Equipment error alarm)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
LIF FAIL (Release 9.6(1))
Description
Line interface failure.
Severity
Major
Cause
This existing alarm is now generated against local interface components. The line interface (LIF) has failed. All physical lines to the Cisco PGW 2200 Softswitch and local interface components can raise this alarm.
SNMP Trap Type
4 (Equipment error alarm)
Action
See LIF FAIL.
Location-FAILURE
Description
Location failed when there is a fault and the Cisco PGW 2200 Softswitch brought offline.
Severity
Major
Cause
Location failed when there is a fault and the Cisco PGW 2200 Softswitch brought offline.
SNMP Trap Type
4 (Equipment error alarm)
Action
Contact the Cisco TAC for assistance in resolving this problem.
Location-DEGRADE
Description
A fault is detected on an FRU. The Cisco PGW 2200 Softswitch is not brought offline.
Severity
Major
Cause
A fault is detected on an FRU.
SNMP Trap Type
4 (Equipment error alarm)
Action
Contact the Cisco TAC for assistance in resolving this problem.
Location-INSERTED
Description
A FRU is inserted onto the platform.
Severity
Minor
Cause
A FRU is inserted onto the platform.
SNMP Trap Type
4 (Equipment error alarm)
Action
Contact the Cisco TAC for assistance in resolving this problem.
Location-CONFIGURE-FAILED
Description
CMS failed to bring FRU online.
Severity
Major
Cause
Location configuration failed.
SNMP Trap Type
4 (Equipment error alarm)
Action
Contact the Cisco TAC for assistance in resolving this problem.
LOG
DescriptionThe Cisco PGW 2200 Softswitch failed to open or write the log file.
SeverityMajor
CauseAn error occurred when the Cisco PGW 2200 Softswitch tried to open or write the log file.
SNMP Trap Type3 (Processing error alarm)
ActionCheck the platform log to identify this error.
Lost connectivity to all RADIUS servers
Description
All RADIUS servers are unreachable after several retry actions.
Severity
Major (service affecting)
Cause
All RADIUS servers are unreachable after trying several times.
SNMP Trap Type
Communication alarm.
Action
Check network traffic and get RADIUS servers up. Log in to the Cisco PGW 2200 Softswitch to copy RADIUS files and delete them.
M3UAKEY Ack Pending
Description
An acknowledgement for an M3UAKEY associated with this SS7PATH or SG has not been received
Severity
Minor
Cause
The Cisco PGW 2200 Softswitch cannot send or receive traffic for the SS7PATH via the SG that has not acknowledged the M3UAKEY
SNMP Trap Type
1
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
M-OOS (Release 9.4(1))
Description
Resource has been manually taken out of service.
Severity
Minor
Cause
A software process not necessary for normal system operation has been requested manually out of service.
Starting with Cisco PGW 2200 Softswitch software release 9.4(1), this alarm is now generated against IP route components.SNMP Trap Type
1 (Communication alarm)
Action
Restore the process to the in-service state using the user interface.
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.M-OOS (Release 9.6(1))
Description
Resource has been manually taken OOS.
Severity
Minor
Cause
A software process not necessary for normal system operation has been manually requested OOS. This existing alarm is now generated against IP route components.
SNMP Trap Type
1 (Communication alarm)
Action
Restore the process to the in-service state using the user interface. IP routes can be returned to service by using the procedure in Changing the Service State of an IP Route.
MAJOR M-OOS
Description
Required process manually out of service.
Severity
Major
Cause
A software process necessary for normal system operation has been requested manually out of service.
SNMP Trap Type
3 (Processing error alarm)
Action
Restore the process to the in-service state using the user interface.
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.Manual Switch Over
Description
A user has initiated a manual switchover.
Severity
Critical
Cause
A user has issued an MML command to switch over the Cisco PGW 2200 Softswitch. This event will happen on the active system only.
SNMP Trap Type
3 (Processing error alarm)
Action
No action is necessary. The alarm clears once the switchover has completed.
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.Master PGW is Active
Description
The master Cisco PGW 2200 Softswitch is taking the active role.
Severity
Minor
Cause
This alarm indicates that the master Cisco PGW 2200 Softswitch is taking the active role. This alarm is not generated if *.AlarmOnActive is set to false in XECfgParm.dat.
SNMP Trap Type
2 (Quality of service alarm)
Action
None required. This alarm is for informational purposes only.
MDL BLKLST 15
Description
15-minute blacklist threshold exceeded.
Severity
Minor
Cause
More than ten calls have been blacklisted within fifteen minutes.
SNMP Trap Type
3 (Processing error alarm)
Action
The alarm will clear automatically when the number of blacklisted calls drops below eight. Be alert for a potential hacker into the system.
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.MDL BLKLST 24
Description
24-hour blacklist threshold exceeded.
Severity
Minor
Cause
More than 200 calls have been blacklisted within 24 hours.
SNMP Trap Type
3(Processing error alarm)
Action
The alarm will clear automatically when the number of blacklisted calls drops below 160. Be alert for a potential hacker into the system.
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.MDL BLKLST 60
Description
60-minute blacklist threshold exceeded.
Severity
Minor
Cause
More than 30 calls have been blacklisted within 60 minutes.
SNMP Trap Type
3 (Processing error alarm)
Action
The alarm will clear automatically when the number of blacklisted calls drops below 24. Be alert for a potential hacker into the system.
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.MeterPulseTariff Table Load Failure
Description
Failed to load the meter pulse tariff table.
Severity
Major
Cause
This alarm indicates that Cisco PGW 2200 Softswitch failed to load the meter pulse tariff table.
SNMP Trap Type
3 (Processing error alarm)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
MINOR M-OOS
Description
Non-required process manually out of service.
Severity
Minor
Cause
A software process that is not necessary for normal system operation has been requested manually out of service.
SNMP Trap Type
3 (Processing error alarm)
Action
The alarm will clear when the process is restored in service.
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.MMDB: Database nearly full
Description
Main memory database is nearly full.
Severity
Major
Cause
The main memory database has detected that allocated resources for data storage are nearly all utilized.
SNMP Trap Type
3 (Processing error alarm)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
MMDB: Database temporary memory is nearly full (Release 9.8(1)
Description
Database temporary memory is nearly full.
Severity
Major (service affecting)
Cause
This alarm is reported when database temporary memory is nearly full.
SNMP Trap Type
Processing error alarm
Action
Expand memory or reduce database size.
MMDB: Database unavailable
Description
Main memory database is unavailable.
Severity
Major
Cause
The main memory database is currently unavailable to provide any services. Recovery is attempted, and the alarm clears when or if the database becomes available.
SNMP Trap Type
3 (Processing error alarm)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
More TDM ports configured than entitled
Description
There are more TDM ports configured than are entitled.
Severity
Major (service affecting)
Cause
This alarm is reported because there are more TDM ports configured than are entitled.
SNMP Trap Type
3 (Processing error alarm)
Action
First verify that the license files are in the right place. If they are, then either contact the account team to order more TDM port licenses or remove the over-configured TDM ports. If they are not, move the license files to the right place.
NAS: AuditResponseFailure
Description
The media gateway (MGW) failed to send RESYNC RESP back to the Cisco PGW 2200 Softswitch within the audit time interval.
Severity
Informational
Cause
The Cisco media gateway failed to send RESYNC RESP back to the Cisco PGW 2200 Softswitch within the audit time interval.
SNMP Trap Type
3 (Processing error alarm)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
NAS: CommsFailure
Description
MGW communication failure.
Severity
Informational
Cause
The Cisco PGW 2200 Softswitch cannot communicate with the media gateway. The media gateway failed to acknowledge a message within 2 seconds.
SNMP Trap Type
1 (Communication alarm)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
NAS: ResourceFailure
Description
Received "not acknowledged" message from the media gateway.
Severity
Informational
Cause
Continuity has not been acknowledged by the media gateway.
SNMP Trap Type
3 (Processing error alarm)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
Normal call rejected due to database oversubscription and restricted access to database (Release 9.8(1)
Description
Non-emergency call will be rejected due to database oversubscription and restricted access to database.
Severity
Major (service affecting)
Cause
This alarm is reported when a call is rejected on percentage when the number of TimesTen entries exceeds the amount that the purchased TimesTen license allows.
SNMP Trap Type
Processing error alarm
Action
Contact the account team to purchase additional TimesTen license.
Normal call rejected due to oversubscription
Description
A non emergency call was rejected due to oversubscription.
Severity
Major (service affecting)
Cause
The number of active call legs exceeded the allowed oversubscription ratio.
SNMP Trap Type
Processing error alarm.
Action
Contact the account team to purchase additional licenses.
Number of remaining Database RTU license reach 5% of the purchased RTU (Release 9.8(1))
Description
Only 5 percent of the purchased Database RTU licenses remain.
Severity
Informational (non-service affecting)
Cause
The LMAgent reports that you have used more than 95 percent of the purchased Database RTU licenses.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
Contact the account team to purchase additional licenses.
Note
Number of remaining Database RTU license reach 10% of the purchased RTU (Release 9.8(1))
Description
Only 10 percent of the purchased Database RTU licenses remain.
Severity
Informational (non-service affecting)
Cause
The LMAgent reports that you have used more than 90 percent of the purchased Database RTU licenses.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
Contact the account team to purchase additional licenses.
Note
Number of remaining Database RTU licenses reach 25% of the purchased RTU (Release 9.8(1))
Description
Only 25 percent of the purchased Database RTU licenses remain.
Severity
Informational (non-service affecting)
Cause
The LMAgent reports that you have used more than 75 percent of the purchased Database RTU licenses.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
Contact the account team to purchase additional licenses.
Note
Number of remaining RTU licenses reach 5% of the purchased RTU
Description
Only 5 percent of the purchased RTU licenses remain.
Severity
Informational (non-service affecting)
Cause
The LMAgent reports that you have used more than 95 percent of the purchased RTU licenses.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
Contact the account team to purchase additional licenses.
Number of remaining RTU licenses reach 10% of the purchased RTU
Description
Only 10 percent of the purchased RTU licenses remain.
Severity
Informational (non-service affecting)
Cause
The LMAgent reports that you have used more than 90 percent of the purchased RTU licenses.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
Contact the account team to purchase additional licenses.
Number of remaining RTU licenses reach 25% of the purchased RTU
Description
Only 25 percent of the purchased RTU licenses remain.
Severity
Informational (non-service affecting)
Cause
The LMAgent reports that you have used more than 75 percent of the purchased RTU licenses.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
Contact the account team to purchase additional licenses.
Number of TCP connections reach limitation
Description
The number of TCP connections reaches limitation.
Severity
Major
Cause
This alarm indicates that the number of SIP TCP connections reaches limitation which is defined as SIP.maxConnection in XECfgParm.dat. The Cisco PGW 2200 Softswitch rejects any new connection.
SNMP Trap Type
1 (Communication alarm)
Action
Delete some siplnk components to bring the number of SIP TCP connections under the limitation or set the SIP.maxConnection property in XECfgParm.dat to a larger value than the existing configuration.
OLC: Leg1chanDeletedValidateError
Description
Failed to parse message.
Severity
Informational
Cause
A DLCX Ack message received from the gateway could not be validated.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
OLC: Leg1chanModifiedValidateError
Description
Failed to parse message.
Severity
Informational
Cause
An MDCX Ack message received from the gateway could not be validated.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
OLC: Leg1chanSeizedValidateError
Description
Failed to parse Seized channel (CRCX) message received from the media gateway.
Severity
Informational
Cause
A CRCX Ack message received from the gateway could not be validated.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
OLC: Leg1notifyValidateError
Description
Failed to parse message.
Severity
Informational
Cause
An NTFY message received from the gateway could not be validated.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
OLC: Leg1deleteChanValidateError
Description
Failed to parse message.
Severity
Informational
Cause
A DLCX message received from the gateway could not be validated.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
OLC: Leg1notifyRequestAckValidateError
Description
Failed to parse message.
Severity
Informational
Cause
An RQNT Ack message received from the gateway could not be validated.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
OLC: Leg1chanOpFailed
Description
Action failed.
Severity
Informational
Cause
The Cisco PGW 2200 Softswitch has detected an internal error or a gateway related problem.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
OLC: Leg1DeleteChanPackError
Description
Some required call context data was not available.
Severity
Informational (non-service affecting)
Cause
DeleteChan Msg pack error for Orig leg
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
None
OLC: Leg1ModifyChanPackError
Description
Some required call context data was not available.
Severity
Informational (non-service affecting)
Cause
Some required call context data was not available.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
None
OLC: Leg1SeizeChanPackError
Description
Some required call context data was not available.
Severity
Informational (non-service affecting)
Cause
Some required call context data was not available.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
None.
OLC: Leg1RqntChanPackError
Description
RqntChan Msg pack error for Orig leg
Severity
Informational (non-service affecting)
Cause
RqntChan Msg pack error for Orig leg
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
None
OLC: Leg1UnexpectedEventDetected
Description
Gateway reports events that are not Cisco PGW 2200 Softswitch-requested for the originating leg.
Severity
Informational (non-service affecting)
Cause
Gateway reports events that are not Cisco PGW 2200 Softswitch-requested for the originating leg.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
None required. This alarm is for informational purposes only.
OOS TRAFFIC RE-ROUTE
Description
Traffic rerouted by far-end network element.
Severity
Minor
Cause
Traffic channels (bearer channels, IP network) on one side of the Cisco PGW 2200 Softswitch have been lost, causing the Cisco PGW 2200 Softswitch to reroute channels away from the alarmed entity. The loss of traffic channels is generally due to a network or equipment failure but might be due to a provisioning failure.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
OrigSigpath Label is not found
Description
The location label of the originating sigpath is not found in the location label table.
Severity
Informational
Cause
This alarm indicates that the location label of the originating sigpath is not defined in the location label table.
SNMP Trap Type
3 (Processing error alarm)
Action
Check the location label definition of the originating sigpath.
OrigTrunkgroup Label is not found
Description
The location label of the originating trunk group is not found in the location label table.
Severity
Informational
Cause
This alarm indicates that the location label of the originating trunk group is not defined in the location label table.
SNMP Trap Type
3 (Processing error alarm)
Action
Check the location label definition of the originating trunk group.
OS
Description
Operating system failure.
Severity
Informational
Cause
A process in the operating system has stopped functioning.
SNMP Trap Type
3 (Processing error alarm)
Action
Contact the Cisco TAC immediately. See the preface for information about contacting the Cisco TAC.
OverloadHeavy
Description
Overload heavy condition exists.
Severity
Major
Cause
The engine has reached a critical overload condition because it has too many protocol messages. Failover from the active to standby server occurs. Calls will not be processed unless this condition is corrected.
SNMP Trap Type
4 (Equipment error alarm)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
OverloadMedium
Description
Overload medium condition exists.
Severity
Major
Cause
The engine has reached an overload condition because it has too many protocol messages. The condition will degrade performance and should be corrected as soon as possible, but it will not cause failover from the active to the standby host.
SNMP Trap Type
4 (Equipment error alarm)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
OverloadLight
Description
Overload light condition exists.
Severity
Minor
Cause
The engine has reached a light overload condition because it has too many protocol messages. The condition should be corrected as soon as possible, but it will not cause failover from the active to standby server.
SNMP Trap Type
4 (Equipment error alarm)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
OverResIncomingThreshold
Description
The percentage of the idle circuits in a trunk group has fallen below the configured threshold.
Severity
Informational
Cause
This alarm is reported when the percentage of idle circuits in a trunk group is lower than the configured threshold.
SNMP Trap Type
2 (Quality of service alarm).
Action
No action is required to clear the alarm. It will clear when the percentage of the idle circuits in the trunk group becomes equal to or higher than the configured threshold. If this alarm occurs frequently, you should evaluate the value set in resIncomingPerc for the routing trunk group to determine whether the threshold is appropriate for the routing plan.
PC UNAVAIL
Description
Point code unavailable.
Severity
Major
Cause
The destination point code (DPC) is unavailable. This can be due to a network failure causing the DPC to become isolated, a local equipment failure causing a loss of connectivity, or a local provisioning failure that has caused the DPC or routes to it to be configured improperly.
SNMP Trap Type
1 (Communication alarm)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
Peer Config Mismatched
Description
Configurations on an active and standby pair of Cisco PGW 2200 Softswitches are not the same.
Severity
Minor
Cause
This alarm indicates the configuration mismatch on the active and standby pair of Cisco PGW 2200 Softswitches.
SNMP Trap Type3 (Processing error alarm)
Action
Start a MML provisioning session on the active Cisco PGW 2200 Softswitch. Then run the MML command, prov-dply, to synchronize the configuration on the active host to the standby host. If the alarm is still not cleared after the configuration synchronization is completed, contact Cisco TAC for help.
Peer IP Links Failure
Description
IP links to peer Cisco PGW 2200 Softswitch failed.
Severity
Major
Cause
This alarm is generated when the IP links to the peer system are removed or down.
SNMP Trap Type
3(Processing error alarm)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
PEER LINK A FAILURE
Description
Fail to communicate with peer module over link A.
Severity
Minor
Cause
This alarm is caused either by loss of communication path between peer modules or the peer module has stopped communicating
SNMP Trap Type
1(Communication alarm)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
PEER LINK B FAILURE
Description
Failure to communicate with peer module over link B.
Severity
Minor
Cause
This alarm is caused either by loss of communication path between peer modules or the peer module has stopped communicating
SNMP Trap Type
1 (Communication alarm)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
PEER MODULE FAILURE
Description
Failure to communicate with peer module over configured links.
Severity
Major
Cause
This alarm is raised by loss of communication indicating failure of the peer module.
SNMP Trap Type
1 (Communication alarm)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
POM INACTIVITY TIMEOUT
Description
Alarm Indication Inactivity timeout.
Severity
Informational
Cause
The current provisioning session has no receiving any provisioning commands for 20 minutes. If there is still no activity within the next 5 minutes, the session will be terminated.
SNMP Trap Type
3 (Processing error alarm)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
POM: PEER_SYNC_ERR
Description
The synchronization error on the standby Cisco PGW 2200 Softswitch when it attempts to synchronize its configuration library while a provisioning session is in progress on the active Cisco PGW 2200 Softswitch.
Severity
Major
Cause
This alarm occurs when the standby Cisco PGW 2200 Softswitch attempts to synchronize the contents of its configuration library while a provisioning session is in progress on the active Cisco PGW 2200 Softswitch.
SNMP Trap Type
3 (Processing error alarm)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
POM SESSION TERMINATE
Description
Alarm Indication Provisioning session has terminated.
Severity
Informational
Cause
This alarm indicates that the provisioning session is terminated. No further provisioning command will be accepted.
SNMP Trap Type
3 (Processing error alarm)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
POM: DynamicReconfiguration
Description
Provisioning: Dynamic Reconfiguration
Severity
Minor
Cause
This alarm is sent at the start of the dynamic reconfiguration procedure, and it is cleared once the dynamic reconfiguration is successfully completed.
SNMP Trap Type
3 (Processing error alarm)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
PRI: B-Channel Not Available
Description
B-Channel state is not available.
Severity
Informational
Cause
The Cisco PGW 2200 Softswitch has received a PRI "setup" message, and the requested B channel is not available or cannot be allocated to the call.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
PRI Charge Table Load Failure
Description
This alarm is raised in case of failure to load the PRI Charge table.
Severity
Major.
Cause
Table access failed.
SNMP Trap Type
3 (Processing error alarm).
Action
No action required.
Pri Tariff Charging Unit Table Load Failure
Description
This alarm is raised in case of failure to load the PRI Tariff Charging Unit table.
Severity
Major.
Cause
Table access failed.
SNMP Trap Type
3 (Processing error alarm).
Action
No action required.
PRI Tariff Table Load Failure
Description
This alarm is raised in case of failure to load the PRI Tariff table.
Severity
Major.
Cause
Table access failed.
SNMP Trap Type
3 (Processing error alarm).
Action
No action required.
Process Manually Removed by Reconfig
Description
Process deleted by dynamic reconfiguration.
Severity
Informational
Cause
Indicates that a dynamic reconfiguration has removed a process.
SNMP Trap Type
3 (Processing error alarm)
Action
Contact the Cisco TAC for assistance in resolving this problem.
PROCM M-OOS
Description
Process manager manually out of service.
Severity
Critical
Cause
The process manager has been commanded out of service using an MML command. The event is also generated if the platform is shut down using an MML command.
SNMP Trap Type
3 (Processing error alarm)
Action
Restore the process manager to the in-service state.
ProcM No Response
Description
Process manager not responding to messages sent by failover daemon.
Severity
Major
Cause
The process manager is not responding to state information changes from the failover daemon.
SNMP Trap Type
3 (Processing error alarm)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
ProtocolFileMissing
Description
The protocol file is missing.
Severity
Informational
Cause
Generated when the engine application cannot load an MDO file in the .mdo or .so formats.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
Contact the Cisco TAC for help identifying the protocol package that needs to be installed.
Radius Records Need Collect
Description
Unsent or unacknowledged records were saved locally and need collecting.
Severity
Informational (non-service affecting)
Cause
This alarm occurs when failover happens, when connectivity is lost to all servers, or when the shared memory in IOCC is used up.
SNMP Trap Type
3 (Processing error alarm)
Action
Log in to the Cisco PGW 2200 Softswitch to manually copy RADIUS files and delete them soon. After that, clean up the alarms on your SNMP server.
This alarm notifies you that some records are left in the Cisco PGW 2200 Softswitch. It does not display in rtrv-alms. The Cisco PGW 2200 Softswitch does not clean up the alarms.
Radius Server Unreachable
Description
RADIUS server is unreachable after several retry actions.
Severity
Minor
Cause
RADIUS server is unreachable after trying several times.
SNMP Trap Type
1 (Communication alarm).
Action
Check network traffic and get RADIUS server up.
RSET CONFIG FAIL
Description
Reset configuration failed.
Severity
Informational
Cause
Provisioning data for the SS7 route set to a destination point code has invalid or incompatible parameter values. This event will not be generated due to a mismatch between the network topology and the DPC data.
SNMP Trap Type
3 (Processing error alarm)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
Run time database oversubscription (Release 9.8(1))
Description
The number of TimesTen entries exceeds the allowed amount.
Severity
Major (service affecting)
Cause
This alarm is reported when the number of TimesTen entries exceeds the amount that the purchased TimesTen license allows.
SNMP Type
3 (Processing error alarm)
Action
Contact the account team to purchase additional licenses.
Run-time oversubscription
Description
The call-leg number stays in the oversubscription zone for more than 15 minutes.
Severity
Major (service affecting)
Cause
This alarm is reported by the engine to indicate run-time license oversubscription.
SNMP Trap Type
3 (Processing error alarm)
Action
Contact the account team to purchase additional licenses.
SC CONFIG FAIL
Description
Signal channel configuration failure.
Severity
Major
Cause
Provisioning parameters for the data link layer of a signaling channel are inconsistent or invalid. The signaling channel may already be provisioned. The configuration file might be corrupted and cannot be read by the system.
SNMP Trap Type
1 (Communication alarm)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
SC FAIL
Description
Signal channel failure.
Severity
Major
Cause
The signaling channel is down and unable to process traffic. The channel is failing to negotiate a D-channel session. Automatic restarts are not able to recover the session. The data link-layer has failed. For example, this alarm occurs when SS7 SLTM/SLTA fails or when PRI D-channel fails.
SNMP Trap Type
1 (Communication alarm)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
SCCP CONFIG FAIL
Description
SCCP configuration failed.
Severity
Major
Cause
The SCCP stack could not be initialized due to internal software problems.
SNMP Trap Type
3 (Processing error alarm)
Action
Collect the information from the log files and call the Cisco TAC.
SCCP MTP3 COMM FAIL
Description
SCCP-MTP3 communication failure.
Severity
Major
Cause
Communication between the SS7 channel controller and the TCAP process could not be established.
SNMP Trap Type
1 (Communication alarm)
Action
Ignore this alarm if you have not configured intelligent network (IN) services (such as LNP and toll-free calls). Otherwise, contact the Cisco TAC. See the Preface section of this guide for information about contacting the Cisco TAC.
SCCP RESOURCE LIMITATION
Description
SCCP resource limitation reached.
Severity
Major
Cause
This alarm indicates the SCCP resource limitation is reached.
SNMP Trap Type
2 (Quality of service alarm)
Action
Collect the platform information with the following commands and contact Cisco TAC.
•
•
•
SG Node Interface Fail
Description
All IP connections to a SG node are out of service.
Severity
Major
Cause
The Cisco PGW 2200 Softswitch cannot communicate with the SG.
SNMP Trap Type
1 (Communication alarm)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
SG Pair Interface Fail
Description
All IP connections to both SGs of a pair or a single non-paired SG are out of service.
Severity
Major
Cause
The SG cannot communicate with the peer SG.
SNMP Trap Type
1 (Communication alarm)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
SIGPATH COT Failure 60
Description
Number of COT failures exceeds the 60 minute threshold.
Severity
Major
Cause
The signaling path COT failures has exceeded the alarm threshold for failures per 60 minutes.
SNMP Trap Type
2 (Quality of service error alarm)
Action
None required. This alarm is for informational purposes only.
SIP: 400 RCV TOT
Description
Bad message received count has been reached.
Severity
Major
Cause
The threshold for bad messages received has been exceeded.
SNMP Trap Type
3 (Processing error alarm)
Action
None required. This alarm is for informational purposes only.
SIP: 405 RCV TOT
Description
The threshold for METHOD-NOT-ALLOWED messages received has been reached.
Severity
Major
Cause
The Cisco PGW 2200 Softswitch has received messages for methods that are not supported. A 405 response is sent for each message received. The 405 message transmit counter has reached the set alarm threshold.
SNMP Trap Type
3 (Processing error alarm)
Action
None required. This alarm is for informational purposes only.
SIP: 406 RCV TOT
Description
The threshold for NOT ACCEPTABLE messages received has been reached.
Severity
Major
Cause
The Cisco PGW 2200 Softswitch has received messages for methods that are not acceptable. A 406 response is sent for each message received. The 406 message transmit counter has reached the set alarm threshold.
SNMP Trap Type
3 (Processing error alarm)
Action
None required. This alarm is for informational purposes only.
SIP: 411 MSG RCV
Description
A LENGTH REQUIRED message was received.
Severity
Major
Cause
The Cisco PGW 2200 Softswitch received a LENGTH REQUIRED message.
SNMP Trap Type
3 (Processing error alarm)
Action
None required. This alarm is for informational purposes only.
SIP: 481 RCV TOT
Description
The threshold for CALL LEG/TRANSACTION DOES NOT EXIST messages received has been reached.
Severity
Major
Cause
The Cisco PGW 2200 Softswitch has received a series of CALL LEG/TRANSACTION DOES NOT EXIST messages. The 481 received counter has reached the set alarm threshold.
SNMP Trap Type
3 (Processing error alarm)
Action
None required. This alarm is for informational purposes only.
SIP: 487 RCV TOT
Description
The REQUEST CANCELLED RESPONSE RECEIVED count threshold has been reached.
Severity
Major
Cause
The 487 received counter has reached the set alarm threshold.
SNMP Trap Type
3 (Processing error alarm)
Action
None required. This alarm is for informational purposes only.
SIP: 501 MSG RCV
Description
A NOT IMPLEMENTED message has been received.
Severity
Major
Cause
The Cisco PGW 2200 Softswitch has received a NOT IMPLEMENTED message.
SNMP Trap Type
3 (Processing error alarm)
Action
None required. This alarm is for informational purposes only.
SIP: 502 RCV TOT
Description
The threshold for BAD GATEWAY messages received has been reached.
Severity
Major
Cause
The Cisco PGW 2200 Softswitch has received a series of BAD GATEWAY messages. The 502 received counter has reached the set alarm threshold.
SNMP Trap Type
3 (Processing error alarm)
Action
None required. This alarm is for informational purposes only.
SIP: 504 RCV TOT
Description
The threshold for GATEWAY TIMEOUT messages received has been reached.
Severity
Major
Cause
The Cisco PGW 2200 Softswitch has received a series of GATEWAY TIMEOUT messages. The 504 received counter has reached the set alarm threshold.
SNMP Trap Type
3 (Processing error alarm)
Action
None required. This alarm is for informational purposes only.
SIP: 504 XMIT TOT
Description
The threshold for GATEWAY TIMEOUT messages transmitted has been reached.
Severity
Major
Cause
The Cisco PGW 2200 Softswitch has transmitted a series of GATEWAY TIMEOUT messages. The 504 transmit counter has reached the set alarm threshold.
SNMP Trap Type
3 (Processing error alarm)
Action
None required. This alarm is for informational purposes only.
SIP: 505 MSG RCV
Description
VERSION NOT SUPPORTED message received.
Severity
Major
Cause
The Cisco PGW 2200 Softswitch received a VERSION NOT SUPPORTED message.
SNMP Trap Type
3 (Processing error alarm)
Action
None required. This alarm is for informational purposes only.
SIP: 505 MSG XMIT
Description
VERSION NOT SUPPORTED response sent.
Severity
Major
Cause
The Cisco PGW 2200 Softswitch has transmitted a series of VERSION NOT SUPPORTED messages. The 505 received counter has reached the set alarm threshold.
SNMP Trap Type
3 (Processing error alarm)
Action
None required. This alarm is for informational purposes only.
SIP: 603 RCV TOT
Description
The threshold for REQUEST DECLINED messages received has been reached.
Severity
Major
Cause
The Cisco PGW 2200 Softswitch has received a series of REQUEST DECLINED messages. The 603 received counter has reached the set alarm threshold.
SNMP Trap Type
3 (Processing error alarm)
Action
None required. This alarm is for informational purposes only.
SIP: 606 RCV TOT
Description
The threshold for NOT ACCEPTABLE messages received has been reached.
Severity
Major
Cause
The Cisco PGW 2200 Softswitch has received a series of NOT ACCEPTABLE messages. The 606 received counter has reached the set alarm threshold.
SNMP Trap Type
3 (Processing error alarm)
Action
None required. This alarm is for informational purposes only.
SIP: DNS CACHE NEARLY FULL
Description
DNS cache is nearly full.
Severity
Informational
Cause
The DNS cache is almost out of free entries.
SNMP Trap Type
3 (Processing error alarm)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
SIP: DNS SERVICE OOS
Description
DNS servers are not responding or access has been lost.
Severity
Major
Cause
The DNS servers are not responding to queries. The DNS servers may be out of service or the access to them is lost.
SNMP Trap Type
1 (Communication alarm)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
SIP: INVALID MSG RCV
Description
An invalid message has been received.
Severity
Major
Cause
A message that violated the SIP protocol message format has been received.
SNMP Trap Type
3 (Processing error alarm)
Action
None required. This alarm is for informational purposes only.
SIP: ITP MAP CFG ERR
Description
The ItpActionRequest property has an invalid value.
Severity
Informational
Cause
The Cisco PGW 2200 Softswitch received a "503 Service Unavailable" message from the ITP, which means that the value of the ItpActionRequest in the Route header is not supported.
SNMP Trap Type
1 (Communication alarm)
Action
Modify the ItpActionRequest property to a valid string. Valid strings include "map-app," which supports the Optimize Routing with MAP Query feature.
SIP: OOS
Description
The IP link used by SIP is out of service.
Severity
Major
Cause
The IP link used by the SIP is out of service.
SNMP Trap Type
Communication alarm
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
SIP: RE-XMIT MSG TOT
Description
Retransmit threshold is exceeded.
Severity
Major
Cause
The retransmit threshold count has been exceeded.
SNMP Trap Type
2 (Quality of service error alarm)
Action
None required. This alarm is for informational purposes only.
SIP Service Failover
Description
Virtual addresses for the Cisco PGW 2200 Softswitch cannot be reached due to failure of the associated LAN interfaces. This alarm is cleared automatically when the LAN interface(s) are ready for traffic again.
Severity
Critical
Cause
This alarm is caused by the failure of LAN interfaces, due to either physical failure or administrative shut down.
SNMP Trap Type
3 (Processing error alarm)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
Slave PGW is Active
Description
The slave Cisco PGW 2200 Softswitch is taking the active role.
Severity
Minor
Cause
This alarm indicates that the slave Cisco PGW 2200 Softswitch is taking the active role.
SNMP Trap Type
2 (Quality of service alarm)
Action
None required. This alarm is for informational purposes only.
SOFTW NON
Description
Nonrequired process failure.
Severity
Major
Cause
A nonrequired process cannot be started or continues to fail when started. The process is not necessary for normal operation of the system; however, failure of nonrequired software might reduce the reliability or performance of the system.
SNMP Trap Type
3 (Processing error alarm)
Action
Contact the Cisco TAC. See the Preface section of this guide for information about contacting the Cisco TAC.
SOFTW REQ
Description
Required process failure.
Severity
Critical
Cause
A required process cannot be started or continues to fail when started. The process provides a necessary service on the Cisco PGW 2200 Softswitch that is not related to call processing.
SNMP Trap Type
3 (Processing error alarm)
Action
Contact the Cisco TAC immediately. See the Preface section of this guide for information about contacting the Cisco TAC.
srcpAudit: GwBackhaulProto
Description
AUDIT GW FAIL—partition backhaul protocol mismatch.
Severity
Major
Cause
The backhaul protocol is different from what the Cisco PGW 2200 Softswitch expects.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
Note
srcpAudit: GwBackhaulSes
Description
AUDIT GW FAIL—partition number of backhaul sessions mismatch.
Severity
Minor
Cause
The number of backhaul sessions is different from what the Cisco PGW 2200 Softswitch expects. Some signaling information might be lost, leading to lost or failed calls.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
Note
srcpAudit: GwControlProto
Description
AUDIT GW FAIL—partition control protocol mismatch.
Severity
Major
Cause
The control protocol is different from what the Cisco PGW 2200 Softswitch expects.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
Note
srcpAudit: GwCoordProto
Description
AUDIT GW FAIL—partition coordination protocol mismatch.
Severity
Minor
Cause
The coordination protocol is different from what the Cisco PGW 2200 Softswitch expects. A mismatch here might cause alarms to be raised erroneously.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
Note
srcpAudit: GwCuIpAddr
Description
AUDIT GW FAIL—partition CU IP address mismatch.
Severity
Major
Cause
The IP address of the gateway (CU) reported by the gateway is different from that configured in the Cisco PGW 2200 Softswitch. This event can lead to a communication failure by the control protocol.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
Note
srcpAudit: GwCuIpPort
Description
AUDIT GW FAIL—partition CU IP port mismatch.
Severity
Major
Cause
The IP port of the gateway (CU) reported by the gateway is different from that configured in the Cisco PGW 2200 Softswitch. This event can lead to a communication failure by the control protocol.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
Note
srcpAudit: GwNumOfLines
Description
AUDIT GW FAIL—partition number of lines mismatch.
Severity
Major
Cause
The number of lines in the gateway partition is different from what the Cisco PGW 2200 Softswitch expects. This event may affect service if calls are made on nonexistent lines. Another error should be raised elsewhere in the system if a call is placed to a nonexistent line.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
Note
srcpAudit: GwSlotNum
Description
AUDIT GW FAIL—partition slot number mismatch.
Severity
Informational
Cause
The hardware for the gateway is in a different slot than the Cisco PGW 2200 Softswitch expects. This event should not affect service but might be an issue in hardware troubleshooting.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
Note
srcpAudit: GwSulpAddr
Description
AUDIT GW FAIL—partition SU IP address mismatch.
Severity
Major
Cause
The IP address of the call agent (SU or Cisco PGW 2200 Softswitch) reported by the gateway is different from that configured in the Cisco PGW 2200 Softswitch. This can lead to a communication failure by the control protocol.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
Note
srcpAudit: GwSulpPort
Description
AUDIT GW FAIL—partition SU IP port mismatch.
Severity
Major
Cause
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
Note
srcpAudit: GwType
Description
AUDIT GW FAIL—partition type mismatch.
Severity
Minor
Cause
The gateway is of a different type than the Cisco PGW 2200 Softswitch expects. This may or may not affect service depending on whether the Cisco PGW 2200 Softswitch has gateway-specific coding
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
Note
srcpAudit: LineCoding
Description
AUDIT LINE FAIL—line signaling protocol mismatch.
Severity
Minor
Cause
The line coding used by the gateway for a line is different from what is configured in the Cisco PGW 2200 Softswitch for that line. This might lead to corrupted data on the B channels.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
Note
srcpAudit: LineLoopback
Description
AUDIT LINE FAIL—line loopback state mismatch.
Severity
Minor
Cause
The line loopback for a line used by the gateway is different from what is configured in the Cisco PGW 2200 Softswitch for that line. A line may be in a loopback state when the Cisco PGW 2200 Softswitch believes it is available.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
Note
srcpAudit: LineSigProto
Description
AUDIT LINE FAIL—line coding mismatch.
Severity
Major
Cause
The signaling protocol for a line used by the gateway is different from what is configured in the Cisco PGW 2200 Softswitch for that line. Some signaling information might be lost, leading to lost or failed calls.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
Note
srcpAudit: LineState
Description
AUDIT LINE FAIL—line state mismatch.
Severity
Minor
Cause
The line state for a line used by the gateway is different from what is configured in the Cisco PGW 2200 Softswitch for that line. A line might be disabled by the gateway when the Cisco PGW 2200 Softswitch believes it is available.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
Note
SS7 SG RTE KEY FAIL
Description
SS7 Signaling Gateway Routing Key failure.
Severity
Major
Cause
One or more routing keys for a SS7 signaling service failed; the service will not receive some ISUP messages. The maximum number of routing keys supported by the Tekelec signaling gateway might have been exceeded.
SNMP Trap Type
1 (Communication alarm)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
SS7 SIG SRVC CONFIG FAIL
Description
SS7 Signaling Service configuration failed.
Severity
Major
Cause
The SS7 signaling service is not configured correctly.
SNMP Trap Type
1 (Communication alarm)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
SS7 SIG SRVC UNAVAIL
Description
SS7 signaling is unavailable.
Severity
Major
Cause
SS7 signaling is unavailable.
SNMP Trap Type
1 (Communication alarm)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
SSN FAIL
Description
IN subsystem number (SSN) failed.
Severity
Major
Cause
The SCP located by subsystem number is not available.
SNMP Trap Type
1 (Communication alarm)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
Standby Warm Start
Description
Warm start initiated.
Severity
Minor
Cause
Warm start initiated. This message may also be displayed by the standby system after the MML command PROV-SYNC is used on the active system.
SNMP Trap Type
3 (Processing error alarm)
Action
No action required.
Stop Call
Description
The graceful termination of a call in progress has been initiated.
Severity
Informational
Cause
This alarm is raised when an operator issues the stp-call MML command to release a call and clear connection resources.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
No action required. This alarm is for informational purposes only.
SUAKEY Ack Pending
Description
An acknowledgement for an SUAKEY associated with this SS7SUBSYS or SG has not been received
Severity
Minor
Cause
The Cisco PGW 2200 Softswitch cannot send or receive traffic for the SS7SUBSYS via the SG that has not acknowledged the SUAKEY
SNMP Trap Type
1 (Communication alarm)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
SUPPORT FAIL
Description
Support entity failed.
Severity
Minor
Cause
The entity cannot provide service because a supporting entity is not providing service. The supporting entity may be hardware, such as a disk or line card. It may also be software, such as an application process.
SNMP Trap Type
3 (Processing error alarm)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
SW Fail
Description
Software failure; check log.
Severity
Informational
Cause
A software failure caused by software logic problems, such as:
•
•
•
•
SNMP Trap Type
3 (Processing error alarm)
Action
Contact Cisco TAC immediately. See the Preface section of this guide for information about contacting the Cisco TAC.
SwitchoverFail
Description
Failure to switch network interfaces to active system.
Severity
Major
Cause
Failover from the active to standby server has failed.
SNMP Trap Type
3 (Processing error alarm)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
System type limit license violation
Description
The entitled license number is larger than the license limit of the corresponding base license.
Severity
Major (service affecting)
Cause
This alarm is reported if the LMAgent finds that the entitled license number is larger than the system type license limit.
SNMP Trap Type
3 (Processing error alarm)
Action
Contact the account team to upgrade the base license to a fully featured Cisco PGW 2200 Softswitch.
TALI: Invalid Protocol Version
Description
TALI link has an invalid version.
Severity
Major
Cause
The software on the signaling gateway must support TALI version 3.0.
SNMP Trap Type
3 (Processing error alarm)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
TALI: Invalid State
Description
SG end of TALI signal channel is prohibited.
Severity
Major
Cause
The connection state of the signaling gateway is not in the allowed state.
SNMP Trap Type
1 (Communication alarm)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
Tariff Table Access Failure
Description
Failed to access the charge tariff table.
Severity
Informational
Cause
An Cisco PGW 2200 Softswitch process was unable to read the tariff table.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
Tariff Table Load Failure
Description
Failed to load the charge tariff table.
Severity
Major
Cause
An Cisco PGW 2200 Softswitch process could not load the tariff table.
SNMP Trap Type
3 (Processing error alarm)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
TCAP CONFIG FAIL
Description
Transaction capabilities application part (TCAP) configuration failed.
Severity
Major
Cause
The TCAP trillium stack could not be initialized because of internal software problems.
SNMP Trap Type
3 (Processing error alarm)
Action
Collect the information from the log files and call the Cisco TAC. See the Preface section of this guide for information about contacting the Cisco TAC.
TCAP ENGINE COMM FAIL
Description
TCAP-Engine communication failure.
Severity
Major
Cause
The TCAP engine communication failed.
SNMP Trap Type
1 (Communication alarm)
Action
Collect the information from the log files and call the Cisco TAC. See the Preface section of this guide for information about contacting the Cisco TAC.
TCAP RESOURCE LIMITATION
Description
TCAP resource limitation.
Severity
Major
Cause
The TCAP trillium stack could not be initialized because of memory allocation errors.
SNMP Trap Type
2 (Quality of service)
Action
Call the Cisco TAC. See the Preface section of this guide for information about contacting the Cisco TAC.
TermSigpath Label is not found
Description
The location label of the terminating sigpath is not found in the location label table.
Severity
Informational
Cause
This alarm indicates that the location label of the terminating sigpath is not defined in the location label table.
SNMP Trap Type
3 (Processing error alarm)
Action
Check the location label definition of the terminating sigpath.
TermTrunkgroup Label is not found
Description
The location label of the terminating trunk group is not found in the location label table.
Severity
Informational
Cause
This alarm indicates that the location label of the terminating trunk group is not defined in the location label table.
SNMP Trap Type
3 (Processing error alarm)
Action
Check the location label definition of the terminating trunk group.
TLC: Leg2chanDeletedValidateError
Description
Failed to parse message.
Severity
Informational
Cause
A DLCX Ack message received from the gateway could not be validated.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
TLC: Leg2chanModifiedValidateError
Description
Failed to parse message.
Severity
Informational
Cause
An MDCX Ack message received from the gateway could not be validated.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
TLC: Leg2chanOpFailed
Description
Action failed.
Severity
Informational
Cause
The Cisco PGW 2200 Softswitch has detected an internal error or a gateway related problem.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
TLC: Leg2chanSeizedValidateError
Description
Failed to parse message.
Severity
Informational
Cause
A CRCX Ack message received from the gateway could not be validated.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
TLC: Leg2DeleteChanPackError
Description
DeleteChan Msg pack error for Term leg
Severity
Informational (non-service affecting)
Cause
DeleteChan Msg pack error for Term leg
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
None
TLC: Leg2deleteChanValidateError
Description
Failed to parse message.
Severity
Informational
Cause
A DLCX message received from the gateway could not be validated.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
TLC: Leg2ModifyChanPackError
Description
ModifyChan Msg pack error for Term leg
Severity
Informational (non-service affecting)
Cause
ModifyChan Msg pack error for Term leg
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
None
TLC: Leg2notifyRequestAckValidateError
Description
Failed to parse message.
Severity
Informational
Cause
An RQNT Ack message received from the gateway could not be validated.
SNMP Trap Type
0 (Do not send an SNMP trap.)
Action
See the Alarm Troubleshooting Procedures section of the Troubleshooting chapter of the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide.
