Server Alarms - Avaya Support

Communication Manager Maintenance Object Repair Procedures
Table 245: Encoding of Error Codes for Software Requested IPSI interchange 2 of 2
Field Variable Name Value Description
x Control (Archangel)
pre and post action
y Fault class/stimulus
causing software
action
z Fault or
improvement
AUX Data Descriptions
0 Control on IPSI before and after the interchange.
1 Not in IPSI control before and after the interchange.
2 Control leaves IPSI.
3 Control moves to IPSI.
1 EAL fault class
2 PKT-INT fault class
3 TONE-BD fault class (not TDM-CLK)
4 TDM-CLK fault class (loss of clock)
7 Preference migration to A-side IPSI
0 This is an improvement in the previous fault class (y).
1 This is a degradation of the previous fault class (y).
Table 246: Aux Data Descriptions for Software-Requested Interchange
Aux Data Description
0 No specific extra information is available
1 An IPSI interchange only took place
2 A control change only took place
3 Both an IPSI interchange and a control change took place
Examples:
Error Code of 30320 with Aux Data 2 software requested the archangel move to the A-side IPSI
as a result of a PKT-INT fault class improvement.
Error Code of 31041 with Aux Data 1 indicates a software requested interchange from the
A-side IPSI to the B-side IPSI leaving the archangel on the IPSI due to a loss of TDM clock.
904 Maintenance Alarms for Avaya Communication Manager, Media Gateways and Servers
2 of 2