Table of Contents

Autonomous Messages

Alarm/Event Categories

Log Messages

System Messages

This chapter lists system messages generated by the Cisco MGC software, including MML responses, alarms, and events. See "MML Command Reference," for more information about MML commands. This chapter contains the following sections:

• Autonomous Messages

• Log Messages

Autonomous Messages

The Cisco MGC 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 an SNMP manager.

Alarms and informational events follow the Telcordia (formerly Bellcore) TL1 autonomous message format.

Alarms and informational events have different behavior. An alarm must by reported when alarm state changes (assuming the alarm does not have a nonreported severity). It is a significant violation of existing management systems to report consecutive active or clear state changes for a particular alarm on a single entity.

A informational event is reported without requiring a state change. 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. It needs to be reported but 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 2-1 defines the message components as displayed using the RTRV-ALMS::CONT command while listening for alarm events.

Table 2-1: Autonomous Message Component Descriptions

Element	Description
systemId	The name of your device and its identifier.
YYYY-MM-DD	Year, month, and day of alarm or informational event.
hh-mm-ss-ms	Hour, minute, second, and millisecond of alarm or informational event.
severity	Severity level of alarm or informational event. This is a two-character indicator with the following meanings: *C---Critical alarm. Critical alarms indicate that a serious problem exists in the network. Critical alarms cause failover (the active server switches processing to the standby server). Critical alarms should be cleared immediately. These alarms are reported to the built-in ARU. **---Major alarm. Major alarms indicate that a problem exists that disrupts service. These alarms should be cleared immediately. Major alarms differ from critical alarms in that they do not cause failover from the active system to the standby system. These alarms are reported to the built-in ARU. *^---Minor alarm. Minor alarms should be noted and cleared as soon as possible. These alarms are reported to the built-in ARU. A^---Informational event. Informational 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 MGC. --- (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. You may want to track how often you receive informational events. If you receive the same event frequently, it is a good idea to research the event, because it might be an indicator of a bigger problem.
comp	The MML name of the system component that is generating the alarm/event. See the Cisco Media Gateway Controller Installation and Configuration Guide for more information about components.
almCat	Alarm category (or event category)---A text string that indicates whether the message is an alarm or an informational event and the MML alarm or event message. See Table 2-2 for a list of alarm categories. Note Despite its name, the alarm category field is used for both alarms and information events.
params	Supplemental parameters used to further clarify the alarm/event.
comment	Supplemental comment used to indicate cause or appropriate action.

Figure 2-1 shows an example of an alarm message from RTRV-ALMS non-continuos.

Figure 2-1: Sample Alarm Message

To determine the meaning of the alarm or event, locate the alarm category in Table 2-2. See the Cisco Media Gateway Controller Software Release 7 Operations, Maintenance, and Troubleshooting Guide for more information on clearing alarms.

Alarm/Event Categories

Table 2-2 lists the following alarm/event information:

• Alarm category---Alarm/event message displayed in MML.

• Description---Brief description of alarm/event.

• Severity level---The severity of the alarm/event.

• Event reporting---Whether the event is reported to the management interface and can be obtained using SNMP.

• Alarm/event cause---The condition causing the alarm/event.

• SNMP trap type---The Cisco MGC software generates an SNMP trap for autonomous messages. Trap types are:

  • 0 = No error

  • 1 = Communication alarm

  • 2 = Quality of service

  • 3 = Processing error alarm

  • 4 = Equipment error alarm

  • 5 = Environment error alarm

See the Cisco Media Gateway Controller Software Release 7 Maintenance, and Troubleshooting Guide for more information on acknowledging and clearing alarms
Table 2-2: Alarm/Event Categories

Alarm/Event Category	Description	Severity Level	Event Report	Alarm Cause	Trap Type	Suggested Action
Admin State Locked	Component has been placed in Administrative State of Locked. The lock procedure gracefully takes down the calls and marks bearer channels as locked.	Information	Y	This event is 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 even to mark the start of the lock procedure. The lock process marks bearer channels as locked and allow calls to terminate gracefully.	0	No action necessary. For more information, refer to the Admin State Unlocked event, below, and "MML Command Reference."
Admin State Unlocked	Component has been placed in Administrative State of Unlocked. The unlocked procedure procedure marks bearer channel as available for call processing	Information	Y	This event is generated when the MML command SET-ADMIN-STATE is used to unlock a component. The ENGINE for VSC, GWAY, SIGPATH and TRUNKGROUP components generates this even to mark the start of the UNLOCK procedure. The UNLOCK process unblocks bearer channels and allows bearer channels to be available for call processing.	0	No action necessary. For more information, refer to the Admin State Locked event, above, and "MML Command Reference."
All Conn Cntl Links Fail	All links transporting connection control messages failed.	Major	Y	This alarm is generated when the MGCP / SGCP session loses a heartbeat, indicating that the session is down.	1	Check Ethernet. Check if the near-end and far-end MGCP / SGCP sessions are operating normally.
All C7 IP Links Fail	All links transporting MPT3 messages to the signal terminal failed.	Critical	Y	This alarm is generated when MTP2 is terminated on a series of Cisco SLTs, and MTP3 is backhauled to the Cisco MGC over Ethernet. This is reported when communication is lost to all Cisco SLTs. This defaults to a critical alarm, and causes a failover if a standby is present.	1	Check Ethernet. Check configuration. Check operation of Cisco SLTs.
All ISDN IP Conn Fail	All IP connections supporting ISDN have failed.	Critical	Y	This alarm is generated when ISDN layer 2 is terminated on a series of Cisco access servers and backhauled to the Cisco MGC over Ethernet. This is reported when communiation is lost to all access servers. This defaults to a critical alarm and causes a failover if standby is present.	1	Check Ethernet. Check configuration. Check operation of access servers.
ANAL: ABNum_AccessFail_ ScrnDB	Analysis: A- or B-number analysis was unable to access the screening database.	Information	Y	The event occurs during A-number or B-number analysis when a screening result is being processed. A call is made to the screening database and the result code returned indicates an error accessing the database. If the SysScreeningCheck parameter in XECfgParm.dat is set to true, then all calls are terminated; if it is set to false, all calls are completed without having been screened.	0	If the box is on a redundant system, check that the alarm "MMDB:Database cause failover" has been set. This alarm will cause a failover in a failover pair. If the box is configured as standalone, the alarm "MMDB:Database unavailable" should be set. See the relevant alarms for more detail.
ANAL: ALoopCtrExceeded	Analysis: A loop counter was exceeded.	Information	Y	The event 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.	0	Validate that there are no infinite loops in the A-number dial plan.
ANAL: ATableFail_GetDigTree	Analysis: A-table failed getting analysis table.	Information	Y	The event indicates that an invalid path for A-number analysis has been given or that the A-number analysis table is not loaded. The problem is caused when an invalid path has been specified for A-number analysis or the A-number analysis table is not loaded.	0	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 the MML commands or SNMP interface.
ANAL: ATableFail_GetDigMod	Analysis: A-number failed getting modification table.	Information	Y	The event indicates that retrieval of a modification string failed while performing 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.	0	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 the MML commands or SNMP interface.
ANAL: ATableFail_GetResult	Analysis: A-table failed getting result table.	Information	Y	This event indicates that access to the result table failed while performing 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.	0	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 the MML commands or SNMP interface.
ANAL: BLoopCtrExceeded	Analysis: B-loop counter exceeded.	Information	Y	The event 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.	0	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 the MML commands or SNMP interface.
ANAL: BNum_GetFail_SrvcTbl	Analysis: B-number analysis was unable to read the service table.	Information	Y	This event 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. This is due to corruption of either the result table or the service table.	0	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 the MML commands or SNMP interface.
ANAL: BNum_MdfyBFail_ AnnounceID	Analysis: The B-number analysis failed to modify B-number to include AnnounceID as last 4 digits.	Information	Y	This event occurs during B-number 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 is commonly caused by an out-of-range announcement Id (it should be 0-9999) or a B-number less than 4 digits long.	0	Ensure that all configured announcement IDs are in the range 0-9999. 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 the MML commands or SNMP interface.
ANAL: BTableFail_GetDigTree	Analysis: B table failed getting analysis table.	Information	Y	This event indicates that an invalid path for B-number analysis has been given or that the B-number analysis table is not loaded. The problem occurs when an invalid path has been specified for B-number analysis or the B-number analysis table is not loaded.	0	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 the MML commands or SNMP interface.
ANAL: BTableFail_GetDigMod	Analysis: B number failed getting modification table.	Information	Y	This event indicates that 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.	0	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 the MML commands or SNMP interface.
ANAL: BTableFail_GetResult	Analysis: B table failed getting result table.	Information	Y	This event indicates that access to the result table failed while performing B-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.	0	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 the MML commands or SNMP interface.
ANAL: Cause_GetFail_CauseTbl	Analysis: The cause analysis was unable to read the cause table.	Information	Y	This event occurs during cause analysis when the cause table is unreadable. This 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	0	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 the MML commands or SNMP interface.
ANAL: Cause_GetFail_DigModTbl	Analysis: The cause analysis was unable to read the digit modification string.	Information	Y	This event occurs during cause analysis when a B-number modification result is encountered and the digit modification string is unreadable. This can be due to the digit modification table being corrupted or an incorrect digit modification index being stored in the B-number modification result's data.	0	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 the MML commands or SNMP interface.
ANAL: Cause_GetFail_InvldRsltType	Analysis: The cause analysis encountered a result that is not valid during cause analysis.	Information	Y	This event occurs during cause analysis when a result is encountered that is not supported in cause analysis. This is due to corruption of the cause or location tables or the result table.	0	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 the MML commands or SNMP interface.
ANAL: Cause_GetFail_LocTbl	Analysis: The cause analysis was unable to read the location table.	Information	Y	This event occurs during cause analysis when the location table is unreadable. This 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.	0	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 the MML commands or SNMP interface.
ANAL: Cause_GetFail_RsltTbl	Analysis: The cause analysis was unable to read the result table.	Information	Y	This event occurs during cause analysis when the result table is unreadable. This 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.	0	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 the MML commands or SNMP interface.
ANAL: Cause_InvldRslts_CauseTbl	Analysis: The values returned to cause analysis from the cause table are logically invalid.	Information	Y	This event 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. Most likely this results from a failure of the underlying software or a corruption of the cause table.	0	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 the MML commands or SNMP interface.
ANAL: Cause_MdfyBFail_ AnnounceID	Analysis: The cause analysis is unable to modify the B-number to include AnnounceID as the last 4 digits.	Information	Y	This event 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 is commonly caused by an out-of-range announcement ID (it should be 0-9999) or a B-number less than 4 digits long.	0	Ensure that all configured announcement IDs are in the range 0-9999. 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 the MML commands or SNMP interface.
ANAL: Cause_MdfyBFail_ AppPtInvld	Analysis: The cause analysis is unable to perform a B-number modification.	Information	Y	This event occurs during cause analysis when a B-number modification result is encountered and the application point (where digits are inserted) specified is beyond the end of the digit string. This is caused by an incorrect application point being specified in the result data, a corrupt result table, or incorrectly constructed cause analysis values.	0	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 the MML commands or SNMP interface.
ANAL: Cause_Rte_Loop Detected	Analysis: The cause analysis has detected a routing loop.	Information	Y	This event 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.	0	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 the MML commands or SNMP interface.
ANAL: CustId/StartIdx Missing	Analysis: The required property CustId or StartIdx is not present.	Information	Y	This event indicates that the property CustGrpId or BOrigStartIndex are not present on the originator. These are required to find the correct place to begin analysis.	0	Check that the CustGrpId and the BOrigStartIndex have been set against the trunk group in a switched environment and the sigpath in a nailed environment.
ANAL: Data Failure Rcvd	Analysis: Received ExtDataFailure from Routing Engine	Information	Y	This event indicates that the analysis module found a data failure in the external routing engine.	0	Check the log for errors from the routing engine. Those errors should provide more information.
ANAL: InvalidtrkGrpType	Analysis: Invalid trunk group type.	Information	Y	This event indicates that 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.	0	Ensure that the trunk group types are valid for the routing.
ANAL: Prof_GetFail_DigMod Tbl	Analysis: Profile analysis is unable to read the digit modification string.	Information	Y	This event occurs during profile analysis when a B-number modification result is encountered and the digit modification string is unreadable. This can be due to the digit modification table being corrupted or an incorrect digit modification index being stored in the B-number modification result's data.	0	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 the MML commands or SNMP interface.
ANAL: Prof_GetFail_InvldRslt	Analysis: Profile analysis encountered a result that is not valid during profile analysis.	Information	Y	This event occurs during profile analysis when a result is encountered that is not supported in profile analysis. This is due to corruption of either the NOA or NPI tables or the result table.	0	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 the MML commands or SNMP interface.
ANAL: Prof_GetFail_NOATbl	Analysis: Profile analysis was unable to read the NOA table.	Information	Y	This event occurs during profile analysis when the NOA table is unreadable. This 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.	0	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 the MML commands or SNMP interface.
ANAL: Prof_GetFail_NPITbl	Analysis: Profile analysis was unable to read the NPI table.	Information	Y	This event occurs during profile analysis when the NPI table is unreadable. This 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.	0	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 the MML commands or SNMP interface.
ANAL: Prof_GetFail_RsltTbl	Analysis: Profile analysis was unable to read the result table.	Information	Y	This event occurs during profile analysis when the result table is unreadable. This 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.	0	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 the MML commands or SNMP interface.
ANAL: Prof_InvldNPAValue	Analysis: Profile analysis encountered an invalid NPA value for the originating trunk group.	Information	Y	This event 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 is most likely caused by data corruption.	0	Ensure that the NPAs have been provisioned correctly for the trunk group.
ANAL: Prof_InvRslts_NOATbl	Analysis: The values returned to profile analysis from the NOA table are logically invalid.	Information	Y	This event 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 results from a failure of the underlying software or a corruption of the NOA table.	0	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 the MML commands or SNMP interface.
ANAL: Prof_MdfyBFail_AppPtInvld	Analysis: Profile analysis was unable to perform a B-Number modification.	Information	Y	This event 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 is caused by an incorrect application point being specified in the result data, a corrupt result table, or incorrectly constructed Profile analysis values.	0	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 the MML commands or SNMP interface.
ANAL: RteStartIndexInvalid	Analysis: Route start index invalid.	Information	Y	This event indicates that the start index for the route analysis table is invalid.	0	Ensure that the route list names referred to by the dial plan are configured in the routing.
ANAL: RteTableFail_GetRteList	Analysis: Route table file failed getting route list.	Information	Y	This event indicates that 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.	0	Check the logs to ensure that there have been no errors in loading routing. Ensure that the routing was imported into the system using either the MML commands or SNMP interface.
ANAL: RteTableFail_GetTrk Attrdata	Analysis: Route table failed getting trunk attribute data.	Information	Y	This event indicates that access to the trunk group attribute data table failed. The problem occurs if the index to the trunk group attribute data table is not valid or if the table is not loaded.	0	Check the logs to ensure that there have been no errors in loading routing. Ensure that the routing was imported into the system using either the MML commands or SNMP interface.
ANAL: RteTableFail_GetTrk Grpdata	Analysis: Route table failed getting trunk group data.	Information	Y	This event indicates that access to the trunk group data failed. The problem occurs if the index to the trunk group data is not valid or if the trunk group data table is not loaded.	0	Check the logs to ensure that there have been no errors in loading routing. Ensure that the routing was imported into the system using either the MML commands or SNMP interface.
ANAL: RteTableFail_GetTrunkList	Analysis: Route table failed getting trunk list.	Information	Y	This event indicates that 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.	0	Check the logs to ensure that there have been no errors in loading routing. Ensure that the routing was imported into the system using either the MML commands or SNMP interface.
ANAL: TrunkGrpRsltCtr Exceeded	Analysis: Trunk group result counter exceeded.	Information	Y	This event indicates that the analysis module has provided the maximum number of candidate trunk groups allowed. The maximum number is 20. The purpose of the alarm is to limit the time spent searching for candidate trunk groups.	0	Check the logs to ensure that there have been no errors in loading routing. Ensure that the routing was imported into the system using either the MML commands or SNMP interface.
C7LNK BLOCKED	C7 link blocked	Minor	Y	This alarm indicates that an SS7 link is blocked from the remotre end.	1	None required. This will be removed when the far end unblocks the MTP2 link.
C7LNK CONGESTION	C7 link congestion.	Major	Y	This alarm indicates that the SS7 MTP2 link has encountered congestion such that it cannot receive any more messages.	2	Reduce traffic from the far end. Potentially add more links to the linkset.
C7LNK INHIBIT	C7 link inhibit.	Minor	Y	This alarm indicates that the C7 link has been inhibited for maintenance.	1	Restore the link after maintenance has been completed.
C7LNK INHIBIT DENY	C7 link inhibit deny.	Information	Y	This event indicates that an SS7 link inhibit request has been denied. An inhibit request will be denied on critical links within a linkset.	1	None. This is an informational event.
CHAN BAD TOT 15	Signal channel TCA total frame errors---15 min.	Information	Y	This event indicates that the number of bad HDLC1 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.	0	The channel remains in an In-Service state. This event is informational only and is sent to the alarm manager as an autonomous alarm.
CHAN BAD TOT 60	Channel TCA total frame errors---60 min.	Information	Y	This event indicates that the number of bad HDLC frames received on this channel (DS-0 time slot) has exceeded the threshold value set in the thresholds.dat table for the last 60-min. period. The channel remains in an In-Service state.	0	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 BAD TOT 24	Channel TCA total frame errors---24 hours.	Information	Y	This event indicates that the number of bad HDLC frames received on this channel (DS-0 time slot) has exceeded the threshold value set in the thresholds.dat table for the last 24-hour period. The channel remains in an In-Service state.	0	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 15	Channel TCA link established---15 min.	Information	Y	This event indicates that the number of resets on this channel (DS-0) has exceeded the threshold value set in the thresholds.dat table for the last 15-min. period. The channel remains in an In-Service state.	0	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 60	Channel TCA link established---60 min.	Information	Y	This event indicates that the number of resets on this channel (DS-0) has exceeded the threshold value set in the thresholds.dat table for the last 60-min. period. The channel remains in an In-Service state.	0	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.	Information	Y	This event indicates that the number of resets on this channel (DS-0) has exceeded the threshold value set in the thresholds.dat table for the last 24-hour period. The channel remains in an In-Service state.	0	This event is informational only and does not require an immediate response; however, the condition should be monitored closely to ensure that service levels do not degrade further.
Chkpt Synch Inprogress	Active and standby synchronization is in progress.	Information	Y	This event indicates that the checkpointing active and standby synchronization process has begun and is in progress.	3	This event is informational only and does not require an immediate response.
Config Fail	Configuration has failed.	Information	Y	This event indicates that the configuration has failed.	3	Check the log files for more information.
CPM: Leg1chanDeleted UnpackError	Fault in data received from the engine.	Information	Y	This event denotes an MDL2 source code issue and is informational only. No user action is required. The Cisco TAC3 might use this information in troubleshooting call-processing problems.	0	No user action is required. The Cisco TAC might use this information in troubleshooting call-processing problems.
CPM: Leg1chanFailed	Resource failure in the engine.	Information	Y	This event denotes an MDL source code issue and is informational only.	0	No user action is required. The Cisco TAC might use this information in troubleshooting call-processing problems.
CPM: Leg1chanModified UnpackError	Fault in data received from the engine.	Information	Y	This event denotes an MDL source code issue and is informational only.	0	No user action is required. The Cisco TAC might use this information in troubleshooting call-processing problems.
CPM: Leg1chanOpFailed	A resource failure in the engine.	Information	Y	This event denotes an MDL source code issue and is informational only.	0	No user action is required. The Cisco TAC might use this information in troubleshooting call-processing problems.
CPM: Leg1chanSeizedUnpackError	Some fault in data received from the engine.	Information	Y	This event denotes an MDL source code issue and is informational only.	0	No user action is required. The Cisco TAC might use this information in troubleshooting call-processing problems.
CPM: Leg1ConfigError	Inconsistent VirtualSwitch and oConPlaneCtrl.	Information	Y	This event denotes an MDL source code issue and is informational only.	0	No user action is required. The Cisco TAC might use this information in troubleshooting call-processing problems.
CPM: Leg1CotStateError	Requested action is incompatible with CPM COT4 state.	Information	Y	This event denotes an MDL source code issue and is informational only.	0	No user action is required. The Cisco TAC might use this information in troubleshooting call-processing problems
CPM: Leg1DeleteChanPack Error	Some required call context data was not available.	Information	Y	This event denotes an MDL source code issue and is informational only.	0	No user action is required. The Cisco TAC might use this information in troubleshooting call-processing problems.
CPM: Leg1ExtCOTPropError	Prop is neither loop nor transponder.	Information	Y	This event denotes an MDL source code issue and is informational only.	0	No user action is required. The Cisco TAC might use this information in troubleshooting call-processing problems.
CPM: Leg1ModifyChanPack Error	Required call context data was not available.	Information	Y	This event denotes an MDL source code issue and is informational only. .	0	No user action is required. The Cisco TAC might use this information in troubleshooting call-processing problems
CPM: Leg1RMXmitCotError	RMXmitCot returned false.	Information	Y	This event denotes an MDL source code issue and is informational only.	0	No user action is required. The Cisco TAC might use this information in troubleshooting call-processing problems.
CPM: Leg1SeizeChanPack Error	Some required call context data was not available.	Information	Y	This event denotes an MDL source code issue and is informational only.	0	No user action is required. The Cisco TAC might use this information in troubleshooting call-processing problems.
CPM: Leg1StateError	Requested action is incompatible with CPM leg state.	Information	Y	This event denotes an MDL source code issue and is informational only.	0	No user action is required. The Cisco TAC might use this information in troubleshooting call-processing problems.
CPM: Leg1Timeout	No response received from the engine.	Information	Y	This event denotes an MDL source code issue and is informational only.	0	No user action is required. The Cisco TAC might use this information in troubleshooting call-processing problems.
CPM: Leg2chanDeleted UnpackError	Some fault in data received from the engine.	Information	Y	This event denotes an MDL source code issue and is informational only.	0	No user action is required. The Cisco TAC might use this information in troubleshooting call-processing problems.
CPM: Leg2chanFailed	A resource failure in the engine.	Information	Y	This event denotes an MDL source code issue and is informational only.	0	No user action is required. The Cisco TAC might use this information in troubleshooting call-processing problems.
CPM: Leg2chanModified UnpackError	Some fault in data received from the engine.	Information	Y	This event denotes an MDL source code issue and is informational only.	0	No user action is required. The Cisco TAC might use this information in troubleshooting call-processing problems.
CPM: Leg2chanOpFailed	A resource failure in the engine.	Information	Y	This event denotes an MDL source code issue and is informational only.	0	No user action is required. The Cisco TAC might use this information in troubleshooting call-processing problems.
CPM: Leg2chanSeizedUnpackError	Some fault in data received from the engine.	Information	Y	This event denotes an MDL source code issue and is informational only.	0	No user action is required. The Cisco TAC might use this information in troubleshooting call-processing problems.
CPM: Leg2ConfigError	Inconsistent VirtualSwitch and tConPlaneCtrl.	Information	Y	This event denotes an MDL source code issue and is informational only.	0	No user action is required. The Cisco TAC might use this information in troubleshooting call-processing problems.
CPM: Leg2CotStateError	Requested action is incompatible with CPM COT state.	Information	Y	This event denotes an MDL source code issue and is informational only	0	No user action is required. The Cisco TAC might use this information in troubleshooting call-processing problems.
CPM: Leg2DeleteChanPack Error	Some required call context data was not available.	Information	Y	This event denotes an MDL source code issue and is informational only.	0	No user action is required. The Cisco TAC might use this information in troubleshooting call-processing problems
CPM: Leg2ExtCOTPropError	Prop is neither loop nor transponder.	Information	Y	This event denotes an MDL source code issue and is informational only.	0	No user action is required. The Cisco TAC might use this information in troubleshooting call-processing problems.
CPM: Leg2ModifyChanPack Error	Some required call context data was not available.	Information	Y	This event denotes an MDL source code issue and is informational only.	0	No user action is required. The Cisco TAC might use this information in troubleshooting call-processing problems.
CPM: Leg2RMXmitCotError	RMXmitCot returned false.	Information	Y	This event denotes an MDL source code issue and is informational only.	0	No user action is required. The Cisco TAC might use this information in troubleshooting call-processing problems.
CPM: Leg2SeizeChanPack Error	Some required call context data was not available.	Information	Y	This event denotes an MDL source code issue and is informational only.	0	No user action is required. The Cisco TAC might use this information in troubleshooting call-processing problems.
CPM: Leg2SeizeConnection PackError	Some required call context data was not available.	Information	Y	This event denotes an MDL source code issue and is informational only.	0	No user action is required. The Cisco TAC might use this information in troubleshooting call-processing problems.
CPM: Leg2StateError	Requested action is incompatible with CPM leg state.	Information	Y	This event denotes an MDL source code issue and is informational only.	0	No user action is required. The Cisco TAC might use this information in troubleshooting call-processing problems.
CPM: Leg2Timeout	No response received from the engine.	Information	Y	This event denotes an MDL source code issue and is informational only.	0	No user action is required. The Cisco TAC might use this information in troubleshooting call-processing problems.
CPM: NotifyUnexpected	An unsolicited chanNotify has been received.	Information	Y	This event denotes an MDL source code issue and is informational only.	0	No user action is required. The Cisco TAC might use this information in troubleshooting call-processing problems.
CPM: UnknownLeg	LCM has requested action, not Leg1 or Leg2.	Information	Y	This event denotes an MDL source code issue and is informational only.	0	No user action is required. The Cisco TAC might use this information in troubleshooting call-processing problems.
CPM: UnknownNotifyType	ISDN User Part T28 has expired.	Information	Y	This event denotes that a chanNotify message with unknown notify type has been received.	0	No user action is required. The Cisco TAC might use this information in troubleshooting call-processing problems.
CRITICAL M-OOS	Critical process manually out of service.	Major	Y	This alarm denotes that a software process critical to normal system operation has been requested manually out of service.	3	Return the process to the in service state.
DISK	Low disk space.	Major	Y	This alarm denotes that the system disk is running out of space.	4	Remove unnecessary cdr, alm, meas. and logs from $BASEDIR/var/log spool.
EQPT M-OOS	Equipment manually out of service.	Major	Y	This alarm denotes athat a card or shelf has been requested manually out of service.	4	Restore the equipment to service using the user interface.
Ext Node Interface Fail	SRCP link failure.	Major	Y	This alarm is generated when an SRCP session loses heartbeats with the remote gateway, indicating that the link to the gateway is down.	1	Check Ethernet, check network connectivity, check if remote gateway associated with this link is still alive, and check if the near-end and far-end SRCP sessions are operating normally.
FAIL	Non-specific failure.	Minor	Y	This indicates that the component referenced in the alarm has failed. The failure may be service affecting, in which case other alarms will be raised.	3	The corrective action depends on the component type. For hardware, reboot or replace the failed component. For software, run diagData and contact the Cisco TAC.
FailoverPeerLost	Lost communication with failover peer.	Major	Y	This alarm indicates that the peer failover daemon is not reachable.	3	Check the Ethernet cable, check that the peer failover daemon is up and running, and check whether the peer system is reachable through the IP links.
FailoverPeerOOS	Failover peer is out of service.	Major	Y	This alarm is raised when the peer foverd goes to OOS.	3	Check the peer system concerning what caused this alarm.
FailoverToInit	Failover daemon is in initializing state.	Information	Y	This event denotes that a failover daemon is initializing.	3	This is an informational alarm only. No user action is required.
FailoverToMaster	Failover daemon is in the active state.	Information	Y	This event denotes that a failover daemon is in the active state.	3	This is an informational alarm only. No user action is required.
FailoverToOOS	Failover daemon is out of service.	Major	Y	A critical alarm has occurred in the system due to : 1. Not receiving a response from the process manager. 2. Going to the OOS state.	3	Check the process that caused the critical alarm.
FailoverToSlave	Failover daemon is in standby state.	Information	Y	This event denotes that a failover daemon is in standby state.	3	This is an informational alarm only. No user action is required.
Fan Failure	Fan failure.	Critical	Y	This event denotes that there has been a fan failure.	4	Replace fan.
Gateway Trunk Held	Gateway Trunk held without associated call	Information	Y	This event is caused when a gateway trunk has been held even though there is no associated call.	3	No action required. The application clears itself through an automatical audit.
GEN FAIL	General process failure.	Information	Y	There has been a failure caused by resource exhaustion or configuration problems, including: Memory exhaustion Queue overflow Message congestion IPC file cannot be opened A timer has expired	3	Check the log for more information.
IP Connection Failed	IP connection to the Cisco SLT5 failed.	Major	Y	This event is triggered when the Cisco MGC 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 signal channel (SS7 link) that has gone A-OOS because of the loss of IP connectivity. The most likely causes of this alarm are: Ethernet cable pulled from the Cisco SLT or Cisco MGC Problem in IP network between teh Cisco SLT and Cisco MGC The Cisco SLT powered down A Cisco SLT software bug A Cisco MGC software bug in the IP network stack or RUDP	1	Check SLT status. If all SLTs are down, reboot them to restore service. Check Ethernet cable and hubs and fix or replace if faulty. If SLTs are still down, contact the Cisco TAC.
ISUP: ABNORM CGBA	ISDN User Part CGBA6 received with nonmatching range or status.	Information	Y	This event indicates that the range and status received in a CGBA message do not match the range and status sent in the CGB.7	1	For more information, refer to the appropriate specification for the protocol concerned.
ISUP: ABNORM CGUA	ISDN User Part CGUA8 received with nonmatching range or status.	Information	Y	This event indicates that the range and status received in a CGUA message do not match the range and status sent in the CGU.9	1	For more information, refer to the appropriate specification for the protocol concerned.
ISUP: ABNORM CQR	ISDN User Part CQR received with nonmatching CQM range.	Information	Y	This event indicates that the range and status received in a CQR message do not match the range and status sent in the CQM	1	For more information, refer to the appropriate specification for the protocol concerned.
ISUP: CGB Processed	Indicates a CGB request has been processed from far-end.	Information	Y	This event is to indicate that the far-end switch has blocked a range of CICs.	1	No action required. But for more information, refer to the appropriate specification for the protocol concerned.
ISUP: COT FAILURE	ISDN User Part initial and subsequent COT failed.	Information	Y	This event occurs when a COT message was received indicating a failed continuity test.	1	Check for continuity, using a manual COT test. Refer to "MML Command Reference,"TST-COTManual COT.
ISUP: FE Parameter Drop	ISDN User Part incoming FE Parameter dropped.	Information	Y	An incoming FE in a backward message has been dropped according to the terminating message map (rule 1).	0	For more information, refer to the appropriate specification for the protocol concerned.
ISUP: T13 Expired	ISDN User Part T13 has expired.	Information	Y	Raised when a blocking message has been sent and the T13 timer has expired because no blocking acknowledgment message was received in response.	0	For more information, refer to the appropriate specification for the protocol concerned.
ISUP: T15 Expired	ISDN User Part T15 has expired.	Information	Y	Raised when an unblocking message has been sent and the T15 timer has expired because no unblocking acknowledgment message was received in response.	0	For more information, refer to the appropriate specification for the protocol concerned.
ISUP: T17 Expired	ISDN User Part T17 has expired.	Information	Y	Raised when a reset unavailable message has been sent and the T17 timer has expired because no acknowledgment message was received.	0	For more information, refer to the appropriate specification for the protocol concerned.
ISUP: T19 Expired	ISDN User Part T19 has expired.	Information	Y	Raised when a group blocking message is sent and the T19 timer has expired because no group blocking acknowledgment message was received.	0	For more information, refer to the appropriate specification for the protocol concerned.
ISUP: T21 Expired	ISDN User Part T21 has expired.	Information	Y	Raised when a group unblocking message has been sent and the T21 timer has expired because no group unblocking acknowledgment message was received.	0	For more information, refer to the appropriate specification for the protocol concerned.
ISUP: T23 Expired	ISDN User Part T23 has expired.	Information	Y	Raised when a group reset message was sent and the T23 timer has expired because no acknowledgment message was received.	0	For more information, refer to the appropriate specification for the protocol concerned.
ISUP: T28 Expired	ISDN User Part T28 has expired.	Information	Y	This event is raised when a circuit query message was sent and T28 expires because no circuit query response message has been received in reponse.	0	For more information, refer to the appropriate specification for the protocol concerned.
ISUP: T5 Expired	ISDN User Part T5 has expired.	Information	Y	Raised when a release message was sent and the T5 timer has expired because no release complete message was received.	0	For more information, refer to the appropriate specification for the protocol concerned.
ISUP: TCVT Expired	ISDN User Part CVT10 timer expired twice.	Information	Y	When a 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, an alarm will be raised.	0	For more information, refer to the appropriate specification for the protocol concerned.
ISUP: UNEQUIPPED CIC	ISDN User Part message received on unequipped CIC.11	Information	Y	Raised when a message is received on an unequipped CIC.	1	For more information, refer to the appropriate specification for the protocol concerned.
ISUP: UNEX ACM	ISDN User Part unexpected ACM.	Information	Y	Raised when an ACM message has been received and an ACM/ANM message has already been sent.	1	For more information, refer to the appropriate specification for the protocol concerned.
ISUP: UNEX ANM	ISDN User Part unexpected ANM.	Information	Y	Raised when an ANM message has been received and an ACM/ANM message has already been sent.	1	For more information, refer to the appropriate specification for the protocol concerned.
ISUP: UNEX BLA	ISDN User Part BLA received with local status unblocked.	Information	Y	Raised when a BLA message has been received and the local status is unblocked.	1	For more information, refer to the appropriate specification for the protocol concerned.
ISUP: UNEX CGBA	ISDN User Part CGBA received with local status blocked.	Information	Y	Raised when a CBGA message is received and local status is already unblocked.	1	For more information, refer to the appropriate specification for the protocol concerned.
ISUP: UNEX CGUA	ISDN User Part CGUA received with local status unblocked.	Information	Y	Raised when a CGUA message has been received and local status is blocked.	1	For more information, refer to the appropriate specification for the protocol concerned.
ISUP: UNEX UBA	ISDN User Part UBA received with local status unblocked.	Information	Y	Raised when a UBA message has been received and the local status is blocked.	1	For more information, refer to the appropriate specification for the protocol concerned.
ISUP: UNMATCHED STATUS	Circuit Grp Blocking (Unblocking) Ack status unmatched	Information	Y	Raised when the circuit group blocking/ unblocking and Ack status are not matching.	1	For more information, refer to the appropriate specification for the protocol concerned.
LIF BER	Excessive bit error ratio detected from frame alignment signal	Information	Y	This might be caused by any source of electrical noise; for example, degraded transmission line, degraded line connectors, high-voltage electrical source located in proximity of line.	1	Isolate the source by testing connections and testing the transmission line.
LIF FAIL	Line interface failure.	Major	Y	The LIF12 has failed. All physical lines to the Cisco MGC can raise this alarm.	4	Review provisioning parameters for line interface and make sure that the configurations are supported by the equipment. Remove equipment from service using MML, reprovision, and restore it to service. If the problem persists, run diagData and contact the Cisco TAC.
LIF LOF	Line interface loss of framing.	Major	Y	A loss of T1/E1 framing has been detected on the LIF. The physical line has signal but has lost framing pattern.	1	Check near-end and far-end terminations to determine if they are sending a framed signal. Perform loopbacks to isolate cause of frame loss.
LIF LOS	Line interface loss of signal.	Major	Y	The transmitted signal is lost in the T1/E1. The receiving end does not receive the signal. The physical line might have a break in it.	1	Check the physical terminations and cabling.
LIF SES 15	Line TCA session---15 minutes.	Information	Y	The severely errored seconds measurement counter has exceeded the threshold value set in the thresholds.dat table for the last 15-min. period. The channel remains in an In-Service state.	0	This event is informational and does not require an immediate response; however, the condition should be monitored closely to ensure that the service level does not degrade further.
LIF SES 60	Line TCA session---60 minutes.	Information	Y	The severely errored seconds measurement counter has exceeded the threshold value set in the thresholds.dat table for the last 60-min. period. The channel remains in an In-Service state.	0	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.
LIF SES 24	Line TCA session---24 hours.	Information	Y	The severely errored seconds measurement counter has exceeded the threshold value set in the thresholds.dat table for the last 24-hour period. The channel remains in an In-Service state.	0	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.
LIF SES	Line automatically set to out of service because of severely errored seconds.	Major	Y	The TDM line has a large amount of noise, causing an error rate greater than 10-3. Framing and signal are within tolerance. This indicates a degraded but functioning line.	1	Check terminations and cabling.
LIF YELLOW	Far-end line failed.	Minor	Y	The receiving end is reporting a loss of the transmitted signal. This is reported for T1/E1 facilities only.	4	Check the far-end termination and fix it. The far-end termination should go into trunk condition when reporting a yellow alarm.
LIF: IDLE CHANGE	Line idle change.	Minor	Y	The physical line has failed because its cable is broken or not plugged in. This is reported for V.35 facilities only.	0	Check V.35 cables and the far end for a valid signal.
LIF: LOST CD	Line loss of carrier-detect.	Major	Y	The physical line has failed because its cable is broken or not plugged in. This is reported for V.35 facilities only.	0	Check V.35 cables and the far end for a valid signal.
LIF: LOST CTS	Line loss of clear-to-send.	Major	Y	The physical line has failed because its cable is broken or not plugged in. This is reported for V.35 facilities only.	0	Check V.35 cables and the far end for a valid signal.
Location-CONFIGURE-FAILED	Location configure failed.	Major	Y	CMS failed to bring FRU online. This alarm is valid for the Sun Netra ft 1800 only.	4	Replace the unit using proper replacement procedures.
Location-DEGRADE	Location degraded.	Major	Y	Fault is detected on an FRU; it is providing service at a degraded level.This alarm is valid for the Sun Netra ft 1800 only. No other Netra platforms generate this alarm.	4	Return this or supporting unit to In-Service state using the management interface. If this does not work, replace the unit that is the source of the alarm.
Location-FAILURE	Location failed.	Major	Y	This alarm is generated when a hardware FRU has failed. This alarm is valid for the Sun Netra ft 1800 only. No other Netra platforms generate this alarm.	4	Replace unit using proper replacement procedures. FRUs are hot-swappable.
Location-INSERTED	Location inserted.	Minor	Y	This event is an initial registration of a hardware module in the chassis.	4	This is an indication that a circuit unit has been inserted properly in its slot. This is for informational purposes only.
LOG	Log file open or write error.	Major	Y	A log file is either open or in error.	3	Check the platform log.
MAJOR M-OOS	Required process manually out of service.	Major	Y	A software process necessary for normal system operation has been requested manually out of service.	3	Restore the process to In-Service state using the user interface.
M-OOS	Resource has been manually taken OOS	Minor	Y	A software process not necessary for normal system operation has been requested manually out of service.	1	Restore the process to In-Service state using the user interface.
ManualSwitchOver	A user has initiated a manual switchover.	Critical	Y	A user using MML has issued a command to switch over the Cisco MGC. This will happen on the active system only.	3	The alarm will clear once the switchover has completed.
MDL BLKLST 15	15-min. blacklist threshold exceeded.	Minor	Y	More than 10 calls have been blacklisted within fifteen minutes.	3	The alarm will clear automatically when the number of blacklisted calls drops below eight. Be alert for a potential hacker into the system.
MDL BLKLST 60	60-min. blacklist threshold exceeded.	Minor	Y	More than 30 calls have been blacklisted within sixty minutes.	3	The alarm will clear automatically when the number of blacklisted calls drops below 24. Be alert for a potential hacker into the system.
MDL BLKLST 24	24-hour. blacklist threshold exceeded.	Minor	Y	More than 200 calls have been blacklisted within fifteen minutes.	3	The alarm will clear automatically when the number of blacklisted calls drops below 160. Be alert for a potential hacker into the system.
MINOR M-OOS	Non-required process manually out of service.	Minor	Y	A software process that is not necessary for normal system operation has been requested manually out of service.	3	The alarm will clear with the process is restored in service.
MMDB: Database unavailable	Main memory database is unavailable.	Major	Y	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.	3	Check the database logs. Check unnecessary disk space used. Refer to the Disk alarm suggested action. If condition persists, contact the Cisco TAC.
MMDB: Database cause failover	Main memory database is unavailable, indicating a failure to occur.	Critical	Y	The main memory database is currently unavailable on a redundant system and is indicating that the system should failover. Recovery is attempted and the alarm clears when or if the database becomes available.	3	Once failures occurs, check if the alarm has cleared on the standby machine. Check unnecessary disk space used. Refer to the Disk alarm suggested action. If condition persistss, contact the Cisco TAC.
MMDB: Database nearly full	Main memory database is nearly full.	Major	Y	The main memory database has detected that allocated resources for data storage are nearly all utilized.	3	Check the database logs. Check unnecessary disk space used. Refer to the Disk alarm suggested action. If condition persistss, contact the Cisco TAC.
MGW: AuditResponse Failure	MGW13 failed to send RESYNC RESP back within the audit time interval.	Information	Y	MGW failed to send RESYNC RESP back within the audit time interval.	3	Use the MML commands RTRV-SC and RTRV-DEST to ensure that the media gateway is In-Service (IS). If it is IS, check the MGW's configuration; if it is OOS, check IP connectivity.
MGW: CommsFailure	MGW communication failure.	Information	Y	The Cisco MGC cannot communicate with the MGW. The MGW failed to acknowledge message within 2 seconds.	1	Check if the MGW is operational. If it is, check IP parameters on both the MGC and MGW.
MGW: ResourceFailure	Received "not acknowledged" message from MGW.	Information	Y	Continuity has not been acknowledged by the MGW.	3	Check MGW reporting of NAK on COT requests for resource issues or other issues.
OOS TRAFFIC RE-ROUTE	Traffic rerouted by far-end network element.	Minor	Y	Traffic channels (bearer channels, IP network) on one side of the Cisco MGC have been lost, causing the Cisco MGC to reroute channels away from the alarmed entity. This is generally due to a network or equipment failure but might be due to a provisioning failure.	0	Isolate the root cause of the alarm by checking other alarms and the configuration. Possibilities include local hardware failure or associated path failure. If the problem persists, run diagData and contact the Cisco TAC immediately.
OS	Operating system failure.	Information	Y	Something in the operating system has stopped functioning.	3	Run diagData and contact the Cisco TAC immediately.
OverloadHeavy	Overload heavy condition exists.	Critical	Y	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.	4	If caused by a rare spike, this might be normal. If this is caused by too much traffic for the SCs, perform load-balancing procedures; route some traffic to other SCs. If due to overload alarm levels set too low, raise the level. (Refer to the RTRV-OVLD MML command in "MML Command Reference.")
OverloadMedium	Overload medium condition exists.	Major	Y	The engine has reached a light 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 standby server.	4	If caused by a rare spike, this might be normal. If this is caused by too much traffic for the SCs, perform load-balancing procedures; route some traffic to other SCs. If due to overload alarm levels set too low, raise the level. (Refer to the RTRV-OVLD MML command in "MML Command Reference.")
OverloadLight	Overload light condition exists.	Minor	Y	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.	4	If caused by a rare spike, this might be normal. If this is caused by too much traffic for the SCs, perform load-balancing procedures; route some traffic to other SCs. If due to overload alarm levels set too low, raise the level. (Refer to the RTRV-OVLD MML command in "MML Command Reference.")
Peer IP Links Failure	IP links to peer VSC failed	Major	Y	This alarm is generated when the IP) links to the peer system are removed or down.	3	Check Ethernet cables to the Peer system, and check whether IP links are up and running.
PC UNAVAIL	Point code unavailable.	Major	Y	The destination point code (DPC) is unavailable. This can be due to a network failure causing the DPC to become isolated, a local failure equipment failure causing a loss of connectivity, or a local provisioning failure causing the DPC or routes to it to be configured improperly.	1	Check alarms to isolate the cause to equipment, SS7 links, or network failure (that is, transfer prohibited). Review provisioning data to the DPC to make sure that the point code parameters are correct and in agreement with how the DPC is configured. Review provisioning data for all routes to the DPC and adjacent STPs. Fix provisioning and retry. If still not active, run diagData and contact the Cisco TAC.
PEER LINK A FAILURE	Fail to communicate with peer module over link A	Minor	Y	This alarm is caused either by loss of communication path between peer modules or the peer module has stopped communicating	1	Use Trace Route and MML commands to determine where and which links and modules are down.
PEER LINK B FAILURE	Fail to communicate with peer module over link B	Minor	Y	This alarm is caused either by loss of communication path between peer modules or the peer module has stopped communicating	1	Use Trace Route and MML commands to determine where and which links and modules are down.
PEER MODULE FAILURE	Fail to communicate with peer module over configured links.	Major	Y	This alarm is by loss of communication indicating failure of the peer module.	1	Use Trace Route and MML commands to determine where and which modules or links are down.
POM INACTIVITY TIMEOUT	Alarm Indication Inactivity timeout.	Information	Y	This alarm indicates that the current provisioning session had been idling for 20 minutes without receiving any provisioning commands. If there is still no provisioning activity within the next five minutes, the session will be terminated.	3	Perform provisioning commands or stop the session.
POM SESSION TERMINATE	Alarm Indication Provisioning session has terminated.	Information	Y	This alarm is sent to indicate that the provisioning session is teminated. No further provisioning command will be accepted.	3	Re-open the provisioning session, with the same srcver set equal to the dstver name.
POM: DynamicReconfiguration	Provisioning: Dynamic Reconfiguration	Minor	Y	At the start of the dynamic reconfiguration procedure, this alarm is set; and it is cleared once the dynamic reconfiguration is successfully completed.	3	If necessary, use the MML command CLR-ALM to clear the alarm or the MML command PROV-SYNC command on the active VSC.
PROCM M-OOS	Process manager manually out of service.	Critical	Y	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.	3	Retore the process manager in service.
ProcM No Response	Process manager not responding to messages sent by failover daemon.	Major	Y	The process manager is not responding to state information changes from the failover daemon.	3	Check if some process NAK'ed to procM's platform state cmd as a result of which procM failed to respond to foverd.
PS A Failure	Power supply A failure.	Minor	Y	Power supply A has failed.	4	Replace power supply.
PS B Failure	Power supply B failure.	Minor	Y	Power supply B has failed.	4	Replace power supply.
REPL: all connections failure	Replicator: All links to peer VSC failed	Critical	Y	This alarm is generated when the Cisco MGC Replication Service cannot establish communication to peer.	0	Check Ethernet, check Replicator configuration on active and standby MGC.
RSET CONFIG FAIL	Reset configuration failed.	Information	Y	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.	3	Check provisioning data for the DPC and all routes to it. Correct discrepancies.
SC CONFIG FAIL	Signal channel configuration failure.	Major	Y	Provisioning parameters for the data link layer of a signal 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.	1	Remove the signal channel, review local configuration parameters, and reprovision the channel.
SC FAIL	Signal channel failure.	Major	Y	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 occurs when SS7 SLTM / SLTA fails or when PRI d-channel fails.	1	Check near-end and far-end data link terminations to make sure they are operational. Confirm that ends agree on communication parameters.
SC M-OOS	Signal channel has been manually taken out of service.	Minor	Y	The signal channel has been manually taken out of service by an operator on the platform.	1	Restore the signal channel to In-Service state using the user interface.
SCCP CONFIG FAIL	SCCP14 configuration failed.	Major	Y	The SCCP trillium stack could not be initialized due to internal software problems.	3	Collect the inforation from the log files and call the Cisco TAC.
SCCP MTP3 COMM FAIL	SCCP-MTP315 communication failure.	Major	Y	Communication between the SS7 channel controller and the TCAP process could not be established.	1	Ignore this alarm if you have not configured IN services (like LNP, and toll-free calls), Otherwise, use the RTRV-SOFTW MML command to start these processes if they are not running. If they are running, use the commands stp-softw: TCAP-01:Kill, and sta-softw:TCAP-01 to stop and restart them. Notify the Cisco TAC.
SOFTW NON	Nonrequired process failure.	Minor	Y	This alarm indicates that 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 a nonrequired software might reduce the reliability or performance of the system.	3	Stop and start the process using the user interface. Run diagData and contact the Cisco TAC.
SOFTW REQ	Required process failure.	Major	Y	This alarm indicates that a required process cannot be started or continues to fail when started. The process provides a necessary service on the Cisco MGC that is not related to call processing.	3	Run diagData and contact the Cisco TAC immediately.
srcpAudit: GwBackhaulProto	AUDIT GW FAIL- partition backhaul protocol mismatch.	Major	Y	The backhaul protocol is different from what the Cisco MGC expects. A mismatch here might cause minimal, partial, or complete signaling/call-control failure.	0	This field is expected to be "none." Verify that the SRCP heartbeat is working (Is gateway OK?). If so, check the gateway configuration.
srcpAudit: GwBackhaulSes	AUDIT GW FAIL- partition number of backhaul sessions mismatch.	Minor	Y	The number of backhaul sessions is different from what the Cisco MGC expects. Some signaling information might be lost, leading to lost or failed calls.	0	This file is derived from the configuration files. Verify that the SRCP heartbeat is working (is gateway OK?). If so, check the gateway configuration. Each backhaul session to the same IP address as the SRCP counts as 1.
srcpAudit: GwControlProto	AUDIT GW FAIL- partition control protocol mismatch.	Major	Y	The control protocol is different from what the Cisco MGC expects. A mismatch here might cause minimal, partial, or complete signaling failure.	0	This field is expected to be "MGCP". Verify that the SRCP is working (is gateway OK?). If so, check the gateway configuration.
srcpAudit: GwCoordProto	AUDIT GW FAIL- partition coordination protocol mismatch.	Minor	Y	The cooordination protocol is different from what the Cisco MGC expects. A mismatch here might cause alarms to be raised erroneously.	0	This field is expected to be "SCRP 1.0" Verify that the SRCP heartbeat is working (is gateway OK?) If so, check the gateway configuration.
srcpAudit: GwCuIpAddr	AUDIT GW FAIL- partition CU IP. address mismatch.	Major	Y	The IP address of the gateway (CU) reported by the gateway is different from that configured in the Cisco MGC. This can lead to a comm failure by the control protocol.	0	This field is derived froma configuratio0n file. Verify the SRCP heartbeat is working (is gateway OK?). If so, check the gateway configuration. The field should be the remote IP address entry for the signal channel path.
srcpAudit: GwCuIpPort	AUDIT GW FAIL- partition CU IP port mismatch.	Major	Y	The IP port of the gateway (CU) reported by the gateway is different from that configured in the Cisco MGC. This can lead to a comm failure by the control protocol.	0	This is derived from a configuration file. Verify that the SRCP heartbeat is working (is gateway OK?). If so, check the gateway configuration. This field should be the remote port entry for this signal channel or signal path
srcpAudit: GwNumOfLines	AUDIT GW FAIL- partition number of lines mismatch.	Major	Y	The number of lines in the gateway partition is different from what the Cisco MGC expects. This may affect service if a call are made on nonexistent lines. Another error should be raised elsewhere in the system if a call is placed to a nonexistent line	0	This is derived from a configuration file. Verify that the SRCP heartbeat is working (is gateway OK?). If so, check the gateway configuration. This field should be the total number of bearer lines associated with this signal path.
srcpAudit: GwSlotNum	AUDIT GW FAIL- partition slot number mismatch.	Information	Y	The hardware for the gateway is in a different slot than the Cisco MGC expects. This should not affect service but might be an issue in hardware troubleshooting.	0	This field is expected to be "0". Verify the SRCP heartbeat is working (is gateway OK?). If so, check the gateway configuration.
srcpAudit: GwSulpAddr	AUDIT GW FAIL- partition SU IP address mismatch.	Major	Y	The IP address of the call agent (SU or MGC) reported by the gateway is different from that configured in the Cisco MGC. This can lead to a comm failure by the control protocol.	0	This field is derived from a configuration file. Verify that the SRCP heatbeat is working (is gateway OK?). If so, check the gateway configuration. This field should be the local IP address entry for this signal channel/path. The field should be one of the four local IP addresses on the Cisco MGC.
srcpAudit: GwSulpPort	AUDIT GW FAIL- partition SU IP port mismatch.	Major	Y	The IP portof the call agent (SU or MGC) reported by the gateway is different from that configured in the Cisco MGC. This can lead to a comm failure by the control protocol.	0	This field is derived from a configuration file. Verify that the SRCP heartbeat is working (is gateway OK ?). If so, check the gateway configuration. The field should be the local port entry for this signal channel/path
srcpAudit: GwType	AUDIT GW FAIL- partition type mismatch.	Minor	Y	The gateway is of a different type than the Cisco MGC expects. This may or may not affect service depending on whether the Cisco MGC has gateway-specific coding	0	This field is expected to be "VISM". Verify that the SRCP heartbeat is working (is gateway OK ?). If so, check the gateway configuration.
srcpAudit: LineCoding	AUDIT LINE FAIL- Line signaling protocol mismatch.	Minor	Y	The line coding used by the gateway for that line is different from that configured in the Cisco MGC for that line. This might lead to corrupted data on the B channels.	0	This field is expected to be "Unknown". Verify the SRCP heartbeat is working (is gateway OK ?). If so, check the gateway configuration.
srcpAudit: LineLoopback	AUDIT LINE FAIL- line loopback state mismatch.	Minor	Y	The line loopback for that line used by the gateway is different from that configured in the Cisco MGC for that line. A line may be in a loopback state when the Cisco MGC believes it is available.	0	This field is expected to be "n". Verify that the SRCP heartbeat is working (is gateway OK ?). If so, check the gateway configuration.
srcpAudit: LineSigProto	AUDIT LINE FAIL- line coding mismatch.	Major	Y	The signaling protocol used by the gateway for that line is different from that configured in the Cisco MGC for that line. Some signaling information might be lost, leading to lost or failed calls.	0	This field is derived from a configuration file. Verify that the SRCP heartbeat is working (is gateway OK ?). If so, check the gateway configuration. The field should be the signaling type associated with the backhaul signaling to the same remote IP address as the SRCP for this signaling channel.
srcpAudit: LineState	AUDIT LINE FAIL- line state mismatch.	Minor	Y	The line state for the line used by the gateway is different from that configured in the Cisco MGC for that line. A line might be disabled by the gateway when the Cisco MGC believes it is available.	0	This field is expected to be "e". Verify the SRCP heartbeat is working (is gateway OK ?). If so, check the gateway configuration.
SSN FAIL	IN SSN16 failed.	Major	Y	The SCP located by subsystem number is not available.	1	Check the local configuration to confirm the SSN and that the routes are valid. Check the network configuraion to confirm that the SCP identified with the SSN is reachable.
Standby Warm Start	Warm start initiated.	Minor	Y	Warm start initiated.	3	No action required.
SUPPORT FAILED	Support entity failed.	Minor	Y	The entity cannot provide service because a supporting entity is not providing service. The supporting entity may be hardware, for example a disk or line card. It may be software, for example an application process.	3	Check alarms to determine the root cause of the failure. Replace entity and restore it to service. Check to see if alarms clear. If not, run diagData and contact Cisco TAC.
SW FAIL	Software failure; check log.	Information	Y	Failure caused by software logic problems, such as: Unknown message received Process in undesirable state Unexpected logic being executed (for example, conditional code that should never be executed is being executed) Some timer expirations	3	Run diagData and contact Cisco TAC immediately.
SwitchoverFail	Failure to switch network interfaces to active system.	Major	Y	Failover from the active to standby server has failed.	3	Check the log.
TCAP CONFIG FAIL	TCAP17 configuration failed.	Major	Y	The TCAP trillium stack could not be initialized because of internal software problems.	3	Collect the information from the log files and call the Cisco TAC.
TCAP ENGINE COMM FAIL	TCAP-Engine communication failure	Major	Y	The TCAP engine communication failed.	1	Collect the information from the log files and call the Cisco TAC.
TCAP RESOURCE LIMITATION	TCAP resource limitation.	Major	Y	The TCAP trillium stack could not be initialized because of memory allocation errors.	2	Call the Cisco TAC.
TUP: ABNORM HBA	TELEPHONE User Part HBA received range and status mis-match	Information	Y	This event is caused by an invalid status mismatch.	0	For more information, refer to the appropriate specification for the protocol concerned.
TUP: ABNORM HUA	TELEPHONE User Part HUA received range and status mis-match	Information	Y	This event is caused by an invalid status mismatch.	0	For more information, refer to the appropriate specification for the protocol concerned.
TUP: ABNORM MBA	TELEPHONE User Part MBA received range and status mis-match	Information	Y	This event is caused by an invalid status mismatch.	0	For more information, refer to the appropriate specification for the protocol concerned.
TUP: ABNORM MUA	TELEPHONE User Part MUA received range and status mis-match	Information	Y	This event is caused by an invalid status mismatch.	0	For more information, refer to the appropriate specification for the protocol concerned.
TUP: ABNORM SBA	TELEPHONE User Part SBA received range and status mis-match	Information	Y	This event is caused by an invalid status mismatch.	0	For more information, refer to the appropriate specification for the protocol concerned.
TUP: ABNORM SUA	TELEPHONE User Part SUA received range and status mis-match	Information	Y	This event is caused by an invalid status mismatch.	0	For more information, refer to the appropriate specification for the protocol concerned.
TUP: COT FAILURE	TELEPHONE User Part Initial and subsequent COT failed	Information	Y	Continuity testing has failed on this call.	0	For more information, refer to the appropriate specification for the protocol concerned.
TUP: GROUPBLOCK HW	TELEPHONE User Part Hardware Group blocking request actioned	Information	Y	Hardware group block has been requested and has been actioned.	0	For more information, refer to the appropriate specification for the protocol concerned.
TUP: GROUPBLOCK SW	TELEPHONE User Part Software Group blocking request actioned	Information	Y	Software group block has been requested and has been actioned.	0	For more information, refer to the appropriate specification for the protocol concerned.
TUP: T13 Expired	TELEPHONE User Part T13 has expired	Information	Y	Time T13 has expired	0	For more information, refer to the appropriate specification for the protocol concerned.
TUP: T16 Expired	TELEPHONE User Part T16 has expired	Information	Y	Time T16 has expired.	0	For more information, refer to the appropriate specification for the protocol concerned.
TUP: T19 Expired	TELEPHONE User Part T19 has expired	Information	Y	Time T19 has expired.	0	For more information, refer to the appropriate specification for the protocol concerned.
TUP: T22 Expired	TELEPHONE User Part T22 has expired	Information	Y	Timer T22 has expired.	0	For more information, refer to the appropriate specification for the protocol concerned.
TUP: T27 Expired	TELEPHONE User Part T27 has expired	Information	Y	Time T27 has expired.	0	For more information, refer to the appropriate specification for the protocol concerned.
TUP: T29 Expired	TELEPHONE User Part T29 has expired	Information	Y	Timer T29 has expired.	0	For more information, refer to the appropriate specification for the protocol concerned.
TUP: T33 Expired	TELEPHONE User Part T33 has expired	Information	Y	Timer T33 has expired.	0	For more information, refer to the appropriate specification for the protocol concerned.
TUP: T35 Expired	TELEPHONE User Part T35 has expired	Information	Y	Timer T35 has expired.	0	For more information, refer to the appropriate specification for the protocol concerned.
TUP: T39 Expired	TELEPHONE User Part T39 has expired	Information	Y	Timer T39 has expired	0	For more information, refer to the appropriate specification for the protocol concerned.
TUP: T41 Expired	TELEPHONE User Part T41 has expired	Information	Y	Timer T41 has expired.	0	For more information, refer to the appropriate specification for the protocol concerned.
TUP: T5 Expired	TELEPHONE User Part T5 has expired	Information	Y	Timer T5 has expired.	0	For more information, refer to the appropriate specification for the protocol concerned.
TUP: T7 Expired	TELEPHONE User Part T7 has expired	Information	Y	Timer T7 has expired.	0	For more information, refer to the appropriate specification for the protocol concerned.
TUP: UNEX BLA	TELEPHONE User Part BLA received with local status unblocked	Information	Y	An unexpected BLA message has been received with a mismatched status.	0	For more information, refer to the appropriate specification for the protocol concerned.
TUP: UNEX HBA	TELEPHONE User Part HBA received with local status unblocked	Information	Y	An unexpected HBA message has been received with a mismatched status.	0	For more information, refer to the appropriate specification for the protocol concerned.
TUP: UNEX HUA	TELEPHONE User Part HUA received with local status unblocked	Information	Y	An unexpected HUA message has been received with a mismatched status.	0	For more information, refer to the appropriate specification for the protocol concerned.
TUP: UNEX MBA	TELEPHONE User Part MBA received with local status unblocked	Information	Y	An unexpected MBA message has been received with a mismatched status.	0	For more information, refer to the appropriate specification for the protocol concerned.
TUP: UNEX MUA	TELEPHONE User Part MUA received with local status unblocked	Information	Y	An unexpected MUA message has been received with a mismatched status.	0	For more information, refer to the appropriate specification for the protocol concerned.
TUP: UNEX SBA	TELEPHONE User Part SBA received with local status unblocked	Information	Y	An unexpected SBA message has been received with a mismatched status.	0	For more information, refer to the appropriate specification for the protocol concerned.
TUP: UNEX SUA	TELEPHONE User Part SUA received with local status unblocked	Information	Y	An unexpected SUA message has been received with a mismatched status.	0	For more information, refer to the appropriate specification for the protocol concerned.
TUP: UNEX UBA	TELEPHONE User Part UBA received with local status blocked	Information	Y	An unexpected UBA message has been received with a mismatched status.	0	For more information, refer to the appropriate specification for the protocol concerned.
XE Rsrc Fail	Resource failure.	Information	Y	This is informational. The log may contain more information as to the failed resource.	4	Check the log.

1HDLC = High-level data link control 2MDL = Message definition language 3Cisco TAC = Cisco technical assistance center 4COT = Continuity test 5SLT = Cisco signaling link terminal 6CGBA = Circuit group blocking acknowledgment 7CBG = circuit group blocking 8CGUA = circuit group unblocking acknowledgment 9CGU = circuit group unblocking 10CVT = circuit validation test 11CIC = circuit identification code 12LIF = line interface 13MGW = Cisco media gateway 14SCCP = Signaling connection control part 15MTP3 = message transfer part 3 16SSN = subsystem number 17TCAP = transaction capabilities application part

.

Log Messages

The Cisco MGC software includes a logging system that writes messages to log files determined during the client initialization period.

The log server software takes messages initiated by various applications (other software processes) within the Cisco MGC software, formats the messages, and writes them to the appropriate files. The log server also adds a time stamp, a process identifier (for the UNIX process), and a log message severity. (Refer to "SET-LOGSet Logging Levels" section for a description of log levels.)

The log files are stored in a directory indicated by the *.logDirectory XE configuration parameter and are given a name indicated by the *.logFileNamePrefix XE Configuration parameter. By default, all message go to the platform.log file in the $BASEDIR/var/log directory.

Through additional logging XE configuration parameters, various log message may be directed to different logs. To direct all log messages from a given process to a dedicated log, the *.logFileNamePrefix can be used to override the default. To direct log messages by category. the various logger.category XE configuration parameters may be used.

A log viewer is available through the Viewer Toolkit to view the contents of the system logs. Various filter criterion are available to provide a reduction in data volumes to review when searching the logs.

The messages take the following form:

Date/time-stamp, Process Name, Process ID, <log level>, LogID:<text of the message>. (This text can take multiple lines but normally is only a single line.)
 
Example:
Fri Jan 14 08:46:53:700 2000 | ProcessManager (PID 19593) <Info>
GEN_INFO_PSTART: Starting process PROVSAGT.
 

For more information about using and working with log messages, refer to the Cisco Media Gateway Controller Software Release 7 Operations, Maintenance, and Troubleshooting Guide.

Log messages, with descriptions of some of the messages, can be found in "Log Message Descriptions."

Posted: Tue Jun 6 07:49:04 PDT 2000
Copyright 1989 - 2000©Cisco Systems Inc.