Configuring SAToP Emulation on T1/E1 interfaces on CE PICs

[Contents] [Prev] [Next] [Index] [Report an Error]

This configuration example applies to the mobile backhaul application shown in Figure 40.

Setting the Emulation Mode

To set the framing emulation mode, use the following statements:



[edit chassis fpc fpc-slot pic pic-slot]
framing (t1 | e1);

After a PIC is brought online, interfaces are created for the PIC’s available ports according to the PIC type and the framing option used. For example:

If you configure a T1 CE PIC, then 12 CT1 interfaces are created.
If you configure an E1 CE PIC, then 12 CE1 interfaces are created.

Note: If you set the framing option incorrectly for the PIC type, performing a commit will log the failure.

CE PICs with SONET and SDH ports require prior channelization down to T1 or E1 before configuring. Only T1/E1 channels support SAToP encapsulation or SAToP options.

Setting the Encapsulation Mode

T1/E1 channels on CE PICs can be configured with SAToP encapsulation at the PE router, as follows:



[edit interfaces (t1|e1)–fpc/pic/port]
encapsulation satop;
unit 0;

You do not need to configure any cross-connect circuit family since it will be automatically created for the above encapsulation.

T1/E1 Loopback Support

Use the CLI to configure remote and local loopback as T1 (CT1) or E1 (CE1). By default, no loopback is configured.

T1 FDL Support

If T1 is used for SAToP, the T1 facility data-link (FDL) loop is NOT supported on the CT1 interface device because SAToP does not analyze T1 framing bits.

Setting the SAToP Options

The following are SAToP options:

apply-groups—Groups from which to inherit configuration data.
apply-groups-except—Don't inherit configuration data from these exception groups.
groups—Specify groups.
excessive-packet-loss-rate—Set packet loss options.
idle-pattern—An 8-bit hexadecimal pattern to replace TDM data in a lost packet (from 0 to 255).
jitter-buffer-auto-adjust—Automatically adjust the jitter buffer.
jitter-buffer-latency—Number of milliseconds delay in the jitter buffer (from 1 to 1000 milliseconds).
jitter-buffer-packets—Number of packets in the jitter buffer (from 1 to 64 packets).
payload-size—Configure the payload size, in bytes (from 32 to 1024 bytes).
sample-period—Number of milliseconds over which excessive packet loss rate is calculated.
threshold—Percentile designating the threshold of excessive packet loss rate (from 1 to 100 percent).

The following example shows the SAToP configuration options:



[edit interfaces (t1|e1)-fpc/pic/port]
satop-options { 


excessive-packet-loss-rate {
apply-groups group-names;
apply-groups-except group-names;
groups group-names;
sample-period milliseconds;
threshold percentile;
)


idle-pattern pattern;
jitter-buffer-auto-adjust;
jitter-buffer-latency milliseconds;
jitter-buffer-packets packets;
payload-size bytes;
}

Pseudowire Interface Configuration

Configuration for the TDM pseudowire at the PE uses the existing Layer 2 circuit infrastructure:



[edit protocols l2circuit]
neighbor address {


interface t1-fpc/pic/port.0 {
virtual-circuit-id 1;
}


}

After the CE-bound interfaces (for both PEs) are configured with proper encapsulation, payload size, and other parameters, the two PEs will try to establish a pseudowire with PWE3 signaling extensions. The following pseudowire interface configurations will be disabled or ignored for TDM pseudowires:

ignore-encapsulation
mtu

The supported pseudowire types are:

0x0011 Structure-Agnostic E1 over Packet
0x0012 Structure-Agnostic T1 (DS1) over Packet

When the local interface parameters match the received parameters, and the pseudowire type and control world bit are equal, the pseudowire is established.

For detailed information about configuring TDM pseudowire, see the VPNs Configuration Guide.

For detailed information about PICs, see the corresponding PIC Guide for your router.

[Contents] [Prev] [Next] [Index] [Report an Error]