To Next Page

To Previous Page

• Configuring Interface Diagnostics Tools to Test the Physical Layer Connections

Configuring T1 Loopback Capability

You can configure loopback capability between the local T1 interface and the remote

channel service unit (CSU), as shown in Figure 19 on page 170. You can configure the

loopback to be local or remote. With local loopback, the T1 interface can transmit packets

to the CSU, but receives its own transmission back again and ignores data from the CSU.

With remote loopback, packets sent from the CSU are received by the T1 interface,

forwarded if there is a valid route, and immediately retransmitted to the CSU.

Figure 19: Remote and Local T1 Loopback

To configure loopback capability on a T1 interface, include the loopback statement at

the [edit interfaces interface-name t1-options] hierarchy level:

[edit interfaces interface-name t1-options]

loopback (local | payload | remote);

Packets can be looped on either the local router or the remote CSU. Local and remote

loopback loop back both data and clocking information.

To exchange BERT patterns between a local router and a remote router, include the

loopback remote statement in the interface configuration at the remote end of the link.

From the local router, issue the test interface command.

For more information about configuring BERT, see Configuring Interface Diagnostics Tools

to Test the Physical Layer Connections. For more information about using operational

mode commands to test interfaces, see the CLI Explorer.

For channelized T3, T1, and NxDS0 intelligent queuing (IQ) interfaces only, you can include

the loopback payload statement in the configuration to loop back data only (without

clocking information) on the remote router’s PIC. In payload loopback, overhead is

recalculated. For T3 IQ interfaces, you can include the loopback payload statement at

the [edit interfaces ct3-fpc/pic/port] and [edit interfaces t3-fpc/pic/port:channel] hierarchy

levels. For T1 interfaces, you can include the loopback payload statement in the

configuration at the [edit interfaces t1-fpc/pic/port:channel] hierarchy level; it is ignored

if included at the [edit interfaces ct1-fpc/pic/port] hierarchy level. For NxDS0 interfaces,

payload and remote loopback are the same. If you configure one, the other is ignored.

NxDS0 IQ interfaces do not support local loopback.

ACX Series Universal Access Router Configuration Guide

Juniper ACX2000 Configuration Guide

Other manuals for Juniper ACX2000