09.12.2012 Views

Server Alarms - Avaya Support

Server Alarms - Avaya Support

Server Alarms - 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 />

t. Error Type 20300 – 20363: a spontaneous PNC interchange took place in response to the<br />

retiring of an alarm on the B-PNC associated with fault class FC_PER. Use status pnc to<br />

look at the state of health indexes for the PNCs, and investigate any associated alarms.<br />

Adding 1 to the last two digits of the Error Code gives the PN number of the port network<br />

that reported the retired alarm. (20303 points to port network 4.) Use list config<br />

port-network to show the cabinet number associated with a port network.<br />

u. Error Type 20400 – 20463: a spontaneous PNC interchange took place in response to the<br />

retiring of an alarm on the B-PNC associated with fault class FC_DS1. Use status pnc to<br />

look at the state of health indexes for the PNCs, and investigate any associated alarms.<br />

Adding 1 to the last two digits of the Error Code gives the PN number of the port network<br />

that reported the retired alarm. (20403 points to port network 4.) Use list config<br />

port-network to show the cabinet number associated with a port network.<br />

v. Error Type 20500 – 20563: a spontaneous PNC interchange took place in response to the<br />

retiring of an alarm on the B-PNC associated with fault class FC_BFD. Use status pnc to<br />

look at the state of health indexes for the PNCs, and investigate any associated alarms.<br />

Adding 1 to the last two digits of the Error Code gives the PN number of the port network<br />

that reported the retired alarm. (20203 points to port network 4.) Use list config<br />

port-network to show the cabinet number associated with a port network.<br />

w. Error Type 20600 – 20664: a spontaneous PNC interchange took place in response to the<br />

retiring of an alarm on the B-PNC associated with fault class FC_SNIL. Use status pnc to<br />

look at the state of health indexes for the PNCs, and investigate any associated alarms. The<br />

last two digits of the Error Code indicate the fiber-link number (01-27) of the fiber that<br />

reported the retired alarm. Use list fiber-link to show the location of the fiber.<br />

x. Error Type 20700 – 20764: a spontaneous PNC interchange took place in response to the<br />

retiring of an alarm on the B-PNC associated with fault class FC_SNIHW. Use status pnc<br />

to look at the state of health indexes for the PNCs, and investigate any associated alarms.<br />

The last two digits of the Error Code indicate the fiber-link number (01-27) of the fiber that<br />

reported the retired alarm. Use list fiber-link to show the location of the fiber.<br />

y. Error Type 21000-21063: a spontaneous PNC interchange took place in response to the<br />

occurrence of a major or minor alarm on the B-PNC associated with fault class FC_EAL.<br />

This indicates that one or more Expansion Archangel Links are down. Investigate any<br />

EXP-PN alarms. Adding 1 to the last two digits of the Error Code gives the PN number of<br />

the port network that reported the alarm. (21003 points to port network 4.) Use list<br />

config port-network to show the cabinet number associated with a port network.<br />

z. Error Type 21100-21163: a spontaneous PNC interchange took place in response to the<br />

occurrence of a major or minor alarm on the B-PNC associated with fault class FC_INL.<br />

This indicates that one or more neighbor or indirect neighbor links with an EI as an endpoint<br />

have experienced faults. Investigate any alarms against EXP-PN and SN-CONF. Adding 1<br />

to the last two digits of the Error Code gives the PN number of the port network that<br />

reported the alarm. (21103 points to port network 4.) Use list config port-network<br />

to show the cabinet number associated with a port network.<br />

1132 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!