Table of Contents
Advertisement
If you enable HDLC payload scrambling on a T3 interface, you must also configure
the interface to be compatible with the channel service unit (CSU) at the remote end
of the line before you commit the interface configuration. For information about
subrating a T3 interface, see "Configuring the T3 CSU Compatibility Mode" on
page 590.
To explicitly disable HDLC payload scrambling, include the
statement at the
To disable payload scrambling again (return to the default), delete the
payload-scrambler
Configuring T3 Start and End Flags
By default, a T3 interface shares the transmission of the start and end flags.
To configure a T3 interface to wait two idle cycles between the start and end flags,
include the
interface-name t3-options]
To revert to the default behavior, sharing the transmission of start and end flags,
include the
interface-name t3-options]
Examples: Configuring T3 Interfaces
T3 interfaces can use PPP, Cisco HDLC, or Frame Relay encapsulation.
PPP Encapsulation on a
DS3 PIC
[edit interfaces interface-name t3-options]
compatibility-mode (adtran | digital-link | kentrox | larscom | verilink) <subrate value>;
payload-scrambler;
[edit interfaces interface-name t3-options]
[edit interfaces interface-name t3-options]
no-payload-scrambler;
statement from the configuration:
[edit]
user@host# delete interfaces t3-fpc/pic/port t3-options payload-scrambler
statement with the
start-end-flag
hierarchy level:
[edit interfaces interface-name t3-options]
start-end-flag filler;
statement with the
start-end-flag
hierarchy level:
[edit interfaces interface-name t3-options]
start-end-flag shared;
[edit]
interfaces {
t3-0/0/0 {
encapsulation ppp;
t3-options {
no-long-buildout;
compatibility-mode larscom;
payload-scrambler;
}
Chapter 32: Configuring T3 Interfaces
no-payload-scrambler
hierarchy level:
option at the
filler
[edit interfaces
option at the
shared
[edit interfaces
Configuring T3 Start and End Flags
597
Advertisement
Table of Contents
