Alarm Clearing 297-2651-543 v1 PDF

297-2651-543
Digital Switching Systems

DMS-Global Services Platform
Alarm Clearing and Performance Monitoring
Procedures Manual Volume 1 of 3
GSP05 (CSP10) Standard 05.01 March 1999
DMS-Global Services Platform

Alarm Clearing and Performance Monitoring Procedures
Manual Volume 1 of 3
Publication number: 297-2651-543

Product release: GSP05 (CSP10)
Document release: Standard 05.01
Date: March 1999
 1997–1999 Northern Telecom

All rights reserved
Printed in the United States of America
NORTHERN TELECOM CONFIDENTIAL: The information contained in this document is the property of Northern
Telecom. Except as specifically authorized in writing by Northern Telecom, the holder of this document shall keep the
information contained herein confidential and shall protect same in whole or in part from disclosure and dissemination to third
parties and use same for evaluation, operation, and maintenance purposes only.
Information is subject to change without notice. Northern Telecom reserves the right to make changes in design or components
as progress in engineering and manufacturing may warrant.
DMS, MAP, NORTEL, NORTEL NETWORKS, NORTHERN TELECOM, NT, and SUPERNODE are trademarks of Northern
Telecom.
Digital Switching Systems Alarm Clearing and Performance Monitoring Procedures Manual Volume 1 of 3
GSP05 (CSP10)
ii
Publication history
March 1999
Standard release 05.01. This version contains information for the software
release GSP05 (CSP10).
August 1998
April 1998
September 1997
July 1997
Preliminary release 02.01. This version contains information for the
software release GCS01 (CSP07).
March 1997
Standard release 01.03. No content changes.
January 1997
Preliminary release 01.02 of this document. Upissued to correct front
section.
January 1997
Preliminary release version 01.01. This version contains information for the
software release GCS01 (CSP06).
297-2651-543 Standard 05.01 March 1999

iii
Contents
Volume 1
About this document ix
When to use this document ix
How to check the version and issue of this document ix
How this document is organized ix
Explanatory and context-setting information x
Summary flowchart x
Step-action instructions x
References in this document x
Procedures to clear application alarms 1-1

Introduction 1-1
Alarm display 1-1
Indication 1-1
Meaning 1-1
Result 1-1
Common procedures 1-1
Action 1-2
APPL CallP major 1-3
Common channel signaling alarm clearing procedures 2-1

Introduction 2-1
Alarm display 2-1
Indication 2-1
Meaning 2-1
Result 2-1
Action 2-2
CCS LK minor 2-3
CCS LK minor in a DPNSS 2-26
CCS LKM major 2-37
CCS LSSC critical 2-62
CCS LSSM 2-72
CCS PC minor 2-82
CCS PCC critical 2-86
CCS RS critical 2-91
Ext MALO Major 2-99
Ext MALT Major 2-103
GSP05 (CSP10)
iv Contents
CCS RS major 2-107

CCS RSSC critical 2-113
CCS RTRC critical 2-122
CCS RTRM major 2-133
Computing module alarm clearing procedures 3-1

Introduction 3-1
Alarm display 3-1
Indication 3-1
Meaning 3-1
Result 3-1
Action 3-2
CM MMsync major 3-3
CM AutoLd minor 3-6
CM CBsyMC major 3-9
CM ClkFlt major 3-18
CM CMTrap major 3-27
CM E2A minor 3-30
CM EccOn minor 3-34
CM IMAGE critical 3-40
CM JInact minor 3-43
CM LowMem critical 3-46
CM LowSpr major 3-55
CM LowSpr minor 3-64
CM MBsyMC major 3-74
CM MC Tbl minor 3-84
CM MemCor major 3-98
CM MemCfg minor 3-104
CM MemCor minor 3-120
CM MemFlt minor 3-123
CM MemLim minor 3-129
CM NoBrst minor 3-132
CM NoOvr minor 3-140
CM MMnoSy major 3-148
CM NoSYNC major 3-158
CM NoTOD critical 3-164
CM CMFlt major 3-172
CM PMCFlt major 3-188
CM PMCTbl minor 3-199
CM PrcOpt major 3-210
CM RExFlt major 3-213
CM RExSch minor 3-217
CM RExTst minor 3-224
CM SBsyMC major 3-230
CM SLMLIM major 3-243
CM SLMLim minor 3-246
CM SRAMFL major 3-249
CM SramFl minor 3-257
CM StrAlc critical 3-260
MCCNACK 3-263
297-2651-543 Standard 05.01 March 1999

Contents v
Procedures to clear an external alarm 4-1

Introduction 4-1
Alarm display 4-1
Indication 4-1
Meaning 4-1
Result 4-1
Action 4-2
Ext Crit critical 4-3
Ext Maj major 4-12
Ext Min minor 4-37
Ext E911_ALI_MAJOR major 4-46
Ext E911_ALI_MINOR minor 4-51
Ext CPPOOL critical 4-56
Ext CPPOOL major 4-61
Ext CPPOOL minor 4-66
Ext FSP major 4-71
Ext FSP GPP cabinet with an MSP shelf major 4-75
Ext FSP APC cabinet major 4-86
Ext FSP CCC frame major 4-98
Ext FSP CDSN cabinet with an MSP shelf major 4-110
Ext FSP CIOE cabinet with an MSP shelf major 4-119
Ext FSP CIPE cabinet with an MSP shelf major 4-127
Ext FSP CISM, CMTA, and CTME cabinet with an MSP shelf major 4-136
Ext FSP CPDC cabinet major 4-146
Ext FSP DCE frame major 4-156
Ext FSP DPCC cabinet major 4-167
Ext FSP DSNE frame or CDSN cabinet major 4-178
Ext FSP DTE or IDTE frame major 4-188
Ext FSP TME frame or CTME cabinet with FSP shelf major 4-199
Ext FSP IOE frame and CIOE cabinet major 4-214
Ext FSP LPP and ELPP cabinet major 4-225
Ext FSP MEX frame major 4-235
Ext FSP MS7E frame major 4-254
Ext FSP NET0 or NET1 frame (with fuses only) major 4-265
Ext FSP NET0 or NET1 frame (circuit breakers and fuses) major 4-276
Ext FSP NETC frame major 4-286
Ext FSP PDC frame major 4-296
Ext E911_PSAP_OFFHK minor 4-307
Ext E911_RCER_MAJOR major 4-314
Ext E911_RCER_MINOR minor 4-319
Ext FSP RLCE frame major 4-324
Ext JESCALL minor 4-346
Ext JESUNANS minor 4-350
Ext E911_SRDB_MEMORY minor 4-354
Procedures to clear an Input/output device alarm 5-1

Introduction 5-1
Alarm display 5-1
Indication 5-1
GSP05 (CSP10)
vi Contents
Meaning 5-1
Results 5-1
Action 5-2
IOD nDDUOS on an IOM major or minor 5-3
IOD nIOCOS on an IOM major or minor 5-18
IOD MPCLNK on an IOM minor 5-26
IOD nCKOS on an IOM major or minor 5-39
IOD nCKEr on an IOM minor 5-53
IOD ssys B critical 5-63
IOD DEVBnn critical, major, or minor 5-64
IOD DMNTnn minor 5-67
IOD HOLDnn minor 5-74
IOD ITOC critical 5-77
IOD ITOC minor 5-86
IOD KEEPn minor 5-95
IOD MPCLNK minor 5-98
IOD nCKEr minor 5-109
IOD nCKEr on an IOM minor 5-117
IOD nCKOS major or minor 5-127
IOD nDDUOS major or minor 5-138
IOD nDPCOS minor 5-155
IOD nIOCOS major or minor 5-161
IOD nMPCOS in an IOC major or minor 5-170
IOD nMTDOS in an IOC minor 5-184
IOD nnAMA critical, major, or minor 5-195
IOD nnJF critical, major, or minor 5-199
IOD nnOM critical, major, or minor 5-204
IOD NO AMA on device type DISK critical 5-208
IOD NO AMA on device type TAPE critical 5-218
IOD NOssys on device type TAPE critical 5-235
IOD NOssys on device type DISK critical, major, or minor 5-252
IOD nSVC critical 5-262
IOD nCKOS on an IOM major or minor 5-269
IOD nMTDOS on an IOM minor 5-283
IOD nMPCOS on an IOM major or minor 5-303
IOD PnnVnn minor 5-319
IOD POOLnn minor 5-331
IOD SCAX25 major 5-338
IOD SENDn minor 5-343
IOD SLMbsy major 5-348
IOD SLMbsy minor 5-355
IOD SLMoff minor 5-361
IOD SLMtbl minor 5-368
IOD ssys B minor 5-374
IOD ssys E minor 5-377
IOD ssys F minor 5-381
IOD ssys I minor 5-384
IOD ssys MP or ssys P critical 5-390
IOD XMITn minor 5-400
297-2651-543 Standard 05.01 March 1999

Contents vii
Lines alarm clearing procedures 6-1

Introduction 6-1
Alarm display 6-1
Indication 6-1
Meaning 6-1
Impact 6-1
Action 6-2
Lns DF Major 6-3
Lns DIAG critical, major, or minor 6-7
Lns FAC major 6-11
Lns HZD major 6-15
Lns IMAJ major 6-19
Lns IMIN major 6-23
Lns LCARD major 6-27
Lns LSET major 6-31
Lns MCARD critical, major, or minor 6-35
Lns MSET major 6-39
Lns NDIAG major 6-43
Lns PSDF critical, major, or minor 6-47
Lns PSPD major 6-51
Lns QDIAG major 6-55
Lns SDIAG major 6-59
Lns TCM major 6-63
Lns OMAJ critical, major, or minor 6-67
Lns OMIN critical, major, or minor 6-71
Volume 2
Message Switch alarm clearing procedures 1-1
Introduction 1-1
Alarm display 1-1
Indication 1-1
Meaning 1-1
Result 1-1
Action 1-2
MS CCFB minor 1-3
MS CLOCK major 1-8
MS CMIC minor 1-11
MS DDM major 1-25
MS FCFB minor 1-32
MS IMSL minor 1-37
MS Istb minor 1-46
MS ManB major 1-63
MS MaxPt minor 1-67
MS MBCD minor 1-70
MS MBCH minor 1-80
MS MBCL minor 1-90
MS MbFb minor 1-101
GSP05 (CSP10)
viii Contents
MS MBPT minor 1-106

MS MbTp minor 1-112
MSpair critical 1-117
MS NOIMSL major 1-120
MS REx minor 1-129
MS RExByp minor 1-133
MS RExFlt minor 1-148
MS SBCD minor 1-157
MS SBCH minor 1-168
MS SBCL minor 1-178
MS SbFb major 1-189
MS SBPT minor 1-194
MS SbTp major 1-205
MS SPAN minor 1-210
MS SysB major 1-214
MS TRIstb minor 1-228
MS TROOS major 1-231
Network alarm clearing procedures 2-1

Introduction 2-1
Alarm display 2-1
Indication 2-1
Meaning 2-1
Result 2-1
Action 2-2
Net Bsy minor 2-3
Net CBsy major 2-9
Net CdPr critical 2-25
Net CSLk minor 2-31
Net ISTb in JNET minor 2-42
Net ISTb in ENET minor 2-49
Net ISTb on a crosspoint card minor 2-53
Net ISTb on a link minor 2-58
Net ISTb on a system card minor 2-66
Net JcTr minor 2-73
Net Link minor 2-82
Net MBCd minor 2-94
Net MBsy minor 2-100
Net RexByp 2-106
Net Pair critical 2-109
Net PSLk minor 2-116
Net LOAD minor 2-129
NetREx minor 2-142
Net RExOff minor 2-145
NetRExSch minor 2-148
Net SBCd major 2-154
Net SBsy major 2-160
Net Shlv critical 2-165
Net SysB major 2-169
297-2651-543 Standard 05.01 March 1999

Contents ix
Peripheral module alarm clearing procedures 3-1

Introduction 3-1
Alarm display 3-1
Indication 3-1
Meaning 3-1
Impact 3-1
Action 3-2
Clearing PM C-side faults 3-3
Clearing PM C-side faults 3-19
PM APU critical 3-38
PM APU major 3-64
PM APU minor 3-86
PM CBSY major 3-117
Monitoring system maintenance PM 3-121
PM DCH major 3-127
PM DCH minor 3-139
PM DTC critical 3-162
PM DTC major 3-185
PM DTC minor 3-209
PM EIU critical 3-225
PM EIU major 3-255
PM EIU minor 3-282
Ext ESR minor 3-315
Ext ESR_TIME_ALARM minor 3-319
PM EXND minor 3-323
PM FP CPUFlt minor 3-329
PM FP critical 3-337
PM FP device-related fault minor 3-343
PM FP JInact minor 3-360
PM FP LowMem minor 3-363
PM FP major 3-372
PM FP MemCor minor 3-378
PM FP MemFlt minor 3-385
PM FP minor 3-391
PM FP MMThrs minor 3-396
PM FP NoOvr minor 3-399
PM FP NoSync minor 3-405
PM FP PrtFlt minor 3-411
PM FP PrtTbl minor 3-416
PM FP Trap minor 3-426
PM GPP critical 3-429
PM GPP major 3-455
PM GPP minor 3-496
PM HLIU critical 3-514
PM HSLR critical 3-529
PM IPML major or minor 3-544
PM ISTb minor 3-553
PM LCME minor 3-564
PM LCME major 3-576
GSP05 (CSP10)
x Contents
PM LCM critical 3-590

PM LCM major 3-606
PM LCM minor 3-622
PM LGC critical 3-633
PM LGC major 3-658
PM LGC minor 3-681
PM VLCM minor 3-697
Ext FSP LME frame (with fuses only) major 3-702
PM LCM ringing generator (LRG) critical 3-718
Ext FSP RLM frame (with fuses only) major 3-728
PM talk battery critical 3-743
PM talk battery minor 3-757
Volume 3
Peripheral module (PM) alarm clearing procedures (cont’d) 1-1
PM LIMF critical 1-2
PM LIM critical 1-15
PM LIU7 critical 1-30
PM NIU critical 1-48
PM VLCM critical 1-71
PM VPU critical 1-78
PM XLIU critical 1-108
PM LIMF major 1-124
PM LIM major 1-137
PM LIU7 major 1-154
PM NIU major 1-171
APPL SDM critical 1-188
PM VPU major 1-189
PM XLIU major 1-214
PM LIM minor 1-230
PM LIMREX minor 1-243
PM LIU7 minor 1-244
PM NIU minor 1-267
APPL SDM minor 1-305
PM VPU minor 1-306
PM XLIU minor 1-337
PM LMPr critical 1-360
PM LTC critical 1-370
PM LTC major 1-393
PM SysB major 1-417
PM LMRex minor 1-433
PM PMLOAD minor 1-438
PM LTC minor 1-451
PM LMDrwr major or minor 1-468
PM LMRGen major or minor 1-474
PM LTCI critical, major, or minor 1-479
PM MSB6, MSB7 critical, major, or minor 1-534
PM STC major or minor 1-574
297-2651-543 Standard 05.01 March 1999

Contents xi
Trunks group (Trks) alarm clearing procedures 2-1

Trks C minor 2-2
Trks CB critical, major, or minor 2-7
Trks CC critical 2-14
Trks CE critical, major, or minor 2-22
Trks CG minor 2-27
Trks CM major 2-35
Trks CR C and CR M critical 2-43
Trks CS critical, major, or minor 2-53
Trks EX critical, major, or minor 2-61
Trks GC, GM, and G critical, major, or minor 2-66
Trks MB critical, major, or minor 2-75
Trks MJ C and MJ M critical or major 2-81
Trks MN C and MN M critical or major 2-91
Trks SB critical, major, or minor 2-101
Alarm clearing common procedures 3-1

Introduction to alarm clearing common procedures 3-1
Application 3-1
Action 3-1
Returning LIM-to-MS links to service 3-2
Activating CCS7 links 3-29
Activity switch with memory match 3-45
Allocating a volume 3-55
Checking the electronic fuse unit in an LME or RLM frame 3-59
Connecting temporary fiber cable between MS and SSLPP 3-64
Connecting temporary fiber cable from an ENET to an MS 3-76
Connecting temporary fiber cable from an ENET to a PM 3-88
Correcting a load mismatch 3-100
Deallocating a volume 3-117
Failure to switch clock mastership 3-121
Moving an XSG to a spare XLIU 3-132
Resetting a volume 3-139
Restoring LIM unit cross-links 3-143
Running a C7BERT 3-158
Loading a PM 3-198
Clearing ringing generator faults LCM 3-207
Clearing lines alarms 3-213
GSP05 (CSP10)
xii
About this document

When to use this document
This document is used to perform alarm clearing procedures on the DMS-
Global Services Platform (GSP) switch alarm panel.
How to check the version and issue of this document

The version and issue of the document are indicated by numbers, for
example, 01.01.
The first two digits indicate the version. The version number increases each
time the document is updated to support a new software release. For
example, the first release of a document is 01.01. In the next software
release cycle, the first release of the same document is 02.01.
The second two digits indicate the issue. The issue number increases each
time the document is revised but rereleased in the same software release
cycle. For example, the second release of a document in the same software
release cycle is 01.02.
This document is written for all DMS Family offices. More than one
version of this document may exist. To determine whether you have the
latest version of this document and how documentation for your product is
organized, check the release information.
To determine which version of this document applies to the software in your

office and how documentation for your product is organized, check the
release information in DMS-Global Services Platform Master Index of
Publications, 297-2651-001.
How this document is organized

Each alarm procedure contains the following:
• explanatory and context-setting information
• summary flowchart
• step-action instructions
297-2651-543 Standard 05.01 March 1999

About this document xiii
Explanatory and context-setting information

The first page of each procedure contains the following headings:
• Indication (where the alarm appears in the MAP display)
• Meaning (what it means)
• Impact (how it affects service)
• Common procedures (common procedures needed to perform the
procedure, if applicable)
• Action (how to use the flowchart and step-action instructions)
Summary flowchart
The flowchart summarizes the main actions, decision points, and possible
paths you may take. Do not use the summary flowchart to perform the
procedure. Instead, use it to preview what you need to do to prepare for
clearing an alarm. For example, if the instructions involve another office,
you will know to advise that office before you begin the step-action
instructions.
Step-action instructions
While following the step-action instructions, you may be directed to the
Common procedures chapter of this document to perform a set of
instructions, or to another NTP, such as Card Replacement Procedures
Manual, for a related procedure. If this happens, the instructions will tell you
when to return to the original procedure and to which point in the procedure
you should go.
References in this document

The following documents are referred to in this document:
• Card Replacement Procedures Manual, 297-2651-547
• Log Reference Manual, 297-2651-840
• Office Parameters Reference Manual, 297-2651-855
• Recovery Procedures Reference Manual, 297-2651-545
• Routine Maintence Procedures Manual, 297-2651-546
• Trouble Locating and Clearing Procedures Manual, 297-2651-544
GSP05 (CSP10)
1-1
Procedures to clear application alarms

Introduction
This chapter provides procedures to clear application alarms. Application
alarms appear under the APPL header of the alarm banner in the MAP
display. All of the procedures contain the following sections:
• Alarm display
• Indication
• Meaning
• Result
• Common procedures
• Action
Alarm display
This section indicates how the alarm appears at the MAP terminal.
Indication
This section indicates:
• the location of the alarm indication
• how the system represents the alarm
• the affected subsystem
• the alarm level
Meaning
This section indicates the cause of the alarm.
Result
This section describes the results of the alarm condition.
Common procedures
This section lists common procedures used during the alarm clearing
procedure. A common procedure is a series of steps repeated within
GSP05 (CSP10)
1-2 APPL alarm clearing procedures
maintenance procedures, for example card removal and replacement.

Common procedures appear in the common procedures chapter in this NTP.
Do not use common procedures unless the step-action procedure directs you
to the common procedures.
Action
This section provides a summary flowchart of the procedure and a list of
steps to clear an alarm. A detailed step-action procedure follows the
flowchart.
297-2651-543 Standard 05.01 March 1999

1-3 Application alarm clearing procedures 1-3
APPL CallP
major
Alarm display
CM MS IOD Net PM CCS Lns Trks Ext APPL
. . . . . . . . . CallP
M
Indication
At the MTC level of the MAP display, CallP appears under the APPL header
of the alarm banner. The CallP indicates a call processing (CallP) major
alarm.
Meaning
Continuous traps occur on software for the call processing base (CallP Base)
during the processing of CallP transactions. A minimum of 20 traps in a
maximum of one minute cause service maintenance to raise this alarm. The
service maintenance system attempts to clear the alarm automatically.
Result
The system cannot permanently deny call originations and feature
activations. The service maintenance system attempts to clear the alarm.
The CallP Base service is in a state of in-service trouble while the system
attempts to clear the alarm.
Common procedures
There are no common procedures.
Action
Manual action is not needed to clear the alarm. The service maintenance
system responds to traps in CallP Base and attempts to clear the fault
automatically. A continuous alarm indicates that call processing software
traps at a low rate.
GSP05 (CSP10)
1-4 Application alarm clearing procedures
APPL CallP
major (continued)
(end)
Summary of Clearing an APPL CallP major alarm
Wait ten This flowchart summarizes the

minutes for procedure.
alarm to clear
automatically Use the instructions that follow
this flowchart to perform the
procedure.
Did the Y End
alarm
clear?
Contact next
level of support
Clearing an APPL CallP major alarm

At the MAP display
1 To access the MTC level of the MAP display, type
> MAPCI;MTC
and press the Enter key.
2 Wait ten minutes for the system attempt to clear software traps of the CallP
Base service.
If the CallP major alarm Do
cleared step 4
did not clear step 3
3 For additional help, contact the next level of support.
4 The procedure is complete.
297-2651-543 Standard 05.01 March 1999

2-1
Common channel signaling alarm

clearing procedures
Introduction
This chapter provides alarm clearing procedures for common channel
signaling. The MAP display indicates alarms for common channel signaling
under the CCS header of the alarm banner. Each procedure contains the
following sections:
• Alarm display
• Indication
• Meaning
• Result
• Action
Alarm display
This section indicates how the MAP terminal displays the alarm.
Indication
• where the alarm indication appears
• how the system represents the alarm
• the alarm level.
Meaning
Result
GSP05 (CSP10)
2-2 CCS alarm clearing procedures
Common procedures
maintenance procedures, for example card removal and replacement. You
can find common procedures in the common procedures chapter in this NTP.
Do not use a common procedure unless the step-action procedure directs you
to the common procedure.
Action
This section provides a summary flowchart and a list of steps. A detailed
step-action procedure follows the flowchart.
297-2651-543 Standard 05.01 March 1999

2-3 Common channel signaling alarm clearing procedures 2-3
CCS LK
minor
Alarm display
. . . . . 1LK . . . .
Indication
At the MTC level of the MAP display, a number and LK appear under the
CCS header in the alarm banner. The LK indicates a minor alarm for a
linkset (LK).
Meaning
An LK has in-service trouble. Not all links in the LK have in-service
trouble or are out of service. The number of links in service is less than the
required threshold number.
The number under the CCS header in the alarm banner indicates the number
of LKs affected.
Result
The LK carries traffic, but the traffic can be at a degraded level of service.
Clear this alarm at the first opportunity. If all signaling links in the
in-service trouble LK go out of service, a linkset major (LKM) alarm rises.
The LK cannot carry traffic after a LKM alarm rises.
If a total router outage (TRO) occurs, all CCS7 links are blocked (Blkd) and
taken out of service. During a TRO, the system does not transmit or receive
the ISDN user part (ISUP) or transaction capabilities application part
(TCAP) messages. The CCS7 network receives a message that CCS7 links
are out of service. The CCS7 network also receives a message that the
office for the service switching point (SSP) no longer provides service.
The system refuses commands entered by operating company personnel.

The (Blkd) condition must clear before the system accepts a return to service
(RTS), activate (ACT), and uninhibit (UNIH) command.
Common procedures
This procedure refers to Running a C7BERT.
GSP05 (CSP10)
2-4 Common channel signaling alarm clearing procedures
CCS LK
minor (continued)
Do not go to the common procedure unless the step-action procedure directs
you to go.
Action
This procedure contains a summary flowchart and a list of steps. Use the
flowchart to review the procedure. Follow the steps to perform the
procedure.
297-2651-543 Standard 05.01 March 1999

CCS LK
minor (continued)
Summary of Clearing a CCS LK minor alarm
Check for PM This flowchart summarizes the

alarms procedure.
Use the instructions that follow this

flowchart to perform the procedure.
Do LIM or Y Perform correct
LIU7 alarms PM alarm 1
appear? clearing
procedure
1 N
Check traffic
and sync states
of a link
Restore link
N Are there more Y

Linkset in links that have 2
service? faults you can try?
Y N
End Contact next
level of support
GSP05 (CSP10)
CCS LK
minor (continued)
Summary of Clearing a CCS LK minor alarm

alarms procedure.
Use the instructions in the

step-action table that follows this
LIM, LIU7, Y Perform flowchart to perform the procedure.
HLIU, or HSLR appropriate PM 1
alarms running? alarm clearing
procedure
1 N
Check traffic
and sync states
of a link
Restore link
N Y
Linkset in Are there more
faulty links you 2
service?
can try?
Y N
End Contact next

level of support
297-2651-543 Standard 05.01 March 1999

CCS LK
minor (continued)
Clearing a CCS LK minor alarm
At the MAP display
1 To access the C7LKSET level of the MAP display, type
>MAPCI;MTC;CCS;CCS7;C7LKSET
2 Check under the PM level of the MAP display alarm banner. Determine if
alarms appear for the link interface module (LIM) or link interface unit for the
CCS7 (LIU7).
Determine if LIM, LIU7, HLIU, or HSLR alarms appear under the PM header in
the MAP alarm banner.
If LIM or LIU7 alarms Do
If LIM, LIU7, HLIU, or HSLR

alarms Do
appear step 3
do not appear step 4
3 Perform the correct alarm clearing procedures in this document to clear all PM
LIM or PM LIU7 alarms. Complete the procedures and return to this point.
Perform the appropriate alarm clearing procedures in this document to clear all
PM LIM, PM LIU7, PM HLIU, or PM HSLR alarms. When you have completed
the procedures, return to this point.
4 To post an LK that runs an LK minor alarm, type

>POST A LK
GSP05 (CSP10)
CCS LK
minor (continued)
Example of a MAP display:
Linkset SSP100_LK ISTb
Traf Sync Link
LK Stat Stat Resource Stat Physical Access Stat Action
0 SysB Sync LIU7 101 InSv DS0A
1 ISTb Sync LIU7 103 InSv DS0A
2 Blkd Alnd LIU7 105 InSv DS0A
Size of Posted Set = 3
If you Do
posted an in-service trouble LK step 5

did not post an in-service trouble LK step 56
5 Record the LK name.

Note: The LK name appears on the right of the Linkset header on the MAP
display.
6 Determine from office records which far-end office connects to the posted LK.
7 Contact the far-end office to determine if the office has LIM or LIU7 alarms.
If the far-end office Do
has LIM or LIU7 alarms step 8

does not have LIM or LIU7 alarms step 9
has LIM, LIU7, HLIU, or HSLR step 8
alarms
does not have LIM, LIU7, HLIU, or step 9
HSLR alarms
8 Wait until the far-end office problems clear. Check the MAP display to
determine the state of the posted LK.
Note: The LK state appears on the right of the LK name.
297-2651-543 Standard 05.01 March 1999

CCS LK
minor (continued)
Linkset SSP100_LK SYSB
Traf Sync Link
If the state of the linkset Do
is InSv step 56
is RInh, LInh, ISTb, ManB, or step 9
SysB
is ISTb, ManB, or SysB step 9
is Blkd step 9
9 Determine if out-of-service or in-service trouble links are in the list for the
posted LK.
Note: The link traffic state appears under the Traf Stat header in the MAP
display. Four links can show at one time in the posted LK. The word MORE
appears at the bottom of the MAP display if more than four links are in the LK.
Traf Sync Link
If Do
out-of-service or ISTb links appear. step 11

You did not work on any of these
links
out-of-service or Blkd links appear. step 10
You worked on all of these links.
Additional links will display
GSP05 (CSP10)
CCS LK
minor (continued)
If Do
out-of-service or ISTb links appear. step 52

You worked on all of these links.
There are no additional links to
display
all displayed links are InSv. step 10
Additional links will display
all displayed links are InSv. There step 52
are no additional links to display
10 To display the next four links in the posted LK, type

>NEXT
Go to step 9.
11 To choose an out-of-service or in-service trouble link, look at the traffic state for
each link.
Note: The link traffic state appears under the Traf Stat header of the MAP.
If the traffic state for Do
a minimum of one link is RInh. You step 14

did not work on the link
a minimum of one link is LInh. You step 17
a minimum of one link is Blkd. You step 14
a minimum of one link is ManB. You step 23
a minimum of one link is IsTb or step 25
SysB. You did not work on the link
all links are RInh, LInh, IsTb, step 55
ManB, or SysB. These links failed to
return to service
a minimum of one link is ManB. You step 23
297-2651-543 Standard 05.01 March 1999

CCS LK
minor (continued)
a minimum of one link is ISTb or step 25

SysB. You did not work on the link
all links are ISTb, ManB, or SysB. step 55
These links failed to return to
service
12 To determine the type of the faults on the link, type

>QUERYFLT link_no
where
link_no is the number of the link (0 to 8)
Linkset COMR_COML_LKSET SysB
Traf Sync Link

QueryFlt 0
Link in Blkd state due to unavailability of External Routing
Display CCS alarms for External Routing information
13 To clear the Blkd condition, display the CCS RSRC or RTRM alarms.
To clear the alarms, bring additional routers online. Use the following
procedures to bring the routers online:
• How to clear an RSC alarm
• How to clear an RTRM alarm.
Go to step 44.
15 Contact the far-end office to determine why the operating company personnel
inhibited the link at that location.
GSP05 (CSP10)
CCS LK
minor (continued)
16 Wait until the far-end office restores the link. Determine the traffic state of the
remote inhibited link.
Note: The link traffic state appears under the Traf Stat header of the MAP
display.
Traf Sync Link
0 InSv Sync LIU7 101 InSv DS0A
If the link traffic state Do
is InSv step 52
is LInh step 17
is ManB step 23
is ISTb or SysB step 25
17 Determine from office records or from operating company personnel why the
link is inhibited locally.
18 When you have permission to uninhibit the link, type

>UINH link_no
where
link_no is the number of the inhibited link (0 to 15)
If the UINH command Do
passed step 19
failed. This attempt is the first step 20
attempt to uninhibit the link
failed. This attempt is the attempt to step 9
uninhibit the link
297-2651-543 Standard 05.01 March 1999

CCS LK
minor (continued)
19 Determine the link traffic state.

Note: The link traffic state appears under the Traf Stat header on the MAP
display.
Traf Sync Link
is InSv step 52
is other than listed here step 9
20 Contact your next level of support to determine if entries that relate to the link
changed at either end of the link.
If entries Do
changed at either end of the link step 21

did not change at either end of the step 22
link
21 Contact the next level of support. Follow the instructions that the next level of
support supplies to correct the problem.
When you correct the problem, go to step 18.
22 Consult your next level of support to determine why the UINH command failed.
link is manual busy.
When you have permission, continue this procedure.
24 To return the link to service, type

>RTS link_no
GSP05 (CSP10)
CCS LK
minor (continued)
where
If the RTS command Do
failed step 9
passed, but the link traffic state is step 14
RInh
LInh
ISTb or SysB
passed, and the link traffic state is step 52
InSv
297-2651-543 Standard 05.01 March 1999

CCS LK
minor (continued)
25 Determine the link synchronization state.

Note: The link synchronization state appears under the Sync Stat header of
the MAP display.
Traf Sync Link
If the link synchronization state Do
is Sync or Alnd step 42

26 To inhibit the link, type

>INH link_no
where
link_no is the number of the link (0 to 15) you want to inhibit
If the INH command Do
passed step 27
failed, and the link traffic state is step 27
SysB
ISTb
GSP05 (CSP10)
CCS LK
minor (continued)
27 To manually busy the link, type

>BSY link_no
where
If the response Do
is Link link_no:Traffic is step 28

running on that link
Please confirm
(“YES”,“Y”,“NO”, or “N”):
is a message not listed here, which step 55
can include the preceding response
28 To confirm the command, type

>YES
29 To deactivate the link, type

>DEACT link_no
where
297-2651-543 Standard 05.01 March 1999

CCS LK
minor (continued)
30 To activate the link, type

>ACT link_no
where
If the ACT command Do
passed, and the link synchronization step 44

state is Sync or Alnd
state is not Sync or Alnd
failed step 33

>RTS link_no
where
32 To uninhibit the link, type

>UINH link_no
where

state is either Sync or Alnd
state is neither Sync or Alnd
failed step 33
GSP05 (CSP10)
CCS LK
minor (continued)
33 Wait 8 min to see if the link activates.

is other than listed here. You did not step 34
ask the far-end office to activate the
link
is other than listed here. You asked step 9
the far-end office to activate the link
34 Inform operating company personnel at the far-end office that:

• You will busy, deactivate, return to service, and activate the link to align the
link again.
• The link must activate from both ends after you busy, deactivate, and return
the link to service.
Coordinate your activities with the activities of the far-end office to realign the
link.

>INH link_no
where
passed step 36
SysB
ISTb
297-2651-543 Standard 05.01 March 1999

CCS LK
minor (continued)

>BSY link_no
where
If the response Do

Please confirm
(“YES”,“Y”,“NO”, or “N”):
is other than listed here, which can step 55
include the preceding response

>YES

>DEACT link_no
where
Note: If the link is associated with an HLIU or HSLR, do not use the DEACT
command. Go to step 39.

>RTS link_no
where
GSP05 (CSP10)
CCS LK
minor (continued)
40 Inform operating company personnel at the far-end office to activate the link
you have in use. Activate the link at your end at the same time as the far-end
office activates the far-end office link. Type
>ACT link_no
where

failed step 9

>UINH link_no
where

state Sync or Alnd
failed step 9
297-2651-543 Standard 05.01 March 1999

CCS LK
minor (continued)
42 Determine the traffic state of the link.

display.
Traf Sync Link
is InSv step 52
is other than InSv step 43
is other than InSv step 44

>INH link_no
where
passed step 44
SysB
ISTb
GSP05 (CSP10)
CCS LK
minor (continued)

>BSY link_no
where
If the response Do

confirm
(“YES”,“Y”,“NO”, or “N”):
is other than listed here, which can step 55
include the preceding response

>YES
46 To test the link, type

>TST link_no
where
If the TST command Do
passed step 48
failed, and you did not run a bit error step 47
rate test on the link
failed step 9
failed, and you ran a bit error rate step 9
test on the link
297-2651-543 Standard 05.01 March 1999

CCS LK
minor (continued)
47 Perform the procedure Running a C7BERT in this document. Complete the

procedure and return to this point.
Note: Perform a bit error rate test on any link in the posted linkset that fails the
manual test at step 46.
Go to step 50.

>RTS link_no
where
passed, and the link is LInh step 51

passed step 52
failed. This attempt is the first step 49
attempt with the RTS command at
this point
failed. This attempt is the second step 9
attempt with the RTS command at
this point
49 Wait 10 min.
Go to step 48.
50 Your next action depends on the results of the bit error rate test.
If during the bit error rate test the

system instructed you Do
to return the link to service step 51

to not return the link to service step 9
GSP05 (CSP10)
CCS LK
minor (continued)

>UINH link_no
where
passed, and the link is InSv step 52

passed, and the link is not InSv step 9
failed step 9
52 Determine the LK state.

Note: The LK state appears on the right of the LK name on the MAP display.
Linkset SSP100_LK InSv
Traf Sync Link
is InSv step 56
is ManB, ISTb, or SysB. All links step 53
are InSv
is ManB, ISTb, or SysB. None of step 9
the displayed links are InSv. More
links will display
is ManB, ISTb, or SysB. None of step 55
the displayed links are InSv. More
links will not display
297-2651-543 Standard 05.01 March 1999

CCS LK
minor
minor
(continued)
(end)
54 Inform operating company personnel at the far-end office that an LK minor

alarm is in use. A minimum of one associated link connected to your office is in
service.
Go to step 56.
GSP05 (CSP10)
CCS LK
minor in a DPNSS
Alarm display
. . . . . 1 LK . . . .
Indication
At the MTC level of the MAP display, a number and LK appear under the
CCS header in the alarm banner. The LK indicates minor alarm for a linkset
(LK).
Meaning
The number of DPNSS links affected appears to the left of LK. These links
are system busy or in service trouble.
Result
An LK alarm indicates that the linkset cannot communicate with the private
branch exchange (PBX). To prevent an change in service, clear the LK
alarms at the first opportunity.
Common procedures
Action
procedure.
297-2651-543 Standard 05.01 March 1999

CCS LK
minor in a DPNSS (continued)
Summary of Clearing a CCS LK alarm
Access This flowchart summarizes the

DPNSS level procedure.
of MAP display
Use the instructions that follow
Check traffic procedure.
states of link(s)
Link Y Restore link

SYSB?
N
Link Y Restore link Link N Contact next
ISTB? restored? level of support
N Y
End
GSP05 (CSP10)
CCS LK
Clearing a CCS LK alarm
At your current location
1 To access the DPNSS level of the MAP display, type
>MAPCI;MTC;CCS;DPNSS
2 To post all links that have an LK minor alarm, type

>POST A
Link name Link ST Carr. action in
(carrier) state No. state state progress
PDTC 0 3 SYSB 108 INSV INSV
2 links in post set, 1 after current link
3 Record the link name. The link name appears under the header Link name on
the MAP display.
4 To display the next link, type

>NEXT
5 Repeat steps 3 and 4 until you record the names of all links that have alarms.
6 To post a link that has an LK alarm, type

>POST L link_name
where
link_name is the name of the link that you recorded in step 3
297-2651-543 Standard 05.01 March 1999

CCS LK
7 Identify the link state of the posted link.

Example of a MAP response:
PDTC 0 3 SYSB 108 INSV INSV
If the link state Do
is SysB step 8
is ISTb step 22
8 To busy the link, type

>BSY
If you Do
can set the SysB link to busy step 10

cannot set the SysB link to busy step 9
9 Use the FORCE option on the link that you cannot busy. To force the command
on the link, type
>BSY FORCE
GSP05 (CSP10)
CCS LK

>RTS
passed step 11
failed step 12
11 Determine if other LK alarms are present.
If Do
another LK alarm is present step 6

another LK alarm does is not step 39
present
12 Check the state of the signaling terminal (ST).

PDTC 0 3 SYSB 108 SYSB INSV
If the ST Do
is SysB step 13
is CBsy step 13
is InSv step 17
13 Perform the procedure Clearing an STC alarm in this document. Clear the
alarm for the signaling terminal controller (STC) and return to this point.
297-2651-543 Standard 05.01 March 1999

CCS LK

>BSY
If you Do

on the link, type
>BSY FORCE

>RTS
passed step 11
failed step 17
GSP05 (CSP10)
CCS LK
17 Check the carrier state.

PDTC 0 3 SYSB 108 InSv SysB
If the carrier state Do
is SysB step 18
is InSv step 22
18 Perform the procedure Clearing an IPML alarm in this document. Clear the
alarm for the interperipheral message link (IPML) and return to this point.

>BSY
If you Do

on the link, type
>BSY FORCE
297-2651-543 Standard 05.01 March 1999

CCS LK

>RTS
passed step 11
failed step 22
22 Check the action in progress field on the MAP display.

PDTC 0 3 SYSB 108 InSv SysB resetting all
LAPS
If the MAP response Do
is querying ST step 23
is hunting flags step 2
is resetting all LAPS step 24
is resetting <n> LAPS step 25
is all LAPS deactivated step 34
is LAP(s) deactivated step 34
is no display step 39
23 This message appears at normal intervals. If the message does not clear in
seconds, a fault is present.
Go to step 38.
24 The fault is with the other PBX.

Go to step 38.
25 This temporary state is normal while the link returns to service.
GSP05 (CSP10)
CCS LK
26 Use the QUERYLAP command to identify the LAPs that attempt to reset. Type
>QUERYLAP FULL
LAP: 00000000001111111111222222222233
01234567890123456789012345678901
Real: –................–.......rrrrrrr
Virtual: –.......rrrrrrrr–rrrrrrrrrrrrrrr
27 To reactivate the LAPs, type

>ACTLAP ALL
If the LAP Do
reactivates step 39
does not reactivate step 28
28 To access the trunk test position (TTP) level of the MAP display, type
>TRKS;TTP
POST DELQ BUSYQ DIG
TTP1
CKT TYPE PM.NO COM LANG STA S R DOT TE RESULT
2W DP DP PDTC 1 5 17 SVNV2W 60 SB + . DIG
If the trunks Do
are in lock-out (LO) state step 38

are in system-busy (SB) state step 29
29 To post the link that is system busy, type

>POST A SB
297-2651-543 Standard 05.01 March 1999

CCS LK

>BSY
If you Do

on the link, type
>BSY FORCE

>RTS
passed step 33
failed step 38
33 The LAP resets automatically.
If the LAP Do
does reset step 39

does not reset step 38
34 To reactivate the LAPs, type

>ACTLAP ALL
GSP05 (CSP10)
CCS LK
(end)

>BSY
If you Do

on the link, type
>BSY FORCE

>RTS
passed step 11
failed step 38
297-2651-543 Standard 05.01 March 1999

CCS LKM
major
Alarm display
. . . . . 1LKM . . . .
Indication
At the MTC level of the MAP display, a number precedes LKM under the
CCS header in the alarm banner. The LKM indicates a major alarm for a
Linkset (LKM).
Meaning
A linkset is out of service. No links in the linkset can carry traffic.
The number under the common channel signaling (CCS) header in the alarm
banner indicates the number of linksets affected.
Result
You cannot signal on the linkset. Traffic routes to another linkset if a linkset
is available. The traffic can be at a degraded level of service.
Common procedures
This procedure refers to Running a C7BERT.

you to go.
Action
procedure.
GSP05 (CSP10)
CCS LKM
major (continued)
Summary of How to clear CCS LKM major

alarms procedure.
Use the instructions the follow this

Perform the flowchart to perform the procedure.
LIM or LIU7 Y correct PM
alarms 1
alarm clearing
running? procedure
1 N
Check traffic
and sync states
of a link
2
Restore the
link
Are there Contact the next

N more links N
Linkset in level of support
service? with faults you
can try?
Y Y
2
Sent here from N
RSC/RSM alarm
procedure?
Y
Return to the End
RSC or RSM
alarm procedure
297-2651-543 Standard 05.01 March 1999

CCS LKM
major (continued)
Summary of Clearing a CCS LKM major alarm

alarms procedure.

Perform flowchart to perform the procedure.
LIM, LIU7, HLIU, Y appropriate PM
or HSLR alarms 1
alarm clearing
running? procedure
1 N
Check traffic
and sync states
of a link
2
Restore link
Contact next
Linkset in N Are there more N
level of support
service? faulty links you
can try?
Y Y
2
Sent here from N
RSC/RSM alarm
procedure?
Y
Return to RSC End
or RSM alarm
procedure
GSP05 (CSP10)
CCS LKM
major (continued)
How to clear a CCS LKM major
At the MAP display
1 To access the C7LKSET level of the MAP display, type
>MAPCI;MTC;CCS;CCS7;C7LKSET
If you Do
come to this procedure from the step 6

RSC or the RSM alarm clearing
procedure
do not come to this procedure from step 2
the RSC or the RSM alarm clearing
procedure
2 Check under the PM header in the MAP display alarm banner. Determine if
alarms appear for link interface modules (LIMs) or link interface units for the
CCS7 (LIU7s).
the MAP display alarm banner.

alarms Do
appear step 3
3 Perform the correct procedures in this document to clear all PM LIM or PM LIU7
alarms. Complete the procedures and return to this point.
the procedures, return to this point.
297-2651-543 Standard 05.01 March 1999

CCS LKM
major (continued)
4 To post a linkset the runs an LKM major alarm, type

>POST A LKM
Linkset SSP100_LK SysB
Traf Sync Link
1 ManB Sync LIU7 103 InSv DS0A

Linkset SSP100_LK SysB
Traf Sync Link
1 ManB algnd LIU7 103 InSv DS0A
2 ManB DAct DLIU 300 InSv DS1
If you Do
posted an out-of-service linkset step 5

did not post an out-of-service linkset step 57
5 Record the linkset name.

Note: The linkset name appears on the right of the Linkset header on the MAP
display.
6 To post the out of service link, type

>POST C linkset_name
where
linkset_name is the name of the linkset the you recorded before you started
this procedure
GSP05 (CSP10)
CCS LKM
major (continued)
Traf Sync Link

Traf Sync Link
7 Determine from office records the far-end office the connects to the posted
linkset.
8 Contact the far-end office to determine if the far-end office has LIM or LIU7
alarms.
has LIM or LIU7 alarms step 9

has LIM, LIU7, HLIU, or HSLR step 9
alarms
does not have LIM or LIU7 alarms step 10
does not have LIM, LIU7, HLIU, or step 10
HSLR alarms
9 When the problems at the far-end office clear, determine the state of the posted
linkset.
Note: The linkset state appears on the right of the linkset name on the MAP
display.
297-2651-543 Standard 05.01 March 1999

CCS LKM
major (continued)
Traf Sync Link

Traf Sync Link
is InSv or ISTb step 54

is RInh, LInh, ManB, or SysBsy step 10
is ManB or SysBsy step 10
GSP05 (CSP10)
CCS LKM
major (continued)
10 Determine if the posted linkset contains out-of-service links.

Note: The link traffic state appears under the traf stat header in the MAP
display. Up to four links show at one time in the posted linkset. If more than
four links are in the linkset, the word “more” appears at the bottom of the MAP
display.
Traf Sync Link

Traf Sync Link
If Do
out-of-service links appear and you step 12

did not work on any of these links
out-of-service or ISTb links appear step 11
and you worked on all of these links,
more links are present
out-of-service or ISTb links appear step 51
and you worked on all of these links,
more links are not present
all displayed links are InSv or step 11
ISTb, more links are present
all displayed links are InSv or ISTb step 51
more links are not present
297-2651-543 Standard 05.01 March 1999

CCS LKM
major (continued)
11 To display the next four links in the posted set, type

>NEXT
Go to step 10.
12 To choose an out-of-service link, check the traffic state for each link.
Note: The link traffic state appears under the traf stat header of the MAP
display.
a minimum of one link is InSv and step 51

you cannot restore any RInh, LInh,
ManB, or SysBsy links
a minimum of one link is InSv and step 51
you cannot restore any ManB or
SysBsy links
a minimum of one link is RInh and step 13
you did not work on the link
a minimum of one link is LInh and step 16
a minimum of one link is ManB and step 22
a minimum of one link is SysBsy step 24
and you did not work on the link
all links are RInh, LInh, ManB, or step 56
SysBsy and these links did not
return to service
all links are ManB or SysBsy and step 56
these links did not return to service
13 Office records will show the far-end office the connects to the posted linkset.
14 Contact the far-end office to determine why the operating company personnel
inhibited the link at a remote location.
GSP05 (CSP10)
CCS LKM
major (continued)
15 When the far-end office restores the link, determine the traffic state of the
inhibited link.
Note: The link traffic state appears under the traf stat header of the MAP
display.
Traf Sync Link

Traf Sync Link

is LInh step 16
is ManB step 22
is SysBsy step 24
system inhibited the link local.
17 When you have permission, uninhibit (UINH) the link. Type

>UINH link_no
where
297-2651-543 Standard 05.01 March 1999

CCS LKM
major (continued)
passed step 18
failed and this attempt is your first step 19
attempt to uninhibit the link
failed and this attempt is your step 10
second attempt to uninhibit the link
18 Determine the link traffic state.

display.
Traf Sync Link

Traf Sync Link

GSP05 (CSP10)
CCS LKM
major (continued)
19 Contact your next level of support to determine if entries for the link change at
either end of the link.
If entries Do
changed at either end of the link step 20

did not change at either end of the step 21
link
20 Consult your next level of support. Follow the instructions of your next level of
support to correct the problem.
21 Consult your next level of support to determine why the UINH command failed.
link is manual busy.

>RTS link_no
where
failed step 10
RInh
LInh
SysBsy
passed, and the link traffic state is step 51
InSv or ISTb
297-2651-543 Standard 05.01 March 1999

CCS LKM
major (continued)
24 Determine the link synchronization state.

Note: The link synchronization state appears under the Sync Stat header of
the MAP display.
Traf Sync Link

Traf Sync Link

is other than listed above step 25
is other than listed above step 26

>INH link_no
where
GSP05 (CSP10)
CCS LKM
major (continued)
passed step 26
SysBsy
ISTb

>BSY link_no
where
If the response Do

running on the link
Please confirm
(“YES”,“Y”,“NO”, or “N”):
is other than listed here, including step 56
additional messages with preceding
response

>YES

>DEACT link_no
where
297-2651-543 Standard 05.01 March 1999

CCS LKM
major (continued)
29 To activate the link, type

>ACT link_no
where

>RTS link_no
where

failed, and the link synchronization step 32
failed step 32

>UINH link_no
where

failed step 32
GSP05 (CSP10)
CCS LKM
major (continued)
32 Wait 8 min to see if the link activates.

is other than listed here and you did step 33
not ask the far-end office to activate
the link
is other than listed here and you step 10
asked the far-end office to activate
the link
33 Contact the far-end office. Inform operating company personnel at that location
of the following information:
• You will busy, deactivate, return to service, and activate the link in order to
align the link again.
• Both ends must activate the link after you busy, deactivate, and return the
link to service.
Coordinate your activities with the far-end office to align the link again.

>INH link_no
where
passed step 35
SysBsy
ISTb
297-2651-543 Standard 05.01 March 1999

CCS LKM
major (continued)

>BSY link_no
where
If the response Do

running on the link
Please confirm
(“YES”,“Y”,“NO”, or “N”):
additional messages with above
response

>YES

>DEACT link_no
where
GSP05 (CSP10)
CCS LKM
major (continued)
38 Inform operating company personnel at the far-end office to activate the link in
use. Activate the link at your end at the same time the far-end office activates
the link at their end.
>ACT link_no
where

failed step 10

>RTS link_no
where
297-2651-543 Standard 05.01 March 1999

CCS LKM
major (continued)

>UINH link_no
where

failed step 10
41 Determine the traffic state of the link.

display.
Traf Sync Link
GSP05 (CSP10)
CCS LKM
major (continued)
Traf Sync Link
is InSv step 51

>INH link_no
where
passed step 43
SysBsy
ISTb
297-2651-543 Standard 05.01 March 1999

CCS LKM
major (continued)

>BSY link_no
where
If the response Do

running on the link
Please confirm
(“YES”,“Y”,“NO”, or “N”):
additional messages with preceding
response

>YES
45 To test the link, type

>TST link_no
where
passed step 47
failed and you did not run a bit error step 46
rate test on the link
failed step 10
failed and you ran a bit error rate step 10
test on the link
GSP05 (CSP10)
CCS LKM
major (continued)
46 Perform the procedure Running a C7BERT in this document. Complete the

Note: Perform a bit error rate test on any link in the posted linkset. Test any
link the fails the manual test at step 45.
Go to step 49.

>RTS link_no
where
passed, and the link is LInh step 50

passed step 51
failed. This attempt is your first step 48
attempt with the RTS command
failed. This attempt is your second step 10
attempt with the RTS command
48 Wait 10 min.
Go to step 47.
49 Your next action depends on the results of the bit error rate test.
If, during the bit error rate test,

you received the instruction Do
to return the link to service step 50

to not return the link to service step 10
297-2651-543 Standard 05.01 March 1999

CCS LKM
major (continued)

>UINH link_no
where
passed, and the link is InSv or step 51

ISTb
passed, and the link is ManB or step 10
SysBsy
failed step 10
51 Determine the linkset state.

Note: The linkset state appears on the right of the linkset name on the MAP
display.
Traf Sync Link
GSP05 (CSP10)
CCS LKM
major (continued)
Traf Sync Link
If the linkset state Do

is ManB or SysBsy and a minimum step 52
of one InSv or ISTb link is present
is ManB or SysB and displayed step 10
links are not InSv or ISTb, more
links are present
is ManB or SysBsy and displayed step 56
links are not InSv or ISTb, more
links are not present
52 Office records will show the far-end office the connects to the posted linkset.
53 Contact the far-end office. Inform operating company personnel the the linkset
is not in service. Inform operating company personnel the a minimum of one
associated link the connects to your office is in service.
54 Your next action depends on the reason you perform this procedure.
If you Do
came to this procedure from the step 55

RSC or the RSM alarm clearing
procedure
did not come to this procedure from step 57
the RSC alarm clearing procedure
55 Return to the clearing procedure for the routeset alarm the sent you to this
procedure. Continue as directed.
297-2651-543 Standard 05.01 March 1999

CCS LKM
majormajor
(continued)
(end)
GSP05 (CSP10)
CCS LSSC
critical
Alarm display
. . . . . 1LSSC . . . .
*C*
Indication
At the MTC level of the MAP display, a number and FSP appear under the
CCS header in the alarm banner. The LSSC indicates a critical alarm for a
local subsystem (LSSC).
Meaning
A local subsystem is system busy or manual busy.
If all occurrences in an affected subsystem are system busy, the associated

service can have had a coordinated state change. The system routes all
queries to the mate service control point II (SCPII). At this time, you must
correct the problem at the SCPLoc level. Subsystem occurrences are not
always in a fault condition.
The number under the CCS header in the alarm banner indicates the number
of subsystems affected.
Result
The affected local subsystem is out of service.
Common procedures
Action
procedure.
297-2651-543 Standard 05.01 March 1999

CCS LSSC
critical (continued)
Summary of How to clear a CCS LSSC critical alarm
Choose a local This flowchart summarizes the

subsystem with procedure.
an LSSC alarm
RTS offline and flowchart to perform the procedure.
out-of-service
instances
Subsystem in Y
service?
N
Contact next End
level of support
GSP05 (CSP10)
CCS LSSC
Summary of How to clear a CCS LSSC critical alarm
Display local This flowchart summarizes the

subsystems with procedure.
LSSC alarms
Is there an Y Clear an flowchart to perform the procedure.
SCPLC critical SCPLC critical
alarm? alarm
N
Are there Y Choose a
manual-busy manual-busy
subsystems? subsystem
N
Choose a Manually busy
system-busy offline
subsystem occurrences
Return all
Subsystem in Y
manual-busy
occurrences to service?
service
N
Return all sys–
tem-busy occur–
rences to service
Y
Subsystem in
service?
N
Contact next End
level of support
297-2651-543 Standard 05.01 March 1999

CCS LSSC
How to clear a CCS LSSC critical alarm
At the MAP terminal
1 To access the CCS7 level of the MAP, type
>MAPCI;MTC;CCS;CCS7
2 To display all subsystems that cause LSSC alarms, type

>DISALM LSSC
Example of a MAP response
Subsystem Alm Stat
800P SSC SYSB
ACCS SSC MANB
3 Choose a subsystem to work on. Choose the out-of-service local subsystem

with the highest value. The MANB has a higher value than SYSB.
4 Record the name and state of the subsystem.

Note: The subsystem name appears under the subsystem header on the MAP
display. The subsystem state appears under the state header.
5 To access the SCCPLOC level of the MAP display, type

>SCCPLOC
6 To post the local subsystem, type

>POST subsystem
where
subsystem is the name of the local subsystem that you selected in step 3
CCS7 SCP
1 LSSC .
C7 SCCP LOCAL 111111 11112222 22222233
Subsystem State 01234567 89012345 67890123 45678901
800P MANB SMMO---- -------- -------- --------
GSP05 (CSP10)
CCS LSSC
7 Determine the state of all occurrences for the post subsystem.
If Do
all occurrences are S (system busy) step 8

a minimum of one occurrence is O step 10
(offline), M (manual busy), or dot (.)
(in service)
8 Determine if the MAP display indicates a SCPLC critical alarm under the SCP
header.
CCS7 SCP
1 LSSC 1 SCPLC
C7 SCCP LOCAL 111111 11112222 22222233
Subsystem State 01234567 89012345 67890123 45678901
800P SYSB SSSS---- -------- -------- --------
If an SCPLC alarm Do
appears step 9
does not appear step 10
9 The SCPII node changed to a coordinated state. Perform the procedure How
to clear an SCPLC critical alarm. Return to this point.
Go to step 25.
297-2651-543 Standard 05.01 March 1999

CCS LSSC
10 Choose a local subsystem occurrence to use.
If Do
at least one subsystem occurrence step 11

is M, and you have not tried to return
the subsystem to service
is O, and you have not tried to return
the subsystem to service
is S, and you have not collected
information on the occurrence that
uses the LOCATE command
you tried to return all M, O, and S step 24
occurrences to service, and you
cannot return the subsystem to
service
11 Determine from office records or from operating company personnel if you have
permission to return the manual busy occurrence to service.
If you Do
have permission to return the step 14

occurrence to service
do not have permission to return the step 10
12 Determine from office records or from operating company personnel if you have
permission to return the offline occurrence to service.
If you Do
have permission to return the step 13

GSP05 (CSP10)
CCS LSSC
13 To manually busy the occurrence, type

>BSY instance_no
where
instance_no is the number of the occurrence (0 to 31)
14 To return the occurrence to service, type

>RTS instance_no
where
occurrence_no is the number of the occurrence (0 to 31)
passed, and the occurrence is step 15

dot (.) (in service)
passed, but the occurrence is S step 10
failed step 22
15 Determine the subsystem state.

Note: The subsystem state appears under the state header on the MAP.
Example of a MAP:
CCS7 SCP
1 LSSC .
C7 SCCP LOCAL 111111 11112222 22222233
Subsystem State 01234567 89012345 67890123 45678901
800P MANB SMMO---- -------- -------- --------
If the local subsystem state Do
is InSv step 25
is not InSv and at least one step 10
occurrence is O, M, or S
is not InSv and no occurrences are step 24
O, M, or S
297-2651-543 Standard 05.01 March 1999

CCS LSSC
16 To manually busy the system busy occurrence, type

>BSY instance_no
where
If the BSY command Do
passed step 18
failed step 17
17 To force the occurrence to busy, type

>BSY instance_no FORCE
where
>RTS instance_no
where
RTS Passed
The EIU peripheral is not in service
passed. The occurrence is step 23

dot (.) (in service)
passed. The occurrence remains S step 19
failed step 22
GSP05 (CSP10)
CCS LSSC
19 The subsystem waits for an indication from the application. Wait 1 min for the
occurrence to return to service.
If the subsystem occurrence Do
is dot (.) (in service) step 23

is other than dot (.) (in service) step 20
20 To learn more about the occurrence, type

>LOCATE instance_no
where
800P 1 is located on EIU 210 which is currently ManB.
The TCP connection to port 30808 at 47.12.0.2. is closed
21 Record why the occurrence returns to system busy.
22 Record the number of occurrences to report the number to your next level of
support. Do not try to correct the occurrence now. Continue to work on other
occurrences that you did not try.
Go to step 10.
297-2651-543 Standard 05.01 March 1999

CCS LSSC
critical
critical
(continued)
(end)

Note: The subsystem state appears under the state header on the MAP.
Example of a MAP:
CCS7 SCP
1 LSSC .
C7 SCCP LOCAL 111111 11112222 22222233
Subsystem State 01234567 89012345 67890123 45678901
800P MANB .MMO---- -------- -------- --------

is not InSv or ISTb and at least step 10
one occurrence is O, M, or S
is not InSv or ISTb and no step 24
occurrences are O, M, or S
GSP05 (CSP10)
CCS LSSM
Alarm display
. . . . . 1LSSM . . . .
M
Indication
At the MTC level of the MAP display, a number and LSSM appear under
the CCS header in the alarm banner. The LSSM indicates a major alarm for
a local subsystem (LSSM). The number indicates the number of
occurrences of affected local subsystems.
At the CCS;CCS7;SCCPLOC level of the MAP display, IsTb appears under

the subsystem state header. The I appears under the number for a local
subsystem occurrence.
Meaning
The Freephone subsystem is the only system that uses the common channel
signaling (CCS) LSSM alarm.
Freephone subsystems associated with the LSSM alarm are as follows:

• E800 - toll-free number service for the United States
• 800P - toll-free number service for Canada
• E008 - toll-free number service for for Australia
Communication problems with the database for the service control point
(SCP) occur on the Freephone subsystem. A minimum of two time-outs
occurred during queries by the Freephone subsystem to the SCP database.
Interruptions to queries to the SCP database require additional analysis. The
Freephone subsystem continues to process toll-free calls.
Result
The CCS LSSM alarm monitors all occurrences of a subsystem. Occurrence
0 is the only occurrence for the Freephone subsystem. Occurrence 0
in-service trouble does not affect service. The alarm warns that problems
can be present that require analysis.
297-2651-543 Standard 05.01 March 1999

CCS LSSM
(continued)
The following logs generate when the state of the local subsystem changes
to in-service troubles:
• The CCS231 indicates that communication problems with the SCP
database occur on the local subsystem
• The CCS250 indicates the local subsystem state changed to in-service
troubles
LINE138 log generates when a query time-out for a service control point
(SCP) database occurs .
When a call times out, the system pegs Register NSCSFLTO in the number
service code (NSC) in the operational measurements (OM) group.
Common procedures
Action
procedure.
GSP05 (CSP10)
CCS LSSM
(continued)
Summary of How to clear a CCS LSSM major alarm
This flowchart summarizes the

procedure.
2
Choose an
occurrence to
procedure.
work on
Is Y Wait for alarm

occurrence to clear 1
IsTb?
N
Is Y Return
occurrence occurrence to 1
ManB? service
N 1
Is Y Busy and return Y End

occurrence occurrence to Alarm
Offl? service cleared?
N
2
Contact next
level of support
297-2651-543 Standard 05.01 March 1999

CCS LSSM
(continued)
How to clear a CCS LSSM alarm

At the MAP terminal
1 To access the CCS7 level of the MAP display, type
>MAPCI;MTC;CCS;CCS7
2 To list the local subsystems with LSSM alarms, type

>DISALM LSSM
Subsystem Alm Stat
800P SSM ISTB
3 Record the names of the local subsystems that have in-service troubles.
Note: The subsystem name appears under, on the right of the subsystem
header on the MAP display. The state appears under the Stat header.
4 To access the SCCPLOC level of the MAP display, type

>SCCPLOC
5 To post the local subsystem, type

>POST subsystem
where
subsystem is the name of the local subsystem that you recorded in step 3
CCS7 SCP
1 LSSM .
C7 SCCP LOCAL 111111 11112222 22222233
Subsystem State 01234567 89012345 67890123 45678901
800P ISTB I------- -------- -------- --------
GSP05 (CSP10)
CCS LSSM
(continued)
6 Choose a local subsystem occurrence to work on.
If Do
a minimum of one subsystem step 9

occurrence is M (manual busy) and
you did not try to return the
subsystem to service
occurrence is O (offline) and you
did not try to return the subsystem
to service
occurrence is S (system busy) and
you did not collect information on
the occurrence through the
LOCATE command
you tried to return all O, M, and S step 22
occurrences to service and you
cannot return the local subsystem to
service
occurrences is I (in-service trouble)
and no O, M, or S occurrences are
present
7 Wait for the alarm to clear.

Note: The alarm will automatically clear when you enter option ALARMTIM in
table NSCDEFS. The alarm also clears when entry time (1 to 1441 min, default
10 min) passes without additional SCP query time-outs. If the alarm clears, the
state of the freephone subsystem changes from in-service trouble to in service.
The system generates a CCS220 log to indicate that the subsystem occurrence
is in service. The system generates a CCS235 log to indicate that the state of
the freephone subsystem changed to in service.
If the alarm Do
clears step 23
does not clear step 8
Note: Use the disable procedure to clear the alarm. To disable the alarm,
297-2651-543 Standard 05.01 March 1999

CCS LSSM
(continued)
enter option NSCALARM in table NSCDEFS as OFF. The alarm clears within
30 s of the entry change. When the alarm clears, the state of the E800
subsystem changes from in-service trouble to in service. The system
generates CCS220 and CCS235 logs to document the alarm clearance and the
state change.
8 Ask the next level of support to help you determine the cause of the alarm.
CAUTION
Loss of service
The alarm will not clear if you wait for the system to
clear or disable the alarm. If the alarm occurs often,
investigate the cause of the alarm.
CAUTION
Loss of service
Do not busy or return the freephone subsystem to
service to clear the alarm. Do not perform a
subsystem restart to clear the alarm. A busy or restart
of the subsystem will terminate all toll free traffic on
the switch.
CAUTION
Loss of service
The alarm will not clear if you wait for the system to
clear or disable the alarm. If the alarm occurs often,
investigate the cause of the alarm.
CAUTION
Loss of service
Do not busy or return the freephone subsystem to
service to clear the alarm. Do not perform a
subsystem restart to clear the alarm. A busy or
restart of the subsystem will terminate all toll free
traffic on the switch.
GSP05 (CSP10)
CCS LSSM
(continued)
9 Determine from office records or operating company personnel if you can return
the manual busy occurrence to service.
If you Do
can return the occurrence to service step 12

cannot return the occurrence to step 6
service
10 Determine from office records or operating company personnel if you can return
the offline occurrence to service.
If you Do
can return the occurrence to service step 11

cannot return the occurrence to step 6
service
11 To manually busy the offline occurrence, type

>BSY occurrence_no
where

>RTS occurrence_no
where
passed. The occurrence is step 13

dot (.) (in-service)
failed. The occurrence is S step 6
failed step 20
297-2651-543 Standard 05.01 March 1999

CCS LSSM
(continued)

Note: The subsystem state appears under the State header on the MAP
display.
CCS7 SCP
1 LSSM .
C7 SCCP LOCAL 111111 11112222 22222233
Subsystem State 01234567 89012345 67890123 45678901
800P ISTB M------- -------- -------- --------
is InSv step 23
is not InSv and one or more O, M, step 6
and S occurrences are present
is not InSv and no O, M, or S step 22
occurrences are present
14 To manually busy the system-busy occurrence, type

>BSY occurrence_no
where
passed step 16
failed step 15
15 To force the occurrence to busy, type

>BSY occurrence_no FORCE
where
GSP05 (CSP10)
CCS LSSM
(continued)

>RTS occurrence_no
where
occurrence _no is the number of the occurrence (0 to 31)
RTS Passed
The EIU peripheral is not in service
passed and the occurrence is dot step 21

(.) (in service)
failed and the occurrence is S step 17
failed step 20
17 The subsystem waits for an indication from the application. Wait 1 min for the
occurrence to return to service.
If the subsystem occurrence Do
is dot (.) (in service) step 21

18 To learn more about the occurrence, type

>LOCATE occurrence_no
where
800P 1 is located on EIU 210 which is currently ManB.
The TCP connection to port 30808 at 47.12.0.2. is closed
19 Record why the occurrence returns to system busy.
297-2651-543 Standard 05.01 March 1999

CCS LSSM
(continued)
(end)
20 Record the number of this occurrence to report this occurrence to your next
level of support. Do not restore the occurrence at this time. Work on
occurrences that you did not try.
Go to step 6.

Note: The subsystem state appears under the State header on the MAP
display.
CCS7 SCP
1 LSSM .
C7 SCCP LOCAL 111111 11112222 22222233
Subsystem State 01234567 89012345 67890123 45678901
800P ISTB .------- -------- -------- --------
is InSv step 23
is not InSv and one or more O, M, step 6
or S occurrences is present
is not InSv. and O, M, or S step 22
occurrences are not present
GSP05 (CSP10)
CCS PC
minor
Alarm display
. . . . . 1PC . . . .
Indication
At the MTC level of the MAP display, a number and PC appear under the
CCS header in the alarm banner. The PC indicates an alarm for a point code
(PC).
Meaning
Traffic congestion occurs on the routes between your office and the office
represented by the point code.
banner indicates the number of route and far-end office groups affected.
Result
Traffic congestion can affect service. If the congestion level is too high, the
system can discard messages to the signaling point identified by the point
code.
Common procedures
Action
procedure.
297-2651-543 Standard 05.01 March 1999

CCS PC
minor (continued)
Summary of Clearing a CCS PC minor alarm
Identify and This flowchart summarizes the

record point procedure.
code names
Y Clear RSM
RSM alarm alarm
active?
N
Contact next End
level of support
GSP05 (CSP10)
CCS PC
minor (continued)
Clearing a CCS PC minor alarm
At the MAP terminal
>MAPCI;MTC;CCS;CCS7
2 To display the name of the PC that causes the PC alarm, type

>DISALM PC
Point code Alm Stat
IPTRS4 PC ISTb
3 Record the name of the PC.

Note: The PC name appears under the PC header on the MAP display.
4 To access the C7RTESET level of the MAP display, type

>C7RTESET
5 To post a routeset that runs an RS major alarm, type

>POST A RSM
C7Routeset SSP100_RT ISTb Linkset Transfer
Rte State Mode Cost Linkset State Status
0 SysB Assoc 0 SSP100_LK SysB TFP
1 InSv Quasi 1 SSP101_LK InSv TFA
If you Do
posted a routeset step 6

did not post a routeset step 8
6 Perform the procedure Clearing a CCS RS major alarm in this document.

Complete the procedure and return to this point.
297-2651-543 Standard 05.01 March 1999

CCS PC
minor
minor
(continued)
(end)
7 Determine if the PC minor alarm cleared.
If the PC alarm Do
cleared step 9
GSP05 (CSP10)
CCS PCC
critical
Alarm display
. . . . . 1PCC . . . .
*C*
Indication
At the MTC level of the MAP display, a number and PCC appear under the
CCS header in the alarm banner. The PCC indicates a critical alarm for a
point code (PCC).
Meaning
A routeset (RS) is out of service as a result of a manual busy or system busy
point code.
banner indicates the number of far-end offices affected.
Result
The signaling point that the point code identifies cannot receive signaling.
Common procedures
Action
procedure.
297-2651-543 Standard 05.01 March 1999

CCS PCC
Summary of Clearing a CCS PCC critical alarm
Display point This flowchart summarizes the

codes with PCC procedure.
alarms
Is the point Y Clear the RSC flowchart to perform the procedure.
code system alarm
busy?
N
Post the point
code
Return the point

code to service
RTS Y
command
passed?
N
Contact next End
level of support
GSP05 (CSP10)
CCS PCC
Clearing a CCS PCC critical alarm
At the MAP terminal
>MAPCI;MTC;CCS;CCS7
2 To display the name of the point code that causes the PCC alarm, type
>DISALM PCC
Point code Alm Stat
IPTRS4 PCC ManB
3 Record the point code name and state.

Note: The point code name appears under the point code header on the MAP
display. The point code state appears under the state header.
If the state of the point code Do
is SysB step 4
is ManB step 8

>C7RTESET
297-2651-543 Standard 05.01 March 1999

CCS PCC
5 To post an RS with an RS critical alarm, type

>POST A RSC
C7Routeset ESTP_C200_RTESET SysB Linkset Transfer
0 SysB Assoc 0 ESTP_C200_Lkset SysB
If you Do
posted an RS step 6
did not post an RS step 12
6 Perform the procedure Clearing a CCS RS critical alarm in this document.

Clear the CCS RSC alarm and return to this point.
7 Determine if the PCC critical alarm cleared.
If the PCC alarm Do
cleared step 13
8 Determine from office records or operating company personnel why a person

manually busied the point code. Determine if you can return the point code to
service.
When you have permission to return the point code to service, continue the
procedure.
9 To access the SCCPRPC level of the MAP display, type

>SCCPRPC
GSP05 (CSP10)
CCS PCC
(end)
10 To post the point code that has the PCC alarm you want to clear, type
>POST point_code
where
point_code is the name of the point code recorded in step 3
11 To return the point code to service, type

>RTS
passed step 13
failed step 12
297-2651-543 Standard 05.01 March 1999

CCS RS
critical
Alarm display
. . . . . 1RS . . . .
*C*
Indication
At the MTC level of the MAP display, a number and RS appear under the
CCS header in the alarm banner. The RS indicates a critical alarm for a
routeset (RS).
Meaning
A routeset is manual busy or system busy for one of the following reasons:
• faults in the peripheral modules that associate with the linksets in the
routeset
• faults on the links that associate with your office
• problems on the network
banner indicates the number of RSs affected.
Result
You cannot signal on the RS.
Common procedures
Action
procedure.
GSP05 (CSP10)
CCS RS
Summary of Clearing a CCS RS critical alarm

alarms procedure.

Perform correct flowchart to perform the procedure.
Are the LIM or Y
PM LIM or LIU7
LIU7 alarms
alarm clearing
running?
procedure
N
Post a routeset
with a critical
alarm
Are the N Network

Linksets out of problems: local
service? maintenance not
correct
Y
Clear a CCS
LKM major
alarm
Y
Is the routeset
in service?
N
Contact next End
level of support
or far-end office
297-2651-543 Standard 05.01 March 1999

CCS RS
Summary of Clearing a CCS RS critical alarm

alarms procedure.

Clear an flowchart to perform the procedure.
LIM, LIU7, HLIU, Y
appropriate PM
or HSLR alarms
LIM, LIU7, HLIU,
running?
or HSLR alarm
N
Post a routeset
with a critical
alarm
N Network problems:
Linksets out of local maintenance
service? not appropriate
Y
Clear a CCS
LKM major
alarm
Y
Routeset in
service?
N
Contact next level End
of support or the
far-end office
GSP05 (CSP10)
CCS RS
Clearing a CCS RS critical alarm
At the MAP terminal
>MAPCI;MTC;CCS;CCS7
2 Check under the PM header in the MAP alarm banner. Determine if alarms
appear for the link interface module (LIM) or link interface unit for the CCS7
(LIU7).

alarms Do
appear step 3
3 Perform the alarm clearing procedures in this document to clear all PM LIM or
PM LIU7 alarms. Complete the procedures and return to this point.
PM LIM, PM LIU7, HLIU, or PM HSLR alarms. When you have completed the
procedures, return to this point.

>C7RTESET
5 To post an RS that runs an RS critical alarm, type

>POST A RSC
297-2651-543 Standard 05.01 March 1999

CCS RS
C7Routeset SSP100_RT SysB Linkset Transfer
0 SysB Assoc 0 SSP100_LK SysB TFA
1 SysB Quasi 1 SSP101_LK ISTb TFA
If you Do
posted a manual busy or system step 6

busy RS
did not post a manual busy or step 20
system busy RS
6 Record the RS name and state.

Note: The RS name appears on the right of the C7Routeset header on the
MAP display. The RS state appears on the right of the RS name.
If the state of the RS Do
is ManB step 7
is SysB step 9
7 Determine the state of the linksets in the posted RS.

Note: The linkset state appears under the linkset state header on the MAP
display.
C7Routeset SSP100_RT ManB Linkset Transfer
0 SysB Assoc 0 SSP100_LK ManB TFP
1 SysB Quasi 1 SSP101_LK SysB TFP
If all linksets Do
are InSv step 8

are RInh, LInh, ManB, or SysB step 11
are ManB or SysB step 11
GSP05 (CSP10)
CCS RS
RS is manually busy .
If you Do
manually busied the RS from your step 15

office
did not manually busy the RS from step 17
your office
9 To force the RS to busy, type

>BSY FORCE

Note: The linkset state appears under the linkset state header on the MAP
display.
Example of a MAP display
1 SysB Quasi 1 SSP101_LK ISTb TFR
If Do
all linksets are InSv step 17

at least one linkset is InSv or ISTb step 17
and at least one linkset is out of
service
all linksets are ManB or SysB step 11
11 Record the name and state for each linkset for the posted RS.
Note: The linkset name appears under the linkset header on the MAP display.
The linkset state appears under the linkset state header.
12 Perform the procedure Clearing a CCS LKM major alarm in this document.
297-2651-543 Standard 05.01 March 1999

CCS RS

>C7RTESET
14 To post the RS, type

>POST C rteset_name
where
rteset_name is the RS name you recorded in step 6
Example input:
>POST C SSP100_RT
0 InSv Assoc 0 SSP100_LK InSv TFA
15 When you have permission to return the RS to service, type

>RTS
passed and the RS is InSv or ISTb step 20

failed step 16
passed and the RS is SysB step 17
16 Determine the RS state.
GSP05 (CSP10)
CCS RS
(end)
Note: The RS state appears under the state header of the MAP.
If the state of the RS Do

is ManB or SysB, and at least one step 17
linkset is InSv or ISTb
is ManB or SysB, and no linksets step 19
are InSv or ISTb
17 Determine from office records which far-end office connects to the posted RS.
18 Contact the far-end office. Tell the operating company personnel that the
critical alarm for an RS is in use. One or more associated linksets that connect
to the office are in service.
Go to step 20.
297-2651-543 Standard 05.01 March 1999

2-99 Ext alarm clearing procedures 2-99
Ext MALO
Major
Alarm display
. . . . . . . 1Maj. .
Indication
Under the Ext subsystem header at the Ext level of the MAP display, 1 Maj.
may indicate one or more malicious call originating (MALO) major alarms.
Meaning
A MALO alarm is raised in the originating office. The alarm is generated
each time a call attempts to terminate to a subscriber with the MALO service
active.
When the MALO alarm is generated, the operating company can check call
information from a log. The operating company can decide on the correct
action, based on this information
Impact
Failure to trace malicious calls.
Common procedures
Not applicable
Action
The following flowchart is only a summary of the procedure. Use the
instructions in the step-action procedure that follows the flowchart to clear
the alarm.
GSP05 (CSP10)
2-100 Ext alarm clearing procedures
Ext MALO
Major (continued)
Summary of clearing an Ext MALO alarm

procedure.

procedure that follows this
Access Ext flowchart to perform the
level at the procedure.
MAP
List major
alarms
Check
MALO100
or101 log
Note calling
party
information
Clear alarm
Alarm Y End of
cleared? procedure
Contact next
level of support
297-2651-543 Standard 05.01 March 1999

Ext alarm clearing procedures 2-101
Ext MALO
Major (continued)
Clearing an Ext MALO alarm
1 To access the Ext level of the MAP display, type
>EXT
Example of a MAP display.
. . 2MPCOS . 1LIM . . 54GC 1 Maj .
Ext Alarms Crit FSP Major Minor NoAlm

0 0 1 1 12
2 To display all the Ext major alarms, type

>LIST MAJ
If response on MAP display is Do
MALOALARM step 4
anything else step 3
3 Perform the appropriate alarm-clearing procedures in this document. When

you have completed the procedure, go to step 12.
4 To access LOGUTIL, type

>LOGUTIL
5 To open the MALO log report buffer, type

>OPEN MALO
GSP05 (CSP10)
Ext MALO
Major (continued)
(end)
6 To browse through the buffer to display the MALO100 or 101 log reports, type
>BACK ALL
If the log is Do
MALO100 step 7
MALO101 step 7
7 Note the date and time, the calling party LEN, the forwarding party LEN, and
the called party DN.
Go to step 9.
8 Note the date and time, the incoming trunk ID, the forwarding party LEN, and
the called party DN.
9 To exit LOGUTIL, type

>QUIT
10 To clear the alarm, type

>SETSC MALO_ALARM REL
0 0 0 0 10
setsc esr_time_alarm rel

OK
If the alarm Do
clears step 12
fails step11
11 Contact the next level of support.
12 You have completed this procedure.
297-2651-543 Standard 05.01 March 1999

Ext MALT
Major
Alarm display
. . . . . . . 1Maj. .
Indication
Under the Ext subsystem header at the Ext level of the MAP display, 1 Maj.
may indicate one or more malicious call terminating (MALT) major alarms.
Meaning
A MALT alarm is raised in the originating office. The alarm is generated
each time a call attempts to terminate to a subscriber with the MALT service
active.
When the MALT alarm is generated, the operating company can check call
information from a log. The operating company can decide on the correct
action, based on this information
Impact
Failure to trace malicious calls.
Common procedures
Not applicable
Action
the alarm.
GSP05 (CSP10)
Ext MALT
Major (continued)
Summary of clearing an Ext MALT alarm

procedure.

Access Ext flowchart to perform the
level at the procedure.
MAP
List major
alarms
Check
MALT100
or101 log
Note calling
party
information
Clear alarm
Alarm Y End of
cleared? procedure
Contact next
level of support
297-2651-543 Standard 05.01 March 1999

Ext MALT
Major (continued)
Clearing an Ext MALT alarm
>EXT
. . 2MPCOS . 1LIM . . 54GC 1 Maj .

0 0 1 1 12
2 To display all the Ext major alarms, type

>LIST MAJ
MALTALARM step 4
3 Perform the appropriate alarm-clearing procedures in this document. When

you have completed the procedure, go to step 11.

>LOGUTIL
5 To open the MALT log report buffer, type

>OPEN MALT
GSP05 (CSP10)
Ext MALT
Major (continued)
(end)
6 To browse through the buffer to display the MALT100 or 101 log reports, type
>BACK ALL
If the log is Do
MALT100 step 7
MALT101 step 8
7 Note the date and time, the called party DN, the called party LEN, and the
calling party DN.
Go to step 9.
8 Note the date and time, the called party DN, the called party LEN, and the
incoming trunk ID.

>QUIT

>SETSC MALT_ALARM REL
0 0 0 0 10
setsc esr_time_alarm rel

OK
If the alarm Do
clears step 12
fails step11
297-2651-543 Standard 05.01 March 1999

CCS RS
major
Alarm display
. . . . . 1RS . . . .
M
Indication
At the MTC level of the MAP display, a number and RS appear under the
CCS header in the alarm banner. The RS indicates a major alarm for a
routeset (RS).
Meaning
A routeset has in-service trouble for the following reasons:
• faults in the peripheral modules associated with the linksets in the
routeset
• faults on the links associated with your office
• problems on the network
• problems within a network cluster
banner indicates the number of routesets affected.
Result
The routeset can carry traffic with the risk of a degraded level of service.
Common procedures
Action
procedure.
GSP05 (CSP10)
CCS RS
major (continued)
Summary of Clearing a CCS RS major alarm

alarms procedure.

Are LIM or Y Perform appropriate
LIU7 alarms PM LIM or LIU7
1
running? alarm clearing
procedure
1 N
Post a routeset
with a major
alarm
Are linksets N Network

out of problems: local
service? maintenance is
not appropriate
Y
Clear a CCS
LKM major
alarm
Is routeset in Y
service?
N
Contact next End
level of support,
or far-end office
297-2651-543 Standard 05.01 March 1999

CCS RS
major (continued)
Summary of Clearing a CCS RS major alarm

alarms procedure.

LIM, LIU7, Y Clear an flowchart to perform the procedure.
HLIU, or HSLR appropriate PM 1
alarms running? LIM, LIU7, HLIU,
or HSLR alarm
1 N
Post a routeset
with a major
alarm
N Network problems:
Linksets out of local maintenance
service? not appropriate
Y
Clear a CCS
LKM major
alarm
Routeset in Y
service?
N
Contact next level End
of support or the
far-end office
GSP05 (CSP10)
CCS RS
major (continued)
Clearing a CCS RS major alarm
At the MAP display
>MAPCI;MTC;CCS;CCS7
2 Check under the PM header in the alarm banner for the MAP display.
Determine if alarms appear for the link interface module (LIM) or link interface
unit for the CCS7 (LIU7).

alarms Do
appear step 3
3 Perform the correct alarm clearing procedures in this document to clear all PM
LIM or PM LIU7 alarms. Complete the procedure and return to this point.
the procedure, return to this point.

>C7RTESET
5 To post an RS that runs an RS major alarm, type

>POST A RSM
297-2651-543 Standard 05.01 March 1999

CCS RS
major (continued)
C7Routeset SSP100_RT ISTb Linkset Transfer
If you Do
posted an in-service trouble RS step 6

did not post an in-service trouble RS step 15
If Do
all linksets are InSv step 12

a minimum of one RInh, LInh, step 7
ManB, or SysBsy linkset is present
a minimum of one ManB or SysBsy step 7
linkset is present
7 Record the name of the RS. Record the linkset name and state for each linkset
in the posted RS.
Note: The RS name appears on the right of the C7Routeset header on the
MAP display. The linkset name appears under the Linkset header. The linkset
state appears under the Linkset State header.
8 Perform the procedure Clearing a CCS LKM major alarm in this document.

>C7RTESET
10 To post the RS, type

>POST C rteset_name
where
rteset_name is the RS name that you recorded in step 7
GSP05 (CSP10)
CCS RS
major (continued)
(end)

C7Routeset SSP100_RT InSv Linkset Transfer
0 InSv Assoc 0 SSP100_LK InSv TFA
11 Determine the RS state.

Note: The RS state appears on the right of the RS name on the MAP display.
If the state of the routeset Do
is InSv step 15
is ISTb and a minimum of one step 8
RInh, LInh, ManB, or SysBsy
linkset is present.
is ISTb and a minimum of one step 8
ManB or SysBsy linkset is present
is ManB or SysBsy and InSv or step 12
ISTb linksets are not present
is ManB or SysBsy and a minimum step 14
of one InSv or ISTb linkset is
present
12 Office records will show the far-end office that connects to the posted RS.
13 Contact the far-end office. Inform operating company personnel that an RS

major alarm is active. All linksets connected to your office are in service.
Go to step 15.
14 The alarm associated with the posted RS upgrades from an RS major alarm to
an RS critical alarm. Perform the procedure How to clear an RS critical alarm
in this document.
297-2651-543 Standard 05.01 March 1999

CCS RSSC
critical
Alarm display
. . . . . 1RSSC . . . .
*C*
Indication
At the MTC level of the MAP display, a number and RSSC appear under the
CCS header in the alarm banner. The RSSC indicates a critical alarm for a
remote subsystem (RSSC).
Meaning
The indicated number of remote subsystems is out of service.
Result
The number shown under the common channel signaling (CCS) header of
the alarm banner indicates the number of remote subsystems affected.
Common procedures
Action
procedure.
GSP05 (CSP10)
CCS RSSC
Summary of Clearing a CCS RSSC critical alarm
Display the This flowchart summarizes the

RSSC alarms procedure.

Subsystem Y Clear PCC flowchart to perform the procedure.
system busy? critical alarm
N
Collect
Subsystem Y information on
manual–busy
point code and
?
subsystem
N
Return
subsystem to
service
Wait 5 min N Subsystem in Y

service?
Did the RSSC Y

alarm clear?
N
Work with Subsystem in Y
remote office service?
to clear the
RSSC alarm
N
Contact next End
level of support
297-2651-543 Standard 05.01 March 1999

CCS RSSC
Clearing a CCS RSSC critical alarm
At the MAP display
>MAPCI;MTC;CCS;CCS7
2 To display the remote subsystems that run the RSSC alarm, type
>DISALM RSSC
Subsystem Alm Stat
SSP100_RT 800P RSSC SysB
SSP107_RT ACCS RSSC ManB
3 Record the point code name, the subsystem name, and state for the first
remote subsystem shown on the MAP display.
Note: The point code name appears under the Subsystem header on the MAP
display. The remote subsystem name appears on the right of the point code
name. The remote subsystem state appears under the state header.
If the state of the remote

subsystem Do
is SysB step 4
is ManB step 7
is INI step 14
GSP05 (CSP10)
CCS RSSC
4 To determine if PCC critical alarms are present, type

>DISALM PCC
Point code Alm Stat
SSP100_RT PCC SysB
SSP107_RT PCC SysB
If the MAP display Do
responds with a list of PCC alarms step 5

responds with no PCC alarms step 38
5 Perform the procedure Clearing a CCS PCC critical alarm in this document.
6 Determine if the RSSC alarm cleared.
If the RSSC alarm Do
cleared step 39
7 To access the SCCPRPC level of the MAP display, type

>SCCPRPC
8 The remote subsystem is on a point code. To post this point code, type
>POST point_code
where
point_code is the point code name recorded in step 3 for the
subsystem that is in use
C7 SCCP REMOTE PC
Point code State Number of SS
SSP107_RT INSV 1
297-2651-543 Standard 05.01 March 1999

CCS RSSC
9 To access the SCCPRSS level of the MAP display, type

>SCCPRSS
10 To post the remote subsystem, type

>POST subsystem
where
subsystem is the name of the remote subsystem that you recorded in
step 3
C7 SCCP REMOTE SS
Subsystem State
800P INSV
subsystem is manual busy.
12 When you have permission to return the subsystem to service, type

>RTS subsystem
where
subsystem is the name of the remote subsystem that you recorded in
step 3
800P : RTS passed
passed step 39
failed step 13
GSP05 (CSP10)
CCS RSSC
13 Determine the state of the remote subsystem.
If the state of the remote

subsystem Do
is INI step 14
14 Wait 5 min to see if the state of the remote subsystem changes to InSv
If the state Do
changed to InSv step 37

did not change to InSv step 15
15 To return to the command interpreter (CI) level of the MAP display, type
>QUIT ALL
16 To access the C7NETSSN table, type

>TABLE C7NETSSN
TABLE: C7NETSSN
17 To position on the tuple for the point code, type

>POSITION point_code
where
point_code is the name of the point code recorded in step 3 and posted in
step 8
PCNAME SSNAMES
SSP107_RT (ACCS 7) (E800 254)$
297-2651-543 Standard 05.01 March 1999

CCS RSSC
18 To display table headings, type

>LIS
PCNAME SSNAMES
SSP107_RT (ACCS 7) (E800 254)$
19 Record the subsystem names and numbers.

Note: The subsystem names and numbers appear in parentheses under and
on the left of the header SSNAMES on the MAP display.
20 Determine which names and numbers recorded at step 19 are the names and
numbers of the subsystem you are working on.
21 To quit the C7NETSSN table, type

>QUIT
22 The office records reveal the point code that represents the far-end office. The
point card is in use at this time. You must work with the operating company
personnel in the far-end office for the remainder of this procedure.
23 Contact the far-end office. To inform the operating company personnel to

access the C7LOCSSN table, type
>TABLE C7LOCSSN
TABLE: C7LOCSSN
24 To inform the operating company personnel at the far-end office to search for
the subsystem in use, type
>LIST ALL (SSNUMBER EQ subsys_no)
where
subsys_no is the number of the subsystem recorded in step 19
SSNAME SSNUMBER MININST REPLINFO TFMI PCNAMES
E800 254 1 N N SSP100_RT
GSP05 (CSP10)
CCS RSSC
25 Determine from the far-end office the results of the LIST command.
reports that a tuple appears step 26

reports that a tuple does not appear step 38
26 Inform operating company personnel at the far-end office to record the

subsystem name.
Note: The subsystem name appears under and to the left of the header
SSNAME on the MAP display.
27 To inform operating company personnel at the far-end office to quit the

C7LOCSSN table, type
>QUIT
28 To inform operating company personnel at the far-end office to access the

SCCPLOC level of the MAP display, type
>MAPCI;MTC;CCS;CCS7;SCCPLOC
29 To inform operating company personnel at the far-end office to post the

subsystem in use, type
>POST subsystem
where
subsystem is the name of the subsystem recorded in step 26.
If the subsystem Do
runs an LSSC alarm step 30

is OFFL step 32
30 Inform the operating company personnel at the far-end office to perform the
procedure Clearing an LSSC critical alarm in this document. When the
operating company personnel complete the procedure, return to this point.
31 Go to step 36.
297-2651-543 Standard 05.01 March 1999

CCS RSSC
critical
critical
(continued)
(end)
32 Contact the operating company personnel at the far-end office. Determine from
office records or from operating company personnel why the subsystem is
offline. When the operating company personnel have permission to perform
maintenance on the offline subsystem, continue the procedure.
33 To inform operating company personnel at the far-end office to manually busy

the subsystem, type
>BSY
passed step 34
failed step 35
34 To inform operating company personnel at the far-end office to return the

subsystem to service, type
>RTS
Go to step 36.
35 Inform operating company personnel at the far-end office to contact the next
level of support for help.

>MAPCI;MTC;CCS;CCS7
37 Determine if the RSSC alarm cleared.
If the RSSC alarm Do
cleared step 39
GSP05 (CSP10)
CCS RTRC
critical
Alarm display
. . . . . 3RTRC . . . .
*C*
Indication
At the MTC level of the MAP display, a number and RTRC appear under the
CCS header in the alarm banner. The RTRC indicates a critical alarm for a
C7 (RTR).
Meaning
An RTRC alarm rises if all the entered routers are not available. A router is
not available if the router is SysB, ManB or Offline.
The number for the alarm indicates the number of routers that are not
available. Table C7ROUTER must contain a minimum of one router. If
table C7ROUTER does not contain any routers, the number associated with
the alarm is one.
Result
If a total router outage (TRO) occurs, all CCS7 links in an office become
blocked (Blkd). The TRO also results in the removal of the links from
service. All messages for ISDN user part (ISUP) or messages for
transaction capabilities applications part (TCAP) do not transmit. Another
possibility is that messages cannot reach a specified destination during a
TRO.
An RTRC alarm is more important than all types of common channel

signaling (CCS) critical alarms.
Note: The return of a router InSv after you clear the RTRC alarm can
cause a RTRM alarm.
Action
procedure.
297-2651-543 Standard 05.01 March 1999

CCS RTRC
Summary of Clearing a CCS RTRC critical alarm
Determine the This flowchart summarizes the

state of C7 procedure.
router
Post the router procedure.
set
Routers Y
ManB?
Routers Y Select the Return to RTRM N

OffL? Offline router service alarm
active?
N Y
Clear the
RTRM alarm
Y Access the PM Clear the LIU7

Router level of the
SysB alarm
MAP
N
SysB
Y End
command
passed?
Contact the
next level of
support
GSP05 (CSP10)
CCS RTRC
Clearing a CCS RTRC critical alarm
At the MAP terminal
1 To access the C7ROUTER level of the MAP display, type
>MAPCI;MTC;CCS;CCS7;C7ROUTER
2 To display routers that have RTRC alarms, type

>DISALM RTRC
Example of MAP display:
External Routing Alarm: RTRC
C7Router Resource Status
2 LIU7 102 SysB
3 LIU7 103 SysB
8 LIU7 108 ManB
Note: A total router outage onset (TRO) occurs if all routers are not available
or out of service.
3 To post the routers, type

>POST ALL
297-2651-543 Standard 05.01 March 1999

CCS RTRC
4 To display status of routers, type

>QUERYRTR_ALL
External Routing InSv
1111111 11122222 22222333
Router 12345678 90123459 78901234 56789012
OSSOOOOM -------- -------- --------
Rtr State Resource PM State
2 SysB LIU 101 SysB
Rtr State Resource PM State Congestion Level
1 OffL LIU7 101 OffL
2 SysB LIU7 102 SysB 0
3 SysB LIU7 103 SysB 0
8 ManB LIU7 108 InSv 0
If any routers Do
are ManB step 5

are OFFL step 7
are SysB step 9
5 Note the numbers of an ManB router and the equivalent LIU7.
6 Determine from office records why the router is ManB.

When you have permission, go to step 26.
GSP05 (CSP10)
CCS RTRC
7 Select an OFFL router and the equivalent LIU7.
If the LIU7 Do
is InSv step 20
is ISTb step 20
8 Go to step 11.
9 Note the number of the SysB router and equivalent LIU7.
10 Go to step 11.
11 To access the PM level of the MAP display, type

>MAPCI;MTC;PM
12 To post the LIU7 you selected, type

>POST LIU7 liu_no
where
liu_no is the number of the LIU7 (0 to 215)
If the LIU7 Do
is ManB step 13
is SysB step 15
is OFFL step 14
13 Determine from office records why the LUI7 is ManB.

When you have permission, go to step 16.
297-2651-543 Standard 05.01 March 1999

CCS RTRC
14 To manually busy the LIU7, type

>BSY
passed step 16
failed step 15
15 Perform the correct procedure in this document to clear all PM LIU7 alarms.
16 To return the LIU7 to service, type

>RTS
passed step 17
failed step 15

>MAPCI;MTC;CCS;CCS7;ROUTER
18 Select the OFFL router for return to service (RTS).
19 To post the router, type

>POST router_no
where
router_no is the number of the router
GSP05 (CSP10)
CCS RTRC
20 To busy the required posted router set, type

>BSY
External Routing Bsy
1111111 11122222 22222333

Router 12345678 90123459 78901234 56789012
MSS----M -------- -------- --------

1 ManB LIU7 108 InSv
Note: The preceding MAP response is for a OFFL router and LIU7.
passed step 26
failed - no message to router step 25
management
failed - no response from router step 25
management
failed - system problems step 21
failed - router not entered in table step 23
C7ROUTER
21 Check CCS196 log and reason for system problems.
22 Go to step 25.
23 Contact the next level of support to determine if you entered the selected router.
24 Go to step 7 and select another OFFL router and equivalent LIU7.
297-2651-543 Standard 05.01 March 1999

CCS RTRC
25 To busy the failed router again, type

>BSY router_no
where
External Routing OffL
1111111 11122222 22222333

Router 12345678 90123459 78901234 56789012
MSS----M -------- -------- --------

passed step 26
failed step 35
GSP05 (CSP10)
CCS RTRC
26 To return the selected routeset to service, type

>RTS router_no
where
1111111 11122222 22222333

Router 12345678 90123459 78901234 56789012
.SS----M -------- -------- --------

1 InSv LIU7 101 InSv
Note: The preceding MAP response is for a Bsy router and LIU7.
passed step 30
passed but a RTRM alarm is active step 27
management
management
failed - system problems step 29
27 Perform the correct procedure in this document to clear the RTRM alarm.
28 Go to step 30.
297-2651-543 Standard 05.01 March 1999

CCS RTRC
29 To return the failed router set to service, type

>RTS router_no
where
1111111 11122222 22222333

Router 12345678 90123459 78901234 56789012
.SS----M -------- -------- --------

Note: The preceding MAP response is for a Bsy router and LIU7.
passed step 30
passed but a RTRM alarm is active step 35
30 Remove the TRO condition when one router is InSv.
If the TRO condition Do
cleared step 32
failed because of a link alarm step 31
31 Use the correct procedures in this manual to clear link alarms and clear the link
problem. Complete the procedure and return to this point.
GSP05 (CSP10)
CCS RTRC
(end)
32 To check the status of the router set, type

>QUERYRTR_ALL
1111111 11122222 22222333

Router 12345678 90123459 78901234 56789012
-.----. -..----- -.----.- --.---.-

4 InSv LIU 101 InSv

1 InSv LIU7 101 InSv 0
33 Office records will reveal the far-end office that connects to the posted linkset.
34 Contact the far-end office. Inform the operating company personnel that you
activated a CCS7 critical alarm. Inform the operating company personnel that
one or more associated links are now in service.
35 For additional help, contact the next level of support
297-2651-543 Standard 05.01 March 1999

CCS RTRM
major
Alarm display
. . . . . 1RTRM . . .
*M*
Indication
At the MTC level of the MAP display, a number and RTRM appear under
the CCS header in the alarm banner. The RTRM indicates a major alarm for
a C7 (RTR). A CCS 189 log indicates the congested router or routers and
the congestion level of the routers.
Meaning
An RTRM alarm raises against a router or routers for the following reasons:
• the router or routers are in a manual busy (ManB) state
• the router or routers are in a system busy (SySb) state. This state occurs
when the peripheral that matches the router is in an out-of-service state
• the router or routers are in an in-service trouble (ISTb) state. High
traffic volume causes congestion. Congestion causes an ISTb in the
routers
Note: One router must be available for this alarm to take effect.
Result
This major alarm can disappear if the last router is not available. If the last
router is not available, all routers become RTRC critical alarms.
Action
procedure.
GSP05 (CSP10)
CCS RTRM
major (continued)
Summary of Clearing a CCS RTRM RTRM major alarm
Determine This flowchart summarizes the

state of C7 procedure.
router
procedure.
Post router set
Router Y
ManB?
Y Select offline Return to Router

Router N
router service congested?
ISTb?
N Y
Access PM Post LIU7 Clear LIU7

Router is level of MAP
SysB alarm
display
Alarm Y End
cleared?
Contact next
level of support
297-2651-543 Standard 05.01 March 1999

CCS RTRM
major (continued)
Clearing a CCS RTRM major alarm
At the MAP display
2 To display routers that have RTRM alarms, type

>DISALM RTRM
External Routing Alarm: RTRM
C7Router Resource Status
1 LIU7 101 ManB
2 LIU7 102 ISTb
3 LIU7 103 ISTb
5 LIU7 105 SysB

>POST ALL
GSP05 (CSP10)
CCS RTRM
major (continued)
4 To display status of routers, type

>QUERYRTR_ALL
External Routing ISTb
1111111 11122222 22222333
Router 12345678 90123459 78901234 56789012
MIIOSOOO -------- -------- --------
2 ISTb LIU 101 InSv
2 ISTb LIU7 102 InSv 2
5 SySb LIU7 105 SysB 0
If one or more of the routers Do
is ManB step 5
is ISTb step 7
is SySb step 8
5 Note the number of the ManB router and equivalent link interface unit for the
CCS7 (LIU7).
6 Determine from office records why the router is ManB.

When you have permission, continue this procedure. Go to step 23.
297-2651-543 Standard 05.01 March 1999

CCS RTRM
major (continued)
7 Select an OFFL router and equivalent LIU7.
If the LIU7 Do
is InSv step17
is ISTb step17
8 Note the number of the SysB router and equivalent LIU7.

>MAPCI;MTC;PM
10 To post the LIU7 you selected, type

>POST LIU7 liu_no
where
liu_no is the number of the LIU7 (0 to 215)
If the LIU7 Do
is ManB step 13
is OFFL step 11
is SysB step 12
11 To manually busy the LIU7, type

>BSY
passed step 13
failed step 12
GSP05 (CSP10)
CCS RTRM
major (continued)
12 Perform the appropriate alarm clearing procedures in this document to clear all
PM LIU7 alarms. Complete the procedure and return to this point.
13 To return the LIU7 to service, type

>RTS
passed step 14
failed step 12

15 Select the OFFL router to return to service.

>POST router_no
where
297-2651-543 Standard 05.01 March 1999

CCS RTRM
major (continued)
17 To busy the required posted router, type

>BSY
1111111 11122222 22222333
Router 12345678 90123459 78901234 56789012
MIIMSOOO ------ -------- --------
4 ManB LIU 104 InSv
Note: MAP response shown is for an OFFL router and LIU7.
passed step 23
management
management
failed - system problem step 18
failed - router not entered in table step 20
C7ROUTER
18 Check logs and the reason for system problems.
19 Go to step 22.
20 Contact your next level of support to determine if the selected router is not
entered.
GSP05 (CSP10)
CCS RTRM
major (continued)
21 Go to step 7 and select another OFFL router and equivalent LIU7.
22 To busy the failed router again, type

>BSY router_no
where
1111111 11122222 22222333
Router 12345678 90123459 78901234 56789012
MIIMSOOO ------ -------- --------
4 ManB LIU 104 InSv
Note: MAP response shown is for an OFFL router and LIU7.
passed step 23
other than listed here step 27
297-2651-543 Standard 05.01 March 1999

CCS RTRM
major (continued)
23 To return the selected router to service, type

>RTS router_no
where
1111111 11122222 22222333
Router 12345678 90123459 78901234 56789012
..I..OOO -------- -------- --------
Note: The following MAP response covers:
• an Offl router and LIU7 selected in step 7
• a ManB router selected in step 5
• a SySb router and LIU7 selected in step 8
passed step 25
management
management
failed - system problem step 24
GSP05 (CSP10)
CCS RTRM
major (continued)
24 To return the failed router to service, type

>RTS router_no
where
1111111 11122222 22222333
Router 12345678 90123459 78901234 56789012
..I..OOO -------- -------- --------
passed step 25
297-2651-543 Standard 05.01 March 1999

CCS RTRM
majormajor
(continued)
(end)
25 To check the status of the routers, type

>QUERYRTR_ALL
1111111 11122222 22222333
Router 12345678 90123459 78901234 56789012
.I...OOO -------- -------- --------
1 InSv LIU 101 InSv
Note: The following MAP response covers:
• an Offl router and LIU7 selected in step 7
• a ManB router selected in step 5
• a SySb router and LIU7 selected in step 8
cleared the alarm step 28

did not clear the alarm. Congestion step 26
continues to occur on the #2 router.
26 Go to step 7 and bring another OFFL router and LIU7 into service to clear the
congestion level alarm.
27 For additional help, contact the next level of support
GSP05 (CSP10)
3-1
Computing module alarm clearing

procedures
Introduction
This chapter provides alarm clearing procedures for the computing module
(CM). Computing module alarms appear under the CM header of the alarm
banner in the MAP display. Each procedure contains the following sections:
• Alarm display
• Indication
• Meaning
• Result
• Action
Alarm display
Indication
This section indicates the following:
• Appearance of the alarm
• Model of the alarm
• Affected subsystems
• Alarm intensity
Meaning
Result
GSP05 (CSP10)
3-2 CM alarm clearing procedures
Common procedures
procedure. A common procedure consists of a series of repeated steps
within maintenance procedures, for example, removal and replacement of a
card. Common procedures are in the common procedures chapter in this
Northern Telecom publication (NTP).
Do not go to a common procedure unless the step-action procedure directs

you to go.
Action
This section provides a summary flowchart of the alarm clearing procedure.
A detailed step-action procedure follows the flowchart.
297-2651-543 Standard 05.01 March 1999

3-3 Computing module alarm clearing procedures 3-3
CM MMsync
major
Alarm display
MMSync . . . . . . . . .
M
Indication
At the MTC level of the MAP display, MMSync appears under the CM
header of the alarm banner. The MMSync indicates a major alarm for a fault
mismatch.
Meaning
A fault mismatch occurred. An adjustable memory fault did not occur.
Synchronization of the switch occurred again. In most occurrences, a
hardware fault causes the mismatch. The next level of support must analyze
the mismatch history.
A Series 60 burst mode write operation can cause a type of mismatch

referred to as a matcher transient mismatch (MTM). The MMsync alarm
threshold for MTMs is different than the threshold for other types of
mismatches. For MTMs, the default threshold is 30 per day. This threshold
can be reset to any value in the range of 10 to 50 using the MMSYNC SET
command.
Result
The problem does not affect switch operation. The switch continues to
operate in the synchronous mode.
Common procedures
Action
procedure.
GSP05 (CSP10)
3-4 Computing module alarm clearing procedures
CM MMsync
major (continued)
Summary of Clearing a CM MMsync major alarm
Refer msmtch This flowchart summarizes the

log to next procedure.
level of support
procedure.
Clear the
alarm
End
297-2651-543 Standard 05.01 March 1999

CM MMsync
majormajor
(continued)
(end)
Clearing a CM MMsync major alarm
1 Notify the next level of support to perform direction analysis on the mismatch
logs.
At the MAP display
2 To access the CM level of the MAP display, type
>MAPCI;MTC;CM
CM Sync Act CPU0 CPU1 Jam Memory CMMnt MC PMC
0 no CPU1 . . . . . . .
3 To begin to clear the MMsync alarm, type

>CLRALARM MMsync
The MMsync alarm will be cleared.
Do you wish to continue?
Please confirm (”YES”, ”Y”, ”NO”,
”N”):
4 To clear the MMsync alarm, type

>Y
The MMsync alarm has been cleared.
Note: A generated CM176 log indicates that the alarm cleared.
GSP05 (CSP10)
CM AutoLd
minor
Alarm display
AutoLd . . . . . . . . .
Indication
At the MTC level of the MAP display, AutoLd appears under the computing
module (CM) header of the alarm banner. The AutoLd indicates a minor
alarm for an automatic reload.
Meaning
A defect or error prevents the automatic reload of the switch.
Result
The problem does not affect subscriber service.
Common procedures
Action
procedure.
297-2651-543 Standard 05.01 March 1999

CM AutoLd
minor (continued)
Summary of Clearing a CM AutoLd minor alarm

procedure.
Obtain CM logs
procedure.
Contact next
level of support
End
GSP05 (CSP10)
CM AutoLd
minor (continued)
(end)
Clearing a CM AutoLd minor alarm
At the MAP terminal
1 Obtain all recent CM logs.
297-2651-543 Standard 05.01 March 1999

CM CBsyMC
major
Alarm display
CBsyMC . . . . . . . . .
M
Indication
At the MTC level of the MAP display, CBsyMC appears under the CM
header of the alarm banner. CBsyMC indicates a major alarm for a C-side
busy message controller.
Meaning
The message controller (MC) is control-side (C-side) busy. The links to the
message switch (MS) are system busy or manual busy.
Result
The computing module (CM) contains two MCs. If one MC is out of
service, the second MC assumes the full messaging load. After the removal
of the second MC, the switch cannot maintain subscriber service.
Common procedures
Action
procedure.
GSP05 (CSP10)
CM CBsyMC
major (continued)
Summary of Clearing a CM CBsyMC major alarm
Clear MS This flowchart summarizes the

alarms procedure.

Test affected procedure.
MC
N Replace card.
Passed? Refer to 1
appropriate NTP.
1
Y Y
Return MC to
service
RTS
N
command
passed?
YY
Release jam
and synchronize
affected CM
Alarm N
cleared?
End Contact next

level of support
297-2651-543 Standard 05.01 March 1999

CM CBsyMC
major (continued)
Clearing a CM CBsyMC major alarm
At the MAP terminal
1 Use the correct MS alarm clearing procedures in this document to clear any MS
alarms. Complete the procedures and return to this point.
2 Determine if the CBsyMC main alarm cleared.
If the alarm Do
cleared step 24
changed to another alarm step 22
3 To access the MC level of the MAP display, type

>MAPCI;MTC;CM;MC
CM 0
MC 0 MC 1
. cbsy
GSP05 (CSP10)
CM CBsyMC
major (continued)
4 To test the affected MC, type

>TST mc_number
and press the Enter key
where
mc_number is the number of the C-side busy MC (0 or 1)
Note: The state of the MCs appears under the MC 0 and MC 1 headers of the
MAP display. In the example in step 3, MC 1 is C-side busy.
Maintenance action submitted.
MC test passed.
Link 0: 0 messages sent, 0 messages received
– Possible C–side problem.
Link 1: 0 messages sent, 0 messages received
– Possible C–side problem.
TOD 0 test passed
TOD 1 test passed
passed step 15
failed, and the system generated a step 5
card list
5 Record the location, description, slot number, product engineering code (PEC),
and PEC suffix of the first card on the list.
6 Perform the correct procedure in Card Replacement Procedures. Complete the

297-2651-543 Standard 05.01 March 1999

CM CBsyMC
major (continued)

>CM;MC
CM 0
MC 0 MC 1
. mbsy
8 To test the affected MC, type

>TST mc_number
where
mc_number is the number of the affected MC (0 or 1)
passed step 10
failed, and you did not replaced all step 9
the cards on the list
failed, and you replaced all the step 23
cards on the list
9 Record the location, description, slot number, PEC, and PEC suffix of the next
card on the list.
Go to step 6.
10 Determine if the affected MC is manual busy.

Note: The term mbsy under the MC0 or MC1 header on the MAP display
means the MC is manual busy. In the example in step 7, MC 1 is manual busy.
If the state of the MC Do
is mbsy step 11
is no mbsy step 12
GSP05 (CSP10)
CM CBsyMC
major (continued)
11 To return the manual busy MC to service, type

>RTS mc_number
where
mc_number is the number of the manual busy MC (0 or 1)
MC RTS ok.
passed step 12
failed step 23
12 Determine if the inactive CM surface powered down.
If the inactive CM surface Do
powered down step 13

did not power down step 15
13 To test the inactive central processing unit (CPU), type

>CM;TST
The test(s) listed below will destroy
the software load in inactive CPU:
Static RAM test
Do you want to do the test(s) anyway?

Please confirm: (”YES”, ”Y”, ”NO”, or ”N”):
297-2651-543 Standard 05.01 March 1999

CM CBsyMC
major (continued)

>YES
Test passed.
passed step 15
failed step 23
15 Determine if the inactive CPU jammed.

Note: The word yes under the Jam header means that the CPU jammed. The
area is blank if the CPU did not jam.
If the inactive CPU Do
jammed step 16
did not jam step 17
At the CM reset terminal for the inactive CPU

16 To release the jam on the inactive CPU, type
>\RELEASE JAM
RTIF response:
JAM RELEASE DONE.
GSP05 (CSP10)
CM CBsyMC
major (continued)
At the MAP terminal
17 Determine if the CM is in sync.
Note: A dot or EccOn under the Sync header means that the CM is in sync.
The word no means that the CM is not in sync.
If the CM Do
is in sync step 20
is not in sync step 18
18 To synchronize the CM, type

>CM;SYNC
Synchronization successful.
If the response Do
indicates the SYNC command is step 20

successful
indicates the CPUs are out of sync step 19
as a result of a problem with
mismatches. Analyze the mismatch
logs before you synchronize the
logs again.
Please confirm (yes, ‘Y”
or no, “N”)
(SN/SNSE Series 70 only)
19 (SN/SNSE Series 70 only)

To deny the action, type
>NO
Go to step 23.
297-2651-543 Standard 05.01 March 1999

CM CBsyMC
majormajor
(continued)
(end)
20 Determine if the CBsyMC main alarm cleared.
If the alarm Do
cleared step 24
21 If a fiber link that has faults is present between the CM and MS, go to step 23.
22 Perform the correct alarm clearing procedure in this document.
GSP05 (CSP10)
CM ClkFlt
major
Alarm display
ClkFlt . . . . . . . . .
M
Indication
At the MTC level of the MAP display, ClkFlt appears under the CM header
of the alarm banner. The ClkFlt indicates a clock major alarm.
Meaning
One of the central processing units (CPU) has a processor clock fault.
Result
In simplex or split mode, the active CPU normally runs on the clock of the
active CPU. In duplex mode, the computing module (CM) is in sync. In
duplex mode, both CPUs are in sync with a common clock.
A CPU with a processor clock that has faults can operate while the CPU
runs on the clock of the mate CPU.
Common procedures
Action
procedure.
297-2651-543 Standard 05.01 March 1999

CM ClkFlt
major (continued)
Summary of Clearing a CM ClkFlt major alarm
Jam inactive This flowchart summarizes the

CPU and drop procedure.
synchronization
Test inactive procedure.
CPU
TST Y
command
passed?
N
Replace card.
Refer to the
correct NTP.
Alarm Y
cleared?
Contact next End

level of support
GSP05 (CSP10)
CM ClkFlt
major (continued)
Clearing a CM ClkFlt major alarm
At the MAP terminal
>MAPCI;MTC;CM
0 no cpu 1 clk . yes . . . .

area is blank if the CPU did not jam. In the example in step 1, the inactive CPU
(CPU 0) jammed.
jammed step 5
did not jam step 3
297-2651-543 Standard 05.01 March 1999

CM ClkFlt
major (continued)
3
CAUTION
Loss of service
Make sure that you do not jam the active CPU. If you
jam the active CPU while the CM is out of sync, a
cold restart occurs. The word Active on the top
banner of the display identifies the reset terminal for
the active CPU.
CAUTION
Loss of service
Make sure that you do not jam the active CPU. If
you jam the active CPU while the CM is out of sync,
a cold restart occurs. The word Active on the top
the active CPU.
To jam the inactive CPU, type

>\JAM
RTIF response:
Please confirm: (YES/NO)

>YES
RTIF response:
JAM DONE
At the MAP terminal

5 Determine that the CM is in sync.
GSP05 (CSP10)
CM ClkFlt
major (continued)
If the CM Do
is in sync step 6
6 To drop synchronization, type

>DPSYNC
If the response Do
is About to drop sync with step 7

CPU n active.
The inactive CPU JAMMED.
Do you want to continue?
Please confirm (”YES”,
”Y”, ”NO”, or ”N”):

>YES

8 Wait until A1 flashes on the reset terminal for the inactive CPU.
Note: Wait five minutes for A1 to flash.
If A1 Do
flashes step 9
does not flash step 22
297-2651-543 Standard 05.01 March 1999

CM ClkFlt
major (continued)
At the MAP terminal
9 To test the inactive CPU, type
>TST
If the response Do
is The test(s) listed below step 10

will destroy the software
load in inactive CPU:
Static RAM test
Do you want to do the

test(s) anyway?
Please confirm: (”YES”,
”Y”, ”NO”, or ”N”):
10 To confirm the command , type

>YES
passed step 17
card list

GSP05 (CSP10)
CM ClkFlt
major (continued)
At the MAP terminal
>CM
0 no cpu 1 clk . yes . . . .

>TST
If the response Do

Static RAM test
Do you want to do the

test(s) anyway?
”Y”, ”NO”, or ”N”):

>YES
passed step 17
failed, and you did not replace all step 16
cards on the list
failed, and you replaced all cards step 22
on the list
297-2651-543 Standard 05.01 March 1999

CM ClkFlt
major (continued)
16 Determine the location, description, slot number, PEC, and PEC suffix of the
next card on the list.
Go to step 12.
>\RELEASE JAM
RTIF response:
JAM RELEASE DONE
At the MAP terminal

>SYNC
If the response Do
indicates the SYNC command was step 20

successful
logs again.
Please confirm (yes, ‘Y”
or no, “N”)
GSP05 (CSP10)
CM ClkFlt
major (continued)
(end)

>NO
Go to step 22.
20 Determine if the ClkFlt main alarm cleared.
If the alarm Do
cleared step 23
297-2651-543 Standard 05.01 March 1999

CM CMTrap
major
Alarm display
CMTrap . . . . . . . . .
M
Indication
At the MTC level of the MAP display, CMTrap appears under the CM
header of the alarm banner. The CMTrap indicates a major alarm for the
trap rate.
Meaning
The trap rate approaches a threshold that can cause a warm restart.
Result
The computing module (CM) requires more time to correct faults than the
average amount of time the CM requires. Subscriber service problems can
arise as a result of the slow system response time. If the trap rate exceeds
the threshold, a warm restart occurs.
Common procedures
Action
procedure.
GSP05 (CSP10)
CM CMTrap
major (continued)
Summary of Clearing a CM CMTrap major alarm
Record number This flowchart summarizes the

of traps procedure.

procedure.
Obtain all latest
trap logs
Contact next
level of support
End
297-2651-543 Standard 05.01 March 1999

CM CMTrap
majormajor
(continued)
(end)
Clearing a CM CMTrap major alarm
At the MAP display
1 To access the CMMNT level of the MAP display, type
>MAPCI;MTC;CM;CMMNT
0 . cpu 0 . . . . . .
Traps: Per minute = 108 Total = 6342
AutoLdev: Primary = SLM 0 disk Secondary = SLM 1 DISK
Image Restartable = No image test since last restart
Next CM image test restart type= RELOAD
Last CMREXTST executed
System memory in kbytes as of 14:39:07

Memory(kbytes):Used = 105984 Avail = 12800 Total = 118784
2 Record the total number of traps.

Note: The total number of traps is on the right of the Traps header in the Total
field.
3 Obtain all current trap logs.
GSP05 (CSP10)
CM E2A
minor
Alarm display
E2A . . . . . . . . .
Indication
At the MTC level of the MAP display, E2A appears under the computing
module (CM) header of the alarm banner. The E2A indicates an E2A minor
alarm.
Meaning
The E2A links are not in service. The E2A links provide remote access to
the reset system of the switch.
Result
The problem does not affect subscriber service. Remote access to the reset
system of the switch through one or both of the E2A links is not available.
Common procedures
Action
procedure.
297-2651-543 Standard 05.01 March 1999

CM E2A
minor (continued)
Summary of Clearing a CM E2A minor alarm

state of the procedure.
E2A link
Verify the procedure.
connection of
the E2A link
Enable the
E2A link
Alarm
N
cleared?
Y
End Contact next
level of support
GSP05 (CSP10)
CM E2A
minor (continued)
Clearing a CM E2A minor alarm
At the MAP terminal
>MAPCI;MTC;CM
0 no cpu 1 e2a . yes . . . .
2 To determine the status of the E2A links, type

>E2ALINK CHECK
CPU0: E2A Link is DISCONNECTED, ENABLED.
CPU1: E2A Link is DISCONNECTED, DISABLED.
If the response indicates that

either E2A link Do
is UNSTABLE, ENABLED or step 3

UNSTABLE, DISABLED
is DISCONNECTED, DISABLED step 3
or DISCONNECTED, ENABLED
is CONNECTED, DISABLED step 5
At the switch
3 At the back of the switch, make sure that all connections between the NT9X26
cards and the E2A telemetry equipment are secure.
297-2651-543 Standard 05.01 March 1999

CM E2A
minor
minor
(continued)
(end)
At the MAP terminal
4 To determine the status of the E2A links, type
>E2ALINK CHECK
CPU1: E2A Link is CONNECTED, ENABLED.
CPU0: E2A Link is DISCONNECTED, DISABLED.
If both E2A links Do
are CONNECTED, ENABLED step 6

are CONNECTED, DISABLED step 5
are other than listed here step 7
5 To enable the E2A links, type

>E2ALINK ENABLE n
where
n is the number of the central processing unit (CPU) with the disabled link (0
or 1)
CPU1: E2A Link is CONNECTED, ENABLED.
6 Determine if the E2A minor alarm cleared.
If the alarm Do
cleared step 8
GSP05 (CSP10)
CM EccOn
minor
Alarm display
EccOn . . . . . . . . .
Indication
At the MTC level of the MAP display, EccOn appears under the CM header
of the alarm banner. The EccOn indicates an error-checking minor alarm.
Meaning
The computing module (CM) runs in synchronization with memory error
checking and correction enabled. Mismatches caused by adjustable single
bit memory errors do not occur.
Result
Processor performance is slower.
Common procedures
Action
procedure.
297-2651-543 Standard 05.01 March 1999

CM EccOn
minor (continued)
Summary of Clearing a CM EccOn minor alarm

Jam inactive procedure.
CPU and drop
synchronization Use the instructions that follow
procedure.
Release jam
and synchronize
CM
Alarm N Contact next

cleared? level of support
Y
End
GSP05 (CSP10)
CM EccOn
minor (continued)
Clearing a CM EccOn minor alarm
1 Consult office records or operating company personnel. Determine the reason
for the enabled memory checking. Determine when you can disable memory
error checking and correction.
To disable memory error checking and correction, continue this procedure as
permitted.
At the MAP terminal
>MAPCI;MTC;CM
0 Eccon cpu 1 . . yes . . . .
3 Determine if the inactive central processing unit (CPU) jammed.

Note: The word yes under the Jam header means that the inactive CPU
jammed. The area is blank if the CPU did not jam.
jammed step 6
did not jam step 4
297-2651-543 Standard 05.01 March 1999

CM EccOn
minor (continued)
4
CAUTION
Loss of service
jam the active CPU while the CM is not in sync, a
the active CPU.
CAUTION
Loss of service
you jam the active CPU while the CM is not in sync,
the active CPU.

>\JAM
RTIF response:
Please confirm (YES/NO)

>YES
RTIF response:
JAM DONE
GSP05 (CSP10)
CM EccOn
minor (continued)
At the MAP terminal
>DPSYNC
If the response Do

CPU n active.
The inactive CPU is
JAMMED.
”Y”, ”NO” or ”N”):

>YES
Note: Wait 5 min for A1 to flash.
If A1 Do
flashes step 9

>\RELEASE JAM
RTIF response:
JAM RELEASE DONE
297-2651-543 Standard 05.01 March 1999

CM EccOn
minor
minor
(continued)
(end)
At the MAP terminal
>SYNC
If the response Do

successful
11 Determine if the EccOn minor alarm cleared.
If the alarm Do
cleared step 13
GSP05 (CSP10)
CM IMAGE
critical
Alarm display
IMAGE . . . . . . . . .
*C*
Indication
At the MTC level of the MAP display, IMAGE appears under the CM
header of the alarm banner. The IMAGE indicates an IMAGE critical alarm.
Meaning
The software load on the inactive central processing unit (CPU) cannot
maintain a restart.
Result
The problem does not affect subscriber service. If a fault occurs on the
active side, the switch cannot recover immediately.
Common procedures
Action
procedure.
297-2651-543 Standard 05.01 March 1999

CM IMAGE
Summary of Clearing a CM IMAGE critical alarm
Obtain CM logs This flowchart summarizes the

procedure.

Contact next procedure.
level of support
End
GSP05 (CSP10)
CM IMAGE
(end)
Clearing a CM IMAGE critical alarm
At the MAP
1 Obtain all the latest CM logs.
297-2651-543 Standard 05.01 March 1999

CM JInact
minor
Alarm display
Jlnact . . . . . . . . .
Indication
At the MTC level of the MAP display, JInact appears under the computing
module (CM) header of the alarm banner. The JInact indicates a jammed
inactive CPU minor alarm.
Meaning
The inactive central processing unit (CPU) jammed. If the system generated
the alarm, SysJam appears on the RTIF status line of the RTIF terminal. If
the inactive CPU manually jammed, ManJam appears on the RTIF status
line of the RTIF terminal.
Result
The problem does not affect subscriber service. Activity cannot switch with
a jammed inactive CPU.
Common procedures
Action
procedure.
GSP05 (CSP10)
CM JInact
minor (continued)
Summary of Clearing a CM JInact minor alarm

procedure.
Inactive CPU When
Y Use the instructions that follow
manually permitted,
jammed? continue. this flowchart to perform the
procedure.
N
Release jam
Jam N
released?
Y
End Contact next
level of support
297-2651-543 Standard 05.01 March 1999

CM JInact
minor
minor
(continued)
(end)
Clearing a CM JInact minor alarm
1 Determine if the inactive CPU system jammed or manually jammed.
system jammed step 3

manually jammed step 2
2 Maintenance personnel jammed the inactive CPU. Determine from office

records or from operating company personnel why the CPU jammed.
When you have permission, continue with this procedure.

>\RELEASE JAM
RTIF response:
JAM RELEASE DONE
If the response Do
is JAM RELEASE DONE step 5

GSP05 (CSP10)
CM LowMem
critical
Alarm display
LowMem . . . . . . . . .
*C*
Indication
At the MTC level of the MAP display, LowMem appears under the CM
header of the alarm banner. LowMem indicates a critical alarm for low
memory.
Meaning
The computing module (CM) has no spare memory left. The CM runs low
on the amount of allocated memory.
Result
The problem does not affect subscriber service. A critical switch procedure
can require additional memory for any reason. If the procedure requires and
cannot obtain additional memory, a warm or cold restart occurs.
Common procedures
Action
procedure.
297-2651-543 Standard 05.01 March 1999

CM LowMem
Summary of Clearing a CM LowMem critical alarm
Determine if a This flowchart summarizes the

defective procedure.
memory card is
present Use the instructions that follow
procedure.
Perform MemFlt
Defective alarm clearing 1
memory card? Y procedure
1 N
Claim memory
Y
CLAIM
command 2
passed?
N
Extend memory.
Refer to the
appropriate NTP.
2
N Contact next
Alarm
level of support
cleared?
End
GSP05 (CSP10)
CM LowMem
Clearing a CM LowMem critical alarm
At the MAP terminal
1 To access the memory level of the MAP display, type
>MAPCI;MTC;CM;MEMORY
Example of a MAP display for DMS SuperNode:
0 . cpu 1 . . . . . .
CM 0
1 Plane 0 C | C Plane 1 1
0987654321 P | P 1234567890
.........f U | U ..........
MEMORY:
Example of a MAP display for DMS SuperNode SE:

0 . cpu 1 . . . . . .
CM 0
Plane 0 C | C Plane 1
54321 P | P 12345
....f U | U .....
MEMORY:
2 Determine if a memory card that has faults exists .

Note: An f under the card number indicates that the card has faults.
If Do
a memory card that has faults is step 3

present
a memory card that has faults is not step 4
present
3 Perform the procedure Clearing a CM MemFlt minor alarm in this document.

Go to step 1.
297-2651-543 Standard 05.01 March 1999

CM LowMem

Note: The word ”yes” under the Jam header means that the CPU jammed.
The area is blank if the CPU did not jam.
0 no cpu 1 . . yes . . .
If the CPU Do
jammed step 7
did not jam step 5

5
CAUTION
Loss of service
the active CPU.
CAUTION
Loss of service
the active CPU.

>\JAM
RTIF response:
GSP05 (CSP10)
CM LowMem

>YES
RTIF response:
JAM DONE
At the MAP terminal

If the CM Do
is in sync step 8

>CM
9 To drop the synchronization, type

>DPSYNC
If the response Do

CPU n active. The inactive
CPU is JAMMED. Do you
want to continue? Please
confirm (”YES”, ”Y”, ”NO”,
or ”N”):

>YES
297-2651-543 Standard 05.01 March 1999

CM LowMem
If A1 Do
flashes step 12
At the MAP terminal

>MEMORY
13
CAUTION
Possible service degradation
The memory claim requires a high level of CPU
occupancy. An attempt to reclaim additional memory
while the switch runs under heavy traffic can affect
call processing.
CAUTION
occupancy. An attempt to reclaim additional
memory while the switch runs under heavy traffic
can affect call processing.
To claim additional memory, type

>CLAIM
The reclaiming of unused Data Store and Program Store to
the Spare Pool should only be done if the switch is NOT
running under heavy traffic.
Please confirm (”YES”, ”Y”, ”NO”, or ”N”):
GSP05 (CSP10)
CM LowMem

>YES
If the CLAIM command Do
passed step 15
failed step 20

>\RELEASE JAM
RTIF response:
JAM RELEASE DONE
At the MAP terminal

>CM
297-2651-543 Standard 05.01 March 1999

CM LowMem

>SYNC
If the response Do

successful
indicates the CPUs are not in sync step 18
logs again.
is Do you wish to continue?

Please Confirm(”YES”, ”Y”,
or ”NO”, ”N”)
18 (SN/ SNSE Series 70 only)

>NO
Go to step 23.
19 Determine if the LowMem critical alarm cleared.
If the alarm Do
cleared step 24
GSP05 (CSP10)
CM LowMem
(end)
20 To extend the memory, use the Memory extension in the SuperNode CM

procedure in Card Replacement Procedures. Complete the procedure and
return to this point.
21 Determine if the LowMem critical alarm cleared.
If the alarm Do
cleared step 24
297-2651-543 Standard 05.01 March 1999

CM LowSpr
major
Alarm display
LowSpr . . . . . . . . .
M
Indication
At the MTC level of the MAP display, LOWSpr appears under the CM
header of the alarm banner. The LOWSpr indicates a major alarm for low
spare memory.
Meaning
Both central processing units (CPUs) run out of available spare memory.
Result
The problem does not immediately affect subscriber service.
If a single memory fault occurs, not enough spare memory is available for
single memory fault recovery. Synchronization drops and the switch cannot
recover in sync.
Common procedures
Action
procedure.
GSP05 (CSP10)
CM LowSpr
major (continued)
Summary of Clearing a CM LowSpr major alarm
Determine if a
memory card that
procedure.
has faults is present
Y Perform MemFlt procedure.
Memory card 1
alarm clearing
have faults?
procedure
1 N
Claim memory
Y
CLAIM
command 2
passed?
N
Extend memory.
Refer to the
correct NTP.
2

End
297-2651-543 Standard 05.01 March 1999

CM LowSpr
major (continued)
Clearing a CM LowSpr major alarm
At the MAP display
0 . cpu 1 . . . . . .
CM 0
0987654321 P | P 1234567890
......f... U | U ..........
MEMORY:
Example of DMS SuperNode SE MAP display:

0 . cpu 1 . . . . . .
CM 0
54321 P | P 12345
.f... U | U .....
MEMORY:
2 Determine if a memory card that has faults is present.

Note: An f under a card number indicates that the card has defects.
If a memory card with defects Do
is present step 3
is not present step 4
3 Perform the procedure Clearing a CM MemFlt minor alarm described in this

document. Complete and return to this point.
Go to step 1.
GSP05 (CSP10)
CM LowSpr
major (continued)

0 no cpu 1 . . yes . . . .
If the CPU Do
jammed step 7
did not jam step 5

5
CAUTION
Loss of service
cold restart occurs. The word Active on the top banner
of the display identifies the reset terminal for the
active CPU.
CAUTION
Loss of service
the active CPU.

>\JAM
RTIF response:
297-2651-543 Standard 05.01 March 1999

CM LowSpr
major (continued)

>YES
RTIF response:
JAM DONE
At the MAP terminal

The word no means that the CM is not in sync. In the example in step 4, the
CM is not in sync.
If the CM Do
is in sync step 8

>CM

>DPSYNC
If the response Do

CPU n active.
The inactive CPU is
JAMMED.
”Y”, ”NO”, or ”N”):
GSP05 (CSP10)
CM LowSpr
major (continued)

>YES

If A1 Do
flashes step 12
At the MAP display

>MEMORY
13
CAUTION
call processing.
CAUTION

>CLAIM
297-2651-543 Standard 05.01 March 1999

CM LowSpr
major (continued)
MAP response:
The reclaiming of unused Data Store and Program
Store to the Spare Pool should only be done if the
switch is NOT running under heavy traffic.

>YES
passed step 15
failed step 20

>\RELEASE JAM
RTIF response:
JAM RELEASE DONE
At the MAP terminal

>CM
GSP05 (CSP10)
CM LowSpr
major (continued)

>SYNC
MAP response:
If the response Do

successful
indicates that the logs do not match. step 18
The CPUs are out of sync. Review
mismatch logs before you
synchronize the CM again
or ”NO”, ”N”)

>NO
Go to step 23.
19 Determine if the LOWSpr major alarm cleared.
If the alarm Do
cleared step 24
20 To extend the memory, use the Memory extension in the SuperNode CM

297-2651-543 Standard 05.01 March 1999

CM LowSpr
majormajor
(continued)
(end)
21 Determine if the LOWSpr major alarm cleared.
If the alarm Do
cleared step 24
22 Perform the correct procedure in this document to clear the alarm.
23 For additional help, contact the next level of maintenance support.
GSP05 (CSP10)
CM LowSpr
minor
Alarm display
LowSpr . . . . . . . . .
Indication
At the MTC level of the MAP display, LowSpr appears under the CM
header of the alarm banner. The LowSpr indicates a minor alarm for low
spare memory.
Meaning
The computing module (CM) runs out of available spare memory on one
central processing unit (CPU).
Result
This alarm can affect handshake override capability. The handshake
override increases the speed of CPU operations. The handshake override
overrides the handshake synchronization of memory access between CPUs.
This alarm can cause the fault tolerance capability to degrade.
Common procedures
This procedure refers to Activity switch with memory match.

you to go.
Action
procedure.
297-2651-543 Standard 05.01 March 1999

CM LowSpr
minor (continued)
Summary of Clearing a CM LowSpr minor alarm
Determine if a This flowchart summarizes the

memory card procedure.
that has faults
is present Use the instructions that follow
Is there a procedure.
Y Perform MemFlt
memory 1
alarm clearing
card with
procedure
faults?
1 N
Claim memory
Y
Alarm
cleared? 2
N
Extend memory.
Refer to correct
NTP.
Y
Alarm End
cleared? 2
Contact next
level of support
GSP05 (CSP10)
CM LowSpr
minor (continued)
Clearing a CM LowSpr minor alarm
At the MAP terminal
0 . cpu 1 . . . . . .
CM 0
0987654321 P | P 1234567890
.........f U | U ..........
MEMORY:
Example of DMS SuperNode SE MAP display

0 . cpu 1 . . . . . .
CM 0
54321 P | P 12345
....f U | U .....
MEMORY:
2 Determine if a memory card that has faults is present.

Note: An f under a card number indicates a card has faults.
If a defective memory card Do
is present step 3
3 Perform the procedure Clearing a CM MemFlt minor alarm in this document.

Go to step 1.
297-2651-543 Standard 05.01 March 1999

CM LowSpr
minor (continued)
4 To determine if the low spare memory (LowSpr) condition is on the active or

inactive CPU plane, type
>SPARE
Note: The plane with the lowest number of spare memory modules has the
LowSpr condition.
Plane 0 has 1 spare 8 Mbyte Modules.
The total Spare memory available is 8 Mbytes.
Plane 1 has 0 spare 8 Mbyte Modules.
The total Spare Memory available is 0 Mbytes.
If the LowSpr condition Do
is on the active CPU step 13

is on the inactive CPU step 5

Note: The word yes under the Jam header at the CM level of the MAP display
means that the CPU jammed. The area is blank if the CPU did not jam.

0 no cpu 1 . . yes . . . .
If the CPU Do
jammed step 8
did not jam step 6
GSP05 (CSP10)
CM LowSpr
minor (continued)
6
CAUTION
Loss of service
Make sure you do not jam the active CPU. If you jam
the active CPU while the CM is not in sync, a cold
restart occurs. The word Active on the top banner of
the display identifies the reset terminal for the active
CPU.
CAUTION
Loss of service
Make sure you do not jam the active CPU. If you
the active CPU.

>JAM
RTIF response:

>YES
RTIF response:
JAM DONE
At the MAP display

297-2651-543 Standard 05.01 March 1999

CM LowSpr
minor (continued)
The word ”no” means that the CM is not in sync. In the example in step 5, the
CM is not in sync.
If the CM Do
is in sync step 9

>CM

>DPSYNC
and pressing the Enter key.
If the response Do

CPU n active.
The inactive CPU is
JAMMED.
”Y”, ”NO”, or ”N”):

>YES

GSP05 (CSP10)
CM LowSpr
minor (continued)
If A1 Do
flashes step 14
13 Perform the procedure Activity switch with memory match in this document.
At the MAP terminal
>MEMORY
15
CAUTION
call processing.
CAUTION

>CLAIM
297-2651-543 Standard 05.01 March 1999

CM LowSpr
minor (continued)
MAP response:
The reclaiming of unused Data Store and Program Store to
the Spare Pool should only be done if the switch is NOT
running under heavy traffic.

>YES
passed step 17
failed step 22

>\RELEASE JAM
RTIF response:
JAM RELEASE DONE
At the MAP terminal

>CM

>SYNC
GSP05 (CSP10)
CM LowSpr
minor (continued)
If the response Do

successful
logs again.
or ”NO”, ”N”)
(SN/ SNSE series 70 only)

>NO
Go to step 25.
21 Determine if the LowSpr minor alarm cleared.
If the alarm Do
cleared step 26
22 To extend the memory, perform the Memory extension in the SuperNode CM

297-2651-543 Standard 05.01 March 1999

CM LowSpr
minor
minor
(continued)
(end)
23 Determine if the LowSpr minor alarm cleared.
If the alarm Do
cleared step 26
24 Perform the correct alarm clearing procedures in this document.
GSP05 (CSP10)
CM MBsyMC
major
Alarm display
MBsyMC . . . . . . . . .
M
Indication
At the MTC level of the MAP display, MBsyMC appears under the CM
header of the alarm banner. The MBsyMC indicates a major alarm for a
manual busy message controller.
Meaning
Maintenance personnel manually busy a message controller (MC).
Result
The problem does not affect subscriber service. Failure of the last MC
results in the loss of subscriber service.
Common procedures
Action
procedure.
297-2651-543 Standard 05.01 March 1999

CM MBsyMC
major (continued)
Summary of Clearing a CM MBsyMC major alarm
Test affected This flowchart summarizes the

MC procedure.

Y this flowchart to perform the
TST procedure.
command 1
passed?
N
Test the
associated SSC
N N
TST Replace NT9X22 Retest SSC TST
command card. Refer to the command 3
passed? correct NTP. passed?
2 Y 2 Y
Test the MC
again
N
TST N Replace cards. Test MC TST
command Refer to the command 3
passed? correct NTP. passed?
1 Y 1 Y
4
Return the MC N
to service Contact next
Alarm
3 level of support
cleared?
4
Y
End
GSP05 (CSP10)
CM MBsyMC
major (continued)
Clearing a CM MBsyMC major alarm
At the MAP terminal
>MAPCI;MTC;CM;MC
CM 0
MC 0 MC 1
. mbsy
2 Record the number of the manual busy MC.

for the removal of the MC from service.
4 To test the manual busy MC, type

>TST mc_number
where
mc_number is the number of the manual busy MC (0 or 1) that you
recorded in step 2
passed step 16
card list
297-2651-543 Standard 05.01 March 1999

CM MBsyMC
major (continued)
5 To access the clock level of the MAP display, type

>CLOCK
T O D
MC0 MC1
Link 0 . manb
Link 1 . manb
SSC . oos
6 To test the manual busy SSC, type

>TST SSC ssc_number
where
ssc_number is the SSC for the manual busy MC (0 or 1) that you recorded
in step 2
passed step 9
failed, and the system generated step 7
card list generates
7 To replace the NT9X22 card, perform the correct card procedure in Card
Replacement Procedures. Complete the procedure and return to this point.
GSP05 (CSP10)
CM MBsyMC
major (continued)
8 To test the manual busy SSC again, type

>TST SSC ssc_number
where
ssc_number is the SSC for the manual busy MC (0 or 1) that
you recorded in step 2
passed step 9
9 To quit from the clock level of the MAP display, type

>QUIT
10 To test the manual busy MC again, type

>TST mc_number
where
mc_number is the number of the manual busy MC (0 or 1) that you
recorded in step 2
passed step 16
card list

297-2651-543 Standard 05.01 March 1999

CM MBsyMC
major (continued)

>CM;MC

>TST mc_number
where
passed step 16
cards on the list
failed, and you replaced all cards on step 27
the list
card on the list.
Go to step 12.

>RTS mc_number
where
passed step 17
failed step 27
GSP05 (CSP10)
CM MBsyMC
major (continued)
17 Determine if the inactive CM plane powered down.
If the inactive CM plane Do


>CM;TST
Static RAM test


>YES
Test passed.
passed step 20
failed step 27
297-2651-543 Standard 05.01 March 1999

CM MBsyMC
major (continued)

jammed step 21
did not jam step 22

>\RELEASE JAM
RTIF response:
JAM RELEASE DONE
At the MAP terminal

0 no cpu 1 . . no . . . .
If the CM Do
is in sync step 25
GSP05 (CSP10)
CM MBsyMC
major (continued)

>SYNC
If the response Do

successful
caused by a problem with
logs again.
Please confirm (”YES”, ”Y”
or ”NO”, ”N”)

>NO
Go to step 27.
25 Determine if the MBsyMC main alarm cleared.
If the alarm Do
cleared step 28
297-2651-543 Standard 05.01 March 1999

CM MBsyMC
majormajor
(continued)
(end)
GSP05 (CSP10)
CM MC Tbl
minor
Alarm display
MC Tbl . . . . . . . . .
Indication
At the MTC level of the MAP display, MC Tbl appears under the computing
module (CM) header of the alarm banner. The MC Tbl indicates a minor
alarm for message controller trouble.
Meaning
A minimum of one message controller (MC)
• is in-service trouble
• has a subsystem clock (SSC) fault
• has a time-of-day (TOD) clock fault
Result
The problem does not now affect subscriber service. If problems develop on
the second MC, communications with one or both message switches can
end.
Common procedures
Action
procedure.
297-2651-543 Standard 05.01 March 1999

CM MC Tbl
minor (continued)
Summary of Clearing a CM MC Tbl minor alarm
Determine type This flowchart summarizes the

of fault procedure.
displayed
Does either Test clock procedure.
Y
clock have 1
faults?
N
Test affected
MC port
TST N Replace cards. TST N Replace cards.

command Refer to the 3 command Refer to the 2
passed? correct NTP. passed? correct NTP.
Y
3 Y 2 Y
N Contact next Return clock to

Alarm service
level of support
cleared?
Y 3
End
GSP05 (CSP10)
CM MC Tbl
minor (continued)
Clearing a CM MC Tbl minor alarm
At the MAP terminal
>MAPCI;MTC;CM;MC
CM 0
MC 0 MC 1
. istb
2 Determine the type of fault that causes the alarm.

Note: The fault indicator appears under the MC 0 and MC 1 headers of the
MAP display. In the example in step 1, the fault indicator for MC 1 is istb.
If the fault indicator Do
is istb step 3
is todf step 11
is sscf step 14
3 To access the port level of the MAP display, type

>PORT
P O R T
MC 0 MC 1
Link 0 . oos
Link 1 . .
297-2651-543 Standard 05.01 March 1999

CM MC Tbl
minor (continued)
4 To test the MC port that has faults, type

>TST mc_number link_number
where
mc_number is the number of the MC (0 or 1) that has in-service trouble
link_number is the number of the link (0 or 1) that is out of service
Note: In the example in step 1, MC 1 has in-service trouble. In the example in
step 3, link 0 of MC 1 is out of service.
In service port test passed.
1000 messages sent, 1000 messages received.
passed step 28
card list

7 To access the port level of the MAP display, type

>MC;PORT
GSP05 (CSP10)
CM MC Tbl
minor (continued)
8 To test the MC port, type

>TST mc_number link_number
where
link_number is the number of the link that was out of service (0 or 1)
passed step 28
cards on the list
the list
card on the list.
Go to step 6.
10 Perform the procedure Clearing an MS CMIC minor alarm in this document.

Go to step 28.

>CLOCK
CM 0
MC 0 MC 1
. todf
TOD
MC0 MC1
Link 0 . flt
Link 1 . .
SSC . .
297-2651-543 Standard 05.01 March 1999

CM MC Tbl
minor (continued)
12 Record the number of the MC that has the TOD fault, and the number of the
TOD clock that has faults.
Note: In the example in step 11, MC 1 has the TOD clock fault. The link
number of the TOD clock that has faults is 0.
13 To test the TOD clock that has faults, type

>TST TOD mc_number link_number
where
mc_number is the number of the MC (0 or 1) that has a TOD clock fault
link_number is the link number (0 or 1) of the damaged TOD clock
Maintenance action Submitted
MC 0 TOD 0 test passed.
passed and alarm cleared step 42

passed and TOD status is OK but step 28
alarm not cleared
passed but TOD status is not OK step 26
failed step 18

>CLOCK
TOD
MC0 MC1
Link 0 . .
Link 1 . .
SSC . flt
GSP05 (CSP10)
CM MC Tbl
minor (continued)
15 Record the number of the MC that has the SSC fault, and the number of the
SSC that has faults.
Note: In the example in step 14, MC 1 has the SSC fault. The number of the
SSC that has faults is 1.
16 To test the SSC that has faults, type

>TST SSC ssc_number
where
ssc_number is the number of the SSC that has faults (0 or 1)
A complete test will include temporary loss of two links.
Please Confirm (”YES”, ”Y”, ”NO”, or ”N”):

>YES
passed step 27
card list
18 Record the location, description, slot number, PEC, and PEC suffix of the first
card on the list.


>MC;CLOCK
297-2651-543 Standard 05.01 March 1999

CM MC Tbl
minor (continued)
21 Determine the type of cleared clock fault.

Note: A fault indicator that was todf in step 2 indicates a cleared TOD clock
fault. A fault indicator that was sscf step 2 indicates a cleared SSC fault.
If the cleared fault Do
is todf step 22
is sscf step 23
22 To test the TOD clock, type

>TST TOD mc_number link_number
where
link_number is the link number of the tested TOD clock (0 or 1)
Maintenance action Submitted
MC 0 TOD 0 test passed.
passed step 26
cards on the list
the list
GSP05 (CSP10)
CM MC Tbl
minor (continued)
23 To test the SSC, type

>TST SSC ssc_number
where
ssc_number is the number of the tested SSC (0 or 1)
A complete test will include temporary loss of two links.
Please Confirm (”YES”, ”Y”, ”NO”, or ”N”):

>YES
passed step 27
cards on the list
the list
card on the list.
Go to step 19.
26 To return the TOD clock to service, type

>RTS TOD mc_number link_number
where
link_number is the link number (0 or 1) of the TOD clock that you returned to
service
297-2651-543 Standard 05.01 March 1999

CM MC Tbl
minor (continued)
passed step 28
failed step 41
27 To return the SSC to service, type

>RTS SSC ssc_number
where
ssc_number is the number of the SSC that you returned to service (0 or 1)
passed step 28
failed step 41

>MC
CM 0
MC 0 MC 1
. mbsy
29 Determine if the accessed MC is manual busy.

Note: If an MC is manual busy, mbsy appears under the MC 0 or MC 1 header.
If the MC Do
is mbsy step 30
is not mbsy step 31
GSP05 (CSP10)
CM MC Tbl
minor (continued)

>RTS mc_number
where
passed step 31
failed step 41


>CM;TST
Static RAM test

297-2651-543 Standard 05.01 March 1999

CM MC Tbl
minor (continued)

>YES
Test passed.
passed step 34
failed step 41

jammed step 35
did not jam step 36

>\RELEASE JAM
RTIF response:
JAM RELEASE DONE
GSP05 (CSP10)
CM MC Tbl
minor (continued)
At the MAP terminal
If the CM Do
is in sync step 39

>SYNC
If the response Do

successful
logs again.
or ”NO”, ”N”)
38 (SN/ SNSE series 70 only)

>NO
Go to step 41.
297-2651-543 Standard 05.01 March 1999

CM MC Tbl
minor
minor
(continued)
(end)
39 Determine if the MC Tbl minor alarm cleared.
If the alarm Do
cleared step 42
GSP05 (CSP10)
CM MemCor
major
Alarm display
MemCor . . . . . . . . .
M
Indication
At the MTC level of the MAP display, MemCor appears under the CM
header of the alarm banner. The MemCor indicates a major alarm with an
adjustable memory fault.
Meaning
A high number of adjustable memory faults occurred in a given time for a
given memory module, memory card, or surface. You can expect a fixed
rate of adjustable memory faults in normal switch operation. Excess of this
rate causes MemCor to initiate. The excess is an indication of a damaged
module, card, or surface.
Result
The mismatch handler isolated the hardware element with the fault. The
mismatch handler also synchronized the switch again. The card(s) affected
appear at the memory level of the MAP display with a mark of IsTb. The
problem does not affect switch operation. The purpose of the alarm is to
indicate that the hardware is the cause of a high number of mismatches. The
alarm indicates that the hardware requires replacement.
Common procedures
Action
procedure.
297-2651-543 Standard 05.01 March 1999

CM MemCor
major (continued)
Summary of Clearing a CM MemCor major alarm

procedure.
Obtain a copy
of the MFC111 Use the instructions that follow
log this flowchart to perform the
procedure.
Suspect Y Replace card

module? that contains
module
Suspect Y Replace suspect

card? card
N
Suspect plane
Replace CPU Contact next Perform

and terminator level of support SWAPHW
card on plane command
Perform
CLRALARM
command
End
GSP05 (CSP10)
CM MemCor
major (continued)
Clearing a CM MemCor major alarm
At the current location
1 Obtain a duplicate of the MFC111 log report generated at the same time as the
MemCor alarm. Refer to Log Report Reference Manual for a description of this
log.
2 Identify the value of the field <threshold_type>. This field has the value
“module”, “card”, or “plane”. The field indicates the suspect hardware element.
If the MFC111 log Do
indicates a suspect module step 3

indicates a suspect card step 5
indicates a suspect plane step 10
Note: A card has three memory modules. A memory module is on a card. A

suspect memory module requires replacement of the card.
3 Consult the log report. Identify the type and location of the card that requires
replacement. The card is an NT9X14DB or NT9X14EA.
4 Go to step 6.
5 Consult the log report. Identify the type and location of the card that requires
6 Refer to the correct procedure in Card Replacement Procedures and replace

the card in question.
At the MAP display
7
CAUTION
Keeping the mismatch database up to date.
Keep the mismatch database up to date. Make sure
that you inform the database of card changes through
the SWAPHW command. If you do not keep the
database up to date, the mismatch software cannot
diagnose later mismatches correctly.
297-2651-543 Standard 05.01 March 1999

CM MemCor
major (continued)
CAUTION
the SWAPHW command. If you do not keep the
database up to date, the mismatch software cannot
diagnose later mismatches correctly.
To notify the maintenance software system of the card replacement, type

>SWAPHW SLOT <shelf> <slot> <side>
where
shelf is the shelf number of the replaced card
slot is the slot number of the replaced card
side is the side number of the replaced card

WARNING: You have indicated that the following circuit
pack has been replaced. Please verify that the
following list accurately reflects the
location of the replaced circuit pack, and
that the displayed PEC code matches the pack
currently equipped in that slot:
Site Flr RPos Bay_id shf Description Slot EqPEC
<site><flr><rpos><bay> <shf> <desc> <slot> <pec> <side>

Please confirm (”YES”, ”Y”, ”NO”, ”N”):
8 To confirm, type
>YES
Card replacement has been recorded.
9 Go to step 14.
GSP05 (CSP10)
CM MemCor
major (continued)
10 Identify from the log report the suspect plane.

Note: As a first attempt to fix the plane that has faults, replace the CPU card
(NT9X10 or NT9X13). Also replace the terminator card (NT9X21).
Refer to the correct procedures in Card Replacement Procedures. Replace the
CPU and the terminator cards on the plane in question.
11 Notify the next level of support that a MemCor alarm occurred for a plane. If
you replaced the terminator and CPU cards on this plane, the next level of
support can investigate the problem.
At the MAP
12
CAUTION
Keep the mismatch database up to date. Inform the
database of card changes through the SWAPHW
command. If you do not keep the database up to date,
the mismatch software cannot diagnose later
mismatches correctly.
CAUTION
Keep the mismatch database up to date. Inform the
database of card changes through the SWAPHW
command. If you do not keep the database up to
date, the mismatch software cannot diagnose later
mismatches correctly.

>SWAPHW plane

WARNING: All ”Memory Fault, Correctable” history will
be deleted during the next manual sync
attempt. The PLANE option of this command
should be used only during manual recovery
from a MFC Plane threshold being exceeded.
297-2651-543 Standard 05.01 March 1999

CM MemCor
majormajor
(continued)
(end)
13 To confirm, type
>YES
14 To begin to clear the MemCor alarm, type

>CLRALARM MemCor
The MemCor alarm will be cleared.
Please confirm (”YES”, ”Y”, ”NO”,
”N”):
15 To clear the MemCor alarm, type

>Y
The MemCor alarm has been cleared.
Note: A generated CM176 log indicates that the alarm cleared
GSP05 (CSP10)
CM MemCfg
minor
Alarm display
MemCfg . . . . . . . . .
M
Indication
At the CM level of the MAP display, MemCfg appears under the CM header
of the alarm banner. The MemCfg indicates a minor alarm for the wrong
memory configuration.
Meaning
The computing module (CM) maintenance detects a memory card
configuration that is not correct on one of the CM planes.
Result
Mismatches can occur which result in a power failure. CM operation that is
not the same can result in a power failure.
Common procedures
Application
The following figures illustrate the correct position of memory cards for the
SN50MX product.
297-2651-543 Standard 05.01 March 1999

CM MemCfg
minor (continued)
Figure 1xxx
Configuration of SN50MX product with two NT9X14EA 96M memory cards
FRONT VIEW
CPU 0 CPU 1
NT9X14DB
NT9X14DB
NT9X14DB
NT9X14DB
NT9X14DB
NT9X14DB
NT9X14DB
NT9X12AD
NT9X12AD
NT9X12AD
NT9X12AD
NT9X14DB
NT9X14DB
NT9X14DB
NT9X14DB
NT9X14DB
NT9X14DB
NT9X14DB
NT9X10AA
NT9X10AA
NT9X14DB
NT9X14DB
NT9X14EA
NT9X14EA
NT9X14EA
NT9X14EA
Slot 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32
numbers
Note 1: Slots 11-16 and 23-28 contain the mandatory minimum memory configuration,
when two NT9X14EA (96 Mbyte) cards are used.
Note 2: Slots 07-10 and 29-32 contain optional memory extension by up to four NT9X14DB
(24 Mbyte) cards.
GSP05 (CSP10)
CM MemCfg
minor (continued)
Figure 2xxx
Configuration of SN50MX product with three NT9X14EA 96M memory cards
FRONT VIEW
CPU 0 CPU 1
Filler faceplate
Filler faceplate
Filler faceplate
Filler faceplate
NT9X14DB
NT9X14DB
NT9X14DB
NT9X14DB
NT9X14DB
NT9X12AD
NT9X12AD
NT9X12AD
NT9X12AD
NT9X14DB
NT9X14DB
NT9X14DB
NT9X14DB
NT9X14DB
NT9X10AA
NT9X10AA
NT9X14EA
NT9X14EA
NT9X14EA
NT9X14EA
NT9X14EA
NT9X14EA
Slot 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32
numbers
Note 1: Slots 12-16 and 23-27 contain the mandatory minimum memory configuration,
when three NT9X14EA (96 Mbyte) cards are used.
Note 2: Slots 09-11 and 28-30 contain optional memory extension by up to three NT9X14DB
(24 Mbyte) cards.
Action
procedure.
297-2651-543 Standard 05.01 March 1999

CM MemCfg
minor (continued)
Summary of Clearing a CM MemCfg minor alarm

procedure.

procedure.
Y
Y Check correct Any process
Determine if
1 memory 2
CM is in sync errors?
configuration
N
N
Maintenance Memory Are there Replace or change

Y Confirm
since last configuration any proc. 1 cards. See
configuration
sync? performed errors appropriate NTP
N
N
1 Alarm
clear? 2
Y
2
Contact next End

level of support
GSP05 (CSP10)
CM MemCfg
minor (continued)
Clearing a CM MemCfg minor alarm
At the MAP terminal
>MAPCI; MTC; CM; MEMORY
Example of SN MAP display
0 . cpu 1 . . . . . .
CM 0 Plane 0 Plane 1
1 | 1
0987654321 P | P 1234567890
----...... - - ......----

If the CM Do
is in SYNC step 3
is not in SYNC step 7
297-2651-543 Standard 05.01 March 1999

CM MemCfg
minor (continued)
3 To check the two CM planes for wrong memory configurations, type

>QRYMEM
Note: Responses to the QRYMEM command are for the two planes.
The following are possible responses:
• a memory configuration result (valid or invalid)
• a possible processor optionality that is not consistent or error warning
• a possible out of sync warning (for the inactive plane only)
• if the memory configuration of the plane is wrong, the system provides a
description of the wrong configuration
0 No cpu 0 . . MemCfg . .
1 1
0987654321 P | P 1234567890
----...... - - -..-------
MEMORY:
>QRYMEM
CPU 0 has a valid memory configuration
CPU 1 has an invalid memory configuration
WARNING: The CM is out of sync with the CPU 0 active.
The data for CPU 1 may be out of date.
Empty slots found between the outer port card
(NT9X12AC) and the first memory card. Move memory
cards so that memory grows away from the processor.
GSP05 (CSP10)
CM MemCfg
minor (continued)
4 Check for responses to the QRYMEM command. The responses are warning
responses for processor optionality.
If the response Do
shows processor optionality step 5

inconsistency
shows processor optionality step 28
error
shows no warning step 5
5 Check for No Sync warning responses to the QRYMEM command as follows:
If the response Do
shows the CM is out of sync step 7

shows no warning step 6
6 Review the correct configuration responses as the table indicates.
If the response Do
is CPU 0 has an invalid step 10

There are empty slots
between memory cards.
Empty slots between
the outer port card <n>
and the first memory
card.
memory configuration
The NT9X14DB and
NT9X14EA cards are
intermixed.
—continued—
297-2651-543 Standard 05.01 March 1999

CM MemCfg
minor (continued)
If the response Do

The block of NT9X14DB
cards are closest to
the processor.
There are too many
<memory type> cards
present on CPU <n>.
There are too few
<memory type> cards
present on CPU <n>. On
the SN50MX platform, a
minimum memory
configuration consists of
2 NT9X14EA’s
and 4 NT9X14DB’s or 3
NT9X14EA’s and 2
NT9X14DB’s
There are too many
NT9X14DB cards
present on CPU <n>. There
should be a maximum of <n>
NT9X14DB’s on a CPU plane
with <n> NT9X14EA cards
—continued—
GSP05 (CSP10)
CM MemCfg
minor (continued)
If the response Do

There are too few
<memory type> cards
present on CPU <n>.
There are too few
NT9X14DB memory cards
present on CPU <n>. There
should be a minimum of <n>
NT9X14DB on a CPU plane
with <n> NT9X14EA cards
—continued—
297-2651-543 Standard 05.01 March 1999

CM MemCfg
minor (continued)
If the response Do
is No reply from request step 19

is Software difference action step 20
cancelled.
is CPU <n> has an invalid step 21
The internal <component>
inventory tables are
corrupt.
The <component> PEC <pec>
is not recognized.
The memory PEC <pec> is
not supported by Processor
Option.
This platform does not
support mixed memory.
is no mailbox available. step 25
is both CPU’s have valid step 27
configuration.
—end—
7 Consult office records. Determine if maintenance was on the CM from the time
the CM was last in sync. Determine if a memory configuration was performed.
If the answer Do
is yes step 8
is no step 6
GSP05 (CSP10)
CM MemCfg
minor (continued)
8 To configure the memory to make sure that the inactive memory configuration
data is up to date, type
>CONFIG
Example of MAP display
WARNING:
I will now ask the mate CPU to re-configure its
memories. I will take the new configuration data and
re-build the MEMORY MAP display for the inactive CPU
memory cards. This must only be done when out of SYNC
and during a memory extension or reduction (adding or
deleting a memory card or replacing a memory card with
one of a different PEC code).
Please confirm (”YES or ”Y”, ”NO” or ”N”)

>YES
Example of MAP display
Maintenance action submitted
If the response Do
indicates the CONFIG command step 3

passed
indicates the CONFIG command step 28
failed
indicates Configure aborted. step 28
NT9X14BB memory is
incompatible with NT9X14EA
memory
297-2651-543 Standard 05.01 March 1999

CM MemCfg
minor (continued)
At the switch
10 Empty memory slots are between the memory cards.
Compare the design of the CPU with the diagram at the end of this procedure.
Note the differences in card positions.
To move the memory cards to fill the empty slots, perform the correct procedure
in Card Replacement Procedures. Complete the procedure and return to this
point.
Note: To achieve the desired result, move the least number of memory cards.
Go to step 26.
11 Empty slots are between the outer port card and the first memory card. Mixed
memory on the CM must grow out from the processor with all empty slots on
the ends of each plane.
Compare the configuration of the CPU with the diagram at the end of this
procedure. Note the differences in card positions.
Move the memory cards in order to fill the empty slots. Perform the correct
Note: To achieve the desired result, move the least number of memory cards.
Go to step 26.
12 The memory cards mix together. Keep the NT9X14EA and NT9X14DB cards
as continuous sets. Keep the NT9X14EA set nearest to the processor, followed
by the NT9X14DB set.
Move the memory cards so that they do not mix together and the NT9X14EA
cards are nearest to the processor. Perform the correct procedure in Card
Note: Empty slots should not be present between the memory cards.
Go to step 26.
GSP05 (CSP10)
CM MemCfg
minor (continued)
13 The NT9X14DB cards are nearest to the processor. Keep the NT9X14EA and
NT9X14DB cards as continuous sets. Keep the NT9X14EA set nearest to the
processor, followed by the NT9X14DB set.
Move the memory cards so that the NT9X14EA cards are nearest to the
processor. Perform the correct procedure in Card Replacement Procedures.
Note: Empty slots should not be present between the memory cards.
Go to step 26.
14 Too many memory cards of a given memory type are on the plane.
Reduce number of memory cards of an indicated type to equal or be less than
the indicated limit. Perform the correct procedure in Card Replacement
Procedures. Complete the procedure and return to this point.
Go to step 26.
15 Not enough memory cards of a given type are on the plane.

Decrease the number of NT9X14DB cards on the plane to equal or be greater
than the indicated limit. Perform the the correct procedure in Card
Go to step 26.
16 Not enough memory cards of a given type are on the plane. On the SN50MX
platform, a minimum memory configuration has two NT9X14EA cards and four
NT9X14DB cards. A minimum memory configuration also can have three
NT9X14EA cards and two NT9X14DB cards.
Increase the number of memory cards of the indicated type in order to conform
to a supported configuration. Perform the correct procedure in Card
Note: This response is for the SN50MX platform.
Go to step 26.
297-2651-543 Standard 05.01 March 1999

CM MemCfg
minor (continued)
17 Too many NT9X14DB cards are on the plane. A maximum number of

NT9X14DB cards is on a CPU plane with a given number of NT9X14EA cards.
Reduce the number of memory cards of an indicated type in order to equal or
be less than the indicated limit. Perform the correct procedure in Card
Go to step 26.
18 Not enough NT9X14DB cards are on the plane. A minimum number of both
NT9X14DB cards are on a CPU plane with a given number of NT9X14EA
cards.
Increase the number of NT9X14DB cards on the plane in order to equal or be
less than the indicated limit. Perform the correct procedure in Card
Go to step 26.
19 The QRYMEM command expired and cancelled.

Go to step 28.
20 Software is not compatible - action cancelled.

Go to step 28.
21 The internal CPU or memory tables have defects.

Go to step 28.
22 The QRYMEM command found a PEC code that the command does not
recognize in the internal software inventory tables.
If the information is correct, and the PEC described is present on the indicated
plane, remove the card from the shelf. To replace the card with the correct
card, perform the correct procedure in Card Replacement Procedures.
Go to step 26.
23 The QRYMEM command found a memory card that the current configuration
does not support.
Remove the card from the shelf. To replace the card with the correct card,
perform the correct procedure in Card Replacement Procedures. Complete the
Go to step 26.
GSP05 (CSP10)
CM MemCfg
minor (continued)
24 The QRYMEM command found multiple memory types on a platform that does
not support mixed memory.
To configure the memory design again with a single memory type, add or
replace cards. Perform the correct card procedure in Card Replacement
Go to step 26.
25 An internal software error occurred.

Go to step 28.
At the MAP display
26 To check both CM planes for wrong memory configurations, type
>QRYMEM

0 cpu 0 . . . .
1 1
0987654321 P | P 1234567890
----...... - - -..-------
MEMORY:
>QRYMEM
CPU 0 has a valid memory configuration
CPU 1 has an valid memory configuration
27 Determine if the CM MemCfg minor alarm cleared.
If the alarm Do
cleared step 29
297-2651-543 Standard 05.01 March 1999

CM MemCfg
minor
minor
(continued)
(end)
GSP05 (CSP10)
CM MemCor
minor
Alarm display
MemCor . . . . . . . . .
Indication
At the MTC level of the MAP display, MemCor appears under the
computing module (CM) header of the alarm banner. The MemCor
indicates an adjustable minor alarm for the memory fault.
Meaning
A correctable memory fault occurred. The switch attempts to correct the
fault. Correction of the fault clears the alarm. A memory fault alarm occurs
if the fault remains.
Result
Common procedures
Action
procedure.
297-2651-543 Standard 05.01 March 1999

CM MemCor
minor (continued)
Summary of Clearing a CM MemCor minor alarm
Access the This flowchart summarizes the

MTC level of procedure.
the MAP display
Changed Perform procedure.
Y
to another appropriate alarm
alarm? clearing procedure
N
Alarm N Contact next level
cleared? of support
Y
End
GSP05 (CSP10)
CM MemCor
minor (continued)
(end)
Clearing a CM MemCor minor alarm
At the MAP terminal

1 To access the MTC level of the MAP display, type
>MAPCI;MTC
MAPCI:
MTC:
2 Wait for the MemCor minor alarm to clear.
If the alarm Do
clears step 6
does not clear within 6 h step 4
changes to another alarm step 3
3 Perform the correct CM alarm clearing procedure in this document.
4 The system failed to clear the memory faults. Obtain copies of the associated
CM and MM log reports.
297-2651-543 Standard 05.01 March 1999

CM MemFlt
minor
Alarm display
MemFlt . . . . . . . . .
Indication
At the MTC level of the MAP display, MemFlt appears under the computing
module (CM) header of the alarm banner. MemFlt indicates a correctable
major alarm for the memory fault.
Meaning
In a given time, a memory module, memory card, or plane has correctable
memory faults which exceed a fixed number. You can expect a fixed rate of
correctable memory faults in normal switch operation. If the number of
faults exceeds the fixed rate of faults, MemFlt appears. The exceeded rate is
also an indication of a module, card, or plane that has faults.
Result
The mismatch handler isolated the hardware element that has faults and
synchronized the switch again. The card(s) affected are marked FLT at the
memory level of the MAP display. The problem does not affect switch
operation. The alarm indicates that the hardware is the cause of a high
number of mismatches. The alarm also indicates the hardware requires
replacement.
Common procedures
Action
procedure.
GSP05 (CSP10)
CM MemFlt
minor (continued)
Summary of Clearing a CM MemFlt minor alarm

procedure.
Obtain a copy
of the MFC111 Use the instructions that follow
log this flowchart to perform the
procedure.
Y Replace card
Suspect that contains
module? module
Suspect Y Replace suspect

card? card
N
Suspect plane
Replace CPU Contact next Perform

and terminator level of support SWAPHW
card on plane command
End
297-2651-543 Standard 05.01 March 1999

CM MemFlt
minor (continued)
Clearing a CM MemFlt minor alarm
1 Obtain a duplicate of the MFC111 log report generated when the MemFlt alarm
occurred. Refer to Log Report Reference Manual for a description of this log.
2 In the MFC111 log, identify the value of the field <threshold_type>. This field
has the value “module”, “card”, or “plane” and indicates the suspect hardware
elements.
If the MFC111 log Do
indicates a suspect module step 3

indicates a suspect card step 5
indicates a suspect plane step 9
Note: Three memory modules are on a card. A suspect memory module

indicates that the card requires replacement.
3 Identify from the log report the type and location of the card that requires
4 Go to step 6.
5 Identify from the log report the type and location of the card that requires
6 Refer to the correct procedure in Card Replacement Procedures.. Replace the

suspect card.
At the MAP display
7
CAUTION
Keep the mismatch database up to date.
the SWAPHW command. Make sure the database is
up to date so the mismatch software can diagnose later
mismatches.
GSP05 (CSP10)
CM MemFlt
minor (continued)
CAUTION
up to date so the mismatch software can diagnose
later mismatches.

>SWAPHW SLOT <shelf> <slot> <side>
where
shelf is the shelf number of the card that you replaced
slot is the slot number of the card that you replaced
side is the side number of the card that you replaced

pack has been replaced. Please verify that the
following list accurately reflects the
location of the replaced circuit pack, and
that the displayed PEC code matches the pack
currently equipped in that slot:
Site Flr RPos Bay_id shf Description Slot EqPEC
<site><flr><rpos><bay> <shf> <desc> <slot> <pec> <side>

Please confirm (”YES”, ”Y”, ”NO”, ”N”):
8 To confirm, type
>YES
Card replacement has been recorded.
9 Go to step 14
297-2651-543 Standard 05.01 March 1999

CM MemFlt
minor (continued)
10 Identify the suspect plane from the log report.

Note: As a first attempt to fix the plane that has faults, replace the CPU card
(NT9X10 or NT9X13) and the terminator card (NT9X21).
Refer to the correct procedures in Card Replacement Procedures Replace the
CPU and the terminator cards on the suspect plane.
11 Notify the next level of support that a MemFlt alarm occurred for the plane. A
recent replacement of the terminator and CPU cards means that the next level
of support can investigate the problem.
At the MAP
12
CAUTION
up to date so the mismatch software can diagnose later
mismatches.
CAUTION
up to date so the mismatch software can diagnose
later mismatches.

>SWAPHW plane
WARNING: All ”Memory Fault, Correctable” history will
be deleted during the next manual sync
attempt. The PLANE option of this command
should be used only during manual recovery
from a MFC Plane threshold being exceeded.
GSP05 (CSP10)
CM MemFlt
minor (continued)
(end)
13 To confirm, type
>YES
297-2651-543 Standard 05.01 March 1999

CM MemLim
minor
Alarm display
MemLim . . . . . . . . .
M
Indication
At the CMMNT level of the MAP display, MemLim appears under the
computing module (CM) header of the alarm banner. The MemLim
indicates a minor alarm for the memory limit.
Meaning
The memory allocation to the operating system reached approximately 90%
of the limit for the given platform.
Result
Problems with operations can be present.
Common procedures
Action
procedure.
GSP05 (CSP10)
CM MemLim
minor (continued)
Summary of Clearing a CM MemLim minor alarm
Obtain CM This flowchart summarizes the

logs procedure.

level of support
End
297-2651-543 Standard 05.01 March 1999

CM MemLim
minor
minor
(continued)
(end)
Clearing a CM MemLim minor alarm
At the MAP display
GSP05 (CSP10)
CM NoBrst
minor
Alarm display
NoBrst . . . . . . . . .
Indication
At the MTC level of the MAP display, NoBrst appears under the computing
module (CM) header of the alarm banner. At the CM level of the MAP
display, noB appears in status fields for both central processing units
(CPUs).
Meaning
The system disabled burst mode operation.
This alarm occurs for one of the following reasons:

• Synchronization of the (CM). The system always disables burst mode
during the part of synchronization when the CM operates in memory
update mode
• Synchronization of the CM by the command SYNC NOBURST
• Synchronization of the CM with the burst mode enabled on the active
CPU. The CM does not have support on the inactive CPU
Result
During periods of high call processing activity, call-start failures can occur.
Common procedures
Action
procedure.
297-2651-543 Standard 05.01 March 1999

CM NoBrst
minor (continued)
Summary of Clearing a CM NoBrst minor alarm
Determine if CM This flowchart summarizes the

is synchronizing procedure.

N this flowchart to perform the
procedure.
CM
1
synchronizing?
Y
Wait until
synchronization
completes
Alarm Y
cleared?
1 N
Drop
synchronization and
synchronize again
Alarm Y
cleared?
N
Record CM memory
and processor card
configuration
Contact next End

level of support
GSP05 (CSP10)
CM NoBrst
minor (continued)
Clearing a CM NoBrst minor alarm
At the MAP terminal
>MAPCI;MTC;CM
0 no cpu 1 ut . yes . . . .
2 Determine if the CM is in synchronization .

If the CM is in synchronization, the following status indicators appear in the
alarm banner. The status indicators disappear as synchronization progresses:
• under test (ut) under the CPU0 or CPU1 header
• InStp under the CM header
• ut under the Memory header
If the CM Do
is synchronizing step 3
is not synchronizing step 5
3 Wait until synchronization is complete. Determine if synchronization was

successful.
Note: If synchronization is complete, a dot or EccOn appears under the Sync
header. The response synchronization successful appears on the right of the
command menu.
If the response Do
indicates synchronization was step 4

successful
indicates synchronization failed step 18
297-2651-543 Standard 05.01 March 1999

CM NoBrst
minor (continued)
4 Determine if the CM NoBrst minor alarm cleared.
If the alarm Do
cleared step 19
5 Determine if the CPUs are in sync.

Note: A dot or EccOn under the Sync header means that the CPUs are in
sync. The word no means that the CPUs are not in sync.
0 . cpu 1 noB noB yes . . . .
If the CPUs Do
are in sync step 6

are not in sync step 13

jammed step 9
did not jam step 7
GSP05 (CSP10)
CM NoBrst
minor (continued)
7
CAUTION
Possible loss of service
the active CPU.
CAUTION
the active CPU.

>\JAM
RTIF response:
PLEASE CONFIRM: (YES/NO)

>YES
RTIF response:
JAM DONE
297-2651-543 Standard 05.01 March 1999

CM NoBrst
minor (continued)
At the MAP display
>DPSYNC
If the response Do

CPU n active.
The inactive CPU is
JAMMED.
Do you want to continue.
”Y”, ”NO”, or ”N”):

>YES
Running in simplex mode with active CPU n.

If A1 Do
flashes step 12

>\RELEASE JAM
RTIF response:
RELEASE JAM DONE.
GSP05 (CSP10)
CM NoBrst
minor (continued)

>SYNC
If the response Do

successful
logs again.
or ”NO”, ”N”)

>NO
Go to step18.
15 Determine if the CM NoBrst minor alarm cleared.
If the alarm Do
cleared step 19
297-2651-543 Standard 05.01 March 1999

CM NoBrst
minor
minor
(continued)
(end)
16 Record the product engineering code (PEC) suffixes of the memory cards on
both CM planes.
Note 1: For DMS SuperNode, memory cards have an NT9X14 PEC. These
memory cards are in slots 7F to 16F in CM 0 and slots 23F to 32F in CM 1.
Note 2: For DMS SuperNode SE, memory cards have an NT9X14 PEC.
These memory cards are in slots 12F to 16F in CM 0 and slots 23F to 27F in
CM 1.
Note 3: Locate the PEC and suffix at the top of the card faceplate.
17 Record the release code of the processor cards in both CM planes.

Note 1: Processor cards have an NT9X10 PEC. These processor cards are in
slot 19F in CM 0 and slot 20F in CM 1.
Note 2: Locate the release code on the bottom of the card faceplate.
GSP05 (CSP10)
CM NoOvr
minor
Alarm display
NoOvr . . . . . . . . .
Indication
At the MTC level of the MAP display, NoOvr appears under the computing
module (CM) header of the alarm banner. The NoOvr indicates a no
handshake-override minor alarm.
Meaning
The switch runs in sync without handshake-override capability.
Result
The central processing unit (CPU) runs 3% to 5% slower. A minor effect on
call processing can occur during a period of high traffic.
Common procedures
Action
procedure.
297-2651-543 Standard 05.01 March 1999

CM NoOvr
minor (continued)
Summary of Clearing a CM NoOvr minor alarm

Jam inactive procedure.
CPU and drop
synchronization Use the instructions that follow
procedure.
Release jam and
synchronize CM
N
Passed?
Perform a
memory match
End Contact next

level of support
GSP05 (CSP10)
CM NoOvr
minor (continued)
Clearing a CM NoOvr minor alarm
At the MAP terminal
>MAPCI;MTC;CM
0 . CPU 1 . . . . . .

jammed step 5
did not jam step 3

3 To jam the inactive CPU, type
>\JAM
RTIF response:

>YES
RTIF response:
JAM DONE
297-2651-543 Standard 05.01 March 1999

CM NoOvr
minor (continued)
At the MAP terminal
>DPSYNC
If the response Do

CPU n active.
The inactive CPU is
JAMMED.
”Y”, ”NO”, or ”N”):

>YES

If A1 Do
flashes step 8

>\RELEASE JAM
RTIF response:
JAM RELEASE DONE
GSP05 (CSP10)
CM NoOvr
minor (continued)
At the MAP terminal
>SYNC
RTIF response:
If the response Do

successful
indicates the CPUs are not in sync step10
logs again.
or ”NO”, ”N”)

>NO
Go to step 20.
297-2651-543 Standard 05.01 March 1999

CM NoOvr
minor (continued)

>MEMORY
0 . cpu 1 . . . . . .
CM 0
0987654321 P | P 1234567890
.......... U | U ..........
MEMORY:
Example of DMS SuperNode SE MAP display:

0 . cpu 1 . . . . . .
CM 0
54321 P | P 12345
..... U | U .....
MEMORY:
12 To match the memories of the CPUs, type

>MATCH ALL
Matching memory between CPUs in sync.
Match ok.
If the response Do
is Match ok step 13
GSP05 (CSP10)
CM NoOvr
minor (continued)
13 To access the command interpreter (CI) level of the MAP display, type
>QUIT ALL
14 To access the log utility, type

>LOGUTIL
15 To determine if the system generated an MM100 log report by the memory

match, type
>OPEN MM 100
Note: If the system did not generate a log report, the response is Log empty.
If the response Do
is Log empty step 16

16 To determine if the system generated an MM101 log report by the memory

match, type
>OPEN MM 101
If the response Do
is Log empty step 17

17 To quit the log utility, type

>QUIT
297-2651-543 Standard 05.01 March 1999

CM NoOvr
minor
minor
(continued)
(end)
18 Determine if the NoOvr minor alarm cleared.
If the alarm Do
cleared step 21
GSP05 (CSP10)
CM MMnoSy
major
Alarm display
MMnoSy . . . . .
*M*
Indication
At the CM level of the MAP display, MMnoSy appears under the CM
header of the alarm banner and indicates that the switch is out of
synchronization because of a mismatch.
Meaning
The switch has been left out-of-sync because one of the following
conditions:
• a hard fault was found by the mismatch handler and resynchronization
was not attempted
• a system recovery was not performed because
— the mate is being tested
— synchronization was lost during testing
— a mismatch threshold was exceeded
— the active CPU is unable transfer activity to the inactive side
— a software error
• system recovery was attempted, but failed
The two CPUs of the computing module (CM) normally operate in the
synchronous matched mode (in-synchronization). The out-of-sync condition
indicates that manual recovery may be required.
Impact
Subscriber service not affected. In most cases, the mismatch handler is able
to clear the fault automatically and recover full functionality of the faulty
CPU. In some cases, the cause of the fault is not known and analysis of
associated log reports is required to determine the cause.
297-2651-543 Standard 05.01 March 1999

CM MMnoSy
major (continued)
Action
the alarm.
GSP05 (CSP10)
CM MMnoSy
major (continued)
Summary of Clearing a CM MMnoSy major alarm
Review MM
logs
procedure.
1 Use the instructions in the

MM111 log N Contact next flowchart to perform the
generated level of support procedure.
Replace cards
identified in
MM111 log
Clear alarm using

CLRALARM
command
N
Alarm
cleared? 1
Record card
replacement
Synchronize
End
297-2651-543 Standard 05.01 March 1999

CM MMnoSy
major (continued)
Clearing a CM MMnoSy major alarm
WARNING
Possible compromise of system integrity
Synchronization was dropped due to a mismatch event.
All mismatch logs must be analyzed and the appropriate
recovery action taken before attempting
resynchronization. Regaining synchronization with an
unresolved mismatch condition can compromise system
integrity.
At the MAP terminal

1 Access the CM level of the MAP display by typing
>MAPCI;MTC;CM
0 no CPU1 . . . . . . .
2 Determine which MM logs were generated after the mismatch occurred.
If the logs are Do
MM100 and MM111 step 3

GSP05 (CSP10)
CM MMnoSy
major (continued)
3 Review MM100 and MM111 logs for the results of the mismatch analysis.
Example of an MM100 log report
MM100 Mismatch Feb14 03:44:36.673
Mismatch number 17, Activity: Start: CPU 0, Final: CPU 0,
Mismatch result: No hardware fault found
Mismatch condition: Mismatch during sync transition
System recovery action: Test mate, re-sync undertaken
CPU 0 CPU 1
Data is valid Data is valid
Module Entry: IOABP SSTI: #052F CMCHKPR SSTI: #022B

AHR Value: 0B0107A4 01471240
AHR Data: A5A5A5A5 534C5F43
MAU AHR: 000E07A0 000E0240
MCR : 00000000 00000000
Not Found Owner #1C23,#0000: Module SOVFG DSPROT
A0–A6 (00042A00,01471244) (000429C0,00044570) (FFFF0000,00DB2D34)

(00042B64,016CC9D8) (01F9E658,016CE0E8) (00042A20,01D1E524)
( 000300C0,0147FFFE)
D0–D7 (000000AD,9D8241CB) (00030100,0147036E) (00000007,534C5F43)

(0000276C,01470000) (78F0FFF4,00000000) (00030100,00000000)
(0000000C,00000000) (FFFF0000,FFFF0000)
PC: (0B011254,0B1921EC) USP: (035478C4,01D1E508) SR: (2410,000A)

ISP: (00042A18,00042B6C) MSP: (0040E7D0,0040E7D0) ICache:(0001,0001)
FIR: (0001,0000) MM_Ctrl:(086C,081C) Timer: (3c2B,5967)

MAU_ctrl: (00AD,00AD) MAU_err:(0080,0080) Clk_stat: (0006,0004)
FC: (0006,0001) IRM: (0000,0000) ProcStat: (2A00,2E00)
SRam_Err: (FFC0,FFC0) PerInt:(0055,0055) Acc Prot: (00CF,00CF)
Mate_FIR: (0000,0001) MateFIR_OK: (y,y) MCR_STAT: (0,0)
User Stack Dump Interrupt Stack Dump

FFFF0000 0B1953B2 0B0107A6 FDFDFDFD
019E0000 000101F6 0004000C FDFDFDFD
01050002 00003C00 00042B20 FDFDFDFD
00010000 00000400 0D752322 FDFDFDFD
00000007 01471000 00000000 FDFDFDFD
0050EB58 00690000 000002B0 FDFDFDFD
MTC Info:
020C1550 000D0550
001010D0 00000000
20000000 00000000
00010000 00000000
00000000 00000000
00000000 00000000
297-2651-543 Standard 05.01 March 1999

CM MMnoSy
major (continued)
Example of an MM100 log report (continued)
Traceback:
0B011254=SYSDEFS.FM07:DISABLE_+#0000
0B1921EC=CMMEMORY.AG04:CHECKSUM+#0008
0D752322=TRAPDEFS.FJ03:TRAPHAND+#0162
0B1A2282=CMMEMORY.AG04:SET_CHEC+#013E
0B016C7E=INTSYS.BW04:FIR_INTE+#00D6
0B19525C=CMMEMORY.AG04:DO_CHECKS+#0098
0B049B3C=MODULES.DP02:INITIALIZ+#0014
0B323876=CMCHKPR.AQ01:CHECKSUM+#00FA
0B03D78Eis valtxt=PROCS.EY01:LIVEANDD+#0012
0B049B3C=MODULES.DP02:INITIALIZ+#0014
0B03D78E=PROCS.EY01:LIVEANDD+#0012
Example of an MM111 log report

MM111 SEP15 07:09:10 4400 INFO MM RECOVERY
Mismatch 9, CM 0, Faulty CPU 1
System recovery complete: CPUs out-of-SYNC
Manual action required to resynchronize the CPUs
Suspect:
Site Flr RPos Bay-id Shf Description Slot EqPEC
HOST 02 A02 DPCC:00 13 CPU: 00:1:0 20 9X13BC FRNT
HOST 02 A02 DPCC:00 13 CPU: 00:1:0 19 9X13BC FRNT
If the recovery action is Do
System recovery complete: step 4

CPUs out of SYNC
4 Record the location, description, slot number, and product engineering code
(PEC) including the suffix, of the first card on the list.
5 Perform the appropriate procedure in Card Replacement procedures. When

you have completed the procedure, return to this point.
If the card list in the MM111 log

contains Do
one card step 8

more than one card step 6
GSP05 (CSP10)
CM MMnoSy
major (continued)
(PEC), including the suffix, of the next card on the list.
7 Perform the appropriate procedure in Card Replacement procedures. When

you have completed the procedure, return to this point.
If all the cards on the list have Do
been replaced step 8

not been replaced step 6
8 Clear the MMnoSy alarm by typing

>CLRALARM MMNOSY
The MMnoSy alarm will be cleared.
Please confirm (“YES”, “Y”, “NO” “N)
9 Confirm the command by typing

>YES
The MMnoSync alarm has been cleared.
Is the response indicates that the

alarm Do
cleared step 12
297-2651-543 Standard 05.01 March 1999

CM MMnoSy
major (continued)
10 Record the card change data in the mismatch history database by typing
>SWAPHW CARD shelf_no slot_no side_no
where
shelf_no is the number of the shelf (0 or 1)
slot_no is the number of the slot (1 to 38)
side_no is the side of the computing module (front or back)
Example of MAP response:
pack has been replaced. Please verify that this
accurately reflects which circuit pack has been changed,
and that the displayed PEC code matches what is currently
equipped in that slot:
Site Flr RPOs Shf Description Slot EQPEC

HOST 00 A00 DPCC 0 18 CM 0;0;0 19 9X13BC

Please confirm (“YES”, “Y”, “NO” “N”): YES
(“YES”, “Y”) if the displayed card = replaced card
11 Confirm the command by typing

>YES
GSP05 (CSP10)
CM MMnoSy
major (continued)
12 Synchronize the CM by typing

>SYNC
The following cards have been reported as being replaced
since the last drop of synchronization. Verify that
these cards truly reflect all hardware which has been
replaced before before continuing with the
synchronization attempt.
PLANE replacement has NOT been recorded.
Site Flr RPos Bay-id Shf Description Slot EqPEC

HOST 01 F02 DPCC:00 00 CPU :00:0:0 19 9X10AA FRNT
HOST 01 F02 DPCC:00 01 PMC00:00:0:1 18 9X12AD FRNT
Please confirm (“YES”, “Y”, “NO” “N”)
If the response indicates Do
synchronization was successful step 20

13 Access the log utility by typing

>LOGUTIL
14 Print all MM logs.
If the software load is Do
BCS34 or earlier step 16

BCS35 or later step 15
15 Retrieve the MMINFO associated with the MM logs by typing

>MMINFO ALL DECODE
297-2651-543 Standard 05.01 March 1999

CM MMnoSy
majormajor
(continued)
(end)
16 Print all MMINFO logs.

Go to step 18.
17 The MMnoSy alarm is associated with matcher transient mismatches. Print all
MM logs.
18 Send all log reports to the next level of support and proceed as directed.
19 For further assistance, contact the next level of support.
GSP05 (CSP10)
CM NoSYNC
major
Alarm display
NoSYNC . . . . . . . . .
M
Indication
At the MTC level of the MAP display, NoSYNC appears under the CM
header of the alarm banner. The NoSYNC indicates a major alarm for no
synchronization.
Meaning
Synchronization of the pair of central processing units (CPUs) on the
computing module (CM) does not occur. In most occurrences, operating
company personnel drop synchronization. If synchronization drops
automatically, a more important alarm can bypass the NoSYNC alarm.
Result
The problem does not affect subscriber service. A fault can occur on the
active side and the switch can attempt to switch activity between the CPUs.
If a fault occurs and the switch affects activity between the CPUs, a cold
restart occurs. Calls in progress terminate.
Common procedures
Action
procedure.
297-2651-543 Standard 05.01 March 1999

CM NoSYNC
major (continued)
Summary of Clearing a CM NoSYNC major alarm

CM in split Y Contact next procedure.
mode? level of support
N this flowchart to perform the
procedure.
If CM is subject
of test, wait
MEMFLT Y Clear MEMFLT

cause of
alarm?
N
TBL cause of Y Clear TBL

alarm?
Inactive CPU Y RELEASE JAM

jammed?
SYNC
Sync Y End
successful?
N Contact next
level of support
GSP05 (CSP10)
CM NoSYNC
major (continued)
Clearing a CM NoSYNC major alarm
At the MAP terminal
>MAPCI;MTC;CM
0 no CPU 1 . . . . . .
2
CAUTION
Do not attempt to synchronize the switch until you
determine the switch runs in split mode.
Synchronization of the switch causes the switch to
drop the split mode and returns to sync. This
synchronization disrupts all other activity that takes
place at the time.
CAUTION
Do not attempt to synchronize the switch until you
determine the switch runs in split mode.
Synchronization of the switch causes the switch to
drop the split mode and returns to sync. This
synchronization disrupts all other activity that takes
place at the time.
Determine if the CM runs in split mode.

Note: If the CM runs in split mode, the word split appears under the Sync
header of the MAP display.
297-2651-543 Standard 05.01 March 1999

CM NoSYNC
major (continued)
0 split CPU 1 . . . . . .
If the CM Do
runs in split mode step 12

does not run in split mode step 3
3 Determine if the CM is the subject of tests.

If the CM is the subject of tests, ut appears under the following MAP display
headers:
• CPU0
• CPU1
• Memory
• MC
0 no CPU 1 ut . . . . .
If the CM Do
is the subject of tests step 4

is not the subject of tests step 5
4 Complete the tests. Continue the procedure.

Note: The removal of the ut status indicator occurs when the tests are
complete.

Note: The fault indicator appears under the Memory and MC headers of the
MAP display.
GSP05 (CSP10)
CM NoSYNC
major (continued)
0 no CPU 1 . flt . . .
If Do
. (dot) appears under the Memory step 8

and MC headers
flt appears under the Memory step 6
header.
tbl appears under the MC header step 7
6 Memory faults cause the CM to drop synchronization. Perform the procedure

Clearing a CM MemFlt minor alarm in this document. Complete the procedure.
Go to step 13.
7 MC faults cause the CM to drop synchronization. Perform the procedure

Clearing a CM MC Tbl minor alarm described in this document. Complete the
procedure. Go to step 13.

0 no CPU 1 . . yes . . . .
jammed step 9
did not jam step 10

>RELEASE JAM
297-2651-543 Standard 05.01 March 1999

CM NoSYNC
majormajor
(continued)
(end)
RTIF response:
JAM RELEASE DONE
At the MAP terminal

10 To synchronize the CM , type
>SYNC
If the response Do

successful
logs again.
”Y”, or ”NO”, ”N”)

>NO
Go to step12.
GSP05 (CSP10)
CM NoTOD
critical
Alarm display
NoTOD . . . . . . . . .
*C*
Indication
At the MTC level of the MAP display, NoTOD appears under the CM
header of the alarm banner. The NoTOD indicates a no time-of-day critical
alarm.
Meaning
An accurate time of day is not present. The system detected faults on all
time-of-day clocks. Loss of real-time value occurred. The system set the
clocks to zero.
Result
The switch needs time-of-day clocks to record billing information
(automatic message accounting) and log reports.
Common procedures
Action
procedure.
297-2651-543 Standard 05.01 March 1999

CM NoTOD
Summary of Clearing a CM NoTOD critical alarm

Determine the
procedure.
type of fault
procedure.
Both MCs have N Clear MC Tbl
time-of-day minor alarm 1
faults?
1 Y
Set time and

date
Synchronize the
CM
N Contact next
Alarm
level of support
cleared?
End
GSP05 (CSP10)
CM NoTOD
Clearing a CM NoTOD critical alarm
At the MAP terminal
1 To access the message controller (MC) level of the MAP display, type
>MAPCI;MTC;CM;MC
CM 0
MC 0 MC 1
. todf
2 Determine the type of fault that caused the alarm.

Note: The type of fault appears under the MC 0 and MC 1 headers of the MAP
display. In the example in step 1, a time-of-day fault (todf) appears under the
MC1 header.
If Do
one MC is istb step 3

one MC is todf step 3
both MCs are todf step 4
3 Perform the procedure Clearing a CM MC Tbl minor alarm in this document.

297-2651-543 Standard 05.01 March 1999

CM NoTOD
4 To set the date, type

>SETDATE dd mm yyyy
where
dd is the day (01 to 31)
mm is the month (01 to 12)
yyyy is the year
Example input:
>SETDATE 15 10 1996
setdate 15 10 1996
Warning: There is an automated TOD clock change
request scheduled on:
1996/10/30 at 1:00 (see table DSTTABLE).
Do you want to proceed with this request?

>Y
Date is THU. 15/OCT/1996 00:00:00
GSP05 (CSP10)
CM NoTOD
6 To use the 24-h clock and set the time, type

>SETTIME hh mm
where
hh is the hour (00 to 23)
mm is the minute (00 to 59)
Example input:
>SETTIME 03 09
Warning: There is an automated TOD clock change
request scheduled on:
1996/10/30 at 1:00 (see table DSTTABLE).
Do you want to proceed with this request?

>Y
Time is 03:09:00 on TUE. 1996/10/15.

>CM
0 no cpu 1 . . yes . . . .
297-2651-543 Standard 05.01 March 1999

CM NoTOD

jammed step 10
did not jam step 11

>\RELEASE JAM
RTIF response:
RELEASE JAM DONE
At the MAP terminal

The word no means the CM is not in sync.
If the CM Do
is in sync step 14
GSP05 (CSP10)
CM NoTOD

>SYNC
If the response Do

successful
is The CPUs are out of sync step 13
due to a problem with
mismatches.

Please confirm(”YES”, ”Y”,
”NO”, ”N”
(Applies to SuperNode or
SuperNode SE Series 70 only)
13 To deny the action, type

>NO
Note: This step applies to SuperNode or SuperNode SE Series 70 only.
Go to step 18.
14 Determine if the NoTOD critical alarm cleared.
If the alarm Do
cleared step 17
297-2651-543 Standard 05.01 March 1999

CM NoTOD
critical
critical
(continued)
(end)
15 Perform the correct alarm clearing procedure in this document. Complete the
procedure, and return to this point.
16 The next step depends on the use of table DSTTABLE.

Note: The MAP response that indicates the use of table DSTTABLE appears in
step 4.
If table DSTABLE Do
is in use step 17
is not in use step 20
17 Make sure that conflicts do not exist between the SETDATE and SETTIME
command entries and the entry in table DSTTABLE.
Note: The warning message indicates a possible problem with an entry in table
DSTTABLE. The message appears when an entry that did not expire is in the
table when you use SETDATE or SETTIME commands.
If a conflict Do
occurs with an entry in DSTTABLE step 19

does not occur with an entry in step 20
DSTTABLE
18 Collect mismatch logs and contact the next level of support.
GSP05 (CSP10)
CM CMFlt
major
Alarm display
CMFlt . . . . . . . . .
M
Indication
At the MTC level of the MAP display, CMFlt appears under the CM header
of the alarm banner. The CMFlt indicates a major alarm for a computing
module (CM) fault.
Meaning
A fault is present on one of the central processing units (CPUs).
Result
When a fault occurs in one of the CPUs, CPU activity automatically
switches and synchronization drops. These actions allow the fault-free CPU
to take control.
Common procedures
Action
procedure.
297-2651-543 Standard 05.01 March 1999

CM CMFlt
major (continued)
Summary of Clearing a CM CMFlt major alarm
Determine fault This flowchart summarizes the

type procedure.

Perform E2A procedure.
Fault indicator Y
alarm clearing
e2a?
procedure
N
Perform CM CLK
Fault indicator Y
alarm clearing
clk?
procedure
N
Make sure CPU is Perform REx

Fault indicator Y inactive, in sync test
rex? and not jammed
N
Fault indicator Y Make sure CPU is TST Replace

Replace cards.
card.
N
mem or flt? inactive, in sync command Refer
Refer to
to correct
the
and not jammed passed? NTP.
appropriate NTP.
N Y
Test
TST Y Sync and

Passed?
command release jam
pass?
Contact next Replace cards. End

level of support Refer to correct
NTP.
GSP05 (CSP10)
CM CMFlt
major (continued)
Clearing a CM CMFlt major alarm
At the MAP display
>MAPCI;MTC;CM
0 no cpu 1 flt . yes . . . .

Note: The fault indicator is under the CPU0 and CPU1 headers of the MAP
display. In the example in step 1, the fault indicator for CPU 0 is flt.
If the fault indicator Do
is clk step 3
is e2a step 4
is rex step 5
is flt step 24
is mem step 24
3 Perform the procedure Clearing a CM ClkFlt major alarm in this document.
4 Perform the procedure Clearing a CM E2A minor alarm in this document.

Note: The word yes under the Jam header of the CM level MAP display means
that the CPU jammed. The area is blank if the CPU did not jam.
jammed step 6
did not jam step 7
297-2651-543 Standard 05.01 March 1999

CM CMFlt
major (continued)
>\RELEASE JAM
RTIF response:
JAM RELEASE DONE
At the MAP display

If the CM Do
is in sync step 9

>SYNC
If the response Do

successful
GSP05 (CSP10)
CM CMFlt
major (continued)
9
CAUTION
Check with operating company personnel to make
sure that a REx test can run at this time. Make sure
that you initiate REx tests during a low traffic period
as a result of the high level of CPU occupancy
required. Synchronization automatically drops and
you cannot synchronize the CM again, while the REx
test runs.
CAUTION
that you initiate REx tests during a low traffic period
as a result of the high level of CPU occupancy
required. Synchronization automatically drops and
you cannot synchronize the CM again, while the REx
test runs.
To run a REx test on the CM , type

>REXTST
If the response Do
is CAUTION: CM sync and step 11

activity states will
change.
”Y”, ”NO”, or ”N”):
is CMREx test not step 10
authorized by REX
controller.
297-2651-543 Standard 05.01 March 1999

CM CMFlt
major (continued)
10 REx tests run on another node. Consult office records or operating company
personnel. Determine where the REx tests run. Wait until the tests finish
before you run the CM REx test. To run the test, type
>REXTST
If the response Do

change
”Y”, ”NO”, or ”N”):

>YES
If the REXTST command Do
passed step 48
card list

GSP05 (CSP10)
CM CMFlt
major (continued)

jammed step 15
did not jam step 16

>\RELEASE JAM
RTIF response:
RELEASE JAM DONE
At the MAP display

16 To make sure that the MAP display is at the CM level, type
>CM

If the CM Do
is in sync step 20
297-2651-543 Standard 05.01 March 1999

CM CMFlt
major (continued)

>SYNC
If the response Do

successful
19 Determine if the CMFlt major alarm cleared.
If the alarm Do
cleared step 44
20
WARNING
sure that a REx test runs at this time. Make sure you
initiate REx tests during a low traffic period, as a
result of the high level of CPU occupancy required.
WARNING
sure that a REx test runs at this time. Make sure you
initiate REx tests during a low traffic period, as a
result of the high level of CPU occupancy required.
GSP05 (CSP10)
CM CMFlt
major (continued)
To run a REx test on the CM, type
>REXTST
Example of a Map response:
CAUTION: CM sync and activity states will change

>YES
If the REXTST command Do
passed step 44
cards on the list
card on the list.
Go to step 13.
23 Determine if the fault is on the inactive or active CPU.
If the fault Do
is on the inactive CPU step 24

is on the active CPU step 25
297-2651-543 Standard 05.01 March 1999

CM CMFlt
major (continued)
24 Determine if the inactive CPU is in sync.
is in sync step 26
25 Determine if the active CPU is in sync.
If the active CPU Do
is in sync step 36

jammed step 32
did not jam step 27

>MEMORY
28 To match the memories of the CPUs, type

>MATCH ALL
Matching memory between CPUs in
sync.
GSP05 (CSP10)
CM CMFlt
major (continued)
29 Determine if the memory match caused the following conditions to occur:

• The memory match was successful.
• The system did not generate mismatch logs, MM100 or MM101.
• The CM remained in sync, indicated by a dot or EccON under the Sync
header on the MAP display.
If the conditions Do
occurred step 30
did not occur step 50

30
WARNING
Loss of service
Make sure that you do not jam the ACTIVE CPU. If
you jam the active CPU while the CM is not in sync, a
the active CPU.
WARNING
Loss of service
Make sure that you do not jam the ACTIVE CPU. If
the active CPU.

>\JAM
press the Enter key.
RTIF response:
PLEASE CONFIRM (”YES” OR ”NO”)
297-2651-543 Standard 05.01 March 1999

CM CMFlt
major (continued)
31 To confirm the response, type

>YES
RTIF response:
JAM DONE

>DPSYNC
If the response Do

CPUn active the inactive
CPU is jammed.
Please confirm
(”YES” OR ”NO”)
is Drop synchronization fails. step 50

is Cancelled. Active CPUn has a step 35
processor clock that has faults

>YES
34 Wait until A1 flashes or fails to flash on the RTIF for the inactive CPU.
If A1 Do
flashes step 37
did not flash after 5 min step 50
GSP05 (CSP10)
CM CMFlt
major (continued)
35 The DPSYNC command is not available as a result of the damaged clock of the
active CPU. Perform the procedures in this document on how to clear a CM
CLK major alarm.
36 Perform the activity switch with memory match procedure in this document.

>TST
If the response Do

is Static RAM test

is Do you want to do the
test(s) anyway?
”Y”, ”NO”, or ”N”):

>YES
passed step 44
cards on the list
297-2651-543 Standard 05.01 March 1999

CM CMFlt
major (continued)
card on the list.


>TST
If the response Do

Static RAM test
is Do you want to do the

test(s) anyway?
”Y”, ”NO”, or ”N”):

>YES
passed step 44
failed, and did not replace all cards step 43
on the list
failed, and replaced all cards on the step 50
list
GSP05 (CSP10)
CM CMFlt
major (continued)
card on the list.
Go to step 40.

jammed step 45
did not jam step 46

>\RELEASE JAM
RTIF response:
JAM RELEASE DONE
At the MAP display

If the CM Do
is in sync step 48
297-2651-543 Standard 05.01 March 1999

CM CMFlt
majormajor
(continued)
(end)

>SYNC
If the response Do

successful
48 Determine if the CMFlt major alarm cleared.
If the alarm Do
cleared step 51
GSP05 (CSP10)
CM PMCFlt
major
Alarm display
PMCFlt . . . . . . . . .
M
Indication
At the MTC level of the MAP display, PMCFlt appears under the CM
header of the alarm banner. The PMCFlt indicates a major alarm for the
peripheral module controller fault.
Meaning
The two ports of the peripheral module controller (PMC) are out of service.
The ports are in one of the following states:
• P-side busy (The associated system load module is [SLM] out of
service.)
• manual busy
• system busy (hard fault)
Result
The computing module (CM) cannot access either SLM.
The problem does not affect subscriber service. If a fault occurs, the switch
cannot access the CM and MS files in order for the switch to recover. The
CM and MS files are on the SLMs.
Common procedures
Action
procedure.
297-2651-543 Standard 05.01 March 1999

CM PMCFlt
major (continued)
Summary of How to clear a CM PMCFlt major alarm

PMC ports
Perform SLM procedure.
Port P-side Y
alarm clearing 1
busy?
procedure
1 N
Y Manually busy
Port system 2
the port
busy?
2 N
Test the port
N Replace the card.

Passed? Refer to the 3
correct NTP.
3 Y
Return the port

to service
N Contact next
Alarm
level of support
cleared?
End
GSP05 (CSP10)
CM PMCFlt
major (continued)
How to clear a CM PMCFlt major alarm
At the MAP terminal
1 To access the PMC level of the MAP display, type
>MAPCI;MTC;CM;PMC
PMC 0
sbsy
PORT0: pbsy
PORT1: sbsy
2 Determine the state of the PMC ports.

Note: The state of the PMC ports appears on the right of the PORT0 and
PORT1 headers on the MAP display.
If the state of either port Do
is sbsy step 5
is pbsy step 3
is mbsy step 4
3 The SLM that connects to the P-side busy port is out of service. Perform the
correct alarm clearing procedure for an input/output device (IOD) SLM.
Go to step 1.

for the removal of the manual busy port from service. When you have
permission, continue with the procedure.
Go to step 1.
297-2651-543 Standard 05.01 March 1999

CM PMCFlt
major (continued)
5 To manually busy the system busy PMC port, type

>BSY 0 PORT port_number
where
port_number is the number of the system busy PMC port (0 or 1)
passed step 6
failed step 35
6 Determine the state of the PMC.

Note: The state of the PMC appears under the PMC header of the MAP
display.
If the state of the PMC Do
is sbsy step 7
7 Obtain a duplicate of CM133 log reports generated during the past hour.
8 Determine the reason that the PMC is in the system busy state.
Note: The reason for the system busy state of the PMC appears in the reason
text of the CM133 log report.
If the reason for the system busy

state of the PMC Do
is A stuck hardware fault step 9

was detected
GSP05 (CSP10)
CM PMCFlt
major (continued)
9 Obtain a duplicate of any CM140 and CM152 log reports that the system
generated during the past hour.
10 To replace the first card on the list in the CM152 log report, perform the correct
Note 1: When both planes have a stuck hardware fault, a peripheral interrupt
mismatch does not occur. When both planes have a stuck hardware fault, the
system also does not generate a CM152 log report. If the system does not
generate a CM152 log report, identify the card that has faults. To identify the
card that has faults, use the information in the CM 140 log report.
Note 2: The CM140 log report identifies the affected PMC and link. The
CM152 log report contains a list of cards that can require replacement.
11 To test the PMC port that you busied in step 5, type

>TST 0 PORT port_number
where
port_number is the number of the manual busy PMC port (0 or 1)
passed step 18
failed, the system generated a card step 12
list, and you did not replace all
cards on the list in the CM152 log
report.
list, and you replaced all cards on
the list in the CM152 log report.
12 To replace the next card on the list in the CM152 log report, perform the correct
Go to step 11.
297-2651-543 Standard 05.01 March 1999

CM PMCFlt
major (continued)
13 To test the manual busy PMC port, type

where
passed step 18
card list


where
passed step 18
cards on the list
the list
card on the list.
Go to step 15.
GSP05 (CSP10)
CM PMCFlt
major (continued)
18 To return the PMC port to service, type

>RTS 0 PORT port_number
where
port_number is the number of the PMC port that you busied in step 5 (0 or 1)
passed step 19
failed step 35
19 Determine the state of the other PMC port.
If the state of the other PMC port Do
is pbsy step 3
is mbsy step 4
is sbsy step 5
is insv step 20

>MC
CM 0
MC 0 MC 1
mbsy .
21 Determine if the message controller (MC) is manual busy.

Note: The state of the MC appears under the MC 0 and MC 1 headers.
is mbsy step 22
is not mbsy step 23
297-2651-543 Standard 05.01 March 1999

CM PMCFlt
major (continued)

>RTS mc_number
where
MC RTS OK.
passed step 23
failed step 35

>CM
24 Determine that the inactive CPU plane turned off.
If the inactive CPU plane Do
turned off step 25

did not turn off step 27

>TST
Static RAM test

GSP05 (CSP10)
CM PMCFlt
major (continued)

>YES
Test passed.
passed step 27
failed step 35

jammed step 28
did not jam step 29

>\RELEASE JAM
RTIF response:
JAM RELEASE DONE
297-2651-543 Standard 05.01 March 1999

CM PMCFlt
major (continued)
At the MAP terminal
29 Determine if the CM is in synchronization.
Note: A dot or EccOn under the Sync header means that the CM is in
synchronization. The word no means that the CM is not in synchronization.
If the CM Do
is in synchronization step 31
is not in synchronization step 30

>SYNC
If the SYNC command Do
was successful step 31

was not successful step 35

>MAPCI;MTC;CM;PMC
32 Determine if the PMC ports are in service.

Note: The state of the PMC ports appears in the PORT0 and PORT1 fields,
under the PMC 0 header. A dot means the port is in service.
If Do
all PMC ports are in service step 33

a minimum of one PMC port is not step 2
in service
GSP05 (CSP10)
CM PMCFlt
major (continued)
(end)
33 Determine if the PMCFlt major alarm cleared.
If the PMCFlt major alarm Do
cleared step 36
297-2651-543 Standard 05.01 March 1999

CM PMCTbl
minor
Alarm display
PMCTbl . . . . . . . . .
Indication
At the MTC level of the MAP display, PMCTbl appears under the
computing module (CM) header of the alarm banner. The PMCTbl indicates
a minor alarm for a peripheral message controller problem.
Meaning
A peripheral message controller (PMC) is in-service trouble because a PMC
port is in one of the following states:
• P-side busy (The associated system load module [SLM] is out of
service.)
• manual busy
• system busy (hard fault)
Result
The CM cannot access an SLM. The problem does not affect subscriber
service.
Common procedures
Action
This procedure has a summary flowchart and a list of steps. Use the
procedure.
GSP05 (CSP10)
CM PMCTbl
minor (continued)
Summary of How to clear a CM PMCTbl minor alarm

PMC ports
procedure.
Y Perform the SLM
Is the port 1
alarm clearing
P-side busy?
procedure
1 N
Y Manually busy
Is the port
the port 2
system busy?
2 N
Test the port
Y
Passed? 3
N
Replace cards.
Refer to the
correct NTP.
Return the port Alarm Y End

to service cleared?
Contact next
level of support
297-2651-543 Standard 05.01 March 1999

CM PMCTbl
minor (continued)
How to clear a CM PMCTbl minor alarm
At the MAP terminal
>MAPCI;MTC;CM;PMC
PMC 0
istb
PORT0: .
PORT1: sbsy
2 Determine the state of the PMC ports.

Note: The state of the PMC ports appears on the right of the PORT0 and
PORT1 headers on the MAP display.
If the state of either port Do
is pbsy step 3
is mbsy step 4
is sbsy step 5
3 The SLM that connects to the P-side busy port is out of service. Perform the
correct alarm clearing procedure for the input/output device (IOD) SLM.
Go to step 1.

for the removal of the manual busy port from service. When you have
permission, continue this procedure.
Go to step 1.
GSP05 (CSP10)
CM PMCTbl
minor (continued)
5 To manually busy the system busy PMC port, type

>BSY 0 PORT port_number
where
port_number is the number of the system busy PMC port (0 or 1)
passed step 6
failed step 32
6 Obtain copies of CM137 log reports generated during the past hour.
7 Determine the cause of the system busy state of the PMC port.
Note: The reason for the system busy state of the PMC port appears in the
reason text of the CM137 log report.

state of the PMC Do

was detected
8 Obtain a duplicate of any CM140 and CM152 log reports generated during the
past hour.
9 Replace the first card on the list in the CM152 log report. Perform the correct
card replacement procedure in Card Replacement Procedures. Complete the
Note 1: A peripheral interrupt mismatch does not occur when a stuck hardware
fault occurs on both planes. The system does not generate a CM152 log report
when a stuck hardware fault occurs on both planes. If the system does not
generate a CM152 log report, identify the card that has faults. To identify the
card that has faults, use the information in the CM140 log report.
Note 2: The CM140 log report identifies the affected PMC and link. The
CM152 log report contains a list of cards that can require replacement.
297-2651-543 Standard 05.01 March 1999

CM PMCTbl
minor (continued)
10 To test the PMC port that you busied in step 5, type

where
passed step 17
report
the list in the CM152 log report
11 Replace the next card on the list in the CM152 log report. Perform the correct
Go to step 10.

where
passed step 17
card list

GSP05 (CSP10)
CM PMCTbl
minor (continued)

where
passed step 17
cards on the list
failed, and you replaced cards on step 32
the list
card on the list.
Go to step 14.
17 To return the manual busy PMC port to service, type

>RTS 0 PORT port_number
where
passed step 18
failed step 32

>MC
CM 0
MC 0 MC 1
mbsy .
297-2651-543 Standard 05.01 March 1999

CM PMCTbl
minor (continued)
19 Determine if the message controller (MC) is manual busy.

Note: The term mbsy under the MC header means that the MC is manual
busy.
is mbsy step 20
is not mbsy step 21

>RTS mc_number
where
MC RTS OK.
passed step 21
failed step 32

>CM
0 no cpu 1 . . yes . . .
GSP05 (CSP10)
CM PMCTbl
minor (continued)


>TST
Static RAM test


>YES
Test passed.
passed step 25
297-2651-543 Standard 05.01 March 1999

CM PMCTbl
minor (continued)

jammed step 26
did not jam step 27

>\RELEASE JAM
RTIF response:
JAM RELEASE DONE
At the MAP terminal

Note: A dot or EccOn under the Sync header means that the CM is in
synchronization. The word no means that the CM is not in synchronization.
If the CM Do
GSP05 (CSP10)
CM PMCTbl
minor (continued)

>SYNC
If the response Do

successful
indicates The CPUs are out of step 29
sync due to a problem with
mismatches. The mismatch
logs should be analyzed
before re-syncing.
”Y”, or ”NO”, ”N”)
(SuperNode and SuperNode SE
Series 70 only)
29 (SuperNode and SuperNode SE Series 70 only)

>NO
Go to step 32.
30 Determine if the PMCTbl minor alarm cleared.
If the PMCTbl minor alarm Do
cleared step 33
297-2651-543 Standard 05.01 March 1999

CM PMCTbl
minor
minor
(continued)
(end)
GSP05 (CSP10)
CM PrcOpt
major
Alarm display
PrcOpt . . . . . .
. . . M
Indication
At the MTC level of the MAP display, PrcOpt appears under the CM header
of the alarm banner. The PrcOpt indicates a processor optionality alarm.
Meaning
The PEC number on the processor card and the value entered for the
processor card card do not match.
Result
The problem does not now affect subscriber service. If a fault occurs on the
active side, the switch cannot recover automatically.
Common procedures
Action
procedure.
297-2651-543 Standard 05.01 March 1999

CM PrcOpt
major (continued)
Summary of Clearing a CM PrcOpt major alarm

Obtain CM logs
procedure.

procedure.
Contact next
level of support
End
GSP05 (CSP10)
CM PrcOpt
major (continued)
(end)
Clearing a CM PrcOpt major alarm
At the MAP terminal
1 Obtain all current CM logs.
297-2651-543 Standard 05.01 March 1999

CM RExFlt
major
Alarm display
RExFlt . . . . . .
. . . M
Indication
At the MTC level of the MAP display, RExFlt appears under the CM header
of the alarm banner. The RExFlt indicates a fault major alarm.
Meaning
The CM RExFlt major alarm occurs if a scheduled computing module (CM)
routine exercise (REx) test does not finish.
Reasons for the failure of CM REx testing to finish include:

• a minimum of one failed REx test
• manual termination of REx testing
• a minimum of one trap
• a minimum of one mismatch
• a minimum of onelinks closure
• an RMS timeout
• an environment error
Result
There is no result.
Common procedures
Action
procedure.
GSP05 (CSP10)
CM RExFlt
major (continued)
Summary of Clearing a CM RExFlt major alarm

Obtain copies of procedure.
latest logs
procedure.
Obtain TRAP,
SWER and
footprint logs for
active and
inactive sides
Access CMMNT
MAP level
Record value
for all counts
Contact next
level of support
End
297-2651-543 Standard 05.01 March 1999

CM RExFlt
major (continued)
Clearing a CM RExFlt major alarm
At the MAP terminal
1 Obtain copies of current CM, TRAP, SWER, and footprint logs for the active and
inactive sides.

>MAPCI;MTC;CM;CMMNT
0 . cpu 0 . . . . . .
AutoLdev: Primary = SLM 0 DISK Secondary = SLM 1 DISK
Next image test restart type= RELOAD

3 To determine the value of the counts for the system stability threshold, type
>QUERYCM REXSCHD COUNTS ALL
The Link Closure count is 2.
The Out-of-sync Recovery Mismatch count is 1.
The In-Sync Recovery Mismatch count is 0.
The Trap Rate count is 0.
The Processor Memory Fault count is 0.
The Clock Fault count is 0.
The Cancelled REx count is 2.
4 Record the values that appear for each count.
GSP05 (CSP10)
CM RExFlt
major (continued)
(end)
297-2651-543 Standard 05.01 March 1999

CM RExSch
minor
Alarm display
RExSch . . . . . .
. . .
Indication
At the MTC level of the MAP display, RExSch appears under the computing
module (CM) header of the alarm banner. The RExSch indicates a REx
schedule minor alarm.
Meaning
The CM RExSch minor alarm occurs for the following reasons:
• Cancellation of two consecutive automatic daily routine exercise (REx)
tests. System stability faults exceed the thresholds and cause the
cancellation of an automatic daily REx test. Maintenance personnel
enter these thresholds to detect recurring problems.
• Entry in table REXSCHED disabled CM REx testing.
Result
There is no result.
Common procedures
Action
procedure.
GSP05 (CSP10)
CM RExSch
minor (continued)
Summary of Clearing a CM RExSch minor alarm

Determine if CM procedure.
REx testing
disabled Use the instructions that follow
procedure.
Y
CM REx Intended to
Y
testing disable CM 1
disabled? REx testing?
N N
Query the Enable CM REx

system stability testing
counts
Y
Record the
Alarm
values for all 1
cleared?
counts
2 2 N
Contact the next

level of support
End
297-2651-543 Standard 05.01 March 1999

CM RExSch
minor (continued)
Clearing a CM RExSch minor alarm
At the MAP terminal
1 Obtain copies of current IOAU112 log reports.
2 Determine if maintenance personnel disabled the CM REx testing. If

maintenance personnel disabled the CM REx testing, the following message
appears in the IOAU112 log report:
The CRITICAL CM_REX_TEST has been DISABLED INDEFINITELY.
If maintenance personnel Do
disabled CM REx testing step 3

did not disable CM REx testing step 16
3 Contact your next level of support to determine if CM REx testing disabled.
If maintenance personnel Do
intended to disable CM REx testing step 20

did not intend to disable CM REx step 4
testing
4 To access table REXSCHED, type

>TABLE REXSCHED
MACHINE NOT IN SYNC - DMOS NOT ALLOWED
JOURNAL FILE NOT AVAILABLE- DMOS NOT ALLOWED
TABLE: REXSCHED
5 To position on the CM REx test tuple, type

>POS CM_REX_TEST
CM_REX_TEST N 1 1 NONE
GSP05 (CSP10)
CM RExSch
minor (continued)
6 To activate write access, type

>RWOK ON
WRITE ACCESS ENABLED FOR RESTRICTED DATA
7 To start the tuple change, type

>CHA
MACHINE NOT IN SYNC - DMOS NOT ALLOWED
JOURNAL FILE NOT AVAILABLE- DMOS NOT ALLOWED
ENTER Y TO CONTINUE PROCESSING OR N TO QUIT
8 To enable CM REx testing, type

>Y
TUPLE TO BE CHANGED:
CM_REX_TEST N 1 1 NONE
ENTER Y TO CONFIRM, N TO REJECT OR E TO EDIT
9 To enter the time period between CM REx tests, type

>period
where
period is the minimum number of days between CM REx tests (1 to 7)
Note: If you do not want to change this part of the tuple, do not make an entry.
Press the Enter key.
297-2651-543 Standard 05.01 March 1999

CM RExSch
minor (continued)
10 To enter the number of CM REx tests that run in parallel, type

>number
where
number is the maximum number of CM REx tests (0 to 99) that run in
parallel
Press the Enter key.
11 To enter the days of the week that you want to disable the CM REx test, type
>daysdsbl
where
(MON, TUE, WED, THU, FRI, SAT, SUN, ALL, or NONE)
Press the Entry key.
12 To confirm the tuple change, type

>Y
TUPLE CHANGED
JOURNAL FILE INACTIVE
13 To exit table REXSCHED, type

>QUIT
14 To verify the activation of CM REx testing, review the most recent IOAU112 log
reports.
Note: If maintenance personnel enabled CM REx testing, the message The
CRITICAL CM_REX_TEST has been ENABLED. appears in the log report.
If the system Do
confirms CM REx testing step 15

does not confirm CM REx testing step 19
GSP05 (CSP10)
CM RExSch
minor (continued)
15 When the next scheduled CM REx test is complete, determine if the RExSch
alarm cleared.
If the RExSch alarm Do
clears step 20
16 To access the CMMnt level of the MAP display, type

>MAPCI;MTC;CM;CMMNT
0 . cpu 0 . . . . . .
Next image test restart type= RELOAD

17 To determine the value of counts for the system stability threshold, type
>QUERYCM REXSCHD COUNTS ALL
The Link Closure count is 2.
The Out-of-sync Recovery Mismatch count is 1.
The In-Sync Recovery Mismatch count is 0.
The Trap Rate count is 0.
The Processor Memory Fault count is 0.
The Clock Fault count is 0.
The Cancelled REx count is 2.
297-2651-543 Standard 05.01 March 1999

CM RExSch
minor
minor
(continued)
(end)
18 Record the values that appear for each count.
GSP05 (CSP10)
CM RExTst
minor
Alarm display
RExTst . . . . . .
. . .
Indication
At the MTC level of the MAP display, RExTst appears under the CM header
of the alarm banner. The RExTst indicates a routine exercise (REx) test
minor alarm.
Meaning
The computing module (CM) undergoes routine exercise (REx) tests.
Result
The problem can affect subscriber service during a CM REx test.
Suppression of all CM alarms except ClkFlt, CM Flt, CMTrap, IMAGE,
LowMem, and NoTOD occurs.
Common procedures
Action
procedure.
297-2651-543 Standard 05.01 March 1999

CM RExTst
minor (continued)
Summary of Clearing a CM RExTst minor alarm
Determine if This flowchart summarizes the

REx test passed procedure.

Y procedure.
Passed?
1
N
Replace card.
Refer to correct
NTP.
Perform CM
REx test
N
Passed? 2
Y
1
N Alarm Y Clear alarm
Alarm changed to
cleared? new alarm?
N
Y 2
End Contact the next
level of support
GSP05 (CSP10)
CM RExTst
minor (continued)
Clearing a CM RExTst minor alarm
At the MAP terminal
>MAPCI;MTC;CM
0 . cpu 0 . . . . . .
2 Wait until the REx test is complete. Continue the procedure.

Note: Wait a maximum of 90 min for the REx test to finish.
3 Determine if the REx test passed.

RExTst passed.
If the response Do
indicates the REx test passed step 12

indicates the REx test failed, and step 4
the system generated a card list
and PEC suffix of all cards on the list.
5 Choose a card to work on.

Note: One or more of the cards that require replacement can be on the
inactive side. If the cards are on the inactive side, work on a card on the
inactive side first.

7 Determine if more cards require replacement.

Note: You recorded this information in step 4.
297-2651-543 Standard 05.01 March 1999

CM RExTst
minor (continued)
If Do
more cards require replacement step 5

no more cards require replacement step 8
8
WARNING
you initiate REx tests during a low traffic period. The
REx tests require a high level of CPU occupancy.
WARNING
you initiate REx tests during a low traffic period.
The REx tests require a high level of CPU
occupancy.
To run a REx test on the CM, type

>REXTST
If the response Do

change
”Y”, ”NO”, or ”N”):
is CMREx test not authorized step 9
by REX controller.
GSP05 (CSP10)
CM RExTst
minor (continued)
9 You now run a REx test on another node. Determine from office records or
from operating company personnel where the REx tests run. Wait until the
tests finish. To run the CM test, type
>REXTST
If the response Do

change
”Y”, ”NO”, or ”N”):

>YES
RExTst passed.
If the response Do
indicates the REx test passed step 12

you did not replace all cards on the
list
you replaced all the cards on the list
11 Record the location, description, slot number, PEC, and PEC suffix of all cards
on the list.
Go to step 5.
297-2651-543 Standard 05.01 March 1999

CM RExTst
minor
minor
(continued)
(end)
12 Determine if the RExTst minor alarm cleared.
If the alarm Do
cleared step 15
GSP05 (CSP10)
CM SBsyMC
major
Alarm display
SBsyMC . . . . . . . . .
M
Indication
At the MTC level of the MAP display, SBsyMC appears under the CM
header of the alarm banner. The SBsyMC indicates a major alarm for a
system busy message controller.
Meaning
A message controller (MC) is out of service for one of the following
reasons:
• a hard fault
• a subsystem clock fault
Result
The computing module (CM) contains two MCs. If one MC is out of
service, the full messaging load transfers to the second MC. The removal of
the second MC from service means the switch cannot maintain subscriber
service.
Common procedures
Action
procedure.
297-2651-543 Standard 05.01 March 1999

CM SBsyMC
major (continued)
Summary of How to clear a CM SBsyMC major alarm

Determine if
procedure.
there are MS
alarms
procedure.
Are there MS N Manually busy
2 and test the
alarms?
affected MC
Y
Y
Clear the MS TST Y Alarm
alarms command 3
cleared?
passed?
N 4 N
N
Are the alarms Replace the
2 card
cleared?
1 Y
Test the MC
N
TST
command 4
passed?
3 Y
Return the MC
to service
GSP05 (CSP10)
CM SBsyMC
major (continued)
Summary of How to clear a CM SBsyMC major alarm (continued)
4
Test the affected
SSC
N
TST Replace the Retest the TST
N
command NT9X22 card SSC command 6
passed? passed?
5 Y 5 Y
Test the MC
again
N
TST Replace the Test the MC TST
N
command cards command 6
passed? passed?
7 Y 7 Y
N
Alarms Contact next
6 level of support
cleared?
1 Y
End
297-2651-543 Standard 05.01 March 1999

CM SBsyMC
major (continued)
How to clear a CM SBsyMC major alarm
At the MAP terminal
1 To clear all MS alarms, use the correct procedure in this document. Complete
the procedure and return to this point.
2 Determine if the SBsyMC major alarm cleared.
If the alarm Do
cleared step 38

>MAPCI;MTC;CM;MC
CM 0
MC 0 MC 1
. sbsy
4 Record the number of the system busy MC.
5 To manually busy the system busy MC, type

>BSY mc_number
where
mc_number is the number of the system busy MC (0 or 1)
6 Obtain copies of CM104 log reports generated during the past hour.
GSP05 (CSP10)
CM SBsyMC
major (continued)
7 Determine the cause of the system busy state of the MC.

Note: The reason for the system busy state of the MC appears in the reason
text of the CM104 log report.

state of the MC Do

was detected
8 Obtain a duplicate of CM128 and CM152 log reports generated during the past
hour.
9 Replace the first card on the list in the CM152 log report. Perform the correct
Note 1: When both planes have a stuck hardware fault, a peripheral mismatch
does not occur. When both planes have a stuck hardware fault, the system
also does not generate a CM 152 log report. If the system does not generate a
CM152 log report, use the information in the report to identify the card that has
faults.
Note 2: The CM128 log report identifies the affected MC and link. The CM152
log report contains a list of cards that can require replacement.

>TST mc_number
where
passed step 23
report
the list in the CM152 log report
297-2651-543 Standard 05.01 March 1999

CM SBsyMC
major (continued)
11 To replace the next card on the list in the CM152 log report, perform the correct

>TST mc_number
where
passed step 23
the cards listed in the CM152 log
report
cards listed in the CM152 log report

>CLOCK
T O D
MC0 MC1
Link 0 . manb
Link 1 . manb
SSC . oos
GSP05 (CSP10)
CM SBsyMC
major (continued)

>TST SSC ssc_number
where
ssc_number is the SSC for the system busy MC (0 or 1) that
passed step 17
card list
failed, and the system did not step 37
generate a card list
15 To replace the NT9X22 card, perform the correct procedure in Card


>TST SSC ssc_number
where
ssc_number is the SSC for the system busy MC (0 or 1) that
passed step 17
failed step 37
17 To quit from the clock level of the MAP display, type

>QUIT
297-2651-543 Standard 05.01 March 1999

CM SBsyMC
major (continued)

>TST mc_number
where
mc_number is the number of the system busy MC (0 or 1) that you
recorded in step 4
passed step 23
card list
card list

21 To test the manual-busy MC, type

>MC;TST mc_number
where
passed step 23
cards on the list
the list
card on the list.
Go to step 20.
GSP05 (CSP10)
CM SBsyMC
major (continued)

>RTS mc_number
where
passed step 24
failed step 37
24 Determine the state of the MC that you returned to service.
is todf, sscf, or istb step 35


>CM
0 no cpu 1 . . yes . . . .
26 Determine if the inactive CM plane turned off.
turned off step 27

did not turn off step 29
297-2651-543 Standard 05.01 March 1999

CM SBsyMC
major (continued)

>TST
Static RAM test


>YES
Test passed.
passed step 29
failed step 37

jammed step 30
did not jam step 31
GSP05 (CSP10)
CM SBsyMC
major (continued)
>\RELEASE JAM
RTIF response:
RELEASE JAM DONE.
At the MAP terminal

Note: A dot or EccOn under the synchronization header means that the CM is
in synchronization. The word no means that the CM is not in synchronization.
If the CM Do
297-2651-543 Standard 05.01 March 1999

CM SBsyMC
major (continued)

>SYNC
If the response Do

successful
indicates The CPUs are out of step 33
sync due to a problem with
mismatches. Review the
mismatch logs should
before re-syncing.
”Y”, or ”NO”, ”N”)
(SuperNode and SuperNode SE
Series 70 only)
33 (SuperNode and SuperNode SE Series 70 only)

>NO
Go to step 37.
34 Determine if the SBsyMC major alarm cleared.
If the alarm Do
cleared step 38
GSP05 (CSP10)
CM SBsyMC
major (continued)
(end)
35 Perform the procedure How to clear a CM MC Tbl minor alarm in this

document.
36 Perform the appropriate alarm clearing procedure in this document.
297-2651-543 Standard 05.01 March 1999

CM SLMLIM
major
Alarm display
SLMLIM . . . . . . . . .
M
Indication
At the CMMNT level of the MAP display, SLMLIM appears under the CM
header of the alarm banner. The SLMLIM indicates an image size major
alarm.
Meaning
The image is too large to transfer to tape for the system load module (SLM).
The two computing module (CM) loads of this size will not fit on the SLM
disk.
Result
The problem does not now affect subscriber service. If a critical switch
process requires additional memory and cannot obtain the additional
memory, a warm or cold restart can occur.
Common procedures
Action
procedure.
GSP05 (CSP10)
CM SLMLIM
major (continued)
Summary of Clearing a CM SLMLIM major alarm

logs procedure.

level of support
End
297-2651-543 Standard 05.01 March 1999

CM SLMLIM
majormajor
(continued)
(end)
Clearing a CM SLMLIM major alarm
At the MAP
GSP05 (CSP10)
CM SLMLim
minor
Alarm display
SLMLim . . . . . . . . .
M
Indication
At the CMMNT level of the MAP display, SLMLim appears under the CM
header of the alarm banner. The SLMLim indicates an image minor alarm.
Meaning
The image is too large to transfer to tape for a system load module (SLM).
Two loads for a computing module (CM) of this size will not fit on the SLM
disk.
Result
The problem does not immediately affect subscriber service. If a critical
switch process requires and cannot obtain additional memory, a warm or
cold restart occurs.
Common procedures
Action
procedure.
297-2651-543 Standard 05.01 March 1999

CM SLMLim
minor (continued)
Summary of Clearing a CM SLMLim minor alarm

logs procedure.

level of support
End
GSP05 (CSP10)
CM SLMLim
minor (continued)
(end)
Clearing a CM SLMLim minor alarm
At your Current Location
297-2651-543 Standard 05.01 March 1999

CM SRAMFL
major
Alarm display
SRAMFL . . . . . . . . .
M
Indication
At the MTC level of the MAP display, SRAMFL appears under the CM
header of the alarm banner. The SRAMFl indicates that the system reached
a parity trap threshold for static random access memory (SRAM).
Note: This alarm does not apply to offices with the SR70 version of Bell
Northern Research (BNR) reduced instruction set computers (BRISC).
Meaning
The number of occurrences of SRAM parity traps on the computing module
(CM) CPU card reached the threshold for the 48-h software counter. This
condition indicates a potentially serious hardware problem.
Result
The problem does not affect subscriber service. The damaged hardware
requires replacement.
Common procedures
This procedure refers to Activity switch with memory match.
Action
procedure.
GSP05 (CSP10)
CM SRAMFL
major (continued)
Summary of Clearing a CM SRAMFL major alarm

Query the procedure.
SRAM software
counters Use the instructions that follow
procedure.
Perform activity
Is the alarm on Y 1
switch
the active CM?
procedure
1 N
Drop
synchronization
N
DPSYNC
command 2
passed?
Y
Replace NT9X13
CPU card
Clear SRAM
software
counters
N
Contact next
Synchronization 2 level of support
passed?
Y
End
297-2651-543 Standard 05.01 March 1999

CM SRAMFL
major (continued)
Clearing a CM SRAMFL major alarm
At the MAP terminal
1 To access the SRAMCNT level of the MAP display, type
>SRAMCNT
SRAMCNT:
2 To display the SRAM fault counter values, type

>QUERYCNT
Query SRAM fault counters
–––––––––––––––––––––––––
Counter/Threshold Value
––––––––––––––––– –––––
act24 2
act48 2
inact24 0
inact48 0
dsdiff24 1
dsdiff48 2
minoralarm 1
preventrex 1
preventsync 2
preventswact 1
3 Note the values of counters act48 and inact48.
4 To exit from the SRAMCNT level of the MAP display, type

>QUIT
GSP05 (CSP10)
CM SRAMFL
major (continued)
5 Determine if the reason for the alarm is the active or inactive CM. To determine
the reason, note if act48 or inact48 shows a minimum value of two.
If the alarm Do
is on the active CM step 6

is on the inactive CM step 7
6 Perform the procedure Activity switch with memory match in this document.
297-2651-543 Standard 05.01 March 1999

CM SRAMFL
major (continued)
7 To determine if the inactive central processing unit (CPU) jammed, access the
CM level of the MAP display. Type
>MAPCI;MTC;CM
0 no cpu 1 . . yes . . . .
If the CPU Do
jammed step 10
did not jam step 8

8
CAUTION
Loss of service
the active CPU.
CAUTION
Loss of service
the active CPU.

>\JAM
GSP05 (CSP10)
CM SRAMFL
major (continued)
RTIF response:

>YES
RTIF response:
JAM DONE
At the MAP display

The word no means that the CM is not in sync. In the example in step 7, the
CM is not in sync.
If the CM Do
is in sync step 11

>DPSYNC
If the response Do

CPU n active.
The inactive CPU is
JAMMED.
”Y”, ”NO”, or ”N”):

>YES
297-2651-543 Standard 05.01 March 1999

CM SRAMFL
major (continued)

If A1 Do
flashes step 14
14 Replace the NT9X13 card on the inactive CPU. Perform the correct procedure
point.
>\RELEASE JAM
RTIF response:
JAM RELEASE DONE
At the MAP terminal

16 To set the values of the SRAM inactive 24- and 48-h software counters to zero,
type
>SRAMCNT;CLEARCNT INACT
The inact counter will be cleared by this
command. Do you wish to continue ?

>SYNC
GSP05 (CSP10)
CM SRAMFL
major (continued)
(end)
MAP response:
If the response Do

successful

>YES
Go to step 20.
297-2651-543 Standard 05.01 March 1999

CM SramFl
minor
Alarm display
SramFl . . . . .
. . .
Indication
At the MTC level of the MAP display, SramFl appears under the computing
module (CM) header. The SramFl indicates a static RAM (SRAM) fault
minor alarm.
Note: This alarm does not apply to offices with the SR70 version of BNR
reduced instruction set computers (BRISC).
Meaning
A 48-h software counter reached a specified threshold. The system
generated a CM168 log to indicate the level of SRAM faults. Set thresholds
for SRAM faults to prevent potential power failures.
Result
There is no result.
Common procedures
Action
procedure.
GSP05 (CSP10)
CM SramFl
minor (continued)
Summary of Clearing a CM SramFl minor alarm
Query the This flowchart summarizes the

system SRAM procedure.
counts
Note the procedure.
values for all
counts
Monitor the
counts for 48 h
End
297-2651-543 Standard 05.01 March 1999

CM SramFl
minor
minor
(continued)
(end)
Clearing a CM SramFl minor alarm
At the MAP display
1 To access the SRAMCNT level of the MAP display, type
>SRAMCNT
SRAMCNT:
2 To display the SRAM fault counter values, type

>QUERYCNT
Query SRAM fault counters
–––––––––––––––––––––––––
Counter/Threshold Value
––––––––––––––––– –––––
act24 2
act48 2
inact24 0
inact48 0
dsdiff24 1
dsdiff48 2
minoralarm 1
preventrex 1
preventsync 2
preventswact 1
3 Note the values that appear for each count in the upper part of the display.
4 To exit from the SRAMCNT level of the MAP display, type

>QUIT
5 Allow the alarm to remain for a 48-h period. If the system does not detect more
faults, the alarm clears. If additional SRAM faults occur, a CM169 log and an
SRAM major alarm appears.
GSP05 (CSP10)
CM StrAlc
critical
Alarm display
StrAlc . . . . . .
Indication
At the MTC level of the MAP display, StrAlc appears under the CM header
of the alarm banner. The StrAlc indicates a critical alarm for storage
allocation.
Meaning
The used data store exceeds the maximum data store threshold. The used
program store exceeds the maximum program store threshold. The current
image size exceeds the maximum image size.
Result
The problem does not affect subscriber service. A critical switch procedure
can require additional memory. If the procedure requires additional memory
and cannot obtain the memory, a warm or cold restart can occur.
Common procedures
Action
procedure.
297-2651-543 Standard 05.01 March 1999

CM StrAlc
Summary of Clearing a CM StrAlc critical alarm

logs procedure.

level of support
End
GSP05 (CSP10)
CM StrAlc
(end)
Clearing a CM StrAlc critical alarm
1 Obtain all the latest CM logs.
297-2651-543 Standard 05.01 March 1999

3-263 Ext critical alarm 3-263
MCCNACK
Alarm display
. . . . . . . MCCNACK .
Indication
The MCCNACK alarm is an Advice of Charge (AOC) alarm, supported for
German PRI, ETSI PRI, and Italian PRI trunks. Sub–services added to AOC
implementation are AOC-D (Advice of Charge during the call) and AOC-E
(Advice of Charge at the end of a call).
The MCCNACK alarm is raised if the XPM does not respond to a query or
switchover during a changeover. The alarm also appears in the EXT level of
the MTC.
Meaning
Approximately ten minutes before a tariff changeover occurs, a Switch Over
Request message is sent to the relevant DTCOIs. The message gives the
PDTCs information necessary to prepare for the changeover. The PDTC
sets a timer and tries to changeover after the timer expires. If this fails,
the CM tries again to send the Switch Over Request message. If the second
attempt fails, a critical alarm MCCNACK is raised.
Impact
The message to central control is not acknowledging the (MCCNACK)
alarm, and indicates that at least one peripheral has not responded to a
metering Time of Day (TOD) changeover request. Billing information is
being lost. The alarm will continue until the problems with the XPM are
resolved.
Common procedures
Not applicable.
Action
The following flowchart is only a summary of this procedure. Use the
the alarm.
GSP05 (CSP10)
3-264 Ext critical alarm
MCCNACK (continued)
Summary of clearing a MCCNACK alarm
N0 This flowchart summarizes the

procedure.

flowchart to perform the
procedure.
Wait five Inform

minutes for personnel at
alarm to clear. the next level
Determine if of support that
MCCNACK has MCCNACK is
cleared. present.
297-2651-543 Standard 05.01 March 1999

Ext critical alarm 3-265
MCCNACK
MCCNACK (end)
(continued)
Clearing a MCCNACK alarm
1
Contact next level of support.
GSP05 (CSP10)
4-1
Procedures to clear an external alarm

Introduction
This chapter provides procedures to clear external alarms. External alarms
appear under the EXT header of the alarm banner in the MAP display. Each
procedure contains the following sections:
• Alarm display
• Indication
• Meaning
• Result
• Action
Alarm display
Indication
• the location of the alarm indication
• the alarm appearance
• the alarm intensity
Meaning
Result
GSP05 (CSP10)
Common procedures
This section lists common procedures used during the procedure to clear an
alarm. A common procedure is a series of steps repeated within
maintenance procedures, for example, the removal and replacement of a
card. The common procedures chapter in this Northern Telecom publication
describes common procedures.
Do not go to a common procedure unless the step-action procedure directs

you to go.
Action
This procedure contains a flowchart and a list of steps. Use the flowchart to
review the procedure. Follow the steps to perform the procedure.
297-2651-543 Standard 05.01 March 1999

Ext Crit
critical
Alarm display
. . . . . . . . 1Crit .
*C*
Indication
At the MTC level of the MAP display, Crit (preceded by a number) appears
under the Ext header of the alarm banner. Crit indicates a critical external
alarm.
Meaning
The alarm determines the meaning of the Crit alarms. Refer to the “Result”
section.
The number that precedes Crit indicates the number of critical alarms.
Result
An alarm for an automatic message accounting failure (AMAFAIL)
indicates that the system does not record billing information. The alarm
does not affect subscriber service.
The critical power (CRPWR) alarm indicates that a critical fault is present in
the power equipment of the DMS switch. Power equipment that supplies
main or emergency power to the DMS switch can generate this alarm. The
alarm does not affect subscriber service unless main and emergency power
sources fail. If main and emergency power sources fail, all subscribers lose
service.
The dead system (DEADSYSM) alarm indicates that a critical alarm scan
point (scannm) changed state. The alarm only occurs if you set the alarm
through ALMSC.
The line load control alarm (LLC_ALARM) indicates that line load control
was activated at the MAP terminal. An office uses line load control to
control a processor overload caused by a period of unusually high traffic.
When line load control is active, calls made to subscribers with the essential
line (ELN) service option have first priority. Calls made to lines that do not
have ELN service experience a delay in reception of a ringing tone.
GSP05 (CSP10)
Ext Crit
The message to central control not acknowledged (MCCNACK) alarm
indicates a peripheral failure. The alarm indicates that at least one
peripheral did not respond to a metering time-of-day changeover request.
This alarm indicates a loss of billing information.
The no call processing alarm (NCPALARM) indicates that the switch does
not process calls. All subscribers lose service.
The operational measurements critical alarm (OMCRITICAL) indicates that

the OM critical alarm index reached the threshold within the scan period.
The power fault previous floor (PFPREFLR) alarm indicates that a critical
fault is present on a lower floor of the building. The result of this alarm
depends on the configuration of your office.
The power fault succeeding floor (PFSUCFLR) alarm indicates that a

critical fault is present on a higher floor of the building. The impact of this
alarm depends on the configuration of your office.
A voice relay critical alarm (VR1_CRITICAL) indicates that no datalinks

are available to the TOPSVR1 application in table MPCFASTA.
A voice relay critical alarm (VR2_CRITICAL) indicates that no datalinks

are available to the TOPSVR2 application in table MPCFASTA.
The voice services node critical alarm (VSN_CRIT_ALM) indicates that a

critical error condition occurred in the voice services node. The alarm does
not affect service.
The voice services node no links (VSN_NO_LINKS) alarm occurs when all
logical datalinks to a voice services node are out of service. When all
logical datalinks are out of service, the system routes Automated Alternate
Billing Service (AABS) calls through the operator.
Common procedures
Action
297-2651-543 Standard 05.01 March 1999

Ext Crit
Summary of Clearing an Ext Crit critical alarm
List alarms This flowchart summarizes the

procedure.

procedure.
Follow the
appropriate
procedure
End
GSP05 (CSP10)
Ext Crit
Clearing an Ext Crit critical alarm
At the MAP terminal

>MAPCI;MTC;EXT
1 0 1 0 12
2 To list the critical external alarms, type

>LIST CRIT
AMAFAIL
3 Determine the name of the first critical external alarm on the list.
If the first alarm Do
is AMAFAIL step 6
is CRPWR step 4
is CRITEQUIP step 4
is DEADSYSM step 21
is LLC_ALARM step 18
is MCCNACK step 27
is MCPALARM step 4
is OMCRITICAL step 21
is PFSUCFLR step 4
is VR1_CRITICAL step 21
is VR2_CRITICAL step 21
is VSN_CRIT_ALM step 21
is VSN_NO_LINKS step 21
297-2651-543 Standard 05.01 March 1999

Ext Crit
4 Use the procedures supplied with your power equipment to find and fix the fault.
5 Go to step 26.
6 Determine if the system displays an IOCOS, DDUOS, or MTDOS alarm, or an

AMA-related alarm. These alarms appear under the IOD header of the MAP
display.
If an IOD alarm Do
appeared step 7
did not appear step 8
7 Perform the correct procedure in this document. Complete the procedure and
8 To start the AMA process again, type

>AMARESTART
MAP response:
THIS COMMAND WILL CAUSE DEAD RECORDING PROCESSES FOR ALL
STREAMS TO BE RESTARTED. DO YOU WISH TO PROCEED?

>Y
CALL RECORDING PROCESS ALREADY RUNNING FOR STREAM: AMA
CALL RECORDING PROCESS ALREADY RUNNING FOR STREAM: SMDR
10 Determine if the AMAFAIL alarm cleared.
If the AMAFAIL alarm Do
cleared step 11
GSP05 (CSP10)
Ext Crit
11 Record the action taken to clear the alarm in the office log.
Go to step 26.
12 Determine if your office connects to a telephone-network operating system

(TNOS).
If your office Do
connects step 13
does not connect step 28
13 To access the TNOS software, type

>TNOS
14 To determine if throttling is ON, type

>FTSTA SCHEDULE
If throttling Do
is ON step 28
is OFF step 15
15 Determine if the AMAFAIL alarm occurred during a period of high traffic.
If the AMAFAIL alarm Do
occurred during a period of high traffic step 16

did not occur during a period of high step 28
traffic
297-2651-543 Standard 05.01 March 1999

Ext Crit
16 To activate throttling of TNOS for high-traffic periods, type

>FTSCH ENABLE starthour startmin endhour endmin
where
starthour is a number from 01 to 23 that indicates the hour at which
throttling is to begin
startmin is a number from 01 to 59 that indicates the minute at which
throttling is to begin
endhour is a number from 01 to 23 that indicates the hour at which
throttling is to end
endmin is a number from 01 to 59 that indicates the minute at which
throttling is to end
Example input:
>FTSCH ENABLE 14 03 23 04
17 Determine if the AMAFAIL alarm continues to occur during high-traffic periods.
If the alarm Do
continues to occur during high-traffic step 28

periods
does not continue to occur during step 25
high-traffic periods
18 Determine if you can deactivate the line load control.
If you Do
have permission step 19

do not have permission step 28
19 To deactivate the line load control, type

>LLC OFF
LINE LOAD CONTROL IS OFF
GSP05 (CSP10)
Ext Crit
20 Determine if the LLC_ALARM alarm cleared.
If the LLC_ALARM alarm Do
cleared step 25
21 Determine if the system generated an EXT103 or an EXT108 log.
If the system Do
generated an EXT103 or an step 22

EXT108 log
did not generate an EXT103 or an step 28
EXT108 log
22 Determine if the alarm turned OFF.

Example of a log report:
EXT108 APR01 09:13:48 425 INFO VSN_CRIT_ALM OFF
LANLINK_FAILURE 1
Note: The word OFF is on the right side of the alarm name. The word OFF
indicates that the alarm turned OFF.
If the alarm Do
turned OFF step 25

did not turn OFF step 23
23 Wait 30 min. Determine if the system generated an EXT103 or an EXT108 log.
If the system Do
generated an EXT103 or an step 24

EXT108 log
did not generate an EXT103 or an step 28
EXT108 log
297-2651-543 Standard 05.01 March 1999

Ext Crit
critical
critical
(continued)
(end)
If the alarm Do
turned OFF step 25

25 To list the critical external alarms, type

>LIST CRIT
26 Determine if the EXT Crit critical alarm cleared.
If the alarm Do
cleared step 29
changed to a lower number step 2
(for example, changed from 2Crit
to 1Crit)
27 Inform the next level of support that an MCCNACK alarm is available. Wait
5 min. Determine if the MCCNACK alarm cleared.
If the MCCNACK alarm Do
cleared step 29
GSP05 (CSP10)
Ext Maj
major
Alarm display
. . . . . . . . 1Maj .
M
Indication
At the MTC level of the MAP display, Maj (preceded by a number) appears
under the Ext header of the alarm banner. The Maj indicates a major
external alarm.
Meaning
The meaning of this alarm depends on the alarm. Refer to the Result
section.
The number that precedes Maj indicates the number of major alarms.
Result
The alarm and battery maintenance trunk module fail (ABMTMFL) alarm
indicates that a fault is present in the dead system alarm (DSA) card. The
DSA card is present in the backup maintenance trunk module (MTM). The
alarm does not affect subscriber service.
The alarm and battery office alarm unit fail (ABOAUFL) alarm indicates
that a fault is present. The primary office alarm unit (OAU) card contains
the fault. The OAU card is in the backup maintenance trunk module
(MTM). The alarm does not affect subscriber service.
297-2651-543 Standard 05.01 March 1999

Ext Maj
major (continued)
The alarm and battery supply fail (ABSFAIL) alarm indicates that a fault is
present. The fault is present in the alarm and battery voltage supply of the
power distribution center (PDC) frame. The alarm does not affect subscriber
service.
The digital recorded announcement machine (DRAM) fail (DRAMALRM)

alarm indicates one of the following conditions:
• The DRAM fails to return the message that the central control (CC) sent.
• The queue audit for the idle terminal linkage blocks (TLB) encounters a
condition that is not planned.
• The CC cannot communicate with the DRAM.
• A power loss is present on the DRAM.
The Emergency 911 automatic location identifier major

(E911_ALI_MAJOR) alarm indicates a multiprotocol controller (MPC) link
failure. The failure can occur in the asynchronous multiprotocol controller
(MPC) link to the automatic location identifier (ALI) controller. The failure
also can occur in both MPC links to an open interface ALI controller. No
ALI information is available to the line or automatic call distribution public
safety answering point (ACD PSAP) operators served by the database.
The Emergency 911 remote call event records major

(E911_RCER_MAJOR) alarm indicates a problem. The problem occurs in
all of the MPC links to a remote location. This location prints records of
calls to the exact public safety answering point (PSAP). The MPC links
failed. This alarm does not affect the records of events, logs, and calls
generated at the E911 tandem location.
A malicious call trace (MCTALARM) alarm indicates that a malicious call

trace occurs on the line of a subscriber.
A metering backup (METBCK) alarm indicates a problem with the backup

file used for metering. The Device Independent Recording Package (DIRP)
subsystem uses the backup file for metering. The METBCK alarm indicates
that the system did not mount the DIRP. The metering system does not have
a backup. Billing-related data are in jeopardy.
A major previous floor (MJPREFLR) alarm indicates that a major fault is

present on a lower floor of the building. The impact of an MJPREFLR
alarm depends on the configuration of your office. The impact of the alarm
also depends on the items that your company chose to trigger the alarm.
GSP05 (CSP10)
Ext Maj
major (continued)
A major power (MJPWR) alarm indicates that a major power fault is present
in the equipment that supplies power to the DMS switch. The fault only
affects subscriber service if a failure is present in both main and emergency
power supplies.
A major succeeding floor (MJSUCFLR) alarm indicates that a major fault is

present on a higher floor of the building. The impact of an MJSUCFLR
alarm depends on the configuration of your office. The alarm result also
depends on the items that your company chose to trigger the alarm.
A major operational measurements (OM) buffered reports (OMBRFAIL)

alarm indicates an output device failed during a write operation. The alarm
The OM major alarm (OMMAJOR) indicates that the OM major alarm

index reached the threshold within the scan period.
The post autoapply sanity (POST_AUTOAPP_SAN) alarm indicates an

exceeded log count. The number of specified logs during the POSTMON
period after the autoapply process exceeds the allowed number. The
following conditions can cause this alarm.
• The switch detects a maintenance condition not related to the autoapply
process. The type of logs, and the number of the logs, identifies the
affect on subscriber service.
• The counted logs include information-only logs and other low-priority
logs. Subscriber service is not affected.
• The number of logs allowed during a POSTMON period may be too low.
Subscriber service is not affected.
A power distribution center failure (PDCFAIL) alarm indicates that a power

fault is present in a power distribution center (PDC) frame. The fault only
affects subscriber service if the fault interrupts power to a shelf that does not
have backup power supply.
An SL-100 link error (SLLNKERR) alarm indicates that data transfer

stopped. A data transfer stop interrupts subscriber service.
A Traffic operator position system personal audio response system

application (TOPS_PARS_APPL) alarm indicates a problem with (MPC)
datalinks. The alarm indicates that all MPC datalinks for the TOPS_PAR
are out of service. The alarm does not affect subscriber service.
297-2651-543 Standard 05.01 March 1999

Ext Maj
major (continued)
A voice alarm (VCEALM) indicates that a fault is present in analog
recorded announcement machine that connects to a DMS switch. The
analog recorded announcement machine does not have a DMS switch.
Subscribers do not receive recorded announcements.
A voice services node major alarm (VSN_MAJ_ALM) indicates a major

error condition. The alarm indicates that a major error condition occurred or
is resolved in the voice services node. The alarm does not affect subscriber
service.
Common procedures
Action
GSP05 (CSP10)
Ext Maj
major (continued)
Summary of Clearing an Ext Maj major alarm

procedure.

Follow the procedure.
correct
procedure
End
297-2651-543 Standard 05.01 March 1999

Ext Maj
major (continued)
Clearing an Ext Maj major alarm
At the MAP terminal

>MAPCI;MTC;EXT
1 0 1 0 12
2 To list the major alarms, type

>LIST MAJ
DRAMALRM
GSP05 (CSP10)
Ext Maj
major (continued)
3 Determine the name of the first major external alarm on the list.
is ABMTMFL step 69
is ABOAUFL step 81
is ABSFAIL step 23
is DRAMALRM step 97
is E911_AU_MAJOR step 25
is E911_RCER_MAJOR step 25
is MCTALARM step 96
is METBCK step 68
is MJPWR step 27
is MJPREFLR step 27
is MJSUCFLR step 27
is OMBRFAIL step 104
is OMMAJOR step 80
POST_AUTOAPP_SAN step 4
POST_AUTOPROC_SA step 4
is PDCFAIL step 23
is SLLNKERR step 29
is TOPS_PARS_APPL step 21
is VCEALM step 27
is VSN_MAJ_ALM step 97
297-2651-543 Standard 05.01 March 1999

Ext Maj
major (continued)
4
ATTENTION
Follow office policy when you troubleshoot and correct any
maintenance condition. If necessary, contact the next level of
support.
Review recent logs for any maintenance condition not related to the autoapply
process.
If recent logs Do
indicate a maintenance condition Perform the correct procedure to

clear the maintenance condition.
When completed, go to step 19.
do not indicate a maintenance step 5
condition
5 Access table AUTOMON by typing

>TABLE AUTOMON
GSP05 (CSP10)
Ext Maj
major (continued)
6 List the table by typing

>LIS ALL
NAME LOGNUM
–––––––––––––
LOST 101
LOST 104
LOST 105
LOST 106
MM 100
CM 103
CM 111
CM 112
CM 116
CM 119
CM 122
CM 125
AUDT 101
AUDT 102
AUDT 397
AUD 395
7 Review the contents of the table for any information-only logs or low-priority
logs.
If table AUTOMON Do
lists any information-only or step 8

low-priority logs that can deleted
from the table
does not list any information-only step 10
or low-priority logs that can be
deleted from the table
297-2651-543 Standard 05.01 March 1999

Ext Maj
major (continued)
8
ATTENTION
Check office policy before you delete any logs from table
AUTOMON. You may have to add the logs to table AUTOMON
at a later date.
Delete the log from the table by typing

>DEL logname_lognum
where
logname_lognum is the name and number of the log
9 Repeat step 8 for each log to be deleted from the table.
10 Quit the table by typing

>QUIT
If you Do
deleted any logs from table step 19

AUTOMON
did not delete any logs from table step 11
AUTOMON
11 Access table AUTOOPTS by typing

>TABLE AUTOOPTS
12 List the table by typing

>LIS ALL
KEY FILEALRM APPROVAL MONDATA DURATION MAXATMPT
DROPSYNC MONDAY TUESDAY WEDNSDAY THURSDAY FRIDAY SATURDAY SUNDAY
MNTTIME
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
AUTOOPTS N N Y T15 T15 15 30 $
N 2300 2300 2300 2300 2300 2300 2300
2315
GSP05 (CSP10)
Ext Maj
major (continued)
13
ATTENTION
Check office policy before you change the percentage increase for
allowed logs.
Change the percentage increase to allow for logs before an EXT MAJ alarm by
typing
>CHA
14 Press Enter to scroll through the fields until you receive the MONLIMIT prompt.
15 Record the current value in MONLIMIT. This value is the percentage increase
that is allowed for logs before an EXT MAJ alarm.
16 Enter the new percentage increase by typing

>percent_increase
where
percent_increase is a number between 1 and 100
17 Confirm the change by typing
>Y
18 Quit the table by typing

>QUIT
At the EXT level of the MAP display
19 Release the alarm by typing
>SETSC alarm_name REL
where
alarm_name is POST_AUTOAPP_SAN or POST_AUTOPROC_SA
20 Go to step 105.
21 Perform the correct procedure in the corresponding Maintenance Manual..

22 Go to step 101.
297-2651-543 Standard 05.01 March 1999

Ext Maj
major (continued)
23 A power fault is present in the PDC frame. Perform the procedure Clearing an
Ext FSP PDC frame major alarm in this document. Complete the procedure
and return to this point.
24 Go to step 101.
25 Perform the correct procedure in this document and return to this point.
26 Go to step 101.
28 Go to step 101.
29 Determine if the system generated an SLNK103 log.
If the system Do
generated an SLNK103 log step 30

did not generate an SLNK103 log step 104
30 Determine the device in error.

Note: The SLNK log report lists the name of the failed device.
Example of an SLNK103 log report:
SLNK103 Jun12 02:03:47 1991 INFO SESSION
SMDR Reports transfer stopped on device MRLINK
31 To access table TERMDEV, type

>TABLE TERMDEV
32 To position on the device, type

>POSITION dev_type
where
dev_type is the name of the device that you determined in step 30
33 Record the input/output controller number (listed under the IOCNO header),
and card number (listed under the CKTNO header).
GSP05 (CSP10)
Ext Maj
major (continued)
34 To quit from table TERMDEV, type

>QUIT
35 To access table SLLNKDEV, type

>TABLE SLLNKDEV
36 To position on the device, type

>POSITION dev_type
where
37 Record the link transfer type (listed under the XFERS header).
38 To quit from table SLLNKDEV, type

>QUIT
39 To access the link utility, type

>LNKUTIL
40 To stop the transfer of data, type

>DEVSTOP dev_type xfer_type
where
xfer_type is the transfer type that you determined in step 37
41 To stop the device, type

>DEVDISC dev_type KILL
where
297-2651-543 Standard 05.01 March 1999

Ext Maj
major (continued)
42 To access the IOD level of the MAP display, type

>IOD
IOD
IOC 0 1 2 3
STAT . S . S
DIRP: AMA B XFER: . NOP : . SLM : SLMbsy DVI : .

DPPP: . DPPU: . NX25: . MLP : . SCAI: .
CDR : .
43 To access the IOC level of the MAP display for the device, type
>IOC ioc_no
where
ioc_no is the IOC number that you recorded in step 33
IOC CARD 0 1 2 3 4 5 6 7 8
1 PORT 0123 0123 0123 0123 0123 0123 0123 0123 0123
STAT C––– P––– C–CC P––– CC–– P––– –C–C P––– ––––
TYPE MTD DDU CONS MPC CONS MPC CONS MPC
44 To access the Card level of the MAP display, type

>CARD card_no
where
card_no is the circuit number that you recorded in step 33
Card 2 Ckt 0 1 2 3
Status CS BUSY – CS BUSY CS BUSY
Cons Id RV120 TEAM1 CRTCOML3
ConType VT100 VT100 VT100
GSP05 (CSP10)
Ext Maj
major (continued)
45 To determine the syntax needed to manually busy the card, type

>HELPBSY
Card 3 Unit 1
User System Board LINK0 LINK1 LINK2 LINK3
Status Ready COMACT UNEQ UNEQ ENABLD ENABLD
46 To manually busy the circuit that corresponds to the device, type one of the
following:
>BSY circuit
>BSY link
Note: Syntax for the BUSY command varies according to the type of device
controller card.
where
circuit is the number of the circuit (0 to 3)
link is the number of the link (0 to 3)
47 To determine the syntax needed to offline the card, type

>HELP OFFL
48 To put the circuit offline, type one of the following:

>OFFL circuit
>OFFL link
and press the Enter.
Note: Syntax for the OFFLINE command varies according to the type of device
controller card.
where
297-2651-543 Standard 05.01 March 1999

Ext Maj
major (continued)
49 To manually busy the circuit, type one of the following:

>BSY circuit
>BSY link
where
50 To determine the syntax needed to return the card to service, type

>HELP RTS
Note: Syntax to return the card to service varies according to the type of
device controller card.
51 To return the circuit to service, type one of the following:

>RTS circuit
>RTS link
where
52 To access the CI level of the MAP display, type

>QUIT ALL
53 To access the link utility, type

>LNKUTIL
54 To start a session on the datalink, type

>DEVCON dev_type
where
dev_type is the name of the device that you recorded in step 30
GSP05 (CSP10)
Ext Maj
major (continued)
55 To start data transmission, type

>DEVSTART dev_type xfer_type
where
dev_type is the name of the device that you recorded in step 30
xfer_type is the transfer type that you determined in step 37

>MAPCI;MTC;EXT
57 To list the major alarms, type

>LIST MAJ
58 Determine if the SLLNKERR alarm is present.
If the SLLNKERR alarm Do
is present step 59
59 To stop the transfer of data, type

>DEVSTOP dev_type xfer_type
where
dev_type is the device that you recorded in step 30
xfer_type is the transfer type that you recorded in step 37
60 To stop the device, type

>DEVDISC dev_type KILL
where
dev_type is the device that you recorded in step 30

>IOD
297-2651-543 Standard 05.01 March 1999

Ext Maj
major (continued)
62 To access the IOC level of the MAP display for the device, type
>IOC ioc_no
where
ioc_no is the IOC number for the device that you recorded in step 33
63 To access the Card level of the MAP display, type

>CARD card_no
where
card_no is the circuit number that you recorded in step 33
64 To determine the syntax needed to manually busy the card, type

>HELP BSY
65 To manually busy the circuit that corresponds to the device, type one of the
following:
>BSY circuit
>BSY link
Note: Syntax for the BUSY command varies according to the type of device
controller card.
where
66 To determine the syntax needed to put the card offline, type

>HELP OFFL
GSP05 (CSP10)
Ext Maj
major (continued)
67 To put the circuit offline, type one of the following:

>OFFL circuit
>OFFL link
Note: Syntax for the OFFLINE command varies according to the type of device
controller card.
where
link is the number of the circuit (0 to 3)
Go to step 104.
68 Mount the backup volume in the DIRP subsystem. After the backup process
runs, the METBCK alarm clears automatically or manually. To manually clear
the METBCK alarm, execute the Mstore command at the MTRSYS level of the
MAP display.
Go to step 102.
69 To access table ALMSD, type

>TABLE ALMSD
70 To position on the tuple for the signal distributor (SD) point MTMFAIL, type
>POSITION MTMFAIL
MTMFAIL 1 0 1 N N
71 To display the table headings, positioned on the SD point tuple, type

>LIST
FUNCTION SDGROUP POINT NORMALST AUDIBLE LAMPTEST
––––––––––––––––––––––––––––––––––––––––––––––––
MTMFAIL 1 0 1 N N
72 Record the SD point group number.

Note: The SD point group number appears under the SDGROUP heading.
297-2651-543 Standard 05.01 March 1999

Ext Maj
major (continued)
73 To quit from table ALMSD, type

>QUIT
74 To access table ALMSDGRP, type

>TABLE ALMSDGRP
75 To position on the SD point group number tuple, type

>POSITION sdgroup_no
where
sdgroup_no is the SD point group number that you recorded in step 72
1 MTM 1 0 3X82AA
76 Display the table headings positioned on the SD point group number tuple. To
display the table headings, type
>LIST
SDGROUP TMTYPE TMNO TMCDTNO CARDCODE
––––––––––––––––––––––––––––––––––––
1 MTM 1 0 3X82AA
77 Record the TMTYPE, TMNO, and CARDCODE for the MTM.
78 To quit from table ALMSDGRP, type

>QUIT

>PM
SysB ManB OffL CBsy ISTb InSv
PM 0 0 1 9 0 0
GSP05 (CSP10)
Ext Maj
major (continued)
80 To determine the state of the MTM, type

>POST MTM mtm_no
where
mtm_no is the TMNO that you recorded in step 77
If the MTM Do
is CB sy or SysB step 95
is not CB sy or SysB step 93
81 To access table ALMSD, type

>TABLE ALMSD
82 To position on the tuple for the SD point OAUFAIL, type

>POSITION OAUFAIL
OAUFAIL 1 0 1 N N
83 Display the table headings, positioned on the SD point tuple. To display the
table headings, type
>LIST
FUNCTION SDGROUP POINT NORMALST AUDIBLE LAMPTEST
––––––––––––––––––––––––––––––––––––––––––––––––
OAUFAIL 1 0 1 N N
84 Record the SD point group number.

Note: The SD point group number appears under the SDGROUP heading.
85 To quit from table ALMSD, type

>QUIT
297-2651-543 Standard 05.01 March 1999

Ext Maj
major (continued)
86 To access table ALMSDGRP, type

>TABLE ALMSDGRP
87 To position on the SD point group number tuple, type

>POSITION sdgroup_no
where
sdgroup_no is the SD point group number that you recorded in step 84
1 OAU 1 0 3X82AA
88 Display the table headings, positioned on the SD point group number tuple. To
display the table headings, type
>LIST
SDGROUP TMTYPE TMNO TMCDTNO CARDCODE
––––––––––––––––––––––––––––––––––––
1 OAU 1 0 3X82AA
89 Record the TMTYPE, TMNO, and CARDCODE for the OAU.
90 To quit from table ALMSDGRP, type

>QUIT

>PM
SysB ManB OffL CBsy ISTb InSv
PM 0 0 1 9 0 0
GSP05 (CSP10)
Ext Maj
major (continued)
92 To determine the state of the OAU, type

>POST OAU oau_no
where
oau_no is the TMNO that you recorded in step 89
If the OAU Do
is CBsy or SysB step 95

is not CBsy or SysB step 93
93 To replace the card that you recorded in step 77 or step 89, perform the correct
94 Go to step 101.
95 Perform the correct procedure to clear a peripheral module alarm. Complete

Go to step 101.
96 To silence the alarm, type

>MAPCI;MTC;SIL
97 Determine if the system generated one of the following logs.
If the system Do
generated an EXT103 log step 98

generated an AUDT205 log step 103
generated a log other than listed step 104
here
297-2651-543 Standard 05.01 March 1999

Ext Maj
major (continued)

EXT107 APR01 09:13:48 425 INFO VSN_MAJ_ALM OFF
CNTRLNK_INTERFACE 1
Note: The word OFF appears on the right side of the alarm name. The word
OFF indicates that the alarm turned OFF.
If the alarm Do
turned OFF step 102

99 Wait 30 min. Determine if the system generated an EXT103 log, an EXT107

log or an EXT108 log.
If the system Do
generated a log step 100

did not generate a log step 104
If the alarm Do
turned OFF step 102

101 Determine if the TOPS_PARS_APPL alarm cleared.
If the alarm Do
cleared step 102

GSP05 (CSP10)
Ext Maj
major (continued)
(end)
102 Determine if the EXT Maj major alarm cleared.
If the alarm Do
cleared step 105

changed to a smaller number (for step 2
example, changes from 2Maj to
1Maj)
103 Refer to the correct log report and maintenance action in the Log Report
Reference Manual.
297-2651-543 Standard 05.01 March 1999

Ext Min
minor
Alarm display
. . . . . . . . 1Min .
Indication
At the MTC level of the MAP display, Min (preceded by a number) appears
under the Ext header of the alarm banner. The Min indicates a minor
external alarm.
Meaning
The meaning of the minor alarms depends on the exact alarm (see Result).
The number that precedes Min indicates the number of minor alarms.
Result
A BLUEBOX alarm indicates that system software detects a false attempt to
make a toll call with a bluebox. A bluebox is a tone generator. Blueboxes
allow persons to make toll calls that are not legal and do not incur toll
charges. The problem does not affect subscriber service.
An emergency 911 automatic location identifier minor (E911_ALI_MINOR)

alarm appears. The alarm indicates that the asynchronous multiprotocol
controller (MPC) link to an open interface automatic location identifier
(ALI) controller failed. Only one of the two redundant links in the ALI
interface can operate. The problem does not affect subscriber service.
An emergency 911 remote call event records minor (E911_RCER_MINOR)

alarm appears. The alarm indicates that one of the MPC links to a remote
location failed. Records of calls to the exact public safety answering point
(PSAP) print at the remote location. The problem does not affect subscriber
service.
An off-hook alarm for the emergency 911 public safety answering point
(E911_PSAP_OFFHK) indicates that a PSAP operator was off-hook. The
PSAP operator was off-hook and did not connect to another party for a time
that exceeds an office parameter setting. The PSAP operator cannot answer
incoming emergency calls. The problem can affect subscriber service.
GSP05 (CSP10)
Ext Min
minor (continued)
An alarm for the emergency 911 selective routing database memory
(E911_SRDB_MEMORY) indicates that one of the following conditions is
present:
• the selective routing database (SRDB) uses storage that exceeds a
specified percentage of the total store
• the free memory is below a specified value
• the number of tuples in the SRDB exceeds a specified value
The preceding conditions do not affect subscriber service.
A metering out-of-service (METOOS) alarm appears. The alarm indicates

that the out-of-service file on the device independent recording package
(DIRP) subsystem for metering is not mounted. You cannot withdraw the
allocation of software meter blocks.
A meter recycle (METXRCYL) alarm indicates a meter audit failed to clear

recycle meters. The alarm occurs after an image backup loads again.
A minor previous floor (MNPREFLR) alarm indicates that a minor power

fault is present on a lower floor of the building. The problem does not affect
subscriber service.
A minor power (MNPWR) alarm indicates that a minor fault is present in

the equipment that supplies power to the switch. The problem does not
affect subscriber service.
A minor succeeding floor (MNSUCFLR) alarm indicates that a minor power

fault is present on a higher floor of the building. The problem does not
affect subscriber service.
A minor alarm for operational measurements buffered reports

(OMBRSTOP) indicates that an output device fails during a read operation.
If you ignore the failure for an extended period, the disk buffer fills and all
operational measurements (OM) data goes unbuffered to the log system.
An OCDL_CONGESTION indicates a large volume of traffic on and along

the OCDL links.
An OCDL_SYSB alarm indicates an affected operator centralization from a

remote toll center to a host DMS TOPS toll center. A reduction of remote
links to the TOPS toll center occurred.
297-2651-543 Standard 05.01 March 1999

Ext Min
minor (continued)
An alarm for a traffic operator position system personal audio response
system link (TOPS_PARS_LINK) appears. The alarm indicates that an
MPC datalink for the TOPS_PARS application is out of service. The
problem does not affect subscriber service.
A traffic operator position system personal audio response system node

(TOPS_PARS_NODE) alarm indicates that all MPC datalinks to any PARS
application are out of service. The problem does not affect subscriber
service.
A minor alarm for the testline 101 (TSTLN101) indicates a call. The call
enters on a 101-type test line at a transmission test center (TTC). The
problem does not affect subscriber service.
A voice relay one (VR1_MINOR) alarm indicates that only one datalink is
available to the TOPSVR1 application in table MPCFASTA. The problem
A voice relay two (VR2_MINOR) alarm indicates that only one datalink is
available to the TOPSVR2 application in table MPCFASTA. The problem
A voice services node minor alarm (VSN_MIN_ALM) indicates that a

minor error condition occurs in the VSN. The alarm also indicates a
resolution of a problem in the VSN. The problem does not affect subscriber
service.
A voice services node one link (VSN_ONE_LINK) alarm appears. A VSN

alarm indicates that only one datalink in a set of two or more datalinks
attached to a VSN can operate.
Common procedures
Action
procedure.
GSP05 (CSP10)
Ext Min
minor (continued)
Summary of Clearing an Ext Min minor alarm

procedure.

appropriate
procedure
End
297-2651-543 Standard 05.01 March 1999

Ext Min
minor (continued)
Clearing an Ext Min minor alarm
At the MAP terminal

>MAPCI;MTC;EXT
Example of a MAP
0 0 0 1 11
2 To list the minor alarms, type

>LIST MIN
METXRCYL
GSP05 (CSP10)
Ext Min
minor (continued)
3 Determine the name of the first minor external alarm on the list.
is BLUEBOX step 13
is E911_ALI_MINOR step 10
is E911_PSAP_OFFHK step 10
is E911_RCER_MINOR step 10
is E911-SRDB_MEMORY step 10
is METOOS step 16
is METXRCYL step 17
is MNPREFLR step 8
is MNPWR step 6
is MNSUCFLR step 8
is OCDL_CONGESTION step 23
is OCDL_SYSB step 4
is OMBRSTOP step 23
is TOPS_PARS_LINK step 4
is TOPS_PARS_NODE step 4
is TSTLN101 step 11
is VR1_MINOR step 18
is VR2_MINOR step 18
is VSN_MIN_ALM step 18
is VSN_ONE_LINK step 18
4 Perform the correct procedure that supports Traffic Operator Position System
(TOPS) to clear the alarm. Complete the procedure and return to this point.
5 Go to step 22.
7 Go to step 22.
297-2651-543 Standard 05.01 March 1999

Ext Min
minor (continued)
8 The occurrence of this alarm depends on the configuration of your office. The
occurrence of the alarm also depends on the stimulus that your company chose
as the trigger for the alarm. Use the procedures outlined by your company to
find and fix the fault. Complete the procedure and return to this point.
9 Go to step 22.
10 Perform the correct procedure in this document. Complete the procedure and
Go to step 22.
11 Answer the incoming call on a 101-type test line at a transmission test center
(TTC). Take action according to the procedure on how to respond to 101-type
calls. Your company outlines the procedure. Complete the procedure and
12 Go to step 22.
13 Determine if the system generated a TRK153 log report.
If the system Do
generated a TRK153 log report step 14

did not generate a TRK153 log step 23
report
14 Respond to the alarm and log report as indicated in your company procedure to
handle toll calls that are not legal. Complete the procedure and return to this
point.
15 Go to step 22.
16 Mount the out-of-service volume on the DIRP subsystem.

Go to step 22.
17 At the CI level of the MAP display, execute the RCLR command.

Go to step 18.
GSP05 (CSP10)
Ext Min
minor (continued)
18 Determine if the system generated an EXT106 log report.
If the system Do
generated an EXT106 log report step 19

did not generate an EXT106 report step 20
19 Determine if the alarm is OFF.

EXT106 APR01 09:13:48 425 INFO VSN_MIN_ALM OFF
CNTRLNK_INTERFACE 1
Note: The word OFF on the right side of the alarm name indicates that the
alarm is off.
If the alarm Do
is OFF step 22
is not OFF step 20
20 Wait 30 min. Determine if the system generated an EXT106 log.
If the system Do

did not generate an EXT106 log step 22
21 Determine if the alarm is OFF.
If the alarm Do
is OFF step 22
is not OFF step 23
297-2651-543 Standard 05.01 March 1999

Ext Min
minor
minor
(continued)
(end)
22 Determine if the EXT Min minor alarm cleared.
If the alarm Do
cleared step 24
changed to a lower number (for step 2
example, changed from 2Min to
1Min)
GSP05 (CSP10)
Ext E911_ALI_MAJOR
major
Alarm display
. . . . . . . . 1Maj .
M
Indication
Under the EXT subsystem header at the MTC level of the MAP display,
1Maj can indicate an E911_ALI_MAJOR alarm. The major alarm for the
E911 automatic location identification (ALI) appears under the EXT header
for both SuperNode and NT40 applications.
Meaning
An E911_ALI_MAJOR alarm means that both multiprotocol controller links
to the ALI controller of an open interface failed.
Result
ALI database information is not available to line or automatic call
distribution public safety answering point (PSAP) operators the database
serves.
Common procedures
Action
procedure.
297-2651-543 Standard 05.01 March 1999

Ext E911_ALI_MAJOR
major (continued)
Summary of Clearing an Ext E911_ALI_MAJOR major alarm

Silence the
procedure.
EXT alarm
procedure.
Access EXT
level at MAP
List major alarms
Check MPC
and E911 logs
for link failures
Post the defective

MPC
Do all MPC N Perform

links appear maintenance
to work? on failed MPC
Y
Contact next level N Y End

Alarm cleared?
of support
GSP05 (CSP10)
Ext E911_ALI_MAJOR
major (continued)
Clearing an Ext E911_ALI_MAJOR major alarm
At the MAP display
1 You enter this procedure from a step in a procedure to clear a system-level
alarm that identifies an EXT major alarm.
2 If you must silence the alarm, type

>MAPCI:MTC:SIL
3 To access the EXT level of the MAP display, type

>EXT
0 0 1 0 14
4 To display all the EXT major alarms, type

>LIST MAJ
If response on MAP Do
is E911_ALI_MAJOR step 6
5 Go to the table of contents.
6 Obtain MPC908 and E911211 logs. To access LOGUTIL, type

>LOGUTIL
297-2651-543 Standard 05.01 March 1999

Ext E911_ALI_MAJOR
major (continued)
7 To open the buffer for the MPC log report, type

>OPEN MPC908
8 Browse through the buffer to display the MPC908 log report. Enter the
following command as many times as needed to see this report. Type
>BACK
The MPC908 log report generates when the tandem detects an MPC card in a
SysB state.
Example of the MPC908 log:
MPC908 FEB 13:05:24 3700 MPC LINK STATUS
MPC 3 LINK 3 STATUS CHANGE: ENBLIP –> SBSY
System Action Taken
9 An E911211 log report can generate without the E911210 to accompany the
report. The absence of the E911210 indicates the tandem tried to send records
to the ALI database twice. The attempts failed. Repeat steps 6, 7, and 8 to
open the E911 log buffer to display the E911211 report. For step 7 only, type
>OPEN E911
Example of the E911211 log report:

E911211 FEB03 13:05:24 0101 ALI RECORD FAILURE SEND
FAILURE
TWO ATTEMPTS FAILED
PSAPNUM 003 POSNUM 0012 MPC 1 MPCLINK 2
10 Exit LOGUTIL, type

>QUIT
11 Note the MPC number listed in the MPC908 log report.
12 To access the MTC MAP level, type

>MAPCI;MTC
GSP05 (CSP10)
Ext E911_ALI_MAJOR
major (continued)
(end)
13 To display MPC card status, type

>IOD;IOC 1;MPC mpc_number
where
mpc_number is the ID of the MPC card identified in step 11
Note: You do not need to know the number of the IOC that contains the card to
display the MPC link status. IOC port information for IOC1 appears when the
system shows link status for the MPC card. The MPC card is on the same IOC
shelf or another IOC shelf.
IOC CARD 0 1 2 3 4 5 6 7 8
User SYSTEM BOARD LINK0 LINK1 LINK2 LINK3
1 PORT 0123 0123 0123 0123 0123 0123 0123 0123 0123
STAT ... .––– .––– .––– .––– ... .... .... ....
TYPE CONS MPC MPC MPC MPC
Card 3 Unit 17
User SYSTEM BOARD LINK0 LINK1 LINK2
Status Ready COMACT UNEQ UNEQ ENBLD SBSY
WARNING: MPC 17 IS NOT ON THE DISPLAYED IOC
MPC 17 IS ON IOC 3
Refer to the following table to determine the next step. The next step depends
on if the card links are system busy.
If links Do
are not SysB step 14

are SysB step 15
15 Perform MPC card maintenance. Refer to this document. Verify that the alarm
cleared. If the alarm persists, contact the next level of support.
297-2651-543 Standard 05.01 March 1999

Ext E911_ALI_MINOR
minor
Alarm display
. . . . . . . . 1Min .
Indication
1Min can indicate an E911_ALI_MINOR alarm. The E911 automatic
location identification (ALI) minor alarm appears under the EXT heading
for both SuperNode and NT40 applications.
Meaning
An E911_ALI_MINOR alarm means one of the multiprotocol controller
(MPC) links to the ALI controller of an open interface failed.
Result
Only one of two redundant links in this two-link ALI interface can operate if
the E911_ALI_MINOR alarm activates.
Common procedures
Action
procedure.
GSP05 (CSP10)
Ext E911_ALI_MINOR
minor (continued)
Summary of How to clear an Ext E911_ALI_MINOR minor alarm
Silence EXT alarm This flowchart summarizes the

procedure.

procedure.
Access EXT
level at MAP
List minor alarms
Check MPC
and E911 logs
for link failures
Post the MPC

Contact next N Y End

Alarm clear?
level of support
297-2651-543 Standard 05.01 March 1999

Ext E911_ALI_MINOR
minor (continued)
How to clear an Ext E911_ALI_MINOR minor alarm
At the MAP display
1 Enter this procedure from a step in a procedure to clear a system-level alarm
that identified an EXT minor alarm.

>MAPCI;MTC;SIL

>EXT
0 0 0 1 14
4 To display all the EXT minor alarms, type

>LIST MIN
If response on MAP Do
is E911_ALI_MINOR step 6
5 Go to the procedures listed in the table of contents for references to other

alarms.
6 Obtain MPC908 and any E911211 log reports. To access LOGUTIL, type
>LOGUTIL

>OPEN MPC
GSP05 (CSP10)
Ext E911_ALI_MINOR
minor (continued)
8 To browse through the buffer to display the MPC908 log report, type
>BACK
SysB state.
MPC908 FEB03 13:05:24 3700 MPC LINK STATUS
System Action Taken
9 An E911211 log report can appear without an E911210. Absence of an

E911210 indicates the tandem tried to send records to the ALI database twice,
and both attempts failed. Repeat steps 6, 7, and 8 to open the E911 log buffer
to display the E911211 report. For step 7 only type
>OPEN E911
E911211 FEB03 13:05:24 0101 ALI RECORD FAILURE SEND
FAILURE
TWO ATTEMPTS FAILED
PSAPNUM 003 POSNUM 0012 MPC 1 MPCLINK 2

>QUIT
11 Note the MPC number listed in the MPC908 log report.

>MAPCI;MTC
297-2651-543 Standard 05.01 March 1999

Ext E911_ALI_MINOR
minor
minor
(continued)
(end)
13 To display card status of the MPC, type

where
mpc_number is the ID of the MPC card identified in step 5.
Note: The card is in an IOC number. You do not need to know the number of
the IOC that contains the card to display the MPC link status. IOC port
information for IOC1 appears when the system shows link status for the MPC
card. The MPC card is on the same IOC shelf or another IOC shelf.
IOC CARD 0 1 2 3 4 5 6 7 8
1 PORT 0123 0123 0123 0123 0123 0123 0123 0123 0123
STAT .... .––– .––– .––– .––– .... .... .... ....
Card 3 Unit 17
MPC 17 IS ON IOC 3
Refer to the following table for the next step. The next step depends on if the
card links are system busy.
If links Do

are SysB step 15
15 Perform MPC card maintenance. Refer to this document. Verify that the alarm
cleared. If the alarm persists, contact next level of support.
GSP05 (CSP10)
Ext CPPOOL
critical
Alarm display
. . . . . . . 1Crit
Indication
At the MTC level of the MAP display, CPPOOLMGR critical appears under
the computing module (CM) header of the alarm banner. The
CPPOOLMGR critical signal indicates that an audit finds a fault condition.
The audit finds a fault when the audit finds an error condition with the pools.
Meaning
The system raises the CPPOOL critical alarm because of the following
conditions:
• The system raises POOL302 when the number of free areas owned by
the server reduces to 10% of the server memory.
• The system raises POOL312 when the number of areas used by a pool
reaches 90% of the server’s limit of vast areas of that pool.
• The system raises POOL321 when a pool reaches 100% of the absolute
possible usage level.
Result
This alarm indicates that memory runs very low. Report the condition
immediately to next level of support, so that call processing does not
degrade.
Common procedures
Action
procedure.
297-2651-543 Standard 05.01 March 1999

Ext CPPOOL
Summary of Clearing an Ext CPPOOL critical alarm
Obtain all recent This flowchart summarizes the

POOL logs procedure.

level of support
End
GSP05 (CSP10)
Ext CPPOOL
Clearing an Ext CPPOOL critical alarm
At the MAP display
>MAPCI;MTC;EXT
2 To access pool information, type

>CPPOOLMGR
3 Review pool logs.
If the log Do
is POOL 302 step 4

is POOL 312 step 5
is POOL 321 step 10
4 To display current information about the server and office parameter, type
>DMEMINFO
DYNAMIC MEMORY SIZE PARM
PARM MEMORY IN KBYTES VAST AREAS
SIZE Total USED Total USED
15MB 15360K 2112K 13% 240 33K 13%
POOLS IN ALARM
POOL FTRQ2WPERMS is in alarm for a POOL_LIMIT alarm
Go to step 7.
297-2651-543 Standard 05.01 March 1999

Ext CPPOOL

>POOL poolname
where
poolname is the name of the pool
CURRENT POOL INFORMATION in BLOCKS
POOL NAME IN USE HWM ALLOC PERCENT PERCENT ALARM
BLOCKS BLOCKS BLOCKS Tot MEM Pool Max
FTRQ2WPERMS 0 69615 69615 7% 100%*

FTRQAGENTS 0 100 4681 1% 7%
FTRQ0WAREAS 0 0 8191 1% 11%
FTRQ2WAREAS 0 0 5461 1% 8%
FTRQ4WAREAS 0 0 4095 1% 5%
FTRQ8WAREAS 0 0 2730 1% 4%
FTRQ16WAREAS 0 0 1638 1% 2%
FTRQ32WAREAS 0 0 910 1% 1%
FTRQ0WPERMS 0 0 5461 1% 8%
NUMBER_OF_NCCBS_
SCRATCHEXT_AREAS 0 0 8191 1% 2%
FTRQ4WPERMS 0 0 3276 1% 4%
FTRQ8WPERMS 0 0 2340 1% 3%
FTRQ16WPERMS 0 0 1489 1% 2%
FTRQ32WPERMS 0 0 862 1% 1%
6 Check the preceding response for the percentage of memory allocated.

Compare the percentage of memory allocated to the total amount of memory
available. Compare the percentage of memory allocated to the maximum
amount that the pool can have.
7 You must increase the size of the parameter DYNAMIC_MEMORY_SIZE in

table OFCENG to clear the alarm.
Go the the next level of support. Determine the amount of store you must add
to the parameter DYNAMIC_MEMORY_SIZE. Return to this point.
8 The pool memory is close to the maximum amount of pool memory. If

necessary, you can reduce the size of the pool memory.
Go the the next level of support. Determine the amount of store you must add
to the parameter DYNAMIC_MEMORY_SIZE. Return to this point.
GSP05 (CSP10)
Ext CPPOOL
(end)
9 To make sure that the amount of store added to the parameter turned OFF the
alarm, type
>DMEMINFO
15MB 15360K 2112K 13% 240 33K 13%
POOLS IN ALARM
If the alarm Do
is OFF step 11
is ON step 10
297-2651-543 Standard 05.01 March 1999

Ext CPPOOL
major
Alarm display
. . . . . . . 1Maj
Indication
At the MTC level of the MAP display, CPPOOLMGR major appears under
the CM header of the alarm banner. The CPPOOLMGR major indicates that
an audit detects a fault condition when the audit detects an error condition
with the pools.
Meaning
The CPPOOL major alarm occurs as a result of the following conditions:
• POOL301 occurs when the number of free areas owned by the server
drops to 20% of server memory.
• POOL311 occurs when the pool uses 80% or more of the server limit of
areas of that pool.
Result
This alarm indicates a potential problem because server memory runs low.
If server memory is not available, call processing degrades.
Common procedures
Action
procedure.
GSP05 (CSP10)
Ext CPPOOL
major (continued)
Summary of Clearing an Ext CPPOOL major alarm


level of support
End
297-2651-543 Standard 05.01 March 1999

Ext CPPOOL
major (continued)
Clearing an Ext CPPOOL major alarm
At the MAP terminal
>MAPCI;MTC;EXT

>CPPOOLMGR
3 Review pool logs.
If log Do
is POOL 301 step 4

is POOL 311 step 5
4 To determine if the memory server needs more memory, type

>DMEMINFO
15MB 15360K 2112K 13% 240 33K 13%
POOLS IN ALARM
Go to step 7.
GSP05 (CSP10)
Ext CPPOOL
major (continued)

>POOL poolname
where
FTRQ2WPERMS 0 69615 69615 7% 100%*

FTRQAGENTS 0 100 4681 1% 7%
FTRQ0WAREAS 0 0 8191 1% 11%
FTRQ2WAREAS 0 0 5461 1% 8%
FTRQ4WAREAS 0 0 4095 1% 5%
FTRQ8WAREAS 0 0 2730 1% 4%
FTRQ16WAREAS 0 0 1638 1% 2%
FTRQ32WAREAS 0 0 910 1% 1%
FTRQ0WPERMS 0 0 5461 1% 8%
NUMBER_OF_NCCBS_
FTRQ4WPERMS 0 0 3276 1% 4%
FTRQ8WPERMS 0 0 2340 1% 3%
FTRQ16WPERMS 0 0 1489 1% 2%
FTRQ32WPERMS 0 0 862 1% 1%
6 Check the preceding response for the allocated percentage of memory.

Compare the memory to the total amount of available memory and the
maximum amount of memory available to the pool.
If pool Do
is close to the total memory step 7

maximum
is close to the pool maximum step 8
297-2651-543 Standard 05.01 March 1999

Ext CPPOOL
majormajor
(continued)
(end)
7 The parameter DYNAMIC_MEMORY_SIZE in table OFCENG must increase in

size to clear the alarm.
Go the the next level of support to determine the amount of store to add to the
parameter DYNAMIC_MEMORY_SIZE. Return to this point.
8 The pool memory is near the maximum. Reduction of pool memory is a

possible fix.
Go the the next level of support to determine the amount of store to add to the
parameter DYNAMIC_MEMORY_SIZE. Return to this point.
9 To check that the amount of store added to the parameter turns the alarm OFF,
type
>DMEMINFO
15MB 15360K 2112K 13% 240 33K 13%
POOLS IN ALARM
If the alarm Do
is OFF step 11
is ON step 10
GSP05 (CSP10)
Ext CPPOOL
minor
Alarm display
. . . . . . . 1Min
Indication
At the MTC level of the MAP display, CPPOOLMGR minor appears under
the CM header of the alarm banner. The CPPOOLMGR indicates that an
audit detects a fault condition when the audit detects an error condition with
the pools.
Meaning
The CPPOOL minor alarm occurs as a result of these conditions:
• POOL300 report generates when the number of server-owned free areas
drops to 30% of server memory
• POOL310 report generates when the pool uses 70% or more of the
server limit of free areas of that pool
• POOL320 report generates when a pool reaches 90% of the absolute
possible use level
Result
This alarm indicates a potential problem because server memory begins to
run low. If server memory is not available, call processing degrades.
Common procedures
Action
procedure.
297-2651-543 Standard 05.01 March 1999

Ext CPPOOL
minor (continued)
Summary of Clearing an Ext CPPOOL minor alarm


level of support
End
GSP05 (CSP10)
Ext CPPOOL
minor (continued)
Clearing an Ext CPPOOL minor alarm
At the MAP terminal
>MAPCI;MTC;EXT

>CPPOOLMGR
3 Review pool logs.
If log Do
is POOL300 step 4
is POOL310 step 5
is POOL320 step 9
4 To determine if the memory server needs more memory, type

>DMEMINFO
15MB 15360K 2112K 13% 240 33K 13%
POOLS IN ALARM
297-2651-543 Standard 05.01 March 1999

Ext CPPOOL
minor (continued)
5 To verify the pool size, type

>POOL poolname
where
FTRQ2WPERMS 0 69615 69615 7% 100%*

FTRQAGENTS 0 100 4681 1% 7%
FTRQ0WAREAS 0 0 8191 1% 11%
FTRQ2WAREAS 0 0 5461 1% 8%
FTRQ4WAREAS 0 0 4095 1% 5%
FTRQ8WAREAS 0 0 2730 1% 4%
FTRQ16WAREAS 0 0 1638 1% 2%
FTRQ32WAREAS 0 0 910 1% 1%
FTRQ0WPERMS 0 0 5461 1% 8%
NUMBER_OF_NCCBS_
FTRQ4WPERMS 0 0 3276 1% 4%
FTRQ8WPERMS 0 0 2340 1% 3%
FTRQ16WPERMS 0 0 1489 1% 2%
FTRQ32WPERMS 0 0 862 1% 1%
6 Check the response for the percentage of allocated memory compared to the
total amount of available memory. Compare the percentage of allocated
memory to the maximum amount of memory available to the pool.
If pool Do
is close to the total amount of step 7

available memory
is close to the maximum amount of step 9
available memory
GSP05 (CSP10)
Ext CPPOOL
minor (continued)
(end)
7 You can increase the size of the server parameter DYNAMIC_MEMORY_SIZE,

in table OFCENG.
Go to step 9.
8 To check if store has enough memory to turn off the alarm, type
>DMEMINFO
15MB 15360K 2112K 13% 240 33K 13%
POOLS IN ALARM
If the alarm Do
is OFF step 10
is ON step 9
297-2651-543 Standard 05.01 March 1999

Ext FSP
major
Alarm display
. . . . . . . . 1FSP .
M
Indication
At the MTC level of the MAP display, FSP (preceded by a number) appears
under the Ext header of the alarm banner. The FSP indicates an Ext frame
supervisory panel (FSP) alarm, or a modular supervisory panel (MSP)
alarm.
Meaning
The system generates an FSP alarm when one or more frames or cabinets in
the office has a power fault. The system also generates an FSP alarm for a
cooling unit fault.
The number that precedes FSP is the number of equipment aisles in which
the subsystem detects an FSP alarm.
Result
The impact on subscriber service depends on the type of the fault and the
type of frame that contains the fault.
Common procedures
Action
GSP05 (CSP10)
Ext FSP
major (continued)
Summary of Clearing an Ext FSP major alarm
List aisles with This flowchart summarizes the

frame faults procedure.

appropriate
procedure
End
297-2651-543 Standard 05.01 March 1999

Ext FSP
major (continued)
Clearing an Ext FSP major alarm
At the MAP terminal

>MAPCI;MTC;EXT
0 1 0 0 12
2 List the aisles in the office that have one or more frames with faults on power or
cooling units. To list the aisles, type
>LIST FSP
FSPAISn
Note: In the example, n represents the aisle that contains one or more frames
with a power or cooling unit fault.
3 Record the identity of the first aisle on the list.
4 In the aisle, locate the frame that has the fault on the power or cooling unit. A lit
FRAME FAIL lamp identifies the frame.
Note: If a frame has an FSP alarm, the FRAME FAIL lamp at the end of the
aisle of the frame illuminates.
5 Perform the FSP alarm clearing procedure in this document. Make sure the
procedure is correct for the type of frame. Complete the procedure and return
to this point.
6 Determine if the FSP major alarm cleared.
If the alarm Do
cleared step 8
changed to a smaller number step 2
(for example, changed from 2FSP
to 1FSP)
GSP05 (CSP10)
Ext FSP
major (continued)
(end)
297-2651-543 Standard 05.01 March 1999

Ext FSP
GPP cabinet with an MSP shelf major
Alarm display
. . . . . . . . 1FSP .
M
Indication
EXT header of the alarm banner. The FSP indicates a major alarm for the
external frame supervisory panel (FSP).
Meaning
A power fault or cooling unit fault exists on one or more global peripheral
platform (GPP) cabinets in the office.
The number under the EXT header of the alarm banner indicates the number
of affected cabinets.
Result
The impact on subscriber service depends on the type of fault and the type of
frame that contains the fault.
Common procedures
Action
procedure.
GSP05 (CSP10)
Ext FSP
GPP cabinet with an MSP shelf major (continued)
Summary of Clearing an Ext FSP major alarm for a GPP cabinet with an MSP shelf
Is FAN Y Repair cooling This flowchart summarizes the

FAIL unit procedure.
lamp lit?
N Use the instructions that follow
procedure.
Y Is the FRAME N
FAIL LED lit?
Is the Replace power

Y
CONVERTER converter
FAIL LED lit?
N
Is the
CONVERTER N
FAIL LED lit?
Y
Replace alarm
module
Y Is the FRAME N
FAIL LED lit?
Replace fuse Did the Ext N

Has a fuse Y Is the FRAME N
FSP alarm 1
blown? FAIL LED lit?
clear?
N Y Y
Clear other Ext Contact next End

FSP alarms 1 level of support
297-2651-543 Standard 05.01 March 1999

Ext FSP
Clearing an Ext FSP major alarm for a GPP cabinet with an MSP shelf
At the front of the GPP cabinet
1 Determine if the FAN FAIL lamp on the MSP is lit.
If the FAN FAIL lamp Do
is lit step 35
is not lit step 2
2 Check each converter in the GPP cabinet. Determine if any CONVERTER

FAIL LEDs are lit.
If a CONVERTER FAIL LED Do
is not lit step 3

is lit step 7
3 Determine if any fuses on the MSP have blown.
If a fuse Do
has blown step 4

has not blown step 40
4 Obtain a replacement fuse with the same voltage and amperage as the blown
fuse.
5 Remove the blown fuse.
GSP05 (CSP10)
Ext FSP
6
DANGER
Risk of fire
To protect against fire, replace the blown fuse with a
fuse of the same type, rating (color code), and
manufacturer.
DANGER
Risk of fire
manufacturer.
Insert the replacement fuse.
If the fuse Do
has not blown again step 34

has blown again step 40
7 Determine if the POWER switch on the power converter is ON or OFF.
If the POWER switch Do
is OFF step 8
is ON step 9
8 Set the POWER switch on the converter to ON.
If the CONVERTER FAIL LED Do
is lit step 9
is not lit step 34
297-2651-543 Standard 05.01 March 1999

Ext FSP
9 Record the numbers of the shelf and unit (0 or 1) that contain the lit
CONVERTER FAIL LED.
Note: The shelf numbers are on the right side of the cabinet.
10 Identify the circuit breaker on the MSP for the shelf and unit that contain the lit
CONVERTER FAIL LED.
Note: Shelves have two circuit breakers each (one for each unit).
Note: A label for each circuit breaker contains numbers for breaker
identification, equipment shelf, and card position for the power converter. For
example, CB02-47-01 is circuit breaker 02 for shelf 47 and card position
number 01.
11 Determine if the circuit breaker is ON or OFF.
If the circuit breaker Do
is ON step 12
is OFF step 13
12 Turn OFF the circuit breaker.
13 Push the power switch on the converter up. Hold the power switch in the
RESET position while you set the circuit breaker to ON.
14 Release the power switch on the converter to the ON position.
turns OFF, and the CONVERTER step 15

FAIL LED is lit
remains ON, and the CONVERTER step 26
FAIL LED is lit
FAIL LED is not lit
15 Record the numbers of the cabinet and shelf with the lit CONVERTER FAIL
LED.
GSP05 (CSP10)
Ext FSP
16 Consult office records or operating company personnel. Determine if power to

the GPP cabinet connects through a power distribution center (PDC) or a
cabinetized PDC (CPDC).
If power Do
connects through PDC step 17

connects through CPDC step 21
At the PDC
17 Locate the fuse for the affected GPP shelf and unit (0 or 1).
18 To remove the fuse, pull the fuse cartridge out.
If the fuse Do
is blown step 19
is not blown step 24
19
DANGER
Risk of fire
manufacturer.
DANGER
Risk of fire
manufacturer.
Remove the blown fuse from the fuse cartridge. Insert a replacement fuse.
20 Insert the fuse cartridge.

Go to step 24.
297-2651-543 Standard 05.01 March 1999

Ext FSP
At the CPDC
21 Locate the circuit breaker that powers the GPP shelf and unit (0 or 1).
is OFF step 23
is ON step 24
23 Set the circuit breaker to ON.

remains ON and the CONVERTER step 26

FAIL LED is lit
turns OFF again and the step 29
CONVERTER FAIL LED is lit
FAIL LED is not lit

26 Set the circuit breaker to OFF.
27 To replace the power converter card, perform the correct procedure in Card
GSP05 (CSP10)
Ext FSP
28 Determine the state of the power converter you replaced. Determine the state
of the associated circuit breaker.
is OFF, and the CONVERTER FAIL step 29

LED is lit
FAIL LED is lit
FAIL LED is not lit
29 Determine if the backplane of the shelf has any short-circuited or bent pins.
Note: The backplane is at the rear of the GPP cabinet.
If short-circuited or bent pins Do
are not present step 30

are present step 40
31 To replace the alarm module (NTRX41AA), perform the correct procedure in

Card Replacement Procedures. Complete the procedure and return to this
point.
297-2651-543 Standard 05.01 March 1999

Ext FSP
is not lit step 34

is lit step 40
34 Determine if the FRAME FAIL lamp on the MSP is lit.
If the FRAME FAIL lamp Do
is lit, and blown fuses exist on the step 4

MSP
is lit, and blown fuses do not exist step 40
on the MSP
is not lit step 37
35 To repair the damaged cooling unit, perform the correct procedure in Trouble
Locating and Clearing Procedures. Complete the procedure and return to this
point.
is lit step 2
is not lit step 37
At the MAP terminal

>MAPCI;MTC;EXT
GSP05 (CSP10)
Ext FSP
38 Determine if an FSP alarm is present.
If an FSP alarm Do
is present and you did not perform step 39

the correct procedure to clear
alarms in all cabinets or frames with
an FSP alarm
is present and you performed the step 40
correct procedure to clear alarms in
all cabinets or frames with an FSP
alarm
39 Perform the correct procedure to clear alarms for the other types of frame or
cabinet that have the FSP alarm. Complete the procedure and return to this
point.
At the back of the GPP cabinet
40
DANGER
Risk of electrocution
Some terminals inside the MSP have an electrical
potential of –48 V dc to –60 V dc. Do not touch any
terminals inside the MSP.
DANGER OF ELECTRIC SHOCK

Determine if the supply wiring for the alarm battery in the MSP is
short-circuited.
Note: The next level of support can request this information.
297-2651-543 Standard 05.01 March 1999

Ext FSP
GPP GPP
cabinet with with
cabinet an MSP shelfshelf
an MSP majormajor
(continued)
(end)
GSP05 (CSP10)
Ext FSP
APC cabinet major
Alarm display
. . . . . . . . 1FSP .
M
Indication
under the EXT header of the alarm banner. The FSP indicates a major alarm
for an external frame supervisory panel (FSP).
Meaning
A power fault or a cooling unit fault is present on one or more office
cabinets.
of affected cabinets.
Result
cabinet that contains the fault.
Common procedures
Action
297-2651-543 Standard 05.01 March 1999

Ext FSP
APC cabinet major (continued)
Summary of Clearing an Ext FSP APC cabinet major alarm

BLOWER FAIL procedure.
LED on FSP is
lit Use the instructions that follow
procedure
Is the Y Repair cooling
BLOWER unit
FAIL LED lit?
N
Is a Y Replace
CONVERTER converter
OFF LED lit?
N
Y Replace fuse
Is a fuse
blown?
Contact next End

level of support
GSP05 (CSP10)
Ext FSP
Clearing an Ext FSP APC cabinet major alarm
At the APC
1 Determine if the BLOWER FAIL LED on the FSP is lit.
If the BLOWER FAIL LED Do
is lit step 38
is not lit step 2
2 Check each converter in the cabinet. Determine if any CONVERTER OFF

LEDs are lit.
If any CONVERTER OFF LEDs Do
are lit step 7

are not lit step 3
3 Determine if fuses 01 to 04 on the FSP have blown.
If a fuse Do
has blown step 4

297-2651-543 Standard 05.01 March 1999

Ext FSP
4
DANGER
Risk of fire
To protect against risk of fire, replace the blown fuse
with a fuse of the same type, rating (color code), and
manufacturer.
DANGER
Risk of fire
manufacturer.
Obtain a replacement fuse with the same voltage and amperage as the blown
fuse.
6 Insert the replacement fuse.
If the fuse Do

If the CONVERTER OFF LED Do
is lit step 8
is not lit step 37
8 Record the number of the shelf that contains the converter with the lit
CONVERTER OFF LED.
GSP05 (CSP10)
Ext FSP
9 Determine if the cabinet is an APC SuperNode or an APC SuperNode SE.
If the cabinet Do
is an APC SuperNode step 11

is an APC SuperNode SE step 10
297-2651-543 Standard 05.01 March 1999

Ext FSP
10 Determine from the following table which fuse associates with the shelf with the
lit CONVERTER OFF LED.
Shelf Fuse
0 (left side) 01
0 (right side) 05
1 (left side) 02
1 (right side) 06
2 (left side) 03
2 (right side) 07
3 (left side) 04
3 (right side) 08
Note: Shelf numbering is from top to bottom. Shelf 0 is below the FSP. Shelf
3 is the bottom shelf. The different sides of each shelf (left and right) relate to
different FSP fuses, as listed in the table.
Go to step 12.
11 Refer to the following table. Determine which fuse associates with the shelf
with the lit CONVERTER OFF LED.
Shelf Fuse
MS0 (left side) 01

MS0 (right side) 02
MS1 (left side) 03
MS1 (right side) 04
CM0 (left side) 05
CM0 (right side) 06
CM/SLM (left side) 07
CM/SLM (right side) 08
GSP05 (CSP10)
Ext FSP
12 Determine if the associated fuse is blown.
If the fuse Do
is blown step 13
13
DANGER
Risk of fire
manufacturer.
DANGER
Risk of fire
manufacturer.
fuse.
If the fuse Do
has blown, and the CONVERTER step 16

OFF LED is lit
has not blown, and the step 39
CONVERTER OFF LED is not lit
CONVERTER OFF LED is lit
297-2651-543 Standard 05.01 March 1999

Ext FSP
16 Determine if the APC connects to a power distribution center (PDC) or

cabinetized PDC (CPDC).
If the APC Do
connects to a PDC step 17

connects to a CPDC step 22
At the PDC
17 Locate the fuse that powers the APC shelf.
If the fuse Do
has blown step 18

18 Remove the fuse holder that contains the blown fuse.
19
DANGER
Risk of fire
manufacturer.
DANGER
Risk of fire
manufacturer.
fuse.
20 Replace the blown fuse.
21 Install the fuse holder into the PDC shelf.
GSP05 (CSP10)
Ext FSP
Go to step 24.
At the CPDC
22 Locate the circuit breaker that powers the APC shelf.
is OFF step 25
is ON step 29
At the APC
24
DANGER
Risk of fire
manufacturer.
DANGER
Risk of fire
manufacturer.
fuse.
is lit step 29
is not lit step 37
297-2651-543 Standard 05.01 March 1999

Ext FSP
27 To replace the converter card, perform the correct procedure in Card

28 Determine if the CONVERTER OFF LED for the replaced converter card is lit.
is lit step 41
is not lit step 37
29 Locate the blown fuse.
If the blown fuse Do
is one of 09, 11, 14, 15, or 16 step 41

is one of 10, 12, or 13 step 30
30 Determine from the following table which alarm and control card associates with
the blown fuse.
Fuse number Alarm and control card
12 slot CD1 (NT6X36KA)

GSP05 (CSP10)
Ext FSP
32
DANGER
Risk of fire
manufacturer.
DANGER
Risk of fire
manufacturer.
fuse.
33 To replace the alarm and control card, perform the correct procedure in Card
If the fuse Do

35 Determine if the FRAME FAIL lamp on the FSP is lit.
If the FRAME FAIL LED Do
is lit, and step 3 is not complete step 3

is lit, and step 3 is complete step 41
is not lit step 40
36 To repair the cooling unit that has faults, perform the correct procedure in
Trouble Locating and Clearing Procedures. Complete the procedure and return
to this point.
297-2651-543 Standard 05.01 March 1999

Ext FSP
APC APC
cabinet majormajor
cabinet (continued)
(end)
is lit step 2
is not lit step 40
At the MAP terminal

>MAPCI;MTC;EXT
If an FSP alarm Do
is present, and you did not access step 40

all the cabinets with an FSP alarm
is present, and you accessed all the step 41
cabinets with an FSP alarm
40 Perform the correct procedure in this document for the type of frame that has
the FSP alarm. Complete the procedure and return to this point.
GSP05 (CSP10)
Ext FSP
CCC frame major
Alarm display
. . . . . . . . 1FSP .
M
Indication
Meaning
A power fault or a cooling unit fault is present in one or more office frames.
of affected frames.
Result
The impact on subscriber service depends on the type of fault. Subscriber
service impact also depends on the type of cabinet of the fault.
Common procedures
Action
procedure.
297-2651-543 Standard 05.01 March 1999

Ext FSP
CCC frame major (continued)
Summary of Clearing an Ext FSP CCC frame major alarm

FAN FAIL lamp procedure.
is lit.
Is the FAN Repair cooling procedure
Y
FAIL lamp unit
lit?
N
Is Replace
Y
CONVERTER converter
FAIL LED lit?
N
Y Replace fuse
Is a fuse
blown?
Contact next End

level of support
GSP05 (CSP10)
Ext FSP
Clearing an Ext FSP CCC frame major alarm
At the CCC frame

1 Determine if the FAN FAIL lamp on the FSP is lit.
is lit step 39
is not lit step 2
2 Determine if any CONVERTER FAIL LEDs are lit. Each converter in the frame
contains CONVERTER FAIL LEDs.
If the CONVERTER FAIL LEDs Do
are lit step 7

are not lit step 3
3 Note any blown alarm battery supply (ABS) fuses (05 to 08).
Note: The fuses are on the FSP.
If a fuse Do
has blown step 44

fuse.
297-2651-543 Standard 05.01 March 1999

Ext FSP
6
DANGER
Risk of fire
manufacturer.
DANGER
Risk of fire
manufacturer.
If a fuse Do
has blown step 44

7 Determine if the POWER switch on the converter is ON or OFF.
is ON step 9
is OFF step 8
8 Turn the POWER switch on the converter ON.
is lit step 9
is not lit step 38
GSP05 (CSP10)
Ext FSP
CONVERTER FAIL LED.
10 Examine the following table. Determine the number of the fuse for the shelf
with the lit CONVERTER FAIL LED.
Shelf Fuse
65 51
51 32
32 18
18 04
Note: The fuses are on the FSP.
11 Determine if the fuse for the shelf blows.
If the fuse Do
has blown step 12

fuse.
297-2651-543 Standard 05.01 March 1999

Ext FSP
13
WARNING
Static electricity damage
Wear a wrist strap that connects to the wrist-strap
grounding point of a frame supervisory panel (FSP) to
handle ENAB and DACT switches. The wrist strap
protects against static electricity damage.
CAUTION FOR ESDS

grounding point of a frame supervisory panel (FSP)
to handle ENAB and DACT switches. The wrist
strap protects against static electricity damage.
Set the ENAB switch on the NT1X48 card in a vertical position.

Note: The NT1X48 card is in the CPU.
14 Set the DACT switch on the NT1X48 card toward the right.
16
DANGER
Risk of fire
manufacturer.
DANGER
Risk of fire
manufacturer.
GSP05 (CSP10)
Ext FSP
17 Press and release the RESET button on the converter.
If the fuse Do

FAIL LED is lit
CONVERTER FAIL LED is not lit
18
WARNING
grounding point on the frame supervisory panel (FSP)
to handle ENAB and DACT switches. The wrist strap
protects against static electricity damage.
CAUTION FOR ESDS

grounding point on the frame supervisory panel
(FSP) to handle ENAB and DACT switches. The
wrist strap protects against static electricity damage.
Set the ENAB switch on the NT1X48 card toward the top.
297-2651-543 Standard 05.01 March 1999

Ext FSP
If the CONVERTER FAIL LEDs Do
are lit step 21

are not lit step 38
21 Record the number of the shelf and frame that contain the converter with the lit
CONVERTER FAIL LED.
At the PDC frame

22 Determine if the fuse that powers the shelf in the CCC frame blows.
If the fuse Do
has blown step 23

24 Replace the cartridge fuse inside the fuse holder.
25
DANGER
Risk of fire
manufacturer.
DANGER
Risk of fire
manufacturer.
Replace the blown fuse.
GSP05 (CSP10)
Ext FSP
26 Install the fuse holder back on the PDC frame.
At the CCC frame

fuse.
29
DANGER
Risk of fire
manufacturer.
DANGER
Risk of fire
manufacturer.
is lit step 31
is not lit step 38
31 To replace the converter, perform the correct procedure in Card Replacement

Procedures. When the procedure is complete, return to this point.
297-2651-543 Standard 05.01 March 1999

Ext FSP
32 Determine if the CONVERTER FAIL LED for the replaced converter is lit.
is lit step 33
is not lit step 38
33 Determine if short-circuited or bent pins are present on the backplane of the

shelf.

r
are present step 46
CONVERTER FAIL LED.
35 Examine the following table. Determine which alarm and control card
corresponds to the shelf with the converter and the lit CONVERTER FAIL LED.
Shelf number Alarm and control card
18 or 51 slot 1 (NT0X36AB)
32 or 65 slot 2 (NT0X36AB)
36 Record the CMC and CPU numbers on the frame.
Replacement Procedures. When the procedure is complete, return to this
point.
GSP05 (CSP10)
Ext FSP
is lit, and more blown fuses are step 3

present
is lit, and no more blown fuses are step 46
present
is not lit step 41
Trouble Locating and Clearing Procedures. When the procedure is complete,
is lit step 2
is not lit step 41
At the MAP terminal

>MAPCI;MTC;EXT
If an FSP alarm Do

all the frames with an FSP alarm
frames with an FSP alarm
43 Perform the procedure in this document that is correct for the type of frame that
has the FSP alarm. Complete the procedure and return to this point.
297-2651-543 Standard 05.01 March 1999

Ext FSP
CCC CCC
frameframe
majormajor
(continued)
(end)
44
DANGER
Some terminals inside the FSP have an electrical
potential of –48V dc to –60V dc. Do not touch any
terminals inside the FSP.

Open the FSP panel from the left-hand side.
45 Determine if the supply wiring for the alarm battery of the MSP is
short-circuited. The next level of support can request this information.
GSP05 (CSP10)
Ext FSP
CDSN cabinet with an MSP shelf major
Alarm display
. . . . . . . . 1FSP .
M
Indication
Meaning
A power fault or a cooling unit fault is present in one or more office
cabinets. The number under the EXT header of the alarm banner indicates
the number of cabinets affected.
Result
Common procedures
Action
procedure.
297-2651-543 Standard 05.01 March 1999

Ext FSP
CDSN cabinet with an MSP shelf major (continued)
Summary of Clearing an Ext FSP CDSN cabinet with an MSP shelf major alarm

Determine if the procedure.
FAN FAIL lamp
on MSP is lit Use the instructions that follow
procedure
FAN FAIL unit
lamp lit?
N
Is a Y Replace
CONVERTER converter
FAIL LED lit?
N
Is a fuse Y Replace fuse

blown?
Contact next End

level of support
GSP05 (CSP10)
Ext FSP
Clearing an Ext FSP CDSN cabinet with an MSP shelf major alarm
At the CDSN
1 Determine if the FAN FAIL lamp on the MSP is lit.
is lit step 30
is not lit step 2
2 Check each converter in the cabinet. Determine if any CONVERTER FAIL

LEDs are lit.
If CONVERTER FAIL LEDs Do
are lit step 7

are not lit step 3
3 Determine if any fuses on the MSP are blown.
If a fuse Do
has blown step 4

fuse.
297-2651-543 Standard 05.01 March 1999

Ext FSP
6
DANGER
Risk of fire
manufacturer.
DANGER
Risk of fire
manufacturer.
If the fuse Do
has blown step 35

is ON step 9
is OFF step 8
is lit step 9
is not lit step 29
GSP05 (CSP10)
Ext FSP
9 Record the number of the shelf that contains the lit CONVERTER FAIL LED.
10 Identify the circuit breaker on the MSP that associates with the shelf that
contains the lit CONVERTER FAIL LED.
Note: The labels for the circuit breakers contain numbers for the breaker
identification, the equipment shelf, and the circuit pack position. For example,
CB02-47-01 is circuit breaker 02 for shelf 47 and circuit pack position
number 01.
is ON step 12
is OFF step 13
13 Press and hold the RESET button on the converter while you set the circuit
breaker to ON.
14 Release the RESET button.

FAIL LED stays lit
FAIL LED is not lit
FAIL LED is lit
LED.
At the CPDC
16 Locate the circuit breaker that powers the CDSN shelf.
297-2651-543 Standard 05.01 March 1999

Ext FSP
is OFF step 18
is ON step 21

At the CDSN
breaker to ON.

FAIL LED stays lit
FAIL LED is not lit
FAIL LED is lit

23 Determine the state of the converter that you replaced. Determine the state of
the associated circuit breaker.

FAIL LED stays lit
FAIL LED is not lit
FAIL LED is lit
GSP05 (CSP10)
Ext FSP
Note: The backplane is at the rear of the cabinet.
If the backplane of the shelf Do
has short-circuited or bent pins step 35

does not have short-circuited or step 25
bent pins

point.
breaker to ON.
is lit step 35
is not lit step 29

present
present
is not lit step 32
point.
297-2651-543 Standard 05.01 March 1999

Ext FSP
is lit step 2
is not lit step 32
At the MAP terminal

>MAPCI;MTC;EXT
If an FSP alarm Do

GSP05 (CSP10)
Ext FSP
(end)
At the back of the CDSN
35
DANGER

Determine if the alarm battery supply wiring of the MSP is short-circuited. The
next level of support can request this information.
297-2651-543 Standard 05.01 March 1999

Ext FSP
CIOE cabinet with an MSP shelf major
Alarm display
. . . . . . . . 1FSP .
M
Indication
Meaning
A power fault or a cooling unit fault exists in one or more office cabinets.
of cabinets affected.
Result
The result on subscriber service depends on the type of fault and the type of
Common procedures
Action
procedure.
GSP05 (CSP10)
Ext FSP
CIOE cabinet with an MSP shelf major (continued)
Summary of Clearing an Ext FSP CIOE cabinet with an MSP shelf major alarm
Determine if any This flowchart summarizes the

CONVERTER procedure.
FAIL LEDs are lit
procedure
Are any Y Replace
CONVERTER converter
FAIL LEDs lit?
N
Y Replace fuse
Is a fuse
blown?
Contact next End

level of support
297-2651-543 Standard 05.01 March 1999

Ext FSP
Clearing an Ext FSP CIOE cabinet with an MSP shelf major alarm
At the CIOE
LEDs are lit.
are lit step 6

are not lit step 2
2 Determine if any blown fuses exist on the MSP.
If a fuse Do
has blown step 3

fuse.
GSP05 (CSP10)
Ext FSP
5
DANGER
Risk of fire
manufacturer.
DANGER
Risk of fire
manufacturer.
If the fuse Do
has blown step 29

is ON step 8
is OFF step 7
is lit step 8
is not lit step 25
297-2651-543 Standard 05.01 March 1999

Ext FSP
8 Record the number of the shelf with the lit CONVERTER FAIL LED.
9 Determine if any blown fuses are present on the MSP.
If a fuse Do
has blown step 10

fuse.
12
DANGER
Risk of fire
manufacturer.
DANGER
Risk of fire
manufacturer.
GSP05 (CSP10)
Ext FSP
If the fuse Do
has blown again, and the step 14

CONVERTER FAIL LED remains lit
does not protrude, and the step 25
14 Record the numbers of the cabinet and shelf that contain the lit CONVERTER
FAIL LED.
At the CPDC
15 Locate the circuit breaker that powers the CIOE shelf.
is OFF step 17
is ON step 19

At the CIOE
breaker to ON.

297-2651-543 Standard 05.01 March 1999

Ext FSP
21 Determine if the CONVERTER FAIL LED for the converter card that you
replaced is lit.
is lit step 22
is not lit step 25
are present step 29


point.
is lit step 29
is not lit step 25
25 Determine if the FRAME FAIL LED on the MSP is lit.

present
is lit, and more blown fuses are not step 29
present
is not lit step 26
GSP05 (CSP10)
Ext FSP
(end)
At the MAP terminal
>MAPCI;MTC;EXT
If an FSP alarm Do

At the back of the CIOE
29
DANGER

Determine if the supply wiring for the alarm battery in the MSP is
short-circuited. The next level of support can ask for this information.
297-2651-543 Standard 05.01 March 1999

Ext FSP
CIPE cabinet with an MSP shelf major
Alarm display
. . . . . . . . 1FSP .
M
Indication
Meaning
A power fault or a cooling unit fault exists in one or more office cabinets.
Result
Common procedures
Action
procedure.
GSP05 (CSP10)
Ext FSP
CIPE cabinet with an MSP shelf major (continued)
Summary of Clearing an Ext FSP CIPE cabinet with an MSP shelf major alarm
Determine if the This flowchart summarizes the

FAN FAIL LED procedure.
on MSP is lit
Y procedure
Is the FAN Repair cooling
FAIL LED lit? unit
N
Is a Y Replace
CONVERTER converter
FAIL LED lit?
N
Y Replace fuse
Is a fuse blown?
Contact next End

level of support
297-2651-543 Standard 05.01 March 1999

Ext FSP
Clearing an Ext FSP CIPE cabinet with an MSP shelf major alarm
At the CIPE
1 Determine if the FAN FAIL LED on the MSP is lit.
If the FAN FAIL LED Do
is lit step 30
is not lit step 2

LEDs are lit.
are lit step 7

are not lit step 3
3 Determine if any blown fuses are present on the MSP.
If a fuse Do
has blown step 4

fuse.
GSP05 (CSP10)
Ext FSP
6
DANGER
Risk of fire
manufacturer.
DANGER
Risk of fire
manufacturer.
If the fuse Do

is ON step 9
is OFF step 8
is lit step 9
is not lit step 29
297-2651-543 Standard 05.01 March 1999

Ext FSP
9 Record the number of the shelf with the lit CONVERTER FAIL LED. The shelf
numbers are on the right side of the cabinet.
10 Identify the circuit breaker on the MSP that associates with the shelf that
contains the lit CONVERTER FAIL LED.
Note: Labels for the circuit breakers contain numbers for the breaker
identification, the equipment shelf, and the circuit pack position. For example,
CB02-47-01 is CB 02 for shelf 47 and number 01 for the circuit pack position.
is ON step 12
is OFF step 13
breaker to ON.

FAIL LED stays lit
FAIL LED is not lit
FAIL LED is lit
LED.
At the CPDC
16 Locate the circuit breaker that powers the cabinetized international peripheral
equipment (CIPE) shelf.
GSP05 (CSP10)
Ext FSP
is OFF step 18
is ON step 21

At the CIPE
breaker to ON.
turns OFF again, and the step 24

FAIL LED is not lit
FAIL LED is lit

23 Determine the state of the converter card you replaced, and the associated
fuse.
If the fuse Do
has blown again, and the step 24

297-2651-543 Standard 05.01 March 1999

Ext FSP
24 Determine if the backplane of the shelf has short-circuited or bent pins. The
backplane is at the rear of the cabinet.
are present step 36


point.
breaker to ON.
is lit step 35
is not lit step 29
is lit and more blown fuses are step 3

present
is lit and no more blown fuses are step 35
present
is not lit step 32

Routine Procedures. Complete the procedure and return to this point.
GSP05 (CSP10)
Ext FSP
is lit step 2
is not lit step 32
At the MAP terminal

>MAPCI;MTC;EXT
If an FSP alarm Do

297-2651-543 Standard 05.01 March 1999

Ext FSP
CIPECIPE
cabinet with with
an MSP majormajor
(continued)
(end)
At the back of the CIPE
35
DANGER

Determine if the supply wiring of the alarm battery in the MSP is short-circuited.
The next level of support can ask for this information.
GSP05 (CSP10)
Ext FSP
CISM, CMTA, and CTME cabinet with an MSP shelf major
Alarm display
. . . . . . . . 1FSP .
M
Indication
EXT header of the alarm banner.
The FSP indicates a major alarm for the external frame supervisory panel
(FSP).
This procedure applies to:

• integrated services module (CISM) cabinets
• metallic test access (CMTA) cabinets
• trunk module equipment (CTME) cabinets
• services module equipment (ISME) frames
Meaning
One or more cabinets in the office has a power fault or a cooling unit fault.
Result
Common procedures
Action
procedure.
297-2651-543 Standard 05.01 March 1999

Ext FSP
CISM, CMTA, and CTME cabinet with an MSP shelf major (continued)
Summary of Clearing an Ext FSP CISM, CMTA, and CTME cabinet with an MSP shelf major
alarm
Determine if any
CONVERTER
procedure.
FAIL LEDs are lit.
Are any Y Replace the procedure.
CONVERTER converter.
FAIL LEDs lit?
N
Is a fuse Y Replace the
blown? fuse.
N
Contact the next End
level of support.
GSP05 (CSP10)
Ext FSP
Clearing an Ext FSP CISM, CMTA, and CTME cabinet with an MSP shelf major
alarm
At the CISM, CMTA ,CTME cabinets or ISME frame
LEDs are lit.
are lit step 6

are not lit step 2
2 Determine if the MSP has any blown fuses.
If a fuse Do
has blown step 3

fuse.
Note: The ISME frame and CISM cabinet can have an input/output module
(IOM). An IOM occupies slot positions 2 and 3 of the integrated services
module (ISM). Fuses in MSP fuse positions 71–07, 71–08 and 71–09 control
IOM slots.
297-2651-543 Standard 05.01 March 1999

Ext FSP
5
Danger
Risk of fire
manufacturer.
DANGER
Risk of fire
manufacturer.
If the fuse Do

is ON step 8
is OFF step 7
7 Turn the POWER switch on the converter to ON.
is lit step 8
is not lit step 28
GSP05 (CSP10)
Ext FSP
8 Record the number of the shelf with the lit CONVERTER FAIL LED. The shelf
9 Identify the circuit breaker on the MSP for the shelf that contains the lit
CONVERTER FAIL LED.
Note: A label for a circuit breaker contains numbers for breaker identification,
equipment shelf and circuit pack position. For example, CB02-47-01 is CB 02
for shelf 47 and number 01 for the circuit pack position.
is ON step 11
is OFF step 12
breaker to ON.
Note: The shelf can contain two converters with lit CONVERTER FAIL LEDs.
When both converters have lit CONVERTER FAIL LEDs, press and hold the
RESET button on the inner converter. Press and hold the RESET button while
you set the circuit breaker to ON (up). After you set the inner converter, press
the RESET button to reset the outer converter.

FAIL LED is lit
FAIL LED is not lit
FAIL LED is lit
LED.
At the CPDC
15 Locate the circuit breaker that powers the CISM, CMTA or CTME shelf.
297-2651-543 Standard 05.01 March 1999

Ext FSP
is OFF step 17
is ON step 20

breaker to ON.
turns OFF again, and the step 23

FAIL LED is not lit
FAIL LED is lit

GSP05 (CSP10)
Ext FSP
22 Determine the state of the converter that you replaced. Determine the state of
the associated circuit breaker.

FAIL LED stays lit
FAIL LED is not lit
FAIL LED is lit
23 Determine if the backplane of the shelf has short-circuited or bent pins.

are present step 32

24 Make sure that the circuit breaker is OFF.

point.
26 Press and hold the RESET button on the converter while you set the associated
circuit breaker to ON.
RESET button on the inner converter. Press and hold the RESET button while
you set the circuit breaker to ON. After you reset the inner converter, press the
RESET button to reset the outer converter.
is lit step 32
is not lit step 28
297-2651-543 Standard 05.01 March 1999

Ext FSP
is lit, and more blown fuses exist step 2

is lit, and more blown fuses do not step 35
exist
is not lit step 29
At the MAP terminal

>MAPCI;MTC;EXT
If an FSP alarm Do

31 Perform the correct procedure for the type of frame that has the FSP alarm.
GSP05 (CSP10)
Ext FSP
32
DANGER

Determine if the supply wiring for an alarm battery in the MSP is short-circuited.
If the alarm battery Do
has short-circuited step 35

has not short-circuited (IOM) step 33
At the CISM cabinet or ISME frame

33 To replace the NTFX30 IOM controller card, perform the correct procedure in
point.
34 Insert another replacement fuse
If the fuse Do

297-2651-543 Standard 05.01 March 1999

Ext FSP
CISM, CMTA,
CISM, and CTME
CMTA, cabinet
and CTME with with
an MSP majormajor
(continued)
(end)
GSP05 (CSP10)
Ext FSP
CPDC cabinet major
Alarm display
. . . . . . . . nFSP .
M
Indication
Meaning
cabinets. The number under the EXT header of the alarm banner indicates
the number of cabinets affected.
Result
Common procedures
Action
297-2651-543 Standard 05.01 March 1999

Ext FSP
CPDC cabinet major (continued)
Summary of Clearing an Ext FSP CPDC cabinet major alarm

procedure.

procedure
Y Y Replace
Is an alarm Is a breaker
1 capacitor, if
LED lit? OFF?
appropriate.
N N
Is the ABS Y Contact next Reset circuit

fuse blown? level of support breaker
Replace fuse
Y Breaker goes
OFF again?
Fuse blows Y
again? FF lamp Y
2 1
remain lit?
N
2 N
Perform additional Y FSP alarm

checks according
present?
to procedure
N
End
GSP05 (CSP10)
Ext FSP
Clearing an Ext FSP CPDC cabinet major alarm
At the CPDC cabinet

1 The alarm LEDs are on the right sides of the breaker panels. Determine if any
of the alarm LEDs are lit.
If alarm LEDs Do
are lit step 2

are not lit step 3
2 Locate any breaker panel that indicates an alarm. Determine if one or more
circuit breakers are OFF.
If Do
one or more circuit breakers are step 4

OFF
all circuit breakers are ON step 3
3 Determine if the alarm battery supply (ABS) fuse on the FSP has blown.
If the ABS fuse Do
has blown step 21

297-2651-543 Standard 05.01 March 1999

Ext FSP
4 Determine the purpose of the circuit breaker that is OFF.

Note: The label under the circuit breaker specifies the element that the circuit
breaker supplies.
supplies talk battery to an LCE step 6

frame
does not supply talk battery to an step 5
LCE frame
supplies power to a filter capacitor step 24
on the CPDC breaker panel
5 Set the circuit breaker to ON. Go to step 20.
6 Record the numbers of the LCE frame and shelf that associate with the circuit
breaker.
At the LCE frame

7 Locate the ten talk battery fuses above the shelves. Remove the ten talk
battery fuses (five for each shelf).
Note: Talk battery A powers the first and third shelves from the bottom of the
LCE. Talk battery B powers the second and fourth shelves.
8 Obtain a capacitor forming tool.

Note 1: A capacitor forming tool consists of a 100-W 120-V light bulb in a
socket without insulation-ended twisted wires. The without insulation-ended
twisted wires must have spring-type alligator clips on each end.
Note 2: You can insert a new tool with the tool number T000655, CPC number
NTA0600512, into the fuse holder instead of the light bulb. You can insert the
new tool in the same method that you insert a fuse.
GSP05 (CSP10)
Ext FSP
9
DANGER
The fuse holder contacts on the filter panel faceplate
have high voltages. Do not touch the probes of the
capacitor forming tool to the faceplate of the filter
panel. Do not let the probes of the capacitor forming
tool touch each other.

The fuse holder contacts on the filter panel faceplate
have high voltages. Do not touch the probes of the
capacitor forming tool to the faceplate of the filter
panel. Do not let the probes of the capacitor forming
tool touch each other.
Connect the leads of the capacitor forming tool across the circuit breaker to
charge the capacitors.
After 5 s, if the light bulb Do
is lit step 10
is not lit step 16
At the LCE frame

10 Label the lead positive terminal of the capacitor as + (positive). Label the lead
of the negative terminal of the capacitor as – (negative).
11 Disconnect the leads from the short-circuited capacitor.
12 Remove the capacitor.
13 Install a replacement capacitor.
14 Connect the + (positive) lead to the positive terminal of the capacitor.
15 Connect the – (negative) lead to the negative terminal of the capacitor.

Go to step 9 to charge the capacitors again.
297-2651-543 Standard 05.01 March 1999

Ext FSP
At the back of the CPDC

16 Remove the capacitor forming tool.
At the front of the CPDC

17 Immediately set the circuit breaker to ON.
At the LCE frame

18 Insert the ten talk battery fuses that you removed in step 7, one at a time.
Pause between each fuse.
19 Depress the indicator on one of the talk battery fuses to determine if a talk
battery is present.
is lit step 39
is not lit step 20
At the CPDC
is OFF step 44
is ON step 39
21 Obtain a replacement fuse that has the same voltage and amperage as the
blown ABS fuse.
22 Remove the blown ABS fuse.
GSP05 (CSP10)
Ext FSP
23
DANGER
To protect against electrocution, replace the blown
fuse with a fuse of the same type, rating (color code),
and manufacturer.

To protect against electrocution, replace the blown
and manufacturer.
Insert the replacement ABS fuse.
If the fuse Do

24 Make sure that the circuit breaker for the capacitor remains OFF.

25 Obtain a capacitor forming tool and a voltmeter.
Note 1: A capacitor forming tool consists of a 100-W 120-V light bulb in a
socket without insulation-ended twisted wires. The without insulation-ended
twisted wires must have spring-type alligator clips on each end.
Note 2: You can insert a new tool with the tool number T000655, CPC number
26 Label the lead positive terminal of the capacitor as + (positive). Label the lead
negative terminal of the capacitor as – (negative).
27 Connect one lead of the capacitor forming tool to a ground stud. Connect the
lead to the ground stud on the ground plate for the battery return (L+) of the
breaker panel.
297-2651-543 Standard 05.01 March 1999

Ext FSP
28 Connect the other lead of the capacitor forming tool to the bottom post of the
circuit breaker that powers the short-circuited capacitor.
29 Use the voltmeter to make sure that no voltage is present across the terminals
of the capacitor.
30 Use the voltmeter to make sure that no voltage is present between either
terminal of the capacitor and the battery return.
31
DANGER
The terminals at the back of the CPDC have an
electrical potential of –48V dc to –60V dc. Use the
voltmeter to detect voltage. Do not attempt to replace
the capacitor.

The terminals at the back of the CPDC have an
electrical potential of –48V dc to –60V dc. Use the
voltmeter to detect voltage. Do not attempt to
replace the capacitor.
Make sure that the capacitor forming tool remains in place. Disconnect the
leads from the short-circuited capacitor.
34 Connect the positive lead to the positive terminal of the capacitor. Connect the
negative lead to the negative terminal of the capacitor.
35 Remove the capacitor forming tool.
36 To allow the capacitor to recharge, wait 3 to 5 min.
At the front of the CPDC

37 Set the circuit breaker for the capacitor to ON.
GSP05 (CSP10)
Ext FSP
is OFF step 44
is ON step 39
39 Determine if the FRAME FAIL LED on the FSP is lit.
is lit, and more circuit breakers are step 4

OFF
is lit, and no more circuit breakers step 43
are OFF
is not lit step 40
At the MAP terminal

40 To access the EXT level of the MAP terminal, type
>MAPCI;MTC;EXT
If an FSP alarm Do

297-2651-543 Standard 05.01 March 1999

Ext FSP
CPDC cabinet
CPDC majormajor
cabinet (continued)
(end)
43
DANGER

Determine if the ABS wiring inside the FSP is short-circuited. The next level of
support can ask for this information.
GSP05 (CSP10)
Ext FSP
DCE frame major
Alarm display
. . . . . . . . 1FSP .
M
Indication
for an external frame supervisory panel (FSP) major alarm.
Meaning
A power fault or a cooling unit fault is present in an office frame. The
number under the EXT header of the alarm banner indicates the number of
cabinets affected.
Result
Common procedures
Action
procedure.
297-2651-543 Standard 05.01 March 1999

Ext FSP
DCE frame major (continued)
Summary of Clearing an Ext FSP DCE frame major alarm

FAIL LEDs on
the FSP are lit. Use the instructions that follow
procedure.
Is a Y Replace
CONVERTER converter
FAIL LED lit?
N
Is an alarm Y Replace fuse

and battery
fuse blown?
N
Contact next End

level of support
GSP05 (CSP10)
Ext FSP
Clearing an Ext FSP DCE frame major alarm
At the DCE frame

1 Check each converter in the frame. Determine if any CONVERTER FAIL LEDs
are lit.
are lit step 6

are not lit step 2
2 Determine if any of the alarm battery supply (ABS) fuses (01 to 05) on the FSP
are blown.
If a fuse Do
has blown step 3

fuse.
297-2651-543 Standard 05.01 March 1999

Ext FSP
5
DANGER
Risk of fire
manufacturer.
DANGER
Risk of fire
manufacturer.
If the fuse Do

is ON step 8
is OFF step 7
is lit step 8
is not lit step 33
GSP05 (CSP10)
Ext FSP
CONVERTER FAIL LED.
9 Use the following table to identify the circuit breaker for the shelf that contains
the converter with the lit CONVERTER FAIL LED. The circuit breaker is on the
FSP.
Shelf number Circuit breaker number
65 CB1
51 CB2
32 CB3
18 CB4
04 CB5
10 Determine if the associated circuit breaker is ON or OFF.
is ON step 11
is OFF step 12
11 Set the identified circuit breaker to OFF.
breaker to ON.
RESET button on the innermost converter. Press and hold the RESET button
on the innermost converter while you set the circuit breaker to ON (up). After
you reset the innermost converter, press the RESET button to reset the
outermost converter.
297-2651-543 Standard 05.01 March 1999

Ext FSP
turns OFF, and the converter FAIL step 14

LED is lit
remains ON, and the converter FAIL step 33
LED is not lit
remains ON, and the converter step 25
FAIL LED is lit
14 Record the numbers of the frame and shelf with the lit converter FAIL LED.
At the PDC frame

15 Locate the fuse that powers the shelf in the data communications equipment
(DCE) frame.
16 Determine if the fuse is blown.
If the fuse Do
has blown step 17

GSP05 (CSP10)
Ext FSP
19
DANGER
Risk of fire
manufacturer.
DANGER
Risk of fire
manufacturer.
20 Install the fuse holder on the PDC frame.
21 Locate the fuse for the battery filter.
22 Determine if the fuse has blown.
If the fuse Do
has blown step 17

At the DCE frame

breaker to ON.
RESET button on the innermost converter. Press and hold the RESET button
on the innermost converter while you set the circuit breaker to ON (up). After
you reset the innermost converter, press the RESET button to reset the
outermost converter.
297-2651-543 Standard 05.01 March 1999

Ext FSP
turns OFF, and the converter FAIL step 26

LED is lit
LED is not lit
LED is lit
25 Set the associated circuit breaker to OFF.

27 Determine if the converter FAIL LED for the replaced converter is lit.
If the converter FAIL LED Do
is lit step 28
is not lit step 33
28 Determine if the backplane of the shelf has any short–circuited or bent pins.

bent pins
29 Record the number of the shelf that contains the converter with the lit converter
FAIL LED.
GSP05 (CSP10)
Ext FSP
30 Use the table and diagram to identify the alarm and control card for the shelf
Shelf number Alarm and control card Card position
04 slot CD1 (NT0X01AA) back

32 and 65 slot CD2 (NT0X91AB) center
18 and 51 slot CD3 (NT0X91AD) front
Card
holder
NT0X91AA
card in
slot CD1
NT0X91AB
card in
slot CD2
NT0X91AD
card in
slot CD3
FSP
31 Note the PM type, PM number, and unit number in each of the shelves
controlled by the alarm and control card. You identified the alarm and control
card in the previous step.
297-2651-543 Standard 05.01 March 1999

Ext FSP

present
present
is not lit step 34
At the MAP terminal

>MAPCI;MTC;EXT
If an FSP alarm Do

This document contains a list of steps. Complete the procedure and return to
this point.
GSP05 (CSP10)
Ext FSP
(end)
At the DCE frame
37
DANGER

Unscrew the slotted nut to the left of the FSP.
38 Open the FSP panel.
39 Determine if the supply wiring for the alarm battery of the MSP is
short-circuited. The next level of support can request this information.
297-2651-543 Standard 05.01 March 1999

Ext FSP
DPCC cabinet major
Alarm display
. . . . . . . . 1FSP .
M
Indication
Meaning
cabinets.
Result
Common procedures
Action
GSP05 (CSP10)
Ext FSP
DPCC cabinet major (continued)
Summary of Clearing an Ext FSP DPCC cabinet major alarm

LED on the FSP
is lit Use the instructions that follow
procedure.
BLOWER unit
FAIL LED lit?
N
Is a Y Replace
CONVERTER converter
OFF LED lit?
N
Y Replace fuse End
Is a fuse
blown?
N
Contact the next
level of support
297-2651-543 Standard 05.01 March 1999

Ext FSP
Clearing an Ext FSP DPCC cabinet major alarm
At the DPCC
If the BLOWER FAIL LED on the

FSP Do
is lit step 38
is not lit step 2
2 Check each converter in the cabinet. Determine if any of the CONVERTER

OFF LEDs are lit.
If any CONVERTER OFF LEDs Do
are lit step 7

are not lit step 3
3 Determine if any of the fuses from 01 to 16 on the FSP have blown.
If a fuse Do
has blown step 4

fuse.
GSP05 (CSP10)
Ext FSP
6
DANGER
Risk of fire
manufacturer.
DANGER
Risk of fire
manufacturer.
If the fuse Do
has blown step 31

is lit step 8
is not lit step 37
CONVERTER OFF LED.
9 Determine if the cabinet is a DPCC SuperNode or a DPCC SuperNode SE.
If the cabinet Do
is a DPCC SuperNode step 11

is a DPCC SuperNode SE step 10
297-2651-543 Standard 05.01 March 1999

Ext FSP
10 Use the following table to identify the fuse for the shelf that contains the lit
CONVERTER OFF LED:
Shelf Fuse
0 (left side) 01
0 (right side) 05
1 (left side) 02
1 (right side) 06
2 (left side) 03
2 (right side) 07
3 (left side) 04
3 (right side) 08
Note: This document numbers the shelves from top to bottom. Shelf 0 is
below the FSP. Shelf 3 is the bottom shelf. The different sides of each shelf
(left and right) relate to different FSP fuses, as listed in the previous table.
Go to step 12.
11 Use the following table to identify the fuse for the shelf that contains the lit
CONVERTER OFF LED:
Shelf Fuse
MS0 (left side) 01

MS0 (right side) 02
MS1 (left side) 03
MS1 (right side) 04
CM0 (left side) 05
CM0 (right side) 06
CM/SLM (left side) 07
CM/SLM (right side) 08
GSP05 (CSP10)
Ext FSP
If the fuse Do
has blown step 13

fuse.
15
DANGER
Risk of fire
manufacturer.
DANGER
Risk of fire
manufacturer.
If the fuse Do

OFF LED is lit
16 Determine if the DPCC connects to a PDC or CPDC.
297-2651-543 Standard 05.01 March 1999

Ext FSP
If the DPCC Do
connects to a PDC step 17

connects to a CPDC step 23
At the PDC
17 Locate the fuse that powers the DPCC shelf.
If the fuse Do
has blown step 19

20 Obtain a replacement fuse.
21
DANGER
Risk of fire
manufacturer.
DANGER
Risk of fire
manufacturer.
22 Install the fuse holder back into the PDC shelf.

Go to step 26.
GSP05 (CSP10)
Ext FSP
At the CPDC
23 Locate the circuit breaker that powers the DPCC shelf.
is OFF step 25
is ON step 29
At the DPCC
fuse.
28
DANGER
Risk of fire
manufacturer.
DANGER
Risk of fire
manufacturer.
is lit step 29
is not lit step 37
297-2651-543 Standard 05.01 March 1999

Ext FSP

Replacement Procedure. Complete the procedure and return to this point.
30 Determine if the CONVERTER OFF LED for the converter card that you
replaced is lit.
is lit step 43
is not lit step 37
31 Determine which fuse is blown.
is one of 09, 11, 14, 15, or 16 step 43

32 Use the following table to identify the alarm and control card that associate with
the blown fuse:

fuse.
GSP05 (CSP10)
Ext FSP
36
DANGER
Risk of fire
Replace the blown fuse with a fuse of the same type,
rating (color code), and manufacturer. This procedure
protects against the risk of fire.
DANGER
Risk of fire
If the fuse Do


present
present
is not lit step 40
point.
297-2651-543 Standard 05.01 March 1999

Ext FSP
DPCC cabinet
DPCC majormajor
cabinet (continued)
(end)
is lit step 2
is not lit step 40
At the MAP terminal

>MAPCI;MTC;EXT
If an FSP alarm Do

GSP05 (CSP10)
Ext FSP
DSNE frame or CDSN cabinet major
Alarm display
. . . . . . . . 1FSP .
M
Indication
Meaning
A power fault or a cooling unit fault exists on one or more office frames.
of frames affected.
Result
Common procedures
Action
procedure.
Note: This procedure applies to a double shelf network equipment (DSNE)

frame and a cabinetized dual-shelf network (CDSN) that has an FSP. The
term DSNE also refers to this type of CDSN, unless otherwise specified.
297-2651-543 Standard 05.01 March 1999

Ext FSP
DSNE frame or CDSN cabinet major (continued)
Summary of Clearing an Ext FSP DSNE frame or CDSN cabinet major alarm

on the FSP is lit.
procedure.
Is the FAN Y Repair cooling
FAIL lamp lit? unit.
Is a Replace
Y
FAIL LED lit?
N
Has an alarm Y Replace fuse.

and battery
fuse blown?
N
Contact next End

level of support.
GSP05 (CSP10)
Ext FSP
Clearing an Ext FSP DSNE frame or CDSN cabinet major alarm
At the DSNE frame

is lit step 33
is not lit step 2
are lit.
are lit step 7

are not lit step 3
have blown.
If a fuse Do
has blown step 4

fuse.
297-2651-543 Standard 05.01 March 1999

Ext FSP
6
DANGER

If the fuse Do

is ON step 9
is OFF step 8
is lit step 9
is not lit step 32
GSP05 (CSP10)
Ext FSP
CONVERTER FAIL LED.
10 Use the following table to identify which circuit breaker associates with the shelf
that contains the converter with the lit CONVERTER FAIL LED. The circuit
breaker is on the FSP.
65 CD1
51 CD2
18 CD4
32 CD5
is ON step 12
is OFF step 13
breaker to ON.

FAIL LED is lit
FAIL LED is not lit
FAIL LED is lit
15 Record the numbers of the frame and shelf that contain the converter with the lit
CONVERTER FAIL LED.
297-2651-543 Standard 05.01 March 1999

Ext FSP
At the PDC frame

16 Locate the fuse that powers the shelf in the DSNE frame.
If the fuse Do
has blown step 18

20
DANGER

At the DSNE frame

breaker to ON.
GSP05 (CSP10)
Ext FSP

FAIL LED is lit
FAIL LED is not lit
FAIL LED is lit

26 Determine if the CONVERTER FAIL LED on the replaced converter is lit.
is lit step 27
is not lit step 32

bent pins
CONVERTER FAIL LED.
297-2651-543 Standard 05.01 March 1999

Ext FSP
29 Use the table and diagram to identify which alarm and control card associates
with the shelf that contains the converter with the lit CONVERTER FAIL LED.
65 and 51 slot CD1 (NT0X91AA) back

32 and 18 slot CD2 (NT0X91AE) front
Card
holder
NT0X91AA
card in
slot CD1
NT0X91AE
card in
slot CD2
Frame
supervisory panel
30 Record the numbers of the network plane and the network module for the
shelves that the alarm and control card control. You identified the alarm and
control card in the previous step.
GSP05 (CSP10)
Ext FSP
At the DSNE frame

is lit, and more blown fuses is step 3

present
is lit, and more blown fuses is not step 41
present
is not lit step 35
point.
is lit step 2
is not lit step 35
At the MAP terminal

>MAPCI;MTC;EXT
297-2651-543 Standard 05.01 March 1999

Ext FSP
DSNE frameframe
DSNE or CDSN cabinet
or CDSN majormajor
cabinet (continued)
(end)
If an FSP alarm Do

This document contains a list of procedures. Complete the procedure and
At the DSNE frame

38
DANGER

40 Determine if the alarm battery supply wiring inside the FSP is short–circuited.
The next level of support can request this information.
GSP05 (CSP10)
Ext FSP
DTE or IDTE frame major
Alarm display
. . . . . . . . 1FSP .
M
Indication
Meaning
A power fault or a cooling unit fault exists in one or more office frames.
of frames affected.
Result
Common procedures
Action
procedure.
Note: This procedure applies to a digital trunk equipment (DTE) frame and
an international digital trunk equipment (IDTE) frame. The word DTE also
refers to IDTE, unless otherwise specified..
297-2651-543 Standard 05.01 March 1999

Ext FSP
DTE or IDTE frame major (continued)
Summary of Clearing an Ext FSP DTE or IDTE frame major alarm

on the FSP is lit
Repair cooling procedure.
Is the FAN Y
FAIL lamp lit? unit
Is a Y Replace
CONVERTER converter
FAIL LED lit?
N
Has an alarm Y Replace fuse

and battery
fuse blown?
N
Contact next End

level of support
GSP05 (CSP10)
Ext FSP
Clearing an Ext FSP DTE or IDTE frame major alarm
At the DTE frame

is lit step 35
is not lit step 2
are lit.
are lit step 7

are not lit step 3
have blown.
If a fuse Do
has blown step 4

fuse.
297-2651-543 Standard 05.01 March 1999

Ext FSP
6
Danger
Risk of fire
To protect against the risk of fire, replace the blown
and manufacturer.
DANGER
Risk of fire
To protect against the risk of fire, replace the blown
and manufacturer.
If the fuse Do

is ON step 9
is OFF step 8
is lit step 9
is not lit step 34
GSP05 (CSP10)
Ext FSP
CONVERTER FAIL LED.
10 Use the following table to identify which circuit breaker associates with the shelf
with the lit CONVERTER FAIL LED. The circuit breaker is on the FSP.
65 CD1
32 CD2
51 CD4
18 CD5
is ON step 12
is OFF step 13
12 Set the circuit breaker you identified to OFF.
breaker to ON.

FAIL LED is lit
FAIL LED is not lit
FAIL LED is lit
CONVERTER FAIL LED.
297-2651-543 Standard 05.01 March 1999

Ext FSP
At the PDC frame
16 Locate the fuse that powers the shelf in the DTE frame.
If the fuse Do
has blown step 18

19
Danger
Risk of fire
manufacturer.
DANGER
Risk of fire
manufacturer.
Replace the cartridge fuse inside the fuse holder.
22 Locate the battery filter fuse.
GSP05 (CSP10)
Ext FSP
If the fuse Do
has blown step 18

At the DTE frame

breaker to ON.

FAIL LED is lit
FAIL LED is not lit
FAIL LED is lit

is lit step 29
is not lit step 34
297-2651-543 Standard 05.01 March 1999

Ext FSP
are present step 43

CONVERTER FAIL LED.
GSP05 (CSP10)
Ext FSP
18 and 51 slot CD1 (NT0X91AA) rear

Card
holder
NT0X91AA
card in
slot CD1
NT0X91AE
card in
slot CD2
Frame
supervisory panel
32 Record the PM type, number, and unit number of each of the shelves that the
alarm and control card control. You identified the alarm and control card in the
previous step.
297-2651-543 Standard 05.01 March 1999

Ext FSP

present
present
is not lit step 37
to this point.
is lit step 2
is not lit step 37
At the MAP terminal

>MAPCI;MTC;EXT
If an FSP alarm Do

GSP05 (CSP10)
Ext FSP
(end)
At the DTE frame

40
Danger

42 Determine if the supply wiring of the alarm inside the FSP is short-circuited.
297-2651-543 Standard 05.01 March 1999

Ext FSP
TME frame or CTME cabinet with FSP shelf major
Alarm display
. . . . . . . . 1FSP .
M
Indication
Note: This procedure applies only to trunk module equipment (TME)

frames and cabinetized trunk module equipment (CTME) frames
provisioned with an FSP. The Ext FSP alarm clearing procedure for CTME
provisioned with an MSP is in another procedure. This procedure is “Ext
FSP in CISM, CMTA, and CTME cabinets with an MSP shelf major”.
Meaning
A power fault or a cooling unit fault is present in one or more office frames
or cabinets. The number that precedes the FSP in the alarm banner indicates
the number of frames or cabinets affected.
Result
The impact on subscriber service depends on the type of the fault. The
impact on subscriber service also depends on the types of subsystems
provisioned in the frame or cabinet.
Common procedures
Action
procedure.
GSP05 (CSP10)
Ext FSP
TME frame or CTME cabinet with FSP shelf major (continued)
Summary of Clearing an Ext FSP TME frame or CTME cabinet with FSP shelf major alarm

FAIL LEDs are
lit. Use the instructions that follow this
Are any Replace power

Y
FAIL LEDs lit?
N
Is an alarm Y Replace fuse.

and battery
fuse blown?
N
Contact next End

level of support.
297-2651-543 Standard 05.01 March 1999

Ext FSP
Clearing an Ext FSP TME frame or CTME cabinet with FSP shelf major alarm
At the TME frame or CTME cabinet

1 Determine if any of the CONVERTER FAIL LEDs on power converters are lit.
are lit step 6

are not lit step 2
2 Determine if any of the alarm battery supply (ABS) or cooling unit fuses on the
FSP are blown.
Note: In the TME FSP, the ABS fuse numbers are 01 to 03. In the CTME FSP,
the ABS fuse numbers are 7 to 10. In the CTME FSP, the cooling unit fuse
numbers are 11 and 14.
If a fuse Do
has blown step 3

3 Obtain a replacement fuse with the same voltage and amperage rating as the
blown fuse.
GSP05 (CSP10)
Ext FSP
5
Danger
Risk of fire
manufacturer.

Risk of fire
manufacturer.
If the fuse Do

6 Determine if the POWER switch on the converter is set to OFF.
is OFF step 7
is ON step 8
7 Set the POWER switch on the power converter to ON.
is lit step 8
is not lit step 46
297-2651-543 Standard 05.01 March 1999

Ext FSP
8 Record the number of the cabinet and shelf that contain the power converter
with the CONVERTER FAIL LED lit.
If you Do
work on a TME frame step 9

work on a CTME cabinet step 14
9 Use the table to identify the circuit breaker that controls the power to the shelf
with the lit CONVERTER FAIL LED. The FSP holds the circuit breaker.
Circuit breaker number Shelf number
01 65
02 51
03 32
04 18
05 04
10 Determine if the associated breaker is set to OFF.
is set to OFF step 11

is set to ON step 12
12 Press the RESET button on the power converter.
GSP05 (CSP10)
Ext FSP
trips again, and the CONVERTER step 21

FAIL LED is lit
does not trip, and the CONVERTER step 38
FAIL LED is lit
does not trip, and the CONVERTER step 46
FAIL LED is not lit
14 Use the table to identify the fuse on the FSP for the shelf with the lit
CONVERTER FAIL LED.
Fuse number Shelf number
01 05
02 33
04 19
05 47
15 Determine if the fuse that controls power to the shelf has blown.
If the fuse Do
has blown step 16

297-2651-543 Standard 05.01 March 1999

Ext FSP
16 Obtain a replacement fuse with the same voltage and amperage rating as the
blown fuse.
17
Danger
Risk of fire
manufacturer.
DANGER
Risk of fire
manufacturer.
Remove the blown fuse.
If the fuse Do

FAIL LED is lit
GSP05 (CSP10)
Ext FSP
21 The next step depends on if the office has a power distribution center (PDC) or
a cabinetized PDC (CPDC).
If the office Do
has a PDC step 22

has a CPDC step 28
At the PDC
22 Locate the fuse that powers the shelf in the TME or CTME.
If the fuse Do
has blown step 24

26
Danger
Risk of fire
DANGER
Risk of fire
297-2651-543 Standard 05.01 March 1999

Ext FSP
If you Do

At the CPDC
28 Locate the circuit breaker that powers the shelf in the TME frame or CTME
cabinet.
29 Determine if the circuit breaker is set to OFF.
is OFF step 30
is ON step 38
31 The next step depends on the type of frame that you work on.
If you Do

At the TME frame

fuse.
GSP05 (CSP10)
Ext FSP
34
Danger
Risk of fire
manufacturer.
DANGER
Risk of fire
manufacturer.
Insert the replacement fuse. Go to step 36.
At the CTME cabinet


is lit step 38
is not lit step 46
38 To replace the power converter, perform the correct procedure in Card

297-2651-543 Standard 05.01 March 1999

Ext FSP
39 Determine if the CONVERTER FAIL LED for the power converter that you
replaced is lit.
is lit step 40
is not lit step 46

bent pins
41 The next step depends on the type of frame that you work on.
If you Do

GSP05 (CSP10)
Ext FSP
At the TME frame
42 Use the table and diagram to identify the drive and alarm card for the shelf with
the lit CONVERTER FAIL LED.
Drive and FSP card FSP circuit

alarm card position breakers Shelf position
NT0X91AA CD1 CB5 04

NT0X91AB CD2 CB3 32
CB1 65
NT0X91AD CD3 CB4 18
CB2 51
Card
holder
NT0X91AA
card in
slot CD1
NT0X91AB
card in
slot CD2
NT0X91AD
card in
slot CD3
FSP
43 Go to step 45.
297-2651-543 Standard 05.01 March 1999

Ext FSP
At the CTME cabinet

Power and FSP

alarm card fuse Shelf
slot number position
PWR ALM 1 01 05
02 33
PWR ALM 2 04 19
PWR ALM 3 05 47
NT0X36AB
card in slot
PWR ALM 1
NT0X36AB
card in slot
PWR ALM 2
NT0X36AB
card in slot
PWR ALM 3
Frame
supervisory panel
GSP05 (CSP10)
Ext FSP
is lit, and more fuses that have step 2

blown are present
is lit, and more blown fuses that step 53
have not blown are present
is not lit step 47
At the MAP terminal

>MAPCI;MTC;EXT
If an FSP alarm Do
is present, and you did not correct step 49

the power faults on all the frames
with an FSP alarm
is present, and you corrected the step 53
power faults on all the frames with
an FSP alarm
49 Determine the type of frame that has the FSP alarm. Perform the correct
procedure in this NTP to clear the alarm. Complete the procedure and go to
step 48.

50 Unscrew the slotted nut to the left of the FSP.
297-2651-543 Standard 05.01 March 1999

Ext FSP
TME TME
frameframe
or CTME cabinet
or CTME with with
cabinet FSP shelf majormajor
FSP shelf (continued)
(end)
52
Danger

Determine if the ABS wiring inside the FSP has short-circuited. The next level
of support can request this information.
GSP05 (CSP10)
Ext FSP
IOE frame and CIOE cabinet major
Alarm display
. . . . . . . . 1FSP .
M
Indication
Meaning
cabinets.
of frames affected.
Result
Common procedures
Action
review the procedure. Follow the instructions to perform the procedure.
Note: This procedure applies to an input/output equipment (IOE) frame and

cabinetized input/output equipment (CIOE) that has an FSP. In this
procedure, IOE also refers to this type of CIOE, unless the procedure
specifies otherwise.
297-2651-543 Standard 05.01 March 1999

Ext FSP
IOE frame and CIOE cabinet major (continued)
Summary of Clearing an Ext FSP IOE frame and CIOE cabinet major alarm

FAIL LEDs are
lit. Use the instructions that follow this
Are any Replace

Y
FAIL LEDs lit?
N
Is an alarm Y Replace fuse.

and battery
fuse blown?
N
Contact next End

level of support.
GSP05 (CSP10)
Ext FSP
Clearing an Ext FSP IOE frame and CIOE cabinet major alarm
At the IOE frame

1 Check each converter in the frame. Determine if any of the CONVERTER FAIL
LEDs are lit.
If any CONVERTER FAIL LEDS Do
are lit step 6

are not lit step 2
2 Locate the alarm battery supply (ABS) fuses (05 to 08) on the FSP. Determine
if any of the ABS fuses are blown.
If a fuse Do
has blown step 3

fuse.
297-2651-543 Standard 05.01 March 1999

Ext FSP
5
Danger
Risk of fire
manufacturer.
DANGER
Risk of fire
manufacturer.
If the fuse Do

is ON step 8
is OFF step 7
if the CONVERTER FAIL LED Do
is lit step 8
is not lit step 35
GSP05 (CSP10)
Ext FSP
CONVERTER FAIL LED.
9 Locate the fuses on the FSP. Use the following table to identify which fuse
associates with the shelf that contains the lit CONVERTER FAIL LED.
Shelf number Fuse number
32 01
18 02
04 03
10 Determine if the associated fuse has blown.
If the fuse Do
has blown step 11

fuse.
12
Danger
Risk of fire
manufacturer.
DANGER
Risk of fire
manufacturer.
Remove the blown fuse.
297-2651-543 Standard 05.01 March 1999

Ext FSP
14 Press the RESET button on the converter.
If the fuse Do

FAIL LED is lit
CONVERTER FAIL LED.
At the PDC frame

17 Locate the fuse that powers the shelf in the IOE frame.
If the fuse Do
has blown step 19

19 Remove the fuse holder with the blown fuse.
GSP05 (CSP10)
Ext FSP
21
Danger
Risk of fire
manufacturer.
DANGER
Risk of fire
manufacturer.
At the IOE frame

fuse.
25
Danger
Risk of fire
manufacturer.
DANGER
Risk of fire
manufacturer.
297-2651-543 Standard 05.01 March 1999

Ext FSP
is lit step 28
is not lit step 35

is lit step 30
is not lit step 35
are present step 42

CONVERTER FAIL LED.
GSP05 (CSP10)
Ext FSP
32 Use the following table and diagram. Identify which alarm and control card
associates with the shelf with the lit CONVERTER FAIL LED.
18 slot 2 (NT0X36AB) left

04 and 32 slot 2 (NT0X36AB right
NT0X36AB
card in slot
PWR ALM 1
NT0X36AB
card in slot
PWR ALM 2
Frame
supervisory
panel
33 Record the input/output controller (IOC) number, and the disk drive unit (DDU)
number. Record the numbers in each of the shelves controlled by the alarm
and control card that you identified.
297-2651-543 Standard 05.01 March 1999

Ext FSP
At the IOE frame

present
present
is not lit step 36
At the MAP terminal

>MAPCI;MTC;EXT
If an FSP alarm Do

GSP05 (CSP10)
Ext FSP
(end)
At the IOE frame
39
Danger

41 Determine if the alarm battery supply wiring inside the FSP is short-circuited.
297-2651-543 Standard 05.01 March 1999

Ext FSP
LPP and ELPP cabinet major
Alarm display
. . . . . . . . 1FSP .
M
Indication
EXT header of the alarm banner. The FSP indicates an external frame
supervisory panel (FSP) major alarm.
Meaning
One or more cabinets in the office has a power fault or a cooling unit fault.
Result
Common procedures
Action
procedure.
GSP05 (CSP10)
Ext FSP
LPP and ELPP cabinet major (continued)
Summary of Clearing an Ext FSP LPP and ELPP cabinet major alarm

LED on FSP is lit
Y procedure
Is the Repair cooling
BLOWER unit
FAIL LED lit?
N
Is a Y Replace
CONVERTER converter
OFF LED lit?
N
Y Replace fuse End
Is a fuse
blown?
Contact next
level of support
297-2651-543 Standard 05.01 March 1999

Ext FSP
Clearing an Ext FSP LPP and ELPP cabinet major alarm
At the LPP or ELPP
If the BLOWER FAIL LED Do
is lit step 31
is not lit step 2
2 Check each power converter in the cabinet. Determine if any of the

CONVERTER FAIL LEDs are lit.
If CONVERTER OFF LEDs Do
are lit step 3

are not lit step 20
is lit step 4
is not lit step 32
CONVERTER OFF LED.
GSP05 (CSP10)
Ext FSP
5 Use the following table to identify the fuse for the shelf that has the lit
CONVERTER FAIL LED.
Shelf number Fuse
39 (left side) 01
39 (right side) 02
26 (left side) 03
26 (right side) 04
13 (left side) 05
13 (right side) 06
00 (left side) 07
00 (right side) 08
If the fuse Do
has blown step 7

fuse.
297-2651-543 Standard 05.01 March 1999

Ext FSP
9
Danger
Risk of fire
manufacturer.
DANGER
Risk of fire
manufacturer.
If the fuse Do

OFF LED is lit
10 Record the number of the shelf with the lit CONVERTER OFF LED. The shelf
At the CPDC
11 Locate the circuit breaker that powers the LPP or ELPP shelf.
is OFF step 13
is ON step 18
GSP05 (CSP10)
Ext FSP

At the LPP or ELPP
fuse.
17
Danger
Risk of fire
manufacturer.
DANGER
Risk of fire
manufacturer.

Go to step step 19.

19 Determine if the CONVERTER OFF LED for the power converter card you
replaced is lit.
If the CONVERTER OFF LED is Do
is lit step 36
is not lit step 32
297-2651-543 Standard 05.01 March 1999

Ext FSP
20 Determine if any of fuses 01 to 04 on the FSP have blown.
If a fuse Do
has blown step 21

fuse.
23
Danger
Risk of fire
manufacturer.
DANGER
Risk of fire
manufacturer.
If the fuse Do

GSP05 (CSP10)
Ext FSP
24 Determine the fuse that has blown.
is one of 09, 11, 14, 15, or 16 step 36

25 Use the following table to identify the alarm and control card that associates
with the blown fuse.

fuse.
297-2651-543 Standard 05.01 March 1999

Ext FSP
29
Danger
Risk of fire
manufacturer.
DANGER
Risk of fire
manufacturer.
If the fuse Do


present
present
is not lit step 33
point.
GSP05 (CSP10)
Ext FSP
(end)
is lit step 2
is not lit step 33
At the MAP terminal

MAPCI;MTC;EXT
34 Determine if an FSP alarm exists.
If an FSP alarm Do

297-2651-543 Standard 05.01 March 1999

Ext FSP
MEX frame major
Alarm display
. . . . . . . . 1FSP .
M
Indication
Meaning
Result
Common procedures
Action
procedure.
GSP05 (CSP10)
Ext FSP
MEX frame major (continued)
Summary of Clearing an Ext FSP MEX frame major alarm

Determine if procedure.
FAN FAIL lamp
on FSP is lit Use the instructions that follow
procedure
Repair cooling
Is the FAN Y
unit
FAIL lamp lit?
Is a Replace
Y
CONVERTER converter
FAIL LED lit?
N
Has an alarm Y Replace fuse

and battery
fuse blown?
N
Contact next End

level of support
297-2651-543 Standard 05.01 March 1999

Ext FSP
Clearing an Ext FSP MEX frame major alarm
At the MEX frame
is it step 75
is not lit step 2
are lit.
are lit step 7

are not lit step 3
have blown.
If a fuse Do
has blown step 4

fuse.
GSP05 (CSP10)
Ext FSP
6
Danger
Risk of fire
manufacturer.
DANGER
Risk of fire
manufacturer.
If the fuse Do
blows again step 80

does not blow step 74
is ON step 9
is OFF step 8
is lit step 9
is not lit step 74
297-2651-543 Standard 05.01 March 1999

Ext FSP
CONVERTER FAIL LED.
10 Use the following table to identify the FSP fuse for the shelf with the lit
CONVERTER FAIL LED.
65 01
51 02
32 03
18 04
If the fuse Do
has blown step 12

12 Record the number of the data store (DS) in the shelf that associates with the
blown fuse.
Note: The DS number is 0 or 1.
At the MAP terminal
13 To access the CC level of the MAP display, type
>MAPCI;MTC;CC
14 Record the number of the active central processing unit (CPU) and inactive
CPU.
GSP05 (CSP10)
Ext FSP
15 Your next step depends on the DS number that you noted in step 12. Your next
step also depends on the CPU that you noted as active in step 14.
If the DS number Do
is 0 and the active CPU is 1 step 19

At the MAP terminal

>MAPCI;MTC;CC
17 To switch CPU activity, type

>SWACT
Note: The CPU must be inactive. The CPU is in the frame that contains the
alarm and control card you want to replace.
18 To confirm the SWACT command, type

>YES
297-2651-543 Standard 05.01 March 1999

Ext FSP
At the CCC frame
19 Go to the CCC frame that contains the inactive CPU.
20
WARNING
Wear a wrist strap that connects to a wrist-strap
handle the ENAB and DACT switches. The wrist
strap protects the switches against static electricity
damage.
CAUTION FOR ESDS

Wear a wrist strap that connects to a wrist-strap
to handle the ENAB and DACT switches. The wrist
damage.
Note: The NT1X48 card is in the CPU. The CPU is in the CCC frame.
22 Note the number of the CMC in the CCC frame that contains the inactive CPU.
At the MAP terminal
23 To access the CMC level of the MAP display, type
>MAPCI;MTC;CMC
24 To manually busy the CMC, type

>BSY
GSP05 (CSP10)
Ext FSP

>SYNCLK
26 Determine if the clock for the inactive CCC frame is active.
If the clock Do
is active step 27
is not active step 28
27 To switch clock activity, type

>SWACT
If the SWACT command Do
passes step 28
fails step 83
At the MEX frame

fuse.
297-2651-543 Standard 05.01 March 1999

Ext FSP
30
Danger
Risk of fire
manufacturer.
DANGER
Briefly state reasons for the danger
Enter the reasons the danger: a danger alerts the
reader to a risk of personal injury or death.
If the fuse Do

FAIL LED is lit
33 Press and release the RESET button on the converter with the lit CONVERTER
FAIL LED.
is lit step 34
is not lit step 74
34 Record the numbers of the frame and shelf that contain the lit CONVERTER
FAIL LED.
GSP05 (CSP10)
Ext FSP
At the PDC frame
35 Locate the fuse that powers the shelf in the MEX frame.
If the fuse Do
has blown step 37

39
Danger
Risk of fire
manufacturer.
DANGER
Risk of fire
manufacturer.
40 Install the fuse holder into the PDC frame.
297-2651-543 Standard 05.01 March 1999

Ext FSP
At the MEX frame
If the fuse Do

FAIL LED is lit
42 Note the number of the DS in the shelf that associates with the blown fuse.
Note: The DS number is 0 or 1.
At the MAP terminal
>MAPCI;MTC;CC
44 Record the number of the active CPU and inactive CPU.
45 Your next step depends on the DS number that you noted in step 42. Your next
step also depends on the CPU that you noted as active in step 44.
If the DS number Do

At the MAP terminal

>MAPCI;MTC;CC
GSP05 (CSP10)
Ext FSP
47 To switch CPU activity, type

>SWACT
Note: The CPU must be inactive. The CPU is in the frame that contains the
alarm and control card you want to replace.
48 To confirm the SWACT command , type

>YES
At the CCC frame
49 Go to the CCC frame that contains the inactive CPU.
50
WARNING
handle the ENAB and DACT switches. The wrist
damage.
CAUTION FOR ESDS

to handle the ENAB and DACT switches. The wrist
damage.
52 Note the number of the CMC in the CCC frame that contains the inactive CPU.
297-2651-543 Standard 05.01 March 1999

Ext FSP
At the MAP terminal
53 To access the CMC level of the MAP display, type
>MAPCI;MTC;CMC
54 To manually busy the CMC, type

>BSY
55 Determine if the clock for the inactive CCC frame is active.
If the clock Do
is active step 56
56 To switch clock activity, type

>SWACT
If the SWACT command Do
passes step 57
fails step 83
If the fuse Do

FAIL LED is lit
58 To replace the converter, perform the appropriate procedure in Card

GSP05 (CSP10)
Ext FSP
59 Determine the state of the converter that you replaced and the associated fuse.
If the fuse Do

FAIL LED is lit
are present step 83

297-2651-543 Standard 05.01 March 1999

Ext FSP
Shelf number Alarm and control card
18 and 51 slot 1 (NT0X36AB)

32 and 65 slot 2 (NT0X36AB)
NT0X36AB
card in slot
PWR ALM 1
NT0X36AB
card in slot
PWR ALM 2
Frame
supervisory
panel
GSP05 (CSP10)
Ext FSP
62 Use the following table to identify fuses for the shelves controlled by the alarm
and control card you want to replace. The fuses are on the FSP.
65 01
51 02
32 03
18 04
63 Remove the two identified fuses.
64
DANGER

Obtain a replacement alarm and control card. Make sure that the replacement
card has the same Product engineering code (PEC) and PEC suffix as the card
you remove.
297-2651-543 Standard 05.01 March 1999

Ext FSP
67
CAUTION
Loss of service
Make sure that the alarm and control card you remove
is the card that controls the PMs that you busied. Loss
of service results if you move the wrong card.
CAUTION
Loss of service
Make sure that the alarm and control card you
remove is the card that controls the PMs that you
busied. Loss of service results if you move the
wrong card.
Remove the alarm and control card.
68 Insert the replacement card.
69 Close the FSP panel.
70 Tighten the slotted nut on the FSP.
71 Insert the two fuses removed in step 63.
72 The replaced alarm and control card controls shelves. Use the following steps
to reset the converter in each shelf the card controls.
is lit step 83
is not lit step 74
GSP05 (CSP10)
Ext FSP
is lit, and more blown fuses exist step 3

is lit, and more blown fuses do not step 83
exist
is not lit step 77
75 To replace the converter, perform the correct procedure in Card replacement

is lit step 2
is not lit step 77
At the MAP terminal

>MAPCI;MTC;EXT
If an FSP alarm Do

297-2651-543 Standard 05.01 March 1999

Ext FSP
MEX MEX
frameframe
majormajor
(continued)
(end)
At the MEX frame
81
WARNING

Open the FSP panel.
82 Determine if the supply wiring for the alarm battery in the FSP is short-circuited.
GSP05 (CSP10)
Ext FSP
MS7E frame major
Alarm display
. . . . . . . . 1FSP .
M
Indication
Meaning
of frames affected.
Result
Common procedures
Action
procedure.
297-2651-543 Standard 05.01 March 1999

Ext FSP
MS7E frame major (continued)
Summary of Clearing an Ext FSP MS7E frame major alarm

the FAN FAIL procedure.
lamp is lit
Is the Y Repair cooling procedure.
FAN FAIL unit
lamp lit?
N
Is the Y Replace
CONVERTER converter
FAIL LED lit?
N
Is the Y Replace fuse End
Alarm/Battery
fuse blown?
N
Contact next
level of support
GSP05 (CSP10)
Ext FSP
Clearing an Ext FSP MS7E frame major alarm
is lit step 32
is not lit step 2
LEDs are lit.
are lit step 7

are not lit step 3
3 Determine if any of the alarm battery supply (ABS) fuses (05 to 09), on the FSP,
have blown.
If a fuse Do
has blown step 4

fuse.
297-2651-543 Standard 05.01 March 1999

Ext FSP
6
DANGER
Risk of fire
manufacturer.
DANGER
Risk of fire
manufacturer.
If the fuse Do

is ON step 9
is OFF step 8
is lit step 9
is not lit step 31
GSP05 (CSP10)
Ext FSP
9 Note the number of the shelf that contains the converter with the lit
CONVERTER FAIL LED. Note the half of the shelf (left or right) that contains
the converter with the lit CONVERTER FAIL LED.
10 Check the table that follows. Identify the circuit breaker on the FSP for the shelf
that contains the converter with the lit CONVERTER FAIL LED.
51 (left side) CD1

18 (left side) CD2
18 (right side) CD3
51 (right side) CD4
32 (left side) CD5
32 (right side) CD6
Note: Each circuit breaker associates with one half of a shelf. The preceding
table indicates if the circuit breaker associates with the left side or with the right
side.
If the fuse Do
is ON step 12
is OFF step 13
297-2651-543 Standard 05.01 March 1999

Ext FSP
12 Set the circuit breaker that you identified to OFF.
breaker to ON.
14 Release the RESET button

FAIL LED is lit
FAIL LED is not lit
FAIL LED is lit
15 Record the numbers of the frame and the shelf that contain the converter with
the lit CONVERTER FAIL LED.
At the PDC frame
16 Locate the fuse that powers the shelf in the MS7E frame.
If the fuse Do
has blown step 18

GSP05 (CSP10)
Ext FSP
19
DANGER
Risk of fire
manufacturer.
DANGER
Risk of fire
manufacturer.
Replace the cartridge fuse inside the fuse holder.
22 Locate the battery filter fuse.
If the fuse Do
has blown step 18

297-2651-543 Standard 05.01 March 1999

Ext FSP
At the MS7E frame
breaker to ON.

FAIL LED is lit
FAIL LED is not lit
FAIL LED is lit

GSP05 (CSP10)
Ext FSP
28 Examine the following table and diagram. Identify which alarm and control card
Alarm and control

Shelf number card Card position
18 and 32 right side slot CD1 (NT0X91AA) rear

18 left side and 51 slot CD2 (NT0X91AE) front
right side
32 abd 51 left side slot CD3 (NT0X91AE) front
Card
holder
NT0X91AE
card in
slot CD1
NT0X91AA
card in
slot CD2
NT0X91AE
card in
slot CD3
FSP
297-2651-543 Standard 05.01 March 1999

Ext FSP
29 Note the MSB7 number and unit number in each of the shelves controlled by
the alarm and control card that you identified.


present
present
is not lit step 34
Routine Maintenance Procedures. Complete the procedure and return to this
point.
is lit step 2
is not lit step 34
At the MAP terminal

>MAPCI;MTC;EXT
GSP05 (CSP10)
Ext FSP
(end)
If an FSP alarm Do

has the FSP alarm. Complete the procedure and return to this point.
At the MS7E frame
37
DANGER

Unscrew the NUT that has slots on the left-hand side of the FSP.
Perform this procedure if the next level of support requests this information.
41 This procedure is complete.
297-2651-543 Standard 05.01 March 1999

Ext FSP
NET0 or NET1 frame (with fuses only) major
Alarm display
. . . . . . . . 1FSP .
M
Indication
At the MTC level of the MAP display, FSP preceded by a number appears
under the EXT header of the alarm banner, and indicates an external frame
Meaning
One or more frames in the office has a power fault or a cooling unit fault.
The number of frames affected is indicated by the number under the EXT
header of the alarm banner.
Impact
The impact on subscriber service depends on the nature of the fault and the
type of frame in which the fault is located.
Common procedures
Not applicable
Action
the alarm.
GSP05 (CSP10)
Ext FSP
NET0 or NET1 frame (with fuses only) major (continued)
Summary of Clearing an Ext FSP NET0 or NET1 frame (with fuses only) major alarm

Determine if the
procedure.
FAN FAIL lamp
on the FSP is lit
Y flowchart to perform the
Is the FAN Repair cooling procedure
FAIL lamp lit? unit
N
Is a Y Replace
CONVERTER converter
FAIL LED lit?
N
and battery
fuse blown?
N
Contact next End

level of support
297-2651-543 Standard 05.01 March 1999

Ext FSP
Clearing an Ext FSP NET0 or NET1 frame (with fuses only) major alarm
At the NET0 or NET1 frame
If the FAN FAIL lamp is Do
lit step 34
not lit step 2
2 Determine if any of the CONVERTER FAIL LEDs on each converter in the

frame are lit.
If Do
any CONVERTER FAIL LEDs are lit step 7

no CONVERTER FAIL LEDs are lit step 3
3 Determine if any of the alarm battery supply (ABS) fuses (05 to 09), which are
located on the FSP, are blown.
If Do
a fuse is blown step 4

no fuses are blown step 39
fuse.
GSP05 (CSP10)
Ext FSP
6
DANGER
Risk of fire
For continued protection against risk of fire, replace
the blown fuse with a fuse of the same type, rating
(color code), and manufacturer.
If the fuse Do
blows again step 39

If the POWER switch is Do
ON step 9
OFF step 8
If the CONVERTER FAIL LED is Do
lit step 9
not lit step 33
297-2651-543 Standard 05.01 March 1999

Ext FSP
9 Use the following table to identify which fuse, located on the FSP, is associated
with the shelf with the lit CONVERTER FAIL LED.
65 01
51 02
32 03
18 04
If the fuse is Do
blown step 11
not blown step 14
fuse.
13
DANGER
Risk of fire
GSP05 (CSP10)
Ext FSP
If the fuse Do
blows, and the CONVERTER FAIL step 15

LED is lit
does not blow, and the step 33
does not blow, and the step 26
15 Records the numbers of the frame and shelf that contain the converter with the
lit CONVERTER FAIL LED.
At the PDC frame
16 Locate the fuse that powers the shelf in the NET0 or NET1 frame.
If the fuse is Do
blown step 18
not blown step 26
20
DANGER
Risk of fire
21 Install the fuse holder back onto the PDC frame.
297-2651-543 Standard 05.01 March 1999

Ext FSP
fuse.
24
DANGER
Risk of fire
lit step 26
not lit step 33
26 Replace the converter by performing the appropriate procedure in Card

Replacement Procedures. When you have completed the procedure, return to
this point.
27 Determine if the CONVERTER FAIL LED for the converter you have just
replaced is lit.
lit step 28
not lit step 33
GSP05 (CSP10)
Ext FSP
28 Determine if there are bent or short-circuited pins on the backplane of the shelf.
If there are Do
bent or short-circuited pins step 42

no bent or short-circuited pins step 29
CONVERTER FAIL LED.
297-2651-543 Standard 05.01 March 1999

Ext FSP
30 Use the following table and illustration to identify which alarm and control card
is associated with the shelf with the lit CONVERTER FAIL LED.
Alarm and control


Card
holder
NT0X91AA
card in
slot CD1
NT0X91AE
card in
slot CD2
Frame
supervisory panel
GSP05 (CSP10)
Ext FSP
31 Record the number of the network plane, as well as the number of the network
module associated with the shelves controlled by the alarm and control card
you have just identified.
32 Replace the alarm and control card by performing the appropriate procedure in
Card Replacement Procedures. When you have completed the procedure,
If the FRAME FAIL lamp is Do
lit, and there are more blown fuses step 3

lit, and there are no more blown step 42
fuses
not lit step 36
34 Repair the faulty cooling unit by performing the appropriate procedure in

Trouble Locating and Clearing Procedures. When you have completed the
procedure, return to this point.
lit step 2
not lit step 36
At the MAP terminal

36 Access the EXT level of the MAP display by typing
>MAPCI;MTC;EXT
297-2651-543 Standard 05.01 March 1999

Ext FSP
NET0NET0
or NET1 frameframe
or NET1 (with(with
fusesfuses
only)only)
majormajor
(continued)
(end)
37 Determine whether an FSP alarm is present.
If an FSP alarm is Do
present, and you have not accessed step 38

present, and you have accessed all step 42
the frames with an FSP alarm
not present step 43
38 Perform the procedure in this document that is appropriate for the type of frame
that has the FSP alarm. When you have completed the procedure, return to
this point.
39
DANGER
Unscrew the slotted nut on the left-hand side of the FSP.
The personnel at the next level of support may request this information.
42 For further assistance, contact the personnel responsible for the next level of
support.
GSP05 (CSP10)
Ext FSP
NET0 or NET1 frame (circuit breakers and fuses) major
Alarm display
. . . . . . . . 1FSP .
M
Indication
Meaning
One or more frames in the office have a power fault or a cooling unit fault.
of frames affected.
Result
cabinet that contains the fault.
Common procedures
Action
procedure.
297-2651-543 Standard 05.01 March 1999

Ext FSP
NET0 or NET1 frame (circuit breakers and fuses) major (continued)
Summary of Clearing an Ext FSP NET0 or NET1 frame (circuit breakers and fuses) major alarm

on the FSP is lit
Repair cooling procedure.
Is the FAN Y
FAIL lamp lit? unit
Is a Replace
Y
CONVERTER converter
FAIL LED lit?
N
Is an alarm Replace fuse

Y
and battery
fuse blown?
N

level of support
GSP05 (CSP10)
Ext FSP
Clearing an Ext FSP NET0 or NET1 frame (circuit breakers and fuses) major
alarm
is lit step 33
is not lit step 2
are lit.
are lit step 7

are not lit step 3
3 Check the alarm battery supply (ABS) fuses (01 to 05) on the FSP. Determine
if any ABS fuses are blown.
Is a fuse Do
is blown step 4
fuse.
297-2651-543 Standard 05.01 March 1999

Ext FSP
6
DANGER
Risk of fire
with the same type, rating (color code), and
manufacturer.
DANGER
Risk of fire
with the same type, rating (color code), and
manufacturer.
If the fuse Do
is blown again step 38

is not blown again step 32
is ON step 9
is OFF step 8
is lit step 9
is not lit step 32
GSP05 (CSP10)
Ext FSP
CONVERTER FAIL LED.
10 Refer to the following table. Identify the circuit breaker located on the FSP that
65 CB1
32 CB2
51 CB4
18 CB5
is ON step 12
is OFF step 13
12 Set the circuit breaker you identified to OFF.
13 Press and hold the RESET button on the converter. Set the circuit breaker to
ON.

FAIL LED is lit
FAIL LED is not lit
FAIL LED is lit
CONVERTER FAIL LED.
297-2651-543 Standard 05.01 March 1999

Ext FSP
At the PDC frame
16 Locate the fuse that powers the shelf in the NET0 or NET1 frame.
If the fuse Do
is blown step 18
20
DANGER
Risk of fire
manufacturer.
DANGER
Risk of fire
manufacturer.

ON.
GSP05 (CSP10)
Ext FSP

FAIL LED is lit
FAIL LED is not lit
FAIL LED is lit

26 Determine if the CONVERTER FAIL LED for the converter that you replaced is
lit.
is lit step 27
is not lit step 32

shelf.
are present step 41

CONVERTER FAIL LED.
297-2651-543 Standard 05.01 March 1999

Ext FSP
29 Refer to the following table and diagram. Identify the alarm and control card
that associates with the shelf with the lit CONVERTER FAIL LED:

Card
holder
NT0X91AA
card in
slot CD1
NT0X91AE
card in
slot CD2
Frame
supervisory panel
GSP05 (CSP10)
Ext FSP
30 Record the numbers of the network plane and the network module for the
shelves controlled by the alarm and control card. You identified the alarm and
control card in the last step.

present
present
is not lit step 35
to this point.
is lit step 2
is not lit step 35
At the MAP terminal

>MAPCI;MTC;EXT
297-2651-543 Standard 05.01 March 1999

Ext FSP
NET0NET0
or NET1 frameframe
or NET1 (circuit breakers
(circuit and fuses)
breakers majormajor
and fuses) (continued)
(end)
If an FSP alarm Do

38
DANGER
potential of -48V dc to -60V dc. Do not touch any

Unscrew the slotted nut on the left side of the FSP.
GSP05 (CSP10)
Ext FSP
NETC frame major
Alarm display
. . . . . . . . 1FSP .
M
Indication
Meaning
One or more frames in the office have a power fault or a cooling unit fault.
of frames affected.
Result
Common procedures
Action
procedure.
297-2651-543 Standard 05.01 March 1999

Ext FSP
NETC frame major (continued)
Summary of Clearing an Ext FSP NETC frame major alarm

Determine if the
procedure.
FAN FAIL lamp
on the FSP is lit
procedure
Is the FAN Y Repair cooling
FAIL lamp lit? unit
Is a Replace
Y
CONVERTER converter
FAIL LED lit?
N
Is an alarm Replace fuse

Y
and battery
fuse blown?
N
Contact next End

level of support
GSP05 (CSP10)
Ext FSP
Clearing an Ext FSP NETC frame major alarm
At the NETC frame
is lit step 33
is not lit step 2
LEDs are lit.
If any CONVERTER FAIL LEDs Do
are lit step 7

are not step 3
3 Check the alarm battery supply (ABS) fuses (01 to 05) on the FSP. Determine
if any of the ABS fuses are blown.
If any fuses Do
are blown step 4

are not blown step 38
fuse.
297-2651-543 Standard 05.01 March 1999

Ext FSP
6
DANGER
Risk of fire
manufacturer.
DANGER
Risk of fire
manufacturer.
If the fuse Do
is blown again step 38

is not blown again step 32
is ON step 9
is OFF step 8
is lit step 9
is not lit step 32
GSP05 (CSP10)
Ext FSP
CONVERTER FAIL LED.
10 Refer to the following table. Identify the circuit breaker on the FSP that
65 CB1
32 CB2
51 CB4
18 CB5
is ON step 12
is OFF step 13
breaker to ON.

FAIL LED is lit
FAIL LED is not lit
FAIL LED is lit
15 Record the number of the frame and shelf that contain the converter with the lit
CONVERTER FAIL LED.
297-2651-543 Standard 05.01 March 1999

Ext FSP
At the PDC frame
16 Locate the fuse that powers the shelf in the NETC frame.
If the fuse Do
is blown step 18
20
DANGER
Risk of fire
To protect against risk of fire, make sure you replace
DANGER
Risk of fire
To protect against risk of fire, make sure you replace

At the NETC frame
ON.
GSP05 (CSP10)
Ext FSP

FAIL LED is lit
FAIL LED is not lit
FAIL LED is lit

26 Determine if the CONVERTER FAIL LED for the converter that you replaced is
lit.
is lit step 27
is not lit step 32

shelf.
If short–circuited or bent pins Do
are present step 41

CONVERTER FAIL LED.
297-2651-543 Standard 05.01 March 1999

Ext FSP
29 Refer to the following table and diagram. Identify the alarm and control card
that associates with the shelf with the lit CONVERTER FAIL LED.
Alarm and control


Card
holder
NT0X91AA
card in
slot CD1
NT0X91AE
card in
slot CD2
Frame
supervisory panel
GSP05 (CSP10)
Ext FSP
30 Record the numbers of the network plane and network module number for the
shelves controlled by the alarm and control card. You identified the alarm and
control card in the previous step.

present
present
is not lit step 35
to this point.
is lit step 2
is not lit step 35
At the MAP terminal

>MAPCI;MTC;EXT
297-2651-543 Standard 05.01 March 1999

Ext FSP
NETCNETC
frameframe
majormajor
(continued)
(end)
If an FSP alarm Do

At the NETC frame
38
DANGER

Unscrew the slotted nut on the left side of the FSP.
GSP05 (CSP10)
Ext FSP
PDC frame major
Alarm display
. . . . . . . . nFSP .
M
Indication
Meaning
A power fault or a cooling unit fault is present on one or more office frames.
of affected frames.
Result
The impact on subscriber service depends on the type of fault. Subscriber
service impact also depends on the type of frame of the fault.
Common procedures
Action
procedure.
297-2651-543 Standard 05.01 March 1999

Ext FSP
PDC frame major (continued)
Summary of Clearing an Ext FSP PDC frame major alarm

procedure.

Are any FA
lamps lit?
procedure.
Is a lit FA Y Replace fuse

lamp present?
Is a lit FA A Obtain capacitor

Y Replace fuse
or FA B lamp forming tool
present?
N
Is an alarm
Y Replace fuse
and battery
supply fuse
blown?
N
End
Contact next
level of support
GSP05 (CSP10)
Ext FSP
Clearing an Ext FSP PDC frame major alarm
At the PDC frame
1 The FA lamps are on the left side of each distribution panel. Determine if any
FA lamps are lit.
If an FA lamp Do
is lit step 2
is not lit step 3
2 The fuses are on the distribution panel. Note any blown fuses that associate
with the lit FA lamp.
If a fuse Do
has blown step 25

3 The FA A and FA B lamps are on the filter panel at the bottom of the frame.
Determine if either of the FA A and FA B lamps are lit.
If Do
the FA A or FA B lamp is lit step 5

neither the FA A nor the FA B lamp step 4
is lit
4 Alarm battery supply (ABS) fuses are on the FSP. Note any blown ABS fuses.
If a fuse Do
has blown step 47

5 Remove the fuse holder nearest the lit lamp (FA A or FA B).
fuse.
297-2651-543 Standard 05.01 March 1999

Ext FSP
7 Replace the cartridge fuse that is inside the fuse holder.
8 Replace the guard fuse that is on the fuse holder.

Note: A capacitor forming tool consists of a 100-W 120-V light bulb that screws
into a socket without insulation-ended twisted wires. The without
insulation-ended twisted wires must have spring-type alligator clips on each
end. You can insert a new tool with the tool number T000655, CPC number
10 Connect the leads of the capacitor forming tool across the connectors in the
fuse holder slot to charge the capacitors.
is lit, and you did not replace the step 11

capacitor
is lit, and you replaced the capacitor step 56
is not lit step 19
11 Remove the fuse that powers the capacitor.
12 Obtain a voltmeter.
At the back of the PDC frame
13 Use the voltmeter to make sure that no voltage is present across the terminals
of the capacitors. Use the voltmeter to make sure that no voltage is present
between either terminal of the capacitor and the battery return.
GSP05 (CSP10)
Ext FSP
14
DANGER

Label the leads that go to the positive terminal of the capacitor as + and the
negative terminal as –.
15 Disconnect the leads from the short–circuited capacitor.
17 Install the replacement capacitor.
18 Connect the lead with the label + to the positive terminal of the capacitor.
Connect the lead with the label – to the negative terminal of the capacitor. Go
to step 10.
At the PDC frame
19 Remove the capacitor forming tool and immediately insert the fuse holder back
into the PDC frame.
20 The FA A and FA B lamps are on the filter panel at the bottom of the frame.
Determine if any FA A or FA B lamps are lit.
If Do
the lamp that was lit in the step 56

beginning, remains lit
neither lamp is lit step 50
21 For each fuse on the distribution panel, record the number of the frame and
shelf that associates with the frame.
297-2651-543 Standard 05.01 March 1999

Ext FSP
22 Go to the next frame that you recorded in step 21.

At the recorded frame
is lit step 25
is lit, and the frame is an LCE step 24
is not lit, and the frame is not an step 22
LCE
24 Press the indicator on the A –48V talk battery QFF fuse. Press the indicator on
the B –48V talk battery QFF fuse.
Note: These fuses are above the LCE shelf.
is lit, and you checked each frame step 56

is lit, and you did not check each step 22
frame
is not lit step 25
At the PDC frame

25 Determine if the blown fuse supplies –48V Talk Battery to an LCE frame.
Note: The information is on the label under the blown fuse.
If the fuse Do
supplies –48V talk battery to an step 26

LCE frame
does not supply –48V talk battery to step 42
an LCE frame
fuse.
GSP05 (CSP10)
Ext FSP

Note: Do not insert the fuse holder back into the PDC frame.

At the LCE frame
30 Remove the ten –48V talk battery fuses that are above the shelves. Talk
battery A powers the first and third shelves from the bottom of the LCE. Talk
battery B powers the second and fourth shelves.

Note: A capacitor forming tool consists of a 100-W 120-V light bulb that screws
into a socket without insulation–ended twisted wires. You can insert a new tool
with the tool number T000655 and CPC number NTA0600512. Insert the new
tool into the fuse holder instead of the light bulb. You can insert the new tool in
the same method that you insert a fuse.
297-2651-543 Standard 05.01 March 1999

Ext FSP
32
DANGER
High voltages are present at the contacts for the fuse
holder on the faceplate of the filter panel. Do not let
the probes of the capacitor forming tool touch the
faceplate of the filter panel. Do not let the probes of
the capacitor forming tool touch together.

High voltages are present at the contacts for the fuse
holder on the faceplate of the filter panel. Do not let
the probes of the capacitor forming tool touch the
faceplate of the filter panel. Do not let the probes of
the capacitor forming tool touch together.
Connect the leads of the capacitor forming tool across the connectors in the
fuse holder slot to charge the capacitors.
is lit, and you have not replaced the step 33

capacitor
is lit, and you replaced the capacitor step 56
is not lit step 38
At the LCE frame from which you just removed the fuses
33 Label the leads that go to the positive terminal of the capacitor as + and the
negative terminal as –.
34 Disconnect the leads from the short–circuited capacitor.
GSP05 (CSP10)
Ext FSP
37 Connect the lead with the label + to the positive terminal of the capacitor.
Connect the lead with the label – to the negative terminal of the capacitor. Go
to step 32.
At the PDC frame
38 Remove the capacitor forming tool and immediately insert the fuse holder back
into the PDC frame.
At the LCE frame from which you just removed the fuses
39 Insert the ten –48V talk battery fuses that you removed in step 30. Insert each
fuse one at a time. Pause between each fuse.
At the PDC frame
40 Determine if any of the fuses that you replaced are blown fuses.
If any fuses Do
have blown step 56

have not blown step 41
At the LCE frame from which you just replaced the fuses
41 Press the indicator on one of the –48V QFF fuses for the talk battery that you
replaced. Use this procedure to determine if the talk battery is present.
is lit step 51
is not lit step 56
At the PDC frame

fuse.
297-2651-543 Standard 05.01 March 1999

Ext FSP
If the fuse Do
has blown step 56

47 Obtain a replacement fuse that has the same voltage and amperage as the
blown fuse.
If the fuse Do

is lit step 1
is not lit step 51

>MAPCI;MTC;EXT
GSP05 (CSP10)
Ext FSP
(end)
If an FSP alarm Do

is not present, and you accessed all step 56
has the FSP alarm. When the procedure is complete, return to this point.
At the PDC frame
54
DANGER

Open the FSP panel.
55 Determine if the supply wiring for the alarm battery inside the FSP is short–
circuited. The next level of support can request this information.
297-2651-543 Standard 05.01 March 1999

Ext E911_PSAP_OFFHK
minor
Alarm display
. . . . . . . . 1Min .
Indication
1Min can indicate an E911_PSAP_OFFHK alarm. The E911 permanent
lockout (PLO) or off-hook minor alarm appears under the EXT heading for
SuperNode and NT40 applications.
Meaning
This alarm indicates one of the following conditions:
• A public safety answering point (PSAP) operator was off-hook after call
disconnect.
• A PSAP operator was off-hook without a connection to another party for
an extended period of time. The off-hook time exceeded an office
parameter (E911_PSAP_OFFHK_ALARM_TIME) setting.
• Equipment failures occur. The equipment failures imitate a PSAP
off–hook state.
Result
The PSAP operator cannot answer emergency calls that enter on a line. If
the originator hold (ORIGHOLD ) is set to Y (Yes), the originator can block
network resources. If an ORIGHOLD is set to Y, the caller cannot place
other calls.
Common procedures
Action
procedure.
GSP05 (CSP10)
Ext E911_PSAP_OFFHK
minor (continued)
Summary of How to clear an Ext E911_PSAP_OFFHK minor alarm
Access EXT level This flowchart summarizes the

at MAP to silence procedure.
EXT alarm
List minor alarm procedure.
Locate E911204 log

report associated
with this alarm
Contact operator
position listed in
E911204 log report
If ORIGHOLD in table
Notify PSAP TRKGRP or VIRTGRPS is
Is the operator Y on, review office parm
operator the
off-hook? position is off-hook setting for
E911_PSAP_DISCONNECT
N TIME
Access LTP
level of the MAP
End
Post line and LDT or LDT

determine line Line/ACD PSAP? 1
status
Line/ACD
297-2651-543 Standard 05.01 March 1999

Ext E911_PSAP_OFFHK
minor (continued)
Summary of How to clear an Ext E911_PSAP_OFFHK minor alarm (continued)
If ORIGHOLD in table TRKGRP or

Is line status IDL VIRTGRPS is on, review office
PLO/CPB or parm setting for
IDL? E911_PSAP_DISCONNECT TIME
PLO or CPB
Perform SMU, DS-1

carrier, or PSAP End
CPE maintenance
Is line status IDL If ORIGHOLD in table

PLO/CPB or VIRTGRPS is on,
IDL? review office parm
setting
PLO or CPB
Perform line and Alarm does not

PM maintenance clear automatically.
Go to MAP and type
CLEAR.
Alarm cleared? N Contact next

level of support
End
GSP05 (CSP10)
Ext E911_PSAP_OFFHK
minor (continued)
How to clear an Ext E911_PSAP_OFFHK minor alarm
At the MAP display
1 You enter this procedure from a step in a procedure to clear system-level
alarms that identifies EXT alarms at the MAP display. The alarm activates for
time on office parameter E911_PSAP_OFFHK_ALARM_TIME.
2 To access EXT level, type

>MAPCI;MTC;EXT
0 0 0 1 11
3 To display all the EXT minor alarms, type

>LIST MIN
E911_PSAP_OFFHK
4 Obtain E911204 to get the directory number (DN) and line equipment number
(LEN) of the operator with the off-hook line. See Input/Output System
Reference Manual, 297-1001-129, to use LOGUTIL and collect this information.
To access LOGUTIL, type
>LOGUTIL
5 To open the buffer for the E911 log report, type

>OPEN E911
297-2651-543 Standard 05.01 March 1999

Ext E911_PSAP_OFFHK
minor (continued)
6 Browse through the buffer to locate the E911204 log report. To access the
previous report, type
>BACK
Repeat the command to display the E911204 log report.
E911204 FEB03 13:05:24 0101 INFO
PERMANENT off–hook CONDITION AT PSAP
LINE EQUIPMENT NUMBER: HOST 0 0 19 06
DN: 6211234
PSAP NAME: RALPOLICE
The last generated E911 log report prints on the MAP screen.
7 Exit LOGUTIL, type

>QUIT
8 Contact PSAP operator to determine if the operator console is off–hook.
If PSAP console Do
is off-hook Tell the PSAP operator to go

on–hook. ORIGHOLD, in table
TRKGRP or VIRTGRPS, can be Y
for the end office where the call
routed. If ORIGHOLD is Y, check
E911_PSAP_DISCONNECT_TIME.
See Office Parameters Reference
Manual. If ORIGHOLD is N, you do
not need more maintenance. Go to
step 12. Originator hold and
ringback are available for local
access 911 calls routed through
virtual facility groups with BCS34.
is on-hook Note the DN/LEN of the operator
with the off–hook line. See the
E911204 log report. Go to the next
step.
GSP05 (CSP10)
Ext E911_PSAP_OFFHK
minor (continued)
9 To access the LTP level of the MAP display from the MTC level of the MAP
display, type
>LNS;LTP;POST L len
where
LEN is the line equipment number listed in the E911204 log
Normal response on the MAP display:
LCC PTY RNG ....LEN.DN STA F S LTA TE RESULT IBN
PSAP 00 0 00 04 621 6004 PLO
Perform maintenance tasks if these events happen:
If the status of the posted line Do
is PLO or CPB and the PSAP is a Perform line and peripheral module
Line/ACD PSAP maintenance. See this document.
Verify the alarm cleared.
is PLO or CPB and the PSAP is an Perform SMU, DS-1 carrier. If
LDT PSAP necessary, perform PSAP CPE
maintenance. Refer to Advanced
Maintenance Guide for DS–1 carrier
information. Refer to this document
for SMU maintenance information.
Verify the alarm cleared.
is IDL If ORIGHOLD is Y for the end office
where the call routed, check the
E911_PSAP_DISCONNECT_TIME
parameter. See Office Parameters
Reference Manual for information.
If the ORIGHOLD is N, you do not
need to take additional action. Go to
step 12. An intermittent fault can be
the cause the alarm. Monitor for
E911204 log reports. Return to this
procedure if the alarm occurs again.

>CLEAR
297-2651-543 Standard 05.01 March 1999

Ext E911_PSAP_OFFHK
minor
minor
(continued)
(end)
11 Check to see if alarm persists.
If alarm Do
clears step 13
12 Refer to the next level of control.
GSP05 (CSP10)
Ext E911_RCER_MAJOR
major
Alarm display
. . . . . . . . 1Maj .
M
Indication
Under the EXT subsystem header at the MTC level of the MAP, 1Maj can
indicate an E911_RCER_MAJOR alarm. The additional feature for RCERs
must exist for the 1Maj to indicate an E911_RCER_MAJOR alarm. The
major alarm for the E911 recent call event record (RCER) appears under the
EXT heading for SuperNode and NT40 applications.
Meaning
An E911_RCER_MAJOR alarm means the multiprotocol controller (MPC)
links to a remote location failed. Records of calls to an exact public safety
answering point (PSAP) print at the remote location. This failure does not
affect records like events, logs, and calls generated at the E911 tandem
location.
Result
Line or automatic call distribution PSAP operators cannot access a printed
record or information about calls at the location.
Common procedures
Action
procedure. Note that these procedures are the same as the procedures
identified for the major alarm for the E911 automatic location identification.
Both procedures deal with the MPC links.
297-2651-543 Standard 05.01 March 1999

Ext E911_RCER_MAJOR
major (continued)
Summary of Clearing an Ext E911_RCER_MAJOR major alarm
Silence the This flowchart summarizes the

EXT alarm procedure.

Access EXT procedure.
level at MAP
List major alarms
Check MPC
and E911 logs
for link failures
Post the damaged

MPC

Contact next N Y End

level of support Alarm cleared?
GSP05 (CSP10)
Ext E911_RCER_MAJOR
major (continued)
Clearing an Ext E911_RCER_MAJOR major alarm
At the MAP display
alarms that identified an EXT major alarm.

>MAPCI:MTC:SIL
3 To access the EXT level of the MAP, type

>EXT
0 0 1 0 14

>LIST MAJ
If response on MAP display Do
is E911_RCER_MAJOR step 6
5 Go to the procedures listed in the table of contents for references to other

alarms.
6 Obtain MPC908 and any E911211 log reports. To access LOGUTIL, type
>LOGUTIL

>OPEN MPC908
297-2651-543 Standard 05.01 March 1999

Ext E911_RCER_MAJOR
major (continued)
8 To browse through the buffer and display the MPC908 log report, type
>BACK
SysB state.
System Action Taken
9 An E911218 log report generates for each call to the PSAP with lost RCER
information. The log report generates while one or more links are down.
Repeat steps 6, 7, and 8 to open the E911 buffer and to browse for this report.
For step 7 only, type
>OPEN E911218
E911218 MAR26 08:15:38 0101 RCER WAS NOT SENT
REASON: No Links Up
1990/03/26 9196211235 MADISONPOLICE1234 15:10:00 15:10:02
15:10:17 15:10:25 9199211901 MADISONFIRE 15:10:19

>QUIT
11 The MPC908 log report lists the MPC number. Note the MPC number. You
can check the first entries for the MPC. Check office records to determine the
MPC that has an RCER.

>MAPCI;MTC
GSP05 (CSP10)
Ext E911_RCER_MAJOR
major (continued)
(end)
13 To display MPC card status, type

where
Note: You do not need to know the number of the IOC that contains the card to
display the MPC link. IOC port information for IOC1 appears when the system
shows link status for the MPC card. The MPC card is on the same IOC shelf or
another IOC shelf.
IOC CARD 0 1 2 3 4 5 6 7 8
1 PORT 0123 0123 0123 0123 0123 0123 0123 0123 0123
STAT .... .––– .––– .––– .––– .... .... .... ....
Card 3 Unit 17
MPC 17 IS ON IOC 3
If the links Do

are SysB step 15
15 Perform MPC card maintenance. Refer to this document. Complete MPC card
maintenance and verify that the E911_RCER_MAJOR alarm cleared. If the
alarm persists, contact the next level of support.
297-2651-543 Standard 05.01 March 1999

Ext E911_RCER_MINOR
minor
Alarm display
. . . . . . . . 1Min .
Indication
1Min can indicate a possible E911_RCER_MINOR alarm. The additional
feature for RCERs must be available for the 1Min to indicate the alarm. The
E911 recent call event record (RCER) minor alarm appears under the EXT
heading for both SuperNode and NT40 applications.
Meaning
An E911_RCER_MINOR alarm means a multiprotocol controller (MPC)
link to a remote location failed. Records of calls to E911 print at the remote
location.
Result
A link that sends information for call event records does not operate if the
E911_RCER_MINOR alarm activates.
Common procedures
Action
procedure.
GSP05 (CSP10)
Ext E911_RCER_MINOR
minor (continued)
Summary of Clearing an Ext E911_RCER_MINOR minor alarm
Silence EXT This flowchart summarizes the

alarm procedure.

procedure.
Access EXT
level at MAP
List minor alarms
Check MPC
and E911 logs
for link failures
Post the MPC

Contact next Y End

N
level of support Alarm cleared?
297-2651-543 Standard 05.01 March 1999

Ext E911_RCER_MINOR
minor (continued)
Clearing an Ext E911_RCER_MINOR minor alarm
At the MAP display

>MAPCI:MTC:SIL

>EXT
0 0 1 0 14
4 To display the EXT major alarms, type

>LIST MIN
is E911_RCER_MINOR step 6
5 Go to the procedures in the table of contents for references to other alarms.
6 Obtain MPC908 and E911211 log reports. To access LOGUTIL, type

>LOGUTIL

>OPEN MPC908
GSP05 (CSP10)
Ext E911_RCER_MINOR
minor (continued)
8 To browse through the buffer and display the MPC908 log report, type
>BACK
SysB state.
System Action Taken
9 An E911218 log report generates for each call to the PSAP with lost RCER
information. The log report generates while one or more links are down.
Repeat steps 6, 7, and 8 to open the E911 buffer and to browse for this report.
For step 7 only, type
>OPEN E911218
Example of E911218 log report:
E911218 MAR26 08:15:38 0101 RCER WAS NOT SENT
REASON: No Links Up
1990/03/26 9196211235 MADISONPOLICE 1234 15:10:00
15:10:02
15:10:17 15:10:25 9199211901 MADISONFIRE 15:10:19

>QUIT
11 The MPC908 log report lists the MPC number. Note the MPC number. You
can check the first entries for the MPC. Check office records to determine the
RCERs assigned to the MPC.

>MATCI;MTC
297-2651-543 Standard 05.01 March 1999

Ext E911_RCER_MINOR
minor
minor
(continued)
(end)
13 To display the MPC card status, type

where
Note: You do not need to know the number of the IOC port that holds the card
to display MPC link status. IOC port information for IOC 1 appears when the
system shows link status for the MPC card. The MPC card is on the same IOC
shelf or another IOC shelf.
IOC CARD 0 1 2 3 4 5 6 7 8
1 PORT 0123 0123 0123 0123 0123 0123 0123 0123 0123
STAT .... .––– ––– ––– .––– .... .... .... ....
TYPE CONS MPC MPC MPC MPC Card 3 Unit 17
MPC 17 IS ON IOC 3
Refer to the following table. The next step depends on if card links are system
busy.
If card links Do

are SysB step 15
15 Perform MPC card maintenance. Refer to this document. Complete MPC card
maintenance and verify that the E911_RCER_MAJOR alarm cleared. If the
alarm persists, contact the next level of support.
GSP05 (CSP10)
4-324 4-324
Ext FSP
RLCE frame major
Alarm display
. . . . . . . . 1FSP .
M
Indication
At the MTC level of the MAP display, FSP preceded by a number appears
under the Ext header of the alarm banner, and indicates an external frame
Meaning
One or more frames in the office has a power fault or a cooling unit fault.
The number that precedes FSP is the number of frames with an FSP alarm.
Impact
The impact on subscriber service depends on the nature of the fault and the
type of frame in which the fault is located.
Common procedures
None
Action
The following flowchart is a summary of this procedure. Use the
instructions in the step-action table that follows the flowchart to perform the
procedure.
Note: This procedure applies to a remote line concentrating equipment

(RLCE) frame.
297-2651-543 Standard 05.01 March 1999

4-325
Ext FSP
RLCE frame major (continued)
Summary of clearing a/an Ext FSP alarm

Check all procedure.
CONVERTER
FAIL LEDs
Is a Y Replace procedure.
CONVERTER converter
FAIL LED lit?
N
Is an RG FAIL Y Replace ringing
LED lit? generator
Is a line Y Replace fuse

drawer fuse
blown?

and battery
fuse blown?
N
Contact next End
level of support
GSP05 (CSP10)
4-326
Ext FSP
Clearing a/an Ext FSP alarm
At the RLCE frame
1 Check the CONVERTER FAIL LED on each converter in the frame.
If Do
any CONVERTER FAIL LED step 52

no CONVERTER FAIL LED step 2
2 Check the ringing generator (RG) FAIL LED on both RGs, which are located at
the top of the frame.
Note: The FAIL LED is located behind the front panel of the RG.
If Do
any FAIL LEDs are lit step 39

no FAIL LEDs are lit step 3
3 Check the line drawer fuses (01 to 15, and RA and RB), which are located on
the fuse panel above each unit in the frame.
If Do
la fuse is blown step 8

4 Check the alarm battery supply (ABS) fuses (01 to 08), which are located on
the FSP.
If Do
a fuse is blown step 5

5 Obtain a replacement fuse wit the same voltage and amperage as the blown
fuse.
297-2651-543 Standard 05.01 March 1999

4-327
Ext FSP
7
DANGER
Risk of fire
blown fuse with a fuse of the same type, rating (color
code), and manufacturer.
If the fuse Do
blows again step 102

8 Determine which fuse is blown.

Note: Fuses 01 to 05 each supply +5 V, fuses 06 to 10 each supply +15V, and
fuses 11 to 15 each supply –48V.
If the blown fuse is any one of Do
01 to 05 step 13
06 to 15 step 9
RA to RB step 13
9 Use the following table to determine which +15V fuse (06 through 10) is
associated with which –48V fuse (11 through 15).
I–48V fuse number +15V fuse number
11 06
12 07
13 08
14 09
15 10
GSP05 (CSP10)
4-328
Ext FSP
10 Remove the blown fuse and its associated fuse. For example, if the blown fuse
is 06, then remove fuse 11 as well.
fuse.
12 Insert the –48V fuse, then the +15 fuse.
If the fuse Do
blows again step 16

fuse.
15
DANGER
Risk of fire
Insert the replacement fuse
If the fuse Do
blows again step 18

fuse.
297-2651-543 Standard 05.01 March 1999

4-329
Ext FSP
18 Use the following table to determine which drawer in the shelf below the fuse
panel is associated with the blown fuse.
Fuse number Drawer number
01, 06, 11 1 (leftmost)

02, 07, 12 2,
03, 08, 13 3
04, 09, 14 4
05, 10, 15 5
Note: The RA and RB fuses supply ringing voltage to all five drawers in the
shelf.
19 Pull out the line drawer you have just identified.

Note: When dealing with a blown RA or RB fuse, begin with the leftmost
drawer.
20
DANGER
Personal injury
Do not touch the line feed resistors on the line cards.
The line feed resistors generate enough heat to burn
you.
CAUTION
Loss of service
Carry out this procedure during periods of low traffic.
Unseat all the line cards in the drawer.
GSP05 (CSP10)
4-330
Ext FSP
Note: Just unseat the line cards; do not remove them from the drawer.
If you are dealing with Do
any one of fuses 01 to 05 step 22

any RA or RB fuse step 22
If the fuse Do
blows again step 25

fuse.
24
DANGER
Personal injury
you.
Insert the replacement fuse
If the fuse Do
blows again step 25

297-2651-543 Standard 05.01 March 1999

4-331
Ext FSP
25 Check the drawer for loose or short-circuited wires.
If there are Do
loose or short-circuited wires step 105

no loose or short-circuited wires, step 26
and the fuse you are dealing with is
a ringing voltage fuse (RA or RB)
and you have not done all five
drawers in the shelf.
no loose or short-circuited wires, the step 105
fuse you are dealing with is a
ringing voltage fuse (RA or RB) and
you have done all five drawers in
the shelf.
no loose or short-circuited wires, step 105
and the fuse you are dealing with is
one of the line drawer fuses (01 to
15)
26 Reseat all the line cards in the drawer and repeat steps 19 and 20 for the next
drawer.
27 Reseat the line cards one at a time, and check the fuse after reseating each
line card.
If after reseating Do
a line card, the fuse blows again step 28

all the line cards, the fuse does not step 98
blow
28
DANGER
Personal injury
you.
Remove the line card from the drawer
GSP05 (CSP10)
4-332
Ext FSP
29 Obtain a replacement line card. Ensure that the replacement card has the
same product engineering code (PEC), including the suffix, as the card being
removed.
30 Insert the replacement line card into the drawer
If you are dealing with Do

any RA or RB fuse step 34
fuse.
If the fuse Do

fuse.
36
DANGER
Risk of fire
297-2651-543 Standard 05.01 March 1999

4-333
Ext FSP
If the fuse Do

37 Reseat all the other line cards in the drawer.
38 Push the drawer back in, and go to step 98.
39 Use the following table to identify which circuit breaker located on the FSP is
associated with RG that has a lit FAIL LED.
RG number Circuit breaker number
RG0 (leftmost) CB5

RG1 CB6
40 Check the associated circuit breaker
If the circuit breaker is Do
lON step 49
OFF step 41
41 Set the circuit breaker to ON
turns OFF and the FAIL LED on the step 42

RG is lit
remains ON and the FAIL LED on step 98
the RG is not lit
remains ON and the FAIL LED on step 49
the RG is lit
GSP05 (CSP10)
4-334
Ext FSP
At the power distribution center (PDC) frame
42 Locate the fuse that powers the RG in the RLCM frame.
If the fuse is Do
blown step 43
not blown step 47
45
DANGER
Risk of fire
47 Locate battery filter fuses.
If the fuse is Do
blown (protruding) step 43

not blown step 50
297-2651-543 Standard 05.01 March 1999

4-335
Ext FSP
At the RLCE frame
turns OFF and the RG FAIL LED is step 50

lit.
remains ON and the RG FAIL LED step 98
is not lit
is lit
50 Perform the appropriate procedure in Lines, Trunks, and Peripherals Card

Replacement Procedures to replace the RG. When you have completed the
51 Check the RG FAIL LED for the RG you have just replaced.
If the RG FAIL LED is Do
lit step 105

not lit step 98
52 Determine which power converter has a lit CONVERTER FAIL LED.
If the converter is Do
an NT6X53 step 53
not an NT6X53 step 56
GSP05 (CSP10)
4-336
Ext FSP
53 Use the following table to identify whch circuit breaker located on the FSP is
associated with the shelf with the lit CONVERTER FAIL LED.
04 CB6
18 CB7
If the circuit breaker is Circuit breaker number
ON step 73
OFF step 55
55 Set the circuit breaker you have just identified to ON.
turns OFF and the RG FAIL LED is step 63

lit.
is lit
is not lit
56 Check the POWER switch on the converter.
If the POWER switch is Do
ON step 58
OFF step 57
297-2651-543 Standard 05.01 March 1999

4-337
Ext FSP
57 Set the POWER switch on the converter to ON
lit step 58
not lit step 98
58 Use the following table to identify whch circuit breaker located on the FSP is
associated with the shelf with the lit CONVERTER FAIL LED.
32 (NT2X70 in slot 22) CB1

32 (NT2X70 in slot 25) CB4
51 CB5
If the circuit breaker is Circuit breaker number
ON step 60
OFF step 61
60 Set the circuit breaker you have just identified to OFF.
61 Press and hold the RESET button on the converter while setting the circuit
breaker to ON.
GSP05 (CSP10)
4-338
Ext FSP
If the circuit breaker Circuit breaker number

turns OFF and the CONVERTER step 63
FAIL LED is lit
remains on and the CONVERTER step 98
FAIL LED is not lit
remains on and the CONVERTER step 73
FAIL LED is lit
63 Record the numbers of the frame and shelf with the lit CONVERTER FAIL LED.
At the power distribution center (PDC) frame

64 Locate the fuse that powers the shelf in the RLCE frame.
If the fuse is Circuit breaker number

blown step 65
not blown step 74
67
DANGER
Risk of fire
297-2651-543 Standard 05.01 March 1999

4-339
Ext FSP
At the RLCE frame
69 Proceed as follows depending on which converter had a lit CONVERTER FAIL
LED.
If the converter is Do
an NT6X53 step 72
70 Press and hold the RESET button on the converter while setting the circuit
breaker to ON.

FAIL LED is lit
FAIL LED is not lit
FAIL LED is lit

FAIL LED is lit
FAIL LED is not lit
FAIL LED is lit

Replacement Procedures to replace the converter. When you have completed
the procedure, return to this point.
GSP05 (CSP10)
4-340
Ext FSP
75 Proceed as follows depending on the converter you have just replaced.
If the converter you have just

replaced is Do
an NT6X53 step 77
76 Check the CONVERTER FAIL LED for the converter you have just replaced.
lit step 93
not lit step 98
77 Check the converter you have just replaced, as well as the associated circuit
breaker.

FAIL LED is lit
FAIL LED is not lit
FAIL LED is lit
79 Remove the NT6X51 and NT6X52 cards from the shelf with the lit
CONVERTER FAIL LED.

lit step 93
not lit step 81
297-2651-543 Standard 05.01 March 1999

4-341
Ext FSP
82 Inserr the NT6X51 card back into the shelf.

FAIL LED is lit
FAIL LED is not lit
FAIL LED is lit

Replacement Procedures to replace the NT6X51 card. When you have
completed the procedure, return to this point.

FAIL LED is lit
FAIL LED is not lit
FAIL LED is lit
88 Insert the NT6X52 card back into the shelf.
GSP05 (CSP10)
4-342
Ext FSP

FAIL LED is lit
FAIL LED is not lit
FAIL LED is lit

Replacement Procedures to replace the NT6X52 card. When you have
completed the procedure, return to this point.
lit step 95
not lit step 98
93 Determine if there are bent or short-circuited pins on the backplane of the shelf
If there are Do
bent or short-circuited pins step 105

no bent or short-circuited pins, and step 94
the converter you are dealing with is
an NT6X53
no bent or short-circuited pins, and step 95
the converter you are dealing with is
not an NT6X53
94 Insert the NT6X51 and the NT6X52 cards back into the shelf.
297-2651-543 Standard 05.01 March 1999

4-343
Ext FSP
95 Use the following table to identify which alarm and control card is associated
with the shelf with the lit CONVERTER FAIL LED.
04 and 18 slot CD1 (NT6X36AA) right

32 (2X70 in slot 25) slot CD2 (NT0X91AA) left
32 (2X70 in slot 22) slot CD3 (NT0X91AE) middle
and 51
NT0X91AA
card in slot
CD 3
NT0X91AE NT6X36
card in slot card in slot FSP
CD 2 CD 1 cover
96 Record the numbers of the LCM and RMM in the frame.

Replacement Procedures to replace the alarm and control card. When you
have completed the procedure, return to this point.
GSP05 (CSP10)
4-344
Ext FSP
lit, and you have not completed step 99

steps 2 or 3 in this procedure
lit, and you have completed steps 2 step 105
and 3 in this procedure
not lit step 100
99 Go to the step you have not yet completed, that is, step 2, 3, or 4 in this
procedure.
At the MAP
100 Access the Ext level of the MAP to determine whether an FSP alarm is present
by typing
>MAPCI;MTC;EXT
present, and you have not accessed step 101

present, and you have accessed all step 105
not present step 106
101 Perform the appropriate procedure for the type of frame that has the FSP alarm
When you have completed the procedure, return to this point.
At the RLCE frame
102
DANGER
Unscrew the slotted nut on the left-hand side of the FSP.
297-2651-543 Standard 05.01 March 1999

4-345
Ext FSP
RLCERLCE
frameframe
majormajor
(continued)
(end)
The personnel at the next level of support may request this information.
support.
GSP05 (CSP10)
Ext JESCALL
minor
Alarm display
. . . . . . . 1 Min. .
Indication
Under the Ext subsystem header at the MTC level of the MAP display,
1 Min. can indicate one or more JESCALL minor alarms.
Meaning
When a caller makes an emergency call to an attendant, a minor alarm
occurs. The operating company personnel monitor the alarm and gather the
call information from a log. The call information is available to the
attendant if the caller fails to complete the call.
Impact
The subscriber can access the emergency service bureau.
Common procedures
Not applicable
Action
the alarm.
297-2651-543 Standard 05.01 March 1999

Ext JESCALL
minor (continued)
Summary of clearing an Ext JESCALL alarm

procedure.
Access Ext
level at the Use the instructions in the
MAP procedure that follows this
procedure.
List minor
alarms
Check
ESV100 logs
Note
calling party
information
Clear alarm
Alarm
cleared?
End
GSP05 (CSP10)
Ext JESCALL
minor (continued)
Clearing an Ext JESCALL alarm
At the MAP terminal
>EXT
. . 2MPCOS . 1LIM . . 54GC 1 Min .

0 0 0 1 10
2 To display all the Ext minor alarms, type

>LIST MIN
Note: You must set field Report in table SFWALARM to yes. This datafill
ensures that EXT logs with the time of day are recorded for the JESCALL
alarm. This information identifies which EVS100 log corresponds to which
JESCALL alarm.
JESCALL step 4
other items step 3
3 Perform the correct alarm-clearing procedure in this document. When you have
completed the procedure go to step 11.

>LOGUTIL
5 To open the ESV log report buffer, type

>OPEN ESV
6 To display the ESV100 log report, type

>BACK ALL
297-2651-543 Standard 05.01 March 1999

Ext JESCALL
minor
minor
(continued)
(end)
Example of an ESV100 log report.
ESV100 APR22 18:53:03 9800 INFO JAPAN EMERGENCY SERVICE TRACE
CALLING PARTY NUMBER : 347701235
CALLING PARTY : HOST 02 0 01 01 DN 7701235 DN0347700020
OUTGOING TRUNK : CKT FPTPLC1 3
7 Note the calling number, the date and time, and the terminating fire and police
trunk (FPT) number.

>QUIT

>jesclear JESCALL
0 0 0 0 10
jesclear JESCALL
JESCALL alarm cleared
If the alarm Do
clears step 11
fails step10
GSP05 (CSP10)
Ext JESUNANS
minor
Alarm display
. . . . . . . 1 Min. .
Indication
Under the Ext subsystem header at the MTC level of the MAP display,
1 Min. can indicate one or more JESUNANS minor alarms.
Meaning
When no attendant answers an emergency call within the datafilled time, a
minor alarm occurs. The operating company personnel monitor the alarm
and gather the call information from a log. The call information is available
to the attendant.
Impact
The subscriber cannot access the emergency service bureau.
Common procedures
Not applicable
Action
the alarm.
297-2651-543 Standard 05.01 March 1999

Ext JESUNANS
minor (continued)
Summary of clearing an Ext JESUNANS alarm

procedure.
Access Ext
level at the
MAP
procedure.
List minor
alarms
Check
ESV100 log
Note
calling party
information
Clear alarm
Alarm
cleared?
End
GSP05 (CSP10)
Ext JESUNANS
minor (continued)
Clearing an Ext JESUNANS alarm
At the MAP terminal
>EXT
. . 2MPCOS . 1LIM . . 54GC 1 Min .

0 0 0 1 10
2 To display all the Ext minor alarms, type

>LIST MIN
Note: You must set field Report in table SFWALARM to yes. This datafill
ensures that EXT logs with the time of day are recorded for the JESUNANS
alarm. This information identifies which EVS100 log corresponds to which
JESUNANS alarm.
JESUNANS step 4
3 Perform the correct alarm-clearing procedure in this document. When you have
completed the procedure go to step 11.

>LOGUTIL
5 To open the ESV log report buffer, type

>OPEN ESV
6 To display the ESV100 log report, type

>BACK ALL
297-2651-543 Standard 05.01 March 1999

Ext JESUNANS
minorminor
(continued)
(end)
Example of an ESV100 log report.
ESV100 APR22 18:53:03 9800 INFO JAPAN EMERGENCY SERVICE TRACE
CALLING PARTY NUMBER : 347701235
CALLING PARTY : HOST 02 0 01 01 DN 7701235 DN0347700020
OUTGOING TRUNK : CKT FPTPLC1 3
7 Note the calling number, the date and time, and the terminating fire and police
trunk (FPT) number.

>QUIT

>JESCLEAR
0 0 0 0 10
jesclear JESUNANS
JESUNANS alarm cleared
If the alarm Do
clears step 11
fails step10
GSP05 (CSP10)
Ext E911_SRDB_MEMORY
minor
Alarm display
. . . . . . . . 1Min .
Indication
1Min can indicate a possible E911_SRDB_MEMORY alarm. The alarm
occurs if table SRDB approaches maximum size or store is not available.
The minor alarm for the E911 selective routing database (SRDB) memory
appears under the EXT heading in SuperNode and NT40 applications.
Meaning
An E911_SRDB_MEMORY minor alarm means that one or more of these
conditions are present:
• The SRDB uses storage that exceeds a set percentage of the total store in
the switch (default percentage is 80%).
• The free memory drops below an exact value (default value is five
areas).
• The number of tuples in the SRDB exceeds a set percentage (default
value is 95% of the total allowable).
Result
Table E911SRDB approaches maximum size or store is not available if an
E911_SRDB_MEMORY minor alarm activates. The update to table SRDB
also stops when the alarm activates.
Common procedures
Action
procedure.
297-2651-543 Standard 05.01 March 1999

minor (continued)
Summary of How to clear an Ext E911_SRDB_MEMORY minor alarm
Silence EXT This flowchart summarizes the

alarm procedure.

procedure.
Access EXT
level at MAP
List minor alarms
Check for
E911226 log
Is reason for alarm Add memory card. See

“High Store Y Card Replacement
1
Percentage” or “Low Procedures
Available Store”?
N
Is reason for alarm Improve database
SRDB tuple count Y performance. Refer to
“Nears Maximum” or translations group or to
“Maximum Reached”? the next level of control.
N
Change threshold
If no log generates,
values (maximum
contact next level of 1
number of tuples) with
support
QSRDB command
GSP05 (CSP10)
minor (continued)
Summary of How to clear an Ext E911_SRDB_MEMORY minor alarm (continued)
Verify thresholds with

QSRDB command
Y End
Alarm cleared?
Contact next level

of support
297-2651-543 Standard 05.01 March 1999

minor (continued)
How to clear an Ext E911_SRDB_MEMORY minor alarm
At the MAP display

>MAPCI;MTC;SIL

>EXT
0 0 1 0 14

>LIST MAJ
is E911_SRDB_MEMORY step 5
5 Obtain an E911226 log report. To access LOGUTIL, type

>LOGUTIL
6 To view these log reports, open the buffer for the E911 log report. Type,
>OPEN E911226
GSP05 (CSP10)
minor (continued)
7 To display E911226 log reports, type the following command as many times as
needed to see the previous report
>BACK
An E911226 log generates when:
• The SRDB uses storage that exceeds an exact percentage of the total
store in the switch (default 80%).
• Free memory drops below an exact value (default five areas).
• The number of tuples in a database exceeds an exact value (default 95% of
permitted total).
• Table E911SRDB has the maximum number of permitted tuples.
Note: Logs with the reason “Nearing maximum” will not print unless five
minutes passed since the last log time. This time limit ensures that E911226
logs do not flood the system,
Example of an E911226 log report:
E911226 MAR26 08:15:38 1290 INFO SRDB MEMORY WARNING!!!
REASON = ––Low Available Store
Note: The E911225 log generates when tuples increase or change by an exact
number (default=1000) in the database. The counter does not reset on new
updates. The log always generates every 1000 changes on update sessions.
The log is for information only.
Example of an E911225 log report:
E911225 MAR26 08:15:38 1289 INFO SRDB MEMORY INFORMATION
SRDB COUNT 250000, SRDB STORE 81 KBytes, FREE STORE
4 VAreas

>QUIT
297-2651-543 Standard 05.01 March 1999

minor (continued)
9 Note the reason category on the E911226 log.
If the reason Do
is high store percentage step 10

is low available store step 10
is near maximum step 11
is maximum reached step 11
is log did not generate contact next level of support
10 To increase the data store in the SuperNode, add memory card NT9X14BB or
NT9X145DB. Refer to Card Replacement Procedures.
Proceed to step 12.
11 You can optimize the database in table E911SRDB. Use higher range tuples
that have a key to define a range. The range can include the DN for the caller
to route to an emergency service number. In an optimized state, the database
allows the SRDB to serve the largest number of DNs. The database uses
tuples for a range of DNs. It does not assign an exact DN to each tuple. Refer
to the translations group or to the next level of control.
Proceed to step 12.
12 To change threshold values, like the maximum number of tuples, use the CI
command. Type
>QSRDB
13 To determine:
• the number of tuples in table E911SRDB
• the amount of store this table uses
• the amount of free store in the switch
type
>QSRDB MEM
SRDB Count 250,000 SRDB STORE 4,032 KBytes FREE STORE
32 VAreas
GSP05 (CSP10)
minor (continued)
14 To display the values that cause the output of store-use information or warnings
on table E911SRDB, type
>QSRDB THRESH
SRDB %: 80 STORE MINIMUM: 5
NEAR LIMIT: 760000 LOG COUNT: 1000
15
CAUTION
Take care when you use the Set option of the QSRDB
command
This option changes the threshold values that
determine when an alarm or log generates. If the
values are set incorrectly, a possibility is present that
the system will not warn of low store access for table
E911SRDB.
CAUTION
Take care when you use the Set option of the QSRDB
command
This option changes the threshold values that
determine when an alarm or log generates. If the
values are set incorrectly, a possibility is present that
the system will not warn of low store access for table
E911SRDB.
To set threshold values, type

>QSRDB SET <PERCENT <VALUE>
STORE
NLIMIT
COUNT>
When you enter 0 for PERCENT, STORE, NLIMIT and COUNT, the parameter
turns off.
297-2651-543 Standard 05.01 March 1999

minor
minor
(continued)
(end)
If you enter the wrong parameter, the correct range of values for the parameter
appears. A request to enter the command again accompanies the parameter
display.
THRESHOLD VALUES WILL BE:
SRDB %: 85 STORE MINIMUM: 5
NEAR LIMIT: 725000 LOG COUNT: 5000
Please confirm (“YES” or “NO”):
>YES
SRDB THRESHOLD VALUES HAVE BEEN UPDATED
Note: If you enter the wrong parameter, the system prompts you with the
correct ranges.
16 Verify that the arm cleared. If the alarm persists, contact the next level of
support.
17 The procedure is complete
GSP05 (CSP10)
5-1
Procedures to clear an Input/output

device alarm
Introduction
This chapter provides alarm clearing procedures for the input/output device.
Input/output device alarms appear under the IOD header of the alarm banner
in the MAP. All procedures contain the following sections:
• Alarm display
• Indication
• Meaning
• Result
• Action
Alarm display
This section indicates how the MAP terminal displays the alarm.
Indication
This section indicates the location of the alarm indication, the design of the
alarm, the affected subsystem, and the alarm condition.
Meaning
Results
Common procedures
GSP05 (CSP10)
5-2 IOD alarm clearing procedures
maintenance procedures. The removal and replacement of a card are

examples of a common procedure. The common procedures chapter in this
NTP contains common procedures.
Do not use common procedures unless the step–action procedure directs

you.
Action
297-2651-543 Standard 05.01 March 1999

5-3 IOD alarm clearing procedures 5-3
IOD nDDUOS on an IOM

major or minor
Alarm display
. . nDDUOS. . . . . . .
Indication
At the IOD level of the MAP display, DDUOS preceded by a number (n)
indicates a DDU major or minor alarm on the IOM.
Meaning
One or more disk drive units (DDU) are out of service. The number that
precedes DDUOS indicates how many DDUs are out of service.
Impact
No files can be recorded to or downloaded from tape or DDU.
Common procedures
Not applicable
Action
the alarm.
GSP05 (CSP10)

major or minor (continued)
Summary of Clearing an IOD nDDUOS on an IOM major or minor alarm

status of the procedure.
DDU
N Is the DDU N
Is the DDU procedure.
status
SBsy?
––––?
Y
3
Y
Determine the Is the DDU N
DDU drive state status OffL or 3
ManB?
Y
Post and busy Post the DDU When possible,

the DDU return the DDU
to service
2
Test the DDU N
Failed with a N Y
3 Passed?
card list?
1 3
Y
Return the DDU Replace cards.
to service Refer to
appropriate NTP.
N Return DDU to
Passed? 2 service
1 Y 3
End N Contact next

Y
Passed? level of support
1 3
297-2651-543 Standard 05.01 March 1999

IOD alarm clearing procedures 5-5

Clearing a/an IOD nDDUOS on an IOM alarm
ATTENTION
Proceed only if you have been directed to this procedure from a step in
the IOD nDDUOS in an IOC minor alarm clearing procedure.
At the MAP
1 Access the IOD level of the MAP display by typing
>MAPCI;MTC;IOD
IOD
IOC 0 1 2 3
STAT . . . S
DIRP: SMDR B XFER: . SLM : . NPO: . NX25: .

MLP : . DPPP: . DPPU: . SCAI :
2 Determine if an audible alarm exists.
If an audible alarm Do
exists step 3
does not exist step 4
3 Silence the alarm by typing

>SIL
GSP05 (CSP10)

4 Post the IOM controller system by typing

>IOC ioc_no
where
ioc_no is the number of the affected IOM
Example of a IOM MAP display:
IOD
IOC 0 1 2 3
STAT . . . S

IOC PORT 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
(IOM) STAT . . . – . . – – – . – – – – – – – –
0 TYPE C C C C M M D S
O O O O T P D C
N N N N D C U S
5 Display the status of the disk drive unit (DDU) by typing

>LISTDEV DDU
DDU USER STATUS IOC CARD PORT DRIVE STATE

1 System Ready 0 3 0 On Line
6 System Offl 3 – 16 ––––––––
6 From the status display, determine the status of the DDU.
If the status is Do
SysB step 7
_ _ _ _ _ step 64
OffL or ManB step 52
297-2651-543 Standard 05.01 March 1999


7 Examine the drive state of the system busy DDU.
If the drive state is Do
ONLINE step 8
DISCONNECTED step 23
DRIVE FAULTS step 27
SPINNING step 26
SPINNING DOWN step 29
SPUN DOWN step 36
UNKNOWN step 44
8 Post the DDU port on the IOM by typing

>IOC ioc_no;PORT port_no
where
port_no is the number of the DDU port
9 Manually busy the DDU IOM port by typing

>BSY PORT port_no
bsy
OK
GSP05 (CSP10)

10 Test the DDU port by typing

>TST
passed step 61
failed, and a card list was generated step 11
failed, and no card list was step 64
generated
11 Record the location, description, slot number and the product engineering code
(PEC), including suffix, of the cards on the card list.
12 Replace the first card on the list by performing the appropriate procedure in
13 Test the DDU device to service by typing

>TST
passed step 61
failed, and you have not replaced all step 14
the cards noted in step
failed, and you have replaced all the step 64
cards noted in step
14 Replace the next card on the list by performing the appropriate procedure in
15 Go to step 13.
297-2651-543 Standard 05.01 March 1999


At the equipment shelf
16
WARNING
Wear a wrist strap connected to the wrist-strap
grounding point of a modular supervisory panel
(MSP) while handling circuit cards. This protects the
cards against damage by static electricity.
Check the NTFX40 SCSI cable connecting the NTFX31 paddleboard to the
backplate pins of slot 4 and reconnect.
Note: The plug-in 3.5-in. (89mm) DDU is located on the NTFX32 IOM storage
media card in slot 4 and 5 of the ISM shelf. The cabling for the storage media
card connects the DDU to the NTFX31 paddleboard located in slot 3 at the rear
of the ISM shelf.
At the MAP terminal
17 Test the DDU by typing
>TST
passed step 61
failed, and a card list was not step 64
generated
18 Record the location, description, slot number and PEC, including suffix, of the
cards on the card list.
GSP05 (CSP10)

20 Test the DDU to service by typing

>TST
passed step 61
the cards noted in step 18
cards noted in step 18
22 Go to step 20.
23 Post the DDU port on the IOM by typing

where
24 Manually busy the DDU by typing

>BSY

bsy
OK
25 Go to step 16.
297-2651-543 Standard 05.01 March 1999


26 Wait for a few minutes while the DDU is spinning up to speed.
If status of the DDU Do
changes to ONLINE step 62

does not change to ONLINE step 64
27 Replace the DDU by performing the appropriate procedure in Trouble Locating

and Clearing Procedures. When you have completed the procedure, return to
this point.
28 Go to step 23.
29 Determine from office records or from office personnel why the DDU is spinning
down. Wait for a few minutes for the DDU to stop spinning.
30 When permissible, return the DDU device to service by typing

>IOC ioc_no;PORT port_no;RTS
where
ioc_no is the number of the affected IOC
port_no is the number of the IOM DDU port
passed step 62
generated
31 Record the location, description, slot number, and PEC, including suffix, of the
card(s) on the card list.
GSP05 (CSP10)


>TST
passed step 61
35 Go to step 33.
36 Post and busy the DDU device on the IOM by typing

>IOC ioc_no;PORT port_no;BSY
where
bsy
OK
37 Determine from the office records or from office personnel why the DDU was
spun down.
297-2651-543 Standard 05.01 March 1999


38 When permissible, return the DDU to service by typing

>RTS
passed step 62
generated

>TST
passed step 61
43 Go to step 41.
GSP05 (CSP10)

44 Post the DDU device on the IOM by typing

where
45 Manually busy the DDU port by typing

>BSY
bsy
OK

>TST
passed step 61
generated
297-2651-543 Standard 05.01 March 1999



>TST
passed step 61
51 Go to step 49.
52 Post the DDU device on the IOM by typing

where
card_no is the number of the DDU port
53 Determine from office records or from office personnel whether the DDU is
offline or manual busy.
If the DDU is Do
offline step 54
manual busy step 55
GSP05 (CSP10)

54 Manually busy the DDU by typing

>BSY
bsy
OK
55 Return the DDU to service by typing

>RTS
passed step 62
generated

>TST
passed step 61
297-2651-543 Standard 05.01 March 1999


majormajor
or minor
or minor
(continued)
(end)
60 Go to step 58.
61 Return the DDU to service by typing

>RTS
passed step 62
failed step 64
62 Check under the IOD banner on your MAP display to determine if the nDDUOS
major or minor alarm has cleared.
If the nDDUOS alarm Do
cleared step 65
63 Perform the appropriate alarm clearing procedure in this document. When you
have completed the procedure, go to step 65.
support.
GSP05 (CSP10)
IOD nIOCOS on an IOM

major or minor
Alarm display
. . nIOCOS . . . . . .
Indication
At the IOD level of the MAP, a number (n) and IOCOS indicate an IOCOS
major or minor alarm.
Meaning
One input/output module or more than one input/output modules (IOMs) are
out of service. The number that precedes IOCOS indicates the number of
out of service IOMs.
Result
All devices with an IOM that is not in service lost communication with the
switch.
Common procedures
Action
The flowchart is a summary of the procedure. Use the instructions in the
step-action procedure that follows the flowchart to clear the alarm.
297-2651-543 Standard 05.01 March 1999


Summary of Clearing an IOD nIOCOS on an IOM alarm

procedure.
Determine the
status of the Use the instructions that follow this
IOM flowchart to perform the procedure.
N N Is the IOM N
Is the IOM Is the IOM
status O 1
status S? status C?
or M?
Y Y Y
MBsy IOC, Clear alarm. When possible,

reset and test Refer to correct return the IOM
the IOM NTP. to service
2
N Replace cards. Return the IOM

Passed? Refer to correct to service
NTP.
Y
3 3 2
Test the IOM
N
Return the IOC Contact next
to service 22 Passed? 1 level of support
Y
1
End
GSP05 (CSP10)

Clearing an IOD nIOCOS on an IOM alarm
ATTENTION
Proceed only if a step in the IOD nIOCOS in an IOC minor alarm
clearing procedure directed you to this procedure
At the MAP terminal

>MAPCI;MTC;IOD
IOD
IOC 0 1 2 3
STAT . . . S

2 Determine if the audible alarm is present.
If the audible alarm Do
is present step 3

>SIL
297-2651-543 Standard 05.01 March 1999


4 To determine the configuration of the controller system, type

>IOC ioc_no
where
Example of an IOM MAP :
IOD
IOC 0 1 2 3
STAT . . . S

IOC PORT 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
(IOM) STAT . . . – . . – – – . – – – – – – – –
O O O O T P D C
N N N N D C U S
5 Determine the status of the affected IOM.
If the status Do
is S (system busy) step 6

is C (C-side busy) step 15
is O(offline) step 16
is M (manual busy) step 16
6 To manually busy the IOM, type

>BSY IOC
bsy
OK
GSP05 (CSP10)

7 To test the IOM controller card, type

>TST IOC

Failed
Site Flr Rpos Bay_Id Shf Description Slot EqPEC
HOST 01 A05 ISME 03 32 IOC 03 FX30AA
passed step 14
card list
8 To reset the IOM processor card, type

>RESET IOC
Wait ten seconds.
This process may cause sever problems with IO devices
Please confirm “YES”, “Y” or “NO” “N”
Enter “Y”
297-2651-543 Standard 05.01 March 1999


9 To test the IOM, type

>TST IOC

Failed
passed step 14
card list
(PEC), and PEC suffix of the cards on the card list.
11 Perform the correct procedure in Card Replacement Procedures. to replace the
first card on the list. Complete the procedure and return to this point.
At the MAP terminal
12 To test the IOM, type
>TST IOC
passed step 14
noted in step 10
GSP05 (CSP10)

next card on the list. Complete the procedure and return to this point.
Note: The splitter unit NTFX39 can require a replacement. Go to the next level
of support.
At the MAP terminal

14 To return the IOC to service, type
>RTS IOC
passed step 20
failed step 19
15 To clear the alarm, perform the correct procedure in this document. Complete
16 Consult office logs or operating company personnel. Determine the reason that
the IOC is offline or manually busy. To return the IOC to service, type
>IOC ioc_no;RTS IOC
where
passed step 20
failed step 19
297-2651-543 Standard 05.01 March 1999


majormajor
or minor
or minor
(continued)
(end)
17 Check under the IOD banner on your MAP display to determine if the nIOCOS
major or minor alarm cleared.
If the alarm Do
cleared step 20
correct procedure and go to step 17.
GSP05 (CSP10)
IOD MPCLNK on an IOM

minor
Alarm display
. . MPCLNK. . . . . . .
Indication
MPCLNK appears at the IOD level of the MAP display. MPCLNK
indicates a minor alarm for the multiple protocol controller link on the
input/output module (IOM).
Meaning
One or more multiple protocol controller links are system-busy.
Result
If the link becomes system busy during transmission, loss of data can occur.
Common procedures
Action
297-2651-543 Standard 05.01 March 1999


minor (continued)
Summary of Clearing an IOD MPCLNK on an IOM alarm

procedure.
Post, bsy and
test MPC Use the instructions that follow this
N MPC logs N N
Passed? Card list 2
Y Y Y
N
Select port, Replace card
offline and test and test Passed? 2
Y
1
Smart N Port N Supply another

connector available? IOM
identified?
Y Y
Change Supply and post
connector and new port
test
1 N
Contact next Move smart

Alarm 2 level of support cable and test
cleared?
1
End
GSP05 (CSP10)

minor (continued)
Clearing an IOD MPCLNK on an IOM alarm
ATTENTION
Proceed only if a step in the IOD MPCLNK in an IOC minor alarm
clearing procedure directed you to this procedure.
At the MAP
>MAPCI;MTC;IOD
IOD
IOC 0 1 2 3
STAT . . . S

2 To post the configured controller system, type

>IOC ioc_no
where
IOC PORT 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
(IOM) STAT . . . – . . – – – . – – – – – – – –
O O O O T P D C
N N N N D C U S
297-2651-543 Standard 05.01 March 1999


minor (continued)
3 To post the affected IOM MPC port, type

>PORT port_no
where
card_no is the port number of the MPC device
Example of a MAP:
Port 3 Unit 1
User SYSTEM PROTOCOL LINK
Status Ready X2584 COMACT ENABLD
4 To manually busy the MPC, type

>BSY

bsy
OK
5 To test the MPC, type

>TST
passed step 35
card list
MPC logs
GSP05 (CSP10)

minor (continued)
6 To place the MPC offline, type

>OFFL
7 To return to the IOC level of the MAP display, type

>QUIT
8 To make the IOM MPC port manually busy, type

>BSY PORT port_no
where
port_no is the number of the MPC port
bsy
OK
9 To place the IOM MPC port offline, type

>OFFL PORT port_no
where
297-2651-543 Standard 05.01 March 1999


minor (continued)
10 To test the IOM MPC port, type

>TST PORT port_no
where
port_no is the port number of the MPC device
Failed
Check and replace smart connector for port 3 (FX34, FX35)
If an identified smart connector Do
is present step 11
At the back of the ISM shelf

11
WARNING
(MSP) to handle circuit cards. The wrist strap protects
the cards against static electricity damage.
CAUTION FOR ESDS

(MSP) to handle circuit cards. The wrist strap
protects the cards against static electricity damage.
Locate the smart cable that connects the MPC port on the paddle board and the
associated MPC device. Check the smart connector LED. Replace the smart
connector.
GSP05 (CSP10)

minor (continued)
12 To test the smart connector, type

>TST PORT port_no
where
Failed
If the smart connector Do
passes step 26
fails step 13
13 Go to step 2. Select an open IOM port and return to this point.
If Do
a port is available on the posted step 14

IOM controller
a port is available on another IOM step 28
another IOC is not available step 30
297-2651-543 Standard 05.01 March 1999


minor (continued)
14
CAUTION
Provisioning changes
You can require the help of the provisioning
administrator before you proceed with the following
provisioning changes.
CAUTION
To determine from table IOC if the open port contains the correct load device,
type
>TABLE IOC
15 To access table MPCLINK, type

>TABLE MPCLINK
16 Delete the link tuple for the affected port.
17 To access table MPC, type

>TABLE MPC
Example of a MPC table:
Table: MPC
MPCNO MPCIOC IOCCCT EQ DNDFILE
1 3 2 FX30AA IOM$LOAD
GSP05 (CSP10)

minor (continued)
18 Delete the tuple for the affected port.

>TABLE MPC
Table: MPC
20 Add the tuple for the spare IOM port selected in step13.

>TABLE MPCLINK
22 Add the link tuple for the spare IOM port selected in step 13.
23 To post the new IOM MPC port, type

>PORT port_no
where
Port 3 Unit 1
Status Ready X2584 COMACT ENABLD
24 To make the MPC manually busy, type

>BSY

bsy
OK
297-2651-543 Standard 05.01 March 1999


minor (continued)
25
WARNING
(MSP) to handle circuit cards. The wrist strap protects
the cards against static electricity damage.
CAUTION FOR ESDS

(MSP) to handle circuit cards. The wrist strap
protects the cards against static electricity damage.
Locate the smart cable that connects the MPC port on the paddle board and the
associated MPC device. Disconnect the smart cable. Connect the smart cable
to the new MPC port.
Go to step 35.
26 To manually busy the port for the MPC device, type

>BUSY PORT port_no
where
bsy
OK
27 To return the MPC port to service, type

>RTS PORT port_no
where
Go to step 35.
GSP05 (CSP10)

minor (continued)
28 To post another configured controller system, type

>IOC ioc_no
where
Example of a IOM MAP:
IOC PORT 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
(IOM) STAT . . . – . . – – – . – – – – – – – –
O O O O T P D C
N N N N D C U S
29 Select an open IOM port on the new controller.
If a port Do
is available step 14
is not available step 30
297-2651-543 Standard 05.01 March 1999


minor (continued)
30
CAUTION
You need the help of the provisioning administrator
before you proceed with the following provisioning
changes.
CAUTION
changes.
You must provide another IOM module. Consult your provisioning administrator
to add and provision another IOM controller card.
Go to step 37.
31 Perform the correct procedure in Card Replacement Procedures to replace the

32 To test the IOM card, type

>TST

Failed
If the test Do
passes step 34
fails, and you did not replace all step 33
cards
fails, and you replaced all cards step 38
GSP05 (CSP10)

minor (continued)
(end)

second card on the list. Complete the procedure and return to this point.
Go to step 32.

>PORT port_no
where
Example of a MAP:
Port 9 Unit 1
Status Ready X2584 COMACT ENABLED
35 To return the IOM MPC to service, type

>RTS
If the alarm Do
cleared step 38
297-2651-543 Standard 05.01 March 1999

IOD nCKOS on an IOM

major or minor
Alarm display
. . nCKOS . . . . . . .
Indication
At the IOD level of the MAP display, CKOS preceded by a number (n)
indicates a major or minor port out-of-service alarm.
Meaning
One or more ports are out of service. The number that precedes CKOS
indicates how many ports are out of service. Each of these ports is
connected to a terminal, such as a MAP terminal or a printer.
Impact
Service is discontinued to any device associated with an out-of-service
circuit or port.
Common procedures
Not applicable
Action
the alarm.
GSP05 (CSP10)
IOD nCKOS on an IOM

Summary of clearing an IOD nCKOS on an IOM alarm

procedure.
2
Select an open procedure that follows this
port flowchart to perform the
procedure.
Offline and test

port
N Select open Port N Provision

Smart
port available? another IOM
connector?
Y Y
Change Move smart Move smart
connector cable cable
3 3 3
Test the circuit
Return the N Contact next

circuit to service Passed? 5 level of support
1 Y
End
297-2651-543 Standard 05.01 March 1999

IOD nCKOS on an IOM

Clearing a/an IOD nCKOS on an IOM alarm
ATTENTION
the IOD nCKOS in an IOC minor alarm clearing procedure.
At the MAP terminal

>MAPCI;MTC;IOD

IOD
IOC 0 1 2 3
STAT . . . S

MLP:: . DPPP: . DPPU: . SCAI: .
exists step 3
does not exists step 4

>SIL
GSP05 (CSP10)
IOD nCKOS on an IOM

4 Determine the configuration of the controller system by typing

>IOC ioc_no
where
IOC PORT 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
(IOM) STAT . . . – . . – – – . – – – – – – – –
0 TYPE C C C C M M S S
O O O O T P C C
N N N N D C S S
5 Record the port status display for each console.
If the port status is Do
C (C-side busy) step 6

P (P-side busy) step 9
6 The C-side links to the console are out of service. Determine if there is an
alarm under the MS header.
If an alarm under the MS header Do
exists step 7
7 Clear the alarm by performing the appropriate procedure in this document.

297-2651-543 Standard 05.01 March 1999

IOD nCKOS on an IOM

8 Determine from the MAP display if the alarm under the MS header has cleared.
If the alarm Do
cleared step 9
9 Record the IOM console ports that have P status.
If the P status affects Do
one port step 11

more than one port step 10
10 Select one port to work from the list recorded in step 9.
11 Post the affected IOM console port by typing

>PORT port_no
where
port_no is the port number of the affected console device
Port 2 Status
Cons Id MAP
ConType CYB
If the device status is Do
SYSb step 12
Offl step 47
ManB step 45
GSP05 (CSP10)
IOD nCKOS on an IOM

12 Manually busy the console by typing

>BSY

bsy
OK
13 Test the console by typing

>TST
passed step 49
generated
14 Offline the terminal by typing

>OFFL
15 Return to the IOC level of the MAP display by typing

>QUIT
16 Manually busy the console port by typing

>BSY PORT port_no
circuit_no is the number of the circuit
bsy
OK
297-2651-543 Standard 05.01 March 1999

IOD nCKOS on an IOM

17 Offline the busied console port by typing

OFFL PORT port_no
18 Test the console port by typing

>TST PORT port_no
where
Failed
Check smart connector for port 5
If a smart connector is Do
identified step 19
not identified step 21
At the rear of the ISM shelf

19
WARNING
Locate the PERTEC smart connector mounted on an L-shaped bracket close to

the tape drive and check the smart connector LED. Replace the smart
connector.
GSP05 (CSP10)
IOD nCKOS on an IOM

20 Test the smart connector by typing

>TST PORT port_no
where
Failed
passes step 29
fails step 21
At the MAP terminal

21 Go to step 4, select an open IOM port and return to this point.
If a port is Do
available on the posted IOM step 23

controller
available on another IOM step 32
there is no other IOM available step 34
297-2651-543 Standard 05.01 March 1999

IOD nCKOS on an IOM

22
CAUTION
You may require the assistance of the provisioning
administrator before proceeding with the following
Determine from table IOC if the open port is datafilled with the correct load
device by typing
>TABLE IOC
23 Go to table CONS by typing

>TABLE TERMDEV
24 Delete the tuple associated with the affected port and add the tuple for the
spare IOM port selected in step 21.
25 Post the new IOM CONS port by typing

>PORT port_no
where
port_no is the number of the CONS port
Port 2 Status
Cons Id MAP
ConType CYB
26 Manually busy the new console by typing

>BSY

bsy
OK
GSP05 (CSP10)
IOD nCKOS on an IOM

27
WARNING
Locate the smart cable connecting the CONS port on the paddleboard and the
associated CONS device. Disconnect the smart cable and connect it to the
new CONS port selected in step 21.
28 Go to step 40.

>BSY PORT port_no
where
port_no is the port number of the CONS device
bsy
OK
30 Return the console port to service by typing

>RTS PORT port_no
where
31 Go to step 36.
297-2651-543 Standard 05.01 March 1999

IOD nCKOS on an IOM

32 Post another configured controller system by typing

>IOC ioc_no
where
IOC PORT 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
(IOM) STAT . . . – . . – – – . – – – – – – – –
O O O O T P C C
N N N N D C S S
If there is a port Do
available step 22
not available step 34
34
CAUTION
You will require the assistance of the provisioning
There will be a requirement to provision another IOM module. Consult your

provisioning administrator about provisioning another IOM controller card.
35 Go to step 51.
36 Replace the card by performing the appropriate procedure in Card

this point.
GSP05 (CSP10)
IOD nCKOS on an IOM

37 Test the IOM card by typing

>TST
Failed
If the test Do
passes step 41
fails, and all cards have not been step 38
replaced
failed, and all cards have been step 51
replaced
return to this point. Go to step 37.
39 Go to step 37.
40 Post the console port by typing

>PORT port_no
where
port_no is the port number of the console device
41 From your MAP display, record the console ID and console type.
42 Determine from office records the correct data set configuration for the console.
43 Check the console to ensure that it is running properly and there are no
physical problems.
297-2651-543 Standard 05.01 March 1999

IOD nCKOS on an IOM

44 Check the external switch settings on the console.
Switch Setting
Power On
Local/OnLine OnLine
Baud Rate 1200 (or as required – see IS3X01)
Parity No Parity
Full Duplex/Half Duplex Full Duplex
If the external switch settings are Do
correct step 46
not correct step 45
45 Change the external switch setting as per the table in step 44. When you have
completed the procedure return to this point.
46 Test the console device by typing

>TST
where
passed step 49
failed step 51
47 Determine from office records or from office personnel why the console is
offline. When permissible, manually busy the console by typing
>BSY
GSP05 (CSP10)
IOD nCKOS on an IOM

(end)
48 Test the manually busy console by typing

>TST
passed step 49
generated
49 Return the console to service by typing

>RTS
passed step 50
failed step 51
50 Determine from the MAP display if the nCKOS major or minor alarm has
cleared.
If the alarm Do
cleared step 52
did not clear, and there are other step 10
consoles out of service
did not clear, and all consoles are in step 51
service
support.
297-2651-543 Standard 05.01 March 1999

5-53 5-53
IOD nCKEr on an IOM

minor
Alarm display
. . 1CKEr. . . . . . . .
Indication
At the MTC level of the MAP display, CKEr preceded by a number appears
under the IOD header of the alarm banner, and indicates a circuit error alarm
in the input/output module (IOM).
Meaning
One or more I/O devices is disconnected. The number preceding CKEr is
the number I/O that are disconnected.
The CkEr alarm for a disconnected an I/O device on an IOM can be disabled
by changing the datafill for the device in field CKERDISC in table
TERMDEV to N. For additional information refer to the description of table
TERMDEV in the Data Schema section of Translations Guide.
If the port is connected to a modem that is currently idle, the disconnected

status is normal. The alarm may be disabled in the field CKERDISC in
table TERMDEV to N.
Impact
The CKEr alarm is generated for an I/O device disconnected at the
Common procedures
Not applicable
Action
the alarm.
GSP05 (CSP10)
5-54
IOD nCKEr on an IOM

minor (continued)
Summary of Clearing an IOD nCKEr on an IOM minor alarm

procedure.
Console Y Post, bsy and Use the instructions in the

disconnected? offline IOM port procedure that follows this
procedure.
N
2
Test IOM port
Smart Y Reconnect
connector connector 1
identified?
N
Check for N
disconnected 2
cables?
Y
Reconnect
cables
1
Check that N Contact next
links are in 2 level of
service? support
Y
End
297-2651-543 Standard 05.01 March 1999

5-55
IOD nCKEr on an IOM

minor (continued)
Clearing a/an IOD nCKEr on an IOM alarm
At the MAP terminal
>MAPCI;MTC;IOD
IOD
IOC 0 1 2 3
STAT . . . S

GSP05 (CSP10)
5-56
IOD nCKEr on an IOM

minor (continued)
2 Display the state of the console devices by typing

>LISTDEV CONS
CONS ID CONSTYPE STATUS IOC.CARD/PORT
MAP VT100 . 0.2
RD030 VT100 . 0.2
RD040 VT100 . 0.4
RD041 VT100 . 0.4
RP042 KSR Disc 0.4
RP061 KSR . 0.6
RV062 VT100 . 0.6
RV063 VT100 . 1.2
RD140 VT100 . 1.4
RD141 VT100 . 1.4
RP142 KSR . 1.4
RV160 VT100 . 1.6
RV163 VT100 . 1.6
RD045 VT100 . 2.0
RD046 VT100 . 2.0
RD050 VT100 . 2.0
RD051 VT100 . 2.0
RP200 VT100 . 2.1
RP203 VT100 . 2.1
RP205 VT100 . 2.2
RP206 VT100 . 3.0
RD31 VT100 . 3.0
RD32 VT100 . 3.1
RD33 VT100 . 3.1
RD34 VT100 . 3.1
RD35 VT100 . 3.1
RD36 VT100 . 3.2
3 Record the IOM number and port number for each console device with a state
of Disc (disconnected).
If Do
one IOM has disconnected console step 5

device
more than one IOM has step 4
disconnected console device
297-2651-543 Standard 05.01 March 1999

5-57
IOD nCKEr on an IOM

minor (continued)
4 Choose an IOM to work on.
5 Post the controller system configured by typing

>IOC ioc_no
where
IOC PORT 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
(IOM) STAT . . . – . . – – – . – – – – – – – –
O O O O T P D C
N N N N D C U S
If Do
one port associated with the IOM step 7

was recorded in step 3.
more than one port associated with step 6
the IOM was recorded in step 3.
6 Choose a IOM port to work on.
GSP05 (CSP10)
5-58
IOD nCKEr on an IOM

minor (continued)
7 Post the terminal controller port by typing

>PORT port_no
where
port_no is the port number of the terminal controller device (0 to 15)

Port 2 Status Disc
Cons Id 1CONS
ConType VT100
Note: Disconnected circuits (links) are identified by a state of Disc in the status
field.
8 Busy the console by typing

>BSY
bsy
OK
9 Offline the console by typing

OFFL

>QUIT
11 Manually busy the IOM controller port by typing

>BSY PORT port_no
bsy
OK
297-2651-543 Standard 05.01 March 1999

5-59
IOD nCKEr on an IOM

minor (continued)
12 Offline the IOM controller port by typing

>OFFL PORT port_no
13 Test the IOM controller port by typing

TST PORT port_no
where
port_no is the number of the port
Failed
Check and replace smart connector for port 5 (FX36)
identified step 14
GSP05 (CSP10)
5-60
IOD nCKEr on an IOM

minor (continued)
At the back of ISM shelf
14
WARNING
Locate the smart cable connecting the CONS port identified in the MAP
response in step 13 and reconnect the RS232 smart connector.
Go to step 17.
15 Locate the console cables between the console port on the paddleboard at the
backplane and the RS232 smart connectors at the associated console device
and determine if they are disconnected.
Note: In the case of a cabinetized ISM (CISM), the cables from the controller
paddleboard are connected to a splitter unit on the ISM bulkhead. Other cables
connect the splitter unit to the associated console device through RS232 smart
connectors.
If Do
one or more cables is disconnected step16

no cables are disconnected step 26
16 Reconnect the cables.

Note: If the associated console device is connected at the remote end with an
RS232 smart connector, ensure that the connector is properly seated.
At the MAP terminal

>BSY PORT port_no
297-2651-543 Standard 05.01 March 1999

5-61
IOD nCKEr on an IOM

minor (continued)
18 Return the IOM controller port to service by typing

RTS PORT port_no
passed step 19
failed step 26
19 Post the terminal port by typing

>PORT port_no
20 Busy the terminal by typing

>BSY
bsy
OK
GSP05 (CSP10)
5-62
IOD nCKEr on an IOM

minor (continued)
(end)
21 Return the terminal to service by typing

>RTS
22 From the MAP display for the posted IOM, determine the state of the links you
reconnected.
If Do
the state of all links is in service (.) step 23

one or more links is not in service step 26
23 Determine if there are other IOMs with disconnected console devices.

If there are Do
other IOMs with disconnected step 4

console devices
no other IOMs with disconnected step 24
console devices
24 Determine if the CKEr alarm cleared.
If the alarm Do
cleared step 27
support.
297-2651-543 Standard 05.01 March 1999

IOD ssys BIOD ssys (continued)

critical B critical
Alarm display
. . ssys B . . . . . . .
C
Indication
At the IOD level of the MAP display, ssys B alarm indicates a ssys B critical
alarm.
Meaning
When a DIRPSSYS table does not contain entered data, or data deletes from
the table, a subsystem failure occurs. The abbreviation ssys represents the
affected subsystem.
Result
If you need to, you can perform a warm restart to activate the subsystem
after you enter data in the tables. Warm restarts disrupt the normal function
of the core.
Common procedures
Action
Contact the next level of support.
GSP05 (CSP10)
IOD DEVBnn
critical, major, or minor
Alarm display
. . DEVBnn . . . . . . .
Indication
At the IOD level of the MAP display, DEVB followed by a number (nn)
indicates a device driver critical, major, or minor alarm.
Meaning
The DIRP utility failed to identify the device driver, DIRPDSON or
DIRPTSON. Another possibility is that the device driver does not run.
These failures are a result of damaged software or hardware that the device
driver depends on.
Result
If you repair the device driver immediately, the condition does not affect
service. Failure to repair the device driver immediately results in loss of
automatic message accounting (AMA) data.
Common procedures
Action
297-2651-543 Standard 05.01 March 1999

IOD DEVBnn
critical, major, or minor (continued)
Summary of Clearing an IOD DEVBnn critical, major, or minor alarm
Activate device This flowchart summarizes the

driver procedure.

procedure.
Contact next
level of support
End
GSP05 (CSP10)
IOD DEVBnn
(end)
Clearing a IOD DEVBnn critical, major, or minor alarm
1 Perform the correct procedure in Recovery Procedures. to activate the device
driver. Complete the procedure and return to this point.
297-2651-543 Standard 05.01 March 1999

IOD DMNTnn
minor
Alarm display
. . DMNTnn . . . . . . .
Indication
At the IOD level of the MAP display, DMNT followed by a number (nn)
indicates a demount minor alarm.
Meaning
The transmission of a tape from a tape drive to a remote data center is
complete. The number that follows DMNT represents the number of the
tape drive with the tape.
Result
Service is not affected.
Common procedures
Action
The following flowchart is a summary of the procedure. Use the
the alarm.
GSP05 (CSP10)
IOD DMNTnn
minor (continued)
Summary of Clearing a IOD DMNTnn minor alarm
Demount tape This flowchart summarizes the

on the MTD procedure.

Manually busy procedure.
MTD
Offline MTD
Enable switches
Demount tape
Manually busy
MTD card
Remove tape
End
297-2651-543 Standard 05.01 March 1999

IOD DMNTnn
minor (continued)
Clearing a IOD DMNTnn minor alarm
At the MAP terminal
1 To access the Xfer (transfer) level of the MAP terminal, type
>MAPCI;MTC;IOD;XFER
Example of a MAP:
IOD
IOC 0 1 2 3
STAT . . . .
DIRP: XFER: DMNT74 SLM : . NPO: . NX25: .

2 To list the files that require demounting, type

>QUERY DMNT
3 Record the number in the HOLDNO field of the MAP terminal. The volume
name is in field FILE_LOCN. Match the two digits that appear in the alarm to
the HOLDNO field.
4 Determine from office records the magnetic tape drive (MTD) with the mounted
tape.
5 To demount the tape, type

>DMNT
where
nn is the number that appears in the alarm
GSP05 (CSP10)
IOD DMNTnn
minor (continued)

>IOC ioc_no
where
ioc_no is the number of the affected IOC or IOM
Example of an IOC MAP display:
IOC CARD 0 1 2 3 4 5 6 7 8
0 PORT 0123 0123 0123 0123 0123 0123 0123 0123 0123
STAT .––– .––– ...P ..–– ..–– ––– ––– ––– –––
TYPE MTD DDU CONS DLC CONS
Example of an IOM MAP display:

IOC PORT 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
(IOM) STAT . . . – . . – – – . – – – – – – – –
O O O O T P C C
N N N N D C S S
If the controller Do
is IOC step 7
is IOM step 8
297-2651-543 Standard 05.01 March 1999

IOD DMNTnn
minor (continued)
7 To post the affected MTD card, type

>CARD card_no
where
card_no is the number of the MPC card
Card 0 Unit 0
User system Drive_state
Status Ready On_line
Go to step 9.
8 To post the affected IOM MTD port, type

>PORT port_no
where
card_no is the number of the MTD port
Port 5 MTD 0
User system Drive_state
9 To make the MTD manually busy, type

>BSY
bsy
OK
passed step 10
failed step 11
GSP05 (CSP10)
IOD DMNTnn
minor (continued)
10 To place the MTD offline, type

>OFFL
Go to step 14.
11 Determine from office logs or from operating company personnel why you
cannot busy the MTD.
Another user Do
uses the MTD step 12

does not use the MTD step 19
12 When you have permission, continue this procedure.
13 To enable the switches, type

>INHIBIT mtd_no OFF
where
mtd_no is the number of the available MTD

>DEMOUNT tape_name
where
tape_name is the name of the tape
15 To make the MTD manually busy, type

>BSY
bsy
OK
passed step 16
failed step 19
297-2651-543 Standard 05.01 March 1999

IOD DMNTnn
minor
minor
(continued)
(end)
At the switch
16 Remove the tape from the hub.
If the tape Do
contains OM or AMA data step 17

does not contain OM or AMA data step 18
17 Enter the tape volume serial number in the DIRPHOLD. Perform the correct
procedure in the Translations Guide. Complete the procedure and return to this
point.
18 Store the tape or prepare the tape for shipping.
GSP05 (CSP10)
IOD HOLDnn
minor
Alarm display
. . HOLDnn . . . . . . .
Indication
At the IOD level of the MAP display, HOLD followed by a number (nn)
indicates a hold minor alarm.
Meaning
A number of slots (nn) out of a possible 100 slots are free in table
DIRPHOLD.
Result
Common procedures
Action
the alarm.
297-2651-543 Standard 05.01 March 1999

IOD HOLDnn
minor (continued)
Summary of Clearing an IOD HOLDnn minor alarm

Contact next
procedure.
level of support
procedure.
End
GSP05 (CSP10)
IOD HOLDnn
minor (continued)
(end)
Clearing an IOD HOLDnn minor alarm
At your Current Location
297-2651-543 Standard 05.01 March 1999

IOD ITOC
critical
Alarm display
. . ITOC . . . . . . .
*C*
Indication
At the MTC level of the MAP display, ITOC appears under the IOD header
of the alarm banner. The ITOC indicates an image table of contents (ITOC)
critical alarm.
Meaning
Image files are not registered do not exist in the two computing module
(CM) ITOCs. Image files are not registered in the two message switch (MS)
ITOCs. Image files are not registered for both CM and for both MS ITOCs,
of the system load module (SLM) disks.
Result
A reload initiated during an ITOC critical alarm can cause a loss of service.
Common procedures
Action
the alarm.
GSP05 (CSP10)
IOD ITOC
Summary of Clearing an IOD ITOC critical alarm

which ITOCs procedure.
are empty
Add image files procedure.
to the ITOCs

End
297-2651-543 Standard 05.01 March 1999

IOD ITOC
Clearing an IOD ITOC alarm
At the MAP terminal
1 To ensure that you are at the CI level of the MAP display, type
>QUIT ALL
2 To access the disk utility, type

>DISKUT
3 To list the volumes on the SLM disks, type

>LISTVOLS CM
Volumes found on the node CM:
–––––––––––––––––––––––––––––
NAME TYPE TOTAL FREE TOTAL OPEN ITOC LARGEST
BLOCKS BLOCKS FILES FILES FILES FREE SEGMENT
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
S00DIMAGE1 STD 614389 142554 28 0 0 81715
S00DPMLOADS STD 614389 137474 83 0 0 82386
S00DDLOG STD 8185 4995 49 0 0 586
S01DIMAGE1 STD 614389 29436 39 0 0 7320
S00DPMLOADS STD 51189 245 116 0 0 78
S01DDLOG STD 8185 597 15 0 0 134
Total number of volumes found on node CM : 6
4 Determine from office records the volumes that contain the CM and MS image
files (one image volume for each disk).
GSP05 (CSP10)
IOD ITOC
5 List the file information for the image volume on the disk of SLM 0. Type
>LISTFL disk_volume_name
where
disk_volume_name is the name of the disk of SLM 0 (S00D) and the name of
the volume on S00D that contains the CM and MS image
files
Example input:
>LISTFL S00DIMAGE1
File information for volume S00DIMAGE1:
{NOTE: 1 BLOCK = 512 BYTES }
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
FILE NAME O R I O O O FILE MAX NUM OF FILE LAST
R E T P L L CODE REC RECORDS SIZE MOFIFY
G C O E D D LEN IN IN DATE
C N FILE BLOCKS
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
930215_CM I F 0 1020 6957 13914 930215
930215_MS I F 0 1020 176542 353084 930215
ERS35CG O V 0 120 761 511 930212
APX35CG 0 V 0 120 52 511 930212
FPX35CG 0 V 0 120 3296 1023 930216
LRC35CG 0 V 0 120 4384 1535 930216
LCC35CG 0 V 0 120 83 511 930215
ASN1UI$LD 0 V 0 120 37 511 930129
LRS35CD 0 V 0 120 493 511 920109
LPX35CG 0 F 0 120 80 511 930212
930212_CM 0 V 0 120 6908 13914 930212
930212_MS 0 V 0 120 174029 353084 920212
6 Determine if a registered CM image file exists in the ITOC for SLM 0.

Note: The letter Y under the ITOC header confirms the file in the ITOC is
registered. The area is blank if a registered file does not exist. The MAP
response in step 5 does not contain an MS or CM image file in the ITOC.
If a CM image file Do
is registered step 9
is not registered step 7
297-2651-543 Standard 05.01 March 1999

IOD ITOC
7 Record the file name of the current CM image file.

Note: In the MAP response in step 5, the current CM image file is 930215_CM.
8 To add the current CM image file to the ITOC for SLM 0, type
>SETBOOTFL disk_volume_name file_name CM 1 ACTIVE
where
disk_volume_name is the disk and volume name specified in step 5
file_name is the name of the current CM image file
Example input:
>SETBOOTFL S00DIMAGE1 930215_CM CM 1 ACTIVE
File 930215_CM in volume S00DIMAGE1 has been
registered in the Image Table Of Contents for CM on
SLM, unit 0 as entry number 1.
It is also registered as the active boot file.
9 Determine if a registered MS image file exists in the ITOC for SLM 0.
registered step 12
did not register step 10
10 Record the file name of the current MS image file.

Note: In the example of a MAP response in step 5, the current MS image file is
930215_MS.
GSP05 (CSP10)
IOD ITOC
11 To add the current MS image file to the ITOC for SLM 0, type
>SETBOOTFL disk_volume_name file_name MS 1 ACTIVE
where
file_name is the name of the current MS image file
Example input:
>SETBOOTFL S00DIMAGE1 930215_MS MS 1 ACTIVE
registered in the Image Table Of Contents for CM
on SLM, unit 0 as entry number 1.
297-2651-543 Standard 05.01 March 1999

IOD ITOC
12 To list the file information for the image volume on the disk of SLM 1, type
where
disk_volume_name is the name of the disk of SLM 1 (S01D) and the name of
the volume on S01D that contains the CM and MS image
files
Example input:
>LISTFL S01DIMAGE1
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
C N FILE BLOCKS
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
930215_CM I F 0 1020 6957 13914 930215
930215_MS I F 0 1020 176542 353084 930215
ERS35CG O V 0 120 761 511 930212
APX35CG 0 V 0 120 52 511 930212
FPX35CG 0 V 0 120 3296 1023 930216
LRC35CG 0 V 0 120 4384 1535 930216
LCC35CG 0 V 0 120 83 511 930215
ASN1UI$LD 0 V 0 120 37 511 930129
LRS35CD 0 V 0 120 493 511 920109
LPX35CG 0 F 0 120 80 511 930212
930212_CM 0 V 0 120 6908 13914 930212
930212_MS 0 V 0 120 174029 353084 920212
13 Determine if a registered CM image file exists in the ITOC for SLM 1.

Note: The MAP response in step 12 does not contain an MS or CM image file
in the ITOC.
registered step 16
did not register step 14
GSP05 (CSP10)
IOD ITOC
15 To add the current CM image file to the ITOC for SLM 1, type
where
Example input:
16 Determine if a MS image file is registered in the ITOC for SLM 1.
18 To add the current MS image file to the ITOC for SLM 1, type
where
Example input:
File 930215_MS in volume S01DIMAGE1 has been
registered in the Image Table Of Contents for
MS on SLM, unit 1 as entry number 1.
297-2651-543 Standard 05.01 March 1999

IOD ITOC
critical
critical
(continued)
(end)
19 Determine if the ITOC critical alarm did clear.
If the alarm Do
cleared step 21
GSP05 (CSP10)
IOD ITOC
minor
Alarm display
. . ITOC . . . . . . .
Indication
At the MTC level of the MAP display, ITOC appears under the IOD header
of the alarm banner. The ITOC indicates an image table of contents (ITOC)
minor alarm.
Meaning
Image files are registered in one of more computing module (CM) ITOC.
Image files are also registered in one message switch (MS) ITOC. One of
the two remaining ITOCs is empty.
Result
Common procedures
Action
the alarm.
297-2651-543 Standard 05.01 March 1999

IOD ITOC
minor (continued)
Summary of Clearing an IOD ITOC minor alarm

which ITOCs procedure.
are empty
Add image files procedure.
to ITOCs

End
GSP05 (CSP10)
IOD ITOC
minor (continued)
Clearing an IOD ITOC minor alarm
At the MAP terminal
1 To make sure that you are at the CI level of the MAP display, type
>QUIT ALL
2 To access the disk utility, type

>DISKUT
3 To list the volumes on the SLM disks, type

>LISTVOLS CM
Volumes found on the node CM:
–––––––––––––––––––––––––––––
NAME TYPE TOTAL FREE TOTAL OPEN ITOC LARGEST
BLOCKS BLOCKS FILES FILES FILES FREE SEGMENT
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
S00DIMAGE1 STD 614389 142554 28 0 0 81715
S00DPMLOADS STD 614389 137474 83 0 0 82386
S00DDLOG STD 8185 4995 49 0 0 586
S01DIMAGE1 STD 614389 29436 39 0 0 7320
S00DPMLOADS STD 51189 245 116 0 0 78
S01DDLOG STD 8185 597 15 0 0 134
Total number of volumes found on node CM : 6
4 Determine from office records the volumes that contain the CM and MS image
files (one image volume for each disk).
297-2651-543 Standard 05.01 March 1999

IOD ITOC
minor (continued)
where
disk_volume_name is the name of the disk of SLM 0 (S00D) and the
name of the volume on S00D that contains the CM
and MS image files
Example input:
>LISTFL S00DIMAGE
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
C N FILE BLOCKS
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
930215_CM I F 0 1020 6957 13914 930215
930215_MS I F 0 1020 176542 353084 930215
ERS35CG O V 0 120 761 511 930212
APX35CG 0 V 0 120 52 511 930212
FPX35CG 0 V 0 120 3296 1023 930216
LRC35CG 0 V 0 120 4384 1535 930216
LCC35CG 0 V 0 120 83 511 930215
ASN1UI$LD 0 V 0 120 37 511 930129
LRS35CD 0 V 0 120 493 511 920109
LPX35CG 0 F 0 120 80 511 930212
930212_CM 0 V 0 120 6908 13914 930212
930212_MS 0 V 0 120 174029 353084 920212
6 Determine the registration of a CM image file in the ITOC for SLM 0.

Note: The letter Y under the ITOC header means that the file is registered in
the ITOC. If the area is blank, a file that is registered is not present. In the
MAP response in step 5, there is no registered MS or CM image file registered
in the ITOC.
Status of a CM image file Do
registered step 10
not registered step 7
GSP05 (CSP10)
IOD ITOC
minor (continued)

Note: In the MAP response in step 5, the current CM image file is 930215_CM.
8 Add the current CM image file to the ITOC for SLM 0. Type
where
Example input:
9 Determine if the ITOC minor alarm cleared.
If the alarm Do
cleared step 24
10 Determine if an MS image file is registered in the ITOC for SLM 0.
Status of the MS image file Do
registered step 14
not registered step 11
297-2651-543 Standard 05.01 March 1999

IOD ITOC
minor (continued)
12 To add the latest MS image file to the ITOC for SLM 0, type
where
file_name is the name of the latest MS image file
Example input:
File 930215_MS in volume S00DIMAGE1 has been
registered in the Image Table Of Contents for MS on
SLM, unit 0 as entry number 1.
If the alarm Do
cleared step 24
GSP05 (CSP10)
IOD ITOC
minor (continued)
where
disk_volume_name is the name of the disk of SLM 1 (S01D) and the
name of the volume on S01D that contains the CM
and MS image files
Example input:
>LISTFL S01DIMAGE1
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
C N FILE BLOCKS
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
930215_CM I F 0 1020 6957 13914 930215
930215_MS I F 0 1020 176542 353084 930215
ERS35CG O V 0 120 761 511 930212
APX35CG 0 V 0 120 52 511 930212
FPX35CG 0 V 0 120 3296 1023 930216
LRC35CG 0 V 0 120 4384 1535 930216
LCC35CG 0 V 0 120 83 511 930215
ASN1UI$LD 0 V 0 120 37 511 930129
LRS35CD 0 V 0 120 493 511 920109
LPX35CG 0 F 0 120 80 511 930212
930212_CM 0 V 0 120 6908 13914 930212
930212_MS 0 V 0 120 174029 353084 920212
15 Determine if a CM image file is registered in the ITOC for SLM 1.

Note: In the MAP response in step 14, a registered CM and MS image file is
not in the ITOC.
If a file Do
297-2651-543 Standard 05.01 March 1999

IOD ITOC
minor (continued)
17 To add the latest CM image file to the ITOC for SLM 1, type
where
file_name is the name of the latest CM image file
Example input:
File 930215_CM in volume S01DIMAGE1 has been registered
in the Image Table Of Contents for CM on SLM, unit 1 as
entry number 1.
If the alarm Do
cleared step 24
19 Determine if an MS image file registered in the ITOC for SLM 1.
If a file Do
20 Record the file name of the latest MS image file.
GSP05 (CSP10)
IOD ITOC
minor (continued)
(end)
21 Add the latest MS image file to the ITOC for SLM 1. Type
where
Example input:
File 930215_MS in volume S01DIMAGE1 has been registered
in the Image Table Of Contents for MS on SLM, unit 1 as
entry number 1.
If the alarm Do
cleared step 24
297-2651-543 Standard 05.01 March 1999

IOD KEEPn
minor
Alarm display
. . KEEPn . . . . . . .
Indication
At the IOD level of the MAP display, KEEP followed by a number (n)
indicates a minor alarm for a keep file.
Meaning
Retain the file on a recording device in the office, following transmission to
a data center. The number that follows KEEP represents the number of the
recording device.
Result
Common procedures
There are no common procedures
Action
the alarm.
GSP05 (CSP10)
IOD KEEPn
minor (continued)
Summary of Clearing an IOD KEEPn minor alarm
Record file This flowchart summarizes the

number procedure.

procedure.
DMNT alarm N
present?
Use this
document to
clear alarm.
End
297-2651-543 Standard 05.01 March 1999

IOD KEEPn
minor
minor
(continued)
(end)
Clearing an IOD KEEPn minor alarm
At the MAP terminal
1 To access the XFER (transfer) level of the MAP display, type
>MAPCI;MTC;IOD;XFER
IOD
IOC 0 1 2 3
STAT . . . .
DIRP: . XFER: . DVI : . DPPP: . DPPU: .

NOP : . SLM : . NX25: . MLP : . SCAI: .
2 To record the number of the file that appears in the alarm, type
>KEPT file_no
where
file_no is the number of the file
If a DMNT alarm Do
appears step 3
does not appear step 4
3 Perform the procedure Clearing an IOD DMNTn minor alarm in this document
to clear this alarm. Complete the procedure and return to this point.
4 Determine if the KEEPn alarm cleared.
If the KEEPn alarm Do
cleared step 6
GSP05 (CSP10)
IOD MPCLNK
minor
Alarm display
. . MPCLNK . . . . . . .
Indication
At the IOD level of the MAP display, MPCLNK indicates a minor alarm for
a multiple protocol controller link on the input/output controller (IOC).
Meaning
One or more multiple protocol controller links are system busy.
Result
Loss of data can occur if the link becomes system busy during transmission.
Common procedures
Action
instructions in the step–action procedure that follows the flowchart to clear
the alarm.
297-2651-543 Standard 05.01 March 1999

IOD MPCLNK
minor (continued)
Summary of Clearing an IOD MPCLNK minor alarm on IOC

Post the MPC
procedure.

procedure.
Manually busy
and return the
link to service
Is the link in Y
service?
Manually busy
the links
Manually busy,
test, and return
MPC to service
Y Return the links

Passed? to service
Y
Passed?

level of support
GSP05 (CSP10)
IOD MPCLNK
minor (continued)
Clearing an IOD MPCLNK minor alarm
At the MAP Terminal
1 To access the IOD level of the MAP, type
>MAPCI;MTC;IOD
IOD
IOC 0 1 2 3
STAT . . . S

297-2651-543 Standard 05.01 March 1999

IOD MPCLNK
minor (continued)

>IOC ioc_no
where
Example of a IOC MAP display:
IOC CARD 0 1 2 3 4 5 6 7 8
0 PORT 0123 0123 0123 0123 0123 0123 0123 0123 0123
STAT .––– .––– ...P ..–– ..–– ––– ––– ––– –––

IOC PORT 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
(IOM) STAT . . . – . . – – – . – – – – – – – –
O O O O T P D C
N N N N D C U S
is IOC step 4
is IOM step 3
3 Perform the IOD MPCLNK on an IOM alarm clearing procedure for the
input/output module (IOM) in this document.
GSP05 (CSP10)
IOD MPCLNK
minor (continued)
4 To post the affected MPC card, type

>IOC ioc_no;CARD card_no
IOC CARD 0 1 2 3 4 5 6 7 8
0 PORT 0123 0123 0123 0123 0123 0123 0123 0123 0123
STAT .––– .––– ...P ..–– ..–– ––– ––– ––– –––
5 To make all the links on the affected MPC manually busy, type
>BSY LINKS
passed step 31
failed step 6
6 To make the MPC card manually busy, type

>BSY ALL Force

bsy
OK
297-2651-543 Standard 05.01 March 1999

IOD MPCLNK
minor (continued)
7 To test the MPC card, type

>TST
passed step 30
card list
failed, as a result of the following step 32
response that appeared at the MAP
terminal: REQUEST FAILED, MPC
LOGS MAY HAVE MORE INFO
8 Replace the multiprotocol controller card. Perform the correct procedure in

point.
9 To download the MPC binary file to the MPC card, type

>DOWNLD
If the DOWNLD command Do
passed step 30
failed, and the download file step 10
parameter was not specified
failed, and a background download step 32
to an MPC occurred
10 To determine the name of the binary file for the MPC card, type
>QMPC
GSP05 (CSP10)
IOD MPCLNK
minor (continued)
11 Determine from office records if the MPC binary file is on tape, IOC disk, or
SLM disk.
If the binary file Do
is on tape step 12
is on IOC disk step 18
is on SLM disk step 20
12 Obtain the tape that contains the MPC binary file and load the tape on an
available MTD tape.
13 To mount the tape, type

>MOUNT mtd_no
where
14 To verify that the MPC binary file is present, type

>LIST
If the tape Do
contains the MPC binary file step 17

does not contain the MPC binary file step 15

>DEMOUNT tape_name
where
16 Determine from office records the tape that contains the MPC binary file.
Go to step 12.
297-2651-543 Standard 05.01 March 1999

IOD MPCLNK
minor (continued)
17 To download the MPC binary file to the MPC card, type

>DOWNLD
passed step 30
failed step 32
18 Determine from office records the IOC disk volume that contains the MPC
binary file.
19 To verify that the MPC binary file is available on the IOC disk volume, type
>DISKUT;LIV vol_name ALL
where
vol_name is the name of the volume that contains the MPC binary file
20 Determine from office records the SLM disk volume that contains the MPC
binary file.
GSP05 (CSP10)
IOD MPCLNK
minor (continued)
21 To verify that the MPC binary file is available on the SLM disk volume, type
>DISKUT;LF vol_name
where
vol_name is the name of the volume that contains the MPC binary file
File information for volume S01DVOL1
{NOTE: 1 BLOCK = 512 BYTES}
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
LAST File O R I O FILE NUM OF MAX FILE NAME
MODIFY CODE R E T P SIZE RECORDS REC
DATE G C O E IN IN LEN
C N BLOCKS FILE
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
930325 0 I F Y 201570 100785 1020 MBCS34CR_CM
930325 0 I F Y 9754 4877 1020 MBCS34CR_MS
930326 0 I F Y 5334 2667 1020 LRC34CR
930226 0 O F Y 7460 3730 1024 ELI34CR
930326 0 O F Y 2396 1198 1024 EDH34CR
930319 0 I F Y 9104 4552 1020 LPX34CR
930319 0 I F Y 6634 3317 1020 NRS34CR
921204 0 I F Y 7284 3642 1020 XRX34CR
931206 0 O F Y 162 1504 55 LCME34U
921208 0 O F Y 1432 716 1024 DCH34CR
22 Determine from table PMLOADS if the data entries of the MPC binary file
contain the correct load device. Type
>TABLE PMLOADS;POSITION file_name;LIST
where
file_name is the name of the MPC binary file
297-2651-543 Standard 05.01 March 1999

IOD MPCLNK
minor (continued)
23 Determine if the MPC binary file data entries contain the correct load device.
If MPC binary file data entries Do
contain the correct load device step 30

do not contain the correct load step 24
device
can not find the tuple step 26
24 To change the device type to the correct load device, type

>CHANGE DEVICE dev_type vol_name
where
dev_type is an MTD, IOC disk, or SLM disk
vol_name is the name of the IOC volume or SLM disk volume
25 To confirm the tuple change, type

>Y
Go to step 17 in this procedure.
26 To add the MPC binary file to table PMLOADS, type

>ADD file_name dev_type vol_name
where
27 To confirm the addition, type

>Y
28 To quit table PMLOADS and the disk utility, type

>QUIT;QUIT
GSP05 (CSP10)
IOD MPCLNK
minor (continued)
(end)
29 To download the binary file to the MPC card, type

>DOWNLD
passed step 30
failed step 32
30 To return the MPC card to service, type

>RTS
passed step 31
failed step 32
failed, and part of the response step 32
included REQUEST FAILED, MPC
31 To return the MPC links to service, type

>RTS LINKS
passed step 33
failed step 32
297-2651-543 Standard 05.01 March 1999

IOD nCKEr
minor
Alarm display
. . 1CKEr . . . . . . .
Indication
At the MTC level of the MAP display, a number and CKEr appears under
the I/O device (IOD) header of the alarm banner. The CKEr indicates a
circuit error alarm in the input/out controller (IOC).
Meaning
The disconnetion of a minimum of one IOD occurs. The number preceding
CKEr is the number of disconnected IODs.
You can disable the CKEr alarm for a disconnected IOD. To disable the
IOD, change the entry for the device in field CKERDISC in table
TERMDEV to N. For additional information, refer to the description of
table TERMDEV in the Data Schema section of Translations Guide.
Result
The system generates the CKEr alarm for an IOD disconnected at the IOC.
Common procedures
Action
the alarm.
GSP05 (CSP10)
IOD nCKEr
minor (continued)
Summary of Clearing an IOD nCKEr minor alarm

procedure.

Console Y Reconnect procedure.
disconnected? console
Check for N
Contact next
disconnected level of
cables? support
Y
End
297-2651-543 Standard 05.01 March 1999

IOD nCKEr
minor (continued)
Clearing an IOD nCKEr minor alarm
At the MAP terminal
>MAPCI;MTC;IOD
IOD
IOC 0 1 2 3
STAT . . . S

GSP05 (CSP10)
IOD nCKEr
minor (continued)

>IOC ioc_no
where
IOC CARD 0 1 2 3 4 5 6 7 8
0 PORT 0123 0123 0123 0123 0123 0123 0123 0123 0123
STAT .––– .––– ...P ..–– ..–– ––– ––– ––– –––

IOC PORT 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
(IOM) STAT . . . – . . – – – . – – – – – – – –
O O O O T P D C
N N N N D C U S
is IOM step 3
is IOC step 4
3 Perform the IOD nCKEr on an IOM alarm clearing procedure for the
297-2651-543 Standard 05.01 March 1999

IOD nCKEr
minor (continued)
4 To display the state of the console devices, type

>LISTDEV CONS
MAP VT100 . 0.2
RD030 VT100 . 0.2
RD040 VT100 . 0.4
RD041 VT100 . 0.4
RP042 KSR Disc 0.4
RP061 KSR . 0.6
RV062 VT100 . 0.6
RV063 VT100 . 1.2
RD140 VT100 . 1.4
RD141 VT100 . 1.4
RP142 KSR . 1.4
RV160 VT100 . 1.6
RV163 VT100 . 1.6
RD045 VT100 . 2.0
RD046 VT100 . 2.0
RD050 VT100 . 2.0
RD051 VT100 . 2.0
RP200 VT100 . 2.1
RP203 VT100 . 2.1
RP205 VT100 . 2.2
RP206 VT100 . 3.0
RD31 VT100 . 3.0
RD32 VT100 . 3.1
RD33 VT100 . 3.1
RD34 VT100 . 3.1
RD35 VT100 . 3.1
RD36 VT100 . 3.2
5 Record the IOC number and card number for each console device that is in a
state of disconnection (Disc).
If Do
one IOC has disconnected console step 7

device
more than one IOC has step 6
GSP05 (CSP10)
IOD nCKEr
minor (continued)
6 Choose an IOC to work on.
7 To access the MAP display for the IOC, type

>IOC ioc_number
where
IOC CARD 0 1 2 3 4 5 6 7 8
0 PORT 0123 0123 0123 0123 0123 0123 0123 0123 0123
STAT .––– .––– ...P ..–– ..–– ––– ––– ––– –––
If you recorded Do
one card that associates with the step 9

IOC in step 5.
more than one card that associates step 8
with the IOC in step 5.
8 Choose a IOC terminal controller card to use.
9 To post the terminal controller card, type

>CARD card_no
where
card_no is the number of the terminal controller card (0 to 8)
Card 4 Ckt 0 1 2 3
Status . Disc . –
Cons Id RD040 RD041 RP042
ConType VT100 VT100 KSR
Note: Identify disconnected circuits (links) by a state of Disc in the status field.
297-2651-543 Standard 05.01 March 1999

IOD nCKEr
minor (continued)
At the back of IOC shelf
10 Locate the terminal controller card. Determine if disconnection of any of the
cables to the associated console device occurred.
If disconnection occurs for Do
a minimum of one cable step 11

no cables step 16

Note: Connection of the associated console device can occur at the remote
end with an RS232 connector. In this condition, make sure the connector is
seated correctly.
At the MAP terminal

12 From the MAP display for the posted terminal controller card, determine the
state of the links you reconnected.
If Do
all links are in service (.) step 13

a minimum of one link is not in step 16
service
13 Determine if other IOCs with disconnected console devices exist.

If other IOCs with disconnected

console devices Do
exist step 6
do not exist step 14
GSP05 (CSP10)
IOD nCKEr
minor (continued)
(end)
If the alarm Do
cleared step 17
15 Perform the correct procedure in this document to clear the alarm.
297-2651-543 Standard 05.01 March 1999

IOD nCKEr on an IOM

minor
Alarm display
. . 1CKEr. . . . . . . .
Indication
At the MTC level of the MAP display, CKEr preceded by a number appears
under the IOD header of the alarm banner, and indicates a circuit error alarm
in the input/output module (IOM).
Meaning
One or more I/O devices is disconnected. The number preceding CKEr is
the number I/O that are disconnected.
The CkEr alarm for a disconnected an I/O device on an IOM can be disabled
by changing the datafill for the device in field CKERDISC in table
TERMDEV to N. For additional information refer to the description of table
TERMDEV in the Data Schema section of Translations Guide.
If the port is connected to a modem that is currently idle, the disconnected

status is normal. The alarm may be disabled in the field CKERDISC in
table TERMDEV to N.
Impact
The CKEr alarm is generated for an I/O device disconnected at the
Common procedures
Not applicable
Action
the alarm.
GSP05 (CSP10)
IOD nCKEr on an IOM

minor (continued)
Summary of Clearing an IOD nCKEr on an IOM minor alarm

procedure.
Console Y Post, bsy and Use the instructions in the

disconnected? offline IOM port procedure that follows this
procedure.
N
2
Test IOM port
Smart Y Reconnect
connector connector 1
identified?
N
Check for N
disconnected 2
cables?
Y
Reconnect
cables
1
Check that N Contact next
links are in 2 level of
service? support
Y
End
297-2651-543 Standard 05.01 March 1999

IOD nCKEr on an IOM

minor (continued)
Clearing a/an IOD nCKEr on an IOM alarm
At the MAP terminal
>MAPCI;MTC;IOD
IOD
IOC 0 1 2 3
STAT . . . S

GSP05 (CSP10)
IOD nCKEr on an IOM

minor (continued)
2 Display the state of the console devices by typing

>LISTDEV CONS
MAP VT100 . 0.2
RD030 VT100 . 0.2
RD040 VT100 . 0.4
RD041 VT100 . 0.4
RP042 KSR Disc 0.4
RP061 KSR . 0.6
RV062 VT100 . 0.6
RV063 VT100 . 1.2
RD140 VT100 . 1.4
RD141 VT100 . 1.4
RP142 KSR . 1.4
RV160 VT100 . 1.6
RV163 VT100 . 1.6
RD045 VT100 . 2.0
RD046 VT100 . 2.0
RD050 VT100 . 2.0
RD051 VT100 . 2.0
RP200 VT100 . 2.1
RP203 VT100 . 2.1
RP205 VT100 . 2.2
RP206 VT100 . 3.0
RD31 VT100 . 3.0
RD32 VT100 . 3.1
RD33 VT100 . 3.1
RD34 VT100 . 3.1
RD35 VT100 . 3.1
RD36 VT100 . 3.2
3 Record the IOM number and port number for each console device with a state
of Disc (disconnected).
If Do
one IOM has disconnected console step 5

device
more than one IOM has step 4
297-2651-543 Standard 05.01 March 1999

IOD nCKEr on an IOM

minor (continued)
4 Choose an IOM to work on.

>IOC ioc_no
where
IOC PORT 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
(IOM) STAT . . . – . . – – – . – – – – – – – –
O O O O T P D C
N N N N D C U S
If Do
one port associated with the IOM step 7

was recorded in step 3.
more than one port associated with step 6
the IOM was recorded in step 3.
6 Choose a IOM port to work on.
GSP05 (CSP10)
IOD nCKEr on an IOM

minor (continued)
7 Post the terminal controller port by typing

>PORT port_no
where
port_no is the port number of the terminal controller device (0 to 15)

Port 2 Status Disc
Cons Id 1CONS
ConType VT100
Note: Disconnected circuits (links) are identified by a state of Disc in the status
field.
8 Busy the console by typing

>BSY
bsy
OK
9 Offline the console by typing

>OFFL

>QUIT

>BSY PORT port_no
bsy
OK
297-2651-543 Standard 05.01 March 1999

IOD nCKEr on an IOM

minor (continued)
12 Offline the IOM controller port by typing

>OFFL PORT port_no
13 Test the IOM controller port by typing

>TST PORT port_no
where
port_no is the number of the port
Failed
Check and replace smart connector for port 5 (FX36)
identified step 14
GSP05 (CSP10)
IOD nCKEr on an IOM

minor (continued)
At the back of ISM shelf
14
WARNING
Locate the smart cable connecting the CONS port identified in the MAP
response in step 13 and reconnect the RS232 smart connector.
Go to step 17.
15 Locate the console cables between the console port on the paddleboard at the
backplane and the RS232 smart connectors at the associated console device
and determine if they are disconnected.
Note: In the case of a cabinetized ISM (CISM), the cables from the controller
paddleboard are connected to a splitter unit on the ISM bulkhead. Other cables
connect the splitter unit to the associated console device through RS232 smart
connectors.
If Do
one or more cables is disconnected step16

no cables are disconnected step 26

Note: If the associated console device is connected at the remote end with an
RS232 smart connector, ensure that the connector is properly seated.
At the MAP terminal

>BSY PORT port_no
297-2651-543 Standard 05.01 March 1999

IOD nCKEr on an IOM

minor (continued)
18 Return the IOM controller port to service by typing

>RTS PORT port_no
passed step 19
failed step 26
19 Post the terminal port by typing

>PORT port_no
20 Busy the terminal by typing

>BSY
bsy
OK
GSP05 (CSP10)
IOD nCKEr on an IOM

minor (continued)
(end)
21 Return the terminal to service by typing

>RTS
22 From the MAP display for the posted IOM, determine the state of the links you
reconnected.
If Do
the state of all links is in service (.) step 23

one or more links is not in service step 26
23 Determine if there are other IOMs with disconnected console devices.

If there are Do
other IOMs with disconnected step 4

console devices
no other IOMs with disconnected step 24
console devices
If the alarm Do
cleared step 27
support.
297-2651-543 Standard 05.01 March 1999

IOD nCKOS
major or minor
Alarm display
. . nCKOS . . . . . . .
Indication
At the IOD level of the MAP display, a number (n) precedes CKOS. CKOS
indicates a major or minor circuit out-of-service alarm.
Meaning
One or more circuits or ports are out of service. The number that precedes
CKOS indicates the number of circuits or ports that are out of service. The
circuit controls one of the four ports on the IOC controller card. Each of
these ports connects to a terminal (for example, a MAP terminal or a
printer).
Result
Service stops to any device associated with an out-of-service circuit or port.
Common procedures
Action
GSP05 (CSP10)
IOD nCKOS
Summary of Clearing an IOD nCKOS major or minor alarm on an IOC
Check circuit This flowchart summarizes the

status of procedure.
consoles
N N procedure.
Status C? Status P? 1
Y Y
5
N
MS alarm? 5
Y
Clear alarm.
Refer to correct
NTP.
N
Is controller 2
IOC?
Select and
manually busy a
circuit
Test circuit
1
Return circuit to N End
service Passed? 2
1 Y
297-2651-543 Standard 05.01 March 1999

IOD nCKOS
Clearing an IOD nCKOS major or minor alarm
At the MAP terminal
>MAPCI;MTC;IOD

IOD
IOC 0 1 2 3
STAT . . . S

2 Determine if an audible alarm is present.
is present step 3

>SIL
GSP05 (CSP10)
IOD nCKOS

>IOC ioc_no
where
IOC CARD 0 1 2 3 4 5 6 7 8
0 PORT 0123 0123 0123 0123 0123 0123 0123 0123 0123
STAT .––– .––– ...P ..–– ..–– ––– ––– ––– –––

IOC PORT 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
(IOM) STAT . . . – . . – – – . – – – – – – – –
O O O O T P C C
N N N N D C S S
is IOM step 5
is IOC step 6
5 Perform the IOD nCKOS on an IOM alarm clearing procedure for the
297-2651-543 Standard 05.01 March 1999

IOD nCKOS
If the port status Do

is P (P-side busy) step 10
7 The C-side links to the console are out of service. Determine if an alarm exists
under the MS header.
is present step 8
8 Perform the correct procedure in this document to clear the alarm. Complete
9 Determine from the MAP display if the alarm under the MS header cleared.
If the alarm Do
cleared step 10
10 List the console cards that have P status.
If the P status Do
affects one card (IOC) step 12

affects more than one card step 11
11 From the list you recorded in step 10, choose one console card to work on.
GSP05 (CSP10)
IOD nCKOS
12 To post the affected IOC console card, type

>CARD card_no
where
card_no is the number of the affected console card
Card 1 Unit 0
User system Drive_State
Status Ready on_line
If the port status Do
is SYSb step 13
is OFFL step 28
is ManB step 29
13 List the IOC circuits that are system busy.
If Do
one circuit is busy step 15

more than one circuit are system step 14
busy
14 From the list, choose one circuit to work on.
297-2651-543 Standard 05.01 March 1999

IOD nCKOS
15 To make the IOC circuit manually busy, type

>BSY circuit_no
where
bsy
OK
16 To test the circuit, type

>TST circuit_no
where
passed step 30
card list
failed, and the system did not step
and PEC suffix of the cards on the card list.
18 Perform the correct procedure in Card Replacement Procedure.to replace the

card. Complete the procedure and return to this point.
GSP05 (CSP10)
IOD nCKOS

>TST circuit_no
where
passed step 30
card list

next card. Complete the procedure and return to this point.
21 Go to step 19.
24 Check the console to make sure that that the console runs correctly and does
not have problems.
297-2651-543 Standard 05.01 March 1999

IOD nCKOS
Switch Setting
Power ON
Local/Online Online
Parity No Parity
If the external switch settings Do
are correct step 27

are not correct step 26
26 Change the external switch setting according to the table in step 25. Complete

>TST circuit_no
where
passed step 30
failed step 32

that the circuit is offline. If you have permission, manually busy the circuit. To
manually busy the circuit, type
>BSY circuit_no
where
GSP05 (CSP10)
IOD nCKOS
29 To test the manually–busy circuit, type

>TST circuit_no
where
passed step 30
card list
30 To return the circuit to service, type

>RTS circuit_no
where
passed, and all circuits are in step 31

service
passed, and one or more circuits step 12
are out of service
failed step 32
297-2651-543 Standard 05.01 March 1999

IOD nCKOS
majormajor
or minor
or minor
(continued)
(end)
31 Determine from the MAP display if the nCKOS major or minor alarm cleared.
If the alarm Do
cleared step 33
did not clear, and other consoles are step 6
out of service
service
GSP05 (CSP10)
IOD nDDUOS
major or minor
Alarm display
. . nDDUOS . . . . . . .
Indication
At the IOD level of the MAP display, DDUOS [preceded by a number (n)]
indicates a DDU major or minor alarm.
Meaning
One or more disk drive units (DDU) are out of service. The number that
precedes DDUOS indicates the number DDUs out of service.
Result
You cannot record files to the tape or DDU. You cannot download files
from the tape or DDU.
Common procedures
Action
297-2651-543 Standard 05.01 March 1999

IOD nDDUOS
Summary of Clearing an IOD nDDUOS major or minor alarm

status of the procedure.
DDU
procedure.
N Is the DDU N
Is the DDU
status
SBsy?
––––?
Y
3
Y
Determine the Is the DDU N
DDU drive state status OffL or 3
ManB?
Y
Post and busy Post the DDU When possible,

the DDU return the DDU
to service
2
Test the DDU N
Failed with a N Y
3 Passed?
card list?
1 3
Y
Return the DDU Replace cards.
to service Refer to correct
NTP.
N Return DDU to
Passed? 2 service
1 Y 3
End N Contact next

Y
Passed? level of support
1 3
GSP05 (CSP10)
IOD nDDUOS
Clearing an IOD nDDUOS major or minor alarm
At the MAP terminal
>MAPCI;MTC;IOD
Example of a MAP:
IOD
IOC 0 1 2 3
STAT . . . S

2 Determine if an audible alarm is present.
is present step 3

>SIL
4 Determine if there is an FSP alarm under the EXT header of the MAP display.
present step 5
not present step 7
have completed the procedure, return to this point.
297-2651-543 Standard 05.01 March 1999

IOD nDDUOS
6 Determine if the DDUOS alarm under the IOD header of the MAP display has
cleared.
If the DDUOS alarm is Do
present step 7
not present step 74
GSP05 (CSP10)
IOD nDDUOS
7 To determine the configured controller system, type

>IOC ioc_no
where
ioc_no is the number of the affected IOC or input/output module (IOM)
IOD
IOC 0 1 2 3
STAT . . . S

IOC CARD 0 1 2 3 4 5 6 7 8
0 PORT 0123 0123 0123 0123 0123 0123 0123 0123 0123
STAT .––– .––– ...P ..–– ..–– ––– ––– ––– –––

IOD
IOC 0 1 2 3
STAT . . . S

IOC PORT 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
(IOM) STAT . . . – . . – – – . – – – – – – – –
O O O O T P D C
N N N N D C U S
is IOM step 8
is IOC step 9
8 Perform the IOD nDDUOS on an IOM alarm clearing procedure for the
297-2651-543 Standard 05.01 March 1999

IOD nDDUOS
9 To display the status of the DDU, type

>LISTDEV DDU
10 From the status display, determine the status of the DDU.
If the status Do
is SysB step 11
is _ _ _ _ _ step 73
is OffL or ManB step 61
11 Examine the drive state of the system busy DDU.
If the drive state Do
is ONLINE step 12
is DISCONNECTED step 4
has DRIVE FAULTS step 28
is SPINNING step 32
is SPINNING DOWN step 35
is SPUN DOWN step 43
is UNKNOWN step 52
12 To post the NT1X55 DDU controller card, type

where
card_no is the number of the DDU controller card
GSP05 (CSP10)
IOD nDDUOS
13 To make the DDU card manually busy, type

>BSY
bsy
OK
14 To test the DDU card, type

>TST
passed step 17
card list

17 To return the DDU device to service, type

>RTS
passed step 71
noted in step 15
297-2651-543 Standard 05.01 March 1999

IOD nDDUOS

19 Go to step 17.
20 Inspect the DDU cabling and power supply.
If the cables and power supply Do
are in good working order step 22

has faults step 21
21 Refer to office installation guides to replace the signal cabling to the DDU, or
adjust the power supply to the DDU. Complete this task and return to this point.
22 To test the DDU, type

>TST
passed step 25
card list
23 Record the location, description, slot number, PEC, and PEC suffix of the cards
on the card list.

GSP05 (CSP10)
IOD nDDUOS
25 To return the DDU to service, type

>RTS
passed step 71
noted in step 23

27 Go to step 25.
28 To post the NT1X55 DDU controller card, type

where
card_no is the card number
29 To make the NT1X55 DDU controller card manually busy, type

>BSY

bsy
OK

30 Perform the correct procedure in Routine Maintenance Procedures to clear the
optical sensors on the DDU. Complete the procedure and return to this point.
31 Go to step 20.
297-2651-543 Standard 05.01 March 1999

IOD nDDUOS
32 Wait 3 min for the DDU to spin up to speed.
If the status of the DDU Do
changes to ONLINE step 71

does not change to ONLINE step 33
33 Perform the correct procedure in Trouble locating and clearing procedures to

replace the DDU. Complete the procedure and return to this point.
34 Go to step 36.

that the DDU spins down. Wait 3 min for the spinning DDU to stop.
36 To return the DDU card to service, type

>IOC ioc_no;CARD card_no;RTS
where
card_no is the number of the DDU controller card
passed step 71
card list
37 Record the location, description, slot number, PEC, and PEC of the card(s) on
the card list.

GSP05 (CSP10)
IOD nDDUOS

>TST
passed step 42
noted in step 37

41 Go to step 39.

>RTS
passed step 71
failed step 73
43 To post and busy the DDU controller card, type

>IOC ioc_no;CARD card_no;BSY
where
bsy
OK
297-2651-543 Standard 05.01 March 1999

IOD nDDUOS
44 Determine from office records or from operating company personnel the reason
that the DDU was spun down.

>RTS
passed step 71
card list
on the card list.


>TST
passed step 51
noted in step 37

50 Go to step 48.
GSP05 (CSP10)
IOD nDDUOS

>RTS
passed step 71
failed step 73
52 To post the DDU controller card, type

where
53 To make the DDU controller card manually busy, type

>BSY
bsy
OK

>TST
passed step 60
card list
on the card list.
297-2651-543 Standard 05.01 March 1999

IOD nDDUOS


>TST
passed step 60
noted in step 55

59 Go to step 57.

>RTS
passed step 71
failed step 73
61 To post the DDU controller card, type

where
GSP05 (CSP10)
IOD nDDUOS
62 Determine from office records or from operating company personnel if the DDU
is offline or manual busy.
If the DDU Do
is offline step 63
is manual busy step 64
63 To make the DDU manually busy, type

>BSY
bsy
OK

>RTS
passed step 71
card list
on the card list.

297-2651-543 Standard 05.01 March 1999

IOD nDDUOS

>TST
passed step 70
noted in step 65

69 Go to step 67.

>RTS
passed step 71
failed step 73
71 Check under the IOD banner on your MAP display to determine if the nDDUOS
If the nDDUOS alarm Do
cleared step 74
the procedure and go to step 71.
GSP05 (CSP10)
IOD nDDUOS
(end)
297-2651-543 Standard 05.01 March 1999

IOD nDPCOS
minor
Alarm display
. . nDPCOS . . . . . . .
Indication
At the IOD level of the MAP display, a number (N) precedes DPCOS and
indicates a DATAPAC controller alarm.
Meaning
One or more DATAPAC controllers are out of service. The number that
precedes DPCOS indicates how many DATAPAC controllers are out of
service.
Result
Data cannot transfer to and from the IOC shelf.
Common procedures
Action
the alarm.
GSP05 (CSP10)
IOD nDPCOS
minor (continued)
Summary of Clearing an IOD nDPCOS minor alarm

procedure.
Post and busy
DATAPAC card Use the instructions that follow
procedure.
Test card
N Replace card. Test card N

Passed? Refer to correct Passed? 2
the NTP.
Y Y
Return card to 1
service
N Test DATAPAC N Test network

Passed? link Passed? connection
1 Y 1 Y
End N
Passed? 2
11 Y
Contact next
level of support
297-2651-543 Standard 05.01 March 1999

IOD nDPCOS
minor (continued)
Clearing an IOD nDPCOS minor alarm
At the MAP terminal
>MAPC;MTC;IOD
Example of a MAP:
IOD
IOC 0 1 2 3
STAT . . . .
DIRP: . XFER: . DVI : . DPPP: . DPPU: .
NOP : . SLM : . NX25: . MLP: . SCAI:
is present step 3

>SIL
4 To display the status of the affected DATAPAC card, type

>LISTDEV dpac
where
dpac is the number of the DATAPAC card
5 From the status display, determine the affected IOC number and DATAPAC
controller card number.
6 To post the NT1X67 DATAPAC controller card, type

>IOC ioc_no; CARD card_no
where
card_no is the number of the affected controller card
GSP05 (CSP10)
IOD nDPCOS
minor (continued)
7 To manually busy the affected NT1X67 DATAPAC controller card, type

>BSY
8 To test the NT1X67 DATAPAC controller card, type

>TST
passed step 9
failed, and a card list generated step 10
failed, and a card list did not step 17
generate
9 To return the NT1X67 DATAPAC controller card to service, type

>RTS
passed step 15
failed step 13
10 Replace the NTX167 DATAPAC controller card. Perform the correct procedure
point.
11 To test the new NT1X67 DATAPAC controller card, type

>TST
passed step 12
failed step 17
297-2651-543 Standard 05.01 March 1999

IOD nDPCOS
minor (continued)
12 To return the NT1X67 DATAPAC controller card to service, type

>RTS
passed step 15
failed step 13
13 To test the DATAPAC link, type

>DISC;DISC;DISC
If the test Do
passed step 15
failed step 14
14 To test the network connection, type

>CON node chan
where
node is the number of the switch within the DATAPAC network
chan is the DATAPAC virtual channel
If the test Do
passed step 15
failed step 17
GSP05 (CSP10)
IOD nDPCOS
minor (continued)
(end)
15 Check under the IOD banner on your MAP display to determine if the nDPCOS
minor alarm cleared.
If the alarm Do
cleared step 18
297-2651-543 Standard 05.01 March 1999

IOD nIOCOS
major or minor
Alarm display
. . nIOCOS . . . . . . .
Indication
At the IOD level of the MAP display, a number (n) and IOCOS indicate an
IOCOS major or minor alarm.
Meaning
More than one input/output controllers (IOCs) are out of service. The
number that precedes IOCOS indicates the number of IOCs out of service.
Result
All devices associated with the IOC that is out of service lost
communication with the switch.
Common procedures
Action
GSP05 (CSP10)
IOD nIOCOS
Summary of Clearing an IOD nIOCOS major or minor alarm

procedure.

Determine the flowchart to perform the procedure.
status of the
IOC
N N Is the IOC N
Is the IOC Is the IOC
status S? status O 3
status C?
or M?
Y Y Y
Manually busy Clear alarm. When possible,

the IOC Refer to correct return the IOC
NTP. to service
2
Test the IOC Return the IOC
to service
Replace cards.
N
Refer to correct Passed? 3
NTP.
Y
1
Return the IOC
to service
N
Contact next
Passed? 2 level of support
1 Y
End
297-2651-543 Standard 05.01 March 1999

IOD nIOCOS
Clearing an IOD nIOCOS major or minor alarm
At the MAP terminal
>MAPCI;MTC;IOD
IOD
IOC 0 1 2 3
STAT . . . S

2 Determine if the audible alarm is present.
If the audible alarm Do
is present step 3

>SIL
GSP05 (CSP10)
IOD nIOCOS

>IOC ioc_no
where
IOD
IOC 0 1 2 3
STAT . . . S

IOC CARD 0 1 2 3 4 5 6 7 8
0 PORT 0123 0123 0123 0123 0123 0123 0123 0123 0123
STAT .––– .––– ...P ..–– ..–– ––– ––– ––– –––

IOD
IOC 0 1 2 3
STAT . . . S

IOC PORT 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
(IOM) STAT . . . – . . – – – . – – – – – – – –
O O O O T P D C
N N N N D C U S
is IOC step 6
is IOM step 5
5 Perform the IOD nIOCOS on an IOM alarm clearing procedure for the
297-2651-543 Standard 05.01 March 1999

IOD nIOCOS
6 Determine the status of the affected IOC.
If the status Do
is S (system busy) step 7

is O (offline) or M (manual busy) step 22
7 To make the affected IOC manually busy, type

>IOC ioc_no;BSY IOC
where
bsy
OK

8 Check to see if the fault indicator lamp is lit on the power converter cards.
If the fault indicator lamp Do
is lit step 9
is not lit step 10

power converter cards. Complete the procedure and return to this point.
GSP05 (CSP10)
IOD nIOCOS
10 To test the IOC, type

>TST IOC
passed step 14
card list
At the MAP terminal
>TST IOC
passed step 14
noted in step 11
297-2651-543 Standard 05.01 March 1999

IOD nIOCOS
14 To return the IOC to service, type

>RTS IOC
passed step 23
failed step 25

At the MAP terminal
>IOC ioc_no;TST IOC
where
passed step 20
cards in the list recorded in step 11
failed, and you replaced all cards in step 18
the list recorded in step 11

next card on the list. Complete the procedure and go to step 16.
18 Check the output voltages on the power converter card. If the voltages are not
correct, adjust the voltages.
GSP05 (CSP10)
IOD nIOCOS
At the MAP terminal
>TST IOC
passed step 20
failed step 25
20 To start the IOC again, type

>RTS IOC
passed step 23
failed step 25
22 Consult office logs or operating company personnel. Determine the reason that
the IOC is offline or manually busy. To return the IOC to service, type
>IOC ioc_no;RTS IOC
where
passed step 23
failed step 25
297-2651-543 Standard 05.01 March 1999

IOD nIOCOS
majormajor
or minor
or minor
(continued)
(end)
23 Check under the IOD banner on your MAP display to determine if the nIOCOS
If the alarm Do
cleared step 26
GSP05 (CSP10)
IOD nMPCOS in an IOC

major or minor
Alarm display
. . nMPCOS . . . . . . .
Indication
At the IOD level of the MAP display, MPCOS preceded by a number (n)
indicates a multiple protocol controller major or minor alarm.
Meaning
One or more multiple protocol controllers or ports are out of service. The
number that precedes MPCOS indicates the number of input/ouput
controller (IOC) multiple protocol controllers or input/output module(IOM)
controller ports that are out of service.
Impact
Multiple controller cards on the IOC shelf or ports on the IOM controller on
the integrated service module (ISM) are out of service. Access to the switch
by remote terminals is lost for any affected cards or ports.
Common procedures
Not applicable
Action
the alarm.
297-2651-543 Standard 05.01 March 1999


Summary of Clearing an IOD nMPCOS in an IOC major or minor alarm in an IOC

procedure.
Display the
status of MPC Use the instructions in the procedure
card that follows this flowchart to perform
the procedure.
Is the MPC N Is the MPC N Is the MPC N

status CBsy or status OffL? status ManB? 2
SysB?
Y Y Y
1
Post and manually When possible,
busy the MPC busy the MPC
card and links card and links
1
Test the MPC
card
N
Passed? 2
1 Y
Return the MPC

card and links to
service
N Contact next
End
GSP05 (CSP10)

Clearing an IOD nMPCOS in an IOC major or minor alarm
At the MAP
>MAPCI;MTC;IOD
IOD
IOC 0 1 2 3
STAT . . . S

exists step 3

>SIL
297-2651-543 Standard 05.01 March 1999



>IOC ioc_no
where
IOC CARD 0 1 2 3 4 5 6 7 8
0 PORT 0123 0123 0123 0123 0123 0123 0123 0123 0123
STAT .––– .––– ...P ..–– ..–– ––– ––– ––– –––

IOC PORT 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
(IOM) STAT . . . – . . – – – . – – – – – – – –
O O O O T P D C
N N N N D C U S
If the controller is an Do
IOC step 6
IOM step 5
5 Perform the IOD nMPCOS on an IOM alarm clearing procedure for the
6 Display the status of the multiprotocol controller (MPC) card that has one or
more P-side busy ports by typing
>IOC ioc_no;LISTDEV MPC
where
GSP05 (CSP10)

7 From the MAP display, determine the status of the MPC card.
If the status is Do
CBusy (C-side busy) or step 8

SysB (system busy)
OffL (offline) step 36
ManB (manual busy) step 39
8 Post the affected MPC card by typing

>CARD card_no
where
Card 1 Unit 0
9 Manually busy all the links on the affected MPC card by typing
>BSY LINKS
passed step 11
failed step 10
297-2651-543 Standard 05.01 March 1999


10 The MPC ports are being used by other users. Instruct all users to log off, and
when they are logged off, attempt to manually busy the MPC links again by
typing
>BSY LINKS
passed step 11
failed, and all users have logged off step 44
11 Manually busy the affected MPC card by typing

>BSY

bsy
OK
12 Test the MPC card by typing

>TST
passed step 40
failed, because the following step 44
response appeared at the MAP
display: REQUEST FAILED, MPC
13 Replace the NT1X89 multiprotocol controller card by performing the appropriate

procedure in Card Replacement Procedures. When you have completed the
GSP05 (CSP10)

14 Download the MPC binary file to the MPC card by typing

>DOWNLD
passed step 40
failed, and the download file step 15
parameter was not specified
failed, and a background download step 44
to an MPC RTS occurred
15 Determine the name of the binary file for the MPC card by typing
>QMPC
16 Determine from office records whether the MPC binary file is on tape, IOC disk
or SLM disk.
If the binary file is on Do
tape step 17
IOC disk step 23
SLM disk step 25
17 Obtain the tape containing the MPC binary file and load the tape on an
available MTD.
18 Mount the tape by typing

>MOUNT mtd_no
where
297-2651-543 Standard 05.01 March 1999


19 Verify that the MPC binary file is present by typing

>LIST
If the tape Do
contains the MPC binary file step 22

does not contain the MPC binary file step 20
20 Demount the tape by typing

>DEMOUNT tape_name
where
21 Determine from office records which tape contains the MPC binary file.
Return to step 17.
22 Download the MPC binary file to the MPC card or IOM port by typing
>DOWNLD
passed step 40
failed step 44
23 Determine from office records which IOC disk volume contains the MPC binary
file.
GSP05 (CSP10)

24 Verify that the MPC binary file is available on the IOC disk volume by typing
>DSKUT;LIV vol_name ALL
where
vol_name is the name of the volume containing the MPC binary file
If the binary file is Do
available step 27
25 Determine from office records which SLM disk volume contains the MPC binary
file.
297-2651-543 Standard 05.01 March 1999


26 Verify that the MPC binary file is available on the SLM disk volume by typing
>DISKUT;LF vol_name
where
vol_name is the name of the volume containing the MPC binary file
File information for volume S01DVOL1
{NOTE: 1 BLOCK = 512 BYTES}
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
LAST File O R I O FILE NUM OF MAX FILE NAME
MODIFY CODE R E T P SIZE RECORDS REC
DATE G C O E IN IN LEN
C N BLOCKS FILE
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
930325 0 I F Y 201570 100785 1020 MBCS34CR_CM
930325 0 I F Y 9754 4877 1020 MBCS34CR_MS
930326 0 I F Y 5334 2667 1020 LRC34CR
930226 0 O F Y 7460 3730 1024 ELI34CR
930326 0 O F Y 2396 1198 1024 EDH34CR
930319 0 I F Y 9104 4552 1020 LPX34CR
930319 0 I F Y 6634 3317 1020 NRS34CR
921204 0 I F Y 7284 3642 1020 XRX34CR
931206 0 O F Y 162 1504 55 LCME34U
921208 0 O F Y 1432 716 1024 DCH34CR
If the binary file is Do
available step 27
27 Check table PMLOADS to verify that the MPC binary file has been datafilled
with the correct load device by typing
>TABLE PMLOADS;POSITION file_name;LIST
where
GSP05 (CSP10)

28 Determine if the MPC binary file has been datafilled correctly with the proper
load device.
If the MPC binary file has Do
been datafilled with the correct load step 35

device
not been datafilled with the correct step 29
load device
you cannot find the tuple step 32
29 Change the device type to the correct load device by typing

>CHANGE DEVICE dev_type vol_name
where
30 Confirm the tuple change by typing

>Y
31 Go to step 35.
32 Add the MPC binary file to table PMLOADS by typing

>ADD file_name dev_type vol_name
where
33 Confirm the addition by typing

>Y
34 Quit table PMLOADS and the disk utility by typing

>QUIT;QUIT
297-2651-543 Standard 05.01 March 1999


35 Download the binary file to the MPC card by typing

>DOWNLD
passed step 40
failed step 44
36 Post the affected MPC card by typing

>CARD card_no
where
Card 1 Unit 0
37 Determine from office records or office personnel why the MPC card is offline.
When permissible, manually busy the MPC card by typing
>BSY
38 Manually busy the MPC links by typing

>BSY LINKS
Go to step 40.
GSP05 (CSP10)

39 Determine from office records or from office personnel why the MPC card is
manually busy, and when permissible post the MPC card by typing
>CARD card_no
where
card_no is the number of the busied card
Card 1 Unit 0
40 Return the MPC card to service by typing

>RTS
passed step 41
failed step 44
failed, and part of the MAP display step 44
was REQUEST FAILED, MPC
41 Return the MPC links to service by typing

>RTS LINKS
If the RTS LINKS command Do
passed step 45
failed step 44
297-2651-543 Standard 05.01 March 1999


majormajor
or minor
or minor
(continued)
(end)
42 Check under the IOD banner of the MAP display to determine if the nMPCOS
If the alarm Do
cleared step 45
have completed the procedure, go to step 42.
support.
GSP05 (CSP10)
IOD nMTDOS in an IOC

minor
Alarm display
. . nMTDOS . . . . . . .
Indication
At the IOD level of the MAP display, MTDOS preceded by a number (n)
indicates a magnetic tape drive (MTD) or digital audio tape (DAT) minor
alarm.
Meaning
One or more tape drives or digital audio tapes are out of service. The
number that precedes MTDOS indicates how many MTDs or DATs are out
of service.
Impact
If the MTD or DAT is being used by the DIRP utility for recording billing
data, then the billing data is lost. If the MTD or DAT is not being used by
the DIRP utility, no files can be downloaded or recorded to or from tape.
Common procedures
Not applicable
Action
the alarm.
297-2651-543 Standard 05.01 March 1999


minor (continued)
Summary of Clearing an IOD nMTDOS in an IOC minor alarm
This flowchart summarizes the procedure.
Determine the Use the instructions in the procedure that

status of the follows this flowchart to perform the
MTD procedure.
N Is the MTD N Is the MTD N

Is the MTD 2
system busy? CBsy? OffL or ManB?
Y Y Y
Post and Display IOC When possible,

manually busy status return the MTD
the MTD to service
Mount a tape. Clear any N

Refer to alarms Passed? 2
appropriate NTP.
Y
Replace cards. 1
Did alarms N
Refer to clear? 2
appropriate NTP.
Y
Return MTD to 1
service
N
Contact next
1 Y
End
GSP05 (CSP10)

minor (continued)
Clearing an IOD nMTDOS in an IOC minor alarm
At the MAP terminal
>MAPCI;MTC;IOD
IOD
IOC 0 1 2 3
STAT . . . .
DIRP: . XFER: . DVI : . DPPP: . DPPU:
NOP : . SLM : . NX25: . MLP : . SCAI:
If the alarm Do
exists step 3

>SIL
4 Display the status of all the magnetic tape drives (MTD) by typing
>LISTDEV MTD
5 From the status display, determine the status of the MTD.
If the status is Do
SysB (system busy) step 6

CBsy (C-side busy) step 27
OffL (offline) or step 31
ManB (manual busy)
297-2651-543 Standard 05.01 March 1999


minor (continued)
6 Post the IOC connected to the MTD by typing

>IOC ioc_no
where
IOC CARD 0 1 2 3 4 5 6 7 8
0 PORT 0123 0123 0123 0123 0123 0123 0123 0123 0123
STAT .––– .––– ...P ..–– ..–– ––– ––– ––– –––

IOC PORT 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
(IOM) STAT . . . – . . – – – . – – – – – – – –
O O O O T P D C
N N N N D C U S
If the device is Do
MTD (IOC) step 8

MTD (IOM) step 7
DAT (IOM) step 7
7 Perform the IOD nMTDOS on an IOM alarm clearing procedure for the
GSP05 (CSP10)

minor (continued)
8 Post the affected MTD by typing

>CARD card_no
where
card_no is the number of the affected card
Card 1 Unit 0
9 Ensure that the MTD is demounted.
If the MTD is Do
demounted step 12
not demounted step 10
10 Demount the MTD by typing

>DEMOUNT tape_name
where
11 Manually busy the MTD by typing

>BSY

bsy
OK
297-2651-543 Standard 05.01 March 1999


minor (continued)
12 Check to see if a tape is loaded on the MTD.
If the tape is Do
loaded on the MTD step 13

not loaded on the MTD step 14
13 Unload the tape on the MTD.
At the MAP terminal

14
CAUTION
Possible loss of MTD data
Ensure that the tape is not loaded on the MTD.
Testing the MTD while a tape is loaded may destroy
data on the tape.
Test the MTD by typing

>TST
passed step 15
generated
15 Load the tape onto the MTD by performing the appropriate procedure in
Routine Maintenance Procedures. When you have completed the procedure,
GSP05 (CSP10)

minor (continued)
16 Reload and mount the tape by typing

>MOUNT mtd_no
where
mtd_no is the number of the MTD
17 Return the MTD to service by typing

>RTS
passed step 34
(PEC), including suffix, of the cards on the card list.
Note: If the input/output message processor card requires replacement, first
ensure that the IOC containing the card is manual busy.
20 Test the MTD by typing

>TST
passed step 23
the cards in the list recorded in
step 18
297-2651-543 Standard 05.01 March 1999


minor (continued)
22 Go to step 20.

>RTS
passed step 34
failed step 24

24 Check the cabling to the MTD for faults.
If the cabling is Do
faulty step 25
not faulty step 36
25 Refer to your office installation manuals to change the cabling to the MTD.
At the MAP terminal

>RTS
passed step 34
failed step 36
GSP05 (CSP10)

minor (continued)
27 Display the status of the IOC connected to the MTD by typing

>IOC ioc_no
where
ioc_no is the number of the IOC connected to the MTD
IOD
IOC 0 1 2 3
STAT . . . S

IOC CARD 0 1 2 3 4 5 6 7 8
0 PORT 0123 0123 0123 0123 0123 0123 0123 0123 0123
STAT .––– .––– ...P ..–– ..–– ––– ––– ––– –––
If the IOC is Do
in service step 29
not in service step 28
28 Perform the procedure Clearing an nIOCOS major or minor alarm in this

document to clear this alarm. When you have completed the procedure, return
to this point.
If the alarm Do
cleared step 37
297-2651-543 Standard 05.01 March 1999


minor (continued)
29 Display the status of the controller port serving the MTD by typing
>PORT port_no
where
port_no is the number of the controller port
If the controller port is Do
in service step 34
not in service step 30
30 Perform the procedure Clearing an nCKOS major or minor alarm in this

document to clear this alarm. When you have completed the procedure, return
to this point.
If the alarm Do
cleared step 37
31 Determine from office records or from office personnel why the MTD is offline or
manual busy. When permissible, return the MTD to service.
If the MTD is Do
offline step 32
manual busy step 33
32 Manually busy the MTD card by typing

>BSY
GSP05 (CSP10)

minor (continued)
(end)

>IOC ioc_no;CARD card_no;RTS
where
card_no is the number of the MTD card
passed step 34
failed step 36
34 Determine if the nMTDOS minor alarm has cleared.
If the alarm Do
cleared step 37

When you have completed the procedure, go to step 34.
support.
297-2651-543 Standard 05.01 March 1999

IOD nnAMA
Alarm display
. . nnAMA . . . . . . .
Indication
At the IOD level of the MAP, a number (nn) precedes AMA. The AMA
indicates an AMA critical, an AMA major, or an AMA minor alarm.
Meaning
The DIRP utility cannot open enough recording files to meet the number of
files specified in the DIRPSSYS table. The number that precedes AMA
indicates the number of files required to satisfy the minimum number of files
for the subsystem. The DIRPSSYS table specifies the number of files.
Result
Backup recording of automatic message accounting (AMA) data is not
available.
Common procedures
This procedure refers to Allocating a volume.
Action
GSP05 (CSP10)
IOD nnAMA
Summary of Clearing an IOD nnAMA critical, major, or minor alarm
Find nn available This flowchart summarizes the

recording procedure.
volumes
Allocate the procedure.
recording
volumes
N
Alarm cleared?
End Contact next

level of support
297-2651-543 Standard 05.01 March 1999

IOD nnAMA
Clearing an IOD nnAMA critical, major, or minor alarm
At the MAP terminal
1 Record the value of nn in the AMA subsystem alarm indicator under the IOD
header of the MAP display.
2 Check local office records for available recording volumes that are acceptable
for AMA subsystem recording. You need the same number of available
volumes as the nn value determined in step 1.
3 Record the volume name(s) of the available recording volumes determined in

step 2.
4 To access the DIRP level of the MAP display, type

>MAPCI;MTC;IOD;DIRP
IOD
IOC 0 1 2
STAT . L .
DIRP: HOLD00 XFER: . DVI : . DPPP: . DPPU: .

5 To allocate one of the additional recording volumes, perform the procedure How
to allocate a volume in this document. You determined which recording
volumes are acceptable in step 2. Complete the procedure and return to this
point.
6 Determine if you need to allocate another volume.
If you Do
need to allocate another volume step 5

do not need to allocate another step 7
volume
GSP05 (CSP10)
IOD nnAMA
(end)
7 Determine if the nnAMA critical, nnAMA major, or nnAMA minor alarm cleared.
If the alarm Do
cleared step 9
297-2651-543 Standard 05.01 March 1999

IOD nnJF
Alarm display
. . nnJF . . . . . . .
Indication
At the IOD level of the MAP, a number (nn) precedes JF. JF indicates a
journal file critical, major, or minor alarm.
Meaning
files specified in the DIRPSSYS table. The number that precedes JF
indicates the number of files needed to satisfy the minimum number of files.
The DIRPSSYS table specifies the number of files.
Result
The system loses records of changes made to data tables or service orders of
the DMS-100 Family systems. The records of changes are on disk or tape.
Common procedures
This procedure refers Allocating a volume.
Action
GSP05 (CSP10)
IOD nnJF
Summary of Clearing an IOD nnJF critical, major, or minor alarm

volumes
Allocate recording procedure.
volumes
Alarm N
cleared?
End Contact next

level of support
297-2651-543 Standard 05.01 March 1999

IOD nnJF
Clearing an IOD nnJF critical, major, or minor alarm
CAUTION
Possible loss or damage of JF data
If you do not use this procedure or follow this procedure
exactly, you can lose or corrupt your JF data.
CAUTION
Possible loss or damage of JF data
If you do not use this procedure or follow this procedure
exactly, you can lose or corrupt your JF data.
At the MAP terminal

1 Record the value of nn in the JF alarm indicator under the IOD header of the
MAP display.
for JF subsystem recording. You need the same number of available volumes
as the nn value determined in step 1.
3 Record the volume name(s) of the available recording volumes determined in

step 2.

>MAPCI;MTC;IOD;DIRP
IOD
IOC 0 1 2
STAT . L .
GSP05 (CSP10)
IOD nnJF
5 To determine the volumes now mounted for JF, type

>QUERY JF VOLUMES
SSNAME SSNO SEQNO ROTATES POOLNO PARLPOOL EMERGENCY
JF 0 1 3 4 NONE ***YES***
REGULAR VOLUME(S)
VOL# VOLNAME STATE IOC CARD VOL FSEG ROOM VLID FILES
21 D010JF READY 1 1 8 4 4 2828 S1
22 D000JF READY 0 1 2 0 0 2802 A
6 If any volumes have problems, where a fault occurred, the STATE is

“INERROR”. A significant reduction in recording capacity occurs when a fault
takes a volume out of service. This fault is a common cause of shortage of
files.
7 If the STATE is READY for all the volumes, you need to allocate additional
volumes.
8 If you need to allocate any volumes, allocate one of the additional recording
volumes determined in step 2. To allocate a volume, perform the procedure
How to allocate a volume in this document. Complete the procedure and return
to this point.
9 Determine if you need to allocate another volume. You must find free space on
a disk to format as an additional JF volume. Go to step 11.
If you Do

volume
10 Determine if the nnJF alarm cleared.
If the alarm Do
cleared step 12
297-2651-543 Standard 05.01 March 1999

IOD nnJF
critical, major,
critical, or minor
major, or minor
(continued)
(end)
GSP05 (CSP10)
IOD nnOM
Alarm display
. . nnOM . . . . . . .
Indication
At the IOD level of the MAP display, a number (nn) and OM indicate an
operational measurement (OM) critical, major or minor alarm
Meaning
files specified in the DIRPSSYS table.
Result
The operating system loses measurement data and cannot collect or display
the data. Measurement data forms the base for decisions about maintenance,
traffic, accounting, and supplies. The number that precedes OM indicates
the number of files required to satisfy the minimum number of files for this
subsystem. The DIRPSSYS table specifies the minimum number of files.
Common procedures
This procedure refers to Allocating a volume.
Action
297-2651-543 Standard 05.01 March 1999

IOD nnOM
Summary of Clearing an IOD nnOM critical, major, or minor alarm

volumes
Allocate the procedure.
recording
volumes
N
Alarm
cleared?
End Contact next

level of support
GSP05 (CSP10)
IOD nnOM
Clearing an IOD nnOM critical, major, or minor alarm
CAUTION
Possible loss or damage of OM data
If you do not use this procedure or follow this
procedure correctly, you can lose or corrupt your OM
data.
CAUTION
Possible loss or damage of OM data
If you do not use this procedure or follow this
procedure correctly, you can lose or corrupt your OM
data.
At the MAP terminal

1 Record the value of nn in the OM alarm indicator under the IOD header of the
MAP display.
for OM subsystem recording. You need the same number of available volumes
as the nn value determined in step 1.
3 Record the volume name(s) of the available recording volume(s) determined in

step 2.

>MAPCI;MTC;IOD;DIRP
IOD
IOC 0 1 2
STAT . L .
5 Allocate one of the additional recording volumes determined in step 2. To

allocate the volume, perform the procedure Allocating a volume in this
document. Complete the procedure and return to this point.
297-2651-543 Standard 05.01 March 1999

IOD nnOM
critical, major,
critical, or minor
major, or minor
(continued)
(end)
6 Determine if you need to allocate another volume.
If you Do

volume
7 Determine if the nnOM critical, major, or minor alarm cleared.
If the alarm Do
cleared step 9
GSP05 (CSP10)
IOD NO AMA on device type DISK

critical
Alarm display
. . NO AMA . . . . . . .
*C*
Indication
At the IOD level of the MAP display, NO AMA indicates a NO AMA
critical alarm. Follow this procedure for device type DISK. For device type
TAPE, follow the procedure Clearing an IOD NO AMA on device type TAPE
critical alarm.
Meaning
Files are not available to record from the AMA subsystem.
Result
Loss of billing information.
Common procedures
Action
the alarm.
297-2651-543 Standard 05.01 March 1999


Summary of Clearing an IOD NO AMA on device type DISK critical alarm
Silence alarm This flowchart summarizes the

procedure.

procedure.
Allocate disk
volume
End
GSP05 (CSP10)

Clearing an IOD NO AMA on device type DISK critical alarm
CAUTION
Possible loss or corruption of AMA data
Use this procedure or follow it exactly. Not doing so will
lose or damage automatic message accounting (AMA)
data. The operating company uses AMA data to produce
billings. Loss or damage of AMA data results in revenue
loss for the operating company.
CAUTION
Use this procedure or follow it exactly. Not doing so
will lose or damage automatic message accounting
(AMA) data. The operating company uses AMA data to
produce billings. Loss or damage of AMA data results
in revenue loss for the operating company.
At the MAP terminal

>MAPCI;MTC;IOD;DIRP
Example of a MAP:
IOD
IOC 0 1 2
STAT . L .
DIRP: HOLD00 XFER: . SLM : . NPO: . NX25: .

2 To silence the audible alarm, type

>SIL
297-2651-543 Standard 05.01 March 1999


3 Inform your maintenance support group of the condition.
If your maintenance group Do
instructs you to continue this step 4

procedure
instructs you not to continue this step 31
procedure
4 Determine the amount of available space in the AMA subsystem. Type

>QUERY AMA SPACE
AMA 0 1 2 0 6 ***YES***
REGULAR SPACE
VOL# VOLNAME STATE SEGS EXP UNEXP TOTAL
5 To query the volumes now mounted in the subsystem, type

>QUERY AMA VOLUMES
AMA 0 1 2 0 6 ***YES***
REGULAR VOLUME(S)
VOL# VOLNAME STATE IOC CARD VOL FSEG ROOM VLID
FILES
NONE
NONE
6 Record the pool number.

Note: The pool number appears under the POOLNO header. The MAP
response in step 5 shows a pool number of 0.
7 To access the DIRPPOOL table, type

>TABLE DIRPPOOL
GSP05 (CSP10)

MACHINES NOT IN SYNC – DMOS NOT ALLOWED
JOURNAL FILE UNAVAILABLE – DMOS NOT ALLOWED
TABLE: DIRPPOOL
8 To position the tuple for the subsystem REGULAR pool, type

>POSITION n;LIST
where
n is the pool number noted in step 5
POOLNO POOLNAME POOLTYPE DEVTYPE VOLUME0 VOLUME1 VOLUME2
VOLUME3 VOLUME4 VOLUME5 VOLUME6 VOLUME7 VOLUME8 VOLUME9
VOLUME10 VOLUME11 VOLUME12 VOLUME13 VOLUME14 VOLUME15
VOLUME22 VOLUME23
0 AMAPOOL REGULAR DISK $ $ $
$ $ $ $ $ $ $
$ $ $ $ $ $
$ $ $ $ $ $
$ $
9 Record the device type shown in the DEVTYPE field for later use.
Note: The device type is under the DEVTYPE header. The MAP response in
step 8 shows the device type as DISK.
10 To exit the DIRPPOOL table, type

>LEAVE
11 Determine from office records the location of an available disk recording volume
used with AMA. Record the volume name.
12 Determine if a disk volume is available.
If a disk volume Do
297-2651-543 Standard 05.01 March 1999



>IOC ioc_no
where
Example of a IOC MAP display
IOC CARD 0 1 2 3 4 5 6 7 8
0 PORT 0123 0123 0123 0123 0123 0123 0123 0123 0123
STAT .––– .––– ...P ..–– ..–– ––– ––– ––– –––

IOC PORT 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
(IOM) STAT . . . – . . – – – . – – – – – – – –
O O O O T P D C
N N N N D C U S
is IOC step 14
is IOM step 15
GSP05 (CSP10)

14 To post the card level, type

>CARD card_no
where
card_no is the card number determined in step 13
Card 1 Unit 0
Go to step 16.
15
To post the port level, type
>PORT port_no
where
port_no is the port number determined in step 13
Port 1 Unit 0
16 To determine the available volumes, type

>ALLOC
VOLID VOL_NAME SERIAL_NO BLOCKS ADDR TYPE R/O FILES_OPEN
0 IMAGE 2800 65535 D000 0 NO 0
1 XPMLOADS 2801 45000 D000 0 NO 0
2 PMLOADS 2802 10000 D000 0 NO 0
3 MPCLOADS 2803 5000 D000 0 NO 0
4 MTCE 2804 10000 D000 0 NO 0
5 MISC 2805 10000 D000 0 NO 0
6 AMA 2806 5000 D000 0 NO 0
7 OM 2807 5000 D000 0 NO 0
8 JF 2808 5000 D000 0 NO 0
297-2651-543 Standard 05.01 March 1999


If a disk volume Do
18 To allocate the disk volume, type

>DIRP;MNT AMA vol_name
where
vol_name is the disk volume name
UPDATING VOLUME INFORMATION FOR vol_name: VOLUME nn IN
REGULAR POOL n, pool_name
19 Determine if you need to allocate the volume.
If you Do
need to allocate the volume step 21

do not need to allocate the volume step 20
20 To halt the allocation, type

>NO
Go to step 32.
21 To confirm the allocation, type

>YES
REGULAR VOLUME vol_name ALLOCATED
22 Allow one minute for the DIRP to allocate the volume.
GSP05 (CSP10)

23 Determine if the NO AMA on device type DISK critical alarm under the IOD
level of the MAP display cleared.
If the alarm Do
cleared step 26
24 Determine from office records the location of another available disk volume that
you did not try.
25 Determine if another disk volume is available.
If another disk volume Do
26 Determine if an nnAMA alarm is present under the IOD header of the MAP
display.
If an alarm Do
is present step 27
27 Clear the nnAMA alarm. Perform the procedure How to clear an nnAMA
critical, major, or minor alarm in this document. Complete the procedure and
28 Determine if the NO AMA on device type DISK critical, major, or minor alarm
cleared.
If the alarm Do
cleared step 32
297-2651-543 Standard 05.01 March 1999


critical
critical
(continued)
(end)
30 Go to step 28.
GSP05 (CSP10)
IOD NO AMA on device type TAPE

critical
Alarm display
. . NO AMA . . . . . . .
*C*
Indication
At the IOD level of the MAP display, NO AMA indicates a NO AMA
critical alarm. Follow this procedure for device type TAPE. For device type
DISK, follow the procedure Clearing an IOD NO AMA on device type DISK
critical alarm.
Meaning
There are no files available to record data from the subsystem.
Result
Loss of billing information.
Common procedures
The following common procedures refer to:
• Allocating a volume
• Deallocating a volume
• Resetting a volume
Action
instructions in the step-action procedure that follow the flowchart to clear
the alarm.
297-2651-543 Standard 05.01 March 1999


Summary of Clearing an IOD NO AMA on device type TAPE critical alarm

Silence the procedure.
alarm
procedure.
Tape volumes N Allocate the

mounted? tape volumes
Tape volumes Y Replace the old Allocate the

full? tape with the new tape
new tape volume
Y Allocate an Repair and

Tape volume alternate reallocate the
damaged? volume defective volumes
N Contact the next

Alarm level of support
cleared?
End
GSP05 (CSP10)

Clearing an IOD NO AMA on device type TAPE critical alarm
CAUTION
will lose or corrupt automatic message accounting
(AMA) data. The operating company uses AMA data
to produce billings. Loss or damage of AMA data
results in revenue loss for the operating company.
CAUTION
(AMA) data. The operating company uses AMA
data to produce billings. Loss or damage of AMA
data results in revenue loss for the operating
company.
At the MAP
>MAPCI;MTC;IOD;DIRP
IOD
IOC 0 1 2
STAT . L .

MLP : . DPPP : . DPPU: . SCAI : . .

>SIL
297-2651-543 Standard 05.01 March 1999


If your maintenance group

instructs you Do
to continue this procedure step 4

not to continue this procedure step 72
4 To query the status of the subsystem files, type

>QUERY AMA FILES
AMA 0 1 2 0 6 ***YES***
REGULAR
FILE(S) STATE VOLUME RECCOUNT BLOCK E V V_B VLID FNUM
FRN#
ACTIVE NONE
STANDBY1 NONE
5 Examine the status of the files in the AMA subsystem.
6 Determine the number of volumes required for the AMA subsystem. Count the
number of active and reserve files displayed. Record this number for later use.

>QUERY AMA VOLUMES
AMA 0 1 2 0 6 ***YES***
REGULAR VOLUME(S)
FILES
22 T0 INERROR 0 0 0 N/A 0 2400
23 T1 INERROR 2 1 0 N/A 0 2400
8 Record the pool number and the status of the normal volumes.
GSP05 (CSP10)

Note: The MAP response in the last step shows a pool number of 0, and two
normal volumes mounted. The response marked the normal volumes as
INERROR.
9 Determine if mounted volumes that are normal are present.
If any normal volumes Do
mounted step 25
did not mount step 10
10 To access table DIRPPOOL , type

>TABLE DIRPPOOL
11 To position the tuple for the normal pool of the subsystem, type
>POSITION n;LIST
where
VOLUME22 VOLUME23
0 AMAPOOL REGULAR TAPE $ $ $
$ $ $ $ $ $ $
$ $ $ $ $ $
$ $ $ $ $ $
T1 T2
12 Record the device type shown in field DEVTYPE.

Note: The MAP response in the last step shows the DEVTYPE of TAPE.
297-2651-543 Standard 05.01 March 1999



>QUIT
If the tape drive Do
is MTD step14
is DAT step 15
14 Determine from office records the location of an available magnetic tape drive
(MTD) for AMA recording. Record the MTD number.
Go to step 16.
15 Determine from office records the location of an available digital audio tape
(DAT) drive for AMA recording. Record the DAT number.
16 Determine if another tape drive is available.
If another tape drive Do
is available (MTD) step 17

is available (DAT) step 18
17 Load a tape on the MTD. Refer to Magnetic Tape Reference Manual,

297-1001-118 and return to this point.
GSP05 (CSP10)

18
WARNING
Tape cartridges
Use cartridges with the DDS logo. The DAT drive unit
supports DDS/DDS-1 cartridges only and rejects
DDS-2 cartridges during the load operation.
WARNING
Tape cartridges
Use cartridges with the DDS logo. The DAT drive
unit supports DDS/DDS-1 cartridges only and rejects
DDS-2 cartridges during the load operation.
Insert the tape cartridge into the drive. The drive automatically takes the
cartridge and performs a load sequence.
19 To allocate the tape volume on the MTD, type

>MNT AMA tn
where
tn is the MTD number
UPDATING VOLUME INFORMATION FOR Tn: VOLUME nn IN REGULAR
POOL n, pool_name
20 Determine if you want to continue with the volume allocation.
If you Do
want to continue step 22

do not want to continue step 21

>NO
297-2651-543 Standard 05.01 March 1999


Go to step 73.

>YES
23 Determine if the NO AMA on device type TAPE critical alarm cleared.
If the alarm Do
cleared step 67
24 Determine from office records if another magnetic tape drive or digital audio
tape drive is available.

25 Determine from the volume the name of the recording device type used for the
allocated volumes.
Note: Tn is the standard name for tape volumes.
26 Determine if any volumes are in the INERROR state.
If any volumes Do
are in the INERROR state step 27

are not in the INERROR state step 58
GSP05 (CSP10)

27 Determine from the DIRP logs why INERROR marks the volumes. Type
>LOGUTIL
28 To record the logs, type

>STARTDEV dev_type ADDREPS dev_name DIRP
where
dev_type is the type of device in use
dev_name is the name of the printer or visual display unit
ONE REPORT ADDED
29 When you determine why the INERROR condition occurred. To exit the log
utility, type
>QUIT
30 Determine if the voume is INERROR because of a volume–full condition or

because of a device error.
If the volume Do
is INERROR and the reason is the step 31

volume is full
is INERROR and the reason is a step 35
device error
31 Deallocate the tape volume. Refer to common procedure Deallocating a

volume in this document. Complete the procedure and return to this point.
is MTD step 32
is DAT step 33
297-2651-543 Standard 05.01 March 1999


32 Unload the full tape from the drive. Label the tape and store it according to
your local procedures. Load a new tape acceptable for the subsystem
recording on the drive. Perform the correct procedure in Magnetic Tape
Reference Manual, 297-1001-118. Complete the procedure and return to this
point.
33
WARNING
Possible loss of data
Force eject a cartridge only at a last resort to recover a
cartridge. Never use this method as a quick way to
eject the cartridge. If you use this method as a quick
way of ejecting the cartridge, you can lose data. This
method can also cause a tape to format in the wrong
manner.
WARNING
Force eject a cartridge only at a last resort to recover
a cartridge. Never use this method as a quick way to
eject the cartridge. If you use this method as a quick
way of ejecting the cartridge, you can lose data. This
method can also cause a tape to format in the wrong
manner.
Remove the full tape cartridge from the drive. Press the unload button at the
front of the unit.
Note: The drive will perform an unload sequence. The tape is rewound to the
beginning of partition (BOP) for partition 0. If the tape is write enabled, the drive
writes a copy of the tape log back to the tape. The drive rewinds the tape to the
beginning of media. The drive rewrites to the tape from the mechanism and
eject the tape.
34 Determine if replacement of more tape volumes is to occur.
If more tape volumes Do
need replacement step 31

do not need replacement step 19
GSP05 (CSP10)

35 Reset the INERROR volume. Perform the common procedure How to reset a
36 Determine if more volumes need to reset.
If more volumes Do
are to be reset step 35

are not to be reset step 37
37 To query the subsystem again and verify the status of the reset volumes, type
>QUERY AMA VOLUMES
AMA 0 1 0 0 NONE ***YES***
REGULAR VOLUME(S)
FILES
38 Determine if the INERROR volumes reset correctly.
If the INERROR volumes Do
reset correctly step 46

did not reset correctly step 39
39 Determine from office records if another recording volume is available. The

MTD or DAT unit that is now in use can have faults.

is not available (MTD) step 40
is not available (DAT) step 41
297-2651-543 Standard 05.01 March 1999


40 Repair the recording device that has faults. Perform the correct procedure in
Recovery Procedures. Complete repairs of the device that has faults and
Go to step 42.
41 Replace the DAT unit that has faults. Perform the correct procedure in Trouble
and Locating Procedures. Complete the repairs of the device that has faults
and return to this point.
42 Reset the repaired volume. Perform the common procedure How to reset a
43 Determine if more volumes need to reset.
If more volumes Do
are to be reset step 42

are not to be reset step 44
44 Query the subsystem again and verify the status of the reset volume(s). Type
>QUERY AMA VOLUMES
AMA 0 1 0 0 NONE ***YES***
REGULAR VOLUME(S)
FILES
45 Determine if the repaired volumes reset.
If the repaired volumes Do
reset step 46
did not reset (MTD) step 47
did not reset (DAT) step 48
GSP05 (CSP10)

46 Determine if the NO AMA alarm cleared.
If the alarm Do
cleared step 67
did not clear (MTD) step 47
did not clear (DAT) step 48
47 Obtain enough blank or expired tapes for the number of tape volumes that you
allocate again. Make sure each tape has a write-enable ring attached.
Go to step 49.
48
WARNING
Tape cartridges
Use cartridges marked with the DDS logo. The DAT
drive unit supports only DDS/DDS-1 cartridges and
rejects DDS-2 cartridges during the load operation.
WARNING
Tape cartridges
Obtain enough blank or expired cartridges for the number of tape volumes that
you allocate again.
49 Select a tape volume to deallocate and record the MTD or DAT number.
50 Deallocate the selected volume. Perform the common procedure Deallocating a

297-2651-543 Standard 05.01 March 1999


51 Unload the tape from the deallocated MTD or DAT. Marked INERROR this
volume can have data errors.
is MTD step 52
is DAT step 54
52 Label and store this tape according to local procedure. Perform the correct
procedure in Magnetic Tape Reference Manual, 297-1001-118. Complete the
53 Load a blank or expired tape on the unloaded MTD. Perform the correct
Go to step 55.
54
WARNING
Labeling of tape cartridges
Cartridge labels must be firmly stuck to the recessed
label area on the cartridge to prevent a jam of the
mechanism.
WARNING
Cartridge labels must be firmly stuck to the recessed
label area on the cartridge to prevent a jam of the
mechanism.
Label and store the cartridge according to local procedure. Make sure that
labels are not:
• peeling off
• over the edge of the label area
• stuck on top of another label
55 Allocate the volume. Perform the common procedure Allocating a volume in this
document. Complete the procedure and return to this point.
GSP05 (CSP10)

56 Allow 1 min for the DIRP utility to allocate the volumes.
57 Determine if more volumes move.
If more volumes Do
require allocation (MTD) step 47

require allocation (DAT) step 48
do not require allocation step 66
58 To deallocate the disk volume, type

>DMNT AMA vol_name
where
vol_name is the name of the disk volume
UPDATING VOLUME INFORMATION FOR
vol_name: VOLUME nn IN REGULAR POOL n, pool_name
PLEASE CONFIRM (”YES” OR ”NO”):
59 Determine if you want to continue with the volume deallocation.
If you want the volume

deallocation Do
to continue step 61
not to continue step 60
60 To halt the deallocation, type

>NO
Go to step 73.
297-2651-543 Standard 05.01 March 1999


61 To confirm the deallocation, type

>YES
REGULAR VOLUME vol_name WILL BE TAKEN OUT OF DIRP AS SOON
AS POSSIBLE

>MNT AMA vol_name
where
UPDATING VOLUME INFORMATION FOR
vol_name: VOLUME nn IN REGULAR POOL n, pool_name
PLEASE CONFIRM (”YES” OR ”NO”):
63 Determine if you want to continue with the volume allocation.
If you want the volume allocation Do
to continue step 65
not to continue step 64

>NO
Go to step 73.

>YES
GSP05 (CSP10)

(end)
66 Determine if the NO AMA alarm cleared.
If the alarm Do
cleared step 67
67 Determine if an nnAMA alarm is present under the IOD header of the MAP
display.
If the alarm Do
is present step 68
68 Clear the nnAMA alarm. Perform the procedure Clearing an IOD nnAMA
critical, major, or minor alarms in this document. Complete the procedure and
69 Determine if the NO AMA on the device type TAPE critical alarm cleared.
If the alarm Do
cleared step 73
71 Go to step 69.
297-2651-543 Standard 05.01 March 1999

IOD NOssys on device type TAPE

critical
Alarm display
. . NOssys . . . . . . .
*C*
Indication
At the IOD level of the MAP, NO ssys indicates a NO ssys alarm. Follow
this procedure for critical alarms on device type TAPE. For critical alarms
on device type DISK, follow the correct procedure. The correct procedure is
Clearing an IOD NOssys on device type DISK critical, major, or minor
alarm.
Meaning
There are no files available to record data from the subsystem. The
abbreviation ssys represents the affected subsystem. Affected subsystems
can include JF, OM, SMDR, and AMA.
Result
If the NO ssys is a NO AMA or NO SMDR alarm, loss of billing data
occurs. If the NO ssys is an alarm that affects any other subsystem, switch
information loss occurs. The following data associates with each subsystem.
• The JF subsystem records changes made to data tables or service orders
• The OM subsystem collects and displays measurement data on the
operating system.
• The AMA subsystem collects and records billing data of subscriber
dialed long distance calls
Common procedures
The following common procedures refer to:
GSP05 (CSP10)

Action
instructions in the step-action procedure that follow the flowchart to clear
the alarm.
297-2651-543 Standard 05.01 March 1999


Summary of Clearing an IOD NOssys on device type TAPE critical alarm

Silence the procedure.
alarm
procedure.
Allocate tape
Tape volumes N
volumes
mounted?
Tape volumes Y Replace the old Allocate the

full? tape with the new tape
new tape volume
Y Allocate an Repair and

Tape volume
alternate reallocate the
have faults?
volume MAP volumes
N Contact next
Alarm
level of support
cleared?
End
GSP05 (CSP10)

Clearing an IOD NOssys on device type TAPE critical alarm
At the MAP terminal
>MAPCI;MTC;IOD;DIRP
IOD
IOC 0 1 2
STAT . L .

MLP : . DPPP : . DPPU: . SCAI : . .

>SIL

instructs you Do

4 To query the status of the subsystem files, type

>QUERY ssys FILES
where
ssys is the affected subsystem
ssys 0 1 2 0 6 REGULAR
FILE(S) STATE VOLUME RECCOUNT BLOCK E V V_B
VLID FNUM FRN#
ACTIVE NONE
STANDBY1 NONE
297-2651-543 Standard 05.01 March 1999


5 Examine the status of the files in the ssys subsystem.
6 Determine the number of volumes required for the subsystem. Count the
number of active and auxiliary files displayed. Record this number for later use.

>QUERY ssys VOLUMES
where
ssys the affected subsystem
ssys 0 1 2 0 6 **YES***
REGULAR VOLUME(S)
FILES
22 T0 INERROR 0 0 0 N/A 0 2400
23 T1 INERROR 2 1 0 N/A 0 2400
8 Record the pool number and the status of the normal volumes.
Note: The MAP response in step 7 shows a pool number of 0. The MAP
response also shows two REGULAR volumes mounted and marked INERROR.
9 Determine if any REGULAR volumes mounted.
If any regular volumes Do
mounted step 26
10 To access table DIRPPOOL, type

>TABLE DIRPPOOL
TABLE: DIRPPOOL
GSP05 (CSP10)


>POSITION pool_no;LIST
where
pool_no is the pool number noted in step 7
VOLUME22 VOLUME23
0 ssysPOOL REGULAR TAPE $ $ $
$ $ $ $ $ $ $
$ $ $ $ $ $
$ $ $ $ $ $
T1 T2
12 For later use, record the device type shown in the DEVTYPE field.
Note: The MAP response in step 11 shows a DEVTYPE as TAPE.
13 To exit table DIRPPOOL, type

>LEAVE
If an tape drive Do
is MTD step 14
is DAT step 15
(MTD) for subsystem recording. Record the MTD number for later use.
Go to step 16.
15 Determine from office records the location of an available digital audio tape
(DAT) drive for AMA recording. Record the DAT number.
297-2651-543 Standard 05.01 March 1999


16 Determine if another tape drive is available.

17 Perform the correct procedure in Magnetic Tape Reference Manual,

297-1001-118. to load a tape on the MTD. Complete the procedure and return
to this point.
18
WARNING
Tape cartridges
WARNING
Tape cartridges
Insert the tape cartridge into the drive. The drive automatically takes the
cartridge and performs a load sequence.
19 To allocate the tape volume on the MTD, type

>MNT ssys tn
where
tn is the MTD number
GSP05 (CSP10)

UPDATING VOLUME INFORMATION FOR Tn: VOLUME nn IN
REGULAR POOL n, pool_name
20 Determine the volume that you will allocate.
If the volume Do
needs allocation step 22

does not need allocation step 21

>NO
Go to step 69.

>YES
23 Allow 1 min for the DIRP utility to allocate the volumes.
24 Determine if the NO ssys alarm cleared.
If the alarm Do
cleared step 63
297-2651-543 Standard 05.01 March 1999


25 Determine from office records if another tape drive is available.

26 Determine from the recording device type used for the allocated volumes from
the volume name.
Note: Tn is the name for tape volumes.
If any volumes Do

28 Determine from the DIRP logs why the volumes have the INERROR marks.
Type
>LOGUTIL
29 To record of the logs, type

>STARTDEV dev_type;ADDREPS dev_name DIRP
where
dev_type is the type of device in use
dev_name is the name of the printer or visual display unit
ONE REPORT ADDED
30 When you determine the reason for the INERROR condition, exit the log utility.
Type
>QUIT
GSP05 (CSP10)

31 Determine if the volume is in the INERROR state because of a volume full

condition or a device error.
If the volume Do
is in the INERROR state and the step 32

reason is the volume is full
is in the INERROR state and the step 37
reason is a device error
32 Deallocate the tape volume. Perform the common procedure Deallocating a

is MTD step 33
is DAT step 35
33 Unload the full tape from the drive. Label the tape and store it according to
your local procedures.
34 Load a new tape acceptable for subsystem recording on the drive. Perform the
correct procedure in Magnetic Tape Reference Manual, 297-1001-118.
Go to step 36.
297-2651-543 Standard 05.01 March 1999


35
WARNING
Force eject a cartridge only at a last resort to recover a
cartridge. Never use the method as a quick way of
ejecting the cartridge. If you use this method as a
quick way of ejecting the cartridge, you can lose data.
This method can also cause a tape to format wrong.
WARNING
Force eject a cartridge only at a last resort to recover
a cartridge. Never use the method as a quick way of
ejecting the cartridge. If you use this method as a
quick way of ejecting the cartridge, you can lose
data. This method can also cause a tape to format
wrong.
To remove the full tape cartridge from the drive, press the unload button at the
front of the unit.
Note: The drive performs an unload sequence. The drive rewinds the tape to
the beginning of partition (BOP) for partition 0. If the tape is write enabled, the
drive writes a copy of the tape log back to tape. The drive then rewinds the
tape to the beginning of media. The drive unthreads the tape from the
mechanism and ejects the tape.
36 Determine if you need to replace more tape volumes.
If you Do
need to replace more tape volumes step 32

do not need to replace any more step 19
tape volumes
37 Reset the INERROR volume. Perform the common procedure Resetting a

GSP05 (CSP10)

38 Determine if more volumes need to be reset.
If you Do
need to reset more volumes step 37

do not need to reset any more step 39
volumes
39 Query the subsystem again and verify the status of the reset volumes. Type
>QUERY ssys VOLUMES
where
AMA 0 1 0 0 NONE ***YES*** REGULAR
VOLUME(S)
40 Determine if the INERROR you reset the volumes correctly.
If the INERROR volumes Do
reset correctly step 48

did not reset correctly step 41
41 Determine from office records if another available recording volume is present.

The MTD or DAT unit now in use can have faults.
If a different drive Do

is not available (MTD) step 42
is not available (DAT) step 43
297-2651-543 Standard 05.01 March 1999


42 Repair the recording device if it has faults. Perform the correct procedure in
Recovery Procedures. Complete the procedure and return to this point.
Go to step 44.
43 Repair or replace the DAT unit that has faults. Perform the correct procedure in
Trouble and Locating Procedures. When replacement of the damaged drive
unit is complete, return to this point.
44 Reset the repaired volume. Perform the common procedure Resetting a

45 Determine if more volumes need to be reset.
If you Do
need to reset more volumes step 44

do not need to reset any more step 46
volumes
46 To query the subsystem again and verify the status of the reset volume(s).
Type
>QUERY ssys VOLUMES
where
AMA 0 1 0 0 NONE ***YES*** REGULAR
VOLUME(S)
47 Determine if the repaired volumes reset.
If the repaired volumes Do
reset step 48
did not reset (MTD) step 49
did not reset (DAT) step 50
GSP05 (CSP10)

If the alarm Do
cleared step 63
did not clear (MTD) step 49
did not clear (DAT) step 50
49 Obtain enough blank or expired tapes for the number of tape volumes that you
allocate again. Make sure that each tape has a write enable ring attached.
Go to step 51.
50
WARNING
Tape cartridges
drive unit will support only DDS/DDS-1 cartridges
and will reject DDS-2 cartridges during the load
operation.
WARNING
Tape cartridges
drive unit will support only DDS/DDS-1 cartridges
and will reject DDS-2 cartridges during the load
operation.
Obtain the correct amount of blank or expired cartridges for the number of tape
volumes that you allocate again.
51 Select a tape volume to deallocate and record the MTD or DAT number.
52 Deallocate the selected volume. Perform the common procedure Deallocating

a volume in this document. Complete the procedure and return to this point.
297-2651-543 Standard 05.01 March 1999


53 Unload the tape from the deallocated MTD or DAT. This INERROR volume can
contain data errors.
is MTD step 54
is DAT step 56
54 Label and store this tape according to your local office procedure. Also, you
can perform the correct procedure in Magnetic Tape Reference Manual,
297-1001-118. Complete the procedure and return to this point.
55 Load a blank or expired tape on the unloaded MTD. Perform the correct
Go to step 57.
56
WARNING
Cartridge labels must be firmly stuck to the inner label
area on the cartridge. You can prevent a mechanism
jam if the cartridge labels are stuck to the inner label
area on the cartridge.
WARNING
Cartridge labels must be firmly stuck to the inner
label area on the cartridge. You can prevent a
mechanism jam if the cartridge labels are stuck to the
inner label area on the cartridge.
Label and store the cartridge according to local procedure. Ensure that labels
are not:
• peeling off
• over the edge of the label area
• stuck on top of another label
GSP05 (CSP10)

57 Allocate the volume. Perform the common procedure Allocating a volume in

this document. Complete the procedure and return to this point.
58 Allow one minute for the DIRP utility to allocate the volumes.
59 Determine if you have to allocate more volumes.
More volumes Do
to be allocated (MTD) step 49

to be allocated (DAT) step 50
not to be allocated step 65
60 Deallocate the volume. Perform the common procedure Deallocating a volume

in this document. Complete the procedure and return to this point.
61 Allocate the volume. Perform the common procedure Deallocating a volume in

62 Allow one minute for the DIRP utility to allocate the volumes.
63 Determine if an nnJF, nnOM, or nnAMA alarm appears under the IOD header of
the MAP.
If Do
an nnJF, nnOM, or nnAMA alarm step 64

no nnJF, nnOM, or nnAMA alarm step 65
64 Clear the nnJF, nnOM, or nnAMA alarm. Perform the correct procedure in this
document. When the procedure is complete, return to this point.
65 Determine if the NO ssys on device type TAPE critical alarm cleared.
If the alarm Do
cleared step 69
297-2651-543 Standard 05.01 March 1999


critical
critical
(continued)
(end)
67 Go to step 65.
GSP05 (CSP10)
IOD NOssys on device type DISK

Alarm display
. . NOssys . . . . . . .
*C*
Indication
At the IOD level of the MAP display, NOssys indicates a NOssys critical,
major, or minor alarm. Follow this procedure for device type DISK. For
critical alarms on device type TAPE, follow Clearing an IOD NOssys on
device type TAPE critical alarm.
Meaning
Files are not available to record data from the subsystem. The abbreviation
ssys represents the affected subsystem. Affected subsystems can include
journal file (JF), operational measurement (OM), station message detail
recording (SMDR), and automatic message accounting (AMA).
Result
If the NOssys is a NO AMA or NO SMDR alarm, loss of billing data occurs.
If the NO ssys is an alarm that affects any other subsystem, the loss of
switch information occurs. Each subsystem contains the following data:
• The JF subsystem records changes made to data tables or service orders.
• The OM subsystem collects and shows measurement data on the
operating system.
• The AMA subsystem collects and records billing data of long distance
calls that the subscriber dialed.
Common Procedures
Action
297-2651-543 Standard 05.01 March 1999


Summary of Clearing an IOD NOssys on device type DISK critical, major, or minor alarm

Silence alarm procedure.

procedure.
Allocate disk
volumes
End
GSP05 (CSP10)

Clearing a IOD NOssys on device type DISK critical, major, or minor alarm
CAUTION
Possible loss or damage of AMA data
lose or corrupt automatic message accounting (AMA)
CAUTION
At the MAP terminal

>MAPCI;MTC;IOD;DIRP
IOD
IOC 0 1 2 3
STAT . L . .


>SIL
297-2651-543 Standard 05.01 March 1999


3 Contact your maintenance support group immediately. Notify the maintenance

group of the condition.

instructs you Do

4 To determine the amount of available space in the subsystem, type

>QUERY ssys SPACE
where
ssys 0 1 2 0 6 ***YES***
REGULAR SPACE
THE SPACE OPTION IS NOT SUPPORTED BY THE DEVICE
USED FOR REGULAR RECORDING BY THIS SUBSYSTEM.

>QUERY ssys VOLUMES
where
ssys is the subsystem affected
ssys 0 1 2 0 6 **YES***
REGULAR VOLUME(S)
VLID FILES
NONE
NONE
6 Record the pool number.
GSP05 (CSP10)

Note: The pool number is under the POOLNO header. For example, the MAP
response in step 5 shows a pool number of 0.

>TABLE DIRPPOOL
TABLE: DIRPPOOL

>POSITION n;LIST
where
VOLUME22 VOLUME23
0 ssysPOOL REGULAR DISK $ $ $
$ $ $ $ $ $ $
$ $ $ $ $ $
$ $ $ $ $ $
T1 T2
9 Record the device type shown in the DEVTYPE field for later use.
Note: The device type appears under the DEVTYPE header. For example,
the MAP response in step 8 shows a DEVTYPE of DISK.
10 To exit table DIRPPOOL, type

>LEAVE
11 Determine from office records the location of an available disk recording

volume. Record the volume name.
297-2651-543 Standard 05.01 March 1999


If a disk volume Do

>IOC ioc_no
where
IOC CARD 0 1 2 3 4 5 6 7 8
0 PORT 0123 0123 0123 0123 0123 0123 0123 0123 0123
STAT .––– .––– ...– .––. P––P P–– .–– ––– –––
TYPE MTD DDU CONS CONS CONS CONS MPC MPC CONS

IOC PORT 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
(IOM) STAT . . . – . . – – – . – – – – – – – –
0 TYPE M D C C C M M D S
T D O O O P P D C
D U N N N C C U S
If the device Do
is IOC step 14
is IOM step 15
GSP05 (CSP10)

14 To post the DDU, type

>CARD card_no
where
card_no is the number of the terminal controller card (0 to 8)

Card 1 Unit 0
Go to step 16.
15 To post the DDU, type

>PORT port_no
where
port_no is the number of the terminal controller port (0 to 15)

Port 1 Unit 0
16 To determine the available volumes, type

>ALLOC

VOLID VOL_NAME SERIAL_NO BLOCKS ADDR TYPE R/O FILES_OPEN
0 IMAGE 2800 65535 D000 0 NO 0
1 XPMLOADS 2801 45000 D000 0 NO 0
2 PMLOADS 2802 10000 D000 0 NO 0
3 MPCLOADS 2803 5000 D000 0 NO 0
4 MTCE 2804 10000 D000 0 NO 0
5 MISC 2805 10000 D000 0 NO 0
6 AMA 2806 5000 D000 0 NO 0
7 OM 2807 5000 D000 0 NO 0
8 JF 2808 5000 D000 0 NO 0
297-2651-543 Standard 05.01 March 1999


If a disk volume Do

>DIRP;MNT ssys vol_name
where
vol_name is the disk volume name
UPDATING VOLUME INFORMATION FOR vol_name: VOLUME nn
IN REGULAR POOL n, pool_name
19 Determine if you need to allocate the volume
If you Do
need to allocate the volume step 21

do not need to allocate the volume step 20

>NO
Go to step 31.

>YES
GSP05 (CSP10)

22 Allow approximately 1 min for the DIRP utility to allocate the volumes.
If the alarm Do
cleared step 25
24 Determine from office records the location of another available disk volume that
is available.
If another disk volume Do
25 Determine if an nnJF, nnOM, or nnAMA alarm is present under the IOD header
of the MAP display.
If an nnJF, nnOM, or nnAMA

alarm Do
is present step 26
26 Use the correct procedure in this document to clear the nnJF, nnOM, or nnAMA
alarm. Complete the procedure and return to this point.
27 Determine if a NOssys on device type DISK critical, major, or minor alarm

cleared.
If the alarm Do
cleared step 31
297-2651-543 Standard 05.01 March 1999


critical, major,
critical, or minor
major, or minor
(continued)
(end)
29 Go to step 27.
GSP05 (CSP10)
IOD nSVC
critical
Alarm display
. . 1SVC . . . . . . .
*C*
Indication
At the MTC level of the MAP display, a number precedes SVC under the
IOD header of the alarm banner. The SVC indicates an alarm for a switched
virtual circuit (SVC). The SVC indicates the number of switched virtual
circuits in alarm condition.
Meaning
A failure of an X.25 link indicates a network operations protocol (NOP)
application is not available
A remote user logged into a switch on an X.25 link. The user disconnected
without first logging out of the NOP session.
The terminal at the remote end of the associated multiprotocol controller

(MPC) link reboots during an NOP session. The rebooting of the MPC link
causes the X.25 link to go out of service.
Result
The X.25 link is not available.
Common procedures
Action
the alarm.
297-2651-543 Standard 05.01 March 1999

IOD nSVC
Summary of Clearing an IOD nSVC critical alarm
Execute the NOP This flowchart summarizes the

and CLEAR procedure.
commands
Y procedure.
Alarm
1
cleared?
Test the MPC

card
2 1
MPC N Return card Y End

Alarm
card and links to
cleared?
defective? service
Y N
Busy card and Contact next

links level of service
Replace card
Load card
Return card
and links to
service
GSP05 (CSP10)
IOD nSVC
Clearing an IOD nSVC critical alarm
At the MAP terminal
1 To access the NOP level of the MAP display, type
>MAPCI;MTC;IOD;NOP
IOD
IOC 0 1 2 3 4 5
STAT . O . O L S
DIRP: NO AMA XFER: . SLM : SLMoff NX25: . MLP : .

NOP : 1 SVC DPPP: . DPPU: . SCAI: .
1
SE: 0123456789012
ST: LLLLLLLL.....
–––––––––––––––––
SESS
?
NOP:
2 To attempt to clear the alarm, type

>CLEAR
If the alarm Do
cleared step 16
297-2651-543 Standard 05.01 March 1999

IOD nSVC

>QUIT
IOD
IOC 0 1 2 3
STAT . . . .
DIRP: NO AMA XFER: . SLM : SLMoff NX25: . MLP : .

NOP : 1 SVC DPPP: . DPPU: . SCAI: .
IOD:
4 Post the MPC card (NT1X62) associated with the affected X.25 link. Type
where
ioc_no is the number of the associated IOC (0 to 11)
card_no is the number of the associated MPC card
IOC CARD 0 1 2 3 4 5 6 7 8
0
1 PORT 0123 0123 0123 0123 0123 0123 0123 0123 0123
STAT .... .––– ...– .––– .... .––– .... .––– ....
TYPE CONS DDU CONS MPC CONS MPC CONS MPC CONS
Card 3 Unit 3
Status Ready COMACT UNEQ UNEQ ENABLD UNEQ
5 Determine the state of the MPC card.
If the state of the card Do
is MANB step 7
is OFFL step 13
Note: The card state appears under the BOARD header of the MAP display.
GSP05 (CSP10)
IOD nSVC
6
CAUTION
Loss of service
When you busy the MPC card and its ports, all active
NOP sessions associated with the card will disconnect.
CAUTION
Loss of service
When you busy the MPC card and its ports, all active
NOP sessions associated with the card will
disconnect.
To make the card and its links manually busy, type

>BSY ALL FORCE
passed step 7
failed step 15
7 To test the MPC card, test

>TST
passed step 11
failed, a card list generated, and the step 8
MPC card listed
297-2651-543 Standard 05.01 March 1999

IOD nSVC
8 To place the MPC card offline, type

>OFFL ALL FORCE
9 Perform the procedure Replacing a card in Card Replacement Procedures. to
replace the MPC card. Complete the procedure and return to this point.
10 To load the MPC card, type

>DOWNLD
passed step 11
failed step 15
11 To return the MPC card and its links to service, type

>RTS ALL
passed step 12
failed step 14
12 Determine if the alarm cleared.
If the alarm Do
cleared step 16
13 Consult operating company personnel to determine why the card is offline.

Continue as directed by office persons.
14 Obtain copies of IOD, MPC and NOP log reports.
GSP05 (CSP10)
IOD nSVC
(end)
297-2651-543 Standard 05.01 March 1999

IOD nCKOS on an IOM

major or minor
Alarm display
. . nCKOS . . . . . . .
Indication
At the IOD level of the MAP display, CKOS preceded by a number (n)
indicates a major or minor port out-of-service alarm.
Meaning
One or more ports are out of service. The number that precedes CKOS
indicates how many ports are out of service. Each of these ports is
connected to a terminal, such as a MAP terminal or a printer.
Impact
Service is discontinued to any device associated with an out-of-service
circuit or port.
Common procedures
Not applicable
Action
the alarm.
GSP05 (CSP10)
IOD nCKOS on an IOM

Summary of clearing an IOD nCKOS on an IOM alarm

procedure.
2
Select an open procedure that follows this
port flowchart to perform the
procedure.
Offline and test

port
N Select open Port N Provision

Smart
port available? another IOM
connector?
Y Y
connector cable cable
3 3 3
Test the circuit
Return the N Contact next

circuit to service Passed? 5 level of support
1 Y
End
297-2651-543 Standard 05.01 March 1999

IOD nCKOS on an IOM

Clearing a/an IOD nCKOS on an IOM alarm
ATTENTION
the IOD nCKOS in an IOC minor alarm clearing procedure.
At the MAP terminal

>MAPCI;MTC;IOD

IOD
IOC 0 1 2 3
STAT . . . S

exists step 3
does not exists step 4

>SIL
GSP05 (CSP10)
IOD nCKOS on an IOM

4 Determine the configuration of the controller system by typing

>IOC ioc_no
where
IOC PORT 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
(IOM) STAT . . . – . . – – – . – – – – – – – –
O O O O T P C C
N N N N D C S S
If the port status is Do
C (C-side busy) step 6

P (P-side busy) step 9
6 The C-side links to the console are out of service. Determine if there is an
alarm under the MS header.
exists step 7

297-2651-543 Standard 05.01 March 1999

IOD nCKOS on an IOM

8 Determine from the MAP display if the alarm under the MS header has cleared.
If the alarm Do
cleared step 9
9 Record the IOM console ports that have P status.
If the P status affects Do
one port step 11

more than one port step 10
10 Select one port to work from the list recorded in step 9.
11 Post the affected IOM console port by typing

>PORT port_no
where
port_no is the port number of the affected console device
Port 2 Status
Cons Id MAP
ConType CYB
If the device status is Do
SYSb step 12
Offl step 47
ManB step 45
GSP05 (CSP10)
IOD nCKOS on an IOM

12 Manually busy the console by typing

>BSY

bsy
OK
13 Test the console by typing

>TST
passed step 49
generated
14 Offline the terminal by typing

>OFFL

>QUIT

>BSY PORT port_no
bsy
OK
297-2651-543 Standard 05.01 March 1999

IOD nCKOS on an IOM

17 Offline the busied console port by typing

OFFL PORT port_no
18 Test the console port by typing

>TST PORT port_no
where
Failed
identified step 19

19
WARNING
Locate the PERTEC smart connector mounted on an L-shaped bracket close to

the tape drive and check the smart connector LED. Replace the smart
connector.
GSP05 (CSP10)
IOD nCKOS on an IOM

20 Test the smart connector by typing

>TST PORT port_no
where
Failed
passes step 29
fails step 21
At the MAP terminal

If a port is Do

controller
available on another IOM step 32
there is no other IOM available step 34
297-2651-543 Standard 05.01 March 1999

IOD nCKOS on an IOM

22
CAUTION
You may require the assistance of the provisioning
Determine from table IOC if the open port is datafilled with the correct load
device by typing
>TABLE IOC
23 Go to table CONS by typing

>TABLE TERMDEV
24 Delete the tuple associated with the affected port and add the tuple for the
spare IOM port selected in step 21.
25 Post the new IOM CONS port by typing

>PORT port_no
where
port_no is the number of the CONS port
Port 2 Status
Cons Id MAP
ConType CYB
26 Manually busy the new console by typing

>BSY

bsy
OK
GSP05 (CSP10)
IOD nCKOS on an IOM

27
WARNING
Locate the smart cable connecting the CONS port on the paddleboard and the
associated CONS device. Disconnect the smart cable and connect it to the
new CONS port selected in step 21.
28 Go to step 40.

>BSY PORT port_no
where
bsy
OK
30 Return the console port to service by typing

>RTS PORT port_no
where
31 Go to step 36.
297-2651-543 Standard 05.01 March 1999

IOD nCKOS on an IOM

32 Post another configured controller system by typing

>IOC ioc_no
where
IOC PORT 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
(IOM) STAT . . . – . . – – – . – – – – – – – –
O O O O T P C C
N N N N D C S S
If there is a port Do
available step 22
34
CAUTION
You will require the assistance of the provisioning
There will be a requirement to provision another IOM module. Consult your

provisioning administrator about provisioning another IOM controller card.
35 Go to step 51.
36 Replace the card by performing the appropriate procedure in Card

this point.
GSP05 (CSP10)
IOD nCKOS on an IOM

37 Test the IOM card by typing

>TST
Failed
If the test Do
passes step 41
fails, and all cards have not been step 38
replaced
failed, and all cards have been step 51
replaced
return to this point. Go to step 37.
39 Go to step 37.
40 Post the console port by typing

>PORT port_no
where
43 Check the console to ensure that it is running properly and there are no
physical problems.
297-2651-543 Standard 05.01 March 1999

IOD nCKOS on an IOM

Switch Setting
Power On
Local/OnLine OnLine
Parity No Parity
If the external switch settings are Do
correct step 46
not correct step 45
45 Change the external switch setting as per the table in step 44. When you have
completed the procedure return to this point.
46 Test the console device by typing

>TST
where
passed step 49
failed step 51
47 Determine from office records or from office personnel why the console is
offline. When permissible, manually busy the console by typing
>BSY
GSP05 (CSP10)
IOD nCKOS on an IOM

(end)
48 Test the manually busy console by typing

>TST
passed step 49
generated
49 Return the console to service by typing

>RTS
passed step 50
failed step 51
50 Determine from the MAP display if the nCKOS major or minor alarm has
cleared.
If the alarm Do
cleared step 52
did not clear, and there are other step 10
consoles out of service
service
support.
297-2651-543 Standard 05.01 March 1999

IOD nMTDOS on an IOM

minor
Alarm display
. . nMTDOS . . . . . . .
Indication
At the IOD level of the MAP display, a number (n) and MTDOS indicate a
minor alarm on an integrated services module (ISM). The minor alarm is
for a magnetic tape drive (MTD) and digital audio tape (DAT).
Meaning
One tape drive or digital audio tape is not in service. The number that
precedes MTDOS indicates the number of MTDs or DATS not in service.
Result
A loss of billing data occurs if the DIRP utility uses the MTD or DAT to
record billing data. If the DIRP utility does not use the MTD or DAT, files
can not download to or from tape.
Common procedures
Action
instructions in the step–action procedure that follows the flowchart to clear
the alarm.
Do not proceed to the common procedure unless the step–action procedure

directs you to go.
GSP05 (CSP10)

minor (continued)
Summary of Clearing an IOD nMTDOS on an IOM minor alarm

procedure.
Display the
status of MTD Use the instructions that follow this
or DAT port flowchart to perform the procedure.
Is the MTD N Is the MTD N Is the MTD N

status CBsy or status OffL? status ManB? 3
SysB?
Y Y Y
Select a new When possible, Return the MPC

port. Offline and busy the MPC or DAT port to
test the port or DAT port service
2 2
Is a smart N Select an open Is a port N Provision

connector port available? another IOM
present?
Y Y
Change and test Move the smart Move the smart

the connector cable cable
1
1 1
Return the port
and links to
service
N Contact next
Passed? 3 End
level of support 4
Y
4
297-2651-543 Standard 05.01 March 1999


minor (continued)
Clearing an IOD nMTDOS on an IOM minor alarm
ATTENTION
The step in the IOD nMTDOS in an IOC minor alarm clearing
procedure directs you to this procedure. Do not proceed at any
other time.
At the MAP terminal

1 To post the controller system connected to the magnetic tape drives (MTD) or
digital audio drive (DAT), type
>IOC ioc_no
where
IOC PORT 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
(IOM) STAT . . . – . . – – – . – – – – – – – –
O O O O T P C C
N N N N D C S S
GSP05 (CSP10)

minor (continued)
2 To display the status of all the MTD or the DAT, type

>LISTDEV MTD
3 From the status display, determine the status of the MTD or DAT.
If the status Do
is SysB MTD step 4

is SysB DAT step 6
is CBsy (C-side busy) step 58
is OffL (offline) or step 60
ManB (manual busy)
4 To post the affected MTD port, type

>PORT port_no
where
port_no is the number of the affected MTD (0-15)
Port 5 MTD 0 DevType
TapeName User
Status Idle
5 Go to step 7.
6 Post the affected DAT port, type

>PORT port_no
where
port_no is the number of the affected DAT port (16-17)
Port 16 MTD 0 DevType DAT
(SCSI) TapeName User
Status Idle
297-2651-543 Standard 05.01 March 1999


minor (continued)
7 Make sure the MTD or DAT is demounted.
If the MTD or DAT Do
is demounted step 9
is not demounted step 8
8 To demount the MTD or DAT, type

>DEMOUNT tape_name
where
9 To manually busy the MTD or DAT, type
>BSY

bsy
OK
If the device Do
is MTD step 10
is DAT step 13

10 Determine if the MTD contains a loaded tape.
If the MTD Do
contains a loaded tape step 11

does not contain a loaded tape step 19
11 Unload the tape on the MTD from the drive unit.
12 Go to step 19.
GSP05 (CSP10)

minor (continued)
At the ISM shelf
13 Determine if the storage media card NTFX32AA contains a DAT cartridge in the
drive unit.
If the NTFX32AA Do
contains a cartridge step 14

does not contain a cartridge step 15
14
WARNING
Ejection of a tape cartridge
Force eject a cartridge a last resort to recover a
eject the cartridge. You can lose data and the tape can
format wrong.
WARNING
Ejection of a tape cartridge
Force eject a cartridge a last resort to recover a
eject the cartridge. You can lose data and the tape
can format wrong.
Press the unload button at the front of the unit to remove the DAT cartridge.
The DAT LED flashes during the removal of the tape.
Note: The drive performs an unload sequence. The drive rewinds the tape to
the beginning of partition (BOP) for partition 0. If the tape is write-enabled, the
drive writes a copy of the tape log back to tape. The drive rewinds the tape to
the start of the media. The drive removes the thread and ejects the tape from
the mechanism.
297-2651-543 Standard 05.01 March 1999


minor (continued)
15 Locate the DAT drive on the media card NTFX32AA slots 4 and 5 of the ISM
shelf. Check the LEDs for the current condition of the DAT unit.
The DAT clean/attention lights Do
are on step 16
are off step 19
16 The status of the DAT LEDs indicates that the drive heads require cleaning.
The DAT LEDs also indicates when a cartridge is not useful. Clean the drive
heads or change the cartridge. Perform the correct procedure in Routine
Maintenance Procedures to clean the drive heads or to change the cartridge.
Return to this point
The DAT clean/attention lights Do
are off step 19

are not off step 17
17 The DAT unit requires replacement. Perform the correct procedure in Trouble
Locating and Clearing Procedures to replace the DAT. Return to this point.
GSP05 (CSP10)

minor (continued)
18 Go to step19
At the MAP terminal
19
CAUTION
Loss of MTD or DAT data
Make sure the MTD or the DAT drive on the storage
media card NTFX32 do not contain the tape. If you
test a MTD or DAT that contain a tape, you can
damage data on the tape.
CAUTION
Loss of MTD or DAT data
Make sure the MTD or the DAT drive on the storage
media card NTFX32 do not contain the tape. If you
test a MTD or DAT that contain a tape, you can
damage data on the tape.
To test the MTD or DAT devices, type

>TST
passed step 46
failed test, controller okay step 46
failed, (MTD) port CFG fail step 22
failed, (DAT) port CFG fail step 20
generated
20 Ensure that the media storage card NTFX32 and the DAT drive NTFX32AA are
mounted. Refer to the appropriate procedure in Trouble Locating and Clearing
Procedures and return to this point.
21 Go to step 46.
297-2651-543 Standard 05.01 March 1999


minor (continued)
22 To place the MTD offline, type

>OFFL

>QUIT
24 To make the MTD port manually busy, type

>BSY PORT port_no
where
port_no is the number of the MTD port
bsy
OK
GSP05 (CSP10)

minor (continued)
25 To place the affected MTD port offline, type

>OFFL PORT port_no
where
26 To test the MTD port, type
>TST PORT port_no
where
Failed
If a SMART connector Do
is identified step 27
is not identified step 33

27 Locate the PERTEC SMART connector mounted on an L-shaped bracket near
the tape drive. Check the SMART connector LED. Replace the SMART
connector.
297-2651-543 Standard 05.01 March 1999


minor (continued)
28 To test the SMART connector, type

>TST PORT port_no
where
Failed
If the SMART connector Do
passes step 29
fails step 33
29 Manually busy the MTD port by typing

>BSY PORT port_no
where
port_no is the port number of the MTD device
30 Return the MTD port to service by typing

>RTS PORT port_no
where
31 Post the MTD port by typing
>PORT port_no
where
32 Go to step 57.
GSP05 (CSP10)

minor (continued)
If a port is Do

controller
available on another IOM controller step 42
there is no other IOM controller step 44
available
34
CAUTION
Assistance in provisioning changes
Contact the provisioning administrator if you require
support before you proceed with the following
provision changes.
CAUTION
Assistance in provisioning changes
provision changes.
type
>TABLE IOC
35 To access the table MTD, type

>TABLE MTD
36 Delete the tuple associated with the affected port.
37 Add the tuple for the spare IOM port selected in step 33.
297-2651-543 Standard 05.01 March 1999


minor (continued)
38 To post the new IOM MTD port, type

>PORT port_no
where
Port 6 MTD 0 DevType DAT
(SCSI) TapeName User
Status Idle
39 To make the IOM MTD port manually busy, type

>BSY
bsy
OK

40
WARNING
When you handle SMART connectors, wear a wrist
strap that connects to the wrist-strap grounding point.
A grounding point is on a frame supervisory panel
(FSP) or a modular supervisory panel (MSP). The
wrist strap protects the connectors against static
electricity damage.
GSP05 (CSP10)

minor (continued)
CAUTION FOR ESDS

When you handle SMART connectors, wear a wrist
strap that connects to the wrist-strap grounding point.
A grounding point is on a frame supervisory panel
wrist strap protects the connectors against static
electricity damage.
Locate the SMART cable that connects to the MTD port on the paddle board
and the associated MTD device. Disconnect the SMART cable and connect it
to the new MTD port.
Go to step 41.
41 To return the MTD to service, type

>RTS
passed step 47
failed, no port available step 42
42 To post another controller system, type

>IOC ioc_no
where
Example of an IOM MAP:
IOC PORT 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
(IOM) STAT . . . – . . – – – . – – – – – – – –
O O O O T P C C
N N N N D C S S
43
297-2651-543 Standard 05.01 March 1999

minor (continued)
Select an open IOM port on the new controller.
A port Do
44
CAUTION
provision changes.
CAUTION
provision changes.
Provision another IOM module. Consult your provisioning administrator about

the addition of an IOM controller card.
45 Go to step 65.
46 To return the MTD to service, type

>RTS
passed step 47
card list g
47 Perform the correct procedure in Routine Maintenance Procedures. to load the

tape on the MTD or DAT unit. Complete the procedure and return to this point.
GSP05 (CSP10)

minor (continued)
48 To reload and mount the tape, type

>MOUNT mtd_no
where
49 Go to step 63.
50 Test the MTD by typing

>TST PORT port_no
where
Failed
passes step 56
failed with a card list step 51
failed without acard list step 65
51 Record the location, description, slot number, product engineering code (PEC)
and PEC suffix of the cards on the list.

Note: If the input/output message processor card requires replacement, first
make sure that the IOM is manual busy.
297-2651-543 Standard 05.01 March 1999


minor (continued)
53 To test the MTD or DAT units, type

>TST
passes step 56
the cards in the list recorded in
step 51
failed, and you did replace all the step 65

55 Go to step 53.
56 Perform the correct procedure in Routine Maintenance Procedures. to load the

tape on the MTD or DAT unit. Complete the procedure and return to this point.
57 To return the MTD or DAT to service, type

>RTS
passed step 63
failed step 65
GSP05 (CSP10)

minor (continued)
58 To post the controller system connected to the MTD, type

>IOC ioc_no
where
IOD
IOC 0 1 2 3
STAT . . . S

IOC PORT 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
(IOM) STAT . . . – . . – – – . – – – – – – – –
O O O O T P C C
N N N N D C S S
If the IOM Do
is in service step 66
is not in service step 59
59 Perform the procedure Clearing an nIOCOS major or minor alarm in this

document to clear this alarm. Complete the procedure and return to this point.
If the alarm Do
cleared step 66
297-2651-543 Standard 05.01 March 1999


minor (continued)
MTD or DAT is offline or manual busy. When acceptable, return the MTD or
DAT to service.
If the MTD or DAT Do
is offline step 61
is manual bsy step 62
61 To make the MTD or DAT port manually busy, type

>BSY
62 To return the MTD or DAT to service, type

>IOC ioc_no;PORT port_no;RTS
where
port_no is the number of the MTD or DAT port
passed step 66
failed step 65
63 Determine if the nMTDOS minor alarm cleared.
If the alarm Do
cleared step 66
GSP05 (CSP10)

minor (continued)
(end)
297-2651-543 Standard 05.01 March 1999

IOD nMPCOS on an IOM

major or minor
Alarm display
. . nMPCOS . . . . . . .
Indication
At the IOD level of the MAP display, MPCOS [preceded by a number (n)]
indicates an input/output module (IOM) major or minor alarm.
Meaning
One or more IOM controller ports are out of service. The number that
precedes MPCOS indicates the number of IOM controller ports out of
service.
Result
Multiple controller ports in the IOM controller on the integrated services
module (ISM) shelf are out of service. Loss of access to the switch by
remote terminals is a result.
Common procedures
Action
The flowchart is a summary of this procedure. Use the instructions in the
GSP05 (CSP10)

Summary of Clearing an IOD nMPCOS on an IOM major or minor alarm
Display the This flowchart summarizes the

status of MPC procedure.
port
Is the MPC N
status CBsy or
SysB?
Is the MPC N Is the MPC N
Y status OffL? status ManB? 3
Has the MPC N Y Y

lost its load? 1
When possible, Return the MPC
Y busy the MPC card and links to
card and links service
2 2
Select new port,
offline and test
N Select open port Port N Supply another

Smart
connector? available? IOM
Y Y
connector and cable cable
test
1 1 1
Return the port
and links to
service
N Contact next
Passed? 3 End
level of support 4
4 Y
297-2651-543 Standard 05.01 March 1999


Clearing an IOD nMPCOS on an IOM major or minor alarm
ATTENTION
Proceed only if a step in the IOD nMPCOS in an IOC major or
minor alarm clearing procedure directs you to.
At the MAP terminal

>IOC ioc_no
where
IOC PORT 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
(IOM) STAT . . . – . . – – – . – – – – – – – –
O O O O T P C C
N N N N D C S S
2 From the MAP display, determine the status of the IOM port.
If the status Do
is CBusy (C-side busy) or step 3

SysB (system busy)
is OffL (offline) step 39
is ManB (manual busy) step 41
GSP05 (CSP10)

3 To display the status of the IOM controller, type

>QIOM
Port IOC: 0 Node_no: 6; Status: SBSY; State: DNLDED
Table IOC File: IOMR0001 on D00DV002
IOM load on board: IOMR0001; Auto_Load: ON
Site Flr Rpos Bay_id Shf Description Slot EqPEC
HOST 01 A05 ISME 03 32 IOC 03 FX30BA
Port Info: (C-CON, M-MPC, D-DDU, T-MTD, s-SCSI, F-Fault
PORT 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
C C C – C T – – – M – – – – – – sD sT
. . . . . . . . . F . . . . . . . .
4 Determine the following information from the MAP response:

• the status of the IOM controller
• data entry in table IOC
• the state of the autoload
If the IOM controller Do
has no load, and autoload is ON step 5

has no load, and autoload is OFF step 7
loaded step 8
5 Wait for 2 min for the audit procedure to work. The process will make three
attempts before the failure to load is complete.
loaded step 8
did not load step 6
297-2651-543 Standard 05.01 March 1999


6 Review log IOD610 and verify that the load file is correct and available.
7 Determine from table IOC if the open port contains the correct load device. If
necessary, enter the correct load file in table IOC again.
Note: The input/output controller (IOC) audit must put into effect
auto_downloading every two minutes for three reports that follow in sequence.
loaded step 8
did not load step 45
8 To post the affected IOM MPC port , type

>PORT port_no
where
Example of a MAP:
Port 9 Unit 1
9 To manually busy the affected MPC,type

>BSY

bsy
OK
GSP05 (CSP10)

10 To test the MPC, type

>TST
passed step 42
card list
MPC logs
11 To put the MPC offline, type

>OFFL

>QUIT
13 To busy the IOM MPC port, type

>BSY PORT port_no

bsy
OK
297-2651-543 Standard 05.01 March 1999


14 To place the MPC port offline, type

>OFFL PORT port_no
15 To test the IOM MPC port, type

>TST PORT port_no
where
Failed
Check and replace smart connector for port 9 (FX34, FX35)
16 Determine if the test identified smart connectors.
If the test Do
identified smart connectors step 17

did not identify smart connectors step 19
GSP05 (CSP10)

17
WARNING
When you handle smart connectors, wear a wrist strap
that connects to a wrist–strap grounding point. The
grounding point is on a frame supervisory panel (FSP)
or a modular supervisory panel (MSP). The wrist
strap protects against static electricity damage.
CAUTION FOR ESDS

When you handle smart connectors, wear a wrist
strap that connects to a wrist–strap grounding point.
The grounding point is on a frame supervisory panel
wrist strap protects against static electricity damage.
Locate the SMART cable that connects the MPC port on the paddleboard and
the associated MPC device. Disconnect the 9–pin connector on the IOM side
and a 25-pin connector on the MPC side. Check the smart connector LED.
Replace the smart connector. Connect the 9–pin and 25-pin connectors again.
18 To test the smart connector, type

>TST PORT port_no
where
Failed
passes step 42
fails step 19
297-2651-543 Standard 05.01 March 1999


19 Go to step 1. Select an open IOM port and return to this point.
If Do
a port is not available on the posted step 20

IOM
a port is available on another IOC step 33
no other IOC is available step 45
20
CAUTION
Help with provisioning changes
CAUTION
Help with provisioning changes
type
>TABLE IOC

>TABLE MPCLINK
22 Delete the link tuple for the affected port.
GSP05 (CSP10)


>TABLE MPC
24 Delete the tuple for the affected port.

>TABLE MPC
26 Add the link tuple for the spare IOM port selected in step 19.

>TABLE MPCLINK
Add the tuple for the spare IOM port selected in step 19.
Table: MPC
28 To post the selected MPC, type

>PORT port_no
where
port_no is the number of the IOM MPC port
Example of a MAP:
Port 9 Unit 1
297-2651-543 Standard 05.01 March 1999


29 To make the MPC manually busy, type

>BSY

bsy
OK

30
WARNING
When you handle smart connectors, wear a wrist strap
that connects to a wrist–strap grounding point. The
grounding point is on a frame supervisory panel (FSP)
and the modular supervisory panel (MSP). The
wrist–strap protects the smart connectors against static
electricity damage.
CAUTION FOR ESDS

When you handle smart connectors, wear a wrist
strap that connects to a wrist–strap grounding point.
The grounding point is on a frame supervisory panel
(FSP) and the modular supervisory panel (MSP).
The wrist–strap protects the smart connectors against
static electricity damage.
Locate the SMART cable that connects the MPC port on the paddleboard and
the associated MPC device. Disconnect the 9–pin connector on the IOM side
and a 25-pin connector on the MPC side. Replace the smart connector.
Connect the 9–pin and 25-pin connectors again.
GSP05 (CSP10)

At the MAP terminal
31 To post the MPC port, type
>PORT port_no
port_no is the number of the selected MPC port
bsy
OK
32 To return the MPC to service, type

>RTS
passed step 46
failed step 45
33 To post another controller system, type

>IOC ioc_no
where
IOC PORT 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
(IOM) STAT . . . – . . – – – . – – – – – – – –
O O O O T P C C
N N N N D C S S
297-2651-543 Standard 05.01 March 1999


34 Select an open IOM port on the new controller selected in step 33.
A port Do
35
CAUTION
changes.
CAUTION
changes.
You need to provision another IOM module. Consult your provisioning

administrator to add an IOM controller card.
Go to step 45.

GSP05 (CSP10)

37 To test the card, type

>TST

Failed
If the test Do
passes step 42
fails, you did not replace all cards step 38
fails, you replaced all cards step 45

next card from the list. Complete the procedure and go to step 37.

>PORT port_no
where
Example of a MAP:
Port 9 Unit 1
40 Consullt office records or operating company personnel. Determine the reason

that the IOM port is offline. To manually busy the IOM MPC, type
>BSY

bsy
OK
297-2651-543 Standard 05.01 March 1999


Go to step 42.
41 Consult office records or from operating company personnel. Determine the

reason that the MPC port is manually busy. To post the MPC port, type
>PORT port_no
where
port_no is the number of the busied port
Port 9 Unit 1
42 To return the IOM MPC to service, type

>RTS
passed step 43
failed step 45
43 Check under the IOD banner of the MAP display to determine if the nMPCOS
If the alarm Do
cleared step 46
Go to step 43.
GSP05 (CSP10)

(end)
297-2651-543 Standard 05.01 March 1999

IOD PnnVnn
minor
Alarm display
. . PnnVnn . . . . . . .
Indication
At the IOD level of the MAP display, P followed by a number (nn) and V
followed by a number (nn) indicates a pool volume minor alarm.
Meaning
The recording volume identified by Vnn in the recording pool that is
identified by Pnn has less than 1 Mbyte of free space, or has been marked
INERROR by the DIRP utility.
Impact
Common procedures
The following common procedures are referenced:
Action
the alarm.
GSP05 (CSP10)
IOD PnnVnn
minor (continued)
Summary of Clearing an IOD PnnVnn minor alarm
Access table This flowchart summarizes the

DIRPPOOL procedure.

Identify affected flowchart to perform the
volume procedure.
Reset the
affected volume
Remove
Alarm N unnecessary
cleared? files from
affected volume
Y
Reset volume
Alarm N Deallocate old Allocate new

cleared? volume volume
End
297-2651-543 Standard 05.01 March 1999

IOD PnnVnn
minor (continued)
Clearing an IOD PnnVnn minor alarm
At the MAP
1
CAUTION
If you fail to use this procedure or to follow it exactly,
you may lose or corrupt your AMA data. Because
AMA data is used to produce billings, loss or
corruption of AMA data results in a revenue loss for
the operating company.
Access the MTC level of the MAP display by typing

>MAPCI;MTC
2 Silence the audible alarm by typing

>SIL
3 Note and record the time the alarm occurred, and the pool and volume
numbers that are indicated by nn in the PnnVnn alarm.
4 Access the DIRPPOOL table by typing

>TABLE DIRPPOOL
TABLE: DIRPPOOL
GSP05 (CSP10)
IOD PnnVnn
minor (continued)
5 Locate the pool number that is associated with this alarm by typing
>POSITION pool_no
where
pool_no is the pool number (nn)
0 AMAPOOL REGULAR TAPE $ $ $ $
$ $ $ $ $ $ $ $
$ $ $ $ $ $ $ $
$ $ $ $
6 List the pool number and pool name that is associated with this alarm by typing
where
VOLUME22 VOLUME23
0 AMAPOOL REGULAR TAPE $ $ $ $
$ $ $ $ $ $ $ $
$ $ $ $ $ $ $ $
$ $ $ $
7 Record the pool name shown under the POOLNAME field.

Note: For example, in the MAP response in the previous step, the
POOLNAME is AMAPOOL.
8 Record the name of the affected volume under VOLUMEnn2.

Note: nn2 is the DIRPPOOL table volume number indicated in the alarm.
9 Exit the DIRPPOOL table by typing

>LEAVE
297-2651-543 Standard 05.01 March 1999

IOD PnnVnn
minor (continued)
10 Access the DIRPSSYS table by typing

>TABLE DIRPSSYS
TABLE: DIRPSSYS
11 List the tuples by typing

>LIST ALL
12 Record the subsystem name under the header SSYSNAME.

SSYSNAME READRITE NUMFILES MINFILES POOLNAME FILENAME ALARM0 ALARM1
ALARM2 ALARM3 RETPD CRETPD PARLPOOL PARCONC MANDPALM FILEDATE SHEDDAYS
SHEDBASE SHEDINCR ROTACLOS AUTOXFER SPACROTE MAXDFSIZ PRIORTIO
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
AMA Y 1 0 AMAPOOL $ NA NA
NA NA 30 30 $ N NA OPENED NNNNNNN
0 NOROTATE NONE NONE N 64 YDLOG Y
1 0 DLOGPOOL $ NA NA
NA NA 0 0 DLOGPARL N NA FIRSTACT NNNNNNN
0 NOROTATE BOTH NONE N 6 NJF Y
1 0 JFPOOL $ NA NA
0 NOROTATE NONE NONE N 64 YOM Y
1 0 OMPOOL $ MN NA
0 NOROTATE NONE NONE N 64 Y
13 Exit the DIRPSSYS table by typing

>LEAVE
GSP05 (CSP10)
IOD PnnVnn
minor (continued)
14 Access the DIRP level of the MAP display by typing

>IOD;DIRP
IOD
IOC 0 1 2
STAT . L .

15 Determine if this is the second time in 5 min that this alarm has occurred for this
volume.
If Do
this is the second time in 5 min that step 33

the alarm has occurred
this is not the second time in 5 min step 16
that the alarm has occurred
16 Reset the affected volume by performing the common procedure Resetting a

volume in this document. When you have completed the procedure, return to
this point.
17 Determine if the PnnVnn alarm cleared.
If the alarm Do
cleared step 53
297-2651-543 Standard 05.01 March 1999

IOD PnnVnn
minor (continued)
18 The next step depends on the type of volume you are working on.
If you are working on Do
an SLM volume step 19

a DDU volume step 20
19 Access the disk utility by typing

>DISKUT
Go to step 21.

>DSKUT
21 List the files on the affected volume by typing

>LISTVOL vol_name ALL
where
vol_name is the name of the volume (nn)
Volume information for SLM disk 0
Volume Modify Total No. of ITOC
Name Date No. of Open Files
Y/M/D Files Files
––––––––– ––––––– –––––––– ––––––– ––––
S00dvol1 870122 876 2 15
S00Dvol2 861121 14 14 0
S00Dvol3 861121 0 0 0
S00Dvol4 861121 2048 100 0
S00Dvol5 861121 1 0 1
22 Leave the disk utility by typing

>QUIT
GSP05 (CSP10)
IOD PnnVnn
minor (continued)
23 Determine if the subsystem is recording to tape or disk.
If the subsystem is recording to Do
tape step 24
disk step 26
24 Remove any unnecessary files from the affected volume by typing

>CLEANUP VOLUME vol_name
where
25 Reset the affected volume by performing the common procedure Resetting a

volume in this document. When you have completed the procedure, go to
step 28.
26 Deallocate the volume by performing the common procedure Deallocating a

this point.
27 Allocate the volume by performing the common procedure Allocating a volume

in this document. When you have completed the procedure, return to this point.
If the alarm Do
cleared step 53
29 Check office records for an available recording volume.
30 Deallocate the full volume by performing the common procedure Deallocating a

this point.
31 Allocate a new volume by performing the common procedure Allocating a

this point.
297-2651-543 Standard 05.01 March 1999

IOD PnnVnn
minor (continued)
If the alarm Do
cleared step 53
33 Contact your maintenance support group and notify them of the situation.
If your maintenance support

group instructs you Do

34 Deallocate the affected volume by performing the common procedure

Deallocating a volume in this document. When you have completed the
35 Attempt to reallocate the affected volume by performing the common procedure

Allocating a volume in this document. When you have completed the
36 Determine if the volume reallocated.
If the volume Do
reallocated step 37
did not reallocate step 38
If the alarm Do
cleared step 53
GSP05 (CSP10)
IOD PnnVnn
minor (continued)
38 Deallocate the affected volume by performing the common procedure

Deallocating a volume in this document. When you have completed the
39 The next step depends on the type of volume you are working on.
If you are working on Do
an SLM volume step 40

a DDU volume step 41

>DISKUT
Go to step 42.

>DSKUT
42 List the files on the affected volume by typing

>LISTVOL vol_name ALL
where
Y/M/D Files Files
––––––––– ––––––– –––––––– ––––––– ––––
S00dvol1 870122 876 2 15
S00Dvol2 861121 14 14 0
S00Dvol3 861121 0 0 0
S00Dvol4 861121 2048 100 0
S00Dvol5 861121 1 0 1
297-2651-543 Standard 05.01 March 1999

IOD PnnVnn
minor (continued)
43 Leave the disk utility by typing

>QUIT
44 Determine if the subsystem is recording to tape or disk.
If the subsystem is recording to Do
tape step 49
disk step 45
45 Remove any unnecessary files from the affected volume by typing

>CLEANUP VOLUME vol_name
where
46 Determine from office records the location of an available disk volume for
recording subsystem data.
47 Attempt to reallocate the affected volume by performing the common procedure

Allocating a volume in this document. When you have completed the
48 Go to step 51.
49 Deallocate the tape volume by performing the common procedure Deallocating

a volume in this document. When you have completed the procedure, return to
this point.
50 Allocate the tape volume by performing the common procedure Allocating a

this point.
If the alarm Do
cleared step 53
GSP05 (CSP10)
IOD PnnVnn
minor (continued)
(end)
support.
297-2651-543 Standard 05.01 March 1999

IOD POOLnn
minor
Alarm display
. . POOLnn . . . . . . .
Indication
At the IOD level of the MAP display, POOL followed by a number (nn)
indicates a pool minor alarm.
Meaning
The data entries in table DIRPPOOL contain a pool. The data entries in
table DIRPSSYS do not contain a pool.
Result
Common procedures
Action
step-action procedure to clear the alarm.
GSP05 (CSP10)
IOD POOLnn
minor (continued)
Summary of Clearing an IOD POOLnn minor alarm

Access table
procedure.
DIRPPOOL
Use the instrunctions that
follow this flowchart to perform
the procedure.
Position the
pool number
Access table
DIRPSSYS
Position the
subsystem
Y Change the Change the

Pool type 1
parallel pool parallel
parallel?
name recording
N
Y Change the End

Pool type pool name 1
regular?
Contact next
level of support
297-2651-543 Standard 05.01 March 1999

IOD POOLnn
minor (continued)
Clearing an IOD POOLnn minor alarm
At the MAP terminal
1 Record the pool number in the alarm (nn is the pool number).
2 To access the DIRPPOOL table, type

>TABLE DIRPPOOL
TABLE: DIRPPOOL

where
VOLUME22 VOLUME23
0 ssysPOOL REGULAR TAPE $ $ $
$ $ $ $ $ $ $
$ $ $ $ $ $
$ $ $ $ $ $
T1 T2
4 Record the device type shown in the DEVTYPE field, the pool name shown in
the POOLNAME field, and the pool number shown in the POOLNO field.
Note: For example in the MAP response in the previous step, the device type
is TAPE, the pool name is ssysPOOL, and the pool number is 0.

>LEAVE
GSP05 (CSP10)
IOD POOLnn
minor (continued)
6 To access table DIRPSSYS, type

>TABLE DIRPSSYS
TABLE: DIRPSSYS
7 To position on the subsystem, type

>POSITION ssys;LIST
where
ssys is the name of the subsystem.
SYSNAME READWRITE NUMFILES MINFILES POOLNAME FILENAME ALARM0 ALARM1

ALARM2 ALARM3 RETPD CRETPD PARLPOOL PARCONC MANDPALM FILEDATE SHEDDAYS
SHEDBASE SHEDINCR ROTACLOS AUTOXFER SPACROTE MAXDFSIZ PRORTID
AMA Y 1 0 AMADISK $ NA NA
14 NOROTATE BOTH FULL N 64 Y
8 Determine if the pool type is parallel.
If the pool type Do
is parallel step 10
is not parallel step 9
9 Determine if the pool type is normal.
If the pool type Do
is normal step 13
is not normal step 21
297-2651-543 Standard 05.01 March 1999

IOD POOLnn
minor (continued)
10 To change the name of the parallel pool, type

>CHANGE PARLPOOL pool_name
where
pool_name is the pool name determined in step 4
ENTER Y TO CONTINUE PROCESSING OR N TO QUIT

>Y
12 To change the parallel recording, type

>CHANGE PARCON Y
TYPE OF PARLPOOL IS POOLNAMESR
TYPE IS POOLNAMESR
{AMAPOOL,OMPOOL,JFPOOL,OCCPOOL,OCCDISK,DLOGPOOL,
DLOGPARL$}
PARLPOOL:
Go to step 18.
GSP05 (CSP10)
IOD POOLnn
minor (continued)
13 To change the pool name, type

>CHANGE POOLNAME pool_name
where
pool_name is the pool name determined in step 4
14 Determine if you want to continue to change the pool name.
If you Do
want to continue step 15

do not want to continue step 16
15 To confirm the change, type

>YES
Go to step 18.
16 To halt the change, type

>NO
17 To leave the table, type

>LEAVE
Go to step 22.
18 To leave the table, type

>LEAVE
19 To return to the DIRP level of the MAP display, type

>MAPCI;MTC;IOD;DIRP
297-2651-543 Standard 05.01 March 1999

IOD POOLnn
minor
minor
(continued)
(end)
20 Determine if the POOLnn alarm cleared.
If the alarm Do
cleared step 22
GSP05 (CSP10)
IOD SCAX25
major
Alarm display
CM MS IIOD Net PM CCS Lns Trks Ext APPL
. . SCAX25. . . . . . .
Indication
At the IOD level of the MAP display, SCAX25 indicates a fault with the
IOC link for CompuCALL.
Meaning
A problem is present inside the central office (CO) with connections at the
host, or outside the CO with either the data link or with the customer
premises equipment (CPE).
If the problem is inside the CO, the CO maintenance personnel need to

check physical connections, verify that the session is logged on, and perform
a continuity test for a switch-computer application interface (SCAI).
If the problem is outside the CO, the CO maintenance personnel need to

contact the appropriate field service personnel and inform them that a
problem exists with either the data link or the CPE.
Impact
CompuCALL session cannot be activated.
Common procedures
Not applicable
Action
the alarm.
297-2651-543 Standard 05.01 March 1999

IOD SCAX25
major (continued)
Summary of clearing an IOD SCAX25 alarm
Access
SCAIX25 level This flowchart summarizes the
at MAP procedure.

Query alarm.
Based on alarm
procedure.
reason, fix the
trouble.
Does CO Replace data

data unit or modem Y unit or modem
fail self-test?
N
Are cables Y Tell customer to

Connect cables
disconnected? re-establish link
N Inform
Tell customer to customer
Is session N Does problem Y that
log on still exist?
logged on? problems
Y N exist on
link or at
Perform CPE
Did continuity N
continuity test
test pass?
from SCAIX25
level Y
Inform customer
End
that problems
exist on link or
at CPE
GSP05 (CSP10)
IOD SCAX25
major (continued)
At the MAP terminal
23 Access the SCAIX25 level of the MAP display by typing
>MAPCI;MTC;IOD;SCAIX25
24 Query the alarms by entering

>QUERY ALARM
Severity M L C Remote_ DNA Reason
CRIT 0 2 1 01208097 DMS LVL3 reset
25 Check the text in the Reason field. The MAP display states the SCAI link is
clear or states a reason for a problem.
If the reason displayed Do
is SCAI application clear step 27

is Host call cleared step 31
is Host LVL3 reset step 31
is DMS LVL3 reset step 26
is MPC SysBusied step 26
is MPC link reset step 26
26 Exit the SCAIX25 MAP level by typing

>QUIT
At the IOD shelf
27 To verify the operation of the CO data unit, perform a self-test on the NT4X25
data unit.
Lift the flip-flop lid of the data unit. Toggle the self-test/normal option switch to
the self-test position and back to the normal position.
You will hear a short beep. After a short delay, all LEDs on the data unit will
illuminate for approximately four seconds.
If the directory number LEDs flash, the system indicates a self-test failure.
297-2651-543 Standard 05.01 March 1999

IOD SCAX25
major (continued)
You will hear a short beep. All LEDs turn off except the power LED.
If the CO data unit Do
fails the self-test step 28

passes the self-test step 29
28 Replace the data unit with a new data unit.
29 Check for disconnected cables between the MPC circuit pack and the data unit
or modem. Also check between the data unit or modem and the jack.
The 32-pin connector of the cable connects to either port 2 or port 3 of the MPC
circuit pack.
The 25-pin connector of the cable connects to the data unit or modem.
The data unit or modem connects to the jack by a cable with RJ11 connectors.
If the connect light on the data unit flashes, the data unit is bad or you must
disconnect the cable.
If Do
you find disconnected cables step 30

you do not find disconnected cables step 31
30 Connect the disconnected cables.

At the MAP terminal
31 The problem is not located inside the CO.
Access the IOD level of the MAP display by typing
>MAPCI;MTC;IOD
32 Post the MPC by typing

>IOC n;CARD y
where
n is the number of the IOC shelf the MPC resides
y is the number of the MPC card.
GSP05 (CSP10)
IOD SCAX25
major (continued)
(end)
33 Determine if the session is logged on. “ L” indicates the session is logged on..
If the session Do
is logged on step 36
is not logged on step 34
34 Inform the subscriber the session is not logged on. The subscriber must log on
to clear the problem.
35 Go to step 41.
36 Access the SCAIX25 level of the MAP display by typing

>SCAIX25
37 Perform a SCAI continuity test by typing

>SCAITEST
If the test Do
fails step 38
passes step 39
38 Tell the subscriber to establish the link again and to log on.
If the trouble Do
no longer exists step 40

still exists step 39
39 Inform operating company personnel a problem is present in the data link

outside the CO or with the customer premises equipment.
297-2651-543 Standard 05.01 March 1999

IOD SENDn
minor
Alarm display
. . SENDn . . . . . . .
Indication
At the IOD level of the MAP display, SEND followed by a number (n)
indicates a SENDn minor alarm.
Meaning
Data tape on a recording device requires transport to a remote data center.
The number after SEND represents the number of the recording device that
holds the mounted tape.
Result
Common procedures
This procedure refers to How to allocate a volume.
Action
GSP05 (CSP10)
IOD SENDn
minor (continued)
Summary of Clearing an IOD SENDn minor alarm

Determine the Use the instructions that follow this
location of the flowchart to perform the procedure.
file
N N Contact next
File on disk? File on tape? level of support
Y Y
Mount the tape. Demount the

Refer to the tape
correct NTP.
Transfer the file Unload the tape

to tape and package for
transport
Demount the Clear the alarm

tape
1
Unload the tape
and package for
transport
Clear the alarm
End
297-2651-543 Standard 05.01 March 1999

IOD SENDn
minor (continued)
Clearing an IOD SENDn minor alarm
At the MAP terminal
1 To access the transfer (XFER) level of the MAP display, type
>MAPCI;MTC;IOD;XFER
2 To list the files requested by the data center, type

>QUERY SENT
3 Determine where the file is stored. Note the number in the HOLDNO field, and
the volume name in the FILE_LOCN field.
If the file storage Do
is on disk step 4
is on tape step 11
(MTD). Record the MTD number.
5 Perform the correct procedure in Routine Procedures to mount the tape.

6 Transfer the file to tape. Use the file noted in step 2. Type
>DIRPCOPY file_name dev_name
where
file_name is the name of the file noted in step 2
dev_name is the name of the device the file is on
7 To demount the tape from the MTD, type

>DIRPCOPY tape_name dev_name
where
tape_name is the name of the tape the file is on
dev_name is the name of the device
GSP05 (CSP10)
IOD SENDn
minor (continued)
At the shelf
8 Unload the tape from the MTD and package the tape. Transport the tape to a
remote data center.
At the MAP terminal
>SENT nn
where
10 Determine if the SENDn alarm cleared.
If the alarm Do
cleared step 22
11 Determine from office records the MTD holds the tape.

>DIRP
13 To determine if the file that will transfer is the active file, type
>QUERY ssys FILE
where
If the file Do
is active step 14
14 To allocate the DIRP disk recording volumes, perform the common procedure
Allocating a volume in this document. Complete the procedure and return to
this point.
297-2651-543 Standard 05.01 March 1999

IOD SENDn
minor
minor
(continued)
(end)
15 To make the new volume the active volume, type

>ROTATE ssys_name REGULAR
where
ssys_name is the affected subsystem

>DMNT ssys_name vol_name
where
ssys_name is the affected subsystem
vol_name is the name of the volume
At the shelf
17 Unload the tape from the MTD. Prepare to transport the tape to the remote
data center.
At the MAP terminal
18 To access the XFER level of the MAP display, type
>XFER
19 To clear the SENDn alarm, type

>SENT nn
where
20 Determine if the SENDn alarm cleared.
If the alarm Do
cleared step 22
GSP05 (CSP10)
IOD SLMbsy
major
Alarm display
. . SLMbsy . . . . . . .
M
Indication
At the MTC level of the MAP display, SLMbsy appears under the IOD
header of the alarm banner. The SLMbsy indicates an SLMbsy major alarm.
Meaning
At least one system load module (SLM) is system busy.
Result
If one SLM is system busy, service can continue. For service to continue,
the bootable computing module (CM) and message switch (MS) files must
be on the in service SLM. Service loss occurs if a reload initiates and both
SLMs are system busy. Service loss can occur if the only bootable CM and
MS files are located on a system busy SLM.
If one SLM is system busy and the in-service SLM has enough recording
volumes, the system maintains billing service information. If both SLMs
are system busy, loss of billing service information occurs. If one SLM is
system busy, and the other does not have enough recording volumes, loss of
billing service information occurs. Automatic message accounting (AMA)
is an example of billing service information.
Common procedures
Action
the alarm.
297-2651-543 Standard 05.01 March 1999

IOD SLMbsy
major (continued)
Summary of Clearing an IOD SLMbsy major alarm
Manually busy
affected SLM This flowchart summarizes the
procedure.

SLM
Replace the Contact next

N N
Passed? card. Refer to Passed? level of support
the correct NTP.
Y Y
1 1
Return SLM to
service
End
GSP05 (CSP10)
IOD SLMbsy
major (continued)
Clearing an IOD SLMbsy major alarm
At the MAP terminal
1 To access the SLM level of the MAP display, type
>MAPCI;MTC;IOD;SLM
IOD
IOC 0 1 2 3
STAT . . . .

SLM 0 1
Stat S .
SLM 0 primary device TAPE DISK

status . .
drive idle on line
user SYSTEM
2 Determine the state of the SLMs.

Note: The letter S to the right side of the SLM stat header means that the
associated SLM is system busy. A dot means that the SLM is in service.
If state of Do
both SLMs is S step 21

one SLM is S step 3
3 Determine which SLM is the primary SLM.

Note: The line under the SLM stat header shows the primary SLM. The other
SLM is, by default, the secondary SLM. In step 1, the primary SLM is SLM 0.
297-2651-543 Standard 05.01 March 1999

IOD SLMbsy
major (continued)
4 Determine if the system busy SLM is the primary or secondary SLM.
If the system busy SLM Do
is the primary SLM step 5

is the secondary SLM step 8

>CM;CMMNT
0 no cpu 0 . . yes . . . .
Next image restart type = WARM
Last CM REXTST executed

Memory(kbytes): Used =105984 Avail = 12800 Total = 118784
6 To change the primary autoload device to a device in the other SLM, type
>AUTOLD SLM slm_number device_type
where
slm_number is the number of the SLM that is not system busy (0 or 1)
device_type is the type of SLM device (DISK or TAPE)
Example input:
>AUTOLD SLM 1 DISK
New autoload route has been set.
GSP05 (CSP10)
IOD SLMbsy
major (continued)
7 Determine which SLM is the secondary SLM.

Note: The secondary SLM appears to the right side of the AutoLdev header.
In step 5, the secondary SLM is SLM 1.
At the SLM shelf
8 Determine if the secondary SLM has a tape cartridge.
If a tape cartridge Do
is present step 9
9 Remove the tape cartridge from the SLM and store the cartridge.
10 Insert a blank tape cartridge.

At the MAP terminal
11 To access the secondary SLM, type
>IOD;SLM slm_number
where
slm_number is the number of the SLM (0 or 1) containing the
secondary autoload device
12 To make the secondary SLM manually busy, type

>BSY
passed step 13
failed step 21
297-2651-543 Standard 05.01 March 1999

IOD SLMbsy
major (continued)
13 To test the secondary SLM, type

>TST
passed step 17
card list
14 Record the location, description, slot number, product engineering code (PEC)
15 Perform the correct card replacement procedure in Card Replacement

16 Go to step 18.
17 To return the SLM to service, type

>RTS
passed step 18
failed step 21
18 Determine if the other SLM is system busy.
If the state of the other SLM Do
is S step 5
is not S step 19
GSP05 (CSP10)
IOD SLMbsy
major (continued)
(end)
19 Determine if the SLMbsy major alarm cleared.
If the alarm Do
cleared step 22
20 Perform the correct alarm clearing procedure.
297-2651-543 Standard 05.01 March 1999

IOD SLMbsy
minor
Alarm display
. . SLMbsy . . . . . . .
Indication
At the MTC level of the MAP display, SLMbsy appears under the IOD
header of the alarm banner. The SLMbsy indicates an SLMbsy minor alarm.
Meaning
One system load module (SLM) is control-side (C-side) or manual busy.
Result
Common procedures
Action
GSP05 (CSP10)
IOD SLMbsy
minor (continued)
Summary of Clearing an IOD SLMbsy minor alarm

status of SLMs procedure.

Y Perform CM procedure.
SLM C-side
alarm clearing
busy?
procedures
N
Test the
affected SLM
N Replace the N Contact next

Passed? card. Refer to Passed? level of support
the correct NTP.
Y 1 Y
1
Return SLM to
service
End
297-2651-543 Standard 05.01 March 1999

IOD SLMbsy
minor (continued)
Clearing an IOD SLMbsy minor alarm
At the MAP terminal
>MAPCI;MTC;IOD;SLM
IOD
IOC 0 1 2 3
STAT . . . .

SLM 0 1
Stat S .

status . .
drive idle on line
user SYSTEM

Note: The letter C on the right of the SLM Stat header means that the
associated SLM is C-side busy. The letter M indicates the SLM is manual busy.
A dot indicates the SLM is in service.
If state of Do
one SLM is C step 20

both SLMs are C step 21
one SLM is M step 3
both SLMs are M step 7

Note: The entry under the SLM Stat header shows the primary SLM. The
other SLM is the secondary SLM. In the MAP display in step 1, the primary
SLM is SLM 0.
GSP05 (CSP10)
IOD SLMbsy
minor (continued)
4 Determine if the manual busy SLM is the primary or secondary SLM.
If the manual busy SLM Do


>CM;CMMNT
0 no cpu 0 . . yes . . . .

Memory(kbytes): Used =105984 Avail = 12800 Total = 118784
6 To change the primary autoload device to a device in the other SLM , type
where
slm_number is the number of the SLM that is not manual busy (0 or 1)
device_type is the SLM device type (DISK or TAPE)
Example input:
>AUTOLD SLM 1 DISK
New autoload route has been set.
297-2651-543 Standard 05.01 March 1999

IOD SLMbsy
minor (continued)

Note: The entry under the SLM Stat header indicates the primary SLM. The
other SLM is the secondary SLM. In the MAP display in step 1, the secondary
SLM is SLM 1.
At the SLM shelf
8 Determine if the secondary SLM holds a tape cartridge.
If the secondary SLM Do
contains a tape cartridge step 9

does not contain a tape cartridge step 10

At the MAP terminal
>IOD;SLM slm_number
where
slm_number is the number of the secondary SLM (0 or 1)

>TST
passed step 16
failed, and a card list generates step 13

15 Go to step 17.
GSP05 (CSP10)
IOD SLMbsy
minor (continued)
(end)
16 To return the secondary SLM to service, type

>RTS
passed step 17
failed step 22
17 Determine if the other SLM is manual busy.
is M step 5
is not M step 18
18 Determine if the SLMbsy minor alarm cleared.
If the alarm Do
cleared step 23
19 Perform the correct procedure in this document to clear an alarm.
20 Perform the procedure Clearing a CM PMCTbl minor alarm described in this

document.
21 Perform the procedure Clearing a CM PMCFlt major alarm described in this

document.
297-2651-543 Standard 05.01 March 1999

IOD SLMoff
minor
Alarm display
. . SLMoff . . . . . . .
Indication
At the MTC level of the MAP display, SLMoff appears under the IOD
header of the alarm banner. The SLMoff indicates an SLMoff minor alarm.
Meaning
One system load module (SLM) is offline.
Result
Service continues if one SLM is offline and a computing module (CM) and
message switch (MS) files can boot. The CM and MS can boot when they
are on the in-service SLM. An initiated reload can cause the loss of service
when both SLMs are offline. The loss of service also occurs when only
bootable CM or MS files are on an offline SLM.
If one SLM is offline and an in-service SLM that contains enough recording
volumes can maintain billing service information. An example of billing
service information is automatic message accounting (AMA) data. The loss
of billing service information occurs when both SLMs are offline. The loss
of billing service information also occurs when the correct amount of
recording volumes are not on the in-service SLM.
Common procedures
Action
GSP05 (CSP10)
IOD SLMoff
minor (continued)
Summary of Clearing an IOD SLMoff minor alarm
Manually busy This flowchart summarizes the

affected SLM procedure.

SLM
N Replace card. N Contact next

Passed? Refer to the Passed? level of support
correct NTP.
1 Y 1 Y
Return SLM to
service
End
297-2651-543 Standard 05.01 March 1999

IOD SLMoff
minor (continued)
Clearing an IOD SLMoff minor alarm
At the MAP terminal
1 Maintenance persons have put one or both SLMs offline. Determine if you can
return the SLMs to service.
If you Do
have permission to return the SLMs step 2

to service
SLMs to service
At the MAP terminal

>MAPCI;MTC;IOD;SLM
IOD
IOC 0 1 2 3
STAT . . . .
DIRP: . XFER: . DVI: . DPPP: . DPPU: .

NOP: . SLM: . NX25: . MLP: . SCAI: .
SLM 0 1
Stat O .

status . .
drive idle on line
user SYSTEM
GSP05 (CSP10)
IOD SLMoff
minor (continued)
3 Determine the status of the SLMs.

Note: The letter O on the right of the SLM Stat header indicates that the
associated SLM is offline. A dot means that the SLM is in service.
If the state of Do
both SLMs is O step 8

one SLM is O step 4

Note: The entry under the SLM Stat header indicates the primary SLM; the
other SLM is the secondary SLM. In the MAP in step 2, the primary SLM is
SLM 0.
5 Determine if the offline SLM is the primary or secondary SLM.
If the offline SLM Do


>CM;CMMNT
0 no cpu 0 . . yes . . . .
AutoLdev: Primary = SLM 0 DISK Secondary = SM 1 DISK

297-2651-543 Standard 05.01 March 1999

IOD SLMoff
minor (continued)
7 To change the primary autoload device to a device in the other SLM , type
where
slm_number is the number of the SLM that is not offline (0 or 1)
Example input
>AUTOLD SLM 1 DISK
Note: The secondary SLM is on the right of the AutoLdev header. In step 6,
the secondary SLM is SLM 1.
At the SLM
9 Determine if the secondary SLM holds a tape cartridge.
is present step 10

At the MAP terminal
>IOD;SLM slm_number
where
GSP05 (CSP10)
IOD SLMoff
minor (continued)
13 To manually busy the secondary SLM, type

>BSY
passed step 14
failed step 22

>TST
passed step 18
card list

17 Go to step 19.
18 To return the SLM to service, type

>RTS
passed step 19
failed step 22
297-2651-543 Standard 05.01 March 1999

IOD SLMoff
minor
minor
(continued)
(end)
19 Determine if the other SLM is offline.
is O step 6
is not O step 20
20 Determine if the SLMoff minor alarm cleared.
If the alarm Do
cleared step 23
GSP05 (CSP10)
IOD SLMtbl
minor
Alarm display
. . SLMtbl . . . . . . .
Indication
At the MTC level of the MAP display, SLMtbl appears under the IOD
header of the alarm banner. SLMtbl indicates an SLMtbl minor alarm.
Meaning
At least one system load module (SLM) is in-service trouble.
Result
The condition does not affect service.
Common procedures
Action
297-2651-543 Standard 05.01 March 1999

IOD SLMtbl
minor (continued)
Summary of Clearing an IOD SLMtbl minor alarm
Manually busy This flowchart summarizes the

affected SLM procedure.

SLM
N Replace card. N Contact next

Passed? Refer to the Passed? level of support
correct NTP.
1 Y 1 Y
Return SLM to
service
End
GSP05 (CSP10)
IOD SLMtbl
minor (continued)
Clearing an IOD SLMtbl minor alarm
At the MAP terminal
>MAPCI;MTC;IOD;SLM
IOD
IOC 0 1 2 3
STAT . . . .
DIRP: . XFER: . DVI: . DPPP: . DPPU: .

.
SLM 0 1
Stat I .

status . .
drive idle on line
user SYSTEM

Note: The letter I on the right side of the SLM Stat header means that the
associated SLM is in-service trouble. A dot means that the SLM is in service.
If state of Do
both SLMs are I step 7

one SLM is I step 3
3 Determine the SLM that is the primary SLM.

Note: The entry under the SLM Stat header shows the primary SLM; the other
SLM is the secondary SLM. In the example MAP display in step 1, the primary
SLM is SLM 0.
297-2651-543 Standard 05.01 March 1999

IOD SLMtbl
minor (continued)
4 Determine if the SLM with in-service trouble is the primary or secondary SLM.
If the SLM with in-service trouble Do


>CM;CMMNT
0 no cpu 0 . . yes . . . .

6 To change the primary autoload device to a device in the other SLM, type
where
slm_number is the number of the SLM that is in service (0 or 1)
Example input:
>AUTOLD SLM 1 DISK
7 Determine the SLM that is the secondary SLM.
Note: The entry under the SLM Stat header shows the primary SLM. The
other SLM is the secondary SLM. In the example MAP display in step 1, the
secondary SLM is SLM 1.
GSP05 (CSP10)
IOD SLMtbl
minor (continued)
At the SLM shelf
8 Determine if the secondary SLM contains a tape cartridge.
is present step 9

At the MAP display
>IOD;SLM slm_number
where
12 To make the secondary SLM manually busy, type

>BSY
passed step 13
failed step 21

>TST
passed step 17
card list
297-2651-543 Standard 05.01 March 1999

IOD SLMtbl
minor
minor
(continued)
(end)

16 Go to step 18.
17 To enable the secondary SLM , type

>RTS
passed step 18
failed step 21
18 Determine if the other SLM has in-service trouble.
is I step 5
is . (dot) step 19
19 Determine if the SLMtbl minor alarm cleared.
If the alarm Do
cleared step 22
GSP05 (CSP10)
IOD ssys B
minor
Alarm display
. . ssys B . . . . . . .
Indication
At the IOD level of the MAP display, ssys B alarm indicates a ssys B minor
alarm.
Meaning
The subsystem failed to bond to the DIRP utility, or does not run. A
common reason for the failures is that the DIRPSSYS table data entries do
not contain the subsystem. The abbreviation ssys represents the affected
subsystem. Affected subsystems can include journal file (JF), operational
measurements (OM), Station-Message Detail Recording (SMDR), and
automatic message accounting (AMA).
Result
This procedure can cause an interruption in service.
Perform this procedure during off-peak hours. To activate the subsystem

after you enter the tables, perform a warm restart. Warm restarts disrupt the
normal function of the core.
Common procedures
Action
297-2651-543 Standard 05.01 March 1999

IOD ssys B
minor (continued)
Summary of Clearing an IOD ssys B minor alarm
Contact the next

level of support
procedure.

Enter tables.
procedure.
Refer to correct
NTP.
End
GSP05 (CSP10)
IOD ssys B
minor (continued)
(end)
Clearing an IOD ssys B minor alarm
CAUTION
Service interruption
Perform this procedure during off-peak hours. You must
perform a warm restart to activate the subsystem after you
enter tables. Warm restarts disrupt the normal function of
the core.
CAUTION
Service interruption
Perform this procedure during off-peak hours. You must
perform a warm restart to activate the subsystem after
you enter tables. Warm restarts disrupt the normal
function of the core.
At the MAP terminal

1 To enter tables DIRPPOOL and DIRPSSYS, perform the correct procedures in
the Translations Guide. Complete the procedure and return to this point.
2 Determine if the ssys B alarm cleared.
If the alarm Do
cleared step 4
297-2651-543 Standard 05.01 March 1999

IOD ssys E
minor
Alarm display
. . ssys E . . . . . . .
Indication
At the IOD level of the MAP display, ssys E indicates a ssys E minor alarm.
Meaning
The DIRP utility completed an emergency rotation of the normal files of the
indicated subsystem. The abbreviation ssys represents the affected
subsystem. Affected subsystems can include journal file (JF), operational
measurements (OM), and automatic message accounting (AMA).
Result
Common procedures
This procedure refers to Resetting a volume.
Action
GSP05 (CSP10)
IOD ssys E
minor (continued)
Summary of Clearing an IOD ssys E minor alarm
Query the This flowchart summarizes the

subsystem procedure.

procedure.
Do logs show N
any volumes
INERROR?
Y
Reset the
INERROR
volumes
Audit the
subsystem
N Contact next
Alarm
level of support
cleared?
End
297-2651-543 Standard 05.01 March 1999

IOD ssys E
minor (continued)
Clearing an IOD ssys E minor alarm
At the MAP terminal
>MAPCI;MTC;IOD;DIRP
2 To query the subsystem, type

>QUERY ssys ALL
where
AMA 0 1 2 0 9
REGULAR
FILE (S) STATE VOLUME RECCOUNT BLOCK E V
V_B VLID FNUM FRN#
ACTIVE AVAIL D000AMA 1 1 0 23
NO 2806 001F A132
STANDBY1 AVAIL D010AMA 0 0 0 23
NO 2806 0020 20BF
3 Determine if volumes are in the INERROR state.
If any volumes Do

4 Perform the common procedure Resetting a volume in this document to reset

the INERROR volumes. Complete the procedure and return to this point.
GSP05 (CSP10)
IOD ssys E
minor (continued)
(end)
5 To audit the subsystem that the alarm indicated, type

>AUDIT ssys
where
ssys is the subsystem
SENDING REQUEST TO SUBSYSTEM
DO YOU WANT THE SUBSYSTEM EMERGENCY INDICATOR TURNED OFF?
PLEASE CONFIRM ( YES OR NO ):
6 To confirm the emergency indicator is OFF, type

> YES
MAP response:
REQUEST SENT TO SUBSYSTEM, CHECK DIRP LOG FOR DETAILS
7 Determine if the ssys E alarm cleared.
If the alarm Do
cleared step 9
297-2651-543 Standard 05.01 March 1999

IOD ssys F
minor
Alarm display
. . ssys F . . . . . . .
Indication
At the IOD level of the MAP display, ssys F alarm indicates a ssys F minor
alarm.
Meaning
More than 24 subsystems tried to bind into the DIRP utility. The
abbreviation ssys represents the affected subsystem. Affected subsystems
can include journal file (JF), operational measurements (OM), and automatic
message accounting (AMA).
Result
Common procedures
Action
GSP05 (CSP10)
IOD ssys F
minor (continued)
Summary of Clearing an IOD ssys F minor alarm
Contact next This flowchart summarizes the

level of support procedure.

End procedure.
297-2651-543 Standard 05.01 March 1999

IOD ssys F
minor
minor
(continued)
(end)
How to clear an IOD ssys F minor alarm
GSP05 (CSP10)
IOD ssys I
minor
Alarm display
. . ssys I . . . . . . .
Indication
At the IOD level of the MAP, ssys I indicates an ssys I minor alarm.
Meaning
The ACTIVE and STANDBY 1 volumes in the indicated subsystem are on
the same input/output controller (IOC). The abbreviation ssys represents the
affected subsystem. Affected subsystems can include journal file (JF),
operational measurements (OM), and automatic message accounting
(AMA).
Result
Common procedures
This procedure refers to Resetting a volume.
Action
297-2651-543 Standard 05.01 March 1999

IOD ssys I
minor (continued)
Summary of Clearing an IOD ssys I minor alarm

Silence alarm procedure.

procedure.
Are any Mount volumes
Y
volumes 1
demounted?
1 N
Reset Y
Are any Y Alarm
volumes INERROR 2
cleared?
INERROR? volumes
N N
Close the
standby file.
N Contact next
Alarm
2 Y
End
GSP05 (CSP10)
IOD ssys I
minor (continued)
Clearing an IOD ssys I minor alarm
CAUTION
lose or corrupt automatic message accounting (AMA)
CAUTION
At the MAP terminal

>MAPCI;MTC;IOD;DIRP

>SIL
3 Determine from office records or from operating company personnel if any

volumes are in the demounted state.
If volumes Do
are in the demounted state step 4

are not in the demounted state step 10
4 Determine the reason that the volume is in the demounted state. When
possible, go to the next step in this procedure.
297-2651-543 Standard 05.01 March 1999

IOD ssys I
minor (continued)
5 Determine if the volume is a parallel volume.
If the volume Do
is not a parallel volume step 6

is a parallel volume step 7
6 To mount the demounted volume, type

>MNT ssys vol_name
where
Example input
>MNT AMA S01DAMA1
7 To mount the demounted volume, type

>MNT ssys vol_name PARALEL
where
Example input
>MNT AMA S01DAMA1 PARALEL
8 Repeat steps 4 through 7 until you mount all demounted volumes. Go to the
next step in this procedure.
GSP05 (CSP10)
IOD ssys I
minor (continued)

>QUERY ssys ALL
where
AMA 0 1 2 0 9
REGULAR
FILE(S) STATE VOLUME RECCOUNT BLOCK E V V_B VLID
FNUM FRN#
ACTIVE AVAIL D000AMA 1 1 0 23
NO 2806 001F A132
STANDBY1 AVAIL D010AMA 0 0 0 23
NO 2806 0020 20BF
If any volumes Do

11 To reset the INERROR volumes, perform the common procedure Resetting a

12 Determine if the INERROR volumes changed to READY status.
If the INFERROR volumes Do
changed to READY status step 14

did not change to READY status step 15
297-2651-543 Standard 05.01 March 1999

IOD ssys I
minor
minor
(continued)
(end)
13 To close the standby file, type

>CLOSE ssys STDBY 1
where
Note: If you close the standby file, the DIRP must open a new standby file on
another IOC.
14 Determine if the ssys I alarm cleared.
If the alarm Do
cleared step 16
GSP05 (CSP10)
IOD ssys MP or ssys P

critical
Alarm display
. . ssys P . . . . . . .
*C*
Indication
At the IOD level of the MAP display, ssys MP indicates critical alarms for
an ssys MP. The ssys P alarm indicates critical alarms for an ssys P.
Meaning
The parallel file assigned to the subsystem indicated by the alarm is not
recording. The abbreviation ssys represents the affected subsystem. There
can be an change in the JF, OM, and AMA subsystems.
Result
Loss of backup files of billing data.
Common procedures
This procedure refers to Allocating a volume and Resetting a volume.
Action
the alarm.
297-2651-543 Standard 05.01 March 1999


Summary of Clearing an IOD ssys MP or ssys P critical alarm

Silence the
Use the instructions that follow this flowchart
alarm
to perform the procedure.
Parallel Wait 3 min

Y Alarm Y
volume
cleared?
rewinding?
N
N
Is the parallel Y Select an MTD Load the tape Format the tape
device type
tape?
N
Is the parallel Y Select a disk CLEANUP Format the
device type volume volume
disk?
N
Add volume to
table
DIRPPOOL
Verify that the

mounted
volume
multiple Allocate N Contact next

N Alarm
parallel additional level of support
cleared?
volumes? volumes
Y
Y
End
GSP05 (CSP10)

Clearing an IOD ssys MP or ssys P critical alarm
At the MAP terminal
1
CAUTION
(AMA) data. The operating company uses AMA data
to produce billings. Loss or damage of AMA data
results in revenue loss for the operating company.
CAUTION
(AMA) data. The operating company uses AMA
data to produce billings. Loss or damage of AMA
data results in revenue loss for the operating
company.
To access the DIRP MAP and DIRP MAP menu, type

>MAPCI;MTC;IOD;DIRP
Example of a MAP:
IOD
IOC 0 1 2
STAT . L .


>SIL

>QUERY ssys ALL
297-2651-543 Standard 05.01 March 1999


where
FILE(S)STATE VOLUME RECCOUNT BLOCK E V V_B VLID FNUM FRN#
ACTIVE AVAIL D000AMA 1 1 0 23 NO 2806 001F A132
STANDBY1 AVAIL D010AMA 0 0 0 23 NO 2806 0020 20BF
PARALLEL FILE STATE VOLUME BLOCK E V V_B VLID FNUM FRN#

B910130174616AMA AVAIL T0 0 0 0 YES 2400
4 Record the status of the parallel volume.
5 Determine if the active parallel volume mounted.
If the active parallel volume Do
mounted step 6
6 Determine if multiple parallel volumes are in use.
Multiple parallel volumes Do
used step 7
not used step 10
7 To query the subsystem to determine the number of parallel volumes that

moved, type
>QUERY ssys ALL
where
GSP05 (CSP10)


B910130174616AMA AVAIL T0 0 0 0 YES 2400
8 Determine if enough recording volumes were allocated to the parallel recording

pool.
If enough recording volumes Do
were allocated step 10

were not allocated step 9
9 Perform the common procedure Allocating a volume in this document to

allocate additional volumes. Complete the procedure and return to this point.
10 Determine if the status of the active parallel volume is RWIND.
If the status Do
is RWIND step 12
is not RWIND step 11
11 Determine if the status of the parallel volume is INERROR.
If the status Do
is INERROR step 14
is not INERROR step 13
12 Wait for the rewind to complete. The rewind takes 3 min. Continue to QUERY
the subsystem to monitor the parallel volume status.
297-2651-543 Standard 05.01 March 1999


13 Determine if the ssys P alarm cleared.
If the alarm Do
cleared step 39
14 Reset the INERROR volume. Perform the common procedure Resetting a

15 To verify that the INERROR volume changed from INERROR to AVAIL , type
>QUERY ssys ALL
where

B910130174616AMA AVAIL T0 0 0 0 YES 2400
16 Determine if the reset was successful.
If the reset Do
was successful step 20

was not successful step 17
17 Check the IOD alarm header on the MAP display for an IOC alarm.
If an IOC alarm Do
is present step 19
GSP05 (CSP10)

18 Contact the next level of support to restore the INERROR volume(s).

Go to step 15.
19 Perform the correct procedure in Recovery Procedures. to clear the alarm.

20 Determine if the ssys P alarm cleared.
If the alarm Do
cleared step 39
21 To determine the recording device type used for subsystem parallel recording,
type
>QUERY ssys ALL
where

B910130174616AMA AVAIL T0 0 0 0 YES 2400
22 Record the pool number shown in the POOLNO field.

>TABLE DIRPPOOL
TABLE: DIRPPOOL
297-2651-543 Standard 05.01 March 1999


24 To determine the recording device type used for the subsystem parallel pool,
type
>POSITION pool_no; LIST
where
pool_no is the pool number found in step 22
POOLNO POOLNAME POOLTYPE DEVTYPE VOLUME0 VOLUME1
VOLUME20 VOLUME21 VOLUME22 VOLUME23
0 AMAPOOL REGULAR TAPE $ $ $ $ $

$ $ $ $ $ $ $ $ $
$ $ $ S $ $
$ $ $ $
25 Record the value in the DEVTYPE field.

Note: The MAP response in the preceding step shows the device type in the
DEVTYPE field is TAPE.

>LEAVE
27 Determine if the parallel device is tape or disk.
If the parallel device Do
is tape step 28
is disk step 31
28 Select a magnetic tape drive (MTD) used for parallel data. Record the MTD
number.
29 Mount a tape acceptable for recording parallel subsystem data on the selected
MTD. Perform the correct procedure in Magnetic Tape Reference Manual,
297-1001-118. Complete the procedure and return to this point.
30 Go to step 34.
GSP05 (CSP10)

31 Select a disk volume for parallel subsystem recording. Determine from office
records the name of the volume.
32 To enter the disk utility, type

>DISKUT
33 To list the files on the selected disk volume, type

>LIST vol_name ALL
where
vol_name is the volume name
Y/M/D Files Files
––––––––– ––––––– ––––––– ––––––– ––––
S00Dvol1 870122 876 2 15
S00Dvol2 861121 14 14 0
S00Dvol3 861121 0 0 0
S00Dvol4 861121 2048 100 0
S00Dvol5 861121 1 0 1
34 To allocate the volume, perform the common procedure Allocating a volume in


>QUERY ssys ALL
where

B910130174616AMA AVAIL T0 0 0 0 YES 2400
297-2651-543 Standard 05.01 March 1999


critical
critical
(continued)
(end)
36 Determine if the parallel volume allocated.
If the parallel volume Do
allocated step 37
did not allocate step 38
37 Determine if the ssys P or ssys MP alarm cleared.
If the alarm Do
cleared step 39
GSP05 (CSP10)
IOD XMITn
minor
Alarm display
. . XMITn . . . . . . .
Indication
At the IOD level of the MAP display, XMIT (transmit) followed by a
number (n) indicates that an XMITn minor alarm exists.
Meaning
A remote data center requested transmission of a file from a recording
device. The number that follows XMIT represents the number of the
recording device that holds the file.
Result
Common procedures
Action
297-2651-543 Standard 05.01 March 1999

IOD XMITn
minor (continued)
Summary of Clearing an IOD XMITn minor alarm

Display file
information Use the instructions that follow this flowchart
to perform the procedure.
Is the file on N N Contact next

Is the file on
disk? level of support
tape?
Y Y
List the disk

volume
Determine
which MTD
holds the file
Load the tape

on the MTD
Mount tape.
Refer to correct
NTP.
List the tape
Send the file End
GSP05 (CSP10)
IOD XMITn
minor (continued)
Clearing an IOD XMITn minor alarm
At the MAP terminal
1 To access the XFER (transfer) level of the MAP display, type
>MAPCI;MTC;IOD;XFER
2 To display information about the file on the recording device, type

>QUERY XMIT dphd_index
where
dphd_index is a value for dirphold index (0 to 99)
3 To determine the location of the stored file, note the data in the FILE_LOCN.
If the file Do
is on disk step 4
is on tape step 6
4 To access the disk utility software, type

>DISKUT
5 To list the volume on the disk, type

>LISTVOLS vol_name ALL
where
Y/M/D Files Files
––––––––– ––––––– –––––––– ––––––– ––––
S00dvol1 870122 876 2 15
S00Dvol2 861121 14 14 0
S00Dvol3 861121 0 0 0
S00Dvol4 861121 2048 100 0
S00Dvol5 861121 1 0 1
297-2651-543 Standard 05.01 March 1999

IOD XMITn
minor
minor
(continued)
(end)
6 Determine from office records the location of the magnetic tape drive (MTD)
that holds the file.
7 Perform the correct procedure in Routine Procedures to mount the tape..

8 To list the tape, type

>LIST mtd_no
where
9 To send the file, type

>XMIT nn
where
nn is the number that appears in the alarms
10 Determine if the XMITn alarm cleared.
If the alarm Do
cleared step 12
GSP05 (CSP10)
6-1
Lines alarm clearing procedures

Introduction
This chapter contains lines alarm clearing procedures. Lines alarms are
indicated under the Lns header of the alarm banner in the MAP display.
Each procedure contains the following sections:
• Alarm display
• Indication
• Meaning
• Impact
• Action
Alarm display
This section indicates how the alarm is displayed at the MAP terminal.
Indication
This section indicates where the alarm indication appears, how the alarm is
represented, which subsystem is affected, and the alarm severity.
Meaning
Impact
This section describes the consequences of the alarm condition.
Common procedures
This section lists common procedures that are used during the alarm clearing
procedure. A common procedure is a series of steps that is repeated within
maintenance procedures, such as a common procedure for removing and
replacing a card. Common procedures are found in the common procedures
chapter in this NTP.
GSP05 (CSP10)
6-2 Lines alarm clearing procedures
Do not use common procedures unless directed to do so in the step-action

procedure.
Action
297-2651-543 Standard 05.01 March 1999

6-3 Lines alarm clearing procedures 6-3
Lns DF
Major
Alarm display
. . . . . . DF . . .
M
Indication
A DF appears under the Lns header in the MAP display for the subsystem
status.
Meaning
A diagnostic failure (DF) alarm indicates that two or more line circuits have
alarms in the same class. The classes are critical, major, or minor. The
alarms are SDIAG, DIAG, NDIAG, FAC, MSET, MCARD, UCARD, or
QDIAG.
Result
The condition affects subscriber service. You must correct the condition.
Common procedures
This procedure refers to Clearing lines alarms.

you to the common procedure.
Action
procedure.
GSP05 (CSP10)
Lns DF
Major (continued)
Summary of Clearing an Lns DF Major alarm
Post failed lines This flowchart summarizes the

procedure.

Analyze the procedure
fault
Clear alarm
N Contact next
Cleared? level
Y
End
297-2651-543 Standard 05.01 March 1999

Lns DF
Major (continued)
Clearing an Lns DF Major alarm
At the MAP display:
1 To access the LTP level of the MAP display, type
>MAPCI;MTC;LNS;LTP
2 To post the lines that have a diagnostic failure , type

>POST DF
POST DF DELQ BUSYQ PREFIX
LCC PTY RNG.....LEN.......... DN STA F S LTA TE

IBN REM1 00 0 00 06 7224345 IDL D
3 Note the failure code that appears under the F header (in bold in the response
in the MAP example in the previous step). Check the following information for
the meaning of the failure code.
Failure Code Meaning
is D the DIAG test failed

is F the DIAG test failed
isS (N/A for ISDN) the SDIAG test failed
is N the SDIAG test passed on the line that has faults
is m the DIAG test detected a missing keyset or
network termination 1 (NT1)
is M the DIAG test detected a missing line card
is Q there is a call processing error
is I there is a major incoming message overload
(ICMO)
is i there is a minor incoming message overload
(ICMO)
is l the keyset line failed the loopback test at the
terminal
GSP05 (CSP10)
Lns DF
Major (continued)
(end)
4 Perform the procedure Clearing lines alarms. Complete the procedure and
5 Check the MAP to see if the DF major alarm cleared.
If the DF major alarm Do
cleared step 7
297-2651-543 Standard 05.01 March 1999

Lns DIAG
Alarm display
. . . . . . DIAG . . .
M
Indication
The DIAG appears under the Lns header in the MAP display for subsystem
status.
Meaning
The diagnostic (DIAG) alarm indicates that a number of lines failed the
extended diagnostic test.
Result
The impact on subscriber service depends on the type of the failure. For
example, a call can continue when a noise problem affects the quality of
service. A test failure for transhybrid loss or flux cancellation results in loss
of service until you correct the fault.
Common procedures

Action
procedure.
GSP05 (CSP10)
Lns DIAG
Summary of Clearing an Lns DIAG critical, major, or minor alarm

procedure.

fault
Clear alarm
N Contact next
Cleared? level
Y
End
297-2651-543 Standard 05.01 March 1999

Lns DIAG
Clearing an Lns DIAG critical, major, or minor alarm
At the MAP:
>MAPCI;MTC;LNS;LTP
2 To post the lines that have a diagnostic failure, type

>POST DF D
POST DF D DELQ BUSYQ PREFIX

IBN REM1 00 0 00 06 7224345 IDL D
the meaning of the failure code.

is S (N/A for ISDN) the SDIAG test failed
is Q a call-processing error is present
is I a major incoming message overload (ICMO) is
present
is i a minor incoming message overload (ICMO) is
present
terminal
GSP05 (CSP10)
Lns DIAG
(end)
4 Perform the procedure Clearing lines alarms. Complete the procedure and
5 Check the MAP display to see if the DIAG major alarm cleared.
If the DIAG major alarm Do
cleared step 7
297-2651-543 Standard 05.01 March 1999

Lns FAC
major
Alarm display
. . . . . . FAC . . .
M
Indication
An FAC appears under the Lns header in the MAP subsystem status display
for the MAP.
Meaning
A facility (FAC) alarm indicates the number of line circuits that failed the
facility check reached the threshold.
Result
The impact on subscriber service depends on the type of the failure. For
example, a call can continue even when a noise problem affects the quality
of service. A test failure for a transhybrid loss or flux cancellation results in
loss of service until correction of the fault occurs.
Common procedures
This procedure refers to Clearing Lines alarms
Do not use the common procedure unless the step-action procedure directs
Action
procedure.
Note: If the card in the HAZ state is a WLC (World Line Card – 6X17BA),
the cause of the HAZard condition must clear first. A DIAGnosis is not
allowed on a 6X17BA while it is in the HAZ state.
GSP05 (CSP10)
Lns FAC
major (continued)
Summary of Clearing an Lns FAC major alarm

procedure.

fault
Clear alarm
N Contact next
Alarm level
cleared?
Y
End
297-2651-543 Standard 05.01 March 1999

Lns FAC
major (continued)
Clearing an Lns FAC major alarm
At the MAP display:
1 To access the line test position (LTP) level of the MAP display, type
>MAPCI;MTC;LNS;LTP

>POST DF F
POST DF F DELQ BUSYQ PREFIX

IBN REM1 00 0 00 06 7224345 IDL D
in the MAP display example in the previous step). Check the following
information for the meaning of that failure code.

is S (N/A for ISDN) the SDIAG test failed
is Q a call-processing error is present
present
present
terminal
GSP05 (CSP10)
Lns FAC
major (continued)
(end)
4 Perform the procedure Clearing Lines alarms. Complete the procedure and
5 Check the MAP display to see if the FAC major alarm cleared.
If the FAC major alarm Do
cleared step 7
297-2651-543 Standard 05.01 March 1999

Lns HZD
major
Alarm display
. . . . . . HZD . . .
M
Indication
An HZD appears under the Lns header in the subsystem status for the MAP.
Meaning
A hazard (HZD) alarm indicates a line hazard. For example, a world line
card (WLC) can have leakage resistance or foreign line voltage. The HZD
alarm also indicates that the cutoff relay is in operation to isolate the line
card. The HZD alarm reports that a condition is present. The system clears
the hazard and the alarm. This procedure provides information about the
alarm.
Result
The affected line is out of service until the hazard condition clears.
Common procedures
Action
procedure.
GSP05 (CSP10)
Lns HZD
major (continued)
Summary of Clearing an Lns HZD major alarm

procedure.

Perform a procedure
diagnostic test
Check log
reports
N Contact next
Alarm level of support
cleared?
Y
End
297-2651-543 Standard 05.01 March 1999

Lns HZD
major (continued)
Clearing an Lns HZD major alarm
At the MAP terminal
>MAPCI;MTC;LNS;LTP

>POST S HAZ
POST S HAZ DELQ BUSYQ PREFIX

IBN REM1 00 0 00 06 7224345 IDL D
the meaning of that failure code.

isS (N/A for ISDN) the SDIAG test failed
is Q a call processing error is present
present
present
terminal
GSP05 (CSP10)
Lns HZD
major (continued)
(end)
4 To perform a diagnostic test on each line, type

>DIAG
***LINE132 AUG01 10:15:57 2356 TBL
LEN HOST 15 1 9 27 DN 3511005
REASON = Line Hazard Condition Found
INFO = N/A Vac N/A Ohms N/A Vdc
ACTION TAKEN = Cut-off Relay Operated
ACTION REQUIRED Check Facility
CARD CODE = 6X17AA
5 Check the log report displayed on the MAP terminal as a result of the Diag
command.
A LINE132 log provides details about the line hazard and is for information
purposes only. When the system clears the alarm, the system generates a
LINE133 log.
If the system Do
generated a 132 log step 6

generated a 133 log step 9
6 Wait 30 min to perform another diagnostic test, type

>DIAG
7 Check the log report displayed on the MAP terminal as a result of the Diag
command.
If a LINE Do
132 log generated step 8

133 log generated step 9
297-2651-543 Standard 05.01 March 1999

Lns IMAJ
major
Alarm display
. . . . . . IMAJ . . .
M
Indication
The IMAJ appears under the Lns header in the MAP subsystem status
display.
Meaning
An incoming message overload major (IMAJ) alarm indicates that lines with
an incoming message overload (ICMO) reached a major threshold.
Result
The condition affects subscriber service for electronic business set (EBS)
and datapath lines until you correct the condition.
Common procedures
This procedure refers to Clearing Lines alarms.
Do not proceed to the common procedure unless the step-action procedure

directs you to go.
Action
procedure.
GSP05 (CSP10)
Lns IMAJ
major (continued)
Summary of Clearing an Lns IMAJ major alarm

procedure.

fault
Clear alarm

Y
End
297-2651-543 Standard 05.01 March 1999

Lns IMAJ
major (continued)
Clearing an Lns IMAJ major alarm
At the MAP terminal:
>MAPCI;MTC;LNS;LTP

>POST DF IMAJ
POST DF IMAJ DELQ BUSYQ PREFIX

IBN REM1 00 0 00 06 7224345 IDL D
3 Note the failure code that appears under the F header. The code appears in
bold for the response in the MAP example of the previous step. To determine
the meaning of the failure code, use the following information.
D the DIAG test failed

F the DIAG test failed
S (N/A for ISDN) the SDIAG test failed
N the SDIAG test passed on the line that had faults
earlier
m the DIAG test detected a missing keyset or
M the DIAG test detected a missing line card
Q a call-processing error is present
I a major Incoming message overload (ICMO) is
present
i a minor Incoming message overload (ICMO) is
present
l the keyset line failed the loopback test at the
terminal
GSP05 (CSP10)
Lns IMAJ
major (continued)
(end)
4 Perform the procedure Clearing Lines alarms. Return to this point.
5 Determine from the MAP display if the IMAJ major alarm cleared.
If the IMAJ alarm Do
cleared step 7
297-2651-543 Standard 05.01 March 1999

Lns IMIN
major
Alarm display
. . . . . . IMIN . . .
Indication
The IMIN appears under the Lns header in the MAP subsystem status
display.
Meaning
An incoming message overload minor (IMIN) alarm indicates that the lines
with incoming message overload (ICMO) alarms reached the minor
threshold.
Result
The condition affects subscriber service until you correct the condition.
Common procedures

directs you to go.
Action
procedure.
GSP05 (CSP10)
Lns IMIN
major (continued)
Summary of clearing an Lns IMIN major alarm

procedure.

step-action procedure that
Analyze the follows this flowchart to
fault
perform the procedure.
Clear alarm

End
297-2651-543 Standard 05.01 March 1999

Lns IMIN
major (continued)
Clearing an Lns IMIN major alarm
>MAPCI;MTC:LNS;LTP

>POST DF IMIN
POST DF IMIN DELQ BUSYQ PREFIX

IBN REM1 00 0 00 06 7224345 IDL D

N the SDIAG test passed on line that had faults
earlier
present
present
terminal
GSP05 (CSP10)
Lns IMIN
major (continued)
(end)
4 Perform the procedure Clearing Lines Alarms. Return to this point.
5 Determine from the MAP display if the IMIN minor alarm cleared.
If the IMIN alarm Do
cleared step 7
297-2651-543 Standard 05.01 March 1999

Lns LCARD
major
Alarm display
. . . . . . LCARD . . .
M
Indication
The LCARD appears under the Lns header in the MAP subsystem status
display.
Meaning
A keyset loopback activated at the line card (LCARD) alarm indicates that
key telephone set (keyset) lines failed a loopback test.
Result
The condition affects subscriber service until the replacement or repair of
the card.
Common procedures
This procedure refers Clearing Lines alarms.

you.
Action
procedure.
GSP05 (CSP10)
Lns LCARD
major (continued)
Summary of clearing an Lns LCARD major alarm

procedure.

fault
Clear alarm

Y
End
297-2651-543 Standard 05.01 March 1999

Lns LCARD
major (continued)
Clearing an Lns LCARD major alarm
>MAPCI;MTC;LNS;LTP

>POST DF LCARD
POST DF LCARD DELQ BUSYQ PREFIX

IBN REM1 00 0 00 06 7224345 IDL D

earlier
present
present
terminal
GSP05 (CSP10)
Lns LCARD
major (continued)
(end)
5 Determine from the MAP display to see if the DF major alarm cleared.
If the LCARD major alarm Do
cleared step 7
297-2651-543 Standard 05.01 March 1999

Lns LSET
major
Alarm display
. . . . . . LSET . . .
M
Indication
The LSET appears under the Lns header in the MAP subsystem status
display.
Meaning
A keyset loopback activated at set (LSET) alarm indicates that key
telephone set (keyset) lines failed a loopback test.
Result
The condition affects subscriber service until the replacement or repair of
the telephone set.
Common procedures

directs you to go.
Action
procedure.
GSP05 (CSP10)
Lns LSET
major (continued)
Summary of clearing an Lns LSET major alarm

procedure.

Analyze the procedure.
fault
Clear alarm

cleared? level
Y
End
297-2651-543 Standard 05.01 March 1999

Lns LSET
major (continued)
Clearing an Lns LSET major alarm
>MAPCI;MTC;LNS;LTP

>POST DF LSET
POST DF LSET DELQ BUSYQ PREFIX

IBN REM1 00 0 00 06 7224345 IDL D

earlier
present
present
terminal
GSP05 (CSP10)
Lns LSET
major (continued)
(end)
5 Determine from the MAP display if the LSET major alarm cleared.
If the LSET major alarm Do
cleared step 7
297-2651-543 Standard 05.01 March 1999

Lns MCARD
Alarm display
. . . . . . MCARD . . .
M
Indication
The MCARD appears under the Lns header in the MAP subsystem status
display.
Meaning
A missing card (MCARD) alarm indicates that lines have missing line cards.
Impact
The condition affects subscriber service until replacement or repair of the
card.
Common procedures

directs you to go.
Action
procedure.
GSP05 (CSP10)
Lns MCARD
Summary of Clearing an Lns MCARD critical, major, or minor alarm

procedure.

fault
Clear alarm

Y
End
297-2651-543 Standard 05.01 March 1999

Lns MCARD
Clearing an Lns MCARD critical, major, or minor alarm
>MAPCI;MTC;LNS;LTP

>POST DF MCARD
POST DF MCARD DELQ BUSYQ PREFIX

IBN REM1 00 0 00 06 7224345 IDL D

earlier
present
present
terminal
GSP05 (CSP10)
Lns MCARD
(end)
5 Determine from the MAP display f the MCARD major alarm cleared.
If the MCARD major alarm Do
cleared step 7
297-2651-543 Standard 05.01 March 1999

Lns MSET
major
Alarm display
. . . . . . MSET . . .
M
Indication
The MSET appears under the Lns heading in the MAP subsystem status
display.
Meaning
A missing set (MSET) alarm indicates that lines do not have telephone sets.
Result
The condition affects subscriber service until replacement or repair of the
telephone set.
Common procedures

directs you to go.
Action
procedure.
GSP05 (CSP10)
Lns MSET
major (continued)
Summary of clearing an Lns MSET major alarm

procedure.

Analyze the procedure.
fault
Clear alarm

cleared? level
Y
End
297-2651-543 Standard 05.01 March 1999

Lns MSET
major (continued)
Clearing an Lns MSET major alarm
>MAPCI;MTC;LNS;LTP

>POST DF MSET
POST DF MSET DELQ BUSYQ PREFIX

IBN REM1 00 0 00 06 7224345 IDL D

earlier
present
present
terminal
GSP05 (CSP10)
Lns MSET
major (continued)
(end)
5 Determine from the MAP display if the MSET major alarm cleared.
If the MSET major alarm Do
cleared step 7
297-2651-543 Standard 05.01 March 1999

Lns NDIAG
major
Alarm display
. . . . . . NDIAG . . .
M
Indication
The NDIAG appears under the Lns header in the MAP subsystem status
display.
Meaning
An NDIAG alarm indicates that lines passed a diagnostic test after a
previous diagnostic failure. The lines require an extended diagnostic test to
clear the alarm.
Result
This condition affects subscriber service if a D or F failure flag associates
with the line. If any other failure flag associates with the line, the condition
Common procedures

directs you to go.
Action
procedure.
GSP05 (CSP10)
Lns NDIAG
major (continued)
Summary of Clearing an Lns NDIAG major alarm

procedure.

fault
Clear alarm

Y
End
297-2651-543 Standard 05.01 March 1999

Lns NDIAG
major (continued)
Clearing an Lns NDIAG major alarm
>MAPCI;MTC;LNS;LTP

>POST DF N
POST DF N DELQ BUSYQ PREFIX

IBN REM1 00 0 00 06 7224345 IDL D

earlier
present
present
terminal
GSP05 (CSP10)
Lns NDIAG
major (continued)
(end)
5 Determine from the MAP display if the NDIAG major alarm cleared.
If the NDIAG major alarm Do
cleared step 7
297-2651-543 Standard 05.01 March 1999

Lns PSDF
Alarm display
. . . . . . PSDF . . .
M
Indication
The PSDF appears under the Lns header in the MAP subsystem status
display.
Meaning
The permanent signal diagnostic failure (PSDF) alarm indicates that lines
have permanent signal partial dial (PSPD) alarms. The alarm also indicates
that lines have DIAG, FAC, MCARD, MSET, NDIAG, QDIAG, SDIAG, or
UCARD alarms. The alarms are in the same class, either critical, major, or
minor.
Result
The condition affects subscriber service until you correct the condition.
Common procedures

directs you to go,
Action
procedure.
GSP05 (CSP10)
Lns PSDF
Summary of clearing an Lns PSDF critical, major, or minor alarm

procedure.

Force lines to procedure.
release
Return lines to
service

Y
End
297-2651-543 Standard 05.01 March 1999

Lns PSDF
Clearing an Lns PSDF critical, major, or minor alarm
1 To access the LTP level of the MAP, type
>MAPCI;MTC;LNS;LTP
2 To post the lines that are in the permanent lock-out state, type
>POST S PLO
POST S PLO DELQ BUSYQ PREFIX

IBN REM1 00 0 00 06 7224345 IDL D

earlier
present
present
terminal
GSP05 (CSP10)
Lns PSDF
(end)
4 To force the lines to release, type

>FRLS
6 Determine from the MAP if the PSDF major alarm cleared.
If the PSDF major alarm Do
cleared step 7
7 To return the force-released lines to service, type

RTS
8 Go to step 10.
297-2651-543 Standard 05.01 March 1999

Lns PSPD
major
Alarm display
. . . . . . PSPD . . .
M
Indication
The PSPD appears under the Lns header in the MAP subsystem status
display.
Meaning
The permanent signal partial dial (PSPD) alarm indicates that a line is
off–hook without any digits dialed. The alarm also indicates that only part
of a directory number dialed.
Result
These conditions affect subscriber service until you correct the conditions.
Common procedures

directs you to go.
Action
procedure.
GSP05 (CSP10)
Lns PSPD
major (continued)
Summary of clearing an Lns PSPD major alarm

procedure.

Force lines to procedure
release
Return lines to
service

Y
End
297-2651-543 Standard 05.01 March 1999

Lns PSPD
major (continued)
Clearing an Lns PSPD major alarm
At the MAP:
>MAPCI;MTC;LNS;LTP

>POST S PLO
POST S PLO DELQ BUSYQ PREFIX

IBN REM1 00 0 00 06 7224345 IDL D
Heading Heading

earlier
present
present
terminal
GSP05 (CSP10)
Lns PSPD
major (continued)
(end)
4 Perform the procedure How to Clear Lines alarms. Return to this point.
5 Determine form the MAP display if the PSPD major alarm cleared.
If the PSPD major alarm Do
cleared step 7
297-2651-543 Standard 05.01 March 1999

Lns QDIAG
major
Alarm display
. . . . . . QDIAG . . .
M
Indication
The QDIAG appears under the Lns header in the MAP subsystem status
display.
Meaning
The queue diagnostic (QDIAG) alarm indicates the number of lines in the
shower queue reached the threshold.
Result
The type of failure determines the result on subscriber service. For example,
a noise problem affects the quality of service while the problem continues to
allow calls. Test failures for transhybrid loss or flux cancellation result in
loss of service until you correct the fault.
Common procedures

directs you to go.
Action
procedure.
GSP05 (CSP10)
Lns QDIAG
major (continued)
Summary of clearing an Lns QDIAG major alarm

procedure.

fault
Clear alarm

cleared? level
Y
End
297-2651-543 Standard 05.01 March 1999

Lns QDIAG
major (continued)
Clearing an Lns QDIAG major alarm
>MAPCI;MTC;LNS;LTP

>POST DF QUEUE
POST DF QUEUE DELQ BUSYQ PREFIX

IBN REM1 00 0 00 06 7224345 IDL D
Heading Heading

earlier
present
present
terminal
GSP05 (CSP10)
Lns QDIAG
major (continued)
(end)
4 Perform the procedure Clearing lines alarms. Return to this point.
5 Determine from the MAP display if the QDIAG major alarm cleared.
If the QDIAG major alarm Do
cleared step 7
297-2651-543 Standard 05.01 March 1999

Lns SDIAG
major
Alarm display
. . . . . . SDIAG . . .
M
Indication
The SDIAG appears under the Lns header in the MAP subsystem status
display.
Meaning
The short diagnostic (SDIAG) alarm indicates that a number of lines failed
the short diagnostic test.
Result
The condition does not affect subscriber service unless a D or F failure flag
associates with the line.
Common procedures

directs you to go.
Action
procedure.
GSP05 (CSP10)
Lns SDIAG
major (continued)
Summary of clearing an Lns SDIAG major alarm

procedure.

fault
Clear alarm

Y
End
297-2651-543 Standard 05.01 March 1999

Lns SDIAG
major (continued)
Clearing an Lns SDIAG major alarm
>MAPCI;MTC;LNS;LTP

>POST DF S
POST DF S DELQ BUSYQ PREFIX

IBN REM1 00 0 00 06 7224345 IDL D
Heading Heading

earlier
present
present
terminal
GSP05 (CSP10)
Lns SDIAG
major (continued)
(end)
5 Determine from the MAP if the SDIAG major alarm cleared.
If the SDIAG major alarm Do
cleared step 7
297-2651-543 Standard 05.01 March 1999

Lns TCM
major
Alarm display
. . . . . . TCM . . .
M
Indication
The TCM appears under the Lns header in the MAP subsystem status
display.
Meaning
The time compression multiplexing (TCM) alarm indicates that the
acceptable number of TCM synchronization losses reached the threshold.
Result
The condition affects subscriber service until the you correct the condition.
Common procedures

directs you to go.
Action
procedure.
GSP05 (CSP10)
Lns TCM
major (continued)
Summary of clearing an Lns TCM major alarm

procedure.

fault
Clear alarm

Y
End
297-2651-543 Standard 05.01 March 1999

Lns TCM
major (continued)
Clearing an Lns TCM major alarm
1 To access the LTP level of the MAP, type
>MAPCI;MTC;LNS;LTP

>POST DF T
POST DF T DELQ BUSYQ PREFIX

IBN REM1 00 0 00 06 7224345 IDL D
Heading Heading

earlier
present
present
terminal
GSP05 (CSP10)
Lns TCM
major (continued)
(end)
5 Determine from the MAP if the TCM major alarm cleared.
If the TCM major alarm Do
cleared step 7
297-2651-543 Standard 05.01 March 1999

Lns OMAJ
Alarm display
. . . . . . OMAJ . . .
M
Indication
OMAJ appears under the Lns header in the MAP subsystem status display.
Meaning
The out-of-service major (OMAJ) alarm indicates that the number of lines
office wide with the O failure code crosses a threshold. Lines with the O
failure code have two or more logical terminal identifiers (LTID)
out-of-service because of rapid messaging (RM). The thresholds appear in
office parameter RMSG_MAJALARM in table OFCVAR. To change the
values of the thresholds, use the ALMSTAT OMAJ command. Using the
table editor to change the threshold values does not update the alarms.
The following indicators can appear under OMAJ:

• *C* indicates a critical OMAJ alarm.
• M indicates a major OMAJ alarm.
• A blank space (neither *C* nor M) indicates a minor OMAJ alarm.
Impact
Common procedures
Not applicable
Action
procedure.
GSP05 (CSP10)
Lns OMAJ
Summary of clearing an Lns OMAJ critical, major, or minor alarm

procedure.
Post failed lines
Return to procedure.
service all
LTIDs
N Contact next
Did alarm level
clear? of support
End
297-2651-543 Standard 05.01 March 1999

Lns OMAJ
Clearing an Lns OMAJ critical, major, or minor alarm
At the MAP:
1 To access the LTP level of the MAP terminal, type
>MAPCI;MTC;LNS;LTP
2 Post the lines or set of lines that have the O failure code. Type
>POST DF OMAJ
POST DELQ BUSYQ PREFIX
LEN HOST 01 0 00 01
LCC PTY RNG STA F S LTA TE
ISDN LOOP DN 613 722 4209 IDL O
Note 1: To view all lines in the posted set, return to the CI level, and type
>MAPCI NODISP;MTC;LNS;LTP
and press the Enter key. To post the lines, type
>POST DF OMAJ PRINT
and press the Enter key. The list of lines in the posted set displays.
Note 2: To view the RM state of an LTID, post the LEN by the LTID. Type
>POST LT <group name> <group number>
where
group name is the LTID group name as defined in table LTDEF
group number is the LTID group number from 1 to 1022
3 Return to service all LTIDs. Type
>RTS LT ALL
Note: The RTS LT command does not return to service a busy line.
Example of a MAP response to the RTS LT ALL command:
Number of fully data filled lines in the posted set: 21
Number of lines with ISDN LTIDs to RTS: 19
Number of lines with ISDN LTIDs that failed to RTS: 2
GSP05 (CSP10)
Lns OMAJ
(end)
4 Check the MAP display to see if the OMAJ alarm cleared.
If the OMAJ major alarm Do

cleared step 6
5 For additional help, contact the personnel responsible for the next level of
support.
297-2651-543 Standard 05.01 March 1999

Lns OMIN
Alarm display
. . . . . . OMIN . . .
M
Indication
OMIN appears under the Lns header in the MAP subsystem status display.
Meaning
The out-of-service minor (OMIN) alarm indicates that the number of lines
office wide with the o failure code crosses a threshold. Lines with the o
failure code have one logical terminal identifier (LTID) out-of-service
because of rapid messaging (RM). The thresholds appear in office
parameter RMSG_MINALARM in table OFCVAR. To change the values of
the thresholds, use the ALMSTAT OMIN command. Using the table editor
to change the threshold values does not update the alarms.
The following indicators can appear under OMIN:

• *C* indicates a critical OMIN alarm.
• M indicates a major OMIN alarm.
• A blank space (neither *C* nor M) indicates a minor OMIN alarm.
Impact
Common procedures
Not applicable
Action
procedure.
GSP05 (CSP10)
Lns OMIN
Summary of clearing an Lns OMIN critical, major, or minor alarm

procedure.
Post failed lines
Return to procedure.
service all
LTIDs
N Contact next
Did alarm level
clear? of support
End
297-2651-543 Standard 05.01 March 1999

Lns OMIN
Clearing an Lns OMIN critical, major, or minor alarm
At the MAP:
1 To access the LTP level of the MAP terminal, type
>MAPCI;MTC;LNS;LTP
2 Post the lines or set of lines that have the o failure code. Type
>POST DF OMIN
POST DELQ BUSYQ PREFIX
LEN HOST 01 0 00 01
LCC PTY RNG STA F S LTA TE
ISDN LOOP DN 613 722 4209 IDL o
Note 1: To view all lines in the posted set, return to the CI level, and type
>MAPCI NODISP;MTC;LNS;LTP
and press the Enter key. To post the lines, type
>POST DF OMIN PRINT
and press the Enter key. The list of lines in the posted set displays.
Note 2: To view the RM state of an LTID, post the LEN by the LTID. Type
>POST LT <group name> <group number>
where
group name is the LTID group name as defined in table LTDEF
group number is the LTID group number from 1 to 1022
3 Return to service all LTIDs. Type
>RTS LT ALL
Note: The RTS LT command does not return to service a busy line.
Example of a MAP response to the RTS LT ALL command:
Number of fully data filled lines in the posted set: 21
Number of lines with ISDN LTIDs to RTS: 19
Number of lines with ISDN LTIDs that failed to RTS: 2
GSP05 (CSP10)
Lns OMIN
(end)
4 Check the MAP display to see if the OMIN alarm cleared.
If the OMIN major alarm Do

cleared step 6
5 For additional help, contact the personnel responsible for the next level of
support.
297-2651-543 Standard 05.01 March 1999

DMS-Global Services
Platform
Alarm Clearing and Performance
Monitoring Procedures Manual Volume 1
of 3
Product Documentation—Dept 3423

Northern Telecom
P.O. Box 13010
RTP, NC 27709-3010
1-800-684-2273
(1-800-NTI-CARE)
 1997–1999 Northern Telecom
All rights reserved
NORTHERN TELECOM CONFIDENTIAL: The
information contained in this document is the property of
Northern Telecom. Except as specifically authorized in writing
by Northern Telecom, the holder of this document shall keep
the information contained herein confidential and shall protect
same in whole or in part from disclosure and dissemination to
third parties and use same for evaluation, operation, and
maintenance purposes only.
Information is subject to change without notice. Northern
Telecom reserves the right to make changes in design or
components as progress in engineering and manufacturing
may warrant.
DMS, MAP, NORTEL, NORTEL NETWORKS, NORTHERN
TELECOM, NT, and SUPERNODE are trademarks of Northern
Telecom.
Publication number: 297-2651-543
Product release: GSP05 (CSP10)
Document release: Standard 05.01
Date: March 1999
Printed in the United States of America

Alarm Clearing 297-2651-543 v1 PDF

Diunggah oleh

Informasi Dokumen

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

Alarm Clearing 297-2651-543 v1 PDF

Diunggah oleh

Hak Cipta:

Format Tersedia

297-2651-543

Digital Switching Systems

DMS-Global Services Platform

Publication number: 297-2651-543

 1997–1999 Northern Telecom

Printed in the United States of America

297-2651-543 Standard 05.01 March 1999

Procedures to clear application alarms 1-1

Common channel signaling alarm clearing procedures 2-1

CCS RS major 2-107

Computing module alarm clearing procedures 3-1

297-2651-543 Standard 05.01 March 1999

Procedures to clear an external alarm 4-1

Procedures to clear an Input/output device alarm 5-1

297-2651-543 Standard 05.01 March 1999

Lines alarm clearing procedures 6-1

MS MBPT minor 1-106

Network alarm clearing procedures 2-1

297-2651-543 Standard 05.01 March 1999

Peripheral module alarm clearing procedures 3-1

PM LCM critical 3-590

297-2651-543 Standard 05.01 March 1999

Trunks group (Trks) alarm clearing procedures 2-1

Alarm clearing common procedures 3-1

About this document

How to check the version and issue of this document

To determine which version of this document applies to the software in your

How this document is organized

297-2651-543 Standard 05.01 March 1999

Explanatory and context-setting information

References in this document

Procedures to clear application alarms

maintenance procedures, for example card removal and replacement.

297-2651-543 Standard 05.01 March 1999

Wait ten This flowchart summarizes the

Clearing an APPL CallP major alarm

If the CallP major alarm Do

3 For additional help, contact the next level of support.

4 The procedure is complete.

297-2651-543 Standard 05.01 March 1999

Common channel signaling alarm

297-2651-543 Standard 05.01 March 1999

The system refuses commands entered by operating company personnel.

There are no common procedures.

297-2651-543 Standard 05.01 March 1999

Check for PM This flowchart summarizes the

Use the instructions that follow this

N Are there more Y

Check for PM This flowchart summarizes the

Use the instructions in the

End Contact next

297-2651-543 Standard 05.01 March 1999

If LIM or LIU7 alarms Do

If LIM, LIU7, HLIU, or HSLR

4 To post an LK that runs an LK minor alarm, type

Size of Posted Set = 3

posted an in-service trouble LK step 5

5 Record the LK name.

If the far-end office Do

has LIM or LIU7 alarms step 8

297-2651-543 Standard 05.01 March 1999

Size of Posted Set = 3

If the state of the linkset Do