An Ultra-Wan Csu/Dsu Interface; Response To A Loopback Assertion Via Inbound Bop And Mop Messages On An Ultra-Wan Csu/Dsu Interface; Performing T3/E3 Loopback Tests - 3Com 3C8S5007 - SuperStack II PathBuilder S500 Switch User Manual

Response to a
Loopback Assertion
via Inbound BoP and
MoP Messages on an
Ultra-WAN CSU/DSU
Interface
Performing T3/E3
Loopback Tests
If the PathBuilder is connected to the T1 central office switch that
supports BoP (bit-oriented protocol) or MoP (message-oriented protocol)
messaging, this central office switch can send a loopback request via
these messages to the PathBuilder switch.
Upon receipt of such a loopback request message, the PathBuilder switch
displays one of the following messages, depending on the loopback
requested:
engaging line loopback
or
engaging payload loopback
The PathBuilder switch then loops the received T1 data stream back to
the transmit side, out to the central office switch.
Upon receipt of a loopback terminate message, the PathBuilder switch
displays:
terminating remote-initiated loopback
The Pathbuilder switch then terminates the loopback.
This section describes the steps required to perform various types of
loopback tests for a T3/E3 interface.
Before running the T3/E3 loopback test, attach a console or Telnet to your
PathBuilder switch.
To perform a loopback test on the T3/E3 interface, follow these steps:
1 Disable the path using:
SETDefault !<path> -PA Control=Disable
2 Start a loopback test by entering one of the following commands.
a To start an internal HSSI loopback test, use:
DS3Lpbk !<path> -PA HSSIIntrnl
b To start an loopback test to an external device in HSSI mode, use:
DS3Lpbk !<path> -PA HSSIPassive
c To start an internal T3 framer loopback test, use:

Performing T3/E3 Loopback Tests

127