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.

PNC-DUP (PNC Duplication)<br />

m. Error Type 11300 – 11363: a spontaneous PNC interchange took place in response to the<br />

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

This indicates one or more faults on peer links that connect SNIs to EIs. Investigate any<br />

alarms against SNI-PEER. Adding 1 to the last two digits of the Error Code gives the PN<br />

number of the port network that reported the alarm. (11303 points to port network 4.) Use<br />

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

network.<br />

n. Error Type 11400 – 11463: a spontaneous PNC interchange took place in response to the<br />

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

This indicates faults on one or more DS1C facilities. Investigate any alarms against<br />

DS1-FAC. Adding 1 to the last two digits of the Error Code gives the PN number of the port<br />

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

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

o. Error Type 11601 – 11664: a spontaneous PNC interchange took place in response to the<br />

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

This indicates one or more faults on peer or neighbor links between SNIs on different switch<br />

nodes. Investigate any alarms against SNI-PEER. The last two digits of the Error Code<br />

indicate the fiber-link number of the fiber that reported the retired alarm. Use list<br />

fiber-link to show the location of the fiber.<br />

p. Error Type 11701 – 11764: a spontaneous PNC interchange took place in response to the<br />

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

This indicates one or more faults on hardware connecting SNIs on different switch nodes.<br />

Investigate any alarms against SN-CONF, SNI-BD, FIBER-LK. The last two digits of the<br />

Error Code indicate the fiber-link number of the fiber that reported the retired alarm. Use<br />

list fiber-link to show the location of the fiber.<br />

q. Error Type 20000 – 20063: a spontaneous PNC interchange took place in response to the<br />

retiring of an alarm on the B-PNC associated with fault class FC_EAL. 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. (20003 points to port network 4.) Use list config<br />

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

r. Error Type 20100 – 20163: a spontaneous PNC interchange took place in response to the<br />

retiring of an alarm on the B-PNC associated with fault class FC_INL. 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. (20103 points to port network 4.) Use list config<br />

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

s. Error Type 20200 – 20263: a spontaneous PNC interchange took place in response to the<br />

retiring of an alarm on the B-PNC associated with fault class FC_HW. 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 />

Communication Manager Release 5.0 Issue 4 January 2008 1131

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

Saved successfully!

Ooh no, something went wrong!