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

Table 535: SNI-BD Configuration Audit (#759) 4 of 6<br />

Error<br />

Code<br />

Test<br />

Result<br />

Description / Recommendation<br />

134 FAIL No neighbor link is administered, but the SNI has an SNI neighbor.<br />

1. Administer the SNI on a fiber link to the SNI neighbor it is connected<br />

to using add fiber-link next. Or remove both fiber endpoints<br />

(i.e., this SNI and its SNI neighbor) and remove the fiber endpoints<br />

from circuit pack administration using change circuit-pack.<br />

135 FAIL The SNI circuit pack cannot communicate with its neighbor. The SNI has<br />

an administered neighbor, but cannot communicate with its neighbor.<br />

1. Check if the administered neighbor is inserted. If not, insert the<br />

neighbor circuit pack.<br />

2. Perform the Fiber link fault isolation procedure in Maintenance<br />

Procedures (03-300432).<br />

136 FAIL The SIN’s administered neighbor does not match the physical neighbor<br />

connected. The type of neighbor administered is an SNI and the type of<br />

neighbor physically connected is an EI.<br />

1. Enter list fiber-link, and verify that the fiber-optic and metallic<br />

cable connections are installed as administered.<br />

137 FAIL The SNI’s administered neighbor does not match the physical neighbor<br />

connected. The type of neighbor administered is an EI and the type of<br />

neighbor physically connected is an SNI.<br />

1. Enter list fiber-link, and verify that the fiber-optic cable and<br />

metallic cable connections are installed as administered.<br />

138 FAIL The physical neighbor location does not match administered neighbor<br />

location. The carrier and slot of the administered neighbor do not match<br />

the carrier and slot of the physical neighbor.<br />

1. Enter list fiber-link, and verify that the fiber-optic cable and<br />

metallic cable connections are installed as administered.<br />

2. If the problem does not seem to be caused by a physical connection<br />

problem or an administration problem, replace the neighbor circuit<br />

pack. It is possible for the neighbor circuit pack to have a hardware<br />

problem that causes it to report a wrong Angel address (physical<br />

carrier/slot address) to software.<br />

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

4 of 6

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

Saved successfully!

Ooh no, something went wrong!