1. Manuals
  2. Brands
  3. Avaya Manuals
  4. Server
  5. DEFINITY Server CSI
  6. Maintenance manual

Avaya DEFINITY Server CSI Maintenance Manual

Hide thumbs
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
Table of Contents

Advertisement

Quick Links

Maintenance for
Avaya DEFINITY
®
Server CSI
Volumes 1 and 2
Release 1.2
555-233-119
Issue 5
October 2002

Advertisement

Table of Contents
loading

Related Manuals for Avaya DEFINITY Server CSI

Summary of Contents for Avaya DEFINITY Server CSI

  • Page 1 Maintenance for Avaya DEFINITY ® Server CSI Volumes 1 and 2 Release 1.2 555-233-119 Issue 5 October 2002...
  • Page 2 How to Get Help ability and security, even when the equipment performs as warranted. For additional support telephone numbers, go to the Avaya Web site: These compromises may become more acute if you fail to follow Avaya's recommendations for configuration, operation and use of the http://www.avaya.com/support/...

  • Page 3: Reset System

    • Reorient or relocate the receiving antenna. sures. Contact your Avaya representative for more laser product infor- • Increase the separation between the equipment and mation.
  • Page 4 FCC before the SDoC process If trouble is experienced with this equipment, for repair or warranty was available. A list of all Avaya registered products may be found at: information, please contact the Technical Service Center at 1-800-242- 2121 or contact your local Avaya representative.
  • Page 5 European Union Declarations of Conformity Avaya Inc. declares that the equipment specified in this document bearing the “CE” (Conformité Europeénne) mark conforms to the European Union Radio and Telecommunications Terminal Equipment Directive (1999/5/EC), including the Electromagnetic Compatibility Directive (89/336/EEC) and Low Voltage Directive (73/23/EEC). This...

  • Page 7: Table Of Contents

    Contents Volume One About this Book Purpose Intended Audience Organization Conventions Used In This Document Safety Precautions Security Issues Standards Compliance Electromagnetic Compatibility Standards Trademarks and Service Marks How to Order Documentation How to Comment on This Document Where to Call for Technical Support Maintenance for CSI systems How to use the Maintenance book CSI design...
  • Page 8 Contents Restoring Power System Backup Troubleshooting Features Install DS1 CPE Loopback Jack (T1 Only) LED Interpretation Multimedia Call Handling TN760D Tie Trunk Option Settings TN464E/F/GP Option Settings ATM Tips Unusual ATM trouble conditions Troubleshooting Multimedia Call Handling (MMCH) Maintenance Commands System Command Structure busyout access-endpoint busyout board...
  • Page 9 Contents change synchronization change system-parameters maintenance clear audits clear errors clear interface clear isdn-testcall clear link clear mst clear pkt clear port disable administered-connection disable filesystem board ppcss disable firmware download disable mst disable suspend-alm-orig disable synchronization-switch disable test-number display alarms display capacity display communication-interface hop-channels display communication-interface links...
  • Page 10 Contents download update-file enable administered-connection enable filesystem board enable mst enable suspend-alm-orig enable synchronization-switch enable test-number get boot-image get ethernet-options get vector list communication-interface processor-channel list configuration list configuration license list configuration software-version list directory list disabled-mos list external-device alarm list history list ip-route list isdn-testcall...
  • Page 11 Contents list trace mark port monitor bcms monitor health monitor security-violations monitor system monitor traffic monitor trunk netstat arp netstat ip-route ping recycle carrier refresh route-table release access-endpoint release board release cdr-link release data-module release journal-printer release link release mis release modem-pool release pms-link release port...
  • Page 12 Contents reset login-session n reset packet-interface reset switch-control reset system reset system 3 reset translation-id reset val restore announcements resume hardware-group save announcements save translation set boot-image set ethernet-options set options set signaling-group set synchronization set tdm set time set tone-clock set vector status access-endpoint status administered-connection...
  • Page 13 Contents status ip-board status ip-network-region status isdn-testcall status journal-link status link n status logins status packet-interface status pms-link status pri-endpoint status processor-channel status psa status signaling-group status sp-link status station status synchronization status sys-link status system status trunk status tsc-administered status tti status val-ip test access-endpoint...
  • Page 14 Contents test inads-link test interface test isdn-testcall test journal-printer test license test led test memory test network-control test pkt test packet-interface test pms-link test port test pri-endpoint test processor test signaling-group test sp-link test station test synchronization test sys-link test tdm test tone-clock test trunk test tsc-administered...
  • Page 15 Contents ADX16A-PT (AUDIX Analog Line/Control Link) ALARM-PT (ALARM PORT) ANL-24-L (24-Port Analog Line) ANL-BD (Analog Line Circuit Pack) ANL-LINE (8-Port Analog Line), ANL-NE-L (8-Port Neon Analog Line) AN-LN-PT (Analog Line Port) ANN-BD (Announcement Circuit Pack) ANN-PT (Announcement Port) ANNOUNCE (Announce) ATM-BCH (ATM B-Channel Trunk) ATM-DCH (ATM D-Channel Port) ATM-INTF (TN2305/6)
  • Page 16 Contents Volume Two DATA-BD (Data Channel Processor Circuit Pack) DATA-CHL (Data Channel) DATA-CON (Network Control Driver) DAT-LINE (Data Line) DETR-BD (International Version) DID-BD (Direct Inward Dial Trunk Circuit Pack) DID-DS1 (DS1 DID Trunk) DID-TRK (DID Trunk) DIG-BD (Digital Line Circuit Pack) 1013 DIG-IP-STN (Digital IP Station) 1014...
  • Page 17 Contents HYB-LINE (Hybrid Line) 1236 INADS (INADS Link) 1258 IO-PROCR (I/O Processor) 1262 IPMEDPRO (IP Media Processor Circuit Pack) 1265 ISDN-PLK (ISDN-PRI Signaling Link Port) 1281 ISDN-SGR (ISDN-PRI Signaling Group) 1287 ISDN-TRK (DS1 ISDN Trunk) 1303 LIC-ERR (License-Error Mode) 1331 LOG-SVN (Login Security Violation) 1339 JNL-PRNT (Journal Printer Link)
  • Page 18 Contents RDIG-STA (Remote Digital Station) 1554 REM-OFF (Remote Office) 1568 RING-GEN (Analog Ring Generator) 1570 S-SYN-BD (Speech Synthesis Circuit Pack) 1574 S-SYN-PT (Speech Synthesis Port) 1575 SEC-CDR (SEC-CDR Link Maintenance) 1587 SW-CTL (Switch Control) 1588 SYNC (Synchronization) 1596 SYS-LINK (System Links) 1603 SYS-PRNT (System Printer) 1608...
  • Page 19 Contents VC-BD 1884 VC-DSPPT 1888 VC-LEV (Voice Conditioner DSP Port Level) 1896 VC-SUMPT 1899 WAE-PORT (Wideband Access Endpoint Port) 1904 XXX-BD (Common Port Circuit Pack) 1911 Index 1925 555-233-119 Issue 5 October 2002...
  • Page 20 Contents Issue 5 October 2002 555-233-119...

  • Page 21: About This Book

    The user’s assigned maintenance technician. The technician is expected to have a knowledge of telecommunications fundamentals and of the Avaya Definity Server CSI system to the extent that the procedures in this book can be performed, in most cases, without assistance.

  • Page 22: Organization

    About this Book This book is not intended to solve all levels of troubles. It is limited to troubles that can be solved by using the Alarm Log, Error Log, trouble-clearing procedures, maintenance tests, and traditional troubleshooting methods. If the trouble still has not been resolved, it is the responsibility of the maintenance technician to escalate the problem to a higher level of technical support.

  • Page 23: Conventions Used In This Document

    The term “ASAI” is synonymous with the newer CallVisor ASAI. The word “system” generally refers to Avaya™ MultiVantage Software running on a Definity® Server CSI with Avaya™ CMC1 Media Gateway. Circuit pack codes (such as TN2402/TN798 or TN2182B) are shown with the minimum acceptable alphabetic suffix (like the “B”...

  • Page 24: Safety Precautions

    Security Issues A number of matters concerning maintenance are affected by security issues. For details, be sure to consult the Avaya Products Security Handbook. CAUTION: ® Login security is an attribute of the DEFINITY Enterprise Communications Server (ECS) Release 10 software.

  • Page 25: Standards Compliance

    Standards 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...

  • Page 26: Electromagnetic Compatibility Standards

    Radiated radio frequency field immunity requirements IEC 1000-4-3 Electrical fast transient/burst immunity requirements IEC 1000-4-4 European Union Standards Avaya declares that the Avaya Definity Server CSI equipment specified in this document bearing the “CE” mark conforms to the European Union Electromagnetic Compatibility Directives.

  • Page 27: Trademarks And Service Marks

    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 Trademarks and Service Marks The following are trademarks or registered trademarks of Avaya, Inc.: AUDIX® Cajun® CallVisor® Callmaster®...

  • Page 28: How To Order Documentation

    In addition to this book, other description, installation and test, maintenance, and administration books are available. This document and any other Avaya documentation can be ordered directly from the Avaya Publications Center toll free at 1-800-457-1235 (voice) and 1-800-457-1764 (fax). International customers should use +1.410.568.3680 (voice) and +1.410.891.0207 (fax).

  • Page 29: Where To Call For Technical Support

    Streamlined Implementation, for missing equipment 1-800-772-5409 USA Technical Service Center 1-800-248-1234 Canada 1-800-387-4268 Technical Service Center (INADS Database 1-800-248-1111 Administration) Avaya Definity Server CSI Helpline 1-800-225-7585 Avaya Toll Fraud Intervention 1-800-643-2353 Avaya Technical Service Center (maintenance/repair) 1-800-242-2121 Avaya Corporate Security 1-800-822-9009 1-925-224-3401...
  • Page 30 About this Book Issue 5 October 2002 555-233-119...

  • Page 31: Maintenance For Csi Systems

    Maintenance for CSI systems The maintenance subsystem is a part of the software that initializes and maintains the system. The software continuously monitors system health and keeps a record of errors detected in the system. The maintenance subsystem also provides a user interface for on-demand testing. This chapter provides a brief description of the maintenance strategy and background information on the system’s overall functions.
  • Page 32 Maintenance for CSI systems Table 1. Alarm levels, reporting conditions and action to take Reported Reported Alarm level Description INADS? console? What action to take? MAJOR Critical service Yes, after 4 Immediate attention degradation attempts to call INADS MINOR Some service Same as See what service is degradation but does not...
  • Page 33 How to use the Maintenance book 2. Enter y in the appropriate fields to restrict the following alarm reports (shown in Screen 1 in bold): Active Major Minor Warning CAUTION: If you enter n for major alarms and y for minor and warning alarms, you will not see the macro-level information that you may need to determine what is wrong with the system.
  • Page 34 Maintenance for CSI systems 7. Find the DID-TRK MO in the Maintenance Object chapter of the appropriate maintenance book. 8. In the first table, look up the command to run in the MAJOR row of the table. In our example, Step indicated that a DID trunk in slot 10, carrier C has a MAJOR alarm.
  • Page 35 How to use the Maintenance book TEST RESULTS Port Maintenance Name Alt. Name Test No. Result Error Code 01C1008 DID-TRK FAIL 61472 Screen 4. Test Results screen 12. Find the Port Diagnostic Test number (35 in our example) in the DID-TRK section of the Maintenance book.
  • Page 36 Maintenance for CSI systems Field descriptions for the Alarm Report query screen Enter error type, or blank Error type active-alarms, errors, or cleared-errors Error List h(our), d(ay), w(eek), m(onth), a(ll) Interval Specify time interval by date and time From/To Enter cabinet number (1 - 44) Cabinet Enter port network number (1 - 44) Port Network...

  • Page 37: Csi Design

    Figure 1 on page 39. Slots 5 and 6 are not contiguous like they are in other Avaya Definity Server cabinet types. Multi-Function circuit packs such as the TN566 and the MAPD boards (TN800, TN801, and TN802) must be installed in specific slots. For example: —...
  • Page 38 Maintenance for CSI systems There is no battery backup in the Avaya Definity Server CSI. If power is interrupted for more than 50 milliseconds, all calls are dropped and memory is lost. To maintain service without interruptions, install a dedicated uninterruptable power supply (UPS) between the AC source and the switch.
  • Page 39 CSI design scdmlft2 KLC 070397 Figure 1. Compact Modular Cabinet (CMC1) slot configuration The RISC-based TN2402/TN798 Processor circuit pack must be located slot 1. Figure 1 shows the Flash Memory Card slot for translations. TN2182 Tone-Clock must be installed in slot 2. This is the only Tone-Clock circuit pack allowed in the CMC1.

  • Page 40: Circuit Packs

    All circuit pack slots in the Compact Modular Cabinet (CMC1) are “universal slots.” Any slot can contain any type of circuit pack (port, control, or service), so there is no purple and white slot coding that is found on other Avaya Definity Server products.

  • Page 41: Alarm And Error Reporting

    Alarm and Error Reporting Alarm and Error Reporting During normal operations, software or firmware may detect error conditions relevant to specific MOs. The system attempts to either fix or circumvent these problems automatically. An alarm is raised if a hardware component incurs too many errors.

  • Page 42: Maintenance Testing

    Maintenance for CSI systems Maintenance Testing Most troubles are reduced to the circuit pack level and can be identified by LEDs on the circuit packs and software reports generated by the system. The background maintenance tests in the system are divided into three groups: Periodic tests are usually performed hourly by maintenance software.
  • Page 43 Maintenance Testing Layers The Open System Interconnect (OSI) model for data communications contains seven layers, each with a specific function. Communications to and through the system concern themselves only with layers 1 and 2 of the model. Layer 1, or the physical layer, covers the physical interface between devices and the rules by which bits are passed.
  • Page 44 Maintenance for CSI systems ORIGINATING SYSTEM DESTINATION DATA DATA MODULE MODULE DATA DATA MODULE MODULE RS232C RAW BITS RS232C ASCII ASCII USER DEFINED MODEM MODEM POOLING CABLE MODEM MODEM RS232C ANALOG ANALOG RS232C ASCII VOICE GRADE DATA ASCII USER DEFINED RS232C ADU PROT RAW BITS...

  • Page 45: Preventive Maintenance Procedures

    Preventive Maintenance Log The sample below shows the Avaya Definity Server CSI Preventive Maintenance Log. Whenever you complete any of the preventive maintenance procedures described in this section, be sure to fill in the requested information on the log screen before leaving the customer’s premises.
  • Page 46 Maintenance for CSI systems Fan and Filter Removal/Replacement 1. Remove the left door. 2. Remove the fan/filter access panel. See Figure 3 on page Filter scdmfltr RPY 072297 Figure 3. Fan/Filter Removal Fan Assembly Removal/Replacement 1. Pull (unplug) the fan assembly from the chassis. The power for the fan automatically disconnects when the assembly is unplugged.

  • Page 47: Recovery

    Recovery Recovery When the system is initially powered up, or when an existing system experiences a catastrophic fault that interrupts its basic functions, the system either initializes or reboots. There are several less severe resets available to the system that allow it to recover from disrupting errors.
  • Page 48 Maintenance for CSI systems Reset System 1 (System Warm Start) This recovery takes about 30 seconds. All stable phone calls remain up. In-progress calls are dropped. No new calls can be made during this time. In this restart, all software (Oryx/Pecos, drivers, maintenance, and so forth.) is reset and the following appears: RESET 1 (WARM) PERFORMED Reset System 2 (System Cold Start...
  • Page 49 Recovery WRITE BUFFER TEST PASSED BTO TEST PASSED TIMER TEST PASSED RESET 3 (COLD_1)PERFORMED Reset System 4 (System Reboot) In this reset Emergency Transfer is invoked. The boot image is already in the flash ROM memory. The system reboots immediately after the LMM performs a series of diagnostics on the processor and memory.
  • Page 50 Maintenance for CSI systems Reset System 5 (System Reboot and Run All 24-Hour Tests) In this reset Emergency Transfer is invoked. The LMM performs a series of diagnostics on the processor, on memory, and on memory card. Some diagnostics perform twice. This takes less than three minutes. The boot image is already in the flash ROM memory.

  • Page 51: Set Neon Voltage (Ring Ping)

    Set Neon Voltage (Ring Ping) Set Neon Voltage (Ring Ping) NOTE: If the ringing option is set to 50 Hz, neon voltage is not available. If 25 Hz is selected, the maximum voltage is 120 volts. If LED message lamps are used, or there are no neon message waiting lamps, or if the 50-Hz ring option is selected, use this step.

  • Page 52: Logging On/Off

    Maintenance for CSI systems Logging On/Off System Login Procedure 1. At the login prompt, type craft and press Enter 2. In the password prompt, type crftpw and press Enter. For security reasons, the password is not displayed as it is typed. The following information appears: Terminal Type (513, 715, 4410, 4425, VT220): [513] 3.
  • Page 53 Logging On/Off 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 the password is about to expire.
  • Page 54 Maintenance for CSI systems If your password has expired, you see the message: Login: telmgr Password: Your Password has expired, enter a new one. Reenter Current Password: New Password: Reenter New Password: Screen 5. Password Expiration Screen 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.
  • Page 55 Logging On/Off To remove Facility Test Calls Access Code: 1. Enter change feature-access-codes to display the Feature Access Code screen. 2. Leave the Facility Test Calls Access Code field blank. CAUTION: No alarms report through the INADS interface if Alarm Origination is disabled.
  • Page 56 Maintenance for CSI systems List Logins 1. Type list logins. The following information for all current logins with the same or lower service level as the requestor appears: Name Service level Status (active, inactive, disabled, svn-disabled, void) Password aging cycle length Remove a Login 1.
  • Page 57 Logging On/Off 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.
  • Page 58 Maintenance for CSI systems 11. Decide whether or not to leave the default of yes in the Facility Test Call Notification Acknowledgment Required field. If y is selected, the user is required to acknowledge that they wish to logoff while Facility Test Call is still administered.
  • Page 59 Logging On/Off 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 change login name to access the Login Administration screen. Enter your super-user password in the Password of Login Making Change field on the Login Administration screen.
  • Page 60 Maintenance for CSI systems category. When the Command Permissions Categories screen appears for a login, the subcategories fields appear with the fields set to give the login full permissions for that login type. The super-user administering login permissions can set any of these field to deny access to a command category for the specified login.
  • Page 61 Logging On/Off Page 1 of 3 COMMAND PERMISSION CATEGORIES Login Name: COMMON COMMANDS Display Admin. and Maint. Data? y System Measurements? _ System Mgmt Data Transfer Only? _ ADMINISTRATION COMMANDS Administer Stations? y Administer Features? y Administer Trunks? y Administer Permissions? y Additional Restrictions? n MAINTENANCE COMMANDS Maintain Stations? n...
  • Page 62 Maintenance for CSI systems Testing a Login 1. Enter your login name at the login prompt. After the user enters the correct login name and password and the login is administered correctly, the command line interface appears. 2. Turn on the administration terminal. 3.

  • Page 63: Procedure For Spe-Down Mode

    Procedure for SPE-Down Mode System Logoff Procedure The system logoff procedure should be done any time the terminal is not being used. This assures that system translations are not accidentally corrupted. The monitor system command, when canceled, automatically causes a terminal user to be logged off and, thus, prevents unauthorized use of the terminal.
  • Page 64 Maintenance for CSI systems Screen 11 shows all possible SPE-Down alarms. DISPLAY ALARMS: Physical Logical Alternate Alarm Date Date Name Name Board? Name Type Alarmed Resolved ------ PROC_BD ----- MAJOR ------ ------ ------ MEM_BD_0 ----- MAJOR ------ ------ ------ M_BUS ----- MAJOR ------...

  • Page 65: Reseating/Replacing Circuit Packs

    Reseating/Replacing Circuit Packs Reseating/Replacing Circuit Packs WARNING: It is NOT recommended that you reseat circuit packs unless the documentation specifically instructs you to do so. If it is required to reseat a circuit pack, follow the instructions below which explain how to unseat, reseat, and replace circuit packs.

  • Page 66: Removing Power

    Maintenance for CSI systems 3. Replace the circuit pack as per the following procedure. NOTE: If a new circuit pack does not correct the problem, install the original circuit pack. To install a new circuit pack or return the original one to service: 1.

  • Page 67: Restoring Power

    Restoring Power 4. The “SHUTDOWN Completed” message appears when the AUDIX is successfully shutdown. This takes about 2 minutes. 5. The AUDIX System can now be removed for service. WARNING: If a translation card alarm is present, or if a translation card problem is suspected, do not save translations to the translation card.
  • Page 68 Maintenance for CSI systems Power Up the AUDIX System If the AUDIX was removed from the cabinet: 1. Re-install the AUDIX and allow it to boot up automatically. 2. Check for SUCIX System errors. If the AUDIX remained in the cabinet, but power was removed from the cabinet: 1.

  • Page 69: System Backup

    System Backup System Backup System translations can be restored by using the data on the system or on the backup translation card. Save Translation To ensure that the translation card contains the most recent copy of the translation data, the system can automatically save the translation data onto the translation card every 24 hours.
  • Page 70 Maintenance for CSI systems Save announcements Enter save announcements to save the recorded announcements in the system on the translation card. NOTE: This command is not necessary for the TN750C Announcement circuit pack. NOTE: A 16 MByte or larger translation card formatted for announcements (and/or translations) is required to save and restore announcements.
  • Page 71 System Backup save translation SAVE TRANSLATION Processor Command Completion Status Error Code SPE-A Success Command successfully completed Screen 12. Save Translation screen 4. Verify that the command successfully completes. If not, an error message appears. Seethe “Translation Card Errors” section. 5.
  • Page 72 — The correct translation card for the desired operation has not been inserted. Load the appropriate translation card. 9. File size exceeded — There is no more file space. Call your Avaya representative. 10. Upgrade Memory Card inserted — The system upgrade translation card may have been inserted instead of the translations card.

  • Page 73: Troubleshooting Features

    Troubleshooting Features Troubleshooting Features In addition to the maintenance and test commands, the following system features may also be useful in troubleshooting certain system resources: ‘‘Automatic Circuit Assurance’’ ‘‘Busy Verification of Terminals and Trunks’’ ‘‘Trunk Group Busy/Warning Indicators to Attendant’’ ‘‘Trunk Identification by Attendant’’...
  • Page 74 Maintenance for CSI systems Busy Verification of Terminals and Trunks A multi-appearance voice terminal or attendant console equipped with a “verify” button is required. Busy Verification of Terminals and Trunks allows a user at a voice terminal or attendant console to make test calls to trunks, voice terminals, and hunt groups (DDC/UCD).
  • Page 75 Troubleshooting Features The following Facility Test Calls are described below: ‘‘Trunk Test Call’’ ‘‘Touch-tone (DTMF) Receiver Test Call’’ ‘‘Time Slot Test Call’’ ‘‘System Tone Test Call’’ Trunk Test Call The trunk test call accesses specific Tie or CO trunks. DID trunks cannot be accessed.

  • Page 76: Touch-Tone (Dtmf) Receiver Test Call

    Maintenance for CSI systems If the call does not go through (that is, no ringing), determine if the trunk circuit pack has been removed. CAUTION: To leave the Facility Test Call administered after you logoff poses a significant security risk that unauthorized individuals may connect to the telecommunications network through the use of test call features.
  • Page 77 Troubleshooting Features Time Slot Test Call The time slot test call connects the voice terminal user to a specific time slot located on the TDM Buses (A or B) or out-of-service time slots. Specific Time Slots To place the call: 1.
  • Page 78 Maintenance for CSI systems Table 5. TDM Bus Time Slot Numbers — Continued TDM Bus A TDM Bus B time slot time slot Tone Heard Alert Tone Busy Tone Ringback Tone Special Ringback Tone 2225 Hz Tone Music Tone on Hold 022-253 278-509 Confirmation (used for calls)
  • Page 79 2. Dial port network number (1), then dial followed by the two-digit tone identification number listed in Table NOTE: For a definition of Call Progress Tones see Administrator’s Guide for Avaya MultiVantage Software. Table 6. System Tone Identification Numbers Number Description Null tone Dial tone...
  • Page 80 Maintenance for CSI systems Table 6. System Tone Identification Numbers — Continued Number Description Chime 350 Hz 440 Hz 480 Hz 620 Hz 2025 Hz 2225 Hz Counter External call waiting Priority call waiting Busy verification Executive override/intrusion tone Incoming call identification Dial zero Attendant transfer Test calls...
  • Page 81 Troubleshooting Features Table 6. System Tone Identification Numbers — Continued Number Description Digital milliwatt 440 Hz + 480 Hz Music Transmission test sequence 100 Transmission test sequence 102 Laboratory test tone 1 Laboratory test tone 2 Disable echo supervision dial tone 7 seconds of answer tone 4 seconds of answer tone Restore music (or silence)
  • Page 82 Maintenance for CSI systems E & M Mode Test Procedure To perform the Analog Tie Trunk port test in the E & M mode: 1. At the administration terminal, enter list configuration trunks to determine which ports are assigned on the Tie Trunk circuit pack. 2.
  • Page 83 Troubleshooting Features display trunk-group 10 Page 1 of TRUNK GROUP Group Number: 10 Group Type: tie CDR Reports? y Group Name: tr 10 COR: 1 TAC: 110 Direction: two-way Outgoing Display? n Data Restriction? n MIS Measured? n Dial Access? y Busy Threshold: 60 Night Service: Queue Length: 0...
  • Page 84 Maintenance for CSI systems Table 7. Carrier Lead Appearances at 110 Cross-Connect Field 110 Connecting Block Terminals CO Trunk TN747B Tie Trunk TN760B Continued on next page 555-233-119 Issue 5 October 2002...
  • Page 85 Troubleshooting Features Table 7. Carrier Lead Appearances at 110 Cross-Connect Field — Continued 110 Connecting Block Terminals CO Trunk TN747B Tie Trunk TN760B Continued on next page 12. At the cross-connect field, use a D Impact Tool (AT-8762) to disconnect outside trunk facilities from the Tie Trunk ports and mark the disconnected wires for later reconnecting the Tie Trunk ports back to normal operation.
  • Page 86 Maintenance for CSI systems 13. 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: Port Port...
  • Page 87 Troubleshooting Features An example of the Trunk Group screen Page 2 is shown in Screen 16 on page Page 2 of 5 TRUNK GROUP GROUP MEMBER ASSIGNMENTS Port Name Mode Type Answer Delay 1: B1901 simplex type 5 2: B1902 simplex type 5 Screen 16.
  • Page 88 Maintenance for CSI systems Terminating Trunk Transmission Testing The Terminating Trunk Transmission (TTT) (noninteractive) 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. The three test types should have extension numbers assigned on the Maintenance-Related System Parameters screen.
  • Page 89 Troubleshooting Features Troubleshooting ISDN-PRI Problems The following flowchart, Figure 5 Figure 6 on page 90, 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 TN765 Processor Interface is layer 2, and the ISDN trunks are layer 3.
  • Page 90 Maintenance for CSI systems COMPARE INDICATED FROM FACILITY TO RECORD PAGE OF PREVIOUS PROBLEMS PERFORM AN IN-DEPTH ANALYSIS OF T1 FACILITY INCLUDING: TRANSMISSION FACILITY, EXTERNAL EQUIPMENT ARE BIT THERE (DACS, CSUs, ETC.,) TRANSIENT ERRORS OCCURRING AND ANY OTHER PROBLEMS MAKING MORE FREQUENTLY NOISE-PRODUCING ISDN-PRI...
  • Page 91 Troubleshooting Features The troubleshooting procedure described here diagnoses faults between the switch and the line-side PRI terminal adapter/ISDN-PRI endpoint equipment. Problems encountered on the network-side of a wideband connection or problems with end-to-end equipment compatibility are outside the scope of this manual. START Are there alarms or...
  • Page 92 Maintenance for CSI systems FROM PAGE 1 Does every TRANSIENT FAILURES ALWAYS FAIL call fail or are the failings transient? CHECK THE HEALTH OF THE Are there APPLICATION EQUIPMENT bit errors (FOR EXAMPLE, VIDEO CODEC) Perform an in-depth over the DS1 AND THE HEALTH OF THE analysis of DS1 interface between the...
  • Page 93 Troubleshooting Features Placing an Outgoing ISDN-PRI Test Call NOTE: 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. Synchronous Method One command is used in this method to start, stop and query an ISDN-PRI test call.
  • Page 94 Maintenance for CSI systems NOTE: Before placing an outgoing ISDN-PRI test call, verify that the FAC on the System Features screen has been administered, and the Far End Test Line No and TestCall Bearer Capability Class (BCC) fields are administered on the Trunk Group Administration screen.
  • Page 95 Troubleshooting Features Field descriptions Port address: PCSSpp (cabinet-carrier-slot-circuit) Port Name of maintenance object Maintenance Name The actual test that was run. Test Number Test result: Pass, Fail, Abort Test Result Numeric code explaining why the release failed or aborted. Refer to Error Code the detailed list of the codes by test number for each MO or see the ISDN Trunk Maintenance documentation for details.

  • Page 96: Install Ds1 Cpe Loopback Jack (T1 Only)

    Maintenance for CSI systems If the outgoing ISDN-PRI test call keeps aborting, please 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.
  • Page 97 Install DS1 CPE Loopback Jack (T1 Only) 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.
  • Page 98 Maintenance for CSI systems 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.
  • Page 99 Install DS1 CPE Loopback Jack (T1 Only) 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” appears on the terminal. This is the first of the 2 results.
  • Page 100 Maintenance for CSI systems Table 8. DS1 Span Troubleshooting — Continued Field Function Indication Bit Error Count Cumulative If there are no wiring problems, the counter count of remains at 0. detected A count that pegs at 65535 or continues to errors increment by several hundred to several thousand on each list meas command execution indicates...
  • Page 101 Install DS1 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.
  • Page 102 Maintenance for CSI systems 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.
  • Page 103 Install DS1 CPE Loopback Jack (T1 Only) Figure Notes: 1. Span Section 1 5. RJ-48 to Network Interface (Up to 1000 Feet) (305 m) 2. Span Section 2 6. Loopback Jack 3. Span Section 3 7. Network Interface Smart Jack 4.
  • Page 104 Maintenance for CSI systems Figure Notes: 1. Span Section 1 6. Loopback Jack 2. Span Section 2 7. “Dumb” Block (Extended Demarcation) 3. Span Section 3 8. Network Interface Smart Jack 4. 120A2 (or later) Integrated 9. Interface Termination or Fiber MUX Channel Service Unit (ICSU) 10.
  • Page 105 Install DS1 CPE Loopback Jack (T1 Only) Figure Notes: 1. Span Section 1 6. “Dumb” Block (Extended Demarcation) 2. Span Section 2 7. Loopback Jack 3. Span Section 3 8. Network Interface Smart Jack 4. 120A2 (or later) Integrated 9. Interface Termination or Fiber MUX Channel Service Unit (ICSU) 10.
  • Page 106 Maintenance for CSI systems 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 12 Figure 13 on page 107. 1.
  • Page 107 Install DS1 CPE Loopback Jack (T1 Only) Figure Notes: 1. Span Section 1 5. Loopback Jack 2. Span Section 2 6. “Dumb” Block (Demarcation Point) 3. 120A2 (or later) Integrated 7. Repeater Channel Service Unit 8. Fiber MUX (ICSU) 9. Central Office 4.
  • Page 108 Maintenance for CSI systems 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.
  • Page 109 Install DS1 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.

  • Page 110: Led Interpretation

    Maintenance for CSI systems LED Interpretation The lighting and unlighting of LEDs indicates to the system user the status of various maintenance components in the system. LEDS are located on the attendant console, on all circuit packs in the switch cabinets and, optionally, on customer-designated voice terminals.
  • Page 111 LED Interpretation 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.
  • Page 112 Maintenance for CSI systems Alarm (Red Test (Green) Busy (Amber) Major alarms (Red) Minor alarms (Red) Emergency transfer control switch Memory card slot ckdmt798 RPY 072297 Figure 14. LED Indicators on the TN2402/TN798 Processor Circuit Pack NOTE: If the LED just above the Memory Card Slot is alternating red and amber, this indicates both card in use and emergency transfer.
  • Page 113 LED Interpretation Control and Port Circuit Pack Status LEDs Each circuit pack has three LEDs on the front panel visible at the front of the carrier. On all circuit packs, except the 650A Power Unit, the LEDs indicate: — 1. Red (alarm) If the circuit pack is communicating with the system, the system has detected a fault in this circuit pack.
  • Page 114 Maintenance for CSI systems — 2. Green (test) the system is running tests on this circuit pack. — 3. Yellow (busy) indicates that the circuit pack is in use. NOTE: A port circuit pack also lights its red LED when it performs initialization tests (for example, when the circuit pack is initially inserted into the system).

  • Page 115: Multimedia Call Handling

    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 Avaya Definity Server CSI must have the expansion service module installed.
  • Page 116 Figure 15. Typical ESM connections CAUTION: The TN2207 circuit pack is the only pack allowing connection of an ESM to the Avaya Definity Server CSI system. Troubleshooting MMCH ‘‘64 Kbps Calls Terminate but Far End Receives 56 Kbps Indication’’ ‘‘Calls Terminate with No Audio’’...
  • Page 117 64 Kbps Calls Terminate but Far End Receives 56 Kbps Indication Description Some 2x64 Kbps conferences on the Avaya Definity Server CSI MMCH do not establish because of framing, audio, or video problems. For calls that are routed in the network through an Avaya/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.
  • Page 118 3. If the problem still exists, suspect a hardware problem. If practical, wait for the Avaya Definity Server CSI 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.
  • Page 119 If there are different clock sources between endpoints and the Avaya Definity Server CSI 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.
  • Page 120 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 Avaya Definity Server CSI systems that have EPNs, synchronization should be provided to sub nodes from the same port network through which the PBX receives its synchronization.
  • Page 121 Multimedia Call Handling No Switching, Full Motion Video If a room is excessively noisy, the Avaya Definity Server CSI MMCH may receive sufficient audio signal to conclude that there is a speaker present. Use the Status Conference x screen 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.
  • Page 122 Because of a lack of a clear explanation in standards, sometimes endpoints do not work well with each other and the Avaya Definity Server CSI 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.
  • Page 123 Endpoint or I-MUX in Loopback Mode Some endpoints have a loopback enable feature. This makes Avaya Definity Server CSI MMCH data loopback at the MMCH when a connection is in progress. The loopback can be enabled prior to or during a connection.

  • Page 124: Tn760D Tie Trunk Option Settings

    Maintenance for CSI systems TN760D Tie Trunk Option Settings The TN760D Tie Trunk circuit pack interfaces between 4 tie trunks and the TDM bus. Two tip and ring pairs screen a 4-wire analog transmission line. An E and M pair are DC signaling leads used for call setup. The E-lead receives signals from the tie trunk and the M-lead transmits signals to the tie trunk.
  • Page 125 Table 13. TN760D Option Switch Settings and Administration E&M/SMPLX Prot/Unprot Administered Installation Situation Preferred Signaling Format Switch Switch Port Circumstance System Far-End Co-Located Avaya E&M Type 1 E&M Type 1 E&M Unprotected Type 1 Definity Server CSI Compatible Standard Compatible Inter-Building Avaya...

  • Page 126: Tn464E/F/Gp Option Settings

    Maintenance for CSI systems TN464E/F/GP Option Settings The TN464E/F/GP DS1/E1 Interface - T1/E1 circuit pack interfaces between a 24- or 32-channel Central Office/ISDN or tie trunk and the TDM bus. Set the switches on the circuit pack to select bit rate and impedance match. See Table 14 Figure Table 14.

  • Page 127: Atm Tips

    ATM Tips ATM Tips This section provides tips for Avaya Definity ATM PNC when interfacing with the ATM switch. Throughout this section, see Figure 18 on page 127. Use TN2238 for R6.3 systems, and TN230X for Release 7 and later.
  • Page 128 Maintenance for CSI systems Table 15. — Continued TN230X LED reference LED color Interpretation Green Yellow 100ms on / Loss of signal on the OC-3 fiber. Either the 100ms off TN230X-receive (top) or TN230X-transmit (bottom) fibers are not working. Fast blink Running DSP diagnostics or downloading code to DSPs (typical during boot process).
  • Page 129 Green Steady on ATM cells are being received frequently enough that the LED is lit constantly. This is a typical pattern for Avaya Definity Server CSI if Constant Bit Rate (CBR) talk paths are present. Green Loss of carrier on the fiber. The A500 detects only if the A500-receive (right-hand) fiber is not working.
  • Page 130 You an also use list configuration UUC (non-control cabinets) to confirm the PPN and EPN board locations and correct insertion. 2. Enter status pnc at the Avaya Definity Server CSI SAT. This display tells you which TN230X board is active in a duplicated system and how many alarms (if any) of each severity level have been logged for the board.
  • Page 131 3. Enter either list configuration UUC (for the carrier in which the ATM-EI packs reside) or display circuit-packs cabinet (non-control cabinet) at the Avaya Definity Server CSI SAT. This command tells you in more detail what boards are in which slots in each cabinet and carrier. Verify that the TN230Xs are physically located in the slots indicated on the screen.
  • Page 132 DIGITAL LINE ’#’ indicates circuit pack conflict. Screen 21. Screen output for display circuit-packs 2 4. Enter display atm pnc portnetwork on the Avaya Definity Server CSI SAT. This screen shows the ATM addresses that have been administered for each TN230X. Verify that each ATM address (the concatenation of the five hexadecimal fields) is correct and match those administered in the A500.
  • Page 133 ATM Tips display atm pnc 2 ATM PNC Connection Number: 2 Location: 02A01 Name: Address Format: ICD ATM AFI: 47 ICD: 0005 HO-DSP: 80FFE1000000F2072A01 ESI: 000000000000 SEL: 00 Screen 23. Screen output for display atm pnc 2 Administered with End System Identifiers If the port networks are addressed using End System Identifiers, the screen looks like Screen 24...
  • Page 134 UNI3.1 Screen 26. Screen output for the show signaling summary command If an A500 port attached to an Avaya Definity Server CSI port network is not listed on this screen, use the admin link command to see if the port was administered as having no UNI signaling.
  • Page 135 Screen 28. Screen output A500: show signaling esi command Check that the Addresses registered (use admin signaling esi add) match those administered in the Avaya MultiVantage Software running on the Definity Server CSI. — If an address or End System Identifier is missing or incorrect on the A500 port associated with the PPN, the EAL and PACL links will come up, but one-way talk paths may result.
  • Page 136 TenBaseT Screen 29. A500 screen output for show sys interfaces command For each administered port used by a Avaya Definity Server CSI port network, the Admin Status should be up (using the admin up command). The state of Oper Status is not pertinent to administration of the A500 and is discussed in a later section.
  • Page 137 Do the TN230X LEDs indicate that board insertion has not yet occurred? Do the TN230X LEDs indicate a maintenance alarm? 3. Enter list configuration carrier cabinetcarrier on the Avaya Definity Server CSI SAT. See Screen 30 on page 137 (1b) and Screen 31 on page (2a).
  • Page 138 ‘‘Reseating/Replacing Circuit Packs’’ on page 4. If the TN230X is inserted and shows a vintage number, enter test board cabinetcarrierslot for this board on the Avaya Definity Server CSI SAT, as shown in Screen 32...

  • Page 139: Physical Layer

    727. Possible Causes 1. The TN230X board is in a slot different from the one administered on the Avaya MultiVantage Software. 2. The TN230X did not complete board insertion. Physical Layer Is there an optical signal between the TN230X and the A500? 1.

  • Page 140: Quick Reference

    Maintenance for CSI systems SAP State If it is PHY_DOWN or DOWN, then there is probably a loss of signal on the port in question. This command detects a continuity problem only with the Receive (right-hand) fiber. It does not detect the state of the Transmit (left-hand) fiber.
  • Page 141 ATM Tips — Oper Status should be up. If it is down, there is likely a loss of signal on the port in question (State of present), or the A500 does not recognize the port board (State of invalid). This command detects a continuity problem only with the Receive (right-hand) fiber;...
  • Page 142 Maintenance for CSI systems Sonet per Port Statistics --------------------------------- Receive Cell Count: 80654 Transmit Cell Count: 79555 Section Level Bit Err: Line Bit Err: Line FEB Err: Path Bit Err: Path FEB Err: Correctable HCS Err: Uncorrectable HCS Err: Loss of Frame Err: Loss of Signal Err: Out of Frame Err: Path Signal Label:...
  • Page 143 ATM Tips Q.SAAL (Data Link) Layer Are ATM signaling messages reaching A500 Call Control? 1. Enter show signaling stats port qsaal on the A500 console. Screen 37 shows the screen output. A500: show signaling stats a1.2 qsaal ------------------------Q.SAAL Statistics------------------------ Port A1.2: ---------- Type: UNI3.1...
  • Page 144 Maintenance for CSI systems Q.93B (Network) Layer Are connection requests being received by A500 Call Control? 1. Enter show signaling stats port q93b (or the port of interest) on the A500 console. Screen 38 shows the screen output. A500:show signaling stats a1.2 q93b -------------------------Q.93B Statistics------------------------ Port A1.2: ----------...
  • Page 145 A500:show signaling cause 31 Cause 31: Normal, unspecified Screen 39. A500:show signaling cause 31 3. At the Avaya Definity Server CSI SAT, type display errors and press Enter The Error Report screen appears (Screen 40).
  • Page 146 ATM network. Service or option unavailable, Avaya Definity Server CSI call volume is too high for unspecified the available resources in the ATM network. 555-233-119 Issue 5 October 2002...
  • Page 147 Avaya MultiVantage Software Call Processing. Other UBR virtual circuits may exist between A500 ports that are not associated with Avaya Definity Server CSI port networks and may be signaling channels for other applications (for example, data network traffic). 555-233-119...
  • Page 148 Do you get a dial tone on a set on the port network in question? Can you ring a set on the EPN dialing from the PPN and vice versa? 1. Enter list sys-link on the Avaya Definity Server CSI SAT. Screen 43 shows the output.
  • Page 149 VBRnrt virtual circuits are also be used for ISDN channels between Avaya Definity Server CSI port networks. Other VBRnrt virtual circuits may exist between A500 ports that are not associated with Avaya Definity Server CSI port networks. A common use of VBRnrt circuits is multimedia and video-conferencing systems. CaPro Layer...
  • Page 150 UBR. — There may be other CBR virtual circuits between A500 ports that are not associated with Avaya Definity Server CSI port networks. A common CBR application is Circuit Emulation, in which T-1, T-3, etc. circuits are carried over ATM.

  • Page 151: Unusual Atm Trouble Conditions

    Unusual ATM trouble conditions Unusual ATM trouble conditions There are a few failure modes in the Avaya Definity Server CSI/A500 combination that are particularly difficult to diagnose. One example might be that you can’t make a completely successful call, even though most indications from the Avaya Definity Server CSI and the A500 look pretty good.
  • Page 152 Maintenance for CSI systems Swapped Routes, End System Identifiers, or Fiber between a PPN and an EPN Symptoms An incorrectly-connected EPN TN230X does not complete board insertion. Dial tone is present on end stations on the PPN and on correctly-connected EPNs, but no dial tone is present on the affected EPN end stations.
  • Page 153 To recover, the PPN re-establishes links to what it thinks is the active TN230X and the cycle repeats indefinitely. Diagnostics 1. The status pnc command on the Avaya Definity Server CSI SAT shows both the A-side and B-side State of Health field as partially functional.

  • Page 154: Troubleshooting Multimedia Call Handling (Mmch)

    Some 2x64 Kbps conferences on the Avaya MultiVantage Software MMCH do not establish because of framing, audio, or video problems. For calls that are routed in the network through an Avaya/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.
  • Page 155 Generally, loss of video can be divided into 2 types. The first occurs when the Avaya MultiVantage Software 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.
  • Page 156 Synchronization Generally, the most common problem is a mismatch in synchronization sources between the endpoint and the Avaya MultiVantage Software 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.
  • Page 157 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 Avaya Definity Server CSI systems that have EPNs, synchronization should be provided to sub nodes from the same port network through which the PBX receives its synchronization.
  • Page 158 Maintenance for CSI systems No Switching, Full Motion Video If a room is excessively noisy, the Avaya MultiVantage Software MMCH may receive sufficient audio signal to conclude that there is a speaker present. Use the Status Conference x screen to determine if the MMCH thinks an endpoint is talking.
  • Page 159 Troubleshooting Multimedia Call Handling (MMCH) 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.
  • Page 160 Rate Adaptation Because of a lack of a clear explanation in standards, sometimes endpoints do not work well with each other and the Avaya MultiVantage Software 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.

  • Page 161: Maintenance Commands

    Maintenance Commands This chapter provides additional trouble-clearing information for resolving both system-alarmed and user-reported troubles. This chapter supplements the information found in Chapter 3, ‘‘Maintenance Objects’’. The maintenance commands are used to control, test, and obtain information associated with maintenance objects (MOs). The commands require the use of the administration terminal or remote Initialization and Administration System (INADS) interface and a valid login and password.

  • Page 162: Busyout Access-Endpoint

    NOTE: The craft login may not be allowed to perform some of the steps needed to initialize the system. If access is denied to some of these procedures, contact your Avaya representative for assistance. Getting Help Use the key for a list of options and the...

  • Page 163: Busyout Board

    busyout board Output The following example shows the output for busyout access-endpoint 22502 and assumes that access endpoint ports for extension 22502 are in cabinet 1, carrier C, slot 11, circuit 1 to 6. The responses appear on a test-by-test basis with one line of data for each test result.
  • Page 164 Maintenance Commands Action/Object Qualifier Qualifier Description Logins Defaults Feature Interactions busyout board location Board address (PCSSpp) init none None inads Examples: craft busyout board 01c11 busyout board 02c15 Output The following shows an example output from busyout board 1c07. In our example, the board is an analog board with three administered ports.

  • Page 165: Busyout Cdr-Link

    busyout cdr-link busyout cdr-link Use busyout cdr-link to busyout a maintenance object associated with the specified call detail recording (cdr) link. Action/Object Qualifier Qualifier Description Logins Default Feature Interactions busyout link-id Link identifier (primary or init Primary None cdr-link secondary) inads craft Examples:...

  • Page 166: Busyout Data-Module

    Maintenance Commands busyout data-module Use busyout data-module to put the data module in a maintenance busy state, even uninstalled data modules. No periodic or scheduled tests is performed on the busied out data module or data channel until it is released and no call processing can be executed on the data modules or over the data channels.

  • Page 167: Busyout Journal-Printer

    busyout journal-printer busyout journal-printer Use busyout journal-printer to put the maintenance object associated with a pms-log or wakeup-log link in a maintenance busy state. No periodic or scheduled tests are performed on the busied out maintenance object until it is released. Also, no activity occurs over the links (that is, no data transferred to the printer) and the link is dropped.

  • Page 168: Busyout Link

    Maintenance Commands Output The following shows the output for busyout journal-printer wakeup-log. busyout journal-printer wakeup-log SPE A COMMAND RESULTS Port Maintenance Name Alt. Name Result Error Code JRNL-LINK PASS Field descriptions Physical object port address: 0 = wakeup log, 1 = pms log Port The name of the maintenance object Maintenance Name...

  • Page 169: Busyout Mis

    busyout mis busyout link 1 SPE A COMMAND RESULTS Port Maintenance Name Alt. Name Result Error Code 01C0301 PI-LINK PASS Field descriptions Port address/link-id Port The name of the busied out maintenance object Maintenance Name Not applicable Alt. Name Test result: Pass, Abort, Fail Result Numeric code explaining why the release failed or aborted.

  • Page 170: Busyout Pms-Link

    Maintenance Commands busyout mis SPE A COMMAND RESULTS Port Maintenance Name Alt. Name Result Error Code PASS Field descriptions Not applicable Port Name of busied out maintenance object: MIS Maintenance Name Not applicable Alt. Name Test result: Pass, Abort, Fail Result Numeric code explaining why the release failed or aborted.
  • Page 171 busyout pms-link Feature Interactions Maintenance of a particular component on a link sometimes interferes with the maintenance of the link itself. For example, maintenance can put a link component in a busy state causing link set-up to fail. Frequent attempts at re-setup of a link may delay the recovery of a faulty component, due to the maintenance test of a component only taking place when the component is idle.

  • Page 172: Busyout Port

    Maintenance Commands busyout port Use busyout port to place the specified port on a circuit pack in a maintenance busy state. No periodic or scheduled tests are performed on the busied out port until it is released. When the object is maintenance busy, it is deactivated (no call processing activity may include the busied object).

  • Page 173: Busyout Pri-Endpoint

    busyout pri-endpoint busyout pri-endpoint Use busyout pri-endpoint to place all PRI endpoint ports (B-channels) associated with the specified PRI endpoint in a maintenance busy state. No periodic or scheduled tests are performed on the busied out PRI endpoint ports until they are released. When the PRI endpoint port is maintenance busy it is deactivated, and no call processing activity may include the busied object.

  • Page 174: Busyout Sp-Link

    Maintenance Commands busyout sp-link Use busyout sp-link to put the system printer link into a maintenance busy state. This prevents access to the system printer. The system printer link is a link from the system to an external printer. The system printer extension is administered and a call is set up to the system printer.

  • Page 175: Busyout Tdm

    busyout tdm busyout station 1002 SPE A COMMAND RESULTS Port Maintenance Name Alt. Name Result Error Code 01C1102 DIG-LINE PASS Field descriptions Port address (cabinet-carrier-slot-circuit) Port Type of busied out maintenance object Maintenance Name Alternate means to identify maintenance object: extension number Alt.

  • Page 176: Busyout Tone-Clock

    Maintenance Commands busyout tdm port-network 1 bus a SPE A COMMAND RESULTS Port Maintenance Name Alt. Name Result Error Code PN 01A TDM-BUS PASS Field descriptions Port address and associated TDM number and bus (PNA or PNB) Port Not applicable Alt.

  • Page 177: Busyout Trunk

    busyout trunk busyout tone-clock 1a SPE A COMMAND RESULTS Port Maintenance Name Alt. Name Result Error Code TONE-PT PASS TDM-CLK PASS TONE-BD PASS Field descriptions Tone/clock board address (cabinet-carrier) Port Circuit pack name: TONE-PT, TDM-CLK, TONE-BD Maintenance Name Not applicable Alt.
  • Page 178 Maintenance Commands Output The following example is a display of busyout trunk. busyout trunk 78/1 SPE A COMMAND RESULTS Port Maintenance Name Alt. Name Result Error Code 01C1505 CO-TRK 78/01 PASS Field descriptions Port address (cabinet-carrier-slot-circuit) Port Type of busied out maintenance object. Maintenance Name Alternate way to identify maintenance objects.

  • Page 179: Cancel Hardware-Group

    cancel hardware-group cancel hardware-group Use cancel hardware-group to temporarily or permanently abort the execution of test hardware-group. To resume testing, use resume hardware-group or test hardware-group. Action/Object Qualifier Qualifier Description Logins Defaults Feature Interactions cancel Examples: init none See below hardware-group cancel hardware-group inads...
  • Page 180 Maintenance Commands change circuit-packs 1 Page 1 of CIRCUIT PACKS Cabinet: 1 Carrier: A Carrier Type: processor Slot Code Name Slot Code Name 01: TN2402/TN798 PROCESSOR 02: TN2182 TONE/CLOCK 06: ADX8D RESERVED-AUDIX-8D 07: ADX8D RESERVED-AUDIX-8D 08: TN566 MULTI-FUNCTION 09: ADX8D RESERVED-AUDIX-8D ’#’...

  • Page 181: Change Firmware Download

    change firmware download Field descriptions Administered cabinet number Cabinet Type of cabinet (single-carrier) Cabinet Layout In-use cabinet carrier Carrier Carrier function (port, processor, or expansion control) Carrier Type Slot numbers (0 - 21). Slot Circuit pack code (TN number) to identify the circuit pack type Code Lists the suffix, if applicable Alphanumeric circuit pack name...

  • Page 182: Change Ip-Network-Region

    9 is administered with connectivity with ip-network-region 11 first and then ip-network-region 11 appears, the fields are automatically populated to show connectivity with ip-network-region 9. See Administrator’s Guide for Avaya MultiVantage Software for field definitions for this screen. 555-233-119...

  • Page 183: Field Descriptions

    change ip-network-region Output change ip-network-region 1 Page 1 of IP Network Region Region: 1 Name: Audio Parameters Direct IP-IP Audio Connections? n Codec Set: 1 IP Audio Hairpinning? y Location: 3 UDP Port Range RTCP Enabled? y Min: 2048 RTCP Monitor Server Parameters Max: 65535 Use Default Server Parameters? n Server IP Address: ___.___.___.__...

  • Page 184: Change Synchronization

    Maintenance Commands change synchronization Use change synchronization to specify the hierarchy of sources used for timing synchronization. DS1 inputs to the external stratum 3 clock affect stratum 3 synchronization hierarchy. Primary and secondary fields reflect Stratum 4 synchronization. If all fields are blank, the tone clock board within each PN provides timing for that PN.

  • Page 185: Change System-Parameters Maintenance

    change system-parameters maintenance Field descriptions Enter the current synchronization stratum (3, 4) Stratum Appears when 4 is entered in the Stratum field. Primary Indicates the primary system synchronization source. Leave blank for no synchronization. Appears when 4 is entered in the Stratum field. Secondary Indicates the secondary system synchronization source.
  • Page 186 Maintenance Commands 8. Press and verify that Command successfully completed Enter appears on the screen. NOTE: Return all fields to their original settings after you complete your task. Action/Object Qualifier Qualifier Description Logins Defaults Feature Interactions change Examples: init none none system-parameters change...
  • Page 187 change system-parameters maintenance The system calls this number to report alarms. This number must be First OSS Telephone obtained from the National Customer Support Center (NCSC) or the Number TSC, and can be INADS or Trouble Tracker, for example. # and * are not allowed. Enter y to enable Abbreviated Alarm Reports for the First OSS.
  • Page 188 Enter n if a Packet Control circuit pack is not installed, unless system translations do not have all the required hardware. Avaya services has sole access to this field. Customer Access to...
  • Page 189 change system-parameters maintenance This display-only field lists the standard test series run by maintenance Daily Maintenance software during daily maintenance. Indicates the days that translation data in memory automatically saves Save Translation to the Mass Storage System disk and/or tape devices during scheduled maintenance.
  • Page 190 Maintenance Commands Output (Page Two) The following example shows Page 2 of change system-parameters maintenance. change system-parameters maintenance Page 2 of 3 MAINTENANCE-RELATED SYSTEM PARAMETERS MINIMUM MAINTENANCE THRESHOLDS ( Before Notification ) TTRs: 4 CPTRs: 2 Call Classifier Ports: _ MMIs: 0 VCs: 0 TERMINATING TRUNK TRANSMISSION TEST (Extension)
  • Page 191 change system-parameters maintenance When the number of call classifier ports (CLSFY-PTs) in service Call Classifier Ports 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 or TN2182 circuit pack. To alarm the first occurrence of a CLSFY-PT being taken out of service, set this field to the total number of CLSFY-PTs.
  • Page 192 Maintenance Commands Test Type 102 tests far end to near end loss by sending: Test Type 102 9 seconds of 1004 Hz tone at 0 dB 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 Test Type 105 C-notch noise by sending:...
  • Page 193 change system-parameters maintenance SPE Optional Boards These fields indicate if a Disk circuit pack is present, and identify Packet Intfl administered Packet Interface slots. If a Packet Interface circuit pack is present, the corresponding Packet Interface field is set to y when the system boots.
  • Page 194 Maintenance Commands Output (Page Three) The following example shows Page 3 of change system-parameters maintenance. change system-parameters maintenance Page 3 of 3 MAINTENANCE-RELATED SYSTEM PARAMETERS Modem Connection: external Data Bits: 8 Parity: none Modem Name: _______ RTS/CTS Enabled: \Q3 Auto Answer Ring Count (rings): S0=10 Asynchronous Data Mode: &M0&Q0 Dial Type: T DTE Auto-Data Speed: ______...
  • Page 195 change system-parameters maintenance Enter up to 6 characters to adjust the speed of the data source DTE Auto-Data (DTE) UART to the outgoing (modem-to-modem) data rate, up to Speed 9600 baud. This field sets the link speed between the switch and the modem, not the speed of the modem.

  • Page 196: Clear Audits

    Maintenance Commands Display-only field. Most off-the-shelf external modems provide a No Answer timer that abandons any outbound data call after a predetermined Time-Out interval. Some modems provide for this timer to be disabled, thus allowing an outbound call to ring indefinitely. AT&T Paradyne does not provide this capability with their modem line, because it is generally undesirable to have an outbound call attempt ring indefinitely.

  • Page 197: Clear Errors

    clear errors clear errors Use clear errors to move errors and resolved alarms from cleared-error lists, making room for new incoming error messages. This command does not clear active alarms from the alarm log. Use clear errors with care to prevent overwriting cleared entries.

  • Page 198: Clear Link

    Maintenance Commands clear link Use clear link to clear the hardware error counters associated with ports on the Processor Interface circuit pack (displayed with status link) or a numbered PPP C-LAN link. Use clear clan-port to accomplish the same thing. The statistical counters cannot be cleared for an Ethernet C-LAN link.

  • Page 199: Disable Administered-Connection

    disable administered-connection disable administered-connection Use disable administered connection to stop scheduled and periodic testing, and to stop processing of in-line errors for all or selected administered connections. Feature Action/Object Qualifier Qualifier Description Logins Defaults Interactions disable Number of the administered connection init none none...

  • Page 200: Disable Suspend-Alm-Orig

    Maintenance Commands disable suspend-alm-orig Use disable suspend-alm-orig to stop entries to the active Suspend Alarm Origination table. This command disables all board entries that match a specific physical board location. NOTE: This command does not disable port entries. Feature Action/Object Qualifier Qualifier Description Logins...

  • Page 201: Disable Test-Number

    disable test-number disable test-number Use disable test-number to prohibit selected maintenance tests from running. To run a disabled test number, use enable test-number. Action/ Feature Object Qualifier Qualifier Description Logins Defaults Interactions disable number Maintenance test number init none none test-number inads print...
  • Page 202 Maintenance Commands The save translation command is executed Translations are saved as part of scheduled maintenance A reboot takes place The PPN is about to lose all power after having been on battery backup The attempt to save the alarm and error logs may be unsuccessful if the MSS is not available.
  • Page 203 display alarms Feature Interactions If the user disables the alarm origination with change system-parameters maintenance, the Ack field on the Alarm Report is blank regardless of the true acknowledged state of the alarm. Options screen When you enter display alarms, an options screen appears. Select the options you want to view on the report.
  • Page 204 Maintenance Commands Board address (PCSS); example: 01A20 Board Number Port address (PCSSpp); example: 01A2031 Port Object code for the equipment category. Category Extension number (per dial-plan) Extension Enter a group number or a group and member number: Trunk Enter the group number (01-99) to display all members in the group.
  • Page 205 display alarms If y, the fault was found on the associated circuit pack On Brd If n, the fault is not connected to the circuit pack. Identifies the location of maintenance object, as follows: Alt Name Station=extension number Trunk=Group number (78/__) or group and member numbers (78/01) Private CO Line=private CO line (P) and group number.

  • Page 206: Display Capacity

    Maintenance Commands display capacity Use display capacity to show how the system is administered and provide a snapshot status of the switch resources. Action/ Feature Object Qualifier Qualifier Description Logins Defaults Interactions display print Report sent to printer init none none capacity inads...
  • Page 207 Field descriptions (page 1) For more information, see Administrator’s Guide for Avaya MultiVantage Software. AAR/ARS The number of route patterns. AAR/ARS Patterns Number of 12-character inserted-digit strings available for Inserted Digit AAR/ARS preferences. Strings Abbreviated Dialing (AD) The number of abbreviated dialing entries for both group AD Entries Per and personal lists.
  • Page 208 Maintenance Commands Field descriptions (page 2) For more information, see Administrator’s Guide for Avaya MultiVantage Software. Attendant Service The number of administered attendants. Attendant Positions A real-time snapshot of the number of calls waiting for all Queue Length attendants. The number of authorization codes used for security Authorization Codes purposes.
  • Page 209 display capacity Call Coverage The number of Coverage Answer Groups. Coverage Answer Groups — Coverage Paths The number of coverage paths which is a Coverage Paths path taken when a call goes to coverage. The number of call pickup groups have been administered. Call Pickup Groups The maximum number of active calls at a given time.
  • Page 210 Maintenance Commands Field descriptions (page 4) For more information, see Administrator’s Guide for Avaya MultiVantage Software. Data Parameters The number of connections between two access or data Administered endpoints. Connections Alphanumeric Dialing Entries Dial Plan This includes stations, data endpoints, hunt groups,...
  • Page 211 display capacity (Page 5) SYSTEM CAPACITY System Used Available Limit - - - - - - - - - - - - - HUNT GROUPS, SPLITS, OR SKILLS Groups/Splits/Skills: Administered Logical Agents: Administered Logical Agent-Skill Pairs: Logged-In ACD Agents: 5200 5200 Logged-In Advocate Agents: Logged-In IP-Softphone Agents:...
  • Page 212 Maintenance Commands The number of intercom groups set up within your organization. Intercom Groups Per System The number of modem pool groups. Modem Pool Groups Per System The number of PCOL trunk groups. Personal CO Line (PCOL) Trunk Groups (Page 6) SYSTEM CAPACITY System Used...
  • Page 213 display capacity Trunks The number of allowed DS1 circuit packs. DS1 Circuit Packs The number of Incoming Call Handling Table (ICHT) ICHT For ISDN Trunks entries administered for trunk groups. The number of call-by-call trunk groups. ISDN CBC Service Selection Trunks The number of trunk groups administered.
  • Page 214 Maintenance Commands The number of voice terminals not having an administered Stations Without port, such as AWOH. Port The number of ports used as conversion resources, agent Other Stations login ID, MASI, and analog announcements. The number of ports assigned by TTI features. TTI Ports The number of stations available to move using ACTR.
  • Page 215 display capacity Field descriptions (page 8) Total Subscribed Ports The number of subscribed radio controller circuit Radio Controllers packs. The total number of ports in the system. Station and Trunk Ports The number of subscribed wireless terminals. Wireless Terminals System-Wide Registration Counts The number of IP stations currently registered in the IP Stations system.

  • Page 216: Display Communication-Interface Hop-Channels

    Maintenance Commands Field descriptions (page 10) Current System Information Software Load The current software load on which the system is running. Memory The system platform. Configuration Offer Category The system’s offer category. Last Translation Loaded Information Software Load The software load translations saved before upgrade or reboot. Can also be unknown/no trans if no flash card is present.

  • Page 217: Display Communication-Interface Links

    display communication-interface links Output for Hop-channels qualifier Use display comm hop to display the Hop Channel Assignment screen, similar to the screen below. The number of the local processor channel, used to hop the interface link channels, is not shown. display communication-interface hop-channels Page 1 of...
  • Page 218 Maintenance Commands display communication-interface links Page 1 of INTERFACE LINKS Link Enable Est Ext Type Destination DTE Conn Name Conn Number DCE Mod. 1: y 2991 ETHERNET ethernet on link 1 2: n 3: n 4: n 5: n 6: n 7: n 8: n 9: n...

  • Page 219: Display Disabled-Tests

    display disabled-tests display disabled-tests Use display disabled-tests to list the numbers for all maintenance tests that have been disabled by INADS. These tests will not be available for background or demand testing. Action/Object Qualifier Qualifier Description Logins Default Feature Interactions display [print | Report sent to printer...
  • Page 220 Maintenance Commands System Reboots and the Error Logs The system saves the alarm and error logs to the memory card if any of the following events occur: The save translation command is executed. Translations are saved as part of scheduled maintenance. A reboot takes place.
  • Page 221 display errors Action/ Feature Object Qualifier Qualifier Description Logins Default Interactions display high Highlights the time stamps on the Error init all errors none errors resolution Report for the first and last occurrences of inads displayed the error. craft cust print Report sent to printer schedule...
  • Page 222 Maintenance Commands Field descriptions Enter the error type. If blank, the system displays all errors. Error Type active-alarms Error List errors cleared-errors The Hardware Error Report title includes the name of the error list. Enter one of the codes: Interval m = last month h = last hour d = last day...
  • Page 223 display errors The screen below is an example of an Hardware Error Report -- Active Alarms, without the high-resolution qualifier in the command line. display errors Page SPE A HARDWARE ERROR REPORT - ACTIVE ALARMS Port Mtce First Last Err Err Rt/ Al Ac Name Name Type...
  • Page 224 Maintenance Commands Sequence Count - This number indicates the order of errors logged Seq Cnt within a second for the time stamps associated with the first occurrence and last occurrence of an error. This information is displayed only if the high-resolution command line option is entered. There may be gaps for the sequence numbers within a given second since the last occurrence of an error may replace an existing entry that had been assigned the missing sequence number.
  • Page 225 display errors The screen below is an example of an Hardware Error Report -- Active Alarms, with the high-resolution qualifier in the command line. When you enter display errors high-resolution, the system adds the Seq Cnt (sequence count) column. The number in the column indicates the order of errors logged within a second for the time stamps associated with the first occurrence and the last occurrence of an error.

  • Page 226: Display Events

    Maintenance Commands display events Use display events to diagnose and correct vectoring problems. 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.
  • Page 227 display events Field descriptions Enter the type of event report, denial or vector. Category The fields in this section allow you choose the time period for the Report Period vector events you want to view only. If blank, all vector events recorded appear.
  • Page 228 Maintenance Commands Field descriptions for display events Event Type The event identification number that points to a specific piece of software code (see Table 18). Event Description A 25-character string describing the problem (see Table 18). Event Data 1 The station UID that is attempting to register (see Table 18).
  • Page 229 display events Table 18. Denied IP events — Continued Event Event Event Type Event Description Explanation Data 1 Data 2 1909 IP RRJ-RemoteOfc Registration rejected because: IP address misadmin Remote Office is enabled on the Signaling Group screen, but the RRQ is not from a supported Remote Office product.
  • Page 230 Maintenance Commands Table 18. Denied IP events — Continued Event Event Event Type Event Description Explanation Data 1 Data 2 1915 IP RRJ-Invalid Registration rejected because the IP address Major endpt/Ver endpoint version is not compatible version with the gatekeeper version. number in 2nd byte;...
  • Page 231 display events Table 18. Denied IP events — Continued Event Event Event Type Event Description Explanation Data 1 Data 2 1924 IP RRJ-No GRQ msg Registration rejected; did not IP address rcvd receive a Gatekeeper Request message 1925 IP RRJ-RQ: new LM Registration rejected;...
  • Page 232 Maintenance Commands Table 18. Denied IP events — Continued Event Event Event Type Event Description Explanation Data 1 Data 2 1930 IP RRJ-No voice Registration rejected: endpoint IP address path spec has neither an associated multimedia extension nor a specified voice path, hence, no audio path.
  • Page 233 display events Table 18. Denied IP events — Continued Event Event Event Type Event Description Explanation Data 1 Data 2 1940 IP RRJ-Duplicate ext Registration rejected as a IP address duplicate extension. 1941 IP KA-from invld Keep Alive registration request Endpoint IP address endpt ID...
  • Page 234 Maintenance Commands Table 18. Denied IP events — Continued Event Event Event Type Event Description Explanation Data 1 Data 2 1952 IP GRJ-Invld Gatekeeper request rejected: Gatekeeper IP address gatekeeperID message is not for this gatekeeper. First value is gatekeeper ID. Second value is IP address.
  • Page 235 display events Table 18. Denied IP events — Continued Event Event Event Type Event Description Explanation Data 1 Data 2 1960 IP GRJ-GRQ: new Gatekeeper request rejected IP address LM fail because of failure to create new LoginMgr. Possible causes No available heap memory to create LoginMgr Cannot start LoginMgr timer...
  • Page 236 Maintenance Commands Table 18. Denied IP events — Continued Event Event Event Type Event Description Explanation Data 1 Data 2 1970 IP BRJ-Endpt not reg Bandwidth Request rejected: the IP address endpoint is not registered. 1971 IP BRJ-Build BCF Bandwidth Request rejected: IP address failure to build a Bandwidth Request Confirm (BCF) message...
  • Page 237 display events Table 18. Denied IP events — Continued Event Event Event Type Event Description Explanation Data 1 Data 2 1983 IP ARJ-CRV already Admission Request rejected: call IP address in use reference value (CRV) is already in use by another call. 1984 IP ARJ-CRV does Admission Request rejected: this...
  • Page 238 Maintenance Commands Table 18. Denied IP events — Continued Event Event Event Type Event Description Explanation Data 1 Data 2 1996 IP URJ-Unexpected Unregistration Request rejected: IP address NSD msg unexpected non-standard data (NSD) in the URQ from the registered application endpoint. 1997 IP URJ-User is on a Unregistration Request rejected:...
  • Page 239 display events Table 18. Denied IP events — Continued Event Event Event Type Event Description Explanation Data 1 Data 2 2007 IP FURQ-User, no Force Unregistration Request. IP address sig conn Unregister user because there is no signalling connection. RAS is alive, but the signalling connection has gone down (user cannot make calls).
  • Page 240 Maintenance Commands Table 18. Denied IP events — Continued Event Event Event Type Event Description Explanation Data 1 Data 2 2012 IP FURQ-Aged Force Unregistration Request. IP address Endpt-no KA Unregister endpoint that has aged out. Endpoint’s time to live (TTL) expired without receiving a keep-alive RRQ.

  • Page 241: Display Failed Ip-Network-Region

    display failed ip-network-region display failed ip-network-region Use display failed network-region to display pairs of network regions with failed connectivity. In descending order of severity, display failed ip-network-region lists up to100 network regions with the most severely broken connectivity. To troubleshoot broken connectivity, also see ‘‘status ip-network-region’’...

  • Page 242: Display Initcauses

    Maintenance Commands display initcauses Use display initcauses to display a history of recovery steps taken by the system. Each time the system performs some type of recovery (due to user request or a hardware or software problem), the recovery information is stored. The software error log also contains information pertaining to restarts.
  • Page 243 display initcauses Field descriptions Bad Memory: A defective memory circuit pack generating too many Cause errors caused a restart. System Technician Request: The restart was performed because of system technician demand. A system technician requested reset system 4 entry should always precede an upgrade software entry.

  • Page 244: Display Memory-Configuration

    Maintenance Commands The level of recovery performed by the system. The recovery levels follow: Action Reset system 1 (Warm) Reset system 2 (Cold-2) Reset system 3 (Cold-1) Reset system 4 (Reboot) Reset system 5 (Extended Reboot) Whether the restart was escalated to a higher level to clear the problem. Escalated There is a software escalation strategy that can cause a higher level restart than the one previously performed to be executed if the need...

  • Page 245: Display Node-Names

    display node-names Output The following output example is for display memory-configuration when on a G3V9si platform with SPE duplication: display memory-configuration PROCESSOR MEMORY-CONFIGURATION (M bytes) SPE_A SPE_B Flash ROM: Total DRAM: SIMM A: SIMM B: SIMM C: Command successfully completed For the Simplex SPE configuration, the column under “SPE_B”...
  • Page 246 Maintenance Commands Field descriptions (page 1) Audix Name Identifies the name of the adjunct or switch node. Enter 1-7 characters for audix or msa; 1-20 characters for others. Default is blank. IP Address IP address for the adjunct or switch. Enter 0 - 255 or leave blank. IP Address IP address for the adjunct or switch.

  • Page 247: Display Port

    display port display port Use display port to display the port location, the equipment connected to the port, and the identification for the port (for example, an extension number or the trunk group and member). Action/ Object Qualifier Qualifier Description Logins Default Feature Interactions...

  • Page 248: Display Synchronization

    Maintenance Commands display synchronization Use display synchronization to display the administered synchronization stratum and reference sources. This screen is display only. Action/ Feature Object Qualifier Qualifier Description Logins Defaults Interactions display print Report sent to printer init none See below synchro- inads schedule...

  • Page 249: Display System-Parameters Duplication

    display system-parameters duplication Field descriptions Synchronization stratum that is used (3 or 4) Stratum First choice system synchronization source (blank = no synchronization); Primary valid only if stratum 4 synchronization specified Second choice system synchronization source (blank = no Secondary synchronization);...

  • Page 250: Display System-Parameters Maintenance

    Maintenance Commands Action/Object Qualifier Qualifier Description Logins Default Feature Interactions display duplication SPE or PNC duplication init none none system- inads Examples: parameters craft display system-parameters duplication Output The following example shows display system-parameters duplication. Page 1 of 1 DUPLICATION-RELATED SYSTEM PARAMETERS Enable Operation of SPE Duplication? y Enable Operation of PNC Duplication? y Screen 57.
  • Page 251 display system-parameters maintenance Feature Action/Object Qualifier Qualifier Description Logins Defaults Interactions display print Report sent to printer init none none system- inads schedule Use the screen to schedule parameters craft execution of the command. The maintenance super-user command is placed in the Maintain command queue and is executed Switch...
  • Page 252 Maintenance Commands display system-parameters maintenance Page 2 of 3 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:...
  • Page 253 display system-parameters maintenance Field descriptions 10-digit number, starting with 1, that identifies the switch to an Product Identification Operations Support System (OSS), for example, INADS. First telephone number that the switch dials to report alarms; First OSS Telephone Number must be obtained from the National Customer Support Center (NCSC) or the TSC.
  • Page 254 INADS Port administration and maintenance interface, via the INADS port when using customer login ID’s. This field can only be activated by Avaya services through system-parameters maintenance administration. Default is n. Indicates the number of minutes that the system must wait...
  • Page 255 display 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. The hour and minute (24-hour notation) at which daily scheduled Start Time maintenance begins. (22:00) Time (hour and minute) when scheduled daily maintenance stops.
  • Page 256 Maintenance Commands When the number of call progress tone receivers in service falls Minimum Threshold for below this number (2 to 100), a WARNING alarm is raised against CPTRs TTR-LEV. These are also known as general purpose tone detectors (GPTDs). There are 8 CPTRs on each TN2182. To alarm the first occurrence of a CPTR being taken out of service, set this field to the total number of CPTRs in the system.
  • Page 257 display system-parameters maintenance Extension number for the test call. This test extension number is DSO Loop-Around Test Call used to establish a loop-around connection on the selected trunk. Extension The DSO Loop-Around Test Call feature is used primarily for testing DSO channels associated with non-ISDN-PRI trunks.

  • Page 258: Modem Connection

    Maintenance Commands These fields indicate whether a Disk circuit pack is present in the SPE Optional Boards 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.
  • Page 259 display system-parameters maintenance This field will turn off the default data compression algorithms that Disable Data Compression are in use by most consumer modems. This field is 6 characters long and is case in-sensitive. (&K0) This field will turn on the V.42 LAPM and MNP error control Enable Error Control protocols, if available on the modem.

  • Page 260: Display Test-Schedule

    Maintenance Commands Most off-the-shelf external modems provide a timer that abandons No Answer Time-Out any outbound data call after a predetermined interval. Some modems provide for this timer to be disabled, thus allowing an outbound call to ring indefinitely. AT&T Paradyne does not provide this capability with their modem line, because it is generally undesirable to have an outbound call attempt ring indefinitely.
  • Page 261 display test-schedule Page 1 of 1 ATMS TRUNK TEST SCHEDULE Schedule No: __ Schedule Time: __:__ Schedule Test Days Interval: __ Schedule Date: __/__/__ SU: _ TU: _ TH: _ SA: _ Duration: __ OTL Throttle: _ MO: _ WE: _ FR: _ Test Type: ______ Trk Bgn End...
  • Page 262 Maintenance Commands One of the following types of test to be performed on the trunk Test Type group/members in this schedule: full runs the most comprehensive test and collects all associated measurements for each TTL type. supv performs a supervision test and only confirms the presence of the test set at the far end.

  • Page 263: Display Time

    display time display time Use display time to display the system time. Feature Action/Object Qualifier Qualifier Description Logins Default Interactions display time print Report sent to printer init none Date and time are inads generally used by schedule Use the screen to schedule craft the system.

  • Page 264: Download Update-File

    Maintenance Commands download update-file Use download update-file to transfer the update file to the system asynchronously from either an INADS host or a personal computer (PC) using the XMODEM protocol. Remote download Remote users can dial into the system by either using the “call” command (from an INADS host) or by dialing the system directly with a modem.
  • Page 265 download update-file Feature Interactions The form displayed for list configuration software-vintage reflects the changes imposed by the flash architecture. The list configuration software command allows INADS to determine with one query the hardware configuration, software vintage, and patch identifier. There is no interaction with routine periodic or scheduled maintenance, because patches are only applied on restarts before the system is in normal operation.
  • Page 266 Maintenance Commands Error on Application of the Patch A patch may not have been applied for the following reasons: 1. The memory card is write-protected. Remove this protection and issue a reset system x command 2. The patch identifiers are inconsistent. Run list configuration software and compare the old_patch identifier with the values in the update file.

  • Page 267: Enable Administered-Connection

    enable administered-connection enable administered-connection Use enable administered-connection to restart scheduled and periodic maintenance for a single or all administered connections, and to track the maintenance processing of administered connections without interference from other maintenance processing. This command also restarts the processing of in-line errors for all or the selected administered connection.

  • Page 268: Enable Suspend-Alm-Orig

    DS1 alarms before a customer resolves facility problems (for example, a T1 trunk that has developed an off-board condition). Improved control over internal (Avaya) problems that cannot be resolved immediately. For example, the command can be used to suspend Alarm Origination for a bad circuit pack detected late Friday night and dispatch personnel cannot respond until Monday.

  • Page 269: Enable Synchronization-Switch

    enable synchronization-switch enable synchronization-switch Use enable synchronization-switch to re-enable automatic clock switching, or to return the maintenance subsystem back to the normal state. The synchronization subsystem consists of the TDM bus clock, DS1 trunk board, and SPE-resident maintenance and administration software and provides error free digital communication between the system and other PBXs, COs, or customer-premise equipment (CPE).
  • Page 270 Maintenance Commands Output get boot-image 1C07 DISPLAY FIRMWARE IMAGE(S) Image 1 Image 2 Board Type: TN2501 TN2501 FW Vintage: 02 HW Signature: 02 Suffix: A Date: 03/02/02 03/02/01 Timestamp: 10:30:50 12:42:18 CRC Checksum: Good Good Active Image: Yes Reboot Image: Yes Screen 58.

  • Page 271: Get Ethernet-Options

    get ethernet-options get ethernet-options Use get ethernet-options to generate a report about an ethernet connection. Action/Object Qualifier Qualifier Description Logins Default Feature Interactions get ethernet-options location The physical location of init none the circuit pack (UUCSS) inads craft customer Output display ethernet-options 1C07 Administered Value Actual Value...

  • Page 272: Get Vector

    Maintenance Commands get vector Use get vector to display the conditions and the Switch Processing Element (SPE) associated with a core dump of memory to tape or memory card. The dump occurs on the tape or disk of the previously active SPE or the SPE previously specified using set vector in systems with duplicated SPEs.
  • Page 273 get vector Field descriptions A hexadecimal value representing the condition(s) that cause(s) a Core Dump Vector core dump. This hexadecimal value is a bit map of the four reset conditions (from least to most significant bit): warm start cold 2 restart cold 1 restart reboot.

  • Page 274: List Communication-Interface Processor-Channel

    Maintenance Commands list communication-interface processor-channel Action/ Object Qualifier Qualifier Description Logins Default Feature Interactions list number Example: init none none communication- list inads interface communication-interface craft processor-channel processor channel 125 Output The following example shows the output for list communication-interface processor-channel.
  • Page 275 list communication-interface processor-channel Field descriptions Displays the BX.25 virtual channel number or the TCP/IP listen Proc Chan port channel to carry this processor (virtual) channel. Type y to enable a processor channel. Enable Type n to disable a processor channel. Identifies the switch application used over this link.

  • Page 276: List Configuration

    Maintenance Commands list configuration Use list configuration to list the group, the type, code, suffix, and vintage of the requested circuit packs as installed in the system, and all ports assigned to the circuit pack. Feature Action/Object Qualifier Qualifier Description Logins Default Interactions...
  • Page 277 list configuration stations Displays all circuit packs that can be assigned stations, including DS1 circuit packs for remote stations. trunks Displays all circuit packs that can be used for administering trunks. Output The following display shows the output from list configuration all. list configuration all Page SYSTEM CONFIGURATION...
  • Page 278 Maintenance Commands The circuit pack is administered but not physically installed no board The circuit pack administered to the slot differs from the circuit pack conflict that is physically installed The T1 link is down to a DS1 circuit pack no link The following display shows output from list configuration ds1.

  • Page 279: List Configuration License

    list configuration license list configuration license In duplicated systems, use list configuration license long to display the serial number of both active and standby hardware from the TN2404 Vintage 3 Processor circuit packs. The License Serial Numbers screen displays the license file serial number(s) embedded in the current License File.

  • Page 280: List Configuration Software-Version

    Maintenance Commands list configuration software-version Use list configuration software-version to display: Software version numbers and compatibility indexes of the software load modules stored in system memory (RAM) and on the Mass Storage System devices (tape). The dates and times when translation and announcement data were last saved to the MSS.
  • Page 281 list configuration software-version list configuration software-version Page SOFTWARE VERSIONS SPE-A SPE-B UPDATE FILE Creation (GMT) Date: none Old Version Tape: none Old Identifier Tape: none New Identifier Tape: none Update State: none in memory SOFTWARE VERSION Memory Resident: G3V6i.00.1.017.0 Mem Card Resident: none Update Identifier: none TRANSLATION DATE Memory Resident:...
  • Page 282 Maintenance Commands Information related to the translation files as stored in memory Translation Date and the MSS. Date and time when translation data was last read from the Memory Resident MSS into memory. This is stored in SPE memory and is not modified by changes to translation data.
  • Page 283 list configuration software-version Information related to the Packet Control firmware. Information is PKT-CTRL FW displayed for the Packet Control circuit pack resident copy as Version well as the corresponding tape file The version of firmware in the Packet Control circuit pack. Pkt-ctrl Resident The version of the Packet Control circuit pack residing on the Flash Resident...

  • Page 284: List Directory

    Maintenance Commands list directory Use list directory board ppcss to list all files in the path directory of the ppcss board memory filesystem. NOTE: In R9 and later versions, the forward slash is the default path for listing files in the root directory. To list the files in a directory other than the “/” root directory, the complete path must be specified.

  • Page 285: List External-Device Alarm

    list external-device alarm Output The following example shows the output from list disabled-MOs. list disabled-MOs DISABLED MAINTENANCE OBJECT INFORMATION Maintenance Name Location Status Enabled DIG-LINE 01A1203 Disabled Field descriptions The type of maintenance object (or group of maintenance objects) that Maintenance Name have been disabled.

  • Page 286: List History

    Maintenance Commands list eda-external-device-alrm Page 1 of 1 SPE A EXTERNAL DEVICE ALARM PORTS Port Alarm Description Product Type Name Identifier 01c1201 minor UPSI DC battery discharged 7000000001 01c1202 major Audix1 Main Audix main equipment 8123456790 01major minor UPSI DC rectifier alarm 7000000001 01minor minor...
  • Page 287 list history All information in the transaction log is saved on tape as translation data when save translation is performed (LIFO order). When the switch COLD I starts or reboots, the saved translation and the transaction log are loaded from tape. In this way, the translation data and the data in the transaction log remain compatible.
  • Page 288 Maintenance Commands Output list history Page 1 HISTORY Date of Loaded Translation: 10:08pm Wed Feb 14,2001 Date Time Port Login Actn Object Qualifier 2/18 12:34 1A0301 tti-m station 4000 2/18 12:23 1B0401 psa-a station 4003 2/16 09:44 2B0608 tti-s station 4003 2/16 09:22 1D0708...

  • Page 289: List Ip-Route

    Use list ip-route to display a list of the IP routes from the Avaya Definity Server CSI out to the LAN. Enter the board parameter and specify which C-LAN circuit pack for which to show the IP routes (for example, list ip-route board UUCss).

  • Page 290: List Isdn-Testcall

    Maintenance Commands Indicates whether a C-LAN circuit pack has accepted the administered Accepted by CLAN IP-route. Routes for a link are downloaded to the C-LAN circuit pack when the link comes into service. Possibilities include: accepted – the route has been accepted by the C-LAN circuit pack rejected –...

  • Page 291: List Marked-Ports

    list marked-ports Field descriptions Trunk in use for the ISDN-PRI test call (trunk group number/member B-Channel number). Time the test call started (dd/hh:mm format). Start Time Expected duration of the test call. Duration The TN771 Maintenance/Test circuit pack’s digital port address (in M/T Port cabinet/carrier/slot/circuit format) in use for the outgoing asynchronous ISDN-PRI test call.

  • Page 292: List Measurements Clan Ethernet

    After the occurrence of “N/A” (not available), the delta equals the total. The primary use of this command is to quickly and unambiguously determine if the fault lies within the Avaya-provided equipment or if the fault is with the LAN or LAN administration to which the Avaya equipment is connected.
  • Page 293 list measurements clan ethernet Action/Object Qualifier Qualifier Description Logins Default Feature Interactions list clan Designates ethernet connection init none measurements ethernet inads craft UUCss Cabinet-carrier-slot address of cust the C-LAN circuit pack Report sent to printer. print Use the screen to schedule schedule execution of the command.

  • Page 294: List Measurements Clan Ppp

    Maintenance Commands The total value of the counter on the board Total NOTE: The counter value can be up to 11 digits long because of the 32-bit counter on the board. After the occurrence of an “N/A,” the delta equals the total. Busyout or release of a board or a port, the reset board command, and reseating the board all clear the firmware counters.
  • Page 295 list measurements clan ppp Action/Object Qualifier Qualifier Description Logins Default Feature Interactions list clan ppp Link identifier (primary or init Primary measurements secondary) inads craft UUCCSSpp Port Address cust print Report sent to printer schedule Use the screen to schedule execution of the command.

  • Page 296: List Measurements Clan Sockets

    Maintenance Commands Total value of the board counter. Total NOTE: The counter value can be up to 7 digits long because the 16- bit counter on the board. After the occurrence of an “N/A” the delta equals the total. Busyout or release of a board or a port, the reset board command, and reseating the board all clear the firmware counters.
  • Page 297 list measurements clan sockets Output The following example shows list measurements clan sockets hourly Page 1. list measurements clan sockets hourly 01B12 Page Switch Name: Date: 5:27 pm WED MAR 26, 1992 CLAN SOCKETS HOURLY REPORT (Last 24 Hours) Socket Socket Meas Avail...

  • Page 298: List Measurements Ds-1

    Maintenance Commands The following example shows list measurements clan sockets summary yesterday-peak Page 1. list measurements clan sockets summary yesterday-peak Page Switch Name: Date: 5:27 pm WED MAR 26, 1992 CLAN SOCKETS PEAK REPORT Peak Hour: 0400 Socket Socket Meas Avail Usage Socket...
  • Page 299 list measurements ds-1 Feature Action/Object Qualifier Qualifier Description Logins Defaults Interactions list Detailed report generated init none none measurements inads summary Summary report generated craft ds1_ The physical location of a DS1 circuit cust location pack entered as cabinet-carrier-slot. rcust browse Report sent to printer.
  • Page 300 Maintenance Commands Field descriptions (list measurements ds1-summary) The start time and date when the associated measurement Counted Since counters were cleared or the DS1 circuit pack was administered. The number of seconds from the beginning of the current Number of Seconds Elapsed Into Current 15-minute interval (0 - 900).

  • Page 301: List Measurements

    list measurements ds-1 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...

  • Page 302: List Measurements Ip Codec

    Maintenance Commands list measurements ip codec Use list measurements ip codec x to list IP media processing resource measurements for IP Media Processor & Medpro circuit packs. Feature Action/ Object Qualifier Qualifier Description Logins Default Interactions list hourly <region Lists the measurements for the none measurements number>...
  • Page 303 list measurements ip codec list measurements ip codec hourly 4 Switch Name: Date: 5:32 pm WED MAR 26, 1992 IP CODEC RESOURCE HOURLY REPORT G711 G723/9 --------------------- ------------------------- Meas Usage In Reg Out of Usage In Reg Out of Hour Region Rscs (Erl) Reg peg...
  • Page 304 Maintenance Commands The total number of times an IP media processor port was needed in G.711 Out the region for a G.711 call, but was successfully allocated to a of Reg peg resource in another region. Out of Region does not include denials. If “Network regions are interconnected?”...
  • Page 305 list measurements ip codec The following example shows list measurements ip codec detail yesterday-peak output for Region 4. list measurements ip codec detail 4 yesterday-peak 4 Switch Name: Date: 5:32 pm WED MAR 26, 1992 IP CODEC RESOURCE DETAIL REPORT G711 G723/9 ---------------------...

  • Page 306: List Measurements Ip Dsp-Resource

    Maintenance Commands list measurements ip dsp-resource list measurements ip dsp-resource x Use list measurements ip dsp-resource x to measure IP media processing resource on IP Media Processor & Medpro. Feature Action/ Object Qualifier Qualifier Description Logins Default Interactions list hourly Lists the measurements for the none measurements...
  • Page 307 list measurements ip dsp-resource list measurements ip dsp-resource hourly 4 Switch Name: Date: 5:32 pm WED MAR 26, 1992 IP DSP RESOURCE HOURLY REPORT Meas DSP Usage In Reg Out of Denied % Out Hour Region Rscs (Erl) Reg Peg of Srv 0400 4 xxxx...
  • Page 308 Maintenance Commands The total number of times an IP media processor port was needed in Out of Reg the region for a call, but was successfully allocated to a resource in another region. Out of Region does not include denials. If “Network regions are interconnected?”...

  • Page 309: List Measurements Ip-Signaling-Group

    list measurements ip-signaling-group The following example shows list measurements ip dsp-resource detail yesterday-peak output for Region 4. list measurements ip dsp-resource detail 4 yesterday-peak 4 Switch Name: Date: 5:32 pm WED MAR 26, 1992 IP DSP RESOURCE DETAIL REPORT Meas DSP Usage In Reg Out of...
  • Page 310 Maintenance Commands Output The following example shows the output for list measurements ip-signaling-group current-hour. list measurements ip-signaling-group current-hour Page 1 of 1 SPE A Switch Name: Date: 6:28 pm THU FEB 4, 1997 IP SIGNALING GROUPS LATENCY AND LOSS REPORT CURRENT HOUR 10 WORST PERFORMING IP SIGNALING GROUPS RANK ORDERED WORST TO LEAST WORST Hour...
  • Page 311 list measurements ip-signaling-group The following example shows list measurements ip-signaling-group today. The screen for “yesterday” has the same layout and content type, but the information applies to the previous day’s 24 hours. list measurements ip-signaling-group today Page 1 of 24 SPE A Switch Name: Date: 6:28 pm THU FEB 4, 1997 IP SIGNALING GROUPS LATENCY AND LOSS REPORT...

  • Page 312: List Mst

    Maintenance Commands list mst Use list mst to display the messages in the trace buffer, when a trace is active or disabled. If the trace is active, older messages may be sporadically omitted if wraparound is selected and the message rate is high. The integrity of the buffer remains intact even with repeated use of list mst.
  • Page 313 list mst Output The following example shows the output for list mst. list mst Message Sequence Trace Data Number Date/Time Type Message 12/21/90 14:30:21.220 00 00 74 17 08 02 00 11 05 04 03 80 90 a2 18 03 a1 83 86 70 01 80 96 28 0d 73 74 61 74 69 6f 6e 20 35 31 30 30 31 14:30:22.420 00 00 74 17 08 02 80 11 02 18 03 a9 83 86...
  • Page 314 Maintenance Commands Table 19. Summary of MST Message Types — Continued Code Description 0x25 PREC message 0x26 CMS outgoing (individual) 0x27 CMS incoming (individual) 0x30 CCMS uplink message 0x31 CCMS downlink message 0x32 Packet uplink message 0x33 Packet downlink message 0x40 IMT internal-message trace for call_p, conn_m, grp_m, serv_d, suser_m...
  • Page 315 list mst Table 19. Summary of MST Message Types — Continued Code Description 0xA1 X.25 Incoming application data message 0xA2 X.25 Application error message 0xB0 X.25 Outgoing session layer control message 0xB1 X.25 Incoming session layer control message 0xCF X.25 Message confirmation 0xD0 X.25 Outgoing processor channel control message 0xD1...
  • Page 316 Maintenance Commands Version 2 of MST message type 0xA2 would appear on the list mst output: Number Date/Time Type Message 12:41:14:112 A2-02 17 10 21 03 32 05 01 80 Vector Trace Message type: 0x10 Message format: Message[1-4] = call identifier (CID) (defined in $BASEPJ/hdrs/capro.h) Message[5-6] = vector number (defined in $BASEPJ/hdrs/dpm_calls.h) Message[7]...
  • Page 317 list mst Events are defined in $BASEPJ/hdrs/evnt_defs.h. Events based on the call_p will have the following auxiliary data: Message[7-8] = vector number Message[9-10] = step number Events based on the grp_m will have the following auxiliary data: Message[7-10] = hunt group number IMT (D92) The messages described in this section cannot be controlled directly through any of the MST screens.
  • Page 318 Maintenance Commands 0x23 - MT_IMT (miscellaneous IMT hooks) This message type is for miscellaneous IMT hooks. The only sub-type currently available is for a debug button (dbut). The button number is provided in the debug button MST message so that more than one button can be administered (through IMT) to convey different meanings.
  • Page 319 list mst serv_d (other serv_d messages): Message[1-4] = user identifier Message[5-6] = hook identifier (defined in $BASEPJ/hdrs/mstencode.h) Message[7] = STIM type Message[8-11] = service identifier Message[12-13] = interpreted STIM Message[14-17] = aux data 0 Message[18-21] = aux data 1 Message[22-25] = aux data 2 Message[26-29] = aux data 3...
  • Page 320 Maintenance Commands Packet (D92) Message type: 0x32 uplink Message format: Message[1-4] = user identifier Message[5-6] = hook identifier (defined in $BASEPJ/hdrs/mstencode.h) Message[7-10] = link identifier Message[11-12] = message type (defined in $BASEPJ/hdrs/pcd_calls.h) Message[13+] = standard packet message Message type: 0x33 downlink Message format: Message[1] = port network number...
  • Page 321 list mst 0x50 - ASAI level 2 uplink primitive Message[1] = Port Network Number of ASAI port Message[2] = reserved Message[3] = Carrier Address of ASAI port Message[4] = Port number of ASAI port Message[5] = SAPI Message[6] = TEI Message[7,8] = Link ID Message[9]...
  • Page 322 Maintenance Commands Message[7-10] = Link ID Message[11] = Uplink encode 0x01 - ASAI Link State 0x02 - TEI Management Message 0x03 - XID Message Message[12] = ASAI Link State: 0x00 - the link has gone down 0x01 - the link has come up 0x02 - the link id has changed 0x03 - the link has gone hyperactive 0x04 - the link has recovered...
  • Page 323 list mst Message[7,8] = Link ID NOTE: The Link ID has no meaning for the link establish request, therefore the Link ID field will contain 0xff 0x.ff Message[9] = Downlink encode 0x01 - ASAI Link Events 0x02 - TEI Management Message 0x03 - XID Message Message[10] = ASAI Link Events:...
  • Page 324 Maintenance Commands Message[11] = Downlink encode 0x01 - ASAI Link Events 0x02 - TEI Management Message 0x03 - XID Message Message[12] = ASAI Link Events: 0x02 - link release request 0x0f - link establish request sent to and received by the lower level = TEI Management Message 0x02 - Identity Assigned...
  • Page 325 list mst 0x53 - ASAI maintenance downlink Message[1] = Port Network Number of ASAI port Message[2] = Reserved Message[3] = Carrier Address of ASAI port Message[4] = Port number of ASAI 3 port Message[5] Message[6+] = standard or abbreviated ASAI message format 0x54 - ASAI unrecognized uplink Message[1] = Port Network Number of ASAI port...
  • Page 326 Maintenance Commands 0x55 - ASAI unrecognized downlink Message[1] = Port Network Number of ASAI port Message[2] = Reserved Message[3] = Carrier Address of ASAI port Message[4] = Port number of ASAI port Message[5] = failure reason Failure reasons 1 - link flow controlled 2 - internal software error - see software error log 3 - packet interface problem - see error log Message[6+]...
  • Page 327 list mst 0x57 - ASAI Association downlink Message[1] = Port Network Number of ASAI port Message[2] = Reserved Message[3] = Carrier Address of ASAI port Message[4] = Port number of ASAI port Message[5] = association type Message[6+] = standard or abbreviated ASAI message format 0x58 - ASAI error uplink Message[1] = Port Network Number of ASAI port...
  • Page 328 Maintenance Commands 0x62 - ISDN PRI downlink Message[1] = Port Network Number of D-channel port Message[2] = Reserved Message[3] = Carrier Address of D-channel port Message[4] = Port number of D-channel port Message[5+] = standard ISDNPRI format NOTE: In abbreviated format, the header of the Q.931 message, the cause IE (if present) and the channel id IE (if present) are the only IEs present.
  • Page 329 list mst 0x66 - ISDN BRI downlink Message[1] = Port Network Number of BRI port Message[2] = Reserved Message[3] = Carrier Address of BRI port Message[4] = Port number of BRI port Message[5] = SAPI Message[6] = TEI Message[7,8] = Link ID Message[9+] = standard ISDNBRI format Message[7-10]...
  • Page 330 Maintenance Commands 0x68 - ISDN BRI level 2 uplink primitive Message[1] = Port Network Number of BRI port Message[2] = Reserved Message[3] = Carrier Address of BRI port Message[4] = Port number of BRI port Message[5] = SAPI Message[6] = TEI Message[7,8] = Link ID Message[9]...
  • Page 331 list mst Message[7-10] = Link ID Message[11] = Uplink encode 0x01 - BRI Link State 0x02 - TEI Management Message 0x03 - XID Message Message[12] = BRI Link State: 0x00 - the link has gone down 0x01 - the link has come up 0x02 - the link id has changed 0x03 - the link has gone hyperactive 0x04 - the link has recovered...
  • Page 332 Maintenance Commands Message[7,8] = Link ID NOTE: The Link ID has no meaning for the link establish request, therefore the Link ID field will contain 0xff 0xff Message[9] = Downlink encode 0x01 - BRI Link Events 0x02 - TEI Management Message 0x03 - XID Message Message[10] = BRI Link Events:...
  • Page 333 list mst Message[7-10] = Link ID NOTE: The Link ID has no meaning for the link establish request, therefore the Link ID field will contain 0xff 0xff 0xff 0x.ff Message[11] = Downlink encode 0x01 - BRI Link Events 0x02 - TEI Management Message 0x03 - XID Message Message[12] = BRI Link Events:...
  • Page 334 Maintenance Commands R1/R3 change types: 0x01 - session up notification 0x02 - Session down notification 0x6D - ISDN PRI level 2 downlink primitive (not implemented) Message[1] = Port Network Number of D-channel port Message[2] = Reserved Message[3] = Carrier Address of D-channel port Message[4] = Port number of D-channel port Message[5]...
  • Page 335 list mst Message[7,8] = Link ID Message[9] = type of failure Types of failure: 0x01 - outgoing ISDN 0x02 - incoming ISDN Message[10+] = standard ISDNBRI format Message[7-10] = Link ID Message[11] = type of failure Types of failure: 0x01 - outgoing ISDN 0x02 - incoming ISDN NOTE: In abbreviated format, the header of the Q.931 message, the cause IE (if...

  • Page 336: List Registered-Ip-Stations

    Maintenance Commands 0x72 - Time changed while trace enabled Message[1] = 0x00 Message[2] = timestamp indication timestamp indication: 0x00 - MST timestamp is old time 0x01 - MST timestamp is new time list registered-ip-stations Use list registered-ip-stations to display information about the ip stations registered at a customer’s facility.
  • Page 337 list skill-status Table 20 displays data for each skilled hunt group. Table 20. Skilled Hunt Group Status Data Group Number Group Name Group Extension Group Type Service Level Call Selection Activate on Oldest Dynamic Threshold Supervisor Override Call Waiting Adjustment Dynamic Percent Dynamic Queue Service Objective...

  • Page 338: List Station

    Maintenance Commands list skill-status SKILL STATUS S C O D D D Grp Name/ Grp L S C T P Q Service Level 1 Level 2 No. Ext Type S O W A A P SO Level Threshold Threshold S General Inquiries English 3001 y n 20...

  • Page 339: List Suspend-Alm-Orig

    list suspend-alm-orig Output The following example shows the output of list station movable. list station movable STATIONS Port/ Name/ Room Data Cv1/ COR/ Cable/ Type Hunt-to Move Jack 1001 01A0301 Digital a0301 6402D always list suspend-alm-orig Use list suspend-alm-orig to list active entries on the Suspend Alarm Origination table.

  • Page 340: List Sys-Link

    Maintenance Commands Output The following example shows the output of list suspend-alm-orig. 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 list sys-link Use list sys-link to display all of the system links, including the location, link type and channel number, link state, current path status, faulted path status, and last recorded fault, if any.

  • Page 341: List Testcalls

    list testcalls Output The following examples shows the output from list sys-link. list sys-link Page SPE A SYSTEM LINKS INFORMATION Location Link Type/ State Current Faulted Last Fault Channel Path Path Recorded 01A0516 present present 12/30/1996 14:18 Field descriptions Physical location of the port associated with the system link Location (cabinet-carrier-slot-circuit) Type of system-link and the processor channel number of...
  • Page 342 Maintenance Commands The measurements are produced by a set of analog trunk tests. The tests are initiated by a maintenance demand test or by a set of scheduled tests. The largest portion of these measurements are generated through scheduled testing during system quiet hours (hours where the traffic volume is low).
  • Page 343 list testcalls list testcalls detail grp 78 to-grp 80 list testcalls detail grp 78 to-grp 80 mem 1 print list testcalls detail grp 78 to-grp 80 mem 1 not-result pass list testcalls detail grp 78 to-grp 80 mem 1 count 2 schedule list testcalls detail grp 78 to-grp 80 mem 1 to-mem 5 list testcalls detail grp 78 to-grp 80 mem 1 to-mem 5 count 3 print list testcalls detail grp 78 to-grp 80 mem 1 to-mem 5 count 3 result pass...
  • Page 344 Maintenance Commands Detail report field descriptions The trunk group number selected. Group The trunk group type. Type The vendor of this trunk group. Vendor The kind of test line for this trunk group. TTL Type The list of marginal and unacceptable threshold values defined on Threshold Values the trunk group form.
  • Page 345 list testcalls 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. The following example is the output from list testcalls summary grp 80. list testcalls summary grp 80 SPE A ATMS MEASUREMENT SUMMARY REPORT...

  • Page 346: List Trace

    Maintenance Commands list trace Use list trace to troubleshoot misdirected calls, trunking/routing problems, and call denials. This command allows you to view the Virtual Path Identifier (VPI) and Virtual Channel Identifier (VCI) data, adding either of these qualifiers: list trace attendant list trace data-module list trace previous list trace ras...
  • Page 347 list trace list trace ras Use list trace ras to see the registration, admission, and status messages in H.225 used between two H.323 entities for gatekeeper discovery and endpoint registration. This information is helpful when an endpoint fails to register. For example, use list trace ras for a particular endpoint, then register the endpoint.

  • Page 348: Mark Port

    MultiVantage Software running on the Definity Server CSI ATM cache reuse indicates that an SVC in the Avaya MultiVantage Software running on the Definity Server CSI ATM cache has been reused mark port Use mark port to mark faulty ports as defective to prevent their use in other administrative operations (for example, adding a data-module or station).

  • Page 349: Monitor Bcms

    monitor bcms Use clear port command to reactivate the port. Use list marked-ports command to display the marked ports in list format. All marked port information is saved as part of translations. Action/Object Qualifier Qualifier Description Logins Defaults Feature Interactions mark port location Location of the port to be...
  • Page 350 Maintenance Commands Output The following examples shows the output from monitor bcms system. monitor bcms system Page 1 of BCMS SYSTEM STATUS Date: 14:02 THU OCT 17 1991 CALLS OLDEST ANSW AVAIL ABAND AFTER SPLIT WAIT CALL SPEED AGENT ABAND TIME TALK CALL...
  • Page 351 monitor bcms The number of Automatic Call Distribution (ACD) calls handled by this # ACD split during the current period. This includes calls that intraflow into the split. This field is measurement data. The average talk time for Automatic Call Distribution (ACD) calls AVG TALK handled by this split during the current period.
  • Page 352 Maintenance Commands The number of agents currently available to receive an Automatic Call Avail 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.

  • Page 353: Monitor Health

    monitor health The number of non-ACD (Automatic Call Distribution) calls that the agent EXTN IN CALLS has received (incoming) and completed during the current period. The maximum number of calls is 255, and if this maximum is exceeded, 255 is displayed.
  • Page 354 Maintenance Commands status health ALARM SUMMARY CABINET STATUS Major: Minor: Emerg Alarms Warning: Cab Trans Mj Mn Wn PNC 0| 7| 0 up BUSY-OUT SUMMARY 0| 0| 4 up Trunks: n.a. 0| 2| 0 up Stations: 0| 0| 0 up/up Others: PROCESSOR OCCUPANCY STATUS Static:...
  • Page 355 monitor health Currently-active processor complex. When the active processor complex Active SPE is locked on-line with lock switching on DUPINT, the “lock” option displays; otherwise, “auto” displays. Duplication status of the SPE (n). Duplicated Current power source for the processor complex. The normal state is SPE Power “commercial”.

  • Page 356: Monitor Security-Violations

    Maintenance Commands monitor security-violations Use monitor security-violations to display information about failed attempts to access the system, including the time of the violation, the login entered, and the port accessed during the failed login attempt. The system logs trunk group numbers, members, and extensions for remote access violations.

  • Page 357: Monitor System

    monitor system MGR1 represents a connection to a system SAT port. Connections are MGR1 either hardwired or dialed-up. Extension assigned to the data module that failed during “logging in” session. If a data module is not used, this field is blank. Date of the logged security violation shown as MM/DD (where MM = month Date and DD = day).
  • Page 358 Maintenance Commands Qualifier Description view1 This screen displays attendant status, maintenance status, last hour’s measurement of trunk groups, hunt groups, attendant groups, and the time of day. view2 This screen displays a subset of view1 form entries. It includes view1 forms except the last hour’s hunt group measurements.
  • Page 359 monitor system 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...
  • Page 360 Maintenance Commands Total abandoned calls by the caller. Calls aban The ratio of outgoing calls that are not carried (due to overload %Out blkg conditions) on a trunk group to outgoing calls offered. The percentage of time within polling intervals that all trunks in the trunk % Time ATB group are unavailable for use.
  • Page 361 monitor system This field contains a value of 0 or 1 depending related to Next_hour measurements taken this hour or the next. This hour reflects maximum call rates. When this flag is set, statistics accumulate for the next hour and shortly thereafter. This field holds the total time slots in use during the time period tot_ts_req elapsed since the top of the last hour.

  • Page 362: Monitor Traffic

    Maintenance Commands This field reflects the total number of requested call progress tone Requests-TN744 CPTRs receivers that are currently active. It decrements when call progress tone receivers are freed and increments when they are requested. This field applies strictly to the TN744 board. This field represents real-time status data.
  • Page 363 monitor traffic monitor traffic hunt-groups HUNT GROUP STATUS 22:49 SAT DEC 31 1988 LCIQ LCIQ (#: Group; S: Grp Size; A: Active Members; Q: Q Length; W: Calls Waiting) (LCIQ: Longest Call In Queue in seconds) Field descriptions Group number for trunk group or hunt group. Number of members administered for each trunk or hunt group.

  • Page 364: Monitor Trunk

    Maintenance Commands monitor trunk Use monitor trunk to display internal software status information. This command helps to locate facilities to which the trunk is communicating. If a trunk group number is entered without a member number, and with or without “/”, it is member 1.

  • Page 365: Netstat Arp

    netstat arp This field identifies maintenance testing that occurs on the trunk. Maintenance Busy The state of temporary signaling connections. (connection set up to CA-TSC State pass call information over PRI signaling links). netstat arp Use netstat arp to: display the contents of the C-LAN circuit pack’s Address Resolution Protocol (ARP) table.
  • Page 366 Maintenance Commands Output netstat arp unsorted The following example shows the output of . The display contains as many pages as are required to display all of the data received from the C-LAN circuit packs. netstat arp unsorted Page 1 of Net to Media Table C-LAN IP Address...
  • Page 367 netstat arp The characters shown in bold type indicate duplicate IP addresses found in the ARP data. Use the Field descriptions (netstat arp) to further interpret this report. The following output example is a display of netstat arp mac-sort. The actual display contains as many pages as are required to display all of the data received from the C-LAN boards.

  • Page 368: Netstat Ip-Route

    Maintenance Commands Field descriptions (netstat arp) A switch-generated, sequential reference number Net Seq Displays the location of the TN799 (C-LAN) circuit pack C-LAN Displays the IP address of the circuit pack Address Displays the MAC address of the circuit pack. Phys Addr If other, the IP address and the MAC address for the circuit...

  • Page 369: Ping

    ping Field descriptions The location of the circuit pack that provides the interface for Board/Pt the route. Display-only field showing the IP address of each route’s Destination destination. The Destination is administered on the Node Name screen. On the Node Name screen, “Default” in the Destination field administers the default route.
  • Page 370 Maintenance Commands Action/ Feature Object Qualifier Qualifier Description Logins Defaults Interactions ping ip-address The IP address of the device to ping in init packet the following format: www.xxx.yyy.zzz inads length = craft 64 bytes Administered node name (use display customer node-name node-names) The location of the C-LAN or IP...
  • Page 371 ping ping node-name Use ping node-name to ping an administered node. Use display node-names to look up the node-name. ping board Use ping board UUCSS to ping from a specific C-LAN circuit pack. If only one C-LAN or IP Medpro board circuit pack is present, the board qualifier is optional. If the “board”...
  • Page 372 Maintenance Commands ping ip-address 192.68.3.26 packet-length 1500 TEST RESULTS End-pt IP Port Port Type Result Time(ms) Error Code 192.68.3.26 01C0202 PPP-PT PASS XXXX Field descriptions The TCP/IP destination address of the ping command. End-pt IP Location of the C-LAN circuit pack (UUCSS). Port Can be either PPP-PT for PPP ports (ports 1-16) or ETH-PT for the Port Type...

  • Page 373: Recycle Carrier

    recycle carrier Table 21. Ping command error messages — Continued Message Interpretation The internal error of not being able to find Error encountered, could not the port through which the IP address is complete request reached. The packet size is greater than 1500 or less Out of range than 64 bytes in length or if there are invalid or unrecognized parameters...
  • Page 374 Maintenance Commands refresh route-table all Page 1 of C-LAN Board Location Number of Routes Removed Number of Routes Added 01B11 01B12 01B13 01C05 01C06 01C07 01C08 01C09 01C10 01C11 Refresh Route Table Is Completed Use the information in Field descriptions (refresh route-table) to interpret this report.

  • Page 375: Release Access-Endpoint

    release access-endpoint release access-endpoint Use release access-endpoint to remove all ports associated with the specified access endpoint from a maintenance busy state. Periodic and scheduled tests subsequently resume on the released ports. Maintenance completes background initialization testing on the released ports. For details of the test sequence, refer to [3].

  • Page 376: Release Board

    Maintenance Commands release board Use release board to activate administered maintenance objects on the circuit pack at specified locations. Action/Object Qualifier Qualifier Description Logins Defaults Feature Interactions release board location Board location: PCSS init none none inads craft Output The following output example is a display of release board 1c07 and assumes that the board in cabinet 1, carrier c, slot 7 is an analog board with three administered ports.

  • Page 377: Release Cdr-Link

    release cdr-link release cdr-link Use release cdr-link to remove maintenance objects associated with specified call detail recording (cdr)-links from a maintenance busy state. These links provide asynchronous data connections from switches to peripherals; they are composed of a: Far end data module Simulated data channel on a PKTINT board Manager that initiates and maintains the link Controller/protocol that services the link...

  • Page 378: Release Data-Module

    Maintenance Commands release data-module Use release data-module to activate the specified data module (or data channel). Hardware tests are executed to verify that the equipment is functioning. Feature Action/Object Qualifier Qualifier Description Logins Defaults Interactions release extension Extension number associated init none none...

  • Page 379: Release Journal-Printer

    release journal-printer release journal-printer Use release journal-printer to activate maintenance objects associated with a pms-log or wakeup-log link. Hardware tests are executed to verify that the equipment is functioning. For general information on journal printer links, see ‘‘busyout pms-link’’. For information on journal printers, see ‘‘status journal-link’’.

  • Page 380: Release Link

    Maintenance Commands release link Use release link to activate MOs associated with a link. Hardware tests verify that equipment is functioning properly. Feature Action/Object Qualifier Qualifier Description Logins Default Interactions release link link-id Number associated with each link (1–8). init none none inads...

  • Page 381: Release Mis

    release mis release mis Use release mis to activate management information systems. Hardware tests are executed to verify that equipment is functioning properly. Action/Object Qualifier Qualifier Description Logins Defaults Feature Interactions release mis init none none inads craft cust rcust Output The following example shows the output from release mis.

  • Page 382: Release Pms-Link

    Maintenance Commands Output The following example shows the output from release modem-pool 1. release modem-pool 1 SPE B COMMAND RESULTS Port Maintenance Name Alt. Name Result Error Code 01C0701 MODEM-PT PASS 01C0703 MODEM-PT PASS Field descriptions Port address (cabinet-carrier-slot-circuit) of busied out Port maintenance object.

  • Page 383: Release Port

    release port Feature Interactions Specific component maintenance performed on a link sometimes conflicts with link maintenance, itself (busied out objects create link setup failure). Frequent link re-setup attempts may delay faulty component recovery. For best results, technicians should use busyout to disable attempted link re-setup. Output The following example shows the output from release pms-link.

  • Page 384: Release Pri-Endpoint

    Maintenance Commands release port 01C0701 COMMAND RESULTS Port Maintenance Name Alt. Name Result Error Code 01C0701 ANL-LINE PASS Field descriptions Port address (cabinet-carrier-slot-circuit) Port The type of maintenance object that is being released. Maintenance Name Alternate way to identify maintenance objects. Alt.

  • Page 385: Release Sp-Link

    release sp-link release pri-endpoint 22501 page 1 of 1 COMMAND RESULTS Port Maintenance Name Alt. Name Result Error Code 01B2001 PE-BCHL 22501 PASS 01B2002 PE-BCHL 22501 PASS 01B2003 PE-BCHL 22501 PASS 01B2004 PE-BCHL 22501 PASS 01B2005 PE-BCHL 22501 PASS 01B2006 PE-BCHL 22501 PASS...

  • Page 386: Release Station

    Maintenance Commands Field descriptions Port address (cabinet-carrier-slot-circuit) of busied out maintenance Port objects. The type of maintenance object that is being busied out. Maintenance Name Alternate way to identify maintenance objects. Alt. Name If the Object is The field contains station extension trunk...

  • Page 387: Release Tdm

    release tdm Alternate way to identify maintenance objects. This field contains Alt. Name an extension when the object is a station. Success status of a busied out object (PASS, ABORT, FAIL) Result System-generated description of a command failure. Error Code release tdm This command removes specified tdm buses from a maintenance busy state.

  • Page 388: Release Tone-Clock

    Maintenance Commands Field descriptions Port network number (preceded by “PN”) and bus (“A” or “B”) Port associated with the TDM bus. TDM-BUS Maintenance Name Not applicable Alt. Name Success status of a busied out object (PASS, ABORT, FAIL) Result System-generated description of a command failure. Error Code release tone-clock Use release tone-clock to remove tone/clocks from maintenance busy states.

  • Page 389: Release Trunk

    release trunk release trunk Use release trunk to remove specified trunk groups or trunk group members from a maintenance busy state. Specifying the group number releases a single group member and the member number. Specifying the trunk group number releases members in a trunk group.

  • Page 390: Remove File

    Maintenance Commands remove file remove file [path] board ppcss Use remove file to request the board (ppcss) to remove the file given by path. If the file does not exist on the source board’s filesystem, an error message appears. To remove a file in a subdirectory, specify the entire path starting at “/”. remove license Use remove license to erase a non-field License File from customer switches, translations, and memory.

  • Page 391: Reset Board

    reset board reset board Use reset board to perform a soft reset of every specified, administered port on the port circuit pack. Ports must be busied out before the port circuit pack resets. WARNING: This command is service disrupting and may cause extraneous alarms. Action/Object Qualifier Qualifier Description...

  • Page 392: Reset Io-Processor

    Maintenance Commands reset io-processor Use reset io-processor to reset and initialize the IO-Processor hardware and firmware. The IO-Processor supports the packet interface and Data Channel data scanners. The IO-Processor is simply reset. Failure of the reset can lead to the processor being placed in the out-of-service state.

  • Page 393: Reset Ip-Endpoints

    reset ip-endpoints reset ip-endpoints Use reset ip-endpoints to unregister IP 4600 series phones, IP Softphones, H.323 stations. Action/Object Qualifier Qualifier Description Logins Defaults Feature Interactions reset init none ip-endpoints inads craft reset login-session n Use reset login-session to terminate a SAT session on a TCP/IP link, or other traditional connection.

  • Page 394: Reset Switch-Control

    Maintenance Commands reset switch-control Use reset switch-control to reset and initialize the switch control hardware and firmware. Action/Object Qualifier Qualifier Description Logins Defaults Feature Interactions reset switch-control none none init none inads craft reset system Use reset system to reset the system beginning with the corresponding vector bit set, a core dump is written to memory card, only if the memory card is the special core dump card), the vector is cleared, and the requested restart is performed.

  • Page 395: Reset System 3

    reset system 3 reset system 3 This command requires an additional parameter if the reset level is 3. The reset system 3 command includes the periodic synchronization of translations in a ATM WAN spare processor (WSP). When you issue this command, indicate whether you want to preserve the license or not: reset system 3 preserve-license—the License File information is retained in memory and is NOT overwritten with the License File on the translation...

  • Page 396: Reset Translation-Id

    Use reset translation-id to reset the translation-ID on the translation card(s) to match the processor(s), saves translations to the memory card, and restore use of the add, change, remove, and duplicate commands. NOTE: This command can be executed only by Avaya Services. Action/Object Qualifier Qualifier Description...

  • Page 397: Restore Announcements

    restore announcements restore announcements Use restore announcements to copy announcement data from the active MSS devices to announcement boards. Feature Action/ Object Qualifier Qualifier Description Logins Defaults Interactions restore print Report sent to printer init Tape-based: see below announcements inads announcement schedule Use the screen to...
  • Page 398 Maintenance Commands To prepare for a failure, users should copy announcement files to announcement boards. If errors result from hardware or firmware failures, MSS software logs hardware errors with maintenance. When errors occur, the system continually attempts to download boards in 10-minute intervals until a download succeeds, announcements record, or downloads initiate from the SAT.

  • Page 399: Resume Hardware-Group

    resume hardware-group resume hardware-group Use resume hardware-group to resume the previous test hardware-group command its canceled position. Entering another test hardware-group disables the resume hardware-group command. A canceled test hardware-group command appears as canceled on the status hardware-group screen. A resumed test hardware-group command appears as active on the status hardware-group screen.
  • Page 400 Maintenance Commands Duplex If no options are specified, the system saves announcements to both processors’ MSS devices. Feature Action/Object Qualifier Qualifier Description Logins Defaults Interactions save spe-active forces the system to write init none see below announcements announcement data to inads specified devices in active craft...
  • Page 401 save announcements When MSS devices on both processors in High or Critical Reliability Systems are specified, the save announcements command saves announcement data from announcement boards to active MSS devices, then to standby MSS devices. The system reports the status of each save operation to users separately.

  • Page 402: Save Translation

    Maintenance Commands save translation Use save translation to save to tape or memory card the in-memory translation data. This command runs as part of scheduled maintenance and/or on demand by the technician. All translation data in memory during system operation is volatile, meaning that if the switch goes down, the system loses all data.

  • Page 403: Set Boot-Image

    set boot-image save translation SAVE TRANSLATION Processor Command Completion Status Error Code SPE-A Success SPE-B Success Field descriptions Identifies the processor carrier where translation data saves. Processor SPE-A/SPE-B Displays a variety of messages, identifying the success or Command Completion Status failure of the command.

  • Page 404: Set Ethernet-Options

    Maintenance Commands set ethernet-options Use set ethernet-options to manually or automatically set the ethernet connection parameters. NOTE: The ethernet port must be administered and busied out before you can issue set ethernet-options. Action/Object Qualifier Qualifier Description Logins Defaults Feature Interactions set ethernet- location The physical location of...

  • Page 405: Set Options

    set options set options Use set options to enable a remote user with INADS permission to select which types of maintenance categories report alarms automatically and which types require customer call-in. Correct options settings can reduce the number of ineffective alarms to the TSC. For effective results, use the set options default settings specified in this section.
  • Page 406 Maintenance Commands set options Page 2 of 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...
  • Page 407 set options No: Alarms that raise on trunks, stations, or adjuncts in this category drop. Error information displays as before, but alarm is evident. LED is inactive and calls are not sent to INADS. Because resources are deactivated without any record, this option is recommended only when other options do not provide desired results.
  • Page 408 Maintenance Commands Default parameters are: The system downgrades all station, trunk (except on-board trunk alarms), and Minor DS1-BD alarms to warning alarms. On-board Major and Minor trunk alarms, and the Memory Card Capacity alarm continue to raise alarms and report to INADS. Station MOs Affected By set options NOTE: Although alarms on some MOs appear as warnings, they should be...
  • Page 409 set options Circuit Pack MOs affected by set options NOTE: Although alarms on some MOs appear as warnings, the alarms should be investigated with user-reported problems. NOTE: The alarm severity of group one downgrades trunks that are not members of Trunk Groups, (for example, PCOLs).
  • Page 410 Maintenance Commands PI-Link and associated Link MOs affected by set options Although alarms on some MOs appear as warnings, the alarms should be investigated with user-related problems. See Processor Interface Link [“PI-LINK (Processor Interface Link)”] for other associated Link Maintenance Objects. Memory Card MOs Affected by set options NOTE: While this option does not automatically downgrade CAP-MEM alarms,...

  • Page 411: Set Signaling-Group

    set signaling-group set signaling-group Use set signaling-group to upgrade secondary D-channel in specified signaling groups to primary D-channels. Current primary D-channel then revert to secondary D-channels. A signaling group is a collection of B-channels that designate single D-channels or a set of D-channels signals over an ISDN-PRI. Action/Object Qualifier Qualifier Description...

  • Page 412: Set Tdm

    Maintenance Commands set tdm Use set tdm to establish the TDM bus on a port network that houses control channels and dedicated tones. Feature Action/Object Qualifier Qualifier Description Logins Defaults Interactions set tdm port Port network number of the TDM init none See below...

  • Page 413: Set Time

    set time set time Use set time to change the day of the week, the day of the month, the month, year, hour, and minute. The second field resets to zero (0) whenever the time on the clock is altered, but cannot be modified by the technician. The day of the week, entered as a text string, translates to an integer for internal storage.

  • Page 414: Set Tone-Clock

    Maintenance Commands set tone-clock Use set tone-clock to set the active tone/clock for a PN that has a duplicated tone/clock circuit pack. Reset the default active tone clock in each PN after using set tone-clock. If it is not in use, a single failure can cause an unnecessary service outage.

  • Page 415: Status Access-Endpoint

    status access-endpoint The vector clears after all core dumps. Action/Object Qualifier Qualifier Description Logins Defaults Feature Interactions set vector vector value See Vector Condition init none none Mapping values below inads craft Vector-Condition Mapping Value Warm Cold II Cold I Reboot status access-endpoint Use status access-endpoint to display the status of an access endpoint and can...
  • Page 416 Maintenance Commands Output The following example shows the output for status access-endpoint 22502. The command assumes that access endpoint ports for extension 22502 are in cabinet 1, carrier C, slot 11, circuit 1 to 6 — that access endpoints are connected on an active call to ports 7 to 12 of the board in location 1B19 (cabinet 1, carrier B, slot 19).

  • Page 417: Status Administered-Connection

    status administered-connection status administered-connection Use status administered-connection to display the status of end-to-end connections between two access/data endpoints. Action/Object Qualifier Qualifier Description Logins Defaults Feature Interactions status Administered init none none administered- number connection number inads connection craft print Report sent to printer. cust rcust bcms...

  • Page 418: Status Attendant

    Maintenance Commands Number of consecutive failed establishment attempts. Number of Retries When an administered connection is connected, this field indicates if auto Auto Restorable restoration attempts when a failure occurs. status attendant Use status attendant to locate facilities to which the attendant console communicates.

  • Page 419: Status Audits

    status audits status audits Use status audits to display Data Relation Audits that are built into the switch. Data Relation Audits check for inconsistencies between selected data items in the switch, and report inconsistencies. Data Relation Audits are useful during development and testing phases of projects to uncover software errors.
  • Page 420 Maintenance Commands Action/ Feature Object Qualifier Qualifier Description Logins Defaults Interactions status peak-hour data collected since the last reboot or since init none see below audits the last execution of the clear audits inads cumulative command. cumulative Data for the peak hour since the last reboot or since the last execution of the clear audits cumulative or clear audits peak-hour command.
  • Page 421 status audits status audits peak-hour AUDIT STATUS INFORMATION Start Date: 10:00 MON MAR 22 1997 # of Audit Cycles Completed: Audit # Cycles # Cycles Could # Cycles Name Fixed Data Not Fix Data Audit Aborted HTLK HU-CALLS CR-AUDIT DE-CALLS CTRK AT-ADM CO-ADM...
  • Page 422 Maintenance Commands Number of times that the audit ran, in the specified interval, and # Cycles Fixed Data found a fixable problem. (0–65534) Asterisks are used for numbers that exceed 65534. Number of times that the audit ran, in the specified interval, and # Cycles Could Not Fix Data found an unfixable problem.
  • Page 423 status audits Table of audits Table 22 shows the names of the audits that are run as part of time available maintenance, the audit number (pname) and a short description of each audit. These audits execute using lname MO_DR_AUDIT (8192). These audits may execute using the test MO command with lname 8192, pname “audit number,”...
  • Page 424 Maintenance Commands Table 22. Time-available maintenance audits Audit Audit Name Number Description CALK Coverage answer member lock audit CATT Attendant connections audit CCTRTAB Call Classifier Tone Receiver Table Audit CCTR-SID Call classifier tone receiver audit Data module connections audit CO-ADM Coverage group administration audit CO-CALLS Coverage group calls audit...
  • Page 425 status audits Table 22. Time-available maintenance audits Audit Audit Name Number Description HU-ADM Hunt group administration audit HU-CALLS Hunt group calls audit HU-QUE Hunt group queue audit IAP-CALLS IAP call record audit IAP-URB IAP user record audit IM-HMM HMM image table audit INST-LNK Instigator/down-link user link audit ISGR-A...
  • Page 426 Maintenance Commands Table 22. Time-available maintenance audits Audit Audit Name Number Description PLIP-LNK LIP link audit PN-HMM HMM pname table audit PRI-CR PRI call record audit PRI-TBUF TSCUUI buffer audit PUR-A Phantom user record audit SDSBUF Service dispatcher stim buffer audit SDSID Service dispatcher SID audit SE-ADM...

  • Page 427: Status Bri-Port

    status bri-port Table 22. Time-available maintenance audits Audit Audit Name Number Description UGMA User group membership audit UPUSR-LNK Up-link user link record audit URMB User record maintenance busy audit X25-CHAN X.25 Channel Status Audit X25-LINK X.25 Link Status Audit Continued on next page The following table shows the names of audits that run as part of scheduled maintenance, the audit number (pname) and a short description of each audit.
  • Page 428 Maintenance Commands Output For the following example shows the output from status bri-port 1c1701. status bri-port 1c1701 Page 1 of 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?
  • Page 429 status bri-port Point-to-point signaling link layer 2 state. Layer2 State un-assigned = the link is in TEI-UNASSIGN state at Layer 2. assigned = the link is in the AWAIT_EST (Await Establish) state at layer 2. (If BRI endpoints support TEI allocation procedures, they successfully execute and a TEI is assigned to the endpoint by the switch.
  • Page 430 Maintenance Commands Status bri-port interpretation Table 23 provides information on the status bri-port form. Table 23. Status BRI-Port Command Interpretation Endpoint Layer 2 Voice Service Types Range State Extension SPID Description / Recommendation ASAI, 0-126 Assigned blank blank Transitory state for BRI endpoints and ASAI adjuncts.
  • Page 431 status bri-port Table 23. Status BRI-Port Command Interpretation — Continued Endpoint Layer 2 Voice Service Types Range State Extension SPID Description / Recommendation 0-126 Established blank Normal state for non-MIM initializing, fixed and automatic TEIBRI endpoints. BRI, 64-126 Established blank blank Transitory state for automatic TEIBRI ASAI...
  • Page 432 Maintenance Commands Table 23. Status BRI-Port Command Interpretation — Continued Endpoint Layer 2 Voice Service Types Range State Extension SPID Description / Recommendation 0-126 L3-Assigned blank Transitory state for BRI endpoints (cont’d) which support MIM initialization. 2. Wait for five seconds and repeat the command.

  • Page 433: Status Card-Mem

    status card-mem Table 23. Status BRI-Port Command Interpretation — Continued Endpoint Layer 2 Voice Service Types Range State Extension SPID Description / Recommendation Signaling suspends. System timeouts in 60 seconds and attempts reactivate the link. If links remain in this state while no activity occurs at BRI endpoints: 1.
  • Page 434 Maintenance Commands Use status card-mem to display the following memory card information located at active or standby SPEs: Is a valid memory card in place? Is the memory card write-protected? NOTE: Beginning with Release 9, the memory card has no write protect switch and no equivalent software mechanism.
  • Page 435 status card-mem Output For following output is an example of status card-mem. status card-mem MEMORY CARD STATUS Location: 01A Write Protection: NA Status: inserted Capacity (MB): 8 ATA Card System Size: Medium Number of Erase Pulses: Card Format: post-G3V8 Translation Storage Space Used (%): 3 File Name Data Present Date...
  • Page 436 Maintenance Commands Field descriptions “inserted” = valid memory card is in the memory card slot. When Status the status is “inserted,” the switch can perform I/O operation to the memory card “no card” = no memory card is inserted or the inserted memory card has a bad connection “unformatted”...

  • Page 437: Status Cdr-Link

    status cdr-link status cdr-link status cdr-link [print] Use status cdr-link to display 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).

  • Page 438: Status Cleared-Alarm-Notif

    Maintenance Commands status cleared-alarm-notif Expert Systems use status cleared-alarm-notif to detect chronic alarming conditions. If status cleared-alarm-notif displays Feature is suspended, Expert Systems can identify open trouble tickets as chronic problems for special consideration. Action/Object Qualifier Qualifier Description Logins Defaults Feature Interactions cleared-alarm First OSS telephone...
  • Page 439 status conference Output Screen 63. status conference: page 1 of 2 It is possible for several records to display. Active conferences display first (in order of conference-ID), followed by completed conferences (most recently completed first). Conferences that have not begun have no data or information. Conference data displays in 2 parts: the first screen describes the status of the conference and indicates the modes and levels of the conference.
  • Page 440 Maintenance Commands Field descriptions (status conference, page 1) Current status of the conference (active, in-use, complete) status conference (MMCH DYNAMIC) name (Voice-activated) conference mode Not Applicable password Not Applicable password scope Conference cascade mode (blank) cascade mode Current operating audio mode (G.711-A, G.711-mu, G.728. G.722) audio mode Conference type (dedicated) class...
  • Page 441 status conference The video format for single-screen conferences: CIF, QCIF, Format (in/out) QCIF/CIF, H.CTS, H.CTX+, and SG4. non-H.261 conferences = input and output formats are always symmetric and the mode is the same for input and output. (H.CTX, H.CTX+, and SG4). H.261 mode non-continuous presence conferences = symmetric format (CIF and QCIF).
  • Page 442 Maintenance Commands The Meet-Me Number administered for the Meet-Me Extension. Meet-me number in = dial-in to join endpoint to conference. Dial Type out = dial-out to join endpoint to conference. y = the endpoint is in use and is fully-connected on all media in an In Use active conference.
  • Page 443 status conference y = the endpoint has the required audio capability. Audio add-on endpoints always set the Aud field to y when the endpoint joins the conference. c = the endpoint is PCM only and it changes the conference video quality by changing the operating audio from G.728 to G.711.
  • Page 444 Maintenance Commands Rate adaptation/Interworking indicator (5, 6, y, c, e, n, blank). 5 and Rate Adpt “6” apply to Low Speed/High Speed Interworking. All other values apply to Rate Adaptation. 5 = 56-kbps (Low Speed) endpoint joins a High Speed (128 kbps or above) conference.
  • Page 445 status conference MCU endpoint video state (a, b, B, c, i, r, R, s, S, u, U, v, blank). Quad-screen conferences = an * appears before the Vs value indicating that an endpoint belongs to the mixed image. # appears before Vs values indicating that an endpoint is set to be in the mixed image (via administration or UCC/CRCS Agent), but instead, Fill video displays in its place.
  • Page 446 Maintenance Commands S = UCC/CRCS Agent interface suppresses this endpoint’s video. For (cont’d) continuous presence conference with fixed quadrant participants, #S represents endpoints that are fixed in a particular quadrant S displays when both the endpoint and the UCC/CRCS Agent suppress the endpoint video.
  • Page 447 status conference Field descriptions (status conference, page 2) The VD audio Level 1 (L1) and Level 2 (L2) summer group parts for each Sum Grp 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”...
  • Page 448 Maintenance Commands Drop Reason Endpoint Clearing received from DS1. The endpoint causes the (cont’d) disconnect. The endpoint notifies the MCU that it intends to disconnect. Far-end Clearing received from DS1. The network or endpoint cause the disconnect. “Handshake” = Framing is not located or is lost for over 40 seconds and the endpoint disconnects.
  • Page 449 1 port slot positions display allocated Call Classifier resources. Expansion Service Module MMI data port. This field defaults to blank. Ports ESM Endpoint’s assigned summer group number. The summer group port Sum Grp assignments are on screen 1. For Avaya use only. software 555-233-119 Issue 5 October 2002...
  • Page 450 Maintenance Commands Field descriptions (status conference endpoint) The status conference x endpoint y command specifies that the conference is found. Data relevant for each endpoint displays in 6 pages. If technicians use the endpoint-ID all, every specified endpoint displays. Page 1 - Status Conference Endpoint status conference endpoint page 1 of 6 STATUS OF CONFERENCE ___...
  • Page 451 status conference Is the endpoint participating in the conference or connecting to the In Use conference? - y, c, e, f, n, blank. y = The endpoint is in use and fully-connected on all media in an active conference. c = The endpoint is in use and fully-connected; however, the endpoint changes the conference audio or video capability, or the rate of the conference due to rate adaptation.
  • Page 452 Maintenance Commands Does it have the required audio capability? - y, c, e, blank y = The endpoint has the required audio capability. Audio add-on endpoints set the Aud field y when the endpoint joins the conference. c = This PCM-only endpoint changes conference video quality by changing the operating audio from G.728 to G.711.
  • Page 453 status conference Rate adaptation/Interworking indicator = 5, 6, y, c, e, n, blank. 5 Rate Adpt and 6 apply to Low Speed/High Speed Interworking. All other values apply to Rate Adaptation. 5 = 56-kbps (Low Speed) endpoints join High Speed (128 kbps or above) conferences.
  • Page 454 Maintenance Commands The MCU video state for this endpoint. a, b, B, c, i, r, R, s, S, u, U, v, blank. Quad-screen conferences = * appears before V values indicating that an endpoint belongs to the mixed image. A # appears before the V values indicating that an endpoint belongs to the mixed image (by administration or UCC/CRCS Agent).
  • Page 455 status conference i = The endpoint is not a valid video source. For continuous presence (cont’d.) conference, #i represents endpoints that are is fixed in a particular quadrant. r = For full-screen conferences, t he endpoint’s video is the return video to the broadcaster.
  • Page 456 Maintenance Commands Page 2 - Endpoint Channel Information This section describes fields specific to endpoint-level command output. status conference endpoint page 2 of 6 ENDPOINT CHANNEL INFORMATION Chan. Join Drop ----Drop---- ------------Ports---------- Time Time Reason Code Num Trunk Video Aud/ESM BONDng Err Software _____ _____ _________ __ ___ ______ ______ ______ ______...
  • Page 457 status conference Channels disconnect because: Drop Reason “2-pri” = Administration errors cause mismatches in primary- secondary designations for cascade links. This mismatch indicates that both MCUs are administered as primaries (see “Cascading” for a description of primary-secondary compatibility). “2-sec” = Administration errors cause mismatches in primary- secondary designations for cascade links.
  • Page 458 Maintenance Commands Drop “Endpoint” = Clearing received from DS1. The endpoint initiates the Reason disconnect. The endpoint notifies the MCU that it intends to disconnect. (cont’d) “Far-end” = Clearing received from DS1. The network or endpoint initiate the disconnect. “Handshake” = Framing is never found or is lost for over 40 seconds and the endpoint is disconnected.
  • Page 459 status conference Drop “Pre-AnsDrop” = The call disconnects an endpoint answers. The network, Reason an endpoint, or a terminal adapter may cause the disconnect. This drop (cont’d) reason differs from ‘No-answer,’ which indicates that a 60-second timeout occurs during alerting. In this case, the call drops before the 60-second timer expires.
  • Page 460 Maintenance Commands Page 3 - Conference Information This section describes fields that are specific to endpoint-level command output. status conference endpoint page 3 of 6 CONFERENCE INFO: Broadcaster: xx (See-Me) Return Vid: xx ---------- MODE COMMANDS/COMMUNICATION MODES ------| EPT MISC | ------- FAW -- STAT CONF...
  • Page 461 status conference The endpoint number that is the current return video. The return video Return Vid is qualified with the following keywords: “blank” = VAS, Chair action, UCC action, or endpoint MCV requests force the previous broadcaster to be the return video. The broadcaster qualifier identifies the action that forced this endpoint to become return video.
  • Page 462 Maintenance Commands The following are field definitions for the Mode Commands/Communication Modes section of Page 3. One of the supported rates in Table XRATE Table 24. Supported Transfer Rates s XRATE Bandwidth of the Call 2x64 2B (2x56 or 2x64) 112kbps or 128kbps 168kbps or 196kbps 224kbps or 256kbps...
  • Page 463 status conference Table 25. Audio Mode Configurations Admin Mode Support Xfer Facility (HC Audio) HC Audio Rate Conf Mode Expected Endpoint Mode auto (G.728) <=128k G.728 G.728 auto (G.728) <=128k G.711-A-56k G.711-A-56k B.711-Mu-56k auto (G.728) <=128k G.711-A-48k G.711-A-48k G.711-MU-48k auto (G.722) >128k G.722-56k G.722-56k G.711-A-56k G.711-Mu-56k...
  • Page 464 Maintenance Commands The High Speed MLP mode. The HMLP mode should be H_MLP H-MLP-off. Other values in this mode will affect video status. Low Speed Data mode. The LSD mode should be LSD-off. Other values in this mode affect video status. High Speed Data mode.
  • Page 465 status conference Multipoint Command Visualize. y = For input, an endpoint requests to become a broadcaster. This is used during Still Frame Graphics and to force “presentation” mode. y = The VC board detects voice energy from the endpoint. The TALK counter TALK indicates the number of starts or stops.
  • Page 466 Maintenance Commands Frame Alignment Word (FAW) Information. The FAW section of page 3 provides 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.
  • Page 467 status conference Page 4 - Endpoint Capability Information This section describes fields specific to endpoint-level command output. status conference endpoint page 4 of 6 ENDPOINT CAPABILITY INFORMATION -------------------------------------------------------------------------------- VID | vfmt: QCIF cmpi: 30 H.CTX | da_sfg qmpi: 7.5 H.CTX+ SG4_sfg -----|-------------------------------------------------------------------------- MISC | derestrict...
  • Page 468 Maintenance Commands Field descriptions Video and frame rate types that the endpoint supports. “vfmt” = Does not display if the endpoint has no video capability. All values are blank if an active call or audio-only endpoint exists. Otherwise, values for this field include: FCIF for full CIF QCIF for quarter CIF.
  • Page 469 status conference Transfer rate capabilities. Endpoint speeds over current connections and Px64 Multiplexes. For 384 kbps (H0) calls, endpoints indicate 384 kbps support, that displays as 384. On 336 kbps calls, endpoints 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).
  • Page 470 Maintenance Commands Page 5 - Endpoint Call Status Information This page summarizes call-related status for per-channel join counts, join/drop times, drop reasons, drop codes, and auxiliary bonding drop codes. In addition, it contains drop codes and software fields from the previous call. The data on the page is retained.
  • Page 471 status conference Page 6 - Administered Connections This page summarizes information for administered connections associated with this endpoint. This data can be viewed while the conference is active. status conference endpoint page 6 of 6 ADMINISTERED CONNECTIONS INFORMATION Retry Failure Chan Num Dial-out Number Connection State...
  • Page 472 Maintenance Commands Field descriptions Numbers that are dialed out by administered connections for each Dial-out number channel in the call. 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.
  • Page 473 status conference Table 26. Status AC - Failure Cause Values Failure Cause (hexadecimal) Description 0x00 (0t0) 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...

  • Page 474: Status Data-Module

    Maintenance Commands Table 26. Status AC - Failure Cause Values — Continued Failure Cause (hexadecimal) Description 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)
  • Page 475 status data-module Field descriptions The data module extension number. The DTDM is an exception: Data Ext/Sta Ext for Stn DM the connected station extension is shown. The port location of the data module (cabinet-carrier-slot-circuit). If Port/Channel Number the data module specified is a data channel, the channel number will be shown instead.

  • Page 476: Status Esm

    Maintenance Commands status esm Use status esm to display the link status and equipment and software revision identifiers for the Expansion Service Module (ESM). Action/Object Qualifier Qualifier Description Logins Defaults Feature Interactions status esm init none none inads craft Output The following example shows the output of status esm.

  • Page 477: Status Firmware Download

    status firmware download status firmware download status firmware download <last> Use status firmware download to display the download status for each board. The qualifier <last> displays the last download schedule. This command displays a blank download schedule if there is no active download schedule or there was no previous schedule for the last qualifier to invoke.

  • Page 478: Status Hardware-Group

    Maintenance Commands status hardware-group Use status hardware-group to display summary information for the active or last hardware group test. The information includes the number and percentage of tested maintenance objects, the percentage of tests passed, failed, and aborted, the time elapsed since initiating the hardware group test, the specific hardware group test command (see ‘‘test hardware-group’’) initiated, and the state...
  • Page 479 status hardware-group Field descriptions “active” = testing in progress, “canceled” = testing canceled, Hardware Group Command State: “complete” = command completed; no testing occurring. Number of MOs in the specified group (refer to test Number of MOs Tested: hardware-group command) that the hardware-group command tests, including MOs that were tested or aborted due to resource contention.

  • Page 480: Status Health

    Maintenance Commands status health Use status health to display the current system alarm summary, maintenance busy summary, user summary, critical system status, and cabinet status. The same page appears with monitor health, except that the status health page does not update periodically. Action/Object Qualifier Qualifier Description...
  • Page 481 status health Combined number of maintenance busied out objects excluding trunks Others and stations. Proportion of the CPU that is dedicated to high priority items (for Static example, the operating system). This percentage is rounded to the nearest integer, therefore a percentage of 0 means that the occupancy is less than one half of a percent.
  • Page 482 Maintenance Commands Settings for emergency transfer switches on the maintenance board for Emerg Trans each cabinet. Available options are: auto-on (“auto+” or “a+”), auto-off (“auto-” or “a-”), “on”, “off”, and “n.a.”. The system defaults to “auto+” or “auto-”. In this state, emergency transfer activate automatically if the cabinet fails (“+”=emergency transfer is activate, “-”...

  • Page 483: Status Interface

    status interface status interface Use status interface to display the number of counters maintained by the PI (a front end processor implementing packet layers and link layers of the BX.25 protocol and the ISDN procedure-D protocols). Feature Action/Object Qualifier Qualifier Description Logins Default Interactions...
  • Page 484 Maintenance Commands Table 27. status c-lan-ip CCcss Field Name on switch output output type MIB data Description Incoming Counter Long ipInHdrErrors The number of input datagrams datagram discarded due to errors in their IP header errors headers, including bad checksums, version number mismatch, other format errors, time-to-live exceeded, errors discovered in processing their IP...
  • Page 485 status ip-board Table 27. status c-lan-ip CCcss Field Name on switch output output type MIB data Description Outgoing Counter Long ipOutRequests The total number of IP datagrams datagrams which local IP user-protocols submitted for (including ICMP) supplied to IP in transmission requests for transmission.

  • Page 486: Status Ip-Network-Region

    Maintenance Commands status ip-network-region status ip-network-region The status ip-network-region x (where x is between 1 to 250 for r and 80 for si/csi/d) provides the status of the administered inter-network region connection management based on the background maintenance ping test. If the background maintenance test concluded a failed connectivity between two regions x and y, then the matrix for status ip-network-region x, or status ip-network-region y will indicate the result as f (failed) between those two regions.

  • Page 487: Status Isdn-Testcall

    status isdn-testcall status isdn-testcall This command displays the progress of an outgoing ISDN-PRI test call. The status screen shows 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.
  • Page 488 Maintenance Commands Field descriptions (cabinet/carrier/slot/circuit) of the ISDN-PRI B-channel. Port The measured bit error count based on the comparison between sent Bit Error Rate and received bit patterns. (Number displays in scientific notation) Number of bits generated. (Number displays in scientific notation) Number of Bits The measured block error count based on the comparison between Block error Rate...

  • Page 489: Status Journal-Link

    status journal-link status journal-link Use status journal-link to display if the link is up or down. If the link is down, the system displays the number of times the switch tries to initialize the link. A journal printer documents automatic wake-up events, emergency access to attendant events, and housekeeping events when the property management system is not functional.

  • Page 490: Status Link N

    Maintenance Commands status link n (csi, si, r models with C-LAN circuit pack - Ethernet connection) Use status link to displays: static information about the link the data extension and port used, connect speed, and protocol information a counter of CHAP failures for PPP links time information for PPP and Ethernet links (includes the time of the last reset, the last hour start time, and end time for the error counter statistics).
  • Page 491 status link n Field descriptions (page 1) Administered link number Link Number (assigned by add/change data-module command) Displays no, yes, unavail, connected, disconnected, enabled, Link Status out-of-service, or restarting The type of interface according to the physical/link protocol(s) Link Type immediately “below”...
  • Page 492 Maintenance Commands Field descriptions, status link page 2 The number of subnetwork-unicast packets delivered to a Incoming received higher-layer protocol. Unchaste packets The number of non-unicast (subnetwork-broadcast or Incoming received subnetwork-multicast) packets delivered to a higher-layer protocol. multicast packets The total number of octets received on the interface, including Incoming dropped octets framing characters.
  • Page 493 status link n Status link page 3, Processor Channel Status The example below is for page 3 of status link, Processor Channel Status. Information about administered hop channels appears on another page. The processor or hop channel status information can appear on 1 or 2 pages, depending on the number of links being reported and their condition.

  • Page 494: Status Logins

    Maintenance Commands status link 1 Page TCP/IP Applications Currently Active Service Type Sessions ALARM1 ALARM2 CDR1 CDR2 DOLAN PMS_JRNL PMS_LOG SYS_PRNT status logins status logins [print] Use status logins to display information about all of the users that are currently logged into the system.

  • Page 495: Status Packet-Interface

    status packet-interface status packet-interface Use status packet-interface to display the status of the packet-interface portion of the TN2402/TN798 processor circuit pack along with link information. Link status information including total, active, and failed links also appears. When the packet-interface is out-of-service or uninstalled, it is not used to establish and maintain links;...

  • Page 496: Status Pms-Link

    Maintenance Commands status pms-link Use status pms-link to display the status of the property management system interface link. If the link displays even when a data base swap occurs between the switch and PMS. If the link is down, the display indicates the number of times the switch tried to set up the link.

  • Page 497: Status Pri-Endpoint

    status pri-endpoint status pri-endpoint Use status pri-endpoint to display internal software state information for diagnosis, and to help locate facilities with which a PRI endpoint is communicating. Status information for each of the B-channels making up the PRI endpoint display in addition to some overall PRI endpoint information. Action/Object Qualifier Qualifier Description...
  • Page 498 Maintenance Commands Note that the line listing of each B-channel’s status may continue onto the next page. The user is prompted to press the key to continue the display. NxtPg Field descriptions PRI endpoint extension Extension Administered number of B-channels associated with the specified Width PRI endpoint ID number of the signaling group that handles the signaling for the...

  • Page 499: Status Processor-Channel

    status processor-channel status processor-channel Use status processor-channel to display the status of the specified processor channel and the values of its various counters. A processor channel is 1 of 64 logical channels associated with an SCI link. Each processor channel terminates in the switch processing element with a session.

  • Page 500: Status Psa

    Maintenance Commands State the channel is in: Channel Status 1. Channel is not administered. 2. Channel is administered but not used. 3. Channel is in a state entering “wait session accept” (WSA). 4. Channel is in a state waiting for a “session accept” message from the far end.
  • Page 501 status signaling-group Output The following output example shows the output from status signaling-group 1. status signaling-group 1 Page 1 of 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:...
  • Page 502 Maintenance Commands State of the primary or secondary D-channels: Level 3 State in-service: the D-channel is in the multiple-frame-established state at layer 2 carrying normal call-control signaling at layer 3. standby: the D-channel is in the multiple-frame-established state at layer 2, and not carrying any layer 3 call-control messages on logical link 0,0.

  • Page 503: Status Sp-Link

    status sp-link status sp-link Use status sp-link to display a page of output summarizing the operational status of the system printer link: its link state, number of retries, and whether the link is maintenance busy. Action/Object Qualifier Qualifier Description Logins Defaults Feature Interactions status sp-link...

  • Page 504: Status Station

    Maintenance Commands status station Use status station to display the internal software state information for diagnosis and to help locate the facilities to which the station is communicating. Feature Action/Object Qualifier Qualifier Description Logins Default Interactions status station extension Station extension (per dial-plan) init none none...
  • Page 505 status station y/n: Whether the station has a call parked. Call Park y/n: Whether ring cut off is activated. Ring Cut Off Activated Call forwarding destination extension, if any. Destination Whether there is a message waiting for the station. AP-SPE, Message Waiting AUDIX, PMS or blank if no messages are waiting.
  • Page 506 Maintenance Commands Page 2 displays the part ID of the station, if available. status station 1002 Page 2 of x GENERAL STATUS CONNECTED STATION INFORMATION Part ID Number: 108576694 Serial Number: 01SP29123456 Station Lock Active? no Field descriptions Shows the Part ID Number (comcode) of the telephone. If this field Part ID Number shows Unavailable, then the software was unable to determine the Part ID Number.
  • Page 507 status station status station Page 3 of X CALL CONTROL SIGNALING Switch Port Switch-end IP Addr: Port Set-end IP Addr:Port IP Signaling: H.245: Node Name: AUDIO CHANNEL Switch Port Other-end IP Addr: Port Set-end IP Addr:Port Audio: Node Name: Audio Connection Type: ip-tdm Product ID: IP_Phone H.245 Tunneled in Q.931? does not apply Registration Status: registered-authenticated...
  • Page 508 If you issue status station for a non-IP station or the connection is hairpinned or shuffled, then the packet loss and jitter size information (page 4) does not appear. See also “Shuffling, Hairpinning, Codec and Inter-Network Management Features” in Avaya MultiVantage Administration for Network Connectivity. status station 78020...

  • Page 509: Status Synchronization

    status synchronization Worst Case this Call Jitter: the worst-case, 1-second jitter buffer size (ms) experienced during the current connection Packet Loss: the worst-case, 1-second packet loss experienced during the current connection. Average this Call Jitter: the average jitter buffer size (ms) for the current connection (the running average of all the one-second intervals during the connection) Packet Loss: the average packet loss number for the current...
  • Page 510 Maintenance Commands Output The following example shows the output for status synchronization. status synchronization SYNCHRONIZATION STATUS Stratum Level:4 Maintenance Name: TONE-BD Physical Location: 01A Switching Capability: Enabled Excessive Reference Switching: No Field descriptions Synchronization stratum level: 3/4 Stratum Level TONE-BD, DS1-BD, STRAT-3 Maintenance Name Board location of the selected DS1 or tone-clock circuit pack Physical...

  • Page 511: Status Sys-Link

    status sys-link status sys-link Use status sys-link to display 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.
  • Page 512 Maintenance Commands Field descriptions Port location (cabinet-carrier-slot-circuit) Location Type of system-link: PRI (ISDN-PRI signaling link) Type/Chan Highest alarm level currently logged against the components Alarms making up the link. Operational status of the current path: Current Path none: link is down. present: current path displayed is valid.

  • Page 513: Status System

    status system status system Use status system to display the status, mode, and operational attributes of the SPE(s), TDM and Packet busses, tone-clock circuit pack(s), and emergency transfer switch of single or all cabinets in the system. CAUTION: The purpose of this command is to provide general information about the cabinet status.
  • Page 514 Maintenance Commands SPE modes are different for simplex systems than for duplicated MODE systems. See SPE Modes section that follows. SPE select switch position: SELECT SWITCH auto: the switch is in the middle position and automatically switches SPE depending upon conditions blank = the 1A SPE in a simplex system.
  • Page 515 status system Whether the dedicated tones are on this TDM Bus: y/n DEDICATED TONES Packet Bus identifier (1). See Packet Bus Maintenance descriptions for more information. The operational state of the Packet Buses: SERVICE STATE in: Packet Bus in-service and operating normally. out: Packet Bus failed certain maintenance tests and has been removed from service.
  • Page 516 Maintenance Commands Emergency Transfer Switch position on the Processor(s) or the SELECT SWITCH EPN maintenance circuit pack and the state of Emergency Transfer in the cabinet display: on: Designated analog phones in this cabinet are cut through to CO trunk lines only in an emergency situation. off: Emergency Transfer is off and cannot be invoked.

  • Page 517: Status Trunk

    status trunk SPE busied out and busyout spe-standby was executed at a busyout/ time when the standby memory was not refreshed. The not-refreshed standby SPE is not able to perform any maintenance or SAT-requested activities until a successful refresh spe-standby is executed. SPE busied out, and the switch software on this SPE has been busyout/ restarted and is executing list configuration.
  • Page 518 Maintenance Commands Examples status trunk 78 status trunk 80/2 print Output Group and member numbers of specified trunks. Trunk Group/Member The location of the port associated with the trunk. Port For ISDN trunks, the number of the signaling group to which the trunk Signaling group belongs.
  • Page 519 status trunk The following example shows the output for status trunk 20/1. 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: The following example shows the output for status trunk 1/19. status trunk 1/19 SPE B TRUNK STATUS...
  • Page 520 Maintenance Commands For an ip-TDM call, the audio switch port field shows one of ports 1-8 on a TN2302 Prowler board. status trunk 1/19 SPE B TRUNK STATUS Trunk Group/Member: 01/19 Service State: in-service/active Port: T00123 Maintenance Busy? no Signaling Group ID: 1 CA-TSC state: not allowed MM Conference ID: 8 MM Endpoint ID: 2...

  • Page 521: Status Tsc-Administered

    status tsc-administered The following example shows the output for status trunk 1 for a trunk group with two members. status trunk 1 TRUNK GROUP STATUS Member Port Service State Mtce Busy Connectd Ports 01/01 01A0101 in-service/idle 01A0501 02B0607 01/02 04A0702 in-service/idle 04C0604 status tsc-administered...

  • Page 522: Status Tti

    Maintenance Commands Field descriptions 1-64: the administered TSC index. TSC Index State of the administered TSC: TSC State inactive: the administered TSC is not functioning (for example, D-channel out-of-service, or disabled) active: indicates that the administered TSC is up and user information can be exchanged end-to-end.
  • Page 523 status tti Output The following example shows the output for status tti and status psa. status tti Page 1 of 1 status psa TTI/PSA STATUS TTI Background Task State: generating tti ports TTI State: voice # of Boards Completed: # of Boards Left to Process: Percent Complete: Elapsed Time since Task Started: 0:15...

  • Page 524: Status Val-Ip

    Maintenance Commands status val-ip Use status val-ip to generate an IP-related status report about the VAL circuit pack’s LAN connection. See status c-lan-ip for field descriptions. Action/Object Qualifier Qualifier Description Logins Defaults Feature Interactions status val-ip Output The following example shows the output for status val-ip. status val-ip 1C02 IP STATUS Reset Time: mm/dd/hh:mm...

  • Page 525: Test Access-Endpoint

    test access-endpoint test access-endpoint Use test access-endpoint to perform hardware diagnostic tests on all port circuits that are associated with the specified access endpoint extension. Action/ Feature Object Qualifier Qualifier Description Logins Defaults Interactions test extension Access endpoint extension (# of digits init Test none...

  • Page 526: Test Alarms

    Maintenance Commands Output The following example shows the output for test access-endpoint 22502, with the access endpoint ports for extension 22502 in cabinet 1, carrier C, slot 11, circuit 1 to 6. The responses are displayed on a port-by-port and test-by-test basis with one line of data for each test result.
  • Page 527 test alarms 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 log for a single object, test alarms tests each physical object only once. Action/ Feature Object...
  • Page 528 Maintenance Commands 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.
  • Page 529 test alarms Test alarm from the specified time specified (mm/dd/hh/mm). If no From from date is entered, then no checking is done and the alarms active since a month prior to the current time are reported. Test alarms associated with records to the specified time specified (mm/dd/hh/mm).
  • Page 530 Maintenance Commands test alarms Page ALARM ENTRY Port Maintenance On Alarm Ack? Date Alarm Name Brd? Name Type State Alarmed Count 01C03 UDS1-BD WARNING 03/06/16:48 1/4 TEST RESULTS Port Maintenance Name Alt. Name Test No. Result Error Code 01C03 UDS1-BD NO BOARD 01C03 UDS1-BD...
  • Page 531 test alarms Test results section Port address (cabinet-carrier-slot-circuit) Port The name of maintenance object Maintenance Name Alternate way to identify maintenance objects. Alt. Name If the Object is The field contains station extension trunk xxx/yyy (xxx=trunk group, yyy=member number) private CO line P/xxx (xxx = private CO line group number) The test being executed Test No Test result: Fail, Pass, Abort, or No Board.

  • Page 532: Test Analog-Testcall

    Maintenance Commands test analog-testcall Use test analog-testcall to run facility diagnostic tests on: an entire trunk group an individual trunk group member an individual trunk port all trunks on a board The type of test call, the far-end test line number, and other parameters are administered on the trunk group screen before executing the command.

  • Page 533: Feature Interactions

    test analog-testcall Action/ Feature Object Qualifier Qualifier Description Logins Defaults Interactions Examples: test analog-testcall trunk 78 f test analog-testcall trunk 78 f schedule test analog-testcall trunk 80/1 s r 2 test analog-testcall trunk 80/1 s r 2 schedule test analog-testcall trunk 78/2 no-selftest r 10 test analog-testcall trunk 78/2 no-selftest r 10 schedule...

  • Page 534: Test Board

    Maintenance Commands Field descriptions The port address (cabinet-carrier-slot-circuit) of the maintenance Port object that is being tested. The type of maintenance object that is being tested. Maintenance Name Alternate way to identify maintenance objects. Alt. Name If the Object isThe field contains trunkxxx/yyy (where xxx = trunk group number and yyy = member number) The test being executed...
  • Page 535 test board Action/ Feature Object Qualifier Qualifier Description Logins Defaults Interactions test board location Physical location of the board PCSS init Test none inads sequence Option for a brief series of craft = short; short nondestructive diagnostic tests. repeat = 1 Option for a longer, more long comprehensive test series (includes a...
  • Page 536 Maintenance Commands Output The following example shows the output from test board 1c07 short. The responses appear on a test-by-test basis with one line of data for each test result. test board 01C07 short TEST RESULTS Port Maintenance Name Alt. Name Test No. Result Error Code 01C07 ANL-BD...

  • Page 537: Test Card-Mem

    test card-mem test card-mem Use test card-mem to run a sequence of tests on the memory card in the specified switch processor element. The test sequences in order for both long and short options are listed in the following table: Test Short Long...
  • Page 538 Maintenance Commands Feature Action/Object Qualifier Qualifier Description Logins Defaults Interactions test card-mem location Carrier location where memory card init Test See below resides: High or Critical Reliability (a inads sequence or b) ; duplicated (a, A, b, or B) craft = short;...
  • Page 539 test card-mem Feature Interactions Use test card-mem long to run the Memory Card Erase/Write/Read Test. This means that save translation and save announcement are rejected while the write-to-memory-card operation is active. This test also invokes the Memory Card Capacity Test which determines whether the memory card is more than 98% full. This test is also invoked after the save translation command.

  • Page 540: Test Cdr-Link

    Maintenance Commands Field descriptions Port address (cabinet-carrier-slot-circuit): cabinet 1, carrier is A Port (control carrier A in a simplex system) and either A or B (control carriers A and B in a duplex system). The slot and circuit fields in the port address for the CAP-MEM, and CARD-MEM maintenance objects are always blank.
  • Page 541 test cdr-link Feature Action/Object Qualifier Qualifier Description Logins Defaults Interactions test cdr-link location Carrier location where memory card init Test resides: High or Critical Reliability (a inads sequence or b) ; duplicated (a, A, b, or B) craft = short short Option for a brief series of nondestructive diagnostic tests.

  • Page 542: Test Customer-Alarm

    Maintenance Commands test customer-alarm Use test customer-alarm to run hardware diagnostic tests on the leads of the Processor and EPN maintenance circuit packs, used for customer-provided alarms by closing the appropriate relay for 1 minute. Failure is verified by checking the customer alarm attached to the specified circuit pack. Feature Action/Object Qualifier...

  • Page 543: Field Definitions

    test customer-alarm Output The following example shows the output from test customer-alarm 02a. test customer-alarm 02A TEST RESULTS Port Maintenance Name Alt. Name Test No. Result Error Code CUST-ALM PASS Field Definitions The port address (cabinet-carrier-slot) Port The maintenance name (always CUST-ALM) Maintenance Name Not applicable...

  • Page 544: Test Data-Module

    Maintenance Commands test data-module Use test data-module to run hardware diagnostic tests on a data module or data channel. Test results are determined by the interface to the digital switch-data line port, digital line port, or network control data channel. Action/ Feature Object...

  • Page 545: Test Ds1-Loop

    test ds1-loop Output The following example shows the output from test data-module 300. The responses appear on a test-by-test basis with one line of data for each test result. test data-module 300 TEST RESULTS Port Maintenance Name Alt. Name Test No. Result Error Code 01C1103 PDMODULE...
  • Page 546 Maintenance Commands Action/ Feature Object Qualifier Qualifier Description Logins Defaults Interactions test location Physical location of board (PCSS) init ds1/csu-l See below ds1-loop inads oopback craft -tests superuser other cpe-loopback- Long-duration loopback test setup jack-test-begin through the Customer Premises Equipment (CPE) Loopback Jack. Allows user to specify a loop-up code for the CPE loopback jack if it differs from the default (0x47F).
  • Page 547 test ds1-loop Feature Interactions Loopback or span tests are not 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. Output The following example shows the output for the test ds1-loop 1c07 command, and assumes that the board in cabinet 1, carrier c, slot 7 is a TN767E DS1 board.

  • Page 548: Test Eda-External-Device-Alrm

    Maintenance Commands test eda-external-device-alrm Use test eda-external-device-alrm to run a hardware diagnostic test on all or specific port’s administered external device alarms. 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.

  • Page 549: Test Environment

    test environment Output The following example shows the output for test external-device-alarm all. The responses appear on a test-by-test basis with one line of data for each test result. test eda-external-device-alarm all TEST RESULTS Port Maintenance Name Alt. Name Test No. Result Error Code 01major EXT-DEV...
  • Page 550 Maintenance Commands 3. EXT-DEV tests external (AUDIX, for example) alarm status for both the SCC and MCC cabinet systems. 4. RING_GEN tests ringing voltage are tested in MCC cabinets only. NOTE: The processor carrier is not be recycled. All port carriers are recycled, and service is interrupted for each port carrier.
  • Page 551 test environment Feature Interactions The long test recycles power in some specified cabinet on non-SPE and maintenance board carriers and is destructive. Specifically, the “a” carrier of PPNs does not have power recycled. All port carriers are recycled, and service is interrupted for each port carrier.

  • Page 552: Test Failed Ip-Network-Region

    Maintenance Commands test failed ip-network-region Use test failed ip-network region to initiate a real-time ping test for failed network-regions connections. The default is ALL failed ip-network regions or “test failed ip-network-region xxx” (where xxx is in the range of 1-250 for R and 1-80 for si/csi/d).

  • Page 553: Test Hardware-Group

    test hardware-group When test firmware download is executed, the tests 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. test hardware-group Use test hardware-group to run a set of hardware diagnostic tests on the whole system, a carrier, cabinet, spe, or board.
  • Page 554 Maintenance Commands Action/ Feature Object Qualifier Qualifier Description Logins Defaults Interactions test system System-wide test of all hardware-groups init Test See below hardware- inads sequence Carrier address: cabinet (1), carrier (A) group = short; carrier Cabinet address (1) repeat = 1 location cabinet Board location: PCSS...
  • Page 555 test hardware-group Feature Interactions test Only test hardware-group can be active at any given time. hardware-group If test hardware-group all-ports is issued when the TTI background task is active, some unadministered ports may not be tested, and active alarms on line ports may be cleared. The status tti command can be used to determine the state of the TTI background task.
  • Page 556 Maintenance Commands Setting the Test Parameters Enter test hardware-group and the object (board, carrier, etc.). The following screen appears. 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:...
  • Page 557 test hardware-group Run the command in the background, thus freeing the SAT (n / y). The Background error results are tabulated in the error log, but no results appear on the terminal. This option cannot be used if either the continuously or the auto-page options are selected.
  • Page 558 Maintenance Commands Table 28. Test of ‘all ports’ option for the following boards: — Continued Board Board Number Description Number Description TN735 MET Line TN2149 Analog Line TN742 8 port Analog Line TN2180 16 port Analog line Continued on next page Allow for planned interchange of duplicated SPEs and SPE-interchange subsequent testing of both the active and standby SPEs.

  • Page 559: Test Inads-Link

    test inads-link Field descriptions Port address (cabinet-carrier-slot-circuit) Port The name of maintenance object Maintenance Name Alternate way to identify maintenance objects. Alt. Name If the Object isThe field contains stationextension trunkxxx/yyy (where xxx = trunk group number and yyy = member number) private CO lineP/xxx (where xxx = private CO line group number) The test being executed...
  • Page 560 Maintenance Commands Once the call is answered by INADS, the system sends a message with a test alarm type. INADS acknowledges receipt of the message and creates a trouble ticket. The trouble ticket is closed immediately and has a “INADS LINK TEST” message entered in the description field.

  • Page 561: Test Interface

    test interface test interface Use test interface to run hardware diagnostic tests on the processor interface circuit pack. The tests also examine the protocol and link interface that is transmitted over the board. Feature Action/Object Qualifier Qualifier Description Logins Defaults Interactions test interface location...
  • Page 562 Maintenance Commands Output The following example shows the output for test interface a1. The responses appear on a test-by-test basis with one line of data for each test result. test interface a1 TEST RESULTS Port Maintenance Name Alt. Name Test No. Result Error Code 01A1 PI-SCI...

  • Page 563: Test Isdn-Testcall

    test isdn-testcall test isdn-testcall Use test isdn-testcall to run an outgoing, asynchronous ISDN-PRI test call in the asynchronous method from a specified trunk. If the test results are PASS, the test call is started. A test result of ABORT means that a resource wasn’t available, for example, B-channel or a Maintenance/Test circuit pack.
  • Page 564 Maintenance Commands Output The following example shows the output for test isdn-testcall 77/1. The responses appear on a test-by-test basis with one line of data for each test result. test isdn-testcall 77/1 SPE A TEST RESULTS Port Maintenance Name Alt. Name Test No. Result Error Code 01B1501 ISDN-TRK...

  • Page 565: Test Journal-Printer

    test journal-printer test journal-printer Use test journal-printer to run hardware diagnostics on the link between the switch and one of the journal printer links. There are two types of journal printer links: pms-log and wakeup-log. For general information on journal printer links, ‘‘busyout pms-link’’.
  • Page 566 Maintenance Commands Feature Interactions The maintenance of a particular component on a link sometimes interferes with the maintenance of the link itself. Maintenance can put a link component in a busy state causing link set-up to fail. Frequent attempts at re-setup of a link may delay the recovery of a faulty component due to the maintenance test of a component only taking place when the component is idle.

  • Page 567: Test License

    test license test license Use test license to run a license file check on the server. Action/ Qualifier Feature Object Qualifier Description Logins Defaults Interactions test short Runs test 1484. init none None license inads long Runs test 19. craft Verifies serial dadmin numbers, including...

  • Page 568: Test Led

    Maintenance Commands test led Use test led to test all the LEDs in a specified cabinet. Once the cabinet is validated and the range of circuit packs determined, test led turns on all LEDs on the circuit packs contained in each carrier until all affected carriers are lit. Once all the LEDs are on, there is a 2-second pause, and all the LEDs are turned off in the same order.

  • Page 569: Test Memory

    test memory test memory Use test memory to run hardware diagnostic tests on any or all memory circuit packs in the specified carrier. Both short and the long test are nondestructive when testing memory. Action/ Feature Object Qualifier Qualifier Description Logins Defaults Interactions...
  • Page 570 Maintenance Commands Output The following example shows the output for test memory 1b. The responses appear on a test-by-test basis with one line of data for each test result. test memory 1b TEST RESULTS Port Maintenance Name Alt. Name Test No. Result Error Code MEM-BD PASS...

  • Page 571: Test Network-Control

    test network-control test network-control Use test network-control to run hardware diagnostic tests on a network control circuit pack. Action/ Feature Object Qualifier Qualifier Description Logins Defaults Interactions test location Network control board carrier location (a) init Cabinet 1, none network- inads carrier a, short...
  • Page 572 Maintenance Commands Output The following example shows the output from test network-control a. The responses appear on a test-by-test basis with one line of data for each test result. test network-control a TEST RESULTS Port Maintenance Name Alt. Name Test No. Result Error Code DATA-BD PASS...

  • Page 573: Test Pkt

    test pkt test pkt Use test pkt to run a series of tests on the Packet bus of a PPN. Action/ Feature Object Qualifier Qualifier Description Logins Defaults Interactions test pkt The Packet bus to be tested: nn (1) init Test none port-...
  • Page 574 Maintenance Commands Output The following example is the output for test pkt port-network 1. The responses appear on a test-by-test basis with one line of data for each test result. test pkt port-network 1 TEST RESULTS Port Maintenance Name Alt. Name Test No. Result Error Code PN 01 PKT-BUS...

  • Page 575: Test Packet-Interface

    test packet-interface test packet-interface Use test packet-interface to run hardware diagnostic tests on the packet interface circuit packs in a carrier. Tests performed include local memory checksum tests and checks of failure counters. Action/ Feature Object Qualifier Qualifier Description Logins Defaults Interactions test...

  • Page 576: Test Pms-Link

    Maintenance Commands test packet-interface 1a1 TEST RESULTS Port Maintenance Name Alt. Name Test No. Result Error Code PKT_INT PASS PKT_INT PASS test pms-link Use test pms-link to run property management system link tests on a pms link. It checks if the link is accessible, and the long test resets the link. For general information on PMS links, see ‘‘busyout pms-link’’.
  • Page 577 test pms-link Feature Interactions The maintenance of a particular component on a link may interfere with the maintenance of the link itself. Maintenance can put a link component in a busy state causing link set-up to fail. Frequent attempts at re-setup of a link may delay the recovery of a faulty component due to the maintenance test of a component only taking place when the component is idle.

  • Page 578: Test Port

    Maintenance Commands test port Use test port to run hardware diagnostic tests on an individual port circuit. In most cases, tests are performed on hardware connected to the port. Action/ Feature Object Qualifier Qualifier Description Logins Defaults Interactions test port location PCSSpp init...
  • Page 579 test port Output The following example is the output for test port. It shows that the port in cabinet 1, carrier c, slot 7, circuit 1 is an analog port. The responses appear on a test-by-test basis with one line of data for each test result. test port 01c0701 short TEST RESULTS Port...

  • Page 580: Test Pri-Endpoint

    Maintenance Commands test pri-endpoint Use test pri-endpoint to run hardware diagnostic tests on all port circuits (B-channels) that are associated with the specified PRI endpoint. Action/ Feature Object Qualifier Qualifier Description Logins Defaults Interactions test extension PRI endpoint extension to be tested init Test none...
  • Page 581 test pri-endpoint Output The following output example is for test pri-endpoint 22501 and assumes that the PRI endpoint ports for extension 22501 are in cabinet 1, carrier B, slot 20, circuits 1 to 3. The responses appear on a port-by-port and test-by-test basis with one line of data for each test result.

  • Page 582: Test Processor

    Maintenance Commands test processor Use test processor to run hardware diagnostic tests on a processor circuit pack. Action/ Feature Object Qualifier Qualifier Description Logins Defaults Interactions test location Cabinet number (a) init For SPE none processor inads simplex, the short Option for a brief series of craft location is...
  • Page 583 test processor Output The following output example is for test processor a. The responses appear on a test-by-test basis with one line of data for each test result. test processor a SPE B TEST RESULTS Port Maintenance Name Alt. Name Test No. Result Error Code PROCR PASS...

  • Page 584: Test Signaling-Group

    Maintenance Commands test signaling-group Use test signaling-group to validate that the signaling group is administered, and to run a series of diagnostic tests that return results and possible error codes. 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.
  • Page 585 test signaling-group Feature Interactions Additional data is available after running a test. See status signaling-group how to access the additional data. Output The following output example is for test signaling-group 1. The responses appear on a test-by-test basis with one line of data for each test result. test signaling-group 1 SPE A TEST RESULTS...

  • Page 586: Test Sp-Link

    Maintenance Commands test sp-link Use test sp-link to validate that the system printer link is administered, and to run a series of diagnostic tests that return results and possible error codes. The system printer link is a link from the switch to an external printer over which jobs can be printed.
  • Page 587 test sp-link Field descriptions Not applicable; always blank Port The name of the maintenance object Maintenance Name Alternate means of identifying the maintenance object. This field Alt. Name contains the extension when the object is a data module. Test being executed Test No Test result: Pass, Abort, Fail, No Board, Disabled, Extra Bd.

  • Page 588: Test Station

    Maintenance Commands test station Use test station to run hardware diagnostic tests on a port circuit assigned to the extension. The technician must specify the extension and a translation is automatically done to the physical port location. Action/ Feature Object Qualifier Qualifier Description Logins...
  • Page 589 test station Output The following screen is an example of the output from test station 81902 short, with the assumptions that port in cabinet 1, carrier c, slot 7, circuit 1 is an analog port and extension 81902 is connected to that port. The responses appear on a test-by-test basis with one line of data for each test result.

  • Page 590: Test Synchronization

    Maintenance Commands test synchronization Use test synchronization to update all the boards with the correct synchronization source and parameters. The system sends a downlink message to the tone clock and DS1 boards to place them in the correct synchronization configuration, providing error-free digital communication between the switch and other PBXs, COs, or customer premise equipment.
  • Page 591 test synchronization Output The following screen is an example of the output for test synchronization short. The responses are displayed on a test-by-test basis with one line of data for each test result. test synchronization short TEST RESULTS Port Maintenance Name Alt.

  • Page 592: Test Sys-Link

    Maintenance Commands test sys-link Use test sys-link to validate a link, and run diagnostic tests on the hardware objects that comprises the system link. If the current or faulted options are 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 is tested.
  • Page 593 test sys-link Output The following example shows the output from test sys-link 01A0516 current. test sys-link 01A0516 current Page SPE A TEST RESULTS Port Maintenance Name Alt. Name Test No. Result Error Code 01A0516 SYS-LINK PASS PKT-INT PASS PKT-INT PASS PN 01A TDM-BUS PASS...

  • Page 594: Test Tdm

    Maintenance Commands test tdm Use test tdm to test the time slots on a bus associated with a PPN or an EPN. Action/ Feature Object Qualifier Qualifier Description Logins Defaults Interactions test tdm pn number nn = number of the port network to have init Test none...
  • Page 595 test tdm Output The following example shows the output for test tdm port-network 1. The responses appear on a test-by-test basis with one line of data for each test result. test tdm port-network 1 TEST RESULTS Port Maintenance Name Alt. Name Test No. Result Error Code PN 01A TDM-BUS...

  • Page 596: Test Tone-Clock

    Maintenance Commands test tone-clock Use test tone-clock to run hardware diagnostic tests on a tone or clock circuit pack. Action/ Feature Object Qualifier Qualifier Description Logins Defaults Interactions test location PCSS init Test none tone-clock inads Sequence short Option for a brief series of craft = short;...
  • Page 597 test tone-clock Output The following is the output for test tone-clock 1a. The responses appear on a test-by-test basis with one line of data for each test result. test tone-clock 1a TEST RESULTS Port Maintenance Name Alt. Name Test No. Result Error Code TONE-BD PASS...

  • Page 598: Test Trunk

    Maintenance Commands test trunk Use test trunk to run hardware diagnostic tests on an entire trunk group or an individual trunk group member, depending on the options entered. Action/ Feature Object Qualifier Qualifier Description Logins Defaults Interactions test group Administered group number (1-99) init Test Seq.
  • Page 599 test trunk Output The following screen is an example of the output for test trunk 78. The responses appear on a test-by-test basis with one line of data for each test result. test trunk 78 TEST RESULTS Port Maintenance Name Alt.

  • Page 600: Test Tsc-Administered

    Maintenance Commands test tsc-administered Use test tsc-administered to submit a switched services request to run the Temporary Signaling Connection’s heartbeat test for all administered TSCs on a signaling group. Feature Action/Object Qualifier Qualifier Description Logins Defaults Interactions test signaling Signaling group number (1–8) init repeat = Additional...

  • Page 601: Traceroute

    (*), which indicates a timeout condition. The primary use of this command is to determine quickly and unambiguously if the fault lies within Avaya-provided equipment or if the fault is with the LAN or LAN administration to which the Avaya Definity Server CSI is connected.
  • Page 602 Maintenance Commands Action/ Feature Object Qualifier Qualifier Description Logins Defaults Interactions traceroute ip-address where IP address is init Primary None www.xxx.yyy.zzz inads craft node-name from node-name form customer board cabinet-carrier-slot address of the IP circuit pack clan-port port 1-17 Example: traceroute ip-address 123.4.56.789 board 1C14...

  • Page 603: Upgrade Software

    upgrade software Field descriptions Identifies the port on the CLAN board from which the traceroute clan-port command is issued. This field appears when the board is a CLAN. The node number (in sequence). The first node (0) is the address from which the traceroute command is issued.
  • Page 604 Maintenance Commands Feature Interactions System Restarts An upgrade causes a system restart: simplex systems perform a Level-4 restart, and duplex systems perform a Level-2 SPE-interchange after the standby is upgraded through a Level-4 restart. Initcauses Use display initcauses to see the software upgrade and the system reset level. Multi-User Contention When this command is executing, all other maintenance commands are blocked.
  • Page 605 upgrade software Disabled Objects All disabled objects retain their “disabled” status after a software upgrade according to the status recorded in the last save translation command. Output The following is the output from upgrade software and a successful simplex upgrade. INITIATING SOFTWARE UPGRADE MEM-CARD CHECKSUM PASSED...
  • Page 606 Maintenance Commands FLASH TEXT If the checksum fails, the software may or may not be CHECKSUM healthy, but it will try to run for as long as it can until further system reset through system technician intervention. REPLACE SOFTWARE The system technician is prompted by a beep and this text MEM-CARD WITH string on the Manager I to replace the software card-mem TRANSLATION...

  • Page 607: Maintenance Objects

    Maintenance Objects NOTE: This document is not intended to solve all troubles. When the limits of these procedures are reached and the problem is not resolved, escalate the problem to a higher level of technical support. Escalation must conform to the procedures in the Technical and Administration Plan.
  • Page 608 Maintenance Objects An Administered Connection provides an end-to-end connection between two access endpoints or data modules. This connection is automatically established when the administered connection is administered and is due to be active. An error is logged when an administered connection cannot be established or when an established administered connection fails.
  • Page 609 ADM-CONN (Administered Connection) Table 29. Administered Connection Error Log Entries — Continued Associated Alarm On/Off Test to Clear Error Type Aux Data Test Level Board Value 44 (a)(b)(c)(l) None None 50 (a)(b)(c)(d)(n) None None 52 (a)(b)(c)(d)(o) None None 54 (a)(b)(c)(o) None None 58 (a)(b)(c)(l)
  • Page 610 Maintenance Objects Notes: a. These errors have no specific test associated with them. Refer to Notes b through p for an explanation and appropriate action. b. These errors are valid only for administered connection established over ISDN facilities; only error 127 is valid for administered connection established over non-ISDN facilities (or between two endpoints on the same switch).
  • Page 611 ADM-CONN (Administered Connection) j. Indicate that a resource (for example, a circuit or bearer capability) required by the administered cConnection is not presently available. k. A network failure (38) or temporary failure (41) has occurred. Error Log entries for other maintenance objects (for example, DS1-BD or ISDN-LNK) may indicate a local problem.

  • Page 612: Adx8D-Bd (Audix Circuit Pack)

    Maintenance Objects ADX8D-BD (AUDIX Circuit Pack) MO Name (in Alarm Log) Alarm Level Initial Command To Run Full Name of MO ADX8D-BD MINOR or WARNINGS test board PCSS sh AUDIX Circuit Pack Where P is the port network number (1 for PPN); C is the carrier designation (for example, A, B, or C);...

  • Page 613: Adx8D-Pt (Audix Digital Port)

    ADX8D-PT (AUDIX Digital Port) ADX8D-PT (AUDIX Digital Port) MO Name (in Alarm Log) Alarm Level Initial Command To Run Full Name of MO ADX8D-PT MINOR test port PCSSpp l AUDIX Digital Port ADX8D-PT WARNING test port PCSSpp sh AUDIX Digital Port Where P is the port network number (1 for PPN);...
  • Page 614 Maintenance Objects Error Log Entries and Test to Clear Values Error On/Off Type Data Associated Test Alarm Level Board Test to Clear Value 0 (a) test port PCSSpp sh r 1 1 (c) 40987 None WARNING 1 (d) 1 to None WARNING 15 (e)
  • Page 615 ADX8D-PT (AUDIX Digital Port) g. The circuit pack is administered but not physically installed. The alarm will clear when a circuit pack is inserted. h. 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 caution at the beginning of this section).
  • Page 616 Maintenance Objects NO-OP Tests The maintenance strategy for EMBEDDED AUDIX emulates the one for DIG-LINE. The tests listed below apply only to DIG-LINE and not to EMBEDDED 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)
  • Page 617 ADX8D-PT (AUDIX Digital Port) Table 30. TEST #9 NPE Crosstalk Test — Continued Error Test Code Result Description/Recommendation 1000 ABORT System resources required to run this test are not available. The port may be in use. 1. Use display port PCSSpp to determine the voice port extension of the port.
  • Page 618 Maintenance Objects Table 30. TEST #9 NPE Crosstalk Test — Continued Error Test Code Result Description/Recommendation 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.
  • Page 619 ADX8D-PT (AUDIX Digital Port) Table 31. TEST #13 Voice and Control Channel Local Loop Test — Continued Error Test Code Result Description/Recommendation 1001 ABORT System resources required for this test are not available. 1. Retry the command at 1-minute intervals a maximum of 5 times. 1002 ABORT The system could not allocate time slots for the test.
  • Page 620 Maintenance Objects Table 31. TEST #13 Voice and Control Channel Local Loop Test — Continued Error Test Code Result Description/Recommendation 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.

  • Page 621: Adx16D-B (16 Port Audix Circuit Pack)

    ADX16D-B (16 Port AUDIX Circuit Pack) ADX16D-B (16 Port AUDIX Circuit Pack) Alarm MO Name (in Alarm Log) Level Initial Command To Run Full Name of MO ADX16D-B MINOR test board PCSS sh AUDIX Circuit Pack ADX16D-B WARNI NG test board PCSS sh AUDIX Circuit Pack Where P is the port network number (1 for PPN);...

  • Page 622: Adx16A-Bd (Audix Circuit Pack)

    Maintenance Objects ADX16A-BD (AUDIX Circuit Pack) MO Name (in Initial Command To Alarm Log) Alarm Level Full Name of MO ADXCL-BD or MINOR, or WARNINGS test board PCSS sh AUDIX Circuit Pack \ADX16A-BD Where P is the port network number (1 for PPN); C is the carrier designation (for example, A, B, or C);...

  • Page 623: Adx16D-P (16-Port Audix Digital Port)

    ADX16D-P (16-Port AUDIX Digital Port) ADX16D-P (16-Port AUDIX Digital Port) MO Name (in Alarm Log) Alarm Level Initial Command To Run Full Name of MO ADX16D-P MINOR or WARNINGS test port PCSSpp l AUDIX Digital Port Where P is the port network number (1 for PPN); C is the carrier designation (for example, A, B, or C);...
  • Page 624 Maintenance Objects Error Log Entries and Test to Clear Values Error Associated Alarm On/Off Type Data Test Level Board Test to Clear Value 0(a) test port PCSSpp sh r 1 1(c) 40987 None WARNING 1(d) 1 to 20 None WARNING 15(e) None 18(f)
  • Page 625 ADX16D-P (16-Port AUDIX Digital Port) g. The circuit pack is administered but not physically installed. The alarm will clear when a circuit pack is inserted. h. The circuit pack has been removed or has been insane for more than 21 minutes.
  • Page 626 Maintenance Objects NO-OP Tests The maintenance strategy for EMBEDDED AUDIX emulates the one for DIG-LINE. The tests listed below apply only to DIG-LINE and not to EMBEDDED AUDIX. These tests always return PASS. Electronic Power Feed Test (#11) Station Lamp Updates Test (#16) Station (Digital) Audits Test (#17) Digital Terminal Remote Loop Around Test (1201) NPE Crosstalk Test (#9)
  • Page 627 ADX16D-P (16-Port AUDIX Digital Port) Table 32. TEST #9 NPE Crosstalk Test — Continued Error Test Code Result Description/Recommendation 1000 ABORT System resources required to run this test are not available. The port may be in use. Use display port PCSSpp to determine the voice port extension of the port.
  • Page 628 Maintenance Objects Table 32. TEST #9 NPE Crosstalk Test — Continued Error Test Code Result Description/Recommendation 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.
  • Page 629 ADX16D-P (16-Port AUDIX Digital Port) Table 33. TEST #13 Voice and Control Channel Local Loop Test — Continued Error Test Code Result Description/Recommendation 1001 ABORT System resources required to run this test are not available. 1. Retry the command at 1-minute intervals a maximum of 5 times. 1002 ABORT The system could not allocate time slots for the test.
  • Page 630 Maintenance Objects Table 33. TEST #13 Voice and Control Channel Local Loop Test — Continued Error Test Code Result Description/Recommendation 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.

  • Page 631: Adx16A-Pt (Audix Analog Line/Control Link)

    ADX16A-PT (AUDIX Analog Line/Control Link) ADX16A-PT (AUDIX Analog Line/Control Link) MO Name (in Alarm Initial Command To Alarm Log) Level Full Name of MO ADXCL-PT or MINOR test port PCSSpp l AUDIX Analog Line/ Control Link ADX16A-PT ADXCL-PT or WARNING test port PCSSpp sh AUDIX Analog Line/ Control Link ADX16A-PT...
  • Page 632 Maintenance Objects Error Log Entries and Test to Clear Values Error Alarm On/Off Type Data Associated Test Level Board Test to Clear Value 0 (a) test port PCSSpp sh r 1 1 (c) 40977 None busyout station release station extension <extension>...
  • Page 633 ADX16A-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 Loop Around Test #161 for example, you may also clear errors generated from other tests in the testing sequence. Order of Investigation Short Test Sequence Long Test Sequence...
  • Page 634 Maintenance Objects Table 34. TEST #6 NPE Crosstalk Test Error Test Code Result Description/ Recommendation ABORT Could not allocate the necessary system resources for this test. 1. Retry the command at 1-minute intervals a maximum of 5 times. 1000 ABORT System resources required to run this test are not available.
  • Page 635 ADX16A-PT (AUDIX Analog Line/Control Link) Table 34. TEST #6 NPE Crosstalk Test — Continued Error Test Code Result Description/ Recommendation 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 for this test.

  • Page 636: Loop Around Test

    Maintenance Objects Table 35. TEST #7 Conference Circuit Test — Continued Error Test Code Result Description/Recommendation 1018 ABORT Test disabled by administration. This only applies to analog stations. 1. To enable the test for the analog station being tested, enter change station extension and set the Test field to y.
  • Page 637 ADX16A-PT (AUDIX Analog Line/Control Link) Table 36. TEST #161 Loop Around Test — Continued Error Test Code Result Description/ Recommendation 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.

  • Page 638: Alarm-Pt (Alarm Port)

    Maintenance Objects ALARM-PT (ALARM PORT) MO Name (in Alarm Log) Alarm Level Initial Command to Run Full Name of MO ALARM-PT test port PCSSpp l Alarm-Port ALARM-PT test port PCSSpp sh Alarm-Port Where P is the port network number (1 for PPN); C is the carrier designation (for example, A, B, or C);...

  • Page 639: Anl-24-L (24-Port Analog Line)

    ANL-24-L (24-Port Analog Line) ANL-24-L (24-Port Analog Line) MO Name (in Alarm Log) Alarm Level Initial Command to Run Full Name of MO ANL-24-L test port PCSSpp l 24-Port Analog Line ANL-24-L test port PCSSpp sh 24-Port Analog Line Where P is the port network number (1 for PPN); C is the carrier designation (for example, A, B, or C);...
  • Page 640 Maintenance Objects Ringing Caused by Maintenance Testing Test #48 applies momentary ringing voltage to phone equipment and monitors resulting current flow to determine whether the equipment is connected to the port. Test #48 may cause some phone equipment to ring briefly during daily maintenance.
  • Page 641 ANL-24-L (24-Port Analog Line) Notes: a. 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. b. Minor alarms on this MO may be downgraded to Warnings based on the values in set options.
  • Page 642 Maintenance Objects 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.
  • Page 643 ANL-24-L (24-Port Analog Line) Table 38. TEST #6 NPE Crosstalk Test — Continued Error Test Description/Recommendation Code Result 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.
  • Page 644 Maintenance Objects Table 38. TEST #6 NPE Crosstalk Test — Continued Error Test Description/Recommendation Code Result 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.
  • Page 645 ANL-24-L (24-Port Analog Line) Conference Circuit Test (#7) This test verifies that the NPE channel for the port being tested can correctly perform the conferencing function. Table 39. TEST #7 Conference Circuit Test Error Test Description/Recommendation Code Result ABORT Could not allocate the necessary system resources to run this test. 1.
  • Page 646 Maintenance Objects Table 39. TEST #7 Conference Circuit Test — Continued Error Test Description/Recommendation Code Result FAIL The NPE of the tested port did not conference the tones correctly. This will cause noisy and unreliable connections. 1. Use display port and status station to determine if the station is idle. If the station is idle, issue test port for this port.
  • Page 647 ANL-24-L (24-Port Analog Line) Table 40. TEST #35 Battery Feed Test Error Test Description/Recommendation Code Result ABORT Could not allocate the necessary system resources to run this test. 1. Retry the command at 1-minute intervals a maximum of 5 times. 1000 ABORT System resources required to run this test are not available.
  • Page 648 Maintenance Objects Table 40. TEST #35 Battery Feed Test — Continued Error Test Description/Recommendation Code Result PASS The port’s battery feed chip is able to provide power to the station equipment to detect on-/off-hook, but may not be able to supply power for touch-tones. If touch-tones are inoperative on this station, replace the circuit pack because this port is inoperative.
  • Page 649 ANL-24-L (24-Port Analog Line) Station Status and Translation Audits and Updates Test (#36) This test updates the analog port’s message lamp state (if it has one) and translations with information in the software. Table 41. Test #36 Station Status and Translation Audits and Updates Error Test Description/ Recommendation...
  • Page 650 Maintenance Objects Table 41. Test #36 Station Status and Translation Audits and Updates — Continued Error Test Description/ Recommendation Code Result FAIL This may be an internal software error. The message waiting lamp update failed. The translation and ringer updates were not performed because of this failure.
  • Page 651 ANL-24-L (24-Port Analog Line) Table 42. TEST #48 Station Present Test Error Test Description/Recommendation Code Result ABORT Could not allocate the necessary system resources to run this test. 1. Retry the command at 1-minute intervals a maximum of 5 times. 1000 ABORT System resources required to run this test are not available.
  • Page 652 Maintenance Objects Table 42. TEST #48 Station Present Test — Continued Error Test Description/Recommendation Code Result FAIL The terminal equipment is not connected to the circuit pack. Some terminal equipment, such as modems, may fail even when connected properly. 1. Remotely test the equipment. 2.
  • Page 653 ANL-24-L (24-Port Analog Line) Looparound Test (#161) This test checks the on-board transmission capabilities of the NPE, the codec, and the battery feed chip of the analog port. The test passes if the signal measured by the tone detector is within acceptable limits. Table 43.
  • Page 654 Maintenance Objects Table 43. TEST #161 Looparound Test — Continued Error Test Description/Recommendation Code Result 1018 ABORT The test has been disabled via administration. The default for the Test field on the Station screen is y. Determine why this field has been set to for this station.

  • Page 655: Anl-Bd (Analog Line Circuit Pack)

    ANL-BD (Analog Line Circuit Pack) ANL-BD (Analog Line Circuit Pack) MO Name Alarm (in Alarm Log) Level Initial Command to Run Full Name of MO ANL-BD test board PCSS sh 8-Port Analog Line Circuit Pack ANL-BD test board PCSS sh 8-Port Analog Line Circuit Pack ANL-BD test board PCSS sh...

  • Page 656: Anl-Line (8-Port Analog Line), Anl-Ne-L (8-Port Neon Analog Line)

    Maintenance Objects ANL-LINE (8-Port Analog Line), ANL-NE-L (8-Port Neon Analog Line) MO Name (in Alarm Log) Alarm Level Initial Command to Run Full Name of MO ANL-LINE test port PCSSpp l 8-Port Analog Line ANL-LINE test port PCSSpp sh 8-Port Analog Line ANL-NE-L test port PCSSpp l 8-Port Neon Analog Line...
  • Page 657 ANL-LINE (8-Port Analog Line), ANL-NE-L (8-Port Neon Analog Line) Hardware Error Log Entries and Test to Clear Values Error Alarm On/Off Type Data Associated Test Level Board Test to Clear Value 0 (a) test port PCSSpp sh r 1 1 (b) 40960 None 40975...
  • Page 658 Maintenance Objects Notes: a. Error type 0: 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. b. Error type 1: These are in-line errors and can only be resolved over time. —...
  • Page 659 ANL-LINE (8-Port Analog Line), ANL-NE-L (8-Port Neon Analog Line) 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.
  • Page 660 Maintenance Objects Table 45. TEST #6 NPE Crosstalk Test Error Test Code Result Description/ Recommendation 1000 ABORT System resources required to run this test are not available. The port may be busy with a valid call. Use display port PCSSpp to determine the station extension.
  • Page 661 ANL-LINE (8-Port Analog Line), ANL-NE-L (8-Port Neon Analog Line) Table 45. TEST #6 NPE Crosstalk Test — Continued Error Test Code Result Description/ Recommendation 1005 ABORT The test was aborted due to a configuration problem. This code will result under either of the following conditions: 1.
  • Page 662 Maintenance Objects Table 45. TEST #6 NPE Crosstalk Test — Continued Error Test Code Result Description/ Recommendation FAIL This test can fail due to on-board or off-board problems. Off-board problems of concern include EXP-INTF faults, TDM-BUS faults, and faults associated with the tone detectors/tone generators. Clear all off-board problems before replacing the board.
  • Page 663 ANL-LINE (8-Port Analog Line), ANL-NE-L (8-Port Neon Analog Line) 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.
  • Page 664 Maintenance Objects Table 46. TEST #35 Battery Feed Test — Continued Error Test Code Result Description/ Recommendation 1018 ABORT Test has been disabled via administration. The default for the field on Test the Station screen is y. Determine why this field has been set to for this station.
  • Page 665 ANL-LINE (8-Port Analog Line), ANL-NE-L (8-Port Neon Analog Line) Table 46. TEST #35 Battery Feed Test — Continued Error Test Code Result Description/ Recommendation The test could not relate the internal ID to the port (no board). This could be BOARD due to incorrect translations, no board is inserted, an incorrect board is inserted, or an insane board is inserted.
  • Page 666 Maintenance Objects Table 47. TEST #36 Station Status and Translation Audits and Updates Test — Continued Error Test Code Result Description/ Recommendation 1005 ABORT The test was aborted due to a configuration problem. This code will result under either of the following conditions: 1.

  • Page 667: Loop Around And Conference Test

    ANL-LINE (8-Port Analog Line), ANL-NE-L (8-Port Neon Analog Line) Table 47. TEST #36 Station Status and Translation Audits and Updates Test — Continued Error Test Code Result Description/ Recommendation FAIL This does not indicate a hardware problem but may be an internal software error.
  • Page 668 Maintenance Objects The Conference Circuit Test verifies that the NPE channel for the port being tested can correctly perform the conferencing function. As part of Test #47, the operation of the port conference circuits in the NPE for three and four parties is also tested.
  • Page 669 ANL-LINE (8-Port Analog Line), ANL-NE-L (8-Port Neon Analog Line) Table 48. TEST #47 Loop Around and Conference Test Error Test Code Result Description/ Recommendation ABORT Could not allocate the necessary system resources to run this test. 1. Retry the command at 1-minute intervals a maximum of 5 times. ABORT The port was seized by a user for a valid call.
  • Page 670 Maintenance Objects Table 48. TEST #47 Loop Around and Conference Test — Continued Error Test Code Result Description/ Recommendation 1005 ABORT The test was aborted due to a configuration problem. This code will result under either of the following conditions: 1.
  • Page 671 ANL-LINE (8-Port Analog Line), ANL-NE-L (8-Port Neon Analog Line) Table 48. TEST #47 Loop Around and Conference Test — Continued Error Test Code Result Description/ Recommendation FAIL 1. Disconnect the terminal equipment from the circuit pack at the cross-connect and run the test again. (cont’d.) 2.
  • Page 672 Maintenance Objects Station Present Test (also called Ringing Application Test) (#48) Test #48 applies momentary ringing voltage to terminal equipment and monitors resulting current flow to determine whether the equipment is connected to the port. Test #48 may cause some terminal equipment to ring briefly during daily maintenance.
  • Page 673 ANL-LINE (8-Port Analog Line), ANL-NE-L (8-Port Neon Analog Line) Table 49. TEST #48 Station Present Test — Continued Error Test Code Result Description/ Recommendation 1008 ABORT Could not allocate a ringing circuit for one of the following reasons: All the ringing circuits are in use, or The ringing generator is defective, or It is not wired correctly.
  • Page 674 Maintenance Objects Table 49. TEST #48 Station Present Test — Continued Error Test Code Result Description/ Recommendation PASS The station is connected properly to the switch. This test may also pass if no terminal equipment is connected and the terminal is located far from the switch (that is, it is off-premises).

  • Page 675: An-Ln-Pt (Analog Line Port)

    AN-LN-PT (Analog Line Port) AN-LN-PT (Analog Line Port) MO Name (in Alarm Log) Alarm Level Initial Command to Run Full Name of MO AN-LN-PT test port UUCSSpp l Analog Line Port AN-LN-PT test port UUCSSpp sh Analog Line Port UU is the universal cabinet number. 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).
  • Page 676 Maintenance Objects Error log entries and test to clear values Table 3-1. Analog line error log entries Error Associated Alarm On/Off Type Data Test Level Board Test to Clear Value test port UUCSSpp sh r 1 1(a) 40960 none 40975 40977 15(b) Audits and...
  • Page 677 AN-LN-PT (Analog Line Port) Notes: a. Error Type 1: these are in-line errors and can only be resolved over time. Aux Data 40960 indicates that too many simultaneous incoming ringing attempts were made on this board. Only 4 ports on a board may ring simultaneously.
  • Page 678 Maintenance Objects 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.
  • Page 679 AN-LN-PT (Analog Line Port) Table 50. TEST #6 NPE Crosstalk Test — Continued Error Test Code Result Description/Recommendation 1000 ABORT System resources are unavailable. 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.
  • Page 680 Maintenance Objects Table 50. TEST #6 NPE Crosstalk Test — Continued Error Test Code Result Description/Recommendation 1018 ABORT Test has been disabled via administration. The default for the Test field on the Station screen is y. Determine why this field has been set to for this station.
  • Page 681 AN-LN-PT (Analog Line Port) Conference Circuit Test (#7) This test verifies that the NPE channel for the port being tested correctly performs the conferencing function. Table 51. TEST #7 Conference Circuit Test Error Test Code Result Description/Recommendation ABORT Necessary system resources could not be allocated to run this test. 1.
  • Page 682 Maintenance Objects Table 51. TEST #7 Conference Circuit Test — Continued Error Test Code Result Description/Recommendation 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.
  • Page 683 AN-LN-PT (Analog Line Port) 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 power, and detecting the resulting current.
  • Page 684 Maintenance Objects Table 52. TEST #35 Battery Feed Test — Continued Error Test Code Result Description/Recommendation 1392 ABORT This port is currently a TTI port and the test does not execute on it. 1. Verify that the port is a TTI port: Use display port UUCSSpp.
  • Page 685 AN-LN-PT (Analog Line Port) Table 52. TEST #35 Battery Feed Test — Continued Error Test Code Result Description/Recommendation The test could not relate the internal ID to the port (no board). This result BOARD could be due to incorrect translations, no board is inserted, an incorrect board is inserted, or an insane board is inserted.
  • Page 686 Maintenance Objects Table 53. Test #36 Station Status and Translation Audits and Updates — Continued Error Test Code Result Description/ Recommendation 1006 ABORT The port is out-of-service. The busy station extension command has been given to this port, or it has been taken out-of-service by the failure of the NPE Crosstalk Test.
  • Page 687 AN-LN-PT (Analog Line Port) Table 53. Test #36 Station Status and Translation Audits and Updates — Continued Error Test Code Result Description/ Recommendation The test could not relate the internal ID to the port (no board). This result BOARD could be due to incorrect translations, no board is inserted, an incorrect board is inserted, or an insane board is inserted.
  • Page 688 Maintenance Objects Station Present Test (also called Ringing Application Test) (#48) Test #48 applies momentary ringing voltage to terminal equipment and monitors resulting current flow to determine whether the equipment is connected to the port. Test #48 may cause some terminal equipment to ring briefly during daily maintenance.
  • Page 689 AN-LN-PT (Analog Line Port) Table 54. TEST #48 Station Present Test — Continued Error Test Code Result Description/Recommendation 1008 ABORT A ringing circuit could not be allocated. Either all of the ringing circuits are in use, the ringing generator is defective, or it is not wired correctly. 1.
  • Page 690 Maintenance Objects Table 54. TEST #48 Station Present Test — Continued Error Test Code Result Description/Recommendation PASS The station is connected properly to the switch. Investigate user-reported troubles on this port by running other port tests, by examining station wiring, or by inspecting the station. NOTE: This test may also pass if no terminal equipment is connected and the terminal is located very far from the switch.
  • Page 691 AN-LN-PT (Analog Line Port) Looparound Test (#161) This test checks the on-board transmission capabilities of the NPE, the codec, and the battery feed chip of the analog port. The test passes if the signal measured by the tone detector is within acceptable limits. Table 55.
  • Page 692 Maintenance Objects Table 55. TEST #161 Looparound Test — Continued Error Test Code Result Description/Recommendation 1004 ABORT A valid call seized the port during the test and aborted the test. 1. Use display port UUCSSpp to determine the station extension. 2.
  • Page 693 AN-LN-PT (Analog Line Port) Table 55. TEST #161 Looparound Test — Continued Error Test Code Result Description/Recommendation The test could not relate the internal ID to the port (no board). This result BOARD could be due to incorrect translations, no board is inserted, an incorrect board is inserted, or an insane board is inserted.

  • Page 694: Ann-Bd (Announcement Circuit Pack)

    Maintenance Objects ANN-BD (Announcement Circuit Pack) MO Name (in Alarm Log) Alarm Level Initial Command to Run Full Name of MO ANN-BD MINOR test board PCSS l Announcement Circuit Pack ANN-BD test board PCSS l Announcement Circuit Pack Where P is the port network number (1 for PPN); C is the carrier designation (for example, A, B, or C);...
  • Page 695 ANN-BD (Announcement Circuit Pack) General Notes Here are a few very important general notes that apply to any problem on the Announcement circuit pack. The user should read this before attempting to work on the TN750 Announcement circuit pack or Announcement Ports, especially if the circuit pack needs to be replaced.
  • Page 696 It may also be necessary to save and restore announcements as part of the maintenance procedures. For a complete description of integrated announcement administration, please refer to Administrator’s Guide for Avaya MultiVantage Software. Issue 5 October 2002...
  • Page 697 ANN-BD (Announcement Circuit Pack) Announcement Session Announcements can be recorded, played back, and deleted from an announcement session. A station’s COS needs to include console permissions in order for that station to be able to enter an announcement session. To enter an announcement session, go off-hook on a station that has console permissions and enter the appropriate Feature Access Code (FAC), administered as Announcement access code on the FACs form.
  • Page 698 Maintenance Objects Hardware Error Log Entries and Test to Clear Values Table 56. Announcement Circuit Pack Error Log Entries Alarm Level Error (See WARNING On/Off Type Data Associated Test message below) Board Test to Clear Value test board PCSS sh r 1 1 (a) Circuit pack MINOR...
  • Page 699 ANN-BD (Announcement Circuit Pack) Table 56. Announcement Circuit Pack Error Log Entries — Continued Alarm Level Error (See WARNING On/Off Type Data Associated Test message below) Board Test to Clear Value 2305 140AY Loop MINOR test board PCSS sh r 3 Around Test (#210) 2561 Super Frame...
  • Page 700 Maintenance Objects If the circuit pack is not in the system, insert a circuit pack (in the same slot as the error indicates) to resolve this error. Or, if the circuit pack is in the system and the red LED is on, follow the instructions for “Red (alarm)” in Table Control and Port Circuit Pack Status LEDs.
  • Page 701 ANN-BD (Announcement Circuit Pack) h. Error Type 1025 This error is not service-affecting and no action is required. i. Error Type 1281 The SP found a fault in the speech main memory (SMM) (that is, it found one or more faulty memory locations). Whenever this error is logged, error 2817 is also logged [see Note (j)], which causes the maintenance system to run the Announcement Checksum Test (#209) to determine if the bad memory location was being used by an...
  • Page 702 Maintenance Objects n. Error type 3999 Indicates that the circuit pack sent a large number of control channel messages to the switch within a short period of time. If error type 1538 is also present, the circuit pack was taken out-of-service due to hyperactivity.
  • Page 703 ANN-BD (Announcement Circuit Pack) Angel-Speech Processor (SP) Handshake Test (#208) This test checks the integrity of the communication link between the two processors on the Announcement circuit pack. WARNING: Failure of this test indicates that the Speech Processor is insane and results in the loss of all integrated announcements on the circuit pack.

  • Page 704: Announcement Checksum Test

    Maintenance Objects Announcement Checksum Test (#209) Associated with every recorded announcement is a checksum. In this test, the SP checks a stored global checksum covering all recorded announcements against a calculated one and returns the results to the maintenance system. If the global checksum failed, maintenance requests the SP to check each individual announcement’s checksum.
  • Page 705 ANN-BD (Announcement Circuit Pack) Table 59. TEST #209 Announcement Checksum Test — Continued Error Test Code Result Description/ Recommendation 2000 ABORT Response to the test request was not received within the allowable time period. If Error Type 1538 is present in the Error Log, follow the maintenance strategy recommended for this Error Type.
  • Page 706 Maintenance Objects Table 59. TEST #209 Announcement Checksum Test — Continued Error Test Code Result Description/ Recommendation PASS All recorded announcements checksum correctly, indicating that the speech main memory is functioning properly. User-reported troubles on this circuit pack should be investigated using other circuit pack and port tests. Refer to ‘‘ANN-PT (Announcement Port)’’...

  • Page 707: Ay Loop Around Test

    ANN-BD (Announcement Circuit Pack) 140AY Loop Around Test (#210) This test checks the integrity of the record channel on the Announcement circuit pack (Announcement Port 1). The main function of the 140AY device is to accept Pulse Code Modulation (PCM)/Adaptive Differential Pulse Code Modulation (ADPCM) samples and compress/expand the samples using ADPCM.
  • Page 708 Maintenance Objects Table 60. TEST #210 140AY Loop Around Test — Continued Error Test Code Result Description/ Recommendation 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.
  • Page 709 ANN-BD (Announcement Circuit Pack) Table 60. TEST #210 140AY Loop Around Test — Continued Error Test Code Result Description/ Recommendation FAIL Test failed. The error code indicates at which speech compression rate the test actually failed (one being the first rate tested, three being the last). 1.

  • Page 710: Super Frame Match Inquiry Test

    Maintenance Objects The Announcement circuit pack lock-up can be cleared remotely by performing a soft reset to the circuit pack: busyout board PCSS (this command drops all calls in progress on the Announcement circuit pack) reset circuit pack using the reset board PCSS command release circuit pack using the release board PCSS command Super Frame Match Inquiry Test (#211) The super frame is a means by which the SP synchronizes with the 140AY device...

  • Page 711: Clock Match Inquiry Test

    ANN-BD (Announcement Circuit Pack) Clock Match Inquiry Test (#212) This test is supported to determine the state of the clock generation circuitry on the Announcement circuit pack. This circuitry is used for controlling various pieces of the hardware, like the 140AY device. It is also used to synchronize the Announcement circuit pack with the clock that is on the backplane.

  • Page 712: Ann-Pt (Announcement Port)

    Maintenance Objects ANN-PT (Announcement Port) MO Name (in Alarm Alarm Log) Level Initial Command to Run Full Name of MO ANN-PT MINOR test port PCSSpp l Announcement Port ANN-PT test port PCSSpp l Announcement Port Where P is the port network number (1 for PPN); C is the carrier designation (for example, A, B, or C);...
  • Page 713 It may also be necessary to save and restore announcements as part of the maintenance procedures. For a complete description of integrated announcement administration, please refer to Administrator’s Guide for Avaya MultiVantage Software. 555-233-119...
  • Page 714 Maintenance Objects Announcement Session Announcements can be recorded, played back, and deleted from an announcement session. A station’s COS needs to include console permissions in order for that station to be able to enter an announcement session. To enter an announcement session, go off-hook on a station that has console permissions and enter the appropriate FAC (administered as Announcement access code on the FACs form).
  • Page 715 ANN-PT (Announcement Port) Hardware Error Log Entries and Test to Clear Values Table 63. Announcement Port Error Log Entries Error Alarm On/Off Type Data Associated Test Level Board Test to Clear Value 0 (a) test port PCSSpp sh r 1 Playback Speech MINOR test port PCSSpp sh r 3...
  • Page 716 Maintenance Objects 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 Channel Administration Memory Array (CAMA) Test, for example, you may also clear errors generated from other tests in the testing sequence.
  • Page 717 ANN-PT (Announcement Port) Table 64. TEST #205 Channel Administration Memory Array (CAMA) Test — Continued Error Test Code Result Description/ Recommendation FAIL Test failed. Announcements played back on this port may sound corrupted. 1. Reset the circuit pack with reset board PCSS and run this test again. If the test continues to fail, replace the circuit pack (see Warning).

  • Page 718: Playback Speech Memory Array (Psma) Test

    Maintenance Objects 3. The save/restore announcements command times out with: Error encountered, can’t complete request The Announcement circuit pack lock-up can be cleared remotely by performing a soft reset to the circuit pack: busyout board PCSS (this command drops all calls in progress on the Announcement circuit pack) reset circuit pack using the reset board PCSS command release circuit pack using the release board PCSS command...
  • Page 719 ANN-PT (Announcement Port) Table 65. TEST #206 Playback Speech Memory Array (PSMA) Test Error Test Code Result Description/ Recommendation 1000 ABORT System resources required to run this test are not available. The port may be in use on a valid call. 1.
  • Page 720 Maintenance Objects Table 65. TEST #206 Playback Speech Memory Array (PSMA) Test — Continued Error Test Code Result Description/ Recommendation 1 to 254 FAIL Test failed. The error code indicates the number of byte count errors found by the Tone Detector. 1.

  • Page 721: Ay Channel Sanity Inquiry Test

    ANN-PT (Announcement Port) Notes: a. The Announcement circuit pack can exhibit a condition that does not allow recording. If the circuit pack gets locked into this state (this is an extremely rare condition), two of the Announcement Ports on the circuit pack (one of which is the record port) will be unusable by software.
  • Page 722 Maintenance Objects Table 66. TEST #222 140AY Channel Sanity Inquiry Test Error Test Code Result Description/ Recommendation 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. ABORT Internal system error.

  • Page 723: Announce (Announce)

    ANNOUNCE (Announce) ANNOUNCE (Announce) MO Name (in Alarm Log) Alarm Level Initial Command to Run Full Name of MO ANNOUNCE none none ANNOUNCEMENT The ANNOUNCE MO logs an error in the hardware error log if at least one of the following is true: The save announcements or restore announcements command does not complete successfully, or the...
  • Page 724 Maintenance Objects Hardware Error Log Entries Associated Alarm On/Off Error Type Aux Data Test Level Board Test to Clear Value 1(a)(c) None 257(c) None 513(b)(c) None 769(c) None 1025(c) None Notes: a. Error occurred while saving announcements. (See Table 67 on page 724 the next section for an explanation of Aux Data and for recommended repair actions.) b.
  • Page 725 ANNOUNCE (Announce) Table 67. Aux Data Error Codes and Recommended Repair Procedures — Continued Data Description/ Recommendation 32003 Announcement port is in use. 1. Wait for all Announcement ports to become available. 2. Enter the save/restore announcements command. 32004 There are no announcements recorded on the Announcement Circuit Pack. The save announcements command is not allowed to prevent the destroying of the announcement file on tape [286 systems] or on the memory card [386 systems].
  • Page 726 Maintenance Objects Table 67. Aux Data Error Codes and Recommended Repair Procedures — Continued Data Description/ Recommendation 32015 Time of day not set. 1. Set the time of day, and reenter the save/restore announcements command. 32016 Internal system errors. Check for any other ANNOUNCE errors and take corrective action.If there are no other announcements errors, do the following: 1.

  • Page 727: Atm-Bch (Atm B-Channel Trunk)

    ATM-BCH (ATM B-Channel Trunk) ATM-BCH (ATM B-Channel Trunk) MO Name (in Alarm Log) Alarm Level Initial Command to Run Full Name of MO ATM-BCH MAJOR test port UUCSSppp l ATM B-Channel Trunk ATM-BCH MINOR test port UUCSSppp l ATM B-Channel Trunk ATM-BCH WARNING test port UUCSSppp sh...
  • Page 728 Maintenance Objects Table 68. ATM ISDN service states Category Description Service states Active A call is connected over the B-channel. B-channel is in normal operating In-Service (INS) state Idle There is no call on the B-channel. Out-of-Service/Far-en The switch has not successfully negotiated B-channel connection as of d (OOS/FE) yet.
  • Page 729 ATM-BCH (ATM B-Channel Trunk) Table 69. ATM-BCH alarms by service state Service state Alarm Possible cause Possible solution Warning Trunk busied out Release the port (release trunk grp#/mbr#). Minor NPE Crosstalk Test Replace ATM circuit pack. (#6) failed Out-of-Service/NE None ATM circuit pack lost Install circuit pack or cable.
  • Page 730 Maintenance Objects Error Log Entries and Test to Clear Values Table 70. ATM-BCH Error Log entries Error Alarm On/Off Type Data Associated Test Level Board Test to Clear Value 0 (a) test port UUCSSppp 1(b) None test port UUCSSppp busyout trunk grp/mbr release trunk grp/mbr 129 (c) None...
  • Page 731 ATM-BCH (ATM B-Channel Trunk) c. Error Type 129: the far-end switch changed its ISDN service state to either out-of-service or maintenance. This may be a temporary condition because the far-end is testing that trunk or a hardware problem with the trunk. Outgoing calls may not be allowed over that trunk.
  • Page 732 Maintenance Objects j. Error Type 3585: ISDN RESTART message received. Active calls have been dropped. The following Aux Data values (Error Type 3585 only) below represent the trunk’s ISDN call state at the time Error 3585 occurred. This information can be useful if users report dropped calls on the ISDN-PRI trunks. Data Description An idle trunk received a restart.
  • Page 733 ATM-BCH (ATM B-Channel Trunk) System Technician-Demanded Tests: Descriptions and Error Codes Always investigate problems in the order presented in the table below. When you clear one of the error codes associated with a given test, you clear errors generated by other tests in the testing sequence. If you clear errors out of order, you can lose important information.
  • Page 734 Maintenance Objects Table 72. TEST #255 Signaling Link State Audit Test — Continued Error Test Code Result Description/Recommendation FAIL Signaling channel problem 1. Look for errors or alarms against the ‘‘ATM-SGRP (ATM Signaling Group)’’ ‘‘ATM-DCH (ATM D-Channel Port)’’ maintenance objects. FAIL TN230x circuit pack failed 1.
  • Page 735 ATM-BCH (ATM B-Channel Trunk) Table 73. TEST #256 Service State Audit Test Error Test Code Result Description/Recommendation 1000 ABORT Needed resources not available, port on a call or initializing 1. Run status trunk grp#/mbr#. 1. Check the results of Test #255. 1018 ABORT Maintenance disabled...
  • Page 736 Maintenance Objects Call State Audit Test (#257) This test audits the internal call state by asking the far-end switch for the ISDN call state. The test is particularly useful when you are trying to clear a hung call. If the internal call state on the near-end differs from that on the far-end, the call is torn down.
  • Page 737 ATM-BCH (ATM B-Channel Trunk) ISDN Test Call Test (#258) This non-destructive test performs a far-end looparound test over an ATM-BCH trunk if the trunk is IN-SERVICE, MAINTENANCE/NEAR-END, or OUT-OF-SERVICE/NEAR-END no calls are active on the trunk the system uses country protocol 1 (including US) or the far-end has looparound capability The test sets up a call to a far-end switch over the ATM-BCH trunk.
  • Page 738 Maintenance Objects Table 75. TEST #258 ISDN Test Call — Continued Error Test Code Result Description/Recommendation 1020 ABORT TN230x circuit-pack problem 1. See the ‘‘ATM-INTF (TN2305/6)’’ maintenance object. 1024 ABORT Maintenance/Test Digital Port in use 1. Wait until yellow and green LEDs on the Maintenance/Test circuit pack are OFF.
  • Page 739 ATM-BCH (ATM B-Channel Trunk) Table 75. TEST #258 ISDN Test Call — Continued Error Test Code Result Description/Recommendation 2000 ABORT Internal system error 2012 1. Retry the command up to 5 times at 1-minute intervals. None 2035 ABORT Call timed out 1.
  • Page 740 Maintenance Objects Table 75. TEST #258 ISDN Test Call — Continued Error Test Code Result Description/Recommendation 2208 ABORT Internal system error 1. Retry the command at 1-minute intervals a maximum of 5 times. 2209- ABORT Could not allocate needed resources 2210 1.

  • Page 741: Atm-Dch (Atm D-Channel Port)

    ATM-DCH (ATM D-Channel Port) ATM-DCH (ATM D-Channel Port) Initial System MO Name (in Alarm Technician Command Full Name of Alarm Log) Level to Run ATM-DCH MINOR test port UUCSSpp l ATM D-Channel ATM-DCH WARNING test port UUCSSpp sh ATM D-Channel pp is administered as a port in the range of 9 through 32.
  • Page 742 Maintenance Objects Hardware Error Log Entries and Test to Clear Values Table 76. ATM D-channel Error Log entries Error Alarm On/Off Type Data Associated Test Level Board Test to Clear Value 0 (a) test port UUCSSpp 18 (b) busyout port UUCSSpp WARNING release port UUCSSpp 130 (c)
  • Page 743 ATM-DCH (ATM D-Channel Port) Signaling Link Board Check (#643) This nondestructive test checks the health of the ATM TN230X trunk circuit pack hardware. The test runs on a periodic or scheduled basis, during initialization testing, and upon demand. NOTE: The board-level maintenance is handled independently of the ATM-CES signaling link maintenance, raising the possibility of inconsistent states.

  • Page 744: Atm-Intf (Tn2305/6)

    Maintenance Objects ATM-INTF (TN2305/6) MO Name (in Alarm Log) Alarm Level Initial Command to Run Full Name of MO ATM-INTF WARNING test board UUCSSpp ATM interface board The TN2305/6 is recognized by the system as an ATM Interface board (ATM-INTF) if it has not been assigned a personality through the add atm-pnc command or add atm trunk command.
  • Page 745 ATM-INTF (TN2305/6) LED states The ATM-INTF circuit pack has the standard red, green and yellow LEDs. The red and green LEDs have the traditional use: red indicates an alarm condition, green means maintenance testing in progress. The yellow LED is not used. The possible LED states are listed below: Condition Board is not healthy...
  • Page 746 Maintenance Objects System Technician-Demanded Tests: Descriptions and Error Codes Failure of this test is not logged in the Error Log. Order of Investigation Short Test Sequence Long Test Sequence D/ND Control Channel Loop Around Test (#52) D = Destructive, ND = Non-destructive Control Channel Loop-Around Test (#52) This test is non-destructive.

  • Page 747: Atm-Sgrp (Atm Signaling Group)

    ATM-SGRP (ATM Signaling Group) ATM-SGRP (ATM Signaling Group) MO Name (in Alarm Log) Alarm Level Initial Command to Run Full Name of MO ATM-SGRP MINOR test sig-group grp# ATM-CES Signaling Group ATM-SGRP WARNING test sig-group grp# ATM-CES Signaling Group grp# is the signaling group number (1-166); the test sequence can be either short or long. This Maintenance Object (ATM-SGRP) applies when ATM signaling groups have been administered on an ATM circuit pack.
  • Page 748 Maintenance Objects When there are problems with ATM-SGRP (ATM signaling group), also investigate: ‘‘ATM-DCH (ATM D-Channel Port)’’ ‘‘ATM-BCH (ATM B-Channel Trunk)’’ ‘‘SYS-LINK (System Links)’’ ‘‘PKT-BUS (Packet Bus)’’ Error Log Entries and Test to Clear Values Table 82. ATM-SGRP Signaling Group Error Log Entries Error Alarm On/Off...
  • Page 749 ATM-SGRP (ATM Signaling Group) There is no test to clear these errors. The error counter is decremented by 1 every 15 minutes. b. Error Type 18: the ATM circuit pack has been busied out (either busyout atm sig-grp or busyout board UUCSS). 1.
  • Page 750 Maintenance Objects f. Error Type 1793: failure of the Layer 2 Query Test for the primary signaling channel. Excessive AAL - The AAL layer is experiencing an excessive number of errors in trying to reconstruct Service Data Unit (SDUs). Possible causes: —...
  • Page 751 ATM-SGRP (ATM Signaling Group) Table 83. Descriptions and repair recommendations (Error Types 3840-3928) Error Code Description Recommendation 3842 A request has been made From the circuit pack and port number (in the Aux Data to use a transit network or field), determine the trunk group against which the error common carrier that cannot was reported.
  • Page 752 Maintenance Objects Table 83. Descriptions and repair recommendations (Error Types 3840-3928) — Continued Error Code Description Recommendation 3890 A request to use a network This could indicate service (for example, SDN) a local administration problem has been denied. a mismatch between the local administration and that Administration somewhere of the network provider.
  • Page 753 ATM-SGRP (ATM Signaling Group) Table 83. Descriptions and repair recommendations (Error Types 3840-3928) — Continued Error Code Description Recommendation 3906 Protocol detail; may offer a 1. If customer is complaining of unexpected intercept clue if customer is having tones when accessing ISDN trunks or PRI endpoints ISDN calls denied with an and no other cause can be found, escalate to the unexpected intercept tone.
  • Page 754 Maintenance Objects Primary Signaling Link Hardware Check (#636) The ATM-SGRP Signaling Group D-Channel port depends on the health of the TN230X interface circuit pack on which it resides. This test fails if there are problems with either the ATM-DCH (D-channel port) maintenance object or the TN230X circuit pack.
  • Page 755 ATM-SGRP (ATM Signaling Group) Table 85. TEST #647 Layer 2 Status Query Test Error Test Code Result Description/Recommendation 1132 ABORT Internal system error. The port location for the D-channel is not known. This condition should not be possible since an administered ATM circuit pack must be specified when a Signaling Group is administered: 1.
  • Page 756 Maintenance Objects Remote Layer 3 Query (#1291) This test queries the far-end switch or terminal adapter to determine if the signaling connection is functioning properly at Layer 3. It selects a B-channel in the in-service or maintenance service state and sends an ISDN Layer 3 SERVice message, which requires a response from the far end (similar to performing Test #256 on an ISDN trunk).
  • Page 757 ATM-SGRP (ATM Signaling Group) Table 86. TEST #1291 Remote Layer 3 Query — Continued Error Test Code Result Description/Recommendation 2100 ABORT Could not allocate the necessary system resources to run this test. 1. Retry the command at 1-minute intervals a maximum of 5 times. 2500 ABORT Internal system error or administration problem...

  • Page 758: Atm-Trk (Circuit Emulation Service Circuit Pack)

    Maintenance Objects ATM-TRK (Circuit Emulation Service Circuit Pack) MO Name (in Alarm Log) Alarm Level Initial Command to Run Full Name of MO ATM-TRK MAJOR test board UUCSS ATM TRUNK (ATM Circuit Emulation Service) ATM-TRK MINOR test board UUCSS ATM TRUNK (ATM Circuit Emulation Service) ATM-TRK WARNING test board UUCSS...
  • Page 759 Trunk groups per switch (max) Trunks per switch (max) R6csi Table 90 shows the ATM CES capacities for T1 and E1 circuits on the Avaya Definity Server CSI. Table 90. Ports available for trunking, for each ISDN facility type Channels per signaling Max.
  • Page 760 Maintenance Objects Table 91. ATM-TRK LED interpretation LEDs Condition LED status Error (alarm logged) Red and Booting (LEDs being tested) Blinking Green (on 200 ms, off 200 ms) Green Test/maintenance in progress Yellow Fiber Loss of Signal (LOS), LOF, MS_RDI, Blinking fast MS_AIS, LCD, HP_RDI, HP_AIS, LOP, PSC (100 ms on, 100 ms off)
  • Page 761 ATM-TRK (Circuit Emulation Service Circuit Pack) Table 92. ATM CES troubleshooting commands — Continued Command Description busyout/release atm Busyout or release of an ATM signaling group signaling-group within a trunk group. status atm signaling-group Show current status of an ATM signaling group. status trunk-group Shows status of the trunk group (ATM signaling groups are part of trunk groups).
  • Page 762 Maintenance Objects Table 93. ATM-TRK Error Log entries — Continued Error Alarm On/Off Type Data Associated Test Level Board Test to Clear Value 2049(m) None test board UUCSS 2306(n) None 2561(o) Packet interface test test board UUCSS r 2 (#598) 2817(p) 1-24 ATM Board DSP test...
  • Page 763 ATM-TRK (Circuit Emulation Service Circuit Pack) e. Error Type 257: Control Channel Loop Test #52 failed. The circuit pack is not properly connected with the control channel on the TDM bus. 1. Take the corrective action specified by Test #52. f.
  • Page 764 Path-Identifier (VPI) and Virtual Channel-Identifier (VCI) addresses. 1. Make sure that the ATM-TRK circuit-pack address is administered identically on the ATM switch and the Avaya Definity Server CSI. i. Error Type 1281: Board major signals error (loss of high-level signal). The far-end has detected a major problem in transmissions originating from the ATM-TRK circuit pack.
  • Page 765 ATM-TRK (Circuit Emulation Service Circuit Pack) Table 94. Error type 1281 Aux Data and repair procedures — Continued Alarm Data Description Repair procedure Multiplexer There is a major problem on the far end (between multiplexer Section Alarm section [MUX] and the switch) that prohibits the circuit pack from Indication Signal: sending a valid signal.
  • Page 766 If Test #1260 fails, replace the board. If Test #1260 passes, make sure the ATM address on both the Avaya Definity Server CSI and the ATM switch sides are the same for this board. If the address is the same, change the port on the ATM switch side.
  • Page 767 ATM-TRK (Circuit Emulation Service Circuit Pack) j. Error Type 1537: LANHO bus timeout. The circuit pack is transmitting too many bytes on the LAN bus for a single frame. This can be due to: an on-board fault. a faulty data received on one of the circuit pack’s external ports. If the error occurs 3 times in 10 minutes, the board is isolated from the Packet Bus and the board is alarmed.
  • Page 768 Maintenance Objects n. Error Type 2306: too many parity errors in data received from the LAN/packet bus. 1. Run test board UUCSS . Then Test 598 fails. Follow the repair procedures suggested for that test Test 598 passes. See the PKT-BUS (Packet Bus) maintenance object, and perform the specified repair.
  • Page 769 ATM-TRK (Circuit Emulation Service Circuit Pack) q. Error Type 3330: LANHO critical error. The circuit pack reports that the on-board LANHO chip is insane (possibly due to a problem in Packet Bus arbitration, in the transmission line frame, or in the circuit pack itself). The circuit pack cannot talk to the Packet Bus.
  • Page 770 Maintenance Objects 1. Run test board UUCSS long . Then Test #1259 fails with Error Code XXYY and Replace the ATM-TRK XX is an AUX value in the preceding table circuit pack. The system does not recognize the circuit Replace the ATM-TRK pack circuit pack.
  • Page 771 ATM-TRK (Circuit Emulation Service Circuit Pack) Table 95. System Technician-Demanded Tests: ATM-TRK Reset Short Test Long Test Board Order of Investigation Sequence Sequence Sequence D/ND ATM Board Time Of Day Update (#1261) Connection Audit Test (#50) Control Channel Loop Test (#52) Packet Interface Loop Around Test (#598) ATM DSP Test (#1293) ATM Board Framer Looparound Test...
  • Page 772 Maintenance Objects Table 96. TEST #50 Connection Audit Test Error Test Code Result Description/Recommendation None ABORT System resources required for this test are not available. 2100 Retry the command up to 5 times at 1-minute intervals. 1019 ABORT The test aborted because a test was already running on the port. Retry the command up to 5 times at 1-minute intervals.
  • Page 773 ATM-TRK (Circuit Emulation Service Circuit Pack) Control Channel Loop Test (#52) The nondestructive Control Channel Loop Test is part of the maintenance subsystem’s Common Port Board Testing feature. The Common Port Board test sends board vintage queries to a port circuit pack and checks the responses. CCMS downlink notifications tell the circuit pack which TDM Bus (A or B) carries the control channel and which carries the touch tones.
  • Page 774 Maintenance Objects Packet Interface Loop Around Test (#598) This nondestructive test checks the ATM-TRK circuit pack’s packet-bus interface. The LANHO chip sends data through the bus and back to itself. Table 98 describes this test, substituting “CES mode” for “PNC mode.” If the data received is consistent with the data sent, the test passes.
  • Page 775 ATM-TRK (Circuit Emulation Service Circuit Pack) ATM Board Reset (#1256) This test is destructive. This test checks the sanity of the angel processor using the Sanity and Control Interface (SAKI) test (Common Port Board test #53). It resets the circuit pack if the SAKI test fails and runs the test again.The ATM Board Reset test passes if SAKI can successfully reset and retest the board.
  • Page 776 Maintenance Objects Table 99. ATM Board Reset (#1256) — Continued Error Test Code Result Description/Recommendation 2100 ABORT Could not allocate required system resources Retry the command up to 5 times at 1-minute intervals. 2500 ABORT Internal system error Try to reset the circuit pack (reset board UUCSS). FAIL The circuit pack failed to reset FAIL...
  • Page 777 ATM-TRK (Circuit Emulation Service Circuit Pack) Table 100. ATM Board Error Query Test (#1259) Error Test Code Result Description/Recommendation 2000 ABORT Test request timed out. 2031 ABORT SCD failure. Unable to sent down-link message. 2100 ABORT Could not allocate needed system resources. 2500 ABORT Internal system error...
  • Page 778 Maintenance Objects Table 101. Aux Data XX for ATM Board Error Query Test (#1259) — Continued If XX= Then Transmit Network Processor failed Memory read failed Dual UART chip failed LANHO receive parity error LANHO FIFO over flow error LAN bus time out. LANHO Xmit FIFO overflow error One or more on-board DSPs failed Continued on next page...
  • Page 779 ATM-TRK (Circuit Emulation Service Circuit Pack) Table 102. Aux Data YY for ATM Board Error Query Test (#1259) — Continued If YY= Then LAPD Excessive retransmission requests - per VC ATM CLP (Cell Loss Priority) Bit - see MO ATM-NTWK ATM Congestion Indicator - see MO ATM-NTWK ATM Cell Underrun - see MO ATM-NTWK ATM Cell Overrun - see MO ATM-NTWK...
  • Page 780 Maintenance Objects Table 103. ATM Board Framer Looparound Test (#1260) Error Test Code Result Description/Recommendation 1002 ABORT Time slots could not be allocated. Traffic could be heavy or time slots could be out-of-service. Run display errors, and perform repairs associated with TDM-BUS errors. Retry the command up to 3 times at 1-minute intervals.
  • Page 781 ATM-TRK (Circuit Emulation Service Circuit Pack) Table 103. ATM Board Framer Looparound Test (#1260) — Continued Error Test Code Result Description/Recommendation 2060 ABORT Packet-bus link has failed. Retry the command up to 3 times at 1-minute intervals. If the test continues to abort, run display errors, and perform the repairs associated with PKT-INT errors.
  • Page 782 The nondestructive ATM-TOD-UPD test updates the system time that the ATM-TRK circuit pack uses for SDH/SONET performance monitoring and synchronizes the ATM-TRK circuit pack with the Avaya Definity Server CSI system clock. This test is run during initialization, scheduled maintenance, and craft long test.
  • Page 783 ATM-TRK (Circuit Emulation Service Circuit Pack) Table 104. ATM Board Time Of Day Update (#1261) Error Test Code Result Description/Recommendation 2031 FAIL The attempt to send the message to the ATM-TRK circuit pack was not successful. 2500 FAIL Internal system error. Did not send the time of day information to the board. Retry the command up to 3 times at 1-minute intervals.
  • Page 784 Maintenance Objects Table 105. ATM Board DSP Test (#1293) Error Test Code Result Description/Recommendation 1002 ABORT Could not allocate time slots. Traffic could be heavy or time slots could be out-of-service Run display errors, and follow associated repair procedures for TDM-BUS. Retry the command up to 3 times at 1-minute intervals.
  • Page 785 ATM-TRK (Circuit Emulation Service Circuit Pack) Table 105. ATM Board DSP Test (#1293) — Continued Error Test Code Result Description/Recommendation FAIL There is at least one bad DSP on the board. The X value indicates the number of bad talker DSPs, Y indicates the number of bad listener DSPs and Z indicates the number of bad echo canceler DSPs.
  • Page 786 Maintenance Objects Table 106. ATM Crosstalk Test (#1298) Error Test Code Result Description/Recommendation ABORT Could not allocate required system resources. Retry the command up to 5 times at 1-minute intervals. 1002 ABORT Could not allocate time slots. Traffic could be heavy or time slots could be out-of-service.

  • Page 787: Axa12-Bd/Adx8D-Bd/Axd12-Bd (Audix Circuit Packs)

    AXA12-BD/ADX8D-BD/AXD12-BD (AUDIX Circuit Packs) AXA12-BD/ADX8D-BD/AXD12-BD (AUDIX Circuit Packs) MO Name (in Alarm Log) Alarm Level Initial Command to Run Full Name of MO AXA12-BD MINOR test board UUCSS AUDIX Circuit Pack AXA12-BD WARNING test board UUCSS sh AUDIX Circuit Pack ADX8D-BD MINOR test board UUCSS sh...

  • Page 788: Axa12-Rs/Adx8D-Rs/Axd12-Rs (Audix Reserve Slots)

    Maintenance Objects AXA12-RS/ADX8D-RS/AXD12-RS (AUDIX Reserve Slots) MO Name (in Alarm Log) Alarm Level Initial Command to Run Full Name of MO AXA12-RS NONE NONE TN568 12-port analog reserve slot ADX8D-RS NONE NONE TN568 8-port digital reserve slot AXD12-RS NONE NONE TN568 12-port digital reserve slot There are no tests associated with these MOs.

  • Page 789: Bri-Bd/Lgate-Bd (Isdn-Bri Line Circuit Pack)

    BRI-BD/LGATE-BD (ISDN-BRI Line Circuit Pack) BRI-BD/LGATE-BD (ISDN-BRI Line Circuit Pack) MO Name (in Alarm Log) Alarm Level Initial Command to Run Full Name of MO BRI-BD MAJOR test board PCSS l ISDN-BRI Line Circuit Pack BRI-BD MINOR test board PCSS l ISDN-BRI Line Circuit Pack BRI-BD WARNING...
  • Page 790 Maintenance Objects Hardware Error Log Entries and Test to Clear Values Table 107. BRI-BD Error Log Entries Error Alarm On/Off Type Data Associated Test Level Board Test to Clear Value test board PCSS sh r 1 1(a) None MINOR 18(b) busyout board WARNING release board PCSS...
  • Page 791 BRI-BD/LGATE-BD (ISDN-BRI Line Circuit Pack) Notes: a. This error indicates the circuit pack totally stopped functioning or it was physically removed from the system. NOTE: The alarm is logged approximately 11 minutes after the circuit pack has been removed and/or SAKI Sanity Test (#53) fails. If the circuit pack is not in the system, insert a circuit pack (in the same slot as the error indicates) to resolve this error.
  • Page 792 Maintenance Objects h. A critical hardware failure has been detected on the circuit pack. Reset the circuit pack with busyout board PCSS and reset board PCSS. If the Circuit Pack Restart Test (#594) passes, the on-board circuitry is healthy. Retire the alarm with test board PCSS long clear. If the Circuit Pack Restart Test (#594) fails, replace the circuit pack.
  • Page 793 BRI-BD/LGATE-BD (ISDN-BRI Line Circuit Pack) k. A critical failure has been detected in the Packet Bus interface of the circuit pack. This failure may be due to either a Packet Bus fault or an on-board fault. The probability of this error being related to Packet bus problems increases with the number of ISDN-BRI circuit packs displaying this error.
  • Page 794 Maintenance Objects System Technician-Demanded Tests: Descriptions and Error Codes Always investigate tests in the order presented in the following tables when inspecting errors in the system. By clearing error codes associated with the Control Channel Loop Around Test, for example, you may also clear errors generated from other tests in the testing sequence.
  • Page 795 BRI-BD/LGATE-BD (ISDN-BRI Line Circuit Pack) Table 108. TEST #595 LANBIC Receive Parity Error Counter Test Error Test Code Result Description/ Recommendation 2000 ABORT Response to the test was not received from the circuit pack within the allowable time period. 1. If the test aborts repeatedly a maximum of 5 times, reset the circuit pack with busyout board PCSS and reset board PCSS.

  • Page 796: Bri-Dat (Isdn-Bri)

    Maintenance Objects BRI-DAT (ISDN-BRI) MO Name (in Alarm Log) Alarm Level Initial Command to Run Full Name of MO BRI-DAT WARNING test data-module ISDN-BRI Standalone Data Module The alarm level for ASAI adjuncts 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 ASAI adjuncts in the system.

  • Page 797: Bri-Port (Isdn-Bri Port), Abri-Port (Asai Isdn-Bri Port)

    WARNING, MINOR, or MAJOR for all ASAI and Avaya adjunct ports in the system. All alarming for an ASAI and Avaya adjunct and OFF-BOARD alarming for an ASAI or Avaya port is disabled if the ASAI or Avaya adjunct asks the switch to suspend maintenance. When this occurs, an error and a WARNING alarm is logged against the ASAI or Avaya adjunct.
  • Page 798 Maintenance Objects The TN556C and TN2198 ISDN-BRI Line circuit packs provide the Avaya Definity Server CSI with the interface to ISDN-BRI end points, Adjunct-Switch Application Interface (ASAI) and adjuncts (for example, CONVERSANT®. Voice System). The circuit packs contain 12 ports of line circuit interface, each of which operates with two B-channels (referred to as B1 and B2 throughout this section) and one D-channel as specified in the ISDN-BRI Specification.
  • Page 799 BRI-PORT (ISDN-BRI Port), ABRI-PORT (ASAI ISDN-BRI Port) Switch BRI line Voice or circuit pack data terminal D-channel B-channel Port B-channel Voice or data terminal Logical connection Physical connection bripor1 LJK 072501 Figure 21. ISDN-BRI Port Interactions Hardware Error Log Entries and Test to Clear Values Table 109.
  • Page 800 Maintenance Objects Table 109. ISDN-BRI Port Error Log Entries — Continued Alarm Level ABRI-PORT Alarm ATT-PORT Error Associated Level LGATE-POR Test to Clear Type Data Test BRI-PORT T ATTE-PT Board Value 769 (e) none 1281(f) NPE Crosstalk MIN/ test port (#617) PCSSpp l r 2 1537(g)
  • Page 801 BRI-PORT (ISDN-BRI Port), ABRI-PORT (ASAI ISDN-BRI Port) b. This error type indicates that the circuit pack has been removed or has been insane for more than 11 minutes. To clear the error, replace or reinsert the circuit pack. c. This error occurs when the EPF Status Inquiry fails due to an overcurrent condition or when the BRI-LINE circuit pack detects that the EPF is in an over current condition.
  • Page 802 Maintenance Objects g. This error occurs when the port receives an invalid frame over the D-channel. When CRC errors exceed five within 15 minutes, the port is taken out of service for five seconds. If five more CRC errors are received within 15 minutes of the first set of five errors, the port is taken out of service for one minute.
  • Page 803 BRI-PORT (ISDN-BRI Port), ABRI-PORT (ASAI ISDN-BRI Port) System Technician-Demanded Tests: Descriptions and Error Codes Always investigate tests in the order presented in the following tables when inspecting errors in the system. By clearing error codes associated with the NPE Crosstalk Test, for example, you may also clear errors generated from other tests in the testing sequence.
  • Page 804 Maintenance Objects This test is not executed for ABRI-PORT/ATT-PORT/LGATE-PT/ATTE-PT because the B-channels associated with the port are not used by ASAI or adjuncts. Table 110. TEST #161 Loop Around Test Error Test Code Result Description/ Recommendation 1000 ABORT System resources required to run this test are not available. The port may be busy with a valid call.
  • Page 805 BRI-PORT (ISDN-BRI Port), ABRI-PORT (ASAI ISDN-BRI Port) BRI Port Local LAN Loop Around Test (#618) This test is destructive. This test, which verifies the connectivity of a BRI port across the LAN Bus, executes only if the port is out-of-service. The test aborts if calls associated with the port are in-progress.
  • Page 806 Maintenance Objects Table 111. TEST #618 BRI Port Local LAN Loop Around Error Test Code Result Description/ Recommendation 1015 ABORT The port is not in the out-of-service service state. 1. Display the BRI Port Status form with status bri-port PCSSpp to determine which stations or adjuncts are on this port.
  • Page 807 BRI-PORT (ISDN-BRI Port), ABRI-PORT (ASAI ISDN-BRI Port) Table 111. TEST #618 BRI Port Local LAN Loop Around — Continued Error Test Code Result Description/ Recommendation FAIL The Loop Around Test has failed. 1. If the test fails repeatedly, attempt to reset the circuit pack if the other ports on the board are not in use.
  • Page 808 Maintenance Objects Tone Tone Generator Detector TDM Bus BRI Line Board Figure 23. Path of the BRI Port Local TDM Loop Around Table 112. TEST #619 BRI Port Local TDM Loop Around Error Test Code Result Description/ Recommendation 1000 ABORT The system resources required to run this test are not available.
  • Page 809 BRI-PORT (ISDN-BRI Port), ABRI-PORT (ASAI ISDN-BRI Port) Table 112. TEST #619 BRI Port Local TDM Loop Around — Continued Error Test Code Result Description/ Recommendation 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.
  • Page 810 Maintenance Objects Table 112. TEST #619 BRI Port Local TDM Loop Around — Continued Error Test Code Result Description/ Recommendation 7, 8 FAIL As stated previously, this test runs a Conference Circuit Test on each B-channel. A failure here indicates that one of these conference tests failed;...
  • Page 811 BRI-PORT (ISDN-BRI Port), ABRI-PORT (ASAI ISDN-BRI Port) Table 113. TEST #620 Electronic Power Feed Restoral Error Test Code Result Description / Recommendation 1005 ABORT This test is not valid for this port type. The TN2208 does not have an electronic power feed, and the test will abort. 2012 ABORT Internal system error.
  • Page 812 Maintenance Objects The Deactivated state indicates a problem with the BRI-LINE circuit pack. When in this state, the Level 1 interface is idle and is not trying to communicate with the BRI endpoints or adjunct. When an ISDN-BRI port is placed in the out-of-service state, Level 1 is also put into the Deactivated state.
  • Page 813 BRI-PORT (ISDN-BRI Port), ABRI-PORT (ASAI ISDN-BRI Port) Table 114. TEST #621 Level 1 Status Inquiry — Continued Error Test Code Result Description/ Recommendation FAIL Received a status of Level 1 Pending Activation-Endpoint Idle which indicates a problem with the BRI endpoint or ASAI or adjunct, the wiring to the endpoint or adjunct, or the ISDN-BRI port.
  • Page 814 Maintenance Objects Table 114. TEST #621 Level 1 Status Inquiry — Continued Error Test Code Result Description/ Recommendation FAIL For the TN556 or TN2208, received a status of Level 1 Pending Activation-Endpoint Active which indicates a problem with the BRI endpoint or ASAI or adjunct, the wiring to the endpoint or adjunct, or the ISDN-BRI port.

  • Page 815: Electronic Power Feed Inquiry

    BRI-PORT (ISDN-BRI Port), ABRI-PORT (ASAI ISDN-BRI Port) Electronic Power Feed Inquiry (#622) This test queries the BRI-LINE circuit pack for the status of the Electronic Power Feed (EPF) supplied to a BRI endpoint or an ASAI or adjunct. If the EPF is on and no overcurrent condition exists, this test passes.

  • Page 816: Layer 1 Transmission Error Counter Test

    Maintenance Objects Layer 1 Transmission Error Counter Test (#624) This test reads and clears the BRI port’s Layer 1 Transmission error counter maintained on the BRI-LINE circuit pack. This counter is incremented by the circuit pack when it detects a Layer 1 transmission problem. The test passes if the value of the counter is 0 (that is, the error is cleared).
  • Page 817 BRI-PORT (ISDN-BRI Port), ABRI-PORT (ASAI ISDN-BRI Port) Receive FIFO Overflow Error Counter Test (#625) This test reads and clears the BRI port’s Receive FIFO Overflow error counter maintained on the BRI-LINE circuit pack. This counter is incremented by the circuit pack when it detects an overflow of its receive buffers. The test passes if the value of the counter is 0 (that is, the error is cleared).
  • Page 818 Maintenance Objects Clear Error Counters Test (#270) This test is not an actual test in the strict sense of the word. There are various error counters associated with each BRI-PORT/ABRI-PORT/ATT-PORT/LGATE-PT/ATTE-PT. This test clears those counters and triggers the auditing of Terminal Endpoint Identifier (TEI) values and layer 3 reinitialization.

  • Page 819: Bri-Set, Asai-Adj, Bri-Dat

    When this occurs, an error and a WARNING alarm are logged against the endpoint. Busying out and releasing the ASAI station or ADJLK station will clear the alarm. The TN2208 ESAI MFB provides the Avaya Definity Server CSI with an Ethernet interface to Adjunct-Switch Application Interface (ASAI) and adjuncts (for example, CONVERSANT ®...
  • Page 820 Maintenance Objects ISDN-BRI endpoints come in a number of configurations. All endpoints require the D-channel to convey signaling information to the switch. A voice-only set requires only one B-channel. A voice and data-capable set requires both B-channels (one for voice and one for data). Therefore, each TN556 port can support either two voice-only sets or one voice and data-capable set.
  • Page 821 BRI-SET, ASAI-ADJ, BRI-DAT Hardware Error Log Entries and Test to Clear Values Table 119. BRI-SET/ASAI-ADJ Error Log Entries Alarm Level ABRI-PORT Alarm ATT-PORT Error Associated Level LGATE-PORT Test to Clear Type Data Test BRI-PORT ATTE-PT Board Value test BRI-SET or ASAI-ADJ ATT-ADJ LGATE-AJ...
  • Page 822 Maintenance Objects Table 119. BRI-SET/ASAI-ADJ Error Log Entries — Continued Alarm Level ABRI-PORT Alarm ATT-PORT Error Associated Level LGATE-PORT Test to Clear Type Data Test BRI-PORT ATTE-PT Board Value 3073(j) BRI Remote WARNING test station ext l Loop Back (#627) test data-module ext l r 2...
  • Page 823 BRI-SET, ASAI-ADJ, BRI-DAT Table 120. Error Type 2 Cause Values Aux Data Timer Type First T303 (SETUP timer) Second T303 (SETUP timer) T305 (DISConnect timer) First T308 (RELease timer) Second T308 (RELease timer) T316 (RESTart timer) T309 (Layer 2 Failure timer) TM100 (Management Information Message timer 1) TM200 (Management Information Message timer 2) TASAI (ASAI Routing Timer)
  • Page 824 Maintenance Objects When this error occurs for an ASAI or adjunct, the Aux Data field indicates the state of the ASAI link or link and whether an invalid response or no response was received to the query from the switch, as shown in Table 121: Table 121.
  • Page 825 BRI-SET, ASAI-ADJ, BRI-DAT f. This error occurs when the signaling link associated with a BRI endpoint has too much link establishment related traffic. This could occur if the signaling link is bouncing between assigned and established states. Software will suspend activity to this endpoint for 75 minutes when the endpoint is alarmed due to this problem (note that service suspension does not occur if the endpoint is an ASAI or adjunct).
  • Page 826 Maintenance Objects k. This error occurs whenever the point-to-point signaling link to the endpoint goes down (except when it goes down because either the PKT-CTRL or the PKT-BUS has failed or has been busied out by system technician). When this error occurs, an alarm is raised against the endpoint or adjunct. Use test station <extension>...
  • Page 827 BRI-SET, ASAI-ADJ, BRI-DAT Table 122. ASAI Cause Values — Continued Code Explanation Recommendation Service or Option Requested ASAI capability or resource is not available on the switch Not Available or adjunct. More than one adjunct may be contending for the same switch resources.
  • Page 828 Maintenance Objects m. Certain ISDN-BRI cause codes are logged by switch software. The cause code can be determined from the following formula: If the error type is greater than 3968, the ISDN-BRI cause code is equal to the error type minus 3968. This code was sent to the endpoint by the switch.
  • Page 829 BRI-SET, ASAI-ADJ, BRI-DAT Table 123. ISDN-BRI Cause Values — Continued Code Explanation Recommendation Switch Switch takes control to limit received traffic. For BRI endpoints: This Equipment cause value is not logged. For ASAI or Adjuncts: Congestion 1. See CallVisor protocol reference manual. Service or Option Not Available Requested...
  • Page 830 Maintenance Objects Table 123. ISDN-BRI Cause Values — Continued Code Explanation Recommendation Requested Requested service not supported in switch or endpoint. Facility Not 1. Consult switch and endpoint documentation to determine service Implemented support. Adjunct switch error conditions Invalid CRV An invalid CRV was sent by the adjunct.
  • Page 831 BRI-SET, ASAI-ADJ, BRI-DAT Signaling Link Status Test (#626) This test determines the current status of the signaling link. This test passes if the link is "bound" to an endpoint and fails if the link is "not bound." The definition of the term "bound" for a link depends upon the type of endpoint and may depend on the successful completion of procedures at both Layers 2 and 3 of the protocol.
  • Page 832 Maintenance Objects Table 125. TEST #626 Signaling Link Status Test — Continued Error Test Code Result Description/ Recommendation 1144 ABORT The PPN Packet Bus is out-of-service. 1. Follow the repair procedures for the Packet Bus in the PPN. 2. After completing Step 1, use test port long PCSSpp, and review the results of the BRI Port Local LAN Loop Around Test to verify the repair.
  • Page 833 BRI-SET, ASAI-ADJ, BRI-DAT Table 125. TEST #626 Signaling Link Status Test — Continued Error Test Code Result Description/ Recommendation 1113 FAIL The signaling link is not "bound" to the adjunct or endpoint. For BRI endpoints supporting MIM initialization, this error indicates that the endpoint has not been bound to a signaling link (that is, SPID initialization has not been completed).
  • Page 834 Maintenance Objects Table 126. TEST #627 BRI Remote Loop Back Error Test Code Result Description/ Recommendation 1000 ABORT Could not seize the endpoint or B-channels for test. 1. Retry the command at 1-minute intervals a maximum of 5 times. 1005 ABORT The endpoint’s MIMs Supported field is administered to “no.”...
  • Page 835 BRI-SET, ASAI-ADJ, BRI-DAT Table 126. TEST #627 BRI Remote Loop Back — Continued Error Test Code Result Description/ Recommendation 1187 ABORT The circuit pack, port or station may have been busied out by a technician. 1. Look in the Error Log for Error Type 18 (busied out) for BRI-BD, BRI-PORT, or BRI-SET.
  • Page 836 Maintenance Objects Table 126. TEST #627 BRI Remote Loop Back — Continued Error Test Code Result Description/ Recommendation 2000 FAIL No loop back activation or deactivation response is received from the endpoint. 1. Consult the endpoint documentation to determine if ISDN-BRI Management and Maintenance Procedures are supported.
  • Page 837 BRI-SET, ASAI-ADJ, BRI-DAT Table 127. TEST #628 BRI XID Error Test Code Result Description/ Recommendation 1000 ABORT The BRI-SET, ASAI-ADJ, ATT-ADJ, LGATE-AJ, ATTE-AJ is busy. The test cannot be used at this time: 1. Pause momentarily (30 seconds) and re-run at this time. NOTE: A BRI-PORT can also be busy.
  • Page 838 Maintenance Objects Table 127. TEST #628 BRI XID — Continued Error Test Code Result Description/ Recommendation 1187 ABORT The circuit pack, port or station may have been busied out by a technician. 1. Look in the Error Log for Error Type 18 (busied out) for BRI-BD, BRI-PORT, or BRI-SET.
  • Page 839 BRI-SET, ASAI-ADJ, BRI-DAT BRI Layer 3 Query Test (#629) This test is used to check the application layer communications between the switch and the endpoint or adjunct. For BRI endpoints, an application message containing the appropriate endpoint service state is sent by the switch to the endpoint. The endpoint responds with an acknowledgment to the application message.
  • Page 840 Maintenance Objects Table 128. — Continued TEST #629 BRI Layer 3 Query Error Test Code Result Description/ Recommendation 1187 ABORT The circuit pack, port or station may have been busied out by a technician. 1. Look in the Error Log for Error Type 18 (busied out) for BRI-BD, BRI-PORT, or BRI-SET.
  • Page 841 BRI-SET, ASAI-ADJ, BRI-DAT Table 128. — Continued TEST #629 BRI Layer 3 Query Error Test Code Result Description/ Recommendation 2069 ABORT The endpoint has returned an error response to the switch sent application message. 1. Retry the command at 1-minute intervals a maximum of 5 times. 2000 FAIL No response is received from the endpoint or the adjunct.
  • Page 842 Maintenance Objects BRI Set Audits Test (#630) This is a series of two tests which are classified as audits. The switch sends messages to the BRI endpoint to perform the following tests: Ringer Audit - This audit ensures that both the switch and the endpoint agree as to the current state of the endpoint’s ringer.
  • Page 843 BRI-SET, ASAI-ADJ, BRI-DAT Table 129. TEST #630 BRI Set Audits — Continued Error Test Code Result Description/ Recommendation 1187 ABORT The circuit pack, port or station may have been busied out by a technician. 1. Look in the Error Log for Error Type 18 (busied out) for BRI-BD, BRI-PORT, or BRI-SET.
  • Page 844 Maintenance Objects When plugged into the port in this manner, the test set establishes a signaling link connection with the switch and attempts to complete SPID initialization by using the Service SPID administered for the system (see the System Maintenance Administration Form).
  • Page 845 BRI-SET, ASAI-ADJ, BRI-DAT Restricted Service Starting Display Column PCSSpp ext1 SPID111111 ext2 SPID222222 Bound to First Endpoint Translation Starting Display Column PCSSpp ext1 SPID111111 ext2 SPID222222 Bound to Second Endpoint Translation Starting Display Column PCSSpp ext1 SPID111111 ext2 SPID222222 555-233-119 Issue 5 October 2002...

  • Page 846: Cabinet (Cabinet Sensors)

    Maintenance Objects CABINET (Cabinet Sensors) MO Name (in Initial Command to Alarm Log) Alarm Level Full Name of MO CABINET MAJOR test environment P Cabinet Sensors Where P is an appropriate port network number determined in the Port field from the Alarm or Error Log.
  • Page 847 CABINET (Cabinet Sensors) Fan and Filter Removal/Replacement 1. Remove the left door. 2. Remove the fan/filter access panel. See Figure Figure 25. Fan/Filter Removal Fan Assembly Removal/Replacement 1. Pull (unplug) the fan assembly from the chassis using the thumb/finger notch provided. The power for the fan automatically disconnects when the assembly is unplugged.
  • Page 848 Maintenance Objects Hardware Error Log Entries and Test to Clear Values Error Alarm On/Off Type Data Associated Test Level Board Test to Clear Value test environment P sh r 1 Cabinet Temperature MAJOR test environment P sh r 3 Query Test (#122) Run the Short Test Sequence first.
  • Page 849 CABINET (Cabinet Sensors) Cabinet Temperature Query Test (#122) This test queries the Processor circuit pack for the status of the cabinet sensors in the Compact Modular Cabinet. The 650A Power Supply is equipped with thermal protection that shuts the power supply down if the internal temperature exceeds the maximum rated safe operating temperature.
  • Page 850 Maintenance Objects — Continued Table 131. TEST #122 Cabinet Temperature Query Test Error Test Code Result Description/ Recommendation FAIL 4. If the fans are not at high speed, measure the cabinet temperature at the air intake and the air exhaust at the top of the cabinet. (cont’d.) a.
  • Page 851 CABINET (Cabinet Sensors) — Continued Table 131. TEST #122 Cabinet Temperature Query Test Error Test Code Result Description/ Recommendation FAIL There is a problem with the environment of the power system: (cont’d.) 7. The power unit could be defective. Refer to the ‘‘Removing Power’’...

  • Page 852: Cap-Mem (Memory Card Capacity)

    Maintenance Objects CAP-MEM (Memory Card Capacity) MO Name (in Alarm Log) Alarm Level Initial Command to Run Full Name of MO CAP-MEM MINOR/ WARNING test card-mem long Memory Card Capacity Downgrading the MINOR alarm (set option) generates the WARNING alarm. Memory Card Capacity tracks the percentage of translation storage space the memory card uses.
  • Page 853 CAP-MEM (Memory Card Capacity) System Technician-Demanded Tests: Descriptions and Error Codes Investigate errors in the order they appear in the table below. Short Test Long Test Order of Investigation Sequence Sequence D/ND Memory Card Insertion Test (#695) (a) Memory Card Format and Read Test (#696) (a) Memory Card Match Test (#697) (a) Memory Card Write-Protected Test (#698) (a) Memory Card Directory Recovery Test (#699) (a)
  • Page 854 Maintenance Objects Memory Card Capacity Test (#1014) This nondestructive test verifies that the memory card is using less than 98% of its translation storage space. This test runs during periodic and schedule maintenance on demand (test card-mem long, save translation). Table 132.

  • Page 855: Card-Mem (Memory Card)

    CARD-MEM (Memory Card) CARD-MEM (Memory Card) MO Name (in Alarm Log) Alarm Level Initial Command to Run Full Name of MO CARD-MEM MAJOR Memory Card CARD-MEM MINOR test card-mem long Memory Card CARD-MEM WARNING test card-mem sh Memory Card The "MAJOR" alarm occurs only at power-up time or on a Reset System 3, 4, or 5 when the switch cannot load all translations from the memory card.
  • Page 856 Maintenance Objects Always use 8 MB memory Cards, 16 MB memory cards should only be used when an 8MB card gives an error in the CAP-MEM Maintenance Object Test #1014 (Memory Card Capacity Test). 16 MB cards must also be used if a DEFINITY Wireless Business System is connected.
  • Page 857 133. Note that the add, change, duplicate, remove, and set commands interfere with daily maintenance when they are active. These commands are frequently used by customer administrators while performing routine Avaya MultiVantage Software administration. Table 133. Avaya MultiVantage Software commands Likely to Disrupt...
  • Page 858 Maintenance Objects Incomplete Command Time-out A time-out feature has been added to the MAINTENANCE-RELATED SYSTEM PARAMETERS form (accessed by the command change system parameters maintenance). This feature improves the operation of daily maintenance by allowing maintenance routines to run that might otherwise not run. It also helps to prevent the loss of translations that were not saved by the save translation command, and were also not saved because daily maintenance was prevented from running prior to the system reset.
  • Page 859 CARD-MEM (Memory Card) change system-parameters maintenance Page 1 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 Suspension Threshold: 5 Restart Notification? y...
  • Page 860 Maintenance Objects Error Log Entries and Test to Clear Values Table 134. Memory Card Error Log Entries Error Alarm On/Off Test to Clear Type Data Associated Test Level Board Value test card-mem 1(a) Memory Card Insertion MINOR test card-mem Test (#695) 513(b) Memory Card Match and WARNING...
  • Page 861 CARD-MEM (Memory Card) Notes: a. Error Type 1 — System detects that no memory card is inserted in the slot at the Processor circuit pack. If a memory card is in place, the memory card may have a bad physical connection. b.
  • Page 862 Maintenance Objects c. Error Type 1025 — The memory card has been detected with a broken directory. A MINOR/OFF_BOARD alarm is raised when maintenance cannot restore the broken directory. The memory card must be replaced before the test to resolve the alarm is run. The Aux Data field contains the following error codes: Directories on the memory card are corrupted and cannot be recovered.
  • Page 863 CARD-MEM (Memory Card) g. Error Type 3841 — The “save translation” operation failed. The reasons for failure are described in the Aux Data field and include the following: Directory file on the memory card failed the checksum test Too many commands are running Command has been aborted Command has collided with a current command Software controller is idle...
  • Page 864 Maintenance Objects 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 Memory Card Insertion Test for example, you may also clear errors generated from other tests in the testing sequence. Table 135.
  • Page 865 CARD-MEM (Memory Card) Table 136. TEST #693 Memory Card Erase/Write/Read Test Error Test Code Result Description/ Recommendation 1192 ABORT Applications are accessing the memory card. 1. Wait 10 minutes for the applications to complete. 2. Retry the command at 1-minute intervals a maximum of 5 times. 2012 ABORT Internal system error...
  • Page 866 Maintenance Objects Table 136. TEST #693 Memory Card Erase/Write/Read Test — Continued Error Test Code Result Description/ Recommendation FAIL Directories on the memory card are corrupted and cannot be recovered. FAIL "0" cannot be written into memory before an erase operation. FAIL Memory card cannot be erased.
  • Page 867 CARD-MEM (Memory Card) Table 137. TEST #694 Memory Card Translation Data Integrity Test — Continued Error Test Code Result Description/ Recommendation 2111 ABORT Inserted memory card cannot be recognized. 1. Insert a new formatted memory card into the slot at the Processor circuit pack.
  • Page 868 Maintenance Objects Memory Card Insertion Test (#695) This test, which is nondestructive, verifies whether a memory card is inserted into the memory card slot at the Processor circuit pack and also whether the system can detect its existence. Table 138. TEST #695 Memory Card Insertion Test Error Test Code...
  • Page 869 CARD-MEM (Memory Card) Memory Card Format and Read Test (#696) This is a non-destructive test, which reads the directory file from the memory card, and verifies the integrity of the directory file. Table 139. TEST #696 Memory Card format and Read Test Error Test Code...
  • Page 870 Maintenance Objects Memory Card Match Test (#697) This test is a nondestructive test. The test verifies the inserted memory card for consistency with the system configuration. The test helps answer the following questions: Is the inserted memory card a system software upgrade card? Does the size of the inserted memory card match the capacity of the system configuration? Does the inserted memory card contain the Announcement file for a...
  • Page 871 CARD-MEM (Memory Card) Table 140. TEST #697 Memory Card Match Test — Continued Error Test Code Result Description/ Recommendation FAIL The inserted memory card does not contain an Announcements file, and the system is configured with the Announcement feature. 1. Replace the memory card with a 10 MB memory card. 2.
  • Page 872 Maintenance Objects Table 140. TEST #697 Memory Card Match Test — Continued Error Test Code Result Description/ Recommendation FAIL The capacity of the inserted memory card doesn’t match the system configuration, and system translation reaches 98% of the memory card reserved storage space.
  • Page 873 CARD-MEM (Memory Card) Table 141. TEST #699 Memory Card Directory Recovery Test Error Test Code Result Description/ Recommendation 1192 ABORT Contention error. Applications are accessing the memory card. 1. Wait 10 minutes for the applications to complete. 2. Retry the command at 1-minute intervals a maximum of 5 times. 2012 ABORT Internal system error...
  • Page 874 Maintenance Objects Table 141. TEST #699 Memory Card Directory Recovery Test — Continued Error Test Code Result Description/ Recommendation FAIL Cannot write to old memory card (pre-g3v9). Card format must be post-g3v8. 1. Replace with proper card. PASS Both directory files in the inserted memory card are sane. Continued on next page Issue 5 October 2002 555-233-119...

  • Page 875: Clan-Bd (Control Lan Circuit Pack)

    CLAN-BD (Control LAN Circuit Pack) CLAN-BD (Control LAN Circuit Pack) MO Name (in Alarm Alarm Log) Level Initial Command to Run Full Name of MO CLAN-BD MINOR test board UUCSS long Control LAN Circuit Pack CLAN-BD WARNING test board UUCSS short Control LAN Circuit Pack UU is the universal cabinet number.
  • Page 876 Maintenance Objects Error Log Entries and Test to Clear Values Table 3-3. CLAN-BD Error Log Entries Error Alarm On/Off Type Data Associated Test Level Board Test to Clear Value 1(a) MINOR 18 (b) WARNING release board UUCSS 217 (c) None WARNING 65535 Control Channel...
  • Page 877 CLAN-BD (Control LAN Circuit Pack) Table 3-3. CLAN-BD Error Log Entries — Continued Error Alarm On/Off Type Data Associated Test Level Board Test to Clear Value 3842 (t) 3844 (u) 3845 (v) 3846 (w) 3848 (x) 3849 (y) 3850- 3861 (z) 3862 (aa) Continued on next page Notes:...
  • Page 878 Maintenance Objects e. Error Type 513: Circuit pack detected and reported hardware failure. 1. Reset the circuit pack (reset board UUCSS). Aux Data: 4352 External RAM error 4353 Internal RAM error 4355 ROM Checksum error 4356 Angel Message Corruption error 4357 Instruction set error f.
  • Page 879 CLAN-BD (Control LAN Circuit Pack) k. Error Type 2049: Packet Interface Test (#598) failed. 1. Attempt to clear the alarm (test board UUCSS l r 3). 2. If alarm does not clear, reset the circuit pack (reset board UUCSS). 3. If circuit pack resets, execute Packet Interface Test (#598) several times.
  • Page 880 Maintenance Objects n. Error Type 2817-2819: Congestion Query Test (#600) failed. The Error Types correspond to the descriptions: 2817 All buffers exhausted. 2819 Utilized buffers exceed threshold. Then: Active buffers exceed threshold, CLAN enters congested state. 1. Refer to Congestion Query Test (# 600) for Abort and Fail 3601s. o.
  • Page 881 CLAN-BD (Control LAN Circuit Pack) q. Error Type 3586 and 3999: Switch removed hyperactive circuit pack that reported threshold number of errors. One or more of the following symptoms may be present: Circuit pack port tests return NO BOARD. List configuration command shows circuit pack and ports are installed properly And traffic If Error Type 3999:...
  • Page 882 Maintenance Objects Below, Error Types correspond to descriptions. 3841 Internal firmware error. 3843 Bad translation RAM. Call uses another translation location. These errors do not affect service, however, they may cause reports of other errors that do affect service. If Error Type 3843 begins to affect service, it escalates to Error Type 1294. t.
  • Page 883 CLAN-BD (Control LAN Circuit Pack) System Technician-Demanded Tests: Descriptions and Error Codes Investigate errors in the order they appear in the table below. Short Test Long Test Order of Investigation Sequence Sequence D/ND Control Channel Loop-Around Test #52 Circuit Pack Restart Test #252 Invalid LAPD Frame Error Counter Test #597 PPE/LANBIC Receive Parity Error Counter Test #595 Receive FIFO Overflow Error Counter Test #596...
  • Page 884 Maintenance Objects Circuit Pack Restart Test (#252) NOTE: This test is destructive. Execute this test (not part of either short or long demand test sequence) to reset the circuit pack only if there are PPCPU errors. This test fails if the circuit pack does not return to a sane state after being reset.
  • Page 885 CLAN-BD (Control LAN Circuit Pack) PPE/LANBIC Receive Parity Error Counter Test (#595) This test is non-destructive. When the CLAN circuit pack detects a parity error with a received frame, it increments the PPE/LANBIC Receive Parity error counter. This test reads and clears the counter, and may verify repair of problem. Errors may indicate a problem with: This circuit pack A packet bus...
  • Page 886 Maintenance Objects Receive FIFO Overflow Error Counter Test (#596) This test is non-destructive. When the CLAN circuit pack detects packet bus buffer overflow, it increments the error on the FIFO Overflow error counter. This test reads and clears the counter. If errors are: Then they may be due to: Occasional...
  • Page 887 CLAN-BD (Control LAN Circuit Pack) Invalid LAPD Frame Error Counter Test (#597) This test is non-destructive. CLAN detects invalid frames when it receives a frame with a CRC error an unrecognizable frame a recognizable frame in an unexpected state When the CLAN circuit pack detects an invalid LAPD frame, it increments the Invalid LAPD Frame error counter.

  • Page 888: Packet Interface Test

    Maintenance Objects Packet Interface Test (#598) This non-destructive test checks the packet bus interface circuitry on the CLAN circuit pack. Test failure indicates faulty circuit pack. Table 147. TEST #598 Packet Interface Test Error Test Code Result Description/ Recommendation 2000 ABORT Did not receive circuit pack test response within the allowable time period.
  • Page 889 CLAN-BD (Control LAN Circuit Pack) Table 148. TEST #600 Congestion Query Test Error Test Code Result Description/ Recommendation 2000 ABORT Did not receive circuit pack test response within the allowable time period. 1. Retry command at 1-minute intervals, up to 5 times. 2.
  • Page 890 Maintenance Objects Link Status Test (#601) This non-destructive test determines the state of the call control signaling link for Control LANs. If the signaling link is physically connected, the test sends a test frame over the link and checks for a response. The test passes only if both the signaling link is connected and the test frame is successfully transmitted.

  • Page 891: Clsfy-Bd (Call Classifier Circuit Pack)

    CLSFY-BD (Call Classifier Circuit Pack) CLSFY-BD (Call Classifier Circuit Pack) MO Name (in Alarm Log) Alarm Level Initial Command to Run Full Name of MO CLSFY-BD test board PCSS sh Call Classifier Circuit Pack CLSFY-BD test board PCSS sh Call Classifier Circuit Pack Where P is the port network number (1 for PPN);...
  • Page 892 Maintenance Objects Hardware Error Log Entries and Test to Clear Values Table 150. Call Classifier Port (CLSFY-PT) Error Log Entries Error Alarm On/Off Type Data Associated Test Level Board Test to Clear Value Tone Detector MAJOR/ test port PCSSpp r 2 Audit/Update Test MINOR (a) (#43)
  • Page 893 CLSFY-PT (Call Classifier Port) System Technician-Demanded Tests: Descriptions and Error Codes Always investigate tests in the order presented in the following tables when inspecting errors in the system. By clearing error codes associated with the Tone Detection Verification Test, for example, you may also clear errors generated from other tests in the testing sequence.
  • Page 894 Maintenance Objects Table 152. TEST #42 Tone Detection Verification Test — Continued Error Test Code Result Description/ Recommendation 1003 ABORT The system could not allocate a Tone-Clock circuit pack for the test connection. This situation could occur when the system is heavily loaded or if a Tone-Clock circuit pack is not present in the port network when this test is executed.
  • Page 895 CLSFY-PT (Call Classifier Port) Table 152. TEST #42 Tone Detection Verification Test — Continued Error Test Code Result Description/ Recommendation 101-122 FAIL Forward or Backward MFC signals were not correctly generated or detected. This impacts reception of incoming MFC calls. 1.
  • Page 896 Maintenance Objects Tone Detector Audit/Update Test (#43) A sanity audit is performed on the CLSFY-PT (Call Classifier Port). Table 153. Tone Detector Audit/Update Test (#43) Error Test Code Result Description/ Recommendation none ABORT The system was not able to allocate all the resources needed for this test. 1.

  • Page 897: Co-Bd (Central Office Trunk Circuit Pack)

    CO-BD (Central Office Trunk Circuit Pack) CO-BD (Central Office Trunk Circuit Pack) MO Name (in Alarm Initial Command to Alarm Log) Level Full Name of MO CO-BD test board PCSS sh Central Office Trunk Circuit Pack CO-BD test board PCSS sh Central Office Trunk Circuit Pack Where P is the port network number (1 for PPN);...

  • Page 898: Co-Ds1 (Ds1 Co Trunk)

    Maintenance Objects CO-DS1 (DS1 CO Trunk) MO Name (in Alarm Alarm Log) Level Initial Command to Run Full Name of MO CO-DS1 MAJOR test trunk <grp/mbr> l DS1CO Trunk CO-DS1 MINOR test trunk <grp/mbr> l DS1CO Trunk CO-DS1 WARNING test trunk <grp/mbr> DS1CO Trunk A Major alarm on a trunk indicates that alarms on these trunks are not downgraded by the set options command and that at least 75 percent of the trunks in this trunk...
  • Page 899 CO-DS1 (DS1 CO Trunk) Hardware Error Log Entries and Test to Clear Values Table 154. DS1 CO Trunk Error Log Entries Error Alarm On/Off Type Data Associated Test Level Board Test to Clear Value test trunk <grp>/<mbr> 1 a) 57408 1(a) 57487 15(b)
  • Page 900 Maintenance Objects Notes: a. Error Type 1—Aux Data 57408—No tip ground is detected on an outgoing call. Aux Data 57487—PBX could not get “loop close” signal (TN767). The DS1 Interface circuit pack detected a hardware fault. These errors cause the Dial Tone Test (#314) to run and are only considered a problem if the Dial Tone Test fails (in which case Error Type 1025 also shows up).
  • Page 901 CO-DS1 (DS1 CO Trunk) k. Error Type 3840—Port Audit and Update Test (#36) failed due to an internal system error. Use status trunk to verify the status of the trunk. If the trunk is out-of-service, use release trunk to put it back into in-service. Retry the test command.
  • Page 902 Maintenance Objects Table 155. TEST #6 NPE Crosstalk Test Error Test Code Result Description/ Recommendation ABORT System resources required for this test are not available. 1. Retry the command at one-minute intervals a maximum of five times. 1000 ABORT System resources required to run this test were not available. The port may be busy with a valid call.
  • Page 903 CO-DS1 (DS1 CO Trunk) Table 155. TEST #6 NPE Crosstalk Test — Continued Error Test Code Result Description/ Recommendation 1020 ABORT The test did not run due to a previously existing error on the specific port or a more general circuit pack error. 1.
  • Page 904 Maintenance Objects Table 155. TEST #6 NPE Crosstalk Test — Continued Error Test Code Result Description/ Recommendation The test could not relate the internal ID to the port (no board). This could be BOARD due to incorrect translations, no board is inserted, an incorrect board is inserted, an insane board is inserted, or the board is hyperactive (see note below).
  • Page 905 CO-DS1 (DS1 CO Trunk) Table 156. TEST #7 Conference Circuit Test Error Test Code Result Description/ Recommendation ABORT System resources required for this test are not available. 1. Retry the command at 1-minute intervals a maximum of 5 times. 1000 ABORT The test was aborted.
  • Page 906 Maintenance Objects Table 156. TEST #7 Conference Circuit Test — Continued Error Test Code Result Description/ Recommendation 1018 ABORT The test was disabled via translation. You may want to determine why the test has been disabled before you enable it. 1.
  • Page 907 CO-DS1 (DS1 CO Trunk) Table 156. TEST #7 Conference Circuit Test — Continued Error Test Code Result Description/ Recommendation 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.
  • Page 908 Maintenance Objects Port Audit and Update Test (#36) This test sends port level translation data from switch processor to the DS1 Interface circuit pack to assure that the trunk’s translation is correct. Translation updates include the following data: trunk type (in/out), dial type, timing parameters, and signaling bits enabled.
  • Page 909 CO-DS1 (DS1 CO Trunk) Table 157. TEST #36 Port Audit and Update Test — Continued Error Test Code Result Description/ Recommendation The test could not relate the internal ID to the port (no board). This result BOARD could be due to incorrect translations, no board is inserted, an incorrect board is inserted, an insane board is inserted, or the board is hyperactive (see note below).
  • Page 910 Maintenance Objects Table 158. TEST #314 DS1CO Dial Tone Seizure Test Error Test Code Result Description/ Recommendation ABORT Internal system error 1. Retry the command at 1-minute intervals a maximum of 5 times. 1000 ABORT The test was aborted because system resources required to run this test were not available.
  • Page 911 CO-DS1 (DS1 CO Trunk) Table 158. TEST #314 DS1CO Dial Tone Seizure Test — Continued Error Test Code Result Description/ Recommendation 1020 ABORT The DS1 Interface circuit pack is out-of-service. 1. Look for DS1-BD errors in the Hardware Error Log. If present, refer to DS1-BD (DS1 Trunk Circuit Pack) Maintenance documentation.
  • Page 912 Maintenance Objects Table 158. TEST #314 DS1CO Dial Tone Seizure Test — Continued Error Test Code Result Description/ Recommendation 2000 FAIL Response to the seizure message was not received within the allowable time period. 1. Use list configuration board PCSS. If the circuit pack is a TN767B vintage 8 or 9, a failure of test 314 causes a subsequent failure of test 7 due to a firmware bug.
  • Page 913 CO-DS1 (DS1 CO Trunk) Table 158. TEST #314 DS1CO Dial Tone Seizure Test — Continued Error Test Code Result Description/ Recommendation The test could not relate the internal ID to the port (no board). This could be BOARD due to incorrect translations, no board is inserted, an incorrect board is inserted, an insane board is inserted, or the board is hyperactive (see Note below).

  • Page 914: Co-Trk (Co Trunk)

    Maintenance Objects CO-TRK (CO Trunk) MO Name (in Alarm Log) Alarm Level Initial Command to Run Full Name of MO CO-TRK MAJOR test port PCSSpp l CO Trunk CO-TRK MINOR test port PCSSpp l CO Trunk CO-TRK WARNING test port PCSSpp l CO Trunk Where P is the port network number (1 for PPN);...
  • Page 915 CO-TRK (CO Trunk) Loop Start and UK Loop Calling Guarded Clearing Operation Idle State - Tip _ ground, Ring = CO Battery a. Outgoing Call 1. PBX Off-Hook (Seize Message): Closes the Tip-Ring Loop a. CO Response: DC loop current + Dial tone 2.
  • Page 916 Maintenance Objects b. B. Incoming Call 1. CO Off-Hook (Seizure): CO applies ground on Tip, CO applies ringing voltage a. PBX Response: Detect ringing, ring destination 2. PBX Off-Hook (Answer Message): Close loop a. CO Response: Trip ringing, provide loop current 3.
  • Page 917 CO-TRK (CO Trunk) Table 159. CO Trunk Error Log Entries — Continued Error Alarm On/Off Type Data Associated Test Level Board Test to Clear Value 1793 Loop Around and MAJ/MIN/ test port PCSS l r 3 Conference Test (#33) 2049 NPE Cross Talk MAJ/MIN/ test port PCSS l r 3...
  • Page 918 Maintenance Objects 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, reinsert or replace the circuit pack. d. Aux data 57345 -- Single polarity ringing current Aux data 57376 -- No loop current on incoming call Aux data 57408 -- No tip ground detected on outgoing call Aux data 57424 -- No loop current on outgoing call...
  • Page 919 CO-TRK (CO Trunk) Table 160. CO Trunk Errors with NO Tests Error Type Data Description and System Action System Technician Action 57347 Port error. Ringing without ground. This error is See Note at end of table. detected on an incoming call on a ground-start CO trunk.
  • Page 920 Maintenance Objects Table 160. CO Trunk Errors with NO Tests — Continued Error Type Data Description and System Action System Technician Action 2561 57345 Single polarity ringing current. This error results Check for other errors and from abnormal ringing current, but does not see Note at end of table.
  • Page 921 CO-TRK (CO Trunk) Notes for Table 160: 1. At the administration terminal, busyout the affected port, and run a Long Test Sequence. Observe the test results. If any tests fail, refer to the description of the tests and the associated error codes. Release the port. If users continue to report troubles, check for other errors and make test calls to determine whether the problem should be escalated or referred to the 2.
  • Page 922 Maintenance Objects System Technician-Demanded Tests: Descriptions and Error Codes Always investigate tests in the order they are presented in the table below when inspecting errors in the system. By clearing error codes associated with the NPE Crosstalk Test, for example, you may also clear errors generated from other tests in the testing sequence.
  • Page 923 CO-TRK (CO Trunk) Table 161. TEST #0 Dial Tone Test Error Test Code Result Description/ Recommendation ABORT Could not allocate system resources to run this test. 1. Retry the command at 1-minute intervals a maximum of 5 times. 1000 ABORT System resources required to run this test are not available.
  • Page 924 Maintenance Objects Table 161. TEST #0 Dial Tone Test — Continued Error Test Code Result Description/ Recommendation FAIL Trunk was seized, but dial tone could not be detected. 1. Test all administered outgoing ports on the board. Failure of 1 indicates a problem toward the CO.
  • Page 925 CO-TRK (CO Trunk) Table 161. TEST #0 Dial Tone Test — Continued Error Test Code Result Description/ Recommendation The test could not relate the internal ID to the port (no board). BOARD 1. Check to ensure that the board translations are correct. Translate the board, if necessary.
  • Page 926 Maintenance Objects Table 162. TEST #3 CO Demand Diagnostic Test — Continued Error Test Code Result Description/ Recommendation 1004 ABORT The port was seized by a user for a valid call. Use the display port PCSSpp command to determine the trunk group/member number of the port.
  • Page 927 CO-TRK (CO Trunk) Table 162. TEST #3 CO Demand Diagnostic Test — Continued Error Test Code Result Description/ Recommendation FAIL Failure to detect ground or faulty ground detected on Ring lead. Display the hardware errors for this trunk, to determine if the fault was on- or-off board. Look for Error Type 1025 or 1281 (if both appear in the Hardware Error Log, pick the most recent error).
  • Page 928 Maintenance Objects Table 162. TEST #3 CO Demand Diagnostic Test — Continued Error Test Code Result Description/ Recommendation The test could not relate the internal ID to the port (no board). BOARD 1. Check to ensure that the board translations are correct. Translate the board, if necessary.
  • Page 929 CO-TRK (CO Trunk) NPE Crosstalk Test (#6) One or more Network Processing Elements (NPEs) reside on each circuit pack with a TDM Bus interface. The NPE controls port connectivity and gain, and provides conferencing functions on a per port basis. The NPE Crosstalk 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.
  • Page 930 Maintenance Objects Table 163. TEST #6 NPE Crosstalk Test — Continued Error Test Code Result Description/ Recommendation 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.
  • Page 931 CO-TRK (CO Trunk) Loop Around and Conference Circuit Test (#33) This test checks the reflective loop around and conference capabilities of a CO port circuit. The test uses 404-Hz, 1004-Hz, and 2804-Hz tones. Each tone is transmitted separately through the loop and checked. Table 164.
  • Page 932 Maintenance Objects Table 164. TEST #33 Loop Around and Conference Circuit Test — Continued Error Test Code Result Description/ Recommendation 1003 ABORT The system could not allocate a tone receiver for the test. The system may be oversized force. 1. Look for TTR-LEV errors in the Error Log. If present, refer to TTR-LEV Maintenance documentation.
  • Page 933 CO-TRK (CO Trunk) Table 164. TEST #33 Loop Around and Conference Circuit Test — Continued Error Test Code Result Description/ Recommendation FAIL The conference capabilities of the port failed (Error Code 7). 129, The reflective 404-Hz Tone Test failed. No transmission was detected to or from the port (Error Code 129).
  • Page 934 Maintenance Objects Port Audit Update Test (#36) This test sends updates of the CO port translation for all ports on the circuit pack that have been translated. The update is non-disruptive and guards against possible corruption of translation data contained on the circuit pack. No response message is expected from the circuit pack once it receives translation updates.
  • Page 935 CO-TRK (CO Trunk) Table 165. TEST #36 Port Audit Update Test — Continued Error Test Code Result Description/ Recommendation The test could not relate the internal ID to the port (no board). BOARD 1. Check to ensure that the board translations are correct. Translate the board, if necessary.
  • Page 936 Maintenance Objects Table 166. TEST #844-848 Transmission Test Error Test Code Result Description/ Recommendation 1000 ABORT System resources required to run this test are not available. The port may be busy with a valid call. Use display port PCSSpp to determine the trunk group/member number of the port.
  • Page 937 CO-TRK (CO Trunk) Table 166. TEST #844-848 Transmission Test — Continued Error Test Code Result Description/ Recommendation 1905 ABORT Intercept tone detected from far end. 1. Get the test line data and verify it with the far end. Dial the test number manually to see if the TTL is reached.
  • Page 938 Maintenance Objects Table 166. TEST #844-848 Transmission Test — Continued Error Test Code Result Description/ Recommendation 1938 ABORT Near-end self test failed. 1. Test the TN2402/TN798 circuit pack. 1939 ABORT Loss self check at 0dBm at 1004 Hz failed. 1. Test the TN2402/TN798 circuit packs. 2.
  • Page 939 CO-TRK (CO Trunk) Table 166. TEST #844-848 Transmission Test — Continued Error Test Code Result Description/ Recommendation 2056 ABORT An error occurred while trying to obtain results from the TN2402/TN798 circuit pack. 1. Test the TN2402/TN798 circuit pack. FAIL Measured transmission performance was in the unacceptable range as administered on the trunk group form.

  • Page 940: Config (System Configuration)

    Maintenance Objects CONFIG (System Configuration) MO Name (in Alarm Log) Alarm Level Initial Command to Run Full Name of MO CONFIG none none System Configuration The System Configuration maintenance object (MO) oversees logical insertion and removal of circuit packs in the system. When Switch Control detects that a circuit pack is present in a port slot, it informs System Configuration and System Configuration queries the circuit pack to determine the type and vintage of the circuit pack.

  • Page 941: Cust-Alm (Customer-Provided Alarming Device)

    CUST-ALM (Customer-Provided Alarming Device) CUST-ALM (Customer-Provided Alarming Device) MO Name (in Alarm Alarm Log) Level Initial Command to Run Full Name of MO CUST-ALM none test customer-alarm PC Customer-Provided Alarming Device Where PC is an appropriate port network number and carrier. The system provides customers a way to connect their own alarm indication device to a switch.
  • Page 942 Maintenance Objects Error Log Entries and Test to Clear Values Error Type Aux Data Associated Test Alarm Level On/Off Board Test to Clear Value none none none System Technician-Demanded Tests: Descriptions and Error Codes There are no errors associated with the CPAD CUST-ALM MO. The test customer-alarm PC command allows a technician to check that the customer-provided alarming device is correctly installed and functional.
  • Page 943 CUST-ALM (Customer-Provided Alarming Device) Customer-Provided Alarming Device Test (#115) This test closes the relay that activates the CPAD for 1 minute only within the port network specified. If it takes longer than 1 minute to check that the CPAD has been activated, the Repeat field on the test customer-alarm PC command can be used to close the relay for up to 99 minutes.
  • Page 944 Maintenance Objects Issue 5 October 2002 555-233-119...

  • Page 945: Data-Bd (Data Channel Processor Circuit Pack)

    DATA-BD (Data Channel Processor Circuit Pack) DATA-BD (Data Channel Processor Circuit Pack) MO Name (in Alarm Log) Alarm Level Initial Command to Run Full Name of MO DATA-BD WARNING test network-control Network Control Circuit Pack DATA-BD MINOR test network-control Network Control Circuit Pack DATA-BD WARNING test network-control...
  • Page 946 Table 168. Data Channel Processor Circuit Pack Error Log Entries — Continued Alarm On/Off Error Type Data Associated Test Level Board Test to Clear Value 769 (e) 4358 None 1025 (f) 4363 NPE Audit Test (#50) test network-control [a | b] 1538 (g) Data Channel Reset MINOR...
  • Page 947 DATA-BD (Data Channel Processor Circuit Pack) b. The circuit pack has been logically administered but not physically installed. The alarm is cleared when the circuit pact is installed. c. This error indicates transient communications problems with this circuit pack. This error is not service-affecting and no action is required. d.
  • Page 948 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 NPE Audit Test, for example, you may also clear errors generated from other tests in the testing sequence. Short Test Long Test Order of Investigation...
  • Page 949 DATA-BD (Data Channel Processor Circuit Pack) Control Channel Loop Around Test (#52) This test queries the circuit pack for its circuit pack code and vintage and verifies its records. Table 170. TEST #52 Control Channel Loop Around Test Error Test Code Result Description/Recommendation...

  • Page 950: Data-Chl (Data Channel)

    DATA-CHL (Data Channel) MO Name (in Alarm Alarm Log) Level Initial Command to Run Full Name of MO DATA-CHL MINOR test data-module l <ext> Data Channel DATA-CHL WARNING test data-module sh <ext> Data Channel The test data-module <ext> long command drops all sessions on all of the Data Channels.
  • Page 951 DATA-CHL (Data Channel) From the viewpoint of administration, the four DATA-CHLs on the TN2402/TN798 Processor circuit pack are numbered 01 through 04. Each DATA-CHL may be assigned a unique extension using the add data-module [ <ext> | next ] command. These extensions are called active extensions. When assigning an active extension to a DATA-CHL XX (where XX is 01, 02, 03, or 04) the Add Data-Module form also requires the user to assign a unique maintenance extension.
  • Page 952 If a DATA-CHL is busy but is not being used for one of these links, then it is being used for a secondary administration terminal connection or for maintenance testing. If it is being used for a secondary administration terminal connection, then in order to test the DATA-CHL that the connection is using, the DATA-CHL must be busied out using the busyout data-module <ext>...
  • Page 953 DATA-CHL (Data Channel) 3. For each of the extensions in the Primary Output Extension and Secondary Output Extension fields, issue the status data-module <ext> command using the extension. Note the value in the Connected Ports field of the resulting form. If there is a port value in the field, then the indicated port is a Data Channel (DATA-CHL).
  • Page 954 Error Log Entries and Test to Clear Values Table 171. Data Channel Error Log Entries Error Alarm On/Off Type Data Associated Test Level Board Test to Clear Value test data-module <ext> sh r 1 Local Loop Back Test MINOR test data-module <ext> sh r 3 (#111) busyout data-module WARNING...
  • Page 955 DATA-CHL (Data Channel) System Technician-Demanded Tests: Descriptions and Error Codes There are two system technician test commands that include the Data Channels (DATA-CHLs). The test data-module <ext> [short | long] command tests the single DATA-CHL that has the extension specified by <ext>. The test network-control [short | long] command tests each administered DATA-CHL that resides on the Processor circuit pack in the specified carrier.
  • Page 956 Table 172. System Technician-Demanded Tests: DATA-CHL — Continued Short Test Long Test Order of Investigation Sequence Sequence D/ND Data Channel Local Loop Back Test (#111) Switch Control Reset Test (#93) (b) (d) Time-of-Day Clock Test (#95) (b) Control Channel Interface Test (#92) (b) Control Channel Transmission Test (#94) (b) 12 Volt Power Supply Test (#701) (c) Memory Card Insertion Test (#695) (c)
  • Page 957 DATA-CHL (Data Channel) Data Channel Reset Test (#107) This test is destructive. This test resets the entire data communications interface provided by the four DATA-CHLs. All existing connections over the DATA-CHLs are dropped. Table 173. TEST #107 Data Channel Reset Test Error Test Code...
  • Page 958 Table 174. TEST #108 Data Channel Dual Port RAM Test Error Test Code Result Description/Recommendation 1000 ABORT System resources required to run this test are not available. 1. Retry the command at 1-minute intervals a maximum of 5 times. FAIL The dual port RAM is not functioning correctly.
  • Page 959 DATA-CHL (Data Channel) If this test aborts or fails, it is impossible to determine from this test alone whether the defective DATA-CHL is the target DATA-CHL or the arbitrarily chosen DATA-CHL, or if the problem lies with the TDM Bus, or Tone-Clock circuit pack. The results of running Tests #107, #108, #110, and #111 on the DATA-CHL can be used to determine whether the target DATA-CHL is defective.
  • Page 960 Table 175. TEST #109 Data Channel Remote Maintenance Loop Around Test — Continued Error Test Code Result Description/Recommendation ABORT Internal system error 1. Retry the command at 1-minute intervals a maximum of 5 times. 1000 ABORT For this test, an Error Code of 1000 can have one of several different meanings: a.
  • Page 961 DATA-CHL (Data Channel) Table 175. TEST #109 Data Channel Remote Maintenance Loop Around Test — Continued Error Test Code Result Description/Recommendation 1000 ABORT 3. Issue the list data-module command to determine if other DATA-CHLs are administered. If no other DATA-CHLs are administered, administer at (cont’d.) least one at this time.
  • Page 962 Table 175. TEST #109 Data Channel Remote Maintenance Loop Around Test — Continued Error Test Code Result Description/Recommendation 1006 ABORT 1. Issue the list data-module command to determine if other DATA-CHLs are administered. If no other CATA-CHLs are administered, administer at (cont’d.) least one at this time.
  • Page 963 DATA-CHL (Data Channel) Table 175. TEST #109 Data Channel Remote Maintenance Loop Around Test — Continued Error Test Code Result Description/Recommendation FAIL In the case of Error Codes 40 and 41, the Remote Maintenance Loop Around Test failed because the data received over the connection did not match the 2000 data sent over the connection (data was corrupted).
  • Page 964 Table 175. TEST #109 Data Channel Remote Maintenance Loop Around Test — Continued Error Test Code Result Description/Recommendation FAIL 6. If the result of Test #110 is FAIL and the result of Test #111 is PASS for the target DATA-CHL, then the most likely problem is that the TDM Bus or (cont’d.) 2000 Tone-Clock circuit pack is defective.
  • Page 965 DATA-CHL (Data Channel) Table 175. TEST #109 Data Channel Remote Maintenance Loop Around Test — Continued Error Test Code Result Description/Recommendation FAIL If the result of Test #107 is PASS and the result of Test #108 is PASS, then the target DATA-CHL is defective. (cont’d.) 2000 Issue the remove data-module <ext>...
  • Page 966 Table 176. TEST #110 Data Channel Crosstalk Test Error Test Code Result Description/Recommendation ABORT For this test, an Error Code of 4 can have one of two different meanings: a. The target DATA-CHL is busy and, therefore, not available for use. b.
  • Page 967 DATA-CHL (Data Channel) Table 176. TEST #110 Data Channel Crosstalk Test — Continued Error Test Code Result Description/Recommendation 1000 ABORT For this test, an Error Code of 1000 can have one of several different meanings: a. The target DATA-CHL is busy and, therefore, not available for use. b.
  • Page 968 Table 176. TEST #110 Data Channel Crosstalk Test — Continued Error Test Code Result Description/Recommendation FAIL In the case of Error Code 40, the Crosstalk Test failed because the data received over the connection did not match the data sent over the connection (data was corrupted).
  • Page 969 DATA-CHL (Data Channel) Table 176. TEST #110 Data Channel Crosstalk Test — Continued Error Test Code Result Description/Recommendation FAIL 4. If the result of Test #111 is FAIL, then the most likely problem is that the target DATA-CHL is defective, or the Processor circuit pack is defective. (cont’d.) Busyout all functions that are using the Data Channels (DATA-CHLs).
  • Page 970 Table 176. TEST #110 Data Channel Crosstalk Test — Continued Error Test Code Result Description/Recommendation PASS The target DATA-CHL, Processor circuit pack, TDM Bus (TDM-BUS), and Tone-Clock circuit pack (TONE-BD, TONE-PT, TDM-CLK) are functioning. Connections can be established over the target DATA-CHL. Continued on next page Data Channel Local Loop Back Test (#111) This test verifies the integrity of the dual port RAM that is shared between the...
  • Page 971 DATA-CHL (Data Channel) Table 177. TEST #111 Data Channel Local Loop Back Test Error Test Code Result Description/Recommendation ABORT For this test, an Error Code of 4 can have one of two different meanings: b. The target DATA-CHL is busy and, therefore, not available for use. c.
  • Page 972 Table 177. TEST #111 Data Channel Local Loop Back Test — Continued Error Test Code Result Description/Recommendation 1000 ABORT For this test, an Error Code of 1000 can have one of several different meanings: a. The target DATA-CHL is busy and, therefore, not available for use. b.
  • Page 973 DATA-CHL (Data Channel) Table 177. TEST #111 Data Channel Local Loop Back Test — Continued Error Test Code Result Description/Recommendation FAIL In the case of Error Code 40, the Local Loop Back Test failed because the 2000 data received over the connection did not match the data sent over the 2003 connection (data was corrupted).
  • Page 974 Table 177. TEST #111 Data Channel Local Loop Back Test — Continued Error Test Code Result Description/Recommendation FAIL c. If the result of Test #107 is PASS and the result of Test #108 is PASS, then the target DATA-CHL is defective. 1.

  • Page 975: Data-Con (Network Control Driver)

    DATA-CON (Network Control Driver) DATA-CON (Network Control Driver) MO Name (in Alarm Alarm Log) Level Initial Command to Run Full Name of MO DATA-CON MINOR none Network Control Driver The TN2402/TN798 Processor circuit pack contains the following objects: the SW-CTL (Switch Control), four DATA-CHLs (Data Channels), the DATA-CON (Network Control Driver), and the generic hardware that interfaces with the TDM Bus (DATA-BD).
  • Page 976 Error Log Entries and Test to Clear Values Table 178. Network Control Driver Error Log Entries Error Alarm On/Off Test to Clear Type Data Associated Test Level Board Value (a) none Local Loop Back Test (#111) MINOR none Remote Maintenance Loop Around MINOR none Test (#109)

  • Page 977: Dat-Line (Data Line)

    DAT-LINE (Data Line) DAT-LINE (Data Line) MO Name (in Alarm Full Name of Alarm Log) Level Initial Command to Run DAT-LINE MINOR test port PCSSpp l Data Line DAT-LINE WARNING test port PCSSpp sh Data Line Where P is the port network number (1 for PPN); C is the carrier designation (for example, A, B, or C);...
  • Page 978 Error Log Entries and Test to Clear Value Table 179. Data Line Error Log Entries Error Alarm On/Off Type Data Associated Test Level Board Test to Clear Value test port PCSSpp sh r 1 Digital Loop Around MINOR test port PCSSpp sh r 2 Test (#171) 15(a) Audit Update Test...
  • Page 979 DAT-LINE (Data Line) 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 Digital Loop Around Test, for example, you may also clear errors generated from other tests in the testing sequence.
  • Page 980 Table 180. TEST #6 NPE Crosstalk Test — Continued Error Test Code Result Description/Recommendation 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.
  • Page 981 DAT-LINE (Data Line) Conference Circuit Test (#7) The Conference Circuit Test verifies that the NPE channel for the port being tested can correctly perform the conferencing function. The NPE is instructed to listen to several different tones and conference the tones together. The resulting signal is then measured by a Tone Detector port.
  • Page 982 Audit Update Test (#36) This audit makes sure that the hardware state of the Data Line is consistent with the system translations. When this audit is run, the port is queried for the switchhook state, and the software state is updated according to the returned value.
  • Page 983 DAT-LINE (Data Line) Digital Loop Around Test (#171) The Digital Loop Around Test checks the Data Line’s ability to transmit and receive data on the TDM Bus. Data is sent through Data Channel 3 (data channel port 3) over the TDM Bus, internally looped through the Data Line back onto the TDM Bus, and received again by Data Channel 3.
  • Page 984 Table 183. TEST #171 Digital Loop Around Test — Continued Error Test Code Result Description/Recommendation 2004 ABORT Failed to receive an off-hook from the Data Channel. 2005 ABORT The handshake between the data channel and the data line port failed. 1.

  • Page 985: Detr-Bd (International Version)

    The companding mode of the DETR-BD circuit pack must match the administered mode for the system for proper tone detection. The companding mode is administered on the System-Parameters Country-Options form. Refer to Administrator’s Guide for Avaya MultiVantage Software. For all DETR-BD circuit pack level errors, refer to ‘‘XXX-BD (Common Port Circuit Pack)’’...

  • Page 986: Did-Ds1 (Ds1 Did Trunk)

    DID-DS1 (DS1 DID Trunk) MO Name (in Alarm Alarm Log) Level Initial Command to Run Full Name of MO DID-DS1 MAJOR test trunk <grp>/<mbr> l Direct Inward Dial Trunk DID-DS1 MINOR test trunk <grp>/<mbr> l Direct Inward Dial Trunk DID-DS1 WARNING test trunk <grp>/<mbr>...
  • Page 987 DID-DS1 (DS1 DID Trunk) Table 184. DID-DS1 Error Log Entries — Continued Error Alarm On/Off Type Data Associated Test Level Board Test to Clear Value 18 (c) WARNING release trunk <grp>/mbr> 130 (d) None WARNING test trunk <grp>/<mbr> 257 (e) 57474 57473 513 (f)
  • Page 988 e. DS1 Interface circuit pack detects a hardware error. The Aux Data field contains the Error Type: 57474, rotary dial rate above 12 pulses per second; 57473, rotary dial rate below eight pulses per second. f. DS1 Interface circuit pack detects a hardware error. The Aux Data field contains the Error Type: 57392, no external release on PBX disconnect.
  • Page 989 DID-DS1 (DS1 DID Trunk) NPE Crosstalk Test (#6) One or more NPEs reside on each circuit pack with a TDM Bus interface. The NPE controls port connectivity and gain, and provides conferencing functions on a per-port basis. The NPE Crosstalk 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.
  • Page 990 Table 185. TEST #6 NPE Crosstalk Test — Continued Error Test Code Result Description/ Recommendation 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.
  • Page 991 DID-DS1 (DS1 DID Trunk) Table 185. TEST #6 NPE Crosstalk Test — Continued Error Test Code Result Description/ Recommendation FAIL The test failed. This can be due to on-board or off-board problems. Off-board problems of concern include EXP-PN and EXP-INTF faults, TDM-BUS faults, and faults associated with the tone detectors/tone generators.
  • Page 992 Table 186. TEST #7 Conference Circuit Test Error Test Code Result Description/ Recommendation ABORT Could not allocate the necessary system resources to run this test. 1. Retry the command at 1-minute intervals a maximum of 5 times. 1000 ABORT System resources required to run this test were not available. The port may be busy with a valid call.
  • Page 993 DID-DS1 (DS1 DID Trunk) Table 186. TEST #7 Conference Circuit Test — Continued Error Test Code Result Description/ Recommendation 1018 ABORT The test was disabled via translation. You may want to determine why the test has been disabled before you enable it. 1.
  • Page 994 Table 186. TEST #7 Conference Circuit Test — Continued Error Test Code Result Description/ Recommendation FAIL The NPE of the tested port did not conference the tones correctly. This can cause noisy and unreliable connections. 1. Enter the list configuration board PCSS command. If the circuit pack is a TN767B vintage 8 or 9, replace the circuit pack with a TN767C V3 or later.
  • Page 995 DID-DS1 (DS1 DID Trunk) Port Audit and Update Test (#36) This test sends port level translation data from the switch processor to the DS1 Interface circuit pack to assure that the trunk’s translation is correct. Translation updates include the following data: trunk type (in/out), dial type, timing parameters, and signaling bits enabled.
  • Page 996 Table 187. TEST #36 Port Audit and Update Test — Continued Error Test Code Result Description/ Recommendation PASS Trunk translation has been updated successfully. The current trunk states kept in the DS1 Interface circuit pack and switch software are consistent. If the trunk is busied out, the test does not run, but returns PASS.

  • Page 997: Did-Trk (Did Trunk)

    2-wire analog line from the CO and the Avaya Definity Server CSI. The DID port receives 3 to 5 digits from the CO that is used to directly connect an outside caller to the called station without assistance from an attendant.
  • Page 998 Central office switch Switch Incoming trunk calls only cydff1p1 LJK 030701 Figure 26. DID Trunk Interactions For each call, the CO switch signals the system by opening and closing individual DID loops (one of the eight ports) and causing the starting or stopping of loop current.
  • Page 999 DID-TRK (DID Trunk) 2. NPE Crosstalk Test—verifies the switch connection operation of the circuit pack. The test also verifies that the trunk circuitry only talks on the selected time slot on the TDM Bus and never crosses over to time slots reserved for other connections.
  • Page 1000 Hardware Error Log Entries and Test to Clear Values Table 188. DID Trunk Error Log Entries Error Alarm On/Off Type Data Associated Test Level Board Test to Clear Value test port PCSSpp sh r 1 1 (a) None 1 (b) 57476 None 1 (c)
  • Page 1001 DID-TRK (DID Trunk) Notes: A common trouble on DID trunks, which reports no errors or alarms, occurs when the CO busies out the port (disconnects port). This situation occurs when the CO thinks there are problems with the DID port. In this case, no incoming calls are possible through this port.

Table of Contents