Using the Layer 2 Interworking Interface to Interconnect a Layer 2 Circuit to a Layer 2 VPN
Instead of using a physical Tunnel PIC for looping the packet received from the Layer 2 circuit, the Layer 2 interworking interface uses Junos OS to stitch together both Layer 2 VPN routes.
To configure the interworking interface, include the iw0 statement. The iw0 statement is configured at the [edit interfaces] hierarchy level. This specifies the peering between two logical interfaces. This configuration is similar to the configuration for a logical tunnel interface. The logical Interfaces must be associated with the endpoints of a Layer 2 circuit and Layer 2 VPN connections.
[edit interfaces]
iw0 {
unit 0 {
peer-unit 1;
}
unit 1 {
peer-unit 0;
}
}
Configure the Layer 2 circuit protocol by including the l2circuit statement at the [edit protocols] hierarchy
level and specifying the neighbor and iw0 interface.
[edit protocols]
l2circuit {
neighbor 192.0.2.0 {
interface iw0.0;
}
}
Configure the Layer 2 VPN connection, by including the routing-instance-name statement at the [edit routing-instances] hierarchy level and specifying the instance-type l2vpn option.
[edit routing-instances]
routing-instance-name {
instance-type l2vpn;
interface iw0.1;
...
protocols {
l2vpn {
<l2vpn configuration>;
}
}
}
In addition to the iw0 interface configuration,
Layer 2 interworking l2iw protocols must be enabled. Without
the l2iw configuration, the l2iw routes will
not be formed, regardless of whether any iw interfaces
are present. Within the l2iw protocols, only trace options can be
configured in the standard fashion. The minimum configuration necessary
for the feature to work is shown below:
[edit]
protocols {
l2iw;
}