PDF DEFINITY ECS R6 Maintenance For R6r

Definity ECS R6 Maintenance for R6r Definity ECS R6 Maintenance for R6r

User Manual: PDF T E X T F I L E S

Open the PDF directly: View PDF .
Page Count: 2397 [warning: Documents this large are best viewed by clicking the View PDF Link!]

Table of Contents
Contents
About This Book
1. Maintenance Architecture
2. Hardware Configurations
3. Management Terminal
4. Initialization and Recovery
5. Responding to Alarms and Errors
6. Additional Maintenance Procedures
7. LED Indicators
8. Maintenance Commands
9. Maintenance Object Repair Procedures
Index
- Numerics
- A
- B
- C
- D
- E
- F
- G
- H
- I
- J
- L
- M
- N
- O
- P
- Q
- R
- S
- T
- U
- V
- W

555-230-126

Comcode 108136128

Issue 2

January 1998

DEFINITY®

Enterprise Communications Server

Release 6

Maintenance for R6r

Volumes 1 & 2

Printed in U.S.A.

Notice

Every effort was made to ensure that the information in this book was

complete and accurate at the time of printing. However, information is

subject to change.

Your Responsibility for Your System’s Security

Toll fraud is the unauthorized use of your telecommunications system

by an unauthorized party, for example, persons other than your com-

pany’s employees, agents, subcontractors, or persons working on your

company’s behalf. Note that there may be a risk of toll fraud associated

with your telecommunications system and, if toll fraud occurs, it can

result in substantial additional charges for your telecommunications

services.

You and your system manager are responsible for the security of your

system, such as programming and configuring your equipment to pre-

vent unauthorized use. The system manager is also responsible for

reading all installation, instruction, and system administration docu-

ments provided with this product in order to fully understand the fea-

tures that can introduce risk of toll fraud and the steps that can be taken

to reduce that risk. Lucent Technologies does not warrant that this

product is immune from or will prevent unauthorized use of com-

mon-carrier telecommunication services or facilities accessed through

or connected to it. Lucent Technologies will not be responsible for any

charges that result from such unauthorized use.

Lucent Technologies Fraud Intervention

If you suspect that you are being victimized by toll fraud and you need

technical support or assistance, call Technical Service Center Toll

Fraud Intervention Hotline at 1 800 643-2353.

Federal Communications Commission Statement

Part 15: Class A Statement. This equipment has been tested and

found to comply with the limits for a Class A digital device, pursuant

to Part 15 of the FCC Rules. These limits are designed to provide rea-

sonable protection against harmful interference when the equipment is

operated in a commercial environment. This equipment generates,

uses, and can radiate radio-frequency energy and, if not installed and

used in accordance with the instructions, may cause harmful interfer-

ence to radio communications. Operation of this equipment in a resi-

dential area is likely to cause harmful interference, in which case the

user will be required to correct the interference at his own expense.

Part 68: Network Registration Number. This equipment is registered

with the FCC in accordance with Part 68 of the FCC Rules. It is identi-

fied by FCC registration number AS593M-13283-MF-E.

Part 68: Answer-Supervision Signaling. Allowing this equipment to

be operated in a manner that does not provide proper answer-supervi-

sion signaling is in violation of Part 68 Rules. This equipment returns

answer-supervision signals to the public switched network when:

• Answered by the called station

• Answered by the attendant

• Routed to a recorded announcement that can be administered by

the CPE user

This equipment returns answer-supervision signals on all DID calls

forwarded back to the public switched telephone network. Permissible

exceptions are:

• A call is unanswered

• A busy tone is received

• A reorder tone is received

Canadian Department of Communications (DOC)

Interference Information

This digital apparatus does not exceed the Class A limits for radio

noise emissions set out in the radio interference regulations of the

Canadian Department of Communications.

Le Présent Appareil Nomérique n’émet pas de bruits radioélectriques

dépassant les limites applicables aux appareils numériques de la class

A préscrites dans le reglement sur le brouillage radioélectrique édicté

par le ministére des Communications du Canada.

Trademarks

See the preface of this document.

Ordering Information

Call: Lucent Technologies Publications Center

Voice 1 800 457-1235 International Voice 317 322-6791

Fax 1 800 457-1764 International Fax 317 322-6849

Write: Lucent Technologies Publications Center

P.O. Box 4100

Crawfordsville, IN 47933

Order: Document No. 555-230-126

Comcode 108136128

Issue 2, January 1998

For additional documents, refer to the section in “About This Docu-

ment” entitled “Related Resources.”

You can be placed on a standing order list for this and other documents

you may need. Standing order will enable you to automatically receive

updated versions of individual documents or document sets, billed to

account information that you provide. For more information on stand-

ing orders, or to be put on a list to receive future issues of this docu-

ment, contact the Lucent Technologies Publications Center.

European Union Declaration of Conformity

The “CE” mark affixed to the DEFINITY® equipment described in

this book indicates that the equipment conforms to the following Euro-

pean Union (EU) Directives:

• Electromagnetic Compatibility (89/336/EEC)

• Low Voltage (73/23/EEC)

• Telecommunications Terminal Equipment (TTE) i-CTR3 BRI

and i-CTR4 PRI

For more information on standards compliance, contact your local dis-

tributor.

Comments

To comment on this document, return the comment card at the front of

the document.

Acknowledgment

This document was prepared by Product Documentation Development,

Lucent Technologies, Denver, CO.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126

Issue 2

January 1998

Contents

Page iii

Contents

Contents iii

About This Book xv

■Safety Precautions xvi

■Electromagnetic Compatibility Standards xvi

■Standards Compliance xviii

■Conventions Used in This Document xix

■Intended Use xx

■How to Use this Document xx

■Organization xx

■Trademarks and Service Marks xxi

■Related Documents xxii

■Federal Communications Commission Statement xxiv

■How to Order Documentation xxvi

■How to Comment on This Document xxvi

1 Maintenance Architecture 1-1

■What’s new for R6.2r 1-1

■Maintenance Objects 1-7

■Alarm and Error Reporting 1-7

■Port Network Connectivity (PNC) 1-9

■SPE Duplication 1-12

■Power Interruptions 1-22

■Protocols 1-24

■Service Codes 1-38

■Facility Interface Codes 1-39

■Multimedia Interface (MMI) 1-40

2 Hardware Configurations 2-1

■Multi-Carrier Cabinet 2-1

■Carriers in Multi-Carrier Cabinets 2-3

■PNC Cabling — Fiber Hardware 2-8

■Circuit Packs 2-12

■Duplication: Reliability Options 2-17

3 Management Terminal 3-1

■Terminals Supported 3-1

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126

Issue 2

January 1998

Contents

Page iv

■Multiple Access 3-1

■Switch-Based Bulletin Board 3-2

■Switch-Based Bulletin Board Message Notification 3-5

■Connecting the MT 3-24

■Logging On 3-26

■Logging Off 3-28

4 Initialization and Recovery 4-1

■Multiple Offer Categories 4-2

■Hot Restart 4-3

■Reset Level 1 (Warm Restart) 4-3

■Reset Level 2 (Cold-2 Restart) 4-5

■Reset Level 3 (Cold-1 Restart) 4-6

■Reset Level 4 (Reboot) 4-6

■Reset Level 5 (Extended Reboot) 4-7

■Initialization Diagnostics 4-7

■SPE-Down Command Interface 4-9

5 Responding to Alarms and Errors 5-1

■Safety Precautions 5-1

■DEFINITY AUDIX System Power Procedures 5-2

■Electrostatic Discharge 5-3

■Suppress Alarm Origination [y] 5-4

■Reseating and Replacing Circuit Packs 5-5

■Replacing a BIU or Rectifier 5-6

■Replacing SPE Circuit Packs 5-7

■Troubleshooting a Duplicated SPE 5-10

■Executing a Planned SPE Interchange 5-15

■Fiber Fault Isolation Procedure 5-18

■Multimedia Call Handling (MMCH) 5-26

■Troubleshooting ISDN-PRI Problems 5-33

■Troubleshooting ISDN-PRI Endpoints (Wideband) 5-36

■Troubleshooting ISDN-BRI/ASAI Problems 5-38

■Troubleshooting ISDN-PRI Test Call Problems 5-42

■Troubleshooting the Outgoing ISDN-Testcall Command5-44

■Packet Bus Fault Isolation and Repair 5-45

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126

Issue 2

January 1998

Contents

Page v

6 Additional Maintenance Procedures 6-1

■Software Updates 6-1

■DS1 CPE Loopback Jack (T1 Only) 6-10

■Facility Test Calls 6-23

■Preventive Maintenance 6-31

■Analog Tie Trunk Back-to-Back Testing 6-34

■Terminating Trunk Transmission Testing 6-38

■Removing and Restoring Power 6-39

■Automatic Transmission Measurement System (ATMS) 6-40

7 LED Indicators 7-1

■Terminal Alarm Notification 7-1

■Attendant Console LEDs 7-2

■Circuit Pack LEDs 7-3

■Expansion Interface Circuit Pack LEDs 7-4

■Maintenance Circuit Pack LEDs 7-5

■Duplication Interface Circuit Pack LEDs 7-7

■Switch Node Interface LEDs 7-8

■DS1 CONV (TN574/TN1654) Circuit Pack LEDs 7-9

■Tone-Clock Circuit Pack LEDs 7-13

■Maintenance/Test Circuit Pack LEDs 7-13

■LEDs on Standby Components 7-14

8 Maintenance Commands 8-1

■Command Line Syntax 8-1

■Common Input Parameters 8-2

■Common Output Fields 8-5

■Contention Between Simultaneous Commands 8-7

■Busyout and Release Commands 8-8

■Common Abort and Fail Codes 8-10

■Alarm and Error Categories 8-13

■backup disk 8-35

■busyout cdr-link 8-37

■busyout data-module 8-37

■busyout disk 8-38

■busyout ds1-facility 8-38

■busyout fiber-link 8-39

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126

Issue 2

January 1998

Contents

Page vi

■busyout host-adapter 8-40

■busyout journal-printer 8-41

■busyout link 8-42

■busyout spe-standby 8-42

■busyout sp-link 8-43

■busyout tape 8-43

■busyout trunk 8-44

■cancel hardware-group 8-44

■change circuit packs 8-46

■change fiber-link 8-49

■change synchronization 8-52

■change system-parameters maintenance 8-54

■clear errors 8-63

■clear firmware-counters 8-63

■clear pgate-port 8-63

■disable suspend-alm-orig 8-64

■display alarms 8-65

■display errors 8-73

■display events 8-80

■display fiber-link 8-82

■display initcauses 8-83

■display system-parameters maintenance 8-85

■display time 8-94

■enable administered-connection 8-94

■enable suspend-alm-orig 8-94

■enable synchronization-switch 8-96

■enable test-number 8-97

■format card-mem 8-97

■get vector 8-99

■list cabinet 8-101

■list configuration 8-102

■list configuration software-version 8-106

■list disabled-MOs 8-112

■list fiber-link 8-113

■list history 8-114

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126

Issue 2

January 1998

Contents

Page vii

■list isdn-testcall 8-117

■list marked-ports 8-118

■list measurements ds1 8-119

■list pms-down 8-123

■list suspend-alm-orig 8-124

■list sys-link 8-126

■mark port 8-127

■monitor bcms 8-127

■monitor health 8-133

■monitor security violations 8-133

■monitor system 8-134

■monitor traffic 8-142

■monitor trunk 8-144

■recycle carrier 8-145

■release commands 8-145

■reset board 8-147

■reset disk 8-147

■reset fiber-link 8-148

■reset host-adapter 8-149

■reset maintenance 8-149

■reset packet-interface 8-150

■reset interchange 8-152

■reset port-network 8-155

■reset spe-standby 8-157

■reset system 8-158

■reset system interchange 8-160

■reset tape 8-162

■restore announcements 8-163

■restore disk 8-165

■resume hardware-group 8-167

■save announcements 8-168

■save translation 8-171

■set options 8-173

■set pnc 8-181

■set signaling-group 8-182

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126

Issue 2

January 1998

Contents

Page viii

■set snc 8-182

■set synchronization 8-182

■set tdm 8-183

■set time 8-184

■set tone-clock 8-185

■set vector 8-186

■status access-endpoint 8-189

■status administered-connection 8-189

■status attendant 8-192

■status bri-port 8-192

■status cdr-link 8-201

■status cleared-alarm-notif 8-202

■status conference 8-203

■status data-module 8-243

■status hardware-group 8-245

■status health 8-247

■status isdn-testcall 8-250

■status journal-link 8-252

■status link 8-253

■status logins 8-261

■status packet-interface 8-261

■status periodic-scheduled 8-262

■status pgate-port 8-264

■status pms-link 8-265

■status pnc 8-265

■status port-network 8-269

■status processor-channel 8-273

■status signaling-group 8-274

■status spe 8-277

■status sp-link 8-280

■status station 8-281

■status switch-node 8-283

■status sys-link 8-285

■status trunk 8-287

■status tsc-administered 8-289

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126

Issue 2

January 1998

Contents

Page ix

■status tti 8-290

■test alarms 8-292

■test analog-testcall 8-301

■test board 8-302

■test cdr-link 8-303

■test customer-alarm 8-303

■test data-module 8-303

■test disk 8-303

■test ds1-facility 8-304

■test ds1-loop 8-304

■test duplication-interface 8-308

■test eda-external-device-alrm 8-310

■test environment 8-313

■test fiber-link 8-314

■test hardware-group 8-316

■test host-adapter 8-321

■test inads-link 8-321

■test isdn-testcall 8-324

■test journal-printer 8-324

■test led 8-325

■test link 8-326

■test maintenance 8-326

■test mass-storage 8-328

■test memory 8-328

■test mssnet 8-329

■test packet-interface 8-330

■test processor 8-330

■test signaling-group 8-331

■test spe-standby 8-331

■test stored-data 8-333

■test switch-control 8-333

■test synchronization 8-334

■test sys-link 8-334

■test tape 8-336

■test tdm 8-337

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126

Issue 2

January 1998

Contents

Page x

■test tone-clock 8-337

■test trunk 8-337

■test tsc-administered 8-337

■upgrade software 8-337

9 Maintenance Object Repair Procedures 9-1

■Escalation Procedures 9-1

■ABRI-PORT (ASAI ISDN-BRI Port) 9-2

■AC-POWER 9-3

■ADM-CONN (Administered Connection) 9-11

■ADX8D-BD (AUDIX Circuit Pack) 9-14

■ADX8D-PT (AUDIX Digital Port) 9-15

■ADX16D-B (16 Port AUDIX Circuit Pack) 9-22

■ADX16A-BD (AUDIX Circuit Pack) 9-23

■ADX16D-P (16-Port AUDIX Digital Port) 9-24

■ADX16A-PT (AUDIX Analog Line/Control Link) 9-31

■ALARM-PT (ALARM PORT) 9-38

■ANL-16-L (16-Port Analog Line) 9-42

■ANL-BD (Analog Line Circuit Pack) 9-58

■ANL-LINE, ANL-NE-L (8-Port Analog Line) 9-59

■ANN-BD (Announcement Circuit Pack) 9-87

■ANN-PT (Announcement Port) 9-104

■ANNOUNCE 9-112

■ASAI-BD (Multi-Application Platform Board) 9-115

■ASAI-EPT 9-117

■ASAI-PT 9-125

■ASAI-RES/E-DIG-RES (TN800 reserve slot) 9-135

■AUDIX-BD (AUDIX Circuit Pack) 9-136

■AUDIX-PT (AUDIX Port) 9-137

■AUX-BD (Auxiliary Trunk Circuit Pack) 9-138

■AUX-TRK (Auxiliary Trunk) 9-139

■BRI-BD/LGATE-BD (ISDN-BRI Line Circuit Pack) 9-148

■BRI-DAT (ISDN-BRI Data Module) 9-157

■BRI-PORT (ISDN-BRI Port),

ABRI-PORT (ASAI ISDN-BRI Port)] 9-158

■BRI-SET, ASAI-ADJ, BRI-DAT 9-188

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126

Issue 2

January 1998

Contents

Page xi

■CABINET (Cabinet Sensors) 9-221

■CARR-POW 9-228

■CDR-LNK (Call Detail Recording Link) 9-246

■CLSFY-BD (Call Classifier Circuit Pack) 9-247

■CLSFY-PT (Call Classifier Port) 9-248

■CO-BD (Central Office Trunk Circuit Pack) 9-253

■CO-DS1 (DS1 CO Trunk) 9-254

■CO-TRK (Analog CO Trunk) 9-269

■CONFIG (System Configuration) 9-291

■CUST-ALM (Customer-Provided Alarming Device) 9-297

■DAT-LINE (Data Line Port) 9-299

■DC-POWER (Single Carrier Cabinet Environment) 9-308

■DETR-BD (Tone Detector Circuit) 9-313

■DID-BD (Direct Inward Dial Trunk Circuit Pack) 9-314

■DID-DS1 (Direct Inward Dial Trunk) 9-315

■DID-TRK (Direct Inward Dial Trunk) 9-326

■DIG-BD (Digital Line Circuit Pack) 9-339

■DIG-LINE (Digital Line) 9-340

■DIOD-BD (DIOD Trunk Circuit Pack) 9-361

■DIOD-DS1 (DS1 DIOD Trunk) 9-362

■DIOD-TRK (DIOD Trunk) 9-373

■DISK (MSS Disk Circuit Pack) 9-382

■DLY-MTCE (MO-DAILY) 9-405

■DS1-BD (DS1 Interface Circuit Pack) 9-406

■DS1-FAC (DS1 Facility) 9-478

■DS1 CONV-BD 9-502

■DT-LN-BD (Data Line Circuit Pack) 9-533

■DTMR-PT (Dual Tone Multi-Frequency Receiver Port) 9-534

■DUP-CHL (Duplication Interface) 9-539

■DUPINT (Duplication Interface Circuit Pack) 9-571

■E-DIG-BD (Multi Application Platform Board) 9-583

■E-DIG-RES (TN800 reserve slot) 9-585

■E-DIG-STA (Emulated Digital Line) 9-586

■EMG-XFER (Emergency Transfer) 9-596

■EPN-SNTY (EPN Sanity Audit) 9-602

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126

Issue 2

January 1998

Contents

Page xii

■ERR-LOG (Error Log) 9-604

■ETR-PT (Enhanced Tone Receiver Port) 9-605

■EXP-INTF (Expansion Interface Circuit Pack) 9-611

■EXP-PN (Expansion Port Network) 9-669

■EXT-DEV ADMIN? N (External Device Alarm) 9-675

■EXT-DEV ADMIN? Y (External Device Alarm) 9-679

■FIBER-LK (Fiber Link) 9-682

■GPTD-PT (General Purpose Tone Detector Port) 9-721

■H-ADAPTR (MSS Host Adapter) 9-726

■HYB-BD (Hybrid Line Circuit Pack) 9-741

■HYB-LINE (Hybrid Line) 9-742

■INADS (INADS Link) 9-762

■ISDN-PLK (ISDN-PRI Signaling Link Port) 9-765

■ISDN-LNK (ISDN-PRI Signaling Link Port) 9-770

■ISDN-SGR (ISDN-PRI Signaling Group) 9-777

■ISDN-TRK (DS1 ISDN Trunk) 9-790

■JNL-PRNT (Journal Printer Link) 9-813

■LGATE-AJ 9-814

■LGATE-BD 9-814

■LGATE-PT 9-814

■LOG-SVN (Login Security Violation) 9-815

■MAINT (EPN Maintenance Circuit Pack) 9-818

■MEM-BD (32MB Memory Circuit Pack) 9-831

■MET-BD (MET Line Circuit Pack) 9-843

■MET-LINE (MET Line) 9-844

■MIS (Management Information System) 9-861

■MMI-BD 9-862

■MMI-LEV (Multimedia Interface Resource Level) 9-872

■MMI-PT 9-875

■MMI-SYNC 9-881

■MODEM-BD (Modem Pool Circuit Pack) 9-883

■MODEM-PT (Modem Pool Port) 9-884

■M/T-ANL (Maintenance/Test Analog Port) 9-900

■M/T-BD (Maintenance/Test Circuit Pack) 9-909

■M/T-DIG (Maintenance/Test Digital Port) 9-913

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126

Issue 2

January 1998

Contents

Page xiii

■M/T-PKT (Maintenance/Test Packet Bus Port) 9-928

■OPS-LINE (DS1 Off Premises Station Line) 9-933

■PDATA-BD (Packet Data Line Circuit Pack) 9-947

■PDATA-PT (Packet Data Line Port) 9-952

■PDMODULE (Processor Data Module)

TDMODULE (Trunk Data Module) 9-968

■PE-BCHL (PRI Endpoint Port) 9-985

■PGATE-BD (Packet Gateway Circuit Pack) 9-1002

■PGATE-PT (Packet Gateway Port) 9-1018

■PKT-BUS (Packet Bus) 9-1043

■PKT-INT (Packet Interface Circuit Pack) 9-1052

■PMS-LINK (Property Management System Link) 9-1089

■PMS-PRNT/JNL-PRNT (PMS Printer Link) 9-1096

■PNC-DUP (PNC Duplication) 9-1101

■POWER 9-1119

■PRI-CDR/SEC-CDR (Call Detail Recording Link) 9-1131

■PROC-SAN (Process Sanity Audits) 9-1137

■PROCR (RISC Processor Circuit Pack) 9-1138

■RING-GEN 9-1149

■S-SYN-BD (Speech Synthesis Circuit Pack) 9-1155

■S-SYN-PT (Speech Synthesis Port) 9-1156

■SN-CONF (Switch Node Configuration) 9-1169

■SNC-BD (Switch Node Clock Circuit Pack) 9-1177

■SNC-LINK (Switch Node Clock Link) 9-1214

■SNC-REF (Switch Node Clock Reference) 9-1219

■SNI-BD (SNI Circuit Pack) 9-1222

■SNI-PEER (SNI Peer Link) 9-1285

■SPE-SELE (SPE Select Switch) 9-1290

■STBY-SPE (Standby SPE Maintenance) 9-1292

■STO-DATA (Stored Data) 9-1315

■STRAT-3 (Stratum 3 Clock) 9-1338

■SVC-SLOT (Service Slot) 9-1350

■SW-CTL (Switch Control) 9-1352

■SYNC (Synchronization) 9-1364

■SYS-LINK (System Links) 9-1393

■SYS-PRNT (System Printer) 9-1399

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126

Issue 2

January 1998

Contents

Page xiv

■SYSAM (Circuit Pack) 9-1404

■SYSTEM (System) 9-1425

■TAPE 9-1430

■TBRI-BD (TN2185

ISDN Trunk-Side BRI) 9-1465

■TBRI-PT (TN2185

ISDN Trunk-Side BRI Port) 9-1473

■TBRI-TRK (TN2185

ISDN Trunk-Side BRI) 9-1494

■TDM-BUS (TDM Bus) 9-1504

■TDM-CLK (TDM Bus Clock) 9-1521

■TDMODULE (Trunk Data Module) 9-1535

■TIE-BD (Tie Trunk Circuit Pack) 9-1536

■TIE-DS1 (DS1 Tie Trunk) 9-1537

■TIE-TRK (Analog Tie Trunk) 9-1555

■TIME-DAY (Time of Day) 9-1576

■TONE-BD (Tone-Clock Circuit Pack) 9-1578

■TONE-PT (Tone Generator) 9-1597

■TSC-ADM (Administered Temporary

Signaling Connections) 9-1607

■TTR-LEV (TTR Level) 9-1613

■UDS1-BD (UDS1 Interface Circuit Pack) 9-1618

■VC-BD 9-1705

■VC-DSPPT 9-1709

■VC-LEV (Voice Conditioner

DSP Port Level) 9-1719

■VC-SUMPT 9-1722

■WAE-PORT (Wideband Access Endpoint Port) 9-1728

■XXX-BD (Common Port Circuit Pack) 9-1736

IN Index IN-1

About This Book

Page xv

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

About This Book

This document provides instructions and supporting information needed to

monitor, test, and maintain the hardware components of the DEFINITY Enterprise

Communications Server Release 6 systems.

These system’s extensive background testing and technician-demanded tests

allow many problems to be addressed before they severely disrupt call

processing. Duplication options further enhance this reliability, giving the

technician an opportunity to provide a high level of service while resolving

problems or performing routine maintenance.

This book provides the necessary information to make full use of these

capabilities and introduces some new components and strategies found in R6r.

NOTE:

This document is intended for Release 6 and later systems only. For

previous DEFINITY systems (G3V5 and earlier), refer to

DEFINITY

Enterprise Communications Server, Release 5 Maintenance for R5r,

555-230-122.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

About This Book

Page xviSafety Precautions

Safety Precautions

Before working on a system, the technician must be thoroughly familiar with the

precautions and practices described at the beginning of Chapter 5,

‘‘Responding to Alarms and Errors’’.

Class 1 Laser Device

The DEFINITY ECS contains a Class 1 LASER device if single-mode fiber optic

cable is connected to a remote Expansion Port Network (EPN). The LASER

device operates within the following parameters:

Power Output: -5 dBm

Wavelength: 1310 nm

Mode Field Diameter: 8.8 microns

CLASS 1 LASER PRODUCT

IEC825 1993

!DANGER:

Use of controls or adjustments or performance of procedures other than

those specified herein may result in hazardous radiation exposure.

Contact your Lucent Technologies representative for more information.

Electromagnetic Compatibility

Standards

This product complies with and conforms to the following:

■Limits and Methods of Measurements of Radio Interference

Characteristics of Information Technology Equipment, EN55022

(CISPR22), 1993

■EN50082-1, European Generic Immunity Standard

■FCC Parts 15 and 68

■Australia AS3548

NOTE:

The system conforms to Class A (industrial) equipment. Voice terminals

meet Class B requirements.

■Electrostatic Discharge (ESD) IEC 1000-4-2

■Radiated radio frequency field IEC 1000-4-3

■Electrical Fast Transient IEC 1000-4-4

■Lightning effects IEC 1000-4-5

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

About This Book

Page xviiElectromagnetic Compatibility Standards

■Conducted radio frequency IEC 1000-4-6

■Mains frequency magnetic field IEC 1000-4-8

■Low frequency mains disturbance

The system conforms to the following:

■Electromagnetic compatibility General Immunity Standard, part 1;

residential, commercial, light industry, EN50082-1, CENELEC, 1991

■Issue 1 (1984) and Issue 2 (1992), Electrostatic discharge immunity

requirements (EN55024, Part 2) IEC 1000-4-2

■Radiated radio frequency field immunity requirements IEC 1000-4-3

■Electrical fast transient/burst immunity requirements IEC 1000-4-4

European Union Standards

Lucent Technologies Business Communications Systems declares that the

DEFINITY equipment specified in this document bearing the “CE” mark conforms

to the European Union Electromagnetic Compatibility Directives.

The “CE” (Conformité Européenne) mark indicates conformance to the European

Union Electromagnetic Compatibility Directive (89/336/EEC) Low Voltage

Directive (73/23/EEC) and Telecommunication Terminal Equipment (TTE)

Directive (91/263/EEC) and with i-CTR3 Basic Rate Interface (BRI) and i-CTR4

Primary Rate Interface (PRI) as applicable.

The “CE” mark is applied to the following Release 5 products:

■Global AC powered Multi-Carrier Cabinet (MCC)

■DC powered Multi-Carrier Cabinet (MCC) with 25 Hz ring generator

■AC powered Single-Carrier Cabinet (SCC) with 25 Hz ring generator

■AC powered Compact Single-Carrier Cabinet (CSCC) with 25 Hz ring

generator

■Enhanced DC Power System

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

About This Book

Page xviiiStandards Compliance

Standards Compliance

The equipment presented in this document complies with the following (as

appropriate):

■ITU-T (Formerly CCITT)

■ECMA

■ETSI

■IPNS

■DPNSS

■National ISDN-1

■National ISDN-2

■ISO-9000

■ANSI

■FCC Part 15 and Part 68

■EN55022

■EN50081

■EN50082

■CISPR22

■Australia AS3548 (AS/NZ3548)

■Australia AS3260

■IEC 825

■IEC950

■UL 1459

■UL1950

■CSA C222 Number 225

■TS001

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

About This Book

Page xixConventions Used in This Document

Conventions Used in This Document

The following conventions are used in this document:

■DEFINITY Systems are called G3V4, G3 Release 5, G3vs, G3si, and G3r

— All occurrences of G3siV4, G3siV4+m, G3siV5, and G3siV5+m are

called G3si unless a specific configuration is required to

differentiate among product offerings

— All occurrences of G3 with out a suffix following the “3” refer to

G3vs, G3si, and G3r

■A component of a DEFINITY System, such as a circuit pack, occurring

without a reference to any specific system, is part of G3

■DEFINITY Communications Sever is abbreviated DEFINITY ECS

■All physical dimensions in this book are in English (Foot Pound Second)

(FPS) followed by metric Centimeter Grams Second) (CGS) in

parenthesis. Wire gauge measurements are in AWG followed by the

diameter in millimeters in parenthesis.

■Information you type at the management terminal is shown in the following

typeface: list system-parameters maintenance

■Information displayed on the management terminal screen is shown in the

following typeface: login

■Keyboard keys are shown in the following typeface: Enter.

■Circuit pack codes (such as TN790 or TN2182B) are shown with the

minimum acceptable alphabetic suffix (like the ‘‘B” in the code TN2182B).

Generally, an alphabetic suffix higher than that shown is also acceptable.

However, not every

vintage

of either the minimum suffix or a higher suffix

code is necessarily acceptable.

NOTE:

Refer to

Technical Monthly: Reference Guide for Circuit Pack

Vintages and Change Notices

, for current information about the

usable vintages of specific circuit pack codes (including the suffix)

in a Release 6 system.

■Admonishments used in this book are as follows:

!CAUTION:

This sign is used to indicate possible harm to software, possible loss

of data, or possible service interruptions.

!WARNING:

This sign is used where there is possible harm to hardware or

equipment.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

About This Book

Page xxIntended Use

!DANGER:

This sign is used to indicate possible harm or injury to people.

Intended Use

■As a guide to diagnosing and repairing the Release 6r system for use by

field technicians, remote service personnel, and user-assigned

maintenance personnel

■As a training manual for teaching technicians how to maintain the system

■As a reference source on the system’s maintenance capabilities

This document assumes that the technician has a working knowledge of

telecommunications fundamentals and PBX maintenance practices. This

document also assumes that the system was initially installed and tested

properly and brought into service with all faults cleared. Adjuncts and other

devices external to the switch are covered by their own service documentation.

How to Use this Document

Most maintenance sessions involve analyzing the Alarm and Error Logs to

diagnose a trouble source and replacing a component such as a circuit pack.

The information in Chapter 9, ‘‘Maintenance Object Repair Procedures’’ will

generally suffice to address these needs. Certain complex elements of the

system, such as fiber links and the packet bus, require a more comprehensive

approach. Special procedures for these elements appear in Chapter 5,

‘‘Responding to Alarms and Errors’’.

This document is not intended to solve all levels of trouble. When the limits of

these procedures have been reached and the problem has not been resolved, it

is the technician’s responsibility to escalate to a higher level of technical support.

Escalation should conform to the procedures in the

Technical and Administration

Plan

Organization

■Chapter 1, ‘‘Maintenance Architecture’’, describes the system’s design

and maintenance strategy.

■Chapter 2, ‘‘Hardware Configurations’’, shows the locations and

arrangements of the system’s cabinets, carriers, circuit packs, and

cabling.

■Chapter 3, ‘‘Management Terminal’’, describes how to set up and use the

management terminal.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

About This Book

Page xxiTrademarks and Service Marks

■Chapter 4, ‘‘Initialization and Recovery’’, describes the various reset and

reboot processes and how these are used to perform maintenance and

recover systems or subsystems that are out of service. Use of the terminal

SPE-down interface on non-functional or standby Switch Processor

Elements is included here.

■Chapter 5, ‘‘Responding to Alarms and Errors’’, describes general repair

procedures such as replacing circuit packs and special troubleshooting

procedures such as those for fiber link and packet bus faults.

■Chapter 6, ‘‘Additional Maintenance Procedures’’, describes preventive

maintenance, software updates and other procedures not associated with

specific alarms or components.

■Chapter 7, ‘‘LED Indicators’’, is a guide to interpreting indications given by

circuit pack and attendant console LEDs.

■Chapter 8, ‘‘Maintenance Commands’’, contains a description of each

maintenance command available through the management terminal. The

commands are ordered alphabetically. A general description of command

syntax and conventions appears at the beginning of the chapter.

■Chapter 9, ‘‘Maintenance Object Repair Procedures’’, contains specific

troubleshooting and repair instructions for every component in the system.

The maintenance objects are listed alphabetically by name as they

appear in the Alarm and Error Logs. Under each maintenance object

appears a description of the object’s function, tables for interpreting alarm

and error logs, and instructions on how to use tests, commands, and

replacements to resolve associated problems. Most of these procedures

are complete and self-contained, while others rely upon procedures in

Chapter 5, ‘‘Responding to Alarms and Errors’’.

Trademarks and Service Marks

The following are trademarks or registered trademarks of Lucent Technologies:

■5ESS™, 4ESS™

■AUDIX®

■Callvisor®

■Callmaster®

■CentreVu™

■CONVERSANT®

■DEFINITY®

■DIMENSION®

■VOICE POWER®

The following are trademarks or registered trademarks of AT&T:

■ACCUNET®

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

About This Book

Page xxiiRelated Documents

■DATAPHONE®

■MEGACOM®

■MULTIQUEST®

■TELESEER®

The following are trademarks or registered trademarks of other companies:

■Ascend® (registered trademark of Ascend, Inc.)

■Audichron® (registered trademark of the Audichron Company)

■MS-DOS® (registered trademark of the Microsoft Corporation)

■MicroChannel® (registered trademark of IBM Systems)

■MULTIQUEST® (registered trademark of Telecommunications Service)

■PagePac® (trademark of the Dracon Division of the Harris Corporation)

■UNIX® (trademark of the Novell Corporation)

Category

AData modules to terminals

or cluster controller

Data module in ASCII

emulation mode

64 kbps

9.6 kbps

500 feet (152 m)

ISDN-BRI Communication interface

to ISDN-BRI S/T

ISDN-BRI U

64 kbps

160 kbps

655 feet (199.3 m) to network

interface or repeater

1310 feet (399.3 m) system to

system

18,000 feet (5486.4 m) from

system to network interface,

and then ~2000 feet to phone

ISDN-PRI Communication interface

to ISDN-PRI 64 kbps 655 feet (199.3 m) to network

interface or repeater

1310 feet (399.3 m) system to

system

Table 1-8. Protocols Used in DEFINITY — Continued

Protocol Applications Maximum

Data Rate Maximum Distance

Continued on next page

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Architecture

Page 1-35Protocols

Frequency Response

Table 1-9 lists the analog-to-analog frequency response for station-to-station or

station-to-CO trunk, relative to loss at 1 kHz for the United States.

Table 1-10 lists the analog-to-digital frequency response of the system for station

or CO-trunk-to-digital interface (DS0), relative to loss at 1 kHz for the United

States.

Table 1-9. Analog-to-Analog Frequency Response

Frequency (Hz) Maximum Loss (dB) Minimum Loss (dB)

60 —20

200 5 0

300 to 3000 1 -0.5

3200 1.5 -0.5

3400 3 0

Table 1-10. Analog-to-Digital Frequency Response

Frequency (Hz) Maximum Loss (dB) Minimum Loss (dB)

60 — 20

200 3 0

300 to 3000 0.5 -0.25

3200 0.75 -0.25

3400 1.5 0

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Architecture

Page 1-36Protocols

Insertion Loss for Port-to-Port; Analog or Digital

Table 1-11 lists the insertion loss in the system for different connection types for

the United States. Table 1-12 shows the overload and cross-talk characteristics.

Intermodulation Distortion

Table 1-13 lists the intermodulation distortion in the system for analog-to-analog

and analog-to-digital, up to 9.6 kbps data

Table 1-11. Insertion Loss for the United States

Typical Connections Nominal Loss

(dB) at 1 kHz

On-premises to on-premises station 6

On-premises to off-premises station 3

Off-premises to off-premises station 0

On-premises station to 4-wire trunk 3

Off-premises station to 4-wire trunk 2

Station-to-trunk 0

Trunk-to-trunk 0

Table 1-12. Overload and Crosstalk

Overload level +3 dBm0

Crosstalk loss >70 dB

Table 1-13. Intermodulation Distortion

Four-Tone Method Distortion

Second-order tone products >46 dB

Third-order tone products >56 dB

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Architecture

Page 1-37Protocols

Quantization Distortion Loss

Table 1-14 lists the quantization distortion loss in the system for analog port to

analog port.

Table 1-15 lists the quantization distortion loss in the system for analog port to

digital port and digital port to analog port.

Terminating Impedance: 600 Ohms nominal

Trunk balance impedance (selectable): 600 Ohms nominal or complex Z [350 Ohms + (1

k Ohms in parallel with 0.215uF)]

Impulse Noise

On 95% or more of all connections, the impulse noise is 0 count (hits) in five

minutes at +55 dBrnC (decibels above reference noise with C-filter) during the

busy hour.

Table 1-14. Quantization Distortion Loss

Analog Port-to-Analog Port

Signal Level Distortion Loss

0 to -30 dBm0 >33 dB

-40 dBm0 >27 dB

-45 dBm0 >22 dB

Table 1-15. Quantization Distortion Loss

Analog Port-to-Digital Port or

Digital Port-to-Analog Port

Signal Level Distortion Loss

0 to -30 dBm0 >35 dB

-40 dBm0 >29 dB

-45 dBm0 >25 dB

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Architecture

Page 1-38Service Codes

ERL and SFRL Talking State

Echo-Return Loss (ERL) and Single-Frequency Return Loss (SFRL) performance

is usually dominated by termination and/or loop input impedances. The system

provides an acceptable level of echo performance if the ERL and SFRL are met.

Peak Noise Level

■Analog to analog — 20 dBrnC (decibels above reference noise with

C-filter)

■Analog to digital — 19 dBrnC

■Digital to analog — 13 dBrnC

Echo Path Delay

■Analog port to analog port — < 3 ms

■Digital interface port to digital interface port — < 2 ms

Service Codes

Service codes (for the United States only) are issued by the Federal

Communications Commission (FCC) to equipment manufacturers and

registrants. These codes denote the type of registered terminal equipment and

the protective characteristics of the premises wiring of the terminal equipment

ports.

Private line service codes are as follows:

■7.0Y — Totally protected private communications (microwave) systems

■7.0Z — Partially protected private communications (microwave) systems

■8.0X — Port for ancillary equipment

■9.0F — Fully protected terminal equipment

■9.0P — Partially protected terminal equipment

■9.0N — Unprotected terminal equipment

Station-to-station ERL should meet or exceed 18 dB SFRL

should meet or exceed 12 dB

Station to 4-wire trunk connection ERL should meet or exceed 24 dB SFRL

should meet or exceed 14 dB

Station to 2-wire trunk connection ERL should meet or exceed 18 dB SFRL

should meet or exceed 12 dB

4-wire to 4-wire trunk connection ERL should meet or exceed 27 dB SFRL

should meet or exceed 20 dB

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Architecture

Page 1-39Facility Interface Codes

■9.0Y — Totally protected terminal equipment

The product line service code is 9.0F indicating it is terminal equipment with fully

protected premises wire at the private line ports.

Facility Interface Codes

A Facility Interface Code (FIC) is a five-character code (United States only) that

provides the technical information needed to order a specific port circuit pack for

analog private lines, digital lines, MTS lines, and WATS lines.

Table 1-16 through Table 1-18 list the FICs. Included are service order codes,

Ringer Equivalency Numbers (RENs), and types of network jacks that connect a

line to a rear panel connector on a carrier.

Table 1-16. Analog Private Line and Trunk Port Circuit Packs

Circuit Pack FIC Service

Order Code Network

Jack

TN742 and TN747B Off-Premises

Station Port, and TN746B Off-Premises

Station Port or On-Premises Station port

0L13C 9.0F RJ21X

TN760/B/C/D Tie Trunk TL31M 9.0F RJ2GX

Table 1-17. Digital Trunk Port Circuit Packs

Circuit Pack FIC Service

Order Code Network

Jack

TN1654 and TN574 DS1 Converter; TN722B

DS1 Tie trunk; and TN767 and TN464 DS1

Interface

04DU9B,C 6.0P RJ48C

and

RJ48M

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Architecture

Page 1-40Multimedia Interface (MMI)

Multimedia Interface (MMI)

The Multimedia Interface handles the following protocols:

■International Telecommunications Union (ITU) H.221 — Includes H.230,

H.242, H.231, and H.243 protocol

■American National Standards Institute (ANSI) H.221 — Includes H.230,

H.242, H.231, and H.243 protocol

■BONDING (Bandwidth On Demand INoperability Group) Mode 1

■ESM HLP HDLC Rate Adaptation

The Vistium Personal Conferencing System is supported either through the

8510T BRI terminal or directly through the Vistium TMBRI PC board.

Using the World Class Core (WCC) BRI interface, most desktop multimedia

applications are supported through a personal computer’s BRI interface.

Table 1-18. MTS and WATS Port Circuit Packs

Circuit Pack FIC

Ringer

Equivalency

Number (REN) Network

Jack

TN742 and TN746B Analog Line 02LS2 None RJ21 and

RJ11C

TN747B Central Office Trunk 02GS2 1.0A RJ21X

TN753 DID Trunk 02RV2-T 0,0B RJ21X

TN790 Processor 02LS2 1.0A RJ21X

TN1648 System Access and

Maintenance 02LS2 0.5A RJ21X

Hardware Configurations

Page 2-1Multi-Carrier Cabinet

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

2Hardware Configurations

The DEFINITY System supports a variety of configurations consisting of a PPN

and up to 21 EPNs. In addition, the system may use a Center Stage Switch (CSS)

consisting of one or two Switch Nodes. This chapter describes the PPN and EPN

cabinets, and the configuration of carriers and circuit packs within these

cabinets.

Multi-Carrier Cabinet

The Multi-Carrier Cabinet (J58890A) accommodates from one to five circuit pack

carriers, and is always used for the PPN. EPNs may use either multicarrier

cabinets or single-carrier cabinets.

The power unit in the bottom of the MCC cabinet supplies AC voltage or DC

voltage from an external source to the power supply in each carrier. The AC

powered cabinet optionally contains a battery charger and backup batteries to

provide temporary power to the cabinet if the external source fails. The backup

unit is optional for systems powered from an Uninterruptible Power Supply (UPS).

The fan unit in the middle of the cabinet cools the carriers. AC-powered cabinets

have two 120V AC receptacles in the back for use as an AC power source. These

can be used to power the G3-MT.

Each cabinet must be connected to one of the following dedicated power

sources:

■120V AC 60 Hz at 50A from a National Electrical Manufacturing

Association (NEMA) 5-50R power outlet or equivalent

■Single phase 240V AC, or three phase 208V AC, 60 Hz at 30A from a

NEMA L 14-30R power outlet or equivalent

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Hardware Configurations

Page 2-2Multi-Carrier Cabinet

■-48V DC battery plant

■Global MCC uses 50-60 Hz at 200-240 VAC power source

Figure 2-1. Multicarrier Cabinet (J58890A) Configurations

Processor Port Network Cabinet

The PPN cabinet, pictured above, is the primary cabinet in all G3r systems. It

contains the Switch Processing Element (SPE) that controls the system and one

Port Network that is interconnected by the daisy-chained TDM/LAN bus. If the

system has a CSS, the PPN cabinet also contains a switch node. The individual

carriers are described in following sections.

The A position always contains a PPN Control Carrier (J58890AP), also known as

the Processor Carrier, which holds the SPE circuit packs. If the system has a

duplicated SPE, the B position holds a second PPN Control Carrier. At least one,

and up to four, Port Carriers (J58890BB) can be located in the other four carrier

positions, depending on traffic needs and whether the system uses those

positions for other types of carriers. In general, Port Carriers are added in the

sequence, B-C-D-E, unless those positions are used otherwise, as follows.

J58890AP

J58890BB

Port

Carrier Carrier

PPN Control

Duplicated

Carrier

PPN Control

J58890AP

J58890SA

Duplicated

Switch

Node

Carrier

Port

Carrier

J58890BB

Power

Distribution

Unit (G Carrier)

Port

Carrier

J58890BB

J58890SA

Switch

Node

Carrier

Port

Carrier

J58890BB

Processor Port Network

J58890BB

Power

Distribution

Unit (G Carrier)

Duplicated

Switch

Node

Carrier

Port

Carrier

Switch

Node

Carrier

Port

Carrier

Port

Carrier

Expansion

Control

Carrier

Port

Carrier

Expansion Port Network

J58890SA

J58890AF

J58890BB

D Carrier

A Carrier

B Carrier

C Carrier

Fan Unit

E Carrier

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Hardware Configurations

Page 2-3Carriers in Multi-Carrier Cabinets

If the system has a Center Stage Switch, the E position holds a Switch Node

Carrier. In a CSS system with duplicated PNC, the D position holds a Switch

Node Carrier that duplicates the one in E position. In large systems requiring a

CSS with two Switch Nodes, the second SN is located in an EPN cabinet, for both

simplex and duplicated systems. Systems that have added a CSS configuration

after the original installation may have their first SN in an EPN cabinet.

Expansion Port Network Cabinets

When used for an EPN, the multicarrier cabinet supports one Port Network with a

daisy-chained TDM/LAN bus, or, optionally, two separate PNs if the cabinet does

not contain a Switch Node. A cabinet with two PNs has two separate TDM/LAN

bus daisy-chains. One TDM/LAN bus between carriers in positions A, B and C

supports the first PN, and another TDM/LAN bus between positions D and E

supports the second PN. Figure 2-1 shows locations of carriers in EPN cabinets.

Each EPN cabinet contains one Expansion Control Carrier (J58890AF) located in

the A position. In cabinets with one PN, up to four Port Carriers are added as

needed in the sequence B-C-D-E, unless the D or E positions are used for a

Switch Node. Cabinets with two PNs use optional Port Carriers in the B position,

and then the C position for the first PN (above the fans). The second PN, (below

the fans), is configured with the first Port Carrier in the E position and an optional

second Port Carrier in D position.

In large systems with a CSS that requires two Switch Nodes, the second SN is

located in an EPN cabinet (this is usually cabinet number 2, PN number 2). This

EPN may not be remoted by a DS1CONV complex. An EPN with an SN has a

Switch Node Carrier in E position. In systems with duplicated PNC, (Critical

Reliability option), the D position holds another Switch Node Carrier that

duplicates the one in E position.

Carriers in Multi-Carrier Cabinets

PPN Control Carrier (J58890AP)

The PPN Control Carrier contains dedicated slots used for circuit packs that

compose the switch processing element (SPE). It does not contain port circuit

pack slots. This carrier always resides in position A of the PPN cabinet. In a

system with a duplicated SPE, a second PPN Control Carrier resides in the B

position of the PPN cabinet.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Hardware Configurations

Page 2-4Carriers in Multi-Carrier Cabinets

Table 2-1 describes the function of each slot in the PPN Control Carrier.

Table 2-1. PPN Control Carrier Circuit Pack Slots

Slot Name Circuit Pack Code Notes

POWER UNIT

(right side) Power Unit (+5V) 649A Required for DC-powered systems. TRI

PLS OUTPUT DC-Powered cabinets

SYS ACCESS/

MAINTENANCE System Access and

Maintenance TN1648 Required

DUP INTFC Duplication Interface UN330B Required for systems with duplicated

SPE

PROCR RISC Processor UN331B Required

TEST INTFC Used by field support to connect

diagnostic equipment

MEMORY 1 to 4 32 Mbyte Memory TN1650B Two required, up to four optional,

Release 5 requires 3

PACKET INTFC 1

to 3 Packet Interface TN1655 One required, two slots reserved for

future use; with duplicated SPE, both

carriers must use same slot

TONE-CLOCK Tone-Clock TN780

TN2182 Required; TN780 required for interface

to external Stratum 3 Clock

MSS/ NET CON Mass Storage System/

Network Control UN332 Required

DISK DRIVE Disk Drive TN1657 Required

TAPE DRIVE Tape Drive TN1656 Required

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Hardware Configurations

Page 2-5Carriers in Multi-Carrier Cabinets

Port Carrier (J58890BB)

Table 2-2 describes the function of each carrier slot.

Table 2-2. Port Carrier Circuit Pack Slots

Error Code Circuit Pack Test

Result Description/ Recommendation

POWER UNIT

(right side) Power Unit

(+5V) 649A Required for DC-powered systems. TRI

PLS OUTPUT DC-Powered

POWER

UNIT/

SERVICE

Power Unit,

Neon TN755B This position is addressed as “00” in

commands and displays. It does not

provide tip and ring to the wall field. The

following circuit packs are optional,

depending on system features. One

TN771D is required in all PPNs, and one

in each EPN of Critical Reliability systems.

Call Classifier TN744

Integrated

Announcement TN750

Speech

Synthesizer TN725B,

TN433,

TN457

Tone Detector TN748,

TN420B

Maintenance/

Test TN771D

TONE-

CLOCK 1 Tone-clock TN768

TN2182 Required as follows:

EPN with duplicated PNC: B carrier EPN

cabinet with two PNs: D carrier

E carrier of an EPN cabinet with two PNs

and duplicated PNC; the Tone-clock slot

is located with Port Slot #2. If the carrier

does not contain a Tone-Clock board, any

port board may be installed in this slot.

EXPN INTFC

2Expansion

Interface TN570 Optional, depending on system’s

connectivity and duplication

configuration; if not used for an EI board,

this slot can accept any common port

board.

3 If the system’s connectivity and

duplication configuration require a

second EI on a port carrier, it resides in

this slot; otherwise, this slot accepts any

common port board.

4 to 20 Port Boards Any common port board.

Continued on next page

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Hardware Configurations

Page 2-6Carriers in Multi-Carrier Cabinets

Expansion Control Carrier (J58890AF)

The Expansion Control Carrier is located in position A of each EPN. Table 2-3

describes the function of each carrier slot.

Table 2-3. Expansion Control Carrier Slots

Slot Name Circuit Pack Code Notes

POWER UNIT

(left side) Power Unit (+5V)

631DA1 Required for

AC-powered systems

644A1 Required for

DC-powered systems

or empty

MAINTENANCE Maintenance TN775B Required

TONE-CLOCK Tone-Clock TN2182 Required

EXPN INTFC Expansion

Interface TN570 Required

2 to 19 Port Boards Any common port

board. Slot 2 may

house a second EI if

the configuration

requires one.

POWER UNIT/

18, 19 Power Unit, Neon TN755B Required for certain

features; otherwise will

accept any common

port board.

POWER UNIT

(right side) Power Unit

(-48V/-5V) 631DB1 Required for

AC-powered systems

645B1 Required for

DC-powered systems

649A TRI PLS OUTPUT for

Release 5 DC-Powered

cabinets

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Hardware Configurations

Page 2-7Carriers in Multi-Carrier Cabinets

Switch Node Carrier (J58890SA)

Switch Node carriers house the components of a Center Stage Switch (CSS). The

first switch node is located in carrier E of the PPN. If duplicated in a Critical

Reliability configuration, its duplicate is located in carrier D of the PPN. The

second switch node is located in carrier E of a non-remoted EPN. If duplicated in

a Critical Reliability configuration, its duplicate is located in carrier D of the same

EPN.

Table 2-4. Switch Node Carrier Circuit Pack Slots

Slot Name Circuit

Pack Code Notes

POWER UNIT

(right side) Power Unit

(+5V) 649A Required for DC-powered systems

EXPN INTFC

DS1 CONV/ 1 DS1

Converter TN574 Provides fiber connectivity from DS1 facilities

to a remote EPN; this slot used in conjunction

with an SNI in one of slots 2 to 9.

Expansion

Interface TN570 Used for an EI board only in the PPN cabinet

in a system with duplicated PNC (Critical

Reliability); used in conjunction with adjacent

SNI

2 to 9, 13 to 20 Switch

Node

Interface

TN573 SNIs are added sequentially as needed

beginning with slot 2. If a second switch node

is needed, (for more than 16 EPNs), up to 5

SNIs (those in slots 7, 8, 9, 13 and 14) are

connected to corresponding SNIs in the other

SN.

SWITCH

NODE

CLOCK / 10

Switch

Node Clock TN572 Required

SWITCH

NODE

CLOCK / 12

Switch

Node Clock TN572 Used in High Reliability option only

(duplicated SPE, simplex PNC)

DS1 CONV/ 21 DS1CONV TN574 Used as above in conjunction with an SNI in

one of slots 13 to 20

Continued on next page

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Hardware Configurations

Page 2-8PNC Cabling — Fiber Hardware

PNC Cabling — Fiber Hardware

The term “fiber” is used to refer to all the hardware needed for the three basic

types of connections used to form multi-PN systems. Fiber administration

specifies the endpoints to be connected, optional DS1 CONV locations, and

parameters for DS1 Facility Line encoding and equalization. The 3 connection

types are:

1. EI-to-EI or EI-to-SNI Intercabinet hardware

2. EI-to-SNI or EI-to-EI intracabinet hardware

3. EI-DS1CONV or SNI-DS1CONV hardware

EI-to-EI or EI-to-SNI Intercabinet Fiber Optic

Cables

EI-to-EI or EI-to-SNI intercabinet connections are implemented by installing a

lightwave transceiver on the I/O connector plate for each of the administered

fiber endpoints. Each lightwave transceiver has a receive and a transmit

connector for a 62.5 micron or 50 micron fiber connection. Standard fibers are

available in various lengths up to 150 feet (46 m) for single-mode fiber and up to

200 feet (61 m) for multi-mode fiber. These fibers are used to connect lightwave

transceivers to each other when they are close enough together, or to optical

cross-connect facilities for greater distances.

The lightwave transceivers are powered from I/O connector plate leads attached

to TN570 Expansion Interface circuit pack or a TN573 Switch Node Interface

circuit pack. The transceivers include loop-around capabilities to support fiber

fault isolation. Either of two different 9823-type multi-mode transceivers may be

used, depending upon the length of the fiber (table below), or the 300A single

mode fiber transceiver. The transceivers at each end of a given fiber should

match. Figure 2-2 illustrates the interconnection of fiber optic hardware.

Part

Number Maximum Fiber Length Fiber Mode

9823A 4900 feet (1494 m) Multi-mode

9823B 25,000 feet (7620 m) Multi-mode

300A 22 miles (35.4 km) Single mode

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Hardware Configurations

Page 2-9PNC Cabling — Fiber Hardware

Figure 2-2. Fiber Link Connection Hardware

To I/O

Connector

Plate

9823-Type

Lightwave

Transceiver

9823-Type

Lightwave

Transceiver

To I/O

Connector

Plate

FL2P-P-xx

Fiber-Optic

Cables

FL2P-P-xx

Fiber-Optic

Cables

FL2P-P-xx

Fiber-Optic

Cables

To I/O

Connector

Plate

9823-Type

Lightwave

Transceiver

9823-Type

Lightwave

Transceiver

To I/O

Connector

Plate

100A

LIU

Optical Cross-Connect Facility

100A

LIU

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Hardware Configurations

Page 2-10PNC Cabling — Fiber Hardware

EI-to-SNI or EI-to-EI Intracabinet Metallic

Cabling

Metallic cable may be substituted for optical cable for “fiber” connections

between EIs or between an EI and an SNI in the same MCC cabinet. The same

I/O plate connectors are used. The metallic cables should not be used for

intercabinet connections, since doing so violates system ground integrity. The

metallic cable comes in two lengths.

DS1 CONV Cabling

Digital services (DS1) can be used to connect PNs that are up to 100 miles (161

km) apart when fiber optic cabling is not practical. Multi-mode (fiber-connected

PNs must be less than 25,000 feet (7620 m) and less than 22 miles (35.4 km) for

single- mode fiber from the PPN.) A TN574 or TN1654 DS1 Converter (DS1

CONV) circuit pack serves as the interface between the network and an EI or SNI

on the switch. DS1 cabling on a carrier consists of a Y-cable that connects a DS1

CONV to an EI or SNI and to the network. The following cables may be used,

depending upon where the DS1 CONV and the EI or SNI are located:

Part No. Length Intended use

H600-278,G1 13 inches (33

cm) From an EI in slot 1 of a switch node carrier to an

SNI in the same half of the carrier (usually the

adjacent slot)

H600-278,G2 66 inches

(168 cm) From an EI to an SNI in the same cabinet, but in a

different carrier or different half of a carrier

Connection Type Length

Comcode

Number

TN574

Comcode

Number

TN1654

On same half carrier 1 foot (30.48 cm) 846448637 847245750

On different half

carriers in same

cabinet

5.5 feet (1.68 m) 846448645 847245768

Between two

adjacent cabinets 1 foot (30.48 cm),

used with two

9823As, and 1

20-foot (6.1 m) fiber

optic cable

846448652, and

one 846885259

bracket

847245776 with

one 846885259

bracket

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Hardware Configurations

Page 2-11PNC Cabling — Fiber Hardware

The DS1 CONV to EI/SNI cable is a shielded metallic Y-cable held in place at the

EI/SNI port connector by a 4B retainer and at the DS1 CONV port connector by a

4C retainer. The cable end with one 25-pair amphenol connector attaches to the

I/O Plate connector for the EI or SNI. The end with two 25-pair amphenol

connectors attaches to the DS1 CONV I/O Plate connector.

The 13-inch cable 846448652 or 847245776 connects the DS1 CONV to a

fiber-optic cable, enabling the DS1 CONV to connect to an EI or SNI at a greater

distance. The cable end with one 25-pair amphenol connector attaches to a

lightwave transceiver using the 846885259 bracket. The end with two 25-pair

amphenol connectors attaches to the DS1 CONV I/O Plate connector. The other

end of the fiber-optic cable connects to a lightwave transceiver attached to the

I/O plate connector of the EI or SNI.

An H600-348 cable connects the DS1 CONV cable to a Channel Service Unit

(CSU), which connects to a wall field. (Alternatively, connection is sometimes

made directly from the Y-cable to the wall field. See the pinout for the 50-pin

connector at the end of the Fiber Fault Isolation Procedure in Chapter 5,

‘‘Responding to Alarms and Errors’’.) This cable provides from one to four DS1

connections. One end of the H600-348 cable is plugged into the 50-pin

amphenol piggy-back connector on the 8464486xx cable connected to the

DS1CONV port connector. The other end of the H600-348 cable has four 15-pin

sub-miniature D-type connectors that plug into the CSU. A pinout of this cable

appears the end of the Fiber Fault Isolation Procedure in Chapter 5. H600-348

cables come in the following lengths:

Group No. Length Group No. Length

G1 25 feet (7.62 m) G5 125 feet (38.1 m)

G2 50 feet (15.24 m) G6 200 feet (60.96 m)

G3 75 feet (22.86 m) G7 400 feet (121.9 m)

G4 100 feet (30. 48 m) G8 650 feet (198 m)

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Hardware Configurations

Page 2-12Circuit Packs

Figure 2-3. Typical DS1 CONV Connections to Remote EPNs

1. Place duplicate pairs in different carriers.

2. When removing two or more, the maximum cable distance between any

two remoted end points is 100 miles (161 km). For example, if the EPN is

75 miles (121 km) from the PPN, then EPN 2 can only be 25 miles (40.2

km) from the PPN.

3. 846447637 is used within a carrier for a TN574, for TN1654 within a carrier

use a 847245750.

846448645 is used within a cabinet between carriers for a TN574, for

TN1654 within a cabinet between carriers use a 847245768.

Circuit Packs

The following tables list all circuit packs supported by DEFINITY Systems. For

information concerning vintages and current versions, see

Reference Guide for

Circuit Pack Vintages and Change Notices

which is published periodically as a

special edition of the

Lucent Technical Monthly

CIRCUIT

PACK

TN574

G3r

CABINET

CIRCUIT

PACK

TN570

DS1C

G3r

CABINET

CIRCUIT

PACK

TN573

FULLY DUPLICATED

CIRCUIT

PACK

TN573

PPN

EPN

CIRCUIT

PACK

TN574

G3r

CABINET

9823A 9823A

846448637

846448645

H600-348,G-()

FL2P-XX

846448652

H600-348,G()

CONNECT

CROSS

FIELD

CONNECT

CROSS

FIELD

CSU CSU

H600-348,G-()

CIRCUIT

PACK

TN574

G3r

CABINET

CIRCUIT

PACK

TN570

EPN

FOR DIRECT CROSS CONNECT -

SEE TEXT

100 MILES

(SEE NOTE 2)

650 FEET

MAX

CIRCUIT

PACK

TN573

CIRCUIT

PACK

TN574

CSU CSU

9823A 9823A

CONNECT

CROSS

FIELD

CSU CSU

SEE NOTE 1

H600-348,G()

CIRCUIT

PACK

TN574

CIRCUIT

PACK

TN570

CIRCUIT

PACK

TN574

CIRCUIT

PACK

TN570

G3r

CABINET

EPN

SEE NOTE 1

100 MILES

(SEE NOTE 2)

FOR DIRECT CROSS CONNECT -

SEE TEXT

650 FEET

846448637

(SEE NOTE 3)

846448637

(SEE NOTE 3)

650 FEET 650 FEET

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Hardware Configurations

Page 2-13Circuit Packs

Table 2-5. Circuit packs and modules

supported by DEFINITY

Apparatus

Code Name Type

631DA1 AC Power Unit Power

631DB1 AC Power Unit Power

644A1 DC Power Unit Power

645B1 DC Power Unit Power

649A DC Power Unit Power

676B DC Power Supply Power

982LS Current Limiter Power

CFY1B Current Limiter Power

CPP1 Memory Expansion Control

ED-1E546

(TN2169)

(TN2170)

(TN566)

(TN567)

DEFINITY AUDIX R3 System Port Assembly

ED-1E546

(TN2208)

(TN2170)

Call Visor ASAI over the DEFINITY (LAN) Gateway R1 Port Assembly

J58890MAP

(TN800) CallVisor over the DEFINITY LAN Gateway R2 Port Assembly

TN417 Auxiliary Trunk Port

TN419B Tone-Clock Control

TN420B/C Tone Detector Service

TN429 Direct Inward/Outward Dialing (DIOD) Trunk Port

TN433 Speech Synthesizer Service

TN436B Direct Inward Dialing Trunk Port

TN437 Tie Trunk Port

TN438B Central Office Trunk Port

TN439 Tie Trunk Port

TN447 Central Office Trunk Port

TN457 Speech Synthesizer Service

TN458 Tie Trunk Port

Continued on next page

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Hardware Configurations

Page 2-14Circuit Packs

TN459B Direct Inward Dialing Trunk Port

TN464C/D/E/F DS1 Interface - T1, 24 Channel - E1, 32 Channel Port

TN465/B/C Central Office Trunk Port

TN467 Analog Line Port

TN468B Analog Line Port

TN479 Analog Line Port

TN497 Tie Trunk Port

TN553 Packet Data Line Port

TN556/B ISDN-BRI 4-Wire S/T-NT Line (A-Law) Port

TN570/B/C Expansion Interface Port

TN572 Switch Node Clock Control

TN573/B Switch Node Interface Control

TN574 DS1 Converter - T1, 24 Channel Port

TN577 Packet Gateway Port

TN722B DS1 Tie Trunk Port

TN725B Speech Synthesizer Service

TN726/B Data Line Port

TN735 MET Line Port

TN742 Analog Line Port

TN744/B Call Classifier Service

TN744/C/D Call Classifier - Detector Service

TN746/B Analog Line Port

TN747B Central Office Trunk Port

TN748/B/C/D Tone Detector Service

TN750/B/C Announcement Service

TN753 Direct Inward Dialing Trunk Port

TN754/B Digital Line 4-Wire DCP Port

TN755B Neon Power Unit Power

TN756 Tone Detector Service

Table 2-5. Circuit packs and modules

supported by DEFINITY — Continued

Apparatus

Code Name Type

Continued on next page

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Hardware Configurations

Page 2-15Circuit Packs

TN758 Pooled Modem Port

TN760B/C/D Tie Trunk Port

TN762B Hybrid Line Port

TN763B/C/D Auxiliary Trunk Port

TN765 Processor Interface Control

TN767B/C/D/E DS1 Interface - T1, 24 Channel Port

TN768 Tone-Clock Control

TN769 Analog Line Port

TN771D Maintenance/Test Service

TN772 Duplication Interface Control

TN773 Processor Control

TN775/B Maintenance Service

TN776 Expansion Interface Port

TN777/B Network Control Control

TN778 Packet Control Control

TN780 Tone-Clock Control

TN786 Processor Control

TN786B Processor Control

TN787F/G Multimedia Interface Service

TN788B Multimedia Voice Conditioner Service

TN789 Radio Controller Control

TN790 Processor Control

TN793 Analog Line, 24-Port, 2-Wire Port

TN796B Processor Control

TNPRI/BRI PRI to BRI Converter Port

TN1648 System Access/Maintenance Control

TN1650B Memory Control

TN1654 DS1 Converter - T1, 24 Channel/E1, 32 Channel Port

TN1655 Packet Interface Control

Table 2-5. Circuit packs and modules

supported by DEFINITY — Continued

Apparatus

Code Name Type

Continued on next page

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Hardware Configurations

Page 2-16Circuit Packs

TN1656 Tape Drive Control

TN1657 Disk Drive Control

TN2135 Analog Line Port

TN2136 Digital Line 2-Wire DCP Port

TN2138 Central Office Trunk Port

TN2139 Direct Inward Dialing Trunk Port

TN2140/B Tie Trunk Port

TN2144 Analog Line Port

TN2146 Direct Inward Dialing Trunk Port

TN2147/C Central Office Trunk Port

TN2149 Analog Line Port

TN2180 Analog Line Port

TN2181 Digital Line 2-Wire DCP Port

TN2182/B Tone-Clock -Tone Detector and Call Classifier Control

TN2183 Analog Line Port

TN2184 DIOD Trunk Port

TN2198 ISDN-BRI 2-Wire U Interface Port

TN2199 Central Office Trunk Port

TN2202 Ring Generator Power

TN2224 Digital Line, 24-Port, 2-Wire DCP Port

UN330B Duplication Interface Control

UN331B Processor Control

UN332 Mass Storage/Network Control Control

WP-90510 AC Power Supply (Compact Single-Carrier Cabinet) Power

WP-91153 AC Power Supply (Single-Carrier Cabinet) Power

Table 2-5. Circuit packs and modules

supported by DEFINITY — Continued

Apparatus

Code Name Type

Continued on next page

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Hardware Configurations

Page 2-17Duplication: Reliability Options

Duplication: Reliability Options

Standard Reliability Option

On Standard Reliability systems, the 512-time-slot TDM bus is divided into two

duplicate 256-time-slot buses, A and B. Call traffic is shared between the two

buses. The first 5 time slots on each bus are reserved for the control channel,

which is active on only one of the two buses at a time. Likewise, the next 17 time

slots are reserved for carrying system tones. The tone times slot are not

necessarily on the same bus (A or B) as the control channel. If any failure takes

place that affects the ability of the active control or tone time slots to function, the

other bus becomes active for those time slots.

High Reliability Option

High Reliability systems duplicate components that are critical to the viability of

the system as a whole to prevent a single failure from dropping all service:

■PPN control carrier and carrier power units (OLSs)

■All SPE circuit packs: Processor, Memory, MSSNET, Disk, Tape, SYSAM,

Duplication Interface, and carrier power units (OLSs)

■PPN Tone Clock circuit pack (EPN Tone-Clocks are not duplicated)

■TDM buses (described above)

In addition to the above, the following are duplicated in Center Stage Switch

(CSS) configurations:

■The PPN to CSS fiber link (consisting of the PPN Expansion Interface

circuit packs, the Switch Node Interface circuit packs that connect to the

PPN EIs, and cabling from the PPN EI to the CSS)

■Switch Node Clocks (SNCs) (two; on each Switch Node carrier)

The duplicated SPEs operate in active/standby fashion. Interchanges of the SPE

and of PPN Tone-Clocks operate independently unless induced by use of the

SPE-select switches. The 2 SNCs on each Switch Node carrier also operate in an

active/standby manner.

The duplicated fiber link between the PPN EIs and the CSS (the cable may

actually be metallic) do not use an active/standby strategy. Instead, both links

simultaneously carry active call traffic and control connectivity in an equally

distributed load-sharing manner. If a component fails one of these fiber links, all

connectivity over it on it is torn down, resulting in some dropped calls and control

and application links. Links and subsequent call service is immediately

re-established over the other EI fiber link.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Hardware Configurations

Page 2-18Duplication: Reliability Options

Critical Reliability Option

Critical Reliability systems include all of the features of the High Reliability option

described above. Additionally, the duplicate components of Port Network

Connectivity (PNC) and other components critical to the viability of each EPN.

■Switch Node carriers and carrier power supplies (OLSs)

■Switch Node Interface (SNI) circuit packs

■Switch Node Clock (SNC) circuit packs (one on each duplicated Switch

Node carrier)

■PPN and EPN Tone-Clock circuit packs

■PPN and EPN Expansion Interface circuit packs

■Each EPN contains a TN771D Maintenance/Test circuit pack

■Inter-PN cabling

■DS1 Converter Complexes (circuit packs, cabling and DS1 facilities used

to connect remote EPNs)

The entire PNC (whether direct connect or CSS connected) is duplicated as a

whole, forming two identical sets which each function as a whole (A-PNC and

B-PNC). The 2 PNCs operate in an active/standby manner with all inter-PN calls

set up on both PNCs so that the active can assume control without disruption of

service. Operation of PNC duplication is described under PNC-DUP in Chapter

9, ‘‘Maintenance Object Repair Procedures’’.

The Tone-Clocks in each EPN operate in an active/standby manner

independently from other duplication strategies.

Management Terminal

Page 3-1Terminals Supported

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

3Management Terminal

The management terminal is used to enter commands and monitor operations

through the maintenance user interface. Chapter 8, ‘‘Maintenance Commands’’

describes the commands available to the maintenance user.

Terminals Supported

Refer to

DEFINITY Enterprise Communications Server Release 5 Installation and

Test for Multi-Carrier Cabinets

, and the user manual on your terminal model for

setup instructions.

Multiple Access

Release 6r allows multiple users to perform maintenance and administration at

the same time:

■This system has a security feature to allow the customer to define their

own logins and passwords and to specify a set of commands for each

can be customized.

■Login Security Violation Notification Following a Security Violation and

a login ID (Customer or Lucent Services logins) following a security

violation (a user defined security violation threshold). The Login Kill after

“N” Attempts feature will not disable the last remaining inads type login.

Lucent Services logins require a Lucent init level login ID to re-enable

logins that have been disabled by a security violation or the command

disable login.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Management Terminal

Page 3-2Switch-Based Bulletin Board

■

Logoff Notification (Release 5)

alerts system administrators, during log

off from the system administration and maintenance interface, of possible

system maintenance problems. This notification also alerts the system

administrators that features that present a significant security risk are

enabled. A message displays on the system administration/maintenance

interface during logoff if a security risk feature is enabled. Additionally, the

user can be required to acknowledge the notification before the logoff is

completed.

■The system is delivered to the customer with one “super-user” login and

password defined. The customer is required to administer any additional

and can customize any login that they create. Login permissions are set

by the super-user to allow or block any object that can affect the health of

the switch. Up to 40 administration or maintenance objects (commands)

can be blocked for a specified login.

■Two maintenance logins are reserved for the SYSAM-RMT and

SYSAM-LCL ports on the TN1648 SYSAM circuit pack located on PPN

control carriers. SYSAM-RMT is a dial-up remote access port reserved for

use by INADS. SYSAM-LCL is accessed by RS232 connectors on the

TN1648. Two other maintenance users can log in by dial-up System

Access Ports (SAPs) or by connecting directly to EPN Maintenance circuit

packs.

■Up to 5 maintenance and 5 administration commands can run

concurrently. Some commands that use the same resources as others

experience contention and cannot be run at the same time. For more

information on contention, see ‘‘Contention Between Simultaneous

Commands’’ in Chapter 8, ‘‘Maintenance Commands’’.

Switch-Based Bulletin Board

This feature allows a System Access Terminal (SAT) user to leave messages in

the system in order to communicate with other system users.

NOTE:

This feature does not substitute for any existing procedures for escalating

problems. It is only an aid to the existing process.

Description

The bulletin board service provides an easy interface for the customer and

Lucent to leave messages on the system.

The bulletin board feature makes it easy for the customer to communicate with

Lucent (and vise versa). For example, when a new load is installed on a switch in

the customer's system, Lucent is able to leave the customer messages that

describe any new functions. It also allow Lucent to keep you informed on the

progress of trouble items. In addition, you can use this feature to provide

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Management Terminal

Page 3-3Switch-Based Bulletin Board

additional information concerning problems that have already been escalated by

the normal procedure.

Accessing the Bulletin Board

Any user with the appropriate permissions can log into the system and have

access to the bulletin board. Users that have “Maintain System” or “Administer

Features” permissions can enter, change, display, print, or schedule to print a

message. Users that have “Display Admin” and “Maintain Data” permission can

display the bulletin board. Any user who has “Display” permission can display,

print, and schedule to print the contents of the bulletin board.

When a user logs on to the system they are notified of any messages on the

bulletin board. The notification message indicates the last time the bulletin board

was updated, if any “High-Priority” message exist, and if the bulletin board is

80% or more full. If a “High-Priority” message exists, the command prompt will

change to the following message:

■High-Priority Bulletin Board Messages Entered:

After the next command is entered, the default command prompt returns to the

screen.

User Considerations

■Only one user at a time may edit a message on the bulletin board.

■The user must have the proper permissions to access the bulletin board.

■You, the user must maintain the information stored on the bulletin board. It

is your responsibility to delete old messages. If the bulletin board is full

any new messages overwrite old messages.

System Considerations

■The Bulletin Board feature provides up to 3 pages of text for each

message. Each page is limited to 20 lines of text and 40 characters per

line. The first 10 lines of text on page 1 are reserved for Lucent Service’s

High-Priority messages.

System Bulletin Board Commands

The system commands “change bulletin board”, “display bulletin board,” and

existing commands in the user interface are provided for use in the Switch Based

Bulletin Board.

To edit or enter a message on the Switch Based Bulletin Board you must:

1. Log into the system with “Maintain System or Administer Features”

Permissions.

2. Enter the command change bulletin-board.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Management Terminal

Page 3-4Switch-Based Bulletin Board

3. Follow system prompts.

To display messages on the Switch Based Bulletin Board you must:

1. Log into the system with “Maintain System”, “Display Admin,” or “Maint

Data” permissions.

2. Enter the command display bulletin board.

3. Follow system prompts.

Editing a Switch-Based Bulletin Board Message

As stated before, a message may contain up to three pages of information with

the first 10 lines on page 1 reserved for Lucent Service’s

High-Priority

messages

(the “INIT”, “INADS”, and “craft” logins can edit the first 10 lines on page one).

Pages 2 and 3 will allow up to 20 lines of 40 characters of text. Each line has a

date field to show when the line is modified.

The control keys used to edit existing feature forms must be used to edit a

message in the Switch Based Bulletin Board. The following characters are

allowed for use in the text field:

■Uppercase/Lowercase letters, spaces, numerals, and !@#$%^&*()_

-+=[]{};’”<>./?.

NOTE:

Tab characters are not allowed. The existing command line interface will

cause the cursor to move to the next field if a Tab character is entered.

If a user changes any lines which cause 2 or more consecutive blank lines the

bulletin board is automatically reorganized (upon submittal). Two or more blank

lines are changed to a single blank line. A blank line is at the top of a form is also

deleted. This prevent holes in the bulletin board screens as old entries are

deleted.

To save a message entered into the bulletin board text field, you must execute

the save translation command.

The following screen, is an example of bulletin board messages between Lucent

and a customer that is having trouble with trunk group translations:

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Management Terminal

Page 3-5Switch-Based Bulletin Board Message Notification

Switch-Based Bulletin Board Message

Notification

When a user logs on to the system they are notified of any messages on the

bulletin board. The notification message indicates the last time the bulletin board

was updated, if any “High-Priority” message exist and if the bulletin board is 80%

or more full. If a “High-Priority” message exists, the command prompt changes to

the following message:

High-Priority Bulletin Board Messages Entered:

After the next command is entered, the default command prompt returns to the

screen.

To Log In

To log in to the switch:

1. Enter your login name and password on the login and password screen.

If your password has expired you see the message:

Your password has expired, enter a new one.

The password aging screen (Screen 3-1) is displayed when a user logs in.

If the user’s password is expired, the user is prompted to enter a new

password. If your password is within 7 days of the expiration date you see:

display bulletin-board Page 1 of 3

Messages (* indicates high-priority) Date

* Lucent is in the process of 02/02/95

* investigating your trunk lockup problem. 02/02/95

* The Bulletin Board will be updated as 02/02/95

* information is found. 02/02/95

* We have identified the problem. 02/02/95

* The trunk you added does not provide 02/02/95

* disconnect supervision, however your trunk 02/02/95

* group was administered as such. 02/02/95

* Please call for details. 02/02/95

We recently added a new trunk group (14) 02/03/95

and have had trunk group members locking up. 02/03/95

We see the error - Thanks for checking. 02/03/95

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Management Terminal

Page 3-6Switch-Based Bulletin Board Message Notification

Screen 3-1. Password Aging Screen

Forced Password Aging and Administrable

Logins for G3V3 and Later Releases

G3V3 and later releases provide enhanced login/password security by adding a

security feature that allows users to define their own logins/passwords and to

specify a set of commands for each login. The system allows up to 11 customer

logins. Each login name can be customized and must be made up of from 3 to 6

alphabetic/numeric characters, or a combination of both. A password must be

from 4 to 11 characters in length and contain at least 1 alphabetic and 1 numeric

symbol. Password aging is an optional feature that the super-user administering

the logins can activate.

NOTE:

If several “users” are logging in and out at the same time, a user may see

the message “Transient command conflict detected; please try later”. After

the “users” have completed logging in or out, the System Access Terminal

is available for use, try executing the command again.

The password for each login can be aged starting with the date the password

was created, or changed, and continuing for a specified number of days (1 to

99). The user is notified at the login prompt, 7 days before the password

expiration date, that his/her password is about to expire. When the password

expires the user is required to enter a new password into the system before

logging in. If a login is added or removed, the “Security Measurement” reports

are not updated until the next hourly poll, or a clear measurements

security-violations command is entered. Once a non-super-user has changed

his/her password, the user must wait 24 hours to change the password again.

V4 security is enhanced by providing a logoff notification screen to a system

administrator when he/she logs off while either the facility test call or remote

access features are still administered. The administrator can be required to

acknowledge the notification before completing the logoff process. Logoff

notification is administered on the Login Administration screen.

The system is delivered to the customer with one customer “super-user”

and can customize any login that he/she creates.

Password:

Your Password has expired, enter a new one.

Reenter Current Password:

Old Password:

New Password:

Reenter New Password:

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Management Terminal

Page 3-7Switch-Based Bulletin Board Message Notification

object that may compromise switch security. Up to 40 administration or

maintenance objects commands can be blocked for a specified login in. When

an object (administrative or maintenance command) is entered in the blocked

object list on the Command Permissions Categories Restricted Object List form,

the associated administrative or maintenance actions cannot be performed by

the specified login.

There are 3 command categories. Each of the 3 command categories has a

group of command subcategories listed under them, and each command

subcategory has a list of command objects that the commands acts on. See

Table 3-1 and Table 3-2 for a list of objects. A super-user can set a users

permissions to restrict or block access to any command in these categories. The

3 categories are:

■Common Commands

— Display Admin. and Maint. Data

— System Measurements

■Administration Commands

— Administer Stations

— Administer Trunks

— Additional Restrictions

— Administer Features

— Administer Permissions

■Maintenance Commands

— Maintain Stations

— Maintain Trunks

— Maintain Systems

— Maintain Switch Circuit Packs

— Maintain Process Circuit Packs

These categories are displayed on the Command Permissions Categories form.

To Log In

To log in to the switch:

1. Enter your login name and password on the login and password screen

(Screen 3-2).

If your password has expired you see the message:

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Management Terminal

Page 3-8Switch-Based Bulletin Board Message Notification

Screen 3-2. Password Expiration Screen

The Password Expiration screen is displayed when you log in. If your password is

expired you are prompted to enter a new password. If your password is within 7

days of the expiration date you see:

WARNING: Your password will expire in X days

To Logoff

To logoff, enter logoff at the command prompt.

If facility test call notification or remote access notification are enabled for your

receive a logoff screen. If either the facility test call or remote access

acknowledgments are required, you need to respond to the Proceed with

Logoff? prompt on the logoff screen. The response is defaulted to n; you will

need to enter y to override the default.

!CAUTION:

To leave the facility test call administered after you logoff poses a

significant security risk.

!CAUTION:

To Leave Remote Access feature administered after logging off poses a

significant security risk if you are using the feature in conjunction with the

Facility Test Call feature.

Password:

Your Password has expired, enter a new one.

Reenter Current Password:

New Password:

Reenter New Password:

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Management Terminal

Page 3-9Switch-Based Bulletin Board Message Notification

Screen 3-3. Logoff Screen

To Display a Login

To display a specified login:

1. Enter the command display login [login name] and press the Enter key.

The system displays the requested login’s:

■Name

■Login type

■Service level

■Access to INADS Port value (V4)

■Password aging cycle length

■Facility test call notification and acknowledgment

■Remote access notification and acknowledgment

To List Logins

To list all of the system logins and the status of each login:

2. Enter the command list logins.

The system displays the following information for all current logins:

■Name

■Service level

■Status (active, inactive, disabled, svn-disabled, void)

■Password aging cycle length

The system displays only those logins with the same, or lower, service

level as the requestor.

To Remove a Login

To remove a login from the system:

1. Enter the command remove login [login name].

Facility Test Call Administered

Remote Access Administered

Proceed with Logoff? [n]

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Management Terminal

Page 3-10Switch-Based Bulletin Board Message Notification

The system displays the Login Administration form.

2. Press the Enter key to remove the login, or press Cancel to exit the remove

To Test a Login

1. Enter your login name at the login prompt.

Screen 3-4. Login Prompt Form

After the user enters the correct login name and password and the login is

administered correctly, the system displays the command line interface.

Administering Customer Logins and Forced

Password Aging

Adding Customer Logins and Assigning Initial

Password

To add a customer login you must be a super-user, have administrative

permissions, and:

1. Enter the add login [name] command to access the Login Administration

form.

2. Enter your super-user password in the Password of Login Making Change

field on the Login Administration form.

The 3- to 6-character login name (characters 0-9, a-z, A-Z) entered with

the add login [name] command is displayed in the Login’s Name field.

3. Enter customer in the Login Type field. The system default for the

of all types is 11.

4. Enter super-user or non-super-user in the Service Level field. Default is

non-super-user.

■“super-user” gives access to the add, change, display, list, and

remove commands for all customer logins and passwords. The

super-user can administer any mix of super-user/non-super-user

logins up to a total of ten additional system logins.

■“non-super-user” permissions are limited by restrictions specified

by the super-user when administering the non-super-user login. A

non-super-user can change his/her password with permission set

Password:vvvvvvvvcf

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Management Terminal

Page 3-11Switch-Based Bulletin Board Message Notification

by the super-user, however once a password has been changed

the non-super-user must wait 24 hours before changing the

password again. A non-super-user cannot change other user

passwords, login characteristics, or permissions.

5. Enter y in the Disable Following a Security Violation field to

disable a login following a login security threshold violation. This field is a

dynamic field and only appears on the Login Administration form when the

SVN Login Violation Notification feature is enabled. The system default for

the Disable Following a Security Violation field is y.

6. Enter y in the Access to INADS Port? field to allow access to the

remote administration port. This field only displays if Acct. has first

enabled customer super-user access to the INADS Remote Administration

Port. Default is n. This step is valid for V4 and higher systems only.

7. Enter a password for the new login in the Login’s Password field. A

password must be from 4 to 11 characters in length and contain at least 1

alphabetic and 1 numeric symbol. Valid characters include numbers,

and!&*?;’^(),.:- (the system will not echo the password to the screen as

you type).

8. Re-enter the password in the Login’s Password field. The system will not

echo the password to the screen as you type.

9. Enter the number of days (1 to 99) from the current day, that you want the

password to expire, in the Password Aging Cycle Length field. If a you

enter a blank in this field, password aging does not apply to the login.

10. Decide whether or not to leave the default of yes (“y”) in the Facility

Test Call Notification? field. If you retain the default, the user

receives notification at logoff that the facility test call feature access code

is administered. If you do not want the notification to appear, set the field

to n.

!CAUTION:

Leaving The facility Test Call administered after logging off poses a

significant security risk.

11. Decide whether or not to leave the default of yes (“y”) in the Facility Test

Call Notification Acknowledgment Required field. If you retain the default,

the user is required to acknowledge that they wish to logoff while Facility

Test Call is still administered. If you do not want to force the user to

acknowledge, set the field to n. This field appears only if the Facility

Test Call Notification field is set to y.

12. Decide whether or not to leave the default of yes (“y”) in the Remote

Access Notification? field. If you retain the default, the user receives

notification at logoff that remote access is still administered. If you do not

want the notification to appear, set the field to n.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Management Terminal

Page 3-12Switch-Based Bulletin Board Message Notification

!CAUTION:

To Leave Remote Access feature administered after logging off

poses a significant security risk if you are using the feature in

conjunction with the Facility Test Call feature.

13. Decide whether or not to leave the default of yes (“y”) in the Remote

Access Acknowledgment Required? field. If you retain the default,

the user is required to acknowledge that they wish to logoff while remote

access is still administered. If you do not want to force the user to

acknowledge, set the field to n. This field appears only if the Facility

Test Call Notification field is set to y.

Screen 3-5. Login Administration

Changing a Login’s Attributes

To change a customer login’s attributes you must be a super-user, have

administrative permissions (specifically, the Administration Permission

field must be set to y for the super-user), and:

1. Enter the change login [name] command to access the Login

Administration form.

2. Enter your super-user password in the Password of Login Making

Change field on the Login Administration form.

The 3- to 6-character login name (characters 0-9, a-z, A-Z) entered with

the change login [name] command is displayed in the Login’s Name

field.

3. Enter customer in the Login Type field.

4. Enter super-user or non-super-user in the Service Level field.

Password of Login Making Change:

Service Level:

Disable Following a Security Violation?

Access to INADS Port?

Reenter Login’s Password:

Password Aging Cycle Length:

LOGOFF NOTIFICATION

Facility Test Call Notification? y Acknowledgment Required? y

Remote Access Notification? y Acknowledgment Required? y

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Management Terminal

Page 3-13Switch-Based Bulletin Board Message Notification

NOTE:

You cannot change your own service level.

5. To disable a login following a login security threshold violation, enter y in

the Disable Following a Security Violation field. This field is a

dynamic field and only appears on the Login Administration form when the

SVN Login Violation Notification feature is enabled.

6. To allow access to the remote administration port, enter y in the Access

to INADS Port? field. This field only displays if Lucent has first enabled

customer super-user access to the INADS Remote Administration Port.

7. Enter a password for the new login in the Login’s Password field. A

password must be from 4 to 11 characters in length and contain at least 1

alphabetic and 1 numeric symbol. Valid characters include numbers,

and!&*?;’^(),.:- (the system will not echo the password to the screen as

you type).

8. Re-enter the password in the Login’s Password field. The system will not

echo the password to the screen as you type.

9. Enter the number of days (1 to 99) from the current day, when you wish the

password to expire, in the Password Aging Cycle Length field. If a

blank is entered in this field, password aging does not apply to the login.

Administering Login Command Permissions

To administer command permissions, log in as super-user and:

1. Access the Command Permissions Categories form by entering the

command change permissions login [login name]. When the Command

Permission Categories form is displayed for a login, the default

permissions for that “login type” are shown on the form. The super-user

administering the login can change a y to n for each subcategory field on

the form.

2. Select a category for the login and enter y in each field where permission

to perform a administrative or maintenance action is needed. The

command object you select must be within the permissions for the login

type you are administering.

If the Maintenance option is set to y on the Customer Options form, the

super-user can enter y in the Maintain Switch Circuit Packs? or

Maintain Process Circuit Packs fields.

3. A super-user with full super-user permissions (super-user administering

the login cannot have the Additional Restrictions field set to y for

his/her own login) can restrict additional administrative or maintenance

actions for a specified login by entering y in the Additional

Restrictions field on the Command Permission Categories form. Enter

the additional restrictions for a login in the Restricted object list

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Management Terminal

Page 3-14Switch-Based Bulletin Board Message Notification

fields on the Command Permission Categories Restricted Object List form.

You can enter up to 40 command names (object names) to block actions

associated with a command category for a specified login.

Screen 3-6. Command Permission Categories (Page 1 of 3)

Screen 3-7. Command Permissions Categories (Page 2 of 3)

Page 1 of 3

COMMAND PERMISSION CATEGORIES

COMMON COMMANDS

Display Admin. and Maint. Data? y

System Measurements? _

ADMINISTRATION COMMANDS

Administer Stations? y Administer Features? y

Administer Trunks? y Administer Permissions? y

Additional Restrictions? n

MAINTENANCE COMMANDS

Maintain Stations? n Maintain Switch Circuit Packs? n

Maintain Trunks? n Maintain Process Circuit Packs? n

Maintain Systems? n

Page 2 of 3

COMMAND PERMISSION CATEGORIES

RESTRICTED OBJECT LIST

_______________________ ______________________

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Management Terminal

Page 3-15Switch-Based Bulletin Board Message Notification

Screen 3-8. Command Permissions Categories (Page 3 of 3)

Table 3-1. Command Permissions Form Entries — Display Administration and

Maintenance

Object Action

Change Display List Monitor Remove Status Tes

aar analysis X X

aar digit-conversion X X

aar route-chosen X

abbreviated-dialing 7103A-buttons X

abbreviated-dialing enhanced X

abbreviated-dialing group X X

abbreviated-dialing personal X X

abbreviated-dialing system X

aca-parameters X

access-endpoint X X X X

adjunct-names X

adjunt-controlled-agents X

administered-connection X X X

agent-loginID X X

alarms X X

alias-station X

alphanumeric-dial-table X

alternate-frl X

Continued on next page

Page 3 of 3

COMMAND PERMISSION CATEGORIES

RESTRICTED OBJECT LIST

_______________________ ______________________

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Management Terminal

Page 3-16Switch-Based Bulletin Board Message Notification

analog -testcall X

announcements X

ars analysis X X

ars analysis X

ars digit-conversion X

ars route-chosen X

ars-toll X

attendant X X

bcms agent X

bcms lignites X

bcms split X

bcms trunk X

bcms vdn X

board X

bri-port X

bridged-extensions X

bulletin-board X

button-location-aca X

cabinet X X

call-forwarding X

call-screening X

capacity X

card-mem1XX

cdr-link XX

circuit-packs X

communication-interface hop-channels X X

communication-interface links X

communication-interface

proc-channels XX

configuration all X

Table 3-1. Command Permissions Form Entries — Display Administration and

Maintenance — Continued

Object Action

Change Display List Monitor Remove Status Tes

Continued on next page

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Management Terminal

Page 3-17Switch-Based Bulletin Board Message Notification

configuration board X

configuration carrier X

configuration control X

configuration network X

configuration software X

configuration station X

configuration trunk X

console-parameters X

cor X X

cos X

coverage answer-group X X

coverage groups X

coverage path X X

customer-alarm X

data-module X X X X

dappling X

digit-absorption X

display-format X X

do-not-disturb group X

do-not-disturb station X

ds1 X X

dsp-msg-auto-wakeup X

dsp-msg-call-identifier X

dsp-msg-date-time X

dsp-msg-lwc X

dsp-msg-mct X

dsp-msg-miscellaneous X

dsp-msg-property-mgmt X

dsp-msg-softkey-label X

dsp-msg-tod-routing X

Table 3-1. Command Permissions Form Entries — Display Administration and

Maintenance — Continued

Object Action

Change Display List Monitor Remove Status Tes

Continued on next page

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Management Terminal

Page 3-18Switch-Based Bulletin Board Message Notification

emergency X

enp-number-plan X

environment X

errors X

events X

external-device-alarm X

extension-type X

external-device-alarming X

feature-access-code X

fiber-link2XX

groups-of-extensions X

hardware-group XX

health X

history X

hunt-group X X

inads-link X

integrated-annc-boards X X

intercom-group X X

interface1XX

intra-switch-cdr X X

isdn cpn-prefix X

isdn network-facilities X

isdn-testcall X

isdn tsc-gateway X

ixc-codes X

journal-printer X

led X

link XX

listed-directory-numbers X

Table 3-1. Command Permissions Form Entries — Display Administration and

Maintenance — Continued

Object Action

Change Display List Monitor Remove Status Tes

Continued on next page

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Management Terminal

Page 3-19Switch-Based Bulletin Board Message Notification

login3 X

maintenance X

marked-port X

mct-group-extensions X

mct-history X

meas-selection coverage X

meas-selection principal X

meas-selection route-pattern X

meas-selection trunk-group X

meas-selection wideband-trunk-grp X

measurements security-violations detail X

measurements security-violations

summary X

memory X

MO X

modem-pool X X X

multi-frequency signaling X

network-control X

node-routing X X

packet-control1XX

packet-interface2X

paging code-calling-ids X X

paging-loudspeaker X

password X

periodic-scheduled X

permissions X

personal-CO-line X X

pgate X X

pickup-group X X

pkt X

Table 3-1. Command Permissions Form Entries — Display Administration and

Maintenance — Continued

Object Action

Change Display List Monitor Remove Status Tes

Continued on next page

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Management Terminal

Page 3-20Switch-Based Bulletin Board Message Notification

pms X

pms-down X

pms-link X

pms-log X

pnc X

port X X

port-network2X

pri-endpoint X X X X

processor X

remote-call-coverage X

report-scheduler X X X

rhnpa X

route-pattern X X

routing-table X X

scr X

second-digit X

security-violations X

set-data X

signaling-group X X X X

sit-treatment X

site-data X

skill X

sp-link XX

spe X

stargate-port X

station X X X

svn-button-location X

switch-node2X

synchronization X X X

sys-link X X

Table 3-1. Command Permissions Form Entries — Display Administration and

Maintenance — Continued

Object Action

Change Display List Monitor Remove Status Tes

Continued on next page

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Management Terminal

Page 3-21Switch-Based Bulletin Board Message Notification

system X

system 1st-cabinet X

system 2nd-cabinet X

system 3rd-cabinet X

system all-cabinets X

system conn X

system customer-options X

system features X

system-maintenance X

system-parameters cdr X

system-parameters country-options X

system-parameters duplication2X

system-parameters hospitality X

system-parameters security X

tdm X

term-ext-group X X

terminal-parameters 603/302B1 X

terminal-parameters 8400 X

test-schedule X X

time X

time-of-day X

toll X

toll all X

toll restricted-call X

toll-list X

toll unrestricted-call X

tone-clock X

trunk XXX

trunk-group X X X

trunk-group-history X

Table 3-1. Command Permissions Form Entries — Display Administration and

Maintenance — Continued

Object Action

Change Display List Monitor Remove Status Tes

Continued on next page

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Management Terminal

Page 3-22Switch-Based Bulletin Board Message Notification

1. Intel only.

2. MIPS only.

3. Must be super-user.

trunk-group-members X

tsc-administered X

tti X

udp X X

unstaffed-agents X

usage button-type hunt-ns X

usage button-type trunk-ns X

usage button-type night-service X

usage-extensions X

usage-hunt X

vdn X X X

vector X X

wakeup incomplete X

wakeup requests X

wakeup station X

wakeup-log X

Table 3-2. Command Permissions Form Entries — Administer Permissions

Object Action

Add Change Display Enable Remove

permissions X

Table 3-1. Command Permissions Form Entries — Display Administration and

Maintenance — Continued

Object Action

Change Display List Monitor Remove Status Tes

Continued on next page

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Management Terminal

Page 3-23Switch-Based Bulletin Board Message Notification

Table 3-3. Command Permissions Form Entries — Administer Stations

Object Action

Add Change Duplicate Remove

abbreviated-dialing 7103A-buttons X X X

abbreviated-dialing enhanced X X X

abbreviated-dialing group X X X

abbreviated-dialing personal X X

abbreviated-dialing system X X X

alias-station X

attendant X X X

console-parameters

data-module X X X X

routing-table X X X

station X X X X

terminal-parameters 603/302B1 X

terminal-parameters 8400 X

vdn X X X

vector X

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Management Terminal

Page 3-24Connecting the MT

Connecting the MT

The management terminal can be connected to the system in the following ways:

■SYSAM-LCL Port

The management terminal can be connected directly to the SYSAM-LCL

port of the TN1648 System Access and Maintenance (SYSAM) circuit

pack in the PPN control carrier (or SPE). Two RS-232 connectors are

located on the rear panel of the PPN control carrier beneath the label

TERMINAL. To access the maintenance user interface running on the

Table 3-4. Command Permissions Form Entries — Administer Trunks

Object Action

Add Change Display Duplicate Remove

aar analysis X

aar digit-conversion X

access-endpoint X X X X

announcements X

ars analysis X

ars digit-conversion X

ars toll X

digit-absorption X

meas-selection route-pattern X

meas-selection trunk-group X

meas-selection wideband-trunk-grp X

modem-pool X X X

personal-CO-line X X X

pri-endpoint X X X X

remote-access X X

rhnpa X

route-pattern X

time-of-day X

toll X

trunk-group X X X

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Management Terminal

Page 3-25Connecting the MT

active SPE, connect an M25B (EIA) cord to the connector labeled ACTIVE.

Connect the other end to the connector on the 715 BCS labeled P2(DCE).

On most other terminals, use the connector labeled MAIN PORT. A null

modem is not required for these ports. More information on setting up the

715 BCS is given in following sections of this chapter.

On systems with duplicated SPEs, there are two PPN control carrier and

two identical sets of connectors. Either connector labeled ACTIVE can be

used, regardless of which SPE is active. The STANDBY connectors are

described below.

■SYSAM-RMT Port (RAP)

One login can access the system by dialing in to the SYSAM-RMT port

with a modem operating at either 1.2 or 2.4 kbps. This port is reserved for

INADS (Initialization and Administration System) access.

Logging In When The SPE Is In SPE Down Mode

If the system is in SPE down mode when the RAP Terminal displays login, enter

INADS as the RAP login/name. Use the first INADS type password as your RAP

password.

NOTE:

You must identify the first INADS login before the system is in SPE

down mode. The first INADS type login may be identified by entering

the list login command and noting the first INADS login listed.

■System Ports

Terminals can log in via system ports (also known as system access ports

or SAPs) if the system is so equipped. The connection is made by dialing

in to a to a data port located on a data line circuit pack that is

administered as a system port. This type of port is identified by the entry

Type: system port on the data module form. These ports operate at

9.6 kbps. For more information on system ports, see ‘‘PDATA-PT (Packet

Data Line Port)’’ in Chapter 9, ‘‘Maintenance Object Repair Procedures’’

and

DEFINITY Enterprise Communication Server Release 6 Administration

and Feature Description

■EPN Maintenance Circuit Pack

Terminals can log in to the system by directly connecting to the TN775

Maintenance circuit pack in each Expansion Port Network. Connect an

M25B (EIA) cord to the RS-232 connector labeled TERM on the rear panel

of the expansion control carrier. This connection operates at a slower

speed because it communicates over system control links shared with call

processing messages. The bit rate is limited to about 1 kbps. This type of

connection is useful for performing maintenance on a remotely located

EPN.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Management Terminal

Page 3-26Logging On

■Standby SPE Connection

With duplicated SPEs, there are two SYSAM connectors on each PPN

control carrier (A and B). Either carrier’s connectors may be used. Either

ACTIVE connector always access the active SPE regardless of which

carrier is active. Either STANDBY connector accesses the standby SPE

through the SPE-Down interface. This interface is available when the SPEs

are locked by the SPE-Select switches on a system with duplicated SPEs.

Otherwise the STANDBY connection is inactive. (On a simplex SPE, this

interface is accessed when the SPE is down through the ACTIVE

connector). Separate terminals may be connected to the two connectors,

or one terminal may be switched back and forth between connections.

The unused connectors should be capped.

The SPE-down interface can only be accessed by SYSAM-LCL or SYSAM-RMT

connections. This interface is described in

Initialization and Recovery

Serial Printer Connection

For serial printer operation, connect the printer to the connector on the back of

the 715 BCS terminal labeled P1(DCE). A null modem is not required. Set the

printer for 9600 baud, 7 data bits and 1 stop bit. These are the default settings for

the 715 BCS. If necessary, terminal settings for serial printer operations can be

changed from the Communication Options sub-menu of the Setup menu.

Parallel Printer Connection

For parallel printer operation, connect the printer to the connector labeled with

the printer icon. To enable parallel printer operation, use the following series of

keystrokes.

1. Cntl + F1 to access the Setup menu

2. F4 to select the User Preferences sub-menu

3. Down arrow to the Parallel Port field

4. F4 to enable the option

5. F1, F5, F1 to return to Setup, save selections, and exit

Logging On

To log in to the system:

1. Connect and power up the MT; the screen displays login:

2. Enter your login name, and press the Return key. The screen displays

password:

3. Enter your password, and press the Return key.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Management Terminal

Page 3-27Logging On

For security reasons, the password is not displayed as you type it. The

system verifies that a valid login and password name were entered. If an

invalid login or password name was entered, the screen displays login

incorrect:

In this case you must repeat the procedure. If your password has expired

or is within 7 days of the expiration day, you see a error message:

Your Password has expired; enter a new one

Old Password:

New Password:

WARNING: your password will expire in xx days

If the system recognizes the login and password name, the screen

displays the software version number followed by the prompt:

Terminal Type (Enter 513, 4410, 4425, or VT220):

[513]

4. Depending on your terminal type, enter one of the following:

5. You can deactivate INADS alarm origination whenever you log in as craft.

After you supply the terminal type information requested, the system will

display the following if alarm origination is activated on the Maintenance

System-Parameters screen:

Suppress Alarm Origination: [y]

The default answer is yes. If you do NOT wish to suppress alarm

origination, enter no. Any other entry will default to yes. The test

inads-link command will work regardless of whether you have overridden

INADS alarm origination.

6. The screen will display:

enter command:

The system is now ready to execute maintenance commands. Press the

HELP key to display a list of all valid entries.

If you have a High-Priority Bulletin Board Message, the command line

prompt will include the following notification to all users who are logged in:

-High-Priority Bulletin Board Messages Entered:

Terminal Type Entry

513 BCT 513 (default)

715 BCS 513 (default)

4410 Data Terminal 4410

4425 Data Terminal 4425

DEC VT220 VT220

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Management Terminal

Page 3-28Logging Off

Logging Off

The terminal should be logged off whenever it is not in use to avoid accidental or

malicious entries that could corrupt translations or disrupt operations. This also

re-enables INADS alarm origination so that alarms will not go unreported.

To log off, simply enter logoff at the command prompt. The screen should then

display:

If no entry is made for 30 minutes during a craft login, the system automatically

times out and terminates the login. At that time, any unresolved alarms that have

not been reported to INADS will be reported. If you are logged in at more than

one G3-MT terminal, the system waits until the last terminal times out or logs off

before reporting such alarms to INADS.

Logoff Notification

alerts system administrators of enabled features that present

a significant security risk. The user may be required to acknowledge the

notification before the logoff is completed

Initialization and Recovery

Page 4-1

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

4Initialization and Recovery

When the system is powered up, or when it experiences a catastrophic fault that

interrupts its basic functions, it undergoes a reboot. In addition to reboot, there

are several less severe resets available for the system to recover from less

disrupting errors. The technician can also initiate these resets with a command.

!CAUTION:

System resets can have wide-ranging disruptive effects. Unless you are

familiar with resetting the system, follow normal escalation procedures

before attempting a demand reset.

If a reset fails to recover normal system operation, the firmware that controls reset

will escalate to the next higher level, up to reboot if necessary. A failure to reboot

results in SPE-down mode, which is described in later in this chapter.

This chapter describes the causes, effects, and duration of each reset level. In a

system with duplicated SPE, the standby SPE can undergo a reset without

disrupting service since the active SPE remains in control. These resets can also

be requested with the corresponding reset standby-spe

level

commands. All

standby resets turn off memory shadowing, leaving the standby SPE temporarily

unavailable for service. Refresh of the standby typically takes several minutes.

When resets occur, including interchanges, an error is logged against the

maintenance object “SYSTEM.” The error code gives information about the cause

of the reset. Information about the reset is also logged in the initcauses log. See

display initcauses in Chapter 8, ‘‘Maintenance Commands’’.

The EPNs can also undergo individual resets. These are described in ‘‘EXP-INTF

(Expansion Interface Circuit Pack)’’ and ‘‘EXP-PN (Expansion Port Network)’’ in

Chapter 9, ‘‘Maintenance Object Repair Procedures’’. PNC interchanges are

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Initialization and Recovery

Page 4-2Multiple Offer Categories

described under PNC-DUP in Chapter 9, and under reset pnc interchange in

Chapter 8, ‘‘Maintenance Commands’’.

Multiple Offer Categories

When the system is initially powered up, or when it experiences a catastrophic

fault that interrupts its basic functions, the system either initializes or reboots.

Initialization

Upon initialization, no forms (not even Customer Options) are available until the

Offer Category is set. (The remote INADS channel is available.) To set the

customer options, do the following:

1. Enter change system-parameters offer-options (init and inads logins

only) and the following form displays:

Field descriptions

2. After these two fields are filled and you press Enter, the system displays:

WARNING: Activating Offer Category may set unchangeable

limits.

This is to let you know that the Offer Category along with the model

determine the system capacities (limits) and allowable hardware.

3. Press the Submit key to submit the form.

4. Use the save translations command to make the changes permanent.

Offer category Type either A or B.

Activate offer? Type y if the entry for Offer category is correct and press Tab.

Type n if there is an error in the Offer category field and press

Tab. Re-enter the correct Offer Category.

change system-parameters offer-options

OFFER OPTIONS FORM

Offer Category: _

Activate Offer? _

WARNING: Need to save translations and reboot to make the change permanent.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Initialization and Recovery

Page 4-3Hot Restart

!CAUTION:

To avoid potential loss of servce, ensure that your system’s

translations are protected by saving them to the PCM/CIA card.

Hot Restart

This reset occurs only on a duplicated SPE during a

planned

SPE interchange.

Reset Level 1 (Warm Restart)

Duration Up to 1.5 minutes

Causes reset system interchange command

(use of the contention-override or health-override options

causes a reset level 1 or higher)

SPE interchange requested by scheduled maintenance

Effects Call service is unaffected.

Yellow LEDs light on new active SPE and go out on the new

standby.

Memory shadowing is turned off.

Remote access port (SYSAM-RMT) login is dropped.

Duration Up to 10 seconds, typically 2 seconds

Causes reset system 1 command

Spontaneous SPE interchange (those caused by hardware

faults)

Software faults that are non-service affecting

Abort of planned SPE interchange

Hardware bus errors

TN1655 Packet Interface faults

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Initialization and Recovery

Page 4-4Reset Level 1 (Warm Restart)

Effects Stable calls are preserved.

System links, and stable feature and service state data are

preserved.

Error and alarm logs are preserved, but all alarms are resolved

except for STBY-SPE and busyouts.

Transient calls (not yet connected), and some user stimuli, are

dropped.

New calls are not processed during the reset.

G3-MT logins, including remote access and system port logins,

are dropped.

If the reset resulted from a spontaneous SPE interchange,

memory shadowing is turned off, and the standby SPE will not

be available for service until memory is refreshed (several

minutes).

Application links such as those to AUDIX and CDR are

dropped and reestablished in under 2 1/2 minutes. (BX.25 links

are not dropped, and CDR data is buffered during the outage.)

MSS activity is aborted.

Translation data is preserved, but if translation changes were in

progress, the reset is escalated to Reset Level 3 (Cold-1).

If core dump is enabled for this reset level, reset is delayed

until the core dump is complete.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Initialization and Recovery

Page 4-5Reset Level 2 (Cold-2 Restart)

Reset Level 2 (Cold-2 Restart)

Duration Up to 3.75 minutes

Causes reset system 2 command

Escalation from reset level 1

An attempted reset level 1 during a PNC interchange

TDM-bus clock recovery on the PPN

Spontaneous interchange into an unrefreshed standby SPE

Effects All system and application links are dropped.

All calls are dropped.

Non-translation feature data, such as Automatic Wakeup calls,

are lost and must be reentered.

All G3-MT logins, including remote access and system port

logins, are dropped.

Initialization firmware runs diagnostics and displays results on

the G3-MT screen.

SPE memory shadowing is turned off, leaving the standby SPE

unavailable for service for several minutes.

All hardware components, except PNC components, are reset,

including the EPNs. All standby Expansion Interfaces, and the

active EI in the PPN are reset. SNIs, SNCs, DS1Cs and active

EIs in the EPNs are not reset.

If the PNC is duplicated, a global refresh of the standby PNC is

performed after the reset.

All busied out maintenance objects are released and must be

rebusied, if so desired.

Circuit packs are reinitialized, (translations are verified by

comparison to physical board locations).

If core dump is enabled for this reset level, reset is delayed

until the core dump is complete.

Error and alarm logs are preserved, but all alarms are resolved

except for STBY-SPE and busyouts.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Initialization and Recovery

Page 4-6Reset Level 3 (Cold-1 Restart)

Reset Level 3 (Cold-1 Restart)

Reset Level 4 (Reboot)

Duration Up to 6.5 minutes

Causes reset system 3 command

Escalation from reset level 2

Translation loading fault

Spontaneous interchange into an unrefreshed standby SPE

Effects Actions and effects are the same as for reset level 2, plus the

following:

Emergency transfer is invoked.

Translations are reloaded from disk or tape.

If core dump is enabled for this reset level, reset is delayed

until the core dump is complete.

Translations entered by users since the last save translation

was executed by command or by scheduled maintenance are

lost.

Duration Typically 8 to 11 minutes

Causes reset system 4 command

Escalation from reset level 3

Power up

Recovery attempt from SPE-down mode (requested by reboot

command, or automatically every 20 minutes)

Spontaneous interchange into an unrefreshed standby SPE

Effects System software (boot image) is reloaded, and all processes

are reinitialized

The disk, if present and healthy, is the default device from

which the software is loaded. Otherwise, the reload is taken

from tape

Before reboot, the system attempts to save the alarm and error

logs to the disk on the active SPE

After reboot, error and alarm logs are restored from the SPE

that is active coming out of the reboot. (Note that this means

that some error and alarm information may be lost if the last

save before the reboot save does not succeed or if an SPE

interchange takes place)

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Initialization and Recovery

Page 4-7Reset Level 5 (Extended Reboot)

Reset Level 5 (Extended Reboot)

Initialization Diagnostics

For each reset level, the system performs a series of diagnostic tests on

components of the SPE to confirm that the system can be brought into service.

The management terminal displays the result of each test as it occurs. If a reboot

fails, and the system cannot bring itself up, SPE-down mode is invoked. A

description of this mode, with troubleshooting procedures available to it, appears

in the following section.

Table 4-1 shows the diagnostic tests run during initializations. Level 1, 2 and 3

resets 4 perform the first 11 tests (through the Timer Test). Reboots complete all

tests in the table except the last one. Only extended reboots execute the Memory

Board Couple Test.

If a test fails, make the indicated repair. If more than one repair is indicated,

perform them in the order shown until the problem is resolved. Follow procedures

described in ‘‘Replacing SPE Circuit Packs’’ in Chapter 5, ‘‘Responding to

Alarms and Errors’’.

Other effects are the same as those in reset level 3, except that

more extensive diagnostics are performed.

If reboot fails, SPE-down mode is invoked.

If a core dump is enabled for this reset level via the set vector

command, the reboot is delayed until the core dump has

completed.

Duration Up to 25 minutes

Causes reset system 5 command

This reset is invoked only by command

Effects Effects are the same as for a level 4 reboot except that more

extensive diagnostics are performed.

This reset is used to diagnose SPE component failures not

detected by level 4 reboot tests.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Initialization and Recovery

Page 4-8Initialization Diagnostics

Table 4-1. Initialization Diagnostics for All Reset Levels

Test Description/Recommendation

Internal Register Test Replace processor.

Loop Data Test Replace processor. Replace memory 1. Reseat

all circuit packs in the processor carrier except

SYSAM. The carrier may be defective. Follow

normal escalation procedures.

Duart Test Replace the processor board. Failure of this test

will not prevent the system from running, but the

processor is probably faulty.

Rom Checksum Test Replace the processor.

Control Status Test Replace the processor.

Dcache Test Replace the processor. Failure of this test may

not prevent the system from running, but

degradation of service is probable.

Icache test Replace the processor. Failure of this test may

not prevent the system from running, but

degradation of service is probable.

Write Buffer Test Replace the processor. Replace the memory 1.

Bus Test Replace processor. Replace memory 1. Reseat

all circuit packs in the processor carrier except

SYSAM. The carrier may be defective. Follow

normal escalation procedures.

Parity Test Replace the processor. Replace the SYSAM.

Timer Test Replace the processor.

Bus Config Test Replace processor.

Mem Config Test Check memory boards for correct TN number

and positioning on the carrier. Reseat memory

boards.

Memory Functional Test Replace memory boards one at a time until test

passes.

Memory Board Stuck Bit

Test Replace memory board.

Memory Board EDC Test Replace memory board.

Continued on next page

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Initialization and Recovery

Page 4-9SPE-Down Command Interface

SPE-Down Command Interface

A limited command interface called the SPE-down interface can be used to

communicate with low level firmware when system software is unavailable for

executing the usual maintenance commands. This is useful in three situations.

■The SPE is down in a system without duplicated SPEs

■The standby SPE is down in a system with duplicated SPEs

■One SPE is locked standby in a system with duplicated SPEs

Memory Board Burst Test Replace memory board Replace processor

board The carrier may be defective. Follow

normal escalation procedures.

Sysam Test Replace the SYSAM board.

Vm Test Replace the processor.

Exception Test Replace the processor.

MSS Test Replace the MSSNET board. Replace the

processor.

Sanity Timer Test Replace the SYSAM board.

Dupint Test Replace the DUPINT board.

Disk Test Replace the disk drive.

Loading Disk Reformat disk. Replace the MSSNET board.

Ram Data Checksum Test Reboot from whichever device (tape or disk) was

not

used for the failed reboot. Replace memory.

Ram Text Checksum Test Reboot from whichever device (tape or disk) was

not

used for the failed reboot. Replace memory.

Tape Test Replace the tape cartridge. Replace the tape

drive. Replace the MSSNET board.

Pktint Reset Test Replace the packet interface board.

Mem Board Couple Test

(Extended reboot only) Replace the indicated memory board.

Table 4-1. Initialization Diagnostics for All Reset Levels — Continued

Test Description/Recommendation

Continued on next page

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Initialization and Recovery

Page 4-10SPE-Down Command Interface

SPE-Down Mode

Severe problems with components of the SPE may render a non-duplicated

system incapable of call processing and other normal operations. When this

happens, the system enters SPE-down mode and software is no longer in control.

If the SPE is duplicated, this situation only occurs when

both

SPEs have fatal

faults. Otherwise, if one SPE goes down, an interchange will occur and the

system will run on the newly active SPE.

SPE Locked Standby or Standby SPE-Down

The SPE-down interface can be useful when repairing a standby SPE on a

duplicated system. For example, if handshake communication is down, this is the

only way to communicate with the standby SPE. Or, if a circuit pack on the

standby has been replaced, this interface allows you to test both that circuit pack

and the rest of the standby SPE before unlocking.

When the standby SPE on a duplicated system is down, or locked by means of

the SPE-Select switches, it is no longer in communication with the active side,

and the system is functionally unduplicated. In this state, the normal

Maintenance User Interface is unavailable to the standby SPE. You can use the

SPE-down interface to test the standby SPE and verify its health before rebooting

or unlocking. A test of all SPE boards takes only a short time and ensures that all

problems have been fixed and the SPE is ready to return to service.

Bringing Up the SPE-Down Interface

When SPE-down mode is in effect, the red LED will be lit on the Processor circuit

pack and the system will present the following message:

An alarm-notification call already in progress will preempt input from the terminal.

When the call is completed or dropped, the system displays the results of the call

and a welcome message with one of the following prompts, indicating which SPE

is currently connected to the terminal.

*********** SPE DOWN MODE *************

SPE_A_DOWN> If SPE-A was active when the system went

down

SPE_B_DOWN> If SPE-B was active when the system went

down

SPE_DOWN> If the SPE is unduplicated

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Initialization and Recovery

Page 4-11SPE-Down Command Interface

You can now enter SPE-down interface commands as described in ‘‘Using the

SPE-Down Interface’’. If the prompt does not appear, check the connections

between the terminal and the control carrier. Make sure the cable is connected to

the connector labeled

ACTIVE

. If possible, try a different cable and/or terminal. If

the prompt is still not present, replace the SYSAM circuit pack. If the SPE remains

down with no prompt, follow normal escalation procedures.

To return the standby SPE to service, see the following section on ‘‘Bringing the

SPE Back into Service’’.

SPE Locked Standby or Standby SPE-Down

To bring up the SPE-down interface on a functioning duplicated system, connect

the terminal to the STANDBY terminal connector on the rear panel of either

processor carrier. Assuming all cabling is intact, either connector will access the

SPE which is standby. If the standby SPE is down, the message and prompt

shown above are displayed. To enter SPE-locked-standby mode, carefully, and

one at a time

, move the SPE-Select switches to the position indicating the carrier

of the currently active SPE. For example, if the SPE in carrier A is active, move the

switches to position A. When the SPE is locked, SPE interchanges are prevented,

memory shadowing is turned off, handshake is down, and maintenance activities

normally controlled by software on the active SPE cease. The following message

is printed, (in this example, A is locked standby):

One of the following prompts will appear, indicating which SPE is locked

standby

and whether the SPE is down.

SPE_A_LOCKED>

SPE_B_LOCKED>

SPE_A_DOWN_LOCKED>

SPE_B_DOWN_LOCKED>

You can now enter the commands described in ‘‘Using the SPE-Down Interface’’.

If the prompt fails to appear, check your connections. Try connecting to the

connector labeled STANDBY on the other PPN control carrier (A or B). If

possible, try using a different cable and/or terminal. If the above actions do not

produce a prompt, replace the SYSAM circuit pack on the standby SPE. If the

prompt is still not present, follow normal escalation procedures.

If an SPE was down and the SPE-Select switches are set to lock, the

down-and-locked-standby mode

replaces

the SPE-down mode. Normally, when

the standby SPE is up and cycling, the yellow LED on the Processor circuit pack

flashes on and off. If the SPE is locked standby

and

a terminal is connected to

the STANDBY connector, the Processor LED remains unlit.

*********SPE A locked standby************

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Initialization and Recovery

Page 4-12SPE-Down Command Interface

To return the standby SPE to service, see the following section on ‘‘Bringing the

SPE Back into Service’’.

NOTE:

The physical connection of the terminal to the STANDBY connector while

the SPE is locked standby with the SPE-Select switches prevents the

Standby Maintenance Monitor (SMM) from running. Any reboot command

to the standby while it is in the locked state will abort.

Using the SPE-Down Interface

When one of the above prompts appear, you may enter Spe-down interface

commands. These are executed by the Low-level Maintenance Monitor (LMM),

which is firmware resident on the processor board for controlling initialization and

recovery actions, and processor and memory diagnostics.

Communications with the terminal are handled by the SYSAM board. If a remote

access port (SYSAM-RMT) call is received while in this mode, it will preempt

access by the local MT, and this message will be displayed:

When the call is completed or dropped, the prompt will return. Note that the

SPE-down interface to an SPE that is locked standby is never available to the

remote access port, because the standby SPE is isolated from the active SYSAM

circuit pack.

A limited set of commands is available to the SPE-down interface, as follows.

Local Terminal session overridden by remote access

KEYBOARD LOCKED, WAIT FOR SYSAM OR LOGIN PROMPT

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Initialization and Recovery

Page 4-13SPE-Down Command Interface

The following qualifier can be used with the test commands:

Enter

only

the characters which appear in bold type. For instance, to test all

memory boards ten times, enter t ma 10 Entering t results in testing all boards

once. You can abort the execution of a command by pressing ESC 3 times.

Test Commands

After a command is entered, various test result messages are printed on the

terminal, indicating whether each test passes, fails or aborts. If any components

fail, refer to the Maintenance Object documentation that applies. Additional

information for interpreting these results can be found in the ‘‘Troubleshooting a

Table 4-2. SPE-Down Interface Commands

Keyboard Entry Command

?Help

rReboot

sSecondary reboot

ddisplay alarms

t al or tTest all standby SPE circuit packs

t sy Test SYSAM circuit pack

t pr Test Processor circuit pack

t m1 Test Memory circuit pack 1

t m2 Test Memory circuit pack 2

t m3 Test Memory circuit pack 3

t m4 Test Memory circuit pack 4

t ma Test all Memory circuit packs

t du Test DUPINT circuit pack

t ms Test MSSNET circuit pack

t p1 Test PKTINT circuit pack 1

t p2 Test PKTINT circuit pack 2

t p3 Test PKTINT circuit pack 3

t pa Test all PKTINT circuit packs

1 to 99 Number of repetitions (default is 1)

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Initialization and Recovery

Page 4-14SPE-Down Command Interface

Duplicated SPE’’ and ‘‘Testing the Standby SPE’’ sections in Chapter 5,

‘‘Responding to Alarms and Errors’’. Note that the test memory command

performs exhaustive tests and can be very time-consuming.

When testing is complete, the system readies itself for another command and the

prompt appears. If testing does not complete within 20 minutes, the following

message is displayed:

LMM did not finish test in time.

This is a serious error indicating that the processor, bus, and/or LMM are not

working properly. Normally you will see initial test result output within a few

seconds. If not, you can abort the test request by pressing ESC 3 times, and the

command prompt will be returned.

If the SPE-down mode is entered or re-entered as a result of the test request, the

screen displays:

Can’t continue - test aborted.

Again, this is a serious error, but at least the processor is able to handle

SPE-down reporting. Likely fault locations are memory board number 1,

processor board, or processor/memory bus.

Display Alarms Command

The display alarms command asks for the alarms that caused the SPE to go

down. It is valid only in the SPE-down or down-and-locked-standby mode. If d is

entered while the SPE is in one of the down modes, the following header is

displayed:

DISPLAY ALARMS:

Physical

Name

Logical

Name

Board?

Alternate

Name

Alarm

Type

Date

Alarmed

Date

Resolved

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Initialization and Recovery

Page 4-15SPE-Down Command Interface

The header is followed by one and only one of the following lines (except that

more than one Memory circuit pack failure may be displayed):

Note that the display is designed to approximate an alarm display from software

maintenance, but is not populated with certain information, represented by

dashed out fields. Only the first failed component detected is displayed.

In the absence of any other information about the cause of the failure, replace the

indicated component using the procedures described in Replacing SPE Circuit

Packs. After all tests pass, return the standby SPE to service, with procedures

described in the following section on ‘‘Bringing the SPE Back into Service’’.

BOOT_ERROR indicates that the LMM was not able to either load, start, or keep

the SPE running following a reboot request. SPE_SAN indicates that SYSAM

detected enough sanity timeouts to exceed the threshold.

Reboot Commands

After all SPE-down interface tests have passed, an SPE can be brought back up

by using the reboot commands. The reboot command, r starts a reboot using the

boot image loaded on the disk device. The secondary reboot command, s, starts

a reboot using the boot image loaded on the tape device. The latter is useful if

the boot image on the disk is corrupted, the disk device is faulty, or a different

software load is desired. A reboot can be interrupted by pressing ESC 3 times.

As noted earlier, if an SPE is locked in the standby mode, the reboot commands

cannot be entered and will abort.

--- PROCR y ----- MAJOR ----- -----

----- MEM_BD_0 y ----- MAJOR ----- -----

----- MEM_BD_1 y ----- MAJOR ----- -----

----- MEM_BD_2 y ----- MAJOR ----- -----

----- MEM_BD_3 y ----- MAJOR ----- -----

----- MSS_NET y ----- MAJOR ----- -----

----- TAPE y ----- MAJOR ----- -----

----- DISK y ----- MAJOR ----- -----

----- NO_TAPE y ----- MAJOR ----- -----

----- BOOT_ERROR ----- MAJOR ----- -----

----- SPE_SAN ----- MAJOR ----- -----

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Initialization and Recovery

Page 4-16SPE-Down Command Interface

Bringing the SPE Back into Service

!WARNING:

In a system with duplicated SPEs, a spontaneous SPE interchange may

occur if the active SPE is not in good health and either

— an unlocked SPE completes its reboot and handshake is

reestablished

— a locked SPE in which the Standby Maintenance Monitor (SMM) is

running is unlocked

!WARNING:

Use the status spe command to determine the health of the active SPE and

whether an interchange will occur.

Once all tests pass using the SPE-down interface, the SPE should be competent

to return to service. There are however certain problems which will not show up in

testing that may prevent this. Follow the appropriate procedure below to bring

the SPE back up.

Simplex SPE

After the reboot command is entered, a series of diagnostics is run on the SPE.

Results are displayed as they occur, as described in preceding sections. If all

tests pass, the boot image is loaded and control is given to the operating system.

If you cannot get the SPE to reboot after replacing the components that failed

SPE-down interface tests, follow normal escalation procedures.

Duplicated SPE

The physical connection of the terminal to the STANDBY connector, while the

SPE is locked standby with the SPE-Select switches, prevents the Standby

Maintenance Monitor (SMM) from running. Thus, any reboot command to the

standby while in this state will abort. To reboot an SPE that is locked standby and

has a terminal connected to it, simply move the SPE-SELECT switches to the

AUTO position one at a time. This will automatically cause the standby SPE to

reboot and its progress is displayed on the terminal. Moving the switches back to

the locked position will cause the reboot to abort.

To reboot the standby SPE and have it remain locked standby following the

reboot, use the following procedure:

1. Start the reboot by moving the SPE-Select switches one at a time to the

AUTO position.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Initialization and Recovery

Page 4-17SPE-Down Command Interface

2. As soon as initialization diagnostics begin to appear on the screen,

disconnect the MT cable from the STANDBY connector on the control

carrier.

3. Return the SPE-SELECT switches to their previous locked position.

When the standby is back up and cycling, the yellow LED on the Processor

circuit pack will begin flashing. It is then safe to unlock the SPE-Select switches if

they were relocked. At this point, the system should re-establish handshake

communication, turn on memory shadowing (assuming the standby is not busied

out), and perform a refresh of the standby SPE’s memory. These steps can be

monitored by using the status spe command at a terminal connected to the

ACTIVE terminal connector. When these steps have been completed, the

standby SPE should have a “functional” state of health and be fully in service.

If all tests pass, but the SPE does not return to service, there may still be

problems on the standby which escaped detection by SPE-down testing. In this

case, use the following steps, which describe a means of sequentially replacing

circuit packs that are the most likely source of the problem.

1. First determine if memory shadowing is disabling handshake. With the

standby locked, busyout the standby SPE; this prevents shadowing from

turning on.

2. Bring up the standby as described above (unlock, unplug the STANDBY

terminal and relock). If the yellow LED on the Processor fails to flash,

follow normal escalation procedures. After the yellow LED begins flashing,

unlock and monitor the recovery progress by repeatedly entering status

spe on a terminal connected to the

active

SPE. If handshake is not

established after 2 minutes, memory shadowing is not the problem.

Proceed to step 4.

3. Release the standby and follow the progress of the refresh with status

spe. If the refresh succeeds, the system should be fully functional. If the

onset of shadowing or refresh coincides with handshake failure, replace

the following circuit pack one at a time in the order shown and repeat this

procedure from step 1 each time. (Use lock-and-power-down and

DUP-CHL instructions).

a. Standby DUPINT

b. Standby PKT-INT

c. Standby MSSNET

d. Active DUPINT

If the problem persists, follow normal escalation procedures.

4. If handshake has not come up after 2 minutes, replace each of the

following circuit packs one at a time, in the order shown, and repeat this

procedure from step 1 each time:

a. Standby PKT-INT

b. Standby DUPINT

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Initialization and Recovery

Page 4-18SPE-Down Command Interface

c. Standby SYSAM

d. Standby PROCESSOR

e. Standby MSSNET

f. Standby MEMORY number 1

g. Standby MEMORY number 2

If the problem persists, follow normal escalation procedures.

Responding to Alarms and Errors

Page 5-1Safety Precautions

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

5Responding to Alarms and Errors

Safety Precautions

By observing the prescribed safety precautions when working on the system,

you can avoid unnecessary disruption of service and damage to the equipment.

The items on this list should be a regular part of your routine.

!WARNING:

Failure to comply with these procedures can have catastrophic effects on

system service and hardware. Read the explanations following the list to

ensure a complete understanding of these necessary procedures.

■Whenever touching any component inside the cabinet, ground yourself by

means of the wrist strap attached to the cabinet, and avoid sources of

static electricity.

■When logging on with the terminal, be aware that INADS alarm notification

is normally disabled. Log off the terminal when leaving the system.

■Think carefully before moving SPE-SELECT switches. Always set them one

at a time to the letter of the PPN control carrier that is

currently active

(unless a procedure specifically tells you to do otherwise).

■Never “hot plug” an SPE circuit pack, except for the tape and disk drives

on a simplex SPE. Lock and power down the PPN control carrier first.

■Do

not

power down switch node or port carriers to replace a board.

■Handle fiber optic cables with care. Bending, piercing, or cutting the

cable can sever communications between major subsystems.

■When disconnecting fiber optic cables, grasp of both the lightwave

transceiver and the cable connector.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Responding to Alarms and Errors

Page 5-2DEFINITY AUDIX System Power Procedures

■Before powering down a cabinet or carrier that contains DEFINITY AUDIX

circuit packs (TN566), first power down the AUDIX unit to avoid damaging

the AUDIX software. Instructions for powering down this unit are in the

‘‘DEFINITY AUDIX System Power Procedures’’ below, on the circuit pack,

and in DEFINITY AUDIX documentation.

■When you are finished working on a cabinet, replace and secure all

panels and covers to avoid disseminating electromagnetic interference.

DEFINITY AUDIX System Power

Procedures

Manually Power Down AUDIX System

A yellow caution sticker on the system’s power unit notifies technicians to shut

down the DEFINITY AUDIX System prior to powering down the system.

1. Using a pointed object, such as a paper clip or pen (do not use a pencil),

press the Boot/shutdown button. The button is located at the top right

portion of the front panel.

2. Hold the boot/Shutdown button in until the LCD display flashes the

message MSHUT.

3. Release the Boot/Shutdown button.

NOTE:

The DEFINITY AUDIX System takes about five minutes to shut down.

The “heartbeat” indication on the display continues to flash.

Manually Power Up AUDIX System

1. Using a pointed object such as a paper clip or a pen (do not use a pencil),

press the Boot/Shutdown button.

2. Hold the boot/Shutdown button in until the display indicates the message,

BTEST, steady on.

3. Release the Boot/Shutdown button. the DEFINITY AUDIX system takes

approximately 5 minutes to power up.

■The display has the following sequence of steady on messages:

—OSINIT

—OS

—AINIT

—ADX

■The DEFINITY AUDIX System is now powered up. When the system

is in the active state, the display indicates ADX, and the red LED is

off.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Responding to Alarms and Errors

Page 5-3Electrostatic Discharge

NOTE:

When powering up, the DEFINITY ADUXI System automatically

reboots. This sequence may show an MD or MJ ADX alarm in the

display until the system how powered up. When the system has

completed its power up sequence, the display reads: ADX.

Electrostatic Discharge

Whenever a circuit pack is inserted or removed, the grounding wrist strap

attached to the cabinet must be used to avoid damage or disruption from ESD.

Use of the wrist strap is also required whenever touching any components inside

the switch cabinet, including the SPE-SELECT and EMERGENCY TRANSFER

switches. While such actions may not cause a problem in a highly controlled

environment, disruption to the system could result when conditions are not ideal,

(for example, when the air is very dry).

If you

must

proceed when a wrist strap is not available, grab the outside panel of

the cabinet with one hand

before

touching any components, and keep your extra

hand grounded throughout the procedure.

Handle a circuit pack only by the faceplate, latch, or top and bottom edges. Do

not touch board components, leads or connector pins. Keep circuit packs away

from plastic and other synthetic materials such as polyester clothing. Do not set a

circuit pack on a non-conductive surface such as paper. Use the anti-static bag,

if available.

Never hand a circuit pack to another person unless that person is also using a

wrist ground strap.

The body collects potentially damaging amounts of static electricity from many

ordinary activities. The smallest amount of ESD that can be felt is far above that

which can damage a sensitive component or disrupt service!

Figure 5-1 shows the location of the grounding jack.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Responding to Alarms and Errors

Page 5-4Suppress Alarm Origination [y]

Figure 5-1. Multi-Carrier Cabinet ESD Grounding Wrist Strap Jack

Suppress Alarm Origination [y]

When logged in as “craft,” no alarms are reported to INADS. After logging off,

INADS automatically reactivates, and any unresolved alarms are reported to

INADS.

Also, when logged in as “craft,” an automatic logoff of the terminal occurs after

30 minutes of non-use. At that time, any unresolved alarms are reported to

INADS. If you are logged in as “craft” at 2 different terminals, the logoff occurs

when the second terminal remains unused for 30 minutes.

NOTE:

The test inads-link command functions even if INADS Alarm Origination is

overridden.

ESD

JACK

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Responding to Alarms and Errors

Page 5-5Reseating and Replacing Circuit Packs

Reseating and Replacing Circuit Packs

Most repair procedures involve replacing faulted circuit packs. In some cases,

problems are resolved by reseating the existing circuit pack. Reseat a circuit

pack

only

when explicitly instructed to do so by the documented procedures.

Reseating is discouraged since it can put a faulty component back into service

without addressing the cause, resulting in additional and unnecessary

dispatches. After reseating a circuit pack, make sure the problem is really fixed

by thorough testing and observing the component in operation.

When a port board is removed from the backplane, no alarm is logged for about

11 minutes to allow for maintenance activity to proceed. After that, a minor

on-board alarm is logged. If the port board is not administered, no alarm is

logged.

!WARNING:

This procedure can be destructive, resulting in a total or partial service

outage.

!WARNING:

Proceed only after consulting and understanding the applicable service

documentation for the component.

!WARNING:

Observe all Safety Precautions described above.

!WARNING:

If the yellow LED on the circuit pack to be removed is lit, the circuit pack is

active and services using it will be interrupted.

!WARNING:

Follow special procedures for the circuit packs listed below.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Responding to Alarms and Errors

Page 5-6Replacing a BIU or Rectifier

Special Procedures

The following circuit packs require special procedures.

For components of the SPE, see “Replacing SPE Circuit Packs”.

■UN331B Processor (SPE)

■TN1650B Memory (SPE)

■TN1655 Packet Interface (SPE)

■TN1648 SYSAM (SPE)

■UN332 MSSNET (SPE)

■TN1657 Disk (SPE)

■TN1656 Tape (SPE)

■TN768/780 Tone/Clock

■UN330B Duplication Interface

■TN750 Expansion Interface

■TN573 Switch Node Interface

■TN572 Switch Node Clock

■DS1 CONV

Replacing a BIU or Rectifier

To remove a Battery Interface Unit (BIU) or rectifier first attach a grounding strap

from the cabinet to your bare wrist then follow the steps listed below:

1. Unlock the latch pin.

2. Pull down on the locking lever until the BUI or rectifier moves forward and

disconnects from its socket.

3. Pull the BIU or rectifier out just enough to break contact with the

backplane connector. Use steady even force to avoid disturbing the

backplane.

4. Carefully slide the BIU or rectifier out of slot.

To install a BIU or rectifier first attach a grounding strap from the cabinet to your

bare wrist than follow the steps listed below:

1. Insert the back edge of the BIU or rectifier making sure that it is

horizontally aligned. Slide the unit in to the slot until it engages the

backplane. Use extreme care in seating the backplane connectors.

2. Lift the locking lever until the latch pin engages.

3. Verify that the unit is seated correctly by observing the operation of the

LED’s.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Responding to Alarms and Errors

Page 5-7Replacing SPE Circuit Packs

Replacing SPE Circuit Packs

All circuit packs on the processor carrier of the PPN except for the Tone/Clock

board are components of the SPE. In addition to the customary MO

documentation, there are additional diagnostic techniques for these boards

described in the following section,

Troubleshooting a Duplicated SPE

, and in the

section

SPE-down Interface

. Instructions for replacing the Tone/Clock circuit

pack can be found in the TDM-CLK MO documentation.

!WARNING:

DO NOT “HOT PLUG” AN SPE BOARD. Before removing any SPE circuit

pack you must power down the carrier in which it resides, (except in the

case of a tape or disk drive in a simplex SPE). Powering down the

processor carrier is destructive on a simplex system, causing a total service

outage. Be sure you have consulted the appropriate documentation for the

component you are replacing. Be sure you are familiar with the precautions

at the beginning of this chapter.

Simplex SPE

This procedure is destructive, resulting in a total service outage except for lines

administered with Emergency Transfer. The processor

must

be powered down to

avoid hardware damage. Arrange to perform this procedure when a service

outage will have the least impact on the customer.

1. Attach the grounding strap to your wrist.

2. Remove power to the processor carrier, (carrier A), by unplugging the

power cords located on the front of the power units located at

both

ends of

the carrier.

3. Remove or reseat the circuit pack using the procedure described

previously in

Reseating and Replacing Circuit Packs

4. Restore power to the carrier by plugging both power cords back in.

5. Monitor the system reboot by observing the LEDs and G3-MT output.

These indicators are described in

Initialization and Recovery

6. Test the replaced component(s) using the appropriate MO

documentation.

7. If the same problem persists, reinstall the original circuit pack to avoid

confusing further troubleshooting.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Responding to Alarms and Errors

Page 5-8Replacing SPE Circuit Packs

Replacing Circuit Packs on a Duplicated SPE:

Lock-and-Power-Down

By following the lock-and-power-down procedure, components of a duplicated

SPE can usually be replaced with no disruption of service.

!WARNING:

In a system with duplicated SPEs, a spontaneous SPE interchange may

occur if the active SPE is not in good health and either an unlocked SPE

completes its reboot and handshake is reestablished, or a locked SPE in

which the Standby Maintenance Monitor (SMM) is running is unlocked.

!WARNING:

Use the status spe command to determine the health of the active SPE and

whether an interchange will occur.

1. Enter status spe

to verify that the component to be replaced is on the

standby SPE. If it is, go to step 2.

If the component is on the active SPE, initiate a planned SPE interchange

by entering reset system interchange. If the interchange fails, there may

be faults on the standby SPE preventing the interchange. You must either

repair the fault on the standby SPE first, or force an interchange by using

reset system interchange health-override.

!WARNING:

Forcing an interchange may disrupt service. Arrange to do so at a

time suitable for the customer.

2. Enter status port-network 1 to check the health of the PPN Tone/Clocks.

The Tone/Clock in the same carrier as the active SPE should have a

service state of “in.” If not, repair it using “TDM-CLK” before proceeding.

3. Lock the active SPE.

After grounding yourself, move the SPE-SELECT switches on both

DUPINT boards, 1 at a time, to the carrier designation of the active SPE.

For example, if the A carrier SPE is currently active, move the switches to

position “A.”

4. Enter status port-network 1 to verify that the active Tone/Clock is in the

same carrier as the active SPE.

If not, repeat the command until this condition is met. If the active

Tone/Clock has not migrated to the active carrier after 1 minute, there is a

Tone/Clock problem. The Tone/Clock problem must be fixed first to avoid

service disruption. See “TDM-CLK” maintenance object.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Responding to Alarms and Errors

Page 5-9Replacing SPE Circuit Packs

5. Power down the standby processor carrier by:

a. Remove the power plug from the left side of the carrier first.

b. Remove the second power plug from the right side of the carrier.

6. Remove the failed circuit pack and replace it with a new one of the same

type.

7. Power up the standby processor carrier by:

a. Insert the power plug in the right side of the carrier first.

b. After inserting the first power plug in the right insert the second

power plug in the left side of the carrier.

The red and green LEDs will light indicating restoration of power and

testing of the boards. These LEDs will go out as tests pass.

8. This step is optional. Use a terminal and the SPE-down interface to test the

standby SPE as follows.

If a terminal is connected to the STANDBY connector on the back of either

PPN control carrier, the power-up reboot of the standby aborts and the

SPE-Down interface can then be used to enter commands to the LMM

firmware. Use t al, or the SPE-Down interface test command for the

replaced component, to confirm that the problem is fixed. Repair any

failures reported.

When testing is finished, move the SPE-Select switches to the AUTO

position

one at a time

. This unlocks the standby and begin a reboot which

can be monitored from the terminal.

9. Verify that the standby is up.

Regular flashing of the yellow LED on the Processor board indicates that

the standby SPE is up and cycling. If the yellow LED is not flashing after

five minutes, test the standby SPE as described in the above step. Relock

the SPE standby, attach a terminal to the STANDBY connector on the back

of either PPN control carrier and execute the SPE-down interface tests. All

tests must pass before unlocking.

10. If the standby SPE is still locked, unlock it by returning both SPE-Select

switches to the AUTO position

one at a time

11. Enter status spe to confirm that handshake is up. This should occur within

2 minutes. When it is, enter the test long clear command for the replaced

component. If an alarm does not clear, consult the appropriate MO.

12. Verify that the standby SPE is brought into service.

Enter status spe. The standby SPE is fully operational when handshake is

up, shadowing is on, and memory is refreshed. It can take up to 10

minutes after unlocking for the standby to be brought fully into service.

13. If the standby SPE does not fully return to service, consult ‘‘STBY-SPE

(Standby SPE Maintenance)’’.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Responding to Alarms and Errors

Page 5-10Troubleshooting a Duplicated SPE

Troubleshooting a Duplicated SPE

The section on maintenance object ‘‘STBY-SPE (Standby SPE Maintenance)’’

contains procedures for troubleshooting specific problems such as handshake

failure, memory shadowing failure, and poor state of health. The following

procedures describe a method for determining the cause of a spontaneous SPE

interchange and resolving any related problems.

If a spontaneous SPE interchange has occurred, assume that a serious fault has

occurred on the SPE that is currently the standby. The following symptoms

indicate that a spontaneous SPE interchange has taken place:

■A MINOR alarm with error type 103 is logged against STBY-SPE.

■An interchange entry is recorded in the initcauses log.

■The system is put into

recent interchange mode

, which prevents further

SPE interchanges from taking place.

The presence of recent interchange mode is displayed on the status spe

screen. The system is released from this mode, and the minor alarm is cleared,

after 1 hour, or upon the execution of test spe-standby long, regardless of

whether all tests pass.

There are three possible causes of a spontaneous interchange:

■Major hardware failure

■Failed recovery that has been software escalated

■Switching both SPE-SELECT switches to the standby carrier (not a

recommended procedure)

In the last case, the interchange is not fault-driven, and no specific repair action

is required. To determine whether this is the case, enter display initcauses. If

the interchange was initiated by the SPE-SELECT switches, the Cause field will

appear as in the following example.

If the interchange was fault-driven, there are two ways of finding the cause.

1. Using alarm and error logs in conjunction with the timestamp described

above. After a spontaneous SPE interchange has occurred, the Alarm Log

retains a record of any MAJOR ON-BOARD alarm against an SPE

component that took place before the interchange. This record is retained

for three hours and may indicate the cause of the interchange when

testing is not possible or conclusive. Other information in the Error Log

may also be helpful.

2. Testing the standby SPE when the logs do not identify the problem.

Cause Action Escalated Carrier Time

SPE-SELECT switch 1 no 1B 11/27 14:53

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Responding to Alarms and Errors

Page 5-11Troubleshooting a Duplicated SPE

Start by determining the time of the interchange. Then, examine the alarm and

error logs as described in the following section. If that does not identify the

problem, proceed to the next section, which describes a sequence of tests of the

standby SPE.

Determining the Time of a Spontaneous

Interchange

There are 2 ways to tell at what time a spontaneous interchange has taken place:

■STBY-SPE Error 103

This error is logged with a minor alarm whenever a spontaneous

interchange takes place. The time recorded for the

first occurrence

of the

error is the approximate time of interchange. The error is logged against

the carrier of the SPE that was active before the interchange. This should

now be the standby SPE, assuming no further interchanges have taken

place.

■Display initcauses

The display initcauses command displays a record of all system resets.

In the following example, a spontaneous interchange

into

the B carrier

SPE took place at 2:53 P.M. The standby SPE (B) transitioned into active

mode with a WARM restart, (reset level 1).

Cause Action Escalated Carrier Time

Interchange 1 no 1B 11/27 14:53

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Responding to Alarms and Errors

Page 5-12Troubleshooting a Duplicated SPE

Examining the Alarm and Error Logs

The system may have had time to log alarms or errors against the fault the

caused the interchange. Proceed through the steps summarized in the following

flowchart. Examine only major alarms with a timestamp near the time of

interchange, and whose carrier designation is the current standby SPE (the SPE

interchanged out of). Include any resolved alarms meeting this description.

Figure 5-2. Determining the Cause of an SPE Interchange

Use the SYSTEM error table following this

chart to determine which SPE component

is implicated.

This indicates a serious processor/memory

bus problem. Busyout or, preferably, lock

the standby SPE to prevent an

interchange, and escalate the problem.

Consult MO documentation for PKT-INT.

Is there a Major alarm against

the standby SW-CTL?

Consult MO documentation for TAPE.

Consult the MO documentation for the

indicated component.

yes

Replace the standby

MSSNET circuit pack.

yes

Consult CARR-POW in

Chapter 9.

yes

If handshake is down (check status spe),

replace the alarmed standby circuit pack

If handshake is up, execute a

test long clear of the alarmed

component and consult documentation

for that MO in Chapter 9.

Proceed to the next ﬂowchart, Testing

the Standby SPE

Is there a TAPE error 3585 with aux code 408?

Is there a PKT-INT error 100?

Is there an error 150 against any SPE component?

Is there a SYSTEM error 6002, 6003,

6102, or 6103?

Enter display errors and look for unalarmed

errors for SPE components, CARR-POW

and SYSTEM. Is there a SYSTEM

error 6001 or 6101.

Enter display alarms for categories SPE

and environ. Are there any major

alarms against CARR-POW?

Are there major alarms against other

SPE components?

All relevant alarms must be timestamped at or near the time of interchange.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Responding to Alarms and Errors

Page 5-13Troubleshooting a Duplicated SPE

Auxiliary Data for SYSTEM Errors 6002, 6003,

6102, and 6103

The following table shows which components are indicted by the auxiliary error

codes found by using the preceding flowchart. Once you have identified the

faulted component, consult the section for that MO.

AUX Data Implicated Maintenance Object

16384 PROCR

16385 MEM-BD

4137 PKT-INT

16391 SW-CTL

16386 SYSAM

16389 DUPINT

16392 HOST-ADAPTER

16397 TAPE

16398 DISK

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Responding to Alarms and Errors

Page 5-14Troubleshooting a Duplicated SPE

Testing the Standby SPE

The system may not have had time to log errors against the failed component

that caused the spontaneous interchange. If you have progressed through the

preceding flowchart without determining the cause of interchange, test the

standby for faults by proceeding through the following steps.

Figure 5-3. Testing the Standby SPE

Consult MO documentation for SW-CTL.

Enter \f(HBtest spe-standby long\fH and wait

for all tests to execute.

Do all tests except for STBY-SPE test 855 pass?

Busyout the standby SPE and enter \f(HBtest dup long\fH.

Do all DUPINT and DUP-CHL tests pass?

When call service needs allow for a

possible disruption, release the standby

SPE and wait for it to refresh (\f(HBstatus spe\fH).

Enter \f(HBreset system interchange\fH. Did the

planned interchange succeed?

Busyout the standby SPE and enter \f(HBtest dupint long\fH.

Do all tests pass?

Run the long test sequence on the active SW-CTL.

Enter \f(HBtest stored data long\fH.

yes

Have you completed the steps in the

preceding ﬂowchart?

Follow normal esclation procedures.

Enter \f(HBstatus spe\fH. Is the standby SPE

fully refreshed with handshake up? Troubleshoot using MO documentation

for STBY-SPE.

Consult MO documentation for the

component whose test failed.

Consult MO documentation for the

component whose test failed.

Consult MO documentation for

DUPINT or DUP-CHL.

Consult the following discussion of

planned interchange failure.

Consult MO documentation for DUPINT.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Responding to Alarms and Errors

Page 5-15Executing a Planned SPE Interchange

Executing a Planned SPE Interchange

Planned SPE interchanges are initiated on demand by the reset system

interchange command, or automatically by scheduled daily maintenance. The

latter is administered with the system-parameters maintenance screen. A

planned interchange normally has no perceivable effect on service. All active

calls, transient calls, system links and stimuli, and data transmission are

preserved. The SYSAM-RMT port (also called the Remote Access Port) is

dropped, necessitating a re-login. The duration of the interchange is

approximately one minute.

!CAUTION:

Switching the SPE-select switches to the standby carrier causes a

spontaneous interchange, not a planned one. This can disrupt service and

is not a recommended procedure.

Prerequisites

Several conditions must be met to guarantee a non-disruptive interchange. If

these are not met the system will not execute the interchange. All of these

conditions, listed below, are expected to be met during normal operation.

■The SPE must not be locked by the SPE-SELECT switches.

■The standby SPE must be fully in service.

That is, handshake is up, shadowing is on, memory is refreshed, and

standby SPE state-of-health is “functional”. ‘‘STBY-SPE (Standby SPE

Maintenance)’’ describes how to correct a failure of any of these.

■There can be no minor alarms against the standby’s PKT-INT or SYSAM

circuit packs.

■There can be no ongoing disk or tape operations on either active or

standby MSS components.

Wait until all such operations, such as translation saves or backup

restores, are complete before requesting an interchange.

SPE Interchange Failures

If the above conditions are not met, or if any intermediate steps taken by the

system in executing the interchange fail, the interchange is prevented. Usually,

failure of a planned interchange has no effect on service.

If the interchange fails after the packet interface links have migrated, the system

will require a reset level 1 (warm restart) to restore the links. In such a case, no

calls are dropped, and new call service resumes within 5 seconds. However, it is

probable that there is a severe system problem which predates the attempted

interchange.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Responding to Alarms and Errors

Page 5-16Executing a Planned SPE Interchange

If the SPE is locked by means of the SPE-SELECT switches, error 607, auxiliary

data 1153, is logged against SYSTEM. If the switches are not locked and the

interchange fails, an unalarmed error 605 is logged against SYSTEM. The

auxiliary code associated with this error indicates which aspect of the

interchange failed. Table 5-1 explains the meaning of the auxiliary codes and

what corrective action to take.

Table 5-1. SYSTEM Error 605 Planned Interchange Failure

Aux

Data See

Note Explanation

1352 1Standby SOH “non-functional”

1353 1Standby SOH not “functional”

1355 1Handshake Communication with Standby SPE is down

1356 1Memory Shadowing not enabled

1357 1Standby memory not refreshed

1358 2Mass Storage System was in use

1359 3PKT-INT link migration failed

1360 1Interchange failed1

1361 4SW-CTL failure

1369 7Could not suspend G3-MT connectivity1

1370 4Could not freeze active SW-CTL1

1371 5 Internal Error associated with processor interrupts1

1372 6Minor alarm on standby SYSAM or PKT-INT

1395 SPE Duplication not administered

1396 3PKT-INT Link Migration failure in Begin Step1

1397 3PKT-INT Link Migration denied, (peer test in progress)

1398 3PKT-INT Link Migration failure in Completion Step1

1399 3PKT-INT Link Migration failure in Finish Step1

1400 4Could Not Idle SW-CTL dual port RAM1

1401 4Could Not Refresh SW-CTL dual port RAM1

1402 5Internal Error (could not get duplication status)

1403 5 Unable to inhibit Standby Maintenance Monitor

1404 5Failure to determine Standby SPE alarm status

Continued on next page

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Responding to Alarms and Errors

Page 5-17Executing a Planned SPE Interchange

Notes for SYSTEM Error 605 AUX Data:

1. Follow repair instructions in ‘‘STBY-SPE (Standby SPE Maintenance)’’ for

the particular standby SPE problem. After fixing that problem, try the

interchange again.

2. Mass Storage System is in use. Check Disk and Tape LEDs for activity.

Wait until all MSS activity completes, then try the interchange again. If the

problem persists, check for alarms and errors against MSS components

and follow repair procedures in Chapter 9, ‘‘Maintenance Object Repair

Procedures’’.

3. Test the PKT-INT on both carriers with the long test sequence. Follow

procedures for ‘‘PKT-INT (Packet Interface Circuit Pack)’’ in Chapter 9,

‘‘Maintenance Object Repair Procedures’’. Once

all

tests of both PKT-INTs

pass, try the interchange again.

4. Consult SW-CTL service documentation. Test SW-CTL on both carriers

with the long test sequence. Follow repair instructions for any failures.

Once

all

tests of both SW-CTLs pass, try the interchange again.

5. Make sure the standby SPE is refreshed Then try the interchange again.

6. Examine alarm log to determine which of PKT-INT or SYSAM circuit packs

has a minor alarm against it. Consult service documentation of whichever

is alarm to clear

7. Check for errors/alarms against active SPE’s SYSAM. If you find any,

consult SYSAM service documentation. If you find none, and if all tests of

the SYSAM long sequence pass, try the interchange again.

8. Run test duplication-interface long and follow instructions for any test

that does not pass.

1. A WARM restart is required.

1406 3Active SPE’s PKT-INT in held-reset state

1418 8Active Duplication Interface circuit pack is in a bad state

and needs to be reset.

2500 5Internal Software failure1 (sometimes)

Table 5-1. SYSTEM Error 605 Planned Interchange Failure — Continued

Aux

Data See

Note Explanation

Continued on next page

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Responding to Alarms and Errors

Page 5-18Fiber Fault Isolation Procedure

Fiber Fault Isolation Procedure

Use the following procedure to isolate faults on a fiber-link. When troubleshooting

a system with duplicated Port Network Connectivity (PNC), first busyout

pnc-standby before busying out a standby Fiber-Link (FIBER-LK), Expansion

Interface (EXP-INTF), Switch Node Interface (SNI) or DS1 Converter (DS1C). At

the end of this section is a description of the loopback tests run and a pinout of

the cable used to connect the DS1 C to DS1 facilities.

■A busyout of any of these components on a simplex PNC is destructive.

■Be sure to release all busied out components after completing the tests.

Steps:

1. Enter display alarms with category pnc.

Are there any on-board alarms? If so, replace the circuit pack(s).

2. Enter display errors for category pnc.

Check for any of the following errors:

one or more

of the above errors are present go to step 3.

none

of the above errors are present, look for SNI-PEER errors.

■If there is one SNI circuit pack with many different SNI-PEER error

types, replace the indicated SNI circuit pack

■If there are many SNI-PEER errors of the same error type, replace

the indicted SNI circuit pack using the following table.

Maintenance

Object Error

Type

FIBER-LK Any

SNI-BD 513

EXP-INTF 257

769

770

1281

1537

3073

3074

3075

3076

3585

3841

3842

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Responding to Alarms and Errors

Page 5-19Fiber Fault Isolation Procedure

■After replacing an SNI circuit pack, clear alarms by executing test

board UUCSSlong clear for all alarmed EXP-INTF circuit packs.

Wait 5 minutes for any SNI-BD or SNI-PEER alarms to clear. (You

can speed this process with clear firmware counters [a-pnc |

b-pnc] for the PNC that was repaired).

■Exit this procedure.

3. Enter list fiber-link to get the physical location of the fiber-link endpoints.

If a DS1 CONV is administered to the fiber-link (DS1 CONV is “y”), use the

display fiber-link command to get the physical location of the DS1 CONV

circuit packs on the fiber-link.

4. Execute busyout fiber-link FP followed by test fiber-link FP long.

If any tests in the sequence fail

, proceed with step 5.

If all of the tests pass

, clear alarms by executing test board UUCSS long

clear for all alarmed EXP-INTF circuit packs. Wait 5 minutes for any

SNI-BD, SNI-PEER, FIBER-LK, or DS1C-BD alarms to clear. You can

speed this process with clear firmware counters [a-pnc | b-pnc] for the

PNC that was repaired. You are finished with this procedure.

Error Type SNI slot

257 3

513 4

769 5

1025 6

1281 7

1537 8

1793 9

2049 13

2305 14

2561 15

2817 16

3073 17

3329 18

3585 19

3841 20

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Responding to Alarms and Errors

Page 5-20Fiber Fault Isolation Procedure

5. For each endpoint of the fiber-link, follow this flowchart:

Busyout and test board UUCSS long and record all test failures. When

looking at test results, consult the explanations and illustrations of the

tests, which appear at the end of this procedure.

Is Board Not Assigned displayed for an EXP-INTF in an EPN? If yes,

test maintenance

long to release an EXP-INTF that may be held reset by an EPN

Maintenance circuit pack.

If No

Did EXP-INTF test 242 fail? If yes, replace the EXP-INTF circuit pack and

the lightwave transceiver (if present) and go back to step 4. (EXP-INTF

test 242 runs an on-board looparound if no lightwave transceiver is

connected to the EXP-INTF.)

If No

Did SNI test 757 fail? If yes, replace the SNI circuit pack and go back to

step 4 of this procedure.

If No

Did SNI test 756 fail? If yes, replace the SNI circuit pack and the lightwave

transceiver (if present) and go back to step 4.

If No

Did EXP-INTF test 240 fail? If yes, replace the EXP-INTF circuit pack and

go back to step 4.

If No

Did tests 238 (EXP-INTF) or 989 (SNI) fail? If yes, replace the lightwave

transceivers and fiber-optic cable, or metallic cable, and go back to step

4. The faulted component can be further isolated by using the Manual

Loopback Procedure described at the end of this procedure.

NOTE:

If a fiber out of frame condition exists and lightwave transceivers are

used, check that both lightwave transceivers are of the same type,

(9823a or 9823b). If they are not both the same, replace one of the

lightwave transceivers so that they match. (9823A is used for

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Responding to Alarms and Errors

Page 5-21Fiber Fault Isolation Procedure

distances up to 4900 feet (1493 m) and 9823B is used for distances

up to 25,000 feet (7620 m)).

If No

Is a DS1 CONV administered on the fiber-link? If no, follow normal

escalation procedures.

If Yes

Is there an SNI-BD 513 alarmed error (display errors for category pnc)?

If yes, replace cabling between the SNI circuit pack and the DS1C circuit

pack. If the alarm persists, replace the DS1C and the SNI circuit packs.

Go back to step 4.

If No

If the connected circuit pack is an EXP-INTF, did test 238 fail? If yes,

replace cabling between the EXP-INTF circuit pack and the DS1C circuit

pack. If test 238 continues to fail, replace the DS1C and the EXP-INTF

circuit packs.

Go back to step 4.

If No

Busyout and test board UUCSS long for both DS1C circuit packs and

note all test failures and aborts.

Did the test return Board not inserted for the near-end circuit pack

(nearest the SPE), or for the far-end circuit pack in a simplex PNC? If so,

replace the cabling between the DS1C circuit pack and the SNI or

EXP-INTF circuit pack.

Wait 1 minute and retest.

If the board is still not inserted, replace the DS1C circuit pack and the

EXP-INTF or SNI connected to it.

Go back to step 4.

If No

Check to see if any of the CSU devices are looped back. Busyout and

test ds1-facility UUCSS external-loop for each DS1 facility.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Responding to Alarms and Errors

Page 5-22Fiber Fault Isolation Procedure

The tests should fail.

If any test passes, the facility is looped back, and the loopback should be

removed. If the DS1C Complex has only one DS1 facility, this test cannot

be executed at the far-end circuit pack (farthest from the SPE).

Did test 788 pass and test 789 fail? If yes, replace the DS1C and lightwave

transceiver (if present) at the other end of the DS1C complex. (See Figure

5-4 and Figure 5-5.)

Go back to step 4.

If No

Did test 788 fail or abort and test 789 fail or abort? If yes, execute test

ds1-facility UUCSS long command for each administered and equipped

DS1 facility.

If No

Did test 797 fail?

If yes, run the test ds1-facility UUCSS external-loopback command for

each administered and equipped DS1 facility.

This test requires manually altering the external connections of the DS1

facility. Place the loopbacks at as many points as your CSU capabilities

will allow (see Figure 5-5).

■If test 799 fails at LB1, problem is with DS1C #1, CSU #1, or the

connections in between.

■If test 799 passes at LB1 and fails at LB2, the problem is with CSU

#1.

■If test 799 passes at LB1 and at LB2, the problem is with the DS1

facility, CSU #2, connections to CSU #2, or DS1C #2.

SNI/EI Manual Loop Back Procedure

Use this procedure to isolate a fault in the cables or lightwave transceivers of

SNI/EI links. (Do not use this procedure on a connection with a DS1C as an

endpoint.) By performing the loopback at both endpoints and, if applicable, at

the cross-connect field, the failure point can be identified. If both endpoints pass,

but the link remains inactive (with the boards not busied out), the fault should lie

in the cabling in between. If the test passes at a transceiver, but fails at the

cross-connect field, the cable or connectors in between are at fault.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Responding to Alarms and Errors

Page 5-23Fiber Fault Isolation Procedure

A short optical fiber jumper with connectors is required for this procedure. If the

link uses metallic cable, the metallic connector must be removed from the back

of the carrier, and a lightwave transceiver connected in its place.

1. Note the condition of the yellow LED on the circuit pack.

2. Busyout the circuit pack.

3. Disconnect the transmit and receive fiber pair from the lightwave

transceiver on the back of the circuit pack. Note which is the transmit fiber

and which is the receive fiber for proper re-connection at the end of this

procedure.

4. Connect the transmit and receive jacks of the lightwave transceiver with

the jumper cable.

NOTE:

Make sure that the total length of the fiber jumper cable does not

exceed the maximum length recommended for the fiber link

connections between cabinets. Otherwise, test results may be

influenced by violation of connectivity guidelines.

5. At the front of the cabinet, observe the yellow LED on the looped back

circuit pack.

■If the yellow LED flashes once per second, the circuit pack or

transceiver should be replaced.

■If the yellow LED flashes five times per second, the circuit pack or

its lightwave transceiver may need replacement. This condition

may also be due to a faulty system clock on the port network (for an

EI) or the switch node carrier (for an SNI).

■If the yellow LED was flashing before starting this procedure, and it

is now either solid on or solid off, this circuit pack and its lightwave

transceiver are functioning properly.

6. Replace the faulty component(s) and reconnect the original cables in their

correct positions. Be sure to use a lightwave transceiver that matches the

one at the opposite end.

7. Release the circuit pack.

Loopback Tests Run for Fiber Fault Isolation

Procedure

Figure 5-5 shows the loopbacks performed on the SNI circuit pack for test 756

and test 757. Test 756 reports the result of the off-board loopback; test 757

reports the result of the on-board loopback. Test 756 and test 757 can run

individually or as part of the test board UUCSS long command for an SNI circuit

pack.

Test 242 can be run as part of the test board UUCSS long command for an

Expansion Interface circuit pack. Besides testing on-board components, this test

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Responding to Alarms and Errors

Page 5-24Fiber Fault Isolation Procedure

is helpful for isolating problems between a circuit pack and the lightwave

transceiver. The loopback shown in this diagram shows only part what test 242

does. If no lightwave transceiver is connected to the Expansion Interface circuit

pack, an on-board loopback is performed on the Expansion Interface circuit

pack. For more information about test 242, see the ‘‘EXP-INTF (Expansion

Interface Circuit Pack)’’ section in Chapter 9, ‘‘Maintenance Object Repair

Procedures’’.

Figure 5-4. Fiber Fault Isolation Tests

If DS1Cs exist on the fiber link (check with list fiber-link), then additional

DS1CONV loopback tests can be run to further isolate the problem. The

loopback tests are shown in Figure 5-5. For more information about loopback

tests 788 and 789, see the ‘‘DS1 CONV-BD’’ section in Chapter 9, ‘‘Maintenance

Object Repair Procedures’’. For more information about DS1 facility loopback

tests 797 and 799, see the ‘‘DS1-FAC (DS1 Facility)’’ section.

Figure 5-5. DS1 CONV Loopbacks

Tone

Clock

Tone

Detector

Test

#242

ﬁber-optic

cable

TDM BUS back skin

of cabinet

lightwave

transceivers

TN753

Switch

Node

Interface

Test

#757

Test

#756

TN570

Expansion

Interface

back skin

of cabinet

Test #989 (framing)Test #238 (framing)

Tests 788, 780, 797,

and 799 start here:

. . . . .

Test 797 loops at internal

interface for the DS1 facility

Test 789

loops here

Test 788

loops here

lightwave

transceiver

DS1 Facility

CSU 2 DS1C

CSU 1

DS1C

Test 799

LB 1 Test 799

LB 2

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Responding to Alarms and Errors

Page 5-25Fiber Fault Isolation Procedure

Table 5-2 shows the pin assignments for the cable used to connect the TN574

DS1 CONV circuit pack to DS1 facilities.

Table 5-2. DS1 Interface Cable Connectors

Lead Desig.

50-Pin

Connector

15-Pin

Connector

Color Pin Color

Plug 04

Facility D Line In LID 38 W-BL 11 W-BL

Facility D Line In LID* 13 BL-W 03 BL-W

Facility D Line Out LOD 39 W-O 09 W-O

Facility D Line Out LOD* 14 O-W 01 O-W

Plug 03

Facility C Line In LIC 41 W-G 11 W-G

Facility C Line In LIC* 16 G-W 03 G-W

Facility C Line Out LOC 42 W-BR 09 W-BR

Facility C Line Out LOC* 17 BR-W 01 BR-W

Plug 02

Facility B Line In LIB 44 W-S 11 W-S

Facility B Line In LIB* 19 S-W 03 S-W

Facility B Line Out LOB 45 R-BL 09 R-BL

Facility B Line Out LOB* 20 BL-R 01 BL-R

Plug 01

Facility A Line In LIA 47 R-O 11 R-O

Facility A Line In LIA* 22 O-R 03 O-R

Facility A Line Out LOA 48 R-G 09 R-G

Facility A Line Out LOA* 23 G-R 01 G-R

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Responding to Alarms and Errors

Page 5-26Multimedia Call Handling (MMCH)

Multimedia Call Handling (MMCH)

Enhancements

Expansion Services Module

The Expansion Services Module (ESM) provides T.120 data sharing capability on

a MMCH multipoint H.320 video conference. Each conference participant must

have endpoints administered and a personal computer with the H.320 video

application installed. The DEFINITY ECS must have the expansion service

module installed.

Figure 5-6. Typical ESM connections

Figure Notes

!CAUTION:

The TN2207 circuit pack is the only pack allowing connection of an ESM to

the DEFINITY ECS switch.

Troubleshooting

Before troubleshooting any problems associated with the DEFINITY MMCH,

always be sure that the endpoint is operating correctly (audio, video, and data)

by making point-to-point test calls. If possible, make the test calls over the

1. Port B Y-cable connector to a TN787

Multimedia Interface (MMI) circuit pack

2. Port A Y-cable connector to a TN2207 PRI

circuit pack

3. 25-pair Y-cable

4. 356A adapter

5. D8W cord connected to 356A

adapter port 1

6. Expansion Service Module (ESM)

7. Port B on compatible primary rate

interface (PRI) card

cydf012 RPY 100697

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Responding to Alarms and Errors

Page 5-27Multimedia Call Handling (MMCH)

network to test the connectivity and routing of network calls from the endpoint.

This eliminates problems such as disconnected audio or video cables and

network troubles.

64 Kbps Calls Terminate but Far End Receives

56 Kbps Indication

Description

Some 2x64 Kbps conferences on the DEFINITY MMCH do not establish because

of framing, audio, or video problems.

For calls that are routed in the network through a Lucent Technologies/LEC

interface, the originating equipment may launch a 64 Kbps call attempt, and the

far end receives either a 56 Kbps or 64 Kbps indication. If the far end receives a

64 Kbps indication, the call may have used 56 Kbps facilities. If so, the call may

exhibit any of the following conditions:

■No handshaking in one direction or both (call disconnects after timeouts)

■Call connects, but audio or video is corrupted (audio noise or no video)

■Call succeeds without disruption (this is the least likely since one endpoint

must be aware that the call is really 56 Kbps to connect)

If any of the above conditions occur, then 64 Kbps calls from the site are

blocked.

Solution

Administer the conference for connection at 56 Kbps.

Calls Terminate with No Audio

Description

To support endpoints that do not support Multipoint Command Conference

(MCC), the DEFINITY MMCH changes its capability set and initiates a capability

set exchange with the endpoint when the Selected Communications Mode (SCM)

changes. If the endpoint does not follow the SCM audio mode, the MCU may

include the endpoint as a secondary (audio only) endpoint. If the endpoint sends

an unknown or unsupported audio mode, then the TN788B decoder port mutes

the endpoint from the conference. The user may hear the conference but may not

be heard by other parties in the conference.

Solution

1. Use the Status Conference x form and check the Audio Mode field for the

current operating mode of the conference.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Responding to Alarms and Errors

Page 5-28Multimedia Call Handling (MMCH)

2. Another indication of the audio modes is in the “Incoming Mode

Commands from Endpoint and Outgoing Commands from MMI” on page

3 of the Status Conference x Endpoint y form. Check the Audio fields

under the Mode Commands/Communication Modes section of the form.

Some Parties Cannot Be Heard by Others (Audio

Subsetting)

Description

Problems where varying subsets of the conference hear different things may

have problems with the various summing resources/groups that are in use.

Traditionally theses faults are caused by the SPE not cleaning up the

connections properly. Isolation and diagnosis should focus on the VC resources

in use by that conference.

Solution

1. Use the status conference command to list the VC resources in use by

this conference. Try a hot replacement of any VC boards in use, which

refreshes the VC translations and move all of the audio connections to

different VC ports.

2. If the problem still exists, try dropping the conference and then bringing

the conference back up again. Not only does this refresh VC translations,

but uses different timeslots as well.

3. If the problem still exists, suspect a hardware problem. If practical, wait for

the DEFINITY MMCH to be idle (no active conferences), and then check

the circuit packs for active (yellow) LEDs. If any of these are unexpected,

such as on a VC board, try replacing the board and then bringing the

conference up again.

Calls Terminate with No Video

Description

Generally, loss of video can be divided into 2 types. The first occurs when the

DEFINITY MMCH switches to the endpoint, but nobody sees them. The receivers

see either “black” video or a frozen image of the previous speaker depending on

the codec of the manufacturer. The type occurs when the DEFINITY MMCH does

not switch to an endpoint.

Solution

In the first type described above, wiring problems, power to the camera, or video

encoder circuit pack problems in the codec are typical causes.

In the second type, no video from an endpoint typically occurs because it is not a

valid video source. This can be checked by looking at page 1 of the Status

Conference x Endpoint y Vid form under the Capability section. In this section, a

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Responding to Alarms and Errors

Page 5-29Multimedia Call Handling (MMCH)

“y” or “c” suggests that the endpoint has video. An “e” means ept has not

declared any video capability in cap set, “n” is audio only, and “blank” means

audio add-on.

Also check page 1 of the Status Conference x Endpoint y Vs form for indication of

the video state for the endpoint values.

Calls Terminate Correctly but Are Unstable

A number of conditions will lead to some or all endpoints having stability

problems during the course of a conference. A lack of stability from an endpoint

is noticeable by a lack of a video switching while the party is the only talker or

excessive disconnects from that endpoint.

Synchronization

Generally, the most common problem is a mismatch in synchronization sources

between the endpoint and the DEFINITY MMCH. This typically causes low-level

(Px64) handshake problems that can trigger the endpoint/MMCH to disconnect

the call. The MCCH’s timers are set to sufficiently high values so that, normally,

the endpoint will timeout and disconnect first. If installed in a customer network, it

is a good idea to perform an audit of the path synchronization is being supplied.

If there are different clock sources between endpoints and the DEFINITY MMCH,

some problems are sure to occur. The severity of these problems can range from

a handshake failure every few seconds to one per day. Depending on the type of

endpoint, this can cause the endpoint to disconnect or just freeze video until the

main problem is resolved.

Specifically, PictureTel System 4000 endpoints seem to be the most sensitive to

instability. The Lucent Technologies Vistium also disconnects fairly infrequently.

Last, the CLI Rembrandt II VP freezes video and waits for framing to be

recovered.

Network Configuration Concerns with Synchronization

When auditing a network for synchronization, avoid unnecessary hops. Thus, a

switch providing star-configuration synchronization is preferred over a

daisy-chain configuration. Additionally, if there are DEFINITY PBXs that have

EPNs, synchronization should be provided to sub nodes from the same port

network through which the PBX receives its synchronization. Passing

synchronization through the PBX Expansion Interface adds an unnecessary hop

to the path and creates another potential point of failure.

Expansion Interface Duplication

If a customer’s network uses PBX EPNs with duplicated Expansion Interfaces,

scheduled switching of the Expansion Interface links should be disabled on the

PBX via change system-parameters maintenance. When scheduled

maintenance runs and switches the links, there is a brief corruption of the data

path. If endpoints have active calls when the switch occurs, this corruption of the

data path causes Px64 handshake problems, which lead to the endpoints losing

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Responding to Alarms and Errors

Page 5-30Multimedia Call Handling (MMCH)

video source status, and sometimes disconnecting as described above.

Disabling the EI switching is in the customer’s best interest to prevent the

disruption of the Px64 data stream. The customer will get the same level of alarm

indications and maintenance on the EI links, regardless of the status of

scheduled switching.

PRI D-Channel Backup

A somewhat unlikely source of call stability problems occur where the

translations for PRI D-channel Backup between two non-MCU switches were

incorrect. As an example, on switch A, DS1 1A10 was designated as the primary

source, and on switch B, the corresponding DS1 was designated as the

secondary source. When scheduled maintenance was run on the switch that had

an active standby D-channel, an audit disconnected some calls using the link.

The problem was corrected when the the D-channel primary/secondary

assignments matched.

Processor Duplication on the PBX

Do not enable the PI link switch on scheduled maintenance. This can cause link

stability problems on the Accunet Bandwidth Controller (ABC).

Voice-Activated Switching Problems

Voice-activated switching on the DEFINITY MMCH does not follow the loudest

talker. The MMCH queues all speaking parties and selects a new video

broadcaster (the second-oldest speaking party) when the oldest speaking party

has stopped talking. The new broadcaster will see the last speaker as its video.

The system can also “learn” about the noise coming from an endpoint to help

prevent false switches, adapting both to noise level and repetitive sounds such

as a fan. This adaptation occurs over approximately 10 seconds.

No Switching, Full Motion Video

If a room is excessively noisy, the DEFINITY MMCH may receive sufficient audio

signal to conclude that there is a speaker present. Use the Status Conference x

form to determine if the MMCH thinks an endpoint is talking. The MMCH sets the

Ts field to t for each endpoint if there is voice energy detected. This endpoint

may have to mute when nobody at the site is speaking to allow the conference to

proceed normally. Remind the customer that it may be necessary to mute if a

side conversation is going on in the background, just as one would do in an

audio conference. If the system does not switch broadcasters even after the

current broadcaster has muted, check the conference administration using the

display conference X command to ensure that the conference is in

voice-activated mode. Also verify that parties who were speaking are valid video

sources as described in the “Calls Terminate with No Video” section above.

The See-Me feature (MCV) can also cause VAS to “lock-up.” An endpoint can

activate MCV to force their site to become the broadcaster. If they do not disable

the feature when finished, the system remains in this mode indefinitely.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Responding to Alarms and Errors

Page 5-31Multimedia Call Handling (MMCH)

Beginning with Release 3.0, the status conference X command shows that MCV

is in effect by displaying av in the Video Status (Vs) column. Page 3 of the Status

Conference X Endpoint Y form also has a Broadcaster field that indicates MCV

is in effect with (SEE-ME) as the broadcaster. The same scenario can occur in a

CHAIR or UCC-controlled conference with a designated broadcaster. In this

situation the CHAIR/UCC has not released the designated broadcaster and

returned to VAS mode. If there is a UCC-designated broadcaster, status

conference X indicates a Video Status of u. Also, for UCC rollcall the return

video may appear to be stuck. Check the Video Status for an “R,” indicating

rollcall.

If none of the examples above appears to be the cause, and if the room was

quiet, all speakers are valid video sources, the conference is voice-activated,

and the speaker can be heard, then escalate the problem.

Video Never Switches to a Particular Party

Description

Verify that the endpoint is a valid video source as described in the “Calls

Terminate with No Video” section above. If it is, then the audio from the endpoint

may not have sufficient voice signal for the hardware to determine the parties at

the endpoint are speaking. Check the Talk field on page three of the Status

Conference X Endpoint Y form to see if the talking bit is y. Next, check the

audio by standing adjacent to the microphone and speaking at a normal level.

Solution

If the audio is not muffled:

1. Use the status conference command to determine which port on the

TN788B (VC board) is connected to this endpoint.

2. Check the VC (TN788B) board using the test board xxyy long command.

3. Drop the call.

4. Find another available port, then:

a. Busyout the port to which the endpoint was connected.

b. Make another call to the same conference. If the problem corrects

itself, then the previous port may be bad. If there are other VC

boards with sufficient available ports to replace calls on the current

VC, then pull the board that has the bad endpoint on it (the status

conference command displays the encoder port associated with

the call). The system will automatically reestablish the VC

connections without dropping the call. If this fixes the problem, then

replace the board, as it has at least one bad port. Reseating the

board may temporarily fix the problem due to the hard reset done to

the board.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Responding to Alarms and Errors

Page 5-32Multimedia Call Handling (MMCH)

Audio Echo

Echo in conference calls, particularly those with large delay characteristics, is

totally disruptive. When Voice Activated Switching is taken into account, the

effects are disastrous. Various arrangements of the microphone(s) and room

speaker(s) may be needed.

For some Lucent Technologies Vistium endpoints, if an external speaker is

attached or was attached when the system was last rebooted, this endpoint will

cause audio echo throughout the conference. First, isolate the offending

endpoint by asking each endpoint to mute, one at a time, until the echo

disappears.

If the input from an endpoint is located too close to the speakers of an endpoint,

then acoustic echo is created. The microphone must be moved away from the

speakers.

Normally, if any microphone in the room is moved relative to the speakers, that

site will cause echo until the echo canceller in the codec retrains itself, some will

require a manual reset. If a PictureTel keypad is configured with external

microphones connected to the keypad, then the internal microphone and

external microphone(s) “sing” to each other if the “ext mic” bat switch is set to

“int mic” on the back of the keypad. In this configuration, VAS locked on that site,

and the acoustic “singing” was inaudible.

Rate Adaptation

Because of a lack of a clear explanation in standards, sometimes endpoints do

not work well with each other and the DEFINITY MMCH. The MMCH will only

allow a conference to downgrade from 64kbps to 56 kbps operation on

conferences that have the Rate Adaptation flag set to y.

When a downgrade does occur, information on the Status Conference form

indicates the success or failure of the 64kbps-endpoints that are participants to

properly rate adapt to 56kbps. As a general indication that the conference has

rate adapted, the Conference Transfer Rate and Effective Transfer

Rate fields show initial and current transfer rates, respectively. For each 64-kbps

endpoint the column that indicates Rate Adapt shows an n if the endpoint did

not follow the procedures as specified by the H.221. If an endpoint shows y, it

did successfully rate adapt. If an endpoint shows c, it joined the conference at

56kbps.

Once the conference rate adapts, the endpoints that do not properly follow suit,

will become audio-only endpoints. A conference will not rate adapt from 56 kbps

back to 64 kbps until all endpoints disconnect from the conference and it idles.

The PictureTel 1000 Release 1.1C, PictureTel 6.01 software, and the Vistium 2.0

software successfully rate adapt with the MCU. External rate adaptation

techniques used by VTEL and CLI are known to cause problems with the

endpoint when used with this feature.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Responding to Alarms and Errors

Page 5-33Troubleshooting ISDN-PRI Problems

Endpoint or I-MUX in Loopback Mode

Some endpoints have a loopback enable feature. This makes DEFINITY MMCH

data loopback at the MMCH when a connection is in progress. The loopback can

be enabled prior to or during a connection.

The MMCH does not detect the loop and continues to VAS. In most scenarios,

the switch occurs, but within a few seconds, the broadcaster’s return video

becomes its own image. Once the broadcaster stops speaking, the system

“false” switches to an apparently random port that was not speaking.

Troubleshooting ISDN-PRI Problems

The following flow chart defines a layered approach when troubleshooting

ISDN-PRI problems. Since a problem at a lower layer affects upper layers, layers

are investigated from low to high. In the flowchart, the DS1 facility is layer 1, the

ISDN-PRI D-channel is layer 2, and the ISDN trunks are layer 3. Transient

problems are diagnosed on Page 2 of the flowchart. For problems with PRI

endpoints (wideband), see the following section.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Responding to Alarms and Errors

Page 5-34Troubleshooting ISDN-PRI Problems

Figure 5-7. Troubleshooting ISDN-PRI (Page 1 of 2)

ARE THERE

ALARMS OR ERRORS

AGAINST UDS1-BD OR

DETERMINE PRESENT STATUS

OF DS-1 FACILITYVIA UDS1-BD

OR DS1-BD MO SECTION.

ARE THERE

ALARMS OR

ERRORS AGAINST

ISDN-LINK OR

ISDN-SGR

IF MULITPLE ALARMS EXIST,

INVESTIGATE IN FOLLOWING

ORDER:

ISDN-LINK

ISDN-SGR

FOLLOW REPAIR PROCEDURE

FOR APPROPRIATE MO

ARE THERE

ALARMS OR

ERRORS AGAINST

FOLLOW REPAIR

PROCEDURE FOR ISDN-TRK

PAGE

YES

START

YES

END

DS1-BD

ISDN-TRK

FOLLOW REPAIR PROCEDURES

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Responding to Alarms and Errors

Page 5-35Troubleshooting ISDN-PRI Problems

Figure 5-8. Troubleshooting ISDN-PRI (Page 2 of 2)

PAGE

YES

END

FROM

ARE

THERE

TRANSIENT

PROBLEMS MAKING

ISDN-PRI

ARE

THERE BIT

ERRORS OVER

HAS A

SYNCHRONIZATION

SOURCE BEEN

SYSTEM SWITCHING

IF PROBLEMS

STILL EXIST,

THEN ESCALATE

COMPARE INDICATED

FACILITY TO RECORD

OF PREVIOUS PROBLEMS

ARE BIT

ERRORS OCCURRING

MORE FREQUENTLY

THAN PREVIOUS

RECORD INDICATED

FACILITY AND, IF THIS

CONTINUES TO OCCUR,

CONTACT FACILITY OR

EXTERNAL EQUIPMENT

PROVIDER. THEN ESCALATE

THE TI FACILITY?

UNSTABLE?

AWAY FROM IT?

YES

SEE UDS1-BD OR DS1-BD

MO FOR REPAIR PROCEDURES

IF SYNC PROBLEM IS DUE

TO SLIPS. OTHERWISE,

FOLLOW REPAIR

PERFORM AN IN-DEPTH

ANALYSIS OF T1

FACILITY INCLUDING:

TRANSMISSION FACILITY,

EXTERNAL EQUIPMENT

(DACS, CSUs, ETC.)

AND ANY OTHER

NOISE-PRODUCING

EQUIPMENT.

REFER TO AT&T PRACTICE

#855-351-101 ISSUE 8,

JANUARY 1987. THIS

DESCRIBES T1 CABLING TO

CSUs, ETC, IN DETAIL

YES

END

CALLS

SEE SYNC MO

HISTORY

PROCEDURES FOR

SYNC MO

USE LIST

MEASUREMENTS

COMMAND

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Responding to Alarms and Errors

Page 5-36Troubleshooting ISDN-PRI Endpoints (Wideband)

Troubleshooting ISDN-PRI Endpoints

(Wideband)

The following flow chart defines a layered approach when troubleshooting PRI

endpoint problems. Because problems at lower layers affect upper layers, layers

are investigated from low to high. In this procedure, the DS1 facility is layer 1, the

TN1655 Packet Interface is layer 2, and the PRI endpoint ports are layer 3.

The troubleshooting procedure described here is limited to diagnosing faults

between the switch and the line-side PRI terminal adapter or ISDN-PRI endpoint

equipment. Problems encountered on the network-side of a wideband

connection or problems with end-to-end equipment compatibility are beyond the

scope of this section.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Responding to Alarms and Errors

Page 5-37Troubleshooting ISDN-PRI Endpoints (Wideband)

START

↓

Are there alarms or errors against any

of the following maintenance objects:

UDS1-BD PKT-INT SYS-LINK

ISDN-LNK ISDN-SGR PE-BCHL

YES

→

Resolve those alarms or errors in the order

listed at left by following procedures for the

appropriate maintenance object in Chapter

↓ NO

Check out the status of the endpoint

equipment or Terminal Adaptor. Do

this at the endpoint, not at the G3-MT

on the switch. Does the adaptor or

endpoint indicate problems?

YES

→Follow repair procedures recommended by

the provider of the Terminal Adapter or

endpoint equipment.

↓ NO

Check administration at the endpoint

and on the switch (for example, port

boundary width). Are they

inconsistent?

YES

→Correct the administration so that both ends

match.

↓ NO

Does every call fail or are the failures

transient?

↓ Transient Failures

Always

Fails

→

Check the health of the application

equipment (for example, the video codec)

and that of the DEFINITY network. If constant

failures persist, follow normal escalation

procedures.

Use list measurements ds1 to check

for bit errors over the DS1 interface

between the switch and the terminal

adapter or endpoint equipment.

↓ No bit errors

Bit

Errors

→

Perform an in-depth analysis of the DS1

interface including premises distribution

wiring, endpoint equipment, and any other

possible source of noise. If the problem

cannot be isolated, follow normal escalation

procedures.

Check for alarms and errors against

SYNC. Has a synchronization source

been unstable? Has the system

switched synch sources?

YES

→Follow procedures described in SYNC in

Chapter 9.

↓ NO

Follow normal escalation

procedures.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Responding to Alarms and Errors

Page 5-38Troubleshooting ISDN-BRI/ASAI Problems

Troubleshooting ISDN-BRI/ASAI

Problems

Troubleshooting ISDN-BRI/ASAI problems can be a complex and involved

procedure. The reason for this is that ISDN-BRI devices communicate with the

SPE over the Packet Bus, as opposed to the TDM Bus. Therefore, it is possible

for failures of other Packet Bus-related system components to cause problems

with ISDN-BRI devices. Figure 5-9 shows the connectivity of the Packet Bus as it

applies to ISDN-BRI signaling.

Figure 5-9. ISDN-BRI/Packet Bus Connectivity

Signaling Links

Testing/

Reconﬁg

Signaling

Links

EPN

Duplicated

PNC

Only

Packet Bus

BRI-PT ABRI-PT

ASAI-ADJ

0 1

ABRI-PT

Duplicated

PNC

Only

Packet Bus

Signaling

Links

BRI-PT

5Testing/

Reconﬁg

PPN

ASAI-ADJ

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Responding to Alarms and Errors

Page 5-39Troubleshooting ISDN-BRI/ASAI Problems

The flowchart in Figure 5-10 describes the steps that should be taken to isolate

and resolve ISDN-BRI problems. The order in which you should examine the

maintenance objects is determined by looking at how wide-spread the failure is.

For example, since all ISDN-BRI devices communicate with the TN1655 Packet

Interface circuit pack, this MO should be examined early in the sequence. On the

other hand, a failure of a TN570 circuit pack may cause ISDN-BRI failure in an

EPN, but could not be the cause of a failure in the PPN.

NOTE:

If the flowchart query ‘‘Is the problem affecting MOs on multiple BRI-BD

circuit packs?’’ is reached, and the port network in question has only one

ISDN-BRI circuit pack, then assume that the answer is ‘‘Yes’’ and follow the

repair procedure for PKT-BUS.

When directed by the flow chart to refer to the Maintenance documentation for a

specific MO, keep in mind that the repair procedure for that MO may refer you to

another MO’s repair procedure. The flowchart tries to coordinate these activities

so that a logical flow is maintained if the ISDN-BRI problems are not resolved with

the first set of repair procedures.

These following status commands may also be useful when diagnosing

ISDN-BRI problems:

■status port-network

■status packet-interface

■status bri-port

■status station

■status data-module

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Responding to Alarms and Errors

Page 5-40Troubleshooting ISDN-BRI/ASAI Problems

Figure 5-10. Troubleshooting ISDN-BRI Problems (Page 1 of 2)

START

ARE THERE

ALARMS OR

ERRORS AGAINST

PKT-BUS

YES

IS THIS A

CRITICAL RELIABILITY

SYSTEM?

ARE THERE

ALARMS OR

ERRORS AGAINST

M/T-PKT

YES

IS THE

PROBLEM

ISOLATED TO

ARE THERE

ALARMS OR ERRORS

AGAINST EXP-INTF*

THE PPN

PAGE

IS THE

ISDN-BRI

PROBLEM

RESOLVED

END

ARE THERE

ALARMS OR

ERRORS AGAINST

PKT-INT

IS THE

ISDN-BRI

PROBLEM

RESOLVED

YES

(DUPLICATED PNC)

YES

PAGE

FOLLOW THE

REPAIR

PROCEDURE

FOR PKT-INT

FOLLOW THE

REPAIR

PROCEDURE

FOLLOW THE

REPAIR

PROCEDURE

FOR M/T-PKT

YES

END

YES

FOR EXP-INTF

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Responding to Alarms and Errors

Page 5-41Troubleshooting ISDN-BRI/ASAI Problems

Figure 5-11. Troubleshooting ISDN-BRI Problems (Page 2 of 2)

PAGE

YES

END

FROM

IS THE

PROBLEM AFFECTING

MOs ON MULTIPLE

BRI-BD CIRCUIT

IS THE

PROBLEM AFFECTING

MULTIPLE MOs ON

THE SAME BRI-BD

CIRCUIT

FOLLOW THE REPAIR

PROCEDURE FOR BRI-PORT,

BRI-DAT, ABRI-PORT, BRI-SET,

OR ASAI-ADJ, AS APPROPRIATE

THE ISDN-BRI

PROBLEM

RESOLVED

FOLLOW THE

REPAIR

PROCEDURE

FOR BRI-BD

YES

FOLLOW THE

REPAIR

PROCEDURE

FOR PKT-BUS

PAGE

FROM

* THESE MOs WOULD BE BRI-PORT,

ABRI-PORT, BRI-DAT,

BRI-SET, OR ASAI-ADJ

PACKS *

ESCALATE

THE

PROBLEM

YES

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Responding to Alarms and Errors

Page 5-42Troubleshooting ISDN-PRI Test Call Problems

Troubleshooting ISDN-PRI Test Call

Problems

An ISDN-PRI test call is placed across an ISDN-PRI user-network interface to a

previously designated number in order to test ISDN capabilities of the switch, the

trunk and the far end. An ISDN-PRI test call is also a maintenance procedure

concerned with the identification and verification ISDN-PRI user-network

interface problems. The ISDN-PRI test call can access ISDN-PRI trunks only.

An ISDN-PRI test call can be placed only if the circuit translates to an ISDN-PRI

trunk. An ISDN-PRI test call can be originated via either the

synchronous

or the

asynchronous

method. Each method is described below.

NOTE:

Before attempting to make an ISDN-PRI test call to the public network (that

is, the network is the far-end), make sure that test call service is provisioned

by the network. The user must subscribe to Test Type 108 service and have

the correct far-end test call number administered on the trunk group form

for the call to be allowed.

Synchronous Method

One command is used in this method to start, stop and query an ISDN-PRI test

call. In the synchronous method, an outgoing ISDN-PRI test call may be part of

one of the following

long

test sequences entered at the terminal:

■test trunk grp/mbr long [repeat #]

■test port UUCSSpp long [repeat #]

■test board UUCSS long [repeat #]

The long qualifier must be entered in the above commands in order for the ISDN

test call to run. The repeat number (#) can be any number from 1 through 99

(default = 1).

The following information is displayed in response to the above commands:

■Port: The port address (UUCSSpp) is the port network number, carrier

designation, slot, and circuit of the maintenance object under test.

■Maintenance Name: The type of maintenance object tested.

■Test Number: The actual test that was run.

■Test Results: Indicates whether the test passes, fails, or aborts.

■Error Code: Additional information about the results of the test (See the

ISDN-TRK section of Chapter 9 for details.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Responding to Alarms and Errors

Page 5-43Troubleshooting ISDN-PRI Test Call Problems

Asynchronous Method

The asynchronous method requires a Maintenance/Test circuit pack to be

present in the system. In this method, 4 commands are used to start, stop, query,

and list an outgoing ISDN-PRI test call:

Before placing an outgoing ISDN-PRI test call, verify that the Feature Access

Code has been administered on the System Features Form, and that the Far End

Test Line Number and TestCall Bearer Capability Class (BCC) have been

administered on the Trunk Group Administration Form. Furthermore, if the

ISDN-PRI trunk is of the cbc (call by call) service type, then the Testcall Service

field on Trunk Group Administration Form must have been administered also.

To initiate an outgoing ISDN-PRI test call with the asynchronous method, issue

the start command listed above, which enables you to specify a specific the

trunk on which to originate the ISDN-PRI test call. An optional qualifier can be

used that specifies in minutes (1 to 120) the duration of the test call. If no duration

is specified, the default is either 8.4 or 9.6 seconds.

Screen 5-1 shows a typical response to the test isdn-testcall command:

Screen 5-1. Test ISDN-TestCall Response

The displayed fields have the following meanings:

Start: test isdn-testcall grp/mbr[minutes]

Stop: clear isdn-testcall grp/mbr

List: list isdn-testcall

Query: status isdn-testcall <grp>/<mbr>

Port The port address (UUCSSpp) is the port network number, carrier

designation, slot, and circuit of the maintenance object under test.

Maint. Name The type of maintenance object tested.

Test Number The actual test that was run.

Test

Results Indicates whether the test passes, fails, or aborts.

Error Code Additional information about the results of the test (See the ISDN-TRK

section in Chapter 9 for details).

test isdn-testcall

Port Maintenance Name Test Number Test Result Error Code

1B1501 ISDN-TRK 258 PASS

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Responding to Alarms and Errors

Page 5-44Troubleshooting the Outgoing ISDN-Testcall Command

The functions of the clear, list, and status commands associated with the ISDN

Testcall are summarized below.

clear isdn-testcall: enables you to cancel an in-progress ISDN-PRI test call and

allow another test call to start.

list isdn-testcall: enables you to list all the ISDN-PRI trunks in use for an

ISDN-PRI test call in the system.

status isdn-testcall: enables you to check on the progress of an outgoing test

call. When an outgoing ISDN-PRI test call completes in a specific port network,

another ISDN-PRI trunk from the same port network is available for testing

(regardless of whether the status information has been displayed).

Troubleshooting the Outgoing

ISDN-Testcall Command

If the TestCall BCC field appears on the Trunk Group Administration Form, make

sure the TestCall BCC field indicates the correct BCC for the service provisioned

on the ISDN-PRI trunk. The TestCall BCC values are defined as follows:

If the ISDN-PRI trunk is of type cbc make sure the TestCall Service field on the

Trunk Group Administration Form indicates the correct service so that a network

facility message can be sent across the ISDN-PRI network.

If the outgoing ISDN-PRI test call keeps aborting, make sure that the far-end

device can handle DCP Mode 0 or DCP Mode 1.

NOTE:

Before attempting to make an ISDN-PRI test call to the public network (that

is, the network is the far-end), make sure that test call service is provisioned

by the network. The user must subscribe to Test Type 108 service and have

the correct far-end test call number administered on the trunk group form

for the call to be allowed.

0Voice

1Digital Communications Protocol Mode 1

2Mode 2 Asynchronous

3Mode 3 Circuit

4Digital Communications Protocol Mode 0 (that is

usually the default).

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Responding to Alarms and Errors

Page 5-45Packet Bus Fault Isolation and Repair

Packet Bus Fault Isolation and Repair

The following procedures provide a means of isolating and correcting faults on

both the packet bus and the various maintenance objects that use the packet

bus. The packet bus is shared by all circuit packs that communicate on it, and a

fault on one of those can disrupt communications over the packet bus.

Furthermore, a circuit pack that does not use the packet bus can also cause

service disruptions by impinging on the backplane or otherwise modifying the

configuration of the bus. (this is discussed in more detail later). For these

reasons, isolating the cause of packet bus failure can be complicated. This

discussion provides a flowchart and descriptions of the tools and procedures

used to isolate and correct packet bus faults.

This discussion is organized into the following sections which provide

background information and troubleshooting procedures. The packet bus Fault

Isolation Flowchart is intended to be the normal starting point for isolating and

resolving packet bus problems. Before using it you should familiarize yourself

with packet bus maintenance by reading the introductory sections.

■‘‘Remote Maintenance versus On-Site Maintenance’’discusses the

strategy and the requirements for performing remote maintenance and

on-site maintenance for the packet bus.

■‘‘Tools for Packet Bus Fault Isolation and Correction’’ discusses the tools

that are needed to isolate and correct packet bus faults.

■‘‘What is the Packet Bus?’’ describes the packet bus, its use in G3r, and

the types of faults that can occur on the packet bus. A diagram shows the

physical and logical connections between circuit packs connected to the

packet bus.

■‘‘Circuit Packs That Use the Packet Bus’’ describes the various circuit

packs, ports, and endpoints that use the packet bus. The section

discusses how these maintenance objects interact, how a failure of one

maintenance object can affect another, and failure symptoms of these

maintenance objects.

■‘‘Maintenance of the Packet Bus’’ describes the strategy of maintenance

software for packet bus. Similarities and differences between the packet

bus and the TDM Bus are discussed. An overview of the Fault Isolation

and Correction Procedures is also presented.

■‘‘The Maintenance/Test Circuit Pack (TN771)’’ discusses the use of the

Maintenance/Test circuit pack in both packet bus fault isolation and other

switch maintenance. The standalone mode of the Maintenance/Test circuit

pack, which is used to perform on-site packet bus fault isolation and

correction, is discussed in detail.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Responding to Alarms and Errors

Page 5-46Packet Bus Fault Isolation and Repair

■‘‘Packet Bus Fault Isolation Flowchart’’ is the starting point for the

troubleshooting process. It is used to determine if a failure of service is

caused by the packet bus itself or by another maintenance object on the

packet bus.

■‘‘Correcting Packet Bus Faults’’ presents the procedures required to

correct either a problem with the packet bus itself or one that is caused by

a circuit pack connected to the Packet Bus.

Remote Maintenance versus On-Site

Maintenance

Most packet bus fault isolation and repair procedures require a technician to be

on-site. This is because a packet bus failures are caused by a hardware failure of

either the packet bus itself or a circuit pack that is connected to it. Initial

diagnoses can be made via use of the

packet bus Fault Isolation Flowchart

, but

the Maintenance/Test Standalone Mode Procedure and the packet bus Fault

Correction Procedure require that a technician be on-site. These procedures are

presented with this requirement in mind.

The flowchart refers to the repair procedures in Chapter 9, ‘‘Maintenance Object

Repair Procedures’’ for various maintenance objects. When a decision point is

reached, a remotely located technician can refer to the appropriate section and

attempt to resolve any fault conditions. Some procedures require on-site repair

action. Keep in mind that failure of a maintenance object appearing early in the

flowchart can cause alarms with maintenance objects that appear later in the

flowchart. Multiple dispatches can be prevented by remotely checking

subsequent stages on the flowchart and preparing the on-site technician for

replacement of several components if necessary.

The Maintenance/Test packet bus port described below provides status

information that is accessed with the status port-network P command and the

PKT-BUS test sequence. The Maintenance/Test circuit pack may or may not be

present at a customer site, depending on the configuration of the switch. If a

Maintenance/Test circuit pack is not present, one must be taken to the site for

diagnosing packet bus problems.

In a system with duplicated SPEs, an SPE interchange may resolve the packet

bus problem. This operation can be executed remotely, and is discussed in

Packet Bus Fault Correction Procedures

below.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Responding to Alarms and Errors

Page 5-47Packet Bus Fault Isolation and Repair

Tools for Packet Bus Fault Isolation and

Correction

The following tools may be required on-site to perform packet bus fault isolation

and correction.

■TN771D Maintenance/Test circuit pack for use in standalone mode, and

the connectors and cables necessary to install it (see the

Maintenance/Test Circuit Pack

section).

■A replacement for the TN771D Maintenance/Test circuit pack in the

system may be needed. See the

A Special Precaution Concerning the

TN771D

section.

■A backplane pin-replacement kit may be required (see

Packet Bus Fault

Correction

) If the kit is not available, replacement of a carrier may be

required.

What is the Packet Bus?

The packet bus is a set of 24 leads in the backplane of each Port Network.

Twenty of these leads are data leads, three are control leads, and one lead is a

spare. This distinction is important only for understanding why some circuit

packs are able to detect only certain faults; the distinction does not affect fault

isolation and repair. Each Port Network has its own packet bus and there is one

packet bus maintenance object (PKT-BUS) in each port network. The packet bus

is not duplicated as is the TDM Bus. There are however several spare leads on

the packet bus and, in Critical Reliability systems (duplicated PNC), these spare

leads are used to recover from some failures on the packet bus.

The packet bus carries various types of information:

■Signaling and data traffic destined for other port-networks and/or Center

Stage Switches. The TN570 Expansion Interface circuit pack provides

packet bus access for these connections.

■ISDN-BRI signaling information for ISDN-BRI stations, data modules and

ASAI adjunct connections. The TN556 ISDN-BRI circuit pack provides

packet bus access for these connections.

■X.25 signaling information and data traffic to support system adjunct

applications. The TN577 Packet Gateway circuit pack provides packet

bus access for these connections.

■ISDN-PRI signaling information carried in the D-channels of ISDN-PRI

facilities connected to the switch. The TN464F Universal DS1 circuit pack

provides packet bus access for these connections.

■System Port traffic to support various input/output devices such as dial-up

modems and printers, as well as system adjunct applications. The TN553

Packet Data circuit pack provides packet bus access for these

connections.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Responding to Alarms and Errors

Page 5-48Packet Bus Fault Isolation and Repair

The SPE interface to the packet bus is the TN1655 Packet Interface circuit pack.

When SPEs are duplicated, there is one TN1655 in each SPE. The TN771D

Maintenance/Test Circuit Pack (discussed in detail later) provides packet bus

maintenance testing and reconfiguration capabilities.

Packet Bus Faults

Two types of packet bus faults occur:

Shorts are far more common than opens, since they can be caused by incorrect

insertion of a circuit pack. It is possible for a circuit pack to be the cause of a

packet bus fault but still operate trouble-free itself. For example, the insertion of a

TDM-only circuit pack such as a TN754 Digital Line could bend the packet bus

pins on the backplane, but remain unaffected since it does not communicate

over the packet bus.

Packet bus faults do not necessarily cause service interruptions, but shorts on it

usually do. Depending on what leads are defective, the system may be able to

recover and continue to communicate. While this allows uninterrupted service, it

makes isolating the fault difficult. The Maintenance/Test circuit pack provides the

capability to detect, and, in some cases, correct packet bus faults.

Packet Bus Connectivity

Various circuit packs communicate on the packet bus (see the next section). For

more details, refer to Chapter 9, ‘‘Maintenance Object Repair Procedures’’ for the

following circuit packs:

■TN1655 Packet Interface: PKT-INTF

■TN570 Expansion Interface: EXP-INTF

■TN556 ISDN-BRI: BRI-BD, BRI-PORT, ABRI-PORT, BRI-SET, BRI-DAT,

ASAI-ADJ

■TN577 Packet Gateway: PGATE-BD, PGATE-PT

■TN553 Packet Data: PDATA-BD, PDATA-PT

■TN464F Universal DS1: UDS1-BD, ISDN-LNK

Shorts A short occurs when different leads on the packet bus become

electrically connected to each other. This can occur due to failures of

circuit packs, cables between carriers, TDM/LAN terminators, or

bent pins on the backplane. A fault occurring during normal

operation is usually caused by a circuit pack. A fault that occurs

while moving circuit packs or otherwise modifying the switch is

usually due to bent pins on the backplane.

Opens An open occurs when there is a break on the packet bus such that

the electrical path to the termination resistors is interrupted. Usually,

this break is caused by a failed TDM/LAN cable or terminator. A less

likely possibility is a failure in the backplane of a carrier.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Responding to Alarms and Errors

Page 5-49Packet Bus Fault Isolation and Repair

■TN771D Maintenance/Test: M/T-BD, M/T-DIG, M/T-PKT

Circuit Packs That Use the Packet Bus

This section describes the circuit packs that use the packet bus and the effects

of circuit pack and bus failures on each other.

Seven circuit packs can use the packet bus: The maintenance objects pertaining

to each circuit pack, (described further in Chapter 9), are listed in brackets.

■TN1655 Packet Interface [PKT-INTF] provides the SPE interface to the

packet bus (as the UN332 MSSNET does to the TDM Bus). All traffic on

the packet bus passes through the Packet Interface. The Packet Interface

can detect some control lead failures and many data lead failures via

parity errors on received data.

■TN570 Expansion Interface [EXP-INTF] connects the Port Networks

(PNs) in the system. (Only TN570s can be used in Release 5r). All Packet

traffic between PNs passes through a pair of TN570s (one in each port

network). The Expansion Interface can detect some control lead failures,

and many data lead failures via parity errors on received data.

■TN556, TN2198, and TN2208 ISDN-BRI circuit packs [BRI-BD,

BRI-PORT, ABRI-PORT, BRI-SET, BRI-DAT, ASAI-ADJ] carries signaling

information for ISDN-BRI station sets and data modules, as well as

signaling information and ASAI messages between the SPE and an ASAI

adjunct. The ISDN-BRI circuit pack has the same fault detection

capabilities as the TN570 Expansion Interface.

■TN577 Packet Gateway circuit pack [PGATE-BD, PGATE-PT] provides

X.25 connectivity to support external system adjuncts such as Audix®

and DCS. The packet bus carries both signaling and customer traffic. The

Packet Gateway circuit pack has the same fault detection capabilities as

the TN570 Expansion Interface.

■TN553 Packet Data circuit pack [PDATA-BD, PDATA-PT] connects via a

backplane cable to a TN726B Data Line circuit pack in an adjacent carrier

slot. Together, the two circuit packs perform a protocol conversion from

mode 3 packet bus traffic originating in the SPE to mode 2 TDM Bus traffic

destined for external system devices and adjuncts. This connectivity is

referred to as a

System Port

. System Ports support devices and adjuncts

such as the System Printer, the PMS Journal Printer, the PMS Wakeup Log

Printer, data terminals, remote administration terminals, and equipment to

support the Call Detail Recording (CDR) feature. System Ports are also

used for saving and restoring System Announcements. The packet bus

carries both signaling and data for the Packet Data circuit pack. The

Packet Data circuit pack has the same fault detection capabilities as the

TN570 Expansion Interface.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Responding to Alarms and Errors

Page 5-50Packet Bus Fault Isolation and Repair

■TN464F Universal DS1 circuit pack [UDS1-BD, ISDN-LNK] supports

ISDN-PRI communications over an attached DS1 facility. It transports of

D-channel signaling information over the packet bus, and B-channel data

over the TDM bus. The Universal DS1 circuit pack has the same fault

detection capabilities as the TN570 Expansion Interface.

■TN771D Maintenance/Test circuit pack [M/T-BD, M/T-DIG, M/T-PKT,

M/T-ANL] is the workhorse of packet bus maintenance. This circuit pack

can detect all packet bus failures for the Port Network in which it resides.

In Critical Reliability systems (duplicated PNC), this circuit pack enables

the reconfiguring of the packet bus around a small number of failed leads.

The TN771D circuit pack provides a standalone mode (one that does not

involve communication with the SPE), for inspecting the packet bus for

faults. Standalone mode is a critical tool for troubleshooting packet bus

faults.

NOTE:

All Maintenance/Test circuit packs must be of vintage TN771D or

later. This circuit pack is also used for ISDN-PRI trunk testing

(M/T-DIG) and ATMS trunk testing (M/T-ANL).

Effects of Circuit Pack Failures on the Packet Bus

Certain failures of any of the above circuit packs can disrupt traffic on the packet

bus Some failures cause packet bus failures with corresponding alarms, while

others cause service outages without alarming the packet bus, (although the

failed circuit pack should be alarmed).

Packet bus circuit pack failures affect the bus in the following ways:

■TN1655 Packet Interface. A failure of the Packet Interface typically

causes all Packet traffic in the system to fail. As a result,

— Expansion Port Networks and Center Stage Switches are disabled.

— ISDN-BRI sets are not able to make or receive calls.

— Communication with ASAI adjuncts fail

— X.25 communications with external adjuncts fail.

— System Ports are disabled.

— ISDN-PRI D-channel signaling is disabled.

If the failure is on the packet bus interface, the packet bus may be

alarmed as well.

In a system with duplicated SPEs, there is one TN1655 Packet Interface in

each SPE. If a Packet Interface failure in the active SPE causes a packet

bus disruption, an SPE interchange may restore service. In other cases,

replacement of the circuit pack may be required before service is

restored.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Responding to Alarms and Errors

Page 5-51Packet Bus Fault Isolation and Repair

■TN570 Expansion Interface. A failure of the Expansion Interface typically

causes all packet traffic in the connected EPN or Center Stage Switch to

fail. If the failure is on the packet bus interface, the packet bus may be

alarmed as well.

If an active Expansion Interface failure causes a packet bus disruption in a

Critical Reliability system (duplicated PNC), a PNC Interchange may

restore service. In other cases, replacement of the circuit pack may be

required before service is restored.

■TN556 ISDN-BRI Circuit Pack. A failure of the ISDN-BRI circuit pack

typically causes some or all ISDN-BRI sets and data modules and/or an

ASAI adjunct connected to the circuit pack to stop functioning. If the

failure is on the circuit pack’s packet bus interface, the packet bus may be

alarmed.

■TN577 Packet Gateway Circuit Pack. A failure of the Packet Gateway

circuit pack disrupts communications with the adjunct (for example,

Audix, DCS) connected to the far end of the X.25 link. If the failure is on the

circuit pack’s packet bus interface, the packet bus may be alarmed.

■TN553 Packet Data Circuit Pack. A failure of the Packet Data circuit pack

disrupts System Port traffic. If the failure is on the circuit pack’s packet bus

interface, the packet bus may also be alarmed. Applications that use

System Ports include:

— Saving and restoring announcements

— Call Detail Recording (CDR)

— Journal Printer for the Property Management System (PMS)

— Wakeup Log Printer for the Property Management System (PMS)

—System Printer

— Data Terminals

— Remote administration terminals

■TN464F Universal DS1 Circuit Pack. A failure of the Universal DS1

Circuit Pack disrupts ISDN-PRI signaling traffic carried on the D-channel.

The loss of that signaling may impact the pack’s 23 B-channels. If the

D-channel supports Non Facility Associated Signaling (NFAS), the

B-channels of up to 20 other DS1 circuit packs may also be affected. In

cases where all 24 channels of the circuit pack are B-channels, packet

bus related failures may not affect the B-channels, since only D-channel

signaling is carried on the packet bus. If the failure is on the circuit pack’s

packet bus interface, the packet bus may be alarmed as well.

■TN771D Maintenance/Test. A failure of the Maintenance/Test may cause

an incorrect indication of a packet bus failure or the inability to detect such

a failure. If the failure is on the packet bus interface, the packet bus may

be alarmed as well.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Responding to Alarms and Errors

Page 5-52Packet Bus Fault Isolation and Repair

Failure of any circuit pack’s bus interface may alarm the packet bus due to

shorting of the packet bus leads. This typically disrupts

all

packet bus traffic in

the affected PN. A failure of the packet bus in the PPN affects packet traffic in the

EPNs as well. Some packet bus failures do not affect all endpoints, so a packet

bus failure cannot be ruled out just because some packet service is still

available.

A circuit pack can fail in a manner such that it transmits bad data on the packet

bus. If the Packet Interface so fails, all Packet traffic is disrupted. Such a failure

on an Expansion Interface may disrupt all Packet traffic in that port network. If an

ISDN-BRI circuit pack fails such that it transmits bad data, all devices connected

to the circuit pack fail to function. This failure may also disrupt the entire packet

bus whenever the circuit pack tries to transmit data. Such a disruption may be

indicated by packet bus alarms that occur and go away, intermittent failures of

other packet circuit packs, and/or interference with other connected endpoints.

These failures are difficult to isolate because of their intermittent nature. In most

cases, the failed circuit pack is alarmed, and all connected endpoints on the

circuit pack are out of service until the circuit pack is replaced. These symptoms

help in isolating the fault.

Maintenance of the Packet Bus

The following topics are covered in this section:

■‘‘Packet Bus and TDM Bus: a Comparison’’

■‘‘Packet Bus Maintenance Software’’

■‘‘Fault Correction Procedures: Overview’’

Packet Bus and TDM Bus: a Comparison

The packet and TDM busses have several similarities and differences. There are

two physical TDM buses in each PN. One of the buses can fail without affecting

the other, but half of the call-carrying capacity is lost. There is

one

packet bus in

each PN. A failure of that bus can disrupt all packet traffic in that PN.

In critical reliability systems, the Maintenance/Test circuit pack provides packet

bus reconfiguration capabilities. This allows the packet bus to remain in service

with up to 3 lead failures. There is no corresponding facility on the TDM Bus.

Instead, the second physical TDM Bus continues to carry traffic until repairs are

completed.

System response varies according by type of bus failure and whether or not the

failure occurs in the PPN or an EPN. In an EPN, a catastrophic TDM Bus failure

(one that affects both TDM Buses) disables

all

traffic in the PN. A catastrophic

packet bus failure affects only packet traffic, so that TDM traffic is unaffected,

while all ISDN-BRI, ASAI, X.25, and ISDN-PRI signaling traffic is disrupted. The

significance of this distinction depends on the customer’s applications. A

customer whose primary application requires ASAI would consider the switch to

be out of service, while a customer with a large number of Digital/Analog/Hybrid

sets and a small number of ISDN-BRI sets would probably not consider the

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Responding to Alarms and Errors

Page 5-53Packet Bus Fault Isolation and Repair

packet bus failure a catastrophic problem. The only way an EPN packet bus

failure can affect TDM traffic is via possible impact on system response time in a

large switch due to running of ISDN-BRI endpoint maintenance. This should

rarely happen because the packet bus maintenance software is able to prevent

this for most faults (see the next section).

If packet bus failure occurs in the PPN, the impact is much more widespread.

Because the PPN packet bus carries the signaling and control links for all EPNs,

PPN packet bus failure effectively removes all the EPNs from service, including

both TDM and packet busses. Packet bus traffic in the PPN is also disrupted.

!CAUTION:

Packet bus fault correction and fault isolation often involve circuit pack

removal, which is destructive to service. Minimize time devoted to

destructive procedures by the use of non-destructive ones where possible.

Packet Bus Maintenance Software

Packet bus maintenance software involves the usual set of maintenance object

error conditions, tests, and alarms. These are described in “PKT-BUS” in Chapter

9. Because a packet bus failure can cause all BRI/ASAI endpoints in the affected

Port Network, and all their associated ports and circuit packs, to report failures,

special care must be taken to ensure that the flood of error messages does not

overload the system and interfere with TDM Bus traffic.

When such a failure

occurs

, circuit pack maintenance is affected in the following manner:

■In-line errors for the following MOs which indicate possible packet bus

failures are logged but

not acted upon:

BRI-BD, PGATE-BD, PDATA-BD,

UDS1-BD.

■In-line errors for the following MOs which indicate possible packet bus

failures are

neither logged nor acted upon:

BRI-PORT, ABRI-PORT,

PGATE-PT, PDATA-PT, ISDN-LNK.

■All in-line errors for the following MOs are

neither logged nor acted upon:

BRI-SET, BRI-DAT, ASAI-ADJ.

■Circuit pack and port in-line errors that are not related to the packet bus,

or that indicate a circuit pack failure, are acted upon in the normal fashion.

■Periodic and scheduled background maintenance is not affected.

■Foreground maintenance (for example, commands executed from the

terminal) is not affected.

These interactions allow normal non-packet system traffic to continue unaffected,

and they reduce the number of entries into the Error/Alarm Logs. If the packet

bus failure is caused by a failed circuit pack, errors against the circuit pack

should appear in the Error/Alarm Logs as an aid for fault isolation. The above

strategy is implemented when:

■In-line errors indicate a possible packet bus failure reported by two or

more Packet circuit packs.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Responding to Alarms and Errors

Page 5-54Packet Bus Fault Isolation and Repair

■A packet bus Uncorrectable report is sent from the Maintenance/Test

packet bus port (M/T-PKT).

When such a failure occurs, a PKT-BUS error is logged. Refer to the PKT-BUS

section in Chapter 9 for more detailed information.

Fault Correction Procedures: Overview

This section gives an overview of the procedures used to isolate the cause of and

correct packet bus faults. Details are presented in following sections.

1. Procedure 1 attempts to determine if a circuit pack that interfaces to the

packet bus is the cause of the packet bus problem. This involves

examination of the Error and Alarm logs followed by the usual repair

actions.

2. If the packet bus problem persists, remove port circuit packs (those in

purple slots) to look for circuit packs that have failed and/or damaged the

packet bus pins.

3. If the packet bus problem persists, perform the same procedure for

control complex circuit packs.

4. If the problem persists, or if the packet bus faults are known to have open

leads, replace bus terminators and cables. If this does not resolve the

problem, reconfigure the carrier connectivity of the port network to attempt

to isolate a faulty carrier.

The Maintenance/Test Circuit Pack (TN771)

The TN771 Maintenance/Test circuit pack provides the following functions:

■Analog Trunk (ATMS) Testing

■Digital Port Loopback Testing

■ISDN-PRI Trunk Testing

■Packet Bus Testing

■Packet Bus Reconfiguration (Critical Reliability systems only)

The PPN always contains a TN771D. Critical Reliability systems have a TN771D

in each EPN. A TN771D is optional in EPNs of other configurations. The ISDN-PRI

Trunk Testing functions are discussed in the ‘‘ISDN-PLK (ISDN-PRI Signaling

Link Port)’’ section in Chapter 9, ‘‘Maintenance Object Repair Procedures’’.

The Digital Port Testing functions are discussed in the ‘‘DIG-LINE (Digital Line)’’,

"DAT-LINE (Data Line Port)", ‘‘PDMODULE (Processor Data Module) TDMODULE

(Trunk Data Module)’’, ‘‘TDMODULE (Trunk Data Module)’’, ‘‘PGATE-PT (Packet

Gateway Port)’’, ‘‘PDATA-PT (Packet Data Line Port)’’, and ‘‘MODEM-PT (Modem

Pool Port)’’, sections in Chapter 9, ‘‘Maintenance Object Repair Procedures’’.

The Analog Trunk Testing functions are discussed in the ‘‘TIE-TRK (Analog Tie

Trunk)’’, ‘‘DID-TRK (Direct Inward Dial Trunk)’’, ‘‘CO-TRK (Analog CO Trunk)’’,

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Responding to Alarms and Errors

Page 5-55Packet Bus Fault Isolation and Repair

and ‘‘AUX-TRK (Auxiliary Trunk)’’, sections in Chapter 9, ‘‘Maintenance Object

Repair Procedures’’.

NOTE:

All Maintenance/Test circuit packs must be of TN771D vintage or later.

TN771D Packet Functions

The Maintenance/Test packet bus port (M/T-PKT) provides the packet bus

testing and reconfiguration capabilities. When the port is in service, it

continuously monitors the packet bus for faults and fault recoveries, and reports

results to PKT-BUS maintenance.

The yellow LED on the TN771D Maintenance/Test circuit pack provides a visual

indication of the state of the packet bus:

NOTE:

It takes 5 to 10 seconds for the LED to respond to a change in the state of

the packet bus.

During normal switch operation, the Maintenance/Test provides visual feedback

of the packet bus state. When in standalone mode (see the next section), these

visual indications are still present, but the packet bus is never reconfigured. The

yellow LED either blinks or is off.

Flashing Flashing of the yellow LED once per second indicates that there

are too many faults for the Maintenance/Test packet bus port to

recover by swapping leads.

The packet bus may be unusable

If the failures detected are open lead failures, the packet bus

may still be operating.

On steady The Maintenance/Test packet bus port has swapped leads on

the packet bus to correct a fault.

The packet bus is still

operating

. Or, one of the other ports on the Maintenance/Test

circuit pack is in use.

NOTE:

First busy out the Maintenance/Test circuit pack ports

used for other than packet bus testing before using the

Maintenance/Test circuit pack to help resolve packet bus

faults. This is done by entering busyout port UUCSS01,

busyout portUUCSSl02, and busyout port UUCSS03. Be

sure to release these ports when the process is

completed.

Off There is no packet bus fault present.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Responding to Alarms and Errors

Page 5-56Packet Bus Fault Isolation and Repair

TN771D in Standalone Mode

In TN771D standalone mode, a terminal is connected to the Maintenance/Test

circuit pack with an Amphenol connector on the back of the cabinet. This setup

allows direct inspection of the packet bus and identifies shorted or open leads.

This mode does not use the usual MT Maintenance User Interface and is thus

available even if switch is not in service. When in standalone mode, the TN771D

does not reconfigure the packet bus.

Required Hardware

■TN771D: Standard or High Reliability systems may not have a TN771D in

each EPN. (Use list configuration to determine if this is so.) When this is

the case, one must be taken to the site. See the following section, ‘‘Special

Precaution Concerning the TN771D’’.

■Terminal or PC with terminal-emulation software: The EIA-232 (RS-232)

port should be configured at 1200 baud, no parity, 8 data bits, and one

stop bit. This is

not

the same configuration as for the G3-MT. If a terminal

configured as a G3-MT is used, change the SPEED field from 9600 to

1200 on the terminal’s options setup menu. (This menu is accessed on

most terminals by pressing the CTRL and F1 keys together. On the 513

BCT, press SHIFT/F5 followed by TERMINAL SET UP). Remember to

restore the original settings before returning the G3-MT to service.

■355A EIA-232 Adapter (COMCODE 105 012 637).

■258B Six-Port Male Amphenol Adapter (COMCODE 103 923 025). A 258A

Adapter and an extension cable can also be used.

■D8W 8-wire modular cable of an appropriate length to connect the 258A

on the back of the cabinet to the 355A adapter. The relevant COMCODE is

determined by the length of the cable, as follows:

— 103 786 786 (7 feet)(2.1 m)

— 103 786 802 (14 feet)(4.3 m)

— 103 786 828 (25 feet)(7.6 m)

— 103 866 109 (50 feet)(15.2 m)

Slot Selection for Standalone Mode

When selecting a carrier slot to use for standalone mode in a port network that

does not already contain a TN771D, keep the following points in mind:

■A port circuit slot (indicated by a purple label) should be used. The

service slot (slot 0)

cannot

be used for standalone mode, although a

TN771D may normally be installed there.

■-5 volt power supply must be available in the carrier. (Refer to

‘‘CARR-POW’’ in Chapter 9, ‘‘Maintenance Object Repair Procedures’’ for

a description of carrier power supply units.)

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Responding to Alarms and Errors

Page 5-57Packet Bus Fault Isolation and Repair

■A slot in the A carrier is preferable for EPNs if the above conditions are

met.

Entering and Exiting Standalone Mode

When in standalone mode, the red LED on the TN771D is lit This is normal and

serves as a reminder to remove the TN771 from standalone mode.

!CAUTION:

The TN771D in standalone must be the only TN771D in the port network. If

a TN771D is already in the port network, place that TN771D in standalone

mode. Do not insert a second TN771D. Otherwise, the system is not able to

detect the extra circuit pack and will behave unpredictably.

!CAUTION:

If the TN771D packet bus port has reconfigured the packet bus in a Critical

Reliability system (indicated by error type 2049 against PKT-BUS), placing

the Maintenance/Test in standalone mode causes a loss of service to the

packet bus. In this case, this procedure disrupts service.

For port networks with a TN771D already installed:

1. Ensure that Alarm Origination is suppressed either at login or via change

system-parameters maintenance.

2. Attach the 258A 6-Port Male Amphenol Adapter to the Amphenol

connector on the back of the carrier corresponding to the TN771D’s slot.

Connect one end of a D8W 8-wire modular cable to port 1 of the 258A.

Connect the other end of the cable to a 355A EIA-232 Adapter. Plug the

EIA-232 Adapter into the terminal to be used, and turn the terminal on.

3. Reseat the TN771D circuit pack.

NOTE:

On a Critical Reliability system, this causes a MINOR OFF-BOARD

alarm to be raised against PKT-BUS. This alarm is not resolved until

the TN771D’s packet bus port (M/T-PKT) is returned to service. To

ensure that PKT-BUS alarms have been cleared, it may be

necessary to restore the TN771D to normal mode.

For port networks without a TN771D installed:

1. Attach the 258A 6-Port Male Amphenol Adapter to the Amphenol

connector on the back of the carrier corresponding to the slot into which

the TN771D is to be inserted. Connect one end of a D8W 8-wire modular

cable to port 1 of the 258A. Connect the other end of the cable to a 355A

EIA-232 Adapter. Plug the EIA-232 Adapter into the terminal to be used,

and turn the terminal on.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Responding to Alarms and Errors

Page 5-58Packet Bus Fault Isolation and Repair

2. Insert the TN771D circuit pack into the slot. The system will not recognize

the presence of the circuit pack.

If the standalone mode is entered successfully, the following is displayed on the

connected terminal:

!CAUTION:

If the above display does not appear, check the wiring between the

terminal and the TN771D, and the terminal parameters settings. If these are

correct, the TN771D may be defective. In such a case, use the following

procedures to exit standalone mode and then test the Maintenance/Test

circuit pack. Refer to M/T-BD and M/T-PKT in

Chapter 9, ‘‘Maintenance

Object Repair Procedures’’

. If the TN771D fails while in standalone mode,

the message

TN771 circuit pack failed

is displayed, and no further

input is accepted on the terminal. The circuit pack must be replaced.

To exit standalone mode:

1. Remove the 258A Adapter from the Amphenol connector.

2. If the TN771D was installed for this procedure, remove it. Otherwise,

reseat the TN771D.

3. If change system-parameters maintenance was used to disable alarm

origination, re-enable it now.

Using Standalone Mode in Packet Bus Fault

Isolation and Correction

When the TN771D is in standalone mode, three commands are available:

ds Displays the current state of the packet bus leads.

dsa Toggles auto-report mode on and off. In auto-report mode, the

state of the packet bus leads are displayed and the terminal

beeps whenever a change occurs.

? Displays the available commands.

TN771 STANDALONE MODE

(Type “?” at the prompt for help)

Command:

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Responding to Alarms and Errors

Page 5-59Packet Bus Fault Isolation and Repair

Below is an example of a standalone mode display. The symbols above the line

represent specific leads on the backplane. The bottom line indicates the

following:

NOTE:

This information is available only from the standalone mode. It is not

available from the MT or a remote login.

Figure 5-12 shows the location of the packet bus leads for a given slot as seen

from the front and back of the carrier.

OOpen lead

S Shorted lead

blank No fault

L L L L L L L L L L H H H H H H H H H H S S S L

P 0 1 2 3 4 5 6 7 8 P 0 1 2 3 4 5 6 7 8 S F B F

_______________________________________________

S S O

Command:

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Responding to Alarms and Errors

Page 5-60Packet Bus Fault Isolation and Repair

Figure 5-12. Packet Bus Leads on the Backplane

. . . .

Front View

. . . .

Backplane

Separation GND

GND

SS CLK

+5v

GND

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Responding to Alarms and Errors

Page 5-61Packet Bus Fault Isolation and Repair

Figure 5-13. Packet Bus Leads on the Backplane

+5v

GND

SS CLK

GND

+5v

+5v +5v

+5v

. . . .

GND

. . . .

Back View

. . . .

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Responding to Alarms and Errors

Page 5-62Packet Bus Fault Isolation and Repair

Special Precaution Concerning the TN771D

A TN771D Maintenance/Test circuit pack must be taken to the customer site if:

■The Maintenance/Test packet bus port indicates that a Packet Bus fault is

present by logging a Major or Minor alarm against PKT-BUS. A Major

alarm is indicated in the error log by Error Type 513; a Minor alarm is

indicated by Error Type 2049.

■Test #572 of the PKT-BUS test sequence is the only test that fails.

This precaution is taken because certain failures of the Maintenance/Test circuit

pack can appear as packet bus failures. To ensure that the problem is indeed

with the packet bus, proceed through the following steps:

1. If the TN771D Maintenance/Test circuit pack is replaced during this

process, enter the test pkt P long command to determine if the packet

bus faults have been resolved. If there are still packet bus problems,

correct them by using the procedures in the sections that follow.

2. If the Maintenance/Test circuit pack was

not

replaced, enter test pkt P.

Record the results (PASS/FAIL/ABORT) and error codes for Test #572.

3. Enter status port-network P. Record the information listed for PKT-BUS.

4. Busyout the Maintenance/Test circuit pack with busyout board UUCSS.

5. Replace the Maintenance/Test circuit pack with the new circuit pack.

6. Release the Maintenance/Test circuit pack with release board UUCSS.

7. Enter the test pkt P and status port-network P commands as described

in Steps 2 and 3.

8. If the data matches the previously recorded data, a packet bus problem

exists, and the original TN771D Maintenance/Test circuit pack is not

defective. Reinsert the original TN771D, and correct the packet bus

problem by using the procedures in the sections that follow.

9. If the data does

not

match the previously recorded data, the original

TN771D circuit pack is defective. If there are still indications of packet bus

problems, correct them by using the procedures in the following sections.

Packet Bus Fault Isolation Flowchart

The flowchart below shows the steps to be taken for isolating and resolving

packet bus problems. The order in which the maintenance objects should be

examined can be determined by assessing how wide-spread the failure is. For

example, since all ISDN-BRI devices communicate with the TN1655 Packet

Interface circuit pack, this MO should be examined early in the sequence. On the

other hand, a failure of a TN570 circuit pack in an EPN may cause ISDN-BRI

failure in the EPN, but not in the PPN.

Whenever the flowchart refers to MO documentation keep in mind that the repair

procedure for that MO may in turn refer to another MO’s repair procedure. The

flowchart tries to coordinate these procedures so that a logical flow is maintained

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Responding to Alarms and Errors

Page 5-63Packet Bus Fault Isolation and Repair

if the packet bus problems are not resolved via the first set of repair procedures.

However, a packet bus failure can lead to a somewhat haphazard referencing of

various MO procedures that may result in taking steps that are repetitive or

unnecessary. If this occurs, return to the flowchart at the step that follows the

reference to Chapter 9, ‘‘Maintenance Object Repair Procedures’’, and continue

from there. The following status commands can also help diagnose packet bus

problems, especially when logged in remotely.

status port-network P status packet-interface

status pnc status bri-port

status station status data-module

status link status pms-link

status sp-link status cdr-link

status journal-link

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Responding to Alarms and Errors

Page 5-64Packet Bus Fault Isolation and Repair

Figure 5-14. Troubleshooting Packet Bus Problems (Page 1 of 2)

Boldface letters in the flowchart refer to paragraphs in the explanatory section

that follows.

YES

page

Are there

alarms or errors

TDM-CLK?

Is only

asinglePN

affected?

Are there

alarms or errors

against

PKT-INTF?

Are there

alarms or errors

against

EXP-INTF?

Are the

packet bus

problems

resolved?

Are the

packet bus

problems

resolved?

Are the

packet bus

problems

resolved?

Is packet

bus use

enabled?

Refer to

"maintenance related

system parameters

form" in chapter 5

Follow the repair

procedure for

TDM-CLK

Follow the repair

procedure for

PKT-INTF

Follow the repair

procedure for

EXP-INTF

Check each

port network

(PPN first)

START

END

fcdfpbp1 RPY 101397

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Responding to Alarms and Errors

Page 5-65Packet Bus Fault Isolation and Repair

Figure 5-15. Troubleshooting Packet Bus Problems (Page 2 of 2)

Boldface letters in the flowchart refer to paragraphs in the explanatory section

that follows.

Flowchart Notes

The following paragraphs refer by letter to corresponding entries in the

preceding flowchart. Individual errors and alarms are not detailed in the

flowchart. When referring to explanations of these in Chapter 9, ‘‘Maintenance

YES

From

page

Is a

TN771 present

in this port

network?

Does the

TN771 indicate

packet bus

faults?

Is the

problem isolated

to a single

board?

Are there

alarms or errors

against

M/T-PKT?

Are the

packet bus

problems

resolved?

Are the

packet bus

problems

resolved?

Are the

packet bus

problems

resolved?

Follow the packet

bus fault isolation and

correction procedures

Follow the board,

port and/or endpoint

repair procedures

Follow the repair

procedure for

M/T-PKT

Place the TN771

in standalone mode

Escalate

the

problem

END

fcdfpbp2 RPY 101397

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Responding to Alarms and Errors

Page 5-66Packet Bus Fault Isolation and Repair

Object Repair Procedures’’, any that do not refer explicitly to the TDM bus

(except TDM-CLK) should be considered a possible cause of packet bus

problems.

a. Problems with the system clock (TDM-CLK) can cause service disruptions

on the packet bus. All alarms active against TDM-CLK should be resolved

first, even if the explanation refers only to TDM bus. A packet bus problem

cannot cause a TDM-CLK problem, but a TDM-CLK problem can cause a

packet bus problem.

b. Throughout the flowchart, the question, ‘‘Are the packet bus problems

resolved?,’’ refers to the problems that led you to this chart, and can

involve several checks, such as:

■Are all packet bus alarms resolved?

■Are all packet circuit pack port and endpoint alarms resolved?

■Are all ISDN-BRI stations/data modules, ASAI adjuncts, System

Port supported adjuncts, Packet Gateway supported adjuncts, and

ISDN-PRI D-channel links in service?

■Does the Maintenance/Test packet bus port (in normal or

standalone mode) still indicate a packet bus fault?

c. If only a single PN is affected, the Packet Interface is probably not the

source of the problem. Nonetheless, if all of the ISDN-BRI, Packet

Gateway, Packet Data, and Universal DS1 circuit packs are located in a

single EPN, assume that the answer to this question is ‘‘No,’’ and check

the Packet Interface.

d. A packet problem that affects more than one port network is probably

caused by either a Packet Interface failure or a PPN packet bus failure.

The Packet Interface is checked before the packet bus.

e. Because the packet bus in each port network is physically separate, each

affected port network must be checked individually. The PPN should be

checked first since any EPN packet problems are usually resolved once a

PPN packet problem is resolved. After resolving the problem in one port

network, make sure that problems in other port networks have also been

resolved.

f. This step applies only when attempting to resolve an EPN packet bus

problem. When checking the Expansion Interfaces in an EPN, be sure to

check the corresponding one(s) in the PPN. (G3r supports only the TN570

Expansion Interface, not the earlier TN776 Port Network Interface).

g. If a TN771D is not present, one must be installed to accommodate the

standalone mode. See the above section on standalone mode.

h. If a TN771D is present, it can fail in such a way that it eventually disrupts

the packet bus or misinterprets a packet bus problem.

i. If work is being done on-site, follow the procedures described earlier in

this discussion on standalone mode. If work is not being done on-site, go

to the next step.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Responding to Alarms and Errors

Page 5-67Packet Bus Fault Isolation and Repair

j. The answer is yes if any of the following apply:

■The TN771D in standalone mode indicates any faulty leads.

■Test #572 in the PKT-BUS test sequence fails.

■The status port-network P display indicates that faulty leads are

present and the TN771D in the port network is known to be

functioning correctly.

k. If the non-functional endpoints are isolated to a single circuit pack, that

circuit pack is probably the cause of the problem.

l. Investigate errors and alarms in the following order:

1. Circuit pack-level

2. Ports

3. Endpoints

m. Follow the ‘‘Troubleshooting Procedures’’ outlined later in this discussion.

If the packet bus problem cannot be resolved with these procedures,

follow normal escalation procedures.

Correcting Packet Bus Faults

The Status Port-Network Command

Status port-network P displays include the service state, alarm status, and, if

the Maintenance/Test packet bus port is present, the number of faulty and open

leads for the packet bus in the specified port-network. This information can be

used to determine the urgency of the repair. In general, a service state of “out”

indicates extreme urgency, while a service state of “reconfig” indicates moderate

urgency.

NOTE:

Ultimately, the urgency of a repair is determined by the customer’s

requirements. A customer who uses ISDN-BRI for station sets, or who relies

heavily on packet bus supported system adjunct features like DCS, Audix,

or CDR, probably considers a packet bus failure critical. On the other hand,

a customer with little ISDN-BRI service and no adjunct features may

consider even an uncorrectable packet bus fault unimportant, and may

prefer to delay repairs due to their disruptive nature.

If background maintenance is running on the packet bus when the status

port-network command is issued, the data reported for the packet bus may be

inconsistent due to updating by the tests. If the data seems inconsistent, enter

the command again.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Responding to Alarms and Errors

Page 5-68Packet Bus Fault Isolation and Repair

If test results or the results of the status port-network command indicate that

there are 24 faults on the packet bus, the problem is probably caused by faulty

cables between carriers, or by defective or missing bus terminators. However,

before proceeding, make sure that the Maintenance/Test packet bus port is not

generating a false report by looking for an M/T-PKT error in the error log. Then

test the Maintenance/Test packet bus port with test port UUCSSpp. See

‘‘Special Precaution Concerning the TN771D’’ above if any problems are

suspected.

NOTE:

If the carrier into which a TN771D Maintenance/Test circuit pack is inserted

does not have a -5V power supply, the Maintenance/Test packet bus port

reports 24 open leads in response to status port-network, or Test #572 of

the PKT-BUS test sequence. Refer to CARR-POW maintenance in Chapter

9 to ensure that a -5 volt power supply is available.

Considerations for Duplicated Systems

Some packet bus-related components are duplicated in systems with one of the

duplication options:

■In High Reliability systems (duplicated SPE, simplex PNC), Packet

Interface circuit packs are duplicated with the SPEs, a Maintenance/Test

circuit pack is required in the PPN, and Maintenance/Test packet bus

reconfiguration is not enabled.

■In Critical Reliability Systems (duplicated SPE and PNC), the Packet

Interface circuit packs are duplicated, Maintenance/Test circuit packs are

required in all port networks, and packet bus reconfiguration by the

Maintenance/Test circuit packs is enabled.

If a packet bus problem is caused by a duplicated component, switching to the

standby component may alleviate the problem and isolate the faulty circuit pack.

Start by executing the commands in the following list when they apply.

■reset system interchange: If this command resolves the packet bus

problem, the problem is with the Packet Interface in the SPE which was

just switched to standby. Refer to ‘‘PKT-INT (Packet Interface Circuit

Pack)’’ in Chapter 9, ‘‘Maintenance Object Repair Procedures’’.

■reset pnc interchange: If this command resolves the packet bus

problem, the problem is with the EIs or the link on the PNC (a or b) that just

became the standby. Refer to ‘‘EXP-INTF (Expansion Interface Circuit

Pack)’’ in Chapter 9, ‘‘Maintenance Object Repair Procedures’’.

■set tone-clock: If this command resolves the packet bus problem, the

problem is with the Tone/Clock that just became the standby. Refer to

‘‘TDM-CLK (TDM Bus Clock)’’ in Chapter 9, ‘‘Maintenance Object Repair

Procedures’’ of this document.

Continue with the procedures in the next section.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Responding to Alarms and Errors

Page 5-69Packet Bus Fault Isolation and Repair

Troubleshooting Procedures

Packet bus faults are usually caused by a defective circuit pack connected to the

backplane, by bent pins on the backplane, or by defective cables or terminators

that make up the packet bus. The first two faults cause shorts, while the third fault

causes either shorts or opens.

There are four procedures for correcting packet bus faults. Which are used

depends on the nature of the fault. For example:

■If the Maintenance/Test packet bus port is activated, and if there is an

indication of open leads on the packet bus from status port-network or

Test #572, go directly to Procedure 4. Procedures 1 through 3 try to locate

faulty circuit packs or bent pins and these do not cause open faults.

■If there are both shorts and opens, start with Procedure 4, and return to

Procedure 1 if shorts persist after the open leads are fixed.

!CAUTION:

Packet bus fault isolation procedures involve removing circuit packs and

possibly disconnecting entire carriers These procedures are destructive.

Whenever possible, implement these procedures during hours of minimum

system use.

!CAUTION:

To replace the following circuit packs, follow instructions in the appropriate

sections: Tone-Clock (‘‘TONE-BD (Tone-Clock Circuit Pack)’’), Expansion

Interface (‘‘EXP-INTF (Expansion Interface Circuit Pack)’’), Packet Interface

(‘‘Replacing SPE Circuit Packs’’).

When the procedure asks whether the packet bus problem has been resolved,

the following conditions should all be met:

■All faulty leads reported by the TN771D standalone mode should no

longer be reported.

■All alarms against the packet bus and packet circuit packs have been

resolved.

■All ISDN-BRI stations and data modules and all relevant ASAI, System

Port, and Packet Gateway supported adjuncts are in service.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Responding to Alarms and Errors

Page 5-70Packet Bus Fault Isolation and Repair

Procedure 1

Procedure 1 determines whether any circuit packs that use the packet bus have

faults. For each circuit pack type in Table 5-3 proceed through the steps below.

Check the circuit pack in the order presented by the flowchart which appears

earlier in this discussion unless newly inserted circuit packs are involved. Newly

added boards are the most likely cause of a problem.

1. Display errors and display alarms for the circuit pack.

2. For any errors or alarms, follow the repair actions recommended in

Chapter 9, ‘‘Maintenance Object Repair Procedures’’.

3. After following the recommended repair actions,

whether they succeed or

fail

, determine if the packet bus fault is resolved. If so, you are finished.

4. If the packet bus fault is still present, apply this procedure to the next

circuit pack.

5. If there are no more circuit packs in the list, go to Procedure 2.

Procedure 2

Procedure 2 removes and reinserts

port

circuit packs (purple slots), and the

Expansion Interface one or several at a time. Use Procedure 2 for each port

circuit pack in the port network until the problem is resolved

all port circuit

packs have been tried.

NOTE:

The Expansion Interface circuit pack should be the last one checked since

removing it disconnects the EPN. To check an active Expansion Interface in

a system with duplicated PNC, use reset pnc interchange to make it the

standby. (Always check the status of the standby before executing an

interchange.)

Table 5-3. Packet Circuit Packs

Circuit Pack Name Circuit Pack Code Associated Maintenance Objects

ISDN-BRI TN556 BRI-BD, BRI-PORT, ABRI-PORT, BRI-SET,

BRI-DAT, ASAI-ADJ

Maintenance/Test TN771D M/T-BD, M/T-PKT

Packet Gateway TN577 PGATE-BD, PGATE-PT

Packet Data TN553 PDATA-BD, PDATA-PT

Universal DS1 TN464F UDS1-BD, ISDN-LNK

Packet Interface TN1655 PKT-INTF

Expansion Interface TN570 EXP-INTF

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Responding to Alarms and Errors

Page 5-71Packet Bus Fault Isolation and Repair

NOTE:

The Tone/Clock circuit pack should be the next-to-last one checked. (The

TN771D must be reseated after the Tone/Clock is reinstalled.) Refer to

Procedure 3 for the TN768 or TN780 Tone/Clock circuit pack in a PPN with

duplicated SPEs.

If the packet bus problem is present when the circuit pack is inserted, but is

resolved when the circuit pack is removed, either the circuit pack or the

backplane pins in that slot caused the problem. If the backplane pins are intact,

replace the circuit pack. Keep in mind that there may be more than one failure

cause.

In Procedure 2, you may try one circuit pack at a time, or multiple circuit packs

simultaneously. The allowable level of service disruption should guide this

choice. If the entire port network can be disrupted, trying large groups of circuit

packs will save time. If traffic is heavy, trying 1 circuit pack at a time is slow but

will minimize outages.

If the TN771D Standalone mode does

not

indicate packet bus faults, perform

Procedure 2 for

only the port

circuit packs (purple slots) listed in Table 5-3 in

Procedure 1. In this case, you need not check for problems with the backplane

pins. It is sufficient to determine whether the problem is resolved by removing

circuit packs.

If you decide to remove multiple circuit packs, consider working with an entire

carrier at a time to more quickly and reliably determine which circuit packs are

not

the source of trouble. Any circuit packs, (packet or non-packet), that have

been recently inserted should be checked first. Packet circuit packs should be

checked before non-packet circuit packs.

1. Remove one or several circuit packs.

2. Determine if the packet bus fault is still present. If not, go to step 4.

3. If the packet bus fault is still present:

a. Determine if the backplane pins in the removed circuit pack’s slot

are bent using the output from the Maintenance/Test standalone

mode and the backplane illustrations which appear earlier in this

discussion.

b. If the backplane pins are bent:

Power down the carrier (see ‘‘Replacing a BIU or Rectifier’’),

straighten or replace the pins, reinsert the circuit pack and restore

power. Repeat Step 2 for the same circuit pack.

c. If the backplane pins are not bent:

Reinsert the circuit pack(s), and repeat this procedure for the next

set of circuit packs.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Responding to Alarms and Errors

Page 5-72Packet Bus Fault Isolation and Repair

4. If the packet bus fault is not present:

a. Reinsert circuit packs one at a time and repeat the following

substeps until all circuit packs have been reinserted.

b. Determine if the packet bus fault has returned.

c. If the packet bus fault has returned, the reinserted circuit pack is

defective. Replace the circuit pack and then continue.

d. If the packet bus fault does not return when all of the circuit packs

have been reinserted, you are finished.

Continue with Procedure 3 if all the port circuit packs have been checked, but

the packet bus fault is still not resolved.

Procedure 3

Procedure 3 removes and reinserts SPE and EPN control circuit packs one at a

time. In the PPN, the following SPE circuit packs either use the packet bus or are

connected to it in the backplane wiring:

■TN1655 Packet Interface

■TN768/TN780 Tone/Clock

■UN332 MSSNET

In the EPN, the following control circuit packs either use the packet bus for

communication or are connected to it in the backplane wiring:

■TN775 EPN Maintenance Board

■TN768/TN780 Tone/Clock

These are the only SPE and EPN control circuit packs that are likely to cause a

packet bus problem in a stable system. Perform this procedure on only these

circuit packs.

If the TN771D Standalone mode does

not

indicate packet bus faults, perform

Procedure 3 for

only

the Packet Interface and Tone/Clock circuit packs and do

not check for problems with the backplane pins. Determining if the problem is

resolved by removing circuit packs is sufficient.

For a system with simplex SPE:

1. Power down the control carrier. Refer to ‘‘Replacing SPE Circuit Packs’’.

2. Remove the suspect circuit pack.

3. Determine if the backplane pins in the removed circuit pack’s slot are

bent.

4. If the backplane pins are bent:

a. Straighten or replace the pins.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Responding to Alarms and Errors

Page 5-73Packet Bus Fault Isolation and Repair

b. Insert the same circuit pack.

5. If the backplane pins are not bent:

a. Replace the circuit pack (reinsert the old one if a replacement is not

available).

6. Turn the power back and allow the system to reboot. This may take up to

12 minutes. Log in at the terminal.

7. Determine if the packet bus fault is still present. If not, you are finished.

If the problem is still present,

a. If the old circuit pack was reinserted in Step 5, replace the circuit pack,

and repeat Procedure 3.

b. If the circuit pack was replaced in Step 5, repeat Procedure 3 for the next

SPE circuit pack.

If Procedure 3 fails to identify the cause of the problem, go to Procedure 4.

For a system with duplicated SPEs:

1. For SPE circuit packs, follow the ‘‘Replacing Circuit Packs on a Duplicated

SPE: Lock-and-Power-Down’’ procedure within the ‘‘Replacing SPE Circuit

Packs’’ section to remove and replace the circuit pack.

2. To remove an EPN Tone/Clock circuit pack, use set tone-clock if

necessary to make the suspect circuit pack the standby. (Always check

the status of the standby Tone/Clock with status port network before

executing an interchange.)

3. Determine if the backplane pins in the removed circuit pack’s slot are

bent.

4. If the pins are bent:

a. Power down the carrier if it is not already.

b. Straighten or replace the pins.

c. Insert the same circuit pack.

d. Restore power to the carrier.

5. If the backplane pins are not bent:

Insert or replace the circuit pack.

6. Determine if the packet bus fault is still present. If not you are finished.

7. If the packet bus fault is still present, do the following:

a. If the old circuit pack was reinserted in Step 5, replace the circuit

pack and repeat Procedure 3 starting at Step 2.

b. If the circuit pack was replaced with a new one, proceed with the

next step.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Responding to Alarms and Errors

Page 5-74Packet Bus Fault Isolation and Repair

8. Repeat this procedure for the other SPE or Tone/Clock. If both have

already been checked, go to the next step.

9. If all SPE and/or EPN control circuit packs have been checked and the

problem is not resolved, continue with Procedure 4.

Procedure 4

Procedure 4 is used when the preceding procedures fail or when open leads are

present. It is helpful in identifying multiple circuit pack faults and carrier hardware

faults. It attempts to isolate the failure to a particular set of carriers and checks

only the circuit packs in those carriers.

In Procedure 4, the TDM/LAN Cable Assemblies and TDM/LAN termination

resistor packs are replaced. If this action does not resolve the packet bus fault,

the carriers are reconfigured by moving the termination resistor packs on the

carrier backplanes in such a manner that certain carriers are disconnected from

the bus. To terminate the packet bus at the end of a particular carrier, unplug the

cable that connects the carrier to the next carrier and replace the cable with a

TDM/LAN terminator resistor pack (see Figure 5-16). When the length of the

packet bus is modified with this procedure, circuit packs that are essential to

system operation (and the TN771D Maintenance/Test in standalone mode) must

still be connected to the new ‘shortened’ packet and TDM busses.

!DANGER:

Power must be removed from the entire port network before any cables or

terminators are removed. Failure to do so can cause damage to circuit

packs and power supplies, and can be hazardous to the technician.

!DANGER:

Circuit packs in carriers that are not part of the shortened bus are not

inserted. As a result, these circuit packs are not alarmed Ignore alarm

status for these circuit packs for now All alarms should be resolved when

the cabinet is restored to its original configuration.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Responding to Alarms and Errors

Page 5-75Packet Bus Fault Isolation and Repair

Figure 5-16. Carrier Rewiring Example—Rear View of Multicarrier Cabinet

Procedure 4 consists of two parts. Part 1 attempts to clear the packet bus fault by

replacing all the bus cabling and terminators within a port-network. Part 2

attempts to isolate the fault to a particular carrier by extending the packet bus

from the control carrier to additional carriers one at a time.

Part 1:

1. Power down the port network.

2. Replace all of the TDM/LAN Cable Assemblies and both TDM/LAN

Terminators.

3. Restore power to the port network.

4. Determine if the packet bus fault is still present.

5. If the packet bus fault is resolved, the procedure is completed. Otherwise,

go to Part 2.

TDM/LAN Bus Cable TDM/LAN Bus Terminator

Normally

Conﬁgured

Cabinet

(All 5 Carriers

Used)

Bus Shortened

to Carrier A Only

(Control Carrier)

Shortened Bus

Extended to

Include

A and B

Carriers

Carrier D

Carrier E

Fans

Carrier A

Carrier B

Carrier C

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Responding to Alarms and Errors

Page 5-76Packet Bus Fault Isolation and Repair

Processor Port Network:

1. Power down the cabinet and terminate the packet bus so that it extends

only from the carrier that contains the active SPE (A or B) to the carrier that

contains the Maintenance/Test circuit pack.

2. Power up the cabinet, allow the system to reboot, and determine if the

packet bus fault is still present. If not, proceed to the next step.

If there are shorts on the packet bus, perform Procedures 2 and/or 3 for

the circuit packs in the active SPE and carriers connected to it on the

shortened bus. (Procedure 2 is performed for port circuit packs, and

Procedure 3 is performed for SPE circuit packs.)

3. If the packet bus fault is not present, extend the packet bus to another

carrier, and repeat the procedure in the previous step. When the addition

of a carrier causes the fault to recur, and if there are shorts, perform

Procedure 2 and/or Procedure 3 for only the circuit packs in that carrier.

4. If the packet bus fault recurs when the packet bus is extended, and if

there are no shorts, or Procedures 2 and 3 do not resolve the problem, the

added carrier(s) that caused the problem to recur are defective and must

be replaced.

Expansion Port Networks:

1. Place the Maintenance/Test circuit pack into a carrier that contains the

active Expansion Interface circuit pack to permit isolation of the failure to

the smallest possible number of carriers.

2. Power down the cabinet and terminate the packet bus on the carrier with

the M/T and active EI.

3. Determine if the packet bus fault is still present If so, and if there are shorts

on the packet bus, perform Procedure 2 and/or Procedure 3 for only the

circuit packs in carriers connected to the ‘‘shortened’’ packet bus.

4. If the packet bus fault is not present, extend the packet bus to another

carrier, and repeat the procedure in the previous step. When a carrier that

causes the fault to recur is added, and if there are shorts, perform

Procedure 2 and/or Procedure 3 for only the circuit packs in that carrier.

5. If the packet bus fault recurs as the packet bus is extended, and if there

are no shorts, or Procedures 2 and 3) do not resolve the problem, the

added carrier(s) that caused the problem to recur are defective and must

be replaced.

Additional Maintenance Procedures

Page 6-1Software Updates

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

6Additional Maintenance Procedures

Software Updates

A software update is the complete replacement of the software load running on a

switch with a new version of software. Updates are used to provide new features

and improved services, and to repair bugs discovered in the field. Note that the

process is called a software update; the command used is upgrade software. A

description of this command appears in Chapter 8, ‘‘Maintenance Commands’’.

Software

field updates

are partial replacements of a software load normally used

for emergency bug fixes. Usually, a field update is transmitted electronically to

the system from a remote site, but a technician must be on site to apply the

update to backup tapes and insure that the system returns to normal operation.

This procedure should be guided by the remote facility applying the update.

Refer to

DEFINITY Enterprise Communications Server Release 5.4 Upgrades and

Additions for R5r

for specific upgrade information.

Software Version Number

Each software load is identified by a version number. The following are typical

software version numbers displayed when list configuration software-version

is entered:

SOFTWARE VERSION: DG3r01.06.1.00.0

SOFTWARE VERSION: G3r5.01.2.0.078

This identifier is also called the release number or the vintage number. Version

numbers are interpreted as follows:

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Additional Maintenance Procedures

Page 6-2Software Updates

Release 5r loads:

The boot image field contains “m” (mips) for G3r systems.

The system expects any software upgrade to be going from a lower, or older

version number, to a higher, or newer version number. To install an older version

(for example, when backing out a failed upgrade), follow normal escalation

procedures to avoid putting the system into a corrupted state.

Each software version also has a compatibility index of the form:

Differences between old and new version numbers and compatibility indexes

can be used to determine what service effects can be expected from the update.

See the ‘‘Service Effects of a Software Update’’ section that follows.

Service Effects of a Software Update

Simplex SPE

The upgrade software command executes a system reboot similar to a reset

system 4. Emergency transfer is invoked and all calls drop. The MT login is

terminated and error logs are cleared. The service outage lasts for a period of up

to 15 minutes. Results of each step in the upgrade process and initialization

diagnostics are displayed on the terminal screen. Screen output is described in

Maintenance Commands

, upgrade software. Failure of initialization will produce

an SPE-down mode, described in

Initialization and Recovery

. Translations are

reloaded from the primary storage device and reformatted for the new software if

necessary.

Duplicated SPE

On a system with a duplicated SPE, a software update may be either

call-preserving

call-dropping

. The compatibility of the old and new versions

determines which type of update is performed. If the major fields of the

compatibility indexes of the two versions are equal, then a call-preserving update

is possible. The documentation accompanying the update tapes (Engineering

Design Information, or EDI, and the Release Letter) should confirm this. With rare

exceptions, this is the case when the Feature Version and Product ID numbers

match.

G3r5 m 01 2 0 078

Product Boot Major Minor Unscheduled Load

ID Image Release Release Release Number

Major Field Minor Field

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Additional Maintenance Procedures

Page 6-3Software Updates

If these conditions are not met, The upgrade software call-override option must

be used, and the update will result in a system reset level 2 (cold-2 restart). An

additional option, preserve-calls, can be added to force the system to attempt to

preserve calls, but this must be used with care. If the incompatibility is great

enough, this option may cause the system to escalate to a reboot (reset system

4). It is recommended that you escalate any such software update.

Call-Preserving Update

During a call-preserving update, calls in which two or more parties are

connected and talking are preserved. The following types of calls are dropped:

wideband calls, held calls, dialing calls, and calls that are connected to

announcements, speech synthesizers, or tones. Administered connections are

dropped and automatically restored. Feature activation attempts are ignored. No

new calls are processed for a brief period. This period usually lasts less than 5

seconds but can last up to 1 minute depending on traffic load during the SPE

interchange. Conference calls that attempt a new connection are either ignored

or dropped.

Call-Dropping Update

During a call-dropping update, the effect will be similar to a cold-2 restart (reset

system 2). All calls and system links drop, and the MT login is terminated. The

service outage lasts up to 4 minutes.

Preparing for a Software Update

1. Notify users of anticipated service effects described in the preceding

section and arrange to do the update at a suitable time. Also advise

appropriate users of the following feature interactions:

■Administered connections are temporarily dropped.

■Leave Word Calling messages stored in the SPE are lost. Those

stored in a Message Server Adjunct or AUDIX system are saved.

■Some feature settings will be lost and must be restored afterward.

The effect is the same as a cold-2 restart. Features affected include

night service, trunk/hunt group control, and manual/clock-manual

override status on time of day routing. For example, hunt groups

and attendant are put into night service after the update.

■ACD queues will be lost. There is no mechanism to drain the

queues. CMS or BCMS can be used to monitor the queue lengths.

If it is important to empty all queues before the update, you must

coordinate with the customer to redirect traffic away from ACD

splits before the update. Changing vectors to temporarily route

calls to a disconnect announcement is one way to accomplish this.

ACD agents will need to log in again after the update and their

status lamps may be incorrect for about an hour (until periodic

background maintenance completes one cycle).

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Additional Maintenance Procedures

Page 6-4Software Updates

■CMS links are dropped and restored, resulting in a loss of incoming

data during the upgrade. Data loss can be minimized by

performing the update soon after the end of a CMS measurement

interval.

■Wideband calls are dropped.

2. Some information which is stored in system memory will be lost and must

be manually recorded and then re-entered after the update:

■Record all busied out maintenance objects. Enter display errors

print, and select error type 18 on the menu. All busyouts will be lost

during the update and must be reentered afterward. Disabled

maintenance objects will likewise be re-enabled by the update.

■All measurement data stored in memory, including BCMS, is lost.

Print any desired reports before the update.

■Enter list report-scheduler. Reports that are currently printing or

queued will be lost. Wait until reports are finished printing or notify

the customer. Reports are printing if the Link State field displays up

on the status sp-link screen.

■Enter list wakeup print and list do-not-disturb stations print.

These feature settings will be lost and must be re-entered

afterwards.

3. Make sure that the system’s health and activity can support a successful

update:

■Enter status spe and verify that the state of health of the SPE is

functional

. This must hold true for active and standby SPEs when

duplicated.

■Enter display alarms and display errors. Resolve any active

alarms or errors against SPE components or the PPN Tone-Clock.

■Enter status logins and make sure that no other logins except

yours are active.

■Enter status health and look at the amount of load on the system. If

call processing is greater than 50 percent, an update is not

recommended due to increased customer impact.

■Disable TTI changes by the change system-parameters features.

■Enter change system-parameters maintenance and make sure

that scheduled daily maintenance will not be running during the

update. The Start Time field should be set to a time well after the

session will end. If scheduled daily maintenance is running and

needs to be shut off, set the Stop Time field to one minute after the

current time. Be sure to restore the original settings when finished.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Additional Maintenance Procedures

Page 6-5Software Updates

Restoring the System after an Update

During software updates, including call-preserving updates, several feature

settings are lost. These must be manually restored afterward.

■Re-enter all Maintenance Object busyouts.

■Re-enter wakeup calls and do-not-disturb stations.

■Restore attendant feature settings.

■Notify Administration and ACD users that the update is complete.

■Re-enable TTI changes by the change system-parameters features.

■On the change system-parameters maintenance form, restore Alarm

Origination, Save Translations, CPE Alarm Level and SPE Interchange

fields and Scheduled Daily Maintenance times to their original settings.

■Manually reset any speakerphones which derive power from the switch by

pressing the button on the voice terminal.

Backing Out of a Software Update

If fatal hardware errors or memory faults prevent the update from completing, the

system must be recovered and the update backed out. If the update command

has already been entered, follow normal escalation procedures. Backing out

after this point is hazardous and may leave the system in a corrupted state.

Software Update Procedure — Simplex SPE

After making the preparations described above, execute the following sequence

of steps, entering the commands shown in bold type. This part of the procedure

normally takes about 3 1/2 hours. Screen output for each command is described

in Chapter 8, ‘‘Maintenance Commands’’. If errors are encountered after entering

the

update software

command, follow normal escalation procedures. Avoid

touching the keyboard while the save or upgrade commands are running since

doing so may cause diagnostic messages to be lost.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Additional Maintenance Procedures

Page 6-6Software Updates

Table 6-1. Software Update—Simplex SPE

Step Time

(min) Remarks

change sys-par

maint 2 Note the current settings of the Save Translation and Alarm

Origination Activated fields and then set them to n. Set CPE

Alarm Activation Level to none. Make sure scheduled daily

maintenance is not set to run during the update.

save

announcements 40 These steps create a backup tape in case the update fails

and a backout is necessary. Saving announcements may be

skipped if display announcements shows no administered

announcements.

save translation 2

backup disk 10

Remove the

backup tape and

clean the tape

drive

5 This procedure is described under ‘‘TAPE’’ in Chapter 9,

‘‘Maintenance Object Repair Procedures’’.

Insert the tape

with the new

software

2 Wait for the tape to retension itself.

list config

software-version 5 Make sure the tape has the expected version number.

restore disk

install 10 This copies files from the new tape to disk. If you are

updating

from

a load earlier than 6.0, substitute for this step

the following sequence: copy announce tape, save

translation tape, then restore disk full.

The following step will result in the service effects described above.

upgrade software

to-version 10 Use the new software version number described above. The

system will reboot and then reload translations. Results of

each step in the upgrade process and initialization

diagnostics will be displayed on the terminal. A full

description of screen output appears in upgrade software

in Chapter 8, ‘‘Maintenance Commands’’.

NOTE:

Be careful not to touch the G3-MT keyboard while

waiting for the command to execute, or the result

messages may be lost.

Continued on next page

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Additional Maintenance Procedures

Page 6-7Software Updates

Software Update Procedure — Duplicated SPE

After making the preparations described above, execute the following sequence

of steps, entering the commands shown in bold type. This part of the procedure

normally takes about 3-1/2 hours. Screen output for each command is described

in Chapter 8, ‘‘Maintenance Commands’’. If errors are encountered after entering

the update software command, follow normal escalation procedures. Avoid

touching the keyboard while the save or upgrade commands are running since

doing so may cause diagnostic messages to be lost.

change sys-par

maint 2 Set the Save Translation, Alarm Origination Activated, CPE

Alarm Level, and Daily Scheduled Maintenance times to the

values that were in effect before starting this procedure.

save translation 2 This step stores the upgraded translations on disk.

backup disk 20 This step makes a backup copy of the new files. If a

coredump from before the upgrade is on disk, this can take

up to 50 minutes.

test stored-data 10 This step verifies that all MSS files are consistent. The next

run of scheduled maintenance will also do this.

list config soft

long 5 Verify that all files are correct.

backup disk 20 Make extra backup copies of the new files as needed. The

next run of scheduled maintenance will also do this.

set vector 8 1 Sets the coredump vector to take a coredump when the

system reboots.

Restore the system as described above.

Table 6-1. Software Update—Simplex SPE — Continued

Step Time

(min) Remarks

Continued on next page

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Additional Maintenance Procedures

Page 6-8Software Updates

Table 6-2. Software Update—Duplicated SPE

Step Time

(min) Remarks

change sys-par maint 2 Note the current settings of the Save

Translation, SPE Interchange, and Alarm

Origination Activated fields and then set

them to n. Set CPE Alarm Activation Level

to none. Make sure scheduled daily

maintenance is not set to run during the

update.

save announcements 40 These steps create a backup tape in case

the update fails and a backout is

necessary. Saving announcements may

be skipped if display announcements

shows no administered announcements.

save translation 2

backup disk 10

Remove tapes and

clean tape drives. 5 This procedure is described under ‘‘TAPE’’

in Chapter 9, ‘‘Maintenance Object Repair

Procedures’’.

Insert the tapes

containing the new

software

2 Wait for the tape to retension itself.

list config

software-version long 5 Make sure the tapes have the expected

version number.

restore disk install

both 10 Copies new tape files to disk. If updating

from

a load earlier than 6.0, substitute for

this step the following sequence: copy

announce tape, save translation tape,

then restore disk full both.

Continued on next page

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Additional Maintenance Procedures

Page 6-9Software Updates

The following step will

result in the service

effects described

above. upgrade

software to-version

10 Use the new software version number

described above. The system will reboot

the standby SPE, reload translations, and

then execute an SPE interchange. Results

of each step in the upgrade process and

initialization diagnostics will be displayed

on the terminal.

NOTE:

Be careful not to touch the G3-MT

keyboard while waiting for the

command to execute, or the result

messages may be lost.

status spe 5 Repeat this command until the states of

health of both SPEs are

functional

reset spe-standby 4 5 This step initiates a reboot of the standby

SPE with the new software load.

status spe 15 Repeat this command until the states of

health of both SPEs are

functional

change sys-par maint 2 Set the Save Translation, Alarm Origination

Activated, CPE Alarm Level, SPE

Interchange fields and Daily Scheduled

Maintenance times to the values that were

in effect before starting this procedure.

save translation both 2 This step stores the upgraded translations

on both disks.

backup disk 20 This step makes a backup copy of the new

files. The next run of scheduled

maintenance will also do this. If a

coredump from before the upgrade is on

disk, this can take up to 50 minutes.

test stored-data 10 This step verifies that all MSS files are

consistent. The next run of scheduled

maintenance will also do this.

list config soft long 5 Verify that all files are correct.

Table 6-2. Software Update—Duplicated SPE — Continued

Step Time

(min) Remarks

Continued on next page

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Additional Maintenance Procedures

Page 6-10DS1 CPE Loopback Jack (T1 Only)

DS1 CPE Loopback Jack (T1 Only)

Using the DS1 CPE Loopback Jack (apparatus code 700A, comcode

107988867), a technician can test the DS1 span between the system and the

network interface point. The loopback jack is required when DC power appears

at the interface to the ICSU.

The loopback jack isolates the ICSU from the DC

power and properly loops the DC span power

NOTE:

The loopback jack operates with any vintage of TN767E (or later) or

TN464F (or later) DS1 circuit packs and with G3V3 EDI release 3 (or later)

software. The loopback jack operates with the 120A2 (or later) Integrated

Channel Service Unit (ICSU) only;

not

the 31xx series of Channel Service

Units or other external CSUs or earlier ICSUs.

Loopback Jack Installation

Configurations Using a Smart Jack

The preferred location of the loopback jack is at the interface to the Smart Jack.

This provides maximum coverage of CPE wiring when remote tests are run using

the loopback jack. If the Smart Jack is not accessible, install the loopback jack at

the extended demarcation point.

1. If there is no extended demarcation point, install the loopback jack directly

at the network interface point as shown in Figure 6-1.

2. If there is an extended demarcation point and the Smart Jack is not

accessible, install the loopback jack as shown in Figure 6-2.

3. If there is an extended demarcation point, but the Smart Jack is

accessible, install the loopback jack as shown in Figure 6-3.

backup disk 20 Make extra backup copies of the new files

as needed.

set vector f spe-maint 1 Sets the coredump vector to take a

coredump when the system reboots.

Restore the system as described above.

Table 6-2. Software Update—Duplicated SPE — Continued

Step Time

(min) Remarks

Continued on next page

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Additional Maintenance Procedures

Page 6-11DS1 CPE Loopback Jack (T1 Only)

Configurations Without a Smart Jack

1. Install the loopback jack at the point where the cabling from the ICSU

plugs into the “dumb” block. If there is more than one “dumb” block,

choose the one that is closest to the Interface Termination feed or the fiber

MUX. This provides maximum coverage for loopback jack tests. Refer to

Figure 6-4 and Figure 6-5.

Installation

1. To install the loopback jack, simply disconnect the RJ-48 (8-wide)

connector (typically an H600-383 cable) at the appropriate interface point

and connect the loopback jack in series with the DS1 span. See Figure 6-1

through Figure 6-5.

2. Plug the H600-383 cable from the ICSU into the female connector on the

loopback jack.

3. Plug the male connector on the loopback jack cable into the network

interface point.

NOTE:

Do not remove the loopback jack after installation. This is not a test

tool and should always be available to remotely test a DS1 span.

Administration

1. At the management terminal, enter change ds1 <location>. The

“location” is the DS1 interface circuit pack for which the loopback jack

was installed.

2. Be sure the “near-end CSU type” is set to integrated.

3. On page 2 of the form, change the supply CPE loopback jack

power field to y.

NOTE:

Setting this field to y informs the technician that a loopback jack is

present on the facility. This allows a technician to determine that the

facility is available for remote testing.

4. Enter save translation to save the new information.

DS1 Span Test

This test should only be performed after the DS1 circuit pack and the 120A2 (or

later) ICSU have been successfully tested using appropriate maintenance

procedures. The DS1 span test consists of 2 sequential parts. Each part provides

a result indicating if there is a problem in the CPE wiring. CPE wiring may be

considered problem-free only if the results of both parts are successful.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Additional Maintenance Procedures

Page 6-12DS1 CPE Loopback Jack (T1 Only)

The first part of the span test powers-up the loopback jack and attempts to send

a simple code from the DS1 board, through the wiring and loopback jack, and

back to the DS1 board. Maintenance software waits about 10 seconds for the

loopback jack to loop, sends the indication of the test results to the management

terminal, and proceeds to the second part of the test.

The second part of the test sends the standard DS1 3-in-24 stress testing pattern

from the DS1 board, through the loopback jack, and back to a bit error detector

and counter on the DS1 board. The bit error rate counter may be examined at will

via the management terminal, and provides the results of the second part of the

test. The test remains in this state until it is terminated so that the CPE wiring may

be bit error rate tested for as long as desired.

1. Busy out the DS1 circuit pack by entering busyout board UUCCSS

(where UUCCSS is the cabinet, carrier, and slot number of the DS1

board).

2. At the management terminal, enter change ds1 <location> and verify the

near-end csu type is set to integrated.

3. Change to page 2 of the DS1 administration form and confirm that the TX

LBO field is 0dB. If not, record the current value and change it to 0dB for

testing. Press Enter to implement the changes or press Cancel to change

nothing.

4. Enter test ds1-loop <location> cpe-loopback-jack. This turns on simplex

power to the loopback jack and waits about 20 seconds for any active

DS1 facility alarms to clear. A “PASS” or “FAIL” displays on the terminal.

This is the first of the 2 results. A “FAIL” indicates a fault is present in the

wiring between the ICSU and the loopback jack. The loopback jack may

also be faulty. A “PASS” only indicates that the loopback jack looped

successfully, not that the test data contains no errors. If a “PASS” is

obtained, continue with the following steps.

NOTE:

The loss of signal (LOS) alarm (demand test #138) is not processed

during this test while the 3-in-24 pattern is active.

5. Enter clear meas ds1 loop <location> to clear the bit error count.

6. Enter clear meas ds1 log <location> to clear the performance

measurement counts.

7. Enter clear meas ds1 esf <location> to clear the ESF error count.

8. Enter list meas ds1 sum <location> to display the bit error count. Refer

to Table 6-3 for troubleshooting information.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Additional Maintenance Procedures

Page 6-13DS1 CPE Loopback Jack (T1 Only)

9. Repeat Steps 5 through 8 as desired to observe bit error rate

characteristics. Also, wait 1 to 10 minutes between Steps 5 through 7. One

minute without errors translates to better than a 1 in 10 to the eighth error

rate. Ten minutes without errors translates to better than a 1 in 10 to the

ninth error rate.

10. If the test runs for 1 minute with an error count of 0, confirm that the 3-in-24

pattern error detector is operating properly by entering test ds1-loop

<location> inject-single-bit-error. This causes the 3-in-24 pattern

generator on the DS1 circuit pack to inject a single-bit error into the

transmit pattern. A subsequent list meas ds1 summary <location>

command displays the bit error count. If a count greater than 1 is

displayed, replace the ICSU and retest. If the problem continues, replace

the DS1 circuit pack.

Table 6-3. DS1 Span Troubleshooting

Displayed Field Function Indication

Test:

cpe-loopback-jack Pattern 3-in-24 The loopback jack test is active.

Synchronized Y or N If “y” displays, the DS1 circuit pack has synchronized to

the looped 3-in-24 pattern and is accumulating a count of

the bit errors detected in the pattern until the test has

ended. If “n” displays, retry the test 5 times by ending the

test per Step 11 and re-starting the test per Step 4. If the

circuit pack never synchronizes, substantial bit errors in

the 3-in-24 pattern are likely. This could be intermittent

connections or a broken wire in a receive or transmit pair

in the CPE wiring.

Bit Error Count Cumulative

count of

detected errors

If there are no wiring problems, the counter remains at 0.

A count that pegs at 65535 or continues to increment by

several hundred to several thousand on each list meas

command execution indicates intermittent or corroded

connections, severe crosstalk, or impedance imbalances

between the two conductors of the receive pair or the

transmit pair. Wiring may need replacement.

Note that “ESF error events” counter and the ESF

performance counter summaries (“errored seconds”,

“bursty errored seconds”, and so forth) will also

increment. These counters are not used with the

loopback jack tests. However, they will increment if errors

are occurring. Counters should be cleared following the

test.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Additional Maintenance Procedures

Page 6-14DS1 CPE Loopback Jack (T1 Only)

11. Terminate the test by entering test ds1-loop <location> end

cpe-loopback-jack-test. Wait about 30 seconds for the DS1 to re-frame

on the incoming signal and clear DS1 facility alarms.

Loopback termination fails under the following conditions:

a. The span is still looped somewhere. This could be at the loopback

jack, at the ICSU, or somewhere in the network. This state is

indicated by a fail code of 1313. If the red LED on the loopback

jack is on, replace the ICSU. Re-run the test and verify that the

loopback test terminates properly. If not, replace the DS1 circuit

pack and repeat the test.

b. The DS1 cannot frame on the incoming span’s signal after the

loopback jack is powered down. This means that there is

something wrong with the receive signal into the loopback jack

from the “dumb” block or the Smart Jack. If the service provider

successfully looped and tested the span, up to the Smart Jack, this

condition isolates the problem to the wiring between the loopback

jack and the Smart Jack. Refer to “Loopback Jack Fault Isolation

Procedures” for information on how to proceed in this case. The

test cannot be successfully terminated until a good signal is

received. To properly terminate the test before a good receive

signal is available, enter reset board <location>.

12. Restore the “TX LBO” field to the original value recorded in Step 2.

13. Release the DS1 circuit pack using the release board UUCCSSpp

command.

14. Leave the loopback jack connected to the DS1 span.

Loopback Jack Fault Isolation Procedures

This section describes the possible DS1 configurations in which the loopback

jack may be used. These configurations are: when the DS1 provider includes a

Smart Jack, when no Smart Jack is provided at all, and when sites use fiber

multiplexers. These configurations are separated into “Configurations Using a

Smart Jack” and “Configurations Without a Smart Jack.”

Configurations Using a Smart Jack

The addition of the loopback jack and the presence of a Smart Jack divides the

DS1 span into 3 separate sections for fault isolation. These sections are shown in

Figure 6-1 through Figure 6-3 for the different span configurations. They are:

Section 1: Between the 120A2 (or later) ICSU and the loopback jack.

Section 2: Between the loopback jack and the Smart Jack (network interface

point).

Section 3: From the Smart Jack to the CO. It is necessary to contact the DS1

provider to run this test.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Additional Maintenance Procedures

Page 6-15DS1 CPE Loopback Jack (T1 Only)

A problem can exist in 1 or more of the 3 sections. The field technician is

responsible for finding and correcting problems in the first 2 sections. The DS1

service provider is responsible for finding and correcting problems in the third

section. Testing is divided into 3 steps.

■Test customer premises wiring (section 1 in the following 3 figures) from

the ICSU to the loopback jack as described in “DS1 Span Test.”

■Test the CO-to-network interface wiring (section 3 in Figure 6-1) using the

Smart Jack loopback (CO responsibility). Coordinate this test with the DS1

provider.

■Test the short length of customer premises wiring (section 2 in the

following 3 figures) between the loopback jack and the Smart Jack. This

can be done using a loopback that “overlaps” section 2 of the cable. Any

of the following loopbacks can do this:

a. The local ICSUs line loopback, which is typically activated, tested,

and then deactivated by the DS1 service provider at the CO end.

b. The local DS1 interface’s payload loopback, activated and tested

by the DS1 service provider at the CO end.

c. The far-end ICSU’s line loopback. This test is activated at the

management terminal by entering test ds1-loop <location>

far-csu-loopback-test-begin. The test is terminated by entering

test ds1-loop <location> end-loopback/span-test. Bit error

counts are examined as described in “DS1 Span Test.” This test

method is the least preferable because it covers wiring that is not in

the local portion of the span. This test only isolates problems to

section 2 wiring if there are no problems in the wiring between the

far-end CO and the far-end ICSU. Coordinate this test with the DS1

service provider.

If any of the above tests (a, b, or c) fail, a problem is indicated in section 2

as long as the tests for section 1 and section 3 pass. Since section 2

includes the network interface point, it is necessary to work with the

service provider to isolate the fault to the loopback jack cable, the “dumb”

block, or the Smart Jack.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Additional Maintenance Procedures

Page 6-16DS1 CPE Loopback Jack (T1 Only)

Figure 6-1. Network Interface at Smart Jack

Figure Notes:

1. Span Section 1

2. Span Section 2

3. Span Section 3

4. 120A2 (or later) Integrated

Channel Service Unit (ICSU)

5. RJ-48 to Network Interface (Up to 1000

Feet) (305 m)

6. Loopback Jack

7. Network Interface Smart Jack

8. Interface Termination or Fiber MUX

9. Central Office

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Additional Maintenance Procedures

Page 6-17DS1 CPE Loopback Jack (T1 Only)

Figure 6-2. Network Interface at Extended Demarcation Point (Smart Jack

Inaccessible)

Figure Notes:

1. Span Section 1

2. Span Section 2

3. Span Section 3

4. 120A2 (or later) Integrated

Channel Service Unit (ICSU)

5. RJ-48 to Network Interface

(Up to 1000 Feet) (305 m)

6. Loopback Jack

7. “Dumb” Block (Extended Demarcation)

8. Network Interface Smart Jack

9. Interface Termination or Fiber MUX

10. Central Office

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Additional Maintenance Procedures

Page 6-18DS1 CPE Loopback Jack (T1 Only)

Figure 6-3. Network Interface at Extended Demarcation Point (Smart Jack

Accessible)

Figure Notes:

1. Span Section 1

2. Span Section 2

3. Span Section 3

4. 120A2 (or later) Integrated

Channel Service Unit (ICSU)

5. RJ-48 to Network Interface

(Up to 1000 Feet) (305 m)

6. “Dumb” Block (Extended Demarcation)

7. Loopback Jack

8. Network Interface Smart Jack

9. Interface Termination or Fiber MUX

10. Central Office

11. “Dumb” Block to Smart Jack RJ-48

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Additional Maintenance Procedures

Page 6-19DS1 CPE Loopback Jack (T1 Only)

Configurations Without a Smart Jack

When the loopback jack is added to a span that does not contain a Smart Jack,

the span is divided into 2 sections. See Figure 6-4 and Figure 6-5.

1. ICSU to the loopback jack.

2. Loopback jack to the Central Office (CO).

Figure 6-4. Network Interface at “Dumb” Block

Figure Notes:

1. Span Section 1

2. Span Section 2

3. 120A2 (or later) Integrated

Channel Service Unit (ICSU)

4. RJ-48 to Network Interface

(Up to 1000 Feet) (305 m)

5. Loopback Jack

6. “Dumb” Block (Demarcation Point)

7. Interface Termination or Fiber MUX

8. Central Office

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Additional Maintenance Procedures

Page 6-20DS1 CPE Loopback Jack (T1 Only)

Figure 6-5. Network Interface at “Dumb” Block with Repeater Line to Fiber

MUX

Section 2 includes the short cable from the loopback jack to the “dumb” block

demarcation point (part of the loopback jack). This is the only portion o f section

2 that is part of customer premises wiring but is not covered in the loopback

jack’s loopback path.

Figure Notes:

1. Span Section 1

2. Span Section 2

3. 120A2 (or later) Integrated

Channel Service Unit (ICSU)

4. RJ-48 to Network Interface

(Up to 1000 Feet) (305 m)

5. Loopback Jack

6. “Dumb” Block (Demarcation Point)

7. Repeater

8. Fiber MUX

9. Central Office

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Additional Maintenance Procedures

Page 6-21DS1 CPE Loopback Jack (T1 Only)

A problem can exist in 1 or both of the 2 sections. The field technician is

responsible for finding and correcting problems in section 1 and the loopback

cable portion of section 2. The DS1 service provider is responsible for finding

and correcting problems in the majority of section 2. Testing is divided into 2

steps.

1. Test customer premises wiring (section 1 in Figure 6-4) from the ICSU to

the loopback jack as described in the “DS1 Span Test” section.

2. Test the loopback jack-to-”dumb” block and ”dumb” block-to-CO wiring

(section 2 in Figure 6-4). This can be done using a loopback that

“overlaps” the section of the span. Any of the following loopbacks can do

this:

a. The local ICSUs line loopback, which is typically activated, tested,

and then deactivated by the DS1 service provider at the CO end.

b. The local DS1 interface’s payload loopback, activated and tested

by the DS1 service provider at the CO end.

c. The far-end ICSU’s line loopback. This test is activated at the

management terminal by entering test ds1-loop <location>

far-csu-loopback-test-begin. The test is terminated by entering

test ds1-loop <location> end-loopback/span-test. Bit error

counts are examined as described in the “DS1 Span Test” section.

This test only isolates problems to section 2 wiring if there are no

problems in the wiring between the far-end CO and the far-end

ICSU. Coordinate this test with the DS1 service provider.

If any of the above tests (a, b, or c) fail, a problem is indicated in

section 2. This could mean bad loopback jack -to-”dumb” block

cabling, but is more likely to indicate a problem somewhere

between the “dumb” block and the CO. This is the responsibility of

the DS1 service provider. If the DS1 Span Test confirms that there

are no problems in section 1, the technician should proceed as

follows to avoid unnecessary dispatch.

■Identify and contact the DS1 service provider

■Inform the DS1 provider that loopback tests of the CPE

wiring to the “dumb” block (section 1) showed no problems

■If the far-end ICSU line loopback test failed, inform the DS1

provider

■Request that the DS1 provider perform a loopback test of

their portion of the section 2 wiring by sending someone out

to loop section 2 back to the CO at the “dumb” block.

If this test fails, the problem is in the service provider’s

wiring.

If the test passes, the problem is in the cable between the

loopback jack and the “dumb” block. Replace the loopback

jack.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Additional Maintenance Procedures

Page 6-22DS1 CPE Loopback Jack (T1 Only)

Configurations Using Fiber Multiplexers

Use the loopback jack when customer premises DS1 wiring connects to an

on-site fiber multiplexer (MUX) and allows wiring to the network interface point on

the MUX to be remotely tested. This requires that ICSUs be used on DS1 wiring

to the MUX.

Fiber MUXes can take the place of Interface termination feeds as shown in Figure

6-1 , Figure 6-2, Figure 6-3, and Figure 6-4. Test these spans using the same

procedures as metallic spans. Note the following points:

1. Fiber MUXes may have loopback capabilities that can be activated by the

service provider from the CO end. These may loop the signal back to the

CO or back to the DS1 board. If the MUX provides the equivalent of a line

loopback on the “problem” DS1 facility, this may be activated following a

successful loopback jack test and used to isolate problems to the wiring

between the loopback jack and the MUX.

2. Be aware that there are installations that use repeatered metallic lines

between the MUX and the “dumb” block. These lines require DC power for

the repeaters and this DC power is present at the “dumb” block interface

to the CPE equipment.

A loopback jack is required in this configuration to

properly isolate and terminate the DC power

To check for the presence of DC, make the following 4 measurements at the

network interface jack:

1. From Transmit Tip (T, Pin 5) to Receive Tip (T1, Pin 2)

2. From Transmit Ring (R, Pin 4) to Receive Ring (R1, Pin 4)

3. From Transmit Tip (T, Pin 5) to Transmit Ring (R, Pin 4)

4. From Receive Tip (T1, Pin 2) to Receive Ring (R1, Pin 4)

All measurements should read 0 (zero) volts DC. For pin numbers and pin

designations, refer to

Integrated Channel Service Unit (ICSU) Installation and

Operation

, 555-230-193.

Operating Charasteristics

If a TN464F or TN767E and a 120A2 were installed in a system running pre-G3V3

software and the software is later upgraded to G3V3 Release 3 or later, reseat

the DS1 circuit pack so that the ICSU administration fields will appear on the DS1

administration form.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Additional Maintenance Procedures

Page 6-23Facility Test Calls

Facility Test Calls

The Facility Test Calls feature allows you to use a voice terminal to make test

calls to specific trunks, time slots, tones, and tone receivers within the system.

The test call verifies that the accessed component is functioning properly. To use

this feature, it must be enabled on the Class of Restriction form, and you must

know the Facility Test Call Access Code. The code can be retrieved by entering

display feature-access-codes. It appears on page one of the screen output.

NOTE:

For the ISDN-PRI Test Call feature see ‘‘Troubleshooting ISDN-PRI Test Call

Problems’’ in Chapter 5, ‘‘Responding to Alarms and Errors’’.

NOTE:

The following test call descriptions are for voice terminal users:

Trunk Test Call

The trunk test call accesses specific Tie or CO trunks, including DS1 trunks. If the

trunk is busied out by maintenance, it will be temporarily released for the test call

and returned to busyout afterwards. Before making the test call, use list

configuration to determine the location of the trunk ports that you which to test.

DID trunks cannot be accessed.

To place a trunk test call:

1. Dial the FAC described above and listen for dial tone.

2. Dial the 7-digit port location UUCSSpp:

UU= Cabinet number (01 for PPN, 02 -- 44 for EPNs)

C = Carrier number (A=1, B=2, C=3, D=4, E=5)

SS = Slot number (01--20)

pp = Port circuit number (01--24)

The channels on a DS1 trunk are addressed by using the channel number

for the port number.

3. Listen for one of the following tones:

Dial tone or Silence The trunk is connected. Go to step 4.

Busy Tone The trunk is either busy processing a call or

is out of service. Check status trunk.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Additional Maintenance Procedures

Page 6-24Facility Test Calls

4. Place a call. If the call does not go through (no ringing is heard) check to

see if the circuit has been removed or if the trunk is a rotary trunk.

The dial tone heard is coming from the far-end. If the far end has been

disabled, you will not hear dial tone. However, depending on far-end

administration, you may still be able to dial digits. All digits dialed after the

port number are transmitted using end-to-end DTMF signaling. If the trunk

being tested is a rotary trunk, it is not possible to break dial tone.

DSO Loop-Around Test Call

The DS0 Loop Around feature provides a loop around connection for incoming

Non-ISDN DS1 trunk data calls. This feature is similar to the far end loop around

connection provided for the ISDN Test Call feature. This DS0 loop around is

provided primarily to allow a network service provider to perform facility testing at

the DS0 level before video teleconferencing terminals are installed at the PBX.

The feature is activated on a call-by-call basis by dialing a test call extension

specified on the second page of the System Parameters Maintenance form. No

special hardware is required. When the test call extension is received by the

PBX, a non inverting 64 kbps connection is set up on the PBX’s Time Division

Multiplexed bus. More than one loop around call can be active at the same time.

For calls routed over the public network using the ACCUNET Switched Digital

Service (SDS) or Software Defined Data Network (SDDN), the data transmission

rate is 56 Kbps since robbed bit signaling is used. For calls established over a

private network using common channel signaling, the full 64 kbps data rate is

available.

When the incoming trunk group is used only for data calls (SDS), the

Communications Type on the associated Trunk Group form should be set to

“data”. When the incoming trunk group is used for robbed bit alternate voice

and/or data (SDN/SDDN), the Communications Type on the Trunk Group form

should be set to “rbavd” (robbed bit alternate voice data). For private network

trunks using common channel signaling, the Communications Type on the

associated Trunk Group form can be set to “avd”.

Reorder tone The trunk requested is in a different port

network from your station, and inter-PN

resources are not available to access it.

Intercept Tone The port addressed is not a trunk, or it is a

DID trunk, or the trunk is not administered.

Confirmation Tone The port is a tone receiver. See the ‘‘DTMR

Test Call’’ section.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Additional Maintenance Procedures

Page 6-25Facility Test Calls

DTMR Test Call

This call accesses and tests the dual tone multifrequency receivers (DTMR-PTs)

located on TN420 and TN748 Tone Detector circuit packs. These tone receivers

are also known as touch tone receivers (TTRs). Before making the test call, use

list configuration to determine the location of the TN420 or TN748 that you

which to test.

To place a tone receiver test call:

1. Dial the FAC described in the introduction to this section and listen for dial

tone.

2. Dial the seven-digit port location UUCSSpp of one of the four DTMR ports

located on a Tone Detector circuit pack:

C = Carrier number (A=1, B=2, C=3, D=4, E=5)

SS = Slot number (00-20)

pp = Port circuit number (DTMR ports are numbered 01, 02, 05, and 06.

3. Listen for one of the following tones:

4. Dial the sequence 1234567890*#.

If the sequence is entered and received correctly, dial tone is returned

and another test call can be made. If the test fails, intercept tone is

returned. A failure may indicate a faulty DTMR port or circuit pack, a faulty

voice terminal, or an error in the entry of the sequence.

5. To test another DTMR, repeat steps 2 through 4.

6. To terminate the test call, hang up the station set used for testing.

TDM Bus Time Slot Test Call

The time slot test call connects the voice terminal to a specified time slot on the A

or B TDM Bus of a specified port network. To connect to any out-of-service time

slots, refer to the ‘‘Out-of-Service Time Slot Test Call’’ section.

To test a specific time slot on the TDM bus of a specific port network:

1. Dial the FAC described in the introduction to this section and listen for dial

tone.

Confirmation tone The DTMR is connected. Go to step 4.

Intercept tone The port entered is not a TTR, (if a trunk, see

above), or the board is not inserted.

Reorder tone The DTMR is in use, (call processing), the

board is busied out, or inter-PN resources are

unavailable for the call.

Dial tone The port is a trunk. See the preceding section.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Additional Maintenance Procedures

Page 6-26Facility Test Calls

2. Dial the 2-digit port network number followed by # and the 3-digit time slot

number listed in the following table.

3. Listen for one of the following tones:

TDM Bus Time Slots

When you address a tone-carrying time slot on the TDM bus (A or B) that is

currently carrying tones, you will be connected to that time slot and will hear the

tone.

Time slots 005-021 and 261-277 are reserved to carry the system’s dedicated

tones. Time slots 000-004 and 256-260 carry control information and are not

addressable. Time slots 254 and 510 are not addressable due to a hardware

constraint. At any given time, only one of the TDM busses (A or B) carries the

dedicated tones, with B being the default. Entering status port-network will

display which TDM bus is currently carrying the dedicated tones. The

corresponding time slots on the other bus are normally inactive and are used for

call service only as a last resort when all other non-control channel time slots on

both busses are busy. Bus A’s tone time slots are numbered 005-021; bus B’s

tone time slots are numbered 261-277.

Reorder tone The time slot is in use, the time slot is not

addressable, or inter-PN resources are not

available to make the call.

Confirmation tone The time slot is idle or out-of-service. The time

slot may be on the TDM bus (A or B) that is not

currently carrying tones, or it may be busied

out. The call is connected to the time slot so

that any noise may be heard.

System tone The time slot is carrying a system tone as listed

in the following table.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Additional Maintenance Procedures

Page 6-27Facility Test Calls

Table 6-4. TDM Bus Time Slot Numbers

TDM Bus A

time slot TDM Bus B

time slot Tone Heard

000 256 Reorder

001 257 Reorder

002 258 Reorder

003 259 Reorder

004 260 Reorder

005 261 Touch Tone 1 - 697Hz

006 262 Touch Tone 2 - 770 Hz

007 263 Touch Tone 3 - 852Hz

008 264 Touch Tone 4 - 941 Hz

009 265 Touch Tone 5 - 1209 Hz

010 266 Touch Tone 6 - 1336Hz

011 267 Touch Tone 7 - 1447 Hz

012 268 Touch Tone 8 - 1633 Hz

013 269 Dial Tone

014 270 Reorder Tone

015 271 Alert Tone

016 272 Busy Tone

017 273 Ringback Tone

018 274 Special Ringback Tone

019 275 2225 Hz Tone

020 276 Music

021 277 Tone on Hold

022-253 278-509 Confirmation (used for calls)

254 510 Reorder

255 511 Confirmation

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Additional Maintenance Procedures

Page 6-28Facility Test Calls

Out-of-Service Time Slot Test Call

This call can be used to determine if there are any out-of-service time slots on the

TDM bus of a specified port network. If there are, you will be connected to one.

By listening to noise on the time slot and selectively removing circuit packs, you

may be able to isolate the source of interference.

To place the call:

1. Dial the FAC described above and listen for dial tone.

2. Dial the port network number followed by **** and listen for one of the

following tones:

3. Repeated test calls will alternate between out-of-service time slots on TDM

bus A and TDM bus B.

System Tone Test Call

This test connects the voice terminal to a specific system tone.

To place the call:

1. Dial the FAC described above.

2. Dial the port network number followed by * and the two-digit tone

identification number from the following table.

3. Listen for one of the following tones:

NOTE:

For a definition of Call Progress Tones see

DEFINITY

Communications System Generic 3 System Descriptions and

Specifications, 555-230-206,

Chapter 11.

Reorder tone There are no out-of-service time slots on the

specified port network.

Confirmation tone Connection is made to an out-of-service time

slot.

Intercept tone The number entered is not a valid tone number.

Reorder tone Inter-PN resources are not available.

System tone The specified tone will be heard if it is functioning.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Additional Maintenance Procedures

Page 6-29Facility Test Calls

Table 6-5. System Tone Identification Numbers

Number Description

00 Null tone

01 Dial tone

02 Reorder tone

03 Alert tone

04 Busy tone

05 Recall dial tone

06 Confirmation tone

07 Internal call waiting tone

08 Ringback tone

09 Special ringback tone

10 Dedicated ringback tone

11 Dedicated special ringback tone

12 Touch tone 1

13 Touch tone 2

14 Touch tone 3

15 Touch tone 4

16 Touch tone 5

17 Touch tone 6

18 Touch tone 7

19 Touch tone 8

20 Chime

21 350 Hz

22 440 Hz

23 480 Hz

24 620 Hz

25 2025 Hz

26 2225 Hz

27 Counter

Continued on next page

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Additional Maintenance Procedures

Page 6-30Facility Test Calls

28 External call waiting

29 Priority call waiting

30 Busy verification

31 Executive override/intrusion tone

32 Incoming call identification

33 Dial zero

34 Attendant transfer

35 Test calls

36 Recall on don’t answer

37 Audible ring

38 Camp-on recall

39 Camp-on confirmation

40 Hold recall

41 Hold confirmation

42 Zip tone

43 2804 Hz

44 1004 Hz (-16db)

45 1004 Hz (0 db)

46 404 Hz

47 Transmission test sequence 105

48 Redirect tone

49 Voice signaling tone

50 Digital milliwatt

51 440 Hz + 480 Hz

52 Music

53 Transmission test sequence 100

54 Transmission test sequence 102

55 Laboratory test tone 1

Table 6-5. System Tone Identification Numbers — Continued

Number Description

Continued on next page

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Additional Maintenance Procedures

Page 6-31Preventive Maintenance

Preventive Maintenance

The following preventive maintenance procedures should be followed when

visiting customer sites. The chart that follows shows a sample of the Preventive

Maintenance Log. Whenever you complete a preventive maintenance procedure,

be sure to fill in the information on the log form before you leave the customer’s

premises.

Air Filters

Air filters should be inspected annually. If a filter is dirty or clogged, first tap it on

the ground. If the filter is still dirty or clogged, then wash it with warm water and a

mild detergent. A vacuum cleaner can be used if one is available. If there is no

facility for washing or vacuuming the air filter, then replace the filter. Refer to

‘‘CABINET (Cabinet Sensors)’’ maintenance documentation for information on air

filters and fans.

56 Laboratory test tone 2

57 Disable echo supervision dial tone

58 7 seconds of answer tone

59 4 seconds of answer tone

60 Restore music (or silence)

61 Warning tone

62 Forced music tone

63 Zip tone (first of 2 sent)

64 Incoming call ID (first of 2 sent)

65 Tone on hold

66 CO dial tone

67 Repetitive confirmation tone

68 Conference/bridging tone

Table 6-5. System Tone Identification Numbers — Continued

Number Description

Continued on next page

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Additional Maintenance Procedures

Page 6-32Preventive Maintenance

Tape Drive

The head and capstan on the tape drive of the SPE should be cleaned every

three months. Abrasive particles from worn tape and environmental debris can

cause loss of information and services. The procedure for cleaning the tape drive

is described in the section on TAPE in Chapter 9, ‘‘ABRI-PORT (ASAI ISDN-BRI

Port)’’.

Batteries

The backup batteries in the power distribution unit in the bottom of the cabinet

should be replaced every four years or whenever a POWER alarm that indicts the

condition of the batteries is logged. Systems with an uninterruptible power

supply (UPS) may not be equipped with backup batteries.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Additional Maintenance Procedures

Page 6-33Preventive Maintenance

Date equipment installed: ________________________

Post this form with the equipment.

1. Inspect annually; clean or replace

2. Clean every three months

3. Replace every 4 years

PREVENTIVE MAINTENANCE LOG

DEFINITY ECS

Air Filters1Scheduled

Date Date

Completed Completed

By Scheduled

Date Date

Completed Completed

Single-carrier cabinet

Multi-carrier cabinet

Tape Head/Capstan2Scheduled

Date Date

Completed Completed

By Scheduled

Date Date

Completed Completed

Battery Packs3Scheduled

Date Date

Completed Completed

By Scheduled

Date Date

Completed Completed

Single-carrier cabinet

Multi-carrier cabinet

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Additional Maintenance Procedures

Page 6-34Analog Tie Trunk Back-to-Back Testing

Analog Tie Trunk Back-to-Back

Testing

The TN760 circuit pack can be configured for back-to-back testing (also known

as connectivity testing) by making translation and cross-connect changes. This

testing configuration allows for the connection of Tie Trunks back-to-back in the

same switch to verify the operation of Tie Trunk ports. The tests can be

performed in either the E&M or simplex modes. (Refer to

DEFINITY

Communications System Generic 1 and Generic 3 Installation and Test,

555-230-104, for instructions on how to make connections at the cross-connect

field).

E&M Mode Test Procedure

1. At the administration terminal, enter list configuration trunks to

determine which ports are assigned on the Tie Trunk circuit pack.

2. Enter display dialplan command to determine the Trunk Access Code

(TAC) format.

3. Enter display port xxx for all ports defined in Step 1. This displays the

trunk groups of which the ports are members. See Chapter 5,

‘‘Responding to Alarms and Errors’’ for details of how to remove and

replace port circuit packs.

4. Insert the circuit pack back into the slot.

5. Enter display trunk xxx p for each trunk group identified in Step 3. This

command displays the specified trunk group on the administration

terminal screen and prints a hard copy on the printer. Save this data for

later use.

6. Remove all members defined by these ports from the trunk group(s) using

the change trunk xxx command.

7. Remove the Tie Trunk circuit pack from the carrier slot.

8. Set the dip (option) switches for each of the two ports to be tested on the

Tie Trunk circuit pack to “E&M mode” and “unprotected.”

9. Enter add trunk n to add a new (test) trunk group. Then enter information

for the following fields:

Group Type tie

TAC Use trunk access code obtained from dial

plan

Trunk Type (in/out) wink/wink

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Additional Maintenance Procedures

Page 6-35Analog Tie Trunk Back-to-Back Testing

10. Locate the Tie Trunk port terminal connections at the cross-connect field.

Consult the appropriate table below for either 110-type or 66-type

hardware.

11. At the cross-connect field, disconnect outside trunk facilities from the Tie

Trunk ports and mark the disconnected wires for reconnecting the Tie

Trunk ports to their normal configuration later. The D Impact Tool

(AT-8762) is required to perform this step.

12. Use jumper wires (DT 24M-Y/BL/R/G and DT 24P-W/BRN) and the D

Impact Tool to connect wiring between the two ports assigned in Step 9 at

the cross-connect field. For example, if the two ports on the Analog Tie

Trunk circuit pack are port 1 and 2, connect the wirings as shown below:

13. Check all wirings to verify good connections between the two test ports.

14. Place a call from one voice terminal to another voice terminal using the Tie

Trunk ports assigned. Dial TAC and extension. For example, if TAC of Tie

Trunk group is 110 and station number is 5012, then dial 110 5012. If the

call cannot be made, either one of these ports could be defective. There

are four ports on the TN760. Try different combinations to determine

defective ports.

15. If there is a defective port on the circuit pack, try to switch to an unused

port. If all ports are normally used, then replace the circuit pack.

16. Disconnect the jumpers between two ports. Then use administration

terminal and trunk printouts to restore all trunk group changes to normal

values.

Port Assign two of the ports from the tie trunk.

Mode E&M for both ports

Type Specify one port as t1 standard and other

port as t1 compatible.

Port 1

(t1 stan)

(E & M)

Port 2

(t1 comp)

(E & M)

T1 connected to T12

R1 “R12

T11 “ T2

R11 “ R2

E1 “ M2

M1 “ E2

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Additional Maintenance Procedures

Page 6-36Analog Tie Trunk Back-to-Back Testing

Table 6-6. Carrier Lead Appearances MDF

110 Connecting

Block Terminals CO Trunk TN747 Tie Trunk TN760

1T1T1

2R1R1

3 T11

4R11

5E1

6M1

7T2T2

8R2R2

9 T12

10 R12

11 E2

12 M2

13 T3 T3

14 R3 R3

15 T13

16 R13

17 E3

18 M3

19 T4 T4

20 R4 R4

21 T14

22 R14

23 E4

24 M4

25 T5

26 R5

Continued on next page

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Additional Maintenance Procedures

Page 6-37Analog Tie Trunk Back-to-Back Testing

Simplex Mode Test Procedure

1. Repeat Steps 1 through 7 of the E&M Mode Test Procedure.

2. Set the dip (option) switches for each of the two ports to be tested on the

Tie Trunk circuit pack to simplex mode.

31 T6

32 R6

37 T7

38 R7

43 T8

44 R8

Table 6-6. Carrier Lead Appearances MDF — Continued

110 Connecting

Block Terminals CO Trunk TN747 Tie Trunk TN760

Continued on next page

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Additional Maintenance Procedures

Page 6-38Terminating Trunk Transmission Testing

3. Enter add trunk n to add a new (test) trunk group. Then enter information

for the following fields:

4. Locate the Tie Trunk port terminal connections at the cross-connect field.

Consult the appropriate table above for either 110-type or 66-type

hardware.

5. At the cross-connect field, disconnect outside trunk facilities from the

Analog Tie Trunk ports and mark the disconnected wires for later when the

Tie Trunk ports are placed back into normal operation. The D Impact Tool

(AT-8762) is required to perform this step.

6. Use jumper wires (DT 24M-Y/BL/R/G) and the D Impact Tool to connect

wiring between the two ports assigned in Step 4 at the cross-connect field.

For example, if the two ports on the Analog Tie Trunk circuit pack are ports

1 and 2, connect the wirings as shown below:

7. Repeat Steps 13 through 16 of the E & M Mode Test Procedure.

Terminating Trunk Transmission

Testing

The Terminating Trunk Transmission (TTT) (non-interactive) feature provides for

extension number access to three tone sequences that can be used for trunk

transmission testing from the far end of the trunks.

Group Type tie

TAC Use trunk access code obtained from dial

plan.

Trunk Type (in/out) wink/wink

Port Assign two of the ports from the tie trunk.

Mode simplex

Type type 5

Port 1 connected to Port 2

(type 5) (type 5)

(simplex) (simplex)

T1 connected to T12

R1 “R12

T11 “ T2

R11 “ R2

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Additional Maintenance Procedures

Page 6-39Removing and Restoring Power

The three test types should have extension numbers assigned on the

Maintenance-Related System Parameters Form.

Test Type 100:___ Test Type 102:___ Test Type 105:___

Test Type 100 provides:

■5.5 seconds of 1004 Hz tone at 0dB

■Quiet until disconnect; disconnect is forced after one minute

Test Type 102 provides:

■9 seconds of 1004 Hz tone at 0dB

■1 second of quiet

■This cycle is repeated until disconnect; disconnect is forced after 24

hours.

Test Type 105 provides:

■9 seconds of 1004 Hz at -16dB

■1 second of quiet

■9 seconds of 404 Hz at -16dB

■1 second of quiet

■9 seconds of 2804 Hz at -16dB

■30 seconds of quiet

■1/2 second of Test Progress Tone (2225 Hz)

■Approximately five seconds of quiet

■Forced disconnect

Removing and Restoring Power

!CAUTION:

Error Log information is lost when the PPN cabinet is powered down. If this

information is to be saved, enter the reset system 4 command. The

command will take several minutes to complete, and will result in saving of

the Error Log to the MSS.

!CAUTION:

Before powering down a cabinet or carrier that contains DEFINITY AUDIX

circuit packs (TN566 and TN2169), you must first power down the AUDIX

unit to avoid damage to the AUDIX software Instructions for powering down

this unit appear on the circuit pack and in DEFINITY AUDIX documentation.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Additional Maintenance Procedures

Page 6-40Automatic Transmission Measurement System (ATMS)

!CAUTION:

If there is an alarm or problem suspected on the Tape or Disk Circuit packs

do not save translations or announcements to the affected device. If there is

an alarm or problem suspected with the Host Adapter circuit, do not save

data to either MSS device. Saving data under these circumstances can

destroy good copies of the file. If necessary, obtain a spare tape cartridge

to save data.

To remove power to the cabinet:

1. If the cabinet is the PPN, execute save translation and save

announcement unless a tape drive problem is active.

2. Set the Emergency Transfer switch(es) in the affected cabinet to ON. In

the PPN these are located on the SYSAM circuit pack(s). Set both in a

system with duplicated SPE. In an EPN the switch is located on the EPN

Maintenance circuit pack. This locks the system in the emergency transfer

mode until the trouble is cleared.

3. Depending on which type of cabinet you are powering down, do one of

the following:

■In an AC-Powered multi-carrier cabinet, set the circuit breaker to

OFF at the Power Distribution Unit.

■In a DC-Powered multi-carrier cabinet, turn off the DC Power

supply.

■In an AC-Powered single-carrier cabinet stack, turn off the power in

each affected carrier individually. The ON/OFF switch is located at

the back of the carrier behind the WP-91153 Power Unit.

■In a DC-Powered single-carrier cabinet stack, turn off the power in

each affected carrier individually. The ON/OFF switch is located at

the back of the carrier behind the 676B Power Unit.

4. Power is restored by reversing the action taken above.

When restoring power to a PPN, the system will reboot. When restoring

power to an EPN, the EPN will under go a restart. This process is

described under EXP-PN in Chapter 9, ‘‘ABRI-PORT (ASAI ISDN-BRI

Port)’’.

If a powered down carrier contains a 676B Power Unit, the 676B must

have been powered down for at least 10 seconds for the unit to restart.

Automatic Transmission

Measurement System (ATMS)

The ATMS performs transmission tests on analog trunks to determine whether

they are performing satisfactorily. The switch automatically originates test calls

from an Originating Test Line (OTL), over the trunks to be tested, to a Terminating

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Additional Maintenance Procedures

Page 6-41Automatic Transmission Measurement System (ATMS)

Trunk Line (TTL) on the switch at the far end of the trunk. Several different

measurements of noise and attenuation are made and compared to administered

thresholds. Test measurements can be viewed in the form of detailed or

summary reports which are described below.

ATMS test calls can be initiated on demand from the management terminal, or

automatically by ATMS Trunk Test Schedules. For complete details on how to set

up ATMS Trunk Test Schedules, see Chapter 4 of

Generic 3 V2 Implementation,

555-230-653

. Demand tests are run with the test analog-testcall command

which is described below.

Trunk groups can be administered to respond in different ways when a trunk fails

to perform within the administered thresholds. Alarms and errors may be logged,

and the trunk can be automatically busied out. When a trunk fails an

unacceptable threshold twice, the system will busy it out if the trunk group is so

administered and doing so will not exceed an administered limit (25, 50, 75, or

100% of the members in the group). This limit is not applied to later busyouts

caused by other factors. Trunks can be manually returned to service by

changing the thresholds and running a demand test or by using the release

command.

ATMS Requirements

ATMS tests utilize the analog port (port number 01) on a TN771

Maintenance/Test circuit pack. Each PPN contains one TN771. Depending on

system configuration, each EPN may also contain one TN771. Multiple TN771s

allow up to 3 concurrent test calls.

AMTS tests are designed to operate on the types of trunks found in the US, and

the TN771 analog port is Mu-law companding only. The tests will not be useful in

all environments.

For ATMS tests to run, several administrative prerequisites must be met. The

following list shows the field entries necessary to enable testing.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Additional Maintenance Procedures

Page 6-42Automatic Transmission Measurement System (ATMS)

Running ATMS Tests

(Test Analog-Testcall Command)

ATMS test calls can be originated either on demand or according to the ATMS

Test Schedule. Test schedules are set up with test-schedule commands which

are described in

DEFINITY Enterprise Communications Server Release 5.4

Administration and Feature Description

Demand test calls are originated by the test analog-testcall command. You can

specify testing of an entire trunk group, an individual trunk, or all trunks on a

single circuit pack. Trunks can be addressed by either group/member numbers

or circuit pack/port locations. The type of test call, the number of the testing line

on the far-end switch and various other parameters must be administered on the

trunk group form before the command can execute.

Table 6-7. ATMS Administration

Form Field Entry/Remarks

System-parameters

customer options ATMS? y (You must logoff/login in order for

changes on this form to take effect.)

Station Extension At least one TN711 analog port must

be assigned.

Port Number UUCSS01 where UUCSS is the

location of any TN771

Port Type COR 105TL

The number of a COR that has

testing enabled (see next form)

Class of Restriction Facility Access Trunk Test y

Trunk Group Maintenance Tests?

ATMS Thresholds (page 4

of form)

This page is used to specify

performance thresholds, the type

and access number of the far-end

TTL, and system response to test

failures.

Hunt Group (Optional, for incoming test calls) If

the system has several TN771s, you

can use this form to make up a hunt

group of TTLs so that one extension

can be used for the whole pool.

ATMS Trunk Test

Schedule (Optional) To set up a test schedule,

see Chapter 4 of

Generic 3 V2

Implementation,

555-230-653

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Additional Maintenance Procedures

Page 6-43Automatic Transmission Measurement System (ATMS)

Normally you should invoke only the full or supervision tests. The other options

are provided mainly for use in setting up an ATMS schedule. Which tests are run

depend on the type of TTL at the far end to which the test call is made. The

following table shows which tests are run for each type of TTL. Command syntax

is as follows:

test analog-testcal

trunkgroup#/| member#| port UUCSSpp | boardUUCSS

[full | supervision | no-selftest | no-return-loss | no-st-or-rl]

[repeat#][schedule]

Input Parameters

Different TTLs have different measurement capabilities and you will need the

following information about specific TTL types. This table does not include the

self-test nor does it distinguish between measurements for different test tone

levels.

trunk

addresses You can specify a single trunk or several trunks by using

trunk, port, or board addresses. These parameters are

described in the introduction to Chapter 8, ‘‘Maintenance

Commands’’. If you enter a trunk group number without a

member number, all members of the group are tested.

full This executes the most comprehensive test call available

using the administered test set type.

“Full“is the default.

supervision This test takes about 10 seconds and simply confirms the

presence of testing capability at the far end.

no-selftest This executes the full test, but skips self test sequences.

This saves about 20 seconds on the type 105 transmission

test and has no effect on type 100 and 102 transmission

tests.

no-return-loss This executes the full test, but skips return loss sequences.

This saves about 20 seconds on the type 105 transmission

test and has no effect on type 100 or 102 transmission tests.

no-st-or-rl This executes the full test, but skips the self test and the

return loss sequences. This saves about 40 seconds on the

type 105 transmission test and has no effect on type 100 or

102 transmission tests.

repeat # This specifies repeating the tests up to 99 times. The default

is a single run of the tests.

schedule This qualifier brings up a form for scheduling execution of

the test at a later time. This is not the same as setting up an

ATMS Test Schedule, which is described above.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Additional Maintenance Procedures

Page 6-44Automatic Transmission Measurement System (ATMS)

Test Call Results

If the test call successfully completes, and all trunks test within administered

thresholds for marginal and unacceptable performance, then a PASS result is

returned. If the test aborts or fails, an error code indicating the cause is returned.

The error codes are explained in the CO-TRK and TIE-TRK sections of Chapter 9,

‘‘ABRI-PORT (ASAI ISDN-BRI Port)’’. When the trunk is being used for call

1. Return Loss includes Singing Return Loss High Frequency, Singing Return Loss Low Frequency, and

Echo Return Loss.

Table 6-8. Measurement Capability by TTL Type

Terminating Test Line Type

Test

105 Type

with Return

Loss

105 Type

without

Return Loss

High-level/

Low-level

Tone Source 100 Type 102 Type

1004 Hz Loss

Far-End to Near-End xx xxx

1004 Hz Loss

Near-End to Far-End xx

404 Hz Loss Far-End

to Near-End xx x

404 Hz Loss

Near-End to Far-End xx

2804 Hz Loss

Far-End to Near-End xx x

2804 Hz Loss

Near-End to Far-End xx

C-Message Noise

Near-End xx xx

C-Message Noise

Far-End xx

C-Notched Noise

Near-End xx

C-Notched Noise

Far-End xx

Return Loss1

Near-End xx xx

Return Loss Far-End

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Additional Maintenance Procedures

Page 6-45Automatic Transmission Measurement System (ATMS)

processing, the test aborts. When the trunk is already being tested by

maintenance software, the test is queued and run when the maintenance activity

finishes.

Measurement data gathered by analog testcalls can be retrieved with the list

testcalls command which is described below. Which measurements are made

and recorded depends on which type of test is specified and the capabilities of

the far-end TTL.

Screen 6-1 shows a typical result for test analog-testcall trunk 60

Screen 6-1. Test Results for test analog-testcall trunk 60

Output Fields

Port The physical location of the port supporting the trunk

being tested. The format is UUCSSpp where UU is the

cabinet number, C is the carrier letter, SS is the circuit

pack slot, and pp is the port circuit number.

Maintenance

Name The name of the maintenance object tested, TIE-TRK

or CO-TRK.

Alt. Name The trunk group number and member number of the

trunk being tested.

Test Number ATMS tests are numbered 844 through 848.

Result If the test call successfully completes, and all trunks

test within administered thresholds for marginal and

unacceptable performance, then a PASS result is

returned. If measurements fall outside the thresholds,

the test fails. The trunks group can be administered to

log errors and alarms, and to busy out the failed trunk.

If the test call cannot be completed, an ABORT is

returned.

test analog-testcall trunk 60 SPE B

TEST RESULTS

Port Maintenance Name Alt. Name Test No. Result Error Code

02B1901 TIE-TRK 060/001 845 PASS

02B1902 TIE-TRK 060/002 845 PASS

02B1903 TIE-TRK 060/003 845 PASS

02B1904 TIE-TRK 060/004 845 ABORT 1004

02B1905 TIE-TRK 060/005 845 PASS

02B1906 TIE-TRK 060/006 845 ABORT 1004

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Additional Maintenance Procedures

Page 6-46Automatic Transmission Measurement System (ATMS)

ATMS Reports (List Testcall Command)

The list testcalls command produces detailed and summary reports of

measurements made by the Automatic Transmission Measurement System

(ATMS). Measurement reports contain data on trunk signal loss, noise, singing

return loss, and echo return loss, and are used to determine the quality of trunk

lines. The system maintains a database with the results of the last test for each

trunk. System resets clear all transmission test data, and ATMS measurements

are not backed up by the Mass Storage System.

ATMS parameters are administered on page 4 of the trunk group form. These

include thresholds for marginal and unacceptable performance. On the screen

display, measurements that exceed the marginal threshold are highlighted.

Measurements that are exceed the unacceptable level appear flashing,

indicating unusable trunks. Trunk groups can be administered to log errors and

alarms, and busyout the failed trunk in response to such results.

The detailed report lists measurements for each trunk group member. The

summary reports lists trunk groups as a whole. Which measurements are

displayed depends on what type of test, if any, was last run on the trunk, and the

capabilities of the TTL on the switch at the far end of the trunk. See the preceding

description of the test analog-testcall command. A blank line indicates that no

test data is available for that trunk or group.

The number of pages of each report is dependent upon the selection criteria and

the number of outgoing trunks in the system. About 10 measurements can be

listed on a page on the administration terminal, or about 50 measurements can

be listed on a printer. By default, reports list all measurements. Filtering can be

used to limit the output. For example, the report can be set up to print only failed

measurements.

The syntax of the command is as follows:

list testcalls detail | summary

[port UUCSSpp]

[grp group#] [to-grpgroup#]

[mem member#] [to-memmember#]

[resultresultID> | not-resultresultID]

[count#] [print | schedule]

Error Code This numerical code indicates the reason for a failure

or abort. The codes are explained in the CO-TRK and

TIE-TRK sections of Chapter 9, ‘‘ABRI-PORT (ASAI

ISDN-BRI Port)’’.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Additional Maintenance Procedures

Page 6-47Automatic Transmission Measurement System (ATMS)

Input Parameters - List Testcall Command

ATMS Summary Reports

The ATMS Summary Report summarizes, on a trunk group basis, the collective

results of the latest ATMS tests performed on each trunk group. By interacting

with the trunk group form, it highlights out-of-tolerance measurements. Marginal

trunks are highlighted, and unusable trunks blink, allowing you to quickly identify

out-of-tolerance or unusable trunks. Screen 6-2 shows a typical summary report.

detail This qualifier specifies a detailed report that shows each measurement

made for each trunk.

summary This qualifier specifies a report that shows totaled results of ATMS tests

for trunk groups as a whole.

grp # This qualifier specifies a report showing measurements for a specific

trunk group. When used with to-grp, this option specifies the starting

trunk group in a range.

to-grp This qualifier specifies a report showing measurements for all trunk

groups from 1 up to the trunk group number entered. When used with

grp, this is the ending trunk group in a range.

mem Used with grp, this qualifier specifies a report showing measurements for

a specific trunk group member. When used with to-mem, this is starting

trunk group member in a range.

to-mem Used with grp, this qualifier specifies display of measurements for all

trunk group members from 1 up to the specified trunk group member

entered. When used with mem, this is the ending trunk group member in

a range.

port This qualifier specifies display of measurements for the trunk assigned to

a specific port circuit.

result Only measurements that match the specified result are displayed. Result

IDs include pass, marg, fail, and numerical abort codes.

not-result Only measurement results that do not match the specified result are

displayed.

count number This qualifier limits the total number of records displayed.

print With this qualifier, the command executes immediately (if resources are

available) and sends output both to the screen and to a printer

connected to the terminal where the command was entered.

schedule With this qualifier, a scheduling form is displayed which allows you to

specify a start time for the command. The command is placed in the

queue and, when executed, sends the output to the system printer.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Additional Maintenance Procedures

Page 6-48Automatic Transmission Measurement System (ATMS)

Screen 6-2. Summary Report Screen

Output Fields - ATMS Summary Report

Trk Grp Num Results for each trunk group are listed by trunk group number.

Trunk group number Only outgoing or two-way analog trunks are

listed.

Num Of Trks The number of members in the trunk group.

Last Test Date The date of the oldest measurement in the trunk group.

Last Test Time The time of the oldest measurement in the trunk group.

Trunks Passed

Transm Test The number of trunks that have passed the trunk transmission

tests.

Trunks Failed

Marginal Threshld The number of trunks that performed outside the marginal

threshold, but not the unacceptable threshold, as defined on the

trunk group form.

Trunks Failed

Unaccept Threshld The number of trunks that performed outside the unacceptable

threshold, as defined on the trunk group form.

Trks In-Use The number of trunks that were in use at the time of testing. Abort

codes for trunk-in-use are 1000 and 1004.

Trks Not Test The number of trunks that were not tested due to error conditions

other than trunk-in-use. Abort codes are given in the detailed

report.

ATMS MEASUREMENT SUMMARY REPORT

Trunks Trunks Trunks

trk Num Last Last Passed Failed Failed Trks Trks Busied

Grp of Test Test Transm Marginal Unaccept In- Not Out

Num Trks Date Time Test Threshld Threshld Use Test Trunks

1 10 10/04/91 15:15 10 0 0 0 0 0

10 10 10/04/91 15:40 10 0 0 0 0 0

20 5 10/04/91 16:00 5 0 0 0 0 0

30 30 0 0 0 0 30 0

40 20 10/04/91 16:15 20 0 0 0 0 0

50 10 10/04/91 16:40 10 0 0 0 0 0

60 3 10/04/91 16:55 0 0 0 0 0 3

78 10 10/04/91 17:05 8 0 0 1 0 1

83 15 10.04/91 17:20 15 0 0 0 0 0

105 100 10/04/91 17:40 100 0 0 0 0 0

125 2 10/04/91 19:30 0 0 0 0 0 2

350 10 10/04/91 19:40 10 0 0 0 0 0

500 55 10/04/91 19:55 55 0 0 0 0 0

650 1 10/04/91 21:00 1 0 0 0 0 0

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Additional Maintenance Procedures

Page 6-49Automatic Transmission Measurement System (ATMS)

ATMS Detail Report

This report is divided into two sections. The upper section lists the trunk group,

trunk type, trunk vendor, TTL type, and the user-defined threshold values

administered on page 4 of the trunk group form. The lower section lists the most

recent set of measurements for each member of the trunk group selected for the

report. Measurements that exceed the marginal threshold, but not the

unacceptable threshold, are highlighted. Measurements that exceed the

unacceptable threshold blink, identifying unusable trunks. When a marginal or

unacceptable measurement is located, scan the top section to find out how far

the measurement deviates from its defined threshold.

Output Fields - ATMS Detail Report

Measurements are made in both directions, near to far end, and far to near end.

For each measurement, there are 2 columns on the lower part of the report, “NE”

for near end, and “FE” for far end. These refer to the destination end for that

measurement.

Busied Out Trunks The number of trunks that were busied out in response to test

failures. These may be caused by hardware problems, incorrect

threshold values, and so on.

Group The trunk group number selected.

Type The trunk group type.

Vendor The vendor of this trunk group.

ATMS TRUNK MEASUREMENTS

Group: 78 Type: co Vendor: AT&T TTL Type: 105-w-rl

THRESHOLD VALUES

Loss dev at

1004Hz-loss 404Hz 2804Hz C-msg C-ntch SRL SRL

Min Max - + - + Noise Noise LO HI ERL

Marginal -2 21 9 9 9 9 55 74 0 0 0

Unacceptable -2 21 9 9 9 9 55 74 0 0 0

Trk Test Test Test -16dBm OdBm

Mem Date Time Rslt FE NE FE NE FE NE FE NE FE NE FE NE FE NE FE NE FE NE

1 10/04 14:25 pass 7 7 7 7 -2 -2 7 7 15 28 34 34 8 16 11 16 11 17

2 10/04 14:26 1920

3 10/04 14:27 1000

4 10/04 14:28 pass 7 7 7 7 -2 -2 7 7 15 29 38 34 8 16 11 15 11 16

5 10/04 14:29 pass 7 7 7 7 -2 -2 6 6 15 35 34 34 8 6 9 6 10 7

6 10/04 14:30 pass 7 7 7 7 -2 -2 6 6 15 26 34 34 8 16 9 13 10 16

7 10/04 14:31 pass 7 7 7 7 -2 -2 7 7 15 30 34 34 8 16 9 11 10 13

8 10/04 14:32 pass 6 6 6 6 -2 -2 6 6 15 25 34 34 10 17 11 16 12 17

9 10/04 14:33 pass 6 6 7 7 -1 -1 7 7 15 25 34 34 8 15 9 13 10 16

10 10/04 14:34 pass 6 6 7 6 -1 -1 7 7 15 36 34 35 8 6 9 6 10 7

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Additional Maintenance Procedures

Page 6-50Automatic Transmission Measurement System (ATMS)

TTL Type The type of terminating test line on the switch at the far end of the trunk

to which the test call was made.

Threshold

Values The list of marginal and unacceptable threshold values for each type of

measurement. These are defined on the trunk group form.

Trk Mem The trunk member number.

Test Date The month and day this trunk was last tested.

Test Time The time of day this trunk was last tested.

Tst Rslt The results of the trunk transmission test as follows:

pass

The test call completed successfully and trunk performance was

satisfactory

marg

Trunk measurements exceeded the marginal threshold, but not the

unacceptable.

fail

Trunk measurements exceeded the unacceptable threshold.

xxxx

A numerical error code indicates the reason for an aborted test call. The

codes are explained in the CO-TRK and TIE-TRK sections of Chapter 9,

‘‘ABRI-PORT (ASAI ISDN-BRI Port)’’.

blank

A blank line indicates that no measurements have been made on this

trunk since the database was last initialized.

1004Hz-los

s Min Far-to-near and near-to-far measurements of 1004-Hz loss from low-level

tone.

1004Hz-los

s Max Far-to-near and near-to-far measurements of 1004-Hz loss at 0 dBm.

Loss dev

at 404Hz These low-frequency transmission tests measure maximum positive and

negative deviation of +9 and -9 dB from the 1004-Hz loss

measurements.

Loss dev

at 2804Hz These high frequency transmission tests measure maximum positive and

negative deviation of +9 and -9 dB from the 1004-Hz loss

measurements.

C-msg

Noise Maximum noise interference noise) terminating on a voice terminal within

the voice-band frequency range (500 to 2500 Hz). The measurement

ranges from 15 to 55 dBrnC (decibels above reference noise).

C-ntch

Noise Maximum signal-dependent noise interference on a line between 34 and

74 dBrnC.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Additional Maintenance Procedures

Page 6-51Automatic Transmission Measurement System (ATMS)

ATMS Measurement Analysis

ATMS compares the results of the test measurements with threshold values to

identify trunks that are out of tolerance or unusable. Once a defective circuit has

been pinpointed, a proper analysis must be made to determine the appropriate

action to take on the facility failures. Although there is no “right” procedure for

every situation, the following items will help in troubleshooting problems:

■If a circuit fails an ATMS transmission test, it does not necessarily mean

the trouble is in the facility itself. The problem could be caused by a faulty

test line, bad switch path, or a variety of other reasons.

■If a circuit fails a transmission test but successfully passes a supervision

test, some of the items mentioned above are probably not at fault, since

proper call routing and circuit continuity are required for successful of a

supervision test.

■If several circuits in the same group are failing, this could indicate the

failure of some common equipment (such as a carrier system, test line, or

cable) or erroneous information in the threshold tables.

■When a test call can be successfully made, but not completed, either the

OTL or TTL is probably defective. For this failure type, further ATMS

testing might be seriously impaired, but the system is not otherwise

affected.

■If a test call cannot be successfully made, the wrong number might have

been dialed, the far-end device might be busy, the far-end device is

defective, or there is a serious trunk failure obstructing the call.

SRL-LO Singing return loss from 0 to 40 dB between the sum of the circuit

(repeater) gains and the sum of the circuit losses. SRL-LO occurs most

often in the frequency range of 200 to 500 Hz.

SRL-HI Singing return loss from 0 to 40 dB between the sum of the circuit

(repeater) gains on a circuit and the sum of the circuit losses. SRL-HI

occurs most often in the frequency range of 2500 to 3200 Hz.

ERL Echo return loss from 0 to 40 dB between the level of signal strength

transmitted and the level of signal strength reflected. ERL occurs most

often in the frequency range of 500 to 2500 Hz

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Additional Maintenance Procedures

Page 6-52Automatic Transmission Measurement System (ATMS)

LED Indicators

Page 7-1Terminal Alarm Notification

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

7LED Indicators

If a maintenance object in the system begins to fail some of the periodic tests,

the system automatically generates an alarm. This alarm indicates to

maintenance personnel that action is required to restore the system to a normal

condition. The system identifies three levels of alarms:

■Major Alarms — Failures that cause critical degradation of service and

require immediate attention.

■Minor Alarms — Failures that cause some degradation of service, but do

not render a crucial portion of the system inoperable. This condition

requires action, but its consequences are not immediate. Problems might

be impairing service to a few trunks or stations or interfering with one

feature across the entire system.

■Warning Alarms — Failures that cause no significant degradation of

service or failures in equipment external to the system. Warning alarms

are not reported to the attendant console or INADS.

Alarms are communicated to the system users and technicians by entries in the

Alarm Log and the lighting of LEDs located on the attendant console, on all

circuit packs in the switch cabinets, and, optionally, on customer-designated

voice terminals.

Terminal Alarm Notification

Terminal Alarm Notification is an optional feature which displays several types of

alarms on voice terminals with administered feature buttons or the attendant

console. A maximum of ten digital and/or hybrid voice terminals may be used.

When an alarm occurs, the green status LED associated with the assigned

button will be in a steady state. The lamp may be turned off by pressing the

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

LED Indicators

Page 7-2Attendant Console LEDs

button associated with the lighted alarm lamp. If the lamp is turned off, and the

alarm has not been resolved by the time maintenance reschedules testing, the

green status LED will resume its steady state. The following alarms are

displayed:

Attendant Console LEDs

The console has two red LEDs, labeled “ALM” and “ACK.” The ALM LED lights

steadily when there is a Major or Minor alarm at the switch cabinet. The ACK LED

lights steadily if the alarm has been successfully reported to INADS. If the system

is unable to report the alarm to INADS, the LED flashes; this signals the attendant

to call INADS and report the alarm.

ac-alarm Administered Connection Alarm: a locally administered

connection (ADM-CONN) has a Major, Minor, or Warning

alarm active.

pr-awu-alm Auto Wakeup Journal Printer Alarm: the automatic wakeup

journal printer has a Major, Minor, or Warning alarm active.

ds1-alarm DS1 Facility Alarm: a DS1-BD has an off-board Major, Minor,

or Warning alarm active.

trk-ac-alm Facility Access Alarm: The facility access trunk test feature

is activated.

major-alrm Major Alarm: The system has logged a Major Alarm.

mj/mn-alrm Major/Minor Alarm: The system has logged a Major or Minor

Alarm.

pr-pms-alm PMS Printer: The Property Management System printer has

a Major, Minor, or Warning alarm active.

rs-alert Reset-Alert: reset system 2 or 3 has been performed.

cdr1-alrm Call Detail Recording Alarm: The Primary CDR Link has a

Major, Minor, or Warning alarm active.

cdr2-alrm Call Detail Recording Alarm: The Secondary Link has a

Major, Minor, or Warning alarm active.

pr-sys-alm System Printer Alarm: The System Printer (SYS-PRNT) has a

Major, Minor, or Warning alarm active.

pms-alarm The Property Management System has a Major, Minor or

Warning alarm active.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

LED Indicators

Page 7-3Circuit Pack LEDs

Circuit Pack LEDs

Each circuit pack typically has three LEDs on the front panel visible at the front of

the carrier, there are some exceptions to this (for example DS1CONV circuit

pack) that are covered later in this section. On most circuit packs, the LEDs

indicate the following when lit. Exceptions to these indications are explained in

subsequent sections.

LED Alarms without Alarm Log Entry or with

Error Type 1

Whenever the system or a part of the system is reset, all affected circuit packs

will briefly light their red and green LEDs as they are initialized. Upon power-up

of a newly installed system, several alarm indicators may remain lit until the

circuit packs are administered. These alarms should be ignored until

administration is completed.

During routine or demand testing of Mass Storage System components, the red,

green and yellow LEDs on the MSSNET, TAPE, and DISK circuit packs all light

temporarily. This is normal and does not indicate a problem.

After a circuit pack has been initialized, a lit red LED should be accompanied by

an alarm in the Alarm Log. A single fault can sometimes light alarm LEDs on

several circuit packs, as in the following examples.

■A TDM bus problem may cause several port circuit packs to display red

LEDS.

■An EPN Maintenance circuit pack can prevent an Expansion Interface

circuit pack from initializing.

■Extensive interactions in the Center Stage Switch can cause multiple

alarms from single faults in DS1C, SNI and SNC circuit packs and fiber

links.

■Tone/clock problems may cause other circuit packs to report alarms.

Red Alarm The system has detected a fault in this circuit pack.

The Alarm Log should contain an on-board alarm for

this circuit pack or one of the maintenance objects

associated with it. The red LED is also lit briefly when a

circuit pack is inserted or reset. If the circuit pack

passes its initialization tests, the LED is extinguished. If

a fault is detected, it remains lit.

Green Testing The system is currently running tests on this circuit

pack as part of background maintenance or demand

testing. This LED is also lit briefly during initialization

tests when a circuit pack is inserted or reset.

Yellow Busy The circuit pack is currently in use by the system.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

LED Indicators

Page 7-4Expansion Interface Circuit Pack LEDs

■Misconnected optical fiber cables may cause several circuit packs to

alarm.

■Packet bus faults can cause several port circuit packs to display red

LEDs.

If a circuit pack has had at least five minutes to be initialized, and the red LED is

lit without an associated alarm in the Alarm Log, the circuit pack may not be in

communication with the system. This may also be the case when a circuit pack is

properly administered and present in its slot, but there is an error type 1 logged

against it. To determine if this is so, proceed as follows:

■Issue the list configuration board UUCSS command. If the system does

not detect the circuit pack, this command will return

identifier not assigned

no board.

If the documentation for the associated maintenance object gives no

special instructions for this situation, go to the next step.

■Check the Hardware Error Log for TONE-BD or TDM-BUS errors. Use the

test tdm and test tone-clock commands and use the appropriate

maintenance procedures to resolve any identified faults. If this does not

resolve the problem, go to the next step

■Reseat the suspect circuit pack.

!CAUTION:

This procedure can cause a partial or total service outage. Consult

thoroughly the documentation for the associated maintenance object

before proceeding. Observe the precautions and procedures

described above.

■Inspect the backplane connectors for bent pins.

■If the system seems to be functioning correctly, but the circuit pack in

question will not communicate with the system, replace the circuit pack.

Expansion Interface Circuit Pack LEDs

The Expansion Interface (EI) TN570 circuit pack has the standard red, green and

yellow LEDs. The red and green LEDs have the traditional meaning, where red

indicates an alarm condition, and green indicates testing in progress.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

LED Indicators

Page 7-5Maintenance Circuit Pack LEDs

The yellow LED displays various flashing patterns to provide status information

useful in isolating faults in the fiber link and other components connected to the

fiber link. Table 7-1 illustrates the EI yellow LED states.

Maintenance Circuit Pack LEDs

TN1648 System Access-Maintenance (SYSAM) and TN775 EPN Maintenance

circuit packs have seven LEDs on their front panels. The top three LEDs are the

standard group of red, green and yellow, and indicate the status of the circuit

pack. The green LED on TN775s blinks faintly once per second, indicating

continual self-testing.

The second group of three LEDs, labeled “ALARMS”, reflect maintenance

conditions throughout the system, and indicate alarms reported against other

components, as described below. On systems with duplicated SPEs, disregard

the Major, Minor, and Warning alarm LEDs on the standby SYSAM circuit pack.

Table 7-1. Expansion Interface Yellow Led Flashing Codes

LED on LED off Condition

0.1 sec 0.1 sec Fiber Out-of-Frame. This state indicates a failure of test

#989. This may be caused by absence of the opposite

end EI or Switch Node Interface, a broken or missing

fiber, or a missing lightwave transceiver on either

endpoint.

0.5 sec 0.5 sec In Frame — No Neighbor. This state corresponds to a

failure of test # 237, usually due to a failure of this EI or

of the EI or SNI at the other end of the fiber.

2 sec 0.2 sec Expansion Interface Active. This is the normal state of

an active EI that is an archangel of an Expansion Port

Network.

solid on Expansion Interface Active. This is the normal state for

an active EI that is not an EPN archangel. These include

EPN EIs connected to other EPN EIs in Direct Connect

Configurations, and EIs located in the Processor Port

Network.

solid off Expansion Interface Standby. This is the normal state for

a standby EI in systems with a duplication option.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

LED Indicators

Page 7-6Maintenance Circuit Pack LEDs

Only those on the active SYSAM are updated with the current system status. The

yellow LED that is third from the top indicates which SYSAM is active.

These LEDS are illustrated on the following page.

MAJOR (red) flashing Major Alarm against a component in

the same cabinet, (PPN for SYSAM,

and EPN for MAINT).

MAJOR (red) solid Major Alarm against a component in

another cabinet in the system.

MINOR (red) flashing Minor Alarm against a component in

the same cabinet.

MINOR (red) solid Minor Alarm against a component in

another cabinet.

WRNG (yellow) flashing Warning Alarm against a component

in the same cabinet.

WRNG (yellow) solid Warning Alarm against a component

in another cabinet.

ACK (green) on Acknowledged; alarm has been

reported to INADS.

EMERGENCY TRANSFER (red) on Emergency transfer has been

invoked. This occurs upon power-up

as well as during disabling failures.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

LED Indicators

Page 7-7Duplication Interface Circuit Pack LEDs

Figure 7-1. SYSAM and EPN Maintenance Circuit Pack LEDs

Duplication Interface Circuit Pack

LEDs

In systems with duplicated SPEs, (High Reliability and Critical Reliability), there

are two Duplication Interface UN330B circuit packs. One is located in carrier A

and one in carrier B of the PPN. Each circuit pack has four LEDs. The top three

have the traditional function of indicating the status of the pack.

The LED located at the bottom of the faceplate directly beneath the SPE Select

switch is labeled OVERRIDE. Under normal operating conditions, the SPE Select

switch is in the AUTO (center) position, and the OVERRIDE LED remains unlit.

This means that the system controls which SPE is active. System selection of the

active SPE can be manually overridden by moving the SPE Select switches from

the AUTO position to either the “A” position or the “B” position on both

Duplication Interface circuit packs. At this time, the red OVERRIDE LEDs on both

Duplication Interface circuit packs will light steadily to indicate that one SPE is

locked Active and the system is not duplicated. If both SPE Select switches are

not in the same position, the system software retains control of Active SPE

selection, and the OVERRIDE LED remains unlit. When control of the SPE

selection is returned to the system by returning the SPE Select switches on both

Duplication Interface circuit packs to the AUTO position, the OVERRIDE LED will

go dark. Forced SPE selection should be undertaken only after consulting the

appropriate sections in Chapter 9, ‘‘Maintenance Object Repair Procedures’’.

Alarm LED (red)

Test LED (green)

Busy LED (yellow)

Major alarm LED (red)

Minor alarm LED (red)

Warning alarm LED (yellow)

Acknowledgement LED (green)

Emergency Transfer control switch

ALARMS

MAJOR

MINOR

WRNG

ACK

EMERGENCY

TRANSFER

OFF ON

AUTO

Emergency transfer LED (red)

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

LED Indicators

Page 7-8Switch Node Interface LEDs

Figure 7-2. Duplication Interface Circuit Pack LEDs

Switch Node Interface LEDs

The Switch Node Interface (SNI) TN573 circuit pack has the standard red, green,

and yellow LEDs. The red and green LEDs have the traditional meaning, where

red indicates an alarm condition, and green indicates testing in progress.

The yellow LED displays various flashing patterns to provide status information

useful in isolating faults in the fiber link and other components connected to the

fiber link. Table 7-2 illustrates the SNI yellow LED states.

SPE-Select Switch

SPE-Select LED (Red)

Alarm LED (Red)

Test LED (Green)

Busy LED (Yellow)

SPE

AUTO

Override

B A

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

LED Indicators

Page 7-9DS1 CONV (TN574/TN1654) Circuit Pack LEDs

DS1 CONV (TN574/TN1654) Circuit

Pack LEDs

The TN574 and the TN1654 LEDs provide an indication of the state of the DS1

Converter and facilities, and are covered in the following sections of this

document.

TN574 Circuit Pack LEDs

Seven LEDs provide an indication of the state of the DS1 Converter (DS1 CONV)

TN574 circuit pack and the DS1 facilities. The top group has the standard red,

green and yellow LEDs. The red and green LEDs have the traditional meaning,

where red indicates an alarm condition, and green indicates testing in progress.

The four green LEDs on the bottom indicate the status of the DS1 facilities (see

following section).

Table 7-2. Switch Node Interface Yellow Led Flashing States

LED on LED off Condition

0.1 sec 0.1 sec Fiber Out-of-Frame. This state indicates a failure of test

#238, which may be caused by absence of the opposite

end EI or Switch Node Interface, a broken or missing

fiber, or a missing lightwave transceiver on either

endpoint.

0.5 sec 0.5 sec In Frame — No Neighbor. This state corresponds to a

failure of test # 237, usually due to a failure of this SNI,

or the EI or SNI at the opposite of the fiber. This

condition may also be due to a faulty Switch Node

Clock.

solid on SNI Active. This is the normal state for an active SNI.

solid off SNI Standby. This is the normal state for a standby SNI

in systems with a duplication option.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

LED Indicators

Page 7-10DS1 CONV (TN574/TN1654) Circuit Pack LEDs

The yellow LED is used to indicate the state of the Fiber Interface, the Fiber

Channel, and the DS1 channel in the following manner and order of priority.

DS1 Facility LEDs

Below the three standard LEDs on the DS1C circuit pack are four green LEDs

used to indicate whether a receive signal is present for each of the four DS1

facilities. Figure 7-3 shows which facility (A, B, C, or D) corresponds to each LED.

If a green LED is off, there is a Loss of Signal condition on the DS1 facility

associated with that LED. The presence of a signal does not guarantee that the

signal is using the correct framing format or line coding; an Alarm Indication

Signal indicating that the opposite end of the DS1C complex is out of service

may be present.

Table 7-3. DS1C Yellow Led Flashing States

LED on LED off Condition

0.1 sec 0.1 sec Fiber Out-of-Frame or Fiber Loss of Signal

0.5 sec 0.5 sec In Frame, fiber channel down. The fiber channel

communicating between the DS1C and the other fiber

endpoint (EI or SNI) is down.

1 sec 1 sec In Frame, DS1 channel down. The channel between the

two DS1Cs in the DS1C complex is down.

2 sec 0.2 sec No response from SPE. The SPE is not acknowledging

messages from the DS1C or the communications link to

the SPR is down.

solid on DS1C active. This is the normal state for an active

DS1C.

solid off DS1C standby. This is the normal state for a standby

DS1C in Critical Reliability Systems (duplicated PNC).

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

LED Indicators

Page 7-11DS1 CONV (TN574/TN1654) Circuit Pack LEDs

Figure 7-3. TN574 DS1C Circuit Pack LEDs

TN1654 Circuit Pack LEDs

The TN1654 DS1CONV board has 11 LEDs on its faceplate. The top 3 system

standard LEDs indicate the state of the DS1CONV board. These LEDs are under

firmware control until the board has established a link to the SPE via the EI or SNI.

Once the link is established, software controls the 3 LEDs. If the link breaks, the

LEDs are again under firmware control.

The red and green LEDs have the traditional use: red means an alarm condition,

and green indicates that maintenance testing is in progress. The red and green

LEDs are also turned on during circuit pack initialization by firmware. When the

control link to the circuit pack is lost, firmware controls the red LED to indicate an

alarm condition.

The yellow LED under firmware control is used to indicate the state of the

physical Fiber Interface, the Fiber Channel (link to EI or SNI), the DS1 Control

Channel (link to opposite DS1CONV board), and the SPE communications link in

the following manner and order of priority. (The yellow LED remains on for longer

periods of time as the DS1CONV Complex becomes closer to being fully

operational.)

1. If the Fiber is Out of Frame or if a Fiber Loss of Signal condition exists, the

yellow LED will flicker at a 5 Hz rate (on for 100 mS, off for 100 mS).

ALARM LED (RED)

TEST LED (GREEN)

BUSY LED (YELLOW)

DS1 FACILITY A

DS1 FACILITY B

DS1 FACILITY C

DS1 FACILITY D

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

LED Indicators

Page 7-12DS1 CONV (TN574/TN1654) Circuit Pack LEDs

2. If the Fiber Channel is down (DS1 Converter circuit pack/fiber endpoint

communications), the yellow LED will flash at a 1 Hz rate (on for 500 ms,

off for 500 ms).

3. If the DS1 Control Channel is down between the two DS1CONVs in the

DS1CONV Complex, the yellow LED will pulse at a 0.5 Hz rate (on for 1

second, off for 1 second).

4. If the SPE communications link is down, the yellow LED will wink off every

2 seconds for 200 ms (2 seconds on, 200 ms off).

5. If all is well with the Fiber Interface and all communications channels, the

yellow LED will remain on continuously in a Standard Reliability and High

Reliability System configuration. In Critical Reliability systems (duplicated

PNC), an active DS1CONV circuit pack will have its yellow LED on

continuously, and a standby DS1CONV circuit pack will have its yellow

LED off. The LED will then be under software control.

The bottom four green LEDs on the TN574 DS1CONV board are under hardware

control. The four green LEDs indicate, for each DS1CONV facility, whether a

receive signal is present for the DS1 facility

The next four LEDs on the TN1654 DS1CONV board are labeled STATUS LEDs

and are for future use. These LEDs will not be lit.

The bottom four LEDs on the TN1654 board are labeled SPAN LEDs. These LEDs

are under firmware control. If the facility is not administered, then the LED is not

lit. The LED is lit amber if the facility is running alarm free. If the facility is

detecting either a red alarm (loss-of-signal or loss-of-frame), a yellow alarm

(remote frame alarm) or a blue alarm (AIS signal) then the LED is lit red. The

SPAN SELECT Switch on the TN1654 faceplate is for future use. Pushing the

switch will have no effect on the board. See Figure 7-4 for a view of the face plate

on the TN1654 DS1CONV circuit pack

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

LED Indicators

Page 7-13Tone-Clock Circuit Pack LEDs

Figure 7-4. TN1654 DS1CONV Circuit Pack

Tone-Clock Circuit Pack LEDs

The Tone-Clock circuit packs have the standard red, green and yellow LEDs. The

red LED has the traditional meaning. The yellow and green LEDs flash in specific

patterns to indicate the status of the circuit pack. The standby status applies only

to systems with a duplication option.

Maintenance/Test Circuit Pack LEDs

The TN771D Maintenance/Test circuit pack has the standard red, green, and

yellow LEDs. The red and green LEDs have the traditional meaning, where red

indicates an alarm condition, and green indicates testing in progress.

The yellow LED can be off or on continuously or flashing, depending on the mode

of operation of the TN771D and whether or not it has detected errors. The yellow

LED is on steady when the TN771D’s analog test port or digital test ports are

being used to test trunks or line circuits. The yellow LED is also used to indicate

INSET

0015_0 RBP 052396

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

LED Indicators

Page 7-14LEDs on Standby Components

Packet Bus status. Table 7-4 illustrates the Maintenance/Test yellow LED states

as they apply to Packet Bus activity.

LEDs on Standby Components

In high reliability and critical reliability option systems, duplicated components

that are on standby will usually have their yellow LEDs unlit, with the following

exceptions.

■The Major, Minor and Warning alarm LEDs on the SYSAM circuit pack on

the standby SPE do not give reliable indications. Pay attention only to

those LEDs that are on the active SYSAM circuit pack.

■The yellow LED will blink on and off when the standby Processor circuit

pack is up and standby maintenance is running.

1. It takes 5 to 10 seconds for the yellow LED to respond to a change in the state of the

Packet Bus.

2. Because the yellow LED on the Maintenance/Test circuit pack can also be on steady

when the digital and analog test ports on the circuit pack are in use, exact

interpretation of the yellow LED may require that the technician busy out the analog

and digital test ports or examine the error and Alarm Logs for PKT-BUS errors and

alarms.

3. “Standalone” refers to the TN771D’s capability to operate autonomously as a

troubleshooting aid. A detailed description of the TN771D standalone mode is

provided in the ‘‘Packet Bus Fault Isolation and Repair’’ section of Chapter 5,

‘‘Responding to Alarms and Errors’’.

Table 7-4. TN771D Maintenance/Test Yellow LED States

LED State1TN771D Mode Condition

Solid off Normal The Maintenance/Test circuit pack

detects no Packet Bus faults.

Solid on2Normal The Maintenance/Test Packet Bus

port has successfully reconfigured

the Packet Bus around a fault.

Flashing (1 Hz) Normal The Maintenance/Test Packet Bus

port is unable to reconfigure the

Packet Bus around a fault.

Solid off Standalone3The Maintenance/Test detects no

Packet Bus faults.

Solid on Standalone This condition cannot normally

occur. The LED is always either off or

blinking in standalone mode.

Flashing (1 Hz) Standalone The Maintenance/Test Packet Bus

port detects a Packet Bus fault.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

LED Indicators

Page 7-15LEDs on Standby Components

■In high reliability systems with a Center Stage Switch, (duplicated SPE,

simplex PNC), the standby Switch Node Clock’s yellow LED is off. In

critical reliability systems, the standby SNC is located on a separate

carrier and normally remains lit.

■Yellow LEDs on Power Units on standby carriers normally remain lit.

When LED indications are not clear, use the status pnc, status spe and

status pn commands to determine which components are active.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

LED Indicators

Page 7-16LEDs on Standby Components

Maintenance Commands

Page 8-1Command Line Syntax

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

8Maintenance Commands

This chapter contains descriptions of commands available to the craft login.

Introductory sections explain the meaning of common input parameters, or

command line arguments, common output fields, and error codes for busyout,

release and reset commands.

!CAUTION:

This document is intended for Release 5 and later systems only. For

previous DEFINITY systems (G3V4 and earlier), refer to DEFINITY

Enterprise Communications Server Release 5 Maintenance for R5r,

555-230-105.

Command Line Syntax

Each command consists of an action word, an object upon which the action is

performed, and optional qualifiers that modify the execution of the command. In

some cases the choice of a qualifier may be required. The syntax of the

command appears under the heading at the beginning of each command

description. The syntax is interpreted as follows:

Command words can be abbreviated. A partially spelled word is recognized as

long as enough letters are entered to distinguish it from other valid entries.

Otherwise, the screen displays a selection of command words that match the

Command Object Optional Qualifiers

test station

extension

[short|long] [repeat number | clear] [schedule]

bold bold italic if a

variable, bold if

entered literally

bracketed; either/or choices are separated by a

vertical slash (|); bold italic if a variable, bold if

entered literally

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-2Common Input Parameters

abbreviation. For example, test alarms step short clear can be entered as t al

st sh c. Drop leading zeroes from numerical entries. For example, cabinet

number 03 can be entered as 3.

Pressing the HELP key displays all available commands. If an incomplete

command is entered, pressing HELP displays all valid qualifiers for the command.

NOTE:

When the successful execution of a command is prevented, an error

message that is usually self-explanatory displays. If the following message

appears, the software is most likely corrupt:

Error encountered; can’t complete request

In this case, follow normal escalation procedures.

Common Input Parameters

Characters in bold type are entered literally on the command line. Characters in

italic bold type are variables. SeeTable 8-1 for common test command

parameters and their explanations and for explanations of less common

parameters.

For example, display cabinet requires only the entry of

: display cabinet 12.

Test port requires a location of the form

UUCSSpp

: test port 05c1506 to test

Table 8-1. Common Test Command Parameters

Parameter Range Meaning

UU 1-22 One or two-digit cabinet number For many commands

this defaults to cabinet 1, the PPN

CA-E Letter designation of a carrier. For many commands

relating to SPE or EPN control circuit packs, this

defaults to A, the control carrier. For PPNs with

duplicated SPEs, A or B is usually specified for SPE

MOs.

SS 1-21 One or two-digit number identifying a circuit pack slot

on a carrier For many commands relating to SPE or EPN

control circuit packs, this usually defaults to the only

possible slot number.

pp 1-24 One or two-digit number identifying an individual port

circuit on circuit pack The range of this variable differs

depending on the type of circuit pack.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-3Common Input Parameters

port circuit 6 on the circuit pack in cabinet 5, carrier C, slot 6. The list and

display commands are useful in relating MO locations to information such as PN

number, extension, link numbers, and so forth. Table 8-2 contains information

about the less-common command parameters.

Table 8-2. Less-Common Test Command Parameters

Parameter Range Default Meaning

PN# One or two-digit port network number. EPN cabinets

may contain one or two port networks. Use list

cabinet to find which port networks are in each

cabinet.

print This command executes immediately (if resources

are available) and sends output both to the screen

and to a printer connected to the terminal where the

command was entered. This option is available for

display, list and status commands.

schedule A scheduling form is displayed which allows you to

specify a start time for the command. The command

is placed in the queue and, when executed, sends

the output to the system printer. The schedule

option is available for display, list and test

commands. When used with display alarms or

errors, a full report is generated. The usual selection

form for error and alarm reports is suppressed so

that it will not interfere with the command’s execution

when it is issued from the queue.

You can see what commands are currently queued

with the list command-queue command. A queued

command can be canceled with remove

command-queue job#. This option requires that the

system printer be administered on page 4 of the

Feature-Related System Parameters form.

group# 1-666 One to three-digit trunk group number; used to

address trunk maintenance objects.

group#/

member# 1-255 Group number followed by a slash and the one to

three-digit member number of an individual trunk;

used to address trunk maintenance objects.

Continued on next page

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-4Common Input Parameters

extension The extension number assigned to the port or other

maintenance object.

The number of digits in an extension is determined

by the system dial plan. The list and display

commands are useful in relating extension numbers,

maintenance objects, and other components.

repeat # 1-100 1 Used with test commands, the number of times a

test sequence is to be repeated. The word repeat, or

simply the letter r, followed by the number.

short

long Used with test commands, these qualifiers

determine either the long or short test sequence run

for this maintenance object. The test sequence run

varies for each maintenance object.

!CAUTION:

For some maintenance objects, the long

sequence is destructive, that is, disruptive to

call service.

The short sequence is always non-destructive.

clear Used with test commands, this specifies that the test

sequence is to be repeated until any active alarms

against the maintenance object is cleared by the

passing of tests or until any test in the sequence

fails.

If no such alarms are active, the sequence is run

once. The long clear combination effects a clearing

of all alarms against the maintenance object if no

errors are encountered. The short clear combination

clears only alarms pertinent to the tests in the short

sequence.

!CAUTION:

If all tests pass, the long clear combination

clears all error counters. If firmware counters

are cleared while actual problem exists,

customer service may degrade due to calls

being routed over faulty components.

Table 8-2. Less-Common Test Command Parameters — Continued

Parameter Range Default Meaning

Continued on next page

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-5Common Output Fields

Common Output Fields

■An indication that the command successfully completed or a

self-explanatory message giving a reason for a failure or abort.

■An input form for entering additional information required to complete the

command. These are described under each command that presents an

input form.

■A form listing one or more lines of results with error codes that indicate the

reason for a FAIL or ABORT result.

Many commands that use the last form display the fields listed in the table below.

Some return one line of output. Other commands that run either one test on

several objects or several different tests on one or more objects return several

lines of output. In this case, each line represents one test result.

The length of this variable differs for the various types of commands. A port

circuit requires a full length address such as 11C1502, which indicates circuit

number 2 on the circuit pack in cabinet 11, carrier C, slot 15. A control carrier

component such as a SYSAM circuit pack is designated simply as 01B,

indicating the SYSAM in carrier B of cabinet 1, the PPN cabinet.

Some MOs such as TDM-BUS are addressed by PN number. In this case, the

number is usually preceded by PN. For example, TDM bus A in port network 5 is

designated as PN 05A.

In critical reliability systems, Port Network Connectivity is duplicated as two

independent sets of PNC components. These are designated as A-PNC and

B-PNC.

Variable Range Meaning

UU 1-22 One or two-digit cabinet number

CA-E Letter designation of a circuit pack carrier

SS 1-21 One or two-digit number identifying a circuit pack slot on a carrier

pp 1-24 One or two-digit number identifying an individual port circuit on

circuit pack

Port The address or physical location of the MO. Usually this is

UUCSSpp.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-6Common Output Fields

Maintenance Name The name of the MO as it appears in the alarm and

error logs.

Alt. Name The output screens of many commands list an

alternate name for certain MOs in addition to their port

address (physical location). The meaning of the name

depends upon the type of the object, as shown in the

following table.

Maintenance

Object Alternate Name Example

Station extension 84140

Trunk trunk group # / member #

(001-666) / (001-255) 45/3

Personal CO line P/ personal CO line group # (001-200) P/23

Test

No. The number of the test run on the MO as part of a test command.

Descriptions of each test and its related error codes appear under the

relevant MO. Other commands such as clear firmware-counters and

reset also report a test number.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-7Contention Between Simultaneous Commands

Contention Between Simultaneous

Commands

The following limits apply to simultaneous maintenance and administration

activities:

■Up to 8 users can be logged into the system at the same time.

■Up to 5 maintenance commands can run concurrently.

Result One of the following results:

PASS: The command successfully completed. For a test command

this indicates that no errors were detected by the test.

ABORT: The command was prevented from completing. See Error

Code below.

FAIL: Indicates that a serious error was detected by the test. See Error

Code below.

NO BOARD: The system does not detect a circuit pack in the location

specified on the command line.

CONFLICT: Another user was testing this maintenance object.

EPN-DOWN: The EPN holding the MO is inaccessible. The Expansion

Archangel Link may be down.

DISABLED: The MO or test has been disabled by the Tier 3 disable

command.

NOT ASSIGNED: The location specified does not have a circuit pack

administered to it.

EXTRA BOARD: This result can appear for the Maintenance/Test, Call

Classifier, Tone Detector, Announcement, and Speech Synthesis

circuit packs. Each of these circuit packs has restrictions on how many

can be in the system or a port network:

Maintenance/Test circuit pack: 1 per port network

Tone Detector circuit pack: up to 50 per system

Call Classifier circuit pack: up to 25 per system

Speech Synthesis circuit pack: 40 per system

Announcement circuit pack: 1 per system

Remove the extra circuit pack(s).

Error

Code A number indicating the reason for a FAIL or ABORT result. For test

commands and other commands that return a test result, consult the

tables of test error codes under the relevant MO. For busyout, release

and reset commands, see ‘‘Common Abort and Fail Codes’’ and Test

Commands.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-8Busyout and Release Commands

■Up to 3 maintenance commands issued from system access port (SAP) or

EPN Maintenance circuit pack logins can run concurrently. The other 2 are

reserved for the SYSAM and INADS ports.

■Up to 5 administration commands can run concurrently.

■In general, a maintenance object or other system entity can be acted upon

by only one command at a time. This restriction applies to such action

commands as:

—busyout

— change

—clear

— recycle

— release

—set

—test

■In general, only 1 SPE component can be acted upon at one time by

commands such as those just mentioned.

■When an action command is acting on a circuit pack, that circuit pack and

all maintenance objects located on it are unavailable for other commands.

■Display-only commands such as the following generally do not conflict

with any other commands.

—display

— status

—get

— monitor

■Certain system-wide actions such as reset system and upgrade

software cannot run concurrently with any other command.

■Most commands require the use of shared system resources in order to

execute. When required resources are already in use, the command will

abort. For example, save, restore, backup, and test disk commands all

require the use of the Mass Storage System (MSS). Only one such

command can run at one time.

Busyout and Release Commands

The busyout command places the object of the command in a maintenance

busy state. In this state, the object is removed from active service and is not

available for use by call processing. Services dependent on the busied out

component are dropped. If the component supports a link, the link is dropped.

No scheduled or periodic background tests are run on the object while it is

busied out. Demand maintenance tests can be run on the object, though some

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-9Busyout and Release Commands

tests require that the object be released to complete. A WARNING alarm with

error type 18 is logged against each busied out object. All busied out MOs can

be displayed by entering error type 18 in the Error Type field on the Hardware

Errors Report Form (see display errors). The matching release command

returns the maintenance object to service, providing the object is not otherwise

incapacitated.

On systems with duplicated SPE, busyouts are preserved across planned SPE

interchanges and level 1 system resets (Warm). System resets of level 2 or

higher release the busied out objects.

A variety of self-explanatory error messages may be displayed if the command

cannot be executed as entered. In addition to these there are a number of

numerical error codes which may be displayed in the Error Code field if the

command ABORTS or FAILS as indicated in the Result field. These are explained

in the

Common Abort and Fail Codes

section of this chapter.

The following screen display shows a typical result for busyout board 1c03

(analog line circuit pack in cabinet 1, carrier c, slot 7 with three administered

ports):

The following display shows a typical result for most maintenance objects. See

‘‘Common Output Fields’’ above for an explanation of the fields displayed.

busyout board 01C03

Command Results

Port Maintenance Name Alt. Name Result Error Code

01C03 ANL-BD PASS

01C0301 ANL-16-L 5409 PASS

01C0302 ANL-16-L 5416 PASS

01C0303 ANL-16-L 5421 PASS

01C0304 ANL-16-L 5422 PASS

01C0305 ANL-16-L 5411 PASS

Command successfully completed

busyout disk b

COMMAND RESULTS

Port Maintenance Name Alt. Name Result Error Code

01B DISK PASS

Command successfully completed

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-10Common Abort and Fail Codes

Common Abort and Fail Codes

Table 8-3 lists common error codes associated with abort and fail results for

busyout, release, test, and reset commands. In addition to these, many

maintenance objects have other unique error codes.

Table 8-3. Common Error Codes for Busyout, Release, Test,

and Reset Commands

Error

Code Command

Result Description/Recommendation

ABORT System resources are unavailable to run command.

1. Try the command again at 1-minute intervals up to 5 times.

0 ABORT Internal system error.

1. Retry the command at 1-minute intervals up to 5 times.

1005 ABORT A DS1 interface circuit pack could not be reset because it is

currently supplying the on-line synchronization reference.

1. Use the set sync command to designate a new DS1

interface circuit pack as the on-line reference, then try the

reset again.

1010 ABORT Attempt was made to busyout an object that was already busied

out.

1011 ABORT Attempt was made to release an object that was not first busied

out.

1015 ABORT A reset of this circuit pack requires that all maintenance objects

on it be in the out-of-service state.

1. Use the busyout board command to place all objects on the

circuit pack in the out-of-service state, and try the reset

again.

1026 ABORT The specified TDM bus cannot be busied out because the

control channel or system tones are being carried on it. You can

use the set tdm PC command to switch the control channel and

system tones to the other TDM bus.

1030 ABORT This command is not allowed on a circuit pack on the standby

SPE.

Continued on next page

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-11Common Abort and Fail Codes

1338 ABORT The system could not execute the command on a component on

the Standby SPE because an interchange was pending.

1. Refer to ‘‘STBY-SPE (Standby SPE Maintenance)’’ in Chapter

2. Try the command again after the SPE interchange occurs.

1339 ABORT The system could not execute the command on a component on

the Standby SPE because an handshake communication was

down.

1. Refer to ‘‘STBY-SPE (Standby SPE Maintenance)’’ in Chapter

2. Try the command again after the standby SPE is restored to

service. Use status spe to determine state of standby SPE.

1347 ABORT The system could not execute the command on a component on

the Standby SPE because memory refresh was not complete.

1. Refer to ‘‘STBY-SPE (Standby SPE Maintenance)’’ in Chapter

2. Try the command again after the standby SPE is restored to

service. Use status spe to determine state of standby SPE.

1350 ABORT The system could not execute the command on a component on

the Standby SPE because memory shadowing was not enabled.

1. Refer to ‘‘STBY-SPE (Standby SPE Maintenance)’’ in Chapter

2. Try the command again after the standby SPE is restored to

service. Use status spe to determine state of standby SPE.

2012

2500 ABORT Internal system error.

2100 ABORT System resources to run this command were unavailable.

1. Try the command again at 1-minute intervals up to 5 times.

Table 8-3. Common Error Codes for Busyout, Release, Test,

and Reset Commands — Continued

Error

Code Command

Result Description/Recommendation

Continued on next page

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-12Common Abort and Fail Codes

62524

62525

62526

ABORT Maintenance is currently active on the maximum number of

maintenance objects that the system can support. This condition

is commonly caused by the fact that the system contains a large

number of stations or trunks that have been administered, and

whose circuit packs are installed, but which are not physically

connected.

1. Resolve as many alarms as possible on the station and trunk

MOs, or busyout these MOs to prevent maintenance activity

on them. Then try the command again.

BOARD The circuit pack is not physically installed.

EXTRA BD This result can appear for Maintenance/Test, Call Classifier, Tone

Detector, Announcement and Speech Synthesis circuit packs.

Each of these circuit packs has restrictions on how many can be

installed in the system or in a port network. The restrictions are as

follows:

TN771D Maintenance/Test: 1 /port network

TN748 Tone Detector: 50 /system

TN744 Call Classifier: 25 /system

Speech Synthesizer: 40 /system

TN750 Announcement: 1 /system

Remove any extra circuit packs.

1 FAIL For reset commands, the circuit pack was not successfully

halted.

2 FAIL For reset commands, the circuit pack was not successfully

restarted after being halted. For both results, replace the circuit

pack.

FAIL Refer to the applicable maintenance object in Chapter 9.

PASS The requested action successfully completed. If the command

was a reset, the circuit pack is now running and should be

tested.

Table 8-3. Common Error Codes for Busyout, Release, Test,

and Reset Commands — Continued

Error

Code Command

Result Description/Recommendation

Continued on next page

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-13Alarm and Error Categories

Alarm and Error Categories

The display alarms and display errors commands allow you to generate

reports for certain groups of maintenance objects. By entering a category from

the Table 8-4 into the Category field of the input form, you can restrict the report

to only those maintenance objects included in that category. The report can be

further narrowed down by using the other fields on the form.

Table 8-4 is a list of the categories showing which MOs are included. Table 8-5 is

sorted by MO and shows the categories containing each MO.

Table 8-4. Alarm and Error Categories

Category Maintenance Objects

adm-conn ADM-CONN

announce ANN-PT

ANN-BD

ANNOUNCE

bri/asai ASAI-ADJ

ASAI-BD

ASAI-PT

ASAI-RES

ABRI-PORT

BRI-BD

BRI-PORT

BRI-SET

LGATE-AJ

LGATE-BD

LGATE-PT

cdr CDR-LNK

data-mod BRI-DAT

DAT-LINE

DT-LN-BD

PDMODULE

TDMODULE

Continued on next page

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-14Alarm and Error Categories

detector DTMR-PT

DETR-BD

GPTD-PT

TONE-BD

dup-spe CARR-POW

DUPINT

MEM-BD

PROCR

SPE-SELEC

STBY-SPE

SW-CTL

TAPE

environ AC-POWER

CABINET

CARR-POW

DC-POWER

EMG-XFER

EXT-DEV

POWER

RING-GEN

exp-intf AC-POWER

CARR-POW

DC-POWER

DUPINT

EPN-SNTY

EXP-INTF

MAINT

SYNC

Table 8-4. Alarm and Error Categories — Continued

Category Maintenance Objects

Continued on next page

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-15Alarm and Error Categories

TDM-CLK

TONE-BD

ext-dev CUST-ALM

generatr STRAT-3

SYNC

TDM-CLK

TONE-PT

TONE-BD

inads-link INADS

infc EXP-INTF

ISDN-LNK

ISDN-SGRP

PGATE-BD

X25-PT

maint MAINT

mass-st DISK

H-ADAPTR

STO-DATA

TAPE

mbus DUPINT

MEM-BD

PROCR

SW-CTL

TAPE

memory MEM-BD

Table 8-4. Alarm and Error Categories — Continued

Category Maintenance Objects

Continued on next page

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-16Alarm and Error Categories

misc CONFIG

ERR-LOG

MIS

PROC-SAN

SYSTEM

TIME-DAY

mmi MMI-BD

MMI-LEV

MMI--PT

MMI-SYNC

mnt-test M/T-ANL

M/T-BD

M/T-DIG

M/T-PKT

modem MODEM-BD

MODEM-PT

mssnet H-ADAPTR

SW-CTL

netcon SW-CTL

pkt M/T-PKT

PKT-BUS

pms/jrnl JNL-PRNT

PMS-LINK

pnc DS1C-BD

DS1-FAC

EXP-INTF

FIBER-LK

PNC-DUP

Table 8-4. Alarm and Error Categories — Continued

Category Maintenance Objects

Continued on next page

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-17Alarm and Error Categories

SN-CONF

SNC-BD

SNC-LINK

SNC-REF

SNI-BD

SNI-PEER

pncmaint DS1C-BD

DS1-FAC

EXP-INTF

FIBER-LK

PNC-DUP

SN-CONF

SNC-BD

SNC-LINK

SNC-REF

SNI-BD

pnc-peer SNI-PEER

procr PROCR

quick-st ABRI-PT

ADXDP-PT

ANL-16-LINE

ANL-LINE

ANL-NE-LINE

ANN-PT

ANNOUNCE

ASAI-ADJ

AUDIX-PT

AUX-TRK

Table 8-4. Alarm and Error Categories — Continued

Category Maintenance Objects

Continued on next page

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-18Alarm and Error Categories

BRI-PT

BRI-SET

CDR-LINK

CLSFY-PT

CO-DS1

CO-TRK

CONFIG

DAT-LINE

DID-DS1

DID-TRK

DIG-LINE

DIOD-TRK

DISK

DS1-FAC

DS1C-BD

DTMR-PT

EPN-SANITY

EXP-INTF

EXP-PN

FIBER-LNK

GPTD-PT

HYB-LINE

ISDN-LNK

ISDN-TRK

JNL-PRNT

MAINT

MEM-BD

MET-LINE

Table 8-4. Alarm and Error Categories — Continued

Category Maintenance Objects

Continued on next page

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-19Alarm and Error Categories

MODEM-PT

OPS-LINE

PDATA-PT

PDMODULE

PGATE-PT

PKT-BUS

PKT-INT

PMS-LINK

PMS-PRNT

PNC-DUP

PRI-CDR

PROCR

S-SYN-PT

SEC-CDR

SN-CONF

SNC-BD

SNC-LNK

SNC-REF

SNI-BD

SNI-PEER

SW-CNTL

SYS-PRNT

SYSAM

SYSLINK

SYSTEM

TAPE

TDM-BUS

TDM-CLK

Table 8-4. Alarm and Error Categories — Continued

Category Maintenance Objects

Continued on next page

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-20Alarm and Error Categories

TDMODULE

TIE-DS1

TIE-TRK

TONE-BD

TTR-LEV

spe DISK

DUP-CHL

DUPINT

H-ADAPTR

MEM-BD

PKT-INT

PROCR

SPE-SELEC

STBY-SPE

STO-DATA

SW-CTL

SYSAM

SYSTEM

TAPE

s-syn S-SYN-BD

S-SYN-PT

stabd ABRI-PORT

ADXDP-BD

ADXDP-PT

ANL-16-LINE

ANL-BD

ANL-LINE

Table 8-4. Alarm and Error Categories — Continued

Category Maintenance Objects

Continued on next page

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-21Alarm and Error Categories

ANL-NE-LINE

ASAI-ADJ

AUDIX-BD

AUDIX-PT

BRI-BD

BRI-PORT

BRI-SET

DIG-BD

DIG-LINE

HYB-BD

HYB-LINE

MET-BD

MET-LINE

stacrk ADXDP-PT

ANL-LINE

ANL-16-LINE

ANL-NE-LINE

AUDIX-PT

DIG-LINE

HYB-LINE

MET-LINE

OPS-LINE

stations ABRI-PORT

ADXDP-PT

ANL-16-LINE

ANL-LINE

ANL-NE-LINE

ASAI-ADJ

Table 8-4. Alarm and Error Categories — Continued

Category Maintenance Objects

Continued on next page

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-22Alarm and Error Categories

AUDIX-PT

BRI-PORT

BRI-SET

DIG-LINE

HYB-LINE

MET-LINE

OPS-LINE

sys-link SYS-LINK

sys-prnt SYS-PRNT

tape TAPE

tdm SW-CTL

TDM-BUS

tone CLSFY-BD

CLSFY-PT

DETR-BD

DTMR-PT

GPTD-PT

STRAT-3

SYNC

TDM-CLK

TONE-BD

TONE-PT

TTR-LEV

trkbd AUX-BD

AUX-TRK

CO-BD

CO-DS1

CO-TRK

Table 8-4. Alarm and Error Categories — Continued

Category Maintenance Objects

Continued on next page

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-23Alarm and Error Categories

DID-BD

DID-DS1

DID-TRK

DIOD-BD

DIOD-TRK

DS1-BD

ISDN-TRK

PE-BCHL

TIE-BD

TIE-DS1

TIE-TRK

UDS1-BD

WAE-PT

trkcrk AUX-TRK

CO-DS1

CO-TRK

DID-DS1

DID-TRK

DIOD-TRK

ISDN-LNK

ISDN-TRK

TIE-DS1

TIE-TRK

trunks CO-TRK

AUX-TRK

CO-DS1

DID-DS1

DID-TRK

Table 8-4. Alarm and Error Categories — Continued

Category Maintenance Objects

Continued on next page

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-24Alarm and Error Categories

DIOD-TRK

ISDN-LNK

ISDN-TRK

PE-BCHL

TIE-DS1

TIE-TRK

WAE-PORT

vc VC-BD

VC-DSPPT

VC-LEV

VC-SUMPT

wide-band PE-BCHL

WAE-PORT

Table 8-4. Alarm and Error Categories — Continued

Category Maintenance Objects

Continued on next page

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-25Alarm and Error Categories

Table 8-5. Alarm and Error Categories

(Sorted by MO)

Maintenance Object Categories

ABRI-PORT bri/asai

quick-st

stabd

stations

AC-POWER environ

exp-intf

ADM-CONN adm-conn

ADXCL-BD

ADXCL-PT

ADXCL-RS

ADXDP-BD quick-st

stabd

ADXDP-PT quick-st

stabd

ADXDP-RS

ANL-16-L quick-st

sta-bd

stacrk

stations

ANL-BD stabd

ANL-LINE quick-st

stabd

stacrk

stations

ANN-BD announce

ANN-PT announce

quick-st

ANNOUNCE quick-st

Continued on next page

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-26Alarm and Error Categories

announce

ASAI-ADJ bri/asai

quick-st

sta-bd

stations

AUDIX-BD quick-st

sta-bd

AUDIX-PT quick-st

stabd

stacrk

stations

AUDIX-RES

AUX-BD trkbd

AUX-TRK quick-st

trkbd

trkcrk

trunks

BRI-BD bri/asai

sta-bd

BRI-DAT data-mod

quick-st

BRI-PORT bri/asai

quick-st

stabd

stations

BRI-SET bri/asai

quick-st

stabd

Table 8-5. Alarm and Error Categories

(Sorted by MO) — Continued

Maintenance Object Categories

Continued on next page

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-27Alarm and Error Categories

stations

CABINET environ

CARR-POW environ

exp-intf

CDR-LNK cdr

quick-st

CLSFY-BD tone

CLSFY-PT tone

quick-st

CO-BD trkbd

CO-DS1 quick-st

trkbd

trkcrk

trunks

CO-TRK quick-st

trkbd

trkcrk

trunks

CONFIG misc

quick-st

CUST-ALM ext-dev

DAT-LINE data-mod

quick-st

DC-POWER environ

exp-intf

DETR-BD detector

tone

DID-BD trkbd

Table 8-5. Alarm and Error Categories

(Sorted by MO) — Continued

Maintenance Object Categories

Continued on next page

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-28Alarm and Error Categories

DID-DS1 quick-st

trkbd

trkcrk

trunks

DID-TRK quick-st

trkbd

trkcrk

trunks

DIG-BD sta-bd

DIG-LINE quick-st

stabd

stacrk

stations

DIOD-BD trkbd

DIOD-TRK quick-st

trkbd

trkcrk

trunks

DISK quick-st

mass-st

spe

DS1-BD trkbd

DS1-FAC pnc

pncmaint

quick-st

DS1C-BD pnc

pncmaint

quick-st

Table 8-5. Alarm and Error Categories

(Sorted by MO) — Continued

Maintenance Object Categories

Continued on next page

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-29Alarm and Error Categories

DT-LN-BD data-mod

DTMR-PT detector

tone

quick-st

DUP-CHL spe

DUPINT dup-spe

exp-intf

mbus

spe

EMG-XFER environ

EPN-SNTY exp-intf

quick-st

ERR-LOG misc

EXP-INTF exp-intf

infc

pnc

pncmaint

quick-st

EXP-PN quick-st

EXT-DEV environ

ext-dev

FIBER-LK pnc

pncmaint

quick-st

GPTD-PT detector

quick-st

tone

H-ADAPTR mass-st

Table 8-5. Alarm and Error Categories

(Sorted by MO) — Continued

Maintenance Object Categories

Continued on next page

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-30Alarm and Error Categories

mssnet

spe

HYB-BD stabd

HYB-LINE quick-st

stabd

stacrk

stations

INADS inads

ISDN-LNK infc

quick-st

trkcrk

trunks

ISDN-SGR infc

ISDN-TRK quick-st

trkbd

trkcrk

trunks

JNL-PRNT quick-st

MAINT exp-intf

maint

quick-st

MEM-BD dup-spe

mbus

memory

quick-st

spe

MET-BD stabd

MET-LINE quick-st

Table 8-5. Alarm and Error Categories

(Sorted by MO) — Continued

Maintenance Object Categories

Continued on next page

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-31Alarm and Error Categories

stabd

stacrk

stations

MIS misc

MODEM-BD modem

MODEM-PT modem

quick-st

M/T-ANL mnt-test

M/T-BD mnt-test

M/T-DIG mnt-test

M/T-PKT mnt-test

pkt

OPS-LINE quick-st

stacrk

stations

PDATA-BD

PDATA-PT quick-st

PDMODULE data-mod

quick-st

PE-BCHL trunkbd

trunks

wideband

PGATE-BD

PGATE-PT quick-st

PKT-BUS pkt

quick-st

PKT-INT quick-st

spe

Table 8-5. Alarm and Error Categories

(Sorted by MO) — Continued

Maintenance Object Categories

Continued on next page

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-32Alarm and Error Categories

PMS-LINK pms/jrnl

quick-st

PMS-PRNT quick-st

PNC-DUP pnc

pncmaint

quick-st

POWER-AC

POWER-DC

PRI-CDR quick-st

PROC-SAN misc

PROCR dup-spe

mbus

procr

quick-st

spe

RING-GEN environ

S-SYN-BD quick-st

S-SYN-PT quick-st

s-syn

SEC-CDR quick-st

SN-CONF pnc

pncmaint

quick-st

SNC-BD pnc

pncmaint

quick-st

SNC-LINK pnc

pncmaint

Table 8-5. Alarm and Error Categories

(Sorted by MO) — Continued

Maintenance Object Categories

Continued on next page

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-33Alarm and Error Categories

quick-st

SNC-REF pnc

pncmaint

quick-st

SNI-BD pnc

pncmaint

quick-st

SNI-PEER pnc

pnc-peer

quick-st

SPE-SELE dup-spe

spe

STBY-SPE dup-spe

spe

STO-DATA mass-st

spe

STRAT-3 generatr

tone

SVC-SLOT

SW-CTL dup-spe

mbus

mssnet

netcon

quick-st

spe

tdm

SYNC exp-intf

generatr

Table 8-5. Alarm and Error Categories

(Sorted by MO) — Continued

Maintenance Object Categories

Continued on next page

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-34Alarm and Error Categories

tone

SYS-LINK sys-link

SYS-PRNT quick-st

sys-prnt

SYSAM quick-st

spe

SYSTEM misc

quick-st

spe

TAPE dup-spe

mass-st

mbus

quick-st

spe

tape

TDM-BUS quick-st

tdm

TDM-CLK exp-intf

generatr

quick-st

tone

TDMODULE data-mos

quick-st

TIE-BD trkbd

TIE-DS1 quick-st

trkbd

trkcrk

trunks

Table 8-5. Alarm and Error Categories

(Sorted by MO) — Continued

Maintenance Object Categories

Continued on next page

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-35backup disk

backup disk

This command copies all information from the disk drive in the specified

processor carrier(s) to the tape system in the same carrier. This can take up to 40

minutes to complete.

TIE-TRK quick-st

trkbd

trkcrk

trunks

TIME-DAY misc

TONE-BD detector

exp-intf

generatr

quick-st

tone

TONE-PT generatr

tone

TSC-ADM

TTR-LEV quick-st

tone

UDS1-BD trkbd

WAE-PORT trunkbd

trunks

wideband

Table 8-5. Alarm and Error Categories

(Sorted by MO) — Continued

Maintenance Object Categories

Continued on next page

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-36backup disk

On a simplex SPE, the default is to perform an incremental backup of SPE-A. On

a duplex SPE, the default is to perform an incremental backup on both SPE-A

and SPE-B.

NOTE:

The backup command can take up to 10 minutes to complete. Avoid

pressing the ENTER key on the keyboard during this time, since doing so will

cause the result messages to be lost.

Parameters

Examples

backup disk

backup disk spe-b

backup disk active incremental

Output

spe-a Specifies a backup from the A processor carrier hard disk to the

A SPE tape.

spe-b This specifies a backup from the B processor carrier hard disk

to the B SPE tape.

active This specifies a backup of the active processor.

standby This specifies a backup of the standby processor.

both This specifies a backup of both processor carriers.

either Specifies a backup of both SPE carriers. If the standby is not

accessible, the command performs a backup of the active SPE.

incremental Causes all data marked “good” that has been changed since

the last backup to tape to be copied to the tape. That is, all files

that have a date newer than the date on the tape file.

full This causes all data to be copied from disk to tape regardless

of the dates and the state of the data (“good” or “bad”).

Processor Identifies the processor carrier that was backed up

(SPE-A, or SPE-B).

Command Completion

Status Results of the command, and the reason for any

failure are displayed.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-37busyout cdr-link

For the following output example, assume that the command, backup disk is

entered on a duplex system.

busyout cdr-link

busyout cdr-link [primary | secondary]

The busyout cdr-link command puts a specified call detail recording link in a

maintenance busy state. When busied out, the link is dropped and must be

reestablished later when returned to service. See the description of status link

for more information on links.

Parameters

Examples

busyout cdr-link

busy cdr secondary

For more information see the following sections at the beginning of this chapter:

Busyout and Release Commands, Common Input Parameters, and Common

Output Fields.

busyout data-module

busyout data-module extension

This command puts the specified data module in a maintenance busy state,

whether or not it is installed. No call processing may be executed on the data

[primary | secondary] This qualifier is used to specify one of the two

possible links to CDR output devices. Primary is the

default.

backup disk

BACKUP DISK

Processor Command Completion Status

SPE-A Success

SPE-B Success

Command Successfully Completed

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-38busyout disk

modules or over the data channels. A list of all data-modules administered on the

system can be displayed with list data-module. This form gives the extension,

port, type and other data for each data-module. The following table gives the

maintenance object name for each type of data-module listed in the “Type” field

on the list data-module form.

busyout disk

busyout disk C

This command puts the hard disk drive of the Mass Storage System (MSS) into a

maintenance busy state. Placing the disk in a busyout state prevents read and

write access to the disk except when performed by demand maintenance

testing. This command and the release command abort if any other MSS

operation has already begun.

When the release command is issued, all alarms against the disk are

automatically resolved. If the host-adapter is busied out, it must be released

before the disk can be released. When the host-adapter becomes out-of-service

due to test or reset failures and becomes uninstalled, the disk also becomes

uninstalled, and all access by system software and maintenance tests and

commands is blocked.

The cabinet is always 1 and need not be entered. The carrier, a or b, must be

entered only on systems with duplicated SPEs.

busyout ds1-facility

busyout ds1-facility UUCSSf [override]

This command puts a specified DS1 facility of a DS1C Complex into a

maintenance busy state. Each DS1C complex uses from 1 to 4 DS1 facilities.

One of the facilities, called the packet facility, carries the control channel for all

facilities in the complex, all packet traffic, and some circuit connections. The

other facilities carry circuit connections only. Whenever the circuit pack resets,

the packet facility is set on the “a” facility. If system software detects a problem

Type Maintenance Object

adm-t BRI-SET

announcement DAT-LINE

dtdm DIG-LINE

pdm PDMODULE

system-port DAT-LINE

x.25 PGATE-PT

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-39busyout fiber-link

with this facility, it switches the packet and control traffic to another facility. The

busyout command is not allowed on the packet facility unless the override

qualifier is used. When the override is used, all packet and circuit traffic on the

packet facility is switched to one of the other 3 facilities; all traffic that was on the

destination facility before the switch is dropped. There is no way to tell which

facility is carrying the packet and control traffic without attempting to busy it out

If there is only 1 facility left in service on the circuit pack, it cannot be busied out.

In this case, the circuit pack must be busied.

!CAUTION:

Busying out a non-packet facility disrupts all traffic carried on that facility.

Use of the override command to busy the packet facility disrupts all traffic

on the facility to which the packet and control traffic is moved. Which facility

this is cannot be determined in advance.

On critical reliability systems (duplicated PNC) a facility on the active PNC

cannot be busied out. To busyout a facility on the standby PNC, the standby PNC

must first be busied out by busyout pnc.

busyout fiber-link

busyout fiber-link fiber# [a-pnc | b-pnc]

The busyout fiber-link command puts a specified fiber link into a maintenance

busy state. (See Busyout and Release Commands at the beginning of this

chapter). A fiber link is a connection carrying all circuit and packet traffic

between two port networks, two switch nodes, or a port network and a switch

node. A fiber link may contain a DS1 CONV complex used to provide

connectivity to a remote EPN.

!CAUTION:

On systems with simplex PNC, the busyout command is destructive. All

calls and application links carried on the busied out fiber link will be torn

down, and new calls will not be established over the link.

On systems with duplicated PNC, the command is allowed only on a fiber link on

the standby PNC, does not impact service, and requires that the standby PNC

be busied first.

For more information on fiber links, see FIBER-LNK in Chapter 9.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-40busyout host-adapter

Parameters

If neither PNC is specified, the command defaults to a-pnc.

Examples

Duplex PNC: busyout fiber-link 01 b-pnc busyout fiber-link 03 (defaults to

a-pnc)

busyout host-adapter

busyout host-adapter C

The busyout host-adapter command puts the host-adapter circuit on the

MSSNET circuit pack into a maintenance busy state. When the host-adapter is

busied out, the tape and disk devices on the same carrier are also busied out,

and warning alarms with error type 526 are raised against DISK and TAPE. The

tape and disk do remain available for maintenance testing. This command will

abort if any other MSS operation has already begun.

When the host-adapter is out of service due to test failures, or uninstalled due to

a reset failure, the related tape and disk devices are also placed in the

uninstalled state. All access by system software, maintenance tests, and

commands, including reset, are blocked from execution.

fiber# The administered number assigned to the fiber link. (In a system with

duplicated PNC, this represents a fiber link pair.) List fiber-link

displays a list of all fiber links with their numbers, endpoints, and

other useful information.

a-pnc If PNC is duplicated, this identifier is used to distinguish between the

two fibers of a duplicated pair. For non duplicated PNC “a-pnc” is the

only valid qualifier.

b-pnc On a system with duplicated PNC, this identifier distinguishes

between the two fibers of a duplicated fiber pair. This identifier is

invalid on a system with simplex PNC.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-41busyout journal-printer

Parameters

Examples

For more information see the following sections at the beginning of this chapter:

Busyout and Release Commands, Common Input Parameters, and Common

Output Fields.

busyout journal-printer

busyout journal-printer pms-log | wakeup-log

The busyout journal-printer command puts the link to the Property

Management System log or wakeup log printers in a maintenance busy state.

(See Busyout and Release Commands at the beginning of this chapter). When

busied out, the link is dropped and no data transfer can take place over it.

This command can be used to prevent unwanted interference between different

maintenance processes. Maintenance software may put a component that is part

of a link in a busy state, causing link set-up to fail, and resulting in attempts by

the system to reestablish the link. If a maintenance test requires that the

component be idle, frequent attempts at re-setup may delay the recovery of a

faulty component. Busying out the link will prevent re-setup attempts.

Parameters

Examples

busyout journal-printer pms-log

busyout journal-printer wakeup-log

For more information see the following sections at the beginning of this chapter:

Busyout and Release Commands, Common Input Parameters, and Common

Output Fields.

C The cabinet is always 1 and need not be entered. On systems with

duplicated SPEs only, carrier a or b must be entered.

Simplex: busyout host-adapter

Duplicated: busyout host-adapter b

pms-log Busies out the link to the Property Management System printer

wakeup-log Busies out the link to the Wakeup Log printer

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-42busyout link

busyout link

busyout link link#

The busyout link command puts a specified Packet Gateway link in a

maintenance busy state. (See Busyout and Release Commands at the

beginning of this chapter). A link may also be busied out with busyout port using

the address of the PGATE port that supports the link.

!CAUTION:

Busyout of a link drops all calls and packet traffic dependent on that link.

The application, adjunct, or switch connected to the link will be

inaccessible and the link will have to be reestablished later when returned

to service. See status link for more details on links.

Parameters

For more information see the following sections at the beginning of this chapter:

Busyout and Release Commands, Common Input Parameters, and Common

Output Fields.

busyout spe-standby

The busyout spe-standby command lowers the Software State Of Health of the

standby Switch Processing Element (SPE) kept by the standby Duplication

Interface (DUPINT) board to the lowest possible level above non-functional. This

diminishes the chance that an interchange will occur, but does not guarantee

that an interchange will not occur. This command also turns off memory

shadowing. Periodic and scheduled testing

are not

turned off on busied out

objects, but warning alarms with error 18 are generated.

Busyout of the standby SPE is allowed if communication to the standby is down

(handshake failure), but the state of health may not be lowered. Use status spe

to determine the condition of the SPE after the busyout has been entered.

When a busyout of the standby SPE is performed, the software state of health of

the standby SPE is set to the lowest possible level and memory shadowing is

turned off. This is done to lessen the probability that the system will switch to the

standby SPE. However, in some cases a “spontaneous” (hard) interchange of the

SPEs may still occur.

Link# A number (1-16) assigned to the link on the

Communication-Interface Links form.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-43busyout sp-link

This command can be used as a mechanism to turn off memory shadowing of

the standby SPE.

The busyout

will

execute even if the standby SPE state of health is less than

“functional”, memory shadowing is already off, or handshake communication

with the standby is down.

For more information see the following sections at the beginning of this chapter:

Busyout and Release Commands, Common Input Parameters, and Common

Output Fields.

busyout sp-link

The busyout sp-link command puts the system printer link into a maintenance

busy state. Placing the system printer link in a busyout state prevents access to

the system printer.

The system printer link is a link from the switch to an external printer. This link is

created by administering the system printer extension and setting up a call to the

system printer.

For more information, refer to the following sections: Busyout and Release

Commands, Common Input Parameters, and Common Output Fields.

busyout tape

busyout tape C

The busyout tape command puts the tape into a maintenance busy state.

Placing the tape in a busyout state prevents read and write access of the tape

except for that requested by demand maintenance testing. This command aborts

if the host adapter on the same carrier is already busied out.

When the host-adapter is busied out, only the demand maintenance busyout and

test commands are permitted on the attached tape in the same carrier. Reset,

release, scheduled and periodic testing and other system software access are

blocked. In this case, the host-adapter must first be released before the tape can

be released.

When the host-adapter is taken out-of-service due to maintenance test or reset

failures, the tape is also placed in the uninstalled state and all access by system

software, maintenance tests and commands, including reset, are blocked.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-44busyout trunk

Parameters

Examples

Simplex: busyout tape

Duplicated: busyout tape a

For more information, refer to the following sections: Busyout and Release

Commands, Common Input Parameters, and Common Output Fields. This

command will abort if any other MSS operation has already begun.

busyout trunk

busyout trunk group# [/member#]

The busyout trunk command puts an entire trunk group or a single trunk group

member in a maintenance busy state whether it is installed or not. Entering only

the group number busies out all members in the group. (Although not

recommended, entering a group number and a slash (/) without a member

number busies out the member with the lowest-numbered port location.)

Examples

busyout trunk 78

busyout trunk 78/1

For more information see the following sections at the beginning of this chapter:

Busyout and Release Commands, Common Input Parameters, and Common

Output Fields.

cancel hardware-group

In the course of executing test hardware-group, you may find it necessary to

halt the test temporarily or permanently. This can be accomplished with cancel

hardware-group. The canceled test hardware-group command may be

restarted where it left off with resume hardware-group, or another test

hardware-group test may be started. In addition to the cancel hardware-group

command, pressing CANCEL will cancel a hardware-group test executing in the

foreground.

C The cabinet is always 1 and need not be entered. On systems with

duplicated SPEs only, the carrier, a orb, must be entered.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-45cancel hardware-group

The status of a canceled test hardware-group command will show up as

“canceled” on the “status hardware-group” screen.

When a hardware-group test is executing in the foreground with the

“continuously” option and CANCEL is pressed or the cancel hardware-group is

entered, then the hardware-group test is canceled and for security reasons, the

MT running the hardware-group test will be logged off. However, after logging

back on the system, you can still restart the canceled hardware-group test

command with resume hardware-group command.

Scheduled and Periodic Maintenance

When a test hardware-group is entered, all activity related to scheduled

background maintenance, periodic background maintenance, and data audits is

suspended for the duration of the execution of the test hardware-group

command. All activity related to scheduled background maintenance, periodic

background maintenance, and data audits will restart if the “test

hardware-group” command is canceled.

Status Hardware-Group

The state of a canceled test hardware-group command is displayed by the test

hardware-group command and the state shows up as canceled.

All Ports Option

When test hardware-group all-ports is canceled, the internally generated port

translations for ports that are otherwise untranslated are removed. If resume

hardware-group is then entered, only customer-administered ports will

subsequently be tested. resume does

not

reinstate the port translations that

were removed by the cancel.

Output

If a test hardware-group command started in the background is successfully

canceled with cancel hardware-group, this response is displayed:

Hardware-group command successfully canceled

If a test hardware-group command executing in the foreground is successfully

canceled with a cancel hardware-group command from another terminal, the

following response will be displayed on the terminal where the hardware-group

command was executing:

Hardware-group command aborted with cancel

command entered from another terminal

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-46change circuit packs

change circuit packs

change circuit-packs UU

This command allows the user to administratively add, change or remove circuit

packs that are to be inserted into port, expansion control, and switch node

carriers. It is used to configure the system when the circuit packs have not yet

been physically inserted. This command does

not

support displaying or

modifying the boards in the PPN control carrier.

Parameters

Output

An input form is displayed containing the following fields:

The following display shows a typical result when change circuit-packs 1 is

entered on a system with simplex SPE and a Center Stage Switch (cabinet 1 is

always 5-carrier).

UU The number of the cabinet containing the circuit packs to be modified.

Default is 1.

Cabinet The administered number of the cabinet (1-22).

Cabinet

Layout Type of cabinet.

Carrier Each page of this form reports the information for 1 carrier.

This field indicates the letter designation of the carrier

displayed on the current page.

Carrier

Type The function of the carrier: (port, processor, switch-node,

dup-switch-node, or not-used).

Slot The carrier slot numbers (00 - 21).

Code The TN or UN part number of the circuit pack. This number

identifies the circuit pack type to system software.

Sfx The letter suffix of the circuit pack, if applicable.

Name The name of the circuit pack. This field aids in entering the

circuit pack codes.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-47change circuit packs

change circuit-packs 1 Page 1 of 5

CIRCUIT PACKS

Cabinet: 1 Carrier: A

Cabinet Layout: five-carrier Carrier Type: processor

*** PROCESSOR BOARDS NOT ADMINISTERABLE IN THIS SCREEN ***

change circuit-packs 1 Page 2 of 5

CIRCUIT PACKS

Cabinet: 1 Carrier: B

Cabinet Layout: five-carrier Carrier Type: not-used

Slot Code Sfx Name Slot Code Sfx Name

00: 11:

01: 12:

02: 13:

03: 14:

04: 15:

05: 16:

06: 17:

07: 18:

08: 19:

09: 20:

10: 21:

’#’ indicates circuit pack conflict.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-48change circuit packs

change circuit-packs 1 Page 3 of 5

CIRCUIT PACKS

Cabinet: 1 Carrier: C

Cabinet Layout: five-carrier Carrier Type: port

Slot Code Sfx Name Slot Code Sfx Name

00: 11: TN754 DIGITAL LINE

01: TN748 C TONE DETECTOR 12: TN753 DID TRUNK

02: 13: TN742 ANALOG LINE

03: 14: TN760 C TIE TRUNK

04: TN771 C MAINTENANCE/TEST 15: TN747 B CO TRUNK

05: TN748 B TONE DETECTOR 16: TN742 ANALOG LINE

06: TN767 DS1 INTERFACE 17: TN556 BRI LINE

07: TN742 ANALOG LINE 18: TN742 ANALOG LINE

08: TN762 B HYBRID LINE 19:

09: TN742 ANALOG LINE 20: TN754 DIGITAL LINE

10:

’#’ indicates circuit pack conflict.

change circuit-packs 1 Page 4 of 5

CIRCUIT PACKS

Cabinet: 1 Carrier: D

Cabinet Layout: five-carrier Carrier Type: port

Slot Code Sfx Name Slot Code Sfx Name

00: 11:

01: 12: TN722 B DS1 TIE TRUNK

02: 13: TN760 C TIE TRUNK

03: TN750 B ANNOUNCEMENT 14:

04: 15: TN754 DIGITAL LINE

05: 16:

06: 17: TN742 ANALOG LINE

07: TN747 B CO TRUNK 18:

08: TN753 DID TRUNK 19:

09: TN742 ANALOG LINE 20:

10: 21:

’#’ indicates circuit pack conflict.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-49change fiber-link

change fiber-link

change fiber-link fiber#

The change fiber-link command changes the translation data associated with

an existing fiber link. On critical reliability systems (duplicated PNC), each fiber

link is duplicated and exists as a pair. When PNC duplication is enabled, only the

fields on pages 2 and 3 (the DS1 CONV complex attributes) can be changed.

Translation data is not changed until the Enter key is pressed. Pressing CANCEL

any time before pressing Enter to enter the changes returns you to the command

line without changing any translation data.

When you enter a command that changes translation data, two checks are made:

■You must have permission to administer the feature.

■No other user may be executing a change, add, or remove fiber-link

command.

On a simplex PNC or fully operational duplex PNC, you must remove a fiber and

add it again to change the endpoint board locations.

change circuit-packs 1 Page 5 of 5

CIRCUIT PACKS

Cabinet: 1 Carrier: E

Cabinet Layout: five-carrier Carrier Type: switch-node

Slot Code Sfx Name Slot Code Sfx Name

11:

01: TN570 EXPANSION INTF 12:

02: TN573 SWITCH NODE INTF 13:

03: TN573 SWITCH NODE INTF 14:

04: 15:

05: 16:

06: 17:

07: 18:

08: 19: TN573 SWITCH NODE INTF

09: 20: TN573 SWITCH NODE INTF

10: TN572 SWITCH NODE CLOCK 21:

’#’ indicates circuit pack conflict.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-50change fiber-link

Parameters

Examples

change fiber-link 21

Output

The following fields appear on Page 2 when a DS1 CONV complex is

administered on the fiber link. Only the DS1 CONV complex

attributes

are

administered here. The circuit pack itself is administered by change circuit

pack. Entries on Page 2 represent the A-PNC. If the PNC is duplicated, these

fields are repeated on Page 3 for the B-PNC. Page 3 fields are display-only, and

can be changed only by changing their counterpoints on Page 2.

number The administered number (1-27) associated with a fiber link or, on

a duplicated PNC, with a fiber link pair.

Fiber Link # This display-only field shows the identifying number of the

fiber link entered on the command line.

Board Location The physical address (cabinet-carrier-slot) of the circuit

packs comprising the two endpoints (ENDPOINT-1 and

ENDPOINT-2) of the fiber link.

Board Type This display-only field shows the type of circuit pack

administered at each endpoint (“ei” or “sni”).

DS1 Converter? y indicates that a DS1C Converter Complex is used on this

link to remotely locate a port network. If this is the case, a

second page displays for administration of the DS1C

Complex attributes.

Board Location This field under the heading DS1C-1 is used to define the

physical location of the converter board connected to

ENDPOINT-1. It is a data entry field consisting of the

board’s physical address by cabinet-carrier-slot. When the

location is entered, validation is performed to ensure that

the board has been administered and is of the correct type

(DS1 CONV).

DS1 Converter

Facilities The fields under this heading define attributes of the four

DS1 facilities (A, B, C, D) that can be connected to the

DS1 CONV.

Facility Installed? This specifies (y or n) whether the indicated facility has

been provided and installed. Facility A is required for the

DS1 CONV Complex.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-51change fiber-link

The line equalization setting defaults to the median value of 3. This setting

remains in effect until changed by administration. Incorrect equalizer settings

may cause a higher error rate on the DS1 facility.

Passes Far-end

Clock? This specifies whether the DS1 CONV can use the timing

of the received signal as a clock source (as when passing

timing from a master PN to a slave PN. If the DS1 signal

does not come directly from the far-end DS1 CONV board

or the network, n should be entered. (For example, when

using a ‘combined’ facility in which the signal is converted

from digital to analog and back to digital.)

Digital Data

Compatible? This specifies whether the facility is suitable for

transmission of digital data. Facility A must be so and this

field cannot be changed. If Customer Premises Equipment

that alters digital data exists on this facility (for example, a

channel expansion multiplexer or a combined DS1 facility),

n should be entered. (Thus, a multiplexer cannot be

installed on facility A).

DS1C-1 Line

Compensation This specifies the type of line compensation or line

equalization for each facility of the DS1 CONV connected

to ENDPOINT-1. Valid entries are 1 to 5. Meanings of these

entries are shown in Table 8-6.

Table 8-6. DS1 Line Equalization Settings

Equalizer Setting

Distance to DSX-1 Interface (feet)

22 AWG ABAM and 24 AWG PDS 26 AWG PDS

1 1 to 133 0 to 90

2 133 to 266 90 to 180

3 266 to 399 180 to 270

4 399 to 533 270 to 360

5 533 to 655 360 to 450

DS1 CONV-2 Line

Compensation: Same as the above for ENDPOINT-2 of the DS1 CONV

Complex.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-52change synchronization

The following display shows a typical result when change fiber-link 1 is entered

on a system with simplex PNC and Center Stage Switch.

change synchronization

Zero Code

Suppression: Specifies the line coding format for each facility. Valid

entries are: zcs and b8zs. There are 2 line coding

options supported by the DS1 Interfaces to meet

ones-density requirements in the data stream. Zero

Code Suppression (ZCS) line coding is the default and

is in place following an initialization until changed by

administration. Note that either line coding option may

be used on the DS1 Interface that carries the packet

time slots.

Framing Mode: Specifies the data framing format (esf or d4) used on

the facility. It is initialized to ESF. In this mode, an

automatic selection process is executed until either the

DS1 Interface is brought into frame, or an Options

CCMS message is received by the framing options

master. Once options are set by administration, they

remain fixed on the framing option master until the board

is again initialized, reset, or sent new options. The

framing option on the framing option slave Converter

Board can change to track the framing option master’s

option.

change fiber-link 1 Page 1 of 1

FIBER LINK ADMINISTRATION

Fiber Link #: 1

ENDPOINT-1 ENDPOINT-2

(A-PNC) (A-PNC)

Board Location: 01E01 Board Location: 01E02

Board Type: ei Board Type: sni

Is one endpoint remoted via DS1 Converter Complex? n

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-53change synchronization

This command sets the source and type of timing signals to be used by the

system.

The system uses a hierarchy of timing sources to synchronize data transmission

throughout the system. Stratum 3 Synchronization uses an external Stratum 3

Clock connected to a port network (usually the PPN) which has a TN780

Tone-Clock circuit pack. Stratum 4 Synchronization uses either external signals

received through a DS1 interface circuit pack or a master Tone-Clock within the

system. (Throughout this discussion, the term DS1 interface includes TN464

UDS1 circuit packs.)

A DS1 interface administered as a primary or secondary synchronization source

cannot be removed on the DS1 circuit pack form or the regular circuit pack form.

The synchronization must first be changed or removed.

Output

Stratum 4 Fields

Stratum 3 Fields

The following display shows a typical result when change synch is entered with

stratum 4 synchronization in use.

Stratum: This field specifies the stratum number, 3 or 4, of the

synchronization source used by the system. The stratum

number determines which other fields are displayed on the

screen form.

Primary: The location of the DS1 Interface circuit pack that provides

the preferred source of timing reference signals. A blank

indicates that no external timing source is used.

Secondary: The location of the DS1 Interface circuit pack that provides

the backup source of timing reference signals to be used if

the primary source fails. It must be in the same port network

as the primary source. A blank indicates that no backup

external timing source is used.

Location: The locations of all administered DS1 circuit packs in the

system.

Name: The user-defined name, if any, administered on the DS1

circuit pack form.

Slip: This field indicates whether there are any slip alarms logged

against the circuit pack.

Port Network: This display-only field gives the number of the port network

connected to the Stratum 3 clock (normally 1, the PPN).

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-54change system-parameters maintenance

The following display shows a typical result when change synch is entered with

stratum 3 synchronization in use.

change system-parameters

maintenance

change system-parameters maintenance

The maintenance-related system parameters form specifies and displays

scheduled maintenance operations and maintenance support functions.

This form activates and deactivates INADS alarm origination when performing

repairs. To deactivate alarm origination:

1. Make a note of the current entries in the Alarm Origination and CPE fields

so you can restore them when you are done.

2. Change the Alarm Origination to OSS Numbers field “neither.”

3. Change the CPE Alarm Activation Level field to “none.”

4. If daily scheduled maintenance must be prevented from starting during a

maintenance procedure, set the Start Time field to a time after the

session will end. If daily Scheduled Maintenance is already running and

needs to be shut off, set the Stop Time field to one minute after the

current time.

5. Press Enter and verify that the screen displays the message:

Command successfully completed

NOTE:

For earlier releases of system software, disable Cleared Alarm

Notification and Restart Notification before submitting the form.

NOTE:

When finished working on the switch be sure to return all fields to

their original settings.

change synchronization Page 1 of 1 SPE A

SYNCHRONIZATION PLAN

SYNCHRONIZATION SOURCE (DS1 circuit pack location)

Stratum: 3

Port Network: 1

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-55change system-parameters maintenance

Examples

change system-parameters maintenance

Output

An input form is displayed with the following fields. Defaults for data entry fields

are listed in parentheses.

Operations Support Parameters:

Product

Identification This is a 10-digit number starting with 1 that identifies the

switch to an Operations Support System (OSS), for example,

INADS.

First OSS

Telephone

Number

The first telephone number that the switch uses to report

alarms to, for example, INADS or Trouble Tracker. The

number must be obtained from the National Customer

Support Center (NCSC) or the TSC. # and * are not allowed

in the telephone number.

Abbrev Alarm

Report Enables the Abbreviated Alarm Report feature for the first

OSS. (yes)

Second OSS

Telephone

Number

The second telephone number that the switch uses to report

alarms to, for example, INADS or DEFINITY SNMP. The

number must be obtained from the National Customer

Support Center (NCSC) or the TSC. # and * are not allowed

in the telephone number.

Abbrev Alarm

Report Enables the Abbreviated Alarm Report feature for the

second OSS. (no)

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-56change system-parameters maintenance

Alarm

Origination to

OSS Numbers

Indicates one of four options for alarm origination (neither):

■If this field is set to “both,” all Major and Minor alarms

result in an automatic call to both OSS telephone

numbers. Both OSS telephone numbers must be

administered.

■If this field is set to “first-only,” all Major and Minor alarms

result in an automatic call to the first OSS number only.

The switch does not call the second OSS telephone

number even if the number is administered. The first

OSS telephone number must be administered

■If this field is set to “neither,” alarm origination does not

take place. Warning alarms are not reported to either

numbers.

■If this field is set to “second-as-backup,” all Major and

Minor alarms result in an automatic call to the first OSS

telephone number. If calling the first OSS telephone

number fails four attempts, the switch starts to call the

second OSS telephone number as a backup until calling

the first OSS telephone number becomes successful.

Both OSS telephone numbers must be administered.

Before Release 5, the name of this field is “Alarm Origination

Activated.” If Alarm Origination is deactivated, both Cleared

Alarm Notification and Restart Notification are disabled,

even though they may still be activated in the administration.

Cleared Alarm

Notification Enables the switch to originate a call to the OSS and send

an alarm resolution message whenever all previously

reported Major and Minor alarms are resolved. Alarm

Origination must be activated in order for Cleared Alarm

Notification to work. (no)

Restart

Notification Enables the switch to originate a call to the OSS and report

any system restarts caused by problems with the switch.

Suspension

Threshold The threshold for suspending Cleared Alarm Notification.

Some problems may cause alarms to be generated and

then resolved repeatedly. To detect these problems (by not

sending additional Cleared Alarm notifications to indicate a

problem- free system), the switch suspends Cleared Alarm

Notification when it has reported this administrable number

of Cleared Alarm notifications in a 24 hour period. A

suspended Cleared Alarm Notification is only enabled again

with a successfully completed “logoff” command, a system

reset, or when the threshold is changed. This field is

irrelevant if Cleared Alarm Notification or Alarm Origination is

disabled. The possible range of threshold values is between

1 and 15.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-57change system-parameters maintenance

Scheduled Maintenance

A series of maintenance tests and operations runs automatically every day

according to the schedule and settings specified in Table 8-7

Test Remote

Access Port Specifies whether testing of the remote access port on the

SYSAM circuit pack is enabled. This field should be set to

"yes" whenever there is an INADS line connected to the

switch and there is a maintenance contract in effect so that

alarm origination capability is maintained.

If no equipment is connected to the remote access port, or if

a trunk for remote access and alarm origination is not

provided, running tests on the remote access port on the

SYSAM results in test failures. This causes unnecessary

maintenance alarms and allows potentially destructive tests

to be run. Setting this field to “no” prevents this.

CPE Alarm

Activation

Level

Indicates the minimum level (Major, Minor or Warning) at

which the Customer-Provided Equipment (CPE) alarm is

activated. If the level is ‘‘none,’’ the CPE does is not

activated for any alarm. (none)

NOTE:

The CPE alarm is always activated when the switch

goes into Emergency Transfer, regardless of the CPE

Alarm Activation Level setting.

Customer

Access to

INADS Port

Provides the capability to prohibit access to system

administration and maintenance interface, via the INADS

port when using customer login ID’s. This field can only be

activated Lucent through system-parameters maintenance

administration.(no)

Table 8-7. Schedules and Settings for Maintenance Tests

Start Time The hour and minute in 24-hour notation at which daily

scheduled maintenance will begin running.

Stop Time The hour and minute when scheduled daily maintenance will

stop running. If any daily maintenance operations are not

completed by this time, the system will note where in the

sequence it stopped and perform those operations during

the next scheduled daily maintenance.

Continued on next page

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-58change system-parameters maintenance

Daily

Maintenance This display-only field simply represents the series of tests

that are always run by maintenance software as part of daily

maintenance.

Save

Translation This field indicates on which days translation data in memory

will automatically be saved to the Mass Storage System disk

and/or tape devices during scheduled maintenance. The

save operation is first made to disk, followed by a disk

backup to tape. On systems with duplicated SPEs, translation

data is saved on both SPEs. Valid entries are daily, days of

the week, or no. "No" specifies that no automatic saves are to

be executed. (daily)

Control

Channel

Interchange

Each port network has a pair of TDM busses called A and B,

each of which has a set of time slots dedicated to use by the

control channel. At any one time, the control channel in each

PN is carried on only one of the two busses. This field

indicates on which days the control channel in each port

network will be switched from one of the paired TDM busses

to the other. Valid entries are daily, days of the week, or no.

"No" specifies that no interchange be executed. (no)

System

Clocks

Interchange

On High and Critical Reliability systems, this option causes a

Tone-Clock interchange in each port network with duplicated

Tone-Clock circuit packs. Each port network interchanges

into the standby Tone-Clock for 20 seconds and then back to

the Tone-Clock that was originally active. This field indicates

on which days the interchanges are to take place. Valid

entries are daily, days of the week, or no. "No" specifies that

interchanges be executed. (no)

The system performs a Tone-Clock interchange, making the

stand by Tone-Clock active. The newly active Tone-Clock

circuit pack is tested and, while active, provides system

clocks for the port network in which it resides. The system then

interchanges back to the originally active Tone-Clock circuit

pack.

SPE

Interchange On systems with duplicated SPEs, this field indicates on

which days an SPE interchange will be executed during

scheduled maintenance. Valid entries are daily, days of the

week, or no. "No" specifies no scheduled interchanges. (no)

Table 8-7. Schedules and Settings for Maintenance Tests — Continued

Continued on next page

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-59change system-parameters maintenance

Minimum

Threshold for

TTRs

When the number of touch tone receivers (TTRs) in service

falls below this number (4 to 200), a WARNING alarm is

raised against TTR-LEV (see TTR-LEV in Chapter 9,

‘‘ABRI-PORT (ASAI ISDN-BRI Port)’’). These are also known

as dual-tone multifrequency receivers (DTMRs). There are 4

TTRs on each TN748 Tone Detector circuit pack, and up to

50 TN748s in a system. To alarm the first occurrence of a TTR

being taken out of service, set this field to 4 times the number

of TN748s. If this number is set to more than three less than

the total number of TTRs, a port network with only one TN748

could lose all of its TTRs before this alarm is raised.

Minimum

Threshold for

CPTRs

When the number of call progress tone receivers in service

falls below this number (2 to 100), a WARNING alarm is

raised against TTR-LEV (see TTR-LEV in Chapter 9,

‘‘ABRI-PORT (ASAI ISDN-BRI Port)’’). These are also known

as general purpose tone detectors (GPTDs). There are 2

CPTRs on each TN748 Tone Detector circuit pack, and up to

50 TN748s in a system. To alarm the first occurrence of a

CPTR being taken out of service, set this field to 2 times the

number of TN748s. If this number is set to more than one less

than the total number of TTRs, a port network with only one

TN748 could lose all of its CPTRs before this alarm is raised.

Minimum

Threshold for

Call Classifier

Ports

When the number of call classifier ports (CLSFY-PTs) in

service falls below this number, a WARNING alarm is raised

against TTR-LEV (see TTR-LEV in Chapter 9). Valid entries

are 1 to 200. There are 8 ports on each TN744 Call Classifier

circuit pack, and up to 25 TN744s in a system. To alarm the

first occurrence of a CLSFY-PT being taken out of service, set

this field to 8 times the number of TN744s. If this number is

set to more than 7 less than the total number of CSLFY-PTs in

the system, a port network with only one TN744 could lose all

of its CLSFY-PTS before the alarm is raised. If there are no

TN744s in the system, leave this field blank.

Table 8-7. Schedules and Settings for Maintenance Tests — Continued

Continued on next page

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-60change system-parameters maintenance

Test Type

100, Test

Type 102,

Test Type 105

An extension assigned to receive tie-trunk calls from other

switches with test line origination capability. The system

responds by sending a sequence of test tones. Test Type

100 tests far end to near end loss and C-message by

sending:

■5.5 seconds of 1004 Hz tone at 0dB

■Quiet until disconnect; disconnect is forced after one

minute

Test Type 102 tests far end to near end loss by sending:

■9 seconds of 1004 Hz tone at 0dB

■1 second of quiet

■This cycle is repeated until disconnect; disconnect is

forced after 24 hours.

Test Type 105 tests 2-way loss, gain slope, and C-message

and C-notch noise by sending:

■nine seconds of 1004 Hz at -16dB

■one second of quiet

■nine seconds of 404 Hz at -16dB

■one second of quiet

■nine seconds of 2804 Hz at -16dB

■30 seconds of quiet

■one half second of Test Progress Tone (2225 Hz)

■approximately 5 seconds of quiet

■forced disconnect

ISDN-PRI Test

Call Extension The extension used by a far-end ISDN node to place a call to

the system to test the ISDN-PRI trunks between the far-end

and the system.

ISDN-BRI

Service SPID This field shows whether or not the link is associated with the

Service SPID. If the link is associated with the Service SPID,

the field contains a number from “0 to 99999” this number is

the test spid (See

SPID Facility Test

chapter 9

under

BRI-SET

MO) otherwise, this field is blank. Service SPID is a

feature used by the system technician to check building

wiring between the switch and the BRI endpoint.

Table 8-7. Schedules and Settings for Maintenance Tests — Continued

Continued on next page

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-61change system-parameters maintenance

DSO

Loop-Around

Test Call

Extension

The extension used by the network service provider to set up

a DSO loop around connection for testing non ISDN DS1

trunks

The DSO Loop-Around Test Call feature is used primarily for

testing DSO channels associated with non ISDN-PRI trunks.

The loop-around is activated by dialing the test extension

number. Multiple DSO Loop-Around connections can be set

up by placing multiple calls to the loop-around extension.

For more information see chapter 6 (Facility Test Calls).

Loss Plan Use only when extra loss is required to maintain quality of

transmission on conference calls. Leave this field blank if no

extra loss is required. If extra loss is required, enter digits as

shown below.

Number Of

Parties To Be

Conferenced Enter Digit

SPE

Optional

Boards:

These fields indicate whether a Disk circuit pack is present in

the system, and which Packet Interface slots are administered.

If a Packet Interface circuit pack is physically present, the

corresponding Packet Interface field is set to y when the

system boots, and no change to that field is allowed. If the

system is equipped with duplicated SPEs, a Packet Interface

field is set to y when either SPE carrier contains a Packet

Interface circuit pack in the corresponding position. If a Packet

Interface circuit pack is not present, then the value for the

Packet Interface field is read from translation data stored on

disk or tape. If the field is set to n, a Packet Interface circuit

pack may be administered by changing the corresponding

Packet Interface field to y.

Table 8-7. Schedules and Settings for Maintenance Tests — Continued

Continued on next page

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-62change system-parameters maintenance

The following display shows a typical result when change system-parameters

maintenance is entered.

change system-parameters maintenance Page 1 of 2

MAINTENANCE-RELATED SYSTEM PARAMETERS

OPERATIONS SUPPORT PARAMETERS

Product Identification: 1000000000

First OSS Telephone Number: 5551212 Abbrev Alarm Report? y

Second OSS Telephone Number: 5551213 Abbrev Alarm Report? n

Alarm Origination to OSS Numbers: both

Cleared Alarm Notification? y

Restart Notification? y

Test Remote Access Port? n

CPE Alarm Activation Level: none

Customer Access to INADS Port? n

Repeat Dial Interval (mins): 7

SCHEDULED MAINTENANCE

Start Time: 22: 00 Stop Time: 04: 00

Daily Maintenance: daily Save Translation: daily

Control Channel Interchange: no System Clocks Interchange: no

SPE Interchange: no

change system-parameters maintenance Page 2 of 2

MAINTENANCE-RELATED SYSTEM PARAMETERS

MAINTENANCE THRESHOLDS ( Before Notification )

Minimum Threshold for TTRs: 4 Minimum Threshold for CPTRs: 1

Minimum Threshold for Call Classifier Ports: _

TERMINATING TRUNK TRANSMISSION TEST (Extension)

Test Type 100: Test Type 102: Test Type 105:

ISDN MAINTENANCE

ISDN-PRI TEST CALL Extension: _____ ISDN BRI Service SPID: _____

DS1 MAINTENANCE

DSO Loop-Around Test Call Extension: _____

LOSS PLAN (Leave Blank if no Extra Loss is Required)

Minimum Number of Parties in a Conference Before Adding Extra Loss: _____

SPE OPTIONAL BOARDS

Disk? y Packet Intf1? y Packet Intf2? n Packet Intf3? n

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-63clear errors

clear errors

The clear errors command moves all errors and resolved alarms to the cleared

errors list, thereby making room for new incoming error messages which might

otherwise be dropped. This command does not clear active alarms from the

alarm log. Cleared error entries are the first entries overwritten when additional

room is needed to log new entries. To retrieve cleared errors, use display errors

clear.

NOTE:

Use this command with care. Cleared data will be lost if the logs fill up.

clear firmware-counters

clear firmware-counters UUCSS | a-pnc | b-pnc

This command clears the firmware error counters on the specified circuit

packs(s). This command is valid only for SNI, SNC, and DS1C board locations.

When a- or b-pnc is specified, all such circuit packs in a single PNC can be

cleared at once. On a Critical Reliability systems (duplicated PNC), only circuit

packs on a standby PNC that is busied out can be cleared.

This command is useful for quickly clearing lingering alarms after a hardware

problem has been fixed. (Test clear commands do not clear alarms on SNI,

SNC, and DS1C circuit packs.)

!WARNING:

This command can mask actual hardware problems since firmware is

cleared and appears as if no problems were ever encountered.

Parameters

For more information see Common Output Fields at the beginning of this chapter.

clear pgate-port

clear pgate-port UUCSSpp

UUCSS The specified location must be occupied by an SNI, SNC or DS1C circuit

pack. All circuit packs on the standby PNC can be cleared at once by

specifying a- or b-pnc. To do so, the standby PNC must first be busied out.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-64disable suspend-alm-orig

The clear pgate-port command clears the hardware error counters associated

with the specified packet gateway port by performing a reset. If the number of

the link assigned to the port is known, clear link accomplishes the same thing.

For more information see Common Input Parameters and Common Output Fields

at the beginning of this chapter.

disable suspend-alm-orig

This command disables one or more active Suspend Alarm Origination entries.

Synopsis

disable suspend-alm-orig (board location).

Examples

disable suspend-alm-orig 1C03

disable suspend-alm-orig 1E07

Description

This command disables one or more active Suspend Alarm Origination entries

from the Suspend Alarm Origination table. This command disables all entries

(boards and ports) matching the specified physical board location.

NOTE:

A port entry cannot be disabled with this command. Allowing for different

ways to disable one or more entries greatly increases the complexity of

updating and displaying the Suspend Alarm Origination table.

Defaults

None.

Parameter

Help Messages

N is the maximum number of cabinets in the switch:

board

location This parameter specifies the physical board location of the

hardware component that has been replaced or corrected. A

port location is not supported because of it complexities.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-65display alarms

Enter board location:[cabinet(1-N)];

carrier(A-E);slot(0-20)

Output

The command returns one of the following messages:

1. If the board specifier is not valid:

Board invalid

2. If no entries can be disabled in the Suspend Alarm Origination table:

Entry not found; no entries disabled

Feature Interactions

None.

display alarms

This command will display an options form which allows the technician to choose

which alarms are to be displayed.

Synopsis

display alarms

[print | schedule]

Permissions

The following default logins may execute this command: system technician,

inads, cust, rcust, bcms, init, browse.

Examples

display alarms display alarms print display alarms schedule

Description

The display alarms command brings up a hardware alarm report. This screen

allows the technician various different options to select which alarms will be

displayed on the alarm report. There are no parameters entered on the command

line, parameters are selected on the hardware alarm report form instead.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-66display alarms

An alarm can occur for any hardware object when it has been determined by the

maintenance subsystem that a problem definitely exists. The impact of the

problem is indicated by the alarm type:

Warning alarm—A problem which has been deemed important enough to log, or

may be external to the system, but not severe enough to cause a noticeable

degradation of service.

Minor alarm—A problem which could disable a local area of the system and so

noticeably degrade the system.

Major alarm—A problem which widely degrades the system and seriously

impairs service. This would cause a call to be placed to INADS.

A resolved alarm is a problem which has been corrected, and the alarmed

component of the system is functioning correctly again. The alarm will be

stamped with a resolved date and time, indicating that it is no longer a concern

(any errors associated with the alarms will also be considered resolved).

Defaults

All alarms will be displayed.

Parameters

Help Messages

If the technician presses HELP after entering “display alarms” the following

message will be displayed:

[’print’ or’schedule’]

print This will cause the report to be printed if a printer is linked to the

SAT.

schedule When the “schedule” option is specified, the command is

validated and then a scheduling form is displayed to allow the

technician to schedule execution of the command. The command

is then placed in the command queue and is executed at the

specified time. The information displayed by the command is sent

to the system printer instead of the screen. Refer to the Report

Scheduler and System Printer feature specification [4] for more

details.

There are no parameters entered on the command line,

parameters are selected on the hardware alarm report form

instead.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-67display alarms

Error Messages

If during the execution of a command a resource problem occurs that requires

the user to restart the command, then the following message will be displayed:

Command resources busy; Press CANCEL to clear, and then resubmit

If all of the available maintenance resources are currently in use, then the

following message will be displayed:

All maintenance resources busy; try again later

From Input

After entering the command display alarms, the system technician will be

presented with an options form.

Alarm Types The type of alarm to be displayed is specified by placing a “y”

or “n” in the alarm type fields. The technician can choose a

combination of active alarms, major, minor, warning, or

resolved alarms.

Interval Display alarm records for the last (m)onth, last (h)our, last

(d)ay, last (w)eek, or (a)ll. The default is all.

From Display alarm records from the time specified by

mm/dd/hh/mm, where mm is the month, dd is the day, hh is

the hour and mm is the minute. If no “from” date is entered,

then no checking is done. This will give the user all the alarms

active since a month prior to the current time.

To Display alarm record to the time specified by mm/dd/hh/mm,

where mm is the month, dd is the day, hh is the hour and mm

is the minute. If no “to” date is entered, any alarm which is

active after the from date will be selected.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-68display alarms

Equipment

Type The technician can choose between seven different

equipment types. If there is no input to any of these fields, the

system will default to all the equipment. The user can select

one of the following fields:

■Cabinet: This allows the technician to display all alarms

associated with a particular cabinet. Alarms for a cabinet

are referenced by a number ranging from 1 to 3 which is

assigned during cabinet administration.

■Port Network: This allows the technician to display all

alarms associated with a particular port network. Alarms

for a port network are referenced by a number ranging

from 1 to 3.

■Board Number: This allows the technician to choose all

alarms associated with a particular circuit pack for

display. Alarms for a (cabinet-carrier-slot). If the cabinet

number is omitted, the system will default to 1.

■Port: This allows the technician to choose all alarms

associated with a particular port on a circuit pack for

display. Alarms for a port circuit are referenced by port

location (cabinet-carrier-slot-circuit). If the cabinet

number is omitted, the system will default to 1.

■Category: Alarms for a particular equipment category.

■Extension: Alarms associated with an extension number.

■Trunk (group/member): The technician can choose to

view all alarms associated with a particular trunk group or

trunk group member. The group identifier should be

entered to view all alarms associated with a trunk group

XXX/___. The group identifier and member identifier

should both be entered to view all alarms associated with

a specific trunk group member XXX/XXX.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-69display alarms

Field Help

Following are the help messages that the system technician will see upon

tabbing to the specified field and pressing the HELP key.

Active? n(o) y(es)

Resolved? n(o) y(es)

Major? n(o) y(es)

Minor? n(o) y(es)

Warning? n(o) y(es)

Interval: The interval field help is a list of objects. This list includes:

m(onth), h(our), d(ay), w(eek), a(ll).

From (month) “Enter month between 1-12

From (day) Enter day between 0-31

From (hour) Enter hour between 0-23

From (minute) Enter minute between 0-59

To (month) Enter month between 1-12

To (day) Enter day between 0-31

To (hour) Enter hour between 0-23

To (minute) Enter minute between 0-59

Cabinet: Enter cabinet number (1-3)

Port Network: Enter port network number (1-3)

Continued on next page

display alarms Page 1 of 1

ALARM REPORTS

The following options control which alarms will be displayed.

ALARM TYPES

Active? y_ Resolved? n_

Major? y_ Minor? y_ Warning? y_

REPORT PERIOD

Interval: m_ From: __/__/__:__ To: __/__/__:__

EQUIPMENT TYPE ( Choose only one, if any, of the following )

Cabinet: ____

Port Network: __

Board Number: _______

Port: ________

Category: ________

Extension: _____

Trunk ( group/member ): ___/___

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-70display alarms

Field Error Messages

Following are the error messages that display on the screen. The messages

display when the system technician tabs out of a field and the validation routines

are executed. In the following messages, an “x” represents the character that

was entered by the user.

Board Number: Enter 5 character board number;

cabinet(01-3):carrier(A-E):slot(00-20)

Port: Enter port number; [cabinet(1-3)]: carrier(A-E):

slot(0-20): circuit(01-31)

Category: The category field help is a list of objects. This list includes the

following:

adm-conn, announce, bri/asai, card-mem, cdr,

data-mod, detector, dup-spe, environ, exp-intf,

ext-dev, generatr, inads-link, infc, maint, mbus,

memory, misc, mnt-test, modem, netcon, pkt,

pkt-ctrl pms/jrnl, procr, quick-st s-syn, stabd,

stacrk, stations, sys-prnt, tape, tdm, tone,

trkbd, trkcrk, trunk, wideband.

For a table describing the category entries in greater detail, see the

display errors command.

Extension: Enter assigned extension

Trunk (group) Enter group number between 1-99

Trunk (member) Enter group member between 1-99, or blank

Body

Active? “x” is an invalid entry; please press HELP

Resolved? “x” is an invalid entry; please press HELP

Major? “x” is an invalid entry; please press HELP

Minor? “x” is an invalid entry; please press HELP

Warning? “x” is an invalid entry; please press HELP

Interval: “x” is an invalid entry; please press HELP

From (month) Entry must be all digits

From (day) Entry must be all digits

Continued on next page

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-71display alarms

Output

After valid options are entered by the technician, an alarm report is displayed.

The data displayed on this form will be:

From (hour) Entry must be all digits

From (minute) Entry must be all digits

To (month) Entry must be all digits

To (day) Entry must be all digits

To (hour) Entry must be all digits

To (minute) Entry must be all digits

Cabinet: Entry invalid

Port Network: Entry invalid

Board Number: Board invalid

Port: Port invalid

Category: “xxxxxxxx” is an invalid entry; please

press HELP

Extension: Entry must be all digits

Trunk (group) Entry must be all digits

Trunk (member) Entry must be all digits

Port The location of the alarmed object. For installed circuit packs,

the location is displayed as cabinet-carrier-[slot]-[circuit].

For Port Network-related objects, the location is displayed as

PN UUB, where “UU” is the Port Network number and B is the

bus (A or B). For Fiber Link-related objects, the location is

displayed as x a-PNC where “x” is the Fiber Link number and

“a” is the PNC side (A or B). This is the same identifier as used

by the alarm log.

Maintenance

Name The logical name of the MO which has been alarmed.

On Brd Whether the fault detected is on the associated circuit pack, or

an off board element connected to the circuit pack.

Continued on next page

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-72display alarms

Alt Name The alternate means of identifying the MO. This field contains

the extension when the object is a station, and it contains

xxx/yyy when the object is a trunk, where xxx is the trunk

group number and yyy is the member number. It contains

P/xxx when the object is a private CO line, where xxx is the

private CO line group number.

Alarm Type MAJOR, MINOR, or WARNING. This is an indicator to the

seriousness of the alarm raised.

Service State RDY (ready for service), OUT (out of service), or IN (in

service). This is the current service state of the station and

trunk ports shown. If a blank is displayed in this field it means

that no service state is associated with the MO.

Ack? The columns under the “1” and “2” headings denote if the

alarm has been acknowledged by the first and second OSS

telephone numbers, respectively. A “y” in this field means that

the alarm has been acknowledged. An “n” means that the

alarm has not been acknowledged. A “c” means that the alarm

resolved and cleared and the alarm notification was

acknowledged. A blank means that there will be no attempt to

report the alarm.

Date

Alarmed Day, hour, and minute of alarm.

Date

Resolved Day, hour, and minute of resolution. For active alarms this field

is zero (0).

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-73display errors

For the following example, the ENTER key was pressed immediately after entering

the display alarms print command.

Feature Interactions

If the alarm origination is disabled by “change system-parameters maintenance,”

the Ack? field displays blanks no matter what the true acknowledge state is for

the alarm.

If “second-as-backup” is administered in the Alarm Origination to OSS

Numbers field, the column under the “2” heading will be blank for the alarms that

the switch has not attempted to send to the second OSS telephone number. For

the alarms that the switch has attempted to send to the second OSS telephone

number, the column will be “y,” “n,” or “c,” depending on the acknowledgment

status of the alarm. After calling the first OSS telephone number becomes

successful, for the alarms that the switch has attempted to send to OSSN2, the

column will be consistent with the column under the “1” heading.

display errors

display errors [high-resolution] [print | schedule]

The display errors command brings up an input form that allows you to select

which errors will be displayed on the hardware error report.

display alarms

ALARM REPORT

Port Maintenance On Alt Alarm Svc Ack? Date Date

Name Brd? Name Type State 1 2 Alarmed Resolved

02A TONE-BD y MAJOR y n 05/22/20:34 00/00/00:00

01C07 ANL-BD y MINOR n n 05/22/20:26 00/00/00:00

01C0702 ANL-LINE n 311 WARNING IN 05/22/20:26 00/00/00:00

01C0701 ANL-LINE n 1051 WARNING IN 05/22/20:26 00/00/00:00

01C0703 ANL-LINE n 1053 WARNING IN 05/22/20:26 00/00/00:00

01C1505 CO-TRK n 78/01 WARNING OUT 05/22/20:26 00/00/00:00

02A0201 TONE-PT n WARNING 05/22/20:34 00/00/00:00

02A TDM-CLK n WARNING 05/23/13:43 00/00/00:00

PN 02B TDM-BUS n WARNING 05/23/14:53 00/00/00:00

Command successfully completed

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-74display errors

Errors can result from in-line firmware errors, periodic tests, failures detected

while executing a test command, software inconsistency, or a data audit

discrepancy. The Error Log is restricted in size. A new entry overwrites the oldest

unalarmed entry. The overwritten entry must be at least six minutes old, or the

new entry is dropped.

Help Messages

The following help message will be displayed when the first page of a multiple

page list of alarms/errors or after the Prev Page key is pressed:

Press CANCEL to abort or NEXT PAGE for next page

The following help message will be displayed after the Next Page key is pressed

and there are more pages of alarms/errors to be displayed:

Press CANCEL to abort, NEXT PAGE for next page, PREV PAGE for

The following help message will be displayed after the Next Page key is pressed

and there are no more alarms/errors to be displayed:

Press CANCEL to abort, NEXT PAGE to complete, PREV PAGE for

Actions

The following command will display the next page of alarms/errors or echo

“Command successfully completed” and exit if there a no more pages of

alarms/errors to display:

The following command will display the previous page of alarms/errors and the

“press CANCEL to abort or NEXT PAGE for next page” help message:

The following display command will be cancelled and echo “Command aborted”

and exit.

Cancel

System Reboots and the Error and Alarm Logs

The system attempts to save the error and alarm logs to the disk on the

active

SPE when any of the following events take place:

— The save translation command is executed.

— Translations are saved as part of scheduled maintenance (as

administered on the maintenance-related system parameters form).

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-75display errors

— A demand or software-escalated system reboot takes place.

— The PPN is about to lose all power after having been on battery backup.

Conditions such as unavailability of the MSS can prevent this attempt from

succeeding.

Whenever the system reboots, the error log is restored from the disk on the SPE

that becomes active with the reboot. Since the logs are saved to the disk on the

SPE that was active before the reboot, the versions restored at reboot time may

not be current. This occurs when either:

— The attempt to save at reboot did not succeed.

— The SPE that is active coming out of the reboot is not the same one to

which the logs were last saved.

In such a case, the logs will not show the errors and alarms that have been

logged since the last time a save was made to the SPE that became active with

the reboot. When looking at errors that precede the last reboot, look for

indications preceding the reboot to determine whether the logs restored at

reboot are complete.

System resets less severe than a reboot rarely affect the error and alarm logs.

NOTE:

If there are SYSTEM errors in the Error Log, use display initcauses to

obtain additional information. Information that could not be logged during a

system reset may be found here.

Parameters

For more information see ‘‘Common Input Parameters’’ at the beginning of this

chapter.

Input Form

This form specifies which errors display on the report. When all selections have

been made, press ENTER. If no selections are made, or if the schedule option is

specified, all errors from the last day that are associated with active alarms

display (or print).

high-resolution This option specifies an error report with high resolution

time stamps for the first occurrence and last occurrence of

the error. The high resolution time stamp includes seconds

and a sequence count within a second. The sequence

count starts over for each second.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-76display errors

Error Type The report can be restricted to specific error codes. This field

defaults to all errors.

Error List The report can be restricted to errors from one of three lists

described below: active-alarms, errors, or cleared-errors.

Default is active-alarms.

Interval Specifies error records for the last month, hour, day, week, or

all errors (m, h, d, w, a). The default is all.

From Specifies error records starting from the time specified by

mm/dd/hh/mm (month/day/hour/minute). If no “from” date is

entered, errors from the earliest record in the log are

displayed.

To Specifies all error records up to the time specified by

mm/dd/hh/mm. If no “to” date is entered, all errors up to the

current date are displayed.

Equipment

Type To limit the report to a specific group of components, enter

the location of a type of equipment in one of the following

fields. If no entry is made, errors for the entire system are

displayed.

■Cabinet: Enter the cabinet number (1-22).

■Port Network Number: 1-22

■Board Number: Enter the cabinet-carrier-slot address of

the circuit pack (for example, 11c04). If the cabinet

number i omitted, it defaults to 1.

■Port: Enter the cabinet-carrier-slot-circuit address of the

port (for example, 11c0408). If the cabinet number is

omitted, the system will default to 1.

■Category: errors for a particular equipment category. See

the list of alarm and error categories at the beginning of

this chapter. The HELP key displays a list of categories.

■Extension: Enter the extension number of a port.

■Trunk (group/member): Enter a trunk group number, or a

trunk group and member number separated by a slash

(for example, 78 or 78/1).

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-77display errors

Output

display errors Page 1 of 1

ERROR REPORT

The following options control which errors will be displayed.

ERROR TYPES

Error Type: ____ Error List: active-alarms

REPORT PERIOD

Interval: _ From: __/__/__:__ To: __/__/__:__

EQUIPMENT TYPE ( Choose only one, if any, of the following )

Cabinet: __

Port Network: __

Board Number: ____

Port: ______

Category: ________

Extension: _____

Trunk ( group/member ): __/__

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-78display errors

Error Log Report Standard Resolution

Port The physical location of the alarmed object. For circuit pack based

MOs, the location is cabinet-carrier-[slot]-[circuit]. For PN-based

objects, such as TDM-BUS, the location displays as 3PN xx, where xx

is the PN number. For Fiber Link-based objects, the location displays as

x a,b-PNC where x is the Fiber Link number and a- or b-pnc indicates

one of the PNC pair. (Always a-pnc on systems with simplex PNC.)

Maintenance

Name The abbreviated name of the MO that encountered the error.

Alt Name An alternate means of identifying the MO.

Error Type Numerical error code that identifies the type of problem. The meanings

of these codes are explained under the name of the MO in Chapter 9.

Aux Data Additional numerical information about the error type. Only the most

recent auxiliary data for each error type is displayed.

First Occur Month, day, hour, and minute (and second if the high-resolution

command line option is used) that the error was first recorded.

Seq Cnt Sequence Count. These numbers give the order in which the errors

were logged. Each sequence covers a period of one second. Sequence

numbers are assigned to the first and last occurrences of a given error

within the one second period given in the time stamp. There may be

gaps in the sequence numbers within a given second because the last

occurrence of an error may replace an existing entry and because

sequence numbers are also assigned to software events not shown in

the hardware error log. This information is displayed only if the

high-resolution option is specified on the command line.

Last Occur The month, day, hour, and minute (and second if the high-resolution

command line option is used) of the most recent error. If the system is

unable to retrieve the time of day when the error occurred, a “dummy”

date will be stamped in the log so as to distinguish it from reliable data.

It appears as “00/00/01:07”

Err Cnt The total number of times that the error type has occurred. The

maximum entry displayed is 999.

Err Rt Average hourly rate at which the error has occurred from the first

occurrence to the present. The maximum entry displayed is 999.

Rt/Hr An approximation of the rate at which this error occurred in the last hour.

The maximum entry displayed is 999.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-79display errors

The following display shows a typical result when disp errors is entered with the

default input settings.

Al St Alarm Status - A character indicating the status of this MO in the error

and alarm logs. The allowed values are:

■a  Active alarm entry

■r  Resolved alarm entry

■c  Resolved alarm entry as a result of the long “clear” option of

the test command.

■s  Resolved alarm entry as a result of a software requested

(non-demand) system restart.

■t  Resolved alarm entry as a result of a technician requested

system restart.

■n  Not alarmed.

Ac A flag (yes or no) indicating whether or not the maintenance object is

still under active consideration by the maintenance subsystem.

display errors Page 1

HARDWARE ERROR REPORT - ACTIVE ALARMS

Port Mtce Alt Err Aux First Last Err Err Rt/ Al Ac

Name Name Type Data Occur Occur Cnt Rt Hr St

01C0702 ANL-LINE 311 257 01/31/09:20 01/31/20:26 255 999 255 a y

01C0701 ANL-LINE 1051 257 01/31/20:26 01/31/20:26 4 0 4 a y

01C0703 ANL-LINE 1053 257 01/31/20:26 01/31/20:26 4 0 4 a y

01A TDM-CLK 0 0 01/31/20:34 01/31/20:34 1 0 1 a n

01C1505 CO-TRK 078/001 3329 57408 01/31/20:26 01/31/20:27 5 300 5 a y

01C1505 CO-TRK 078/001 1537 01/31/20:26 01/31/20:28 5 150 5 a y

02A0201 TONE-PT 0 01/31/20:34 01/31/20:34 1 0 1 a y

PN 02B TDM-BUS 18 0 01/31/14:53 01/31/21:12 1 0 1 a n

1 A-PNC FIBER-LK 18 0 01/31/21:55 01/31/21:55 1 0 1 a y

Command successfully completed

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-80display events

Error Log Report High Resolution

The following display shows a typical result when display errors high-res is

entered with the default input settings.

display events

display events [print]

A vector event is the occurrence of something unexpected during a

vector-routed call due to resource exhaustion or faulty vector programming. (For

example, route-step failures are typically due to the programming of an invalid

extension.) These types of failures are not due to faulty hardware or system

software error and do not constitute incorrect feature operation. This command

allows you to diagnose and correct vectoring problems due to the

above-mentioned causes. See

DEFINITY Communications System Generic 3 Call

Vectoring and Expert Agent Selection (EAS) Guide

, 555-230-520, for information

on how to interpret this report.

Input Form

The following entry form is displayed to allow limiting the report to events of a

certain type or from a certain time period. Enter the desired parameters and

press ENTER.

Category “Vector” specifies the type of event report to display and is the

only valid entry.

display errors high-resolution Page 1

HIGH RESOLUTION HARDWARE ERROR REPORT - ACTIVE ALARMS

Port Mtce Alt Err Aux First Seq Last Seq Err Al

Name Name Type Data Occur Cnt Occur Cnt Cnt St

01C0702 ANL-LINE 311 257 01/31/09:20:21 1 01/31/20:26:05 1 255 a

01C0701 ANL-LINE 1051 257 01/31/20:26:18 1 01/31/20:26:18 7 4 a

01C0703 ANL-LINE 1053 257 01/31/20:26:18 2 01/31/20:26:18 8 4 a

01A TDM-CLK 0 0 01/31/20:34:35 1 01/31/20:34:35 1 1 a

01C1505 CO-TRK 078/001 3329 57408 01/31/20:26:07 1 01/31/20:27:28 1 5 a

01C1505 CO-TRK 078/001 1537 01/31/20:26:52 1 01/31/20:28:41 1 5 a

02A0201 TONE-PT 0 01/31/20:34:28 1 01/31/20:34:28 1 1 a

PN 02B TDM-BUS 18 0 01/31/14:53:03 1 01/31/21:12:22 1 1 a

1 A-PNC FIBER-LK 18 0 01/31/21:55:24 1 01/31/21:55:24 1 1 a

Command successfully completed

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-81display events

Output

See

DEFINITY Communications System Generic 3 Call Vectoring and Expert

Agent Selection (EAS) Guide

, 555-230-520, for more information on how to

interpret this report. In particular, the Event Data 2 field will be associated with

possible causes and repair strategies for the event.

Report

Period The fields in this section allow you to view only those vector

events that occurred within a specific time period. If these are

left blank, all vector events recorded are displayed.

Interval: This field specifies a display of all events within the last time

period of the type Enter the first letter of one of the following

selections:

ll,

onth,

ay,

our,

inute.

Start/Stop

Time The starting and ending times, in 24-hour notation, of the

interval to be reported.

Vector

Number The number of the vector (1-256) for which events will be

reported. If this field is left blank, events for all vectors will be

reported.

Event Type Specific types of vector events are associated with numbers

from 50000 to 50999. Entering one of these numbers will limit

the report to events of this type. If this field is left blank, events

for all types of vectors will be reported.

Event Type A number from 50000 to 50999 that identifies what type of

vector event occurred.

Event

Description A text string describing the event.

Event Data

1If in the format

number

such as “200/10”, this

indicates the vector number and step number associated

with the event. If in the format “Split

number”

such as “Split

2”, this indicates the split number.

Event Data

2Additional data concerning the event encoded as a hex

number.

First Occur The date and time when the vector event first occurred.

Last Occur The date and time when the vector event last occurred.

Evnt Cnt The total number of times, up to 255, that vector events of

this type have occurred.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-82display fiber-link

The following example shows the input form for display events:

The following example shows a typical vector event report.

display fiber-link

display fiber-link fiber# [print | schedule]

The display fiber-link command displays the translation data associated with an

existing fiber link.

The output for this command is the same as that for change fiber-link.

display events Page 1 of 1 SPE B

EVENT REPORT

The following options control which events will be displayed.

EVENT CATEGORY

Category: vector

REPORT PERIOD

Interval: _a_ From: __/__/__:__ To: __/__/__:__

SEARCH OPTIONS

Vector Number: ___

Event Type: _____

display events Page 1 SPE B

EVENTS REPORT

Event Event Event Event First Last Evnt

Type Description Data 1 Data 2 Occur Occur Cnt

50020 Call not queued 256/5 B 09/28/13:43 09/28/13:43 1

50541 Not a messaging split Split 89 4C 09/28/13:43 09/28/13:43 1

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-83display initcauses

Parameters

display initcauses

display initcauses [print | schedule]

The display initcauses command displays a history of recovery steps taken by

the system.

This command displays information for restarts of the active

processor only

. Whenever the processor resets and the system is restarted,

whether initiated by a technician command or by system software, information

about the recovery is stored. If the reset is escalated, only the reset that

successfully completes is recorded. Information about the reset may also be

found in the Error Log. When a reset 4 (reboot) occurs, the Error Log is saved on

the Mass Storage System.

Records of the last 16 restarts are retained in the initcauses log in chronological

order. A power failure results in loss of all records in the initcauses log.

Output

The entire initcauses log, consisting of 16 resets, fills one screen.

fiber# The administered number (1 to 27) associated with a fiber link (or

fiber link pair in a duplicated PNC).

Cause This gives the reason for the system reset, as follows:

Agent Request: The restart was requested through the

Agent/GEMINI debugger interface (not available to craft login).

Craft Request: The reset was initiated using reset system. This

includes restarts requested through the SPE-Down interface.

Initialized: This represents a power-up, and is always the first

entry in the log unless more than 15 restarts have occurred since

the last power up.

Interchange: A spontaneous interchange was executed by the

system usually in response to a major hardware fault on the active

SPE.

Maintenance Reset: The SPE was reset by maintenance software

on the SYSAM circuit pack. This includes periodic resets initiated

by the SYSAM during SPE-Down mode.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-84display initcauses

The following display shows a typical result when dis init is entered.

Cause mon: A restart was initiated from the system monitor (not

available to craft login).

Sanity Timer Reset: The sanity timer on the processor timed out

and reset the system. This usually indicates corrupted software.

Scheduled Interchange: An interchange was performed as part

of scheduled daily maintenance.

Software Request: System software detected problems and

executed a restart to recover.

SPE-Select Lead Change: On systems with duplicated SPEs, the

SPE select lead changed and reset the processor.

SPE-Select Switch: The SPE select switches on the DUPINT

circuit packs were manually set to lock the standby SPE active,

causing a spontaneous interchange. This is not a recommended

procedure.

Unknown: The restart could not be classified. The Error Log may

contain more information about the restart.

Upgrade Software: The indicated SPE was reset as part of the

execution of the upgrade software command. If this precedes a

Software Requested level 2 reset, both are probably associated

and indicate a non-call preserving upgrade took place.

Action The level of recovery performed by the system.

1 Reset system 1 (Warm)

2 Reset system 2 (Cold-2)

3 Reset system 3 (Cold-1)

4 Reset system 4 (Reboot)

5 Reset system 5 (Extended Reboot)

Planned SPE Interchange (requested by reset system command

or scheduled maintenance)

Escalated Whether the restart was escalated to a higher level than originally

attempted. The system’s software escalation strategy can perform

a higher level restart than the one initiated if problems prevent or

conditions interfere with normal execution.

Carrier The carrier (always A in a simplex system) on which the restart

took place. If an interchange took place, this indicates the carrier

of the newly active SPE that was switched into.

Time The month, day and time of the restart.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-85display system-parameters maintenance

display system-parameters

maintenance

This command displays existing maintenance-related system parameters.

Synopsis

display system-parameters maintenance [high-resolution] [print | schedule]

Permissions

Logins with the following service levels may execute this command: craft, inads,

init, super-user, or logins with Maintain Switch Circuit Packs permissions

enabled.

Examples

display system-parameters maintenance

display system-parameters maintenance print

display system-parameters maintenance schedule

display initcauses

INITIALIZATION CAUSES

Cause Action Escalated Carrier Time

Initialized 4 no 1A 06/01 7:14

Scheduled Interchange i no 1B 06/02 2:00

Scheduled Interchange i no 1A 06/03 2:00

Scheduled Interchange i no 1B 06/04 2:00

Scheduled Interchange i no 1A 06/05 2:00

Scheduled Interchange i no 1B 06/06 2:00

Scheduled Interchange i no 1A 06/07 2:00

Scheduled Interchange i no 1B 06/08 2:00

Scheduled Interchange i no 1A 06/09 2:00

Scheduled Interchange i no 1B 06/10 2:00

Scheduled Interchange i no 1A 06/11 2:00

Interchange 1 no 1B 06/11 12:14

Craft Request i no 1A 06/11 15:40

Craft Request i no 1B 06/11 16:33

Scheduled Interchange i no 1A 06/12 2:00

Scheduled Interchange i no 1B 06/13 2:00

Command successfully completed

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-86display system-parameters maintenance

Description

The display system-parameters maintenance command displays the

translation data for maintenance related system parameters.

Parameters

For more information see ‘‘Common Input Parameters’’ at the beginning of this

chapter.

Help Messages

The following help message will be displayed when the system technician

presses the help key after entering the display system-parameters

maintenance command:

[‘Print’ or ‘schedule’]

Output

An input form is displayed with the following fields. Defaults for data entry fields

are listed in parentheses.

Print This option causes the report to be printed if a printer is linked

to the SAT.

Schedule When the schedule option is specified, the command is

validated and a schedule form is displayed to allow the

technician to schedule execution of the command at a

specified time. The information displayed by the command

will be sent to the system printer instead of the screen.

Product

Identificati

This is a 10-digit number starting with 1 that identifies the

switch to an Operations Support System (OSS), for example,

INADS.

First OSS

Telephone

Number

The first telephone number that the switch uses to report

alarms to, for example, INADS or Trouble Tracker. The

number must be obtained from the National Customer

Support Center (NCSC) or the TSC. # and * are not allowed

in the telephone number.

Abbrev

Alarm Report Enables the Abbreviated Alarm Report feature for the first

OSS. (yes)

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-87display system-parameters maintenance

Second OSS

Telephone

Number

The second telephone number that the switch uses to report

alarms to, for example, INADS or DEFINITY SNMP. The

number must be obtained from the National Customer

Support Center (NCSC) or the TSC. # and * are not allowed

in the telephone number.

Abbrev

Alarm Report Enables the Abbreviated Alarm Report feature for the

second OSS. (no)

Alarm

Origination

to OSS

Numbers

Indicates one of four options for alarm origination (neither):

■If “both,” all Major and Minor alarms result in an

automatic call to both OSS telephone numbers. Both

OSS telephone numbers must be administered.

■If “first-only,” all Major and Minor alarms result in an

automatic call to the first OSS number only. The switch

does not call the second OSS telephone number even if

the number is administered. The first OSS telephone

number must be administered

■If “neither,” alarm origination does not take place.

Warning alarms are not reported to either numbers.

■If “second-as-backup,” all Major and Minor alarms result

in an automatic call to the first OSS telephone number. If

calling the first OSS telephone number fails four

attempts, the switch starts to call the second OSS

telephone number as a backup until calling the first OSS

telephone number becomes successful. Both OSS

telephone numbers must be administered.

Before Release 5, the name of this field is “Alarm Origination

Activated.” If Alarm Origination is deactivated, both Cleared

Alarm Notification and Restart Notification are disabled, even

though they may still be activated in the administration.

Cleared

Alarm

Notification

Enables the switch to originate a call to the OSS and send an

alarm resolution message whenever all previously reported

Major and Minor alarms are resolved. Alarm Origination must

be activated in order for Cleared Alarm Notification to work.

(no)

Restart

Notification Enables the switch to originate a call to the OSS and report

any system restarts caused by problems with the switch.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-88display system-parameters maintenance

Scheduled Maintenance

A series of maintenance tests and operations runs automatically every day

according to the schedule and settings specified in the following fields.

Suspension

Threshold The threshold for suspending Cleared Alarm Notification.

Some problems may cause alarms to be generated and then

resolved repeatedly. To detect these problems (by not

sending additional Cleared Alarm notifications to indicate a

problem- free system), the switch suspends Cleared Alarm

Notification when it has reported this administrable number

of Cleared Alarm notifications in a 24 hour period. A

suspended Cleared Alarm Notification is only enabled again

with a successfully completed “logoff” command, a system

reset, or when the threshold is changed. This field is

irrelevant if Cleared Alarm Notification or Alarm Origination is

disabled. The possible range of threshold values is between

1 and 15.

Test Remote

Access Port Specifies whether testing of the remote access port on the

SYSAM circuit pack is enabled. This field should be set to

“yes” whenever there is an INADS line connected to the

switch and there is a maintenance contract in effect so that

alarm origination capability is maintained.

CPE Alarm

Activation

Level

Indicates the minimum level (Major, Minor or Warning) at

which the Customer-Provided Equipment (CPE) alarm is

activated. If the level is “none,” the CPE does is not activated

for any alarm. (none)

NOTE:

The CPE alarm is always activated when the switch

goes into Emergency Transfer, regardless of the CPE

Alarm Activation Level setting.

Start Time The hour and minute in 24-hour notation at which daily

scheduled maintenance will begin running. (22:00)

Stop Time The hour and minute when scheduled daily maintenance

will stop running. If any daily maintenance operations are

not completed by this time, the system will note where in

the sequence it stopped and perform those operations

during the next scheduled daily maintenance.

Daily

Maintenance This display-only field simply represents the series of

tests that are always run by maintenance software as part

of daily maintenance.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-89display system-parameters maintenance

Save

Translation This field indicates on which days translation data in

memory will automatically be saved to the Mass Storage

System disk and/or tape devices during scheduled

maintenance. The save operation is first made to disk,

followed by a disk backup to tape. On systems with

duplicated SPEs, translation data is saved on both SPEs.

Valid entries are daily, days of the week, or no. “No”

specifies that no automatic saves are to be executed.

(daily)

Control Channel

Interchange Each port network has a pair of TDM busses called A and

B, each of which has a set of time slots dedicated to use

by the control channel. At any one time, the control

channel in each PN is carried on only one of the two

busses. This field indicates on which days the control

channel in each port network will be switched from one of

the paired TDM busses to the other. Valid entries are

daily, days of the week, or no. “No” specifies that no

interchange be executed. (no)

System Clocks

Interchange On High and Critical Reliability systems, this option

causes a Tone-Clock interchange in each port network

with duplicated Tone-Clock circuit packs. Each port

network interchanges into the standby Tone-Clock for 20

seconds and then back to the Tone-Clock that was

originally active. This field indicates on which days the

interchanges are to take place. Valid entries are daily,

days of the week, or no.”No” specifies that interchanges

be executed. (no)

SPE Interchange On systems with duplicated SPEs, this field indicates on

which days an SPE interchange will be executed during

scheduled maintenance. Valid entries are daily, days of

the week, or no.”No” specifies no scheduled

interchanges. (no)

Minimum

Threshold for

TTRs

When the number of touch tone receivers (TTRs) in

service falls below this number (4 to 200), a WARNING

alarm is raised against TTR-LEV. These are also known as

dual-tone multifrequency receivers (DTMRs). There are 4

TTRs on each TN748 Tone Detector circuit pack, and up

to 50 TN748s in a system. To alarm the first occurrence of

a TTR being taken out of service, set this field to 4 times

the number of TN748s. If this number is set to more than 3

less than the total number of TTRs, a port network with

only one TN748 could lose all of its TTRs before this alarm

is raised.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-90display system-parameters maintenance

Minimum

Threshold for

CPTRs

When the number of call progress tone receivers in

service falls below this number (2 to 100), a WARNING

alarm is raised against TTR-LEV (see TTR-LEV in Chapter

9, ‘‘ABRI-PORT (ASAI ISDN-BRI Port)’’). These are also

known as general purpose tone detectors (GPTDs). There

are 2 CPTRs on each TN748 Tone Detector circuit pack,

and up to 50 TN748s in a system. To alarm the first

occurrence of a CPTR being taken out of service, set this

field to 2 times the number of TN748s. If this number is

set to more than one less than the total number of TTRs, a

port network with only one TN748 could lose all of its

CPTRs before this alarm is raised.

Minimum

Threshold for

Call Classifier

Ports

When the number of call classifier ports (CLSFY-PTs) in

service falls below this number, a WARNING alarm is

raised against TTR-LEV. Valid entries are 1 to 200. There

are 8 ports on each TN744 Call Classifier circuit pack,

and up to 25 TN744s in a system. To alarm the first

occurrence of a CLSFY-PT being taken out of service, set

this field to 8 times the number of TN744s. If this number

is set to more than 7 less than the total number of

CSLFY-PTs in the system, a port network with only one

TN744 could lose all of its CLSFY-PTS before the alarm is

raised. If there are no TN744s in the system, leave this

field blank.

Test Type 100,

Test Type 102,

Test Type 105

An extension assigned to receive tie-trunk calls from

other switches with test line origination capability. The

system responds by sending a sequence of test tones.

Test Type 100 tests far-end to near-end loss and

C-message by sending:

■5.5 seconds of 1004 Hz tone at 0dB

■Quiet until disconnect; disconnect is forced after 1

minute

ISDN-PRI Test

Call Extension The extension used by a far-end ISDN node to place a

call to the system to test the ISDN-PRI trunks between the

far-end and the system.

ISDN-BRI

Service SPID This field shows whether or not the link is associated with

the Service SPID. If the link is associated with the Service

SPID, this field contains a “yes” and the extension field is

blank; otherwise, this field is blank. Service SPID is a

feature used by the system technician to check building

wiring between the switch and the BRI endpoint.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-91display system-parameters maintenance

DSO Loop-Around

Test Call

Extension

This field contains the extension number for the test call

extension number. This test extension number will be

used to establish a loop-around connection on the

selected trunk.

The DSO Loop-Around Test Call feature is used primarily

for testing DSO channels associated with non-ISDN-PRI

trunks. The loop-around is activated by dialing the test

extension number. Multiple DSO Loop-Around

connections can be set up by placing multiple calls to the

loop-around extension.

DSO Loop-Around

Test Call

Extension

The DS0 Loop Around feature provides a loop around

connection for incoming non-ISDN DS1 trunk data calls.

This feature is similar to the far-end loop around

connection provided for the ISDN Test Call feature. This

DS0 loop around is provided primarily to allow a network

service provider to perform facility testing at the DS0 level

before video teleconferencing terminals are installed at

the PBX.

The feature is activated on a call-by-call basis by dialing

a test call extension specified on the second page of the

System Parameters Maintenance form. No special

hardware is required. When the test call extension is

received by the PBX, a non-inverting, 64 kbps connection

is set up on the PBX’s Time Division Multiplexed bus.

More than one loop around call can be active at the same

time.

More information follows.

DSO Loop-Around

Test Call

Extension

(cont’d.)

For calls routed over the public network using the

ACCUNET Switched Digital Service (SDS) or Software

Defined Data Network (SDDN), the data transmission rate

is 56 kbps, since robbed bit signaling is used. For calls

established over a private network using common

channel signaling, the full 64 kbps data rate is available.

When the incoming trunk group is used only for data calls

(SDS), the Communications Type on the associated Trunk

Group form should be set to “data.” When the incoming

trunk group is used for robbed bit alternate voice and/or

data (SDN/SDDN), the Communications Type on the

Trunk Group form should be set to “rbavd” (robbed bit

alternate voice data). For private network trunks using

common channel signaling, the Communications Type on

the associated Trunk Group form can be set to “avd.”

Loss Plan Use only when extra loss is required to maintain quality of

transmission on conference calls. Leave this field blank if

no extra loss is required. If extra loss is required, enter

digits as shown below.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-92display system-parameters maintenance

No. Of Parties To

Be Conferenced Enter Digit

SPE Optional

Boards: These fields indicate whether a Disk circuit pack is

present in the system, and which Packet Interface slots

are administered. If a Packet Interface circuit pack is

physically present, the corresponding Packet Interface

field is set to y when the system boots, and no change to

that field is allowed. If the system is equipped with

duplicated SPEs, a Packet Interface field is set to y when

either SPE carrier contains a Packet Interface circuit pack

in the corresponding position. If a Packet Interface circuit

pack is not present, then the value for the Packet

Interface field is read from translation data stored on disk

or tape. If the field is set to n, a Packet Interface circuit

pack may be administered by changing the

corresponding Packet Interface field to y.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-93display system-parameters maintenance

The following display shows a typical result when display system-parameters

maintenance is entered.

display system-parameters maintenance Page 1 of 2

MAINTENANCE-RELATED SYSTEM PARAMETERS

OPERATIONS SUPPORT PARAMETERS

Product Identification: 1000000000

First OSS Telephone Number: 5551212 Abbrev Alarm Report? y

Second OSS Telephone Number: 5551213 Abbrev Alarm Report? n

Alarm Origination to OSS Numbers: both

Cleared Alarm Notification? y

Restart Notification? y

Test Remote Access Port? n

CPE Alarm Activation Level: none

Packet Bus Activated? n

Customer Access to INADS Port? n

Repeat Dial Interval (mins): 7

SCHEDULED MAINTENANCE

Start Time: 22: 00 Stop Time: 04: 00

Daily Maintenance: daily Save Translation: daily

Control Channel Interchange: no System Clocks Interchange: no

SPE Interchange: no EXP-LINK Interchange: no

display system-parameters maintenance Page 2 of 2

MAINTENANCE-RELATED SYSTEM PARAMETERS

MAINTENANCE THRESHOLDS ( Before Notification )

Minimum Threshold for TTRs: 4 Minimum Threshold for CPTRs: 1

Minimum Threshold for Call Classifier Ports: _

TERMINATING TRUNK TRANSMISSION TEST (Extension)

Test Type 100: Test Type 102: Test Type 105:

ISDN MAINTENANCE

ISDN-PRI TEST CALL Extension: _____ ISDN BRI Service SPID: _____

DS1 MAINTENANCE

DSO Loop-Around Test Call Extension: 1001

LOSS PLAN (Leave Blank if no Extra Loss is Required)

Minimum Number of Parties in a Conference Before Adding Extra Loss: _____

SPE OPTIONAL BOARDS

Disk? y Packet Intf1? y Packet Intf2? n Packet Intf3? n

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-94display time

display time

display time [print | schedule]

This command displays the system date and time that is used by software

processes for scheduling and so on.

Output

enable administered-connection

enable administered-connection [adm-conn# | all

This command re-enables scheduled and periodic testing and in-line error

processing on a specified administered connection (AC) or all ACs. It is used

after previously disabling maintenance via the disable

administered-connection command. These commands can be useful in

isolating results of certain maintenance processes by preventing interference

from others.

Parameters

enable suspend-alm-orig

This command suspends Alarm Origination for alarms generated from a

specified hardware component over a time-out duration.

adm-conn# The number (1-128) of the administered connection as assigned

during administration.

all This qualifier causes all ACs in the system to be enabled.

display time

DATE AND TIME

DATE

Day of the Week: Sunday Month: January

Day of the Month: 1 Year: 1992

TIME

Hour: 6 Second: 20

Minute: 8

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-95enable suspend-alm-orig

Synopsis

enable suspend-alm-orig (board or port location) [off-board-only]

expires-in-hrs(1-72).

Examples

enable suspend-alm-orig 1C03 expires-in-hrs 3

enable suspend-alm-orig 1E0701 expires-in-hrs 72

enable suspend-alm-orig 1E07 off-board-only expires-in-hrs 24

Description

This command enables Suspend Alarm Origination for a board (which also

includes all ports and endpoints on the board) or for a port (which includes all

endpoints on the port), and either for both on- and off-board alarms or for

off-board alarms only. Many control circuit packs do not have a board location,

so this command cannot support all circuit packs.

On the command line, specify a time-out duration between one and 72 hours.

The “off-board-only” keyword is optional; if the keyword is not specified, the entry

suspends Alarm Origination for both on-and off-board alarms. Each enable

command becomes a new entry or replaces an existing entry in the Suspend

Alarm Origination table. A new entry that matches both the physical location and

off-only/on- and off-board specifications of an active entry replaces the active

entry in the Suspend Alarm Origination table.

This command may be useful for improving control over situations such as the

following:

■Improved control over customer requests. For example, to suspend

off-board DS1 alarms temporarily for customers that periodically

disconnect DS1 trunks for testing or other business related purposes.

■Improved control over external (non-Lucent) problems. For example, to

suspend off-board DS1 alarms before a customer resolves facility

problems (such as working with the vendor of a T1 trunk that has

developed an off-board condition).

■Improved control over internal (Lucent) problems that cannot be resolved

right away. For example, to suspend Alarm Origination for a bad circuit

pack detected late Friday night and personnel cannot be dispatched until

Monday.

NOTE:

Also see other Suspend Alarm Origination related commands, including

“disable suspend-alm-orig” and “list suspend-alm-orig”.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-96enable synchronization-switch

Defaults

This command enables Suspend Alarm Origination for both on- and off-board

alarms if the “off-board-only” keyword is not specified.

Parameter

Help Messages

Enter board or port location,

[‘off-board-only’], expires-in-hrs(1-72)

Output

The command returns one of the following messages:

1. If the time-out duration is not between one and 72:

XX is an invalid identifier; please press HELP

2. If the port or board specifier is not valid:

Port/Board invalid

3. If the Suspend Alarm Origination table is full:

Table full; cannot enable a new entry

Feature Interactions

None.

enable synchronization-switch

board or port

location This parameter specifies the physical location of the

hardware component for suspending Alarm

Origination.

off-board-only This option enables Suspend Alarm Origination for

off-board alarms only.

expires-in-hrs This parameter specifies the time-out duration for a

Suspend Alarm Origination entry. Expired entries are

removed automatically.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-97enable test-number

This command returns control of the selection of synchronization source to the

maintenance subsystem and tone-clock after being previously turned off by the

disable synch command. See “SYNCH” in Chapter 9 for details.

enable test-number

enable test-number test#

Examples

enable test-number 102

This command will re-enable a specified test that was previously turned off with

the disable test command. (The disable test command is not available to the

craft login.) While disabled a test cannot be run by background or demand

maintenance. Before enabling a test, ascertain why it was disabled, and inform

INADS that it has been turned back on.

Parameters

format card-mem

This command formats the active and standby processor Flash Read-Only

Memory.

Synopsis

format card-mem [translation] [announcements] [coredump]

Permissions

The following default logins may execute this command: browse, system

technician, cust, inads, init.

Examples

format card-mem translation

format card-mem announcements

format card-mem coredump

test# The number of the test to be re-enabled

Descriptions of each test appear under the relevant MO in Chapter 9.

See the Index for a numerical list of all demand maintenance tests.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-98format card-mem

Description

The maintenance command, “format card-mem translation” will erase and format

the memory card for translations only. The maintenance command format

card-mem announcement will erase and format the memory card for

translations and announcements. The maintenance command format card-mem

coredump will erase and format the memory card for translations,

announcements and coredump.

Defaults

No defaults.

Parameters

Help Messages

If the system technician presses help after entering

displaymemory-configuration the following message will be displayed:

Error Messages

If the format memory [translation] [announcements] [coredump] maintenance

command is executed and errors occur, one of the following error messages will

be displayed:

— flash card to small for operation requested

— card is bad (reformat failed)

— card is write protected

— command cannot be executed due to command contention

— NETCON 12V programming power failure

print This parameter causes the information displayed by this command to

be sent to the printer attached to the terminal as well as to the screen.

schedule When the “schedule” option is specified, the command is validated and

then a scheduling form is displayed to allow the technician to schedule

execution of the command. The command is then placed in the

command queue and is executed at the specified time. The information

displayed by the command is sent to the system printer instead of the

screen. Refer to the Report Scheduler and System Printer feature

specification [1] for more details.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-99get vector

Output

For the following output example the command format card-mem was entered.

Feature Interactions

None

get vector

get vector [long] [print]

This command displays the triggering conditions and the SPE associated with a

core dump of memory to the tape or disk device. The vector is a set of system

reset levels which will cause the contents of memory to be saved on tape. When

the core dump occurs, the vector settings are cleared. The vector is set with the

set vector command (not available to craft logins). If no core dump has taken

place since the vector was set, the settings are displayed. If a core dump has

taken place, the time and location of the core dump files is displayed.

NOTE:

When a system reset of a level that is set to trigger a core dump takes

place, the vector is cleared regardless of whether the core dump is

successful.

Enter ’translation’ or ’announcements’ or ’coredump’ or ’firmware’

’translation’ option includes translation only

’announcements’ option includes translation and announcments

’core-dump’ option includes translation, announcments, and code-dump

’firmware’ option includes translation, announcements, and firmware

Or press CANCEL to cancel the command

-------------------------------------------------------------------------------

Identifier command word(s) omitted; please press HELP PREV-FIELD to edit

-------------------------------------------------------------------------------

Command: format card-mem <Help>

Command:

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-100get vector

Parameters

long Specifies display of the timestamps for the core dump. If SPEs are

duplicated, timestamps are printed for both SPEs (or a message

stating why the timestamp cannot be printed is displayed).

Core

Dump

Vector

The conditions which are enabled to initiate a core dump to tape or

disk, as represented by a hexadecimal value. The hexadecimal

value represents a combination of four system reset levels: warm

restart (reset level 1), cold 2 restart (2), cold 1 restart (3), and reboot

(4). The table below shows which reset levels will initiate a core

dump for each value of the vector.

Vector Value Reset Levels Vector Value Reset Levels

0 none 8 4

1191, 4

22a2, 4

3 1, 2 b 1, 2, 4

43c3, 4

5 1, 3 d 1, 3, 4

62, 3e2, 3, 4

7 1, 2, 3 f 1, 2, 3, 4

Set

Vector

Command

Option

This indicates from which SPE the core dump is to be taken as specified

with the set vector command. This is always spe-active for simplex

systems. Additional options for systems with duplicated SPEs are

spe-standby and spe-smm. If the vector has been cleared or not set,

blanks are displayed.

Core

Dump

Time

For each SPE, the date and time at which the core dump took place, or on

of the following:

Blank: No core dump has been stored.

Cannot access: The system cannot currently access the core dump file.

(For example, a standby SPE may not be refreshed).

Non-duplicated SPE: This SPE does not exist (as in a simplex system).

Device busy: the MSS device on which the core dump is stored is busy with

another operation.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-101list cabinet

The following display shows a typical result when get vic is entered and no core

dump has taken place.

The following display shows a typical result when get vec long is entered and a

core dump has taken place, clearing the vector.

list cabinet

list cabinet [print | schedule]

The list cabinet command displays the type, layout, room, floor, building,

operational carriers and port network number for each cabinet in the system. This

command is useful when the port network number is needed for another

command entry and only the cabinet number is known.

get vector

GET RESULTS

Core Dump Vector Set Vector Command Option

F spe-standby

Core Dump Time

SPE_A

SPE_B

Command successfully completed

get vector

GET RESULTS

Core Dump Vector Set Vector Command Option

F spe-standby

Core Dump Time

SPE_A JUN 5 14:31

SPE_B device busy

Command successfully completed

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-102list configuration

Output

The following display shows a typical result when list cabinet is entered on a

system with four port networks. In this example there are two port networks in

cabinet 2.

list configuration

list configuration hardware-group [print | schedule]

NOTE:

The list configuration software-version command is discussed

separately under its own heading.

Number The administered number of the cabinet.

Type The type of cabinet (PPN or EPN).

Layout The layout of the cabinet .

Room Room where cabinet is located, if administered on the

cabinet form.

Floor Floor where cabinet is located, if administered on the

cabinet form.

Building Building where cabinet is located, if administered on the

cabinet form.

A B C D E The letter designation of each carrier. For each carrier the

port network number is given (PN #). If the carrier is a switch

node this number is preceded by SN.

list cabinet Page 1 SPE A

CABINET REPORT

Number Type Layout Room Floor Building A B C D E

1 PPN 5-car PN 01 PN 01 PN 01 PN 01 SN 01

2 EPN 5-car PN 02 PN 02 PN 02 PN 05 PN 05

3 EPN 5-car PN 03 PN 03 PN 03 PN 03 PN 03

4 EPN stack PN 04 PN 04 PN 04 PN 04 PN 04

Command Successfully Completed

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-103list configuration

Hardware configuration reports list, for each circuit pack in the group specified,

the type, code, suffix, and vintage of the requested circuit packs as installed in

the switch, and all ports assigned to the circuit pack.

Parameters

Enter one of the following hardware groups.

■all—Specifies the display of all circuit packs administered and/or

physically inserted in port, switch node and control carriers on the entire

system.

■board

UUCSS

—Specifies the display of all assigned ports on the circuit

pack specified by cabinet, carrier and slot.

■carrier

—Specifies the display of all circuit packs and assigned ports on

a specified carrier.

■control—Specifies the display of all circuit packs located in the control

complex.

■ds1—Specifies the display of all the DS1 (TN722, TN767 and TN464)

circuit packs administered and/or physically inserted in port carriers on

the entire system.

■port-network pn#—Specifies the display of all circuit packs located in a

specified port network. List cabinet gives the port network number(s)

associated with a particular cabinet. Circuit packs on switch node carriers

are not displayed when the port-network qualifier is entered. To display

SN circuit packs, use the all, carrier or board qualifiers.

■stations—Specifies the display of all circuit packs that can be assigned

stations (including DS1 circuit packs for remote stations). All assigned

ports are displayed.

■trunks—Specifies the display of all circuit packs that can be used for

administering trunks. All assigned ports are displayed.

Examples

list configuration carrier 2c schedule

list configuration port-network 5

list configuration stations print

Output

Assigned Ports:

■Board Number—The functional name of the circuit pack

■Code—The TN or UN code and suffix of the circuit packs are displayed.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-104list configuration

■Vintage 00000000-065535 KKKKKK—The vintage number of the circuit

pack.

■no board—The circuit pack is administered but not physically installed.

■conflict—The circuit pack administered to the slot differs from the circuit

pack that is physically installed.

■no link—The T1 link is down to a DS1 circuit pack.

Field definitions:

■Signaling—This field is displayed only when ”list configuration ds1”

option is selected. The contents of the field are the same as the signaling

mode administered for the ds1 circuit pack (via add/change ds1

command) or ”none” if the circuit pack is not administered.

■Name—This field is displayed only when “list configuration ds1” option is

selected. The contents of the field are the same as the name administered

for the ds1 circuit pack (by the add/change ds1 command) or “blank” if

the circuit pack is not administered.

■CSU MOD—This field is displayed only when “list configuration ds1”

option is selected. The field contains the identification number of the

Integrated CSU module present on the ds1 circuit pack (TN767E or later /

TN464F or later) or “none”. If the circuit pack is a TN464E or TN767D,

“unknown” will be displayed. If the circuit pack is a TN464D or TN767C or

earlier suffix DS1 board, then “n/a” will be displayed.

Assigned Ports

Each port on the circuit pack is represented by a position corresponding to its

circuit number in ascending order from left to right. The assigned ports are not

displayed for list configuration ds1. Two rows are required for circuit packs with

more then 8 ports. The position displays one of the following values depending

on its administered status:

■01-16—The circuit number of an assigned port.

■u—The port corresponding to this position exists but is unassigned.

■t—The port is not currently assigned and is supported by the Terminal

Translation Initialization feature. Ports in this state can be activated by the

TTI association sequence.

■mj—The port corresponding to this position is currently assigned as an

external device (mj) alarm port.

■mn—The port corresponding to this position is currently assigned as an

external device (mn) alarm port.

Each port on a TN556 ISDN-BRI circuit pack can have two BRI endpoints. BRI

ports are displayed once when assigned only one endpoint and twice when fully

configured with two endpoints.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-105list configuration

The following display shows a typical result when list configuration all is

entered.

The following display shows a typical result when list configuration ds1 is

entered.

list configuration all Page 1

SYSTEM CONFIGURATION

Board Assigned Ports

Number Board Type Code Vintage u=unassigned t=tti

01C00 MAINTENANCE/TEST TN771C 000003 u 02 03 04

01C01 AUXILIARY TRUNK TN748C conflict u u u u

01C02 EXPANSION INTRFC no board

01C03 PGATE BOARD TN577 000003 u u u u

01C05 TONE DETECTOR TN748B 000002 01 02 03 u 05 06 07

01C06 DS1 INTERFACE TN767 000011 u u u u u u u

u u u u u u u

01C07 ANALOG LINE TN742 000010 u u u u u u u

01C08 HYBRID LINE TN762B 000004 u u u u u u u

01C09 ANALOG LINE TN742 000010 u u u u u u u

01C11 DIGITAL LINE TN754 000004 u u u u u u u

01C12 DID TRUNK TN753 000006 u u u u u u u

01C13 ANALOG LINE TN742 000010 u u u u u u u

01A14 SYS ACCESS-MAINT TN1648 000002 mj mn

01A15 Maintenance TN775B 000002 mj u

press CANCEL to quit -- press NEXT PAGE to continue

list configuration ds1

SYSTEM CONFIGURATION - DS1 Circuit Packs

Location Code Vintage Signaling Name CSU MOD

01B05 TN464F 000002 isdn-pri 120A1

01B06 TN464D 000002 isdn-pri n/a

01B10 TN767C 000003 none n/a

01B11 TN767E 000003 robbed-bit 120A1

01B12 TN767E conflict none <blank>

01C06 no board none <blank>

01C13 TN464E 000003 common-channel unknown

01C16 TN767D 000024 robbed-bit unkonwn

01C18 TN464F 000002 isdn-pri none

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-106list configuration software-version

list configuration software-version

list configuration software-version [memory-resident | long] [print |

schedule]

This command displays

■Software version numbers and compatibility indexes of the software load

modules stored in system memory (RAM) and on the Mass Storage

System devices (tape and disk).

■The dates and times when translation and announcement data were last

saved to the MSS.

■Information about any software update files that have been applied to the

system. See ‘‘Software Updates’’ in Chapter 6, ‘‘Additional Maintenance

Procedures’’ for an explanation of software versions and compatibility

indexes.

Parameters

Output

If the tape contains a core dump file, fields for tape data display coredump.

When a core dump is present, all other files on the device are marked invalid. If

the tape or disk files cannot be read at the time the command is entered, the

relevant fields display no tape or no disk. (This does not indicate that the

system does not recognize the presence of the device.)

Fields in the SPE-B column are blank for standard reliability systems. On high

and critical reliability systems, only fields for the active SPE are displayed unless

the long option is specified.

Tape and Disk Second Copy Fields

Many of the files on disk and tape are duplicated: a second copy of the file is

stored on the same device. The Second Copy fields indicate whether the two

copies are consistent using the following entries:

long Specifies display of data for both SPEs in a high or critical

reliability If not used, only data for the active SPE is

shown.

memory-resident Specifies display of RAM-resident files only. Fields for

tape and disk data will contain n/a

Good The second copy is considered usable. The time stamp and/or

vintage of the second copy matches the first, and its status bits

mark it as a good file.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-107list configuration software-version

Update File Section

The top half of page 1 of the form displays information pertaining to software

field-update files (“patches”).

Software Verson Section

This section at the bottom of page 1 of the output form displays information

related to the current software-load module stored in memory and in the MSS.

Inconsistent The time stamp or vintage of the file is inconsistent with the first

copy, or the status bits mark it as a bad file. Follow normal

escalation procedures.

Inaccessible The second copy of the file could not be accessed. Media

failure is the most probable cause.

Creation

(GMT) Tape

and (GMT) Disk

When the update file was originally created, in

Greenwich Mean Time (GMT). Note that this is

not

the

time at which the update file was written to the MSS

device.

Old-Version

Tape and Disk The software version for which the update was created.

Old-Identifier

Tape and Disk Which previous update file this update file expected to

find stored in the MSS when it was applied.

New-Identifier

Tape and Disk Uniquely identifies the current update file.

Memory Resident Version number of the RAM-resident load module.

Tape Resident Version number of the tape-resident load module.

Tape Second Copy See Second Copy remarks above.

Disk Resident Version number of the disk-resident load module.

Disk Second Copy See Second Copy remarks above.

Update-identifier This uniquely identifies the update file, if any, that has

been applied to memory.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-108list configuration software-version

Translation Date Section

This section at the top of page 2 displays information related to the translation

files as stored in memory and the MSS.

Update-state The status of the software field-update (“patch”) file:

none in memory

No software update has been applied to memory.

immediate partially applied

A software update failed in the process of being

applied. Check the validity of the update file that was

sent. Check also the hardware error log for tape errors,

and follow standard maintenance procedures.

all immediate applied deferred pending

A valid update file was received by the switch, and all

update files marked for immediate application were

applied. This message indicates that there are

additional files in the update file whose application has

been deferred until a system reset of a required level

takes place.

deferred partially applied

Application of the deferred files of a software update

was attempted and failed. Check the validity of the

update file that was sent. Check also the hardware error

log for tape errors, and follow standard maintenance

procedures.

entirely applied to memory

All files in a software update have been successfully

applied.

Memory

Resident Date and time marked on the tape or disk when translation

data was last read from the MSS into memory. This is

stored in SPE memory and is not modified by changes to

translation data. A save translation will update this date. If

“Date invalid” is displayed, the timestamp does not contain

the expected information.

Tape Resident The last date and time that translation data was saved to

tape. This date is read from tape and appears blank if the

tape is not installed.

Tape Second

Copy See Second Copy remarks above.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-109list configuration software-version

System Configuration Section

This section of page 2 pertains to size of the memory configuration. All fields

should display large except when the tape indicates the presence of a

coredump.

Announcement Date Section

This section at the bottom of page 2 displays data pertaining to the recorded

announcement files.

Compatibility Index Section

This section on page 3 displays data pertaining to the compatibility index, which

is used to determine what types of software updates can be applied to a system

running this software load.

The following display shows a typical result when list configuration

software-version is entered on a simplex system. On a duplicated system the

Disk Resident The last date and time that translation data was saved to

disk. This date is read from disk and appears blank if the

disk is not installed.

Disk Second

Copy See Second Copy remarks above.

Tape Resident The last date and time that announcement data was saved to

tape. This date is read from the tape.

Tape Second

Copy The last date and time that announcement data was saved to

tape. This date is read from the second copy of the file on the

tape.

Disk Resident The last date and time that announcement data was saved to

disk. This date is read from disk and appears blank if the disk

is not installed.

Disk Second

Copy The last date and time that announcement data was saved to

disk. This date is read from the second copy of the file on the

disk.

Memory

Resident The compatibility index of the software version in memory.

Tape Resident The compatibility index of the software version on tape.

Disk Resident The compatibility index of the software version on disk.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-110list configuration software-version

fields under SPE-B should display the same entries as the SPE-A fields if all files

are consistent.

list configuration software-version Page 1

SOFTWARE VERSIONS

SPE-A SPE-B

UPDATE FILE

Creation (GMT) Tape: none

(GMT) Disk: none

Old Version Tape: none

Disk: none

Old Identifier Tape: none

Disk: none

New Identifier Tape: none

Disk: none

SOFTWARE VERSION

Memory Resident: DG3r01.06.0.01.0

Tape Resident: DG3r01.06.0.01.0

Tape Second Copy: good

Disk Resident: DG3r01.06.0.01.0

Disk Second Copy: good

Update Identifier: none

Update State: none in memory

press CANCEL to quit -- press NEXT PAGE to continue

list configuration software-version Page 2

SOFTWARE VERSIONS

SPE-A SPE-B

TRANSLATION DATE

Memory Resident: 10:00 pm SAT APR 11, 1992

Tape Resident: 2:00 am SAT APR 11, 1992

Tape Second Copy: good

Disk Resident: 10:00 pm SAT APR 11, 1992

Disk Second Copy: good

SYSTEM CONFIGURATION

Memory Resident: large

Tape Resident: large

Disk Resident: large

ANNOUNCEMENT DATE

Tape Resident: 11:38 am FRI MAR 27, 1992

Tape Second Copy: 11:38 am FRI MAR 27, 1992

Disk Resident: 10:09 pm SAT APR 11, 1992

Disk Second Copy: 10:09 pm SAT APR 11, 1992

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-111list configuration software-version

The following display shows a typical result when list config soft mem is

entered on a system with duplicated SPE while the B carrier SPE is active.

SOFTWARE VERSIONS

SPE-A SPE-B

COMPATIBILITY INDEX

Memory Resident: 8.3

Tape Resident: 8.3

Disk Resident: 8.3

list configuration software-version memory-resident Page 1 SPE B

SOFTWARE VERSIONS

SPE_A SPE_B

UPDATE FILE

Creation (GMT) Tape: n/a

(GMT) Disk: n/a

Old Version Tape: n/a

Disk: n/a

Old Identifier Tape: n/a

Disk: n/a

New Identifier Tape: n/a

Disk: n/a

SOFTWARE VERSION

Memory Resident: DG3r01.06.1.00.0

Tape Resident: n/a

Tape Second Copy: n/a

Disk Resident: none

Disk Second Copy: n/a

Update Identifier: none

Update State: none in memory

press CANCEL to quit -- press NEXT PAGE to continue

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-112list disabled-MOs

list disabled-MOs

list disabled-MOs [print | schedule]

This command displays a list of the maintenance objects that have been

disabled with the disable MO, disable all, or disable MO-all command (not

available to craft logins). as well as whether or not the command has been run.

Use display disabled-tests for numbers of tests that have been disabled.

list configuration software-version memory-resident Page 2 SPE B

SOFTWARE VERSIONS

SPE_A SPE_B

TRANSLATION DATE

Memory Resident: 12:10 pm THU JUN 4, 1992

Tape Resident: n/a

Tape Second Copy: n/a

Disk Resident: n/a

Disk Second Copy: n/a

SYSTEM CONFIGURATION

Memory Resident: large

Tape Resident: n/a

Disk Resident: n/a

ANNOUNCEMENT DATE

Tape Resident: n/a

Tape Second Copy: none

Disk Resident: n/a

Disk Second Copy: none

press CANCEL to quit -- press NEXT PAGE to continue

list configuration software-version memory-resident Page 3 SPE B

SOFTWARE VERSIONS

SPE_A SPE_B

COMPATIBILITY INDEX

Memory Resident: 8.4

Tape Resident: n/a

Disk Resident: n/a

Command successfully completed

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-113list fiber-link

Output

The following display shows a typical result when list disabled-MOs is entered

and no MOs are currently disabled.

list fiber-link

list fiber-link [print | schedule]

This command displays a list of all fiber links in the system. The list is a summary

of data entered on the fiber link form (add, display, change, or remove

fiber-link).

Maintenance

Name Type of maintenance object(s) disabled. “ALL” is displayed

if all MOs are either enabled or disabled.

Location The physical location (cabinet-carrier-[slot-circuit]) of the

maintenance objects. Blank when “ALL” is displayed under

Maintenance Name.

Status Whether the MOs displayed are enabled or disabled.

list disabled-MOs

DISABLED MAINTENANCE OBJECT INFORMATION

Maintenance Name Location Status

ALL Enabled

Command successfully completed

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-114list history

Output

The following display shows a typical result when list fiber is entered on a

system with duplicated PNC and 5 EPNs, one of which is DS1C remoted.

list history

list history [print | schedule]

The list history command generates a log listing of the most recent

data-affecting administration and maintenance commands successfully

completed.

Administration data commands change translation data. Maintenance data

commands change state information. For example, change station would be

classed as a data command, whereas display station would not.

FIBER LINK # The administered number used to identify the fiber link (1 to 27).

TYPE The types of circuit packs that constitute endpoint 1 and

endpoint 2 of the fiber link. (ei or sni).

A-PNC LOC The physical locations (cabinet-carrier-slot number) of the

circuit packs that constitute the endpoints.

B-PNC LOC In a system with duplicated PNC, the physical location

(cabinet-carrier-slot number) of the circuit packs that constitute

the endpoints of the link in the B-PNC.

DS1 CONV Whether or not an endpoint of the link is remotely located by

means of a DS1C Converter Complex.

list fiber-link SPE A

FIBER LINK ADMINISTRATION

FIBER - - - ENDPOINT 1- - - - -ENDPOINT 1- - DS1

LINK # TYPE A-PNC B-PNC TYPE A-PNC B-PNC CONV

LOC LOC LOC LOC

1 ei 01E01 01D01 sni 01E02 01D02 n

2 ei 02A01 02B02 sni 02E02 02D02 n

3 ei 03A01 03B02 sni 01E20 01D20 n

4 ei 04A01 04B02 sni 02E02 02D20 n

5 ei 05A01 05B02 sni 02E03 02D03 y

6 sni 01E13 01D13 sni 02E13 02D13 n

7 sni 01E09 01D09 sni 02E09 02D09 n

8 sni 01E14 01D14 sni 02E14 02D14 n

9 ei 06A01 06B02 sni 01E03 01D03 n

Command Successfully Completed

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-115list history

All information in the transaction log is saved on tape as translation data when

the save translation command is performed (LIFO order). A system reset of

level 3 or higher (COLD 1 and reboots) saved translations and the transaction log

are read from tape. In this way, the translation data and the data in the

transaction log will remain compatible.

The translation log is written to tape as translation data when the save translation

command is executed.

Translation data is time stamped when saved on tape. This time stamp is noted

when translation is loaded from tape and included in all recent change history

reports.

When a user requests a recent change history report, there could be other users

concurrently issuing data commands and altering the contents of the transaction

log. Therefore, if the user pages the entire way through the report, the oldest

entries in the transaction log may have been overwritten by data commands

issued by these other users. Should this occur, the final entries of the report will

show the data commands which have been issued by these other users since

the recent change history report was originally requested.

Use of the maintenance command “set time” to alter the system clock could

make it look as if the recent change history report is not in true LIFO order.

A maximum of 250 commands are stored in the transaction log.

Output

NOTE:

The date listed in the header, refers to the last date on which a reset level 3

(COLD-1 restart) or greater took place.

This date is not updated

when

translation is saved manually by command, or automatically by scheduled

daily maintenance. Thus, it is usually

not

the date of the current translations.

.Date of Loaded Translation:

Date The date the command was issued. Format “mm/dd” where “mm” is

the month and “dd” is the day.

Time The time the command was issued. Format “hh:mm” where “hh” is

the hour and “mm” is the minute.

Port The port field indicates the port type to which the user was

connected when the command was issued.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-116list history

Port Type List History

Display

EPN Maintenance Board Port MAINT

System Access Port SYS-PORT

Maintenance Board Port SYSAM-LCL

Remote Maintenance Board Port SYSAM-RMT

“craft.”

Actn The first word (verb) of the command, specifying the operation to

be performed. This field is truncated after four characters to allow

enough space for objects and qualifiers. Four characters is enough

to uniquely identify each action.

Object The second phrase of the command specifying the particular thing

being acted upon by the command.

NOTE:

Where the object is multiple words in length, only the first

word will be displayed in the object field. All succeeding

words will be treated as qualifiers. This field is truncated after

twelve characters to allow enough space for qualifiers. 12

characters is enough to uniquely identify each object.

Qualifier One or more qualifiers which specify the characteristics of the

action/object pair. This field is truncated after 31 characters to keep

information for a command on a single line.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-117list isdn-testcall

The following display shows a typical result when list history is entered.

list isdn-testcall

list isdn-testcall [print | schedule]

The list isdn-testcall command displays the ISDN-PRI trunks that are currently

in use for outgoing ISDN test calls.

list history Page 1 SPE A

HISTORY

Date of Loaded Translation: 12:10pm Thu Jun 4, 1992

Date Time Port Login Actn Object Qualifier

6/05 14:55 SYSAM-LCL craft enab test-number 5

6/05 14:54 SYSAM-LCL craft set vector f

6/05 14:31 SYSAM-LCL craft rese system 1

6/05 14:29 SYSAM-LCL craft set vector f

6/05 14:27 SYSAM-LCL craf disa synchronizat

6/05 14:26 SYSAM-LCL craft enab synchronizat

6/05 14:20 SYSAM-LCL craft enab synchronizat

6/05 14:19 SYSAM-LCL craft disa synchronizat

6/05 14:19 SYSAM-LCL craft clea port 1c0308

6/05 14:19 SYSAM-LCL craft mark port 1c0308

6/05 14:18 SYSAM-LCL craft clea firmware-cou 3d21

6/05 14:18 SYSAM-LCL craft busy pnc-standby

6/05 14:16 SYSAM-LCL craft clea errors

6/05 14:08 SYSAM-LCL craft rel trunk 1

press CANCEL to quit -- press NEXT PAGE to continue

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-118list marked-ports

Output

The following display shows a typical result when list isdn-testcall is entered.

list marked-ports

list marked-ports [print | schedule]

The list marked-ports command displays all of the ports that have been marked

unusable with the mark port command.

B-Channel The trunk group number and member number of the trunk in

use.

Start Time Day of the month, hour and minute when the test call began.

Duration Expected duration, in minutes, of the test call.

M/T Port Cabinet, carrier, slot and circuit number of the port on the

Maintenance/Test circuit pack in use for the outgoing test call.

list isdn-testcall

ISDN-PRI TESTCALLS

B-Channel Start Time Duration M/T Port

078/001 25/14:36 120 1B1102

Command successfully completed

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-119list measurements ds1

Output

list measurements ds1

list measurements ds1 UUCSS [print | schedule]

list measurements ds1-log UUCSS [print | schedule]

list measurements ds1-fac UUCSSf [log | summary] [print | schedule]

The list measurements ds1 and list measurements ds1-log commands

provide performance measurements on a DS-1 link. The ds1 option provides a

summary report while the ds1-log option provides a detailed report.

The performance measurements of a DS-1 link indicate the quality of the DS-1

physical interface between the system and a far-end system.

The list measurements ds1-fac command provides link performance

measurements on a DS1 Converter facility.

The DS1 Converter Complex consists of two DS1Cs connected by one to four

DS1 facilities. This complex allows the distance between two port networks to

extend up to 100 miles, thereby extending the range of the optical fiber link within

limited bandwidth (96 channels). A DS1C Complex can be used in a direct

connectivity configuration or a Center Stage Switch configuration. The DS1

converters may be connected to an Expansion Interface(EI) or a Switch Node

Interface(SNI) via a metallic connection.

Port The physical location (cabinet-carrier-slot-port circuit) of the

marked port.

Board-Type The type of circuit pack with the marked port.

list marked-ports

MARKED-PORT INFORMATION

Port Board-Type

1C0101 DIG-BD

1C0102 DIG-BD

Command successfully completed

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-120list measurements ds1

Parameters

Examples

list measurements ds1 2a18

list measurements ds1-log 2e01a

list measurements ds1-facility summary 2e01d schedule

Output

The following field descriptions pertain to the summary reports accessed by list

measurements ds1 and list measurements ds1-facility summary.

UUCSS The location of a DS1 circuit pack.

UUCSS The location of a DS1 converter facility where

UUCSS

is the

location of the circuit pack and

is a letter (a-d) designating one

of the four DS1 facilities.

Counted Since: The start time and date when the associated measurement

counters were cleared, or when the DS1C circuit pack or

facility was administered.

Number of

Seconds Elapsed

Into Current

15-min

Interval:

The number of seconds from the beginning of the current

15-minute interval. This field has a value from 0 to 900.

Total of Valid

15-min

Intervals in

Past 24-hr

Period:

The total number of 15-minute intervals in the past 24-hour

period that contain valid data. This field has a value from 0

to 96.

Category The following four fields report data form the error

counters.

Errored Seconds The value of the errored seconds counter for the specified

15-minute interval. This field has a value from 0 to 900 or

N/A if the data for the 15-minute interval is invalid.

Bursty Err Secs The value of the bursty errored seconds counter for the

specified 15-minute interval. This field has a value from 0 to

900 or N/A if the data for the 15-minute interval is invalid.

Severely Err

Secs The value of the severely errored seconds counter for the

specified 15-minute interval. This field has a value from 0 to

900 or N/A if the data for the 15-minute interval is invalid.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-121list measurements ds1

The following field descriptions pertain to the detailed reports accessed by the

list measurements ds1-log and list measurements ds1-facility log

commands.

Failed Seconds The value of the failed seconds counter for the specified

15-minute interval. This field has a value from 0 to 900 or

N/A if the data for the 15-minute interval is invalid.

Worst 15-Min

Interval The date(Date), end time(Time), and error count (Count;

from 0 to 900 in increments of four) of the 15-minute

interval in the previous 24-hour period that contains the

maximum value for each of the four error categories

(errored seconds, bursty errored seconds, severely

errored seconds, and failed seconds).

Total of 24-Hour

Count The sum of all valid 15-minute counts for the previous

24-hour period for each of the four error categories. This

field has a value from 0 to 65535.

Current

15-Minute

Interval

The error count for the current (incomplete) 15-minute

interval for each of the four error categories. This field has

a value from 0 to 899 or N/A if the data for the current

15-minute interval is invalid.

Counted

Since: The start time and date when the associated measurement

counters were cleared or the DS1C circuit pack was administered.

Date The date of the 15-minute interval.

Time The time of the 15-minute interval.

Errored

seconds The value of the errored seconds counter for the specified

15-minute interval. This field has a value from 0 to 900 or N/A if the

data for the 15-minute interval is invalid.

Bursty

err secs The value of the bursty errored seconds counter for the specified

15-minute interval. This field has a value from 0 to 900 or N/A if the

data for the 15-minute interval is invalid.

Valid

interval This field indicates whether the data for the specified 15-minute

interval is valid. Data is considered valid when a count for that

15-minute interval. If the field has a value of ‘‘y’’, the data for the

four error categories is valid; otherwise, the data is invalid. Data is

considered valid when a count for that 15-minute interval is

retrieved and none of the following invalid conditions occur. Data

is invalid if a system warm start or a system cold start occurred

during the interval, if the DS1C circuit pack was not inserted

during the interval, if the system time was changed during the

interval, or if the system was too busy to respond to a poll request

for the interval.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-122list measurements ds1

The following output examples show all of the four different DS1 reports.

list measurements ds1 2a19 SPE A

Switch Name: Date: 1:25 pm THU APR 16, 1992

DS-1 Link Performance Measurements Summary Report

Counted Since: 1:20 pm THU APR 16, 1992

Number of Seconds Elapsed Into Current 15-min Interval: 323

Total of Valid 15-min Intervals in Past 24-hr Period: 0

Total of Current

Worst 15-Min Interval 24-hr 15-Min Int

Category Date Time Count Count Count

Errored Seconds 4/16 13:20 0 0 4

Bursty Err Secs 4/16 13:20 0 0 4

Severely Err Secs 4/16 13:20 0 0 0

Failed Seconds 4/16 13:20 0 0 0

Command successfully completed

list measurements ds1-facility summary 2e01a SPE A

Switch Name: Date: 1:26 pm THU APR 16, 1992

DS1C Link Performance Measurements Summary Report

Counted Since: 10:50 am THU APR 16, 1992

Number of Seconds Elapsed Into Current 15-min Interval: 375

Total of Valid 15-min Intervals in Past 24-hr Period: 10

Total of Current

Worst 15-Min Interval 24-hr 15-Min Int

Category Date Time Count Count Count

Errored Seconds 4/16 10:50 0 0 0

Bursty Err Secs 4/16 10:50 0 0 0

Severely Err Secs 4/16 10:50 0 0 0

Failed Seconds 4/16 10:50 0 0 0

Command successfully completed

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-123list pms-down

list pms-down

list pms-down [start-time][stop-time][print]

list measurements ds1-log 2a19 SPE A

Switch Name: Date: 1:26 pm THU APR 16, 1992

DS-1 Link Performance Measurements Detailed Log Report

Counted Since: 1:20 pm THU APR 16, 1992

ERRORED BURSTY SEVERELY FAILED VALID

DATE TIME SECOND ERR SECS ERR SECS SECONDS INTERVAL

4/16 13:05 0 0 0 0 y

4/16 13:20 0 0 0 0 y

Command successfully completed

list measurements ds1-facility log 2e01a SPE A

Switch Name: Date: 1:26 pm THU APR 16, 1992

DS1C Link Performance Measurements Detailed Log Report

Counted Since: 10:50 am THU APR 16, 1992

ERRORED BURSTY SEVERELY FAILED VALID

DATE TIME SECOND ERR SECS ERR SECS SECONDS INTERVAL

4/16 11:05 0 0 0 0 y

4/16 11:20 0 0 0 0 y

4/16 11:35 0 0 0 0 y

4/16 11:50 0 0 0 0 y

4/16 12:05 0 0 0 0 y

4/16 12:20 0 0 0 0 y

4/16 12:35 0 0 0 0 y

4/16 12:50 0 0 0 0 y

4/16 13:05 0 0 0 0 y

4/16 13:20 0 0 0 0 y

Command successfully completed

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-124list suspend-alm-orig

This command lists all events that have meaning to the Property Management

System (PMS) that have occurred while the link between the switch and the PMS

was down. For example, any room status codes entered by hotel housekeeping

staff during a time of PMS outage would be shown in this report.

Parameters

Output

The following example shows a typical result when list pms-down is entered.

list suspend-alm-orig

This command lists entries in the Suspend Alarm Origination table.

Synopsis

list suspend-alm-orig [print | schedule]

start-time The starting time in 24-hour notation from which events are to

be listed.

stop-time The time in 24-hour notation up to which events are to be

listed.

Extension The extension associated with the reported event.

Event The PMS event that was reported to the switch, but which could

not be sent to the PMS.

Reason The reason that the event could not be reported by the switch to

the PMS.

Time The time at which the event was reported.

list pms-down

PROPERTY MANAGEMENT SYSTEM ACTIVITY

Extension Event Reason Time

402 from room, code 1 PMS link out of service 7:00am

405 from stn, code 1 PMS link out of service 9:00am

411 check in, complete PMS link out of service 9:30am

411 PBX enabled MWL PMS link out of service 12:00am

450 from room, code 1 PMS reject 12:05am

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-125list suspend-alm-orig

Examples

list suspend-alm-orig

list suspend-alm-orig print

list suspend-alm-orig schedule

Description

This command lists active entries in the Suspend Alarm Origination table. Even

though this command only lists active entries, an entry that expires during the list

process still appears in the output. If the Suspend Alarm Origination table is

empty, the output would only contain the title and field headings.

Parameters

Help Messages

[‘print’ or ‘help’]

Output

Print This option causes the report to be printed if a printer is linked

to the SAT.

Schedule When the schedule option is specified, the command

validates and a schedule form displays to allow the

technician to schedule execution of the command at a

specified time. The information displayed by the command is

sent to the system printer instead of the screen.

list suspend-alm-orig

Suspend Alarm Origination Entries

Physical Board Expires At

01C03 off-only 06/11/15:06

01E0407 on-and-off 06/11/17:26

01E0406 on-and-off 06/12/45:34

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-126list sys-link

Feature Interactions

None.

list sys-link

list sys-link [print | schedule]

The list sys-link displays all of the system links. The location, link type and

channel number, link state, current path status, faulted path status, and last

recorded fault, if any, are displayed for each system link. See SYS-LINK in

Chapter 9, ‘‘ABRI-PORT (ASAI ISDN-BRI Port)’’ for details.

Output

Location The physical location of the far endpoint associated with the

system link (cabinet-carrier-slot-circuit).

Link

Type/Channel The type of system-link and the processor channel number

of the link (if there is one). System links include the following

(see MO SYS-LINK):

Expansion Archangel Links (EAL), Indirect Neighbor Links

(INL), Processor Gate Control links (PGC), PRI signaling

links (PRI), System Port links (SAP), Remote Neighbor links

(RNL), Local Neighbor links (LNL), X25 adjunct links.

Processor channel numbers range from 1 to 128.

State Whether the system link is “up” or “down.”

Current Path This field specifies the status of the current path. This field

displays “none” if the link is down or “present” if the current

path is functional.

Faulted Path This field shows whether the link has experienced a fault and

been switched to another path. “Present” indicates that the

link has been faulted at least once. “None” is displayed if the

link has not gone down. “Default” is displayed if the default

faulted path is being used.

Last Fault

Recorded The date and time that the most recent fault on the link took

place.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-127mark port

The following display shows a typical result when list sys-link is entered on a

system with 5 PNs and PNC duplication.

mark port

mark port UUCSSpp

The mark port command will identify a port as unusable by normal call

processing. The port will be able to be tested, etc. but calls will not be attempted

through the port. The marking of a port is saved as part of translation. The port

can be restored to service by using the clear port command.

For more information see ‘‘Common Input Parameters’’ and ‘‘Common Output

Fields’’ at the beginning of this chapter.

monitor bcms

monitor bcms split split# | system system# | skill skill#

The monitor bcms command displays output for agents and splits summarizing

the Basic Call Management System (BCMS) condition. This on-line status report

is automatically updated every 30 seconds or on demand by pressing UPDATE.

The command is canceled by pressing CANCEL which results in termination of the

list sys-link Page 1 SPE A

SYSTEM LINKS INFORMATION

Location Link Type/ State Current Faulted Last Fault

Channel Path Path Recorded

02A0101 EAL up present present 12/30/1991 14:18

02B0201 EAL up present none

03A0101 EAL up present present 12/30/1991 12:56

03B0201 EAL up present none

04A0101 EAL up present present 12/30/1991 14:18

04B0201 EAL up present none

05A0101 EAL up present present 12/30/1991 12:56

05B0201 EAL up present none

01E0201 LNL up present none

01D0201 LNL up present none

01E2001 RNL up present none

02E0201 RNL up present present 12/30/1991 14:18

02E0301 RNL up present present 12/30/1991 14:18

02E2001 RNL up present none

press CANCEL to quit -- press NEXT PAGE to continue

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-128monitor bcms

Parameters

Examples

monitor bcms split 1

monitor bcms system 1 5 7 8 9

monitor bcms system 1-15

split This specifies display of status information for one particular split

(ACD hunt group). The qualifier is followed by an ACD hunt group

number (split number) that identifies the split to the switch.

system This specifies display of split queue status as well as cumulative split

information for all splits measured by BCMS. The qualifier is followed

by ACD hunt group numbers (split numbers) separated by spaces

and/or split number ranges separated by a hyphen (“-”).

skill This specifies display of status information for one particular skill

group. The qualifier is followed by a skill number that identifies the

group.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-129monitor bcms

Output for the System Option

Date The current date and time which is updated every 30 seconds

or when the UPDATE key is pressed.

SPLIT The name of the split being reported, if no name is

administered then the split extension is displayed in the form

“EXTxxxxx”. Splits are displayed in split number order. This

field is translation data.

CALLS WAIT The number of calls currently waiting in this split’s queue. If

any of these calls are Direct Agent Calls, the field will be

preceded by an asterisk. This field is real-time status data.

OLDEST CALL The amount of time that the oldest call has waited in queue.

This field is real-time status data.

AVG ANSW

SPEED The average time required for an answer in this split during the

current period, including time in queue and time ringing at the

agent’s voice terminal. Intraflow calls (those that overflow from

one ACD split to another split) will not have queue time from

previous splits included in the average. The calculation is

Total Answer Time/Total Automatic Call Distribution (ACD)

Calls. This is measurement data and includes only those calls

that have completed.

AVAIL AGENT The number of agents in this split currently available to receive

an Automatic Call Distribution (ACD) call from this split. This

field is real-time status data.

# ABAND The number of calls that have abandoned during the current

period. This field is measurement data.

AVG ABAND

TIME The average time abandoned calls waited in queue before

abandoning during the current period. The calculation is Total

Abandon Time/Total Calls Abandoned. This field is

measurement data and includes only those calls that have

completed (terminated).

# ACD The number of Automatic Call Distribution (ACD) calls handled

by this split during the current period. This includes calls that

intraflow into the split. This field is measurement data.

AVG TALK The average talk time for Automatic Call Distribution (ACD)

calls handled by this split during the current period. This does

not include ring time at the agents’ voice terminal. The

calculation is Total ACD Talk Time/Number of ACD Calls. This

field is measurement data and includes only those calls that

have completed (terminated).

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-130monitor bcms

The following display shows a typical result when monitor bcms system is

entered.

AVG AFTER

CALL The average After Call Work (ACW) time for Automatic Call

Distribution (ACD) calls handled by this split during the current

period. ACD calls with no ACW time are included in the

average. Time spent on direct incoming or outgoing calls while

in ACW will not be included in the average. The calculation is

(Total ACW Time - Total ACW Incoming Time - Total ACW

Outgoing Time)/Total ACD Calls. This field is measurement

data and includes only those calls that have completed

(terminated).

monitor bcms system Page 1 of 1

BCMS SYSTEM STATUS

Date: 14:02 THU OCT 17 1991

AVG AVG AVG

CALLS OLDEST ANSW AVAIL # ABAND # AVG AFTER

SPLIT WAIT CALL SPEED AGENT ABAND TIME ACD TALK CALL

Service 3 1:03 :45 0 3 :30 20 2:30 1:25

Sales 5 :33 :15 0 11 :45 36 1:32 :35

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-131monitor bcms

Output for the Split Option

Split: The number of the split requested. This field is translation

data.

Split Name: The name of the split requested. If no name exists the split

extension is displayed in the form “EXT xxxxx”. This field is

translation data.

Date: The current date and time which is updated every 30 seconds

or when the UPDATE key is pressed.

Calls

Waiting: The number of calls currently waiting in this split’s queue. If

any of these calls are Direct Agent Calls, the field will be

preceded by an asterisk. This field is real-time status data.

Oldest

Call: The time in minutes:seconds that the current oldest call has

waited in this split’s queue. This field is real-time status data.

Staffed: The number of agents currently logged into this split. This field

is real-time status data.

Avail The number of agents currently available to receive an

Automatic Call Distribution (ACD) call in this split. Agents are

in either the Auto-in or Manual-in work modes and are not

currently on a call. If the agent is on another split’s call or in

After Call Work (ACW) for another split, this agent is not

considered available and will not be recorded here. This field

is real-time status data.

ACD The number of agents in this split currently on an Automatic

Call Distribution (ACD) call for this split. This includes ACD

calls that are being handled by this split that arrive as

coverage from another split. This field also includes outbound

calls (Outgoing Call Manager) that are distributed through the

ACD. Note that if an agent puts an ACD call on hold, but does

not enter another state (for example, the agent does not enter

the AVAIL state), the agent will still be seen as in the ACD

state. This field is real-time status data.

ACW The number of agents in this split currently in After Call Work

(ACW) split. This field is real-time status data.

AUX The number of agents in this split currently in AUX work for this

split. If an agent is on another split’s call or in After Call Work

(ACW) for another split, this agent is not considered in AUX

work and will not be recorded here. This field is real-time

status data.

Extn The number of agents in this split currently on non-ACD

(Automatic Call Distribution) calls, either incoming or outgoing

directly to/from their extensions. If the agents are also in After

Call Work (ACW) or AUX they will be recorded as Extn rather

than ACW or AUX. This field is real-time status data.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-132monitor bcms

The following display shows a typical result when mon bcms spl 1 is entered.

OtherSplit The number of agents in this split on another split’s call or in

After Call Work (ACW) for another split. Only used if agents

belong to multiple splits. This field is real-time status data.

AGENT The name of the agent associated with the extension. If no

name exists this field will be left blank. This field is translation

data.

EXT The agent’s extension. This field is translation data.

STATE The current state of the agent for this split. This possible states

are Avail, ACD, ACW, AUX, Extn In, Extn Out, OtherSplit, and

Unstaff. If an agent is staffed, the agent must also be in one of

the above states. This field is real-time status data.

TIME The clock time at which the agent entered the current state.

This field is real-time status data.

ACD CALLS The number of Automatic Call Distribution (ACD) calls

(inbound and outbound), that the agent has completed for this

split during the current period (half hour or hour). The

maximum number of calls is 255, and if this maximum is

exceeded, 255 is displayed. This field is measurement data.

EXTN IN

CALLS The number of non-ACD incoming calls that the agent has

received and completed during the current period. The

maximum number of calls displayed is 255. This field is

measurement data.

EXTN OUT

CALLS The number of outgoing non-ACD (Automatic Call Distribution)

calls that the agent has completed during the current period.

The maximum number displayed is 255. This field is

measurement data.

monitor bcms split 1 Page 1 of 1 SPE A

BCMS SPLIT (AGENT) STATUS

Split: 1

Split Name: hunt group 1 Date: 9:02 TUE OCT 22 1991

Calls Waiting: 0

Oldest Call: 0:00

0=Staffed 0=Avail 0=ACD 0=ACW 0=AUX 0=Extn 0=OtherSplit

AGENT EXT STATE TIME ACD EXTN IN EXTN OUT

CALLS CALLS CALLS

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-133monitor health

monitor health

The monitor health command displays the same information as the status

health command and updates the display automatically every minute. The

command is terminated by pressing Cancel. When the command is canceled, the

management terminal login is dropped. See status health for a description of

the fields displayed.

monitor security violations

monitor security-violations [print]

The monitor security-violations command displays the following information

about failed attempts to access the system: the time of the violation, the login

entered, and the port accessed during the failed login attempt. For remote

access violations, the trunk group number, member, and extension are also

shown. A total of 16 entries are maintained for each type of access. The report is

automatically updated every 30 seconds until the command is canceled by

pressing CANCEL. Unlike some other monitor commands, canceling does not

cause the terminal to be logged off.

Output

Date The date of the security violation given as MM/DD.

Time The time of the logged security violation given as HH:MM.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-134monitor system

System Management Violations

Remote Access Violations

monitor system

This command with the view1 or view2 option displays one screen page of

output summarizing the overall condition of the system. With the connection

option, the command displays the real-time status for time slots and buses.

Additionally, there are other miscellaneous parameters displayed that show call

rates, intervals, etc.

Port

Type The type of port through which the login violation was attempted:

SYS-PORT

A dial-in connection to a system port.

MAINT

A physical connection to the G3-MT terminal connector on an

EPN maintenance circuit pack.

SYSAM-LCL

A physical connection to the ACTIVE terminal connector on the

SYSAM circuit pack in a PPN control carrier.

SYSAM-RMT

A connection to the Remote Access Port (RAP) on the SYSAM

circuit pack. This port is usually accessed by dialing in and is

reserved for use by INADS.

Ext The extension assigned to the data module that was used to

attempt the failed login. If a data module was not used (as in the

case of dedicated EIA connections, for example) the field is

blank.

TG No. The trunk group that carried the incoming remote access attempt

(remote access violations only).

Mbr The trunk group member number associated with the trunk from

which the remote access attempt terminated (remote access

violations only).

Ext The extension used to access the RAP (remote access violations

only).

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-135monitor system

Synopsis

monitor system [ view1 | view2 | conn [ pnn

pnn number 1 pnn number 2 pnn

number 3

] ]

Permissions

The following default logins may execute this command: system technician,

inads, cust, init, nms, browse.

Examples

monitor system view1

monitor system view2

monitor system conn

monitor system conn pnn 1 5 7

Description

The monitor system view1 and view2 commands display a page of output

summarizing the condition of the system. This on-line status report is

automatically updated until the command is canceled by pressing the CANCEL

key. Two display options are available: view1 and view2.

The current overall system status is available with either of the view options.

“View1” displays attendant, maintenance, and traffic status. Attendant and

maintenance status are updated every minute and traffic status is updated on an

hourly basis. When the command is canceled, the technician will be

automatically logged off for security reasons. The “view2” report contains

everything the “view1” report does, except the hunt group measurements are

omitted from the traffic status portion of the “view2” report. These forms contain

simplified high-level information from which a basic picture of the system’s health

can be drawn. The monitor system conn command displays output that shows

the status of connections in the connection manager process. Data is collected

frequently in the connection manager for certain key information items. It is from

this database that this report is drawn. This on-line status report is automatically

updated every minute (or by pressing the UPDATE key) until the command is

canceled by pressing the CANCEL key. Pressing the CANCEL keys forces a logout

of the current login id.

There is one option to the command line entry, monitor system conn. That

parameter is

pnn

. On the

gaz target

, there are only 3 possible pnns. On the

mips

target

, however, up to 22 pnn can be administered. The command line

parameter

pnn

is used to indicate which 3 pnns the user wishes to see.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-136monitor system

Defaults

No defaults.

Parameters

Help Messages

If the system technician presses HELP after entering “monitor system”, the

following object command word choices will be displayed:

conn view1 view2

scr

If the system technician presses HELP after entering “monitor system conn” the

following message will be displayed:

Enter 3 port network numbers (xx-xx) [’pnn’ x x x]

Error Messages

If the pnn number entered is non numeric, not administered, or invalid in any

other way, one of following messages will be displayed:

Object command word omitted; please press HELP

“xx” is an invalid identifier; press RETURN to execute modified command

If during the execution of a command a resource problem occurs that requires

the user to restart the command, then the following message will be displayed:

Command resources busy; Press CANCEL to clear, and then resubmit

view1 This specifies a form that will include the attendant status, the

maintenance status, the last hour’s measurement of trunk

groups, hunt groups, and the attendant group, and finally, the

time of day.

view2 This specifies a form that will display a subset of the view1

form entries. This form will include all of the view1 form except

the last hour’s hunt group measurements.

conn This option will bring up the connection monitor output for key

information.

entering no

options Omitting the “pnn # # #” argument on the command line will

cause the default configuration of Pnn’s 1, 2 and 3 to be

displayed.

pnn # # # Entering “pnn # # #”, where “#” is replaced by a pnn number

from 1 to 3, will cause data for the specified pnns to be

displayed.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-137monitor system

If all of the available maintenance resources are currently in use, then the

following message will be displayed:

All maintenance resources busy; try again later

Output

The following output fields are for the monitor system view1 and monitor

system view2 commands.

Console # A list of console numbers that are either activated or

deactivated.

Activated: The attendant console is in service. An attendant console is

considered activated if its handset/headset is plugged in, it is

not busied out, and the system is in day service and the

console is a day or day/night or principle console, or the

system is in night service and the console is a night or

day/night console.

Deactivated

:The attendant console is not in service. The attendant console

is considered deactivated if it does not meet the previous

activated conditions.

# of

alarms for

trunks

The total number of existing minor and major alarms on trunk

ports.

# of

alarms for

other

resources

The total number of existing minor and major alarms on all

maintainable objects in the system except trunks and stations.

First OSS

number has

been

informed?

Has all the alarm been reported and acknowledged by the first

OSS telephone number. If the “Alarm Origination” is not

enable or there are no active alarm, the field will be “n”.

Measurement

Hour The starting time of the period for which the measurement was

taken. For example, if the measurement hour is shown as

1800, it means the traffic status data displayed is for the time

period from 6 PM to 7 PM (The measurement is taken on an

hourly basis).

Grp no A number between 1 and the maximum trunk group number or

maximum hunt group number in the system.

Grp dir Group direction: incoming, outgoing or two way.

Calls qued Total calls that arrived and were placed in the queue for trunk

groups.

Calls aban Total calls that were abandoned by the caller.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-138monitor system

For the following output example, the command monitor system view1 was

entered.

%Out blkg: The ratio of outgoing calls that are not carried (due to overload

conditions) on a trunk group to the outgoing calls offered.

% Time ATB: The percentage of time within the polling interval that all trunks

in the trunk group were unavailable for use.

Time of day The current time of day acquired from the system.

monitor system view1

ATTENDANT STATUS MAINTENANCE STATUS

Console no. # of alarms for trunks: 4

Activated: 1 2 3 4 5 6 # of alarms for stations: 2

# of alarms for other res: 1

Deactivated: 7 8 First OSS number has been informed? n

TRAFFIC STATUS

Measurement Hour: 1800

Trunk Group Measurement Hunt groups Measurement

(4 grps with highest %time ATB) (4 grps with highest # of qued calls)

Grp no: 78 Grp no: 16

Grp dir: Calls qued: 2

Calls qued: 1 Calls aban: 1

%Out blkg: Attendant Group Measurement

%Time ATB: Calls qued: 1 Calls aban: 0

16:06 WED MAR 6 1996

- press CANCEL to quit -

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-139monitor system

For the following output example, the command monitor system view2 was

entered.

Output

The following output fields are for the monitor system conn command.

Time Slot

Status There are 4 numbers associated with the time slot status for

each specified pnn; for each of the two buses (0 and 1)

there is a maintenance and a normal state. The first row is

the pnn, the second specifies the bus while the third

specifies the bus’s state while the last column represents

the number of idle counts. These fields represent real-time

status data.

Bus Status For the bus status fields, there are two numbers associated

with each of the two buses for each pnn. Shown are the pnn

number; the bus associated with it, i.e., 0 or 1; and the state

of the bus, i.e., “avail” or “unavail”. These fields represent

real-time status data.

Callrate The callrate field represents the call rate being experienced

currently on the switch. This is a counter which is bumped

each time a call attempt is made. This field represents

real-time status data.

monitor system view2

ATTENDANT STATUS MAINTENANCE STATUS

Console no. # of alarms for trunks: 4

Activated: 1 2 3 4 5 6 # of alarms for stations: 2

# of alarms for other res: 1

Deactivated: 7 8 First OSS number has been informed? n

TRAFFIC STATUS Measurement Hour: 1800

Trunk Group Measurement

(4 grps with highest %time ATB)

Grp no: 78

Grp dir:

Calls qued: 1

%Out blkg:

%Time ATB:

Attendant Group Measurement

Calls qued: 1 Calls aban: 0

16:08 WED MAR 6 1996

- press CANCEL to quit -

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-140monitor system

Interval This field is related to the above field in that it represents

the interval being applied with which the call rate is

applicable. It is normally set to a 36 second time period.

This field represents a constant status data.

Max_callrate This field represents the maximum call rate which has been

hit during the time since the last hour has passed. If, for

example, at 20 minutes past 12:00 this command is

executed, this field will represent the maximum call rate

obtained during the past 20 minutes. This field represents

real-time status data.

Next_hour This field will contain a value of 0 or 1 depending upon if the

measurements being taken are for this hour or the next. It is

related to the previous field in that the maximum call rate is

reflected for this hour. When this flag is set, then statistics

begin to accumulate for the next hour and shortly

thereafter, the maximum call rate will become zero and

accumulations will begin anew.

tot_ts_req This field holds the total time slots in use during the time

period elapsed since the top of the last hour. Data is

internally collected every 100 seconds. When the timer fires

and the data collection occurs, a check is made as to how

many time slots are currently in use. That’s where the total

comes from. There are three numbers displayed for this

field on the form; one for each of the pnns requested. This

field represents real-time status data.

ts_denied This field holds the total time slots requests that were

denied during the time period elapsed since the top of the

last hour. Data is internally collected every 100 seconds.

There are three numbers displayed for this field on the form;

one for each of the pnns requested. This field represents

real-time status data.

tot_fts_req This field represents the total fiber time slots that have been

requested. This field is incremented each time a fiber time

slots that have been allocated since the last top of the hour

measurements polling. There are three values shown on the

form; one for each of the requested pnns. This field

represents real-time status data.

ts_count This field indicates how many time slots are in use during

the last 100 second poling period. An internal timer causing

polling to occur every 100 seconds. The value in this field

represents the requests for time slots during that 100

second interim. There are three numbers displayed for this

field on the form; one for each of the pnns requested. This

field represents real-time status data.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-141monitor system

ts_total This field gets it’s value from the time slots count field

discussed above every 100 seconds. It represents the total

number of time slots requested since the top of the last

hour and is real-time status data.

fts_count This field indicates how many fiber time slots are in use

during the last 100 second poling period. An internal timer

causing polling to occur every 100 seconds. The value in

this field represents the requests for fiber time slots during

that 100 second interim. There are three numbers

displayed for this field on the form; one for each of the pnns

requested. This field represents real-time status data.

fts_total This field indicates the total number of fiber time slots. This

field gets it’s value from the fiber time slots count field

discussed above every 100 seconds. It represents the total

number of fiber time slots requested since the top of the

last hour and is real-time status data.

Requests-TN748

TTRs The total number of touch tone receivers requested is

reflected in this field. It is a running count of currently active

requests. It is decremented when a tone receiver is freed

and incremented when they are requested. Note that this

field applies strictly to the TN748 board. This field

represents real-time status data.

Requests-TN748

CPTRs The total number of call progress tone receivers requested

is reflected in this field. It is a running count of currently

active requests. It is decremented when a call progress

tone receiver is freed and incremented when they are

requested. Note that this field applies strictly to the TN748

board. This field represents real-time status data.

Requests-TN744

CPTRs The total number of call progress tone receivers requested

is reflected in this field. It is a running count of currently

active requests. It is decremented when a call progress

tone receiver is freed and incremented when they are

requested. Note that this field applies strictly to the TN744

board. This field represents real-time status data.

Requests-TN744

TTRs The total number of touch tone receivers requested is

reflected in this field. It is a running count of currently active

requests. It is decremented when a tone receiver is freed

and incremented when they are requested. Note that this

field applies strictly to the TN744 board. This field

represents real-time status data.

Requests-TN744

MFC The total number of multi-frequency receivers requested is

reflected in this field. It is a running count of currently active

requests. It is decremented when a multi-frequency

receiver is freed and incremented when they are

requested. Note that this field applies strictly to the TN744

board. This field represents real-time status data.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-142monitor traffic

The following display was produced by entering monitor system conn.

Feature Interactions

None.

monitor traffic

monitor traffic trunk-groups [group#]

monitor traffic hunt-groups

The monitor traffic command shows the current load on specified trunk and hunt

groups and the length of time that the oldest call in the group has been waiting.

Time Slot Status Bus Status

Pnn Bus State *Idle Count Pnn Bus State

10 0 Maint 0 10 0 Avail

10 1 Normal 233 10 1 Avail

10 0 Maint 0 22 0 Avail

10 1 Normal 233 22 1 Avail

22 0 Maint 0 1 0 Avail

22 1 Normal 233 1 1 Avail

22 0 Maint 0

22 1 Normal 233 *Callrate: 20

1 0 Maint 0 *Interval: 60

1 1 Normal 233 *Max_callrate:45

1 0 Maint 0 *Next_hour: 70

1 1 Normal 233

tot_ts_req :0F24 0000 3CE2 ts_count :0010 0920 0200 Requests-TN748 TTRs :0014

ts_denied :0E46 3CE2 0000 ts_total :0000 0090 0028 Requests-TN748 CPTRs:0041

tot_fts_req:0000 53D2 2231 fts_count:02E0 0910 0784 Requests-TN744 CPTRs:0082

fts_total:0320 0192 7048 Requests-TN744 TTRs :0082

Requests-TN744 MFCs :0082

Note: * Denotes Base 10, All Other Figures are in Base 16

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-143monitor traffic

Parameters

Output

trunk-groups The trunk group report displays the number of calls in the

queue waiting to be serviced for each trunk group. The total

number of members in the group and the number of members

active on calls are displayed for comparative analysis. Only

administered trunk groups up to a maximum of 60 are

displayed.

You can specify the starting trunk group. For example, if you

enter 5, trunk groups from group 5 up are displayed.

hunt-groups The hunt-group report is similar to the trunk-group report. In

addition to the information contained in the trunk-group report,

this report displays how long the oldest call in each group’s

queue has been waiting. The display is updated every minute.

refreshed. Fields are blank for unadministered hunt groups.

#Group number for the trunk or hunt group.

SThe size (number of members administered) of each trunk or hunt

group.

AThe number of members in a group that are active on a call. This does

not include members which have been busied out.

QThe length of the queue administered for a group.

WThe number of calls waiting in the group queue to be serviced.

LCIQ The longest call in queue (LCIQ) indicates the time in seconds the

oldest call in the hunt group queue has been waiting to be serviced.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-144monitor trunk

The following display shows a typical result when mon tr hu is entered.

The following display shows a typical result when mon tr tr is entered.

monitor trunk

monitor trunk group# / member#

This command displays the same information as the status trunk command and

updates the data automatically every minute or on demand. To manually update

the display, press UPDATE (f6 on most terminals). Press CANCEL to cancel the

monitor traffic hunt-groups

HUNT GROUP STATUS 22:49 G3-MT DEC 31 1988

# S A Q W LCIQ # S A Q W LCIQ

1 15 10 10 0 20 17

2 18

3 19

4 20

5 21

6 22

7 23

8 24 10 5 0 0 10

9 25

10 26

11 27

12 28

13 29

14 30

15 31

16 32

(#: Group; S: Grp Size; A: Active Members; Q: Q Length; W: Calls Waiting)

(LCIQ: Longest Call In Queue in seconds

monitor traffic trunk-groups

TRUNK GROUP STATUS 22:49 G3-MT DEC 311988

# S A Q W # S A Q W # S A Q W # S A Q W

1 15 10 0 0

2 22 21 10 10

9 31 12 20 0

65 5 5 10 8

99 12 0 0 0

(#: Group; S: Grp Size; A: Active Members; Q: Q Length; W: Calls Waiting)

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-145recycle carrier

command. Unlike some monitor commands, the terminal login is not dropped

when you cancel the command.

recycle carrier

recycle carrier UUC

The recycle carrier command turns power off, then back on, on a specific carrier.

When a power unit is replaced in a carrier, this command must be entered to

restart the power on that carrier. The following carriers cannot be recycled:

■PPN Control Carrier (active or standby)

■Switch Node Carrier

■EPN Control Carrier

■Any carrier holding an active Tone-Clock or an active Expansion Interface

circuit pack

!CAUTION:

When a port carrier is recycled, all ports and adjuncts supported by circuit

packs on that carrier undergo a service outage.

!CAUTION:

Never recycle power to a carrier containing DEFINITY AUDIX

TN566/TN2169 circuit packs without first shutting down the AUDIX system.

Doing so can damage AUDIX software. Follow instructions on the

TN566/TN2169 faceplate (these also appear under ADXDP-PT in

Chapter

9, ‘‘ABRI-PORT (ASAI ISDN-BRI Port)’’

). On G3r V1 systems, the

TN566/TN2169 may appear as a TN746 with a vintage greater than 50.

For more information see Common Input Parameters and Common Output Fields

at the beginning of this chapter.

release commands

release board UUCSS

release maintenance-name [address]

Release commands release specified maintenance objects from the

maintenance busyout state and puts them back into service, assuming the health

of the component(s) permits. Hardware tests specific to the maintenance object

are performed to verify that it is functioning.

For each maintenance object, the release command is entered in the same

fashion as the associated busyout command, except that the word release is

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-146release commands

entered instead of busyout. See the description of the related busyout command

for details of command syntax.

If a release command is entered for an object that is not busied out, the

command will abort. Some release commands trigger recovery actions by the

system, such as the refresh of a standby PNC or SPE. See the description of the

related busyout command for details of command execution and interactions.

Parameters

Input parameters consist of specifying the location, if required, of the given

maintenance object. Use the same format as that used for the related busyout

command.

Examples

release board 01c11

release data-module 310

release tone-clock 2a

release ds1-fac 02e01a

release fiber-link 13

release standby-spe

Output

The identity of the maintenance object and the result of command execution is

displayed on a screen form similar to the related busyout screen. When the

command aborts or fails, an error code indicating the reason is displayed. See

Common Abort and Fail Codes at the beginning of this chapter.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-147reset board

The following display shows a typical result when release board 01c07 is

entered.

reset board

reset board UUCSS [repeat #]

!CAUTION:

This command can be service disrupting and may cause extraneous

alarms. Effects of a reset vary depending upon the type of object being

reset and upon whether the component is duplicated. Consult the section in

Chapter 9, ‘‘ABRI-PORT (ASAI ISDN-BRI Port)’’

on the relevant maintenance

object for details.

When a port circuit pack is specified, the reset board command performs a

software reset of every administered port on the circuit pack. All ports must be

busied out before the port circuit pack is reset.

On Critical Reliability systems (duplicated PNC), reset of an Expansion Interface,

Switch Node Interface, Switch Node Clock, or DS1 Converter circuit pack on the

active PNC is not permitted. Standby components must first be busied out before

entering the reset.

Cabinet number and repeat both default to 1. For more information see Common

Input Parameters and Common Output Fields at the beginning of this chapter.

reset disk

reset disk [C]

release board 01C07

COMMAND RESULTS

Port Maintenance Name Alt. Name Result Error Code

01C07 ANL-BD PASS

01C0701 ANL-LINE 5409 PASS

01C0702 ANL-LINE 5416 PASS

01C0703 ANL-LINE 5421 PASS

Command successfully completed

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-148reset fiber-link

This command resets the disk device, queries the device for ID, size and other

information, and initiates self-testing by the device. Upon successful completion,

all alarms on that disk are cleared and the device is returned to service.

The cabinet is always 1 and need not be entered. On systems with duplicated

SPEs only, carrier a or b must be entered.

Failure of the reset command places the disk in the uninstalled state. All system

access to the disk, including demand testing, is prevented except for demand

resets.

When the host-adapter is busied out, only the demand busyout and test

commands are permitted on the attached disk. Reset, release, scheduled and

periodic testing and other system software access are blocked. In this case, the

host-adapter must first be released before the disk can be released.

When the host-adapter is taken out of service due to test or reset failures, and

becomes uninstalled, the disk is also placed in the uninstalled state and all

access by system software, including resets, is blocked.

reset fiber-link

reset fiber-link fiber# [a-pnc | b-pnc]

!CAUTION:

The reset fiber-link command is destructive on standard and high reliability

systems (simplex PNC), and may cause an entire port network to be

removed from service.

This command resets the Expansion Interface and/or Switch Node Interface

circuit packs that are endpoints of a specified fiber link, dropping the link in the

process.

A fiber link must be busied out before being reset. To busyout a fiber on critical

reliability systems, the fiber must be on the standby PNC and the standby PNC

must first be busied out. See busyout fiber-link for associated interactions.

The list fiber-link command displays a list of fiber links and their locations.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-149reset host-adapter

Parameters

Examples

Simplex PNC: reset fiber-link 1

Duplex PNC: reset fiber-link 1

reset host-adapter

reset host-adapter C

This command resets and initializes the host-adapter circuit on the MSSNET

circuit pack. Upon successful completion, the host-adapter is put into service

and all alarms active for that host-adapter circuit are cleared.

The cabinet is always 1 and need not be specified. Carrier a or b must be

specified only on systems with duplicated SPEs.

This command will abort if any other MSS operation has already begun.

Failure of this command will place the host-adapter in the uninstalled state,

preventing all maintenance testing, including demand testing, of the failed

host-adapter. The reset must pass to put the host-adapter back into service.

When the host-adapter is taken out of service due to failures of its tests, or fails a

reset and becomes uninstalled, the attached tape and disk are also placed in the

uninstalled state and all access by system software, maintenance tests and

commands including reset are blocked from execution.

reset maintenance

reset maintenance UUC

This command performs a reset on a specified maintenance circuit pack.

Specifying cabinet 1 resets the PPN SYSAM circuit pack on the selected carrier,

dropping any remote or local logins. Specifying cabinets 2 through 22 resets the

fiber# The administered number of the fiber link (1-27). On critical

reliability systems (duplicated PNC), this number designates a

fiber link pair; the following qualifier specifies which fiber in the

pair is to be reset.

a-pnc, b-pnc On critical reliability systems (duplicated PNC), this

distinguishes between the two fibers in a duplicated pair. On

systems with simplex PNC this is always a-pnc and need not be

specified.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-150reset packet-interface

EPN maintenance circuit pack in the ‘a’ carrier of the specified cabinet, dropping

any local login to that circuit pack.

The cabinet number defaults to 1. The carrier must be specified only for PPNs

with duplicated SPEs.

reset packet-interface

reset packet-interface C [S]

!CAUTION:

Resetting a packet interface is disruptive under the following conditions:

■On all standard reliability systems (simplex SPE)

■When SPEs in a duplicated system are locked, or handshake is down, and

the active packet interface is reset.

■When the standby SPE in a duplicated system has a state of health lower

than the active, and the active packet interface is reset.

!CAUTION:

In the above cases, call service throughout the system is disrupted, the

terminal is logged off and all EPNs are unavailable during the reset interval.

A minor alarm is logged against the circuit pack to be reset. This lowers the

state of health of the associated SPE and may cause a spontaneous SPE

interchange in duplicated systems.

This command resets and initializes the packet interface circuit pack hardware

and firmware. The actual sequence of operation depends on the type and status

of the SPEs.

When an active packet interface is reset, its links are dropped and reassigned to

the remaining in-service packet interface circuit packs. These links are not

migrated back to the packet interface after the reset. A level 2 (Cold-2) or greater

system restart is required to redistribute the links equally among all active packet

interfaces, including the one that was reset.

Simplex SPE

For standard reliability systems the specified packet interface circuit pack is

simply reset. Failure of the reset can lead to the circuit pack being placed in the

out-of-service state. When a packet interface is out of service, scheduled,

periodic, error and demand testing of the circuit pack is prevented and it is not

used for links. The circuit pack returns to the in-service state upon passing the

reset. A level 2 (Cold-2) or greater system restart is then performed to distribute

the links equally among the available packet interface circuit packs.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-151reset packet-interface

Duplicated SPE Standby Packet Interface

Reset of a packet interface on the standby SPE does not disrupt service and

results in a reset of all packet interfaces on the standby SPE. The following

conditions are necessary:

■Handshake communication is up.

■The SPE carriers are not locked with the SPE-Select switches.

The following sequence occurs:

1. Memory shadowing is turned off.

2. All standby packet interfaces are reset.

3. If the reset succeeds, shadowing is turned on, memory refresh initiated,

and the packet is put into the standby state.

4. If the reset fails, the circuit pack is put into the out-of-service state,

lowering the standby SPE’s state-of-health.

Duplicated SPE Active Packet Interface

Standby SPE available

When a packet interface on the active SPE of a duplicated system is specified, a

spontaneous SPE interchange is first performed by the system, assuming that:

■The SPE carriers are not locked with the SPE-Select switches.

■Handshake communication is up.

■The state of health of the standby SPE is not lower than that of the active.

If these conditions are met, the interchange places the active SPE into the

standby state, and then all standby packet interfaces are reset as in the above

case. Links are not disrupted, but due to the interchange transient calls are

dropped and the terminal is logged off.

Standby SPE Not Available

If any of the three conditions listed above are not met, an SPE interchange is

prevented and the active packet interface is reset, resulting in disruption of all

links associated with the circuit pack (see the Caution above). When the

interchange is prevented by lower state of health of the standby, the standby

packet interfaces are also reset according to the sequence listed above.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-152reset interchange

Parameters

reset interchange

reset pnc interchange [override-and-lock]

NOTE:

This command does not work like other reset commands. Instead of

resetting or initializing hardware, a PNC interchange is executed. Before

entering this command, look at the states of health of the two PNCs with

status pnc.

This command executes a PNC interchange on a Critical Reliability system

(duplicated PNC). The standby PNC becomes active and assumes control of

active call processing, and the active goes to standby. If the health of the

standby PNC is the same as or better than that of the active, no service

disruption takes place; all stable calls and links are preserved. Some unstable

calls may drop.

Both demand and spontaneous PNC interchanges are prevented by the

following conditions:

■The standby PNC is busied out.

■The PNCs are locked by means of the set pnc lock or reset PNC

override-and-lock commands.

■For 5 minutes after a spontaneous PNC interchange, or for 30 seconds

after a demand interchange, an anti-thrashing mechanism prevents

subsequent interchanges unless the override-and-lock option is used.

■If the state of health of the standby PNC is worse than that of the active,

the command will abort unless the override-and-lock option is used.

■If the standby PNC has not completed a global refresh since it was last

initialized or released, the reset will abort unless the override-and -lock

option is used.

Note the following caution regarding the use of the override-and-lock option.

See status pnc for details of how to obtain and interpret the states of health and

other current information about the PNCs. For a more complete explanation of

PNC duplication and interchanges, see PNC-DUP in Chapter 9.

C, CS The cabinet is always 1 and need not be specified. Carrier a or b

must be specified only for duplicated SPEs. The slot number

(1-3) designates one of the dedicated PKT-INTFC slots on the

PPN control carrier and defaults to the lowest-numbered slot with

a packet interface installed in it.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-153reset interchange

Parameters

Output

One of the following messages is displayed:

Command successfully completed

If the reset pnc interchange command is unsuccessful due to the state of health

of the standby Port Network Connectivity, operation of anti-thrashing, or the

following message will be displayed:

Interchange of pnc failed;

try again using the ’override-and-lock’ identifier

See the preceding caution regarding use of the override-and-lock option. If the

reset pnc interchange command is unsuccessful due to a busyout of the standby

PNC, the following message will be displayed:

Must release port network connectivity first

reset pnc interchange [override-and-lock]

NOTE:

This command does not work like other reset commands. Instead of

resetting or initializing hardware, a PNC interchange is executed. Before

entering this command, look at the states of health of the two PNCs with

status pnc.

This command executes a PNC interchange on a Critical Reliability system

(duplicated PNC). The standby PNC becomes active and assumes control of

active call processing, and the active goes to standby. If the health of the

standby PNC is the same as or better than that of the active, no service

disruption takes place; all stable calls and links are preserved. Some unstable

calls may drop.

interchange ”interchange” (without a preceding hyphen) must be

specified on the command line.

override-and-lock This option is also used to override the anti-thrashing

mechanism. Subsequent PNC interchanges are prevented,

regardless of changes in the states health of the PNCs.

Double call setup still takes place; each call is set up on

both PNCs. To unlock the PNCs, use set pnc unlock.

!CAUTION:

This option forces execution of the interchange

regardless of the state of health of the standby,

possibly disrupting service.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-154reset interchange

Both demand and spontaneous PNC interchanges are prevented by the

following conditions:

■The standby PNC is busied out.

■The PNCs are locked by means of the set pnc lock or reset PNC

override-and-lock commands.

■For five minutes after a spontaneous PNC interchange, or for 30 seconds

after a demand interchange, an anti-thrashing mechanism prevents

subsequent interchanges unless the override-and-lock option is used.

■If the state of health of the standby PNC is worse than that of the active,

the command will abort unless the override-and-lock option is used.

■If the standby PNC has not completed a global refresh since it was last

initialized or released, the reset will abort unless the override-and -lock

option is used.

Note the following caution regarding the use of the override-and-lock option.

See status pnc for details of how to obtain and interpret the states of health and

other current information about the PNCs. For a more complete explanation of

PNC duplication and interchanges, see PNC-DUP in Chapter 9.

Parameters

interchange ”interchange” (without a preceding hyphen) must be

specified on the command line.

override-and-loc

kThis option is also used to override the anti-thrashing

mechanism. Subsequent PNC interchanges are prevented,

regardless of changes in the states health of the PNCs.

Double call setup still takes place; each call is set up on

both PNCs. To unlock the PNCs, use set pnc unlock.

!CAUTION:

This option forces execution of the interchange

regardless of the state of health of the standby,

possibly disrupting service.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-155reset port-network

Output

One of the following messages is displayed:

Command successfully completed

If the reset pnc interchange command is unsuccessful due to the state of health

of the standby Port Network Connectivity, operation of anti-thrashing, or the

following message will be displayed:

Interchange of pnc failed;

try again using the ’override-and-lock’ identifier

See the preceding caution regarding use of the override-and-lock option. If the

reset pnc interchange command is unsuccessful due to a busyout of the standby

PNC, the following message will be displayed:

Must release port network connectivity first

reset port-network

reset port-network PN# level [1 | 2]

!CAUTION:

A reset of level 2 is destructive, causing all calls and application links on the

specified EPN to drop. EPN resets are described under EXP-PN in Chapter

This command resets a specified port network to a specified level. This does not

cause an interchange on a system with duplicated PNC. The command will not

execute on the PPN, or on an EPN whose fiber link to the PPN or CSS is down.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-156reset port-network

Parameters

Examples

reset port-network 10 level 2

Output

For more information, see ‘‘Common Output Fields’’ and ‘‘Common Abort and Fail

Codes’’ at the beginning of this chapter. The following display shows a typical

result when reset port-network 4 lev 1 is entered.

PN# Port network number

Use list cabinet to find the PN number(s) associated with a

given cabinet.

level 1 | 2 Reset level 1 (WARM restart) is used to restart an EPN that is

still fully or partially in service. All stable calls are preserved,

and full service is restored within 35 seconds.

Reset level 2 (COLD restart) results in reset, removal, and

reinsertion of all EPN circuit packs. It is used to recover an

EPN that has been taken out of service. Level 2 restarts should

take less than 2 minutes. All calls and application links with an

endpoint in the EPN are dropped. If two level 2 resets within an

hour fail to return the EPN to service, EPN Emergency Transfer

is invoked. (EPN Emergency Transfer will already be in effect if

the link to the EPN has been down for more than 1 minute).

Port The PN number of the reset EPN.

reset port-network 4 level 1

TEST RESULTS

Port Maintenance Name Alt. Name Test No. Result Error Code

04 EXP-PN 956 PASS

Command Successfully Completed

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-157reset spe-standby

reset spe-standby

reset spe-standby level# [tape]

This resets the standby SPE on a system with duplicated SPEs to a specified

level. The command is increasingly destructive as the reset level increases. On a

system with disk and tape devices, the reset is executed using the boot image

stored on disk unless a reset of level 4 (reboot) with the “tape” qualifier is

requested. During the reset, the standby SPE is taken out of service for several

minutes. Reset status can be monitored with the status spe command.

During a reset of any level, memory shadowing is turned off. After the reset

completes, memory shadowing is automatically restored and a memory refresh

of the standby takes place. The standby is not fully in service until the refresh is

complete. Reset spe-standby invokes initialization of the standby in the same

fashion as low level maintenance. The reset level requested will not be escalated

by software. The level requested will always be the level that is performed.

Any reset of the standby SPE turns off shadowing, leaving the standby SPE

unrefreshed. It may take several minutes before the standby is available for

service.

Parameters

Output

The message: Command successfully completed indicates that the reset

has been initiated. Execution and recovery can take several minutes.

level# This specifies the level of reset to be executed, from 1 to 5:

Tape Recovery

1 Warm Restart

2Cold-2

3Cold-1

4 Reboot

5 Extended Reboot

Tape Valid only for a reset of level 4, this specifies a reboot using the

boot image stored on tape instead of disk.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-158reset system

reset system

reset system [level# | interchange] [disk | tape] [contention-override]

!CAUTION:

All system resets (except planned interchanges) are service affecting, with

higher levels being increasingly destructive. Some resets may take up to

one half hour to complete. Certain conditions may result in a higher reset

level than the one requested. Unless you are experienced with resetting a

system, follow normal escalation procedures.

NOTE:

reset system interchange, used to switch control of the system from an

active SPE to the standby, is discussed separately under its own heading.

This command resets a Switch Processing Element (SPE) at a specified level that

is increasingly disruptive as the reset level increases.

All system resets (except

reset system interchange) are disruptive and terminate the G3-MT login.

When the command is entered, the MSS devices are checked to see if they are

currently in use. If any command or maintenance process that accesses the MSS

is in progress, the reset is denied and a message is displayed. In this case, the

contention-override option is required to force the reset. This check prevents

aborting of a save translation or other MSS process.

If the vector bit is set to trigger a core dump for the specified reset level, a copy

of system memory is first written to the primary MSS device. The system then

clears the vector and proceeds with the request. If the vector is set for an active

SPE core dump for reset level 1 a reset level 2 will be performed to recover the

Packet Interface links. See the get vector command.

System software will generally not escalate a demand system reset to a higher

level. There are certain conditions that result in a higher level reset than that

requested. These include the following:

■The vector is set to trigger a core dump on the active SPE in the event of a

level 1 reset.

■A PNC interchange is already in progress.

■A change in translation administration is in progress.

Reset levels greater than 1 turn off shadowing in a duplicated system, and leave

the standby SPE in an unrefreshed condition for several minutes.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-159reset system

Parameters

Examples

reset system 1

reset system 4 tape contention-override

Output

Once this command is entered, it may not be canceled. The screen will display

the results of various initialization tests. If the reset command is successful the

user will be logged off (except for reset system interchange). Several

Level Reset levels are numbered as shown in Table 8-8. The execution times

listed are approximations.

Table 8-8. Approximate Recovery Time for System Resets (min:sec)

Level Recovery 2,400 lines 5,000 lines 15,000 lines

Tape Disk Tape Disk Tape Disk

1 Warm Restart :10 :10 :10 :10 :10 :10

2 Cold-2 1:001:002:002:004:004:00

3 Cold-1 3:00 2:00 5:00 3:00 11:00 7:00

4 Reboot 12:00 4:00 15:00 6:30 23:00 11:00

5 Extended Reboot 15:00 7:00 18:00 10:00 25:00 15:00

Interchange See reset system interchange

Health-override See reset system interchange

Disk Valid only for reset level 4, this specifies use of the boot

image stored on disk for the reboot. Disk is the default

device.

Tape Valid only for reset level 4, this specifies use of the boot

image stored on tape for the reboot.

Contention-override Contention control aborts the reset system command if

any other command is currently running. The

contention-override option forces other processes to

abort, allowing the reset to proceed.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-160reset system interchange

conditions may prevent a requested reset. If the reset fails and the message

displayed is not self-explanatory, use status spe to determine what caused the

failure.

reset system interchange

reset system interchange [health-override][contention-override]

!CAUTION:

Although this command is normally not disruptive, certain conditions may

escalate the interchange to a higher reset level.

This command is used to switch control from the currently active SPE to the

standby. This type of interchange is called a planned, soft, demand or requested

interchange. Interchanges caused by hardware faults or the SPE-Select

hardware switches are called spontaneous or hard interchanges. Planned

interchanges are discussed under:

— SPE Duplication in Chapter 1, ‘‘Maintenance Architecture’’

— Executing a Planned Interchange in Chapter 5, ‘‘Responding to Alarms

and Errors’’

— STBY-SPE in Chapter 9

This operation is not disruptive if the state of health of the standby SPE is

“functional.” If this condition is not met, system software will normally abort a

requested interchange. When this is the case, the health-override option can be

specified to try to force a

spontaneous

(hard) interchange.

!CAUTION:

Use of health-override may cause serious service disruption.

Once a planned interchange has been initiated, it cannot be aborted with the

CANCEL key. A reset system interchange command will abort for the following

reasons:

■If the standby SPE is down

■If the SPEs are locked by means of the SPE-Select switches

■If communication to the standby SPE is not possible (handshake is down)

■If shadowing to the standby SPE is not turned on

■If the standby SPE is not fully refreshed

■If the State-of-Health of the standby is not “functional”

■There is an SCD dual-port RAM failure

■If there is any Mass Storage System activity

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-161reset system interchange

■If Packet Interface link migration fails

■If a minor or major alarm is logged against the standby SPE’s SYSAM or

Packet Interface circuit packs

■If the standby SPE is busied out

The destructiveness of an interchange that fails depends on how far the

interchange proceeds before it fails. A non-destructive recovery should occur if

an interchange is aborted before link migration has started. If the interchange

fails after link migration has started, the system will perform a WARM restart to

recover.

The SPE-Select switches located on the Duplication Interface circuit packs

override any demand maintenance activities. If the SPEs are locked by means of

these hardware switches, an interchange cannot take place until the switches

are unlocked.

If a planned interchange aborts or fails, an error will be logged against SYSTEM,

signaling that the expected interchange has not occurred. In this case, the reset

may be escalated by software. This condition is described in Failure of Planned

Interchange in Chapter 5, ‘‘Responding to Alarms and Errors’’.

If reset system interchange override is specified while a PNC interchange is

occurring, a spontaneous (hard) SPE interchange will occur which results in a

Cold restart. After the restart, the active PNC will be the one that was being

switched into before the restart.

If a requested SPE interchange fails, an error conveying additional information

about the failure will be logged against the SYSTEM maintenance object.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-162reset tape

Parameters

Output

Once this command is entered, it may not be canceled. The screen will display

the results of various initialization tests. Several conditions can prevent a

requested interchange. If the interchange fails and the message displayed is not

self-explanatory, use status spe to determine what caused the failure. Executing

a Planned SPE Interchange in Chapter 5, ‘‘Responding to Alarms and Errors’’

and STBY-SPE in Chapter 9 contain useful information for troubleshooting

interchange failures, The following display shows a typical result when reset sys

int is entered while a save operation is currently running.

reset tape

reset tape [C]

This command resets the tape circuit pack, queries the device for ID, size and

other information, initiates self testing of the device, and rewinds the tape. If

successful, all alarms active for the tape device are cleared and the device is put

back in service.

health-override If a planned (demand) interchange fails for any of the

previously listed reasons, this option can be specified to

try to force a switch to occur. This option causes the

active SPE’s state of health to be downgraded as much

as possible in order to allow a spontaneous (hard)

switch to occur. However, if the standby SPE’s state of

health is still not better than that of the active, or if the

SPEs are locked, the interchange will still not occur.

contention-override Due to contention control, reset system interchange

aborts if any other command is currently running. Use of

this option overrides contention control and forces the

command to execute regardless of whether other

commands are currently running.

reset system interchange SPE A

Unable to interchange due to MSS activity.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-163restore announcements

This command will abort if any other MSS operation has already begun.

Failure of the reset command will place the tape in the uninstalled state,

preventing all maintenance testing including demand testing of the failed tape as

well as all system access to the failed tape except for this reset command.

When the host-adapter is busied out, only the busyout and test commands are

permitted on the tape in that carrier. Reset, release, scheduled and periodic

testing and other system software access are blocked. The host-adapter must be

released before the tape can be released.

When the host-adapter is taken out-of-service due to test failures, or fails a reset

and becomes uninstalled, the tape on the same carrier is also placed in the

uninstalled state. All access to that tape by system software, including

maintenance tests, resets and other commands are blocked from execution.

Parameters

Examples

For more information see ‘‘Common Output Fields’’ at the beginning of this

chapter.

restore announcements

restore announcements [disk | tape]

This command copies stored announcement data from the specified MSS device

to the announcement board. On a duplicated system, data is always copied from

the device on the active SPE.

NOTE:

The restore command can take up to 40 minutes to complete. Avoid

pressing the ENTER key on the keyboard during this time, since doing so

will cause the result messages to be lost.

The command is not executed if any of the following conditions is present:

■An announcement data module and a system port data module have not

been administered.

CThe cabinet is always 1 and need not be entered. Carrier a or b must be

specified only for systems with duplicated SPE.

Simplex SPE: reset tape

Duplicated SPE: reset tape a

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-164restore announcements

■The announcement data module port is out of service or already in use (for

example, performing an announcement playback).

■An integrated announcements session is in progress or the circuit pack is

currently being uploaded or downloaded. Announcements cannot be

save or restored after the restore announcements command has started.

Tape is specified and a tape cartridge is not in the tape drive.

■A system port is not available.

■The MSS is in use by either another user or by maintenance.

■An announcement file does not exist on the specified device, or is

corrupted.

In case of a failure of the restore command, you must make sure the

announcement file is completely copied to the announcement circuit pack. The

system will continually attempt to download the circuit pack at 10 minute intervals

until either a download is successful, announcements are recorded, or a

download is initiated from the terminal. In case of a hardware or firmware error,

an error will be logged, pointing to the source of trouble. Maintenance software

will invoke tests to diagnose and attempt to correct the problem. If maintenance

software fails to correct the problem, an alarm is raised.

If a system crash or spontaneous SPE interchange takes place, the restore

operation will fail, leaving the announcement circuit pack without a valid

announcement file. To remedy this, repeat the restore command on the newly

active SPE.

NOTE:

Until announcements are completely copied to the announcement circuit

pack, calls will not be connected to any announcements on the

announcement circuit pack.

When the announcement circuit pack is inserted or reset, an automatic download

of the announcement file is performed.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-165restore disk

Parameters

Output

The following display shows a typical result when restore announcements is

entered.

restore disk

This command copies all information from the tape device in the specified SPE to

the disk device on the same carrier. Defaults are a full restore and, if the SPE is

duplicated, both SPEs.

disk This specifies copying the announcement data stored on the disk

device. Disk is the default device.

tape This specifies copying the announcement data stored on the tape

device.

Processor The SPE from whose MSS device the announcement data was

copied.

Command

Completion

Status

This field indicates the results of the command execution an

gives a self-explanatory reason for any failures.

Error Code A number indicating whether the announcement file was

successfully restored to the announcement board:

0 = The restore was successful.

1 = The restore failed.

restore disk [active | standby] [spe-a | spe-b] [both | either]

[incremental | full]

restore announcements Page 1 of 1 SPE A

RESTORE ANNOUNCEMENTS

Processor Command Completion Status Error Code

SPE-A Success 0

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-166restore disk

NOTE:

The restore command can take up to 1 hour to complete. Avoid pressing

the ENTER key on the keyboard during this time, since doing so will cause

the result messages to be lost.

Parameters

Examples

restore disk

restore disk active incremental

Output

The outcomes are displayed for each SPE.

spe-a This specifies a restore from the A carrier tape device to the A

carrier disk device.

spe-b This specifies a restore from the B carrier tape device to the B

carrier disk device.

active This specifies a restore on the active SPE.

standby This specifies a restore on the standby SPE.

both This specifies a restore on both SPEs. If the MSS on either SPE is

inaccessible, the restore will abort on both SPEs.

either This specifies a restore on both SPEs. If the standby SPE is

inaccessible, the active SPE only will be restored.

incremental This specifies that all data on tape marked “good” that has a date

newer than the date on the disk be copied to the disk from the

tape.

full This specifies that all data be copied to the disk regardless of the

dates and the status of the data (e.g., “good” or “bad”).

Processor This identifies the processor carrier that was backed up

(SPE-A or SPE-B).

Command

Completion

Status

This field displays one of various self-explanatory messages

indicating the success or failure of the command.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-167resume hardware-group

The following display shows a typical result when restore disk is entered.

resume hardware-group

In the course of execution of a test hardware-group command, it may be

desirable to halt the test temporarily or permanently. This is accomplished by

either the cancel hardware-group command for a background test, or by

pressing Cancel for a foreground test. Resume hardware-group enables you to

restart the hardware group test at the point where it was canceled. This

capability is not available if another hardware group test has been started. The

status of a hardware group test can be obtained with status hardware-group.

When test hardware-group all-ports is canceled, the internally generated port

translations for previously untranslated ports are removed. If resume

hardware-group is then entered, only customer-administered ports will then be

tested. resume does

not

reinstate the port translations that were removed by

cancellation of the test.

Output

When a test that was executing in the background is resumed, a success

message is displayed. When a test that was executing in the foreground is

resumed, test results are displayed.

restore disk

RESTORE DISK

Processor Command Completion Status

SPE-A Success

SPE-B Success

Command Successfully Completed

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-168save announcements

save announcements

!CAUTION:

Do not execute save announcements if there is an unresolved problem

with the HOST-ADAPTR maintenance object. Save translations should not

be done to a tape or disk device with unresolved problems. Doing so may

destroy a good copy of the files.

!CAUTION:

The option to save announcements to only one SPE in a duplicated system

should be used with care since it causes two inconsistent versions to exist

in storage.

!CAUTION:

The save command can take up to 40 minutes to complete. Avoid pressing

ENTER

during this time since doing so will cause the result messages to be

lost.

The save announcements command copies announcement data from the

TN750B Integrated Announcement circuit pack to the Mass Storage System

(MSS). Default devices are the disk in a disk/tape system, and the devices in

both SPEs in a duplicated system. Other options are available as described

below.

Save announcements writes two identical copies of the announcement data to

each specified device. Each copy bears the same time-stamp, (the time at which

the first copy was written). Each copy is also marked with the state of the copy

(“good” or “bad”).

Execution of this command requires the presence of a TN750B circuit pack and

an administered announcement data module and associated system port.

The command is disallowed or aborts if:

■An announcement data module and system port data module are not

administered.

■The announcement data module port is out of service or already in use.

■No announcements are on the board.

■An integrated announcements session is in progress.

■The board is currently being uploaded or downloaded.

[disk | tape]

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-169save announcements

■The tape drive is specified and no tape is in the tape drive or the tape is

write-protected.

■No system access port is available.

■The MSS is in use by another user or by maintenance.

■The specified device or SPE is not in service.

■The standby SPE is specified and shadowing is not enabled.

A user cannot record announcements while a save announcements command is

in progress. However, 15 channels are still available for announcement playback

(one is reserved for uploading and downloading).

When MSS devices on both SPEs in a duplicated system are specified, save

announcements will save data from the announcement board to the active and

standby devices in parallel. The status of each save operation is reported

separately. If one save operation fails, the save to the other device continues.

Thus, the data is not lost. In this case, announcement date is inconsistent

between the two devices. In case of a failure due to hardware faults or

spontaneous SPE interchange, the user must make the announcement files on

the two MSS devices consistent.

If a hardware failure occurs during a save announcements operation, software

will log a hardware error. Maintenance software will invoke tests to diagnose and

attempt to correct the problem. If corrective action fails, an alarm is raised

against the ANNOUNCE maintenance object. Follow procedures recommended

under ANNOUNCE in Chapter 9, ‘‘ABRI-PORT (ASAI ISDN-BRI Port)’’.

If a good copy of the announcement file is not available on the MSS, the restore

announcements command can not be executed until after a successful save

announcements is completed. The announcements on the board are still

accessible and usable.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-170save announcements

Parameters

Examples

save announcements

save announcements active disk

save announcements standby tape

save announcements spe-a disk

active This option specifies writing to the specified device in the currently

active SPE.

standby This option specifies writing to the specified device in the standby

SPE.

spe-a This option specifies writing to the specified device in the SPE on

the A carrier.

spe-b This option specifies writing to the specified device in the SPE on

the B carrier.

both This option specifies writing to the specified device in each SPE

concurrently. A failure in accessing either device causes the entire

operation to fail and neither device is written to.

either This option specifies writing to the specified device in both SPEs

concurrently. If there is a failure in accessing one of the devices,

the announcement data will still be written to the other one.

disk This option specifies writing to the disk drive. Disk is the default

device.

tape This option specifies writing to the tape drive.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-171save translation

Output

The following display shows a typical result when save announcements is

entered on a system with simplex SPE.

save translation

NOTE:

The save command can take up to 15 minutes to complete. Avoid pressing

the ENTER key on the keyboard during this time, since doing so will cause

the result messages to be lost.

All translation data is kept in volatile system memory during normal operation. In

the event of a power outage or certain system failures, data in memory is lost.

The save translation command allows the user to store on disk or tape the

translation data currently in memory. This operation can be executed as part of

scheduled background maintenance or on demand. The defaults are to save to

disk and, on a system with duplicated SPEs, to both SPEs.

Processor The SPE(s) to which announcement data was written (SPE-A or

SPE-B).

Command

Completion

Status

The result of command execution, with a self-explanatory

message explaining any failure or abort.

Error Code Each device holds two copies of the announcements file. This

field indicates whether both copies on the device were

successfully stored:

2 = Both copies of the file were saved.

1 = One copy was saved and one failed.

0 = Neither copy was saved.

[disk | tape]

save announcements Page 1 of 1 SPE A

SAVE ANNOUNCEMENTS

Processor Command Completion Status Error Code

SPE-A Success 2

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-172save translation

!CAUTION:

Save translation should not be executed if there is an unresolved problem

with the HOST-ADAPTR maintenance object. Save translations should not

be done to a TAPE or DISK device with unresolved problems. Doing so may

destroy a good copy of the files.

!CAUTION:

On systems with duplicated SPEs, the capability to save translation to only

one SPE should be used with extreme caution since it results in the two

SPEs having inconsistent translation data in storage.

The save translation cannot be executed if translation data is being changed by

an administration command.

Parameters

Examples

save translation disk

save translation either tape

Output

Results are displayed for each SPE.

spe-a This specifies saving translation data to the MSS device on the SPE

in carrier A only.

spe-b This specifies saving translation data to the MSS device on the SPE

in carrier B only.

active This specifies saving translation data on the active SPE only.

standby This specifies saving translation data on the standby SPE only.

both This specifies saving translation data on both SPEs concurrently (the

default). The command will fail if the specified device on either SPE

is inaccessible, and neither device will be saved to.

either This specifies saving translation data on both SPEs. If the standby is

inaccessible, the save will still be done on the active SPE.

disk This specifies saving translation data to the disk drive. Disk is the

default device.

tape This specifies saving translation data to the tape drive.

Processor This identifies the SPE to which translation data was saved

(SPE-A or SPE-B).

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-173set options

The following display shows a typical result of entering save translation on a

duplex system.

set options

This command allows the user to administer whether certain alarms are reported

to INADS or whether they are downgraded to a minor alarm, warning alarm, or no

alarm.

Synopsis

set options

Permissions

The following default logins may execute this command: inads, init.

Examples

set options

Command

Completion

Status

One of the following results is displayed:

Success

Disk device is out of service

Tape device is out of service

save translation

SAVE TRANSLATION

Processor Command Completion Status

SPE-A Success

Command Successfully Completed

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-174set options

Description

This special command enables the technician (that is, remote user with INADS

permission) to select which types of maintenance categories report alarms

automatically and which types require the customer to call in. Judicious use of

this command can reduce the number of ineffective alarms to the TSC. For the

set options command to be effective, the default settings specified in this

section should always be used. These settings are not intended to be changed

on a per-system basis. Special circumstances (for example, special studies) may

require temporary changes under the guidance of Tiers 3 and 4.

NOTE: Alarms can’t be upgraded.

Defaults

Initially, the alarm reporting options for On-board Trunk Alarms (Alarm Group 1),

both Major and Minor, are set to “yes” (y); all others are set to “warning” (w). All

trunk groups are associated with alarm severity group 1 by default.

Parameters

None.

Help Messages

If the user presses HELP after entering set options, the following message is

displayed:

Entry is not required

Error Messages

If the command entered is in conflict with another currently executing command,

then a message is displayed showing the login id of the conflicting user and the

conflicting command. The message is as follows:

’login id’:’command’ has a command conflict

If during the execution of a command a resource problem occurs that requires

the user to restart the command, then the following message is displayed:

Command resources busy;

Press CANCEL to clear, and then resubmit

If all of the available maintenance resources are currently in use, then the

following message is displayed:

All maintenance resources busy; try again later

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-175set options

Form Input

After entering the command set options, the user is presented with the following

form.

NOTE:

The remaining Trunk Group information is shown on the next 6 pages and is

not documented in this Manual.

On the first page of the Alarm Reporting Options Form, the user selects the alarm

severity options for station alarms, the four trunk alarm severity groups, the

adjunct alarms, off-board DS1 alarms, off board PGATE-PT alarms, and other

off-board alarms. On the second page, known as the Alarm Reporting Options

Form, the user assigns an alarm severity group to each trunk group. This feature

set options Page 1 of 8

ALARM REPORTING OPTIONS

Major Minor

On-board Station Alarms: w w

Off-board Station Alarms: w w

On-board Trunk Alarms (Alarm Group 1): y y

Off-board Trunk Alarms (Alarm Group 1): w w

On-board Trunk Alarms (Alarm Group 2): w w

Off-board Trunk Alarms (Alarm Group 2): w w

On-board Trunk Alarms (Alarm Group 3): w w

Off-board Trunk Alarms (Alarm Group 3): w w

On-board Trunk Alarms (Alarm Group 4): w w

Off-board Trunk Alarms (Alarm Group 4): w w

On-board Adjunct Alarms: w w

Off-board Adjunct Alarms: w w

Off-board DS1 Alarms: w w

Off-board PGATE-PT Alarms: w w

Off-board Alarms (Other): w w

set options Page 2 of 8

TRUNK GROUP ALARM OPTIONS

(Alarm Group)

01: 1 11: 1 21: 1 31: 1 41: 1 51: 1 61: 1 71: 1 81: 1 91: 1

02: 1 12: 1 22: 1 32: 1 42: 1 52: 1 62: 1 72: 1 82: 1 92: 1

03: 1 13: 1 23: 1 33: 1 43: 1 53: 1 63: 1 73: 1 83: 1 93: 1

04: 1 14: 1 24: 1 34: 1 44: 1 54: 1 64: 1 74: 1 84: 1 94: 1

05: 1 15: 1 25: 1 35: 1 45: 1 55: 1 65: 1 75: 1 85: 1 95: 1

06: 1 16: 1 26: 1 36: 1 46: 1 56: 1 66: 1 76: 1 86: 1 96: 1

07: 1 17: 1 27: 1 37: 1 47: 1 57: 1 67: 1 77: 1 87: 1 97: 1

08: 1 18: 1 28: 1 38: 1 48: 1 58: 1 68: 1 78: 1 88: 1 98: 1

09: 1 19: 1 29: 1 39: 1 49: 1 59: 1 69: 1 79: 1 89: 1 99: 1

10: 1 20: 1 30: 1 40: 1 50: 1 60: 1 70: 1 80: 1 90: 1 100: 1

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-176set options

enables the technician to reduce the level of alarms reported for on-board or

off-board trouble conditions.

The following alarm options are available:

■Minor

Alarms are raised as maintenance testing discovers them but the severity

of the alarm is downgraded to a minor. Alarmed resources that would

have normally been taken out of service are still taken out of service. LEDs

on the port board and maintenance board follow the normal Minor alarm

LED strategy and there is a call to the receiving OSS.

■Warning

Alarms are raised as maintenance testing discovers them, but the severity

of the alarm is downgraded to a warning. The advantage to the technician

here is that the Alarm Log can still be used to pinpoint trunk or station

problems reported by the customer. Alarmed resources that would

normally have been taken out-of-service are still taken out-of-service.

Alarm LEDs light on the port circuit pack and Maintenance circuit pack as

before, but no attendant LEDs or stations reporting alarms are affected.

There is no call to INADS.

■Report

This option treats the alarms in the same way as the warning category with

one exception: alarms are reported to INADS using a special WARNING

category. When an alarm of this type is received, INADS logs the

occurrence and either creates a trouble ticket or closes it immediately.

The retry strategy for a call of this type is similar to normal Major or Minor

alarm reports. However, the acknowledgment LED on the attendant

console or alarm reporting station does not reflect the status of the call.

■Yes

Alarms are raised in the normal manner. There is no filtering of alarm data.

■No

Alarms raised on a trunk, station, or adjunct in this category are dropped.

Error information is provided as before, but there is no trace of an alarm.

There is no LED activity and no call to INADS. Because resources are

taken out-of-service without any record, this option is recommended only

when other options do not provide the desired result.

The alarm options can be administered only on a system-wide basis for the

following alarm categories:

■Major on-board station alarms

■Minor on-board station alarms

■Major off-board station alarms

■Minor off-board station alarms

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-177set options

Four alarm severity groups are provided for trunk alarms. You can administer the

alarm options for the categories listed below in each alarm severity group.

However, in G1, the alarm options can be administered only on a system-wide

basis for the following categories:

■Major on-board trunk alarms

■Minor on-board trunk alarms

■Major off-board trunk alarms

■Minor off-board trunk alarms

For Adjuncts, an alarm severity option is assigned to each of the following

categories:

■Major on-board adjunct alarms

■Major off-board adjunct alarms

■Minor on-board adjunct alarms

■Minor off-board adjunct alarms

You can also administer the options on a system-wide basis for Minor off-board

DS1 Interface circuit pack alarms.

Alarm reporting options information in the Alarm Reporting Options Form is

considered translation data and, thus, is preserved through all levels of restart.

This feature affects the alarming of the MOs listed below. Neither the trunk nor

the station category applies to alarms raised on the common portion of the circuit

pack.

In all cases, if the option associated with the alarm type is set to “n,” the alarm

report is dropped. All error information about the alarm is intact, but there is no

record of an alarm and no LEDs light on the port circuit pack, the Maintenance

circuit pack, the attendant console, or alarm reporting station to indicate a

problem.

If the option is set to “warning” or “report,” port circuit pack LEDs and LEDs on

the Maintenance circuit pack are affected the same as normal warning alarms.

The default parameters are as follows:

■Downgrade all station, trunk (except on-board trunk alarms), and Minor

DS1-BD alarms to warning alarms.

■On-board Major and Minor trunk alarms, should continue to raise alarms

and report to INADS.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-178set options

Station MOs Affected By This Command

NOTE:

Although alarms on these MOs may appear as warnings, the alarms should

be investigated with user-reported problems.

■Analog Lines (ANL-LINE, ANL-NE-L, ANL-16-L)

■Digital Lines (DIG-LINE)

■Hybrid Lines (HYB-LINE)

■MET Lines (MET-LINE)

■ISDN-BRI Lines (BRI-PORT, BRI-SET)

Trunk maintenance is characterized by an escalation of a Minor alarm to a Major

alarm if more than 75 percent of the members of the trunk group are alarmed. If

the option for the trunk category is set to “warning,” “minor,” “report,” or “no,” this

no longer happens. Maintenance removes an individual trunk member

out-of-service according to the normal criteria used for Major and Minor alarms.

Trunk MOs Affected By This Command:

NOTE:

Although alarms on these MOs may appear as warnings, the alarms should

be investigated with user-reported problems.

■Auxiliary Trunks (AUX-TRK)

■Central Office Trunks (CO-TRK)

■Direct Inward Dialing Trunks (DID-TRK)

■Direct Inward and Outward Dial Trunks (DIOD-TRK)[G1.2SE only]

■DS1 Central Office Trunks (CO-DS1)

■DS1 Direct Inward Dialing Trunks (DID-DS1)

■DS1 Tie Trunks (TIE-DS1)

■ISDN Trunks (ISDN-TRK)

■Tie Trunks (TIE-TRK)

Circuit Pack MOs Affected By This Command

NOTE:

Although alarms on these MOs may appear as warnings, the alarms should

be investigated with user-reported problems.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-179set options

NOTE:

Trunks that are not members of Trunk Groups, (e.g. PCOLs) are

downgraded according to the alarm severity of group one.

■DS1 Interface Circuit Pack (DS1-BD)

Adjunct-Related MOs Affected by this Command

NOTE:

Although alarms on these MOs may appear as warnings, the alarms should

be investigated with user-reported problems.

■ASAI Adjunct (ASAI-ADJ)

■Lucent Adjunct Port (ATT-PORT)

■Ethernet ASAI Port (LGATE-PT)

■Ethernet ASAI Adjunct (LGATE-AJ)

■Ethernet Lucent Port (ATTE-PT)

■Ethernet Lucent Adjunct (ATTE_AJ)

■ISDN-BRI Ports connected to Adjuncts (ABRI-PORT)

Although adjuncts are administered as stations, the administration of alarm

severity for the station alarm group does not affect the alarm severity levels of the

adjuncts. Similarly, the administration of alarm severity for the adjunct alarm

group does not affect the alarm severity levels for other types of stations.

PGATE-PT and associated Link MOs Affected by

this Command

NOTE:

Although alarms on these MOs may appear as warnings, the alarms should

be investigated with user-related problems.

■

See

Packet Gateway Port (PGATE-PT)

for other Link associated MOs

affected by this Command

NOTE:

Although alarms on these MOs may appear as warnings, the alarms should

be investigated with user-related problems.

■EPN Maintenance Circuit Pack (MAINT)

■Expansion Interface (EXP-INTF)

■ISDN-PRI Signaling Group (ISN-SGR)

■Journal Printer (JNL-PRNT)

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-180set options

■PMS Link (PMS-LINK)

■PMS log printer (PMS-LOG)

■Primary CDR Link (PRI-CDR)

■Secondary CDR Link (SEC-CDR)

■SPE Select Switches (SPE-SELEC)

■Synchronization (SYNC)

■Packet Gateway Port (PGATE-PT)

■System Printer (SYS-PRNT)

■TDM Clock (TDM-CLK)

■Tone Generator Circuit Pack (TONE-BD)

Field Help

Since all fields on the first page may have the same values, then pressing HELP in

any field on the first page presents the following field help message:

m(inor) n(o) r(eport) w(arning) y(es)

The following is a description of the values:

All fields on page 2 may have the same values. Pressing HELP in any field on

page 2 gives the following field help message:

Enter alarm group number: 1 to 4

The alarm group number is a way of distinguishing four different groups of

alarms. These alarm groups allow the user to specify that alarms in different

groups are handled differently from those in other groups.

Field Error Messages

All of the fields on the first page allow the same values. Only one error message

is printed for all first page fields. If the value is not one of the listed characters

(m,n,r,w,or y) then the following message is displayed:

m(inor) Downgrade the major alarm to a minor alarm and report the alarm

to INADS.

n(o) Do not log the alarm or report it to INADS.

r(eport) Downgrade the alarm to a warning and report the warning to

INADS.

w(arning) Downgrade the alarm to a warning, log it but do not report the

alarm to INADS.

y(es) Log and report the alarm to INADS.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-181set pnc

“X” is an invalid entry; please press HELP key

All of the fields on page 2 allow the same values. If the value in one of these fields

is not numeric, the following message is displayed:

Entry must be all digits

All of the fields on pages page 2 allow the same values. If the value in one of

these fields is a digit other than 1, 2, 3, or 4, the following message is displayed:

Entry out of range

Output

After the user has entered in the changes to the options and pressed SUBMIT,

the following message appears at the bottom of the screen:

Command successfully completed

Feature Interactions

None.

set pnc

set pnc lock | unlock

On Critical Reliability systems (duplicated PNC), set pnc lock locks the active

port network connectivity in the active state. PNC interchanges will be prevented

and the active port network connectivity will remain active regardless of its state

of health. Duplicate call setup will still take place, though the standby is not

available for service. This condition can also be initiated by the reset pnc

interchange override-and-lock command. You can tell if the PNC is locked by

looking at the Software Locked? field on the status pnc screen. (The

Interchange Disabled? field refers to the antithrashing mechanism.)

Set pnc unlock releases the lock and enables subsequent interchanges to take

place.

If the health of the active pnc has degraded to worse than that of the standby

pnc, unlocking the active port network connectivity can cause an immediate PNC

interchange This condition can be foreseen by use of status pnc.

System restarts remove a PNC lock.

!CAUTION:

If the active PNC experiences problems while in the locked state, service

disruptions may occur that would ordinarily be avoided by PNC

interchange.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-182set signaling-group

Parameters

set signaling-group

set signaling-group group#

The set signaling-group command sets the secondary D-Channel in the

specified signaling group to be the primary D-Channel. The primary D-Channel

becomes the secondary D-Channel. A signaling group is a collection of

B-channels signaled for by a designated single D-channel or set of D-channels

over an ISDN-PRI link.

Parameters

set snc

set snc UUCSS [override]

This command sets which switch node clock (SNC) circuit pack in a given switch

node carrier is active.

NOTE:

This command is valid only on a High Reliability system with a Center Stage

Switch (duplicated SPE, simplex PNC). In this configuration, SNCs are

duplicated on each switch node carrier.

Parameters

set synchronization

set synchronization UUC [SS]

lock PNC interchanges will be prevented, and the active port network

connectivity will be locked on-line.

unlock Releases the PNC lock.

group# The signaling group identifier is an administered number assigned

to each signaling group.

override This qualifier will force execution of the set command regardless of

the health of the standby SNC circuit pack.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-183set tdm

This command sets a specific DS1 trunk or tone-clock circuit pack as the

reference source for system synchronization signals. It is permitted only after

synchronization has been disabled with disable synch. Any administered DS1

trunk or

active

tone-clock may be entered with the set command. The DS1 or

tone-clock will remain the synchronization reference until either the set command

specifies another circuit pack, or enable synchronization is entered.

After an enable synchronization, the administered primary or secondary

synchronization source will become the synchronization reference. If no primary

or secondary source is administered, an active tone-clock will be used as the

synchronization reference.

See SYNCH in Chapter 9, ‘‘ABRI-PORT (ASAI ISDN-BRI Port)’’ for details.

Parameters

set tdm

set tdm port-network PN# bus a | b [override]

This command determines which of the paired TDM buses (A or B) on a port

network will carry the control channel and dedicated tone time slots. Each port

network has a 512 time-slot TDM bus configured as two separate 256 time-slot

buses. This division allows for duplication of control channels and time slots

dedicated for use by system tones. On power-up, the control channel is carried

on the A bus, and the tone time slots are carried on the B bus. Execution of this

command puts both the control channel and the tone time slots on the specified

bus.

Under extremely heavy traffic load, tone time slots on the bus that is not currently

carrying the tones may be used for call processing. Use of the override

command under these conditions will cause calls to be dropped.

See TDM-BUS in Chapter 9 for details.

UUCSS The location of the DS1 Interface or Tone-Clock circuit pack

selected to provide the reference timing signals for system

synchronization. The location of a DS1 trunk is entered as UUCSS.

The location of a tone-clock, which must be active, is entered as

UUC. UU represents the cabinet number, C the carrier letter, and SS

the slot number.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-184set time

Parameters

Examples

set tdm port-network 2 bus a

set time

This command brings up a form showing the current day, date, month, year and

time kept by the system clock. These entries can be edited to update the system

time. The second field is set to zero whenever the time on the clock is altered. If

no new entries are made, system time remains unchanged.

Input Form

An input form with the following fields is displayed. The current time, or default

time will be displayed in the fields.

PN# The Port Network number of the TDM bus to be set. List cabinet

displays port network numbers for a given cabinet.

bus One of the paired TDM buses, a or b.

override This option forces the setting of a bus which is out of service or a

bus whose dedicated tone time slots are in use by call

processing.

!CAUTION:

Use of this option disrupts service.

Day of the Week: Valid entries are Monday through Sunday.

Day of the Month: 1-31 are valid entries. A check for leap year is also

made.

Month: January through December.

Year: The year must be saved as translation data and

passed to the kernel whenever kernel memory is

corrupted (system reboot or cold I restart), or the

data is changed.

Hour: 0-23 are valid entries.

Minute: 0-59 are valid entries.

Second: This field is reset automatically and cannot be

altered.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-185set tone-clock

set tone-clock

set tone-clock UUC [override]

On port networks with duplicated Tone-Clocks, this command is used to select

which of the two Tone-Clock circuit packs is to be active.

In EPNs, the A-carrier Tone Clock is the

preferred

Tone-Clock. It is always active

unless a failure, maintenance testing, or use of this set command has caused an

interchange to the B-carrier Tone-Clock. If you have used this command during a

maintenance session, set the EPN Tone-Clock back to the A carrier when you are

finished, assuming it is healthy. Tone-Clock interchanges executed by

scheduled daily maintenance cause the standby to become active for 20

seconds and then interchange back to whichever Tone-Clock was originally

active.

Cabinet number defaults to 1.

Parameters

Examples

set tone-clock 01c override

set tone-clock a

override This qualifier forces execution of the set command regardless of

the health of the Tone-Clock circuit pack.

!CAUTION:

Use of this option is destructive to an entire port network for

EPNs and for the entire system for PPN Tone-Clocks.

set time Page 1 of 1

DATE AND TIME

DATE

Day of the Week: _________ Month: _________

Day of the Month: __ Year: ____

TIME

Hour: __ Second:

Minute: __

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-186set vector

set vector

set vector reset-level# [spe-standby | spe-active | spe-maint | spe-smm]

The set vector command specifies the reset levels which will activate a core

dump. When a designated reset occurs, a current copy of the system’s memory

is stored on the disk device, allowing the information to be examined later for

troubleshooting purposes.

To force an immediate core dump, set the appropriate bit using this command

and then execute reset system of the corresponding level,

but

be aware of

possible disruption as a result of the reset.

!CAUTION:

Note that level 1 (WARM) resets may result in a more destructive level 2

(COLD2) reset for certain settings of the vector.

!CAUTION:

Service is disrupted whenever an active SPE is performing a core dump.

Execution

The following actions are taken in response to the vector settings listed below

when a designated reset takes place. In all cases after a core dump has been

performed, the vector will be cleared.

Simplex SPE

When a system restart occurs on a system with simplex (SPE) with the

corresponding vector bit set, the core dump is written to the primary MSS device.

Once the core dump is written, the vector is cleared and the restart is performed.

When a WARM restart (reset system 1) is performed and the vector is set for

WARM restarts, a COLDII is executed after the WARM restart in order to recover

the packet interface circuit pack. Packet interface recovery is necessary due to

delays of writing the core dump.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-187set vector

Duplicated SPE Options

Feature Interactions

In a simplex SPE system, service will be disrupted while a core dump is being

written to the primary Mass Storage System device. In addition, service will

continue to be disrupted until the software is restarted at an appropriate level.

These “disruption” times will vary depending upon the particular switch

configuration.

If a core dump file already exists, a subsequent core dump will overwrite it.

If the disk is not accessible, a core dump cannot be executed.

A core dump file can overwrite other files on tape. Caution must be exercised

when generating a core dump on tape.

The vector will be cleared when a system restart of the proper level is performed

regardless of whether the core is actually dumped.

If handshake is down in a duplicated system, while spe-active, spe-standby, or

spe-maint is set, the active vector will be set, but the standby vector will retain its

former value. This could lead to different vectors on the active and standby SPEs.

Set vector should be reentered after handshake is back up. (Setting spe-smm

spe-active The active SPE will perform a core dump. When a WARM restart

(reset system 1) is performed and the vector is set for WARM

restarts, a COLDII is executed after the WARM restart in order to

recover the packet interface circuit pack. This packet interface

recovery is necessary due to the delays of writing the core dump

spe-standby The standby SPE will perform a core dump after its memory has

been refreshed. When a WARM restart (reset system 1) is

performed and the vector is set for WARM restarts, a COLDII is

executed after the WARM restart in order to recover the packet

interface circuit pack. This packet interface recovery is

necessary due to the delays of refreshing the standby processor.

spe-maint The standby SPE will perform a core dump without refreshing its

memory first. This option is the default on a duplicated system.

spe-smm The standby SPE will perform a core dump. This allows a dump

of the Standby Maintenance Monitor (SMM) when the standby

SPE is experiencing problems. If an interchange occurs after the

standby (spe-smm) SPE vector has been set, a core dump will

not be performed on either the new active SPE or the new

standby SPE regardless of the level of restart that occurs.

However, if another interchange occurs making the new active

SPE the standby SPE once again, a core dump on the standby

SPE will occur if the standby restarts at the appropriate level.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-188set vector

while handshake is down returns an error message.) If handshake is up, the

selected vector (active or standby) will be set and the other cleared.

If an interchange occurs after the spe-smm vector has been set, a subsequent

restart will not trigger a core dump. However, if

another

interchange occurs, a

core dump on the standby SPE will take place in response to a reset of the

appropriate level on the standby.

Parameters

condition A hexadecimal value representing the combination of reset levels

(1= warm restart, 2= cold-2 restart, 3=cold-1 restart, and 4=reboot)

that are enabled to initiate a core dump, as illustrated in the following

table.

Vector

Value Reset

Levels Vector

Value Reset

Levels

0 none 8 4

1191, 4

22a2, 4

3 1, 2 b 1, 2, 4

43c3, 4

5 1, 3 d 1, 3, 4

6 2, 3 e 2, 3, 4

7 1, 2, 3 f 1, 2, 3, 4

spe-standby This is the default for duplicated systems. If a restart of a

designated level occurs on the active SPE and the

corresponding vector bit is set, a core dump will be taken on the

standby SPE after the standby SPE has performed a refresh of

memory.

spe-active On duplicated systems, a restart on the active SPE will cause a

core dump to be taken on the active SPE.

!CAUTION:

A core dump performed with the spe-active option causes

a service disruption.

spe-maint On a duplicated system, if a restart of a designated level occurs

on the active SPE, a core dump will be taken on the standby

SPE without a refresh of its memory first.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-189status access-endpoint

status access-endpoint

status access-endpoint extension [print]

This command displays the operational of a non-signaling port on a DS1

interface or on an analog tie trunk circuit pack.

Output

The following display shows a typical result when status access-endpoint 2300

is entered.

status administered-connection

status administered-connection adm-conn# [print]

spe-smm On a duplicated system, if a restart of a designated level occurs

on the standby SPE, a core dump will be taken on the standby

SPE. This can be useful to debug Standby Maintenance Monitor

(SMM) problems.

Extension The extension number of the specified port.

Port The physical location (cabinet-carrier-slot-circuit) of the

port.

Communication

Type The type of communication supported by the channel:

56k-data, 64k-data, or voice-band-data.

Service State The operational status of the access-endpoint channel:

in-service/idle, out-of-service, maintenance-busy or

disconnected.

Connected

Ports The location of any facility/endpoint to which this

access-endpoint is connected.

status access-endpoint 2300 SPE A

ACCESS END-POINT STATUS

Extension: 2300

Port: 02B0905

Communication Type: 56k-data

Service State: disconnected

Connected Ports:

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-190status administered-connection

This commands displays the operational status of an administered connection.

To view administrative information for administered connections, use list

administered-connection and display administered-connection.

Parameters

Output

adm-conn# The number (1-128) of the administered connection as

assigned during administration.

Connection

Number: The number assigned to the administered connection.

Enabled? Whether the administered connection is enabled.

Originator: The extension of the access or data endpoint that originates the

connection.

Destination: The destination address used to route the administered connection.

Connection

State: The current status of the administered connection as follows:

connected = A connection between the originating and destination

endpoints is currently active.

restored = The connection has been restored. The session may or may

not have been preserved.

failed = The connection failed due to either an administrative error such

as a wrong number or a service-blocking condition such as barring of

outgoing calls.

Recovering from such a failure requires manual intervention. No further

attempt is made by the system to re-establish the administered connection

until the change administered- connection command is executed. If the

failure was caused by a transient condition, you may be able to

re-establish the connection by first disabling and then enabling the

connection via the “Enable?” field on the change administered

connection form. (The enable admin and disable admin

commands

affect only maintenance processes).

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-191status administered-connection

Connection

State:

(cont’d.)

The cause of the failure is reported as an ISDN cause value that is

recorded in the error log. Refer to the Hardware Error Log Table for

ADM-CONN in Chapter 9 to identify failure causes.

waiting to retry = The system is waiting between attempts to restore

the connection. The amount of time between attempts to restore is

administered on the administered connections form. Check the contents of

the Failure Cause field for information about why the administered

connection failed.

attempting to connect/attempting to restore = These are

transitional states during which an attempt is made to connect or restore

the administered connection. If an administered connection remains in this

state for longer than 1 minute, disable and then re-enable the connection.

If the problem still persists, or if the administered connection has retried a

number of times with administered connection origination

attempt timed out reported in the Failure Cause field, then make sure

that the originating data module is connected and the destination access

endpoint is not out-of-service.

not scheduled = The administered connection is enabled but is not

scheduled to be active at the current time.

Failure

Cause: This field displays a self-explanatory message indicating the reason for a

current state of attempting to connect, attempting to restore,

or failed. If the administered connection should be active but is not

connected, then this field shows the most recent reason for failure. See

also the above description of "Connection State: failed."

Number of

Retries: The number of consecutive failed attempts to establish the connection.

Auto

Restorable? When an administered connection fails, the system can automatically

attempt to restore the connection. This field indicates whether this

capability is activated on the administered connections administration

form.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-192status attendant

The following display shows a typical result when status administered-conn 3 is

entered. In this example, destination is another switch, and the destination

number consists of a trunk access code (512) and extension (26001).

status attendant

status attendant console# [print]

The status attendant command displays the operational state of the specified

attendant console. This information can help in trouble diagnosis and in locating

facilities to which the attendant console is connected.

status bri-port

status bri-port UUCSSpp [print]

The status bri-port command displays the service state, maintenance state and

layer 1 state of an ISDN-BRI port. Also displayed on this form is information on

the point-to-point signaling links carried over the port. For more information, see

BRI-PORT in Chapter 9, ‘‘ABRI-PORT (ASAI ISDN-BRI Port)’’.

Output

An extra section describing how to interpret the results of this command follows

the screen display.

Port The location of the ISDN-BRI port.

Service

State Whether the ISDN-BRI port is ‘‘in-service’’ or ‘‘out-of-service.’’

Maintenance

Busy? Whether maintenance testing is currently being performed on

the port.

status administered-connection 3 page 1 of 1

ADMINISTERED-CONNECTION STATUS

Connection Number: 3

Enabled? y

Originator: 71001

Destination: 51226001

Connection State: connected

Failure Cause:

Number of Retries:

Auto Restorable? y

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-193status bri-port

Layer 1

State The operational state of the physical connection (Layer 1) of the

ISDN link carried over the port:

activated = Layer 1 frames are being passed between the

port and BRI endpoints.

pend-activation = The port is in service, the layer 1

interface device is turned on and layer 1 frames are being sent

from the port, but the BRI endpoints are not responding.

deactivated = The layer 1 interface device on the BRI has

been turned off due to the port being out of service.

TEI Value The Terminal Endpoint Identifier (TEI) is a layer 2 addressing

parameter used by the switch to exchange information with BRI

endpoints over the point-to-point signaling link. The TEI is a

number from 1 to 127.

Layer2

State The operational state of the point-to-point signaling link (Layer

2):

assigned = The link is currently in the AWAIT_EST (Await

Establish) state at layer 2. If the BRI endpoint supports TEI

allocation procedures, those procedures have been

successfully executed and a TEI has been assigned to the

endpoint by the switch.

established = The link is in the MF_EST_NORM (Multi-Frame

Established Normal) state at layer 2. The switch has

successfully started the link and is now capable of exchanging

layer 3 frames with the endpoint. If the endpoint does not

support SPID initialization procedures, the voice extension of

the endpoint associated with the link is also displayed. This is

the normal state for a link in a point-to-point wiring configuration.

L3-established = The link is in the MF_EST_NORM state at

layer 2 and SPID initialization procedures have been

successfully completed. The voice extension of the endpoint

associated with the link is also displayed. This is the normal

state for a link in a multi-point wiring configuration.

hyperactive = Traffic on this link has exceeded the threshold

and the link has been suspended.

Endpt

Extension The extension of the voice/data endpoint associated with the

link. This field is blank if the link is not in the established or

L3-established state.

Endpt SPID The SPID (Service Profile Identifier) administered for the

voice/data endpoint. This field is blank if the link is not in the

established or L3-established state.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-194status bri-port

The following display shows a typical result when status bri-port is entered.

Service

SPID? If the link is associated with the Service SPID this field displays

yes and the Endpoint Extension field is blank. Otherwise this

field is blank. Service SPID is a feature used by service

technicians to check building wiring between the switch and the

BRI endpoint.

Table 8-9. Interpreting BRI-Port Status Reports

Error

Type Aux

Data Associated

Test Alarm

Level On/Off

Board Test to Clear Value

ASAI,

BRI 0-126 Assigned blank blank This is a transitory state for BRI

endpoints and ASAI adjuncts. The

switch is attempting to establish the link.

1. Check the endpoint and wiring by

following the SPID Facility Test

Procedure described in the BRI-SET

section of Chapter 9.

2. Repeat status bri-port to determine

that the Layer 2 state of the

signaling link is either

L3-Established (for ASAI

adjuncts and BRI endpoints

supporting MIM initialization) or

Established (for fixed TEI BRI

endpoints and automatic TEI BRI

endpoints not supporting MIM

initialization). If it is not, follow

normal escalation procedures. (A

MIM or management information

message is a level-3 message that

conveys management and

maintenance information between a

communications system and a BRI

terminal.)

Continued on next page

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-195status bri-port

ASAI 0-63 Established blank blank This is a transitory state for ASAI

adjuncts. ASAI signaling is connected at

Layer 2 but the Layer 3 Restart

procedure has not been completed

between switch and adjunct.

1. Check the adjunct by following the

recommended repair procedures

of the manufacturer.

2. Repeat status bri-port and

determine whether the L2 state of

the signaling link is L3-Established.

If it is not, follow normal escalation

procedures.

BRI 0-126 Established ext# blank This is the normal state for non-MIM

initializing, fixed, and automatic TEI BRI

endpoints.

BRI,

ASAI 64-126 Established blank blank This is a transitory state for automatic

TEI BRI endpoints that support MIM

initialization.

1. Verify that SPID administration on

the switch and the endpoint are

consistent. Repeat status bri-port

to determine whether the Layer 2

state of the signaling link is

L3-Established.

2. Try replacing the endpoint. Repeat

status bri-port to determine

whether the Layer 2 state of the

signaling link is L3-Established.

If it is not, follow normal escalation

procedures.

BRI 64-126 L3-Established ext# blank This is the normal state for automatic TEI

BRI endpoints that support MIM

initialization.

BRI,

ASAI 64-126 L3-Established blank yes A demand SPID Facility Test is in

progress on the port, and the link is not

currently associated with a BRI

endpoint. See SPID Facility Test

Procedures described in the BRI-SET

section of Chapter 9, ‘‘ABRI-PORT (ASAI

ISDN-BRI Port)’’.

Table 8-9. Interpreting BRI-Port Status Reports — Continued

Error

Type Aux

Data Associated

Test Alarm

Level On/Off

Board Test to Clear Value

Continued on next page

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-196status bri-port

BRI 64-126 L3-Established ext# yes A demand SPID Facility Test is in

progress on the port, and the link is

associated with an endpoint on the port.

See SPID Facility Test Procedures

described in the BRI-SET section of

Chapter 9.

BRI 0-126 L3-Established blank blank An invalid SPID is assigned to link.

1. Change the SPID value in the BRI

endpoint to match the SPID

administered to the BRI endpoint on

the port. Repeat status bri-port to

determine whether the Layer 2 state

of the signaling link is

L3-Established. If it is not, follow

normal escalation procedures.

BRI 0-126 L3-Assigned ext# blank This is a transitory state for BRI

endpoints that support MIM initialization.

1. Wait 5 seconds and repeat the

command. If the state has not

changed, continue with Step 2.

2. Make sure SPID administration on

the switch and endpoint are

consistent. Repeat status bri-port

to determine whether the Layer 2

state of the signaling link is

L3-Established. If it is not, go to

Step 3.

3. Try replacing the endpoint. Repeat

status bri-port to determine

whether the Layer 2 state of the

signaling link is L3-Established.

If it is not, follow normal escalation

procedures.

Table 8-9. Interpreting BRI-Port Status Reports — Continued

Error

Type Aux

Data Associated

Test Alarm

Level On/Off

Board Test to Clear Value

Continued on next page

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-197status bri-port

BRI 0-126 L3-Assigned ext# yes This is a transitory state for BRI

endpoints that support MIM initialization

when a SPID Facility Test has been

used to initialize the station.

1. Wait 5 seconds and repeat the

command. If the state has not

changed continue with Step 2.

2. Make sure SPID administration on

the switch and endpoints are

consistent. Repeat status bri-port

to determine whether the Layer 2

state of the signaling link is

L3-Established. If it is not, go to

Step 3.

3. Try replacing the endpoint. Repeat

status bri-port to determine

whether the Layer 2 state of the

signaling link is L3-Established.

If it is not, follow normal escalation

procedures.

ASAI

BRI 0-126 Hyperactive ignore ignore Link has sent too many messages per

unit time. Signaling has been

suspended. After 60 seconds, the

system attempts to put the link into

service. If a link remains in this state

while there is no activity at the BRI

endpoint, take the following steps:

1. Make sure SPID administration on

the switch and endpoints are

consistent. Repeat status bri-port

to determine whether the Layer 2

state of the signaling link is

L3-Established. If it is not, go to

Step 2.

2. Try replacing the endpoint. Repeat

status bri-port to determine

whether the Layer 2 state of the

signaling link is L3-Established.

If it is not, follow normal escalation

procedures.

Table 8-9. Interpreting BRI-Port Status Reports — Continued

Error

Type Aux

Data Associated

Test Alarm

Level On/Off

Board Test to Clear Value

Continued on next page

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-198status bri-port

Interpreting Results of BRI-Port Status Reports

Table 8-9 will help to interpret results of the status bri-port command. Find the

combination of output field values contained in your report and follow the

recommendations for the type of endpoint connected to the portStatus Cabinet

status cabinet UU [print]

This command displays the operational status and attributes of the specified

cabinet. The output screen displays configuration information for each carrier,

connectivity and alarm information for each port network or switch node, and the

emergency transfer status of the cabinet.

The cabinet number defaults to 1.

ASAI 0-126 L3-Restarting ext# The switch has sent a Restart message

to the adjunct but has not yet received a

Restart Acknowledgment message

from the adjunct.

ASAI 0-126 L3-Restarted ext# After receiving a Restart

Acknowledgment message, the switch

has sent a Heartbeat message to the

adjunct and is waiting for a response.

ASAI 0-126 L3-Established ext# This is the normal state for ASAI adjunct.

Table 8-9. Interpreting BRI-Port Status Reports — Continued

Error

Type Aux

Data Associated

Test Alarm

Level On/Off

Board Test to Clear Value

Continued on next page

status bri-port 1c1701 Page 1 of 1 SPE A

STATUS BRI-PORT

Port: 01C1701

Service State: in-service

Maintenance Busy?: no

Layer 1 State: activated

TEI Value Layer2 State Endpt Extension Endpt SPID Service SPID?

Link1 64 13-established 1010 1010

Link2

Link3

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-199status bri-port

Output

Carrier Location The cabinet number and carrier letter of each carrier in the

cabinet.

PN/SN Number The Port Network number (1-22) or Switch Node number (1 or 2)

of the indicated carrier.

Carrier Type The type of the indicated carrier: processor, port,

expansion-control, switch-node, dup-sw-node or not-used.

Cabinet Type One of the following types:

MCC Multicarrier cabinet

SCC Single carrier cabinet

S75XE System 75 (pre-R1V4) single carrier XE cabinet

blank The cabinet type could not be determined.

PN/SN Each Port Network and Switch Node located in the cabinet is

identified by its PN number or its SN number and PNC

designation (A or B).

Connectivity

Status

For PNs connectivity status refers to the availability of the

Expansion Archangel Link (EAL) and Indirect Neighbor Link (INL)

to the carrier for both active and standby PNCs (if duplicated).

Possible values are:

upEAL and INL are both available.

downEAL and INL are both unavailable.

near-endThe EAL is available and the INL is unavailable.

far-endThe INL is available and the EAL is unavailable.

blankIn the standby column, this means PNC is not

duplicated.

For SNs connectivity status indicates circuit pack insertion on the

Switch Node as follows:

upAt least one switch node interface circuit pack in the

Switch Node is inserted.

downThere are no switch node interface circuit packs

inserted on the Switch Node.

blankIn the active column, this indicates that the Switch Node

carrier is currently the standby in a critical reliability system.

In the standby column, this indicates that the Switch Node

carrier is currently active (whether or not PNC is duplicated).

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-200status bri-port

The following display shows a typical result when status cabinet 1is entered.

Emergency

Transfer The location of the circuit pack containing the emergency transfer

select switch (EPN maintenance or SYSAM). In PPN cabinets with

duplicated SPEs, there are two such circuit packs. In this case, if

the standby Emergency Transfer Select switch is changed while

handshake is down, switch setting displayed will be incorrect

until handshake comes back up.

Select

Switch The current setting of the emergency transfer switch:

on Emergency transfer has been manually activated.

off Emergency transfer is being manually prevented.

auto+ The cabinet is controlling emergency transfer and it is

currently activated.

auto- The cabinet is controlling emergency transfer it is not

currently activated.

unavail The current setting of the emergency transfer switch

is not available.

PN/SN Each Port Network and Switch Node located in the cabinet is

identified by its PN number or its SN number and PNC

designation (A or B).

Mj, Mn, Wn The number of major, minor and warning alarms currently logged

against the Port Network or Switch Node.

status cabinet 1

CABINET CONFIGURATION STATUS CABINET CONNECTIVITY STATUS

Carrier PN/SN Carrier Cabinet PN/SN Connectivity Status

Location Number Type Type Active Standby

01A PN 1 processor MCC PN 1 up up

01B PN 1 processor SN 1 B-PNC up

01C PN 1 port SN 1 A-PNC up

01D SN 1 dup-sw-node

01E SN 1 switch-node

CABINET EMERGENCY TRANSFER CABINET ALARM STATUS

Emergency Select PN/SN Mj Mn Wn

Transfer Switch PN 1 0 2 1

01A off SN 1 B-PNC 0 0 0

01B off SN 1 A-PNC 0 0 0

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-201status cdr-link

status cdr-link

status cdr-link [print]

The status cdr-link command displays the status of the call detail recording

(CDR) links. If a link is down, the report includes the number of times the switch

has tried to re-establish the link.

The CDR link is the physical link that the SPE uses to send call detail records to

an output device such as a Call Detail Recording Utility (CDRU). CDR links use

System Ports which are described in the PDATA-PT section of Chapter 9. A

system may have up to two CDR links, a primary and a secondary. See PRI-CDR

in Chapter 9.

Output

The following information is displayed for both the Primary and Secondary CDR

links, whether or not both are used.

The following is an example of the fields contained on the output form.

Link State The operational status of the link as follows:

up The link is established and is capable of supporting the

application. This is the normal operational state.

down The link is physically down.

extension not administered An extension number for

the output device has not been assigned on the CDR system

parameters form.

Number of

Retries The number of times the switch has tried to set up the link.

Maintenance

Busy Whether the link is busied out for testing.

status cdr-link SPE A

CDR LINK STATUS

Primary Secondary

Links state: up extension not administered

Maintenance Busy? no

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-202status cleared-alarm-notif

status cleared-alarm-notif

This command returns the status of Cleared Alarm Notification.

Synopsis

status cleared-alarm-notif [1 | 2]

Examples

status cleared-alarm-notif

status cleared-alarm-notif 1

status cleared alarm-notif 2

Description

This command is intended to be used by Expert System to detect a chronic

alarming condition. If this command returns Feature is suspended, Expert

System can then identify an open trouble ticket as a chronic problem for special

considerations.

Defaults

The test defaults to return the status of Cleared Alarm Notification of the first OSS

telephone number.

Parameter

Help Messages

[‘1’ or ‘2’]

1This option returns the status of Cleared Alarm Notification of the first OSS

telephone number.

2This option returns the status of Cleared Alarm Notification of the second

OSS telephone number.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-203status conference

Output

The command returns one of the following messages:

1. If Cleared Alarm Notification is enabled and has not been suspended:

Feature is enabled

2. If Cleared Alarm Notification is disabled:

Feature is disabled

3. If Cleared Alarm Notification is enabled and has been suspended:

Feature is suspended

Feature Interactions

None.

status conference

This command is a troubleshooting aid to help identify problems with a

multimedia conference and can help solve more complex problems.

Synopsis

The first screen appears when status conference is entered and at least 1 valid

conference is found.

Permissions

The following default logins may execute this command: system technician,

inads, init.

Examples

status conference

status conference 2 print

status conference [all \ conference-ID] [print \ schedule]

status conference [all \ conference-ID] [endpoint \ endpoint id]

(see ‘‘Field Descriptions (status conference endpoint)’’ on page 8-218)

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-204status conference

Description

Use the status conference command to solve the following multimedia

problems:

1. A user unable to join or remain joined to a conference.

2. A conference having poor video quality due to it being downgraded

because of the automatic algorithms - audio AUTO mode and the Px64

video picture specifications.

3. A user not receiving full service, such as being an audio-only endpoint (no

video).

4. An audio add-on user unable to join or remain joined to a conference.

5. A conferee not being seen by other users due to interworking problems.

6. A user not able to participate in the Muiltpoint Communications Service

conference.

7. A continuous conference not switching endpoints in or out of quadrants.

Defaults

The default for the conference-ID is all (all stored data).

Parameters

Feature Interactions

None.

Output

Depending on the command entered, it is possible to have many records

display. Active conferences display first (in order of conference-ID), followed by

completed conferences (most recently completed first). There is no data or

information about conferences not yet begun.

The data for each conference displays in 2 parts: the first screen describes the

status of the conference and indicates the modes and levels of the conference. It

also shows certain endpoint information such as which endpoints are in use and

which endpoint caused the conference operating mode to change. This screen

status conference Displays all stored conference data.

status conference 2 print Displays data on conference 2 (current or last

completed), and sends it to the SAT printer.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-205status conference

is similar to the administration screens. The remainder of the screens display

endpoint level data (up to 8 endpoints per screen), displaying the ports and drop

reasons.

Screen 8-1 shows page 1 of a typical administration screen. The first screen

appears when status conference is entered and at least 1 valid conference is

found.

Screen 8-1. status conference: page 1 of 2

Field Descriptions (status conference, page 1)

status The current status of the conference - active, in-use, complete

conference

name Always set as MMCH DYNAMIC

conference

mode Always set as voice-activated

password Not Applicable

password

scope Not Applicable

cascade mode Conference cascade mode - blank

audio mode The current operating audio mode - G.711-A, G.711-mu, G.728.

G.722

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-206status conference

class The type of conference - dedicated

data mode Data mode capability for this conference - none, any-mlp, ww-pcs

MLP rate MLP Data Rate for this conference - blank.

start

time/date Conference start time in 24-hour notation with month and day.

stop

time/date End of conference in 24-hour notation with month and day. It is the

actual end time if Status is complete; otherwise it is blank.

admin

bandwidth The channel bandwidth as administered on the Conference Record

form - 64k.

no of

channels The number of channels (transfer rate) required for each Px64 endpoint

- 2.

Chair Identifies the current chair token holder. This field is always blank.

conf

bandwidth The current operating channel conference bandwidth. This can be

different from the administered bandwidth because of Rate Adaptation.

Rate

adaptation Does this conference support Rate Adaptation? - n, y.

Format

(in/out) For single-screen conference, the video format of the conference, CIF,

QCIF, QCIF/CIF, H.CTS, H.CTX+, and SG4. For conferences

other than H.261, the input and output formats are always symmetric

and the mode is the same for input and output. These display as

H.CTX, H.CTX+, and SG4. For H.261 mode non-continuous presence

conferences, the format is always symmetric and displays as CIF and

QCIF. The same is true for the non-presentation, continuous presence

conference in single-screen. For presentation mode H.261 single

screen continuous presence capable conferences, the input and

output formats may be symmetric QCIF/CIF (displayed as CIF) or

asymmetric QCIF/CIF, depending on if the format is administered as

upgradeable. For quad-screen conferences, the format is QCIF/CIF to

reflect the input of QCIF from all participants and output of CIF to all

participants. For presentation mode quad-screen conference, the

format is also QCIF/CIF to reflect the input/output of all participants

except the presenter. In quad-screen mode, the input from the

presenter is always CIF.

FPS The CIF frame rate (frames per second) - ‘-‘, 30, 15, 10, 7.5. FPS

indicates the rate that an endpoint is capable of receiving frames. Note

that there is no indication of the maximum transmit frame rate nor the

current frame rate that the MCU can detect. The frame rate changes as

a function of the amount of motion in the input image.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-207status conference

QFPS The ACIF frame rate (frames per second) - ‘ - ‘, 30, 15, 10, 7.5. QFPS

indicates the rate that an endpoint is capable of generating/receiving

frames.

For quad-screen VAS conferences, QFPS reflects the highest common

QCIF frame rate of all endpoints and the rate of the video mixer board,

which may be lower than the rest of the participants. Note that QCIF

calculation takes into account the highest common CIF frame rate

declared by all conference participants, since QCIF rate cannot be

greater than that of the highest common CIF rate.

For quad-screen presentation conferences, QFPS reflects the highest

common QCIF frame rate of all participants and the rate of the video

mixer board. Note that the QFPS cannot be greater than the CIF frame

rate announced by the presenter.

QFPS field is blank for proprietary modes.

lo/hi

interworking Does this conference support Low Speed/High Speed Interworking? -

This field will always have a value of n.

Type The type of conferee, either Audio/Video (P64), Audio Add-on (AUD),

Cascade Link (CAS), BONDing Call (BOND), BONDing Cascade Link

(BCAS), UCC Controller (UCC), or Dedicated Access (DA). BONDing

calls use up to 12 channels to form a single multimedia pipe.

Ext Endpoint extension chosen at administration. This field is blank.

Meet-me

number The Meet-Me Number administered for the Meet-Me Extension. This

field is blank.

Dial Type Indicates whether dial-in or dial-out is used to join the endpoint to the

conference - in, out. The value in is for dial-in, and out is for dial-out.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-208status conference

In Use Is the endpoint currently participating in the conference or in process of

connecting to the conference? - y, c, e, f, n, blank.

y means that the endpoint is in use and is fully connected on all media

in an active conference.

c means that the endpoint is in use and is fully connected, however the

endpoint has changed the conference audio or video capability or has

changed the rate of the conference because of rate adaptation. This

condition requires analysis of this endpoint’s capabilities and mode

fields to identify which capability was reduced.

e means that the endpoint is in use but the endpoint had capability

problems. The endpoint does not have one of the required capabilities

(Vid, Bhl, MLP) to be a full participant. For MLP capabilities, see the

“T120” field. This condition requires analysis of this endpoint’s

capabilities and mode field to identify the missing capability.

f means that the endpoint is in use but is not connected to all media.

This indicates that the endpoint has declared all the required

capabilities (channel/video/ audio/data) but is not fully connected to all

conference media at this time. This endpoint may be in the process of

connecting, has failed to connect, or is not a valid video source. This

condition requires analysis of this endpoint’s capabilities and mode

fields to identify the problem.

n means that the endpoint was connected in a conference but has/was

disconnected or attempted to connect to a conference but was

unsuccessful.

blank means the field is blank until the first call is made from/to the

endpoint.

Chl Data on the quantify and quality of channels (transfer rate)? - y, e, n,

blank

y the endpoint has the required number of channels.

e means that the endpoint has not declared support for the correct

number of channels and cannot participate fully in the conference.

n means that the endpoint has declared the correct number of

channels, but all the channels have not yet joined the conference, due

to either a network or endpoint problem.

blank Audio add-on endpoints always have the Chl field set to blank.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-209status conference

Aud Does it have the required audio capability? - y, c, e, blank

y the endpoint has the required audio capability. Audio add-on

endpoint always have the Aud field set to y once the endpoint has

joined the conference.

c this endpoint is PCM only and it changed the video quality of the

conference by changing the operating audio from G.728 to G.711. If

the administered audio mode is auto and the administered bandwidth

is 112 kbps (56 k/channel) or 128 kbps (64 k/channel), the system

starts out with the highest common audio of G.728. When the

administered bandwidth is greater than 128 kbps, the system starts out

with the highest common bandwidth of 7 kHz.

e A PCM-only endpoint that did not have the capability of supporting

the administered audio mode of G.728 (such as a data conference), or

G. 278/G.711 endpoint that did not have the capability of supporting

the administered audio mode of 7 kHz. Such endpoints operate with

PCM audio and interwork with the current operating audio mode.

blank the field is blank until the first call is made from/to the endpoint.

Vid Does it have the required video capability and is receiving video? - y, c,

e, n, blank

y the endpoint has the required video capability and should be

receiving video if the Chl, Aud, and Dat fields are y.

c means it downgraded the conference’s video quality - either from CIF

to ACIF or by decreasing the frame rate. The conference video mode is

set by default to CIF and if a QCIF-only endpoint joins the conference,

then the entire conference is made to operate in QCIF, with the video

clarity downgraded. Also, the conference frame rate is initially set to the

highest frame rate that can then be reduced by any endpoint. If the

conference video mode is not administered with upgrade capability,

then if the video parameters for a conference have been

“downgraded,” they are not “upgraded” until all endpoints disconnect

from the conference.

e means that the endpoint has not declared any video capability in its

cap-set.

n means audio only, not receiving video, possibly due to an audio or

data problem.

blank Audio add-on endpoint always have the Vid field set to blank.

Mlp The state of the Control Link to the ESM (T.120 stack terminator), the

endpoint MLP data capability, and the state of the data connection in

the T.120 stack. This field value is always blank, indicating that the

Data Mode for the conference is none, and therefore, the data does not

apply, or the endpoint has never joined the conference.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-210status conference

Gx Does it have the Still Frame Graphics capability? - y, e, blank

y This endpoint has this capability.

e This endpoint did not declare this capability. The conference retains

the still frame graphics capability when a non-compliant endpoint joins

the conference.

blank This endpoint has never joined the conference.

Rate Adpt Rate adaptation/Interworking indicator - 5, 6, y, c, e, n, blank. Values

of 5 and 6 apply only to Low Speed/High Speed Interworking. All other

values apply only to Rate Adaptation.

5 A 56-kbps (Low Speed) endpoint has joined a High Speed (128 kbps

or above) conference. This endpoint is connected with audio only

capability but is not a valid video source and destination.

6 A 64-kbps (Low Speed) endpoint has joined a High Speed (128 kbps

or above) conference. This endpoint is connected with audio only

capability but is not a valid video source and destination.

y This endpoint has joined the conference at the administered rate of

64 kbps, but because rate adaptation to 56 kbps was triggered by

another endpoint, this endpoint has successfully rate adapted to 56

kbps.

c The administered bandwidth of the conference is 64 kbps and this

endpoint has joined the conference at 56 kbps. The first 56 kbps

endpoint that joins 64 kbps rate adaptable conference triggers rate

adaptation (see Join Time below).

n A 64-kbps conference was triggered to rate adapt to 56 kbps by

some other endpoint. This endpoint joined the conference at the

bandwidth of 64 kbps, but encountered problems in rate adapting

down to 56 kbps. This endpoint may have the audio and may be

receiving video, but is not a valid video source.

blank Rate adaptation was never triggered by any endpoint, and if this

endpoint is in use and connected, then it has joined the conference at

the administered bandwidth.

Bond Mode BONDing Mode - blank. This field is blank for calls that are not related

to bonding.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-211status conference

Ts Indication of the talking state of the endpoint - t, m, M, S, blank.

t At the time the command was invoked, voice energy (talking) was

detected from the endpoint.

m At the time the command was invoked, the endpoint indicated to the

MCU that it was muted. It is possible that an endpoint may mute, but

not send any indication to the MCU. In this situation the MCU does not

display a mute indication.

M At the time the command was invoked, the endpoint’s audio was

muted via UDD/CRCS Agent interface. M displays when both the

endpoint and the UCC/CRCS Agent have muted the endpoint audio.

S At the time the command was invoked, the endpoint’s audio was

muted because of solo-audio state set by UCC/CRCS Agent. While in

solo-audio state, new endpoints joining the conference are

automatically muted.

blank At the time the command was invoked voice energy (talking)

was not being detected from the endpoint.

Vs Indication of the MCU video state for this endpoint - a, b, B, c, i, r, R, s,

S, u, U, v, blank.

For quad-screen conferences an * is affixed before the value of Vs to

indicate that an endpoint is currently part of the mixed image. A # may

be affixed before the value of Vs to indicate that an endpoint was fixed

to be in the mixed image (via administration or UCC/CRCS Agent), but

instead, a Fill video is shown in its place. This occurs when the video

of an endpoint that is fixed in a quadrant cannot be used as a video

source because the endpoint is currently not joined to the conference,

has suppressed its video, or has invalid video to be the video source.

Notice that at most four endpoints have an * or # affixed before the Vs

field value.

For quad-screen conference in VAS mode, the mixed image is

broadcast to all endpoints. For quad-screen conference in presentation

mode, the mixed image is return video to the presenter.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-212status conference

(cont’d.)

a This value applies only to quad-screen conferences. *a indicates that

an endpoint is part of the current mixed image and is fixed in one of the

quadrants via administration. A value of *a indicates that the endpoint

is fixed in a quadrant but is not currently connected (Fill image

displays).

b For full-screen conference it indicates that at the time the command

was invoked, this endpoint’s video was being broadcast to other sites.

This conference was in VAS, broadcast, or presentation mode. For

quad-screen VAS conference it is prefixed with an asterisk (*) and

indicates that this endpoint’s video is part of the mixed image because

of VAS. For quad-screen presentation conferences, b (without an

asterisk) identifies the presenter as the broadcaster.

B At the time the command was invoked the endpoint’s video was

being broadcast to other sites because of the UCC roll call feature.

UCC roll call feature can only be performed in full-screen mode.

c At the time the command was invoked this endpoint’s video was

being broadcast to other sites. The conference was in chair mode and

the broadcaster was designated by the chair. Chair features can only

be performed in full-screen mode.

i At the time the command was invoked the endpoint was not a valid

video source. For continuous presence conference, if this endpoint is

fixed in a particular quadrant, an asterisk (#) is affixed before i.

r For full-screen conferences, at the time the command was invoked

the endpoint’s video was the return video to the broadcaster. For

continuous presence conference in presentation mode, *r represents a

VAS quadrant that is part of the mixed image.

R At the time the command was invoked, the endpoint’s video was the

return video to the broadcaster because of the UCC browse feature.

UCC Browse feature can only be performed in full-screen mode.

s At the time the command was invoked this endpoint’s video was

suppressed at the request of the endpoint. For continuous presence

conference with fixed quadrant participants, if this endpoint is fixed in a

particular quadrant a # is affixed before s.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-213status conference

(cont’d)

S At the time the command was invoked this endpoint’s video was

suppressed via UCC/CRCS Agent interface. For continuous presence

conference with fixed quadrant participants, if this endpoint is fixed in a

particular quadrant, # is affixed before S. S displays when both the

endpoint and the UCC/CRCS Agent have suppressed the endpoint

video.

u For full-screen conferences, at the time the command was invoked

this endpoint’s video was being broadcast to other sites. The

conference was in VAS mode and the broadcaster was designated by

the UCC/CRSCS Agent interface. For quad-screen conferences, it

indicates that UCC/CRCS Agent designated this endpoint as fixed in a

quadrant. An asterisk (*) is affixed before u if the endpoint is currently

part of the quad image, and # is affixed if the endpoint is not currently

joined.

U Applies only to quad-screen conference and indicates that

UCC/CRCS Agent designated a quadrant as VAS. An asterisk (*) is

affixed before U to indicate that this endpoint is part of the current quad

image.

v At the time the command was invoked this endpoint’s video was

being broadcast to other sites. The conference was in VAS mode but

the endpoint has asked to be a broadcaster via “See-Me” request and

was granted a MCV (Multipoint Command Visualize) token. The See-Me

feature is only performed in full-screen mode.

blank At the time of the request the endpoint’s video was not

broadcast, return, video, or part of the mixed-image, but it is a valid

video source.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-214status conference

Screen 8-2. status conference: page 2 of 2

Field Descriptions (status conference, page 2)

Sum Grp The VD audio Level 1 (L1) and Level 2 (L2) summer group parts for

each assigned group (1-4). Summer parts are assigned only for

conferences with over 6 participants. When a conference operates at an

audio mode of 7 kHz (administered audio mode is 7 kHz, or auto with

the bandwidth greater than 128 kbps), the system allocates “primary”

and “secondary” L1 and L2 summer parts. These primary and

secondary parts are allocated as adjacent port slots on the same board.

Status conference only displays the primary summer ports. The

secondary summer ports are always one slot higher than the displayed

primary summer port.

Join Time Time (in 24-hour notation) when the channel joined the conference.

Drop Time Time (in 24-hour notation) when the channel disconnected. If the first

channel has a drop time, then it means that the endpoint is not in use. If

there is a drop time without a join time, it means that the call

disconnected without being joined to the conference.

status conference page 2 of 2

STATUS OF CONFERENCE:

Sum Grp: Group1 Group2 Group3 Group 4

L1:

L2:

Join Drop Drop AC --------Ports--------- Sum

Ext Time Time Reason Num Trunk Video Aud/Esm Grp Software

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-215status conference

Drop Reason The reason for the channel’s disconnect:

2-pri This drop reason occurs when an administration error causes a

mismatch in primary-secondary designation for a cascade link. This

mismatch shows that both MCUs are administered as primaries (see

“Cascading” for a description of primary-secondary compatibility).

2-sec This drop reason occurs when an administration error causes a

mismatch in primary-secondary designation for a cascade link. This

mismatch shows that both MCUs are administered as secondaries (see

“Cascading” for a description of primary-secondary compatibility).

Agent The reservation agent has caused the call to disconnect (for

example, the agent has changed a connected dial-out destination

number).

Bandwidth mismatch between a call and the conference it attempted

to join. For example, a 56-kbps call attempted to join a 64-kbps

conference that does not allow rate adaptation.

BondHshake BONDing handshake drop reason can be caused due to

the following reasons: information channel parameter not supported or

invalid, parameter negotiation terminated out of sequence, timer

expired because of the secondary channels did not establish, or

BONDing framing was not detected for one of the other channels.

Busy This dial-out drop reason occurs when the MCU detects that the

conferee’s terminal equipment is busy. This drop reason is detected by

an ISDN cause value (for example h0). See “Dial-out” for a description

of CPTR usage.

Chair disconnected the endpoint, using either Chair Command

Disconnect (CCD) or Chair Command Kill (CCK) signals.

Conf End The conference was ended due to reaching stop time for a

reserved conference or due to an active conference being converted to

file.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-216status conference

Drop Reason

(cont’d)

Endpoint Clearing received from DS1 - the disconnect came from the

endpoint. The endpoint notified the MCU that it intended to disconnect.

Far-end Clearing received from DS1 - the disconnect came from either

the network or the endpoint.

Handshake Either framing was never found (the endpoint could not

complete initialization - problems finding Frame Alignment Signal (FAS),

Multi Frame Alignment (MFA) and getting a corrected coded cap-set) or

framing was lost for some time (over 40 seconds) and the endpoint was

disconnected.

IDtimeout The MCU has not received response to the UIN/password

Query from the H.320 user after three attempts. Each attempt has a

system administered timeout period.

Internal MCU has a problem allocating trunk resources necessary to

route the dial-out call for the specified dial-numbers. This problem can

be associated with routing pattern or trunk associated translation (for

example, TAC specified in the dial-out number or routing pattern points

to a trunk group without members), or it can indicate a lack of trunk

resources (for example, all trunk members are maintenance busy or all

in-service members are busy on a call).

Network Clearing received from DS1 - the disconnect came from the

network. The endpoint that had the disconnect notification capability

disconnected without notifying the MCU.

Not-MCU The dial-out destination number(s) of the “CAS” extension has

terminated to a number that is not a dial-in cascade MCU extension.

No-ring This dial-out drop reason occurs when the call has been up

for 30 seconds and no ringing is detected.

Reorder This dial-out drop reason occurs when the MCU detects that

there are no available trunks in the network to place the call. This drop

reason is detected by MCU CPTR resources. See “Dial-out” for a

description of CPTR usage.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-217status conference

Drop Reason

(cont’d)

Pre-AnsDrop The call disconnected before answer by an endpoint.

The cause of the disconnect may be the network, an endpoint, or a

terminal adapter. This drop reason is different from ‘No-answer,’ which

indicates that a 60-second timeout occurred while alerting. In this case,

the call drops before the 60-second timer has expired. Some busy

endpoints connected through terminal adapters display this behavior.

Resource MCU could not provide resources (VC or MMI) when the call

arrived or lost the resources during the call. This could be due to them

being Out of Service, busied out by craft, or being used by system

maintenance. This drop reason could also occur if the DS1/MMI cable is

disconnected. If there was a resource problem when the call arrived, it

would get reorder (fast busy) and not get disconnected by the MCU.

Password Either the user entered the wrong password or the audio

add-on user did not enter it within the specified time period. Note that

the audio add-on user gets one attempt to enter a correct password and

inter-digit timing for each digit (that is, about 10 seconds between

digits).

System An MCU restart (level 2) disconnected all calls.

UIN-Inv The user entered an invalid User Identification Number.

Unknown The system could not determine the cause of the disconnect.

Wrong-num This dial-out drop reason occurs when the MCU detects

the wrong destination number was dialed. This drop reason is detected

by MCU CPTR resources SDN cause value. See “Dial-out” for details.

UCC controller intentionally disconnected the endpoint.

AC Num Administered Connection Number - from 1 to 128. AC number can be

used to further diagnose a problem by combining status conference

information with the status administered connection command and

data stored in the error and alarm logs.

Ports Trunk The data endpoint that the channel is using.

Ports Video The MMI port for the channel.

Ports Aud If the endpoint type is not “UCC,” the VC audio encoder port (which is

always paired to a decoder port) for the channel (only the first channel).

Because only one audio encoder port is allocated per endpoint, it

appears together with the ESM data port in the endpoint’s channel 1

port slot position of the Port Aud/ESM column. For “UCC” endpoint

type, the channel 1 port slot position displays the allocated Call

Classifier resource.

Ports ESM The Expansion Service Module MMI data port. This field is always blank.

Sum Grp Endpoint’s assigned summer group number. The summer group port

assignments are on screen 1.

software For Lucent Technologies use only.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-218status conference

Field Descriptions (status conference endpoint)

status conference

endpoint

The first screen appears when status conference

endpoint

is entered and

the specified conference is found. Data relevant for each endpoint displays in 6

pages. If the endpoint-ID of all is used, all possible endpoints associated with

the specified conference display.

Page 1 - Status Conference Endpoint

Screen 8-3. Page 1 of 6: status conference x endpoint y

Endpoint Endpoint-ID is a slot number associated with the endpoint entered on

the conference forms.

Product Product identification number obtained from the endpoint.

Manufacturer/

Country Manufacturer identification number and manufacturer’s country code

obtained from the endpoint.

Terminal Name This field is always blank.

Sum Grp Summer group number to which this endpoint belongs and the VC

Audio Level (L1) and Level 2 (L2) summer ports for this group. These

fields have an entry only for conferences with over 6 participants.

Dial Out #1

Dial Out #2 Blank

Blank

status conference endpoint page 1 of 6

STATUS OF CONFERENCE ___ ENDPOINT: __ Status: ________

Ext: _____ Type: ____ Manufacturer/Country: ____/____ Product: _____

Terminal Name: _______________ Data Mode: _________ MLP Rate: ____

Admin Bandwidth: ____ Rate Adaptation: _

Conf Bandwidth: ____ Lo/Hi Interworking: _

Meet-Me Number: ____________________ Dial Out #1: _______________________

Sum Grp: _ L1: ______ L2: ______ #2: _______________________

Quadrature: ______ ________

ENDPOINT STATES/CAPABILITIES/MODES

In Enh ----Capability---- Rate Bond

Use BAS Chl Aud Vid Mlp Gx Adpt Mode Ts Vs

- - - - - - - - - - -

Help line

enter command:

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-219status conference

In Use Is the endpoint currently participating in the conference or in process

of connecting to the conference? - y, c, e, f, n, blank.

y means that the endpoint is in use and is fully connected on all

media in an active conference.

c means that the endpoint is in use and is fully connected, however

the endpoint has changed the conference audio or video capability

or has changed the rate of the conference because of rate

adaptation. This condition requires analysis of this endpoint’s

capabilities and mode fields to identify which capability was reduced.

e means that the endpoint is in use but the endpoint had capability

problems. The endpoint does not have one of the required

capabilities (Vid, Bhl, MLP) to be a full participant. For MLP

capabilities, see the “T120” field. This condition requires analysis of

this endpoint’s capabilities and mode field to identify the missing

capability.

f means that the endpoint is in use but is not connected to all media.

This indicates that the endpoint has declared all the required

capabilities (channel/video/ audio/data) but is not fully connected to

all conference media at this time. This endpoint may be in the

process of connecting, has failed to connect, or is not a valid video

source. This condition requires analysis of this endpoint’s capabilities

and mode fields to identify the problem.

n means that the endpoint was connected in a conference but

has/was disconnected or attempted to connect to a conference but

was unsuccessful.

blank means the field is blank until the first call is made from/to the

endpoint.

Enh BAS EnhancedBasic Service Flag - n, y

y means that the endpoint supports the enhanced BAS

commands/caps;

n means that the endpoint only supports the basic BAS

commands/caps.

Chl Data on the quantify and quality of channels (transfer rate)? - y, e, n,

blank

y the endpoint has the required number of channels.

e means that the endpoint has not declared support for the correct

number of channels and cannot participate fully in the conference.

n means that the endpoint has declared the correct number of

channels, but all the channels have not yet joined the conference,

due to either a network or endpoint problem.

blank Audio add-on endpoints always have the Chl field set to

blank.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-220status conference

Aud Does it have the required audio capability? - y, c, e, blank

y the endpoint has the required audio capability. Audio add-on

endpoint always have the Aud field set to y once the endpoint has

joined the conference.

c this endpoint is PCM only and it changed the video quality of the

conference by changing the operating audio from G.728 to G.711. If

the administered audio mode is auto and the administered bandwidth

is 112 kbps (56 k/channel) or 128 kbps (64 k/channel), the system

starts out with the highest common audio of G.728. When the

administered bandwidth is greater than 128 kbps, the system starts

out with the highest common bandwidth of 7 kHz.

e A PCM-only endpoint that did not have the capability of supporting

the administered audio mode of G.728 (such as a data conference),

or G. 278/G.711 endpoint that did not have the capability of

supporting the administered audio mode of 7 kHz. Such endpoints

operate with PCM audio and interwork with the current operating

audio mode.

blank the field is blank until the first call is made from/to the

endpoint.

Vid Does it have the required video capability and is receiving video? - y,

c, e, n, blank

y the endpoint has the required video capability and should be

receiving video if the Chl, Aud, and Dat fields are y.

c means it downgraded the conference’s video quality - either from

CIF to ACIF or by decreasing the frame rate. The conference video

mode is set by default to CIF and if a QCIF-only endpoint joins the

conference, then the entire conference is made to operate in QCIF,

with the video clarity downgraded. Also, the conference frame rate is

initially set to the highest frame rate that can then be reduced by any

endpoint. If the conference video mode is not administered with

upgrade capability, then if the video parameters for a conference

have been “downgraded,” they are not “upgraded” until all endpoints

disconnect from the conference.

e means that the endpoint has not declared any video capability in its

cap-set.

n means audio only, not receiving video, possibly due to an audio or

data problem.

blank Audio add-on endpoint always have the Vid field set to

blank.

Mlp The state of the Control Link to the ESM (T.120 stack terminator), the

endpoint MLP data capability, and the state of the data connection in

the T.120 stack. This field value is always blank, indicating that the

Data Mode for the conference is none, and therefore, the data does

not apply, or the endpoint has never joined the conference.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-221status conference

Gx Does it have the Still Frame Graphics capability? - y, e, blank

y This endpoint has this capability.

e This endpoint did not declare this capability. The conference

retains the still frame graphics capability when a non-compliant

endpoint joins the conference.

blank This endpoint has never joined the conference.

Rate Adpt Rate adaptation/Interworking indicator - 5, 6, y, c, e, n, blank.

Values of 5 and 6 apply only to Low Speed/High Speed Interworking.

All other values apply only to Rate Adaptation.

5 A 56-kbps (Low Speed) endpoint has joined a High Speed (128

kbps or above) conference. This endpoint is connected with audio

only capability but is not a valid video source and destination.

6 A 64-kbps (Low Speed) endpoint has joined a High Speed (128

kbps or above) conference. This endpoint is connected with audio

only capability but is not a valid video source and destination.

y This endpoint has joined the conference at the administered rate of

64 kbps, but because rate adaptation to 56 kbps was triggered by

another endpoint, this endpoint has successfully rate adapted to 56

kbps.

c The administered bandwidth of the conference is 64 kbps and this

endpoint has joined the conference at 56 kbps. The first 56 kbps

endpoint that joins 64 kbps rate adaptable conference triggers rate

adaptation (see Join Time below).

n A 64-kbps conference was triggered to rate adapt to 56 kbps by

some other endpoint. This endpoint joined the conference at the

bandwidth of 64 kbps, but encountered problems in rate adapting

down to 56 kbps. This endpoint may have the audio and may be

receiving video, but is not a valid video source.

blank Rate adaptation was never triggered by any endpoint, and if

this endpoint is in use and connected, then it has joined the

conference at the administered bandwidth.

Bond Mode BONDing Mode - blank. This field is blank for calls that are not related

to bonding.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-222status conference

Ts Indication of the talking state of the endpoint - t, m, M, S, blank.

t At the time the command was invoked, voice energy (talking) was

detected from the endpoint.

m At the time the command was invoked, the endpoint indicated to

the MCU that it was muted. It is possible that an endpoint may mute,

but not send any indication to the MCU. In this situation the MCU

does not display a mute indication.

M At the time the command was invoked, the endpoint’s audio was

muted via UDD/CRCS Agent interface. M displays when both the

endpoint and the UCC/CRCS Agent have muted the endpoint audio.

S At the time the command was invoked, the endpoint’s audio was

muted because of solo-audio state set by UCC/CRCS Agent. While in

solo-audio state, new endpoints joining the conference are

automatically muted.

blank At the time the command was invoked voice energy (talking)

was not being detected from the endpoint.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-223status conference

Vs Indication of the MCU video state for this endpoint - a, b, B, c, i, r, R,

s, S, u, U, v, blank.

For quad-screen conferences an * is affixed before the value of Vs to

indicate that an endpoint is currently part of the mixed image. A #

may be affixed before the value of Vs to indicate that an endpoint was

fixed to be in the mixed image (via administration or UCC/CRCS

Agent), but instead, a Fill video is shown in its place. This occurs

when the video of an endpoint that is fixed in a quadrant cannot be

used as a video source because the endpoint is currently not joined

to the conference, has suppressed its video, or has invalid video to

be the video source. Notice that at most four endpoints have an * or

# affixed before the Vs field value.

For quad-screen conference in VAS mode, the mixed image is

broadcast to all endpoints. For quad-screen conference in

presentation mode, the mixed image is return video to the presenter.

a This value applies only to quad-screen conferences. *a indicates

that an endpoint is part of the current mixed image and is fixed in one

of the quadrants via administration. A value of *a indicates that the

endpoint is fixed in a quadrant but is not currently connected (Fill

image displays).

b For full-screen conference it indicates that at the time the command

was invoked, this endpoint’s video was being broadcast to other

sites. This conference was in VAS, broadcast, or presentation mode.

For quad-screen VAS conference it is prefixed with an asterisk (*) and

indicates that this endpoint’s video is part of the mixed image

because of VAS. For quad-screen presentation conferences, b

(without an asterisk) identifies the presenter as the broadcaster.

B At the time the command was invoked the endpoint’s video was

being broadcast to other sites because of the UCC roll call feature.

UCC roll call feature can only be performed in full-screen mode.

c At the time the command was invoked this endpoint’s video was

being broadcast to other sites. The conference was in chair mode

and the broadcaster was designated by the chair. Chair features can

only be performed in full-screen mode.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-224status conference

Page 2 - Endpoint Channel Information

This section only describes the fields that are specific to the endpoint-level

command output.

(cont’d.)

i At the time the command was invoked the endpoint was not a valid

video source. For continuous presence conference, if this endpoint is

fixed in a particular quadrant, an asterisk (#) is affixed before i.

r For full-screen conferences, at the time the command was invoked

the endpoint’s video was the return video to the broadcaster. For

continuous presence conference in presentation mode, *r represents

a VAS quadrant that is part of the mixed image.

R At the time the command was invoked, the endpoint’s video was

the return video to the broadcaster because of the UCC browse

feature. UCC Browse feature can only be performed in full-screen

mode.

s At the time the command was invoked this endpoint’s video was

suppressed at the request of the endpoint. For continuous presence

conference with fixed quadrant participants, if this endpoint is fixed in

a particular quadrant a # is affixed before s.

S At the time the command was invoked this endpoint’s video was

suppressed via UCC/CRCS Agent interface. For continuous

presence conference with fixed quadrant participants, if this endpoint

is fixed in a particular quadrant, # is affixed before S. S displays when

both the endpoint and the UCC/CRCS Agent have suppressed the

endpoint video.

u For full-screen conferences, at the time the command was invoked

this endpoint’s video was being broadcast to other sites. The

conference was in VAS mode and the broadcaster was designated

by the UCC/CRSCS Agent interface. For quad-screen conferences, it

indicates that UCC/CRCS Agent designated this endpoint as fixed in

a quadrant. An asterisk (*) is affixed before u if the endpoint is

currently part of the quad image, and # is affixed if the endpoint is not

currently joined.

U Applies only to quad-screen conference and indicates that

UCC/CRCS Agent designated a quadrant as VAS. An asterisk (*) is

affixed before U to indicate that this endpoint is part of the current

quad image.

v At the time the command was invoked this endpoint’s video was

being broadcast to other sites. The conference was in VAS mode but

the endpoint has asked to be a broadcaster via “See-Me” request

and was granted a MCV (Multipoint Command Visualize) token. The

See-Me feature is only performed in full-screen mode.

blank At the time of the request the endpoint’s video was not

broadcast, return, video, or part of the mixed-image, but it is a valid

video source.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-225status conference

Screen 8-4. Page 2 of 6: status conference x endpoint y

Join Time Time (in 24-hour notation) when the channel joined the conference.

Drop Time Time (in 24-hour notation) when the channel disconnected. If the first

channel has a drop time, then it means that the endpoint is not in use.

If there is a drop time without a join time, it means that the call

disconnected without being joined to the conference.

status conference endpoint page 2 of 6

ENDPOINT CHANNEL INFORMATION

Chan. Join Drop ----Drop---- AC ------------Ports---------- Fr

No. Time Time Reason Code Num Trunk Video Aud/ESM BONDng Err Software

1: _____ _____ _________ __ ___ ______ ______ ______ ______ ___ ________

2: _____ _____ _________ __ ___ ______ ______ ______ ______ ___ ________

3: _____ _____ _________ __ ___ ______ ______ ______ ___ ________

4: _____ _____ _________ __ ___ ______ ______ ______ ___ ________

5: _____ _____ _________ __ ___ ______ ______ ______ ___ ________

6: _____ _____ _________ __ ___ ______ ______ ______ ___ ________

7: _____ _____ _________ __ ___ ______ ______ ______ ___ ________

8: _____ _____ _________ __ ___ ______ ______ ______ ___ ________

9: _____ _____ _________ __ ___ ______ ______ ______ ___ ________

10: _____ _____ _________ __ ___ ______ ______ ______ ___ ________

11: _____ _____ _________ __ ___ ______ ______ ______ ___ ________

12: _____ _____ _________ __ ___ ______ ______ ______ ___ ________

Help line

enter command:

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-226status conference

Drop Reason The reason for the channel’s disconnect:

2-pri This drop reason occurs when an administration error causes

a mismatch in primary-secondary designation for a cascade link. This

mismatch shows that both MCUs are administered as primaries (see

“Cascading” for a description of primary-secondary compatibility).

2-sec This drop reason occurs when an administration error causes

a mismatch in primary-secondary designation for a cascade link. This

mismatch shows that both MCUs are administered as secondaries

(see “Cascading” for a description of primary-secondary

compatibility).

Agent The reservation agent has caused the call to disconnect (for

example, the agent has changed a connected dial-out destination

number).

Bandwidth mismatch between a call and the conference it

attempted to join. For example, a 56-kbps call attempted to join a

64-kbps conference that does not allow rate adaptation.

BondHshake BONDing handshake drop reason can be caused due

to the following reasons: information channel parameter not

supported or invalid, parameter negotiation terminated out of

sequence, timer expired because of the secondary channels did not

establish, or BONDing framing was not detected for one of the other

channels.

Busy This dial-out drop reason occurs when the MCU detects that

the conferee’s terminal equipment is busy. This drop reason is

detected by an ISDN cause value (for example h0). See “Dial-out” for

a description of CPTR usage.

Chair disconnected the endpoint, using either Chair Command

Disconnect (CCD) or Chair Command Kill (CCK) signals.

Conf End The conference was ended due to reaching stop time for

a reserved conference or due to an active conference being

converted to file.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-227status conference

Drop Reason

(cont’d)

Endpoint Clearing received from DS1 - the disconnect came from

the endpoint. The endpoint notified the MCU that it intended to

disconnect.

Far-end Clearing received from DS1 - the disconnect came from

either the network or the endpoint.

Handshake Either framing was never found (the endpoint could not

complete initialization - problems finding Frame Alignment Signal

(FAS), Multi Frame Alignment (MFA) and getting a corrected coded

cap-set) or framing was lost for some time (over 40 seconds) and the

endpoint was disconnected.

IDtimeout The MCU has not received response to the

UIN/password Query from the H.320 user after three attempts. Each

attempt has a system administered timeout period.

Internal MCU has a problem allocating trunk resources necessary

to route the dial-out call for the specified dial-numbers. This problem

can be associated with routing pattern or trunk associated translation

(for example, TAC specified in the dial-out number or routing pattern

points to a trunk group without members), or it can indicate a lack of

trunk resources (for example, all trunk members are maintenance

busy or all in-service members are busy on a call).

Network Clearing received from DS1 - the disconnect came from the

network. The endpoint that had the disconnect notification capability

disconnected without notifying the MCU.

Not-MCU The dial-out destination number(s) of the “CAS” extension

has terminated to a number that is not a dial-in cascade MCU

extension.

No-ring This dial-out drop reason occurs when the call has been up

for 30 seconds and no ringing is detected.

Reorder This dial-out drop reason occurs when the MCU detects

that there are no available trunks in the network to place the call. This

drop reason is detected by MCU CPTR resources. See “Dial-out” for

a description of CPTR usage.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-228status conference

Drop Reason

(cont’d)

Pre-AnsDrop The call disconnected before answer by an endpoint.

The cause of the disconnect may be the network, an endpoint, or a

terminal adapter. This drop reason is different from ‘No-answer,’

which indicates that a 60-second timeout occurred while alerting. In

this case, the call drops before the 60-second timer has expired.

Some busy endpoints connected through terminal adapters display

this behavior.

Resource MCU could not provide resources (VC or MMI) when the

call arrived or lost the resources during the call. This could be due to

them being Out of Service, busied out by craft, or being used by

system maintenance. This drop reason could also occur if the

DS1/MMI cable is disconnected. If there was a resource problem

when the call arrived, it would get reorder (fast busy) and not get

disconnected by the MCU.

Password Either the user entered the wrong password or the audio

add-on user did not enter it within the specified time period. Note that

the audio add-on user gets one attempt to enter a correct password

and inter-digit timing for each digit (that is, about 10 seconds

between digits).

System An MCU restart (level 2) disconnected all calls.

UIN-Inv The user entered an invalid User Identification Number.

Unknown The system could not determine the cause of the

disconnect.

Wrong-num This dial-out drop reason occurs when the MCU detects

the wrong destination number was dialed. This drop reason is

detected by MCU CPTR resources SDN cause value. See “Dial-out”

for details.

UCC controller intentionally disconnected the endpoint.

Drop Code A detail code complementing the Drop Reason (see above).

Additional bonding related information may be obtained from

supplementary BONDing Drop Codes described above.

AC Num Administered Connection Number - from 1 to 128. AC number can be

used to further diagnose a problem by combining status conference

information with the status administered connection command and

data stored in the error and alarm logs.

Ports Trunk The data endpoint that the channel is using.

Ports Video The MMI port for the channel.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-229status conference

Page 3 - Conference Information

This section only describes the fields that are specific to the endpoint-level

command output.

Screen 8-5. Page 3 of 6: status conference x endpoint y

Conference Info. This information applies mostly to full-screen conferences. The

Broadcaster field also applies to quad-screen presentation mode

conferences.

Ports Aud If the endpoint type is not “UCC,” the VC audio encoder port (which is

always paired to a decoder port) for the channel (only the first

channel). Because only one audio encoder port is allocated per

endpoint, it appears together with the ESM data port in the endpoint’s

channel 1 port slot position of the Port Aud/ESM column. For “UCC”

endpoint type, the channel 1 port slot position displays the allocated

Call Classifier resource.

Ports ESM The Expansion Service Module MMI data port. This field is always

blank.

Ports BONDng The MMI port used for BONDing for the channel.

Fr Err Frame error counter. A circular hex counter (0-FF) to indicate the

occurrence of framing errors.

status conference endpoint page 3 of 6

CONFERENCE INFO: Broadcaster: xx (See-Me)

Return Vid: xx

---------- MODE COMMANDS/COMMUNICATION MODES ------| EPT MISC | ------- FAW --

CMD STAT CONF EPT-IN EPT-OUT |------ I O | CH1 CH2

----- ---- ------------ ------------- -------------| AIM: y n | --- ---

XRATE: y 384 384 384 | VIS y n | A-OUT: y n

AUDIO: n G728 neutral G728 | MIS: n | A-IN: y n

56/64: y derestrict derestrict derestrict | MCV: n | M-FRM: y n

VIDEO: n H.261 H.261 H.261 |-------------| MFA: y n

MLP: y MLP-off MLP-off MLP-off | TALK: y 05 | MFN: y n

H-MLP: y H-MLP-off H-MLP-off H-MLP-off | VFCV: y 01 | FAS: y n

LSD: y LSD-off LSD-off LSD-off | BCTK: n 02 |MCUFAL: 00 00

HSD: y HSD-off HSD-off HSD-off | RTTK: y 01 | FEFAL: 00 00

CRYPT: y encrypt-off encrypt-off encrypt-off | BCLS: n |

S/M: y N-comp-6B-H0 N-comp-6B-H0 N-comp-6B-H0 | RTLS: n |

| HYPR: n 00 |

|DMUTE: n 00 |

|H.261: n 00 |

| VFMT: n 00 |

Help line

enter command:

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-230status conference

Mode Commands/Communication Modes. This is a collection of both incoming

and outgoing bandwidth allocations for the multiplex. The Incoming data is the

rate at which the MCU thinks the endpoint is communicating based on the

Bit-rate Allocation Signal (BAS) codes received from the endpoint/codec and the

capabilities the MCU has declared. The Outgoing data is the rate from the MCU

toward the endpoint. The following are column definitions for this section of page

Broadcaster Indicates the endpoint number that is the current broadcaster. The

Broadcaster can be qualified with the following keywords:

1. Broadcast - indicates a broadcast mode broadcaster.

2. Chair - indicates that the broadcaster was designated by the

chair.

3. See-Me - indicates that the broadcaster is a result of MCV

request from an endpoint.

4. Presenter - indicates a presentation mode broadcaster.

5. Rollcall - indicates that the broadcaster was designated by

the UCC via the Rollcall feature.

6. UCC - indicates that the broadcaster was designated by the UCC.

7. VAS - indicates a Voice Activated Switching broadcaster.

Broadcaster Indicates the endpoint number that is selected to be the next

broadcaster.

Return Vid Indicates the endpoint number that is the current return video. The

return video can be qualified with the following keywords:

1. blank - indicates that the return video is the previous broadcaster

forced to be return video because of VAS, action by Chair, action

by UCC, or endpoint MCV request. The broadcaster qualifier

identifies which action forced this endpoint to become return

video.

2. Autoscan - indicates auto scan return video. This is true only

when conference mode is broadcast with auto scan.

3. Browse - indicates that the return video was designated by the

UCC via the Browse feature.

4. VAS - indicates a Voice Activated Switching return video.

Next Return

Vid Indicates the endpoint number that is selected to be the next return

video.

CONF The desired conference operating mode. This may be different from

the endpoint in (EPT-IN) or endpoint out (EPT-OUT) modes.

CMD labels for the various types of mode commands

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-231status conference

The following are field definitions for the Mode Commands/Communication

Modes section of Page 3.

STAT indicates if the conference and the incoming modes are compatible.

A value of y indicates mode compatibility; a value of n indicates that

the modes are not compatible.

EPT-IN defines the communication modes coming in from an endpoint.

EPT-OUT defines the communication modes sent out to an endpoint based on

the number of channels connected and the capabilities of the

endpoint.

XRATE One of the supported rates in Table 8-10:

Table 8-10. Supported Transfer Rates

XRATE Bandwidth of the Call

2x64 2B (2x56 or 2x64)

128 112kbps or 128kbps

196 168kbps or 196kbps

256 224kbps or 256kbps

320 280kbps or 320kbps

384 336kbps or 384kbps

512 512kbps

768 768kbps

1472 1472kbps

1536 1536kbps‘

1920 1920kbps

Continued on next page

XRATE

(cont’d.)

XRATE may be 64 when the endpoint is just dialing in, or in the event

of problems. It implies that only one B channel is being used.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-232status conference

AUDIO Audio rate (kbps bandwidth) of the conference and the endpoint

must be the same but not necessarily their mode. When the audio

rate of the conference and the endpoint are different the endpoint’s

audio will interwork but the endpoint’s video will be invalid. MCU may

or may not send video to such an endpoint.

Table 8-11 summarizes expected endpoint audio mode with different

configurations of transfer rate, facility bandwidth, conference mode,

and whether or not all endpoints support the highest common audio

mode (HC audio) when the administered mode is auto. The highest

common conference mode is dependent on the administered

bandwidth. A ‘-’ in the table indicates ‘does not apply.’

Table 8-11. Audio Mode Configurations

Admin Mode

(HC Audio)

All

Support

HC Audio Xfer

Rate Facility

BW Conf Mode Expected Endpoint Mode

auto (G.728) yes <=128k - G.728 G.728

auto (G.728) no <=128k 64k G.711-A-56k G.711-A-56k B.711-Mu-56k

auto (G.728) no <=128k 56k G.711-A-48k G.711-A-48k G.711-MU-48k

auto (G.722) - >128k 64k G.722-56k G.722-56k G.711-A-56k G.711-Mu-56k

auto (G.722) - >128k 56k G.722-48k G.722-48k G.711-A-48k G.711-Mu-48k

G.728 - - G.728 G.728

G.711 - - 64k G.711-A-56k G.711-A-56k G.711-Mu-56k

G.711 - - 56k G.711-A-48k G.711-A-48k G.711-Mu-48k

G.722 - - 64k G.722-56k G.722-56k G.711-A-56k G.711-mu-56k

G.722 - - 56k G.722-48k G.722-48k G.711-A-48k G.711-Mu-48k

Continued on next page

AUDIO

(cont’d.)

Other possible AUDIO mode values include neutral (neutralized

I-channel) and Au-off, Frm (no audio signal) which never match

conference mode and are not supported by MCU.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-233status conference

Endpoint Miscellaneous (EPT MISC) Information. EPT MISC contains

miscellaneous states and counters for an endpoint. The flags can be a value of y

or n. The counters start with initial value of 0x00, they increment to 0xff, and then

56/64 The 65/64 field is derestrict when operating at per-channel

speeds of 64kbps, 128kbps, 192kbps, 256kbps, 320kbps, 384kbps,

512kbps, 768 kbps, 1472kbps, 1536kbps, or 1920kbps; it is

restrict when operating at 56kbps, 112kbps, 168kbps, 224kbps,

280kbps, 336kbps, 448kbps, and 672kbps.

Note that if the conference is configured for Nx56kbs operation, the

endpoint may signal either via capabilities or modes that is operating

at the proper rate. In such a case, even when we receive

derestrict command which does not match the conference

communication mode of restrict, if the capability indicates

restrict (MISC capability has restrict displayed on Page 4) the

STAT 56/64 is set to y to indicate 56/64 compatibility between the

conference and the endpoint.

VIDEO The Video mode: H.261 (recommended), H.CTX (proprietary),

H.CTX+ (proprietary), or SG4 (proprietary) indicate that video is on in

the direction indicated; video-off when the video is off.

MLP Multi Layer Protocol data mode. When Data Mode is administered as

any-mlp or ww-pcs, the MLP mode should be var-MLP. Other

values will affect video status.

The MLP mode should be MLP-off when Data Mode is administered

as none. Again, other values in this mode will affect video status.

H_MLP The High Speed MLP mode. The HMLP mode should be H-MLP-off.

Other values in this mode will affect video status.

LSD Low Speed Data mode. The LSD mode should be LSD-off. Other

values in this mode will affect video status.

HSD High Speed Data mode. The HSD mode should be HSD-off. Other

values in this mode will affect video status.

CRYPT Encryption mode. The CRYPT mode should be encrypt-off. Other

values in this mode will affect video status.

S/M Single/Multi channel interoperability mode. 6B-H0-comp indicates

that the sender is interoperating multiple channels and a single

channel (for example, 6B and H0). Not-comp-6B-H0 indicates that

the sender is not interoperating between 6B and H0. Normally this

value is Not-comp-6B-H0. Other values in this mode will affect video

status.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-234status conference

wrap around to 0x01. AIM and VIS are BAS commands which can be sent as

input (I) to MCU from an endpoint or as output (O) from MCU to an endpoint.

AIM Audio Indicate Muted. Value of y on input (I) indicates that this

endpoint has muted its audio. MCU will not VAS to an endpoint

displaying mute indicate. Value of n on input indicates that this

endpoint has not muted (only if endpoint audio mode is turned on).

Value of y on output (O) indicates that all other endpoints in the

conference have muted their audio (have sent AIM to MCU). MCU in

turn tells this endpoint (by sending it AIM) that there is no audio

output from MCU. A value of n on output indicates that there is an

audio path open across the bridge.

VIS Video Indicate Suppressed. Value of y on input (I) indicates that this

endpoint has suppressed its video (indicated video is muted). Value

of y on output (O) indicates that the MCU is not sending video to this

endpoint because there is no video broadcaster (broadcaster has not

joined or broadcaster’s video is not valid).

MIS Multipoint Indicate Secondary-status. This command is only sent as

output (O) to an endpoint. A value of n indicates that the endpoint is

viewed as capable of being a valid source (although not necessarily

at this moment). A value of n is the correct state to be in for video. A

value of y indicates that MIS was sent to an endpoint and that this

endpoint is viewed as a secondary endpoint. The endpoint is

included in the audio portion of the conference but not the video

portion. Video will not be sent.

MCV Multipoint Command Visualize. This command is only sent as input (I)

from an endpoint. A value of y indicates that an endpoint has

requested to become a broadcaster. This is used during Still Frame

Graphics and to force “presentation” mode.

TALK A value of y indicates that the VC board is detecting voice energy

from the endpoint. The TALK counter indicates the number of times a

start/stop was detected.

VRCV Value of y indicates if the endpoint is receiving video (MMCH is

sending video to the endpoint). The VRCV counter indicates the

number of times video was sent/not sent to this endpoint.

BCTK Applies to single screen and quad-screen presentation mode

conferences. A value of y indicates that the endpoint is the video

broadcast source. The BCTK counter indicates the number of times

this endpoint was the video broadcast source.

RTTK Applies only to single screen conferences. A value of y indicates that

the endpoint is the return video source. The RTTK counter indicates

the number of times this endpoint was the return video source.

BCLS Applies to single screen and quad-screen presentation mode

conferences. A value of y indicates that the endpoint is watching the

video of the broadcast source.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-235status conference

Frame Alignment Word (FAW) Information. The FAW section of page 3

provides the channel Frame Alignment Word information for the communication

paths labeled CHL 1 and 2. For 2B calls, both CHL 1 and 2 are used. For

1-channel calls (112,bps, 128kbps, 168kbps, 196kbps, 224kbps, 256kbps,

280kbps, 320kbps, 336kbps, 384kbps, 768kbps, 1472kbps, 1536kbps, and

1920kbps) only CHL 1 is used. A-OUT, A-IN, M-FRM, MFA, and MFN are flags

with values of y or n.

RTLS Applies only to single screen conferences. A value of y indicates that

the endpoint is watching the video of the return source.

HYPR A value of y indicates hyperactivity from an endpoint (MCU isolated

endpoint from the MCU conference due to “thrashing” behavior) and

affects endpoint’s status as a video source (for 5 seconds of

hyperactivity timer). The HYPR counter indicates the number of times

this endpoint was hyperactive.

DMUTE A value of y indicates that the decoder was muted by the VC board or

the software in the MCU. VC board mutes the decoder when it loses

MMI or endpoint framing is lost, when it receives an invalid audio

code word, and when endpoint is hyperactive. The only time that the

MCU software mutes the decoder of an endpoint is to mute all

endpoints, other than the broadcaster, when a mode of a conference

is “broadcastw/scan” (broadcast with auto scan). The DMUTE

counter indicates the number of times this endpoint’s decoder was

muted by the VC board.

VFMT The video format applicable only to quad-screen conferences. This

field always has a value of n, indicating QCIF format.

H.261 A value of y indicates video framing loss. The H.261 counter

indicates the number of times the framing was lost.

A-OUT MCU has endpoint framing.

A-IN Endpoint has MCU framing

M-FRM Multichannel frame alignment is present (alignment of both channels

in 2B).

MFA Multiframe alignment word is present (required in 2B call).

MFN Multiframe numbering is present (required in 2B call).

FAS Frame Alignment Signal (FAS) channel number (1 or 2). This number

should match the column header.

MCUFAL MCU Frame Alignment Loss (MCUFAL). A counter of the number of

times the MCU indicates to the endpoint that it has lost endpoint FAW

or multichannel synchronization (M-FRM). The MCU a-bit toggles

when the MCU gains or loses endpoint multichannel synchronization.

This counter starts with an initial value of 0x00, increments to 0xff,

then wraps around to 0x01. The MCUFAL count is also shown in the

Fr Err field on Page 2

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-236status conference

Page 4 - Endpoint Capability Information

This section only describes the fields that are specific to the endpoint-level

command output.

Screen 8-6. Page 4 of 6: status conference x endpoint y

FEFAL Far End Frame Alignment Loss (FEFAL). A counter of the number of

changes the MCU detects in the endpoint’s a-bit (A-OUT). The

endpoint a-bit toggles when an endpoint gains or loses MCU framing.

This counter starts with an initial value of 0x00, increments to 0xff,

then wraps around to 0x01.

status conference endpoint page 4 of 6

ENDPOINT CAPABILITY INFORMATION

--------------------------------------------------------------------------------

VID | vfmt: QCIF cfps: 30 H.CTX SG4 imp

| da_sfg qfps: 7.5 H.CTX+ SG4_sfg

-----|--------------------------------------------------------------------------

MISC | derestrict S/M mbe dcomp cic

-----|--------------------------------------------------------------------------

XR | 64 64x2 64x3 64x4 64x5 64x6 384 384x2 384x3 384x4 384x5

| 128 192 256 320 512 768 1152 1472 1536 1920

-----|--------------------------------------------------------------------------

AUD | ntrl 711m 711a g728 g722_64 g722_48

-----|--------------------------------------------------------------------------

LSD | var 300 1200 4800 6400 8000 9600 14.4k 16k 24k 32k 40k 48k 56k 62.4k 64k

-----|--------------------------------------------------------------------------

HSD | var 64k 128k 192k 256k 320k 348k 512k 768k 1152k 1536k

-----|--------------------------------------------------------------------------

MLP | var 4k 6.4k 14.4k 16k 22.4k 24k 30.4k 32k 38.4k 40k 46.4k 62.4k

-----|--------------------------------------------------------------------------

HMLP | var 62.4k 68k 128k 192k 256k 320k 384k

--------------------------------------------------------------------------------

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-237status conference

Endpoint Capability Information. Fields on this page will only be displayed if an

endpoint declares the specific capability. For example, if an endpoint does not

declare the VID H.CTX capability, the H.CTX field will not be displayed.

VID Provides information about the type of video and frame rate the

endpoint supports.

vfmt - does not display if the endpoint has no video capability. All

values are blank if there is an active call or this is an audio-only

endpoint. Otherwise, values for this field include:

■FCIF for full CIF

■QCIF for quarter CIF. Support of CIF implies support of QCIF. In

general, for larger screens, CIF displays sharper resolution video,

which ZCIF is blocked, but may run at higher frame rates and less

clear. The differences are less observable on very small displays.

■cfps and qfps are the maximum frame rate (frames/second) at

which the endpoint can receive video for CIF and QCIF operating

modes. CIF frame rate values are 30fps, 15fps, 10fps, and 7.4fps.

If the endpoint does not support CIF (that is, the vfmt field is

QCIF), the cfps value should be blank.

■da_sfg indicates support for H.261 Still Frame Graphics

transfers.

■H.CTX, H.CTX+ and SG4 are proprietary video format

capabilities.

■SG4_sfg indicates support for SG4 Still Frame Graphics

MISC The restrict field is 1 way for an endpoint to indicate that it is

operating at 56 kbps per channel, the other way is the 56/64

command mode with a value of restrict. An endpoint on a 56 kbps

conference must send one or both of the 2 indications that they are

operating at 56 kbps before they become a video source in a 56 kbps

conference. If they signal either way that they are operating at 56

kbps in a 64 kbps or 384 kbps conference, they are an audio-only

source, but the MCU continues to send Selected Communication

Mode (SCM) toward them when possible.

A MISC capability of derestrict and a 56/64 command of

derestrict together indicate that an endpoint is operating at 64

kbps. If either is restrict, the conference operates at 56 kbps.

Other field values include:

■dcomp indicates support for WorldWorx PCS data compliance.

■mbe indicates support for Multi Byte Extension. MBE capability is

used for the exchange of passwords, terminal names, and other

special capabilities, such as, support of WorldWorx PCS specific

features.

■cic (Chair Indicate Capability) indicates chair control capability.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-238status conference

Page 5 - Endpoint Call Status Information

This page summarizes such call-related status as per-channel join counts,

join/drop time, drop reason, drop code, and auxiliary bonding drop code. In

addition, it contains a drop code and software fields from the previous call. The

data on the page is always retained. The Endpoint Call Status Information section

groups together all call-related fields. The only new field in this section is Join

Count; all other fields are described in Screen 8-3 and Screen 8-4.

XR Transfer rate capabilities are statement about the speeds at which

the endpoint can operate over the current connection and operate a

Px64 Multiplex.

For a 384 kbps (H0) call, the endpoint sends its capabilities to

indicate 384 kbps support, which displays as 384. On a 336 kbps

call, the endpoint must signal 384 kbps support. If an endpoint does

not indicate support for 384 kbps on a 384/336 kbps conference, the

MCU provides Audio Only Communications Mode (ACOM). For a 2B

conference, the MCU sets the rate to 2x64, expecting the endpoints

to do likewise (64x2 is displayed; if this is not displayed, there is no

64x2 capability). Endpoints may occasionally take 2x64 (or the

current channel rate: 384, 768, 1472, 1536) out of their capability.

This is Mode 0 forcing and is part of normal procedures. The MCU

will provide AOCM if the endpoint does not signal support matching

the configuration of the conference.

AUD The audio fields are statements of the audio protocols that the

endpoint supports. 711m and 711a are PCM (G.711) and support Mu

and A-law, respectively, and at least one is required of endpoints.

The g728 field indicates whether G.728 is supported (LB_CELP). This

value depends upon the type of the endpoint and how that endpoint

is currently configured. The g722_48 field indicates endpoint support

for G.722 (7 kHz) at both 48 kbps and 56 kbps. Therefore, g722_48

indicates that the endpoint supports G.722 audio at both rates. The

g722_64 field indicates endpoint support for G.722 at 64 kbps in an

unframed (not supported by the MCU) mode.

LSD The LSD fields indicate the capabilities for Low Speed Data

conferencing.

HSD The HSD fields indicate the capabilities for High speed Data

conferencing.

MLP The MLP fields indicate the capabilities for Multi Layer Protocol Data

capabilities.

HMLP The HMLP fields indicate the conference’s capability for High Speed

MLP data conferencing.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-239status conference

Screen 8-7. Page 5 of 6: status conference x endpoint y

Page 6 - Administered Connections

This page summarizes information on the administered connections associated

with this endpoint. This data can only be viewed while the conference is active.

Join Count This field displays a count of the number of times this endpoint joined

this conference during this conference session. This counter starts

with an initial value of 0, can increment to 64, and wraps around back

to 1.

status conference endpoint page 5 of 6

ENDPOINT CALL STATUS INFORMATION

Join Join Drop -------------- Drop -------- --- Previous -----

Chan Count Time Time Reason Code BondCode DropCode Software

1: __ _____ _____ __________ __ __ __ ________

2: __ _____ _____ __________ __ __ __ ________

3: __ _____ _____ __________ __ __ __ ________

4: __ _____ _____ __________ __ __ __ ________

5: __ _____ _____ __________ __ __ __ ________

6: __ _____ _____ __________ __ __ __ ________

7: __ _____ _____ __________ __ __ __ ________

8: __ _____ _____ __________ __ __ __ ________

9: __ _____ _____ __________ __ __ __ ________

10: __ _____ _____ __________ __ __ __ ________

11: __ _____ _____ __________ __ __ __ ________

12: __ _____ _____ __________ __ __ __ ________

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-240status conference

Screen 8-8. Page 6 of 6: status conference x endpoint y

Dial-out

number The actual numbers that are dialed out by the administered

connections for each channel in the call. Note that the dial Out #1 and

#2 on page 1 of the forms display the DCP endpoint number. This is

particularly useful with bonding dial-out calls.

status conference endpoint page 6 of 6

ADMINISTERED CONNECTIONS INFORMATION

AC Retry Failure

Chan Num Dial-out Number Connection State Count Cause

1: ___ _____________________ _____________________ __ __

2: ___ _____________________ _____________________ __ __

3: ___ _____________________ _____________________ __ __

4: ___ _____________________ _____________________ __ __

5: ___ _____________________ _____________________ __ __

6: ___ _____________________ _____________________ __ __

7: ___ _____________________ _____________________ __ __

8: ___ _____________________ _____________________ __ __

9: ___ _____________________ _____________________ __ __

10: ___ _____________________ _____________________ __ __

11: ___ _____________________ _____________________ __ __

12: ___ _____________________ _____________________ __ __

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-241status conference

Connection

State Indicates the current call state of the AC. The following are connection

states associated with dial-out ACs:

■enabled - is transient in nature and indicates that an AC is about

to enter the attempting to connect state.

■disabled - this may mean one of three things:

— The AC has reached an administered retry threshold, and all

retries are stopped. Verify this by checking the Error Log and

checking whether an error type of 9 is logged against the AC.

— The AC was in a connected state and the far end disconnected.

— The initial channel call has not yet connected. No dial out call

attempt is made for the additional channel(s) until the initial

channel has reached a connected state.

■not scheduled - is transient in nature and indicates that an AC is

about to enter the “attempting to connect” state.

■waiting to retry - means that the AC is inactive (sleeping)

and waiting for the retry timer to expire. Once the timer expires, the

AC sends a dial out call and enters the “attempting to connect”

state. ACs in this state indicate that the dial out call has failed at

least once.

■attempting to connect - means that the AC is active on a call,

but the call has not yet connected.

■connected - means that the call associated with the AC has been

answered and join cut-thru to the conference.

Retry Count This field indicates how many retries have been attempted for this AC

during this join attempt. This field does not clear when the AC

connects. However, it clears when a new join attempt is made via a

Redial feature. Note that this is different from the Join Count which

counts the number of times the channel joined the conference during

this conference session.

Failure Cause This field shows an ISDN or CPTR cause value (values lower than 0x7f)

recorded when the last dial out call was dropped. Values above 0x7f

are generated internally. Table 8-12 lists all possible failure cause

values displayed by this field and its associated description. The

Failure Cause value is logged in the Error Log and can be

displayed via the display errors command. (Err Type is normally

displayed as a decimal.)

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-242status conference

Table 8-12. Status AC - Failure Cause Values

Failure Cause

(hexadecimal) Description

0x00 (0t0) N/A

0x01 (0t1) Incorrect destination address

0x02 (0t2) Reason unknown

0x06 (0t6) Reason unknown

0x10 (0t16) Normal call clearing

0x11 (0t17) Endpoint not available

0x12 (0t18) ISDN timer expired

0x15 (0t21) Reason unknown

0x12 (0t22) Destination address changed

0x1C (0t28) Bad destination or access denied

0x1D (0t29) Access denied

0x1F (0t31) Reason unknown

0x22 (0t34) Trunks unavailable

0x26 (0t38) Temporary or facility failure

0x29 (0t41) Temporary or facility failure

0x2A (0t42) Resources unavailable

0x2C (0t44) Resources unavailable

0x32 (0t50) Access denied

0x34 (0t52) Access denied

0x36 (0t54) Access denied

0x3A (0t58) Resources unavailable

0x41 (0t65) Required capability not implemented

0x42 (0t66) Required capability not implemented

0x45 (0t69) Required capability not implemented

0x51 (0t81) ISDN protocol error

0x52 (0t82) Required capability not implemented

0x58 (0t88) Incorrect destination number

0x60 (0t96) ISDN protocol error

0x61 (0t97) ISDN protocol error

0x62 (0t98) ISDN protocol error

Continued on next page

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-243status data-module

status data-module

status data-module extension [print]

This command displays internal software states of a specified data-module port.

It is useful for diagnosis and locating facilities to which the data module is

connected.

0x64 (0t100) ISDN protocol error

0x66 (0t102) ISDN timer expired

0x7f (0t127) Reason unknown

0xC2 (0t194) Ring no answer

0xC8 (0t200) Hi and dry - no feedback detected

0xC9 (0t201) Cascade link administered wrong

0xCA (0t202) CPTR not available to detect failure

Table 8-12. Status AC - Failure Cause Values — Continued

Failure Cause

(hexadecimal) Description

Continued on next page

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-244status data-module

Output

If the specified port is administered as a system port, the following fields will be

displayed at the bottom of the screen. See PDATA-PT in Chapter 9 for more

information.

Data

Ext/Sta Ext

for Stn DM

The data module’s extension number. For DTDMs, the

connected station extension is shown instead.

Port/Channel

Number The location of the port connected to the data module. For

data channels, the channel number is shown instead.

Service

State The operational state of the data-module:

in-service/idle The data module is connected but not

in use.

in-service/active The data module is connected and in

use.

out-of-service The data module has been removed from

service.

CF Destination

Ext The call-forwarding destination, if any, of the port.

Maintenance

Busy Whether the port is busied out for testing.

Connected Ports Locations of ports to which the data module is currently

connected.

Associated

PDATA Port The location of a port on a TN553 Packet Data Line

circuit pack to which this data-module port is

connected.

Service State The operational state of the associated PDATA port.

Maintenance

Busy Whether the PDATA port is busied out for testing.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-245status hardware-group

The following display shows a typical result when status data-module 301 is

entered.

The following display shows a typical result when status data-module 5451 is

entered and extension 5451 is a system port.

status hardware-group

status hardware-group [print]

Summary information on the active or last hardware group tests will be displayed.

This display includes the number and percentage of maintenance objects tested,

the percentage of tests passed/failed/aborted, the time elapsed since initiating

the hardware group test, the specific hardware group test command (see test

hardware-group command) initiated, and the state (active/canceled/complete) of

the hardware-group test.

status data-module 301

DATA MODULE STATUS

Data Ext/Stn Ext for Stn DM: 301 Service State: out-of-service

Port/Channel Number: 01C1103 Maintenance Busy? no

CF Destination Ext:

Connected Ports:

status data-module 5451

DATA MODULE STATUS

Data Ext/Stn Ext for Stn DM: 5451 Service State: in-service/active

Port/Channel Number: 01D0601 Maintenance Busy? no

CF Destination Ext:

Connected Ports: 04B0402

Associated PDATA Port: 01D0501

Service State: in-service/active

Maintenance Busy? no

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-246status hardware-group

Output

Hardware

Group

Command

State:

The state of a hardware-group command: active: testing is in progress;

canceled: testing has been canceled; complete the command has

completed and there is no testing going on.

Number of

MOs Tested: The number of MOs in the specified group (refer to test

hardware-group command) that have had been tested by the current

hardware-group command. This includes all MOs that were either

actually tested or were aborted due to resource contention.

Total

Number of

MOs to be

Tested:

The total number of MOs in the group that was specified in the "test

hardware-group" command.

Percent

Complete: A ratio of the number of MOs completed and the total number of MOs

to test in the command.

Elapsed

Test Time: The duration of the hardware-group test. If a test was canceled and

then restarted this time excludes the cancel period. If the

hardware-group command has finished it will indicate the length of

time it took to complete the command. The time is displayed in the

HH:MM:SS format where HH is hours, MM is minutes, and SS is

seconds.

Repetition

Number The number of iterations that have been completed corresponding to

the ‘repeat’ or the ‘continuously’ option.

Percentage

of Tests

Passed:

The percentage of tests that passed.

Percentage

of Tests

Failed:

The percentage of tests that failed.

Percentage

of Tests

Aborted:

The percentage of tests that were aborted.

Command: The hardware-group action object and qualifiers that were entered.

Test

sequence: This will display either short or long.

Test

repetition: This will display either continuously or the keyword repeat along with

the repeat value entered.

Output

options: This will display the selections that were chosen on the input form:

auto-page, background, or failures.

Hardware

options: This will display the selections that were chosen on the input form,

(all-ports or SPE-interchange).

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-247status health

The following display shows a typical result when status hardware-group is

entered.

status health

status health [print]

The status health command displays a summary of current conditions throughout

the system that are critical to service. Monitor health displays the same screen

and updates it automatically.

Parameters

Output

print Sends output to a printer connected to the terminal and to the screen

Major Number of major alarms logged up to 2000

Minor Number of minor alarms logged up to 2000

Warning Number of warning alarms logged up to 2000

Trunks Number of busied-out trunks

Stations Number of busied-out stations

Others Number of busied-out maintenance objects, excluding trunks and

stations

status hardware-group page 1 of 1

HARDWARE GROUP STATUS

Hardware Group Command State: active

Number of MOs Tested: 11070

Total Number of MOs to be Tested: 12300

Percent Complete: 90%

Elapsed Test Time (hr:min:sec): 4:15:30

Repetition Number: 1

Percentage of Tests Passed: 82%

Percentage of Tests Failed: 11%

Percentage of Tests Aborted: 7%

ENTERED HARDWARE GROUP Command

Command: test hardware-group system

Test sequence: short

Test repetition: repeat 3

Output Options: failures

Hardware Options: SPE-interchange

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-248status health

Static Percentage of CPU time currently dedicated to high priority items such

as the operating system, rounded to the nearest whole number

SM Percentage of CPU time currently dedicated to system management or

periodic and scheduled maintenance, rounded to the nearest whole

number

If a large amount of periodic or scheduled maintenance testing is being

performed, this number can be high without affecting service.

CP Percentage of CPU time currently dedicated to call processing, rounded

to the nearest whole number

Call processing has priority over system management and will draw

occupancy from the SM or IDLE categories.

Idle Percentage of CPU time currently idle and available for use, rounded to

the nearest whole number

Active SPE Always A for a simplex SPE, otherwise:

A or BThe currently active SPE

lockedThe SPE is locked by the SPE-Select switches on the

Duplication Interface circuit packs.

autoThe switches are set to allow the system control of active SPE

selection.

Active PNC Always A for a simplex PNC, otherwise:

A-PNC The currently active PNC or B-PNC

lockedThe PNC is locked via the set pnc command.

autoThe system is controlling selection of the active PNC.

Duplicated? Whether the SPE and PNC are duplicated

SPE Power Current source of power to the PPN

commercialThe SPE is currently powered by the normal external

power source.

backupThe SPE is currently powered by the backup batteries. This

is usually due to a failure of the external power source.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-249status health

Time Source The current source of timing signals used for system synchronization

For systems with a Stratum 3 clock:

externalNormal operating condition

internalAnother source besides the Stratum 3 clock, such as a

Tone-Clock circuit pack, is providing the master timing signal.

For systems with Stratum 4 timing:

primaryThe primary administered timing source

secondaryThe secondary administered timing source

localAnother source besides the administered ones, such as a

Tone-Clock circuit pack, is providing the master timing signal.

# Logins Number of current users

Cab Cabinet number

Cabinet numbers can be related to port network numbers with the list

cabinet command.

Emerg Trans The current setting of the switches on the SYSAM and EPN Maintenance

circuit packs that control Emergency Transfer

See EMG-XFER in Chapter 9. For a PPN cabinet with duplicated SPEs,

settings for both SYSAM circuit packs are displayed; auto is then

abbreviated to a, and off to of. If the Emergency Transfer switch

setting on a standby SYSAM is changed while handshake is down, this

field will display the prior value until handshake is restored.

auto - Emergency Transfer is under system control and is not

currently activated (normal operating state).

auto + Emergency Transfer is under system control and is in effect.

on Emergency Transfer has been manually activated. This setting

should only be in effect during an emergency.

offEmergency Transfer is manually prevented from occurring. This

setting should only be in effect when a technician is on site.

n.a.The setting of the switch in this EPN is not available to the

switch. The Expansion Archangel Link may be down.

Mj, Mn, Wn Number of Major, Minor or Warning alarms associated with the cabinet

An asterisk indicates that the number exceeds 99.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-250status isdn-testcall

The following display shows a typical result when status health is entered on a

system with 3 cabinets.

Feature Interactions

In a High or Critical Reliability System, if the standby SPE Emergency Transfer

Select Switch is changed and the handshake is down, the displayed Emerg

Trans field will be incorrect until the handshake comes up again.

status isdn-testcall

status isdn-testcall group# / member# [print]

Examples

status isdn-testcall 78/1 print

PNC Current Port Network Connectivity (PNC) status for each of the port

networks in the cabinet

When multiple port networks exist within a cabinet, Carriers A, B, and C

are listed first and separated from Carriers D and E by a slash (e.g.

up/up).

up Both the Expansion Archangel Link (EAL) and the Indirect

Neighbor Link (INL, if applicable) are available.

dn Both EAL and INL (if applicable) are not available.

ne (Near End) The EAL is available but the INL is not available.

fe (Far End) The INL is available but the EAL is not available.

up/up When two port networks share a cabinet, the port network in

carriers A, B, and C is listed first and separated from the one in

carriers D and E by a slash.

Time of Day Current system time

status health

SPE: A/Auto B/functional OCC: ST: 9% Cp: 25% Sm: 10% Idl:66%

PNC: A-PNC/Auto B-PNC/functional ALARM:Maj: 0 Min: 2 Wrn: 9

Pwr: Comm Sync:local Logins:4 BUSYOUTS:Trk: 0 Stn: 0 Oth: 0

Cab EmTr Mj Mn Wn PNC Cab EmTr Mj Mn PNC Cab EmTr Mj Mn Wn PNC

1 off 0| 7| 0 up

2 off 0| 0| 4 up

3 nia 0| 2| 0 up -Press CANCEL to

quit - 9:33 THU APR 16 :1993

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-251status isdn-testcall

This command displays the progress of an outgoing ISDN-PRI test call on the

trunk specified. The tested ISDN-PRI B-channel port number, bit error rate,

number of bits transmitted, block error rate, number of blocks transmitted, start

time, duration specified, duration of test call and reason of termination are

displayed on the status form.

If the bit error rate or block error rate is greater than zero, the ISDN-PRI trunk

“may” be in a troubled state. Based on the statistical information displayed on the

terminal, it can be decided to take the ISDN trunk out of service. This is

subjective data because the ISDN trunk may be used for data or voice. If the

trunk is used for data and the rates are high, the trunk should be taken out of

service. If the trunk is used for voice, the trunk may not have to be taken out of

service. High rates may also be due to some type of power hit on the line.

Output

Port This field specifies the physical address of the ISDN-PRI

B-channel.

Bit Error

Rate The measured bit error count according to the comparison of

the sent and received bit pattern. The number is displayed in

scientific notation.

Number of

Bits The number of bits generated. The number is displayed in

scientific notation.

Block

error Rate The measured block error count according to the comparison

of the sent and received bit pattern. The number is displayed

in scientific notation.

Number of

Blocks The number of blocks generated. The number is displayed in

scientific notation.

Start Time The time the test call started (dd/hh:mm).

Duration

Specified The duration specified in minutes for how long the test call

should run. Valid durations are 1-120 (minutes) or blank (to

indicate the default amount of minutes was used to run the

test).

Duration

of Test The duration specified in minutes for how long the test call has

been running. A blank indicates that the default amount of time

was used to run the test.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-252status journal-link

The following display shows a typical result when status isdn-t 80/1 is entered.

status journal-link

status journal-link wakeup-log | pms-log [print]

This command displays the operational status of a wakeup-log or a pms-log

printer link. If the link is down, the number of times the switch has tried to

re-establish the link will be shown.

A journal printer is used to document automatic wake-up events, emergency

access to attendant events and, if the Property Management System is not

functional, housekeeping events. When the system includes two printers, one is

for the housekeeping events and the other is used for automatic wake-up events

and emergency access events.

Reason of

Termination The reason of termination indicates why the test call has

terminated. Valid reasons of termination are "finished,"

"canceled," "overflow," "no bits," "transmission," "internal fail,"

"data corrupt," and "in progress." A termination reason of

"finished" means the test finished in the specified time. A

termination reason of "canceled" means the test call has been

canceled with the "clear isdn-testcall" command. A reason of

"overflow" denotes that the bits transmitted have overflowed

buffer allocation. A reason of "no bits" means that no bits have

been received because the ISDN-PRI test call circuit

connection is bad. A reason of "transmission" means there has

been a data transmission interruption, probably caused from a

power hit. A termination reason of "internal fail" specifies that

there is an internal error on the Maintenance/Test circuit pack.

A reason of "in progress" means the test is still running and a

reason of "data corrupt" is used for any other error condition.

status isdn-testcall 80/1 Page 1 of 1 SPE A

ISDN TESTCALL STATUS

Bit Number Block Number Duration Reason

Error Of Error Of Start Duration Of Of

Port Rate Bits Rate Blocks Time Specified Test Termination

1B1401 0EE0 4EE7 0EE0 6EE2 25/12:36 120 100 in progress

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-253status link

Parameters

Examples

status journal-link wakeup-log

status journal-link pms-log print

Output

The following display shows a typical result when status journal-link

wakeup-log is entered.

status link

status link link# [print]

wakeup-log The printer that handles automatic wakeup events, emergency

access events and scheduled reports.

pms-log The printer that handles housekeeping events while the PMS is

down.

print This qualifier sends output to a printer connected to the terminal and

to the screen.

Link State The operational status of the link as follows:

up The link is established and is capable of supporting the

application. This is the normal operational state.

down The link is physically down.

extension not administered An extension number for the

printer administered has not been assigned on the hospitality

system parameters.

Maintenance

Busy Whether there is any maintenance testing being performed upon

the link.

status journal-link wakeup-log SPE A

JOURNAL LINK STATUS

Link State: down

Number of retries: 1

Maintenance Busy? no

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-254status link

The status link command displays the operational status associated with a

specified X.25 link. If you know the physical Packet Gateway port number, but

not the link number, use status pgate-port to access the same information.

Adjunct Applications supported over X.25 connections include:

■AUDIX

■Calling Party Billing Number (CPN/BN or ISDN Gateway)

■CMS

■DCS

■Gateway Channels for DCS over ISDN-PRI

■Message Server

For details regarding these adjuncts and their administration, see

DEFINITY

Enterprise Communications Server Release 5 Administration and Feature

Description

The following terms are used in the descriptions of the output fields:

Link A synchronous connection between the switch and an adjunct or

another switch. The link consists of three protocol levels described

below. The entire link is identified by a link number (1-16) which is

specified on the change communications-interface links form.

Level 1 The physical connection between a local port on a PGATE board and the

corresponding hardware at the other end (for example, a PI board on a

G3i, an SCP board on AUDIX, or a PGATE board on another G3r). There

may be several Level 1 components between these two endpoints (for

example, modems, DS1 facilities, cables, and so forth.).

Level 2 The logical protocol that allows data communication between these two

endpoints. BX.25 specifies that this be the LAPB (Link Access Protocol

on the B-channel) protocol. Frames are sent at Level 2. Establishment of

the protocol requires one end to send a SABM (Set Asynchronous

Balanced Mode) frame and the other to respond with a UA (User

Acknowledgment) frame. Both sides send SABMs until they receive a

UA, at which time Level 2 is up and the Link Status field indicates

“restarting”. Restarting should be a temporary condition, since the link is

unusable until Level 3 comes up. Level 3 should come up quickly after

the establishment of Level 2.

Level 3 The logical protocol that allows multiplexing of many channels onto one

Level 2 link. BX.25 specifies the X.25 data phase protocol. Packets are

sent at Level 3 and are included in Level 2 frames. This protocol is

established after Level 2 when one end sends a Restart packet and the

other end replies with a Restart Confirm packet. The Link Status field

indicates "connected" when Level 3 is up.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-255status link

Parameters

Output

Processor

channel One of the 128 channels that connect the SPE to ports communicating

with adjuncts or other switches over the BX.25 links. A single link may

utilize up to 64 processor channels. The link number (1-16), the Level 3

processor channel number (1-128), and the name of the associated

adjunct (dcs, audix, and so on) using the channel are administered on

the communication-interface processor-channel form which can be

accessed with display and change commands.

Hop channel Used in DCS, a hop channel allows a remote switch to communicate with

another switch (or an adjunct) through an intermediary switch (called the

tandem switch). The hop channel connects a channel on one link to a

different channel on another link to form an extended connection that

allows the joined endpoints to function as if they were directly

connected. In this way each machine in the DCS network can have

processor channel connections to every other machine without requiring

a direct link with every other machine.

link# The number (1-16) used to identify a specific link.

Data

Extension The extension of the packet gateway port.

Port

Location The physical location of the packet gateway port

(cabinet-carrier-slot-circuit).

Service

State One of the following service states is displayed:

in-service/idle The circuit pack has been inserted by

system software and the port has initialized properly, but

Level 3 protocol is not established.

in-service/active The circuit pack has been inserted by

system software, the port has initialized properly, and Level 3

protocol is established.

out-of-service Either the port is busied out or the circuit

pack is absent.

Maintenance

Busy? Whether or not the Packet Gateway port is busied out for

maintenance testing.

Connected

to The port that connects to the link. The port can be specified

by destination digits or by an extension number entered in the

Connected To field on the Change

Communication-Interface Link form.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-256status link

AC This field is displayed when the extension displayed in the

Connected to field is part of an administered connection.

The following information is given:

■Administered connection number

■Status of the administered connection: Connected,

Disconnected, or Disabled

■Extension type: Orig for an originating extension and

Dest for a destination extension

The status command searches for the first occurrence of the

Connected Data Module as an originator or destination of an

AC. If the same AC is administered twice (with different

numbers), the lower numbered one is disabled and the

higher numbered one is enabled. In such a case, the

command will find the lower one and display it as not

connected even though the link may be up on the higher one.

Link Number The link number (1-16) specified on the command line.

Link Id A descriptive string assigned by the user. This is ordinarily

the name of the application or adjunct connected to the link.

Link Status One of the following states is displayed:

connected A Level 3 connection with the other end is

established.

disconnected A Level 2 connection with the other end is

not established.

restarting A Level 2 connection with the other end is

established and the Level 3 connection is being attempted.

Active

Channels The number of logical channels active on this link.

Service

State The service state of the PDM listed in the Connected to

field: in-service/active, in-service/idle, or

out-of-service.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-257status link

The following fields represent values of counters read from the Packet Gateway

circuit pack. These counters are not initialized when the circuit pack is inserted.

To get reliable values for these, use clear link and wait about 15 minutes.

CRC Check

(receive) The number of frames received with a bad Cyclic Redundancy Check.

Excessive errors of this type indicate noise on the link, which is usually

caused by a Level 1 problem. If this is the case, try testing and replacing

the various Level 1 components in the connection or the circuit pack at

the far end of the link. Look also at the error counters for the far-end

circuit pack. If the near-end CRC Check or Invalid Frame counters are

increasing, the far-end should report an increasing number of

retransmitted frames. If this is the case, the problem probably lies in the

connecting facilities.

Invalid Frame

(receive) The number of frame errors received from the far end of the link.

Diagnostics for this counter are the same as those for "CRC Check

(receive)" described above.

Information

Frame

(retransmit)

The number of Level two information frames that have been retransmitted

due to errors or missing messages. A high value in this field usually

means noise is being introduced on the link, causing the data within the

information to be changed; therefore, when the cyclic redundancy check

(CRC) is performed by the receiver it will not agree with the CRC sent

with the message. Excessive errors of this type indicate noise, usually

caused by a Level 1 problem. Try testing and replacing, if necessary,

both the various Level 1 components in the connection and the circuit

pack. Look also at the error counters on the far-end circuit pack. If the

CRC check or Invalid Frame counters are increasing on the far-end, the

near-end should report an increasing number of retransmitted frames. If

this is the case, then the problem probably lies in the connecting

facilities.

Level 2 link

reset

(receive)

This value indicates the number of times the Level 2 protocol has been

reset by the far end. A non-zero value indicates one of the following:

■Noise is being introduced on the link and a reset has been

requested. See ‘‘Information Frame (retransmit).’’

■If this counter increases without the link coming up, and the near

end’s transmitted resets are increasing also, there may be a one-way

connection (incoming only).

■If the near end’s resets transmitted count is not increasing, the near

end may not be accepting the reset request. Busyout and release the

link.

■Translations are not correct. One side must act as a DTE and the

other as a DCE. Try changing the administration of the near end to

the opposite of its current definition on the X.25 data module form.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-258status link

Level 2 link

reset

(transmit)

The number of times the Level 2 protocol has been reset by the near end.

A non-zero value may indicate any of the following:

■Noise is being introduced on the link, causing a reset. (See "Invalid

Frame (receive)" above.

■The link has been taken down by the near end, resulting in the far

end continuously sending SABMs while waiting for the near end to

■The far end has faulty translations, causing it to fail to respond to the

I-frames received.

■The connections to the far end are faulty.

Level 3

restart

packet

(receive)

The number of "Level 3 link reset" messages received by the switch.

These packets are received when the connected application decides to

reset and restart the communication channel. This counter is meaningful

only if there are no Level 2 problems. If Level 2 is functioning correctly,

non-zero values may indicate a malfunctioning adjunct, or slow packet

transmission at the switch end causing the adjunct’s timers to expire.

Level 3

restart

packet

(transmit)

The number of "Level 3 link reset" messages transmitted by the switch.

These are transmitted when the switch decides to reset and restart the

communication channel. This counter is meaningful only if there are no

Level 2 problems. If Level 2 is functioning correctly, non-zero values may

indicate that the adjunct is not responding to the messages in time,

causing the timers on the switch to expire.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-259status link

PROCESSOR/HOP

CHANNEL

STATUS

For each channel, the type of the channel (p for processor, h for hop), the

channel number (1-128), and the channel’s status is given as follows:

+ For hop channels, this indicates that connectivity is established

through this switch.

For processor channels, this indicates that the session level protocol

(which uses Level 3) is established, and application messages can

be transferred. Level 3 must be up for this to occur.

For the DCS gateway application

, a + does not mean that end-to-end

communication is established. The local SPE does not interpret

gateway data as it does data from other applications. Instead the

data is retransmitted over a TSC (temporary signaling connection)

carried on a PRI D-channel. Such a processor channel can be up

regardless of the status of the corresponding TSC. Messages

received by the gateway application for a TSC that is not established

are silently dropped.

— The SPE could not establish a connection to the specified channel

on the PGATE circuit pack. This is always the case when link Level

3 is not up. If Level 3 is up, check for errors on PGATE-BD,

PGATE-PT, or other related maintenance objects (SYSLINK,

PKT-INT or PKT-BUS). SYSLINK procedures should indicate

whether there are any other objects to check. Note that a hop

channel is associated with two links; “-” is displayed unless Level

3 is up on both links.

More information follows.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-260status link

The following display shows a typical result when status link 1 is entered.

PROCESSOR/HOP

CHANNEL

STATUS

(cont’d.)

* On a processor channel, Level 3 is established but the session Level

protocol is not. This will be the case immediately after Level 3 is

established on the link. The channel should come up (“+”) within 30

seconds. (This status is not valid for a hop channel).

If Level 3 is established on a link, and other channels on the link are up,

down channels may indicate:

■Port translations (local and remote port numbers) do not match. (For

each end, the local port specification must match the opposite end’s

remote port specification).

■Distant components of the channel’s logical connectivity may be

faulty. The down channel may hop to another channel at the far-end

switch, or at another, more distant, switch. If the link to which the

channel is hopped is down (at the far-end switch) the channel will not

come up. All links on the path between the two ultimate endpoints

must be up for the channel to come up. Therefore, this condition

could come and go because of actions taking place on a distant

machine.

If all sessions on the link are down, the following may be indicated:

■Either or both of the two problems mentioned above may be present

for each processor channel on the link.

■If all of the processor channels terminate on the same machine, (they

are not hopped elsewhere), there may be problems with the far-end

machine’s software. First busyout and release the link. If that fails,

restart the far end’s software.

status link 1 Page 1 of 1

LINK/PGATE PORT STATUS

Data Extension: 4011 Link Number: 1

Port Location: 01C0301 Link Id: audixA

Service State: in-service/active Link Status: in-service

Maintenance Busy? n Active Channels: 0

Connected To: 12C0308 PDMODULE Service State: in-service/active

AC: 1 Connected/Orig

ERROR COUNTERS

CRC Check (receive): 0

Invalid Frame (receive): 0 Information Frame (retransmit): 0

Level 2 link reset (receive): 0 Level 2 link reset (transmit): 0

Level 3 restart packet (receive): 0 Level 3 restart packet (transmit):0

PROCESSOR/HOP CHANNEL STATUS

P001+ H005+ H001+

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-261status logins

status logins

status logins [print]

This command will display information about all of the users that are currently

logged into the system. This information will contain their login names, location of

physical access, and their currently executing command.

The screen does not automatically update, and is a reflection of the system at the

time the request was made. Users may have logged off, or on, or the command

may have finished executing while the information is being displayed. These

updates will not be reflected until the next execution of the command.

The command will take a snapshot of the commands that the users on the system

are currently executing. Because of timing, the command could be terminated by

the time this command finishes displaying the list (i.e. the active command may

not be accurate).

status packet-interface

status packet-interface [print]

The status packet-interface command displays the status of all packet-interface

circuit packs in the system along with link information. The service state is

displayed for both active and standby packet-interface circuit packs. Link status

information including total, active and failed links are displayed for active

packet-interface circuit packs only.

If there are no standby packet interface circuit packs, or if the standby is

inaccessible (due to handshake failure, incomplete memory refresh, or locking of

the SPEs) the standby packet-interface circuit packs will be in the uninstalled

state.

When a packet-interface circuit pack is out-of-service or uninstalled, it is not used

to establish and maintain links. When the circuit pack returns to in-service status,

new links are again assigned to it.

For simplex SPE systems, information for only the A carrier packet-interface is

displayed. For duplicated SPE systems, if the standby is inaccessible because of

handshake failure or locking of carriers, the standby packet-interface circuit

packs will be in the uninstalled state.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-262status periodic-scheduled

Output

Separate columns identify each packet interface circuit pack slot. Service state is

displayed for both active and standby packet-interface circuit packs. Dashes in

output fields for the standby SPE indicate that link information is not applicable to

standby packet-interface circuit packs.

The following display shows a typical result when status packet-interface is

entered.

status periodic-scheduled

status periodic-scheduled [print]

Location The packet-interface cabinet, carrier and circuit pack position

number.

Service

State One of the following states is displayed: "in-service",

"out-of-service" or "uninstalled". The "standby" state is used in

place of "in-service" for standby packet-interface circuit packs.

Total links The total number of links.

Active

links The number of links that are in use.

Failed

links The number of links that failed to be established. These links

are in a recovery state and not active. The failures can arise

from problems in the packet-interface, EI or center stage

hardware. The number of failed links is the number of total

links minus the number of active links.

status packet-interface

PACKET INTERFACE STATUS

Location: 01A1 01A2 01A3

Service State: in-service uninstalled uninstalled

Total Links: 32 - -

Active Links: 32 - -

Failed Links: 0 - -

Location: 01B1 01B2 01B3

Service State: standby uninstalled uninstalled

Total Links: - - -

Active Links: - - -

Failed Links: - - -

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-263status periodic-scheduled

The status periodic-scheduled command displays summary information on

currently active and recently completed background testing. Periodic tests are

run every hour, and scheduled tests are run daily. Starting and stopping times,

and other parameters for daily scheduled testing are administered on the

change system parameters maintenance form.

Output

The following display shows a typical result when status periodic-scheduled is

entered.

Percentage

Complete The ratio of the number of maintenance objects tested to

the total number of maintenance objects tested during a

cycle. For periodic tests, the ratio is for the current cycle, if

active; or for the last completed cycle if not. For scheduled

tests, the ratio is for the last completed cycle.

System

Critical System critical resources are those whose health affects

the entire system such as the processor. These are always

tested first.

Shared

Resource Shared resources are those that are used by many users,

such as trunks. These are tested after system critical

resources.

Single User Single User resources are those whose health affects only

one user, such as voice stations.

Pre-

SCHEDULED

MAINTENANCE

The system can be administered to perform interchanges

of duplicated components and backup of data to disk

before daily scheduled maintenance begins. This is

pre-scheduled maintenance and is administered on the

change system-parameters maintenance form.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-264status pgate-port

status pgate-port

status pgate UUCSSpp [print]

The status pgate-port command displays the operational status of a a specified

Packet Gateway port. Such ports support the connection of X.25 adjunct

applications to the system. If the technician knows the X.25 link number

associated with the connection, but not the port number, then the “status link”

command may be used to access exactly the same information.

Adjunct Applications supported over X.25 connections include:

■AUDIX

■Calling Party Billing Number (CPN/BN or ISDN Gateway)

■CMS

■DCS

■Gateway Channels for DCS over ISDN-PRI

■Message Server

See

DEFINITY Communications System Generic 3 V2 Implementation,

555-230-653, for details. Status information provided by the command is

restricted to the switch hardware and extends no further than the Packet

Gateway circuit pack port.

status periodic-scheduled

MO Current Current Previous Cycle Rate of

Type Cycle % Cycle Duration Completed

Complete Active? (hr:min:sec Cycles

PERIODIC System Critical 80% y 00:00:48 1.0/hr

MAINTENANCE Shared Resource 100% n 00:00:43 1.0/hr

Single User 100% n 00:00:48 1.0/hr

Total 00:01:57

Start Time of Current or Previous Cycle: 11/19/13:34:36

Pre-SCHEDULED MAINTENANCE n 00:08:15

SCHEDULED System Critical 100% n 00:02:15 1.0/day

MAINTENANCE Shared Resource 100% n 00:03:16 1.0/day

Single User 100% n 00:20:05 1.0/day

Total 00:25:36

Start Time of Current or Previous Cycle: 11/18/22:00

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-265status pms-link

The screen output for this command is the same as that for the status link

command.

status pms-link

status pms-link [print]

The status pms-link command displays the status of the property management

system interface link. If the link is up, whether or not a data base swap is taking

place between the switch and PMS, will be shown. If the link is down, the number

of times the switch has tried to set up the link will be shown.

A property management system (PMS) is a stand alone computer system which

can be integrated with the switch to enhance the service capability for a

hotel/motel.

Output

The following display shows a typical result when status pms-link is entered.

status pnc

status pnc [print]

The status pnc command displays a summary of conditions on the active and

standby Port Network Connectivities. If the PNC is not duplicated, the screen

displays blanks in the PNC-B and other duplication-related fields.

Physical

Link State Up, down, or extension not administered will be displayed.

The PMS link is considered administered only if an extension

is given in the system hospitality form.

Protocol

State

Maintenance

Busy Whether there is any maintenance testing being performed

upon the link.

status pms-link

PMS LINK STATUS

Physical Link State: extension not administered

Protocol State:

Maintenance Busy?

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-266status pnc

Output

Most fields on this screen display blanks when the PNC is not duplicated.

In a duplicated system, each PNC has a separate entry for the following fields,

representing conditions for only that particular PNC.

Duplicated? Whether or not the system has a duplicated PNC (Critical

Reliability option).

Software

Locked? On a system with duplicated PNC, whether the PNCs are

locked by means of the set pnc lock or reset pnc

override-and-lock commands. When this field displays “yes”,

spontaneous or demand PNC interchanges are not possible. To

enable interchanges, use the set pnc unlock command.

Standby

Busied? On a system with duplicated PNC, whether or not the standby

PNC is busied out with the busy pnc command. Interchanges

are prevented when the standby is busied out.

Direct

Connect? Whether the system uses direct-connect connectivity or a

center stage switch.

Standby

Refreshed? On a duplicated system, this field indicates whether the

standby PNC has completed a global refresh of duplicated call

setup after being released from a busyout, or after a system

reset.

NOTE:

This field does not indicate if a partial unrefresh has taken

place in response to a problem on the standby. Only a

“functional” state of health on the standby (all zeros in the

state of health vector) guarantees that the standby’s call

setup matches completely that of the active.

Interchange

Disabled? This field displays “yes” when the anti-thrashing mechanism is

in effect, preventing PNC interchanges. This is the case for 5

minutes after a spontaneous PNC interchange, and for 30

seconds after a demand interchange. The reset pnc

interchange override-and-lock command overrides

antithrashing. This field does not indicate whether a PNC

interchange is currently prevented by a software lock, by

insufficient state of health of the standby, or by busyout of the

standby.

Mode This field displays "active" or "standby", depending on whether or

not that PNC controls active call processing.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-267status pnc

State of

Health On a system with duplicated PNC, the state of health of each

PNC. For the standby PNC, service effects mentioned below are

those that would occur if that PNC were to become active via an

interchange.

Functional: the indicated PNC has no service disrupting alarms

against it. The state of health vector is all zeros, and call setup on

the standby PNC matches that of the active.

Partially functional: the health of the PNC is less than perfect. The

source and severity of the problem is indicated by the state of

health vector (Inter-PN and Inter-SN Indexes). Whenever the

standby’s state of health is partially functional, duplicated call

setup on the standby probably does not match that on the active.

Not functional: Expansion Archangel Links to all EPNs are down

on this PNC. No service is possible to any EPNs via this PNC.

Inter PN

Index,

Inter SN

Index

The Inter-PN and Inter-SN Indexes form the state of health vector,

which is used to track and compare the states of health of both

PNCs. The fields making up the indexes are two digit numbers

separated by periods (.), with each field representing a different

class of faults. The fault class fields are arranged in order of

decreasing importance from left to right. In other words, each

field in the index supersedes the following fields in determining

which PNC is healthiest. The Inter-PN Index contains five fields

(XX.XX.XX.XX.XX), and the Inter-SN Index has two (XX.XX). The

Inter-PN Index reports faults in connectivity between port

networks and supersedes the Inter-SN Index, which reports faults

in connectivity between switch nodes. (The Inter-SN Index is only

meaningful for systems with a center stage switch having 2

switch nodes, each of which is duplicated).

The meaning of each fault class field is given in Table 8-13

below. A zero entry indicates that there are no such faults

reported. Higher numbers indicate increasing number of faults.

All zeros indicates perfect state of health. Unless the PNCs are

locked, the active PNC’s state of health should always be equal

to or better than the standby’s. (Otherwise, the system would

perform a spontaneous interchange.)

After a PNC-related alarm is cleared, the system performs a

partial refresh of the standby PNC. The corresponding fault class

field is not updated to reflect the improved state of health until the

refresh is done. The state of health indexes will not agree with the

current alarm status during this period.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-268status pnc

Table 8-13. Fault Class Field Descriptions

Fault Class Priority Description MOs

FC_EAL 1 Number of PNs with EALs down EXP-PN

FC_INL 2 Number of PNs with LINL, RINL, or EI-SNI

neighbor link faults EXP-PN

SN-CONF

FC_HW 3 Number of PNs affected by hardware faults in

a link having an EI as an endpoint (Endpoints

can be determined with list fiber-link.)

EXP-INTF

SN-CONF

FIBER-LK

SNI-BD

DS1C-BD

FC_PER 4 Number of PNs affected by SNI peer link faults

for SNIs connected to EIs SNI-PEER

FC_DS1 5 Number of PNs affected by DS1C facility faults DS1FAC

FC_SNIL 6 Number of inter-switch-node fibers affected by

peer or neighbor link faults SNI-PEER

FC_SNIHW 7 Number of inter-switch-node fibers affected by

hardware faults SN-CONF

SNI-BD

FIBER-LK

Major Alarms,

Minor Alarms,

Warning Alarms

The number of major, minor, or warning alarms logged

against DS1C-BD, SNI-BD, SNC-BD, EXP-INTF, FIBER-LK,

DS1C-FAC, SNC-LINK, SN-CONF, SNC-REF, SYNCH, and

SNI-PEER on the indicated PNC.

Switch Node

Locations The locations of all Switch Nodes comprising the indicated

PNC.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-269status port-network

The following display shows a typical result when status pnc is entered on a

system with a single switch node CSS and duplicated PNC.

status port-network

status port-network [PN#] [print]

This command displays the operational status and attributes of the user

specified Port Network and several of its key components, including expansion

interface circuit pack(s), TDM busses, tone-clock circuit packs, and the packet

bus.

Blank will be displayed for tdm bus, tone-clock and packet bus fields if the link to

the EPN is down or if that information is otherwise unavailable.

Port network number defaults to 1.

If the Expansion Archangel Link to the specified Port Network is not available,

tdm bus, tone clock, and packet bus fields will be blank.

status pnc

PORT NETWORK CONNECTIVITY

Duplicated? yes

Software Locked? no

Standby Busied? no

Direct Connect? no

Standby Refreshed? yes

Interchange Disabled? no

A-PNC B-PNC

Mode: active Mode: standby

State of Health: functional State of Health: functional

Inter PN Index: 00.00.00.00.00 Inter PN Index: 00.00.00.00.00

Inter SN Index: 00.00 Inter SN Index: 00.00

Major Alarms: 0 Major Alarms: 0

Minor Alarms: 0 Minor Alarms: 0

Warning Alarms: 0 Warning Alarms: 0

SN Locations: 01E SN Locations: 01D

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-270status port-network

Output

PN The Port Network number associated with the Port Network for which

status is being displayed.

Major

Alarms The number of major alarms logged against the Port Network that is

being displayed.

Minor

Alarms The number of minor alarms logged against the Port Network that is

being displayed.

Warning

Alarms The number of warning alarms logged against the Port Network that is

being displayed.

Carrier

Locs The cabinet and carrier locations of each carrier in the Port Network.

PNC Status Active (and Standby if PNC is duplicated) Port Network Connectivity

(PNC) status for the specified port network is displayed. The PNC Status

of a port network is determined by the availability of the Expansion

Archangel Link (EAL) and Indirect Neighbor Link (INL) to the port

network. A status of "up" denotes that the EAL and INL are both available.

A status of "down" is displayed when the EAL and INL are both

unavailable. When the EAL is available, but the INL is unavailable, a

status of "near-end" is displayed. A status of "far-end" is displayed when

the INL is available and the EAL is unavailable. When the EAL is

unavailable (far-end), tone clock, tdm bus, and packet bus information

will be blank.

FIBER-LINK This field displays the fiber-link number associated with all fiber links

having an Expansion Interface circuit pack endpoint residing in the

specified Port Network. The fiber connectivity side will also be displayed

(i.e. "A-PNC" or "B-PNC").

Endpoints The physical position of each Expansion Interface board that is an

endpoint for a fiber link in the specified Port Network is displayed as

“UUcSS.” “UU” represents the cabinet number, “c” represents the

carrier, and “SS” represents the slot position. The simplex PNC

configuration will display only one Expansion Interface pair, while the

duplex PNC configuration will display two Expansion Interface pairs

separated by a hyphen (-). If blanks are displayed it means the endpoints

could not be retrieved by software.

Mode The mode is the current role of the link. A mode of "active" means the link

is providing normal circuit and control functions for the Port Network. A

mode of "standby" means the link is part of a duplicated system and is

ready to perform its functions but is not active. If blanks are displayed it

means that PNC is not duplicated, or the mode could not be retrieved

from software.

TDM Bus The TDM bus identifier associated with the Port Network is displayed.

The TDM bus ("a" or "b") specifies which half of the TDM bus is being

displayed.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-271status port-network

Service

State The operational state of the TDM bus. A TDM bus service state of "in"

means the bus is in normal operation. A TDM bus service state of "out"

means the bus has failed certain maintenance tests and has been taken

out of service, or the maintenance object has been demand busied out.

Control

Channel This field shows whether the TDM bus has the control channel on it

(“y”/”n”). Only one TDM bus of a TDM bus pair on each Port Network can

have the control channel on it at a given time. If the system does not

contain an EPN, blanks appear in this field.

Dedicated

Tones This field shows whether the TDM bus has the system tones on it

(“y”/”n”). Only one TDM bus of a TDM bus pair can have system tones on

it at a given time. If the system does not contain an EPN, blanks appear

in this field.

TONE/CLOCK The location of the tone-clock circuit packs in the specified Port Network.

The location is represented using the cabinet and carrier where the

tone-clock resides (e.g. 1a, 1b, 2a, 2b, etc.).

Service

State This field represents the operational state of the tone-clock circuit pack.

A service state of "in" means the tone-clock has been installed and is in

normal operation. A service state of "out" means that the tone-clock is out

of service and has failed certain maintenance tests.

System

Clock This field shows which tone-clock circuit pack supplies the system clock

for that port network by displaying the mode of the tone-clock. An

“active” mode means that the tone-clock supplies the system clock. Only

one tone-clock in each Port Network can have a mode of “active” at any

given time. A “standby” mode means the tone-clock is part of a

duplicated clock system and is ready to supply the system clock, but is

not currently “active.” A “down” mode means the tone-clock is not

operational.

System

Tones This field shows which tone-clock circuit pack supplies the system tones

for that port network by displaying the mode of the tone-clock. An

“active” mode means that the tone-clock supplies the system tones. Only

one tone-clock in each Port Network can have a mode of “active” at any

given time. A “standby” mode means the tone-clock is part of a

duplicated clock system and is ready to supply system tones, but is not

currently “active.” A “down” mode means the tone-clock is not

operational.

PKT This field contains the Packet Bus identifier, which is the same as the Port

Network number.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-272status port-network

Service

State This field represents the operational state of the packet bus. A service

state of “in” means the packet bus has been installed and is in normal

operation. A service state of “out” means that the packet bus is out of

service and has failed certain maintenance tests, or the maintenance

object has been demand busied out. A service state of “reconfig” means

that the Maintenance/Test circuit pack has swapped one or more signal

leads because of lead faults detected during testing (Duplex System

Only). A service state of “open lds” means the Maintenance/Test circuit

pack query was run and open bus leads were found. A service state of

Blanks in this field means the system does not have the Packet Bus

feature optioned.

Major

Alarms Whether major alarms are logged against the packet bus that is being

displayed ("y" or "n").

Minor

Alarms Whether minor alarms are logged against the packet bus that is being

displayed ("y" or "n").

Bus Faults This field indicates the number of faulty bus leads, where a fault is

defined as either shorted to another lead or stuck at some value. This

field may take on any integer value between 0 and 24. The field contains

a blank if the Maintenance/Test circuit pack is not present or has been

taken out of service.

Open Bus

Leads This field indicates the number of bus leads that have an open circuit

between the Maintenance/Test circuit pack and bus terminator. This

information is determined by testing performed on the bus leads; bus

leads test open as a result of physical damage to the backplane or the

backplane’s connectors, or because a bus terminator is missing. This

field may contain integer values between 0 and 24. This field contains a

blank if the Maintenance/Test circuit pack is not present or has been

taken out of service.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-273status processor-channel

The following display shows a typical result when status port-network 2 is

entered.

status processor-channel

status processor-channel channel# [print]

The status processor-channel command displays the status of the specified

processor channel and the values of its various counters. A processor channel is

one of 128 logical channels associated with an SCI link. Each processor channel

terminates in the switch processing element with a session.

status port-network 2

PORT NETWORK STATUS

Major Minor Warning Carrier PNC Status FIBER-

PN Alarms Alarms Alarms Locs Active Standby LINK Endpoints Mode

2 1 4 2 02A up up 2 A-PNC 02A01-01E03 active

02B 2 B-PNC 02B01-01D03 standby

02C

02D

TDM Service Control Dedicated TONE/ Service System System

Bus State Channel Tones CLOCK State Clock Tones

A In y n 02A In Active Active

B In n y 02B Out Standby Standby

Service Major Minor Bus Open Bus

PKT State Alarms Alarms Faults Leads

2 out n n 0 0

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-274status signaling-group

Parameters

Output

The following display shows a typical result when status processor-channels 1

is entered.

status signaling-group

status signaling-group group# [print]

This command displays the service state, type, port location, and of the primary

and secondary D-Channels within an ISDN-PRI signaling group. A signaling

group is a set of B-channels signaled for by a designated single D-channel or

combination of D-channels.

channel number The processor channel number (1-128).

Channel Number The processor channel number 1-128.

Channel Status The state that the channel is in: 1-16. The following

describes the various channel states:

Reset Count The number of times that the reset has been issued for

this channel.

Message Buffer

Number The number of message buffers currently allocated for

communications on this channel.

Link Number The physical BX.25 interface link, 1-16, associated with

the channel.

Retransmission

Count The number of times that message retransmission has

occurred.

status processor-channels 1

PROCESSOR CHANNEL STATUS

Channel Number: 1

Channel Status: 11: Administered but not connected

Reset Count: 0

Message Buffer Number: 0

Link Number: 3

Retransmission Count: 0

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-275status signaling-group

Parameters

Output

The following information is given for both primary and secondary D-channels, if

any.

group# An administered number associated with each signaling group.

Group ID: An administered number from 1 to 666 that identifies the signaling

group.

Type: See “ISDN-SGR (ISDN-PRI Signaling Group)” in Chapter 9 for

more information about group types.

facility All members are carried on a single DS-1 associated

facility. Facility-associated signaling groups support only

simplex D-channel configuration.

non-facility Members can include trunks on several different

associated DS-1 facilities. The DS-1 facility is identified

signaling across the ISDN-PRI using an explicit facility

identifier. A single D-channel on one of the facilities is used to

signal for all members. In a duplex configuration, a second

D-channel is assigned to act as a backup in case the primary

signaling channel fails.

Group

State: The operational state of D-channel providing signaling for the

group: in-service or out-of-service. In duplex

configurations, this field displays in-service if either D-channel

is functioning.

Link: The number of the link carrying the D-channel.

Port: The location of the port carrying the D-channel.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-276status signaling-group

The following display shows a typical result when status signaling-group 1 is

entered.

Level 3

State: The operational state of the primary and secondary D-channels:

in-service The D-channel is functioning.

standby the link is established but the D-channel is not

currently being used for layer 3 signaling.

wait This is a transitional state in the process of progressing to

the in-service state. The switch has sent an ISDN SERVICE

message requesting establishment of layer 3 communications,

and is awaiting a SERVICE ACKNOWLEDGE message from the

far end to put the D-channel into service.

maintenance busy The D-channel is no longer in the

multiple-frame-established state at layer 2. When an active

D-channel in a duplex signaling group fails, it is placed into this

state and an interchange to the standby D-channel takes place.

When layer 3 signaling is re-established over the new

D-channel, the failed D-channel is moved from this state to

out-of-service and restarted. If the link is successfully

re-established, it is put into the standby state.

manual-out-of-service The link carrying the D-channel has

been busied-out by command.

out-of-service The D-channel is down.

no-link A link has not been administered for this D-channel on

the signaling-group form.

status signaling-group 1 Page 1 of 1 SPE A

STATUS SIGNALING-GROUP

Group ID: 1

Type: facility associated signaling

Group State: in-service

Primary D-Channel

Link: 1 Port: 01C1924 Level 3 State: in-service

Secondary D-Channel

Link: Port: Level 3 State:

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-277status spe

status spe

status spe [print]

The status spe command displays a page of output summarizing the condition of

the active and standby (if the system is duplicated) SPE(s) in the system. If the

SPEs are not duplicated, the fields in the standby SPE column will be blank.

Output

Duplicated? This field specifies whether the system is a duplex SPE system ("yes" or

"no").

SPE

Selected: If the system is a duplex SPE system, this field displays which SPE is

locked active by the position of the duplication interface circuit pack

Select-switches. If "spe a locked active" is displayed, then the SPE in

cabinet 1 and carrier A has been locked active (both duplication

interface circuit pack switches are switched left). If "spe b locked active"

is displayed, then the SPE in cabinet 1 and carrier B has been locked

active (both duplication interface circuit pack switches are switched

right). If "auto" is displayed, it means the switches are in any other

combination of positions besides both left or both right. If blanks are

displayed, the system is not a duplex SPE system (there are no

duplication interface boards).

Standby

Busied? This field specifies whether the standby SPE is busied out ("yes" or "no").

Blanks are displayed if the system is not a duplex SPE system.

Standby

Refreshed? This field specifies whether the standby SPE’s memory has been

completely refreshed ("yes" or "no"). Blanks are displayed if the system is

not a duplex SPE system.

Standby

Shadowing: This field specifies whether the standby SPE’s memory is currently being

updated when changes are made to the active SPE’s memory ("on" or

"off"). Blanks are displayed if the system is not a duplex SPE system.

Standby

Handshake: This field specifies whether the software running on the standby SPE’s

duplication interface board is communicating to the software on the

active SPE’s duplication interface board ("up" or "down"). Blanks are

displayed if the system is not a duplex SPE system.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-278status spe

Recent

Spontaneous

Interchange?

This field specifies whether a spontaneous interchange has occurred

within the last hour. If this field displays “yes,” a spontaneous

interchanges has occurred within the last hour. If the field displays “no” a

spontaneous interchange has not occurred within the last hour, or a

technician has purposely reset this field in the software. Immediately

following a spontaneous interchange, the field is set to “yes.” While the

field displays “yes,” the health of the standby SPE can never be better

than “partially functional,” and an interchange can not occur unless the

health of the active SPE drops below “partially functional.” Recent

interchange mode can be cleared by either test spe-standby long or

busyout spe-standby. This condition clears automatically one hour after

the interchange occurred.

This field will be blank in a simplex SPE system.

Mode: The mode is the current role of the SPE. "active" indicates that this SPE

is controlling the network and providing services for the system.

standby indicates that this SPE is part of a duplicated system and is not

currently active. Blanks indicate that the system has a simplex SPE.

Select

Switch: This field shows the position of the SPE Select-switch on the duplication

interface circuit pack. The Select-switch can be in three different

positions. A position of "spe a" means the switch is switched left. A

position of "spe b" means the switch is switched right. A position of "auto"

means the switch is in the center position. "unavail" means the

duplication interface circuit pack has been removed (the board has been

unseated). Blanks mean that the system is not duplicated and there is no

Select-switch due to there being no duplication interface boards.

Major

Alarms: The number of major alarms logged against the SPE are displayed in this

field. Blanks in the standby fields mean that the system is not duplicated

and a standby SPE does not exist. The category spe may be entered on

the display alarms or display errors forms to view all alarms or errors

logged against SPE maintenance objects.

Minor

Alarms: The number of minor alarms logged against the SPE are displayed in this

field. Blanks in the standby side mean that the system is not duplicated

and a standby SPE does not exist. The category spe may be entered on

the display alarms or display errors forms to view all alarms or errors

logged against SPE maintenance objects.

Warning

Alarms: The number of warning alarms logged against the SPE are displayed in

this field. Blanks in the standby side mean that the system is not

duplicated and a standby SPE does not exist. The category spe may be

entered on the display alarms or display errors forms to view all alarms

or errors logged against SPE maintenance objects.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-279status spe

State of

Health: On a duplicated SPE system, these fields each display one of the

following states of health for each SPE: "functional," "partially functional,"

"not refreshed," or "not functional". If the system has a simplex SPE, the

state of health fields for both the active and the standby SPEs will display

nothing. A health of "functional" means that the SPE has no service

disrupting alarms. A health of "partially functional" means that the health

of the SPE has been degraded (possibly service disrupting). A health of

"not functional" means that the associated SPE is not cycling at all (no

service). A health of "not refreshed" means that the standby SPE’s

memory has not been refreshed with the active SPE’s memory, but it is

otherwise healthy and cycling correctly.

Tape State: This field represents the operational state of the tape device. A service

state of "in-service" means the tape has been installed and is in normal

operation. A service state of "out-of-service" means that the tape is out of

service and has failed certain maintenance tests. A state of

"maintenance-busy" means the tape is busied out. Blanks mean the tape

device is not installed or the system has a simplex SPE.

Disk

Present? If a disk device resides on the SPE this field will display "yes," otherwise,

the field will display "no." A blank in the SPE-B side indicates the system

has a simplex SPE.

Disk State: This field represents the operational state of the disk device. A service

state of "in-service" means the disk has been installed and is in normal

operation. A service state of "out-of-service" means that the disk is out of

service and has failed certain maintenance tests. A state of

"maintenance-busy" means the disk is busied out. Blanks are displayed

on the SPE-B side when the system is not duplicated.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-280status sp-link

The following display shows a typical result when status spe is entered on a

duplicated system

status sp-link

status sp-link [print]

This command displays a summary of the operational state of the system printer

link.

status spe page 1 of 1

PROCESSOR COMPLEX

Duplicated? yes

SPE Selected: auto

Standby Busied? no

Standby Refreshed? yes

Standby Shadowing: on

Standby Handshake: up

Recent Spontaneous Interchange? no

SPE-A SPE-B

Mode: active Mode: standby

Select Switch: auto Select Switch: auto

Major Alarms: 0 Major Alarms: 0

Minor Alarms: 0 Minor Alarms: 0

Warning Alarms: 0 Warning Alarms: 0

State of Health: functional State of Health: functional

Tape State: in-service Tape State: in-service

Disk Present? yes Disk Present? yes

Disk State: in-service Disk State: in-service

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-281status station

Output

The following display shows a typical result when status sp-link is entered.

status station

status station extension [print]

The status station command displays internal software state information for

diagnosis. This command can help locate facilities to which the station is

communicating.

Output

Link State: The operational state of the link:

up A call is currently set up to the system printer.

down The link is administered but a call is not currently set up

to the printer.

extension not administered An extension has not

been administered for the system printer on the

features-related system parameters form.

Number of

Retries: The number of times the switch has tried to establish the link

since a request to set it up has been received. This field is

displayed only when the link is down. The maximum value

displayed is 999.

Maintenance

Busy? Whether maintenance testing is being performed on the

system printer link. A blank is displayed if the system printer

link is not administered.

Type The type of equipment administered for the extension.

Extension The extension number specified on the command line.

Port The location of the port assigned to the station.

status sp-link SPE A

SYSTEM PRINTER LINK STATUS

Link State: down

Number of Retries: 0

Maintenance Busy? no

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-282status station

Call Park Whether the station has a call parked.

Ring Cut Off

Activated Whether ring cut-off is activated.

Destination

Ext

The extension of the call forwarding destination.

Message

Waiting The location of any active messages for the station:

AUDIX, PMS or AP-SPE. The field is blank if no

messages are waiting.

Connected

Ports Locations of ports currently connected to the station.

Agent Logged

In Numbers of hunt groups that the agent is currently

logged into. A maximum of three groups is displayed.

On ACD Call? Whether the agent is currently on an ACD call.

Work Mode Work mode of each hunt group that an agent is logged

into.

Service State The service stat of the station: in-service/on-hook,

in-service/off-hook, out-of-service, or disconnected.

Maintenance

Busy? Whether maintenance is currently testing the object.

SAC Activated Whether send-all-calls is activated.

User Cntrl

Restr Which, if any, restrictions are placed on the individual

terminal:

total The station cannot originate or receive calls.

stat-stat The station cannot originate or receive calls

to other stations.

outward The station cannot originate calls to the public

network.

terminate The station cannot receive calls.

none

Group Cntrl

Restr Whether the station is restricted as part of a restricted

group. Values are the same as for the above field, User

Cntrl Restr.

AWU Call at If an automatic wakeup call is scheduled, this field

displays the time scheduled for the call.

DND Status of the do not disturb feature.

Room Status Whether a room is occupied, vacant, or a non-guest

room.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-283status switch-node

The following display shows a typical result when status station 1002 is entered.

status switch-node

status switch-node SN# [print]

This command displays the operational status and attributes of the user

specified switch node. The operational status of the active and standby switch

node Clock(SNC) circuit packs for the switch node are displayed along with any

alarms logged against the specified switch node.

Parameters

Output

A line of information is displayed for each switch node carrier.

SN number Normally switch node 1 is located in the PPN cabinet, and switch

node 2, if present, is located in the nearest EPN cabinet. The

switch node number defaults to 1.

Switch Node The switch node number, 1 or 2. If the PNC is duplicated, the A

and B PNCs are each reported separately.

status station 1002

GENERAL STATUS

Type: 7405D Service State: in-service/on-hook

Extension: 1002 Maintenance Busy? no

Port: 01C0702 SAC Activated? no

Call Parked? no User Cntrl Restr: none

Ring Cut Off Act? no Group Cntrl Restr: none

CF Destination Ext:

Message Waiting:

Connected Ports:

ACD STATUS HOSPITALITY STATUS

Agent Logged In Work Mode AWU Call At:

DND: not activated

Room Status: non-guest room

On ACD Call? no

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-284status switch-node

The following display shows a typical result when status switch-node is entered.

Location The physical position of the switch node carrier represented as

"UUc". Where "UU" represents the cabinet number and "c"

represents the carrier. The simplex PNC configuration will

display only one switch node location, while the duplex PNC

configuration will display the active and standby switch node

locations.

Mode The mode is the current role of the switch node carrier. A mode

of "active" means the SN is providing normal circuit and control

functions for PNC. A mode of "standby" means the SN is ready

to become active, but is currently not active. If blanks are

displayed it means that PNC is not duplicated.

Major

Alarms The number of major alarms logged against the switch node

carrier that is being displayed.

Minor

Alarms The number of minor alarms logged against the switch node

carrier that is being displayed.

Warning

Alarms The number of warning alarms logged against the switch node

carrier that is being displayed.

Active SNC

Location The physical position of the active switch node Clock circuit

pack, per administration, represented as "UUcSS." "UU"

represents the cabinet number, "c" represents the carrier, and

"SS" represents the slot position. If an SNC is administered but

not inserted, "no board" will be displayed.

Standby

SNC

Location

The physical position of the standby switch node Clock circuit

pack, per administration, represented as "UUcSS." "UU"

represents the cabinet number, "c" represents the carrier, and

"SS" represents the slot position. Blanks will be displayed if

there is no standby switch node Clock for a given switch node.

If an SNC is administered but not inserted, "no board" will be

displayed.

status switch-node 1 page 1 of 1

switch node STATUS

Major Minor Warning Active SNC Standby SNC

Switch Node Location Mode Alarms Alarms Alarms Location Location

1 A-PNC 01E active 0 0 0 01E10 01E12

1 B-PNC 01D standby 0 1 2 01D10 01D12

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-285status sys-link

status sys-link

status sys-link UUCSSpp [ channel channel# ] [print]

The status sys-link command displays status data for a specified system link. The

report includes the type and operational state of the link, the associated

processor channel, if any, active alarms and path status, and a list of all

hardware components making up the link’s path. If in addition to the current path

a faulted path exists, the components making up the faulted path are displayed

on page 2 of the report.

Parameters

Examples

status sys-link 1e0201

status sys-link 1c17 channel 2

Output

UUCSSpp The link is specified by giving the location of the port associated with

the link.

channel# If the link is an X.25 link (to an adjunct or another switch), you must

specify a processor channel number (1-128) associated with the link.

Location The location of the port associated with the system link

(cabinet-carrier-slot-circuit).

Type/Chan The type of system-link and the channel number of the link (for

X.25 links) as follows:

EALExpansion Archangel Link

INLIndirect Neighbor Link (Center Stage Switch)

PGCPacket Gateway Call-Control Link

PRIISDN-PRI signaling Link

SAPSystem Access Port Link

X25X.25 Link to an adjunct or DCS

Alarms The highest level of alarm currently logged against the

components making up the link.

Current

Path The operational status of the current path:

noneThe link is down.

presentThe current path displayed below is valid.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-286status sys-link

The following display shows a typical result when status sys-link 2a0101 is

entered. In the following case, the link encountered a fault and recovered by

switching to a different inter-switch-node fiber.

Faulted

Path The status of the faulted path, if any:

presentThe path of the link has been faulted at least once.

noneThere is no record of the link having gone down.

defaultThe default faulted path is being used.

Last Fault The date and time at which the most recent fault occurred.

State Whether the system link is "up" or "down."

Current

Hardware

Path

The location, maintenance name, and alarm information for

each hardware component making up the current path of the

link. The path begins at the Packet Interface in the SPE and

terminates at the circuit path that terminates the other end of the

link.

Faulted

Hardware

Path

If the link encounters a fault, the system will reroute it if possible

over an alternate route. If this has taken place, the faulted path

is displayed on page 2 of the report. The location, maintenance

name, and alarm information for each hardware component

making up the most recent faulted path is shown.

status sys-link 2a0101 Page 1 of 2 SPE A

Location: 02A0101 Type/Chan: EAL Alarms: none

Current Path: present Faulted Path: present Last Fault: 12/30/1991 14:18

State: up

Current Hardware Path

Maintenance Maintenance

Location Name Alarms Location Name Alarms

01A1 PKT-INT none

PN 01 PKT-BUS none

01E01 EXP-INTF none

1 A-PNC FIBER-LK none

01E02 SNI-BD none

01E09 SNI-BD none

7 A-PNC FIBER-LK none

02E09 SNI-BD none

02E02 SNI-BD none

2 A-PNC FIBER-LK none

02A01 EXP-INTF none

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-287status trunk

status trunk

status trunk group# [/ member#] [print]

The status trunk command displays information about the operational status of a

single trunk or of all members of a trunk group. You can also use it to locate

facilities with which the trunk is communicating.

The monitor trunk command displays the same information and updates the

screen automatically every minute or on demand.

Parameters

group#/member# If you enter a trunk group number without a member number,

then information for all members of that group is displayed as

shown in the second screen shown below. If you enter a trunk

group and a member number separated by a slash (/), then

information for only that member, including some additional

fields, is displayed as shown in the first screen shown below. If

you enter a group number followed by only a slash (/), then the

system defaults to member number 1 and displays the member

report.

status sys-link 2a0101 Page 2 of 2 SPE A

Location: 02A0101 Type/Chan: EAL Alarms: none

Current Path: present Faulted Path: present Last Fault: 12/30/1991 14:18

State: up

Faulted Hardware Path

Maintenance Maintenance

Location Name Alarms Location Name Alarms

01A1 PKT-INT none

PN 01 PKT-BUS none

01E01 EXP-INTF none

1 A-PNC FIBER-LK none

01E02 SNI-BD none

01E13 SNI-BD none

6 A-PNC FIBER-LK none

02E13 SNI-BD none

02E02 SNI-BD none

2 A-PNC FIBER-LK none

02A01 EXP-INTF none

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-288status trunk

Examples

status trunk 78

status trunk 80/2 print

Output

The following display shows a typical result when status trunk 20/1 is entered.

Trunk

Group/Member Group and member numbers of specified trunks.

Port The location of the port associated with the trunk.

Signaling

Group ID For ISDN trunks, the number of the signaling group to which the

trunk group belongs. For other trunk types, the field is blank.

Connected

Ports Locations of ports currently connected to the trunk.

Service

State One of the following states is displayed: in-service/active,

in-service/idle, out-of-service, out-of-service-NE (Near End),

out-of-service-FE (Far End), maint-NE/active, maint-FE/active,

maint-NE/idle, maint-FE/idle, pending-in-service, pending-maint,

or disconnected. NE (Near End) and FE (Far End) refer to which

end of the trunk has placed the facility in its current state.

Explanations of these service states for each type of trunk appear

in the maintenance object descriptions in Chapter 9, ‘‘ABRI-PORT

(ASAI ISDN-BRI Port)’’.

Maintenance

Busy Whether maintenance testing is currently being performed upon

the trunk.

CA-TSC State The status of the call-associated temporary signaling connection,

if any. A TSC is a temporary connection set up to pass call

information over ISDN-PRI signaling links.

status trunk 20/1

TRUNK STATUS

Trunk Group/Member: 020/001 Service State: in-service/idle

Port: 01D0801 Maintenance Busy? no

Signaling Group ID: 1 CA-TSC State: none

Connected Ports:

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-289status tsc-administered

The following display shows a typical result when status trunk 1 is entered for a

trunk group with two members.

status tsc-administered

status tsc-administered signaling-group# [ /tsc-index] [print]

This command displays the operational status of temporary signaling

connections (TSCs) administered for a specified signaling group.

Examples

status tsc-administered 1

status tsc-administered 1/2 print

Parameters

Output

signaling-group# An administered number associated with each signaling group.

tsc-index A number associated with each TSC in a signaling group.

TSC Index The administered TSC index (1-759).

TSC State A state of "inactive" means that the administered TSC is not

functioning (i.e. D-Channel out-of-service, or disabled, etc.). A state

of "active" indicates that the administered TSC is up and user

information can be exchanged end-to-end. A state of

"pending-inactive" shows that the TSC is being released. A state of

"pending-active" means that the TSC is about to come up.

status trunk 1

TRUNK GROUP STATUS

Member Port Service State Mtce Busy Connectd Ports

01/01 01A0101 in-service/idle no 01A0501 02B0607

01/02 04A0702 in-service/idle no 04C0604

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-290status tti

following display shows a typical result when status tsc-administered 1/1 is

entered.

status tti

status tti [print]

This command displays the operational status of the Terminal Translation

Initialization (TTI) background maintenance task. The TTI Background

maintenance task is activated by enabling the TTI feature on the

system-parameters features administration form. See

DEFINITY Communications

System Generic 3 V2 Implementation,

555-230-653.

Establish This field pertains to the switch responsible for the origination of the

administered TSC. A state of "as-needed" shows that the TSC is

established on an as needed basis. A state of "permanent" shows

that the TSC is permanently established.

Enabled “Y” indicates that the administered TSCs have been enabled.

Congested A congested state indicates that the network cannot handle the

receipt of USER INFORMATION messages for the administered

TSC. "Yes" indicates that the administered TSC is congested. "No"

indicates that the administered TSC is not congested. "Clear"

indicates that TSC was congested during its active period and the

congestion has been cleared.

status tsc-administered 1/1

ADMINISTERED NON-CALL-ASSOCIATED TSC STATUS

TSC TSC

Index State Establish Enabled Congested

1 inactive as-needed yes no

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-291status tti

Output

TTI

Background

Task State:

One of the following:

generating TTI ports

removing TTI ports

suspended

not active

completed - all ports translated

The last execution of the background task completed normally.

completed - some ports not trans

The task completed due to resource exhaustion with some ports left

untranslated.

TTI State: offThe TTI feature is not enabled.

voice, dataThe type of TTI ports that are being generated or removed

# of Boards

Completed: Number of TTI-supported circuit packs that have been processed by the

background maintenance task.

A “completed” circuit pack has either had all its unadministered ports

translated as TTI ports or its TTI ports have been removed and are now

unadministered ports.

# of Boards

Left to

Process:

Number of TTI-supported circuit packs that have not yet been processed

by the background maintenance task.

Percent

Complete: A ratio of the of number of circuit packs completed to the total number.

Elapsed

Time Since

Task

Started:

Elapsed time in hours:minutes:seconds since the TTI background task

was started.

This field is blank if the task is not active. If the task is completed or

suspended, this field displays the elapsed time up to when the job

finished or was suspended.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-292test alarms

The following display shows a typical result when status tti is entered.

test alarms

This command tests the hardware associated with selected alarms

Synopsis

test alarms

auto-page failures step [short | long][repeat number | clear]

Permissions

The following default logins may execute this command: system technician,

inads, init, nms.

Examples

test alarms

test alarms step failures

test alarms long clear auto-page

test alarms long failures

Description

This command allows the technician to automatically test all of the hardware that

is associated with the active alarms in the alarm log. This command provides a

query form to help the user narrow the selection of alarmed objects. Once the

form is filled out, the user presses ENTER and the hardware associated with the

selected alarm log entries is tested. The results will be displayed in standard test

output and status information will be displayed on the message line as the

command progresses.

Several alarms may be logged against a single maintenance object, each alarm

representing a different problem. Even if there are multiple entries in the alarm

status tti

TTI STATUS

TTI Background Task State: completed - all ports translated

TTI State: voice

# of Boards Completed: 30

# of Boards Left to Process: 0

Percent Complete: 100

Elapsed Time since Task Started: 0 :0 :1

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-293test alarms

log for a single object, the test alarms command will only test each physical

object once.

Defaults

The default options for this command are: short, repeat of 1.

Parameters

auto-page This option provides the ability to continue testing and

displaying test results, by providing a new screen every time

the SAT screen is filled with test results. The screen does not

scroll to accommodate new results; instead a new screen is

provided after the current screen fills up.

If the auto-page option is not specified, the SAT screen will not

be refreshed once it is filled with test results and testing will

stop until the user enters the "PAGE" key to continue or the

"CANCEL" key to halt the testing.

failures This requests that only the failures be displayed on the screen.

All passes will not be displayed on the output screen.

Hardware failures as well as aborts, conflicts and EPN-down

failures will be displayed.

step This option will allow the user to step to the next or previous

alarm and not have the current alarm tested. When this option

is specified, the user is presented with the alarm information

and prompted for a keypress. The user may enter CANCEL to

abort the command, ENTER to test the currently displayed

alarm, NEXT ALARM (function key) to move to the next alarm,

PREV ALARM (function key) to move to the previous alarm

without testing the currently displayed alarm. If this option is

given, then the NEXT ALARM (function key) or PREV ALARM

(function key) may be pressed at any time during the

command (even during test results). If the NEXT ALARM or

PREV ALARM is pressed during a test, the test is aborted,

testing of the current alarm stops, and the next alarm or

previous alarm is displayed. If the first alarms is displayed, and

the PREV ALARM is pressed, then the last alarm is displayed.

Also, if the last alarm is currently displayed, and the NEXT

ALARM is requested, then the first alarm will be shown.

NOTE:

When this option is given the only way to terminate this

command is to press CANCEL.

short This will cause the command to execute a series of

nondestructive diagnostic tests.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-294test alarms

Help Messages

If the technician presses HELP after entering “test alarms” the following message

will be displayed:

Enter [’auto-page’], [’failures’], [’step’],

[’short’ or ’long’], [’repeat’ (1-100) or ’clear’]

long This will execute a more comprehensive and longer version of

the diagnostic tests. This may involve both destructive and

nondestructive tests.

repeat number The "number" specifies how many times each test in the

sequence is to be repeated. "Number" may be any integer

between 1 and 100.

clear This option causes the test sequence (short or long) to repeat

until the alarm is cleared or a single test in the sequence fails.

The long clear option forces a clear of all alarms if no errors are

encountered during testing. The short clear option only clears

alarms pertinent to tests in the short sequence.

!WARNING:

Executing a clear with short option, may not clear all

alarms even if all tests pass.

!WARNING:

Since the "clear long" options clear all counters if tests

pass, it is possible for firmware counters to be cleared

even when a problem exists. In some cases customer

service might degrade since calls may be routed over

defective equipment.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-295test alarms

Error Messages

If the command entered is in conflict with another currently executing command,

then a message will be displayed showing the login id of the conflicting user and

the conflicting command. The message is as follows:

’login id’:’command’ has a command conflict

If during the execution of a command a resource problem occurs that requires

the user to restart the command, then the following message will be displayed:

Command resources busy;

Press CANCEL to clear, and then resubmit

If all of the available maintenance resources are currently in use, then the

following message will be displayed:

All maintenance resources busy; try again later

Query From Input

After entering the command test alarms, the system technician will be presented

with an options form for alarm selection.

Alarm

Types The type of alarm to be tested is specified by placing a ’y’ or ’n’ in

the alarm type fields. The technician can choose a combination of

active alarms: major, minor, and/or warning.

Interval Test alarms for records for the last hour (h), last day (d), last week

(w) or all (a). The default is all.

From Test alarm associated with records from the time specified by

mm/dd/hh/mm, where mm month, dd is the day, hh is the hour and

mm is the minute. If no “from” date is entered, then no checking is

done. This will give the user all the alarms active since a month prior

to the current time.

To Test alarms associated with records to the time specified by

mm/dd/hh/mm, where mm is the month, dd is the day, hh is the hour

and mm is the minute. If no "to" date is entered, any alarm which is

active after the from date will be selected.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-296test alarms

Equipment

Type The technician can choose between five different equipment types.

If there is no input to any of these fields, the system will default to all

the equipment. The user can select one of the following fields:

■Cabinet: This allows the technician to test all alarms associated

with a particular cabinet. Alarms for a cabinet are referenced by

a number ranging from 1 to 3 which is assigned during cabinet

administration.

■Port Network: This allows the technician to test all alarms

associated with a particular port network. Alarms for a port

network are referenced by a number ranging from 1 to 3.

■Board Number: This allows the technician to choose all alarms

associated with a particular circuit pack for testing. Alarms for a

circuit pack are referenced by circuit pack location

(cabinet-carrier-slot). If the cabinet number is omitted, the

system will default to 1.

■Port: This allows the technician to choose all alarms associated

with a particular port on a circuit pack for testing. Alarms for a

port circuit are referenced by port location

(cabinet-carrier-slot-circuit). If the cabinet number is omitted,

the system will default to 1.

■Category: Alarms for a particular equipment category.

■Extension: Alarms associated with an extension number.

■Trunk (group/member): The technician can choose to test all

alarms associated with a particular trunk group or trunk group

member. The group identifier should be entered to test all

alarms associated with a trunk group (XX/__). The group

identifier and member identifier should both be entered to test

all alarms associated with a specific trunk group member

(XX/XX).

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-297test alarms

Field Help

Following are the help messages that the system technician will see upon

tabbing to the specified field and pressing the HELP key.

Major? "n(o) y(es)"

Minor? "n(o) y(es)"

Warning? "n(o) y(es)"

Interval: "m(onth), h(our), d(ay), w(eek), a(ll)"

From month "Enter month between 1-12"

From (day) "Enter day between 0-31"

From (hour) "Enter hour between 0-23"

From

(minute) "Enter minute between 0-59"

To (month) "Enter month between 1-12"

To (day) "Enter day between 0-31"

To (hour) "Enter hour between 0-23"

To (minute) "Enter minute between 0-59"

Cabinet: "Enter cabinet number (1-3)"

Port

Network: "Enter port network number (1-3)"

test alarms repeat 1

HARDWARE TEST ALARM QUERY

The following options control which alarms will be tested.

ALARM TYPES

Major? y_ Minor? y_ Warning? y_

REPORT PERIOD

Interval: m_ From: __/__/__:__ To: __/__/__:__

EQUIPMENT TYPE ( Choose only one, if any, of the following )

Cabinet: __

Port Network: __

Board Number: ____

Port: ______

Category: ________

Extension: _____

Trunk ( group/member ): __/__

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-298test alarms

Field Error Messages

Following are the error messages that will be displayed on the screen. The

messages are displayed when the system technician tabs out of a field and the

validation routines are executed. In the following messages, an “x” represents

the character that was entered by the user.

Board

Number: "Enter 4 character board number;

[cabinet(1-3)]:carrier(A-E):slot(0-21)"

Port: "Enter port number;

[cabinet(1-3)]:carrier(A-E):slot(0-21):circuit(1-24)"

Category: “adm-conn, announce, bri/asai, card-mem, cdr, data-mod,

detector, dup-spe, environ, ext-intf, ext-dev, generatr,

inads-link, infc, maint, mbus, memory, misc, mnt-test, modem,

netcon, pkt, pkt_ctrl, quick-st, pms/jrnl, procr, s-syn, stabd,

stacrk, stations, sys-prnt, tape, tdm, tone, trkbd, trkcrk, trunks

and wideband” (For a table describing the category entries in

greater detail, see the “display errors” command.)

Extension: "Enter assigned extension, or blank"

Trunk

(group) "Enter group number between 1-99"

Trunk

(member) "Enter group member between 1-99, or blank"

Major? ""x" is an invalid entry; please press HELP"

Minor? ""x" is an invalid entry; please press HELP"

Warning? ""x" is an invalid entry; please press HELP"

Interval: ""x" is an invalid entry; please press HELP key"

From (month) "Entry must be all digits"

From (day) "Entry must be all digits"

"Day invalid"

From (hour) "Entry must be all digits"

"Hour invalid"

From

(minute)

"Entry must be all digits"

"Minute invalid"

To (month) "Entry must be all digits"

To (day) "Entry must be all digits"

"Day invalid"

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-299test alarms

Output

The responses, with normal output, will be displayed on a test-by-test basis with

one line of data displayed for each test result. With the failures option only the

tests that have failed will be displayed.

The following output fields are for the ALARM ENTRY section:

To (hour) "Entry must be all digits"

"Hour invalid"

To (minute) "Entry must be all digits"

"Minute invalid"

Cabinet: "Invalid entry"

Port

Network:

"Port Network invalid"

Board

Number:

"Invalid entry"

Port: "Port invalid"

Category: “xxxxxxxx” is an invalid entry; please press

HELP”

Extension: "Entry must be all digits"

"Extension not assigned"

Trunk

(group)

"Entry must be all digits"

"Group not assigned, or group assigned but with

no member"

Trunk

(member)

"Entry must be all digits"

"Number invalid""

"Group member not assigned"

"Trunk or trunk group invalid"

Port The location of the alarmed object (cabinet-carrier-slot-circuit).

This is the same identifier as used by the alarm log.

Maintenance

Name The logical name of the maintenance object which has been

alarmed.

On Board Whether the fault detected is on the associated circuit pack, or

an off board element connected to the circuit pack.

Alt Name Terminal extension numbers or trunk group numbers.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-300test alarms

The following fields are displayed for the test results:

When errors are encountered preparing a particular object to be tested (not

inserted, contention, etc.) the an error message will be displayed. This error

message will be displayed in the TEST RESULTS data.

For the following output example, assume that only one alarm was in the alarm

log and it is on the board in cabinet 1, carrier c, slot 7. The command that was

Alarm Type Major, Minor, or Warning. This is an indicator to the seriousness

of the alarm raised.

Service

State RDY (ready for service), OUT (out of service), or IN (in service).

This is the current service state of the station and trunk ports

shown.

Ack The columns under the “1” and “2” headings denote if the alarm

has been acknowledged by the first and second OSS

telephone numbers, respectively.

Date Alarmed Day, hour, and minute of alarm.

Alarm Count This field contains the count of the current alarm entry verses

the total number of alarms to be tested.

Port The port address (cabinet-carrier-slot-circuit) of the maintenance

object that is being tested.

Maintenance

Name The type of maintenance object that is being tested.

Alt. Name The alternate means of identifying the maintenance object. This

field contains the extension when the object is a station, and it

contains xxx/yyy when the object is a trunk, where xxx is the trunk

group number and yyy is the member number. It contains P/xxx

when the object is a private CO line, where xxx is the private CO

line group number.

Test No The actual test that is being executed.

Result An indicator as to whether the test failed, passed, aborted or no

hardware was available (no board). If this field has conflict, this

means that another user was testing this hardware. If this field

has epn-down it means that the epn is inaccessible at this time.

Error Code A numerical description of why the test failed or was aborted.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-301test analog-testcall

entered was “test alarms” and the query form was left empty by just pressing

ENTER.

Feature Interactions

With the enhancement of multiple maintenance users, there may be a possibility

of two users attempting to test the same physical hardware (e.g. one via the test

alarms command and another through the test board command). If this

command should attempt to test a board that is currently being tested by another

user, a error message is displayed.

test analog-testcall

The test analog-testcall command causes the Automatic Transmission

Measurement System (ATMS) to originate a test calls over analog trunks. ATMS

collects performance measurements on the test call and compares them to

administered thresholds. Detail and summary reports of these measurements are

generated with the list testcalls command.

You can specify testing of an entire trunk group or an individual trunk using either

group/member addresses or port and circuit pack location. The type of test call,

the number of the testing line on the far-end switch and various other parameters

must be administered on the trunk group form before the command can execute.

test analog-testcall trunk group# / member# | port UUCSSpp | board UUCSS

[full | supervision | no-selftest | no-return-loss | no-st-or-rl]

[repeat #] [schedule]

test alarms Page 1

ALARM ENTRY

Port Maintenance On Alt Alarm Svc Ack? Date Alarm

Name Brd? Name Type State 1 2 Alarmed Count

01C03 UDS1-BD n WARNING 03/06/16:48 1/4

TEST RESULTS

Port Maintenance Name Alt. Name Test No. Result Error Code

01C03 UDS1-BD 138 NO BOARD

01C03 UDS1-BD 139 NO BOARD

01C03 UDS1-BD 140 NO BOARD

01C03 UDS1-BD 141 NO BOARD

01C03 UDS1-BD 142 NO BOARD

01C03 UDS1-BD 143 NO BOARD

01C03 UDS1-BD 144 NO BOARD

01C03 UDS1-BD 145 NO BOARD

01C03 UDS1-BD 146 NO BOARD

Testing completed for this object.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-302test board

ATMS, the operation of this command, and the measurement reports are

described in Automatic Transmission Measurement System (ATMS) in Chapter 6,

‘‘Additional Maintenance Procedures’’.

test board

test board UUCSS [short | long] [repeat # | clear] [schedule]

The test board command will validate that the board exists at the specified

location. Based on the logical type (e.g., Analog, Digital, Hybrid, etc.) of board a

series of tests will be executed. Each individual test will exercise diagnostics on

the board and then return results of the test along with any possible error codes.

Destructive long tests on a Switch Node Interface (SNI) board are not allowed

unless the board has been busied out.

For more information see Common Input Parameters and Common Output Fields

at the beginning of this chapter.

The following display shows a typical result when test board 1D07 is entered

and slot 1D07 hods a Digital Line circuit pack with 7 ports administered.

test board 1d07 short SPE B

TEST RESULTS

Port Maintenance Name Alt. Name Test No. Result Error Code

01D07 DIG-BD 52 PASS

01D0701 DIG-LINE 5401 16 PASS

01D0701 DIG-LINE 5401 17 PASS

01D0702 PDMODULE 5460 17 PASS

01D0703 PDMODULE 5461 17 ABORT 5

01D0704 PDMODULE 5444 17 ABORT 5

01D0705 DIG-LINE 16 ABORT 1392

01D0705 DIG-LINE 17 ABORT 1392

01D0706 DIG-LINE Attd2 16 PASS

01D0706 DIG-LINE Attd2 17 PASS

01D0707 DIG-LINE Attd1 16 PASS

01D0707 DIG-LINE Attd1 17 PASS

Command Successfully Completed

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-303test cdr-link

test cdr-link

The test cdr-link command validates that a call detail recording link has been

administered and established.

Parameters

For more information see ‘‘Common Input Parameters’’ and ‘‘Common Output

Fields’’ at the beginning of this chapter.

test customer-alarm

test customer-alarm UUC [short | long] [repeat # | clear] [schedule]

The test customer-alarm command performs hardware diagnostic tests on the

leads of the SYSAM or EPN Maintenance circuit pack in a specified cabinet.

These leads are connected to customer equipment and provide a means of

alerting the system administrator and INADS when that equipment fails. The

alarm is activated when a relay on the connected equipment is closed for 1

minute.

The cabinet default is 1. The carrier needs be specified only for PPNs with

duplicated SPEs.

test data-module

test data-module extension [short | long] [repeat # | clear] [schedule]

The test data-module command performs hardware diagnostic tests on a data

module or a data channel. Test results are determined by the interface to the

digital switch-data line port, digital line port, or network control data channel.

test disk

test disk [C] [short | long] [repeat # | clear] [schedule]

test cdr-link primary | secondary

[short | long] [repeat number | clear] [schedule]

[primary | secondary] A system may have up to two CDR links: a primary that

is normally used and a secondary that serves as a

backup in case the primary fails. This qualifier specifies

which link to test. Primary is the default.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-304test ds1-facility

The test disk command performs a series of tests on the disk circuit pack and

the disk media itself. The cabinet is always 1 and need not be entered. Carrier a

or b must be specified only for duplicated SPEs. This command will abort if any

other MSS operation has already begun.

Failure of the disk test may result in the disk being taken out of service. In this

state, access to the disk by all system software except maintenance is blocked.

When the host-adapter is taken out of service due to test or reset failures and

becomes uninstalled, the disk is also placed in the uninstalled state and all

access by system software, maintenance tests, commands (including resets) is

blocked.

test ds1-facility

test ds1-facility UUCSSf [short | long | external loopback] [repeat #]

[schedule]

The test ds1-facility command performs a series of tests on the specified

facility. Each individual test will exercise diagnostics on the facility and then

return results of the test along with any possible error codes. The long test is

destructive and is not allowed unless the facility has been busied out.

Parameters

Examples

test ds1-facility 04a01d

test ds1-facility 03a01a sh c

test ds1-loop

test ds1-loop - For TN464F or TN767E or later suffix DS1 Interface circuit packs.

This command is used for loopback and one-way span testing of the DS1 span.

UUCSSf A DS1 facility is specified by the location of the DS1 Converter circuit

pack and a letter from a to d corresponding to the four facilities

connected to the circuit pack.

external

loopback This specifies a destructive test that sends a test pattern to an

external device and returns it for comparison to the original.

Configure the external device to loop back the signal. See “DS1-FAC

(DS1 Facility)” and “DS1C-BD (DS1 Converter)” in Chapter 9.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-305test ds1-loop

Synopsis

test ds1-loop location [cpe-loopback-jack-test-begin [number-of-bits

bit-pattern] | far-csu-loopback-test-begin | one-way-span-test-begin |

end-loopback/span-test | inject-single-bit-error | ds1/csu-loopback-tests]

Permissions

Logins with the following service levels may execute this command: system

technician, inads, init, super-user, or logins with Maintain Switch Circuit Packs

permissions enabled.

Examples

test ds1-loop 01c08

test ds1-loop 1-3c03 cpe-loopback-jack

test ds1-loop 1-3c03 cpe

test ds1-loop 10c03 end

test ds1-loop 02d12 fa

test ds1-loop 02d12 inj

Description

The test ds1-loop command will validate that the board exists at the specified

location, that the board is a TN464F or TN767E or later suffix DS1 Interface

board. Based on the command parameter, a long-duration loopback/span test or

series of short-duration loopback tests will be executed.

Long-duration loopback tests execute for an extended period of time until the

system technician terminates it. Short-duration loopback tests return the result of

the test to the screen when finished executing. The list measurements ds1

summary command should be used to monitor the status of a long-duration

loopback/span test.

Defaults

The default for the command is ds1/csu-loopback-tests.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-306test ds1-loop

Parameters

Help Messages

If the system technician presses HELP after entering “test ds1-loop” the following

message will be displayed:

Enter DS1 board location,

1. The test will abort if the busyout command has not been set

location A [location] represents the physical position of the

board to be tested. For Standard cabinets a location is

entered as [UUcSS] where “UU” represents the

cabinet number, “c” represents the carrier, and “SS”

represents the slot position. A single digit cabinet

(1-3) are entered with or without a leading zero (0).

cpe-loopback-jack-test-begin1For TN464F or TN767E or later suffix DS1 boards, this

causes a long-duration loopback test to be setup

through the Customer Premises Equipment (CPE)

Loopback Jack. The command allows you to specify a

loop-up code for the CPE loopback jack if it differs

from the default of 0x47F. Specify the number of bits in

the loop-up code as well as the actual bit-pattern (in

hexadecimal).

far-csu-loopback-test-begin1For TN464F or TN767E or later suffix DS1 boards, this

causes a long-duration loopback test to be setup

through the far-end Channel Service Unit (CSU).

one-way-span-test-begin1For TN464F or TN767E or later suffix DS1 boards, this

begins execution of a long-duration one-way span

test.

end-loopback/span-test For TN464F or TN767E or later suffix DS1 boards, this

parameter terminates long-duration one-way span and

loopback testing.

inject-single-bit-error For TN464F or TN767E or later suffix DS1 boards, this

parameter causes a single bit error to be sent within

an active framed 3-in-24 test pattern used in

long-duration loopback and span testing.

ds1/csu-loopback-tests For TN464F or TN767E or later suffix DS1 boards, this

parameter executes the following loopback tests: DS1

Board LoopBack, CSU Module Equipment LoopBack,

and CSU Module Repeater LoopBack. These tests are

performed sequentially for a short duration each, and

individual PASS/FAIL/ABORT test results are reported

following each test.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-307test ds1-loop

[’cpe-loopback-jack-test-begin [number-of-bits bit-pattern]’ or

’far-csu-loopback-test-begin’ or’one-way-span-test-begin’ or

’end-loopback/span-test’ or’inject-single-bit-error’ or

’ds1/csu-loopback-tests’]

Error Messages

If the format for the board location is incorrect, the following error message will

be displayed:

Port/Board invalid

If the EPN in which the specified board resides is not available, the following

message will be displayed:

EPN is not available

If the specified board is not inserted in the system, the following message will be

displayed:

Board not inserted

If the command entered is in conflict with another currently executing command,

then a message will be displayed showing the login id of the conflicting user and

the conflicting command. The message is as follows:

’login id’:’command’ has a command conflict

If during the execution of a command a resource problem occurs that requires

the user to restart the command, then the following message will be displayed:

Command resources busy; Press CANCEL to clear, and then resubmit

If all of the available maintenance resources are currently in use, then the

following message will be displayed:

All maintenance resources busy; try again later

If the test ds1-loop command is executed and the “G3 Version” field on the

“system-parameters customer-options” form is not V3 or later, then the following

message will be displayed:

G3 Version must be V3 or later

If the test ds1-loop command is executed on a circuit pack other than TN464F or

TN767E or later DS1 board, then the following message will be displayed:

Command valid for TN464F or TN767E or

later release DS1 circuit packs

If the [inject-single-bit-error] parameter is selected, but no CPE Loopback Jack,

far-end CSU, or one-way span test is active on the DS1 circuit pack, then the

following message will be displayed:

Parameter valid only if a loopback/span test is active on the DS1

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-308test duplication-interface

Output

The responses will be displayed on a test-by-test basis with one line of data

displayed for each test result.

For the following output example, assume that the board in cabinet 1, carrier c,

slot 7 is a TN767E DS1 board. The command that was entered was test ds1-loop

1c07.

Feature Interactions

Loopback or span tests will not be allowed on DS1 boards unless the board has

been busied out.

Only one of the CPE Loopback Jack, far-end CSU, one-way span, or DS1/CSU

loopback tests may be active at any given time on a DS1 span.

test duplication-interface

test duplication-interface [short | long] [repeat # | clear] [schedule]

Port The port address (cabinet-carrier-slot-circuit) of the

maintenance object that is being tested.

Maintenance

Name The type of maintenance object that is being tested.

Alt. Name The alternate means of identifying the maintenance object.

Test No The actual test that is being executed.

Result The result of the individual test - PASS, ABORT, FAIL, NO

BOARD, DISABLED, EXTRA BD.

Error Code A system-generated number that tells why the release failed

or aborted. A detailed list of the codes according to “Test No.”

is provided for each MO.

test ds1-loop 01C07 ds1/csu-loopback-tests

TEST RESULTS

Port Maintenance Name Alt. Name Test No. Result Error Code

01C07 DS1-BD 1209 PASS

01C07 DS1-BD 1210 PASS

01C07 DS1-BD 1211 PASS

Command Successfully Completed

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-309test duplication-interface

The test duplication-interface command performs hardware diagnostic tests on

the system’s dupint circuit packs and interconnecting cable (DUPINT and

DUP-CHL maintenance objects). Testing is under control of the active SPE. See

descriptions of these maintenance objects in Chapter 9 for more details.

The DUP-CHL maintenance object is associated with both active and standby

DUPINT boards and the interconnecting cable. The DUPINT maintenance object

is associated with the active dupint board. There are five tests for the DUPINT

maintenance object and an additional eight tests for the DUP-CHL maintenance

object.

When testing the active and standby dupint circuit packs and the interconnection

cable for an active SPE carrier, duplication channel components are only tested

in one direction. By performing an SPE interchange, the duplication channel

components can be tested in the other direction for complete testing. Further

testing of the standby dupint board can also be done through the SPE-down

Command Interface with carriers locked. This interface can be used for general

testing of the standby SPE when the SPE handshake is not functioning.

The duplication-interface test is invalid for an SPE simplex system. For SPE

duplex systems, the presence of both DUPINT boards is assumed. In duplex

SPE systems, any DUPINT communication failures will give FAIL or ABORT

results on the output screen.

Loss of handshake between active and standby SPEs prevents testing of

standby SPE components unless the SPE-down interface is used.

The long test sequence is destructive and requires that busyout spe-standby

be executed first.

Output

Port The physical address of the maintenance object that is being

tested. For DUPINT the address is the cabinet (1) and carrier (A

or B) of the active SPE. For DUP-CHL, the address is the cabinet

and carrier of the standby SPE.

Maintenance

Name The type of maintenance object that is being tested.

Alt. Name Not applicable.

Test No. The number of the test being executed.

Result An indicator as to whether the test failed, passed or was

aborted.

Error Code A numerical description of why the test failed or was aborted.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-310test eda-external-device-alrm

The following display shows a typical result when test duplication-interface is

entered and A is the active carrier of a duplicated SPE system.

test eda-external-device-alrm

test eda-external-device-alrm all | physical location [repeat number | clear][

schedule]

This test will perform hardware diagnostic tests on an individual

external-device-alarm port or on all external-device-alarm ports.

The test eda-external-device-alrm command performs a hardware diagnostic

test on all administered external device alarms if all is entered. If an administered

external device alarm port is entered, the test external-device-alarm command

performs a hardware diagnostic test on that port. The test PASSES if the external

device is not reporting an external device alarm and FAILS if the external device

is reporting an external device alarm. If the technician specifies the port it must

be administered as an external device alarm port on a maintenance board or on

an analog line port carrier board.

Defaults

The default for this command is a repeat of 1.

test duplication-interface

TEST RESULTS

Port Maintenance Name Alt. Name Test No. Result Error Code

01B DUPINT 979 PASS

01A DUP-CHL 980 PASS

01A DUP-CHL 874 PASS

01A DUP-CHL 875 PASS

01A DUP-CHL 876 PASS

Command Successfully Completed

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-311test eda-external-device-alrm

Parameters

physical location In addition to entering the word “physical” the system

technician must specify the physical location. For an

administered external device alarm analog line port, a

“physical location” represents the physical position of the port

to be tested and is entered as UUcSSpp where “UU”

represents the cabinet number (1-MAX_CABS), “c”

represents the carrier, “SS” represents the slot position, and

“pp” represents the circuit.

Since the “maintenance board” alarm connections connect to

control carrier boards that are in unnumbered slots, the

standard port format cannot be used to designate these alarm

connections. The special ports UUmajor and UUminor are

used designate the major or minor maintenance board alarm

connection for cabinet UU.

NOTE:

The major/minor designation specifies the pair of wires,

not the alarm level associated with the connection (

i.e

the "major" port can be administered as a major, minor

or warning alarm and the "minor" port can be

administered as a major, minor or warning alarm).

The “all” location is used to test all administered external

device alarm ports on analog line boards and maintenance

boards.

repeat number The “number” specifies how many times the “test physical

location” is to be repeated. “Number” may be any integer

between 1 and 100.

clear This option causes the test sequence (short or long) to repeat

until the alarm (if one exists against the MO) is cleared or a

single test in the sequence fails. If no alarms are registered

against the maintenance object then the test sequence will be

exercised only once.

schedule When the “schedule” option is specified, the command is

validated and then a scheduling form is displayed to allow the

technician to schedule execution of the command. The

command is then placed in the command queue and is

executed at the specified time. The information displayed by

the command is sent to the system printer instead of the

screen. Refer to the Report Scheduler and System Printer

feature specifications [1] for more details.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-312test eda-external-device-alrm

Examples

test eda-external-device-alrm all

test eda-external-device-alrm all schedule

test eda-external-device-alrm physical 1major r 10

test eda-external-device-alrm physical 2c1101 c

Output

For the following output example the command that was entered was test

external-device-alarm all:

The responses will be displayed on a test-by-test basis with one line of data

displayed for each test result.

Field definitions:

Port The port address (cabinet-carrier-slot-circuit) of the

maintenance object that is being tested.

Maintenance

Name The type of maintenance object that is being tested.

test eda-external-device-alrm all

TEST RESULTS

Port Maintenance Name Alt. Name Test No. Result Error Code

03major EXT-DEV CMS1 120 PASS

03A2102 EXT_DEV CMS2 120 FAIL

01major EXT-DEV UPS1 120 PASS

01minor EXT-DEV UPS1 120 PASS

01c1201 EXT-DEV UPS1 120 PASS

03A2101 EXT_DEV CC temp 120 PASS

01c1202 EXT-DEV Audix1 120 PASS

03minor EXT-DEV Audix2 120 FAIL

04major EXT-DEV unknown 120 FAIL

Command successfully completed

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-313test environment

test environment

test environment UU [short | long] [repeat # | clear] [schedule]

The test environment command performs hardware diagnostic tests of the

environment monitoring and control, and emergency transfer functions of a

specified cabinet. This command tests both PPN and EPN cabinets. Circuit

packs involved are the SYSAM (PPN) EPN Maintenance, and tone/clock (for the

ring generator test.

!CAUTION:

The long test recycles power on all port circuit pack carriers and is

destructive. It does not recycle power on active or standby PPN or EPN

control carriers or switch node carriers. When a port carrier is recycled, all

service and links to ports on the carrier are dropped. If a carrier containing

an active EI or tone-clock is recycled, all service to that cabinet will be

disrupted.

There are nine Maintenance Objects involved in this test:

Note that although the CUST-ALARM maintenance object is part of the

environment functionality, it is not actually tested using the ‘test maintenance’

command. See ‘test customer-alarm’ for details on testing this particular MO.

Output

The following display shows a typical result when test environment 1 is entered

in order to test the PPN cabinet.

Alt. Name The alternate means of identifying the MO. This is an

administered more descriptive name of the external device alarm

Test No The actual test that is being executed.

Result The result of the individual test -PASS, ABORT, FAIL,NO BOARD,

DISABLED, EXTRA BD.

Error Code A system-generated number that tells why the release failed or

aborted. A detailed list of the codes according to “Test No.” is

provided for each MO.

EMG-XFER POWER RING-GEN

AC-POWER DC-POWER CUST-ALARM

CARR-POW CABINET EXT-DEV

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-314test fiber-link

The following display shows a typical result when test environment 2 is entered

and cabinet 2 is a single carrier cabinet.

test fiber-link

The test fiber-link command validates that the optical fiber connection between

switch node interfaces (SNI) and expansion interfaces (EI), or a combination

thereof, are administered. If the fiber link is administered, a series of hardware

diagnostic tests are performed on the specified fiber link. The test results along

with any possible error codes are displayed on the MT. The long test sequence

test fiber-link# [a-pnc | b-pnc] [short | long]

[repeat # | clear] [schedule]

test environment 1

TEST RESULTS

Port Maintenance Name Alt. Name Test No. Result Error Code

01 POWER 5 PASS

01 AC-POWER 78 PASS

01E CARR-POW 127 PASS

01D CARR-POW 127 PASS

01A CARR-POW 127 PASS

01B CARR-POW 127 PASS

01C CARR-POW 127 PASS

01 EMG-XFER 124 PASS

01 CABINET 122 PASS

01 EXT-DEV 120 PASS

01 RING-GEN 117 PASS

01 RING-GEN 118 PASS

Command Successfully Completed

test environment 2

TEST RESULTS

Port Maintenance Name Alt. Name Test No. Result Error Code

04 DC-POWER 79 PASS

04 EMG-XFER 124 PASS

04 EXT-DEV 120 PASS

04 RING-GEN 117 PASS

04 RING-GEN 118 PASS

Command Successfully Completed

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-315test fiber-link

includes destructive tests. All destructive tests abort unless the fiber link is first

busied out. The short test sequence is non-destructive and can be performed

regardless of whether the fiber link is busied out.

A fiber link is a connection between port networks (PNs), switch nodes (SNs), or

between a PN and the Center Stage Switch (CSS). This connection is comprised

of a bi-directional optical fiber connection (optionally extended via a DS1

Converter Complex), with each end terminated on either an Expansion Interface

(EI) or a Switch Node Interface (SNI). Fiber links provide the medium for circuit

and packet connections between PNs and for communication between the SPE

and Expansion PNs (EPNs) for the CSS.

The long sequence includes destructive tests and requires that the fiber link be

busied out first. When a fiber is busied out, all calls over that fiber are dropped.

clear firmware-counters clears the firmware counters of specified SNI, SNC or

DS1C circuit packs, or of an the entire PNC (A or B).

Parameters

Examples

Simplex PNC:

test fiber-link 1 l schedule

test fiber-link 10 sh r 25 sch

Duplicated PNC:

test fiber-link 1 a-pnc schedule

test fiber-link 03 b-pnc sh r 3

Output

The following display shows a typical result when test fiber-link 1 b-pnc is

entered.

link# The number associated with a fiber link or fiber link pair (on

duplicated PNCs). List fiber-link displays the location of

endpoints for each fiber link.

a-pnc | b-pnc On Critical Reliability systems (duplicated PNC) this identifier is

used to distinguish between the two fibers of a duplicated fiber

pair.

Port On Critical Reliability systems (duplicated PNC) there are two

fibers associated with every fiber link number. A-PNC and B-PNC

distinguish one from the other.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-316test hardware-group

test hardware-group

This command runs a series of demand maintenance tests on all hardware in a

specified group: a carrier, cabinet, port network, PNC (A or B), SPE, circuit pack

or the entire system. The tests executed vary depending on the options chosen

and types of hardware in the group. Some tests are run concurrently to speed

execution, so test results for several maintenance objects may be intermixed.

A hardware-group command running in the foreground can be aborted by

pressing Cancel or by entering cancel hardware-group at another terminal. The

cancel command must be used for a test running in the background. You can

restart a canceled hardware-group test at the point it left off by entering resume

hardware-group. Hardware group tests started with the all-ports or

spe-interchange options can be resumed, but they will not always test every port

that originally would have been tested.

Feature Interactions

test hardware-group [system | carrier UUC | cabinet UU | port-network PN# |

pnc a-pnc | b-pnc | board UUCSS | spe]

[print | schedule]

Test

hardware-group Only one "test hardware-group" command can be active at any

given time.

test fiber-link 1 b-pnc SPE B

TEST RESULTS

Port Maintenance Name Alt. Name Test No. Result Error Code

1 B-PNC FIBER-LK 777 PASS

1 B-PNC FIBER-LK 759 PASS

1 B-PNC FIBER-LK 989 PASS

1 B-PNC FIBER-LK 237 PASS

1 B-PNC FIBER-LK 238 PASS

Command Successfully Completed

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-317test hardware-group

TTI If the test hardware-group command is issued with the

all-ports option while the TTI background task is active, some

unadministered ports may not be tested. In addition, active

alarms on line ports may be cleared by this task. The status tti

command may be used to determine the state of the TTI

background task.

Add Station If the add station command is entered for an untranslated port

at the same time as it is being tested by the test

hardware-group command with the all-ports option, the

request to add station will fail and the following message will

be displayed:

Object in use; please try later

Trunk

Administration If an attempt is made to add an unadministered trunk port to a

trunk group at the same time as it is being tested because of

the test hardware-group command with the all-ports option,

the request will fail and the following message will be

displayed:

Object in use; please try later

Save Translation If the test hardware-group command is issued with the

all-ports option when a translation save operation is active,

some unadministered ports may not be tested. All other

hardware will be tested normally.

Hardware

Alarms When a hardware error is detected by the test hardware-group

command the hardware goes through the standard escalation

strategy. Alarms will be raised on hardware that manifest hard

errors. This alarming strategy is the same, regardless of

whether the ports are translated or not.

System

Interaction The performance of test hardware-group is affected by call

processing traffic, administration activity, choice of the short or

long option, whether the all-ports option was chosen, whether

the spe-interchange option was chosen, and other demand

maintenance activity.

Scheduled and

Periodic

Maintenance

When a test hardware-group command is entered, all activity

related to scheduled background maintenance, periodic

background maintenance, and data audits is suspended for

the duration of the execution of the test hardware-group

command. When a test hardware-group command is canceled

or when the test hardware-group command completes, all

suspended periodic, scheduled, and data audits background

maintenance activity will be restarted where it left off.

Demand Testing

of SPE

Components

When a test hardware-group command is entered with the

SPE-interchange option, demand tests of SPE components

may abort while the interchange is in progress.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-318test hardware-group

Parameters

All maintenance objects included in the specified hardware group are tested,

including all circuit packs and ports. When a cabinet or larger entity is specified,

environmental MOs are tested (see test environment).

Examples

test hardware-group system

test hardware-group port-network 11

test hardware-group pnc a-pnc

test hardware-group board 01c07

test hardware-group spe

Form Input

When you enter the command, an input form is displayed upon which you can

specify certain options.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-319test hardware-group

Test

sequence Specify the short or long test sequence. The long sequence is

more comprehensive and is not destructive.

Test

Repetition Specify repeat to enter a number of times that the entire test

sequence is to be repeated. Specify continuously to cause the

test sequence to be repeated until the command is canceled.

count When the previous field is set to repeat, specify the number of

repetitions here.

Auto-page? Specifying y causes a whole new screen to be displayed

automatically whenever the screen fills up with results. This

option is incompatible with the background option. If you do not

specify the auto-page option, once the screen fills with results,

testing will stop until you press Page or Cancel. Specifying print

on the command line automatically engages auto-page.

Background? Specifying y causes the tests to run in the background, freeing

up the terminal for other tasks. Error results are logged in the

error log but not displayed on the screen. This option is

incompatible with the auto-page and "continuously" options.

Failures? Specifying y causes only failure results to be displayed on the

screen.

All-ports? Specifying y causes testing of all customer-translated line and

trunk ports and, for the following circuit packs, untranslated

ports as well:

TN# Description TN# Description

TN413 Digital Line [G3r V2] TN753 Direct-Inward-Dial Trunk

TN417 Auxiliary Trunk [G3r V2] TN754 Digital Line

TN429 DIOD Trunk [G3r V2] TN754 Digital Line

TN436 DID Trunk [G3r V2] TN760C Tie Trunk

TN437 Tie Trunk [G3r V2] TN762 Hybrid Line

TN438 Central Office Trunk [G3r V2] TN762B Data Line

TN439 Tie Trunk [G3r V2] TN763C Auxiliary Trunk

TN447 Central Office Trunk [G3r V2] TN769 Analog Line with Message Waiting

TN458 Tie Trunk [G3r V2] TN784 Digital Line

TN459 DID Trunk [G3r V2] TN785 16 Port Analog Line

TN465 Central Office Trunk [G3r V2] TN2135 Italian 16 Port Analog Line [G3r V2]

TN467 8 port Analog line [G3r V2] TN2136 Digital Line [G3r V2]

TN468 16 port Analog line [G3r V2] TN2138 Central Office Trunk [G3r V2]

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-320test hardware-group

Output

When the test is run in the foreground, test results are displayed in the normal

format. In addition, the message line displays a running count of the number of

maintenance objects already tested, the total number included in the tests,

percent completed and repetition count.

The following display shows a typical result when test hardware-group system

is entered.

TN479 16 port Analog line [G3r V2] TN2139 Direct Inward Dialing Trunk [G3r V2]

TN497 Tie Trunk [G3r V2] TN2140 Tie Trunk [G3r V2]

TN556 ISDN BRI Line TN2144 Analog Line [G3r V2]

TN735 MET Line TN2146 Direct Inward Dialing Trunk [G3r V2]

TN742 8 port Analog Line TN2147 Central Office Trunk [G3r V2]

TN746 16 port Analog line TN2149 Analog Line [G3r V2]

TN747B Central Office Trunk TN2180 16 port Analog line [G3r V2]

SPE-interchange? Specifying y causes the system to perform a planned

SPE interchange so that both SPEs can be fully tested.

TN# Description TN# Description

test hardware-group system Page 1 of 1

TEST HARDWARE-GROUP SELECTIONS

Select the desired options for the specified test.

Test sequence: short

Test repetition: repeat_____ count: 1

Output OPTIONS: HARDWARE OPTIONS:

Auto-page? n All-ports? n

Background? n SPE-interchange? n

Failures? n

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-321test host-adapter

test host-adapter

test host-adapter [C] [short | long] [repeat # | clear] [schedule]

The test host-adapter command performs a series of tests on the host-adapter

portion of the specified MSSNET circuit pack. This command will abort if any

other MSS operation has already begun.

Failure of the host-adapter test may result in disabling access to the host-adapter

by all system software except maintenance. Such a failure of the host-adapter

also denies access to the related tape and disk until the host-adapter is fully in

service.

The cabinet is always 1 and need not be entered. Carrier a or b must be

specified only for systems with duplicated SPEs.

test inads-link

This command will perform hardware diagnostic tests from the inads port that is

accessible through the maintenance board to an OSS telephone number.

Synopsis

test inads-link [1 | 2]

test hardware-group system

TEST RESULTS

Port Maintenance Name Alt. Name Test No. Result Error Code

01C07 ANL-BD 51 PASS

01C07 ANL-BD 52 PASS

01C0703 ANL-LINE 5444 35 PASS

01C0702 ANL-LINE 5447 35 PASS

01C0703 ANL-LINE 5444 48 PASS

01C0701 ANL-LINE 5401 35 FAIL 1000

01C0702 ANL-LINE 5447 48 PASS

01C0703 ANL-LINE 5444 36 PASS

01C0702 ANL-LINE 5447 36 PASS

01C0701 ANL-LINE 5401 48 FAIL 1000

01C0701 ANL-LINE 5401 36 PASS

Testing system, 68 of 342 (19%) MOs tested for repetition 1

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-322test inads-link

Permissions

The following default logins may execute this command: system technician,

inads, init, nms.

Examples

test inads-link

test inads-link 1

test inads-link 2

Description

The test inads-link command attempts to make a call over the inads port on the

maintenance board to verify the INADS alarm notification process. By default, the

link to the first OSS telephone number is tested. If there is an alarm pending to be

reported or the call is in progress or up, then the test will be aborted. If the alarm

origination to the OSS telephone number to be tested is disabled, the test

generates an informative error and the test continues. The test will wait 2 minutes

before executing to allow the remote maintenance technician to logoff freeing the

line. The line must be free so the system can place a call to INADS. A local SAT

user entering the test inads-link command need not log off for the system to

place a call to INADS, but the2 minute delay still exists.

Once the call is answered by INADS, the system will send a message with a test

alarm type. INADS acknowledges receipt of the message and creates a trouble

ticket. The trouble ticket will be closed immediately and have a “INADS LINK

TEST” message entered in the description field. If an alarm is raised while the

test call is up, the system will not send an alarm message over the existing link.

The normal retry mechanism will be followed, which means an attempt to make a

call to INADS to report the error will take place 7 minutes later. An INADS trouble

ticket will be created only if the connection is successfully established, and a

message is sent to the system acknowledging that INADS received the system

message.

The “Maintain Process Circuit Packs” field must be set to yes on the inads and

technician permission forms. This will provide permissions to execute the test

inads-link command. The field can be changed by executing a change

permission login command.

There will be no alarms raised on the system as a result of the “test inads-link”

command. Attendant alarm and acknowledgment lamp states will not be

changed as a result of the command. The test will not be run during periodic or

scheduled maintenance.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-323test inads-link

Defaults

The test will default to test the link to the first OSS telephone number.

Parameter

Help Messages

If the system technician presses HELP after entering test inads-link the following

message will be displayed:

[‘1’ or ‘2’]

Or press CANCEL to cancel the command

If the command entered is in conflict with another currently executing command,

then a message will be displayed showing the login id of the conflicting user and

the conflicting command. The message is as follows:

’login id’:’command’ has a command conflict

If during the execution of a command a resource problem occurs that requires

the user to restart the command, then the following message will be displayed:

Command resources busy;

Press CANCEL to clear, and then resubmit

If all of the available maintenance resources are currently in use, then the

following message will be displayed:

All maintenance resources busy; try again later

Output

If the test passed then the following message will be displayed:

Command successfully completed

If the test failed, because the link was up or because there was an active alarm

that the switch needs to report or there was a problem with the call, the following

message will be displayed:

Command failed

NOTE:

An entry is made in the error log describing why the inads-link test failed.

1This option will cause testing of the link to the first OSS telephone

number.

2This option will cause testing of the link to the second OSS telephone

number.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-324test isdn-testcall

Feature Interactions

None

test isdn-testcall

test isdn-testcall group#/member# [minutes #] [schedule]

The test isdn-testcall command starts an outgoing ISDN-PRI test call using the

asynchronous method.

Only 1 ISDN trunk in each port network can be tested at one time. The maximum

number of asynchronous outgoing test calls that can be run simultaneously

depends on the number of Maintenance/Test circuit packs in the system.

For more information, see Test #258 under “ISDN-TRK (DS1 ISDN Trunk)” in

Chapter 9.

Parameters

For more information, see ‘‘Common Input Parameters’’ at the beginning of this

chapter.

Examples

test isdn-testcall 78/2 minutes 10

Output

test journal-printer

test journal-printer pms-log | wakeup-log

[short | long] [repeat number| clear] [schedule]

group#/member# Specify the trunk over which to originate the test call.

minutes # Specify the duration of the test call in minutes from 1 to

120. The duration defaults to 8.4 or 9.6 seconds.

Result PASS - The test call was successfully initiated.

ABORT - Resources were not available (for example, a B-channel

or Maintenance/Test circuit pack).

FAIL - An outgoing test call could not be initiated.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-325test led

The test journal-printer command performs hardware diagnostics on the link

between the switch and a specified journal printer link to either the PMS-log

printer or the wakeup-log printer.

Parameters

One of the 2 journal printers must be specified:

Output

Background maintenance activity on a link can interfere with testing and

recovery of a particular component of the link. For example, as part of a test,

maintenance software may busy out a component of the link, causing the link to

drop. The system may then perform frequent attempts to re-establish the link.

This can delay recovery of the component, since it must be idle for certain tests

to take place. Busying out the link will prevent the system from these attempts to

set up the link. Remember that a busyout will tear down a link if it is not already

down.

test led

b-pnc] [repeat #]

This command verifies that a specified cabinet, port network, PNC or switch

node is recognized by the system. It is also useful for identifying a port network,

cabinet, or PNC (A or B).

When test led is entered, the red, green and yellow circuit pack LEDs are turned

on until all administered carriers in the specified group have been lit for 2

seconds. They are then turned off in the same order in which they came on. The

cycle can be repeated a number of times with the repeat option. Once all of the

repeat cycles are completed, all affected LEDs are restored to reflect their

current status.

pms-log This specifies the link to the Property Management System

printer, whose maintenance name is PMS-PRNT.

wakeup-log This specifies the wakeup-log printer, whose maintenance

name is JNL-PRNT.

Maintenance

Name PMS-PRNT designates the PMS-log printer. JNL-PRNT

designates the wakeup-log printer.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-326test link

test link

test link link [short | long] [repeat | clear] [schedule]

This command verifies that the specified link is administered and performs a

series of tests on the link.

Parameters

Output

The following display shows a typical result when test link 1 long is entered.

test maintenance

test maintenance [C] [short | long] [repeat # | clear] [schedule]

The test maintenance command performs hardware diagnostic tests on a the

SYSAM (PPN) and EPN Maintenance circuit packs.

Port Each link is identified by a number (1-16) assigned on the

Communication-Interface Links form. Display

communication-interface links shows the location and

identification of each link.

Port The location of the port on a Packet Gateway circuit pack associated

with the link being tested.

test link 1 long SPE B

TEST RESULTS

Port Maintenance Name Alt. Name Test No. Result Error Code

01C2001 PGATE-PT 5464 610 ABORT 1000

01C2001 PGATE-PT 5464 611 ABORT 1000

01C2001 PGATE-PT 5464 599 ABORT 1005

01C2001 PGATE-PT 5464 613 PASS

01C2001 PGATE-PT 5464 614 ABORT 1

01C2001 PGATE-PT 5464 976 FAIL 2

01C2001 PGATE-PT 5464 977 FAIL

Command Successfully Completed

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-327test maintenance

On the SYSAM, this command tests system maintenance, ACTIVE and STANDBY

terminal ports, and the SYSAM refresh, dual port RAM, system reset and sanity

timer functions. On the SYSAM, the long test sequence resets the circuit pack,

terminating any local or remote SYSAM logins. To see if the last 2 tests pass, you

must log in again. The Outpulse Relay Test and the Analog Loop Around Test are

not run on the standby SYSAM in a duplicated SPE.

On EPN Maintenance circuit packs, the MT interface, EI link, reset and sanity

functions are tested. The long test resets the EPN Maintenance circuit pack,

causing a local EPN Maintenance login to drop.

The cabinet number defaults to 1. Carrier a or b must be specified only for PPN

cabinets with duplicated SPEs.

Output

The following display shows a typical result when test maintenance a is entered.

The following display shows a typical result when test maintenance 2 is entered.

test maintenance

TEST RESULTS

Port Maintenance Name Alt. Name Test No. Result Error Code

01A SYSAM 911 PASS

01A SYSAM 913 PASS

01A SYSAM 915 PASS

Command Successfully Completed

test maintenance 2

TEST RESULTS

Port Maintenance Name Alt. Name Test No. Result Error Code

02A MAINT 106 PASS

02A MAINT 229 PASS

02A MAINT 303 PASS

02A MAINT 854 PASS

02A MAINT 337 PASS

Command Successfully Completed

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-328test mass-storage

test mass-storage

test mass-storage [C] [short | long] [repeat | clear] [schedule]

This command performs tests on each of the 3 components of the Mass Storage

System (MSS): the host adapter circuit on the MSSNET circuit pack, the tape

circuit pack and the disk circuit pack. Each of the 3 objects is tested using the

same sequence used when individual components are tested separately.

This command aborts if any other mass-storage operation has already begun.

Failure of the host-adapter test may result in the disabling of periodic and

scheduled testing of the failed host-adapter and the related tape and disk.

Failure of a tape or disk test may result in the disabling of periodic and

scheduled testing of the component.

The cabinet is always 1 and need not be entered. Carrier a or b must be

specified only for systems with duplicated SPEs.

The following display shows a typical result when test mass-storage a is

entered.

test memory

test memory CSS [short | long] [repeat # | clear] [schedule]

This command performs hardware diagnostic tests on any or all Memory circuit

packs in the specified carrier. All tests in both sequences are non-destructive.

test mass-storage

TEST RESULTS

Port Maintenance Name Alt. Name Test No. Result Error Code

01A H-ADAPTR 822 PASS

01A H-ADAPTR 823 PASS

01A H-ADAPTR 824 PASS

01A H-ADAPTR 825 PASS

01A TAPE 809 PASS

01A TAPE 812 PASS

01A TAPE 813 PASS

01A TAPE 814 PASS

01A TAPE 815 PASS

01A DISK 809 PASS

01A DISK 812 PASS

01A DISK 813 PASS

01A DISK 814 PASS

01A DISK 815 PASS

Command Successfully Completed

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-329test mssnet

The short test takes about 2 minutes to complete. The long test on a single circuit

pack takes about 2.5 minutes. The long test takes an additional 2 minutes on

circuit pack 1 for the Checksum Test.

Parameters

Output

NOT ASSIGNED indicates that the specified slot is not administered.

test mssnet

test mssnet C [short | long][repeat |clear][schedule]

The test mssnet command runs a series of diagnostic tests on the MSSNET

circuit pack. Tests are run on both maintenance objects located on the MSSNET

circuit pack: host-adapter (H-ADAPTR) and switch control (SW-CTL).

Parameters

Output

The following display shows a typical result when test mssnet 1a is entered.

CSS The cabinet is always 1 and need not be specified. Carrier a or b must

be specified only for duplicated SPEs. You can specify one of the

Memory circuit pack slots (1-4) on the PPN control carrier. If the slot is

not specified, all memory circuit packs are tested.

CThe cabinet is always 1 and need not be entered. The carrier, a or b,

must be specified in a duplicated SPE system.

clear The clear option does not provide a useful function for this command.

MSSNET is used only as a command object to run tests of the MSSNET

circuit pack. Failures of circuits on the MSSNET board cause alarms

against H-ADAPTR and SW-CTL. Individual demand tests of those

maintenance objects should be used to clear associated alarms.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-330test packet-interface

test packet-interface

test packet-interface [CSS] [short | long] [repeat # |clear] [schedule]

This command performs hardware diagnostic tests on any or all of the packet

interface circuit packs in a specified carrier. Tests performed include local

memory checksum tests, loop-around tests, and checks of failure counters.

The Maintenance Loop-Around Test (#886) is included in the test sequences of

active

packet-interface circuit packs only. The Active-Standby Peer Link Test

(#888) is included in the test sequences of the

standby

packet-interface circuit

packs only.

If the packet-interface circuit pack is in the “out-of-service” or “uninstalled”

states, no demand tests as well as scheduled, periodic and error tests will run.

See also reset packet-interface and status packet-interface.

Parameters

test processor

test processor [C] [short | long] [repeat # | clear] [schedule]

The test processor command performs hardware diagnostic tests on a specified

processor circuit pack.

CSS The cabinet is always 1 and need not be entered. The carrier, a or b, must

be entered only for duplicated SPEs. Slot number ranges from 1 to 3,

corresponding to the dedicated PKT-INTFC slots on the control carrier. If

omitted, all Packet Interface circuit packs on the specified carrier are

tested.

test mssnet 1a SPE A

TEST RESULTS

Port Maintenance Name Alt. Name Test No. Result Error Code

01A H-ADAPTR 822 PASS

01A H-ADAPTR 823 PASS

01A H-ADAPTR 824 PASS

01A H-ADAPTR 825 PASS

01A SW-CTL 92 PASS

Command Successfully Completed

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-331test signaling-group

test signaling-group

test signaling-group group#[short | long] [repeat# | clear][schedule]

The test signaling-group validates the administration of a signaling group and

runs a series of diagnostic tests on it.

An ISDN-PRI signaling group is a set of B-channels whose signaling messages

are carried together on a designated D-channel or set of D-channels.

Parameters

test spe-standby

test spe-standby [short | long] [repeat # | clear][schedule]

This command is valid only on systems with duplicated SPE. The test

spe-standby command performs hardware diagnostic tests on each component

of the standby Switch Processing Element (SPE). This command is also used

with the long option to remove a standby from recent interchange mode. The

sequence begins with testing of the STBY-SPE maintenance object to determine

the availability of the standby SPE. The following tests are run on STBY-SPE:

1. Standby SPE status query

2. Standby SPE handshake test

3. Standby SPE time of day comparison (standby in synch with active)

4. Standby SPE configuration matchup test

The last test is run only in the long sequence. After the above sequence, tests of

each component on the standby SPE are run.

Testing the standby SPE does not affects the availability of the standby SPE for

service only in that execution of the long sequence takes the standby out of

recent interchange mode.

group# An administered number associated with each signaling group.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-332test spe-standby

Output

The following display shows a typical result when test spe-standby is entered.

test spe-standby Page 1 SPE B

TEST RESULTS

Port Maintenance Name Alt. Name Test No. Result Error Code

01A STBY-SPE 855 PASS

01A STBY-SPE 919 PASS

01A STBY-SPE 858 PASS

01A DISK 809 PASS

01A DISK 812 PASS

01A DISK 813 PASS

01A DISK 814 PASS

01A DISK 815 PASS

01A TAPE 809 PASS

01A TAPE 812 PASS

01A TAPE 813 PASS

01A TAPE 814 PASS

01A TAPE 815 PASS

01A H-ADAPTR 822 PASS

01A H-ADAPTR 823 PASS

press CANCEL to quit -- press NEXT PAGE to continue

test spe-standby Page 2 SPE B

TEST RESULTS

Port Maintenance Name Alt. Name Test No. Result Error Code

01A H-ADAPTR 824 PASS

01A H-ADAPTR 825 PASS

01A PROCR 896 PASS

01A PROCR 897 PASS

01A PROCR 899 PASS

01A PROCR 900 PASS

01A SYSAM 911 PASS

01A SYSAM 913 PASS

01A SYSAM 912 PASS

01A SYSAM 915 PASS

01A2 MEM-BD 906 PASS

01A2 MEM-BD 907 PASS

01A2 MEM-BD 908 PASS

01A1 MEM-BD 906 PASS

01A1 MEM-BD 907 PASS

press CANCEL to quit -- press NEXT PAGE to continue

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-333test stored-data

test stored-data

test stored-data [short | long] [repeat # | clear] [schedule]

The test stored-data command performs a set of consistency checks of the boot

images and translation data on tape and disk. In particular, software vintage

numbers and translation time stamps are compared.

The short test sequence includes only inter-device tests. These include a

tape-to-tape, disk-to-disk and two tape-to-disk tests for SPE duplex systems with

tape and disk devices on both carriers. The long test sequence includes up to

four intra-device consistency checks, one for each device. Another check of the

system boot source is included in the long sequence.

For SPE simplex systems, only one tape-to-disk inter-device test and two

intra-device consistency checks along with the boot source check are run. The

other tests simply do not appear in the short or long test sequences.

The lack of the optional disks does not affect which tests are run. For both SPE

simplex systems and SPE duplex systems, aborts are returned for those tests

which require a disk.

This command will abort if any other MSS operation has already begun.

If translations have been saved to disk since the last time the disk was backed

up to tape (a normal situation during work sessions), tests executed by this

command will fail.

test switch-control

test switch-control [C] [short | long] [repeat # | clear] [schedule]

test spe-standby PAGE 3 SPE B

TEST RESULTS

Port Maintenance Name Alt. Name Test No. Result Error Code

01A1 MEM-BD 908 PASS

01A SW-CTL 92 PASS

01A1 PKT-INT 887 PASS

01A1 PKT-INT 888 PASS

Command Successfully Completed

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-334test synchronization

The test switch-control command performs hardware diagnostic tests of the

PPN Archangel, or SW-CTL circuit, on a specified MSSNET circuit pack. The PPN

Archangel is responsible for transmitting messages back and forth between the

SPE and the port circuit packs. For the short test of the active PPN Archangel, a

loop-around test and a Control Channel test are performed. For the short test of

the standby PPN Archangel, only the loop-around test is performed.

The long test includes a reset. When applied to the active PPN Archangel, this

momentarily prevents call origination from stations or trunks connected to ports

in the PPN. It is non-destructive for existing calls.

Parameters

test synchronization

test synchronization [short | long] [repeat # | clear] [schedule]

The test synchronization command checks the timing synchronization source

and updates circuit packs with the correct synchronization parameters. The

tone-clocks, DS1s, and EIs are sent down-link messages to place them in the

correct synchronization configuration given the current on-line synchronization

reference.

The synchronization subsystem provides error-free digital communication

between the switch and other PBXs, COs, or customer premises equipment. The

subsystem is made up of the TDM bus clock, DS1 trunk circuit packs, and

maintenance and administration software resident in the SPE.

Parameters

test sys-link

test sys-link UUCSSpp [channel # ] [current | faulted]

[short | long][repeat # | clear] [schedule]

CThe cabinet is always 1 and need not be entered. Carrier a or b must

be specified only for systems with duplicated SPEs.

long This will execute a more comprehensive and longer version of the

diagnostic tests. When applied to the active PPN Archangel, this

momentarily prevents call origination from stations or trunks

connected to ports in the PPN. It is non-destructive for existing calls.

long Both long and short sequences run Test #417. If Stratum 3 synchronization

is administered, an additional non-destructive test (#649) is run by the

long sequence.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-335test sys-link

The test sys-link command will validate the existence of the specified link and

run diagnostic tests on the hardware path that comprises the system link. If the

“current” or “faulted” option is specified, tests are run on all hardware objects

that comprise the specified link. If “current” or “faulted” is not specified, only the

end-to-end sys-link connection will be tested.

The hardware path that comprises a system link consists of up to 21 hardware

components that affect the behavior of the link. The number of components of a

given system link hardware path depends on the system configuration and type

of system link. The following links are examples of system links: Expansion

Archangel Links (EAL), Indirect Neighbor Links (INL), Processor Gate Control

links (PGC), PRI signaling links (PRI), System Access Port links (SAP), X.25

adjunct links (X25).

Parameters

Examples

test sys-link 2e0201 current l schedule

test sys-link 2e0201 faulted r 10

test sys-link 1c1701 channel 3 r 10

Output

The following display shows a typical result when test sys-link 1e0201 current is

entered.

UUCSSpp The location of the port associated with the system link.

channel

number The processor channel (1 to 128) associated with an X.25 adjunct

link to be tested.

current This specifies testing of the current hardware path of the system

link.

faulted This specifies testing of the hardware path of the system link as it

was constituted when a fault last caused the link to go down. For

more information, see ‘‘Common Input Parameters’’ at the

beginning of this chapter.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-336test tape

test tape

test tape [C] [short | long] [repeat # | clear] [schedule]

The test tape command performs a series of tests on the tape circuit pack and

tape cartridge. The standard cartridge used for backups of the disk is

compatible with this test. The tape cartridge is rewound and a specific portion of

the tape is used for test reads and writes. Tapes used for core dumps have an

incompatible file system and should not be used for this test.

The cabinet is always 1 and need not be entered. Carrier a or b must be

specified only for systems with duplicated SPEs.

This command aborts if any other MSS operation has already begun.

Failure of the tape test may result in the tape being placed in an out-of-service

state. In this state, access to the tape by all system software except maintenance

is blocked.

When the host-adapter is taken out of service due to failures of its tests, or fails a

reset and becomes uninstalled, the tape is also placed in the uninstalled state

and all access by system software, maintenance tests and commands including

reset are blocked from execution.

Tapes used for core dumps have an incompatible file systems and cannot be

tested by this command.

test sys-link 1e0201 current Page 1 SPE A

TEST RESULTS

Port Maintenance Name Alt. Name Test No. Result Error Code

01E0201 SYS-LINK LNL 985 PASS

01A1 PKT-INT 886 PASS

01A1 PKT-INT 887 PASS

PN 01 PKT-BUS 572 PASS

PN 01 PKT-BUS 573 PASS

01E01 EXP-INTF 237 PASS

01E01 EXP-INTF 238 PASS

01E01 EXP-INTF 240 PASS

01E01 EXP-INTF 241 PASS

01E01 EXP-INTF 589 PASS

01E01 EXP-INTF 316 PASS

1 A-PNC FIBER-LK 777 PASS

1 A-PNC FIBER-LK 759 PASS

1 A-PNC FIBER-LK 237 PASS

1 A-PNC FIBER-LK 238 PASS

press CANCEL to quit -- press NEXT PAGE to continue

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-337test tdm

test tdm

test tdm port-network PN# [short | long] [repeat # | clear] [schedule]

The test tdm command performs hardware diagnostic tests on the time slots of

the specified TDM bus. Both halves (“a” and “b”) of the TDM bus are tested.

test tone-clock

test tone-clock UUC [short | long] [repeat # | clear] [schedule]

The test tone/clock command performs hardware diagnostic tests on the 3

maintenance objects on a specified tone/clock circuit pack: TONE-BD,

TONE-GEN, TDM-CLK.

test trunk

test trunk group# [/ member#] [short | long] [repeat # | clear] [schedule]

The test trunk command performs hardware diagnostic tests on an entire trunk

group or an individual trunk group member, depending on the options entered.

test tsc-administered

test tsc-administered signaling-group# / tsc-index [repeat#] [schedule]

The test tsc-administered command runs diagnostic tests on any type of

administered Temporary Signaling Connections (TSCs) on a signaling group. A

switched services request to run the TSC heartbeat test is also performed.

upgrade software

Simplex:

upgrade software to-version [version-override] [save-translation |

no-translation]

Duplex:

upgrade software to-version [call-override] [no-interchange]

[version-override] [preserve-calls | no-calls] [save-translation |

no-translation]

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-338upgrade software

This command is a single user command; that only status commands may be

executed while this command is running; all other commands will be blocked.

Parameters

Simplex: In a simplex system this command will result in translation being saved

to the primary device, followed by a reboot of the processor with loading

of the new software and translation data, and any field updates from the

primary MSS device. When completed, service is restored.

Duplex: In a duplicated SPE system, the upgrade software command will save

translation, reboot the standby SPE with new software from its primary

MSS device, load translations, apply any field updates, initiate an

interchange of the SPE’s, and begin providing service to the system.

Normally the interchange of the SPEs will result in minimal service

disruption. In cases where the new software load is incompatible with

the existing load, the system may perform a service-disrupting reboot.

to-version This qualifier identifies the software version. This qualifier is

checked against the data on the MSS device to verify that the

correct software version is being loaded and that the

software version is the same or newer that the version in

memory.

no-interchange This option is only available in duplicated systems and

provides the technician the ability to reboot the standby

processor with the software on the standby primary MSS

device, apply any field-updates and yet have the standby

SPE remain the standby.

The duplex default is to interchange the processors, upon a

successful boot of the standby SPE.

call-override This option is only available in duplicated systems and allows

the command to continue, even if the command will result in

a reset level 2 of the processor. Normally, the command

would print an error message if it was able to determine if the

reset was necessary. This reset would cause all calls in the

system to be dropped.

version-override This option allows the command to continue if the version

specified is older than the version in memory. This would

normally result in the command aborting because the

upgrade is not moving to a newer version of the software. If

the version-override option is used and the version on the

primary MSS device is older than the current version in

memory then the save translation step will be skipped.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-339upgrade software

Examples

Duplex

upgrade software DG3v02.03.0.01.0

upgrade software DG3v02.03.0.01.0 no-interchange no-translation

upgrade software DG3v02.03.0.01.0 call-override version-override

Input

Due to the complexity of this command and the options available, the system will

display the following screen and ask for input (ENTER or CANCEL) from the user to

either proceed with the command or to cancel the request.

The following display shows a typical result when upgrade software

DGv01.02.1.13.0 is entered on a system with simplex SPE:

save-translation This option will override the internal system and save

translation. The switch will not save translation if the version in

memory is newer than the version to be booted. With this

option the translation will be saved regardless of the software

version.

no-translation This option will cause the system not to save translation.

When the upgrade is from an older to a newer release, the

system will save translation, even if the translation is

incompatible between the two particular releases. There may

be rare occasions when there may be this incompatibility and

therefore this option will keep the translation from being

saved on the new version.

preserve-calls The system may automatically not preserve calls because of

the compatibility index, which signals a potential memory

mismatch across the processors. Compatibility index major

numbers must be identical, and the minor must either be

identical or greater going forward for the upgrade to

automatically be call preserving. This option will override the

software determination of call preservation, and force the

memory from the active to be sent to standby processor in an

attempt to preserve calls. This option should be used with

care, because attempting to preserve calls when the internal

memory layout is not compatible will result in processor

escalation to an eventual reboot.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-340upgrade software

The following display shows a typical result when upgrade software

DG3v01.02.1.13.0 is entered on a system with duplicated SPE.

If the user presses ENTER, then the command will proceed. If, however, the user

presses the CANCEL key then the command will be terminated.

Output

NOTE:

After initiating an upgrade software, do not touch the keyboard while

waiting for the command to execute. Entering a carriage return will cause

the progress and diagnostic messages to be lost. If the upgrade is

successful, Command successfully completed is

not

displayed.

Instead, the terminal is logged off the system and must be logged in again.

upgrade software DG3v01.02.1.13.0

This upgrade software command will result in the following actions:

From software version: DG3v01.02.1.13.0

To software version: DG3v01.03.4.13.0

Save CURRENT translation to MSS? yes

Press ENTER to continue or CANCEL to abort the command

upgrade software DG3v01.02.1.13.0

This upgrade software command will result in the following actions:

From software version: DG3v01.02.1.13.0

To software version: DG3v01.03.4.13.0

From compatibility index: 2.2

To compatibility index: 2.2

Save CURRENT translation to both active and standby MSS? yes

Attempt to preserve calls across interchange? yes

Press ENTER to continue or CANCEL to abort the command

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-341upgrade software

As the command progresses, results of each step are displayed with

corresponding error codes. The entire process takes about 10 minutes. While the

system is saving translations the following progress message is displayed and

updated every 10 seconds:

Maximum remaining translation save time: 03 mins 20 secs

A success or failure result is displayed. If the following message appears, system

software is corrupted; follow normal escalation procedures.

Error encountered; can’t complete request

Simplex SPE

The following display shows a typical result when upgrade software is executed

on a system with a simplex SPE.

Upgrade Step Each step in the upgrade execution is displayed after it occurs:

1. disable maintenance: This step prevents periodic

maintenance from interfering with the upgrade (similar to

the disable all command).

2. save translation: Saves a copy of the current translation to

the primary MSS device

3. reboot processor: Reboots the processor, causing a

temporary service outage.

4. If the upgrade is successful, Command successfully

completed is

not

displayed. Instead, the terminal is

logged off the system and must be logged in again.

Results This displays whether the step was successful or not. Possible

values are: PASS, FAIL, or SKIPPED. SKIPPED only occurs for

the save translation step when the current version is newer than

the version on the primary MSS device, causing this step to be

bypassed.

Error Code If a step fails, this field displays a code indicating the reason.

See the following table.

upgrade software

UPGRADE RESULTS

Upgrade Step Results Error Code

disable maintenance PASS

save translation PASS

reboot processor PASS

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-342upgrade software

Duplicated SPE

The following display shows a typical result when upgrade software is entered

on a system with duplicated SPE.

Upgrade Step Error

Code Description

Disable maintenance 6 Internal software error

Save translation 6 Internal software error

7 Storage device currently in use

8 Tape/disk access failure

9 Internal translation data is corrupted

10 Storage device has corrupted translation

2000 The save was not completed in the allotted time

6 Internal software error

Reboot processor 11 Could not load the boot image from the storage device

12 Could not reboot the processor

upgrade software

UPGRADE RESULTS

Upgrade Step Results Error Code

disable maintenance PASS

save translation PASS

busyout standby processor PASS

translation load and reboot standby PASS

change memory shadow bounds PASS

release standby processor PASS

refresh standby memory PASS

request an SPE interchange PASS

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-343upgrade software

Upgrade Step Each step in the upgrade execution is displayed after it occurs:

1. disable maintenance: This prevents periodic maintenance from

interfering with the upgrade (similar to the disable all command).

2. save translation: save a copy of the current translation to the primary

MSS device

3. busyout standby processor: This busies out the standby SPE,

preventing spontaneous interchanges while the new software load is

booted on the standby processor. This also turns off memory

shadowing from active memory to the standby.

4. translation load and reboot standby: This causes the standby

processor to load the boot image and translation on its primary

device. The SPE remains standby, and starts running the Standby

Maintenance Monitor (SMM).

5. change memory shadow bounds: This adjusts the range of memory

transmitted from the active to the standby SPE to include only the

information pertaining to active calls so as to preserve stable calls

across the interchange.

6. release standby processor: This releases the standby SPE from

busyout, allowing resumption of handshake and memory shadowing,

with transfer of active call status to the standby.

7. refresh standby memory: The system waits for refresh to complete

and reports the result.

8. request an SPE interchange: An interchange is executed into the

standby SPE with the new load. If this step succeeds, the terminal is

logged off. Otherwise, a failure code is returned.

9. If the upgrade is successful, Command successfully completed

not

displayed. Instead, the terminal is logged off the system and

must be logged in again.

Results Result of the execution of the corresponding step: PASS, FAIL, or

SKIPPED. SKIPPED occurs only for the save translation step when the

current version is newer than the version on the primary MSS device.

Error Code If a step fails, this field displays a code indicating the reason according

to Table 8-14:

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-344upgrade software

Table 8-14. Upgrade Software Error Codes—Duplicated SPE

Upgrade Step Error

Code Description

disable

maintenance 6 Internal software error

save translation 6 Internal software error

7 Storage device currently in use

8 Tape/disk access failure

9 Internal translation data is corrupted

10 Storage device has corrupted translation

2000 The save was not completed in the allotted time

busyout standby

processor 6 Internal software error

2010 Standby is already busied out

translation load

and reboot

standby

1 Could not create software processes on the standby

2 Not all processes on the standby were able to start

3 Standby LMM detected hardware failures on processor

complex

4 Software update file on standby corrupted

5 Translation on standby was not able to load correctly

6 Internal software error

2000 The load and reboot was not completed in the allotted

time, or communication with the standby was corrupted

2500 Internal software error with standby communication

change memory

shadow bounds 6 Internal software error

2500 Internal software error with standby communication

release standby

processor 6 Internal software error

2011 Standby processor was not busied out.

refresh standby

memory 6 Internal software error

2000 The refresh of the standby was not completed in the

allotted time

Continued on next page

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-345upgrade software

Feature Interactions

System Restarts

An upgrade causes in a system restart. For a complete description of effects,

see “Software Updates” in Chapter 6.

Error and Alarm Log

Error and alarm logs are cleared.

Busyouts

Maintenance objects that have been busied out by command are released

during the reboot or interchange. If the upgrade command is canceled, all

busyouts are preserved.

Multi-User Contention

While the upgrade command is executing, all other administration and

maintenance commands except status reports are blocked.

Periodic and Scheduled Maintenance

Periodic and scheduled maintenance are suspended while the upgrade

command is processing.

request an SPE

interchange 6 Internal software error

2000 The load and reboot was not completed in the allotted

time, or communication with the standby was corrupted

2300 Communication failure with standby resulted in

interchange failure

2360 LMM attempt to interchange processors failed

2500 Internal software error with standby communication

Table 8-14. Upgrade Software Error Codes—Duplicated SPE — Continued

Upgrade Step Error

Code Description

Continued on next page

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-346upgrade software

Command History Log

Unlike other commands, the upgrade software command is logged into the

history log

before

it completes, prior to the save translation step. A record of the

upgrade is saved on the new active SPE.

Alarm Origination

To prevent reporting of alarms generated by the upgrade, alarm origination is

suspended during the execution of the command. After a successful interchange

on a system with duplicated SPE, alarm origination remains suspended for

approximately 5 minutes, or until the newly active SPE is ready to begin normal

maintenance.

Enable All

All previously disabled maintenance objects are re-enabled following the

upgrade. If the command is canceled, disables are preserved.

Parameters

Output

The following display shows a typical result when busyout ds1-facility 2e1a is

entered.

UUCSSf The location of a DS1 Converter facility. F represents a letter (a-d)

used to identify the separate DS1 facilities connected to the DS1

Converter.

override This option must be used to busyout the facility on a DS1 Converter

that is carrying the packet traffic and control messages. See the

caution note above.

Port The DS1 facility as described above in UUCSSf.

busyout ds1-facility 02e01a

COMMAND RESULTS

Port Maintenance Name Alt. Name Result Error Code

02E01A DS1-FAC PASS

Command successfully completed

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-347upgrade software

For more information see the following sections at the beginning of this chapter:

‘‘Busyout and Release Commands’’ and ‘‘Common Output Fields’’.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Commands

Page 8-348upgrade software

Maintenance Object Repair Procedures

Page 9-1Escalation Procedures

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

9Maintenance Object Repair

Procedures

This document is intended for Release 5 and later systems only. For previous

DEFINITY systems (G3V4 and earlier), refer to

DEFINITY Enterprise

Communications Server Release 5.4 Maintenance for R5r

For maintenance Objects and Maintenance Commands for the DEFINITY

Wireless Business System (DWBS), refer to the appropriate maintenance

documentation that accompanies the DWBS.

Escalation Procedures

This document is not intended to solve all levels of trouble. When the limits of

these procedures have been reached and the problem has not been resolved, it

is the technician’s responsibility to escalate to a higher level of technical support.

Escalation should conform to the procedures in the

Technical and Administration

Plan

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Object Repair Procedures

Page 9-2ABRI-PORT (ASAI ISDN-BRI Port)

ABRI-PORT (ASAI ISDN-BRI Port)

Refer to BRI-PORT (ISDN-BRI Port) information for repair procedures.

1. The alarm level for ABRI ports may be administered using the set options command. The

alarm level can be set independently for off-board and on-board alarms to WARNING,

MINOR, or MAJOR for all ABRI ports in the system.

2. UU is the universal cabinet number (1 for PPN, 2 - 44 for EPNs). C is the carrier designation

(A, B, C, D, or E). SS is the number of the slot in which the circuit pack resides (01 to 21).

pp is the two digit port number (01, 02, ...).

MO Name (in

Alarm Log) Alarm Level Initial Command to Run Full Name of MO

ABRI-PORT 1MAJ/MIN/WRN test port UUCSSpp l 2ASAI ISDN-BRI Port

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Object Repair Procedures

Page 9-3AC-POWER

AC-POWER

AC Power for AC-Powered Systems

DEFINITY systems support two different cabinet types: Multi-Carrier Cabinets

and Single-Carrier Cabinets. Single-Carrier Cabinets are used only for EPNs.

Both cabinet types may be powered by either AC or DC power source.

Environmental maintenance differs according to cabinet type and power supply.

!CAUTION:

Before powering down a cabinet or carrier that contains DEFINITY AUDIX

circuit packs (TN566), first power down the AUDIX unit to avoid damaging

the AUDIX software. Instructions for powering down this unit are in the

‘‘DEFINITY AUDIX System Power Procedures’’ in Chapter 5, ‘‘Responding

to Alarms and Errors’’, on the circuit pack, and in DEFINITY AUDIX

documentation.

Single-Carrier Cabinet Power Systems

Each Single-Carrier Cabinet has one power supply that distributes DC power

and AC ringing voltage to the circuit pack slots in the cabinet.

AC Power Supply (WP-91153)

In an AC-powered cabinet, a single, plug-in, multi-output AC power supply is in

the power supply slot. A power cord, with a three-prong plug on one end and an

appliance connector on the other end, connects the supply to a dedicated AC

power source. The inputs to the power supply can be (depending on list version):

■120 VAC, 60 Hz, 15 Amp to 20 Amp; three wires in the power cord: one

hot wire, one neutral wire, and one ground wire

■220 VAC or 240 VAC, 50 Hz, 10 Amp; three wires in the power cord: one

hot wire, one neutral wire, and one ground wire

The AC power supply produces the following DC outputs: +5 VDC, -5 VDC,

-48 VDC, +12 VDC, and a battery-charging voltage. The DC outputs distribute

power on the cabinet backplane to the circuit pack slots.

1. UU is the universal cabinet number (1 for PPN, 2 - 44 for EPNs).

MO Name (in

Alarm Log) Alarm Level Initial Command to Run Full Name of MO

AC-POWER WARNING test environment UU1AC Power

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Object Repair Procedures

Page 9-4AC-POWER

The AC power supply also produces AC ringing voltage. The AC ringing voltage

output value and frequency depend on the country of use. The power supply has

a circuit breaker and EMI filtering.

Nominal Power Holdover

Multi-Carrier Cabinets

Two types of battery holdover are available:

■The small battery assembly provides short-term battery holdover. If AC

power fails, 48 VDC batteries power the system for 10 seconds in a PPN

cabinet, for 15 seconds in an EPN cabinet, and for 10 minutes in the

control carrier in a standard reliability system. The batteries also provide

system power for five minutes in the control carrier in high and critical

reliability systems, and for 10 minutes in the expansion control carrier in

the "A" position of an EPN cabinet (Release 5r only).

■Some AC-powered Multi-Carrier Cabinets contain three 48V batteries and

a battery charger (397C) to provide backup power in case power is

interrupted. The holdover times are identical to those above.

Single-Carrier Cabinets

A holdover circuit in the power supply allows a system to operate normally during

AC power interruptions. When AC input power fails, reserve batteries supply

power to the memory and processor circuit packs and fans for two minutes. All

port circuit packs are inactive during this time. The power supply contains a

battery charger to charge the holdover batteries.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Object Repair Procedures

Page 9-5AC-POWER

Error Log Entries and Test to Clear Values

System Technician-Demanded Tests:

Descriptions and Error Codes

Always investigate tests in the order shown in the table below. By clearing error

codes associated with the

Battery and Battery Charger Query Test

, for example,

you may also clear errors from other tests in the testing sequence. Refer to the

appropriate sections of this chapter for descriptions of each test.

NOTE:

The following tests apply to J58890CE, J58890CF, and J58890CH.

1. Run the Short Test Sequence first. If all tests pass, run the Long Test Sequence. Refer to the appropriate

test description and follow the recommended procedures.

Table 9-1. AC Power Error Log Entries

Error

Type Aux

Data Associated Test Alarm

Level On/Off

Board Test to Clear Value

010 Any Any Any test environment UU sh r 1

513 Any AC Power Query

Test (#78) WARNING OFF test environment UU sh r 1

Order of Investigation Short Test

Sequence Long Test

Sequence D/ND1

Battery & Battery Charger Query Test (#5) X X ND

AC Power Query Test (#78) X X ND

Power Unit Query Test (carrier E) (#127) X X ND

Power Unit Query Test (carrier D) (#127) X X ND

Power Unit Query Test (carrier A) (#127) X X ND

Power Unit Query Test (carrier B) (#127) X X ND

Power Unit Query Test (carrier C) (#127) X X ND

Emergency Transfer Query Test (#124) X X ND

Cabinet Temperature Query Test (#122) X X ND

External Alarm Lead Query Test (#120) X X ND

Analog Ring Generator Initialization Test (#117) X X ND

Analog Ring Generator Query Test (#118) X X ND

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Object Repair Procedures

Page 9-6AC-POWER

AC Power Query Test (#78)

This test queries the SYSAM in the PPN or the EPN maintenance circuit pack in

an EPN Multi-Carrier Cabinet system for the status of AC power to the cabinet.

1. D = Destructive; ND = Nondestructive

Table 9-2. TEST #78 Power Query Test

Error Code Test

Result Description/Recommendation

1000 ABORT System resources required to run test are not available (a)

100

2000 ABORT Response to the test request was not received within the allowable time

period (a)

1. If the test continues to ABORT with error code 2000, check for

system powering problems with the A carrier (PPN or EPN).

Resolve all AC-POWER and CARR-POW alarms. Then, repeat the

test.

2. If the test continues to ABORT with a 2000 error code, check for

and resolve all SYSAM errors in a PPN or MAINT errors (EPN

maintenance circuit pack) in an EPN. Then, repeat the test.

2029 2319

2320 2500 ABORT Internal system error

1FAIL

NOTE:

For a J58890CE, skip to step 2.

1. Procedures for a Global MCC (J58890CH):

a. For a nominal holdover system if there is no AC power at the

wall outlet, have a qualified electrician restore power to the

outlet. Power should range from 170 to 264 VAC.

b. If there is AC power at the wall outlet, then there could be a

problem with the RM0850 Rectifiers, BU3200A Battery Interface

Unit (BIU), or battery. Resolve all alarms logged against the

POWER maintenance object, and rerun the test. If the test still

fails, the BIU may be defective. Check the BIU. If the BOD

alarm LED is on, replace the BIU.

If the BOD LED is off and the BOK LED is on, then the SYSAM or

the EPN maintenance circuit pack may be incorrectly reporting

the problem. Resolve all alarms against these MOs and rerun

the test.

Continued on next page

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Object Repair Procedures

Page 9-7AC-POWER

Notes:

a. Retry the command at 1-minute intervals a maximum of 5 times.

(Continued) FAIL 2. Procedures for a J58890CE:

The cabinet is currently without AC power.

1. Check for AC at the wall outlet (99-127 VAC, or 200 - 250 VAC).

a. If there is no AC power at the wall outlet, then the problem is not

with the system itself. Power must be restored to the wall outlet.

b. If there is AC power at the wall outlet, then there could be a

problem with the Battery or Battery chargers. Resolve all alarms

logged against POWER (Battery & Battery Charger), and rerun

the test. If the test still fails, the fuse F5 may have opened.

!WARNING:

Turn off the 397C Battery Charger before inserting or

removing Fuse F5.

Replace fuse F5 and rerun the test. If the test still fails, then the

SYSAM or the EPN Maintenance circuit pack may be incorrectly

reporting the problem. Resolve all alarms against these MOs, and

rerun the test. There are failures that can occur on the SYSAM and

EPN Maintenance circuit pack that

will not

be detected by their

respective maintenance, but which will cause many, if not all,

environment tests to fail. If more than two environment tests are

failing, the suspect circuit pack, depending on the system

configuration, should be replaced and the test rerun.

100 FAIL The cabinet is currently without AC power, and AC power maintenance

is in the middle of timing the NPH interval.

1. Follow the repair steps for error code 1.

PASS The SYSAM in the PPN or the EPN MAINT (maintenance) circuit pack in

an EPN has reported that the cabinet has AC power. If there is no AC

power at the wall outlet, then look for and resolve all alarms against the

appropriate MO listed.

Table 9-2. TEST #78 Power Query Test — Continued

Error Code Test

Result Description/Recommendation

Continued on next page

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Object Repair Procedures

Page 9-8AC-POWER

AC-POWER for DC-Powered Systems

NOTE:

In a DC-powered Multi-Carrier Cabinet, the AC-POWER maintenance

object exists, but serves no functional purpose. Because the system cannot

determine the type of power used, the AC-POWER test should always pass

or abort. The maintenance strategy for power components in DC cabinets

is described in the ‘‘CARR-POW’’ section.

DEFINITY supports two different cabinet types: Multi-Carrier Cabinets and

Single-Carrier Cabinets. Single-Carrier Cabinets are used only for EPNs. Both

cabinet types may be powered by either AC or DC power source. Environmental

maintenance differs according to cabinet type and external power supply.

1. UU is the universal cabinet number (1 for PPN, 2 - 44 for EPNs).

MO Name (in

Alarm Log) Alarm

Level Initial Command to Run Full Name of MO

AC-POWER WARNING test environment UU1AC Power

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Object Repair Procedures

Page 9-9AC-POWER

Error Log Entries and Test to Clear Values

System Technician-Demanded Tests:

Descriptions and Error Codes

Always investigate tests in the order presented in the table below. By clearing

error codes associated with the

AC Power Query Test

, for example, you may also

clear errors generated from other tests in the testing sequence. Refer to the

appropriate sections of this chapter for descriptions of each test.

1. Run the Short Test Sequence first. If all tests pass, run the Long Test Sequence. Refer to the appropriate

test description and follow the recommended procedures.

1. D = Destructive; ND = Nondestructive

Table 9-3. AC Power Error Log Entries

Error

Type Aux

Data Associated Test Alarm

Level On/Off

Board Test to Clear Value

010 Any Any Any test environment UU sh r 1

513 Any AC Power Query

Test (#78) WARNING OFF test environment UU sh r 1

Order of Investigation Short Test

Sequence Long Test

Sequence D/ND1

Battery & Battery Charger Query Test (#5) X X ND

AC Power Query Test (#78) X X ND

Power Unit Query Test (carrier E) (#127) X X ND

Power Unit Query Test (carrier D) (#127) X X ND

Power Unit Query Test (carrier A) (#127) X X ND

Power Unit Query Test (carrier B) (#127) X X ND

Power Unit Query Test (carrier C) (#127) X X ND

Emergency Transfer Query Test (#124) X X ND

Cabinet Temperature Query Test (#122) X X ND

External Alarm Lead Query Test (#120) X X ND

Analog Ring Generator Initialization Test (#117) X X ND

Analog Ring Generator Query Test (#118) X X ND

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Object Repair Procedures

Page 9-10AC-POWER

AC Power Query Test (#78)

This test is not valid for DC-powered cabinets and should always abort or pass.

Notes:

a. Retry the command at 1-minute intervals a maximum of 5 times.

Table 9-4. TEST #78 Power Query Test

Error

Code Test

Result Description/Recommendation

1000 ABORT System resources required to run test are not available

100

2000 ABORT Response to the test request was not received within the allowable time

period

2029

2319

2320

2500

ABORT Internal system error (a).

Any FAIL The SYSAM in a PPN or the EPN Maintenance circuit pack in an EPN is

incorrectly reporting an AC power problem. If this test fails, there is a

problem with the SYSAM OR EPN Maintenance circuit pack. Replace the

suspect circuit pack and run the test again. (b)

PASS Since this test is invalid for DC-powered cabinets, this result simply

indicates that the SYSAM or EPN Maintenance circuit pack is handling this

test properly

Continued on next page

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Object Repair Procedures

Page 9-11ADM-CONN (Administered Connection)

ADM-CONN (Administered

Connection)

An administered connection provides an end-to-end connection between two

access endpoints or data modules on either the same or different switches. The

connection is automatically established when it is administered and scheduled to

be active.

An error is logged whenever an administered connection fails or cannot be

established. Failures to establish a connection generate an error whether they

occur on an initial try, a retry, a fast retry, a redial or an auto-restoration. A failed

connection generates an error whether or not the connection is subsequently

reestablished by fast retry, redial, or auto restoration.

An alarm is logged when an administered connection cannot be established

either initially or after failure of a connection. Both the alarm level (none to major)

and a failure threshold can be administered for each administered connection.

An alarm is raised when either of the following occurs:

■The number of consecutive failed attempts to establish a connection

reaches the administered threshold.

■Software determines that failure to establish a connection is due to a

mistake in administration. See Table 9-5.

Error Log Entries and Test to Clear Values

1. Where N is an administered connection number indicated in the PORT field of the Alarm or Error Log.

MO Name (in

Alarm Log) Alarm Level Initial Command to Run Full Name of MO

ADM-CONN MAJOR, MINOR,

or WARNING status administered-connection N 1Administered Connection

Table 9-5. Administered Connection Error Log Entries

Error Type Aux

Data Associated

Test Alarm

Level On/Off

Board Test to Clear

Value

0, or 29 Any None Any OFF None

1, or 28 (a,b) Any None Any OFF None

2 (c) Any None Any OFF None

6,21,31, or 127(d) Any None Any OFF None

Continued on next page

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Object Repair Procedures

Page 9-12ADM-CONN (Administered Connection)

For all ADM-CONN errors:

All of the above errors have no specific test associated with them and, except for

errors 17 and 127, are valid only for administered connections established over

ISDN-PRI facilities. Error 127 is valid for administered connections established

over non-ISDN facilities or between two endpoints on the same switch.

Notes:

a. These errors are typically associated with administration problems and

are not expected to be of a temporary nature. The administered

connection is not retried and the failure is alarmed immediately. The alarm

threshold specified by the customer is ignored.

b. The address of the destination endpoint is: an unassigned number (1),

has an invalid number format (28), or is restricted from terminating calls

due to Class of Restriction (‘‘Access Denied’’). Verify that the destination

address is correct and that the destination endpoint is administered. The

destination endpoint is not administered on the switch where this error is

logged.

c. A request has been made to use a transit network or common carrier that

cannot be accessed. Check the routing pattern used by this administered

connection and verify that the inter-exchange carrier specified is correct.

16 (a) Any None Any OFF None

17 (e) Any None Any OFF None

18, or 102 (f) Any None Any OFF None

22 (a,g) Any None Any OFF None

34,42,44, or 58 (h) Any None Any OFF None

38, or 41 (i) Any None Any OFF None

43, or 81 Any None Any OFF None

50 (a) Any None Any OFF None

52 (a) Any None Any OFF None

54 Any None Any OFF None

65,66, or 69 (a) Any None Any OFF None

82 Any None Any OFF None

88 (a) Any None Any OFF None

91,95,96,97,98,99,1

00, or 111 Any None Any OFF None

Table 9-5. Administered Connection Error Log Entries — Continued

Error Type Aux

Data Associated

Test Alarm

Level On/Off

Board Test to Clear

Value

Continued on next page

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Object Repair Procedures

Page 9-13ADM-CONN (Administered Connection)

d. The exact failure cause is unknown or has been mapped to one of these

values. If this is not a temporary condition, try reversing the direction of the

Administered Connection (originate the administered connection from the

destination switch). This may yield another failure cause.

e. The destination endpoint is not available. Check the status of the

destination endpoint at the far-end switch. The status for the destination

endpoint will not be available on the switch where this error is logged. At

the far end, use status access-endpoint or status data-module to see

whether the endpoint is busy, out-of-service or otherwise unavailable.

f. This switch sent an ISDN message to another switch, which either did not

respond (18) or did not respond within the allotted time (102). This could

be due to link failure or congestion or outage at the other switch.

g. The address of the destination endpoint has changed. Change the

administered connection accordingly. The destination endpoint will not be

administered on the switch where this error is logged.

h. These errors indicate that a resource (for example, a circuit or bearer

capability) required by the administered connection is not presently

available.

i. A network failure (38) or temporary failure (41) has occurred. Error Log

entries for other MOs (for example, DS1-BD) may indicate a local problem.

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Object Repair Procedures

Page 9-14ADX8D-BD (AUDIX Circuit Pack)

ADX8D-BD (AUDIX Circuit Pack)

The ADX8D-BD maintenance object represents a TN566/TN2169 DEFINITY

AUDIX circuit pack (sometimes called Embedded AUDIX) operating in

digital-port (DP) mode. For circuit-pack-level problems, see ‘‘XXX-BD (Common

Port Circuit Pack)’’. Port-level problems are covered by ADX8D-PT.

DEFINITY AUDIX consists of two circuit packs that occupy 5 slots on a port

carrier. The tests described in this manual apply only to switch-side maintenance

which tests circuit pack components related to the TDM bus interface. The

AUDIX system has an extensive maintenance strategy that is described in

DEFINITY AUDIX System Maintenance

, 585-300-110.

1. UU is the universal cabinet number (1 for PPN, 2 - 44 for EPNs). C is the carrier

designation (A, B, C, D, or E). SS is the number of the slot in which the circuit pack

resides (01 to 21).

MO Name (in

Alarm Log) Alarm Level Initial Command to Run1Full Name of MO

ADX8D-BD MINOR or

WARNING test board UUCSS sh AUDIX Circuit Pack

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Object Repair Procedures

Page 9-15ADX8D-PT (AUDIX Digital Port)

ADX8D-PT (AUDIX Digital Port)

The ADX8D-PT maintenance object represents a port on a TN566/TN2169

DEFINITY AUDIX circuit pack (sometimes called Embedded AUDIX) operating in

digital-port (DP) mode. The maintenance strategy for ports on the TN566

operating in control-link mode is described in ADX16A-PT.

The tests described in this section apply only to switch-side maintenance which

tests circuit pack components related to the TDM bus interface. The AUDIX

system has an extensive maintenance strategy that is described in

DEFINITY

AUDIX System Maintenance

, 585-300-110.

AUDIX resides on a combined pair of circuit packs: the TN566 Multifunction

Board (MFB) and the TN2169 Alarm Board (ALB). Because of its size this

combination occupies 5 slots, but only 1 slot is functional as far as the switch is

concerned. The other 4 slots are seen by the switch as ‘‘AUDIX-reserved’’ slots

(or ADXDP-RS/ADX8D-RS.)

In DP mode the TN566 pack supports up to 8 voice ports, each with a primary

information channel and a secondary information channel. Ports are

administered in increments of two. When a call to a station with an AUDIX login is

not answered, AUDIX answers the call using one of the available voice ports.

Unlike other AUDIX systems, DEFINITY AUDIX is not an adjunct.

!CAUTION:

Never do any of the following without first shutting down AUDIX. Follow

instructions on the TN566/TN2169 faceplate:

■

Remove DEFINITY AUDIX circuit packs

■

Cycle power to a carrier containing DEFINITY AUDIX circuit packs

■

Remove power to a carrier containing DEFINITY AUDIX circuit packs

1. UU is the universal cabinet number (1 for PPN, 2 - 44 for EPNs). C is the carrier

designation (A, B, C, D, or E).

is the number of the slot in which the circuit pack

resides (01 to 21).

is the two digit port number (01, 02, ...).

MO Name (in

Alarm Log) Alarm

Level Initial Command to

Run1Full Name of MO

ADX8D-PT MINOR test port UUCSSpp l AUDIX Digital Port

ADX8D-PT WARNING test port UUCSSpp sh AUDIX Digital Port

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Object Repair Procedures

Page 9-16ADX8D-PT (AUDIX Digital Port)

Error Log Entries and Test to Clear Values

Notes:

a. The user may experience a noisy port or link. This is an off-board problem

that is detected by the port circuit. If this problem exists, replace the

circuit pack (see caution at the beginning of this section). Once the

problem is resolved, the alarm is retired after a predetermined time.

b. At least 15 off-board problems have been detected with the link to the

voice port. When an error with the link is detected, an on-board counter is

incremented. Also see Note (a).

c. This is an internal type error that occurs when an audit request fails.

d. The port is busied-out by command. You can release the port via the

release port UUCSSpp command.

1. Run the Short Test Sequence first. If all tests pass, run the Long Test Sequence. Refer to the

appropriate test description and follow the recommended procedures.

2. Minor alarms on this MO may be downgraded to Warning alarms based on the values used in the

set options command.

Table 9-6. DEFINITY AUDIX Digital Port Error Log Entries

Error

Type Aux

Data Associated Test Alarm Level On/Off

Board Test to Clear Value

010 Any Any Any test port UUCSSpp sh r 1

1(a) 40987 None WARNING OFF

1(b) 1 to

20 None WARNING OFF

15(c) Any None

18(d) 0 busyout port

UUCSSpp WARNING OFF release port UUCSSpp

23(e) 0 None WARNING OFF

130(f) None WARNING ON test port UUCSSpp sh

257(g) 40971 None

513(h) Any None

1537(i) 40968 None WARNING OFF

1793 Voice & Ctrl. Local

Loop Test (#13) MIN/WRN2ON test port UUCSSpp l r 3

2049 NPE Crosstalk Test

(#9) MIN/WRN2ON test port UUCSSpp l r 3

2305(j) 40967 None

3840(k) 40965 None

3840(l) 41029 None

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Object Repair Procedures

Page 9-17ADX8D-PT (AUDIX Digital Port)

e. The circuit pack is administered but not physically installed. The alarm will

clear when a circuit pack is inserted.

f. The circuit pack has been removed or has been insane for more than

21-minutes. To clear the error, reinsert or replace the AUDIX circuit pack

(see pcaution at the beginning of this section).

g. Something is interfering with transmitting to the voice port. This is usually

an on-board problem and can be ignored if no user complaints are

received.

h. AUDIX is not available to the switch, possibly due to a busyout on the

AUDIX system. Check out the AUDIX system referring

DEFINITY AUDIX

System Maintenance

, 585-300-110, if necessary.

i. An in-line maintenance error has generated an off-board warning due to

some problem with the link to the voice port. This can be ignored if no user

complaints are received. If the problem persists, replace the circuit pack

(see precaution at the beginning of this section). Once the problem is

resolved, the alarm is retired after a certain period of time.

j. The link between the circuit pack and the voice port is successfully reset.

No craft action is necessary.

k. No voice ports are connected to the DEFINITY AUDIX circuit pack. No

maintenance action is required.

l. The message buffer in the circuit pack is full.

System Technician-Demanded Tests:

Descriptions and Error Codes

Always investigate tests in the order presented in the table below when you are

inspecting errors in the system. By clearing error codes associated with the

Voice and Control Channel Local Looparound Test

for example, you may also

clear errors generated from other tests in the testing sequence.

1. D = Destructive; ND = Nondestructive

Order of Investigation Short Test

Sequence Long Test

Sequence D/ND1

Voice and Control Channel Local Looparound

Test (#13) XND

NPE Crosstalk Test (#9) X ND

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Object Repair Procedures

Page 9-18ADX8D-PT (AUDIX Digital Port)

NO-OP Tests

The maintenance strategy for DEFINITY AUDIX emulates the one for DIG-LINE.

The tests listed below apply only to DIG-LINE and not to DEFINITY AUDIX. These

are referred to as

NO-OP

tests, and they always return PASS.

■Electronic Power Feed Test (#11)

■Station Lamp Updates Test (#16)

■Station (Digital) Audits Test (#17)

NPE Crosstalk Test (#9)

This test verifies that this port’s NPE channel talks on the selected time slot and

that it never crosses over to time slots reserved for other connections. If the NPE

is not working correctly, one-way and noisy connections may be observed. This

test is part of a port’s Long Test Sequence, and it takes about 20 to 30 seconds

to complete.

Crosstalk testing is performed on both the primary information channel (voice)

and on the secondary information channel (data) associated with each DEFINITY

AUDIX port. If this test fails on either channel, the voice port is taken

out-of-service.

Table 9-7. TEST #9 NPE Crosstalk Test

Error

Code Test

Result Description/Recommendation

1 ABORT During testing of the primary information channel, system resources may

not have been available. Also, the port may have been busy during the

test.

1. Check the port status. Use the display port UUCSSpp command to

determine the voice port extension of the port. Use the status station

command to determine the service state of the port. If the service state

indicates that the port is in use, you must wait until the port is idle.

When the port is idle, try (a).

2 ABORT System resources may not have been available, or the port may have been

busy during the test. Try (a).

1000 ABORT System resources required to run this test are not available. The port may

be in use. Use the display port UUCSSpp command to determine the

voice port extension of the port. Use the status station command to

determine the service state of the port. If the service state indicates that

the port is in use, you must wait until the port is idle before retesting. Try

(a).

1001 ABORT System resources required to run this test are not available. Try (a).

Continued on next page

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Object Repair Procedures

Page 9-19ADX8D-PT (AUDIX Digital Port)

Notes:

a. Retry the command at 1-minute intervals a maximum of 5 times.

Voice and Control Channel Local Loop Test (#13)

This test checks the information and control channels between the Switch

Processing Element (SPE) and the DEFINITY AUDIX port circuit. First, the

primary information (voice) channel loop back test is run.

1002 ABORT The system could not allocate time slots for the test. The system may be

under heavy traffic conditions, or it may have time slots out-of-service due

to TDM-BUS errors. Refer to TDM-BUS maintenance to diagnose any

active TDM-BUS errors.

1. If system has no TDM-BUS errors, and if it is not handling heavy traffic,

try (a).

1003 ABORT The system could not allocate a tone receiver for the test. The system may

be oversized for the number of Tone Detectors present, or some Tone

Detectors may be out-of-service.

1. Look for TTR-LEV errors in the Error Log. If present, refer to TTR-LEV.

2. Look for TONE-PT errors in the Error Log. If present, refer to TONE-PT.

Try (a).

1004 ABORT The port was put in use during the test. The test has been aborted. Use the

display port UUCSSpp command to determine the voice port extension of

the port. Use the status station command to determine the service state

of the port. If the port is in use, wait until the port is idle before testing.

1020 ABORT Test disabled by background testing. Use the status station command to

determine when the voice port is available for testing.

2000 ABORT Response to the test request was not received within the allowable time

period. Try (a).

2 FAIL The NPE of the tested port is transmitting in error. This causes noisy and

unreliable connections. Failure code 1 indicates that the Crosstalk test

failed on the primary channel. Failure code 2 indicates that the Crosstalk

test failed on the secondary channel.

1. Replace the circuit pack .

PASS The port is using its allocated time slots correctly.

1. To be sure that this is not an intermittent problem, repeat this test up to

a maximum of 10 times to make sure it continues to pass.

2. If complaints still exist, examine the connections.

Table 9-7. TEST #9 NPE Crosstalk Test — Continued

Error

Code Test

Result Description/Recommendation

Continued on next page

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Object Repair Procedures

Page 9-20ADX8D-PT (AUDIX Digital Port)

While the primary information channel is still looped around, the Control Channel

Looparound Test is performed. The Looparound Test for the secondary

information (data) channel is then performed. This test is the same as the primary

information channel loop around test.

Next, a Conference Test is implemented for the primary information channel. This

test is the same as Conference Test #6.

Only one value (Pass, Fail, or Abort) is generated as a result of the four tests run.

If any test fails or aborts, the sequence is stopped.

Table 9-8. TEST #13 Voice and Control Channel Local Loop Test

Error

Code Test

Result Description/Recommendation

ABORT Internal system error. Try (a) then (b).

1000 ABORT System resources required to run this test are not available. The port may

be in use. Use the display port UUCSSpp command to determine the

voice port extension of the port. Use the status station command to

determine the service state of the port. If the service state indicates that

the port is in use, you must wait until the port is idle before retesting. Try

(a).

1001 ABORT System resources required for this test are not available. Try (a).

1002 ABORT The system could not allocate time slots for the test. The system may be

under heavy traffic conditions, or may have time slots that are

out-of-service due to TDM-BUS errors. Refer to “TDM-BUS” to diagnose

TDM-BUS errors.

1. If the system has no TDM-BUS errors, and is not handling heavy

traffic, try (a).

1003 ABORT The system could not allocate a tone receiver for the test. The system may

be oversized for the number of Tone Detectors present, or some Tone

Detectors may be out-of-service.

1. Look for TTR-LEV errors in the Error Log. If present, refer to TTR-LEV

(TTR Level).

2. Look for TONE-PT errors in the Error Log. If present, refer to TONE-PT

(Tone Generator).

3. If neither condition exists, try (a).

1004 ABORT The port was put in use during the test. Use the display port UUCSSpp to

determine the voice port extension of the port. Use the status station

command to determine the service state of the port. If the service state

indicates that the port is in use, you must wait until the port is idle before

retesting. Try (a).

2000 ABORT Response to the test request was not received within the allowable time

period. Try (a).

2100 ABORT Could not allocate the necessary system resources to run this test. Try (a).

Continued on next page

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Object Repair Procedures

Page 9-21ADX8D-PT (AUDIX Digital Port)

7 FAIL Conference Test failed on the primary channel. Some users may not notice

a disruption in service. In extreme cases, the conferencing feature may

not work at all.

14 FAIL The primary voice channel is not transmitting properly. User impact may

range from no noticeable effect to loss of use of this port.

15 FAIL The control channel between the processor and DEFINITY AUDIX circuit

pack is not transmitting properly. User impact may range from no

noticeable effect to loss of use of this port. This failure could also be

disruptive to other users.

16 FAIL The secondary voice channel is not transmitting properly. User impact

may range from no noticeable effect to loss of use of this port.

None FAIL The test failed for reasons external to the DEFINITY AUDIX circuit pack.

1. Run circuit pack tests to check the Tone Generator circuit pack and

the Tone Detector circuit pack by using the test board UUCSS s

command.

2. Resolve any problems that are detected on the Tone Generator circuit

pack or Tone Detector circuit pack.

3. If the Tone Generator and Tone Detector circuit packs are functioning

properly, and if the test still fails, replace the DEFINITY AUDIX circuit

pack (see precaution at the beginning of this section).

PASS Voice and Control Channel Local Loop test passed. All channels are

transmitting properly.

1. To be sure that this is not an intermittent problem, repeat this test up

to 10 times and see if it continues to pass.

2. If complaints still exist, examine the connections.

Table 9-8. TEST #13 Voice and Control Channel Local Loop Test — Continued

Error

Code Test

Result Description/Recommendation

Continued on next page

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Object Repair Procedures

Page 9-22ADX16D-B (16 Port AUDIX Circuit Pack)

ADX16D-B (16 Port AUDIX Circuit

Pack)

The ADX16D-BD maintenance object represents a TN566/TN2169 DEFINITY

AUDIX circuit pack combination operating in 16 port mode digital (DP). For

circuit-pack-level problems, see “XXX-BD (Common Port Circuit Pack)”.

Port-level maintenance is covered by ADX16D-PT.

DEFINITY AUDIX consists of 2 circuit packs that occupy 5 slots on a port carrier.

The tests described in this manual apply only to switch-side maintenance which

tests circuit pack components related to the TDM bus interface. The AUDIX

system has an extensive maintenance strategy of its own that is described in

DEFINITY AUDIX System Maintenance

, 585-300-110.

1. UU is the universal cabinet number (1 for PPN, 2 - 44 for EPNs). C is the carrier

designation (A, B, C, D, or E). SS is the number of the slot in which the circuit pack

resides (01 to 21).

MO Name (in

Alarm Log) Alarm

Level Initial Command to Run1Full Name of MO

ADX16D-B MINOR test board UUCSS sh AUDIX Circuit Pack

ADX16D-B WARNING test board UUCSS sh AUDIX Circuit Pack

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Object Repair Procedures

Page 9-23ADX16A-BD (AUDIX Circuit Pack)

ADX16A-BD (AUDIX Circuit Pack)

The ADX16A-BD maintenance object represents a TN566/TN2169 DEFINITY

AUDIX circuit pack combination operating in control-link (CL) mode. For

circuit-pack-level problems, see “XXX-BD (Common Port Circuit Pack)”.

Port-level maintenance is covered by ADX16A-PT.

DEFINITY AUDIX consists of 2 circuit packs that occupy 5 slots on a port carrier.

The tests described in this manual apply only to switch-side maintenance which

tests circuit pack components related to the TDM bus interface. The AUDIX

system has an extensive maintenance strategy that is described in

DEFINITY

AUDIX System Maintenance

, 585-300-110.

1. UU is the universal cabinet number (1 for PPN, 2 - 44 for EPNs). C is the carrier designation

(A, B, C, D, or E). SS is the number of the slot in which the circuit pack resides (01 to 21).

MO Name (in

Alarm Log) Alarm Level Initial Command to Run1Full Name of MO

ADXCL-BD or

\ADX16A-BD MINOR, or

WARNINGS test board UUCSS sh AUDIX Circuit Pack

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Object Repair Procedures

Page 9-24ADX16D-P (16-Port AUDIX Digital Port)

ADX16D-P (16-Port AUDIX Digital

Port)

!CAUTION:

Never do any of the following without first shutting down AUDIX. Follow the

instructions on the TN566/TN2169 faceplate:

■

Remove DEFINITY AUDIX circuit packs

■

Cycle power to a carrier containing DEFINITY AUDIX circuit packs

■

Remove power to a carrier or cabinet containing DEFINITY AUDIX circuit

pack.

The ADX16D-P maintenance object represents a port on a TN566/TN2169

DEFINITY AUDIX circuit pack operating in digital-port (DP) mode. The

maintenance strategy for ports on the TN566 operating in control-link mode is

described in ADX16A-PT.

The tests described in this section apply only to switch-side maintenance which

tests circuit pack components related to the TDM bus interface. The AUDIX

system has an extensive maintenance strategy that is described in

DEFINITY

AUDIX System Maintenance

, 585-300-110.

AUDIX resides on a combined pair of circuit packs: the TN566 Multifunction

Board (MFB) and the TN2169 Alarm Board (ALB). Because of its size this

combination occupies 5 slots, but only 1 slot is functional as far as the system is

concerned. The other 4 slots are seen by the switch as ‘‘AUDIX-reserved’’ slots

(or ADX16-RES/ADX16D-RS).

In 16 Port DP mode, the TN566 pack supports up to 16 voice ports, each with a

primary information channel and a secondary information channel. Ports are

administered in increments of two. When a call to a station with an AUDIX login is

not answered, AUDIX answers the call using one of the available voice ports.

Unlike other AUDIX systems, DEFINITY AUDIX is not an adjunct.

1. UU is the universal cabinet number (1 for PPN, 2-44 for EPNs). C is the carrier

designation (A, B, C, D, or E). SS is the number of the slot in which the circuit pack

resides (01 to 21). pp is the two digit port number (01, 02, ...).

MO Name (in

Alarm Log) Alarm Level Initial Command to Run1Full Name of MO

ADX16D-P MINOR or

WARNINGS test port UUCSSpp l AUDIX Digital Port

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Object Repair Procedures

Page 9-25ADX16D-P (16-Port AUDIX Digital Port)

Error Log Entries and Test to Clear Values

Notes:

a. The user may experience a noisy port or link. This is an off-board problem

that is detected by the port circuit. If this problem exists, replace the

circuit pack (see caution at the beginning of this section). Once the

problem is resolved, the alarm is retired after a predetermined time.

b. At least 15 off-board problems have been detected with the link to the

voice port. When an error with the link is detected, an on-board counter is

incremented. Also see Note a, above.

c. This is an internal type error that occurs when an audit request fails.

1. Run the Short Test Sequence first. If all tests pass, run the Long Test Sequence. Refer to the

appropriate test description and follow the recommended procedures.

2. Minor alarms may be downgraded to Warning alarms based on the values used in the set options

command.

Table 9-9. DEFINITY AUDIX Digital Port Error Log Entries

Error

Type Aux

Data Associated

Test Alarm

Level On/Off

Board Test to Clear Value

010 Any Any Any test port UUCSSpp sh r 1

1(a) 40987 None WARNING OFF

1(b) 1 to 20 None WARNING OFF

15(c) Any None

18(d) 0 busyout port

UUCSSpp WARNING OFF release port UUCSSpp

23(e) 0 None WARNING OFF

130(f) None WARNING ON test port UUCSSpp sh

257(g) 40971 None

513(h) Any None

1537(i) 40968 None WARNING OFF

1793 Voice and

Control Local

Loop TEST

(#13)

MIN/ WRN2ON test port UUCSSpp l r 3

2049 NPE Crosstalk

Test (#9) MIN/ WRN2ON test port UUCSSpp l r 3

2305(j) 40967 None

3840(k) 40965 None

3840(l) 41029 None

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Object Repair Procedures

Page 9-26ADX16D-P (16-Port AUDIX Digital Port)

d. The port is busied-out by command. Release the port with the release

port UUCSSpp command.

e. The circuit pack is administered but not physically installed. The alarm will

clear when a circuit pack is inserted.

f. The circuit pack has been removed or has been insane for more than

21-minutes. To clear the error, reseat or replace the AUDIX circuit pack

(see caution at the beginning of this section).

g. Something is interfering with transmitting to the voice port. This is usually

an on-board problem and can be ignored if no user complaints are

received.

h. AUDIX is not available to the switch, possibly due to a busyout on the

AUDIX system. Refer to

DEFINITY AUDIX System Maintenance

585-300-110, if necessary.

i. An in-line maintenance error has generated an off-board warning due to

some problem with the link to the voice port. This can be ignored if no user

complaints are received. If the problem persists, replace the circuit pack

(see caution at the beginning of this section). Once the problem is

resolved, the alarm is retired after a certain period of time.

j. The link between the circuit pack and the voice port is successfully reset.

No craft action is necessary.

k. No voice ports are connected to the DEFINITY AUDIX circuit pack. No

maintenance action is required.

l. The message buffer in the circuit pack is full.

System Technician-Demanded Tests:

Descriptions and Error Codes

Always investigate tests in the order presented in the table below. By clearing

error codes associated with the

Voice and Control Channel Local Looparound

Test

for example, you may also clear errors generated from other tests in the

testing sequence.

1. D = Destructive; ND = Nondestructive

Order of Investigation Short Test

Sequence Long Test

Sequence D/ND1

Voice and Control Channel Local Looparound Test (#13) X ND

NPE Crosstalk Test (#9) X ND

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Object Repair Procedures

Page 9-27ADX16D-P (16-Port AUDIX Digital Port)

NO-OP Tests

The maintenance strategy for DEFINITY AUDIX emulates the one for DIG-LINE.

The tests listed below apply only to DIG-LINE and not to DEFINITY AUDIX. These

tests always return PASS.

■Electronic Power Feed Test (#11)

■Station Lamp Updates Test (#16)

■Station (Digital) Audits Test (#17)

■Digital Terminal Remote Looparound Test (1201)

NPE Crosstalk Test (#9)

This test verifies that this port’s NPE channel talks on the selected time slot and

that it never crosses over to time slots reserved for other connections. If the NPE

is not working correctly, one-way and noisy connections may be observed. This

test is part of a port’s Long Test Sequence, and it takes about 20 to 30 seconds

to complete.

Crosstalk testing is performed on both the primary information channel (voice)

and on the secondary information channel (data) associated with each DEFINITY

AUDIX port. If this test fails on either channel, the voice port is taken

out-of-service.

Table 9-10. TEST #9 NPE Crosstalk Test

Error

Code Test

Result Description/Recommendation

1 ABORT During testing of the primary information channel, system resources may

not have been available. Also, the port may have been busy during the test.

1. Check the port status. Use the display port UUCSSpp command to

determine the voice port extension of the port. Use the status station

command to determine the service state of the port. If the port is in use,

it is unavailable for this test. Wait until the port is idle (a).

2 ABORT System resources may not have been available, or the port may have been

busy during the test.

1. Check if port is being used try (a)

1000 ABORT System resources required to run this test are not available. The port may

be in use. Use the display port UUCSSpp command to determine the

voice port extension of the port. Use the status station command to

determine the service state of the port. If the port is in use, it is unavailable

for certain tests. Refer to “Status” commands in Chapter 8, for a full

description of all possible states. Wait until the port is idle before testing.

1. If the port status is idle, try (a)

1001 ABORT System resources required to run this test are not available. Try (a)

Continued on next page

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Object Repair Procedures

Page 9-28ADX16D-P (16-Port AUDIX Digital Port)

Notes:

a. Retry the command at 1-minute intervals a maximum of 5 times.

1002 ABORT The system could not allocate time slots for the test. The system may be

under heavy traffic conditions, or it may have time slots out-of-service due

to TDM-BUS errors. Refer to “TDM-BUS” to diagnose TDM-BUS errors.

1. If system has no TDM-BUS errors, and if it is not handling heavy traffic,

try (a)

1003 ABORT The system could not allocate a tone receiver for the test. The system may

be oversized for the number of tone detectors present, or some tone

detectors may be out-of-service.

1. Look for TTR-LEV errors in the Error Log. If present, refer to “TTR LEV”.

2. Look for TONE-PT errors in the Error Log. If present, refer to

“TONE-PT”.

1004 ABORT The port was put in use during the test. The test has been aborted. Use the

display port UUCSSpp command to determine the voice port extension of

the port. Use the status station command to determine the service state of

the port. If the port is in use, it is unavailable for certain tests. Refer to

“Status” commands in Chapter 8, ‘‘Maintenance Commands’’ for

explanations of all possible states. Wait until the port is idle before testing.

1020 ABORT Test disabled via background testing. Use the status station command to

determine when the voice port is available for testing.

2000 ABORT Response to the test request was not received within the allowable time

period (a)

2 FAIL The NPE of the tested port was found to be transmitting in error. This

causes noisy and unreliable connections. Failure code 1 indicates that the

Crosstalk test failed on the primary channel. Failure code 2 indicates that

the Crosstalk test failed on the secondary channel.

1. Replace the circuit pack (see caution at the beginning of this section).

PASS The port is using its allocated time slots correctly.

1. To be sure that this is not an intermittent problem, repeat this test up to

a maximum of 10 times to make sure it continues to pass.

2. If complaints still exist, examine the connections.

Table 9-10. TEST #9 NPE Crosstalk Test — Continued

Error

Code Test

Result Description/Recommendation

Continued on next page

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Object Repair Procedures

Page 9-29ADX16D-P (16-Port AUDIX Digital Port)

Voice and Control Channel Local Loop Test (#13)

This test checks the information and control channels between the Switch

Processing Element (SPE) and the DEFINITY AUDIX port circuit. The SPE sends

a message to loop around both the information and control channels for the port.

First, the primary information (voice) channel loop back test is run.

While the primary information channel is still looped around, the Control Channel

Looparound Test is performed. The Looparound Test for the secondary

information (data) channel is then performed. This test is the same as the primary

information channel loop around test.

Next, a Conference Test is implemented for the primary information channel. This

test is the same as Conference Test #6.

Only one value (Pass, Fail, or Abort) is generated as a result of the four tests run.

If any test fails or aborts, the sequence is stopped.

Table 9-11. TEST #13 Voice and Control Channel Local Loop Test

Error

Code Test

Result Description/Recommendation

ABORT Internal system error (a).

1000 ABORT System resources required to run this test are not available. The port may be in

use. Use display port UUCSSpp command to determine the voice port

extension of the port. Use status station command to determine the service

state of the port. Wait until the port is idle before testing. Try (a).

1001 ABORT System resources required to run this test are not available. Try (a)

1002 ABORT The system could not allocate time slots for the test. The system may be under

heavy traffic conditions, or it may have time slots that are out-of-service due to

TDM-BUS errors. Refer to “TDM-BUS” to diagnose TDM-BUS errors.

1. If the system has no TDM-BUS errors and if it is not handling heavy traffic,

try (a).

1003 ABORT The system could not allocate a tone receiver for the test. The system may be

oversized for the number of tone detectors present, or some tone detectors

may be out-of-service.

1. Resolve any “TTR-LEV” errors.

2. Resolve any “TONE-PT” errors. Try (a)

1004 ABORT The port was put in use during the test. The test has been aborted. Use display

port UUCSSpp to determine the voice port extension of the port. Use status

station command to determine the service state of the port. If the port is in use,

wait until the port is idle before retesting.

2000 ABORT Response to the test request was not received within the allowable time period.

Try (a).

2100 ABORT Could not allocate the necessary system resources for this test. Try (a).

Continued on next page

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Object Repair Procedures

Page 9-30ADX16D-P (16-Port AUDIX Digital Port)

Notes:

a. Retry the command at 1-minute intervals a maximum of 5 times.

7 FAIL Conference Test failed on the primary channel. In some cases, users may not

notice a disruption in service. In extreme cases, the conferencing feature may

not work at all.

14 FAIL The primary voice channel is not transmitting properly. User impact may range

from no noticeable effect to loss of use of this port.

15 FAIL The control channel between the processor and AUDIX is not transmitting

properly. User impact may range from no noticeable effect to loss of use of this

port. This failure could also be disruptive to other users.

16 FAIL The secondary voice channel is not transmitting properly. User impact may

range from no noticeable effect to loss of use of this port.

None FAIL The test failed for reasons external to the AUDIX.

1. Run circuit pack tests to check the tone generator circuit pack and the tone

detector circuit pack using test board UUCSS s.

2. Resolve any problems detected on the tone generator circuit pack or tone

detector circuit pack.

3. If the tone generator and tone detector circuit packs are functioning

properly, and if the test still fails, replace the AUDIX (see caution at the

beginning of this section).

PASS Voice and Control Channel Local Loop test passed. All channels are

transmitting properly.

1. To be sure that this is not an intermittent problem, repeat this test up to 10

times and see if it continues to pass.

2. If complaints still exist, examine the connections.

Table 9-11. TEST #13 Voice and Control Channel Local Loop Test — Continued

Error

Code Test

Result Description/Recommendation

Continued on next page

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Object Repair Procedures

Page 9-31ADX16A-PT (AUDIX Analog Line/Control Link)

ADX16A-PT (AUDIX Analog

Line/Control Link)

!CAUTION:

Never do any of the following without first shutting down AUDIX. Follow the

instructions on the TN566/TN2169 faceplate:

■

Remove DEFINITY AUDIX circuit packs

■

Cycle power to a carrier containing DEFINITY AUDIX circuit packs

■

Remove power to a carrier containing DEFINITY AUDIX circuit packs

The ADX16A-PT maintenance object represents a port on a TN566/TN2169

DEFINITY AUDIX circuit pack that is operating in control-link (CL) mode. For

circuit-pack-level problems (ADX16A-BD or ANL-16-BD), see “XXX-BD

(Common Port Circuit Pack)”. For port-level problems with AUDIX operating in

digital-port mode, see ADXDP-PT/ADX8D-PT.

The tests described in this section apply only to switch-side maintenance which

tests circuit pack components related to the TDM bus interface. The AUDIX

system has an extensive maintenance strategy that is described in

DEFINITY

AUDIX System Maintenance

, 585-300-110.

AUDIX resides on a combined pair of circuit packs: the TN566 Multifunction

Board (MFB) and the TN2169 Alarm Board (ALB). Because of its size this

combination occupies 5 slots, but only 1 slot is functional as far as the switch is

concerned. The other 4 slots are seen by the switch as ‘‘AUDIX-reserved’’ slots.

In CL mode the TN566 pack supports up to 16 voice ports. When a call to a

station with an AUDIX login is not answered, AUDIX answers the call using one of

the available voice ports.

Unlike other AUDIX systems, DEFINITY AUDIX is not an adjunct.

1. UU is the universal cabinet number (1 for PPN, 2 - 44 for EPNs). C is the carrier designation (A, B,

C, D, or E). SS is the number of the slot in which the circuit pack resides (01 to 21). pp is the two

digit port number (01, 02, ...).

MO Name (in

Alarm Log) Alarm

Level Initial Command to

Run1Full Name of MO

ADXCL-PT or

ADX16A-PT MINOR test port UUCSSpp l AUDIX Analog Line/ Control Link

ADXCL-PT or

ADX16A-PT WARNING test port UUCSSpp sh AUDIX Analog Line/ Control Link

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Object Repair Procedures

Page 9-32ADX16A-PT (AUDIX Analog Line/Control Link)

Error Log Entries and Test to Clear Values

Notes:

a. This is an in-line error and can only be resolved over time. This indicates

that no terminal equipment was present when ringing was attempted.

Execute the short test port UUCSSpp command.

b. The circuit pack has been logically administered but not physically

installed. The alarm will be cleared when the circuit pack is installed.

c. The circuit pack has been removed or has been insane for more than

11-minutes. To clear the error, reseat or replace the circuit pack.

d. This is an in-line error and can only be resolved over time. This error

indicates that ringing voltage is absent. If only one analog circuit pack in

the system has this problem, then replace the circuit pack. If only analog

circuit packs on a particular carrier have this error, then the ringing

generator may not be connected to this carrier. If analog circuit packs on

many carriers have this error, check the ringing generator.

e. AUDIX is not available to the switch. Check the AUDIX system, referring to

DEFINITY AUDIX System Maintenance

, 585-300-110.

f. The TDM bus is out of service. See the “TDM-BUS” section.

1. Run the Short Test Sequence first. If all tests pass, run the Long Test Sequence. Refer to the

appropriate test description and follow the recommended procedures.

2. Minor alarms on this MO may be downgraded to Warning alarms based on the values used in the

set options command.

Table 9-12. DEFINITY AUDIX Analog Line/Control Link Error Log Entries

Error

Type Aux

Data Associated Test Alarm

Level On/Off

Board Test to Clear Value

010 Any Any Any test port UUCSSpp sh r 1

1 (a) 40977 None

18 0 busyout station

extension

>WRN ON release station <

extension

23 (b) 0 None WRN OFF

130 (c) None WRN ON test port UUCSSpp sh

257 (d) 40973 None

513 (e) Any None

1025 (f) Looparound

Test (#161) MIN/

WRN2ON test port UUCSSpp l r 2

1281 Conference Test

(#7) MIN/

WRN2ON test port UUCSSpp l r 2

1537 NPE Crosstalk

Test (#6) MIN/

WRN2ON test port UUCSSpp l r 2

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Object Repair Procedures

Page 9-33ADX16A-PT (AUDIX Analog Line/Control Link)

System Technician-Demanded Tests:

Descriptions and Error Codes

Always investigate tests in the order presented in the table below. By clearing

error codes associated with the

Looparound Test #161

for example, you may

also clear errors generated from other tests in the testing sequence.

NO-OP Tests

The maintenance strategy for DEFINITY AUDIX emulates the one for ANL-16-L.

The tests listed below apply only to ANL-16-L and not to DEFINITY AUDIX. These

tests always return PASS.

■Battery Feed Test (#35)

■Audits and Updates Test (#36)

■Station Present Test (#48)

Tests 36 and 48 ABORT when AUDIX is not running.

NPE Crosstalk Test (#6)

This test verifies that this port’s NPE channel talks on the selected time slot and

never crosses over to time slots reserved for other connections. If the NPE is not

working correctly, one-way and noisy connections may be observed. This test is

part of the long test sequence and takes about 25 seconds to complete.

1. D = Destructive; ND = Nondestructive

Order of Investigation Short Test

Sequence Long Test

Sequence D/ND1

Looparound Test (#161) X ND

Conference Test (#7) X ND

NPE Crosstalk Test (#6) X ND

Table 9-13. TEST #6 NPE Crosstalk Test

Error

Code Test

Result Description/ Recommendation

ABORT Could not allocate the necessary system resources to run this test.1

Continued on next page

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Object Repair Procedures

Page 9-34ADX16A-PT (AUDIX Analog Line/Control Link)

1000 ABORT System resources required to run this test are not available. The port may

be busy with a valid call. Use the display port UUCSSpp command to

determine the station extension. Use the status station command to

determine the service state of the port. If the port is in use, it is unavailable

for certain tests. Wait until the port is idle before testing.1

1001 ABORT Could not allocate the necessary system resources to run this test.1

1002 ABORT The system could not allocate time slots for the test. The system may be

under heavy traffic conditions or it may have time slots out-of-service due to

TDM-BUS errors. Refer to TDM-BUS Maintenance documentation to

diagnose any active TDM-BUS errors.

1. If system has no TDM-BUS errors and is not handling heavy traffic,

then 1.

1003 ABORT The system could not allocate a tone receiver for the test. The system may

be oversized for the number of tone detectors present or some tone

detectors may be out-of-service.

1. Resolve any “TTR-LEV” errors.

2. Resolve any “TONE-PT” errors.1

1004 ABORT The port was seized by a valid call during the test. The test has been

aborted. Use the display port UUCSSpp command to determine the

station extension. Use the status station command to determine the

service state of the port. If the port is in use, it is unavailable for certain

tests. Wait until the port is idle before testing.1

1005 ABORT This condition indicates that the test is not applicable when the analog port

is used in a combined modem pool. This error can be ignored.

1018 ABORT Test disabled via administration.

1. To enable the test for the particular analog station being tested, enter

the change station <extension> command and change the ‘‘Test?’’

field on the Station Form from ‘‘n’’ to ‘‘y.’’

2000 ABORT Response to the test request was not received within the allowable time

period.

2012 ABORT System could not respond to this request.

2100 ABORT Could not allocate the necessary system resources to run this test.1

Table 9-13. TEST #6 NPE Crosstalk Test — Continued

Error

Code Test

Result Description/ Recommendation

Continued on next page

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Object Repair Procedures

Page 9-35ADX16A-PT (AUDIX Analog Line/Control Link)

Conference Circuit Test (#7)

This test verifies that the NPE channel for the port being tested can correctly

perform the conferencing function.

1. Retry the command at 1-minute intervals a maximum of 5 times.

Any FAIL The NPE of the tested port was found to be transmitting in error. This

causes noisy and unreliable connections.

1. Replace the circuit pack.

PASS The port is correctly using its allocated time slots. User-reported troubles

on this port should be investigated by using other port tests, by examining

station wiring, or by examining the station.

Table 9-14. TEST #7 Conference Circuit Test

Error

Code Test

Result Description/Recommendation

ABORT Could not allocate the necessary system resources to run this test. (a)

1000 ABORT System resources required to run test are not available. The port may be busy

with a valid call. Use the display port UUCSSpp command to determine the

station extension. Use the status station command to determine the service

state of the port. If the port is in use, wait until it is idle before retesting.(a)

1004 ABORT The port was seized by a valid call during the test. The test has been aborted.

Use the display port UUCSSpp command to determine the station extension.

Use the status station command to determine the service state of the port. If

the port is in use, wait until it is idle before testing. Try (a).

1018 ABORT Test disabled by administration. This only applies to analog stations.

1. To enable the test for the analog station being tested, enter the change

station <extension> command and change the ‘‘Test?’’ field on the Station

Form from ‘‘n’’ to ‘‘y.’’

2000 ABORT Response to the test request was not received within the allowable time period.

Continued on next page

Table 9-13. TEST #6 NPE Crosstalk Test — Continued

Error

Code Test

Result Description/ Recommendation

Continued on next page

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Object Repair Procedures

Page 9-36ADX16A-PT (AUDIX Analog Line/Control Link)

Notes:

a. Retry the command at 1-minute intervals a maximum of 5 times.

Looparound Test (#161)

This test is designed to check the on-board transmission capabilities of the NPE

on the analog port.

2100 ABORT Could not allocate the necessary system resources for this test. Try (a).

Any FAIL The NPE of the tested port did not conference the tones correctly. This causes

noisy and unreliable connections.

1. Replace the circuit pack.

PASS The port can correctly conference multiple connections. User-reported troubles

on this port should be investigated by using other port tests and by examining

station, trunk, or external wiring.

Table 9-15. TEST #161 Looparound Test

Error

Code Test

Result Description/ Recommendation

ABORT Could not allocate the necessary system resources for this test. Try (a).

1000 ABORT System resources required to run this test are not available. The port may be

busy with a valid call. Use the display port UUCSSpp command to

determine the station extension. Use the status station command to

determine the service state of the port. If the port is in use, wait until it is idle

before testing.

1. If the port status is idle, try (a).

1002 ABORT The system could not allocate time slots for the test. The system may be

under heavy traffic conditions or it may have time slots out-of-service due to

TDM-BUS errors. Refer to “TDM-BUS” to diagnose TDM-BUS errors.

1. If system has no TDM-BUS errors and is not handling heavy traffic, try (a).

Continued on next page

Table 9-14. TEST #7 Conference Circuit Test — Continued

Error

Code Test

Result Description/Recommendation

Continued on next page

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Object Repair Procedures

Page 9-37ADX16A-PT (AUDIX Analog Line/Control Link)

Notes:

a. Retry the command at 1-minute intervals a maximum of 5 times.

1003 ABORT The system could not allocate a tone receiver for the test. The system may be

oversized for the number of tone detectors present or some tone detectors

may be out-of-service.

1. Resolve any “TTR-LEV” errors.

2. Resolve any “TONE-PT” errors.

3. If neither condition exists, try (a).

1004 ABORT The port was seized by a valid call during the test. The test has been aborted.

Use the display port UUCSSpp command to determine the station

extension. Use the status station command to determine the service state of

the port. If the port is in use, wait until the port is idle before testing. Try (a).

1018 ABORT Test disabled by administration. To enable the test for the particular analog

station, enter the change station <extension> command and change the

‘‘Test?’’ field on the Station Form from ‘‘n’’ to ‘‘y.’’

2000 ABORT Response to the test was not received within the allowable time period.

2100 ABORT Could not allocate the necessary system resources to run this test. Try (a).

FAIL The reflective Looparound Test failed. This causes noisy or unreliable

connections or other users calling this port may hear an echo.

1. Replace the circuit pack.

PASS The port is able to provide an analog transmission path to the station

equipment. User-reported troubles on this port should be investigated by

using other port tests, by examining station wiring, or by examining the

station.

Table 9-15. TEST #161 Looparound Test — Continued

Error

Code Test

Result Description/ Recommendation

Continued on next page

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Object Repair Procedures

Page 9-38ALARM-PT (ALARM PORT)

ALARM-PT (ALARM PORT)

The Alarm Port MO provides on-board maintenance for an analog line port that is

administered as an external device alarm port. Test are provided to verify the

analog line ports ability to detect an external device alarm. The external device

alarm (EXT-DEV) MO is used for the off-board external device alarm.

Error Log Entries and Test to Clear Values

Notes:

a. This is a software audit error that does not indicate any hardware

malfunction. Run Short Test Sequence and investigate errors.

1. UU is the universal cabinet number (1 for PPN, 2 -44 for EPNs). C is the carrier

designation (A, B, C, D, or E). SS is the number of the slot in which the circuit pack

resides (01 to 21). pp is the two digit port number (01, 02, ...).

1. Run the Short Test Sequence first. If all tests pass, run the Long Test Sequence. Refer to the

appropriate test description and follow the recommended procedures

MO Name (in

Alarm Log) Alarm

Level Initial Command to

Run1Full Name of MO

ALARM-PT MIN test port UUCSSpp l Alarm-Port

ALARM-PT WRN test port UUCSSpp sh Alarm-Port

Table 9-16. 8-Port Analog Line Error Log Entries

Error

Type Aux

Data Associated Test Alarm

Level On/Off

Board Test to Clear Value

010 Any Any Any test port UUCSSpp sh r 1

15 (a) Any Audits and

Updates Test

(#36)

18 0 busy-out station

extension

WARNIN

GOFF release station

extension

130 (b) None WARNIN

GON test port UUCSSpp sh

769 Battery Feed

Test (#35) MINIOR ON test port UUCSSpp sh r 2

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Object Repair Procedures

Page 9-39ALARM-PT (ALARM PORT)

b. Indicates that the circuit pack has been removed or has been insane for

more than 11-minutes. To clear the error, reseat or replace the circuit

pack.

System Technician-Demanded Tests:

Descriptions and Error Codes

Always investigate tests in the order presented in the table below. By clearing

error codes associated with the

Battery Feed Test

, for example, you may also

clear errors generated from other tests in the testing sequence.

Battery Feed Test (also called Port Diagnostic

Test) (#35)

The battery feed chip provides power to the telephone equipment, signaling,

rotary dial pulsing, transmission, and balance. This test checks the signaling and

switchhook capabilities of the battery feed chip by terminating the port, applying

battery, and trying to detect a current.

1. D = Destructive; ND = Nondestructive

Order of Investigation Short Test

Sequence Long Test

Sequence D/ND1

Battery Feed Test (#35) X X ND

Station Status and Translation Audits and Updates

Test (#36) XXND

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Object Repair Procedures

Page 9-40ALARM-PT (ALARM PORT)

Note:

a. Retry the command at 1-minute intervals a maximum of 5 times.

Station Status and Translation Audits and

Updates Test (#36)

For an analog line port that is administered as an external alarm, this test is

limited to updating the software with the switchhook state.

Table 9-17. TEST #35 Battery Feed Test

Error

Code Test

Result Description/Recommendation

ABORT Could not allocate the necessary system resources to run this test. Try (a).

1000 ABORT System resources required to run this test are not available. The port may be

reporting an external device alarm.

1. Enter test external-device-alarm port UUCSSpp to determine if the port

is reporting an EXT-DEV failure before retesting.

2. When the port has no EXT-DEV failure, try (a).

1004 ABORT The port received an EXT-DEV failure during the test. The test has been

aborted.

1. Enter test external-device-alarm port UUCSSpp to determine if the port

is reporting an EXT-DEV failure before retesting.

2. If the port has no EXT-DEV failure, try (a).

2000 ABORT Response to the test request was not received within the allowable time

period.

2100 ABORT Could not allocate the necessary system resources to run this test. Try (a).

FAIL The port’s battery feed chip is unable to supply sufficient power to sense the

external device alarm. This may occur when the test is performed at the same

time that the external device contact closure occurred.

1. Enter test external-device-alarm port UUCSSpp to determine if the port

is reporting an EXT-DEV failure before retesting. Wait until the port has no

EXT-DEV failure before retesting. Try (a).

PASS The port’s battery feed chip is able to provide power to the external device

alarm to detect contact closure.

Continued on next page

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Object Repair Procedures

Page 9-41ALARM-PT (ALARM PORT)

Note:

a. Retry the command at 1-minute intervals a maximum of 5 times.

Table 9-18. TEST #36 Station Status and Translation Audits and Updates

Error

Code Test

Result Description/Recommendation

ABORT Could not allocate the necessary system resources to run this test. Try (a).

1004 ABORT The port received an EXT-DEV failure during the test. The test has been

aborted.

1. Enter test external-device-alarm port UUCSSpp to determine if the

port is reporting an EXT-DEV failure before retesting.

2. If the port has no EXT-DEV failure, try (a).

1006 ABORT This port has been busied out by command.

1. Check Error Log for Error Type 18 (port busied out). If present, release

the port with the release port UUCSSpp command and run the test

again.

2000 ABORT Response to the test request was not received within the allowable time

period.

2100 ABORT Could not allocate the necessary system resources to run this test. Try (a).

1 FAIL This failure does not indicate a hardware problem. The switchhook audit

failed, this condition may occur when the audit is performed at the same

time that the terminal equipment goes off-hook.

1. Enter test external-device-alarm port UUCSSpp to determine if the

port is reporting an EXT-DEV failure before retesting. Wait until the port

has no EXT-DEV failure before retesting

2. If the port has no EXT-DEV failure, try (a).

7 FAIL The translation update failed. This does not indicate a hardware problem

but may be an internal software error.

PASS The software and the port processor have the same status.

Continued on next page

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Object Repair Procedures

Page 9-42ANL-16-L (16-Port Analog Line)

ANL-16-L (16-Port Analog Line)

The circuit packs listed below provide 16 analog line ports for single-line voice

terminals. The table indicates which circuit packs are equipped with lightning

protection (for off-premises (out-of -building) stations), and which ones support

the neon message waiting lamp feature.

No maintenance of the terminal connected to the 16-Port Neon Analog Line

circuit pack is performed, except to determine whether or not the terminal is

connected. Failures of the neon message waiting lamp power and the common

ringing application circuitry are reported as part of common port circuit pack

errors; see errors 1281 and 1793 in the “XXX-BD (Common Port Circuit Pack)”

section.

Ringing Caused by Maintenance Testing

Test #48 may cause some terminal equipment to ring briefly during daily

maintenance. If this ringing is disturbing the customer or the terminal equipment,

it should be disabled in the Tests field of the change station extension form. Be

aware that this action will also disable Tests #6, 7, 161 and 35.

1. UU is the universal cabinet number (1 for PPN, 2 -44 for EPNs). C is the carrier

designation (A, B, C, D, or E). SS is the number of the slot in which the circuit pack resides

(01 to 21). pp is the two digit port number (01, 02, ...).

MO Name (in

Alarm Log) Alarm Level Initial Command to

Run1Full Name of MO

ANL-16-L MIN test port UUCSSpp l 16-Port Analog Line

ANL-16-L WRN test port UUCSSpp sh 16-Port Analog Line

16-Port Analog Line Circuit Packs

Circuit

Pack Off-

Premises Neon

TN468B y

TN479

TN746 y

TN746B y y

TN2135 y

TN2144 y

TN2149 y

TN2180 y

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Object Repair Procedures

Page 9-43ANL-16-L (16-Port Analog Line)

Error Log Entries and Test to Clear Values

Notes:

a. These are in-line errors and can only be resolved over time.

■40960 indicates that too many simultaneous incoming ringing

attempts were made on this board. Only 4 ports on a board may

ring simultaneously. A 5th incoming call will cause an inline error

from the board.

1. Run the Short Test Sequence first. If all tests pass, run the Long Test Sequence. Refer to the

appropriate test description and follow the recommended procedures.

2. Minor alarms on this MO may be downgraded to Warning alarms based on the values used in the

set options command.

Table 9-19. 16-Port Analog Line Error Log Entries

Error

Type Aux

Data Associated

Test Alarm

Level On/Off

Board Test to Clear Value

010 Any Any Any test port UUCSSpp sh r 1

1(a) 40960

40975

40977

none

15(b) Any Audits and

Updates Test

(#36)

18 0 busy-out

station

extension

WRN ON release station

extension

130(c) None WRN ON test port UUCSSpp sh

257(d) 40973 none

513(e) Station

Present Test

(#48)

WRN OFF test port UUCSSpp sh r 2

769 Battery Feed

Test (#35) MIN/ WRN2ON test port UUCSSpp sh r 2

1025 Looparound

Test (#161) MIN/ WRN2ON test port UUCSSpp l r 2

1281 Conference

Test (#7) MIN/ WRN2ON test port UUCSSpp l r 2

1537 NPE

Crosstalk Test

(#6)

MIN/ WRN2ON test port UUCSSpp l r 2

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Object Repair Procedures

Page 9-44ANL-16-L (16-Port Analog Line)

■40975 indicates that the terminal equipment was on-hook when

ring-tip was detected during ringing. This usually indicates a failure

in the terminal equipment or the type of terminal has a low ringer

impedance. Call the terminal equipment and verify that the terminal

rings. If the terminal does not ring, then replace it. Otherwise, issue

the test port UUCSSpp command, and follow the procedure for

Test #48.

■40977 indicates that no terminal equipment was connected when

ringing was attempted. Run the short test via the test port

UUCSSpp command, and follow the procedure for the results of

Test #48.

b. This is a software audit error that does not indicate any hardware

malfunction. Run Short Test Sequence and investigate associated errors.

c. This error type indicates that the circuit pack has been removed or has

been insane for more than 11-minutes. To clear the error, reseat or replace

the circuit pack.

d. This is an in-line error and can only be resolved over time. This error

indicates that ringing voltage is absent. If only 1 analog circuit pack in the

system has this problem, then replace the circuit pack. If only analog

circuit packs on a particular carrier have this error, then the ringing

generator may not be connected to this carrier. If analog circuit packs on

many carriers have this error, then it is probably a problem with the ringing

generator.

e. Test #48 may cause some terminal equipment to ring briefly during daily

maintenance. If this disturbs the customer or the terminal equipment,

disable it by setting the Tests field on the change station extension form

to n. On some software releases, this will also disable Tests #6, 7, 161,

and 35.

System Technician-Demanded Tests:

Descriptions and Error Codes

Always investigate tests in the order presented in the table below when

inspecting errors in the system. By clearing error codes associated with the

Battery Feed Test,

for example, you may also clear errors generated from other

tests in the testing sequence.

Order of Investigation Short Test

Sequence Long Test

Sequence D/ND1

Battery Feed Test (#35) X X ND

Station Present Test (#48) X X ND

Looparound Test (#161) X ND

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Object Repair Procedures

Page 9-45ANL-16-L (16-Port Analog Line)

NPE Crosstalk Test (#6)

This test verifies that this port’s NPE channel talks on the selected time slot and

never crosses over to time slots reserved for other connections. If the NPE is not

working correctly, one-way and noisy connections may be observed. This test is

usually part of the long test sequence and takes about 20 to 30 seconds to

complete.

1. D = Destructive; ND = Nondestructive

Conference Test (#7) X ND

NPE Crosstalk Test (#6) X ND

Station Status and Translation Audits and Updates Test

(#36) XXND

Table 9-20. TEST #6 NPE Crosstalk Test

Error

Code Test

Result Description/Recommendation

ABORT Could not allocate the necessary system resources to run this test. Try (a).

1000 ABORT System resources required to run test are not available. The port may be

busy with a valid call. This result is also reported for the system’s

Music-On-Hold port when it is off-hook, which it usually is.

1. Enter display port UUCSSpp to determine the station’s extension.

Enter status station extension to determine the service state of the

port. If the port is in use, wait until the port is idle. Try (a).

1001 ABORT System resources required to run test are not available. This could be due

to a failure to seize the port. Try (a).

1002 ABORT The system could not allocate time slots for the test. The system may be

under heavy traffic conditions or have time slots out-of-service due to

TDM-BUS errors. Refer to “TDM-BUS” to diagnose any active TDM-BUS

errors.

1. If system has no TDM-BUS errors and is not handling heavy traffic, try

(a).

Continued on next page

Order of Investigation Short Test

Sequence Long Test

Sequence D/ND1

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Object Repair Procedures

Page 9-46ANL-16-L (16-Port Analog Line)

1003 ABORT The system could not allocate a tone receiver for the test. The system may

be oversized for the number of tone detectors present or some tone

detectors may be out-of-service.

1. Look for TTR-LEV errors in the Error Log. If present, refer to “TTR-LEV”.

2. Look for TONE-PT errors in the Error Log. If present, refer to

“TONE-PT”.

3. If neither condition exists, try (a).

1004 ABORT The port was seized by a valid call during the test. The test has been

aborted. Use the display port UUCSSpp command to determine the

station extension. Use the status station command to determine the

service state of the port. If the port is in use, wait until the port is idle before

testing. Try (a).

1005 ABORT The test was aborted due to a configuration problem. This test may not be

applicable, or it may be disruptive to terminal equipment other than a voice

terminal (for example, the modem pool member or Music On Hold).

1018 ABORT The test has been disabled by administration. The default for the “Test”

field on the “Station” form is “y”. Determine why this field has been set to “n”

on this station (this may be due to the ringing application test 48, that can

be customer or terminal disturbing).

1. To enable the test for a particular station being tested, enter change

station extension and set the “Test?” field on the station from “n” to

“y.”

2000 ABORT Response to the test request was not received within the allowable time

period.

2100 ABORT System resources required to run test are not available. This could be due

to a failure to seize the port. Try (a).

Any FAIL This test can fail due to on-board or off-board problems. Off-board

problems include EXP-PN and EXP-INTF faults, TDM-BUS faults, and faults

associated with the tone detectors/tone generators. Clear all off-board

problems before replacing the board. A TDM-BUS problem is usually the

result of a faulty board connected to the backplane, or bent pins on the

backplane.

1. Look for EXP-PN and/or EXP-INTF errors in the error log. If present,

refer to “EXP-PN” and “EXP-INTF”.

2. Look for TDM-BUS errors in the error log. If present, refer to

“TDM-BUS”.

3. Look for TONE-BD and/or TONE-PT errors in the error log. If present,

refer to “TONE-BD” and “TONE-PT”.

4. Test the board when the faults from Steps 1, 2, and 3 are cleared.

Replace the board only if the test fails.

Table 9-20. TEST #6 NPE Crosstalk Test — Continued

Error

Code Test

Result Description/Recommendation

Continued on next page

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Object Repair Procedures

Page 9-47ANL-16-L (16-Port Analog Line)

Notes:

a. Retry the command at 1-minute intervals a maximum of 5 times.

Conference Circuit Test (#7)

This test verifies that the NPE channel for the port being tested can correctly

perform the conferencing function.

PASS The port is correctly using its allocated time slots. User-reported troubles

on this port should be investigated by using other port tests, by examining

station wiring, or by examining the station.

0NO

BOARD The test could not relate the internal ID to the port (no board). This could be

due to incorrect translations, no board is inserted, an incorrect board is

inserted, or an insane board is inserted.

1. Check to ensure that the board translations are correct. Use the list

config command, and resolve any problems.

2. If the board was found to be correctly inserted in step 1, issue the

busyout board command.

3. Issue the reset board command.

4. Issue the release busy board command.

5. Issue the test board long command. This should re-establish the

linkage between the internal ID and the port. If this is not the case,

check to ensure that there is a valid board inserted.

Table 9-20. TEST #6 NPE Crosstalk Test — Continued

Error

Code Test

Result Description/Recommendation

Continued on next page

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Object Repair Procedures

Page 9-48ANL-16-L (16-Port Analog Line)

Table 9-21. TEST #7 Conference Circuit Test

Error

Code Test

Result Description/Recommendation

ABORT Could not allocate the necessary system resources to run this test. Try (a).

1000 ABORT System resources required to run this test are not available. The port may be

busy with a valid call. This result is also reported for the system’s

Music-On-Hold port when it is off-hook, which it usually is.

1. Enter display port UUCSSpp to determine the station’s extension.

Enter status station extension to determine the service state of the

port. If the port is in use, wait until the port is idle and try (a).

1004 ABORT The port was seized by a valid call during the test. The test has been

aborted. Use the display port UUCSSpp command to determine the station

extension. Use the status station command to determine the service state

of the port. If the port is in use, wait until the port is idle and try (a).

1005 ABORT The test was aborted due to a configuration problem. This test may not be

applicable, or it may be disruptive to terminal equipment other than a voice

terminal (for example, the modem pool member or Music On Hold).

1018 ABORT The test has been disabled via administration. The default for the “Test” field

on the “Station” form is “y”. Determine why this field has been set to “n” on

this station (this may be due to the ringing application test 48, which can be

customer or terminal disturbing).

1. To enable the test for the particular analog station being tested, enter

change station extension and set the “Test?” field on the station from

“n” to “y.”

2000 ABORT Response to the test request was not received within the allowable time

period.

2100 ABORT System resources required to run this test are not available.

1. Look for TONE-PT errors in the error log. If present, refer to “TONE-PT”.

2. If there are no TONE-PT errors in the error log, try (a).

Continued on next page

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Object Repair Procedures

Page 9-49ANL-16-L (16-Port Analog Line)

Notes:

a. Retry the command at 1-minute intervals a maximum of 5 times.

Battery Feed Test (also called Port Diagnostic

Test) (#35)

The battery feed chip provides power to the telephone equipment, signaling,

rotary dial pulsing, transmission, and balance. This test checks the signaling and

switchhook capabilities of the battery feed chip by terminating the port, applying

battery and detecting the resulting current.

For the TN746B, Test #35 does not actually run and instead always returns PASS.

Test #35 operates in the normal manner for TN746.

Any FAIL The NPE of the tested port did not conference the tones correctly. This will

cause noisy and unreliable connections.

1. Issue the display port and the status station commands to determine

if the station is idle. If the station is idle, issue the test port command for

this port.

2. If the test continues to fail, issue the busyout port and the release port

commands, and then retest.

3. If the test still fails, replace the board.

PASS The port can correctly conference multiple connections. User-reported

troubles on this port should be investigated by using other port tests and by

examining station, trunk, or external wiring.

0NO

BOARD The test could not relate the internal ID to the port (no board). This could be

due to incorrect translations, no board is inserted, an incorrect board is

inserted, or an insane board is inserted.

1. Check to ensure that the board translations are correct. Use the list

config command, and resolve any problems.

2. If the board was found to be correctly inserted in step 1, issue the

busyout board command.

3. Issue the reset board command.

4. Issue the release busy board command.

5. Issue the test board long command. This should re-establish the

linkage between the internal ID and the port. If this is not the case,

check to ensure that there is a valid board inserted.

Table 9-21. TEST #7 Conference Circuit Test — Continued

Error

Code Test

Result Description/Recommendation

Continued on next page

DEFINITY Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Issue 2

January 1998

Maintenance Object Repair Procedures

Page 9-50ANL-16-L (16-Port Analog Line)

Table 9-22. TEST #35 Battery Feed Test