09.12.2012 Views

Server Alarms - Avaya Support

Server Alarms - Avaya Support

Server Alarms - Avaya Support

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Communication Manager Maintenance Object Repair Procedures<br />

2. A similar relationship exists for the PN Archangel (EAA - the active ATM-EI) and 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 tests find no problems with the bus, then it is either<br />

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

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

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

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

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

board is faulty.<br />

Error Log Entries<br />

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

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

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

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

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

Table 140: Error Code descriptions and Aux Data correlations and Table 141: Error Log<br />

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

the source of the problem.<br />

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

Error<br />

Code<br />

Description Aux Data 1<br />

00000 Error in generating error 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 Demand Interchange Active PNC<br />

60800 PNC Demand 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 />

544 Maintenance <strong>Alarms</strong> for <strong>Avaya</strong> Communication Manager, Media Gateways and <strong>Server</strong>s

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

Saved successfully!

Ooh no, something went wrong!