Maintenance Alarms for Avaya Communication

Maintenance Alarms for Avaya Communication
Maintenance Alarms for Avaya
Communication Manager 4.0,
Media Gateways and Servers
03-300430
Issue 3
February 2007
© 2007 Avaya Inc.
All Rights Reserved.
Notice
While reasonable efforts were made to ensure that the information in this
document was complete and accurate at the time of printing, Avaya Inc. can
assume no liability for any errors. Changes and corrections to the information
in this document may be incorporated in future releases.
For full legal page information, please see the complete document,
Avaya Legal Page for Software Documentation,
Document number 03-600758.
To locate this document on the website, simply go to
http://www.avaya.com/support and search for the document number in
the search box.
Documentation disclaimer
Avaya Inc. is not responsible for any modifications, additions, or deletions to
the original published version of this documentation unless such modifications,
additions, or deletions were performed by Avaya. Customer and/or End User
agree to indemnify and hold harmless Avaya, Avaya's agents, servants and
employees against all claims, lawsuits, demands and judgments arising out of,
or in connection with, subsequent modifications, additions or deletions to this
documentation to the extent made by the Customer or End User.
Link disclaimer
Avaya Inc. is not responsible for the contents or reliability of any linked Web
sites referenced elsewhere within this documentation, and Avaya does not
necessarily endorse the products, services, or information described or offered
within them. We cannot guarantee that these links will work all of the time and
we have no control over the availability of the linked pages.
Warranty
Avaya Inc. provides a limited warranty on this product. Refer to your sales
agreement to establish the terms of the limited warranty. In addition, Avaya’s
standard warranty language, as well as information regarding support for this
product, while under warranty, is available through the following Web site:
http://www.avaya.com/support
Copyright
Except where expressly stated otherwise, the Product is protected by copyright
and other laws respecting proprietary rights. Unauthorized reproduction,
transfer, and or use can be a criminal, as well as a civil, offense under the
applicable law.
Avaya support
Avaya provides a telephone number for you to use to report problems or to ask
questions about your product. The support telephone number
is 1-800-242-2121 in the United States. For additional support telephone
numbers, see the Avaya Web site:
http://www.avaya.com/support
Contents
About this book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
21
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
21
Audience. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
22
How to use this Document. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
23
Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
23
Structure of the book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
24
Conventions used in this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
25
Useful terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
27
Related resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
28
Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
29
Safety labels and security alert labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
29
Safety precautions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
30
Downloading this book and updates from the Web . . . . . . . . . . . . . . . . . . . . . . . .
31
Technical assistance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
31
Sending us comments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
32
Chapter 1: Server Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
33
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
33
Alarm Classifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
34
Background Terms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
35
Alarm-Related LEDs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
36
Alarm Content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
36
QOS Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
37
Alarm Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
37
Connection Strategies to a Services Organization . . . . . . . . . . . . . . . . . . . . . . . .
37
Alarms in Linux Media Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
38
Clearing Media Server Alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
39
Displaying Media Server Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
39
Alarms on the S8300 Functioning as an LSP . . . . . . . . . . . . . . . . . . . . . . . . . . .
40
Communication Manager Hardware Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . .
40
ARB (Arbiter) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
43
DAJ1/DAL1/DAL2 (Duplication Memory Board) . . . . . . . . . . . . . . . . . . . . . . . . . .
54
DUP (Duplication Manager) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
61
ENV (Environment) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
66
FSY (File Synchronization) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
79
GAM (Global Alarm Manager) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
80
Issue 3 February 2007
3
Contents
HARD DISK (Hard Disk Drive) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
81
Login Alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
86
_MP (Maintenance Processor) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
87
NIC (Network Interface Card) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
88
RMB (Remote Maintenance Board) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
89
SME (Server Maintenance Engine) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
94
STD (Standard SNMP Traps) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
95
SVC_MON (Service Monitor) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
96
_TM (Translation Manager) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
104
UPG (Upgrade) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
105
UPS (Uninterruptible Power Supply) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
106
USB1 (Modem) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
112
_WD (Watchdog) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
117
Login Alarms - S8300 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
134
S8710 Alarms
135
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 2: Denial Events
Event Type number ranges
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
139
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
140
Event Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
141
Denial Event Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
191
Chapter 3: LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
281
Alarm levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
282
Terminal alarm notification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
282
Attendant Console LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
283
Circuit Pack LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
283
Avaya Ethernet Switch LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
299
UPS LEDs
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
300
IPSI LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
301
650A Power supply LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
304
655A Power Supply LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
305
Duplication Memory Board LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
306
S8300 Media Server LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
309
S8500 Media Server LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
314
S8700 Media Server LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
315
S8710 Media Server LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
317
G250/G350 and Media Module LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
321
4 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Contents
Front panel LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
322
Media Module LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
325
G700 and Media Module LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
334
Chapter 4: Media Gateway Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
345
Alarm Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
345
SNMP Alarming on the Media Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
346
Configure the Media Gateway to send SNMP traps . . . . . . . . . . . . . . . . . . . . . . . .
347
G250/G350 Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
348
G700 Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
367
Chapter 5: Communication Manager Maintenance Object Repair Procedures . . . .
391
Displaying MOs Maintained by Communication Manager . . . . . . . . . . . . . . . . . . . . .
392
MO groupings by Media Module type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
394
Viewing Communication Manager Alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
395
Command Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
395
Abort Code 1412 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
396
Escalation Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
396
EPN Angel Address/Slot Mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
397
ABRI-POR (ASAI ISDN-BRI Port) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
399
AC-POWER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
400
AC-POWER for DC-Powered Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
403
ADJ-IP (ASAI Adjunct TCP/IP Link) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
405
ADM-CONN (Administered Connection) . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
407
ADX8D-BD (AUDIX Circuit Pack) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
410
ADX8D-PT (AUDIX Digital Port) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
411
ADX8D-RS (AUDIX Reserve Slots) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
414
ADX16A-B (AUDIX Circuit Pack) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
415
ADX16A-P (AUDIX Analog Line/Control Link). . . . . . . . . . . . . . . . . . . . . . . . . . .
416
ADX16D-B (16-Port AUDIX Circuit Pack) . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
419
ADX16D-P (16-Port AUDIX Digital Port) . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
420
AESV-LNK (AE Services Link) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
424
AESV-SES (AE Services Session) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
427
ALARM-PT (Alarm Port) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
429
AN-LN-PT (Analog Line Port) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
431
ANL-16-L (16-Port Analog Line) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
435
ANL-BD (Analog Line Circuit Pack) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
439
Issue 3 February 2007
5
Contents
ANL-LINE (8-Port Analog Line) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
440
ANL-NE-L (8-Port Analog Line) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
443
ANN-BD (Announcement circuit pack) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
444
ANN-PT (Announcement Port) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
453
ANNOUNCE (Announcement) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
456
ASAI-ADJ (ASAI Adjunct) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
459
ASAI-BD (Multi-Application Platform Board) . . . . . . . . . . . . . . . . . . . . . . . . . . .
460
ASAI-EPT (ASAI Endpoint) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
462
ASAI-PT (ASAI Port) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
469
ASAI-RES (TN800 reserve slot) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
473
ATM-BCH (ATM B-Channel Trunk) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
474
ATM-DCH (ATM D-Channel Port) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
481
ATM-EI (Expansion Interface Circuit Pack) . . . . . . . . . . . . . . . . . . . . . . . . . . . .
483
ATM-INTF (ATM Interface) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
503
ATM-NTWK (ATM Network Error) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
505
ATM PNC-DUP (ATM PNC Duplication). . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
516
ATM-SGRP (ATM Signaling Group) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
527
ATM-SYNC (ATM Synchronization) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
535
ATM-TRK (Circuit Emulation Service Circuit Pack) . . . . . . . . . . . . . . . . . . . . . . . .
541
ATT-ADJ (Avaya Adjunct) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
555
ATTE-AJ (Ethernet Avaya Adjunct) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
556
AUX-BD (Auxiliary Trunk Circuit Pack) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
557
AUX-TRK (Auxiliary Trunk) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
558
AXA12-BD (AUDIX Circuit Pack) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
562
AXA12-RS (AUDIX Reserve Slots) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
563
AXD12-RS (AUDIX Reserve Slots) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
565
BRI-BD (ISDN-BRI Line Circuit Pack) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
566
BRI-DAT (ISDN-BRI Data Module) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
571
BRI-PORT (ISDN-BRI Port) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
572
BRI-SET, Various Adjuncts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
579
CAB-CALM (Customer alarm) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
592
CAB-EXFR (Emergency Transfer). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
593
CAB-MTCE (Media Gateway Maintenance). . . . . . . . . . . . . . . . . . . . . . . . . . . .
595
CAB-PFL (Power Fan Lead). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
598
CAB-TEMP (Cabinet Temperature) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
600
CABINET (Cabinet Sensors) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
602
6 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Contents
CARR-POW (Carrier Power Supply) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
608
CDR-LNK (Call Detail Recording Link) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
620
CLAN-BD (Control LAN Circuit Pack) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
621
CLSFY-BD (Call Classifier Circuit Pack). . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
630
CLSFY-PT (Call Classifier Port) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
631
CO-BD (Central Office Trunk Circuit Pack) . . . . . . . . . . . . . . . . . . . . . . . . . . . .
633
CO-DS1 (DS1 CO Trunk) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
634
CO-TRK (Analog CO Trunk). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
638
CONFIG (System Configuration) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
646
CUST-ALM (Customer-Provided Alarming Device) . . . . . . . . . . . . . . . . . . . . . . . .
652
DAT-LINE (Data Line Port) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
653
DC-POWER (Single-Carrier Cabinet Environment) . . . . . . . . . . . . . . . . . . . . . . . .
656
DETR-BD (Tone Detector Circuit) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
658
DID-BD (Direct Inward Dial Trunk Circuit Pack) . . . . . . . . . . . . . . . . . . . . . . . . . .
659
DID-DS1 (Direct Inward Dial Trunk) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
660
DID-TRK (Direct Inward Dial Trunk) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
664
DIG-BD (Digital Line Circuit Pack). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
669
DIG-IP-S (Digital IP Station) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
670
DIG-LINE (Digital Line) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
673
DIG-RES (TN800 reserve slot) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
685
DIOD-BD (DIOD Trunk Circuit Pack) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
686
DIOD-DS1 (DS1 DIOD Trunk) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
687
DIOD-TRK (DIOD Trunk) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
692
DLY-MTCE (Daily Maintenance). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
696
DS1-BD (DS1 Interface Circuit Pack) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
699
DS1-FAC (DS1 Facility) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
710
DS1C-BD (DS1 Converter Circuit Pack) . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
727
DT-LN-BD (Data Line Circuit Pack) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
752
DTMR-PT (Dual-Tone Multifrequency Receiver Port) . . . . . . . . . . . . . . . . . . . . . . .
753
E-DIG-BD (Multi Application Platform Board)
. . . . . . . . . . . . . . . . . . . . . . . . . .
756
E-DIG-ST (Emulated Digital Line) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
757
EMG-XFER (Emergency Transfer) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
760
EPN-SNTY (PN Sanity Audit) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
764
ERR-LOG (Error Log) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
766
ESS (Enterprise Survivable Server)
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
767
ETH-PT (Control LAN Ethernet) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
773
Issue 3 February 2007
7
Contents
ETR-PT (Enhanced Tone Receiver Port) . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
777
EXP-INTF (Expansion Interface Circuit Pack) . . . . . . . . . . . . . . . . . . . . . . . . . . .
781
EXP-PN (Expansion Port Network) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
806
EXT-DEV (External Device Alarm) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
810
EXT-DEV ADMIN? N (External Device Alarm) . . . . . . . . . . . . . . . . . . . . . . . . . .
812
EXT-DEV ADMIN? Y (External Device Alarm) . . . . . . . . . . . . . . . . . . . . . . . . . .
814
FIBER-LK (Fiber Link) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
816
FW-DWNLD (Firmware Download) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
823
FW-STDL (Firmware Station Download) . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
833
GPTD-PT (General-Purpose Tone Detector Port) . . . . . . . . . . . . . . . . . . . . . . . . .
843
H323-BCH (H.323 B Channel) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
845
H323-SGR (H.323 Signaling Group) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
847
H323-STN (H.323 IP Station) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
854
HYB-BD (Hybrid Line Circuit Pack) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
856
HYB-LINE (Hybrid Line) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
857
INADS (INADS Link). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
861
IPMEDPRO (IP Media Processor). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
865
IPMEDPRO (TN2302 IP Media Processor) . . . . . . . . . . . . . . . . . . . . . . . . . . . .
866
IPMEDPRO (TN2602AP IP Media Resource 320) . . . . . . . . . . . . . . . . . . . . . . . .
872
IPSV-CTL (IP Server Interface Control) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
879
IP-SVR (IP Server Interface) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
889
ISDN-PLK (ISDN-PRI Signaling Link Port) . . . . . . . . . . . . . . . . . . . . . . . . . . . .
898
ISDN-SGR (ISDN-PRI Signaling Group) . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
902
ISDN-TRK (DS1 ISDN Trunk) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
910
JNL-PRNT (Journal Printer Link) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
921
LGATE-AJ (Ethernet ASAI Endpoint) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
922
LGATE-BD (ISDN-BRI Line Circuit Pack) . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
923
LGATE-PT (Ethernet Adjunct Port) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
924
LIC-ERR (License Error Mode) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
925
LOG-SVN (Login Security Violation) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
933
MAINT (PN Maintenance Circuit Pack) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
935
MAPD-BD (MAPD Interface Circuit Pack) . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
940
MEDPRO (Media Processor MAPD Circuit Pack). . . . . . . . . . . . . . . . . . . . . . . . .
961
MEDPRO-C (Media Processor Control) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
965
MEDPROPT (MEDPRO DSP PORT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
969
MED-GTWY (MEDIA GATEWAY) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
972
8 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Contents
MET-BD (MET Line Circuit Pack) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
974
MET-LINE (MET Line) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
975
MG-ANA (Analog Media Module) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
979
MG-ANN (Voice Announcements) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
982
MG-BRI (BRI Trunk Media Module) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
983
MG-DCP (Digital Line Media Module) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
986
MG-DS1 (DS1 Interface Media Module). . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
989
MG-IAMM (Integrated Analog Media Module). . . . . . . . . . . . . . . . . . . . . . . . . . .
996
MG-VOIP (MM760 VoIP Media Module) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1000
MIS (Management Information System). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1001
MMI-BD (Multimedia Interface Circuit Pack) . . . . . . . . . . . . . . . . . . . . . . . . . . . 1002
MMI-LEV (Multimedia Interface Resource Level) . . . . . . . . . . . . . . . . . . . . . . . . . 1007
MMI-PT (Multimedia Interface Port) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1010
MMI-SYNC (MMI Synchronization) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1014
MODEM-BD (Modem Pool Circuit Pack) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1016
MODEM-PT (Modem Pool Port) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1017
M/T-ANL (Maintenance/Test Analog Port) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1023
M/T-BD (Maintenance/Test Circuit Pack) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1026
M/T-DIG (Maintenance/Test Digital Port) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1030
M/T-PKT (Maintenance/Test Packet Bus Port) . . . . . . . . . . . . . . . . . . . . . . . . . . 1034
NO-LIC (No License) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1037
NR-CONN (Network-Region Connect) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1041
NR-REG (Network Region Registrations) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1043
OPS-LINE (DS1 Off-Premises Station Line). . . . . . . . . . . . . . . . . . . . . . . . . . . . 1045
PDMODULE (Processor Data Module) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1048
PE-BCHL (PRI Endpoint Port) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1056
PKT-BUS (Packet Bus) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1065
PKT-INT (Packet Interface) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1070
PLAT-ALM (Platform Alarms) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1089
PMS-LINK (Property Management System Link) . . . . . . . . . . . . . . . . . . . . . . . . . 1090
PMS-PRNT (PMS Printer Link) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1096
PNC-DUP (PNC Duplication) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1100
POWER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1118
POW-SUP (Power Supply) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1124
PPP-PT (Control LAN Packet/Port) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1129
PRI-CDR (Call Detail Recording Link) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1133
Issue 3 February 2007
9
Contents
PROC-SAN (Process Sanity Audits) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1137
PS-RGEN (Power Supply Ring Generator) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1138
RANL-STA (Remote Analog Line (Station) Port) . . . . . . . . . . . . . . . . . . . . . . . . . 1141
RDIG-STA (Remote Digital Station) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1144
REM-OFF (Remote Office) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1152
RING-GEN (Analog Ring Generator) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1154
RMC-ENV (Power/Fan Sensors) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1156
S-SYN-BD (Speech Synthesis Circuit Pack) . . . . . . . . . . . . . . . . . . . . . . . . . . . 1159
S-SYN-PT (Speech Synthesis Port) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1160
SEC-CDR (Call Detail Recording Link) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1163
SER-BUS (Serial Communication Bus) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1164
SIP-BCH (SIP B Channel) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1170
SIP-SGRP (SIP Signaling Group) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1172
SN-CONF (Switch Node Configuration) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1180
SNC-BD (Switch Node Clock Circuit Pack) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1184
SNC-LINK (Switch Node Clock Link) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1192
SNC-REF (Switch Node Clock Reference) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1196
SNI-BD (SNI Circuit Pack). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1199
SNI-PEER (SNI Peer Link) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1213
SP-REG-M (Survivable Processor-Main) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1217
SP-REG-S (Survivable Processor) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1219
STRAT-3 (Stratum-3 Clock) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1221
SVC-SLOT (Service Slot) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1229
SYNC (Port Network Synchronization) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1231
SYS-LINK (System Links) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1262
SYS-PRNT (System Printer) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1267
SYSTEM (System) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1270
S8400-BD (S8400 Media Server) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1272
TBRI-BD (ISDN Trunk-Side BRI Circuit Pack). . . . . . . . . . . . . . . . . . . . . . . . . . . 1274
TBRI-PT (ISDN Trunk-Side BRI Port) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1279
TBRI-TRK (ISDN Trunk-Side BRI Channel) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1285
TDM-BUS (TDM Bus) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1288
TDM-CLK (TDM Bus Clock) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1300
TDMODULE (Trunk Data Module). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1307
TIE-BD (Tie Trunk Circuit Pack) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1308
TIE-DS1 (DS1 Tie Trunk) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1309
10 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Contents
TIE-TRK (Analog Tie Trunk) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1315
TIME-DAY (Time of Day) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1321
TONE-BD (Tone-Clock Circuit Pack) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1322
TONE-PT (Tone Generator) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1346
TR-LN-BD (Analog Trunk/Line Board). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1350
TSC-ADM (Administered Temporary Signaling Connections) . . . . . . . . . . . . . . . . . . . 1351
TTR-LEV (TTR Level) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1353
UDS1-BD (UDS1 Interface Circuit Pack) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1357
VAL-BD (Voice Announcements over LAN Circuit Pack) . . . . . . . . . . . . . . . . . . . . . 1376
VAL-PT (Voice Announcements over LAN Packet/Port). . . . . . . . . . . . . . . . . . . . . . 1391
VC-BD (Voice Conditioner Circuit Pack). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1394
VC-DSPPT (Voice Conditioner DSP Port) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1397
VC-LEV (Voice Conditioner Resource Level) . . . . . . . . . . . . . . . . . . . . . . . . . . . 1399
VC-SUMPT (Voice Conditioner Summer Port) . . . . . . . . . . . . . . . . . . . . . . . . . . 1402
WAE-PORT (Wideband Access Endpoint Port) . . . . . . . . . . . . . . . . . . . . . . . . . . 1404
XXX-BD (Common Port Circuit Pack/Media Module) . . . . . . . . . . . . . . . . . . . . . . . 1407
Chapter 6: Maintenance Demand Tests . . . . . . . . . . . . . . . . . . . . . . . . .
1413
Dial Tone Test (#0). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1413
CO Port Diagnostic Test (#3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1417
Battery and Power Supply Query Test (#5) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1420
NPE Crosstalk Test (#6) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1426
Conference Circuit Test (#7). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1434
GPP NPE Crosstalk Test (#9) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1440
Digital Line Electronic Power Feed Test (#11) . . . . . . . . . . . . . . . . . . . . . . . . . . . 1447
Local Loop Test (#13) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1449
Digital Station Lamp Update (#16). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1457
Digital Station Audits Test (#17) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1459
Looparound and Conference Test (#33). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1462
Port Diagnostic Test (#35) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1466
Port Audit And Update Test (#36) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1471
Tone Generator Transmission Test (#40) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1475
Tone Generator Update/Audit Test (#41) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1478
Tone Detection Verification Test (#42) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1479
Tone Detector Audit/Update Test (#43) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1483
Clock Health Inquiry Test (#46) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1485
Issue 3 February 2007
11
Contents
Looparound and Conference Test (#47). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1486
ONS Ringer Application Test (#48) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1492
NPE Audit Test (#50) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1495
Ringing Application Test (#51). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1496
Control Channel Looparound Test (#52) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1498
SAKI Sanity Test (#53) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1499
Analog Electronic Power Feed (#56) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1500
Hybrid Circuit and Conference Circuit Test (#57) . . . . . . . . . . . . . . . . . . . . . . . . . 1502
Hybrid Line Local Digital Looparound Test (#58) . . . . . . . . . . . . . . . . . . . . . . . . . 1505
Hybrid Line Remote Digital Looparound Test (#59) . . . . . . . . . . . . . . . . . . . . . . . . 1507
Analog Line Station Lamp Update Test (#60) . . . . . . . . . . . . . . . . . . . . . . . . . . . 1509
Analog Line Audits Test (#61) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1510
Analog Line Ringer Update Test (#62) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1512
Tie Trunk Seizure Test (#73) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1513
Tie Trunk EPF Test (#74) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1516
RMC Power/Fan Query Test (#77) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1518
AC Power Query Test (#78) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1521
Single-Carrier Cabinet Power Query Test (#79) . . . . . . . . . . . . . . . . . . . . . . . . . . 1524
Tone Generator Crosstalk Test (#90) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1526
Modem Pool NPE Crosstalk Test (#96) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1527
Modem Pool Conference Test (#97). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1530
Modem Pool Conversion Resource Looparound Test (#98). . . . . . . . . . . . . . . . . . . . 1533
Modem Pool Audit Test (#99) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1538
Sanity Handshake Test (#106) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1539
Auxiliary Trunk Diagnostic Test (#114) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1541
Customer-Provided Alarming Device Test (#115) . . . . . . . . . . . . . . . . . . . . . . . . . 1542
Ring Generator Initialization Test (#117) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1544
Ring Generator Query Test (#118) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1545
External Device Alarm Query Test (#120) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1549
Cabinet Temperature Query Test (#122) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1551
Emergency Transfer Query Test (#124) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1556
OLS Recycle Test (#126) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1559
OLS/Power Unit Query Test (#127) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1560
Internal Looparound Test (#135) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1564
DS1 Tie Trunk Seizure Test (#136) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1568
Loss of Signal Alarm Inquiry Test (#138) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1571
12 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Contents
Blue Alarm Inquiry Test (#139) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1579
Red Alarm Inquiry Test (#140). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1581
Yellow Alarm Inquiry Test (#141) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1582
Major Alarm Inquiry Test (#142) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1584
Minor Alarm Inquiry Test (#143) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1585
Slip Alarm Inquiry Test (#144) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1587
Misframe Alarm Inquiry Test (#145) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1588
Translation Update Test (#146) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1589
TDM bus Clock Circuit Status Inquiry Test (#148) . . . . . . . . . . . . . . . . . . . . . . . . . 1590
TDM Bus Clock Slip Inquiry Test (#149). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1593
TDM Bus Clock PPM Inquiry Test (#150) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1595
TDM Bus Clock Parameter Update Test (#151) . . . . . . . . . . . . . . . . . . . . . . . . . . 1596
Analog Looparound Test (#161) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1597
Speech Synthesis DTMF Receiver Test (#163) . . . . . . . . . . . . . . . . . . . . . . . . . . 1600
Speech Synthesis DTMF Sanity Inquiry (#164) . . . . . . . . . . . . . . . . . . . . . . . . . . 1601
Speech Synthesis DSP Tone Test (#165) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1601
Speech Synthesis Memory Test (#166) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1603
Speech Synthesis SSD Inquiry Test (#167) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1604
Speech Synthesis PSS Handshake Test (#168). . . . . . . . . . . . . . . . . . . . . . . . . . 1605
Speech Synthesis Parameter Update Test (#169). . . . . . . . . . . . . . . . . . . . . . . . . 1606
Digital Looparound Test (#171) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1606
Data Module Internal Looparound Test (#175) . . . . . . . . . . . . . . . . . . . . . . . . . . 1610
Channel Administration Memory Array Test (#205) . . . . . . . . . . . . . . . . . . . . . . . . 1615
Playback Speech Memory Array Test (#206) . . . . . . . . . . . . . . . . . . . . . . . . . . . 1616
Angel Speech Processor Handshake Test (#208) . . . . . . . . . . . . . . . . . . . . . . . . . 1619
Announcement Checksum Test (#209) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1621
140AY Looparound Test (#210) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1625
Super Frame Match Inquiry Test (#211) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1628
Clock Match Inquiry Test (#212) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1629
Link Tear Down Test (#213) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1631
Link Retry Test (#215) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1632
Neon Test (#220) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1634
140AY Channel Sanity Inquiry Test (#222) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1636
MTP SAT Channel Local Looparound Test (#228) . . . . . . . . . . . . . . . . . . . . . . . . 1637
Serial Channel Local Looparound Test (#229) . . . . . . . . . . . . . . . . . . . . . . . . . . 1639
Expansion Interface Neighbor Query Test (#237) . . . . . . . . . . . . . . . . . . . . . . . . . 1641
Issue 3 February 2007
13
Contents
Expansion Interface Fiber Out-of-Frame Query Test (#238) . . . . . . . . . . . . . . . . . . . 1642
Expansion Interface Local Looparound (#240) . . . . . . . . . . . . . . . . . . . . . . . . . . 1644
Expansion Interface 2-Way Transmission Test (#241) . . . . . . . . . . . . . . . . . . . . . . 1647
Expansion Interface Lightwave Transceiver Looparound Test (#242) . . . . . . . . . . . . . . . 1653
Circuit Pack Restart Test (#252) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1660
Signaling Link State Audit Test (#255). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1661
Service State Audit Test (#256) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1663
Call State Audit Test (#257) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1666
ISDN Test Call Test (#258) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1667
Clear Error Counters (#270) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1674
Idle Time Slot Test (#294) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1675
Control Channel Test (#296). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1676
Non-control Channel Test (#297) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1677
PN Maintenance Circuit Pack
Sanity Maze Test (#303) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1678
Expansion Interface Lock Query Test (#304) . . . . . . . . . . . . . . . . . . . . . . . . . . . 1679
PN Maintenance Circuit Pack Reset Test (#306) . . . . . . . . . . . . . . . . . . . . . . . . . 1680
Battery Holdover Hardware Verification Test (#311) . . . . . . . . . . . . . . . . . . . . . . . . 1683
DS1 OPS Switchhook Inquiry Test (#312). . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1684
DS1 CO Trunk Dial Tone Seizure Test (#314) . . . . . . . . . . . . . . . . . . . . . . . . . . . 1685
Expansion Interface Control Channel Test (#316) . . . . . . . . . . . . . . . . . . . . . . . . . 1689
Expansion Interface Reset Test (#336) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1690
PN Maintenance Circuit Pack Serial Link Test (#337) . . . . . . . . . . . . . . . . . . . . . . . 1694
Synchronization Update Test (#417) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1696
Digital Port Sanity Test (#565) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1696
Hook State Inquiry Test (#566) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1699
Packet Bus Port Health Inquiry Test (#567) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1700
Maintenance/Test Circuit Pack Query Test (#572) . . . . . . . . . . . . . . . . . . . . . . . . 1701
Packet Circuit Pack Audit Test (#573) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1704
Board Type Check Test (#574) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1705
Expansion Interface Packet Interface Test (#589) . . . . . . . . . . . . . . . . . . . . . . . . . 1706
Circuit Pack Restart Test (#594) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1714
LANBIC Receive Parity Error Counter Test (#595) . . . . . . . . . . . . . . . . . . . . . . . . 1715
Receive FIFO Overflow Error Counter Test (#596) . . . . . . . . . . . . . . . . . . . . . . . . 1716
Invalid LAPD Frame Error Counter Test (#597) . . . . . . . . . . . . . . . . . . . . . . . . . . 1717
Packet Interface Test (#598). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1718
14 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Contents
Congestion Query Test (#600). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1719
Link Status Test (#601) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1721
TSC Heartbeat Inquiry Test (#604) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1722
BRI NPE Crosstalk Test (#617) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1726
BRI Port Local LAN Looparound Test (#618) . . . . . . . . . . . . . . . . . . . . . . . . . . . 1727
BRI Port Local TDM Looparound Test (#619) . . . . . . . . . . . . . . . . . . . . . . . . . . . 1729
Electronic Power Feed Restoral Test (#620) . . . . . . . . . . . . . . . . . . . . . . . . . . . 1732
Level 1 Status Inquiry Test (#621) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1733
Electronic Power Feed Inquiry (#622) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1737
CRC Error Counter Test (#623) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1738
Layer 1 Transmission Error Counter Test (#624) . . . . . . . . . . . . . . . . . . . . . . . . . 1739
Receive FIFO Error Counter Test (#625) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1740
Signaling Link Status Test (#626) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1741
BRI Remote Loopback Test (#627) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1743
BRI XID Test (#628) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1747
BRI Layer 3 Query Test (#629) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1749
BRI Set Audits Test (#630) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1753
Primary Signaling Link Hardware Check (#636). . . . . . . . . . . . . . . . . . . . . . . . . . 1755
Remote Layer 3 Query (#637). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1756
Secondary Signaling Link Hardware Check (#639) . . . . . . . . . . . . . . . . . . . . . . . . 1759
Signaling Link Board Check (#643) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1760
Layer 2 Status Test (#647). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1761
Stratum-3 Clock Alarm Query (#649) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1764
Standby Reference Health Check Test (#651) . . . . . . . . . . . . . . . . . . . . . . . . . . 1769
Tie Trunk Dial Test (#747) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1770
SNI Circuit Path Test (#755) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1772
SNI Destructive Facility Off-Board Test (#756) . . . . . . . . . . . . . . . . . . . . . . . . . . 1776
SNI Destructive Facility On-board Test (#757) . . . . . . . . . . . . . . . . . . . . . . . . . . 1779
Configuration Audit (#759). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1781
Processor Route Audit Test (#760) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1804
Switch Node Interface Reset Test (#761) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1806
Packet Neighbor Link Test (#767) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1809
Fiber Link Reset Test (#768) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1814
Failure Audit (#777) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1815
SNC On-Board Test (#778) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1817
TPN Test (#779) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1820
Issue 3 February 2007
15
Contents
Switch Node Clock Reset Test (#780) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1822
Reset Test (#787) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1825
Far-End DS1 Converter Circuit Pack
Loopback Test (#788) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1826
Far-End Lightwave Transceiver
Loopback Test (#789) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1829
DS1 Facilities Connectivity Test (#790) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1832
DS1C Board Options Administration (#795). . . . . . . . . . . . . . . . . . . . . . . . . . . . 1835
Far-End Internal Loopback Test (#797) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1837
DS1 Interface Options Audit Test (#798) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1840
Near-End External Loopback Test (#799) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1841
Automatic Transmission Test (#844-848) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1843
Packet Interface Memory Checksum Test (#884) . . . . . . . . . . . . . . . . . . . . . . . . . 1848
Packet Interface Private Looparound Test (#885) . . . . . . . . . . . . . . . . . . . . . . . . . 1851
Packet Interface Maintenance Looparound Test (#886) . . . . . . . . . . . . . . . . . . . . . . 1854
Packet Interface Read and Clear Counters (#887) . . . . . . . . . . . . . . . . . . . . . . . . 1858
Active-Standby Peer Link Test (#888) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1862
Packet Interface Reset Test (#889) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1864
Signaling Port LAN Loopback Test (#939). . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1866
Failure Audit Test (#949) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1868
PN Cold Restart Test (#955). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1869
PN Warm Restart Test (#956) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1870
Analog Port Sanity Test (#963) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1871
SNI Sanity Timer Test (#964) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1872
System Link Status (#985). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1873
SNI Fiber Out of Frame Query Test (#989) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1874
VC Summer Port Local TDM Looparound Test (#1100) . . . . . . . . . . . . . . . . . . . . . . 1882
VC DSP Port NPE Crosstalk Test (#1103). . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1885
VC DSP Port Local TDM Loopback Test (#1104) . . . . . . . . . . . . . . . . . . . . . . . . . 1886
VC DSP Port DSP Looparound Test (#1105) . . . . . . . . . . . . . . . . . . . . . . . . . . . 1889
VC Port Reset DSP Test (#1106) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1891
TSI Looparound Test (#1108) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1892
Resource Looparound Test (#1111) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1893
MMI Synchronization Status Test (#1122) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1895
MMI Update Synchronization Status Test (#1123). . . . . . . . . . . . . . . . . . . . . . . . . 1896
Digital Terminal Remote Looparound Test (#1201) . . . . . . . . . . . . . . . . . . . . . . . . 1898
16 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Contents
DS1 Board Loopback Test (#1209) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1901
CSU Equipment Loopback Test (#1210) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1903
CSU Repeater Loopback Test (#1211) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1905
CPE Loopback Jack Test (#1212) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1908
Far CSU Loopback Test (#1213) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1911
One-Way Span Test (#1214) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1913
Inject Single Bit Error Test (#1215) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1916
End Loopback/Span Test (#1216) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1917
ICSU Status LEDs Test (#1227) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1919
Level 1 Status Query Test (#1242) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1920
BRI Layer 3 Query Test (#1243). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1923
BRI Port Slip Query Test (#1244) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1924
Signaling Link State (#1251). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1925
ATM Board Reset (#1256) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1926
ATM Board Error Query Test (#1259) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1929
ATM Board Framer Looparound Test (#1260) . . . . . . . . . . . . . . . . . . . . . . . . . . . 1932
ATM Board Time Of Day Update (#1261) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1938
SCOTCH Synchronous Looparound Test (#1275) . . . . . . . . . . . . . . . . . . . . . . . . 1938
Ethernet Local Looparound Test (#1278) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1940
PPP Link Status Inquiry Test (#1279) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1941
TCP/IP Ping Test (#1281) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1942
Link Integrity Inquiry Test (#1282) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1945
TDM Looparound Test (#1285) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1946
Session Status Test (#1286). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1948
ATM Remote Layer 3 Query (#1291) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1950
ATM Board DSP Test (#1293) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1951
ATM Crosstalk Test (#1298) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1954
ASAI Link Status Test (#1365). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1956
IP Address Update Test (#1371) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1957
Registration Status Inquiry Test (#1372). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1959
Signaling Path PING Test (#1373). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1960
Media Path PING Test (#1374) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1961
Ping Test (#1379) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1962
DSP Port TDM Looparound Test (#1380) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1964
Windows 2000 Reset Test (#1381) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1966
DSP Query Test (#1382) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1967
Issue 3 February 2007
17
Contents
Network Connectivity Query Test (#1383) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1968
C-LAN Ethernet Port Status Test (#1386) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1969
Signaling Group Ping Test (#1387) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1971
MedPro Status Test (#1392) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1973
PPC Sanity Query Test (#1402) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1974
Ethernet Hardware Query Test (#1405) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1975
MP Diagnostic Test (#1406) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1977
DSP Port Status Query Test (#1407) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1978
Firmware Download Test (#1413) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1979
Network Region Interconnectivity Test (#1417) . . . . . . . . . . . . . . . . . . . . . . . . . . 1982
Echo Canceller Test (#1420) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1984
Short IP 2-Way Transmission Test (#1505) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1986
Long IP 2-Way Transmission Test (#1506) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1989
Verify NIC Options Test (#1511) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1992
Link State Audit Test (#1527) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1995
Serial Bus Status Test (#1531) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1996
Emergency Transfer Query Test (#1532) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2000
Power/Fan Lead Query Test (#1533) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2003
Power Supply Recycle Test (#1534). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2006
Power Supply Detection Test (#1535) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2008
Power Supply Voltage Test (#1536) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2012
Power Supply Temperature Test (#1537) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2015
Power Supply Fan Test (#1538) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2017
Ring Generator Interchange Test (#1539) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2018
Ring Generator Status Test (#1540) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2020
Reset Environmental Maintenance Test (#1545) . . . . . . . . . . . . . . . . . . . . . . . . . 2022
Correct Board Test (#1546) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2023
Sanity Test (#1547) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2024
AESVCS Session Level Link Status Test (#1623) . . . . . . . . . . . . . . . . . . . . . . . . . 2025
AESVCS Link Heartbeat Test (#1624). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2025
Aggregator Hardware Query (#1629) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2026
Packet Count Query Test (#1630) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2027
System Link Status (#1647) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2029
Power Supply Aux Signal Test (#1649) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2030
Board Health Query Test (#1652) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2031
Media Gateway Hyperactivity Audit Test (#1659) . . . . . . . . . . . . . . . . . . . . . . . . . 2033
18 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Contents
H.323 Signaling Layer 3 Test (#1673) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2033
IP Signaling Group Far-End Status Test (#1675) . . . . . . . . . . . . . . . . . . . . . . . . . 2034
NO BOARD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2035
Hyperactive DS1/UDS1 Interface
Circuit Pack/Media Module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2036
Repair Procedures for DS1/UDS1
Circuit Pack/Media Module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2037
Index
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2039
Issue 3 February 2007
19
Contents
20 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
About this book
Overview
This document provides procedures to monitor, test, and maintain an Avaya Media Server or
Gateway system. It covers many of the faults and troubles that can occur and provides
procedures to correct them.
Using this documentation, the Avaya technicians and the technicians of their business partners
and customers should be able to follow detailed procedures for:
●
●
●
Monitoring, testing, and maintaining an Avaya Media Server, Media Gateway, and many
other system components.
Using troubleshooting methods to clear faults.
Required replacements, visual inspections, continuity checks, and clarifying operating
procedures with end users.
Document set
Although this maintenance book is published separately, it is part of a set:
●
Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and
Servers, 03-300430 (formerly 03-300190, 555-245-102)
●
Maintenance Commands for Avaya Communication Manager 4.0, Media Gateways and
Servers, 03-300431 (formerly 03-300191, 555-245-101)
●
Maintenance Procedures for Avaya Communication Manager 4.0, Media Gateways and
Servers, 03-300432 (formerly 03-300192, 555-245-103)
Equipment/platforms
This book contains information about the following equipment/platforms
●
Avaya S8700/S8710/S8720 Media Servers
●
Avaya S8300 Media Servers
●
Avaya S8400 Media Servers
●
Avaya S8500 Media Servers
●
Avaya G700/G650/G600/MCC/SCC Media Gateways
Issue 3 February 2007
21
About this book
It does not contain information about
●
●
●
●
●
●
DEFINITY G3R (see 555-233-117: Maintenance for Avaya MultiVantage and DEFINITY
Server R)
DEFINITY CSI (see 555-233-119: Maintenance for Avaya MultiVantage and DEFINITY
Server CSI)
DEFINTIY SI (see 555-233-123: Maintenance for Avaya MultiVantage and DEFINITY
Server SI)
Avaya S8100 Media Server (see 555-233-149: Maintenance for the S8100 Media Server
with the Avaya G600 and CMC1 Media Gateways)
Avaya S8700 Media Servers with MCC1/SCC1 (see 555-233-143: Maintenance for the
Avaya S8700 Media Server with MCC1/SCC1 Media Gateways)
G150/G250/G350 Media Gateways (see 03-300438: Maintenance for the Avaya G250 and
the G350 Media Gateways)
Audience
The information in this book is intended for use by Avaya technicians, provisioning specialists,
business partners, and customers, specifically:
●
●
Trained Avaya technicians
A maintenance technician dispatched to a customer site in response to a trouble alarm or
a user trouble report
●
A maintenance technician located at a remote maintenance facility
●
The customer’s assigned maintenance technician
The technician is expected to have a working knowledge of telecommunications fundamentals
and of the particular Avaya Media Server and/or Media Gateway to the extent that the
procedures in this book can be performed, in most cases, without assistance.
This book is not intended to solve all levels of troubles. It is limited to troubles that can be solved
using:
●
The Alarm Log
●
The Error Log
●
Trouble-clearing procedures
●
Maintenance tests
●
Traditional troubleshooting methods
If the trouble still has not been resolved, it is the maintenance technician’s responsibility to
escalate the problem to a higher level of technical support. Escalation should conform to the
procedures in the Technical and Administration Escalation Plan.
22 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
How to use this Document
How to use this Document
Most maintenance sessions involve analyzing the Alarm and Error Logs to diagnose a trouble
source and replacing a component such as a circuit pack or media module. The information in
Chapter 5: Communication Manager Maintenance Object Repair Procedures of this reference
will generally suffice to address these needs. Certain complex elements of the system require a
more comprehensive approach. Special procedures for these elements appear in Chapter
4: General troubleshooting of Maintenance Procedures for Avaya Communication Manager 4.0,
Media Gateways and Servers (03-300432).
Note:
Note:
This document is designed to be read online and in paper format. Because of the
large volume of information, additional cross-references have been added to
make it easier to locate information when using the manual online.
Organization
Chapter 1: Server Alarms, contains information on alarms generated on various platforms,
including the S8300, S8400, S8500, and S8700 Series media servers. These alarms cover
such categories as process watchdog, environmental, login, translation monitoring, and power
supply alarms. Alarm identifications, levels, and resolutions are given.
Chapter 2: Denial Events, contains information about denial events that are generated by Avaya
Communication Manager. Denial events are displayed via the Events Report (display
events screen) of Avaya Communication Manager.
Chapter 3: LEDs, contains information on the definition and interpretation of LED indicators that
are found on various system components such as servers, gateways, circuit packs, and media
modules.
Chapter 4: Media Gateway Traps, contains information on traps that can occur on media
gateways. Trap identifications, alarm levels, trap descriptions, and recommended resolutions
are given.
Chapter 5: Communication Manager Maintenance Object Repair Procedures, contains specific
troubleshooting and repair instructions for every component in the system. The maintenance
objects are listed alphabetically by name as they appear in the Alarm and Error Logs. Under
each maintenance object appears a description of the object’s function, tables for interpreting
alarm and error logs, and instructions on how to use tests, commands, and replacements to
resolve associated problems.
Issue 3 February 2007
23
About this book
Structure of the book
This document includes new information developed for this release of Communication
Manager. It contains combined Maintenance Alarms information for:
●
S8300, S8400, S8500, and S8700 series media servers
●
MCC1, SCC1, and CMC1 media gateways
●
G600, G650, and G700 media gateways
In order to present maintenance information from all these sources side-by-side, marking
conventions delineate material specific to a particular source. The markers act on two levels:
●
Major and minor sections
●
Paragraphs or inline comments
Major and minor sections
At the Major and minor sections level, a ruled line delineates the beginning of a section of
material specific to the media server or gateway identified in bold. At the conclusion of the
section, another ruled line marks the end of the specific material and a return to common text.
For example, a section of material specific to the S8700 or S8500 media server would look like:
S8700 | S8710 | S8720 | S8500
1. If only 1 analog circuit pack in the system has this problem, replace the circuit pack.
2. If only analog circuit packs on a particular carrier have this error, the ringing generator
may not be connected to this carrier.
3. If analog circuit packs on many carriers have this error, it is probably a problem with the
ringing generator.
Such sections can occasionally extend for several pages.
Paragraphs or inline comments
At the paragraph level and for inline comments, the specific media server or gateway is
indicated by its bold name, and the parenthetical information follows immediately afterward. For
example, a paragraph insert for the S8700 and S8500 media servers might looks like:
1. If the Tone-Clock circuit is a slave clock, then the EI to which it is listening is providing a bad
timing source. Follow the diagnostic procedures specified for TDM-CLK Error Code 2305.
24 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Conventions used in this document
2. S8700 | S8710 | S8720 | S8500: If no problem can be found with the incoming synchronization
signal, replace the IPSI or Tone-Clock circuit pack. See Replacing the IPSI or Tone-Clock
Circuit Pack on page 1332.
In such cases, it is not necessary to delineate the beginning and end of the material.
An example of an inline comment might look like:
3. Error Type 1: There is a serial number mismatch between the hardware serial number and
installed license file (S8700 | S8710 | S8720 | S8500: there is a serial-number mismatch of the
reference IPSI and a subsequent License Error failure. S8300: there is a serial-number
mismatch of the G700 motherboard on which the serial number resides and a subsequent
License Error failure). This error is caused by the:
●
●
S8700 | S8710 | S8720 | S8500: Reference IPSI not responding
S8300: G700 motherboard not responding
Expiration of the 10-day timer
The system enters No-License mode.
It is hoped that, by these techniques, material specific to several different sources can be
combined and viewed side-by-side without confusion.
Conventions used in this document
Table 1: Typography used in this book describes the typographic conventions used in this
document.
Table 1: Typography used in this book 1 of 2
To represent . . .
SAT commands
This typeface and syntax
are shown as . . .
●
Bold for literals
●
Bold italic for variables
●
●
For example, . . .
refresh ip-route [all | location]
Square brackets [ ]
around optional
parameters
"Or" sign | between
exclusive choices
1 of 2
Issue 3 February 2007
25
About this book
Table 1: Typography used in this book 2 of 2
To represent . . .
SAT screen input
and output
Linux commands
This typeface and syntax
are shown as . . .
●
●
●
●
●
●
Linux output
Web interface
Constant width for
output (screen
displays and
messages)
Constant-width bold for
literals
●
Set the Save Translation field to
daily.
The message Command successfully
completed should appear.
testmodem [-s] | [-t arg]
Constant-width bold
italics for variables
Square brackets []
around optional
arguments
“Or” sign | between
exclusive choices
Constant width
●
Keys
Bold for input
For example, . . .
Bold for menu
selections, tabs,
buttons, and field
names
Right arrow > to
separate a sequence
of menu selections
Special font for keyboard
keys and SAT screen
clickable buttons
Linux returns the message
almdisplay 4: Unable to connect
to MultiVantage.
Select Alarms and Notification, the
appropriate alarm, and then click Clear.
Select Diagnostics > View System
Logs, then click Watchdog Logs.
Press Tab.
Click Next Page.
2 of 2
26 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Useful terms
Other conventions used in this book:
●
Physical dimensions are in English [Foot Pound Second (FPS)] units, followed by metric
[Centimeter Gram Second) (CGS)] units in parentheses.
Wire-gauge measurements are in AWG, followed by the diameter in millimeters in
parentheses.
●
Circuit-pack codes (such as TN790B or TN2182B) are shown with the minimum
acceptable alphabetic suffix (like the “B” in the code TN2182B).
Generally, an alphabetic suffix higher than that shown is also acceptable. However, not
every vintage of either the minimum suffix or a higher suffix code is necessarily acceptable.
Useful terms
Table 2: Terminology summary summarizes several of the terms used in this book and relates
them to former terminologies.
Table 2: Terminology summary
Present Terminology
Former Terminology
Communication Manager
DEFINITY
MultiVantage
Avaya Call Processing
S8300 Media Server
ICC, Internal Call Controller
S8700 Media Server (or
non-co-resident S8300)
ECC, External Call Controller
MGP, Media Gateway Processor
860T Processor
Layer 2 Switching Processor
P330 Stack Processor
Cajun Stack Processor
i960 Processor
Fiber-PNC
Multiconnect. This is an umbrella term for direct-connect,
CSS-connected, and ATM-connected PNC.
IP-PNC
IP-connect
Issue 3 February 2007
27
About this book
Related resources
Additional document resources lists additional documentation that is available from the Avaya
web site http:/support.avaya.com.
Table 3: Additional document resources 1 of 2
Document
Number
Using the Avaya Enterprise Survivable Servers (ESS) 03-300428
03-300428
Hardware Description and Reference for Avaya Communication Manager
555-245-207
555-245-207
Administrator Guide for Avaya Communication Manager, 03-300509
03-300509
Installation and Upgrades for the Avaya G700 Media Gateway and Avaya
S8300 Media Server 555-234-100
555-234-100
Maintenance Commands for Avaya Communication Manager 4.0, Media
Gateways and Servers (03-300431)
03-300431
Maintenance Procedures for Avaya Communication Manager 4.0, Media
Gateways and Servers (03-300432)
03-300432
User’s Guide for the Avaya P333T Stackable Switch Release 3.12
See web page
DEFINITY® AUDIX Maintenance, 585-300-110
585-300-110
DEFINITY® Communications System Network and Data Connectivity,
555-025-201
555-025-201
Installing and Operating a 120A Channel Service Unit with Avaya
Communication Manager (03-601508)
03-601508
DEFINITY® Communications System Generic 2.2 and Generic 3 V2 DS1/
CEPT1/ISDN-PRI Reference, 555-025-107
555-025-107
DEFINITY® Communications System Generic 1 and Generic 3i Wiring,
555-204-111
555-204-111
Maintenance for the Avaya S8700 Media Server with an Avaya SCC1 Media
Gateway or an Avaya MCC1 Media Gateway, 555-233-143
555-233-143
Avaya MultiVantage Solutions Installation and Maintenance for Survivable
Remote EPN, 555-233-121
555-233-121
Installing the Avaya S8700 Media Server with the Avaya G600 Media
Gateway, the Avaya MCC1 Media Gateway, or the Avaya SCC1 Media
Gateway (Library CD)
Library CD
1 of 2
28 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Trademarks
Table 3: Additional document resources 2 of 2
Document
Number
ATM Installation, Upgrades, and Administration using Avaya Communication
Manager, 555-233-124
555-233-124
Multiple Asynchronous Data Unit User Manual, 555-401-702
555-401-702
Administration for Network Connectivity for Avaya Communication Manager,
555-233-504
555-233-504
Site Preparation, Installation, and Operator’s Manual - See appropriate
manual for the UPS Model
See web page
Installing and Configuring the S8700 Series Media Server, 03-300145
03-300145
Installing the Avaya G650 Media Gateway, 03-300685
03-300685
Installing and Configuring the Avaya S8500 Media Server, 03-300143
03-300143
Job Aids for Field Replacements (FRUs) for the Avaya S8700 Series Media
Servers, 03-300530
03-300530
Job Aids for Field Replacements (FRUs) for the Avaya S8500 Media Server,
03-300529
03-300529
2 of 2
Trademarks
All trademarks identified by the ® or ™ are registered trademarks or trademarks, respectively,
of Avaya Inc. All other trademarks are the property of their respective owners.
Safety labels and security alert labels
Observe all caution, warning, and danger statements to help prevent loss of service, equipment
damage, personal injury, and security problems. This book uses the following safety labels and
security alert labels:
! CAUTION:
CAUTION:
A caution statement calls attention to a situation that can result in harm to
software, loss of data, or an interruption in service.
Issue 3 February 2007
29
About this book
!
WARNING:
!
DANGER:
!
SECURITY ALERT:
WARNING:
A warning statement calls attention to a situation that can result in harm to
hardware or equipment.
DANGER:
A danger statement calls attention to a situation that can result in harm to
personnel.
SECURITY ALERT:
A security alert calls attention to a situation that can increase the potential for
unauthorized use of a telecommunications system.
Safety precautions
When performing maintenance or translation procedures on the system, observe all caution,
warning, and danger admonishments to prevent loss of service, possible equipment damage,
and possible personal injury. In addition, the following precautions regarding electromagnetic
interference (EMI) and static electricity must be observed:
Electromagnetic interference
This equipment generates, uses, and can radiate radio frequency energy. Electromagnetic
fields radiating from the switch may cause noise in the customer’s equipment. If the equipment
is not installed and used in accordance with the instruction book, radio interference may result.
!
WARNING:
WARNING:
To maintain the EMI integrity of the system, maintenance personnel must ensure
that all cabinet panels, covers, and so forth, are firmly secured before leaving the
customer’s premises.
30 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Downloading this book and updates from the Web
Downloading this book and updates from the Web
The latest version of this book can be downloaded from the Avaya Web site. You must have
access to the Internet, and a copy of Acrobat Reader must be installed on your personal
computer.
Avaya makes every effort to ensure that the information in this book is complete and accurate.
However, information can change after the book has been published. The Avaya Web site may
contain new product information and updates to the information in this book.
To download the latest version of this book:
1. Access the Avaya Web site at http://support.avaya.com
2. Click on Advanced Search on the top right of the screen
3. Enter the name or number of the document
Technical assistance
Avaya provides the following resources for technical assistance.
Within the United States
For help with:
●
●
●
Feature administration and system applications, call Avaya Technical Consulting Support
at 1-800-225-7585
Maintenance and repair, call the Avaya National Customer Care Support Line at
1-800-242-2121
Toll fraud, call Avaya Toll Fraud Intervention at 1-800-643-2353
International
For all international resources, contact your local Avaya authorized dealer for additional help.
Issue 3 February 2007
31
About this book
Sending us comments
Avaya welcomes your comments about this book. To reach us by:
●
Mail, send your comments to:
Avaya Inc.
Product Documentation Group
Room B3-H13
1300 W. 120th Avenue
Westminster, CO 80234 USA
●
E-mail, send your comments to:
document@avaya.com
●
Fax, send your comments to:
Mention the name and number of this book, Maintenance Alarms for Avaya Communication
Manager 4.0, Media Gateways and Servers (03-300430)
32 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Chapter 1: Server Alarms
S8700 | S8710 | S8720 | S8300| S8400 | S8500
This chapter provides background information on server alarming. For detailed information on
G250/G350 and G700 Media Gateway Traps, refer to Chapter 4: Media Gateway Traps.
Introduction
During normal operations, software or firmware may detect error conditions pertaining to
specific Maintenance Objects (MOs). The system automatically attempts either to fix or
circumvent these problems. Errors are detected in two ways:
●
By firmware on the component during on-going operations
●
A “periodic test” or a “scheduled test” started by software
The technician can run tests on demand that are generally more comprehensive (and
potentially disruptive) than are the "scheduled tests".
When an error is detected, the maintenance software puts the error in the Error Log. If a
component incurs too many errors, an alarm is raised.
Alarms on the Linux media servers can occur in several areas:
●
●
●
●
Media Modules, Media Servers, the Media Gateway Processor, and the Layer 2 Switching
Processor are all capable of detecting internal failures and generating traps and alarms.
Media Gateways detect faults and alert the Media Server. The Media Server then raises
an alarm and sends the alarm to an appropriate network management site.
Communication Manager alarms reflect the health status of network elements such as
circuit packs, media modules, and their associated links, ports, and trunks.
Messaging alarms provide health status of embedded or external messaging systems.
Alarms may be viewed using the following:
●
Maintenance Web Interface
Provides alarms information related to Communication Manager, the media server, and
messaging.
Note:
Note:
For non-Communication Manager alarms, use the Web Page header "Alarms
and Notification" and "Diagnostics: View System Log". Choose the appropriate
heading and, if necessary, call Avaya support.
Issue 3 February 2007
33
Server Alarms
●
Media Server bash shell
Provides alarms information related to Communication Manager, the media server, and
messaging.
●
Media Server SAT CLI
Provides alarms information related to Communication Manager.
●
MGP CLI (on the G700 Media Gateway)
Provides alarms and traps information related to the G700 platform and its subsystems.
●
Layer 2 Switching Processor CLI (on the G700 Media gateway)
Provides information related to the media gateway stack.
Information related to Communication Manager, the media server, and messaging alarms can
be displayed using either the Maintenance Web Interface or the media server bash shell.
However, this document (Maintenance Alarms for Avaya Communication Manager 4.0, Media
Gateways and Servers, 03-300430) provides maintenance information only for Communication
Manager (Chapter 5: Communication Manager Maintenance Object Repair Procedures) and
media server alarms (Chapter 1: Server Alarms). For messaging alarms and repair procedures,
refer to the appropriate documentation for the messaging system.
Alarm Classifications
Alarms are classified depending on their effect on system operation:
●
●
●
●
●
MAJOR alarms identify failures that cause a critical degradation of service. These alarms
require immediate attention.
MINOR alarms identify failures that cause some service degradation but that do not render
a crucial portion of the system inoperable. Minor alarms require attention. However, a
minor alarm typically affects only a few trunks, stations, or a single feature.
WARNING alarms identify failures that cause no significant degradation of service or
equipment failures external to the switch. These failures are not reported to INADS or to
the attendant console.
ON-BOARD problems originate in the circuitry on the alarmed Media Module or circuit
pack.
OFF-BOARD problems originate in a process or component that is external to the Media
Module or circuit pack.
34 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Background Terms
Background Terms
Table 4: Alarming Background Terms gives a useful explanation of terms.
Table 4: Alarming Background Terms
Term
Explanation
TRAP
A trap is an event notification that is sent to the SNMP trap manager and
received from the Media Gateway Processor, Layer 2 Switching Processor,
or RTCP Monitor (Avaya VisAbility).
ALARM
Some traps are determined to be an alarm. If determined to be an alarm,
they are sent to an appropriate alarm management site, such as INADS.
INADS
Initialization and Administration System, a software tool used by Avaya
services personnel to initialize, administer, and troubleshoot customer
communications systems remotely.
SNMP
Simple Network Management Protocol, the industry standard protocol
governing network management and the monitoring of network devices and
their functions.
RTCP
Real Time Control Protocol, contained in IETF RFC 1889.
ISM
Intelligent Site Manager, a VPN gateway on the customer’s LAN that
provides a means for services personnel to access the customer’s LAN in a
secure manner via the Internet.
VPN
Virtual Private Network, a private data network that makes use of the public
telecommunication infrastructure, maintaining privacy through the use of a
tunneling protocol and security procedures.
Issue 3 February 2007
35
Server Alarms
Alarm-Related LEDs
Table 5: Alarm-Related LEDs shows alarm-related LEDs on the faceplate of the Media
Gateway or on an attendant console, and shows how certain LEDs reflect specific alarm
situations.
Table 5: Alarm-Related LEDs
LED
Location
Alarm-Related Cause
ALARM LED
Attendant Console
The system alarm causes the attendant console ALARM
LED to light.
ACK LED
Attendant Console
The ACK LED on the attendant console reflects the state
of acknowledgement of the alarm report from INADS.
However, this is only possible for S8700-based Media
Servers.
RED ALM or
ALARM LED
Front Panel of
Media Gateway
The RED ALM or ALARM LED indicates the "health" of
the Media Gateway by lighting when there are impaired
functions of the Media Gateway Processor, Layer 2
Switching Processor, or VOIP engine. It lights, for
example, when the power supply voltage is out of
bounds, if the Media Gateway cannot locate any Media
Servers, or when the unit is overheating. It also indicates
when the system is in Power-up mode, or when a Media
Module is resetting.
Alarm Content
Alarms logged by Communication Manager are stored in an alarm log. All alarms include a date
and time stamp that reflects the date and time of the sending device. The alarm contains:
●
Device type
●
Component type
●
Device name
●
Current IP address
●
Additional information necessary for identification of alarm origination
●
Severity level to indicate the priority of the alarm
Alarms originating in a specific media server, such as an S8300, have a prefix denoting that of
an S8300.
36 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
QOS Alarms
QOS Alarms
An RTCP monitor using the local SNMP agent generates traps to a pre-administered trap
collector. The following QoS alarms are generated:
●
●
●
The voip-callqos alarm is generated if a single session exceeds configured QOS levels. It
can generate a warning or an SNMP trap. Warnings are used for less severe problems.
They can be accumulated internally within Avaya VoIP Monitoring Manager for use by the
alarms defined below.
The voip-systemqos alarm is generated if the number of voip-callqos warnings from all
terminals exceeds a configured count over a given period (e.g. 100 alarms over 24 hours).
The alarm causes a SNMP trap to be sent.
The voip-terminalqos alarm is like the voip-systemqos alarm except it applies to a single
terminal. If any one terminal generates a number of voip-callqos warnings that exceed a
threshold then the alarm is generated.
Alarm Management
This section describes methods to determine the source of alarms that are generated when an
error occurs. The alarm log is viewable and follows that defined in Maintenance Commands for
Avaya Communication Manager 4.0, Media Gateways and Servers (03-300431). Technicians
can view alarms via the Web Interface, CLI, and SAT command-line interface.
SNMP management is a function of the Avaya Network Management Console with VoIP
SystemView application. For additional information, including information on event logs and trap
logs, please refer to the User’s Guide for the Avaya P333T Stackable Switch Release 3.12.
Alarm management follows the Media Server Alarming Architecture Design. See Maintenance
Procedures for Avaya Communication Manager 4.0, Media Gateways and Servers
(03-300432).
Connection Strategies to a Services Organization
A services organization, such as INADS, receives alarms from the Media Server and connects
to the media server for troubleshooting. There are currently two product-connect strategies:
dialup modem access and Virtual Private Network (VPN) access over the Internet.
Issue 3 February 2007
37
Server Alarms
For dialup modem access:
1. Connect a USB modem, connected to a telephone line, to the USB port on the faceplate of
the media server.
2. Enable the modem from the media server Web Interface. In addition, use the Setup Modem
Interface under the Configure Server pages.
3. With this modem, a client PC uses the Point-to-Point Protocol (PPP) to access the media
server and connect via telnet to a Linux shell.
4. Once logged into the media server, you can telnet out to media gateways such as the G700,
and other devices on the network.
Note:
Additionally, this modem can be used to allow the media server to call out to the
INADS or other alarm receiving system to report alarms. When performing
remote diagnostic tests, Services personnel should disable alarm call-outs to
INADS to avoid generating unnecessary alarms. Alarm suppression is released
after 30 minutes. If you are remotely logged in through the modem, you prevent
alarms from being sent because you are using the modem, but you do not
prevent an alarm noting the absence of alarm reporting service being logged at
the alarm receiving site.
Note:
The VPN alternative is achieved by the use of the Intelligent Site Manager (ISM) application.
The ISM is a VPN gateway that resides on the customer’s LAN and provides a means for
services personnel to gain access to the customer’s LAN in a secure manner over the Internet.
Telnet is then used to access the media server and/or media gateways and other IP network
equipment.
Alarms in Linux Media Servers
S8700 | S8710 | S8720 | S8300 | S8400 | S8500
A Linux-based media server can be configured so that it serves as the trap collector and
provides external alarm notification.
A process called the Global Maintenance Manager (GMM) runs on the media server and
collects events that are logged to the Linux syslog_d process. These events consist primarily of
failure notification events logged by Communication Manager and INTUITY maintenance
subsystems or traps sent by media gateways. For events that require external notification, one
option is to call the Avaya technical service center’s INADS (Initialization and Administration
System). Other options include sending an e-mail to specified destinations or sending an SNMP
trap to a specified network management address.
The media server has an SNMP trap manager that collects traps from:
●
Uploads and downloads to media modules
●
VoIP Media Modules
38 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Clearing Media Server Alarms
●
VoIP engines on media gateway motherboards
●
media gateway-associated UPS systems
Media server alarms perform a similar role to Communication Manager alarms in a traditional
telephony context. Media Server alarms:
●
Comprise related sets of alarms
●
Create an internal record of actual or potential problems
●
Notify maintenance personnel of a problem
●
Help isolate the source of the problem
●
Point to and facilitate local and remote resolution of a problem
Note:
If a user is logged into a server by an analog modem that is also the server’s only
alarm-reporting interface, enter almsuppress on the Linux command line to
suppress alarm reporting. Otherwise, the other server logs an occurrence of
SME Event ID #1 (see SME Alarms).
Note:
Clearing Media Server Alarms
A media server is an open standards-based CPU in the data- communications context. Unlike a
Communication Manager alarm, which cannot be cleared unless it is also resolved, a server
alarm:
●
Can be manually cleared from its log, with the almclear Linux command
●
Should not be considered resolved until it is actually repaired
Displaying Media Server Alarms
In the following sections, each server alarm is described and its resolution procedure is
provided. Like traditional Communication Manager maintenance objects, the 3-column table for
each server MO shows an alarm’s:
1. Event ID
2. Severity
3. Definition, probable cause, and troubleshooting procedure
Issue 3 February 2007
39
Server Alarms
To help isolate a server problem, the 3rd column of these tables begins with quoted text for each
event (unlike traditional Communication Manager MOs). The text consists of the verbose (-v)
output of the almdisplay -v Linux command. For example, “interchange hand off failed” is
the quoted text for Arbiter’s Event ID #3.
If the almdisplay command returns a failure message, such as:
almdisplay: 4: Unable to connect to MultiVantage
enter the man almdisplay Linux command for command-related information.
Alarms on the S8300 Functioning as an LSP
The S8300, when functioning as a Local Survivable Processor (LSP), logs an alarm when it
becomes active. It also logs an alarm for every G700 Media Gateway that registers with it. It
logs a warning when IP phones register with it.
Communication Manager Hardware Traps
Table 6: Communication Manager Hardware Traps illustrates hardware traps that apply to
Communication Manager.
Table 6: Communication Manager Hardware Traps
Trap
Description
Media Server HW trap
Hardware faults are analyzed by maintenance software and
correlate fault conditions to determine the appropriate action. If
appropriate action requires attention, a trap of critical severity is
sent.
Media Server HW clear
trap
Hardware faults that have created traps send a clear trap upon
clearing.
Media Server with
administered MG that is
not registered
If a Media Server has an administered G700 but it has not
registered after an appropriate amount of time, send an alarm of
major severity indicating such.
40 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Communication Manager Hardware Traps
Note:
The Avaya S8300 Media Server on a G700 Media Gateway platform has several
watchdog timers. If any one of them is not verified regularly, a trap of major
severity is sent. The timer associated with the S8300 is the S8300 Software
watchdog, which resets the S8300 processor if its connection is not verified
regularly.
Note:
Backup and Restore Traps
The S8300 uses the LAN to backup a copy of its translation data. Table 7: Backup and Restore
Traps illustrates the backup and restore traps.
Table 7: Backup and Restore Traps
Trap
Description
Successfully stored
backup
A trap of informational severity is sent when backup is successful.
(REPLY_ACK) The trap reads “Successful backup of S8300
translation data,” and names the backup location stored in the
string “BACKUP_LOCATION.”
This information also goes to the local maintenance screen, since
it is very possible that a backup is being requested as a result of an
on-site attempt to replace the S8300.
No backup data stored
A trap of major severity is sent as soon as a REPLY_ERROR
message is returned. The trap states “Translation Data backup not
available,” and names the backup location stored in the string
“BACKUP_LOCATION.”
Linux Media Server MOs and Alarms
Hardware MOs
The server’s hardware MOs are described in the following sections:
●
DAJ1/DAL1/DAL2 (Duplication Memory Board)
●
HARD DISK (Hard Disk Drive)
●
RMB (Remote Maintenance Board)
●
SME (Server Maintenance Engine)
●
USB1 (Modem)
●
UPS (Uninterruptible Power Supply)
Issue 3 February 2007
41
Server Alarms
Server-related alarms
Server-related alarms and their troubleshooting procedures are described in the following
tables:
●
ARB (Arbiter)
●
DUP (Duplication Manager)
●
DUP (Duplication Manager)
●
ENV (Environment)
●
FSY (File Synchronization)
●
Login Alarms
●
HARD DISK (Hard Disk Drive)
●
Login Alarms
●
NIC (Network Interface Card)
●
RMB (Remote Maintenance Board)
●
SME (Server Maintenance Engine)
●
SVC_MON (Service Monitor)
●
_TM (Translation Manager)
●
UPS Alarms to the Media Server
●
USB1 (Modem)
●
_WD (Watchdog)
●
Login Alarms - S8300
●
S8710 Alarms
●
S8710 Environmental Alarms
●
S8710 Server BIOS Error Messages
42 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
ARB (Arbiter)
ARB (Arbiter)
S8700 | S8710 | S8720
The Arbiter process runs on S8700 Series Media Servers to:
●
Decide which server is healthier and more able to be active
●
Coordinate data shadowing between servers, under the Duplication Manager’s control
At the physical and data-link layers, three links may serve as redundant inter-arbiter UDP
communication paths: the control network A link, the control network B link (if present), or an
Ethernet-based duplication link. Two of these links must be present. The redundant inter-arbiter
UDP communication paths are used to:
●
Enable arbitration between the active and standby servers
●
Provide the necessary status signaling for memory refreshes
All inter-arbiter communication uses triple DES encryption for secure communication and
control.
ARB Alarms describes the Arbiter’s alarms and their troubleshooting procedures. See DUP
(Duplication Manager) for more information.
Issue 3 February 2007
43
Server Alarms
Table 8: ARB Alarms 1 of 10
Event
ID
3
Alarm
Level
Alarm Text, Cause/Description, Recommendation
MIN
"Interchange handoff failed” — The standby server could not process the
active server’s interchange request. The interchange does not occur, and
the active side remains active.
Follow steps 1 - 4 if using the Web interface. Follow steps 5 - 8 if using the
Linux Command Line Interface.
1. Using the Web Interface: From the Web interface’s Server section,
select View Summary Status to see if the standby side is RESET.
2. Manually clear the alarm by selecting Alarms and Notification, the
appropriate alarm, and Clear
3. If the problem persists, troubleshoot the standby server:
a. Check if the standby side is RESET. From the Web interface’s
Server section, select View Summary Status
b. Check for application problems by selecting View Process Status
and restore any applications with problems.
c. Check for problems with an Ethernet interface by selecting the
Execute Pingall diagnostic. Check both sides of each failed link,
and make any necessary repairs.
4. If the applications and interfaces are okay but the problem persists,
escalate the problem.
5. Using the Linux Command Line Interface: Enter server and
check if the standby side is RESET.
6. Enter almclear -n #id to manually clear the alarm.
7. If the problem persists, troubleshoot the standby server:
a. Enter server and check if the standby side is RESET.
b. Enter statapp and check for application problems. Restore any
applications with problems.
c. Check for problems with an Ethernet interface by entering
pingall -a. Check both sides of each failed link, and make any
necessary repairs.
8. If the applications and interfaces are okay but the problem persists,
escalate the problem.
1 of 10
44 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
ARB (Arbiter)
Table 8: ARB Alarms 2 of 10
Event
ID
7
Alarm
Level
Alarm Text, Cause/Description, Recommendation
MAJ
“Arbiter in invalid/unknown state” — Memory corruption or bad code/build
1. Verify that the server’s state is “Corrupt!” by entering the following
commands on the Linux command line:
server
stop -Sf -s arbiter
start -s arbiter
server -c
If the output no longer shows "Mode: Corrupt!", then the problem has
been fixed. Otherwise, proceed to step 2.
2. Compare the suspected arbiter with the one in /root2.
Enter the following Linux command to display the arbiter’s version
string:
/opt/ecs/sbin/acpfindvers /opt/ws/arbiter
Enter the following command to run a cyclical redundancy check
(CRC) against the arbiter and display both the CRC output value
and the number of bytes in the arbiter file:
/sbin/cksum /opt/ws/arbiter
3. If the two arbiter files differ:
a. Get a fresh copy of arbiter from the CD.
b. Manually clear the alarm, either from the:
- Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
- Linux command line, by entering almclear -n #id
4. If the arbiter file is OK or the problem persists, escalate the
problem.
2 of 10
Issue 3 February 2007
45
Server Alarms
Table 8: ARB Alarms 3 of 10
Event
ID
8
Alarm
Level
Alarm Text, Cause/Description, Recommendation
MIN
“Both servers thought they were active".
1. If using the Web Interface:
a. From the Web interface’s Server section, select
View Summary Status and verify that both servers are active.
b. To distinguish the cause, examine the trace logs for Interarbiter
messages with timestamps shortly before to shortly after the loss of
heartbeat by
1. Selecting the View System Logs diagnostic and
Logmanager Debug trace
2. Specifying the Event Range for the appropriate time frame
3. Matching the Interarb pattern
c. Depending on the cause, continue with either Step 3 or Step 4.
2. If using the Linux command line:
a. Enter server and verify that both servers are active.
b. To distinguish the cause, examine the trace logs for Interarbiter
messages with timestamps shortly before to shortly after the loss of
heartbeat by entering logv -t ts
c. Depending on the cause, continue with either Step 3 or Step 4.
3 of 10
46 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
ARB (Arbiter)
Table 8: ARB Alarms 4 of 10
Event
ID
8
(cont’d)
Alarm
Level
MIN
Alarm Text, Cause/Description, Recommendation
3. A high-priority process caused the active Arbiter to hang for at least
4.1 seconds, causing an interchange. Each Arbiter then realized that
the other had assumed the active role.
An automatic resolution process should leave the newly active server
active, while the other server backs down to the standby role.
a. If one server is active and the other is standby, manually clear the
alarm, either from the:
- Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
- Linux command line, by entering almclear -n #id
b. If the problem recurs, escalate the problem.
4. Every Interarbiter link is down or mis-configured.
a. Check for problems with an Ethernet interface, either from the:
- Web interface, by selecting the Execute Pingall diagnostic
- Linux command line, by entering pingall -a
Check both sides of each failed link, and make any necessary
repairs.
b. If the links are OK but the problem persists, escalate the problem.
9
WRN
<SOH (state-of-health) string> — Before an interchange, the standby
server is significantly healthier than the active server requesting the
interchange. (The active server is probably unable to sustain call
processing.)
Understanding ARB Event #9’s String Pairs
ARB Event #9 generates pairs of SOH strings, where in each string pair,
the:
●
1st string represents the active
●
2nd string represents the standby
server’s SOH just before an interchange. Since – (unless prevented by
external circumstances) – Event 9 triggers a server interchange, the 1st
string normally represents the less healthy server – which became the
standby. So, the 1st string’s data is usually more pertinent.
4 of 10
Issue 3 February 2007
47
Server Alarms
Table 8: ARB Alarms 5 of 10
Event
ID
Alarm
Level
Alarm Text, Cause/Description, Recommendation
9
WRN
The following is a sample string pair generated by ARB Event #9. Within
this sample, four pairs of digits in each string have special meaning, and
are labeled “aa” through “dd.”
(cont’d)
aa
bb cc
dd
↓↓
↓↓ ↓↓
↓↓
gmm 0700, pcd 00/00, dup 270, wd 81, actv 004
gmm 0700, pcd 06/06, dup 370, wd 01, actv 014
●
For “aa,” any value other than “00” indicates a hardware problem.
(For example, the value “20” is common for a power failure.)
In the above example, neither server had hardware trouble.
●
“bb” and “cc”: Here, "bb" indicates the number of IPSI’d PNs that the
server in question controls (if active) or is prepared to control (if
standby), and "cc" indicates the number of connections to PNs with
IPSIs. For non-ESS servers, different values within the same string
indicate a problem with controlling one or more IPSI-connected PNs.
A PN reset can cause both server’s strings to reflect equally degraded
health, but that event (in itself) should not trigger a server interchange.
●
For “dd,” any value other than “01” indicates a failed software
process. (More precisely, a certain value indicates a problem with a
discrete portion of the platform’s process set, including:
- “21” for a Linux daemon (for example, “atd”, “httpd”, “inetd”, or
“xntpd”)
- “41” for a platform service (for example, “dbgserv”, “prune”, or
“syslog”)
- “81” for reloaded Communication Manager software, as in the
previous sample
5 of 10
48 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
ARB (Arbiter)
Table 8: ARB Alarms 6 of 10
Event
ID
Alarm
Level
Alarm Text, Cause/Description, Recommendation
9
WRN
Troubleshooting ARB Event #9
(cont’d)
1. compare the health of both servers, either from the:
- Web interface’s Server section, by selecting
View Summary Status
- Linux command line, by entering server
2. Using the output from Step 1, check the health of each server’s
individual processes.
3. Check the health of the active server’s individual processes, either
from the:
- Web interface, by selecting View Process Status
- Linux command line, by entering statapp
and restore any applications with problems.
4. See if the standby side is RESET, either from the:
- Web interface’s Server section, by selecting
View Summary Status
- Linux command line, by entering server
5. Check the health of the standby server’s individual processes, either
from the:
- Web interface, by selecting View Process Status
- Linux command line, by entering statapp,
and restore any applications with problems.
6. Check for problems with an Ethernet interface, either from the:
- Web interface, by selecting the Execute Pingall diagnostic
- Linux command line, by entering pingall -a
Check both sides of each failed link, and make any necessary repairs.
On the Linux command line, enter ifconfig -a
Ensure the IP addresses match /etc/opt/ecs/servers.conf and
/etc/hosts, and check that all ethernet ports have been assigned IP
addresses. Enter /sbin/arp -a to ensure that no MAC addresses
of "incomplete" appear.
7. If the standby’s applications and interfaces are OK but the problem
persists, escalate the problem.
6 of 10
Issue 3 February 2007
49
Server Alarms
Table 8: ARB Alarms 7 of 10
Event
ID
Alarm
Level
Alarm Text, Cause/Description, Recommendation
9
WRN
After the interchange, the newly active server’s health should be
significantly better than the standby server’s. See the SOH values "bb" and
"cc" as defined above. The server with the larger "bb" value is generally
considered more healthy. If there is a tie, the server with the larger "cc"
value is more healthy. If the newly active server’s health is significantly
better than the standby server’s, troubleshoot the standby server.
(cont’d)
If the newly active server’s health is not significantly better:
1. Manually clear the alarm, either from the:
- Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
- Linux command line, by entering almclear -n #id
2. If the problem recurs, escalate the problem.
11
WRN
“Cannot create receive socket;” “Cannot create transmit socket;” “Cannot
bind receive socket;” “Cannot (re)bind send socket”
Since the Arbiter continuously attempts to create or bind the socket, the
problem may resolve itself. Once resolved, the Arbiter can send and
receive across every Interarbiter link (no subsequent error messages in
the trace log).
1. Examine the alarm log to distinguish between a:
Bind or create problem
Send or receive socket problem
by accessing either the:
- Web interface, by:
a. Selecting Alarms and Notification and the appropriate alarm
b. Selecting the View System Logs diagnostic
c. Selecting the Logmanager Debug trace
d. Specifying the Event Range for the appropriate time frame
e. Matching the “cannot create” pattern
- Linux command line, by entering almdisplay -v
7 of 10
50 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
ARB (Arbiter)
Table 8: ARB Alarms 8 of 10
Event
ID
Alarm
Level
11
WRN
(cont’d)
Alarm Text, Cause/Description, Recommendation
2. Check for both the completeness and consistency of the servers’
hosts and servers.conf files (containing IP addresses of the
system’s configured components), either from the:
- Web interface, by selecting Configure Server
- Linux command line, by entering:
more /etc/hosts
more /etc/opt/ecs/servers.conf
The Arbiter uses port number 1332 for sockets. Enter
netstat -a | grep 1332 to see if the alarm is still active. The
output should look something like:
upd
0
0<server-name>-cnb:1332
*.*
upd
0
0<server-name>-cna:1332
*.*
upd
0
0<server-name>-dup:1332
*.*
3. If the IP addresses agree and there are no alarms for port 1332,
manually clear the alarm, either from the:
- Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
- Linux command line, by entering almclear -n #id
4. If this problem affects call processing or if the problem persists,
continue with Step 5.
If not, continue only at the customer’s convenience.
5. Escalate this problem for explicit guidance with Steps 5a through 6.
a. Enter server to verify that the suspected server is the standby.
b. If not, enter server -if to force a server interchange. Busy out
the standby server from the Linux command line, by entering
server -b.
c. Reboot the server (as the standby), either from the:
- Web interface, by selecting Shutdown This Server
- Linux command line, by entering /sbin/shutdown -r now
6. If rebooting the standby does not help or if the problem recurs,
escalate the problem to the next higher tier.
8 of 10
Issue 3 February 2007
51
Server Alarms
Table 8: ARB Alarms 9 of 10
Event
ID
12
Alarm
Level
Alarm Text, Cause/Description, Recommendation
MIN
“Interchange without doing prep” — Since the Arbiter could not create a
thread to request a file synchronization, some files did not get shadowed.
1. Examine the trace logs for the entry, Can't create
interchange-prep thread, either from the:
- Web interface by:
a. Selecting the View System Logs diagnostic and
Logmanager Debug trace
b. Specifying the Event Range for the appropriate time frame
c. Matching the “interchange-prep” pattern
- Linux command line, by entering logv -t ts
2. Resubmit any translation changes using the save_trans
command.
3. Manually clear the alarm, either from the:
- Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
- Linux command line, by entering almclear -n #id
9 of 10
52 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
ARB (Arbiter)
Table 8: ARB Alarms 10 of 10
Event
ID
13
Alarm
Level
Alarm Text, Cause/Description, Recommendation
MIN
“Heartbeat timeout from ACTIVE” — There are two possible causes for
this event:
●
●
An unexplained Linux lock-up that starved CPU cycles from all
Communication Manager processes for more than 3.3 seconds
A third main server with a server ID that matches one of the other
two main servers was somehow started and is accessible from the
network
In the case of a Linux lock-up, the problem has already corrected itself by
the time the problem has been seen. There is no corrective action to take.
To investigate the existence of a third main server:
1. On the Linux command line, enter /sbin/arp -a to determine the
MAC addresses of the alternate server ethernet ports associated with
the CNA, CNB, and duplication links.
2. Log into the alternate server and verify that the MAC addresses
match. Do this from both servers.
3. If the MAC addresses do not match, there may be a third system in
the network posing as a doppelganger, and a network sniffer can be
used to find it.
14
MIN
"Standby failed to come back up" - The standby server in a duplex system
has been down for longer than 15 minutes. The standby server is not able
to alarm on its own behalf. Typical causes are:
●
●
Rolling Linux reboots. This in turn could be caused by rolling
Communication Manager reloads or by a failure to even start
Communication Manager.
A server was powered down (manually or UPS failure) for more than
15 minutes without first being taken out of service (busied out). The
correct procedure for doing a "stop" on a standby server is to busy it
out first, then stop it.
Escalate the problem.
10 of 10
Back to:
Hardware MOs
Server-related alarms
Issue 3 February 2007
53
Server Alarms
DAJ1/DAL1/DAL2 (Duplication Memory Board)
S8700 | S8710 | S8720
The Duplication Memory boards are a NIC (network interface card) serving as the physical and
data-link interface for an Ethernet-based duplication link between the servers. This link provides
a call-status data path for sending:
●
TCP-based communication between each server’s Process Manager
●
UDP-based communication between each server’s Arbiter to:
- Enable arbitration between the active and standby servers
- Provide status signaling for memory refreshes
Note:
Note:
Note:
The Duplication Memory boards are not interchangeable between Media
Servers. The DAJ1 (256 MB) will only work in S8700 Media Servers. The DAL1
(256 MB) will only work in S8710 Media Servers and S8720 Media Servers with
standard configuration. The DAL2 (512 MB) will only work in S8720 Media
Servers with the Extra Large configuration running Communication Manager 4.0
and later.
Note:
This call-status data is separate from the translations and Linux files shadowed
between servers. See FSY (File Synchronization).
Table 9: DAJ1/DAL1/DAL2 Alarms describes Duplication Memory board alarms and their
troubleshooting procedures. See also ARB (Arbiter), DUP (Duplication Manager), and NIC
(Network Interface Card).
There is one Linux command for testing the Duplication Memory Board, testdupboard. This
command provides the ability to perform a local loop test and to read error registers. The local
loop test can only be run on a busied out standby server. To check the status of the servers, use
the server command. Enter man server to get information on how to busy out a server.
Table 10: testdupboard command syntax and arguments describes the command usage and
possible errors.
Table 9: DAJ1/DAL1/DAL2 Alarms 1 of 3
Event
ID
Alarm
Level
Alarm Text, Cause/Description, Recommendation
1
WRN
"Single bit EDC test (bad err register)" - ne or more single bit errors have
been detected and corrected on an SDRAM operation. The board
automatically corrects these errors. If this condition continues to occur,
replace the Duplication Memory board.
1 of 3
54 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
DAJ1/DAL1/DAL2 (Duplication Memory Board)
Table 9: DAJ1/DAL1/DAL2 Alarms 2 of 3
Event
ID
Alarm
Level
Alarm Text, Cause/Description, Recommendation
2
WRN
“Single-bit EDC test (bad SB err cnt)” — Single-bit SDRAM error occurred
20 times.
Software automatically clears the single-bit error register. This is a
log-only indication of the error’s occurrence.
1. Manually clear the alarm, either from the:
- Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
- Linux command line, by entering almclear -n #id
3
MAJ
“Dup board SDRAM Multibit errors” — Catastrophic multibit SDRAM
error occurred. This is usually due to a hardware problem.
1. Enter testdupboard on the Linux command line.
2. If the test fails, escalate this problem for explicit guidance with Steps
3 through 5.
3. Power-cycle the server.
4. Enter testdupboard again.
5. If the test still fails, replace the server.
4
MIN
“Local Looparound test failure” — On-demand local loop test failed 3
times. (Cannot read from or write to duplication memory board buffers.)
The Local Looparound test only runs on a busied-out standby server.
1. If the on-demand test is failing but a running duplicated system has
no problems, do nothing.
If the running duplicated system has problems, continue with Step 2
2. Enter testdupboard on the Linux command line.
3. If the test fails, escalate this problem for explicit guidance with Steps
4 through 6.
4. Power-cycle the server.
5. Enter testdupboard again.
6. If the test still fails, replace the server.
2 of 3
Issue 3 February 2007
55
Server Alarms
Table 9: DAJ1/DAL1/DAL2 Alarms 3 of 3
Event
ID
5
Alarm
Level
Alarm Text, Cause/Description, Recommendation
MIN
“Optical Link Receiver CRC errors” — Received multiple CRC errors
across the fiber link.
1. Run testdupboard on both servers.
2. If CRC errors are occurring on both servers, it may be a:
●
Likely problem with the fiber link
●
Far less likely problem with both Duplication Memory boards
If not, the other server’s Duplication Memory board may be faulty.
3. If the running system has duplication-related problems, escalate this
problem to replace the server.
If not, ignore and clear the alarm.
6
MAJ
"Fail to open Dup board card" - The Duplication Memory board is missing
or the software driver for the Duplication Memory board is not installed.
On a new server, either the software configuration is incorrect, or the
Duplication Memory board has failed.
3 of 3
Table 10: testdupboard command syntax and arguments describes the command usage and
possible errors for the testdupboard command.
56 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
DAJ1/DAL1/DAL2 (Duplication Memory Board)
Table 10: testdupboard command syntax and arguments
Argument
Description
Syntax: testdupboard [-s | -l] | [-t arg] | [-?]
none
Performs "short" test
-s
Short test, performs read_err_reg test. This is also the default option
-l
Performs "short" tests and localloop test
-t
arg Specific test to perform. Possible values for arg are:
-?
●
read_err_reg
●
localloop
Display the usage statement.
The following errors may occur:
1
Requested tests must be run on a busied out, standby server.
Use the server command to busyout a server.
3
Failed to create socket
Command could not allocate a system resource. Wait a minute, then
try again.
4
Failed to connect to SME
Command could not connect to the server. Verify that both the Server
Maintenance Engine (SME) and Communication Manager are UP by
entering the command statapp on the server.
5
Failed to send request to SME
Request could not be sent to the server. Verify that both the Server
Maintenance Engine (SME) and Communication Manager are UP by
entering the command statapp on the server.
6
Failed to receive response from SME
The test did not receive a response from the server. Verify that both
the Server Maintenance Engine (SME) and Communication Manager
are UP a by entering the command statapp on the server.
Issue 3 February 2007
57
Server Alarms
Demand test descriptions and error codes
Investigate tests in the order shown in. By clearing error codes associated with the first test
errors generated from other tests in the sequence may also be cleared.
Order of Investigation
Test Command
Read Error Register Test
testdupboard -t read_err_reg
Duplication Memory Board Local Loop Test
testdupboard -t localloop
Read Error Register Test
The Read Error Register test queries three registers, then clears them. The registers are:
●
Optical line receiver’s CRC error register
CRC errors indicate problems with the optical interface between the active and standby
servers.
●
SDRAM’s single-bit error register
Although the Duplication Memory board can “self heal” single-bit errors in the SDRAM’s
error register, chronic problems can indicate a more serious problem.
●
SDRAM’s multiple-bit error register
An SDRAM multiple-bit error condition indicates a problem in the Duplication Memory
board’s memory.
The first time testdupboard is run after a boot or after a certain amount of time, a false FAIL
may occur. This may be caused by the command reporting errors and clearing error registers in
the duplication memory boards, not from a board error.
Repetitive testdupboard failures indicate problems with the duplication memory board.
The following errors can be detected:
58 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
DAJ1/DAL1/DAL2 (Duplication Memory Board)
Table 11: Read Error Register Test
Error
Test
Result
Description / Recommendation
Open failed to MDD
ABORT
The Memory Duplication Driver (MDD) is the system driver
that communicates with the duplication memory board. If this
driver cannot be opened, then the duplication memory
board’s registers cannot be read.
1. This is a system error, try again.
System Error Dup
Memory driver
failed to return data
ABORT
The test ran, but for some reason, the MDD could not return
data.
Dup board err count
query, code=?
?= 1 to 7
FAIL
Code 1 - Single-bit errors occurred.
Code 2 – CRC errors occurred.
Code 3 - Single-bit and CRC errors occurred.
Code 4– Multiple-bit errors occurred.
Code 5 - Multiple-bit and Single-bit errors occurred.
Code 6 - Multiple-bit and CRC errors occurred.
Code 7 - Multiple-bit, Singe-bit, and CRC errors occurred.
Failed to open Dup
Memory Board
FAIL
This may be a system error or a problem with the Duplication
Memory Board. Try the command again. If the test continues
to fail, escalate the problem.
1. This is a system error, try again.
Issue 3 February 2007
59
Server Alarms
Duplication Memory Board Local Loop Test
Note:
Note:
This test runs only if the standby media server is busied out.
This test runs a local looparound test on the duplication memory board of the standby media
server. A 32-bit data number is written to an address and verified for correct transmission. The
test reads the contents of the last data received registers and the last address received register,
and then compares the data. If the data matches, the test passes. If not, the test fails.
The following errors can be detected:
Table 12: Duplication Memory Board Local Loop Test
Error
Test Result
Description / Recommendation
Open failed to
MDD
ABORT
The MDD is the system driver that communicates with the
Duplication Memory board. If this driver cannot be
opened, the board’s registers cannot be read.
Wrong Hardware
for this test
ABORT
Verify that the correct Duplication Memory Board is
inserted in the system.
Looparound test
failed
FAIL
The last address received does not match the address
that was written, or the last data received does not match
the data that was written.
Back to:
Hardware MOs
Server-related alarms
60 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
DUP (Duplication Manager)
DUP (Duplication Manager)
S8700 | S8710 | S8720 only
The Duplication Manager process, via coordination of the Arbiter process, runs on the servers
to control data shadowing between them.
At the physical and data-link layers, an Ethernet-based duplication link provides a TCP
communication path between each server’s Duplication Manager to enable their control of data
shadowing. This TCP/IP link provides the actual data shadowing for software duplication. For
hardware duplication, there is an additional fiber optic link between the duplication memory
boards that provides the data shadowing.
Table 13: DUP Alarms describes the Duplication Manager’s alarms and their troubleshooting
procedures.
See ARB (Arbiter) and DAJ1/DAL1/DAL2 (Duplication Memory Board) for more information.
Issue 3 February 2007
61
Server Alarms
Table 13: DUP Alarms 1 of 4
Event
ID
1
Alarm
Level
Alarm Text, Cause/Description, Recommendation
MAJ
“Duplication card error” — The Duplication Manager determined that the
duplication card is not functioning, but it cannot distinguish between a bad
card, an unplugged card, or a bad fiber link.
Follow steps 1 - 7 if using the Web Interface. Follow steps 8 - 14 if using
the Linux command line interface.
1. Using the Web Interface: Check the physical fiber connectivity at
each server.
2. Verify the alarm by accessing the trace log by:
a. Selecting the View System Logs diagnostic and
Logmanager Debug trace
b. Specifying the Event Range for the appropriate time frame
c. Matching the “dup” pattern
3. Examine the trace-log query’s output for one of these messages:
“glbi: couldn't open Dup Card, errno=<#>. ndm exiting”
“glbi: mmap failed, errno=<#>. ndm exiting”
“Haven't heard from active dupmgr. Dup fiber link down.”
“san_check_rsp() FAILED: Dup Fiber link down.”
4. See if the dup link is both “up” and “refreshed” from the Web
interface’s Server section by selecting View Summary Status
5. If so, manually clear the alarm by selecting Alarms and Notification,
the appropriate alarm, and Clear
1 of 4
62 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
DUP (Duplication Manager)
Table 13: DUP Alarms 2 of 4
Event
ID
Alarm
Level
1
(cont’d)
MAJ
Alarm Text, Cause/Description, Recommendation
If not: Since the following commands cause a brief service outage,
they should only be executed at the customer’s convenience:
a. Force a server interchange to make the suspected server standby
by selecting Interchange Servers
b. Busy out the standby server by selecting Busy Server
c. Release the standby server by selecting Release Server
6. If the problem persists, try:
a. Replacing the fiber between the two servers
b. Rebooting the standby server
7. If the problem continues to persist, escalate for a probable server
replacement.
8. Using the Linux Command Line Interface: Check the physical fiber
connectivity at each server.
9. Enter logv -t ts to verify the alarm by accessing the trace log.
10. Examine the trace-log query’s output for one of these messages:
“glbi: couldn't open Dup Card, errno=<#>. ndm exiting”
“glbi: mmap failed, errno=<#>. ndm exiting”
“Haven't heard from active dupmgr. Dup fiber link down.”
“san_check_rsp() FAILED: Dup Fiber link down.”
11. Enter server and check if the dup link is both “up” and “refreshed”.
12. If so, manually clear the alarm by entering almclear -n #id
If not: Since the following commands cause a brief service outage,
they should only be executed at the customer’s convenience:
a. Enter server -if and select the force option to force a server
interchange and make the suspected server standby.
b. Enter server -b to busy out the standby server.
c. Enter server -r to release the standby server.
13. If the problem persists, try:
a. Replacing the fiber between the two servers
b. Rebooting the standby server
14. If the problem still persists, escalate for a probable server
replacement.
2 of 4
Issue 3 February 2007
63
Server Alarms
Table 13: DUP Alarms 3 of 4
Event
ID
2
Alarm
Level
Alarm Text, Cause/Description, Recommendation
MAJ
“Duplication link down” — One server’s Duplication Manager cannot
communicate with the other server’s Duplication Manager.
Follow steps 1 - 5 if using the Web Interface. Follow steps 6 - 10 if using
the Linux Command Line Interface.
1. Using the Web Interface: Access the trace log by
a. Selecting the View System Logs diagnostic and
Logmanager Debug trace
b. Specifying the Event Range for the appropriate time frame
c. Matching the “ndm” or "DUPLICATION" pattern
2. Examine the trace-log query’s output for one of these messages:
“mainlp: get_addrs returned ***. Could not get IP address for other
server.
Verify name and address in servers.conf. ndm exiting.”
“san_check_msg() sync_msg failed: DUPLINK DOWN.”
3. Check if the dup link is “up” from the Web interface’s Server section by
selecting View Summary Status
4. If so, manually clear the alarm by selecting Alarms and Notification,
the appropriate alarm, and Clear
If not, check the duplication interface’s Ethernet connectivity by
selecting the Execute Pingall diagnostic
5. If pingall passes, check the other server’s applications by selecting
View Process Status
3 of 4
64 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
DUP (Duplication Manager)
Table 13: DUP Alarms 4 of 4
Event
ID
2
(cont’d)
Alarm
Level
MAJ
Alarm Text, Cause/Description, Recommendation
6. Using the Linux Command Line Interface: Access the trace log by
entering logv -t ts
7. Examine the trace-log query’s output for one of these messages:
“mainlp: get_addrs returned ***. Could not get IP address for other
server.
Verify name and address in servers.conf. ndm exiting.”
“san_check_msg() sync_msg failed: DUPLINK DOWN.”
8. Enter server and check if the dup link is “up”.
9. If so, manually clear the alarm by entering almclear -n #id
If not, check the duplication interface’s Ethernet connectivity by
entering pingall -d
10. If pingall passes, enter statapp and check the other server’s
applications.
3
MAJ
Duplication Card Error - Double Bit SDRAM error. This alarm is usually
seen on the active server and indicates a potential problem with the
duplication card on that server.
1. If the alarm occurs multiple times, replace the duplication card.
4
MAJ
Duplication Card Error - Double Frame CRC error. This alarm is usually
seen on the standby server and indicates a possible problem with the fiber
link between the servers.
1. If the alarm occurs multiple times, replace the fiber link.
2. If the alarm still occurs after replacing the fiber link, there might be a
problem with one of the duplication cards. Escalate for a probable
server replacement.
4 of 4
Back to:
Hardware MOs
Server-related alarms
Issue 3 February 2007
65
Server Alarms
ENV (Environment)
S8700 | S8710 | S8720 | S8400 | S8500B | S8710
The ENV environmental maintenance objects are monitored within the server. These include
temperature, voltages, and fans. Table 14: ENV Alarms describes the ENV alarms and their
troubleshooting procedures.
For the S8400, only Event IDs 2, 3, and 4 in Table 14: ENV Alarms apply.
For the S8500B, only Event IDs 31, 32, 33, 34, 35, 36, and 37 in Table 14: ENV Alarms apply.
For the S8700, see Table 14: ENV Alarms.
For the S8710, see S8710 Environmental Alarms
Table 14: ENV Alarms 1 of 13
Event
ID
1
Alarm
Level
Alarm Text, Cause/Description, Recommendation
MIN
“Temperature reached Warning Low” — Motherboard's temperature
reached a warning low level.
1. See if the alarmed condition is still present, either from the:
- Web interface, by selecting the View Temperature/Voltage
diagnostic
- Linux command line, by entering environment
2. If not, manually clear the alarm, either from the:
- Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
- Linux command line, by entering almclear -n #id
2
MIN
“Temperature reached Critical Low” — Motherboard's temperature
reached a critically low level.
1. See if the alarmed condition is still present, either from the:
- Web interface, by selecting the View Temperature/Voltage
diagnostic
- Linux command line, by entering environment
2. If not, manually clear the alarm, either from the:
- Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
- Linux command line, by entering almclear -n #id
1 of 13
66 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
ENV (Environment)
Table 14: ENV Alarms 2 of 13
Event
ID
3
Alarm
Level
Alarm Text, Cause/Description, Recommendation
MIN
“Temperature reached Warning High” — Motherboard's temperature
reached a warning high.
1. See if the alarmed condition is still present, either from the:
- Web interface, by selecting the View Temperature/Voltage
diagnostic
- Linux command line, by entering environment
2. If not, manually clear the alarm, either from the:
- Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
- Linux command line, by entering almclear -n #id
4
MAJ
“Temperature reached Critical High” — Motherboard's temperature
reached a critically high level.
1. Look for any obstructions blocking the server’s fans.
2. Check for any fan alarms, and clear those alarms.
3. Shut down and restart the system.
4. See if the alarmed condition is still present, either from the:
- Web interface, by selecting the View Temperature/Voltage
diagnostic
- Linux command line, by entering environment
5. If not, manually clear the alarm, either from the:
- Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear.
- Linux command line, by entering almclear -n #id
2 of 13
Issue 3 February 2007
67
Server Alarms
Table 14: ENV Alarms 3 of 13
Event
ID
5
Alarm
Level
Alarm Text, Cause/Description, Recommendation
MIN
“+3.3 voltage reached Warning Low” — Motherboard's nominal +3.3
voltage reached a warning low level.
1. See if the alarmed condition is still present, either from the:
- Web interface, by selecting the View Temperature/Voltage
diagnostic
- Linux command line, by entering environment
2. If not, manually clear the alarm, either from the:
- Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
- Linux command line, by entering almclear -n #id
6
MAJ
“+3.3 voltage reached Critical Low” — Motherboard's nominal +3.3
voltage reached a critically low level.
1. See if the alarmed condition is still present, either from the:
- Web interface, by selecting the View Temperature/Voltage
diagnostic
- Linux command line, by entering environment
2. If not, manually clear the alarm, either from the:
- Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
- Linux command line, by entering almclear -n #id
7
MIN
“+3.3 voltage reached Warning High” — Motherboard's nominal +3.3
voltage reached a warning high level.
1. See if the alarmed condition is still present, either from the:
- Web interface, by selecting the View Temperature/Voltage
diagnostic
- Linux command line, by entering environment
2. If not, manually clear the alarm, either from the:
- Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
- Linux command line, by entering almclear -n #id
3 of 13
68 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
ENV (Environment)
Table 14: ENV Alarms 4 of 13
Event
ID
8
Alarm
Level
Alarm Text, Cause/Description, Recommendation
MAJ
“+3.3 voltage reached Critical High” — Motherboard's nominal +3.3
voltage reached a critically high level.
1. See if the alarmed condition is still present, either from the:
- Web interface, by selecting the View Temperature/Voltage
diagnostic
- Linux command line, by entering environment
2. If not, manually clear the alarm, either from the:
- Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
- Linux command line, by entering almclear -n #id
9
MIN
“+5 voltage reached Warning Low” — Motherboard's nominal +5 voltage
reached a warning low level.
1. See if the alarmed condition is still present, either from the:
- Web interface, by selecting the View Temperature/Voltage
diagnostic
- Linux command line, by entering environment
2. If not, manually clear the alarm, either from the:
- Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
- Linux command line, by entering almclear -n #id
10
MAJ
“+5 voltage reached Critical Low” — Motherboard's nominal +5 voltage
reached a critically low level.
1. See if the alarmed condition is still present, either from the:
- Web interface, by selecting the View Temperature/Voltage
diagnostic
- Linux command line, by entering environment
2. If not, manually clear the alarm, either from the:
- Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
- Linux command line, by entering almclear -n #id
4 of 13
Issue 3 February 2007
69
Server Alarms
Table 14: ENV Alarms 5 of 13
Event
ID
11
Alarm
Level
Alarm Text, Cause/Description, Recommendation
MIN
“+5 voltage reached Warning High” — Motherboard's nominal +5 voltage
reached a warning high level.
1. See if the alarmed condition is still present, either from the:
- Web interface, by selecting the View Temperature/Voltage
diagnostic
- Linux command line, by entering environment
2. If not, manually clear the alarm, either from the:
- Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
- Linux command line, by entering almclear -n #id
12
MAJ
“+5 voltage reached Critical High” — Motherboard's nominal +5 voltage
reached a critically high level.
1. See if the alarmed condition is still present, either from the:
- Web interface, by selecting the View Temperature/Voltage
diagnostic
- Linux command line, by entering environment
2. If not, manually clear the alarm, either from the:
- Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
- Linux command line, by entering almclear -n #id
13
MIN
“+12 voltage reached Warning Low” — Motherboard's nominal +12
voltage reached a warning low level.
1. See if the alarmed condition is still present, either from the:
- Web interface, by selecting the View Temperature/Voltage
diagnostic
- Linux command line, by entering environment
2. If not, manually clear the alarm, either from the:
- Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
- Linux command line, by entering almclear -n #id
5 of 13
70 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
ENV (Environment)
Table 14: ENV Alarms 6 of 13
Event
ID
14
Alarm
Level
Alarm Text, Cause/Description, Recommendation
MAJ
“+12 voltage reached Critical Low” — Motherboard's nominal +12 voltage
reached a critically low level.
1. See if the alarmed condition is still present, either from the:
- Web interface, by selecting the View Temperature/Voltage
diagnostic
- Linux command line, by entering environment
2. If not, manually clear the alarm, either from the:
- Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
- Linux command line, by entering almclear -n #id
15
MIN
“+12 voltage reached Warning High” — Motherboard's nominal +12
voltage reached a warning high level.
1. See if the alarmed condition is still present, either from the:
- Web interface, by selecting the View Temperature/Voltage
diagnostic
- Linux command line, by entering environment
2. If not, manually clear the alarm, either from the:
- Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
- Linux command line, by entering almclear -n #id
16
MAJ
“+12 voltage reached Critical High” — Motherboard's nominal +12 voltage
reached a critically high level.
1. See if the alarmed condition is still present, either from the:
- Web interface, by selecting the View Temperature/Voltage
diagnostic
- Linux command line, by entering environment
2. If not, manually clear the alarm, either from the:
- Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
- Linux command line, by entering almclear -n #id
6 of 13
Issue 3 February 2007
71
Server Alarms
Table 14: ENV Alarms 7 of 13
Event
ID
17
Alarm
Level
Alarm Text, Cause/Description, Recommendation
MIN
“-12 voltage reached Warning Low” — Motherboard's nominal -12 voltage
reached a warning low level.
1. See if the alarmed condition is still present, either from the:
- Web interface, by selecting the View Temperature/Voltage
diagnostic
- Linux command line, by entering environment
2. If not, manually clear the alarm, either from the:
- Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
- Linux command line, by entering almclear -n #id
18
MAJ
“-12 voltage reached Critical Low” — Motherboard's nominal -12 voltage
reached a critically low level.
1. See if the alarmed condition is still present, either from the:
- Web interface, by selecting the View Temperature/Voltage
diagnostic
- Linux command line, by entering environment
2. If not, manually clear the alarm, either from the:
- Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
- Linux command line, by entering almclear -n #id
19
MIN
“-12 voltage reached Warning High” — Motherboard's nominal -12 voltage
reached a warning high level.
1. See if the alarmed condition is still present, either from the:
- Web interface, by selecting the View Temperature/Voltage
diagnostic
- Linux command line, by entering environment
2. If not, manually clear the alarm, either from the:
- Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
- Linux command line, by entering almclear -n #id
7 of 13
72 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
ENV (Environment)
Table 14: ENV Alarms 8 of 13
Event
ID
20
Alarm
Level
Alarm Text, Cause/Description, Recommendation
MAJ
“-12 voltage reached Critical High” — Motherboard's nominal -12 voltage
reached a critically high level.
1. See if the alarmed condition is still present, either from the:
- Web interface, by selecting the View Temperature/Voltage
diagnostic
- Linux command line, by entering environment
2. If not, manually clear the alarm, either from the:
- Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
- Linux command line, by entering almclear -n #id
21
MIN
“CPU Core Voltage reached Warning Low” — Motherboard's CPU core
voltage reached a warning low level.
1. See if the alarmed condition is still present, either from the:
- Web interface, by selecting the View Temperature/Voltage
diagnostic
- Linux command line, by entering environment
2. If not, manually clear the alarm, either from the:
- Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
- Linux command line, by entering almclear -n #id
22
MAJ
“CPU Core Voltage reached Critical Low” — Motherboard's CPU core
voltage reached a critically low level.
1. See if the alarmed condition is still present, either from the:
- Web interface, by selecting the View Temperature/Voltage
diagnostic
- Linux command line, by entering environment
2. If not, manually clear the alarm, either from the:
- Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
- Linux command line, by entering almclear -n #id
8 of 13
Issue 3 February 2007
73
Server Alarms
Table 14: ENV Alarms 9 of 13
Event
ID
23
Alarm
Level
Alarm Text, Cause/Description, Recommendation
MIN
“CPU Core Voltage reached Warning High” — Motherboard's CPU core
voltage reached a warning high level.
1. See if the alarmed condition is still present, either from the:
- Web interface, by selecting the View Temperature/Voltage
diagnostic
- Linux command line, by entering environment
2. If not, manually clear the alarm, either from the:
- Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
- Linux command line, by entering almclear -n #id
24
MAJ
“CPU Core Voltage reached Critical High” — Motherboard's CPU core
voltage reached a critically high level.
1. See if the alarmed condition is still present, either from the:
- Web interface, by selecting the View Temperature/Voltage
diagnostic
- Linux command line, by entering environment
2. If not, manually clear the alarm, either from the:
- Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
- Linux command line, by entering almclear -n #id
25
MIN
“CPU I/O Voltage reached Warning Low” — Motherboard's CPU I/O
voltage reached a warning low level.
1. See if the alarmed condition is still present, either from the:
- Web interface, by selecting the View Temperature/Voltage
diagnostic
- Linux command line, by entering environment
2. If not, manually clear the alarm, either from the:
- Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
- Linux command line, by entering almclear -n #id
9 of 13
74 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
ENV (Environment)
Table 14: ENV Alarms 10 of 13
Event
ID
26
Alarm
Level
Alarm Text, Cause/Description, Recommendation
MAJ
“CPU I/O Voltage reached Critical Low” — Motherboard's CPU I/O voltage
reached a critically low level.
1. See if the alarmed condition is still present, either from the:
- Web interface, by selecting the View Temperature/Voltage
diagnostic
- Linux command line, by entering environment
2. If not, manually clear the alarm, either from the:
- Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
- Linux command line, by entering almclear -n #id
27
MIN
“CPU I/O Voltage reached Warning High” — Motherboard's CPU I/O
voltage reached a warning high level.
1. See if the alarmed condition is still present, either from the:
- Web interface, by selecting the View Temperature/Voltage
diagnostic
- Linux command line, by entering environment
2. If not, manually clear the alarm, either from the:
- Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
- Linux command line, by entering almclear -n #id
28
MAJ
“CPU I/O Voltage reached Critical High” — Motherboard's CPU I/O
voltage reached a critically high level.
1. See if the alarmed condition is still present, either from the:
- Web interface, by selecting the View Temperature/Voltage
diagnostic
- Linux command line, by entering environment
2. If not, manually clear the alarm, either from the:
- Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
- Linux command line, by entering almclear -n #id
10 of 13
Issue 3 February 2007
75
Server Alarms
Table 14: ENV Alarms 11 of 13
Event
ID
29
Alarm
Level
Alarm Text, Cause/Description, Recommendation
MAJ
“All fan failure” — Every fan is running at a critically low speed.
1. See if the alarmed condition is still present, either from the:
- Web interface, by selecting the View Temperature/Voltage
diagnostic
- Linux command line, by entering environment
2. If not, manually clear the alarm, either from the:
- Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
- Linux command line, by entering almclear -n #id
30
MIN
S8500B
+1.5 voltage reached Warning Low. S8500B media server environment.
1. See if the alarmed condition is still present, either from the:
- Web interface, by selecting the View Temperature/Voltage
diagnostic
- Linux command line, by entering environment
2. If not, manually clear the alarm, either from the:
- Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
- Linux command line, by entering almclear -n #id
31
S8500B
MAJ
+1.5 voltage reached Critical Low. S8500B media server environment.
1. See if the alarmed condition is still present, either from the:
- Web interface, by selecting the View Temperature/Voltage
diagnostic
- Linux command line, by entering environment
2. If not, manually clear the alarm, either from the:
- Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
- Linux command line, by entering almclear -n #id
11 of 13
76 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
ENV (Environment)
Table 14: ENV Alarms 12 of 13
Event
ID
32
Alarm
Level
Alarm Text, Cause/Description, Recommendation
MIN
+1.5 voltage reached Warning High. S8500B media server environment.\
S8500B
1. See if the alarmed condition is still present, either from the:
- Web interface, by selecting the View Temperature/Voltage
diagnostic
- Linux command line, by entering environment
2. If not, manually clear the alarm, either from the:
- Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
- Linux command line, by entering almclear -n #id
33
MAJ
S8500B
+1.5 voltage reached Critical High. S8500B media server environment.\
1. See if the alarmed condition is still present, either from the:
- Web interface, by selecting the View Temperature/Voltage
diagnostic
- Linux command line, by entering environment
2. If not, manually clear the alarm, either from the:
- Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
- Linux command line, by entering almclear -n #id
34
S8500B
MIN
+2.5 voltage reached Warning Low. S8500B media server environment.
1. See if the alarmed condition is still present, either from the:
- Web interface, by selecting the View Temperature/Voltage
diagnostic
- Linux command line, by entering environment
2. If not, manually clear the alarm, either from the:
- Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
- Linux command line, by entering almclear -n #id
12 of 13
Issue 3 February 2007
77
Server Alarms
Table 14: ENV Alarms 13 of 13
Event
ID
35
Alarm
Level
Alarm Text, Cause/Description, Recommendation
MAJ
+2.5 voltage reached Critical Low. S8500B media server environment.
S8500B
1. See if the alarmed condition is still present, either from the:
- Web interface, by selecting the View Temperature/Voltage
diagnostic
- Linux command line, by entering environment
2. If not, manually clear the alarm, either from the:
- Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
- Linux command line, by entering almclear -n #id
36
MIN
S8500B
+2.5 voltage reached Warning High. S8500B media server environment.
1. See if the alarmed condition is still present, either from the:
- Web interface, by selecting the View Temperature/Voltage
diagnostic
- Linux command line, by entering environment
2. If not, manually clear the alarm, either from the:
- Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
- Linux command line, by entering almclear -n #id
37
S8500B
MAJ
+2.5 voltage reached Critical High. S8500B media server environment.
1. See if the alarmed condition is still present, either from the:
- Web interface, by selecting the View Temperature/Voltage
diagnostic
- Linux command line, by entering environment
2. If not, manually clear the alarm, either from the:
- Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
- Linux command line, by entering almclear -n #id
13 of 13
Back to:
Hardware MOs
Server-related alarms
78 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
FSY (File Synchronization)
FSY (File Synchronization)
S8700 | S8710 | S8720 | S8400 | S8500
The File Synchronization (FSY) process uses TCP-based communication over 100BaseT
Ethernet links to provide synchronized duplication of critical data files, including translations and
important Linux files.
Note:
This set of files is separate from the data shadowed between each server’s
DAJ1/DAL1/DAL2 (Duplication Memory Board).
Note:
Table 15: FSY Alarm in Media Server describes the FSY alarms and their troubleshooting
procedures.
Table 15: FSY Alarm in Media Server
Event
ID
1
Alarm
Level
Alarm Text, Cause/Description, Recommendation
MIN
“File sync failed” — File synchronization operation failed.
1. See if the filesyncd (file sync daemon) process is up, either from the:
- Web interface, by selecting View Process Status
- Linux command line, by entering statapp
2. Check the trace log for more granular information. (The file sync daemon can
report failures of synchronizing one or more files.)
Access the trace log, either from the:
- Web interface, by:
a. Selecting the View System Logs diagnostic and
Logmanager Debug trace
b. Specifying the Event Range for the appropriate time frame
c. Matching the “file sync failed” pattern
- Linux command line, by entering logv -t ts
3. (Except S8500) Make sure that the Ethernet duplication link is up, either from
the:
- Web interface, by selecting the Execute Pingall diagnostic
- Linux command line, by entering pingall -a
If not, check each side of this failed link, and make any necessary repairs.
4. (Except S8500) Check the physical fiber connectivity at each server to verify
that this alarm is not a consequence of other duplication-related problems.
5. If the problem persists, escalate the problem.
Back to:
Hardware MOs
Server-related alarms
Issue 3 February 2007
79
Server Alarms
GAM (Global Alarm Manager)
The Global Alarm Manager determines which events require external alarm notification and
notifies the Global Maintenance Manager (GMM). Table 16: GAM Alarms describes the GAM
Event IDs and the recommended procedures.
Table 16: GAM Alarms
Event
ID
Alarm
Level
Alarm Text, Cause/Description, Recommendation
2
WRN
The GMM is unable to report alarms. The GMM sends out the alarm but
never receives any response from INADS.
1. Test the administered reporting mechanisms by entering testinads
on the Linux command line. This test could fail if the modem is bad.
2. If the test fails, enter testmodem -l on the Linux command line.
3. If the test fails, see Table 31: testmodem command usage for a
description of error messages and recommended procedures.
Back to:
Hardware MOs
Server-related alarms
80 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
HARD DISK (Hard Disk Drive)
HARD DISK (Hard Disk Drive)
The Hard Disk Drive is monitored via the Self Monitoring, Analysis, and Reporting Technology
(SMART) capability that is built into the hard disk drive unit. The SMART technology makes
status information concerning the disk drive available to monitoring software.
Some hard disk drive problems do not occur suddenly. They are the result of a gradual
degradation of disk components. For example, if the value for Reallocated Event Count (count
of remap operations, both successful and non-successful) for Event ID 21 is going up, it may
indicate an impending disk failure. At the very least, it should be monitored closely.
A RAM DISK configuration is used for the Avaya S8500/S8500B simplex server and the Avaya
S8300B ICC server to support platform reliability during hard disk crashes. Hard drives are
among the least reliable hardware components. The RAM DISK feature provides reliable
storage for critical resources that are necessary for continued operation in the absence of the
hard drive. The server will continue to process calls for up to 72 hours after a hard disk failure
has occurred. However, administration additions and changes cannot be made and translations
cannot be saved until the hard disk drive has been replaced.
Table 17: Hard Disk Drive Alarms describes the Hard Disk Event IDs and their troubleshooting
procedures. Not all of the events are described in the table. In general, if the alarm message
displays an alarm severity of MAJ, MIN, or SUP, replace the hard drive.
Table 17: Hard Disk Drive Alarms 1 of 5
Event
ID
16
Alarm
Level
Alarm Text, Cause/Description, Recommendation
MAJ
# HARD DISK 26 MAJ
This message (from the almdisplay -v command) indicates that the
hard disk drive has failed.
1. Replace the hard disk drive.
19
WRN
Device: device_name, Failed attribute: attr_number
This message indicates that the attribute has exceeded its threshold value.
1. The user very likely has a drive problem and should definitely consider
replacing the drive.
20
WRN
smartd: Device: device_name, Read Smartd Values Failed
smartd: Device: device_name, Read Smartd Threshold Failed
This message indicates the SMART utility was unable to read the current
SMART values or thresholds for the drive. This may result in SMART not
executing and the values that are reported may be stale (or outdated). See
also Event ID 22.
1 of 5
Issue 3 February 2007
81
Server Alarms
Table 17: Hard Disk Drive Alarms 2 of 5
Event
ID
Alarm
Level
Alarm Text, Cause/Description, Recommendation
21
WRN
smartd: Device: /dev/had, SMART Attribute: attr_number Changed
chng_value.
The value for the specified attribute number (attr_number) has changed by
the specified value (chng_value). Posting of this alarm may/may not
indicate possible drive problems.
Definitions for the attributes are:
21
(cont’d)
Num
Name
Description
1
Raw Read Error
Indicates the rate of hardware read errors
that occur when reading data from the
disk surface. This error is critical. An
increasing error rate may indicate a
failing disk drive. (Samsung, Seagate,
IBM (Hitachi), Fujitsu, Maxtor, Western
Digital)
2
Throughput
Performance
Overall throughput performance of the
hard disk.
3
Spin Up Time
Raw value average of time to spin up
drive spindle. (Samsung, Seagate, IBM
(Hitachi), Fujitsu, Maxtor, Western Digital)
4
Start Stop Count
Count of hard disk spindle start/stop
cycles. (Samsung, Seagate, IBM
(Hitachi), Fujitsu, Maxtor, Western Digital)
5
Reallocated Sector
Count
Amount of remapped sectors.
6
Read Channel Margin
No explanation of attribute available
7
Seek Error Rate
Average rate of seek errors: if this value
continues to increase it indicates there
may be a problem with the disk surface or
a mechanical problem. (Samsung,
Seagate, IBM (Hitachi), Fujitsu, Maxtor,
Western Digital)
8
Seek Time Performance
Disk seek system performance.
(Samsung, Seagate, IBM (Hitachi),
Fujitsu, Maxtor, Western Digital)
2 of 5
82 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
HARD DISK (Hard Disk Drive)
Table 17: Hard Disk Drive Alarms 3 of 5
Event
ID
Alarm
Level
21 (cont’d)
Alarm Text, Cause/Description, Recommendation
9
Power_On_Hours
Number of hours of the power-on state of
the drive. This value indicates aging.
(Samsung, Seagate, IBM (Hitachi),
Fujitsu, Maxtor, Western Digital)
10
Spin_Retry_Count
Count of retry of drive spindle spine start
up attempts. (Samsung, Seagate, IBM
(Hitachi), Fujitsu, Maxtor, Western Digital)
11
Recalibration Retries
Number of times recalibration was
requested after initial request. (Samsung,
Seagate, IBM (Hitachi), Fujitsu, Maxtor,
Western Digital)
12
Device Power Cycle
Count
Count of full hard disk power on/off
cycles. (Samsung, Seagate, IBM
(Hitachi), Fujitsu, Maxtor, Western Digital)
13
Soft Read Error Rate
Rate of program read errors when
reading data from disk. (Samsung,
Seagate, IBM (Hitachi), Fujitsu, Maxtor,
Western Digital)
193
Load/Unload Cycle
Count of load/unload cycles into landing
zone position. (Samsung, Seagate, IBM
(Hitachi), Fujitsu, Maxtor, Western Digital)
194
Temperature
Hard disk drive temperature. (Samsung,
Seagate, IBM (Hitachi), Fujitsu, Maxtor,
Western Digital - select models)
196
Reallocated Event
Count
Count of remap operations (transferring
of data from bad sector to reserved disk
area) successful and non-successful.
This error is critical. An increasing
count for this error may indicate a
failing disk drive. (Samsung, Seagate,
IBM (Hitachi), Fujitsu, Maxtor, Western
Digital - select models)
197
Current Pending Sector
Count
Current count of unstable sectors (waiting
for remap). This error is critical. An
increasing count for this error may
indicate a failing disk drive. (Samsung,
Seagate, IBM (Hitachi), Fujitsu, Maxtor,
Western Digital)
3 of 5
Issue 3 February 2007
83
Server Alarms
Table 17: Hard Disk Drive Alarms 4 of 5
Event
ID
Alarm
Level
21 (cont’d)
Alarm Text, Cause/Description, Recommendation
198
Uncorrectable Sector
Count
Count of uncorrectable errors when
reading/writing a sector. This error is
critical. An increasing count for this
error may indicate a failing disk drive.
(Samsung, Seagate, IBM (Hitachi),
Fujitsu, Maxtor, Western Digital)
199
UltraDMA CRC Error
Count
Count of Cyclic Redundancy Check
(CRC) errors during UltraDMA mode
(Samsung, Seagate, IBM (Hitachi),
Fujitsu - select models, Maxtor, Western
Digital - select models)
200
Write Error Rate (Multi
Zone Error Rate
Total number of errors found when writing
a sector. (Samsung, Seagate, IBM
(Hitachi), Fujitsu, Maxtor, Western Digital)
220
Disk Shift
Indicates how much the disk has shifted
(unit of measure unknown). This error is
critical. An increasing value for this
error may indicate a failing disk drive.
(Seagate)
221
G-Sense Error Rate
Rate of errors occurring as a result of
impact loads such as dropping the drive
or wrong installation. (Seagate, Hitachi)
222
Loaded Hours
Loading on magnetic heads actuator
caused by the general operating time.
223
Load/Unload Retry
Count
Loading on magnetic heads actuator
caused by numerous recurrences of
operations such as reading, recording, or
positioning.
224
Load Friction
Loading of magnetic heads actuator
caused by friction in mechanical part of
the store.
226
Load-in Time
Total time of loading on the magnetic
heads actuator.
4 of 5
84 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
HARD DISK (Hard Disk Drive)
Table 17: Hard Disk Drive Alarms 5 of 5
Event
ID
Alarm
Level
21 (cont’d)
22
WRN
Alarm Text, Cause/Description, Recommendation
227
Torque Amplification
Count
Count of efforts of the rotating moment of
a drive
228
Power-Off Retract
Count
Count of the number of times the drive
was powered off.
230
GMR Head Amplitude
Amplitude of the heads trembling in
running mode.
Failed to read SMART values/thresholds
This indicates that the SMART utility was not able to read the SMART
values/thresholds from the drive. The SMART utility is unable to function due
to drive access problems.
5 of 5
Back to:
Hardware MOs
Server-related alarms
Issue 3 February 2007
85
Server Alarms
Login Alarms
The Login MO monitors access to the server and alarms suspicious activity. Table 18: Login
Alarms describes the Login alarms and their troubleshooting procedures.
Table 18: Login Alarms
Event
ID
Alarm
Level
Alarm Text, Cause/Description, Recommendation
1
WRN
Successful CM login.
2
MIN
“sat_Auth:Login for [inads] invalid password” — An SAT login to
Communication Manager failed.
1. Verify the alarm, either from the:
- Web interface, by selecting View Current Alarms
- Linux command line, by entering almdisplay -v
2. Since mis-typing a login sequence usually causes this alarm, enter
almclear -n #id to clear the alarm.
3. If this alarm is perceived as a security threat (often due to its
persistence or frequent recurrence), notify the customer.
3
WRN
Successful Linux login
4
MIN
“Login for [linux] – failed – password check” — A login to a server’s Linux
command line failed.
1. Verify the alarm, either from the:
- Web interface, by selecting View Current Alarms
- Linux command line, by entering almdisplay -v
2. Since mis-typing a login sequence usually causes this alarm, enter
almclear -n #id to clear the alarm.
3. If this alarm is perceived as a security threat (often due to its
persistence or frequent recurrence), notify the customer.
5
MAJ
“Probation interval for login ends – lockout interval begins” — Multiple
consecutive login failures.
1. If this alarm is perceived as a security threat, notify the customer.
2. Using a services login, enter the command userlock -s on the
Linux command line. This will display all of the logins in the system, the
number of failed logins, and if the login in question is currently locked
out.
86 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
_MP (Maintenance Processor)
_MP (Maintenance Processor)
S8500B | S8400
Table 19: _MP Alarm in Media Server descibes the alarms returned for _MP.
Table 19: _MP Alarm in Media Server
Event
ID
1
Alarm
Level
Alarm Text, Cause/Description, Recommendation
MAJ
SAMP/MPC is in a rolling reboot state.
1. The problem may be related to corruption. On the server, enter
sampcmd cme load < /etc/agxcm.xml on the Linux command
line.
2. Reboot the SAMP/MPC by entering sampcmd sudo reboot on the
Linux command line.
3. If the rolling reboot persists, escalate the problem.
Back to:
Hardware MOs
Server-related alarms
Issue 3 February 2007
87
Server Alarms
NIC (Network Interface Card)
S8700 | S8710 | S8720 | S8500
The NICs provide the physical and data-link interfaces for Ethernet-based links.
Table 20: NIC Alarms describes NIC alarms and their troubleshooting procedures. See DAJ1/
DAL1/DAL2 (Duplication Memory Board) for more information.
Table 20: NIC Alarms
Event
ID
1
Alarm
Level
Alarm Text, Cause/Description, Recommendation
MIN
“eth0 NIC Link is Down” — Ethernet link on native NIC 0 is down.
1. Verify Ethernet connectivity, either from the:
- Web interface, by selecting the Execute Pingall diagnostic
- Linux command line, by entering pingall -a
Check both sides of each failed link, and make any necessary repairs.
2. If the ping test fails, check the physical connections of NIC 0’s Ethernet
cable.
If the test passes, manually clear the alarm, either from the:
- Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
- Linux command line, by entering almclear -n #id
2
MIN
“eth1 NIC Link is Down” — Ethernet link on native NIC 1 is down.
1. Verify Ethernet connectivity, either from the:
- Web interface, by selecting the Execute Pingall diagnostic
- Linux command line, by entering pingall -a
Check both sides of each failed link, and make any necessary repairs.
2. If the ping test fails, check the physical connections of NIC 1’s Ethernet
cable.
If the test passes, manually clear the alarm, either from the:
- Web interface, by selecting Alarms and Notification, the
appropriate alarm, and “Clear”
- Linux command line, by entering almclear -n #id
Back to:
Hardware MOs
Server-related alarms
88 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
RMB (Remote Maintenance Board)
RMB (Remote Maintenance Board)
S8400 | S8500 | S8500B | S8500C
RMB alarms are reported for the S8400, S8500, S8500B, and S8500C media servers. The
functionality of the Remote Maintenance Board (RMB) is to:
●
Monitor the media server environmental state of health: fans, voltages, and temperature.
●
Report server failures.
●
Provide the ability to perform remote server power-on, power off, and reset functionality.
RMB alarms are not recorded on the server. Alarms are reported to INADS when certain failure
conditions are detected.
S8400: The Maintenance Processor Complex (MPC) board is integrated in the S8400 media
server. It monitors the S8400 server temperature and provides reset control. See
Table 21: RMB Alarms in the S8400 Media Server for this media server.
S8500: The RMB functionality for the S8500 media server is implemented by the Remote
Supervisor Adapter (RSA) board. It is installed in PCI-X slot 1 of the media server. See
Table 22: RMB Alarms in the S8500 Media Server for this media server.
S8500B and S8500C: The RMB functionality for the S8500B and S8500C media servers is
implemented by the Augmentix Server Availability Management Processor™ (A+SAMP) board.
See Table 23: RMB Alarms in the S8500B and S8500C Media Servers for this media server.
Table 21: RMB Alarms in the S8400 Media Server
Event ID
Alarm
Level
Alarm Text, Cause/Description, Recommendation
0
MIN
Test Alarm. Hardware Platform Interface (HPI) User Event - for testing
modem setup.
2
MAJ
Host boot failure. Hardware Platform Interface (HPI) OEM Event host is not booting.
3
MAJ
Host Alarm. Hardware Platform Interface (HPI) User Event Communication Manager detects rolling reboot.
5
MAJ
Host failure timeout. Hardware Platform Interface (HPI) Watchdog
Event - Communication Manager is hung.
Back to:
Hardware MOs
Server-related alarms
Issue 3 February 2007
89
Server Alarms
Table 22: RMB Alarms in the S8500 Media Server 1 of 3
Event
ID
1
Alarm
Level
Alarm Text, Cause/Description, Recommendation
MIN
"RMB driver missing - handshake Failed" - The driver for communicating
with the RSA card cannot be found. Several failures can generate this fault:
●
the Linux bash command /sbin/lsmod is missing
●
the results from running /sbin/lsmod could not be read
●
/sbin/lsmod returned nothing
●
the RSA device driver was not loaded
●
the RSA device driver does not exist
The recommendations are:
1. Be sure /sbin/ibmod exists and is executable.
2. Be sure /tmp exists as a directory and can be written.
3. Be sure /lib/modules/ibmasm/ibmasm.o exists and has read
permission.
4. Run the bash command "service ibmasm start".
2
MIN
"RMB cli is not loaded on the server." - The program that talks to the RSA
card could not be found. Several failures generate this fault:
●
●
the Linux bash command /bin/ls is missing or not working properly
the bash command /opt/ecs/rmb/rsa/rsacli is missing or is not
executable
The recommendations are:
1. Be sure all the above files and directories exist and have read and
execute permissions.
2. Reload any missing files from the distribution.
1 of 3
90 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
RMB (Remote Maintenance Board)
Table 22: RMB Alarms in the S8500 Media Server 2 of 3
Event
ID
3
Alarm
Level
Alarm Text, Cause/Description, Recommendation
MAJ
"RMB reset command failed" - The RSA card did not respond to a reset
command. Several failures generate this fault:
●
●
the bash command opt/IBMmpcli/bin/mpcli is missing or is not
executable
the directory /usr/java/latest is missing or not symbolically linked to
the Java runtime environment (JRE)
●
the file /opt/ecs/rmb/rsareset does not exist or cannot be read
●
no response from the RSA card
●
the RSA card did not execute the request
The recommendations are:
1. Be sure all the above files and directories exist and have read and
execute permissions.
2. Reload any missing files from the distribution.
3. Be sure the RSA card is installed by looking at the back and checking
that the green power LED on the RSA card is on, and that the amber
error LED is off.
4. Verify that the RSA card is working by dialing into it or logging on to it
over the service’s port of the RSA card.
5. Restart the RSA card from the RSA modem or service’s port and check
the LEDs on the back of the card.
6. Verify that the RSA card is plugged into the PCI-X slot of the server.
7. Verify that the flat ribbon cable from the RSA card to the server
motherboard has been installed and is firmly seated in the connectors
at both ends.
8. Replace the RSA card.
2 of 3
Issue 3 February 2007
91
Server Alarms
Table 22: RMB Alarms in the S8500 Media Server 3 of 3
Event
ID
4
Alarm
Level
Alarm Text, Cause/Description, Recommendation
MAJ
"RMB failed handshake test" - The RSA card did not respond to commands
from the server. Several failures generate this fault:
●
●
the bash command /opt/IBMmpcli/bin/mpcli is missing or is not
executable
the directory /usr/java/latest is missing or not symbolically linked to
the Java runtime environment (JRE)
●
the file /opt/ecs/rmb/rsagetip1 does not exist or cannot be read
●
no response from the RSA card
●
the RSA card did not execute the request
The recommendations are:
1. Be sure all the above files and directories exist and have read and
execute permissions.
2. Reload any missing files from the distribution.
3. Be sure the RSA card is installed by looking at the back and checking
that the green power LED on the RSA card is on, and that the amber
error LED is off.
4. Verify that the RSA card is working by dialing into it or logging on to it
over the service’s port of the RSA card.
5. Restart the RSA card from the RSA modem or service’s port and check
the LEDs on the back of the card.
6. Verify that the RSA card is plugged into the PCI-X slot of the server.
7. Verify that the flat ribbon cable from the RSA card to the server
motherboard has been installed and is firmly seated in the connectors
at both ends.
8. Replace the RSA card.
3 of 3
Back to:
Hardware MOs
Server-related alarms
92 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
RMB (Remote Maintenance Board)
Table 23: RMB Alarms in the S8500B and S8500C Media Servers
Event
ID
Alarm
Level
Alarm Text, Cause/Description, Recommendation
0
MIN
Test Alarm. Hardware Platform Interface (HPI) User Event
1
MIN
Loss of power to host. Hardware Platform Interface (HPI) Sensor Event.
2
MAJ
Host boot failure. Hardware Platform Interface (HPI) OEM Event
3
MAJ
Host Alarm. Hardware Platform Interface (HPI) User Event
4
MIN
Loss of External Power to SAMP. Hardware Platform Interface (HPI)
Sensor Event
5
MAJ
Host failure timeout. Hardware Platform Interface (HPI) Watchdog Event
Back to:
Hardware MOs
Server-related alarms
Issue 3 February 2007
93
Server Alarms
SME (Server Maintenance Engine)
S8700 | S8710 | S8720 only
The Server Maintenance Engine (SME) is a Linux process which provides error analysis,
periodic testing, and demand testing for the server.
Table 24: SME Alarms describes the alarms and troubleshooting procedures.
Table 24: SME Alarms
Event
ID
Alarm
Level
Alarm Text, Cause/Description, Recommendation
1
MAJ
“Far-end alarm service is down” — No remote alarm service is available. The other server is
unable to report alarms due to a failure of either the GMM or its administered reporting
mechanisms (SNMP and/or modem). It is also possible that the modem has been in use for
more than 50 minutes by someone dialing into the server for troubleshooting purposes.
1. Look for any GMM failures on the other server, either using the:
- Web interface, by selecting Diagnostics > View System Logs and Watchdog Logs
- Linux command line, by entering logv -w or, directly, by examining /var/log/
ecs/wdlog.
2. If a GMM failure was found:
a. See if the GMM application is up, either from the:
- Web interface, by selecting View Process Status
- Linux command line, by entering statapp
b. If so, continue with Step 3.
If not, try to restart this application by entering start -s GMM on the Linux
command line.
c. If the GMM application successfully restarts, continue with Step 4.
If not, escalate the problem to the next higher tier.
3. If a GMM failure was not found, see if alarm reporting failed by looking in the trace log for
a string that includes “snd2Inads”, either from the:
- Web interface, by:
a. Selecting the View System Logs diagnostic and
Logmanager Debug trace
b. Specifying the “Event Range” for the appropriate time frame
c. Matching the “snd2Inads” pattern
- Linux command line, by entering logv -t ts
4. Test the administered reporting mechanisms by entering testinads on the Linux
command line. This test could fail if the modem is bad.
5. Once the alarm is resolved, manually clear the alarm, either from the:
- Web interface, by selecting Alarms and Notification, the appropriate alarm, and
Clear
- Linux command line, by entering almclear -n #id
2
WRN
For security only. If the IP address in the trap doesn’t match UPS translations, this server is
getting a trap from an illegal source. No action is needed.
Back to:
Hardware MOs
Server-related alarms
94 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
STD (Standard SNMP Traps)
STD (Standard SNMP Traps)
Table 25: STD Alarms describes STD traps and their troubleshooting procedures.
Table 25: STD Alarms
Event Alarm
ID
Level
Type
Cause/Description
1
MIN
ACT
"coldStart" - Agent Up with Possible Changes. A coldStart trap indicates
that the entity sending the protocol (SNMPv2) is re initializing itself in
such a way as to potentially cause the alteration of either the agent’s
configuration or the entity’s implementation.
2
MIN
ACT
“warmStart" - Agent Up with No Changes. A warmStart trap indicates that
the entity sending the protocol (SNMPv2) is re initializing itself in such a
way as to keep both the agent configuration and the entity’s
implementation intact.
3
MIN
ACT
"linkDown" - Agent Interface Down. A linkDown trap indicates that the
entity sending the protocol (SNMPv2) recognizes a failure in one of the
communication links represented in the agent’s configuration. The data
passed within the event is 1) The name and value of the ifIndex instance
for the affected interface. 2) The name of the interface can be retrieved
via an snmpget of .1.3.6.1.2.1.2.2.1.2.INST, where INST is the instance
returned with the trap. The state is indicated by the included value of
ifOperStatus.
3
MIN
RESS
"linkUP" - Agent Interface Up. A linkUp trap indicates that the entity
sending the protocol (SNMPv2) recognizes that one of the
communication links represented in the agent’s configuration has come
up. The data passed within the event is 1) The name and value of the
ifIndex instance for the affected interface. 2) The name of the interface
can be retrieved via an snmpget of .1.3.6.1.2.1.2.2.1.2.INST, where INST
is the instance returned with the trap. The state is indicated by the
included value of ifOperStatus.
Issue 3 February 2007
95
Server Alarms
SVC_MON (Service Monitor)
S8700 | S8710 | S8720 | S8500
SVC_MON is a media server process, started by the Watchdog, to monitor Linux services and
processes. It also starts up threads to communicate with a hardware-sanity device.
Table 26: SVC_MON Alarms describes SVC_MON alarms and their troubleshooting
procedures.
For information about the Watchdog, see _WD (Watchdog).
Table 26: SVC_MON Alarms 1 of 8
Event
ID
1
Alarm
Level
Alarm Text, Cause/Description, Recommendation
MIN
“service atd could not be restarted” — The Linux at daemon is down. Scheduled
services such as session cleanup or daily filesync will not work.
1. From the /sbin directory, enter service atd restart to restart the "at"
daemon.
2. If the daemon restarts, manually clear the alarm, either from the:
● Web interface, by selecting Alarms and Notification, the appropriate
alarm, and Clear
● Linux command line, by entering almclear -n #id
If not, escalate this problem for explicit guidance with steps 2a through 3
a. Enter grep svc_mon /var/log/messages to investigate why the
daemon failed.
! CAUTION:
CAUTION:
Since the following commands cause a brief service outage, they
should only be executed at the customer’s convenience.
b. If the grep command’s output does not help:
● S8700 | S8710 | S8720: enter server to verify that the suspected server is
the standby. If necessary and at the customer’s convenience, enter
server -if to force a server interchange.
●
S8500: Proceed to Step d.
If necessary and at the customer’s convenience, enter server -if to force a
server interchange.
c. S8700 | S8710 | S8720: Reboot the standby server, either from the:
● Web interface, by selecting Shutdown This Server
● Linux command line, entering /sbin/shutdown -r now
d. S8500: Reboot the server, either from the:
● Web interface, by selecting Shutdown This Server
● Linux command line, entering /sbin/shutdown -r now
3. If rebooting the standby does not help or if the problem recurs, escalate the
problem to the next higher tier.
1 of 8
96 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
SVC_MON (Service Monitor)
Table 26: SVC_MON Alarms 2 of 8
Event
ID
2
Alarm
Level
Alarm Text, Cause/Description, Recommendation
MIN
“service crond could not be restarted” — The Linux cron daemon is down. Periodic
services such as session cleanup or daily filesync will not work.
1. Enter /sbin/service cron restart to restart the cron daemon.
2. If the daemon restarts, manually clear the alarm, either from the:
●
Web interface, by selecting Alarms and Notification, the appropriate
alarm, and Clear
●
Linux command line, by entering almclear -n #id
If not, escalate this problem for explicit guidance with steps 2a through 3
a. Enter grep svc_mon /var/log/messages to investigate why the
daemon failed.
Since the following commands cause a brief service outage, they should only be
executed at the customer’s convenience.
b. If the grep command’s output does not help:
●
●
S8700 | S8710 | S8720: enter server to verify that the suspected server is
the standby. If necessary and at the customer’s convenience, enter
server -if to force a server interchange.
S8500: Proceed to Step d.
If necessary and at the customer’s convenience, enter server -if to force a
server interchange.
c. S8700 | S8710 | S8720: Reboot the standby server, either from the:
●
Web interface, by selecting Shutdown This Server
●
Linux command line, entering /sbin/shutdown -r now
d. S8500: Reboot the server, either from the:
●
Web interface, by selecting Shutdown This Server
●
Linux command line, entering /sbin/shutdown -r now
3. If rebooting the standby does not help or if the problem recurs, escalate the
problem to the next higher tier.
2 of 8
Issue 3 February 2007
97
Server Alarms
Table 26: SVC_MON Alarms 3 of 8
Event
ID
3
Alarm
Level
Alarm Text, Cause/Description, Recommendation
MIN
“service inet could not be restarted” — The Linux internet server daemon is down.
Networking services will not work.
1. Enter /sbin/service inet restart to restart the inet daemon.
2. If the daemon restarts, manually clear the alarm, either from the:
- Web interface, by selecting Alarms and Notification, the appropriate alarm,
and Clear
- Linux command line, by entering almclear -n #id
If not, escalate this problem for explicit guidance with steps 2a through 3.
a. Enter grep svc_mon /var/log/messages to investigate why the
daemon failed.
b. If this problem affects call processing, continue with the following steps now.
If not, continue only at the customer’s convenience – since the following
commands cause a brief service outage.
The following commands cause a brief service outage.
c. If the grep command’s output does not help:
●
●
S8700 | S8710 | S8720: enter server to verify that the suspected server is
the standby. If necessary and at the customer’s convenience, enter
server -if to force a server interchange.
S8500: Proceed to Step e.
If necessary and at the customer’s convenience, enter server -if to force a
server interchange.
d. S8700 | S8710 | S8720: Reboot the standby server, either from the:
●
Web interface, by selecting Shutdown This Server
●
Linux command line, entering /sbin/shutdown -r now
e. S8500: Reboot the server, either from the:
●
Web interface, by selecting Shutdown This Server
●
Linux command line, entering /sbin/shutdown -r now
3. If rebooting the standby does not help or if the problem recurs, escalate the
problem to the next higher tier.
3 of 8
98 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
SVC_MON (Service Monitor)
Table 26: SVC_MON Alarms 4 of 8
Event
ID
4
Alarm
Level
Alarm Text, Cause/Description, Recommendation
MIN
“service syslog could not be restarted” — Linux “syslog” service is down. Event
logging to syslog and alarm generation will fail.
1. Enter /sbin/service syslog restart to restart the syslog service.
2. If the service restarts, manually clear the alarm, either from the:
●
Web interface, by selecting Alarms and Notification, the appropriate
alarm, and Clear
●
Linux command line, by entering almclear -n #id
If not, escalate this problem for explicit guidance with steps 2a through 3
a. Enter grep svc_mon /var/log/messages to investigate why the
daemon failed.
Since the following commands cause a brief service outage, they should only be
executed at the customer’s convenience.
b. If the grep command’s output does not help:
●
●
S8700 | S8710 | S8720: enter server to verify that the suspected server is
the standby. If necessary and at the customer’s convenience, enter
server -if to force a server interchange.
S8500: Proceed to Step d.
If necessary and at the customer’s convenience, enter server -if to force a
server interchange.
c. S8700 | S8710 | S8720: Reboot the standby server, either from the:
●
Web interface, by selecting Shutdown This Server
●
Linux command line, entering /sbin/shutdown -r now
d. S8500: Reboot the server, either from the:
●
Web interface, by selecting Shutdown This Server
●
Linux command line, entering /sbin/shutdown -r now
3. If rebooting the standby does not help or if the problem recurs, escalate the
problem to the next higher tier.
4 of 8
Issue 3 February 2007
99
Server Alarms
Table 26: SVC_MON Alarms 5 of 8
Event
ID
5
Alarm
Level
Alarm Text, Cause/Description, Recommendation
MIN
“service xntpd could not be restarted” — The Linux network time protocol daemon is
down. The server’s clock and recently logged time stamps may be inaccurate.
1. Enter /sbin/service xntpd restart to restart the xntpd daemon.
2. If the daemon restarts, manually clear the alarm, either from the:
●
Web interface, by selecting Alarms and Notification, the appropriate
alarm, and Clear
●
Linux command line, by entering almclear -n #id
If not, escalate this problem for explicit guidance with steps 2a through 3
a. Enter grep svc_mon /var/log/messages to investigate why the
daemon failed.
b. If this problem affects call processing, continue with the following steps now.
If not, continue only at the customer’s convenience – since the following
commands cause a brief service outage.
The following commands cause a brief service outage.
c. If the grep command’s output does not help:
●
●
S8700 | S8710 | S8720: enter server to verify that the suspected server is
the standby. If necessary and at the customer’s convenience, enter
server -if to force a server interchange.
S8500: Proceed to Step e.
If necessary and at the customer’s convenience, enter server -if to force a
server interchange.
d. S8700 | S8710 | S8720: Reboot the standby server, either from the:
●
Web interface, by selecting Shutdown This Server
●
Linux command line, entering /sbin/shutdown -r now
e. S8500: Reboot the server, either from the:
●
Web interface, by selecting Shutdown This Server
●
Linux command line, entering /sbin/shutdown -r now
3. If rebooting the standby does not help or if the problem recurs, escalate the
problem to the next higher tier.
5 of 8
100 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
SVC_MON (Service Monitor)
Table 26: SVC_MON Alarms 6 of 8
Event
ID
6
Alarm
Level
Alarm Text, Cause/Description, Recommendation
MIN
“service dbgserv could not be restarted” — Debug server is down, and Gemini
debugger may not work. Although losing this service does not affect operations, the
debugging of a running system is prevented.
1. Enter /sbin/service dbgserv restart to restart the dbgserv service.
2. If the service restarts, manually clear the alarm, either from the:
●
Web interface, by selecting Alarms and Notification, the appropriate
alarm, and Clear
●
Linux command line, by entering almclear -n #id
If not, escalate this problem for explicit guidance with steps 2a through 3
a. Enter grep svc_mon /var/log/messages to investigate why the
daemon failed.
Since the following commands cause a brief service outage, they should only be
executed at the customer’s convenience.
b. If the grep command’s output does not help:
●
●
S8700 | S8710 | S8720: enter server to verify that the suspected server is
the standby. If necessary and at the customer’s convenience, enter
server -if to force a server interchange.
S8500: Proceed to Step d.
If necessary and at the customer’s convenience, enter server -if to force a
server interchange.
c. S8700 | S8710 | S8720: Reboot the standby server, either from the:
●
Web interface, by selecting Shutdown This Server
●
Linux command line, entering /sbin/shutdown -r now
d. S8500: Reboot the server, either from the:
●
Web interface, by selecting Shutdown This Server
●
Linux command line, entering /sbin/shutdown -r now
3. If rebooting the standby does not help or if the problem recurs, escalate the
problem to the next higher tier.
6 of 8
Issue 3 February 2007
101
Server Alarms
Table 26: SVC_MON Alarms 7 of 8
Event
ID
7
Alarm
Level
Alarm Text, Cause/Description, Recommendation
MIN
“service prune could not be restarted” — The prune service is not running. The hard
disk’s partition usage is not being monitored or cleaned.
1. Enter /sbin/service prune restart to restart the prune service.
2. If the service restarts, manually clear the alarm, either from the:
●
Web interface, by selecting Alarms and Notification, the appropriate
alarm, and Clear
●
Linux command line, by entering almclear -n #id
If not, escalate this problem for explicit guidance with steps 2a through 3
a. Enter grep svc_mon /var/log/messages to investigate why the
daemon failed.
b. If this problem affects call processing, continue with the following steps now.
If not, continue only at the customer’s convenience – since the following
commands cause a brief service outage.
The following commands cause a brief service outage.
c. If the grep command’s output does not help:
●
●
S8700 | S8710 | S8720: enter server to verify that the suspected server is
the standby. If necessary and at the customer’s convenience, enter
server -if to force a server interchange.
S8500: Proceed to Step e.
If necessary and at the customer’s convenience, enter server -if to force a
server interchange.
d. S8700 | S8710 | S8720: Reboot the standby server, either from the:
●
Web interface, by selecting Shutdown This Server
●
Linux command line, entering /sbin/shutdown -r now
e. S8500: Reboot the server, either from the:
●
Web interface, by selecting Shutdown This Server
●
Linux command line, entering /sbin/shutdown -r now
3. If rebooting the standby does not help or if the problem recurs, escalate the
problem to the next higher tier.
7 of 8
102 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
SVC_MON (Service Monitor)
Table 26: SVC_MON Alarms 8 of 8
Event
ID
8
Alarm
Level
Alarm Text, Cause/Description, Recommendation
MIN
“service httpd could not be restarted” — The hypertext transfer protocol daemon is
down. The Web interface will not work.
1. Enter /sbin/service httpd restart to restart the http daemon.
2. If the daemon restarts, manually clear the alarm, either from the:
●
Web interface, by selecting Alarms and Notification, the appropriate
alarm, and Clear
●
Linux command line, by entering almclear -n #id
If not, escalate this problem for explicit guidance with steps 2a through 3
a. Enter grep svc_mon /var/log/messages to investigate why the
daemon failed.
Since the following commands cause a brief service outage, they should only be
executed at the customer’s convenience.
b. If the grep command’s output does not help:
●
●
S8700 | S8710 | S8720: enter server to verify that the suspected server is
the standby. If necessary and at the customer’s convenience, enter
server -if to force a server interchange.
S8500: Proceed to Step d.
If necessary and at the customer’s convenience, enter server -if to force a
server interchange.
c. S8700 | S8710 | S8720: Reboot the standby server, either from the:
●
Web interface, by selecting Shutdown This Server
●
Linux command line, entering /sbin/shutdown -r now
d. S8500: Reboot the server, either from the:
●
Web interface, by selecting Shutdown This Server
●
Linux command line, entering /sbin/shutdown -r now
3. If rebooting the standby does not help or if the problem recurs, escalate the
problem to the next higher tier.
8 of 8
Back to:
Hardware MOs
Server-related alarms
Issue 3 February 2007
103
Server Alarms
_TM (Translation Manager)
S8700 | S8710 | S8720 | S8300 | S8400 | S8500
The Translation Manager monitors the server’s ability to read Communication Manager
translations. Table 27: TM Alarm describes the _TM alarms and their troubleshooting
procedures.
Table 27: TM Alarm
Event
ID
1
Alarm
Level
Alarm Text, Cause/Description, Recommendation
MAJ
“Cannot read translations” — Server could not read translations. Usually,
indicates a failure loading translations, but can also infrequently occur on a
running system.
S8700 | S8710 | S8720: The servers spontaneously interchange.
S8300 | S8400 | S8500: The server reboots.
1. Check the integrity of the translation files xln1 and xln2 in /etc/opt/defty,
and verify that they are of the same non-zero length.
2. From the /etc/opt/defty directory, enter the Linux command
cksum xln1 xln2 to verify that the checksums of the files are
identical.
3. S8700 | S8710 | S8720: Copy the translation files from the backup or the
other server.
4. S8300 | S8400 | S8500: Copy the translation files from the backup.
5. If Steps 1 to 3 do not help, load the system with null translations.
6. If the system comes up, this is probably a translation problem.
If not, escalate the problem.
7. Once resolved, manually clear the alarm, either from the:
- Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
- Linux command line, by entering almclear -n #id
Back to:
Hardware MOs
Server-related alarms
104 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
UPG (Upgrade)
UPG (Upgrade)
S8700 | S8710 | S8720 | S8400
THE UPG raises an alarm if the upgrade was not made permanent within a certain amount of
time after the upgrade. Table 28: UPG Alarms, describes the alarms and their troubleshooting
procedures.
Table 28: UPG Alarms
Event
ID
1
Alarm
Level
Alarm Text, Cause/Description, Recommendation
MAJ
The upgrade was not made permanent within two hours.
1. Make the upgrade permanent by using the web interface. Select
Server Upgrade, then select Make Upgrade Permanent
Back to:
Hardware MOs
Server-related alarms
Issue 3 February 2007
105
Server Alarms
UPS (Uninterruptible Power Supply)
S8700 | S8710 | S8720 | S8500 | S8300
The UPS MO supports the UPS device for each media server. This section contains tables
which explain UPS Traps to the Media Server and UPS Alarms to the Media Server.
UPS Traps to the Media Server
Table 29: Enterprise-Specific UPS Traps to Server contains the various UPS-generated SNMP
traps to the media server.
Table 29: Enterprise-Specific UPS Traps to Server 1 of 3
SNMP Trap from UPS
Event
ID
Definition of Trap
Trap (1)
#8
(1–8)
Alarm string = #1, ACT, UPS, A, 8, MAJ, Warning,
system power failure: Possible UPS exhaustion in
8 minutes.
The UPS battery’s power is in a critically low
condition, with an estimated 8 minutes or less of
remaining holdover.
●
A warning is sent to every logged-in user of
the server.
For troubleshooting procedures, see Events #1–8
Trap (3)
upsAlarmShutdownPending
#11
Alarm string = #1, ACT, UPS, A, 11, WRN,
Miscellaneous trap, e.g., bad battery.
For troubleshooting procedures, see Event #11
Trap (3)
upsAlarmShutdownPending
#12
Alarm string = #1, ACT, UPS, A, 12, WRN,
Miscellaneous trap, e.g., bad battery.
For troubleshooting procedures, see Event #12
Trap (3)1
upsAlarmShutdownImminent
#13
Alarm string = #1,ACT, UPS, A, 13, MAJ,
Miscellaneous trap, e.g., bad battery.
For troubleshooting procedures, see Event #13
Trap (3)1
upsAlarmDepletedBattery
#14
Alarm string =
#1,ACT,UPS,A,14,MAJ,Miscellaneous trap, e.g.,
bad battery.
For troubleshooting procedures, see Event #14
Trap (3)1
upsAlarmBatteryBad
#15
Alarm string =
#1,ACT,UPS,A,15,MIN,Miscellaneous trap, e.g.,
bad battery
For troubleshooting procedures, see Event #15
1 of 3
106 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
UPS (Uninterruptible Power Supply)
Table 29: Enterprise-Specific UPS Traps to Server 2 of 3
SNMP Trap from UPS
Event
ID
Definition of Trap
Trap (3)
upsAlarmInputBad
#16
Alarm string =
#1,ACT,UPS,A,16,MIN,Miscellaneous trap, e.g.,
bad battery
For troubleshooting procedures, see Event #16
Trap (3)
upsAlarmTempBad
#17
Alarm string =
#1,ACT,UPS,A,17,WRN,Miscellaneous trap, e.g.,
bad battery
For troubleshooting procedures, see Event #17
Trap (3)
upsAlarmCommunicationsLost
#18
Alarm string =
#1,ACT,UPS,A,18,WRN,Miscellaneous trap, e.g.,
bad battery
For troubleshooting procedures, see Event #18
Trap (3)
upsAlarmBypassBad
#19
Alarm string =
#1,ACT,UPS,A,19,MIN,Miscellaneous trap, e.g.,
bad battery
For troubleshooting procedures, see Event #19
Trap (3)
upsAlarmLowBattery
#20
Alarm string =
#1,ACT,UPS,A,20,WRN,Miscellaneous trap, e.g.,
bad battery
For troubleshooting procedures, see Event #20
Trap (3)
upsAlarmUpsOutputOff
#21
Alarm string =
#1,ACT,UPS,A,21,WRN,Miscellaneous trap, e.g.,
bad battery
For troubleshooting procedures, see Event #21
Trap (3)
upsAlarmOutputBad
#22
Alarm string =
#1,ACT,UPS,A,22,WRN,Miscellaneous trap, e.g.,
bad battery
For troubleshooting procedures, see Event #22
Trap (3)
upsAlarmOutputOverload
#23
Alarm string =
#1,ACT,UPS,A,23,WRN,Miscellaneous trap, e.g.,
bad battery
For troubleshooting procedures, see Event #23
Trap (3)
upsAlarmChargerFailed
#24
Alarm string =
#1,ACT,UPS,A,24,WRN,Miscellaneous trap, e.g.,
bad battery
For troubleshooting procedures, see Event #24
2 of 3
Issue 3 February 2007
107
Server Alarms
Table 29: Enterprise-Specific UPS Traps to Server 3 of 3
SNMP Trap from UPS
Event
ID
Definition of Trap
Trap (3) – upsAlarmFanFailure
#25
Alarm string =
#1,ACT,UPS,A,25,WRN,Miscellaneous trap, e.g.,
bad battery
For troubleshooting procedures, see Event #25
Trap (3) – upsAlarmFuseFailure
#26
Alarm string =
#1,ACT,UPS,A,26,WRN,Miscellaneous trap, e.g.,
bad battery
For troubleshooting procedures, see Event #26
Trap (3) –
upsAlarmGeneralFault
#27
#1,ACT,UPS,A,27,WRN,Miscellaneous trap, e.g.,
bad battery
For troubleshooting procedures, see Event #27
Trap (4), Event ID #9
upsAlarmOnBattery
9
Alarm string = #1, ACT, UPS, A, 9,WRN,
Miscellaneous trap, e.g., bad battery.
This UPS trap [Event #9] is a miscellaneous
environmental alarm sent from the UPS that
supports server A. For example, the battery may
be bad and should be replaced.
3 of 3
1. This event degrades the server’s state of health.
Back to:
Hardware MOs
Server-related alarms
UPS Alarms to the Media Server
S8700 | S8710 | S8720 | S8500 | S8300
Table 30: UPS Alarms describes the server’s UPS-related alarms and their troubleshooting
procedures.
Table 30: UPS Alarms 1 of 4
Event
ID
1–8
Alarm
Level
Alarm Text, Cause/Description, Recommendation
MAJ
“upsEstimatedMinutesRemaining” — UPS does not have an AC-power
source.
1. Restore AC power to the UPS.
1 of 4
108 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
UPS (Uninterruptible Power Supply)
Table 30: UPS Alarms 2 of 4
Event
ID
Alarm
Level
Alarm Text, Cause/Description, Recommendation
11
WRN
“upsAlarmonBattery” — The UPS is drawing power from the batteries. This
message should be accompanied by a "upsEstimatedMinutesRemaining"
message.
1. Restore AC power to the UPS.
12
MAJ
“upsAlarmShutdownPending” — A shutdown-after-delay countdown is
underway (i.e., the UPS has been commanded off).
1. Stop countdown timer. (Can be done via SNMP messages.)
13
MAJ
“upsAlarmShutdownImminent” — The UPS will turn off power to the load in
< 5 seconds.
1. Restore AC power to the UPS.
14
MAJ
“upsAlarmDepletedBattery” — If primary power is lost, the UPS could not
sustain the current load.
1. Charge or replace the batteries in the UPS, according to procedures in
its Site Preparation, Installation, and Operator’s Manual - See
appropriate manual for the UPS Model.
15
MAJ
“upsAlarmBatteryBad” — One or more batteries needs to be replaced.
1. Replace any defective batteries in the UPS, according to procedures in
its Site Preparation, Installation, and Operator’s Manual - See
appropriate manual for the UPS Model.
16
MIN
“upsAlarmInputBad” — An input condition is out of tolerance.
1. Provide appropriate AC power to the UPS.
17
MIN
“upsAlarmTempBad” — The internal temperature of a UPS is out of
tolerance. (On the UPS, the “over temperature” alarm indicator flashes,
and the UPS changes to Bypass mode for cooling. Either:
1. Look for and remove any obstructions to the UPS’s fans.
2. Wait at least 5 minutes, and restart the UPS.
3. Check for and resolve any fan alarms (Event ID 25) against the UPS.
4. Either:
●
Change (increase or decrease) the environment’s temperature.
●
Change the alarming thresholds.
2 of 4
Issue 3 February 2007
109
Server Alarms
Table 30: UPS Alarms 3 of 4
Event
ID
18
Alarm
Level
Alarm Text, Cause/Description, Recommendation
MIN
“upsAlarmCommunicationsLost” — The SNMP agent and the UPS are
having communications problems. (A UPS diagnosis may be required.)
1. Behind the UPS in its upper left-hand corner, verify that an SNMP card
(with an RJ45 connector) resides in the UPS — instead of a serial card
with DB9 and DB25 connectors.
2. Verify that the server is physically connected to the UPS via the RJ45
connector.
3. Verify that the SNMP card is properly administered according to the
procedures in its users guide, provided by the vendor.
4. If necessary, replace the SNMP card in the UPS.
5. If the problem persists, replace the UPS, and diagnose it later.
19
MIN
“upsAlarmBypassBad” — The “source” power to the UPS, which (during a
UPS overload or failure) also serves as “bypass” power to the load, is out of
tolerance — incorrect voltage by > ±12% or frequency > ±3%.
This on-line UPS normally regenerates its source power into clean AC
power for the load. However, the source power’s quality is currently
unacceptable as bypass power to the load).
1. Verify that the UPS expects the correct “nominal input voltage” from its
power source.
2. If so, restore acceptable AC power to the UPS.
If not, reconfigure the UPS to expect the correct voltage, according to
procedures in its Site Preparation, Installation, and Operator’s Manual See appropriate manual for the UPS Model.
20
WRN
“upsAlarmLowBattery” — The battery’s remaining run time ≤ specified
threshold.
1. Restore AC power to the UPS.
21
WRN
“upsAlarmUpsOutputOff” — As requested, UPS has shut down output
power. The UPS is in Standby mode.
1. Turn on output power. (Can be done via SNMP messages.)
22
WRN
“upsAlarmOutputBad” — A receptacle’s output is out of tolerance. (A UPS
diagnosis is required.)
1. Replace the UPS, and diagnose it later.
3 of 4
110 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
UPS (Uninterruptible Power Supply)
Table 30: UPS Alarms 4 of 4
Event
ID
Alarm
Level
Alarm Text, Cause/Description, Recommendation
23
WRN
“upsAlarmOutputOverload” — The load on the UPS exceeds its output
capacity. The UPS enters Bypass mode.
1. Reduce the load on the UPS.
2. Verify that the UPS returns to Normal mode.
24
WRN
“upsAlarmChargerFailed” — The UPS battery charger has failed. (A UPS
diagnosis is required.)
1. Replace the UPS, and diagnose it later.
25
WRN
“upsAlarmFanFailure” — One or more UPS fans have failed. Unless lightly
loaded, the UPS enters Bypass mode.
1. Replace the UPS, and diagnose it later.
26
WRN
“upsAlarmFuseFailure” — One or more UPS fuses have failed.
1. Replace the UPS, and diagnose it later.
27
WRN
“upsAlarmGeneralFault” — A general fault occurred in the UPS. (A UPS
diagnosis is required.)
1. Replace the UPS, and diagnose it later.
4 of 4
The maintenance strategy for UPS provides periodic and on-demand testing. The periodic test
runs the “handshake” test every 15 minutes. The on-demand tests include the Handshake Test,
Off-Hook Test, and Reset USB Test.
Back to:
Hardware MOs
Server-related alarms
Issue 3 February 2007
111
Server Alarms
USB1 (Modem)
S8700 | S8710 | S8720 | S8500
MO Name in Log
Alarm
Level
Initial Command to Run
USB1
MAJ
MIN
WRN
testmodem
Full Name of MO
USB Port Modem
The testmodem command provides the ability to reset the modem and perform offhook,
handshake, and looparound tests. The -l option causes the command to dial out to INADS
(Initialization and Administration System) and wait for an acknowledgement. The command is
described in Table 31: testmodem command usage.
112 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
USB1 (Modem)
Table 31: testmodem command usage
Usage: testmodem [ -s ] | [ -l | [ -t arg ] | [ -?]
no argument
Performs short test (offhook and handshake)
-s
Performs short test (offhook and handshake)
-l
Performs long test (offhook, handshake, and
looparound to INADS)
-t reset_usb
Resets the modem
-t handshake
Handshakes with the modem
-t offhook
Requests the modem to go offhook
-t looparound
Dials out to INADS and waits for a response
-?
Displays the command usage
The following errors may be displayed:
1: Run almcall command to administer
the telephone numbers
Alarm configuration has not been done. Use the
oss command to configure the phone number and
try again.
2: No telephone number configured Use almcall to administer
The OSS phone number was not configured. Use
the oss command to configure the phone number
and try the command again.
3: Failed to create socket
The command could not allocate a system
resource. Wait a few minutes and try the command
again.
4: Failed to connect to SME
The command could not connect to the server to
process the command. Verify that Communication
Manager is running and the Server Maintenance
Engine (SME) is running by entering the Linux
command statapp
5: failed to send request to SME
The request could not be sent to the server. Verify
that Communication Manager is running by
entering the Linux command statapp
6: Failed to receive response from
SME
The test did not receive a response from the
server. The system may be hung. Verify that
Communication Manager is running by entering
the Linux command statapp
Issue 3 February 2007
113
Server Alarms
Table 32: USB1 Event IDs and Alarm Text contains the Event IDs, alarm text, and
recommended command to enter for USB1 alarms.
Table 32: USB1 Event IDs and Alarm Text
Event
ID
Alarm
Level
Alarm Text
Test To
Investigate
Command to Enter
1
MIN
"USB Modem
Handshake Test Failed"
Handshake Test
testmodem -t handshake
2
MIN
"USB Modem Offhook
Test Failed"
Off-Hook Test
testmodem -t off-hook
3
MAJ
None
Reset USB Test
testmodem -t reset_usb
Handshake Test
This test is destructive.
This test verifies that the system can “handshake” with the attached modem hardware.
The following messages can be displayed:
Table 33: Handshake Test
Error
Message
Test
Result
Description / Recommendation
Modem in
use, try again
later
ABORT
Another application is currently using the modem. Try again later.
Could not
open USB
port
ABORT
System error: An attempt to open the USB device failed.
1. Retry the test in about 5 minutes.
2. If the test still aborts, escalate the problem.
Read error,
could not run
test
ABORT
A probable system error aborted the test.
1. Retry the test in about 5 minutes.
2. If the test still aborts, escalate the problem.
Modem
Handshake
Test Failed
FAIL
The modem did not handshake with the system.
1. Retry the test in about 5 minutes.
2. If the test still fails, escalate the problem.
114 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
USB1 (Modem)
Off-Hook Test
This test is destructive.
This test runs an off-hook test for the modem attached to the USB port on the server. The test
verifies that a line is connected to the modem. The following messages can be displayed:
Table 34: Off-Hook Test
Error
Message
Test
Result
Description / Recommendation
Modem in
use, try again
later
ABORT
Another application is currently using the modem. Try again later.
Could not
open USB
port
ABORT
An attempt to open the USB device failed. Try again later
Read error,
could not run
test
ABORT
A probable system error aborted the test. Try again. If the test
continues to abort, escalate the problem.
Modem
Off-Hook Test
Failed
FAIL
Modem Off-Hook test failed. Dial tone was not detected in the
time allowed.
1. Retry the test.
2. If the test still aborts, escalate the problem.
Issue 3 February 2007
115
Server Alarms
Reset USB Test
This test is destructive.
This test causes the modem to be reset if the modem is not in use. The following messages can
be displayed:
Table 35: Reset USB
Error Code
Test
Result
Description / Recommendation
Could not
open USB port
ABORT
System error: An attempt to open the USB device failed. Try
again later.
Modem in use,
try again later
ABORT
Another application is using the modem. Try the test at a later
time.
Modem Reset
Test Failed
FAIL
The modem was not reset. Try the command again. If the test
continues to fail, escalate the problem.
Modem has
been reset
PASS
The modem was successfully reset.
Back to:
Hardware MOs
Server-related alarms
116 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
_WD (Watchdog)
_WD (Watchdog)
S8700 | S8710 | S8720 | S8500 | S8400 | S8300
The Watchdog is a media server process that:
●
Creates other Communication Manager processes
●
Monitors process sanity
●
Can recover process failures
Watchdog also communicates with a hardware-sanity device. For alarm-related information
about these services, see SVC_MON (Service Monitor).
Table 36: _WD Alarms describes the _WD alarms and their troubleshooting procedures.
Issue 3 February 2007
117
Server Alarms
Table 36: _WD Alarms 1 of 16
Event
ID
4
S8300
Alarm
Level
Alarm Text, Cause/Description, Recommendation
MAJ
“Application <name> (pid) TOTALLY FAILED” — An application is present
but not launching. The application could not start the maximum allowed
number of times. (This alarm usually occurs with Event ID #20.)
1. To verify the alarm, look for the application’s name or process ID
(PID),” either using the:
- Web interface, by selecting Diagnostics > View System Logs and
Watchdog Logs
- Linux command line, by entering logv -w or, directly, by
examining /var/log/ecs/wdlog
2. If the application is down, enter start -s application to start the
application.
3. If the application comes up, continue with Step 7.
If the application does not come up, check the trace log to further
investigate why the application fails, either from the:
- Web interface by:
a. Selecting the View System Logs diagnostic and
Logmanager Debug trace
b. Specifying the Event Range for the appropriate time frame
c. Matching the application’s PID as the pattern
- Linux command line, by entering logv -t ts
Look for a related core-dump file in /var/crash, and escalate for an
analysis of this file.
4. Verify that the file named in the log exists and is executable.
To locate the application’s executable file, enter the Linux command:
ls -l /opt/ecs/sbin/appl
If the executable is present, Linux returns a symbolic link to its
location.
1 of 16
118 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
_WD (Watchdog)
Table 36: _WD Alarms 2 of 16
Event
ID
Alarm
Level
4
(cont’d)
MAJ
Alarm Text, Cause/Description, Recommendation
5. If so (less common):
a. Enter ls -l on the symbolic link’s address.
b. Verify that the executable has “execution” permissions.
c. If not, enter chmod +x to enable execution of the application.
If not — Linux has returned a “null link” (more common):
- Acquire the executable from the CD.
6. Enter start -s application to start the application.
7. Manually clear the alarm, either from the:
- Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
- Linux command line, by entering almclear -n #id
8. If the problem recurs, escalate the problem.
2 of 16
Issue 3 February 2007
119
Server Alarms
Table 36: _WD Alarms 3 of 16
Event
ID
5
Alarm
Level
Alarm Text, Cause/Description, Recommendation
MIN
“WARNING: timeout waiting for reqsvr to initialize” — During each server’s
boot process, the server’s Watchd process waits up to 2 minutes for its
“reqsvr” (request server) thread to initialize. If the 2-minute waiting interval
elapses, this server logs this alarm, and its boot process hangs.
(Meanwhile, if the other server is already booted or subsequently boots, it
assumes the active role.)
In that (when this alarm occurs) a server hangs during its booting process,
this alarm’s external symptoms resemble those of two other _WD alarms,
#13 (Except S8500) and #14 (Except S8500). Therefore, carefully
discriminate between these three events.
1. To inspect the symptoms of this problem, verify that the:
a. Linux OS and the Web interface are up (including the commands:
telnet, statapp, server, logv, cat, grep, tail, vi, etc.)
b. Watchdog application is partially up, but no other Communication
Manager software is up
c. The almdisplay command displays no alarms. Instead, the
command returns the message:
“almdisplay: 4: Unable to connect to
MultiVantage”
Since the following commands cause a brief service outage, they should
only be executed at the customer’s convenience.
2. Escalate this problem for explicit guidance with the following steps.
3. Enter server to verify that the suspected server is the standby.
If necessary and at the customer’s convenience, enter server -if
to force a server interchange.
4. Reboot the standby server, either from the:
- Web interface, by selecting Shutdown This Server
- Linux command line, by entering /sbin/shutdown -r now
5. Once the standby server has booted, verify that Event ID #5 was
logged, either using the:
- Web interface, by selecting Diagnostics > View System Logs and
Watchdog Logs
- Linux command line, by entering logv -w or, directly, by
examining /var/log/ecs/wdlog.
3 of 16
120 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
_WD (Watchdog)
Table 36: _WD Alarms 4 of 16
Event
ID
Alarm
Level
5
(cont’d)
MIN
6
MAJ
S8300
Alarm Text, Cause/Description, Recommendation
6. If rebooting the server does not help or if the problem recurs, escalate
the problem to the next higher tier.
“Application <name> (pid) not started, config parm errors” — Watchdog
cannot read its configuration file, /etc/opt/ecs/watchd.conf.
1. To verify the alarm, look for the application’s name or process ID
(PID), either using the:
- Web interface, by selecting Diagnostics > View System Logs and
Watchdog Logs
- Linux command line, by entering logv -w or, directly, by
examining /var/log/ecs/wdlog.
2. Get a fresh copy of watchd.conf from the CD.
3. Verify that every executable file listed in watchd.conf exists and is
executable.
4. Enter start -s application to start the application.
5. Manually clear the alarm, either from the:
- Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
- Linux command line, by entering almclear -n #id
4 of 16
Issue 3 February 2007
121
Server Alarms
Table 36: _WD Alarms 5 of 16
Event
ID
7
S8300
Alarm
Level
Alarm Text, Cause/Description, Recommendation
MAJ
“Application <name> not started, parm file errors” — Since an
application’s specified location in watchd.conf is incorrect, Watchdog
cannot start the application.
1. To verify the alarm, look for the application’s or process ID (PID),
either using the:
- Web interface, by selecting Diagnostics > View System Logs and
Watchdog Logs
- Linux command line, by entering logv -w or, directly, by
examining /var/log/ecs/wdlog.
2. Verify that the executable file named in the log exists and is
executable.
To locate the application’s executable file, enter the Linux command:
ls -l /opt/ecs/sbin/appl
If the executable is present, Linux returns a symbolic link to its
location.
3. If so (less common):
a. Enter ls -l on the symbolic link’s address.
b. Verify that the executable has “execution” permissions.
c. If not, enter chmod +x to enable execution of the application.
If not — Linux has returned a “null link” (more common):
- Acquire the executable from the CD.
4. Verify that the string in watchd.conf is correct.
5. Enter start -s application to start the application.
6. Manually clear the alarm, either from the:
- Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
- Linux command line, by entering almclear -n #id
5 of 16
122 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
_WD (Watchdog)
Table 36: _WD Alarms 6 of 16
Event
ID
13
(Except
S8500)
Alarm
Level
Alarm Text, Cause/Description, Recommendation
MIN
“ERROR: could not dup socket fd in reqsvr.c, heartbeat thread not created,
errno=<x>” — As either a:
●
●
Booting application initiates
Restarting application re-initiates heart beating with Watchdog (see
Event ID #5), the “reqsvr” (request server) thread tries to create a
duplicate socket for the hearbeating thread. This alarm indicates that
reqsvr could not create the socket. (Meanwhile, if the other server is
already started or subsequently starts, it assumes the active role.)
In that (when this alarm occurs) a server hangs, this alarm’s external
symptoms resemble those of two other _WD alarms, #5 and #14
(Except S8500). Therefore, carefully discriminate between these
three events.
1. To inspect the symptoms of this problem, verify that the:
a. Linux OS and the Web interface are up (including the commands:
telnet, statapp, server, logv, cat, grep, tail, vi, etc.)
b. Watchdog application is partially up, and some other
Communication Manager processes may be up, either using the:
- Web interface, by selecting View Process Status
- Linux command line, by entering statapp
c. If the GMM process is up, the almdisplay -v command shows
Event #13’s message string.
If not, the Watchdog log shows the message string, either using
the:
- Web interface, by selecting Diagnostics > View System Logs
and Watchdog Logs
- Linux command line, by entering logv -w or, directly, by
examining /var/log/ecs/wdlog.
Since the following commands cause a brief service outage, they should
only be executed at the customer’s convenience.
2. Escalate this problem for explicit guidance with the following steps.
3. Enter server to verify that the suspected server is the standby.
If necessary and at the customer’s convenience, enter server -if
to force a server interchange.
6 of 16
Issue 3 February 2007
123
Server Alarms
Table 36: _WD Alarms 7 of 16
Event
ID
13
(Except
S8500)
(cont’d)
Alarm
Level
MIN
Alarm Text, Cause/Description, Recommendation
4. Reboot the standby server, either from the:
- Web interface, by selecting Shutdown This Server
- Linux command line, by entering /sbin/shutdown -r now
5. If rebooting the server does not help or if the problem recurs, escalate
the problem to the next higher tier.
14
(Except
S8500)
MIN
“ERROR in req2svr.p trying to create heartbeat thread, errno=<x>” — After
the “reqsvr” (request server) creates a duplicate socket (see Event ID #13
(Except S8500)), it tries to create a heart beating thread. This alarm
indicates that reqsvr could not create the thread. (Meanwhile, if the other
server is already started or subsequently starts, it assumes the active role.)
In that (when this alarm occurs) a server hangs, this alarm’s external
symptoms resemble those of two other _WD alarms, #5 and #13 (Except
S8500). Therefore, carefully discriminate between these three events.
1. To inspect the symptoms of this problem, verify that the:
a. Linux OS and the Web interface are up (including the commands:
telnet, statapp, server, logv, cat, grep, tail, vi, etc.)
b. Watchdog application is partially up, but all other Communication
Manager processes are up, either using the:
- Web interface, by selecting View Process Status
- Linux command line, by entering statapp
c. The almdisplay -v command shows Event #14’s message
string
Since the following commands cause a brief service outage, they should
only be executed at the customer’s convenience.
2. Escalate this problem for explicit guidance with the following steps.
3. Enter server to verify that the suspected server is the standby.
If necessary and at the customer’s convenience, enter server -if
to force a server interchange.
4. Reboot the standby server, either from the:
- Web interface, by selecting Shutdown This Server
5. If rebooting the server does not help or if the problem recurs, escalate
the problem to the next higher tier.
7 of 16
124 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
_WD (Watchdog)
Table 36: _WD Alarms 8 of 16
Event
ID
15
S8300
Alarm
Level
Alarm Text, Cause/Description, Recommendation
MAJ
“Detected a rolling reboot” — Watchdog has detected “x” number of Linux
reboots within “y” minutes (where x and y are configurable in /etc/opt/
ecs/watchd.conf). Rolling reboots have a wide variety of possible
causes.
1. To verify the alarm, look for the message, “WARNING: Rolling reboot
detected!!,“either using the:
- Web interface, by selecting Diagnostics > View System Logs and
Watchdog Logs
- Linux command line, by entering logv -w or, directly, by
examining /var/log/ecs/wdlog.
2. Escalate this problem for explicit guidance with the following steps.
3. Paying special attention to Communication Manager errors, continue
examining the Watchdog log (from Step 1), and try to determine which
application failed.
4. Verify that every executable file listed in watchd.conf exists and is
executable. Rolling reboots are often caused by executables in
unexpected locations.
5. If the files and their locations are OK, investigate the trace log to
isolate the cause, either from the:
- Web interface by:
a. Selecting the View System Logs diagnostic and
Logmanager Debug trace
b. Specifying the Event Range for the appropriate time frame
c. Matching the “rolling reboot” pattern
- Linux command line, by entering logv -t ts
8 of 16
Issue 3 February 2007
125
Server Alarms
Table 36: _WD Alarms 9 of 16
Event
ID
Alarm
Level
Alarm Text, Cause/Description, Recommendation
18
WRN
“Application <name> restarted. Retry <retry count>, New Pid: <pid>” —
An application has failed, and Watchdog successfully restarted it.
S8300
1. To verify the alarm, look for the application’s name or process ID (pid),
either using the:
- Web interface, by selecting Diagnostics > View System Logs and
Watchdog Logs
- Linux command line, by entering logv -w or, directly, by
examining /var/log/ecs/wdlog.
2. No resolution. Manually clear the alarm, either from the:
- Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
- Linux command line, by entering almclear -n #id
9 of 16
126 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
_WD (Watchdog)
Table 36: _WD Alarms 10 of 16
Event
ID
19
S8300
Alarm
Level
Alarm Text, Cause/Description, Recommendation
MIN
“Application failed unintentionally” — Watchdog is bringing the system
down because an application failed to start correctly. The application may
have failed to start either because:
●
●
The file did not exist (coincident with Event ID #7).
Required application parameters were missing or invalid in
watchd.conf.
1. To verify the alarm, look for the message, “Application num <#>
(<application path>) not started. Watchdog exiting NOW,” either using
the:
- Web interface, by selecting Diagnostics > View System Logs and
Watchdog Logs
- Linux command line, by entering logv -w or, directly, by
examining /var/log/ecs/wdlog.
2. Verify that the file named in the log exists and is executable.
3. Verify that the string in watchd.conf is correct.
4. If Steps 2 and 3 are OK, investigate the trace log to see why the
application fails, either from the:
- Web interface by:
a. Selecting the View System Logs diagnostic and
Logmanager Debug trace
b. Specifying the Event Range for the appropriate time frame
c. Matching the application’s number as the pattern
- Linux command line, by entering logv -t ts
5. Once resolved, manually clear the alarm, either from the:
- Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
- Linux command line, by entering almclear -n #id
10 of 16
Issue 3 February 2007
127
Server Alarms
Table 36: _WD Alarms 11 of 16
Event
ID
20
S8300
Alarm
Level
Alarm Text, Cause/Description, Recommendation
MAJ
“Application <name> (pid) TOTALLY FAILED” — Application failed the
maximum allowed number of times. (This alarm usually occurs with Event
ID #4.)
1. To verify the alarm, look for the application’s name or process ID
(PID), either using the:
- Web interface, by selecting Diagnostics > View System Logs and
Watchdog Logs
- Linux command line, by entering logv -w or, directly, by
examining /var/log/ecs/wdlog.
- See if the application is up, either from the:
- Web interface, by selecting View Process Status
- Linux command line, by entering statapp
2. If the application is down, enter start -s application to start the
application.
3. If the application comes up, continue with Step 7.
If not, check the trace log to further investigate why the application
fails, either from the:
- Web interface by:
a. Selecting the View System Logs diagnostic and
Logmanager Debug trace
b. Specifying the Event Range for the appropriate time frame
c. Matching the application’s PID as the pattern
- Linux command line, by entering logv -t ts
4. To locate the application’s executable file, enter the Linux command:
ls -l /opt/ecs/sbin/appl
If the executable is present, Linux returns a symbolic link to its
location.
11 of 16
128 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
_WD (Watchdog)
Table 36: _WD Alarms 12 of 16
Event
ID
20
(cont’d)
Alarm
Level
MAJ
Alarm Text, Cause/Description, Recommendation
5. If so (less common):
a. Enter ls -l on the symbolic link’s address.
b. Verify that the executable has “execution” permissions.
c. If not, enter chmod +x to enable execution of the application.
If not — Linux has returned a “null link” (more common):
- Acquire the executable from the CD
6. Enter start -s application to start the application.
7. Manually clear the alarm, either from the:
- Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
- Linux command line, by entering almclear -n #id
8. If the problem recurs, escalate the problem.
12 of 16
Issue 3 February 2007
129
Server Alarms
Table 36: _WD Alarms 13 of 16
Event
ID
22
S8300
Alarm
Level
Alarm Text, Cause/Description, Recommendation
MIN
“Application <name> (<pid>) terminated” — Watchdog successfully shut
down the named application, and (if appropriate) watchdog will try to
restart it.
1. To verify the alarm, look for the application’s name or process ID
(PID), either using the:
- Web interface, by selecting Diagnostics > View System Logs and
Watchdog Logs
- Linux command line, by entering logv -w
2. On the standby server, look for occurrences of the stop command,
either from the:
- Web interface, by:
a. Selecting View System Logs
b. Selecting Platform command history log
c. Specifying the Event Range for the appropriate time frame
d. Matching the “Stop” pattern
- Linux command line, by entering listhistory
3. If a stop command was inappropriately executed, prevent any future
misuse of the stop command.
Note: From the system’s perspective, this is normal behavior.
However, in terms of potential service outage due to human error, this
is quite irregular. (Shutting down a server effectively downgrades a
duplex-, high- or critical-reliability system to an unsupported
standard-reliability system.)
4. If listhistory shows no stop commands, then Watchdog
responded to abnormal internal processes by shutting down the
application.
Check the trace log for information about this application, either from
the:
- Web interface, by:
a. Selecting the View System Logs diagnostic and
Logmanager Debug trace
b. Specifying the Event Range for the appropriate time frame
c. Matching the application’s PID as the pattern
- Linux command line, by entering logv -t ts
13 of 16
130 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
_WD (Watchdog)
Table 36: _WD Alarms 14 of 16
Event
ID
22
Alarm
Level
MIN
S8300
Alarm Text, Cause/Description, Recommendation
5. Manually clear the alarm, either from the:
- Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
(cont’d)
- Linux command line, by entering almclear -n #id
6. Watch to see if the alarm recurs. If so, escalate the problem.
23
S8300
MAJ
“Watchd high-monitor thread is rebooting the system” — The:
1. Lo-monitor thread is missing heartbeats (can't get CPU time).
2. Hi-monitor thread has tried 3 times to recover the system by killing any
infinitely looping processes.
If after 3 CPU-occupancy profiles and recoveries, the lo-monitor thread is
still not heartbeating, then Watchd reboots the server.
3. To verify the alarm, look for messages:
Containing the CPU profiling results and attempted recoveries
Stating that Watchd is rebooting the server
using either the:
- Web interface, by selecting Diagnostics > View System Logs and
Watchdog Logs
- Linux command line, by entering logv -w or, directly, by
examining /var/log/ecs/wdlog.
A resolution is probably unnecessary. The server has usually rebooted
by the time a technician can analyze the system. (A reboot clears the
alarm and normally fixes problems with unresponsive software.)
4. Watch to see if the alarm recurs. If so, escalate the problem.
14 of 16
Issue 3 February 2007
131
Server Alarms
Table 36: _WD Alarms 15 of 16
Event
ID
24
Alarm
Level
Alarm Text, Cause/Description, Recommendation
MAJ
“Watchd’s high-monitor thread is stopping tickling of hw” — Event ID #23’s
call to reboot the server was unsuccessfully invoked. (A Linux kernel’s
semaphore is possibly stuck.) After this happens, Watchd stops tickling
the HW sanity timer so that the HW sanity watchdog executes a hard
reboot of the processor.
S8300
1. To verify that the alarm occurred, look for messages about:
Stopping the tickling of the HW sanity timer
CPU occupancy profiling
using either the:
- Web interface, by selecting Diagnostics > View System Logs
and Watchdog Logs
- Linux command line, by entering logv -w or, directly, by
examining /var/log/ecs/wdlog.
- If the HW sanity watchdog successfully executed a hard reboot,
the alarm was cleared. (This reboot normally fixes problems due
to unresponsive software.)
If not, power cycle the server to release it from this condition and to
clear the alarm.
2. Watch to see if the alarm recurs. If so, escalate the problem.
26
MIN
“Watchd handshake error” — IF USB alarms are also present, this
strongly points to a global SAMP or networking problem. This error
implies:
●
the SAMP is missing
●
the SAMP is malfunctioning
●
the SAMP is not configured properly
●
the firewall on the server is not configured
●
●
the SAMP firmware is not correct for the Communication Manager
version
the server Ethernet port is misconfigured.
1. Refer to the SAMP User Guide for troubleshooting procedures
(03-300322).
2. Escalate the problem.
15 of 16
132 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
_WD (Watchdog)
Table 36: _WD Alarms 16 of 16
Event
ID
27
Alarm
Level
Alarm Text, Cause/Description, Recommendation
MAJ
“Free memory on the system is low” —
1. To verify that the alarm occurred, look for messages about:
Stopping the tickling of the HW sanity timer
CPU occupancy profiling
using either the:
- Web interface, by selecting Diagnostics > View System Logs
and Watchdog Logs
- Linux command line, by entering logv -w or, directly, by
examining /var/log/ecs/wdlog.
16 of 16
Back to:
Hardware MOs
Server-related alarms
Issue 3 February 2007
133
Server Alarms
Login Alarms - S8300
S8300
Table 37: Login Alarms describes the S8300 media server login alarms and their
troubleshooting procedures.
Table 37: Login Alarms
Event
ID
Alarm
Level
Cause/Description, Recommendation
1
WRN
Using the Web Interface, select View Current Alarms.
1. Notify the customer.
2
WRN
Using the Web Interface, select View Current Alarms.
1. Notify the customer.
3
MIN
Security violation.
1. Using the Web Interface, select View Current Alarms.
2. Notify the customer.
4
MIN
Security violation.
1. Using the Web Interface, select View Current Alarms.
2. Notify the customer.
5
MAJ
Security violation.
1. Using the Web Interface, select View Current Alarms.
2. Notify the customer.
Back to:
Hardware MOs
Server-related alarms
134 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
S8710 Alarms
S8710 Alarms
S8710 Environmental Alarms
The S8710 Environmental maintenance objects (ENV) are monitored within the server,
including temperature and fans.
To check the S8710 server temperature and voltage readings:
1. On the Maintenance Web Page, select Diagnostics > Temperature/Voltage.
2. The Temperature/Voltage page is displayed.
Issue 3 February 2007
135
Server Alarms
3. Use the descriptions in Table 38 to interpret the report.
Table 38: S8710 Temperature and voltage report
Field
Description
ID
An identification number automatically generated by the system.
Type
Power supply:
●
Intelligent—power regulating
●
Standard—other
Fan: speeds include
●
Var Speed—variable speed
●
Basic Fan—fixed speed
●
Auto. Speed—automatic speed fan
●
Pwr Supply—power supply
●
Unknown
Temperature: Basic Sensor—generic; ADM1022; Internal PS; Unknown
Type
Location
The device location in the media server.
Status
For power supplies and fans:
●
Normal—operating normally
●
Alarm—having a problem
Redundant
For all types: Yes, No, or NA
Fan Speed
Fans: percentage of full speed.
●
Unknown
●
Automatic—For Auto. Speed Fans, no speed state
●
Low—< 30%
●
Medium—30%–70%
●
High—> 70%, reporting state: High state
●
Normal—reporting state: Normal state
●
Off
Current
Temperature: current temperature of the device, in degrees Fahrenheit and
Celsius.
Threshold
Temperature: above for which an alarm is generated, in degrees Fahrenheit
and Celsius.
136 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
S8710 Alarms
S8710 Server BIOS Error Messages
The S8710 server BIOS error messages are listed and interpreted in Table 39: S8710 BIOS
error messages.
Table 39: S8710 BIOS error messages
Error
Code
Description
Audible
Beeps
Possible Problem
Possible Action
207
Memory configuration
warning; DIMM in DIMM
Socket X is not 4 bytes
wide (32 bits) and only
supports standard ECC.
None
Installed DIMMs are
8 bytes wide (64
bits).
Escalate; replace
the media server
209
Online spare memory
configuration; spare bank
is invalid. Mixing of DIMMs
with 4 and 8 byte widths is
not allowed in this mode.
One
long and
one
short
Installed DIMMs for
online spare bank
are of a different
primary width than
the DIMMs in other
banks.
Escalate; replace
the media server
NA
A mixture of 533-MHz and
400-MHz front side bus
speed processors
detected. All processors
must have the same front
side bus speed. System
halted.
One
long and
one
short
Wrong processors;
Processors have
different front side
bus speeds.
Escalate; replace
the media server
NA
Media server only supports
400-MHz front side bus
speed processors. One or
more 533-MHz front side
bus speed processors
have been initialized at 400
MHz.
One
long and
one
short
Wrong processors;
Media server does
not support a front
side bus speed of
533 MHz.
Escalate; replace
the media server
Issue 3 February 2007
137
Server Alarms
138 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Chapter 2: Denial Events
The tables in this chapter define and explain the information listed on the Events Report
(display events screen). The Event Type tables are grouped by denial event category,
denial event number, and Communication Manager release number. The Event Tables list:
●
●
●
●
The number that identifies the Event Type. See Table 40: Denial Event types and
ranges on page 140. If the Event Type number defines different denial events in different
Communication Manager releases, that information is also listed.
Event Description text, as it appears on the Events Report (display events type
denial).
An explanation of why the event was generated.
Type of data in Event Data 1 and Event Data 2 fields, for each applicable Event Type,
where this information is available. See Event Data on page 141.
To view denial events, use:
●
display events type denial (to see historical denial event logs)
●
list trace station
●
list trace TAC
Enter list trace to see any available Calling Party Number and Calling Party Name
associated with call setup.
Issue 3 February 2007
139
Denial Events
Event Type number ranges
Event Type number ranges help define the type and source of the denial event, as listed in
Table 40: Denial Event types and ranges. Some numbers are placeholders and have no
assigned denial event.
Table 40: Denial Event types and ranges 1 of 2
Number range
Type/source of denial event
Reference
0 - 999
Vector process
Avaya Communication Manager Call Center Software Call
Vectoring and Expert Agent Selection (EAS) Guide,
07-300186.
Hunt/Trunk Group Vector
process
Avaya Communication Manager Call Center Software Call
Vectoring and Expert Agent Selection (EAS) Guide,
07-300186.
Call Process
Table 50: Call Process denial events (1001 - 1172) on
page 191.
● 1000 - 1299
Call Process, reorder
Table 50: Call Process denial events (1001 - 1172) on
page 191 and Table 52: Call Process denial events (1225 1899) on page 207.
● 1164, 1167,
Call Process, ISDN, IP, SIP
Table 51: ISDN, IP, and SIP-generated denial events (1173
- 1224) on page 204.
● 1300 - 1899
Call Process, intercept
Table 52: Call Process denial events (1225 - 1899) on
page 207.
● 1900 - 1906
User Manager process
Table 53: User Manager denial events (1900 - 1906) on
page 242.
● 1907 - 2079
IP
Table 54: IP Denial Events (1907 - 2020) on page 243.
● 2021-2299
Call Process
Table 55: Call Process denial events (2021 - 2299) on
page 254.
2300 - 2399
Connection Manager process
Table 56: Connection Manager denial events (2300 2399) on page 271.
2400 - 2499
Dial Plan Manager process
Table 57: Dial Plan Manager denial events (2400 - 2406) on
page 274.
3000 - 3100
Data Manager process
Table 58: Data Manager generated Denial Events (3001 3003) on page 275.
3101 - 3200
Dial Access Plan process
Table 59: Dial Access Plan denial events (3101 - 3200) on
page 275.
3201 - 3299
Meetme Conference process
Table 60: Meet Me Conference denial events (3201 3299) on page 276.
3300 - 3399
LSP process
Table 61: LSP denial events (3300 - 3399).
● 500 - 999
1000 - 2299
1173 - 1224
1 of 2
140 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Event Data
Table 40: Denial Event types and ranges 2 of 2
Number range
Type/source of denial event
Reference
3400 - 3499
Data Error (corruption) process
Table 62: Data Error denial events (3400 - 3499) on
page 278.
3500 - 3599
Contact Closure process
Table 63: Contact Closure denial events (3500 - 3503) on
page 279.
3600 - 3604
ESS process
Table 64: ESS denial events (3600 - 3604) on page 280.
2 of 2
Event Data
Use Event Data information to isolate mistranslation and/or mismatched provisioning.
Event Data might contain the information for:
●
Internal User ID (UID) of a component involved in the call (station, IP User, gatekeeper)
●
Product ID
●
Object ID
●
IP Address
●
Extension
●
IP Address involved in the call
●
TTI State
●
Numeric reason code explained in the tables in this chapter
●
Numeric code showing the Cause Value, Cause Value Diagnostic, and Location Code for
the event. See Cause Values and their meanings/interpretations on page 142.
Issue 3 February 2007
141
Denial Events
Cause Values and their meanings/interpretations
See Table 51: ISDN, IP, and SIP-generated denial events (1173 - 1224) on page 204 for the
Denial Events that show Cause Value information (Cause Value, Location Code, and Diagnostic
Code) in Event Data 2 fields.
Event Data 2 sometimes contains data that represents the Cause Value (CV) (required), Cause
Value Diagnostic (DIAG) (optional), Location Code (LC) (optional) from the denial event. This
information (DIAG/LOC/CV) is coded as a 32 bit hexadecimal number, divided into 8-bit fields.
The least significant (right most) two digits are the Cause Value in hexadecimal.
●
The next two digits to the left are the Location Code (optional) in hexadecimal. See
Table 44: Location Code definitions on page 144.
●
●
The next two digits to the left are the Diagnostic Code (optional) in hexadecimal.
●
The most significant (left most) two digits are not used.
See Table 41: Event Data 2 layout.
Table 41: Event Data 2 layout
8 bits
8 bits
8 bits
8 bits
NOT USED
Diagnostic Code
(DIAG) (optional)
Zero + Location Code in lower 4 bits
(LOC) (optional)
Cause Value
(CV) (required)
Interpreting Event Data 2 Cause Value information
In our example, we will use Denial Event 1178 with Event Data 1 and Event Data 2.
display events denial
Page
1
of
EVENTS REPORT
Event Event
Type Description
Event
Data 1
Event
Data 2
1178
0x64
0x429
Normal Call Clearing
First
Occur
Last
Occur
Evnt
Cnt
01/09/09:53 01/09/09:53
1. Note the information under the Event Data 2 column: 0x429.
●
0x29 is the Cause Value.
●
0x4 is the Location Code.
●
0x00 is the Diagnostic Code (not provided for this denial event).
142 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
1
1
Event Data
2. Convert the hexadecimal number provided in Event Data 2 to three binary numbers: put a
one in the appropriate binary number positions that add up to the value of the number.
Each binary number consists of eight bits. See Table 42: Event Data 2 conversion
example on page 143 for an example of the hexadecimal number 0x429, and
Table 43: Hexadecimal, decimal, and binary equivalents on page 144 for the binary
equivalents for individual digits.
3. Add up the decimal weights that have a one for each of the eight bit segments.
●
Convert Cause Value 0x29 to decimal and find the sum.
Cause Value (Bits 1 - 8): 1 +8 + 32 = 41. This is Cause Value 41.
●
Convert Location Code 0x4 to decimal and find the sum.
Location Code (Bits 9 - 16): 4 = 4. This is Location Code 4.
●
Convert Diagnostic Value 0x00 (Bits 17 - 24): 0 = 0.
Diagnostic Code is 0, not provided for this example denial event.
4. Use the information in this chapter to find an explanation of the Data Event 2 information.
●
●
Cause Value 41 = Temporary Failure. See Cause Values on page 148.
Location Code 4 = Remote Network/Public Network Serving Remote User (the Local
Exchange Carrier at the far end of the call). See Table 44: Location Code definitions on
page 144.
Table 42: Event Data 2 conversion example
Diagnostic Code
Location Code
Cause Value
Event Data 2
0
0
0
4
2
9
Binary number
0
0
0
0
0
0
0
0
0
0
0
0
1
0
0
0
0
1
0
1
0
0
1
8
4
2
1
8
4
2
1
8
4
2
1
8
4
2
1
Decimal weight of each digit position
8
4
2
1
8
4
2
1
Decimal weight of the binary positions for each eight-bit field
128
64
32
16
8
4
2
1
128
64
32
16
8
4
2
1
128
64
32
16
8
4
2
1
21
20
19
18
17
16
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
Bit position
24
23
22
Issue 3 February 2007
143
Denial Events
.
Table 43: Hexadecimal, decimal, and binary equivalents
HEX
Decimal
Binary
Hex
Decimal
Binary
0
0
0000
8
8
1000
1
1
0001
9
9
1001
2
2
0010
A
10
1010
3
3
0011
B
11
1011
4
4
0100
C
12
1100
5
5
0101
D
13
1101
6
6
0110
E
14
1110
7
7
0111
F
15
1111
Location Codes
See Table 51: ISDN, IP, and SIP-generated denial events (1173 - 1224) on page 204 for the
Denial Events that show Cause Value information (Cause Value, Location Code, and Diagnostic
Code) in Event Data 2 fields.
Use the location information of Event Data 2 to identify where in the network the called number
failed to be recognized, and from where the Cause Value originated. See Table 44: Location
Code definitions.
Table 44: Location Code definitions 1 of 2
Location
Code
Definition
0
User
1
Private Network Serving Local User.
The Local PBX or phone system on the Called Party premise
2
Public Network serving the Local User (the CO to which the PBX is directly
connected).
3
Transit network. For example, the long distance network to which the call was
passed by the LEC.
4
Public Network Serving Remote User [the Local Exchange Carrier (LEC) at the far
end of the call].
1 of 2
144 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Event Data
Table 44: Location Code definitions 2 of 2
Location
Code
Definition
5
Private Network Serving Remote User (the remote PBX or phone system on the
Called Party premises).
7
International.
A
Network beyond inter-networking point.
2 of 2
Transmission Protocols
See Table 51: ISDN, IP, and SIP-generated denial events (1173 - 1224) on page 204 for the
Denial Events that show Cause Value information (Cause Value, Location Code, and Diagnostic
Code) in Event Data 2 fields.
The meaning of the Denial Event Data information differs depending on the type of protocol
used for the call. The transmission protocol for your system is defined on the DS1 screen (add/
change/display ds1 location command) by:
●
The numeric country code value in the Protocol field - sets the country protocol.
●
The letter value for the protocol version in the Protocol Version field.
See Table 45: Country Codes and Transmission Protocols.
Table 45: Country Codes and Transmission Protocols 1 of 3
Country Code –
Protocol Version
Country
Protocol Supported
B-channel
Maint.
Message
Inter-working
Message
1-a
US-Canada
AT&T TR 41449 / 41459
SERVICE
PROGRESS
1-b
US
Bellcore TR1268;
NIUF.302;
ANSI T1.607
RESTART
PROGRESS
1-c
US-Canada
Nortel A211
AT&T TR 4449/41459
(with Layer 3 timers
adjusted)
SERVICE
PROGRESS
1-d
US
Bellcore TR3268
SERVICE
PROGRESS
2
Australia
AUSTEL TS014.1;
Telcom Australia TPH 1856
RESTART
PROGRESS
1 of 3
Issue 3 February 2007
145
Denial Events
Table 45: Country Codes and Transmission Protocols 2 of 3
Country Code –
Protocol Version
Country
Protocol Supported
B-channel
Maint.
Message
Inter-working
Message
3
Japan
NTT INS-NET
RESTART
ALERTING
4
Italy
ETS 300 102
RESTART
PROGRESS
5
Netherlands
ETS 300 102
RESTART
PROGRESS
6
Singapore
ETS 300 102
RESTART
PROGRESS
7
Mexico
ETS 300 102
RESTART
PROGRESS
8
Belgium
ETS 300 102
RESTART
ALERTING
9
Saudi Arabia
ETS 300 102
RESTART
PROGRESS
10-a
UK
ETS 300 102 (Connect to
DASS II/DPNSS through
external converter)
RESTART
PROGRESS
10-b
UK
ETS 300 102 (Mercury)
British Telcom ISDN 30
NONE
ALERTING
11
Spain
Telefonica ISDN Spec
RESTART
PROGRESS
12-a
France
VN4 (French National PRI)
NONE
ALERTING
12-b
France
Modified ETS 300 102
according to P10-20
(Euronumeris)
NONE
ALERTING
13-a
Germany
FTZ 1 TR 6
(German National PRI)
NONE
ALERTING
13-b
Germany
ETS 300 102
RESTART
ALERTING
14
Czech Republic
/ Slovakia
ETS 300 102
RESTART
PROGRESS
15
RUSSIA (CIS)
ETS 300 102
RESTART
PROGRESS
16
Argentina
ETS 300 102
RESTART
PROGRESS
17
Greece
ETS 300 102
RESTART
PROGRESS
18
China
ETS 300 102
RESTART
PROGRESS
19
Hong Kong
ETS 300 102
RESTART
PROGRESS
20
Thailand
ETS 300 102
RESTART
PROGRESS
2 of 3
146 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Event Data
Table 45: Country Codes and Transmission Protocols 3 of 3
Country Code –
Protocol Version
Country
Protocol Supported
B-channel
Maint.
Message
Inter-working
Message
21
Macedonia
ETS 300 102
RESTART
PROGRESS
22
Poland
ETS 300 102
RESTART
PROGRESS
23
Brazil
ETS 300 102
RESTART
PROGRESS
ETSI-a
Europe, etc.
ETS 300 102
RESTART
PROGRESS
ETS 300 102
NONE
PROGRESS
ETS 300 102
RESTART
PROGRESS
ETSI-b
QSIG
Private network
3 of 3
Cause Values
The Data Event 2 field on the display events screen sometimes contains Cause Value
information (DIAG/LOC/CV). Use this information to identify the Cause Value for each denial
event. The following information lists classes of Cause Values, their meaning and
interpretations, and associated translations.
See Table 51: ISDN, IP, and SIP-generated denial events (1173 - 1224) on page 204 for the
Denial Events that show Cause Value information (Cause Value, Location Code, and Diagnostic
Code) in Event Data 2 fields.
Cause Value Classes
Table 46: Cause Value Classes and Ranges 1 of 2
Number range
Cause Value Class
empty to 33
Normal Class Cause Values on page 148
●
12, 14, 15, 24
34 to 47
●
36, 48
49 to 63
●
55, 60, 64
unassigned
Resource Unavailable Class Cause Values on page 161
unassigned
Service or Option not Available Class Cause Values on page 165
unassigned
1 of 2
Issue 3 February 2007
147
Denial Events
Table 46: Cause Value Classes and Ranges 2 of 2
Number range
Cause Value Class
65 to 79
Service or Option not Implemented Class Cause Values on page 172
●
67, 68, 71-78, 80
81 to 95
●
92-94
96 to127
●
104-109, 116-126
unassigned
Invalid Message Class Cause Values on page 175
unassigned
Protocol Error Class Cause Values on page 179
unassigned
2 of 2
Cause Values
Normal Class Cause Values
Cause Value (empty)
[]Normal call clearing (1TR6: AT&T ISDN Protocol)
The call was disconnected normally by either end hanging up.
This Cause Value has end-to-end significance and should always be passed back through the
network to the user.
Cause Value 00
[0x0/0x80] Normal disconnect
The call was disconnected normally by either end hanging up. Most equipment uses Cause
Value 16 to report normal disconnect.
Cause Value 01
[0x1/0x81] Unassigned (Unallocated number)/
Invalid Call Reference Value (CRV) (1TR6: AT&T ISDN Protocol)
The call could not be completed because the number requested in the SETUP message is not
assigned/allocated by the ISDN network.
This Cause Value has end-to-end significance and should always be passed back through the
network to the user.
148 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Event Data
See also Cause Value 22 on page 157 and Cause Value 56 on page 168.
Troubleshooting
●
Check the numbers sent to see if any prefixes or service values that were needed to
access the network were not sent.
●
Check the Cause Value Information Element (LOC). See Location Codes on page 144.
●
Check Communication Manager administration.
- Dial-plan/Location: The home NPA is administered incorrectly, causing incorrect code
conversion.
- IXC: The IXC matching pattern is administered incorrectly or not at all on the dial-plan,
causing incorrect IXC manipulation.
- AAR/ARS digit conversion: The wrong digit string substitution is being made. The call is
being routed into the wrong network and over the wrong route pattern. Further
conversion is needed, but the dial string is restricted from further conversion.
- AAR/ARS digit analysis: Call type is incorrect for the call being made specifying the
wrong type of number and/or number plan information, or it is preventing code
conversion from taking place. Call is being routed to the incorrect route pattern where the
incorrect digit manipulation and/or code conversion is taking place.
- ARS toll analysis: Toll/no toll classification is incorrect, causing incorrect code conversion
at the route pattern.
- Route pattern: Incorrect code conversion due to wrong entries in NPA, prefix mark, and
toll list/prefix mark fields. Deleting the wrong number of digits or inserting the wrong
digits. Failing to strip IXC or international code digits, stripping a user-dialed IXC code, or
IXC forcing the call to the wrong interexchange carrier.
- Trunk Group: The incorrect service or feature is specified for the call being made on a
CBC trunk group preference. The number format is being changed to a format incorrect
for the call type.
Cause Value 02
[0x2/0x82] No route to specified transit network/
Calling party off hold (5ESS: 5 Electronic Switching System)
The ISDN service provider’s equipment cannot route the call through the specified network. The
network either does not exist or is not compatible with the ISDN service provider’s equipment.
This Cause Value has local significance only. The ISDN network between the user and the
equipment generating the Cause Value might:
●
Send no cause indication through the network.
●
Send a more generic Cause Value through the network.
Because this Cause Value has only local significance, on tandem calls Communication
Manager might map it to Cause Value 31 instead of passing it back through the network.
Issue 3 February 2007
149
Denial Events
Troubleshooting
●
●
●
●
Check the diagnostic information (DIAG) for the transit network identity of the unreachable
network. See Cause Values and their meanings/interpretations on page 142.
Check the numbers sent for any missing prefixes or service values that were needed to
access the network.
Check that the call type (data, voice, fax) can be routed between the ISDN networks
serving both ends of the call.
Check that the bearer capabilities of the call are acceptable to the ISDN network serving
both ends of the call.
●
Check the Cause Value Information Element (LOC). See Location Codes on page 144.
●
Check Communication Manager administration.
- AAR/ARS digit analysis: Call type is incorrect for the call being made specifying the
wrong type of number and/or number plan information, or it is preventing code
conversion from taking place. Call is being routed to the incorrect route pattern where the
incorrect digit manipulation and/or code conversion is taking place.
- Route pattern: Incorrect digits or IXC were inserted. Incorrect number of digits were
deleted. An incorrect ITC and/or BCIE were specified, affecting the SETUP message
bearer capability encoding. An incorrect service or feature was specified for the
preference. The number format specified is wrong for the call type.
- The ITC administered on the originating endpoint might be incorrect for this call.
- Incorrect data speed option is set in the BRI device, causing a call from a BRI endpoint
tandeming through Communication Manager to create a SETUP message with the
wrong bearer capability.
Cause Value 03
[0x3/0x83] No route to destination/
Calling party dropped while on hold (5ESS: 5 Electronic Switching System)/
Bearer service not implemented (1TR6: AT&T ISDN Protocol)
The ISDN service provider cannot route the call to the indicated destination. Communication
Manager does not originate Cause Value 03.
Troubleshooting
●
Check the numbers sent for any missing prefixes or service values that were needed to
access the network.
●
Check the Cause Value Information Element (LOC). See Location Codes on page 144.
●
Check Communication Manager administration.
- Dial-plan/Location: The home NPA is administered incorrectly, causing incorrect code
conversion.
150 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Event Data
- IXC: The IXC matching pattern is administered incorrectly or not at all on the dial-plan,
causing incorrect IXC manipulation.
- AAR/ARS digit conversion: The wrong digit string substitution is being made. The call is
being routed into the wrong network and over the wrong route pattern. Further
conversion is needed but the dial string is restricted from further conversion.
- AAR/ARS digit analysis: Call type is incorrect for the call being made specifying the
wrong type of number and/or number plan information, or it is preventing code
conversion from taking place. Call is being routed to the incorrect route pattern where the
incorrect digit manipulation and/or code conversion is taking place.
- ARS toll analysis: Toll/no toll classification is incorrect, causing incorrect code conversion
at the route pattern.
- Route pattern: Incorrect code conversion due to wrong entries in NPA, prefix mark, and
toll list/prefix mark fields. Deleting the wrong number of digits or inserting the wrong
digits. Failing to strip IXC or international code digits, stripping a user-dialed IXC code, or
IXC forcing the call to the wrong interexchange carrier. Number format changed to a
format incorrect for the call type. The incorrect service or feature is specified for the call
being made on a CBC trunk group preference.
Cause Value 04
[0x4/0x84] Send special information tone/
Vacant Code (NI-2: National ISDN 2)
Cause Value 04 indicates the remote number that was dialed could not be reached.
Cause Value 04 (NI-2) indicates that the destination requested by the calling party cannot be
reached because the Numbering Plan Area (NPA) or Central Office (CO) code is vacant
(unassigned).
Troubleshooting
●
Check the numbers sent for any missing prefixes or service values that were needed to
access the network.
●
Check the Cause Value Information Element (LOC). See Location Codes on page 144.
●
Check Communication Manager administration.
- Dial-plan/Location: The home NPA is administered incorrectly, causing incorrect code
conversion.
- IXC: The IXC matching pattern is administered incorrectly or not at all on the dial-plan,
causing incorrect IXC manipulation.
- AAR/ARS digit conversion: The wrong digit string substitution is being made. The call is
being routed into the wrong network and over the wrong route pattern. Further
conversion is needed but the dial string is restricted from further conversion.
Issue 3 February 2007
151
Denial Events
- AAR/ARS digit analysis: Call type is incorrect for the call being made specifying the
wrong type of number and/or number plan information, or it is preventing code
conversion from taking place. Call is being routed to the incorrect route pattern where the
incorrect digit manipulation and/or code conversion is taking place. An incorrect service
or feature is specified for the call being made on a CBC trunk group preference.
Changing the Number format to a format incorrect for the call type.
- ARS toll analysis: Toll/no toll classification is incorrect, causing incorrect code conversion
at the route pattern.
- Route pattern: Incorrect code conversion due to wrong entries in NPA, prefix mark, and
toll list/prefix mark fields. Deleting the wrong number of digits or inserting the wrong
digits. Failing to strip IXC or international code digits, stripping a user-dialed IXC code, or
IXC forcing the call to the wrong interexchange carrier.
Cause Value 05
[0x5/0x85] Misdialed trunk prefix
The remote number that was dialed could not be reached.
Troubleshooting
●
Check the numbers sent for any missing prefixes or service values that were needed to
access the network.
●
Check the Cause Value Information Element (LOC). See Location Codes on page 144.
●
Check Communication Manager administration.
- Dial-plan/Location: The home NPA is administered incorrectly, causing incorrect code
conversion.
- IXC: The IXC matching pattern is administered incorrectly or not at all on the dial-plan,
causing incorrect IXC manipulation.
- AAR/ARS digit conversion: The wrong digit string substitution is being made. The call is
being routed into the wrong network and over the wrong route pattern. Further
conversion is needed but the dial string is restricted from further conversion.
- AAR/ARS digit analysis: Call type is incorrect for the call being made specifying the
wrong type of number and/or number plan information, or it is preventing code
conversion from taking place. Call is being routed to the incorrect route pattern where the
incorrect digit manipulation and/or code conversion is taking place.
- ARS toll analysis: Toll/no toll classification is incorrect, causing incorrect code conversion
at the route pattern.
- Route pattern: Incorrect code conversion due to wrong entries in NPA, prefix mark, and
toll list/prefix mark fields. Deleting the wrong number of digits or inserting the wrong
digits. Failing to strip IXC or international code digits, stripping a user-dialed IXC code, or
IXC forcing the call to the wrong interexchange carrier.
152 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Event Data
- AAR/ARS digit analysis: Call type is incorrect for the call being made specifying the
wrong type of number and/or number plan information, or it is preventing code
conversion from taking place. An incorrect service or feature is specified for the call being
made on a CBC trunk group preference. Changing the Number format to a format
incorrect for the call type.
Cause Value 06
[0x6/0x86] Channel Unacceptable
The call attempt failed because the requested channel is not acceptable to the ISDN service
provider.
Troubleshooting
●
Check Communication Manager administration.
- B-channels might be assigned off a T1/E1 into a trunk group that are not available for
service from the remote end. Contact the ISDN service provider to find out which
B-channels can be used.
Cause Value 07
[0x7/0x87] Call awarded and being delivered in an established channel/
Call identity does not exist (1TR6: AT&T ISDN Protocol)
Cause Value 07 indicates that a new incoming call is being established and is being connected
on a channel that has previously been connected to the same user for similar type calls.
Cause Value 07 (1TR6) indicates that a call resume has been attempted for a call with an
identity different from any currently suspended calls.
Not an option for ISDN D-channels.
Cause Value 08
[0x8/0x88] Preemption/
Prefix 0 dialed in error (NI-2: National ISDN 2)/
Call identity in use (1TR6: AT&T ISDN Protocol)/
Call is proceeding (NI-1: National ISDN 1)
Cause Value 08 For Autovon switching networks, the call attempt was blocked by a call with a
higher priority.
Cause Value 08 (NI-2) indicates that the network does not want to receive the prefix digit 0 as
part of the digit string in the CALLED PARTY NUMBER.
Cause Value 08 (1TR6) indicates that the call identity that sent in the call resume request is
already in use by the network.
Issue 3 February 2007
153
Denial Events
Troubleshooting
Wait and try the call again later.
Cause Value 09
[0x9/0x89] Preemption, circuit reserved for reuse/
Prefix 1 dialed in error (NI-2: National ISDN 2)
Cause Value 09 For Autovon switching networks, the call attempt was blocked by a call with a
higher priority reserving the requested channel for reuse.
Cause Value 09 (NI-2) indicates that the network does not want to receive the prefix digit 1 as
part of the digit string in the CALLED PARTY NUMBER.
Troubleshooting
Wait and try the call again later.
Cause Value 10
[0xA/0x8A] Prefix 1 not dialed (NI-2: National ISDN 2)/
No channel available (1TR6: AT&T ISDN Protocol)
Cause Value 10 (N1-2) indicates that he user must send the prefix digit 1 as part of the
CALLED PARTY NUMBER.
Cause Value 10 (1TR6) indicates that the call cannot be completed because there is no
appropriate circuit/channel presently available to handle the call request, or that congestion
exists within the ISDN network.
This Cause Value has end-to-end significance and should always be passed back through the
network to the user.
Cause Value 11
[0xB/0x8B] Excessive digits received call proceeding (NI-2: National ISDN 2)
The equipment received more address digits in the CALLED PARTY NUMBER IE than
expected during call origination procedures, and the received address information has been
truncated.
Cause Value 13
[0xD/0x8D] Service Denied (NI-1: National ISDN 1)
154 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Event Data
Cause Value 16
[0x10/0x90] Normal call clearing/
Requested facility not implemented (1TR6: AT&T ISDN Protocol)
Cause Value 16 indicates that the call was disconnected normally by either end hanging up.
Cause Value 16 (1TR6) indicates that the call could not be completed because the equipment
sending this Cause Value does not support the requested service, feature, or supplementary
service in the SETUP message.
This Cause Value has end-to-end significance and should always be passed back through the
network to the user.
Troubleshooting
●
●
●
Check the diagnostic information (DIAG) for the facility identifier of the not implemented
service. See Cause Values and their meanings/interpretations on page 142.
If the remote device terminated the connection unexpectedly, contact the person
responsible for the remote end to determine if there is a problem with the remote endpoint.
For data bearer capability calls, if the connection has failed to establish, but the CONNECT
and CONNECT_ACK messages were exchanged before the DISCONNECT was
received, the handshake between the devices involved in the call might have failed due to:
- Option settings with the endpoint devices
- Bandwidth constriction issues on the B-channel used by the two devices to make the call
Cause Value 17
[0x11/0x91] User busy/
Requested facility not subscribed (1TR6: AT&T ISDN Protocol)
Cause Value 17 indicates that the endpoint called is unable to accept another call.
Cause Value 17 (1TR6) indicates that the call could not be completed because the user has not
subscribed to the service, feature, or supplementary service requested in the SETUP message.
This Cause Value has end-to-end significance and should always be passed back through the
network to the user.
See also Cause Value 16 on page 155 and Cause Value 31 on page 160.
Troubleshooting
●
●
Wait and try the call again later.
If the user is supposed to have access to the service, feature, or supplementary service,
complete the ordering process with the ISDN service provider.
Issue 3 February 2007
155
Denial Events
●
Check the Cause Value Information Element (LOC).
- If the location information of the Cause Value is 4, “public network serving the remote
user”, the trunk group to the remote endpoint location might be experiencing an “all
trunks busy” condition or not enough channels allocated into a virtual group for the
particular NSF of the call.
- If the location information of the Cause Value is 0, “user”, the endpoint might be busy.
●
If Communication Manager is generating this Cause Value, and the endpoint is not busy,
check the following Communication Manager administration.
- Trunk group screen: Usage Allocation is y on the CBC Service Type field. Not enough
incoming channels have been allocated for the NSF associated with this call.
- VDNs and Call vectoring: Analyze the vector processing and the call flow to determine
where the failure is occurring. VDN vector administration might incorrectly send the call
to a “busy” vector step. The call might go to a skill/Automatic Call Distribution (ACD)
group queue that is full and cannot accept any more calls. Look Ahead Interflow/Best
Service Routing (LAI/BSR) might receive an inappropriate ISDN response while
checking other sites for available agents and return busy feedback to the caller. The LAI/
BSR attempt might interact with the public network features Egress on busy – overflow to
POTS, Alternate Destination Routing (ADR), or Alternate Destination Call Redirection
(ADCR).
- Trunk and/or station Class of Restriction (COR) might prevent the call from terminating at
the endpoint.
- The endpoint might be call forwarded, and this is the second call within the 30-second
time limit on a station call-forwarding a call.
Cause Value 18
[0x12/0x92] No user responding/
No response from the remote device
The remote device/endpoint/PBX did not respond with an ALERTING/PROGRESS/CONNECT
indication within the time administered in the T303 or T310 timers Q.931 specification.
Cause Value 18 indicates high traffic conditions in the serving ISDN network or noisy conditions
on the T1/E1 span carrying the d-channel messaging. The noise is causing the loss of
messages being sent to the remote device. The remote device might also be unable to respond
to the incoming SETUP request.
This Cause Value has end-to-end significance and should always be passed back through the
network to the user.
156 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Event Data
Cause Value 19
[0x13/0x93] User alerting no answer
The remote device returned an alerting [ringing] indication but did not provide a connect
indication within the period of time prescribed by timer T301.
Communication Manager never originates this Cause Value.
Troubleshooting
Wait and retry the call later.
Cause Value 20
[0x14/0x94] Subscriber absent [wireless networks]
The mobile remote device/endpoint is not available.
Troubleshooting
Wait and try the call again later.
Cause Value 21
[0x15/0x95] Call rejected
The remote endpoint did not accept this call, even though the equipment is neither busy nor
incompatible and it could have accepted the call.
Check the diagnostic information (DIAG) for the user-supplied condition for why the call was
rejected. See Cause Values and their meanings/interpretations on page 142.
Cause Value 22
[0x16/0x96] Number changed
The called party number was changed to a new number.
Cause Value 01 appears if the ISDN network does not support Cause Value 22.
A BRI or Adjunct Switch Application Interface (ASAI) application might generate Cause Value
22. Communication Manager does not originate Cause Value 22 for PRI.
This Cause Value has end-to-end significance and should always be passed back through the
network to the user.
Check the diagnostic information (DIAG) for the new number. See Cause Values and their
meanings/interpretations on page 142.
Issue 3 February 2007
157
Denial Events
Cause Value 23
[0x17/0x97] Redirection to new destination
The call has been redirected to a different endpoint.
Communication Manager does not originate Cause Value 23.
Cause Value 25
[0x19/0x99] Exchange routing error
The call cannot be routed to the remote party.
Cause Value 26
[0x1A/0x9A] Non-selected user clearing
The call was cleared before the called endpoint was awarded the incoming call.
Cause Value 27
[0x1B/0x9B] Destination out of order
The call cannot be delivered to the remote endpoint because the interface to the endpoint is not
functioning correctly. A signaling message could not be delivered to the remote device (for
example, there is a physical or data link layer failure at the remote device, or the remote device
is turned off).
Communication Manager does not originate Cause Value 27.
Cause Value 28
[0x1C/0x9C] Invalid number format (address incomplete)
Special intercept announcement (NI-1: National ISDN 1)
The called endpoint could not be reached because the CALLED PARTY NUMBER information
is not in a valid format or is not complete.
This Cause Value has end-to-end significance and should always be passed back through the
network to the user.
158 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Event Data
Troubleshooting
●
Check the Cause Value Information Element (LOC). See Location Codes on page 144.
●
Check Communication Manager administration (network generated the Cause Value).
- Dial-plan/Location: The home NPA is administered incorrectly, causing incorrect code
conversion.
- IXC: The IXC matching pattern is administered incorrectly or not at all on the dial-plan,
causing incorrect IXC manipulation.
- AAR/ARS digit conversion: The wrong digit string substitution is being made. The call is
being routed into the wrong network and over the wrong route pattern. Further
conversion is needed but the dial string is restricted from further conversion.
- AAR/ARS digit analysis: Call type is incorrect for the call being made specifying the
wrong type of number and/or number plan information, or it is preventing code
conversion from taking place. Call is being routed to the incorrect route pattern where the
incorrect digit manipulation and/or code conversion is taking place.
- ARS toll analysis: Toll/no toll classification is incorrect, causing incorrect code conversion
at the route pattern.
- Route pattern: Incorrect NPA is causing incorrect code conversion. If the Prefix mark
field has the wrong value, incorrect code conversion takes place. Toll list in combination
with prefix mark is causing incorrect code conversion to take place. The wrong number of
digits are deleted, or failed to strip IXC digits or international code digits. Inserted the
wrong digits IXC forcing the call to the wrong inter-exchange carrier, or stripped out a
user dialed IXC code. The incorrect service or feature is specified for the call being made
on a CBC trunk group preference. The Number format was changed to a format incorrect
for the call type.
●
Check administration (Communication Manager generated the Cause Value).
- Trunk group: Incoming call handling table might cause Communication Manager to
delete or insert the wrong digits or number of digits to match the dial-plan.
Cause Value 29
[0x1D/0x9D] Facility rejected/
Special intercept announcement undefined code (NI-1: National ISDN 1)
The call could not be completed because the ISDN network does not support or is not
subscribed to the network service or feature requested for use by this call.
This Cause Value has end-to-end significance and should always be passed back through the
network to the user.
Issue 3 February 2007
159
Denial Events
Troubleshooting
●
●
Check the diagnostic information (DIAG) for the facility identifier of the service that was
rejected. See Cause Values and their meanings/interpretations on page 142.
Check Communication Manager administration (network generated the Cause Value).
- Route pattern: The service or feature field contains an incorrect value for this route
preference. The ITC/BCIE fields might not indicate the correct information for a data call.
●
Check administration (Communication Manager generated the Cause Value).
- Trunk group form: the Service type field might indicate a static service type when the
network is sending NSF information. Change the field to indicate CBC service.
Cause Value 30
[0x1E/0x9E] Response to STATUS_ENQUIRY
Special intercept announcement number unassigned (NI-1: National ISDN 1)
Cause Value 30 is included in a STATUS message when the STATUS message is generated
because a STATUS_ENQUIRY message was received. This is a normal event and does not
indicate a call-affecting problem. Communication Manager generates a call-state audit every
maintenance cycle that elicits this response from the remote end.
This Cause Value has local significance only. The ISDN network between the user and the
equipment generating the Cause Value might:
●
Send no cause indication through the network
●
Send a more generic Cause Value through the network
Cause Value 31
[0x1F/0x9F] Normal unspecified/
Special intercept announcement call blocked due to group restriction (NI-1: National
ISDN 1)
Cause Value 31 reports a normal event when no other cause in the normal class applies.
The ISDN network might substitute this Cause Value for other causes generated within the
network that do not have end-to-end significance.
For most Cause Values with only local significance on tandem calls, Communication Manager
maps Cause Values to Cause Value 31. See also Cause Value 02 on page 149.
Cause Value 31 can also be used as a return code on BSR polling attempts instead of Cause
Value 16 or Cause Value 17 depending on which Cause Value has less impact/interaction on
the intervening ISDN network.
160 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Event Data
Cause Value 32
[0x20/0xA0] Outgoing calls barred (1TR6: AT&T ISDN Protocol)
The call could not be completed because the calling user does not have permission to make an
outgoing call.
This Cause Value has local significance only. The ISDN network between the user and the
equipment generating the Cause Value might:
●
Send no cause indication through the network
●
Send a more generic Cause Value through the network
Cause Value 33
[0x21/0xA1] User access busy (1TR6: AT&T ISDN Protocol)
Resource Unavailable Class Cause Values
Cause Value 34
[0x22/0xA2] No circuit/channel available/
Negative closed user group comparison (1TR6: AT&T ISDN Protocol)
Cause Value 34 indicates that the call cannot be completed because there is no appropriate
circuit/channel available to handle the call request, or congestion exists within the ISDN
network.
Communication Manager generates this Cause Value when a call is tandeming through
Communication Manager and the trunk group to be used for the outgoing leg is:
●
In “all trunks busy” condition
●
Otherwise unavailable for service
●
Unreachable from the incoming trunk group due to Class of Restriction (COR), FRL,
trunk-to-trunk transfer restrictions, or disconnect supervision restrictions
Cause Value 34 (1TR6) indicates that the packet mode call was rejected because the user is
not a member of the remote end’s Closed User Group (CUG), which is a feature associated with
packet mode calls similar to X.25 connection made over the ISDN D-channel.
Communication Manager does not support packet mode sessions on D-channels, therefore this
is not applicable to Communication Manager.
This Cause Value has end-to-end significance and should always be passed back through the
network to the user.
Issue 3 February 2007
161
Denial Events
Troubleshooting
●
Check Communication Manager administration (network generated the Cause Value).
- B-channels might be assigned off a T1/E1 into a trunk group that are not available for
service from the remote end. Contact the ISDN service provider to find out which
B-channels can be used.
●
Check administration that might cause Communication Manager to generate this Cause
Value.
- If all of the B-channels in a span are busied out or otherwise tied up by switch
maintenance but the D-channel is still up, an incoming call is rejected with this Cause
Value because the call cannot be negotiated to another span.
Cause Value 35
[0x23/0xA3] Non-existent closed user group (1TR6: AT&T ISDN Protocol)
The packet mode call was rejected because the equipment sending the Cause Value does not
recognize the requested Closed User Group (CUG), which is a feature associated with packet
mode calls similar to X.25 connection made over the ISDN D-channel.
Communication Manager does not support packet mode sessions on D-channels, therefore this
is not applicable to Communication Manager.
Cause Value 37
[0x25/0xA5] Semi-permanent connection not permitted (1TR6: AT&T ISDN Protocol)
Cause Value 38
[0x26/0xA6] Network out of order
The call was not completed because the ISDN network is not functioning correctly, and the
condition is likely to last a relatively long period of time. Immediately reattempting the call will
probably be unsuccessful.
Cause Value 39
[0x27/0xA7] Permanent frame mode connection out of service
This appears to be a Q.933 frame relay Cause Value. Equipment failure might have caused
termination of a frame relay PVC.
Not applicable to a Communication Manager system.
162 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Event Data
Cause Value 40
[0x28/0xA8] Permanent frame mode connection is operational
This appears to be a Q.933 frame relay Cause Value. A frame relay PVC that was terminated
has been restored to service.
Not applicable to a Communication Manager system.
Cause Value 41
[0x29/0xA9] Temporary Failure
The call was not completed because the ISDN network is not functioning correctly. The
condition is not likely to last a long period of time. If the user attempts the call again it will
probably complete.
Cause Value 41 might also indicate:
●
The failure of channel negotiation at the terminating interface.
●
A data link layer malfunction has occurred locally or at the remote network interface.
●
The call is being cleared as a result of one or more protocol errors at the remote network
interface.
See also Cause Value 63 on page 171 and Cause Value 79 on page 174.
Cause Value 42
[0x2A/0xAA] Switching equipment congestion
The call could not be completed because the switching equipment generating this Cause Value
is experiencing a period of high traffic.
This Cause Value has end-to-end significance and should always be passed back through the
network to the user.
Troubleshooting
Wait and try the call again later.
Cause Value 43
[0x2B/0xAB] Access information discarded
The network could not deliver access or user information (such as low-layer compatibility or
calling-name information) to the remote endpoint for any one of various reasons. For example,
the call interworked from ISDN to non-ISDN facilities, or the remote end does not support
delivery of such information.
Issue 3 February 2007
163
Denial Events
This Cause Value is usually delivered in a STATUS message. Communication Manager
generates this Cause Value when:
●
●
●
A tandem call inter-works from ISDN to non-ISDN trunking.
Calling number and/or calling name information is sent in the SETUP message when it is
not needed.
Connected number information is sent when the network does not support it.
This Cause Value has end-to-end significance and should always be passed back through the
network to the user.
Check the diagnostic information (DIAG) for the Information Element identifier of the discarded
information. See Cause Values and their meanings/interpretations on page 142.
Cause Value 44
[0x2C/0xAC] Requested circuit/channel not available
The call was not completed because the circuit/channel requested for use in the SETUP
message was not available, and the call could not be negotiated to another channel either
because no other channel was available, or negotiation is not supported or was not wanted for
this call.
This Cause Value is generated when a glare condition is occurring and B-channel negotiation is
not supported.
Communication Manager generates this Cause Value when:
●
●
It is the NETWORK side of the interface and a glare condition is occurring on the
requested B-channel.
The B-channel requested in the incoming SETUP message is not in the correct
maintenance state to handle a call (for example, it is busied out or undergoing testing).
Troubleshooting
●
●
CO switch default settings turn off channel negotiation support. Make a specific request to
turn on channel negotiation support when ordering CO service.
Check Communication Manager administration (network generated the Cause Value).
- Trunk group form: When the Channel Negotiation field is set to exclusive,
Communication Manager requests B-channels for calls without support for negotiation so
if at the remote end the requested B-channel is unavailable for whatever reason the call
cannot be negotiated to a more acceptable B-channel and the call will be rejected with
Cause Value 44. Set the Channel Negotiation field to preferred to support channel
negotiation.
164 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Event Data
Cause Value 45
[0x2D/0xAD] Pre-empted
The call could not be completed because the equipment sending this Cause Value does not
have the requested B-channel in a maintenance state that allows for call requests to be
processed.
Communication Manager does not support this Cause Value.
Cause Value 46
[0x2E/0xAE] Precedence call Blocked
For Autovon switching networks, the call could not complete because the remote endpoint is
busy with a call that has a higher priority.
Cause Value 47
[0x2F/0xAF] Resource unavailable, unspecified/
New destination (4ESS/5ESS: 4/5 Electronic Switching System)
Cause Value 47 indicates a resource unavailable event only when no other cause in the
resource unavailable class applies.
Cause Value 47 (4ESS/5ESS) If this Cause Value is returned in a RELEASE_COMPLETE or
DISCONNECT message and the customer is an Alternate Destination Call Redirection (ADCR)
subscriber, it invokes call redirection.
Communication Manager does not originate Cause Value 47.
Service or Option not Available Class Cause Values
Cause Value 49
[0x31/0xB1] Quality of service unavailable
The call could not be completed because the quality of service requested in the SETUP as
defined in ITU recommendation X.213 cannot be provided (for example, requested throughput
or transit delay cannot be supported).
Issue 3 February 2007
165
Denial Events
Cause Value 50
[0x32/0xB2] Requested facility not subscribed
The call could not be completed because the user has not subscribed to the service, feature, or
supplementary service requested in the SETUP message. If the user is supposed to have
access to this service, feature, or supplementary service, then complete the required ordering
process with the ISDN service provider.
This Cause Value has end-to-end significance and should always be passed back through the
network to the user.
Communication Manager does not originate this Cause Value for PRI. A BRI or Adjunct Switch
Application Interface (ASAI) application might generate this Cause Value.
Communication Manager translations that can affect receiving this Cause Value from the
network are:
●
●
Route Pattern: service or feature: An incorrect service or feature is specified for the call
being made on this CBC trunk group preference. An incorrect ITC and/or BCIE is
specified. These fields affect how the bearer capability is encoded in the SETUP message.
The ITC administered on the originating endpoint might be incorrect for this call.
- Incorrect data speed option is set in the BRI device, causing a call from a BRI endpoint
tandeming through Communication Manager to create a SETUP message with the
wrong bearer capability.
●
●
●
On tandem calls through Communication Manager from ISDN trunks to ISDN trunks, an
inappropriate NSF can be tandemed from one D-channel to the other D-channel.
The problem is that the outgoing trunk group is CBC but no service or feature was
specified on the outgoing route pattern to overwrite the incoming NSF. Add the correct
service or feature to the route pattern or make the outgoing trunk group a static trunk
group (for example, public-network or tie) as appropriate.
System Parameters Features: The US NI send Calling Name ID field is y. Communication
Manager sends the Bellcore calling name ID but the customer has not subscribed to that
service. Set the US NI send Calling Name ID field to n.
Cause Value 51
[0x33/0xB3] Bearer capability incompatible with service request (NI-1: National ISDN 1)
The requested action could not be completed. The requested action is incompatible with the
bearer capability of the call (for example, trying to place a data call on hold).
166 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Event Data
Cause Value 52
[0x34/0xB4] Outgoing calls barred
The call could not be completed because the network screened the call, and the calling user is
not permitted to make an outgoing call.
This Cause Value has local significance only. The ISDN network between the user and the
equipment generating the Cause Value might:
●
Send no cause indication through the network
●
Send a more generic Cause Value through the network
Cause Value 53
[0x35/0xB5] Service operation violated (NI-1: National ISDN 1)/
Destination not obtainable (1TR6: AT&T ISDN Protocol)
Cause Value 53 (NI-1) indicates that the user has violated the service operation.
Cause Value 53 (1TR6) indicates that the call cannot be delivered to the remote endpoint
because the interface to the endpoint in not functioning correctly. A signaling message could not
be delivered to the remote device (for example, there is a physical or data link layer failure at
the remote device, or the remote device is turned off).
Cause Value 54
[0x36/0xB6] Incoming calls barred
The call could not complete because the called user is not allowed to accept the call delivered in
the SETUP message.
This Cause Value has end-to-end significance and should always be passed back through the
network to the user.
Troubleshooting
●
Check Communication Manager administration (network generated the Cause Value).
- Trunk group: Direction: The Communication Manager field might be set to two-way on a
trunk group that the ISDN network has configured as outgoing only, relative to the CO
switch, and a user on Communication Manager is attempting to make an outgoing call
over this trunk group, which is an incoming call to the CO.
- On tandem calls through Communication Manager from ISDN trunks to ISDN trunks, an
NSF for a one-way service (for example, Megacom 800) is being tandemed from one
D-channel to the other D-channel. The problem is that the outgoing trunk group is CBC
but no service or feature was specified on the outgoing route pattern to overwrite the
incoming NSF. Add the correct service or feature to the route pattern or make the
outgoing trunk group a static trunk group (for example, public-network or tie) as
appropriate.
Issue 3 February 2007
167
Denial Events
Cause Value 56
[0x38/0xB8] Number changed (1TR6: AT&T ISDN Protocol)
The called party number indicated has been changed to a new number that might be sent in the
diagnostic information (DIAG) for this Cause Value. See Cause Values and their meanings/
interpretations on page 142. If this Cause Value is not supported by the ISDN network, Cause
Value 01 is used instead.
This Cause Value has end-to-end significance and should always be passed back through the
network to the user.
Communication Manager does not originate this Cause Value for PRI. A BRI or Adjunct Switch
Application Interface (ASAI) application might generate this Cause Value.
Cause Value 57
[0x39/0xB9] Bearer capability not authorized/
Out of order (1TR6: AT&T ISDN Protocol)
Cause Value 57 indicates that the call could not be completed because the user has requested
a bearer capability in the SETUP message which is implemented by the equipment generating
this Cause Value, but user has not subscribed to it or in other ways is not authorized to use.
Cause Value 57 (1TR6) indicates that the call cannot be delivered to the remote endpoint
because the interface to the endpoint is not functioning correctly. A signaling message could not
be delivered to the remote device (for example, due to a physical or data link layer failure at the
remote device, or the remote device is turned off).
Troubleshooting
●
●
Check the diagnostic information (DIAG) for the unauthorized bearer capability attributes.
See Cause Values and their meanings/interpretations on page 142.
Check Communication Manager administration (network generated the Cause Value).
- Route pattern: An incorrect ITC and/or BCIE specified, these fields affect how the bearer
capability is encoded in the SETUP message.
- The ITC administered on the originating endpoint might be incorrect for this call, and/or
the speed options in the device itself might be incorrect for calls over these ISDN
facilities.
- Incorrect data speed option is set in the BRI device, causing a call from a BRI endpoint
tandeming through Communication Manager to create a SETUP message with the
wrong bearer capability.
- A call tandeming through Communication Manager ISDN trunk group to ISDN trunk
group might have a bearer capability that is not supported by the outgoing ISDN facilities
or network.
168 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Event Data
- A call tandeming through Communication Manager on a non-ISDN trunk group
inter-working to an ISDN trunk group might have an incorrect bearer capability assigned
on the incoming trunk group. The BC and ITC fields on the incoming trunk group might
be set wrong.
Cause Value 58
[0x3A/0xBA] Bearer capability not presently available/
No user responding (1TR6: AT&T ISDN Protocol)
This Cause Value has end-to-end significance and should always be passed back through the
network to the user.
Cause Value 58 indicates that the call could not be completed because the user has requested
a bearer capability in the SETUP message which is implemented by the equipment generating
this Cause Value, but for which there are presently no resources available to be used to
complete the call.
Troubleshooting
Wait and try the call again later.
Cause Value 58 (1TR6) indicates that the remote device/endpoint/PBX did not respond with an
ALERTING/PROGRESS/CONNECT indication within the prescribed period of time allocated by
the expiry of the T303 or T310 timers in the Q.931 specification.
Troubleshooting
●
●
Check the diagnostic information (DIAG) for the bearer capability attributes that are not
available. See Cause Values and their meanings/interpretations on page 142.
Check Communication Manager administration (network generated the Cause Value).
- Route pattern: An incorrect ITC and/or BCIE specified, these fields affect how the bearer
capability is encoded in the SETUP message.
- The ITC administered on the originating endpoint might be incorrect for this call, and/or
the speed options in the device itself might be incorrect for calls over these ISDN
facilities.
- Incorrect data speed option is set in the BRI device, causing a call from a BRI endpoint
tandeming through Communication Manager to create a SETUP message with the
wrong bearer capability.
- A call tandeming through Communication Manager ISDN trunk group to ISDN trunk
group might have a bearer capability that is not supported by the outgoing ISDN facilities
or network.
- A call tandeming through Communication Manager on a non-ISDN trunk group
inter-working to an ISDN trunk group might have an incorrect bearer capability assigned
on the incoming trunk group. The BC and ITC fields on the incoming trunk group might
be set wrong.
Issue 3 February 2007
169
Denial Events
Cause Value 59
[0x3B/0xBB] User busy (1TR6: AT&T ISDN Protocol)
The endpoint called has indicated an inability to accept another call.
This Cause Value has end-to-end significance and should always be passed back through the
network to the user.
Troubleshooting
●
Wait and try the call again later.
●
Check the Cause Value Information Element (LOC)
- If the Location Information of the Cause Value is 0 (User), the endpoint is probably busy.
- If the Location information of the Cause Value is 4 (Public Network Serving Remote
User), it is most likely that the trunk group to the remote endpoint location is experiencing
an “all trunks busy” condition or not enough channels allocated into a virtual group for the
particular NSF of the call.
●
If Communication Manager is generating this Cause Value and the endpoint is not busy,
the following translations and features could be affecting the call:
- Trunk and/or station Class of Restriction (COR) might be preventing the call from
terminating at the called endpoint.
- The endpoint might be call-forwarded and this is the second call within the 30-second
time limit on a station call forwarding a call.
- Trunk group form: CBC service type: Usage Allocation is y. The usage allocation plan
might not have allocated enough incoming channels for the NSF associated with this call.
- VDNs and Call Vectoring: The vector associated with the VDN might be incorrectly
programmed and the call is inappropriately sent to a busy vector step. The skill/
Automatic Call Distribution (ACD) group that the call is trying to queue to might have a
full queue and cannot accept any more calls. Look Ahead Interflow/Best Service Routing
(LAI/BSR) might have received an inappropriate ISDN response while checking other
sites for available agents and has inadvertently returned busy feedback to the caller. The
LAI/BSR attempt might be interacting with the public network features Egress on busy –
overflow to POTS, Alternate Destination Routing (ADR), or Alternate Destination Call
Redirection (ADCR). Analyze the vector processing of the call and the call flow to
determine where the failure is occurring.
Cause Value 61
[0x3D/0xBD] Incoming calls barred (1TR6: AT&T ISDN Protocol)
The call could not complete because the called user is not allowed to accept the call delivered in
the SETUP message.
This Cause Value has end-to-end significance and should always be passed back through the
network to the user.
170 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Event Data
Troubleshooting
●
Check Communication Manager administration (network generated the Cause Value).
- Trunk group: Direction: Communication Manager might be set to “two-way” on a trunk
group the ISDN network has configured as outgoing only, relative to the CO switch, and a
user on Communication Manager is attempting to make an outgoing call over this trunk
group, which is an incoming call to the CO.
- On tandem calls through Communication Manager from ISDN trunks to ISDN trunks, an
NSF for a one-way service (for example, Megacom 800) is being tandemed from one
D-channel to the other D-channel. The problem is that the outgoing trunk group is CBC
but no service or feature was specified on the outgoing route pattern to overwrite the
incoming NSF. Add the correct service or feature to the route pattern or make the
outgoing trunk group a static trunk group (for example, public-network or tie) as
appropriate.
Cause Value 62
[0x3E/0xBE] Service not authorized (VN4: French National PRI)/
Call rejected (1TR6: AT&T ISDN Protocol)
This Cause Value has end-to-end significance and should always be passed back through the
network to the user.
Cause Value 62 (VN4) indicates that the call could not be completed because the user has not
subscribed to the service, feature, or supplementary service requested in the SETUP message.
If the user is supposed to have access to this service, feature, or supplementary service, then
complete the required ordering process with the ISDN service provider.
Cause Value 62 (1TR6) indicates that the remote endpoint does not wish to accept this call,
although it could have accepted the call because the equipment is neither busy nor
incompatible.
The diagnostic information (DIAG) might be populated with the user-supplied condition for why
the call was rejected. See Cause Values and their meanings/interpretations on page 142.
Cause Value 63
[0x3F/0xBF] Service or option not available, unspecified
This Cause Value indicates that the requested service or option is unavailable when no other
cause in the Service or option not available class applies.
As an implementation option, this Cause Value shall either be passed to the user or mapped to
Cause Value 41 (Temporary Failure) when it is received at a CO as part of SS7 call handling.
Communication Manager does not originate Cause Value 63.
Issue 3 February 2007
171
Denial Events
Service or Option not Implemented Class Cause Values
Cause Value 65
[0x41/0xC1] Bearer capability not implemented
The call could not be completed because the equipment sending this Cause Value does not
support the bearer capability requested in the SETUP message.
This Cause Value has end-to-end significance and should always be passed back through the
network to the user.
Troubleshooting
The diagnostic information (DIAG) of the Cause Value should contain if implemented the bearer
capability attributes that are not implemented. See Cause Values and their meanings/
interpretations on page 142.
Cause Value 66
[0x42/0xC2] Channel type not implemented
The call could not be completed because the equipment sending this Cause Value does not
support the channel type requested in the SETUP message.
This Cause Value has end-to-end significance and should always be passed back through the
network to the user.
Troubleshooting
●
●
Check the diagnostic information (DIAG) for the unsupported channel type. See Cause
Values and their meanings/interpretations on page 142.
Check Communication Manager administration (network generated Cause Value):
- Communication Manager is attempting to make a wideband call over an interface to an
ISDN network that does not support wideband calls. Check the trunk group and routing
translations to be sure the attempted call has not inadvertently been routed to this
interface or was mis-classified as a wideband call.
●
Communication Manager administration that can affect sending of this Cause Value:
- The network is supporting wideband calling and Communication Manager does not have
wideband support enabled on the Wideband Switching field on the
system-parameters customer-options screen
- Communication Manager does not have wideband support enabled on the Wideband
Support field on the appropriate trunk group
- The trunk group does not have the correct type(s) of wideband channels enabled
- Communication Manager does not have the right size wideband endpoint programmed.
172 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Event Data
Cause Value 69
[0x45/0xC5] Requested facility not implemented
The call could not be completed because the equipment sending this Cause Value does not
support the requested service, feature, or supplementary service in the SETUP message.
This Cause Value has end-to-end significance and should always be passed back through the
network to the user.
Communication Manager does not originate this Cause Value for PRI. A BRI or Adjunct Switch
Application Interface (ASAI) application might generate this Cause Value.
Troubleshooting
●
●
Check the diagnostic information (DIAG) for the facility identifier of the not-implemented
service. See Cause Values and their meanings/interpretations on page 142.
Check Communication Manager administration (network generated the Cause Value).
- Route Pattern: service or feature: An incorrect service or feature is specified for the call
being made on this CBC trunk group preference. An incorrect ITC and/or BCIE specified,
these fields affect how the bearer capability is encoded in the SETUP message.
- The ITC administered on the originating endpoint might be incorrect for this call.
- Incorrect data speed option is set in the BRI device, causing a call from a BRI endpoint
tandeming through Communication Manager to create a SETUP message with the
wrong bearer capability.
- On tandem calls through Communication Manager from ISDN trunks to ISDN trunks, an
inappropriate NSF can be tandemed from one D-channel to the other D-channel. The
problem is that the outgoing trunk group is CBC but no service or feature was specified
on the outgoing route pattern to overwrite the incoming NSF. Add the correct service or
feature to the route pattern or make the outgoing trunk group a static trunk group (for
example, public-network or tie) as appropriate.
- System Parameters Features: US NI send Calling Name ID field is y. Communication
Manager sends the Bellcore calling name ID but the customer has not subscribed to that
service. Set the US NI send Calling Name ID field to n.
●
Communication Manager is attempting to send User-to-User information in a message
through the public network when not subscribed to a UUS service, for example Look
Ahead Interflow/Best Service Routing (LAI/BSR) information, Adjunct Switch Application
Interface (ASAI) information, etc.
Issue 3 February 2007
173
Denial Events
Cause Value 70
[0x46/0xC6] Only restricted digital information bearer capability is available
The call could not be completed because the equipment sending this Cause Value only
supports the restricted version of the requested bearer capability, and in the SETUP message
bearer capability was unrestricted.
Communication Manager does not originate Cause Value 70.
Troubleshooting
●
Check Communication Manager administration (network generated the Cause Value).
- Route pattern: An incorrect ITC and/or BCIE specified, these fields affect how the bearer
capability is encoded in the SETUP message.
- The ITC administered on the originating endpoint might be incorrect for this call, and/or
the speed options in the device itself might be incorrect for calls over these ISDN
facilities.
- Incorrect data speed option is set in the BRI device, causing a call from a BRI endpoint
tandeming through Communication Manager to create a SETUP message with the
wrong bearer capability.
- A call tandeming through Communication Manager ISDN trunk group to ISDN trunk
group might have a bearer capability that is not supported by the outgoing ISDN facilities
or network.
- A call tandeming through Communication Manager on a non-ISDN trunk group
inter-working to an ISDN trunk group might have an incorrect bearer capability assigned
on the incoming trunk group. The BC and ITC fields on the incoming trunk group might
be set wrong.
Cause Value 79
[0x4F/0xCF] Service or option not implemented, unspecified
The call could not be completed because the equipment sending this Cause Value has not
implemented a service, feature, or supplementary service requested by the user, and none of
the other Cause Values in the Service or option not implemented class apply.
As an implementation option, this Cause Value might be mapped to Cause Value 41 (Temporary
Failure) when it is received at a CO as part of SS7 call handling.
Communication Manager does not originate Cause Value 79.
174 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Event Data
Invalid Message Class Cause Values
Cause Value 81
[0x51/0xD1] Invalid call reference value
The equipment sending this Cause Value received a message with a call reference value that is
not currently in use on this user-network (D-channel) interface. This could indicate a call state
mismatch for the attempted connection between the two sides of the interface.
This Cause Value is most often generated when a message in a call clearing sequence of
messages is lost in transmission due to problems experienced on the D-channel. One side of
the interface thinks that the call has been torn down but the other side sends messages to
complete clearing the call. The response to this new call clearing sequence becomes a
RELEASE_COMPLETE message with Cause Value 81.
This Cause Value has local significance only. The ISDN network between the user and the
equipment generating the Cause Value might:
●
Send no cause indication through the network
●
Send a more generic Cause Value through the network
Cause Value 82
[0x52/0xD2] Identified channel does not exist
The equipment sending this Cause Value received a SETUP request to use a channel that is
not activated on this interface for a call. For example, when a user has subscribed to those
channels on a primary rate interface numbered 1 to 12, and the user equipment or network
attempts to use one of the channels number 13 to 23, this Cause Value is generated.
This Cause Value has local significance only. The ISDN network between the user and the
equipment generating the Cause Value might:
●
Send no cause indication through the network
●
Send a more generic Cause Value through the network
Troubleshooting
●
●
Check the diagnostic information (DIAG) for the channel number of the non-existent
channel. See Cause Values and their meanings/interpretations on page 142.
Check Communication Manager administration (network generated the Cause Value).
- Communication Manager might have B-channels assigned off a T1/E1 into a trunk group
that are not available for service from the remote end. Contact the ISDN service provider
to find out which B-channels can be used.
Issue 3 February 2007
175
Denial Events
●
Communication Manager administration that can affect sending this Cause Value:
- Communication Manager might have missed assigning some B-channels into a trunk
group that the remote believes can be used for service and is attempting to request a call
on one. Check which channel is being requested and if possible assign it into the
appropriate trunk group. If the channel being requested is the 24th (T1) or 16th (E1)
channel, it might be incorrectly programmed as isdn-pri on the DS1 screen instead of
isdn-ext.
Cause Value 83
[0x53/0xD3] A suspended call exists, but this call identity does not
This Cause Value indicates that a call resume has been attempted for a call with an identity that
differs from any that are presently in a suspended state.
Cause Value 84
[0x54/0xD4] Call identity in use
This Cause Value indicates that the call identity sent in the call resume request is already in use
by the network.
Cause Value 85
[0x55/0xD5] No call suspended
This Cause Value indicates that a call resume has been attempted for a call, but the network
does not presently have any calls in a suspended state within the domain of interfaces over
which calls can be suspended.
Cause Value 86
[0x56/0xD6] Call having the requested call identity has been cleared
The equipment sending this cause received a resume request for a call identity indicating a
suspended call that had been cleared while still in the suspended state, either by a network
timeout or by the remote user.
176 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Event Data
Cause Value 87
[0x57/0xD7] User not a member of the Closed User Group [CUG]
The packet mode call was rejected because the user is not a member of the remote end’s
Closed User Group (CUG), which is a feature associated with packet mode calls similar to X.25
connection made over the ISDN D-channel.
Communication Manager does not support packet mode sessions on D-channels, therefore this
is not applicable to Communication Manager.
Cause Value 88
[0x58/0xD8] Incompatible destination
The call could not be completed because the call request in the SETUP message has low layer
compatibility, high layer compatibility, or other compatibility attributes (for example, data rate,
DN, or sub-address information) which the remote endpoint or network cannot accommodate.
This Cause Value has end-to-end significance and should always be passed back through the
network to the user.
Troubleshooting
●
Check Communication Manager administration (network generated the Cause Value).
- Route pattern: An incorrect ITC and/or BCIE specified, these fields affect how the bearer
capability is encoded in the SETUP message.
- The ITC administered on the originating endpoint might be incorrect for this call, and/or
the speed options in the device itself might be incorrect for calls over these ISDN
facilities.
- Incorrect data speed option is set in the BRI device, causing a call from a BRI endpoint
tandeming through Communication Manager to create a SETUP message with the
wrong bearer capability.
- A call tandeming through Communication Manager ISDN trunk group to ISDN trunk
group might have a bearer capability that is not supported by the outgoing ISDN facilities
or network.
- A call tandeming through Communication Manager on a non-ISDN trunk group
inter-working to an ISDN trunk group might have an incorrect bearer capability assigned
on the incoming trunk group. The BC and ITC fields on the incoming trunk group might
be set wrong.
●
Communication Manager administration that can affect sending this Cause Value:
- The extension number assigned in Communication Manager that was received in the
incoming SETUP message for this data call is assigned to an analog extension.
- The extension number assigned in Communication Manager that was received in the
incoming SETUP message for this voice call is assigned to a data extension.
Issue 3 February 2007
177
Denial Events
- A data call attempt tandeming through Communication Manager ISDN trunk group to
ISDN trunk group the outgoing route pattern has the Bearer Capability Class (BCC)
required for making this call set to “NO” and/or the ITC and BCIE are not compatible with
the incoming bearer capability.
- A Temporary Signaling Connection (TSC) setup attempt that is tandeming through
Communication Manager, the outgoing route pattern does not have the TSC bearer
capability activated.
Cause Value 89
[0x59/0xD9] Network Congestion (1TR6: AT&T ISDN Protocol)
The call could not be completed because the switching equipment generating this Cause Value
is experiencing a period of high traffic.
This Cause Value has end-to-end significance and should always be passed back through the
network to the user.
Troubleshooting
Wait and try the call again later.
Cause Value 90
[0x5A/0xDA] Non-existent closed user group (CUG)/
Remote user initiated clearing (1TR6: AT&T ISDN Protocol)
The packet mode call was rejected because the equipment that sent the Cause Value did not
recognize the requested Closed User Group (CUG), which is a feature associated with packet
mode calls similar to X.25 connection made over the ISDN D-channel.
Communication Manager does not support packet mode sessions on D-channels, therefore this
is not applicable to Communication Manager.
Cause Value 91
[0x5B/0xDB] Invalid transit network selection
The call could not be completed because the equipment that sent this Cause Value received a
request to route a call to a transit network that it does not have a connection to, or the transit
network identification that was received is of an incorrect format as defined in Annex C of the
ITU Q.931 specification for either the TNS IE or the NSF IE.
Communication Manager does not originate Cause Value 91.
178 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Event Data
Troubleshooting
●
Check Communication Manager administration (network generated the Cause Value).
- Communication Manager sent the transit network identification in the NSF IE when the
network expected it to be in the TNS IE. The protocol version on the DS1 form does not
match the near-end ISDN network that is terminating the D-channel. Contact the ISDN
network service provider and try to line up the protocols being used. NI-2 only supports
the TNS IE, while custom protocol supports use of the NSF IE for this purpose.
Cause Value 95
[0x5F/0xDF] Invalid message, unspecified
This Cause Value indicates an invalid message event only when no other cause in the invalid
message class applies.
Communication Manager does not originate this Cause Value for PRI. A BRI or Adjunct Switch
Application Interface (ASAI) application might generate this Cause Value.
Troubleshooting
The diagnostic information (DIAG) of the Cause Value should contain, if implemented, the
message type identifier of the invalid message. See Cause Values and their meanings/
interpretations on page 142.
Protocol Error Class Cause Values
Cause Value 96
[0x60/0xE0] Mandatory information element is missing
The equipment that sent this Cause Value Call Reference Value (CRV) received a message that
did not contain a required Information Element for the message to be parsed and processed.
Depending on which message in the call establishment sequence is missing information, a
message returned with this Cause Value might or might not indicate a problem establishing a
call.
When the public network is screening for Calling Party Number (CPN), the fact that CPN is
missing causes the network to return this Cause Value, but depending on optioning in the CO
the call might still go through.
This Cause Value has local significance only. The ISDN network between the user and the
equipment generating the Cause Value might:
●
Send no cause indication through the network
●
Send a more generic Cause Value through the network
Issue 3 February 2007
179
Denial Events
Troubleshooting
●
●
Check that the protocols at each end of the interface match (for example, both sides are
AT&T Custom or both sides are NI-2). If the ends of the interface are running different
protocols, they might be running with different Information Element encoding.
Check the diagnostic information (DIAG) for the IE identifier of the missing information.
See Cause Values and their meanings/interpretations on page 142.
Communication Manager generates diagnostic information. See Table 47: Cause Value 96 &
100 Diagnostic Information.
Table 47: Cause Value 96 & 100 Diagnostic Information 1 of 2
Missing IE Identifier
Information Element
Code-set 0
0C/4C
CONNECTED NUMBER
0D
CONNECTED SUB-ADDRESS
01
CHANGE STATUS
1C
FACILITY
1E
PROGRESS INDICATOR
2C
KEYPAD
04
BEARER CAPABILITY
6C
CALLING PARTY NUMBER
6D
CALLING PARTY SUB-ADDRESS
7C
LOW LAYER COMPATIBILITY
7D
HIGH LAYER COMPATIBILITY
7E
USER-TO-USER INFORMATION
08
CAUSE
10
CALL IDENTITY
14
CALL STATE
18
CHANNEL IDENTIFICATION
1 of 2
180 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Event Data
Table 47: Cause Value 96 & 100 Diagnostic Information 2 of 2
Missing IE Identifier
Information Element
20
NETWORK SPECIFIC FACILITIES
27
NOTIFICATION INDICATOR
28
DISPLAY
34
SIGNAL
70
CALLED PARTY NUMBER
71
CALLED PARTY SUB-ADDRESS
74
REDIRECTING NUMBER
79
RESTART INDICATOR
78
TRANSIT NETWORK SELECTION
Code-set 6
7B
LOOK AHEAD INTERFLOW
08
TRAVELING CLASS MARK
28
DISPLAY
55
Distributed Communication System
(DCS)
56
Distributed Communication System
(DCS) AUDIX
57
AUDIX
96
LOCK SHIFT TO CODE-SET6
2 of 2
Cause Value 97
[0x61/0xE1] Message type non-existent or not implemented
The equipment that sent this Cause Value received a message containing a message type it
does not recognize, either because the message type is not defined or it is defined but not
implemented by the equipment.
Issue 3 February 2007
181
Denial Events
This Cause Value has local significance only. The ISDN network between the user and the
equipment generating the Cause Value might:
●
Send no cause indication through the network
●
Send a more generic Cause Value through the network
Troubleshooting
●
●
Check that the protocols at each end of the interface match (for example, both sides are
AT&T Custom or both sides are NI-2). If the ends of the interface are running different
protocols, they might be running with different Information Element encoding.
Check the diagnostic information generated by Communication Manager for the message
type identifier of the unrecognized message.
Table 48: Cause Value 97, 98, 101 Diagnostic Information 1 of 2
Message Type Identifier
Message
0D
SETUP ACKNOWLEDGE
0F
CONNECT ACKNOWLEDGE
01
ALERTING
02
CALL PROCEEDING
03
PROGRESS
05
SETUP
07
CONNECT
4D
RELEASE
4E
RESTART ACKNOWLEDGE
5A
RELEASE COMPLETE
6A
FACILITY ACKNOWLEDGE
6E
NOTIFY
7B
INFORMATION
7D
STATUS
20
USER INFORMATION
45
DISCONNECT
46
RESTART
62
FACILITY
1 of 2
182 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Event Data
Table 48: Cause Value 97, 98, 101 Diagnostic Information 2 of 2
Message Type Identifier
Message
72
FACILITY REJECT
75
STATUS ENQUIRY
79
CONGESTION CONTROL
Maintenance Message
0F
SERVICE
07
SERVICE ACKNOWLEDGE
2 of 2
Cause Value 98
[0x62/0xE2] Message type, not compatible with call state, or non-existent, or not implemented
The equipment that sent this Cause Value received a message, and the procedures in the
protocol specification indicate that this is not a permissible message to receive while in this call
state. A STATUS message was received indicating an incompatible call state.
This Cause Value has local significance only. The ISDN network between the user and the
equipment generating the Cause Value might:
●
Send no cause indication through the network
●
Send a more generic Cause Value through the network
Troubleshooting
●
●
●
Check that the protocols at each end of the interface match (for example, both sides are
AT&T Custom or both sides are NI-2). If the ends of the interface are running different
protocols, they might be running with different call state machines, or different message
type encoding.
Check the diagnostic information generated by Communication Manager for the message
type identifier of the message that violates protocol. See Table 48: Cause Value 97, 98,
101 Diagnostic Information on page 182.
Call state problems are reported with STATUS messages. The equipment sending the
Cause Value uses the CALL STATE IE of the STATUS message to indicate the call state.
To determine the call state of the other end of the interface, run the message sequence of
the call through the SDL flow charts of the appropriate side (user or network) and the
appropriate protocol (TR41449/41459, TR1268, A211 etc.). If the call state at the other end
of the interface does not agree with that reported in the STATUS message and both sides
are already running the same protocol, then a problem with the implementation of the state
machine exists on either side.
Issue 3 February 2007
183
Denial Events
Problems have been revealed with the state machine implementations of some of the CO
switches for different protocols, and the state machine problems in the CO switches are
most likely not going to be corrected. Communication Manager has not shown any
problems with its state machine implementations for the different protocols.
Change Communication Manager administration to change the message sequence of the
call scenario causing the error, and help solve state machine implementation problems. For
example:
- change the inter-working message on the DS1 form from PROGRESS to ALERTING
- change the “wait” steps in vectors to be “i-silent” so that they do not generate extra
PROGRESS messages in the calling message sequence.
Cause Value 99
[0x63/0xE3] Information element non-existent or not implemented
The equipment that sent this Cause Value received a message that includes Information
Elements that are not recognized because the Information Element identifier is not defined, or it
is defined but has not been implemented by the equipment sending the Cause Value. However,
the Information Element is not mandatory in the message, and the equipment that sent the
Cause Value does not need to parse the Information Element in order to process the message.
This Cause Value has local significance only. The ISDN network between the user and the
equipment generating the Cause Value might:
●
Send no cause indication through the network
●
Send a more generic Cause Value through the network
Troubleshooting
●
●
Check that the protocols at each end of the interface match (for example, both sides are
AT&T Custom or both sides are NI-2). If the ends of the interface are running different
protocols, they might be running with different Information Element encoding.
Check Communication Manager administration (network generated the Cause Value).
- Sending connected number information with the domestic custom Information Element
identity encoding (0C), but international encoding (4C)is expected.
Cause Value 100
[0x64/0xE4] Invalid information element contents
The equipment that sent this Cause Value received a message that includes an Information
Element that it does recognize and implements, however one or more of the fields contained in
the Information Element are coded in such a way that it has not been implemented by the
equipment that sent this Cause Value.
184 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Event Data
This Cause Value has local significance only. The ISDN network between the user and the
equipment generating the Cause Value might:
●
Send no cause indication through the network
●
Send a more generic Cause Value through the network
Troubleshooting
●
●
Check that the protocols at each end of the interface match (for example, both sides are
AT&T Custom or both sides are NI-2). If the ends of the interface are running different
protocols, they might be running with different Information Element encoding.
Check Communication Manager diagnostics for the IE identifier of the Information Element
that contains the information that violates protocol.
The PROGRESS INDICATOR IE information that Communication Manager generates
should not affect call completion. There is no way to modify how Communication Manager
generates this information.
See Table 47: Cause Value 96 & 100 Diagnostic Information on page 180.
Cause Value 101
[0x65/0xE5] Message not compatible with call state/
Protocol threshold exceeded (NI-2: National ISDN 2)
Cause Value 101 indicates that the equipment that sent this Cause Value received a message
that it does recognize, and procedures in the protocol specification indicate that it is not
permissible to receive the message while in this call state.
This Cause Value has local significance only. The ISDN network between the user and the
equipment generating the Cause Value might:
●
Send no cause indication through the network
●
Send a more generic Cause Value through the network
Cause Value 101 (NI-2) can also mean that an established call or an establishing call is being
cleared because the threshold for multiple signaling protocol errors occurring during an active
call has been exceeded.
Troubleshooting
●
●
Check that the protocols at each end of the interface match (for example, both sides are
AT&T Custom or both sides are NI-2). If the ends of the interface are running different
protocols, they might be running different call state machines.
Check the Communication Manager diagnostic information for the message type identifier
that is in violation of the protocol. Table 48: Cause Value 97, 98, 101 Diagnostic
Information on page 182
Issue 3 February 2007
185
Denial Events
●
Call state problems are reported with STATUS messages. The equipment sending the
Cause Value uses the CALL STATE IE of the STATUS message to indicate the call state.
To determine the call state of the other end of the interface, run the message sequence of
the call through the SDL flow charts of the appropriate side (user or network) and the
appropriate protocol (TR41449/41459, TR1268, A211 etc.). If the call state at the other end
of the interface does not agree with that reported in the STATUS message and both sides
are already running the same protocol, then a problem with the implementation of the state
machine exists on either side.
Problems have been revealed with the state machine implementations of some of the CO
switches for different protocols, and the state machine problems in the CO switches are
most likely not going to be corrected. Communication Manager has not shown any
problems with its state machine implementations for the different protocols.
Change Communication Manager administration to change the message sequence of the
call scenario causing the error, and help solve state machine implementation problems. For
example:
- change the inter-working message on the DS1 form from PROGRESS to ALERTING
- change the “wait” steps in vectors to be “i-silent” so that they do not generate extra
PROGRESS messages in the calling message sequence.
Cause Value 102
[0x66/0xE6] Recovery on timer Expiry
The equipment sending this Cause Value sent or received a Layer 3 Q.931 message. Sending
or receiving this message has initiated a Layer 3 timer that has expired. This Cause Value is
being generated in conjunction with Q.931 protocol error handling procedures.
This Cause Value has local significance only. The ISDN network between the user and the
equipment generating the Cause Value might:
●
Send no cause indication through the network
●
Send a more generic Cause Value through the network
Communication Manager logs timer expiry errors that it generates to the error log against the
signaling group of the D-channel where the error occurred. The signaling group (ISDN-SER)
error is Error Type 1 and the Aux Data contains the identifier of the Layer 3 timer that expired.
Communication Manager does not generate the diagnostic information for the Cause Value IE.
186 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Event Data
Table 49: Cause Value 102, Signaling Group Error Type 1, Aux Data information
Aux
Data
Value
Timer
Name
Timer
Value
Description
1
T302
4s
SETUP_ACK messages (overlap receiving mode)
2
T303_1
4s
SETUP message 1st timer expiration
3
T303_2
4s
SETUP message 2nd timer expiration
4
T305
4/30s
DISCONNECT message
5
T308_1
4s
RELEASE message 1st expiration
6
T308_2
4s
RELEASE message 2nd expiration
7
T310
10s
CALL_PROCEEDING message
8
T313
4s
CONNECT message
9
T313_2
4s
“no longer used”
10
T316
120s
RESTART message
11
TL3
30s
Layer 3 timer expired (d-channel dropped)
12
T309
90s
d-channel reestablishment expiration stable calls are
dropped
13
T_WRN
h
FACILITY message (waiting for ACK or REJ)
14
T321
120s
SERVICE message (waiting for ACK)
15
TSM
h
retransmission of SERVICE on d-channel switchover
16
TM100
h
ISDN-BRI maintenance (MIM timer)
Troubleshooting
●
●
Check the diagnostic information for the timer number that has expired. See Cause Values
and their meanings/interpretations on page 142.
Check that the protocols at each end of the interface match (for example, both sides are
AT&T Custom or both sides are NI-2).
- If the ends of the interface are running different protocols, they might be running with
different values for their Layer 3 timers.
- If the protocols at each end of the interface match, the Communication Manager timer
might have expired because:
Issue 3 February 2007
187
Denial Events
●
●
●
●
the far end never saw the message because the message was corrupted in
transmission by noise on the D-channel. Check for any type of T1/E1 facility errors.
the far end is experiencing a high traffic condition and did not have the processing
time to parse the sent message before the timer expired.
even though the message was seen to be generated in an internal Communication
Manager trace, the message was never transmitted out onto the D-channel. Perform
an external protocol capture on the D-channel to confirm the transmission of the
suspect message.
To interpret the receipt of Cause Value 102 from the far end, look at a trace/protocol
capture of the messaging taking place, and find the last message received from the far end
before Cause Value 102 is received. The timer that expired is most likely the Layer 3 timer
associated with that last message. If Communication Manager generated a message in
between those 2 events that should have stopped the timer, the cause might be:
- the far end never saw the message because the message was corrupted in transmission
by noise on the D-channel. Check for any type of T1/E1 facility errors.
- the far end might be experiencing a high traffic condition and did not have the processing
time to parse the sent message before the timer expired.
- even though the message was seen to be generated in an internal Communication
Manager trace, the message was never actually transmitted out onto the D-channel.
Perform an external protocol capture on the D-channel to confirm the transmission of the
suspect message.
●
If Communication Manager did not respond to the receipt of the last message from the far
end, then Communication Manager internal hardware and software becomes suspect, and
trouble shooting the problem must proceed from that point.
Communication Manager administration that can contribute to seeing timer expiry errors:
●
●
●
Trunk group form: Incoming call handling table. If the Per call CPN/BN field is incorrectly
populated in comparison to how the CO is programmed to send CPN or BN, it causes
Communication Manager to send a FACILITY message to the CO requesting CPN/BN
information and the CO will never respond. Communication Manager will log many timer
expiry errors against the signaling group (Error Type 1, Aux Data 13).
DS1 form: Protocol version: If Communication Manager is running custom protocol
(protocol version “A”) and is connected to a Nortel DMS central office running custom
protocol, Communication Manager will log timer expiry errors against signaling group for
DISCONNECT problems (Error Type 1, Aux Data 4) during high traffic conditions.
The DMS CO custom protocol implementation uses the ANSI recommended timer values
for their Layer 3 timers while Communication Manager uses the ITU recommended timer
values. Thus the T305 timer in the Communication Manager is 4 seconds while the same
timer in the DMS is 30 seconds, this difference causes timer expiry problems in high traffic
conditions. Change Communication Manager’s protocol version to c to line up the timers.
188 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Event Data
Cause Value 103
[0x67/0xE7] Parameter not implemented
The equipment sending this Cause Value received a message that includes an Information
Element that it does recognize and implements, however one or more of the fields contained in
the Information Element are coded in such a way that it has not been implemented by the
equipment sending this Cause Value.
The diagnostic information of the Cause Value should contain, if implemented, the identifier of
the Information Element that contains the information that violates protocol. See Cause Values
and their meanings/interpretations on page 142.
This Cause Value has local significance only. The ISDN network between the user and the
equipment generating the Cause Value might:
●
Send no cause indication through the network
●
Send a more generic Cause Value through the network
Cause Value 110
[0x6E/0xEE] Message with unrecognized parameter
The equipment sending this Cause Value received a message that includes Information
Elements that are not recognized because the Information Element identifier is not defined, or it
is defined but has not been implemented by the equipment sending the Cause Value. However,
the Information Element is not mandatory in the message, and the equipment sending the
Cause Value does not need to parse the Information Element in order to process the message.
This Cause Value has local significance only. The ISDN network between the user and the
equipment generating the Cause Value might:
●
Send no cause indication through the network
●
Send a more generic Cause Value through the network
Cause Value 111
[0x6F/0xEF] Protocol error unspecified
Cause Value 111 indicates that he equipment sending this Cause Value experienced a protocol
error event for which no other Cause Value in the Protocol Error class applies.
This Cause Value has local significance only. The ISDN network between the user and the
equipment generating the Cause Value might:
●
Send no cause indication through the network
●
Send a more generic Cause Value through the network
Issue 3 February 2007
189
Denial Events
Cause Value 111 (NI-2) is used in packet mode to be able to map the X.25 Cause Value 17
“remote procedure error”.
Communication Manager does not originate this Cause Value for PRI. A BRI or Adjunct Switch
Application Interface (ASAI) application might generate this Cause Value.
Cause Value 112
[0x70/0xF0] Local procedure error (1TR6: AT&T ISDN Protocol)
This is a packet mode Cause Value.
Cause Value 113
[0x71/0xF1] Remote procedure error (1TR6: AT&T ISDN Protocol)
This is a packet mode Cause Value.
Cause Value 114
[0x72/0xF2] Remote user suspended (1TR6: AT&T ISDN Protocol)
This Cause Value indicates to the remote user that the call has been put on hold.
Cause Value 115
[0x73/0xF3] Remote user resumed (1TR6: AT&T ISDN Protocol)
This Cause Value indicates to the remote user that the call has been taken off hold.
Inter-working Class Cause Values
Cause Value 127
[0x7F/0xFF] Inter-working, unspecified/
User info discarded locally (1TR6: AT&T ISDN Protocol)
This Cause Value indicates that in the equipment sending this Cause Value is the point in the
network where the call has inter-worked with a network that does not provide Cause Value
information for actions it takes. Thus when an event takes place this Cause Value is sent
because the precise cause for the event cannot be ascertained.
This Cause Value has end-to-end significance and should always be passed back through the
network to the user.
190 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Denial Event Tables
Communication Manager generates this Cause Value for events on tandem calls that have
inter-worked from ISDN trunk groups to non-ISDN trunk groups.
Troubleshooting
●
Check the Cause Value Information Element (LOC). See Location Codes on page 144.
Denial Event Tables
Call Processing Denial Events
Event Types 1000 - 2299 show denial events generated during call processing, as listed in
Table 50: Call Process denial events (1001 - 1172) on page 191, Table 52: Call Process denial
events (1225 - 1899) on page 207, and Table 55: Call Process denial events (2021 - 2299) on
page 254.
Use Event Types 1000 - 1899 to help isolate the cause of receiving reorder or intercept
treatment:
●
●
Event Types 1000 -1299 might explain events where reorder treatments are initiated, or to
events that eventually lead to reorder treatments.
Event Types 1300 - 1899 might explain events where intercept treatments are initiated, or
to events that eventually lead to intercept treatments.
Table 50: Call Process denial events (1001 - 1172) 1 of 13
Event
Type
Event Description, as it
appears on the event log
Explanation
Event
Data 1
1001
Resource not available
grp_m process returned GM_FAIL in response to
GM_MTM_DIG_DONE message.
1002
Call parked on user
A call might already be parked on user.
1003
Can't connect Tone Det
Cannot connect or reconnect tone detector during
outgoing wait supervision. Automatic Number
Identification (ANI) request is expected.
1004
Can't reserve Tone Det
Cannot reserve tone detector.
1005
Trunk sequence error
Outgoing MFE call received answer before
addressing was complete.
1006
TTR unavailable
GCOL_ERR usually means no Touch Tone
Receiver (TTR) available.
Event Data 2
1 of 13
Issue 3 February 2007
191
Denial Events
Table 50: Call Process denial events (1001 - 1172) 2 of 13
Event
Type
Event Description, as it
appears on the event log
Explanation
1007
CAS Remote Hold
The Centralized Attendant Service (CAS) Remote
Hold feature was accessed. No CAS attendant
exists.
1008
CAS Remote Hold
Centralized Attendant Service (CAS) Remote
Hold was accessed by a non-CAS attendant.
1009
CAS Remote Hold
Centralized Attendant Service (CAS) Remote
Hold was accessed by non-CAS attendant.
Analog Answer-Hold/Unhold invalid.
1010
TEG denied origination
Terminating Extension Group was denied an
origination.
1011
Destination Unavailable
Facilities were exhausted during rerouting. Bearer
capability is VOICE, VOICE BAND DATA.
Received unexpected TCM not yet used in
routing. Reroute attempt using received TCM
finds principal is NULL or attendant extended call
to ARS. Queueing is not allowed.
1012
Destination Unavailable
Facilities were exhausted during rerouting. Bearer
capability is VOICE, VOICE BAND DATA. No
outgoing trunk queuing, or no trunks, or DEXT, or
Adjunct origination, or Administered Connection,
or QSIG Call Completion Ringout attempt.
Queueing is not allowed.
1013
Destination Unavailable
Facilities were exhausted during rerouting. Bearer
capability is VOICE, VOICE BAND DATA. No
outgoing trunk queuing, or no trunks, or DEXT, or
Adjunct origination, or Administered Connection,
or QSIG Call Completion Ringout attempt.
Queueing is not allowed.
1014
Destination Unavailable
Inter-PBX attendant service termination attempt
failed. The trunk was busy.
1015
Destination Unavailable
Attendant seizing trunk for thru-dialing failed. The
trunk was busy or not available.
1016
Remote Cvg loop denial
Outgoing remote coverage call, with digit
conversion to the principal's extension. Prevent
looping.
1017
AUDIX Unavailable
Termination to AUDIX coverage point failed,
unable to terminate at an AUDIX hunt group.
1018
Multimedia call denial
Multimedia call. Convert termination to a meetme
User ID instead of station User ID failed. Invalid
bearer cap received.
1019
Multimedia call denial
Multimedia call. Convert termination to a meetme
User ID instead of station User ID failed. user_m
failed to get & return meetme User ID.
1020
Multimedia call denial
Multimedia call. Convert termination to a meetme
User ID instead of station User ID failed. user_m
returned a meetme uid = 0.
1021
Call Term overflow
Call termination overflow to DDD of an Electronic
Tandem Network Listed Directory Number. Call
should be blocked.
Event
Data 1
Event Data 2
2 of 13
192 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Denial Event Tables
Table 50: Call Process denial events (1001 - 1172) 3 of 13
Event
Type
Event Description, as it
appears on the event log
Explanation
Event
Data 1
1022
CDR resource exhaustion
Call Detail Recording (CDR) resource exhaustion.
Caller from tie trunk can receive reorder tone.
1023
CDR resource exhaustion
Call Detail Recording (CDR) resource exhaustion.
Give Trunk/Personal Central Office Line (TK/
PCOL) caller termination to announcement. User
ID not found for announcement.
1024
CDR resource exhaustion
Call Detail Recording (CDR) resource exhaustion.
Caller from non-Trunk/Personal Central Office
Line (TK/PCOL) (from line) can receive reorder
tone.
1025
Incompatable Bandwidth
Terminated to an endpoint or trunk group that
cannot support the requested bandwidth.
1026
AUDIX Unavailable
Call from non-trunk. Unable to terminate at an
AUDIX hunt group.
1027
Attd control trk denial
Switch Classified Calls might not go to a trunk
controlled by an attendant.
1028
Trunk Unavailable
No trunks are available and there is no chance of
being queued.
1029
Modem Unavailable
Modem unavailable from pool.
1030
Modem Unavailable
Modem unavailable from pool.
1031
LWC failure
Leave Word Calling. Async message response
from msg_sv: give user LW_REORDER.
1032
Multimedia call failure
Multimedia call. Creating a multimedia user. User
ID (UID) - failure. user_m returned a mtm_uid of
0.
1033
Multimedia call failure
Multimedia call. Cannot create a multimedia user.
1034
Multimedia call failure
Multimedia call. GM_MTM_DIGIT digit sending
message failed on second address of
multi-number call.
1035
Multimedia call failure
Multimedia call. Trying to send more than the
maximum of two addresses in a multi-number call.
1036
Station sec code len qry
The query for the administered minimum
station-security-code length failed.
1037
Routing UID=0
The Routing User ID (UID) = 0 for a remote
Distributed Communication System (DCS) user
that has activated automatic callback toward a
station local to this switch.
1038
ACD login failed
Traditional Automatic Call Distribution (ACD)
agent login failed. The maximum number of logins
already exist.
1039
ACD login failed
GM/UM set up of the Automatic Call Distribution
(ACD) Logical Agent login info failed, before
password matching, if any.
Event Data 2
3 of 13
Issue 3 February 2007
193
Denial Events
Table 50: Call Process denial events (1001 - 1172) 4 of 13
Event
Type
Event Description, as it
appears on the event log
Explanation
1040
ACD login failed
GM/UM set up of the Automatic Call Distribution
(ACD) Logical Agent login info failed after
password matching succeeded.
1041
DS0 looparound failed
Incoming ds0 test call failed to set up
non-inverting digital looparound capability.
1042
TTR unavailable
Facility Access Test. Touch Tone Receiver (TTR)
is missing, did not get attached, might be in use
by some other call.
1042
460.1 Neg failed in ARQ
Registration Request rejected because no Digital
Signal Processor (DSP) resources are available.
1043
Specified TTR unavailable
Facility Access Test. The specified Touch Tone
Receiver (TTR) needed to collect digits was in
use.
1044
reserve for FAT fat_compl
Facility Access Test. Reserved for silent reorder
on the chance that recoding is required.
1045
FAT tone test failed
Facility Access Test. The test to hear tone failed.
The Expansion Network Link might be down.
1046
Specified TSLOT busy
Facility Access Test. Specified timeslot was busy.
1047
Music port connect fail
Facility Access Test. Completing call to music port
failed. EPN Link might be down, or music port is
not administered.
1048
FAT trunk busy
Facility Access Test - completing call to trunk.
Trunk is busy.
1049
ISDN trunk busy
Facility Access Test - completing call to ISDN
trunk. Trunk is busy.
1050
Illegal Message Retrieval
Remote access users are not allowed access to
messages via voice coverage message retrieval.
1051
Speech Port unavailable
No voice synthesis speech port is available for
coverage message retrieval.
1052
Called announcement busy
Call to announcement, but announcement is busy.
1053
Chime tone connection
Connection of a chime tone to a service failed.
There might be an invalid service ID or software
error.
1054
TTR unavailable
Collection of password digits needs a Touch Tone
Receiver (TTR). No in-service TTRs are available.
1055
No call to cancel
Deactivate automatic callback (ACB) was denied
or outgoing trunk queueing (OTQ) was denied.
The Caller ID of the ACB/OTQ call to be cancelled
could not be found. There might be nothing to
deactivate.
1056
Adjct Rte calls can't Que
Adjunct Switch Application Interface (ASAI)
adjunct originated switch classified calls and
adjunct-routed calls are not allowed to queue.
Communication
Manager
Event
Data 1
Event Data 2
UID
IP address
Release 3.1
4 of 13
194 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Denial Event Tables
Table 50: Call Process denial events (1001 - 1172) 5 of 13
Event
Type
Event Description, as it
appears on the event log
Explanation
Event
Data 1
1057
COS - Auto Callback
User's Class of Service does not permit activation
of automatic callback.
1058
Auto Callback User ID
User activating automatic callback has software
partyblock member misrepresented.
1059
Auto Callback double qued
User is activating automatic callback, but the call
has already been queued or has no principal
terminating User ID.
1060
Auto Callback terminator
Activating automatic callback is not allowed when
the terminating extension is a group attendant,
terminating extension group, Vector Directory
Number, or if vector processing is active.
1061
Auto Callback terminator
Activating automatic callback.
● For a non-Distributed Communication
System (DCS) terminator, if there is an
accompanying Call Detail Recording
(CDR) ineffective call attempt record, the
queue is full or zero-length.
● For a DCS terminator, termination did not
happen for one of several reasons
identified in rc from gm_term
re_termination attempt in onhk_que.c
1062
Auto Callback activation
Activating automatic callback. Checks on queue
availability and/or Distributed Communication
System (DCS) termination pass OK, but activation
is denied.
1063
Auto Callback ineligible
Activating Automatic Callback (ACB). Response
to callback type query is queue ineligible, might be
ACB is in use or call is on hold, or GQRY_ERR
(might be no call ID behind call back button).
1064
Double queueing denied
Manual activation of queueing. Call has already
been queued (automatic).
1065
Manual queing terminator
Manual activation of queueing. There is no
principal terminator on which to queue.
1066
Manual queing - full que
Manual activation of queueing. The queue is full
or queue length is zero.
1067
Manaual queing denied
Manual activation of queueing. Checks on queue
availability pass OK, but activation is denied.
1068
queued call went away
Reactivation of automatic callback or outgoing
trunk queueing. The call disappeared from the
queue.
1069
PMS link/printer down
Property Management System (PMS) cannot log
housekeeping status. PMS link is not operational
and the printer is down.
1070
(also in
Table 51)
TTR unavailable
ISDN trunk initiation of in-band end-to-end digit
collection failed. Might be waiting for a Touch Tone
Receiver (TTR).
Event Data 2
5 of 13
Issue 3 February 2007
195
Denial Events
Table 50: Call Process denial events (1001 - 1172) 6 of 13
Event
Type
Event Description, as it
appears on the event log
Explanation
1071
Wireless - trunk failure
General Central Office (GCO) Wireless
Subscriber System (WSS) call origination denied iap_cid_qry failure. Route to GCO subscriber
trunk failed.
1072
TTR TDM VC failed
Time Division Multiplexed (TDM) Voice Condition
(VC) creation for Touch Tone Receiver (TTR)
failed while in Audio add-on password
supervision.
1073
TTR TDM VC failed
Time Division Multiplexed (TDM) Voice Condition
(VC) creation for Touch Tone Receiver (TTR)
failed while in authorization code supervision,
waiting for digit analysis of the authorization code.
1074
TTR TDM VC failed
Time Division Multiplexed (TDM) Voice Condition
(VC) creation for Touch Tone Receiver (TTR)
failed while in Code Call paging seizure
supervision.
1075
TTR TDM VC failed
Time Division Multiplexed (TDM) Voice Condition
(VC) creation for Touch Tone Receiver (TTR)
failed while in feature supervision waiting to see
which feature is being invoked.
1076
TTR TDM VC failed
Time Division Multiplexed (TDM) Voice Condition
(VC) creation for Touch Tone Receiver (TTR)
failed while in idle supervision.
1077
TTR TDM VC failed
Time Division Multiplexed (TDM) Voice Condition
(VC) creation for Touch Tone Receiver (TTR)
failed while in normal answer supervision.
1078
TTR TDM VC failed
Time Division Multiplexed (TDM) Voice Condition
(VC) creation for Touch Tone Receiver (TTR)
failed while in outgoing trunk outpulsing
supervision.
1079
TTR TDM VC failed
Time Division Multiplexed (TDM) Voice Condition
(VC) creation for Touch Tone Receiver (TTR)
failed while in outgoing trunk seizure supervision.
1080
TTR TDM VC failed
Time Division Multiplexed (TDM) Voice Condition
(VC) creation for Touch Tone Receiver (TTR)
failed while in the supervisor for telecommuting
access waiting for certain Feature Access Codes
after the telecommuting extension has been
accessed.
1081
Change SSC denied
Change Station Security Code (SSC) REORDER. Possible causes:
● Too many admin users or save-trans in
progress
● Data already locked
● Translations being saved
● SAT user changing station data
● Station recently removed from translation
● System error
● Problem applying confirmation tone
● Terminal Translation Initiation (TTI)
feature not enabled
● TTI state not Voice (Data TTI enabled)
Event
Data 1
Event Data 2
6 of 13
196 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Denial Event Tables
Table 50: Call Process denial events (1001 - 1172) 7 of 13
Event
Type
Event Description, as it
appears on the event log
Explanation
Event
Data 1
1082
Rmv skill - agent busy
Doing “Remove Skill” on agent currently busy for
that skill (has DAC or is in ACW or on call).
1083
Add/Rmv skill denied
Add/Remove Agent Skills. Possible causes:
Event Data 2
● could not get station ID
● too many admin users or
save-translations in progress
● data already locked, maybe translations
are being saved or SAT user is changing
agent data
1084
DCS link down
Remote user activation of call forward Distributed Communication System (DCS) link not
up.
1085
PMS response timeout
Property Management System failed to respond
to maid status in the 4 seconds allowed.
1086
MFC no answer timeout
MultiFrequency Compelled (MFC) call circuit
congestion. No answer timeout from MFC call.
1087
MFC no answer timeout
MultiFrequency Compelled call circuit congestion.
No answer timeout. Might be bad trunk or no
Touch Tone Receiver (TTR) available at remote
end, for example.
1088
No answer timeout
MultiFrequency Compelled call circuit congestion.
No answer timeout. Might be bad trunk or no
Touch Tone Receiver (TTR) available at remote
end, for example.
1089
MFC no answer timeout
MultiFrequency Compelled call circuit congestion.
No answer timeout. Might be bad trunk or no
Touch Tone Receiver (TTR) available at remote
end, for example.
1090
T302 intercept timeout
T302 interdigit timer timeout.
1091
Max Paste users Pasting
The maximum allowable stations are currently
using PC Application Software Exchange
(PASTE). Wait and try again.
1092
Announcement unavailable
Might be announcement is busy, or
announcement is not present on board.
1093
Announcement memory exh
Announcement is dropped, announcement
memory is exhausted.
1094
Permanent Seizure
Direct Inward Dialing trunk origination. Digit
timeout with no digits dialed. Permanent incoming
seizure treatment is to give reorder.
1095
QSIG Call Offer timeout
QSIG Call Offer encountered timeout of 1 minute
path retention timer.
1096
Wakeup time unavailable
Collecting digits for “room wakeup by tones”
feature. Cannot do a wakeup for the specified
time.
7 of 13
Issue 3 February 2007
197
Denial Events
Table 50: Call Process denial events (1001 - 1172) 8 of 13
Event
Type
Event Description, as it
appears on the event log
Explanation
1097
MFC No Answer timeout
MFC call circuit congestion. No answer timeout.
Might be bad trunk or no Touch Tone Receiver
(TTR) available at remote end, for example.
1098
TTI merge/unmerge failed
Station server could not perform Terminal
Translation Initiation (TTI) merge/unmerge.
Certain resources are unavailable. The user can
try again and the resources might be available.
1099
LWC access code rejected
Voice synthesis Leave Word Calling access code
rejected by msg_sv.
1100
TTI - station active
In preparation for lock resources step for Terminal
Translation Initiation (TTI) merge/unmerge,
Personal Station Access (PSA) association/
disassociation finds that the station is active on a
call not to be interrupted.
1101
Modem unavailable
There is a problem with allocating or finding a
modem for an incoming data call.
1102
MM - voice call failure
Processing a Multimedia compatible vector, there
is failure doing conversion to voice call.
1103
Tone Detector conn fail
Cannot connect tone detector for trunk terminated
call. Silent Reorder.
1104
Tone Detector conn fail
Cannot connect tone detector for voice station or
DEXT. Silent Reorder.
1105
Ringback limit met
The limit is met of 4 ringbacks in a row before far
end answers. Silent Reorder.
1106
Ringback limit met
The limit is met of 36 ringbacks in a row before far
end answers. Silent Reorder.
1107
Reorder tone received
Reorder tone received before far end answers.
Silent Reorder.
1108
LWC access code rejected
The message server rejected the Leave Word
Calling Access code that was dialed.
1109
DCS link/msg buffer
Remote busy verification encountered a
Distributed Communication System (DCS) link
down or an exhausted DCS message buffer.
1110
DCS link down
Distributed Communication System (DCS) remote
trunk group selection. Remote Direct Trunk Group
Selection (DTGS) button push by attendant, but
DCS link is down.
1111
CFWD activate/cancel
Send a callforward activation message to the
remote switch. Message buffers exhausted, call
not UDP & not Distributed Communication
System (DCS), DCS link is down.
1112
TTR unavailable
Russian Automatic Number Identification (ANI)
3rd party feature button. Touch Tone Receiver
(TTR) not available.
1113
ANI error limit
3rd party feature activation. Automatic Number
Identification (ANI) error on 2 tries.
Event
Data 1
Event Data 2
8 of 13
198 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Denial Event Tables
Table 50: Call Process denial events (1001 - 1172) 9 of 13
Event
Type
Event Description, as it
appears on the event log
Explanation
Event
Data 1
1114
DCS trunk required
Remote busy verification. A Distributed
Communication System (DCS) trunk is required.
1115
LWC timeout
Leave Word Calling timeout occurred in the dap
for a non-call associated attempt.
1116
DCS confirm msg timeout
Remote busy verification. A Distributed
Communication System (DCS) confirmation
message was not back in 4 seconds.
1117
Outgoing trk seizure fail
Outgoing trunk seizure failure, busy verify hit
glare, digit timeout via ogt_sz_sup().
1118
Analog station ringer
Analog principal station has trouble ringing.
1119
Analog station ringer
Analog covering station has trouble ringing and
principal was station not rung successfully.
1120
Bsy Vfy termination fail
RP_M found busy verification terminator
available, but termination to it failed.
1121
Bsy Vfy termination fail
RP_M found busy verification trunk terminator
available, but USER_M found it maintenance
busy or otherwise unavailable.
1122
Bsy Vfy termination fail
GRP_M found busy verification terminator
available, but USER_M found it out-of-service.
1123
Bsy Vfy termination fail
GRP_M found busy verify terminator available,
but USER_M denied termination to:
● TRUNK
- admin busy
- incoming seizure
● STATION
- query for virtual set’s station hunting
User ID fails
- virtual set’s physical station’s current
state is not idle or call busy
- admin busy
- maintenance busy
- no available call appearance
- currently dialing
- available call appearance not idle or
busy HUNTGRP - no available
member in free list, at least one not
made busy
1124
Bsy Vfy termination fail
GRP_M found busy verify hunt group member
available, but USER_M found hunt group all busy
1125
Bsy Vfy call went away
Bridging a busy verification party to a call that no
longer exists.
Event Data 2
9 of 13
Issue 3 February 2007
199
Denial Events
Table 50: Call Process denial events (1001 - 1172) 10 of 13
Event
Type
Event Description, as it
appears on the event log
Explanation
1126
Bsy Vfy merge failed
Bridging a busy verification party to a call cannot
be merged. Merge checks include:
● not being busy verified by another user
● not a data call
● the call is in either talk or park state
- One exception to this is Converse calls
which are always in nrm_ans_sup()
● no tone connected or bv or conference
tone connected
● not exceed conference limit
● no aux trunk involved in the call
1127
Bsy Vfy warn tone conn
Busy verification warning tone connection (callr)
failed.
1128
Bsy Vfy warn tone conn
Busy verify warning tone connection to verified
call (callr2) failed.
1129
Bsy Vfy call went away
Bridging a busy-verification call with a
busy-verification call that no longer exists.
1130
Bsy Vfy merge failed
Bridging a busy verification party to a call cannot
be merged. Merge checks include:
● not being busy verified by another user
● not a data call
● the call is in either talk or park state
- One exception to this is Converse calls
which are always in nrm_ans_sup()
● no tone connected or bv or conference
tone connected
● not exceed conference limit
● no aux trunk involved in the call
1131
Bsy Vfy merge failed
Bridging a busy verification party to a call, the
merge operation failed.
1132
Auto Callback failure
Event
Data 1
Event Data 2
● Query for calling party’s callback type
failed
● Adding an automatic callback call to the
que of a trunk group failed or the queue
is full
● Calling party activation of automatic
callback failed
● No automatic callback button/feature
administered
● Automatic callback button already busy.
1133
Whisp Pg termination fail
Whisper paging termination to station, idle call
appearance failed.
1134
Whisp Pg to OS station
Whisper paging to Out of Service (OOS) station.
10 of 13
200 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Denial Event Tables
Table 50: Call Process denial events (1001 - 1172) 11 of 13
Event
Type
Event Description, as it
appears on the event log
Explanation
Event
Data 1
1135
Whisp Pg term denied
Whisper page to station denied.
STATION - admin busy
● user has blocked whisper pages or has
service observe pending
● (BRI) maintenance busy and the call is
already queued
● whisper page not allowed towards
analog line
● whisper page termination requires at
least 2 idle call appearances
● the current call is in the CA_DIAL state
1136
Whisp Pg hunt grp busy
Whisper paging - hunt group all made busy.
shouldn’t see this - hnt_qry does not respond to
qtype QWHISP_PG.
1137
Whisp Pg user blocked
User has whisper page blocked.
1138
Whisp Pg Svc Obsvd call
Whisper page - bridging to service-observed call.
1139
Whisp Pg Attd call
Whisper page - bridging to call with an attendant
on it.
1140
Whisp Pg Man Exclsn call
Whisper page - bridging to call with manual
exclusion activated.
1141
Whisp Pg merge denied
Bridging a busy whisper paging party to a call
cannot be merged.
Merge checks include:
● not being busy verified by another user
● not a data call
● the call is in either talk or park state
- One exception to this is Converse calls
which are always in nrm_ans_sup()
● no tone connected or bv or conference
tone connected
● not exceed conference limit
● no aux trunk involved in the call
1142
Whisp Pg warn tone conn
Whisper page warning tone connection to callr
failed.
1143
Whisp Pg warn tone conn
Whisper page warning tone connection to callr2
failed.
1144
Whisp Pg merge failed
Merge page call with paged call - query for
originator’s portid failed.
1145
Whisp Pg merge failed
Merge page call with paged call - query for paged
party’s portid failed.
1146
Whisp Pg call went away
Merge page call with paged call - paged party’s
call no longer exists
1147
Whisp Pg blocked
Merge page call with paged call - paged party has
whisper page blocked.
1148
Whisp Pg Svc Obsvd call
Merge page call with paged call - paged party is
being service observed.
Event Data 2
11 of 13
Issue 3 February 2007
201
Denial Events
Table 50: Call Process denial events (1001 - 1172) 12 of 13
Event
Type
Event Description, as it
appears on the event log
Explanation
1149
Whisp Pg merge Attd call
Merge page call with paged call - paged party is
on a call with an attendant.
1150
Whisp Pg merge Man Exclsn
Merge page call with paged call - paged party has
manual exclusion activated.
1151
Whisp Pg merge denied
Bridging a busy whisper paging party to a call
cannot be merged.
Merge checks include:
● not being busy verified by another user
● not a data call
● the call is in either talk or park state
- One exception to this is Converse calls
which are always in nrm_ans_sup()
● no tone connected or bv or conference
tone connected
● not exceed conference limit
● no aux trunk involved in the call
1152
Whisp Pg merge failed
Merge page call with paged call - merge operation
failed.
1153
ARS man activation queing
Manual activation of queueing seen while in ARS
supervision - ARS DAC has been dialed.
1154
Outgoing trk seizure fail
Seize failed. Indicates either:
● a problem with the selected trunk
● an incoming call was received on a trunk
selected for an outgoing call in busy
verification on non-Distributed
Communication System (DCS) call type
and not bridge-on case.
1155
Bsy Vfy digit timeout
Digit timeout while in busy verification on
non-DCS call type and not bridge-on case.
1156
Connection resrce unavail
Connection resource not available. this is an
administered connection.
1157
TTR unavailable
Activate service observing feature. Initiated from a
vector step and only the Feature Access Code of
service observing is in the vector step. End-to-end
signaling digit collection of extension to be
observed could not get a Touch Tone Receiver
(TTR).
1158
Svc Obsv Ext table full
Validation of service observed extension. No room
in software table to store service observing User
IDs.
1159
Cancel wakeup failed
Collect digits for time used by the wakeup
features. Could not cancel wakeup.
1160
Activate wakeup failed
Collect digits for time used by the wakeup
features. Could not activate wakeup time.
Possible causes:
● previous request exists and cancel flag
not set
● wakeup request time is too close
● 15 min interval limit exceeded
● system limit on requests exceeded?
Event
Data 1
Event Data 2
12 of 13
202 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Denial Event Tables
Table 50: Call Process denial events (1001 - 1172) 13 of 13
Event
Type
Event Description, as it
appears on the event log
Explanation
Event
Data 1
1161
Max# connected parties
Whisper page - bridging to a call that has
maximum number of parties already connected.
1162
Max# connected parties
Whisper page - bridging to call that has maximum
number of parties already connected.
1163
TTR TDM VC failed
Time Division Multiplexed (TDM) Voice Condition
(VC) creation for Touch Tone Receiver (TTR)
failed while in whisper supervision.
1164
(also in
Table 51)
ISDN no cause value
Outgoing ISDN trunk rejected/ dropped by far end
1165
Attd ctrl of ARS pref (s)
Attendant control of trunk group access ARS
preference(s).
1166
(also in
Table 51)
Unassigned number
Unassigned number.
1167
Can’t term emergency call
No Attendants or redirection extension assigned
for termination of emergency call.
1168
Second call failed
Russia MultiFrequency (MF) Packet Signaling Second call attempt failed.
1169
Retry option not enabled
Russia MultiFrequency (MF) Packet Signaling.
Either T1 or T2 timer expired, or a B6 signal was
received, and the “Re-try?” option is no.
1170
Erroneous signal received
Russia MultiFrequency (MF) Packet Signaling Erroneous signal received.
1171
ATM Blockage:TDMSVC fail
TDM_SVC failed due to lack of resources, call
was dropped. The caller hears dead air.
1172
Path Rep ASAI to non-ASAI
Path Replace merged from Adjunct Switch
Application Interface (ASAI) callr to non-ASAI
callr.
Event Data 2
DIAG/LOC/CV
13 of 13
Issue 3 February 2007
203
Denial Events
ISDN, IP, and SIP Denial Events
Some Event Type numbers in this section can be re-used for IP and SIP Denial Events. Please
check your log information carefully to determine what type of network experienced the event
that led to the denial, even if the explanation refers to ISDN.
Table 51: ISDN, IP, and SIP-generated denial events (1173 - 1224) 1 of 4
Event
Type
Event Description, as it
appears on the event log
Explanation
Event
Data 1
Event Data 2
1070 (also
in Table 50)
TTR unavailable
ISDN trunk initiation of in-band end-to-end digit
collection failed. Might be waiting for a Touch
Tone Receiver (TTR).
1164
(also in
Table 50)
ISDN no cause value
Outgoing ISDN trunk rejected/ dropped by far
end.
1166
(also in
Table 50)
Unassigned number
Unassigned number.
1173
No route to transit ntwk
No route to specific transit network.
See Cause Value 02.
UID
DIAG/LOC/CV
1174
No route to dest
No route to destination.
See Cause Value 03 on page 150.
UID
DIAG/LOC/CV
1175
ISDN channel unacceptable
Channel unacceptable.
See Cause Value 06 on page 153.
UID
DIAG/LOC/CV
1176
ISDN MLPP circ not resrvd
MLPP preemption, circuit not reserved.
See Cause Value 08 on page 153.
UID
DIAG/LOC/CV
1177
ISDN MLPP circ resv reuse
MLPP preemption, circuit reserved for reuse.
See Cause Value 09 on page 154.
UID
DIAG/LOC/CV
1178
Normal call clearing
Normal call clearing.
See Cause Value 16 on page 155.
UID
DIAG/LOC/CV
1179
User busy
User busy.
See Cause Value 17 on page 155.
UID
DIAG/LOC/CV
1180
No user responding
No user responding.
See Cause Value 18 on page 156.
UID
DIAG/LOC/CV
1181
User alerting, no answer
User alerting, no answer.
See Cause Value 19 on page 157.
UID
DIAG/LOC/CV
1182
Subscriber absent
Subscriber absent.
See Cause Value 20 on page 157.
UID
DIAG/LOC/CV
1183
Call rejected
Call rejected.
See Cause Value 21 on page 157.
UID
DIAG/LOC/CV
1184
Number changed
Number changed.
See Cause Value 22 on page 157.
UID
DIAG/LOC/CV
DIAG/LOC/CV
1 of 4
204 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Denial Event Tables
Table 51: ISDN, IP, and SIP-generated denial events (1173 - 1224) 2 of 4
Event
Type
Event Description, as it
appears on the event log
Explanation
Event
Data 1
Event Data 2
1185
Dest out of order
Destination out of order.
See Cause Value 27 on page 158.
UID
DIAG/LOC/CV
1186
Invalid number format
Invalid number format.
See Cause Value 28 on page 158.
UID
DIAG/LOC/CV
1187
Facility rejected
Facility rejected.
See Cause Value 29 on page 159.
UID
DIAG/LOC/CV
1188
Response status enquiry
Response status enquiry.
See Cause Value 30 on page 160.
UID
DIAG/LOC/CV
1189
Normal, unspecified
Normal, unspecified.
See Cause Value 31 on page 160.
UID
DIAG/LOC/CV
1190
No circ/chan avail
No circuit or channel available.
See Cause Value 34 on page 161.
UID
DIAG/LOC/CV
1191
Network failure
Network failure.
See Cause Value 38 on page 162.
UID
DIAG/LOC/CV
1192
Temporary failure
Temporary failure.
See Cause Value 41 on page 163.
UID
DIAG/LOC/CV
1193
Equipment congestion
Switching equipment congestion.
See Cause Value 42 on page 163.
UID
DIAG/LOC/CV
1194
ISDN user info discarded
User info discarded.
See Cause Value 43 on page 163.
UID
DIAG/LOC/CV
1195
Circ/channel unavail
Requested circuit / channel not available.
See Cause Value 44 on page 164.
UID
DIAG/LOC/CV
1196
ISDN blocked precedence
Locked precedence level.
See Cause Value 46 on page 165.
UID
DIAG/LOC/CV
1197
Resources unavail/unspec
Resources unavailable, unspecified.
See Cause Value 47 on page 165.
UID
DIAG/LOC/CV
1198
ISDN req fac no subscribe
Requested facility no subscribed.
See Cause Value 50 on page 166.
UID
DIAG/LOC/CV
1199
ISDN outgoing call barred
Outgoing calls barred.
See Cause Value 52 on page 167.
UID
DIAG/LOC/CV
1200
ISDN incoming call barred
Incoming calls barred.
See Cause Value 54 on page 167.
UID
DIAG/LOC/CV
1201
Bearer cap not available
Bearer capability not presently available.
See Cause Value 58 on page 169.
UID
DIAG/LOC/CV
1202
Service unauth FranceVN4
Service not authorized / France VN4.
See Cause Value 62 on page 171.
UID
DIAG/LOC/CV
1203
Serv/option unavailable
Service/option not available, unspecified.
See Cause Value 63 on page 171.
UID
DIAG/LOC/CV
1204
Bearer cap not implem
Bearer capability not implemented.
See Cause Value 65 on page 172.
UID
DIAG/LOC/CV
2 of 4
Issue 3 February 2007
205
Denial Events
Table 51: ISDN, IP, and SIP-generated denial events (1173 - 1224) 3 of 4
Event
Type
Event Description, as it
appears on the event log
Explanation
Event
Data 1
Event Data 2
1205
ISDN chan type not implem
Channel type not implemented.
See Cause Value 66 on page 172.
UID
DIAG/LOC/CV
1206
Req facility not implem
Requested facility not implemented.
See Cause Value 69 on page 173.
UID
DIAG/LOC/CV
1207
Only restr digital BC av
Only restricted digital BC available.
See Cause Value 70 on page 174.
UID
DIAG/LOC/CV
1208
Srv/opt not imp/unsp
Service/option not implemented, unspecified.
See Cause Value 79 on page 174.
UID
DIAG/LOC/CV
1209
Invalid call reference
Invalid call reference.
See Cause Value 81 on page 175.
UID
DIAG/LOC/CV
1210
Channel doesn't exist
Identified channel does not exist.
See Cause Value 82 on page 175.
UID
DIAG/LOC/CV
1211
Incompatible dest
Incompatible destination.
See Cause Value 88 on page 177.
UID
DIAG/LOC/CV
1212
ISDN trans ntwk not exist
Transit network does not exist.
See Cause Value 91 on page 178.
UID
DIAG/LOC/CV
1213
Invalid message
Invalid Message.
See Cause Value 95 on page 179.
UID
DIAG/LOC/CV
1214
Mandatory IE missing
Mandatory IE is missing.
See Cause Value 96 on page 179.
UID
DIAG/LOC/CV
1215
ISDN msg typ nonexist/imp
Message type nonexistent or not implemented.
See Cause Value 97 on page 181.
UID
DIAG/LOC/CV
1216
Msg not compat state
Message not compatible with call state.
See Cause Value 98 on page 183.
UID
DIAG/LOC/CV
1217
ISDN nonexistant IE
Nonexistent IE.
See Cause Value 99 on page 184.
UID
DIAG/LOC/CV
1218
Invalid IE contents
Invalid IE contents.
See Cause Value 100 on page 184.
UID
DIAG/LOC/CV
1219
ISDN msg not compat state
Message not compatible with call state.
See Cause Value 101 on page 185.
UID
DIAG/LOC/CV
1220
Recovery on timer expiry
Recovery on timer expiry.
See Cause Value 102 on page 186.
UID
DIAG/LOC/CV
1221
Protocol err unspecified
Protocol Error Unspecified.
See Cause Value 111 on page 189.
UID
DIAG/LOC/CV
1222
ISDN intr ana ntwk Fr VN4
Inter-worked to analog network France VN4
UID
DIAG/LOC/CV
1223
ISDN goto con mode Fr VN4
Go to conversation mode France VN4
UID
DIAG/LOC/CV
1224
Interwork/cause unknown
Inter-working or cause unknown.
See Cause Value 127 on page 190.
UID
DIAG/LOC/CV
3 of 4
206 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Denial Event Tables
Table 51: ISDN, IP, and SIP-generated denial events (1173 - 1224) 4 of 4
Event
Type
Event Description, as it
appears on the event log
Explanation
Event
Data 1
1570 (also
in Table 55)
TTR insertion failed
Processing incoming digits for ISDN call.
Insertion of Touch Tone Receiver (TTR) to
collect in-band digits failed.
1573 (also
in Table 55)
Principal is not ISDN
Get called digits, calling number and name,
etc., and send ISDN SETUP message to the far
end. The principal is not ISDN.
Event Data 2
4 of 4
Call processing Denial Events
Event Types 1000 - 1899 show denial events generated during call processing, as listed in Call
Process denial events (1001 - 1172) on page 191 and Call Process denial events (1225 1899) on page 207.
Table 52: Call Process denial events (1225 - 1899) 1 of 36
Event
Type
Event Description, as it
appears on the event log
Explanation
Event
Data 1
1225
All SBS extensions in use
Separation of Bearer and Signaling (SBS)
Signaling call tried to allocate an SBS extension,
but all SBS extensions are in use.
1226
Cannot get SBS Sig CID
Separation of Bearer and Signaling (SBS) Bearer
call tried to retrieve SBS Signaling call Caller ID.
1227
Can't send SBS ID to orig
Separation of Bearer and Signaling (SBS)
Signaling call tried to send an INFO message
with unique ID, but the INFO could not be sent.
1228
Non-bearer trk to SBS ext
A non-trunk call terminated to an allocated
Separation of Bearer and Signaling (SBS)
extension waiting for the Bearer SBS call to
come.
1229
Unable to get ARS fac
Error occurred when getting the ARS Feature
Access Code in order to build the Separation of
Bearer and Signaling (SBS) complete callback
number.
1230
Unable to get contry code
Error occurred when getting the local country
code in order to build the Separation of Bearer
and Signaling (SBS) complete callback number.
1231
Unable to get intl accode
Error occurred when getting the international
access code in order to build the Separation of
Bearer and Signaling (SBS) complete callback
number.
Event Data 2
1 of 36
Issue 3 February 2007
207
Denial Events
Table 52: Call Process denial events (1225 - 1899) 2 of 36
Event
Type
Event Description, as it
appears on the event log
Explanation
1232
TTR err SBS ID dgt coll
Error occurred when trying to allocate Touch
Tone Receiver (TTR) to collect the Unique ID
in-band at the terminating node.
1233
Invalid SBS ID dgts/tmo
Invalid or partial Separation of Bearer and
Signaling (SBS) Unique ID collected, or interdigit
tmo while collecting Unique ID at SBS
terminating node.
1234
TTR err IGAR ID dgt coll
Error occurred when trying to allocate Touch
Tone Receiver (TTR) to collect the Unique ID
in-band at the originating node.
No VOA/Data Priv Active
VOA not played for this call because data privacy
is active
Invalid IGAR ID dgts/tmo
Invalid or partial Inter-Gateway Alternate Routing
(IGAR) Index collected, or interdigit timeout while
collecting destination IGAR index at IGAR
originating node.
No VOA COR Permissions
COR (Class of Restriction) permissions do not
allow party (agent, Service Observer, etc.) to
hear VOA.
1236
No PSA_DIS with ACD call
Deny Personal Station Access (PSA)
disassociate because there is an Automatic Call
Distribution (ACD) call on the phone.
1237
TTR err IGAR ID dgt coll
Error occurred when trying to allocate Touch
Tone Receiver (TTR) to collect the Unique ID
in-band at the originating node.
1238
Invalid IGAR ID dgts/tmo
Invalid or partial Inter-Gateway Alternate Routing
(IGAR) Index collected, or interdigit timeout while
collecting destination IGAR index at IGAR
originating node.
1239
Deny ACB act to Self
Activation of Automatic Callback (ACB) to self is
not allowed.
1240
No response to IGAR DTMF
E-sigged digits three times with no response from
the far end.
1241
Non-numerics in Invite FNU
Invite FNU contains non-numeric characters in
the extension field.
1242
Off-net cvg/fwd threshold
Redirect off-net coverage or forward was blocked
due to the threshold limit set on the
system-parameters coverage screen.
Communication
Manager
Release
3.0
1234
Communication Manager
Event
Data 1
Event Data 2
Release
3.1
1235
Communication Manager
Release
3.0
1235
Communication Manager
Release
3.1
1243
Bandwidth limit was exceeded on an endpoint or
trunk group.
2 of 36
208 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Denial Event Tables
Table 52: Call Process denial events (1225 - 1899) 3 of 36
Event
Type
Event Description, as it
appears on the event log
Explanation
Event
Data 1
1244
DPT:TTR err idx dgt coll
Error occurred when trying to allocate TTR to
collect the destination IGAR user index
1245
DPT:TTR err UID dgt coll
Error occurred when trying to allocate TTR to
collect calling/called party UIDs
1246
Svs obsrv exceed max
New observer denied, maximum number of
observers already in use
1247
IGAR/DPT LDN grew too big
IGAR/DPT LDN converts to a number that is
longer than ARS can process
1248
1299
not assigned
Event Data 2
begin intercept type source of denials
1300
Digits prevent call route
MultiFrequency Compelled call not routed due to
invalid digit, not enough digits, etc.
1301
Need MFC or TT dial type
Outgoing dial type is not MultiFrequency
Compelled or Touch Tone (TT).
1302
Dgts needed or caller typ
Minimum digits not dialed before pressing feature
button, or calling party is not a station or
attendant.
1303
TTR queue type invalid
Touch Tone Receiver (TTR) queueing problem.
Invalid “ttrq_typ” found.
1304
Dgt absorbtion/insertion
Digit block requires preconditioning for digit
absorption or insertion. Error in treatment. A
Touch Tone Receiver (TTR) is available.
1305
Dgt collection software
Software error. Invalid return code
ttrq_type == ORIG_TTRQ?
y - valid rc: GCOL_AUTO, GCOL_OK
ttrq_type == NO_TTRQ?
y - valid rc: GCOL_AUTO, GCOL_OK
GCOL_ERR, GCOL_ATTD, GCOL_ATTD_NS,
GCOL_NS, GCOL_TTRQ, GCOL_TERM
1306
Satlt dropped TGU B4 ansr
Italian outgoing tie (TGU) call dropped by satellite
before answer.
1307
LoginID UID query failure
Query for User ID of logged-in Logical Agent’s
LoginID failed.
1308
PNT or TIE restriction
Enforce PNT-PNT Restrictions. PTT or TIE not
allowed to connect to this PTT trunk.
1309
Data/Voice BCC setup fail
Trouble setting up voice to data/data to voice
(change Bearer Capability Class) and/or outgoing
Bearer Capability Class (BCC) for ISDN voice
call.
1310
Incompatible term endpnt
Tried to terminate to incompatible endpoint.
1311
Routing software failure
Invalid return code from dpm_rerte. Software
error.
3 of 36
Issue 3 February 2007
209
Denial Events
Table 52: Call Process denial events (1225 - 1899) 4 of 36
Event
Type
Event Description, as it
appears on the event log
Explanation
1312
Route PTRN trunk unavail
No available trunks in the routing pattern.
1313
Remote DTGS invalid digit
Remote Direct Trunk Group Selection (DTGS)
that was processing digits (after tie Trunk Access
Code) from the preprocessing digit buffer to the
digit buffer found invalid digit (digit = 0 or > 0xa).
1314
Dgt collection setup fail
Error during setup for end-to-end signaling digit
collection.
1315
Dgt collection setup fail
Error during setup for end-to-end signaling digit
collection prevented setting an indication in
ttrq_typ that the call was queued during
termination waiting for a Touch Tone Receiver
(TTR) (CODEC_TTR).
1316
No unrstrictd term point
No principal to terminate to, or it is termination
restricted, and there is no termination coverage
point.
1317
Coverage software failure
Software error call_p termination to coverage
point received invalid gm_term return code.
1318
Split UID query failure
Adjunct Switch Application Interface (ASAI)
Direct Agent Call termination fails in querying isg
for split User ID.
1319
Call record sftw failure
Incoming QSIG call completion ringout call.
Failure retrieving suspended Temporary
Signaling Connection (TSC) call record from
service dispatcher.
1320
Call record sftw failure
Incoming QSIG call completion ringout call. Call
completion ringout call record does not match
Temporary Signaling Connection (TSC) call
record retrieved from service dispatcher
suspension.
1321
Illegal term to rmt Audix
Adjunct Switch Application Interface (ASAI)
switch classified call. Illegal attempt to terminate
off-switch to a remote AUDIX.
1322
Data to station w/o H.320
ATA call to station type endpoint, but the station
does not have the H.320 conversion flag set.
1323
Dgt collection setup fail
Authorization code received, terminate to local
extension, origination from ISDN trunk or
endpoint, error during end-to-end signaling digit
collection setup.
1324
Data Ext code calling
Code calling by a data extension.
1325
ASAI SCC to UDP nite svc
ASAI Switch Classified Call (SCC) to hunt group
with UDP night service. This type of call is not
allowed to go off-switch.
1326
MM to Attd ctrld trunk
Multimedia user is not allowed to call a trunk
under attendant control, Attendant Control of
Trunk Group Active (ACTGA).
Event
Data 1
Event Data 2
4 of 36
210 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Denial Event Tables
Table 52: Call Process denial events (1225 - 1899) 5 of 36
Event
Type
Event Description, as it
appears on the event log
Explanation
Event
Data 1
1327
Obtaining Attd UID fails
Call to trunk under attendant control (Attendant
Control of Trunk Group Active (ACTGA)). Failure
getting attendant User ID from dpm.
1328
Term to ACTGA Attd fails
Call to trunk under attendant control (Attendant
Control of Trunk Group Active (ACTGA)). Failure
terminating caller to controlling attendant.
1329
Term to inappropriate pt
Block termination to incoming-only type trunk or
user with voice bearer termination to a DEXT
group.
1330
Iterative term attd-retry
Call termination failure rerouting to attendant.
Retry of termination to attendant was blocked to
prevent an endless retry.
1331
Italian misoperation
Italian misoperation treatment.
1332
Data mod options qry fail
Reserving a pooled modem. Query data module
for its options failed.
1333
Term to modem failure
Seizing (terminating on) a pooled modem failed.
1334
Term to modem failure
Analog endpoint termination to pooled modem
(after administrable time delay expires) failed.
1335
LWC blocked by msg_sv
Leave Word Calling. Async message response
from msg_sv says give user LW_INTRCPT.
1336
Tone detection timeout
Tone detector timeout without receiving a valid
tone.
1337
Intrcpt tone from far end
Intercept tone received before far end answers.
1338
Wait for answer timeout
Wait answer supervision was timedout on a call
from a station or tie trunk.
1339
Auth code required
Digit analysis and routing problem. Authorization
code required.
1340
Rmt cfwd invald local ext
The attendant activated call forwarding for a
remote extension to an invalid local extension.
1341
Non-voice call intercept
Non-voice call was routed to attendant or
announcement for intercept treatment. Switch to
intercept tone treatment.
1342
Dest BCC incompatible
The destination bearer capability code is
incompatible.
1343
Need higher FRL to route
A higher Facility Restriction Level is needed to
route the call.
1344
Hop count restricted
The outgoing call is hop count restricted.
1345
Multiparty caller paging
Accessing paging equipment with more than 1
party on the call is not allowed.
1346
Svc Obsrv from wireless
Service observing is not possible from wireless
stations because they don’t support “off-hook
idle” state.
Event Data 2
5 of 36
Issue 3 February 2007
211
Denial Events
Table 52: Call Process denial events (1225 - 1899) 6 of 36
Event
Type
Event Description, as it
appears on the event log
Explanation
1347
Svc Obsrv dpm query fail
Query of dpm to see if Feature Access Code
service observing is optioned failed.
1348
No Fac Svc Observing
Feature Access Code service observing is not
optioned.
1349
Term dial-up tst brdg app
Feature Access Code entered to do terminal
dial-up test, not allowed on bridged appearances.
1350
Term dial-up tst term typ
Terminal dial-up test is not allowed on attendant,
BRI, wt or analog type terminal, or the terminal
does not have a call appearance active on the
voice channel.
1351
More digits expected
Appending number to end of digit buffer. All digits
have been processed for an Adjunct Switch
Application Interface (ASAI) originated call, but
more digits are expected to be collected.
1352
Port ntwk numbr too large
Facility access test specified a port network
number greater than the maximum allowed
(MAX_PPNS).
1353
Cabinet number too large
Malicious call trace specified a cabinet number
greater than the maximum allowed
(MAX_PPNS).
1354
SSC dialed ext's uid fail
Station Security Code (SSC) digit processing.
The dialed extension’s User ID has lost its
association with the extension number.
1355
Auth code reqired. (ASAI)
Call requires an authorization code. Call is an
Adjunct Switch Application Interface (ASAI)
phantom call. Not allowed.
1356
ASAI SCC VDN destination
The first leg of an Adjunct Switch Application
Interface (ASAI) Switch Classified Call (SCC) has
Vector Directory Number as destination.
1357
LAGT COR/COR restriction
There is a COR-to-COR (Class of Restriction)
between the originating logical agent and
terminating facility.
1358
ASAI SCC term loginID
Adjunct Switch Application Interface (ASAI)
Switch Classified Call (SCC) first leg attempting
to terminate to logical agent loginID. Not allowed.
1359
LoginID extensn qry fail
gm_query failure determining if the loginID
extension used for the Direct Agent call is
associated with a logged-in agent.
1360
ASAI SCC term loginID
Adjunct Switch Application Interface (ASAI)
Switch Classified Call (SCC) first leg attempting
to terminate to logical agent loginID. Not allowed.
1361
Page data call preindictd
Paging is denied if data call preindication was
activated.
1362
FAC follows priority FAC
Priority feature activation code shouldn’t be
followed by other feature activation codes. (auth)
Event
Data 1
Event Data 2
6 of 36
212 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Denial Event Tables
Table 52: Call Process denial events (1225 - 1899) 7 of 36
Event
Type
Event Description, as it
appears on the event log
Explanation
Event
Data 1
1363
FAC follows priority FAC
Priority feature activation code shouldn’t be
followed by other feature activation codes. (route)
1364
FAC follows priority FAC
Priority feature activation code shouldn’t be
followed by other feature activation codes. (other)
1365
More digits needed to rte
Adjunct Switch Application Interface (ASAI) call.
DPM says it needs more digits to route on. There
are no digits left to use in the preprocessing
buffer, and no more digits are expected.
1366
BCC incompatibility
Being called from auth_code(). DPM says digit
analysis is done and we have Bearer Capability
Class (BCC) incompatibility.
1367
BCC incompatibility
Not being called from auth_code(). DPM says
digit analysis is done and we have Bearer
Capability Class (BCC) incompatibility.
1368
MFC out dialing timeout
outgoing MultiFrequency Compelled call under
outpulse supervision. Interdigit or end-of-dialing
timeout without any expectation of user
completing dialing.
1369
Dgt tmout PCOL merge fail
Unexpected digit timeout. Drop of principal finds
that it is a Personal Central Office Line (PCOL)
group User ID. Merge of PCOL member(s) into
the call (pcol_merge()) for disposition via
stndseq() fails.
1370
Digit timeout - drop fail
Unexpected digit timeout. Drop of non-Personal
Central Office Line (PCOL)-type principal failure.
1371
Abbrv Dial DAC limit
Abbreviated Dialing was already dial accessed.
There is a limit of 3 times that the DAC can be
dialed to get digits to route on. This would seem
to have a purpose of preventing looping via
entries in the abbreviated dial lists.
1372
Abbrv Dial list/entry inv
Abbreviated Dialing. Invalid list and/or list entry.
1373
Abbrv Dial software fail
Abbreviated Dialing. Software error while getting
the digits stored in user’s abbreviated dial list.
1374
Agent skills enabled qry
Error while querying system parameters to see if
Expert Agent Selection (EAS) agent skills is
enabled.
1375
Dbl agent login to statn
Agent is logging into a physical station that
already has an agent logged in.
1376
Agent login illegl source
Trunk user or Remote Access user trying to do
Expert Agent Selection (EAS) agent login
operation. Not allowed.
1377
Last ACD call skill qry
Query of UM for last Automatic Call Distribution
(ACD) call’s skill fails. Query of attendant, hunt,
DEXT, paging or Personal Central Office Line
(PCOL) group or Non Call Associated-Temporary
Signaling Connection (NCA-TSC) user
Event Data 2
7 of 36
Issue 3 February 2007
213
Denial Events
Table 52: Call Process denial events (1225 - 1899) 8 of 36
Event
Type
Event Description, as it
appears on the event log
Explanation
1378
No hunt grp for split idx
Split group index from dialed digits is a
non-existent hunt group number.
1379
Agent logout fail (auto?)
Agent logout failure. Might be spl_chk.c. logging
out while auto-available.
1380
Agent login failure
Agent login failure getting number of digits in
logical agents password. Might be login-id User
ID was not found in dpm extension table Ext_e, or
an invalid logical agent login-id extension.
1381
Agent login failure
1382
agent login invalid/error
Login invalid or error condition.
1383
Agent login failure/error
Logical Agent (LAGT) failure getting agent
login-id. Possible causes:
● error initializing agent-stat table
● login for a skill failed
● TRAD logging into split already logged
into
● already logged into maximum number of
splits.
1384
Agent logins maximum'd
Maximum number of simultaneous logins
exceeded or ACPT_LOGIN failed.
1385
Agent passwd digits fail
Failure getting logical agent password digits from
DPM.
1386
Agent passwd mismatch
Agent entered password does not match
administered password.
1387
Agent login invalid/error
Login invalid or error condition.
1388
Login acceptance fails
Logical Agent login processing of ACPT_LOGIN
message to the la_spl_chk routine fails.
1389
Agent login max/error
Maximum number of simultaneous logins
exceeded, or this agent failed the login digits
check (for example, this agent is using someone
else’s login-id).
1390
Work mode change failed
Change of Agent Work Mode to after-call-work
failed.
1391
Work mode change failed
Change of Logical Agent Work Mode to aux-work
failed.
1392
Work mode change failed
Change of Agent Work Mode to man_in failed.
1393
Work mode change failed
Change of Agent Work Mode to auto-in failed.
1394
Agent feat act FAC error
Unrecognized Feature Access Code being
processed for Automatic Call Distribution (ACD)
agent feature activation.
Event
Data 1
Event Data 2
● An agent logging into MCH split or
adjunct controlled split is already logged
in
● The Expert Agent Selection (EAS)
Enabled field on system-parameter
features form is n
8 of 36
214 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Denial Event Tables
Table 52: Call Process denial events (1225 - 1899) 9 of 36
Event
Type
Event Description, as it
appears on the event log
Explanation
Event
Data 1
1395
Agent sup assist rqst er
Agent requesting supervisor assist. Possible
causes:
● split group invalid
● agent not logged in
● split group has no supervisor
● administered
1396
Split invalid/agent login
Adjunct Switch Application Interface (ASAI)
requesting supervisor assist. Possible causes:
● split group invalid
● agent not logged in
1397
Direct agent call setup
Supervisor assisted call to Expert Agent
Selection (EAS) login ID. Error encountered in
setting up Direct Agent Call.
1398
Direct agent calling COR
Supervisor assisted call to Expert Agent
Selection (EAS) login ID. Direct agent calling
Class of Restriction (COR) check failure.
1399
EAS not enabled
Activating Add/Remove Skill feature but Expert
Agent Selection (EAS) is not enabled.
1400
EAS not enabled
Activating Add/Remove Skill feature but Expert
Agent Selection (EAS) is not enabled.
1401
COR_AR_SKL query failure
Activating Add/Remove Skill feature
COR_AR_SKL dpm_query failed. User ID
structure not found.
1402
Skills COR restricted
Activating Add/Remove Skill feature. User has no
Class of Restriction (COR) permission to Add/
Remove Agent Skills.
1403
Console prmsn, EAS agent
Activating Add/Remove Skill feature. User has no
console permission and is not an Expert Agent
Selection (EAS) Agent. Activator is wrong type.
1404
LoginID prompt setup err
Activating Add/Remove Skill feature. Error in
setting up the prompt for agent’s loginID.
1405
Skills prompt setup err
Setting up prompting for skill number in the Add/
Remove Skills feature. Error in setting up prompt
for agent’s skills.
1406
LoginID tenant nbr fail
Add agent. Skills translations failed to get the
Tenant Number for the agent’s loginID.
1407
Skills tenant nbr fail
Add agent Skills translations. Failed to get the
Tenant Number for the agent’s skill.
1408
Tenant number mismatch
Add agent Skills translations. Tenant Number of
the Expert Agent Selection (EAS) agent’s loginID
does not match the Tenant Number of the skill
being added.
1409
Skill level out of range
Add agent Skills translations. Skill level out of
range.
1410
DAC skill nbr qry failed
Remove agent Skills translations. dpm_query for
Logical Agent’s (LAGT) DAC skill number failed.
Event Data 2
9 of 36
Issue 3 February 2007
215
Denial Events
Table 52: Call Process denial events (1225 - 1899) 10 of 36
Event
Type
Event Description, as it
appears on the event log
Explanation
1411
DAC skill not removable
Remove agent Skills translations. Logical agent’s
DAC skill is not removable.
1412
Skills ftr msg failure
Add/Remove agent Skills translations. Add/
Remove Skills feature message sending to
station server failed. (SS_AR_SKL)
1413
DAC agent dest/split
Adjunct Switch Application Interface (ASAI) third
party direct agent call. Process CP_DIR_AGENT
message from ISG. No DAC agent destination or
split specified in message.
1414
DAC agent dgts to uid
Adjunct Switch Application Interface (ASAI) third
party direct agent call. Process CP_DIR_AGENT
message from ISG. DAC agent digits conversion
to User ID. failure.
1415
DAC msg err/agent login
Adjunct Switch Application Interface (ASAI) third
party direct agent call. process CP_DIR_AGENT
message from ISG. Possible causes:
● adjunct agent not logged in
● adjunct gave the switch a wrong agent
extension
● adjunct gave the switch a wrong split
extension
1416
Auth code dgt coll fail
Collecting authorization code digits as end-to-end
signaling failed.
1417
TTR queueing invalid
Collecting authorization code digits. “TTR
queueing occurred in remote access” is indicated
in Touch Tone Receiver (TTR) of callr - not valid
in this routine.
1418
Bsy vfy trk member
Error on query for busy status. Possible causes:
trunk member specified greater than maximum
trunks in group, or corrupted trunk index after a
tape read.
1419
COS restrctn Rus Intrsn
User’s Class of Service does not allow access to
Russian Power Trunk Intrusion feature.
1420
Bsy vfy call merge fail
Merging the busy-verifying call with the
busy-verified call. Failure to find an available
callr2 party slot.
1421
Bsy vfy termination fail
Terminating the busy-verifying call to a trunk.
Failure to find an available caller party slot.
1422
Bsy vfy termination fail
Terminating the busy-verifying call to a trunk.
Error getting the trunk’s index into the tmem_tbl
1423
Software invalid stim
Remote user activation/deactivation of a type of
attendant call forwarding - stimulus other than
CP_ACFON, CP_ACFBDAON or CP_ACFOFF
received.
1424
Cfwd dest dgts storage
Activation of call forwarding. Call forward
destination address digits did not all get stored.
1425
Cfwd actvt error/denial
Activation of call forwarding. Error or denial of
activation.
Event
Data 1
Event Data 2
10 of 36
216 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Denial Event Tables
Table 52: Call Process denial events (1225 - 1899) 11 of 36
Event
Type
Event Description, as it
appears on the event log
Explanation
Event
Data 1
1426
Off prem extension size
Request remote switch to activate CF on one of
its local extensions. Answer Distributed
Communication System (DCS) off-premise
station extension size is defined by destination
digits dialed.
1427
FWDed party extension nbr
Activating call forwarding. Feature button IDs
forwarded party extension number for which we
cannot find a user ID.
1428
Phys ext not cfwd avail
Logged-in Expert Agent Selection (EAS) agent’s
physical extension is unavailable for any “simple”
(on switch?) call- forwarding.
1429
Rmte cfwd not allowed
Disallow remote call-forwarding of an Expert
Agent Selection (EAS) loginID extension in all
cases (for example, whether the loginID is logged
into a terminal or not).
1430
COS deny cfwd activate
User’s Class of Service does not allow this call
forwarding activation.
1431
Cfwd deact not allowed
Expert Agent Selection (EAS) agents are not
permitted to deactivate call forwarding.
1432
Cfwd deact err/denial
Deactivation of call forwarding. Error or denial of
deactivation.
1433
Held xfr call missing
Converse Data Return requires that there be a
call held due to transfer while processing the
Converse Data return code (CONV_DAT_RET).
1434
Held call retrieval fail
Converse Data Return processing failed to
retrieve the suspended call record from the SD
for the held call. The held call must be active on a
Converse vector step.
1435
Invalid vec step typ/pty
Converse Data Return processing encountered
an invalid vector step type (not V_CONVERSE)
or the party is invalid.
1436
No COS for ctl rstrctn
User Class of Service does not allow activation/
deactivation of controlled restrictions.
1437
Sys parm - dir call pkup
Directed-call-pickup system parameter is not
enabled.
1438
Invalid usr dir call pkup
Directed call pickup attempt from invalid user (for
example, not a station or attendant).
1439
Dir call pkup COR rsrtrct
Directed call pickup attempt from user without
Class of Restriction (COR) permission.
1440
Dir call pkup non-station
Directed call pickup attempt on a call to an
endpoint other than a station.
1441
Dir call pkup COR rsrtrct
Directed call pickup attempt to a station that has
no Class of Restriction (COR) permission to
accept directed call pickup.
Event Data 2
11 of 36
Issue 3 February 2007
217
Denial Events
Table 52: Call Process denial events (1225 - 1899) 12 of 36
Event
Type
Event Description, as it
appears on the event log
Explanation
1442
Ring check query failure
Directed call pickup attempt. Failure of UM query
to see if called station is still ringing before
completing the pickup to it.
1443
COS deny dat pvcy ftr act
User’s Class of Service does not allow activation
of the data privacy feature.
1444
DS0 test call invalid
DS0 test call is valid only for incoming data trunk
calls.
1445
Rmt emrg accs to attd dny
Emergency access call to attendant is not
permitted from a remote user.
1446
Port ID/UID mapping fail
Facilities Access Test call. Trunk or Touch Tone
Receiver (TTR) port_id->User ID mapping failed.
1447
TTR port type query fail
Facilities Access Test call - Touch Tone Receiver
(TTR) test. CM query for TTR port type fails.
1448
Tested not trunk or TTR
Facilities Access Test call - user type being tested
is neither a trunk or Touch Tone Receiver (TTR),
but logic that got us here thought it was.
1449
Vis Imprd Svc incompatibl
Facilities Access Test call - this feature is not
compatible with Visually Impaired Service.
1450
FAT call error
Facilities Access Test call. Possible causes:
● CM error connecting to tone or
maintenance timeslot
● necessary number of digits not dialed for
tone or timeslot call
● on trunk or Touch Tone Receiver (TTR),
call conversion of external ID to internal
ID failed, or portid to User ID mapping
failed.
1451
Connection to music error
Facilities Access Test call to a music port. CM
error connecting to music.
1452
FAT non-ISDN COR rstrct
Facilities Access Test (FAT) call to a trunk. User
is Class of Restriction (COR) restricted from
making a FAT test of the non-ISDN trunk.
1453
FAT test RLT/DID illegal
Facilities Access Test (FAT) call to a trunk. FAT is
allowed for this trunk type, Release Link Trunk
(RLT) or Direct Inward Dialing (DID).
1454
Trk svc state change fail
Facilities Access Test call to a trunk. Failure
moving trunk from out-of-service state to
in-service. Might be a bad User ID.
1455
FarEnd TstLn nbr qry fail
Facilities Access Test call to a PRI trunk. GM
query for far end ISDN test line number failed
(QTC_NUM).
1456
FarEnd TstLn nbr invalid
Facilities Access Test call to a PRI trunk. Invalid
digit in far end test line number.
1457
FarEnd TstLn nbr invalid
Facilities Access Test call to a PRI trunk. Invalid
digit in far end test line number.
Event
Data 1
Event Data 2
12 of 36
218 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Denial Event Tables
Table 52: Call Process denial events (1225 - 1899) 13 of 36
Event
Type
Event Description, as it
appears on the event log
Explanation
Event
Data 1
1458
Wrg Bch svc/usg/mnt state
Facilities Access Test (FAT) call to a PRI trunk.
Wrong B-channel service, usage or maintenance
state to allow FAT test.
1459
Bad user Id
Facilities Access Test call to a trunk. Might be a
bad User ID.
1460
Trk grp qry/get TAC
Facilities Access Test call to a trunk. um_query
failure getting trunk’s group User ID
(QTRKGRPUID)? dpm_dgtget() failure getting
trunk group’s “real” dial access code.
1461
User Cverage path missing
User activating Send All Calls does not have
coverage path allowing Send All Calls. If user is
an Expert Agent Selection (EAS) agent neither
the agent or station has a coverage path.
1462
Split group digits wrong
User activating/deactivating Position Busy.
Wrong number of digits used to specify split
group.
1463
Agent denied in split group
Agent deactivating Position Busy, not allowed in
split group.
1464
Agent not in aux work
Agent not in AUX_WORK activating Position
Busy.
1465
SAC unavail to attd
Send All Calls (SAC) or Position Busy feature
activation/deactivation denied (for example,
attendant is not allowed to activate/deactivate
SAC).
1466
No call to xfr to AUDIX
Route transferred or call conferenced to AUDIX.
There is no held call that would be transferred/
conferenced in with AUDIX.
1467
No call to xfr to AUDIX
Route transferred or call conferenced to AUDIX,
but the calling party was disconnected.
1468
Inelgbl invoker xfr AUDIX
Route transferred or conferenced call to AUDIX.
Only the principal or covering user (or bridges of
them) are allowed to invoke this feature.
1469
Invld remote ADX mach-nbr
Route remote transfer to AUDIX. Failure getting
the remote principal’s AUDIX Machine number.
1470
No ADX mach-nbr/
node-name
Route remote transfer to AUDIX. The remote
principals AUDIX Machine number does not
translate into an adjunct index. (QAX_ADJ_IDX)
1471
Invalid AUDIX mach-nbr
Route remote transfer to AUDIX. The remote
principal’s AUDIX Machine number received is
“0”. dpm query for user’s serving AUDIX index
fails.
1472
Invalid AUDIX mach-nbr
Route remote transfer to AUDIX. The remote
principal’s AUDIX Machine number received is
“0”. dpm query for user’s serving AUDIX index
received “0”. Query of grp_m for the first AUDIX
whose DCS link is up fails.
Event Data 2
13 of 36
Issue 3 February 2007
219
Denial Events
Table 52: Call Process denial events (1225 - 1899) 14 of 36
Event
Type
Event Description, as it
appears on the event log
Explanation
1473
No local AUDIX mach-nbr
route local transfer to AUDIX. the local principals
AUDIX Machine number received is “0”. dpm
query for user’s serving AUDIX index fails.
1474
No primary AUDIX hnt grp
Route transfer to AUDIX. Query for an AUDIX.
Adjunct’s Primary Transfer into AX Hunt Group
failed.
1475
No ADX hnt grp-cvg path
Route local non-vector transfer to AUDIX. AUDIX
hunt group is not in the principal’s coverage path.
1476
Dat pvcy/rstrct ICOM call
User with data privacy or data restriction is trying
to originate an ICOM call. This is not allowed.
1477
Invalid ICOM grp/dial cod
ICOM call handling. Invalid ICOM group or ICOM
dial code of terminating station. (icm_route())
1478
Block iteratve Lst Nbr Dl
Last Number Dialed was accessed through an
Abbreviated Dialing list. Do not allow it again.
1479
LND digits - DPM fail
User’s Last Number Dialed (LND) digits were not
returned successfully by dial plan manager.
(DPM_LND)
1480
LND digits - DPM fail
User’s Last Number Dialed (LND) digits were not
returned successfully by dial plan manager.
(software error)
1481
MASI setup not incmg ISDN
Multimedia Application Server Interface (MASI)
path setup call - valid only for incoming ISDN
calls.
1482
MCT on DCS trk disallowed
User activating Malicious Call Trace for a DCS
trunk not allowed.
1483
MCT target type invalid
Malicious Call Trace target cannot be a group
User ID. Target PORT entered, must be a regular
TRUNK port or PRI.
1484
MCT target not in a call
Malicious Call Trace target must actually be
involved in a call.
1485
MCT call serv_d rtrv fail
Malicious Call Trace cannot retrieve callr from
serv-d for the call being traced.
1486
MCT trace resorce unavail
Malicious Call Trace activation by button could
not get trace resources from GRP_M.
1487
MCT start invld ctlr alrt
Malicious Call Trace start invalid controller
alerting return code from GRP_M (mct_start()).
1488
MCT deact dny by GRP_M/er
Malicious Call Trace deactivation (not via
busyout) denied by GRP_M or error. (mct_end())
1489
MCT activator grp uid/uid
Malicious Call Trace activation failure getting
individual User ID from activator group User ID.
1490
MCT activator COR rstrctd
Malicious Call Trace (MCT) activation. Activator’s
Class of Restriction (COR) does not allow MCT
feature access.
Event
Data 1
Event Data 2
14 of 36
220 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Denial Event Tables
Table 52: Call Process denial events (1225 - 1899) 15 of 36
Event
Type
Event Description, as it
appears on the event log
Explanation
Event
Data 1
1491
Trk ext/int ID cnvsn fail
Malicious Call Trace request targeted to a trunk
port ID. Failure converting the external ID
(cabinet, carrier, slot, circuit) into an internal ID
(angel, circuit). (dig23dportid() - ATM,
dig2portid()).
1492
MCT act on trk pt ID fail
Malicious Call Trace request targeted to a trunk
port ID. failure activating MCT for given trunk pt
ID.
1493
AD prg from non station
Abbreviated dialing programming is messaging
the station server to enter a different mode and
prepare for digit collection. Only simple users
allowed. Wrong user type.
1494
Extension/passwd required
Coverage message retrieval. Remote access not
allowed unless the user supplies the extension
and password.
1495
Local only/annc dest/uid
Announcement record/playback session. Only
local calls to the announcement are allowed. Call
destination must be an announcement group.
Must have a User ID slot for the announcement
board.
1496
Annc ID needed/conn fail
Begin integrated announcement session.
Integrated announcement not identified
(ann_sess()). cm_pt_conn failure or invalid Caller
ID root (au_sbegin()).
1497
Restricted by COS
User’s Class of Service does not permit one of:
● Leave Word Calling-cancel
● AP Demand Print
● voice synthesis principal message
retrieval
● voice synthesis coverage message
retrieval
● integrated announcement session
1498
MM call software failure
MultiMedia Call Handling multimedia call
activation from voice station. Notification of
USER_M failed.
1499
MM failure getting BCC
MultiMedia Call Handling multimedia call
activation from voice station button. Failure
getting bearer capability from USER_M.
1500
Ext nbr or page typ invld
Failure getting Code Call paging ID
corresponding to dialed extension. Invalid
extension number or page type.
1501
Page call park failure
Drop paging equipment, start park timer, and park
call permanently. There is no record in callr of a
call having been parked during a page.
1502
Drop software failure
Paging zone seizure denied. gm_drop() problem
returned other than GDRP_OK, GDRP_ANS, or
GDRP_OUT.
1503
Answer back merge failure
Answer parked call, give confirmation tone to
parked party, merge 2 calls. Have no call record
of party originating answer back.
Event Data 2
15 of 36
Issue 3 February 2007
221
Denial Events
Table 52: Call Process denial events (1225 - 1899) 16 of 36
Event
Type
Event Description, as it
appears on the event log
Explanation
1504
Answer back merge failure
Answer parked call, give confirmation tone to
parked party, merge 2 calls. No call parked on
this extension.
1505
Answer back merge failure
Answer parked call, give confirmation tone to
parked party, merge 2 calls. Unknown return from
GRP_M retrieval of Caller ID of the parked call.
1506
Answer back merge failure
Answer parked call, give confirmation tone to
parked party, merge 2 calls. Unknown return from
GRP_M unpark of call if the last party drops.
1507
Answer back merge failure
Answer parked call, give confirmation tone to
parked party, merge 2 calls. Accessing the callr of
the parked call failed retrieval from serv-d.
1508
Unparking vec ctrld call
Answer parked call, give confirmation tone to
parked party, merge 2 calls. Deny the unpark
(answer back) attempt if the parked call is under
vector control.
1509
Answr back station dialed
Answer parked call, give confirmation tone to
parked party, merge 2 calls. User ID of station
dialed for answer back differs from park_uid in
call_r.
1510
COR/COR user restricted
Answer parked call, give confirmation tone to
parked party, merge 2 calls. COR-to-COR (Class
of Restriction) between user where call is parked
and users in answer back callr.
1511
Parked call already dropd
Answer parked call, give confirmation tone to
parked party, merge 2 calls. The parked call was
already dropped by the originator but the chimes
haven’t finished yet.
1512
Too many parties to merge
Answer parked call, give confirmation tone to
parked party, merge 2 calls. The merge is not
possible because cannot find an empty slot in
callr2.
1513
Park call on station only
Trying to park a call on a non-station type user.
must park on a user with a SMPL group type.
1514
No call to park
There is no conference pending. The caller to be
parked must have dropped or been dropped.
1515
Park ftr serv_d failure
Failure encountered releasing the callr to serv_d.
1516
Park ftr serv_d failure
Failure encountered retrieving the callr from
serv_d.
1517
Park ftr serv_d failure
Failure encountered retrieving the callr from
serv_d.
1518
Too many park conferees
Too many conferees in the call to allow parking.
1519
Vector active cant park
Vectoring is active on the held call. Cannot allow
the held call to be parked.
1520
Park ftr serv_d failure
Failure encountered releasing the callr to serv_d.
Event
Data 1
Event Data 2
fail code
(for example,
DPXFR_DENY
_9)
16 of 36
222 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Denial Event Tables
Table 52: Call Process denial events (1225 - 1899) 17 of 36
Event
Type
Event Description, as it
appears on the event log
Explanation
Event
Data 1
1521
Park ftr serv_d failure
Failure encountered retrieving the callr from
serv_d.
1522
TAAS from guest room
Pickup for Call Pickup or Trunk Answer Any
Station (TAAS). Attendant backup alerting is
active, maid status is dialed from guest room on
station doing pickup. Might be maid is invoking
TAAS from guest room.
1523
Not a pickup grp mbr
Pickup for Call Pickup or Trunk Answer Any
Station (TAAS). Pickup initiator is not a member
of a pickup group.
1524
Picked up call ID error
Pickup for Call Pickup or Trunk Answer Any
Station (TAAS). Error encountered getting call ID
of call to be picked up.
1525
Call pickup from adjnct
Pickup for Call Pickup or Trunk Answer Any
Station (TAAS). Pickup of call originated by an
adjunct is not allowed.
1526
Pickup of call wait call
Pickup for Call Pickup. Pickup of a call waiting
call is not allowed.
1527
Pickup of converse call
Pickup for Call Pickup or Trunk Answer Any
Station (TAAS). Trying to pickup a converse call,
this is not allowed. Passing data efficiently to a
party that has already cut through on the call
cannot be handled.
1528
Pickup of self's call
Stations A and B are in same pickup group.
Station A calls Station B, holds, and dials Feature
Access Code for pickup. Disallow pickup of
self-initiated call.
1529
Pickup COR/COR usr rstrct
Pickup for Call Pickup or Trunk Answer Any
Station (TAAS). COR-to-COR (Class of
Restriction) restriction between the initiator of
pickup and user(s) of the call being picked up.
1530
Priority call COS denied
Caller’s Class of Service does not allow initiation
of priority calling treatment of call.
1531
Priority call COS denied
Caller pushes the priority calling button after the
call has been dialed, but before it is answered.
Caller’s Class of Service does not allow initiation
of priority calling treatment of call.
1532
Passwd storage exhausted
Dual Tone MultiFrequency (DTMF) password
collection for audio add-on party in VSP-MCU
passworded conference. No room in opls_dig to
store conference password - should never
happen.
1533
Invalid TTR queueing type
Dual Tone MultiFrequency (DTMF) password
collection for audio add-on party in VSP-MCU
passworded conference. Touch Tone Receiver
(TTR) queing type in callr has invalid indication
whether or where TTR queing occurred.
Event Data 2
fail code
(for example,
DPXFR_DENY
_9)
17 of 36
Issue 3 February 2007
223
Denial Events
Table 52: Call Process denial events (1225 - 1899) 18 of 36
Event
Type
Event Description, as it
appears on the event log
Explanation
1534
Software invalid stim
Performing the callback of a party after the call
has been queued. Invalid Call Processing (CP)
message being processed and passed from a
call supervisor.
1535
ACB held call dropped
Analog station flashooks and dials Automatic
Callback (ACB) activation Feature Access Code.
The call from which the user flashed is to be
removed from hold and used to activate ACB.
The call didn’t get held or it disappeared.
1536
GRP_M que service error
GQSRV_ERR error returned from gm_qsrvc().
1537
Callback type sftw error
Invalid callback type returned by gm_query().
1538
Auto callback COS denied
User’s Class of Service does not allow activation
of Automatic Callback feature.
1539
Callback type qry failed
gm_query() for callback type failed.
1540
Callback type qry failed
Invalid callback type returned by gm_query().
1541
Invalid call ID/conn fail
Switch has answered remote access call. Set up
end-to-end signaling digit collection. Invalid
Caller ID or Touch Tone Receiver (TTR)
connection failure. (tu_ecoll_dg(), bch_ecoll_dg()
-).
1542
TTR queueing error
Switch answered a remote access call. Set up
end-to-end signaling digit collection. Touch Tone
Receiver (TTR) queueing erroneously occurred
in auth_feat().
1543
Telcmt accss ext qry fail
Switch answered a remote access call and set up
end-to-end signaling digit collection. Failure
querying DPM for User ID of telecommuting
access extension.
1544
Barrier/auth cod qry fail
Switch answered a remote access call and set up
end-to-end signaling digit collection. Invalid
response from DPM on query for whether barrier
code and authorization code are needed.
(dpm_remqry())
1545
Acct code length qry fail
Query of DPM for SMDR account code length
failed.
1546
Held call serv_d failure
Handle T120 requests for a video conference.
Accessing the callr of the held call failed retrieval
from serv-d.
1547
Video conf deact flag er
T120 request for deactivation of video
conference, but the call has no indication that a
video conference exists. (mm_dataconf_on)
1548
Dat drop not frm dat orig
T120 request for deactivation of video
conference. It is only valid to drop data from the
originator of data. The user who pressed the
button is not the originator.
1549
T120 drop CM failure
CM failure on T120 drop request from valid user
with T120 on.
Event
Data 1
Event Data 2
18 of 36
224 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Denial Event Tables
Table 52: Call Process denial events (1225 - 1899) 19 of 36
Event
Type
Event Description, as it
appears on the event log
Explanation
Event
Data 1
1550
T120 activate CM failure
CM failure on Feature Access Code dialed
request for T120 activation.
1551
Invalid test tone specfd
Terminating trunk transmission test call. Invalid
test tone specified for connection to the call.
1552
Whisp pg elgblity qry err
Query of GRP_M for whisper page eligibility
encountered an error or the response was
invalid.
1553
Whisp pg too many parties
Activate whisper page answer ftr. callr party block
has no slot available for the page originator.
1554
Whisp pg ansr merge fail
Activate whisper page answer ftr. switch of the
Caller ID of the paging party from the original call
failed (um_wpswap())
1555
Whisp pg too many parties
Merging the paging call with the paged call. callr2
party block has no slot available for the merged
call.
1556
Annc/music connect fail
Wakeup announcement verification. Failure of
the CM to connect a wakeup announcement or
music to the call.
1557
Wakeup annc vfy COS deny
Call originator does not have Class of Service
permission to verify wakeup announcements.
1558
Maid status PMS msg fail
Sending the PMA_MDSTATUS message to the
PMS failed.
1559
Maid status ext COS deny
Maid status Feature Access Code dialed from a
room station that does not have Class of Service
permission.
1560
Maid info digits qry fail
Query of DPM for number of maid info digits
failed.
1561
Maid status PMS msg fail
Send of a PMA_MDSTATUS message to the
PMS failed.
1562
Maid status ext COS deny
Maid status Feature Access Code dialed from a
designated station that does not have Class of
Service permission.
1563
Maid status ftr ID invld
Processes the dialed maid status code, but callr
feat_id is invalid for either maid status dialed from
a guest room or from a designated station.
1564
PMS rejects hskp status
Property Management System rejects
housekeeping status v.
1565
PMS hskp response invalid
Property Management System response to
housekeeping status is invalid. (CP_MDRES)
1566
Guest rm station COS deny
Routing call to Property Management System to
log or obtain guest room status. The User ID of
the station entered by the user is not Class of
Service identified as a guest room station.
Event Data 2
19 of 36
Issue 3 February 2007
225
Denial Events
Table 52: Call Process denial events (1225 - 1899) 20 of 36
Event
Type
Event Description, as it
appears on the event log
Explanation
1567
Maid info digits qry fail
Routing call to Property Management System to
log or obtain guest room status. Query of DPM for
number of maid information digits failed.
1568
Maid status PMS msg fail
Routing call to Property Management System
(PMS) to log or obtain guest room status. Send of
a PMA_MDSTATUS message to the PMS failed.
1569
Voice msg type call_r flg
Digit timeout waiting for entry of Do Not Disturb
turn-off time or entry of Automatic Wakeup time.
callr does not have this flagged as a Voice
message type call (vtype).
1570 (also
in Table 51)
TTR insertion failed
Processing incoming digits for ISDN call.
Insertion of Touch Tone Receiver (TTR) to collect
in-band digits failed.
1571
WSS no callng pty nbr IE
Processing incoming digits for ISDN call. A
General Central Office (GCO) Wireless
Subscriber System (WSS) call origination denied
- no calling party number IE was sent.
1572
Call hndlng/usg alloc err
Processing incoming digits for ISDN call.Eerror
during Incoming Call Handling Treatment or
Usage allocation Check (GM_ISDNDIG).
1573 (also
in Table 51)
Principal is not ISDN
Get called digits, calling number and name, etc.,
and send ISDN SETUP message to the far end.
The principal is not ISDN.
1574
SETUP msg IEs not created
Get called digits, calling number and name, etc.,
and send ISDN SETUP message to the far end.
IEs necessary for SETUP not created and stored
in the IAP.
1575
SETUP msg send failed
Get called digits, calling number and name, etc.,
and send ISDN SETUP message to the far end.
The “send” failed. (trk_setup(), um_setup())
1576
ISDN routing failure
Get called digits, calling number and name, etc.,
and send ISDN SETUP message to the far end.
Routing failure. (gm_routepat())
1577
ISDN SETUP msg failure
ISDN trunk group Trunk Access Code dialed or
simulated Q931_REC IEs set up and stored in
iap, and request send of SETUP msg. cp_setup()
returned a failure error.code. suser_m got a
failure indication from the gip in trying to send the
ISDN SETUP message?
1578
Inc tst call 2many partys
Incoming test call for talk/listen on same timeslot.
Failure to find an available callr party slot.
1579
Inc tst call wrg usr type
Incoming test call for talk/listen on same timeslot.
This type of test call is not permitted to access
the user type.
Event
Data 1
Event Data 2
20 of 36
226 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Denial Event Tables
Table 52: Call Process denial events (1225 - 1899) 21 of 36
Event
Type
Event Description, as it
appears on the event log
Explanation
Event
Data 1
1580
Must be ISDN trunk group
Check for usage allocation restrictions on
incoming overlap receiving calls. Possible
causes:
● not ISDN trunk group
● insane index into the call by call data
table
● get_tmem() failure from GRP_M
usage_chk()
● Unexpected error from inc_cuap_sf()
1581
Passwd digits err/timeout
MCU audio add-on password supervision.
Possible causes:
● digit timeout before collecting all the
digits
● an invalid digit
● a set of digits that does not match the
conference password
1582
Spvsr state/feat_id wron
Generating intercept via CP_REORDER with sup
= ACT_TTI_SUP (for Terminal Translation
Initiation digit collection) and feat_id !=
CHG_SEC (Change station security code).
Possible causes:
● wrong supervisory state
● wrong feat_id in callr
1583
Spvsr state/feat_id wrong
Generating intercept via CP_CONFTONE with
sup = ACT_TTI_SUP (for Terminal Translation
Initiation digit collection) and feat_id !=
CHG_SEC (Change station security code).
Possible causes:
● wrong supervisory state
● wrong feat_id in callr
1584
Software invalid stim
Software error. Invalid Call Processing (CP)
stimulus received while in supervision state that
handles Terminal Translation Initiation (TTI) digit
collection during dialing of the TTI security code
and extension.
1585
Abbrv Dial invalid digit
Invalid digit detected while processing
abbreviated dialing.
1586
Abbrev dial prg rejected
Rejection of abbreviated dialing programming
from station server.
1587
Agent extension invalid
Add/Remove Agent Skills. Feature Access Code
was dialed by a user with console permissions,
but the agent-loginID extension entered is not a
valid Expert Agent Selection (EAS) AGENT
extension.
1588
Skill grp nbr illegal
Add/Remove Agent Skills feature has been
invoked and the Skill number has been collected.
It does not represent a legal skill group number.
1589
Skill number invalid
Add/Remove Agent Skills feature has been
invoked and the Skill number is not valid.
1590
System or software error
Add/Remove Agent Skills feature has been
invoked. STN_SV encountered system or
software error.
Event Data 2
21 of 36
Issue 3 February 2007
227
Denial Events
Table 52: Call Process denial events (1225 - 1899) 22 of 36
Event
Type
Event Description, as it
appears on the event log
Explanation
1591
Digit collection error
Add/Remove Agent Skills feature has been
invoked. Error in digit collection.
1592
Routing not to a station
QSIG Call Completion ringout call from remote
originating party. Routing erroneously to a local
facility that is not an SMPL station.
1593
Digit tmo/invld rsn code
Interdigit timeout or invalid reason code entered
during Expert Agent Selection (EAS) aux work
and logout reason code digit collection is in
progress.
1594
Software invalid stim
Code Call paging seizure supervision received a
Call Processing (CP) stimulus from one of a big
list of incompatible feature CP stimulus.
1595
Cfwd tenant parttn rstrct
Attendant-activation of call forwarding, and
extended administration of call forwarding. Error
or access denial resulted from TENANT_CHECK
where originator’s partition is restricted from
accessing partition of extension being
administered for call forwarding.
1596
Attd must enter station
Attendant-activation of call forwarding, and
extended administration of call forwarding. The
extension being administered is not a simple
station user.
1597
Attd cant fwd attd calls
Attendant-activation of call forwarding, and
extended administration of call forwarding.
Attendant is not allowed to forward its own calls.
1598
Feature ID invalid
Attendant-activation of call forwarding, and
extended administration of call forwarding. The
feature ID in callr feat_id is wrong for the Call
Processing (CP) stimulus being processed by
this supervisor.
1599
Change cvg COR restricted
Attendant-activation of call forwarding, and
extended administration of call forwarding.
Change coverage Feature Access Code was
dialed. Class of Restriction (COR) of dialed
extension does not permit change coverage.
1600
Software error
Attendant-activation of call forwarding, and
extended administration of call forwarding.
CP_REJECT - partial perch write in station server
to administer the new active coverage option
failed.
1601
Software invalid stim
Attendant-activation of call forwarding, and
extended administration of call forwarding. Invalid
Call Processing (CP) stimulus type sent to this
supervisor.
1602
Cfwd act to paging grp NA
Call forwarding supervision. Activating call
forwarding to a paging group is not allowed.
1603
Cfwd offnet COS restrcted
Call forwarding supervision. Activating call
forwarding off-net is not allowed for this user.
check the Class of Service permissions.
Event
Data 1
Event Data 2
22 of 36
228 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Denial Event Tables
Table 52: Call Process denial events (1225 - 1899) 23 of 36
Event
Type
Event Description, as it
appears on the event log
Explanation
Event
Data 1
1604
Cfwd offnet COS restrcted
Call forwarding supervision. Activating call
forwarding off-net via AAR/ARS is not allowed for
this user. Check the Class of Service
permissions.
1605
Cfwd to self denied
Call forwarding supervision. Call forwarding to
self is prevented.
1606
Software error
Call forwarding supervision. Invalid feedback
message type received with CP_FEEDBK type
stimulus to this supervisor from dap function.
1607
Software invalid stim
Call forwarding supervision. invalid Call
Processing (CP) stimulus type sent to this
supervisor.
1608
Routing not to data user
The “routed to” party is not a Data User.
1609
Local rtg must be to sta
QSIG Call Completion ringout call from the
remote originating party. Routing locally, but not
to a station. This is not allowed.
1610
Party count not = 1
Prepare to collect deluxe paging & park
extension. The callr pty_cnt is not = 1.
1611
Not MM station/chnl busy
Sending down the MultiMedia Call Handling
Basic mode activation message to the User
Manager fails. Possible causes:
● station not part of Multi-media
● data user busy on at least one channel.
1612
Svc link creation failure
Sending down the MultiMedia Call Handling
Enhanced mode deactivation message to the
User Manager fails. Might be the creation of a
service link failed.
1613
BCC query failed
MultiMedia Call Handling multinumber type call.
Query of USER_M for bearer capability failed.
1614
Ctrl rstrct/DND fail
Controlled restriction activation/ deactivation, with
possible interaction with do-not-disturb. Failure
return from (dpm_crstrict() or awu_cancel()).
1615
Rstrct typ/featid/usr id
Initial processing supervision for controlled
restriction. Possible causes:
● originator’s User ID not found in
DP_MGR User ID data tables
● restriction digit does not identify with
outward, total, termination or
station-to-station type restriction
● featid is not one of:
- activate user control restriction
- deactivate user control restriction
- activate group control restriction
- deactivate group control restriction
Event Data 2
23 of 36
Issue 3 February 2007
229
Denial Events
Table 52: Call Process denial events (1225 - 1899) 24 of 36
Event
Type
Event Description, as it
appears on the event log
Explanation
1616
Ctrl rstrct featid bad
Initial processing supervision for controlled
restriction. Might be featid is not one of:
● activate user control restriction
● deactivate user control restriction
● activate group control restriction
● deactivate group control restriction
1617
Dialing tmo/invalid digit
Supervisor for Logical Agents is logging in by
dialing LoginID digits, dialing timeout occurs or
an invalid digit is dialed.
1618
Paging timeout
Loudspeaker paging seizure supervision. Might
be a paging timeout.
1619
LWC access cod dgt invld
Supervision for Leave Word Calling access code.
Processing invalid digit dialed.
1620
LWC access code rejected
Supervision for Leave Word Calling access code.
Processing msg_sv rejects code.
1621
Software invalid stim
Invalid Call Processing (CP) message stimulus’d
to Malicious Call Trace supervisor.
1622
BCC selection digit invld
Supervision for multimedia parameter selection.
Invalid digit dialed for selecting bearer capability
for call.
1623
MM parm select failure
Supervision for multimedia parameter selection.
error returned from gm_ftr_act().
1624
Backward tone absent tmo
Trunk outpulsing supervision. Outgoing backward
tone absent timeout on MultiFrequency
Compelled digit sending.
1625
7 min tmo - no tone rcvd
Trunk outpulsing supervision. No tone has been
detected within 7 minutes after dialing Trunk
Access Code of a Cut Through Central Office
(CO) or Foreign Exchange (FX) trunk.
1626
MFC trk seize failure
Trunk seizure supervision on outgoing trunks.
MultiFrequency Compelled trunk seizure failure.
1627
Out trk seize dgt invld
Trunk seizure supervision on outgoing trunks.
1628
7 min tmo - no tone rcvd
Trunk seizure supervision on outgoing trunks. No
tone has been detected within 7 minutes after
dialing Trunk Access Code of a Cut Through
Central Office (CO) or Foreign Exchange (FX)
trunk.
1629
7 min tmo - no tone rcvd
Supervision when there is a tone detector on the
call, a wait timer has been set for a VOICE user,
or a data call over a trunk is waiting for a Stall
Answer feedback to DEXT. No tone has been
detected within 7 minutes after dialing the Trunk
Access Code of a Cut Through Central Office
(CO) or Foreign Exchange (FX) trunk.
1630
Onhk que spvsn invld dg
Queued call or anticipated manually queued call
sees CP_INVDGT from somewhere.
Event
Data 1
Event Data 2
24 of 36
230 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Denial Event Tables
Table 52: Call Process denial events (1225 - 1899) 25 of 36
Event
Type
Event Description, as it
appears on the event log
Explanation
Event
Data 1
1631
Rmt ACB ftr act timeout
Queued call or anticipated manually queued call
sees timeout waiting for remote drop by activator
of Automatic Call Back feature.
1632
PASTE enbl/rstrct/usrtyp
Possible causes:
● PC Application Software Exchange
(PASTE) not enabled
● attendant use of PASTE is not allowed.
station
● Class of Restriction (COR) does not
allow PASTE
● totally restricted station cannot use
PASTE
● station has no display
● bridge appearance cannot use PASTE
● agent not in AUX cannot use PASTE
● (su_ok4paste()) COR restricted for
PASTE
1633
Digit tmo/list nbr invld
Inter-digit timeout or invalid list number entered
during PC Application Software Exchange
(PASTE) display list number collection.
1634
Software invalid stim
Supervision after position busy (de)activation dial
access code has been recognized. Collecting
more digits. Invalid Call Processing (CP) stimulus
type sent to this supervisor.
1635
Extension type qry fail
Refresh Terminal Parameters supervision. The
query to get the extension type failed.
1636
Not a downloadable set
Refresh Terminal Parameters supervision. Port
type is not a valid downloadable station port type.
Only 8400/6400/4600/603 type stations and the
302 type attendant consoles are allowed.
1637
Wrt prot/maxd/annc bd
Supervision for announcement record/playback
session processing. Integrated announcement
session instruction message sent to GRP_M.
Possible causes:
● announcement is write/delete protected
● invalid feat_type or not the same Caller
ID that is in the session
● CM port connection failure
● invalid Caller ID root (au_sbegin())
● CM port disconnect failure
● CM port listen failure
● no announcement board
● maximum number of announcements
already recorded
1638
Record playback reject
Supervision for announcement record/playback
session processing. CP_REJECT stimulus
received from somewhere.
1639
Permanent seizure
Standard action stimulus processing. Non-Direct
Inward Dialing trunk origination. Digit timeout with
no digits dialed. The permanent incoming seizure
treatment is to give intercept.
Event Data 2
25 of 36
Issue 3 February 2007
231
Denial Events
Table 52: Call Process denial events (1225 - 1899) 26 of 36
Event
Type
Event Description, as it
appears on the event log
Explanation
1640
Permanent seizure
Standard action stimulus processing. Italian
external tie (TGU) call. Digit timeout with no digits
dialed. The permanent incoming seizure
treatment is to give intercept.
1641
Permanent seizure
Standard action stimulus processing. Trunk group
type other than: DID, IN_TIE, EX_TIE, TAN_TIE,
ACCESS, IN_APLT,EX_APLT, ISDN_PRI, or
DIOD. Digit timeout with no digits dialed. The
permanent incoming seizure treatment is to give
intercept.
1642
Ofhk alrt tmo intvl admin
Standard action stimulus processing. Station,
attendant or analog adjunct data extension
originator. Off-hook alert feature activation. No
off-hook alert timeout interval administered.
(OHK_ALERT)
1643
Off-hook dialing time out
Standard action stimulus processing. originator
group type not trunk, DEXT, SMPL(station), or
attendant? DEXT, SMPL, attendant does not
Class of Service allow off-hook alert, processing
a CP_DG_TMO for Line Intercept Tone timer.
1644
Orig block/invalid digits
Standard action stimulus processing. originator
group type not trunk, DEXT, SMPL(station), or
attendant? DEXT, SMPL, ATTD does not Class of
Service allow off-hook alert and NOT processing
a CP_DG_TMO for Line Intercept Tone timer.
1645
Talk state MFC trk fail
MultiFrequency Compelled trunk failure after the
call is the talking state. (CP_MFCINTRCPT)
1646
No act call_ap/sftw err
One-button transfer to data feature activation
failed. Possible causes:
● No active call appearance
● Call id passed from call_p to su_obt() is
not on the active call appearance
1647
Telcomtr diald illegl FAC
Supervisor for telecommuting access.
Telecommuting extension was accessed, then a
Feature Access Code was dialed that is not
allowed to telecommute.
1648
Ctrl rstrct VDN extension
Supervision for controlled restriction of user.
Control Restriction Activation/Deactivation for a
Vector Directory Number extension is not
allowed.
1649
Ctrl rstrct locl ext only
Supervision for controlled restriction of user.
Control Restriction Activation/ Deactivation must
be on an extension that is local to the switch.
Event
Data 1
Event Data 2
26 of 36
232 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Denial Event Tables
Table 52: Call Process denial events (1225 - 1899) 27 of 36
Event
Type
Event Description, as it
appears on the event log
Explanation
Event
Data 1
1650
Rstrct typ/featid/COR/sta
Supervision for controlled restriction of user.
Possible causes:
● Originator’s User ID not found in
DP_MGR User ID data tables
● Restriction digit does not identify with
outward, total, termination or
station-to-station type restriction
● Featid is not one of:
- activate user control restriction
- deactivate user control restriction
- activate group control restriction
- deactivate group control restriction
● Class of Restriction (COR) restricted
● Controlled restriction not allowed on
trunk or attendant group type.
1651
TTI merge/unmerge fail
Station server could not perform Terminal
Translation Initiation (TTI) merge/unmerge.
1652
LWC access cod dgt invld
Voice synthesis Leave Word Calling access code
digit processing saw an invalid digit or msg_sv,
rejected the request.
1653
TTI - attd not allowed
Terminal Translation Initiation (TTI) unmerge
operation is not allowed from attendants.
1654
TTI - attd not allowed
Personal Station Access (PSA) associate
operation cannot be originated by attendant.
1655
TTI - BRI not allowed
Personal Station Access (PSA) associate
operation cannot be originated by BRI station.
1656
Other calls active/COS
Personal Station Access (PSA) associate
operation. If not on a Terminal Translation
Initiation (TTI) port, check the Class of Service.
Deny if possible. Also check for other calls active
on the station.
1657
TTI - attd not allowed
Personal Station Access (PSA) disassociate
operation cannot be originated by attendant.
1658
TTI - BRI not allowed
Cannot Personal Station Access (PSA)
disassociate a BRI station.
1659
TTI - COS restricted
Class of Service does not allow Personal Station
Access (PSA) disassociate operation.
1660
TTI - BRI not allowed
Cannot Personal Station Access (PSA) associate
a BRI station.
1661
TTI - COS restricted
Class of Service of the extension to be
associated does not have Personal Station
Access (PSA) capability.
1662
Crossing tenant partition
Personal Station Access (PSA) associate
operation cannot cross tenant partitions.
1663
Invalid user ID/sftw err
Personal Station Access (PSA) associate
operation. There is no extension associated with
user ID. Invalid User ID or software error.
Event Data 2
1
27 of 36
Issue 3 February 2007
233
Denial Events
Table 52: Call Process denial events (1225 - 1899) 28 of 36
Event
Type
Event Description, as it
appears on the event log
Explanation
1664
Getting user ID failed
Failure getting the User ID for the extension
dialed in an association/ dissociation step.
1665
Data mod usr id qry fail
Data Terminal Translation Initiation (TTI) call. The
query for the real User ID of data module in dext
group failed.
1666
Originator ext not dialed
Unmerge sequence initiated, and the extension
dialed must be the same as the originator’s.
1667
Non trunk intercept
Proper intercept treatment for non DID/TIE/ISDN
trunk groups, or non-trunk originators.
1668
Trk needs disc supervisn
Activate service observing feature. Service
observing cannot be activated by a trunk without
disconnect supervision.
1669
Svc obsrv from attd NA
Activate service observing feature. Service
observing cannot be activated by an attendant.
1670
Svc obsrv from brdg NA
Activate service observing feature.Service
observing cannot be activated from a bridged
appearance.
1671
Svc obsrvg svc obsrvd NA
Activate service observing feature.Service
observing cannot be activated by a user that is
already a service observer or is being service
observed.
1672
Svc obsrvr/obsrvd COR dny
Activate service observing feature. Activating
user’s Class of Restriction (COR) does not allow
it to be a service observer of intended observed.
1673
Svc obsrvr COR rstrct
Activate service observing feature. Activator’s
Class of Restriction (COR) check failed.
1674
Svc obsrvr/obsrvd COR dny
Activate service observing feature. Activating
user’s Class of Restriction (COR) does not allow
it to be a service observer of intended observed.
1675
Svc obsrvr vecstep/extdgt
Activate service observing feature. Initiated from
a vector step and only the Feature Access Code
of service observing is in the vector step.
End-to-end signaling digit collection of extension
to be observed failed.
1676
Svc obsrv not on ext/VDN
Validation of service observed extension. Service
observing is allowed only on a simple User ID or
a Vector Directory Number.
1677
Svc obsrv cust opt qry
Validation of service observed extension. Query
for service observing customer-options failed.
1678
Need VDN obsrvg option
Validation of service observed extension. Vector
Directory Number observing is not enabled.
1679
Svc obsrvee data rstrctd
Validation of service observed extension.
Observee is data restricted.
1680
Svc obsrvg svc obsrvd
Validation of service observed extension.
Non-Vector Directory Number observee is
already being observed, or is an observer.
Event
Data 1
Event Data 2
28 of 36
234 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Denial Event Tables
Table 52: Call Process denial events (1225 - 1899) 29 of 36
Event
Type
Event Description, as it
appears on the event log
Explanation
Event
Data 1
1681
Svc obsrvee COR rstricted
Validation of service observed extension. Class
of Restriction (COR) of observee does not allow
being observed.
1682
Svc obsrvd COR chk fail
Validation of service observed extension. Class
of Restriction (COR) check failure.
1683
Svc obsrvr/obsrvd COR dny
Validation of service observed extension.
Observer/observee Class of Restrictions do not
allow observer to observe observee.
1684
Svc obsrvg/obsrvg race
Validation of service observed extension. The
observee is already in the process of activating
service observing for another party.
1685
Svc obsrv ftr act failure
Validation of service observed extension. Feature
activation of selected “listen only” or “listen/talk”
service observing failed.
1686
Svc obsrv VDN SO wait flg
Supervision after confirmation tone to a service
observer. DPM failure to set Vector Directory
Number (VDN) Service Observing wait flag in the
VDN’s VDN information block.
1687
Obsrvr conf_state unclear
Supervision after confirmation tone to a service
observer. Confirmation tone is complete for an
observer. Make observer eligible to be taken off
the wait list for the Vector Directory Number.
Failure to clear the “conf_state” for the observer.
1688
Svc obsrvg/obsrvg race
Supervision after confirmation tone to a service
observer. Bridging observer onto the agent
encountered race condition, observee is already
in the process of activating service observing for
another party.
1689
Svc obsrv ftr act fail
Supervision after confirmation tone to a service
observer. Failure activating service observing for
observee.
1690
Software invalid stim
Supervision after confirmation tone to a service
observer. Invalid Call Processing (CP) stimulus
received by this supervisor.
1691
Term restriction chk fail
Processing incoming Call Forwarding. All
Distributed Communication System (DCS)
message. Other switch had problem processing
CF_ACT message. Termination restriction check
failed or could not convert designated extension
to a user ID.
Event Data 2
29 of 36
Issue 3 February 2007
235
Denial Events
Table 52: Call Process denial events (1225 - 1899) 30 of 36
Event
Type
Event Description, as it
appears on the event log
Explanation
1692
LWCpmsn/UDPext/dpst
admin
Leave Word Calling (LWC) operations generates
INT_DRP. Possible causes:
● attendant cannot leave DCS messages
because of eDIM, S85
● lw_nocall() activator of lwc store does
not have lwc permission
● activator is not a udp ext
● lwc_store() lw_rmstore()- DCS LWC - no
remote users involved
● lwc store operation remote to localVoice Mail Applications Support is
disabled
● called party not administered to receive
LWC messages
● no called party message header
● no LWC depository administered
● error in sending AUDIX STORE
message info (from remote user) to AAP
1693
Out trk DID orig/sftw err
Italian Direct Inward Dial (DID) trunk group drop
treatment. Possible causes:
● DID origination on outgoing trunk
● Invalid return code from gm_orig()?
● Software error?
1694
Sta intrcpt tone fwd disc
Station Intercept Tone Forward Disconnect.
1695
Bsy vfy sta/trk/hnt grp
Cannot busy verify attendants.
1696
Bsy vfy trk grp no mbr
Busy verify of trunk failure. Possible causes:
● No trunk in the group
● Trunk group member not found
1697
Bsy vfy access endpt trk
Busy verification not supported for access
endpoint trunk type.
1698
Bsy vfy hnt grp no mbr
Busy verify of hunt group failure. Might be there is
no member in the hunt group.
1699
LWC msg stor fail (conf)
Leave Word Calling message cannot be stored
when there is a conference call.
1700
LWC msg - no destination
No destination determined for Leave Word
Calling message store.
1701
Whisp pg not to station
Whisper page allowed only to simple station
group type of user.
1702
Whisp pg query fail
Whisper paging - shouldn’t see this - sim_quer/
su_query don’t develop GQRY_INVALID
response to qtype QWHISP_PG
1703
Whisp pg query fail
Whisper paging - shouldn’t see this - sim_quer/
su_query don’t develop GQRY_AE response to
qtype QWHISP_PG
1704
Whisp pg usr not allowed
Whisper paging. User is not allowed to make
whisper pages.
1705
Whisp pg query fail
Whisper paging. QWHISP_PG type gm_query
failed.
Event
Data 1
Event Data 2
30 of 36
236 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Denial Event Tables
Table 52: Call Process denial events (1225 - 1899) 31 of 36
Event
Type
Event Description, as it
appears on the event log
Explanation
1706
Wake up typ/voice actvat
VIP and DAILY type wakeup cannot be modified
or deleted via voice-activated process.
1707
No attd to rcv wakeup
Voice synthesizer is not available. Routing
automatic wakeup call to attendant, but no
attendant. (TN725).
1708
No attd to rcv wakeup
Voice synthesizer not available. Routing
automatic wakeup call to attendant, but no
attendant. (TN725).
1709
Bsy vfy term is PCOL
Busy verify is denied, the principal terminator is
Personal Central Office Line (PCOL).
1710
Bsy vfy is term rstrctd
Busy verify is termination restricted.
1711
Bsy vfy dgt invalid/tmo
While collecting digits for busy verification,
supervisor got an indication of invalid digit or digit
timeout.
1712
Ofhk alrt tmo intvl admin
Standard action stimulus processing. Station,
attendant, or analog adjunct data extension
originated off-hook alert feature activation, but no
off-hook alert timeout interval is administered.
1713
Bsy vfy dgt invalid/tmo
While collecting trunk member number digits for
busy verification, supervisor got an indication of
invalid digit or digit timeout.
1714
Whisp pg term is PCOL
Whisper page feature activated, principal
terminator is Personal Central Office Line
(PCOL).
1715
Whisp pg is term rstrctd
Whisper page feature activated, whisper page is
termination restricted.
1716
Software invalid stim
Whisper page feature activated, whisper page
supervisor saw an invalid Call Processing (CP)
stimulus while collecting station digits.
1717
Self Sta Display denial
Self Station Disp feature activated, either
activated from a bridged appearance or GRP_M
denial.
1718
Grp call pkup not enabled
Group Call pickup is not enabled.
1719
Invalid dgts collected
Invalid digits are collected in dgt_egpkup().
1720
QSIG VM-no simple uid
Could not obtain simple user User ID for an SS-B
ISDN trunk.
1721
QSIG VM-no remote user id
Received a Voicemail Number MSI but did not
receive an original diverting number.
1722
QSIG VM-prin not smpl uid
The local principal User ID is not a simple user
User ID.
1723
QSIG VM-no voicemail nbr
Do not know the number of the voicemail adjunct,
the call cannot transfer to the adjunct.
1724
Annc Record Session Fail
Announcement record session was denied by the
board.
Event
Data 1
Event Data 2
UID
board’s reason
for denial.
31 of 36
Issue 3 February 2007
237
Denial Events
Table 52: Call Process denial events (1225 - 1899) 32 of 36
Event
Type
Event Description, as it
appears on the event log
Explanation
1725
QSIG VM-hunt not in cvg p
Principal does not have a QSIG MWI (Message
Waiting Indicator) hunt group in its coverage
path.
1726
Cant get Smpl Attd-uid
Cannot get simple attendant User ID.
1727
cannot use PASTE
Station restriction is total, cannot use PC
Application Software Exchange (PASTE).
1728
Deny PE originated calls
PE already active on call.
1729
Direct Agent call failed
Direct Agent Call failed.
1730
Trk-grp uid retrieve fail
All failed to retrieve Release Link Trunk (RLT)
trunk group User ID for Centralized Attendant
Service (CAS).
1731
I/C call on O/G Trunk
Incoming call on outgoing trunk.
1732
Caller COR Restricted
Caller Class of Restriction (COR) restricted
access.
1733
Conference 2 Attendants
Cannot conference 2 attendants.
1734
Max Pub Net Trks on conf
Maximum number of Public Network Trunks on
conference.
1735
Max conf parties w/PNTrks
Maximum number of conference parties with
Public Network Trunks.
1736
Max conf parties wo/PNTrk
Maximum number of conference parties without
Public Network Trunks.
1737
Max conf/xfer parties
Maximum number of conference or transfer
parties.
1738
Conf/xfer unstable calls
Cannot conference or transfer unstable calls.
1739
Div Reroute/Path Replace
Cannot transfer Diversion Rerouting or Path
Replacement call.
1740
No Disconnect Supervision
Cannot transfer, no disconnect control party.
1741
Transfer trunk to trunk
Cannot transfer trunk to trunk.
1742
Conf/xfer Whisper Page
Cannot conference or transfer whisper page.
1743
cnf/xfr Emergency/Wakeup
Cannot conference or transfer emergency or
wakeup call.
1744
Conf/xfer a tone
Cannot conference or transfer tone.
1745
Conf/xfer Announcements
Cannot conference or transfer with multiple
announcements.
1746
Conf/xfer a Vector call
Cannot conference or transfer vector call.
1747
Cnf/xfr Service Observers
Cannot conference or transfer two service
observers.
Event
Data 1
Event Data 2
32 of 36
238 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Denial Event Tables
Table 52: Call Process denial events (1225 - 1899) 33 of 36
Event
Type
Event Description, as it
appears on the event log
Explanation
Event
Data 1
1748
Conf/xfer a Page call
Cannot conference or transfer group or
loudspeaker page call.
1749
No Disconnect Supervision
Cannot route call, no disconnect control party.
1750
FRL too low to route call
Cannot route the call, Facility Restriction Level is
too low.
1751
No AAR/ARS route pat/pref
No route pattern or preference translated.
1752
Conf with no ISDN connect
Conference when ISDN connect message has
not been sent due to SA8434.
1753
Caller cvgpt COR restrict
Remote/caller cannot terminate to coverage point
due to Class of Restriction (COR) setting.
1754
Caller cvgpt COR restrict
Remote/caller cannot terminate to coverage point
due to Class of Restriction (COR) setting.
1755
Caller cvgpt COR restrict
Remote caller cannot terminate to coverage point
due to Class of Restriction (COR) setting.
1756
Caller fwdto COR restrict
Remote/caller cannot terminate forwarded to
party, Class of Restriction (COR) setting.
1757
Attd release COR restrict
Attendant cannot release call, Class of
Restriction (COR) setting.
1758
Attd release link failure
Attendant cannot release call, link restriction.
1759
Attd hold COR restrict
Attendant cannot release call, Class of
Restriction (COR) setting.
1760
Conference COR restrict
Controller cannot conference call, Class of
Restriction (COR) setting.
1761
Transfer COR restrict
Controller cannot transfer call, Class of
Restriction (COR) setting.
1762
Transfer no pooled modem
Controller cannot transfer call, no pooled modem.
1763
Cnf/xfr Intercept Anncmt
Attempt to transfer/conference an intercept
announcement.
1764
Btn Ring Control timeout
Button ring control activated via Feature Access
Code & time out has occurred. SA8428
1765
Invalid button pushed
Invalid button pushed in button ring control mode.
SA8428
1766
Remote Logout Agent fail
no info available
1767
Rmt Logout COR restricted
no info available
1768
Rmt Logout COS restricted
no info available
1769
Rmt Logout invalid input
no info available
1770
Rmt Logout tenant number
no info available
Event Data 2
fail code
33 of 36
Issue 3 February 2007
239
Denial Events
Table 52: Call Process denial events (1225 - 1899) 34 of 36
Event
Type
Event Description, as it
appears on the event log
Explanation
Event
Data 1
Event Data 2
1771
Rmt Logout cant do self
no info available
1772
PSA on Virt EXT disallow
Personal Station Access (PSA) associate/
disassociate not allowed for virtual extension.
1773
Cnf/xfr Atd Intcpt Ann
Attempt to transfer an intercept announcement at
the attendant.
1774
Stn Lock act/deact failed
Station lock activation or deactivation failed.
1775
No adm for SBS extensions
Separation of Bearer and Signaling (SBS) call
tried to allocate an SBS extension, but none was
administered.
1776
Can't send SBS # to orig
Separation of Bearer and Signaling (SBS) call
tried to send back an INFO message with the
SBS complete public number, but the INFO could
not be sent. Check proper administration of
isdn-pub-unk form.
1777
Calling Pty COR chk fail
Error occurred when retrieving Class of
Restriction (COR) of calling party.
1778
Orig COR/Auth COR dny
Calling party Class of Restriction (COR) not
allowed to use mapped COR from authorization
code entry.
1779
FIPN RO when call on hold
Fujitsu Intelligent Priva Network (FIPN -a Fujitsu
ISDN Protocol spec) route optimization denial.
There is call on hold. SA8506
1780
AAR/ARS fac not
administered
ARS/ARR Feature Access Code is not
administered.
1781
Note: Error codes 1781 through 1791 apply to Feature Access Code invocations that are designed to operate on
contact closure relays on a G350 Media Gateway. These error codes apply only to Linux-based servers.
17811
CC: Improper COS
ARS/ARR Feature Access Code is not
administered.
17821
CC: Invalid digits
Invalid digits (or a symbol for a digit, etc.) entered
for contact-closure related operation on a G350
Media Gateway.
17831
CC: MG# out of range
Media gateway number is out-of-range.
17841
CC: software error
Contact-closure related operation had internal
software error, should never happen. First byte of
the seconds data item gives info to ID where
error occurred out of many places that it can
happen.
17851
CC: Invalid closure#
Contact-closure related operation had bad
closure number.
17861
CC: MG not administered
Contact-closure related operation had
unadministered media gateway number.
17871
CC: MG not registered
An unregistered media gateway was selected for
a contact-relay related operation on a G350
Media Gateway.
34 of 36
240 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Denial Event Tables
Table 52: Call Process denial events (1225 - 1899) 35 of 36
Event
Type
Event Description, as it
appears on the event log
Explanation
17881
CC: MG in link recovery
The G350 Media Gateway selected for a
contact-relay related operation was in link
recovery mode.
17891
CC: No CC on this MG type
The media gateway selected for a contact-relay
related operation does not have a contact relay.
17891
CC: MG not a G350 gateway
The media gateway selected for a contact-relay
related operation is not a G350.
17901
CC: Invalid button push
An invalid feature button was pushed after
invoking contact closure feature.
17911
CC: Trunk usr not allowed
Trunk access is not allowed for contact closure
feature.
1792
MI Chg Fail: Agt Burnout
Deny change to manual-in mode because the
agent is in burnout state.
1793
AI Chg Fail: Agt Burnout
Deny change to auto-in mode because the agent
is in burnout state.
1794
No STNHNT for Remote cvg
Deny station hunt after coverage if the last
coverage party is remote.
1795
(not used in
Caller FEAC restricted
Caller FEAC restricted access.
1796
Caller TOLL restricted
Caller TOLL restricted access.
1797
TTI Outcall Needs PSA COR
Terminal Translation Initiation (TTI) Caller has
AAR/ARS network restricted access.
1798
No TTI merge to AAR/UDP
No Terminal Translation Initiation (TTI) merge is
allowed to an AAR/UDP network.
1799
Annc in Audio Grp
Deny recording or deleting the announcement if it
is part of an audio group.
1800
Parties Tenant restrict
Tenant is restricted.
1801
Public Trunk restrict
Public trunk is restricted.
1802
Parties COR restrict
Parties’ COR is restricted.
1803
Origination restrict
Origination is restricted.
1804
Manual Line restrict
Manual line is restricted.
1805
Inward restrict
Inward is restricted.
1806
Termination restrict
Termination is restricted.
1807
Outward restrict
Outward is restricted.
Communication
Manager Re-
Event
Data 1
Event Data 2
lease 2.2
Communication
Manager
Release
3.0
35 of 36
Issue 3 February 2007
241
Denial Events
Table 52: Call Process denial events (1225 - 1899) 36 of 36
Event
Type
Event Description, as it
appears on the event log
Explanation
1808
Conf hold restrict
Conference hold is not allowed during digit
collection.
1809
Rej CFU act ECF active
Reject the activation of CFU because ENHCF
(unconditional) is already activated.
1810
Rej CFBDA act ECF active
Reject the activation of CFBDA because ENHCF
(busy or no reply) is already activated.
18111899
not assigned
Event
Data 1
Event Data 2
36 of 36
1. Error codes 1781 through 1791 apply to Feature Access Code invocations that are designed to operate on
contact closure relays on a G350 Media Gateway. These error codes apply only to Linux-based servers.
User Manager Events
Event Types 1900 - 1906 show User Manager-generated denial events, as listed in User
Manager denial events (1900 - 1906) on page 242.
Table 53: User Manager denial events (1900 - 1906)
Event
Type
Event Description, as it
appears on the event log
Explanation
1900
Invalid CFWD destination
CF_DEST digits do not map to station User ID.
1901
Control Restrn Check fail
Control Restriction.
1902
Enhanced Abbr List Failur
Enhanced Abbreviated Dialing entry length failed.
1903
LWC Button xln Error
Ignore Leave Word Calling button push due to bad translation.
1904
Override for the PGN disa
User not allowed to activate override for this partition
1905
Auto selection of DID dis
Automatic selection of Direct Inward Dialing numbers is disabled.
1906
SA8428 Btn Ring Ctl disab
SA8428 Station User Button Ring Control has been disabled,
ignore button-ring button push.
Event
Data 1
242 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Event
Data 2
Denial Event Tables
IP Denial Events
Event Types 1907 - 2079 show IP denial events, as listed in IP Denial Events (1907 - 2020) on
page 243 and Table 55, Call Process denial events (2021 - 2299), on page 254.
Table 54: IP Denial Events (1907 - 2020) 1 of 12
Event
Type
Event Description, as it
appears on the event log
Explanation
Event Data 1
Event Data 2
1907
IP RRJ-Invalid RAS addr
IP Registration Rejected because the
RAS address in the registration request
(RRQ) is invalid.
0
IP address of
the endpoint
1908
IP RRJ-Invld call SigAddr
IP Registration Rejection because the call
signaling address in the registration
request (RRQ) is invalid.
0
IP address of
the endpoint
1909
IP RRJ-RemoteOfc
misadmin
Registration rejected because:
0
IP address of
the endpoint
● Remote Office is enabled on the
Signaling Group screen, but the
registration request (RRQ) is not
from a supported Remote Office
product (the Remote MAX
Product/Vendor ID is invalid).
● The RRQ is from a supported
Remote Office product, but
Remote Office is not enabled on
the Signaling Group screen.
● Remote Office is enabled on the
Signaling Group screen, but the
Terminal Type in the RRQ is not
valid (the Terminal Type is not a
gateway).
1910
IP RRJ-H323 UserObj undef
IP Registration rejected because there is
no H323 User Object.
0
IP address of
the endpoint
1911
IP RRJ-Exceed max endpts
IP Registration rejected because the
capacity for either registered endpoints,
registered Remote Office endpoints, or
registered un-authenticating endpoints is
exceeded. Check maximum allowed in
the system on page 1 of the System
Parameters Customer Options screen.
0
Upper part:
number of
registered RO
endpoints.
Lower part:
number of
registered IP
endpoints.
1912
IP RRJ-Exceed ProdID/Ver
IP Registration rejected because the
maximum number of registered endpoints
of a specific product ID and version is
exceeded. Check the limit on the
System-Parameters Customer-Options
screen.
Truncated
Product ID from
the SystemParameters
CustomerOptions screen
Upper part:
registered limit.
Lower part:
actual count.
1 of 12
Issue 3 February 2007
243
Denial Events
Table 54: IP Denial Events (1907 - 2020) 2 of 12
Event
Type
Event Description, as it
appears on the event log
Explanation
Event Data 1
Event Data 2
1913
IP RRJ-Invalid ProdID/Ver
IP Registration rejected because of an
invalid Product ID / Version. Registering
Application's product ID is not
administered on the System-Parameters
Customer-Options screen or no Product
ID in registration request (RRQ)
message.
Truncated
Product ID of the
registering
application
Major version
number of the
endpoint sent in
the RRQ
1914
IP RRJ-ProdID search fail
IP Registration rejected because the
search for the registering application's
Product ID failed.
Truncated
Product ID of the
registering
application
Major version
number of the
endpoint sent in
the RRQ
1915
IP RRJ-Invalid endpt/Ver
Registration rejected because the
endpoint version is not compatible with
the gatekeeper version.
IP address of
endpoint
Endpoint’s
major version
number in 2nd
byte, minor
version number
in low byte
1916
IP RRJ-No H323
NonStdData
Registration rejected because
Non-standard Data (NSD) is missing in
the registration request (RRQ) from the
endpoint.
0
IP address of
the endpoint
1917
IP RRJ-Invld H323 ObjID
Registration rejected because the H323
Object ID in the registration request
(RRQ) is invalid.
Object ID in
RRQ
IP address of
the endpoint
1918
IP RRJ-Invld H225 NSData
Registration rejected because cannot
decode H225 Non-standard Data (NSD)
message.
0
IP address of
the endpoint
1919
IP RRJ-Bad H225
NSDchoice
Registration rejected because an
unexpected Non-standard Data (NSD)
message was received from the
registering application.
NSD choice in
RRQ
IP address of
the endpoint
1920
IP GRJ-RRJ: new LM fail
Registration rejected because of failure in
creating a new Login Manager. Possible
causes are:
UID
IP address of
the endpoint
● No available heap memory to
create LoginMgr
● Cannot start LoginMgr timer
● Clock not set
1921
IP RRJ-IP-TTI port fail
Registration rejected because of failure
when inserting the IP Terminal
Translation Initiation (TTI) port.
UID
IP address of
the endpoint
1922
IP RRJ-TTI inactive
Registration rejected for an IP set with
Terminal Translation Initiation (TTI)
service. Possible causes:
0
IP address
Communication
Manager
Release
2.1 and
earlier
● TTI is not enabled on the
System Parameters Customer
Options screen.
● Remote Office is not enabled on
the System Parameters Feature
Options screen.
2 of 12
244 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Denial Event Tables
Table 54: IP Denial Events (1907 - 2020) 3 of 12
Event
Type
Event Description, as it
appears on the event log
Explanation
Event Data 1
Event Data 2
1922
IP RRJ-TTI or RO inactive
Registration rejected for an IP set with
Terminal Translation Initiation (TTI)
service. Possible causes:
0
IP address
Communication
Manager
● TTI is not enabled on the
Release
2.2
System-Parameters
Customer-Options screen.
● Remote Office is not enabled on
the Feature Related
System-Parameters screen.
IP RRJ-TTI or RO inactive
Registration rejected for an IP set with
Terminal Translation Initiation (TTI)
service. Possible cause is TTI is not
enabled on the System-Parameters
Customer-Options screen.
IP address of the
endpoint
TTI state where:
0=TTI off
2=TTI on for
voice
3=TTI on for
data
1923
IP RRJ-No E164 number
Registration rejected because there is no
valid E.164 number in the RRQ or the
extension is not administered.
UID
IP address of
the endpoint
1924
IP RRJ-No GRQ msg rcvd
Registration rejected because no
Gatekeeper Request message was
received or RRQ was received more than
15 seconds after GRQ
UID
IP address of
the endpoint
1925
IGAR trunk routing failed
Registration rejected, denied while
routing an outgoing Inter-Gateway
Alternate Routing (IGAR) trunk call,
because of failure creating a new Login
Manager. Possible cause:
UID
IP address
1922
Communication
Manager
Release
3.0
● No available heap memory to
create LoginMgr
● Cannot start LoginMgr timer
● Clock not set
1926
IP RRJ-Authenticatn fail
Registration rejected because of
password authentication/ encryption
failure. The password that the user
entered and the administered password
on the station screen do not match or no
cryptoToken or keys sent in RRQ.
UID
IP address of
the endpoint
1927
IP RRJ-Invld station type
Registration rejected because of:
UID
station type or
IP address of
the endpoint
Communication
Manager
Release
2.2 and
earlier
● Invalid station type
● No Remote Office or IP
Softphone administration on the
station screen
● IP Softphone tried to register
shared-control to the wrong
telephone endpoint type.
3 of 12
Issue 3 February 2007
245
Denial Events
Table 54: IP Denial Events (1907 - 2020) 4 of 12
Event
Type
Event Description, as it
appears on the event log
Explanation
Event Data 1
Event Data 2
1927
IP RRJ-Invld station type
Registration rejected because of:
UID
station type or
IP address of
the endpoint
UID
Endpoint type
(3rd and 2nd
nyble); call
signaling
protocol (low
nyble)
Communication
Manager
● Invalid station type for the
endpoint application
Release
3.0
● R1 IP telephone
● R1 or R2 IP softphone in
roadWarrior or Telecommuter
mode
● IP console and not console
station type
● IP softphone and softphone not
set to yes on station screen
● IP telephone application and not
IP telephone station type
● Softphone that cannot operate
with a station type that does not
have a BIS or the speaker is
turned off
1928
IP RRJ-StnTyp/Protocl err
Registration rejected because station
type and call-signaling protocol are
inconsistent. An IP Softphone should be
assigned as one of the following:
● DCP extension, with call control
set to IP Softphone
● H.323 extension, with call
control set to none
1929
IP RRJ-No idx for MMCmplx
Registration rejected: user record for
dual-connected DCP set is missing the
index for the multimedia complex.
UID
IP address of
the endpoint
1930
IP RRJ-No voice path spec
Registration rejected because the
endpoint (the virtual phone) has neither
an associated multimedia extension nor a
specified voice path, so no audio path
exists. Either:
UID
IP address of
the endpoint
UID
IP address of
the endpoint
Communication
Manager
Release
2.2 and
earlier
● Add a Media Complex extension
on the station screen
or
● Add an extension on the
softphone (register as a
telecommuter)
1930
Communication
Manager
Release
3.0 and
later
IP RRJ-No voice path spec
Registration rejected because the
endpoint (the virtual phone) has neither a
specified voice path for telecommuter
mode or is itself audio capable, so no
audio path exists.
● Add an extension on the
softphone (register as a
telecommuter)
4 of 12
246 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Denial Event Tables
Table 54: IP Denial Events (1907 - 2020) 5 of 12
Event
Type
Event Description, as it
appears on the event log
Explanation
Event Data 1
Event Data 2
1931
IP RRJ-H323 ext is
MMCmpx
Registration rejected because this H.323
extension is administered as a Media
Complex extension on a non-H.323 (for
example, a DCP) set.
UID
IP address of
the endpoint
1932
IP RRJ-Ext has data modl
Registration rejected because the
extension has a data module.
UID
IP address of
the endpoint
1933
IP RRJ-IP addr mismatch
Registration rejected because the H.323
application is not at the same IP address
as the authenticating application.
UID
IP address of
registering
endpoint
1934
IP RRJ-Ext already reg
Registration rejected because the
extension is already registered.
UID
IP address of
the endpoint
1935
IP RRJ-Not Remote Ofc ext
Registration rejected because Remote
Office is not administered on the station
screen for this extension.
UID
IP address of
the endpoint
1936
IP RRJ-RO stn mismatch
Registration rejected because of invalid
analog station type.
UID
IP address of
the endpoint
IP RRJ-RO stn mismatch
Registration of Remote Office endpoint
rejected because set type on Remote
Office differs from set type on station
screen.
UID
IP address of
the endpoint
1937
IP RRJ-RemOfc not admin
Registration rejected because the
Remote Office is not administered on the
remote-office form
UID
IP address of
the endpoint
1938
IP RRJ-Immediate re-reg
Immediate re-registration is rejected
when a registration or unregistration is in
progress for the extension.
UID
IP address of
the endpoint
1939
IP RRJ-Failure moving ext
Registration rejected because of failure
while trying to force the unregistration of
an extension in the process of moving it
to another port.
UID
IP address of
the endpoint
1940
IP RRJ-Duplicate ext
Registration rejected as a duplicate
extension.
UID
IP address of
the endpoint
1941
IP KA-from invld endpt ID
Keep Alive registration request rejected
because of invalid endpoint identifier in
RRQ.
UID
IP address of
the endpoint
1942
IP KA-from unreg user
Keep Alive registration request rejected
because it was received from an
unregistered extension.
UID
IP address of
the endpoint
1943
IP-KA-from unreg SigGrp
Keep Alive registration request rejected
because it was received from an
unregistered signaling group.
UID
IP address of
the far-end
Communication
Manager
Release
2.2 and
earlier
1936
Communication
Manager
Release
3.0 and
later
5 of 12
Issue 3 February 2007
247
Denial Events
Table 54: IP Denial Events (1907 - 2020) 6 of 12
Event
Type
Event Description, as it
appears on the event log
Explanation
Event Data 1
Event Data 2
1944
IP RRJ-PSA merge failure
Registration rejected because the
Personal Station Access (PSA) merge
failed (internal software error). Check for
corruption
UID
IP address of
the endpoint
1945
IP RRJ-New IP user fail
Registration rejected because of failure to
construct new H323 User object (internal
software error).
0
IP address of
the endpoint
1946
IP RRJ-PSA merge failure
Registration rejected because the
LoginManager Personal Station Access
(PSA) merge operation failed (internal
software error). Check for corruption.
0
IP address of
the endpoint
1947
IP RRJ-PSA unmerge fail
Registration rejected because the
LoginManager Personal Station Access
(PSA) unmerge operation failed (internal
software error). Check for corruption.
UID
IP address of
the endpoint
1948
IP RRJ-Complete pend reg
Registration rejected because of failure to
obtain a station user record (internal
software error – corrupt translation).
UID
IP address of
the endpoint
1949
IP RRJ-Build KARCF msg
Registration rejected because of failure to
build a KeepAlive Registration Confirm
(KARCF) message (internal software
error).
0
IP address of
the endpoint
1950
IP RRJ-Build RCF msg
Registration rejected because of failure to
build a Registration Confirm (RCF)
message (internal software error).
0 or UID
IP address of
the endpoint
1951
IP GRJ-Invld IP addr/port
Gatekeeper request rejected because of
invalid destination IP address and port in
the request (GRQ).
0
IP address
1952
IP GRJ-Invld gatekeeperID
Gatekeeper request rejected because the
message is not for this gatekeeper.
Gatekeeper ID
IP address
1953
IP GRJ-Invld auth capblty
Gatekeeper request rejected because the
gatekeeper supports a capability that the
registering endpoint does not.
0
IP address of
the endpoint
1954
IP GRJ-Invld auth algrthm
Gatekeeper request rejected because no
compatible authentication algorithm
exists between the endpoint and the
gatekeeper.
0
IP address of
the endpoint
1955
(not
used in
IP GRJ-Bld GCF:Gatewy/
MCU
Gatekeeper request rejected because of
failure to build a GateKeeper Confirm
(GCF) message for a GateWay/MCU
(internal software error).
0
IP address
Communication
Manager
Release
3.0)
6 of 12
248 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Denial Event Tables
Table 54: IP Denial Events (1907 - 2020) 7 of 12
Event
Type
Event Description, as it
appears on the event log
Explanation
Event Data 1
Event Data 2
1956
(not
used in
IP GRJ-Bld GCF:TTI
Gatekeeper request rejected because of
failure to build a GateKeeper Confirm
(GCF) message for an un-named
endpoint registration (internal software
error).
0
IP address
IP GRJ-GK will not host
Gatekeeper request rejected because the
gatekeeper is unwilling to host endpoint
because:
TTI state
IP address of
the endpoint
Communication
Manager
Release
3.0
1957
Communication
Manager
● no alias address has been
Release
2.2 and
earlier
provided
or
● Terminal Translation Initiation
(TTI) is in incorrect state (for
example, TTI is not enabled for
voice)
IP GRJ-GK will not host
Gatekeeper request rejected because the
gatekeeper is unwilling to host endpoint
because no alias address has been
provided.
Endpoint type
sent in GRQ
IP address of
the endpoint
1958
IP GRJ-Invalid extension
Gatekeeper request rejected because the
extension is not administered.
Either extension
number or 0
IP address of
the endpoint
1959
IP GRJ-No stn user record
Gatekeeper request rejected because no
station user record exists for registering
this user (internal software error).
UID
IP address of
the endpoint
1960
IP FURQ-Shared Ctrl Unreg
Forced Unregistration Request: The
Gatekeeper is unregistering the IP
Softphone because it is in shared control
with IP Telephone, and the Telephone is
unregistering.
UID
IP address of IP
Softphone
1961
IP GRJ-Build GCF msg
Gatekeeper request rejected because of
failure to build a GateKeeper Confirm
(GCF) message (internal software error).
UID
IP address of
the endpoint
1962
IP LRJ-No H323 sig group
Location Request rejected because no
H.323 signaling group is administered to
handle the call.
UID
IP address of
the far-end
1963
IP LRJ-Build LCF msg
Location Request rejected because of
failure to build a Location Request
Confirm (LCF) message (internal
software error).
UID
IP address
1964
IP DRJ-Null UserID
Disengage Request rejected because the
endpoint ID could not be converted to a
User ID (UID).
UID
IP address
1957
Communication
Manager
Release
3.0 and
later
7 of 12
Issue 3 February 2007
249
Denial Events
Table 54: IP Denial Events (1907 - 2020) 8 of 12
Event
Type
Event Description, as it
appears on the event log
Explanation
Event Data 1
Event Data 2
1965
IP DRJ-Bld DCF:Gatewy/
MCU
Disengage Request rejected because of
failure to build Disengage Request
Confirm (DCF) message for a gateway or
MCU (internal software error).
UID
IP address
1966
IP DRJ-Endpt not reg
Disengage Request rejected because the
endpoint is not registered.
UID
IP address
1967
IP DRJ-Build DCF msg
Disengage Request rejected because of
failure to build a Disengage Request
Confirm (DCF) message for a
non-gateway or MCU user (internal
software error).
UID
IP address
1968
IP BRJ-Null UserID
Bandwidth Request rejected because an
invalid endpoint ID was received.
0
IP address
1969
IP BRJ-Bld BCF:Gatewy/
MCU
Bandwidth Request rejected because of
failure to build a Bandwidth Request
Confirm (BCF) message for a Gateway or
MCU (internal software error).
UID
IP address
1970
IP BRJ-Endpt not reg
Bandwidth Request rejected because the
endpoint is not registered.
UID
IP address
1971
IP BRJ-Build BCF msg
Bandwidth Request rejected because of
failure to build a Bandwidth Request
Confirm (BCF) message for a
non-Gateway or MCU user (internal
software error).
UID
IP address
1972
IP BRJ-No H323 user
Bandwidth Request rejected because the
H.323 user object does not exist (internal
software error).
UID
IP address
1973
IP BRJ-Call non-existent
Bandwidth Request rejected because the
request is made for a non-existing call.
UID
IP address
1974
IP BRJ-Bandwdth rqst fail
Bandwidth Request rejected because of
unexpected return code from bandwidth
request.
UID
IP address
1975
IP ARJ-Null UserID
Admission Request rejected: received
invalid endpoint ID.
NIL UID
IP address
1976
IP ARJ-Endpt not reg
Admission Request rejected: the endpoint
is not registered.
UID
IP address
1977
IP ARJ-No avail B-channel
Admission Request rejected: no
B channel is available for the call.
UID
IP address
1978
IP ARJ-Bld ACF:Gatewy/
MCU
Admission Request rejected: because of
failure to build an Admission Request
Confirm (ACF) message for a Gateway or
MCU (internal software error).
UID
IP address
1979
IP ARJ-Not an H323 user
Admission Request rejected: request was
received from a non-H.323 user.
UID
IP address
1980
IP ARJ-Stn not in service
Admission Request rejected: station is
not in service.
UID
IP address
8 of 12
250 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Denial Event Tables
Table 54: IP Denial Events (1907 - 2020) 9 of 12
Event
Type
Event Description, as it
appears on the event log
Explanation
Event Data 1
Event Data 2
1981
IP ARJ-Build ACF msg
Admission Request rejected: failure to
build an Admission Request Confirm
(ACF) message for a non-Gateway or
MCU user (internal software error).
UID
IP address
1982
IP ARJ-No H323 user
Admission Request rejected: H.323 user
object does not exist (internal software
error).
UID
IP address
1983
IP ARJ-CRV already in use
Admission Request rejected: Call
Reference Value (CRV) is already in use
by another call.
UID
IP address
1984
IP ARJ-CRV does not exist
Admission Request rejected: this call
reference value (CRV) does not exist.
UID
IP address
1985
IP ARJ-CRV already in use
Admission Request rejected: Call
Reference Value (CRV) is already in use
by another call. An ARQ has been
received while an earlier one is still
pending.
UID
IP address
1986
IP ARJ-Insuff bandwidth
Admission Request rejected: insufficient
bandwidth available to support this call.
UID
IP address
1987
IP ARJ-Admissn rqst fail
Admission Request rejected: unexpected
return code from Admission Request
(internal software error).
UID
IP address
1988
IP URJ-Null UserID
Unregistration Request rejected: received
invalid endpoint ID.
0
IP address of
the endpoint
1989
IP URJ-Endpt not reg
Unregistration Request rejected: endpoint
is not registered.
UID
IP address of
the endpoint
1990
IP URJ-No endpoint ID
Unregistration Request rejected: no
endpoint ID provided in URQ.
0
IP address of
the endpoint
1991
IP URJ-GW/MCU is not reg
Unregistration Request rejected: URQ
received from a Gateway or MCU that is
not registered.
UID
IP address of
the far-end
1992
IP URJ-No H323 sig group
Unregistration Request rejected because
there is no H.323 user for the signaling
group (internal software error).
UID
IP address of
the far-end
1993
IP URJ-No non-std data
Unregistration Request rejected because
there is no non-standard data in the URQ.
UID
IP address of
the endpoint
1994
IP URJ-NSD has invld OID
Unregistration Request rejected because
the Non-standard Data (NSD) from the
registered application has an invalid
object ID in the URQ.
UID
IP address of
the endpoint
1995
IP URJ-Can’t decode NSD
Unregistration Request rejected because
of failure to decode Non-standard Data
(NSD) in the URQ.
UID
IP address of
the endpoint
1996
IP URJ-Unexpected NSD
msg
Unregistration Request rejected because
of unexpected Non-standard Data (NSD)
in the URQ from the registered endpoint.
UID
IP address of
the endpoint
9 of 12
Issue 3 February 2007
251
Denial Events
Table 54: IP Denial Events (1907 - 2020) 10 of 12
Event
Type
Event Description, as it
appears on the event log
Explanation
Event Data 1
Event Data 2
1997
IP URJ-User is on a call
Unregistration Request rejected because
the user is on a call.
UID
IP address of
the endpoint
1998
IP URJ-PSA unmerge failed
Unregistration Request rejected because
the Personal Station Access (PSA)
unmerge operation failed (internal
software error). Check for corruption.
UID
IP address of
the endpoint
1999
IP URJ-PSA merge failed
Unregistration Request rejected because
the Personal Station Access (PSA) merge
operation failed (internal software error).
Check for corruption
UID
IP address of
the endpoint
2000
IP URJ-No stn user record
Unregistration Request rejected because
no station user record exists for
unregistering user (internal software
error).
UID
IP address of
the endpoint
2001
IP URJ-TTI op failed
Unregistration Request rejected because
of an unexpected Terminal Translation
Initiation (TTI) return code.
UID
IP address of
the endpoint
2002
IP URJ-Build UCF msg
Unregistration Request rejected because
of failure to build an unregistration
request confirm (UCF) message (internal
software error).
0
IP address of
the endpoint
2003
IP URJ-PSA unmerge failed
Unregistration Request rejected because
the Personal Station Access (PSA)
unmerge operation failed (internal
software error). Check for corruption.
UID
IP address of
the endpoint
2004
IP URJ-No stn user record
Unregistration Request rejected because
the no station user record exists for the
unregistering user (internal software
error).
UID
IP address of
the endpoint
2005
IP URJ-PSA unmerge failed
Unregistration Request rejected because
the Personal Station Access (PSA)
unmerge operation failed (internal
software error).
UID
IP address of
the endpoint
2006
(not
used in
IP FURQ-no H.323 ext reg
Force Unregistration Request. Received
a KeepAlive request (RRQ) from a
dual-connect endpoint without a
registered H.323 extension (cannot make
calls). Re-register the endpoint.
UID
IP address
2007
IP FURQ-User, no sig conn
Force Unregistration Request. Unregister
user because there is no signaling
connection. RAS is alive, but the
signaling connection has gone down
(user cannot make calls). Re-register the
endpoint.
UID
IP address of
the endpoint
2008
IP FURQ-H323, no sig conn
Force Unregistration Request. Unregister
associated H.323 user because there is
no signaling connection. Re-register the
endpoint.
UID
IP address of
the endpoint
Communication
Manager
Release
3.0)
10 of 12
252 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Denial Event Tables
Table 54: IP Denial Events (1907 - 2020) 11 of 12
Event
Type
Event Description, as it
appears on the event log
Explanation
Event Data 1
Event Data 2
2009
IP FURQ-Move user
Force Unregistration Request. Extension
is already registered, but received a
forced login registration request (RRQ).
Send a URQ to the existing extension.
UID
IP address of
the endpoint
2010
IP FURQ-Sig Conn closed
Forced Unregistration Request. The
Gatekeeper is unregistering the endpoint
because its call signaling connection has
closed.
UID
0
2011
IP FURQ-NoQ931 msg rcvd
Force Unregistration Request. After an
endpoint registers it should initiate the
TCP connection and send a SETUP
message. The SETUP message has not
been received from the endpoint, and no
Q931 Call object exists. The endpoint
cannot make calls, so unregister it.
H.323 UID
IP address of
the endpoint
2012
IP FURQ-Aged Endpt-no KA
Force Unregistration Request. Unregister
endpoint that has aged out. Endpoint's
time to live (TTL) expired without
receiving a keep-alive request (RRQ).
UID
IP address of
the endpoint
2013
IP FURQ-SigGrp removed
Force Unregistration Request. An H.323
Gateway (administered as a signaling
group) is registered. Unregister the
Gateway before removing the
administered signaling group.
Gateway UID
IP address of
the far-end
2014
IP FURQ-Siggrp changed
Force Unregistration Request. Changes
have been made to a registered H.323
Gateway (administered as a signaling
group). Unregister the Gateway.
Signaling group
IP address of
the near-end
2015
IP FURQ-Ext removed
Forced Unregistration Request.
Unregister user because the extension
has been removed.
UID
0
2016
(not
used in
IP FURQ-IPusr is sftphone
Forced Unregistration Request.
IP User-UID
0
IP User-UID
0
● A user has Personal Station
Accessed (PSA) an extension
that was registered as an IP
endpoint.
Communication
Manager
Release
3.0)
2017
Communication
Manager
● An IP telephone extension in
shared-control was moved to
another IP port via registration.
Both shared-control IP
Telephone and IP softphone will
unregister if the rejected
registration attempt is forced.
IP FURQ-Records
exhausted
Forced Unregistration Request.
Unregister the LAN port if there are no
station user-records remaining.
Release
2.2 and
earlier
11 of 12
Issue 3 February 2007
253
Denial Events
Table 54: IP Denial Events (1907 - 2020) 12 of 12
Event
Type
Event Description, as it
appears on the event log
Explanation
Event Data 1
Event Data 2
2017
IP FURQ-Records
exhausted
Forced Unregistration Request.
Unregister the endpoint if there are no
station user-records remaining.
IP User-UID
0
2018
IP FURQ-Mtc: H323/Vphone
Forced Unregistration Request. The
release command was run on the
extension or port.
UID
0
2019
IP FURQ-Mtc: Remote Max
Forced Unregistration Request. The
release command was run on the
Remote Office extension or port.
UID
0
2020
IP FURQ-Mtc:RemOfc TTI
Forced Unregistration Request. Terminal
Translation Initiation (TTI) background
maintenance task has requested the
removal of Remote Office LAN TTI ports.
UID
0
IP FURQ-Mtc:RemOfc TTI
Forced Unregistration Request. Terminal
Translation Initiation (TTI) was turned off.
UID
0
Communication
Manager
Release
3.0 and
later
Communication
Manager
Release
2.2 and
earlier
2020
Communication
Manager
Release
3.0 and
later
12 of 12
Call Process Denial Events
Event Types 2021 - 2299 show Call Process denial events, as listed in Call Process denial
events (2021 - 2299) on page 254.
Table 55: Call Process denial events (2021 - 2299) 1 of 17
Event
Type
Event Description, as it
appears on the event log
Explanation
2021
Cust Sel of DIDs inactive
Custom Selection of VIP Direct
Inward Dialing numbers feature is
not active.
2022
Annc pres but not admin
Announcement present but not
administered.
2023
Annc pres none on board
Announcement present but no
announcements administered for
the board.
Event Data 1
Event Data 2
1 of 17
254 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Denial Event Tables
Table 55: Call Process denial events (2021 - 2299) 2 of 17
Event
Type
Event Description, as it
appears on the event log
Explanation
Event Data 1
Event Data 2
2024
Cannot create entry
Registration rejected because
unable to create an entry in the
MTM complex table.
UID
IP address of the endpoint
2025
Unadministered option
Registration rejected because the
option chosen by the endpoint in
the RRQ for the emergency call
does not match the option
administered on the station form.
UID
IP address of the endpoint
2026
Xmobile OOS: block orig
Xmobile offhook request rejected
because Xmobile station has been
taken out of service.
2027
Annc not found on board
User attempted to play VAL Board
announcement and file was not
found on board.
2028
Annc file has bad format
User attempted to play VAL Board
announcement and file had bad
format.
2029
IP GRJ-NSD has invld
OID
Gatekeeper Request rejected
because the Non Standard Data
(NSD) from the registered
application has an invalid object ID.
UID
IP address of the endpoint
2030
IP GRJ-Can't decode
NSD
Gatekeeper Request rejected
because of failure to decode Non
Standard Data (NSD) element.
UID
IP address of the endpoint
2031
IP GRJ-Unexpected NSD
msg
Gatekeeper Request rejected
because of unexpected Non
Standard Data (NSD) message
from the registered application
endpoint.
UID
IP address of the endpoint
2032
Force Unregistration Req
Force Unregistration Request.
Instruct the RAS manager to
cleanup a User ID which had just
been registered prior to a system
restart. This event is not logged, but
only passed in the URQ.
2033
IP FURQ-Demand
Unregister
Force Unregistration Request. The
command to force unregister
endpoints has been executed from
the SAT.
User ID
IP address
IP FURQ-Demand
Unregister
Force Unregistration Request.
Reset ip-stations was executed
from the SAT to force unregister
endpoints.
NULL
NULL
Communication
Manager
Release
2.2 and
earlier
2033
Communication
Manager
Release
3.0 and
later
2 of 17
Issue 3 February 2007
255
Denial Events
Table 55: Call Process denial events (2021 - 2299) 3 of 17
Event
Type
Event Description, as it
appears on the event log
Explanation
Event Data 1
Event Data 2
2034
Illegal TSC interaction
A QSIG Non Call
Associated-Temporary Signaling
Connection (NCA-TSC) tried to
route out an AT&T TSC, or vice
versa, and this interaction is not
supported. This might occur when a
bsr_poll call over an IP trunk tries to
use a QSIG TSC but is tandemed
out an AT&T TSC.
2035
NCA-TSC not available
Possible causes:
● The terminated
administered Temporary
Signaling Connection
(TSC) endpoint is disabled
● The incoming Non Call
Associated-Temporary
Signaling Connection
(NCA-TSC) call arrived at
the wrong signaling group
● The Maximum number of
NCA-TSC is set to 0
2036
Incoming QSIG LWC
failed
Leave Word Calling on the
incoming side of a QSIG_LWC MSI
CS0FAC message failed.
2037
QSIG LWC fail find voice
Getting the voice callr on the
outgoing side of a QSIG_LWC MSI
SETUP message failed.
2038
QSIG LWC fail get cling
Getting the calling party number
from the incoming side of the call
failed.
2039
IP KA-No endpoint ID
Keep Alive Registration Request.
Registration rejected because no
endpoint identifier was provided.
0
IP address
2040
IP GRJ-No C-LAN
available
Gatekeeper Request rejected
because no resources available for
signaling connection.
UID
IP address
2041
IP RRJ-No DSP Resource
Registration Request rejected
because no Digital Signal
Processor (DSP) resources are
available.
UID
IP address
Registration Request rejected
because no Digital Signal
Processor (DSP) resources are
available.
UID
IP address
ARQ rejected because srcInfo and
destinationInfo contents indicate
the multipoint ept (VSX) is calling
itself.
UID
IP address
2042
2043
Multipoint call to self
20442046
not assigned
3 of 17
256 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Denial Event Tables
Table 55: Call Process denial events (2021 - 2299) 4 of 17
Event
Type
Event Description, as it
appears on the event log
Explanation
2047
Reject-Unauthorized MG
Registration rejected because it
was received from unauthorized
media gateway.
2048
Reject-MGC not ready
Registration rejected because it is
not ready for a media gateway
re-registration.
2049
No VOIP Resource
VOIP Resources unavailable.
2050
No MG Resource
No gateway resource available.
2051
IP GRJ-RemOfc No Sig
Grp
Remote Office invalid request
(GRQ) No Sig Group available.
2052
IP RRJ-RemOfc No Sig
Grp
Remote Office invalid registration
request (RRQ) No Sig group
available.
2053
MG heartbeat missed
MGKeepAlive: Wakeup() media
gateway heartbeat missed,
indicates lack of traffic from
specified gateway.
2054
Signaling CONN
Congestion
UMSocket: SockWrite() Congestion
on the Signaling Link due to PCD
buffer exhaustion.
2055
Reset MG - Pkt Send Err
Reset the media gateway Signaling
Link due to error in Sending
packets.
2056
No null caps SBS orig
end
IncomingMsg. Null caps not
received on originating end of
Separation of Bearer and Signaling
(SBS) trunk.
2057
No null caps SBS term
end
IncomingMsg. Null caps not
received on terminating end of
Separation of Bearer and Signaling
(SBS) trunk.
2058
Null caps on H323 trunk
IncomingMsg. Null caps received
on terminating end of H323 trunk.
2059
SecCode change
disallowed
Change of security code through
Feature Access Code not
supported for IP.
2060
SA8508:Off
Emergency access call to the
attendant using the 2nd access
code is not permitted because the
SA8508 is not optioned.
2061
Invalid Post msg dgt/tmo
Post message digit timeout.
2062
Post msg too many msg
dgt
Post message too many digits.
2063
Post msg not stn user
Post message not station user.
Event Data 1
Event Data 2
4 of 17
Issue 3 February 2007
257
Denial Events
Table 55: Call Process denial events (2021 - 2299) 5 of 17
Event
Type
Event Description, as it
appears on the event log
Explanation
Event Data 1
Event Data 2
2064
IP RRJ-NSD encode
failed
Registration rejected because of
failure to encode Non-standard
Data (NSD) message.
UID
IP address
2065
IP RRJ-Invalid vendor id
Registration rejected because LSP
requesting registration has not sent
a valid vendor ID.
NULL
IP address
2066
IP RRJ-LSP obj not init
Registration rejected because the
LSP object has not been initialized.
NULL
IP address
2067
IP RRJ-NSD improper
OID
Registration rejected because the
Non-standard Data (NSD) sent by
the LSP contains an invalid OID.
NULL
IP address
2068
IP RRJ-Cannot decode
NSD
Registration rejected because of
failure to decode Non-standard
Data (NSD) message sent by the
LSP.
NULL
IP address
2069
IP RRJ-Unxpctd NSD
Registration rejected because of
receipt of an unexpected
Non-standard Data (NSD) message
from LSP.
NULL
IP address
2070
MG must send full reg
msg
Media gateway attempted
registration with “warm start”
condition, but the controller needs
“cold start” data.
2071
Serial Number incorrect
Media gateway attempted to
register with a different serial
number.
2072
Conf/Transfer 2 Meet-me
Conference or transfer 2 Meet-me
conference call.
2073
Permission denied (or)
Download permission
deny
User attempted to download
firmware to a station. User does not
have console permission.
2074
Rec fail: annc is playing
Attempt to record a VAL
announcement while that
announcement is playing on a VAL
board.
2075
Var-in-Vec COS restricted
User does not have console
permissions
2076
IP RRJ-Call Mismatch
IP Registration Rejection (RRJ)
because of no call present on the
switch side. But there is a call
present on the ept.
UID
IP address.
2077
IP FURQ-CallTimer
Expired
Force Unregistration Request.
Unregister endpoint whose call
preservation timer (H323 link loss
delay timer) expires.
UID
IP address.
5 of 17
258 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Denial Event Tables
Table 55: Call Process denial events (2021 - 2299) 6 of 17
Event
Type
Event Description, as it
appears on the event log
Explanation
Event Data 1
Event Data 2
2078
Extend Call Button Denial
OPTIM Extend Call via extend call
button press was denied.
station where
the button
was pushed
Reason the call was denied:
0 - denied because the call
already has 6 ports on it
1 - denied because the
station is at the OPTIM call
limit
2 - denied because the
application has no termination
mapping
3 - denied because call failed
to extend (check application
RTU)
2079
IP RRJ-Invld sta state
Registration rejected because set in
wrong state (for example on call,
Out of Service (OOS), Administered
Without Hardware (AWOH),
Terminal Translation Initiation (TTI),
shared-control endpoints attempt to
register to different LSPs).
2080
IP FURQ-User dialed TSA
IP Softphone in shared control
configuration with DCP is forced
unregistered because user dialed
TSA.
2081
IP FURQ-Invld sta state
IP Softphone in shared control
configuration with DCP is forced
unregistered because softphone
switched to invalid state.
2082
Exceeded TLS conn limit
A TLS socket was rejected because
of the constraint on the maximum
number of TLS peers.
2083
TLS: No cert returned
A peer cert was rejected by
common name checking.
2084
TLS: Handshake Failure
Handshake failed, for example due
to no common cipher suite.
2085
TLS: Certificate expired
An expired certificate was returned
and rejected.
2086
SBS bearer Auth not
supp
If authorization code is required on
outgoing Separation of Bearer and
Signaling (SBS) bearer call, this is
not supported. The call is dropped
with intercept treatment to the
originator.
2087
IP RRJ-Shrd Ctrl
OutofSrv
Used to inform softphone trying to
register in shared control with an
out-of-service DCP endpoint to try
registration with LSP.
UID
IP address
2088
TLS: No Authorization
Bad Record Max. For example, an
attacker does not have the correct
private key, which can go
undetected until the MAC of the
exchange is checked.
6 of 17
Issue 3 February 2007
259
Denial Events
Table 55: Call Process denial events (2021 - 2299) 7 of 17
Event
Type
Event Description, as it
appears on the event log
Explanation
2089
TLS: Bad Record MAC
Bad Record Max. For example, an
attacker does not have the correct
private key, which can go
undetected until the MAC of the
exchange is checked.
2090
Event Data 1
Event Data 2
IP address of
the far end to
which the call
failed
Port number of the far end
UID of the
party that was
attempting to
terminate
Cause value/feedback
indicating the reason.
TLS shutdown received. Listen
socket could not be created.
2091
Conf/xfer Audix rec
AUDIX one-step rec while conf.
2092
Post msg invalid SSC
Post message invalid Station
Security Code (SSC).
2093
Can't start
announcement
Cannot start announcement.
2094
TCP/IP sig socket failure
Establish a socket on an IP trunk.
The far end might be
mis-administered.
2095
Rmt Div-fwding ext local
QSIG Remote Diversion activation
for local extension not allowed.
2096
Rmt Div-SSC too long
QSIG Remote Diversion Station
Security Code (SSC) contains too
many digits.
2097
Rmt Div-non QSIG trunk
QSIG Remote Diversion is not
allowed over a non-QSIG trunk.
2098
Rmt Div-act ext not stn
QSIG Remote Diversion activation
only allowed from station user.
2099
Rmt Div-act/deact failed
QSIG Remote Diversion activation/
deactivation failed.
2100
Rmt Div-QSIG VALU
disable
QSIG Remote Diversion is not
allowed over a QSIG trunk with
QSIG VALU disabled.
2101
Feat. requires only dgts
A feature was activated via a
request URI. The part of the request
URI string that should contain all
digits contained characters other
than digits.
2102
SIP Estab Timer expiry
SIP call establishment timer expired
prior to 200 OK (incoming or
outgoing call). Timer length is
administered on SIP sig-group
forms.
2103
Cannot ring add-in party
Attempt to add a party to a call
failed at the termination stage.
7 of 17
260 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Denial Event Tables
Table 55: Call Process denial events (2021 - 2299) 8 of 17
Event
Type
Event Description, as it
appears on the event log
Explanation
Event Data 1
Event Data 2
2104
Cannot add party to call
Attempt to add a party to a call
failed at or after answer.
UID of the
party that was
being added
in
reason code:
1: internal failure (look for
proc_err around same time)
2: internal failure (look for
proc_err around same time)
3: conflict (ie adding
announcement to call with
tone or announcement)
4: already have six
connected/held parties on the
call
5: unable to combine voice
streams
6: internal failure (look for
proc_err around same time)
7: internal failure (look for
proc_err around same time)
2105
SCCAN handover denied
Seamless Converged
Communications Across Networks
(SCCAN) attempt to handover
failed.
UID of the
station
involved in
handover
reason for failure:
0: No call found to handover
to
1: There is already a call in
the wireless domain
2: There are multiple
candidate calls to handover to
3: Handover from call not
found
4: Handover to call not found
5: Handover aborted
6: Call is at conference limit
2106
SCCAN announcement
denied
Seamless Converged
Communications Across Networks
(SCCAN) attempt to handover
failed.
UID of the
station
involved in
handover
reason for failure:
0: Announcement not
administered on sys-param
sccan form
1+ - Feedback type
OPTIM SCCAN termination
was denied
1: WLAN call limit exceeded
2: No termination mapping
3: Cellular call limit exceeded
4: No termination mapping or
call NOT allowed or disabled
disabled is the most likely
cause (user controlled)
5: Call on bridged
appearance, and termination
disallowed
2107
SCCAN call out blocked
OPTIM Seamless Converged
Communications Across Networks
(SCCAN) termination was denied
UID of the
station
involved
reason for denial:
1: WLAN call limit exceeded
2: No termination mapping
3: Cellular call limit exceeded
4: No termination mapping or
call NOT allowed or disabled.
Disabled is the most likely
cause (user controlled)
5: Call on bridged appearance
and termination disallowed.
8 of 17
Issue 3 February 2007
261
Denial Events
Table 55: Call Process denial events (2021 - 2299) 9 of 17
Event
Type
Event Description, as it
appears on the event log
Explanation
Event Data 1
Event Data 2
2108
SCCAN retransmit
denied
There are problems with Seamless
Converged Communications
Across Networks (SCCAN) notify
retransmission response.
UID of the
station
involved
reason for denial:
1:Could not get Event header
from request
2: Could not get time to wait
for retransmission
3: Unknown event type
4: Internal failure (look for
proc_err around same time)
5: OPTIM application not
SCCAN
6: Station not administered
with OPTIM
2109
IP RRJ-Unknown
unnamed
Registration rejected because an
unnamed endpoint did not have the
terminal present bit set, or because
it did not supply Lucent vendor
information.
2110
Release btn push ignored
Agent pushed IM_ACD_REL button
simultaneously with call
termination.
UID of agent
pushing
IM_ACD_RE
L button
NULL
2111
IP RRJ-TTI reg not in map
Deny Terminal Translation Initiation
(TTI) registration, IP endpoint not in
ip-network-map.
IP address
TTI state
2112
IP RRJ-TTI reg shared ctl
Deny Terminal Translation Initiation
(TTI) registration, IP endpoint
requesting shared control.
IP address
TTI state
2112
IP LRJ-No Route to dest
Send Location Request reject
message because we cannot route
to the destination.
2113
IP RRJ-TTI incapable
Deny Terminal Translation Initiation
(TTI) registration, IP endpoint not
TTI capable.
IP address
TTI state
2113
Invalid NSF for CA-TSC
Rq
Invalid NSF for CA-Temporary
Signaling Connection (TSC)
request.
IP RRJ-TTI reg eConsole
Deny Terminal Translation Initiation
(TTI) registration, request from IP
eConsole.
NULL
IP address.
Communication
Manager
Release
3.1
Communication
Manager
Release
3.1
2114
2114
Communication
Manager
Release
3.1
AAR/ARS not accessible from
Direct Inward Dial/Direct
Inward-Outward Dial (DID/DIOD)
trunk
9 of 17
262 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Denial Event Tables
Table 55: Call Process denial events (2021 - 2299) 10 of 17
Event
Type
Event Description, as it
appears on the event log
Explanation
Event Data 1
Event Data 2
2115
IP RRJ-RO addr no admin
Deny Terminal Translation Initiation
(TTI) registration, Remote Office
address not administered.
IP address
TTI state
2115
Transfer denied - SA8759
Special Application block of
call-transfer. Drop if second call-leg
is not answered.
2116
460.1 Neg failed in GRQ
460.1 feature not supported.
2116
Conf/drop denied SA8759
Special Application block of
call-conference/drop if second
call-leg is not answered.
2117
Agent accept login error
Non-EAS ACD split agent accept
login failed
Agent UID
Caller ID
2117
TSC attempt denied
TSC administration is incorrect on
the Feature Related System
Parameters screen and the Route
Pattern screen.
2118
ACD agent tot exceeds
max
Max number of ACD agents already
logged-in
UID
Logged-in ACD agent count
2119
Memb per skill exceeds
mx
Max number of agents already
logged-in to skill
Agent UID
Skill number
2120
Advocate agents exceed
mx
Max number of Business Advocate
agents already logged-in
Agent UID
Logged-in Business Advocate
Agent count
2121
Oth agt using this logid
Some other agent already using
this loginID
Agent UID
Split number
2122
This agt using oth logid
This agent already using some
other loginID
Agent UID
Split number
2123
BCMS logid val failed
BCMS (Basic Call Management
System) Login ID validation failed.
Agent UID
Split number
2124
Agent tot exceeds sys
max
Agent total exceeds system limit
Agent UID
Agent total
2125
Over CMS agent login
cap
Maxed-out mis_ap CMS capacity
Agent UID
Skill number
2126
Over CMS agent login
cap
Maxed out mis_ap CMS capacity
Agent UID
Skill number
2127
Over BCMS agent login
cap
Maxed out mis_ap BCMS (Basic
Call Management System) capacity
Agent UID
BCMS agent total
Communication
Manager
Release
3.1
Communication
Manager
Release
3.1
Communication
Manager
Release
3.1.2
10 of 17
Issue 3 February 2007
263
Denial Events
Table 55: Call Process denial events (2021 - 2299) 11 of 17
Event
Type
Event Description, as it
appears on the event log
2128
Explanation
Event Data 1
Event Data 2
Missing far-end IGAR LDN
(Inter-Gateway Alternate Routing)
2129
No near-end IGAR trunks
No idle trunks in either network
region (IGAR request)
2130
IP RRJ-TTI reg not in map
Deny TTI registration - IP endpoint
not in ip-network-map
IP address
TTI state
2131
IP RRJ-TTI reg shared ctl
Deny TTI registration - IP endpoint
requesting shared control
IP address
TTI state
2132
IP RRJ-TTI incapable
Deny TTI registration - IP endpoint
not TTI capable
IP address
TTI state
2133
IP RRJ-Unnamed
disabled
Deny TTI registration - Unnamed
registration feature is disabled.
IP address
TTI state
2134
RAS message failed
Annex H
Incoming RAS message failed
Annex H authentication and was
ignored
2135
Q931 message failed
Annex H
Incoming Q931 message failed
Annex H authentication and was
ignored
2136
H.245 Port alloc failure
Unable to allocate H.245 pooled
port; try dynamic port, but the
connection attempt will likely be
blocked by firewall
2137
H.245 VideFastUpd throt
Throttled excessive H245
VideoFastUpdate message
2138
H.245 ConfInd Join throt
Throttled excessive H245
ConferenceIndication
EmterminalJoinedCOnference
message
2139
H245 Timeout Call
Dropped
H245 connection timed out and call
was dropped
2140
IP RRJ-TTI reg eConsole
Deny TTI registration - request from
IP eConsole
NULL
IP Address
2141
IP RRJ-RO addr no admin
Deny TTI registration - Remote
Office address is not administered
IP address
TTI state
2142
460.1 Neg failed in GRQ
460.1 feature is not supported
2143
BRJ Rcvd-Not Bound
Received a BRJ message,
EmBRJ_notBound__chosen
2144
BRJ Rcvd-Inv Conf Id
Received a BRJ message,
EmBRJ_invalidConferenceID_chos
en
2145
BRJ Rcvd-Inv Permission
Received a BRJ message,
EmBRJ_invalidPermission_chosen
11 of 17
264 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Denial Event Tables
Table 55: Call Process denial events (2021 - 2299) 12 of 17
Event
Type
Event Description, as it
appears on the event log
Explanation
2146
BRJ Rcvd-Insuff Rsrc
Received a BRJ message,
EmBRJ_insufficientResources_cho
sen
2147
BRJ Rcvd-Inv Revision
Received a BRJ message,
EmBRJ_invalidRevision_chosen
2148
BRJ Rcvd-Security
Denial
Received a BRJ message,
EmBRJ_securityDenial_chosen
2149
BRJ Rcvd-Security Error
Received a BRJ message,
EmBRJ_securityError_chosen
2150
BRJ Rcvd-Unknown
Reason
Received a BRJ message,
EmBRJ_undefinedReason_chosen
2151
IP FURQ shrd ctrl sftphn
Busyout of a shared control
softphone forces unregistration of
the softphone, leaves base phone
in service
2152
Conf/xfer denied-SA8652
Denial for NH Consult call merge
(conference) Special Application
2153
Feature denied-SA8652
Denial for features used on an NH
Consult call (hold, park) Special
Application
2154
NHCnsl Orig
denied-SA8652
Denial for NH Consult origination
Special Application
2155
Unsupported Remove VM
typ
Deny transfer into voice mail
because voice mail hunt group type
is not supported. Must be SIP,
QSIG, or AUDIX.
2156
Mod_ID mismatch in
setup
There is a mismatch in Module ID
setup
2157
call mismatch in setup
Call mismatch in setup
2158
No TSC’s left in system
No free Temporary Signaling
Connection (TSC) user record is
available.
2159
No TSC’s for this D-chan
No free Temporary Signaling
Connection (TSC) is available.
2160
EMU:invalid act/deact ext
Enterprise Mobility User (EMU)
activation/deactivation only allowed
from station user.
2161
EMU:dny act for local ext
Enterprise Mobility User (EMU)
activation not allowed for local
extension.
2162
EMU:nonQSIG trunk
Enterprise Mobility User (EMU)
over non-QSIG trunk not allowed.
2163
EMU:vst login not
allowed
Enterprise Mobility User (EMU)
login not allowed based on station
administration.
Event Data 1
Event Data 2
12 of 17
Issue 3 February 2007
265
Denial Events
Table 55: Call Process denial events (2021 - 2299) 13 of 17
Event
Type
Event Description, as it
appears on the event log
Explanation
2164
CC:Ringout Call Failure
QSIG-CC: Ringout call failure
2165
CC:Comparison Failed
QSIG-CC Orig cancel: components
did not match
2166
Button lbl mem
exhausted
There is no more customized label
space
2167
EMU:CTMI term to
non-SSB
CtmiInform SETUP is terminating to
a non-SSB trunk (Enterprise
Mobility User (EMU))
2168
EMU:Map/vst uid
mismatch
Mapped User ID does not match
the visitor User ID (Enterprise
Mobility User (EMU))
2169
IP GRJ-No PE in region
Gatekeeper Request is rejected
because no resources are available
on this phone’s region
2170
CC:Ringout not Routed
QSIG CC: Rignout could not route
2171
CC:Queueing Failed
QSIG-CC: Queueing failed
2172
CC:Orig comp ck failed
QSIG-CC Exec Possible:
components did not match
2173
CC:Term comp ck failed
QSIG-CC Term Cancel:
components did not match
2174
EMU:Unsup clg pty nbr
fmt
Unsupported calling party
numbering format for Enterprise
Mobility User (EMU)
2175
Event Data 1
Event Data 2
UID
IP address
Module ID mismatch, re-registration
required
2176
SigConn fail to establish
Tried three times to bring up socket
and failed each time. Do not try
again.
2177
Invalid XFR to VM
attempt
Deny transfer into voicemail
because either:
● QSIG transfer to QSIG
voice mail is not allowed
● an attempt was made to
interwork QSIG and SIP
for transferring into
voicemail
2178
EMU:User dialed unsup
FAC
Enterprise Mobility User (EMU)
user dialed an unsupported Feature
Access Code (FAC)
2179
EMU:Non-emrg call
denial
HEMU user placed non-emergency
call (Enterprise Mobility User
(EMU))
2180
EMU:Reg-invld SSC
dialed
Invalid security coded was dialed
during registration (Enterprise
Mobility User (EMU))
13 of 17
266 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Denial Event Tables
Table 55: Call Process denial events (2021 - 2299) 14 of 17
Event
Type
Event Description, as it
appears on the event log
Explanation
2181
EMU:PSA not allowed
PSA not allowed on home station
(Enterprise Mobility User (EMU))
2182
EMU:DeReg-inv SSC
dialed
Invalid security code dialed during
deregistration (Enterprise Mobility
User (EMU))
2183
EMU:Del-invld SSC
dialed
Invalid security code dialed during
deregistration (Enterprise Mobility
User (EMU))
2184
EMU:Usr not fnd far end
User not found in dtabase on far
end (Enterprise Mobility User
(EMU))
2185
EMU:Delete failed far end
The delete operation failed
(Enterprise Mobility User (EMU))
2186
EMU:Reg failed far end
The registration operation failed
(Enterprise Mobility User (EMU))
2187
EMU:DeReg failed far end
The Deregistration operation failed
(Enterprise Mobility User (EMU))
2188
EMU:IPReg block for
VEMU
IP Registration is not allowed when
there is an active Enterprise
Mobility User (EMU)
2189
EMU:EC500 act on nat
stn
Virtual Enterprise Mobility User
(VEMU) registration is not allowed
when EC500 is active on the native
station
2190
EMU:VEMU not map to
home
The Virtual Enterprise Mobility User
(VEMU) attempting deregistration is
not mapped to a specified home
extension
2191
EMU:Forced
deregistration
Forced deregistration of Enterprise
Mobility User (EMU)
2192
EMU:Btn mismatch far
end
Button Mismatch (Enterprise
Mobility User (EMU))
2193
EMU:PSig oper timeout
Partner Signaling operation timed
out (Enterprise Mobility User
(EMU))
2194
EMU:Reg oper timeout
Registration operation timed out
(Enterprise Mobility User (EMU))
2195
EMU:DeReg oper timeout
Deregistration operation timed out
(Enterprise Mobility User (EMU))
2196
EMU:Delete oper timeout
Delete operation timed out
(Enterprise Mobility User (EMU))
2197
Unsupported Remove VM
typ
Deny transfer into voice mail
because the voice mail hunt group
is not a supported type (must be
SIP, QSIG, or AUDIX)
Event Data 1
Event Data 2
14 of 17
Issue 3 February 2007
267
Denial Events
Table 55: Call Process denial events (2021 - 2299) 15 of 17
Event
Type
Event Description, as it
appears on the event log
Explanation
2198
Mod_ID mismatch in
setup
There is a mismatch in the Module
ID in setup
2199
call mismatch in setup
Call mismatch in setup
2200
No TSC’s left in system
No free Temporary Signaling
Connection (TSC) user record
available
2201
No TSC’s for this D-chan
No free Temporary Signaling
Connection (TSC) is available
2202
EMU:invalid act/deact ext
EMU activation/deactivation is
allowed only from the station user
2203
Deny DND: E911CF is
active
Deny DND if E911 call forward is
active
2204
Forced Disconnect
SA8847
Special Application8847 - forced
disconnect of diverted predictive
calls
IPFURQ-reg
expired-nosock
Force unregister the link bounce
phone if its link loss delay timer
expired and it is not on the call
Forced Disconnect
SA8847
Special Application8847 - forced
disconnect of diverted predictive
calls
Wrong Group Page set
type
Wrong set type for group page.
Communication
Manager
Event Data 1
Event Data 2
Release
3.1.x
2204
Communication
Manager
Release
4.0
2205
Communication
Manager
Release
4.0
2206
2207
Invalid digits are collected in
dgt_dgcpkup.
2209
Extension not part of any pickup
group.
2209
Msg’ing Hunt Grp Xln
Bad
An fp-mwi, qsig-mwi, or sip-adjunct
messaging hunt group does not
route over the correct trunking
facility.
2210
ECF: COS value reject
Enhanced call forwarding: the
current Class of Service (COS)
definition does not allow enhanced
call forwarding.
15 of 17
268 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Denial Event Tables
Table 55: Call Process denial events (2021 - 2299) 16 of 17
Event
Type
Event Description, as it
appears on the event log
Explanation
2211
ECF: ATD CFWD active
Enhanced call forwarding: classic
call forwarding all (CFWD) is active
for this station, that received a
ENHCF activation via console
permission.
2212
ECF: ATD CFBDA active
Enhanced call forwarding: classic
call forwarding busy & don’t answer
(CFBDA) is active for this station,
which received a ENHCF activation
via console permission.
2213
ECF: CFWD active
Enhanced call forwarding: classic
Call forwarding all (CFWD) is
active.
2214
ECF: CFBDA active
Enhanced call forwarding: classic
call forwarding busy & don’t answer
(CFBDA) is active.
2215
ECF: Attd fwd own calls
Enhanced call forwarding:
Attendant is not allowed to forward
its own calls.
2216
Cannot override logout
Logout-ovr denied, the agent is not
in the logout tables.
2217
DPT not enab on both
NRs
DPT not enabled for both network
regions.
2218
Answer back failed
Parked call is failed to answer back
even after second attempt.
2219
H.248 transaction
timeout
H.248 transaction timer expired;
media gateway did not send a reply
in the allotted time. See error logs
for terms affected.
2220
ECF: Number invalid
Enhanced call forwarding: Invalid
number entered in case of
extension or call forward
destination.
2221
ECF: COS via btn reject
Enhanced call forwarding: The
current Class of Service (COS)
definition does not allow enhanced
call forwarding via feature button.
2222
ECF: Default denial
Enhanced call forwarding: default
denial.
2223
ECF: Invalid station
Enhanced call forwarding:
Activation, deactivation or status is
requested by an invalid station type
or remote user.
2224
No Disc. Supervision
Tmo.
Call is dropping due to the timeout
of 2 hour no-disconnect supervision
timer. IP Trunk LInk Bounce.
Event Data 1
Event Data 2
16 of 17
Issue 3 February 2007
269
Denial Events
Table 55: Call Process denial events (2021 - 2299) 17 of 17
Event
Type
Event Description, as it
appears on the event log
Explanation
2225
No Disc. Sup. -Invalid
Msg
Call is dropping due to an invalid
stim/msg on a call in no disconnect
supervision processing. IP Trunk
Link Bounce.
2226
Team Pickup of selfs cll
Station calls another station in the
same pickup group, puts the call on
hold and dials FAC for pickup.
Disallow pickup of self-initiated call.
2227
Event Data 1
Event Data 2
So_idx not set.
2228
Flow ctrl out of memory
Out of memory for UMFlowControl
for buffering.
2229
ECF: Button ext invalid
Enhanced call forwarding: Feature
button extension cannot be mapped
to a valid user ID.
2230
ECF: EAS login phys ext
Enhanced call forwarding:
Logged-in EAS agent’s physical
extension is unavailable for any call
forwarding.
2231
Drop: Call Sate Mismatch
Call state mismatch, drop the call.
2232
Drop: CRV audit timeout
CRV audit timeout, drop the call.
2233
ECF: Station no display
Enhanced call forwarding: Display
of status of ENHCF is requested on
a station that is not equipped with a
display.
2234
ECF: ATD station no displ
Enhanced call forwarding:
Extension for display of status of
ENHCF is questioned on a station
that is not equipped with a display.
2235
Drop: lk loss tmr expired
Link Loss Delay Timer expired.
Drop the call.
2236
ECF: Remote cfwd EAS
Enhanced call forwarding: Disallow
any remote call forwarding of an
EAS loginID extension.
2237
DPT src/dst NRs are
same
Deny DPT request, source and
destination network regions are the
same.
2238
INVITE From:domain
Inval.
Domain in the INVITE’s "From"
header is invalid. Block for potential
toll fraud.
2239
Invalid pub-unk
numbering
The public-unknown-numbering
form has not been populated.
22402299
not assigned
17 of 17
270 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Denial Event Tables
Connection Manager Denial Events
Event Types 2300 - 2399 show Connection Manager denial events, as listed in Connection
Manager denial events (2300 - 2399) on page 271.
Table 56: Connection Manager denial events (2300 - 2399) 1 of 4
Event
Type
Event Description, as it
appears on the event log
Explanation
2300
Ept capabilities mismatch
Endpoint connects to Time Division Multiplexed (TDM) bus or
it hairpinned capabilities mismatch.
2301
Tran/rec codec mismatch
Transmitted or received codec mismatch.
2302
Ip_ept is in loopback
Ip_ept is in loopback.
2303
Silence suppress mismatch
Endpoint connects to Time Division Multiplexed (TDM) bus or
is hairpinned silence suppression mismatch.
2304
Tran/rec codec mismatch
Transmitted or received codec mismatch.
2305
Silence suppress mismatch
Ept1 directly connected to Ept2 silence suppression
mismatch.
2306
Reject outbound OLC
Reject outbound OLC.
2307
TDM resource blockage
Time Division Multiplexed (TDM) resource blockage.
2308
Selected codec mismatch
Codec no longer supported.
2309
Drop call codec mismatch
Drop call, codec mismatch.
2310
Invalid regions
Invalid region
2311
Invalid codec region
Invalid codec region
2312
No DSP resource
No Digital Signal Processor (DSP) resource
2313
No free list channels
No channels on free list
2314
No channel resources
No channel resources
2315
Not enough capacity
Not enough prowler capacity
2316
Event
Data 1
Event
Data 2
network
region
of the
endpoint
preferred
desti_
nation
network
region
Drop call, no bandwidth for ept’s codec.
23172328
not assigned
2329
No BW, prowler <--> IP ept
No available bandwidth channel resources from the endpoint
to the necessary resources. The call fails.
2330
No BW, prowler <--> prowler
No bandwidth channel resources between processors.
2331
No VOIP channel, PN <--> PN
No Voice Over IPchannel resources between port networks.
1 of 4
Issue 3 February 2007
271
Denial Events
Table 56: Connection Manager denial events (2300 - 2399) 2 of 4
Event
Type
Event Description, as it
appears on the event log
Explanation
2332
No BW, prowler <--> MG
No bandwidth channel resources between processor and
media gateway.
2333
No VOIP channel, PN <--> MG
No Voice Over IPchannel resources between port network
and media gateway.
2334
No channel resources
No available bandwidth to access the necessary resources.
The call fails
2335
RejReqMode-no common
mode
Deny inbound RM, not compatible with modes received in
request.
2336
RejReqMode-no common
mode
Deny inbound RM, cannot arrive at common profile.
2337
RejReqMode-no modes rcvd
Deny inbound RM, no data modes were received in request.
2338
RejReqMode-not 2 connectd
Deny inbound RM, there are not two pt_conn parties on call.
2339
RejReqMode-no common
mode
Deny inbound RM dirip ept, no common profile.
2340
T38Fail-no voip resources
Insufficient voip resources.
2341
T38Fail-far end timeout
Far-end timeout.
2342
T38Fail-near end timeout
Near-end timeout.
2343
ReqMode reject received
Time Division Multiplexed (TDM)/HP connection.
2344
ReqMode reject received
DIRIP connection.
2345
ReqMode release received
Request release received, Time Division Multiplexed (TDM)/
HP connection.
2346
ReqMode release received
Request release received, DIRIP connection.
2347
Rej inc T38OLC, not seq'd
Not in sequence, dropping call.
2348
Rej inc T38OLC, no common
Incompatible mode, Time Division Multiplexed (TDM)/HP
connection. Dropping call.
2349
Rej inc T38OLC, no common
Incompatible mode, DIRIP connection. Dropping call.
2350
Rej inc T38OLC, idle state
Deny inbound T38 OLC - IDLE state. Dropping call.
2351
Failed Xoip Attempt
XOIP failed attempt, invalid call type.
2352
Failed Fax Relay Xoip
Fax Relay XOIP failed attempt.
2353
Failed Modem Relay Xoip
Modem Relay XOIP failed.
2354
T38Fail-no dsp resources
Insufficient Digital Signal Processor (DSP) resources.
2355
IGAR trunk limit exceeded
Attempt to exceed the number of trunks allowed for
Inter-Gateway Alternate Routing (IGAR) in this network
region.
Event
Data 1
Event
Data 2
network
region
(from)
network
region
(to)
2 of 4
272 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Denial Event Tables
Table 56: Connection Manager denial events (2300 - 2399) 3 of 4
Event
Type
Event Description, as it
appears on the event log
Explanation
2356
All IGAR managers in-use
All Inter-Gateway Alternate Routing (IGAR) manager are in
use.
2357
Failed Fax Prowler
Prowler reports chl could not go to FAX mode.
2358
Failed Fax Media Gateway
Media Gateway reports chl could not go to FAX mode.
2359
Event
Data 1
Event
Data 2
Received G.726 dynamic RTP payload type from the far - ,
conflicts with existing dynamic RTP payload types (fixed and
encryption)
2360
RejReqMode-no common
mode
Deny inbound RM - no common profile. Already in a
sequence, have a collision.
2361
RejStartT38-no common
Cannot start RM sequence -no ocommon profile between ept
and regn/hw (VOIP detected a fax tone)
2362
Multimedia OLC rejected
Reject inbound multimedia Open Logical Channel (OLC) due
to state mismatch.
2363
Multimedia OLCReject
received
Multimedia reject outbound Open Logical Channel (OLC).
A video endpoint is denying Communication Manager’s
attempt to establish video.
2364
BCF Rcvd-diff bandwidth
Different confirming bandwidth than what is stored
2365
RejStartT38-not in rgn/hw
Cannot start RM sequence - T38 is not supported in region/
hw intersection (VOIP detected a fax tone)
2366
RejAckT38-no modes in msg
Deny inbound RM Acknowledgment. No data modes were
received in the request. (Fast Request Mode - dcap ptr is
null)
2367
RejAckT38-no modes in msg
Deny inbound RM Acknowledgment. No data modes were
received in the request. (Fast Request Mode - no modes
received)
2368
RejAckT38-not common
Deny inbound RM Acknowledgment. Mode received in Ack
was not common (Fast Request Mode - TDM case)
2369
RejReqMode-fast collision
Deny inbound RM Acknowledgment. There is a collision,
already in T38 sequence (Fast Request Mode case)
2370
VOIP inactivity has been detected by this media processor
channel. Call will be torn down.
2371
IGC:Exch no common codec
Codec intersection between master and slave ends is null;
will reattempt to establish IGC with all inter-region codecs if
first attempt fails
2372
MG link needs encryption
Hardware codecs do not match. There is a non-encrypted
H.248 signaling link on the media gateway and a codec set
with only encrypted codecs. Encryption keys cannot be left
exposed on unencrypted signaling link.
2373
No Video BW available
No bandwidth is available for video
2374
No available BW for priority
video calls.
A priority video caller was not able to get bandwidth to make
a video call.
3 of 4
Issue 3 February 2007
273
Denial Events
Table 56: Connection Manager denial events (2300 - 2399) 4 of 4
Event
Type
Event Description, as it
appears on the event log
2375
23762399
Explanation
Event
Data 1
Event
Data 2
OLC mismatch, master/slave mismatch
not assigned
4 of 4
Dial Plan Manager Denial Events
Event Types 2400 - 2406 show Dial Plan Manager denial events, as listed in Dial Plan Manager
denial events (2400 - 2406) on page 274.
Table 57: Dial Plan Manager denial events (2400 - 2406)
Event
Type
Event Description, as it
appears on the event log
Explanation
2400
UDP: too many conversions
Digit conversion counter exceeded.
2401
UDP: node-rte pat blank
Node number route pattern is blank.
2402
UDP: ENP code blank
ENP numbering prefix is blank.
2403
Loc Digits Size incorrect
Location Prefix digits size is not n, where the UDP form’s
matching row, Insert digits field is Ln.
2404
Var-in-Vec No adm for VAC
Variable Access Code (VAC) in Variables in Vector Table not
administered.
2405
Var-in-Vec Invalid digit
Invalid digit entered, or Feature Access Code corrupted from
call_p to dp_mgr.
2406
Unadministered annc ext
Unadministered announcement extension for a location.
Event
Data 1
Event
Data 2
Data Manager Denial Events
Event Types 3001 - 3003 show Data Manager denial events, as listed in Table 58: Data Manager
274 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Denial Event Tables
generated Denial Events (3001 - 3003) on page 275.
Table 58: Data Manager generated Denial Events (3001 - 3003)
Event Type
Event Description, as it appears on the event log
Explanation
3001
Bridge in use
indicate PR_BRIDGE object is in use
3002
Button in use
PR_BUTTON/PR_BTNTTI object is in use
3003
Station/Trunk in use
one of the station/trunk PREC object is in use
3004
Team Group in use
the PR_TEAM object is in use
Dial Access Plan Denial Events
Event Types 3101 - 3200 show Dial Access Plan denial events, as listed in Dial Access Plan
denial events (3101 - 3200) on page 275.
Table 59: Dial Access Plan denial events (3101 - 3200)
Event
Type
Event Description, as it
appears on the event log
Explanation
Event
Data 1
3101
DCS invalid PBX/Mach/Node
Distributed Communication System (DCS) requires Trunk
Group pbx-id, Signal Group Mach-id, or AAR Analysis node
number.
3102
DCS no msg buffer avail
No Distributed Communication System (DCS) message buffers
are available.
3103
DCS Station LWC mis-admin
Distributed Communication System (DCS) station Leave Word
Calling is mis-administered.
3104
DCS Trunk Group mis-admin
Distributed Communication System (DCS) trunk-group is
mis-administered.
3105
DCS invalid PBX/Mach/Node
Distributed Communication System (DCS) requires Trunk
Group pbx-id, Signal Group Mach-id, or AAR Analysis node
number
31063200
not assigned
Event
Data 2
Issue 3 February 2007
275
Denial Events
Meet Me Conference Denial Events
Event Types 3201 - 3299 show denial events generated by the Meet Me conference process, as
listed in Meet Me Conference denial events (3201 - 3299) on page 276.
Table 60: Meet Me Conference denial events (3201 - 3299) 1 of 2
Event
Type
Event Description, as it
appears on the event log
Explanation
3201
Meet-Me Access chg TMO
Meet-me security/access change time-out.
3202
Invld Num Digits MM Acc.
Meet-me security/access change received too many digits.
3203
MM Extention not valid
Meet-me security/access change not a valid extension.
3204
MM Access Chg Not a VDN
Meet-me security/access change not a Vector Directory Number
extension.
3205
MM Invalid Access Entered
Meet-me security/access change invalid security/access code.
3206
MM Access Obj/SAT Busy
SAT window with Meet-me security/access code or obj is busy
and cannot make changes via AC.
3207
Merge Meet-me Conf call
User tried to merge to a existing Meet-me conference call and
mmcon _val failed to validate the merge.
3208
Serv Observ Meet-me VDN
User tried to service-observe a Meet-me conference call and
the service observing route failed.
3209
Meet-me Conf call full
Meet-me conference total party number is over limit.
3210
Wrong MM Acc. code dialed
Party failed to dial correct Meet-me conference access.
3211
Chg Station no Cons/Perm
Meet-me security/access change the station extension does not
have console permissions.
3212
VDN not a meetme type
Vector Directory Number (VDN) is not a meetme type.
3213
MM Invalid Conf Ctrlr Sta
Station extension does not match controller extension.
3214
MM Inv Trk not Remote Acc
Trunk User ID not allowed as a controller extension.
3215
MM Invalid Station Type
Invalid station type of calling extension.
3216
Conf/Transfer 2 Meet-me
Conference/or transfer 2 Meet-me conference call.
3217
MM Abbrev Dial Invalid
Cannot use abbreviated dialing.
3218
Error in EMMC route dgt
Error retrieving Enhanced MeetMe Conferencing (EMMC)
routing digits.
3219
Empty EMMC route digits
Empty Enhanced MeetMe Conferencing (EMMC) routing digits.
3220
Exceed EMMC active conf
Exceeded Enhanced MeetMe Conferencing (EMMC) active
conference.
3221
Exceed EMMC license ports
Exceeded Enhanced MeetMe Conferencing (EMMC) license
ports.
Event
Data 1
Event
Data 2
1 of 2
276 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Denial Event Tables
Table 60: Meet Me Conference denial events (3201 - 3299) 2 of 2
Event
Type
Event Description, as it
appears on the event log
Explanation
3222
Exceed EMMC party limit
Exceeded Enhanced MeetMe Conferencing (EMMC) party limit.
3223
Event
Data 1
Event
Data 2
Enhanced MeetMe Conferencing (EMMC)-no new vector proc
3224
Add meet-me user/whsp pg
32253299
not assigned
Can’t add meet-me party if whisper page is active
2 of 2
LSP Denial Events
Event Types 3300 - 3399 show LSP-generated denial events, as listed in LSP denial events
(3300 - 3399) on page 277.
Table 61: LSP denial events (3300 - 3399)
Event
Type
Event Description
Explanation
Event
Data 1
Event
Data 2
3300
IP RRJ-LSP not active
Local Survivable Processor (LSP) is not yet active.
NULL
sending LSP’s
IP address
3301
IP RRJ-LSP not admin
Local Survivable Processor (LSP) has not been
administered.
NULL
sending LSP’s
IP address
3302
IP RRJ-Version mismatch
Local Survivable Processor has not been
administered.
NULL
sending LSP’s
IP address
3303
IP RRJ-GK reg with GK
Local Survivable Processor (LSP)/ESS is
attempting to register with another LSP/ESS.
3304
IP RRJ-LSP's MG not admin
Local Survivable Processor’s serial number does
not match any administered gateway.
NULL
sending LSP’s
IP address
3305
IP RRJ-LSP memory size
Local Survivable Processor’s Memory
Configuration (DRAM) is inadequate to handle
translations from the main.
NULL
sending LSP’s
IP address
33063399
not assigned
(keyword)
Issue 3 February 2007
277
Denial Events
Data Error Events
Event Types 3400 - 3499 show data error-generated denial events, as listed in Data Error denial
events (3400 - 3499) on page 278.
Table 62: Data Error denial events (3400 - 3499)
Event
Type
Event Description, as it
appears on the event log
Explanation
3400
Error in vector data
Bad step type.
3401
Invalid vector step type
Bad step type.
3402
Companding mode mismatch
Companding mode mismatch.
3403
Bad date in MCT record
Bad Malicious Call Trace date.
3404
Bad date in MCT record
Bad Malicious Call Trace date.
3405
Unicode cus file not read
Unicode translation read error. Entire customer file not read.
3406
Error in Unicode cus file
Unicode translation read error. Error found in customer file.
3407
Unicode ava file not read
Unicode translation read error. Entire Avaya file not read.
3408
Error in Unicode ava file
Unicode translation read error. Error found in Avaya file.
3409
Usr-def cus file not read
User-defined translation read error 3409. Entire custom_ file
not read.
3410
Err in User-def cus file
User-defined translation read error (3410). Error found in
custom_ file.
3411
Usr-def ava file not read
User-defined translation read error (3411). Entire avaya_ file
not read.
3412
Err in User-def ava file
User-defined translation read error (3412). Error found in
avaya_ file.
34133500
not assigned
Event
Data 1
278 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Event
Data 2
Denial Event Tables
Contact Closure Denial Events
Contact Closure Denial Event Types 3501 - 3503 show successful feature activations and are
kept as historical data, as listed in Contact Closure denial events (3500 - 3503) on page 279.
Table 63: Contact Closure denial events (3500 - 3503)
Event
Type
Event Description
Explanation
3500
not assigned
3501
Relay OPEN
Contact closure OPEN.
3502
Relay CLOSE
Contact closure CLOSE.
3503
Relay PULSE
Contact closure PULSE.
(keyword)
Event
Data 1
Event
Data 2
Issue 3 February 2007
279
Denial Events
ESS Denial Events
Event Types 3600 - 3604 are ESS-generated denial events, and listed in ESS denial events
(3600 - 3604) on page 280.
Table 64: ESS denial events (3600 - 3604)
Event
Type
Event Description, as it
appears on the event log
Explanation
Event
Data 1
Event Data 2
3600
IP RRJ-ESS not admin
ESS has not been administered.
NULL
sending ESS’s IP address
3601
IP RRJ-ESS obj not init
EssMgr_ptr has not been initialized.
NULL
sending ESS’s IP address
3602
IP RRJ-ESS bad SID sent
ESS sent a bad System ID.
SID
sending ESS’s IP address
ESS had a failure from ParseNsdLSPInfo
method.
NULL
sending ESS’s IP address
3603
3604-
not assigned
280 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Chapter 3: LEDs
LEDs are important status indicators for technicians during on-site installation, maintenance,
troubleshooting, and repair. They encompass three major areas: Alarms, Testing, and Usage
Activity. Some LEDs are specialized to support specific procedures such as removing the
S8300 Media Server. When alarms or problems occur, the LEDs indicate that attention is
needed. LEDs are not suitable for conveying detailed diagnostic information. Further diagnosis
or troubleshooting is supported by software-based solutions that can provide detailed test
explaining the error condition.
This chapter describes the meanings of the LEDs on system components, the alarm levels they
indicate, and includes the following topics:
●
Alarm levels
●
Terminal alarm notification
●
Attendant Console LEDs
●
Circuit Pack LEDs
●
Expansion Interface Circuit Pack LEDs
●
Maintenance Circuit Pack LEDs
●
DS1/UDS1 (TN767/TN464) Circuit Pack LEDs
●
DS1C (TN574/TN1654) Circuit Pack LEDs
●
Switch Node Interface LEDs
●
Tone-Clock Circuit Pack LEDs
●
Maintenance/Test Circuit Pack LEDs
●
Avaya Ethernet Switch LEDs
●
UPS LEDs
●
IPSI LEDs
●
650A Power supply LEDs
●
655A Power Supply LEDs
●
Duplication Memory Board LEDs
●
S8300 Media Server LEDs
●
S8500 Media Server LEDs
●
S8700 Media Server LEDs
●
S8710 Media Server LEDs
●
G250/G350 and Media Module LEDs
●
G700 and Media Module LEDs
Issue 3 February 2007
281
LEDs
Alarm levels
During normal operations, software or firmware may detect error conditions concerning specific
Maintenance Objects (MOs). The system automatically attempts to fix or circumvent the
problem. The alarms are classified depending on their effect on system operation:
●
●
●
●
●
Major alarms — Failures that cause critical degradation of service. These alarms require
immediate attention.
Minor alarms — Failures that cause some degradation of service, but do not render a
crucial portion of the system inoperable. A minor alarm typically affects a few trunks or
stations or a single feature. Minor alarms require attention, but the consequences are not
immediate.
Warning alarms — Failures that cause no significant degradation of service or failures in
equipment. These failures are not reported to INADS or the attendant console.
On-Board problems originate in the circuitry on the alarmed Media Module or circuit pack.
Off-Board problems originate in a process or component that is external to the Media
Module or circuit pack.
Alarms are communicated by entries in the alarm log and the turning on of LEDs located on the
attendant console, on all circuit packs, on the server, on the Ethernet switch if there is one, and,
optionally, on customer-designated voice terminals.
Terminal alarm notification
Terminal alarm notification is an optional feature which displays several types of alarms on
voice terminals with administered feature buttons or the attendant console. A maximum of 10
digital and/or hybrid voice terminals may be used.
When an alarm occurs, the green status LED associated with the assigned button will be turned
on in a steady state. The LED may be turned off by pressing the button associated with the lit
alarm LED. If the LED is turned off and the alarm has not been resolved by the time
maintenance software reschedules testing, the green status LED will resume its steady state.
The following alarms are displayed:
ac-alarm
Administered Connection alarm: A locally administered connection
(ADM-CONN) has an active major, minor, or warning alarm.
pr-awu-alm
Auto Wakeup Journal Printer alarm: The automatic wakeup journal printer has
an active major, minor, or warning alarm.
282 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Attendant Console LEDs
off-bd-alarm
DS1 or ATM Facility alarm: An off-board major, minor, or warning alarm is
active on a DS1-BD, UDS1-BD, or ATM-TRK board.
trk-ac-alm
Facility Access alarm: The facility access trunk test feature is activated.
major-alrm
Major alarm: The system has logged a major alarm.
mj/mn-alrm
Major/Minor alarm: The system has logged a major or minor alarm.
pr-pms-alm
The Property Management System (PMS) printer has an active major, minor, or
warning alarm.
rs-alert
Reset-Alert: reset system 2 has been performed.
cdr1-alrm
Call Detail Recording alarm: The primary CDR link has an active major, minor,
or warning alarm.
cdr2-alrm
Call Detail Recording alarm: The secondary link has an active major, minor, or
warning alarm.
pr-sys-alm
System Printer alarm: The System Printer (SYS-PRNT) has an active major,
minor, or warning alarm.
pms-alarm
The Property Management System has an active major, minor, or warning
alarm.
Attendant Console LEDs
The attendant console has two red LEDs labeled “ALM” and “ACK.” The ALM LED lights
steadily when there is a major or minor alarm at the switch cabinet. The ACK LED lights steadily
if the alarm has been successfully reported. If the system is unable to report the alarm, the LED
flashes. This signals the attendant to call the Avaya alarm receiving system and report the
alarm.
Circuit Pack LEDs
Typically, each circuit pack has three LEDs on the front panel which are visible from the front of
the carrier. There are some exceptions to this (for example, the DS1 and IPSI circuit packs
which are covered later in this section). On most circuit packs, the LEDs indicate the following
when lit (Table 65: LED indicators on page 284). Exceptions to these indications are explained
in subsequent sections.
Issue 3 February 2007
283
LEDs
Table 65: LED indicators
LED
Color
State
Interpretation
Red
Alarm
The system detected a fault on this circuit pack. The alarm log should
contain an on-board alarm for this circuit pack or one of the maintenance
objects associated with it. The red LED is also lit briefly when a circuit pack
is inserted or reset. If the circuit pack passes its initialization tests, the LED is
turned off. If a fault is detected, the LED remains lit.
Green
Testing
The system is currently running tests on this circuit pack as part of
background maintenance or demand testing. This LED is also lit briefly
during initialization tests when a circuit pack is inserted or reset.
Yellow
Busy
The circuit pack is currently in use by the system.
This section includes LED interpretation on the following circuit packs:
●
LED alarms without Alarm Log entry or with Error Type 1
●
Expansion Interface Circuit Pack LEDs
●
Maintenance Circuit Pack LEDs
●
DS1/UDS1 (TN767/TN464) Circuit Pack LEDs
●
DS1C (TN574/TN1654) Circuit Pack LEDs
●
Switch Node Interface LEDs
●
Tone-Clock Circuit Pack LEDs
●
IPSI LEDs
LED alarms without Alarm Log entry or with Error Type 1
Whenever the system or a part of the system is reset, every affected circuit pack will briefly light
their red and green LEDs as they are initialized. Upon power up of a newly installed system,
several alarm indicators may remain lit until the circuit packs are administered. These alarms
should be ignored until administration is completed.
Boards with a “P” suffix have downloadable firmware. If such a board has both its green and
yellow LEDs lit simultaneously, a download may be in progress and the board will not appear to
be recognized. Enter either the SAT command status firmware download or
status firmware download last to verify this condition.
284 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Circuit Pack LEDs
After a circuit pack has been initialized, a red LED should be accompanied by an alarm in the
alarm log. A single fault can sometimes light alarm LEDs on several circuit packs, as in the
following examples.
●
●
●
●
●
●
A TDM bus problem may cause several port circuit packs to display red LEDs.
A Maintenance circuit pack can prevent an Expansion Interface (EI) circuit pack from
initializing.
Extensive interactions in the Center Stage Switch (CSS) can cause multiple alarms from
single faults in DS1C, SNI and SNC circuit packs and fiber links.
Tone-Clock problems may cause other circuit packs to report alarms.
Optical fiber cables which are not connected correctly may cause several circuit packs to
alarm.
Packet-bus faults can cause several port circuit packs to display red LEDs.
If a circuit pack has had at least five minutes to be initialized and the red LED is lit without an
associated alarm in the alarm log, the circuit pack may not be in communication with the
system. This may also be the case when a circuit pack is properly administered and present in
its slot, but there is an Error Type 1 logged against it. To determine whether this is so, proceed
as follows:
1. Enter the list configuration board location command. If the system does not
detect the circuit pack, this command will return one of the following:
identifier not assigned
no board
If the documentation for the associated maintenance object gives no special instructions for
this situation, go to the next step.
2. Check the hardware error log for TONE-BD or TDM-BUS errors with the display errors
command. If the board has a “P” suffix, execute the reset board location command.
Otherwise, execute the test tdm and test tone-clock commands. Use the
appropriate maintenance procedures to resolve any identified faults. If this does not resolve
the problem, go to the next step.
3. Reseat the suspect circuit pack.
! CAUTION:
CAUTION:
This procedure can cause a partial or total service outage. Consult the
documentation for the associated maintenance object before proceeding.
Observe any precautions and procedures described above.
4. Inspect the backplane connectors for bent pins.
5. If the system seems to be functioning correctly, but the circuit pack in question will not
communicate with the system, replace the circuit pack.
Issue 3 February 2007
285
LEDs
Expansion Interface Circuit Pack LEDs
The Expansion Interface (EI) TN570 circuit pack has the standard red, green, and yellow LEDs.
The red and green LEDs have the traditional meaning, where red indicates an alarm condition
and green indicates testing in progress.
The yellow LED displays various flashing patterns to provide status information for isolating
faults in the fiber link and other components connected to the fiber link. Table 66: Expansion
Interface yellow LED flashing codes on page 286 illustrates the EI yellow LED states.
Table 66: Expansion Interface yellow LED flashing codes
LED
on
LED
off
Condition
0.1 sec
0.1 sec
Fiber Out-of-Frame. This state indicates a failure of test #989. This may
be caused by absence of the opposite end EI or Switch Node Interface
(SNI), a broken or missing fiber, or a missing lightwave transceiver on
either endpoint.
0.5 sec
0.5 sec
In Frame — No Neighbor. This state corresponds to a failure of test #237,
usually due to a failure of this EI or of the EI or SNI at the other end of the
fiber.
2 sec
0.2 sec
EI Active. This is the normal state of an active EI that is an archangel of
an EPN.
solid on
EI Active. This is the normal state for an active EI that is not an EPN
archangel. These include EPN EIs connected to other EPN EIs in direct
connect configurations, and EIs located in the processor port network.
solid off
EI Standby. This is the normal state for a standby EI in systems with a
duplication option.
Maintenance Circuit Pack LEDs
TN775D PN maintenance circuit packs have seven LEDs on their front panels. The top three
LEDs are the standard group of red, green, and yellow, and indicate the status of the circuit
pack. The green LED on TN775Ds blinks faintly once per second, indicating continual
self-testing.
286 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Circuit Pack LEDs
The second group of three LEDs, labeled “ALARMS”, reflects maintenance conditions
throughout the system and indicates alarms reported against other components, as shown in
Table 67: Maintenance circuit pack LED interpretation.
Table 67: Maintenance circuit pack LED interpretation
LED
Color
State
Level/
Function
Interpretation
Red
flashing
MAJOR
Major alarm against a component in the same cabinet.
solid
MAJOR
Major alarm against a component in another cabinet.
solid
MINOR
Minor alarm against a component in another cabinet.
flashing
MINOR
Minor alarm against a component in the same cabinet.
flashing
WARNING
Warning alarm against a component in the same
cabinet.
solid
WARNING
Warning alarm against a component in another
cabinet.
Green
on
ACK
Acknowledged. The alarm has been reported.
Red
on
EMERGENCY
TRANSFER
Emergency transfer has been invoked. This occurs
upon power-up as well as during disabling failures.
Yellow
These LEDS are illustrated Figure 1: TN775 circuit pack LEDs on faceplate.
Issue 3 February 2007
287
LEDs
Figure 1: TN775 circuit pack LEDs on faceplate
Figure notes:
1. Alarm LED (Red)
2. Test LED (Green)
3. Busy LED (Yellow)
4. Latch pin
5. Locking lever
DS1/UDS1 (TN767/TN464) Circuit Pack LEDs
The DS1 (TN767) and UDS1 (TN464) circuit packs have four status LEDs on the faceplate in
addition to the three standard faceplate LEDs. These four status LEDs are associated with the
120A Channel Service Unit (CSU) Module which can be connected to the TN767 or TN464
circuit pack through the I/O connector panel on the back of the port carrier.
The TN464 circuit pack, combined with the 120A CSU module or the 401A T1 sync splitter,
forms an Integrated CSU (I-CSU).
TN767/TN464 LEDs shows the DS1/UDS1 circuit pack LEDs.
288 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Circuit Pack LEDs
Figure 2: TN767/TN464 LEDs
Test 1 Failure: Solid red on only this LED indicates faulty DS1 board.
Test 2 Failure: Flashing red on status 1 LED indicates either
faulty DS1 board, faulty wiring between the
DS1 board and the 120A, or a faulty 120A.
Test 3 Failure: Flashing red on status 2 LED indicates faulty 120A.
S
T
A
T
U
S
1
Steady green on status 3 LED indicates all tests passed.
2
3
4
S
I
E
O
E
M
S
<
E
I
S
O
h1dfcsu5 LAO 072606
See Table 68: TN767/TN464 circuit pack LED interpretation for a guide to interpreting LEDs on
the TN767 and TN464 circuit packs. In the table, DS1 refers to both DS1 and UDS1.
Note:
Note:
On the TN767/TN464 circuit pack faceplate, loopback indications share the same
LEDs as alarm indications. Loopback indications take priority over alarm
indications. Disregard alarm indications while loopback indications are active. For
example, if the status 2 LED is yellow, indicating a loopback problem, disregard
status 3 and status 4 alarm indications.
Table 68: TN767/TN464 circuit pack LED interpretation 1 of 3
LED
Color
Condition
Solid red only
on top
circuit-pack
LED
Red
Faulty DS1 circuit pack
STATUS 1
Green
Far end line loop back
(LLB) active
Notes
A near end DS1 circuit
pack-initiated line loop back is
active at the far end CSU.
1 of 3
Issue 3 February 2007
289
LEDs
Table 68: TN767/TN464 circuit pack LED interpretation 2 of 3
STATUS 2
STATUS 3
Yellow
Bit error rate (BER)
alarm active
Error rate from the network
exceeds 10-4.
Solid red
Loss of signal (LOS)
from DS1 circuit pack
If the DS1 circuit pack fails to send
a signal to the CSU module, the top
LED on the circuit pack will turn on
red.
Steady
flashing red
Failed equipment loop
back (ELB) test
Flash rate is .5 seconds on and off.
This could indicate either a bad
DS1 circuit pack where the problem
is between the circuit pack
loopback and the edge of the circuit
pack, bad wiring between the DS1
and the CSU module, or a bad
CSU module.
Off
Normal operation
Green
CSU repeater loop back
(RLB) or ELB active
Yellow
Near end CSU module
LLB or PLB active
Solid or
randomly
flashing red
Span alarm indicated by
STATUS 3 or STATUS 4
is active
Flashing
red
Failed RLB test
Off
Normal operation
Green
Pulses present
If this LED is off, the STATUS 4
LED will be red, indicating LFA or
LOS from the span. Either STATUS
3 or STATUS 4 will always be on if
a 120A is present. Pulses from the
span might be intermittent. In this
case, the LED might go off for
several seconds, then turn back on.
During the time it is off, other status
LEDs will indicate alarms.
Yellow
Bipolar violation (BPV)
received from span
This LED flashes each time a BPV
is received from the network. B8ZS
BPVs are not reported.
Red
CRC or frame bit error
from span
This LED flashes each time a CRC
or bit error received from the
network.
Flash rate is .5 seconds on and off.
Replace the 120A.
2 of 3
290 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Circuit Pack LEDs
Table 68: TN767/TN464 circuit pack LED interpretation 3 of 3
STATUS 4
Off
No pulses
Triggers the STATUS 4 red LED.
Green
Alarm indication signal
(AIS) received from
span
Blue alarm, indicating equipment is
down on the far end.
Yellow
Remote frame alarm
(RFA) received from
span
This indicates that the far end
cannot frame on the DS1 circuit
pack’s signal.
Red
Loss of frame alignment
(LFA) from span
Off
Normal operation
3 of 3
Table 69: Facility Alarms, describes the facility alarms indicated by the LEDs.
Table 69: Facility Alarms 1 of 2
Alarm
Description
Cyclic Redundancy Check
(CRC) Errors
May be produced by marginal or faulty line repeaters, network
circuit terminating equipment (NCTE), noise on the
transmission line, or by the circuitry that generates the
framing pattern or CRC at the transmit end. Bit errors in a
DS1’s signal are detected via CRC errors when Extended
Super Frame (ESF) is used.
Loss of Frame (LOF) Alarm,
Red Alarm
Occurs when the near-end interface cannot frame up on the
DS-1’s signal. A red LED lights on D4-channel banks when
this alarm is on. A frequent cause is an incorrect setting of the
framing option at one end of the transmission facility or within
the network. This scenario will cause the LFA at both ends of
the transmission link. Other possible causes are an
intermittent cable, broken cable, and a rain-attenuated signal
(with microwave transmission facilities).
This alarm is tripped several seconds after detecting a
continuous loss of framing, and clears several seconds after
restoring the in-frame condition. The end of the span with the
LFA sends an RFA to the other end to indicate it cannot frame
on the other’s signal.
1 of 2
Issue 3 February 2007
291
LEDs
Table 69: Facility Alarms 2 of 2
Remote Frame Alarm (RFA)
Yellow Alarm
When received at the near end, shows that the far end is
unable to frame up on the signal sent by the near end. The
far-end interface is in an LFA state. A yellow LED lights on
D4-channel banks. Something is wrong with the part of the
transmission facility that transmits the DS1’s signal from the
near end to the far end. May be caused by a broken conductor
in the transmission cable wiring or within the network.
Loss of Signal (LOS) Alarm
Shows that there is no bipolar signal present at the receiver
input. Occurs in parallel with the LFA alarm. Usually caused
by cable-related problems such as a broken pair inside a
cable, an intermittent cable at a cross-connect point, or a
cable connector not completely seated.
AIS, Blue Alarm
Shows that maintenance activities are in progress and that
the out-of-service condition exists for that DS1 facility. The
alarm is recognized as a continuous stream of 1s with no
framing bit.
This alarm condition may be treated differently depending on
the particular network circuit terminating equipment (NCTE)
used. It may result in the NCTE automatically looping the
signal back to the switch. If the looped facility is providing
synchronization, then the synchronization subsystem must
detect that the facility is looped and deal with that condition.
Otherwise, synchronization problems will occur.
2 of 2
DS1C (TN574/TN1654) Circuit Pack LEDs
The TN574 and the TN1654 LEDs provide an indication of the state of the DS1 converter and
facilities.
Note:
Note:
DS1 converters are used exclusively with a Center Stage Switch (CSS).
TN574 circuit pack LEDs
Seven LEDs indicate the state of the DS1 converter (DS1C-BD) TN574 circuit pack and the
DS1 facilities. The top group has the standard red, green, and yellow LEDs. The red and green
LEDs have the traditional meaning, where red indicates an alarm condition and green indicates
testing in progress. The four green LEDs on the bottom indicate the status of the DS1 facilities
which is explained in the following section.
292 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Circuit Pack LEDs
The yellow LED indicates the state of the fiber interface, the fiber channel, and the DS1 channel
as listed in Table 70: DS1C yellow LED flashing states in order of priority.
Table 70: DS1C yellow LED flashing states
LED
on
LED
off
Condition
0.1 sec
0.1 sec
Fiber Out-of-Frame or Fiber Loss of Signal
0.5 sec
0.5 sec
In Frame, fiber channel down. The fiber channel communicating between
the DS1C and the other fiber endpoint (EI or SNI) is down.
1 sec
1 sec
In Frame, DS1 channel down. The channel between the two DS1Cs in the
DS1C complex is down.
solid on
DS1C active. This is the normal state for an active DS1C.
solid off
DS1C standby. This is the normal state for a standby DS1C in
critical-reliability systems (duplicated PNC).
DS1 Facility LEDs
There are four green LEDs below the three standard LEDs on the DS1C circuit pack which
indicate whether a receive signal is present for each of the four DS1 facilities. Figure 3: TN574
DS1 Converter circuit pack LEDs on page 294 shows which facility (A, B, C, or D) corresponds
to each LED. If a green LED is off, there is a Loss of Signal condition on the DS1 facility
associated with that LED. The presence of a signal does not guarantee that the signal is using
the correct framing format or line coding. An Alarm Indication Signal indicating that the opposite
end of the DS1C complex is out of service may be present.
Issue 3 February 2007
293
LEDs
Figure 3: TN574 DS1 Converter circuit pack LEDs
Figure notes:
1. Alarm LED (Red)
2. Test LED (Green)
3. Busy LED (Yellow)
4. STATUS LEDs
5. SPAN LEDs
TN1654 circuit pack LEDs
The TN1654 DS1C circuit pack has 11 LEDs on its faceplate as shown in Figure 4: TN1654
DS1C circuit pack on page 296.
The top three LEDs have the traditional meaning, where red indicates an alarm condition and
green indicates testing in progress. The red and green LEDs are also turned on during circuit
pack initialization. When the control link to the circuit pack is lost, the red LED is turned on to
indicate an alarm condition.
294 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Circuit Pack LEDs
The yellow LED indicates the state of the physical fiber interface, the Fiber Channel (link to EI or
SNI), the DS1 Control Channel (link to opposite DS1C circuit pack), and the S8700 Media
Server communications link in the following manner and order of priority. The yellow LED
remains on for longer periods of time as the DS1C complex becomes closer to being fully
operational.
1. If the fiber is Out of Frame or a Fiber Loss of Signal condition exists, the yellow LED will
flicker at a 5 Hz rate (on for 100 mS, off for 100 mS).
2. If the fiber channel is down (DS1 Converter circuit pack/fiber endpoint communications), the
yellow LED will flash at a 1 Hz rate (on for 500 ms, off for 500 ms).
3. If the DS1 control channel is down between the two DS1Cs in the DS1C complex, the
yellow LED will pulse at a 0.5 Hz rate (on for 1 second, off for 1 second).
4. If the S8700 Media Server communications link is down, the yellow LED will wink off every 2
seconds for 200ms (2 sec on, 200 msec off).
5. If all is well with the fiber interface and every communications channel, the yellow LED will
remain on continuously in a standard- or high-reliability system configuration. In
critical-reliability systems (duplicated PNC), an active DS1C circuit pack will have its yellow
LED on continuously, and a standby DS1C circuit pack will have its yellow LED off.
The next four LEDs on the TN1654 DS1C circuit pack are labeled STATUS LEDs and are for
future use. These LEDs will not be lit.
The bottom four LEDs on the TN1654 board are labeled SPAN LEDs. These LEDs indicate
whether a receive signal is present for each DS1 facility. If the facility is not administered, the
LED is not lit. The LED is lit amber if the facility is running alarm free. If the facility is detecting
either a red alarm (loss-of-signal or loss-of-frame), a yellow alarm (remote frame alarm) or a
blue alarm (AIS signal), the LED is lit red. The SPAN SELECT switch on the TN1654 faceplate
is for future use. Pushing the switch will have no effect on the board. See Figure 4: TN1654
DS1C circuit pack on page 296 for a view of the faceplate on the TN1654 DS1C circuit pack.
Issue 3 February 2007
295
LEDs
Figure 4: TN1654 DS1C circuit pack
.
INSET
0015_0 RBP 052396
Switch Node Interface LEDs
The Switch Node Interface (SNI) TN573 circuit pack has the standard red, green, and yellow
LEDs. The red and green LEDs have the traditional meaning where red indicates an alarm
condition and green indicates testing in progress.
The yellow LED displays various flashing patterns to provide status information useful in
isolating faults in the fiber link and other components connected to the fiber link.
296 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Circuit Pack LEDs
Table 71: Switch Node Interface (SNI) yellow LED flashing states illustrates the SNI yellow LED
states.
Table 71: Switch Node Interface (SNI) yellow LED flashing states
LED
on
LED
off
0.1 sec
0.1 sec
Fiber Out-of-Frame. This state indicates a failure of test #238, which may
be caused by the absence of the opposite end EI or Switch Node
Interface, a broken or missing fiber, or a missing lightwave transceiver on
either endpoint.
0.5 sec
0.5 sec
In Frame — No Neighbor. This state corresponds to a failure of test #237,
usually due to a failure of this SNI, or the EI or SNI at the opposite of the
fiber. This condition may also be due to a faulty Switch Node Clock
(SNC).
solid
on
Condition
SNI Active. This is the normal state for an active SNI.
solid
off
SNI Standby. This is the normal state for a standby SNI in systems with a
duplication option.
Tone-Clock Circuit Pack LEDs
The Tone-Clock circuit packs found in non-IPSI connected port networks have the standard red,
green, and yellow LEDs. The red LED has the traditional meaning. The yellow and green LEDs
flash in specific patterns to indicate the status of the circuit pack. The standby status applies
only to systems with the duplication option.
Maintenance/Test Circuit Pack LEDs
The TN771D maintenance/test circuit pack has the standard red, green, and yellow LEDs. The
red and green LEDs have the traditional meaning where red indicates an alarm condition, and
green indicates testing in progress.
The yellow LED can be off, on continuously, or flashing, depending on the mode of operation of
the TN771D and whether or not it has detected errors. The yellow LED is on steady when the
TN771D’s analog test port or digital test ports are being used to test trunks or line circuits. The
yellow LED is also used to indicate packet-bus status. Table 72: TN771D Maintenance/Test
Yellow LED States illustrates the maintenance/test yellow LED states as they apply to
packet-bus activity.
Issue 3 February 2007
297
LEDs
Table 72: TN771D Maintenance/Test Yellow LED States
LED State1
TN771D Mode
Condition
Solid off
Normal
The Maintenance/Test circuit pack detects no packet-bus
faults.
Solid on2
Normal
The Maintenance/Test packet-bus port has successfully
reconfigured the packet bus around a fault.
Flashing (1 Hz)
Normal
The Maintenance/Test packet-bus port is unable to
reconfigure the packet bus around a fault.
Solid off
Standalone3
The Maintenance/Test detects no packet-bus faults.
Solid on
Standalone
This condition cannot normally occur. The LED is always
either off or blinking in standalone mode.
Flashing (1 Hz)
Standalone
The Maintenance/Test packet-bus port detects a
packet-bus fault.
1. It takes 5 to 10 seconds for the yellow LED to respond to a change in the state of the packet bus.
2. Because the yellow LED on the Maintenance/Test circuit pack can also be on steady when the digital and
analog test ports on the circuit pack are in use, exact interpretation of the yellow LED may require that the
technician busy out the analog and digital test ports or examine the error and alarm logs for PKT-BUS
errors and alarms.
3. “Standalone” refers to the TN771D’s capability to operate autonomously as a troubleshooting aid.
298 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Avaya Ethernet Switch LEDs
Avaya Ethernet Switch LEDs
The Avaya Ethernet switch’s LEDs are shown in Figure 5: Avaya Ethernet Switch LEDs.
Figure 5: Avaya Ethernet Switch LEDs
51 52 53 54
55 56 57 58
1
2
3
4
5
6
7
8
9
Cajun P333T Switch
10 11 12
EXPANSION
SLOT
59 60 61 62
63 64 65 66
FIV
13 14 15 16
LNK COL Tx
17 18 19 20
Rx FDX FC Hspd LAG
21 22 23 24
SYS OPR PWR
LAG
LAG
LAG
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
CONSOLE
51 52 53 54
55 56 57 58
59 60 61 62
63 64 65 66
1
2
3
4
5
6
7
8
9
10 11 12
EXPANSION
SLOT
1
FIV
13 14 15 16
LNK COL Tx
17 18 19 20
Rx FDX FC Hspd LAG
21 22 23 24
2
SYS OPR PWR
3
ledl333t KLC 030602
4
Figure notes:
1. Ports in use
2. CPU boot status
3. Power
4. Lights if this module is the Cajun P33x stack master
The following three LEDs are the primary indicators:
●
SYS shows whether this module is the Cajun P330 stack master or not.
●
OPR shows CPU boot status.
●
PWR is lit when power is on.
For all other LEDs, refer to the quick start guide and user guide that came with the Avaya
Ethernet switch.
Issue 3 February 2007
299
LEDs
UPS LEDs
All Ethernet hubs and Uninterruptible Power Supplies (UPSs) have LEDs which indicate if they
are powered on or off. LEDs “on” imply the device is powered on. LED “off” implies the device is
powered down.
The Powerware front panel has the LEDs shown in Figure 6: UPS LEDs.
Figure 6: UPS LEDs
ledlups KLC 030102
1
2
8
7
3
4
5
6
Figure notes:
1.
2.
3.
4.
Normal mode indicator
Battery mode indicator
Bypass mode indicator
Test/Alarm reset button
5.
6.
7.
8.
Off button
On button
Bar graph indicators
Alarm indicators
When the Normal mode LED is steady green, it has power. If the LED is flashing, the UPS is in
standby mode.
For information on the other LEDs, refer to the UPS user’s guide that came with the Powerware
UPS unit.
300 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
IPSI LEDs
IPSI LEDs
There are four LEDs on the TN2312AP IP Server Interface (IPSI) faceplate, and five LEDs on
the TN2312BP IPSI faceplate. The top three are the standard LEDs found on most TN circuit
packs. The fourth LED indicates that the Tone/Clock function is active and imitates the
TN2182B Tone-Clock’s amber LED. The archangel flashes the yellow LED when active, 2
seconds on and 200 ms off. In addition, the TN2312BP has a fifth LED that shows the
emergency transfer control status.
Table 73: TN2312 IPSI LED States describes the LED status on an IPSI circuit pack.
Table 73: TN2312 IPSI LED States
LED Color
Condition
Red
Power up/Failure
Amber
Circuit pack is in use
Green
Maintenance diagnostics/testing
Amber
Clock function active
Red
TN2312BP - Emergency Transfer invoked
Figure 7: IPSI Display with static address shows the display on a TN2312AP IPSI circuit pack
which is using a static IP address.
Issue 3 February 2007
301
LEDs
Figure 7: IPSI Display with static address
1
2
CLK
S
E
R
V
I
C
E
ledlip1 KLC 030502
N
E
T
W
O
R
K
Figure notes:
1. IPSI using DHCP
2. IPSI has connectivity and a static IP address
Figure 8: IPSI Board Display using DHCP addressing shows the display on a TN2312AP IPSI
circuit pack which is using Dynamic Host Control Protocol (DHCP). This protocol dynamically
assigns TCP/IP addresses for use in an IP network and reduces the total number of IP
addresses required in enterprises.
302 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
IPSI LEDs
Figure 8: IPSI Board Display using DHCP addressing
1
CLK
2
3
S
E
R
V
I
C
E
ledsa01 KLC 030502
N
E
T
W
O
R
K
Figure notes:
1. Switch identifier
2. Cabinet number
3. IPSI has connectivity and a DHCP
address
Figure 9: IPSI display connectivity status explains the different connectivity states of an IPSI
circuit pack which is using DHCP.
Issue 3 February 2007
303
LEDs
Figure 9: IPSI display connectivity status
2
3
4
5
ledlipsi KLC 030502
1
Figure notes: IPSI connection status
Connectivity status
1
2
3
4
5
IPSI is connected to Avaya Ethernet switch
no
yes
yes
yes
yes
IPSI has an IP address
no
no
yes
yes
no
Laptop computer is connected to IPSI
services port
no
no
no
yes
yes
650A Power supply LEDs
Table 74: LED and alarm conditions shows the LED and alarm conditions for the 650A Power
Supply. Ring voltage and neon bus output do not activate alarm status.
Table 74: LED and alarm conditions 1 of 2
Condition
LED
status
Alarm
state
Fan alarm
Normal
Red off
Yellow on
Open
Normal
No input power
Red off
Yellow off
Closed
No input power
1 of 2
304 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
655A Power Supply LEDs
Table 74: LED and alarm conditions 2 of 2
Condition
LED
status
Alarm
state
Fan alarm
DC output not present (except Neon)
Red on
Yellow off
Closed
DC output not present
(except Neon)
Fan alarm
Red on
Yellow on
Closed
Fan alarm
2 of 2
655A Power Supply LEDs
The G650 media gateway normally has two 655A power supplies. Each has a set of five LEDs,
the function of which is indicated in Table 75: 655A Power Supply LEDs.
Table 75: 655A Power Supply LEDs
LED
Color
Function
1
Red
Failure of power supply or fan
2
Yellow
Status of power supply OK
3
Green
AC input voltage applied
4
Green
DC input voltage applied
5
Green
Power supply providing ring voltage
Normally, the ring voltage LED (#5) on the left power supply is ON and the ring voltage LED on
the right power supply is OFF. This changes momentarily when the ringer interchange test is
run. The ring voltage LED will only remain lit on the right power supply when there is a power
supply failure of the left hand supply or the left hand supply is removed.
LED indicators of serial bus commands to the power supply
Operation of the 655A power supply LED indicators for visual indication of serial bus commands
to the power supply for power supply shutdown and ringing shutdown are described below.
Issue 3 February 2007
305
LEDs
Power supply shutdown
The 655A power supply can be commanded off for a period of time selectable from 1 to 255
seconds. The intent is to allow a hard reset to the G650 chassis remotely. The yellow LED
indicating correct operation of the 655A power supply is on for normal power supply operation.
When the power supply is commanded off, the yellow LED blinks at a rate of 1 second on and
100ms off, indicating that the power supply is operational but commanded off by the serial bus.
Ringing shutdown
The left hand power supply in the G650 cabinet is the master ringer. If the master ringer fails,
ringing is transferred to the redundant power supply, if present. The red LED on the left hand
power supply turns on and the yellow LED turns off, indicating failure of the power supply.
The serial bus can command the ringer off for a period of 1 to 255 seconds. The purpose of this
command is to verify redundant ringer operation through the serial bus remotely from the G650
chassis. The red LED blinks at a rate of 1 second on and 100ms off, indicating that the power
supply is operational but commanded off by the serial bus.
A second command relating to ringer operation is the command to turn off the master ringer.
This command shuts down the master ringer and transfers control to the redundant power
supply. This command is used to permanently transfer ring voltage to the redundant power
supply through the serial bus, in order to resolve a problem with the master ringer. The red LED
blinks at a rate of 1 second on and 100ms off, indicating that the power supply is operational but
commanded off by the serial bus.
Duplication Memory Board LEDs
!
WARNING:
WARNING:
The DAJ1, DAL1, and DAJ2 Duplication Memory boards are not interchangeable.
The DAJ1 only functions in an S8700 Media Server. The DAL1 functions in an
S8710 Media Server and an S8720 Media Server with standard configuration.
The DAL2 functions in an S8720 Media Server running Communication Manager
4.0 or later with the extra large configuration.
The Duplication Memory Board is a circuit board that plugs into the processor. It does not
"insert" from the maintenance perspective. There are no SAT screens or Linux commands for
administration of this board.
The Duplication Memory board has four LEDs which indicate the state of the fiber link and the
mode (transmit or receive) that the Duplication Memory board is currently programmed as. The
faceplate also has a cutout for the fiber optic transceiver.
Figure 10: DAJ1 Faceplate shows the DAJ1 faceplate and LEDs.
306 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Duplication Memory Board LEDs
Figure 11: DAL1/DAL2 Faceplate shows the DAL1/DAL2 faceplate and LEDs. "DALX" refers to
DAL1 and DAL2. They have the same faceplate except for the DAL designation.
Figure 10: DAJ1 Faceplate
LINE
RECEIVE
TRANS
LINK
STATUS
fpcmdaj1 LAO 082306
DAJ-1
DUP
MEMORY
The DAJ1 LED functions are:
●
Line -- Indicates the On/Off line status of the server. Green when on-line.
●
Receive -- Green when transceiver is in receive mode.
●
●
Trans -- Bi-color, red or green. The red LED is turned on at reset (power-up). Green when
transceiver is in transmit mode.
Link Status -- Green when a light signal is sensed on the fiber.
On the active server, the Trans LED will be green and the Receive LED will be dark. On the
standby server, the Receive will be green and the Trans LED will be dark.
Issue 3 February 2007
307
LEDs
Figure 11: DAL1/DAL2 Faceplate
TRANS
MODE
RECEIVE
MODE
LINK
SYNC
LINK
ACTIVE
fpcmdalx LAO 082306
DALX
DUP
MEMORY
The DAL1/DAL2 LED functions are:
●
Trans Mode -- Green when Duplication Memory board is enabled to transmit.
●
Receive Mode -- Green when Duplication Memory board is enabled to receive.
●
Link Sync -- Green when characters are received.
●
Link Active -- Green when a light signal is sensed on the fiber.
On the active server, the Trans Mode LED will be green and the Receive Mode LED will be
dark. On the standby server, the Receive Mode will be green and the Trans Mode LED will be
dark.
Also see System shutdown LEDs.
308 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
S8300 Media Server LEDs
Testing the Duplication Memory board LEDs
When testing the LEDs, the Duplication Memory board LED should blink according to the
following pattern:
1 second red, 1 second red off, 1 second green, 1 second green off
and so on for a total of one minute.
If the LED shows any of the following flashing patterns, an abnormal condition is indicated.
Table 76: Duplication memory board abnormal LED conditions describes the condition and
recommends actions to resolve it.
Table 76: Duplication memory board abnormal LED conditions
LED
Color
Behavior
Indication
Resolution
Red
Flashes on 1 second,
off 3 seconds
in a repeating pattern
The green element
is burned out
Replace the server.
Green
Flashes on 1 second,
off 3 seconds,
in a repeating pattern
The red element is
burned out
Replace the server.
LED remains off
continuously
The Duplication
Memory board is
not getting power,
or the server is
hung
If the server is hung, it should
automatically reboot itself. If it does
not, power it down and reboot it.
Flashed continuously
The server is hung
If the server is hung, it should
automatically reboot itself. If it does
not, power it down and reboot it.
Green or
Red
S8300 Media Server LEDs
Figure 12: S8300 Media Server
Issue 3 February 2007
309
LEDs
The S8300 Media Server has a total of 6 LEDs on the faceplate (Figure 12: S8300 Media
Server). It has the three standard, red, green, and yellow LEDs. See S8300 LED differences
from Media Modules for a detailed description of these LEDs. The three additional LEDs are the
"OK-to-Remove" LED and two Services Port LEDs.
“OK-to-Remove” LED
The fourth LED is the "OK-to-Remove" LED. The S8300 has a hard drive that must be shut
down prior to removal of the S8300. When a shutdown is in progress, the fourth LED will first
blink, then go steady. Once steady, the fourth LED indicates that the disk drive has been shut
down properly and the S8300 is ready to be removed. Follow standard Media Module removal
procedures after the green LED indicates that the disk drive has been properly shut down.
There are three different ways to properly shut down the S8300 before it is removed:
●
●
●
Press the shutdown button on the faceplate for 2-4 seconds.
Initiate the shutdown via the Web interface with a computer connected remotely on the
customer’s LAN.
Initiate the shutdown via the Web interface with a computer connected locally on the
S8300 using the Services Port on the faceplate of the S8300
Green or Yellow Services Port LEDs
One LED is located on the lower left side of the Services Port. This LED indicates the data rate
of the connection:
●
When green, the data rate is 10MB.
●
When yellow, the data rate is 100MB.
A second LED, located on the lower right side of the Services Port, indicates whether or not
data is being sent over the RJ45 jack. This LED serves as a visual status of the Services'
Ethernet interface (TX/RX).
S8300 LED differences from Media Modules
Certain behaviors of the traditional S8300 LEDs differ from the Media Modules because the
S8300 is a Media Server running Communication Manager.
●
●
Situations like “insanity” and IP concepts of “registered” through H.248 do not necessarily
apply to other Media Modules.
The red LED provides a major alarm indication. After startup, the red LED turns on
whenever a major alarm is present, and turns off whenever a major alarm clears. Since
the S8300 sees a major alarm whenever a G700 Media Gateway becomes unregistered,
the red LED turns on. If the Media Gateway subsequently becomes registered, the major
alarm clears, and the red LED turns off.
310 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
S8300 Media Server LEDs
Note:
Note:
For an S8300 configured as an LSP, the converse is true. If a G700 Media
Gateway registers with an LSP, a major alarm is generated, and the red LED
turns on. When the Media Gateway unregisters, the red LED turns off.
●
●
●
The red LED can be turned on by software to report an application or other error. The red
LED can also be turned on by a hardware watchdog that has not been cleared for at least
10ms, when the processing complex has ceased to function.
The green LED provides a self-testing and maintenance indication. For an S8300, the
software turns on the green LED when the Communication Manager application is
running. This is important to know when the S8300 is used in the Local Survivable
Processor (LSP) configuration and no gateways or IP endpoints are registered with it.
The yellow LED provides active “in use” indication. For an S8300, the software turns on
the yellow LED during system startup, and turns off the LED during shutdown. During
normal call processing operation, the yellow LED turns on whenever a G700 Media
Gateway, an IP station, or an IP console registers with the S8300. Likewise, it turns off
when none of the IP endpoints are registered.
Table 77: Major alarm (RED LED) through Table 81: ENET Link/Activity (GREEN LED)
illustrate the states of S8300 LEDs.
Table 77: Major alarm (RED LED)
Major alarm
Indicator
Power on Reset
On
BIOS Boot
On
OS and SW Boot
On
System Up
Off - SW
H.248 Registered
Off - SW
Shutdown in Progress
On
Shutdown Complete
On
Issue 3 February 2007
311
LEDs
Table 78: Test – Communication Manager status (GREEN LED)
Test – To Be Defined
Power On Reset
Off
BIOS Boot
Off
OS and SW Boot
On-SW
System Up
Off - SW
Communication Manager Running
On
H.248 Registered
Off - SW
Shutdown in Progress
Off - SW
Shutdown Complete
Off
Table 79: Active – In Use (YELLOW LED)
Active – In Use
Power On Reset
Off
BIOS Boot
Off
OS and SW Boot
Off
System Up
SW
H.248 Registered
On-SW
Shutdown in Progress
Off-SW
Shutdown Complete
Off
Table 80: OK to Remove (GREEN LED) 1 of 2
OK to Remove
Power On Reset
Off
BIOS Boot
Off
OS and SW Boot
Off
1 of 2
312 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
S8300 Media Server LEDs
Table 80: OK to Remove (GREEN LED) 2 of 2
OK to Remove
System Up
Off
H.248 Registered
Off
Shutdown in Progress
1 Hz flash
Shutdown Complete
On
2 of 2
Table 81: ENET Link/Activity (GREEN LED)
ENET Link/Activity
Power On Reset
Off
BIOS Boot
N/A
OS and SW Boot
N/A
System Up
Link Status
H.248 Registered
Link Status
Shutdown in Progress
Unknown
Shutdown Complete
Off
S8300 LED lighting sequence
In general, S8300 LEDs light in order from top to bottom, then from left to right on the S8300
faceplate.
The following order applies during restart or boot of the S8300:
1. ALM - RED: lights up first then turns off.
2. TST - GREEN: lights up second then turns off.
3. ACT - YELLOW: lights up third then turns off.
4. OK To REMOVE - GREEN: lights up fourth then turns off.
5. LEFT LED in SERVICES jack - GREEN (10 MB link speed): lights up fifth then turns off.
6. LEFT LED in SERVICES jack - YELLOW (100 MB link speed): lights up sixth then turns off.
7. RIGHT LED in SERVICES jack - GREEN: lights up seventh then turns off.
Issue 3 February 2007
313
LEDs
S8500 Media Server LEDs
The S8500 Media Server has:
●
Five (5) LEDs on the front panel (Figure 13: S8500 front panel)
●
Four (4) LEDs on the back (Figure 14: S8500 rear panel)
Figure 13: S8500 front panel
1
2
3
4
5
disc
h3msfrnt LAO 070103
6
7
8
9
Figure notes:
1.
2.
3.
4.
5.
CD-ROM drive activity LED (green)
CD eject button
Power-control button
USB connector 1
USB connector 2
6. System-error LED (amber)
7. Hard disk drive activity LED
(green)
8. Reset button
9. Power-on LED (green)
The four LEDs on the S8500 back panel are shown in Figure 14: S8500 rear panel.
314 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
S8700 Media Server LEDs
Figure 14: S8500 rear panel
PCI
1
100-127 -, 3,0A, 50/60 Hz
200-240 -, 1,5A, 50/60 Hz
PCI 2
LINK TX/RX
133 MHz/64 Bit, 100 MHz/64 Bit
LINK TX/RX
1
2
h3msble2 KLC 082503
100-127 -, 3,0A,
200-240 -, 1,5A, 5
2
1
Figure notes:
1. Activity
2. Connection speed
●
LED is off: there is a 10 BASE-T active link.
●
LED is green: there is a 100 BASE-T active link.
●
LED is orange: there is a 1000 BASE-T active link.
S8700 Media Server LEDs
The S8700 Media Server has an LED called Active/Standby which indicates whether the server
is the active server or the standby server. The Active/Standby LED in the “on” state implies
active and in the “flashing” state implies standby. It flashes at the rate of 400 ms “on” and 600
ms “off” when in standby mode.
Issue 3 February 2007
315
LEDs
Figure 15: S8700 Media Server LEDs—Front and Back
1
2
SERVICE
1
3
4
ACTIVE
STANDBY
5
6
U2
7
8
5
4
3
2
9
LINE
RECEIVE
AVAYA
TRANS
LINK
STAT
DAI - 1
DUP
MEMORY
2
10
11
1
scdlled KLC 030502
Figure notes:
1.
2.
3.
4.
5.
Power
Configuration fault
Disk activity
Network activity (not used)
Service—configuration health (not
used)
6. Active or standby mode indicator
7. U2 (not used)
8. 4 NIC ports (the numbers indicate their
assigned Ethernet ports)
9. LEDs for the NIC ports
10. LEDs for fiber optic duplication
connectivity
11. Status LED (not used)
System shutdown LEDs
All server and Duplication Memory board LEDs are in the “off” state but still powered “on” when
the server is shut down.
Testing server LEDs
Using the Media Server Web interface, click Diagnostics > Test Server LEDs to ensure that
the Active/Standby LED on the server and the transmit LED on the Duplication Memory board
are controllable and not burned out, and that the server is not hung.
During the test, the Active/Standby LED on the Media Server and the transmit LED on the
Duplication Memory board should blink slowly (1 second on, 1 second off) for 1 minute.
To test the server LEDs:
1. On the main menu, under Diagnostics, click Test Server LEDs.
2. On the Test Server LEDs screen, click Test LEDs.
3. Observe the Active/Standby LED on the server and the transmit LED on the duplication card
to ensure they are blinking.
316 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
S8710 Media Server LEDs
Interpreting the test results
An abnormal condition is indicated if an LED shows any of the following flashing patterns.
LED color / behavior
Indication
Flashes red
The green element is either burned out or not controlled.
Flashes green
The red element is either burned out or not controlled.
Flashes between red
and amber
The green element is stuck on.
Flashes between green
and amber
The red element is stuck on.
Stays amber continuously
Either the server is hung or the LED controller is stuck.
Stays off continuously
The server is hung or powered off, the controller is stuck, or the
server is using a new or different LED controller.
Also see Testing the Duplication Memory board LEDs.
Resolving problems
If the server is hung, it should automatically reboot and fix itself. If the server does not reboot
itself, power it down and reboot it.
If an LED is clearly stuck or has a burned out element, ignore the indicators until the server can
be conveniently replaced.
S8710 Media Server LEDs
The S8710 Media Server has LEDs on both the front and back panels. Use the links in Table 82
for LED information and interpretation.
Table 82: S8710 LED information
S8710
location
Diagram
LED interpretation
Front panel
Figure 16
Figure notes: S8710 front panel LED interpretation
Back panel
Figure 17
Figure notes: S8710 rear panel LED interpretation
Issue 3 February 2007
317
LEDs
Figure 16: LEDs on front panel of S8710 Media Server
1
2
3
4
Duplex ch 1 ch 2
5
disc
2
1
2
6
0
0
Simplex
1
1
COMPACT
1
msdsled1 KLC 041304
Figure notes: S8710 front panel LED interpretation 1 of 2
Number
Description
Status
1
Internal health
GREEN: normal
AMBER: system degraded. See system board
LEDs to identify the component which is in a
degraded state.
RED: system critical. See the system board LEDs
to identify the component that is in a critical state.
2
Power supply
GREEN: normal
AMBER: power redundancy failure
RED: Critical power supply failure
3
NIC 1 (Eth0) link/activity
(GREEN)
STEADY ON: network link
FLASHING: network link and activity
Off: No link to network
4
NIC 2 (Eth1) link/activity
(GREEN)
STEADY ON: network link
FLASHING: network link and activity
OFF: No link to network
1 of 2
318 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
S8710 Media Server LEDs
Figure notes: S8710 front panel LED interpretation 2 of 2
Number
Description
Status
5
Active/Standby mode (BLUE)
STEADY ON: in active mode
FLASHING: in standby mode
OFF: deactivated
NOTE: If pressed, the LED is deactivated. Wait 10
seconds and the LED comes back on.
6
Power on/
Standby button/
System power
GREEN: system on
AMBER: system shut down but power still applied
OFF: power supply failure
2 of 2
Issue 3 February 2007
319
LEDs
Figure 17: LEDs on back panel of S8710 Media Server
1
3
2
3
2
4
3
3
2
DAL1
DUP
MEMORY
LINC
ACTIVE
LINC
SYNC
TRANS
MODE
RECEIVE
MODE
100 MGz
2
100 MGz
iLO
2
1
1
133 MGz
VDCI
UID
5
6
8
7
msds871c KLC 040604
Figure notes: S8710 rear panel LED interpretation 1 of 2
Number
Description
Status
1
Not used
ON: expansion board failed.
OFF: normal
2
Not used
STEADY ON: slot has power
FLASHING: power is cycling
OFF: no power
3
Quad-NIC fault
(slot 2) (AMBER)
ON: expansion board failed.
OFF: normal
4
Quad-NIC power
(slot 2) (GREEN)
STEADY ON: slot has power
FLASHING: power is cycling
OFF: no power
5
RJ45 link (GREEN)
ON: linked to network
OFF: not linked to network
6
RJ45 link (GREEN)
STEADY ON: network activity
FLASHING: network activity
OFF: no network activity
7
Active/standby mode
(BLUE)
STEADY ON: in active mode
FLASHING: in standby mode
Off: deactivated
NOTE: If pressed, the LED is deactivated. Wait 10
seconds and the LED comes back on.
1 of 2
320 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
G250/G350 and Media Module LEDs
Figure notes: S8710 rear panel LED interpretation 2 of 2
Number
Description
Status
8
Power supply
(GREEN)
ON: power is on and the power supply is functioning
properly
OFF: indicates one or more of the following conditions:
●
AC power is unavailable
●
Power supply failed
●
Power supply is in standby mode
●
Power supply exceeded current limit
2 of 2
G250/G350 and Media Module LEDs
LEDs appear on the G250/G350 front panel and on each media module.
Some media modules have additional LEDs, although each media module has the three
standard LEDs. Table 83: LED Interpretation indicates the meanings associated with standard
DEFINITY server LEDs. Although in some cases these LEDs have been augmented or modified
for the S8300 Media Server and Avaya G250/G350 Media Gateways, it is important to be aware
of their standard meanings when viewing the system.
Table 83: LED Interpretation
Note:
Red
Upon power-up or module insanity, this LED is turned
on. Upon passing diagnostics, this LED is turned off.
Green
During power-up self-testing and maintenance testing,
this LED is turned on.
Yellow
This LED indicates that the module is in service.
Note:
The four multi-color specialized status LEDs that have appeared on various
DEFINITY server TN boards like the E1/T1/DS1 board (TN464F) do not appear
on the media modules.
Issue 3 February 2007
321
LEDs
Front panel LEDs
The following figure shows the G250-Analog chassis:
Figure 18: G250-Analog chassis
The following figure shows the G250-BRI chassis:
Figure 19: G250-BRI chassis
The following figure shows the G250-DCP chassis:
Figure 20: G250-DCP chassis
322 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Front panel LEDs
The following figure shows the G250-DS1chassis:
Figure 21: G250-DS1 chassis
The following figure shows the G350 chassis:
Figure 22: G350 chassis
System LEDs
The system LEDs show the status of the Avaya G250/G350 Media Gateway. The following
table shows the meaning of the system LEDs when they are lit:
Table 84: System LEDs 1 of 2
LED
Name
Color
Meaning
MDM
Modem Detected
Green
A modem is connected to the
CONSOLE or USB port
ALM
Alarm
Red
An alarm is present in the system
1 of 2
Issue 3 February 2007
323
LEDs
Table 84: System LEDs 2 of 2
LED
Name
Color
Meaning
CPU
CPU
Green
OFF — A test is in progress
ON — Normal operation
PWR
Power
Green
OFF — No power
BLINKING — Problem with power
ON — Normal operation
2 of 2
Analog telephone ports and LEDs
The analog telephone ports are standard RJ-45 telephone network ports.
●
The TRUNK ports are trunk ports.
●
The LINE ports are analog telephone ports.
The analog telephone port LEDs show the status of the analog telephone ports.
The following table shows the meaning of the analog telephone LEDs when they are lit:
Table 85: Analog telephone port LEDs
LED
Name
Color
Meaning
ETR
Emergency Transfer
Green
The Emergency Transfer Relay (ETR)
feature has been activated. This feature
provides an emergency link between the
telephone connected to the first LINE port
(port 2) and the trunk connected to the
TRUNK port if power is disconnected from
the G250/G350 or if the G250/G350
becomes unregistered from its Media
Gateway Controller (MGC).
ALM
Alarm
Red
An alarm is present on the board
TST
Test
Green
A test is in progress
ACT
Activity
Yellow
A call is in progress
324 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Media Module LEDs
Media Module LEDs
Media Gateway physical LEDs provide the technician with information regarding the ability to
troubleshoot the media module as a whole.
Note:
Note:
Note:
The physical LEDs provide board level status information, while the SAT provides
port level status information.
Note:
The G250 only supports the S8300 Media Server and the WAN media modules
(MM340 and MM342).
LED locations on the Media Modules
Most media modules have three standard LEDs on the faceplate (Figure 33: Faceplate of
Media Modules with Standard LEDs). On the Avaya BRI (MM720, MM722), Avaya DCP
(MM312, MM712, MM717), Avaya WAN (MM340, MM342), and Avaya Analog (MM711,
MM714, and MM716) media modules, these are the only LEDs present.
Figure 23: Faceplate of Media Modules with Standard LEDs
The Avaya E1/T1 media module (MM710) has an additional LED, as shown in Figure 34: T1/
E1 Media Module with Fourth LED.
Figure 24: E1/T1 Media Module with Fourth LED
The Avaya LAN media modules (MM314 and MM316) have a single alarm (ALM) LED. This
LED is located on the left side of the front panel, as shown in Figure 25: MM314 LAN Media
Module and Figure 26: MM316 LAN Media Module
Issue 3 February 2007
325
LEDs
Figure 25: MM314 LAN Media Module
Figure 26: MM316 LAN Media Module
S8300 Media Server LEDs
Figure 27: S8300 Media Server
The S8300 Media Server has a total of 4 LEDs on the faceplate (Figure 12: S8300 Media
Server), the three standard LEDs and one additional LED:
- A fourth LED labeled “OK-to-Remove”, which indicates when the S8300’s disk is properly
shut down.
GREEN “OK-to-Remove” LED
The S8300 has a hard drive that must be shut down prior to removal of the S8300. Initiate a
shutdown process by first depressing the shutdown button located next to the fourth GREEN
“Ok-to-Remove” LED for 2-4 seconds (specific to the S8300). The behavior of the S8300’s
LEDs during shutdown differs depending on the version of Avaya Communication Manager
running:
- For Avaya Communication Manager versions 1.2 and earlier, the fourth GREEN LED
flashes at a constant rate until it finally glows steadily.
- For Avaya Communication Manager version 1.3 and later, the fourth GREEN
“Ok-to-Remove” LED flashes at a constant rate, and the TST LED flashes slowly at first.
As computer processes exit, the TST LED flashes faster. When the shutdown has
completed, the TST LED goes out, and the “OK-to-Remove” LED then glows steadily.
326 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Media Module LEDs
Once steady, the GREEN LED indicates that the disk drive has been shut down properly and
the S8300 is ready to be removed. Follow standard media module removal procedures after the
GREEN LED indicates that the disk drive has been properly parked.
There are three different ways that you can properly shut down the S8300 before it is removed:
- Press the shutdown button on the faceplate for 2-4 seconds.
- Initiate shutdown via the web interface with a computer connected either:
●
Remotely, on the customer’s LAN
●
Locally, on the S8300 using the Services Port on the faceplate of the S8300
S8300 LED differences from media modules
Certain behaviors of the traditional S8300 LEDs differ from the media modules because the
S8300 is a Media Server running Avaya Communication Manager.
- Situations like “insanity” and IP concepts of “registered” via H.248 do not necessarily
apply to other media modules.
- The red ALM LED provides a major alarm indication. Software turns off the red ALM LED
during system startup. After startup, software turns on the red LED whenever a major
alarm is present, and turns off the red ALM LED whenever a major alarm clears. Since
the S8300 sees a major alarm whenever an Replace variable w/ product name becomes
unregistered, this means the red ALM LED turns on. If the Media Gateway subsequently
becomes registered, the major alarm clears, and the red ALM LED turns off.
Note:
Note:
For an S8300 configured as an LSP, the converse is true. If an Avaya G250/G350
Media Gateway registers with an LSP, a major alarm is generated, and the RED
ALM LED turns on. When the Media Gateway unregisters, the RED ALM LED
turns off.
The red ALM LED can be turned on by software to report an application or other error.
The red ALM LED can also be turned on by a hardware watchdog that has not been
cleared for at least 10ms, when the processing complex has ceased to function.
- The green TST LED provides self-testing and maintenance indication. This LED is lit
steady when Avaya Communication Manager is running. This is an important indication
on Local Survivable Processors that are not controlling any media gateways, because
the yellow ACT LED will not be lit.
- The yellow ACT LED provides active “in use” indication. For an S8300, the software turns
on the yellow ACT LED during system startup, and turns off the LED during shutdown.
During normal call processing operation, the yellow ACT LED turns on whenever an
Avaya media gateway, an IP station, or an IP console is registered with the S8300.
Likewise, it turns off when none of the IP endpoints are registered.
Table 86: ALM (Alarm) LED through Table 89: OK to Remove illustrate the states of S8300
LEDs.
Issue 3 February 2007
327
LEDs
Table 86: ALM (Alarm) LED
ALM (Alarm) LED
Color
Red
Power On Reset
On
BIOS Boot
On
OS and SW Boot
On
Avaya Communication
Manager is Running
(LSP)
On
H.248 Registered
Off - SW
Shutdown in Progress
On
Shutdown Complete
On
Table 87: TST (Test) LED
TST (Test) LED
Color
Green
Power On Reset
Off
BIOS Boot
Off
OS and SW Boot
On-SW
System Up
Off - SW
H.248 Registered
Off - SW
Shutdown in Progress
Off - SW
Shutdown Complete
Off
328 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Media Module LEDs
Table 88: Active (In Use) LED
Active (In Use) LED
Color
Yellow
Power On Reset
Off
BIOS Boot
Off
OS and SW Boot
Off
System Up
SW
H.248 Gateway
Registered
On-SW
Shutdown in Progress
Off-SW
Shutdown Complete
Off
Table 89: OK to Remove
OK to Remove
Color
Green
Power On Reset
Off
BIOS Boot
Off
OS and SW Boot
Off
System Up
Off
H.248 Registered
Off
Shutdown in Progress
1 Hz flash
Shutdown Complete
On
Issue 3 February 2007
329
LEDs
S8300 LED lighting sequence
In general, S8300 LEDs light in order from top to bottom on the S8300 faceplate.
The following order applies during restart or boot of the S8300:
Note:
Note:
The Red ALM LED stays on until the Linux operation system takes over control
from the S8300 BIOS. The following sequence takes place after this occurs.
LED Lighting Sequence
1. ALM - RED – lights up first then turns off
2. TST - GREEN – lights up second then turns off
3. ACT - YELLOW – lights up third then turns off
4. OK To REMOVE - GREEN – lights up fourth then turns off
5. Left LED in SERVICES port - GREEN (10 MB link speed) – lights up then turns off
Left LED in SERVICES port - YELLOW (100 MB link speed) – lights up then turns off
Right LED in Services port - GREEN (10 MB link speed) – lights up then turns off
At this point, you can connect to the S8300. When Avaya Communication Manager starts, the
green TST LED turns on and stays on.
MM710 E1/T1 media module LEDs
Figure 28: E1/T1 Media Module LEDs
The E1/T1 media module has four LEDs on its faceplate (see Figure 35: T1/E1 Media Module
LEDs). Table 94: T1/E1 LEDs shows their color and functions. The first three are the standard
LEDs, which are under software control.
330 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Media Module LEDs
Table 90: E1/T1 LEDs
Name
Color
Location
Description
ALM
RED
Top
Upon power-up, this LED is turned on. Upon passing
diagnostics this LED is turned off. During normal circuit
pack operation this LED is not turned on except for
certain alarm states.
TST
GREEN
Second
During power-up self-testing and maintenance testing
requested by the SPE, this LED is turned on.
ACT
YELLOW
Third
This LED indicates that the clock is synchronized with a
source (usually the Central Office). The LED is blinking
2700 ms ON and 300 ms OFF. This is the most
common condition.
The opposite blinking of the YELLOW LED is 300 ms
ON and 2700 ms OFF. This is an error condition, and
indicates that the MM710 E1/T1 media module is not
synchronized with a clock.
An infrequent occurrence is a steady YELLOW LED.
This indicates in-use activity, only when clock
synchronization is set to local.
SIG
GREEN
Bottom
This LED indicates whether the link to the Central
Office (CO) is up (equivalent to the TN464F circuit pack
Status 3 GREEN LED). See Figure 35: T1/E1 Media
Module LEDs.
The supported portion of the LED Control message allows software to change the status of the
three standard LEDs on the E1/T1 media module faceplate. Power-up and alarm states are the
only conditions where hardware sets the state of the LEDs independent of ANGEL firmware
control. The exceptions to letting software turn off the LEDs are:
- The board is in reset (RED ALM LED remains on)
- A call is up (YELLOW ACT LED remains on while the E1 line is in-frame and at least one
voice/data call is up)
- During board reset initialization testing (GREEN TST LED remains on until initialization
testing is complete)
Note:
Note:
For ISDN operation, the Yellow LED will be turned on if ANY port has an active
TDM connection (including the D-channel).
Issue 3 February 2007
331
LEDs
Synchronization
The YELLOW ACT LED on the front of the MM710 media module can tell you the status of that
module regarding synchronization.
●
●
If the YELLOW ACT LED is solidly on or off, it has NOT been defined as a synchronization
source. If it is on, one or more channels is active. If it is an ISDN facility, the D-channel will
count as an active channel and will cause the YELLOW ACT LED to be on.
When the MM710 is driving a clock sync source line to the Replace variable w/ short
product name main clock, the YELLOW ACT LED does not indicate port activity, but
instead indicates that the MM710 is the sync source by flashing with a regular 3-second
period:
- It is on for 2700 ms off for 300 ms if it has been specified as a sync source and is
receiving a signal that meets minimum requirements for the interface.
- If it has been specified as a sync source and is not receiving a signal, or is receiving a
signal that does not meet minimum requirements for the interface, then the YELLOW
ACT LED will be off for 2700 ms and flash on for 300 ms.
E1/T1 initialization
The E1/T1 media module LEDs behave in the following manner during initialization. The Angel
provides a visual indication of the media module’s status through the three faceplate LEDs:
●
●
During initialization the YELLOW ACT LED is held off, while the RED and GREEN LEDs
are on during the entire initialization sequence.
Upon power up or reset, if only the RED ALM LED comes on, the Angel processor is dead
or the board is being held permanently in reset.
●
Upon completion of the diagnostics and initialization, the GREEN TST LED turns off.
●
If the initialization tests fail, the RED ALM LED remains on.
●
If the tests all pass, then all LEDs are extinguished until Avaya Communication Manager
starts using the media module.
Operational control
After successful initialization, the E1/T1 media module’s LEDs are controlled as follows:
●
●
●
The Angel lights the YELLOW ACT LED when there is at least one non-idle trunk. If Avaya
Communication Manager sends a message to drive the clock sync signals, the YELLOW
ACT LED indicates this instead of the port busy/idle status.
The Media Server may independently light and extinguish the three LEDs through
downlink LED Control messages, subject to the constraint that it may not turn off a
YELLOW ACT LED turned on by the Angel as a result of port activity.
If the media module resets for any reason and is not released from reset, the RED ALM
LED lights and the YELLOW ACT and GREEN TST LEDs are held off.
332 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Media Module LEDs
Avaya MM314 Media Module LEDs
The MM314 media module is a LAN media module that provides:
●
●
24 Ethernet 10/100 Base-T Ethernet access ports with inline Power over Ethernet (PoE).
One Gigabit Ethernet copper port for server connection or uplink to another switch or
router.
Figure 29: The MM314 Media Module front panel
MM314 alarm LED
The MM314’s alarm (ALM) LED is located on the lower left corner of the front panel. The ALM
LED indicates that an alarm is present in the module, or that Avaya Communication Manager
(CM) has the slot administered for a Voice media module.
MM314 port LEDs
On the left side of the MM314’s front panel are numbered LEDs that correspond to each of the
MM314’s network ports. Underneath these LEDs is a row of LEDs that indicate particular
functions. The function LED that is lit indicates which function the network port LEDs are
reporting. For example, if the LNK LED is lit, the port LEDs indicate whether the network links
for the specific ports are functioning properly.
To the right of the function LEDs are two push buttons. Use these buttons to select the function
you want the port LEDs to report. For example, if the COL LED is lit, all the port LEDs are
reporting the Collision status of their respective port. Table 91 shows each of these functions:
Table 91: MM314 Port LEDs 1 of 2
LED
Name
Meaning
LNK
Link
If the port LED is lit, the port is enabled and the link is
working properly.
COL
Collision
If the port LED is off, there has been no collision on line.
If this LED is flashing, there are collisions occurring.
Tx
Transmit to line
If the port LED is lit, data is being transmitted.
1 of 2
Issue 3 February 2007
333
LEDs
Table 91: MM314 Port LEDs 2 of 2
LED
Name
Meaning
Rx
Receive from line
If the port LED is lit, data is being received from the line.
FDX
Half/Full Duplex
If the port LED is lit, the line is operating in Full Duplex
mode. If the port LED is off, the line is operating in Half
Duplex mode.
FC
Symmetric Flow Control
If the port LED is lit, the port is in Full Duplex and Flow
Control mode. If the port LED is off, the port’s Flow
Control mode is disabled, or the port is operating in Half
Duplex mode.
Hspd
High Speed
If the LED is lit, the port is operating at the higher of its
possible speeds.
LAG
Link Aggregation Trunking
If the LED is lit, the port belongs to a LAG.
PoE
Power over Ethernet
If the LED is lit, the port is operating in PoE mode.
2 of 2
G700 and Media Module LEDs
The G700 LEDs are the same as those on the Avaya Cajun P330, with the following exceptions:
●
Slight modifications to two of the LEDs (OPR and SYS)
●
Addition of the Alarm LED to the LED Panel to display prominently any error condition
See Table 3.1: Avaya P333T LED Description, in the "User’s Guide for the Avaya P333T
Stackable Switch Release 3.12" for a complete listing of LEDs.
Some Media Modules have additional LEDs, although each Media Module has the three
standard LEDs. Table 92: LED Interpretation indicates the meanings associated with standard
server LEDs. Although in some cases these LEDs have been augmented or modified for the
S8300 Media Server and G700 Media Gateway, it is important to be aware of their standard
meanings when viewing the system.
G350: For G350 - WAN media modules, MM314, MM340, and MM342. If these media modules
are inserted in a slot administered for a voice media module, the red LED will be lit.
Table 92: LED Interpretation 1 of 2
Red
Upon power-up or module insanity, this LED is turned on. Upon passing
diagnostics, this LED is turned off.
1 of 2
334 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
G700 and Media Module LEDs
Table 92: LED Interpretation 2 of 2
Green
During power-up self testing and maintenance testing, this LED is turned on.
Yellow
This LED indicates that the module is in service.
2 of 2
Note:
Note:
Note:
The four multi-color specialized status LEDs that have appeared on various TN
circuit packs like the T1/E1/DS1 board (TN464) do not appear on the Media
Modules.
Note:
LEDs can also be viewed using the embedded Device Manager on the L2
Switching Processor. However, it displays LED position only and does not
indicate status.
LED panel location on the G700
As shown in Figure 30: G700 LED Panel Location, the LED panel is located on the top left
corner of the G700. Media Module slot V1 is directly below the LED panel. This slot can be
occupied by any type of Media Module. However, the S8300 Media Server can reside only in
this particular slot because of height restrictions. For a specific discussion of the S8300 LEDs,
see S8300 Media Server LEDs.
Figure 30: G700 LED Panel Location
3
ALM PWR CPU MSTR
V1
1
ALM
TST
ACT
OK TO
REMOVE
LNK COL
Tx
Rx
FDX
6
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
FC Hspd LAG
V2
EXT 1 EXT 2
2
SERVICES
USB 1
SM EM
SI
EO
EXT 1
4
EXT 2
EIA 530A DCE
ALM
TST
ACT
USB 2
V4
msdcs830 KLC 031402
EI
E1/T1
V3
SHUT DOWN
SO
ALM
TST
ACT
SIG
7
1
2
3
4
5
6
7
8
1
2
3
4
5
6
7
8
ALM
TST
ACT
CONSOLE
9
5
8
Figure notes:
1. Media Module Slot #1 (V1)
2. S8300 Services Port (Used
with cross-over ethernet cable)
3. S8300 USB Series Modem
connection
4. Avaya Expansion Module Slot
5. 10/100 BaseT Ethernet Ports
(EXT1, EXT2)
6. Media Module Slot #2 (V2)
7. Media Module Slot #3 (V3)
8. Media Module Slot #4 (V4)
9. Console Interface (use with serial
cable)
Issue 3 February 2007
335
LEDs
Figure 31: G700 LED Panel shows an expanded view of the G700 LED panel.
Figure 31: G700 LED Panel
51
ALM PWR CPU MSTR
LNK COL
Tx
Rx
FDX
52
V1
ALM
TST
ACT
OK TO
REMOVE
LNK COL
Tx
Rx
FDX
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
FC Hspd LAG
V2
EXT 1 EXT 2
V3
USB 1
55
SO
60
61
62
V4
EXT 2
57
58
SI
64
65
66
EI
SM EM
1
2
3
4
5
6
7
8
1
2
3
4
5
6
7
8
ALM
TST
ACT
SIG
EO
EIA 530A DCE
ALM
TST
ACT
USB 2
EXT 1
56
63
E1/T1
SHUT DOWN
SERVICES
54
EXT 1 EXT 2
59
ALM PWR CPU MSTR
53
FC Hspd LAG
ALM
TST
ACT
CONSOLE
msdcled2 KLC 031402
336 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
G700 and Media Module LEDs
Front panel LEDs
The front panel includes the following LEDs (Figure 32: G700 Front Panel LEDs):
●
4 LEDs in Voice/Data Module zone (ALM, PWR, CPU, MSTR)
Note:
The LEDs labeled OPR and SYS on the P330 are labeled CPU and MSTR,
respectively, on the G700.
Note:
●
16 LEDs representing the Data Ports associated with the Personality Module or Data
Expansion Ports
●
8 LEDs in Data Function zone (LNK, COL, Tx, Rx, FDX, FC, Hspd, LAG)
●
2 LEDs (EXT 1 and EXT 2) for two 10/100 Mb data ports on the chassis
Note:
The four LEDs (ALM, PWR, CPU, MSTR) are positioned as closely as possible to
the top left corner of the LED Panel so that important motherboard-related
information can be quickly located.
Note:
Figure 32: G700 Front Panel LEDs
51
ALM PWR CPU MSTR
LNK COL
Tx
Rx
FDX
52
53
54
55
56
57
58
FC Hspd LAG
EXT 1 EXT 2
59
60
61
62
63
64
65
66
ledcled KLC 031402
A total of 30 LEDs appear on the LED Panel for the G700. The following three LEDs have been
added to the Avaya Cajun LEDs (see “Avaya P330 Manager User Guide”):
●
Red ALM or Alarm LED
●
EXT 1 LED
●
EXT 2 LED
The G700 MSTR LED differs from the Avaya Cajun LED in that the bottom G700 in a stack of
10 G700s with the same version firmware is always elected master (therefore, its MSTR light is
lit). But, if the firmware versions are not the same, the G700 with the latest firmware version is
elected master and its MSTR light is lit. If there is only one G700 in a stack, its MSTR light is
always lit.
Issue 3 February 2007
337
LEDs
Navigating using the front panel LEDs
Navigation using the front panel LEDs on the G700 is the same as that of the Avaya Cajun P330
series. “Table 3.2: Avaya P330 <--> Select buttons, in the "User’s Guide for the Avaya P333T
Stackable Switch Release 3.12". For example, arrow keys can be used to move left and right
between the LEDs to check the following:
●
LNK (link)
●
Col (collision)
●
Tx (send)
●
Rx (receive)
In addition, the status of the ports can be queried using 51-66 in the LED panel.
Use the push buttons (on the right and left of data mode LEDs) for selecting the function to be
reported simultaneously by all 16 of the Port data expansion LEDs. The function selected is
indicated by a lit LED in that Function zone. Each time the right or left push-button is pressed,
the function currently lit moves by one position to the right or to the left accordingly.
For example, if the COL LED is lit, all 16 Ports associated with the data expansion module LEDs
are reporting the Collision status of their respective port. To select the LAG function, press 6
times on the right push-button. Afterwards, to select the Rx function, press 4 times on the left
push-button.
For the G700, the LEDs display the information of ports 2 External 10/100Base-T Ethernet links
and data expansion ports 51-66. At power up the LEDs indicate the Link status of ports 51-66
and ext 1 & ext 2. Push the right button once to move the indication to Collision status of ports
51-66 and ext 1 & ext 2. Push the left button to move the indication backwards.
Note:
Note:
Eight pushes in one direction complete a full cycle of display.
If the right and the left push buttons are pushed simultaneously for:
●
Note:
1.5 seconds, the module resets the Layer 2 Switching Processor but not the Media
Gateway Processor
●
4 seconds, the whole stack resets (performing slot renumbering)
●
18 seconds, the module enters the debug mode – module is disabled for data traffic
Note:
Currently, there is no physical button or sequence of button presses defined to
reset the Media Gateway Processor or G700. Perform software resets by using
the Command Line Interface (CLI) for the Device Manager of the G700.
338 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
G700 and Media Module LEDs
Red ALM or Alarm LED
The red ALM or Alarm LED is on the top-left most corner of the LED Panel next to other
important system LEDs (PWR, CPU, MSTR), as specified in Figure 32: G700 Front Panel
LEDs. The presence of this red ALM LED is primarily for on-site service technicians or
dispatches. It alerts technicians of major failures that require a physical replacement or removal
of equipment. Most major G700 components controlled or monitored by the motherboard can
be a cause of failure. This includes the VoIP Media Module, but not other Media Modules.
Note:
The red ALM LED lights for motherboard problems only. Check for a red ALM
LED for problematic G700s. Also check all of the Media Module LEDs for any
Media Module specific red ALM LEDs.
Note:
Note:
If the red ALM LED is lit on a non-VoIP Media Module, check the G700 alarm
screens and the Communication Manager alarm screens to determine where the
fault lies.
Note:
The red ALM LED indicates the health of the G700 by turning on under two distinct
circumstances:
●
G700 hardware failure
- Impaired functions of the Layer 2 Switching Processor, Media Gateway Processor, or
VoIP engine
- Power supply voltage out of bounds
- Unit overheating
●
The G700 cannot communicate to any server
The following are a few examples:
●
The red ALM LED is lit when two or more fans have failed.
Various warnings, alarms, and a graceful shutdown are performed based on the fan and
thermal sensor conditions.
●
The red ALM LED is lit from the time power is applied until diagnostics end.
●
The red ALM LED turns “OFF” when:
- Physical conditions such as temperature are rectified and return to normal or acceptable
operating ranges.
- The alarm is cleared manually.
Issue 3 February 2007
339
LEDs
EXT 1 LED
EXT 1 LED appears on the LED Panel (Figure 32: G700 Front Panel LEDs), which reports the
status of the first 10/100 MB/sec port (these LEDs report the 8 different functional statuses
dictated by the left and right arrow buttons).
EXT 2 LED
EXT 2 LED appears on the LED Panel (Figure 32: G700 Front Panel LEDs), which reports the
status of the second 10/100 MB/sec port (these LEDs report the 8 different functional statuses
dictated by the left and right arrow buttons).
G700 LED panel definitions
Table 93: LED Definitions illustrates the LED definitions for the G700 LED Panel.
Table 93: LED Definitions 1 of 2
No.
LED Name
Description
LED States
1
ALM
Alarm Status
Color is RED
OFF - No alarms exist
ON (RED) - Alarm exists on the chassis itself
2
PWR
Alarm Status
Color is
GREEN
OFF - Power is down
ON - Power is up
Blinking - every 1.2 seconds (400ms on, 800ms off)
when 5 volts power is not available to the riser
board and the Media Modules
3
CPU
CPU Operation
Color is
GREEN
OFF - CPU is in boot operation or is running BIST
ON - CPU boot operation and BIST completed
4
MSTR
Master/Slave
Status Color is
GREEN
OFF - Slave box of the stack
ON - Master of the stack and redundant cable is not
present or not active
1 Blink every 1.5 sec - Master of the stack and
active redundant cable
a
LNK port
51-66, Ext
1-2
Port Status
Color is
GREEN
OFF - Port disabled or not existent. At phase 1, or
link fail of Giga ports.
ON - Port is enabled and link is OK.
1 Blink every 1.5 sec - Link test fail (of 10/100M
ports only at phase 1)
2 Blinks every 1.5 sec - Partition
b
COL
Port 51-66,
Ext 1-2
Collision
(GREEN)
OFF - No collision or FDX port
ON - Collision occurred on line
5
1 of 2
340 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
G700 and Media Module LEDs
Table 93: LED Definitions 2 of 2
No.
LED Name
Description
LED States
c
Tx
Port 51-66,
Ext 1-2
Transmit to line
(GREEN)
OFF - No transmit activity
ON - Data transmitted on line
d
Rx
Port 55-66,
Ext 1-2
Receive from
line
(GREEN)
OFF - To receive activity
ON - Data received from the line
e
FDX
Port 51-66,
Ext 1-2
Half/Full
Duplex
(GREEN)
OFF - Half Duplex mode of operation
ON - Full Duplex mode of operation, or for 10/
100Base-T ports when link test fail with
auto-negotiation enabled
f
FC*
Port 51-66,
Ext 1-2
Symmetric
Flow Control
(GREEN)
OFF - Port is in an Asymmetric Flow control mode,
or in Flow Control mode disabled, or it is in half
duplex
ON - Port is in full duplex and in a symmetric Flow
Control mode
g
HSpd
Port 51-66,
Ext 1-2
High Speed
(GREEN)
OFF - 10Base-T or for an expansion port that does
not exist
ON - 100Base-T, 100Base-F, 1000Base-X, and
OC-12, or for 10/100Base-T ports when link test fail
with auto-negotiation enabled
h
LAG
Port 51-66,
Ext 1-2
Link
Aggregation
"Trunking"
(GREEN)
OFF - No LAG defined with this port
ON - Port belongs to a LAG
6
Data
16 data
expansion ports
51-66
(GREEN)
OFF - see notes on No. 5 a-h
ON - see notes on No. 5 a-h
7
EXT 1
RJ 45 to
Non-Avaya
equipment
(GREEN)
OFF - see notes on No. 5 a-h
ON - see notes on No. 5 a-h
8
EXT 2
RJ 45 to
Non-Avaya
equipment
(GREEN)
OFF - see notes on No. 5 a-h
ON - see notes on No. 5 a-h
* For Giga ports, when auto-negotiation is enabled and the link is down, FC LED reflects the last mode
If the user resets the module/stack, all of the module’s/stack’s LEDs turn on (test lamp) for 150ms. The
COL, Tx, and Rx LED signals must be at least 150ms.
2 of 2
Issue 3 February 2007
341
LEDs
Media Module LEDs
LEDs provide the technician with information regarding the ability to troubleshoot the Media
Module as a whole.
Note:
Note:
The physical LEDs provide board level status information, while the SAT provides
port level status information.
LED Locations on the Media Modules
All Media Modules have three standard LEDs on the faceplate (Figure 33: Faceplate of Media
Modules with Standard LEDs). On the VoIP (MM760), BRI (MM720), DCP (MM712), and
Analog (MM711) Media Modules, these are the only LEDs present. The T1/E1 Media Module
(MM710) has an additional LED, as shown in Figure 34: T1/E1 Media Module with Fourth LED.
Figure 33: Faceplate of Media Modules with Standard LEDs
ALM
TST
ACT
1
2
3
4
5
6
7
8
mmdc712 KLC 022702
Figure 34: T1/E1 Media Module with Fourth LED
SO
ALM
TST
ACT
SIG
E1/T1
EI
SM EM
SI
EO
EIA 530A DCE
mmdc710 KLC 020402
342 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
G700 and Media Module LEDs
MM710 T1/E1 Media Module LEDs
The T1/E1 Media Module has four LEDs on its faceplate (see Figure 35: T1/E1 Media Module
LEDs). Table 94: T1/E1 LEDs shows their color and functions. The first three are the standard
LEDs, which are under software control.
Table 94: T1/E1 LEDs
Name
Color
Location
Description
ALM
RED
Top
This LED is turned on during power up. This LED is turned off
when it passes diagnostics. During normal circuit pack
operation, this LED is not turned on except for certain alarm
states.
TST
GREEN
Second
This LED is turned on during power-up self-testing and
maintenance testing requested by the SPE.
ACT
YELLOW
Third
This LED indicates that the clock is synchronized with a
source (usually the Central Office). The LED is blinking 2700
ms ON and 300 ms OFF. This is the most common condition.
The opposite blinking of the YELLOW LED is 300 ms ON and
2700 ms OFF. This is an error condition, and indicates that
the MM710 T1/E1 Media Module is not synchronized with a
clock.
An infrequent occurrence is a steady YELLOW LED. This
indicates in-use activity only when clock synchronization is
set to local.
SIG
GREEN
Bottom
This LED indicates whether the link to the Central Office (CO)
is up (equivalent to the TN464 circuit pack Status 3 GREEN
LED). See Figure 35: T1/E1 Media Module LEDs.
Figure 35: T1/E1 Media Module LEDs
SO
ALM
TST
ACT
SIG
E1/T1
EI
SM EM
SI
EO
EIA 530A DCE
mmdc710 KLC 020402
Note:
Note:
For ISDN operation, the Yellow LED will be turned on if ANY port has an active
TDM connection (including the D-channel).
Issue 3 February 2007
343
LEDs
Synchronization
The yellow ACT LED on the front of the MM710 Media Module indicates the synchronization
status of that module.
●
●
If the yellow ACT LED is solidly on or off, it has NOT been defined as a synchronization
source. If it is on, one or more channels is active. If it is an ISDN facility, the D-channel will
count as an active channel and will cause the yellow ACT LED to be on.
When the MM710 is driving a clock sync source line to the G700 main clock, the yellow
ACT LED does not indicate port activity, but instead indicates that the MM710 is the sync
source by flashing with a regular 3-second period:
●
●
It is on for 2.8 seconds and flashes off for 200 milliseconds if it has been specified as a
sync source and is receiving a signal that meets minimum requirements for the interface.
If it has been specified as a sync source and is not receiving a signal, or is receiving a
signal that does not meet minimum requirements for the interface, the yellow ACT LED
will be off for 2.8 seconds and flash on for 200 milliseconds.
T1/E1 Initialization
The T1/E1 Media Module LEDs behave in the following manner during initialization. The Angel
provides a visual indication of the Media Module’s status through the three faceplate LEDs:
●
●
During initialization, the yellow ACT LED is turned off, while the red and green LEDs are
turned on during the entire initialization sequence.
Upon power up or reset, if only the red ALM LED comes on, the Angel processor is dead
or the Media Module is being held permanently in reset.
●
Upon completion of the diagnostics and initialization, the green TST LED turns off.
●
If the initialization tests fail, the red ALM LED remains on.
●
If the tests all pass, all LEDs are turned off until Communication Manager starts using the
Media Module.
Operational control
After successful initialization, the T1/E1 Media Module’s LEDs are controlled as follows:
●
●
●
The Angel lights the yellow ACT LED when there is at least one non-idle trunk. If
Communication Manager sends a message to drive the clock sync signals, the yellow ACT
LED indicates this instead of the port busy/idle status.
The Media Server may independently light and turn off the three LEDs through downlink
LED Control messages, subject to the constraint that it may not turn off a yellow ACT LED
turned on by the Angel as a result of port activity.
If the Media Module resets for any reason and is not released from reset, the red ALM LED
is turned on and the yellow ACT and green TST LEDs are turned off.
344 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Chapter 4: Media Gateway Traps
This chapter describes G250, G350, and G700 Media Gateway Traps.
A trap indicates a special condition that exists or an event that occurs within the system. Some
traps indicate configuration changes or component modifications and are merely informative.
Other traps indicate warning or error conditions that may compromise the performance of the
media gateway. Serious traps trigger alarms which are communicated to an alarm management
site.
Alarm Format
Media Gateways report alarms to the primary server (either an S8300, S8500, or S8700 Series
Media Server) using SNMP traps. Like the primary server’s own alarms, alarms from a Media
Gateway:
●
Reside in the primary server’s alarm log
●
Can be viewed using the SAT command display alarms
●
Can be viewed using the Web Interface Display Alarms option
However, the format of these displayed alarms is slightly different. As an example, a displayed
G700 alarm has the following format:
n CMG 1 WRN 07/17/2006:13:45 121.1.1.2:cmgMultipleFanFault
Within the above alarm-display string, the value:
●
“n” is a sequential alarm ID.
●
“CMG” identifies a Media Gateway as the maintenance object.
●
“1” is the event’s ID (1st column of Table 99: G700 Traps and Resolutions).
This table also contains each alarm’s corresponding SNMP trap # in the 2nd column. However,
many of the MIB-defined traps have been excluded, either because:
●
●
●
A specific trap (such as Trap #3) is the SNMP mechanism to clear an alarm logged by
another specific trap (in this case, Trap #2).
The specific event indicated by a trap is not severe enough to justify an entry in the
primary server’s alarm log.
●
A trap is defined, but not implemented.
●
A trap # is reserved for future use.
“WRN” is the event’s severity (3rd column of Table 99: G700 Traps and Resolutions).
Issue 3 February 2007
345
Media Gateway Traps
●
●
●
“07/17/2006:13:45“is the event’s date and time stamp.
“121.1.1.2“is the IP address for Telnet access to the alarmed Media Gateway Processor
(MGP).
“cmgMultipleFanFault” is the trap name (4th column of Table 99: G700 Traps and
Resolutions).
SNMP Alarming on the Media Gateway
Setting up SNMP alarm reporting involves two main tasks:
●
Configure the primary server to report alarms
●
Configure the Media Gateway to send SNMP traps
Configure the primary server to report alarms
The primary server may be either an S8300, S8500, S8700, S8710, or S8720 Media Server.
The Media Server supports two methods for reporting alarms. Either method, both, or no
alarm-reporting method may be used at a given site.
●
OSS Method - The server's software applications and hardware devices under its control
can generate Operations Support System (OSS) alarms. These alarms are recorded in the
server logs, and may be reported to Avaya's Initialization and Administration System
(INADS) or another services support agency over the server's modem interface.
To activate OSS alarm notification: The server requires a USB connection to a modem that
is connected to an analog line. The modem must be configured using the Web Interface on
the Set Modem Interface screen and enabled to send and receive calls using the Enable/
Disable Modem screen. Configuration of the OSS alarming method can only be done
using Linux shell commands.
●
SNMP Method - SNMP traps may be sent in User Datagram Protocol (UDP) to a
corporate network management system (NMS) using the Configure Trap Destinations
screen. The OSS and SNMP alarm-notification methods operate independently of each
other. Either or both may be used. Currently, the following NMSs are supported:
●
Communication Manager Fault and Performance Manager, as a standalone application,
or integrated within
●
Avaya Network Management Console with VoIP SystemView
●
HP Openview
To activate SNMP alarm notification: On the server Web Interface, use the Configure Trap
Destinations screen to set up SNMP destinations in the corporate NMS.
346 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Configure the Media Gateway to send SNMP traps
Add INADS Phone Numbers and Enable Alarms to INADS
The following procedure using the primary server’s Linux shell commands administers the
dial-out modem to send alarms in the OSS method. In this example, the primary server is an
S8300, and the services support agency is Avaya’s Initialization and Administration System
(INADS).
Note:
Note:
Perform this task after all Communication Manager administration is complete.
To add INADS phone numbers and enable alarms to INADS
1. Connect the laptop to the Services port of the S8300 Media Server
Note:
Note:
Perform these steps only if the S8300 is the primary controller and the customer
has a maintenance contract with Avaya. Use the information acquired from the
ART tool. See “Run the ART Tool for the INADS IP Address” in Installation and
Upgrades for the Avaya G700 Media Gateway and Avaya S8300 Media Server
555-234-100. Also, a USB modem must have already been installed. See
"Universal Serial Bus (USB) Modems" in the same source.
2. Click Start > Run to open the Run dialog box
3. Enter telnet 192.11.13.6
4. Log in as craft.
5. At the prompt, enter almcall -f INADS phone number -s second-number
6. At the prompt, enter almenable -d b -s y
7. Enter almenable to verify that the alarms are enabled.
8. Log off.
Configure the Media Gateway to send SNMP traps
See G250/G350 Traps for configuring, sending, and resolving traps specific to the G250/G350
Media Gateway.
See G700 Traps for configuring, sending, and resolving traps specific to the G700 Media
Gateway.
Issue 3 February 2007
347
Media Gateway Traps
G250/G350 Traps
This section describes the set of traps that are defined for the Avaya G250/G350 Media
Gateway.
SNMP management is a function of the Avaya MultiService Network Manager. For additional
information, including information on event logs and trap logs, please refer to the Avaya P333T
User’s Guide.
The Dynamic Trap Manager feature of the G250/G350 insures that SNMP traps and alarms are
always sent to the currently active Media Gateway Controller. By default, the Dynamic Trap
Manager sends all SNMP messages to the currently active MGC. The Dynamic Trap Manager
can be configured to manage only a subset of SNMP messages using the snmp-server
dynamic-trap-manager CLI command.
Configuring the G250/G350 to send SNMPv3 alarms
The Avaya G250/G350 Media Gateway uses SNMPv3 for traps and alarms. In order to
configure the Avaya G250/G350 Media Gateway to send SNMP traps to the primary server you
must enable the SNMP agent, specify the SNMP host, and setup SNMP authentication. You
perform these tasks using the following CLI commands:
●
To enable the SNMP agent: ip snmp-server
●
To specify the SNMP host: snmp-server host
●
To create an SNMPv3 view: snmp-server view viewname subtree
●
●
To create an SNMPv3 group and specify its views: snmp-server group groupname
read readviewname write writeviewname notify notifyviewname
To create a user and add the user to a group: snmp-server user username
groupname
Configure the host for G250/G350 SNMP traps
Events occurring on the G250/G350 cause SNMP traps to be generated. The Avaya G250/
G350 Media Gateway can be configured to send SNMP traps to any network management
system (NMS) in the network, including the primary server (S8300/S8500/S8700/S8710). You
specify the destination host using the G250/G350 CLI snmp-server host command. The
traps are sent in User Datagram Protocol (UDP) on the customer’s IP network.
The command syntax is:
snmp-server host {<hostaddress>|<hostname>} {traps|informs}
{{{v1|v2c} <community> | {v3 [auth|noauth|priv] <user>}} [udp-port
<port>] [<notification-type-list>]
348 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
G250/G350 Traps
This command is used both to specify the destination host for SNMP messages, and to define
which SNMP messages are to be sent.
For example, to enable the SNMPv3 manager at IP address 192.16.55.126 to receive
inform-type messages, to use SNMPv3 authentication, and to receive Ethernet port fault
notifications only, enter:
G350-001(super)# snmp-server host 192.16.55.126 informs v3 auth localuser
eth-port-faults
Note:
Note:
You must log in to the CLI as admin to administer SNMP settings.
Refer to Table 95: SNMPv3 Notification Types for a full list of notification types that can be
configured.
Table 95: SNMPv3 Notification Types 1 of 2
Notification Type
Description
all
All notifications
generic
Generic traps
hardware
Hardware faults
rmon
RMON rising/falling alarm
dhcp server
DHCP server error, such as a DHCP IP conflict
detection or notification of no IP address left for
specific network
dhcp-clients
DHCP client error, such as a DHCP client conflict
detection
rtp-stat-faults
RTP statistics: OwS fault/clear traps
rtp-stat-qos
RTP statistics: end-of-call QoS traps
wan
WAN router traps
media-gateway
Media gateway traps (equivalent to G700 MGP
traps)
security
Security traps, such as unAuthAccess,
macSecurity, unknownHostCopy, and
accountLockout
config
Configuration change notifications
eth-port-faults
Ethernet port fault notifications
sw-redundancy
Software redundancy notifications
1 of 2
Issue 3 February 2007
349
Media Gateway Traps
Table 95: SNMPv3 Notification Types 2 of 2
Notification Type
Description
temperature
Temperature warning notifications
cam-change
Changes in CAM notifications
policy
Changes in policy (L3 devices) notifications
link-faults
ITC proprietary link down notifications
supply
Power supply (main and backup) notifications
2 of 2
Configure SNMPv3 authentication
In order to use SNMPv3 authentication, you must create users, groups, and views for the G250/
G350.
The G250/G350 provides several pre-configured views and groups for setting up SNMP
authentication. Refer to Table 96: G250/G350 pre-configured views and Table 97: G250/G350
pre-configured groups for a description of these objects and how they can be used.
Table 96: G250/G350 pre-configured views
Viewname
Description
snmpv1View
A view for backwards compatibility with v1 SNMP users, providing
v1 level access only.
v3ConfigView
A view for an SNMPv3 user with non-administrative privilege.
USM and VACM table access is restricted to changing password
and all download copy config commands.
restricted
A view providing limited access to SNMP objects. Access is
restricted to the system, snmp, snmpEngine, snmpMPDStats, and
usmStats subtreees.
iso
A view providing maximal access, for users with admin privileges.
Table 97: G250/G350 pre-configured groups 1 of 2
Group Name
Security
Model
Security Level
Read View
Name
Write View
Name
ReadCommG
v1
1 (noAuthNoPriv)
snmpv1View
snmpv1View
ReadCommG
v2
1 (noAuthNoPriv)
snmpv1View
snmpv1View
WriteCommG
v1
1 (noAuthNoPriv)
snmpv1View
snmpv1View
Trap View
Name
snmpv1View
1 of 2
350 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
G250/G350 Traps
Table 97: G250/G350 pre-configured groups 2 of 2
Group Name
Security
Model
Security Level
Read View
Name
Write View
Name
Trap View
Name
WriteCommG
v2
1 (noAuthNoPriv)
snmpv1View
snmpv1View
snmpv1View
v3ReadWriteG
v3 (USM)
3 (AuthPriv)
v3configview
v3configview
v3configview
v3ReadOnlyG
v3 (USM)
3 (AuthPriv)
v3configview
initial
v3 (USM)
1 (noAuthNoPriv)
restricted
restricted
restricted
v3AdminViewG
v3 (USM)
3 (AuthPriv)
iso
iso
iso
v3configview
2 of 2
G250/G350 traps and resolutions
Although these alarms can be viewed from the primary server, they are normally resolved from
within the Avaya G250/G350 Media Gateway. The G250/G350 generates the following traps.
Follow the error resolution procedures in Table 98: G250/G350 Traps and Resolutions to
resolve errors indicated by these traps.
Table 98: G250/G350 Traps and Resolutions 1 of 16
Enterprise
Trap
ID
Name
Msg
Facility
Severity
Description / Resolution
snmpTraps
1
coldStart
Boot
Warning
The entity is reinitializing itself in such a
way as to potentially cause the alteration
of either the agent’s configuration or the
entity’s implementation.
This trap is always enabled.
snmpTraps
2
warmStart
Boot
Warning
The entity is reinitializing itself in such a
way as to keep both the agent’s
configuration and the entity’s
implementation intact.
This trap is always enabled.
snmpTrap
3
linkDown
System
Warning
There is a failure in one of the
communication links in the agent’s
configuration.
snmpTraps
4
linkUp
System
Warning
One of the communication links in the
agent’s configuration has come up.
snmpTrap
5
authenticFailure
Security
Notification
The protocol is not properly authenticated.
rmon
1
risingAlarm
Threshold
Warning
An alarm entry has crossed its rising
threshold.
rmon
2
fallingAlarm
Threshold
Warning
An alarm entry has crossed its falling
threshold.
frame-relay
1
frDLCIStatusChange
A DLCI has been created or deleted, or
has state changes.
1 of 16
Issue 3 February 2007
351
Media Gateway Traps
Table 98: G250/G350 Traps and Resolutions 2 of 16
Enterprise
Trap
ID
Name
Msg
Facility
Severity
Description / Resolution
avayaG350
1
config
The configuration has been changed.
avayaG350
2
fault
A fault has been generated.
avayaG350
12
deleteSWRedundancyTrap
Switch
Fabric
Info
A redundancy link has been deleted.
avayaG350
13
createSWRedundancyTrap
Switch
Fabric
Info
A redundancy link has been created for
the specified ports.
avayaG350
27
duplicateIPTrap
Router
Warning
A duplicate IP address has been
identified.
avayaG350
30
wanPhysicalAlarmOn
Wan
Critical
An E1/T1 serial cable has been
disconnected.
avayaG350
31
wanPhysicalAlarmOff
Wan
Notification
An E1/T1 serial cable has been
reconnected.
avayaG350
32
wanLocalAlarmOn
Wan
Error
A local alarm (such as LOS) has been
generated.
avayaG350
33
wanLocalAlarmOff
Wan
Notification
A local alarm (such as LOS) has been
cleared.
avayaG350
34
wanRemoteAlarmOn
Wan
Error
A remote alarm (such as AIS) has been
generated.
avayaG350
35
wanRemotetAlarmOff
Wan
Notification
A remote alarm (such as AIS) has been
cleared.
avayaG350
36
wanMinorAlarmOn
Wan
Warning
avayaG350
37
wanMinorAlarmOff
Wan
Notification
avayaG350
60
lntPolicyChangeEvent
Policy
Info
avayaG350
62
ipPolicyAccessControlListLvlRuleTrap
Policy
avayaG350
64
lntPolicyAccessControlViolationFit
Policy
avayaG350
68
lntUnAuthorizedAccessEvent
avayaG350
70
ipArpViolationTrap
The active policy list for the specified
device or module has changed.
A packet fragment has been denied
access on the specified interface
Warning
A packet has violated a policy rule on the
specified interface. The trap includes
information about the slot where the event
occurred. The id of the rule that was
violated in the current rules table, and the
quintuplet that identifies the faulty packet.
This trap will not be sent at intervals
smaller than one minute for identical
information in the varbinds list variables.
An attempt has been made to logon to the
device with an invalid userid/password.
2 of 16
352 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
G250/G350 Traps
Table 98: G250/G350 Traps and Resolutions 3 of 16
Enterprise
Trap
ID
Name
Msg
Facility
avEntTraps
1
avEntFanFlt
Temp
Severity
Description / Resolution
There is a faulty fan on the device.
1. Verify there are faults in the
system. Use the Avaya G250/G350
Media Gateway CLI command
show faults to display any faults on
the G250/G350.
2. If there is a fan/temperature fault,
check to see if the fans are
working, and/or if there is sufficient
space around the G250/G350 for
air circulation.
3. Maintenance software monitors
voltages applied to the media
modules and other components of
the G250/G350, and compares
these to the general power supply
unit (PSU) status bit. If none of
these voltages are out of tolerance,
but the PSU status indicates
failure, this generates the fan fault,
which will be indicated in the show
faults command output. Replace
the entire G250/G350. Fans and
the PSU are not field replaceable.
avEntTraps
2
avEntFanOk
Temp
Notification
A faulty fan has returned to normal
functioning.
3 of 16
Issue 3 February 2007
353
Media Gateway Traps
Table 98: G250/G350 Traps and Resolutions 4 of 16
Enterprise
Trap
ID
Name
Msg
Facility
avEntTraps
4
avEnt48vPwrFlt
Supply
Severity
Description / Resolution
There is a problem with the 48V power
supply.
1. Check voltages. Use the CLI
command show voltages to
determine voltages for media
modules and other components of
the G250/G350. Voltage may be
reduced by a short in one of the
media modules or a bad power
supply.
2. Systematically, remove each media
module to determine if one of the
media modules is responsible for
reducing the voltage levels.
Replace faulty media module.
3. If the alarm clears in 10-20
seconds, it most likely was a
voltage spike. Do not replace the
G250/G350. Use a power monitor
to monitor the power line.
4. If a brown-out condition is
suspected, use a power monitor to
monitor the power line.
5. If the fault persists and the show
voltages command continues to
show the level is out of tolerance,
replace the G250/G350.
avEntTraps
5
avEnt48vPwrFltOk
Supply
The problem with the 48V power supply
has been corrected.
avEntTraps
7
avEnt5vPwrFlt
Supply
There is a problem with the 5V power
supply.
To resolve the problem, follow the steps
for the avEnt48vPwrFlt trap.
avEntTraps
8
avEnt5vPwrFltOk
Supply
The problem with the 5V power supply has
been corrected.
avEntTraps
10
avEnt3300mvPwrFlt
Supply
There is a problem with the 3.3V power
supply.
To resolve the problem, follow the steps
for the avEnt48vPwrFlt trap.
avEntTraps
11
avEnt3300mvPwrFltOk
Supply
The problem with the 3.3V power supply
has been corrected.
avEntTraps
13
avEnt2500mvPwrFlt
Supply
There is a problem with the 2.5V power
supply.
To resolve the problem, follow the steps
for the avEnt48vPwrFlt trap.
avEntTraps
16
avEnt1800mvPwrFlt
Supply
There is a problem with the 1.8V power
supply.
To resolve the problem, follow the steps
for the avEnt48vPwrFlt trap.
4 of 16
354 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
G250/G350 Traps
Table 98: G250/G350 Traps and Resolutions 5 of 16
Enterprise
Trap
ID
Name
Msg
Facility
Severity
Description / Resolution
avEntTraps
14
avEnt2500mvPwrFltOk
Supply
The problem with the 2.5V power supply
has been corrected.
avEntTraps
17
avEnt1800mvPwrFltOk
Supply
The problem with the 1.8V power supply
has been corrected.
avEntTraps
19
avEnt1600mvPwrFlt
Supply
There is a problem with the 1.6V power
supply.
To resolve the problem, follow the steps
for the avEnt48vPwrFlt trap.
avEntTraps
20
avEnt1600mvPwrFltOk
Supply
The problem with the 1.6V power supply
has been corrected.
avEntTraps
22
avEntAmbientHiThresholdTempFlt
Temp
The ambient temperature in the device is
above the acceptable temperature
range.
1. Verify there are faults in the
system. Use the Avaya G250/G350
Media Gateway CLI command
show faults to display any faults on
the G250/G350.
2. If there is a temperature fault, turn
off the G250/G350 and allow it to
cool.
3. Reboot the G250/G350. Check to
see if the fans are working and/or if
there is sufficient space around the
G250/G350 for air circulation. Use
the CLI show faults command to
check for fan problems.
4. Low voltage may be responsible for
slower fans. Voltage may be
reduced by a short in one of the
media modules or a bad power
supply. If there are no fan faults,
use the CLI command show
voltages to display voltages applied
to components on the motherboard
and to the media modules.
5. If the media module voltage is out
of tolerance, systematically,
remove each media module to
determine if one of the media
modules is responsible for
reducing the voltage level. If one is
found, replace the media module.
If no media module is found to be bad, the
power supply is suspect. Replace the
G250/G350.
avEntTraps
23
avEntAmbientHiThresholdTempOk
Temp
The ambient temperature in the device
has returned to the acceptable range.
5 of 16
Issue 3 February 2007
355
Media Gateway Traps
Table 98: G250/G350 Traps and Resolutions 6 of 16
Enterprise
Trap
ID
Name
Msg
Facility
Severity
Description / Resolution
avEntTraps
24
avEntAmbientLoThresholdTempFlt
Temp
The ambient temperature in the device is
below the acceptable temperature range.
avEntTraps
25
avEntAmbientLoThresholdTempOk
Temp
The ambient temperature in the device
has returned to the acceptable range.
6 of 16
356 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
G250/G350 Traps
Table 98: G250/G350 Traps and Resolutions 7 of 16
Enterprise
Trap
ID
Name
cmgTrapTypes
30
cmgSyncSignalFault
Msg
Facility
Severity
Description / Resolution
Major
The synchronization signal has been lost.
Check that the provisioned clock-sync
source has a good signal using the Media
Gateway CLI command show sync timing.
To set synchronization timing sources on
E1/T1 MM or MM710:
1. If the E1/T1 MM has not been
added properly on the Media
Server, you must use the SAT
command ADD DS1 before using
the Media Gateway CLI commands
set sync interface or set sync
source.
2. Specify the primary and secondary
clock sources for synchronizing the
E1/T1 span, using the CLI
command set synch interface.
Note: The local clock is “built-in”
and not provisionable.
3. Use a set sync source command to
set to the specific MM710 E1/T1
media module to be used as the
active clock reference.
4. Use a show sync timing command
to ensure that the source is
provisioned and active, or visually
inspect the Yellow LED on the
MM710 media module.
Note: When the Yellow LED is on
2.7 seconds and off 0.3 seconds,
this means the tone-clock
synchronizer is in “active” mode,
and an external synchronization
source is being used as a
synchronization reference. Setting
the sync timing was successful.
When the Yellow LED is on 0.3
seconds and off 2.7 seconds, this
means the tone-clock synchronizer
is in “active” mode and the internal
(on-board) clock is being used as a
synchronization reference. Setting
the sync timing was not successful.
5. If there is more than one MM710
media module, and they have been
set up as primary and secondary,
this behavior could be on the
second and not the timing of the
bus.
cmgTrapTypes
31
cmgSyncSignalClear
The synchronization signal has been
regained.
7 of 16
Issue 3 February 2007
357
Media Gateway Traps
Table 98: G250/G350 Traps and Resolutions 8 of 16
Enterprise
Trap
ID
Name
Msg
Facility
Severity
Description / Resolution
cmgTrapTypes
32
cmgVoipHardwareFault
Major
A DSP complex serving the VoIP engines
has failed.
cmgTrapTypes
33
cmgVoipHardwareClear
cmgTrapTypes
34
cmgSyncSignalWarn
cmgTrapTypes
35
cmgSyncWarnClear
cmgTrapTypes
36
cmgSyncSignalExcess
cmgTrapTypes
37
cmgSyncExcessClear
cmgTrapTypes
50
cmgModuleRemove
A media module has been removed.
cmgTrapTypes
52
cmgModuleInsertFault
The insertion sequence for a media
module has failed.
cmgTrapTypes
53
cmgModuleInsertSuccess
A media module has been inserted.
cmgTrapTypes
57
cmgDataModuleAwohConflict
cmgTrapTypes
71
cmgFirmwareDownloadSuccess
The Media Gateway successfully
downloaded a software or configuration
file.
cmgTrapTypes
73
cmgRegistrationSuccess
The Media Gateway has successfully
registered with a Media Controller.
cmgTrapTypes
74
cmgMgManualReset
The Media Gateway is beginning a
user-requested reset operation.
cmgTrapTypes
75
cmgModuleManualReset
A media module is beginning a
user-requested reset operation.
The DSP complex serving the VoIP
engines has returned to normal
functioning.
8 of 16
358 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
G250/G350 Traps
Table 98: G250/G350 Traps and Resolutions 9 of 16
Enterprise
Trap
ID
Name
cmgTrapTypes
90
cmgMemoryFault
Msg
Facility
Severity
Description / Resolution
Major
The Media Gateway has detected a low
memory condition. This occurs when a
software module is unable to allocate
memory, or the available memory falls
below 4 MB.
1. Check the Media Gateway and
insure that it has the latest version
of firmware installed. If it does not,
install the latest version of firmware
and continue to monitor.
2. If this trap occurs infrequently and
is automatically cleared, the trap
may be due to an unusual transient
condition. Monitor future traps.
3. If this trap occurs frequently and is
automatically cleared, it is likely
that the Media Gateway software
has the wrong limits set for its
memory monitoring. These limits
are hard coded in the software.
Speak to an Avaya technical
professional.
4. If this trap occurs and does not
clear, the Media Gateway may be
functionally impaired. Do not reset
the Media Gateway. Escalate and
have Tier 3 personnel capture the
trap information and the event logs
for analysis.
5. If this trap occurs and the Media
Gateway Processor automatically
resets, then a severe processor
memory shortage occurred.
Escalate and have Tier 3 personnel
capture the trap information and
the event logs for analysis.
cmgTrapTypes
91
cmgMemoryClear
The low memory condition has been
cleared. This occurs when the available
memory rises above 5 MB.
9 of 16
Issue 3 February 2007
359
Media Gateway Traps
Table 98: G250/G350 Traps and Resolutions 10 of 16
Enterprise
Trap
ID
Name
cmgTrapTypes
94
cmgFirmwareDownloadFault
Msg
Facility
Severity
Description / Resolution
Major
An attempt to download a software
module has failed.
1. Check the event log to find the
specific error.
2. Troubleshoot the specific error
according to the information found.
For example, if the string “File not
found” appears in the log, then
verify that the image file:
a. Exists
b. Has the correct name
c. Resides in the correct directory
cmgTrapTypes
98
cmgIccMissingFault
cmgTrapTypes
99
cmgIccMissingClear
cmgTrapTypes
100
cmgIccAutoReset
cmgTrapTypes
101
cmgIccAutoResetClear
cmgTrapTypes
102
cmgPrimaryControllerFault
Major
An internal communications controller
(S8300), expected in slot 1, is missing.
A missing internal communications
controller (S8300) has been found.
Major
The Media Gateway automatically reset
the internal communications controller.
Major
The Media Gateway cannot contact the
first controller in its controller list.
1. Verify that the controller list is
correct. From the CLI, use the
command show mgc list. The IP
address should match the Media
Server or the Media Server IP
addresses.
2. If needed, correct this in configure
mode in the CLI. Clear the mgc list
first with the clear mgc list
command. Then use a set mgc list
with the correct IP addresses.
3. Verify that the primary controller is
up.
4. If so, shut down every LSP
cmgTrapTypes
103
cmgPrimaryControllerClear
10 of 16
360 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
G250/G350 Traps
Table 98: G250/G350 Traps and Resolutions 11 of 16
Enterprise
Trap
ID
Name
cmgTrapTypes
104
cmgNoControllerFault
Msg
Facility
Severity
Description / Resolution
Major
The Media Gateway does not have any
controllers in its controller list.
1. Verify that the controller list is
empty. From the CLI, use the
command show mgc list to verify
that there are no controllers listed.
2. If none are listed, correct this by
adding the correct IP address of
the S8700/S8710/S8500/S8300. In
the CLI’s 'configure' mode, use a
set mgc list command with the
correct IP address.
cmgTrapTypes
105
cmgnoControllerClear
cmgTrapTypes
106
cmgRegistrationFault
The cmgNoControllerFault trap has been
cleared.
Major
The Media Gateway cannot register with
any controllers in its controller list.
1. Verify that the controller list is
correct. From the CLI, use the
command show mgc list. The IP
address should match the Media
Server CLAN or the Media Server
IP addresses.
2. If needed, correct this in the CLI’s
'configure' mode. Clear the mgc list
with the clear mgc list command.
Then use a set mgc list with the
correct IP addresses.
3. If the IP address in the mgc list
matches the Media Server CLAN
or the Media Server IP addresses,
there may be a network problem.
4. Verify that the primary controller is
up.
11 of 16
Issue 3 February 2007
361
Media Gateway Traps
Table 98: G250/G350 Traps and Resolutions 12 of 16
Enterprise
Trap
ID
Name
cmgTrapTypes
108
cmgH248LinkDown
Msg
Facility
Severity
Description / Resolution
Minor
An H.248 link between the Media
Gateway and its controller is down.
1. Check the S8300, S8500, or
S8700/S8710. If down, bring up.
2. If not, check the G250/G350
administration.
Since the following command
causes a brief service outage, it
should only be executed at the
customer’s convenience.
3. If the administration is correct,
reboot the G250/G350.
4. If the problem persists, check
network connectivity. Use ping or
traceroute to the S8300/S8500/
S8700/S8710 to check
connectivity.
5. If the problem persists, speak to an
Avaya technical professional.
cmgTrapTypes
109
cmgH248LinkUp
An H.248 link between the Media Gateway
and its controller that was down has come
back up.
12 of 16
362 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
G250/G350 Traps
Table 98: G250/G350 Traps and Resolutions 13 of 16
Enterprise
Trap
ID
Name
cmgTrapTypes
114
cmgMgAutoReset
Msg
Facility
Severity
Description / Resolution
Warning
The Media Gateway automatically reset.
This may be due to a critical error from
which the Media Gateway could not
recover. It may be due to a maintenance
test running on the call controller. It may
also be due to the Media Gateway’s
reregistration with a call controller after
being out of contact for too long.
1. Check to see if a maintenance test
that resets the processor was run.
2. Check to see if the reset was due
to the link with the call controller
going down. If so, follow call
controller link failure
troubleshooting procedures.
3. Check the Media Gateway and
insure that it has the latest version
of firmware installed. If it does not,
install the latest version of firmware
and continue to monitor.
4. If this trap occurs infrequently, the
trap may be due to an unusual
transient condition. Monitor future
traps.
5. If this trap occurs and the Media
Gateway is frequently resetting,
manually reset the media gateway.
Escalate and have Tier 3 personnel
capture the trap information and
the event logs for analysis.
6. If this trap occurs frequently and
the Media Gateway is not resetting,
the Media Gateway may be
functionally impaired, and is not
capable of resetting itself to restore
service. If service is impaired, reset
the Media Gateway manually.
Escalate and have Tier 3 personnel
capture the trap information and
the event logs for analysis.
13 of 16
Issue 3 February 2007
363
Media Gateway Traps
Table 98: G250/G350 Traps and Resolutions 14 of 16
Enterprise
Trap
ID
Name
cmgTrapTypes
116
cmgModuleAutoReste
Msg
Facility
Severity
Description / Resolution
Warning
cmgModuleAutoReset — A media
module in the Media Gateway
automatically reset (rebooted). To
resolve the problem, take the following
steps:
1. Check if a maintenance test that
resets the media module was run.
2. Check the media module and
insure that it has the latest version
of firmware installed. If not, install
the latest version of firmware and
continue to monitor.
3. If this trap occurs infrequently, the
trap may be due to an unusual
transient condition. Monitor future
traps.
4. If this trap occurs and the media
module does not return to service,
or if this trap occurs frequently,
attempt to reset the failing module
from the SAT or CLI and see if this
returns it to stable service.
5. If manually resetting the media
module does not return it to
service, and if a spare media
module of the same time is
available, replace the failing media
module with the spare and see if
the spare media module goes into
service. If so, follow procedures for
dealing with the original bad media
module.
6. If the spare media module fails to
go into service, it is possible that
the spare media module is also
bad. If not, manually reset the
Media Gateway at a time
convenient to the customer. If this
restores service, both the original
and the spare media modules can
be considered okay. The problem
is probably with the Media
Gateway itself. Escalate and have
Tier 3 personnel capture the trap
information and the event logs for
analysis.
cmgTrapTypes
117
cmgModuleAutoResetClear
cmgTrapTypes
118
cmgModulePostFault
Minor
A media module failed its power-on
start-up test.
14 of 16
364 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
G250/G350 Traps
Table 98: G250/G350 Traps and Resolutions 15 of 16
Enterprise
Trap
ID
Name
cmgTrapTypes
119
cmgModulePostClear
cmgTrapTypes
122
cmgConfigUpoadFault
Msg
Facility
Severity
Description / Resolution
Major
An attempt to upload a configuration file
failed.
1. Check the event log for an error
message during the backup/restore
process.
2. Troubleshoot the specific error
according to the information found.
3. Retry the upload (backup)
command; for example:
copy startup-config tftp <filename>
<ip address>
CAUTION: Since the following
command causes a brief service
outage, it should only be executed
at the customer’s convenience.
4. If the problem persists, reboot the
G250/G350.
cmgTrapTypes
124
cmgVoipOccFault
cmgTrapTypes
125
cmgVoipOccClear
cmgTrapTypes
126
cmgVoipAvgOccFault
cmgTrapTypes
127
cmgVoipAvgOccClear
15 of 16
Issue 3 February 2007
365
Media Gateway Traps
Table 98: G250/G350 Traps and Resolutions 16 of 16
Enterprise
Trap
ID
Name
cmgTrapTypes
128
cmgVoipAutoReset
Msg
Facility
Severity
Description / Resolution
Warning
The VoIP module in the Media Gateway
automatically reset.To resolve the
problem, take the following steps:
1. Check if a maintenance test that
resets the VoIP module was run.
2. Check to see if the VoIP module
had its IP address re-administered.
3. Check to see if the IP address
administered on the VoIP module is
correct.
4. Check to see if the IP address of
the Media Gateway itself can be
pinged. Physical or logical
connectivity issues (cabling or
routing problems) in the data
network can cause ping failures.
5. Check the VoIP module and insure
that it has the latest version of
firmware installed. If not, install the
latest version of firmware and
continue to monitor.
6. If this trap occurs infrequently, the
trap may be due to an unusual
transient condition. Monitor future
traps.
7. If this trap occurs and the VoIP
module does not return to service,
or if this trap occurs frequently,
attempt to reset the failing module
from the SAT or CLI.
8. Manually reset the Media Gateway
at a time convenient to the
customer. If this restores service,
the problem is probably with the
Media Gateway itself. Capture the
trap information. If possible,
capture the event logs, using the
show event-log CLI command, for
analysis. Escalate.
9. If none of this works, capture the
trap information. If possible,
capture the event logs, using the
show event-log CLI command, for
analysis. Escalate.
cmgTrapTypes
129
cmgVoipAutoResetClear
16 of 16
366 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
G700 Traps
G700 Traps
Configure the G700 to send SNMP traps
Configuring the G700 Media Gateway to send SNMP traps to the primary server can be
accomplished by two commands:
●
●
Layer 2 Switching Processor CLI command: set snmp community trap [community
string]
Media Gateway Processor (MGP) CLI command: set snmp trap <IP address>
enable
Configure an SNMP community string for traps
SNMP requires community strings to be used for each SNMP "request". Only three community
strings can be set on the G700 — one each for read requests, write requests, and traps. The
command for traps is set snmp community trap [community string].
To configure an SNMP community string for traps
1. Open the Run dialog box.
2. Enter telnet <IP address of L2 Processor>
3. Log in as root.
4. At the L2 Processor CLI prompt, enter set snmp community trap [community
string]
5. Enter exit
Configure the destination for G700 SNMP traps
Events occurring on the G700 cause SNMP traps to be generated. The G700 MGP can be
configured to send SNMP traps to any network management system (NMS) in the network,
including the primary server (S8300/S8700). The MGP CLI set snmp trap command is the
way to configure the NMS network element that will receive those traps. The traps are sent in
User Datagram Protocol (UDP) on the customer’s IP network.
Issue 3 February 2007
367
Media Gateway Traps
The command syntax is:
set SNMP trap <IP address> {enable|disable}
[{all|power|temp|app|module|config|voice|operations}]
where <IP address> is the IP address of the NMS trap receiver that will be receiving the
traps from the G700, and
[{all|power|temp|app|module|config|voice|operations}] indicates the groups
whose traps will be sent to the specified receiver. If no keywords follow the IP address entry,
then all traps will be enabled for the specified receiver.
If "enable" or "disable" is used without a trap designation keyword, then all traps is
assumed. Up to ten trap receivers can be configured.
To configure the destination for G700 SNMP traps
1. From the L2 Processor CLI, enter session mgp
2. At the mg-xxx-n(super-user) prompt, enter configure
3. At the mg-xxx-n(configure) prompt, enter set snmp trap <IP address> enable
4. Enter exit
368 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
G700 Traps
G700 Traps and Resolutions
Although alarms can be viewed from the primary server, they are normally resolved from within
the G700 Media Gateway. The G700 generates the following traps. Follow the error resolution
procedures in Table 99: G700 Traps and Resolutions to resolve errors indicated by these traps.
Table 99: G700 Traps and Resolutions 1 of 22
Event
ID
Trap #
Alarm
Level
Description / Recommendation
1
2
WRN
cmgMultipleFanFault — At least two G700 fans have been
operating at less than 90% of their nominal speed for 5 minutes
or more. This may be an early warning of overheating.
1. Verify there are faults in the system. Use the Avaya G700
Media Gateway Processor (MGP) Command Line Interface
(CLI) command show faults to display any faults on the
G700. Check for voltage alarms first. If it is a voltage alarm,
fix the voltage alarm. Low voltage may be responsible for
slower fans. Voltage may be reduced by a short in one of the
media modules or there may be a bad power supply.
Systematically remove each media module to determine if
one of the media modules is responsible for reducing the
voltage levels.
2. If there is a fan/temperature fault, check to see if the fans are
working, and/or if there is sufficient space around the G700
for air circulation.
3. f none of the voltages are out of tolerance, but the PSU
status indicates failure, replace the entire G700. Fans and
the PSU are not field replaceable.
1
3
WRN
cmgMultipleFanClear - at least three fans are operating normally.
The system should be operable indefinitely without overheating.
1 of 22
Issue 3 February 2007
369
Media Gateway Traps
Table 99: G700 Traps and Resolutions 2 of 22
Event
ID
Trap #
Alarm
Level
Description / Recommendation
2
4
MIN
cmgPsuFanBriefFault — The power supply fan has been
operating at less than 90% of its optimal speed for 10 minutes or
more, but less than 15 minutes. This may be an early warning of
overheating.
1. Verify there are faults in the system. Use the Avaya G700
Media Gateway Processor (MGP) Command Line Interface
(CLI) command show faults to display any faults on the
G700. Check for voltage alarms first. If it is a voltage alarm,
fix the voltage alarm. Low voltage may be responsible for
slower fans. Voltage may be reduced by a short in one of the
media modules or there may be a bad power supply.
Systematically remove each media module to determine if
one of the media modules is responsible for reducing the
voltage levels.
2. If there is a fan/temperature fault, check to see if the fans are
working, and/or if there is sufficient space around the G700
for air circulation.
3. f none of the voltages are out of tolerance, but the PSU
status indicates failure, replace the entire G700. Fans and
the PSU are not field replaceable.
2
5
MIN
cmgPsuFanBriefClear - The power supply fan is operating
normally.
2 of 22
370 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
G700 Traps
Table 99: G700 Traps and Resolutions 3 of 22
Event
ID
Trap #
Alarm
Level
Description / Recommendation
3
6
MIN
cmgPsuFanProlongedFault — The power supply fan has been
operating at less than 90% of its optimal speed for 15 minutes or
more. This may be an early warning of overheating.
1. Verify there are faults in the system. Use the Avaya G700
Media Gateway Processor (MGP) Command Line Interface
(CLI) command show faults to display any faults on the
G700. Check for voltage alarms first. If it is a voltage alarm,
fix the voltage alarm. Low voltage may be responsible for
slower fans. Voltage may be reduced by a short in one of the
media modules or there may be a bad power supply.
Systematically remove each media module to determine if
one of the media modules is responsible for reducing the
voltage levels.
2. If there is a fan/temperature fault, check to see if the fans are
working, and/or if there is sufficient space around the G700
for air circulation.
3. f none of the voltages are out of tolerance, but the PSU
status indicates failure, replace the entire G700. Fans and
the PSU are not field replaceable.
3
7
8-9
MIN
cmgPsuFanProlongedClear - The power supply fan is operating
normally.
Reserved
3 of 22
Issue 3 February 2007
371
Media Gateway Traps
Table 99: G700 Traps and Resolutions 4 of 22
Event
ID
Trap #
Alarm
Level
Description / Recommendation
4
10
MIN
cmgCpuTempWarningFault — The temperature sensor at the
CPU has exceeded its warning threshold.
1. Verify there are faults in the system. Use the Avaya G700
Media Gateway Processor (MGP) Command Line Interface
(CLI) command show faults to display any faults on the
G700.
2. If there is a temperature fault, turn off the G700 and allow it to
cool.
3. Reboot the G700. Check to see if the fans are working and/
or if there is sufficient space around the G700 for air
circulation. Use the MGP CLI show faults command to
check for fan problems.
4. Low voltage may be responsible for slower fans. Voltage may
be reduced by a short in one of the Media Modules or a bad
power supply. If there are no fan faults, use the MGP CLI
command show voltages to display voltages applied to
components on the motherboard and to the Media Modules.
5. If the Media Module voltage is out of tolerance,
systematically, remove each Media Module to determine if
one of the Media Modules is responsible for reducing the
voltage level. If one is found, replace the Media Module.
6. If no Media Module is found to be bad, the power supply is
suspect. Replace the G700.
4
11
MIN
cmgCpuTempWarningClear - The temperature sensor at the
CPU has dropped below its warning threshold.
4 of 22
372 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
G700 Traps
Table 99: G700 Traps and Resolutions 5 of 22
Event
ID
Trap #
Alarm
Level
Description / Recommendation
5
12
MIN
cmgDspTempWarningFault — The temperature sensor at the
DSP complex has exceeded its warning threshold.
1. Verify there are faults in the system. Use the Avaya G700
Media Gateway Processor (MGP) Command Line Interface
(CLI) command show faults to display any faults on the
G700.
2. If there is a temperature fault, turn off the G700 and allow it to
cool.
3. Reboot the G700. Check to see if the fans are working and/
or if there is sufficient space around the G700 for air
circulation.
4. Low voltage may be responsible for slower fans. Voltage may
be reduced by a short in one of the Media Modules or a bad
power supply. If there are no fan faults, use the MGP CLI
command show voltages to display voltages applied to
components on the motherboard and to the Media Modules.
5. If the Media Module voltage is out of tolerance,
systematically, remove each Media Module to determine if
one of the Media Modules is responsible for reducing the
voltage level. If one is found, replace the Media Module.
6. If no Media Module is found to be bad, the power supply is
suspect. Replace the G700.
5
13
MIN
cmgDspTempWarningClear - The temperature sensor at the
DSP complex has dropped below its warning threshold.
6
14
MAJ
cmgTempShutdownFault — The CPU temperature sensor has
exceeded its shutdown threshold. The system is about to begin
controlled shutdown.
1. Turn off the G700 and allow it to cool.
2. Check the fans and replace the G700 as necessary. Fans
are not field-replaceable.
6
15
Reserved
5 of 22
Issue 3 February 2007
373
Media Gateway Traps
Table 99: G700 Traps and Resolutions 6 of 22
Event
ID
Trap #
Alarm
Level
Description / Recommendation
7
16
MAJ
cmgMgpPowerFault — The voltage reading at the +5.1V power
source serving the media gateway processor is out of tolerance.
1. Replace the power supply only if the problem is persistent.
Do not replace the power supply if there is a suspected
voltage spike or temporary brown-out.
7
17
MAJ
cmgMgpPowerClear - The voltage reading at the +5.1V power
source serving the media gateway processor is back within its
tolerance range.
8
18
MAJ
cmgMediaModulePowerFault — The voltage reading at the -48V
power source serving the media modules is out of tolerance.
1. Replace the power supply only if the problem is persistent.
do not replace the power supply if there is a suspected
voltage spike or temporary brown-out.
8
19
MAJ
cmgMediaModulePowerClear - The voltage reading at the -48V
power source serving the media modules is back within its
tolerance range.
9
20
MAJ
cmgVoipPowerFault — The voltage reading at the +3.4V power
source serving the VoIP complexes is out of tolerance.
1. Replace the power supply only if the problem is persistent.
Do not replace the power supply if there is a suspected
voltage spike or temporary brown-out.
9
21
MAJ
cmgVoipPowerClear - The voltage reading at the +3.4V power
source serving the VoIP complexes is back within its tolerance
range.
10
22
MAJ
cmgDspPowerFault — The voltage reading at the +1.58V power
source serving the DSP units is out of tolerance.
1. Replace the power supply only if the problem is persistent.
Do not replace the power supply if there is a suspected
voltage spike or temporary brown-out.
10
23
MAJ
cmgDspPowerClear - The voltage reading at the +1.58V power
source serving the DSP units is back within its tolerance range.
6 of 22
374 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
G700 Traps
Table 99: G700 Traps and Resolutions 7 of 22
Event
ID
Trap #
Alarm
Level
Description / Recommendation
11
24
MAJ
cmg8260PowerFault — The voltage reading at the +2.5V power
source serving the 8260 processor is out of tolerance.
1. Replace the power supply only if the problem is persistent.
Do not replace the power supply if there is a suspected
voltage spike or temporary brown-out.
11
25
MAJ
cmg8260PowerClear - The voltage reading at the +2.5V power
source serving the 8260 processor is back within its tolerance
range.
12
26
MAJ
cmgAuxPowerFault - The voltage reading at the -48V auxiliary
power source serving the end points is out of tolerance.
1. No action is required.
12
27
MAJ
cmgAuxPowerClear - The voltage reading at the -48V auxiliary
power source serving the end points is back within its tolerance
range
13
28
MAJ
cmgFanPowerFault - The voltage reading at the +12V auxiliary
power source serving the fans is out of tolerance.
1. Replace the power supply only if the problem is persistent.
Do not replace the power supply if there is a suspected
voltage spike or temporary brown-out.
13
29
MAJ
cmgFanPowerClear - The voltage reading at the +12V auxiliary
power source serving the fans has returned to within its tolerance
range.
7 of 22
Issue 3 February 2007
375
Media Gateway Traps
Table 99: G700 Traps and Resolutions 8 of 22
Event
ID
Trap #
Alarm
Level
Description / Recommendation
14
30
MAJ
cmgSyncSignalFault — Synchronization signal lost.
1. Check that the provisioned clock-sync source has a good
signal by entering the Media Gateway Processor (MGP)
Command Line Interface (CLI) command
show sync timing
Procedure for setting synchronization timing sources on E1/T1
MM or MM710:
1. Be sure that the E1/T1 MM has been added properly on the
Avaya S8300 Media Server or Avaya S8700 Media Server,
otherwise, using the System Access Terminal (SAT), enter
the add DS1 command before using the MGP CLI and
entering a set sync interface or set sync source
command. Otherwise, the MGP CLI will not allow these
commands to be executed.
2. Using the MGP’s CLI, first specify the primary and secondary
clock sources for synchronizing the E1/T1 span with the set
synch interface command.
Note: The internal clock source is not specified from the CLI only the primary and secondary. The local clock is "built-in"
and not administrable.
3. Enter a set sync source command to set to the specific
MM710 E1/T1 Media Module to be used as the active clock
reference.
4. Verify whether or not these commands were executed by
issuing a show sync timing command to ensure that the
source is provisioned and active, or visually inspect the
Yellow LED on the MM710 Media Module.
Note: When the Yellow LED is on 2.7 seconds and off 0.3
seconds, this means the tone-clock synchronizer is in
“active” mode, and an external synchronization source is
being used as a synchronization reference. Setting the sync
timing was successful.
When the Yellow LED is on 0.3 seconds and off 2.7 seconds,
this means the tone-clock synchronizer is in “active” mode
and the internal (on-board) clock is being used as a
synchronization reference. Setting the sync timing was not
successful.
8 of 22
376 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
G700 Traps
Table 99: G700 Traps and Resolutions 9 of 22
Event
ID
Trap #
Alarm
Level
14
30
MAJ
(cont’d)
Description / Recommendation
5. Verify whether or not these commands were executed by
issuing a show sync timing command to ensure that the
source is provisioned and active, or visually inspect the
Yellow LED on the MM710 Media Module.
Note: When the Yellow LED is on 2.7 seconds and off 0.3
seconds, this means the tone-clock synchronizer is in
“active” mode, and an external synchronization source is
being used as a synchronization reference. Setting the sync
timing was successful.
When the Yellow LED is on 0.3 seconds and off 2.7 seconds,
this means the tone-clock synchronizer is in “active” mode
and the internal (on-board) clock is being used as a
synchronization reference. Setting the sync timing was not
successful.
6. If there is more than one MM710 Media Module, and they
have been set up as primary and secondary, this behavior
could be on the second and not the timing of the bus.
For more details, please consult the maintenance documentation
under LEDs and E1/T1 Media Module, or see
http://support.avaya.com/elmodocs2/S8300/cd/index.htm
14
31
MAJ
cmgSyncSignalClear - Synchronization signal normal.
15
32
MAJ
cmgVoipHardwareFault — One or more of the DSP complexes
serving the VoIP engines has failed.
1. Check the IP configuration.
2. Reset or replace the Media Module.
15
16
33
MAJ
cmgVoipHardwareClear - All of the DSP complexes serving the
VoIP engines are back in service.
34 49
Reserved
50
cmgModuleRemove - A media modules has been removed.
51
Reserved
52
MAJ
cmgModuleInsertFault — Media module insertion sequence has
failed.
1. Reset or replace the media module.
9 of 22
Issue 3 February 2007
377
Media Gateway Traps
Table 99: G700 Traps and Resolutions 10 of 22
Event
ID
Trap #
Alarm
Level
Description / Recommendation
53
cmgModuleInsertSuccess - A media module has been inserted.
54
cmgMgBusyout - An administrator has moved a media module or
port to the busy-out state.
55
cmgMgRelease — An administrator has moved a media module
or port from the busy-out state back into service.
56 –
69
Reserved
70
cmgFirmwareDownloadBegun - The media gateway has begun
download of a software module.
71
cmgFirmwareDownloadSuccess - The media gateway has
completed successful download of a software module.
72
Reserved
73
cmgRegistrationSuccess - The media gateway has successfully
registered with a controller.
74
cmgMgManualReset - The media gateway is beginning a
user-requested reset operation.
75
cmgModuleManualReset - A media module is beginning a
user-requested reset operation.
76
cmgVoipManualReset - A VoIP engine is beginning a
user-requested reset operation.
77
cmgDsuManualReset - An E1/T1 DSU is beginning a
user-requested reset operation.
78
cmgConfigUploadBegun — The Media Gateway has begun
upload of a configuration file.
79
cmgConfigUploadSuccess — The Media Gateway has completed
successful upload of a configuration file.
80 89
Reserved
10 of 22
378 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
G700 Traps
Table 99: G700 Traps and Resolutions 11 of 22
Event
ID
Trap #
Alarm
Level
Description / Recommendation
17
90
MAJ
cmgMemoryFault — The Media Gateway Processor has
detected a low processor memory condition.
1. Check the Media Gateway Processor and insure that it has
the latest version of firmware installed. If it does not, install
the latest version of firmware and continue to monitor.
2. If this trap occurs infrequently and is automatically cleared,
the trap may be due to an unusual transient condition.
Monitor future traps.
3. If this trap occurs frequently and is automatically cleared, it is
likely that the Media Gateway Processor software has the
wrong limits set for its memory monitoring. These limits are
hard coded in the software. Escalate the problem.
4. If this trap occurs and does not clear, the Media Gateway
may be functionally impaired. Do not reset the Media
Gateway. Escalate and have Tier 3 personnel capture the
trap information and the event logs for analysis.
5. If this trap occurs and the Media Gateway Processor
automatically resets, then a severe processor memory
shortage occurred. Escalate and have Tier 3 personnel
capture the trap information and the event logs for analysis.
17
91
MAJ
cmgMemoryClear - The main processor memory has returned to
normal operation.
18
92
MAJ
cmgDhcpRequestFault — The Media Gateway cannot contact its
DHCP server or the server failed to respond to a request.
1. Correct the DHCP problem, or correct the G700
configuration file.
18
93
MAJ
cmgDhcpRequestClear - The media gateway received a
successful response to a DHCP request.
11 of 22
Issue 3 February 2007
379
Media Gateway Traps
Table 99: G700 Traps and Resolutions 12 of 22
Event
ID
Trap #
Alarm
Level
Description / Recommendation
19
94
MAJ
cmgFirmwareDownloadFault — An attempt to download a
software module has failed.
1. Check the event log to find the specific error.
2. Troubleshoot the specific error according to the information
found.
For example, if “File not found” appears in the log, then verify
that the image file:
a. Exists
b. Has the correct name
c. Resides in the correct directory
3. If the error cannot be resolved after following the above
procedure, reboot the G700.
19
95
20
96
Reserved
WRN
cmgProcessRestartFault — a software process on the Media
Gateway Processor failed. The Media Gateway Processor will
attempt to restart the failed process. A successful restart of the
process will clear this trap
1. Check the Media Gateway Processor and insure that it has
the latest version of firmware installed. If it does not, install
the latest version of firmware and continue to monitor.
2. If this trap occurs infrequently and is automatically cleared,
the trap may be due to an unusual transient condition.
Monitor future traps.
3. If the trap occurs frequently and is automatically cleared, it
may indicate an issue with a particular software module.
Reset the Media Gateway at a time convenient with the
customer. Escalate and have Tier 3 personnel capture the
trap information and the event logs for analysis.
4. If the trap occurs and does not clear, the Media Gateway
may be functionally impaired. Reset the Media Gateway at a
time convenient with the customer and consistent with the
impairment. Escalate and have Tier 3 personnel capture the
trap information and the event logs for analysis.
12 of 22
380 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
G700 Traps
Table 99: G700 Traps and Resolutions 13 of 22
Event
ID
Trap #
Alarm
Level
Description / Recommendation
20
97
WRN
cmgProcessRestartClear - Media gateway software processes
are running normally.
21
98
MAJ
cmgIccMissingFault — An internal communications controller,
expected in Slot 1, is missing.
1. Check for the presence of an S8300.
2. If present, check the G700 administration.
3. If the administration is correct, suspect the S8300.
21
99
MAJ
cmgIccMissingClear - The Internal Communications Controller
expected in slot 1 is present.
22
100
MAJ
cmgIccAutoReset — The Media Gateway automatically reset the
Internal Communications Controller.
1. If the problem persists, escalate.
22
101
MAJ
cmgIccAutoResetClear - The Internal Communications
Controller is running normally.
23
102
MAJ
cmgPrimaryControllerFault — The Media Gateway cannot
contact the first controller in its controller list.
1. Verify that the controller list is correct. From the MGP CLI,
enter the command show mgc list. The IP address
should match the S8700 Media Server C-LAN or the S8300
Media Server IP address. If the IP addresses match, go to
step 3.
2. If needed, correct this in 'configure' mode on the MGP's CLI
by clearing the mgc list first with the clear mgc list
command, and then enter set mgc list with the correct IP
addresses.
3. Verify that the primary controller is up.
4. If so, shut down every LSP.
23
103
MAJ
cmgPrimaryControllerClear - The media gateway successfully
contacted the first controller in its controller list.
13 of 22
Issue 3 February 2007
381
Media Gateway Traps
Table 99: G700 Traps and Resolutions 14 of 22
Event
ID
Trap #
Alarm
Level
Description / Recommendation
24
104
MAJ
cmgNoControllerFault — The Media Gateway cannot contact
any controller in its controller list.
1. Verify that the controller list is empty. From the MGP CLI,
enter the command show mgc list to verify that there are
no controllers listed.
2. If none are listed, add the correct IP address of the S8700/
S8300. In 'configure' mode on the MGP's CLI, enter
set mgc list with the correct IP address.
24
105
MAJ
cmgNoControllerClear - The media gateway successfully
contacted one of the controllers in its controller list.
25
106
MAJ
cmgRegistrationFault — The Media Gateway cannot register
with any controllers in its controller list.
1. Verify that the controller list is correct. From the MGP CLI,
enter the command show mgc list. The IP address
should match the S8700 Media Server C-LAN or the S8300
Media Server IP addresses.
2. If needed, correct this in 'configure' mode on the MGP's CLI
by clearing the mgc list with the clear mgc list
command, and then issuing a set mgc list with the
correct IP addresses.
3. If the IP address in the mgc list matches the S8700 Media
Server C-LAN or the S8300 Media Server IP addresses,
there may be a network problem.
4. Verify that the primary controller is up.
5. If the above steps do not fix the problem, reboot the G700.
25
107
Reserved
14 of 22
382 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
G700 Traps
Table 99: G700 Traps and Resolutions 15 of 22
Event
ID
Trap #
Alarm
Level
Description / Recommendation
26
108
MIN
cmgH248LinkDown — The H.248 link between the Media
Gateway and its controller is down.
1. Check the S8300 or S8700.
2. If it is down, bring it up.
3. If it is not, check the G700 administration.
Since the following command causes a brief service outage, it
should only be executed at the customer’s convenience.
4. If the administration is correct, reboot the G700.
5. If the problem persists, check network connectivity. Use
ping or traceroute to the S8300/S8700 to check
connectivity.
6. If the problem persists, escalate.
26
109
MIN
cmgH248LinkUp - The H.248 link between the media gateway
and its controller is back in service.
27
110
MIN
cmgTestFault - Maintenance tests have failed.
1. Refer to the specific maintenance object failure for diagnosis.
27
111
MIN
cmgTestClear - Previously failed maintenance tests have
passed.
28
112
MAJ
cmgTestThresholdFault - The maintenance test failure count has
exceeded its reporting threshold. No action is required.
28
113
MAJ
cmgTestThresholdClear - The maintenance test failure count has
dropped below its reporting threshold.
15 of 22
Issue 3 February 2007
383
Media Gateway Traps
Table 99: G700 Traps and Resolutions 16 of 22
Event
ID
Trap #
Alarm
Level
Description / Recommendation
29
114
WRN
cmgMgAutoReset — The Media Gateway Processor
automatically reset (rebooted). The processor automatically
resets when a critical error occurs from which it cannot recover.
The error may be software or hardware related. It may
automatically reset when it reregisters with a call controller after
being out of touch for too long. This trap is generated as the
Media Gateway Processor comes back up after resetting. If the
Media Gateway Processor resets and fails to come back up, this
trap will not be generated.
1. Check to see if a maintenance test that is supposed to reset
the processor was run.
2. Check that the reset was not due to the link with the call
controlling going down. If the reset is due to a link failure with
the call controller, follow call controller link failure
troubleshooting procedures.
3. Check the Media Gateway Processor and insure that it has
the latest version of firmware installed. If it does not, install
the latest version of firmware and continue to monitor.
4. If this trap occurs infrequently, the trap may be due to an
unusual transient condition. Monitor future traps.
5. If this trap occurs and the Media Gateway Processor is
frequently resetting, manually reset the media gateway.
Escalate and have Tier 3 personnel capture the trap
information and the event logs for analysis.
6. If this trap occurs frequently and the Media Gateway
Processor is not resetting, the Media Gateway may be
functionally impaired and is not capable of resetting itself to
restore service. If service is impaired, reset the Media
Gateway manually. Escalate and have Tier 3 personnel
capture the trap information and the event logs for analysis.
29
115
Reserved
16 of 22
384 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
G700 Traps
Table 99: G700 Traps and Resolutions 17 of 22
Event
ID
Trap #
Alarm
Level
Description / Recommendation
30
116
WRN
cmgModuleAutoReset — A Media Module in the Media Gateway
automatically reset (rebooted). A Media Module automatically
resets when it fails a sanity test performed by the Media Gateway
Processor.
1. Check to see if a maintenance test that is supposed to reset
the Media Module was run.
2. Check the Media Module and insure that it has the latest
version of firmware installed. If it does not, install the latest
version of firmware and continue to monitor.
3. If this trap occurs infrequently, the trap may be due to an
unusual transient condition. Monitor future traps.
4. If this trap occurs and the Media Module does not return to
service, or if this trap occurs frequently, attempt to reset the
failing module from the SAT or CLI and see if this returns it to
stable service.
5. If manually resetting the Media Module does not return it to
service, and if a spare Media Module of the same time is
available, replace the failing Media Module with the spare
and see if the spare Media Module goes into service. If so,
follow procedures for dealing with the original, bad, Media
Module.
6. If the spare Media Module fails to go into service, it is of
course possible that the spare Media Module is bad as well.
But that aside, try manually resetting the Media Gateway
Processor at a time convenient to the customer and see if
this restores service. If so, the both the original and the spare
Media Modules can probably be considered okay, and the
problem is probably with the Media Gateway Processor itself.
Escalate and have Tier 3 personnel capture the trap
information and the event logs for analysis.
30
117
WRN
cmgModuleAutoResetClear - The reset media module is
operating normally.
17 of 22
Issue 3 February 2007
385
Media Gateway Traps
Table 99: G700 Traps and Resolutions 18 of 22
Event
ID
Trap #
Alarm
Level
Description / Recommendation
32
118
MIN
cmgModulePostFault — A Media Module failed its power-on
start-up test.
1. Reset or replace the Media Module.
32
119
MIN
cmgModulePostClear - The media module power-on start-up test
was successful.
33
120
MIN
cmgModuleParameterFault - A media module failed its
parameter exchange.
1. Manually reboot the G700 at a convenient time.
2. If the problem persists, escalate.
33
121
MIN
cmgModuleParameterClear - The media module’s parameter
exchange succeeded.
34
122
MAJ
cmgConfigUploadFault — An attempt to upload a configuration
file failed.
1. Check the event log for an error message during the backup/
restore process.
2. Troubleshoot the specific error according to the information
found.
3. Retry the upload (backup) command; for example:
copy mgp-config tftp <filename> <ip address>
Since the following command causes a brief service outage, it
should only be executed at the customer’s convenience.
4. If the problem persists, reboot the G700.
123
Reserved
35
124
MIN
cmgVoipOccFault - One or more of the VoIP engines in the
media gateway is over is its occupancy threshold as measured
by a snapshot: (Channels In Use/Total Channels). No action is
required.
35
125
MIN
cmgVoipOccClear - All of the VoIP engines in the media gateway
are operating below occupancy threshold.
18 of 22
386 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
G700 Traps
Table 99: G700 Traps and Resolutions 19 of 22
Event
ID
Trap #
Alarm
Level
Description / Recommendation
36
126
MIN
cmgVoipAvgOccFault - One or more of the VoIP engines in the
media gateway is operating above its average occupancy
threshold. No action is required.
36
127
MIN
cmgVoipAvgOccClear - All of the VoIP engines in the media
gateway are operating below occupancy threshold.
37
128
WRN
cmgVoipAutoReset — A VoIP (Voice Over IP) module in the
Media Gateway automatically reset (rebooted). A VoIP module
automatically resets when it fails a sanity test performed by the
Media Gateway Processor, when its IP address is administered,
or when it fails a ping test performed by the Media Gateway
Processor against the VoIP module's IP address.
1. Check to see if a maintenance test that is supposed to reset
the VoIP module was run.
2. Check to see if the VoIP module had its IP address
re-administered.
3. Check to see if the IP address administered on the VoIP
module is correct.
4. Check to see if the IP address of the Media Gateway itself
can be pinged. Physical or logical connectivity issues
(cabling or routing problems) in the data network can cause
ping failures.
5. Check the VoIP module and insure that it has the latest
version of firmware installed. If it does not, install the latest
version of firmware and continue to monitor.
6. If this trap occurs infrequently, the trap may be due to an
unusual transient condition. Monitor future traps.
7. If this trap occurs and the VoIP module does not return to
service, or if this trap occurs frequently, attempt to reset the
failing module from the SAT or CLI and see if this returns it to
stable service.
19 of 22
Issue 3 February 2007
387
Media Gateway Traps
Table 99: G700 Traps and Resolutions 20 of 22
Event
ID
Trap #
Alarm
Level
37
128
WRN
(cont’d)
Description / Recommendation
8. If manually resetting the VoIP module does not return it to
service, and if a spare VoIP module of the same type is
available, replace the failing VoIP module with the spare and
see if the spare VoIP module goes into service. If so, follow
procedures for dealing with the original, bad, VoIP module.
9. If the spare VoIP module fails to go into service, it is of
course possible that the spare VoIP module is bad, as well.
There may be a power issue, also.
10. Try manually resetting the Media Gateway Processor at a
time convenient to the customer and see if this restores
service. If so, both the original and the spare VoIP modules
can probably be considered okay, and the problem is
probably with the Media Gateway Processor itself. Capture
the trap information. If possible, capture the event logs, using
the show event-log CLI command, for analysis. Escalate.
If none of this works, capture the trap information. If possible,
capture the event logs, using the show event-log CLI
37
129
WRN
cmgVoipAutoResetClear - A VoIP engine has completed its
automatic reset and is running normally.
39
130
MAJ
cmgDsuFpgaConfigureFault - The DSU in one of the E1/T1
media modules failed to configure its Field Programmable
Gateway Array. No action is required.
39
131
MAJ
cmgDsuFpgaConfigureClear - The DSU in one of the E1/T1
media modules successfully configured its Field Programmable
Gateway Array.
40
132
WRN
cmgDsuAutoReset - A DSU in one of the E1/T1 media modules
began an automatic reset. No action is required.
40
133
WRN
cmgDsuAutoClear - A DSU in one of the E1/T1 media modules
completed its automatic reset and is running normally.
41
134
MIN
cmgDsuDteDtrFault - One of the E1/T1 media modules has
detected that the DTR signal from its DTE is off. This indicates
that the DTE is not connected or not functioning.
41
135
MIN
cmgDsuDteDtrClear - One of the E1/T1 media modules has
detected that the DTR signal from its DTE has returned to
normal.
20 of 22
388 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
G700 Traps
Table 99: G700 Traps and Resolutions 21 of 22
Event
ID
Trap #
Alarm
Level
Description / Recommendation
42
136
MIN
cmgDsuDteRtsFault - An E1/T1 media module has detected that
the RTS signal from its DTE is off whenever the DTE requests to
send data and during data transfer. This indicates that the DTE is
not functioning.
42
137
MIN
cmgDsuDteRtsClear - An E1/T1 media module has detected that
the RTS signal from its DTE has returned to normal.
43
138
MAJ
cmgDsuTxDFault - An E1/T1 media module has detected that
the data received from the local DTE to be sent to the far end is
either all ones or all zeroes.
43
139
MAJ
cmgDsuTxDClear - The E1/T1 media module is receiving normal
data from the local DTE to be sent to the far end.
44
140
MAJ
cmgDsuRxDFailure - An E1/T1 media module has detected that
the data received from the far end to be sent to the local DTE is
either all ones or all zeroes.
44
141
MAJ
cmgDsuRxDClear - The E1/T1 media module is receiving normal
data from the far end to be sent to the local DTE.
45
34
WRN
cmgSyncSignalWarn - A change to the port status of a board that
is providing sync timing has occurred. There is only one good
port out of the >1 ports configured. If this port goes out of service,
trap # 30, cmgSyncSignalFault, is generated.
45
35
WRN
cmgSyncWarnClear - More than one port is in service on a board
that is providing sync timing.
46
142
MIN
cmgVoipIpConfigFault - There are two possible causes:
1. Duplicate IP address
2. VoIP failed to initialize.
Examine the event log to determine which failure caused the
event.
46
143
MIN
cmgVoipIpConfigClear - The duplicate IP address has been
changed or the VoIP reset to re-initialize.
47
144
MAJ
MG registration - G700 registered successfully with CMG. Alarm
cleared
21 of 22
Issue 3 February 2007
389
Media Gateway Traps
Table 99: G700 Traps and Resolutions 22 of 22
Event
ID
Trap #
Alarm
Level
Description / Recommendation
48
145
MIN
MG de-registered - G700 de-registered from CMG.
49
146
MG unregistered - G700 has been unregistered from the CMG
for too long. All board and call information has been cleared.
22 of 22
390 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Chapter 5: Communication Manager Maintenance
Object Repair Procedures
This chapter provides information for troubleshooting and repairing maintenance objects.
Note:
This chapter does not contain maintenance objects for the Avaya Wireless
Business System or messaging systems. Refer to the documentation that
accompanies these products for this information.
Note:
Each identifiable part in the system is considered a Maintenance Object (MO). A maintenance
object can be:
●
An individual circuit pack or media module
●
A hardware component that is part of a circuit pack or media module
●
Any software process
●
Significant events
●
Environmental controls
●
A cabinet
Each maintenance object has its own unique set of tests, error codes, and recovery strategy.
“Maintenance names” are recorded in the Error and Alarm logs. Individual copies of an MO are
assigned an address that defines the MO’s physical location in the system when applicable.
These locations display as the port field in the Alarm and Error logs and as output of commands
such as test board (see Figure 36: Display of test board).
Issue 3 February 2007
391
Communication Manager Maintenance Object Repair Procedures
Figure 36: Display of test board
Displaying MOs Maintained by Communication Manager
Communication Manager maintenance objects are displayed using the list configuration
or show mg list_config command.
list config all on the Communication Manager System Access Terminal (SAT) displays
the Board Name (location 1A02), Board Type (IP SERVER INTFC), Code (TN2312AP), Vintage
(HW02 FW022), and the assigned ports, if any, of all installed equipment in the system.
show mg list_config on the MGP displays information for the installed equipment in that
media gateway.
392 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Displaying MOs Maintained by Communication Manager
G700 Subsystems
The G700 subsystems are either field replaceable or integrated (part of the system and not
replaceable). These subsystems are not under Communication Manager control and are not
maintained by the system. Table 100: G700 Subsystems Maintained by Communication
Manager lists the applicable subsystems and if they are field replaceable or not.
Table 100: G700 Subsystems Maintained by Communication Manager
Subsystem
Field Replaceable
Any Media Module
Yes
VOIP Media Module
No
Announcement Circuitry (part of the MGP)
No
Media Gateway Maintenance Objects
Maintained by Communication Manager
The maintenance strategy for the Media Gateways is intended to provide easy fault isolation
procedures and to restrict problems to field-replaceable components. The following list contains
the maintenance objects which are under Communication Manager control and are maintained
by the system:
●
MED-GTWY (MEDIA GATEWAY)
●
MG-ANA (Analog Media Module)
●
MG-ANN (Voice Announcements)
●
MG-BRI (BRI Trunk Media Module)
●
MG-DCP (Digital Line Media Module)
●
MG-DS1 (DS1 Interface Media Module)
●
MG-IAMM (Integrated Analog Media Module)
●
MG-VOIP (MM760 VoIP Media Module)
Issue 3 February 2007
393
Communication Manager Maintenance Object Repair Procedures
MO groupings by Media Module type
Table 101: Media Module Types shows MO groupings by Media Module type.
Table 101: Media Module Types 1 of 2
Media Module (MM)
Maintenance Object (MO)
E1/T1 Media Module
Board (MG-DS1)
DS1 CO Trunk (CO-DS1)
DS1 DID Trunk (DID-DS1)
DS1 Tie Trunk (TIE-DS1)
DS1 ISDN Trunk (ISDN-TRK)
ISDN-PRI Signaling Link Port
(ISDN-LNK)
ISDN-PRI Signaling Group
(ISDN-SGRP)
Wideband Access Endpoint Port
(WAE-PORT)
Analog Media Module
Board (MG-ANA)
Analog Line (AN-LN-PT)
Analog Co Trunk (CO-TRK)
Analog DID Trunk (DID-TRK)
DIOD Trunk (DIOD-TRK)
Alarm Port (ALARM-PT)
DCP Media Module
Board (MG-DCP)
Digital Line (DIG-LINE)
1 of 2
394 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
Viewing Communication Manager Alarms
Table 101: Media Module Types 2 of 2
Media Module (MM)
Maintenance Object (MO)
BRI Trunk Media Module
Board (MG-BRI)
ISDN Trunk Side BRI Port (TBRI-PT)
ISDN Trunk Side Signaling
(TBRI-TRK)
Integrated Analog Module in V7 (G350)
Integrated Analog Module in V3(G250’s)
MG-IAMM
2 of 2
Viewing Communication Manager Alarms
Communication Manager alarms and events are viewed using commands that are available via
the Web Interface or the SAT command-line interface (CLI). See Table 102: Commands for
Viewing Communication Manager Alarms.
Table 102: Commands for Viewing Communication Manager Alarms
Command
Interface
Purpose
Description
View Current Alarms
Web Interface,
under Alarms and
Notification
View a list of outstanding
alarms against
Communication Manager
Displays a summary of alarms,
if present, followed by a
detailed table of explanation.
display alarms
SAT CLI
View logged Communication
Manager alarms
These are alarms that have not
yet been cleared, either
manually or via an Expert
System.
Command Syntax
Commands use a different syntax for the board or port location depending upon whether they
refer to circuit packs or media modules. Test command sequences can be either short or long
(l). The default is short. The test sequence can be repeated several times. The default is 1.
Issue 3 February 2007
395
Communication Manager Maintenance Object Repair Procedures
The following is an example for testing a port on a circuit pack:
test port UUCSSpp l r 2
●
UU = the universal cabinet number (1 - 64)
●
C = the carrier designation (A, B, C, D, or E)
●
SS = the circuit pack slot number (01, 02,...)
●
pp = the 2-digit port number (01, 02,...)
●
l = long test sequence
●
r = repeat
●
2 = the number of times the test sequence should be repeated.
The following is an example for testing a port on a media module. It runs the short test
sequence:
test port GGGVSpp r 3
●
GGG = the media gateway number (1 - 250)
●
V = the literal letter V, which designates a media gateway
●
S = the media module number (1 - 9)
●
pp = the 2-digit port number (01, 02,...)
●
r = repeat
●
3 = the number of times the test sequence should be repeated
Abort Code 1412
Tests which are not applicable for media modules or media gateways abort with Error Code
1412. This error indicates that the test is not valid for the particular maintenance object and can
be ignored.
Escalation Procedure
This document is not intended to solve all problems. If the limits of these procedures have been
reached and the problem is not resolved, the problem should be escalated to a higher level of
technical support.
This escalation should conform to the procedures in the Technical and Administration Plan.
396 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
EPN Angel Address/Slot Mapping
Frequently, a repair procedure recommends repeating a test several times after waiting short
time intervals, for example, at one minute intervals up to five times. If, after these repetitions, no
response to the test has occurred, or if the same Abort or Failure continues to occur, escalate
the problem to a higher level of technical support.
EPN Angel Address/Slot Mapping
The following table contains the angel addresses for EPNs. Note the different mappings for
different A-carrier types.
Table 103: EPN Angel Address/Slot Mapping 1 of 2
Carrier
A1
A2
A3,4
B4
C4
D4
E4
D5
E5
0
27
----
90
86
118
54
22
----
----
1
28
30
27
66
98
34
02
----
----
2
29
31
28
67
99
35
03
32
00
3
30
56
29
68
100
36
04
33
01
4
31
57
30
69
101
37
05
34
02
5
56
58
31
70
102
38
06
35
03
6
57
59
56
71
103
39
07
36
04
7
58
60
57
72
104
40
08
37
05
8
59
61
58
73
105
41
09
38
06
9
60
62
59
74
106
42
10
39
07
10
61
63
60
75
107
43
11
48
16
11
62
----
61
76
108
44
12
----
----
12
63
----
62
77
109
45
13
49
17
13
88
----
63
78
110
46
14
40
08
14
89
----
88
79
111
47
15
41
09
15
90
----
89
80
112
48
16
42
10
Slot Number
1 of 2
Issue 3 February 2007
397
Communication Manager Maintenance Object Repair Procedures
Table 103: EPN Angel Address/Slot Mapping 2 of 2
Carrier
A1
A2
A3,4
B4
C4
D4
E4
D5
E5
16
91
----
----
81
113
49
17
43
11
17
92
----
----
82
114
50
18
44
12
18
93
----
----
83
115
51
19
45
13
19
94
----
----
84
116
52
20
46
14
20
95
----
----
85
117
53
21
47
15
216
----
----
----
86
118
54
22
----
----
Slot Number
2 of 2
1. Carrier A mappings for EPN MCC1/SCC1 media gateways
2. Carrier A mappings for EPN G600 media gateway (RMC) carrier
3. Carrier A mappings for G650 media gateway (ERMC) carrier
4. G650 MGs have power supply in slots 0/15. Slots 16-20 n/a
5. Carrier E/D mappings for SN/Dup SN carrier slots 2-10, 12-20
6. Service Slot is labeled slot 0, external slot 21
398 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
ABRI-POR (ASAI ISDN-BRI Port)
ABRI-POR (ASAI ISDN-BRI Port)
S8700 Series | S8500
MO Name in Log
Alarm Level
Initial Command to Run
Full MO Name
ABRI-POR 1
MAJ
MIN
WRN
test port location l
ASAI ISDN-BRI port
1. Use set options to set the alarm level for ABRI ports. The alarm level can be set independently for
on- and off-board alarms to WARNING, MINOR, or MAJOR for every ABRI port in the system.
For repair procedures, see BRI-PORT (ISDN-BRI Port) on page 572.
Issue 3 February 2007
399
Communication Manager Maintenance Object Repair Procedures
AC-POWER
S8700 Series | S8500
AC Power for AC-Powered Systems
MO Name in Log
Alarm Level
Initial Command to Run
Full Name of MO
AC-POWER
WRN
test environment location1
AC Power
1. Cabinet number indicated in the PORT field of the alarm log.
Three different cabinet types are supported as PNs: multicarrier cabinets, single-carrier
cabinets and the G650 rack mounted cabinets. All types may be powered by either an AC or DC
power source. Environmental maintenance differs according to a cabinet’s type and its power
supply.
! CAUTION:
Before powering down a cabinet or carrier that contains an EMBEDDED AUDIX
circuit packs (TN566), first power down the AUDIX unit to avoid damaging its
software. Instructions for powering down this unit are in Maintenance Procedures
for Avaya Communication Manager 4.0, Media Gateways and Servers
(03-300432).
CAUTION:
Power System for Single-Carrier Cabinet
Each single-carrier cabinet has one power supply that distributes DC power and AC ringing
voltage to the circuit pack slots in the cabinet.
AC Power Supply (WP-91153)
In an AC-powered cabinet, a single, plug-in, multi-output AC power supply is in the power
supply slot. A power cord, with a 3-prong plug on one end and an appliance connector on the
other end, connects the supply to a dedicated AC power source. The inputs to the power supply
can be (depending on list version):
●
●
120 VAC, 60 Hz, 15 to 20 Amp; three wires in the power cord (one hot, one neutral, and
one ground wire)
220 VAC or 240 VAC, 50 Hz, 10 Amp; three wires in the power cord (one hot, one neutral,
and one ground wire)
The AC power supply produces the following DC outputs: +5 VDC, -5 VDC, -48 VDC, +12 VDC,
and a battery-charging voltage. The DC outputs distribute power on the cabinet backplane to
the circuit pack slots.
400 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
AC-POWER
The AC power supply also produces AC ringing voltage. The AC ringing voltage output value
and frequency depend on the country of use. The power supply has a circuit breaker and EMI
filtering.
Nominal Power Holdover
Multicarrier Cabinets
Two types of battery holdover are available:
●
The small battery assembly provides short-term battery holdover. If AC power fails, 48
VDC batteries power the system for:
- 15 seconds in a PN cabinet
- 10 minutes in the expansion control carrier in the “A” position of a PN cabinet
●
Some AC-powered multicarrier cabinets (MCCs) contain three 48-Volt batteries and a
battery charger (397C) to provide backup power in case power is interrupted. The
holdover times are identical to those above.
Single-Carrier Cabinets
A holdover circuit in the power supply allows a system to operate normally during AC power
interruptions. When AC input power fails, reserve batteries supply power to the memory and
processor circuit packs and fans for two minutes. Every port circuit pack is inactive during this
time. The power supply contains a battery charger to charge the holdover batteries.
Error log entries and recommended actions
Table 104: AC Power Error Log Entries
Error
Type
Aux
Data
Associated Test
Alarm
Level
On/Off
Board
Recommended action
01
0
Any
Any
Any
test environment location
513
Any
AC Power Query
Test (#78)
WRN
OFF
test environment location
1. Run the short test sequence first. If every test passes, run the long test sequence. Refer to each
appropriate test’s description, and follow its recommended procedures.
Demand test descriptions and error codes
Investigate tests in the order presented. By clearing errors associated with the first test, errors
generated from other tests may also be cleared. Click on the link to see the full description of
the test, error codes, and recommended actions.
Issue 3 February 2007
401
Communication Manager Maintenance Object Repair Procedures
Note:
Note:
The following tests apply to J58890CE, J58890CF, and J58890CH.
Order of Investigation
D/ND1
Short Test
Sequence
Long Test
Sequence
Battery and Power Supply Query Test (#5)
X
X
ND
AC Power Query Test (#78)
X
X
ND
OLS/Power Unit Query Test (#127) (Carrier E)
X
X
ND
OLS/Power Unit Query Test (#127) (Carrier D)
X
X
ND
OLS/Power Unit Query Test (#127) (Carrier A)
X
X
ND
OLS/Power Unit Query Test (#127) (Carrier B)
X
X
ND
OLS/Power Unit Query Test (#127) (Carrier C)
X
X
ND
Emergency Transfer Query Test (#124)
X
X
ND
Cabinet Temperature Query Test (#122)
X
X
ND
External Device Alarm Query Test (#120)
X
X
ND
Ring Generator Initialization Test (#117)
X
X
ND
Ring Generator Query Test (#118)
X
X
ND
1. D = Destructive; ND = Nondestructive
402 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
AC-POWER for DC-Powered Systems
AC-POWER for DC-Powered Systems
MO Name in Log
Alarm
Level
Initial Command to Run
Full Name of MO
AC-POWER
WRN
test environment location
AC Power
Note:
In a DC-powered multicarrier cabinet, the AC-POWER MO exists but serves no
functional purpose. Because the system cannot determine the type of power
used, the AC-POWER test should always pass or abort. See CARR-POW
(Carrier Power Supply) on page 608 for the maintenance strategy for power
components in DC cabinets.
Note:
S8700 Fiber-PNC supports three cabinet types for PNs: multicarrier cabinets (MCCs),
single-carrier cabinets (SCCs), and 19-inch rack mounted cabinets. Every type may be powered
by either an AC or DC power source. Environmental maintenance differs according to a
cabinet’s type and its power supply.
S8700 IP-PNC supports 19-inch rack mounted cabinets, powered by either an AC or DC power
source.
Error log entries and recommended actions
Table 105: AC Power Error Log Entries
Error
Type
Aux
Data
Associated Test
Alarm
Level
On/Off
Board
Recommended action
01
0
Any
Any
Any
test environment location
513
Any
AC Power Query test
(#78)
WRN
OFF
test environment location
1. Run the short test sequence first. If every test passes, run the long test sequence. Refer to each
appropriate test’s description, and follow its recommended procedures.
Issue 3 February 2007
403
Communication Manager Maintenance Object Repair Procedures
Demand test descriptions and error codes
Investigate tests in the order presented. By clearing errors associated with the first test, errors
generated from other tests may also be cleared. Click on the link to see the full description of
the test, error codes, and recommended actions.
Order of Investigation
Short Test
Sequence
Long Test
Sequence
D/ND1
Battery and Power Supply Query Test (#5)
X
X
ND
AC Power Query Test (#78)
X
X
ND
OLS/Power Unit Query Test (#127) (Carrier E)
X
X
ND
OLS/Power Unit Query Test (#127) (Carrier D)
X
X
ND
OLS/Power Unit Query Test (#127) (Carrier A
X
X
ND
OLS/Power Unit Query Test (#127) (Carrier B)
X
X
ND
OLS/Power Unit Query Test (#127) (Carrier C)
X
X
ND
Emergency Transfer Query Test (#124)
X
X
ND
Cabinet Temperature Query Test (#122)
X
X
ND
External Device Alarm Query Test (#120)
X
X
ND
Ring Generator Initialization Test (#117)
X
X
ND
Ring Generator Query Test (#118)
X
X
ND
1. D = Destructive; ND = Nondestructive
404 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
ADJ-IP (ASAI Adjunct TCP/IP Link)
ADJ-IP (ASAI Adjunct TCP/IP Link)
MO Name in Log
Alarm
Level
Initial Command to Run
Full Name of MO
ADJ-IP
MAJ
MIN
WRN
test port location
ASAI Adjunct
TCP/IP Link
The ASAI Adjunct TCP/IP Link is the Adjunct Switch Application Interface (ASAI) proprietary link
which connects to a C-LAN circuit pack.
Error log entries and recommended actions
Table 106: ADJ-IP Error Log Entries
Error Type
Aux
Data
Associated Test
Alarm
Level
On/Off
Board
Recommended action
0 (a)
0
Any
Any
Any
test aesvcs link#
2 (b)
Any
18 (c)
257 (d)
Any
test aesvcs link#
busyout port
location
WRN
OFF
release aesvcs link#
ASAI Link Status
Test (#1365)
MAJ
MIN
WRN1
OFF
test aesvcs link#
MAJ
MIN
WRN1
OFF
test aesvcs link#
MAJ
MIN
WRN1
OFF
test aesvcs link#
1025 (e)
3329 (f)
ASAI Link Status
Test (#1365)
1. Alarms may be downgraded according to values set on the set options form.
Notes:
a. Error Type 0: Run the ASAI Link Status Test (#1365) and follow its recommended
procedures.
b. Error Type 2: Too many Q931 protocol timeouts in a short time. No action to take.
Issue 3 February 2007
405
Communication Manager Maintenance Object Repair Procedures
c. Error Type 18: The ASAI link has been busied out by command. To release the link, enter
release aesvcs link#
d. Error Type 257: The ASAI TCP/IP link is not in an "established" state.
e. Error Type 1025: TCP Tunnel Connection failure
f. Error Type 3329: ASAI TCP/IP link failure.
Demand test descriptions and error codes
Order of Investigation
ASAI Link Status Test (#1365)
Short Test
Sequence
X
Long Test
Sequence
X
1. D = Destructive; ND = Nondestructive
406 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
D/ND1
ND
ADM-CONN (Administered Connection)
ADM-CONN (Administered Connection)
MO Name in Log
Alarm
Level
Initial Command to Run
Full Name of MO
ADM-CONN
MAJ
MIN
WRN
status administered-connection n 1
Administered
Connection
1. n is an administered connection number indicated in the PORT field of the Alarm or Error Log.
An administered connection provides an end-to-end connection between two access endpoints
or data modules residing in either the same switch or different switches. When administered,
the connection is automatically established and scheduled to be permanently active.
An error is logged whenever an administered connection fails or cannot be established. Failures
to establish a connection generate an error whether they occur on an initial try, a retry, a fast
retry, a re-dial or an auto-restoration. A failed connection generates an error whether or not the
connection is subsequently reestablished by fast retry, re-dial, or auto restoration.
An alarm is logged when an administered connection cannot be established either initially or
after a connection failure. Both the alarm level (none to major) and a failure threshold can be
administered for each administered connection. An alarm is raised when either of the following
occurs:
●
●
The number of consecutive failed attempts to establish a connection reaches the
administered threshold.
Software determines that failure to establish a connection is due to a mistake in
administration. See Table 107: Administered Connection Error Log Entries.
Error log entries and recommended actions
Table 107: Administered Connection Error Log Entries 1 of 2
Error Type
Aux Data
Associated Test
Alarm
Level
On/Off
Board
Recommended
action
0, 29
Any
None
Any
OFF
None
1, 28 (a, b)
Any
None
Any
OFF
None
2 (c)
Any
None
Any
OFF
None
6, 21, 31, 127 (d)
Any
None
Any
OFF
None
16 (a)
Any
None
Any
OFF
None
1 of 2
Issue 3 February 2007
407
Communication Manager Maintenance Object Repair Procedures
Table 107: Administered Connection Error Log Entries 2 of 2
Error Type
Aux Data
Associated Test
Alarm
Level
On/Off
Board
Recommended
action
17 (e)
Any
None
Any
OFF
None
18, 102 (f)
Any
None
Any
OFF
None
22 (a, g)
Any
None
Any
OFF
None
34, 42, 44, 58 (h)
Any
None
Any
OFF
None
38, 41 (i)
Any
None
Any
OFF
None
43, 81
Any
None
Any
OFF
None
50 (a)
Any
None
Any
OFF
None
52 (a)
Any
None
Any
OFF
None
54
Any
None
Any
OFF
None
65, 66, 69 (a)
Any
None
Any
OFF
None
82
Any
None
Any
OFF
None
88 (a)
Any
None
Any
OFF
None
91, 95, 96, 97,
98, 99, 100, 111
Any
None
Any
OFF
None
2 of 2
ADM-CONN Errors
None of the Administered Connection Error Types have a specific associated test and, except
for errors 17 and 127, are valid only for administered connections established over ISDN-PRI
facilities. Error 127 is valid for administered connections established over non-ISDN facilities or
between two endpoints on the same switch.
Notes:
a. Error Types 1, 16, 22, 50, 52, 65, 66, 69, 88 are typically associated with administration
problems and are not expected to be temporary. The administered connection is not retried
and the failure is alarmed immediately. The alarm threshold specified by the customer is
ignored.
b. Error Types 1, 28: the address of the destination endpoint is: an unassigned number (1),
has an invalid number format (28), or is restricted from terminating calls due to Class of
Restriction (“Access Denied”). Verify that the destination address is correct and that the
destination endpoint is administered. The destination endpoint is not administered on the
switch where this error is logged.
408 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
ADM-CONN (Administered Connection)
c. Error Type 2: a request has been made to use a transit network or common carrier that
cannot be accessed. Check the routing pattern used by this administered connection and
verify that the inter-exchange carrier specified is correct.
d. Error Types 6, 21, 31, 127: the exact failure cause is unknown or has been mapped to one
of these values. If this is a permanent condition, try reversing the direction of the
Administered Connection (originate the administered connection from the destination
switch). This may yield another failure cause.
e. Error Type 17: the destination endpoint is not available. Check the status of the destination
endpoint at the far-end switch. The status for the destination endpoint will not be available
on the switch where this error is logged. At the far end, use status access-endpoint or
status data-module to see whether the endpoint is busy, out-of-service or otherwise
unavailable.
f. Error Types 18, 102: this switch sent an ISDN message to another switch that either did not
respond (18) or did not respond within the time allowed (102). This could be due to link
failure, or congestion, or an outage at the other switch.
g. Error Type 22: the address of the destination endpoint has changed. Change the
administered connection accordingly. The destination endpoint will not be administered on
the switch where this error is logged.
h. Error Types 34, 42, 44, 58: a resource (for example, a circuit or bearer capability) required
by the administered connection is not currently available.
i. Error Types 38, 41: a network failure (38) or temporary failure (41) has occurred. Error Log
entries for other MOs (for example, DS1-BD) may indicate a local problem.
Issue 3 February 2007
409
Communication Manager Maintenance Object Repair Procedures
ADX8D-BD (AUDIX Circuit Pack)
MO Name in Log
Alarm Level
Initial Command to Run
Full Name of MO
ADX8D-BD
MIN
WRN
test board location
AUDIX circuit pack
The ADX8D-BD MO defines a TN566/TN2169 EMBEDDED AUDIX circuit pack operating in DP
(digital-port) mode.
For port-level problems, see ADX8D-PT (AUDIX Digital Port).
For circuit-pack-level problems, see XXX-BD (Common Port Circuit Pack/Media Module).
EMBEDDED AUDIX consists of two circuit packs that occupy 5 slots on a port carrier. The tests
apply only to switch-side maintenance which tests a circuit pack’s components related to the
TDM-bus interface. The AUDIX system has an extensive maintenance strategy that is
described in DEFINITY® AUDIX Maintenance, 585-300-110.
410 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
ADX8D-PT (AUDIX Digital Port)
ADX8D-PT (AUDIX Digital Port)
MO Name in Log
Alarm Level
Initial Command to Run
Full Name of MO
ADX8D-PT
MIN
test port location l
AUDIX digital port
WRN
test port location
The ADX8D-PT MO represents a port on a TN566/TN2169 EMBEDDED AUDIX circuit pack
operating in DP (digital-port) mode. The maintenance strategy for ports on the TN566 operating
in control-link mode is described in ADX16D-P (16-Port AUDIX Digital Port).
The tests described in this section apply only to switch-side maintenance that tests a circuit
pack’s components related to the TDM-bus interface. The AUDIX system has an extensive
maintenance strategy that is described in DEFINITY® AUDIX Maintenance, 585-300-110.
AUDIX resides on a combined pair of circuit packs: the TN566 MFB (multifunction board) and
the TN2169 ALB (alarm board). Because of its size, this combination occupies 5 slots, but only
1 slot is functional as far as the switch is concerned. The other 4 slots are seen by the switch as
“AUDIX-reserved” slots (or ADXDP-RS/ADX8D-RS).
In DP mode, the TN566 pack supports up to 8 voice ports, each with a primary and a secondary
information channel. Ports are administered in increments of two. When a call to a station with
an AUDIX login is not answered, AUDIX answers the call using one of the available voice ports.
Unlike other AUDIX systems, EMBEDDED AUDIX is not an adjunct.
! CAUTION:
Always shut down AUDIX first before removing circuit packs. Follow instructions
on the TN566/TN2169 faceplate:
CAUTION:
●
Remove EMBEDDED AUDIX circuit packs
●
Cycle power to a carrier containing EMBEDDED AUDIX circuit packs
●
Remove power to a carrier containing EMBEDDED AUDIX circuit packs
Error log entries and recommended actions
Table 108: EMBEDDED AUDIX Digital Port Error Log Entries 1 of 2
Error Type
Aux
Data
Associated Test
Alarm
Level
On/Off
Board
Recommended action
0 (a)
0
Any
Any
Any
test port location
1 (b)
40987
None
WRN
OFF
1 of 2
Issue 3 February 2007
411
Communication Manager Maintenance Object Repair Procedures
Table 108: EMBEDDED AUDIX Digital Port Error Log Entries 2 of 2
Error Type
Aux
Data
Associated Test
Alarm
Level
On/Off
Board
1 (c)
1 to 20
None
WRN
OFF
15 (d)
Any
None
18 (e)
0
busyout port
location
WRN
OFF
23 (f)
0
None
WRN
OFF
None
WRN
ON
130 (g)
Recommended action
release port location
test port location
257 (h)
40971
None
513 (i)
Any
None
1537 (j)
40968
None
WRN
OFF
1793
Voice & Ctrl.
Local Loop (#13)
MIN
WRN1
ON
test port location l r 3
2049
GPP NPE
Crosstalk Test
(#9)
MIN
WRN1
ON
test port location l r 3
2305 (k)
40967
None
3840 (l)
40965
None
3840 (m)
41029
None
2 of 2
1. Minor alarms on this MO may be downgraded to Warning alarms based on the values used in set options.
Notes:
a. Error Type 0: run the short test sequence. If every test passes, run the long test sequence.
Refer to each appropriate test’s description, and follow its recommended procedures.
b. Error Type 1, Aux Data 40987: the user may experience a noisy port or link due to an
off-board problem. If so, replace the circuit pack (see caution at the beginning of this
section). Once the problem is resolved, the alarm is retired after a predetermined time.
c. Error Type 1, Aux Data 1 to 20: At least 15 off-board problems have been detected with
the link to the voice port. Also see Note (a).
d. Error Type 15: internal error that occurs when an audit request fails.
e. Error Type 18: the port is busied-out by command. Enter release port location to
release the port.
412 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
ADX8D-PT (AUDIX Digital Port)
f. Error Type 23: the circuit pack is administered but not physically installed. The alarm will
clear when a circuit pack is inserted.
g. Error Type 130: the circuit pack was 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).
h. Error Type 257: Something is interfering with transmission to the voice port. This is usually
an on-board problem and can be ignored if there are no user complaints.
i. Error Type 513: AUDIX is not available to the switch, possibly due to a busyout on the
AUDIX system. See DEFINITY® AUDIX Maintenance, 585-300-110, if necessary.
j. Error Type 1537: There is a problem with the link to the voice port. This error can be
ignored if there are no user complaints. If the problem persists, replace the circuit pack (see
Caution at the beginning of this section). Once the problem is resolved, the alarm is retired
after a certain period of time.
k. Error Type 2305: the link between the circuit pack and the voice port successfully reset. No
action is necessary.
l. Error Type 3840, Aux Data 40965: no voice ports are connected to the EMBEDDED
AUDIX circuit pack. No maintenance action is required.
m. Error Type 3840, Aux Data 41029: the message buffer in the circuit pack is full.
Demand test descriptions and error codes
Investigate tests in the order presented. By clearing errors associated with the first test, errors
generated from other tests may also be cleared. Click on the link to see the full description of
the test, error codes, and recommended actions.
Order of Investigation
Short Test
Sequence
Long Test
Sequence
D/ND1
Local Loop Test (#13)
X
ND
GPP NPE Crosstalk Test (#9)
X
ND
1. D = Destructive; ND = Nondestructive
Issue 3 February 2007
413
Communication Manager Maintenance Object Repair Procedures
ADX8D-RS (AUDIX Reserve Slots)
See AXA12-RS (AUDIX Reserve Slots).
414 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
ADX16A-B (AUDIX Circuit Pack)
ADX16A-B (AUDIX Circuit Pack)
MO Name in Log
Alarm
Level
Initial Command to Run
Full Name of MO
ADXCL-BD
MIN
test board location
AUDIX circuit pack
ADX16A-B
WRN
test board location
The ADX16A-BD MO represents a TN566/TN2169 EMBEDDED AUDIX circuit pack
combination operating in control-link (CL) mode.
For circuit-pack-level problems, see XXX-BD (Common Port Circuit Pack/Media Module).
Port-level maintenance is covered by AESV-LNK (AE Services Link).
EMBEDDED AUDIX consists of two circuit packs that occupy 5 slots on a port carrier. The tests
apply only to switch-side maintenance that tests a circuit pack’s components related to the
TDM-bus interface. The AUDIX system has an extensive maintenance strategy that is
described in DEFINITY® AUDIX Maintenance, 585-300-110.
Issue 3 February 2007
415
Communication Manager Maintenance Object Repair Procedures
ADX16A-P (AUDIX Analog Line/Control Link)
MO Name in
Log
Alarm
Level
Initial Command to Run
Full Name of MO
ADXCL-PT
ADX16A-P
MIN
test port location l
AUDIX Analog Line/ Control Link
ADXCL-PT
ADX16A-P
WRN
test port location
AUDIX Analog Line/ Control Link
! CAUTION:
Never do any of the following without first shutting down AUDIX. Follow the
instructions on the TN566/TN2169 faceplate:
CAUTION:
●
Remove EMBEDDED AUDIX circuit packs
●
Cycle power to a carrier containing EMBEDDED AUDIX circuit packs
●
Remove power to a carrier containing EMBEDDED AUDIX circuit packs
The ADX16A-P MO represents a port on a TN566/TN2169 EMBEDDED AUDIX circuit pack that
is operating in control-link (CL) mode.
For circuit-pack-level problems (ADX16A-B or ANL-16-BD), see XXX-BD (Common Port Circuit
Pack/Media Module) on page 1407.
For port-level problems with AUDIX operating in digital-port mode, see:
●
ADX8D-PT (AUDIX Digital Port) on page 411
●
ADX16D-P (16-Port AUDIX Digital Port) on page 420
The tests described in this section apply only to switch-side maintenance that tests a circuit
pack’s components related to the TDM-bus interface. The AUDIX system has an extensive
maintenance strategy that is described in DEFINITY® AUDIX Maintenance, 585-300-110.
AUDIX resides on a combined pair of circuit packs: the TN566 Multifunction board (MFB) and
the TN2169 Alarm board (ALB). Because of its size this combination occupies 5 slots, but only 1
slot is functional as far as the switch is concerned. The other 4 slots are seen by the switch as
“AUDIX-reserved” slots.
In CL mode the TN566 pack supports up to 16 voice ports. When a call to a station with an
AUDIX login is not answered, AUDIX answers the call using one of the available voice ports.
Unlike other AUDIX systems, EMBEDDED AUDIX is not an adjunct.
416 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
ADX16A-P (AUDIX Analog Line/Control Link)
Error log entries and recommended actions
Table 109: EMBEDDED AUDIX Analog Line/Control Link Error Log Entries
Error
Type
Aux
Data
Associated Test
Alarm
Level
On/Off
Board
Recommended action
01
0
Any
Any
Any
test port location
1 (a)
40977
None
18
0
busyout
station ext
WRN
ON
release station extension
23 (b)
0
None
WRN
OFF
None
WRN
ON
test port location
130
(c)
257
(d)
40973
None
513
(e)
Any
None
1025
(f)
Looparound Test
(#161)
MIN
WRN2
ON
test port location l r 2
1281
Conference Circuit
Test (#7)
MIN
WRN2
ON
test port location l r 2
1537
NPE Crosstalk Test
(#6)
MIN
WRN2
ON
test port location l r 2
1. Run the short test sequence first. If every test passes, run the long test sequence. Refer to each
appropriate test’s description, and follow its recommended procedures.
2. Minor alarms on this MO may be downgraded to Warning alarms based on the values used in set options.
Notes:
a. Error Type 1 is an inline error that can only be resolved over time. No terminal equipment
was present when ringing was attempted. Execute test port location
b. Error Type 23: The circuit pack was logically administered but not physically installed. The
alarm will clear when the circuit pack is installed.
c. Error Type 130: The circuit pack was removed or has been insane for more than
11 minutes. To clear the error, reseat or replace the circuit pack.
Issue 3 February 2007
417
Communication Manager Maintenance Object Repair Procedures
d. Error Type 257 is an inline error and can only be resolved over time. Ringing voltage is
absent. If only one analog circuit pack in the system has this problem, replace the circuit
pack. If only analog circuit packs on a particular carrier have this error, the ringing generator
may not be connected to this carrier. If analog circuit packs on many carriers have this error,
check the ringing generator.
e. Error Type 513: AUDIX is not available to the switch. Check the AUDIX system, referring to
DEFINITY® AUDIX Maintenance, 585-300-110.
f. Error Type 1025: The TDM bus is out of service. See TDM-BUS (TDM Bus) on page 1288.
Demand test descriptions and error codes
Investigate tests in the order presented. By clearing errors associated with the first test, errors
generated from other tests may also be cleared. Click on the link to see the full description of
the test, error codes, and recommended actions.
Long Test
Sequence
D/ND1
Analog Looparound Test (#161))
X
ND
Conference Circuit Test (#7)
X
ND
NPE Crosstalk Test (#6)
X
ND
Order of Investigation
Short Test
Sequence
1. D = Destructive; ND = Nondestructive
Tests 36 and 48 ABORT when AUDIX is not running.
418 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
ADX16D-B (16-Port AUDIX Circuit Pack)
ADX16D-B (16-Port AUDIX Circuit Pack)
MO Name in Log
Alarm
Level
Initial Command to Run
Full Name of MO
ADX16D-B
MIN
WRN
test board location
AUDIX circuit pack
The ADX16D-B MO represents a TN566/TN2169 EMBEDDED AUDIX circuit pack combination
operating in 16-port mode digital (DP).
For circuit-pack-level problems, see XXX-BD (Common Port Circuit Pack/Media Module) on
page 1407.
Port-level maintenance is covered by ADX16D-P (16-Port AUDIX Digital Port) on page 420.
EMBEDDED AUDIX consists of two circuit packs that occupy 5 slots on a port carrier. The tests
apply only to switch-side maintenance that tests a circuit pack’s components related to the
TDM-bus interface. The AUDIX system has an extensive maintenance strategy of its own that is
described in DEFINITY® AUDIX Maintenance, 585-300-110.
Issue 3 February 2007
419
Communication Manager Maintenance Object Repair Procedures
ADX16D-P (16-Port AUDIX Digital Port)
MO Name in Log
Alarm
Level
Initial Command to Run
Full Name of MO
ADX16D-P
MIN
WRN
test port location l
AUDIX Digital port
! CAUTION:
Never do any of the following without first shutting down AUDIX. Follow the
instructions on the TN566/TN2169 faceplate:
CAUTION:
●
Remove EMBEDDED AUDIX circuit packs
●
Cycle power to a carrier containing EMBEDDED AUDIX circuit packs
●
Remove power to a carrier or cabinet containing EMBEDDED AUDIX circuit pack
The ADX16D-P MO represents a port on a TN566/TN2169 EMBEDDED AUDIX circuit pack
operating in digital-port (DP) mode. The maintenance strategy for ports on the TN566 operating
in control-link mode is described in ADX16A-P (AUDIX Analog Line/Control Link).
The tests described in this section apply only to switch-side maintenance that tests a circuit
pack’s components related to the TDM-bus interface. The AUDIX system has an extensive
maintenance strategy that is described in DEFINITY® AUDIX Maintenance, 585-300-110.
AUDIX resides on a combined pair of circuit packs: the TN566 Multifunction board (MFB) and
the TN2169 Alarm board (ALB). Because of its size this combination occupies 5 slots, but the
system sees only 1 slot as functional. The other 4 slots are seen by the switch as
“AUDIX-reserved” slots (or ADX16-RES/ADX16D-RS).
In 16-port DP mode, the TN566 pack supports up to 16 voice ports, each with a primary and a
secondary information channel. Ports are administered in increments of two. When a call to a
station with an AUDIX login is not answered, AUDIX answers the call using one of the available
voice ports.
Unlike other AUDIX systems, EMBEDDED AUDIX is not an adjunct.
420 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
ADX16D-P (16-Port AUDIX Digital Port)
Error log entries and recommended actions
Table 110: EMBEDDED AUDIX Digital Port Error Log Entries
Error
Type
Aux
Data
Associated Test
Alarm
Level
On/
Off
Board
Recommended action
0 (a)
0
Any
Any
Any
test port location
1 (b)
40987
None
WRN
OFF
1 (c)
1 to 20
None
WRN
OFF
15 (d)
Any
None
18 (e)
0
busyout port
location
WRN
OFF
23 (f)
0
None
WRN
OFF
None
WRN
ON
130 (g)
release port location
test port location
257 (h)
40971
None
513 (i)
Any
None
1537 (j)
40968
None
WRN
OFF
1793
Voice and Control
Local Loop Test
(#13)
MIN
WRN1
ON
test port location l r 3
2049
GPP NPE
Crosstalk Test (#9)
MIN
WRN1
ON
test port location l r 3
2305
(k)
40967
None
3840 (l)
40965
None
3840
(m)
41029
None
1. Minor alarms may be downgraded to Warning alarms based on the values used in set options.
Notes:
a. Error Type 0: run the short test sequence first. If every test passes, run the long test
sequence. Refer to each test’s description, and follow the recommended procedures
Issue 3 February 2007
421
Communication Manager Maintenance Object Repair Procedures
b. Error Type 1 with Aux Data 40987: The user may experience a noisy port or link, due to an
off-board problem that is detected by the port circuit. If so, replace the circuit pack (see
caution at the beginning of this section). Once the problem is resolved, the alarm is retired
after a predetermined time.
c. Error Type 1: At least 15 off-board problems have been detected with the link to the voice
port. When an error with the link is detected, an on-board counter is incremented. Also see
Note a above.
d. Error Type 15: An internal type error that occurs when an audit request fails.
e. Error Type 18: The port is busied-out by command. Release the port with release port
location.
f. Error Type 23: The circuit pack is administered but not physically installed. The alarm will
clear when a circuit pack is inserted.
g. Error Type 130: The circuit pack has been removed or has been insane for more than
21-minutes. To clear the error, reseat or replace the AUDIX circuit pack (see caution at the
beginning of this section).
h. Error Type 257: Something is interfering with transmission to the voice port. This is usually
an on-board problem and can be ignored if there are no user complaints.
i. Error Type 513: AUDIX is not available to the switch, possibly due to a busyout on the
AUDIX system. Refer to DEFINITY® AUDIX Maintenance, 585-300-110.
j. Error Type 1537: An inline maintenance error has generated an off-board warning due to
some problem with the link to the voice port. This can be ignored if there are no user
complaints. If the problem persists, replace the circuit pack (see caution at the beginning of
this section). Once the problem is resolved, the alarm is retired after a certain period of time.
k. Error Type 2305: The link between the circuit pack and the voice port is successfully reset.
No craft action is necessary.
l. Error Type 3840 with Aux Data 40965: No voice ports are connected to the EMBEDDED
AUDIX circuit pack. No maintenance action is required.
m. Error Type 3840 with Aux Data 41029: The message buffer in the circuit pack is full.
422 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
ADX16D-P (16-Port AUDIX Digital Port)
Demand test descriptions and error codes
Investigate tests in the order presented. By clearing errors associated with the first test, errors
generated from other tests may also be cleared. Click on the link to see the full description of
the test, error codes, and recommended actions.
Long Test
Sequence
D/ND1
Local Loop Test (#13)
X
ND
GPP NPE Crosstalk Test (#9)
X
ND
Order of Investigation
Short Test
Sequence
1. D = Destructive; ND = Nondestructive
Issue 3 February 2007
423
Communication Manager Maintenance Object Repair Procedures
AESV-LNK (AE Services Link)
MO Name in Log
Alarm
Level
Initial Command to Run
Full Name of MO
AESV-LNK
MAJ
WRN
test aesvcs-server
Application Enablement
Services (AESVCS)
Link
AESVCS Links provide a connection between Communication Manager and an AESVCS
Server in which data is exchanged. Communication Manager dynamically creates and deletes
AESVCS Links as socket connections to the AESVCS Server are established and torn down.
AESVCS Links that are connected to the same AESVCS Server are grouped into an AESVCS
Session.
Error log entries and recommended actions
Table 111: AESV-LNK Error Log Entries
Error Type
Aux
Data
Associated
Test
513 (a)
AESVCS
Link
Heartbeat
Test (#1624)
769 (b)
1537 (c)
2561 (d)
Any
Alarm
Level
On/Off
Board
Recommended action
WRN
Off
none
Log
only
test aesvcs link link#
Log
only
Log
only
Notes:
a. Error Type 513 is displayed when an AESVCS Link is hyperactive. The hyperactivity might
be caused by fluctuations in the engineered traffic load being generated by the AESVCS
Server. Both an AESVCS Session level and Link level alarm is generated to indicate that a
link is overloaded.
Once the problem has been resolved, it might take up to 45 minutes for the alarm to clear
due to the “leaky bucket” strategy. If the hyperactivity persists, escalate the problem.
b. Error type 769 is a log only error and is displayed when Communication Manager does not
receive a response from the AESVCS Server to a heartbeat message that was sent over
424 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
AESV-LNK (AE Services Link)
the AESVCS Link. Failure to receive a response to a heartbeat message results in the
deletion of the AESVCS Link by Communication Manager. Both an AESVCS Session Level
and Link level error is generated against this condition. Escalate if the error persists.
c. Error type 1537 is a log only error and displayed when an AESVCS Link is deleted from an
AESVCS Session for reasons other than a heartbeat failure. Both an AESVCS Session
Level and Link level error is generated against this condition. The Aux Data field contains
the reason code.
Aux Data
Description
1
The far end closed the socket connection. Check the error logs on
the AEVCS Server for more information.
100
The reset aecvcs-link command was used to close the socket
connection
101
The AESVCS Interface on the IP Services form was disabled.
102
The AESVCS Interface was removed from the IP Services form.
103
The AE Services Server was disabled on the AE Services
Administration page of the IP Services form.
104
The AE Services Server was deleted on the AE Services
Administration page of the IP Services form.
200
The socket connection closed due to an internal error. Escalate if the
problem persists.
201
The socket connection was unexpectedly closed by Communication
Manager. Escalate if the problem persists.
202
Communication Manager detected and error and closed the socket
connection. Escalate if the problem persists.
203
Communication Manager detected an error reading from the socket
and closed the connection. Escalate if the problem persists.
204
Communication Manager failed to write a complete message and
closed the socket connection. Escalate if the problem persists.
205
AE Server established a new connection causing Communication
Manager to close the existing one. Escalate if the problem persists.
206
Communication Manager failed to send a heartbeat request and
closed the socket connection. Escalate if the problem persists.
207
Communication Manager detected a protocol violation and closed
the socket connection. Escalate if the problem persists.
1 of 2
Issue 3 February 2007
425
Communication Manager Maintenance Object Repair Procedures
Aux Data
Description
208
Communication Manager detected processing the data from the
AESVCS Server and closed the socket connection. Escalate if the
problem persists.
209
Communication Manager could not read data from the socket and
closed the connection. Escalate if the problem persists.
2 of 2
d. Error Type 2561 is a log only error and is displayed when an AESVCS message is
discarded due to a link buffer overflow. Both an AESVCS Session Level and Link level error
is generated against this condition. Escalate if the problem persists.
Demand test descriptions and error codes
Investigate tests in the order presented. By clearing errors associated with the first test, errors
generated from other tests may also be cleared. Click on the link to see the full description of
the test, error codes, and recommended actions.
Order of Investigation
D/ND1
Short Test
Sequence
Long Test
Sequence
AESVCS Link Heartbeat Test (#1624)
X
X
ND
AESVCS Session Level Link Status Test (#1623)
X
X
ND
1. D = Destructive; ND = Nondestructive
426 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
AESV-SES (AE Services Session)
AESV-SES (AE Services Session)
MO Name in Log
Alarm
Level
Initial Command to Run
Full Name of MO
AESV-SES
MAJ
WRN
test aesvcs-server
Application Enablement
Services Session
An AESVCS Session is a logical connection between Communication Manager and a single
AESVCS Server, and encompasses all the AESVCS Links that are connected between them.
Error log entries and recommended actions
Table 112: AESV-SES Error Log Entries
Error Type
Aux
Data
Associated
Test
513 (a)
1-16
769 (b)
1-16
1025 (c)
1-16
MAJ
1537 (d)
1-16
Log
only
2561 (e)
1-16
Log
only
AESVCS
Link
Heartbeat
Test (#1624)
Alarm
Level
On/Off
Board
Recommended action
WRN
Off
none
Off
test aesvcs-server
Log
only
Notes:
a. Error Type 513 occurs when one or more AESVCS Links within a given AESVCS Session
is hyperactive. The hyperactivity might be caused by fluctuations in the engineered traffic
load being generated by the AESVCS Server. Both an AESVCS Session Level and Link
level alarm is generated to indicate that a link is overloaded. The Aux Data field contains the
link ID of the last AESVCS Link to report hyperactivity.
Once the problem has been resolved, it might take up to 45 minutes for the alarm to clear
due to the “leaky bucket” strategy. Refer to AESV-LNK (AE Services Link) for more
information.
b. Error type 769 is a log only error and is displayed when Communication Manager detects a
heartbeat failure on one or more AESVCS Links within the AESVCS Session. The Aux Data
Issue 3 February 2007
427
Communication Manager Maintenance Object Repair Procedures
field contains the link ID of the last AESVCS Link to report a heartbeat failure. An AESVCS
Link level error is also generated against this condition. Refer to AESV-LNK (AE Services
Link) for more information.
c. Error Type 1025 is displayed when no AESVCS Links are left in an AESVCS Session. This
alarm is cleared when Communication Manager associates a new AESVCS Link to the
session. The Aux Data field contains the link ID of the last AESVCS Link deleted from the
session.
d. Error type 1537 is a log only error and is displayed when one or more AESVCS Links,
within the AESVCS Session is deleted for reasons other than a heartbeat failure. The Aux
Data field contains the link ID of the last AESVCS Link deleted from the session. An
AESVCS Link level error is also generated against this condition. Refer to AESV-LNK (AE
Services Link) for more information.
e. Error Type 2561 is a log only error and is displayed when one or more AESVCS Links
within the AESVCS Session is discarding messages due to a link buffer overflow. This error
represents the sum of all the discarded messages in a given session. The Aux Data field
contains the link id of the last AESVCS Link, within the session, to discard a message. An
AESVCS Link level error is also generated against this condition. Refer to AESV-LNK (AE
Services Link) for more information.
Demand test descriptions and error codes
Investigate tests in the order presented. By clearing errors associated with the first test, errors
generated from other tests may also be cleared. Click on the link to see the full description of
the test, error codes, and recommended actions.
Order of Investigation
D/ND1
Short Test
Sequence
Long Test
Sequence
AESVCS Link Heartbeat Test (#1624)
X
X
ND
AESVCS Session Level Link Status Test (#1623)
X
X
ND
1. D = Destructive; ND = Nondestructive
428 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
ALARM-PT (Alarm Port)
ALARM-PT (Alarm Port)
MO Name in Log
Alarm
Level
Initial Command to Run
Full Name of MO
ALARM-PT
MIN
test port location l
Alarm Port
WRN
test port location
The Alarm Port MO provides on-board maintenance for an analog line port that is administered
as an external device alarm port. Tests are provided to verify the analog line port’s ability to
detect an external device alarm. The related MO, EXT-DEV ADMIN? Y (External Device
Alarm) on page 814, is used for the off-board external device alarm.
Error log entries and recommended actions
Table 113: ALARM-PT Error Log Entries
Error
Type
Aux
Data
Associated Test
Alarm
Level
On/Off
Board
Recommended action
0 (a)
0
Any
Any
Any
test port location
15 (b)
Any
Port Audit and
Update (#36)
18
0
busyout station
extension
WRN
OFF
release station extension
None
WRN
ON
test port location
130 (c)
Notes:
a. Error Type 0: Run the short test sequence first. If every test passes, run the long test
sequence. Refer to each appropriate test’s description, and follow its recommended
procedures.
b. Error Type 15 is a software audit error that does not indicate any hardware malfunction.
Run the short test sequence and investigate errors.
c. Error Type 130 indicates that the circuit pack or Media Module was removed or has been
insane for more than 11 minutes. To clear the error, reseat or replace the circuit pack or
Media Module
Issue 3 February 2007
429
Communication Manager Maintenance Object Repair Procedures
Demand test descriptions and error codes
Investigate tests in the order presented. By clearing errors associated with the first test, errors
generated from other tests may also be cleared. Click on the link to see the full description of
the test, error codes, and recommended actions.
Short Test
Sequence
Long Test
Sequence
D/ND1
Port Diagnostic Test (#35)
X
X
ND
Port Audit And Update Test (#36)
X
X
ND
Order of Investigation
1. D = Destructive; ND = Nondestructive
430 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
AN-LN-PT (Analog Line Port)
AN-LN-PT (Analog Line Port)
MO Name in Log
Alarm Level
Initial Command to Run
Full Name of MO
AN-LN-PT
MIN
test port location l
Analog Line port
WRN
test port location
The TN793B/TN2793B Analog Line (w/ Caller ID) and the TN797 Analog Trunk and Line circuit
packs support AN-LN-PT.
The TN793B/TN2793B Analog Line circuit pack (w/ Caller ID) provides 24 ports for voice
terminals and supports both on-premises and off-premises analog voice terminals.
Note:
Note:
The TN793B/TN2793B analog line circuit pack supports analog data modules.
When assigned, analog data modules provide access to the NETPKT (TN794
circuit pack) data ports. To activate an analog data module, you must assign the
port location on the data screen and connect a modem to the port. The analog
data module can be used for connection to a CDR output, or other adjuncts as
needed. These ports are tested like any other analog port on the circuit pack.
For S8500, S8700 products, CDR data is moved via LAN to a CDR adjunct.
The TN797 Analog Trunk and Line circuit pack provides 8 ports, each of which may be
administered in any of several ways, as described in TR-LN-BD (Analog Trunk/Line Board).
The MM711 Analog Trunk and Line Media Module provides 8 ports. The MM716 provides 24
ports. Each of the ports may be administered in any of several ways, as described in MG-ANA
(Analog Media Module). Not all tests that run on the TN797 circuit pack are applicable to the
media modules, and will abort with error code 1412. This error can be ignored.
Ringing caused by maintenance testing
Test #48 may cause some terminal equipment to ring briefly during daily maintenance. If this
ringing disturbs the customer or the terminal equipment, disable it in the Tests field of the
change station extension form. Be aware that this action also disables Tests #6, 7, 161,
and 35 on some software releases.
Issue 3 February 2007
431
Communication Manager Maintenance Object Repair Procedures
Error log entries and recommended actions
Table 114: AN-LN-PT Error log entries
Error
Type
Aux
Data
Associated Test
Alarm
Level
On/Off
Board
Recommended Action
0 (a)
0
Any
Any
Any
test port location
1 (b)
40960
40975
40977
none
15 (c)
Any
Port Audit and Update (#36)
18
0
busy station extension
WRN
ON
release station extension
None
WRN
ON
test port location
130 (d)
257 (e)
40973
None
513 (f)
Ringing Application Test (#48)
WRN
OFF
test port location r 2
769
Port Diagnostic Test (#35)
MIN
WRN1
ON
test port location r 2
1025
Looparound test (#161)
MIN
WRN2
ON
test port location l r 2
1281
Conference Circuit Test (#7)
MIN
WRN2
ON
test port location l r 2
1537
NPE Crosstalk Test (#6)
MIN
WRN2
ON
test port location l r 2
1. Minor alarms on this MO may be downgraded to Warning alarms based on the values used in set
options.
Notes:
a. Error type 0: Run the short test sequence first. If every test passes, run the long test
sequence. Refer to each appropriate test’s description, and follow its recommended
procedures.
b. Error Type 1: these are inline 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. A 5th incoming call
causes an inline error from the board.
Aux Data 40975 indicates that the terminal equipment was on-hook when ring-tip was
detected during ringing. This usually indicates a failure in the terminal equipment or the
type of terminal has a low ringer impedance.
1. Call the terminal equipment and verify that the terminal rings.
432 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
AN-LN-PT (Analog Line Port)
2. If the terminal does not ring, replace it.
3. Otherwise, run test port location, and follow the procedure for Test #48.
●
Aux Data 40977 indicates that no terminal equipment was connected when ringing was
attempted. Run test port location, and follow the procedure for the results of Test
#48
c. Error Type 15: this is a software audit error that does not indicate any hardware
malfunction. Run the short test sequence, and investigate any associated errors.
d. Error Type 130: this error type indicates that the circuit pack or media module has been
removed or has been insane for more than 11 minutes. To clear the error, reseat or replace
the circuit pack or media module.
e. Error Type 257: this is an inline error and can only be resolved over time. This error
indicates that ringing voltage is absent.
For media modules: If not resolved over time, replace the media module.
For circuit packs:
●
●
●
If only 1 analog circuit pack in the system has this problem, replace the circuit pack.
If only analog circuit packs on a particular carrier have this error, the ringing generator
may not be connected to this carrier.
If analog circuit packs on many carriers have this error, it is probably a problem with
the ringing generator.
f. Error Type 513:Test #48 can cause some terminal equipment to ring briefly during daily
maintenance.
1. If this disturbs the customer or the terminal equipment, disable it by setting the Tests
field on the change station extension form to n. In some software releases, this
also disables Tests #6, 7, 161, and 35.
Issue 3 February 2007
433
Communication Manager Maintenance Object Repair Procedures
Demand test descriptions and error codes
Investigate tests in the order presented. By clearing errors associated with the first test, errors
generated from other tests may also be cleared. Click on the link to see the full description of
the test, error codes, and recommended actions.
Order of Investigation
Short Test
Sequence
Long Test
Sequence
D/
ND1
Port Diagnostic Test (#35)
X
X
ND
ONS Ringer Application Test (#48)
X
X
ND
Analog Looparound Test (#161)
X
ND
Conference Circuit Test (#7)
X
ND
NPE Crosstalk Test (#6)
X
ND
X
ND
Port Audit And Update Test (#36)
X
1. D = Destructive; ND = Nondestructive
434 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
ANL-16-L (16-Port Analog Line)
ANL-16-L (16-Port Analog Line)
MO Name in Log
Alarm Level
Initial Command to Run
Full Name of MO
ANL-16-L
MIN
test port location l
16-Port Analog Line
WRN
test port location
The circuit packs listed below provide 16 analog line ports for single-line voice terminals. The
table below indicates which circuit packs are equipped with lightning protection (for
off-premises, out-of -building stations), and which ones support the neon message waiting lamp
feature.
16-Port Analog Line Circuit Packs
Circuit Pack
TN468B
Off- Premises
Neon
y
TN479
TN746
y
TN746B
y
TN2135
y
TN2144
y
TN2149
y
TN2180
y
y
S8700 Series | S8500
These circuit packs provide 16 ports for analog voice terminals. The TN746, TN468, and TN749
support only single-line, on-premises/in-building, analog voice terminals, and not off-premises
stations, since these circuit packs are not equipped with lightning protection. The TN746B,
TN2144, TN2149, and TN468B support both on-premises and off-premises (that is,
out-of-building) analog voice terminals. The TN468, TN468B, TN479, TN2135, TN2144, and
TN2149 do NOT support the neon message waiting feature.
No maintenance of the terminal connected to the 16-Port Neon Analog Line circuit pack is
performed, except to determine whether or not the terminal is connected. Failures of the neon
message waiting lamp power and the common ringing application circuitry are reported as part
of common port circuit pack errors; see errors 1281 and 1793 in XXX-BD (Common Port Circuit
Pack/Media Module) on page 1407.
Issue 3 February 2007
435
Communication Manager Maintenance Object Repair Procedures
Ringing Caused by Maintenance Testing
Test #48 may cause some terminal equipment to ring briefly during daily maintenance. If this
ringing is disturbing the customer or the terminal equipment, it should be disabled in the Tests
field of the change station extension screen. Be aware that this action will also disable
Tests #6, 7, 161, and 35.
Error log entries and recommended actions
Table 115: ANL-16-L Error Log Entries
Error
Type
Aux
Data
Associated Test
Alarm
Level
On/ Off
Board
Recommended action
0 (a)
0
Any
Any
Any
test port location
1(b)
40960
40975
40977
none
15(f)
Any
Port Audit and Update
(#36)
18
0
busyout station
extension
WRN
ON
release station extension
None
WRN
ON
test port location
130(g)
257(h)
40973
none
513(i)
Ringing Application
Test (#48)
WRN
OFF
test port location r 2
769
Port Diagnostic Test
(#35)
MIN
WRN1
ON
test port location r 2
1025
Looparound (#161)
MIN
WRN1
ON
test port location l r 2
1281
Conference Circuit
Test (#7)
MIN
WRN1
ON
test port location l r 2
1537
NPE Crosstalk Test
(#6)
MIN
WRN1
ON
test port location l r 2
1. Minor alarms on this MO may be downgraded to Warning alarms based on the values used in set options.
436 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
ANL-16-L (16-Port Analog Line)
Notes:
a. Error Type 0: Run the short test sequence first. If every test passes, run the long test
sequence. Refer to each appropriate test’s description, and follow its recommended
procedures.
b. Error Type 1: These are inline errors and can only be resolved over time.
c. 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. A 5th incoming call
causes an inline error from the board.
d. Aux Data 40975 indicates that the terminal equipment was on-hook when ring-tip was
detected during ringing. This usually indicates a failure in the terminal equipment or the type
of terminal has a low ringer impedance. Call the terminal equipment and verify that the
terminal rings. If the terminal does not ring, then replace it. Otherwise, enter test port
location, and follow the procedure for Test #48.
e. Aux Data 40977 indicates that no terminal equipment was connected when ringing was
attempted. Run the short test via test port location, and follow the procedure for the
results of Test #48.
f. Error Type 15 is a software audit error that does not indicate any hardware malfunction.
Run short test sequence, and investigate associated errors.
g. Error Type 130: the circuit pack has been removed or has been insane for more than 11
minutes. To clear the error, reseat or replace the circuit pack.
h. Error Type 257: This is an inline error and can only be resolved over time. This error
indicates that ringing voltage is absent. If only 1 analog circuit pack in the system has this
problem, then replace the circuit pack. If only analog circuit packs on a particular carrier
have this error, then the ringing generator may not be connected to this carrier. If analog
circuit packs on many carriers have this error, then it is probably a problem with the ringing
generator.
i. Error Type 513: Associated Test #48 may cause some terminal equipment to ring briefly
during daily maintenance. If this disturbs the customer or the terminal equipment, disable it
by setting the Tests field on the change station extension screen to n. On some
software releases, this will also disable Tests #6, 7, 161, and 35.
Issue 3 February 2007
437
Communication Manager Maintenance Object Repair Procedures
Demand test descriptions and error codes
Investigate tests in the order presented. By clearing errors associated with the first test, errors
generated from other tests may also be cleared. Click on the link to see the full description of
the test, error codes, and recommended actions.
Short Test
Sequence
Long Test
Sequence
D/ND1
Port Diagnostic Test (#35)
X
X
ND
ONS Ringer Application Test (#48)
X
X
ND
Analog Looparound Test (#161)
X
ND
Conference Circuit Test (#7)
X
ND
NPE Crosstalk Test (#6)
X
ND
X
ND
Order of Investigation
Port Audit And Update Test (#36)
X
1. D = Destructive; ND = Nondestructive
438 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
ANL-BD (Analog Line Circuit Pack)
ANL-BD (Analog Line Circuit Pack)
MO Name in Log
Alarm
Level
Initial Command to Run
Full Name Of MO
ANL-BD
MIN
WRN
test board location
Analog Line circuit pack
See XXX-BD (Common Port Circuit Pack/Media Module) for circuit pack-level errors.
See ANL-16-L (16-Port Analog Line) or ANL-LINE (8-Port Analog Line) for related line
information.
Issue 3 February 2007
439
Communication Manager Maintenance Object Repair Procedures
ANL-LINE (8-Port Analog Line)
MO Name in Log
Alarm
Level
Initial Command To Run
Full Name of MO
ANL-LINE
MIN
test port location l
8-Port Analog Line
WRN
test port location
MIN
test port location l
WRN
test port location
ANL-NE-L
8-Port Neon Analog Line
Error log entries and tests apply to ANL-LINE and ANL-NE-L.
The 8-port Analog Line circuit packs,
TN411
TN443
TN467
TN712
TN742
TN769
provide eight ports for single-line, on or off-premises analog endpoints such as analog voice
terminals, queue warning level lamps, recorded announcements, dictation machines,
PAGEPAC paging equipment, external alerting devices, modems, fax machines, and AUDIX
voice ports. Only the TN769 supports a neon message waiting lamp.
Note:
Note:
PAGEPAC™ is a registered trademark of Harris Corporation, Dragon Division.
Test #48 may cause some terminal equipment to ring briefly during daily maintenance, which
may disturb the customer or the terminal equipment. Test #47 may cause a false alarm when
the port is connected to certain off-premises equipment, non-voice terminal equipment, or loop
equipment. In either case, the tests can be disabled by entering n in the Tests field on the
change station extension screen. Be aware that this will disable Tests 6, 35, 47, and 48.
No maintenance of the terminal connected to the 8-Port Analog Line circuit pack or 8-Port Neon
Analog Line circuit pack is performed, except to determine whether or not the terminal is
connected. Failures of the common ringing application circuitry and the neon message waiting
lamp power (ANL-NE-L only) are reported as errors 1281and 1793 against XXX-BD (Common
Port Circuit Pack) in Table 378: Common Port Circuit Pack Maintenance Error Log Entries on
page 1408.
440 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
ANL-LINE (8-Port Analog Line)
Error log entries and recommended actions
Table 116: 8-Port Analog Line Error Log Entries
Error
Type
Aux
Data
Associated Test
Alarm
Level
On/Off
Board
Recommended Action
0 (a)
0
Any
Any
Any
test port location
1 (b)
40960
40975
40977
None
15 (c)
Any
Port Audit and
Update Test (#36)
18
0
busyout station
extension
WRN
OFF
release station
extension
130
(d)
None
WRN
ON
test port location
257
(e)
Ringing Application
Test (#48)
WRN
OFF
test port location r 3
513
Port Diagnostic Test
(#35)
MIN
WRN1
ON
test port location r 2
769 (f)
Loop Around &
Conference (47)
1025
NPE Crosstalk Test
(#6)
test port location l r 3
MIN
WRN1
ON
test port location l r 3
1281
(g)
1793
(g)
1. Minor alarms on this MO may be downgraded to Warning alarms based on the values used in set options.
Notes:
a. Error Type 0: Run the short test sequence first. If every test passes, run the long test
sequence. Refer to each appropriate test’s description, and follow its recommended
procedures.
Issue 3 February 2007
441
Communication Manager Maintenance Object Repair Procedures
b. Error Type 1: These are inline errors that are resolved over time by the system.
Aux Data 40960: too many simultaneous incoming ringing attempts were made on this
board. Only 4 ports on a board may ring simultaneously. A 5th incoming call will cause an
inline error from the board.
Aux Data 40975: the terminal equipment was on-hook when ring-tip was detected during
ringing. This usually indicates a failure in the terminal equipment or the type of terminal has
a low ringer impedance. Call the terminal equipment and verify that the terminal rings. If the
terminal doesn’t ring, then replace it. Otherwise, enter test port location, and follow
the procedure for Test #48.
Aux Data 40977: no terminal equipment was connected when ringing was attempted. Run
test port location, and follow the procedure for the results of Test #48.
c. Error Type 15: software audit error, does not indicate any hardware malfunction. Run the
short test sequence, and investigate errors (if any).
d. Error Type 130: the circuit pack was removed or has been insane for more than 11 minutes.
To clear the error, reinsert or replace the circuit pack.
e. Error Type 257: Associated Test #48 may cause some terminal equipment to ring briefly
during daily maintenance. If this ringing is disturbing the customer or the terminal
equipment, it should be disabled via change station extension. However, on some
releases of the software, this will disable Tests #6, 47, and 35 as well as Test #48.
f. Error Type 769: Associated Test #47 may cause a false alarm when the port is connected
to off-premises equipment, some non-voice terminal equipment, and some loop equipment.
If this causes a false alarm, use change station, and change the Tests field to n to
disable the test.
g. Error Types 1281 and 1793: See XXX-BD (Common Port Circuit Pack/Media Module).
Demand test descriptions and error codes
Investigate tests in the order presented. By clearing errors associated with the first test, errors
generated from other tests may also be cleared. Click on the link to see the full description of
the test, error codes, and recommended actions.
Short Test Sequence
Long Test Sequence
D/ND1
Port Diagnostic Test (#35)
X
X
ND
ONS Ringer Application Test (#48)
X
X
ND
NPE Crosstalk Test (#6)
X
ND
Looparound and Conference Test (#47)
X
ND
X
ND
Order of Investigation
Port Audit And Update Test (#36)
X
1. D = Destructive; ND = Nondestructive
442 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
ANL-NE-L (8-Port Analog Line)
ANL-NE-L (8-Port Analog Line)
This maintenance object covers the neon message waiting lamp power on the 8-port analog
line board.
See ANL-LINE (8-Port Analog Line).
Issue 3 February 2007
443
Communication Manager Maintenance Object Repair Procedures
ANN-BD (Announcement circuit pack)
Note:
MO Name in Log
Alarm Level
Initial command to run
Full name of MO
ANN-BD
MIN
WRN
test board location l
Announcement Circuit Pack
Note:
The information contained in ANN-BD refers only to the TN750-series of circuit
packs. Expressions such as "announcement circuit pack" and "announcement
board" are to be interpreted to mean the TN750-series only.
The TN750 Announcement circuit pack is a service circuit which provides an integrated means
for recording announcements that can be played back on demand by call processing as part of
a calling feature (for example, announcements on hunt group calls). There are 16
Announcement Ports on the Announcement circuit pack. Each port can play any integrated
announcement, independently of the other ports. In addition to the 16 Announcement Ports, the
Announcement circuit pack also has one Data Line Circuit Port (port 17). The Data Line Circuit
Port is used for uploading/downloading the announcement memory to/from the memory card. If
there are any errors associated with port 17, refer to DAT-LINE (Data Line Port). If there are any
errors associated with any other port, refer to ANN-PT (Announcement Port).
Note:
Note:
TN750C is required if your system has multiple TN750x announcement boards
(up to ten are allowed). Only one TN750A/B may be present in the system with
up to nine additional TN750C boards. All ten boards may be TN750C. The
announcements from a TN750A/B can be saved and restored to a TN750C, but
once the announcements are recorded onto a TN750C they are not backward
compatible with the TN750A/B.
The Announcement circuit pack has two processors on it. The first processor, or Angel, controls
the circuit pack and communicates with the switch via the control channel on the TDM Bus. The
second processor, or Speech Processor (SP), controls the speech memory and
announcements. Digital speech is converted from its TDM Bus form to an internal storage form
(for recording) and vice versa (for playbacks) by the 140AY device on the circuit pack, which
has 16 channels (one for each Announcement Port).
General notes
Here are a few 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.
1. The TN750 Announcement circuit pack retains all integrated announcements as long as the
circuit pack has power. For this reason, whenever there is a problem with either the
444 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
ANN-BD (Announcement circuit pack)
Announcement circuit pack or an Announcement Port that may require the circuit pack to be
reset, it is always best to try to reset the circuit pack via reset board PCSS first. If that
does not work, replace the circuit pack. Announcements are preserved through a software
reset, but they are lost when the circuit pack is reseated.
2. If a customer has announcements on the Announcement circuit pack, then announcements
must be saved on the memory card to ensure that they are not lost. This should be done as
soon as the announcements are recorded on the circuit pack (or whenever they are
changed), assuming that the circuit pack is in proper working order (see Note).
Note:
Note:
Unlike translations, announcements are NEVER automatically saved to the
memory card.
3. Save announcements replaces the TN750x announcement file on the memory card.
Care must be taken not to mistakenly enter this command and, as a result, destroy a valid
file on the memory card.
4. Restore announcements replaces the TN750x Announcement circuit pack speech
memory with the announcement file on the memory card. Care must be taken not to
mistakenly enter this command, destroying valid speech memory, especially if the memory
card does not have a valid announcement file on it.
5. Whenever the TN750x Announcement circuit pack is replaced, announcements must
always be rerecorded or downloaded to the new circuit pack. Otherwise, call processing is
not able to use the pack.
6. If announcement speech memory is corrupted, announcements should not be saved [that
is, if the Announcement Checksum Test (#209) fails, or if the speech sounds corrupted on
playback]. This can ruin a good announcement file on the memory card and potentially
cause errors/alarms on any circuit pack to which the new file is downloaded. However, if the
customer does not have a valid announcement file on the memory card, announcements
can be saved in an effort to try to retain some of them (all of the announcements recorded
may not be corrupted).
7. Due to a hardware fault in the TN750 announcement board, the following sequence of
events may cause the announcement file to become corrupted and unusable:
a. Fill the board with recorded announcements.
b. Delete the last few announcements recorded.
c. Re-record the announcements deleted.
If the announcement file becomes corrupted, the only solution is to re-record all
announcements. To do this, follow these steps:
d. Remove the announcement board.
e. Remove the tape cartridge from the tape drive. Do this so that announcements are not
automatically restored from tape.
f. Re-insert the announcement board.
Issue 3 February 2007
445
Communication Manager Maintenance Object Repair Procedures
g. Re-record all announcements.
h. Insert the tape cartridge in the tape drive.
i. Enter save announcements to save all the announcements on the tape.
This hardware fault is fixed in the TN750B announcement board. However, the TN750B
board will not automatically correct an announcement file which has previously been
corrupted by a TN750 board. The only way to correct an announcement file corrupted by
the TN750 board is to follow the steps above.
Announcement administration
A brief description of the integrated announcement administration is given here to aid in
troubleshooting the Announcement circuit pack and its ports. In many cases, it is necessary to
record, play back, and/or delete announcements to resolve an alarm. 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 Guide for
Avaya Communication Manager, 03-300509.
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. Dial tone should be returned at this point. Enter the extension of the
announcement that needs to be recorded, deleted, or played back. Again, dial tone should be
heard. To record an announcement, press station keypad digit 1, record after the tone, and
hang up when done. To play back an announcement, press 2. To delete an announcement,
press 3 (confirmation tone is given if the delete worked). Announcements can also be played
back by simply calling the announcement extension associated with them.
Uploading/Downloading announcements
Integrated announcements on the TN750 Announcement circuit pack can be uploaded to the
memory card with save announcements. Likewise, integrated announcements can be
downloaded to the Announcement circuit pack with restore announcements. Both of these
commands require a free data module of NETCON type to be administered, a data module of
announcement type (on the Announcement circuit pack) to be administered, and a memory
card. These commands are useful in maintaining the customer’s recorded announcements.
446 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
ANN-BD (Announcement circuit pack)
Depending on system traffic, announcement uploads and/or downloads take between 30 and
45 minutes.
The system automatically tries to download the Announcement circuit pack five minutes after it
is inserted. This automatic download procedure is aborted if:
●
An announcement is recorded within 10 minutes of circuit pack insertion.
●
An announcement download is invoked sooner with the restore announcements.
●
No announcement and/or NETCON data module is administered.
●
Note:
Either the announcement data module is busy or all the administered NETCON data
modules are busy.
●
No memory card is in the system.
●
The memory card in the system does not have a valid announcement file saved on it.
Note:
Unlike translations, there is no provision in the system for automatically saving
announcements to the memory card.
Announcement Board Locked Condition
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. Also, save/restore announcements will not work since the record port looks
busy to the circuit pack. Note that software does not have any way of knowing this and will
attempt to use the ports.
If the circuit pack is locked into this state, the following symptoms will be observed:
1. When attempting to record an announcement, users will hear the proper record tone, but
the announcement will not record (they will not know it until the announcement is played
back).
2. Performing a test board long when the circuit pack is in this state will yield the
following abort codes:
●
Ports 1 AND 9 abort Test 206 with code 1024.
●
Ports 1 AND 9 abort Test 205 with code 2000.
●
Board-level Tests 209 and 210 abort with code 1024.
3. The save/restore announcements times out with:
Error encountered, can’t complete request
Issue 3 February 2007
447
Communication Manager Maintenance Object Repair Procedures
The Announcement circuit pack lock-up can be cleared remotely by performing a soft reset to
the circuit pack:
●
busyout board location (this command drops every call in progress on the
Announcement circuit pack).
●
Reset circuit pack using reset board location.
●
Release board using release board location.
Error log entries and recommended actions
Table 117: Announcement circuit pack error log entries 1 of 2
Error
Type
Aux
Data
Associated test
Alarm
Level (See
WRN
message)
On/off
Board
Recommended action
0 (a)
0
Any
Any
Any
test board location
1 (b)
0
Circuit pack removed or SAKI Test
failed (#53)
MIN
ON
2 (c)
None
14 (d)
1 to 64
Announcement Checksum (#209)
18
0
busyout board PCSS
WRN
OFF
23 (e)
0
None
WRN
OFF
None
MIN
ON
125 (f)
170
0
None
MIN
ON
217 (g)
0
None
WRN
OFF
257
65535
Control Channel Looparound Test
(#52)
MIN
ON
257 (h)
Any
None
267 (g)
0
None
WRN
OFF
513 (i)
Any
None
1025 (j)
4363
NPE Audit Test (#50)
1281 (k)
17699
None
1538 (l)
Any
None
MIN
ON
Angel SP Handshake (#208)
MIN
ON
1793
release board location
test board location l r 20
test board location l
test board location l r 3
1 of 2
448 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
ANN-BD (Announcement circuit pack)
Table 117: Announcement circuit pack error log entries 2 of 2
Error
Type
Aux
Data
Associated test
17680
inline Error
2049
(m) (n)
Clock Match Inquiry (#212)
17674
Alarm
Level (See
WRN
message)
On/off
Board
Recommended action
MIN
ON
test board location r 3
inline Error
2305
140AY Looparound (#210)
MIN
ON
test board location r 3
2561
Super Frame Match Inquiry (211)
MIN
ON
test board location r 3
MIN
ON
test board location r 3
17676
2817
(m)
inline Error
Announcement Checksum (#209)
17682
inline Error
17699
inline Error
3840 (j)
Any
None
3999 (o)
Any
None
2 of 2
!
WARNING:
WARNING:
All ANN-BD alarms are upgraded to MAJOR when the BASE Tone Generator is
set to 12 (France).
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: the circuit pack totally stopped functioning or it was physically removed from
the system.
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 RIGHT LED in SERVICES jack - GREEN: lights
up seventh then turns off..
Note:
Note:
The alarm is logged about 11 minutes after the circuit pack has been removed
and/or SAKI Test (#53) fails.
Issue 3 February 2007
449
Communication Manager Maintenance Object Repair Procedures
!
WARNING:
WARNING:
Reseating and/or replacing the circuit pack results in loss of integrated
announcements (TN750/B only). See General notes on page 444 near the
beginning of this Maintenance procedure.
c. Error Type 2: Check the Class of Restriction (COR) administered for the Data Line
extension assigned to the TN750 for uploading and downloading announcements. The
extension can be found by using list data-module.
d. Error Type 14: logged when the Announcement Checksum Test (#209) fails. The Aux Data
indicates the number of the first defective announcement found. This number corresponds
to the announcement numbers on the announcement form. The extension relating to the
announcement can be determined by display announcement. This error only appears
in the Error Log in conjunction with Error Type 2817. Follow the procedures for Error Type
2817 to troubleshoot Error Type 14.
e. Error Type 23: the circuit pack has been logically administered but not physically installed.
The alarm is cleared when the circuit pack is installed.
f. Error Type 125: the wrong circuit pack is inserted in the slot where this circuit pack is
logically administered. To resolve this problem, either remove the wrong circuit pack and
insert the logically administered circuit pack OR use change circuit-pack to
re-administer this slot to match the circuit pack inserted.
g. Error Type 217 and 267: there is more than one TN750 Announcement circuit pack
inserted in the system. Remove the alarmed circuit pack.
h. Error Type 257: transient communication problems with this circuit pack. This error is not
service-affecting and no action is required.
i. Error Type 513: when reported with Aux Data in the range of 4352 to 4358, the circuit pack
has reported a hardware failure on the circuit pack. The circuit pack should be replaced.
Replacing the circuit pack results in loss of integrated announcements (TN750/B only). See
General notes on page 444 near the beginning of this Maintenance procedure.
j. Error Types 1025 and 3840: not service-affecting, no action is required.
k. Error Type 1281: the speech processor (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 (m)], which causes the maintenance system to
run the Announcement Checksum Test (#209) to determine if the bad memory location was
being used by an announcement.
l. Error Type 1538: the hyperactive circuit pack is out-of-service and may exhibit one or more
of the following symptoms:
1. The tests run on the ports of this circuit pack are returning with a NO-BOARD.
2. A busyout/release of the circuit pack has no effect on test results.
3. A list configuration command shows that the circuit pack and ports are properly
installed.
450 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
ANN-BD (Announcement circuit pack)
The system tries to restore the circuit pack within 15 minutes. If the error recurs after 15
minutes, replace the circuit pack. (Refer to Reseating and replacing server circuit packs in
Maintenance Procedures for Avaya Communication Manager 4.0, Media Gateways and
Servers, 03-300432.)
Note:
m. Error Types 2049 and 2817: logged in conjunction with Error Type 1281, Aux Data 17699.
Because Error Type 1281 means that a defective speech memory location was found, [see
Note (k)] the announcement checksum error is also logged. This causes the Announcement
Checksum Test (#209) to run, which determines if the defective memory location has
corrupted any recorded announcements. If the Checksum Test passes, the faulty memory
location is currently not being used, and the SP marks the location as faulty to ensure that
future announcements do not attempt to use it.
Note:
As memory locations are marked faulty, the amount of available memory
decreases, which decreases the total amount of announcement time available on
the circuit pack.
n. Error Type 2049: transient error that does not cause an alarm can occasionally occur
during a SPE, TDM BUS, or Tone Clock interchange. It is possible for a marginal
Tone-Clock circuit pack to cause this error against the ANN-BD without alarming the
TONE-BD. If this error occurs again, replacing the Tone-Clock circuit pack may clear up this
error. See the FAIL case in the Clock Match Inquiry Test (#212).
o. Error type 3999: 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, then the circuit pack
was taken out-of-service due to hyperactivity. If error type 1538 is not present, then the
circuit pack has not been taken out-of-service, but it has generated 50% of the messages
necessary to be considered hyperactive. This may be completely normal during heavy
traffic periods. However, if this error type is logged when the circuit pack is being lightly
used, it may indicate a problem with the circuit pack or the equipment attached to it.
Demand test descriptions and error codes
Investigate tests in the order presented. By clearing errors associated with the first test, errors
generated from other tests may also be cleared. Click on the link to see the full description of
the test, error codes, and recommended actions.
Long Test
Sequence
D/ND1
Control Channel Looparound Test (#52)
X
ND
Angel Speech Processor Handshake Test (#208)
X
ND
Order of investigation
Short Test
Sequence
Clock Match Inquiry Test (#212)
X
X
ND
Super Frame Match Inquiry Test (#211)
X
X
ND
Issue 3 February 2007
451
Communication Manager Maintenance Object Repair Procedures
Short Test
Sequence
Long Test
Sequence
D/ND1
140AY Looparound Test (#210)
X
X
ND
Announcement Checksum Test (#209)
X
X
ND
X
ND
Order of investigation
NPE Audit Test (#50)
1. D = Destructive, ND = Nondestructive
452 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
ANN-PT (Announcement Port)
ANN-PT (Announcement Port)
MO Name in Log
Alarm Level
Initial command to run
Full name of MO
ANN-PT
MIN
WRN
test port location l
Announcement Port
The TN750 Announcement circuit pack is a service circuit pack that provides an integrated
means for recording announcements that can be played back on demand by call processing as
part of a calling feature (that is, announcements on hunt group calls). There are 16
Announcement Ports on the Announcement circuit pack. Each port can play any integrated
announcement, independently of the other ports. If there are any errors associated with the
circuit pack, refer to ANN-BD (Announcement circuit pack).
The Announcement circuit pack has two processors on it. The first processor, or Angel, controls
the circuit pack, and communicates with the switch via the control channel on the TDM Bus. The
second processor, or SP, controls the speech memory and announcements. Digital speech is
converted from its TDM Bus form to an internal storage form (for recording) and vice versa (for
playbacks) by the 140AY device on the circuit pack, which has 16 channels (one for each
Announcement Port).
See ANN-BD (Announcement circuit pack) for general notes that apply to problems on the
TN750 Announcement circuit pack.
Note:
●
There is no memory card in the system.
●
The memory card in the system does not have a valid announcement file saved on it.
Note:
Unlike translations, there is no provision in the system for automatically saving
announcements to the memory card.
Issue 3 February 2007
453
Communication Manager Maintenance Object Repair Procedures
Error log entries and recommended actions
Table 118: ANN-PT Error Log Entries
Error
Type
Aux
Data
Associated test
Alarm
Level
On/Off
Board
Recommended action
0 (a)
0
Any
Any
Any
test port location
Playback Speech
Memory Array
(PSMA) Test (#206)
MIN
ON
test port location r 3
The port was busied
out
WRN
OFF
release port location
130 (b)
None
WRN
ON
test port location
257
Channel
Administration
Memory Array
(CAMA) Test (#205)
MINOR
ON
test port location l r 3
MINOR
ON
test port location r 3
1
18
0
17667
513
140AY Channel
Sanity Inquiry Test
(#222)
17684
769 (c)
inline error
inline error
None
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 130: 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.
c. Error Type 769 is logged and the port is alarmed when an alarm is raised on the
Announcement circuit pack because of a faulty condition with a common circuit pack
resource. Any one of the following alarmed errors on the Announcement circuit pack causes
this error to be logged against the Announcement Port: 1793, 2049, 2305, 2561. Follow the
ANN-BD (Announcement circuit pack) maintenance documentation to resolve these alarms.
When the corresponding circuit pack alarm is cleared, this alarm clears.
454 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
ANN-PT (Announcement Port)
Demand test descriptions and error codes
Investigate tests in the order presented. By clearing errors associated with the first test, errors
generated from other tests may also be cleared. Click on the link to see the full description of
the test, error codes, and recommended actions.
Order of investigation
Short test
sequence
Channel Administration Memory Array Test (#205)
Long test
sequence
D/ND1
X
ND
Playback Speech Memory Array Test (#206)
X
X
ND
140AY Channel Sanity Inquiry Test (#222)
X
X
ND
1. D = Destructive; ND = Nondestructive
Issue 3 February 2007
455
Communication Manager Maintenance Object Repair Procedures
ANNOUNCE (Announcement)
MO Name in Log
Alarm Level
Initial command to run
Full name of MO
ANNOUNCE
none
none
ANNOUNCEMENT
The ANNOUNCE MO logs an error in the error log if save announcements or restore
announcements does not complete successfully, or the system fails to restore announcements
from the memory card at boot time.
Error Log Entries
Table 119: ANNOUNCE error log entries
Error Type
Aux Data
Associated Test
1 (a) (d)
any
None
257 (d)
any
None
513 (b) (d)
0
None
769 (d)
0
None
1025 (c) (d)
any
None
Alarm
Level
On/Off
Board
Recommended
Action
Notes:
a. Error Type 1: occurred while saving announcements. See Table 120: Aux data error codes
and recommended repair procedures on page 457.
b. Error Type 513: User pressed cancel while announcements were being saved.
c. Error Type 1025: Error occurred while restoring announcements. See Table 120: Aux data
error codes and recommended repair procedures on page 457.
d. Error Types 1, 257, 513, 769, 1025: The port field for this error contained the active PE
complex when the error occurred.
456 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
ANNOUNCE (Announcement)
Aux data error codes and recommended repair procedures
Table 120: Aux data error codes and recommended repair procedures 1 of 2
Aux data
Description/ Recommendation
32001
Internal system error.
1. Check other ANNOUNCE errors and take corrective action. If there are no
other ANNOUNCE errors, do the following:
2. Retry the command at 2-minute intervals a maximum of 3 times.
3. If restore announcements fails, escalate the problem.
32002
Announcement circuit pack is in use.
1. Retry the command at 2-minute intervals a maximum of three times.
2. If restore announcements fails, escalate the problem.
32003
Announcement port is in use.
1. Wait for all Announcement ports to become available.
2. Enter save/restore announcements.
32004
There are no announcements recorded on the Announcement Circuit Pack. Save
announcements does not prevent the destroying of the announcement file on
tape [286 systems] or on the memory card [386 systems].
32005
Integrated announcement circuit pack is not present. The Announcement Circuit
Pack is not inserted, or it is defective.
1. Enter list config to check for the presence of the circuit pack in the
system.
2. If the Announcement Circuit Pack is present, use test board PCSS to
check the status of the Announcement Circuit Pack.
32006
Announcement Data Module not available.
1. Enter status to check the status of the Announcement Data Module.
32007
Announcement Data Module out of service.
1. Enter status to check the status of the Announcement Data Module.
32008
Announcement data is being saved or loaded.
1. Retry the command at 2-minute intervals a maximum of three times.
2. If save/restore announcements fails, escalate the problem.
1 of 2
Issue 3 February 2007
457
Communication Manager Maintenance Object Repair Procedures
Table 120: Aux data error codes and recommended repair procedures 2 of 2
Aux data
Description/ Recommendation
32012
Required Announcement Data Module is not administered.
1. Add an Announcement Data Module and repeat the command.
32015
Time of day not set.
1. Set the time of day, and reenter save/restore announcements.
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. Retry the command at 2-minute intervals a maximum of three times.
2. If save/restore announcements fails, escalate the problem.
2 of 2
458 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
ASAI-ADJ (ASAI Adjunct)
ASAI-ADJ (ASAI Adjunct)
See BRI-SET, Various Adjuncts.
Issue 3 February 2007
459
Communication Manager Maintenance Object Repair Procedures
ASAI-BD (Multi-Application Platform Board)
MO Name in Log
Alarm Level
Initial Command to Run
Full Name of MO
ASAI-BD
MIN
WRN
test board location
ASAI-BD
Maintenance testing of the common circuit pack is handled by on-board firmware and
server-controlled tests. Maintenance software queries the firmware for error and alarm
information, status, and test results. Firmware automatically reports error conditions that result
in server-controlled testing.
For MAPD board insertion, the switch makes an additional board query if any of the following
circuit packs are inserted:
Circuit Pack
Vintage
TN754
49
TN556
49,
80 or
greater
TN800
any
For any of the previous initial board uplinks, the switch queries the board for administration data
as well as reporting the switch software release and the system type.
For the native mode, the response to the board query downlink messages consists of several
CCMS uplink messages that identify the true board code, vintage, suffix, emulation type, and
number of reserved slots needed.
Note:
Note:
Refer to LAN-BD Maintenance documentation for circuit pack level errors. See
also ASAI-PT (ASAI Port) on page 469 and ASAI-EPT (ASAI Endpoint) on
page 462 for related line information. See the following exceptions listed below:
●
●
Hyperactivity: Currently, the common circuit pack is considered “hyperactive” if the
Service Dispatcher receives 200 uplink messages from the circuit pack in a 10-second
period. Since MAPD has 32 ports, the hyperactivity limit increases to 500 uplink
messages per 10 seconds. The switch issues an alarm when the limit reaches 400; when
it reaches 500 up-link messages in 10 seconds, the board is taken out of service.
LED use: The LED Control message 038x requests the Angel to drive the red, amber,
and green LEDs on the face plate of a typical port board on or off. Only the MAPD’s red
LED is controlled by this message. Yellow and green change requests the MAPD
receives from the switch drive LCD behavior rather than LED behavior. The system
460 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
ASAI-BD (Multi-Application Platform Board)
continues to send the same LED control messages to the MAPD that the system
currently sends to every other port board. The MAPD handles proper interpretation of
these messages. You should note that the PC on the MAPD and the switch itself control
the LEDs and the LCD on the MAPD.
●
Port Administration: In Administration Without Hardware (AWOH), the switch allows
administration of up to 8 ports in any of the first 12 ports. If the port type later reported by
the board does not match the existing type, the switch assumes it to be a MAPD board
with a different configuration and rejects the board.
Issue 3 February 2007
461
Communication Manager Maintenance Object Repair Procedures
ASAI-EPT (ASAI Endpoint)
MO Name in Log
Alarm Level
Initial Command to Run
Full Name of MO
ASAI-EPT
MAJ1
test station extension
ASAI-Adjunct
1. The alarm level for ASAI adjuncts is administered using set options. The alarm level can be set
independently for on- and off-board alarms to WARNING, MINOR, or MAJOR for every ASAI
adjunct in the system.
The maintenance strategy for this endpoint MO is built on maintenance facilities offered in the
Avaya ISDN-BRI protocol and in the ASAI adjuncts. Currently there are no facilities in the
protocol that provide for maintenance of set data features.
The TN800 is a PC-based platform that allows interaction of multiple applications with
Communication Manager at any time. Communication Manager (native mode) supports
emulation of three types of port MOs on this board. The type of ports to be emulated is defined
by the applications running on the TN800.
Note:
Note:
If the TN800 is emulating BRI, the software/firmware supports up to 12 ports, but
only 8 of the 12 ports can be administered at any one time.
Error log entries and recommended actions
Table 121: ASAI-EPT Error Log Entries 1 of 2
Error
Type
Aux
Data
Associated Test
Alarm
Level
ASAI-EPT
On/ Off
Board
Recommended action
0 (a)
0
Any
Any
Any
test ASAI-ADJ
2 (b)
2-102
None
257 (c)
Any
BRI Layer 3 query
MAJ
WRN1
OFF
test station ext r 2
test data-module ext r 2
351 (d)
0
none
WRN
OFF
busyout and release station
513 (e)
0
None
769 (f)
0
None
MAJ
OFF
25622566 (g)
0
None
2567 (h)
0
None
1 of 2
462 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
ASAI-EPT (ASAI Endpoint)
Table 121: ASAI-EPT Error Log Entries 2 of 2
Error
Type
Aux
Data
Associated Test
2568 (i)
0
None
3329 (j)
Any
Signaling Link status (#626)
35843839 (k)
Any
None
3841 (l)
4095
Any
None
Alarm
Level
ASAI-EPT
On/ Off
Board
MAJ
WRN†
OFF
Recommended action
2 of 2
1. Major alarms on this MO may be downgraded to Warning alarms based on the value used in set options.
Notes:
a. Error Type 0: Run the short test sequence first. If every test passes, run the long test
sequence. Refer to each appropriate test’s description, and follow its recommended
procedures.
b. Error Type 2: ISDN-BRI signaling protocol violation. Timers associated with layer-3
messages expired before a required response was received. In the following table, the aux
data column indicates which timer has just expired.
Aux Data
Timer Type
2
First T303 (SETUP timer)
3
Second T303 (SETUP timer)
4
T305 (DISConnect timer)
5
First T308 (RELease timer)
6
Second T308 (RELease timer)
10
T316 (RESTart timer)
12
T309 (Layer-2 Failure timer)
16
TM100 (Management Information message Timer 1)
17
TM200 (Management Information message Timer 2)
102
TASAI (ASAI Routing Timer)
The switch sent a message to an endpoint that did not respond in the time allowed. This
may be due to failure of the point-to-point signaling link or because of a problem in the ASAI
Issue 3 February 2007
463
Communication Manager Maintenance Object Repair Procedures
adjunct. To repair, enter test station extension and perform the associated repair
procedures for those tests.
c. Error Type 257: An endpoint is not responding to the service state query message sent to
the adjunct or to the endpoint. This error causes an alarm to be raised. The alarm is retired
when the switch receives a response to the service state query to the endpoint or to the
adjunct.
When this error occurs for an ASAI adjunct, the Aux Data field indicates the state of the
ASAI link and whether an invalid response or no response was received to the query from
the switch, as shown in the following table:
Aux
Data
ASAI Link State
Error
102
13-restarting
No response to RESTART message
104
13-restarting
Invalid response to RESTART message
152
13-restarted
No response to layer-3 query
154
13-restarted
Invalid response to layer-3 query
202
13-established
No response to layer-3 query
204
13-established
Invalid response to layer-3 query
See Maintenance SAT Commands in Maintenance Commands for Avaya Communication
Manager 4.0, Media Gateways and Servers, 03-300431 for an explanation of the ASAI link
states.
For ASAI or Avaya adjuncts, the switch queries the adjunct every two minutes. The Layer 3
Query test is not executed for ASAI or Avaya adjuncts through a command entered from the
management terminal. While alarmed for this error, the switch takes the associated port
out-of-service for five seconds every 15 minutes. This action attempts to stimulate recovery
actions to be taken by the adjunct.
When this error occurs for an ASAI or Avaya adjunct, the service technician should:
1. Execute test station extension and perform the associated repair procedures.
2. Check the health of the adjunct by following the recommended repair procedures of the
manufacturer of the adjunct if the preceding step does not resolve the problem.
d. Error Type 351: logged against an ASAI endpoint when the adjunct asks the switch to
suspend maintenance on the ASAI endpoint. Clear with busyout and release of the ASAI
station.
e. Error Type 513: the endpoint sent more messages than the switch could handle. The
switch suspends the reception of messages from the endpoint for a short period of time.
There is no repair procedure for this error. If the condition persists, replace the endpoint.
464 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
ASAI-EPT (ASAI Endpoint)
f. Error Type 769: an ASAI endpoint’s associated signaling link has too much traffic related to
link establishment. This occurs when the signaling link is alternating between assigned and
established states. If this problem persists, replace the endpoint.
g. Error Type 2562 - 2566: the ASAI message is not transmitted because the transmit buffer
for the ASAI link is full, causing the link to be flow-controlled. Frequent or persistent
occurrence of these events may indicate a hardware problem or traffic overload on the
signaling link or the ASAI adjunct. Follow the repair procedures issued by the manufacturer
of the adjunct. If these attempts fail, re-engineering of the traffic on the signaling link or
adjunct may be necessary.
h. Error Type 2567: This version of ASAI is not supported. Check the software version that is
running on the ASAI adjunct.
i. Error Type 2568: The adjunct identification is invalid. Check the vendor ID or software
running on the ASAI adjunct.
j. Error Type 3329: the point-to-point signaling link to the endpoint went down, except when
the link goes down because either a system technician has busied out the PKT-BUS, or it
has failed. This error raises an alarm against the endpoint or adjunct. Execute test
station extension short and note the results of the Signaling Link Status Test (#626).
If this test fails, follow the repair procedure for Signaling Link Status Test (#626). The alarm
is retired when the signaling link is re-established to the endpoint or adjunct.
k. Error Type 3584 - 3839: The switch software logs certain ASAI cause values. The cause
value is determined from the following formulas:
- If the error type is greater than 3712, then the ASAI cause value is equal to the error type
minus 3712. The switch sent this value to the adjunct.
- If the error type is less than 3712, then the ASAI cause value is equal to the error type
minus 3584. The adjunct sent this value to the switch.
Table 122: ASAI cause values on page 466 contains a description of the various ASAI
cause values and recommended system technician actions associated with the cause
value.
l. Error Type 3841 - 4095: The switch software logs certain ASAI cause values. The cause
value is determined from the following formula:
- If the error type is greater than 3968, then the ASAI cause value is equal to the error type
minus 3968. The switch sent this value to the endpoint.
- If the error type is less than 3968, then the ASAI cause code is equal to the error type
minus 3840. The endpoint sent this value to the switch.
Issue 3 February 2007
465
Communication Manager Maintenance Object Repair Procedures
Table 122: ASAI cause values 1 of 2
Code
Explanation
Recommendation
0
Unrecognized
ASAI Protocol
Operation.
Requested ASAI protocol is not implemented by switch or adjunct.
Aux Data field of error log entry contains protocol identifier for
unrecognized operation.
1. Consult switch and adjunct documentation to determine which
set of operations is supported by switch and the adjunct. Turning
off adjunct operations not implemented by the switch may
resolve the problem.
34
No circuit or
channel
available
A resource on the switch is unavailable for a call. For BRI endpoints,
this cause value is not logged. For ASAI, this condition means that
there are no available trunks for an outgoing call request.
1. Verify that the adjunct is administered to support the trunk
capabilities of the switch.
2. Investigate trunk-group status by issuing status trunk from
the SAT or by requesting trunk-group queries from the adjunct.
3. Perform trunk diagnostic procedures such as test trunk.
40
Resources
not available.
No available internal resources to service switch or adjunct request.
Exceeds system transaction capacity for adjunct or switch.
1. May require re-engineering of adjunct services.
50
Requested
facility not
subscribed
Requested facility is implemented, but not administered. Potential
administration problem with endpoint or adjunct.
For BRI endpoints:
1. Verify the switch administration of endpoint using display
station or display data-module.
2. If step 1 does not resolve the problem, refer to the endpoint’s
service manual and verify administration on the endpoint.
For ASAI adjuncts:
1. Display the Customer Optional Features screen (administration
screen) on the switch to determine which ASAI capabilities are
turned on in the switch.
2. Verify that the adjunct is administered to support the identical
capabilities as the switch. If there is a mismatch in the
administered capabilities, then re-administer the switch and/or
the adjunct to establish a consistent set of desired capabilities
on both the switch and the adjunct.
1 of 2
466 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
ASAI-EPT (ASAI Endpoint)
Table 122: ASAI cause values 2 of 2
Code
Explanation
Recommendation
58
Bearer
capability not
currently
available
Requested bearer capability is implemented, but not administered.
No B-channel is administered. See code 50 above.
63
Service or
option not
available
Requested ASAI capability or resource is not available on the switch
or adjunct. More than one adjunct may be contending for the same
switch resource. Potential administration mismatch between the
resource domains administered on the switch and those
administered on the adjunct.
1. Verify that no overlapping administration of switch resources (for
example, requesting notifications on a single domain by multiple
adjuncts attempting to control a single call) exists across any
adjunct connected to the switch. If an overlap exists, then
re-administer the adjuncts to ensure that each adjunct is
associated with a unique set of switch resources.
65
Bearer
service not
implemented
Requested service not implemented in switch or endpoint.
69
Requested
facility not
implemented
Requested service not supported in switch or endpoint.
Service or
option not
implemented
Requested service or option (or combination of selected options) is
not supported (implemented) in switch or the adjunct.
Invalid CRV
An invalid CRV was sent by the adjunct.
79
81
1. Consult switch and endpoint documentation to determine
service support.
1. Consult switch and adjunct documentation to determine ASAI
service and options supported by both switch and adjunct.
Re-administration of the switch-administered capabilities (see
Customer Optional Feature screen) or those of the adjunct may
be necessary to correct the problem.
1. This may indicate a CRV inconsistency between the switch and
the adjunct. See the CallVisor protocol reference manual.
87
Internal switch
audit
There is an inconsistency in switch data records.
1. There is no action needed, since the switch has corrected the
data inconsistency.
2 of 2
Issue 3 February 2007
467
Communication Manager Maintenance Object Repair Procedures
Demand test descriptions and error codes
Order of Investigation
Signaling Link Status Test (#626)
Short Test
Sequence
Long Test
Sequence
X
X
D/ND
Nondestructive
468 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
ASAI-PT (ASAI Port)
ASAI-PT (ASAI Port)
MO Name in Log
Alarm Level
Initial Command to Run
Full Name of MO
ASAI-PT
MAJ1,2
WRN
test port location l
ASAI ISDN BRI port
1. The alarm level for ASAI adjunct ports may be administered using set options. The alarm level can
be set independently for on- and off-board alarms to WARNING, MINOR, or MAJOR for every ASAI
adjunct port in the system.
2. All alarming for an ASAI adjunct and off-board alarming for an ASAI port is disabled if the ASAI
adjunct asks the switch to suspend maintenance. When this occurs, an error and a WARNING alarm
is logged against the ASAI adjunct. Check the Hardware Error and Alarm Logs to see if the adjunct
has disabled alarming.
Unless otherwise stated, every maintenance action contained in this section applies to ASAI-PT
and ISDN-BRI ports connected to ASAI adjuncts. This port type is administered as an ASAI-BD
on the TN800 circuit pack.
The TN800 circuit pack is a PC-based platform that allows interaction of multiple applications
with Avaya™ Communication Manager. Communication Manager software (native mode)
supports emulation of three types of port MOs on this board. The type of ports to be emulated
are defined by the applications running on the TN800. The TN800 can support up to 32 ports
(time slots) at a time.
The TN800 connects to the switch through a single slot in the backplane, however its width is
not limited to one slot. The number of slots occupied by the TN800 is supplied by the board
during its insertion. The TN800 (Release 5 and higher) is three slots wide. The blank (reserve)
slots are to the left of the functional slot.
In non-native mode the TN800 is recognized as TN556, TN2181, TN754, or TN746 based on
the switch software and the application running on the TN800. In non-native mode only one type
of port MO runs at any time, and the port type depends on the application running on the
TN800. If the TN800 fails diagnostics in non-native mode, the system’s alarm and error logs
would show a failure for the board type the TN800 is emulating.
Issue 3 February 2007
469
Communication Manager Maintenance Object Repair Procedures
Error log entries and recommended actions
Table 123: ASAI-PT Error Log Entries
Error
Type
Aux
Data
Associated
Test
Alarm Level
On/Off
Board
Recommended Action
0 (a)
0
Any
Any
Any
test port location
1 (b)
(a)
Level 1 Status
Inquiry (#621)
MAJ1
OFF
test port location r 2
513 (c)
0
none
MAJ
ON
1537 (d)
46210
CRC Error
Counter (#623)
MAJ1
OFF
3841 (e)
46208
None
3844 (f)
46223
None
3845 (g)
46211
None
3846 (h)
TEI
None
1. Major and Minor alarms may be downgraded to warning alarms based on the value used in set options.
Notes:
a. Error Type 0: Run the short test sequence first. If every test passes, run the long test
sequence. Refer to each appropriate test’s description, and follow its recommended
procedures.
b. Error Type 1: Level 1 Status inquiry fails or when the BRI circuit pack detects that Level 1
has been deactivated on the port. The Aux Data field contains one of the following values:
Blank
This indicates that the Level 1 Status inquiry failed.
32773
This is a message from the ASAI-Line circuit pack indicating Level 1 has been
deactivated.
Refer to the repair procedures for Level 1 Status Inquiry Test (#621) If the alarm does not
clear, verify the status of the PC/server. This could be a customer network issue and not a
board problem.
470 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
ASAI-PT (ASAI Port)
c. Error Type 513: The circuit pack is having problems transmitting data to the packet bus,
thus affecting the conveyance of signaling information over the D channel. This error occurs
when the packet bus transmit FIFO buffer overflows. This condition probably indicates a
hardware problem as well. The ASAI-PORT alarm level is MAJOR with aux data 0. Use
troubleshooting procedures for both on-board hardware problems and potential off-board
packet-bus problems.
d. Error Type 1537: The port received an invalid frame over the D channel. When the cyclical
redundancy check (CRC) errors exceed 5 within 15 minutes, the port is taken out of service
for 5 seconds. If 5 more CRC errors are received within 15 minutes of the first set of 5
errors, the port is taken out of service for one minute. If 5 more CRC errors are received
within 15 minutes of the last 5, the port is taken out of service for 15 minutes.
This error is most likely due to a problem with the wiring to the set or adjunct, interference
on the wiring due to a noise source, or no termination (an open circuit). It usually does not
indicate a problem with the circuit pack.
●
Check the wiring to the endpoints or the adjunct.
●
If the problem persists, replace the endpoints or adjuncts.
e. Error Type 3841: a Layer 1 Transmission error is detected for the port. Run the long test
sequence, and note the results of the Layer 1 Transmission Error Counter Test (#624).
f. Error Type 3844: the circuit pack detects an overflow of its receive buffers. Run the long
test sequence, and note the results of the Receive FIFO Error Counter Test (#625).
g. Error Type 3845: the BRI Port Local LAN Looparound Test (#618) fails. Run the long test
sequence, and note the results of Test #618.
h. Error Type 3846: the TEI (Terminal Endpoint Identifier) administered for the ASAI endpoint
most likely does not match the TEI administered in the ASAI adjunct. Check the switch
administration of the TEI against that of the adjunct, and make sure that both are using the
same TEI.
Demand test descriptions and error codes
Investigate tests in the order presented. By clearing errors associated with the first test, errors
generated from other tests may also be cleared. Click on the link to see the full description of
the test, error codes, and recommended actions.
Order of Investigation
Short Test
Sequence
BRI Port Local LAN Looparound Test (#618)
Level 1 Status Inquiry Test (#621)
CRC Error Counter Test (#623)
X
Long Test
Sequence
D/ND1
X
D
X
ND
X
ND
Issue 3 February 2007
471
Communication Manager Maintenance Object Repair Procedures
Long Test
Sequence
D/ND1
Layer 1 Transmission Error Counter Test (#624)
X
ND
Receive FIFO Error Counter Test (#625)
X
ND
X
ND
Order of Investigation
Clear Error Counters (#270)
Short Test
Sequence
X
1. D = Destructive, ND = Nondestructive
472 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
ASAI-RES (TN800 reserve slot)
ASAI-RES (TN800 reserve slot)
MO Name in Log
Alarm
Level
Initial Command to Run
Full Name of MO
ASAI-RES
NONE
NONE
TN800 ASAI reserve slot
DIG-RES
NONE
NONE
TN800 DIG reserve slot
Error log entries and tests also apply to DIG-RES.
There are no tests associated with these MOs. Both the test board and busyout board
commands abort when either is attempted on a reserved slot. An error message indicates the
slot is associated with the circuit pack that the TN800 is emulating, but the requested operation
is not valid.
The TN800 MAPD (Multi-Application Platform) circuit pack connects to the switch through a
single slot in the backplane. The number of slots occupied by the MAPD pack is supplied by the
board when inserted. The TN800 in R5EM is three slots wide. The TN800 requires 2 reserve
slots to its left. The reserve (blank) slots are to left of the functional slot and are place holders on
the switch, and do not have any interaction with the switch.
Each instance of these MOs represents a reserve slot associated with respective circuit pack
mode in which the MAPD is working.
Issue 3 February 2007
473
Communication Manager Maintenance Object Repair Procedures
ATM-BCH (ATM B-Channel Trunk)
MO Name in Log
Alarm Level
Initial Command to Run
Full Name of MO
ATM-BCH
MAJ1
MIN
test port location l
ATM B-Channel Trunk
WRN
test port location
1. A MAJOR alarm on a trunk means that alarms on these trunks are not downgraded by set options, and at
least 75% of the trunks in this trunk group are alarmed.
ATM-BCH explains how to test and repair TN230x ATM Interface circuit packs (TN2305 and
TN2306) that have ATM B-channel trunks administered for ATM Circuit Emulation Service
(CES).
For additional repair information, see also, ATM-SGRP (ATM Signaling Group) on page 527 and
PKT-BUS (Packet Bus) on page 1065.
For maintenance instructions for TN230x circuit packs that are administered as Expansion
Interfaces for ATM network connectivity, see ATM-INTF (ATM Interface) on page 503.
ATM Circuit Emulation Service
Under ATM Circuit Emulation Service, you simulate ISDN-PRI circuits by assigning ATM ports
to signaling groups. Each signaling group represents a PRI circuit, and the ports in the group
represent the D channel and B-channels of that circuit. B-channels must also be assigned to
ISDN-PRI trunk groups. TN230x circuit packs support up to 248 ports per circuit pack.
Signaling Group Components
B (bearer) channels (ATM-BCH) transmit digitized voice or data, while a separate D-channel
(ATM-DCH) handles call-control signaling. One D-channel handles signaling for a group of
B-channels that combine to form a signaling group (ATM-SGRP).
474 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
ATM-BCH (ATM B-Channel Trunk)
B-Channel Service States
The ISDN specification defines two service state categories for B-channels as listed in
Table 124: ATM ISDN service states on page 475.
Table 124: ATM ISDN service states
Category
Description
Service states
In-Service (INS)
B-channel is in normal
operating state
Active
A call is connected over
the B-channel.
Idle
There is no call on the
B channel.
Out-of-Service/
Far-End (OOS/FE)
The switch has not successfully negotiated B-channel connection as
of yet. Calls cannot be placed or received.
When you first administer a B-channel, the switch initializes the
B channel to this state while it tries to negotiate a connection to the far
end. If the request times out with no response from the far end, the
switch leaves the B-channel in the OOS/FE state.
Out-of-Service/
Near-End (OOS/NE)
The NPE Crosstalk test has failed, or the trunk is busied out. Calls
cannot be placed or received.
Maintenance/
Far-End (MTC/FE)
A request has timed out with no response from the far end after
signaling is in place and B-channels are in service. Calls can be
received but not placed, and stable calls are unaffected.
Maintenance/
Near-End (MTC/NE)
The signaling channel (ISDN-LNK) has been busied out, possibly after
test trunk grp#/mem# long. Calls cannot be placed or received,
but stable calls are unaffected.
Pending states
The switch is waiting for a reply from the far end. Pending service
states remain in effect until the near end receives a response or times
out.
Pending-in-Service
The near end is waiting for a response to a transition-to-service
request.
PendingMaintenance
The near end is waiting for a transition-to-maintenance-service
request (US and other country-protocol-1 systems).
Issue 3 February 2007
475
Communication Manager Maintenance Object Repair Procedures
B-Channel Alarms
The Maintenance/Far-End and Out-Of-Service/Far-End states generate warning alarms
displayed with status trunk grp#/mem#.
Table 125: ATM-BCH alarms by service state
Service state
Alarm1
Possible cause
Possible solution
Out-of-Service/NE
WRN
Trunk busied out
Release the port (release trunk
grp#/mem#).
MIN
NPE Crosstalk test
(#6) failed
Replace ATM circuit pack.
None
ATM circuit pack
lost signal or there
is a circuit pack
problem.
Install circuit pack or cable. Check circuit
pack using procedures in ATM-BCH.
Check far-end switch status.
WRN
Unadministered far
end
Administer the corresponding trunk on
the far-end switch.
WRN
Far-end busied out
Check the status of the far-end switch.
None
Maintenance
message timed out
waiting for reply
Wait 2 minutes after the pending state
clears, and check the service state.
None
ISDN test call in
progress (test
trunk long)
Wait for the test to finish and recheck.
None
System link busied
out
Check link status. Run release link
link#.
WRN
Signaling channel
down for over 90
sec.
See ATM-SGRP (ATM Signaling
Group) on page 527 or ATM-DCH (ATM
D-Channel Port) on page 481.
WRN
Repeated lack of
response to
messages sent to
the far end
Wait. Maintenance software resends
messages periodically. Or run test
trunk grp#/mem# or test
signaling-grp grp#.
WRN
The far-end trunk
is being tested.
Check status of the far-end switch. Wait
for testing to finish.
None
Normal operating
state
Out-of-Service/FE
Pending/
In-Service
Pending/Maint
Maint/NE
Maint/FE
In-Service
1. ATM-BCH alarms; alarms against other MOs may also be present.
476 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
ATM-BCH (ATM B-Channel Trunk)
Error log entries and recommended actions
Table 126: ATM-BCH Error Log entries
Error
Type
Aux
Data
Associated Test
Alarm
Level
On/Off
Board
Recommended Action
0 (a)
0
Any
Any
Any
test port location
1(b)
Any
None
test port location
18
0
busyout trunk grp/
mbr
release trunk grp/mbr
None
129 (c)
WRN
OFF
130 (d)
test port location
test port location
257(e)
Any
Service State Audit test
(#256)
513(f)
Any
None
769(g)
Any
Service State Audit test
(#256)
test port location
1793
(h)
Any
None
test port location
3073(i)
Any
Service State Audit test
(#256)
test port location
3585(j)
Any
None
none
3841
(k)
Any
None
test port location
WRN
WRN
OFF
OFF
test port location
none
Notes:
a. Error Type 0: Run the short test sequence first. If every test passes, run the long test
sequence. Refer to each appropriate test’s description, and follow its recommended
procedures.
b. Error Type 1: the two ends of the ATM trunk do not agree on the ISDN call state. Possible
causes:
●
●
Received a DISConnect or RELease COMplete message with cause value 52 (outgoing
calls barred)
Received a DISConnect or RELease COMplete message with cause value 54 (incoming
calls barred)
Issue 3 February 2007
477
Communication Manager Maintenance Object Repair Procedures
●
●
Outgoing call renegotiated by the far end to another B-channel in the absence of SETUP
message glare
Near end attempted a call on a B-channel that the far end has marked OOS
When running the short test sequence, pay close attention to the results of the Call State
Audit Test (#257).
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.
1. Investigate the trunk’s status (status trunk grp#/mem#).
d. Error Type 130: the circuit pack has been removed or has been insane for more than 11
minutes.
1. Reinsert or replace the circuit pack to clear the error.
e. Error Type 257: SETUP received for a B-channel that is in an invalid service state. Service
states may be incompatible at the two ends of the trunk. A normal call was received while
the B-channel was MTC/FE, MTC/NE, OOS/FE, or OOS/NE or a test call was received
while the B channel was OOS/FE or OOS/NE.
f. Error Type 513: RELease COMplete message received with cause value 82 (nonexistent
channel). The B-channel may not be administered at the far end. The trunk has been placed
in the OOS/FE state.
g. Error Type 769: inconsistent SERVice or SERVice ACKnowledge message. Possible
causes:
●
●
SERVice or SERVice ACKnowledge message received containing a change status that
is more available than the previously-transmitted SERVice message.
Unsolicited SERVice ACKnowledge message received containing a change status that
does not match the current B-channel state.
ISDN-PRI service-state negotiation rules have been violated and may indicate that a
pending service-state audit is failing. The system:
●
cancels the maintenance timer
●
increments the Service State Audit counter
●
attempts a Service State Audit
When running the short test sequence, pay close attention to the results of the Service State
Audit Test (#256).
h. Error Type 1793: TN230x circuit pack failed. The maintenance system
●
●
●
places the trunk in the OOS/NE state
sends a SERvice message to the far end (if possible) containing a change status of OOS
for the B-channel
returns the trunk to service when the ATM trunk circuit pack reports the failure cleared
478 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
ATM-BCH (ATM B-Channel Trunk)
i. Error Type 3073: Service State Audit attempt failed. See Service State Audit Test (#256).
Calls can be received but not placed until the test passes and the trunk state returns to
In-Service.
1. Check the trunk’s status (status trunk grp#/mem#).
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.
Aux Data
Description
0
An idle trunk received a restart.
10
An ISDN RESTART from the far end has unexpectedly cleared a call in the
ACTIVE state (call stable, parties talking).
4
7
8
260
263
An ISDN RESTART from the far end has unexpectedly cleared a RINGING call.
1
3
6
9
265
An ISDN RESTART from the far end has unexpectedly cleared a call before the
call entered the RINGING state.
11
12
19
531
267
268
An ISDN RESTART from the far end has unexpectedly cleared a call that was
already in the process of clearing.
If this condition occurs frequently, the far end may be trying to clear trunks that
appear to be in the “hung” state.
k. Error Type 3841: the far end rejected an ATM CES trunk selected by the near end 10 times.
The ATM CES trunk may not be administered on the far end.
1. Get the physical name of the ATM trunk by noting the decimal number in the Aux Data
field.
2. Check administration for the named trunk on the far end.
3. If problems persist, then busyout the ATM trunk to take it out of the hunt group.
The WARNING alarm retires automatically whenever a called endpoint answers an
outgoing or incoming call that uses the alarmed trunk.
Issue 3 February 2007
479
Communication Manager Maintenance Object Repair Procedures
Demand test descriptions and error codes
Investigate tests in the order presented. By clearing errors associated with the first test, errors
generated from other tests may also be cleared. Click on the link to see the full description of
the test, error codes, and recommended actions.
Short Test
Sequence
Long Test
Sequence
D/ND1
Signaling Link State Audit Test (#255)
X
X
ND
Service State Audit Test (#256)
X
X
ND
Call State Audit Test (#257)
X
X
ND
X
ND
Order of Investigation
ISDN Test Call Test (#258)
1. D = Destructive, ND = Nondestructive
480 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
ATM-DCH (ATM D-Channel Port)
ATM-DCH (ATM D-Channel Port)
MO Name in Log
Alarm Level
Initial Command to Run
Full Name of MO
ATM-DCH
MIN
test port location l
ATM D-Channel
WRN
test port location
Note:
TN2305 and TN2306 circuit packs are not interchangeable. Always replace an
ATM circuit pack with the same type.
Note:
ATM-DCH uses the existing ISDN-PLK or D-channel maintenance strategy with modifications.
The ATM circuit pack can be administered for up to 8 Circuit Emulation Service (CES) or
signaling groups, each with its own D channel, as opposed to one D channel for an entire DS1
circuit pack.
Note:
Due to the dual personalities and the number of D channels that the ATM board
can possess, the inline errors and signaling port LAN loopback test have been
moved to ATM-TRK (Circuit Emulation Service Circuit Pack) on page 541. When
an inline error is sent due to packet-bus errors, the ATM circuit pack receives the
error, not ATM-DCH.
Note:
The D-channel ISDN-PRI interface is emulated for ATM-CES and uses out-of-band signaling to
transmit control messages between two endpoints. User information or bearer channels
(B-channels) carry digitized voice and digital data and are assigned to DS1 ISDN trunks or PRI
endpoints. Call-control signaling for the B-channels is combined and carried over the separate
ISDN-PRI Signaling Link port D channel.
Problems with ATM-DCH affects every associated B-channel, since call-control signaling
cannot reach the far-end switch or terminal adapter. Stable calls can remain operational, but no
new calls can be made. In turn, ATM-DCH depends on the:
●
TN230X ATM Trunk circuit pack where it resides
●
Packet bus that provides the link to the processor
When working ATM-DCH alarms or errors, also investigate
●
ATM-TRK (Circuit Emulation Service Circuit Pack) on page 541
●
PKT-BUS (Packet Bus) on page 1065
Issue 3 February 2007
481
Communication Manager Maintenance Object Repair Procedures
Error log entries and recommended actions
Table 127: ATM-DCH Error Log entries
Error
Type
Aux
Data
Associated Test
Alarm
Level
On/Off
Board
Recommended Action
0 (a)
0
Any
Any
Any
test port location
18 (b)
0
busyout port
location
WRN
OFF
release port location
130 (c)
None
WRN
ON
test port location
1793 (d)
Signaling Link Board
check (#643)
test board location l
Notes:
a. Error Type 0: Run the short test sequence first. If every test passes, run the long test
sequence. Refer to each appropriate test’s description, and follow its recommended
procedures.
b. Error Type 18: D channel busied out; no calls possible over this D channel.
c. Error Type 130: circuit pack removed or has been insane for more than 11 minutes. To
clear the error, reinsert or replace the circuit pack.
d. Error Type 1793: ATM Trunk circuit pack failed the Signaling Link Board check (#643).
Resolve any ATM-TRK errors in the Error Log.
Demand test descriptions and error codes
The command to test the ATM-DCH MO is test port location, where location is port
number 9-32.
Order of Investigation
Signaling Link Board Check (#643)
Short Test
Sequence
X
Long Test
Sequence
X
D/ND
Nondestructive
482 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
ATM-EI (Expansion Interface Circuit Pack)
ATM-EI (Expansion Interface Circuit Pack)
MO Name in Log
Alarm Level
Initial Command to Run
Full Name of MO
ATM-EI
MAJ
MIN
WRN
test board location
ATM Expansion
Interface circuit pack
ATM-EI covers the ATM circuit pack administered as an Expansion Interface (ATM-EI) for ATM
Port-Network Connectivity (ATM PNC). The ATM-EI monitors port network connectivity between
a server and every PN through the ATM switch.
The circuit packs listed in Table 128: ATM-EI circuit packs on page 483 are ATM-EI boards if
they are administered to support ATM Port Network Connectivity (ATM PNC).
Table 128: ATM-EI circuit packs
Note:
Note:
Circuit pack
Fiber
Echo cancellation
TN2305
Multimode
Y
TN2306
Single mode
Y
Note:
TN230x circuit packs are not interchangeable. Always replace an ATM circuit
pack with the same type.
Note:
ATM switch maintenance is not covered in this section. When maintenance
software suspects the ATM switch connections, it raises appropriate
Communication Manager alarms. To clear any ATM switch faults, refer to the
particular ATM switch’s documentation.
Issue 3 February 2007
483
Communication Manager Maintenance Object Repair Procedures
LEDs
The ATM Interface circuit pack has three LEDs:
●
Red indicates some alarm condition.
●
Green indicates maintenance testing in progress.
●
Amber provides useful visual information regarding the operating mode of the ATM-EI and
possible error conditions.
The possible LED states are described in Table 129.
Table 129: ATM Interface LED codes
LED
LED Status
Condition
Red
Steady on
Board is not healthy
Not on
Normal conditions
Red
and
Green
Red LED solid on
Green LED 200 msec on; 200 msec off
Board is in the processes of booting
Green
Steady on1
Maintenance is running tests on the
board
100 msec on - 100 msec off
No links to the board
Amber
100 msec on -100 msec off
Board has loss of signal alarms - Fiber
Loss of Signal (LOS), LOF, MS_RDI,
MS_AIS, LCD, HP_RDI, HP_AIS, LOP,
PSC
Amber
500 msec on; 500 msec off
Signal to the ATM switch is down
Amber
2 sec on; 0.2 sec off
ATM-EI is Expansion Archangel (EAA)
Amber
Steady on
ATM-EI active (Center Stage Switch PN)
Amber
Not on
ATM-EI standby
1. The green LED flashes between tests.
484 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
ATM-EI (Expansion Interface Circuit Pack)
ATM-EI-Related Commands
The following commands can be helpful in resolving ATM-EI problems:
add atm pnc
list measurements atm
busyout/release atm pnc
remove atm pnc
busyout/release board
reset board
change atm pnc (pnc duplication)
status atm pnc
display atm pnc
status cabinet
list atm oam-statistics
status port-network
list atm pnc
test board
Replacing an ATM-EI Circuit Pack
Standard Reliability
1. Enter busyout atm pn# (this is service-affecting) at the SAT.
2. Replace the ATM PNC circuit pack, and reconnect the fiber.
3. Enter release atm pnc.
4. Wait 2½ minutes for board insertion.
5. Enter list sys-link to verify that the links are up.
6. Enter test board location, and verify that every test passes.
Duplex or High Reliability
There is 1 ATM-EI circuit pack in each PN.
1. Enter busyout atm pnc # at the SAT.
Note:
Note:
If the ATM-EI is in a PN, this is service-affecting.
2. Replace the circuit pack.
3. Enter release atm pnc.
4. Wait 2½ minutes for board insertion.
5. Enter list sys-link to verify that the links are up.
6. Enter test board location, and verify that every test passes.
Issue 3 February 2007
485
Communication Manager Maintenance Object Repair Procedures
Critical Reliability
There are 2 ATM-EI circuit packs in each PN.
1. Enter status pnc at the SAT. If the board is on the active side, enter reset pnc
interchange to switch the active ATM-EI board to the standby side.
2. Enter busyout pnc-standby.
3. Enter busyout atm pnc # a-pnc or b-pnc.
4. Replace the circuit pack.
5. Enter release atm pnc #.
6. Enter release pnc-standby.
7. Wait 2½ minutes for board insertion.
8. Enter test board location, and verify that every test passes.
Basic ATM PNC Administration
Note:
This section contains basic administration information only. Refer to ATM
Installation, Upgrades, and Administration using Avaya Communication Manager,
555-233-124, for more detailed information.
Note:
ATM PNC connections involve administering
●
1 ATM-EI board in each PN (standard, duplex, or high reliability)
●
2 ATM-EI boards in each PN (critical reliability)
Adding ATM PNC Connections
Standard, Duplex or High Reliability
1. If the ATM-EI circuit pack is absent or if the circuit pack is present but in a PN, use the
change circuit-pack command to add circuit pack translations.
2. Enter add atm pnc n (connection number), and administer the circuit pack’s location and
its ATM address.
Critical Reliability
1. Enter change system-parameters duplication, and change the Enable Operation
of PNC Duplication field to n.
2. If the ATM-EI circuit pack is absent or is present but in a PN that does not yet have PNC
connectivity to it, use the change circuit-pack command to add circuit pack translation
for the missing circuit pack.
486 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
ATM-EI (Expansion Interface Circuit Pack)
3. Enter add atm pnc n (connection number), and administer the circuit pack location and
ATM address.
4. Enter change system-parameters duplication, and change the Enable Operation
of PNC Duplication field to y.
Removing ATM PNC Connections
Standard, Duplex or High Reliability
Note:
Note:
These systems are not equipped with PNC duplication.
1. Enter busyout atm pnc n (connection number).
2. Enter remove atm pnc n (connection number).
Critical Reliability
1. Enter status pnc, and ensure that the A-PNC is active.
If not, request a PNC interchange using the reset pnc interchange command.
2. Enter busyout pnc-standby.
3. Enter change system-parameters duplication, and change the Enable Operation
of PNC Duplication field to n.
4. Enter busyout atm pnc n (PN’s number).
5. Enter remove atm pnc n (PN’s number) to remove both ATM-EI boards, or enter change
atm pnc to remove the B-side ATM-EI board.
6. Enter change system-parameters duplication, and change the Enable Operation
of PNC Duplication field to y.
Changing Circuit Pack Location or ATM Address
Standard, Duplex or High Reliability
Note:
Note:
These systems are not equipped with PNC duplication.
1. Remove the ATM PNC connection (see Removing ATM PNC Connections on page 487).
2. Add an ATM PNC connection (see Adding ATM PNC Connections on page 486).
A-side ATM-EI—Critical Reliability
1. Remove the ATM PNC connection (see Removing ATM PNC Connections on page 487).
2. Add an ATM PNC connection (see Adding ATM PNC Connections on page 486).
Issue 3 February 2007
487
Communication Manager Maintenance Object Repair Procedures
B-side ATM-EI—Critical Reliability
1. Enter status pnc, and ensure that the A-PNC is active.
If not, request a pnc interchange using reset pnc interchange.
2. Enter busyout pnc-standby.
3. Enter list config carrier, and verify that an ATM circuit pack is assigned for the new
location. If not, add the ATM circuit pack’s translations.
4. Enter busyout atm pnc n (connection number) b-pnc.
5. Enter change atm pnc n (connection number) and change circuit pack location for the B
side.
6. Enter release pnc-standby.
Changing ATM Address of Standby
ATM PNC EI, Critical Reliability
1. Enter busy pnc-standby.
2. Enter change atm pnc n (connection number), and change the ATM address for the
standby side.
3. Enter release pnc-standby.
Error log entries and recommended actions
Table 130: ATM-EI Error Log Entries 1 of 3
Error
Type
Aux
Data
Associated Test
Alarm
Level
On/Off
Board
Recommended Action
0 (a)
0
Any
Any
Any
test board location
None
MIN
ON
2 (b)
18 (c)
0
busyout board
location
WRN
OFF
23 (d)
0
None
WRN
OFF
125 (e)
None
MIN
ON
131 (f)
None
MIN
ON
Expansion Interface
Control Channel test
(#316)
MAJ
ON
257-259
(g)
Any
release board location
test board location r 2
1 of 3
488 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
ATM-EI (Expansion Interface Circuit Pack)
Table 130: ATM-EI Error Log Entries 2 of 3
Error
Type
Aux
Data
Associated Test
Alarm
Level
On/Off
Board
Recommended Action
513 (h)
Any
ATM Crosstalk test
(#1298)
MIN
ON
test board long
location
769 (i)
34
35
ATM Board Error
Query (1259)
WRN
OFF
test board location
770 (i)
25
ATM Board Error
Query (#1259)
WRN
OFF
test board location
771 (i)
26
ATM Board Error
Query (#1259)
WRN
OFF
test board location
1024–
1151 (j)
Any
None
WRN
MIN
ON
test board location
1153 (k)
None
WRN
ON
test board location
1281 (l)
ATM Board Error
Query (1259)
MAJ
OFF
test board location
1537
(m)
12
None
MIN
ON
1538 (n)
0
None
MIN
ON
1793 (o)
13
None
MIN
ON
test board location
2049 (p)
15
None
MIN
OFF
test board location r 4
2050 (p)
Expansion Interface
Lock Query (#304)
MIN
OFF
test board location r 4
2305 (q)
None
MIN
ON
2309 (q)
Packet interface test
(#598)
MIN
ON
test board location r 2
2561 (r)
Expansion Interface
2-way Transmission
test (#241)
MAJ
OFF
test board location r 3
2817 (s)
Any
ATM Board DSP test
(#1293)
MIN
ON
test board location
2818 (s)
Any
None
MIN
ON
test board location
3329 (t)
3
LANHO critical error
MAJ
OFF
2 of 3
Issue 3 February 2007
489
Communication Manager Maintenance Object Repair Procedures
Table 130: ATM-EI Error Log Entries 3 of 3
Error
Type
Aux
Data
Associated Test
Alarm
Level
On/Off
Board
Recommended Action
3585 (u)
ATM Framer
Looparound (#1260)
MAJ
ON
test board location l
3586 (u)
ATM Framer
Looparound (#1260)
MAJ
ON
test board location l
3841 (v)
3842(w)
None
3843 (x)
3999 (y)
Any
None
Any (z)
32767
None
3 of 3
Notes:
a. Error Type 0: Run the short test sequence first. If every test passes, run the long test
sequence. Refer to each appropriate test’s description, and follow its recommended
procedures.
b. Error Type 2: The on-board DUART chip failed. This results in communication failure
between the PN’s Maintenance board and the ATM-EI board. The Maintenance board
should have a red LED lit because the link to the ATM-EI is down in this PN.
1. Reset the board with reset board location.
2. If the board does not recover, replace the board.
c. Error Type 18: The ATM-EI circuit pack has been busied out.
1. Release the circuit pack (release board location).
d. Error Type 23: An ATM-EI circuit pack has been administered with the add atm pnc n
command, but the circuit pack has not been physically inserted into the system.
1. Insert an ATM-EI circuit pack at this location.
e. Error Type 125: A wrong circuit pack is located in the slot where the ATM-EI circuit pack is
logically administered.
1. Either remove the wrong circuit pack and insert the ATM-EI circuit pack or remove the
ATM-EI administration (see Basic ATM PNC Administration on page 486).
2. Remove the ATM-INTF administration and re-administer the slot (change circuit-pack) to
match the circuit-pack that is physically present in this slot.
490 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
ATM-EI (Expansion Interface Circuit Pack)
f. Error Type 131: An ATM-EI circuit pack has been removed from the slot for 5 minutes.
1. Insert the ATM-EI circuit pack into its administered slot.
2. Another way to resolve or prevent this alarm is to remove the ATM-EI administration (see
Basic ATM PNC Administration on page 486), then remove the ATM-INTF administration
(change circuit-pack).
It is possible that the ATM-EI could be held in reset by the PN’s Maintenance board and is
not inserted in the system.
3. Try issuing test maint P long on the maintenance board in the same PN.
g. Error Type 257: Expansion Interface Control Channel Test (#316) failed (board cannot
communicate on the TDM bus control channel). Follow the suggested test procedures.
Error Type 258: The archangel is out of sequence (Aux Data indicates angel number).
Error type 259: The expansion archangel link (EAL) to the active ATM-EI board is down.
See SYS-LINK (System Links) on page 1262.
h. Error Type 513: The ATM Crosstalk test failed. The board is either writing to or reading
from a TDM time slot that is not allocated to the board.
1. Test the board (test board location), and follow the procedures suggested for this
test. In random tests of a single DSP during low or high traffic, the same DSP can be
tested more than once.
i. Error Types 769 and 770: are board-degraded alarm errors that result when the ATM
switch is sending corrupted cells or excessive AAL/LAPD retransmissions (off-board ATM
cell corruption errors). These errors indicate the detection of a problem in handling ATM
cells that are received from the fiber interface.
Aux Data for these Error Types:
Error Type
Aux Data
Description
769
34
Excessive AAL-5 retransmission requests
769
35
Excessive LAPD retransmission requests
770
25
Uncorrectable ATM cell headers – threshold
771
26
VPI, VCI pair unknown
The problem is most likely not on the ATM-EI circuit pack reporting the errors, but it could be
due to one or more of the following reasons:
●
●
●
The fiber is not snugly connected to either the board or the ATM switch.
The PN’s packet bus is corrupting the cells. See PKT-BUS (Packet Bus) on page 1065
(Aux Data 35 only).
The fiber between the ATM switch and the ATM-EI is too long (greater than 2 km for
multimode fiber). Use loopback to see if the fiber is corrupting the cells.
Issue 3 February 2007
491
Communication Manager Maintenance Object Repair Procedures
●
●
Some other ATM-EI board is not receiving the cells properly.
The intervening ATM switch is dropping the ATM cells due to a shortage of bandwidth, or
the server is using more than the subscribed bandwidth.
Error Type 771: The ATM switch is sending cells with unknown VPI and VCI address
(wrong connection).
1. Ensure that the address translations are correct.
j. Error Types 1024-1151: These errors represent problems detected by the ATM-EI board in
response to SETUP and ADDPARTY requests from software.
●
●
The Error Types and descriptions are in Table 131: ATM Error Types 1024 - 1151 on
page 492.
Aux Data values represent PN and angel numbers and are in Table 132: Error Type
1024-1151 Converted Aux Data Values on page 494.
Table 131: ATM Error Types 1024 - 1151 1 of 3
Error
Type
Description
General problem
1024
Next node unreachable
1056
DTL Transit not my node ID
ATM protocol stack on
ATM-EI3 circuit pack
1 of 3
492 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
ATM-EI (Expansion Interface Circuit Pack)
Table 131: ATM Error Types 1024 - 1151 2 of 3
Error
Type
Description
General problem
1088
1104
ATM-EI circuit pack received a request with an
invalid connection identifier.
1089
1105
ATM-EI circuit pack received a request with a
reference to an unknown VC token.
1090
1106
ATM-EI circuit pack did not have enough
resources (memory) for the requested operation.
1091
1107
Internal failure in the local protocol stack. This can
occur when the connection to the ATM switch
failed, perhaps because the:
Firmware-detected problems
on the ATM-EI circuit pack.
Note: Error Types 1088–1103
are reported by the board that
is originating the connection.
Error Types 1104–1119 are
reported by the board that is
terminating the connection. In
most cases, when the
terminating board reports one
of these errors, the originating
board also reports an
ATM-NTWK error for the same
event (usually with Error Type
21).
●
●
ATM switch rebooted
fiber between the ATM switch and the
ATM-EI circuit pack disconnected
1092
1108
ATM-EI circuit pack received a request for which
the referenced VC was in the wrong call state.
1093
1109
ATM-EI circuit pack received a request for which
the VPI/VCI pair was invalid or out of range.
1094
1110
ATM-EI circuit pack received a request to add a
party to an existing VC. The add party request
failed, and a retry was not possible.
1095
1111
ATM-EI circuit pack in link recovery after the lower
ATM layer (Q.SAAL portion of the protocol stack)
failed. This can occur when the connection to the
ATM switch failed, perhaps because the:
● ATM switch rebooted
● fiber between the ATM switch and the
ATM-EI circuit pack disconnected
1096
1112
ATM-EI circuit pack received an error from the
local protocol stack for which no more detailed
cause was specified.
1102
ATM-EI circuit pack asked to create more
connections that it was capable of creating.
1103
ATM-EI circuit pack detected an illegal message
from software.
Check the Error Log for CONN-M errors for more
information.
2 of 3
Issue 3 February 2007
493
Communication Manager Maintenance Object Repair Procedures
Table 131: ATM Error Types 1024 - 1151 3 of 3
Error
Type
Description
General problem
1113
Problems detected by the
board terminating the
connection
3 of 3
1. Test the ATM-EI circuit pack (test board location) and investigate further based on
each test’s results. If every test passes, the error was a transient problem.
Aux Data values: For Setup and Add Party connection request failure type, the port-network
and the angel number of the destination ATM-EI circuit pack are logged Aux Data values in
the form XXYYY, where
●
port-network number = XX
●
angel number = YYY
Since you need to know the slot number also, Table 132: Error Type 1024-1151 Converted
Aux Data Values converts the Aux Data to slot numbers.
Table 132: Error Type 1024-1151 Converted Aux Data Values 1 of 2
Slot
Carrier
A
B
C
D
E
Failure type
Failure type
Failure type
Failure type
Failure type
Slot #
Set
up
Add
Party
Set
up
Add
Party
Set
up
Add
Party
Set
up
Add
Party
Set
up
Add
Party
1
28
528
66
566
98
598
34
534
02
502
2
29
529
67
567
99
599
35
535
03
503
3
30
530
68
568
100
600
36
536
04
504
4
31
531
69
569
101
601
37
537
05
505
5
56
556
70
570
102
602
38
538
06
506
6
57
557
71
571
103
603
39
539
07
507
7
58
558
72
572
104
604
40
540
08
508
8
59
559
73
573
105
605
41
541
09
509
9
60
560
74
574
106
606
42
542
10
510
1 of 2
494 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
ATM-EI (Expansion Interface Circuit Pack)
Table 132: Error Type 1024-1151 Converted Aux Data Values 2 of 2
Slot
Carrier
A
B
C
D
E
Failure type
Failure type
Failure type
Failure type
Failure type
Slot #
Set
up
Add
Party
Set
up
Add
Party
Set
up
Add
Party
Set
up
Add
Party
Set
up
Add
Party
10
61
561
75
575
107
607
43
543
11
511
11
62
562
76
576
108
608
44
544
12
512
12
63
563
77
577
109
609
45
545
13
513
13
88
588
78
578
110
610
46
546
14
514
14
89
589
79
579
111
611
47
547
15
515
15
90
590
80
580
112
612
48
548
16
516
16
91
591
81
581
113
613
49
549
17
517
17
92
592
82
582
114
614
50
550
18
518
18
93
593
83
583
115
615
51
551
19
519
19
94
594
84
584
116
616
52
552
20
520
20
95
595
85
585
117
617
53
553
21
521
21
NA
NA
86
586
118
618
54
554
22
522
22
NA
NA
87
587
119
619
55
555
23
523
2 of 2
k. Error type 1153: The ATM connection audit found some discrepancy in the firmware’s VC
token numbers and live VCs. The problem is rectified in firmware and no action is needed.
This is an indication of an event only.
l. Error Type 1281: The ATM circuit pack cannot talk to the ATM switch. The loss of high-level
signal error indicates operational problems of equipment located outside of the circuit pack
and the fiber connected to the board. Aux Data values are listed in Table 133: Error type
1281 Aux Data and repair procedures on page 496.
Issue 3 February 2007
495
Communication Manager Maintenance Object Repair Procedures
Table 133: Error type 1281 Aux Data and repair procedures 1 of 3
Aux
Data
Alarm
Description
Repair procedure
15
SYSCLOCK
failed
The board is not locked to the TDM backplane clock signal. This is
probably due to a Tone-Clock problem.
1. Check for TDM-BUS or TONE-BD errors in the Error Log.
2. If no other problems are present, reset the circuit pack (reset
board location)
16
Loss of Signal:
LOS
The fiber is not connected properly to the ATM-EI board or ATM
switch (or to the multiplexer section [MUX] if present).It is possible
that the board transceivers are not functioning properly.
1. Run test board location.
2. If Test #1259 fails, connect a fiber back-to-back in a looped
mode (one strand of fiber connecting the transmit transceiver to
the receive transceiver of the board) and see if the amber LED
flash goes away. If it does, the problem is off-board.
3. If the amber LED continues to flash, replace the circuit pack.
17
Loss of Frame:
LOF
The fiber signal cannot obtain or maintain STM-1/OC-3 framing.
1. Try to move the fiber on the ATM switch side to a different port.
This could require administration on the ATM switch.
2. If the problem persists, reset the circuit pack (reset board
location).
18
Multiplexer
Section Alarm
Indication
Signal:
MS_AIS
There is a major problem on the far end (between multiplexer
section [MUX] and the switch) that prohibits the circuit pack from
sending a valid signal.
1. See if the ports at the MUX and/or the ATM switch are
connected snugly.
2. Run test board location.
3. If Test #1259 fails with Error Code 18, connect a fiber
back-to-back in a looped mode (one strand of fiber connecting
the transmit transceiver to the receive transceiver of the board)
and see if the amber LED flash goes away.
4. If it does, the problem is off-board.
5. If the amber LED continues to flash, replace the circuit pack; if
the error persists, escalate the problem.
1 of 3
496 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
ATM-EI (Expansion Interface Circuit Pack)
Table 133: Error type 1281 Aux Data and repair procedures 2 of 3
Aux
Data
Alarm
Description
Repair procedure
19
Multiplexer
Section
Remote Defect
Indicator:
MS_RDI
The far end is detecting a major problem with the signal that this
board is transmitting.
1. Make sure the ATM switch port (or a MUX port, if present
between ATM switch and the ATM-EI board) is the same as the
ATM-EI circuit pack’s cable interface.
2. Run test board location.
3. If Test #1259 fails with Error Code 19, connect a fiber
back-to-back in a looped mode (one strand of fiber connecting
the transmit transceiver to the receive transceiver of the board)
and see if the amber LED flash goes away.
4. If it does the problem is off-board.
5. If the amber LED continues to flash, replace the circuit pack; if
the error persists, escalate the problem.
20
Loss of pointer:
LOP
ATM framer chip is unable to access the payload part of the signal.
1. Reset the board (reset board location).
2. If the error persists replace the board.
21
Path Signal
Error (PSL)
(STM1/
SONET)
The incoming signal payload is not set up for transmission of ATM
data.
1. Make sure the ATM switch port (or a MUX port, if present
between ATM switch and the ATM-EI board) is the same as the
ATM-EI circuit pack’s cable interface.
22
High-level Path
Alarm
Indication
Signal:
HP_AIS
The payload is invalid.
1. Make sure the ATM switch port (or a MUX port, if present
between ATM switch and the ATM-EI board) is the same as the
ATM-EI circuit pack’s cable interface.
2. Run test board location.
3. If Test #1259 fails with Error Code 22, connect a fiber
back-to-back in a looped mode (one strand of fiber connecting
the transmit transceiver to the receive transceiver of the board)
and see if the amber LED flash goes away.
4. If it does the problem is off-board.
5. If the amber LED continues to flash, replace the circuit pack.
2 of 3
Issue 3 February 2007
497
Communication Manager Maintenance Object Repair Procedures
Table 133: Error type 1281 Aux Data and repair procedures 3 of 3
Aux
Data
Alarm
Description
Repair procedure
23
High-level path
Remote defect
Indicator:
HP_RDI
The far end is detecting a major problem with the signal that this
board is transmitting. The transmitted payload is invalid.
1. Make sure the ATM switch port (or a MUX port, if present
between ATM switch and the ATM-EI board) is the same as the
ATM-EI circuit pack’s cable interface.
2. Run test board location. If the Test #1259 fails with Error
Code 23, connect a fiber back-to-back in a looped mode (one
strand of fiber connecting the transmit transceiver to the
receive transceiver of the board) and see if the amber LED
flash goes away.
3. If it does, the problem is off-board.
4. If the amber LED continues to flash, replace the circuit pack.
24
Loss of cell
delineation
(LCD)
On board ATM framer chip is not able to frame cells based on the
cell header.
1. Reset the board (reset board location).
2. If the error persists, replace the board.
27
SIGCON_DO
WN ATM
switch high
level signal
The board cannot communicate with the ATM switch.
1. Busyout the board (busyout board location).
2. Test the board (test board long location).
3. If Test #1260 fails, replace the board.
4. If Test #1260 passes, make sure the ATM address on both the
server and the ATM switch sides are the same for this board.
5. If the address is the same, change the port on the ATM switch
side. This could require administration on the ATM switch.
6. If the error is resolved, the problem is on the ATM switch port.
3 of 3
m. Error Type 1537: LAN bus time out. The circuit pack is transmitting a packet larger than
1,024 bytes. Replace the circuit pack.
n. Error Type 1538: A hyperactive ATM-EI circuit pack is generating an excessive amount of
control messages to the processor. When this error is generated, the system automatically
resets the ATM-EI.
Duplicated PNC?
Then:
Yes
service to the PN is disrupted
No
the system switches to the standby PNC
1. Enter reset board location for this ATM-EI circuit pack.
2. If the same error persists, replace the ATM-EI circuit pack.
498 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
ATM-EI (Expansion Interface Circuit Pack)
o. Error Type 1793: LANHO transmit FIFO overflow error (the transmit FIFO RAM buffers on
the circuit pack overflowed). This most likely indicates a hardware problem on the circuit
pack because the speed of the LAN/packet bus is much higher than the speed of the link
connected to the port.
1. Test the ATM-EI circuit pack (test board location).
2. If Test #598 fails again, replace the ATM-EI circuit pack.
p. Error Types 2049 and 2050: The ATM-EI clock generation is out of lock with the backplane
system clock.
1. Test the ATM-EI circuit pack (test board location).
2. If Test #304 fails, follow the repair procedures suggested for this test.
q. Error Type 2305: Too many parity errors on data received from the LAN/packet bus (could
be due to packet-bus problems).
1. Test the ATM-EI circuit pack (test board location).
2. If Test #598 fails, follow the repair procedures for Packet Interface Test (#598).
3. If the test passes, look for and resolve any PKT-BUS (packet bus) alarms/errors.
4. If there are no PKT-BUS errors and the problem persists, escalate the problem.
Error Type 2309: The packet-interface chip (LANHO) is malfunctioning. Perform the
following steps:
5. Test the ATM-EI circuit pack (test board location).
6. If Test #598 fails, follow the repair procedures for Packet Interface Test (#598).
r. Error Type 2561: ATM-EI 2-way transmission failure (circuit pack is having problems
creating connections to other PNs in the system).
1. Test the ATM-EI circuit pack (test board location).
2. Follow the repair procedures suggested for Expansion Interface 2-Way Transmission
Test (#241).
s. Error Types 2817 and 2818: A bad DSP was detected on the ATM-EI circuit pack.
Error Type
Description
Aux Data indicates
2817
DSP test failure
The Aux Data field contains the following
information about the failed DSPs:
X is the number of talker DSPs
Y is the number of listener DSPs
Z is the number of echo-cancelling DSPs
2818
One or more DSPs failed
DSP number that has failed
1. Test the ATM-EI circuit pack (test board location).
2. Follow the repair procedures suggested for Test #1258.
Issue 3 February 2007
499
Communication Manager Maintenance Object Repair Procedures
t. Error Type 3329: The on-board LANHO chip is insane, possibly due to a problem in
packet-bus arbitration, the transmission line frame, or the circuit pack itself. The circuit pack
cannot talk to the packet bus.
If the packet bus is alarmed:
1. Resolve any PKT-BUS errors. The probability of this error being related to a packet-bus
problem increases with the number of other circuit packs using the bus that are also
showing this error.
If the packet bus is not alarmed:
2. Reset the circuit pack (reset board location).
3. If the problem persists, replace the ATM-EI circuit pack.
If the system has a duplicated PNC, and the inline error received is from an active ATM-EI,
the system switches to the standby PNC.
! CAUTION:
CAUTION:
If the system does not have duplicated PNC, services to the PN could be
disrupted.
u. Error Types 3585 and 3586: Board major component failure. A failure of critical
components involved in the operation of the circuit pack. If the system has a duplicated
PNC and the inline error received is from an active ATM-EI, the system switches to the
standby PNC.
! CAUTION:
CAUTION:
If the system does not have duplicated PNC, services to the PN could be
disrupted.
Error Type 3585
Aux Data (Error Type 3585 only):
Aux Data
Description
1
ATM framer failure
2
NCE failed (only from ATM-EIs in PN)
4
TDM_PLD_FAILED
5
DSP_ALL FAILED
6
Receive Network Processor (RNP) failure
7
Transmit Network Processor (TNP) failure
8
MEMORY read/write failure
500 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
ATM-EI (Expansion Interface Circuit Pack)
1. If the system has duplicated PNC:
a. Test the ATM-EI (test board location l).
b. If Error 3585 is detected again, or if the board is not recognized anymore, replace the
ATM-EI circuit pack.
2. If the system does not have duplicated PNC and the circuit pack is in a PN:
a. Replace the ATM-EI circuit pack.
Error Type 3586: Framer Looparound test (#1260) failed.
Aux Data (Error Code 3586 only):
Aux Data
Description
2
Packet path failed
3
Circuit path failed
4
TDM loop cannot be created
5
Packet loop cannot be created
3. If Error Type 3586 is detected again, replace the circuit pack.
v. Error Type 3841: The board received a message from the switch that it does not recognize,
and the board responded with an inconsistent down link error message. This error does not
affect service, and no action is required.
w. Error Type 3842: The circuit pack received data from the packet bus faster than it could
distribute the data to its endpoint. This circuit pack should be able to recover by itself, and
no action is necessary.
x. Error Type 3843: The firmware on the circuit pack is reporting a resource that is low. This
error does not affect service and no action is required.
y. Error Type 3999: The circuit pack sent a large number of control channel messages to the
switch within a short period of time.
If
Then
Error Type 1538 is also
present
Circuit pack is taken out of service
Error Type 1538 is absent
Circuit pack is not taken out of service, but has generated
50% of the messages necessary to be considered
hyperactive.
This can be normal during heavy traffic.
If the error is logged during light traffic, it can indicate a
problem with the circuit pack or the equipment attached to it.
Issue 3 February 2007
501
Communication Manager Maintenance Object Repair Procedures
z. Aux Data 32767 for any error log entry indicates that an alarmed ATM-EI was busied out
and then released. When this occurs, existing service-affecting alarms must be preserved.
Typically, every alarm is resolved when the ATM-EI is released. Therefore, the Alarm and
Error Logs must be repopulated with the alarms present at time of busyout. This Aux Data
indicates that existing Error Type and Error Log time stamps are no longer valid because
they were lost when the circuit pack was released.
Demand test descriptions and error codes
Investigate tests in the order presented. By clearing errors associated with the first test, errors
generated from other tests may also be cleared. Click on the link to see the full description of
the test, error codes, and recommended actions.
Order of Investigation
Short Test
Sequence
ATM Board Time Of Day Update (#1261)
Long Test
Sequence
Reset
Board
Sequence
X
ND
Expansion Interface Control Channel Test
(#316)
X
X
ND
Packet Interface Test (#598)
X
X
ND
ATM Board DSP Test (#1293)
X
X
ND
Expansion Interface 2-Way Transmission
Test (#241)
X
X
ND
ATM Board Framer Looparound Test (#1260)
X
D
ATM Crosstalk Test (#1298)
X
ND
Expansion Interface Lock Query Test (#304)
X
X
ND
ATM Board Error Query Test (#1259)
X
X
ND
ATM Board Reset (#1256)
X
1. D = Destructive, ND = Nondestructive
Note:
D/
ND1
Note:
To get a better indication of a problem’s location, test both ATM-EI circuit packs
on the associated fiber link, whether the circuit packs are both ATM-EI circuit
packs or not.
502 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
D
ATM-INTF (ATM Interface)
ATM-INTF (ATM Interface)
S8700 Fiber-PNC
MO Name in Log
Alarm Level
Initial Command to Run
Full Name of MO
ATM-INTF
WRN
test board location
ATM interface board
The system recognizes a TN2305/6 as an ATM interface board (ATM-INTF) unless it has an
assigned personality (add atm pnc or add atm trunk). ATM-INTF does not have an
associated maintenance strategy, although the:
●
list config and change circuit-pack display information regarding the board
●
test board runs an on-demand Control Channel test
●
reset board resets the board
Table 134 lists circuit packs that are ATM-EI boards if they are administered to provide ATM
port-network connectivity (ATM PNC).
Table 134: ATM-EI circuit packs for ATM PNC
Note:
Circuit Pack
Fiber
Echo
Cancellation
TN2305
Multimode
Yes
TN2306
Single-mode
Yes
Note:
Always replace an ATM-EI circuit pack with the same type.
Error log entries and recommended actions
Table 135: ATM-INTF Error Log Entries
Error
Type
Aux
Data
Associated Test
Alarm
Level
On/Off
Board
23 (a)
0
None
WRN
Off
None
MINOR
On
None
WRN
Off
125 (b)
217 (c)
0
Recommended
Action
Issue 3 February 2007
503
Communication Manager Maintenance Object Repair Procedures
Notes:
a. Error Type 23: The ATM expansion interface circuit pack is administered through a change
circuit-pack command, but has not been inserted into the system. Insert the circuit
pack.
b. Error Type 125: A wrong circuit pack is located in the slot where this circuit pack is logically
administered. To resolve this problem either remove the wrong circuit pack or insert the
logically-administered circuit pack.
c. Error Type 217: The ATM circuit pack is physically present but has not been given a
personality. Remove the circuit pack or administer it using add atm pnc or add atm
trunk.
Demand test descriptions and error codes
Order of Investigation
Control Channel Looparound Test (#52)
Short Test
Sequence
Long Test
Sequence
X
X
D/ND
Nondestructive
504 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
ATM-NTWK (ATM Network Error)
ATM-NTWK (ATM Network Error)
S8700 Fiber-PNC
MO Name in Log
Physical Name in
Error Log1
Alarm
Level
Full Name of MO
ATM-NTWK
ATUUP
WRN
ATM Network Error
ATM-NTWK
location
WRN
ATM Network Error
1. AT indicates it is an ATM switch-related address, UU is the connection number. The connection
number can be converted into a board location with display atm pnc UU, which shows the
translations for the board that reported the ATM network error. P indicates if the ATM-EI board
(reporting the ATM network error) is on the PNC’s A side or the B side. If the system is simplex, only A
is valid.
In an ATM PNC configuration, a proprietary Center Stage Switch (CSS) is replaced by an ATM
network. Because CSS nodes are replaced by the ATM network in the ATM PNC configuration,
SNI boards are no longer needed. In place of the SNI boards, ATM Expansion Interface (EI) or
ATM Circuit Emulation Service (CES) boards are connected to an ATM switch port over a
fiber-optic cable. The ports on the ATM switch are under control of its maintenance software.
Refer to ATM Installation, Upgrades, and Administration using Avaya Communication Manager,
555-233-124, for more information.
An error against ATM-NTWK indicates a problem in the ATM network (including the ATM
switch) that is affecting service quality. These error events are either:
●
Reported by the ATM network to an ATM EI or ATM CES board
●
Detected by either the ATM EI or ATM CES board itself
Since these errors are not related to the ATM EI or ATM CES board, they are not reported
against the ATM-EI or ATM-TRK MO. However, some of these errors invoke alarms that require
action by the system’s maintenance software, while other log-only errors require no action.
Error Codes and Aux Data values
The Cause Code/Error Type information is shown in Table 136: Error codes and Aux Data
values ATM-NTWK on page 506. These are the possible errors that can be logged against
ATM-NTWK.
Issue 3 February 2007
505
Communication Manager Maintenance Object Repair Procedures
If ATM-NTWK receives more than 6 errors, the most recent are discarded.
Table 136: Error codes and Aux Data values ATM-NTWK 1 of 6
Cause
Code/
Error
Type
Aux
Data
Cause Codes Description
NORMAL EVENTS
0
(a)
Network unreachable
1
(a)
Unallocated (unassigned) number. This cause indicates that the called
party cannot be reached because, although the number is in a valid format,
it is not currently assigned (allocated).
2
(a)
No route to specified transit network. This cause indicates that the
equipment sending this cause has received a request to route the call
through a particular network that it does not recognize, either because the
transit network does not exist or because that particular transit network
does not serve the equipment that is sending this cause. This cause is
supported on a network-dependent basis.
3
(a)
No route to destination. This cause indicates that the called party cannot be
reached because the network through which the call has been routed does
not serve the destination desired. This cause is supported on a
network-dependent basis.
10
(a)
VPCI/VCI unacceptable. This cause indicates that the virtual channel most
recently identified is not acceptable to the sending entity for use in this call.
16
(a)
Normal call clearing. This cause indicates that the call is being cleared
because one of the users involved in the call has requested that the call be
cleared. Under normal situations, the source of this cause is not the
network.
17
(a)
User busy. This cause indicates that the called party is unable to accept
another call because the user busy condition has been encountered. This
cause value can be generated by the called user or by the network.
18
(a)
No user responding. This cause is used when a called party does not
respond to a call establishment message with a connect indication within
the prescribed period of time allocated.
1 of 6
506 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
ATM-NTWK (ATM Network Error)
Table 136: Error codes and Aux Data values ATM-NTWK 2 of 6
Cause
Code/
Error
Type
Aux
Data
Cause Codes Description
21
(a)
Call rejected. This cause indicates that the equipment sending this cause
does not wish to accept this call, although it could have accepted the call
because the equipment sending this cause is neither busy nor
incompatible.
Note: If the call was rejected by the far-end ATM-EI or ATM-CES board,
there could also be additional information about this rejection in an ATM-EI
error log entry. Look for an ATM-EI or error with an Error Type between
1104 and 1119 inclusive, with approximately the same time stamp as this
error.
22
(a)
Number changed. This cause is returned to a calling party when the called
party’s number indicated by the calling user is no longer assigned. The new
called party’s number can optionally be included in the diagnostic field. If a
network does not support this capability, cause number 1 “unassigned
(unallocated) number” is used.
23
(a)
User rejects every call with CLIR (calling line identification restriction). This
cause is returned by the called party when the call is offered without calling
party’s number information and the called party requires this information.
27
(a)
Destination out of order. This cause indicates that a user-indicated
destination cannot be reached because a signaling message could not be
delivered to the remote user over the destination’s interface (for example, a
physical-layer or SAAL failure at the remote user, or remote user’s
equipment is off line).
28
(a)
Invalid number format (address incomplete). This cause indicates that the
called user cannot be reached because the called party’s number is not in a
valid format or has insufficient digits.
30
(a)
Response to STATUS ENQUIRY. This cause is included in the STATUS
message when the reason for generating the STATUS message was the
prior receipt of a STATUS ENQUIRY message.
31
(a)
Normal, unspecified. When no more specific cause values apply, this cause
reports a normal event.
32
(a)
DTL transit not-my-node ID
RESOURCE UNAVAILABLE
35
(a)
Requested VPCI/VCI not available. This cause indicates that the requested
VPCI/VCI is not available. This can be caused by mismatched VCI ranges
on different ATM switches.
36
(a)
VPCI/VCI assignment failure
2 of 6
Issue 3 February 2007
507
Communication Manager Maintenance Object Repair Procedures
Table 136: Error codes and Aux Data values ATM-NTWK 3 of 6
Cause
Code/
Error
Type
Aux
Data
Cause Codes Description
37
(a)
User Cell Rate not available
38
(a)
Network out of order. This cause indicates that the network is not
functioning correctly and that the condition is likely to last a relatively long
time. (Immediately retrying the call is unlikely to succeed.)
41
(a)
Temporary failure. This cause indicates that the network is not functioning
correctly, but the condition is unlikely to last long. (Immediately retrying the
call is likely to succeed.)
43
(a)
Access information discarded. This cause indicates that the network could
not deliver access information to the remote user as requested (that is, ATM
adaptation-layer parameters, Broadband low-layer information, Broadband
high-layer information, or sub-address as indicated in the diagnostic).
45
(a)
No VPCI/VCI available. This cause indicates that no appropriate VPCI/VCI
is currently available to handle the call.
47
(a)
Resource unavailable, unspecified. When no more specific cause values
apply, this cause reports a resource-unavailable event.
SERVICE OR OPTION UNAVAILABLE
49
(a)
Quality of Service unavailable. This cause reports that the requested
Quality of Service cannot be provided.
51
(a)
User cell rate not available. This cause reports that the requested ATM
Traffic Descriptor is unobtainable.
57
(a)
Bearer capability not authorized. This cause indicates that a user-requested
bearer capability is implemented by the cause-sending equipment, but the
user is not authorized to use the capability.
58
(a)
Bearer capability not currently available. This cause indicates that the
user-requested bearer capability is implemented by the cause-sending
equipment, but the capability is currently unavailable.
63
(a)
Service or option not available, unspecified. When no more specific cause
values apply, this cause reports an unavailable service or option event.
65
(a)
Bearer capability not implemented. This cause indicates that its sending
equipment does not support the bearer capability requested.
73
(a)
Unsupported combination of traffic parameters. This cause indicates that
the combination of traffic parameters contained in the ATM traffic descriptor
information element (IE) is not supported.
3 of 6
508 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
ATM-NTWK (ATM Network Error)
Table 136: Error codes and Aux Data values ATM-NTWK 4 of 6
Cause
Code/
Error
Type
Aux
Data
Cause Codes Description
78
(a)
AAL parameters cannot be supported.
INVALID MESSAGES
81
(a)
Invalid call reference value. This cause indicates that its sending equipment
received a message with a call reference that is currently inactive on the
user-network interface.
82
(a)
Identified channel does not exist. This cause indicates that its sending
equipment received a request to use a channel not activated for the call’s
interface.
88
(a)
Incompatible destination. This cause indicates that its sending equipment
received a request to establish a call with either Broadband low-layer
information, Broadband high-layer information, or other compatibility
attributes that cannot be accommodated.
89
(a)
Invalid endpoint reference value. This cause indicates that its sending
equipment has received a message with an endpoint reference that is
currently idle on the user-network interface.
91
(a)
Invalid transit network selection. This cause indicates that a transit network
identification was received in an incorrect format.
92
(a)
Too many pending add-party requests. This cause indicates a temporary
condition when the calling party sends an add-party message, but the
network rejects the message due to full queues.
93
(a)
AAL parameters cannot be supported. This cause indicates that its sending
equipment received a request to establish a call with ATM adaptation-layer
parameters that cannot be accommodated.
PROTOCOL ERROR
96
(a)
Mandatory information element (IE) is missing. This cause indicates its
sending equipment has received a message with a missing IE.
97
(a)
Message type either non-existent or not implemented. This cause indicates
that its sending equipment received a message with an unrecognized type,
either because the type is undefined, or defined but not implemented by the
cause-sending equipment.
4 of 6
Issue 3 February 2007
509
Communication Manager Maintenance Object Repair Procedures
Table 136: Error codes and Aux Data values ATM-NTWK 5 of 6
Cause
Code/
Error
Type
Aux
Data
Cause Codes Description
99
(a)
Information element (IE) either non-existent or not implemented. This cause
indicates that its sending equipment received a message with an
unrecognized IE, either because the IE’s identifier(s) are undefined, or
defined but not implemented by the cause-sending equipment.
This cause indicates that its sending equipment discarded the IE. However,
the equipment could still process the message since this IE was not
required.
100
(a)
Invalid contents in information element (IE). This cause indicates that its
sending equipment received and implemented an IE. However, one or more
of the IE’s fields are coded in a way that the cause-sending equipment has
not implemented.
101
(a)
Message not compatible with call state. This cause indicates receipt of a
message that is incompatible with the call state.
102
(a)
Recovery on timer expiration. This cause indicates that a timer’s expiration
initiated an error-handling procedure.
104
(a)
Incorrect message length
111
(a)
Protocol error, unspecified. When no more specific cause values apply, this
cause reports a protocol-error event.
5 of 6
510 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
ATM-NTWK (ATM Network Error)
Table 136: Error codes and Aux Data values ATM-NTWK 6 of 6
Cause
Code/
Error
Type
Aux
Data
Cause Codes Description
257 to
300 (b)
(b)
ATM Impaired Paths
1. Examine the error log (display errors), atm setup-events log
(list measurements atm svc-setup), and atm pnc-latency
(list measurements atm latency) screens to help diagnose the
problem, although the switch could be operating normally. In this case,
you should consider raising the Activation threshold and/or increasing
the Timeout value on the ATM-RELATED System Parameters screen.
(change system atm).
Enter list measurements atm svc-setup to see information
about errors associated with connection numbers.
2. After entering the above command, note the time stamps shown in the
list measurements atm setup-events screen. Execute the
above command periodically and note the time stamps. If the time
stamps have changed for a particular From Conn-To Conn pair, this
indicates there are still setup failures/delays for that connection.
3. After verifying that every associated ATM endpoint is operating
correctly, and if errors are still occurring, contact your local service
provider.
301 (c)
ANY
System wide ATM Impaired Paths.
See the suggestions listed above to trouble shoot these errors.
769 (d)
ATM CLP (Cell Loss Priority) Bit Errors
1025 (e)
ATM Congestion Bit Errors
1281 (f)
ATM Cell Underrun Errors
1537 (g)
ATM Cell Overrun Errors
1793 (h)
ATM Lost Cells
6 of 6
Issue 3 February 2007
511
Communication Manager Maintenance Object Repair Procedures
Notes:
a. Aux Data values for Setup and Add Party (XX = port network, YYY = location code).
Table 137: Location codes from Aux Data values is a list of UNI 3.1 location codes:
Table 137: Location codes from Aux Data values
Setup
(Location
Code)
Add Party
(Location Code)
Location Code Meaning
0
500
User
1
501
Private network serving the local user
2
502
Public network serving the local user
3
503
Transit network
4
504
Public network serving the remote user
5
505
Private network serving the remote user
7
507
International network
10
510
Network beyond interworking point
b. Error Types 257 to 300: used to determine the destination PNC connection number of an
ATM Network connection that is experiencing an impaired path. The connection number is
obtained by subtracting 256 from the number that is shown in the Error Type field. See the
following example:
If the Error Type field = 263, subtract 256, which equals 7, the PNC destination
connection number.
The Aux Data field contains the originating and destination PN number (XXYY). XX = the
originating PN #, and YY = the destination PN # for example:
1. Aux Data = 302
3 = orig
2 = dest
2. Example Aux Data = 1510
15 = orig
10 = dest
c. Error Type 301 indicates that there is a system wide impaired path network problem.
Note:
Note:
Under certain circumstances network errors can be against the ATM EI board.
512 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
ATM-NTWK (ATM Network Error)
d. Error Type 769: ATM CLP (Cell Loss Priority) Bit Errors
The ATM cell header has a bit called the cell loss priority (CLP) bit. The bit indicates one of
two states: the cell is eligible for discarding, or it is not. In an ATM configuration, every cell is
transmitted into the ATM network with the CLP bit set to 0 indicating that these cells are
NOT eligible for discarding. Should the system ever receive a cell from the ATM network
with the CLP bit set to 1 (discard eligible), an entity in the ATM network modified the bit
during transit. Generally, an ATM network switch sets the CLP bit to 1 (discard eligible) only
if the cell fails to conform to the cell rate specified in the traffic contract for the VC. However,
Communication Manager cell emissions conform with the VC traffic contract. Therefore, the
presence of a non-conforming cell implies that something else in the ATM network switch is
setting the CLP bit in some cells, the ATM switch can also be policing out (discarding) cells
which do not conform to the traffic contract. This error can occur together with other errors
such as:
“Excessive AAL-5 CRC errors” or
“Excessive LAP-D retransmissions”
These errors affect SVCs with Variable Bit Rate (VBRnt) traffic contracts. VBR SVCs
transport system links such as EAL, PACL, and PRI links. Again, this indicates problems
with cell transmissions in the ATM network.
If cell discard is happening generically in the ATM network, other symptoms can affect the
Constant Bit Rate (CBR) SVCs including audible artifacts in talk paths, failure of modems
over voice lines, and “Cell Underruns” - see note (f).
e. Error Type 1025: ATM Congestion Bit Errors
The ATM cell header has a bit called the congestion bit. In Communication Manager ATM,
every cell is transmitted into the ATM network with the congestion bit set to 0 (congestion
not experienced). Should the system ever receive a cell from the ATM network with the
congestion bit set to 1 (congestion experienced), an entity in the ATM network modified the
bit during transit. It simply indicates that the ATM network is experiencing heavy traffic.
During periods of congestion, the ATM network can choose to discard cells even though
those cells conform to their traffic contracts. Should the ATM network discard cells, errors
such as the following can occur:
“Excessive AAL-5 CRC errors”
“Excessive LAP-D retransmissions”.
These errors affect SVCs with Variable Bit Rate (VBRnt) traffic contracts. VBR SVCs
transport system links such as EAL, PACL, and PRI links. Symptoms that can affect the
Constant Bit Rate (CBR) SVCs include audible artifacts in talk paths, failure of modems
over voice lines, and “cell Underruns” – see note (f).
f. Error Type 1281: ATM Cell Underruns
Communication Manager ATM monitors for cell underrun conditions on SVCs with Constant
Bit Rate (CBR) traffic contracts or on ATM CES trunks. In either case, cells are expected to
arrive at a fixed rate. If cells arrive below that rate, an underrun condition exists. The most
likely cause of cell underruns is a problem with cell transmission through the ATM network.
Issue 3 February 2007
513
Communication Manager Maintenance Object Repair Procedures
Possible symptoms include audible artifacts in talk paths and failure of modems over voice
lines. If cell loss is happening generically in the ATM network, other symptoms like
“excessive AAL-5 CRC errors” or “excessive LAP-D retransmissions” are possible on SVCs
with Variable Bit Rate (VBRnt) traffic contracts. The VBR SVCs transport system links such
as EAL, PACL, and PRI links.
Another ATM board within the system originally generated the arriving cells at the specified
traffic contract rate. In order to have arrived at a lower rate, these cells were either slowed
during transmission or possibly discarded by the ATM network. This indicates problems with
cell transmission in the ATM network. Consult the ATM network vendor. Ask about cell delay
variation, cell discard, and traffic policing.
Cell underruns often happen in conjunction with cell overruns. If both occur, it further indicts
the ATM network.
g. Error Type 1537: ATM Cell Overruns
Communication Manager ATM monitors for cell overrun conditions on SVCs with Constant
Bit Rate (CBR) traffic contracts or on ATM CES trunks. In either case, cells are expected to
arrive at a fixed rate. If cells arrive above that rate, an overrun condition exists. The most
likely cause of cell overruns is a problem with cell transmission through the ATM network.
Both cell underruns and overruns are typical symptoms of cell transmission problems like
cell jitter or delay. The ATM board attempts to compensate somewhat by buffering cells.
However, if the ATM network transmission delays are high, the board could conclude that it
has seen a cell overrun because it has exhausted all of its buffer space.
If cell underruns or both cell underruns and overruns occur, indict the ATM network. Consult
the ATM vendor. Ask about cell delay variation, cell discard, and traffic policing.
Another much less likely cause of cell overruns is that an ATM board is generating cells
above the traffic contract rate. Suppose, a board somehow generates cells too quickly. The
ATM network likely reacts by at least setting the CLP bit in the cells that exceed the traffic
contract (see note (d) for ATM CLP errors). The ATM network can also discard the excess
cells.
If only cell overruns occur, locate the ATM board generating those cells. Execute test
board long. If the board passes, then the ATM network remains the likely cause of
transmission problems. Consult the ATM network vendor. Ask about cell delay variation, cell
discard, and traffic policing.
h. Error Type 1793: ATM lost cells:
The ATM board receiving the CBR cell stream is detecting out-of-sequence AAL1 sequence
numbers, above the defined threshold. This normally indicates that the ATM network has
lost the missing cells. In this case, “lost” could mean that the cells were, for example,
policed out, lost to congestion, or misdirected to another endpoint.
The likely user-visible symptoms of lost cells are missing talk paths or poor voice quality.
514 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
ATM-NTWK (ATM Network Error)
The “lost cells” error can help you diagnose cell underrun problems. When cell underruns
are accompanied by lost cells errors, the lost cells could have caused the underruns. But if
you have cell under runs without lost cells, it could indicate that the underruns were due to
network jitter instead. It is also possible that network jitter can cause both cell underruns
and lost cells, if the jitter is so severe it causes the cells to violate their traffic contract.
When accompanied by congestion or CLP errors, the congestion or CLP can be causing the
lost cells.
When accompanied by cell overrun errors, the cell overruns can be causing the TN2305 to
discard cells, which in turn can show up as lost cells.
Lost cells without other errors can indicate that cells are being corrupted, especially the
AAL1 sequence number.
In any case, consult your ATM network vendor about possible causes. Look for jitter (cell
delay variation), cell discard, and traffic policing.
Issue 3 February 2007
515
Communication Manager Maintenance Object Repair Procedures
ATM PNC-DUP (ATM PNC Duplication)
S8700 Fiber-PNC
MO Name in Log
Alarm Level
Initial Command to Run
Full Name of MO
PNC-DUP
NA
status pnc
PNC duplication
The PNC-DUP MO tracks the health of the active and standby PNCs, controls planned and
spontaneous interchanges, and manages related functions such as double call refresh and
unrefresh, antithrashing, and so on. The main responsibility of PNC-DUP is to recover the
system to full service in the event of a fault. In the event of multiple faults, PNC-DUP does its
best to maximize service continuity.
Note:
ATM PNC-DUP behaves differently when the system is running the ATM PNC
feature. While not a separate MO, this discussion explains the unique behavior of
PNC-DUP under the ATM PNC feature.
Note:
In critical-reliability systems, the following components comprising the port-network connectivity
(PNC), are duplicated:
●
ATM-Expansion Interface (ATM-EI) circuit packs in port networks (PNs)
●
Fiber-optic cables connecting the above circuit packs to the ATM Switch Interface Modules
●
ATM Switch
Although not part of the PNC, Tone-Clock circuit packs are also duplicated in each PN. ATM
PNC systems can have up to 64 PNs.
PNC duplication architecture utilizes an active/standby duplication scheme in which one
complete set of PNC components supports call processing, while the duplicate PNC is held in
reserve. All calls on the active PNC are simultaneously set up, or shadowed, on the standby
PNC in order for it to be capable of instantly assuming active status when necessary, allowing
for interchanges without service disruption (in the case of single faults).
PNC duplication does not introduce any additional types of hardware or hardware faults, and
there are no tests associated with the PNC-DUP MO. Instead, its error log entries contain useful
information about the occurrence and causes of interchanges in order to facilitate diagnosis of
problems, which can then be addressed by using the documentation for the individual MO
involved.
516 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
ATM PNC-DUP (ATM PNC Duplication)
PNC-DUP Related Commands
Table 138: PNC-DUP Commands on page 517 lists the PNC-DUP related commands and their
output forms are fully described in Maintenance SAT Commands in Maintenance Commands
for Avaya Communication Manager 4.0, Media Gateways and Servers, 03-300431.
Table 138: PNC-DUP Commands
Command
Description
status pnc
Shows information about both PNCs’ operational status,
including state of health, alarms, busyouts and locks.
reset pnc interchange
Initiates a demand PNC interchange. If the standby is healthy
(all-zero state-of-health indexes), there is no effect on service.
Otherwise, calls may be dropped.
set pnc
Locks or unlocks the active PNC, preventing interchanges.
Does not interfere with double call setup.
busyout pnc
Removes the standby PNC from service. See also the section
on busyout of PNC components.
Busyouts and PNC-DUP
Busyout pnc puts the standby PNC in the busyout state. In this condition:
●
Double call set up is turned off.
●
The standby PNC is unrefreshed; existing duplicate call connections are removed.
●
PNC interchanges are prevented.
Upon release, interchanges are re-enabled and a global refresh of double call setup on the
standby is performed.
When PNC duplication is in effect:
●
●
●
An active PNC component cannot be busied-out.
A standby PNC component can only be busied-out when the standby PNC is first
busied-out.
The standby PNC cannot be released unless all standby PNC components are released.
Issue 3 February 2007
517
Communication Manager Maintenance Object Repair Procedures
Enabling and Removing PNC Duplication
To Enable PNC Duplication
To enable PNC duplication, perform the following sequence of steps:
1. Enable administration of PNC-DUP on the change system-parameters
customer-options screen.
2. Fully administer duplicate ATM PNC connectivity. Verify by list atm pnc. Or for IP
duplication, go to step three.
3. Fully administer IPSI duplication (ipserver-interface duplication). Verify by using
list ipserver-interface.
4. Activate PNC-DUP through the change system-parameters duplication screen.
This is not allowed if any component of either PNC (A or B) is busied out.
5. The system must insert all connectivity-related components for both standby and active
PNC, a process that takes up to 5 minutes, depending upon circuit pack insertion. The
process finishes when the first terminal login prompt appears.
6. The PNC-DUP initialization anti-thrashing timer must expire (this occurs 5 minutes after
completion of board insertion, PNC interchange, or system reset of level 2 or higher).
To Disable PNC Duplication
To disable PNC duplication perform the following sequence of steps:
1. Verify that the A-PNC is active. A forced interchange may be required. See reset pnc.
2. Busyout the standby PNC (B-PNC).
3. Turn off the system parameter for PNC-DUP through change system-parameters
duplication.
4. Remove the B-PNC connectivity by removing the Board Locations on the change fiber
screen for ATM PNC.
5. Remove the B-PNC circuit packs (ATM-EI boards). Enter change circuit-pack
location.
6. Disable administration of PNC duplication on the change system-parameters
customer-options screen by changing the PNC Duplication field to n.
Notes:
●
●
●
Alterations to PNC that involve only the addition of connectivity can be done with
PNC-DUP operational.
Alterations requiring the removal of connectivity must be done with PNC-DUP removed.
PNC-DUP must be removed and translations should be saved before making any
hardware changes.
518 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
ATM PNC-DUP (ATM PNC Duplication)
Steady State LEDs
The LEDs of PNC components in a stable duplicated system should appear as follows:
●
For an active ATM EI (functioning as Archangel) in a PN without IPSIs, the amber LED’s
flash pattern is 2 seconds on/200 ms off.
●
For a standby ATM EI in a PN without IPSIs, the amber LED is off.
●
For an active ATM EI in a PN with IPSIs, the amber LED is on steady.
●
For an standby ATM EI in a PN with IPSIs, the amber LED is off.
PNC State of Health
PNC-DUP software monitors the health of the two PNCs as determined by their state-of-health
(SOH) vectors, and initiates an interchange when the health of the active falls below that of the
standby (unless prevented from doing so by a PNC lock, busyout, or antithrashing mechanism).
Potentially service-disrupting faults that occur in a PNC’s components are reported to
PNC-DUP and incorporated in the affected PNC’s state of health. The SOHs of both PNCs are
displayed on the status pnc screen, as shown in Figure 37: Status PNC screen with standby
PNC fully In-Service on page 519.
Figure 37: Status PNC screen with standby PNC fully In-Service
status pnc
page 1 of 1
PORT-NETWORK CONNECTIVITY
Duplicated? yes
Software Locked? no
Standby Busied? no
Standby Refreshed? yes
Interchange Disabled? no
A-PNC
Mode: active
State of Health: functional
Inter PN Index: 00.00.00.00
Major Alarms: 0
Minor Alarms: 0
Warning Alarms: 0
B-PNC
Mode: standby
State of Health: functional
Inter PN Index: 00.00.00.00
Major Alarms: 0
Minor Alarms: 0
Warning Alarms: 0
Issue 3 February 2007
519
Communication Manager Maintenance Object Repair Procedures
PNC State-of-Health Indexes
The Inter-PN Index screen the state-of-health vector is used to track and compare the states of
health of both PNCs. The fields making up the indexes are 2-digit numbers separated by
periods (.), with each field representing a different class of faults. The fault class fields are
arranged in order of decreasing importance from left to right. In other words, each field in the
index supersedes the following fields in determining which PNC is healthiest. A fault class
drives an interchange only when all of the higher priority fault classes are equal. A zero entry
indicates no faults present for that class. Increasing numbers indicate increasingly higher
numbers of faults present in that class.
The Inter-PN Index contains four fields (XX.XX.XX.XX). The Inter-PN Index reports faults in
connectivity between PNs.
●
The meaning of each fault class field is given in Table 139: PNC State-of-Health Fault
Classes on page 520.
●
A zero entry indicates that there are no faults reported.
●
Higher numbers indicate increasing number of faults.
●
All zeros indicate a perfect state of health.
●
Unless the PNCs are locked, the active PNC’s state of health should always be equal to or
better than the standby’s. Otherwise, the system performs a spontaneous interchange.
After a PNC-related alarm is cleared, the system performs a partial refresh of the standby PNC.
The corresponding fault class field is not updated to reflect the improved state of health until the
refresh is done. The state-of-health indexes do not agree with the current alarm status during
this period.
Table 139: PNC State-of-Health Fault Classes
Fault
Class
Priority
Description
MOs
FC_EAL
1
Number of PNs with EALs down
EXP-PN
FC_PACL
2
Number of PNs with LINL, RINL, or EI-SNI neighbor link
faults
EXP-PN
FC_BFD
3
Number of PNs with BFDL (Bearer Fault Detection Link)
faults
SYS-LINK
FC_HW
4
Number of PNs affected by hardware faults in a link having
an EI as an endpoint. Enter list atm pnc to see endpoint
designations.
ATM-EI
520 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
ATM PNC-DUP (ATM PNC Duplication)
Resolving Poor State of Health
When both PNCs do not have an all-zero SOH (perfect health), use the following steps to
identify and repair the problem.
1. Look for PNC component alarms (major or minor) for the PNC side without an all-zero SOH.
The standby PNC should be repaired first.
2. Busy-out the standby PNC.
3. Follow the appropriate diagnostic and repair procedures for the alarmed PNC components
just as with a simplex PNC. Both the alarm and error logs should be examined to isolate the
fault.
4. Verify that the related PNC’s SOH is restored to all zeros.
5. Release the standby PNC.
Refresh and Unrefresh of the Standby PNC
In a fully-functional PNC with healthy standby and active sides, the standby PNC has a
complete set of call connections corresponding to those in the active PNC. If, however, the
standby PNC’s state of health degrades, a selective unrefresh of those connections that utilize
the faulted component(s) is performed. If the standby PNC’s health improves, a selective
refresh of connections on the affected route is performed so that call setup is consistent
between the active PNC and the healthy parts of the standby PNC.
The Standby Refreshed? field on the status pnc screen does not refer to the selective type
of refresh. It refers only to a global refresh that is performed when:
●
The system is initialized and PNC duplication is enabled.
●
There has been a spontaneous PNC interchange.
●
The standby PNC has been released from busy-out.
●
A system reset of level 2 or higher has taken place.
The Refreshed field may display yes when in fact the standby is partially unrefreshed. An
interchange into an incompletely refreshed standby results in dropped calls. This can happen
when a more severe fault occurs on the active PNC or when reset pnc interchange is
used with the override option.
Issue 3 February 2007
521
Communication Manager Maintenance Object Repair Procedures
PNC Interchanges
PNC spontaneous interchanges occur when PNC duplication software determines that the
standby PNC’s state of health (SOH) surpasses the active PNC’s.
●
●
●
PNC-DUP executes a spontaneous interchange in response to a message from a PNC
component MO indicating that either a fault has occurred on the active PNC or a fault has
been resolved on the standby PNC.
The PNC SOH is compared to the standby PNC, and an interchange occurs if the standby
PNC’s state of health surpasses the active PNC’s.
A corresponding Major or Minor alarm is logged by the reporting MO, stimulating an alarm
report.
When the resolution of a fault on the standby renders it more healthy than a
simultaneously-faulted active PNC, the error message indicates the type and location of the
improved component.
Once the interchange completes, the failed component is on the standby PNC. A demand
interchange can be requested in the presence or absence of standby PNC faults. The following
sequence of actions can be observed during a fault-free interchange:
1. The ATM-Expansion Interfaces currently acting as archangels in the PNs are deactivated as
indicated by the amber LEDs going from flashing to on solid.
2. The ATM-EIs in IPSI connected PNs are interchanged, indicated by the new standby
ATM-EI amber LED off and the new active ATM-EI amber LED on steady.
3. One by one, the ATM-EIs in non IPSI connected PNs are interchanged as indicated by new
standby ATM-EI amber LED turning off and the new active ATM-EI amber LED flashing (2
seconds on / 200 milliseconds off). At this point, the interchange is functionally complete.
Certain conditions may interfere with the normal execution of the interchange:
1. In a faulted spontaneous interchange, it is possible the PN(s) directly affected by the fault
will be the last to interchange.
2. A user directly affected by the single fault instigating a PNC interchange can experience a
momentary voice path outage during the switch.
3. If faults exist on both the standby and active PNC, it is possible to have some PNs go out of
service while others are returned to service.
In any multifault situation, rely on status pnc to determine which is the active PNC.
PNC duplication informs Timing Synchronization maintenance when a PNC interchange has
been completed and indicates which PNC is active. This causes Synchronization to audit and
ensure that the primary source for synchronization of Tone-Clocks in each PN is supplied by a
path associated with the active PNC.
522 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
ATM PNC-DUP (ATM PNC Duplication)
Antithrashing and PNC Interchanges
Following a spontaneous PNC interchange, subsequent PNC interchanges are prevented for 5
minutes. This condition is indicated by y in the Interchange Disabled? field of the status
pnc screen. After 5 minutes, the antithrashing timer expires, interchange decisions are
re-enabled, and the field displays n.
Note:
Note:
Should a catastrophic failure occur on the active PNC during the period when the
Interchange Disabled? field is set to “yes,” there will be no spontaneous
PNC interchange.
Demand PNC interchanges also invoke anti-thrashing, but only for a period of 30 seconds.
During antithrashing mode, demand interchanges are also prevented unless the override option
is specified.
! CAUTION:
Use of this option may cause a service disruption.
CAUTION:
Repairs on the Standby PNC Components
! CAUTION:
If there is a TDM-CLK alarm, system timing may be routed through part of the
standby PNC, and circuit switched data may be affected by the following repair
procedures. This can happen, for example, when a slave tone/clock circuit pack
experiences a loss of signal and switches to receive timing from the standby
ATM-EI. In this case TDM-CLK 2305 error is logged, and the clock problem
should be addressed first, if possible.
CAUTION:
To repair PNC components in a duplicated PNC proceed as follows:
1. Most repairs involve fixing a single fault on the standby PNC. Enter set pnc lock or
busy-out pnc to prevent an interchange into the PNC being repaired.
2. If a faulty component exists on the active PNC, this also means that the standby PNC is
more severely faulted. Normally, the standby PNC is repaired first, since it is the most
severely impaired.
To repair the active PNC (standby is already repaired), enter set pnc unlock, which
generates a spontaneous interchange. In a PNC demand interchange with reset pnc
interchange use the override-and-lock qualifier for the active PNC. The
override-and-lock option ensures that no subsequent interchange can occur during
the repair of the standby PNC. A demand interchange may not be necessary if the following
conditions drive a spontaneous interchange:
●
The anti-thrashing period from the last interchange has expired.
Issue 3 February 2007
523
Communication Manager Maintenance Object Repair Procedures
●
The global refresh from releasing the standby PNC has completed.
●
The standby PNC’s state of health surpasses the active PNC’s.
At this point, the faulty component is on the standby PNC, and the PNCs are locked in their
current active/standby state.
3. Busyout the PNC with busyout pnc.
4. Use fault isolation and component testing procedures for the individual PNC components,
just as for a simplex PNC. Replacement of components does disrupt operation of the active
PNC.
5. Once the failed component is replaced, use status pnc to check the health standby PNC
component.
6. When confident that the problem has been resolved, as indicated by an all-zero state of
health, unlock (set pnc unlock) and release (release pnc) the PNC. Note that no
further PNC interchange is required since you can test the standby PNC as thoroughly as
the active.
Interactions: Server Resets and PNC Interchanges
●
●
A system reset of level 1 (warm), 2 (cold2) or 4 (reboot) does not change which PNC is
active. If a PNC interchange was in progress when the reset took place, the PNC
interchange continued until completion.
If a reset system 1 (warm) takes place during a PNC interchange, the reset is
escalated to level 2 (cold2).
Fault Isolation Using Duplicated PNC
In some cases, PNC duplication can aid in the fault isolation procedure. PNC interchanges can
be used to help isolate the faulty hardware. Two examples demonstrating this technique follow:
1. There is a fault that can occur in either an IPSI connected PN’s ATM-EI or the PKT-INT
which cannot be readily attributed to one board or the other. If the packet bus transceivers
on either the PKT-INT or ATM-EI fail, the two boards cannot communicate, but it will not be
clear which board is at fault. In this case, a planned interchange of the PNC can be used to
indicate which of the two boards. If the interchange:
- Cures the problem, the ATM-EI was at fault
- Does not cure the problem, the PKT-INT is suspect (provided there are no PKT-BUS
faults)
524 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
ATM PNC-DUP (ATM PNC Duplication)
2. A similar relationship exists for the PN Archangel (EAA - the active ATM-EI) and certain
TDM-bus problems. If the EAA is unable to communicate with a port board over the TDM
bus, either the EAA has a fault, the port board has a fault, or there is a problem with the
TDM bus itself. If TDM bus maintenance tests find no problems with the bus, then it is either
the port board or the EAA. It may be simpler to replace the port board than to request a
PNC interchange. However, if it is not clear which port board may be at fault or maintenance
is being performed remotely, verify that the EAA is not at fault by executing a PNC
interchange. If the interchange solves the problem, then the EAA is faulty. If the problem
persists after the interchange, but TDM bus maintenance finds no problem, then the port
board is faulty.
Error Log Entries
Whenever a PNC interchange takes place, an error is logged against PNC-DUP with a code
that conveys information about the cause of the interchange and which PNC became active.
There are no alarms associated with PNC-DUP errors, but there should be an alarm against the
PNC component that caused the interchange. There are no PNC-DUP test sequences, but
status pnc provides information regarding the status of the PNCs. The information in
Table 140: Error Code descriptions and Aux Data correlations on page 525 and
Table 141: Error Log Encode Field Decoding on page 526 can help to identify which areas of
the Alarm Log to investigate to find the source of the problem.
Table 140: Error Code descriptions and Aux Data correlations
Error
Code
Description
Aux Data1
00000
Error in generating error code
None
1cxpp
Spontaneous Interchange in response to a constraint for A-PNC
Active PNC
2cxpp
Spontaneous Interchange in response to a constraint for B-PNC
Active PNC
51000
Spontaneous Interchange at expiration of SOH validation timer
Active PNC
52000
Spontaneous Interchange upon PNC UNLOCK
Active PNC
53000
Spontaneous Interchange at completion of Global Refresh
Active PNC
60801
PNC Demand Interchange
Active PNC
60800
PNC Demand Interchange with override
Active PNC
1. The Aux Data indicates which PNC became active after the PNC interchange: “0” denotes PNC-A; “1”
denotes PNC-B.
Issue 3 February 2007
525
Communication Manager Maintenance Object Repair Procedures
Table 141: Error Log Encode Field Decoding
Field
Variable Name
Values
Description
c
Alarm Type
0
1
Alarm retired
MAJOR or MINOR alarm on any PNC component
x
Fault class; see
description for
contributing
MOs
0
EAL (Expansion Archangel Link - EXP-PN) carries CCMS
messages
1
PACL (ATM-EI) carries ATM signaling commands from Call
Processing to the remote ATM-EI circuit packs
2
PNC hardware (providing connectivity of PN-to-PN or
-ATM-EI)
5
BFDL (bearer fault detection link) solely for the purpose of
detecting bearer faults
0–63
0–2 for constraint class (this is an internal number; add 1 for
external port number)
pp
Port-network
number
Error log entries and recommended actions
Note:
Error
Type
Aux
Data
Associated Test
Alarm
Level
On/Off
Board
Recommended Action
18
None
busy PNC-DUP
WRN
ON
release pnc-dup
Note:
The list config port-network command displays the cabinet number
associated with a PN.
526 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
ATM-SGRP (ATM Signaling Group)
ATM-SGRP (ATM Signaling Group)
MO Name in Log
Alarm Level
Initial Command to Run1
Full Name of MO
ATM-SGRP
MIN
WRN
test sig-group grp#
ATM-CES Signaling Group
1. grp# is the signaling group number (1–166); the test sequence can be either short or long.
ATM-SGRP applies when ATM signaling groups have been administered on an ATM circuit
pack as ATM trunks.
Table 142: ATM-SGR circuit packs outlines the differences between ATM interface circuit
packs:
Table 142: ATM-SGR circuit packs
Circuit
pack
Channel
types
Interface
Fiber
Echo
cancellation
TN2305
B and D
channels
24- or
32-channel
Multimode
Y
TN2306
B and D
channels
24- or
32-channel
Single-mode
Y
The TN2305 and TN2306 ATM Interface circuit boards are referred to as TN230X for the
remainder of ATM-SGRP.
An ATM Signaling Group is a collection of B-channels for which a given ISDN-PRI
signaling-channel port (ATM D channel) carries signaling information. ATM B channels
(ATM-BCH) carry voice or data and are assigned to ISDN trunks. For more information see
ATM-TRK (Circuit Emulation Service Circuit Pack) on page 541.
The operation of the entire ATM signaling group depends on several other entities:
●
ATM-DCH signaling-channel port
●
TN230X Interface circuit pack where a D channel resides
●
System link to the processor via the packet bus
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)
Issue 3 February 2007
527
Communication Manager Maintenance Object Repair Procedures
Error log entries and recommended actions
Table 143: ATM-SGRP Signaling Group Error Log Entries
Error
Type
Aux Data
Associated Test
Alarm
Level
0
0
Any
Any
1 (a)
Any
None
On/Off
Board
Recommended Action
test sig-group grp#
MO busied out
18 (b)
257 (c)
Any
None
test sig-group grp#
769 (d)
Any
Primary Signaling Link
Hardware Check (#636)
test sig-group grp#
1281
(e)
Any
Secondary Signaling Link
Hardware Check (#639)
test sig-group grp#
1793
(f)
Any
Layer 2 Status Test (#647)
WRN
OFF
test sig-group grp#
2305
(g)
Any
Remote Layer 3 Query test
(#637)
MIN
OFF
test sig-group grp#
3585
(h)
Port
number
None
3840 3928
(i)
Port
number
None
Notes:
a. Error Type 1: switch sent a message to the far-end switch or terminal adapter, and the far
end did not respond in the time allowed. Possible causes include link failure and congestion
or outage at the far end. The Aux Data field contains layer-3 protocol information used by
internal counters.
If no other symptoms are present, no action is required.
If layer-3 communication is down, check for alarms and errors against link components.
Check out other errors against ATM-SGRP, ATM-TRK, and other hardware components on
the link. There is no test to clear these errors. The error counter is decremented by 1 every
15 minutes.
528 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
ATM-SGRP (ATM Signaling Group)
b. Error Type 18: the ATM circuit pack has been busied out (either busyout atm sig-grp
or busyout board location).
1. Release the ATM signaling group (release atm sig-grp) or the circuit pack
(release board location).
c. Error Type 257: the primary signaling channel connection has been lost for more than 90
seconds.
●
●
●
The associated B-channels are placed in the ISDN Maintenance/Far-End state.
The B-channels are not usable for outgoing calls, although incoming calls can be
accepted.
The switch automatically attempts to recover the signaling link.
1. Check the results of the Primary Signaling Link Hardware Check (#636) in the test
sequence.
●
When the link does recover, the B-channels are negotiated back to the In-Service state
and their alarms are retired.
2. When this error occurs, the state of the Signaling Group is changed to out-of-service
(verify using the status sig-group command).
d. Error Type 769: signaling link hardware error.
Service-affecting failures of the hardware used to transport the D channel are reported to
the ATM CES Signaling Group MO. Maintenance logs this error, places the D channel into
the OOS state, and raises a board-level alarm. The D channel is returned to service, and
the alarm is retired once the hardware failure condition clears.
e. Error Type 1281: Degraded PVC alarms indicate that a particular Permanent Virtual Circuit,
or signaling group, has encountered sufficient errors to exceed firmware thresholds.
Operations can continue but at a lower level of reliability or performance. Firmware filters
these alarms so that only one is reported active at a given time. The following inline error is
considered a Degraded PVC alarm:
●
Excessive AAL – The AAL layer is experiencing an excessive number of errors in trying
to reconstruct Service Data Units (SDUs). Possible causes:
- Problem with the ATM switch
- Noisy communication paths on opposite side of ATM switch
- Unhealthy sending node
- Congestion at the ATM switch
f. Error Type 1793: Layer 2 Query test for the primary signaling channel failed.
●
Excessive AAL – The AAL layer is experiencing an excessive number of errors in trying
to reconstruct Service Data Unit (SDUs). Possible causes:
- Problem with the ATM switch
- Noisy communication paths on opposite side of ATM switch
- Unhealthy sending node
- Congestion at the ATM switch
Issue 3 February 2007
529
Communication Manager Maintenance Object Repair Procedures
g. Error Type 2305: The Remote Layer 3 Query (#637) failed. A specific message was sent to
the far-end switch, and it did not respond within the time allowed.
1. Investigate elements of the ATM D channel(s) (ATM-DCH) for both this switch and the
far-end switch.
If Test #637 fails twice in a row, the B-channels are alarmed and made unavailable for
outgoing calls (although incoming calls are still accepted). When Test #637 succeeds and
the far-end switch starts responding properly, the ATM trunk (B-channels) are placed back
into normal operation and their alarms retired.
h. Error Type 3585: A SERV or SERV ACK ISDN D-channel message has been received by a
non-US-type interface (country option other than 1 on the DS1 administration screen).
However, these messages are used only for duplex NFAS signaling, which is supported by
country protocol 1.
Thus, there may be a mismatch in administration between the local and far-end switches.
1. Consult with the customer’s network provider to determine whether the D channel is set
up correctly on the far-end switch.
i. Error Type 3840-3928: These error types are used to report certain error messages
received by the ATM-SGRP Signaling Group for one of its associated B-channels. The Aux
Data field is the port number of the B channel from which the message was received.
The error code generated equals 3840+x, where x is a Cause Value defined by the ISDN
PRI Specification. Note that there is no recommended action for these error types; selected
ISDN cause values are placed in the log when they are received, but no direct action or
alarming is performed solely in response to receiving them. They provide added data that
may prove useful when tracking down obscure networking and routing problems. See
Table 144: Descriptions and repair recommendations (Error Types 3840-3928) on
page 530 for more information.
Table 144: Descriptions and repair recommendations (Error Types 3840-3928) 1 of 5
Error
Code
Description
Recommendation
3842
A request has been
made to use a transit
network or common
carrier that cannot be
accessed.
From the circuit pack and port number (in the Aux Data
field), determine the trunk group against which the error
was reported.
1. Check every routing pattern containing this trunk group
for validity of interexchange carriers requested (IXC
field).
1 of 5
530 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
ATM-SGRP (ATM Signaling Group)
Table 144: Descriptions and repair recommendations (Error Types 3840-3928) 2 of 5
Error
Code
Description
Recommendation
3846
The far-end switch has
indicated that the
B channel (trunk) is
not acceptable for use
in the call for which it
was requested.
This could indicate
●
●
an administration problem (for example, the local
switch and the far-end switch have different
B-channels administered)
a normal race condition (for example, the local switch
has requested use of a B-channel that the far-end
switch had just reserved for use on another call).
1. From the circuit pack and port number (in the Aux Data
field), determine the trunk group against which the
error was reported.
2. Enter status trunk for the indicated trunk.
3. Refer to Table 124: ATM ISDN service states on
page 475 for recovery suggestions.
3858
3878
Similar to Error Type
1. The switch sent an
ISDN message to the
far-end switch or
terminal adapter that
did not respond in the
time allowed.
The far-end switch has
indicated that the
network is not
functioning correctly
and that the condition
may last a relatively
long period of time (for
example, immediately
re-attempting the call
may not be
successful).
1. Check for alarms and errors against link components
2. Check out other errors against ATM-SGRP (ATM
Signaling Group), ATM-TRK (Circuit Emulation Service
Circuit Pack), and other hardware components on the
link.
1. From the circuit pack and port number (in the Aux Data
field, determine the trunk group against which the error
was reported.
2. Consult with the network provider to determine the
nature and expected duration of the out of service
condition.
3. Consider modifying every routing pattern containing
this trunk group, to route calls around the network that
is out of service.
2 of 5
Issue 3 February 2007
531
Communication Manager Maintenance Object Repair Procedures
Table 144: Descriptions and repair recommendations (Error Types 3840-3928) 3 of 5
Error
Code
Description
Recommendation
3890
A request to use a
network service (for
example, SDN) has
been denied.
Administration
somewhere in the
network has indicated
that the requested
service has not been
subscribed to or
purchased for this
trunk.
This could indicate
●
●
a local administration problem
a mismatch between the local administration and that
of the network provider.
1. From the circuit pack and port number (in the Aux Data
field), determine the trunk group against which the
error was reported.
2. Display the trunk group screen.
If the trunk group is Call-by-Call (the Service Type
field is cbc), check every routing pattern screen
containing this trunk group to see if the Service/
Feature fields contain the correct network services
purchased for this trunk.
If the trunk group is not Call-by-Call, check that the
Service Type field contains the single network service
purchased for this trunk.
3. If local administration appears correct, consult with the
customer and/or the network provider to determine the
services that the customer has subscribed to for this
trunk group.
3892
Protocol detail; may
offer a clue if customer
is having ISDN calls
denied with an
unexpected intercept
tone.
1. If customer is complaining of unexpected intercept
tones when accessing ISDN trunks or PRI endpoints
and no other cause can be found, escalate the
problem and provide the next tier with this Error Log
information.
3 of 5
532 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
ATM-SGRP (ATM Signaling Group)
Table 144: Descriptions and repair recommendations (Error Types 3840-3928) 4 of 5
Error
Code
Description
Recommendation
3894
Protocol detail; may
offer a clue if customer
is having ISDN calls
denied with an
unexpected intercept
tone.
Do the following:
1. Eliminate any transitory state mismatch problems
(test port location for the trunk port shown in
the Aux Data field). Service State Audit Test (#256) is
the important test in the sequence.
2. If Test #256 passes yet the customer continues to
complain of unexpected intercept tones when
accessing ISDN trunks or PRI endpoints and no other
cause can be found, escalate the problem and provide
the next tier with this Error Log information.
3905
3906
3909
Protocol detail; may
offer a clue if customer
is having ISDN calls
denied with an
unexpected intercept
tone.
Do the following:
Protocol detail; may
offer a clue if customer
is having ISDN calls
denied with an
unexpected intercept
tone.
Do the following:
A request to use a
network service has
been made, but the
network has rejected
the request because
the requested service
is not implemented.
Follow the recommendations for Error Type 3890.
1. If customer is complaining of unexpected intercept
tones when accessing ISDN trunks or PRI endpoints
and no other cause can be found, escalate the
problem and provide the next tier with this Error Log
information.
1. If customer is complaining of unexpected intercept
tones when accessing ISDN trunks or PRI endpoints
and no other cause can be found, escalate to the
problem and provide the next tier with this Error Log
information.
4 of 5
Issue 3 February 2007
533
Communication Manager Maintenance Object Repair Procedures
Table 144: Descriptions and repair recommendations (Error Types 3840-3928) 5 of 5
Error
Code
Description
Recommendation
3928
A call was denied
because of a basic
incompatibility
between the type of
call and either the
facilities selected by
the routing pattern or
the called user itself.
This error might be helpful as a clue if the customer
complains of receiving unexpected intercept tone after
accessing ISDN trunks or PRI endpoints.
1. Determine the trunk group from the circuit pack and
port number (in the aux data field)
2. check the BCC fields of the pertinent routing patterns.
3. Also, investigate whether or not the calling and called
endpoints are compatible (for example, some ISDN
switches may not allow a voice station to call a data
extension).
5 of 5
Demand test descriptions and error codes
Investigate tests in the order presented. By clearing errors associated with the first test, errors
generated from other tests may also be cleared. Click on the link to see the full description of
the test, error codes, and recommended actions.
Short Test
Sequence
Long Test
Sequence
D/ND1
Primary Signaling Link Hardware Check (#636)
X
X
ND
Layer 2 Status Test (#647)
X
X
ND
ATM Remote Layer 3 Query (#1291)
X
X
ND
Order of Investigation
1. D = Destructive, ND = Nondestructive
534 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
ATM-SYNC (ATM Synchronization)
ATM-SYNC (ATM Synchronization)
S8700 Fiber-PNC
MO Name in Log
Alarm Level
Initial Command to Run
Full Name of MO
ATM-SYNC
MIN
display errors
ATM Synchronization
WRN
test synchronization
This section discusses intra-switch synchronization maintenance and the hardware and
software components that provide a common reference frequency for reliable digital
communications among the system, the ATM switch, and other PBXs, Central Offices (COs) or
customer-premises equipment (CPE). Circuit packs involved in synchronization include:
Note:
TN768 or TN780 Tone-Clock circuit packs are not compatible with ATM EIs.
Note:
●
TN2312 IPSI circuit pack’s Tone-Clock circuit
●
TN2182 Tone-Clock
●
TN722, TN464, and TN767 DS1 Interfaces (all suffixes)
●
TN2305/6 ATM Expansion Interface (multimode fiber)
Synchronization is achieved between the S8700 Media Server IPSI and the port networks (PNs)
through the ATM port-network connectivity (ATM PNC) between the networks. Depending on
the network’s synchronization plan and the status of synchronization sources, the system timing
reference may be:
●
●
●
The clock circuit pack on the ATM switch
A DS1 or UDS1 interface circuit pack-tapped T1 input signal connected to the ATM switch
clock circuit
An OC-3 interface circuit pack on the ATM switch
Stratum 4 synchronization extracts timing information directly from
●
A DS1 or UDS1 reference
●
An OC3 reference
●
The ATM switch clock
For further information about synchronization including network synchronization, refer to
DEFINITY® Communications System Network and Data Connectivity, 555-025-201.
Issue 3 February 2007
535
Communication Manager Maintenance Object Repair Procedures
Stratum 4 Synchronization
Systems may have primary and secondary synchronization references (DS1/UDS1 interface
circuit packs or ATM-Switch) when using Stratum 4 synchronization.
If the primary synchronization reference in Figure 38: Stratum-4 Synchronization with
Unduplicated ATM PNC on page 537 is providing a valid timing signal, then the flow of system
synchronization would travel from the DS1 interface circuit pack in the PN to the ATM switch.
The primary DS1 interface circuit pack provides a timing signal for the ATM switch clock
circuitry. This synchronization source is then distributed to all of its OC3 Interface Modules.
Each ATM Expansion Interface circuit pack uses the received data stream from the ATM switch
to generate a timing signal. The Tone-Clock circuits in the PNs use this signal to generate timing
for every circuit pack in their respective PNs. All PNs, in the above mentioned scenario are
designated the slave PNs. The ATM switch is the master that contains the system
synchronization source. If the primary synchronization reference does not provide a valid timing
signal, ATM synchronization maintenance infers a switch to the secondary reference.
If the primary synchronization reference is not providing a valid timing signal, the system
automatically switches to the secondary synchronization reference. If the primary
synchronization reference is invalid, and if the secondary reference does not provide a valid
timing signal or is not administered as a synchronization reference, the switch infers that the
local oscillator of the ATM switch provides the system timing source. If the system is using the
local oscillator of the ATM switch as the system timing source because the primary and
secondary references are providing invalid timing signals, when either the primary or secondary
reference becomes valid again, the system switches back to the primary or secondary source.
When both the primary and secondary source become valid, the system switches to the primary
source, since the primary source is always preferred over the secondary source when both
sources are equally healthy.
Figure 38: Stratum-4 Synchronization with Unduplicated ATM PNC on page 537 depicts a
simplex ATM PNC with T1/OC3 synchronization reference into the ATM switch.
536 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
ATM-SYNC (ATM Synchronization)
Figure 38: Stratum-4 Synchronization with Unduplicated ATM PNC
External T1/E1
primary
Clock
External T1/E1
secondary
ATM switch fabric
ATM timing distribution
Interface
module
Interface
module
Interface
module
ATM PNC
OC3
ATM-EI
OC3
DEFINITY
EPN
DEFINITY
PPN
Tone clock
DS1
DS1
ATM-EI
Tone clock
DS1
T1-splitter
DS1
T1-secondary
T1-primary
iodfst4 LJK 011998
Note:
Note:
The TN722 DS1 Interface circuit pack does not provide a synchronization
reference as reliably as the TN767 or TN464 circuit packs. Therefore, administer
the TN767 or TN464 circuit packs as the primary or secondary sources.
Stratum-3 Synchronization
Stratum-3 synchronization is not supported on S8700 servers with ATM PNC.
Troubleshooting ATM synchronization
A significant part of the Synchronization Recovery Strategy for a S8700 system with ATM PNC
resides in the ATM switch’s clock hardware, firmware, and software. The system monitors
synchronization performance and alarms any faulty components. See SYNC (Port Network
Synchronization) on page 1231.
Issue 3 February 2007
537
Communication Manager Maintenance Object Repair Procedures
ATM-SYNC Commands
Use the commands in Table 145: ATM-SYNC commands to help troubleshoot ATM-SYNC
problems:
Table 145: ATM-SYNC commands
Command
Description
change synchronization
Allows primary and secondary references to be administered
for the Stratum 4 option, or ATM-Switch, indicating that the
synchronization references are input directly to the ATM
switch
status synchronization
Shows the current inferred synchronization reference
status synchronization
Shows the administered primary and secondary
synchronization references
disable/enable
synchronization-switch
Prevents or allows switching to another synchronization
source
test synchronization
Tests the administered synchronization source
Error log entries and recommended actions
Table 146: ATM-SYNC Error Log Entries
Error
Type
Aux
Data
Associated
Test
Alarm
Level
On/Off
Board
Recommended Action
0 (a)
0
Any
Any
Any
test synchronization
1 (b) (h)
None
WRN
MINOR
OFF
None
257 (c) (h)
None
WRN
MINOR
OFF
None
513 (d) (h)
None
WRN
MAJOR
OFF
None
1537 (e)
None
WRN
OFF
None
1793 (f)
0-50
None
NONE
OFF
None
2049 (g)
0
None
WRN
OFF
None
538 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
ATM-SYNC (ATM Synchronization)
Notes:
a. Error Type 0: Run the short test sequence first. If every test passes, run the long test
sequence. Refer to each appropriate test’s description, and follow its recommended
procedures.
b. Error Type 1: problem with the primary DS1 reference. It is cleared when the primary
reference is restored. The following steps should give an indication of the source of the
problem:
1. Check if the primary DS1 interface circuit pack is inserted in the carrier with list
configuration board location.
2. Verify that the administered primary reference matches the DS1 reference from the
network synchronization plan.
3. Test the primary DS1 interface circuit pack with test board location long. Check
the Error Log for DS1-BD or UDS1-BD errors and see DS1-BD (DS1 Interface Circuit
Pack) on page 699 or UDS1-BD (UDS1 Interface Circuit Pack) on page 1357 to resolve
any errors associated with the primary DS1 (DS1 or UDS1) interface circuit pack. If the
only errors against DS1-BD or UDS1-BD are slip errors, then follow the procedures
described in the troubleshooting section above. If no errors are listed in the Error Log for
the primary DS1 interface circuit pack, continue with the following steps.
4. Test the active Tone-Clock circuit in the master PN with test tone-clock location long.
Check the Error Log for TDM-CLK errors and verify that TDM Bus Clock Test #148 (TDM
Bus Clock Circuit Status Inquiry test) passes successfully. If Test #148 fails with an Error
Code 2 through 32, see TDM-CLK (TDM Bus Clock) on page 1300 to resolve the
problem.
c. Error Type 257: problem with the secondary DS1 reference. It is cleared when the
secondary reference is restored. Refer to note (a) to resolve this error substituting
secondary for primary in the preceding resolution steps.
d. Error Type 513: the ATM switch clock is inferred to be providing the timing source for the
system. The primary and secondary (if administered) are not providing a valid timing signal.
Investigate errors 1 and 257 to resolve this error.
e. Error Type 1537: over half of the DS1s that are administered with slip detection enabled
through the Slip Detection field set to y are experiencing slips. It may take up to 1 hour for
these alarms to clear via the “leaky bucket” strategy.
f. Error Type 1793: inferred excessive switching of system synchronization references has
occurred. When this error occurs, it is inferred that the ATM switch clock has become the
synchronization reference for the system. It may take up to 1 hour for these alarms to clear
via the “leaky bucket” strategy.
1. Check for timing loops and resolve any loops that exist.
Issue 3 February 2007
539
Communication Manager Maintenance Object Repair Procedures
2. Test the active Tone-Clock circuit in the master PN with test tone-clock location
long.
Check the Error Log for TDM-CLK errors, and verify that TDM Bus Clock Circuit Status
Inquiry test (#148) passes successfully.
If Test #148 fails with an Error Code 2–32, see TDM-CLK (TDM Bus Clock) on
page 1300 to resolve the problem. If not, continue with the following steps.
3. For Duplicated Tone-Clock circuit packs in the master PN: Switch Tone-Clock circuit
packs on the master PN with set tone-clock location.
For Simplex Tone-Clock circuit packs in the master PN: replace the primary and
secondary (if administered) DS1 Interface circuit packs.
4. Investigate any other SYNC errors.
g. Error Type 2049: the ATM Expansion Interface circuit packs have errors that affect
synchronization. Test the ATM Expansion Interface circuit pack with test board
location.
This error is cleared by a “leaky bucket” strategy and takes up to one hour to clear (leak
away) the error counter once it is cleared.
h. Error Types 1, 257, and 513: noise on the DS1 line can cause transient alarms on
synchronization. Therefore, when a synchronization problem occurs on Error Types 1, 257,
or 513, a WARNING alarm is first raised for 15 to 20 minutes before the alarm is upgraded
to a MINOR or MAJOR alarm.
Demand test descriptions and error codes
Order of Investigation
Synchronization Update Test (#417)
Short Test
Sequence
Long Test
Sequence
D/ND1
X
X
ND
1. D = Destructive, ND = Nondestructive
540 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
ATM-TRK (Circuit Emulation Service Circuit Pack)
ATM-TRK (Circuit Emulation Service Circuit Pack)
MO Name in Log
Alarm Level
Initial Command to Run
Full Name of MO
ATM-TRK
MAJ
MIN
WRN
test board location
ATM TRUNK (ATM
Circuit Emulation
Service)
ATM-TRK explains how to test and repair TN230x ATM Interface circuit packs (TN2305 and
TN2306) that have been administered as virtual ISDN-PRI trunks for ATM Circuit Emulation
Service (CES). The maintenance instructions for TN230x circuit packs that have been
administered as Expansion Interfaces for WAN connectivity are in ATM-INTF (ATM Interface)
Description
The TN2305 and TN2306 (Table 147: ATM-TRK circuit packs on page 541) are dual-purpose
ATM circuit packs that can be administered as either:
●
●
ATM Circuit Emulation Service or virtual ISDN-PRI signaling trunks
Expansion Interfaces (ATM-EIs) for port-network connectivity (ATM PNC) between the
PNs
Either circuit pack “personality” requires SONET OC-3 or SDH STM-1 fiber cable connections
between the circuit pack and the ATM switch. As a trunk board, it supports direct connection
between ATM CES circuit packs without an intervening ATM switch.
Table 147: ATM-TRK circuit packs
Note:
Circuit
pack
Channel types
Interface
Fiber
Echo
cancellation
TN2305
B and D
channels
24 or 32
channel
Multimode
Y
TN2306
B and D
channels
24 or 32
channel
Single-mode
Y
Note:
TN230x circuit packs are not interchangeable.
ATM Circuit Emulation Service
Under ATM Circuit Emulation Service (CES), simulate ISDN-PRI circuits by assigning ports to
signaling groups. Each signaling group represents a PRI circuit, and the ports in the group
represent the D channel and B channels of that circuit.
Issue 3 February 2007
541
Communication Manager Maintenance Object Repair Procedures
Virtual D channels
Non-facility associated signaling is not supported under ATM-CES, so you must reserve one
port in each signaling group for use as a D channel. Use channel 24 when emulating a T-1
ISDN facility, and channel 16 when emulating an E-1 facility. The D channel can be any physical
port from 9 to 32.
Virtual circuits
The TN230x can support a varied number of virtual circuits, depending on the switch and the
administration of the circuit pack.
Virtual trunk groups
You cannot bundle physical DS1 ISDN-PRI circuits and virtual ATM-CES circuits into the same
trunk groups. Virtual circuits can only be assigned to all-virtual, all-ATM trunk groups.
LEDs
The ATM circuit pack LEDs give you a visual indication of the condition of the TN230x circuit
pack (Table 148: ATM-TRK LED interpretation on page 542).
Table 148: ATM-TRK LED interpretation
LEDs
Condition
LED status
Red
Error (alarm logged)
On
Red &
Green
Booting (LEDs being tested)
Blinking (on 200 ms, off 200 ms)
Green
Test/maintenance in progress
On
Amber
Fiber Loss of Signal (LOS), LOF,
MS_RDI, MS_AIS, LCD, HP_RDI,
HP_AIS, LOP, PSC
Blinking fast (100 ms on, 100 ms off)
Amber
Signal to ATM switch down
Blinking slowly (500 ms on, 500 ms off)
Amber
One or more CES signaling groups
administered
On
Amber
CES signaling group not administered or
not reporting to firmware
Off
542 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
ATM-TRK (Circuit Emulation Service Circuit Pack)
ATM-TRK-related commands
Table 149: ATM CES troubleshooting commands on page 543 lists some commands that can
be useful in troubleshooting ATM errors and alarms.
Table 149: ATM CES troubleshooting commands
Command
Description
display circuit-packs cabinet
Shows the circuit packs in the cabinet,
identifying ATM trunk as well as ATM-EI
boards. “ATM Interface” boards have not been
administered as CES or PNC.
display atm ports location
Shows the 256 ports on the ATM board with
the corresponding signaling and trunk group.
list configuration atm
Lists the ATM boards, identifying equipment
location, board code, type, and vintage.
list configuration trunks
Lists boards identifying assigned ports. While
the ATM board is listed, the 256 ports are not.
busyout/release atm
signaling-group
Busyout or release of an ATM 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).
Error log entries and recommended actions
Table 150: ATM-TRK Error Log entries 1 of 3
Error
Type
Aux
Data
Associated Test
Alarm
Level
0
0
Any
Any
None
MIN
1(a)
On/Off
Board
Recommended Action
test board location
ON
1 of 3
Issue 3 February 2007
543
Communication Manager Maintenance Object Repair Procedures
Table 150: ATM-TRK Error Log entries 2 of 3
Error
Type
Aux
Data
Associated Test
Alarm
Level
On/Off
Board
Recommended Action
18(b)
0
busyout board
location
MIN
ON
release board location
23(c)
0
None
MIN
ON
None
MIN
ON
125(d)
257(e)
Any
Control Channel
Looparound (#52)
MIN
ON
test board location r 2
513(f)
Any
ATM Crosstalk (#1298)
MIN
ON
test board location l
769(g)
35
ATM Error Query (#1259)
WRN
OFF
test board location
770(g)
25
ATM Error Query (#1259)
WRN
OFF
test board location
771(h)
26
ATM Error Query (#1259)
WRN
OFF
test board location
ATM Board Error Query
(#1259)
WRN
MIN
OFF
test board location
1281(i)
1537(j)
12
None
WRN
MIN
ON
1538(k)
0
None
WRN
MIN
ON
1794(l)
13
None
MIN
ON
2049(m)
15
None
WRN
OFF
test board location
reset board location
2306(n)
None
2561(o)
Packet interface test
(#598)
MIN
ON
test board location r 2
ATM Board DSP (#1293)
WRN
MIN
ON
test board location
test board location
2817(p)
1-24
2818(p)
1-24
WRN
MIN
ON
3330(q)
3
MIN
OFF
WRN
MIN
ON
ATM Board Error Query
(#1259)
3585(r)
3841(s)
Any
None
3842(t)
11
None
test board location l
2 of 3
544 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
ATM-TRK (Circuit Emulation Service Circuit Pack)
Table 150: ATM-TRK Error Log entries 3 of 3
Error
Type
Aux
Data
Alarm
Level
On/Off
Board
Recommended Action
None
3843 (u)
3999(v)
Associated Test
Any
None
3 of 3
Notes:
a. Error Type 1: the ATM-TRK circuit pack does not appear to be in its assigned slot.
1. Make sure that the ATM-TRK circuit pack is installed correctly seated in the slot
administered for the ATM trunk.
b. Error Type 18: the ATM circuit pack is busied out.
1. Run release board location.
c. Error Type 23: an ATM trunk is administered, but the corresponding ATM-TRK circuit pack
does not appear to be physically installed.
1. Make sure the ATM-TRK circuit pack is installed and correctly seated in the slot.
d. Error Type 125: an ATM trunk is administered but a non-ATM-TRK circuit pack is installed
in the corresponding slot. You have two options:
●
●
Replace the incorrect circuit pack with an ATM-TRK circuit pack.
Or re-administer the slot for the circuit pack that is physically present, locate the slot
where the ATM-TRK circuit pack is actually installed, and re-administer the ATM trunk.
e. Error Type 257: Control Channel Looparound 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 Control Channel Looparound Test (#52).
f. Error Type 513: ATM CrossTAlk Test #1298 failed. The board is writing to or reading from a
TDM time slot that is not allocated to the board, or the Digital Signal Processor (DSP)
selected for this test has malfunctioned.
1. Run test board location.
2. Take the corrective action specified for ATM Crosstalk Test (#1298)
g. Error Type 769, 770: the ATM switch is requesting too many LAPD retransmissions
(off-board ATM cell corruption errors).
Error
Type
Aux
Data
Description
769
35
Excessive LAPD retransmission requests
770
25
Uncorrectable ATM cell headers – threshold
Issue 3 February 2007
545
Communication Manager Maintenance Object Repair Procedures
1. Check the connections between the fiber cable, the ATM-TRK circuit pack, and the ATM
switch.
2. See PKT-BUS (Packet Bus) on page 1065 for test and corrective procedures.
3. Determine what type of fiber is installed between the ATM-TRK circuit pack and the ATM
switch.
If
Then
There is multimode fiber
Check the length of the fiber. If the cable is
longer than 2 km, it may be causing errors.
There is single-mode fiber or the length of
the multimode fiber is less than 2 km
The source of the errors can lie in the ATM
facility, the ATM-TRK circuit pack, or the far-end
circuit pack.
4. Perform ATM loopback tests on the near-end ATM-TRK circuit pack and on the far-end
circuit pack or ATM switch.
If
Then
The ATM-TRK circuit pack fails the
loopback test.
The problem is in the ATM-TRK circuit pack.
Replace the circuit pack.
The far-end circuit pack or ATM switch
fails the loopback test.
The problem is in the far-end circuit pack or ATM
switch. Consult the circuit-pack or ATM switch
documentation for advice.
The equipment at each end of the ATM
span passes the loopback test
The problem is somewhere in the ATM span. Lack
of bandwidth can be forcing an intermediate ATM
switch to drop cells.
5. Check capacity and peak bandwidth consumption for the ATM span.
If
Then
The capacity of the span is inadequate, or
bandwidth consumption is too high.
Reduce traffic on the system to ensure that it is
using no more that its subscribed bandwidth.
h. Error Type 771: the ATM switch is sending cells with unknown Virtual 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 S8700 system.
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. The
possible Aux Data values for this software counter are listed in Table 151: Error type 1281
Aux Data and repair procedures on page 547.
546 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
ATM-TRK (Circuit Emulation Service Circuit Pack)
Table 151: Error type 1281 Aux Data and repair procedures 1 of 3
Aux
Data
Alarm
Description
Repair procedure
15
SYSCLOCK
failed
The board is not locked to the TDM backplane clock signal. This is
probably due to a Tone-Clock problem.
1. Check for TDM-BUS or TONE-BD errors in the Error Log.
2. If no other problems are present, reset the circuit pack with
reset board location
16
Loss of Signal:
LOS
The fiber is not connected properly to the ATM-TRK board or ATM
switch (or to the multiplexer section [MUX] if present).It is possible
that the board transceivers are not functioning properly.
1. Run test board location.
2. If Test #1259 fails with Error Code 16, connect a fiber
back-to-back in a looped mode (one strand of fiber connecting
the transmit transceiver to the receive transceiver of the board)
and see if the amber LED flash goes away. If it does the
problem is off-board.
3. If the amber LED continues to flash, replace the circuit pack.
17
Loss of Frame:
LOF
The fiber signal cannot obtain or maintain STM-1/OC-3 framing.
1. Try to more the fiber on the ATM switch side to a different port.
2. If the problem persists, reset the circuit pack with reset
board location.
18
Multiplexer
Section Alarm
Indication
Signal:
MS_AIS
There is a major problem on the far end (between multiplexer
section [MUX] and the switch) that prohibits the circuit pack from
sending a valid signal.
1. See if the ports at the MUX and/or the ATM switch are
connected snugly.
2. Run test board location.
3. If Test #1259 fails with Error Code 18, connect a fiber
back-to-back in a looped mode (one strand of fiber connecting
the transmit transceiver to the receive transceiver of the board)
and see if the amber LED flash goes away.
4. If it does the problem is off-board.
5. If the amber LED continues to flash, replace the circuit pack; if
the error persists, escalate the problem.
1 of 3
Issue 3 February 2007
547
Communication Manager Maintenance Object Repair Procedures
Table 151: Error type 1281 Aux Data and repair procedures 2 of 3
Aux
Data
Alarm
Description
Repair procedure
19
Multiplexer
Section
Remote Defect
Indicator:
MS_RDI
The far end is detecting a major problem with the signal that this
board is transmitting.
1. Make sure the ATM switch port (or a MUX port, if present
between ATM switch and the ATM-TRK board) is the same as
the ATM-TRK circuit pack’s cable interface
2. Run test board location.
3. If Test #1259 fails with Error Code 19, connect a fiber
back-to-back in a looped mode (one strand of fiber connecting
the transmit transceiver to the receive transceiver of the board)
and see if the amber LED flash goes away.
4. If it does the problem is off-board.
5. If the amber LED continues to flash, replace the circuit pack; if
the error persists, escalate the problem.
20
Loss of pointer:
LOP
ATM framer chip is unable to access the payload part of the signal.
1. Reset the board with reset board location.
2. If the error persists replace the board.
21
Path Signal
Error (PSL)
(STM1/
SONET)
The incoming signal payload is not set up for transmission of ATM
data.
1. Make sure the ATM switch port (or a MUX port, if present
between ATM switch and the ATM-TRK board) is the same as
the ATM-TRK circuit pack’s cable interface.
22
High-level Path
Alarm
Indication
Signal:
HP_AIS
The payload is invalid.
1. Make sure the ATM switch port (or a MUX port, if present
between ATM switch and the ATM-TRK board) is the same as
the ATM-TRK circuit pack’s cable interface.
2. Run test board location.
3. If Test #1259 fails with Error Code 22, connect a fiber
back-to-back in a looped mode (one strand of fiber connecting
the transmit transceiver to the receive transceiver of the board)
and see if the amber LED flash goes away.
4. If it does the problem is off-board.
5. If the amber LED continues to flash, replace the circuit pack.
2 of 3
548 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
ATM-TRK (Circuit Emulation Service Circuit Pack)
Table 151: Error type 1281 Aux Data and repair procedures 3 of 3
Aux
Data
Alarm
Description
Repair procedure
23
High-level path
Remote defect
Indicator:
HP_RDI
The far end is detecting a major problem with the signal that this
board is transmitting. The transmitted payload is invalid.
1. Make sure the ATM switch port (or a MUX port, if present
between ATM switch and the ATM-TRK board) is the same as
the ATM-TRK circuit pack’s cable interface.
2. Run test board location.
If Test #1259 fails with Error Code 23, connect a fiber
back-to-back in a looped mode (one strand of fiber connecting
the transmit transceiver to the receive transceiver of the board)
and see if the amber LED flash goes away.
●
If it does the problem is off-board.
●
If the amber LED continues to flash, replace the circuit pack.
24
Loss of cell
delineation
(LCD)
On board ATM framer chip is not able to frame cells based on the
cell header.
1. Reset the board with reset board location.
2. If the error persists, replace the board.
27
SIGCON_DO
WN ATM
switch high
level signal.
The board cannot communicate with the ATM switch.
1. Busyout the board (busyout board location).
2. Test the board (test board long location).
3. If Test #1260 fails, replace the board.
4. If Test #1260 passes, make sure the ATM address on both the
server and the ATM switch sides are the same for this board.
5. If the address is the same, change the port on the ATM switch
side.
6. If the error is resolved, the problem is on the ATM switch port.
3 of 3
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 three times in 10 minutes, the board is isolated from the packet bus, and
the board is alarmed. To clear the alarm:
1. Restore this circuit pack to the packet bus with this command sequence:
a. busyout board location
b. reset board location
c. test board location long
d. release board location
2. If the problem persists and there are no PKT-BUS or port alarms, replace the circuit pack.
Issue 3 February 2007
549
Communication Manager Maintenance Object Repair Procedures
k. Error Type 1538: The ATM-TRK circuit pack is hyperactive (sending an abnormal number
of control messages to the processor). Use the following command sequence for this
ATM-TRK circuit pack:
1.busyout board location
2.reset board location
3.test board location long
4.release board location
5. If this error persists, replace the circuit pack.
l. Error Type 1794: LANHO transmit FIFO overflow. The circuit pack’s transmit buffers have
overflowed.
1. Run test board location r 5. If Test #598 fails, replace the circuit pack.
m. Error Type 2049: ACL Link Failure (link is down). The ATM Control Link (ACL) has failed,
communication has been interrupted between the server and the ATM-TRK circuit packs on
the system, and signaling-group parameters are not communicated across the packet bus.
1. Check the PKT-BUS (Packet Bus) and SYS-LINK (System Links) MOs, and follow the
repair procedures indicated.
2. Run test board location against the ATM-TRK circuit pack. If Test #598 fails, follow
the repair procedures for Packet Interface Test (#598)
n. Error Type 2306: too many parity errors in data received from the LAN/packet bus.
1. Run test board location
If
Then
Test 598 fails.
Follow the repair procedures for Packet Interface Test
(#598).
Test 598 passes
See PKT-BUS (Packet Bus) and perform the
specified repair.
There are no errors against
the packet bus MO
This can be a transient condition. Do nothing now, but
escalate if the error occurs repeatedly.
o. Error Type 2561: Packet Interface Loop Around test (#598) failure. The ATM-TRK circuit
pack has failed, the packet bus has a minor alarm active, or the packet bus is out of service.
550 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
ATM-TRK (Circuit Emulation Service Circuit Pack)
1. Run test board location
If
Then
Test 598 fails
Follow the repair procedures for Packet
Interface Test (#598).
Test 598 passes
See PKT-BUS (Packet Bus) and
perform the specified repair.
There are no
errors against the
packet bus MO
This can be a transient condition. Do
nothing now, but escalate if the error
occurs repeatedly.
p. Error Type 2817, 2818: DSP failure detected along the circuit path.
1. Run test board location.
2. Follow the repair procedures suggested for ATM Board DSP Test (#1293).
Error
Type
Description
2818
One or more DSPs failed. The Aux Data field contains the ID number
of DSP that failed
2817
DSP test failure. The Aux Data field contains the following information
about the failed DSPs:
X is the number of talker DSPs
Y is the number of listener DSPs
Z is the number of echo-cancelling DSPs
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.
1. Check for PKT-BUS alarms.
If
Then
There is a packet-bus alarm
There is probably a packet-bus problem,
particularly if other circuit packs on the packet
bus report the same error. See PKT-BUS
(Packet Bus) and Isolating and repairing
packet-bus faults in Maintenance Procedures for
Avaya Communication Manager 4.0, Media
Gateways and Servers, 03-300432 for repair
procedures.
1 of 2
Issue 3 February 2007
551
Communication Manager Maintenance Object Repair Procedures
If
Then
There are no packet-bus
alarms
Run the following command sequence:
1. busyout board location
2. reset board location
3. test board location long
4. release board location
The problem persists
Replace the ATM-TRK circuit pack.
2 of 2
r. Error Type 3585: Major board alarm; failure of critical components involved in the operation
of the circuit pack. The circuit pack has failed, and the switch can no longer recognize it.
Aux
Data
Description
1
ATM framer chip failure
2
NCE failed
4
TDM PLD failed
5
Every DSP on the circuit pack has failed.
6
RNP (Receive Network Processor) failed
7
TNP (Transmit Network Processor)
failed
8
MEMORY read/write failure
9
DUART failure
1. Run test board location long.
If
Then
Test #1259 fails with Error Code XXYY
and XX is an AUX value in the
preceding table
Replace the ATM-TRK circuit pack.
The system does not recognize the
circuit pack
Replace the ATM-TRK circuit pack.
s. Error Type 3841: the ATM-TRK circuit pack received an unrecognized message from the
switch and responded with an inconsistent down-link error message.
1. Do nothing. This error does not affect service.
552 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
ATM-TRK (Circuit Emulation Service Circuit Pack)
t. Error Type 3842: LANHO Receive FIFO Overflow error; the packet bus is delivering data to
the ATM-TRK circuit pack faster than the circuit pack can distribute it to the endpoint.
1. Do nothing. The circuit pack can recover by itself.
u. Error Type 3843: The firmware on the circuit pack is reporting a resource that is to low. This
error does not affect the service and no action is required.
v. Error Type 3999: circuit pack sent a large number of control channel messages to the
switch within a short period of time.
If
Then
Error Type 1538 is also present
Circuit pack is taken out of service.
Error Type 1538 is absent
Circuit pack is not taken out of service, but has
generated 50% of the messages necessary to
be considered hyperactive.
●
●
This can be normal during heavy traffic.
If the error is logged during light traffic, it
can indicate a problem with the circuit
pack or the equipment attached to it.
Demand test descriptions and error codes
Investigate tests in the order presented. By clearing errors associated with the first test, errors
generated from other tests may also be cleared. Click on the link to see the full description of
the test, error codes, and recommended actions.
Order of Investigation
Short Test
Sequence
Long Test
Sequence
Reset
Board
Sequence
D/ND1
ATM Board Time Of Day Update (#1261)
X
ND
NPE Audit Test (#50)
X
ND
Control Channel Looparound Test (#52)
X
ND
Packet Interface Test (#598)
X
X
ND
ATM Board DSP Test (#1293)
X
X
ND
X
D
X
ND
ATM Board Framer Looparound Test (#1260)
ATM Board Error Query Test (#1259)
X
1 of 2
Issue 3 February 2007
553
Communication Manager Maintenance Object Repair Procedures
Order of Investigation
ATM Crosstalk Test (#1298)
ATM Board Reset (#1256)
Short Test
Sequence
Long Test
Sequence
Reset
Board
Sequence
X
D/ND1
ND
X
D
2 of 2
1. D = Destructive, ND = Nondestructive
554 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
ATT-ADJ (Avaya Adjunct)
ATT-ADJ (Avaya Adjunct)
See BRI-SET, Various Adjuncts on page 579.
Issue 3 February 2007
555
Communication Manager Maintenance Object Repair Procedures
ATTE-AJ (Ethernet Avaya Adjunct)
See BRI-SET, Various Adjuncts on page 579.
556 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
AUX-BD (Auxiliary Trunk Circuit Pack)
AUX-BD (Auxiliary Trunk Circuit Pack)
MO Name in Log
Alarm Level
Initial Command to Run
Full Name of MO
AUX-BD
MIN
WRN
test board location
Auxiliary Trunk circuit
pack
See XXX-BD (Common Port Circuit Pack/Media Module) on page 1407 maintenance
information for circuit pack-level errors.
See AUX-TRK (Auxiliary Trunk) on page 558 for related trunk information.
Issue 3 February 2007
557
Communication Manager Maintenance Object Repair Procedures
AUX-TRK (Auxiliary Trunk)
MO Name in Log
Alarm Level
Initial Command to Run
Full Name of MO
AUX-TRK
MAJ1
MIN
test port location l
Auxiliary Trunk
WRN
test port location
1. A Major alarm on a trunk indicates that alarms on these trunks are not downgraded by set
options and that at least 75% of the trunks in this trunk group are alarmed.
The TN763B/C/D and TN417 Auxiliary Trunk circuit packs may be used to provide ports for the
following features: Music-On-Hold, loudspeaker paging (voice and coded chimes), dictation,
automated wake-up with AUDICHRON. Recorder/Announcer, and recorded announcements.
TN763C circuit packs support Mu-law companding. TN417 circuit packs support A-law
companding. TN763D can support either companding mode and defaults to mu-law on
initialization. Companding modes are administered on the location-parameters screen.
Use the following commands to administer the features:
Command
Administration
change system-parameters features
Music-On-Hold
change paging loudspeaker
loudspeaker paging
add trunk-group grp#
[Customer-Provided Equipment
(CPE) Type]
loudspeaker paging
change paging loudspeaker
system-provided paging
add trunk-group grp#
access to otherwise-provided (CPE) paging
change paging code-calling-ids
translation for code chiming
add trunk-group grp# (CPE Type)
Recorded announcement and dictation
change system-parameters
hospitality
Automatic wake-up (uses all four ports on a
TN763B Auxiliary Trunk circuit pack)
Music-On-Hold provides audible feedback to a held, parked, or otherwise split-away party
indicating that the call is still connected. The feedback can be customer-provided music, a
recorded message, or other audible indication. Since the Music-On-Hold port is always busy,
some of its port tests always abort.
The Loudspeaker Paging feature provides voice and/or code calling chime paging. If multiple
paging zones are provided at a customer’s premises, the Loudspeaker Paging feature gives a
user the option of paging to a particular zone or to every zone. If a zone is active for one page, it
cannot be used at the same time for another.
558 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
AUX-TRK (Auxiliary Trunk)
An Auxiliary Trunk circuit pack contains four ports and uses DTMF signaling. A different
hardware interface between the switch and the auxiliary equipment is used for the four types of
signaling that the auxiliary trunk circuit pack supports.
The interface used for the Communication Manager loudspeaker paging consists of the
following three pairs:
●
The Tip-Ring (T-R) pair used for voice transmission.
●
The S (S-S1) pair that carries answer supervision and/or make busy information.
●
The SZ (SZ-SZ1) pair that provides the external equipment with a seizure indication.
The interface used for recorded announcement, dictation, and other loudspeaker paging
consists of the following two pairs:
●
The Tip-Ring (T-R) pair used for voice transmission.
●
The S (S-S1) pair that carries answer supervision and/or make busy information.
The interface used for Music-On-Hold consists of one pair:
●
The Tip-Ring (T-R) pair used for voice transmission.
The interface, used for automatic wake-up using an Audichron recorder/announcer unit,
consists of the following two pairs:
●
The Tip-Ring (T-R) pair used for voice transmission.
●
The S (S-S1) pair that carries the synchronization signal.
Error log entries and recommended actions
Table 152: AUX-TRK Error Log Entries 1 of 2
Error
Type
Aux
Data
Associated Test
Alarm
Level
On/Off
Board
Recommended Action
0 (a)
0
Any
Any
Any
test port location
1(b)
57481
None
1(c)
57482
15(d)
Any
Port Audit and
Update Test (#36)
18
0
busyout port
location
WRN
OFF
release port location
None
WRN
ON
test trunk grp#/mem#
130(e
1 of 2
Issue 3 February 2007
559
Communication Manager Maintenance Object Repair Procedures
Table 152: AUX-TRK Error Log Entries 2 of 2
Error
Type
Aux
Data
Associated Test
769(c)
57482
None
257
Hybrid/Conference
Alarm
Level
On/Off
Board
Recommended Action
MIN
WRN1
ON
test port location l r 3
Looparound
Conference test
(#33)
513
NPE Crosstalk Test
(#6)
MIN
WRN2
ON
test port location l r 3
1025
Auxiliary Trunk
Diagnostic Test
(#114)
WRN
ON
test port location r 3
2 of 2
1. Major or Minor alarms may be downgraded to Warning alarms based on the values used in set options.
Notes:
a. Error Type 0: Run the short test sequence first. If every test passes, run the long test
sequence. Refer to each appropriate test’s description, and follow its recommended
procedures.
b. Error Type 1 with Aux Data 57481 indicates a port fault. Use an empty port if one is
available until the circuit pack can be replaced.
c. Error Type 1 or 769 with Aux Data 57482 indicates a fault on signaling lead, which is an
off-board error. This error should only occur with loudspeaker paging. If the trunk is being
used for another application, check that the administration is correct. Otherwise, check the
wiring to the external equipment connected to the Auxiliary Trunk and check the external
equipment.
d. Error Type 15: software audit error that does not indicate any hardware malfunction. Run
short test sequence, and investigate associated errors.
e. Error Type 130: the circuit pack has been removed or has been insane for more than 11
minutes. To clear the error, reseat or replace the circuit pack.
560 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
AUX-TRK (Auxiliary Trunk)
Demand test descriptions and error codes
Investigate tests in the order presented. By clearing errors associated with the first test, errors
generated from other tests may also be cleared. Click on the link to see the full description of
the test, error codes, and recommended actions.
Long Test
Sequence
D/ND1
Looparound and Conference Test (#33)
X
ND
NPE Crosstalk Test (#6)
X
ND
Order of Investigation
Short Test
Sequence
Auxiliary Trunk Diagnostic Test (#114)
X
X
ND
Port Audit And Update Test (#36)
X
X
ND
1. D = Destructive; ND = Nondestructive
Issue 3 February 2007
561
Communication Manager Maintenance Object Repair Procedures
AXA12-BD (AUDIX Circuit Pack)
MO Name in Log
Alarm
Level
Initial Command to Run
Full Name of MO
AXA12-BD
MIN
WRN
test board location
AUDIX circuit pack
TN568 EMBEDDED AUDIX circuit packs operating in control-link mode appear to the system as
TN746 Analog Line circuit packs with vintage greater than 50.
For circuit-pack-level problems, see XXX-BD (Common Port Circuit Pack/Media Module).
The AUDIX system has an extensive maintenance strategy of its own that is described in
DEFINITY® AUDIX Maintenance, 585-300-110.
562 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
AXA12-RS (AUDIX Reserve Slots)
AXA12-RS (AUDIX Reserve Slots)
MO Name in 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. Both test board and busyout board abort
when either is attempted on a reserved slot. An error message indicates that the slot is
associated with the circuit pack that the TN568 is emulating, but the requested operation is not
valid. If there are errors logged against these MOs, see XXX-BD (Common Port Circuit Pack/
Media Module) on page 1407.
The TN568 circuit pack connects to the switch through a single slot in the backplane; however,
the number of slots physically occupied by the circuit pack is supplied by the board when
inserted. The TN568 is 2 slots wide: the functional slot and a reserve slot. The reserve (blank)
slot to the left of the functional slot is a place holder on the switch and has no interaction with
the switch.
These MOs are place holders for the extra slot needed for the EMBEDDED AUDIX board. Each
instance of these MOs represents a reserve slot associated with the respective circuit pack
mode in which the TN568 (EMBEDDED AUDIX) is working. They are used for EMBEDDED
AUDIX and emulation of respective port types.
Issue 3 February 2007
563
Communication Manager Maintenance Object Repair Procedures
AXD12-BD (AUDIX circuit pack)
MO Name in
Log
Alarm
Level
Initial Command to Run
Full Name of MO
AXD12-BD
MIN
WRN
test board location
AUDIX circuit pack
The AXD12-BD MO represents a TN568 EMBEDDED AUDIX circuit pack operating in 12-port
digital (DP) mode. TN568 EMBEDDED AUDIX circuit packs operating in 12-port digital mode
appear to the system as TN2181 Digital Line circuit packs with vintage greater than 50.
For circuit-pack-level problems, see XXX-BD (Common Port Circuit Pack/Media Module) on
page 1407.
564 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
AXD12-RS (AUDIX Reserve Slots)
AXD12-RS (AUDIX Reserve Slots)
See AXA12-RS (AUDIX Reserve Slots) on page 563.
Issue 3 February 2007
565
Communication Manager Maintenance Object Repair Procedures
BRI-BD (ISDN-BRI Line Circuit Pack)
MO Name in Log
Alarm Level
Initial Command to Run
Full Name of MO
BRI-BD
MAJ
MIN
WNR
test board location l
ISDN-BRI Line circuit pack
LGATE-BD
MAJ
MIN
test board location l
LAN Gateway
WRN
(See Caution)
test board location
! CAUTION:
CAUTION:
A detailed flowchart for isolating and resolving Packet Bus faults is included in
Isolating and repairing packet-bus faults in Maintenance Procedures for Avaya
Communication Manager 4.0, Media Gateways and Servers, 03-300432. This
flowchart, along with the other information presented in the chapter, can help in
resolving problems that involve more than a single station or circuit pack.
Whenever the repair procedures for this Maintenance Object refer to Packet Bus
and/or Packet Control maintenance, be sure to see Isolating and repairing
packet-bus faults. See also PKT-BUS (Packet Bus) for repair procedures.
Error log entries and tests also apply to LGATE-BD.
This section relates to the TN556 ISDN BRI, TN2198 ISDN BRIU, TN2208 Ethernet,
(LGATE)-Ethernet Multifunction (MFB) circuit packs.
The TN2208 LGATE MFB provides the system with the interface to Adjunct-Switch Application
Interface (ASAI) and Avaya adjuncts (for example, CONVERSANT® Voice System). This circuit
pack contains 12 ports for line circuit interface (although only 8 are usable by the switch), each
of which operates with two B channels and 1 D channel. In this context, the term “ISDN-BRI
port” is used to refer to ports on the TN2208 MFB circuit pack that are connected to ASAI or
Avaya adjuncts. The TN2208 LGATE MFB is handled by the switch software as if it is an
ISDN-BRI compatible board, and every maintenance action referring to ASAI and Avaya adjunct
links in this section applies.
The TN556, TN2198, and TN2208 ISDN-BRI Lines are packet port circuit packs that provides
access to ISDN-BRI endpoints. The ISDN-BRI Line circuit packs supports 12 ports, each of
which provides access to ISDN stations. Voice and circuit-switched data from the ISDN stations
are carried on the Time Division Multiplex (TDM) Bus. Signaling is carried over the packet bus.
566 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
BRI-BD (ISDN-BRI Line Circuit Pack)
Error log entries and recommended actions
Table 153: BRI-BD Error Log Entries
Error
Type
Aux Data
Associated Test
Alarm
Level
On/Off
Board
Recommended Action
0 (a)
0
Any
Any
Any
test board location
1(b)
Any
None
MIN
ON
18(c)
0
busyout board
location
WRN
OFF
23(d)
0
None
WRN
OFF
257(e)
65535
Control Channel
Looparound (#52)
MIN
ON
513(f)
4352 to
4357
769(g)
4358
1025(h)
4363
NPE Audit Test
(#50)
1293
1294 (i)
46088
to
46096
SAKI Sanity test
(#534)
MIN
ON
1537
1538 (j)
46082
MIN
ON
1793 (k)
46080
MIN
ON
1794 (k)
46094
MIN
ON
1795 (k)
46085
MIN
ON
MIN
OFF
2306 (k)
release board location
test board location r 20
LANBIC Receive
Parity Error
Counter test
(#595)
3330 (l)
46083
3840
(m)
4096 to
4101
3843 (n)
46097
3999 (o)
Any
None
Issue 3 February 2007
567
Communication Manager Maintenance Object Repair Procedures
Notes:
a. Error Type 0: Run the short test sequence first. If every test passes, run the long test
sequence. Refer to each appropriate test’s description, and follow its recommended
procedures.
b. Error Type 1: the circuit pack totally stopped functioning or it was physically removed from
the system. 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. Or, if the circuit pack is in the system and the red LED is on,
follow the instructions for “Red (alarm)” in Circuit Pack LEDs on page 283.
c. Error Type 18: This circuit pack has been busied out via busyout board location.
d. Error Type 23: Port(s) has (have) been administered on this circuit pack but the circuit pack
is not physically present.
e. Error Type 257: transient communication problems between the switch and this circuit
pack. Execute test board location and see Control Channel Looparound Test
(#52) on page 1498 for the repair procedures.
f. Error Type 513: An on-board hardware failure has been detected by the circuit pack.
Aux Data 4352: External RAM error
Aux Data 4353: Internal RAM error
Aux Data 4355: ROM Checksum error
Aux Data 4357: Instruction set error
Reset the circuit pack by executing busyout board location and reset board
location. When it is reset, the circuit pack executes a set of tests to detect the presence
of any of the above faults. The detection of one of these errors during initialization causes
the circuit pack to lock-up and appear insane to the system. See the repair procedure in
footnote (a) for error type 1.
g. Error Type 769: reported by the circuit pack when it detects a program logic error. No action
is required, but this error may lead to errors of other types being reported against this circuit
pack.
h. Error Type 1025: reported by the circuit pack when it cannot update NPE memory and read
it back. No action is required, but this error may lead to errors of other types being reported
against the circuit pack.
i. Error Type 1293, 1294: a critical hardware failure has been detected on the circuit pack.
Error Type 1293: On-board auxiliary processor insane.
Error Type 1294: Internal memory access error.
Reset the circuit pack via busyout board location and reset board location. If
the Circuit Pack Restart Test (#594) passes, then the on-board circuitry is healthy. Retire the
alarm via test board location long clear. If the Circuit Pack Restart test (#594)
fails, replace the circuit pack.
568 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
BRI-BD (ISDN-BRI Line Circuit Pack)
j. Error Type 1537: Frame overrun at packet-bus interface. This condition may be caused by
an on-board fault or by faulty data received on one of the circuit pack’s external ports. If any
of the ports on this circuit pack are alarmed, refer to the repair procedures for those MOs.
Error Type 1538: Circuit packet is hyperactive; that is, it is flooding the switch with
messages sent over the control channel. The circuit pack is taken out-of-service when a
threshold number of these errors is reported to the switch. Clear the alarm with busyout
board location, reset board location, test board location long clear,
release board location. If the error recurs within 10 minutes, then replace the circuit
pack.
k. Error Type 1793, 1794, 1795, 2306: the circuit pack is having problems transmitting data to
the packet bus.
Error Type 1793: Parity errors are detected when transmitting data to the packet bus.
Error Type 1794: Overflow of packet-bus transmit buffers has occurred.
Error Type 1795: Circuit pack cannot find end of frame when transmitting to packet bus.
Clear the alarm via the following commands: busyout board location, reset board
location, test board location long clear, release board location. If the
error recurs within 10 minutes, then replace the circuit pack.
Error Type 2306: This error occurs when the circuit pack detects an error in a received
frame from the packet bus. These errors are most likely caused by a packet-bus problem,
but may be due to a circuit pack fault. An invalid Link Access Procedure Data (LAPD) frame
error occurs if the frame contains a bad cyclical redundancy check (CRC), is greater than
the maximum length, or violates the link level protocol. When bus parity errors are reported,
the LANBIC Receive Parity Error Counter test (#595) should be performed to determine
whether the condition had cleared. See Isolating and repairing packet-bus faults in
Maintenance Procedures for Avaya Communication Manager 4.0, Media Gateways and
Servers, 03-300432 to determine whether the problem is isolated to this circuit pack or is
caused by packet-bus faults.
l. Error Type 3330: 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 or to an on-board fault. If the
packet bus is alarmed, see PKT-BUS (Packet Bus) and Isolating and repairing packet-bus
faults in Maintenance Procedures for Avaya Communication Manager 4.0, Media Gateways
and Servers, 03-300432 for recommended repair procedures. The probability of this error
being related to packet-bus problems increases with the number of ISDN-BRI circuit packs
displaying this error.
If the packet bus is not alarmed, reset the circuit pack with busyout board location
and reset board location. If the Circuit Pack Restart Test (#594) passes, then the
on-board circuitry is healthy. Retire the alarm with test board location long clear.
If the Circuit Pack Restart test (#594) fails, replace the circuit pack. If the problem persists
after complying with the above instructions, then follow normal escalation procedures.
m. Error Types 4096, 4097, 4098, 4099, 4100, 4101: reported by the circuit pack when it
receives a bad control channel message from the switch. Not service-affecting, no action is
required. The auxiliary data identifies the error events.
Error Type 4096: Bad major heading
Error Type 4097: Bad port number
Error Type 4098: Bad data
Issue 3 February 2007
569
Communication Manager Maintenance Object Repair Procedures
Error Type 4099: Bad sub-qualifier
Error Type 4100: State inconsistency
Error Type 4101: Inconsistent downlink message
n. Error Type 3843: bad translation RAM detected, but call continues by using another
translation location. This error is not service-affecting. No action is required.
o. Error Type 3999: the circuit pack sent a large number of control channel messages to the
switch in a short period of time.
If Error Type 1538 is also present, the circuit pack was taken out-of-service due to
hyperactivity.
If Error Type 1538 absent, the circuit pack was not taken out-of-service, but has generated
50% of the messages necessary to be considered hyperactive. This may be normal during
heavy traffic periods. If traffic is light, it may indicate a problem with the circuit pack or the
equipment attached to it.
Demand test descriptions and error codes
Investigate tests in the order presented. By clearing errors associated with the first test, errors
generated from other tests may also be cleared. Click on the link to see the full description of
the test, error codes, and recommended actions.
Short Test
Sequence
Long Test
Sequence
D/ND1
X
X
ND
NPE Audit Test (#50)
X
ND
LANBIC Receive Parity Error Counter Test (#595)
X
ND
Order of Investigation
Control Channel Looparound Test (#52)
1. D = Destructive; ND = Nondestructive
570 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
BRI-DAT (ISDN-BRI Data Module)
BRI-DAT (ISDN-BRI Data Module)
MO Name
in Log
Alarm Level
Initial Command to Run
Full Name of MO
BRI-DAT
WRN1
test data-module extension
ISDN-BRI Stand-alone
Data Module
1. The alarm level for ASAI or Avaya adjuncts may be administered using set options. The alarm level can
be set independently for on- and off-board alarms to WARNING, MINOR, or MAJOR for every ASAI
adjunct in the system.
See BRI-SET, Various Adjuncts on page 579.
Issue 3 February 2007
571
Communication Manager Maintenance Object Repair Procedures
BRI-PORT (ISDN-BRI Port)
MO Name in
Log
Alarm
Level
Initial Command to Run
Full Name of MO
BRI-PORT
MIN
test port location l
ISDN-BRI port
WRN
test port location
ABRI-POR
MAJ 1
WRN 1
test port location l
ASAI ISDN-BRI port
ATT-PORT
MAJ 1
WRN 1
test port location l
Avaya Adjunct ISDN-BRI port
LGATE-PT
MAJ 1
WRN 1
test port location l
Ethernet ASAI port
ATTE-PT
MAJ 1
WRN 1
test port location l
Ethernet Avaya Adjunct port
1. Major alarms may be downgraded to Warning alarms based on the value used in set options.
! CAUTION:
The section, Isolating and repairing packet-bus faults in Maintenance Procedures
for Avaya Communication Manager 4.0, Media Gateways and Servers,
03-300432, along with the other information presented in the chapter, can help
resolve problems involving more than one station or circuit pack.
CAUTION:
!
WARNING:
WARNING:
If a significant packet-bus failure occurs, errors and alarms may not be logged as
expected for BRI-PORT/ABRI-POR/ATT-PORT/ LGATE-PT/ ATTE-PT.
Conditions under which this occurs are detailed in Isolating and repairing
packet-bus faults in Maintenance Procedures for Avaya Communication Manager
4.0, Media Gateways and Servers, 03-300432.
The TN2208 LGATE MFB provides Communication Manager with the interface to
Adjunct-Switch Application Interface (ASAI) and Avaya adjuncts (for example, CONVERSANT®
Voice System). The circuit pack contains 12 ports of line circuit interface (although only 8 are
usable by the switch), each of which operates with two B channels (referred to as B1 and B2
throughout this section) and one D channel. In this context, the term “ISDN-BRI port” is used to
refer collectively to ports on the TN2208 circuit pack that are connected to ASAI or Avaya
adjuncts.
572 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
BRI-PORT (ISDN-BRI Port)
The TN556 and TN2198 ISDN-BRI Line circuit packs provide the system with the interface to
ISDN-BRI endpoints, Adjunct-Switch Application Interface (ASAI) and Avaya 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. In this context, the term “ISDN-BRI port” is used to refer collectively
to ports on the TN556 an TN2198 circuit packs that are connected to either BRI endpoints, ASAI
or Avaya adjuncts.
For BRI endpoints, each B channel may support voice or circuit-switched data and may be
circuit-switched simultaneously. The B channels are not used on ports connected to ASAI or
Avaya adjuncts. The D channel is used for conveying signaling between the switch and a BRI
endpoint(s), ASAI or Avaya adjunct. Each ISDN-BRI D channel is connected to the switch
processor and the ISDN-BRI port through the packet bus.
ISDN-BRI endpoints are available in various configurations. Every endpoint requires the D
channel to convey signaling information to the switch. Only one B channel is required for a
voice-only set or a stand-alone data module (BRI-DAT). A voice and data-capable set requires
both B channels (one for voice and one for data). Therefore, each TN556 or TN2198 port can
support either two voice-only sets, two stand-alone data modules (BRI-DAT), or one voice and
data-capable set. Only a single ASAI or Avaya adjunct may be connected to an ISDN-BRI port.
Multiple adjuncts per line are not supported.
Figure 39: ISDN-BRI Port Interactions on page 574 illustrates the physical connection (solid
line) between an ISDN-BRI port and its associated ISDN-BRI set(s). Each physical connection
allows for two B channels and one D channel. Each ISDN-BRI circuit pack can support up to 12
of these physical connections to different voice and voice/data sets or ASAI or Avaya adjuncts.
On a TN2198 each ISDN-BRI circuit pack can support up to 12 physical connections to a NT1
which in turn connects to 2 terminals.
This section covers the maintenance documentation for ISDN-BRI ports. Some of the results of
maintenance testing of ISDN-BRI ports may be affected by the health of the ISDN-BRI Line
circuit pack (BRI-BD), BRI endpoint (BRI-SET), or ASAI adjunct (ASAI-ADJ/LGATE-ADJ/
LGATE-AJ) or Avaya adjunct (ATT-ADJ/ATTE-AJ). These interactions should be kept in mind
when investigating the cause of ISDN-BRI port problems. For more information about the circuit
pack, see:
●
BRI-BD (ISDN-BRI Line Circuit Pack) on page 566
●
BRI-SET, Various Adjuncts on page 579
and for more information about its endpoints, see:
●
ASAI-ADJ (ASAI Adjunct) on page 459
●
ATT-ADJ (Avaya Adjunct) on page 555
●
LGATE-AJ (Ethernet ASAI Endpoint) on page 922
Issue 3 February 2007
573
Communication Manager Maintenance Object Repair Procedures
Figure 39: ISDN-BRI Port Interactions
Switch
BRI line
circuit pack
Port
Voice or
data terminal
D-channel
B-channel
B-channel
Voice or
data terminal
Logical connection
Physical connection
bripor1 LJK 072501
Error log entries and recommended actions
Table 154: BRI-PORT Error Log Entries 1 of 2
Error
Type
Aux
Data
Associated Test
Alarm
Level for
BRI-PORT
Alarm
Level for
ABRI-PORT
ATT-PORT
LGATE-PT
ATTE-PT
On/Off
Board
Recommended Action
0 (a)
0
Any
Any
Any
Any
test port PCSSpp
1(b)
Level 1 Status
Inquiry (#621)
WRN
Any1
OFF
test port PCSSpp r 2
18
busyout port
PCSSpp
WRN
OFF
release port PCSSpp
WRN
ON
test port PCSS
test port PCSSpp
130(c)
257(d
EPF Inquiry (#622)
WRN
Any1
OFF
513(e)
46222
none
(d)
(d)
ON
769(f)
0
none
WRN
MAJ
OFF
1 of 2
574 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
BRI-PORT (ISDN-BRI Port)
Table 154: BRI-PORT Error Log Entries 2 of 2
Error
Type
Aux
Data
1281(g)
46210
1537(h)
1793(i)
Associated Test
Alarm
Level for
BRI-PORT
BRI NPE Crosstalk
(#617)
MIN
WRN1
CRC Error
Counter (#623)
WRN
BRI Port Local
TDM Looparound
(#619)
MIN
WRN1
3841(j
46208
None
3842(k)
0
None
3843(l)
0
None
3844(m)
46223
None
3845(n)
Alarm
Level for
ABRI-PORT
ATT-PORT
LGATE-PT
ATTE-PT
Any1
On/Off
Board
Recommended Action
ON
test port PCSSpp l r 2
OFF
ON
test port PCSSpp l r 2
None
3846(o)
TEI
None
3847(p)
0
None
2 of 2
1. Major and Minor alarms on this MO may be downgraded to Warning alarms based on the value used in set
options.
Notes:
a. Error Type 0: Run the short test sequence first. If every test passes, run the long test
sequence. Refer to each appropriate test’s description, and follow its recommended
procedures.
b. Error Type 1: the Level 1 Status Inquiry fails or when the BRI circuit pack detects that Level
1 has been deactivated on the port. Refer to the repair procedures for Test #621.
Aux Data blank: the Level 1 Status Inquiry failed.
Aux Data 32773: message from the BRI-LINE circuit pack indicating Level 1 has been
deactivated.
c. Error Type 130: 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.
d. Error Type 257: 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. The aux data field
contains one of the following values:
●
blank – This indicates that the EPF Status Inquiry failed due to an overcurrent condition.
Issue 3 February 2007
575
Communication Manager Maintenance Object Repair Procedures
●
40988 – This indicates that the BRI-LINE circuit pack has detected an overcurrent
condition and has turned the EPF off.
Execute the short test sequence, and see the repair procedures for Test #622.
e. Error Type 513: the circuit pack is having problems transmitting data to the packet bus,
thus affecting the conveyance of signaling information over the D channel. With Aux Data
46222, this error occurs when the packet-bus transmit buffers overflow. This condition
probably indicates a hardware problem. The BRI-PORT Alarm Level for the error with Aux
Data 46222 is “MINOR/WARNING,” and the ABRI-PORT/ATT-PORT/LGATE-PT/ATTE-PT
Alarm Level is “MAJOR/MINOR/WARNING.” With Aux Data 0, this error occurs whenever
the packet-bus transmit FIFO buffers overflow. This condition can be caused by an
on-board hardware problem as well as by problems on the packet bus that disrupt the BRI
circuit pack’s ability to transmit data onto the packet bus. Use troubleshooting procedures
for both on-board hardware problems and potential off-board packet-bus problems. See
PKT-BUS (Packet Bus) on page 1065 as well as Isolating and repairing packet-bus faults in
Maintenance Procedures for Avaya Communication Manager 4.0, Media Gateways and
Servers, 03-300432 for more information about troubleshooting the packet bus. The
BRI-PORT Alarm Level for the error with Aux Data 0 is “MINOR,” and the ABRI-PORT/
ATT-PORT/LGATE-PT/ATTE-PT Alarm Level is “MAJOR.”
f. Error Type 769: the BRI NPE Crosstalk Test (#617) fails. Run the long test sequence, and
note the results of Test #617.
g. Error Type 1281: a port’s associated broadcast-signaling links have too much traffic related
to link establishment. This could occur if an endpoint on this port is sending link
establishment traffic on a port level broadcast link or if there are Level 1 problems on the
port. Check the error logs for Level 1 errors. If Level 1 problems exist, follow the repair
procedures listed for Test #621. Software will suspend activity to this port for 75 minutes
when the port is alarmed due to this error (note that service suspension does not occur if
the port is an ABRI-PORT/LGATE-PT/ATTE-PT/ATT-PORT). If this problem persists,
replace the endpoint or endpoints associated with this port. If replacing the endpoints does
not fix the problem, follow normal escalation procedures.
h. Error Type 1537: 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. If five more CRC errors are received within 15 minutes of the last
five, the port is taken out of service for 15 minutes.
This error is most likely due to a problem with the wiring to the set or adjunct, interference
on the wiring due to a noise source, or no termination (an open circuit). It usually does not
indicate a problem with the circuit pack.
●
Check the wiring to the endpoints or the adjunct.
●
If the problem persists, replace the endpoints or adjuncts, or escalate the problem.
576 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
BRI-PORT (ISDN-BRI Port)
i. Error Type 1793: the BRI Port Local TDM Looparound Test (#619) fails. Run the long test
sequence, and note the results of Test #619.
There are no recommended actions for the following error types. The error types are simply
provided as additional data that may prove useful while troubleshooting.
j. Error Type 3841: a Layer 1 Transmission error is detected for the port. Run the long test
sequence, and note the results of the Layer 1 Transmission Error Counter Test (#624).
k. Error Type 3842: A BRI port supports up to three Terminal Endpoint Identifiers (TEIs). This
error occurs when the switch receives a request for a fourth TEI on a port. Check the
number of endpoints administered for this port.
l. Error Type 3843: a SPID initialization request is made from an endpoint and the switch
determines that the SPID value is invalid or is a duplicate of another SPID that is already
initialized at Layer 3 on the port. Check the administration of the endpoints.
m. Error Type 3844: the circuit pack detects an overflow of its receive buffers. Run the long
test sequence, and note the results of the Receive FIFO Error Counter Test (#625).
n. Error Type 3845: the BRI Port Local LAN Looparound Test (#618) fails. Run the long test
sequence, and note the results of Test #618.
o. Error Type 3846: most likely occurs when the Terminal Endpoint Identifier (TEI)
administered for the ASAI or Avaya endpoint does not match the TEI administered in the
ASAI or Avaya adjunct. Check the switch administration of the TEI against that of the
adjunct and make sure that both are using the same TEI.
p. Error Type 384: sets on the port do not support layer-3 initialization. Consult the Service
Set documentation.
Demand test descriptions and error codes
Investigate tests in the order presented. By clearing errors associated with the first test, errors
generated from other tests may also be cleared. Click on the link to see the full description of
the test, error codes, and recommended actions.
Long Test
Sequence
D/ND1
BRI NPE Crosstalk Test (#617)
X
D
BRI Port Local LAN Looparound Test (#618)
X
D
BRI Port Local TDM Looparound Test (#619)
X
D
X
ND
Order of Investigation
Electronic Power Feed Restoral Test (#620)
Short Test
Sequence
X
1 of 2
Issue 3 February 2007
577
Communication Manager Maintenance Object Repair Procedures
Short Test
Sequence
Long Test
Sequence
D/ND1
Level 1 Status Inquiry Test (#621)
X
X
ND
Electronic Power Feed Inquiry (#622)
X
X
ND
CRC Error Counter Test (#623)
X
ND
Layer 1 Transmission Error Counter Test (#624)
X
ND
Receive FIFO Error Counter Test (#625)
X
ND
X
ND
Order of Investigation
Clear Error Counters (#270)
X
2 of 2
1. D = Destructive; ND = Nondestructive
578 Maintenance Alarms for Avaya Communication Manager 4.0, Media Gateways and Servers
BRI-SET, Various Adjuncts
BRI-SET, Various Adjuncts
MO Name in Log
Alarm
Level
Initial Command to Run
Full Name of MO
BRI-SET
WRN1
test station extension l
ISDN-BRI Set
BRI-DAT
WRN1
test data-module extension l
ISDN-BRI Data Module
ASAI-ADJ
MAJ1
test station extension
test data-module extension
ASAI-Adjunct
WRN2
test data-module extension
ATT-ADJ
MAJ1
WRN2
test station extension
Avaya-Adjunct
LGATE-AJ
MAJ1
WRN2
test station extension
Ethernet ASAI-Adjunct
ATTE-AJ
MAJ1
WRN2
test station extension
Ethernet Avaya-Adjunct
1. The alarm level for ASAI and Avaya adjuncts may be administered using set options. The alarm level can
be set independently for on- and off-board alarms to WARNING, MINOR, or MAJOR for every ASAI and
Avaya adjunct in the system.
2. Alarming for an ASAI and Avaya adjuncts is disabled if the adjunct asks the switch to suspend
maintenance. When this occurs, an error and a WARNING alarm are logged against the endpoint. Busying
out and releasing the ASAI station or ADDLE station will clear the alarm.
!
WARNING:
!
WARNING:
WARNING:
Information for isolating and resolving packet-bus faults is included in Isolating
and repairing packet-bus faults in Maintenance Procedures for Avaya
Communication Manager 4.0, Media Gateways and Servers, 03-300432. The
Troubleshooting Packet Bus Problems flowchart, along with the other information
presented in the chapter, can help resolve problems that involve more than a
single station or circuit pack.
WARNING:
If a significant packet-bus failure occurs, errors and alarms may not be logged as
expected for BRI-PORT/ABRI-POR/ATT-PORT/ LGATE-PT/ ATTE-PT.
Conditions under which this occurs are detailed in the Isolating and repairing
packet-bus faults in Maintenance Procedures for Avaya Communication Manager
4.0, Media Gateways and Servers, 03-300432.
The TN2208 ESAI MFB provides the system with an Ethernet interface to Adjunct-Switch
Application Interface (ASAI) and Avaya adjuncts (for example, CONVERSANT® Voice System).
This circuit pack contains 8 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. In this context,
Issue 3 February 2007
579
Communication Manager Maintenance Object Repair Procedures
the term ``ISDN-BRI port'' is used to refer collectively to ports on the TN2208 MFB circuit pack
that is connected to ASAI or Avaya adjuncts. The TN2208 ESAI MFB is handled by switch
software as it is an ISDN BRI compatible board and every maintenance action referring to ASAI
and Avaya Adjunct Links in this section applies.
Two types of ISDN-BRI endpoints may be connected to ISDN-BRI (ISDN Basic Rate Interface
Line) TN556 and TN2198 circuit packs: ISDN-BRI station endpoints, ASAI (Adjunct-Switch
Application Interface) and Avaya adjuncts (for example CONVERSANT® Voice System). These
circuit packs contain 12 ports of line circuit interfaces, each of which operates at 192 kilobits per
second (kbps) with two B channels and one D channel. For BRI endpoints, each B channel may
support voice or circuit-switched data and may be circuit-switched simultaneously. The B
channels are not used by ASAI or Avaya adjuncts. The D channel is used for conveying
signaling between the switch and a BRI endpoint(s) or ASAI or Avaya adjuncts. Each ISDN-BRI
D channel is connected to the switch processor and the ISDN-BRI port through the PKT-BUS
(packet bus).
ISDN-BRI endpoints come in a number of configurations. Every endpoint requires the D
channel to convey signaling information to the swi