Related Documentation
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:
- In configuration mode, go to the [edit protocols
l2circuit] hierarchy level.[edit]user@host# edit protocol l2circuit
- 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.[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
For example:
[edit protocol l2circuit]user@host# set neighbor 10.255.0.6 interface ds-1/0/0:1:1:1 virtual-circuit-id 1
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, packetization latency, 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 type is 0x0015 CESoPSN basic mode.
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.
