Configuring The Channelized T3 Loop Timing; Configuring T3 Loopback Capability - Juniper JUNOS 10.1 - CONFIGURATION GUIDE 1-2010 Configuration Manual

JUNOS 10.1 Network Interfaces Configuration Guide
The
T3 interfaces. You cannot configure a line buildout for a DS3 channel on a channelized
OC12 interface, which runs over fiber-optic cable. If you configure this statement on
a channelized OC12 interface, it is ignored.
To have the interface drive a line that is longer than 255 feet and shorter than
450 feet, include the
t3-options]
To explicitly configure the default short line buildout, include the
statement at the

Configuring the Channelized T3 Loop Timing

By default, internal clocking (line timing) is used on channelized IQ and IQE interfaces.
To configure SONET/SDH or DS3-level external clocking, include the
statement:
You can include this statement at the following hierarchy levels:
To explicitly configure the default line timing, include the
in the configuration:
The
configure on channelized IQ and IQE PICs. If you attempt to include these statements
on any other interface type, they are ignored.
For all channelized IQ and IQE PICs, the
channels. To configure clocking on individual interfaces, include the
at the
the
For more information, see "Configuring the Clock Source" on page 140 and "Clock
Sources on Channelized Interfaces" on page 398.

Configuring T3 Loopback Capability

You can configure loopback capability between the local T3 interface and the remote
CSU, as shown in Figure 57 on page 595. You can configure the loopback to be local
594
Configuring the Channelized T3 Loop Timing
and
long-buildout no-long-buildout
long-buildout
hierarchy level:
[edit interfaces interface-name t3-options]
long-buildout;
[edit interfaces interface-name t3-options]
[edit interfaces interface-name t3-options]
no-long-buildout;
loop-timing;
[edit interfaces ct3-fpc/pic/port t3-options]
[edit interfaces stm1-fpc/pic/port sonet-options]
no-loop-timing;
and
loop-timing no-loop-timing
[edit interfaces type-fpc/pic/port:channel]
clocking statement, the individual interfaces use internal clocking by default.
statements apply only to copper-cable-based
statement at the [edit interfaces interface-name
hierarchy level:
no-loop-timing
statements apply only to E1 and T1 interfaces you
statement is supported on all
clocking
hierarchy level. If you do not include
no-long-buildout
loop-timing
statement
clocking statement