Autonomous System Messages

Transcription

1 1 CHAPTER Revised: August 4, 2010, This 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, page 1-2 Alarm/Event Categories, page 1-3, page 1-4 Obsolete, page Some ISUP alarms do not generate corresponding traps. You can identify these alarms by checking the following files or monitoring real-time alarms: All alarms are configured in the alarmcats.dat file located in the $BASEDIR/etc directory. The last column of file data defines the SNMP trap type. If the trap type is 0, no SNMP trap is generated for this alarm. All alarms including those that do not generate traps are logged in alarm log files located in the /var/spool directory. These files are named alm_date-time_seq.log, where date-time is the timestamp of the log file start time. seq is the sequence number of the file. Example: The alm_ _ log file has a timestamp of 2003/03/28 05:23:12 and a sequence number of For more information on alarm log files, see Appendix A, Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide. You can monitor alarms in real time by using the RTRV-ALMS::CONT MML command. For more information on this command, see the Cisco PGW 2200 Softswitch Release 9 MML Command Reference Guide. 1-1

2 Autonomous Message Components Chapter 1 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. Table 1-1 Autonomous Message Component s Element systemid YYYY-MM-DD hh-mm-ss-ms timezone severity The name of your device and its identifier. Year, month, and day of alarm or event. Hour, minute, second, and millisecond of alarm or event, displayed in system time. Time zone for which the system time is configured. Two-character indicator with the following meanings: *C Critical alarm. Reported to the built-in ARU. ** alarm. Reported to the built-in ARU. *^ Minor alarm. Reported to the built-in ARU. A^ event. If you receive the same event frequently, it is a good idea to research the event because it might be an indicator of a more significant problem. (empty spaces in two leftmost columns). Alarm/Event has been cleared. STATE=CLEARED is displayed. These alarms are not reported to the built-in ARU. They can be obtained from your SNMP manager or by issuing the RTRV-ALMS::CONT MML command. 1-2

3 Chapter 1 Alarm/Event Categories Table 1-1 Element comp almcat params comment Autonomous Message Component s (continued) MML name of the component that is generating the alarm/event. See the Cisco PGW 2200 Softswitch Release 9 Provisioning Guide for more information about components. Alarm category (or event category) A text string that indicates whether the message is an alarm or an informational event and lists the MML alarm or event message. Note Despite its name, the alarm category field is used for both alarms and information events. Supplemental parameters used to further clarify the alarm/event. Supplemental comment used to indicate cause or appropriate action. See the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide for more information on clearing alarms. Note The timestamp in alarm messages is displayed in system time. Figure 1-1 shows an example of an alarm message from RTRV-ALMS. Figure 1-1 Sample Alarm Message Component ID Alarm category level "DC-1-1:ALM=\"SC CONFIG FAIL\",SEV=MJ 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. A brief description of the alarm or event. The severity level of the alarm or event. 1-3

4 Chapter 1 Critical A critical alarm indicates that a critical problem exists somewhere in the network. Critical alarms cause failover (the active server switches processing to the standby server). Critical alarms should be cleared immediately. A major alarm indicates that a serious problem exists that is disrupting service. alarms differ from critical alarms in that they do not cause failovers. alarms should also be cleared immediately. Minor Minor alarms should be noted and cleared as soon as possible. events indicate atypical network conditions, such as timer expirations, values that have exceeded preset thresholds, or unexpected responses from end points to signaling messages sent by the Cisco PGW 2200 Softswitch. Reported Whether the event is reported to the management interface and can be obtained using SNMP. Y = Yes, the event is reported. N = No, the event is not reported. Note All of the alarms or events described here are reported, so this element of the event message text has been omitted in the interest of brevity. of the condition causing the alarm or event. 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: 0 = Do not send an SNMP trap. 1 = Communication alarm 2 = Quality of service alarm 3 = Processing error alarm 4 = Equipment error alarm 5 = Environment error alarm Recommendations for resolving the problem. Note See the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide for more information on acknowledging and clearing alarms. Autonomous system messages and informational events that are reported by the Cisco PGW 2200 Softswitch are described in this section in alphabetical order. 1-4

5 Chapter 1 Active and standby machines have different license files Admin State Locked Admin State Reset License files are mismatched between active and standby Cisco PGW 2200 Softswitches. Local files are used. (service affecting) License files are different on both machines. 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. Component has been placed in administrative state of locked. The lock procedure gracefully takes down the calls and marks bearer channels as locked. 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. 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. Component has been placed in administrative state of reset. 1-5

6 Chapter 1 This alarm is raised after the user runs the MML command: set-admin-state:target:reset,confirm The Cisco PGW 2200 Softswitch releases calls, clears any local blocking and sends out this alarm. None required. This alarm is for informational purposes only. Admin State Unlocked All C7 IP Links Fail Component has been placed in the administrative state of Unlocked. The unlocked procedure marks bearer channel as available for call processing. 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. 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 links transporting MTP3 messages to the signal terminal failed. Note For Release 9.4(1) and up, the severity of this alarm can be configured using a XECfgParm.dat property, *.AllLinksFailsFailover. The property has a default value of false, which sets the severity to. If the value is set to true, the severity is set to Critical. This property should be set to true if your Cisco PGW 2200 Softswitch hosts are geographically separated. You can also set the property to true if 1-6

7 Chapter 1 your system is not processing SS7 calls and you want your system to perform an automatically switchover when all of the connections to your Cisco SLTs fail. Prior to Release 9.4(1), this alarm had a severity of Critical. All Conn Cntl Links Fail All ISDN BRI IP Conn Fail 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. All links transporting connection control messages failed. Generated when the MGCP or SGCP session loses a heartbeat, indicating that the session is down. All IP connections supporting an QSIG/Q.931 Over BRI Backhaul signaling service have failed. This alarm is reported when all IP connections supporting an QSIG/Q.931 Over BRI Backhaul signaling service have failed. 1-7

8 Chapter 1 See the All ISDN BRI IP Conn Fail section. All ISDN IP Conn Fail All IP connections supporting ISDN have failed. Critical Note The ability to change the severity level of this alarm is implemented in a patch (CSCOgs059) for Release 9.5(2). The severity level of this alarm is now controlled by an XECfgParm.dat parameter, *.AllISDNLinksFailsFailover. When this parameter is set to false (the default value), this alarm has a severity level of. If you set this parameter to true, this alarm has a severity level of Critical. 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. 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. All M3UAKEY Acks Pending All acknowledgements for an M3UAKEY associated with this SS7PATH have not been received The Cisco PGW 2200 Softswitch cannot send or receive traffic for the SS7PATH 1-8

9 Chapter 1 Note If you modify an ss7path that is configured for M3UAKEY, the system generates this alarm for every other ss7path that is configured with the same M3UAKEY but is not being modified. Coincidentally, as you are modifying the ss7path, the system generates M3UAKEY Ack Pending alarms while the prov-cpy and prov-dply commands are processing. However, such alarms clear when the commands complete. While the prov-cpy and prov-dply commands are processing, no new calls can be placed to any of the ss7paths for which alarms were generated. Existing calls are not affected. All M3UA Assoc Fail All M3UA associations transporting SS7 signaling have failed. Note The severity of this alarm can be configured using a property, *.AllLinksFailsFailover, in XECfgParm.dat. The property has a default value of false, which sets the severity to. If the value is set to true, the severity is set to Critical. This property should be set to true if your Cisco PGW 2200 Softswitch hosts are geographically separated. You can also set the property to true if your system is not processing SS7 calls and you want your system to perform an automatically switchover when all of the M3UA connections fail. All M3UA associations transporting SS7 signaling have failed. All SUAKEY Acks Pending All acknowledgements for an SUAKEY associated with this SS7SUBSYS have not been received. 1-9

10 Chapter 1 The Cisco PGW 2200 Softswitch cannot send or receive traffic for the SS7SUBSYS. All SUA Assoc Fail All SUA associations transporting SS7 signaling have failed. Note The severity of this alarm can be configured using a property, *.AllLinksFailsFailover, in XECfgParm.dat. The property has a default value of false, which sets the severity to. If the value is set to true, the severity is set to Critical. This property should be set to true if your Cisco PGW 2200 Softswitch hosts are geographically separated. You can also set the property to true if your system is not processing SS7 calls and you want your system to perform an automatically switchover when all of the SUA connections fail. All SUA associations transporting SS7 signaling have failed. ANAL: ALoopCtrExceeded A loop counter was exceeded. 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

11 Chapter 1 ANAL: ATableFail_GetDigMod A-number failed getting modification table. ANAL: ATableFail_GetResult 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. 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. A-table failed getting result table. 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. 1-11

12 Chapter 1 ANAL: ATableFlt_DgtRangeError A-Number analysis digit tree accessed with a digit out of range ANAL: ATableFlt_IdxRangeError 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. A-number analysis Digit tree accessed with a start-index out of range ANAL: BLoopCtrExceeded 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. Contact the Cisco TAC for assistance in resolving this problem. B-loop counter exceeded. 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

13 Chapter 1 ANAL: BNum_GetFail_SrvcTbl B-number analysis was unable to read the service table. 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. ANAL: BNum_MdfyBFail_ AnnounceID The B-number analysis failed to modify B-number to include AnnounceID as last 4 digits. 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. 1-13

14 Chapter 1 ANAL: BTableFail_GetDigMod B number failed getting modification table. ANAL: BTableFail_GetResult 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. B table failed getting result table. 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. ANAL: BTableFlt_DgtRangeError B-Number analysis digit tree accessed with a digit out of range. 1-14

15 Chapter 1 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. ANAL: BTableFlt_IdxRangeError B-number analysis digit tree accessed with a start-index out of range ANAL: _GetFail_Tbl 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. Contact the Cisco TAC for assistance in resolving this problem. The cause analysis was unable to read the cause table. 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 1-15

16 Chapter 1 ANAL: _GetFail_DigModTbl The cause analysis was unable to read the digit modification string. 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. ANAL: _GetFail_InvldRsltType The cause analysis encountered a result that is not valid during cause analysis. ANAL: _GetFail_LocTbl 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. The cause analysis was unable to read the location table. 1-16

17 Chapter 1 ANAL: _GetFail_RsltTbl 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. The cause analysis was unable to read the result table. ANAL: _InvldRslts_Tbl 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. The values returned to cause analysis from the cause table are logically invalid. Occurs when cause analysis successfully reads the cause table, but the value returned is logically invalid. 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. 1-17

18 Chapter 1 ANAL: _MdfyBFail_AnnounceID The cause analysis is unable to modify the B-number to include AnnounceID as the last 4 digits. ANAL: _MdfyBFail_AppPtInvld 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. The cause analysis is unable to perform a B-number modification. ANAL: _Rte_Loop Detected 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. The cause analysis has detected a routing loop. 1-18

19 Chapter 1 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. ANAL: CustID/StartIdx Missing The required property CustId or StartIdx is not present. ANAL: DataBaseAccessFail The property CustGrpId or BOrigStartIndex is not present on the originator. Both properties are required to find the correct place to begin analysis. Access to the on-board database failed. Minor 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. 1-19

20 Chapter 1 ANAL: Data Failure Rcvd Received ExtDataFailure from Routing Engine The analysis module found a data failure in the external routing engine. ANAL: dpselection_table_fail Error reading the dial plan selection table. Minor The correct dial plan selection could not be determined. ANAL: getdialplanbase_fail Failed to get dial plan. Minor 1-20

21 Chapter 1 The Cisco PGW 2200 Softswitch could not load or generate the dial plan. ANAL: InvalidtrkGrpType Invalid trunk group type. ANAL: Prof_GetFail_CPCTbl 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. Generic analysis was unable to read the calling party category (CPC) table. This alarm is reported when generic analysis cannot access the CPC table. An internal processing error has occurred. Capture traces and provisioning data, and contact the Cisco TAC for assistance in resolving this problem. 1-21

22 Chapter 1 ANAL: Prof_GetFail_DigModTbl Profile analysis is unable to read the digit modification string. ANAL: Prof_GetFail_InvldRslt 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. Profile analysis encountered a result that is not valid during profile analysis. 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. ANAL: Prof_GetFail_NOATbl Profile analysis was unable to read the NOA table. 1-22

23 Chapter 1 ANAL: Prof_GetFail_NOATbl_A 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. Profile analysis was unable to read the A-number NOAcg table. ANAL: Prof_GetFail_NPITbl 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. This alarm typically points to an internal processing error. Capture traces and provisioning data, contact your Cisco support representative and provide this information. Profile analysis was unable to read the NPI table. 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. 1-23

24 Chapter 1 ANAL: Prof_GetFail_NPITbl_A Profile analysis was unable to read the A-number NPIcg table. ANAL: Prof_GetFail_RsltTbl 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. This alarm typically points to an internal processing error. Capture traces and provisioning data, contact your Cisco support representative and provide this information. Profile analysis was unable to read the result table. 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. ANAL: Prof_GetFail_TMRTbl Generic analysis is unable to read the transmission medium requirements (TMR) table. 1-24

25 Chapter 1 This alarm is reported when generic analysis cannot access the TMR table. ANAL: Prof_GetFail_TNSTbl An internal processing error has occurred. Capture traces and provisioning data, and contact the Cisco TAC for assistance in resolving this problem. Generic analysis is unable to read the calling transit network selection (TNS) table. This alarm is reported when generic analysis cannot access the TNS table. ANAL: Prof_InvldNPAValue An internal processing error has occurred. Capture traces and provisioning data, and contact the Cisco TAC for assistance in resolving this problem. Profile analysis encountered an invalid NPA value for the originating trunk group. 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. 1-25

26 Chapter 1 ANAL: Prof_InvRslts_NOATbl The values returned to profile analysis from the NOA table are logically invalid. ANAL: Prof_InvRslts_NOATbl_A 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. The values returned to profile analysis from the NOA table are logically invalid. 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. 1-26

27 Chapter 1 ANAL: Prof_MdfyBFail_AppPtInvld ANAL: RedirectingNbrFail This alarm typically points to an internal processing error. Capture traces and provisioning data, contact your Cisco support representative and provide this information. Profile analysis was unable to perform a B-number modification. 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. Redirecting number is being used during A-number tree analysis, and a result type other than Blacklist has been encountered. 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. 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. 1-27

28 Chapter 1 ANAL: RteStartIndexInvalid Route start index invalid. The start index for the route analysis table is invalid. ANAL: RteTableFail_GetRteList Route table file failed getting route list. ANAL: RteTableFail_GetTrkAttrdata 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. Route table failed getting trunk attribute data. 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. 1-28

29 Chapter 1 ANAL: RteTableFail_GetTrkGrpdata Route table failed getting trunk group data. ANAL: RteTableFail_GetTrunkList 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. Route table failed getting trunk list. ANAL:Rte_TableHopCtrExceeded 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. Generic analysis has encountered excessive analysis table hops. 1-29

30 Chapter 1 This alarm is reported when the number of analysis table hops is exceeded during generic analysis. ANAL: SerialCountExceeded 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. Serial triggering counter exceeded. 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. ANAL:TableFail_BearerCapTable None required. This alarm is for informational purposes only. Generic analysis is unable to read the bearer capacity data table. This alarm is reported when generic analysis cannot access the bearer capacity data table. 1-30

31 Chapter 1 ANAL:TableFail_CondRouteDescTable An internal processing error has occurred. Capture traces and provisioning data, and contact the Cisco TAC for assistance in resolving this problem. Generic analysis is unable to read the conditional route description table. This alarm is reported when generic analysis cannot access the conditional route description table. ANAL: TableFail_CondRouteTable An internal processing error has occurred. Capture traces and provisioning data, and contact the Cisco TAC for assistance in resolving this problem. Generic analysis was unable to read the conditional routing table. This alarm is reported when the conditional routing table is not available during generic analysis. An internal processing error has occurred. Rebuild the dial plan. Contact the Cisco TAC for assistance in resolving this problem. 1-31

32 Chapter 1 ANAL:TableFail_PercRouteTable Generic analysis is unable to read the percentage route table. This alarm is reported when generic analysis cannot access the percentage route table. ANAL: TableFail_RouteHolTable An internal processing error has occurred. Capture traces and provisioning data, and contact the Cisco TAC for assistance in resolving this problem. Failure to read the route holiday table. Generic analysis was unable to read the route holiday table. ANAL: TrunkGrpRsltCtrExceeded 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. Trunk group result counter exceeded. 1-32

33 Chapter 1 ANAL: VPNid_GetFail_VPNidTbl 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. The analysis module cannot read the VPNid table. This alarm indicates that the analysis module failed to read the VPNid table. Anumber Label is not found An internal processing error has occurred. Capture traces and provisioning data, and contact the Cisco TAC for assistance in resolving this problem. The location label of A number is not found in the location label table. This alarm indicates the location label of A number is not defined in the location label table. Check the location label definition of the A number. 1-33

34 Chapter 1 Association Fail (Release 9.4(1)) The SCTP association has failed. This alarm is reported when the destination node is out of service or there is an IP connectivity failure. Association Fail (Release 9.6(1)) The SCTP association has failed. This alarm is reported when the destination node is out of service or there is an IP connectivity failure. See Association Fail. Association Degraded (Release 9.4(1)) A destination address of the association has failed, and the association is still in an UP state. Minor This alarm is reported when one of the association destination addresses has failed. 1-34

35 Chapter 1 Association Degraded (Release 9.6(1)) A destination address of the association has failed, and the association is still in an UP state. Minor This alarm is reported when one of the association destination addresses has failed. See Association Degraded. Base license line missing in license files The base license line is missing in license files. (service affecting) This alarm could happen if the license file containing the base license has been removed. Bnumber Label is not found 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. The location label of B number is not found in the location label table. 1-35

36 Chapter 1 This alarm indicates the location label of B number is not defined in the location label table. Check the location label definition of the B number. C7DPC CONGESTION Destination point code is congested. 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. 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 C7 link alignment lost This alarm occurs when the MTP2 for the C7 link between a Cisco SLT and an associated APC has lost alignment. 1-36

37 Chapter 1 C7LNK BLOCKED C7 link blocked An SS7 link is blocked from the remote end. None required. This alarm is removed when the far end unblocks the MTP2 link. C7LNK CONGESTION C7 link congestion. The SS7 MTP2 link has encountered congestion, and it cannot receive any more messages. 2 (Quality of service) C7LNK INHIBIT C7 link inhibit. The C7 link has been inhibited for maintenance. 1-37

38 Chapter 1 C7LNK INHIBIT DENY C7 link inhibit deny. An SS7 link inhibit request has been denied. An inhibit request will be denied on critical links within a linkset. None. This is an informational event C7SLTLnkCong SS7 SLT link is congested. Minor Call Back feature insertion failure Generated when an SS7 link on the SLT side becomes congested. 2 (Quality of service alarm) A call back feature entry insertion in the main memory database fails. 1-38

39 Chapter 1 Call Back feature deletion failure 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. The problem identified by this alarm can only be resolved by the Cisco TAC. A call back feature entry deletion from the main memory database fails. CAS: Leg1RQNTTimeOutError 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. The problem identified by this alarm can only be resolved by the Cisco TAC. The originating leg fails to receive an acknowledgement to a notifyrequest message. The originating leg fails to receive an acknowledgement to a notifyrequest message. 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. 1-39

40 Chapter 1 CAS: Leg2RQNTTimeOutError The terminating leg fails to receive an acknowledgement to a notifyrequest message. The terminating leg fails to receive an acknowledgement to a notifyrequest message. 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 Signal channel TCA total frame errors 15 min. Minor 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. 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 Channel TCA total frame errors 24 hours. Minor 1-40

41 Chapter 1 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. 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 Channel TCA total frame errors 60 min. Minor 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. 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 Channel TCA link established 15 min. 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. 1-41

42 Chapter 1 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 Channel TCA link established 24 hours. 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. No immediate response is required; however, the condition should be monitored closely. CHAN LINK ESTAB 60 Channel TCA link established 60 min. 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. 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. 1-42

43 Chapter 1 Charge Table Access Failure Charge Table Load Failure Chkpt Synch Inprogress Failed to access the charge table. The Cisco PGW 2200 Softswitch could not access the charge table. Failed to load the charge table. An Cisco PGW 2200 Softswitch process has been unable to load the charge table. Active and standby synchronization is in progress. Checkpointing is active, and the standby synchronization process is in progress. 1-43

44 Chapter 1 This event does not require an immediate response. Comm Srvc Creation Error Failed to create communication service. Minor There has been an error creating or opening a communication service. Configuration time port discrepancy period expired Config Fail The discrepancy period expired. The license will be enforced at run time. The allowed configuration time TDM port and SIP and H.323 call legs discrepancy period expired. None required. This alarm is for informational purposes only. Configuration has failed. 1-44

45 Chapter 1 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 Conn Cntl Link Fail Conn Cntl Service Lost The link that transporting connection control messages failed. Minor Generated when the MGCP session loses a heartbeat, indicating that the session is down. 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. The Cisco PGW 2200 Softswitch loses the ability to provide service for connection control. Critical Generated when the connection control ability was lost on Cisco PGW 2200 Softswitch. 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. 1-45

46 Chapter 1 CPM: Leg1chanDeletedUnpackError Fault in data received from the engine. Indicates an MDL source code issue. CPM: Leg1chanFailed Resource failure in the engine. Indicates an MDL source code issue. No action is required. The Cisco TAC can use this information to troubleshoot call-processing problems. CPM: Leg1chanModifiedUnpackError Fault in data received from the engine. Indicates an MDL source code issue. 1-46

47 Chapter 1 No action is required. The Cisco TAC can use this information to troubleshoot call-processing problems. CPM: Leg1chanOpFailed A resource failure in the engine. Indicates an MDL source code issue. No action is required. The Cisco TAC can use this information to troubleshoot call-processing problems. CPM: Leg1chanSeizedUnpackError Some fault in data received from the engine. Indicates an MDL source code issue. No action is required. The Cisco TAC can use this information to troubleshoot call-processing problems. CPM: Leg1ConfigError Inconsistent VirtualSwitch and oconplanectrl. Indicates an MDL source code issue. 1-47

48 Chapter 1 No action is required. The Cisco TAC can use this information to troubleshoot call-processing problems. CPM: Leg1CotStateError Requested action is incompatible with CPM COT state. Indicates an MDL source code issue. No action is required. The Cisco TAC can use this information to troubleshoot call-processing. CPM: Leg1DeleteChanPackError Some required call context data was not available. Indicates an MDL source code issue. No action is required. The Cisco TAC can use this information to troubleshoot call-processing problems. CPM: Leg1ExtCOTPropError Prop is neither Loop nor Transponder. 1-48

49 Chapter 1 Indicates an MDL source code issue. No action is required. The Cisco TAC can use this information to troubleshoot call-processing problems. CPM: Leg1ModifyChanPackError Required call context data was not available. Indicates an MDL source code issue. No action is required. The Cisco TAC can use this information to troubleshoot call-processing problems. CPM: Leg1RMXmitCotError RMXmitCot returned false. Indicates an MDL source code issue. No action is required. The Cisco TAC can use this information to troubleshoot call-processing problems. CPM: Leg1RqntChanPackError A call-context variable is not available. 1-49

50 Chapter 1 Indicates an MDL source code issue. No action is required. The Cisco TAC can use this information to troubleshoot call-processing problems. CPM: Leg1SeizeChanPackError Some required call context data was not available. Indicates an MDL source code issue. No action is required. The Cisco TAC can use this information to troubleshoot call-processing problems. CPM: Leg1StateError Requested action is incompatible with CPM leg state. Indicates an MDL source code issue. No action is required. The Cisco TAC can use this information to troubleshoot call-processing problems. 1-50

51 Chapter 1 CPM: Leg1TestLineLoopError Test line loop back error. Indicates an MDL source code issue. No action is required. The Cisco TAC can use this information to troubleshoot call-processing problems. CPM: Leg1TestLineResourceError A brief description of the alarm or event. Indicates an MDL source code issue. No action is required. The Cisco TAC can use this information to troubleshoot call-processing problems. CPM: Leg1TestLineTableError Error reading the Test Line Table. Indicates an MDL source code issue. 1-51

52 Chapter 1 No action is required. The Cisco TAC can use this information to troubleshoot call-processing problems. CPM: Leg1TestLineToneError Test line tone error. Indicates an MDL source code issue. No action is required. The Cisco TAC can use this information to troubleshoot call-processing problems. CPM: Leg1Timeout No response received from the engine. This event denotes an MDL source code issue. No action is required. The Cisco TAC can use this information to troubleshoot call-processing problems. CPM: Leg2chanDeletedUnpackError Some fault in data received from the engine. Indicates an MDL source code issue. 1-52

53 Chapter 1 No action is required. The Cisco TAC can use this information to troubleshoot call-processing problems. CPM: Leg2chanFailed A resource failure in the engine. Indicates an MDL source code issue. No action is required. The Cisco TAC can use this information to troubleshoot call-processing problems. CPM: Leg2chanModifiedUnpackError Some fault in data received from the engine. Indicates an MDL source code issue. No action is required. The Cisco TAC can use this information to troubleshoot call-processing problems. CPM: Leg2chanOpFailed A resource failure in the engine. 1-53

54 Chapter 1 Indicates an MDL source code issue. No action is required. The Cisco TAC can use this information to troubleshoot call-processing problems. CPM: Leg2chanSeizedUnpackError Some fault in data received from the engine. Indicates an MDL source code issue. No action is required. The Cisco TAC can use this information to troubleshoot call-processing problems. CPM: Leg2ConfigError Inconsistent VirtualSwitch and tconplanectrl. Indicates an MDL source code issue. No action is required. The Cisco TAC can use this information to troubleshoot call-processing problems. CPM: Leg2CotStateError Requested action is incompatible with CPM COT state. 1-54

55 Chapter 1 Indicates an MDL source code issue. No action is required. The Cisco TAC can use this information to troubleshoot call-processing problems. CPM: Leg2DeleteChanPackError Some required call context data was not available. Indicates an MDL source code issue. No action is required. The Cisco TAC can use this information to troubleshoot call-processing problems. CPM: Leg2ExtCOTPropError Prop is neither loop nor transponder. Indicates an MDL source code issue. No action is required. The Cisco TAC can use this information to troubleshoot call-processing problems. 1-55