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

Before using this procedure, determine if more than one SNI is unable to communicate with<br />

software. Verify SNI and SNC circuit pack insertion using the list configuration<br />

carrier location where location is the cabinet and carrier location of a switch node<br />

carrier. Check for inserted SNIs and SNCs in every administered switch node carrier.<br />

If every SNI and SNC is not inserted, then “NO BOARD” is displayed for each board in the<br />

entire PNC (either the a-pnc or the b-pnc). The link between the IPSI connected PN’s EI (on the<br />

PNC where SNI and SNC circuit packs were not inserted) and the connected SNI does not<br />

function properly. If this applies:<br />

1. Run test board location on the IPSI connected PN’s EI, and fix any problems.<br />

2. Perform the Expansion Interface Manual Loopback Procedure for the IPSI connected PN’s<br />

EI.<br />

3. Perform the Switch Node Interface Manual Loopback Procedure for the SNI connected to<br />

the IPSI connected PN’s EI.<br />

4. Replace the active SNC.<br />

If the system has a 2-level switch node carrier configuration (i.e., SNI-to-SNI fiber links exist)<br />

and the SNIs and SNCs in the second switch node carrier only (the switch node carrier that has<br />

no SNI connected to the IPSI connected PN’s EI) are not inserted and at least two SNI-to-SNI<br />

fiber links exist:<br />

1. Run test board location long on the SNIs in the first switch node carrier that are<br />

connected to SNIs in the second switch node carrier and fix any problems.<br />

2. Replace the active SNC.<br />

3. Perform the Switch Node Interface Manual Loopback Procedure for the SNIs in the second<br />

switch node carrier that are connected to SNIs in the first switch node carrier.<br />

If software is unable to communicate with a PN’s EI but can communicate with the connected<br />

SNI:<br />

1. Run test board location long on the connected SNI and fix any problems.<br />

2. Perform the Expansion Interface Manual Loopback Procedure for the PN EI.<br />

If the connection to the SNI circuit pack is fiber, a short length of optical fiber is required for<br />

this procedure. If a metallic cable is used in the connection, remove the metallic connector<br />

from the back of the carrier, and install a lightwave transceiver in its place. The short length<br />

of optical fiber can then be used.<br />

If this procedure is run on both endpoints on a fiber link (Expansion Interface circuit packs or<br />

Switch Node Interface circuit packs), and both check out fine, then the failure is most likely<br />

in the connection (fiber or metallic) itself if neither endpoint circuit pack is busied out, but the<br />

link remains inactive.<br />

1. Use busyout board location to busyout the circuit pack (Expansion Interface or<br />

SNI).<br />

2. Disconnect the transmit and receive fiber pair from the lightwave transceiver on the back<br />

of the circuit pack (Expansion Interface or Switch Node Interface) slot.<br />

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