Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

ON THIS PAGE

Configuring SAToP Emulation on T1/E1 Interfaces on 12-Port Channelized T1/E1 Circuit Emulation PICs

 

The following sections describes configuring SAToP on the 12-port Channelized T1/E1 Circuit Emulation PICs:

Setting the Emulation Mode

To set the framing emulation mode, include the framing statement at the [edit chassis fpc fpc-slot pic pic-slot] hierarchy level:

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:

  • If you include the framing t1 statement (for a T1 Circuit Emulation PIC), 12 CT1 interfaces are created.

  • If you include the framing e1 statement (for an E1 Circuit Emulation PIC), 12 CE1 interfaces are created.

Note

If you set the framing option incorrectly for the PIC type, the commit operation fails.

Circuit Emulation PICs with SONET and SDH ports require prior channelization down to T1 or E1 before you can configure them. Only T1/E1 channels support SAToP encapsulation or SAToP options.

Bit error rate test (BERT) patterns with all ones received by T1/E1 interfaces on Circuit Emulation PICs configured for SAToP do not result in an alarm indication signal (AIS) defect. As a result, the T1/E1 interfaces remain up.

Configuring SAToP Emulation on T1/E1 Interfaces

Setting the Encapsulation Mode

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

Note

The below mentioned procedure can be used to configure T1 channels on circuit emulation PICs with SAToP encapsulation at the PE router.

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

    For example:

  2. Configure 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 above encapsulation.

Configuring Loopback for a T1 Interface or an E1 Interface

To configure loopback capability between the local T1 interface and the remote channel service unit (CSU), see Configuring T1 Loopback Capability. To configure loopback capability between the local E1 interface and the remote channel service unit (CSU), see Configuring E1 Loopback Capability.

Note

By default, no loopback is configured.

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:

See also

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 the configuration mode, go to [edit protocols l2circuit] hierarchy level.
  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.
    Note

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

    For example:

  3. To verify the 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 PICs, see the PIC Guide for your router.

Note

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

Related Documentation