SN-CONF (Switch Node Configuration)
Issue 1 May 2002
8-1381
555-233-143
Forcing SNI-to-SNI Fiber Connection
To force an SNI-to-SNI fiber connection to be used as a system-link, remove
every SNI-to-SNI connection except the fiber link being tested at the distant switch
node by removing SNI boards in the distant switch node.
1. Use the status sys-link command to verify that the fiber selected for test is
in the path to the EPN connected to the distant switch node that will be
used for the LED test.
2. Run the test led sequence to a port network as described above to verify
this fiber connection.
3. Repeat the above procedure for each of the SNI-to-SNI fibers terminating
on the distant switch node.
Testing Multiple Fiber Connections
To test multiple fiber connections to a distant switch node:
1. Use the list fiber-link command to determine the number of SNI-to-SNI
fibers that are administered to and terminate on the distant switch node.
2. Run the test led port-network command on an EPN connected to the
distant switch node, and verify the LEDs on the correct EPN are lit.
3. Use the status sys-link command, and select the active EI in the
IPSI-connected EPN connected to the distant EPN under test. (The
display will show the path from the IPSI-connected EPN and the
SNI-to-SNI fiber being used.)
4. If the EPN’s LEDs are lit and there are multiple fibers to the distant switch
node, remove the SNC that is listed by the list fiber-link command for this
path.
If not, enter the list fiber-link command to verify that the fiber connections
to the EPN are consistent with the administration assignments.
5. Use the status sys-link command to determine the new path from the
IPSI-connected EPN to the distant switch.
6. Run the test led port-network command on the port network connected to
the distant switch node, and verify that the LEDs on the correct EPN are lit.
7. Repeat steps 4 – 6 until every SNI-to-SNI fiber connection to the distant
switch has been tested.
Summary of Contents for S8700 Series
Page 50: ...Maintenance Architecture 555 233 143 1 26 Issue 1 May 2002 ...
Page 74: ...Initialization and Recovery 555 233 143 3 12 Issue 1 May 2002 ...
Page 186: ...Alarms Errors and Troubleshooting 555 233 143 4 112 Issue 1 May 2002 ...
Page 232: ...Additional Maintenance Procedures 555 233 143 5 46 Issue 1 May 2002 ...
Page 635: ...status psa Issue 1 May 2002 7 379 555 233 143 status psa See status tti on page 7 406 ...
Page 722: ...Maintenance Commands 555 233 143 7 466 Issue 1 May 2002 ...