nn10275-909v17_12.03_cvm16_c20_logs-alarms

C20 Converged Softswitch

Logs and Alarms Reference,Volume 17Release: CVM16Document Revision: 12.03

www.genband.com

NN10275-909v17

C20 Converged SoftswitchRelease: CVM16Publication: NN10275-909v17Document status: StandardDocument release date: 13 May 2013

Copyright © 2010-2013 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 anydocument provided with this Release is Copyright © 2010 Nortel Networks or its licensors. All rights reserved. Useof this software and/or documentation and its contents is subject to the terms and conditions of the applicable enduser or software license agreement, right to use notice, and all relevant copyright protections.

ContentsNew in this release 9DMS_SALNtoToME 9 Logs and alarms fundamentals 11 DMS_SALNtoToME alarms and logs reference 13SALN100 13SALN101 14SCAI100 15SCAI101 17SCAI102 Format 1 18SCAI103 21SCAI200 23SCAI300 24SCAI301 26SCAI302 27SCAI303 29SCAI311 30SCAI400 32SCAI500 34SCAI501 35SCAI502 36SCR100 38SDM307 Format 1 39SDM307 Format 2 40SDS600 42SDS601 44SECU101 45SECU102 46SECU103 47SECU104 49SECU105 53SECU106 54SECU107 55SECU108 57SECU109 58SECU110 59SECU111 60SECU112 62SECU113 64

3

13 May 2013 Logs and Alarms Reference, Volume 17 NN10275-909v17 12.03Copyright © 2010-2013 GENBAND. All Rights Reserved.

SECU114 65SECU115 66SECU116 67SECU117 68SECU118 69SECU119 71SECU120 72SECU121 73SECU122 74SECU123 76SECU124 77SECU125 78SECU126 79SIM600 80SLE101 82SLE102 83SLE103 84SLE104 86SLE105 88SLE106 89SLE107 91SLE108 92SLM200 93SLM208 98SLM400 98SLM401 100SLM402 101SLM403 102SLM404 103SLM405 104SLM406 105SLM407 106SLM408 108SLM409 109SLM410 110SLNK100 112SLNK101 112SLNK102 113SLNK103 114SLNK104 116SLNK105 116SLNK106 117SLNK107 119SLNK108 120SMDI100 125SMDI101 126SMDI102 127SMDI103 128SMDI104 129SMDI105 131SMDI106 132SMDI107 133

4

13 May 2013 C20 Converged Softswitch NN10275-909v17 12.03Copyright © 2010-2013 GENBAND. All Rights Reserved.

SMDI108 134SME100 135SME101 136SME102 137SME103 138SME104 139SME105 140SME106 141SME107 142SME108 143SME109 144SME110 146SME111 147SNAC100 Format 1 148SNAC100 Format 3 151SNAC101 154SNAC102 157SNAC103 161SNAC104 164SNAC105 166SOC300 167SOC301 168SOC302 170SOC303 171SOC304 172SOC305 174SOC306 177SOC307 178SOC308 179SOC310 181SOC311 182SOC312 184SOC313 186SOC314 187SOC315 188SOC316 190SOC317 191SOC318 192SOC319 194SOC320 195SOC321 196SOC322 197SOC323 198SOC324 199SOC325 200SOC326 201SOC400 202SOC402 204SOC403 205SOC404 206SOC500 207SOC501 209

5


SOC502 210SOC503 213SOC504 217SOC505 220SOC506 223SOC507 225SOC508 226SOC509 228SOC510 229SOC511 232SOC600 233SOC601 234SOC604 236SOC605 237SOC606 238SOC607 240SOC800 241SOC801 242SOC802 243SOC803 244SOS100 246SOS101 247SOS102 248SOS103 249SOS104 250SOS105 251SOS106 252SOS107 252SOS109 254SOS110 255SOS111 256SOS120 258SOS130 259SOS132 259SOS400 260SOS410 262SOS411 263SOS412 265SOS602 266SOS603 267SOS604 268SOS605 270SOS910 271SOS911 272SOS912 274SOS913 275SPC100 277SPC101 278SPC102 280SPM633 282SPM690 283SPRF670 284

6


SPRF671 287SRC400 289SRC500 291SRC510 292SRC520 294SRC620 295SRC640 296SRC660 298SRC661 299SSR600 300STOR101 306STOR102 307STOR103 308STOR104 309STOR105 311STOR106 313STOR107 314STOR108 318SWCT102 320SWCT103 322SWCT104 325SWCT105 326SWCT106 329SWCT112 332SWCT114 333SWCT115 334SWCT116 335SWCT117 337SWER 338SWNR100 339SWNR101 341SWNR102 342SYNC101 343SYNC102 346SYNC104 352SYNC201 354SYNC203 357SYNC204 361SYNC205 364SYNC206 370SYNC208 374SYNC209 375TCAP100 378TCAP101 388TCAP102 394TCAP199 Format 1 395TCAP199 Format 2 398TCAP200 402TCCI100 404TCCI101 407TCCI102 409TCW600 411

7


TCW601 414TDR101 416TDR102 418TDR200 419TELN100 422TELN110 423TEOL100 424TIBM100 426TKCV100 430TME102 431ToME301 434ToME601 436ToME602 437

8


New in this releaseThe following sections detail what's new in the following network elementsand applications for the CORE13 release.

DMS_SALNtoToMESSR600 has two additional fields: CALL_CAP and XACORE_CPC.

9


10 New in this release


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 This document uses multiple volumes to describe logs that the C20 networkcomponents 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.

11


12 Logs and alarms fundamentals


DMS_SALNtoToME alarms and logsreference

This section provides a reference for the DMS_SALNtoToME alarms andlogs for the CORE13 release.

SALN100The Station Administration Line (SALN) subsystem generates log reportSALN100. The subsystem generates this report when a line equipmentnumber (LEN) that a business network management (BNM) customerowns changes on the DMS database. The user does not save the LEN toupload to the BNM database on the digital network controller (DNC). Theuser cannot save the LEN if the DMS internal LEN list is full.

Remedial actionSchedule a database synchronization immediately to free some space inthe internal list of the changed LEN. Do not perform data changes to BNMLEN from the DMS until some space is available in the LEN list.

AttributesAttribute ValueSeverity Warning

FormatSALN100 mmdd hh:mm:ss ssdd INFO CHANGED LEN LOST.

LEN: len

13


Selected field descriptionsField Value Fixed or

VariableDescription

INFO CHANGEDLEN LOST

Constant Variable Indicates a changed LEN on theDMS database that the user does notsave to upload to the BNM database.The DMS internal list of LEN is full

LEN Integers Variable Identifies the lost LEN. Refer to TableI

Active message exampleSALN100 JUN 12 11:12:01 3643 INFO CHANGED LEN LOST.

LEN: HOST 01 1 01 01

Clear message examplen/a

Associated OM registers

SALN101The Station Administration Line (SALN) subsystem generates log reportSALN101. The subsystem generates this report when the swap internaltable of size 1k is full. To make sure the swap table does not fill up,perform incremental uploads more often.

Remedial actionPerform incremental upload from the DMS to upload the swap informationfrom the internal swap table. The system deletes the data that you upload.The system deletes the data from the internal table after an incrementalupload to make space free.


FormatSALN101 mmdd hh:mm:ss nnnn INFO SWAP INFORMATION LOST.

len AND len

14 DMS_SALNtoToME alarms and logs reference



VariableDescription

INFO SWAPINFORMATIONLOST

Constant Variable Indicates the swap internal table isfull and information is lost.

LEN Integers Variable Identifies the line equipment number(LEN). Refer to Table I.

Active message exampleSALNl101 JAN03 08:00:11 4900 INFO SWAP INFORMATION LOST.

HOST 00 0 03 31 AND HOST 00 0 04 06



SCAI100The system produces log report SCAI100 when an attempt to associatewith a wrong parameter occurs.

Remedial actionVerify customer entries. The SCAI group can be entered with invalidparameters entries or the host user can have invalid information forsession establishment.

AttributesAttribute ValueSeverity Indeterminate

FormatSCAI100 mmdd hh:mm:ss ssdd

FAIL_SESSION_ASSOCIATION_FAILED

LINK ID: len or dna PROTOCOL: protocol_number

DEVICE: device_number LINK: link_number

REASON : error_reason VALUE: parameter_value

SCAI100 15


Selected field descriptionsField Value Fixed

orVariable

Description

FAIL_SESSION_ASSOCIATION_FAILED

Constant Variable

Indicates an attempt toassociate with a wrongparameter

LINK ID DNA Variable

The data network address(DNA) identifies the link onwhich the session associationfails. The DNA is output whenthe switch-computer-application interface (SCAI),link uses X.25 transport.

PROTOCOL digits Variable

In x.25 terminology thisinformation is called userdata. User data is protocol-specific data that thecomputer uses to receive andsend information to and fromthe switch.

DEVICE MPC number Variable

The MPC supports thecontroller. The MPC indicatesthe MPC number. The linkindicates the MPC link for thissession.

Value Symbolic text Variable

The value of the correctparameter that is not correct.For example, if the REASONis INVALID PASSWORD,then the value is the contentof the invalid password that isin the session associationrequest.

Reason INVALID APPLID, INVALIDAPPLVERSION,INVALIDCUSTOMER.INVALIDNETNODEID,INVALIDPASSWORDRESOURCELIMITATIONINVALIDSCAIGRP,

Variable

The reason the sessionestablishment fails. Customerhost application ID.

The user gives an invalidapplication identification.

The user gives an invalidapplication version.

The user gives an invalidcustomer group

The user gives an invalidnetwork node identification.



Field Value FixedorVariable

Description

The user gives an invalidpassword

Not able to retrieve datablocks

The user gives an invalidSCAI group

Active message exampleSCAI100 MAY25 13:51:33 5169 FAIL_SESSION_ASSOCIATION_FAILED

LINK ID: DNA 123456789 PROTOCOL: 0 0 1 1

DEVICE: MPC: 0 LINK: 3

REASON : INVALID PASSWORD VALUE: ABCDEFGH



SCAI101The system generates log report SCAI101 after three attempts to associateto a link with wrong password occur. The SCAI101 log report enhances thepresent SCAI security system.

Remedial actionThe SCAI101 log report displays "multiple attempts with wrong password,"which indicates a session to a specific link.


FormatSCAI101 mmdd hh:mm:ss ssdd INFO WRONG_PASSWORD

LINK ID: len or dna

SCAI101 17



VariableDescription

INFOWRONG_PASSWORD

Constant Variable Indicates

LINK ID LEN or DNA,Integers

Variable Identifies the link for which threeattempts of session association withthe wrong password occur.

Active message exampleSCAI101 MAY25 13:51:33 5169 INFO WRONG PASSWORD

LINK ID: DNA 123456789



SCAI102 Format 1The system produces log report SCAI102 if orderly disassociation occursor abort disassociates a session. The log contains the session associationstart time stamp and the disassociation time stamp. The followingsummarizes the SCAI102 log report for both the X.25 and transmissioncontrol protocol (TCP) links:

• If the host application sends a DV_APPL_LOGON message with aHARD_RESET parameter set to T, the SCAI102 log report generates.

• If an established session exists and a DV_APPL_LOGON message isaccidentally sent with the HARD_RESET parameter set to T, then theSCAI102 log report does not generate.

The following summarizes the SCAI102 log report for X.25 and TCP links:

• If the one corrupt switched virtual circuit (SVC) link is the only link in asession, the session ID and session associations release. TheSCAI102 log report generates with the reasonHARDRESET_SESS_CLEAR.

• If the corrupt SVC detected is one of multiple SVCs in a session, theswitch clears only the session data of the corrupt SVC from thesession. The switch does not release the session id and all sessionassociations remain intact. The SCAI102 log report does not generate.These actions occur when the corruption is found in the sessioncurrently being logged onto or in another session other than the onebeing logged onto.



If the one corrupt SVC link is the only link in the session being logged onto,the session ID does not release, but session associations release.

When the host application sends a DV_APPL_LOGON message with theHARD_RESET parameter set to T for TCP links, the session id andsession associations release. Both the valid transport (if found) and thecorrupt data session clears. The SCAI102 log report generates with thereason HARDRESET_SESS_CLEAR.

If corrupt transports are detected in both an X.25 and TCP sessions, theSCAI102 log report generates with the reasonHARDRESET_TRANS_CLEAR. In both scenarios, the transport data iscleared.

Remedial actionn/a


FormatSCAI102 mmdd hh:mm:ss ssdd INFO SESSION_DISASSOCIATED

LINK ID:

DEVICE:

SCAI GROUP:

REASON: HARDRESET TRANS CLEAR


VariableDescription

REASON HARDRESET_SESS_CLEAR

Variable Identifies the reason for the sessiondisassociation and the specific loggeneration.

HARDRESET_TRANS_CLEAR

Variable Identifies the reason for the clearingof transport data and the specific loggeneration.

START TIME, STOPTIME

Variable Identifies the year (yyyy) the sessionwas established. Identifies the time ofday (hh:mm:ss) the session wasestablished. The range for hh:mm:ssis (0-23), (0-59) and (0-59). Identifies

SCAI102 Format 1 19


Field Value Fixed orVariable

Description

the fraction of seconds (ff). Identifiesthe weekday. This field onlyconsiders weekdays.

INFOSESSION_DISASSOCIATED

constant Variable Indicates the disassociation of asession by orderly disassociation orabort.

LINK ID LEN or DNA plusintegers

Variable Identifies the link on which orderlydisassociation or abort disassociatesthe session. The link is output whenthe switch/computer applicationinterface (SCAI) link uses integratedservices digital network (ISDN) basic-rate interface (BRI) transport.

DNA, integers Variable Identifies the calling data networkaddress (DNA). The DNA is outputwhen the SCAI link uses X.25transport.

Identifies the internet protocol (IP)address and the linkset name for aTCP link. The DNA and IP are output.

DEVICE ID 0 to 9 characters Variable Identifies the multiprotocol controller(MPC) and link information of anestablished session for an X.25 link.

This field does not apply to a TCPlink.

SCAI GROUP symbolic text Variable Identifies the name of the SCAIgroup. A maximum of 16 charactersis allowed.

Active message exampleSCAI102 MAY25 13:51:33 5169 INFO SESSION_DISASSOCIATED

LINK ID : DNA 000000000000000 PROTOCOL : 0 0 0 0

DEVICE :MPC :0 LINK: 3

SCAI GROUP:

REASON : HARDRESET TRANS CLEAR

START TIME: NOT AVAILABLE

STOP TIME: 1990/05/25 13:33:03.234 WED

SCAI102 MAY25 13:51:33 5169 INFO SESSION_DISASSOCIATED



LINK ID:DNA 000000000000000 PROTOCOL:protocol_id

DEVICE ID: 0000 LINK: 3

SCAI GROUP: SCAI_GRP1

REASON : HARDRESET SESS CLEAR

START TIME: 1990/05/25 09:15:01.123 WED

STOP TIME: 1990/05/25 13:33:03.234 WED


LINK ID:IP_ADDR 192 136 141 205 LINKSET:TCP_1

DEVICE: NOT APPLICABLE


REASON : HARDRESET TRANS CLEAR

START TIME: 1990/05/25 09:15:01.123 WED

STOP TIME: 1990/05/25 13:33:03.234 WED


LINK ID:IP_ADDR 192 136 141 205 LINKSET:TCP_1

DEVICE: NOT APPLICABLE


REASON : HARDRESET SESSCLEAR

START TIME: 1990/05/25 09:15:01.123 WED

STOP TIME: 1990/05/25 13:33:03.234 WED



SCAI103The system produces log report SCAI103 when the application continuitytest causes the switch to terminate a session.

SCAI103 21


The switch generates this log when the application continuity auditterminates a session in a linkset. The application continuity auditterminates a session if all of the following conditions apply:

• The linkset has the option CONTAUD in table SCAICOMS.

• The parameter AUDIT is Y.

• The parameter TERMINET is Y.

• None of the links in the linkset respond with a RETURN RESULT.

Remedial actionn/a


FormatSCAI103 date time segnbr INFO CONTINUITY_DISASSOCIATED

SCAI GROUP: <SCAI GROUP NAME> LINK: <X25 / TCP>

LINKSET NAME: <LINK SET NAME>

REASON: No response to continuity audit


VariableDescription

CONTINUITYDISASSOCIATED

Constant Variable This field indicates the disassociationof the continuity test.

SCAI GROUP mandatory/typeSCAI_GRPSCAI_GRP15

Variable This field application continuity testidentifies the name of the customergroup in the linkset.

LINK mandatory/typeSCAI_LINK X25

Variable This field identifies the type ofdisassociated link.

LINKSET NAME mandatory/typeTABLE [0-29] OFCHAR X25_TEMP

Variable This field identifies the name of theterminated linkset.

REASON optional/type TABLE[0-31] OF CHARCONTINUITY_DISASSOCIATED

Variable No response to continuity audit.




Description

START TIME mandatory/typeTABLE [0-27] OFCHAR

Variable This field identifies the time ofsession logon.

STOP TIME mandatory/typeTABLE [0-27] OFCHAR

Variable This field identifies the time ofsession termination.

Active message exampleSCAI103 JULY 1 13:51:33 INFO CONTINUITY DISASSOCIATED

SCAI GROUP: SCAI_GRP15 LINK: X25

LINKSET NAME: X25_TEMP

REASON: No response to continuity audit

START TIME: 1999/03/22 09:15:03.123 MON.

STOP TIME: 1999/03/22 10:40:04.234 MON.



SCAI200The system produces log report SCAI200 when a host does not respond toa DV-CALL-RECEIVED-C message in a predetermined time period. Theswitch sends the DV-CALL-RECEIVED message.

Remedial actionLog report SCAI200 indicates the following possibilities occur:

• The host is slow to respond

• The host response time exceeds the entered time

• The host is down.


FormatSCAI200 mmdd hh:mm:ss ssdd INFO NO_RESPONSE_FROM_HOST

SCAI200 23


MESSAGE: DV-CALL-RECEIVED-C

LINK ID: DNA or LEN SCAI GROUP: scai_group


VariableDescription

INFONO_RESPONSE_FROM_HOST

Constant Variable Indicates that the system does notreceive an expected response fromhost.

DV-CALL-RECEIVED-C

Constant Variable Identifies the message to which thehost does not respond

LINK ID LEN, Integers Variable The line equipment number (LEN)identifies the link on which thesession is associated. The LEN isoutput when the SCAI link uses ISDNBRI transport.

DNA, Integers Variable The calling data network address(DNA) identifies the link on which thesession is associated. The DNA isoutput when the SCAI link uses X.25transport.

SCAI GROUP Symbolic text Variable The name of the SCAI group. Amaximum of 16 characters.

Active message exampleSCAI200 MAY25 13:51:33 5169 INFO NO RESPONSE FROM HOST

MESSAGE: DV-CALL-RECEIVED-C

LINK ID: DNA 123456789 SCAI GROUP: SCAIGRP1



SCAI300The system produces a SCAI300 log when a standard problem with thebase of the switch computer application interface (SCAI) occurs.

Remedial actionNone, inactive, link




FormatSCAI300 mmdd hh:mm:ss ssdd FAIL SCAI_TRANSPORT_PROBLEM

LINK ID: Link_DNA PROTOCOL: Protocol_id

DEVICE: MPC: mpc_no LINK: link_no

REASON: error_reason VALUE: scai_return_value


VariableDescription

VALUE numeric Variable 0 = MPC Send OK1 = Bad MPCspecified in Send2 = Message sizeexceeds 242 bytes3 = MPC disables(SVC Reset, Cleared or card busied)4 = MPC system busiesor, when lastREASON above, the value is thenumber of lost messages from theSCAI work queue.

FAILSCAI_TRANSPORT_PROBLEM

Constant Variable Indicates a SCAI base transportfailure

LINK ID DNA Variable The DNA identifies the link on whichthe session association fails. DNAoutput occurs when the SCAI linkuses X.25 transport.

PROTOCOL 0 to 9 Variable The protocol used appears as fourintegers.

DEVICE Alphanumeric Variable Identifies the device and number ofthe associated equipment

LINK numeric Variable Identifies the link number on whichthe session failed

REASON INACTIVE LINK Variable The reason that the session failed

Active message exampleSCAI300 MAY 25 13:31:33 5169 FAIL SCAI TRANSPORT PROBLEM


DEVICE: MPC:0 LINK:2

SCAI300 25


REASON: INACTIVE LINK VALUE:0



SCAI301The SCAI301 log is generated to indicate that there is no room to enqueuea new message on the incoming or outgoing work queue. On a SCAI link,the rate of incoming or outgoing messages has exceeded the capability tosend outgoing messages long enough to exhaust the internal buffers.

Remedial actionThere is no short term action to be taken. If this condition persists, thecustomer using the link is exceeding the throughput capabilities of oneswitched virtual circuit. Therefore, the customer should provision a secondlink (or second switched virtual circuit within the same link).


FormatSCAI301 mmdd hh:mm:ss ssdd FAIL COULD NOT ENQUEUE MESSAGE



REASON: error_reason VALUE: scai_return_value


VariableDescription

FAIL COULD NOTENQUEUEMESSAGE

Constant Variable Indicates that there is no room toenqueue a new message on theincoming or outgoing work queue.

LINK ID LEN, DNA Variable The calling line equipment number(LEN) or data network address (DNA)identifies the link on which thesession association fails. LEN isoutput when the SCAI is using ISDNBRI transport. DNA is output whenthe SCAI link is using X.25 transport.




Description

PROTOCOL 0 to 9 Variable The protocol used displayed as fourintegers.

DEVICE Alpha-numeric Variable Identifies the device and number ofthe associated equipment.

LINK numeric Variable Identifies the link number on whichthe session failed.

REASON SCAI INCOMINGERROR, SCAIOUTGOING ERROR

Variable The reason that causes the sessionto fail.

VALUE numeric Variable 1 = Incoming queue failure 2 =Outgoing queue failure

Active message exampleSCAI301 MAY 25 13:51:33 5166 FAIL COULD NOT ENQUEUE MESSAGE



REASON: SCAI OUTGOING ERROR VALUE:02



SCAI302The system generates log report SCAI302 for the following reasons:

• Outgoing data that the multi-protocol controller (MPC) handles exceedsthe process rate of the MPC.

• Outgoing data that the MPC rejects the process rate of the MPC.

• A corrupt X.25 session terminates during hard reset and the switchcomputer application interface (SCAI) messages clear.

The SCAI302 log report does not generate when a TCP/IP session isterminated due to hard reset.

Remedial actionn/a

SCAI302 27



FormatSCAI302 mmdd hh:mm:ss ssdd FAIL SEND TO MPC FAILED

LINK ID: Link_DNA PROTOCOL ID: Protocol_id


REASON: error_reason VALUE: MPC_Return_code or Lost_count


VariableDescription

FAILSEND_TO_MPC_FAILED

constant Variable Indicates that the outgoing data thatthe MPC handles fails.

LINK ID LEN or DNA plusintegers (0 to 47)

Variable The calling line equipment number(LEN) or data network address (DNA)identifies the link on which thesession association fails. The LEN isoutput when the SCAI uses ISDNBRI transport. The DNA is outputwhen the SCAI link uses X.25transport.

PROTOCOL ID 0 to 9 Variable The protocol in use appears as fourintegers.

DEVICE alphanumeric Variable Identifies the device and number ofthe associated equipment.

LINK numeric Variable Identifies the link number on whichthe session fails.

REASON INACTIVE LINKSENDBAD SENDRCLINK CLEARED.LOST HARDRESET. LOST

Variable The reason the session fails.

VALUE numeric Variable 0 = MPC Send OK

1 = Bad MPC specified in Send

2 = Message size exceeds 242 bytes

3 = MPC is disabled (SVC Reset,Cleared or card busied)

4 = MPC is system busied




Description

or, when last REASON above, thevalue will be the number of lostmessages from the SCAI workqueue.

Active message exampleSCAI302 MAY 25 13:51:33 5166 FAIL SEND TO MPC FAILED

LINK ID: DNA 01208105 PROTOCOL ID: 1 1 1 1


REASON: INACTIVE LINK SEND VALUE:03



SCAI303The SCAI303 log generates when Flow Control is discarding messagescaused by the host ignoring a flow control message.

Remedial actionn/a


FormatSCAI303 mmdd hh:mm:ss ssdd INFO Flow_control_Warning

LINK ID: <Link_DNA> PROTOCOL: <Protocol_id>

DEVICE: MPC:<mpc_no> LINK: <link_no>

REASON: <warning_reason>

SCAI303 29



VariableDescription

INFO WARNINGFLOW CONTROL

Constant Variable Indicates that the Flow Control isdiscarding messages.

LINK ID LEN, DNA Variable The calling line equipment number(LEN) or data network address (DNA)identifies the link on which thesession association fails. LEN isoutput when the SCAI is using ISDNBRI transport. DNA is output whenthe SCAI link uses X.25 transport.

PROTOCOL 0 to 9 Variable The protocol used displays as fourintegers.

DEVICE alphanumeric Variable Identifies the device and number ofthe associated equipment.

LINK number Variable Identifies the link number on whichthe session failed.

REASON Flow ControlEnabled

Variable The reason that causes the sessionto fail.

Active message exampleSCAI303 May25 13:51:33 INFO WARNING: FLOW CONTROL

LINK ID: DNA: 01208105 PROTOCOL: 1 1 1 1


REASON: Flow Control Enabled



SCAI311The Switch-Computer Application Interface (SCAI) subsystem generatesthis report whenever no room is available for a new message in theincoming or outgoing work queue for a Transmission Control Protocol/Internet Protocol (TCP/IP) SCAI link. This log is analogous to the SCAI301log for the X.25 SCAI link.



Remedial actionNo short-term action is necessary. If the condition persists, the subscriberusing the link is exceeding the capabilities of the TCP/IP SCAI session.Therefore, the subscriber should provision additional TCP/IP SCAIsessions.


FormatSCAI311 mmdd hh:mm:ss ssdd FAIL COULD NOT ENQUEUE MESSAGE

LINKID: IP_ADDR: XXX XXX XXX XXX

LINKSET NAME: scai_coms_linkset

REASON : error_reason VALUE: scai_return_value


VariableDescription

FAIL COULD NOTENQUEUEMESSAGE

Constant Variable Indicates that no room is available toenqueue a new message on theincoming or outgoing work queueused for a TCP/IP SCAI link.

LINK ID: IP_ADDR 0 to 255 Variable Displays the Internet Protocol (IP)address of the host computer as fourintegers.

LINKSET NAME Symbolic text Variable Displays the name of the linkset datafilled in table SCAICOMS for theSCAI session in use.

REASON SCAI INCOMINGERROR or SCAIOUTGOING ERROR

Variable Displays the reason that causes thesession to fail.

VALUE Numeric Variable 1 = incoming queue failure

2 = outgoing queue failure

Active message exampleSCAI311 JUL22 18:57:33 3300 FAIL COULD NOT ENQUEUE MESSAGE

LINK ID: IP_ADDR: 47 4 162 167

LINKSET NAME: TCP_INTRANET_2

SCAI311 31


REASON : SCAI OUTGOING ERROR VALUE: 2



SCAI400The system outputs the SCAI400 log when a Switch Computer ApplicationInterface (SCAI) link enters an alarm state. The alarm severity is based ona LINKSET condition. The alarm severity is based on a percentage ofSCAI links in a LINKSET and the number of SCAI links in an alarm state.

Remedial actionThere is no immediate action required. The user can post the link in theSCAI level in the maintenance administrative position command interpreter(MAPCI).

AttributesAttribute ValueSeverity • Warning

• Critical

• Major

• Minor

Format***SCAI400 mmdd hh:mm:ss ssdd INFO LINKSET ALARM STATUS

LINKSET NAME: linkset_name


DIVICE: MPC: mpc_no LINK: link_no

ALARM LEVEL: alarmjevel

LAST ALARM LEVEL: previous_alarm_level

REASON: reason_text




VariableDescription

alarm ***, **, *, or blank Variable Indicates the alarm type of the logreport. ** *= critical alarm, * *= majoralarm, *= minor alarm, blank = noalarm.

INFO LINKSETALARM STATUS

Constant Variable Indicates that a SCAI link enters analarm state.

LINKSET NAME mandatory variable Variable See table SCAICOMS for descriptionof linkset name.

LINK ID DNA Variable The (DNA) identifies the link on whichthe session association fails. TheDNA is output when the SCAI linkuses X.25 transport.

PROTOCOL 0 to 9 Variable The protocol in use appears as fourintegers.

DEVICE Alpha-numeric Variable Identifies the device and number ofthe associated equipment.

LINK numeric Variable Identifies the link number on whichthe session fails.

ALARM LEVEL minor, major, critical Variable Indicates the alarm severity of thelink.

LAST ALARMLEVEL

minor, major, critical Variable Indicates the previous alarm severityof the link.

REASON text string Variable This field indicates when the alarmcondition of a link clears. Clearanceallows the system to output a log.This log shows the new alarmcondition of the linkset to which thislink belongs.

Active message example***SCAI400 FEB11 13:26:25 9313 INFO LINKSET ALARM STATUS

LINKSET NAME: LINKSET1

LINK ID: DNA 01208098 PROTOCOL:0 0 0 0 0

DEVICE: MPC: 5 LINK:3

ALARM LEVEL:CRITICAL

LAST ALARM LEVEL: MAJOR

REASON: 7 OF 8 LINKS IN LINKSET AFFECTED. SVC CLEARED

SCAI400 33




SCAI500The SCAI500 log report indicates when an agent is reassigned to anothersubgroup. The dv-Reassign-Agent message effects the agent by assigninga different supervisor.

Occurrence of the SCAI500 log report indicates that the parameter AgentPosition ID identifies the position ID. The parameter Cust Group identi esthe customer group of the agent and supervisor. The parameter NewSupervisor Position ID identifies the position ID of the customer to thesubgroup. When the reassignment occurs, the parameter Session ID givesthe ID of the session.

Remedial actionn/a


FormatSCAI500 mmdd hh:mm:ss INFO ICM_Reassign_Agent

CUST GROUP: <CHARKEY>

AGENT POSITION ID: <AGENT''S POSID>

NEW SUPERVISOR POSID: <NEWSUPERVISOR POSID>

JOURNAL FILE ACTIVE: <YES or NO>


VariableDescription

date, time, segnbr,INFO

$info Variable This field gives the information aboutthe time and type of occurrence.

Cust Group DESCOFCHAR Variable This field gives the customer groupname for the reassignment.

Agent Position ID Int Variable This field gives the position ID of thechanged agent's supervisor.




Description

New SupervisorPosID

Int Variable This field gives the position ID of thenew supervisor for the agent.

Journal File Active Yes or No Variable This field gives when the journal fileis active for the event.

Active message exampleSCAI500 JULY 1 13:51:33 INFO ICM Reassign Agent

CUST GROUP: BNR

AGENT POSITION ID: 2219

NEW SUPERVISOR POSID: 1234

JOURNAL FILE ACTIVE: Yes



SCAI501The SCAI501 log indicates when feature ICM Configuration Managementchanges variable wrap-up time for an Automatic Call Distribution (ACD)agent or an ACD group.

The SCAI501 log report indicates the following possibilities:

• The dv-Set-Feature changes the variable wrap time for the agent, if theTable Changed parameter contains ACDLOGIN or ACDENLOG.

• The dv-Set-Feature changes the variable wrap time for the group, if theTable Changed parameter contains ACDGRP.

• The Orig Address field provides the source of the request. The OrigAddress field contains a 4-digit position ID (posid) when the request ismade for an agent. The Orig Address field contains a 10-digit directorynumber when the request is made for the group.

Remedial actionn/a


SCAI501 35


FormatSCAI501 mmmdd hh:mm:ss INFO Change_Varwrap

NEW WRAP: <new wrap time>

TABLE CHANGED: <ACDGRP, ACDENLOG, ACDLOGIN>

JOURNAL FILE ACTIVE: <yes, no>


VariableDescription



New Wrap Int Variable This field gives the new variable wraptime.

Table changed DESOFCHAR Variable This field identifies the changedtable.

Orig Address DESCOFCHAR Variable This field provides the originaladdress of the request.

Journal file active DESCOFCHAR Variable This field identifies if the journal file isactive for the event

Active message exampleSCAI501 JULY 01 13:51:33 INFO Change Varwrap

NEW WRAP: 11

TABLE CHANGED: ACDGRP

ORIG ADDRESS: 1287022134

JOURNAL FILE ACTIVE: YES



SCAI502The SCAI502 log report indicates when the call forcing option for anAutomatic Call Distribution (ACD) agent or an ACD group has changed.The ICM Configuration Management feature changes option call forcing toactive in the HSET, BASE, or None.



The SCAI502 log report indicates the following possibilities:

• The message dv-Set-Feature changes option call forcing for the agent,if the Table Changed parameter contains ACDLOGIN andACDENLOG.

• The message dv-Set-Feature changes option call forcing for the group,if the Table Changed parameter contains ACDGRP.

• The Orig Address field provides the source of the request. The OrigAddress field contains a 4-digit posid when the request is made for anagent. The Orig Address field contains a 10-digit directory numberwhen the request if made for the group.

Remedial actionn/a


FormatSCAI502 mmmdd hh:mm:ss INFO ICM_Change_Forcing

NEW FORCE: <New call forcing option>

TABLE CHANGED <ACDGRP, ACDENLOG, ACDLOGIN>

ORIG ADDRESS: <originating_address>

JOURNAL FILE ACTIVE: <yes or no>


VariableDescription



New Force DESCOFCHAR Variable This field gives the new forcingoption.

Table Changed DESCOFCHAR Variable This field indicates the changedtable.

Orig Address DESCOFCHAR Variable This field provides the originaladdress of the request.

Journal File Active DESCOFCHAR Variable This field indicates when the journalfile is active for the event.

SCAI502 37


Active message exampleSCAI502 JULY01 13:51:33 4827 INFO ICM Change Forcing

New Force: BASE

TABLE CHANGED: ACDENLOG

ORIG ADDRESS: 2987

JOURNAL FILE ACTIVE: Yes



SCR100The Selective Charge Recording (SCR) subsystem generates log reportSCR100. The subsystem generates this report at the completion of a callfor which the calling party activates selective charge recording (SCR). Thecalling party activates SCR before the calling party dials the calleddirectory number (DN). The user must assign the SCR option as a lineoption, to the calling DN. The user uses order procedures to assignoptions.

Remedial actionWhen you receive log report SCR100, collect payment for charges the callacquires. If the log indicates 0 charges, make sure that the duration is 0.Toll calls produce two logs: one with 0 charges and one with charges thatthe rating system or metering information evaluates.

In China, the rating system evaluates the toll charges. The log that thesystem generates as a result of metering information access indicates 0charges. The user must ticket dial calls that are not direct. The user usesthe answer time and duration fields to ticket the calls.


FormatSCR100 mmmdd hh:mm:ss ssdd INFO SCR LOG ENTRY

Msgcnt clgno: dn cldno: dn dd/mm Answer time hh:mm

Duration: MMM Chgs Bth: 0




VariableDescription

INFO SCR LOGENTRY

Constant Variable Indicates a report of SCRinformation.

Msgcnt Integers Variable Indicates the number of SCR logsthat the system generates.

clgno Symbolic text Variable Identifies the DN of the originator.cldno Symbolic text Variable Identifies the DN of the terminator.dd/mm Integers Variable Indicates the date the call originates.Answer time Integers Variable Indicates the time in hours and

minutes the system answers the call.Duration Integers Variable Indicates the call duration in minutes.Chgs Integers Variable Indicates the charges that the calling

party acquires.Bth Integers Variable Indicates the booth number.

Active message exampleSCR100 JAN29 15:54:25 7645 INFO SCR LOG ENTRY

14 44312 791334327 28/02 13:20 020 23056 0



SDM307 Format 1The system log report SDM307. The system generates SDM307 forSuperNode Data Manager (SDM) internal use only. The system does notsend this log to the operations support system (OSS). The SDM remotemaintenance interface (RMI) can show log SDM307 when a user logs on tothe SDM. The SDM307 log indicates that the process controller stopped anapplication process.

The system generates SDM307 in two formats. Format 1 contains aheader. Format 2 does not contain a header because the system does notsend format 2 to the OSS.

The system does not generate SDM307 for Telecom 06 and up.

Remedial actionn/a

SDM307 Format 1 39



FormatSDM307

Package: <package_name>

Process: <process_name>

State: <action>

Day mmm dd hh:mm:ss yyyy


VariableDescription

package_name character string Variable Indicates the package that had thefailure.

process_name character string Variable Indicates which process in thepackage failed.

action stopped Variable Indicates the process stopped.

Active message exampleSDM307

Package: tasl

Process: /sdm/tasl/das/taslddm

State: stopped

Mon Oct 30 18:08:19 1995



SDM307 Format 2The system log report SDM307. The system generates SDM307 forSuperNode Data Manager (SDM) internal use only. The system does notsend this log to the operations support system (OSS). The SDM remote



maintenance interface (RMI) can show log SDM307 when a user logs on tothe SDM. The SDM307 log indicates that the process controller stopped anapplication process.

The system generates SDM307 in two formats. Format 1 contains aheader. Format 2 does not contain a header because the system does notsend format 2 to the OSS.

The system does not generate SDM307 for Telecom 06 and up.

Remedial actionn/a


FormatSDM307

The high availability system has started. No processes arerunning.


VariableDescription

package_name character string Variable Indicates the package that had thefailure.

process_name character string Variable Indicates which process in thepackage failed.

action stopped Variable Indicates the process stopped.

Active message exampleSDM307

The high availability system has started. No processes arerunning.


SDM307 Format 2 41



SDS600The following pegged OM group SDS register generates the SDS600 logreport:

• SOFTFAIL

The reason specified in the log report indicates that there is a softwarefailure. For example, no feature data block is available.

• ANNCFAIL

The reason specified in the log report indicates that the register can notprovide an SDS announcement. Also the reason indicates either the failedannouncement is an offer-of-service announcement or a helpannouncement.

• UTRSHORT

The reason specified in the log report indicates that there is no universaltone receiver (UTR) available.

Remedial actionSave the log report for additional information to investigate the failure ofSDS.


Formatlogoffid SDS600 mmmdd hh:mm:ss nnnn INFO SDS log report

Reason : the condition that caused an operationalmeasurement

to be pegged in OM group SDS

Call ID : call identification number

Calling DN : calling party directory number




VariableDescription

logoffid Symbolic text Variable LOG_OFFICE_ID - an officeparameter defined in table OFCVARthat specifies the name for officeidentification in the log output header

mmmdd Symbolic text Variable date the log was generated inmonth:day format

hh:mm:ss Symbolic text Variable time at which the log was generatedin hour:minute:second format

nnnn Symbolic text Variable sequential number of logsINFO SDS log report Constant Variable log report typeReason Text Variable text of 22 characters maximum. The

possible reasons are the following:

'Reverse Trans failure ''No UTRavailable ''Basic announc. failure''Help announc. failure ''No fdbavailable ''Cannot start a timer ''Noext block available'

Call ID Symbolic text Variable call identification numberCalling DN Symbolic text Variable calling party directory number (10

digits)

Active message exampleMTLEN04AG SDS600 DEC10 12:30:55 3800 INFO SDS log report

Reason : No UTR available

Call ID : 53

Calling DN : 6137224065

MTLEN04AG SDS600 APR03 12:10:15 3800 INFO SDS log report

Reason : ACBMSGAN NIL

Call ID : 53

Calling DN : 6137224065


SDS600 43



SDS601The subsystem generates the SDS601 log report when operationalmeasurement (OM) group SDS register ROUTFAIL increases. Thisregister increases when an attempt to route a call to an SDS messagingrouting directory number (DN) fails. A treatment is set by the originatingswitch, as part of the operation of the Access to Messaging feature. TheSDS messaging routing DN corresponds to a Voice Messaging System(VMS) location.

Remedial actionSave the log report for additional information to investigate the failure ofAccess to Messaging service.


Formatlogoffid SDS601 mmmdd hh:mm:ss nnnn INFO SDS log report

Call ID :call identification number

Calling DN :calling party directory number

SDS DN :SDS messaging routing DN

Reason :the reason for the generation of the log

Treatment :call treatment associated with the routingfailure


VariableDescription

logoffid Symbolic text Variable The LOG_OFFICE_ID is an officeparameter, defined in table OFCVAR,which specifies the name for officeidentification in the log output header.

mmmdd Symbolic text Variable Indicates the date, in month:dayformat, that the subsystem generatedthe log.

hh:mm:ss Symbolic text Variable Indicates the time the subsystemgenerated the log inhour:minute:second format




Description

nnnn Symbolic text Variable Sequential number of logsINFO SDS log report Constant Variable Log report typeCall ID Symbolic text Variable Call identification numberCalling DN Symbolic text Variable Calling party directory number (10

digits)SDS DN Symbolic text Variable SDS messaging routing DN (a

maximum of 30 digits)Reason Constant Variable Fails to route to callTreatment Symbolic text Variable Call treatment associated with the

routing failure (4 characters)

Active message exampleMTLEN04AG SDS601 APR03 12:10-:15 3800 INFO SDS log report

Call ID :67

Calling DN :6137224065

SDS DN :6137211234

Reason :Fails to re-route call

Treatment :GNCT



SECU101The Security (SECU) subsystem generates SECU101. The subsystemgenerates SECU101 when a valid user uses normal login/logoffprocedures to log on or off of a terminal.

Remedial actionSave the report for security personnel.


SECU101 45


FormatSECU101 mmmdd hh:mm:ss ssdd INFO

User: <user> logtxt <term>


VariableDescription

INFO Constant Variable Indicates information about theSECU subsystem

User Descriptive text Variable Identifies user that logged on or off ofa specified terminal. Use the CIcommand SHOWUSERS for a list ofusers defined to the system.

logtxt logged IN to Variable Identifies user that logged on theterminal

logged OUT from Variable Identifies user that logged off of theterminal

term Descriptive text Variable Identifies the terminal where the userlogged on or off. List TERMDEV fromCI MAP level for list of terminals.

Active message exampleSECU101 APR01 12:00:00 2112 INFO

User: JANET logged OUT from MAP



SECU102The Security (SECU) subsystem generates SECU102. The subsystemgenerates SECU102 when a user uses an invalid identification orpassword to attempt to login on a terminal.

Remedial actionSave report for security personnel.





Invalid LOGIN attempt on <term>. USERID: <user>. reastxt.


VariableDescription


Invalid LOGINattempt

Symbolic text Variable Identifies the terminal on which theuser attempted to login. ListTERMDEV from CI MAP level for listof terminals.

USERID Bad user Variable Indicates use of invalid useridentification to attempt login onterminal

0000-FFFF Variable Provides valid identification for a userthat attempts to login the terminal.Use the CI command SHOWUSERSfor a list of users defined to thesystem.

reastxt Bad password Variable Indicates the user attempted to loginthe terminal with an invalid password.

Password expired Variable Indicates the user attempted to loginthe terminal with an expiredpassword.

Bad userid Variable Indicates the user attempted to loginthe terminal with an invalid useridentification.


Invalid LOGIN attempt on MAP. USERID: JANET. Bad

password.



SECU103The Security (SECU) subsystem generates SECU103 when one userforces another user off the terminal. Both users are logged on this terminal.

SECU103 47





User: <user> forced out from <term>.

By Command from user <usernm> on <termnm>.


VariableDescription


User Symbolic text Variable Identifies the user forced off theterminal. Use the CI commandSHOWUSERS for a list of usersdefined to the system.

forced out from Symbolic text Variable Identifies terminal that one userforced the other user off. ListTERMDEV from CI MAP level for listof terminals.

By command fromuser

Constant Variable Identifies the user forcing the otheruser off the terminal. Use the CIcommand SHOWUSERS for a list ofusers defined to the system.

on Symbolic text Variable Identifies the terminal used to forcethe user off. Use the CI commandSHOWUSERS for a list of usersdefined to the system.


User: JANET forced out from MAP.

By Command from user OPERATOR on MAP.





SECU104The Security (SECU) subsystem generates SECU104 when a userchanges one of the following:

• the commandset class for a privileged command,

• the automatic logging of command use/abuse in customer data TableCMDS.

Line three (old commandset), line five (old use log/alarm) and line seven(old abuse log/alarm) can appear. The system displays these lines if thecommand was present in CMDS and the user changed the tuple for thatcommand.



• Minor

• Major

• Critical


User: <user> from <term>. CMDS changed to <cmdnm>.

old commandset: n,n,n,n,n.

new commandset: n,n,n,n,n.

old use log/alarm: B/alrmtxt

new use log/alarm: B/alrmtxt

old abuse log/alarm: B/alrmtxt

new abuse log/alarm: B/alrmtxt

SECU104 49



VariableDescription

User Symbolic text Variable Identifies the user that changes thecommandset or the automatic loggingof command use/abuse in TableCMDS. Use the CI commandSHOWUSERS for a list of usersdefined to the system.

from Symbolic text Variable Identifies the terminal from which theuser made the change(s). ListTERMDEV from CI MAP level for listof terminals.

CMDS changed tocommand

Symbolic text Variable Identifies the changed command inCMDS. List CMOS from CI MAP levelfor privileged commands. Refer tocustomer data Table TERMDEV.

old commandset 0-30 Variable Identifies the commandset classpreviously able to execute thecommand.

ALL Variable Indicates all commandset classeswere necessary in order to executethe command

NONE Variable Indicates that commandset classeswere not necessary to execute thecommand. All users were able toexecute the command.

new commandset 0-30 Variable Identifies commandset class nowable to execute the command

ALL Variable Indicates the system requires allcommandset classes to execute thecommand.

NONE Variable Indicates commandset classes arenot required to execute thecommand. All users are now able toexecute the command.

old use log/alarm NO/NO_ALARM Variable Indicates that automatic logging ofuse was not in effect. Use of thecommand did not raise an alarm.

YES/NO_ALARM Variable Indicates that automatic logging ofuse was in effect. Use of thecommand did not raise an alarm.

NO/MINOR Variable Indicates that automatic logging ofuse was not in effect. Use of thecommand raised a minor alarm.




Description

YES/MINOR Variable Indicates that automatic logging ofuse was in effect. Use of thecommand raised a minor alarm.

NO/MAJOR Variable Indicates that automatic logging ofuse was not in effect. Use of thecommand raised a major alarm.

YES/MAJOR Variable Indicates that automatic logging ofuse was in effect. Use of thecommand raised a major alarm.

NO/CRITICAL Variable Indicates that automatic logging ofuse was not in effect. Use of thecommand raised a critical alarm.

YES/CRITICAL Variable Indicates that automatic logging ofuse was in effect. Use of thecommand raised a critical alarm.

new use log/alarm NO/NO_ALARM Variable Indicates that automatic logging ofuse is not in effect. Use of thecommand did not raise an alarm.

YES/NO_ALARM Variable Indicates that automatic logging ofuse is in effect. Use of the commanddid not raise an alarm.

NO/MINOR Variable Indicates that automatic logging ofuse is not in effect. Use of thecommand raised a minor alarm.

YES/MINOR Variable Indicates that automatic logging ofuse is in effect. Use of the commandraised a minor alarm.

NO/MAJOR Variable Indicates that automatic logging ofuse is not in effect. Use of thecommand raised a major alarm.

YES/MAJOR Variable Indicates that automatic logging ofuse is in effect. Use of the commandraised a major alarm.

NO/CRITICAL Variable Indicates that automatic logging ofuse is not in effect. Use of thecommand raised a critical alarm.

YES/CRITICAL Variable Indicates that automatic logging ofuse is in effect. Use of the commandraised a critical alarm.

old abuse log/alarm NO/NO_ALARM Variable Indicates that automatic logging ofabuse was not in effect. Abuse of thecommand did not raise an alarm.

SECU104 51



Description

YES/NO_ALARM Variable Indicates that automatic logging ofabuse was in effect. Abuse of thecommand did not raise an alarm.

NO/MINOR Variable Indicates that automatic logging ofabuse was not in effect. Abuse of thecommand raised a minor alarm.

YES/MINOR Variable Indicates that automatic logging ofabuse was in effect. Abuse of thecommand raised a minor alarm.

NO/MAJOR Variable Indicates that automatic logging ofabuse is not in effect. Abuse of thecommand raised a major alarm.

YES/MAJOR Variable Indicates that automatic logging ofabuse was in effect. Abuse of thecommand raised a major alarm.

NO/CRITICAL Variable Indicates that automatic logging ofabuse was not in effect. Abuse of thecommand raised a critical alarm.

YES/CRITICAL Variable Indicates that automatic logging ofabuse was in effect. Abuse of thecommand raised a critical alarm.

new abuse log/alarm NO/NO_ALARM Variable Indicates that automatic logging ofabuse is not in effect. Abuse of thecommand did not raise an alarm.

YES/NO_ALARM Variable Indicates that automatic logging ofabuse is in effect. Abuse of thecommand did not raise an alarm.

NO/MINOR Variable Indicates that automatic logging ofabuse is not in effect. Abuse of thecommand raised a minor alarm.

YES/MINOR Variable Indicates that automatic logging ofabuse is in effect. Abuse of thecommand raised a minor alarm.

YES/MAJOR Variable Indicates that automatic logging ofabuse is in effect. Abuse of thecommand raised a major alarm.

NO/CRITICAL Variable Indicates that automatic logging ofabuse is not in effect. Abuse of thecommand raised a critical alarm.

YES/CRITICAL Variable Indicates that automatic logging ofabuse is in effect. Abuse of thecommand raised a critical alarm.




User: JANET from MAP. CMDS changed to RESTART.

old commandset: 1,3,4,5,6.

new commandset: 3,4,5,6.

old use log/alarm: NO/NO_ALARM

new use log/alarm: YES/MINOR

old abuse log/alarm: NO/MAJOR

new abuse log/alarm: YES/CRITICAL



SECU105The Security (SECU) subsystem generates SECU105 when one userchanges the password for another user.




User:<user> on <term>. Password has been changed for<usernm>.

SECU105 53



VariableDescription

INFO Constant Variable Indicates information about theSECU subsystem.

User Symbolic text Variable Identifies the user that changes thepassword. Use the CI commandSHOWUSERS for a list of usersdefined to the system.

on Symbolic text Variable Identifies the terminal where the userchanged the password. ListTERMDEV from CI MAP level for listof terminals.

Password has beenchanged for

Symbolic text Variable Identifies the user that had passwordchanged. Use the CI commandSHOWUSERS for a list of usersdefined to the system.


User: JANET on MAP. Password has been changed for OPERATO]



SECU106The Security (SECU) subsystem generates SECI106 when a user with theproper command class set issues a command. The command is entered incustomer data Table CMDS. The system executes the command.




User: <user> on <term>. Valid use of command <cmdnm>.




VariableDescription


User Symbolic text Variable Identifies the user that issues thecommand. Use the CI commandSHOWUSERS for a list of usersdefined to the system.

on Symbolic text Variable Identifies the terminal where the userissued the command. List TERMDEVfrom CI MAP level for list ofterminals.

Valid use ofcommand

Symbolic text Variable Identifies the command that a userwith the correct commandset issues.List CMDS from CI MAP level forprivileged commands.


User: JANET on MAP. Valid use of command RESTART



SECU107The Security (SECU) subsystem generates SECU107 when a user withoutthe correct command class set issues a command. The command isentered in customer data Table CMDS. The system does not execute thecommand.




User: <user> on <term>. *UNABLE* to use command: cmdnm

SECU107 55


User''s effective commandset: n,n,n,n.

Command''s commandset: n,n,n,n.


VariableDescription

User Symbolic text Variable Identifies the invalid user that issuesthe command. Use the CI commandSHOWUSERS for a list of usersdefined to the system.

on Symbolic text Variable Identifies the terminal where theinvalid user issued the command. ListTERMDEV from CI MAP level for listof terminals.

*UNABLE *tousecommand

Symbolic text Variable Identifies the privileged commandissued by the invalid user. List CMDSfrom CI MAP level for privilegedcommands.

User's effectivecommandset

0-30 Variable Provides the command class set forthe user that issues the command.

ALL Variable Indicates the user is authorized toexecute all commands.

NONE Variable Indicates the user does not have acommand class set.

Command'scommandset

0-30 Variable Provides command class set for thecommand.

ALL Variable Indicates the system requires allcommand classes to execute thecommand.

NONE Variable Indicates the system does not requirecommand classes to execute thecommand.



User: JANET on MAP. *UNABLE* to use command: RESTART

User''s effective commandset: 3,2,3,4.

Command''s commandset: 3,2,3,4,8.





SECU108The Security (SECU) subsystem generates SECU108. The subsystemgenerates SECU108 when a user without the correct command class setattempts to access a table. The user does not access the table.




User: <user> on <term>. *UNABLE* to access table: <tbl>

User''s effective commandset: n,n,n,n.

table''s commandset: n.


VariableDescription


User Symbolic text Variable Identifies the invalid user thatattempts to access the table. Use CIcommand SHOWUSERS for a list ofusers defined to the system.

on Symbolic text Variable Identifies the terminal where aninvalid user attempted to access atable. List TERMDEV from CI MAPlevel for list of terminals.

*UNABLE *to accesstable

Symbolic text Variable Identifies customer data table theuser attempted to access. RefertoCustomer Data Schema,297-1001-451, for index to customerdata tables.

SECU108 57



Description

User's commandset 0-30 Variable Provides command class set for theuser that attempts to access thetable.

NONE Variable Indicates the user does not have acommand class set.

ALL Variable Indicates the user is authorized toaccess all tables.

table commandset 0-30 Variable Provides the command class setrequired to access the table.

NONE Variable Indicates the user does not requirecommand classes to access thetable.

ALL Variable Indicates a user with a full-privilegecommand class set can access thetable.


User: JANET on MAP. *UNABLE* to access table: TERMDEV

User''s effective commandset: 3,2,3,4.

table''s commandset: 8.



SECU109The Security (SECU) subsystem generates SECU109 when a valid userlogs on a terminal using priority login (PLOGIN) procedures.






User: <user> PLOGINing on <term>.


VariableDescription


User Symbolic text Variable Identifies the user that logged on theterminal with PLOGIN procedures.Use CI command SHOWUSERS fora list of users defined to the system.

PLOGINing on Symbolic text Variable Identifies the terminal user logged onwith PLOGIN procedures. ListTERMDEV from CI MAP level for listof terminals.


User: JANET PLOGINing on MAP.



SECU110The Security (SECU) subsystem generates SECU110. The subsystemgenerates SECU110 when a user attempts a priority login (PLOGIN) on aterminal with an invalid identification or password.




Invalid PLOGIN attempt on: <term>. USERID: <user>. reastxt.

SECU110 59



VariableDescription


Invalid PLOGINattempt on

Symbolic text Variable Identifies the terminal where userattempted to PLOGIN. ListTERMDEV from CI MAP level for listof terminals.

USERID Bad user Variable Indicates use of invalid useridentification to attempt PLOGIN onthe terminal. The field reastxt isblank.

Symbolic text Variable Identifies the valid user thatattempted PLOGIN on terminal. UseCI command SHOWUSERS for a listof users defined to the system.

reastxt Bad Password Variable Indicates the user attempted toPLOGIN on the terminal with aninvalid password.

Bad userid Variable Indicates the user attempted toPLOGIN on the terminal with aninvalid user identification. (USERID =Bad user)


Invalid PLOGIN attempt on: MAP. USERID: JANET. Bad Password



SECU111The Security (SECU) subsystem generates SECU111 when a userchanges the command class set for a terminal. Customer data TableTERMDEV defines the command class set for a terminal.






User: <user> on <term>. TERMDEV COMCLASS changed for <term>

Old commandset: n,n,n,n,n.

New commandset: n.


VariableDescription


User Symbolic text Variable Identifies the user that changed thecommand set for a terminal thatTERMDEV defines. Use CI commandSHOWUSERS for a list of usersdefined to the system.

on Symbolic text Variable Identifies the terminal where the userchanged another terminalcommandset. List TERMDEV from CIMAP level for list of terminals.

TERMDEVCOMCLASSchanged for

Symbolic text Variable Identifies the terminal that the userchanged the command set inTERMDEV. List TERMDEV from CIMAP level for list of terminals.

Old commandset 0-30 Variable Identifies the command class set theuser earlier assigned to terminal.

ALL Variable Indicates the user assigned allcommand classes to the terminal.

NONE Variable Indicates the user did not assigncommand classes to the terminal.

New commandset 0-30 Variable Identifies the command class set nowassigned to the terminal.

ALL Variable Indicates the user assigned allcommand classes to the terminal


SECU111 61


User: JANET on MAP. TERMDEV COMCLASS changed for MAPI

Old commandset: 3,4,5,6.

New commandset: 8.



SECU112The Security (SECU) subsystem generates SECU112 when one user addsor changes the security profile for another user .




User: <user> on <term>. <type> user <user>

Old Stack nnnn

Old Priority nnnn

Old Language <lang>

Old Commandset n,n,n,n.

New Stacknnnn

New Priority nnnn

New Language <lang>

New Commandset n,n,n,n.




VariableDescription


User Symbolic text Variable Identifies the user that adds orchanges the security profile ofanother user. Use CI commandSHOWUSERS for a list of usersdefined to the system.

on term Symbolic text Variable Identifies the terminal where the useradded or changed the security profileof another user. List TERMDEV fromCI MAP level for list of terminals.

type ADD Variable Indicates addition of a new userCHANGED Variable Indicates the current user has had

attributes changed.user 0000-FFFF Variable Identifies the user with the changed

security profile. Use CI commandSHOWUSERS for a list of usersdefined to the system.

Old Stack 1500-8000 Variable Identifies number of words for olduser process. This field appearswhen<type>= CHANGED.

Old Priority 1-4 Variable Identifies priority of old user process.This field appears when<type>=CHANGED.

Old Language English, French,German, Spanish,Turkish

Variable Identifies the user interface languagefor user.

Old commandset 0-30 Variable Identifies command class set earlierassigned to user. This field displayedwhen<type>= CHANGED.

ALL Variable Indicates that the user assigned theother user to all command classes.This field appears when<type>=CHANGED.

NONE Variable Indicates that the user did not assignthe other user to any commandclasses. This field appearswhen<type>= CHANGED.

New Stack 1500-8000 Variable Identifies the number of words for thenew user process.

New Priority 1-4 Variable Identifies priority of new userprocess.

SECU112 63



Description

New Language English, French,German, Spanish,Turkish

Variable Identifies user interface language foruser.

New commandset 0-30 Variable Identifies command class setassigned to user.

ALL Variable Indicates the user assigned the otheruser to all command classes.

NONE Variable Indicates the user did not assign theother user to any command classes.


User: JANET on MAP. CHANGE user LISA

Old Stack 4000

Old Priority 3

Old Language English

Old Commandset 1,2,3,4.

New Stack 5000

New Priority 4

New Language Spanish

New Commandset 1,2,3,4.



SECU113The Security (SECU) subsystem generates SECU113. The systemgenerates SECU113 when a user makes an attempt to login on a terminalthat is not enabled.






Attempt to login on disabled console: <term>


VariableDescription


Attempt to LOGIN ondisabled console

Symbolic text Variable Identifies the terminal where the usermade the attempt to login. ListTERMDEV from CI MAP level for listof terminals.


Attempt to LOGIN on disabled console: DIALUP



SECU114The Security (SECU) subsystem generates SECU114 when a console ismanually enabled or disabled.




User: <user> on <term>. Manually <able>: <term>

SECU114 65



VariableDescription


User Symbolic text Variable Identifies the user that enabled ordisabled the terminal. Use CIcommand SHOWUSERS for a list ofusers defined to the system.

on Symbolic text Variable Identifies the terminal that the userused to enable or disable anotherterminal. List TERMDEV from CIMAP level for list of terminals. Referto customer data Table TERMDEV.

Manually DISABLE Variable Indicates the user manually disabledthe terminal.

ENABLE Variable Indicates the user manually enabledthe terminal.

term Symbolic text Variable Identifies the user manually enabledor disabled the terminal. ListTERMDEV from CI MAP level for listof terminals.


User: JANET on MAP. Manually ENABLE: DIALUP



SECU115The Security (SECU) subsystem generates SECU115. The subsystemgenerates SECU115 when the user exceeds the maximum login time thatLOGINCONTROL command specifies. The system disables the terminal.






User took too long to LOGIN on: <term>. opttxt


VariableDescription

INFO Constant Variable Indicates the system disables theenabled terminal that waits for login.

User took too long toLOGIN on

Symbolic text Variable Indicates the user exceeded themaximum login time during loginattempt. List TERMDEV from CI MAPlevel for list of terminals.

opttxt Console disabled Variable Indicates the system disables theenabled terminal that waits for login.

Blank Variable Indicates the system does not disablethe enabled terminal that waits forlogin.


User took too long to LOGIN on: DIALUP. Console wasdisabled.



SECU116The Security (SECU) subsystem generates SECU116. The systemgenerates SECU116 when the user exceeds the maximum number ofinvalid login attempts that the LOGINCONTROL command specifies. Thesystem disables the console.



SECU116 67



Too many invalid LOGINs on: <term>. opttxt


VariableDescription


Too many invalidLOGINs on

Symbolic text Variable Indicates the user made themaximum number of invalid loginattempts. List TERMDEV from CIMAP level for list of terminals.

opttxt Console disabled Variable Indicates the system disabled theenabled terminal that waits for login.

opttxt Blank Variable Indicates the system disabled theenabled terminal that waits for login.


Too many invalid LOGINs on: DIALUP. Console was disabled.



SECU117The Security (SECU) subsystem generates SECU117 when the systemenables a terminal as the LOGINCONTROL command specifies.




Console: <term> has been automatically enabled.



reastxt


VariableDescription


Console:<term>hasbeen automaticallyenabled.

Symbolic text Variable Indicates the system enabled theterminal. List TERMDEV from CIMAP level for list of terminals.

reastxt End of disable time Variable Indicates the system enabled theterminal when disable time wasexceeded.

To prevent systemlockout

Variable Indicates the system enables aterminal to prevent being placed onthe lockout list. The disable timespecified by the LOGINCONTROLcommand normally equals thedefault, FOREVER.


Console: DIALUP has been automatically enabled.

End of disable time.



SECU118The Security (SECU) subsystem generates SECU118 when a user is idlefor a long period of time. The system also generates SECU118 when thesystem detects an open line condition. The system logs the user off theterminal. The terminal security profile defined in Table TERMDEV andTable LOGINCONTROL determines if the system can disconnect theterminal.


SECU118 69




reastxt: <user> on <term> forced out by system.

opttxt


VariableDescription


reastxt Idle User Variable Indicates user logs on specifiedterminal does not press the Enter keyduring the timeout period set for theterminal.

Line open Variable Indicates that the system detects aline open condition.

<user> Symbolic text Variable Identifies idle user which the systemlogs out. Use CI commandSHOWUSERS for a list of usersdefined to the system.

on<term>forced outby system.

Symbolic text Variable Identifies terminal, that the systemcan disconnected. The system logsan idle user off of that terminal. ListTERMDEV from CI MAP level for listof terminals.

opttxt Console wasdisabled

Variable Indicates system logs idle user offterminal. Indicates system disablesspecified terminal.

Blank Variable Indicates system logs idle user offterminal. Indicates system does notdisconnects terminal.

Active message exampleFP503 SEP05 18:14:33 4827 INFO Device State Change

Location: FP 2 DEVICE 1 (DK) SCSI BUS 0

REASON: Change of state of associated entity

FROM: InSv (Isolated) DRIVE STATE: Unknown



TO: InSv DRIVE STATE: On Line



SECU119The Security (SECU) subsystem generates SECU119 when the systemdisables a terminal after the user logs out. The subsystem also generatesSECU119 when the terminal is busied out.




reastxt. Console: <term> disabled.


VariableDescription


reastxt Console BSY Variable Indicates console is busied out.User logout Variable Indicates user logs out of system.

Console:<term>disabled

Symbolic text Variable Indicates the system automaticallydisables the terminal when the userlogs out. List TERMDEV from CIMAP level for list of terminals.


User logout. Console: DIALUP disabled.


SECU119 71



SECU120The Security (SECU) subsystem generates SECU120 when a userattempts to log on a dialup terminal with an invalid identification orpassword.




<term>. DIALBACK login failed with id <id>

Reason: reastxt


VariableDescription


<term> Symbolic text Variable Identifies terminal on which the userattempts to login. List TERMDEVfrom CI MAP level for list ofterminals.

DIALBACK loginfailed with id

Bad user Variable Indicates the user uses invalid useridentification to log on the terminal(reastxt = Invalid dialback id).

Symbolic text Variable Provides correct identification foruser attempt to log on the terminal.List DIALBACK from CI MAP level forlist of users. See Customer dataTable DIALBACK.

Blank Variable Indicates LOGIN timeout occurs.Reason Bad return code Variable Indicates user attempts to log on the

terminal and a system error occurs.Incorrect dialbackpassword

Variable Indicates user attempts to log on theterminal with an invalid password.




Description

Invalid dialback id Variable Indicates user attempts to log on theterminal with an invalid dialbackidentifier.

LOGIN timeout Variable Indicates user attempt to log on theterminal, and fails to complete loginprocedures in the specified time.


DIALUP. Dialback login failed with id DBID123

Reason: Incorrect dialback password.



SECU121The Security (SECU) subsystem generates SECU121 when a valid userlogs on a dialup terminal. The user uses normal login procedures to log onthe terminal.



Format1.SECU121 mmmdd hh:mm:ss ssdd INFO

<term>. Dialback login with id <id>

SECU121 73



VariableDescription


<term> Symbolic text Variable Identifies terminal the user logs on.List TERMDEV from CI MAP level forlist of terminals.

Dialback login with id Symbolic text Variable Identifies user that logs on specifiedterminal. List DIALBACK from CIMAP level for list of users. Seecustomer data Table DIALBACK.

Active message example1.SECU121 APR01 12:00:00 2112 INFO

DIALUP. Dialback login with id DNID123



SECU122The Security (SECU) subsystem generates SECU122 when an attempt tolog on a dialup terminal fails.




<term>. DIALBACK call failed.

Dialback id: <id>. Number: <dn>

Reason: reastxt




VariableDescription


<term> Symbolic text Variable Identifies terminal on which user triedto log into. Refer to customer dataTable TERMDEV from CI MAP levelfor list of terminals.

DIALBACK call failed Constant Variable Indicates attempt to perform dialbackfailed.

Dialback id Symbolic text Variable Identifies user which attempteddialback. List DIALBACK from CIMAP level for list of users. Refer tocustomer data Table DIALBACK.

Number Integers Variable Provides directory number forterminal that the user cannot access.The user cannot access the terminalwhen dialback does not complete.Refer to Table I.

Reason Bad file systemrequest

Variable Indicates file system receives acommand that the system cannotexecute.

Bad return code Variable Indicates system received an errorcode that the system cannotunderstand.

Call aborted bysystem

Variable Indicates system aborts the dialbackcall. For example, the modemequipment is not available for use.

Call connected Variable Indicates modem dials out.Could not initiatelogin

Variable Indicates system cannot completelogin sequence. For example, the filesystem fails to output data throughthe modem.

Error in file system Variable Indicates error occurs in file system.For example, a corrupted filereference number.

Invalid directorynumber

Variable Indicates dialback directory numberthat is not correct.

Line was busy Variable Indicates modem discovers the linewas busy when the modem makesthe dialback call.

Modem unstable Variable Indicates modem does not workcorrectly.

SECU122 75



Description

No answer Variable Indicates modem is not available, orthe called party can not answer whenthe modem placed the dialback call.

No modem availablefor dialback

Variable Indicates modem is not available tomake dialback call.

Unable to detectcarrier

Variable Indicates modem is not able to detectcarrier.

Unable to detectdialtone

Variable Indicates modem is not able to detectdial tone.


DIALUP. DIALBACK call failed.

Dialback id: DBID123. Number: 7811999

Reason: Modem unstable.



SECU123The Security (SECU) subsystem generates SECU123. The subsystemgenerates SECU123 when attempts to log on a dialup terminal succeed,dialback call is successful, and login is complete.




<term>. DIALBACK call connected.

Dialback id: <id>. Number: <dn>



New <term>


VariableDescription


<term> Symbolic text Variable Identifies first terminal where userattempts to logon. See customer dataTable TERMDEV from CI MAP levelfor list of terminals.

DIALBACK callconnected

Constant Variable Indicates attempt to perform dialbackis successful.

Dialback id Symbolic text Variable Identifies user attempted dialbacks.List DIALBACK from CI MAP level forlist of users. See customer dataTable DIALBACK.

Number Symbolic text Variable Provides directory number forterminal to complete dialback call.

New Symbolic text Variable Identifies terminal used in dialbackconnection. List Table TERMDEVfrom CI MAP level.


DIALUP. DIALBACK call connected.

Dialback id: DBID123. Number: 7811999

New DIALUP1



SECU124The Security (SECU) subsystem generates log report SECU124 when auser changes the dialback password for a user.


SECU124 77




User: <user> on <term>. DIALBACK password changed for id<id>.


VariableDescription


User Symbolic text Variable Identifies user that changes dial-uppassword. Use CI commandSHOWUSERS for a list of usersdefined to the system.

on Symbolic text Variable Identifies terminal where user makesthe change to the dial-up password.List customer data table TERMDEVfrom CI MAP level for list ofterminals.

DIALBACKpassword changedfor id

Symbolic text Variable Identifies user for which the userchanges dialback password. ListDIALBACK from CI MAP level for alist of users. See customer data tableDIALBACK.


User:JANET on DIALUP. DIALBACK password changed for id

DBID123.



SECU125The Security (SECU) subsystem generates log report SECU125 when auser enables dialback for a dial-up terminal.






User: <user> on <term>. DIALBACK enabled for <term>.


VariableDescription


User Symbolic text Variable Identifies user that enables dial-upterminal. Use CI commandSHOWUSERS for a list of usersdefined to the system.

on Symbolic text Variable Identifies terminal on which the userenables the dial-up terminal. Listcustomer data table TERMDEV fromCI MAP level for list of terminals.

DIALBACK enabledfor

Symbolic text Variable Identifies dial-up terminal that theuser enables. See customer datatable TERMDEV.


User: JANET on DIALUP. DIALBACK enabled for DBID123.



SECU126The Security (SECU) subsystem generates log report SECU126 when auser disables dialback for a dial-up terminal.


SECU126 79




User: <user> on <term>. DIALBACK disabled for <term>.


VariableDescription


User Symbolic text Variable Identifies user that disables the dial-up terminal. Use CI commandSHOWUSERS for a list of usersdefined to the system.

on Symbolic text Variable Identifies terminal on which the userdisables the dial-up terminal. Listcustomer data table TERMDEV fromCI MAP level for list if terminals.

DIALBACK disabledfor

Symbolic text Variable Identifies dial-up terminal that theuser disables. See customer datatable TERMDEV.


User: JANET on DIALUP. DIALBACK disabled for DBID123.



SIM600The Residential Enhanced Services Simultaneous Ringing featuregenerates the SIM600 log report when a failure occurs during SimRingpilot directory number (PDN) -to-non-pilot member directory number(NPMDN) call setup. The following failures can occur:

• The NPMDN routes to a non-supported agent.

• The NPMDN fails translations.



The SIM600 log tracks down the cause of an error.

During a call to the PDN of a SimRing group, the RES SimultaneousRinging feature establishes calls between the PDN and the NPMDNs. TheRES Simultaneous Ringing feature generates logs if it encounters a failurein the call between the PDN and the NPMDNs.

Remedial actionNo immediate action. This log report is an information-type log.

When log reason is "Non-supported agent" then the cause is a PDF-to-NPMDN call routing to an unsupported agent. To resolve, verify theNPMDNs of the SimRing group associated with the PDN. The outgoingtrunk can be different from one call to the next call.

When the log reason is "Translation failure" then the cause is a translationfailure between the PDFN and a particular NPMDN. To resolve, verify theNPMDNs of the SimRing group of the PDN.


FormatMTLEN08AP SIM600 mmmdd hh:mm:ss ssdd INFO SIMRING

Call ID: 2 x 4 digits

Pilot DN: 10 digits

Member DN: up to 30 digits

Reason: Reason of failure


VariableDescription

Call ID 2 x 4 digits Variable This field specifies the identificationnumber of the caller-to-PDN call.

Pilot DN 10 digits Variable This field specifies the DN that thesubscriber must call in order for theSimRing group to be alerted.

SIM600 81



Description

Member DN 4 to 30 Variable digits This field specifies the memberDN that the pilot tries to reach whenthe failure occurs.

Reason Non-supportedagent, Translationfailure

Variable This field specifies the problempreventing the call leg from beingestablished.

Active message exampleMTLEN08AP SIM600 MAI10 12:30:55 3800 INFO SIMRING

CallID: 6789 7654

Pilot DN: 6136211500

Member DN: 1234567

Reason: Translation Failure



SLE101The Screening List Editing (SLE) subsystem generates log report SLE101when table RESFEAT changes. The change occurs during call processing,while the journal file is not active. The table changes when the subscriberactivates or deactivates the screening list service. Table RESFEATdisplays the status of the tuple after the subscriber activates or deactivatesthe screening list service.

Remedial actionn/a


FormatSLE101 mmmdd hh:mm:ss ssdd INFO NO JOURNAL FILE

RESFEAT TABLE WAS UPDATED WHILE JOURNAL FILE WAS

INACTIVE.



NEW TUPLE IS:

resfeat tuple


VariableDescription

INFO NO JOURNALFILE

Constant Variable Indicates that a table changes whilethe journal file is not active.

NEW TUPLE IS Symbolic text Variable Indicates the new tuple. Refer totable RESFEAT for all the values.

Active message exampleSLE101 JAN01 09:01:38 1234 INFO NO JOURNAL FILE

RESFEAT TABLE WAS UPDATED WHILE JOURNAL FILE WAS

INACTIVE.

NEW TUPLE IS:

HOST 00 0 16 03 SCRJ SCRJ NOAMA ACT



SLE102The Screening List Editing (SLE) subsystem generates SLE102. Thesubsystem generates SLE102 when a tuple in Table SLELIST changeswhen the journal file is not active. This condition occurs when the useradds or deletes entries in screening lists or updates the privacy or voiceback information.

Remedial actionn/a


FormatSLE102 mmmdd hh:mm:ss ssdd INFO NO JOURNAL FILE

SLELIST TABLE WAS UPDATED WHILE JOURNAL FILE WAS

SLE102 83


INACTIVE.

TUPLE actxt IS:

slelist tuple


VariableDescription

INFO NO JOURNALFILE

Constant Variable Indicates a user updated a tablewhile the journal file was not active.

TUPLE IS: ADDED DELETEDCHANGED

Variable Indicates the action performed toupdate the table.

slelist tuple Symbolic text Variable Indicates the updated SLELIST tuple.Refer to Table SLELIST for all thevalues.

Active message exampleSLE102 JAN01 09:01:38 1234 INFO NO JOURNAL FILE

SLELIST TABLE WAS UPDATED WHILE JOURNAL FILE WAS

INACTIVE.

TUPLE ADDED IS:

HOST 00 0 17 04 SCRJ 4 Y 6136212341 PRIVATE 0 N



SLE103The Screening List Editing (SLE) subsystem generates log report SLE103when the compaction process begins.

Remedial actionn/a




FormatSLE103 mmmdd hh:mm:ss ssdd INFO SLE PROCESS STARTED

SLE COMPACTION PROCESS STARTED BECAUSE: rsntxt userid

THE NUMBER OF TRANSACTIONS WHICH HAVE OCCURRED

SINCE THE

PROCESS WAS LAST STARTED IS: count

THE CURRENT THRESHOLD IS: currentnum


VariableDescription

INFO SLEPROCESSSTARTED

Constant Variable Indicates the screening list editing(SLE) process begins.

rsntxt THRESHOLDEXCEEDED

Variable Indicates the process begins. Theprocess begins because the numberof SLE transactions exceeds thenumber that the SLE TRANSACTIONTHRESHOLD office parameterspecifies.

CI REQUEST Variable Indicates the process beginsbecause the user uses the SLEPACKcommand to make the request.

WAKEUP_RECEIVED

Variable Indicates the process beginsautomatically at the time that the SLEWAKEUP TIME office parameterspecifies.

userid Variable Identifies the originator of therequest. The log report displaysuserid when the rsntxt field indicatesCI REQUEST.

count 0-32k Variable Indicates the number of transactionsthat occur from the time of the lastcompaction process.

currentnum 0-32k Variable Indicates the current value of theTable SLE TRANSACTIONTHRESHOLD.

Active message exampleSLE103 JAN01 09:01:38 1234 INFO SLE PROCESS STARTED

SLE COMPACTION PROCESS STARTED BECAUSE: WAKEUP_RECEIVED

SLE103 85


THE NUMBER OF TRANSACTIONS WHICH HAVE OCCURRED SINCE

THE PROCESS WAS LAST STARTED IS: 824

THE CURRENT THRESHOLD IS: 1024



SLE104The Screening List Editing (SLE) subsystem generates log report SLE104when the compaction process is complete. This report provides informationon the data store that the screening lists allocate and use.

Remedial actionAction is required under the following conditions:

The value of the max_count field can be larger than the number ofsegments allocated. This value indicates that a cold or reload restart hasnot occurred from the time the office parameter was last set. The max_field count can be larger when the system has enough data store toaccommodate the current volume of SLE data. If SLE data does not haveenough data store, perform a cold or reload restart. A cold or reload restartmakes additional data store available for SLE data.

If the number of segments used is less than the number of segmentsallocated, the system has enough data store. If the number of segments isthe same, survey the logs for SWERs. If the logs indicate failure to obtainstore for SLE data, activate the office parameter immediately.


FormatSLE104 mmmdd hh:mm:ss ssdd INFO SLE PROCESS COMPLETED

SLE COMPACTION PROCESS HAS COMPLETED.

NUMBER OF SEGMENTS RECOVERED IS: rec seg rec words

VALUE OF PARM SLE_MAX_SEGMENT_COUNT IS: max_ count

NUMBER OF SEGMENTS ALLOCATED IS: allocated



NUMBER OF SEGMENTS USED IS: used

NUMBER OF ITEMS PER SEGMENT IS: segment size


VariableDescription

INFO SLEPROCESSCOMPLETED

Constant Variable Indicates the SLE compactionprocess is complete.

SLE COMPACTIONPROCESS HASCOMPLETED

Constant Variable Indicates the SLE compactionprocess is complete.

NUMBER OFSEGMENTSRECOVERED IS

0-2048 segments Variable Indicates the number of segmentsreleased during the compactionprocess. This field is a data store thatother applications can release anduse. Other applications use this datastore when the system overuses thescreening list editing facility.

3x (0-2048) words Variable Indicates the number of wordsreleased during the compactionprocess. This field is a data store thatother applications can release anduse. Other applications use this datastore when the system overuses thescreening list editing facility.

VALUE OF PARMSLE_MAX_SEGMENT_COUNT IS

0-2048 Variable Indicates the current value of the SLEMAX SEGMENT COUNT officeparameter. The current value is themaximum number of segmentsallocated for use by SLE data.

NUMBER OFSEGMENTSALLOCATED IS

0-2048 Variable Indicates the number of segmentsallocated for use by SLE data. Thisvalue must correspond to theprevious value.

NUMBER OFSEGMENTS USEDIS

0-2048 Variable Indicates the number of segmentsused by SLE data. This field is astore consumption indicator.

NUMBER OF ITEMSPER SEGMENT IS

1024-8192 Variable Indicates the size of segments thatSLE data use.

Active message exampleSLE104 JAN01 09:01:38 1234 INFO SLE_PROCESS_COMPLETED

SLE COMPACTION PROCESS HAS COMPLETED.

SLE104 87


NUMBER OF SEGMENTS RECOVERED IS: 1 segment 3072 words

VALUE OF PARM SLE_MAX_SEGMENT_COUNT IS: 5

NUMBER OF SEGMENTS ALLOCATED IS: 5

NUMBER OF SEGMENTS USED IS: 4

NUMBER OF ITEMS PER SEGMENT IS: 1024



SLE105The Screening List Editing (SLE) subsystem generates log report SLE105when the RESFEAT process encounters a problem.

Remedial actionIf the error text field indicates NO RESFEAT MAILBOX, restart theprocess. If the problem occurs again, contact the next level ofmaintenance.

If the error text field indicates BAD RESFEAT MSGTYPE, there is noaction required. If the subsystem generates a large number of SLE105logs, contact the next level of maintenance.


FormatSLE105 mmmdd hh:mm:ss ssdd INFO RESFEAT PROCESS TROUBLE

RESFEAT TROUBLE ENCOUNTERED. ERROR IS:

errortxt




VariableDescription

INFO RESFEATPROCESSTROUBLE

Constant Variable Indicates that the RESFEAT processencounters trouble

ERROR IS NO RESFEATMAILBOX

Variable Indicates that the system cannotallocate a mailbox for the RESFEATprocess

BAD RESFEATMSGTYPE

Variable Indicates that the RESFEAT mailboxreceives a message that is notexpected.

Active message exampleSLE104 JAN01 09:01:38 1234 INFO RESFEAT PROCESS TROUBLE

RESFEAT TROUBLE ENCOUNTERED. ERROR IS:

NO RESFEAT MAILBOX.



SLE106The Screening List Editing (SLE) subsystem generates log report SLE106when the central SLE process encounters a problem.

Remedial actionMatch the error code in the log to the following list:

• DATA STORE NOT ALLOCATED -- Set the office parameter SLE MAXSEGMENT COUNT. If the parameter is set, perform a restart. Thisresponse indicates the system cannot allocate the data store for SLEdata.

• NO DATA STORE -- Contact the next level of maintenance. Thisresponse Indicates the data store is not available for SLE data.

• UNABLE TO SET WAKEUP -- Perform a restart. If the problempersists, contact the next level of maintenance. This response indicatesthe system cannot generate the next wake-up for the compactionprocess.

• NO SLE MAILBOX -- Perform a restart. If the problem persists, contactthe next level of maintenance. This response indicates the systemcannot allocate a mailbox for the central process.

SLE106 89


• BAD MAILBOX ID -- Perform a restart. If the problem persists, contactthe next level of maintenance. This response indicates an invalidmailbox is present.

• NOT SLE MSGTYPE -- Perform a restart. If the problem persists,contact the next level of maintenance. This response indicates that theSLE process receives a message that is not expected.

• UNABLE TO START COMPACTION -- Perform a restart. If theproblem persists, contact the next level of maintenance. This responseindicates the central process cannot start the compaction process.

• NO RESPONSE -- Perform a restart. If the problem persists, contactthe next level of maintenance. This response indicates response wasnot received when a message transmitted between processes.


FormatSLE106 mmmdd hh:mm:ss ssdd INFO SLE PROCESS TROUBLE

SLE TROUBLE ENCOUNTERED. ERROR IS:

errortxt


VariableDescription

INFO SLEPROCESSTROUBLE

Constant Variable Indicates that the SLE processencounters trouble

ERROR IS Symbolic text Variable Identifies the problem that the SLEprocess encounters. Refer to thetable at the end of this log report.

Active message exampleSLE104 JAN01 09:01:38 1234 INFO SLE PROCESS TROUBLE

SLE TROUBLE ENCOUNTERED. ERROR IS:

NO SLE MAILBOX.





SLE107The Screening Line Editing (SLE) subsystem generates log report SLE107when the SLE audit finds a discrepancy in the data. The SLE audit is partof the compaction process.

Remedial actionn/a


FormatSLE107 mmmdd hh:mm:ss ssdd INFO SLE AUDIT

ERROR FOUND DURING SLE AUDIT. ERROR IS:

errortxt


VariableDescription

INFO SLE AUDIT Constant Variable Indicates that the SLE audit finds adiscrepancy in the data.

errortxt Symbolic text Variable Identifies the error that the auditfinds.

• ITEM MARKED FREE --Indicates an item with valid datamarked free in the SLE free map.

• ITEM MARKED INUSE --Indicates an item with invaliddata marked in use in the SLEfree map.

• COUNTS TOO LARGE --Indicates that the counts in theSLE admin data have moreentries in the list than data. Thesystem corrects the counts.

• COUNTS TOO SMALL --Indicates that the counts in theSLE admin data contain less

SLE107 91



Description

entries in list than data. Thesystem releases additionalentries.

• COUNTS UNBALANCED --Indicates that the total count inthe SLE admin data is correct,but the separate counts are notcorrect. The system calculatesthe counts again.

Active message exampleSLE107 JAN01 09:01:38 1234 INFO SLE AUDIT

ERROR FOUND DURING SLE AUDIT. ERROR IS:

ITEM MARKED FREE.



SLE108The Screening List Editing (SLE) subsystem generates log report SLE108.The subsystem generates this report when the SLE session count auditfinds a discrepancy in the internally stored session counts. The SLE auditis part of the compaction process. The subsystem compares the number ofSLE sessions that are active with the internally calculated counts. If thecounts differ, the system corrects the counts and generates this report.

Remedial actionn/a


FormatSLE108 mmmdd hh:mm:ss ssdd SLE SESSION COUNT ERROR

featname SLE SESSION COUNT DISCREPANCY

OLD COUNT = oldnum RESET TO NEW COUNT = newnum




VariableDescription

SLE SESSIONCOUNT ERROR

Constant Variable Indicates the SLE session count auditfinds a discrepancy in the internallystored counts.

featname SCRJ SCF SCADRCW

Variable Indicates the feature that detects theproblem.

OLD COUNT nn Variable Indicates the previous value in thecount.

RESET TO NEWCOUNT

nn Variable Indicates the corrected value in thecount.

Active message exampleSLE108 JAN01 09:01:38 1234 INFO SLE SESSION COUNT ER

SCRJ SLE SESSION COUNT DISCREPANCY

OLD COUNT = 23 RESET TO NEW COUNT = 16



SLM200The System Load Module (SLM) subsystem generates log report SLM200.The subsystem generates this report when the SLM controller hardwaredetects a major SLM command failure. The subsystem SLM node systemis set to busy (SysB). An audit attempts to return the SLM node to service.

When the problem that caused the SLM200 log is cleared, an SLM406 logreport appears.

Remedial actionPerform maintenance on the affected SLM.

AttributesAttribute ValueSeverity • Major

• Warning

Format**SLM200 mmmdd hh:mm:ss ssdd INFO Command Failure

SLM200 93


Cmd cmdtxt Unit n

Error Class : clastxt

Error Detail: detxt

hhhh hhhh hhhh hhhh hhhh hhhh

hhhh hhhh hhhh hhhh hhhh hhhh


VariableDescription

hhhh 0000-FFFF VariableError Detail Symbolic text Variable • RECEIVE FIFO PARITY ERROR

-- The system detects a parityerror while the system reads theoutgoing message body. Thetarget can execute the requestbefore this error returns.

• PROM ID RESPONSE TIMEOUT-- A read or write operation to theelement blocks on the paddleboard or the SLM board to fails.Failure is a result of a DTACKtimeout

• 12-VOLT POWER-UP TIMEOUT-- Boot BLP attempts to turn onthe 12-volt power converter. The12-volt power converter outputfails to reach the 12-volt levelafter 1 s. The subsystem mustreach the 12-volt level after amaximum of 0.15 s. The usermust use the ENHANCED BOOTcommand to return this errorcode.

• SCSI BUS NOT FREE --Indicates a selection attempt to atarget fails. The selection attemptfails because a target uses theSCSI bus.

• DEVICE NOT RESPONDING --Target does not respond to aselection attempt.




Description

• MULTIPLE ERRORS DURINGERROR RECOVERY -- Indicateserrors occur duringcommunication with a target toallow accurate analysis of theproblem.

• TARGET DROPPED SLM BSYLINE -- Target device drops theSCSI BSY line to the SLM for areason that is not known.

• TARGET IS BUSY -- Targetdevice processes a command.Another base-level processissued the command.

• INVALID DEVICE RETURNSTATUS -- Target device returnsan invalid status to the SLMwhen the device executes aSCSI command

• DATA BLOCK COUNTMISMATCH -- Indicates thetarget device does not return thenumber of blocks of data that theSLM requests. The user mustuse the ENHANCED BOOT andENHANCED BOOT CONTINUEcommands to return this errorcode. The subsystem includesthis error response fordevelopment purposes.

• NODE NUMBER INCORRECT --Indicates the node number on areceived message is not correct

• INVALID OPCODE -- Indicatesthe opcode on a message is notcorrect. Error Byte 3 contains theopcode.

• TRANSMITTED DATA LOST --Indicates the data that theingoing message returns are lost.The data loss is a result of atransmission that is notsuccessful. No copy of the dataremains in the SLM to allow thesubsystem to reload the transmit

SLM200 95



Description

buffer of the SLM. The user mustuse the MESSAGE LOOP BACKcommand to return the errorcondition.

• SUCCESSIVE TRANSMITFAILURES -- The remote end ofthe link does not acknowledge aningoing message (with data) thatBoot BLP attempts to send. BootBLP attempts to send thismessage repeatedly. Theseattempts exceed the messageretry threshold. Boot BLPterminates. The user must usethe ENHANCED BOOT orENHANCED BOOT CONTINUEcommand to return the errorcode.

• TARGET DATA LOSTTHROUGH SLM FAULTRECOVERY -- Indicates the datafor the target device are lost. Thedata loss is a result of mediafaults. The data loss requires theSLM to perform blockreassignment. The user must usethe SET ITOC and RESET ITOCcommands to return the errorcondition.

• BOOT FILE SENT -- Indicatesthe subsystem reaches the endof image file. Error Byte 3provides additional informationon ITOC updates. 0x00 indicatesthe ITOC default entry is OK,0x01 indicates the ITOC was notupdated. The user must use theENHANCED BOOT orENHANCED BOOT CONTINUEcommand to return these errorconditions.




Description

• UNEXPECTED OPCODE -- Theopcode on a received messagewas not planned. Error Byte 3contains the opcode.

• PROCESS ACTIVE -- The 5-voltlock command to remove the 5-volt interlock command issueswhile an SLM process is active.

NFO CommandFailure

Constant Variable Indicates that an SLM command fails

Cmd Symbolic name Variable Identifies the command that failsUnit 0, 1 Variable Identifies the SLM controller on which

the problem occursError Class Symbolic text Variable • SLM HW ERROR -- Indicates a

system load module hardwareerror

• SLM SCSI ERROR -- Indicates asystem load module SCSI error

• SLM LINK ERROR -- Indicates asystem load module link error

Active message example**SLM200 APR01 12:00:00 2112 INFO Command Failure

Cmd D READ BLKS Unit 0

Error Class : SLM SCSI ERROR

Error Detail : Device Not Responding

8102 0000 0000 0000 0000 0000

0000 0000 0000 0000 0000 0000


SLM200 97



SLM208The System Load Module (SLM) subsystem generates log report SLM208.The subsystem generates this report when the subsystem receives anSLM product engineering code (PEC) that is not correct. This reportindicates that the SLM unit does not have correct rmw are.

Remedial actionContact the next level of maintenance.


Format**SLM208 mmmdd hh:mm:ss ssdd INFO SLM PEC unknown

Unit n


VariableDescription

INFO SLM PECunknown

Constant Variable Indicates the subsystem receives anSLM PEC that is not correct.

Unit 0-1 Variable Identifies the SLM controller on whichthe problem occurs.

Active message example**SLM208 APR01 12:00:00 2011 INFO SLM PEC unknown

Unit 0



SLM400The System Load Module (SLM) subsystem generates log report SLM400.The subsystem generates this report when an SLM resource managementschema (RMS) request is delayed. This SLM RMS must not connect withthe current execution of requests.



The subsystem generates this log report one time every hour while arequest over flow occurs.

Remedial actionIf request delays occur because of not enough SLM user processes,contact the next level of maintenance.


FormatSLM400 mmmdd hh:mm:ss ssdd INFO RMS REQUEST OVERFLOW

SLMn

rsntxt

n REQUESTS DELAYED.


VariableDescription

INFO RMSREQUESTOVERFLOW

Constant Variable Indicates a report of SLM resourcemanagement schema requestoverflow.

SLM 0, 1 Variable Identifies the affected SLM.rsntxt INSUFFICIENT

NUMBER OF SLMWORKERPROCESSES

Variable Indicates that more persons musthandle the volume of resourcerequests.

SLM WORKERPROCESSES HADNOT YETINITIALIZEDFOLLOWINGRESTART

Variable Indicates users do not startprocesses after a restart. This fielddoes not indicate an error condition.

n REQUESTSDELAYED

1-9 Variable Indicates the number of RMSrequests that are in delay.

Active message exampleSLM400 NOV11 15:43:21 2112 INFO RMS REQUEST OVERFLOW SLM1

INSUFFICIENT NUMBER OF RMS WORKER PROCESSES.

5 REQUESTS DELAYED.

SLM400 99




SLM401The System Load Module (SLM) subsystem generates log report SLM401when an SLM is set to offline (OFFL) from the indicated state.

Remedial actionRefer to the SLM MAP (maintenance and administration position) displayfor additional information and commands to test the SLM.


FormatSLM401 mmmdd hh:mm:ss ssdd OFFL SLM STATUS CHANGE PMCn

SLMn

BY MANUAL ACTION, SET FROM statxt


VariableDescription

OFFL SLM STATUSCHANGE

Constant Variable Indicates an SLM changes status

PMC 0, 1 Variable Identifies the affected peripheral side(P-side) message controller

SLM 0, 1 Variable Identifies the affected SLMBY MANUALACTION

Constant Variable Indicates that manual action set SLMto OffL

SET FROM ManB Variable Indicates that the previous state ofthe SLM was: manual busy (ManB)

UNEQ Variable Indicates that the previous state ofthe SLM was: unequipped (UNEQ)

Active message exampleSLM401 JAN03 23:07:12 2112 OFFL SLM STATUS CHANGE PMC0

SLM1



BY MANUAL ACTION, SET FROM ManB.



SLM402The System Load Module (SLM) subsystem generates this report when aSLM is set to manual busy (ManB) from the specified state.

Remedial actionn/a


Format*SLM402 mmmdd hh:mm:ss ssdd MANB SLM STATUS CHANGE

PMCn SLMn

BY actxt ACTION, SET FROM statxt


VariableDescription

MANB SLM STATUSCHANGE

Constant Variable Indicates a report of SLM statuschange.

PMCn 0-1 Variable Identifies the p-side messagecontroller affected.

SLMn 0-1 Variable Identifies the SLM affected.actxt manual Variable Indicates manual action caused the

SLM status change.statxt OK Variable Indicates the previous status of the

SLM was OK.ISTB Variable Indicates the previous status of the

SLM was in-service trouble.SysB Variable Indicates the previous status of the

SLM was system busy.OFFL Variable Indicates the previous status of the

SLM was off-line.

SLM402 101


Active message example*SLM402 JAN02 08:45:30 2112 MANB SLM STATUS CHANGE PMCO

SLM1

BY manual ACTION, SET FROM Ok.



SLM403The System Load Module (SLM) subsystem generates log report SLM403when an SLM is set to system busy (SysB) from the specified state.



Format**SLM403 mmmdd hh:mm:ss ssdd SYSB SLM STATUS CHANGE PMCn

SLMn

BY SYSTEM ACTION, SET FROM statxt


VariableDescription

SYSB SLM STATUSCHANGE


PMC 0, 1 Variable Identifies the affected peripheral side(P-side) message controller.

SLM 0, 1 Variable Identifies the affected SLM.Constant Variable Indicates that system action causes

the SLM status change.BY SYSTEMACTION, SET FROM

OK Variable Indicates that the previous status ofthe SLM was correct.




Description

ISTb Variable Indicates that the previous status ofthe SLM was inservice trouble.

CBsy Variable Indicates that the previous status ofthe SLM was central side busy(CBsy).

Active message example**SLM403 JAN02 08:45:30 2112 SYSB SLM STATUS CHANGE PMCO

SLM1

BY SYSTEM ACTION, SET FROM OK.



SLM404The System Load Module (SLM) subsystem generates log report SLM404.The subsystem generates this report when a SLM is set to inservicetrouble (ISTb) from the specified state.



Format*SLM404 mmmdd hh:mm:ss ssdd TBL SLM STATUS CHANGE PMCn

SLMn

BY SYSTEM ACTION, ISTb FROM statxt

SLM404 103



VariableDescription

TBL SLM STATUSCHANGE

Constant Variable Indicates a report of SLM statuschange

PMC 0,1 Variable Identifies the affected peripheral side(P-side) message controller

SLM 0,1 Variable Identifies the affected SLMBY SYSTEMACTION

Constant Variable Indicates that system action causesthe SLM status change

ISTb FROM SysB Variable Indicates that the previous status ofthe SLM was system busy

OK Variable Indicates that the previous status ofthe SLM was correct

CBsy Variable Indicates that the previous status ofthe SLM was central side busy(CBsy)

Active message example*SLM404 JAN02 08:45:30 2112 TBL SLM STATUS CHANGE PMC0 SLM1

BY SYSTEM ACTION, ISTb FROM ManB.



SLM405The System Load Module (SLM) subsystem generates log report SLM405when a SLM is set to central side busy (CBsy) from the specified state.

Remedial actionn/a


Format*SLM405 mmmdd hh:mm:ss ssdd CBSY SLM STATUS CHANGE

PMCn SLMn





VariableDescription

CBSY SLM STATUSCHANGE


PMCn 0-1 Variable Identifies the affected P-sidemessage controller.

SLMn 0-1 Variable Identifies the affected SLM.actxt manual Variable Indicates that manual action causes

the SLM status change.system Variable Indicates that system action causes

the SLM status change.statxt OK Variable Indicates that the previous status of

the SLM was correct.ISTB Variable Indicates that the previous status of

the SLM was in-service trouble.SysB Variable Indicates that the previous status of

the SLM was system busy.

Active message example*SLM405 JAN02 08:45:30 2112 CBSY SLM STATUS CHANGE PMCO

SLM1

BY manual ACTION, SET FROM Ok.



SLM406The System Load Module (SLM) subsystem generates log report SLM406.The subsystem generates this report when an SLM returns to service fromthe specified state.

Remedial actionn/a


SLM406 105


FormatSLM406 mmmdd hh:mm:ss ssdd RTS SLM STATUS CHANGE PMCn

SLMn



VariableDescription

PMCn 0,1 Variable Identifies the affected P-sidemessage controller.

SLMn 0,1 Variable Identifies the affected SLM.actxt manual Variable Indicates that manual action causes

the SLM status change.system Variable Indicates that system action causes

the SLM status change.statxt ManB Variable Indicates that the previous status of

the SLM was manual busy.SysB Variable Indicates that the previous status of

the SLM was system busy.RTS SLM STATUSCHANGE


Active message exampleSLM406 JAN02 08:45:30 2112 RTS SLM STATUS CHANGE PMC0 SLM1

BY manual ACTION, SET FROM Manb.



SLM407The System Load Module (SLM) subsystem generates log report SLM407.The subsystem generates this report when a user uses the NOWAIToption to perform a manual test on the specified SLM. Firmwarecommands can fail. The user issues these commands to the SLMcontroller. If a command fails, the system generates an SLM200 log report.This report specifies the failure reason. The SLM200 log report precedesthe SLM407 log report.



Examples of test results follow:

• Minimum test passes

• Minimum test fails

• Disk loopback test passes

• Disk loopback test fails

• Disk and tape tests passes

• Disk and tape tests fails

• Tape loopback test passes

• Tape loopback test fails

• In-service test passes

• In-service test fails

Remedial actionn/a


FormatSLM407 mmmdd hh:mm:ss ssdd INFO SLM TEST RESULT PMCn

SLMn

BY MANUAL ACTION, restxt.


VariableDescription

INFO SLM TESTRESULT

Constant Variable Indicates a report of a system loadmodule test result.

PMC 0, 1 Variable Identifies the affected P-sidemessage controller.

SLM 0, 1 Variable Identifies the system load modulethat the user tests.

BY MANUALACTION

Constant Variable Indicates that manual action initiatesthe test.

restxt Symbolic text Variable Indicates the results of the test. Referto the "Additional information" at theend of this log description.

SLM407 107


Active message exampleSLM407 DEC9 08:45:30 393 INFO SLM TEST RESULT PMC0 SLM0

BY MANUAL ACTION, Minimum test passed.



SLM408The System Load Module (SLM) subsystem generates log report SLM408.The system generates this log report to report software errors from theSLM maintenance code. The subsystem generates this log for severaldifferent reasons.

Examples of test results areas follows:

• SLM DEVICE DRIVER DEAD - PMC REX

• MANUAL BUSY FAILED - DEVICE DRIVER IS DEAD

• IO AUDIT RTS REQUEST TIMED-OUT

• MANUAL RTS FAILED - DEVICE DRIVER IS DEAD

• MANUAL TEST FAILED - DEVICE DRIVER IS DEAD

• MANUAL OFFLINE FAILED - DEVICE DRIVER IS DEAD

• SLM DISK AUDIT FAILED - DEVICE DRIVER IS DEAD

• SLM F/W READ/CLEAR FAILED - DEVICE DRIVER IS DEAD

• SPIN FAILED - DEVICE DRIVER IS DEAD

Remedial actionn/a


FormatSLM408 mmmdd hh:mm:ss ssdd INFO SLM MAINTENANCE LOG

SLMn

rsntxt




VariableDescription

INFO SLMMAINTENANCELOG

Constant Variable Indicates a report from SLMmaintenance code.

SLM 0,1 Variable Identifies the affected SLM.rsntxt Symbolic text Variable Provides the reason that the

subsystem generates this log. Referto table Reasons at the end of thislog report.

Active message exampleSLM408 NOV11 5:43:21 4565 INFO SLM MAINTENANCE LOG SLM1

MANUAL RTS FAILED - DEVICE DRIVER IS DEAD.



SLM409The System Load Module (SLM) subsystem generates log report SLM409.This report appears when manual action sets the specified SLMunequipped from an offline state.

Remedial actionn/a


FormatSLM409 mmmdd hh:mm:ss ssdd UNEQ SLM STATUS CHANGE

PMCn SLMn

BY manual ACTION, SET FROM offline.

SLM409 109



VariableDescription

UNEQ SLM STATUSCHANGE

Constant Variable Indicates a SLM changed status.

PMCn 0, 1 Variable Identifies the affected P-sidemessage controller.

SLMn 0, 1 Variable Identifies the affected SLM.BY manual ACTION Constant Variable Indicates manual action set the SLM

unequipped.SET FROM offline Constant Variable Indicates the SLM was previously

offline.

Active message exampleSLM409 JA3 23:07:12 392 UNEQ SLM STATUS CHANGE PMC0 SLM1

BY manual ACTION, SET FROM offline.



SLM410The System Load Module (SLM) subsystem generates log report SLM410on completion of the SLM daily audit. This log indicates if the audit passedor failed. If the log indicates failure, the SLM cannot boot correctly.

Test results (restxt):

• All tests passed

• Microprocessor test failed

• PROM checksum test failed

• RAM test failed

• MPU exception vectors test failed

• Sanity timer test failed

• Control/Status register test failed

• Transmit FIFO test failed

• Receive FIFO test failed

• SCSI controller test failed

• Disk write test failed



• Disk read test failed

• Test aborted because SLM out of service

• Test aborted because SLM loading mate CPU

Remedial actionIf the daily audit failed, manually busy (ManB) the affected SLM. Set theunit offline (OffL) and replace the SLM.


FormatSLM410 mmmdd hh:mm:ss ssdd INFO SLM DAILY AUDIT PMCn

SLMn

BY SYSTEM ACTION, restxt.


VariableDescription

INFO SLM DAILYAUDIT

Constant Variable Indicates a report of SLM daily auditresults

PMC 0, 1 Variable Identifies the peripheral side (P-side)message controller involved

SLM 0,1 Variable Identifies the SLM that system actionaudited

BY SYSTEMACTION

Constant Variable Indicates that system action initiatedthe audit.

restxt Descriptive text Variable Provides the results of the audit.Refer to audit results at the end ofthis log report.

Active message exampleSLM410 DEC19 08:45:30 2112 INFO SLM DAILY TEST PMC0 SLM0

BY SYSTEM ACTION, all tests passed.


SLM410 111



SLNK100The SL-100 Link (SLNK) subsystem generates log report SLNK100. Thisreport appears when system establishes a session on a datalink. Use theDEVCON command in the LNKUTIL CI interface to establish the sessionon a datalink.

Remedial actionn/a


FormatSLNK100 mmmdd hh:mm:ss ssdd INFO SESSION

Session connected on device devnm


VariableDescription

INFO SESSION Constant Variable Represents INFO SESSION forSL-100 link

devnm Symbolic text Variable Indicates device name entered inTable TERMDEV.

Active message exampleSLNK100 APR22 06:29:56 1819 INFO SESSION

Session connected on device MRLINK



SLNK101The SL-100 Link (SLNK) subsystem generates log report SLNK101. Thisreport appears when the system terminates a session on the datalink. Usethe DEVDISC command in the LNKUTIL CI interface to terminate asession on the datalink.



Remedial actionThere is no action required if operating company personnel at the MAPterminal terminate the session.

Software terminates the session if manual action does not occur. Softwareerror reports (SWER), TRAPs, and/or LOGs accompany SLNK101 andindicate the error that occurred.



Session disconnected on device devnm


VariableDescription

INFO SESSION Constant Variable Indicates information sessionSessiondisconnected ondevice

Symbolic text Variable Indicates device name entered inTable Termdev


session disconnected on device MRLINK



SLNK102The SL-100 Link (SLNK) subsystem generates log report SLNK102 foreach datalink device. This report occurs when the system starts datatransfer. Use the DEVSTART command to start data transfer. The reportalso appears for each datalink in the pool when the system starts datatransfer. Use the POOLSTART command in the LNKUTIL CI to start datatransfer.

Remedial actionn/a

SLNK102 113




report_type Reports transfer started on devnm


VariableDescription

INFO SESSION Constant Variable Indicates information sessionreport_type ACD Variable Indicates the report is an automatic

call distribution (ACD) reportACDRTD Variable Indicates the report is an automatic

call distribution real time display(ACDRTD) report.

SMDI Variable Indicates the report is a simplifiedmessage desk interface (SMDI)report

SMDR Variable Indicates the report is a stationmessage detail recording (SMDR)report

devnm Symbolic text Variable Indicates device name in TableTERMDEV

Active message exampleSLNK102 JUN12 01:45:56 1181 INFO SESSION

SMDR Reports transfer started on device MRLINK



SLNK103The SL-100 (SLNK) subsystem generates log report SLNK103 for eachdata link device. This report appears when the system stops data transfer.Use the DEVSTOP command to stop data transfer. This report alsoappears for each data link when the system stops data transfer. Use thePOOLSTOP command in the LNKUTIL CI increase to stop data transfer.



Remedial actionThere is no action required if operating company personnel at the MAPterminate the transfer. Software terminates the transfer if manual action didnot occur. The SWERs, TRAPs, and/or LOGs that can accompany thisreport provide information about what happened.


Format1.SLNK103 mmmdd hh:mm:ss ssdd INFO SESSION

report_type Reports transfer stopped on device devnm


VariableDescription

INFO SESSION Constant Variable Indicates information sessionreport_type ACD Variable Indicates the report is an automatic

call distribution (ACD) reportACDRTD Variable Indicates the report is an automatic

call distribution real time display(ACDRTD) report

SMDI Variable Indicates the report is a simplifiedmessage desk interface (SMDI)report

SMDR Variable Indicates the report is a stationmessage detail recording (SMDR)report

devnm Symbolic text Variable Indicates device name entered inTable TERMDEV

Active message example1.SLNK103 JUN12 02:03:47 1999 INFO SESSION

SMDR Reports transfer stopped on device MRLINK


SLNK103 115



SLNK104The SL-100 Link (SLNK) subsystem generates log report SLNK104. Thisreport appears when the system starts down stream processor initializationon a pool. Use the INIT command in ACDMR CI interface to start downstream processor initialization on a pool.

Remedial actionn/a


Format1.SLNK104 mmmdd hh:mm:ss ssdd INFO MGTRPT

ACD Management Reports initialization started on poolnm


VariableDescription

poolnm Symbolic text Variable Indicates pool name.

Active message example1.SLNK104 APR22 06:45:22 1999 INFO MGTRTP

ACD Management Reports initialization started on pool

MRPOOL



SLNK105The SL-100 Link (SLNK) subsystem generates log report SLNK105. Thisreport appears when the system completes down stream processorinitialization on a pool.

Remedial actionn/a




FormatSLNK105 mmmdd hh:mm:ss ssdd INFO MGTRPT

ACD Management Reports initialization completed on poolpoolnm

Number of groups: nnnnn Number of positions: nnnnn


VariableDescription

poolnm Integers Variable Indicates pool nameNumber of groups 1-32,767 Variable Indicates the ACD group for which

the system generates the logNumber of positions 1-32,767 Variable Indicates number of positions in the

ACD group

Active message exampleSLNK105 APR22 06:45:22 1999 INFO MGTRPT

ACD Management Reports initialization completed on pool

MRPOOL

Number of groups: 92 Number of positions: 857



SLNK106The SL-100 Link (SLNK) subsystem generates log report SLNK106. Thisreport appears if the system failed to queue a remote operation (RO) in thelast 2 min. The system queues an RO for a data link device. The failureoccurs because of a full queue. As a result, the system discards newmessages or overwrites old messages.

SLNK106 117


Remedial actionThe subsystem generates log report SLNK106 when the message volumeon a data link device exceeds the transmission capacity of the device. Thedata links run at maximum capacity. As a result, the only action required isto reduce the message volume of the data links.

To reduce message volume, perform either of the following actions:

• assign additional devices to the pool to provide load-sharing

• reroute some of the message traffic assigned to the pool that overflows



Last occurrence = date time day

Total number of overflow msgs = nnn


VariableDescription

INFO SESSION Constant Variable Indicates a session errorLast occurrence Character string Variable Displays the date and time of the

week of the last overflowTotal number ofoverflow msgs

Integers Variable Indicates the number of messagesthat overflowed the queue


Last occurrence = 1976/01/02 02:19:20.940 SAT

Total number of overflow msgs = 46





SLNK107The SL-100 Link (SLNK) subsystem generates log report SLNK107. Thisreport appears if the SL-100 link wakeup (SLLNKWKP) does not restart a1X67 datalink after restart or link failure.

The SMDI Re-Engineering feature (59010576) converts this log into acritical log. Three asterisks appear in the log report. The SLLNKERR alarmgenerates at the same time as the SLNK107 log.

Remedial actionManual intervention requires the following three steps. The first step is todetermine if the data link is in service. If the data link is not in service,return the link to service. The second step is to determine if the link is in aconnected state. If the link is not in a connected state, return the link to aconnected state. The third step is to determine if the system starts theappropriate transfer types on the link. If the system did not start theappropriate transfer types on the link, start the transfer types.


• Critical

Format***SLNK107 mmmdd hh:mm:ss ssdd INFO SESSION

Device devnm has failed to restart.

It requires manual intervention.


VariableDescription

INFO SESSION Constant Variable Indicates a failure to restart the datalink after a restart or link failure

Device devnm hasfailed to restart

Symbolic text Variable Indicates device name entered in theSLLNKDEV table

It requires manualintervention

Constant Variable Indicates manual interventionnecessary

Active message example***SLNK107 JUN12 01:45:56 1181 INFO LINK_WAKEUP_FAILURE

SLNK107 119


Device SMDI5 has failed to restart.

It requires manual intervention.



SLNK108The DMS-100 switch generates the SLNK108 log when the simplifiedmessage desk interface (SMDI) incoming or outgoing process stops. Theprocesses that follow refer to SMDI:

• SMDIOG is the outgoing process for the 1x67 device.

• SMDINC is the incoming process for the 1x67 device.

• SMDINMPC is the incoming process for the 1x89 and Fx30 devices.

• SLMPCOGT is the outgoing process for the 1x89 and Fx30 devices.

• SLLNKOGT is the outgoing process for the SL-100 link.

• SLLNKICT is the incoming process for the SL-100 link.

Each process is for each link except the SMDINMPC process. There is oneSMDINMPC process for the DMS-100 switch. The SMDI103 log generateswhen the SMDINMPC process stops instead of the SLNK108 log.

The SMDI process stops because of hardware or software problems. TheSLNK108 log generates when the SMDI process stops because of thesoftware problems that follow:

• file status is not acceptable for the 1x67 device

• did not take resource for the 1x67, 1x89, Fx30, and the SLLNKOGT(SL-100)

• did not allocate pool for the 1x67

• did not allocate resource for the 1x67, 1x89, Fx30, and SLLNKOGT(SL-100)

• did not get the resource for the 1x67, SLLNKOGT, and SLLNKICT(SL-100)

• Nil SMDI descriptor for the 1x67

• did not setup the les for the 1x67

• incorrect message in the mailbox for the 1x67

• the mailbox is not acceptable for the 1x67, 1x89, and Fx30

• no entry in the data 11 for the SLLNK device for SMDI for the 1x67



• no allocation for the SMDI pool for the 1x67

• did not allocate the mailbox for the 1x67

• the SMDIOG process is not acceptable for the 1x67

• the SMDI link is not available for the data transfer for the 1x89 or Fx30

• did not receive the SLMPC wakeup message for the 1x89 or Fx30

The SLNK108 log generates when the SMDI process stops because of thehardware problems that follow:

• input output controller (IOC) port is in service for the 1x67

• driver is not up for the 1x67

• port is not up for the 1x67

• deletion of the link for the 1x67

• the SLLNK device data did not initialize for the 1x89 or Fx30

• the SMDI device is not part of the SLLNK pool for the 1x89 or Fx30

• did not release the resource for the 1x89 or Fx30

• did not send data out on the SLLNKOGT link for the SL-100

The SMDIERROR alarm for software problems and the SLNKERR alarmfor hardware problems generate with the SLNK108 log.

Remedial actionThe description of the action is in the log report field descriptions section.

AttributesAttribute ValueSeverity • Critical

• Major

• Warning

Format***SLNK108 mmmdd hh:mm:ss ssdd INFO SMDI_DEAD_PROCESS_REPORT

Reason: <Name of SMDI process? Process killed

DATALINK = linkname

**SLNK108 mmmdd hh:mm:ss ssdd INFO_SMDI_DEAD_PROCESS_REPORT

Reason: <Name of SMDI process> Process killed

SLNK108 121


DATALINK = linkname


VariableDescription

INFOSMDI_DEAD_PROCESS_REPORT

Constant Variable The field that indicates a SMDIprocess death. (SMDIINC, SMDIOG,SMDINMPC, SLLNKOGT, orSLLNKICT)

rpttxt File status not ok.(for 1x67 devices)

Variable The value indicates the incoming andoutgoing files for the 1x67 card denywrite option for outgoing messages(SMDIOG) and read option forincoming messages (SMDINC).

Action: Check for hardware problemsfor the link.

Failed to claimresource, (for 1x67,1x89, or Fx30,SLLNKOGT)

Variable The value indicates the DMS-100switch did not demand resources forthe equivalent SMDI process.

Action: Check the office engineerparameters and increase theappropriate number of officeparameters.

Failed to allocatepool. (1x67)

Variable The value indicates the DMS-100switch did not allocate pool resourcesfor the equivalent SMDI process.


Failed to getresource. (1x67,SLLNKOGT, orSLLNKICT)

Variable The value indicates the DMS-100switch did not get the resources forthe equivalent SMDI process.


Nil SMDI descriptor.(1x67)

Variable The value indicates the SMDIdescriptor is nil.

Action: Check the entries for theSMDI device in the SLLNKDEV table.

rpttxt Failed to setup files.(1x67)

Variable The value indicates that SMDI did notset up files for the incoming andoutgoing processes.




Description

Action: Does not require specificaction.

Incorrect message inmailbox. (1x67)

Variable The value indicates the incorrectmessages between the SMDIINCand the SMDIOG process.


Mailbox not ok.(1x67, 1x89, orFx30)

Variable The value indicates the messages inthe mailbox are not in the correctformat. Action: Does not requirespecific action.

SLLNK device notdatafilled for SMDI.(1x67)

Variable The value indicates an entry for theSMDI device is not in the SLLNKDEVtable for SMDI.

Action: Check the SLLNKDEV tablefor the SMDIDATA transfer option forthe SLLNK device.

SMDI pool has notbeen allocated.(1x67)

Variable The value indicates the DMS-100switch did not allocate pool resourcesfor the equivalent SMDI process.


Failed to allocatemailbox. (1x67)

Variable The value indicates the DMS-100switch did not allocate a mailbox forthe equivalent SMDI process.


SMDIOG processnot ok. (1x67)

Variable The value indicates the SMDIOGprocess is not acceptable.


SMDI link notavailable for datatransfer. (1x89 orFx30)

Variable The value indicates the SLLNKdevice is not available for datatransfer.

Action: Check for link status.SLMPC wakeupmessage notreceived. (1x89 orFx30)

Variable The value indicates the SLMPCautomatic wakeup message did notreceive for the SMDI link.

SLNK108 123



Description

Action: Check the link status.IOC port not inservice. (1x67)

Variable The value indicates the IOC port isnot in service for the equivalent link.

Action: Restore the IOC port toservice.

Driver is not up.(1x67)

Variable The value indicates the driver is notin service for the link.

Action: Restore the driver to service.Port is not up. (1x67) Variable The value indicates the port is not in

service for the link.

Action: Restore the port to service.Link was deleted.(1x67)

Variable The value indicates the deletion ofthe SLLNK device from theSLLNKDEV table.

Action:Add the SLLNK device in thetable SLLNKDEV.

SLLNK deviceuninitialized. (1x89 orFx30)

Variable The value indicates the SLLNKdevice did not initialize.

Action: Initialize the SLLNK device.SMDI device is notpart of the SLLNKpool. (1x89 or Fx30)

Variable The value indicates an entry for theSLLNK device is not in theSLLNKDEV table for the SMDI datatransfer.

Action: Add the SLLNK device to theSLLNKDEV table for the SMDI datatransfer.

Failed to release theresource. (1x89 orFx30)

Variable The value indicates the resource didnot release for the 1x89 or the Fx30.Action: Does not require specificaction.

Failed to send dataout on the link(SLLNKOGT)

Variable The value indicates the data did nottransfer over the link.

Action: Check the link status.Failed to allocateresource. (1x67,1x89, Fx30, andSLLNKOGT[SL-100])

Variable The value indicates the SL-100switch did not allocate pool resourcesfor the equivalent SMDI process.




Description


DATALINK Symbol text Variable The value indicates the name of theSMDI datalink for incoming andoutgoing messages.

Active message example***SLNK108 DEC 05 18:14:33 4827 SMDI_DEAD_PROCESS_REPORT

Port is not up.SMDIINC process killed.

DATALINK = SMDIO

**SLNK108 DEC 05 18:15:34 4828 SMDI_DEAD_PROCESS_REPORT

Incorrect message in mailbox.SMDIOG process killed.

DATALINK = SMDIO



SMDI100The system generates log report SMDI100. This report appears when theswitch encounters an error in the simplified message desk interface (SMDI)message waiting indication (MWI). The error report text indicates thereason for the error. If any information required for a field is in valid ormissing, the field is empty.

Remedial actionn/a


FormatSMDI100 mmmdd hh:ss ssdd INFO SMDI_ERR_REPORT

REQUESTEE STATION MISSING MWT OPTION

SMDI100 125


DATALINK = linkname

REQUESTEE INFO = len DN dn

SUBSCRIBER DN = nnnnnnnnnnn


VariableDescription

INFOSMDI_ERR_REPORT

Constant Variable Indicates an error in the SMDImessage waiting indicator (MWI).

DATALINK Symbol text Variable Identifies the datalink name assignedin the UCDGRP table for incomingand outgoing messages.

REQUESTEE INFO Symbol text Variable Identifies the requestee LEN and DN.This field does not identify the LENand DN, if the message desk sendsan invalid DN. This field supportsvariable length DN format up to 10digits.

Active message exampleSMDI100 NOV08 15:26:53 3122 INFO SMDI_ERR_REPORT

REQUESTEE STATION MISSING MWT OPTION

DATALINK = SMDILK0

REQUESTEE INFO = $ LEN HOST 2 0 0 13 DN 9097227640



SMDI101The Simplified Message Desk Interface (SMDI) subsystem generates logreport SMD101.

This report appears when the following conditions occur:

• the system places the first call to a VMS voice link

• the SMDI application cannot send the SMDI message that corresponds



Remedial actionIf the link is on an NT1X89 card, BSY and RTS the link. If the failurecontinues, contact the next level of maintenance support.


FormatSMDI101 mmmdd hh:mm:ss nnnn INFO SMDI_ERR_REPORT

DATALINK IS DOWN. FAILED TO SEND SMDI MESSAGE.

DATALINK = link_name


VariableDescription

INFOSMID_ERR_REPORT DATALINK ISDOWN. FAILED TOSEND SMDIMESSAGE.

Constant Variable Indicates the SMDI applicationcannot send the SMDI message thatcorresponds to a VMS voice link call

Datalink 0000-FFFF Variable Indicates the name of the failed linkas entered in table SLNKDEV

Active message exampleSMDI101 JAN25 01:45:56 1181 INFO SMDI_ERR_REPORT

DATALINK IS DOWN. FAILED TO SEND SMDI MESSAGE

DATALINK = VMSLINK1



SMDI102The Simplified Message Desk Interface (SMDI) subsystem generatesSMDI102 for each data link. After SMDI101 condition clears, the rst timean SMDI message queues, the system generates SMDI102.

SMDI102 127


Remedial actionMonitor the link to make sure that the link has stability.


FormatSMDI102 mmmdd hh:mm:ss nnnn INFO SMDI_LINK_REPORT

DATALINK IS UP. DATALINK = link_name.


VariableDescription

INFOSMDI_LINK_REPORT

Constant Variable Indicates system a SMDI messagequeues after an SMDM 01 conditionclears.

DATALINK IS UP. Constant Variable Indicates the data link is operating.DATALINK 0000-FFFF Variable Indicates the name of the returned to

service link as entered in TableSLNKDEV.

Active message exampleSMDI102 JAN25 01:45:56 1181 INFO SMDI_LINK_REPORT

DATALINK IS UP. DATALINK = VMSLINK1.



SMDI103The system generates this log when the SMDINMPC (simplified messagedesk interface incoming process) terminates.

The SMDI Re-Engineering feature (59010576) converts the SMDI103 loginto a major log. Two asterisks appear in the log report. The SMDIERRORalarm generates with this log.

Remedial actionThis log requires manual intervention. First, go to the MTC;IOD level of themap. Post the appropriate IOC number and card (the IOC and cardnumbers are located in the MPC table and the LISTDEV CONS



command). Next, perform the OFFLINE ALL, BSY ALL, and RTS ALLcommands. Perform the REVIVE ALL command to restore the processSMDINMPC. An alarm (SMDIERR) also generates with this log. The alarmresets automatically when the SMDINMPC or SLMPCOGT process starts.


• Major

Format**SMDI103 mmmdd hh:mm:ss ssdd INFO SMDI INCOMING PROCESS

SMDINMPC process died. Requires manual intervention.


VariableDescription

INFO SMDIINCOMINGPROCESS

Constant Variable This field indicates the SMDINMPCprocess has died.

SMDINMPC Constant Variable This field indicates that the systemrequires manual intervention.

Active message example**SMDI103 MAR26 20:59:44 7500 INFO SMDI INCOMING PROCESS

SMDINMPC process died. Requires manual intervention.



SMDI104This information-only log indicates that the switch failed to locate a primarydesk for a host requestee line. The switch uses a rotational message desk.Log SMDI104 creates no operating impact.

Remedial actionn/a

SMDI104 129



FormatSMDI104 mmmdd hh:mm:ss ssdd INFO SMDI_ERR_REPORT

Rotational desk used. No primary desk for DN.

DATALINK = linkname

REQUESTEE INFO = LEN len DN dn

SUBSCRIBER DN = nnnnnnnnnnn


VariableDescription

INFOSMDI_ERR_REPORT

Constant Variable This field indicates an error in thesimplified message desk interface(SMDI) message waiting indicator(MWI).

DATALINK Symbol text Variable This field identifies the SMDI datalinkfor incoming and outgoing messages.

REQUESTEE INFO Symbol text Variable This field identifies the line equipmentnumber (LEN) and directory number(DN) for local requestees. The DNfield supports variable length DNformat up to 10 digits.

Active message exampleSMDI104 NOV08 15:26:53 3122 INFO SMDI_DESK_ERR_REPORT

Rotational Desk used. NO primary desk for DN.

DATALINK = VMAIL1

REQUESTEE INFO = $ LEN HOST 2 0 0 13 DN 7224444





SMDI105The system generates SMDI105 when the switch fails to locate a commonmessage desk for network message waiting indicator (MWI) request(setting or removal). The rst message desk entered helps set MWI.

Remedial actionTelephone operating customer personnel must define a common messagedesk. Telephone operating customer personnel configure the link to definea common message desk. Telephone operate desk 63 or entry optionCOMMON in table SLLNKDEV [Link Device Table].


FormatSMDI105 mmmdd hh:mm:ss ssdd INFO SMDI_NETWORK_ERR_

REPORT

rpttxt

UCD GROUP INFO = ucdgrpno DATALINK = linkname


VariableDescription

1NFoSMDI_NETWORK_ERR_REPORT

Constant Variable Indicates an error in the SMDI MWI.

rpttxt Failed to determine aCommon Desk forNetwork MWIRequest.

Variable Indicates the switch fails to locate acommon message desk for an MWIrequest with the incoming message.

ucdgrpno 0 to 63 Variable Indicates the rotational desk number.linkname Link from table

SLLNKDEVVariable Indicates the SMDI datalink for

incoming and outgoing messages.

Active message exampleSMDI105 SEP05 18:14:33 3122 INFO SMDI_NETWORK_ERR_ REPORT

Failed to determine a Common Desk for Network MWI

SMDI105 131


Request.

UCD GROUP INFO = VM1GRP DATALINK = VMAIL1



SMDI106The system generates SMDI106 when the switch fails to locate themessage desk number associated with option COMMON of tableSLLNKDEV (Link Device Table).

Remedial actionTelephone operating company personnel must define the message desknumber to associate with option COMMON in table SLLNKDEV.Telephone operating company personnel must delete the option if thesystem does not need this option. Table UCDGROUP (Uniform CallDistribution) defines the message desk number for UCD member. TableHUNTGRP (Hunt Group) defines the message desk number for HUNTmembers.


FormatSMDI106 mmmdd hh:mm:ss ssdd INFO SMDI_COMMON_ERR_

REPORT

rpttxt

UCD GROUP INFO = ucdgrpno DATALINK = linkname


VariableDescription

INFOSMDI_COMMON_ERR_REPORT

Constant Variable Indicates an error in the SMDI MWI.

rpttxt DESKNUM messagedesk of COMMONoption is not present.

Variable Indicates that the switch fails tolocate the message desk numberassociated with option COMMON intable SLLNKDEV.




Description

ucdgrpno 0 to 63 Variable Indicates the rotational desk number.linkname Link from table

SLLNKDEVVariable Indicates the SMDI datalink for

incoming and outgoing messages.

Active message exampleSMDI106 SEP05 18:14:33 3122 INFO SMDI_COMMON_ERR_REPORT

DESKNUM message desk of COMMON option does not exist.

UCD GROUP INFO = VM1GRP DATALINK = VMAIL1



SMDI107The SMDI107 log generates when the les of a 1x67 card do not allow thewrite option for outgoing messages and the read option for incomingmessages.

Remedial actionn/a


FormatSMDI107 mmmdd hh:mm:ss ssdd SMDI_FILE_STATUS

FILE STATUS NOT O.K.

DATALINK_INDEX = linkname

SMDI107 133



VariableDescription

INFO SMDI_FILESTATUS FILESTATUS NOT O.K.

Constant Variable The value indicates the files for the1x67 card do not allow the writeoperation for outgoing messages orthe read operation for incomingmessages.

DATALINK Symbol text Variable The value is the name of the SMDIdatalink for incoming and outgoingmessages.

Active message exampleSMDI107 DEC05 18:14:33 4827 INFO SMDI_FILE_STATUS

FILE STATUS NOT O.K.

DATALINK_INDEX = VMAIL1



SMDI108The SMDI108 log generates when the IOC (input output controller) port isnot in service.

The SLLNKERR alarm for hardware problems generates with the SMDI108log.

Remedial actionAn alarm generates for the SMDI108 log and requires manual intervention.


• Warning

Format***SMDI108 mmmdd hh:mm:ss ssdd INFO SMDI_HW_AUDIT

IOC PORT NOT IN SERVICE FOR LINK.

DATALINK_INDEX = linkname




VariableDescription

INFOSMDI_HW_AUDITIOC PORT NOT INSERVICE FORLINK.

Constant Variable The value indicates the IOC port isnot in service.

DATALINK Symbol text Variable The value is the name of the SMDIdatalink for incoming and outgoingmessages.

Active message example***SMDI108 DEC05 18:14:33 4827 INFO SMDI_HW_AUDIT

IOC PORT NOT IN SERVICE FOR LINK.

DATALINK_INDEX = VMAIL1



SME100The Signaling Management Environment (SME) subsystem generatesSME100. The subsystem generates SME100 when an attempt to allocatedata store required for num_sme_control_blocks parameter in tableOFCENG fails.

Remedial actionCheck for SME logs that accompany this log report. Contact the next levelof maintenance to increase data store memory.


FormatSME100 mmmdd hh:mm:ss dddd FLT ALLOC CONTROL BLKS

Failed to allocate nn blocks as datafilled.

Reason = reasontxt

SME100 135



VariableDescription

FLT ALLOCCONTROL BLKS

Constant Variable Indicates an attempt to allocatecontrol blocks fornum_sme_control_blocks parameterin table OFCENG occurred.

Failed to allocate nnblocks as data filled.

Integers Variable Indicates failure of an attempt toallocate requested number of controlblocks.

Reason Text Variable Indicates the reason for the failure.

Active message exampleSME100 JAN01 21:24:49 1220 FLT ALLOC CONTROL BLKS

Failed to allocate 3 blocks as datafilled.

Reason = STOREUNAVAIL.



SME101The Signaling Management Environment (SME) subsystem generatesSME101. The subsystem generates SME101 when an attempt to allocatedata store required for num_sme_data_blocks parameter contained in tableOFCENG fails.



FormatSME101 mmmdd hh:mm:ss dddd FLT ALLOC DATA BLKS

Failed to allocate nn blocks as datafilled.

Reason = reasontxt




VariableDescription

FLT ALLOC DATABLKS

Constant Variable Indicates an attempt to allocate datablocks for num_sme_data_blocksparameter in table OFCENG.

Failed to allocate nnblocks as datafilled

Integers Variable Indicates failure of attempt to allocaterequested number of blocks.

Reason Text Variable Indicates reason for the failure.

Active message exampleSME101 JAN01 21:24:49 1532 FLT ALLOC DATA BLKS

Failed to allocate 10 blocks as datafilled.




SME102The Signaling Management Environment (SME) subsystem generatesSME102 when the following attempts fail:

• an attempt to allocate data store that num_sme_control_blocksparameter contained in table OFCENG requires

• an attempt to allocate the previous number of SME control blocks

Before restart, the number of SME control blocks is more than 0, and lessthan the current value in table OFCENG.



FormatSME102 mmmdd hh:mm:ss dddd FLT ALLOC CONTROL BLKS

Failed to allocate nn blocks as prior to the restart.

SME102 137


Reason = reasontxt


VariableDescription

FLT ALLOCCONTROL BLKS

Constant Variable Indicates that an attempt to allocatecontrol blocks fornum_sme_control_blocks parameterin table OFCENG occurred.

Failed to allocate nnblocks as prior to therestart.

Integers Variable Indicates failure of an attempt toallocate the same number of controlblocks allocated before the restart.

Reason Text Variable Indicates reason for failure.

Active message exampleSME102 JAN01 21:24:49 1532 FLT ALLOC CONTROL BLKS

Failed to allocate 10 blocks as prior to the restart.

Reason = STOREUNAVAIL



SME103The Signaling Management Environment (SME) subsystem generatesSME103. The subsystem generates SME103 when an attempt to allocatedata store required for the num_sme_data_blocks parameter contained intable OFCENG fails. An attempt to allocate the previous number of SMEdata blocks also fails. Before restart, the number of SME data blocks ismore than 0 and less than the current value in table OFCENG.

Remedial actionCheck for SME logs that accompany this report. Contact the next level ofmaintenance to increase data store memory.


FormatSME103 mmmdd hh:mm:ss dddd FLT ALLOC DATA BLKS



Failed to allocate nn blocks as prior to the restart.

Reason = reasontxt


VariableDescription

FLT ALLOC DATABLKS

Constant Variable Indicates that an attempt to allocatedata blocks for num_sme_data_-blocks parameter in table OFCENGoccurred.

Failed to allocate nnblocks as prior torestart.

Integers Variable Indicates the failure of an attempt toallocate the same number of blocksallocated before a restart.

Reason Text Variable Indicates reason for failure.

Active message exampleSME103 JAN01 21:24:49 1532 FLT ALLOC DATA BLKS

Failed to allocate 30 blocks as prior to the restart.




SME104The Signaling Management Environment (SME) subsystem generates logreport SME104. The subsystem generates this report when an attempt toallocate data store that num_sme_control_blocks parameter contained inTable OFCENG requires failed. An attempt to allocate the previous numberof SME control blocks passes.

Before restart, the number of SME control blocks was more than 0, andless than the current value in Table OFCENG.

Remedial actionn/a


SME104 139


FormatSME104 mmmdd hh:mm:ss ssdd INFO CONTROL BLKS

Successfully allocated nn blocks as prior to the restart.


VariableDescription

INFO CONTROLBLOCKS

Constant Variable Indicates that an attempt to allocatecontrol blocks fornum_sme_control_blocks parameterin Table OFCENG occurred.

Correctly allocatednn blocks as prior torestart.

Integers Variable Indicates a completed attempt toallocate the same number of controlblocks that were allocated before therestart.

Active message exampleSME104 JAN01 21:24:49 1532 INFO ALLOC CONTROL BLKS

Successfully allocated 30 blocks as prior to the

restart.



SME105The Signaling Management Environment (SME) subsystem generates logreport SME105. The system generates this report when an attempt toallocate data store that num_sme_data_blocks parameter contained inTable OFCENG requires failed. An attempt to allocate the previous numberof SME data blocks succeeded. Before restart, the number of SME datablocks is less than O, and more than the current value in Table OFCENG.

Remedial actionn/a




FormatSME105 mmmdd hh:mm:ss ssdd INFO DATA BLKS

Successfully allocated nn blocks as prior to the restart.


VariableDescription

INFO DATA BLKS Constant Variable Indicates that an attempt to allocatedata blocks for"num_sme_data_blocks" parameterin Table OFCENG occurred.

Correctly allocatednn blocks as prior tothe restart

Integers Variable Indicates a complete attempt toallocate the same number of datablocks allocated before restart.

Active message exampleSME105 JAN01 21:24:49 1532 INFO ALLOC DATA BLKS

Successfully allocated 30 blocks as prior to the

restart.



SME106The Signaling Management Environment (SME) subsystem generates logreport SME106. The subsystem generates this report when an attempt toaccess a new SME control block is not successful.

Remedial actionIncrease the "num_of_sme_control_blocks" parameter in table OFCENG.


FormatSME106 mmmdd hh:mm:ss dddd FLT CONTROL BLKS

No block available for call processing on callid.

SME106 141


Signaling information lost.


VariableDescription

FLT CONTROLBLKS

Constant Variable Indicates that an attempt to get anSME control block that was not usedoccurred.

Blocks not availablefor call processing on

Constant Variable Indicates that blocks were notavailable for call processing.

Callid. Integers Variable Identifies the call.Signaling informationlost.

Constant Variable Indicates the loss of signalinginformation

Active message exampleSME106 JAN01 21:27:36 8771 FLT CONTROL BLKS

No block available for call processing on 72.




SME107The Signaling Management Environment (SME) subsystem generates logreport SME107. The subsystem generates this report when an attempt toaccess a new SME data block fails.

Remedial actionIncrease the "num_of_sme_data_blocks" parameter in table OFCENG.


FormatSME107 mmmdd hh:mm:ss dddd FLT DATA BLKS

No block available for call processing on callid.





VariableDescription

FLT DATA BLKS Constant Variable Indicates that an attempt to get annew SME data block occurred.

Blocks not availablefor call processing on

Constant Variable Indicates that blocks were notavailable for call processing.

Callid. Integers Variable Identifies the call.Signaling informationlost.

Constant Variable Indicates the loss of signalinginformation

Active message exampleSME107 JAN01 21:30:03 3014 FLT DATA BLKS

No block available for call processing on 32833.




SME108The Signaling Management Environment (SME) subsystem generates logreport SME108. The subsystem generates this report when the followingactions occur:

• a call attached to a SME control block is being cleaned up

• the SME control block is being dumped

Remedial actionRecord the error and generate a customer service report (CSR).


FormatSME108 mmmdd hh:mm:ss dddd INFO CONTROL BLOCK DUMP

Block at address hhhhhh reasontxt

Contents of block:

SME108 143



VariableDescription

INFO CONTROLBLOCK DUMP

Constant Variable Indicates that SME control blockdump occurs.

Blocks at address 0000-FFFF Variable Indicates control block address.reasontxt Text Variable Indicates reason for block dump.Contents of block Symbolic text Variable Indicates contents of the control

block.

Active message exampleSME108 JAN01 21:52:22 5979 INFO CONTROL BLOCK DUMP

Block at address A85F47 freed due to call cleanup.

Contents of block:

CONTROL_LINK= FFFFFF DATA_LINK= A85FBF

PORT_CHAIN= FFFFFF CALLID= 163904

NODE: Tid (1) NN:56 TN:183 Agent:HOST 01 0 00 00

DN 9097225001 SME_INDEX=BRAFunc (1)

IN_USE=Y AUDIT=N NUM_SMEDBS=1



SME109The Signaling Management Environment (SME) subsystem generates logreport SME109. The system generates this report when a call attached to aSME data block is cleaned up and the SME data block is dumped.

Remedial actionRecord the error condition and generate a customer service report (CSR).




FormatSME109 mmmdd hh:mm:ss dddd INFO DATA BLOCK DUMP

Block at address hhhhhh reasontxt

Contents of block:


VariableDescription

INFO DATA BLOCKDUMP

Constant Variable Indicates a dump of the contents of adata block occurred.

Blocks at address 0000-FFFF Variable Indicates location of data block.reasontxt Text Variable Indicates reason for the data block

dump.Contents of block Symbolic text Variable Provides a complete list of contents

of the dump.

Active message exampleSME109 JAN01 21:52:22 6080 INFO DATA BLOCK DUMP

Block at address A85FBF freed due to call cleanup.

Contents of block:

NEXTSMEDB= FFFFFF IN_USE=Y AUDIT=N

FEATURE=Basic_call (1) EVENT=Term_ind (4)

Data area: Refinement No 3

Orig_Pty: Agent: HOST 01 0 00 01 DN 9097225002

Custgrp: COMKODAK STATE: Talking

Side: Orig Name: Public DN: Public

Cannot_Rls: N Cannot_Hold: N I

Msg_Dest_Pty_Num: Term_Pty

Term_Pty: Agent: HOST 01 0 00 00 DN 9097225001

Custgrp: COMKODAK STATE: On_Hook

Side: Term Name: Public DN: Public

SME109 145



Prev_Conn_Pty: Agent: <NIL>Custgrp: POTSDATA

STATE: Talking Side: Neither

Name: Public DN: Public


BRA Functional Terminate Indication Refinement:

Valid_Sourceparms=Y Intragroup=Y

Bearer_Capability=1



SME110The Signaling Management Environment (SME) subsystem generates logreport SME110. The system generates this report when the SME auditprocess frees at least one SME control block.

Remedial actionn/a


FormatSME110 mmmdd hh:mm:ss ssdd INFO SME AUDIT

Number of control blks freed by Phase n of audit: blks


VariableDescription

INFO SME AUDIT Constant Variable Indicates that the SME audit processran.

Phase n Variable Identifies the phase of the audit.blks n Variable Indicates the number of blocks that

the audit freed.



Active message exampleSME110 JAN01 21:07:59 6656 INFO SME AUDIT

Number of control blks freed by Phase 2 of audit : 1.



SME111The Signaling Management Environment (SME) subsystem generates logreport SME111. The subsystem generates this report when the SME auditprocess frees at least one SME data block.

Remedial actionn/a


FormatSME111 mmmdd hh:mm:ss ssdd INFO SME AUDIT

Number of data blks freed by Phase n of audit: blks


VariableDescription

INFO SME AUDIT Constant Variable Indicates that a SME audit processran.

Phase n Variable Identifies the phase of the audit.blks n Variable Indicates the number of blocks that

the audit freed.

Active message exampleSME111 JAN01 21:08:00 6666 INFO SME AUDIT

Number of data blks freed by Phase 3 of audit : 2.


SME111 147



SNAC100 Format 1The Service Analysis Center (SNAC) subsystem generates this reportwhen an operator at a Traffic Operator Position System (TOPS) position orat an overseas operator center (OOC) keys in a trouble code. This troublecode corresponds to a trouble condition. The trouble condition can eitherbe reported by a customer to an operator or detected by an operator duringcall processing.

An operating company (OC) can define up to 100 trouble codes in tableTOPSTRBL. When an operator at either the TOPS or OOC receives ordetects a trouble condition, the operator enters a one- or two-digit troublecode. The trouble code corresponds to the trouble condition. The SNACsubsystem only generates this report for trouble conditions that are notrelated to maintenance.

The following fields are added in TOPS11:

• APU node number

• VPU node number


• alternate route indication

• called party name

• calling party name

• memo text

Remedial actionA cross-reference of the trouble code in SNAC100 to the TRBLCODE fieldof table TOPSTRBL provides important information. Operating companypersonnel can use this information to determine the trouble condition andto take actions to correct the problem. If the correct action is not apparent,the operating company personnel should forward the trouble condition tothe next level of maintenance.


FormatSNAC100 mmmdd hh:mm:ss ssdd TBL n1 n2 n3

INCOMING TRK = <trkid>



OUTGOING TRK = <trkid>

CLGNO = <dn> <clg party name>

CLDNO = <dn> <cld party name>

OPR VOICE = <agentid>

CF3P = <agentid>

ALT RTE = <route code>

MEMO = <memo text>


VariableDescription

TRBL Variable This field indicates that this log has atrouble condition.

n1 0-99 Variable This field indicates that there is atrouble condition. Reference theTRBLCODE field of TableTOPSTRBL.

n2 000-999 Variable This field displays the loginidentification of the operator thatreported the trouble condition.

n3 000-999 Variable This field displays the positionnumber of the operator who reportedthe trouble condition.

INCOMING TRK symbolic text Variable This field displays the equipmentidentification for the originating trunkequipment.

OUTGOING TRK symbolic text Variable This field displays the equipmentidentification for the terminating trunkequipment.

CLGNO integers Variable This field displays the calling numberof the customer who reported thetrouble.

CLGNAME alphanumeric Variable This field displays the calling partyname on which the trouble conditionwas detected. If no name isassociated with the calling number,this field is blank.

CLDNO integers Variable This field displays the called numberdialed by the customer or operator onwhich the trouble is detected.

SNAC100 Format 1 149



Description

CLDNAME alphanumeric Variable This field displays the called partyname on which the trouble conditionwas detected. If no name isassociated with the called number,this field is blank.

CF3P integers Variable This field displays the 3-portconference circuit that is in use whenthe trouble occurred.

OPR VOICE symbolic text Variable This field displays the individualoperator voice link (can be a TOPSoperator centralization voice link) inuse.

ALT RTE alphanumeric Variable This field provides the operator withthe ability to perform alternate routingfor international calls when aconnection cannot be made by wayof a direct route. This event canoccur if no direct route exists or if thedirect route is connected.

MEMO alphanumeric Variable This field displays additionalinformation that the operatordescribes to further explain theservice problem.

APU integers Variable This field displays the APU nodenumber datafilled in table LIUINV.This field is filled for DA callsreceiving ADAS service. Use thenode number to post the peripheral atthe maintenance administrationposition (MAP).

VPU integers Variable This field displays the APU nodenumber datafilled in table LIUINV.This field is filled for DA callsreceiving ADAS service. Use thenode number to post the peripheral atthe MAP.

Active message exampleSNAC100 NOV08 15:45:14 2200 TBL 99 102 201

INCOMING TRK = CKT ITCARY0631IC 58

OUTGOING TRK = CKT ITCARY0541OG 45

CLGNO = 9909101 YASUDA SYUUHEI



CLDNO = F0109195155065 JANE DOE

CF3P = CKT CF3P 399

OPR VOICE = CKT TOPSPOS 201

ALT RTE =

MEMO = TRANSMISSION DIFFICULTY FOR CLD PARTY

APU = 5 VPU = 14



SNAC100 Format 3The Service Analysis Center (SNAC) subsystem generates this reportwhen an operator at a Traffic Operator Position System (TOPS) position orat an overseas operator center (OOC) keys in a trouble code. This troublecode corresponds to a trouble condition. The trouble condition can eitherbe reported by a customer to an operator or detected by an operator duringcall processing.

An operating company (OC) can define up to 100 trouble codes in tableTOPSTRBL. When an operator at either the TOPS or OOC receives ordetects a trouble condition, the operator enters a one- or two-digit troublecode. The trouble code corresponds to the trouble condition. The SNACsubsystem only generates this report for trouble conditions that are notrelated to maintenance.


• APU node number

• VPU node number





• memo text



Remedial actionA cross-reference of the trouble code in SNAC100 to the TRBLCODE fieldof table TOPSTRBL provides important information. Operating companypersonnel can use this information to determine the trouble condition andto take actions to correct the problem. If the correct action is not apparent,the operating company personnel should forward the trouble condition tothe next level of maintenance.





CLGNO = <dn>

CLDNO = <dn>


CF3P = <agentid>


VariableDescription


n3 000-999 Variable This field displays the positionnumber of the operator who reportedthe trouble condition.







Description





OPR VOICE symbolic text Variable This field displays the individualoperator voice link (can be a TOPSoperator centralization voice link) inuse.

ALT RTE alphanumeric Variable This field provides the operator withthe ability to perform alternate routingfor international calls when aconnection cannot be made by wayof a direct route. This event canoccur if no direct route exists or if thedirect route is connected.

MEMO alphanumeric Variable This field displays additionalinformation that the operatordescribes to further explain theservice problem.

APU integers Variable This field displays the APU nodenumber datafilled in table LIUINV.This field is filled for DA callsreceiving ADAS service. Use thenode number to post the peripheral atthe maintenance administrationposition (MAP).

TRBL Variable This field indicates that this log has atrouble condition.




Description


VPU integers Variable This field displays the APU nodenumber datafilled in table LIUINV.This field is filled for DA callsreceiving ADAS service. Use thenode number to post the peripheral atthe MAP.

Active message exampleSNAC100 APR01 12:00:00 2112 TBL 5 212 3

INCOMING TRK = CKT TERMBX01 1

OUTGOING TRK = CKT TERMBX03 1

CLGNO = 613-239_0123 850-1234

CLDNO = 850-1234

CF3P = CKT CF3P 6

OPR VOICE = CKT TOCVLIC4 1600



SNAC101The Service Analysis Center (SNAC) subsystem generates this reportwhen an operator at a Traffic Operator Position System (TOPS) position orat an overseas operator center (OOC) keys in a trouble code. This troublecode corresponds to a trouble condition, which is either reported to theoperator by a customer or detected by the operator during the course ofcall processing.

An operating company (OC) may define up to 100 trouble codes in TableTOPSTRBL. When an operator at either the TOPS or the OOC receives ordetects a trouble condition, the operator enters a one- or two-digit troublecode that corresponds to the trouble condition. The SNAC subsystem onlygenerates this report for maintenance-related trouble conditions enteredthat are not severe enough to generate an alarm.



In TOPS07, the following fields are added to SN AC101:




• memo text

Remedial actionBy mapping the trouble code in SNAC101 to the TRBLCODE field of tableTOPSTRBL, operating company personnel can determine the troublecondition and take appropriate action to correct the problem. If it is notapparent what the correct action should be, the trouble condition should beforwarded to the next level of maintenance.








CF3P = <agentid>


MEMO = <memo text>

SNAC101 mmmdd hh:mm:ss ssdd TBL n1 n2 n3



CLGNO = <dn>

CLDNO = <dn>

SNAC101 155



CF3P = <agentid>


VariableDescription


TRBL Variable This field indicates this log has atrouble condition.


n3 000-999 Variable This field displays the positionnumber of the operator that reportedthe trouble condition.











Description

OPR VOICE symbolic text Variable This field displays the individualoperator voice link (may be a TOPSoperator centralization voice link) inuse.

ALT RTE alphanumeric Variable This field provides the operator withthe ability to perform alternate routingfor international calls when aconnection cannot be made by wayof a direct route. This may occur if nodirect route exists or if the directroute is connected.

MEMO alphanumeric Variable This field displays additionalinformation that the operatorspecifies to further explain theservice problem.




CLGNO = 613-239_0123 850-1234

CLDNO = 850-1234

CF3P = CKT CF3P 6




SNAC102The Service Analysis Center (SNAC) subsystem generates this reportwhen an operator at a Traffic Operator Position System (TOPS) position orat an overseas operator center (OOC) keys in a trouble code. This troublecode corresponds to a trouble condition, which is either reported to theoperator by a customer or detected by the operator during the course ofcall processing.

SNAC102 157


An operating company (OC) may define up to 100 trouble codes in TableTOPSTRBL. When an operator at either the TOPS or the OOC receives ordetects a trouble condition, the operator enters a one- or two-digit troublecode that corresponds to the trouble condition. The SNAC subsystem onlygenerates this report for maintenance-related trouble conditions enteredthat are severe enough to generate a minor alarm.





• memo text

Remedial actionBy mapping the trouble code in SNAC102 to the TRBLCODE field of TableTOPSTRBL, operating company personnel can determine the troublecondition and take appropriate action to correct the problem. If it is notapparent what the correct action should be, the trouble condition should beforwarded to the next level of maintenance.

AttributesAttribute ValueSeverity Minor







CF3P = <agentid>


MEMO = <memo text>






CLGNO = <dn>

CLDNO = <dn>


CF3P = <agentid>


VariableDescription










SNAC102 159



Description




ALT RTE alphanumeric Variable This field provides the operator withthe ability to perform alternate routingfor international calls when aconnection cannot be made via adirect route. This may occur if nodirect route exists or if the directroute is connected.





CLGNO = 613-239_0123 850-1234

CLDNO = 850-1234

CF3P = CKT CF3P 6






SNAC103The Service Analysis Center (SNAC) subsystem generates this reportwhen an operator at a Traf c Operator Position System (TOPS) position orat an overseas operator center (OOC) keys in a trouble code. This troublecode corresponds to a trouble condition, which is either reported to theoperator by a customer or detected by the operator during the course ofcall processing.

An operating company (OC) may define up to 100 trouble codes in TableTOPSTRBL. When an operator at either the TOPS or the OOC receives ordetects a trouble condition, the operator enters a one- or two-digit troublecode that corresponds to the trouble condition. The SNAC subsystem onlygenerates this report for maintenance-related trouble conditions enteredthat are severe enough to generate a major alarm.





• memo text

Remedial actionBy mapping the trouble code in SNAC103 to the TRBLCODE field of TableTOPSTRBL, operating company personnel can determine the troublecondition and take appropriate action to correct the problem. If it is notapparent what the correct action should be, the trouble condition should beforwarded to the next level of maintenance.

AttributesAttribute ValueSeverity Major






SNAC103 161



CF3P = <agentid>


MEMO = <memo text>




CLGNO = <dn>

CLDNO = <dn>


CF3P = <agentid>


VariableDescription











Description






ALT RTE alphanumeric Variable This field provides the operator withthe ability to perform alternate routingfor international calls when aconnection cannot be made by wayof a direct route. This may occur if nodirect route exists or if the directroute is connected.





CLGNO = 613-239_0123 850-1234

CLDNO = 850-1234

CF3P = CKT CF3P 6


SNAC103 163




SNAC104The Service Analysis Center (SNAC) subsystem generates this reportwhen an operator at an overseas operator center (OOC) keys in a troublecode. This trouble code corresponds to a trouble condition, which is eitherreported to the operator by a customer or detected by the operator duringthe course of call processing.

Since the trouble code originates at an OOC position, report output is inFrench.

This log became obsolete in software stream TOPS03.

Remedial actionIdentify the trouble condition from the trouble code and take theappropriate action.



DMR = dn optxt clgnm

DME = dn optxt cldnm

RTE ALT = altnm

memotxt


VariableDescription

TBL n1 0-99 Variable indicates trouble condition. Seecustomer data table TOPSTRBL

n2 000-999 Variable provides login identification of theoperator that reported the troublecondition




Description

n3 000-999 Variable provides position number of theoperator that reported the troublecondition

DMR integers Variable provides calling number of thecustomer who reported the trouble.See table 1

optxt OM, blank Variable indicates a foreign calling directorynumber (DN) when option text (optxt)represents operationalmeasurements

clgnm customer name Variable provides the name of the customerthat reported the trouble condition

DME integers Variable provides the called number dialed bythe customer or operator on whichthe trouble is detected. See table I.

optxt OM, blank Variable indicates a foreign called DN whenoption text represents operationalmeasurements

cldnm customer name Variable provides the name of the customer atthe called number on which thetrouble condition was detected

RTE ALT character string Variable provides the alternate route codememotxt symbolic text Variable identifies the service problem. the

operator enters this data. Refer totable TOPSTRBL.

Active message exampleSNAC104 APR01 12:00;00 2112 TBL 14 315 21

DMR:514-8706657 SMITH

DME:44-214567832 OM COLLINS

RTE ALT: PAR

LA RTE ALT DE PARIS N''EST PLUS AUTHORISEE


SNAC104 165



SNAC105The Switching Network Analysis Center (SNAC) subsystem generates logSNAC105 when the number of consecutive invalid personal identificationnumber (PIN) entries associated with a known calling card number (CCN)exceeds a specified threshold within a certain time frame. This log is usefulfor detecting fraudulent use of calling cards.

Remedial actionThe craftsperson may disable the CNN if fraud is suspected.


FormatSNAC105 mmmdd hh:mm:ss ssdd TBL

CLGNO = dn

CLDNO = dn

SPLNO = dn


VariableDescription

CLGNO integers Variable provides the calling number of thecalling card user. See table I.

CLDNO integers Variable provides the called number dialed bythe calling card user. See table I.

SPLNO integers Variable provides the calling card number.See table I.

Active message exampleSNAC105 FEB05 11:41:21 2112 TBL

CLGNO = 613-223-5111

CLDNO = 212-333-7092

SPLNO = 613-618-4576





SOC300The system generates log report SOC300 during the software selectioncontrol (SOC) periodic audit.

This log indicates when the system finds a feature in a troubled state. Atroubled state is any state except IDLE or ON.

This log indicates one or more of the following:

• internal data is not the same

• partial SOC feature functionality

Log SOC300 associates with a major alarm.

Remedial actionContact Northern Telecom ETAS to assist in the resolution of the problemthat the SOC300 log indicates.


FormatSOC300 mmmdd hh:mm:ss ssdd TBL AUDIT

Feature: <SOC feature identifier>

State: <state name or numeric value>

Reason: <reason description>


VariableDescription

TBL Audit Constant Variable Indicates that trouble with the SOCperiodic audit is present.

Feature 8 alpha-numericcharacter string

Variable Contains the SOC feature identifier.

SOC300 167



Description

State 14 alpha-numericcharacter string

Variable This field contains the state of thereported feature. The state value canbe one of the following:

• IDLE TO ON

• ON TO IDLE

• STATE ERROR

• an integer followed by thecharacter string UNKNOWN

Reason 58 alpha-numericcharacter string

Variable This field indicates the reason for thegeneration of the log. The values forthis field can be one of the following:

• Feature was in an intermediatestate.

• Feature was in an invalid state.

Active message exampleSOC300 JUN12 14:49:22 7815 TBL Audit

Feature: AN0408__

State: State ERROR

Reason: Feature was found to be in an invalid state




This log indicates when an option in a defective state. A defective state isany state except IDLE or ON.



• partial SOC option functionality






FormatSOC301 mmmdd hh:mm:ss ssdd TBL Audit

Option: <SOC option identifier>




VariableDescription

TBL Audit Constant Variable Indicates that trouble with theperiodic audit is present.

Option 8 alphanumericcharacter string

Variable Contains the SOC option identifier.


Variable Contains the state of the reportedoption. The state value can be one ofthe following:

• IDLE TO ON

• ON TO IDLE

• STATE ERROR

• an integer and the characterstring UNKNOWN


Variable Indicates the reason for thegeneration of the log. The values forthis field can be one of the following:

• Option found to be in anintermediate state.

• Option found to be in an invalidstate.


SOC301 169


Option: OSDA0006

State: State ERROR

Reason: Option was found to be in an invalid state



SOC302The system generates log report SOC302. The system generates thisreport when a problem with a feature is detected during an audit. Thesystem generates this log for problems relating to internal data differencesand defective features.

Remedial actionContact Northern Telecom (Nortel) ETAS for support.

Keep any SWERs or SOC logs related to this problem. Preserve all data toassist in problem identification and resolution.


FormatSOC302 mmmdd hh:mm:ss nnnn TBL Audit Failure




VariableDescription

Feature alpha-numeric Variable Specifies the feature identifier of thefeature with the problem.

Reason failed to audit (usenot counted)

Variable Indicates the audit procedure of thefeature did not complete for a reasonnot known.




Description

parent option isinvalid

Variable Indicates that the system is not ableto locate the parent option of thefeature in the database.

trouble flag is set Variable Indicates that the feature reportedthat the feature is defective. Thesystem did not record the feature asdefective before.

Active message exampleSOC302 MAY26 09:13:16 4606 TBL Audit Failure

Feature: SOCFTR04

Reason: parent option is invalid




This log indicates an audit failed on an option.




Log SOC303 associates with a minor alarm.



FormatSOC303 mmmdd hh:mm:ss ssdd TBL Audit Failure

SOC303 171



Reason: failed to audit (data access error); resultsuncertain


VariableDescription

TBL Audit failure Constant Variable Indicates that the SOC periodic auditfailed.

Option 8 alpha-numericcharacter string


REASON Constant Variable FEATURE FAILED TO AUDIT (DATAACCESS ERROR). RESULTSUNCERTAIN indicates that the optiondatabase information could not beread. The audit could not beperformed.

Active message exampleSOC303 JUN12 14:49:38 8926 TBL Audit failure

Option: OSDA0006

Reason: failed to audit (data access error); results

uncertain




This log indicates when an option and / or a part feature have differentstates.










Identifier State Time

------------------ ------------------------------------------

Option: <option id> <state value> YY/MM/DD

Feature: <feature id> <state value> YY/MM/DD

Reason: Option and its feature state mismatch


VariableDescription

TBL Audit Constant Variable Indicates trouble with the SOCperiodic audit occurred.

Option Identifier 8 alpha-numericcharacter string


Option State 14 alpha-numericcharacter string


• ON

• IDLE

• IDLE TO ON

• ON TO IDLE

• STATE ERROR


Feature Identifier 8 alpha-numericcharacter string


SOC304 173



Description

Feature State 14 alpha-numericcharacter string


• ON

• IDLE

• IDLE TO ON

• ON TO IDLE

• STATE ERROR


Time YY/MM/DD Variable Identifies the year, month and day ofthe reported difference.

REASON Constant Variable OPTION AND ITS FEATURE STATEMISMATCH indicates that the stateof the option and the state of thefeature do not correspond.


Identifier State Time

--------- ------------ --------

Option: OSDA0004 ON 94/06/12

Feature: AN0408__ IDLE 94/06/12

Reason: Option and its feature state mismatch




This log identifies a mismatch between an SOC database and a featurestate.







Remedial actionThere is no action required for this log. Log report SOC can place thefeature into the state that the feature indicates in the log. Log report SOCalso can update the parent option(s) of the feature accordingly.




State Troubled

------------------------ --------------------

Feature: <state value> <trouble indicator>

SOC : <state value> <trouble indicator>

Reason : SOC and feature data mismatch


VariableDescription

TBL Audit Constant Variable Indicates trouble with the SOCperiodic audit is present.


Variable Contains the SOC feature identifier

Feature state 14 alpha-numericcharacter string

Variable Contains the state of the reportedfeature. The state value can be oneof the following:

• ON

• IDLE

• IDLE TO ON

SOC305 175



Description

• ON TO IDLE

• STATE ERROR

• an integer and the characterstring UNKNOWN.

Feature trouble 14 alpha-numericcharacter string

Variable Indicates if the feature is troubled(YES) or not (NO).

SOC state 14 alpha-numericcharacter string

Variable Contains state of the featureaccording to the SOC database. Thestate value can be one of thefollowing:

• ON

• IDLE

• IDLE TO ON

• ON TO IDLE

• STATE ERROR


SOC trouble 14 alpha-numericcharacter string

Variable Indicates if the feature is troubled(YES) or not in agreement with theSOC database.

REASON Constant Variable SOC AND FEATURE DATAMISMATCH indicates that theinformation in the SOC database andthe feature information do notcorrespond.


Feature: AN0408__

State Troubled

------------ ---------------

Feature: IDLE TO ON YES

SOC: ON NO

Reason: SOC and feature data mismatch






This log indicates that the system can not access the SOC featuredatabase or the SOC option database during an audit. The system cannotcomplete the audit.







FormatSOC306 mmmdd hh:mm:ss ssdd TBL Audit failure



VariableDescription

TBL Audit failure Constant Variable Indicates that the SOC periodic auditfailed.


Variable Indicates that the system was notable to access the SOC featuredatabase or the SOC optiondatabase. The system did not audit

SOC306 177



Description

the SOC features (or the SOCoptions). The value of this field canbe one of the following:

• audit not done; cannot getfeature list

• audit not done; cannot get optionlist

Active message exampleSOC306 JUN12 14:49:38 9229 TBL Audit failure

Reason: audit could not be done; could not get feature

list



SOC307The system generates log report SOC307 during the software optionalitycontrol (SOC) periodic audit.

This log indicates that the system cannot access the SOC option databaseduring an audit. The system cannot complete the audit.









FormatSOC307 mmmdd hh:mm:ss ssdd TBL Audit failure





VariableDescription

TBL Audit Constant Variable Indicates that trouble with the SOCperiodic audit is present.



Option 8 alpha-numericcharacter string


REASON Constant Variable FEATURE NOT FOUND IN THEFEATURE LIST OF THE PARENTOPTION. REASON indicates that theoption that the feature recorded as itsparent does not have the featurerecorded as its child.


Feature: AN0408__

Option: ENSV0007

Reason: feature not in parent option''s feature list



SOC308The system generates log report SOC308 when the following occurs:

• a feature indicates that the feature is in a troubled state to the softwareselection control (SOC) database

• the SOC database did not record this feature as troubled before

SOC308 179



Remedial actionContact Northern Telecom ETAS to assist in the resolution of the problemindicated by an SOC308 log.


FormatSOC308 mmmdd hh:mm:ss ssdd FAIL Feature troubled





VariableDescription

FAIL Featuretroubled

Constant Variable Indicates that the reported feature isin a troubled state.




Variable Contains the state of the reportedfeature. The state value can be oneof the following:

• IDLE TO ON

• ON TO IDLE

• STATE ERROR

• an integer and by the characterstring UNKNOWN

REASON Constant Variable FEATURE IS MARKED ASTROUBLED indicates that thereported feature is marked astroubled. The SOC database did notrecord the feature as troubled

Active message exampleSOC308 JUN12 14:49:43 9532 TBL Feature trouble

Feature: AN0408___



State: IDLE

Reason: Feature is marked as troubled



SOC310The system generates log report SOC310 when a software optionalitycontrol (SOC) audit discovers a problem with a SOC option

Remedial actionIf the reason is "state is ON but right to use not set", immediate action isnot required. The option must have the state set to IDLE or obtain andapply the right to use.

If the reason is not "state is ON but right to use not set", keep a record ofthe log and contact next level of support.


FormatSOC310 mmmdd hh:mm:ss nnnn TBL Audit

Option: <option>

Reason: <reason>


VariableDescription

option Character string of 8alphanumeric

Variable Identifies the option to which the logrefers.

reason option is not defined Variable Indicates some reference to theoption occurs and is not completelydefined.

reason state is ON but rightto use not set

Variable The option is on, but the right to usethe option is not set

SOC310 181



Description

reason feature list is invalid Variable Indicates damage to the list ofmember features of the option.

reason option is a memberof its own precludeslist

Variable Indicates the option precludes theoption.

Active message exampleSOC310 AUG31 19:43:21 6900 TBL Audit

Option: ENSV0007

Reason: option is a member of its own precludes list



SOC311The system generates log report SOC311. The system generates thisreport when a feature change to the requested state during the one-nightprocess (ONP) for software upgrades fails.

Log SOC311 indicates failure of a feature state change request.


This log is an important ONP information log. Issues related to theindicated feature can arise because of the following reasons:

• The failure of the feature to return to the original state of the feature.

• The feature was not able to accept original data transferred across.

Remedial actionContact Northern Telecom ETAS to assist in resolution of the problem thatthe SOC311 log indicates.


FormatSOC311 mmmdd hh:mm:ss ssdd FAIL Software upgrade transition




From: <state name or numeric value>

Request: <state name>

Result: <state name or numeric value>


Summary: Feature did not reach requested state


VariableDescription

FAIL Softwareupgrade transition

Constant Variable Indicates failure of the reportedfeature to change to a requestedstate during the ONP.

Feature 8-alphanumericcharacter string


From 14-alphanumericcharacter string

Variable Contains the current state of thereported feature. The state value canbe one of the following:

• IDLE

• ON

• IDLE TO ON

• ON TO IDLE

• STATE ERROR

• an integer and character stringUNKNOWN

Request 14-alphanumericcharacter string

Variable Contains the state of the reportedfeature. The state value can be ONor IDLE.

Result 14-alphanumericcharacter string

Variable Contains the current state of thereported feature. The state value canbe one of the following:

• IDLE

• ON

• IDLE TO ON

• ON TO IDLE

SOC311 183



Description

• STATE ERROR

• an integer and character stringUNKNOWN

Reason 58-alphanumericcharacter string

Variable Indicates the reason for the failedchange. The value for this field isvariable and the feature provides itsown explanation.

SUMMARY Constant Variable FEATURE DID NOT REACHREQUESTED STATE indicates thatno change occurred. The requestedstate is the same as the state of thefeature before the ONP. When theoriginal feature state does notcontinue on original feature datatransfer, loss of data and associatedservice can occur. The loss occurs inthe new software upgrade.

Active message exampleSOC311 JUN12 14:49:58 9936 FAIL Software upgrade transition

Feature: AN0408__

From: IDLE

Request: ON

Result: IDLE

Reason: Cannot alloc memory

Summary: Feature did not reach requested state



SOC312The system generates log report SOC312 during the Software OptionalityControl (SOC) periodic audit. Log report 312 indicates that the auditdetected a feature-related error in the SOC database.

Remedial actionContact your next level of support to assist in resolution of the problem.




FormatSOC312 mmmdd hh:mm:ss nnnn INFO Data mismatch



Reason: <reason text>


VariableDescription

INFO Data mismatch constant Variable Indicates detection of a feature-related error in the SOC database.

Option 8-alphanumericcharacter string




Reason 58-alphanumericcharacter string

Variable • Contains a description of thefeature-related error. The valuefor this field can be one of thefollowing:

• "feature belongs to differentoption" -Indicates that in thecurrent database the recordedparent of the feature does notregister the feature as a memberfeature

• "feature is not a valid feature" -Indicates that in the currentdatabase the data of the featureis not consistent or corrupts

• "feature's UNITS do not matchoption's" - Indicates that, in thecurrent database, the featureusage units do not match theunits of the option parent of thefeature.

Active message exampleSOC312 AUG31 19:43:32 8500 INFO Data mismatch

SOC312 185


Option: OSDA006

Feature: AN0409___

Reason: Feature belongs to a different option



SOC313The system generates log report SOC313 during an audit or featurerequest. The system generates this report when Software OptionalityControl (SOC) detects a minimum of one invalid or not available SOCfeature support procedure.


Remedial actionContact the next level of support. Keep any SWERs or other SOC logsrelated to this problem to assist in problem identification and resolution.




The following procedures are invalid or unavailable:

<procedure list>


VariableDescription


Variable Specifies the SOC feature identifier.

procedure list Audlt Impact ResetSoftware UpgradeTransition ValidateUsage Audit InformLimit

Variable Specifies the procedure identifiersthat are invalid or not available.



Active message exampleSOC313 JAN10 10:28:44 5310 TBL Audit

Feature: SOCFTR05

The following procedures are invalid or unavailable:

Audit, Impact, Reset, Software Upgrade, Transition,

Validate



SOC314The system generates log report SOC314 during a Software OptionalityControl (SOC) audit. Log report SOC314 indicates that the audit detected aproblem related to a specified feature.

Remedial actionKeep a record of the log and contact the next level of support.



Feature: <feature>

Reason: <reason>


VariableDescription

feature 8-alphanumericcharacter string

Variable Identifies the feature to which the logrefers.

reason Feature not amember of anyoption

Variable The feature does not appear in theCONTAINS list of an option.

SOC314 187



Description

reason Feature bound toSOC but not indatabase

Variable The feature bound procvars withSOC, and does not appear in theSOC Content File.

reason Feature in databasenot bound to SOC

Variable The feature appears in the SOCContent File, but did not bindprocvars with SOC at IPL

reason Feature is notdefined butreferences to thefeature exist

Variable Other features or options refer to thisone in their DEPENDS,PRECLUDES, or CONTAINS lists.But it does not appear in the SOCContent file, and did not bindprocvars with SOC at IPL.

reason Error retrieve featuredata-audit is notcomplete

Variable A database error occurred during anattempt to audit this feature.

reason Feature is a memberof its own precludeslist

Variable The feature names the feature as apart of precludes list of the feature.


Feature: AN0408___

Reason: Feature is a member of its own precludes list



SOC315The system generates log report SOC315 when the system finds a cycle inthe uses relationships between the named options. One of the two optionsdepends directly on the other. The other option depends on the rst optionthrough other options or directly. This condition is an error because noindication is present as to which option to turn on rst.

The system always generates more than one log SOC315. The systemgenerates this log for each option in the loop. An examination of allSOC315 logs from a given audit indicates exactly what options are in theloop.






Option 1: <option_1>

Option 2: <option_2>

Reason: <reason>


VariableDescription

option_1 8-alphanumericcharacter string

Variable Identifies one of the options to whichthe log refers.


Variable Identifies the second option to whichthe log refers.

reason Options depend oneach other (possiblyindirectly)

Variable Indicates that the options named arein a uses loop.


Option 1: ENSV0007

Option 2: ABS00008

Reason : Options depend on each other (possibly

indirectly)


SOC315 189



SOC316The system generates log report SOC316 when the system finds a cycle inthe uses relationships between the named features. One of the two optionsdepends directly on the other. The other option depends on the rst optionthrough other options or directly. This condition is an error because noindication is present as to which option to turn on rst.

The system always generates more than one log SOC316. The systemgenerates this log for each feature in the loop. An examination of allSOC315 logs from a given audit indicates exactly what features are in theloop.




Feature 1: <feature_1>

Feature 2: <feature_2>

Reason: <reason>


VariableDescription

feature_1 8-alphanumericcharacter string

Variable Identifies one of the features the logrefers to.


Variable Identifies the second feature the logrefers to.

reason Features depend oneach other (possiblyindirectly)

Variable Indicates the named features namedare in a uses loop.


Feature 1: AN0408__



Feature 2: AN0819__

Reason : Features depend on each other (possibly

indirectly)



SOC317The system generates log report SOC317 during a Software OptionalityControl (SOC) audit. The system generates this report when the auditdetects the following conditions:

• Feature A in option X needs feature B in option Y

• Feature B needs some other feature C in option X

Activation of these options breaks the dependency rules.

Remedial actionKeep a record of the log and contact next level of support.



Feature 1: <feature_1> Option 1: option_1

Feature 2: <feature_2> Option 2: option_2

Reason: <reason>


VariableDescription


Variable Identifies one of the features involvedin an implied uses loop.


Variable Identifies the option that containsfeature_1.

SOC317 191



Description


Variable Identifies the second feature in animplied uses loop.


Variable Identifies the option that containsfeature_2.

reason Implied loop in optiondepends due tofeature depends

Variable Indicates a dependency cycle existsbecause of the action betweenfeature dependencies and optionsubscription.


Feature 1: AN0408__ Option 1: ENSV0007

Feature 2: AN0819__ Option 2: ABS00008

Reason : Implied loop in option depends due to feature

depends



SOC318The system generates log report SOC318 log. The system generates thisreport when an option depends on an illegal option for one of the followingreasons:

• The needed option is undefined, is pending, does not apply , or isusage-only.

• The needed option precludes the named option.

• The needed option is in the IDLE state while the named option is in ONstate.

• The precluded option is not defined, is pending, or is use-only .

Remedial actionIf the reason is "Needed option is in a less active state," turn on theneeded option or turn off the option that requires the needed option.

If the reason is not "Needed option is in a less active state", keep a recordof the log and contact the next level of support.




FormatLoad_name * SOC318 mmmdd hh:mm:ss nnnn TBL Audit

Option: <option>

Needed option: <needed_option>



VariableDescription

option 8-alphanumericcharacter string

Variable Identifies the option that depends onan option that is not legal.

needed_option 8-alphanumericcharacter string

Variable Identifies the option that is not legal.

reason text Needed option isundefined, pending,N/A, or usage.

Variable Indicates the option named uses anoption that is not present.

reason text Option and neededoption cannotcoexist.

Variable Indicates that the named optionrequires and precludes the neededoption.

Needed option is in aless active state.

Variable Indicates the named option is in theON state and depends on an optionin the IDLE state.

Precluded option isundefined, pending,or usage.

Variable Indicates the named option uses anoption that is not present, or is of thewrong type.

Option is undefinedor cannot use optionneeded.

Variable The named option uses an optionthat is not defined or that cannot usethe needed option.

Active message exampleBASE_ALL04AN * SOC318 AUG31 19:43:32 8500 TBL Audit

Option: SOCOPT04

Needed option: SOCOPT05

Reason: Needed option is undefined, pending or usage

SOC318 193




SOC319The system generates log report SOC319 when a feature depends onanother feature that is not legal. The necessary feature is not defined orthe necessary feature precludes the named feature.




Feature: <feature>

Needed feature: <needed_feature>

Reason: <reason>


VariableDescription


Variable Identifies the feature that depends onan feature that is not legal.

needed_feature 8-alphanumericcharacter string

Variable Identifies the necessary feature thatis not legal.

reason Needed feature isundefined

Variable Indicates that the option named usesan option which is not present.

reason Feature needs andprecludes otherfeature

Variable Indicates that the feature namedrequires and precludes the neededfeature.


Feature: AN0408__

Needed feature: AN0819__



Reason: Needed feature is undefined



SOC320The system generates log report SOC320 for a problem of feature A thatuses feature B and precludes feature C. Features B and C must be in thesame option.




Feature: <feature> in Option: <option>

Needed Feature: <need_feature> in Option: <need_option>

Precluded Feature: <preclude_feature> in Option:<preclude_option>

Reason: <reason>


VariableDescription


Variable Identifies the feature that needs orprecludes other features.


Variable Identifies the option that containsfeature.

need_feature 8-alphanumericcharacter string

Variable Identifies the necessary feature.

need_option 8-alphanumericcharacter string

Variable Identifies the option that containsneed_feature.

preclude_feature 8-alphanumericcharacter string

Variable Identifies the precluded feature.

SOC320 195



Description

preclude_option 8-alphanumericcharacter string

Variable Identifies the option that containspreclude_feature (the same asneed_option).

reason Needed andprecluded featuresare in same option

Variable Indicates the necessary andprecluded features are in the sameoption.


Feature: AN0408__ in Option: ENSV0007

Needed Feature: AN0819__ in Option: ABS00008

Precluded Feature: AN0409__ in Option: ABS00008

Reason: Needed and precluded features are in same option



SOC321The system generates log report SOC321 when a feature precludesanother feature in the same option. The option cannot activate becausethese features cannot be on at the same time.




Feature: <feature> in Option: <option>

Precluded Feature: <precluded_feature>

Reason: <reason>




VariableDescription


Variable Identifies the feature that precludesanother feature.


Variable Identifies the option that contains theseparate features.

precluded_feature 8-alphanumericcharacter string

Variable Identifies the precluded feature.

reason Feature andprecluded featureare in same option

Variable Indicates that both the feature andthe precluded feature are in the sameoption.


Feature: AN0408__ in Option: ENSV0007

Precluded Feature: AN0819__

Reason: Feature and precluded feature are in same option



SOC322The system generates log report SOC322 when a Software OptionalityControl (SOC) audit detects both of two separate options turned on.

Remedial actionOne or both of the options must be IDLE.



Option: <option>

Precluded option: <precluded_option>

SOC322 197


Reason: <reason>


VariableDescription


Variable Identifies one of the two separateoptions.

precluded_option 8-alphanumericcharacter string

Variable Identifies the other option.

reason Option andprecluded option areboth ON

Variable Indicates the option and theprecluded option are both ON.


Option: ENSV0007

Precluded option: ABS00008

Reason: Option and precluded option are both ON



SOC323The system generates log report SOC323 during a Software OptionalityControl (SOC) audit. The system generates this report when the audit findsa usage-only option that depends on, or precludes another option. Onlystate and dual options can depend on or preclude other options.

Remedial actionThis log indicates an error in the SOC database. Contact the next level ofsupport.



Option: <option>



Usage based option has dependencies


VariableDescription

Option 8-alphanumericcharacter string

Variable Specifies the order code for theusage option that depends orprecludes the option.

Usage based optionhas dependencies

constant Variable Indicates that the usage optiondepends on, or precludes anotheroption.


Option: SOCOPT04

Usage based option has dependencies



SOC324The system generates SOC324 if, during an audit, SOC finds a usage-onlyfeature with ndencies on, or preclusions with, another feature. Only state ordual features can have dependencies or preclusions.

Remedial actionLog SOC324 indicates a severe error in the SOC database. Contact thepersonnel responsible for the next level of support.



Feature: <feature>

Usage based feature has dependencies

SOC324 199



VariableDescription

Feature alphanumeric Variable Specifies the order code for theusage feature that has dependenciesor preclusions.

Usage based featurehas dependencies

constant Variable Indicates that a usage feature hasdependencies on or preclusions withanother feature.


Feature: SOCFTR04

Usage based feature has dependencies



SOC325The system generates SOC325 if, during an audit, SOCfinds an option withan illegal usage limit. A legal usage limit is from 0 to 999999.

Remedial actionRequest a password for a correct usage limit from Northern Telecom. Usethe ASSIGN LIMIT command to apply the correct usage limit to the option.



Option: <option>

Limit: <limit>

Reason: <reason>




VariableDescription

Option alphanumeric Variable Specifies the order code of the optionwith the illegal usage limit.

Limit numeric Variable Specifies the current usage limit ofthe option.

Reason Limit must not bebelow zero

Variable Indicates that the illegal usage limit isbelow zero.

Limit must not beover 999999

Variable Indicates that the illegal limit is over999999.


Option: SOCOPT04

Limit : -5

Reason: Limit must not be below zero



SOC326The system generates SOC326 if the features of an option do not matchthe type of the option. The following rules apply to features in options:

• A state option must contain at least one state-only feature and no othertype of feature.

• A usage option must contain at least one one usage-only feature andno other type of feature.

• A dual option must contain at least one usage component and at leastone state component.

Remedial actionThis log indicates a severe error in the SOC database. Contact the nextlevel of support.


SOC326 201



Option: <option>

Reason: <reason>


VariableDescription

Option Alphanumeric Variable Specifies the order code of the optionthat violates one of the SOC rules.

Reason Usage optioncontains state/dualfeature

Variable Indicates the option is usage andcontains a state or dual feature.

State option containsusage/dual feature

Variable Indicates the option is state andcontains a usage or dual feature.

Dual option has nousage/dual feature

Variable Indicates the option is dual and doesnot contain a usage or dual feature.

Dual option has nostate/dual feature

Variable Indicates the option is dual and doesnot contain a state or dual feature.

Option containsillegal features

Variable Indicates the option contains featuresthat are not allowed.

No features in option Variable Indicates there are no features in theoption.


Option: SOCOPT04

Reason: Usage option contains state/dual feature



SOC400The system generates SOC400 at the end of a SOC audit. Log SOC400summarizes the results of the audit and reports the total number ofregistered options:

• in the IDLE state

• in the ON state



• in a trouble state

• with the right-to-use (RTU) set

Log SOC400 also speci es the total number of errors that caused logs togenerate during the audit.

Options in a trouble state can have functionality that is not complete.

Remedial actionIf the ERRS field is not zero, check the SOC logs to determine the errorsand take appropriate action.


FormatSOC400 mmmdd hh:mm:ss nnnn SUMM SOC option audit summary

Total IDLE ON TBL RTU ERRS

_______ ______ _______ _______ _______ _______

<nnnnn> <nnnnn> <nnnnn> <nnnnn> <nnnnn> <nnnnn>

Audit Reason: <reason>


VariableDescription

Total 0-511 Variable Indicates the total number of optionsdefined in the SOC database.

IDLE 0-511 Variable Indicates the total number of optionsin the IDLE state.

ON 0-511 Variable Indicates the total number of optionsin the ON state.

TBL 0-511 Variable Indicates the total number of optionsin a trouble state.

RTU 0-511 Variable Indicates the total number of optionswith the RTU set.

ERRS numeric Variable Identifies the total number of errorconditions reported in logs during theaudit.

SOC400 203



Description

Audit Reason User Request Variable Indicates that a user requested theaudit.

Periodic Audit Variable Indicates that the audit was a routineSOC audit.

Post-Restart Audit Variable Indicates that after a RELOAD or aCOLD restart the audit runs.

Active message exampleSOC400 JAN05 16:49:26 3603 SUMM SOC option audit summary

Total IDLE ON TBL RTU ERRS

------ ------ ------ ------ ------ ------

14 10 1 0 1 0

Audit Reason: User Request



SOC402The system generates SOC402 during an audit in which SOC determinesthat the current usage of an option exceeds its warning threshold. This logtells the operating company the usage for this option is near the limit.

Remedial actionn/a


FormatSOC402 mmmdd hh:mm:ss nnnn INFO Usage Exceeds Threshold

Option: <option>

Usage: <usage>

Threshold: <threshold>



Limit: <limit>


VariableDescription

Option alphanumeric Variable Specifies the order code of the SOCoption to which this log applies.

Usage alphanumeric Variable Specifies the current usage ofresources for this option.

Threshold alphanumeric Variable Specifies the current warningthreshold, either a number or apercent.

Limit alphanumeric Variable Specifies the limit of usage for theoption. If the number is followed byan S, the limit may be exceeded, buta log will be generated. If the limit isMONITORED, the option has no limit.

Active message exampleSOC402 JAN10 10:29:05 8845 INFO Usage Exceeds Threshold

Option: SOCOPT04

Usage: 255

Threshold: 50%

Limit: 500



SOC403The system generates SOC403 during an audit in which SOC detects anoption with a current usage that exceeds its limit. This log only indicates anerror if the usage limit is hard.

Remedial actionIf the limit of the option is hard (no suf x S), this log indicates an errorcondition. The operating company should immediately reduce usage of theresource controlled by this option or obtain a higher limit from NorthernTelecom.

SOC403 205


If the limit of this option is soft (with suf x S), no immediate action isrequired. The contract under which this option was purchased dictates theappropriate action.


FormatSOC403 mmmdd hh:mm:ss nnnn INFO Current Usage Exceeds Limit

Option: <option>

Usage: <usage>

Limit: <limit>


VariableDescription

Option alphanumeric Variable Specifies the order code of the SOCoption that exceeds its usage limit.

Usage numeric Variable Specifies the current usage of thisoption.

Limit numeric Variable Specifies the usage limit of thisoption.

Active message exampleSOC403 JAN10 10:29:06 9047 INFO Current Usage Exceeds Limit

Option: SOCOPT04

Usage: 406

Limit: 400S



SOC404The system generates SOC404 during an audit in which SOC determinesthat the usage of an option exceeds 2147483647. The number2147483647 is the highest number SOC can count. The limit for the option



must be soft or monitored in order for this condition to exist. The SOCcontinues to allow resources to be allocated. The SOC does not allowresources to decrease because a number is not present to subtract from.

Remedial actionContact the personnel responsible for your next level of support. Theusage counter of the option must be set again.


FormatSOC404 mmmdd hh:mm:ss nnnn INFO SOC Usage Has Overflowed

Option: <option>

Usage is greater than 2147483647


VariableDescription

Option alphanumeric Variable Specifies the order code of the SOCoption with overflowed usage thatcannot be decreased.

Usage is greaterthan 2147483647

constant Variable Indicates the usage of the optionexceeds the maximum number towhich SOC can count.

Active message exampleSOC404 JAN10 10:29:07 9249 INFO SOC Usage Has Overflowed

Option: SOCOPT04

Usage is greater than 2147483647



SOC500The system generates SOC500 when a feature changes to a stable statefrom a troubled transition state.

SOC500 207


Remedial actionn/a


FormatSOC500 mmmdd hh:mm:ss nnnn PASS State transition


User: <user name> Terminal: <terminal name>





VariableDescription

Feature alphanumeric Variable Specifies the SOC feature identifier.User alphanumeric Variable Specifies the name of the user that

requested this transition.Terminal alphanumeric Variable Specifies the name of the terminal at

which this request was made.From alphanumeric Variable Specifies the original state of the

option.Result alphanumeric Variable Specifies the state the option is in

now.Reason Recovery to stable

state from transitionstate

Variable Indicates the stable state replacedthe troubled transition state.

Feature recoveryover restart

Variable Indicates a restart achieved thestable state after troubled transition.

Feature has beenreset

Variable Indicates the feature reset to a stablestate because it trapped or timed outon a previous SOC request.

Active message exampleSOC500 SEP05 18:14:33 9350 PASS State transition

Feature: SOCFTR04



User: ADMIN Terminal: VMAP1

From: IDLE TO ON

Result: ON

Reason: Recovery to stable state from transition state



SOC501The system generates SOC501 when an option changes state.

Remedial actionn/a


FormatSOC501 mmmdd hh:mm:ss nnnn PASS State Transition

Option : <option>

User : <user> Terminal: <terminal>

From : <from state>

Result: <result state>

Reason : <reason>


VariableDescription

Option alphanumeric Variable Specifies the order code of the SOCoption that changed state.

User alphanumeric Variable Specifies the DMS user ID of theuser that requested this transition.

Terminal alphanumeric Variable Specifies the DMS terminal ID of theterminal that originated the request.

SOC501 209



Description

From alphanumeric Variable Indicates the original state of theoption.

Result alphanumeric Variable Indicates the end state of the option.Reason Recovery to stable

state from transitionstate

Variable Indicates the option changed to astable state from a troubled transitionstate.

Recovery to stablestate during restart

Variable Indicates the option changed to astable state from a troubled transitionstate. The recovery occurred as aresult of a restart.

Manual request Variable Indicates the option reached thisstate as the result of a manual SOCrequest.

Active message exampleSOC501 JAN10 10:29:11 9855 PASS State transition

Option: SOCOPT04

User: OPERATOR Terminal: TTYO

From: IDLE

Result: ON

Reason: Manual request



SOC502The system generates SOC502 when a feature fails to change to the staterequested by the assigned command. Log SOC502 is provided as anevent trail.

Remedial actionThere is no action required. This log is part of the SOC event trail andindicates the state transition is not successful.




Formatload_name SOC502 mmmdd hh:mm:ss ssdd FAIL State transition


User: <user name> Terminal: <terminal name>


Target: <state name or numeric value>




VariableDescription

FAIL State transition Constant Variable This field indicates that a featurefailed a requested state transition.

Feature 8 alphanumericcharacter string

Variable This field contains the SOC featureidentifier.

User 12 alphanumericcharacter string

Variable This field contains the name of theuser that requested this transition.

Terminal 16 alphanumericcharacter string

Variable This field contains the name of theterminal that originated this request.

From 14 alphanumericcharacter string

Variable This field contains the original stateof the reported feature. The statevalue can be one of the following:

• IDLE

• ON

• IDLE TO ON

• ON TO IDLE

• STATE ERROR


Target 14 alphanumericcharacter string

Variable This field contains the state thefeature failed to reach. The statevalue must be either IDLE or ON.

SOC502 211



Description

Result 14 alphanumericcharacter string

Variable This field contains the end state ofthe reported feature. The state valuemust be either IDLE or ON.

Reason 58 alphanumericcharacter string

Variable This field indicates the reason whythe feature transition to the requestedstate failed. The value for this fieldcan be one of the following:

• Invalid target state - indicatesthat the feature is already in therequested state.

• Invalid result state - indicates thatit reached the target state but thereported state is not the targetstate.

• Unsupported transition - meansthe feature does not support atransition to the requested state.

• A non-specific error has occurred- the feature indicated that itfailed to reach the target state butdid not provide any reason forthis failure.

• Feature provided an undefinedresponse means the transitionrequest response for the featurewas not defined and the data canbe corrupt. The feature canappear not normal.

• Feature trapped and was reset -means a severe error orcondition occurred during thetransition and the feature was notable to change state. The featurewas reset to a stable state.

• Feature trapped and was notreset -means a severe error orcondition occurred during the




Description

transition and the feature was notable to change state. It was notreset to a stable state.

• Feature failed to adjust stateduring ONP -means the featuredid not reach the requested stateduring one-night softwareupgrade.

Active message exampleBAS_ALL05AG SOC502 18:14:33 4827 INFO Device State Change

Feature: SOCFTR04

User: ADMIN Terminal: MAP

From: ON

Target: IDLE

Result: ON

Reason: Unsupported transition



SOC503The system generates SOC503 when an option failed to make the changeto a new state for one of the following reasons:

• The right of the option to use was not set. (IDLE->ON transitions only)

• One or more features failed to make the change to the new state.

• One or more features refused to make the change to the new state.

Features control if they are changed to a new state. You can reject arequest for a state change. The feature determines if the state changeaffects service, results in corrupted data, or leaves an unstable peripheralmodule.

• One or more features failed to determine if the change to the new stateis safe.

SOC503 213


A safe change does not result in corrupted data, loss or degradation ofservice, or an unstable peripheral module.

• A change in state creates a dependency violation.

• Database differences make it not possible to verify dependency safety.

A safe dependency does not result in corrupted data, loss or degradationof service, or an unstable peripheral module.

• A feature failed a change while the feature tried to rationalize optionstates.

• The option is not state controlled but use controlled.

Remedial actionKeep a record of the log and contact next level of support.

Transition failures and database differences require involvement of thenext level of support.


Formatload_name SOC503 mmmdd hh:mm:ss nnnn FAIL State transition

Option: <option>

User: <user> Terminal:<terminal>

From: <from_state>

Target: <target_state>

Result: <result_state>





VariableDescription

reason One or morefeatures failedimpact determination

Variable Indicates one or more memberfeatures failed to determine theimpact of setting the feature to IDLE.The member features cannotdetermine if the feature is in use.

refused due todependency errors

Variable Indicates the requested state changecreate dependency violations. Adescription of the changes neededfor the change to work is displayedwhen the state change is requested.

refused due todatabaseinconsistencies

Variable Indicates the database is not sane.Dependencies cannot be checked.The transition is not be allowed untildependencies are checked.

Illegal to set state ofusage-only option

Variable Indicates the option is not state-controlled and it is illegal to changethe state of the option.

Illegal to set state oftracked or pendingoption

Variable Indicates the option cannot have itsstate changed because the option isnot controlled.

User failed to confirmstate change

Variable The user is asked to enter the nameof the option to confirm the statechange. The user did not enter thecorrect name in the maximumnumber of attempts allowed (three).

Option is N/A (notapplicable)

Variable The option is not available for use inthe currently loaded PCL.

Option is A/P(always provided)

Variable The option is essential for thecurrently loaded PCL. It is not anOPTIONAL capability and you cannotmanipulate it.

option 8 alphanumericcharacters

Variable Identifies the SOC option.

user up to 12alphanumericcharacters

Variable Identifies the name of the user thatrequests the change.

terminal up to 16alphanumericcharacters

Variable Identifies the name of the terminalthat originated the state changerequest.

SOC503 215



Description

from_state up to 14alphanumericcharacters

Variable Identifies the original state of theoption. The value can be one ofIDLE, IDLE TO ON, ON, ON TOIDLE, STATE ERROR, or an integerfollowed by the string UNKNOWN.

target_state up to 14alphanumericcharacters

Variable Identifies the state the option failed toreach. The value can be either IDLEor ON.

result_state up to 14alphanumericcharacters

Variable Identifies the end state of the option.The value must be either IDLE orON.

reason Right To Use not set Variable Indicates that the Right To Use flagfor the option is not set.

reason One or morefeatures failedtransition

Variable Indicates that one or more memberfeatures did not reach the target stateand the option did not reach thetarget state. One or more SOC502logs indicate each feature that did notcomplete the transition request.

reason One or morefeatures failedvalidation

Variable Indicates one or more memberfeatures failed to validate therequested state transition The optiondid not reach the target state. One ormore SOC502 logs indicate eachfeature that did not complete thetransition request.

Active message exampleBASE_ALL04AN SOC503 AUG31 19:43:37 1400 FAIL Statetransition

Option: ENSV0007

User:OPERATOR Terminal: TTY0

From:IDLE

Target: ON

Result: IDLE

Reason: Right To Use not set





SOC504The SOC log reports the successful application of a software optionalitycontrol (SOC) key code to:

• assign a usage limit

• apply a right-to-use (RTU)

• remove an RTU

The log indicates the old and new values and any SOC comments andwarnings about a new limit.

Remedial actionTake the appropriate action to respond to a message, if present, in thewarning field.


FormatSOC504 mmmdd hh:mm:ss nnnn INFO Key Code Accepted

Option: <option>

User: <user> Terminal: <terminal>

Action: <action>

Old RTU: <old_rtu> New RTU: <new_rtu>

Old Limit: <old_limit> New Limit: <new_limit>

Comment: <comment>

Warning: <warning>

SOC504 217



VariableDescription

Option alphanumeric Variable Specifies the order code of the SOCoption to which the key code wasapplied.

User alphanumeric Variable Specifies the DMS user ID of theuser that initiated the key codeapplication.

Terminal alphanumeric Variable Specifies the DMS terminal ID of theterminal from which the commandwas executed.

Action Apply RTU Variable Indicates the action taken was toapply an RTU.

Remove RTU Variable Indicates the action taken was toremove an RTU.

Set Limit Variable Indicates the action taken was to seta usage limit.

Old RTU YES or NO Variable Indicates if the RTU for the optionwas set (YES) or not (NO) before thekey code was applied.

New RTU YES or NO Variable Indicates if the RTU for the optionwas set (YES) or not (NO) after thekey code was applied.

Old Limit alphanumeric Variable Identifies the old value of the usagelimit before the key code is applied.NA means not applicable.

New Limit alphanumeric Variable Identifies the new value of the usagelimit after the key code is applied. NAmeans not applicable.

Comment pending optioncreated

Variable Indicates an option with this ordercode is not present. The password iscorrect and a pending option iscreated.

RTU already set Variable Indicates the operation completed,but the RTU was already set for theoption. Changes did not occur.

RTU alreadyremoved

Variable Indicates the operation completed,but the RTU was already removedfrom the option. Changes did notoccur.

limit unchanged Variable Indicates the operation completed,but the limit was already set to thevalue. Changes did not occur.




Description

limit less than currentusage

Variable Indicates a condition that is not anerror, but is not normal. The new limitis less than the current usage.

limit less thanwarning threshold

Variable Indicates a condition that is not anerror, but is not normal. The new limitis less than the warning threshold sothe threshold cannot be reached.

Warning alphanumeric Variable Specifies a warning message, if any,provided by the software of theoption, not by SOC.

The explanations that follow are forthe warnings introduced in BASE07.Other warnings can occur.

Maximum supportedSSP routeset limit is2047 tuples.

Variable Indicates that an attempt was madeto change the SOC limit to a numberhigher than the maximum allowed.External routing is activated.

Maximum supportedSSP routeset limit is255 tuples.

Variable Indicates that an attempt was madeto change the SOC limit to a numberhigher than the maximum allowed.External routing is not activated.

Active message exampleSOC504 JAN10 10:29:25 2279 INFO Key Code Accepted

Option: SOCOPT04


Action: Apply RTU

Old RTU: NO New RTU: YES

Old Limit: N/A New Limit: N/A

Comment: none

Warning: none


SOC504 219



SOC505The SOC505 log describes the failure of an attempt to apply a SOC keycode to perform the following:

• assign a use limit

• apply a right-to-use (RTU)

• remove an RTU

This log indicates the current value and the reason for failure. This logprovides any comments SOC has on the operation.

Remedial actionMatch the failure reason in the following list:

• incorrect password -- Make sure the user types the password incorrectly. If the password is not correct, try the password again. If thepassword fails a second time, verify the password with NorthernTelecom (Nortel).

• incorrect syntax -- This message normally indicates that the key codefile is corrupt. Obtain the correct key code file from Nortel.

• internal error -- Obtain the associated TRAP, SWER and SOC logreports. Give these log reports to the next level of support forevaluation.

• failed to create pending option -- Obtain the associated TRAP, SWERand SOC log reports. Give these log reports to the next level of supportfor evaluation.

• cannot revoke RTU when state not idle -- Set the state of the option toIDLE using the ASSIGN STATE command.

• cannot set limit for state option -- Limits do not apply to state-onlyoptions. Try the ASSIGN RTU command or obtain the correct ordercode for the use or dual option.

• cannot change RTU for use or dual option -- The use limit for use anddual options determines the RTU. The use limit cannot be set directly.Try the ASSIGN LIMIT command or obtain the correct order code forthe state option.

• unknown option -- If this failure reason is an attempt to create apending option, the order code or password is not correct. If the optionis not a pending option, the order code is not correct. Try again with thecorrect password or order code.




FormatLoad_name SOC505 mmmdd hh:mm:ss nnnn INFO Key Code Rejected

Option: <option>


Action: <action>

Failure: <failure>

Current RTU: <rtu> Current Limit: <limit>

Comment: <comment>


VariableDescription

Option 8 alphanumericcharacters

Variable Identifies the order code of the SOCoption on which the user attemptedthe operation.

User up to 12alphanumericcharacters

Variable Identifies the DMS user ID of the userthat initiated the operation.

Terminal up to 16alphanumericcharacters

Variable Identifies the DMS terminal ID of theterminal where the user attemptedthe command.

Action Apply RTU Variable Indicates the system rejected anapplication for RTU.

Remove RTU Variable Indicates the system rejected anattempt to remove an RTU.

Set Limit Variable Indicates the system rejected anattempt to set a use limit.

Failure incorrect password Variable Indicates that the password is notcorrect.

incorrect Variable syntax Indicates that a key code fileis corrupt,

internal error Variable Indicates an internal error in the SOCutility.

failed to createpending option

Variable Indicates an internal error in the SOCutility.

SOC505 221



Description

cannot revoke RTUwhen state not IDLE

Variable Indicates that a state of the optionwas not set to IDLE when the userapplied the key code.

cannot set limit forstate option

Variable Indicates an attempt to set a use limitfor a state-only option. The state-onlyoption is not important.

cannot change RTUfor use or dual option

Variable Indicates an attempt to change theRTU of a use or dual option.

Cannot set limit to 0when state not idle

Variable Indicates that a state of the optionwas not set to IDLE when the userapplied a key code.

unknown option Variable Indicates that the order code orpassword is not correct.

cannot assign keycodes to N/A options

Variable The option is not available for use inthe currently loaded PCL. Thesystem cannot assign the key code.

Failure cannot assign keycodes to A/P options

Variable The option is necessary for thecurrently loaded PCL. The option isnot an OPTIONAL capability. Thesystem cannot change the option.

Current RTU YES or NO Variable Indicates if the RTU of the option isset. The RTU is not changed by thisoperation.

Current Limit alphanumeric Variable Identifies the current value of the uselimit. The value NA means that thisfield is not correct.

Comment RTU already set Variable Indicates that the RTU is set for thatoption.

limit already set tothis value

Variable Indicates that the use limit is set tothat value.

RTU alreadyremoved

Variable Indicates the RTU is not present forthat option.

none Variable Indicates that the operation arerequired. The previous three valueswere not required.

Active message exampleBASE_ALLOAN SOC505 JAN10 10:29:30 3184 INFO Key CodeRejected

Option: SOCOPT04




Action: Set Limit

Failure: incorrect password

Current RTU: YES Current Limit: 50S

Comment: limit already set to this value



SOC506The system generates SOC506 when a feature tells the softwareoptionality control (SOC) database that state of the feature changed. TheSOC database did not request the state change.

Remedial actionn/a


FormatSOC506 mmmdd hh:mm:ss ssdd TRAN Spontaneous state transition






VariableDescription

TRAN Spontaneousstate transition

Constant Variable Indicates that the state of a featurechanged. The SOC database did notrequest the change.

Feature 8 alphanumericcharacter string

Variable Indicates the SOC feature identifier.

SOC506 223



Description

From 14 alphanumericcharacter string

Variable Indicates the original state of thereported feature. The state value canbe one of the following:

• IDLE

• ON

• IDLETOON

• ON TO IDLE

• STATE ERROR


Result 14 alphanumericcharacter string

Variable Indicates new state of the feature.This state value can be one of thefollowing:

• IDLE

• ON

• IDLE TO ON

• ON TO IDLE

• STATE ERROR


Reason 58 alphanumericcharacter string

Variable Indicates the reason for the failedchange. The value for this field canbe one of the following:

• <Variable text>- the featureprovides the explanation.

• Feature state change overRESTART -the feature changedstate during a RESTART.

• Feature provided no explanation- the feature changed stateduring operation. The feature didnot provide an explanation.

Active message exampleSOC506 JUN12 14:50:19 4173 TRAN Spontaneous state transition

Feature: AN0409___

From: IDLE TO ON



Result: ON

Reason: Manual test



SOC507The SOC507 log indicates the user changed the warning threshold for anoption. When the current use of an option exceeds the threshold, thesystem generates a SOC800 log. When use exceeds the threshold whenan audit runs, the system generates a SOC402 log.

Remedial actionn/a


FormatSOC507 mmmdd hh:mm:ss nnnn INFO Option Threshold Change

Option: <option>


Old Threshold: <old threshold>

New Threshold: <new threshold>

Note: <note>


VariableDescription

Option alphanumeric Variable Specifies the order code of the SOCoption to which this log applies.

User alphanumeric Variable Specifies the DMS user ID of theuser that changed the threshold.

Terminal alphanumeric Variable Specifies the DMS terminal ID of theterminal where the user executed thethreshold change.

SOC507 225



Description

Old Threshold alphanumeric Variable Specifies the previous threshold.New Threshold alphanumeric Variable Specifies the new threshold.Note Threshold is higher

than use limitVariable Indicates that the threshold is much

higher than use limit. This thresholdis not often of use.

Current use exceedsnew threshold

Variable Indicates that current use exceedsthe threshold. The system will notgenerate a SOC800 log to indicatethat use exceeds the threshold.

Active message exampleSOC507 JAN10 10:29:33 3687 INFO Option Threshold Change

Option: SOCOPT04


Old Threshold: 100%

New Threshold: 75%

Note: none



SOC508The SOC508 log indicates failure of an attempt to set the warningthreshold for an option. When current use of an option exceeds thethreshold, the system generates SOC800. When use exceeds thethreshold when an audit runs, the system generates SOC402.

Remedial actionTake the correct action to address the problem in the Reason field. Try toset the warning threshold again. The restriction that a percentage thresholdother than 100% are not allowed for an option with a monitored limit cancause errors.




FormatSOC508 mmmdd hh:mm:ss nnnn INFO Threshold Change Failed

Option: <option>

User: <user> Terminal: <Terminal>

Current Threshold: <current threshold>

Reason: <reason>


VariableDescription

Option alphanumeric Variable Identifies the order code of the SOCoption for which the user attempts theoperation.

User alphanumeric Variable Identifies the DMS user ID of the userthat attempted the threshold change.

Terminal alphanumeric Variable Identifies the DMS terminal ID of theterminal where the user attemptedthe threshold change.

Current Threshold numeric Variable Identifies the current threshold.Reason Requested threshold

is illegalVariable Indicates that the system does not

allow the requested threshold.Not known option Variable Indicates that the order code for the

option is not correct.Cannot set thresholdon state-only option

Variable Indicates that the threshold cannot beset for a state-only option.

Cannot set thresholdon tracked orpending option

Variable Indicates that the threshold cannot beset for a tracked or pending option.

Active message exampleSOC508 JAN10 10:29:33 3788 INFO Threshold Change Failed

Option: SOCOPT04


Current Threshold: 50%

Reason: Requested threshold is illegal


SOC508 227



SOC509The system generates SOC509 when the state of an option changesduring a one-night process (ONP). The state changes because datatransferred during the ONP specifies that the option must be ON after theONP.

Remedial actionn/a


FormatSOC509 mmmdd hh:mm:ss nnnn INFO Feature Set Option''s State

Option: <option> Feature: <feature>

From state: <from state> To state: <to state>

Number of required options also changed: <num changed>


VariableDescription

Option alphanumeric Variable Identifies the option that changedstate.

Feature alphanumeric Variable Identifies the feature in the optionthat determines the option mustactivate.

From state alphanumeric Variable Identifies the state the option statebefore that option changed state.

To state alphanumeric Variable Identifies the state of the option now.Num of optionschanged

numeric Variable Identifies the number of options thatchanged state for this option. TheSOC changes the state of anyoptions on which the option relies.For example, if A and B are idle andA depends on B, B is turned on. Thisaction allows A to be turned onduring the ONP. In this example, thenumber of changed options is 1.



Active message exampleSOC509 SEP05 18:14:33 4091 INFO Feature Set Option''s State

Option: SOCOPT04 Feature: SOCFTR04

From state: IDLE To state: ON

Number of required options also changed: 23



SOC510The system generates SOC510 if an option attempts to change stateduring a one-night process (ONP), but fails. This condition can be serious.Functionality available before the ONP is not always available after theONP.

Remedial actionMatch the failure reason in the following list:

• Mutual exclusion problem -- Determine which of the options must beset to ON (active). The not active option can be set to ON. To set thisoption to ON, set the active option to IDLE and the not active option toON.

• Dependency error (uses loop or memory shortage) -- Execute theSOC;DBAUDIT command. Send all SOC, SWER and TRAP log reportsthat result from this command to the next level of support.

• Required option failed transition -- Review SOC502 and SOC503 logsto determine the reason the change failed. Correct the problem andattempt to manually change state with the ASSIGN STATE command.If the problem continues, collect all recent SOC502, SOC503, SOC510and SOC511 log reports. Contact the next level of support.

• Option failed transition -- Review SOC502 and SOC503 logsassociated with the option and the member features of the option. If thelogs indicate the reason for the failure, attempt to correct the problem.Attempt to change state with the ASSIGN STATE command. If theproblem continues, Collect all recent SOC502, SOC503, SOC510 andSOC511 log reports. Contact the next level of support.

• Internal error (check SWER log) -- Attempt to change state manuallywith the ASSIGN STATE command. Get the associated SWER andSOC log reports. Give these reports to the next level of support.

SOC510 229


• Not permitted to go to IDLE -- Set the option to IDLE (if desired) withthe ASSIGN STATE command.

• Not permitted to go to a transient state -- Determine the state the optionmust be in. Attempt to set the option to that state with the ASSIGNSTATE command.

• Not a state or dual option -- Send the SOC510 log report, recent SOClog reports and any recent SWER logs to Northern Telecom technicalsupport.

• Unknown feature -- Send the SOC510 log report, recent SOC logreports and any recent SWER logs to the next level of support.


FormatLoad_name SOC510 mmmdd hh:mm:ss nnnn INFO ONP State Change

Failed

Option: <option> Feature: <feature>

From state: <from state> Target state: <target state>

Reason: <reason>


VariableDescription


Variable Identifies the order code of the SOCoption that tried to change state, butfailed.

Feature 8 alphanumericcharacters

Variable Identifies the ID code of the featurethat requested the state change.

From state IDLE, IDLE TO ON,ON, ON TO IDLE,STATE ERROR oran integer followedby UNKNOWN

Variable Indicates the original state of theoperation and current state, becausethe operation failed.

Target state IDLE, IDLE TO ON,ON, ONTO IDLE,STATE ERROR oran integer followedby UNKNOWN

Variable Identifies the state to which theoption tried to change.




Description

Reason Mutual exclusionproblem

Variable Indicates an option that cannot workwith this option is turned ON. Thesystem cannot turn this option on.

Dependency error(uses loop ormemory shortage)

Variable Indicates an error in the SOCdatabase or code.

Required optionfailed transition.

Variable Indicates that another option failed tomake the change. The original optionrequires this option.

Option failedtransition.

Variable Indicates that the option did notchange state.

Internal error (checkSWER log)

Variable Indicates an internal error.

Not permitted to goto IDLE.

Variable Indicates the option tried to go fromthe ON state to the IDLE state. Thisis not permitted during ONP.

Not permitted to goto a transient state.

Variable Indicates the option tried to go to atransient state. The system neverallows this state.

Not a state or dualoption.

Variable Indicates that an option that is notstate-based attempted to set thestate of the option.

Not known feature Variable Indicates a feature that is not knowntried to change the state of theoption.

Option not correct forthis PCL.

Variable The option is not available for use inthe currently loaded productcomputing module load (PCL).

Active message exampleBASE_ALL04AN SOC510 JAN10 10:29:37 4394 INFO ONP StateChange Failed

Option: SOCOPT04 Feature: SOCFTR04

From State: IDLE Target State: ON

Reason: Required option failed transition


SOC510 231



SOC511The system generates SOC511 for each option that changes state. Theoption changes state because the option requested a state change. Theoption requested a state change to conform to the state of the optionbefore the one-night process (ONP).

Remedial actionn/a


FormatSOC511 mmmdd hh:mm:ss nnnn INFO ONP State Transition

Option: <option>

From state: <from state> To state: <to state>

Requesting Option: <option>

Reason: <reason>


VariableDescription

Option alphanumeric Variable Identifies the option that changedstate.

From state alphanumeric Variable Specifies the state of the optionbefore the option changed state.

To state alphanumeric Variable Specifies the current state of theoption.

Requesting option alphanumeric Variable Identifies the option that wanted tochange state.

Reason Needed by otheroption during datamove.

Variable Indicates that the option changedstate because another option thatdepends on this option wants tochange state.

Active message exampleSOC511 SEP05 18:14:33 5001 INFO ONP State Transition



Option: SOCOPT04

From state: IDLE To state: ON

Requesting option: SOCOPT05

Reason: Needed by other option during data move



SOC600The system generates SOC600 during the one-night process (ONP). Thesystem generates SOC600 when the SOC database transfers from the oldside to the new side. A feature on the old side must not transfer to the newside.

Remedial actionDetermine if the ONP step-by-step bulletins identify this information. If thebulletins identify this information, action is not required. If the information isnot present, contact Northern Telecom.


FormatSOC600 mmmdd hh:mm:ss nnnn INFO ONP feature data mismatch

Feature: <feature>

Reason: <reason>

State: <state>

SOC600 233



VariableDescription

Feature alphanumeric Variable Indicates the SOC feature identifier.Reason Feature is not

present in new PCL.The systemdiscarded data.

Variable Indicates that a feature registeredwith SOC before the ONP is notregistered with SOC now. Thesystem discarded data from beforethe ONP.

State alphanumeric Variable Indicates the state of the feature onthe old side.

Active message exampleSOC600 SEP05 18:14:33 5102 INFO ONP feature data mismatch

Feature: OLDFTRXX

Reason: Feature does not exist in new PCL, data has been

discarded

State: ON



SOC601The system generates SOC601 during a one-night process (ONP). Thesystem generates SOC601 when the SOC database transfers from the oldside to the new side. The old side is before the ONP. The new side is afterthe ONP. This log indicates that an old side option has not been registeredwith SOC on the new side. The system discarded the old side data.

An alarm for this log is not present.

Remedial actionDetermine if the one-night process (ONP) procedural bulletins identify thisinformation. If this information is present, action is not required. If theinformation is not present, contact your next level of support.




Formatload_name SOC601 mmmdd hh:mm:ss nnnn INFO ONP option datamismatch

Option: <option>

Reason: <reason>

State: <state>


VariableDescription


Variable Identifies the order code of the SOCoption to which the log applies.

Reason Option is not presentin new PCL. Thesystem discardeddata.

Variable Indicates the option identifierreceived from the old side has notbeen registered with SOC on the newside. The system discarded the oldside data.

Reason Service disabled innew PCL.

Variable Indicates the option identifierreceived from the old side is notregistered with SOC on the new side.The system discarded the old sidedata.

Service not correctfor new PCL.

Variable Indicates the option identifierreceived from the old side is NotApplicable. The capability is notavailable.

State IDLE, IDLE TO ON,ON, ONTO IDLE,STATE ERROR oran integer followedby unknown

Variable Indicates the state of the option onthe old side.

Active message exampleBASE_ALL04AN SOC601 JAN10 10:29:42 5203 INFO ONP option datamismatch

Option: OLDOPTYY

Reason: Option does not exist in new PCL,data has beendiscarded

State: ON

SOC601 235




SOC604The system generates log SOC604 when the software optionality control(SOC) database state and trouble ag for a feature is reset. The resetoccurs to match the value that the feature indicates. This is an information-only log.

Remedial actionn/a


FormatSOC604 mmmdd hh:mm:ss ssdd INFO SOC reset by feature


State: <state name>

Trouble: <YES or NO>


VariableDescription

INFO SOC reset byfeature

Constant Variable Indicates the reset of information inthe SOC database for the state andtrouble flag of the reported feature.The reset of information occurs tomatch the data that the featureindicates.

Feature eight alphanumericcharacter string

Variable This field contains the SOC featureidentifier.

State 14 alphanumericcharacter string

Variable Indicates the new state for thefeature. The state value can be oneof:

• IDLE

• ON

• IDLE TO ON




Description

• ON TO IDLE

• STATE ERROR

Trouble four alphanumericcharacter string

Variable Indicates if the feature has problems.The field value can be YES or No.

Active message exampleSOC604 JUN12 14:50:24 4577 INFO SOC reset by feature

Feature: AN0409__

State: ON

Trouble: NO



SOC605The system generates log SOC605 if the resolution of the level of resourceusage option differs from the resolution of the option. The SOC assumesthat the option is correct and updates the database.

Remedial actionThis log indicates damage of the SOC database. This log also indicatesthat the option allocated freed resources without a record. For additionalhelp, contact the next level of maintenance.


FormatSOC605 mmmdd hh:mm:ss nnnn INFO Current Usage Mismatch

Option: <option>

Recorded Usage: <recorded usage>

Actual Usage: <actual usage>

SOC record has been updated to reflect actual usage

SOC605 237



VariableDescription

Option alpha numeric Variable Specifies the order code of the optionto which this log applies.

Recorded Usage numeric Variable Specifies the best level of use of theoption. The SOC determines thislevel.

Actual Usage numeric Variable Specifies the level of use that theoption allocates. (The SOC assumesthis number is correct.)

Active message exampleSOC605 JAN10 10:29:45 5607 INFO Current Usage Mismatch

Option: SOCOPT04

Recorded Usage: 1000

Actual Usage: 1001

SOC record has been updated to reflect actual usage



SOC606Log SOC606 indicates that SOC discovered a usage warning thresholdthat is not legal during an audit. In response, the SOC reset the warningthreshold to the default.

Remedial actionThere is no immediate action required. The SOC corrects the limit to alegal value. To obtain another value, reset the warning threshold with theASSIGN THRESHOLD command.


FormatSOC606 mmmdd hh:mm:ss nnnn INFO Illegal Threshold



Option: <option>

Old Threshold: <old threshold>

New Threshold: <new threshold>

Threshold reset by SOC

Reason: <reason>


VariableDescription

Option alphanumeric Variable Specifies the order code of the SOCoption with a warning threshold thathas been reset.

Old Threshold numeric Variable Identifies the old (not permitted)threshold.

New Threshold numeric Variable Identifies the new threshold. The newthreshold is 100% for options with aMONITORED limit and 75% for allother options.

Reason Threshold must benon-negative

Variable Indicates that the threshold was notallowed because the threshold is anegative number.

Reason (cont.) Only 100% thresholdlegal with monitoredlimit

Variable Indicates the threshold is not allowedbecause the threshold is apercentage other than 100 and thelimit of the option is monitored.

Percentagethreshold must be<=100

Variable Indicates the threshold is not allowedbecause the threshold is apercentage greater than 100.

Active message exampleSOC606 JAN10 10:29:45 5708 INFO Illegal Threshold

Option: SOCOPT04

Old Threshold: 200%

New Threshold: 75%

Threshold reset by SOC

Reason: Percentage threshold must be <=100

SOC606 239




SOC607The system generates log SOC607 when Northern Telecom runs theRESET HIGHWATER command.

Remedial actionn/a


FormatSOC607 mmmdd hh:mm:ss ssdd INFO High Water Mark Reset

Option: <option>

Old High Water Mark: <old HWM>

New High Water Mark: <new HWM>


VariableDescription

Option alphanumeric Variable Identifies the option. The high watermark of this option was reset.

Old High Water Mark numeric Variable Specifies the old high water mark forthe option.

New High WaterMark

numeric Variable Specifies the new high water mark forthe option.

Active message exampleSOC607 SEP05 18:14:33 6011 INFO High Water Mark Reset

Option: SOCOPT04

Old High Water Mark: 1234

New High Water Mark: 5678





SOC800The system generates log SOC800 when the current use of an optionexceeds the warning threshold. For example, the system generates this logwhen the current use is 495, the threshold 500, and 10 more units wereallocated.

Remedial actionThere is no immediate action required. This log indicates when theresource use of this option nears the limit.


FormatSOC800 mmmdd hh:mm:ss nnnn INFO Usage Has Exceeded Threshold

Option: <option>

Usage: <usage>

Threshold:<threshold>

Limit: <limit>


VariableDescription

Option alphanumeric Variable Specifies the order code of the SOCoption with resources that exceed thewarning threshold.

Usage numeric Variable Specifies the new current use of theoption.

Threshold numeric Variable Specifies the warning threshold of theoption.

Limit numeric Variable Specifies the limit of use for thisoption.

Active message exampleSOC800 JAN10 10:29:48 6112 INFO Usage Has Exceeded Threshold

SOC800 241


Option: SOCOPT04

Usage: 5001

Threshold: 5000

Limit: 6000



SOC801The system generates log SOC801 when the use limit of an option hasbeen exceeded. An excess occurs when the use limit is soft. It also occurswhen an excess of the limit occurs during a data move. During a datamove, SOC allows an option to exceed a hard limit in order to avoid loss ofservice.

The SOC801 log indicates when the operating company exceeds the limitof MDC line capacity in the DMS-100. The order code for the SOC usecontrol option is MDC00058.

Remedial actionThere is no immediate action required. When the reason is "ExceedingHARD limit on INACTIVE processor," the option cannot have as manyresources allocated that the option has. Reduce usage or contact NorthernTelecom to purchase a higher limit.


FormatSOC801 mmmdd hh:mm:ss nnnn INFO Usage Has Exceeded Limit

Option: <option>

Usage: <usage> Limit: <limit>

Comment: <comment>




VariableDescription

Option alphanumeric Variable Specifies the order code of the SOCoption with a use that exceeds thelimit.

Usage numeric Variable Specifies the current use of theoption.

Limit numeric Variable Specifies the exceeded use limit.Reason Exceeds HARD limit

on INACTIVEprocessor

Variable Indicates that a hard limit wasexceeded on the inactive processor.This hard limit was probablyexceeded during a softwareapplication.

Exceeds SOFT limit Variable Indicates that soft limit wasexceeded.

Active message exampleSOC801 JAN10 10:29:49 6415 INFO Usage Has Exceeded Limit

Option: SOCOPT04

Usage: 10043 Limit: 10000S

Comment: Exceeding SOFT limit



SOC802The system generates this log when the use of an option exceeds2147483647, which is as high as SOC can count. The SOC continues toallow the allocation of resources. The SOC does not permit decrement ofresources because a number to subtract from is not present.

Remedial actionn/a


SOC802 243


FormatSOC802 mmmdd hh:mm:ss nnnn INFO Usage Has Overflowed

Option: <option>

Usage: over<max usage>

Comment: <comment>


VariableDescription

Option alphanumeric Variable Specifies the order code of the SOCoption with a use that exceeds theability of SOC to count.

Max usage 2147483647 Variable Indicates the highest amount of usethat SOC can record

Comment Additional useallowed but use willnot be recorded

Variable Indicates that SOC continues to grantrequests for more use, but cannotrecord the amount in use.

Active message exampleSOC802 JAN0 10:29:50 6516 INFO Usage Has Overflowed

Option: SOCOPT04

Usage: over 2147483647

Comment:Further usage is allowed but will not be recorded



SOC803The system generates this log when an option attempts to allocate more ofa resource. The SOC803 refuses this allocation to avoid an excess of theoption limit.

Remedial actionThere is no immediate action required. This log identifies a condition thatcan be important. This log indicates that the office cannot utilize more ofthis resource or count more of this event. For example, if the event is AINtriggers, reduction in AIN functionality can result until an increase in thelimit occurs.




FormatSOC803 mmmdd hh:mm:ss nnnn INFO Usage Request Refused

Option: <option>

Current Usage: <usage>

Request: <request>

Limit: <limit>

Granting this request would cause usage to exceed the limit


VariableDescription

Option alphanumeric Variable Specifies the order code of the SOCoption.

Usage numeric Variable Specifies the current usage for thisoption.

Request numeric Variable Specifies the additional units ofresource usage the option wants toallocate. This number plus thecurrent usage exceeds the limit.

Limit numeric Variable Specifies the limit of usage for thisoption.

Active message exampleSOC803 JAN10 10:29:51 6617 INFO Usage Request Refused

Option: SOCOPT04

Current Usage: 9995

Request: 10

Limit: 10000

Granting this request would cause usage to exceed the limit


SOC803 245



SOS100The Support Operating System (SOS) subsystem generates this reportwhen a DUMP command fails. Log SOS100 indicates a minor or majorfailure like a magnetic tape drive (MTD) that malfunctions.

Log history

(I)SN08

Added acntxt field value PREDUM to help file. First documented in (I)SN08for International and North American markets (CR Q00873806).

Remedial actionTake action to correct and reinitiate dump. The MAP (maintenance andadministration position) terminal from which the user issued the DUMPcommand gives additional information about the failure.


• Minor

• Warning

Format**SOS100 mmmdd hh:mm:ss ssdd INFO DUMP ERROR:

typtxt acntxt FAILURE ON CPUn


VariableDescription

INFO DUMP ERROR Constant Variable Indicates that the DUMP commandfailed.

typtxt ACTIVE, MATE,DEBUG, UNSAFE

Variable Indicates the type of dump

acntxt DUMP, CHECK ,PREDUM

Variable Indicates if failure occurred when thesystem checked or when the systemdumped.

FAILURE ON CPU 0, 1 Variable Identifies the CPU on which thedump failed



Active message example**SOS100 JUN04 13:28:49 3275 INFO DUMP ERROR:

ACTIVE DUMP FAILURE ON CPU1



SOS101The Support Operating System (SOS) subsystem generates this reportwhen a DUMP command executes correctly.

Remedial actionn/a


Format**SOS101 mmmdd hh:mm:ss ssdd INFO DUMP COMPLETE:

acntxt DUMP ON CPUn, hhhh BLOCKS, nn CORRECTIONS


VariableDescription

DUMP COMPLETE Constant Variable Indicates that the dump executescorrectly.

acntxt ACTIVE MATEDEBUG NOT SAFE

Variable Indicates type of dump.

DUMP ON CPUn CPUO, CPU1 Variable Indicates on which CPU the systemexecuted the dump.

hhhh Blocks 0000-FFFF Variable Indicates the number of blockswritten to the file.

hhhhCORRECTIONS

0000-FFFF Variable Indicates the number of correctionsthat occurred because of updates.

Active message example**SOS101 JUN04 13:26:07 2871 INFO DUMP COMPLETE:

ACTIVE DUMP ON CPU1, 6818 BLOCKS, 18 CORRECTIONS

SOS101 247




SOS102The Support Operating System (SOS) generates this log report. This reportrecords all inputs of the PRIORITY command. This report checks use thatis not authorized. A PRIORITY command operation is required if switchdiagnostics or measures that correct on a running switch cannot beperformed.

Remedial actionDetermine if use was authorized and if use was discontinued when nolonger necessary.


Format*SOS102 mmmdd hh:mm:ss ssdd INFO PRIORITY OPERATION: optxt

Priority : Priority:

User : User Logged

Device number : Users device


VariableDescription

PRIORITY STARTS, STOPS Variable Indicates if the user at this consolestarted or stopped the PRIORITYoperation over other CI processes.

USER 1-16 Variable characters Indicates the name ornumber of the user that performs thepriority on/off operation.

DEVICE NUMBER Device Number(0-1023), DeviceName (0-21characters)

Variable Indicates the device number and thename of the device that performs thepriority operation.

Active message example*SOS102 JUN04 12:56:25 4904 INFO PRIORITY OPERATION: STOPS



Priority : STARTS

User : ADMIN

Device number: 0, MAP



SOS103The Support Operating System (SOS) generates log SOS102 when anattempt to execute the command SETPRIV occurs. A privileged user canuse this command for full privileges on the terminal from which thisterminal works.

Remedial actionMake sure you use the command correctly to preserve the security of the24 switch.


Format*SOS103 mmmdd hh:mm:ss ssdd INFO SETPRIV OPERATION: optxt


VariableDescription

INFO SETPRIVOPERATION

Constant Variable Indicates that an attempt to use thecommand SETPRIV occurred.

optxt SET ON, FAILED Variable Indicates that the operation has beenset on, or failed (because of aninvalid password)

Active message example*SOS103 JUN04 12:57:26 5005 INFO SETPRIV OPERATION: SET ON


SOS103 249



SOS104The Support Operating System (SOS) generates SOS104. The log reportSOS104 indicates the number of software error (SWERR) reportsdiscarded in the previous ten minutes. This report indicates that aperipheral device does not behave normally. This report also indicates theassociated central message controller (CMC) input handler generates toomany SWERRs.

The SWERR reports that the CMC input handlers generate can ood thesystem. The CMC can generate multiple SWERRs in a minute, only one isallowed. The system discards additional SWERRs.

Remedial actionIf the system discards a large number of SWERR reports, informmaintenance support immediately.


FormatSOS104 mmmdd hh:mm:ss ssdd INFO DISCARDED SWERRS

nnn SWERRS DISCARDED IN PAST 10 MINUTES


VariableDescription

INFO DISCARDEDSWERRS

Constant Variable Indicates discarded SWERR reports.

nnn SWERRSDISCARDED INPAST 10 MINUTES

1-32,768 Variable Number of discarded SWERRs.

Active message exampleSOS104 JUN18 16:44:43 7400 INFO DISCARDED SWERRS

355 SWERRS DISCARDED IN PAST 10 MINUTES





SOS105The Support Operating System (SOS) generates SOS105. The log reportSOS105 indicates the number of software error (SWERR) reportsdiscarded in the previous ten minutes. This report indicates that aperipheral does not behave normally. This report also indicates theassociated central message controller (CMC) input handler generates toomany logs.

The SWERR reports that the CMC input handlers generate can ood thesystem. The CMC can generate multiple SWERRs in a minute, only one isallowed. The system discards additional SWERRs.

Remedial actionIf the system discards a large number of log reports, inform maintenancesupport immediately.


FormatSOS105 JUN18 16:44:43 7501 INFO DISCARDED LOGS

nnn LOGS DISCARDED IN PAST 10 MINUTES


VariableDescription

INFO DISCARDEDLOGS

Constant Variable Indicates discarded logs

nnn LOGSDISCARDED INPAST 10 MINUTES

1-32,768 Variable Indicates number of logs discarded

Active message exampleSOS105 JUN18 16:44:43 7501 INFO DISCARDED LOGS

363 LOGS DISCARDED IN PAST 10 MINUTES


SOS105 251



SOS106The subsystem for the Support Operating System (SOS) generatesSOS106 when the GUARANTEED_TERMINAL_CPU_SHARE officePARM changes.

Remedial actionn/a


FormatSOS106 mmmdd hh:mm:ss ssdd INFO OFFICE PARM CHANGED

GUARANTEED TERMINAL CPU SHARE SET TO n


VariableDescription

INFO OFFICE PARMCHANGED

Constant Variable Indicates that the GUARANTEEDTERMINAL CPU SHARE officePARM changes.

GUARANTEEDTERMINAL CPUSHARE SET TO n

Symbolic text Variable Indicates the new value of thisparameter.

Active message exampleSOS106 JUN27 10:07:33 0834 INFO OFFICE PARM CHANGED

GUARANTEED TERMINAL CPU SHARE SET TO 4



SOS107The Support Operating System (SOS) subsystem generates SOS107when the user enters or exits the EMERGENCY MODE. The subsystemalso generates this report when an invalid attempt to enter EMERGENCYMODE from a terminal occurs. The log also indicates why the system



returned to the NORMAL MODE (emergency mode exited). The systemreturns to NORMAL MODE because of a command entered from theterminal or from system action.

Remedial actionThe log report SOS107 is an information log. Monitor the logs to preventactivation of EMERGENCY MODE that is not authorized.


FormatSOS107 mmmdd hh:mm:ss ssdd INFO EMER_MODE

modtxt MODE actxt FROM DEV : n ***


VariableDescription

INFO EMER_MORE Constant Variable Indicates user enters or exitsEMERGENCY MODE, or an attemptto enter EMERGENCY MODE isinvalid.

modtxt NORMAL Variable Indicates user enters NORMALMODE (user exits EMERGENCYMODE).

EMERGENCY Variable Indicates entry of EMERGENCYMODE.

EMER Variable Indicates EMERGENCY MODE. Thesystem generates EMER state in thisfield when EMERGENCY MODEtimes out.

MODE ATTEMPTED Variable Indicates attempt to enterEMERGENCY MODE is invalid.

REQUESTED Variable Indicates request for EMERGENCYMODE.

REPEATED Variable Indicates user requestsEMERGENCY MODE from the sameterminal twice in a row.

ENTERED Variable Indicates activated EMERGENCYMODE if modtxt is EMERGENCY. Ifmodtxt is NORMAL, indicatesdeactivated EMERGENCY MODE.

SOS107 253



Description

EXTENDED Variable Indicates extended EMERGENCYMODE for another 15 min.

SYSTEM TIMEOUT:NORMAL MODEENTERED

Variable Indicates deactivated EMERGENCYMODE after a 15 to 20 min timeout.The system does not generate thedevice number when this messageappears.

n Integers Variable Indicates the device number of theterminal. Refer to table TERMDEV inthe customer data schema section oftheTranslations Guide.

Active message exampleSOS107 JAN01 09:18:06 1400 INFO EMER_MODE

EMERGENCY MODE ENTERED FROM DEV : 6 ***



SOS109The Support Operating System (SOS) subsystem generates SOS109when the user activates the REMOTE LOGIN feature.

The subsystem generates this log on Supernode-based DMS-Familyswitches ONLY. Log report SOS109 is an information log that records theuse of the REMOTE LOGIN feature. Use the REMOTE LOGIN feature toactivate command interpreter (CI) sessions on non-core nodes in thecentral office.

To activate remote CI sessions use the REMLOGIN command. Remote CIsessions are only for debugging purposes. This log tracks outages thatoccur as a result of commands that a user executes during a remote CIsession. These conditions cannot arise during normal maintenance fromthe central MAP.

Remedial actionn/a




FormatSOS109 mmmdd hh:mm:ss ssdd INFO REMOTE LOGIN: usernm

logged ltxt nodenm


VariableDescription

INFO REMOTELOGIN

Constant Variable Indicates a report of remote logonactivation.

usernm Symbolic text Variable Identifies the CI user, that thePERMIT command defines in theCM. The CI user initiates the remotelogon action.

nodnm Symbolic text Variable Identifies the node on which the CIuser sets up or terminates the remotelogon session See Table I.

ltxt OFF Variable Indicates that the CI user terminatesthe remote logon session.

INTO Variable Indicates that the CI user initiates theremote logon session.

Active message exampleSOS109 FEB17 14:34:37 7300 INFO REMOTE LOGIN: OPERATOR

logged into MS1



SOS110The Support Operating System (SOS) generates SOS110 when the dumpprogram fails to allocate store for update records. When the system cannotallocate store for the update records the system encounters a fatal errorand aborts the dump.

Remedial actionUse the CI commands "STORE SUMMARY" and "STORE USAGE" toobtain information on the store use. Contact the next level of maintenance.


SOS110 255


Format**SOS110 mmmdd hh:mm:ss ssdd INFO Dump error

Dump failed due to insufficient store


VariableDescription

INFO Dump error Constant Variable Indicated dump program fails.Dump failed causedby insufficient store

Constant Variable Indicates reason for the error.

Active message example**SOS110 JAN01 12:00:00 1234 INFO Dump error

Dump failed due to insufficient store



SOS111The Support Operating System (SOS) generates SOS111. The systemgenerates this report when a process reaches the limit of outgoingmessages the system can generate between suspensions.

Remedial actionLog SOS111 only appears if tools are loaded into the switch of theoperating company and debugging ags are on. When the systemgenerates log SOS111, contact the next level of maintenance. LogSOS111 is for Northern Telecom personnel.


FormatSOS111 mmmdd hh:mm:ss ssdd INFO Outgoing messages limitreached

Process: numbers (string) Limit: number

Msg: hex_msg



Traceback:

traceback_sequence


VariableDescription

Traceback Variable Variable Identifies software elements thathave faults on which the problemoccurs.

INFO Outgoingmessages limitreached

Constant Variable A message that indicates the processreaches an outgoing message limit.

Process Variable Variable Two hexadecimal numbers thatidentify a process that reaches theoutput message limit.

String Variable The ASCII equivalent of the Processnumeric identifier, in parentheses.

Limit Variable Variable An integer that indicates the processreaches the message limit.

Msg Variable Variable A hexadecimal translation of themessage Process sends whenprocess reaches limit.

Active message exampleSOS111 DEC05 18:14:33 4827 INFO Outgoing messages limit

reached

Process: #2107 #0001 (INVOKER) Limit: 50

Msg: 0123 0008 1F45 9876

Traceback:

OC9C1DB2=SISUTIL.AU03:SIS_CHEC+#018E

OB42C254=INVOKER.B001:SOS_INVO+#0AA8


SOS111 257



SOS120The Support Operating System (SOS) generates SOS120 when a staticrandom access memory (SRAM) action occurs. Each time an SRM repackoccurs, the system generates two SOS logs. The system generates a logbefore the repack starts and on completion of a successful repack. Thesystem also generates a log if the required repack cannot proceed. LogSOS120 provides the system time, the action, and the reason for theaction.

Remedial actionIf the SRAM repack status field states "MUTEX Problem" and the systemgenerates SOS120 daily, attempt to correct the problem. The user cantemporarily deactivate the tools, or remove the debug tracepoints to correctthe problem and allow the SRAM repack to proceed. Otherwise the usermust contact the next level of maintenance.


FormatCM SOS120 JAN01 10:38:29 0100 SRAM operation

<action> - <reason>


VariableDescription

<action> variable Variable Indicates SRAM repacking status<reason> variable Variable Indicates cause of SRAM action

Active message exampleCM SOS120 JAN01 10:38:29 0100 SRAM operation

Repacking started - USER REQUEST





SOS130The Support Operating System (SOS) generates SOS130 when more than90% of the control blocks (FCB) are allocated. If the FCBs run out,applications can fail. The applications fail when new users are not able tologin.

Remedial actionAn application can use all available FCBs. Examine FCB use with a toollike the international digital trunk controller (IDCT). Take the correct actionbased on these results.


FormatSOS130 mmmdd hh:mm:ss ssdd INFO FCB pool nearly empty


VariableDescription

INFO FCB poolnearly empty

Constant Variable Indicates that more than 90 % of theFCBs are allocated.

Active message exampleSOS130 MAR05 19:31:16 1404 INFO FCB pool nearly empty



SOS132The system generates SOS132 when SYSOAUD process audit determinesthe central processing unit (CPU) runs at an occupancy of more than 50%in the laboratory. This action does not allow any process of proschedclassSYSTEMO to run. This log gives a warning when SYSTEMO processes donot run in the laboratory.

The central processing unit status (CPUSTAT) provides information onCPU occupancies. The CPU occupancy is the ratio of real time used on afunction to the time allowed for a function. The CPU occupancy has apercentage value.

SOS132 259


The software operating system (SOS) scheduler uses scheduler classes toallocate CPU time in concurrent processes. A scheduler class is a group ofprocesses that perform related functions. The SOS requires detailedknowledge of the machine design. The SOS provides the means to createand start a process. The SOS assigns a process ID that identifies allprocesses.

Remedial actionRun the HOGCT tool to determine the process that overloads the CPU.The HOGCT tool computes total CPU time that all processes use inrelation to the work the processes perform.


FormatSOS132 mmmdd hh:mm:ss ssdd INFO General SOS Message


VariableDescription

INFO General SOSMessage

Constant Variable Indicates the messages betweencontrol component processors.

Active message exampleSOS132 SEP04 12:00:12 1300 INFO General SOS Message



SOS400The system generates the log report SOS400 when an image volume isrunning out of space. The log prints if the calculated free space is less than5% of the total volume space after the image completes. The purpose ofthis log is to give a warning that there is not enough future image space.

The size of the percentage of free space is relative to the size of thevolume.

Remedial actionThe system requires no immediate action. This log warns of a decrease ofimage volume space.




FormatSOS400 mmmdd hh:mm:ss ssdd INFO IMAGE VOLUME LOW

ON FREE SPACE

After taking the current image this volume

will have less than 5% free left.

Volume Name: <volume name>

Blocks Free: <blocks free>

Percent Free: <percent free>%


VariableDescription

volume name SLM volume name Variable The name of the SUM volume wherethe current image exists.

blocks free numeric Variable The number of blocks that areavailable after the image is taken.This number is calculated bysubtracting the image size from thecurrent free image blocks.

percent free percentage Variable The percentage of available volumespace after the image is taken. Thecalculation is the number of freeblocks divided by the total number ofavailable blocks and the resultmultiplied by 100.

Active message exampleSOS400 JAN12 14:00:15:6000 INFO IMAGE VOLUME LOW

ON FREE SPACE

After taking the current image this volume

will have less than 5% free left.

Volume Name: SOSDIMAGE0

SOS400 261


Blocks Free: 299874

Percent Free: 4%



SOS410The system generates log report SOS410 when the image dump processattempts to use the SDM as indicated in table IMGSCHED but the SDMcannot be accessed.

When the image dump process cannot access the SDM, the processcontinues to take an image without using the SDM, to make sure asuccessful image dump is completed. If the field USESDM is set to "Y" intable IMGSCHED for the next scheduled image dump, the next scheduledimage dump will try to use the SDM.

Remedial actionThe following list indicates the causes and actions for this error:

• SDM is not data lied. Either connect the SDM to the switch and data 11it in table SDMINV, or enter "N" in field USESDM in table IMGSCHED.

When field USESDM is set to N in table IMGSCHED, the SDM will not beused. The maximum 15 minute lockout time for recent changes does notapply when the SDM is not used.

• SDM not in service. Either return the SDM to service or enter "N" infield USESDM in table IMGSCHED.

When field USESDM is set to N in table IMGSCHED, the SDM will not beused. The maximum 15 minute lockout time for recent changes does notapply when the SDM is not used.

• Failed to get SDM fta =<reason>. Save all swerrs, MTS, and SOS logsand contact your next level of support.


FormatSOS410 mmmdd hh:mm:ss ssdd INFO SDM RESOURCES ERROR

The SDM cannot be used to assist with the current image dump



REASON: <reason>


VariableDescription

reason SDM not in service. Variable The SDM is not in service and couldnot be used.

SDM is not datafilled. Variable There is no SDM datafilled in tableSDMINV.

Failed to get SDM fta=<reason>

Variable There is a DMS software problem.

Active message exampleSOS410 JAN12 14:00:15 6000 INFO SDM RESOURCES ERROR

The SDM cannot be used to assist with the current image dump

REASON: SDM not in service



SOS411The system generates log report SOS411 when there is a communicationproblem between the image dump process and the SDM.

When the image dump process cannot access the SDM, the processcontinues to take an image without using the SDM, to make sure asuccessful image dump is completed. If the field USESDM is set to "Y" intable IMGSCHED for the next scheduled image dump, the next scheduledimage dump will try to use the SDM.

Remedial actionThe following list indicates actions for this error:

• If the SDM is out of service, return the SDM to service and confirm it'' ssoftware load is compatible with the CM.

• If the SDM is in service and it''s software load is compatible with theCM, there is a problem with the messaging between the DMS and theSDM. Save all swerrs, MTS, and SOS logs and contact your next levelof support.

SOS411 263



FormatSOS411 mmmdd hh:mm:ss ssdd INFO SDM MESSAGING ERROR

An error has occurred in the communication between the

image dump process and the SDM during an image dump.

REASON: <the messaging error>

EXPECTED: <what was expected>

RECEIVED: <what was actually received>


VariableDescription

reason character string Variable Text describing reason for failure.expected character string Variable Values that the software was

expecting.received character string Variable Values that the software received.

Active message exampleSOS411 JAN12 14:00:15 6000 INFO SDM MESSAGING ERROR

An error has occurred in the communication between the

image dump process and the SDM during an image dump.

REASON: failed to get new buffer at index 1

EXPECTED: waiting_for_ack to be false

RECEIVED: waiting_for_ack was true





SOS412The system generates log report SOS412 when there is a problem with thetransmission of the CM image dump block between the SDM le systemand the CM le system.

When the image dump process cannot access the SDM, the processcontinues to take an image to make sure a successful image dump iscompleted. If the field USESDM is set to "Y" in table IMGSCHED, the nextscheduled image dump will try to use the SDM.

Remedial actionConfirm that the SDM and CM le systems are operating correctly. Save allswerrs, SOS, SLM and MTS logs and contact your next level of support forthe SDM and CM.


FormatSOS412 mmmdd hh:mm:ss ssdd INFO SDM FILE SYSTEM ERROR

The SDM le system reported an error during the imagingprocess.

REASON: <le system error>


VariableDescription

reason character string Variable The reason indicates a problem withthe SDM.

Active message exampleSOS412 JAN12 14:00:15 6000 INFO SDM FILE SYSTEM ERROR

The SDM le system reported an error during the imagingprocess.

REASON: Failed to open CM image dump le on the SDM


SOS412 265



SOS602The system generates log report SOS 602 when the number of pools isunder 15. The maximum number of pool types allowed is 15. The systemgenerates this report for each pool type. Log report SOS602 does notreport the shortages for all pool types.

Use the pools utility to manage resources. The pools utility providesmanagement of ownership of resources like mail boxes and ags.

Remedial actionn/a


FormatSOS602 mmmdd hh:mm:ss ssdd INFO Too many pools allocated

Number of POOLTYPEID <pooltype_id> allocated is<no_allocated>

Maximum allowed is <max>


VariableDescription

pooltype_id nnnnn-nnnnn, wherennnnn is 000000 to32767

Variable Identifies the pool type for which thenumber of pools is under 15. Themaximum number of pools allowed is15.

no_allocated 0 to 255 Variable Indicates the number of poolsallocated to the pool type

max 0 to 255 Variable Indicates the maximum number ofpools allowed for the pool type

Active message exampleSOS602 SEP05 18:14:33 4827 INFO Too many pools allocated

Number of POOLTYPEID 00000-29545 allocated is 245

Maximum allowed is 255





SOS603The system generates log report SOS603. The system generates thisreport to indicate that an automated time-of-day (TOD) clock changeoccurs in the next 24 h. The automated TOD clock change associates withthe change to or from Daylight-Saving Time. The TOD clock changerequests are stored in table DSTTABLE.

Remedial actionIf the entry in the From_date or To_date field is not correct, correct thecorresponding entry in table DSTTABLE.

If the entries in the From_date and To_date fields are correct, there is noaction required.


FormatSOS603 <Date/time> INFO Time of Day Clock Changenotification

Automated Time of Day clock change request will occur on:<Date>

(table DSTTABLE)

The Time of Day clock will be changed

From: <From_date> To: <To_date>


VariableDescription

Date/time MMM DD hh:mm:ss Variable Indicates when the system generatesthe log report. The format is monthday hours:minutes:seconds

INFO Time of DayClock Changenotification

constant Variable Indicates that an automated TODclock change occurs in the next 24hours.

SOS603 267



Description

Automated Time ofDay clock changewill occur on:

constant Variable Indicates that an automated TODclock change occurs.

Date MMM DD, YYYY Variable The Date field indicates the date theTOD change occurs. The format ismonth day, year.

(table DSTTABLE) constant Variable Indicates the automated time changeis in table DSTTTABLE.

The Time of Dayclock will be changed

constant Variable Indicates that an automated TODclock change occurs.

From_date YYYY/MM/DDhh:mm:ss DAY

Variable Indicates the date, time, and day atwhich the TOD change occurs. Theformat is year/month/day, time, andday of the week.

To_date YYYY/MM/DDhh:mm:ss DAY

Variable Indicates the date, time, and dayafter the TOD change occurs.

Active message exampleSOS603 OCT 29 01:00:00 9700 INFO Time of Day Clock Changenotification

Automated Time of Day clock change request will occur on:OCT 30, 1996

(table DSTTABLE)

The Time of Day clock will be changed

From: 1997/10/30 01:00:00 SUN. To: 1997/10/30 00:00:00 SUN.



SOS604The system generates log report SOS605 to indicate that the systemdeleted all time-of-day (TOD) clock change requests. Manual actiondeleted the TOD clock change requests from table DSTTABLE.

Remedial actionThe system generates log report SOS604 to indicate that automated TODclock change requests are not available to process. To reactivate theautomated TOD change feature, enter requests in Table DSTTABLE.




• Minor

Format<alarm>SOS604 <Date/time> INFO DSTTABLE is empty.

Automated Time of Day change requests were deleted fromtable

DSTTABLE.

Automated Time of Day change feature is turned off.


VariableDescription

Alarm *(constant) Variable Indicates how severe the problem is.( *= minor)

Date/time MMM DD hh:mm:ss Variable Indicates when the system generatedthe log report. The format is monthday hours:minutes:seconds

INFO DSTABLE isempty

constant Variable Indicates that table DSTTABLE is notentered.

Automated Time ofDay change requestswere deleted fromtable DSTTABLE.

constant Variable Indicates that manual action deletedthe TOD change requests from tableDSTTABLE.

Automated Time ofDay change featureis turned off.

constant Variable Indicates that the automated TODchange feature is off.

Active message example*SOS604 OCT 29 01:00:00 9700 INFO DSTTABLE is empty.

Automated Time of Day change requests were deleted fromtable DSTTABLE.



SOS604 269



SOS605The system generates log report SOS605. The system generates thisreport to indicate that all automated time-of-day (TOD) clock changes intable DSTTABLE expire. The TOD clock changes expire when the systemuses all tuples in DSTABLE to implement automated time-of-day changes.

Remedial actionThe system generates log report SOS605 to indicate automated TOD clockchange requests that did not expire are not available to process. Toreactivate the automated TOD change feature, delete the expired requestsand enter new requests into table DSTTABLE.


• Minor

Format<alarm>SOS605<Date/time> INFO DSTTABLE is empty.

Automated Time of Day change requests have expired (table

DSTTABLE).



VariableDescription

Alarm *(constant) Variable Indicates how severe the problem is.( *= minor)

Date/time MMM DD hh:mm:ss Variable Indicates when the system generatesthe log report. The format is monthday hours:minutes:seconds

INFO DSTABLE isempty

constant Variable Indicates TOD change requests thatare not processed are not in TableDSTTABLE.




Description

Automated Time ofDay change requestshave expired (tableDSTTABLE)

constant Variable Indicates all TOD change requests intable DSTTABLE expire.

Automated Time ofDay change featureis turned off.

constant Variable Indicates that the automated TODchange feature is off.

Active message example*SOS603 OCT 29 01:00:00 9700 INFO DSTTABLE is empty.

Automated Time of Day change requests have expired (tableDSTTABLE).




SOS910The system generates log SOS910 via the MSCCSIST process when itsets the slave clock card busy after a five second time-out, if no messagesare received from MS Clock Maintenance Busy FSM during this timewindow.

The log can be viewed with the LOGUTIL CI command:CI

>LOGUTIL

LOGUTIL>OPEN SOS

Log history

SN08 (DMS)

Log SOS910 is generated by the MSCCSIST process when it receives themessages from the MS Clock Maintenance Busy FSM about the slaveclock card becoming busy. The new log is introduced by featureA00007487.

SOS910 271


Remedial actionThe slave card going busy causes the MS to go sys busy. In this case,follow the standard procedures for maintenance of a system busy MS.Check for a possible clock card failure.


• Major

Format<coffice identifier> <alarm severity> SOS910 mmmdd hh:mm:ssssdd <INFO> MSCCSIST process sets slave MS to bsy state

<data>


VariableDescription

OFFICE IDENTIFIER Character string VariableALARM SEVERITY MAJOR VariableINFO MSCCSIST process

sets slave MS to bsystate

Variable Event type

DATA MS 0 or MS 1 Variable

Active message exampleXA2_PPC21AR ** SOS910 SEP28 21:23:24 6630

MSCCSIST process sets slave MS to bsy state

MS 0



SOS911The system generates log SOS911, via the MSCCSIST process, when itreceives the messages from the MS Clock Maintenance Busy FSM aboutthe slave clock card becoming busy. Before this, MSCCSIST receives the



message from Report FSM to busy the slave. The process starts a fivesecond delay but it is interrupted by the message from Busy FSM. Theslave clock card is set busy immediately.


>LOGUTIL

LOGUTIL>OPEN SOS

Log history

SN08 (DMS)

Log SOS911 is generated by the MSCCSIST process when it receives themessages from the MS Clock Maintenance Busy FSM about the slaveclock card becoming busy. The new log is introduced by featureA00007487.

Remedial actionThe MS will go sys busy. In this case, follow the standard procedures formaintenance of a system busy MS. Check for a possible clock card failure.


• Warning

Format<office identifier> <alarm severity> MSCCSIST process setsMS bsy after repeated

request

<data>


VariableDescription

OFFICE IDENTIFIER Character string VariableALARM SEVERITY MAJOR Variable

SOS911 273



Description

INFO MSCCSIST processsets MS bsy afterrepeated request

Variable Event type



MSCCSIST process sets MS bsy after repeated request

MS 0



SOS912The system generates log SOS912, via the MSCCSIST process, when itreceives the messages from the MS Clock Maintenance Busy FSM aboutthe master clock card becoming busy. This means that the MSCCSISTprocess aborts the procedure to busy the slave. This way the MS Clocksystem is give a chance to recover. Switch of clock mastership happensand the previous slave becomes the master.


>LOGUTIL

LOGUTIL>OPEN SOS

Log history

SN08 (DMS)

Log SOS912 is generated by the MSCCSIST process when it receives themessages from the MS Clock Maintenance Busy FSM about the masterclock card becoming busy. The new log is introduced by featureA00007487.

Remedial actionThe MS will go sys busy. In this case, follow the standard procedures formaintenance of a system busy MS. Check for a possible clock card failure.




• Major

Format<coffice identifier> <alarm severity> SOS912 mmmdd hh:mm:ss

ssdd <INFO> MSCCSIST is aborted due to MS clock maintenance

action

<data>


VariableDescription

OFFICE IDENTIFIER Character string Variable ALARM SEVERITYMAJOR INFO Variable MSCCSIST is aborted due to MS

clock maintenance actionEvent type DATA Variable MS 0 or MS 1


MSCCSIST is aborted due to MS clock maintenance action

MS O



SOS913The system generates log SOS913 when the MS Clock MaintenanceReport FSM sends a message to the MSCCSIST process to busy theslave clock card as a result of DAC adjustment failure. MSCCSIST waitsfive seconds before it busies the slave clock card.


>LOGUTIL

SOS913 275


LOGUTIL>OPEN SOS

Log history

SN08 (DMS)

Log SOS913 is generated when the MS Clock Maintenance Report FSMsends a message to process MSCCSIST to busy the slave clock card as aresult of DAC adjustment failure. The new log is introduced by featureA00007487.

Remedial actionWhen this log is generated possible maintenance action will busy either themaster or slave clock card. This will cause the corresponding MS to go sysbusy. In this case follow the standard procedures for maintenance of asystem busy MS. Check for a possible clock card failure.


• Major

Format<office identifier> <alarm severity> SOS913 mmmdd hh:mm:ss

ssdd <INFO> MSCCSIST:MS Clock is set to ISTB

<data>


VariableDescription

OFFICE IDENTIFIER Character string VariableALARM SEVERITY MAJOR VariableINFO MSCCSIST:MS

Clock is set to ISTBVariable Event type



MSCCSIST:MS Clock is set to ISTB

MS O





SPC100The Semipermanent Connections (SPC) subsystem generates log reportSPC100. The subsystem generates this report when the system activatesa semipermanent connection through table control.

All SPC connections, except SPC connections that go through an RC02node, remain connected over a warm restart. For reloads and cold restarts,the system constructs the connections again, after the restart is complete.The system also constructs SPC connections again, after an XPMSWACT.

The SPC connections use nailed-up connections through the network.Office parameter MAXNUCS determines the maximum number of activeSPC connections allowed at a time.

The system cannot intraswitch SPC connections when the systemconducts traffic studies.

Remedial actionn/a


FormatSPC100 mmmdd hh:mm:ss ssdd INFO SPC ACTIVATED

AGENT1 cktid

AGENT2 cktid

CONNECT = cnectxt REASON = CONNECTION MADE

SPC100 277



VariableDescription

INFO SPCACTIVATED

Constant Variable Indicates that the system activated asemipermanent connection.

AGENT1 cktid Symbolic text Variable Circuit identification. Agents can beline equipment numbers (LEN), in theevent of a line; or CLLI + membernumbers, in the event of a trunk. Thetype of number depends on the typeof connection: line to line, trunk totrunk, line to trunk. Refer to table I forvalues.

AGENT2 cktid Symbolic text Variable Circuit identification. Agents can beline equipment numbers (LEN) in theevent of a line; or CLLI + membernumber, in the event of a trunk. Thetype of number depends on the typeof connection: line to line, trunk totrunk, line to trunk. Refer to Table Ifor values.

CONNECT N, Y Variable Indicates if the system can activate aconnection.

REASON =CONNECTIONMADE

Constant Variable Indicates the reason for a log report.

Active message exampleSPC100 JUL25 11:32:06 1203 INFO SPC ACTIVATED

AGENT1 LEN 00 0 01 12 DN 2222

AGENT2 LEN 00 0 01 13 DN 2223

CONNECT = Y

REASON = CONNECTION MADE



SPC101The Semipermanent Connection (SPC) subsystem generates log reportSPC101. The subsystem generates this report when the entries disconnecta semipermanent connection.



All SPC connections, except SPC connections that go through an RC02node, remain connected over a warm restart. For reloads and cold restarts,the system constructs the connections again, after the restart is complete.The system also constructs SPC connections again, after an XPMSWACT.

The SPC connections use nailed-up connections through the network.Office parameter MAXNUCS determines the maximum number of activeSPC connections allowed at a time.


Remedial actionThere is no action required. To restore the connection, change the value ofCONNECT to Y in table SPCCON.


FormatSPC101 mmmdd hhmmss ssdd INFO SPC DEACTIVATED

AGENT1 cktid

CONNECT = N

REASON = ADMIN DISCONNECT


VariableDescription

INFO SPCDEACTIVATED

Constant Variable Indicates that a change in the entriesdisconnects the SPC.

AGENT2 LEN Symbolic text Variable Agents can be a line equipmentnumber (LEN), in the event of a line;or CLLI+ member numbers, in theevent of a trunk. The type of numberdepends on the type of connection:line to line, trunk to trunk, line totrunk.

CONNECT Constant Variable Indicates that the system cannotactivate a connection.

REASON = ADMINDISCONNECT

Constant Variable Indicates that a change in the entriescauses a manual disconnect.

SPC101 279


Active message exampleSPC101 JUL25 11:32:12 1210 INFO SPC DEACTIVATED

AGENT1 LEN 00 0 01 13 DN 2223

CONNECT = N

REASON = ADMIN DISCONNECT



SPC102The Semipermanent Connections (SPC) subsystem generates log reportSPC 102. The subsystem generates this report when a semipermanentconnection fails because of an event other than an entry change.

All SPC connections, except SPC connections that through an RC02 node,remain connected over a warm restart. For reloads and cold restarts, thesystem constructs the connections again, after the restart is complete. Thesystem also constructs SPC connections again, after an XPM SWACT.

The SPC connections use nailed-up connections through the network.Office parameter MAXNUCS determines the maximum number of activeSPC connections allowed a time.


Remedial actionContact the next level of support.


Format.SPC102 mmmdd hh:mm:ss ssdd INFO SPC FAILURE

AGENT1 cktid

AGENT2 cktid

CONNECT = Y



REASON = REASON FOR FAILURE


VariableDescription

INFO SPC FAILURE Constant Variable Indicates that a SPC fails because ofan event other than an entry change.

AGENT1 Symbolic text Variable Agents can be line equipmentnumbers (LEN) or directory number(DN), in the event of a line; or CLLI+member numbers, in the event of atrunk. The type of number dependson the type of connection: line to line,trunk to trunk, line to trunk.

AGENT 2 Symbolic text Variable Agents can be line equipmentnumber or directory number in theevent of a line; CLLI+ membernumbers, in the event of a trunk. Thetype of number depends on the typeof connection: line to line, trunk totrunk, line to trunk.

CONNECT=Y Constant Variable Indicates that the system can activatea connection.

REASON FAILEDCONNECTION

Variable Indicates the state of one or both ofthe agents in the SPC changes fromSEIZED.

AGENT FAILED Variable Indicates one or both of the agents inthis SPC requires interrogation.

UNKNOWN Variable Indicates reason for failure of SPC isnot known.

Active message exampleSPC102 JUL25 11:34:12 1230 INFO SPC FAILURE

AGENT1 LEN 00 0 01 12 DN 2222

AGENT2 LEN 00 0 01 13 DN 2223

CONNECT = Y

REASON = FAILED CONNECTION


SPC102 281



SPM633The SPM633 log is generated when a REX test on an SPM is successful.

Node 500 logs will be reported for state changes on the CEM during REXtest.

Remedial actionn/a


FormatSPM 633 <mmmdd hh:mm:ss> <ssdd> INFO SPM REX Success

SPM: <spm_number> Type: <spm_variant>

REX test successful


VariableDescription

SPM REX Success Constant Variable Indicates that the REX test on theSPM node was successful.

Node type Constant, SPM Variable Indicates that the node type for thislog is SPM.

Node Number Integer (0-85) Variable SPM numberType alphanumeric string

upto 6 chars long.{DMSCP, MG4K, IW,DPT}

Variable Indicates the variant of the SPM.

REX test successful Constant Variable Shows that the REX test on thereported SPM was successful.

Active message exampleSPM633 JAN24 01:57:54 2112 INFO SPM REX Success

SPM: 0 Type: SMG4

REX test successful.





SPM690This log is generated when the XA-Core receives BootP requests from aBootP suppressed node. It indicates that the XA-Core has received aBootP request from the CEM of the MG4000. This means that the edgerouter is not correctly configured and has its BootP forwarding enabled.

Remedial actionCheck the router configuration for the MG4000. It may have BootPforwarding enabled in the edge router.


Format<Switch_name> SPM690 mmmdd hh:mm:ss ssdd INFO BOOTPSUPPRESSED REPORT

Warning : Unexpected BootP MSG on BootP suppressed node

Action : Check network Configuration at remote MG4000

Location: <PM_type><PM_number> Type: <SPM_class> Fabric:<SPM_fabric>


VariableDescription

Switch_name Char string Variable Gives the switch name.Warning Char string Variable Describes the problem.Action Char string Variable Suggests any action to be taken.PM_type SPM Variable Peripheral module type.PM_number 0-85 Variable Peripheral module number.SPM_class SMG4 Variable The variant of SPM. This is not

applicable to DMSCP and IW SPMs.SPM_fabric IP, ATM or UNK Variable The network fabric type.

SPM690 283


Active message exampleMSH206BE SPM690 FEB10 06:28:39 2021 INFO BOOTP SUPPRESSREPORT

Warning : Unexpected BootP Msg on BootP suppressed node

Action : Check network configuration at remote MG4000

Location: SPM 10 Type: SMG4 Fabric: ATM



SPRF670The SPRF670 log represents the data from the past 15 samples from theSPM. The data is for the SPM activity (SPMACT) subtool.

Start the SPRF670 log from the SPERFORM process.

Remedial actionn/a


FormatSPRF 670 mmmdd hh:mm:ss ssdd INFO SPMACT_DATA


VariableDescription

TONE 0 to MAX Variable Resources in use during a particularminute

SUMMARY Numeric Variable Average of the samplesMFAVAIL Numeric Variable Highest number of MFs availableDTMFAVAIL Numeric Variable Highest number of DTMFs availableECANAVAIL 0 to MAX Variable ECAN resources available for the

SPM node.




Description

COTAVAIL 0 to MAX Variable COT resources available for the SPMnode. TONEAVAIL 0 to MAXResources available for the SPMnode.

MFHIGH Numeric Variable Highest number of MFs used duringthe 15 samples period

DTMFHIGH Numeric Variable Highest number of DTMFs usedduring the 15 samples period

ECANHIGH 0 to MAX Variable Maximum usage of ECAN resourcesfor the SPM node

COTHIGH 0 to MAX Variable Maximum usage of COT resourcesfor the SPM node

TONEHIGH 0 to MAX Variable Maximum usage of TONE resourcesavailable for the SPM node

CEMSYS Numeric Variable System class occupancyCEMAPP Numeric Variable Application occupancyCEMBAK Numeric Variable Background class occupancyORIG Numeric Variable OriginationsTERM Numeric Variable TerminationsMF Numeric Variable Multi frequency in useDTMF Numeric Variable Dual tone multi frequency in useECAN 0 to MAX Variable ECAN resources in use during a

particular minuteCOT 0 to MAX Variable Resources in use during a particular

minute

Active message examplePSWC SPRF670 SEP23 17:38:01 3800 INFO SPMACT_DATA

SPM 0 Load Name: CEM0011

CEMSYS CEMAPP CEMBAK ORIG TERM

1: 0% 0% 98% 0 0

2: 0% 0% 98% 0 0

3: 0% 0% 97% 0 0

4: 1% 0% 97% 0 0

5: 1% 0% 97% 0 0

SPRF670 285


6: 0% 0% 98% 0 0

7: 0% 0% 98% 0 0

8: 2% 0% 96% 0 0

9: 0% 0% 98% 0 0

10: 0% 0% 98% 0 0

11: 0% 0% 98% 0 0

12: 0% 0% 98% 0 0

13: 0% 0% 98% 0 0

14: 0% 0% 98% 0 0

15: 0% 0% 98% 0 0

SUMMARY 0% 0% 98% 0 0

MF DTMF ECAN COT TONE

1: 0 0 0 0 0

2: 0 0 0 0 0

3: 0 0 0 0 0

4: 0 0 0 0 0

5: 0 0 0 0 0

6: 0 0 0 0 0

7: 0 0 0 0 0

8: 0 0 0 0 0

9: 0 0 0 0 0

10: 0 0 0 0 0

11: 0 0 0 0 0

12: 0 0 0 0 0

13: 0 0 0 0 0



14: 0 0 0 0 0

15: 0 0 0 0 0

SUMMARY 0 0 0 0 0

SUMMARY MFAVAIL: 32 DTMFAVAIL: 82 MFHIGH: 0 DTMFHIGH: 0

ECANAVAIL 16 ECANHIGH 0 COTAVAIL 32 COTHIGH 0

TONEAVAIL 32 TONEHIGH 0



SPRF671The SPRF 671 log displays the data from the past 15 samples from theSPM. The data is for the SPM USAGE(SPUSAGE) subtool.

Start the logs from the SPERFORM process.

Remedial actionn/a


FormatSPRF671 mmmdd hh:mm:ss ssdd INFO SPUSAGE_DATA


VariableDescription

ABDN Numeric Variable Abandon messageEXIT Numeric Exit

messageVariable

CONF Numeric Variable Confusion messageREL_CAL Numeric Variable Release call messagesTX_FAIL Numeric Variable Transmit fail messagesNET_PAR Numeric Variable Parity error count messagesNET_INTG Numeric Variable Network integrity lost messages

SPRF671 287



Description

NET_FND Numeric Variable Network integrity found messagesNET_NFND Numeric Variable Network integrity not found

messagesDTMF_DNY Numeric Variable Dual Tone Multi Frequency Deny

messagesMF_DNY Numeric Variable Multi Frequency Deny messagesECAN_DNY 0 to MAX Variable ECAN allocation denied during a

particular minuteCOT_DNY 0 to MAX Variable COT allocation denied during a

particular minuteTONE_DNY 0 to MAX Variable TONE allocation denied during a

particular minute

Active message examplePSWC SPRF671 SEP23 17:38:01 9651 INFO SPUSAGE_DATA

SPM 0 Load Name: CEM0011

ABDN EXIT CONF REL_CAL TX_FAIL NET_PAR NET_INTG NET_FNDNET_NFND

1: 0 0 0 0 0 0 0 0 0

2: 0 0 0 0 0 0 0 0 0

3: 0 0 0 0 0 0 0 0 0

4: 0 0 0 0 0 0 0 0 0

5: 0 0 0 0 0 0 0 0 0

6: 0 0 0 0 0 0 0 0 0

7: 0 0 0 0 0 0 0 0 0

8: 0 0 0 0 0 0 0 0 0

9: 0 0 0 0 0 0 0 0 0

10: 0 0 0 0 0 0 0 0 0

11: 0 0 0 0 0 0 0 0 0

12: 0 0 0 0 0 0 0 0 0



13: 0 0 0 0 0 0 0 0 0

14: 0 0 0 0 0 0 0 0 0

15: 0 0 0 0 0 0 0 0 0

SPRF 671 SEP23 17:38:01 9651 INFO SPUSAGE_DATA

DTMF_DNY MF_DNY ECAN_DNY COT_DNY TONE_DNY

1: 0 0 0 0 0

2: 0 0 0 0 0

3: 0 0 0 0 0

4: 0 0 0 0 0

5: 0 0 0 0 0

6: 0 0 0 0 0

7: 0 0 0 0 0

8: 0 0 0 0 0

9: 0 0 0 0 0

10: 0 0 0 0 0

11: 0 0 0 0 0

12: 0 0 0 0 0

13: 0 0 0 0 0

14: 0 0 0 0 0

15: 0 0 0 0 0



SRC400The system recovery controller (SRC) system generates log reportSRC400. The system generates this report when initialization of a servicecomponent software occurs for level 1 to level 4.

SRC400 289


Remedial actionn/a


FormatSRC400 mmmdd hh:mm:ss ssdd INIT

Service: <service_component> <sos_node>

Reinit level: <reinit_level>

Duration: <time>

Reinit reason: <reinit_reason>

Impact: <impact_statement>


VariableDescription

service_component Character string Variable Indicates the identification of aservice component

sos_node Character string Variable Indicates the node of the supportoperating system (SOS)

reinit_level 1-4 Variable Indicates the level of reinitializationtime Character string of

h:min:sVariable Indicates the time taken to reinitialize

reinit_reason Character string Variable Indicates the reason for thereinitialization

impact_statement Character string Variable Indicates the impact of thereinitialization

Active message exampleSRC400 FEB07 08:15:36 1800 INIT

Service: CallP Base (CM)

Reinit level: 1

Duration: 00:00:00.089

Reinit reason: System initiated reinit



Impact: Loss of call originations for 00.069 sec



SRC500The system generates log SRC500 during core restart and norestart-swactto indicate the progress of system recovery controller (SRC) recoverystatus.

Remedial actionn/a


FormatSRC500 mmmdd hh:mm:ss ssdd INFO SRC Progress

Report SRC action in progress: <src_action>

<number> percent done, with <numobj> object<s> to recover.


VariableDescription

src_action Character string Variable Current SRC action.number 33, 67, 100 Variable Percentage of objects in the SRC

object database recovered by SRCwhen the system generates the log.

numobj 0-10240 Variable Total number of objects in the SRCobject database that the SRCrecovers when the system generatesthe log.

Active message exampleSRC500 MAR18 15:40:23 6600 INFO SRC Progress Report

SRC action in progress: Core Restart

100 percent done, with 0 object to recover

SRC500 291




SRC510This log is generated whenever SRC times out waiting to recover someobjects during a core restart or norestart-swact. (Note the variant parts inthe examples.)

Remedial actionCraft should apply usual manual actions to recover the out-of-servicenodes.


FormatSRC510 mmmdd hh:mm:ss ssdd INFO SRC Progress Report

SRC action timed out: <src_action>

<percent> percent done, with a total of <num_obj> object<s>

to recover.

<callpblock>

<callpblock> ::= <nocallpmsg> <callp_classlist>

<no_callp_obj_msg> ::= No unrecovered Callp_pm class object.

<callp_classlist> ::=

Callp Class Number of unrecovered Callp objects

TM_x: <num_obj>

DCM_x: <num_obj>

LM_x: <num_obj>

LGC_x: <num_obj>

RCC_x: <num_obj>




VariableDescription

src_action text Variable Current SRC actionpercent 0 to 100 Variable Percentage of objects in the SRC

object database recovered by SRC atthe time of the log.

num_obj integer Variable Total number of objects in the SRCobject database that have not beenrecovered at the time of the log.

no_callp_obj_msg text Variable This message is printed if there areno callp_pm class objects still waitingto be recovered when SRC timed out.This is mutually exclusive with thevariant part callp_classlist.

callp_classlist text Variable This portion of the message is printedif there are callp_pm class objectsstill waiting to be recovered whenSRC timed out. This is mutuallyexclusive with the variant partno_callp_obj_msg and has 1 outputline per callp_pm class registeredwith SRC.

Active message exampleSRC510 MAR18 16:07:40 0700 INFO SRC Progress Report

SRC action timed out: Core Restart

79 percent done, with a total of 4 objects to recover.

Callp Class Number of unrecovered Callp objects

TM_C: 2

DCM_C: 0

LM_C: 0

LGC_C: 0

RCC_C: 1

SRC510 MAR19 19:07:42 0060 INFO SRC Progress Report

SRC action timed out: Core Restart

80 percent done, with a total of 3 objects to recover.

SRC510 293


No unrecovered Callp_pm class object.



SRC520The system generates SRC520 to indicate an important event in thesystem recovery controller (SRC). The system generates this log when theevents that follow occur:

• the rst time the Dependency Manager Fail-Safe Process starts after acore restart.

• a restart or norestart-swact completes or times out while the SRCconcurrency limit was reached during the recovery.

• a service part passes a test.

• the system detects a software class disabled for fault recovery. Thesoftware class activates again in 24 h.

• the software maintenance query object procedure fails.

• the Group Manager Audit finds a difference between the GroupManager database and the Name Server.

Remedial actionn/a


FormatSRC520 mmmdd hh:mm:ss ssdd INFO SRC Status Report

<statustxt>


VariableDescription

statustxt Character string Variable Status message.

Active message exampleSRC520 MAR18 16:07:50 0800 INFO SRC Status Report

Dependency FailSafe Process is started





SRC620The subsystem generates log SRC620 when the system detects one of thefollowing conditions:

• a condition that is not expected.

• a condition that requires analysis.

This condition occurs in the system recovery controller (SRC). The SRCcontinues to operate with the problem condition. The subsystem generatesSRC620 when the events that follow occur:

• the system detects an SRC request timeout.

• an application aborts an SRC request.

• an SRC object stays in the initiate-required state for too long. TheDependency Manager Fail-Safe Process detects the SRC object.

Remedial actionn/a


FormatSRC520 mmmdd hh:mm:ss ssdd INFO SRC Status Report

Procedure <procname>,

Encountered: <message>

While working on object: <gridname>,

<classlabel>: <obj_class>

<actionlabel> <src_internal_action>

Tag: <hexnumber>

SRC620 295



VariableDescription

procname Character string Variable Name of the procedure thatgenerates this log.

message Character string Variable Internal SRC cause to generate thislog.

gridname Character string Variable Name of the object.obj_class Character string Variable Class name of object.src_internal_action Character string Variable Current SRC action.hexnumber 0B00, 20B5, 3200,

3201Variable The SRC development group uses

hexnumber internally to indicatewhere the system generates the log.

Active message exampleSRC620 MAR21 13:27:30 9600 INFO SRC Trace Log

Procedure SRCBASEI::handle_timeout,

Encountered: obj timed out waiting for completion

While working on object: Test 1, of Class: NEWAPPL_C

SRC action: Core_Restart

Tag: 20B5



SRC640The subsystem generates log SRC640 when the system detects acondition that is not expected. This condition is in the system recoverycontroller (SRC) system. The system generates SRC640 in place ofSRC620. The replacement occurs when the system prints an integer valuewith the object name and procedure name. The system uses SRC620under the following conditions:

• a system fails to delete an object from an auxiliary group during a givenphase of an SRC group request. This given phase is the groupingphase.

• application phase advance procedure returns a code that is not acorrect return code.



Maintain a record of the log during a power failure. Contact the next levelof maintenance.

Remedial actionn/a


FormatSRC640 mmmdd hh:mm:ss ssdd INFO SRC Trace Info

<procname_str>

Object Name <gridname>

<label> : <number>

Tag : <hexnumber>


VariableDescription

proname_str Character string Variable Indicates the name of the procedurethat generates this log and indicateswhy the system generates the log.

Object Name Character string Variable Indicates the name of the object.label number Character string Variable Indicates the value of the field

printed.Tag hexnum Character string Variable Indicates the hexadecimal that the

SRC development group usesinternally to indicate where systemgenerates the log.

Active message exampleSRC640 MAR21 12:53:07 7100 INFO SRC Trace Info

Phase advance failed

Object Name: MTM 4

Phase Num : 1 Tag : 20F1


SRC640 297



SRC660The system recovery controller (SRC) generates this report when thetarget of a service component returns a code that is not expected.

Maintain a record of the log during a power failure. Contact the next levelof support.

Remedial actionn/a


FormatSRC660 mmmdd hh:mm:ss ssdd INFO Bad return code


Target: <target>

Return code: <return_code>


VariableDescription

service_component Character string Variable Indicates the identification of aservice part.

sos_node Character string Variable Indicates the node of the supportoperating system (SOS).

target Character string Variable Indicates that the target of a servicecomponent returns a code that is notexpected.

return_code Character string Variable Indicates the code returned by theservice part. This code is the returncode that is not expected.

Active message exampleSRC660 MAR18 15:40:23 7400 INFO Bad return code


Target : Abort



Return code: Failed



SRC661The system recovery controller (SRC) generates this report when thesystem aborts or times out a maintenance action.

Maintain a record of the log during a power failure. Contact next level ofsupport.

Remedial actionn/a


FormatSRC661 mmmdd hh:mm:ss ssdd INFO Unexpected event


Action: <mtc_action>

Event: <event>

Reason: <reason>


VariableDescription

service_component Character string Variable Indicates the identification of aservice part.

sos_node Character string Variable Indicates the node of the supportoperating system (SOS).

mtc_action Character string Variable Indicates the maintenance action inprogress while the abort or timeoutoccurs.

SRC661 299



Description

event Character string Variable Indicates if the system aborted themaintenance action or a timeoutoccurred.

reason Character string Variable Indicates the cause of the abort.

Active message exampleSRC661 MAR18 15:40:23 7400 INFO Unexpected event


Action: Deloading Event : Timeout

Reason: -



SSR600The Switch Status Report Generator feature implements the Switch StatusReport (SSR) log. The Switch Status Report Generator feature providesthe ability to customize log reports from a base of OM calculations. Thesystem generates the default log report SSR600 every 15 min. The systemprovides one accurate log on different aspects of switch status.

The SSR600 log can appear in a long format that includes text descriptionsfor each field. To access the SSR commands, type:

Remedial actionCheck the data in the SSR600 log. Compare current values to previousvalues and average values to determine if service loss conditions arepresent.


• Warning

FormatSSR600 MMMDD hh:mm:ss 6408 INFO Switch Status Report



Current Data reported from MMMDD hh:mm to MMMDD hh:mm

00:15 00:15 00:15 00:15

00:15 00:15

NAME CURR PREV AVG NAME CURR

PREV AVG

------------------------------------------------------------------

LABEL_1: <VALUE> <VALUE> <VALUE> LABEL_2: <VALUE> <VALUE><VALUE>



. . .

------------------------------------------------------------------

TRK_LOW_1: <CLLI> XX TRK_LOW_2: <CLLI> XX

------------------------------------------------------------------

CM: <STATUS> MS: <STATUS> IOD: <STATUS> Net: <STATUS>

PM: <STATUS> CCS: <STATUS> Lns: <STATUS> Trks: <STATUS>

Ext: <STATUS> APPL :<STATUS>


VariableDescription

CP_OCC_PCT numeric Variable Indicates CPU status Call Processingoccupancy.

TOTAL_ORIG numeric Variable Indicates combined total number ofline and trunk originations.

CURR numeric Variable Current value of optional user definedparameter for the last 15 minuteinterval.

SSR600 301



Description

ORIG_CHG numeric Variable Indicates the percent changebetween reporting periods.

C7MSU_TX numeric Variable Indicates number of CCS7 MSUstransmitted and terminated. Thenumber must equal C7MSU_RX.

PSIG_PDIL numeric Variable Indicates combined total number ofpermanent signal and part dialconditions encountered.

C7RS_ERR numeric Variable Indicates number of CCS7 routesetactivities and failures.

PREV numeric Variable Previous value of optional userdefined parameter. The valueprovides information on the previous15 minute interval.

SWER_LOGS numeric Variable Indicates number of SWER logs.NONCP_TRAP numeric Variable Indicates number of CPU traps. The

number does not include CP softwaretraps.

CALL_CAP numeric Variable Indicates call processing classutilization of the compact PCIplatform

CPU_LOVERLD numeric Variable Indicates number of minutes of CM(CC) overload.

SYSB_PM numeric Variable Indicates number of PM changes toSYSB that did not go to CBSY first.

LINE_ORIG numeric Variable Indicates number of line originations.BLKD_CPRES numeric Variable Indicates number of calls blocked

because not enough call processing(CP) resources are available.

C7MSU_RX numeric Variable Indicates number of CCS7 MSUsreceived and originated. The numbermust equal C7MSU_TX.

DROPPED numeric Variable Indicates number of established callsthat the system dropped.

1TRIALFAIL numeric Variable Indicates number of first trial failures(no network path).

DLY_PER10K numeric Variable Indicates number of dial tone delaysfor each group of 10000 delays.

CP_SUICIDE numeric Variable Indicates number of call processingdetected software errors.

C7LINK1_ERR numeric Variable Indicates combined total number ofCCS7 link syncs and link errors.




Description

PM_OVERLD numeric Variable Indicates the number of calls deniedbecause of peripheral module (PM)overload.

MANB_PM numeric Variable Indicates number of PM changes toMANB from IS or ISTB.

AMA_RECS numeric Variable Counts number of automaticmessage accounting (AMA) recordsgenerated.

INTER_OFC numeric Variable Indicates number of line to trunkcalls.

TANDEM numeric Variable Indicates number of trunk to trunkcalls.

AVG numeric Variable Average value of optional userdefined parameter. Computed as thegathered average for that hour onthat day of the week divided by four.To produce quarter-hour values,divide the gathered average of thehour by four.

CP_TRAPS numeric Variable Indicates number of call processingsoftware traps.

BLKD_MISC numeric Variable Indicates total number of callsblocked for all other causes. Thisnumber does not include callsblocked because not enough callprocessing resources (CP) areavailable.

XACORE_CPC numeric Variable Indicates call processing classutilization of the XACore platform

TRK_INC numeric Variable Indicates number of trunkoriginations.

INTRA_OFC numeric Variable Indicates number of line to line calls.TOTAL_TERM numeric Variable Indicates combined total number of

line and trunk terminations.TRK_LOW_2 alphanumeric Variable CLLI of the trunk with the second

largest number of failures.TRK_LOW_1 alphanumeric Variable CLLI of the trunk with the most

failures.

Active message exampleExample of XA-Core SSR600 log:

SSR600 303


SSR600 MAY06 07:17:00 5600 INFO Switch Status Report

Current data reported from MAY-06 7:02 to MAY-06 7:17

00:15 00:15 00:15 00:15 00:15 00:15

Name CURR PREV AVG Name CURR PREV AVG

-----------------------------------------------------------------------

TOTAL_TERM: 0 0 0 BLKD_CPRES: 0 0 0

TOTAL_ORIG: 1 1 1 BLKD_MISC: 1 1 1

TRK_INC: 0 0 0 DROPPED: 0 0 0

LINE_ORIG: 1 1 1 CP_TRAPS: 0 0 0

TANDEM: 0 0 0 CP_SUICIDE: 0 0 0

INTER_OFC: 0 0 0 1TRIALFAIL: 0 0 0

INTRA_OFC: 0 0 0 CPU_OVERLD: 0 0 0

PSIG_PDIL: 0 0 0 PM_OVERLD: 0 0 0

XACORE_CPC: 0 0 0 SYSB_PM: 0 0 0

XA_NCPTRAP: 0 0 0 MANB_PM: 0 0 0

SWER_LOGS: 0 0 0 C7MSU_TX: 116 116 323

C7LNK1_ERR: 102 93 39 C7MSU_RX: 116 116 323

C7RS_ERR: 270 270 270 AMA_RECS: 0 0 0

ORIG_CHG: 0 0 0

-----------------------------------------------------------------------

TRK_LOW_1: DTCSPM0S7IBTO 0 TRK_LOW_2: M1PBXSPM0PRN 0

-----------------------------------------------------------------------

XAC: Split / MS: RExByp/ IOD: AMA E/ Net: 34PSLk/

PM: 4LIU7/*C* CCS: 3 RS/*C* Lns: SYSB / Trks: 7CCd/*C*



Ext: 1 Min/ APPL: SDM +/*C*

Example of Compact PCI SSR600 log:

SSR600 FEB22 15:02:00 0300 INFO Switch Status Report

Current data reported from FEB-22 14:47 to FEB-22 15:02

00:15 00:15 00:15 00:15 00:15 00:15

Name CURR PREV AVG Name CURR PREV AVG

-----------------------------------------------------------------------

TOTAL_TERM: 12242 78266 16454 BLKD_CPRES: 0 0 0

TOTAL_ORIG: 77789 78003 34063 BLKD_MISC: 8 5 2725

TRK_INC: 77789 78003 34063 DROPPED: 0 0 0

LINE_ORIG: 0 0 0 CP_TRAPS: 0 0 0

TANDEM: 77789 78003 34063 CP_SUICIDE: 0 0 0

INTER_OFC: 0 0 0 1TRIALFAIL: 0 0 0

INTRA_OFC: 0 0 0 CPU_OVERLD: 0 0 0

PSIG_PDIL: 0 0 0 PM_OVERLD: 0 0 0

CALL_CAP: 24 23 6 SYSB_PM: 0 0 0

MANB_PM: 0 0 0 SWER_LOGS: 0 0 0

C7MSU_TX: 0 0 0 C7LNK1_ERR: 0 0 0

C7MSU_RX: 0 0 0 C7RS_ERR: 0 0 0

AMA_RECS: 17850 17782 6479 ORIG_CHG: 0 0 0

-----------------------------------------------------------------------

TRK_LOW_1: AKRSAGEES 6 TRK_LOW_2: LDEAIN1LDT5 2

-----------------------------------------------------------------------

SSR600 305


IOD: . / PM: . / CCS: 1 PCC /*C* Lns: . /

Trks: 2C../*C* Ext: . / APPL: . /


Associated OM registersFormulas depend on OMs. See separate formulas for each field todetermine the associated OM registers.

STOR101The Store (STOR) subsystem generates this report when a request forstorage occurs. The storage is greater than the maximum amountaccepted for a module entered in Table DSlimit. The manufacturer entersdata in Table DSlimit before delivery.

Remedial actionList Table DSlimit from the CI MAP (maintenance and administrationposition) level for the DSmax value. Reduce the amount of store requestedbelow the DSmax value entered for the module in Table DSlimit.


FormatSTOR101 mmmdd hh:mm:ss ssdd INFO DSLIMIT_OVERFLOW

Data store request of nnnn words disallowed for module IDhhhh.

MAX TOTAL nnnn WORDS EXCEEDED.

CHECK TABLE DSLIMIT AND REDUCE STORE.


VariableDescription

INFODSLIMIT_OVERFLOW

Constant Variable Indicates request for storage greaterthan the maximum accepted in TableDSlimit.

Data store request ofnnnn wordsdisallowed

Integers Variable Provides number of words requested.




Description

for module ID hhhh. 0000-FFFF Variable Provides hexadecimal identificationnumber for process.

MAX TOTAL nnnnWORD EXCEEDED.

Integers Variable Provides DSmax value entered inTable DSlimit.

CHECK TABLEDSLIMIT ANDREDUCE STORE.

Constant Variable Indicates that the user must reducestore request below the DSmax valueentered for the module in TableDSlimit.

Active message exampleSTOR101 APR01 12:00:00 2112 INFO DSLIMIT_OVERFLOW

Data store request of 4096 words disallowed for module ID

1490.

MAX TOTAL 5408 WORDS EXCEEDED.

CHECK TABLE DSLIMIT AND REDUCE STORE.



STOR102The Store (STOR) subsystem generates log report STOR102 when thestore audit detects an error in the inuse or avail vastarea links. The storeaudit connects the vastarea links again to correct the error.

Remedial actionThere is no action required. This log is for BNR and NT personnel to use ifthe system encounters other problems.


FormatSTOR102 mmmdd hh:mm:ss ssdd INFO LINK CORRUPTION

TYPE= nn LNKS= nn ORGN= nn DSTN= nn

VATYP= nn STAT= nn ACT= hhhh

STOR102 307



VariableDescription

INFO LINKCORRUPTION

Constant Variable Indicates a link corruption detected.

TYPE nn Variable Indicates the type of corruption theaudit discovered.

LNKS nn Variable Identifies the links that the systemwas scanning at the time the auditdiscovered the error.

ORGN nn Variable Identifies the vastarea that startedthe link field.

DSTN nn Variable Identifies the vastarea indicated bythe link field.

VATYP nn Variable Identifies the vastarea where thecorruption occurred.

STAT nn Variable Indicates the status of the vastareawhere the corruption occurred.

ACT hhhh Variable Indicates the action the auditperformed to correct the problem.

Active message exampleSTOR102 JAN 1 00:00:01 0902 INFO LINK CORRUPTION

TYPE= 02 LNKS= 03 ORGN= 32 DSTN= 45

VATYP= 05 STAT= 02 ACT= 07



STOR103The Store (STOR) subsystem generates log report STOR103. Thesubsystem generates this report when the STOR audit detects errors thatrelate to a critical variable in the STOR allocator. If STOR audit correctingaction is enabled, the audit regenerates the variable immediately.

Remedial actionThere is no action required. Bell Northern Research and Northern Telecomoperating company personnel can use this log if other problems occur.




• Warning

FormatSTOR103 hh:mm:ss ssdd INFO VARIABLE CORRUPTION

TYPE= nn DORP= nn CUR= hhhhhhhh

COR= hhhhhhhh ACT= hhhh


VariableDescription

INFO VARIABLECORRUPTION

Constant Variable Indicates store audit detects an errorwith a critical variable in storeallocator.

TYPE nn Variable Identifies type of corruption.DORP nn Variable Identifies if data store or program

store.CUR 0000-FFFF Variable Indicates current value of corrupted

field.COR 0000-FFFF Variable Indicates correct value of corrupted

field.ACT hhhh Variable Identifies action that the audit

performs to correct problem.

Active message exampleSTOR103 JAN 1 00:00:01 0903 INFO VARIABLE CORRUPTION

TYPE= 04 DORP= 01 CUR= 00F00000

COR= 00F00000 ACT= 06



STOR104The Store (STOR) subsystem generates log report STOR104. Thesubsystem generates this report when the subsystem detects an error inthe information that relates to a vast area. The STOR audit normally

STOR104 309


generates the specified value again. In some events, the STOR auditmarks the vast area as corrupt. The user can correct the error after theSTOR audit correcting action is enabled.

Remedial actionThere is no action required. Bell Northern Research and Northern Telecomoperating company personnel can use this log if other problems occur.


FormatSTOR104 hh:mm:ss: ssdd INFO VAST AREA CORRUPTION

TYPE= nn INDEX= nn VATYP= nn STAT= nn

ADDR= hhhhhhhh SIZE= hhhh WORDS

CUR= hhhh COR= hhhh ACT= hhhh


VariableDescription

INFO VAST AREACORRUPTION

Constant Variable Indicates an error that the systemdetects in information that relates to avast area.

TYPE nn Variable Indicates type of corruption that anaudit discovers.

INDEX nn Variable Provides index of vast area inaudit_allvastareasdesc.

VATYP nn Variable Indicates type of corrupted vast area.STAT nn Variable Indicates status of corrupted vast

area.ADDR 0000-FFFF Variable Indicates physical address of

corrupted area.SIZE 0000-FFFF Variable Indicates size of block of store that

ADDR indicates.CUR hhhh Variable Indicates current value of corrupted

field.COR hhhh Variable Indicates correct value of corrupted

field.ACT hhhh Variable Indicates the action that the audit

performs to correct the error.



Active message exampleSTOR104 JAN 1 00:00:01 0904 INFO VAST AREA CORRUPTION

TYPE= 03 INDEX= 45 VATYP= 02 STAT= 02

ADDR= 006E0000 SIZE= 7FFF WORDS

CUR= 0002 COR= 0003 ACT= 0002



STOR105The Store (STOR) subsystem generates log report STOR105. Thesubsystem generates this report when the STOR audit detects an errorthat associates with the headers for a vast area. The STOR audit marksthe area corrupt when the audit correcting action is enabled.

Remedial actionThere is no action required. Bell Northern Research and Northern Telecomemergency personnel can use this log if other problems occur.


FormatSTOR105 hh:mm:ss ssdd INFO HEADER CORRUPTION

TYPE= nn INDEX= nn VATYP= nn

ADDR= hhhhhhhh SIZE= hhhh WORDS

BLKS= nnn MAX= nnn IND= nnn

CUR= hhhhhhhh COR= hhhh ACT= hhhh

STOR105 311



VariableDescription

INFO HEADERCORRUPTION

Constant Variable Indicates that the system detects anerror with a header for a specifiedvast area.

TYPE nn Variable Indicates type of corruption that anaudit discovers.

INDEX nn Variable Provides index of vast area inaudit_allvastareasdesc.

VATYP nn Variable Indicates type of corrupt vast area.ADDR 0000-FFFF Variable Provides physical address of vast

area where corruption occurs.SIZE 0000-FFFF Variable Indicates size of block of store that

ADDR indicates.BLKS nnn Variable Indicates number of blocks in current

vast area.MAX nnn Variable Indicates maximum number of blocks

possible in current vast area.IND Variable Indicates index in header table of

current block.CUR 0000-FFFF Variable Provides current value of corrupt

field.COR hhhh Variable Provides correct value of corrupt

field.ACT hhhh Variable Indicates action audit performs to

correct problem.

Active message exampleSTOR105 JAN 1 00:00:01 0905 INFO HEADER CORRUPTION

TYPE= 02 INDEX= 45 VATYP= 00

ADDR= 006E0000 SIZE= 7FFF WORDS

BLKS= 150 MAX= 700 IND= 43

CUR= FDFDFDFD COR= 0001 ACT= 11





STOR106The Store (STOR) subsystem generates log report STOR106. Thesubsystem generates this report when the STOR audit cannot allocate ordeallocate store. The STOR audit cannot allocate or deallocate store forthe local tables or the test procedure. In the rst occurrence, the system killsthe audit and creates the audit again. In the second occurrence, the auditdoes not take action.

Remedial actionThere is no action required. Bell Northern Research or Northern Telecomemergency personnel can use this log if other problems occur.


FormatSTOR106 hh:mm:ss ssdd INFO STORE AUDIT FAILED

ALLOCATE/DE

ALLOCATE

DALOC= nn RC= nn BSIZE= hhhh STT= nn

BIG= hhhh TEST= nn ACT= hhhh


VariableDescription

INFO STORE AUDITFAILED ALLOCATE/DEALOCATE

Constant Variable Indicates store audit fails to allocateor not allocate store for the localtables or the test procedure.

DALOC nn Variable Indicates system generates log,because of an allocation ordeallocation problem.

RC nn Variable Identifies the return code that theSTOR allocator generates when theaudit fails to allocate or deallocatestore.

BSIZE hhhh Variable Indicates size of current block ofstore.

STOR106 313



Description

STT nn Variable Identifies store type used in allocationor not allocation.

BIG hhhh Variable Indicates size of largest block of storeavailable.

TEST nn Variable Indicates if audit fails allocation for alocal variable or for a test ofallocation/deallocation process.

ACT hhhh Variable Indicates action the audit performsaction to correct problem.

Active message exampleSTOR106 JAN 1 00:00:01 0906 INFO STORE AUDIT FAILED

ALLOCATE/DE

ALLOCATE

DALOC= 00 RC= 05 SIZE= 5EF STT= 00

BIG= 70F TEST= 01 ACT= 10



STOR107The Store (STOR) subsystem generates log report STOR107 daily. Thisreport provides information about the condition of the STOR allocator. Usethis information if other problems occur.

Remedial actionThere is no action required. Bell Northern Research or Northern Telecomemergency personnel can use this log if problems occur.


FormatSTOR107 hh:mm:ss ssdd INFO STORE AUDIT DAILY REPORT

PAUD= mmmdd hh mm ss FREQ= hhhh MINUTES ACT= hhhh



hhhh

PROB CNT= hhhh hhhh hhhh hhhh hhhh...........

STT| CUR USG |TTL VA| TTL CPTD |TTL ALOC|TTL D

LOC |

----- |------ |-------- |------- |---------

--- |-----

--- |

0 | <> | . | . | . | .

|

1 | . | | | |

|

2 | . | | | |

|

3 | | | | |

|

4 | | | | |

|

. | | | | |

|

. | | | | |

|

. | | | | |

|

TTL VAST= nnn TTL DS ST= hhhh hhhh TTL PS ST= hhhh hhhh

SPRE=

STOR107 315


hhhh

CUR DS INSE= nn% (vast1) CUR PS INSE= nn%(vast2)

CUR DS AVAL= nn% (vast3) CUR PS AVAL= nn%(vast3)


VariableDescription

ACT hhhh hhhh Variable Indicates store allocator activity.PROB CNT hhhh hhhh hhhh

hhhh hhhh.........Variable Indicates number of problems that

the audit detects for each error class.TTL VAST nnn Variable Indicates total number of vast areas

in use.TTL DS ST 0000-FFFF Variable Indicates total data store in

hexadecimal.TTL PS ST 0000-FFFF Variable Indicates total program store in

hexadecimal.SPRE 0000-FFFF Variable Indicates total program store in

hexadecimal.CUR DS INSE nn% (vast1) Variable Indicates current in use data store, as

a percentage. Indicates number ofvast areas assigned in use status.

CUR PS INSE nn% (vast2) Variable Indicates average in use programstore, as a percentage. Indicatesnumber of vast areas assigned in usestatus.

CUR DS AVAL nn% (vast3) Variable Indicates current available data store,as a percentage. Indicates number ofvast areas assigned available status.

CUR PS AVAL nn% (vast4) Variable Indicates average available programstore, as a percentage. Indicatesnumber of vast areas assignedavailable status.

STT n Variable Identifies store type.CUR USG 0000-FFFF Variable Indicates current use of each store

type in hexadecimal.TTL VA 0000-FFFF Variable Indicates total number of vast areas

assigned to each store type.TTL CPTD hhhh Variable Indicates number of corrupted vast

areas of each store type.TTL ALOC 0000-FFFF Variable Indicates total number of allocations

for each store type.




Description

TTL DLOC hhhh Variable Indicates total number ofdeallocations for each store type.

INFO STORE AUDITDAILY REPORT

Constant Variable Indicates information display. TheSTOR audit gathered informationfrom previous and current STORallocator audits.

PAUD mmmdd hh mm ss Variable Indicates date and time previousaudit runs.

FREQ hhhh Variable Indicates frequency of store audit.

Active message exampleSTOR107 DEC 31 00:00:01 0907 INFO STORE AUDIT DAILY REPORT

PAUD= DEC30 22:00:00 FREQ= 0002 MINUTES ACT= 0000 0005

PROB CNT= 0000 0005 0001 0002 0000 0000 0000 0000 0001

STT | CUR USG | TTL VA | TTL CPTD | TTL ALOC | TTL D

LOC |

------- | --------- | --------| ---------- | ---------- |------

--- |

0 |003A B778 | 003C | 0000 | 0100 003E | 0000

0011|

1 |0000 38B6 | 0001 | 0000 | 0000 0567 | 0000

0431|

2 |0053 B910 | 0056 | 0000 | 0000 1234 | 0000

1111|

3 |001C 961C | 001E | 0001 | 0000 F0AD | 0000

1010|

4 |0003 0000 | 0000 | 0000 | 0000 1101 | 0000

0E00|

STOR107 317


. | . | . | . | . | .

|

. | . | . | . | . | .

|

. | . | . | . | . | .

|

TTL VAST= 150 TTL DS ST= 3E 7FFF TTL PS ST= 4E 0000 SPRE=

50

0000

CUR DS INSE= 89% (133) CUR PS INSE= 93% (155)

CUR DS AVAL= 8% (4) CUR PS AVAL= 7% (10)



STOR108The Store (STOR) subsystem generates log report STOR108. Thesubsystem generates this report when the STOR audit detects a wrongpattern written to over flow buffers for block of store. The STOR audit doesnot define the over flow buffer if STOR audit correcting action is enabled.

Remedial actionThere is no action required. Bell Northern Research or Northern TelecomTechnical Assistance Service (TAS) operating personnel can use this log ifproblems occur. Contact TAS immediately.


FormatSTOR108 mmdd hh:mm:ss ssdd Inuse/Free Block Corruption

TYPE=<inuse/free> VAINDEX=<vastnum> HEADING<header index>



VATYPE=<vasttype> STAT=<status>

VAADDR:ADDR:<addres> SIZE=<words> WORDS OWNER=

<ownerid> <owner type and name>

THISBLK:ADDR=<address> SIZE=<words> WORDS OWNER=

<ownerid> <owner type and name>

NEXTBLK:ADDR=<address> SIZE=<words> WORDS OWNER=

<ownerid> <owner type and name> <memlock><pattern before>*

<invalid pattern> <pattern after>


VariableDescription

NEXTBLK alphanumeric Variable The block address, size and owner ofnext block in memory.

memloc hexadecimal Variable The corrupted pattern, the patternbefore corruption, and the patternafter corruption.

INUSE/FREEBLOCKCORRUPTION

buffer, or free block Variable The type of corruption the systemdetects (buffer or free block)

TYPE numeric Variable Indicates type of corruption that theaudit discovers.

VAINDEX alphanumeric Variable The index of vast area for whichblock in question resides.

HEADING numeric Variable The index in header table thatcorresponds to block in question.

VATYPE numeric Variable The store type of vast area.STAT numeric Variable The status of vast area.VAADDR numeric Variable The vast area block.MEM y,n Variable If the memory (memloc) that appears

is correct.ACT numeric Variable Store Audit performs correcting

action.PREVBLK alphanumeric Variable The block address, size and owner.THISBLK alphanumeric Variable The block address, size and owner.

Active message exampleSTOR108 JAN02 15:11:08 550 Inuse/Free Block Corruption

STOR108 319


TYPE:001 VAINDEX=001B HEADING=0023 VATYPE=0000

STAT=0002

VAADDR:ADDR=0059000 SIZE=8000 WORDS MEM=Y ACT=0000

PREVBLK:ADDR=0059B44 SIZE=0036 WORDS OWNER=6108 8040

MODULE WASTE

THISBLK:ADDR=0059BB0 SIZE=004E WORDS OWNER=6108 8040

PROCESS PROCESS JUNK

0059AC3E:FDFD FDFD FDFD FDFD *001 EFEF 004E FFFF 0000

0094



SWCT102This log report provides an account of the improvement of a central control(CC) warm switch of activity (SWACT). The system executes steps 0through 11 on the active side of the CC before the SWACT. The systemexecutes steps 100 through 105 on the active side after the SWACT.

Remedial actionLog SWCT102 is an information log. There is no action required.


FormatSWCT102 mmmdd hh:mm:ss ssdd PASS msgtxt




VariableDescription

msgtxt Preinitialization done Variable Step 0, successful completion ofinitialization of warm SWACT onactive side.

Communicationestablished

Variable Step 1, establishment ofcommunication between active andnot active sides is successful.

Exchange of datawith the mate done

Variable Step 2, exchange of data betweenactive and not active sides issuccessful.

Data estimation done Variable Step 3, estimation of how much datais transferred in step 11 is successful.

Store allocated onactive CC

Variable Step 4, allocation of data storecalculated in step 3 on active side issuccessful.

Store allocated oninactive CC

Variable Step 5, allocation of data store onside that is not active is successful.

AMA processingcomplete

Variable Step 6, AMA data dump issuccessful.

msgtxt Call processing inPM stopped

Variable Step 7, which disallows calloriginations is successful.

Call processing I/Oin CC stopped

Variable Step 8, which stops processing calloriginations and feature activationrequests is successful.

Call data extracted Variable Step 9, which saves active, steadytwo-port call data to make sure thatcalls maintain SWACT, is successful.

Data transfercompleted

Variable Step 10, which transfers data savedin step 9 to not active side issuccessful.

SWACT done Variable Step 11, which active and not activesides switch activity is successful.

Post-initializationdone

Variable Step 100, initialization of warmSWACT on active side is successful.

Data restored Variable Step 101, in which data transferred instep 10 is restored on active side, issuccessful.

CC processesresumed

Variable Step 102, in which call processing I/Oactivates again in active CPU, issuccessful.

SWCT102 321



Description

Created EXECloading process

Variable Step 103, creates process todownload EXECs to PMs, issuccessful.

PM states set Variable Step 104, downloads bitmaps to PMsto indicate which calls must maintainSWACT is successful. Callprocessing resumes in theperipherals.

SWACTfinishedTotal time inhh:mm:ss

Variable Step 105, indicates completion ofwarm SWACT, and displaysprocessing time, is successful.

Active message exampleSWCT102 SEP05 18:14:33 1800 PASS Preinitialization done



SWCT103The software for the central control (CC) warm switch of activity (SWACT)generates this report when a warm SWACT step fails or traps.

It is recommended that you collect SWACT, SWERR, and TRAP logs forthe active and inactive sides.

Remedial actionThis log report indicates a problem that affects service. You mustinvestigate and clear the cause(s) he cause(s) before a warm SWACT canbe completed.


FormatSWCT103 mmmdd hh:mm:ss ssdd FAIL <failure_text>




VariableDescription

FAIL constant Variable Indicates that a description of a CCwarm SWACT step trap or failurefollows.

failure_text Failedpreinitialization

Variable Step 0, initialization of CC warmSWACT on active side, did notcomplete. This field indicates that animage was taken when the SWACTwas attempted.

Failed to establishcommunication

Variable Step 1, communication between theactive and inactive sides, was notestablished.

Check for SWCT105 logs.failure_text Failed to exchange

data with the mateVariable Step 2, data exchange between

active and inactive sides, was notsuccessful.

Check for SWCT104, 105, and 106logs.

Failed data storeestimation

Variable Step 3, estimation of the amount ofdata transferred in step 11, was notsuccessful.

Check for SWCT106 logs.Failed to allocatestore on active CC

Variable Step 4, allocation of data store onactive side, was not successful.

Check for STOR, SOS, SWERR, andTRAP logs.

Failed to allocatestore on inactive CC

Variable Step 5, allocation of data store oninactive side, was not successful.

Check for STOR, SOS, SWERR,SWACT105, and TRAP logs on theactive and inactive sides.

Failed to processAMA data

Variable Step 6, AMA data dump, was notsuccessful.

Check the billing device to make surethat the process operates correctly.

Failed to stop PMcall processing

Variable Step 7, which prevents new calloriginations, was not successful.

Check for PM logs.

SWCT103 323



Description

Failed to stop callprocessing I/O

Variable Step 8, which stops call processingI/O in the CPU, was not successful.The system did not process calloriginations or feature activationrequests.

Failed to extract data Variable Step 9, which saves information onactive, stable, two-port calls, was notsuccessful.

Failed to transferdata

Variable Step 10, which transfers data savedin step 9 to the inactive side, was notsuccessful.

Check for MS, CM, TRAP, SWERR,and SWCT117 logs.

Failed to SWACT Variable Step 11, which switches activity fromone CPU to the other, was notsuccessful.

Check for MS, CM, TRAP, SWERR,and SWCT117 logs.

Failed post-initialization

Variable Step 100, the initialization of the CCwarm SWACT, failed on the activeside.

Check for SWCT106 logs.Failed to restore data Variable Step 101, which restores the data

transferred in step 10 to the activeside, was not successful.

Failed to resume CCCP process

Variable Step 102, which activates callprocessing I/O on the active CPUagain, was not successful.

Failed to createEXEC loadingprocess

Variable Step 103, which creates the EXECloading process, was not successful.

Failed to set PM TSI Variable Step 104, which resumes callprocessing in the PMs, was notsuccessful.

Check for PM logs.Failed to finish CCwarm QWACT

Variable Step 105, which completes warmSWACT, was not successful.

Check for TRAP, SWERR, andSWCT106 logs.

Active message exampleSWCT103 OCT04 11:48:03 5100 FAIL Failed to allocate store on



active CC



SWCT104The SWCT subsystem generates SWCT104 to provide importantinformation during the warm Switch of Activity (SWACT) process.

Remedial actionFix the device status when the message text reads: STATUSCHECKdevice status mismatch found. Fix the device status on the old active ornew inactive side of the CM. You must x the de vice status to correct themismatch. The list of mismatched devices is output to the console of theuser.


FormatSWCT104 mmmdd hh :mm : ss ssdd INFO msgtxt


VariableDescription

INFO Constant Variable Indicates warm SWACT informationfollows.

msgtxt FORCESWCTenabled

Variable Indicates that if more than 10% ofPMs are out of service on new side,activity remains on new BCS side.

FORCESWCTdisabled

Variable Indicates activity returns to old BCSside if system encounters conditionthat is not normal. The systemgenerates this message if the userenters the CI commandFORCESWCT OFF.

ABNORMALCONDITIONCONTINUING

Variable Indicates that more than 10% of PMsare offline, and warm SWACTcontinues on new BCS side.

SWCT104 325



Description

ABNORMALCONDITIONRETURNING TOOLD SIDE

Variable Indicates that more than 10% of PMsare offline, and warm SWACT returnsto old BCS side.

NOCHECK optionexecuted

Variable Indicates an option specified for thecentral control (CC) warm SWACTthat disables the node status thatchecks on active side.

NOMATCH optionexecuted

Variable Indicates an option specified for CCwarm SWACT that disables the nodestatus matching between active andinactive side.

Time-out in CC warmSWACT occurred

Variable Indicates a communication time-out,between computing module (CM) anda peripheral, while the systemestablishes the call processing on theperipheral, again.

STATUSCHECKdevice statusmismatch found

Variable Fix device status on old active or newinactive side of CM.

Active message exampleSWCT104 DEC08 11:17:23 7000 INFO FORCESWCT enabled



SWCT105The central control (CC) warm Switch of Activity (SWACT) subsystemgenerates SWCT105. The system generates this report when CC warmSWACT fails communication over the MATE communication facilities. TheNT40 uses the MATE communication register (MCR). The SuperNodeuses MATELINK.

This condition occurs when the communication link between the two sidesfails to operate. The communication link fails to operate because of asoftware restriction or hardware problem. The INFO lines give a two-linetrace of the calling code. Problem analysis requires INFO lines.



Remedial actionUse the communication link, MATE/MATELOG, to determine if the problemrelates to the hardware or the software. If MATE/MATELOG does not work,the problem is with the hardware. For software problems, check the logsfor software error reports (SWER).

Contact the next level of maintenance.


FormatSWCT105 mmmdd hh:mm:ss ssdd TBL COMMUNICATION

PROBLEM

REASON : reasontext

INFO: infotext1

: infotext2


VariableDescription

INFO Symbolic text Variable Provides additional information aboutcommunication failure.

TBLCOMMUNICATIONPROBLEM

Constant Variable Indicates a communication problem.

REASON Areas for inactiveexceed maximumnumber.

Variable Indicates limit for number of transferdata areas exceeded on the side thatis inactive.

Not able to protectinactive.

Variable Indicates attempt to unprotect datastore (DS) not allowed.

Not enough store oninactive.

Variable Indicates inactive side free store isnot enough for data transfer.

Work area full oninactive.

Variable Indicates inactive side applicationsthat return data to active overflowbuffer.

Not able to sendfrom inactive toactive side.

Variable Indicates communication to activeside is not possible.

SWCT105 327



Description

Reply not receivedon inactive.

Variable Indicates that the data transfer frominactive to active side is notacknowledged.

Reply not correct oninactive.

Variable Indicates active side sends reply thatis not correct.

Areas for activeexceed maximumnumber.

Variable Indicates limit for number of datatransfer areas exceeded on activeside.

Not able to unprotectactive.

Variable Indicates attempt to unprotect DSallowed.

Not enough store onactive.

Variable Indicates active side free store is notenough for data transfer.

Work area full onactive.

Variable Indicates active side applications thatfill the data transfer buffer, overflowthe buffer.

Not able to sendfrom active toinactive side.

Variable Indicates communication to side thatis inactive is not possible.

Reply not receivedon active.

Variable Indicates that the data transfer fromactive to inactive side is notacknowledged.

Reply not correct onactive.

Variable Indicates side that is inactive sends areply that is not correct.

Comm link failure,bad return code.

Variable Indicates the MCR or MATELINK didnot open or was not claimed for CCwarm SWACT use. Also indicatesfailure of the communication link.

Estimate of storeexceeded.

Variable Indicates an error in store estimateoccurs.

Fail to read datafrom inactive.

Variable Indicates attempt to read data frominactive side fails.

Fail to copy data oninactive.

Variable Indicates attempt to copy data fromactive to inactive side failed.

Fail to write data toinactive side.

Variable Indicates attempt to write data intoinactive store failed.

Invalid format fordata.

Variable Indicates data transferred contains aformat that is not correct.

End of formatmissing for data.

Variable Indicates data transferred does notcontain end format information.

Count for data that isnot correct.

Variable Indicates amount of data stored foran application and transferred, wasnot correctly put in the index.




Description

Handshake failureSWACT DATA.

Variable Indicates handshake failure whensystem determines SWACTapplication format codes.

Handshake failureDEVICE STATUS.

Variable Indicates handshake failure when thesystem determines SWACT deviceapplication codes.

Switch activity noticefails to send.

Variable Indicates system cannot send switchactivity notice for inactive side.

Switch activity noticeACK fails.

Variable Indicates inactive side does notacknowledge request to switchactivity notice.

OFCSTDBCS_NUMBER isnot correct forSWACT.

Variable Indicates software version of CCwarm SWACT identifies the dataentered BCS_NUMBER, is notcorrect.

Failed to attain BCSnumber frominactive.

Variable Indicates attempt to reach BCSversion from inactive side failed.Check BCS_NUMBER of inactiveside and logs to help identifyproblem.

Active message exampleSWCT105 JAN12 11:05:25 2112 TBL COMMUNICATION PROBLEM

REASON : HANDSHAKE FAIL SWCT DATA.

INFO : 0A132D: SWCTNRUI.AQ01:SWCT_HAND_#+00A2

: OA12EA:SWCTNRUI.AQ01:SWCT_SWCT_D#+0009



SWCT106The system generates SWCT106 when a central control (CC) warm Switchof Activity (SWACT) application encounters problems. This conditionnormally occurs when a software restriction or hardware problem occurs.

The system generates SWCT106 if a SWACT application trap occurs. Thelog report contains information on the application that traps.

SWCT106 329


Reason text explanations for SWCT106 logs, associated with traps in a CCwarm SWACT, appear in the following list. Match the reason text:

• Trap occurs on critical application -- Indicates that a trap occurs on acritical warm SWACT application. The SWACT aborts.

• Trap occurred on a not-critical application -- Indicates that a trap occurson a not critical warm SWACT application. The SWACT is not affected.

• Trap on area in SWACT code (stops SWACT) that cannot be traced. --Indicates that a trap occurs on a not-traceable location in SWACTcode. This reason text indicates that the SWACT aborts.

Remedial actionReport the SWCT106 log to the operating company personnel responsiblefor the SWACT.

AttributesAttribute ValueSeverity Critical

FormatSWCT106 mmdd hh:mm:ss ssdd TBL SWACT Application Problem

Application : <application_name>

Reason : <reason_text>

Data : aaaa bbbb cccc dddd eeee ffff gggg hhhh iiii jjjj

Traceback : <traceback_text1>

: <traceback_text2>


VariableDescription

TBL SWACTApplication Problem

Constant Variable Indicates that a warm SWACTapplication has a problem.

Application Constant Variable Indicates that name of affectedSWACT BASE activity follows.

application_name text Variable Indicates warm SWACT applicationthat has the problem.

Reason constant Variable Indicates the reason that the systemgenerates the log.

reason_text text Variable Indicates the problem that occurs.




Description

The first table in the Additionalinformation section of this log reportdescription contains reasons forSWACT logs. The SWACT logs areassociated with CC warm SWACTtraps.

Data constant Variable Indicates that debug informationfollows.

aaaa bbbb ccccdddd eeee ffff gggghhhh iiii jjjj

0000 to 9999 foraaaa through jjjj

Variable Indicates a series of up to ten 4-digitnumbered codes that provide debuginformation on the problem.

The value 1234 indicates that datawas not output.

Traceback constant Variable Indicates that tracebacks follow. Atraceback identifies the warmSWACT procedure that generatesthe log.

traceback_text1 Alphanumeric text Variable Indicates the procedure and theoffset into procedure where thesystem detects a problem.

traceback_text2 Alphanumeric text Variable Indicates the procedure and theoffset into procedure where thesystem makes call to first procedure.

Active message exampleSWCT106 APR25 16:01:54 4200 TBL SWACT Application Problem

Application : SWACT Base Activity

Reason : Trap occurred on critical application

Data : 0002 0001 0000 1234 1234 1234 1234 1234

1234 1234

Traceback :

:073AE6C4+SWCTNRUI.CD12:SWCT_ME+#012C

:073AF7C4+SWCTNRUI.CD12:SWCT_VER+#0024


SWCT106 331



SWCT112The Switch of Activity (SWACT) subsystem generates log reportSWCT112. The subsystem generates this report when the EXEC thatpreloads, fails for the specified peripheral module (PM). The subsystemgenerates one report for every PM that fails to preload EXECs.

Remedial actionRepeat the procedure. Attempt to preload the EXECs to the specified PM.If the procedure fails, load the EXECs for the specified PM after the SWACT.


FormatSWCT112 mmmdd hh:mm:ss ssdd EXEC PRELOADING FAILED

FOR <pm_id>


VariableDescription

EXECPRELOADINGFAILED FOR

Constant Variable Indicates the EXEC that preloads forthe specified PM failure.

<pm_id> Symbolic text Variable Indicates the PM on which the EXECthat preloads, fails.

Active message exampleSWCT112 JUL17 23:15:32 2300 EXEC PRELOADING FAILED FOR

LTC 0





SWCT114• The warm Switch of Activity (SWACT) subsystem generates log report

SWCT114. The subsystem generates this report after use of theMODCHECK facility is not successful. This problem can occur afterthe:

• PRESWACT step

• MODCHECK command

• use of RESTART/ABORTSWCT commands.

Remedial actionUse of the OVERRIDE option on MODCHECK is very risky

Use only after the flagged modules that are not present have beeninvestigated fully. During SWACT, severe degradation occurs in the featurethat the overridden module supports.

Take the following steps if problems arise:

• Collect all SWCT115 logs to see modules that are not present on theINACTIVE side.

• Use SWACT command MODCHECK OVERRIDE to override themodules that are not present, if no modules ag as critical. Contact thenext level of support to determine the reason that critical SWACTmodules are not present on the INACTIVE side.

AttributesAttribute ValueSeverity Critical

FormatSWCT114 mmmdd hh:mm:ss ssdd FAIL SWACT MODULES MISSING


VariableDescription

FAIL SWACTMODULES MISSING

Constant Variable Indicates failure caused by missingSWACT modules.

Active message exampleSWCT114 AUG09 06:02:06 4200 FAIL SWACT MODULES MISSING

SWCT114 333




SWCT115The warm Switch of Activity (SWACT) subsystem generates log reportSWCT115. The subsystem generates SWCT115 after use of theMODCHECK facility is not successful. This problem can occur after the:

• PRESWACT step

• MODCHECK command

• use of RESTART/ABORTSWCT commands.

This log indicates that use of the MODCHECK facility is not successful.This log displays the name of every module that is not present. The systemoutputs one log per module that is not present.

Refer to the following list for correct module names:

• SWCTNRUI, SWCTUI, SWCTDAD, SWCTKID, SWCTMACH

• SWEXKD, SWCTCI, NRPMEX, SWCTEMPCP, IPMLSWCT, C6SWCT

• STAUPDUI, RESTPRCS, C7MTPSWT, SCCPSWCT, LIUSWCT

• INTSWCTI, XPMASWCT, MSCSWCT, SYNCKUI, ENCSWCT

• SEASSWCT, FTRQPERM, DPNSWCT, N6SWACT, NODESTAT

• JCTRSTAT, CARRSTAT, IPMLSTAT, STCSTAT, CMWSWACT

• OPMSTAT, DCHSTAT, CCS6STAT, CSCSTAT, RCUSTAT,DRCCSTAT

• MPCSTAT, NRLMEX, INTLSWCT, FTASWCT, FRSSWCT,DATESWCT

Remedial actionYou can ag modules that are not present as critical. Use this log todetermine the reason the modules that are not critical, are not in the newINACTIVE load. Contact the next level of maintenance to determine thecritical SWACT modules that are not present on the INACTIVE side.During SWACT, severe degradation occurs in the feature that theoverridden module supports.




• Critical

FormatSWCT115 mmmdd hh:mm:ss ssdd INFO SWACT MODULE modname

IS MISSING


VariableDescription

INFO SWACTMODULE...ISMISSING

Constant Variable Indicates that a SWACT module isnot present.

modname Symbolic text Variable Displays the name of the module thatis not present, that causes thesystem to output log SWCT114.Refer to the list of correct modulenames at the end of this log report.

Active message exampleSWCT115 AUG09 06:02:06 4200 INFO SWACT MODULE ENCSWCT IS

MISSING



SWCT116The warm Switch of Activity (SWACT) subsystem generates log reportSWCT116. The subsystem generates this report after use of the:

• MODCHECK OVERRIDE command in SWACT

• PRESWACT step

• MODCHECK command.

This log indicates that an override on checks for a SWACT module istoggled. The log informs the user of these conditions.

SWCT116 335


Refer to the following list for correct module names:

• SWCTNRUI, SWCTUI, SWCTDAD, SWCTKID, SWCTMACH

• SWEXKD, SWCTCI, NRPMEX, SWCTEMPCP, IPMLSWCT, C6SWCT

• STAUPDUI, RESTPRCS, C7MTPSWT, SCCPSWCT, LIUSWCT

• INTSWCTI, XPMASWCT, MSCSWCT, SYNCKUI, ENCSWCT

• SEASSWCT, FTRQPERM, DPNSWCT, N6SWACT, NODESTAT

• JCTRSTAT, CARRSTAT, IPMLSTAT, STCSTAT, CMWSWACT

• OPMSTAT, DCHSTAT, CCS6STAT, CSCSTAT, RCUSTAT,DRCCSTAT

• MPCSTAT, NRLMEX, INTLSWCT, FTASWCT, FRSSWCT,DATESWCT

Remedial actionNote overridden modules. During SWACT, severe degradation occurs inthe feature that the overridden module supports.


FormatSWCT116 mmmdd hh:mm:ss ssdd INFO modname SET FOR action


VariableDescription

INFO...SET FOR Constant Variable Indicates that a SWACT module hasbeen overridden.

modname Symbolic text Variable Displays the name of the affectedmodule. Refer to the list of correctmodule names at the end of thisreport.

action OVERRIDE Variable Indicates the action for the affectedmodule

CHECKING Variable

Active message exampleSWCT116 AUG09 06:02:06 4200 INFO ENCSWCT SET FOR OVERRIDE





SWCT117The Switch of Activity (SWACT) subsystem generates log report SWCT117to document activities or problems.

Remedial actionFor message "Critical trap in SWACT base code (non-application orSWACT step)" then collect all SWCT, SWERR, and TRAP logs andcontact the next level of maintenance. This message indicates that acritical trap occurred in a part of the SWACT base code that is not anapplication or base step.


• Critical

FormatSWCT117 mmmdd hh:mm:ss ssdd INFO SWACT information

TEXT: <info_text>


VariableDescription

INFO SWACTinformation

constant Variable Indicates that SWACT informationfollows.

TEXT constant Variable Indicates that a description ofSWACT activities or problemsfollows.

info_text Up to 80 characters Variable The SWACT:

• messages

• the meaning of the messages

• required action

Active message exampleSWCT117 JUN09 14:22:10 5600 INFO SWACT information

TEXT: Critical trap occurred in SWACT Base code (non

application or SWACT step).

SWCT117 337




SWERThe Software Error Reporting (SWER) subsystem generates log reportSWER. The subsystem generates this report when a software conditionaffects normal operation of the DMS switch or switch peripherals. Thesubsystem also generates this report when a user requests log trace fromthe LOGUTIL MAP (maintenance and administration position) level. SeeInput/Output System Reference Manual, 297-1001-129, for commandsyntax to trace log reports.

Remedial actionIf the user requests SWER for a log trace, there is no action required.

If the user does not save all reports that the system generates 5 min beforethe SWER report. Contact the next level of maintenance.


FormatSWERR mmmdd hh:mm:ss ssdd MISC

REASON=hhhh, PROCID= #hhhh #hhhh: modnm, TEXT= reastxt

traceinfo


VariableDescription

MISC Constant Variable Indicates a miscellaneous SWER log.REASON 0000-FFFF Variable Provides hexadecimal number for

trouble isolation by software problemsolving personnel. The default value(0000) indicates that additionalinformation is not supplied for thesoftware event that generates thereport.

PROCID 0000-FFFF Variable Provides hexadecimal identificationnumber for process.




Description

modnm Character string Variable Provides module name in whichprocess that generates SWERresides.

TEXT Character string orblank

Variable Provides additional information fortrouble isolation by software problemsolving personnel.

Variable If the system generates SWER as aresult of LOGTRACE, reastxt equalslog name and report number fortraced log report.

traceinfo Software addressesand procedures

Variable Provides traceback of modules andprocesses in user before systemencounters SWER.

Variable TRACEINFO contains the log nameand report number if the systemgenerates SWER as a result ofLOGTRACE.

Active message exampleSWERR APR01 12:00:00 2112 MISC

REASON=0000, PROCID= #A11E #C005: CPAPKID, TEXT=

1B73AF=STNZD.EH02:STN_RECO+#00CB

1B6B89=STNZD.EH02:STN_AUDI+#0245

0BF49D=CPMUI.DF01:AUDIT_CP+#0013

0DEF97=CPAPKID.AA01:CP_AUDIT+#003D

01365F=MODULES.BJ01:INITIALIZEP+#0009

00AE3B=POCS.DO02:LIVEANDD+#0007



SWNR100The Switch of Activity (SWACT)/Non-Resident Software (SWNR)subsystem generates log report SWNR100. The subsystem generates thisreport to provide central control (CC) warm SWACT information after aSWACT transfer of DMS control. The transfer goes to alternate CC. The

SWNR100 339


subsystem can generate this report when this software is resident. Forexample, when the system loads of a new batch change supplement(BCS).

Remedial actionThere is no action required. Refer to BCS applications.


FormatSWNR100 mmmdd hh:mm:ss ssdd INFO msgtxt


VariableDescription

msgtxt FORCESWCT INEFFECT

Variable Indicates default condition. If the notnormal condition encounters morethan 10 % of peripheral modules(PMs) out of service on new side,activity remains on new BCS side.

FORCESWCT NOTIN EFFECT

Variable Indicates that activity returns to oldBCS side if the not normal conditionoccurs. The system generates thismessage if the user enters the CIcommand FORCESWCT OFF.

EXEC LOADINGDISABLED

Variable Indicates the peripherals do not loadEXECS as part of a warm SWACT.The system generates this messageif the user enters the CI commandLOADEXECS OFF.

EXEC LOADINGENABLED

Variable Indicates the default condition. Theperipherals do not load EXECS aspart of warm SWACT.

OUTGOINGBUFFERS FORPMS LESS THAN 10

Variable Indicates that a small number ofoutgoing buffers are available. As aresult EXEC loading can be slow.Applies to trunk module (TM) anddigital carrier module (DCM) typenodes.

OUTGOINGBUFFERS FOR LMSLESS THAN 10

Variable Indicates a small number of outgoingbuffers are available. As a resultEXEC loading can be slow. Appliesto line module (LM) and remote linemodule (RLM) type nodes.




Description

ABNORMALCONDITIONCONTINUING

Variable Indicates that more than 10 % of PMsare offline. Indicates that warmSWACT continues on new BCS side.

ABNORMALCONDITION-RETURNING TOOLD SIDE

Variable Indicates that more than 10 % of PMsare offline. Indicates that warmSWACT returns to old BCS side.

BCS VERSIONSDIFFER-EXECLOADINGREQUIRED

Variable Indicates that software versions onboth sides differ. Indicates the userchooses the LOADEXECS OFFoption. This group is not allowed andstops the warm SWACT.

NOMATCH OPTIONEXECUTED

Variable Indicates that the RESTARTSWCTcommand uses the NOMATCHparameter.

FAILURE: DEVICEMISMATCH FOUND

Variable Indicates a device statusMISMATCH, results in a warmSWACT failure. The MISMATCHcauses the subsystem to generatelog report SWCT103. The user canissue the CI commandSTATUSCHECK to issue this reportmessage.

EXEC LOADINGPROC NOT BOUNDIN

Variable The procedures necessary, to loadEXECS to peripherals are notpresent.

Active message exampleSWNR100 DEC08 11:17:23 7000 INFO FORCESWCT IN EFFECT



SWNR101The Switch of Activity (SWACT)/Non-Resident Software (SWNR)subsystem generates log report SWNR101. The subsystem loads EXECSinto the nodes. It does this as part of a central control (CC) warm SWACTtransfer of Digital Multiplex System (DMS) control to alternate CC.

Remedial actionn/a

SWNR101 341



FormatSWNR101 mmmdd hh:mm:ss ssdd PASS msgtxt


VariableDescription

msgtxt EXEC LOADING OKLM NODES

Variable Indicates that the line modules (LMs)have EXECS loaded.

EXEC LOADING OKDCM NODES

Variable Indicates that the digital carriermodules (DCMs) have EXECSloaded.

EXEC LOADING OKTM NODES

Variable Indicates that the trunk modules(TMs) have EXECS loaded.

EXEC LOADING OKRLM NODES

Variable Indicates that the remote linemodules (RLMs) have EXECSloaded.

EXEC LOADING OKXPM NODES

Variable Indicates that the peripheral modules(PMs) have EXECS loaded.

Active message exampleSWNR101 AUG09 06:02:06 4200 PASS EXEC LOADING OK LM

NODES



SWNR102The Switch of Activity/Non-Resident Software (SWNR) subsystemgenerates log report SWNR102. The subsystem generates this report afteran attempt to load a node with an exec fails. This attempt is part of acentral control (CC) warm SWACT (transfer of DMS control to alternateCC). The subsystem only generates the report when the software isresident; for example, during the loading of a new software release.

Remedial actionAll failed nodes must have their execs loaded and returned to service(RTS). Refer to software release applications.




FormatSWNR102 mmmdd hh:mm:ss ssdd FAIL msgtxt


VariableDescription

FAIL msgtxt EXEC LOADINGFAILED LM NODES

Variable Failure of exec load to a line modulenode type. All nodes of that type willbe made system busy (SysB).

EXEC LOADINGFAILED DCMNODES

Variable Failure of exec load to a digital carriermodule node type. All nodes of thattype will be made SysB.

EXEC LOADINGFAILED TM NODES

Variable Failure of exec load to a trunkmodule node type. All nodes of thattype will be made SysB.

EXEC LOADINGFAILED RLMNODES

Variable Failure of exec load to a remote linemodule node type. All nodes of thattype will be made SysB.

EXEC LOADINGFAILED XPMNODES

Variable Failure of exec load to an XMSperipheral module node type. Allnodes of that type will be made SysB.

Active message exampleSWNR102 AUG09 06:02:12 5300 FAIL EXEC LOADING FAILURE DCM

NODES



SYNC101The Synchronous Clock (SYNC) subsystem generates log reportSYNC101. The SYNC generates this report when the subsystem updatesa tuning control in a clock for the reason given. The tuning control changecauses a clock frequency change.

Remedial actionThere is no action required. This report provides information onsynchronous clocks that you can use with the trouble clearing procedures.

SYNC101 343


For the phase register, the bit position an meanings follow:

• 0-7 -- Phase detector counter. Values are 0000 0000-1111 1111 (00-FF in hexadecimal).

• 8,9,10 -- Indicates the type of clock card affected. Refer to the TableClock bits below.

• 11 -- Beat frequency detector.

• 12 -- Reference selection indicator.

• 13 -- Alm0 indicator value is 1 if alarm Alm0 is present and the externalreference oscillator failed. If the alarm is not present and the oscillatordid not fail, the value is 0.

• 14 -- A0m1 indicator. Value is 1 if alarm A1m1 is active and theexternal reference oscillator power supply failed. If the alarm is notactive and the oscillator power supply did not fail, the value is 0.

• 15 -- Phase detector indication. Value 0 or 1, toggles with each phasedetector measurement.

Bits 10, 9, and 8 indicate the clock card type. With bit 1 on the left and 8 onthe right:

• 000 -- 3X15AA

• 001 -- 3X15AB/BA

• 010 -- 3X15CA

• 011 -- 3X15AD

• 100 -- 3X15DA/3X16

• 101 -- Not used

• 110 -- Not used

• 111 -- Not used


FormatSYNC101 mmmdd hh:mm:ss ssdd INFO reason

ACTIVE CLOCK = clkno

CLK0, CLK1: TUN CTL = hhhh,hhhh PHASE REG = hhhh,hhhh




VariableDescription

reason MANUAL DACLOAD

Variable Manual action use of the commandADJDOWN or ADJUP on theSYNCLK level changed the control ofthe tuning. The digital to analogconverter (DAC) in the NT3X15 clockcard was adjusted. The clock cardwas adjusted the specified number ofsteps, either down or up or to thecenter value.

POWER ERRORCLOCK RESET

Variable Automatic action changed the controlof the tuning because of a powererror. DAC was reset to the centervalue.

ALARM CLEARED:SYSTEM

Variable Indicates that the system cleared theSYNCLK alarm after 15 minutes ofnot allowing a switch performance.

ALARM CLEARED:MANUAL TEST

Variable Indicates that the manual actionperformance of the long test on bothclocks cleared the SYNCLK alarm.

CLK0, CLK1: Constant Variable Indicates that the system gives thefollowing values for both clocks.

ACTIVE CLOCK 0,1 Variable CMC clock number.TUN CTL 0000-FFFF, 0000-

FFFFVariable Label for tuning control values of

clocks. The system presents thevalues for each clock as fourhexadecimal digits. The hexadecimalvalues and the frequencies thatcorrespond to the hexadecimalvalues are:

0000 Variable A frequency lower than the center byan frequency shift ratio (FSR) of -1.5x 10-6.

8000 Variable The center frequency, nominally10.240 MHz.

FFFF Variable A frequency higher than middle by aFSR of + 1.5 x 10-6.

Variable To obtain FSR subtract the nominalfrequency from the current frequency.Divide the difference by the centerfrequency.

PHASE REG 0000-FFFF, 0000-FFFF

Variable Label for phase register values ofclocks. Values appear as four-digithexadecimal numbers. To interpret

SYNC101 345



Description

the value, convert the number tobinary and the bits numbered fromright to left as 0 to 15. See TablePhase register.

Active message exampleSYNC101 MAY31 08:46:32 2112 INFO MANUAL DAC LOAD

ACTIVE CLOCK = 1

CLK0, CLK1: TUN CTL = 4BC3,5FF1 PHASE REG = CD35,2A5B



SYNC102The Synchronous Clock (SYNC) subsystem generates the SYNC102 log.The SYNC generates this report when a clock switch or a timing link switchoccurs. The switch occurs when a sync clock reaches the fault threshold.The SYNC102 gives detailed information about the clocks.

Remedial actionThere is no action required. The central controller (CC) subsystemprovides information about the synchronous clock. You can use theinformation with the trouble clearing procedures.

Match the event value with the following list:

• BEAT FREQUENCY -- Indicates too short of a beat frequency period.The short beat frequency period caused the system to generate thelog.

• MANUAL CLOCK SWITCH OK -- Indicates completion of a manualclock switch operation.

• STARTING TO SYNC CLOCK --Indicates start of clocksynchronization. In SLAVE configuration, either the inactive clock is insync with the active clock. Or, the active clock is in sync with the hostoffice. In MASTER INTERNAL configuration, the inactive clock is insync with the active clock. In MASTER EXTERNAL configuration,either clock is in sync with its own external timing source.

• MANUAL DROP SYNC -- Indicates a clock was manually set freerunning.



• CARRIER SWITCH OK -- Indicates that manual action switched thecarrier that provides timing samples to the active clock. (SLAVEconfiguration only).

• CLOCK TESTS OK -- Indicates successful tests of a clock.

• CLOCK RTS -- Indicates a clock was returned to the in-service mode.The clock was returned to either the linking, free-running, orsynchronization state.

• PERIODIC TEST -- Indicates that the system performed a periodic teston the inactive clock and the test passed.

• AUDIT: INACTIVE CLOCK NOT IN SYNC -- Indicates that the systemperformed an audit and the inactive clock was not synchronized.

• AUDIT: CLOCK STATE ERROR -- Indicates an audit found the clocksin an invalid state.

• AUDIT: FREQ ADJUST OK -- Indicates that the system cleared theCLKADJ alarm. The system cleared the alarm because the oscillatorreached a frequency adjust, lower than the LOWDRIFT parameter inTable SYNCLK.

• AUDIT: INACTIVE CLOCK IS FREE -- Indicates that the systemperformed an audit. The audit found the inactive clock in the freerunning state.

• AUDIT: INVALID TIMING LINK STATE -- Indicates an audit found thelinks in an invalid state.

• AUDIT: SAMPLING STARTED -- Indicates an audit started the timingsamples.

• AUDIT: NEITHER LINK LOCKING -- Indicates an audit determined thatneither timing link can lock.

• AUDIT: INVALID LINK LOCKING -- Indicates an audit detected aninvalid link lock.

• LOOP CONSTANCES UPDATED -- Indicates that the system updatedthe phase-locked loop constances.

• CMC RTS -- Indicates the system returned a CMC to service.

• CMC BSY -- Indicates a CMC was busied.

• LINK STATE CHANGE -- Indicates a change of state of one of theDS-1 links used for synchronization in a slave office.

• CLOCK IN SYNC -- Indicates the CMC clocks are in sync.

• LINK SWITCH OK -- Indicates completion of a timing link switch.

• PHASE ERROR -- Indicates that the system detects a phase error fromthe timing samples.

SYNC102 347


• PHASE COUNTER ERROR -- Indicates that the system detects anerror with the phase counter.

• OSCILLATOR ALARM CLEARED -- Indicates the clearing of anoscillator alarm.

• PROCESS RECREATED -- Indicates the process that receivessamples was created again.

• ALTERNATE PM SLIP -- Indicates a slip occurred on the alternatetiming link.

• SAMPLING STOPPED -- Indicates the peripheral stopped the timing.

• SAMPLING CONTINUED BY PM -- Indicates the peripheral moduleresumed sampling.

• LINK STATUS CHANGE -- Indicates the status of a timing linkchanged.

• UNEXPECTED SAMPLE -- Indicates a sample received from a sourcethat was not planned.

• CLOCK SWITCH, HW CLOCK INTERRUPT -- Indicates the systemperformed a clock switch because a hardware clock interrupt reachedthe threshold.

• CLOCK SWITCH, CMC PORT ERRORS -- Indicates the systemperformed a clock switch because the CMC port error reached thethreshold.

• ALARM CLEARED: SYSTEM -- Indicates the system cleared theSYNCLK alarm after 15 min of not performing a switch.

• CLOCK SWITCH, TIMING LINK SWITCH -- Indicates the systemperformed a clock switch because the number of timing link switchreached the threshold.

• TIMING LINK SWITCH, SLIPS -- Indicates the system performed atiming link switch because the number of slips reached the threshold.

• TIMING LINK SWITCH, BAD SAMPLES -- Indicates the systemperformed a timing link switch because of the number of bad samples.

• CLOCK SWITCH, CMC PERIODIC TEST -- Indicates the CMCperiodic pretest performed the clock switch, to ensure the inactive clockis OK.

• PERIODIC CLOCK SWITCH FAILED -- Indicates that the periodicpretest failed because the clock switch failed at some point.

• AUDIT: HIGH FREQ ADJUST LIMIT -- Indicates an audit determinedthat the frequency adjust limit of +/- 75% was reached or exceeded.



• AUDIT: LOW FREQ ADJUST LIMIT -- Indicates that the oscillatorfrequency adjust raised an alarm. The oscillator frequency adjust isbeyond the range specified in table SYNCLK but below the systemdefined limit of 75 percent.

• CLOCK SWITCH SYNCLK FAULT COUNTS -- Indicates that thereason of the switching clock is not HW CLOCK INTERRUPT, CMCPORT ERROR or TIMING LINK SWITCH.

• LINK SWITCH SYNCLK FAULT COUNTS -- Indicates that the reasonof the switching link is not sample slip or bad sample.

The following list identifies the status register bit value meanings:

• Bit 0 -- Set to value 1 if reference fail detector is under test.

• Bit 1 -- Set to value 1 if oscillator fail detector is under test.

• Bit 2 -- Set to value 1 if reference fail detector is under test.

• Bit 3 -- Set to value 1 if frame pulse fail detector is under test.

• Bit 4 -- Set to value 1 if reset error condition is in effect.

• Bit 5 -- Not used.

• Bit 6 -- Set to value 1 if clock interrupt is disabled.

• Bit 7 -- Set to value 1 after power is reset, cleared by RSTIND.

• Bit 8 -- Set to value 1 if clock is the active clock.

• Bit 9 -- Set to value 1 if you detect failure of the 10.240 MHz.

• Bit 10 -- Set to value 1 if you detect a frame pulse failure.

• Bit 11 -- Set to value 1 if the external select is not set or the externalreference signed failed. You will see Code Ext on the SynClk displayunder the header ExtOsc.

• Bit 12 -- Set to value 1 if the digital to analog converter (DAC) load hastime-out.

• Bit 13 -- Set to value 1 if no clock interrupt is posted.

• Bit 14 -- Set to value 1 if a power converter failed. You will see theAlarm code Pwr on the SynClk display under the header IntOsc.

• Bit 15 -- Set 1 if the oscillator heater cycle time is greater than 5minutes. You will see the Alarm code Htr on the SynClk display underthe header IntOsc.


SYNC102 349


FormatSYNC102 mmmdd hh:mm:ss ssdd INFO STAT event

ACTIVE CLOCK = clkno

CLK0,CLK1:STATE=syncst,syncst STAT REG=hhhh,hhhh ALARM=

fltcode,fltcode

TUNING CONTROL=hhhh,hhhh PHASE REG=hhhh,hhhh

LNK0,LNK1: STATE = 1st1txt,1st2txt SLIP CT= n,n

PREV STATE = st1txt,st2txt


VariableDescription

INFO STAT Constant Variable Indicates a report of SYNC clockstatus.

event Symbolic text Variable Indicates the event that causedSYNC to generate the report. Referto Table Event at the end of this logreport.

ACTIVE CLOCK 0,1 Variable Indicates the active CMC clock.CLK0,CLK1: Constant Variable Indicates the values for the following

fields appear for Clock 0 followed byClock 1.

STATE FREE Variable Indicates the clock is free-running.SYNC -Synchronized

Variable Indicates the clock is synchronized toa timing source.

LKNG - Linking Variable Indicates the clock is attempting tosynchronize to a timing source.

STAT REG 0000-FFFF, 0000-FFFF

Variable Indicates status register values foreach CMC clock. Convert the four-digit hexadecimal numbers to binary.Refer to Table Status register at theend of this log report for a descriptionof each bit.

ALARMS Indicates thealarm(s) associatedwith the clocks.

Variable Fitcode refers to the fault code for theinternal or external oscillator. If novalue appears, there is no alarm.Possible values are:

HTR Variable Indicates internal oscillator heaterfault.




Description

PWR Variable Indicates failure of a clock cardpower converter.

PHSE Variable Indicates failure of phase detectorcircuitry.

TUN Variable Indicates the clock is near the end ofits tuning range.

EXT Variable Indicates active clock in master-external office is in state FREE, orfailure of the external referencesignal.

ALM 0 Variable Indicates failure of the externalreference oscillator.

ALM 1 Variable Indicates failure of the power supplyof the emergency referenceoscillator.

BEAT Variable Indicates that the beat frequency ofthe two external reference signalshas too short a period.

TUN CTL 0000-FFFF Variable Indicates tuning control values ofclocks. Values appear as four-digithexadecimal numbers. Thehexadecimal values and theircorresponding frequencies are:

0000 Variable Indicates a frequency lower thanmiddle by a FSR of-1.5 x 10-6.

8000 Variable Indicates the center frequency,nominally 10.240 MHz.

FFFF Variable Indicates a frequency higher thanmiddle by a FSR of +1.5 x 10-6.

Variable To obtain frequency shift ratio (FSR)subtract the nominal frequency fromthe current frequency. Divide thedifference by the center frequency.

PHASE REG 0000-FFFF, 0000-FFFF

Variable Indicates phase register values ofclocks. The system gives the valuesin four-digit hexadecimal numbers.Convert the numbers to binary. Tointerpret each of the bits refer toTable Phase register at the end of logreport SYNC101.

LNK0,LNK LCK = LOCKED Variable Indicates the locked state, for theDS-1 links used for synchronization.

SYNC102 351



Description

SMP = SAMPLING Variable Indicates the state for either of theDS-1 links used for synchronization issampling.

IDL = IDLE Variable Indicates the timing link is in-servicebut will not send samples.

OOS Variable Indicates the timing link is out ofservice.

SLIP CT 0-32,768 Variable Slip count of the timing link from thetime the clock system was initiallysynchronized.

PREV STATE LCK = LOCKED Variable Indicates the previous state of eitherDS-1 link used for synchronizationwas locked.

SMP = SAMPLING Variable Indicates the previous state of eitherDS-1 link used for synchronizationwas sampling.

IDL = IDLE Variable Indicates the timing link is in-servicebut does not send samples.

Active message exampleSYNC102 MAR08 15:16:07 9573 INFO STAT CLOCK SWITCH

INACTIVE FREE

ACTIVE CLOCK = 1

CLK0,CLK1: STATE = Lkng,Sync STAT REG= A000,3100 ALARM=

,

TUNING CONTROL = 6F84,7700 PHASE REG= 327F,B251

LNK0,LNK1: STATE = Smp,Lck SLIP CT= 0,0

PREV STATE = Id1,Lck



SYNC104The Synchronous Clock (SYNC) subsystem generates log reportSYNC104 when the system fails either an automatic or manual test.



Remedial actionThere is no action required. The following list identifies the tests in theFAILING TESTS:

• Bit 0 -- Test for trap on clock address read or write.

• Bit 1 -- Data path test, loop-back register.

• Bit 2 -- Reset error flags.

• Bit 3 -- Inhibit clock interrupts.

• Bit 4 -- Oscillator fail test.

• Bit 5 -- Reset errors.

• Bit 6 -- Frame pulse fail.

• Bit 7 -- Reset errors.

• Bit 8 -- Tuning control write error.

• Bit 9 -- Time-out too soon.

• Bit 10 -- No time-out.

• Bit 11 -- Write protect not on.

• Bit 12 -- Cannot disable write protect.

• Bit 13 -- Tuning control read/write test.

• Bit 14 -- Phase address bit not toggling.

• Bit 15 -- Beat frequency detector test.

• Bit 16 -- Frequency shift test.

• Bit 17 -- Reset of external select failed (master external reference only).

• Bit 18 -- Set of external select failed (master external reference only).

• Bit 19 -- External fail test (master external reference only).

• Bit 20 -- Reset errors (master external reference only).

• Bit 21 -- Tuning control test.




• Bit 25 -- Synchronize clock to active.


SYNC104 353


Format*SYNC104 mmmdd hh:mm:ss ssdd FLT CLOCK n FAILS TESTS

CLOCK UNDER TEST = clkno

FAILING TESTS = bbbbbbbb bbbbbbbb

bbbbbbbb bb


VariableDescription

FLT CLOCK n FAILSTESTS

0,1 Variable Indicates that the clock indicatedfailed an automatic or a manual test.

CLOCK UNDERTEST

0,1 Variable Number of the active centralmessage controller (CMC) clock.

FAILING TESTS 0,1 Variable A field of 26 bits with value of 1 or 0.The bits are numbered from left toright, 0 to 25. A value of 1 in any bitposition indicates that test failed.

Active message example*SYNC104 MAY31 07:45:22 2112 FLT CLOCK 0 FAILS TESTS

CLOCK UNDER TEST = 0

FAILING TESTS = 10010010 01111001

01101101 11



SYNC201The Synchronous Clock (SYNC) subsystem generates log reportSYNC201. The SYNC generates this report when the subsystem updatesthe tuning control. The subsystem updates the tuning control, digital analogconverter (DAC) register, in a clock for an ECORE switch. The tuningcontrol change causes a clock frequency change.



Remedial actionThere is no action required. Log report SNC201 provides information onthe synchronous clocks that you can use with the trouble clearingprocedures. The following list identifies the reasons:

• Manual request

• Clock CMU DAC failure

• Central and local data mismatch

• DAC upper limit was reached

• DAC lower limit was reached

• Timing link returned to service

• Office configuration changed

• Failed to reach synchronization

• Sample range exceeded - check source

• Not able to start PM sampling

• No in-service timing links available

• No primary PM samples received

• No alternate PM samples received

• A slip occurred while in sync

• Local time-out threshold was reached


FormatSYNC201 mmmdd hh:mm:ss ssdd INFO eventxt

CLOCK = n clktxt

CLK0, CLK1: State=synctxt, synctxt Tuning Control =hhhh,hhhh

rsntxt

SYNC201 355



VariableDescription

eventxt Manual DAC load Variable Manual action use of the commandADJDOWN or ADJUP on theSYNCLK level changed the control ofthe tuning. The DAC in the NT3X15clock card was adjusted. The DACwas adjusted either down or up thespecified number of steps, oradjusted to the center value.

DAC load error Variable Indicates the DAC was loaded with avalue in error.

DAC limit reached Variable Indicates the DAC was adjusted tothe limit.

DAC load fail Variable Indicates the DAC load failed.CLOCK 0,1 Variable Indicates which clock caused the

generation of the report.clktxt Master clock, clock

slaveVariable Indicates if the clock that caused the

generation of the report was themaster or the slave clock.

CLK0, CLK1: Constant Variable Indicates that the system gives thefollowing values for both clocks.

State FREE (free running),SYNC(synchronized),LKNG (linking)

Variable Indicates the state of thesynchronous clocks.

Tuning Control 0000-FFFF, 0000-FFFF

Variable Label for tuning control values ofclocks. Values appear for each clockin four hexadecimal digits. Thehexadecimal values and theircorresponding frequencies are:

0000 Variable A frequency lower than middle by afrequency shift ratio (FSR) of -1.5 x10-6.


FFFF Variable A frequency higher than middle by aFSR of + 1.5 x 10-6.




Description

Variable To obtain FSR subtract the nominalfrequency from the current frequency.Divide the difference by the centerfrequency.

rsntxt Symbolic text Variable Provides a reason for the generationof this log report. Refer to TableSYNC log reasons list at the end ofthis log report.

Active message exampleSYNC201 SEP24 05:12:36 6121 INFO Manual DAC Load

CLOCK 0 Master Clock

CLK0,CLK1: State = Free,Sync Tuning Control = 8000,8000

Manual Request



SYNC203The Synchronous Clock System (SYNC) subsystem generates log reportSYNC203. This action occurs when the subsystem detects a problem in aclock, and the office is in the base design.

The SYNC203 log is an FLT log generated to convey

• a timing-link fault

• a clock fault

• office dropped synchronization

• digital-to-analog convertor (DAC) for the system clock

Remedial actionIf the CLOCK or SPAN alarm appears under the MS header of the alarmbanner, clear the alarm. To clear the alarm, use the correct procedureinAlarm Clearing Procedures. If no CLOCK or SPAN alarm is present,contact the next level of support.

If the system started synchronization again and failed, attemptsynchronization again manually.

SYNC203 357



Format*SYNC203 mmmdd hh:mm:ss ssdd FLT System CNFG: SYNC Event

Failure

CLOCK <clock_no> <mastership> <sync_log_event>

CLK0,CLK1: State = <sst0>,<sst1> Tuning Control=<dac0>,<dac1>

Alarm = <alm0>, <alm1>

LK0,LK1 : State = <tlk0>, <tlk1> Slip Count = <tls0>, <tls1>

Carrier = <cst0>, <cst1>

System Fault: <system fault description>

Timing Ref 0 Fault: <timing ref fault description>


Internal Clock 0 Fault: <internal fault description>


Remote Clock 0 Fault: <remote fault description>



VariableDescription

dac0, dac1 0000-FFFF Variable The label for the tuning control valuesof the clocks. Values have fourhexadecimal digits for each clock.

Alarm = Constant Variable




Description

almo, alm1 Htr, Pwr, Phse, Sub,Tun, Ext, Al0, Al1,Beat, MM, . (dot)

Variable Identifies the alarms for the clocks.The alarm codes are as follows:

• Htr indicates an internal oscillatorheater fault.

• Pwr indicates the failure of aclock card power converter.

• Phse indicates a failure of phasedetector circuits.

• Sub indicates a problem with thesubsystem clock.

• Tun indicates the clock is close tothe end of the tuning range.

• Ext Indicates the clock in themaster-external office is in stateFREE, or the external referencesignal failed.

• Al0 indicates the externalreference oscillator failed.

• Al1 indicates the power supply ofthe emergency referenceoscillator failed.

• Beat indicates the beat frequencyof the two external referencesignals has too short a period.

• MM indicates a clock datamismatch between the CM andMS.

• A dot (.) indicates there is noalarm.

LK0,LK1 Constant Variabletlk0, tlk1 Lck (locked), Smp

(sampling), Idl (idle)Variable The states of the two DS-1 links used

for synchronization.Slip Count Constant Variabletls0, tls1 0 to 32, 768 Variable The total slip count for the timing link

after clock system was firstsynchronized.

NA Variable In the case of OC-3 line-timing mode,indicates slip count is not available.

Carrier = Constant Variable

SYNC203 359



Description

cst0, cst1 Variable Indicates the state of the carriers.The carrier states are as follows:

• MBsy indicates the carrier ismanual busy.

• SBsy indicates the carrier issystem busy.

• OOS indicates the carrier is outof service.

• IS indicates the carrier is inservice.

System Fault: Constant Variablesystem faultdescription

Text Variable The system sync defects that arepresent.

Timing Ref n Fault n = 0 or 1 Variabletiming ref faultdescription

Text Variable The timing reference defects that arepresent.

Internal Clock n Fault n = 0 or 1 Variableinternal faultdescription

Text Variable The internal clock defects that arepresent.

Remote Clock nFault

n = 0 or 1 Variable

remote faultdescription

Text Variable The remote clock defects that arepresent.

INFO System CNFG:SYNC Event Failure

Constant Variable Indicates that a clocking faultcondition is present.

CLOCK Constant Variableclock_no 0, 1 Variable The number of the clock that caused

the system to generate the report.mastership Master Clock, Slave

ClockVariable Identifies the clock that caused the

system to generate the report.sync_log_event Text Variable The clock synchronization event that

caused the system to generate thelog report.

CLK0,CLK1 Constant Variable Indicates that the followinginformation is for Clock 0 and Clock1.

State = Constant Variable




Description

sst0, sst1 Free (free-running),Sync (synchronized),Lkng (linking)

Variable The synchronization state of thecentral message controller (CMC)clocks.

Tuning Control = Constant Variable

Active message example*SYNC203 JAN12 16:23:25 5500 FLT System CNFG: SYNC Eventfailure

CLOCK 1 Master Clock Unexpected sample

CLK0,CLK1: State = Sync ,Sync Tuning Control = 0800, 0800

Alarm = Htr ,Sub

LK0 ,LK1: State = Lck ,Idl Slip Count = 1,7

Carrier = . , MBsy

Subsystem clock failure



SYNC204The Synchronous Clock System (SYNC) subsystem generates SYNC204when the tuning control (DAC Register) in a clock updates. The tuningcontrol change causes a clock frequency change.

Remedial actionThere is no action required. This report provides information on thesynchronous clocks that you can use in addition to procedures to solveproblems. The following list identifies the SYNC clock failure causes:

• Clock failed to SYNC.

• Phase limit exceeded .

• Sample range exceeded.

• Stuck samples.

• Phase range error.

• Ext ref select fail.

SYNC204 361


• Ref oscillator not selected.

• Ref oscillator fail.

• Beat frequency det

• Phase counter error.

• Multiple bad samples.

• Man clock test fail.


FormatSYNC204 mmmdd hh:mm:ss ssdd Clock Failed to Sync

CLOCK clkno mastership

REM0,REM1: State = synst, synst Tuning Control = hhhh, hhhh

CLK0,CLK1: State = synst, synst Tuning Control = hhhh, hhhh

log_reason


VariableDescription

Clock Failed to Sync Constant Variable Indicates that an error conditionexists

CLOCK 0,1 Variable Identifies the clock that generatedthis log report.

clktxt Master clock, slaveclock

Variable Identifies the clock as the master orthe slave that caused the system togenerate this report.

REM0 Constant Variable Identifies the remote clock to whichstate and tuning control fields, andthe associated values, belong.

State FREE SYNC LKNG Variable Indicates if the synchronization stateof each remote clock is free-running,synchronized, or linking.

Tuning Control 0000-FFFF Variable Refers to the label for the tuningcontrol values of the clocks. Thehexadecimal values and theirassociated frequencies are:




Description

0000 Variable A frequency lower than the center byan FSR of-1.5 x 10&sm.&s6.


FFFF Variable A frequency higher than the center byan FSR of+1.5 x 10&sm.&s6.10&sm.&s6. To obtain the frequencyshift ratio, subtract the nominalfrequency from the actual frequency,and divide the difference by thecenter frequency.

Alarm Variable Indicates the type of alarm for theclocks. Alarm values are:

HTR Variable Indicates a defect in the internalheater.

PWR Variable Indicates a failure of a clock cardpower converter.

PHSE Variable Indicates an error in the phasedetector circuits.

TUN Variable Indicates that the clock is close to theend of the tuning range of the clock.

EXT Variable Indicates that the master-externaloffice is in state FREE, or that theexternal reference signal failed.

ALM 0 Variable Indicates that the external referenceoscillator failed.

ALM 1 Variable Indicates that the power supply of theemergency reference oscillator failed.

BEAT Variable Indicates that the beat frequency ofthe external reference signals has tooshort a period.

MM Variable(blank) Variable If no value appears after ALARM,

there is no defect.LNL0,LNK1. Constant Variable Identifies the link that fields state, slip

count, and carrier, and theassociated values belong.

State LCK SMP IDL Variable Indicates if the links used forsynchronization are locked, sampling,or idle.

SYNC204 363



Description

SLIP CT 0-9,0-9 Variable Indicates the number of times the linkwas out of sync after the time of thelast synchronization.

Carrier SysB ManB OOS .(dot)

Variable Indicates if the carriers are systembusy, manually busy, out of service,or in service.

log_reason Variable Provides the cause for the SYNCclock failure. Refer to Table SYNCclock failure causes at the end of thislog report.

Active message exampleSYNC204 SEP24 05:12:36 6121 Clock Failed to Sync

CLOCK 0 Master Clock

REM0,REM1: State = Free, sync Tuning Control = 0800,0800

CLK0,CLK1: State = synst,synst Tuning Control= 0800,0800

No response from Message Switch



SYNC205The system generates the SYNC205 log report when the system detects asynchronization problem in an office in the remote synchronizationconfiguration.

An office in the remote synchronization configuration is equipped with aStratum 2 or Stratum 2.5 clock and NT9X53AC or NT9X53AD clock cards.

Match the log message in the following list:

• Clock unable to sync within time limit -- Contact the next level ofsupport

• Phase error limit exceeded -- Contact the next level of support

• Stuck phase comparator detected -- Contact the next level of support

• Sync central/Local data mismatch -- No action required

• Sync/maintenance mastership mismatch -- No action required



• Sync system dropped sync within the last hour -- No action required

• Sync system switched carrier within the last hour -- No action required

• Sync system master within the last hour -- No action required

Match the timing ref fault description in the following list:

• Sample continuity check failed -- Contact the next level of support

• Sample continuity check warning -- No action required

• Sample maximum-minimum check warning -- No action required

• Sample maximum-minimum check failed -- Contact the next level ofsupport

• Sample range check warning -- No action required

• Sample range check failed -- Contact the next level of support

• Samples timed out in central -- No action required

• Samples timed out in local -- No action required

• Slips reported on this link -- No action required

• Unable to make link active -- Contact the next level of support

• Unable to start link sampling -- No action required

Match the message in the internal fault description field:

• DAC read failures exceed threshold -- No action required

• DAC write failures exceed threshold -- Contact the next level of support

Match the message in the remote fault description field:

• Clock unable to sync within time limit -- No action required

• Faulty phase report -- No action required

• Firmware and software PLL modes mismatch -- No action required

• Unable to change remote PLL mode -- No action required

• Unable to query remote PLL data -- Contact the next level of support

• Unable to start remote phase reports -- No action required

• Unable to stop remote phase reports -- No action required

Remedial actionFor a list of user actions for different log messages, refer to the tables inthe Additional information section.

SYNC205 365



FormatSYNC205 mmmdd hh:mm:ss ssdd INFO Reference CNFG: SYNC Info

CLOCK <clock_no> <mastership> <sync_log_event>

REM0, REM1: State = <rst0>, <rst1> Tuning Control = <rdc0>,<rdc1>

CLK0, CLK1: State = <sst0>, <sst1> Tuning Control = <dac0>,<dac1>


LK0, LK1: State = <tlk0>, <tlk1> Slip Count = <tls0>, <tls1>


<log_reason>

System Fault: <system_fault_description>

Timing Ref 0 Fault: <timing_ref_fault_description>

Timing Ref 1 Fault: <timing_ref_fault_description>

Internal Clock 0 Fault: <internal_fault_description>

Internal Clock 1 Fault: <internal_fault_description>

Remote Clock 0 Fault: <remote_fault_description>

Remote Clock 1 Fault: <remote_fault_description>


VariableDescription

INFO ReferenceCNFG: SYNC Info

Fixed Variable Indicates the system detected asynchronization problem

CLOCK Fixed Variableclock_no 0 or 1 Variable Identifies the plane number of the

affected clockmastership Master Clock, Slave

ClockVariable Indicates whether the affected clock

is the master clock or the slave clock




Description

sync_log_event Text string Variable Identifies the clock synchronizationevent that caused the log report

REM0, REM1 Fixed Variable Indicates the information in the nextfield is for remote clock 0 and remoteclock 1

State = Fixed Variable Indicates that clock state informationfollows

rst0, rst1 Free (free-running),Sync (synchronized),Lkng (linking)

Variable Indicates the synchronization state ofthe remote clocks

Tuning Control = Fixed Variable Indicates that tuning controlinformation follows

rdc0, rdc1 0000 to FFFF Variable Indicates the tuning control values ofthe remote clocks. The values areshown as four-digit hexadecimalnumbers

CLK0, CLK1 Fixed Variable Indicates the information that followsis for clock 0 and clock 1

sst0, sst1 Free (free-running),Sync(synchronized),Lkng(linking)

Variable Indicates the synchronization state ofthe message switch (MS) clocks

dac0, dad1 0000 to FFFF Variable Indicates the tuning control values ofthe clocks. The values are shown asfour-digit hexadecimal numbers.

Alarm = Fixed Variable Indicates alarm information followsalm0, alm1 Htr, Pwr, Phse, Sub

Tun Ext A10 AMBeat MM . (dot)

Variable Identifies the alarms associated withthe clocks. The alarm codes are asfollows:

• Htr indicates an internal oscillatorheater fault

• Pwr indicates the failure of aclock card power converter

• Phse indicates a malfunction ofphase detector circuitry

• Sub indicates a problem with thesubsystem clock

• Tun indicates the clock is almostout of its tuning range

SYNC205 367



Description

• Ext indicates the state of theclock in the master-external officeis free running, or the externalreference signal has failed

• AI0 indicates the externalreference oscillator has failed

• AI1 indicates the power supply ofthe emergency referenceoscillator has failed

• Beat indicates the beat frequencyperiod of the two externalreference signals is too short

• MM indicates a clock datamismatch between the CM andMS

• A dot (.) indicates there is noalarm

LK0, LK1 Fixed Variable Indicates DS-1 synchronization linkinformation follows

This entry appears in the log reportonly if field OFF_CONF in tableSYNCLK is datafilled as SLAVE.

tlk0, tlk1 Lck (locked), Smp(sampling), Idl (idle)

Variable Indicates the state of the two DS-1links used for synchronizing

This field appears in the log reportonly if field OFF_CONF in tableSYNCLK is datafilled as SLAVE.

Slip Count Fixed Variable Indicates that slip count informationfollows


tls0, tls1 0 to 32 768 Variable Indicates the accumulated slip countfor the timing link since the clocksystem was synchronized


Carrier = Fixed Variable Indicates carrier state informationfollows




Description


cst0, cst1 MBsy, SBsy, OOS, .(dot)

Variable Indicates the state of the carriers.The carrier states are as follows:

• MBsy indicates the carrier ismanual busy

• SBsy indicates the carrier issystem busy

• OOS indicates the carrier is outof service

• A dot (.) indicates the carrier is inservice


log_reason Text string Variable Describes the fault that caused thelog report to be generated

System Fault: Fixed Variable Indicates fault descriptions followsystem_fault_description

Text string Variable Describes the current systemsynchronization faults

Timing Ref n Fault Fixed except that n =0 or 1

Variable Indicates timing reference faultinformation follows

timing_ref_fault_description

Text string Variable Describes the timing reference faults

Internal Clock n Fault Fixed except that n =0 or 1

Variable Indicates internal clock faultinformation follows

internal_fault_description

Text string Variable Describes the internal clock faults

Remote Clock nFault

Fixed except that n =0 or 1

Variable Indicates remote clock faultinformation follows

remote_fault_description

Text string Variable Describes the remote clock faults

Active message exampleSYNC205 SEP24 16:23:25 6000 INFO Reference CNFG: SYNC Info

CLOCK 1 Master Clock Unexpected sample

REM0, REM1: State = Sync, Sync Tuning Control = 0800, 0800

CLK0, CLK1: State = Sync, Sync Tuning Control = 0800, 0800

SYNC205 369


Alarm = Htr, Sub

LK0, LK1: State = Lck, Idl Slip Count = 1,7

Carrier = . , MBsy

Subsystem clock failure

Timing Ref 0 Fault: Sample continuity check failed



SYNC206The Synchronous Clock System (SYNC) subsystem generates SYNC206.The subsystem generates SYNC206 when the subsystem detects an errorcondition in a clock and the office is in remote SYNC design. The SYNCdesign indicates the clock type is Stratum2/2.5 and the switch hasNT9X53AA or NT9X53AB.

Remedial actionIf the CLOCK or SPAN alarm appears under the MS header of the alarmbanner, clear the alarm. To clear the alarm, use the correct procedureinAlarm Clearing Procedures. If no CLOCK or SPAN alarm is present,contact the next level of support.

If the second synchronization the system initiates fails, attempt a manualsynchronization.


FormatSYNC205 mmmdd hh:mm:ss ssdd INFO Reference CONFG: SYNC EventFailure

CLOCK <clock_no><mastership> <sync_log_event>

REM0 ,REM1: State = <rst0>,<rst1> Tuning Control=<rdc0>,<rdc1>

CLK0 ,CLK1: State = <sst0>,<sst1> Tuning Control=<dac0>,<dac1>




LK0 ,LK1: State = <tlk0>, <tlk1> Slip Count = <tls0>, <tls1>


System Fault: <system fault description>






Remote Clock 1


VariableDescription

INFO ReferenceCNFG:SYNC EventFailure

Constant Variable Indicates that a synchronizationevent occurred.

CLOCK Constant Variableclock_no 0, 1 Variable The number of the clock that caused

the subsystem to generate the report.mastership Master Clock, Slave

ClockVariable Identifies the clock that caused the

subsystem to generate the report.sync_log_event Text Variable The clock synchronization event that

caused the subsystem to generatethe log report.

REMO ,REM1 Constant Variable Indicates the information that followsis for Remote Clock 0 and RemoteClock 1.

Tuning Control = Constant Variabledac0, dac1 0000-FFFF Variable The label for tuning control values of

clocks. Values have fourhexadecimal digits for each clock.

rst0, rst1 Free (free-running),Sync (synchronized),Lkng (linking)

Variable The synchronization state of theremote clocks.

CLK0 ,CLK1 Constant Variable Indicates the information that followsis for Clock 0 and Clock 1.

SYNC206 371



Description

State = Constant Variablesst0, sst1 Free (free-running),

Sync (synchronized),Lkng (linking)

Variable The synchronization state of thecentral message controller (CMC)clocks.

Alarm = Constant Variablealm0, alm1 Variable Identifies alarms for the clocks. The

alarm codes are as follows:

• Htr indicates an internal oscillatorheater defect.

• Pwr indicates the failure of aclock card power converter.

• Phse indicates a failure of phasedetector circuits.

• Sub indicates a problem with thesubsystem clock.

• Tun indicates the clock is close tothe end of the tuning range.

• Ext indicates the clock in themaster-external office is in stateFREE, or the external referencesignal failed.

• AI0 indicates the externalreference oscillator failed.

• AI1 indicates the power supply ofthe emergency referenceoscillator failed.

• Beat indicates the beat frequencyof the two external referencesignals has too short a period.

• MM indicates a clock datamismatch between the CM andMS.

• A dot (.) indicates there is noalarm.

LKO ,LK1 Constant Variabletlk0, tlk1 Lck (locked), Smp

(sampling), IdI (idle)Variable The state of DS-1 links used for

synchronization.Slip Count Constant Variable




Description

tls0, tls1 0 to 32, 768 Variable Indicates the total slip count for thetiming link after clock system wassynchronized.

Carrier = Constant Variablecst0, cst1 Variable Indicates the state of the carriers.

The carrier states are as follows:

• MBsy indicates the carrier ismanual busy.

• SBsy indicates the carrier issystem busy.

• OOS indicates the carrier is outof service.

• IS indicates the carrier is inservice.

System Fault: Constant Variablesystem faultdescription

Text Variable The system sync defects that arepresent.

Timing Ref n Fault n = 0 or 1 Variabletiming ref faultdescription

Text Variable The timing reference defects that arepresent.

Internal Clock n Fault n = 0 or 1 Variableinternal faultdescription

Text Variable The internal clock defects that arepresent.

Remote Clock nFault

n = 0 or 1 Variable

remote faultdescription

Text Variable The remote clock defects that arepresent.

Active message example*SYNC205 JAN12 16:23:25 5500 INFO Reference CNFG: SYNC EventFailure *SYNC205 JAN12 16:23:25 5500 INFO Reference CNFG:SYNC Event Failure

CLOCK 1 Master Clock Unexpected sampleCLOCK 1 Master ClockUnexpected sample

REM0,REM1: State = Sync ,Sync Tuning Control = 0800,0800REM0,REM1: State = Sync ,Sync Tuning Control = 0800,0800

SYNC206 373


CLK0,CLK1: State = Sync ,Sync Tuning Control = 0800,0800CLK0,CLK1: State = Sync ,Sync Tuning Control = 0800,0800

Alarm = Htr ,SubAlarm = Htr ,Sub

LK0 ,LK1: State = Lck ,Idl Slip Count = 1,7LK0 ,LK1: State =Lck ,Idl Slip Count = 1,7

Carrier = . ,MBsy.Carrier = . ,MBsy.

Timing Ref 0 Fault: Sample continuity check failedTiming Ref0 Fault: Sample continuity check failed



SYNC208There is no explanation.

Remedial actionn/a


FormatFP503 mmmdd hh:mm:ss ssdd INFO Device State Change

Location: <object description>

REASON: <change reason>

FROM: <basic> <qualif>DRIVE STATE: <drivest>

TO:<basic> <qualif> DRIVE STATE:<drivest>

<test status>

Active message exampleFP503 SEP05 18:14:33 4827 INFO Device State Change

Location: FP 2 DEVICE 1 (DK) SCSI BUS 0



REASON: Change of state of associated entity

FROM: InSv ( Isolated ) DRIVE STATE: Unknown

TO: InSv DRIVE STATE: On Line



SYNC209The Synchronous Clock System (SYNC) subsystem generates SYNC209when the subsystem detects an error condition in a clock on a SuperNode.

Remedial actionTest the clock that has faults or refer the problem to the next level ofsupport.


FormatSYNC209 mmmdd hh:mm:ss ssdd FLT Reference CNFG: SYNC Event

Failure

CLOCK n clktxt Remote : log_event

REMO,REM1: State = syncst,syncst Tuning Control = hhhh,hhhh

CLK0,CLK1:State = syncst,syncst Tuning Control = hhhh,hhhh

Alarm = fltcode,fltcode

LK0 ,LK1 : State = linkst,linkst Slip Count = n,n

Carrier = carrst,carrst

log_reason

SYNC209 375



VariableDescription

EXT Variable Indicates that the master externaloffice is in state FREE, or theexternal reference signal failed.

ALM 0 Variable Indicates that the external referenceoscillator failed.

ALM 1 Variable Indicates that the power supply of theemergency reference oscillator failed.

BEAT Variable Indicates that the beat frequency ofthe external reference signals has tooshort a period.

MM Variable This field does not apply.(blank) Variable If no value appears after ALARM,

there is no fault.LK0,LK1 Constant Variable Identifies the link that fields state, slip

count, and carrier and thecorresponding values for these fields.

State LCK SMP IDL Variable Indicates the links used forsynchronization as locked, sampling,or idle.

SLIP CT 0-9, 0-9 Variable Indicates the number of times thatthe link slips out of sync, after thetime of the last synchronization.

Carrier SysB,ManB,OOS, .(dot)

Variable Indicates if the carriers are systembusy, manually busy, out of service,or in service.

log_reason Text Variable Provides the cause for the SYNCclock failure.

FLT ReferenceCNFG: SYNC EventFailure

Constant Variable Indicates a fault condition that ispresent.

CLOCK n 0,1 Variable Identifies the clock that generatedthis log report.

clktxt Master Clock, SlaveClock

Variable Indicates the clock that caused thegeneration of this report as themaster or the slave clock.

FLT ReferenceCNFG: SYNC EventFailure

Constant Variable Indicates that an error conditionexists

clktxt Master Clock, SlaveClock

Variable Identifies the clock that caused thegeneration of this report as themaster or the slave clock.




Description

log_event Text Variable Identifies the clock synchronizationevent that caused the generation ofthis log.

REM0,REM1 Constant Variable Identifies the remote clock to thestate field, and the tuning controlfield, and the values associated withthese fields.

State Character string Variable Indicate if the synchronization stateof each remote clock is free-running,synchronized or linking.

Tuning Control 0000-FFFF Variable Refers to the label for the tuningcontrol values of the remote clocks.The hexadecimal values and theassociated frequencies are:

0000 Variable Indicates a frequency lower than thecenter by a frequency shift ratio(FSR) of -1.5 x 10&sm.&s6.&sm.

8000 Variable Indicates the center frequency,nominally 10.240 MHz.

FFFF Variable Indicates a frequency higher than thecenter by an FSR of +1.5 x10&sm.&s6. 10&sm.&s6. To obtainthe frequency shift ratio, subtract thenominal frequency from the actualfrequency, and divide the differenceby the center frequency.

CLK0,CLK1 Constant Variable Identifies the clock to the followingfields: state, tuning control, alarm,and the values associated with thesefields.

Alarm Variable Indicates the type of alarm for theclocks. Alarm values are:

HTR Variable Indicates an internal oscillator heaterfault.

PWR Variable Indicates failure of a clock cardpower converter.

PHSE Variable Indicates a failure of phase detectorcircuits.

TUN Variable Indicates that the clock is close to theend of the tuning range of the clock.

Active message exampleSYNC209 JAN24 05:12:05 0600 FLT Reference CNFG: SYNC Event

SYNC209 377


Failure

CLOCK 0 Slave Clock Remote : Drop Sync

REM0,REM1: State = Free,Free Tuning Control = 0858,0841

CLK0,CLK1: State = Sync,Sync Tuning Control = 07E7,07E1

Alarm = .,.

LK0 ,LK1 : State = Smp ,Smp Slip Count = 0,0

Carrier = .,.

MS node is busied out



TCAP100Example 1

The Transaction Capability Application Part (TCAP) subsystem generatesTCAP160 when these conditions occur:

• If the Freephone Services sends a reject or report error, the subsystemgenerates a TCAP report to print the error message.

• If the SSP receives a response message with a call that is notabandoned, from the SCP.

• If the subsystem receives a one-way or query package, the subsystemgenerates TCAP100 to print the business services database (BSDB)message.

• If the BSDB response message contains an invalid responsetransaction ID, the subsystem generates TCAP100 to print the BSDBmessage.

• For any response package, return error, or reject component, thesubsystem generates TCAP100 to print the return error or rejectmessage.

• If the private virtual network (PVN) sends a return error, reject, orReport Error, the subsystem generates TCAP100 to print the errormessage.

• For every Originating Line Number Screening (OLNS) TCAP responsepackage that the Digital Multiplex System (DMS) switch receives fromthe OLNS line information database (LIDB) that contains:



• a return error component

• a return error component with a problem data parameter

• a reject component

• a various data error

The TCAP interface supports the residence name database designdescribed in TR-NWT-001188, CLASS Calling Name Delivery GenericRequirements. The CNAMD feature provides the name of the calling partyto the customer premises equipment (CPE) of the called party fordisplay.Example 2 - TOPS07

The TCAP subsystem generates this log when the subsystem receives aTOPSLNP TCAP package from the LNP SCP database. The packagecontains a return error component.

This log does not occur if the LNPVER Tool performed the query.

This log only appears with the TOPSLNP information in a LET PCLenvironment.Example 3 - TOPS07

The subsystem generates TOPS07 when the subsystem receives a TCAPresponse package from the LNP SCP database that contains a rejectcomponent.

This log does not occur if the LNPVER Tool performed the query.

This log only appears with the TOPSLNP information in a North Americanenvironment.Example 4 - TOPS07

The subsystem generates this log when the subsystem receives an abortpackage from the LNP SCP database.

This log does not occur if the was the LNPVER Tool performed the query.

This log only appears with the TOPSLNP information in a LET PCLenvironment.Example 5 - TOPS07

The subsystem generates TOPS07 when the subsystem receives aTOPSLNP TCAP package from the LNP SCP database that contains avarious data error.

This log does not occur if the LNPVER Tool performs the query.

This log only appears with the TOPSLNP information in a LET PCLenvironment.

TCAP100 379


The following list provides reasons that the subsystem generatesTCAP100.

• CNAMD REJECT RECEIVED -- Indicates the subsystem received aCNAMD TCAP response package that contains a reject component.The subsystem received the package from the central residence namedatabase.

• CNAMD RETURN ERROR COMPONENTS -- Indicates the subsystemreceived from a CNAMD TCAP response package that contains areturn error component. The subsystem received the package from adatabase.

• CNAMD RETURN ERROR RECEIVED -- Indicates that the CNAMDTCAP response package received from the central residence namedatabase contains a return error. The central residence name databasecannot return the requested name information correctly. The text doesnot apply to return error components received in response to TCAPquery with permission (QWP) packages. The subsystem sent theseTCAP QWP packages with the TESTSS CNAMD database verificationcommand. The terminating switch sends a TCAP QWP package to thecentral database to request the name information.

• CNAMD VERIFICATION QUERY SENT -- Indicates that the systemsent a CNAMD TCAP QWP package with a reject component to thecentral residence name database. The subsystem used the TESTSSCNAMD database verification command to send the package.

• CNAMD VERIFICATION RESPONSE RCVD -- Indicates thesubsystem received the CNAMD TCAP response package in responseto a CNAMD TCAP QWP package sent. The system uses the TESTSSCNAMD database verification command to send the package.

• CONVERSATION SENT BY SSP -- Indicates that the verificationfeature sent a conversation message to the BSDN. This event normallyoccurs after the verification feature collects personal identificationnumber (PIN) or authorization code digits.

• DN VALIDATION REJECT MSG RECEIVE -- Indicates invalid directorynumber (DN) options entered in the service order.

• NETRAG SEND FAILED -- Indicates the NETRAG application sent afailure message. The message appears in hexadecimal bytes in thelog.

• OLNS RETURN ERROR RECEIVED -- This reason indicates that theDMS switch received an OLNS return error component.

• OLNS RETURN ERROR WITH PD RCVD -- This reason indicates thatthe DMS switch received a OLNS return error component with problemdata.

• OLNS REJECT RECEIVED -- This reason indicates that the DMSswitch received a OLNS reject component.



• OLNS DATA ERROR IN RESPONSE -- This reason indicates that theDMS switch received a miscellaneous error.

• PACKAGE TYPE NOT SUPPORTED PVN -- Indicates that the PVNapplication received a query package from the database. The receivedmessage appears in hexadecimal bytes in the log.

• PVN RECEIVED RETURN ERROR -- Indicates the PVN applicationreceived a database with a return error component. The receivedmessage appears in hexadecimal bytes in the log.

• PVN SENT REJECT -- Indicates the PVN application sent a messagewith a reject component to the database. The message appears inhexadecimal bytes in the log.

• PVN SENT REPORT ERROR -- Indicates the PVN application sent amessage with an invoke component, procedure report error, to thedatabase. The message appears in hexadecimal bytes in the log.

• PVN SENT RETURN ERROR -- Indicates that the PVN applicationsent a message with a return error component to the database. Themessage appears in hexadecimal bytes in the log.

• RESP MSG WITH NON-ABANDONED CALL -- Indicates that thefreephone application received a response message with a call that isnot abandoned. The received message appears in hexadecimal bytesin the log.

• RTRS ABORT RECEIVED -- Indicates an RTRS abort packagereceived.

• RTRS DATA ERROR IN RESPONSE -- Indicates an RTRS TCAPresponse package received from the Real-Time Rating Systemdatabase that contains a miscellaneous data error.

• RTRS REJECT RECEIVED -- Indicates an RTRS reject componentreceived.

• RTRS RETURN ERROR WITH PD RCVD -- Indicates an RTRS returnerror component with a problem data parameter received.

• TERMINATION MESSAGE SENT BY SSP -- Indicates that theverification feature received a request for termination information fromthe BSDB. Indicates the verification feature sent the terminationinformation to the BSDB.

• UNI MSG RECEIVED-PVN -- Indicates that the PVN applicationreceived a one-way package from the database. The message appearsin hexadecimal bytes in the log.

• UNRECOGNIZED TRID-PVN -- Indicates that the PVN applicationreceived a response / conversion message with an invalid transactionID. The message appears in hexadecimal bytes in the log.

TCAP100 381


• UNSOLICITED FREEPHONE CALL -- Indicates a call that the systemcannot complete because of an internal systems error, or the time-outvalue expired.

• VERIFICATION MESSAGE SENT FROM BSDB -- Indicates that theverification feature received a message of any type from the BSDB.

• VERIFICATION MESSAGE SENT BY SSP -- Indicates that theverification feature sent a query to the BSDB.

• RETURN ERROR RECEIVED -- Indicates a TOPSLNP Return Errorcomponent received.

• REJECT RECEIVED -- Indicates a Reject component received.

• ABORT RECEIVED -- Indicates a TOPSLNP Abort package received.

• ERROR IN RESPONSE -- Indicates a TOPSLNP TCAP packagereceived from the LNP SCP database that contains a miscellaneouserror. The log can cover conditions like the receipt of an AIN messagethat is not correct for TOPSLNP. A disconnect message is an exampleof an AIN message that is not correct.

• QVPN: MISTYPED PARAMETER RECEIVING OPERATION --Indicates that the QVPN TCAP application received a TCAP messagecontaining a mis-typed parameter from the far-end node. Analyze theCOMPONENT SET field to determine the exact error.

• QVPN: RECEIVED UNRECOGNIZED OPERATION -- Indicates thatthe QVPN TCAP application received a TCAP message containing anunrecognized operation from the far-end node. Analyze theCOMPONENT SET field to determine the exact error.

• QVPN:INVOKE ID MISMATCH RECEIVING OPERATION -- Indicatesthat the QVPN TCAP application received a TCAP message containinga Return Result or Reject component with an Invoke identifier that doesnot match the identifier of the previous Invoke component. Analyze theCOMPONENT SET field to determine the exact error.

• QVPN: UNEXPECTED PACKAGE TYPE -- Indicates that the QVPNTCAP application received a TCAP message with an unexpectedTCAP package type from the far-end node. Analyze the PKGTYP andCOMPONENT SET fields to determine the exact error.

• QVPN: RESOURCE LIMITATION AT PAN -- Indicates that the QVPNTCAP application received a TCAP message from the far-end node,but insufficient software resources were available to process themessage. Analyze other switch logs and OMs to determine the exacterror.

• QVPN: REMOTE OPERATION CANCELLED -- Indicates that theQVPN TCAP application received a TCAP message containing anAbort indication or a Reject component from the far-end node. Analyzethe COMPONENT SET field to determine the exact error.



• QVPN: UNRECOGNIZED COMPONENT -- Indicates that the QVPNTCAP application received a TCAP message containing anunrecognized component from the far-end node. Analyze theCOMPONENT SET field to determine the exact error.

• QVPN: UNRECOGNIZED OPERATION ID -- Indicates that the QVPNTCAP application received a TCAP message containing anunrecognized operation identifier from the far-end node. Analyze theCOMPONENT SET field to determine the exact error.

• QVPN: GENERAL DECODING FAILURE -- Indicates that the QVPNTCAP application received a TCAP message where the componentportion could not be decoded successfully. Analyze the COMPONENTSET field to determine the exact error.

• ISDNSS: LOST UDT -- Indicates that the ISDNSS TCAP frameworkreceived a TCAP message (an SCCP UnitData message) from the far-end node, but the UDT could not be delivered to any local TCAPapplication. Analyze the COMPONENT SET field and other switch logsand OMs to determine the exact problem.

Remedial actionThe reason textCNAMD RETURN ERROR RECEIVEDindicates the centralresidence name database cannot return the requested name informationcompletely. Analyze the component set of the log report data to determinethe error code.

The reason textCOMMAND REJECT RECEIVEDindicates the centralresidence name database cannot perform the database search. Thedatabase cannot perform the search because of a protocol problem foundin the TCAP QWP package. Analyze the component set of the log reportdata to determine the problem code.

If the reason text isCNAMD VERIFICATION QUERY SENT, analyze thecontents of the CNAMD TCAP QWP package sent. Use the TESTSSCNAMD database verification command to make sure TCAP standardsconform to specifications for the service switching point (SSP).

If the reason text isCNAMD VERIFICATION RESPONSE RCVD, analyzethe contents of the CNAMD TCAP response package. Analyze thepackage to make sure TCAP standards conform to specifications for thecentral residence name database.

In the OLNS environment, the subsystem generates this log for informationuse. There is no action that the operating company personnel to perform, ifthe reason text is:

TCAP100 383


OLNS RETURN ERROR RECEIVED, OLNS RETURN ERROR WITH PDRCVD, OLNS REJECT RECEIVED, or OLNS DATA ERROR INRESPONSE


FormatTCAP100 mmmdd hh:mm:ss ssdd INFO TCAP UDT MESSAGE

REASON: <rsntxt>

SUBSYSTEM NAME: TOPSLNP INSTANCE: 0

CALLED ADDR: INDICATOR=<indicator> SUBSYS=<subsys>

SSN=<ssn>

PC: NI=<ni> NETTYPE=<nettype> <aa>-<bb>-<cc>

CALLING ADDR: INDICATOR=<indicator>

SUBSYS=<subsys> SSN=<ssn>


CLASS=<class> SEQUENCE=<seq> OPTION=<opt> PRIORITY=<pri>

PACKAGE TYPE: <pkgtyp> RESPONSE ID: <response id>

COMPONENT SET: <component set>


VariableDescription

INFO TCAPMESSAGE

Constant Variable Indicates a report of transactioncapabilities application part (TCAP)unit data message.

REASON RSNTXT Variable Provides the reason the subsystemgenerated TCAP100. Refer to thetable at the end of this report.

SUBSYSTEM NAME Defined inC7LOCSSN/C7NETSSN

Variable Identifies the subsystem name.

INSTANCE 0 -31 Variable Identifies the subsystem instance.




Description

PC Variable Primary center. Any of the third-ranktoll switching points in the distancedialing network. The primary centercan home in on sectional centers,regional centers, or both of thesecenters.

NI (Integer) Variable Network interface is a circuit cardused in the network modules (NM).This card provides an interfacebetween a peripheral module (PM)and the crosspoint switches in theNM. The value indicates the NIinvolved.

CALLED ADDR Constant Variable Indicates that the field on the sameline refers to the call address.

INDICATOR 00-FF Variable Identifies the contents of the address,which can be one or more point code,subsystem, or global title.

SUBSYS #00-#FF Variable Provides the DMS subsystem ID ofan address that refers to a localsubsystem.

SSN #00-#FF Variable Identifies the subsystem.CALLING ADDR Constant Variable Indicates that the field on the same

line refers to the call address.GLOBAL TITLE TRANS (Integer) Variable Translation number. A Global title is

an application address. It does notcontain the necessary information toallow the signaling connection controlpart (SCCP) to route the messagetransfer part (MTP). The SCCPglobal title translation (GTT) functionis required to translate a GT in anetwork address that is correct.

CLASS 0-4 Variable Identifies the signaling connectioncontrol part (SCCP) routing class ofthe message.

SEQUENCE 0-1F Variable Identifies the signaling link sector(SLS) of the message.

OPTION 0-0F Variable Identifies the routing options thatapply to the message.

PRIORITY 0-3 Variable Identifies the message priority givenin the service information octet (SIO).

pkgtyp Unidirectional Variable Identifies the package type asunidirectional.

TCAP100 385



Description

Begin Variable Identifies the package type as begin.Query Variable Identifies the package type as query.Response Variable Identifies the package type as

response.Abort Variable Identifies the package type as abort.Conversation Variable Identifies the package type as

conversation.COMPONENT SET 0000-FFFF Variable Identifies the message sent or

received.

Active message exampleTCAP100 APR14 15:15:37 9000 INFO TCAP MESSAGE

REASON: OLNS RETURN ERROR RECEIVED

SUBSYSTEM NAME: OLNS INSTANCE: 2

CALLED ADDR: INDICATOR=#C1 SUBSYS=#58 SSN=#F0

PC: NI=1 NETTYPE=1 38-37-36

CALLING ADDR: INDICATOR=#C1 SUBSYS=#58 SSN=#F0

GLOBAL TITLE: TRANS=#23 TYPE=#05 DIGITS: 6138474387

CLASS=0 SEQUENCE=0D OPTION=0 PRIORITY=1

PACKAGE TYPE: RESPONSE RESPONSE ID: 00 00 00 00

COMPONENT SET: E8 0A EB 08 CF 01 00 D3 01 04 F2 00

TCAP100 APR14 15:15:37 9000 INFO TCAP UDT MESSAGE

REASON: RETURN ERROR RECEIVED


CALLED ADDR : INDICATOR=#C1 SUBSYS=#6C SSN=#F7








COMPONENT SET: E8 0A EB 08 CF 01 00 D4 01 01 30 00


REASON: REJECT RECEIVED








COMPONENT SET: E8 0B EC 09 CF 01 00 D5 02 01 01 F2 00


REASON: ABORT RECEIVED


CALLED ADDR: INDICATOR=#C1 SUBSYS=#6C SSN=#F7





PACKAGE TYPE: ABORT_PACKAGE RESPONSE ID: 00 00 00 00

COMPONENT SET: D7 01 01


REASON: ERROR IN RESPONSE

TCAP100 387









COMPONENT SET: E8 0C E9 0A CF 02 01 00 D1 02 65 03 30 00


Associated OM registers• The following OM registers are for log report TCAP100 in the OLNS

environment:OLNDATUN (OM group TOPSOLNE); OLNMISRT (OMgroup TOPSOLNE); OLNMISSR (OM group TOPSOLNE);OLNMSSGR (OM group TOPSOLNE); OLNNOPGR (OM groupTOPSOLNE); OLNPRTPR (OM group TOPSOLNE); OLNSCRND (OMgroup TOPSOLNE); OLNUNEXC (OM group TOPSOLNE);OLNUNEXD (OM group TOPSOLNE); OLNUNNET (OM groupTOPSOLNE); OLNVCTGR (OM group TOPSOLNE); OLNRREJ (OMgroup TOPSOLNS); OLNRRERR (OM group TOPSOLNS);RETERRCV (OM group TOPATCAP); REJCRCV (OM groupTOPATCAP); ABTRCV (OM group TOPATCAP)

• When the subsystem generates this log in TOPS07, one of theregisters in tuple TOPSLNP, OM group TOPATCAP can increase. If aregister in TOPATCAP does not increase, a register in tupleTOPSLNP, OM group TOPAAPPL increases.

TCAP101Example 1

Transaction Capabilities Application Part (TCAP) applications useTCAP101 to log TCAP messages received in signaling connection controlpart (SCCP) messages. This log has text reasons that relate to the CLASSCalling Name Delivery (CNAMD) TCAP application.

The subsystem generates log report TCAP101 each time a TCAP querywith permission (QWP) package returns in a SCCP message. TCAP101includes two text reasons to indicate that a CNAMD TCAP QWP package



returned. The two text causes are CNAMD UDTS RECEIVED and CNAMDVERIFICATION UDTS RECEIVED. The two text reasons identify CNAMDTCAP QWP packages sent. Text causes use the TESTSS CNAMDdatabase verification command and CNAMD TCAP QWP packages sentfor current calls.

In NA006, TCAP101 expands to display a message that relates toOriginating Line Number Screening (OLNS). The subsystem generates logreport TCAP101 for each OLNS TCAP package that returns to the serviceswitching point (SSP). OLNS TCAP packages return to the SSP from asignaling transfer point (STP) or service control point (SCP). OLNS TCAPpackages return to the SSP from a STP or SCP in an SCCP unitdataservice message (UDTS). A problem occurred if the report displays thisreason message. The problem occurred while the system attempted toroute the OLNS TCAP package to the OLNS LIDB.Example 2 - TOPS07

The subsystem generates log report TCAP101 each time a TOPSLNPTCAP package returns to the SSP in an SCCP UDTS message. Thesystem encounters a problem when an attempt to route the TOPSLNPTCAP package to the LNP SCP database occurred.

This log appears with TOPSLNP information in a LET PCL environment.

The following table describes each reason.

• ABAR UDTS MSG, LT_DENIAL -- Indicates a failure detected duringthe attempt to route the ACBAR message. The received messageprints in hexadecimal bytes in the log.

• ABAR UDTS MSG, ST_DENIAL -- Indicates that a network problemoccurred. The received message prints in hexadecimal bytes in the log.

• ACBAR UTS MSG, RESP OR UNI -- Indicates that a failure occurredduring the attempt to route an ACBAR TCAP UNI or RSP message.The received message prints in hexadecimal bytes in the log.

• CNAMD UDTS RECEIVED -- Indicates that the route process to aresidence name database failed.

• CNAMD VERIFICATION UDTS RECEIVED -- Indicates that a networkproblem occurred.

• PACKAGE TYPE NOT SUPPORTED-PVN -- Indicates that thedatabase sent a PVN application to the QUERY package. The receivedmessage prints in hexadecimal bytes in the log.

• OLNS UDTS RECEIVED -- This reason indicates that an OLNS TCAPpackage returned to the Traffic Operator Position System (TOPS) DMSswitch in an SCCP UDTS.

TCAP101 389


• PVN RECEIVED REJECT -- Indicates that the PVN applicationreceived a database message with a reject component. The receivedmessage prints in hexadecimal bytes in the log.

• PVN RECEIVED RETURN ERROR -- Indicates that the PVNapplication received a database with a return error component. Thereceive message prints in hexadecimal bytes in the log.

• PVN SENT REJECT -- Indicates that the PVN application sent amessage with a reject component to the database. The message sentprints in hexadecimal bytes in the log.

• PVN SENT REPORT ERROR -- Indicates that the PVN applicationsent a message with a cause component, procedure report error, to thedatabase. The message sent prints in hexadecimal bytes in the log.

• PVN SENT RETURN ERROR -- Indicates that the PVN applicationsent a message with a return error component to the database. Themessage sent prints in hexadecimal bytes in the log.

• RTRS UDTS RECEIVED -- Indicates an RTRS TCAP packagereturned to TOPS in an SCCP UDTS message.

• UNI MSG RECEIVED-PVN -- Indicates that the database sent a PVNapplication to the unidirectional package. The received message printsin hexadecimal bytes in the log.

• UNRECOGNIZED TRID-PVN -- Indicates that the PVN applicationreceived a response/conversion message with a transaction ID that isnot correct. The received message prints in hexadecimal bytes in thelog.

• UDTS RECEIVED -- Indicates a TOPSLNP TCAP package returned toTOPS in an SCCP UDTS message.

• ISDNSS: LOST UDTS -- Indicates that the ISDNSS TCAP frameworkreceived a TCAP message (an SCCP UnitData service message) fromthe SCCP software subsystem, but the UDTS could not be delivered toany local TCAP application. Analyze the COMPONENT SET field andother switch logs and OMs to determine the exact problem.

Remedial actionThe received reason textCNAMD UDTS RECEIVEDindicates a problem.The problem is that the attempt to route the CNAMD TCAP QWP packageto the central residence name database failed. Analyze the test field of thelog report data to determine the cause of the problem.

The received reason textCNAMD VERIFICATION UDTSRECEIVEDindicates a problem. The problem occurred in the network. Theproblem occurred when the system attempted to route the CNAMD TCAPQWP package to the central residence name database. Analyze the testfield of the log report data to determine the cause of the problem.



The received reason textACBAR UDTS MSG, LT_DENIALindicates aproblem. The problem occurred when the attempt to route the ACBARTCAP QWP, QNP, CWP or CNP package failed. Analyze the test field ofthe log report data to determine the cause of the problem.

The received reason textACBAR UDTS MSG, ST_DENIALindicates aproblem. The problem occurred in the network when the system attemptedto route the ACBAR TCAP QWP, QNP, CWP or CNP package. Analyzethe test field of the log report data to determine the cause of the problem.

The received reason textACBAR UDTS MSG, RESP OR UNIindicates aproblem. The problem occurs when the system attempts to route theACBAR TCAP UNI or RSP package. Analyze the test field of the log reportdata to determine the cause of the problem.

If the DMS switch receives the reason textOLNS UDTS RECEIVED, theoperating company personnel does not need to perform any action. Thislog generates in the OLNS environment for information use only.

This log is for information use. The network administration must take actionas the report indicates that a Common Channel System 7 (CCS7) routingproblem occurred.


FormatTCAP101 mmmdd hh:mm:ss ssdd INFO TCAP UDTS MESSAGE

REASON: <rsntxt>


CALLED ADDR: INDICATOR=<indicator> SUBSYS=<subsys>

SSN=<ssn>


CALLING ADDR: INDICATOR=<indicator>

SUBSYS=<subsys> SSN=<ssn>


CLASS=<class> SEQUENCE=<seq> OPTION=<opt> PRIORITY=<pri>

TCAP101 391


DIAGNOSTIC=<diag>

PACKAGE TYPE: <pkgtyp> ORIGIN ID: <origin id>

COMPONENT SET: component set>


VariableDescription

INFO TCAPSERVICEMESSAGE

Constant Variable Indicates a report of transactioncapabilities application part (TCAP)unit data service message.

rsntxt Refer to the Table,Reasons at the endof this report.

Variable Provides the reasons that thesubsystem generates this log.

SUBSYSTEM NAME Defined inC7LOCSSN/C7NETSSN

Variable Identifies the subsystem name.

INSTANCE 0-31 Variable Identifies the subsystem instance.CALLED ADDR Constant Variable Indicates that the field on the same

line relates to the called address.INDICATOR #00-#FF Variable Identifies the contents of the address,

which may be one or more pointcode, subsystem, or global title.

SUBSYS #00-#FF Variable Provides the DMS subsystem ID ofan address that refers to a localsubsystem.

SSN #00-#FF Variable Identifies the subsystem.CALLING ADDR Constant Variable Indicates that the field on the same

line applies to the calling address.CLASS 0-4 Variable Identifies the signaling connection

control part (SCCP) routing class ofthe message.

SEQUENCE 0-1F Variable Identifies the signaling link sector(SLS) of the message.

OPTION 0-0F Variable Identifies the routing options thatapply to the message.

PRIORITY 0-3 Variable Identifies the message priorityprovided in the service informationoctet (SIO).

pkgtyp Unidirectional Variable Identifies the package type asunidirectional.

Begin Variable Identifies the package type as begin.Query Variable Identifies the package type as query.




Description

Response Variable Identifies the package type asresponse.

Abort Variable Identifies the package type as abort.Conversation Variable Identifies the package type as

conversation.COMPONENT SET 0000-FFFF Variable Identifies the message sent or

received.

Active message exampleTCAP101 APR14 15:16:37 9000 INFO TCAP SERVICE MESSAGE

REASON: OLNS UDTS RECEIVED


CALLED ADDR: INDICATOR=#89 SUBSYS=#58 SSN=#F0



GLOBAL TITLE: TRANS=#23 TYPE=#05 DIGITS: 6138474387

CLASS=0 SEQUENCE=0D OPTION=0 PRIORITY=1 DIAGNOSTIC=02

PACKAGE TYPE: QUERY_W_PERMISSION RESPONSE ID:00 00 00 00

COMPONENT SET: E8 1B E9 19 CF 01 00 D0 02 81 01 F2 10 97

00 AA 0B 84 09 0B 00 11 0A 16 83 42 44 44

TCAP101 APR14 15:16:37 9000 INFO TCAP UDTS MESSAGE

REASON: UDTS RECEIVED


CALLED ADDR : INDICATOR=#89


CALLING ADDR: INDICATOR=#C3 SUBSYS=#6C SSN=#F7


CLASS=0 SEQUENCE=0D OPTION=0 PRIORITY=1 DIAGNOSTIC=02

TCAP101 393


PACKAGE TYPE: QUERY_W_PERMISSION ORIGIN ID: 00 00 00 00

COMPONENT SET: E8 21 E9 1F CF 01 00 D1 02 64 03 30 16 BF 35

07 81 05 03 24 02 21 43 8D 01 00 8F 07 03 10 03 24 02 21 43


Associated OM registers• Any one of the following OM registers in the C7SCCP OM group may

associate with this log:C7RTFALL.; C7RTFNTN.; C7RTFNTA.;C7RTFNWF.; C7UDTSRX.; C7RTFSSF.; C7RTFSSC.;C7RTFUEQ.The following OM registers are for log report TCAP101 inthe OLNS environment:OLNNETCG (OM group TOPSOLNE);OLNNETFL (OM group TOPSOLNE); OLNNOXLA (OM groupTOPSOLNE); OLNNOXLS (OM group TOPSOLNE); OLNSUBCG (OMgroup TOPSOLNE); OLNSUBFL (OM group TOPSOLNE);OLNUNEQP (OM group TOPSOLNE)

• When the subsystem generates this log, one of the registers in tupleTOPSLNP in OM group TOPASCCP increases.

TCAP102The Common Channel Signaling (CCS) subsystem generates this reportwhen the TCAP fails to send a Reject component in response to a protocolerror. The log identifies the Signaling Connection Control Part (SCCP)subsystem and the transaction ID for which the reject was being sent.

Remedial actionn/a


FormatTCAP102 mmmdd hh:mm:ss ssdd INFO TCAP Send Reject failed

SUBSYSTEM: sstxt INDEX: nn TRANSACTION ID: #hh hh hh hh




VariableDescription

INFO TCAP SendReject failed

Constant Variable Indicates that the TCAP has failed tosend a Reject component inresponse to a protocol error.

SUBSYSTEM symbolic range Variable Identifies the subsystem affected(value depends on applicationsloaded for the BCS).

INDEX 0-2&s3.&s2. VariableIdentifies thetransaction ID forwhich the Reject isbeing sent.

00 00 00 00 - FF FFFF FF

Variable Identifies the transaction ID for whichthe Reject is being sent.

Active message exampleTCAP102 JUN18 06:47:33 7700 INFO TCAP Send Reject Fail

SUBSYSTEM: TUP INDEX: 0 TRANSACTION ID: #26 CA 14 00



TCAP199 Format 1Example 1

The Common Channel Signaling (CCS) subsystem generates TCAP199when a miscellaneous error condition occurs. The subsystem generatesTCAP199 for debugging purposes only.

In NA006, the OLNS SCCP FORMAT ERROR adds to the errtxt field. Thiserror appears when a miscellaneous error occurs in the Originating LineNumber Screening (OLNS) environment.Example 2 - TOPS07

The changes to this log for the TOPSLNP application are made in specificconditions. These conditions are when the subsystem attempts to formatthe Signaling Connection Control Part (SCCP) data. The subsystemattempts to format the SCCP data for a Transaction CapabilitiesApplication Part (TCAP) message and the format fails.

This log appears with TOPSLNP information in a Line Equipment Transfer(LET) Product CM Load (PCL) environment.Example 3 - TOPS07

TCAP199 Format 1 395


The subsystem generates log report TCAP199 when the subsystemreceives a package. The package is from the Local Number Portability(LNP) Service Control Point (SCP) and does not have a respondingtransaction id. At the present time, the AIN0.1 TCAP messaging interfacethis activity creates does not handle received packages without transactionids.

This log appears with TOPSLNP information in a LET PCLenvironment.Example 4

The OLI ERROR log appears when the incoming virtual message does notcontain the Originating Line Identity (OLI).

On the transit node, the directory number (DN) of the originating stationmust uniquely identify digital private network signaling system (DPNSS)virtual calls and TCAP/SCCP interworked requests at this node.

If the originating station does not send the OLI, the OLI ERROR logappears at the DPNSS integrated services digital network user part (ISUP)transit node for virtual calls.Example 5

The point code from table MSGRTE is necessary to send a TCAPmessage to the far transit node.

Table MSGRTE routes DPNSS-ISUP virtual messages. Network identi er(NETID) and Called Party Address index these messages. The NETID of aDPNSS-ISUP call is the NETID of the originating line or DPNSS trunk. TheCalled Party Address used is the DPNSS Destination Address mostsiginifcant digits.

This log appears when there is no entry in Table MSGRTE against theNETID and most of the signi cant digits of the Destination Address.

Remedial actionLog TCAP199 may report that there are not enough of Transaction IDs forthe RTRS application. When this occurs, contact your next level of support.

An RTRS SCCP FORMAT ERROR message indicates a possibletranslation problem in the SCCP CCS7 tables. Check for data 11 that ismissing or wrong in the following CCS7 translations tables:

• C7GTTYPE

• C7NETWRK,

• C7GTT

• any other CCS7 tables



An SCCP FORMAT ERROR message for subsystem TOPSLNP, indicatesa possible translation problem in SCCP CCS7 tables. Check for data thatis missing or wrong in CCS7 translations tables:

• C7GTTYPE

• C7NETWRK

• C7GTT

• other CCS7 tables

An ISDNSS LOST MESSAGE error indicates that the ISDNSS TCAPframework received a TCAP message from the SCCP software subsystem,but the message could not be delivered to any local TCAP application. Thenature of the message could not be determined.

Originating Line Number Screening

A TCAP199 may report that there are not enough Transaction IDs for theOLNS application. When this occurs, contact your next level of support.

An OLNS SCCP FORMAT ERROR message indicates a possibletranslation problem in the SCCP CCS7 tables. Check for data that ismissing or wrong in the following CCS7 translations tables:

• C7GTTYPE

• C7NETWRK

• C7GTT



FormatTCAP199 mmmdd hh:mm:ss ssdd INFO TCAP MISC ERROR

TCAP Traffic: <errtxt> reason = n

SUBSYSTEM NAME: ssss INSTANCE: tt




VariableDescription

INFO TCAP MISCERROR

Constant Variable Indicates a miscellaneous errorcondition occurred as the systemtested.

errtxt Dynamic Variable Describes the error that occurred.reason 2 bytes Variable Identifies the return code from the

tested procedure.Subsystem Name 8 bytes Variable Identifies the subsystem name

defined in C7LOCSSN/C7NETSSNInstance 0-31 Variable Identifies the subsystem instance.<text message> SCCP FORMAT

ERRORVariable A text reason why the TCAP 199 log

generated.BAD PKG RCVD Variable

Active message exampleTCAP199 JUN18 18:47:33 7700 INFO TCAP MISC ERROR

TCAP Traffic: OLNS SCCP FORMAT ERROR reason = 0




TCAP199 Format 2Example 1

The Common Channel Signaling (CCS) subsystem generates TCAP199when a miscellaneous error condition occurs. The subsystem generatesTCAP199 for debugging purposes only.

In NA006, the OLNS SCCP FORMAT ERROR adds to the errtxt field. Thiserror appears when a miscellaneous error occurs in the Originating LineNumber Screening (OLNS) environment.Example 2 - TOPS07

The changes to this log for the TOPSLNP application are made in specificconditions. These conditions are when the subsystem attempts to formatthe Signaling Connection Control Part (SCCP) data. The subsystemattempts to format the SCCP data for a Transaction CapabilitiesApplication Part (TCAP) message and the format fails.



This log appears with TOPSLNP information in a Line Equipment Transfer(LET) Product CM Load (PCL) environment.Example 3 - TOPS07

The subsystem generates log report TCAP199 when the subsystemreceives a package. The package is from the Local Number Portability(LNP) Service Control Point (SCP) and does not have a respondingtransaction id. At the present time, the AIN0.1 TCAP messaging interfacethis activity creates does not handle received packages without transactionids.

This log appears with TOPSLNP information in a LET PCLenvironment.Example 4

The OLI ERROR log appears when the incoming virtual message does notcontain the Originating Line Identity (OLI).

On the transit node, the directory number (DN) of the originating stationmust uniquely identify digital private network signaling system (DPNSS)virtual calls and TCAP/SCCP interworked requests at this node.

If the originating station does not send the OLI, the OLI ERROR logappears at the DPNSS integrated services digital network user part (ISUP)transit node for virtual calls.Example 5

The point code from table MSGRTE is necessary to send a TCAPmessage to the far transit node.

Table MSGRTE routes DPNSS-ISUP virtual messages. Network identifier(NETID) and Called Party Address index these messages. The NETID of aDPNSS-ISUP call is the NETID of the originating line or DPNSS trunk. TheCalled Party Address used is the DPNSS Destination Address mostsignificant digits.

This log appears when there is no entry in Table MSGRTE against theNETID and most of the significant digits of the Destination Address.

Remedial actionLog TCAP199 may report that there are not enough of Transaction IDs forthe RTRS application. When this occurs, contact your next level of support.

An RTRS SCCP FORMAT ERROR message indicates a possibletranslation problem in the SCCP CCS7 tables. Check for data 11 that ismissing or wrong in the following CCS7 translations tables:

• C7GTTYPE

• C7NETWRK,



• C7GTT

• any other CCS7 tables

An SCCP FORMAT ERROR message for subsystem TOPSLNP, indicatesa possible translation problem in SCCP CCS7 tables. Check for data thatis missing or wrong in CCS7 translations tables:

• C7GTTYPE

• C7NETWRK

• C7GTT


An ISDNSS LOST MESSAGE error indicates that the ISDNSS TCAPframework received a TCAP message from the SCCP software subsystem,but the message could not be delivered to any local TCAP application. Thenature of the message could not be determined.

Originating Line Number Screening

A TCAP199 may report that there are not enough Transaction IDs for theOLNS application. When this occurs, contact your next level of support.

An OLNS SCCP FORMAT ERROR message indicates a possibletranslation problem in the SCCP CCS7 tables. Check for data that ismissing or wrong in the following CCS7 translations tables:

• C7GTTYPE

• C7NETWRK

• C7GTT



FormatTCAP199 mmmdd hh:mm:ss ssdd INFO TCAP MISC ERROR

<text message> 0


<hex data>




VariableDescription

INFO TCAP MISCERROR

Constant Variable Indicates a miscellaneous errorcondition occurred as the systemtested.

errtxt Dynamic Variable Describes the error that occurred.reason 2 bytes Variable Identifies the return code from the

tested procedure.Subsystem Name 8 bytes Variable Identifies the subsystem name

defined in C7LOCSSN/C7NETSSNInstance 0-31 Variable Identifies the subsystem instance.<text message> SCCP FORMAT

ERRORVariable A text reason why the TCAP 199 log

generated.BAD PKG RCVD Variable

Active message exampleTCAP199 APR14 15:15:40 1210 INFO TCAP MISC ERROR

SCCP FORMAT ERROR 0


TCAP199 APR14 15:15:40 1210 INFO TCAP MISC ERROR

BAD PKG RCVD 0


<hex data>


SIGTRANS: OLI ERROR 0

SUBSYSTEM NAME: INSTANCE: 6

<hex data>


SIGTRANS: No MSGRTE entry 0

SUBSYSTEM NAME: INSTANCE: 6

<hex data>





TCAP200The TCAP200 log generates at the host node if a network message waitingindication (MWI) request indicates an invalid directory number (DN) andthere is no entry for a route in the MSGRTE table.

Remedial actionn/a


FormatTCAP200 mmmdd hh:mm:ss ssdd INFO TCAP FAC SEND FAILED

ORG NETID: 0 DN: nnnnnnnnnn

DST NETID: 0 DN: nnnnnnnnnn

PKG TYPE: QUERY_W_PERMISSION

REASON: NO ROUTE DATAFILLED

32E2 04C7 0000 0008 2AE8 28E9 01CF D101

7E02 F203 AA1F 841D 0109 2100 160A 2273

3211 C0DF 0949 00FA 0A21 7316 1122 DF12

45C0 0101 007F EBAD CE12 210A 000A 001D




VariableDescription

INFO TCAP FACSEND FAILED

Constant Variable The value indicates the DMS-100switch did not locate a common deskfor the network MWI request.

ORG NETID Symbol text Variable The value indicates the originatingDN. The DN field changes to supportvariable length DN format up to tendigits because of the E.164compliance.

DST NETID Symbol text Variable The value indicates the destinationDN. The DN field changes to supportvariable length DN format up to tendigits because of the E.164compliance.

PKG TYPE Constant Variable The value indicates the package typeof the TCAP message.

REASON Constant Variable The value indicates the reason thelog generates. The reason is theentry for the route is not complete.

Active message exampleTCAP200 DEC05 18:14:33 4827 INFO TCAP FAC SEND FAILED

ORG NETID: 0 DN: 6137221121

DST NETID: 0 DN: 6137221123

PKG TYPE: QUERY_W_PERMISSION

REASON: NO ROUTE DATAFILLED

32E2 04C7 0000 0008 2AE8 28E9 01CF D101

7E02 F203 AA1F 841D 0109 2100 160A 2273

3211 C0DF 0949 00FA 0A21 7316 1122 DF12

45C0 0101 007F EBAD CE12 210A 000A 001D


TCAP200 403



TCCI100The Traffic Operator Position System (TOPS) Computer Consoles Inc.(TCCI) subsystem generates this log report for one of several reasons:

• Directory Assistance (DA) tracing is turned on.

• The switch attempts to send an improperly formatted message to theDirectory Assistance Service (DAS).

• The switch receives an improperly formatted message from the DAS.

Remedial actionThe operating company personnel should retain the previous five minutesof log reports and contact the next level of support.


FormatTCCI100 mmmdd hh:mm:ss seq# INFO TOPS CCI PROTOCOL ERROR

ERROR = <error>

STATE = <state>

DATABASE= <da database>

HEX MSG = <hex msg>

FORMATTED MSG:

MSG TYPE = <message type>

SWITCHID = <switch id>

DAS AREA = <das area>

DETAIL = <detail>

DAS CALLID= <das callid>

POS/ARU ID= <pos/aru id>

CLG/REQ DN= <calling/requested dn>

CLD DN = <called dn>



ANN NUMBER= <announcement number>

ORIG INFO = <originating information>


VariableDescription

INFO TOPS CCIPROTOCOLERROR

constant Variable Mandatory. This field indicates thereare TOPS CCI protocol messagingproblems.

ERROR alphanumericsymbolic text

Variable Mandatory. This field indicates thecondition that caused the CCImessage error.

STATE alphanumericsymbolic text

Variable Mandatory. This field indicates thecurrent call state (how far the call hadprogressed) of the DMS call processwhen the message was received.

DATABASE TOPSVR1 (0-15)TOPSVR2 (0-15)STUB (0-15)

Variable Mandatory. This field indicates whichdatabase instance is involved withthe CCI protocol error.

STUB is used primarily in a NORTELlab environment, but is sometimesused in configurations that do nothave DMS-DAS links.

HEX MSG hexadecimal digits Variable Message contents.FORMATTED MSG constant Variable Mandatory. This field is a fixed text

string that marks the beginning of theformatted message. The fields thatfollow the fixed text string provide aninterpretation of the hexadecimalmessage in IBM protocol format.These fields are MSG TYPE,SWITCH ID, DAS AREA, DETAIL,DACALLID, POS/ARU ID, CLG/REQDN, CLD DN, ANN NUMBER, andORIG INFO.

MSG TYPE alphanumericsymbolic text

Variable Mandatory. This field indicates thetype of message request (forexample ARU Request, POSConnect).

SWITCH ID 0-15 Variable Mandatory. This field indicates theswitch on which the error occurred.

DAS AREA alphanumeric text Variable Mandatory. This field indicates theDAS Vendor storage area.

TCCI100 405



Description

DETAIL alphanumericsymbolic text

Variable Mandatory. This field indicates thedetail information depending on thetext in the MSG TYPE field.

DACALLID 0000-3072 Variable Mandatory. This field indicates thecall number that is related toerroneous CCI message.

POS/ARU ID 0-9999 Variable Mandatory. This field indicates theposition/terminal number that isassociated with the call.

CLG/REQ DN numeric string Variable Mandatory. This field indicates thecalling subscriber number.

CLD DN numeric string Variable Mandatory. This field Indicates thecalled directory number.

ANN NUMBER 0-254 Variable Mandatory. This field indicates theaudio announcement number.

ORIG INFO 0-3, 0-999 Variable Mandatory. This field indicates thelanguage and interexchangeidentifiers. The first range representsthe language identifier; the latterrepresents the interchange identifier.

Active message exampleTCCI100 MAR03 10:38:29 5700 INFO TOPS CCI PROTOCOL ERROR

ERROR = TRACING ACTIVATED

STATE = 14

DATABASE= STUB 0

HEX MSG=010FFFFF0301002402165902214314F1FFFFFFFFF0FFFFFFFFFF

FFFF00FF020000000040400E00FFFFFFFFFFFFFF

FORMATTED MSG:

MSG TYPE = CALL BEGIN

SWITCHID = 15

DAS AREA = FFFF

DETAIL = 3

DAS CALLID= 1



POS/ARU ID= 548

CLG/REQ DN= 619-520-1234

CLD DN = 411-FFFF

ANN NUMBER= 255

ORIG INFO = FFF0



TCCI101The Traffic Operator Position System (TOPS) Computer Consoles Inc.(TCCI) subsystem generates this log for one of two reasons:

• Directory Assistance (DA) tracing is turned on and the switch receivesa Transfer With Context message from the Directory AssistanceService (DAS).

• The switch receives an improperly formatted Transfer With Contextmessage from the DAS.

Remedial actionThis error indicates that the DA system has sent the DMS an out of rangevalue in a Transfer With Context message. Notify the next level of support.



ERROR = <error>

STATE = <state>


HEX MSG = <hex msg>

FORMATTED MSG:


TCCI101 407




DETAIL = <detail>

DAS CALLID = <das callid>

CONTROL LISTID= <control list id>

CONTEXT BLOCK = <context block>


VariableDescription

TOPS CCIPROTOCOLERROR

Constant Variable Indicates that an out of range valuehas been received in a Transfer WithContext message

ERROR text Variable Indicates the error condition thatcaused the log

STATE text Variable Current DMS Call processing statewhen the invalid message wasreceived

HEX MSG hexadecimal digits Variable Message contentsFORMATTEDMESSAGE

text Variable Indicates Protocols view of themessage

MSG TYPE text Variable Indicates the message typeSWITCHID 0 - 15 Variable Indicates the switch where the error

occurredDETAIL 0 - 1 Variable Indicates the value in the Detail area

of the messageDAS CALLID 0 - 1022 Variable A per call identifier that uniquely

identifies the call that this messagebelongs to

CONTROL LISTID 0 - 4094 Variable The Control List Identifier that the DAsystem invokes with this message

CONTEXT BLOCK hexidecimal digits Variable Context block (first byte is count;remaining bytes are data)



STATE = 14



DATABASE= STUB 0

HEX MSG = 150F0000FF0100010022000102030405060708090A0B

0C0D0E0F101112131415161718191A1B1C1D1E1F202IFFFF

FORMATTED MSG:

MSG TYPE = XFER WITH CNTX

SWITCHID = 15

DAS AREA = 0000

DETAIL = 255

DAS CALLID = 1

CONTROL LISTID= 1

CONTEXT BLOCK = 002202010403060508070A090C0B0E0D100F1211

1413161518171A191C1B1E1D201F4A21



TCCI102The Traffic Operator Position System (TOPS) Computer Consoles Inc.(TCCI) subsystem generates this log for one of two reasons:

• Directory Assistance (DA) tracing is turned on and the switch sends aContext Block message to the Directory Assistance Service (DAS).

• The switch attempts to send an improperly formatted Context Blockmessage to the DAS.

Remedial actionNotify the next level of support.



TCCI102 409


ERROR = <error>

STATE = <state>


HEX MSG = <hex msg>

FORMATTED MSG:




DETAIL = <detail>

DAS CALLID = <das callid>

CONTEXT BLOCK= <context block>


VariableDescription

ERROR<error> alphanumericsymbolic text

Variable Describes error

STATE<state> alphanumericsymbolic text

Variable TOPS internal call state

DATABASE<dadatabase>

Link sets defined intable MPCLSET

Variable Indicates which link set the messagewas sent/received on

HEX MSG<hexmsg>

hexadecimal digits Variable Message contents

FORMATTED MSG: constant Variable This field is a fixed text string thatmarks the beginning of the formattedmessage. The fields that follow thefixed text string provide aninterpretation of the hexadecimalmessage in IBM protocol format.

MSGTYPE<messagetype>

CONTEXT BLOCK Variable Type of message

SWITCHID<switchid>

0 through 99 Variable Identifies the switch

DAS AREA<dasarea>

0000 through FFFF Variable DAS application specific data




Description

DETAIL<detail> 0 to 255 Variable Detail field in messageDAS CALLID<dascallid>

0 to 3070 Variable DAS CALLID field in message

CONTEXTBLOCK<contextblock>

hexadecimal digits Variable Context block (first byte is count;remaining bytes are data)



STATE = 14

DATABASE= STUB 0

HEX MSG =160FFFFFFF010022000102030405060708090A0B0C0D0E0F101:

12131415161718191A1B1C1D1E1F202IFFFFFFFF

FORMATTED MSG:

MSG TYPE = CONTEXT BLOCK

SWITCHID = 15

DAS AREA = FFFF

DETAIL = 255

DAS CALLID = 1

CONTEXT BLOCK=002202010403060508070A090C0B0E0D100F12111413

161518171A191C1B1E1D201F0021



TCW600The system generates the TCW600 log when a call to the SN results in atreatment or routes to an unsupported agent.

TCW600 411


Remedial actionThe TCW600 log indicates a problem with the call to the SN. To determinethe cause of the problem

• save the log report for reference

• examine the log report to verify the Directory Number (DN) that TCWused to route to the SN, and the treatment that was applied to the call

• use the translations verification (TRAVER) tool to verify the translationsfor the call to the SN

The following section lists the causes of routing failure and the treatmentsassociated with the routing failure.

Fails to route to Service Node

The TCW600 information log has a value of ''fails to route to Service Node''when the call to the SN encounters a treatment.

Examine the treatment field of the log report to determine what treatmentthe call to the SN encountered. Modify the data 11 so that the call to theSN avoids this treatment and use the TRAVER tool to verify the newtranslations.

The treatment field of the log report may contain No Software Resource(NOSR). This treatment can indicate the call to the SN could not betranslated using Routing Characteristics because of a lack of softwareresources. If the value of office parameter NUM_RC_EXT_BLKS in tableOFCENG is set too low it can cause this problem. In this case, increasingthe value of NUM_RC_EXT_BLKS ensures that calls to the SN aresuccessfully translated.

Unsupported type of call to SN

The TCW600 information log has a value of ''unsupported type of call toSN'' when the call to the SN encounters an unsupported feature or anunsupported agent. This value can result in two treatments

Feature Not Allowed (FNAL)

A treatment of FNAL indicates that the call to the SN encountered anunsupported feature. For example, an 800 service was encountered on thecall to the SN.

In this case, change the data 11 so that the call to the SN a voidsunsupported features and use TRAVER to verify the new translations.

Undetermined (UNDT)



A treatment of UNDT indicates that TCW blocks the call to the SN becausethe agent is unsupported. The supported agents to route out of the TCWserving office for the call to the SN are ISUP, BRI or PRI trunks.

If TCW blocks the call to the SN because the agent is unsupported, modifythe data ll for the call to the SN and use the TRAVER tool to verify the newtranslations.


Formatlogoffid TCW600 mmmdd:mm:ss nnnn TCW log report

Reason The condition that caused the log to

generate

Call ID call identification number (hex number)

TCW DN the Talking Call Waiting (TCW)

subscriber''s directory number (DN)

SN DN the directory number (DN) that TCW uses

to reach the service node (SN)

Treatment call treatment associated with the routing

failure


VariableDescription

logoffid symbolic text Variable Log_office_id - an office parameterdefined in table OFCVAR thatspecifies a name for the office for thepurpose of office identification in thelog output header

TCW600 constant Variable log namemmmdd symbolic text Variable date the system generated the log, in

the format monthdayhh:mm:ss symbolic text Variable time the system generates the log, in

the format Hour:minute:second

TCW600 413



Description

nnnn symbolic text Variable sequential number of logsTCW log report constant Variable log report typeReason fails to route to

Service NodeVariable error while routing to the SN

unsupported type ofcall to SN

Variable unsupported feature or unsupportedagent encountered while routing tothe SN

Call ID hexadecimal Variable call identification numberTCW DN 10 digits Variable controller's directory numberSN DN 4 to 30 digits Variable service node directory numberTreatment treatment text of 4

characters maximumVariable call treatment associated with the

routing failure (4 characters)

Active message exampleNTL2110AP TCW600 MAR11 16:04:14 2300 TCW log report

Reason Fails to route to Service Node

Call ID 038B 0000

TCW DN 5145425541

SN DN 5148547855

Treatment PSIG



TCW601The following conditions cause the system to generate the TCW601 log:

• the TCW serving office does not receive the ANM message within theduration that the T1 allows

• the TCW serving office does not receive the REL message within theduration that the T2 allows

• the system is unable to allocate the resources to route the call

• the connection to the SN is not ISUP or PRIALL-THE-WAY



Remedial actionSave the log report and use it as additional information to investigate:

• the failure of the SN to respond within the normal time range

• the failure of the system to allocate enough resources to route the callto the SN

• the routing to the SN (verify the translations to the SN and the trunktypes)


Formatlogoffid TCW601 mmmdd:mm:ss nnnn TCW log report

Reason The condition that caused the log to

generate

Call ID call identification number (hex number)

TCW DN the Talking Call Waiting (TCW)

subscriber''s directory number (DN)

SN DN the directory number (DN) that TCW uses

to reach the service node (SN)


VariableDescription

logoffid symbolic text Variable Log_office_id - an office parameterdefined in table OFCVAR thatspecifies a name for the office for thepurpose of office identification in thelog output header

TCW601 constant Variable log namemmmdd symbolic text Variable date the system generated the log, in

the format monthdayhh:mm:ss symbolic text Variable time the system generates the log, in

the format Hour:minute:secondnnnn symbolic text Variable sequential number of logsTCW log report constant Variable log report type

TCW601 415



Description

Reason T1 expired Variable T1 expiresT2 expired Variable T2 expiresNO_OF_CLONE_TIDS exceeded

Variable TCW was not able to allocate anecessary resource to route the callto the SN.

unsupportedsignaling to SN

Variable the connection to the SN is not ISUPor PRI all the way

Call ID hexadecimal Variable call identification numberTCW DN 10 digits Variable controller's directory numberSN DN 4 to 30 digits Variable service node directory number

Active message exampleNTL2110AP TCW601 MAR11 16:04:14 2300 TCW log report

Reason T1 expired

Call ID 038B 0000

TCW DN 5145425541

SN DN 5148547855



TDR101This log identifies TOPS call detail recording (TDR) records that arepadded with zeroes to the size of the TDR provisioned by parameterTDR_RECORD_SIZE in table TOPTDROP. This log is generated onlywhen parameter GEN_PADDED_RECORD_LOG in table TOPTDROP isturned on.

History

TOPS11

This log was created by feature AF7817 in functionality TOPS/CarrierInterworking, OSB00001.



Remedial actionNone. Refer to functionality TOPS/Carrier Interworking, OSB00001, in theapplicable manual as follows:NA DMS-100 Translations Guide,297-8021-350GTOP DMS-100 Translations Guide, 297-8441-350TOPSCall Detail Recording (TDR) User''s Guide, 297-8403-904


FormatTDR100 mmmdd hh:mm:ss ssdd TBL TDR Format Truncated

Stream: <string>

Tmplt ID: <string>

Version: <integer>

Seq Num: <integer>

Words Padded: <integer>


VariableDescription

Stream alphanumeric Variable Name of the billing stream collectingthe TDR records. The stream isdefined in table CRSMAP and usedas the key in table CRSFMT.

Tmplt ID Combined, CallCompletion, CallTransfer to IC,Listing Services,Intercept, BLV/Interrupt, ChargeAdjust, OSSAINCustom Billing, or INInterworking Billing

Variable Identifies the template being usedwhen formatting the record

Version 0 Variable Identifies the version of the templatebeing used to format the record

Seq Num up to a 32 bit number Variable Identifies the billing record sequencenumber

Words Padded 1 to 239 Variable Contains the number of words thatcontain padding on the end of theassociated template.

TDR101 417


Active message exampleTDR101 AUG31 04:09:19 2100 TBL TDR Format Padded

Stream: TDR

Tmplt ID: Call Completion

Version: 0

Seq Num: 1000

Words Padded: 20



TDR102This log is generated when the Combined Template is used and OSSAINCustom Billing data is attached to the call. Since the Combined Templatedoes not support OSSAIN Custom Billing, the OSSAIN Custom Billing datais lost.

Therefore, if table TOPTDROP parameter TEMPLATE_TYPE =SINGLE_FIXED and OSSAIN Custom Billing data is associated with thecall, the data is lost and a TDR102 log is generated.

History

TOPS11






FormatTDR102 mmmdd hh:mm:ss ssdd TBL SN Lost Data

Stream: <string>

Version: <integer>

Seq Num: <integer>


VariableDescription

Stream alphanumeric Variable Name of the billing stream collectingthe TDR records. The stream isdefined in table CRSMAP and usedas the key in table CRSFMT.


Seq Num up to a 32 bit number Variable Identifies the billing record sequencenumber

Active message exampleTDR102 AUG31 04:09:19 2200 TBL TDR SN Lost Data

Stream: TDR

Version: 0

Seq Num: 1000



TDR200This log is the hex representation of the TOPS call detail recording (TDR)record. It contains the header fields, information about the originating andterminating agents in the call, and a hex dump of the remaining fields in thetemplate. It is only generated when GEN_RECORD_LOG = ON in tableTOPTDROP.

TDR200 419


A register in OM group TDRFTMPL is pegged according to the template IDidentified in the log report. The following lists shows the mapping:

• COMB when template = Combined

• CALLCMP when template = Call Completion

• XFRTOIC when template = Transfer to IC

• LSTSRV when template = Listing Services

• BLV when template = BV/Interrupt

• GENASST when template = Generl Assistance

• CHGADJ when template = Charge Adjust

• SNCUST when template = OSSAIN Customer Billing

• INTC when template = Intercept

• INWORKINTC when template = IN Interworking Billing

History

TOPS11




FormatTDR200 mmmdd hh:mm:ss ssdd TBL TDR Call Entry

Rec Code: <digit_string> Tmplt ID: <string>

Act ID: <integer> Version: <integer>

Calling DN: <digit_register>

Orig Agent: <cp_id>

Called DN: <digit_register>



Term Agent: <cp_id>

Length: <integer>

Data: <digit_string>


VariableDescription

Rec Code F0 Variable Indicates the value of Record Codefor the TDR call record which is F0.

Tmplt ID Combined, CallCompletion, CallTransfer to IC,Listing Services,Intercept, BLV/Interrupt, ChargeAdjust, OSSAINCustom Billing, or INInterworking Billing

Variable Identifies the template being usedwhen formatting the record

Act ID 0 to 7 Variable Identifies the Active Template ID inthe history file.


Calling DN up to 10 digits Variable Identifies the DN of the calling partyOrig Agent A valid call

processing identifierVariable Identifies the calling party agent

Called DN up to 30 digits Variable Identifies the called digitsTerm Agent A valid call

processing identifierVariable Identifies the called party agent

Length 0 TO 124 Variable Identifies the number of words ofdata in the record excluding theheader.

Data hexadecimal Variable Hex dump of the record. Any paddinghas not been included

Active message exampleTDR200 AUG31 04:09:19 2200 TBL TDR Call Entry

Rec Code: F0 Tmplt ID: Call Completion

Act ID: 0 Version: 0

Calling DN: 2016948839

Orig Agent: CKT ISNSS7IC 5

TDR200 421


Called DN: 4108485057

Term Agent: CKT TOG2 0

Length: 96

Data: C6F00040003F0006000000000400225719010000

000040004040004040E1000002B84240400F0000

00000000270F0000000000000000005000000000

0000000000000000000000000000404040400000

0001000000004006404040404040404000400000

0000000014001254490100000000400040404940

8000400010450D8B5C0B00000000



TELN100The subsystem generates TELN100 when the system establishes acomplete Telnet connection to the Computing Module (CM).

Remedial actionn/a


FormatTELN100 mmmdd hh:mm:ss ssdd INFO Telnet Connection

Node Name: <node name> Node Number: <node_num>

Remote Node Address: <IP_Addr>




VariableDescription

Date mmmdd Variable Indicates the date the subsystemgenerated the report.

Time hh:mm:ss Variable Indicates the time the subsystemgenerated the report.

Sequence #### Variable Indicates the sequence number ofthe report generated.

Node_name Text Variable Indicates the name of the nodewhere the Telnet server is. The nameof the node has an eight-characterlimit.

Node_num Integer Variable Indicates the number of the nodewhere the Telnet server is.

IP Addr Numeric Variable Indicates the IP address of theremote node that connects to theCM.

Active message exampleTELN100 AUG10 10:51:52 8600 INFO Telnet Connection

Node Name: CM Node Number: 0

Remote Node Address: 47.128.9.190



TELN110The subsystem generates TELN110 when the system closes a Telnetconnection to the Computing Module (CM).

Remedial actionn/a


FormatTELN100 mmmdd hh:mm:ss ssdd INFO Telnet Dis-Connection

TELN110 423


Node Name: <node name> Node Number: <node_num>

Remote Node Address: <IP_Addr>


VariableDescription

Date mmmdd Variable Indicates the date the subsystemgenerated the report.

Time hh:mm:ss Variable Indicates the time the subsystemgenerated the report.

Sequence #### Variable Indicates the sequence number ofthe report generated.

Node_name Text Variable Indicates the name of the nodewhere the Telnet server is. The nameof the node has an eight-characterlimit.

Node_num Integer Variable Indicates the number of the nodewhere the Telnet server is.

IP Addr Numeric Variable Indicates the IP address of theremote node that connects to theCM.

Active message exampleTELN100 AUG10 10:51:52 8600 INFO Telnet Dis-Connection

Node Name: CM Node Number: 0

Remote Node Address: 47.128.9.190



TEOL100TOPS end of life notification This log is generated when TOPS functionalitythat is scheduled for removal within three releases has been used at leastonce in the preceding week.

This log occurs only at midnight Sunday if there is an activity to report.

Although this log is produced with a release of SN10, the functionality isalso removed in the corresponding SN10 load.



The log indicates only that the functionality was used one or more times inthe previous week. It does not indicate when the functionality was used(that is, the time of the log itself is not at all related to the time of usage),nor does it indicate the number of times it was used.

Log history

SN09 (TDM)

Added "OSSAIN Broadcast Announcements" to the Functionality Usedfield, and added "SN10" to the Schedule Removal field to log TEOL100 tosupport Feature a00009012.

Remedial actionIf there is a plan in place to transition off of the identified functionalitybefore upgrading to the identified release (or beyond), then the notificationlogs can be ignored. If there is no such plan in place, then the next level ofsupport should be contacted to start an appropriate transition plan.


FormatTEOL100 mmmdd hh:mm:ss ssdd INFO TOPS End Of LifeNotification

Use of functionality scheduled for removal:

Functionality Used Scheduled Removal

______________________________________________________________

<function> <release>


VariableDescription

Functionality used BP Terminal, SA/ICPosition, IBM-DAProtocol, ServicesDatabase, TOPS OCvia DCM, TableTOPSBC, TableSPLDNID, DANISignaling, OC Night

Variable The functionality that is scheduled forremoval, but is being used.

TEOL100 425



Description

Closedown, TOPSOC via ETMS,Position via ETMS,Authorization Code,EAOSSIC Signaling,MODBELLSignaling,EAFGD Signaling,DMODEM, OSSAINBroadcastAnnouncements

Scheduled removal TOPS16, TOPS17,TOPS18, or SN10

Variable The release that the functionality isscheduled for removal.

Active message exampleIf an OSSAEST broadcast announcement was used during a week,a TEOL100 log is generated at midnight on the followingSunday with the "OSS AEST Broadcast Announcements"functionality listed (other functionality may also be listedhere). An example log report follows:

TEOL100 SEP24 13:23:54 2112 INFO TOPS End Of LifeNotification

Use of functionality scheduled for removal:

Functionality Used Scheduled Removal

------------------ -----------------

BP Terminal TOPS16

Table SPLDNID TOPS17

OSSAIN Broadcast Anns SN10



TIBM100The Traffic Operator Position System (TOPS) International BusinessMachines (TIBM) subsystem generates this log when an error occurs in themessaging between the Digital Multiplex System (DMS) and theInternational Business Machines (IBM) DAS.



The Traffic Operator Position System (TOPS) Computer Consoles Inc.(TCCI) subsystem generates this log report when

Traffic Operator Position System offices with release NA006 and higher

For TOPS offices with the Directory Assistance functional group(OSDA0001), the DATABASE field is added to log report TIBM100. Thisfield is necessary to distinguish which application (database instance)returned an invalid IBM protocol message to either the DAS and the DMSswitch. This distinction is necessary since multiple applications can useIBM protocol.

The DATABASE field is not displayed for TOPS offices that do not havethe NA006 version of OSDA0001.

Remedial actionThe operating company personnel should retain the previous five minutesof log reports and contact the next level of maintenance.


FormatTIBM100 mmmdd hh:mm:ss ssdd INFO IBM PROTOCOL ERROR

ERROR: = [symbolic text]

STATE: = [numeric]

DATABASE: = [dbinst]

MSG IN HEX: = [hexadecimal string

FORMATTED MSG =

TRANS CODE: = [symbolic text]

POSID/ARUID: = [numeric]

CALLID:= [numeric]

DESTID:= [numeric]

LISTSTATUS: = [numeric]

TARG/TENLO1 = [number string]

TIBM100 427



VariableDescription

INFO IBMPROTOCOLERROR

constant Variable Mandatory. This field indicates thatan IBM protocol error has occurred.

ERROR INVALID MESSAGE,INVALID MESSAGEDIRECTION,INVALID MESSAGELENGTH, INVALIDCALLID, INACTIVECALLID, INVALIDDESTINATION ID,NILANNOUNCEMENT

Variable Mandatory. This field indicates thereason that the log is generated.

STATE integer Variable Mandatory. This field indicates thecurrent state of the call when themessage was received.

DATABASE TOPSVR1 (0-15)TOPSVR2(0-15)STUB (0-15)

Variable Mandatory. This field indicates whichdatabase instance was involved inthe invalid IBM protocol message.

STUB is used primarily in a NORTELlab environment, but is sometimesused in configurations that do nothave DMS-DAS links.

MSG IN HEX hexadecimal Variable string Mandatory. This field indicatesthe hexadecimal string representationof the message received, that causedthis error to occur.

FORMATTED MSG constant Variable Mandatory. This field is a fixed textstring that marks the beginning of theformatted message. The fields thatfollow the fixed text string provide aninterpretation of the hexadecimalmessage in IBM protocol format.These fields are TRANS CODE,POSID/ARUID, CALLID, DESTID,LISTSTATUS, and TARG/TELNO1.

If the message type is "INVALIDMESSAGE", this section of the reportwill be unassigned.

TRANS CODE ARU SELECT, ARUSTATUS, ARU STATREQ, DELAYEDXFR, CALLARRIVAL, NEW

Variable Mandatory. This field indicates thetransaction that is involved with theinvalid message.




Description

REQUEST, IMMEDTRANSFER, POSBUSY IN, POSSTATUS, POSSTATUS REQ, POSRELEASE,REFERRAL,SPEAK, SPEAKCOMPLETE, SPEAKREJECT, SUBDISCONNECT, SYSID REPLY, SYS IDREQUEST,TRANSFER,TRANSERABORT,XFR CANCEL, CCTRANSFER, CCARU SELECT, CALLCOMPLETE, CALLRELEASE, DETEXCEPTION, RLYFROM POSN, AMAUPDATE, CALLINIT, UNKNOWN

POSID/ARUID 0-9999 Variable Mandatory. This field indicates theposition/terminal number thatgenerated the call.

DACALLID 0000-3072 Variable Mandatory. This field indicates thecall on which the error occurred.

DESTID integer Variable Mandatory. This field indicates thedestination identifier.

LISTSTATUS integer Variable Mandatory. This field indicates thecurrent list status.

TARG/TELNO1 numeric Variable string Mandatory. This field indicatesthe called directory number.

Active message exampleTIBM100 FEB02 22:50:43 9316 INFO IBM PROTOCOL ERROR

ERROR: = INVALID CALLID

STATE: = 53

DATABASE: = TOPSVR1 2

MSG IN HEX: = 0123170003FD06039012345678

TIBM100 429


FORMATTED MSG =

TRANS CODE: = NEW REQUEST

POSID/ARUID: = 123

CALLID: = 1022

DESTID: = -1

LISTSTATUS: = 6

TARG/TENL01 = 9012345678



TKCV100The Trunk Conversion (TKCV) subsystem generates TKCV100 when thesubsystem encounters an error condition. This error condition occursduring the operation of commands entered from the TRKCONV level of theMAP (maintenance and administration position).

Remedial actionPost the trunk that uses the TTP POST command to determine the state ofthe trunk. If possible, manually busy (ManB) the trunk. If this action doesnot work, contact the next level of support.


FormatTKCV100 mmmdd hh:mm:ss ssdd INFO TRK CONVERT TRBL

CKT cktid RECORD NUMBER = n

REASON = rsntxt




VariableDescription

INFO TRKCONVERT TRBL

Constant Variable Indicates trunk conversion trouble.

CKT Symbolic text Variable Identifies the circuit affected. Refer toTable I.

RECORD NUMBER Integer Variable Identifies the record number (fromTKCV data table) that caused theerror condition.

REASON Cannot change stateto MB

Variable Indicates the circuit cannot bemanual busy.

Cannot change stateto IDLE

Variable Indicates the circuit cannot be idle.

Cannot change stateto OFFLINE

Variable Indicates the circuit cannot be offline.

Cannot convert trunkto PTS

Variable Indicates the trunk cannot convert toper trunk signaling.

Cannot convert trunkto ISUP

Variable Indicates the trunk cannot convert toISDN User Part.

Continuity testFAILED

Variable Indicates a continuity test failed.

Active message exampleTKCV100 MAY31 09:00:00 2112 INFO TRK CONVERT TRBL

CKT ISUPOTG 5 RECORD NUMBER = 5

REASON = Cannot change state to OFFLINE



TME102The Terminal Management Environment (TME) subsystem generatesTME102 when the TME session updates the database while the journal leis not active.

Remedial actionExample 1 indicates that the journal le does not operate. Activate thejournal le. Example 2 notifies the operating company when the databasechanges through TME. Direct these log reports to a separate le so that thereports can be processed for billing purposes.

TME102 431



FormatTME102 mmmdd hh:mm:ss ssdd INFO TME UPDATE

TME SESSION UPDATED THE DATABASE WHEN JOURNAL FILE

WAS INACTIVE

AN ENTRY IN TABLE nametxt WAS actxt

THE LEN OF THE ENTRY WAS len DN dn

TME102 mmmdd hh:mm:ss ssdd INFO TME UPDATE

TME SESSION UPDATED THE DATABASE <Journal file status>

THE ADMINISTRATOR WAS: <LEN<DN<KEY NUMBER>

THE CHANGED DN WAS: <LEN<DN><KEY NUMBER>

THE AFFECTED DNS ARE IN COUSTOMER GROUP: <customer

group name>

AN ENTRY IN TABLE <TABLE NAME> WAS: <TABLE

OPERATION>

THE AFFECTED TUPLE IS:

<tuple data>


VariableDescription

INFO TME UPDATE Constant (BothFormats)

Variable Indicates the Terminal ManagementEnvironment (TME) session updatedthe database.

TME SESSIONUPDATE THEDATABASE WHENJOURNAL FILEWAS INACTIVE

Constant (Format 1) Variable Indicates the TME session updatedthe database when the journal filewas not active.




Description

AN ENTRY INTABLE

KSETFEATDNATTRS

Variable Identifies the table that the TMEsession updated in the database.

WAS CHANGED ADDEDDELETED

Variable Indicates the activity to the entry inthe database that the TME sessionupdated.

THE LEN OF THEENTRY WAS LEN

Integers Variable Identifies the line equipment number(LEN).

DN Integers Variable Identifies the directory number (DN).TME SESSIONUPDATED THEDATABASE

Symbolic text Variable Indicates the journal file status.

THEADMINISTRATORWAS

Alphanumeric Variable Indicates the LEN and DN of theadministrator.

THE CHANGED DNWAS

Alphanumeric Variable Indicates the changed LEN and DN.

THE AFFECTEDDNS ARE INCUSTOMERGROUP

Symbolic text Variable Indicates the customer group of theaffected DNs.

AN ENTRY INTABLE

Symbolic text Variable Indicates the table name.

WAS Character string Variable Indicates the table operationperformed.

THE AFFECTEDTUPLE IS

Alphanumeric Variable Indicates the tuple data.

Active message exampleTME102 JUN13 10:30:06 4169 INFO TME UPDATE

TME SESSION UPDATED THE DATABASE WHEN JOURNAL FILE WAS

INACTIVE

THE LEN OF THE ENTRY WAS REM4 00 0 1 24 DN 9097225033

THE ADMINISTRATOR WAS: HOST 00 1 07 07 DN 9097220177 KEY 1

TME102 JUN05 16:48:07 5000 INFO TME UPDATE

TME SESSION UPDATED THE DATABASE WHEN JOURNAL FILE WAS

INACTIVE

TME102 433


THE ADMINISTRATOR WAS:HOST 00 1 07 07 DN 9097220177 KEY 1

THE CHANGED DN WAS: HOST 00 1 07 07 DN 9097220177 KEY 1

THE AFFECTED DNS ARE IN CUSTOMER GROUP: COMKODAK

AN ENTRY IN TABLE TRKS WAS: ADDED

THE AFFECTED TUPLE IS:

HOST 00 1 07 07 5 RAG RAG



ToME301The Topology Mapping Environment (ToME) generates this log when theallocated number of VTids in the ToME VTids pool exceeds 90% of theinternally defined maximum number of VTids in the ToME VTids pool. Themaximum pool size is displayed in TOME601 log.

If the ToME VTids pool becomes exhausted, some features may be unableto operate normally.

TOME301 indicates that the number of VTids currently in use is exceeding90% of the maximum number of VTids available in the TOME VTids pool.This pool is expanded automatically until it reaches a maximum value.When the number of active ToME VTids exceeds 90% of the maximumvalue, TOME301 is generated.

TOME301 displays the "Number of times max threshold exceeded" value.This value indicates how many times the number of VTids in use hasexceeded the maximum threshold within 5 min of the rst time the thresholdwas exceeded. When this value is high and TOME301 is generated every5 min, the maximum threshold is being exceeded often and there is agreater risk of the TOME VTid pool reaching exhaustion.

As the sampling times for TOME301 and EXT OM 198 are notsynchronous, EXT OM 198 may need to be observed for approximately 10min before it displays information that agrees with TOME301.



Remedial actionComplete the following steps:

• View the latest version of log TOME601 to determine the currentnumber of VTids allocated and the maximum number that can beallocated.

• Determine the number of DITM extension blocks currently in use byentering OMSHOW EXT ACTIVE 198 at the command prompt. Checkthe EXTHI count of the displayed register. Each time a virtual agent isallocated, a TOME VTid and a DITM extension block are allocated.Therefore, if 27,000 VTids are currently in use, at least 27,000 DITMextension blocks will also be in use.

• Contact Nortel (Northern Telecom) with the information gathered.


FormatTOME301 mmdd hh:mm:ss ssdd INFO TOME VTID

THRESHOLD EXCEEDED

Number of times max threshold exceeded = nnn

Contact Nortel field support


VariableDescription

nnn Integer Variable The number of times the number ofactive VTids has exceeded 90% ofthe internally defined maximumnumber of VTids in the ToME VTidspool (the threshold) within 5 min ofthe first time the threshold isexceeded.

Active message exampleTOME301 SEP05 18:14:33 4827 INFO TOME VTID

THRESHOLD EXCEEDED

Number of times max threshold exceeded = 1

Contact Nortel field support

ToME301 435




ToME601The Topology Mapping Environment (ToME) generates this log when theallocated number of VTids in the ToME VTids pool expands toaccommodate the demands of the DMS switch load.

If the "New ToME Virtual TID Pool Size" field equals the "Maximum ToMEVtid Pool Size" field, the pool size cannot expand any further. Expansion tothis size indicates that the maximum number of VTids that can be allocatedmay need to be increased. This value is hardcoded, and can only beexpanded when loading a new release.

Remedial actionIf the "New ToME Virtual TID Pool Size" value equals the "Maximum ToMEVtid Pool Size" value, contact Nortel. Inform Nortel that the ToME VTidpool has expanded to is maximum value.


FormatTOME601 mmdd hh:mm:ss ssdd INFO EXPANDING ToMEVTID POOL

SIZE

New ToME Virtual TID Pool Size = nnnn

Maximum ToME Vtid Pool Size=mmmm


VariableDescription

nnnn Integer Variable The new size of the ToME VTidspool.

mmmm Integer Variable The maximum number of VTids thatcan be allocated in the ToME VTidpool. When the pool size equals thisvalue, the pool size does not expand.



Active message exampleTOME601 SEP05 18:14:33 4827 INFO EXPANDING ToMEVTID POOL

SIZE

New ToME Virtual TID Pool Size = 4096

Maximum ToME Vtid Pool Size = 30000



ToME602The Topology Mapping Environment (ToME) generates this log when thenumber of Data Interface and Topology Mapping (DITM) extension blocksin the DITM extension block pool concurrently in use nears exhaustion.

The number of DITM extension blocks in the DITM extension block pool isincreased by increasing the value of office engineering parameterNUMBER_OF_DITM_EXTENSION_BLOCKS in table OFCENG.

If the available number of DITM extension blocks in the DITM extensionblock pool becomes exhausted, some features may not operate normally.The number of DITM extension blocks should be increased as soon as thislog is generated.

This log indicates that the number of DITM extension blocks concurrentlyin use reached 90% of the total number of DITM extension blocks in theDITM extension block pool. When this threshold value is exceeded, thepool is nearing exhaustion. Increase the OFCENG office parmNUMBER_OF_DITM_EXTENSION_BLOCKS to avoid possible poolexhaustion.

ToME602 437


Remedial actionComplete the following steps:

• Determine the number of DITM extension blocks currently in use byentering OMSHOW EXT ACTIVE 198 at the command prompt. Checkthe EXTHI count of the displayed register. Note the value.

• Enter table OFCENG and position onNUMBER_OF_DITM_EXTENSION_BLOCKS office parameter. Verifythat the EXTHI count has exceeded 90% of the office parameter. Theoffice parameter indicates the number of DITM extension blockscurrently allocated.

• Increase the value of the office parameter to accommodate the DMSswitch''s demand on DITM extension blocks.


FormatTOME602 mmdd hh:mm:ss ssdd DITM AGENT POOL SIZE

THRESHOLD REACHED

Check OM register EXT #198 DITM_AGENT_EXT_BLOCKS

NUMBER_OF_DITM_EXTENSION_BLOCKS office parm may need

to be increased. Number of times max threshold exceeded

during audit delay = nnn


VariableDescription

nnn Integer Variable The number of times the number ofDITM extension blocks concurrentlyin use has exceeded 90% of the totalnumber of DITM extension blocksavailable in the DITM extension blockpool (the threshold) during the last 5min.

Active message exampleTOME602 SEP05 18:14:33 4827 DITM AGENT POOL SIZE

THRESHOLD REACHED



Check OM register EXT #198 DITM_AGENT_EXT_BLOCKS

NUMBER_OF_DITM_EXTENSION_BLOCKS office parm may need

to be increased. Number of times max threshold exceeded

during audit delay = 4



ToME602 439


C20 Converged Softswitch

Logs and Alarms Reference, Volume 17Release: CVM16Publication: NN10275-909v17Document Revision: 12.03Document release date: 13 May 2013

Copyright © 2010-2013 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.

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

www.genband.com

nn10275-909v17_12.03_cvm16_c20_logs-alarms

Documents

genband andor

property of genband

employees of genband

genband corporate logo

alarms reference

software andor documentation

software license agreement

information andor