I P - D S U U s e r ’ s M a n u a l
02/02/08
39
between the BNS trunk and the
IP-DSU
. Make sure the BNS trunk module and the
device port on the
IP-DSU
have the same timing configurations.
7.1.2 Circuit
Tracing
With the
IP-DSU
loopback
command and
ping
, trace the complete circuit between BNS
nodes. Start tracing from either end of the circuit, not the middle. A failed trace test
points to the set of interfaces, cables, and facilities that make up the failing circuit.
Most of the following diagnostic steps can be done from a central location, such as from
a StarKeeper® II NMS.
Step 1:
Set
IP-DSU
(1) in port loopback mode. This instructs the
IP-DSU
to return any
data it receives at its device interface.
6
From BNS node (1) run a remote loopback test from the trunk module to
IP-DSU
(1).
If the test passes, move to step two.
If the test fails, check the facility between the two devices.
Step 2:
Set
IP-DSU
(2) to net loopback mode. This instructs the far-end
IP-DSU
to
return any data it receives at its 10BaseT LAN interface.
From BNS node (1) run a remote loopback test from the trunk module to
IP-DSU
(2).
If the test passes, move to step seven.
If the test fails, move to step three.
Step 3:
Ping
IP-DSU
(1) from a device (e.g. router) on the same LAN segment.
6
It is necessary to have first established peer-to-peer communication between the
IP-DSU
s if you are using
pre-build 17 software. Otherwise the BNS trunk diagnostic will fail due to EIA lead status on the device
interface. Build 17 includes a modification to eliminate this requirement.
BNS-2000(2)
IP-DSU(1)
BNS-2000(1)
IP-DSU(2)
Intranet
/
Internet
