Configure Routing Instances for Layer 2 VPNs on the PE Routers
The three PE routers service the Layer 2 VPN, so you need to configure a routing instance on each router. For the VPN, you must define the following in each routing instance:
- Route distinguisher, which must be unique for each routing instance on the PE router. It is used to distinguish the addresses in one VPN from those in another VPN.
- Instance type of
l2vpn, which configures the router to run a Layer 2 VPN.- Interfaces connected to the CE routers.
- VPN routing and forwarding (VRF) import and export policies, which must be the same on each PE router that services the same VPN and are used to control the network topology. Unless the import policy contains only a
then rejectstatement, it must include a reference to a community. Otherwise, when you attempt to commit the configuration, the commit fails.On Router A, configure the following routing instances for the Layer 2 VPN:
[edit]routing-instances {VPN-Sunnyvale-Portland-Austin {instance-type l2vpn;interface so-6/0/0.0;interface so-6/0/0.1;route-distinguisher 100:1;vrf-import vpn-SPA-import;vrf-export vpn-SPA-export;protocols {l2vpn {encapsulation-type frame-relay;site Sunnyvale {site-identifier 1;interface so-6/0/0.0 {remote-site-id 2;}interface so-6/0/0.1 {remote-site-id 3;}}}}}}On Router B, configure the following routing instance:
[edit]routing-instances {VPN-Sunnyvale-Portland-Austin {instance-type l2vpn;interface so-6/0/0.2;interface so-6/0/0.3;route-distinguisher 100:1;vrf-import vpn-SPA-import;vrf-export vpn-SPA-export;protocols {l2vpn {encapsulation-type frame-relay;site Austin {site-identifier 2;interface so-6/0/0.2 {remote-site-id 1;}interface so-6/0/0.3 {remote-site-id 3;}}}}}}On Router C, configure the following routing instance for the Layer 2 VPN:
[edit]routing-instances {VPN-Sunnyvale-Portland-Austin {instance-type l2vpn;interface so-6/0/0.4;interface so-6/0/0.5;route-distinguisher 100:1;vrf-import vpn-SPA-import;vrf-export vpn-SPA-export;protocols {l2vpn {encapsulation-type frame-relay;site Portland {site-identifier 3;interface so-6/0/0.4 {remote-site-id 1;}interface so-6/0/0.5 {remote-site-id 2;}}}}}}