Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Configuring SAToP Encapsulation on T1/E1 Interfaces

 

This configuration applies to the mobile backhaul application shown in Mobile Backhaul Application.

This topic includes the following tasks:

Setting the Encapsulation Mode

E1 channels on Circuit Emulation MICs can be configured with SAToP encapsulation at the provider edge (PE) router, as follows:

Note

The following procedure can be used to configure T1 channels on Circuit Emulation MICs with SAToP encapsulation at the PE router.

  1. In configuration mode, go to the [edit interfaces e1-fpc-slot/pic-slot/port] hierarchy level.

    For example:

  2. Configure the SAToP encapsulation and the logical interface for E1 interface.

    For example:

You do not need to configure any cross-connect circuit family because it is automatically created for the SAToP 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. See Configuring T1 Loopback Capability and Configuring E1 Loopback Capability.

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

To configure SAToP options on T1/E1 interfaces:

  1. In configuration mode, go to the [edit interfaces e1-fpc-slot/pic-slot/port] hierarchy level.

    For example:

  2. Use the edit command to go to the satop-options hierarchy level.
  3. In this hierarchy level, using the set command you can configure the following SAToP options:
    • excessive-packet-loss-rate—Set packet loss options. The options are groups, sample-period, and threshold.

      • groups—Specify groups.

      • sample-period—Time required to calculate excessive packet loss rate (from 1000 through 65,535 milliseconds).

      • threshold—Percentile designating the threshold of excessive packet loss rate (1–100 percent).

    • idle-pattern—An 8-bit hexadecimal pattern to replace TDM data in a lost packet (from 0 through 255).

    • jitter-buffer-auto-adjust—Automatically adjust the jitter buffer.

      Note

      The jitter-buffer-auto-adjust option is not applicable on MX Series routers.

    • jitter-buffer-latency—Time delay in the jitter buffer (from 1 through 1000 milliseconds).

    • jitter-buffer-packets—Number of packets in the jitter buffer (from 1 through 64 packets).

    • payload-size—Configure the payload size, in bytes (from 32 through 1024 bytes).

    Note

    In this section, we are configuring only one SAToP option. You can follow the same method to configure all the other SAToP options.

    For example:

To verify this configuration, use the show command at the [edit interfaces e1-1/0/0] hierarchy level:

Configuring the Pseudowire Interface

To configure the TDM pseudowire at the provider edge (PE) router, use the existing Layer 2 circuit infrastructure, as shown in the following procedure:

  1. In configuration mode, go to the [edit protocols l2circuit] hierarchy level.
  2. Configure the IP address of the neighboring router or switch, the interface forming the Layer 2 circuit, and the identifier for the Layer 2 circuit.
    Note

    To configure the T1 interface as the Layer 2 circuit, replace e1 with t1 in the configuration statement.

    For example:

  3. To verify this configuration, use the show command at the [edit protocols l2circuit] hierarchy level.

After the customer edge (CE)-bound interfaces (for both PE routers) are configured with proper encapsulation, payload size, and other parameters, the two PE routers try to establish a pseudowire with Pseudowire Emulation Edge-to-Edge (PWE3) signaling extensions. The following pseudowire interface configurations are 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 word bit are equal, the pseudowire is established.

For detailed information about configuring TDM pseudowire, see the Junos OS VPNs Library for Routing Devices.

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

Related Documentation