nn10275-909v2_13.01_cvm17_c20_fault-management

C20 Converged Softswitch

Logs and Alarms Reference,Volume 2Release: CVM17Document Revision: 13.01

www.genband.com

NN10275-909v2

C20 Converged SoftswitchRelease: CVM17Publication: NN10275-909v2Document status: StandardDocument release date: 23 October 2012

Copyright © 2010-2012 GENBAND. All rights reserved. Use of this documentation and its contents is subject tothe terms and conditions of the applicable end user or software license agreement, right to use notice, and allrelevant copyright protections.

GENBAND, the GENBAND corporate logo and tagline, and certain of GENBAND's product and solution namesare registered trademarks of GENBAND and its affiliates.

While the information in this document is believed to be accurate and reliable, except as otherwise expresslyagreed to in writing, GENBAND AND/OR ITS LICENSORS PROVIDES THIS DOCUMENT "AS IS" WITHOUTWARRANTY OR CONDITION OF ANY KIND, EITHER EXPRESS OR IMPLIED. The information and/or productsdescribed in this document are subject to change without notice.

THE INFORMATION CONTAINED HEREIN IS THE PROPERTY OF GENBAND OR ITS LICENSORS ANDMUST NOT BE DISCLOSED, OTHER THAN TO EMPLOYEES OF GENBAND OR CUSTOMERS WITH NEED-TO-KNOW, WITHOUT THE PRIOR WRITTEN CONSENT OF GENBAND OR ITS LICENSORS. THEINFORMATION MUST NOT BE DISCLOSED TO SUBCONTRACTORS OR REGULATORY AUTHORITIES. GENBAND MUST BE NOTIFIED OF ANY REQUEST OR ORDER FOR DISCLOSURE PRIOR TO SUCHDISCLOSURE.

Software and documentation owned by or under license with Nortel Networks included in this Release or in any document provided with this Release is Copyright © 2010 Nortel Networks or its licensors. All rights reserved. Use of this software and/or documentation and its contents is subject to the terms and conditions of the applicableend user or software license agreement, right to use notice, and all relevant copyright protections

ContentsNew in this document 7Document revision 13.01 7GWC 7 Logs and alarms fundamentals 9 GWC (GC 170) alarms and logs reference 11CICM Problem Line Data 11CICM Valid Line Data 14GWC300 16GWC301 18GWC302 20GWC303 21GWC304 22GWC305 23GWC306 24GWC307 26GWC308 28GWC309 29GWC311 30GWC312 31GWC314 32GWC315 33GWC315 Format 1 35GWC315 Format 2 38GWC315 Format 3 41GWC315 Format 4 43GWC315 Format 5 46GWC317 48GWC318 51GWC319 52GWC320 53GWC321 57GWC322 59GWC324 61GWC325 63GWC328 64GWC351 68GWC399 69GWC501 69

3

23 October 2012 Logs and Alarms Reference, Volume 2 NN10275-909v2 13.01Copyright © 2010-2012 GENBAND. All Rights Reserved.

GWC502 71GWC503 Format 1 72GWC503 Format 2 74GWC506 76GWC507 78GWC508 80GWC509 82GWC600 84GWC601 89GWC603 91GWC604 92GWC605 94GWC606 95GWC607 99GWC608 100GWC609 103GWC610 105GWC611 106GWC612 108IPSec security logs 109 GWC (GL170) alarms and logs reference 113GWCA207 113GWCA240 114GWCA241 115GWCA300 116GWCA301 119GWCA302 122GWCA304 125GWCA305 128GWCA306 131GWCA307 134GWCA308 136GWCA311 138GWCA312 139GWCA313 141GWCA314 143GWCA315 145GWCA317 148GWCA318 150GWCA319 152GWCA322 155GWCA323 157GWCA324 159GWCA325 161GWCA326 164GWCA327 166GWCA328 167GWCA330 169GWCA331 171GWCA332 174GWCA333 177

4

23 October 2012 C20 Converged Softswitch NN10275-909v2 13.01Copyright © 2010-2012 GENBAND. All Rights Reserved.

GWCA334 179GWCA335 181GWCA336 183GWCA337 186GWCA399 187GWCA500 188GWCA501 189GWCA502 190GWCA503 191GWCA506 193GWCA507 194GWCA508 196GWCA509 197GWCA600 198GWCA605 204GWCA606 205GWCA607 207GWCA608 208GWCA609 209GWCA610 211GWCA611 212GWCA613 213GWCA614 213GWCA615 214

5


6


New in this documentDocument revision 13.01

This section describes the changes that have been made to this documentsince it was last released.

GWC• CICM Problem Line Data modified

• CICM Valid Line Data modified

• GWC300 modified

• GWC301 modified

• GWC302 modified

• GWC303 modified

• GWC304 modified

• GWC305 modified

• GWC306 modified

• GWC307 modified

• GWC308 modified

• GWC309 modified

• GWC311 modified

• GWC312 modified

• GWC314 modified

• GWC315 modified

• GWC315 Format 1 modified





7


• GWC317 modified

• GWC318 modified

• GWC319 modified

• GWC320 modified

• GWC321 modified

• GWC322 modified

• GWC324 modified

• GWC325 modified

• GWC328 modified

• GWC351 modified

• GWC399 modified

• GWC501 modified

• GWC502 modified



• GWC506 modified

• GWC507 modified

• GWC508 modified

• GWC509 modified

• GWC600 modified

• GWC601 modified

• GWC603 modified

• GWC604 modified

• GWC605 modified

• GWC606 modified

• GWC607 modified

• GWC608 modified

• GWC609 modified

• GWC610 modified

• GWC611 modified

• GWC612 modified

• IPSec security logs modified

8 New in this document


Logs and alarms fundamentalsA log report is a message about an important conditions or events relatedto component(s) performance. Log reports include, but are not restrictedto, the following information:

• state and activity reports

• changes in state

• hardware or software errors

• test results

• other events or conditions that affect performance

Both system actions and manual overrides can generate log reports.

Attention The Genband Carrier Voice over IP Fault Management Logs Reference documentuses multiple volumes to describe logs that Carrier Voice over IP (CVoIP) Portfoliocomponents can generate. Not all components apply to every solution.

Attention In systems which include an Integrated Element Management System (IEMS),clearing of manually clearable alarms through OMI (or a System ManagementGUI) is reflected in the IEMS. However, acknowledgement of alarms through OMI(or a System Management GUI) is NOT reflected in the IEMS.

9


10 Logs and alarms fundamentals


GWC (GC 170) alarms and logs referenceThis section provides a reference for the GWC alarms and logs for theGC170 release.

CICM Problem Line DataLog report Problem Line Data log contains a set of zero or more problemreport strings indicating problems that require correction, have beencorrected, or being flagged for attention - e.g., a missing user.

System impactn/a

Remedial actionThis log report requires no immediate action. This log is informational andis intended to help with diagnosing call completion problems.

AttributesAttribute Value

Log name n/aSeverity WarningAssociatedcomponent

n/a

Legend n/a

FormatGWC = <GWC>, GW = <GW>, EP = <EP Name>,

CICM line = <CICM line>. Problem Report = <Problem Report>

11


Selected field descriptionsField Value Fixed

orVariable

Description

GWC Name String Variable

Name of GWC hosting theCICM GW

GW Name String Variable

Name of CICM GWprovisioned at CS 2000Management Tools server

EP Name String Variable

Name of CICM endpoint

CICM Line Integer Variable

CICM line numbercorresponding to endpoint /LEN

Problem Report String Variable

• HASU Line state -- Line inHASU state but has userentry at CICM.

• Missing user -- Line inWORKING state but noprovisioned user.

• Extension modulemismatch -- Mismatchbetween number ofprovisioned M522modules.

• Illegal extension module --Extension module typeprovisioned at call servernot supported by CICM.

• Mismatch_LCC -- LCCtype provisioned a callserver not supported byCICM.

• Feature missing --Provisioned feature is notpresent on designatedkey.

• Feature mismatch --Provisioned featuremismatch between CMand CICM.

• Unexpected feature -- Nofeature at CM but keyprovisioned at CICM.

12 GWC alarms and logs reference


Field Value FixedorVariable

Description

• Incorrect_DN -- DNnumber at CICM does notmatch the CM.

• Incorrect label -- Userstring at CICM does notmatch that provisionableby flowthroughprovisioning.

• Multiple mismatches --Large number ofmismatches at CICM; notdisplayed individually toprevent flooding log.

• HASU features -- Featureprovisioned against aHASU line.

• Missing Line -- LEN entryat CM but correspondingCICM line is missing.

• Deleted HASU user --HASU user at CICMdeleted.

• Correct extension module-- M522 extension setmismatch corrected atCICM.

• Added feature -- Missingfeature code added to keyon CICM.

• Corrected feature --Feature code mismatchcorrected at CICM.

• Deleted feature -- Deletedfeature code from CICMkey.

• Correct DN -- CorrectedDN number on CICM key.

• Correct label -- Correctedlabel mismatch on CICMkey.

CICM Problem Line Data 13



Description

• Multi correct -- Largenumber of correctionsperformed against CICMline. Not listed individuallyto prevent flooding log.

• Deleted HASU line -- Allline data fill removed froma HASU line at CICM.

• Unexpected report --Problem report type notsupport by CICM EM. Notend user visible.

• Corrupt user -- Corruptionof user data fill detected atCICM.

• Correct corrupt user --Corruption of user data filldetected at CICM andcorrected by audit.

• Audit line not possible --CICM is unable to auditline; indicates Node is outof service or incorrectprovisioning.

• Unsupported report -- Thisversion of the CS 2000Management Tools serverdoes not support thereceived type of problemreport.

Associated logs

Associated OM registers

CICM Valid Line DataLog report Valid Line Data is generated during the Line Data Integrity audit.



Log report Valid Line Data is generated as a result of the following:

• Feature data is valid but audit wants to warn about a user not beingassigned.

• Audit has corrected the problem so the line is valid post audit.

System impactn/a



Log name n/aSeverity WarningAssociatedcomponent

n/a

Legend n/a

FormatLEN = <LEN>, GW Name = <GW Name>, GWC Name = <GWC Name>,

EP Name = <EP Name>, CICM line = <CICM line>, USER = <User>,

Enterprise = <Enterprise>, Profile = <Profile>


orVariable

Description

LEN Integer Variable

Line entry from table LNINV(KSETLINE)

GW Name String Variable

Name of CICM GWprovisioned at CS 2000Management Tools server

GWC Name String Variable

Name of GWC hosting theCICM GW

EP Name String Variable

Name of CICM endpoint

CICM Valid Line Data 15



Description

CICM Line Integer Variable

CICM line numbercorresponding to endpoint /LEN

User String Variable

User assigned to Line (may beempty)

Enterprise String Variable

Enterprise associated withUser (SN10+ CICM node)

Profile String Variable

Profile that user is associatedwith (SN10+ CICM node)

Associated logs


GWC300Log report GWC300 indicates an "Active unit disabled." Unit Out ofService: Service is not available or Invalid GWC Profile Data. The alarmseverity is Critical.

This log is cleared by log report GWC399. If required, see "GWC399" formore information.

Remedial actionIndicates that a unit is out of service: Service is not available.

This log reports that the unit is not in service (Operational state of"disabled"). If the Administrative state is "unlocked" and the Usage state is"busy" this indicates the unit is trying to recover itself to an in service state.Note that when both units are out of service, the active unit must recoverbefore the standby unit will. A probable cause is the lack of availability ofthe underlying resource.

Check the following:

• Whether the unit is manually locked out of service (Administrative stateof "locked" ) .

• Alarms that may indicate a problem on the unit preventing it fromreturning to service.

• Other state indicators which may indicate problems, such as



• Isolation state of "isolated"

• If it is the standby unit, Availability state of "degraded"

• Availability state of "offLine"

• Logs which may also indicate a failure of a step in the process ofrecovering the unit.

Indicates that a unit has invalid GWC Profile Data: Service is not available.

Probable causes are configuration or customization errors. Check theprofile data for the unit and do one of the following:

• Change to another profile

• Reconfigure the GWC unit software or CS 2000 GWC Managersoftware to remove the incompatibility.

• Then, RTS the unit


Severity CriticalProbablecause

Underlying Resource Unavailable

FormatCOMPACT2 *** GWC300 JUN30 11:01:55 0580 TBL GWC Fault

Location: GWC-0-UNIT-0

NotificationID: 1

State: Raise

Category: Quality of Service

Cause: Underlying resource unavailable

Time: Jun 30 11:09:16 2003

Component Id: GWC-0-UNIT-0

Specific Problem: Unit Out of Service: Service is notavailable

Description: Active unit disabled.

GWC300 17


Active message examplen/a

Clear message examplen/a


GWC301Log report GWC301 indicates a "Standby unit disabled." Unit Out ofService: Service is not available or Invalid GWC Profile Data. The alarmseverity is Minor or Major.




If the Operational state "disabled" and Administrative state is "unlocked",the unit is system busy (SysB) - the alarm is major.

If the Operational state "disabled" and Administrative state is "locked", theunit is manually busy (ManB) - the alarm is minor.



• Other state indicators which may indicate problems, such as:






Indicates that a unit has invalid GWC Profile Data: Service is not available.

A probable cause is a configuration or customization error. Check theprofile data for the unit and do one of the following:

• Change to another profile.

• Reconfigure the GWC unit software or CS 2000 GWC Managersoftware to remove the incompatibility.

• Then, RTS the unit.


Severity • Major

• Minor

Probablecause


FormatCOMPACT2 * GWC301 JUN30 11:02:44 0588 TBL GWC Fault


NotificationID: 1

State: Raise



Time: Jun 30 10:54:34 2003

Component Id: GWC-0-UNIT-1

Specific Problem: Unit Out of Service: Service is notavailable

Description: Standby unit disabled.



GWC301 19



GWC302Log report GWC302 indicates a Major for active unit; Minor for inactiveunit. "Core communication lost." No response received to Core heartbeatmessages.


Remedial actionThe alarm condition associated with this log clears automatically after aCore or network outage clears. Otherwise, verify that the node number andCore Side IP address is correct for the GWC to communicate with theCore.


Severity • Major

• Minor

Probablecause

LAN Error

FormatCOMPACT06BT * GWC302 JUL1 15:02:21 0055 TBL GWC Fault


NotificationID: 3

State: Raise

Category: Communications

Cause: LAN error

Time: Jul 01 15:02:27 2003

Component Id: GWC=GWC-2-UNIT-0;Version=PGC91AQ;Unit=unit_0;

Software=NODE MTC

Specific Problem: No response received to Core heartbeatmessages.



Description: Core communication lost.




GWC303Log report GWC303 indicates a "Mate unit communication lost." Noresponse received to mate heartbeat messages. The alarm severity isminor if mate is in Manual busy state.Else the severity is major.


Remedial actionThe alarm associated with this log can be cleared by restoringcommunication from the CS 2000 GWC Manager to the GWC unit. Do thisby unlocking the GWC at the CS 2000 SAM21 Manager. Also, verify thatthe Ethernet cable is connected, and that the GWC is setup to use thecorrect node number.


Severity • Major

• Minor

Probablecause

LAN Error

FormatCOMPACT2 * GWC303 JUN30 11:02:47 0589 TBL GWC Fault


NotificationID: 4

State: Raise


Cause: LAN error

GWC303 21


Time: Jun 30 11:10:08 2003

Component Id: GWC=GWC-0-UNIT-0;Version=PGT09BL;Unit=unit_0;

Software=NODE MTC

Specific Problem: No response received to mate heartbeatmessages.

Description: Mate unit communication lost.




GWC304Log report GWC304 indicates that communication with a gateway is down.The alarm severity is Major.

'Gateway' is defined as large gateway or audio gateway (for example,PVG, H.323 gateway with 64 or more endpoints, MG 9000, UAS).


Remedial actionThe alarm condition associated with this log can be cleared by restoringcommunication to the managed gateway. Do this by verifying theavailability of the gateway, and comparing the configuration data at theGateway and the CS 2000 GWC Manager (IP address, protocol/version,etc).


Severity MajorProbablecause


FormatCOMPACT2 ** GWC304 JUL2 01:25:58 0619 TBL GWC Fault




NotificationID: 78

State: Raise



Time: Jul 02 01:21:20 2003

Component Id: GWC=GWC-1-UNIT-1;Version=PGT09BL;

Unit=unit_1;Software=SSC

Specific Problem: TESTPVG

Description: Communication with a gateway is down.




GWC305Log report GWC305 indicates that a test alarm is generated from pmdebuginterface to log in to the notilog table. May be any level.


Remedial actionThe alarm condition associated with this log can be cleared by using thepmdebug command (not a customer interface) or with a GWC reload.


Severity IndeterminateProbablecause

Unexpected Information

GWC305 23


FormatCOMPACT2 *** GWC305 JUL10 09:56:30 0671 TBL GWC Fault


NotificationID: 12

State: Raise


Cause: Unspecified reason

Time: Jul 10 10:07:23 2003


Software=DEBUG

Specific Problem: Alarms test from debug interface

Description: This is a test alarm generated from pmdebuginterface.




GWC306Log report GWC306 indicates a DQoS/COPS connection failure. Thealarm severity is major.



When a dynamic quality of service (DQoS) connection is down betweenthe CS 2000 and a CMTS, the CS 2000 will allow new calls hosted by thatCMTS to proceed without DQoS. The behavior of the multimedia terminaladapter (MTA) and CMTS determines whether new calls are attemptedusing best-effort service or whether they are torn down:

• Some MTA vendors allow calls to proceed as data calls (best-effort)and do not send a data-over-cable service interface specification(DOCSIS) authorization block to the CMTS. In this case, the CMTScannot recognize the call as a voice call and so it proceeds withoutmanaged quality of service.

• Other MTA vendors send the DOCSIS authorization block to the CMTSwith no authorization key or gate-id. When this happens, the CMTSdecides whether or not to allow calls to proceed.

When the DQoS connection is up, but the CS 2000 does not receive aDQoS gate-id from the CMTS, the CS 2000 will tear down a call.


Remedial actionThe DQoS connection loss alarm is cleared by DCCNXMGR (usingDCALARM) when the connection is reestablished or the connection isdeleted from provisioning.



Communication Subsystem Failure

FormatCOMPACT2 ** GWC306 JUL10 09:56:31 0672 TBL GWC Fault


NotificationID: 13

State: Raise


Cause: Communications subsystem failure

GWC306 25


Time: Jul 10 10:07:24 2003


Software=DQOS MTC

Specific Problem: DQoS connection CMTS065 has failed -attempting

rec overy.

Description: DQoS/COPS connection failure.




GWC307Log report GWC307 indicates an "Element Manager communicationfailure." Specific problem is one of the following:

- EM indicates provisioned data mismatched in this unit

- EM is not responding, provisioned data loaded from local Flash

- Provisioned data updated in Flash, but not yet in use

The alarm severity is Major.


Remedial actionThe alarm condition associated with this log can be cleared with a Busy/RTS of GWC unit.



Restore communication with the CS 2000 GWC Manager. Determine if theCS 2000 GWC Manager is down and or disconnected. Determine if theGWC has been setup to use the wrong IP address for the CS 2000 GWCManager at the CS 2000 SAM21 Manager.




FormatCOMPACT06BT ** GWC307 JUL1 10:45:47 0028 TBL GWC Fault


NotificationID: 10

State: Raise



Time: Jul 01 10:45:51 2003


Software=NODE MTC

Specific Problem: EM indicates provisioned data mismatchedin this

unit

Description: Element Manager communication failure.



GWC307 27



GWC308Log report GWC308 indicates a "Flash memory error." Erase of Flashsector failed. The alarm severity is Minor


Remedial actionThe alarm condition associated with this log can be cleared by replacingthe hardware.


Severity MinorProbablecause

Equipment Malfunction

FormatCOMPACT2 * GWC308 JUL10 09:56:37 0675 TBL GWC Fault


NotificationID: 16

State: Raise

Category: Equipment

Cause: Equipment Malfunction Time: Jul 10 10:07:23 2003


Software=FLAS H

Specific Problem: Erase of Flash sector failed

Description: Flash memory error.






GWC309Log report GWC309 indicates that the number of the security associations(SA) that the system can support has been exceeded. The associatedalarm severity is Minor.


Remedial actionThis log is associated with a minor information alarm. Report this alarmwith details to your next level of support. Note that the alarm clearsautomatically as SA usage decreases.


Severity MinorProbablecause

Resource at or Nearing Capacity

FormatGWC309 AUG10 14:15:09 0674 TBL GWC Fault


Component ID: GWC=GWC-12-UNIT-0;Version=GN070BV;Unit=unit_0;

Software=Signalling security

Alarm Level: Minor

Alarm Description: Security SAs are nearing capacity

Category: Processing Error

Alarm Time: 14:05:10 10-Aug-2004 EDT

Probable Causes: Resource at or nearing capacity

Specific Problem: SA nearing capacity

System Uptime: 1 hours, 0 minutes, 45 seconds


GWC309 29




GWC311Log report GWC311 indicates a Warning. "Provisioned GWC Profile not yetactivated." The GWC Profile loaded into Flash will activate on the nextreload.


Remedial actionThe alarm condition associated with this log can be cleared by reloadingthe GWC.


Severity WarningProbablecause

Configuration or Customizing Error

FormatCOMPACT06BT GWC311 JUL1 10:39:56 0022 TBL GWC Fault


NotificationID: 12

State: Raise


Cause: Configuration or customization error

Time: Jul 01 10:40:03 2003


Software=CONFIG

Specific Problem: GWC Profile loaded into Flash willactivate on

next reload.



Description: Provisioned GWC Profile not yet activated.




GWC312Log report GWC312 indicates a QCA connection failure, either a majoralarm (partial outage) or a critical alarm (total outage).


Remedial actionNo reports are lost since they are collected on a backup server.

• Ensure that the QCA contains the correct properties (port, IP address,etc). Check that the QCA is properly provisioned using the CS 2000Management Tools.

• Use the ping command to see if you can reach the QCA server. If youcannot reach the server, there may be a problem in the network.

• Verify that there is no memory exhaustion on the QCA server.

• To bring up the links, restart the QCA application on the server.

• Try connecting to a QCA on another CS 2000 Management Toolsserver.


Severity • Critical

• Major

Probablecause


FormatCOMPACT2 *** GWC312 JUN30 11:02:37 0586 TBL GWC Fault


NotificationID: 3

GWC312 31


State: Raise



Time: Jun 30 11:09:58 2003


Software=QCAMTC

Specific Problem: QCA connection<qca_47.142.130.70 Port #20000>has

failed - attempting recovery.

Description: QCA connection failure




GWC314Log report GWC314 indicates a Major alarm (partial outage). The CentrexIP Client Manager (CICM) location identification reporting application failsto establish a TCP/IP connection to the location recipient, or theestablished connection is broken.


Remedial actionClear the alarm condition using one of the following approaches:

• Re-establish the connection to the location recipient.

• Disable the location ID reporting application.

• Busy/RTS the GWC unit.






FormatCS2K1 *** GWC314 JUN30 11:02:37 0586 TBL GWC Fault


NotificationID: 3

State: Raise

Category: Processing Error


Time: Jun 30 11:09:58 2003

Component Id: GWC=GWC-213-UNIT-0;Version=GI070BCD;Unit=unit_0;

Software=LocIdRep

Specific Problem: Location Id Reportingconnection<47.30.178.20>

has failed - attempting recover

Description: Location Id Reporting connection failure




GWC315This alarm is based on the number of gateways that failed DNS lookup in a5-minute polling period.

Use the new DNS OMs to check the number of gateways not discovered,and the number of gateways discovered using RSIP.

GWC315 33


RSIP discovery does not survive a cold SwAct on the GWC, which maycause long outages.

The alarm severity is as follows:

Critical (50% or more)

Major (7% or more)

Minor (1% or more)

Warning (<1%, but some GWs are undiscovered yet)


Remedial actionCheck if DNS server is up.


Log name GWC315Severity • Critical

• Major

• Minor

• Warning

• Cleared

Type Quality of Service AlarmProbablecause


FormatCategory: <category>

Time: <Timestamp>

Severity: <severity>

Probable Cause: <cause>

CompID: GWC=<GWC_UNIT>;Version=<sw_version>;Unit=<unit_no>;Software=<software>



Specific Problem : <problem>


orVariable

Description

ComponentID Text description Variable

Identifies the GWC node, itsload and the unit that initiatedthe alarm.

Specific problem Text description Variable

Identifies the specific problemassociated with the alarm.

Severity Text description Variable

Identifies the severity of thealarm(critical/major/minor/warning)

Category Text description Variable

Identifies the alarm category(Ex.: qualityOfService)

Cause Text description Variable

Identifies the probable causesfor the alarm. (Ex.:Configuration or customizationerror)

Active message exampleCategory : qualityOfService

Time: Wed Jul 30 16:50:0 2008

Severity : critical

Probable Cause : Configuration or customization error

CompID : GWC=GWC-1-UNIT-1;Version=GC120AV;Unit=unit_1;Software=OM Collection

Specific Problem : DNS failed GW discovery

GWC315 Format 1Log report GWC315 indicates the loss of external host interface signals.The alarm severity is as follows:

• Critical

• more than 50% of provisioned small GWs or media proxies in adisabled state (Format 1)

• more than 50% of peer connections failed during the 5-minute pollingperiod (Format 2)

• Major

GWC315 Format 1 35


• 20-49% of provisioned small GWs or media proxies in a disabled state(Format 1)

• 20-49% of peer connections failed during the 5-minute polling period(Format 2)

• USP SS7 paths disabled (both links down; Format 3)

• both USP SS7 links inactive (Format 4)

• Minor

• some (less than 20%) provisioned small GWs or media proxies in adisabled state (Format 1)

• some (less than 20%) peer connections failed during the 5-minutepolling period (Format 2)

• USP SS7 paths disabled (one link down; Format 3)

• one USP SS7 link inactive (Format 4)

• Warning

• GWs failed DNS lookup during the 5-minute polling period (Format 5)

A "peer connection failure" is an abnormal call takedown during connectionsetup phase of a call. During connection setup phase two parties areselected for the call but speech path is not connected yet. This calltakedown is triggered by a peer GWC or Interworking Spectrum PeripheralModule (IWSPM) failure.

Some possible causes of a peer connection failure are:

• peer GWC encounters a protocol exception from its gateway whenattempting to allocate connection or negotiate Session DescriptorProtocol (SDP)

• peer GWC cannot authorize bandwidth for this call with Policy server

• peer GWC fails to get response from its gateway and thus connectiontimes out

• peer GWC is unresponsive and this GWC times out waiting for aresponse

Minor or Major Peer connection alarms can be expected to occur for ashort period after GWC or gateway maintenance activities, due to protocolstate mismatches. Persistent Minor or Major alarms can indicate a problemrequiring corrective action by operating company or Nortel personnel.





• Use the small GW OMs to check how many small line GWs are out ofservice, and use the logs to identify which GWs need attention.

• Use the peer messaging OMs to check the number of calls failed overa longer period, and check the Ethernet link between the GWC and theremote host or peer GWCs.

• Check the USP connections.

• Check the USP configuration to the GWC.



• Major

• Minor

• Warning

Probablecause


FormatNetwork Element: GWC-8-UNIT-1

IP:(data not available)

Component Id: GWC=GWC-8-UNIT-1;Version=GN090BT;Unit=unit_1;

Software=OM Collection


Alarm Time: Wed Aug 17 09:00:00 EDT 2005

Alarm Level: Critical

Probable Cause: Loss of signal

Specific Problem: Small GWs in Disabled State

Description: External communication interface

System Uptime: 1 day, 2 hours, 25 minutes, 0 seconds

GWC315 Format 1 37


Network Element: GWC-22-UNIT-0


Component Id: GWC=GWC-22-UNIT-0;Version=GN090BV;Unit=unit_0;



Alarm Time: Tue Aug 16 06:35:01 EDT 2005

Alarm Level: Major


Specific Problem: Media Proxies in Disabled State







• Critical



• Major







• Minor





• Warning










GWC315 Format 2 39









• Major

• Minor

• Warning

Probablecause


FormatNetwork Element: GWC-50

IP:(could be mate)

Component Id: GWC=GWC-50-UNIT-0;Version=GN090BO;Unit=unit_0;



Alarm Time: Mon Jul 25 17:50:00 EDT 2005

Alarm Level: Minor


Specific Problem: Peer connections failed during interval









• Critical



• Major





• Minor





• Warning



GWC315 Format 3 41
















• Major

• Minor

• Warning

Probablecause









Alarm Time: Thu Aug 18 09:40:00 EDT 2005

Alarm Level: Minor


Specific Problem: USP SS7 paths disabled


System Uptime: 2 days, 3 hours, 9 minutes, 9 seconds





• Critical



• Major





• Minor

GWC315 Format 4 43






• Warning



















• Major

• Minor

• Warning

Probablecause







Alarm Time: Thu Aug 18 09:40:00 EDT 2005

Alarm Level: Minor


Specific Problem: USP SS7 paths inactive


System Uptime: 2 days, 3 hours, 9 minutes, 9 seconds

GWC315 Format 4 45






• Critical



• Major





• Minor





• Warning



















• Major

• Minor

• Warning

Probablecause



GWC315 Format 5 47



Component Id: GWC=GWC-8-UNIT-1;Version=GN090BT;Unit=unit_1;



Alarm Time: Wed Aug 17 09:00:01 EDT 2005

Alarm Level: Warning

Probable Cause: Configuration or customization error

Specific Problem: DNS failed GW discovery


System Uptime: 1 DAY, 2 hours, 25 minutes, 1 seconds




GWC317Log report GWC317 is used to indicate that the Pre Swact audit failureoccurred for two consecutive cycles. An alarm will be raised whenever thePreSwact audit fails for two consecutive cycles due to resource exhaust.The text of the alarm describes which component has led to the failure.Itwill be reflected in the SESM as well as in the GWC with the availablestatus of the GWC in the SESM reflecting 'DEGRADED'. The audit runsperiodically and raises alarm for PSA fail on error conditions. A duplicatealarm for the same reason as that of an existing one will not be raised.


Remedial actionCheck the alarm text to see which component has failed. The alarm clearswhen you clear the error condition. If required, you can use Swact force toforce a manual warm Swact.



This alarm will be cleared when the fault is cleared as PSA will be runningperiodically other than running during Swacts. The PSA will pass for aresource when its usage comes down with in limits.


Log name GWC317Severity MajorType Quality of Service AlarmProbablecause

Performance Degraded;Resource at or Nearing Capacity

Format<OFFICE> GWC317 MMDD hh:mm:ss <sequence number> TBL GWCFault

Location: GWC-<node>-UNIT-<unit>

NotificationID: <Notification ID>

State: Raise

Category: qualityOfService

Cause: performanceDegraded

Time: MM DD hh:mm:ss YYYY

Component ID: GWC=GWC-<node>-UNIT-<unit>; Version:<version>; Unit: <unit>

Software: Hlt hchk

Specific Problem: Unit Jammed Problem

Description: PreSwact Audit Failure

GWC317 49



orVariable

Description

Sequencenumber

0000-9999 Variable

Four-digit sequence numberidentifying a specific log entry.

location Alpha-numericcharacter string

Variable

Identifies the GWC node andunit that initiated the alarm.Example: GWC-50-UNIT-0

NotificationID Integer Variable

A unique value assigned eachtime an alarm is raised.

State Raise/Clear Variable

Indicates whether the alarm israised or cleared.


Identifies the probable causesfor the alarm. Example:Performance degraded.



Specific problem Text description Variable


Description Text description Variable

Indicates a brief description ofthe Alarm.

Active message exampleMTOSSRTP4 ** GWC317 NOV27 14:33:15 3360 TBL GWC Fault


NotificationID: 287

State: Raise


Cause: performanceDegraded

Time: Nov 27 14:33:15 2007

Component Id: GWC=GWC-50-UNIT-0;

Version=GN110BD;Unit=unit_0;Software=Hlt hchk

Specific Problem: Unit Jammed Problem



Description: PreSwact Audit Failure


GWC318Log report GWC318 indicates that the Gateway Controller (GWC) initiatedan autonomous switch of activity (SWACT) in an attempt to restorecommunication with its associated media gateways. The alarm severity iscritical.


Remedial actionCheck the related network component managers to identify failures withinthe network.

The alarm clears automatically when a manual SWACT back to the originalactive unit is performed.

You can also manually clear this alarm once the problem on the originalactive unit is solved. Follow procedure "Clear the GWC318 critical alarmmanually" in theGateway Controller Fault Management, NN10202-911.




Formatznc0s0jh *** GWC318 NOV16 11:02:37 0126 TBL GWC Fault


NotificationID: 5

State: Raise

Category: communications

Cause: underlyingResourceUnavailable

Time: Nov 16 11:02:58 2005

GWC318 51


Component Id: GWC=GWC-9-UNIT-0;Version=GN91AWJK;Unit=unit_0

Software=AUTOSWACT

Specific Problem: GWC-9-UNIT-0: No communication withassociated

media gateway(s)

Description: Autonomous SWACT initiated




GWC319Log report GWC319 indicates that the Gateway Controller (GWC) lostcommunication with all associated media gateways. The alarm severity iscritical.



The alarm clears when the GWC detects communication with at least oneassociated gateway. It also clears when the GWC automatically ormanually switches activity but it is raised again on the newly active unit ifcommunication is still lost with all associated gateways.




Formatznc0s0jh *** GWC319 NOV16 15:17:23 0126 TBL GWC Fault




NotificationID: 4

State: Raise


Cause: underlyingResourceUnavailable

Time: Nov 16 15:17:23 2005

Component Id: GWC=GWC-9-UNIT-0;Version=GN91AWJK;Unit=unit_0

Software=SSC

Specific Problem: GWC-9-UNIT-0: No communication withassociated

media gateway(s)

Description: GWC communication loss with all associatedmedia

gateway(s).




GWC320Log report GWC320 indicates an IKE/IPSec processing problem. The logentry identifies the specific problem. The alarm severity and actiondepends on the specific problem. For the description of associatedGWC320 alarms, see procedure "View and troubleshoot GWC servicealarms" in the Gateway Controller Fault Management, NN10202-911.

In addition, each specific alarm (except "private key mismatch") has anassociated security log, which provides additional details about theproblem. For the description of all IPSec and IKE security logs, seeprocedure "IPSec and IKE security logs" in the Gateway Controller FaultManagement, NN10202-911.

GWC320 53



Remedial actionThe following describes specific problems and required actions associatedwith this log report.

One or more certificates in set number<x>are expiring. An outage mayoccur if an IKE connection policy is using these certificates. At theGWCEM, please verify the expiry dates for certificates in set number<x>--<IP>

• <x>- is the set number of the [IKE certificates] panel

• <IP>- is the IP address of the GWC node

This log report indicates that an IKE certificate is expiring soon and theGWC Manager has not obtained a new certificate from the CertificateManager. This condition may cause service disruptions.

For information on how to clear the alarm associated with this log report,see the<ATM/IP Solution-level ???, NN?? - to be determined>

One or more certificates in set number<x>are expired. An outage will occurif an IKE connection policy is using these certificates. At the GWCEM,please verify the expiry dates for certificates in set number<x>--<IP>

• <x>- is the set number of the [IKE certificates] panel


This log report indicates that an IKE certificate is expired and the GWCManager has not obtained a new certificate from the Certificate Manager.Service disruption will occur when the certificate expires.

For information on how to clear the alarm associated with this log report,see the<ATM/IP Solution-level ???, NN?? - to be determined>

Invalid Subject Alternative Name in GWC certificate (set number<x>) -- IP

• <x>- is the set number of the [IKE certificates] Panel


This log report indicates that the Subject Alternative Name in the GWCcertificate does not match the provisioned IP address for the GWCcertificate. This may indicate a data or communication problem betweenthe GWC and the GWC Manager.



Contact your next level of support.

Phase 1 SA failure --<remote_gateway_IP_address>

This log reports indicate that a Phase 1 negotiation failed. This log report isthe result of an outage.

Refer to the appropriate security log associated with the alarm to obtainmore detailed information. See procedure "IPSec and IKE security logs" intheGateway Controller Fault Management, NN10202-911 for thedescription of IPSec/IKE security logs and required actions.

Phase 2 SA failure --<remote_gateway_IP_address>

This log reports indicate that a Phase 2 negotiation failed. This log report isthe result of an outage

Refer to the appropriate security log associated with the alarm to obtainmore detailed information. See procedure "IPSec and IKE security logs" intheGateway Controller Fault Management, NN10202-911 for thedescription of IPSec/IKE security logs and required actions.

GWC certificate in set number<x>doesn't match private key --<GWC_IP_address>

This log report may indicate an outage.

Contact your next level of support immediately.

There are no security logs associated with this specific problem.


Severity Indeterminate

FormatMmm DD hh:mm:ss<OFFICE>GWC320<severity>TBL GWC Fault

Location: GWC-###-UNIT-#

NotificationID:<integer>

State:<Raise, Clear>

GWC320 55


Category: processingError

Cause:<probable_cause>

Time: Mmm DD hh:mm:ss YYYY

Component Id: GWC=GWC-###-UNIT-#;Version=<load>;Unit=unit_#;

Software=Signaling security

Specific Problem:<specific problem>

Description: IKE/IPSec


orVariable

Description

location alpha-numericcharacter string

Variable

Identifies the GWC node andunit that initiated the alarm.

Example: GWC-8-UNIT-0notificationID integer Variabl

eA unique value assigned eachtime an alarm is raised.

state Raise or Clear Variable

Indicates whether the alarm israised or cleared.

cause text description Variable

Identifies one of the followingprobable causes for the alarm:

• key expired

• underlyingResourceUnavailable

• unexpected information

componentID text description Variable


specific problem text description Variable


sequencenumber

0000-9999 Variable


description text description Variable

Indicates an IKE/IPSec-relatedproblem.






GWC321Log report GWC321 indicates that the auto-negotiation capability isdisabled on the Ethernet Routing Switch 8600. An associated major alarmis raised whenever the system detects that auto-negotiation is disabled onthe Ethernet Routing Switch 8600.


Remedial actionEnable the auto-negotiation capability on the Ethernet Routing Switch8600. If required, refer to Ethernet Routing Switch 8600 configurationdocumentation.


Severity MajorType CommunicationsProbablecause


Format<OFFICE>** GWC321 MMMDD hh:mm:ss 7413 TBL GWC Fault



State: Raise


Cause: Configuration or customization error



Software=IP

GWC321 57


Specific Problem: Auto-negotiation disabled on ethernet link

Description: Ethernet/IP Errors


orVariable

Description

Location Alpha-numericcharacter string

Variable

The field indicates the GWCnode and unit that initiated thealarm.

Example: GWC-8-UNIT-0NotificationID Integer Variabl

eA unique value assigned eachtime an alarm is raised for thatGWC.

State Text description Variable

This field indicates the alarm israised.


Indicates the X.733-basedcategory of the alarm. In thiscase, Communications.

Time Alpha-numericcharacter string

Variable

Indicates the date and time ofthe alarm raise.

Example: Jan 26 15:14:252006


This field identifies the GWCnode, its load and the unit thatinitiated the alarm.

Example: GWC=GWC-8-UNIT-0;Version=GN091BH;Unit=unit_0;Software=IP

Specific Problem Text description Variable

This field identifies the specificcause for the alarm.

Example: Auto-negotiationdisabled on ethernet link.


This field describes thespecific cause for raising thealarm.

Example: Ethernet/IP Errors.Cause Text description Variabl

eIndicates the cause of thealarm. In this case,Configuration or customizationerror.






GWC322Log report GWC322 indicates that the simple network managementprotocol (SNMP) message rate exceeded the recommended maximum. Aminor alarm is raised on crossing the Panic Levels and a warning alarm israised on crossing the Warning Levels.

This log is cleared by log report GWC399. If required, see "GWC399"

for more information.

Remedial actionMake sure that the SNMP traffic is reduced.


Severity • Minor

• Warning

Type CommunicationsProbablecause

Threshold Crossed

Format<OFFICE>** GWC322 MMMDD hh:mm:ss 1234 TBL GWC Fault



State: Raise


Cause: Threshold crossed



GWC322 59


Software=SNMPMessaging


Description: A subsystem is overloaded


orVariable

Description


Variable

Indicates the GWC node andunit that initiated the alarm.



State Raise Variable

Indicates that the alarm israised.




Indicates the cause of thealarm. In this case, Thresholdcrossed.


Variable


Example: Jan 26 15:14:252006



Example: GWC=GWC-8-UNIT-0;Version=GN091BH;Unit=unit_0;Software=SNMPMessaging




Description


Identifies the specific cause forthe alarm.

Examples:

SNMP message rateexceeded recommendedmaximums.

or

SNMP message rate is closeto recommended maximums.


Describes the specific causefor raising the alarm.

Example: A subsystem isoverloaded.




GWC324Log report GWC324 indicates that uptime alarms have been raised on theGWCs.


Remedial actionNone.


Severity Major

FormatTime: Mmm DD hh:mm:ss YYYY rtp6iems

GWC324 61


IEMS: _V2_~I=~H=rtp6iems~A=IEMS~S=2735~~ GWC324 MAJOR TBLGWC Fault



State: Raise


Cause: softwareError


Component Id: GWC=GWC-###-UNIT-#;Version=;Unit=unit_#;

Software=NODE MTC

Specific Problem: This unit is approaching the uptime limitof 248 days.

Description: An automated maintenance action is scheduledfor this unit.


orVariable

Description


Variable




State Raise Variable

Indicates that the alarm israised.




Indicates the cause of thealarm. In this case, softwareerror.


Variable





Description

Example: Jan 26 15:14:252006



Example: GWC=GWC-8-UNIT-0;Version=GN091BH;Unit=unit_0;Software =NODE MTC


Identifies the specific cause forthe alarm.


Describes the specific causefor raising the alarm.




GWC325Log report GWC325 indicates that "Inactive unit refresh is in progress". Analarm will be raised after Routine Data Refresh Operation request ishandled at the inactive unit of the GWC and inactive unit refresh is startedsuccessfully. It will be cleared after inactive unit refresh is completed oraborted.


System impactDuring the inactive unit refresh the inactive unit will be in SYSB state.

Remedial actionThe status of the Data Refresh operation needs to be checked.

GWC325 63



Severity MinorType Communications AlarmProbablecause

Unspecified Reason

Format<OFFICE> GWC325 MMDD hh:mm:ss <sequence number> TBL GWCFault


NotificationID: <Notification ID>

State: Raise


Cause: Unspecified reason

Time: MM DD hh:mm:ss YYYY

Component ID: GWC=GWC-<node>-UNIT-<unit>; Version:<version>; Unit: <unit> Software: NODEMTC

Specific Problem: Alarm will be cleared when mtc is over

Description: Inactive unit refresh is in progress

GWC328Log report GWC328 is used to indicate that terminating call attempts arereached to overload levels.

When a burst of very high traffic is routed to a particular terminating GWC,the GWC internal resources (e.g. CPU, buffers, etc.) may exhaust andcause the GWC to enter an overload state.

The new emergency overload message is used to indicate the immediateoverload levels

of MAJOR, CRITICAL or NONE from the GWC to the Core. GWC alsoraises alarms for Major and Critical levels. A Major alarm is raised oncrossing the Warning Levels and critical alarm is raised on crossing thePanic Levels.



A duplicate alarm for the same reason as that of an existing one will not beraised.


Remedial actionMake sure that the terminating GWC traffic is reduced.


Log name GWC328Severity • Cleared

• Critical

• Major

Type Communications AlarmStatus set/clearProbablecause


Associatedcomponent

n/a

Format<OFFICE> <Severity> GWC328 MMMDD hh:mm:ss <sequence#> TBLGWC Fault

Location: <Location>

NotificationID: <NotificationID>

State: Raise

Category: <Category>

Cause: <Cause>

Time: MMM DD hh:mm:ss YYYY

Component Id: <Component id>

Specific Problem:<problem>

Description: GWC Overloaded

GWC328 65


<OFFICE> <Severity> GWC399 MMMDD hh:mm:ss <sequence#> INFOGWC Fault

Location: <Location>

NotificationID: <NotificationID>

State: Clear

Time: MMM DD hh:mm:ss YYYY

Component Id: <Component id>



orVariable

Description

NotificationID Integer Variable

A unique value assigned eachtime an alarm is raised.

Sequence# 0000-9999 Variable



Variable


Example: GWC-37-UNIT-0Severity Text description Variabl

eIdentifies the severity of thealarm.

"**" represents "major".

"***" represents "critical"

" " represents warning or clear.

Active message exampleMTOSSRTPI ** GWC328 SEP30 06:02:38 0038 TBL GWC Fault


NotificationID: 25

State: Raise


Cause: resourceAtOrNearingCapacity



Time: Sep 30 06:02:38 2010

Component Id: GWC=GWC-37-UNIT-1;Version=GC150BF;Unit=unit_1;Software=GWCOverloaded

Specific Problem: GWC is in Major Overload Level


MTOSSRTPI *** GWC328 SEP30 06:07:12 0040 TBL GWC Fault


NotificationID: 80

State: Raise


Cause: resourceAtOrNearingCapacity

Time: Sep 30 06:07:12 2010

Component Id: GWC=GWC-37-UNIT-0;Version=GC150BF;Unit=unit_0;Software=GWCOverloaded

Specific Problem: GWC is in Critical Overload Level


Clear message exampleMTOSSTMA2 GWC399 OCT01 12:56:21 1148 INFO GWC Fault


NotificationID: 25

State: Clear

Time: Oct 01 12:56:21 2010

Component Id: GWC=GWC-14-UNIT-0;Version=GC150BD;Unit=unit_0;Software=GWCOverloaded


GWC328 67


Associated logs


GWC351GWC351 log is generated when an ISUP trunk is datafilled on a line GWCin table "TRKMEM".

Remedial actionRemove the ISUP trunk datafill corresponding to line GWC from the table"TRKMEM" and "C7TRKMEM".


Severity WarningAssociatedcomponent

n/a

Legend n/a

Format<OFFICE> GWC351 MMDD hh:mm:ss <sequence number> NONE FLTDatafill


Component Id: GWC=GWC-<node>-UNIT-<unit>;Software=TRKMEMTable handler

Reason: ISUP trunks are not supported on this GWC


orVariable

Description

Office Alphanumeric Variable

11-character identifierindicating which office the logcomes from.

SequenceNumber

0000-9999 Variable


GWC node/unit alpha-numerictext label

Variable

Identifies the affected GWCnode and unit.



Associated logs


GWC399Log report GWC399 clears all other GWC logs.

In the case of H.323 GWCs, this log report is generated only for H.323gateways that contain 64 endpoints or greater.

Remedial actionn/a


Severity Warning

FormatMSH10_IO6BR GWC399 MAY26 13:38:30 0529 INFO GWC Fault


NotificationID: 6

State: Clear

Time: May 26 13:38:40 2003




GWC501Log report GWC501 indicates a connection fault between the GatewayController (GWC) and a gateway configured with NCS or MGCP signalingprotocol. The fault requires investigation.

Remedial actionVerify the availability of the gateway and compare the configuration data atthe gateway and the CS 2000 GWC Manager (IP address, protocol,protocol version, and so on).

GWC501 69




Format<OFFICE>GWC501 MMMDD hh:mm:ss<sequence number>PBSY SSC LOGMESSAGE

Location:<GWC node/unit>

Component Id: GATEWAY=<MG_name>GWIP:<MG_IP>

Reason:<fault_reason>


orVariable

Description

sequencenumber

0000-9999 Variable


GWC node/unit alpha-numericcharacter string

Variable

Identifies the GWC node andunit affected by the failure.

Example: GWC-8-UNIT-0MG_name alpha-numeric

character stringVariable

Name of the media gateway(MG) associated with theGWC card and affected by theconnection fault.

Example: SLOA118-0-3MG_IP numeric Variabl

eIP address of the mediagateway

Example: 123.1.2.3fault_reason text description Variabl

eProvides more informationabout the connection fault.

Example: GW failed torespond to HeartBeat/Audit.






GWC502Log report GWC502 indicates that service is restored to the referencedgateway.

This log report refers only to gateways configured with NCS or MGCPsignaling protocol.

Remedial actionn/a



Format<OFFICE>GWC502 MMMDD hh:mm:ss<sequence number>RTS SSC LOGMESSAGE


Component Id: GATEWAY=<MG_name>GWIP:<G_IP>

Reason:<reason><MG_name>


orVariable

Description

sequencenumber

0000-9999 Variable



Variable

Identifies the GWC node andunit where the gatewayconnection was restored.



Name of the media gateway(MG) associated with theGWC card that has theconnection restored.


eIP address of the mediagateway.

GWC502 71



Description

Example: 123.1.2.3reason text description Variabl

eProvides more information,including the name of thegateway to which theconnection was restored.

Example: Connection toremote gateway restored:SLOA23.




GWC503 Format 1Log report GWC503 indicates one of the following:

• the gateway dropped the connection to the associated GWC (forgateways configured with NCS or MGCP signalling protocol)

• the gateway attempts to reestablish a lost connection (for gatewaysconfigured with DQoS TCP/COPS and connected to PEP/VCACservers)

The DQoS version of the log format occurs only when the maximum DQoSalarm threshold of 21 major alarms is exceeded.

Remedial actionn/a


Severity Major

Format<OFFICE>GWC503 MMMDD hh:mm:ss<sequence number>OFFL SSC LOGMESSAGE




Component Id: GATEWAY=<MG_name>GWIP:<G_IP>

Reason:<reason><MG_name>


orVariable

Description

sequencenumber

0000-9999 Variable



Variable

Depending on theconfiguration, this field either:

• identifies the GWC nodeand unit to which thegateway dropped theconnection (for NCS orMGCP)identifies the GWCnode and unit to which itattempts to reestablish alost connection (for DQoS)

MG_name alpha-numericcharacter string

Variable

Name of the media gateway(MG) that dropped theconnection with the associatedGWC.




eDepending on theconfiguration, this field either:

• provides more informationabout the connection drop,including the name of thegateway that initiated it(for NCS or MGCP).

Example: Connection dropinitiated by remote gateway:SLOA23.

• provides information aboutthe attempted TCP Socketrecovery, including thenode

GWC503 Format 1 73





GWC503 Format 2Log report GWC503 indicates one of the following:




Remedial actionn/a


Severity Major

Format<OFFICE>GWC503 MMMDD hh:mm:ss<sequence number>NONE OFFL DQOSLOG MESSAGE


Component Id: DQoS Connection Failure

Reason: Attempting TCP Socket recovery to node<Node_name&IP>




orVariable

Description

sequencenumber

0000-9999 Variable



Variable

Depending on theconfiguration, this field either:

• identifies the GWC nodeand unit to which thegateway dropped theconnection (for NCS orMGCP)identifies the GWCnode and unit to which itattempts to reestablish alost connection (for DQoS)

MG_name alpha-numericcharacter string

Variable

Name of the media gateway(MG) that dropped theconnection with the associatedGWC.




eDepending on theconfiguration, this field either:

• provides more informationabout the connection drop,including the name of thegateway that initiated it(for NCS or MGCP).

Example: Connection dropinitiated by remote gateway:SLOA23.

• provides information aboutthe attempted TCP Socketrecovery, including thenode



GWC503 Format 2 75



GWC506Log report GWC506 indicates that an H.323 GWC unit has lost theconnection to an H.323 gateway. The log entry identifies the specificproblem and describes the reason for the failure.

This log report recommends a set of actions that depend on the specificproblem and reason for the problem.

This log report is generated only for H.323 gateways that contain less than64 endpoints.

Remedial actionThe following describes the actions the user may take when a GWCexperiences a loss of connection to an H.323 gateway.

Gateway Unregistration by CS2K Successful

• No action required.

• The craftsperson has busied the D-channel for the H.323 gateway, orthe CS 2000 has busied the D-channel for H.323 gateway due amaintenance action such as GWC cold SWACT, CS 2000 restartreload, etc.

Time to Live Expired

• The H.323 gateway failed to refresh the 30 second keepalive timer inthe CS 2000 GWC.

• Verify communication between the gateway and the GWC. Ifnecessary, check the H.323 gateway itself since the CS 2000 GWCunregistered the H.323 gateway because the Time To Live value hasexpired.

Gateway Initiated Unregistration Successful

• The H.323 gateway initiated the unregistration from the CS 2000 forsome reason.

• Action on the H.323 gateway side may be warranted if theUnregistration was unplanned.


Severity WarningType Communications



Format<OFFICE>GWC506 MMDD hh:mm:ss<sequence number>INFO

PBSY Gateway State Change


Component Id: GWC=<GWC node/unit>;LINK=<gateway name>

Category: Communication

Specific Problem: H323 Connection lost to H323 gateway:

<gateway name>

Description:<reason for problem>

MTOSSCOM4 GWC506 FEB24 13:19:13 4593 INFO PBSY Gateway StateChange


Component Id: GWC=GWC-44-UNIT-1;LINK=T38HORIG1



T38HORIG1

Description: Gateway Unregistration by CS2K GK Successful


orVariable

Description

OFFICE alphanumeric Variable

A string indicating the officethat generated the log report.

sequencenumber

0000-9999 Variable

Four digit sequence numberidentifying a specific log entry.

GWC node / unit Alpha-numerictext label

Variable


Example: GWC-11-UNIT-0

GWC506 77



Description

gateway name Alpha-numerictext label

Variable

Identifies the gatewayconnected to the GWC cardaffected by the failurecondition.

Example: BCM_RTPG1reason forproblem

Text description Variable

Describes the specific reasonfor the failure.

Active message exampleMTOSSCOM4 GWC506 FEB24 13:19:13 4593 INFO PBSY Gateway StateChange





T38HORIG1

Description: Gateway Unregistration by CS2K GK Successful



GWC507Log report GWC507 indicates that the connection between a GWC and anH.323 gateway has been restored.


Remedial actionNo action is required.

You may verify that the D-channel has gone in service (INSV) at theMAPCI;MTC:TRKS; TTP; PRADCH; POST GD<trkname>. If any trunkmembers are provisioned and you wish to be able to make calls, thencheck the trunk members to see that they are also idle (IDL).




Severity WarningType Communications

Format<OFFICE>GWC507 MMMDD hh:mm:ss<sequence number>INFO

RTS Gateway State Change




Specific Problem: H323 Connection restored to

H323 gateway:<gateway name>

Description: Gateway Registration Successful

MTOSSCOM4 GWC507 FEB24 13:19:30 4629 INFO RTS Gateway StateChange





H323 gateway: T38HORIG1



orVariable

Description


A string indicating the officethat generated the log report.

sequencenumber

0000-9999 Variable

Four digit sequence numberidentifying a specific log entry.

GWC507 79



Description

GWC node / unit Alpha-numerictext label

Variable


Example: GWC-11-UNIT-0gateway name Alpha-numeric

text labelVariable


Example: BCM_RTPG1

Active message exampleMTOSSCOM4 GWC507 FEB24 13:19:30 4629 INFO RTS Gateway StateChange





H323 gateway: T38HORIG1




GWC508Log report GWC508 indicates that a GWC unit has lost the connection to aVOIP VPN virtual media gateway (vmg) . The log entry identifies thespecific problem and describes the reason for the failure.


This log report is generated only for vmgs that contain less than 64endpoints configured in the associated trunk group in the CS2K. Otherwiseexisting gw communication lost alarms are used.



System impactNo VOIP VPN calls can be made using the trunks associated with theaffected vmg.

Remedial actionBsy then rts the associated D-chnl for the vmg.

Verify the provisioning in the MCP System Manager for the vmg to ensurethat it is hosted by the correct GWC in regards to ip addresses.


Severity MajorType Communications AlarmStatus setProbablecause


Format<Office> GWC508 GWC508 AUG02 14:18:28 8719 PBSY VMG StateChange


Component Id: GWC=<gwc unit>; LINK=<vmg name>

Specific Problem: <problem>

Description: <message>

GWC508 81



orVariable

Description

Component Id GWC Variable

This field identifies the GWCnode/unit name that isconfigured on the SAM21Manager and the GWCManager

Specific Problem problem Variable

This field indicates that thecommunication connection islost to the specified VoIP VPNvmg.

Description message Variable

This field indicates one of thepossible reasons for the PBSYVMG State Change.

Active message exampleRTPG GWC4 GWC508 AUG02 14:18:28 8719 PBSY VMG State Change


Component Id: GWC=GWC-4-UNIT-0;LINK=VMG1SESM5

Specific Problem: VoIP VPN Connection lost to VMG1SESM5

Description: D-CHNL MAN BUSY by CS2K Successful

GWC509Log report GWC509 indicates that a GWC unit has restored connection toa VOIP VPN virtual media gateway (vmg) .

This log report is generated only for vmgs that contain less than 64endpoints configured in the associated trunk group in the CS2K. Otherwiseexisting gw communication lost alarms are cleared.

System impactVOIP VPN calls may be possible using the trunks associated with thespecified vmg.

Remedial actionNone




Severity MajorType Communications AlarmStatus setProbablecause


Format<Office> GWC509 GWC509 AUG02 14:18:28 8719 RTS VMG StateChange


Component Id: GWC=<gwc unit>; LINK=<vmg name>

Specific Problem: <problem>

Description: <message>


orVariable

Description

Component Id GWC Variable

This field identifies the GWCnode/unit name that isconfigured on the SAM21Manager and the GWCManager

Specific Problem problem Variable

This field indicates that thecommunication connection isrestored to the specified VoIPVPN vmg.

Description message Fixed This field indicates that the D-Chnl for the associated trunkgroup has been RTSed.

Active message exampleRTPG GWC4 GWC509 AUG02 14:18:28 8719 RTS VMG State Change


Component Id: GWC=GWC-4-UNIT-0;LINK=VMG1SESM5

Specific Problem: VoIP VPN Connection restored to VMG1SESM5

GWC509 83


Description: D-Chnl INSV

GWC600Log report GWC600 is an information log for an H.323 failure. The logentry identifies the specific problem and describes the reason for thefailure.


This section provides examples of Core logs relevant to

• Specific problem: H323 RRQ rejected

• Description: D-Channel Out Of Service.

Examples of Core logs when the D-channel is manually busied (BSY):

RTPG * ISDN105 JUN16 21:45:44 2311 FLT PRA Sync Loss

ISP = 0 GWC 11 PORT 0 CHNL 0

RTPG *** ISDN112 JUN16 21:45:44 2412 INFO PRA D-CHANNEL

CRITICAL ALARM RTPG_BCM_LOCAL DCH=GWC 11 120 1 : OOS

RTPG *** TRK103 JUN16 21:45:49 2917 FLT GROUP_ALARM

RTPG_BCM_LOCAL 100% BUSY

Examples of Core logs when the D-channel is returned to service (RTS)and the gateway registers with GWC:

RTPG ISDN118 JUN16 21:46:52 6654 INFO PRA Sync Established

ISP = 0 GWC 11 Port 0 Chnl 0

RTPG TRK104 JUN16 21:46:56 7462 INFO GROUP OK

RTPG_BCM_LOCAL

Remedial actionThe following describes the actions the user takes when an H.323 failurecondition occurs.

GRQ = Gatekeeper request

RRQ = Registration request



ARQ = Admission request

URQ = Unregistration request

DRQ = Disengage request

RAS = Registration, admission and status

H323 GRQ rejected - Gateway Name Not Provisioned

Ensure that the H.323 gateway name provisioned on the CS 2000 GWCManager matches exactly with the gateway name provisioned using theH323 GW provisioning tool.

A log with same description is generated for RRQ received with invalid GWname.

H323 GRQ rejected - Gateway IP Address Invalid

A log with same description is generated for RRQ received with an invalidsource gateway IP address. In this case, the source IP address is the IPaddress in the ethernet frame. So, for gateways behind the NAT, thesource IP address will be the NAT IP address.

The RAS IP address is not part of the H.323 payload. If the H.323 gatewayis not behind a NAT, the source IP will be the IP address of the H.323gateway.

If the H.323 gateway is behind the NAT, ensure that the H.323 gateway IPaddress provisioned on the CS 2000 GWC Manager matches exactly theIP address of the NAT box.

If the H.323 Gateway is not behind a NAT box, ensure that the H.323gateway IP address provisioned on the CS 2000 GWC Manager matchesexactly the IP address of the H323 gateway.

H323 GRQ rejected - Gateway Port Invalid

A log with same description is generated for an RRQ received with aninvalid source gateway port. In this case, the source port is the source portaddress in the ethernet frame. So, for gateways behind a NAT, the sourceport is the port entry of the static bind at the enterprise NAT for the H323gateway. It is not the RAS port which is part of the H323 payload.

If the H323 Gateway is not behind a NAT, the source port will be the RASport of the H323 gateway.

GWC600 85


If the H.323 gateway is behind the NAT, ensure that the H.323 gatewayport provisioned on the CS 2000 GWC Manager matches exactly the portentry of the static bind at the enterprise NAT for the H323 gateway.

If the H.323 Gateway is not behind a NAT box, ensure that the H.323gateway IP address provisioned on the CS 2000 GWC Manager matchesexactly the IP address of the H323 gateway.

H323 GRQ rejected - Missing Mandatory RAS Address

No action needed. This log report is for information only.

H323 RRQ rejected - Incorrect Endpoint Identifier Syntax


H323 keepAlive RRQ rejected - Incorrect Endpoint Identifier Syntax


H323 RRQ rejected - Invalid Endpoint Identifier


H323 ARQ rejected - Invalid Endpoint Identifier


H323 RRQ rejected - D-Channel Not Provisioned

Ensure that the trunk datafill is provisioned correctly on the CS 2000 Coreand CS 2000 GWC Manager.

H323 RRQ rejected - D-Channel Out Of Service

Ensure that the D-channel associated with the H.323 gateway is in LOstate at mapci, mtc, ttp, trks, pradch level on the CS 2000 Core before theH.323 gateway registers.

This log can be cleared with a BSY/RTS of the D-channel associated withthe H.323 gateway on the CS 2000 Core.

Trunk logs are also generated which are similar to PRI trunk logs.

For example, H.323 gateway "BCM_RTPG" appears on the Core as trunkname "RTPG_BCM_LOCAL"

Refer to section "Additional information"



for examples of Core logs.

H323 RRQ rejected - Table LTDATA Needs H323 Option

Check the datafill in Table LTDATA on the CS 2000 Core. The optionPRI_IP_PROT H323 should be present for the D-channel associated withthe H.323 gateway.

H323 RRQ rejected - Max Gateways Registered


The CS 2000 GWC has reached the maximum limit for the number of H.323 gateways it can have registered simultaneously.

H323 ARQ rejected - B-Channel Resource Unavailable

Ensure that B-channels associated with the gateway are idle (IDL) atmapci, mtc, ttp, trks level on the CS 2000 Core. This log can be clearedwith a BSY/RTS of the B-channels associated with the H.323 gateway onthe CS 2000 Core.

If all the B-channels associated with the H.323 gateway are call processingbusy (CPB) at mapci, mtc, ttp, trks level on the CS 2000 Core, then noaction is needed. There is no B-channel available for the call. This logreport is for information.

H323 RRQ rejected - No GWC Unit Active Running

A log with the same description will be generated if any RAS message(GRQ, RRQ, ARQ, URQ, DRQ) is received when the GWC unit is notactive running. This log can be cleared with a BSY/RTS of GWC unit.

Ensure that the CS 2000 GWC is in active running state.

This log can be cleared with a BSY/RTS of GWC unit.

H323 DRQ rejected - Request to Drop Non Existent Call


This reports a disengage request for a call which is not active or non-existent.

H323 URQ rejected - Endpoint Not Registered

A RAS request is received from a H.323 gateway which is not registeredon the CS 2000 GWC.

GWC600 87


Verify that the H.323 gateway is provisioned on the CS 2000 GWC.

H323 Call rejected - Codec Mismatch With CS2K

Ensure that at least one of the codecs provisioned on the H323 gatewaymatches the codec for the CS 2000 provisioned at the CS 2000 GWCManager.

H323 Call rejected - Codec / Payload Mismatch With CS2K

Ensure that at least one of the codecs provisioned on the H323 gatewaymatches the codec for the CS 2000 provisioned at the CS 2000 GWCManager.

Ensure that the payload (packetization) time on the H323 gatewaymatches the payload (packetization) for the CS 2000 provisioned at the CS2000 GWC Manager.

H323 Call rejected - H245 Tunneling Not Enabled On Gateway

Ensure that H.245 tunneling is enabled on the H.323 gateway.


Severity • Warning

• Critical

Type Communications

Format<OFFICE>GWC600 MMMDD hh:mm:ss<sequence number>INFO GWCProtocol Event





Description:<reason for problem>

COM4 GWC600 FEB14 23:55:51 0415 INFO GWC Protocol Event




Component Id: GWC=GWC-44-UNIT-0;LINK=HURR02


Specific Problem: H323 Call Rejected

Description: Codec / Payload Mismatch With CS2K


orVariable

Description

OFFICE Alphanumeric Variable


sequencenumber

0000 to 9999 Variable


GWC node/unit Alphanumerictext label

Variable


Example: GWC-11-UNIT-0gateway name Alphanumeric

text labelVariable


Example: BCM_RTPG1specific problem Text description Variabl

eIdentifies the H.323 failurecondition (see the table belowfor a list of possible values andcorresponding user actionsrequired).

reason forproblem

Text description Variable

Describes the specific reasonfor the failure.




GWC601Log report GWC601 is an information-only log that indicates the change ofthe Gateway Controller (GWC) Manager IP address.

GWC601 89


This log report is available on both Managers:

• the one that is currently associated with the GWC

• the one that served the GWC before the configuration changed

This log event is extremely rare. If it occurs, treat it as a sign of possiblesecurity problem.

Remedial actionNo action required.


Severity Warning

Format<OFFICE>GWC601 MMMDD hh:mm:ss<sequence number>INFOConfiguration Change


Component Id: GWC=<GWC node/unit>;Software=SystemConfig

Changed value: Element Manager address

Previous:<previous_EM_IP>New:<current_EM_IP>


orVariable

Description


11-character identifierindicating the office thatgenerated the log report.

sequencenumber


Four-digit sequence numberwhich can be used for lost logdetection.

GWC node/unit alphanumericcharacter string

Variable

Identifies the GWC node andunit for which the configurationchange occurred.




Description

previous_EM_IP numeric Variable

IP address of the Manager thatserved the GWC before theconfiguration changed.

current_EM_IP numeric Variable

IP address of the Manager thatis currently serving the GWCafter the configuration change.




GWC603Log report GWC603 is an information-only log and there is no alarmassociated with it. Log GWC603 indicates that a netfail event occurred onthe gateway and it was reported to the Gateway Controller (GWC).

Remedial actionNo action required. This log report provides additional information whenTRK113 or LINE104 log is generated on the Core as a result of netfailevent received from H.248 gateways.


Severity Warning

Format<OFFICE> GWC603 MMMDD hh:mm:ss <sequence_number> INFONETFAIL EVENT


Component Id: GATEWAY=<MG_name> GWIP:<MG_IP> ENDPOINT ID:<Epid>

TID: <Tid> Reason: <Exception Reason>

GWC603 91



orVariable

Description

sequence_number

0000-9999 Variable


GWC node-unit alpha-numericcharacter string

Variable

GWC node and unit affectedby the failure.

Example: GWC-11-UNIT-0MG_name alphanumeric


Name of the media gatewayassociated with the GWC cardaffected by the failurecondition.

MG_IP numeric Variable

IP address of the mediagateway.

Example: 123.1.2.3Epid alphanumeric


Identifier of the endpoint thatcaused the exception.

Example: tp/0/0028Tid numeric Variabl

eInternal Terminal IDmaintained by the GWC.

Example: 4125ExceptionReason

alphanumericcharacter string

Variable

The cause of the netfail event.

Example: 599 Connection Lost




GWC604Log report GWC604 is an information-only log and there is no alarmassociated with it. This report indicates an internal Gateway Controller(GWC) exception. Use this log report for debugging process.

Remedial actionNo action required. Usually (but not always) this log report is generated inconjunction with log report TRK113 or LINE104 on the Core. Use both logreports for debugging process.




Severity Warning

Format<OFFICE> GWC604 MMMDD hh:mm:ss <sequence_number> INFO GWCEXCEPTION EVENT


Component Id: GATEWAY=<MG_name> GWIP:<MG_IP> ENDPOINT ID:<Epid>

TID: <Tid> Reason: <Exception Reason>


orVariable

Description

sequence_number

0000-9999 Variable


GWC node-unit alpha-numericcharacter string

Variable

GWC node and unit affectedby the failure.



Name of the media gatewayassociated with the GWC cardaffected by the failurecondition.

MG_IP numeric Variable

IP address of the mediagateway.

Example: 123.1.2.3Epid alphanumeric


Identifier of the endpoint thatcaused the exception.

Example: tp/0/0028Tid numeric Variabl

eInternal Terminal IDmaintained by the GWC.

Example: 4125ExceptionReason

alpha-numericcharacter string

Variable

The reason for raising theexception.

Example: InsufficientBandwidth

GWC604 93





GWC605Log report GWC605 indicates that the M3UA Application Server Process(ASP) path audit has detected all the ASP paths in the down state for tenminutes. When this happens, the system initiates an autonomous SWACTrequest.

Remedial actionGWC605 log reports that a warm SWACT request is initiated if the M3UAASP paths are down for ten minutes. The warm SWACT attempts torecover the M3UA links and bring back the trunks into service. No specificaction is required, as the event takes place automatically.


Severity Warning

Format<OFFICE>GWC605 MMMDD hh:mm:ss<sequence number>INFO M3UAEVENT


Component Id: GWC=<GWC node/unit>;Software=M3UA_ASP_AUDIT

Event: Autonomous Swact Request

Reason: M3UA ASP paths down




orVariable

Description



sequencenumber




Variable

Identifies the GWC node andunit affected by the event.

Event Text description Variable

Indicates that the eventAutonomous Swact Request isinitiated.

Reason Text description Variable

Indicates the reason for thelog: the M3UA ASP paths aredown for ten minutes.

Active message exampleCOM4 GWC605 JAN04 16:29:54 9129 INFO M3UA EVENT


Component Id: GWC=GWC-34-UNIT-0;Software=M3UA_ASP_AUDIT


Reason: M3UA ASP paths down



GWC606Log report GWC606 is an information log for a Media Proxy (MP) idle orlong call detection event. Idle and long call durations are measured interms of audit periods, which the user can define in the Media Proxyelement manager.

The log contains a correlation ID passed down from the Core. Thiscorrelation ID is used for correlation with an associated billing record forthat call. In (I)SN09FF this is the only mechanism available to linkgenerated logs with particular billing records.

GWC606 95


Remedial actionThe user should review the contents of the log report and take action asshown in the following .

Long Call Detected - Call longer than long call duration defined in MediaProxy element manager.

Use the correlation ID in the log to identify the associated billing record forthat call.

Idle Call Detected - Call longer than idle call duration defined in MediaProxy element manager.


In order to associate the correlation ID with a particular billing record, theQuality of Service feature must be configured and activated.


Severity Warning

Format<OFFICE>GWC606 MMMDD hh:mm:ss<sequence number>INFO MediaProxy


Component Id: MEDIA PROXY=<MP_name>

Reason:<Long/Idle>Call Detected, CorrelationID=<CorrelationId>


orVariable

Description



sequencenumber






Description


Variable

Identifies the GWC node andunit affected by the event.

MP_name Alphanumericcharacter string

Variable

The name of the Media Proxyfor which the long or idle callhas been detected.

Long/Idle Alphabetic; Longor Idle

Variable

Identifies the type of call (longcall or idle call) detected.

Correlation Id Numeric Variable

30-digit number used forcorrelation with an associatedbilling record for that call.

Active message exampleCS2K5 GWC606 FEB16 02:52:09 3592 INFO Media Proxy


Component Id: MEDIA PROXY=SAM16P4

Reason: Long Call Detected,CorrelationID=111000223111000157247241006000

CS2K5 GWC606 FEB16 02:52:09 3593 INFO Media Proxy



Reason: Idle Call Detected,CorrelationID=111000223111000157247241006000

enterprise=1.3.6.1.4.1.562.29.6.1.0.306

uptime=26274273

agent_ip=47.129.118.161

version=Ver2

1.3.6.1.4.1.562.29.6.1.3.1.1=.0.0

1.3.6.1.4.1.562.29.6.1.3.1.2="IEMS=0x00000063000000a10a68011a-GWC-3-UNIT-0;MEDIA PROXY=SAM16P4"

GWC606 97


1.3.6.1.4.1.562.29.6.1.3.1.3="Hex String=07 D6 02 10 02 3409 00 2D 05 00"

1.3.6.1.4.1.562.29.6.1.3.1.4=GWC606

1.3.6.1.4.1.562.29.6.1.3.1.5=" 52 GWC 606 3591 INFO MediaProxy<010><013>Long Call Detected,CorrelationID=111000223111000157247241006000"

enterprise=1.3.6.1.4.1.562.29.6.1.0.306

uptime=26274273

agent_ip=47.129.118.161

version=Ver2

1.3.6.1.4.1.562.29.6.1.3.1.1=.0.0

1.3.6.1.4.1.562.29.6.1.3.1.2="IEMS=0x00000063000000a10a68011a-GWC-3-UNIT-0;MEDIA PROXY=SAM16P4"

1.3.6.1.4.1.562.29.6.1.3.1.3="Hex String=07 D6 02 10 02 3409 00 2D 05 00"

1.3.6.1.4.1.562.29.6.1.3.1.4=GWC606

1.3.6.1.4.1.562.29.6.1.3.1.5=" 52 GWC 606 3592 INFO MediaProxy<010><013>Idle Call Detected,CorrelationID=111000223111000157247241006000"

52 GWC 606 3591 INFO Media Proxy



Reason: Long Call Detected,CorrelationID=111000223111000157247241006000

52 GWC 606 3592 INFO Media Proxy



Reason: Idle Call Detected,CorrelationID=111000223111000157247241006000



Feb 16 16:10:59 zcary0tn IEMS:_V2_~I=~H=zcary0tn~A=IEMS~S=3986~~ GWC606 NONE INFO MediaProxy^M Location: GWC-3-UNIT-0^M Component Id: MEDIAPROXY=SAM16P4^M Reason: Long Call Detected,CorrelationID=111000223111000157247241006000

Feb 16 16:10:59 zcary0tn IEMS:_V2_~I=~H=zcary0tn~A=IEMS~S=3987~~ GWC606 NONE INFO MediaProxy^M Location: GWC-3-UNIT-0^M Component Id: MEDIAPROXY=SAM16P4^M Reason: Idle Call Detected,CorrelationID=111000223111000157247241006000



GWC607Log report GWC607 is an informational log generated by the GWC to theIEMS to identify lines where IP Call Recording is requested but could notbe performed (because the Border Control Point 7200 (BCP 7200) isunavailable or is not provisioned, or because the BCP 7200 has insufficientresources). The GWC607 log report is generated for the followingprotocols:

• Nortel Standard (NTSTD)

• Switching Control Center 2 (SCC2)

• Syslog

• Simple Network Management Protocol (SNMP)

Remedial actionLog report GWC607 is an informational GWC log used to correlateinformation provided by the BCP 7200 and the IP Call Recording device.


Severity Warning

FormatGWC607 MAY26 10:38:22 0040 INFO BCP REPLICATION EVENT


Component Id: GATEWAY=rtp7-1104a.us.nortel.com GWIP:47.142.92.200

GWC607 99


ENDPOINT ID: aaln/1 TID: 4097

Reason: BCP not available or provisioned


orVariable

Description

Reason BCP notavailable orprovisionedreceived

Variable

No BCP 7200 is available toinsert for replication.

DuplicateRecordingRequest

Variable

A duplicate recording requestwas received and ignored.

Field Value Variable

Description




GWC608Log report GWC608 is a Syslog that is generated when a call signalingfailure occurs. Log report GWC608 can be correlated to the XPKT300 logusing the Correlation ID field, and provides additional troubleshootinginformation to the XPKT300 log.

The GWC608 log report is generated for faults that previously generated aGWC603 or a GWC604 log. The GWC603 and GWC604 logs are nolonger generated.

Remedial actionThe failure should be investigated to determine any necessary actions.


Severity Warning



FormatFeb 4 10:52:21 [47.142.92.146] GWC: _V2_~I=GWC14~H=GWC-14-UNIT-1~A=GWC~S=0001~~ GWC608 INFO GWC Signaling Failure^M

Location: GWC-1-UNIT-1^M

Component Id: GWC Manager=47.143.164.20;GWC Card=GWC-1-UNIT-1^M

CID: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000 00^M

QCA CID: 012345678901234567890123456789^M

Media Gateway: PVG02^M

Endpoint: DS1/1/1^M

Reporting TID: 38 658^M

Far-end TID: 41 854^M

Far-end Media Address: 47.142.99.192^M

Reporting Device: MG^M

Application: MEGACO^M

Failure Reason: 432^M

Text: No more termination IDs available^M


orVariable

Description


Description

Location String Variable

The Gateway Controller(GWC) card reporting thefailure.

Component Id String Variable

The CMT and the GWC cardreporting the failure.

CID 20 bytes Variable

Hex bytes with a blank spacebetween each byte.

GWC608 101



Description

QCA CID Numeric Variable

The existing QCA correlationID. It is reverse engineeredbased on the CID above asthe QCA CID is a subset of theCID. The QCA CID is printedas 30 decimal digits with nospacing, and is used to matchup billing records that containthis same CID.

Media Gateway String Variable

Name of the Media Gateway(MG).

Endpoint String Variable

The endpoint name.

Reporting TID Numeric Variable

The node and terminalnumbers of the reportingTerminal ID (TID).

Far End TID Numeric Variable

The node and terminalnumbers of the connected TID.

Far-end Media IPAddress

String Variable

The IP or ATM address of thefar-end device.

Reporting device String Variable

The device that initiallydetected the signaling failure,either the GWC or the MG.

Application String Variable

The application (within thereporting device) that detectedthe signaling failure.

Failure Reason Numeric Variable

The failure reason reported bythe application.

Text String Variable

The text reason reported bythe application.






GWC609Log report GWC609 is an information log that is generated when theGateway Controller (GWC) detects communication issues with an in-service trunk or large capacity line gateway. This occurs for the first missedheartbeat reply and when communication lost is declared for a gateway. Inthe later case, an accompanying GWC304 trouble log is also generated.

The GWC609 log contains the output of a traceroute command performedfrom the GWC to the IP address of the gateway. For traceroute to functionend-to-end, ICMP protocol must be allowed to pass through all routers andfirewalls between the GWC and the gateway.

The personnel that support the network path between the GWC andgateway may use this log to determine if action is required to restore ormaintain communication from the GWC to gateway.

Remedial actionNo action is required. The traceroute hop data can be used to help identifynetwork issues that may be causing communication problems between theGWC and gateway.


Severity Warning

Format<OFFICE>GWC609 MMMDD hh:mm:ss<sequence number>INFOTraceroute


Component Id: GWC Card=<GWC node/unit>;GATEUAY-<Gateway)

Description: Traceroute to<Gateway IP><Status>.

<Result>.

Hop Data (rtt in Ms):

1 47.142.64.1 0

2 47.142.204.205 2

3 47.143.206.21 5

GWC609 103


4 47.143.205.1 10

5 *

6 *

7 *


orVariable

Description

Field Values Variable

Description



sequencenumber




Variable

Identifies the GWC node andunit where the tracerouteoriginated from. Example:GWC-3-UNIT-1

Gateway Alphanumerictext label

Variable

Identifies the name of thegateway for which thetraceroute is being executedfor. This gateway name willmatch the gateway name seenin the GWC Manager.

Gateway IP IPv4 IP address Variable

Identifies the IP address forthe Gateway which thetraceroute is being executedfor. Example: 47.135.21.3

Status Executed orAborted

Variable

Identifies the summary statusof the traceroute.

Result Alphanumerictext label

Variable

Explanation for the result ofthe traceroute. Abortedexplanations: "Running longerthan 5 seconds" or "Max of 20hops exceeded." Executedexplanations: "Could not reachdestination." or "Destinationreached. Last GW signalingmsg received<x>secs ago."




Description

For the case where thetraceroute successfullyreached the destination, thelog also includes how manyseconds have elapsed fromwhen the traceroute completedand the GWC last received amessage from the gateway onits signaling (e.g., H.248) path.

The log also includes the hopdata with the round-trip time inmilliseconds. A time out for ahop is indicated by an asterisk.




GWC610Log report GWC610 is an informational log that is generated when a NilCodec condition is detected (that is, when a codec profile table on theGWC is corrupted or is not provisioned, and as such the GWC cannotactively participate in any call).



Severity Warning

FormatMay 30 09:11:05 [172.16.16.26.128.136] GWC:_V2_~I=GWC0~H=GWC-0-UNIT-0~A=GWC~S=0002~~ GWC610 NONE INFOGWC^


GWC610 105


Component Id: Nil Codec

Condition detected


orVariable

Description


Description

Location GWC-<number>UNIT-(unitnumber>

Variable

The GWC unit in which theCodec table is NIL.

Component ID NIL Codec Variable

The problem description.

Reason Conditiondetected

Variable

Currently, this is the onlyreason that is displayed.




GWC611Log report GWC611 is an informational log that is generated when amismatch occurs between RAM and Flash on a Gateway Controller(GWC), and an Autonomous SWACT Request is triggered. There is noalarm associated with this log.

An example of log report GWC611 is as follows:

RTP2 GWC611 May23 04:56:36 8736 INFO PDATAAUDIT EVENT


Component Id: GWC=GWC-2-UNIT-1;Software=PDATA_RAM_FLASH_AUDIT


Reason: Data mismatch between Ram and Flash



Remedial actionNo immediate action is required. This log is informational and is intendedto inform customers that an Autonomous SWACT was requested due to adata mismatch in the GWC.


Severity Warning

FormatMay 23 05:06:33 nc0rtp215.us.nortel.com GWC:_V2_~I=GWC2~H=GWC-2-UNIT-1~A=GWC~S=8783~~ GWC611 NONE INFOPDATAAUDIT EVENT^M

Location: GWC-2-UNIT-1^M

Component Id: GWC=GWC-2-UNIT-1;Software=PDATA_RAM_FLASH_AUDIT^M

Event: Autonomous Swact Request^M

Reason: Data mismatch between Ram and Flash


orVariable

Description


Description

Location GWC-<number>-UNIT-<unitnumber>

Variable

The GWC unit in which thedata mismatch between RAMand Flash occurred.

Component ID GWC=GWC-2-UNIT-1;Software=PDATA_RAM_FLASH_AUDIT

Variable

The problem description.

Reason Data mismatchbetween Ramand Flash

Variable

The reason for the datamismatch.



GWC611 107



GWC612The GWC612 log report is a warning log and is not associated with anyalarms. This log report is first generated when the GWC reaches 95% ofthe maximum number of ATHB resources due to a large number ofsimultaneous calls. Subsequently, when the GWC reaches 100% of themaximum number of ATHB resources, this log report is generated forevery new call attempt.

Log report GWC612 is available under customerlogs on the CS 2000Management Tools server.

Remedial actionSplit the resources over multiple GWC nodes. If required, contact Norteltechnical support for assistance.


Severity • Warning

• Major

Format<OFFICE>GWC612 MMDD hh:mm:ss<sequence number>NONE INFO GWCATHB_IDX


Component Id: ATHB Index<Utilized Level Description>

<OFFICE>GWC612 MMDD hh:mm:ss<sequence number>MAJOR FAIL GWCATHB_IDX


Component Id: ATHB Index<Utilized Level Description>

RTPG GWC612 Jan04 11:03:47 1234 MAJOR FAIL GWC ATHB_IDX


Component Id: ATHB Index No Free ATHB




orVariable

Description

sequencenumber

0000-9999 Variable



Variable

Identifies the affected GWCnode and unit.

Example: GWC-40-UNIT-1Utilized LevelDescription

character string Variable

Is either "ATHB usageexceeded 95%" or "No FreeATHB".

Active message exampleRTPG GWC612 Jan04 11:03:47 1234 MAJOR FAIL GWC ATHB_IDX


Component Id: ATHB Index No Free ATHB



IPSec security logsThis section describes how to access and understand IPSec security logreports associated with GWC nodes. These log reports are stored in thesecuritylog files in directory /var/log on the CS 2000 Management Toolsserver.

To display IPSec log reports, search for the text string ISAKMP within thesecuritylog files.

The format for IPSec log reports is as follows:

Remedial actionn/a


Severity Warning

IPSec security logs 109


Formatmmm dd hh:mm:ss [<IP address>] class_security.ver01CMD="<log message>, #PKTs :<# pkts>, SRCIP :<IP>,DSTIP :<IP>, SPI =<SPI>" STAT=<status>MID=<MID>


orVariable

Description

mmm ddhh:mm:ss

alphanumeric Variable

The date and time stamp forthe log report.

mmm means three first lettersof the month, for example,Aug.

<IP address> numeric Variable

The IP address of the unitdevice from which the logoriginated.

<log type> class_security.ver01

Variable

Common name for securitylogs.

ISAKMP_INFO orISAKMP_FAIL

text string Variable

Indicates an information-onlyor a problem-reporting log.

<log message> alphanumericcharacter string

Variable

A description of the conditionsor reasons generating the log.

IPSEC: UNSECURED PKTDISCARDED indicates theGWC received an unsecurepacket from a node but wasexpecting a secured packet asper the policy provisioned inthe GWC.

IPSEC PKT DISCARDED BYPOLICY indicates the GWCreceived an unsecure packetfrom a node and a DISCARDpolicy is provisioned in theGWC for that node.

<status> success or failure Variable

Indicates whether theoperation succeeded or failed.

<MID> MID=MID_Nortel_MGC_autho.<0016 or 0017>

Variable

0016 indicates an INFO log.0017 indicates a FAIL log.






IPSec security logs 111


GWC (GL170) alarms and logs referenceThis section provides a reference for the GWC alarms and logs for theGL170 release.

GWCA207Log report GWCA207 indicates that a test log is generated from pmdebuginterface.

Remedial actionn/a


Log name GWCA207Suppressionsetting

suppression-allowed

Format• STD Autonomous Non-Alarm Event Format:

<OFFICE> <Severity> GWCA207 MMMDD hh:mm:ss <Sequence Number>EVT Log

Location: <IEMS Display Name>;<dn>

Notification Id: <Notification Id>

State: None

Category: other

Cause: nil-probable-cause


Component Id: <ref-entity-type>;<ref-entity-tag>;<ref-subentity-info>

113


Specific Problem: <Specific Problem>

Description: Test log generated from pmdebuginterface;<additional-text>

Reason: <reason>;proposed repair action=Field not used.

GWCA240



suppression-allowed





State: None

Category: other





Description: Security-Authorization Logs;<additional-text>


Active message exampleMTOSSOTT18 GWCA240 AUG23 14:30:57 9858 EVT Log

Location: ott18vse;VSE-OTT18_C20a/SERVICE_Container/SG-gwc0

Notification Id: 345939

114 GWC (GL170) alarms and logs reference


State: None

Category: other


Time: Aug 23 23:30:57 2011

ComponentId: service-group;/=/v=1/sg-name=gwc0;/=/v=1/proxied-su-name=gwc0_SU_1:gwcapp

Specific Problem: GWCA240;Id=2002-0-90194378752-/=/v=1/sg-name=gwc0-/=/v=1/proxied-su-name=gwc0_SU_1:gwcapp-240-0

Description: Security-Authorization Logs;

Reason: class_security.ver01 CMD=connect_w STAT=startSRC=47.133.147.4 CONNECT=telnet_connectMID=MID_Nortel_MGC_auth.0001;proposed repair action=Fieldnot used.

GWCA241



suppression-allowed





State: None

Category: other



GWCA241 115




Description: Security-Authorization Logs;<additional-text>


GWCA300Log report GWCA300 indicates an "Active unit disabled." Unit Out ofService: Service is not available. The alarm severity is Critical.

This log is cleared by log report GWCA399. If required, see "GWCA399"for more information.


This log reports that the unit is not in service (Operational state of"disabled").

- This is not usual nodal status where instance get stuck in invalid state.Activity is lost when oper-disable status. If this alarms persistent, it deemsas software problem.


• Before geting assistance from Genius Platform - AMF as GWC MtceManager, check the mate ( for duplex) and try to bring it into service toshortened the outage

• Recover by lock force - unload - load and unlock in order to bring thisunit as Inactive Inservice Ready. If it does not help at first trial, it againneeds next level support

• There are various reasons to cause Oper Disable : it should detailanalysis where the unit drop the activity and goes to SBSY from Core/EM alarm history data.



suppression-allowed



Attribute ValueSeverity • Cleared

• Critical

Type Quality of Service AlarmStatus set/clearProbablecause


FormatSTD Raise Format:

<OFFICE> <Severity> GWCA300 MMMDD hh:mm:ss <Sequence Number>AON Alarm set



State: Raised


Cause: underlying-resource-unavailable




Description: Active unit disabled;<additional-text>

Reason: <reason>;proposed repair action=<proposed-repair-action>

• STD Clear Format:

<OFFICE> GWCA300 MMMDD hh:mm:ss <Sequence Number> AOFF Alarmclear



State: Cleared

GWCA300 117







Description: Active unit disabled;<additional-text>


Active message exampleMTOSSOTT18 *** GWCA300 AUG21 15:08:54 3820 AON Alarm set



State: Raised



Time: Aug 22 00:08:54 2011



Description: Active unit disabled;

Reason: GWC=GWC-16-UNIT-0;Version=GL160BX;Unit=unit_0;Software=NODEMTC: UnitOut of Service: Unit is system_w disabled; Service is notavailable;proposed repair action=

Clear message exampleMTOSSOTT18 GWCA300 AUG21 15:09:19 3864 AOFF Alarm clear





State: Cleared



Time: Aug 22 00:09:19 2011



Description: Active unit disabled;


GWCA301Log report GWCA301 indicates a "Standby unit disabled." Unit Out ofService: Service is not available. The alarm severity is Minor or Major.




If the Operational state "disabled" and Administrative state is "unlocked",the unit is system busy (SysB) - the alarm is major.

GWCA301 119


If the Operational state "disabled" and Administrative state is "locked", theunit is manually busy (ManB) - the alarm is minor.



• Other state indicators which may indicate problems, such as:






suppression-allowed

Severity • Cleared

• Major

• Minor







State: Raised








Description: Standby unit disabled;<additional-text>






State: Cleared






Description: Standby unit disabled;<additional-text>


Active message exampleMTOSSOTT18 ** GWCA301 AUG23 09:38:22 4146 AON Alarm set



State: Raised

Category: other

GWCA301 121



Time: Aug 23 18:38:22 2011



Description: Standby unit disabled;





State: Cleared



Time: Aug 23 18:38:30 2011



Description: Standby unit disabled;


GWCA302Log report GWCA302 indicates a Major for active unit; Minor for inactiveunit. "Core communication lost." No response received to Core heartbeatmessages.




Remedial actionThe alarm condition associated with this log clears automatically after aCore or network outage clears. Otherwise, verify that the node number andCore Side IP address is correct for the GWC to communicate with theCore.



suppression-allowed


• Major

• Minor


LAN Error

Format• STD Raise Format:




State: Raised


Cause: lan-error




GWCA302 123


Description: Core communication lost;<additional-text>






State: Cleared


Cause: lan-error




Description: Core communication lost;<additional-text>





State: Raised


Cause: lan-error

Time: Aug 21 23:03:13 2011





Description: Core communication lost;

Reason: GWC=GWC-17-UNIT-0;Version=GL160BX;Unit=unit_0;Software=NODEMTC: Noresponse received to Core heartbeat messages.;proposedrepair action=




State: Cleared


Cause: lan-error

Time: Aug 21 23:03:44 2011



Description: Core communication lost;

Reason: GWC=GWC-15-UNIT-0;Version=GL160BX;Unit=unit_0;Software=NODEMTC: Noresponse received to Core heartbeat messages.;proposedrepair action=

GWCA304Log report GWCA304 indicates that communication with a gateway isdown. The alarm severity is Major.

'Gateway' is defined as large gateway or audio gateway (for example,PVG, H.323 gateway with 64 or more endpoints, MG 9000, UAS).


GWCA304 125


Remedial actionThe alarm condition associated with this log can be cleared by restoringcommunication to the managed gateway. Do this by verifying theavailability of the gateway, and comparing the configuration data at theGateway and the CS 2000 GWC Manager (IP address, protocol/version,etc).



suppression-allowed


• Major







State: Raised






Description: Communication with a gateway isdown;<additional-text>








State: Cleared






Description: Communication with a gateway isdown;<additional-text>





State: Raised



Time: Aug 23 22:19:26 2011

ComponentId: service-group;/=/v=1/sg-name=gwc2;OTT18MG3600

GWCA304 127


Specific Problem: GWCA304;Id=2002-0-98784313344-/=/v=1/sg-name=gwc2-OTT18MG3600-4056-42

Description: Communication with a gateway is down;

Reason: GWC=GWC-2-UNIT-1;Version=GL160BX;Unit=unit_1;Software=SSC:OTT18MG3600;proposed repair action=




State: Cleared



Time: Aug 23 22:19:26 2011

ComponentId: service-group;/=/v=1/sg-name=gwc2;OTT18MG3600

Specific Problem: GWCA304;Id=2002-0-98784313344-/=/v=1/sg-name=gwc2-OTT18MG3600-4056-42

Description: Communication with a gateway is down;

Reason: GWC=GWC-2-UNIT-1;Version=GL160BX;Unit=unit_1;Software=SSC:OTT18MG3600;proposed repair action=

GWCA305Log report GWCA305 indicates that a test alarm is generated frompmdebug interface to log in to the notilog table. May be any level.







suppression-allowed


• Indeterminate


Unspecified Reason





State: Raised


Cause: unspecified-reason




Description: Test alarm generated from pmdebuginterface;<additional-text>




GWCA305 129




State: Cleared






Description: Test alarm generated from pmdebuginterface;<additional-text>





State: Raised



Time: Aug 23 05:05:33 2011



Description: Test alarm generated from pmdebug interface;

Reason: GWC=GWC-0-UNIT-0;Version=GL160BX;Unit=unit_0;Software=DEBUG: Alarmstest from debug interface;proposed repair action=






State: Cleared



Time: Aug 23 05:46:59 2011



Description: Test alarm generated from pmdebug interface;

Reason: GWC=GWC-0-UNIT-0;Version=GL160BX;Unit=unit_0;Software=DEBUG: Alarmstest from debug interface;proposed repair action=

GWCA306Log report GWCA306 indicates a DQoS/COPS connection failure. Thealarm severity is major or critical.

When a dynamic quality of service (DQoS) connection is down betweenthe C20 and a CMTS, the C20 will allow new calls hosted by that CMTS toproceed without DQoS. The behavior of the multimedia terminal adapter(MTA) and CMTS determines whether new calls are attempted using best-effort service or whether they are torn down:

• Some MTA vendors allow calls to proceed as data calls (best-effort)and do not send a data-over-cable service interface specification(DOCSIS) authorization block to the CMTS. In this case, the CMTScannot recognize the call as a voice call and so it proceeds withoutmanaged quality of service.

• Other MTA vendors send the DOCSIS authorization block to the CMTSwith no authorization key or gate-id. When this happens, the CMTSdecides whether or not to allow calls to proceed.

GWCA306 131


When the DQoS connection is up, but the C20 does not receive a DQoSgate-id from the CMTS, the C20 will tear down a call.


Remedial actionThe DQoS connection loss alarm is cleared by DCCNXMGR (usingDCALARM) when the connection is reestablished or the connection isdeleted from provisioning.



suppression-allowed


• Critical

• Major







State: Raised


Cause: communication-subsystem-failure






Description: DQoS/COPS connection failure;<additional-text>






State: Cleared






Description: DQoS/COPS connection failure;<additional-text>





State: Raised



Time: Aug 21 23:03:24 2011

GWCA306 133




Description: DQoS/COPS connection failure;

Reason: GWC=GWC-17-UNIT-0;Version=GL160BX;Unit=unit_0;Software=DQOSMTC: DQoSconnection <[email protected]> has failed - attemptingrecovery.;proposed repair action=




State: Cleared



Time: Aug 21 23:03:25 2011



Description: DQoS/COPS connection failure;

Reason: GWC=GWC-17-UNIT-1;Version=GL160BX;Unit=unit_1;Software=DQOSMTC: DQoSconnection <[email protected]> has failed - attemptingrecovery.;proposed repair action=

GWCA307Log report GWCA307 indicates an "Element Manager communicationfailure".

- EM indicates provisioned data mismatched in this unit





Remedial actionThe alarm condition associated with this log can be cleared with a lock/unlock of GWC unit.



suppression-allowed


• Major







State: Raised






GWCA307 135


Description: Element Manager communicationfailure;<additional-text>






State: Cleared








GWCA308Log report GWCA308 indicates a "Flash memory error" but it is a alarmgenerated from pmdebug interface. The alarm severity is Major.







suppression-allowed


• Major

Type Equipment AlarmStatus set/clearProbablecause

Equipment Malfunction





State: Raised

Category: equipment

Cause: equipment-malfunction




Description: Flash memory error;<additional-text>




GWCA308 137




State: Cleared

Category: equipment

Cause: equipment-malfunction






GWCA311Log report GWCA311 indicates a Warning. "Provisioned GWC Profile notyet activated." The GWC Profile loaded into Flash will activate on the nextreload.


Remedial actionThe alarm condition associated with this log can be cleared by reloadingthe GWC.



suppression-allowed


• Warning

Type Quality of Service Alarm



Attribute ValueStatus setProbablecause






State: Raised


Cause: configuration-or-customization-error




Description: Provisioned GWC Profile not yetactivated;<additional-text>


GWCA312Log report GWCA312 indicates a QCA connection failure, either a majoralarm (partial outage) or a critical alarm (total outage).


GWCA312 139


Remedial actionNo reports are lost since they are collected on a backup server.

• Ensure that the QCA contains the correct properties (port, IP address,etc). Check that the QCA is properly provisioned using the CS2MTools.

• Use the ping command to see if you can reach the QCA server. If youcannot reach the server, there may be a problem in the network.

• Verify that there is no memory exhaustion on the QCA server.

• To bring up the links, restart the QCA application on the server.

• Try connecting to a QCA on another CS2M Tools server.



suppression-allowed


• Critical

• Major







State: Raised


Cause: communication-subsystem-failure Time: Mmm DD hh:mm:ssYYYY





Description: QCA connection failure;<additional-text>






State: Cleared


Cause: communication-subsystem-failure Time: Mmm DD hh:mm:ssYYYY



Description: QCA connection failure;<additional-text>


GWCA313Log report GWCA313 indicates that "RMGC is overloaded." Thecorresponding alarm severity is Major.

RMGC stands for Redirecting Media Gateway Controller.

The specific problem is that RMGC cannot process all incoming requests.The probable cause is that the resource at or nearing capacity.

GWCA313 141



Remedial actionThe RMGC is temporarily overloaded. The alarm corresponding to this logwill clear itself once the RMGC is able to process requests again.Gateways keep sending requests until they get a response. So, once theoverload clears, gateways should be able to register without any furtherintervention.

If the alarm corresponding to this log is seen regularly or does not clear,then this is an indication that there is insufficient RMGC processingcapacity in the office. Consider commissioning another RMGC.



suppression-allowed


• Major

Type Processing Error AlarmStatus set/clearProbablecause






State: Raised


Cause: resource-at-or-nearing-capacity






Description: RMGC overloaded;<additional-text>






State: Cleared






Description: RMGC overloaded;<additional-text>


GWCA314Log report GWCA314 indicates a Major alarm (partial outage). TheCentrex IP Client Manager (CICM) location identification reportingapplication fails to establish a TCP/IP connection to the location recipient,or the established connection is broken.


GWCA314 143



• Re-establish the connection to the location recipient.

• Disable the location ID reporting application.

• Lock/Unlock the GWC unit.



suppression-allowed


• Major







State: Raised






Description: Location Id Reporting connectionfailure;<additional-text>








State: Cleared






Description: Location Id Reporting connectionfailure;<additional-text>


GWCA315Log report GWCA322 indicates that USP SS7 paths are not active. Thealarm severity is Major or Critical.

- When no path is up then a critical alarm is raised

- When not all paths are up or either USP lose connection then a majoralarm is raised


GWCA315 145




suppression-allowed


• Critical

• Major


Communication Protocol Error





State: Raised


Cause: communication-protocol-error




Description: External communication Interface;<additional-text>








State: Cleared








Active message exampleMMTOSSOTT18 * GWCA315 AUG22 15:05:01 2300 AON Alarm set



State: Raised

Category: ocommunications


Time: Aug 23 00:05:01 2011



Description: External communication Interface;

GWCA315 147


Reason: GWC=GWC-13-UNIT-1;Version=GL160BX;Unit=unit_1;Software=OM Collection:USP SS7 path not Active;proposed repair action=




State: Cleared



Time: Aug 23 01:05:00 2011




Reason: GWC=GWC-1-UNIT-1;Version=GL160BX;Unit=unit_1;Software=OM Collection:USP SS7 path not Active;proposed repair action=

GWCA317Log report GWCA333 is used to indicate that the Pre Swact audit failureoccurred for two consecutive cycles. An alarm will be raised whenever thePreSwact audit fails for two consecutive cycles due to resource exhaust.The text of the alarm describes which component has led to the failure.Itwill be reflected in the SESM as well as in the GWC with the availablestatus of the GWC in the SESM reflecting 'DEGRADED'. The audit runsperiodically and raises alarm for PSA fail on error conditions. A duplicatealarm for the same reason as that of an existing one will not be raised.













suppression-allowed


• Major


Performance Degraded





State: Raised


GWCA317 149


Cause: performance-degraded




Description: PreSwact Audit failure;<additional-text>






State: Cleared


Cause: problem-degraded






GWCA318Log report GWCA318 indicates that the Gateway Controller (GWC)initiated an autonomous switch of activity (SWACT) in an attempt to restorecommunication with its associated media gateways. The alarm severity iscritical.





Log name GWCA318Severity • Cleared

• Critical





State: Raised






Description: <description>;<additional-text>






GWCA318 151


State: Cleared






Description: <description>;<additional-text>


GWCA319Log report GWCA319 indicates that the Gateway Controller (GWC) lostcommunication with all associated media gateways. The alarm severity iscritical.



The alarm clears when the GWC detects communication with at least oneassociated gateway. It also clears when the GWC automatically ormanually switches activity but it is raised again on the newly active unit ifcommunication is still lost with all associated gateways.



suppression-allowed


• Critical

Type Communications Alarm



Attribute ValueStatus set/clearProbablecause



<OFFICE> <Severity> GWCA319 MMDD hh:mm:ss <Sequence Number>AON Alarm set



State: Raised






Description: GWC communication loss with associated mediagateway(s);<additional-text>






State: Cleared



GWCA319 153





Description: GWC communication loss with associated mediagateway(s);<additional-text>





State: Raised



Time: Aug 21 23:02:49 2011



Description: GWC communication loss with associated mediagateway(s);

Reason: GWC=GWC-17-UNIT-1;Version=GL160BX;Unit=unit_1;Software=SSC: GWC-17-UNIT-1: No communication with associated mediagateway(s);proposed repair action=




State: Cleared





Time: Aug 21 23:03:25 2011



Description: GWC communication loss with associated mediagateway(s);

Reason: GWC=GWC-17-UNIT-1;Version=GL160BX;Unit=unit_1;Software=SSC: GWC-17-UNIT-1: No communication with associated mediagateway(s);proposed repair action=

GWCA322Log report GWCA322 indicates that the simple network managementprotocol (SNMP) message rate exceeded the recommended maximum. Aminor alarm is raised on crossing the Panic Levels and a warning alarm israised on crossing the Warning Levels.

This log is cleared by log report GWCA399. If required, see "GWCA399"


Remedial actionMake sure that the SNMP traffic is reduced.



suppression-allowed


• Minor

• Warning

Type Quality of Service Alarm

GWCA322 155


Attribute ValueStatus set/clearProbablecause

CPU Cycles Limit Exceeded





State: Raised


Cause: cpu-cycles-limit-exceeded




Description: Overloaded subsystem;<additional-text>






State: Cleared


Cause: cpu-cycles-limit-exceeded








GWCA323



suppression-allowed


• Major







State: Raised





GWCA323 157



Description: NGSS Communication Lost;<additional-text>






State: Cleared






Description: NGSS Communication Lost;<additional-text>





State: Raised



Time: Aug 22 10:14:19 2011





Description: NGSS Communication Lost;

Reason: GWC=GWC-8-UNIT-1;Version=GL160BX;Unit=unit_1;Software=NGSS: NGSSCommunication Lost;proposed repair action=




State: Cleared



Time: Aug 22 10:15:24 2011



Description: NGSS Communication Lost;

Reason: GWC=GWC-8-UNIT-1;Version=GL160BX;Unit=unit_1;Software=NGSS: NGSSCommunication Lost;proposed repair action=

GWCA324Log report GWCA324 indicates that uptime alarms have been raised onthe GWCs.


GWCA324 159




suppression-allowed


• Major

• Minor


Software Error





State: Raised


Cause: software-error




Description: Automated maintenance action is scheduled forthis unit;<additional-text>








State: Cleared


Cause: software-error




Description: Automated maintenance action is scheduled forthis unit;<additional-text>


GWCA325Log report GWCA325 indicates that "Inactive unit refresh is in progress".An alarm will be raised after Routine Data Refresh Operation request ishandled at the inactive unit of the GWC and inactive unit refresh is startedsuccessfully. It will be cleared after inactive unit refresh is completed oraborted.


Remedial actionn/a



suppression-allowed

GWCA325 161


Attribute ValueSeverity • Cleared

• Minor


Unspecified Reason





State: Raised






Description: Inactive unit refresh is inprogress;<additional-text>








State: Cleared






Description: Inactive unit refresh is inprogress;<additional-text>


Active message exampleMTOSSOTT18 * GWCA325 AUG28 09:30:20 8439 AON Alarm set



State: Raised



Time: Aug 28 18:30:20 2011



Description: Inactive unit refresh is in progress;

Reason: GWC=GWC-0-UNIT-0;Version=GL160BX;Unit=unit_0;Software=NODEMTC: Alarmwill be cleared when mtc is over.;proposed repair action=

Clear message exampleMTOSSOTT18 * GWCA325 AUG28 09:30:30 8444 AON Alarm set

GWCA325 163




State: Raised



Time: Aug 28 18:30:30 2011



Description: Inactive unit refresh is in progress;

Reason: GWC=GWC-1-UNIT-1;Version=GL160BX;Unit=unit_1;Software=NODEMTC: Alarmwill be cleared when mtc is over.;proposed repair action=

GWCA326Log report GWCA326 indicates that there is a "ITA Resource capacityproblem". The alarm severity is Major or Critical.




suppression-allowed


• Critical

• Major









State: Raised






Description: ITA Resource capacity problem;<additional-text>






State: Cleared






GWCA326 165


Description: ITA Resource capacity problem;<additional-text>


GWCA327Log report GWCA327 indicates that there is a "H323 Object nearingcapacity". The alarm severity is Major or Critical.




suppression-allowed


• Critical

• Major







State: Raised








Description: H323 Object nearing capacity;<additional-text>






State: Cleared






Description: H323 Object nearing capacity;<additional-text>


GWCA328Log report GWCA328 is used to indicate that terminating call attempts arereached to overload levels.

When a burst of very high traffic is routed to a particular terminating GWC,the GWC internal resources (e.g. CPU, buffers, etc.) may exhaust andcause the GWC to enter an overload state.

The new emergency overload message is used to indicate the immediateoverload levels

GWCA328 167


of MAJOR, CRITICAL or NONE from the GWC to the Core. GWC alsoraises alarms for Major and Critical levels. A Major alarm is raised oncrossing the Warning Levels and critical alarm is raised on crossing thePanic Levels.

A duplicate alarm for the same reason as that of an existing one will not beraised.


Remedial actionMake sure that the terminating GWC traffic is reduced.


Log name GWCA328Severity • Cleared

• Critical

• Major

Type Communications AlarmProbablecause






State: Raised








Description: GWC overloaded;<additional-text>






State: Cleared






Description: GWC overloaded;<additional-text>



- Provisioned data updated in Flash, but not yet in use



GWCA330 169


Remedial actionThe alarm condition associated with this log can be cleared with a lock/unlock of GWC unit.



suppression-allowed


• Major


Version Mismatch





State: Raised


Cause: version-mismatch












State: Cleared


Cause: version-mismatch






GWCA331Log report GWCA331 indicates that there is a DNS lookup failure. Thealarm severity is Minor, Major, or Critical.




suppression-allowed


• Critical

• Major

• Minor

GWCA331 171


Attribute ValueType Quality of Service AlarmStatus set/clearProbablecause






State: Raised












State: Cleared













State: Raised



Time: Aug 19 22:30:00 2011




Reason: GWC=GWC-4-UNIT-1;Version=GL000AA;Unit=unit_1;Software=OM Collection:DNS failed GW discovery;proposed repair action=




GWCA331 173


State: Cleared

Category: other


Time: Aug 19 22:30:00 2011




Reason: GWC=GWC-4-UNIT-0;Version=GL160BX;Unit=unit_0;Software=OM Collection:DNS failed GW discovery;proposed repair action=

GWCA332Log report GWCA332 indicates that there are:

- Small GWs in disabled state, or

- Media Proxies in disabled state, or

- connection failures of peers

The alarm severity is Minor, Major, or Critical.




suppression-allowed


• Critical

• Major

• Minor



Attribute ValueType Communications AlarmStatus set/clearProbablecause

Loss of Signal





State: Raised


Cause: loss-of-signal










State: Cleared


GWCA332 175








Active message exampleMTOSSOTT18 * GWCA332 AUG23 02:50:00 1548 AON Alarm set



State: Raised



Time: Aug 23 11:50:00 2011




Reason: GWC=GWC-13-UNIT-1;Version=GL160BX;Unit=unit_1;Software=OM Collection:USP SS7 paths disabled;proposed repair action=






State: Cleared



Time: Aug 23 12:00:00 2011




Reason: GWC=GWC-13-UNIT-1;Version=GL160BX;Unit=unit_1;Software=OM Collection:USP SS7 paths disabled;proposed repair action=

GWCA333Log report GWCA333 is used to indicate that the Pre Swact audit failureoccurred for two consecutive cycles. An alarm will be raised whenever thePreSwact audit fails for two consecutive cycles due to resource exhaust.The text of the alarm describes which component has led to the failure.Itwill be reflected in the SESM as well as in the GWC with the availablestatus of the GWC in the SESM reflecting 'DEGRADED'. The audit runsperiodically and raises alarm for PSA fail on error conditions. A duplicatealarm for the same reason as that of an existing one will not be raised.





GWCA333 177








suppression-allowed


• Major







State: Raised














State: Cleared








GWCA334Log report GWCA334 indicates that the CPU usage has crossed thethreshold. A major alarm is raised on crossing the Panic Levels.



GWCA334 179




suppression-allowed


• Major


Threshold Crossed





State: Raised


Cause: threshold-crossed












State: Cleared


Cause: threshold-crossed






GWCA335Log report GWCA308 indicates a "Flash memory error." Erase of Flashsector failed. The alarm severity is Minor


Remedial actionThe alarm condition associated with this log can be cleared by reloadingthe GWC unit.



suppression-allowed


• Minor

Type Equipment AlarmStatus setProbablecause

Input/Output Device Error

GWCA335 181






State: Raised

Category: equipment

Cause: io-device-error










State: Cleared

Category: equipment

Cause: io-device-error









- EM is not responding, provisioned data loaded from local Flash



Remedial actionThe alarm condition associated with this log can be cleared with a lock/unlock of GWC unit. In addition to this, if the CS2M responds to indicate amismatch, this alarm is cleared and GWCA330 is set to indicate themismatch of the provisioned data in this GWC unit.

Restore communication with the CS2M. Determine if the CS2M is downand or disconnected. Determine if the GWC has been setup to use thewrong IP address for the CS2M.



suppression-allowed


• Major


Application Subsystem Failure


GWCA336 183





State: Raised


Cause: application-subsystem-failure










State: Cleared











Location: ott18vse;VSE-OTT18_C20a/C20_Container/GWC_Container/SG-gwc20


State: Raised



Time: Aug 22 12:29:26 2011

ComponentId: gwc-sg-config;/=/v=1/sg-name=gwc20;/=/v=1/proxied-su-name=gwc20_SU_1:gwcapp


Description: Element Manager communication failure;

Reason: GWC=GWC-20-UNIT-1;Version=GL160BX;Unit=unit_1;Software=NODEMTC: EM notresponding, provisioned data loaded from localFlash;proposed repair action=


Location: ott18vse;VSE-OTT18_C20a/C20_Container/GWC_Container/SG-gwc20


State: Cleared



Time: Aug 22 12:30:24 2011

GWCA336 185


ComponentId: gwc-sg-config;/=/v=1/sg-name=gwc20;/=/v=1/proxied-su-name=gwc20_SU_1:gwcapp


Description: Element Manager communication failure;

Reason: GWC=GWC-20-UNIT-1;Version=GL160BX;Unit=unit_1;Software=NODEMTC: EM notresponding, provisioned data loaded from localFlash;proposed repair action=

GWCA337Log report GWCA337 indicates that the Gateway Protocol message rate isexceeding the recommended maximum. A major alarm is raised.





suppression-allowed


• Major







State: Raised














State: Cleared








GWCA399Log report GWCA399 clears all other GWC logs.

GWCA399 187


In the case of H.323 GWCs, this log report is generated only for H.323gateways that contain 64 endpoints or greater.

Remedial actionn/a


Log name GWCA399

GWCA500Log report GWCA500 indicates that there is an "Unknown reason". To seethe specific area where the unknown reason is seen, please refer to thereason text.

Remedial actionn/a



suppression-allowed





State: None

Category: other







Description: Unknown reason;<additional-text>


GWCA501Log report GWCA501 indicates a connection fault between the GatewayController (GWC) and a gateway configured with NCS or MGCP signalingprotocol. The fault requires investigation.

Remedial actionVerify the availability of the gateway and compare the configuration data atthe gateway and CS2M (IP address, protocol, protocol version, and so on).



suppression-allowed





State: None

Category: other





Description: Unknown reason;<additional-text>


GWCA501 189


GWCA502Log report GWCA502 indicates that service is restored to the referencedgateway.

This log report refers only to gateways configured with NCS or MGCPsignaling protocol.

Remedial actionn/a



suppression-allowed





State: None

Category: other





Description: MG is in service;<additional-text>







State: None

Category: other


Time: Aug 22 22:00:10 2011



Description: MG is in service;

Reason: _V2_~I=GWC12~H=GWC-12-UNIT-1~A=GWC~S=0014~~ GWC502NONE RTS SSC LOG MESSAGE Location: GWC-12-UNIT-1 ComponentId: GATEWAY=tma-hk-1y.tma.asiapac.nortel.com GW IP:137.116.148.97 Reason: Connection to remote gatewayrestored: tma-hk-1y.tma.asiapac.nortel.com;proposed repairaction=Field not used.

GWCA503Log report GWCA503 indicates one of the following:




Remedial actionn/a



suppression-allowed

GWCA503 191






State: None

Category: other





Description: MG is out of service;<additional-text>





State: None

Category: other


Time: Aug 18 12:54:01 2011



Description: MG is out of service;



Reason: _V2_~I=GWC5~H=GWC-5-UNIT-0~A=GWC~S=0003~~ GWC503NONE OFFL SSC LOG MESSAGE Location: GWC-5-UNIT-0 ComponentId: GATEWAY=ttm315.ottawalaboperations.car3c.ott GW IP:10.0.107.73 Reason: Connection drop initiated by remotegateway: ttm315.ottawalaboperations.car3c.ott;proposedrepair action=Field not used.

GWCA506Log report GWCA506 indicates that an H.323 GWC unit has lost theconnection to an H.323 gateway. The log entry identifies the specificproblem and describes the reason for the failure.



Remedial actionThe following describes the actions the user may take when a GWCexperiences a loss of connection to an H.323 gateway.

Gateway Unregistration by C20 Successful

• No action required.

• The craftsperson has busied the D-channel for the H.323 gateway, orthe C20 has busied the D-channel for H.323 gateway due amaintenance action such as GWC cold SWACT, C20 restart reload,etc.

Time to Live Expired

• The H.323 gateway failed to refresh the 30 second keepalive timer inthe C20 GWC.

• Verify communication between the gateway and the GWC. Ifnecessary, check the H.323 gateway itself since the C20 GWCunregistered the H.323 gateway because the Time To Live value hasexpired.

GWCA506 193


Gateway Initiated Unregistration Successful

• The H.323 gateway initiated the unregistration from the C20 for somereason.

• Action on the H.323 gateway side may be warranted if theUnregistration was unplanned.



suppression-allowed





State: None

Category: other





Description: Connection lost to H323 gateway;<additional-text>


GWCA507Log report GWCA507 indicates that the connection between a GWC andan H.323 gateway has been restored.




Remedial actionNo action is required.

You may verify that the D-channel has gone in service (INSV) at theMAPCI;MTC:TRKS; TTP; PRADCH; POST GD<trkname>. If any trunkmembers are provisioned and you wish to be able to make calls, thencheck the trunk members to see that they are also idle (IDL).



suppression-allowed





State: None

Category: other





Description: Connection restored to H323gateway;<additional-text>


GWCA507 195


GWCA508Log report GWCA508 indicates that a GWC unit has lost the connection toa VOIP VPN virtual media gateway (vmg) . The log entry identifies thespecific problem and describes the reason for the failure.


This log report is generated only for vmgs that contain less than 64endpoints configured in the associated trunk group in the C20. Otherwiseexisting gw communication lost alarms are used.

System impactNo VOIP VPN calls can be made using the trunks associated with theaffected vmg.

Remedial actionBsy then rts the associated D-chnl for the vmg.

Verify the provisioning in the MCP System Manager for the vmg to ensurethat it is hosted by the correct GWC in regards to ip addresses.



suppression-allowed





State: None

Category: other







Description: VMG is out of service;<additional-text>


GWCA509Log report GWCA509 indicates that a GWC unit has restored connectionto a VOIP VPN virtual media gateway (vmg) .

This log report is generated only for vmgs that contain less than 64endpoints configured in the associated trunk group in the C20. Otherwiseexisting gw communication lost alarms are cleared.

System impactVOIP VPN calls may be possible using the trunks associated with thespecified vmg.

Remedial actionn/a



suppression-allowed





State: None

Category: other

GWCA509 197






Description: VMG is in service;<additional-text>


GWCA600Log report GWCA600 is an information log for an H.323 failure. The logentry identifies the specific problem and describes the reason for thefailure.


This section provides examples of Core logs relevant to

• Specific problem: H323 RRQ rejected

• Description: D-Channel Out Of Service.

Examples of Core logs when the D-channel is manually busied (BSY):

RTPG * ISDN105 JUN16 21:45:44 2311 FLT PRA Sync Loss

ISP = 0 GWC 11 PORT 0 CHNL 0

RTPG *** ISDN112 JUN16 21:45:44 2412 INFO PRA D-CHANNEL

CRITICAL ALARM RTPG_BCM_LOCAL DCH=GWC 11 120 1 : OOS

RTPG *** TRK103 JUN16 21:45:49 2917 FLT GROUP_ALARM

RTPG_BCM_LOCAL 100% BUSY



Examples of Core logs when the D-channel is returned to service (RTS)and the gateway registers with GWC:

RTPG ISDN118 JUN16 21:46:52 6654 INFO PRA Sync Established

ISP = 0 GWC 11 Port 0 Chnl 0

RTPG TRK104 JUN16 21:46:56 7462 INFO GROUP OK

RTPG_BCM_LOCAL

Remedial actionThe following describes the actions the user takes when an H.323 failurecondition occurs.

GRQ = Gatekeeper request

RRQ = Registration request

ARQ = Admission request

URQ = Unregistration request

DRQ = Disengage request

RAS = Registration, admission and status

H323 GRQ rejected - Gateway Name Not Provisioned

Ensure that the H.323 gateway name provisioned on the CS 2000 GWCManager matches exactly with the gateway name provisioned using theH323 GW provisioning tool.

A log with same description is generated for RRQ received with invalid GWname.

H323 GRQ rejected - Gateway IP Address Invalid

GWCA600 199


A log with same description is generated for RRQ received with an invalidsource gateway IP address. In this case, the source IP address is the IPaddress in the ethernet frame. So, for gateways behind the NAT, thesource IP address will be the NAT IP address.

The RAS IP address is not part of the H.323 payload. If the H.323 gatewayis not behind a NAT, the source IP will be the IP address of the H.323gateway.

If the H.323 gateway is behind the NAT, ensure that the H.323 gateway IPaddress provisioned on the CS2M matches exactly the IP address of theNAT box.

If the H.323 Gateway is not behind a NAT box, ensure that the H.323gateway IP address provisioned on the CS2M matches exactly the IPaddress of the H323 gateway.

H323 GRQ rejected - Gateway Port Invalid

A log with same description is generated for an RRQ received with aninvalid source gateway port. In this case, the source port is the source portaddress in the ethernet frame. So, for gateways behind a NAT, the sourceport is the port entry of the static bind at the enterprise NAT for the H323gateway. It is not the RAS port which is part of the H323 payload.

If the H323 Gateway is not behind a NAT, the source port will be the RASport of the H323 gateway.

If the H.323 gateway is behind the NAT, ensure that the H.323 gatewayport provisioned on the CS2M matches exactly the port entry of the staticbind at the enterprise NAT for the H323 gateway.

If the H.323 Gateway is not behind a NAT box, ensure that the H.323gateway IP address provisioned on the CS2M matches exactly the IPaddress of the H323 gateway.

H323 GRQ rejected - Missing Mandatory RAS Address




H323 RRQ rejected - Incorrect Endpoint Identifier Syntax


H323 keepAlive RRQ rejected - Incorrect Endpoint Identifier Syntax


H323 RRQ rejected - Invalid Endpoint Identifier


H323 ARQ rejected - Invalid Endpoint Identifier


H323 RRQ rejected - D-Channel Not Provisioned

Ensure that the trunk datafill is provisioned correctly on the C20 Core andCS2M.

H323 RRQ rejected - D-Channel Out Of Service

Ensure that the D-channel associated with the H.323 gateway is in LOstate at mapci, mtc, ttp, trks, pradch level on the C20 Core before the H.323 gateway registers.

This log can be cleared with a BSY/RTS of the D-channel associated withthe H.323 gateway on the C20 Core.

Trunk logs are also generated which are similar to PRI trunk logs.

GWCA600 201


For example, H.323 gateway "BCM_RTPG" appears on the Core as trunkname "RTPG_BCM_LOCAL"

Refer to section "Additional information"

for examples of Core logs.

H323 RRQ rejected - Table LTDATA Needs H323 Option

Check the datafill in Table LTDATA on the C20 Core. The optionPRI_IP_PROT H323 should be present for the D-channel associated withthe H.323 gateway.

H323 RRQ rejected - Max Gateways Registered


The C20 GWC has reached the maximum limit for the number of H.323gateways it can have registered simultaneously.

H323 ARQ rejected - B-Channel Resource Unavailable

Ensure that B-channels associated with the gateway are idle (IDL) atmapci, mtc, ttp, trks level on the C20 Core. This log can be cleared with aBSY/RTS of the B-channels associated with the H.323 gateway on the C20Core.

If all the B-channels associated with the H.323 gateway are call processingbusy (CPB) at mapci, mtc, ttp, trks level on the C20 Core, then no action isneeded. There is no B-channel available for the call. This log report is forinformation.

H323 RRQ rejected - No GWC Unit Active Running

A log with the same description will be generated if any RAS message(GRQ, RRQ, ARQ, URQ, DRQ) is received when the GWC unit is notactive running. This log can be cleared with a lock/unlock of GWC unit.



Ensure that the C20 GWC is in active running state.

This log can be cleared with a lock/unlock of GWC unit.

H323 DRQ rejected - Request to Drop Non Existent Call


This reports a disengage request for a call which is not active or non-existent.

H323 URQ rejected - Endpoint Not Registered

A RAS request is received from a H.323 gateway which is not registeredon the C20 GWC.

Verify that the H.323 gateway is provisioned on the C20 GWC.

H323 Call rejected - Codec Mismatch With C20

Ensure that at least one of the codecs provisioned on the H323 gatewaymatches the codec for the C20 provisioned at the CS2M.

H323 Call rejected - Codec / Payload Mismatch With C20

Ensure that at least one of the codecs provisioned on the H323 gatewaymatches the codec for the C20 provisioned at the CS2M.

Ensure that the payload (packetization) time on the H323 gatewaymatches the payload (packetization) for the C20 provisioned at the CS2M.

H323 Call rejected - H245 Tunneling Not Enabled On Gateway

GWCA600 203


Ensure that H.245 tunneling is enabled on the H.323 gateway.



suppression-allowed





State: None

Category: other





Description: H323 failure;<additional-text>


GWCA605Log report GWCA605 indicates that the M3UA Application Server Process(ASP) path audit has detected all the ASP paths in the down state for tenminutes. When this happens, the system initiates an autonomous SWACTrequest.

Remedial actionGWCA605 log reports that a warm SWACT request is initiated if the M3UAASP paths are down for ten minutes. The warm SWACT attempts torecover the M3UA links and bring back the trunks into service. No specificaction is required, as the event takes place automatically.





suppression-allowed

Active message example• STD Autonomous Non-Alarm Event Format:




State: None

Category: other





Description: M3UA ASP paths down;<additional-text>


GWCA606Log report GWCA606 is an information log for a Media Proxy (MP) idle orlong call detection event. Idle and long call durations are measured interms of audit periods, which the user can define in the Media Proxyelement manager.

The log contains a correlation ID passed down from the Core. Thiscorrelation ID is used for correlation with an associated billing record forthat call. In (I)SN09FF this is the only mechanism available to linkgenerated logs with particular billing records.

GWCA606 205


Remedial actionThe user should review the contents of the log report and take action asshown in the following .

Long Call Detected - Call longer than long call duration defined in MediaProxy element manager.


Idle Call Detected - Call longer than idle call duration defined in MediaProxy element manager.


In order to associate the correlation ID with a particular billing record, theQuality of Service feature must be configured and activated.



suppression-allowed





State: None

Category: other







Description: Media Proxy (MP) Idle/Long calldetected;<additional-text>


GWCA607Log report GWCA607 is an informational log generated by the GWC toidentify lines where IP Call Recording is requested but could not beperformed (because the Border Control Point 7200 (BCP 7200) isunavailable or is not provisioned, or because the BCP 7200 has insufficientresources). The GWCA607 log report is generated for the followingprotocols:

• Nortel Standard (NTSTD)

• Switching Control Center 2 (SCC2)

• Syslog

• Simple Network Management Protocol (SNMP)

Remedial actionLog report GWCA607 is an informational GWC log used to correlateinformation provided by the BCP 7200 and the IP Call Recording device.



suppression-allowed





State: None

Category: other

GWCA607 207






Description: BCP unavailable or not provisioned;<additional-text>


GWCA608Log report GWCA608 is a Syslog that is generated when a call signalingfailure occurs. Log report GWCA608 can be correlated to the XPKT300 logusing the Correlation ID field, and provides additional troubleshootinginformation to the XPKT300 log.

The GWCA608 log report is generated for faults that previously generateda GWCA603 or a GWCA604 log. The GWCA603 and GWCA604 logs areno longer generated.

Remedial actionThe failure should be investigated to determine any necessary actions.



suppression-allowed





State: None

Category: other







Description: GWC signaling failure;<additional-text>


GWCA609Log report GWC609 is an information log that is generated when theGateway Controller (GWC) detects communication issues with an in-service trunk or large capacity line gateway. This occurs for the first missedheartbeat reply and when communication lost is declared for a gateway. Inthe later case, an accompanying GWC304 trouble log is also generated.

The GWCA609 log contains the output of a traceroute commandperformed from the GWC to the IP address of the gateway. For tracerouteto function end-to-end, ICMP protocol must be allowed to pass through allrouters and firewalls between the GWC and the gateway.

The personnel that support the network path between the GWC andgateway may use this log to determine if action is required to restore ormaintain communication from the GWC to gateway.

Remedial actionNo action is required. The traceroute hop data can be used to help identifynetwork issues that may be causing communication problems between theGWC and gateway.



suppression-allowed



GWCA609 209




State: None

Category: other





Description: Communication issues with an INSV trunk orlarge capacity line gateway;<additional-text>



Location: VSE-OTT18_C20a;VSE-OTT18_C20a/SERVICE_Container/SG-gwc21


State: None

Category: other


Time: Aug 23 23:49:32 2011



Description: Communication issues with an INSV trunk orlarge capacity line gateway;

Reason: _V2_~I=GWC21~H=GWC-21-UNIT-0~A=GWC~S=0005~~ GWC609NONE INFO Traceroute Location: GWC-21-UNIT-0 Component Id:GWC Card=GWC-21-UNIT-0;GATEWAY=vmg01gwc21 Description:



Traceroute to 47.133.146.70 executed. Destination reached.Last GW signaling msg received 11 secs ago. Hop data (rtt inms): 1 84.240.52.10 0;proposed repair action=Field not used.

GWCA610Log report GWCA610 is an informational log that is generated when a NilCodec condition is detected (that is, when a codec profile table on theGWC is corrupted or is not provisioned, and as such the GWC cannotactively participate in any call).




suppression-allowed





State: None

Category: other





Description: Empty codec profile table;<additional-text>


GWCA610 211


GWCA611Log report GWCA611 is an informational log that is generated when amismatch occurs between RAM and Flash on a Gateway Controller(GWC), and an Autonomous SWACT Request is triggered.

Remedial actionNo immediate action is required. This log is informational and is intendedto inform customers that an Autonomous SWACT was requested due to adata mismatch in the GWC.



suppression-allowed





State: None

Category: other





Description: Data mismatch between RAM andFlash;<additional-text>




GWCA613



suppression-allowed





State: None

Category: other





Description: Codec Mismatches or faults;<additional-text>


GWCA614



suppression-allowed


GWCA614 213





State: None

Category: other





Description: MS2030 Overload Control / MS state ischanged;<additional-text>


GWCA615



suppression-allowed





State: None

Category: other







Description: MS2030 Overload Control / GWC state ischanged;<additional-text>


GWCA615 215


C20 Converged Softswitch

Logs and Alarms Reference, Volume 2Release: CVM17Publication: NN10275-909v2Document Revision: 13.01Document release date: 23 October 2012

Copyright © 2010-2012 GENBAND. All rights reserved. Use of this documentation and its contents is subject to the terms andconditions of the applicable end user or software license agreement, right to use notice, and all relevant copyright protections.

GENBAND, the GENBAND corporate logo and tagline, and certain of GENBAND's product and solution names are registeredtrademarks of GENBAND and its affiliates.

While the information in this document is believed to be accurate and reliable, except as otherwise expressly agreed to in writing,GENBAND AND/OR ITS LICENSORS PROVIDES THIS DOCUMENT "AS IS" WITHOUT WARRANTY OR CONDITION OF ANYKIND, EITHER EXPRESS OR IMPLIED. The information and/or products described in this document are subject to changewithout notice.

THE INFORMATION CONTAINED HEREIN IS THE PROPERTY OF GENBAND OR ITS LICENSORS AND MUST NOT BEDISCLOSED, OTHER THAN TO EMPLOYEES OF GENBAND OR CUSTOMERS WITH NEED-TO-KNOW, WITHOUT THEPRIOR WRITTEN CONSENT OF GENBAND OR ITS LICENSORS. THE INFORMATION MUST NOT BE DISCLOSED TOSUBCONTRACTORS OR REGULATORY AUTHORITIES. GENBAND MUST BE NOTIFIED OF ANY REQUEST OR ORDERFOR DISCLOSURE PRIOR TO SUCH DISCLOSURE.

www.genband.com

nn10275-909v2_13.01_cvm17_c20_fault-management

Documents