Configuring T3 Hdlc Payload Scrambling - Juniper JUNOS 10.1 - CONFIGURATION GUIDE 1-2010 Configuration Manual

Network interfaces configuration
Table of Contents

Advertisement

JUNOS 10.1 Network Interfaces Configuration Guide
With this configuration, the link stays up, so you can loop ping packets to a remote
router. The
before the data reaches the transceiver.
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, for example:
For channel 0 on channelized interfaces only, you can include the
at the
setting configured for channel 0 applies to all channels on the channelized interface.
The
configuration of other channels. To configure loopbacks on individual channels, you
must include the
each channel. This allows each channel to be put in loopback mode independently.
For example, for DS3 channels on a channelized OC12 interface, the
loopback
configuration for channels 1 through 11. The SONET loopback configured for channel
0 applies to all 12 channels equally. To configure loopbacks on the individual DS3
channels, you must include the
for each channel. This allows each DS3 channel can be put in loopback mode
independently.

Configuring T3 HDLC Payload Scrambling

T3 HDLC payload scrambling, which is disabled by default, provides better link
stability. Both sides of a connection must either use or not use scrambling.
On a channelized OC12 interface, the SONET
To configure scrambling on the DS3 channels on the interface, you can include the
t3-options payload-scrambler
hierarchy level for each DS3 channel.
596
Configuring T3 HDLC Payload Scrambling
encapsulation cisco-hdlc;
t3-options {
loopback local;
}
unit 0 {
family inet {
address 10.100.100.1/24;
}
}
}
statement causes the interface to loop within the PIC just
loopback local
[edit]
user@host# delete interfaces t3-fpc/pic/port t3-options loopback
user@host> show interfaces t3-fpc/pic/port extensive
[edit interfaces interface-name interface-type-options]
statement is ignored if you include it at this hierarchy level in the
loopback
channel-type-options loopback
statement is supported only for channel 0; it is ignored if included in the
loopback
show interface interface-name extensive
statement in the configuration for
statement in the configuration
t3-options loopback
payload-scrambler
statement at the
[edit interfaces interface-name t3-options]
statement from the
statement
loopback
hierarchy level. The loopback
sonet-options
statement is ignored.

Advertisement

Table of Contents
loading

This manual is also suitable for:

Junos 10.1

Table of Contents