Configuring SAToP Emulation on 4xCOC3/CSTM1 CE PICs

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

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

Configuring SONET/SDH Framing Emulation Mode

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



[edit chassis fpc fpc-slot pic pic-slot]
framing (sonet | sdh); # SONET for COC3 or SDH for CSTM1

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 COC3 CE PIC, then 4 COC3 interfaces are created.
If you configure a CSTM1 CE PIC, then 4 CSTM1 interfaces are created.

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

Configuring COC3 CE Channelization Down to T1 Channels

On each of the four COC3 ports (0-3), you can configure three COC1 channels (1-3). On each COC1 channel, you can configure 28 T1 channels (1-28). To configure COC3 channelization down to COC1 and then down to T1 channels, use the following statements:



[edit interface coc3-fpc/pic/port]
set coc1 coc3-fpc/pic/port:coc1–channel

set t1 coc1-fpc/pic/port:coc1–channel:t1–channel

After you configure the T1 channels, you can set the SAToP options. See Setting the SAToP Options.

Configuring CSTM1 Channelization Down to E1 Channels

On each of the four CSTM1 ports (0-3), you can configure four CAU4 channels (0-3). On each CAU4 channel, you can configure 63 T1 channels (1-63). To configure CSTM1 channelization down to CAU4 and then down to E1 channels, use the following statements:



[edit interface cstm1-fpc/pic/port]
set cau4 cstm1-fpc/pic/port:cau4–channel

set e1 cau4-fpc/pic/port:cau4–channel:e1–channel

After you configure the E1 channels, you can set the SAToP options and encapsulation. See Setting the SAToP Options.

Setting the Encapsulation Mode

T1/E1 channels on COC3/CSTM1 CE PICs can be configured with SAToP encapsulation at the PE router:



[edit interfaces (t1|e1)-fpc/pic/port:(coc1–channel
| cstm1–channel):t1/e1–channel]
encapsulation satop;
unit 0;

There is no need to configure any cross-connect circuit family since it will be automatically created for the above encapsulation.

Pseudowire Interface Configuration

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



[edit protocols l2circuit]
neighbor address {


interface coc3-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]