Lucent Technologies Release 7 User Manual
DEFINITY Enterprise Communications Server Release 7
Maintenance for R7r
Maintenance for R7r
555-230-126
Issue 4
June 1999
Maintenance Object Repair Procedures
9-1434
SNI-BD (SNI Circuit Pack)
9
Before using this procedure, first determine whether more than one SNI is unable
to communicate with software. Verify SNI and SNC circuit pack insertion via the
list configuration carrier UUC command, where UUC is the cabinet and carrier
location of a switch node carrier. Check for SNI and SNC insertion for every
administered switch node carrier.
to communicate with software. Verify SNI and SNC circuit pack insertion via the
list configuration carrier UUC command, where UUC is the cabinet and carrier
location of a switch node carrier. Check for SNI and SNC insertion for every
administered switch node carrier.
If all of the SNIs and SNCs are not inserted ("NO BOARD" is displayed for each
board) in the entire PNC (either the a-pnc or the b-pnc), then the link between the
PPN EI (on the PNC where SNI and SNC circuit packs did not insert) and the
connected SNI is not functioning properly. If this case applies, perform the
following steps:
board) in the entire PNC (either the a-pnc or the b-pnc), then the link between the
PPN EI (on the PNC where SNI and SNC circuit packs did not insert) and the
connected SNI is not functioning properly. If this case applies, perform the
following steps:
1. Run the test board UUCSS command on the PPN EI and fix any problems
found.
2. Perform the manual loopback procedure for the PPN EI.
3. Perform the manual loopback procedure for the SNI connected to the PPN
EI.
4. Replace the active SNC.
If the system has a two level switch node carrier configuration, i.e. SNI-SNI fiber
links exist, and the SNIs and SNCs in the second switch node carrier only (the
switch node carrier that has no SNI connected to the PPN EI) are not inserted
and at least two SNI-SNI fiber links exist, perform the following steps:
links exist, and the SNIs and SNCs in the second switch node carrier only (the
switch node carrier that has no SNI connected to the PPN EI) are not inserted
and at least two SNI-SNI fiber links exist, perform the following steps:
1. Run the test board UUCSS long command on the SNIs in the first switch
node carrier that are connected to SNIs in the second switch node carrier
and fix any problems found.
and fix any problems found.
2. Replace the active SNC.
3. Perform the manual loopback procedure for the SNIs in the second switch
node carrier that are connected to SNIs in the first switch node carrier.
If software is unable to communicate with an EPN EI but can communicate with
the connected SNI:
the connected SNI:
1. Run the test board UUCSS long command on the connected SNI and fix
any problems found.
2. Perform the manual loopback procedure for the EPN EI.
When the connection to the SNI circuit pack is via fiber, a short length of
optical fiber is required for this procedure. If a metallic cable is used in the
connection, the metallic connector must be removed from the back of the
carrier, and a lightwave transceiver connected in its place. The short
length of optical fiber can then be used.
optical fiber is required for this procedure. If a metallic cable is used in the
connection, the metallic connector must be removed from the back of the
carrier, and a lightwave transceiver connected in its place. The short
length of optical fiber can then be used.
If this procedure is run on both endpoints on a fiber link (Expansion
Interface circuit packs or Switch Node Interface circuit packs), and both
check out fine, then the failure is most likely in the connection (fiber or
metallic) itself if neither endpoint circuit pack is busied out, but the link
remains inactive.
Interface circuit packs or Switch Node Interface circuit packs), and both
check out fine, then the failure is most likely in the connection (fiber or
metallic) itself if neither endpoint circuit pack is busied out, but the link
remains inactive.