19.12.2012 Views

Demand test descriptions and error codes - Avaya Support

Demand test descriptions and error codes - Avaya Support

Demand test descriptions and error codes - Avaya Support

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Communication Manager Maintenance Object Repair Procedures<br />

2. A similar relationship exists for the PN Archangel (EAA - the active ATM-EI) <strong>and</strong> certain<br />

TDM-bus problems. If the EAA is unable to communicate with a port board over the TDM<br />

bus, either the EAA has a fault, the port board has a fault, or there is a problem with the<br />

TDM bus itself. If TDM bus maintenance <strong>test</strong>s find no problems with the bus, then it is<br />

either the port board or the EAA. It may be simpler to replace the port board than to<br />

request a PNC interchange. However, if it is not clear which port board may be at fault or<br />

maintenance is being performed remotely, verify that the EAA is not at fault by executing a<br />

PNC interchange. If the interchange solves the problem, then the EAA is faulty. If the<br />

problem persists after the interchange, but TDM bus maintenance finds no problem, then<br />

the port board is faulty.<br />

Error Log Entries<br />

Whenever a PNC interchange takes place, an <strong>error</strong> is logged against PNC-DUP with a code<br />

that conveys information about the cause of the interchange <strong>and</strong> which PNC became active.<br />

There are no alarms associated with PNC-DUP <strong>error</strong>s, but there should be an alarm against the<br />

PNC component that caused the interchange. There are no PNC-DUP <strong>test</strong> sequences, but<br />

status pnc provides information regarding the status of the PNCs. The information in<br />

Table 44: Error Code <strong>descriptions</strong> <strong>and</strong> Aux Data correlations <strong>and</strong> Table 45: Error Log Encode<br />

Field Decoding can help to identify which areas of the Alarm Log to investigate to find the<br />

source of the problem.<br />

Table 44: Error Code <strong>descriptions</strong> <strong>and</strong> Aux Data correlations<br />

Error<br />

Code<br />

Description Aux Data 1<br />

00000 Error in generating <strong>error</strong> code None<br />

1cxpp Spontaneous Interchange in response to a constraint for A-PNC Active PNC<br />

2cxpp Spontaneous Interchange in response to a constraint for B-PNC Active PNC<br />

51000 Spontaneous Interchange at expiration of SOH validation timer Active PNC<br />

52000 Spontaneous Interchange upon PNC UNLOCK Active PNC<br />

53000 Spontaneous Interchange at completion of Global Refresh Active PNC<br />

60801 PNC <strong>Dem<strong>and</strong></strong> Interchange Active PNC<br />

60800 PNC <strong>Dem<strong>and</strong></strong> Interchange with override Active PNC<br />

1. The Aux Data indicates which PNC became active after the PNC interchange: “0” denotes PNC-A; “1”<br />

denotes PNC-B.<br />

168 Maintenance Alarms for Communication Manager, Media Gateways <strong>and</strong> Servers

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!