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

• Setting the Emulation Mode
• Configuring SAToP Emulation on T1/E1 Interfaces

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:

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

   For example:

   [edit][edit interfaces e1-1/0/0]
2. Configure SAToP encapsulation and the logical interface for E1 interface
   [edit interfaces e1-1/0/0]user@host# set encapsulation encapsulation-typeunit interface-unit-number;

   For example:

   [edit interfaces e1-1/0/0]user@host# set encapsulation satop unit 0;

You do not need to configure any cross-connect circuit family because it is 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. 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

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

   For example:

   [edit]user@host# edit interfaces e1-1/0/0
2. Use the edit command to go to the satop-options hierarchy level.
   [edit]user@host# edit satop-options
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.

   [edit interfaces e1-1/0/0 satop-options]user@host# set excessive-packet-loss-rate sample-period sample-period

   For example:

   [edit interfaces e1-1/0/0 satop-options]user@host# set excessive-packet-loss-rate sample-period 4000

Configuring the Pseudowire Interface

1. In the configuration mode, go to [edit protocols l2circuit] hierarchy level.
   [edit]user@host# edit protocol l2circuit
2. Configure the IP address of the neighboring router or switch, interface forming the layer 2 circuit and the identifier for the layer 2 circuit.
   [edit protocol l2circuit]user@host# set neighbor ip-address interface interface-name-fpc-slot/pic-slot/port.interface-unit-number virtual-circuit-id virtual-circuit-id;

   Note: To configure T1 interface as the layer 2 circuit, replace e1 with t1 in the below statement.

   For example:

   [edit protocol l2circuit]user@host# set neighbor 10.255.0.6 interface e1-1/0/0.0 virtual-circuit-id 1
3. To verify the configuration use the show command at the [edit protocols l2circuit] hierarchy level.
   [edit protocols l2circuit]user@host# show

   neighbor 10.255.0.6 {interface e1-1/0/0.0 {virtual-circuit-id 1;}}

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

• 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 Configuration Guide.

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