19.12.2012 Views

Demand test descriptions and error codes - Avaya Support

Demand test descriptions and error codes - Avaya Support

Demand test descriptions and error codes - 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.

Replacing an SNI Circuit Pack— Duplicated PNC<br />

SNI-BD (SNI Circuit Pack)<br />

WARNING: On a system with duplicated PNC synchronization may be provided over a<br />

combination of active <strong>and</strong> st<strong>and</strong>by components. This condition is indicated by an<br />

OFF-BOARD WRN alarm against TDM-CLK with Error Type 2305. Repairs to<br />

st<strong>and</strong>by PNC in this state may disrupt service. If the active PNC is functional,<br />

replacement of a st<strong>and</strong>by component does not disrupt service.<br />

To replace a Switch Node Interface circuit pack in an duplicated PNC:<br />

1. Enter status pnc.<br />

Verify that the component to be replaced is on the st<strong>and</strong>by PNC.<br />

2. Enter busyout pnc.<br />

3. Enter busyout board location.<br />

4. Replace the circuit pack.<br />

5. Enter release board location.<br />

CAUTION: Do<br />

! CAUTION:<br />

not busyout any Expansion Interface circuit pack after this point.<br />

6. Enter <strong>test</strong> alarms long clear for category exp-intf.<br />

7. Wait 5 minutes for SNI-BD, SNI-PEER, FIBER-LK, <strong>and</strong> DS1C alarms to clear, or enter<br />

clear firmware-counters sp 0 a-pnc | b-pnc.<br />

Use the letter designation of the pnc which holds the replaced component (the st<strong>and</strong>by<br />

pnc).<br />

8. Enter status pnc.<br />

If either PNC’s state of health is not “functional”, consult PNC-DUP (PNC Duplication).<br />

9. Enter release pnc.<br />

Switch Node Interface Manual Loopback Procedure<br />

This procedure is destructive.<br />

Use this procedure when an SNI circuit pack cot be <strong>test</strong>ed by software. This can occur when<br />

communication between the switch node carrier <strong>and</strong> the server is down. Before using this<br />

procedure, use <strong>test</strong> board location to run the Configuration Audit (#759) on SNI circuit<br />

packs where possible. Also, use <strong>test</strong> board location long to run the Processor Route<br />

Audit Test (#760) for the active SNC in the switch node carrier. If the active SNC is not inserted,<br />

use <strong>test</strong> hardware-group pnc P, where P is a-pnc or b-pnc to run Test #760.<br />

Issue 5 May 2009 867

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

Saved successfully!

Ooh no, something went wrong!