Server Alarms - Avaya Support

Communication Manager Maintenance Object Repair Procedures
Table 205: EXP-INTF Error Log Entries 3 of 3
Error Type Aux
Data 1
2817 (n) Any MIN ON
3073 (o) Any EI Packet Interface
test (#589)
MAJ OFF test board location r 3
3074 (p) 2 EI Packet Interface
test (#589)
MAJ OFF test board location r 3
3075 (p) 1 EI Packet Interface
test (#589)
MAJ OFF test board location r 3
3076 EI Packet Interface
test (#589)
MAJ OFF test board location r 3
3330 (q) Any WRN ON
3585 (r) 0 WRN OFF
3841(t,v) Any MIN OFF (s)
3842(u,v) Any MIN OFF (s)
10001
(w)
0
Associated Test Alarm
Level
On/Off
Board
Recommended Action
1. Aux Data 32767 for any error log entry indicates that an alarmed EI was busied out and then released.
When this occurs, existing service affecting alarms must be preserved. As is typical, when the EI is
released every alarm is resolved. Therefore the alarm and error logs must be repopulated with the alarms
present at time of busyout. This error code is an indication that existing aux data and error log time stamps
are no longer valid because they were lost when the alarms were resolved upon release of the circuit
pack.
2. 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.
Notes:
a. Error Type 18: the EI circuit pack has been busied out via busyout board location. To
resolve this error, release the EI circuit pack via release board location.
b. Error Type 23: the EI circuit pack has been administered on the Circuit Pack screen, but
has not been physically inserted into the system. Insert the circuit pack.
c. Error Type 125: A different circuit pack occupies the slot where this circuit pack is logically
administered. To resolve this problem, either:
1. Replace the incorrect circuit pack with the logically assigned circuit pack.
818 Maintenance Alarms for Avaya Communication Manager, Media Gateways and Servers
3 of 3