Demand test descriptions and error codes - Avaya Support

● Be physically inserted into the correct slot
If the circuit pack has an entry on the circuit pack screen and any of the other conditions
are not met, a MINOR alarm is logged. To resolve the error:
● Make sure every condition for administration is met, and that a functioning Media
Resource is inserted in the correct slot.
● Completely remove the IP Media Resource from the system:
a. Remove the administered IP-Interface associated with the circuit pack.
b. Physically remove the circuit pack from the slot.
b. Error Type 10012: Simplex mode downlink. The reason for the state interchange to active
was a Simplex mode downlink to the circuit pack. When the board is inserted and before it
is used for any bearer traffic, the server configures the board to operate either in Simplex or
Duplex mode via a downlink message. That operation may trigger the interchange.
c. Error Type 10021 and 10022: Duplex mode downlink. The reason for the state interchange
(active/standby) was a Duplex mode downlink to the circuit pack. When the board is
inserted and before it is used for any bearer traffic, the server configures the board to
operate either in Simplex or Duplex mode via a downlink message. That operation may
trigger the interchange.
d. Error Type 10031 and 10032: Demand interchange. A demand interchange caused the
state change (active/standby) in response to the set media-processor command.
e. Error Type 10041 and 10042: Free token. The reason for the interchange (active/standby)
was that the standby circuit pack detected the availability of a token. Boards operating in
duplex mode arbitrate to determine which will be the active board. A hardware-supported
soft token supports this operation. The standby circuit pack monitors the token and initiates
an interchange if the peer has ceased to be the active board.
f. Error Type 10051 and 10052: Abdicate Request. The state interchange (active/standby)
was caused by the board receiving a request to give up the active state. Boards operating in
duplex mode exchange health information and other details of duplicated operation. If the
standby board determines it must become the active board because it was commanded to
do so or because the active board is less healthy than the standby, the standby board sends
an abdicate request to the active board.
g. Error Type 10061 and 10062: Abdicate Received. The state interchange (active/standby)
was caused by the standby board receiving a notification that the other board was leaving
the active state. As part of normal operation, the boards monitor their components and
internal state to verify their ability to perform their function. If the board determines it can no
longer fulfill the requirements of being the active board, or because it was commanded to do
so, it will send an abdicate notification to the standby board.
h. Error Type 10110: The board was configured by CM software to be duplicated but the
firmware version of the board does not have this capability. Upgrade the board firmware.
i. Error Type 10991 and 10992: Transient Error. The state interchange (active/standby) was
caused by a fault condition that was cleared by the time the state transition was complete.
614 Maintenance Alarms for Communication Manager, Media Gateways and Servers