Table of Contents
Advertisement
E1 interface, forwarded if there is a valid route, and immediately retransmitted to
the CSU.
Figure 54: Remote and Local E1 Loopback
To configure loopback capability on an E1 interface, include the
at the
Packets can be looped on either the local router or the remote CSU.
To exchange BERT patterns between a local router and a remote router, include the
loopback remote
link. From the local router, you issue the
For more information about configuring BERT, see "Interface Diagnostics" on page 146.
For more information about using operational mode commands to test interfaces,
see the JUNOS System Basics and Services Command Reference.
To turn off the loopback capability, remove the
configuration:
You can determine whether there is an internal problem or an external problem by
checking the error counters in the output of the
command:
Example: Configuring E1 Loopback Capability
To determine whether a problem is internal or external, loop packets on both the
local and the remote router. To do this, include the
cisco-hdlc
loopback local
level.
[edit interfaces interface-name e1-options]
[edit interfaces interface-name e1-options]
loopback (local | remote);
statement in the interface configuration at the remote end of the
[edit]
user@host# delete interfaces e1-fpc/pic/port e1-options loopback
user@host> show interfaces interface-name extensive
statements at the
statement at the
Chapter 29: Configuring E1 Interfaces
hierarchy level:
test interface
loopback
show interface interface-name extensive
no-keepalives
[edit interfaces interface-name]
[edit interfaces interface-name e1-options]
Configuring E1 Loopback Capability
statement
loopback
command.
statement from the
and
encapsulation
hierarchy level and the
hierarchy
565
Advertisement
Table of Contents
