Server Alarms - Avaya Support

Communication Manager Maintenance Object Repair Procedures
n. Error Type 3585-3839: Certain ASAI protocol-specific cause codes are logged by switch
software. The cause code can be determined from the following formula:
If the Error Type is greater than 3712, then the ASAI cause code is equal to the Error Type
minus 3712. This code was sent to the adjunct by the switch.
If the Error Type is less than 3712, then the ASAI cause code is equal to the Error Type
minus 3584. This code was sent to the switch by the adjunct.
A description of the various ASAI cause values is contained in the Table 157: ASAI CAUSE
VALUES; (BRI-SET/ASAI-ADJ Error Log Entries Notes). This table also contains
recommended system technician actions associated with the cause value. In addition, the
Aux Data field of the Error Log entry contains additional diagnostic information additional
diagnostic.
Table 157: ASAI CAUSE VALUES; (BRI-SET/ASAI-ADJ Error Log Entries Notes) 1 of 2
Error
Code
Test Result Description / Recommendation
0 Unrecognized
ASAI Protocol
Operation
40 Resources not
available
63 SERVICE OR
OPTION NOT
AVAILABLE
Requested ASAI protocol operation is not implemented by the
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 the switch and the adjunct.
Adjunct administration turning off operations not implemented
by the switch may resolve the problem.
2. If step 1 does not resolve the problem, escalate to the next
tier.
No available internal resources to service switch or adjunct
request. System transaction capacity for adjunct or switch is
exceeded.
1. Re-engineering of adjunct services my be required. If problem
persists, escalate problem to the next tier.
Requested ASAI capability or resource is not available on the
switch or adjunct. More than one adjunct may be contending for the
same switch resources. 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
(e.g., requesting notifications on a single domain by multiple
adjuncts or 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 guarantee
that each adjunct is associated with a unique set of switch
resources.
2. If step 1 does not resolve the problem, escalate to the next
tier.
606 Maintenance Alarms for Avaya Communication Manager, Media Gateways and Servers
1 of 2