L3VPN Configuration Example
Note: The I.P addresses configured between the routers are in the format of 192.168.x.x/24 for routers.
In this setup, there are 2 different customers which are using the same MPLS backbone/ISP.
| – | Customer1 on R1 and R6 routers. |
| – | Customer2 on R3 and R7 routers. |
The configuration is divided into five parts:
| – | Static Route configured at the Customer edge routers R1& R6, R3 & R7. |
| – | OSPF configured at Backbone routers R2, R4, R5. |
| – | VRF configured at Provider Edge routers R2 and R5. |
| – | MPLS configured at Backbone routers R2, R4 and R5. |
| . | . |
| – | The routers R1, R2, R3, R4, R5, R6 and R7 have been configured with router-id 1.1.1.1, 2.2.2.2, 3.3.3.3, 4.4.4.4, 5.5.5.5, 6.6.6.6 and 7.7.7.7 respectively. |
| – | The routers R1, R2, R3, R4, R5, R6 and R7 have been configured with router-id 1.1.1.1, 2.2.2.2, 3.3.3.3, 4.4.4.4, 5.5.5.5, 6.6.6.6 and 7.7.7.7 respectively. |
| – | A static route is configured from R1 to R6 at R1 for Customer 1 and vice versa at R6. Similarly, static route has been configured for Customer 2. |
| – | By using OSPF protocol, the connectivity between MPLS Backbone/ISP Routers is established. |
| – | 2 different VRFs are used for the 2 customers. The VRF is associated with a table. At Router R2, eth1 is configured as a member of VRF Customer 1, and eth3 as a member of VRF Customer 2. Similarly eth2 and eth3 are configured at Router R5. |
| – | Enabling interfaces for MPLS at Backbone routers eth2 at R2, eth2 and eth1 at R4, eth1 at R5. |
| – | Static labels are used at R2, R4 and R5 for Push, Swap and Pop operation. |
Once the ping is initiated from PC1, a label 100 will be inserted at R2. This label will swap 101 at R4. Now, this label will be popped at R5 and the packet will reach it destination i.e. PC3.
The above mentioned features are offered and supported by VCL-MX-50xx family of IP/MPLS Routers.