DEFINITY Enterprise Communications Server Release 7
Maintenance for R7r
555-230-126
Issue 4
June 1999
Maintenance Object Repair Procedures
9-1433SNI-BD (SNI Circuit Pack)
9
Replacing an SNI Circuit Pack— Duplicated PNC
!
WARNING:
On a system with duplicated PNC, synchronization may be provided over a
combination of active and standby components. This condition is indicated
by an OFF-BOARD WARNING alarm against TDM-CLK with error type
2305. Repairs to standby PNC in this state may disrupt service. Otherwise,
if the active PNC is functional, replacement of a standby component will not
disrupt service.
Switch Node Interface Manual Loop Back
Procedure
This procedure is destructive.
This procedure is to be used when an SNI circuit pack cannot be tested by
software. This can occur when communication between the switch node carrier
and the SPE is down. Before using this procedure, the configuration audit test
(#759) should be run on SNI circuit packs where possible via test board UUCSS
s. Also, the processor route audit test (#760) should be run via the test board
UUCSS long command for the active SNC in the switch node carrier. If the active
SNC is not inserted, test 760 can be run via test hardware-group pnc P, where
P is a-pnc or b-pnc.
1. Enter status pnc Verify that the component to be replaced is on the
standby PNC.
2. Enter busyout pnc
3. Enter busyout board UUCSS UUCSS represents the cabinet-carrier-slot address
of the circuit pack to be replaced.
4. Replace the circuit pack
5. Enter release board UUCSS
!
CAUTION:
Do not busyout any Expansion Interface
circuit pack after this point.
6. Enter test alarms long clear for
category exp-intf.
7. Wait 5 minutes for SNI-BD, SNI-PEER,
FIBER-LK, and DS1C alarms to clear,
or enter clear firmware counterssp 0
<a-pnc or b-pnc>.
Use the letter designation of the pnc which holds
the replaced component (the standby pnc).
8. Enter status pnc. If either PNC state-of-health is not "functional",
consult the ‘‘PNC-DUP (PNC Duplication)’’
section.
9. Enter release pnc.
