Creating MPLS Layer 3 VPN

When used with MPLS, the VPN feature allows several sites to interconnect transparently through a service provider's network. One service provider network can support several different IP VPNs. Each of these appears to its users as a private network, separate from all other networks. Within a VPN, each site can send IP packets to any other site in the same VPN.

Each VPN is associated with one or more VPN routing and forwarding instances (VRFs). A VRF consists of an IP routing table, a derived Cisco express forwarding (CEF) table, and a set of interfaces that use this forwarding table.

The router maintains a separate routing and CEF table for each VRF. This prevents information being sent outside the VPN and allows the same subnet to be used in several VPNs without causing duplicate IP address problems.

In this document, we'll be configuring basic MPLS Layer 3 VPN for two customers, each having two physical sites at different location.

Network Topology:

Creating MPLS Layer 3 VPN
MPLS Layer 3 VPN
Download the gns3 topology here:

Creating MPLS Layer 3 VPN.7z



In the Network diagram,
  • P1 and P2 are provider's core routers.
  • PE1 and PE2 are provider's edge routers that connect to customer sites.
  • CE1_A and CE2_A are customer edge routers of Customer-A at physically different locations.
  • CE1_B and CE2_B are customer edge routers of Customer-B at physically different locations.
  • Both the customers, Customer-A and Customer-B have different ASN at each location.

Configuration


P1
In the configuration, interfaces facing the core of the provider network are in OSPF area 0 and interfaces connected to the edge routers are in OSPF area 10. Also we have forcefully configured to use IP address of Loopback0 as mpls ldp router-id i.e. router ID of mpls ldp process will change immediately after executing the command, without waiting to restart the device.
hostname P1
!
ip cef
!
interface Loopback0
 ip address 192.0.2.1 255.255.255.255
 ip ospf 1 area 0.0.0.0
!
interface GigabitEthernet0/0
 description ## Connected to PE1 G-0/0 ##
 ip address 198.51.100.1 255.255.255.252
 ip ospf 1 area 0.0.0.10
 media-type gbic
 speed 1000
 duplex full
 negotiation auto
 mpls ip
!
interface GigabitEthernet1/0
 description ## Connected to P2 G-1/0 ##
 ip address 198.51.100.5 255.255.255.252
 ip ospf 1 area 0.0.0.0
 negotiation auto
 mpls ip
!
router ospf 1
!
mpls ldp router-id Loopback0 force

P2
In the configuration, interfaces facing the core of the provider network are in OSPF area 0 and interfaces connected to the edge routers are in OSPF area 10. Also we have forcefully configured to use IP address of Loopback0 as mpls ldp router-id i.e. router ID of mpls ldp process will change immediately after executing the command, without waiting to restart the device.
hostname P2
!
ip cef
!
interface Loopback0
 ip address 192.0.2.2 255.255.255.255
 ip ospf 1 area 0.0.0.0
!
interface GigabitEthernet0/0
 description ## Connected to PE2 G-0/0 ##
 ip address 198.51.100.9 255.255.255.252
 ip ospf 1 area 0.0.0.10
 media-type gbic
 speed 1000
 duplex full
 negotiation auto
 mpls ip
!
interface GigabitEthernet1/0
 description ## Connected to P1 G-0/0 ##
 ip address 198.51.100.6 255.255.255.252
 ip ospf 1 area 0.0.0.0
 negotiation auto
 mpls ip
!
router ospf 1
!
mpls ldp router-id Loopback0 force

PE1
Both the customers, Customer-A and Customer-B are using different ASN at each location for simplicity of configuration. We can also use same autonomous system number for a customer at all the his locations, but for that we have to use allowas-in feature on CE device. In the configuration, the device is configured with different VRFs for both the customers with route distinguisher in the form of . Both the values i.e. import and export route targets are used as same for simplicity. VRF configuration needs to done on PE routers only and not on P routers. Appropriate interface is assigned to each VRF. Three BGP neighbors have been configured, one BGP neighborship with Customer-A connected to PE1, second BGP neighborship with Customer-B connected to PE1 and third iBGP neighborship with PE2 which is the provider's edge router at physically different location, to which other site of Customer-A and Customer-B is connected, to create a VPN through Provider's core network.
hostname PE1
!
ip vrf Customer-A
 rd 64500:110
 route-target export 64500:1000
 route-target import 64500:1000
!
ip vrf Customer-B
 rd 64500:120
 route-target export 64500:2000
 route-target import 64500:2000
!
ip cef
!
interface Loopback0
 ip address 192.0.2.3 255.255.255.255
 ip ospf 1 area 0.0.0.10
!
interface GigabitEthernet0/0
 description ## Connected to P1 G-1/0 ##
 ip address 198.51.100.2 255.255.255.252
 ip ospf 1 area 0.0.0.10
 media-type gbic
 speed 1000
 duplex full
 negotiation auto
 mpls ip
!
interface GigabitEthernet1/0
 description ## Connected to CE1_A ##
 ip vrf forwarding Customer-A
 ip address 10.0.0.1 255.255.255.252
 negotiation auto
!
interface GigabitEthernet2/0
 description ## Connected to CE1_B ##
 ip vrf forwarding Customer-B
 ip address 10.0.0.5 255.255.255.252
 negotiation auto
!
router ospf 1
!
router bgp 64500
 bgp log-neighbor-changes
 neighbor 192.0.2.4 remote-as 64500
 neighbor 192.0.2.4 update-source Loopback0
 !
 address-family vpnv4
  neighbor 192.0.2.4 activate
  neighbor 192.0.2.4 send-community extended
 exit-address-family
 !
 address-family ipv4 vrf Customer-A
  neighbor 10.0.0.2 remote-as 65531
  neighbor 10.0.0.2 activate
 exit-address-family
 !
 address-family ipv4 vrf Customer-B
  neighbor 10.0.0.6 remote-as 64512
  neighbor 10.0.0.6 activate
 exit-address-family
!
mpls ldp router-id Loopback0 force

PE2
In the configuration, the device is configured with different VRFs for both the customers with route distinguisher in the form of . Both the values i.e. import and export route targets are used as same for simplicity. Appropriate interface is assigned to each VRF. Three BGP neighbors have been configured, one BGP neighborship with Customer-A connected to PE2, second BGP neighborship with Customer-B connected to PE2 and third iBGP neighborship with PE1 which is the provider's edge router at physically different location, to which other site of Customer-A and Customer-B is connected, to create a VPN through Provider's core network.
hostname PE2
!
ip vrf Customer-A
 rd 64500:110
 route-target export 64500:1000
 route-target import 64500:1000
!
ip vrf Customer-B
 rd 64500:120
 route-target export 64500:2000
 route-target import 64500:2000
!
ip cef
!
interface Loopback0
 ip address 192.0.2.4 255.255.255.255
 ip ospf 1 area 0.0.0.10
!
interface GigabitEthernet0/0
 description ## Connected to P2 G-0/0 ##
 ip address 198.51.100.10 255.255.255.252
 ip ospf 1 area 0.0.0.10
 media-type gbic
 speed 1000
 duplex full
 negotiation auto
 mpls ip
!
interface GigabitEthernet1/0
 description ## Connected to CE2_A ##
 ip vrf forwarding Customer-A
 ip address 10.1.1.1 255.255.255.252
 negotiation auto
!
interface GigabitEthernet2/0
 description ## Connected to CE2_B ##
 ip vrf forwarding Customer-B
 ip address 10.1.1.5 255.255.255.252
 negotiation auto
!
router ospf 1
!
router bgp 64500
 bgp log-neighbor-changes
 neighbor 192.0.2.3 remote-as 64500
 !
 address-family ipv4
  neighbor 192.0.2.3 activate
  neighbor 192.0.2.4 update-source Loopback0 
exit-address-family
 !
 address-family vpnv4
  neighbor 192.0.2.3 activate
  neighbor 192.0.2.3 send-community extended
 exit-address-family
 !
 address-family ipv4 vrf Customer-A
  neighbor 10.1.1.2 remote-as 65532
  neighbor 10.1.1.2 activate
 exit-address-family
 !
 address-family ipv4 vrf Customer-B
  neighbor 10.1.1.6 remote-as 64513
  neighbor 10.1.1.6 activate
 exit-address-family
!
mpls ldp router-id Loopback0 force


All the customer edge routers are connected to ISP through a point-to-point link and using BGP for advertising their LAN segment. Loopback1 is configured to emulate inside network of customer. A default route is configured on all CE devices pointing towards ISP.

CE1_A
hostname CE1_A
!
interface Loopback1
 ip address 172.16.1.1 255.255.255.0
!
interface GigabitEthernet0/0
 description ## Connected to ISP ##
 ip address 10.0.0.2 255.255.255.252
 media-type gbic
 speed 1000
 duplex full
 negotiation auto
!
router bgp 65531
 bgp log-neighbor-changes
 neighbor 10.0.0.1 remote-as 64500
!
 address-family ipv4
  network 172.16.1.0 mask 255.255.255.0
  neighbor 10.0.0.1 activate
 exit-address-family
!
ip route 0.0.0.0 0.0.0.0 10.0.0.1

CE2_A
hostname CE2_A
!
interface Loopback1
 ip address 172.16.2.1 255.255.255.0
!
interface GigabitEthernet0/0
 description ## Connected to ISP ##
 ip address 10.1.1.2 255.255.255.252
 media-type gbic
 speed 1000
 duplex full
 negotiation auto
!
router bgp 65532
 bgp log-neighbor-changes
 network 172.16.2.0 mask 255.255.255.0
 neighbor 10.1.1.1 remote-as 64500
!
ip route 0.0.0.0 0.0.0.0 10.1.1.1

CE1_B
hostname CE1_B
!
interface Loopback1
 ip address 192.168.1.1 255.255.255.0
!
interface GigabitEthernet0/0
 description ## Connected to ISP ##
 ip address 10.0.0.6 255.255.255.252
 media-type gbic
 speed 1000
 duplex full
 negotiation auto
!
router bgp 64512
 bgp log-neighbor-changes
 network 192.168.1.0
 network 192.168.1.1
 neighbor 10.0.0.5 remote-as 64500
!
ip route 0.0.0.0 0.0.0.0 10.0.0.5

CE2_B
hostname CE2_B
!
interface Loopback1
 ip address 192.168.2.1 255.255.255.0
!
interface GigabitEthernet0/0
 description ## Connected to ISP ##
 ip address 10.1.1.6 255.255.255.252
 media-type gbic
 speed 1000
 duplex full
 negotiation auto
!
router bgp 64513
 bgp log-neighbor-changes
 network 192.168.2.0
 neighbor 10.1.1.5 remote-as 64500
!
ip route 0.0.0.0 0.0.0.0 10.1.1.5




Comments

Post a Comment

Popular posts from this blog

Specifying SSH port in Ansible Inventory

There may be some instances where you set a custom port for SSH on your network device. If ssh port for hosts is different than the default port 22, it can be specified in the inventory file with colon (:) after hostname. #vi inventory # Inventory file for Ansible   [XE] ios-xe-mgmt.cisco.com:8181 ios-xe-mgmt-latest.cisco.com:8181   [XR] sbx-iosxr-mgmt.cisco.com:8181
Read more

Ansible-Playbook to display output of multiple show commands (using stdout_lines with Loop)

 In this playbook, we we'll see how we can get display of multiple show commands in stdout_lines format. We can make use of loops (or with_items) for submitting multiple commands, but debug output with stdout_lines does not gives the formatted result as it would give for single command. So in case of multiple commands, we can debug the output of each command separately in stdout_lines format.
Read more

Filtering Routes in BGP using Route-maps and Prefix-list

Image
Order of preference of attributes in BGP The order of preference varies based on whether the attributes are applied for inbound updates or outbound updates. For inbound updates the order of preference is:     route-map     filter-list     prefix-list, distribute-list For outbound updates the order of preference is:     prefix-list, distribute-list     filter-list     route-map NOTE: The attributes prefix-list and distribute-list are mutually exclusive, and only one command (neighbor distribute-list or neighbor prefix-list) can be applied to each inbound or outbound direction for a particular neighbor. Scenario: We own the AS500 and advertising a network block of 192.0.2.0/24 and 180.179.179.0/16 to two different ISPs. Objectives: Configure router R1 to establish eBGP neighbor relationship with ISP1. Configure router R1 to establish eBGP neighbor relationship with ISP2. Advertise  192.0.2.0/24 network to ISP1 only. Advertise 180.179.179.0/16 network to ISP2 only. Receive routes having n
Read more

Ansible Playbook for Network OS Upgrade with pre and post checks

You have 100s of network switches or routers that you need to upgrade. How much time would it take for you to do the upgrades? There are a lot number of sub-tasks involved while upgrading IOS image of a Cisco router or a switch. This time of upgradation can be reduced through automation from various Enterprise Configuration Management tools that also have ability to upgrade network OS. Though these tools give an easy to use graphical interface, but this requires you to have appropriate license and also restricts you to customize your upgrade process.
Read more

VMware NSX Traffic Flow — East-West & North-South

Image
Understanding how traffic is flowing in NSX environment is an important aspect to successfully maintain and troubleshoot networks having NSX. In this post we'll understand hop-by-hop flow of traffic in East-West and North-South directions. East-West: VMs on Same Subnet, Same Host VM-1 has IP address 172.16.20.6 and VM-2 has IP address 172.16.20.7 VM-1 vNIC è Logical Switch (Segment ID 5002) è VM-2 vNIC
Read more

Bypassing Proxy Server in Google Chrome

Image
There may be times when you might want to use Google Chrome and do not wish to use the proxy settings for which you are bound to use in Internet Explorer because of your company policies. If you try to change proxy settings in Google Chrome, by default it will open the System Internet Properties dialogue box, and most of the times, change in proxy setting options is restricted by domain group policy. So here is an alternate way to remove or disable proxy settings in Google Chrome. 1. Right click the GoogleChrome.exe and create it's shortcut. 2. Open the properties of the shortcut of GoogleChrome.exe created in previous step. 3. Here you have to edit the Target of this shortcut. You have to add   --proxy-server=""  after the existing path. You are done. Now enjoy the web browsing without any restrictions.
Read more

Export or Backup Azure Network Security Groups into CSV using PowerShell

There could be many use cases where you may want to export Network Security Groups into CSV. You might have question, how to export or backup Azure Network Security Groups into CSV. Here is the PowerShell script that you can use to export Azure Network Security Groups into CSV using PowerShell script. This script will export Network Security Group along with rules of all Active subscriptions into a CSV.
Read more

Ansible-playbook for backing up running config of Cisco IOS

This ansible-playbook can be used to backup running configuration from Cisco IOS devices. You can refer to my earlier post Getting Started with your first ansible-playbook for Network Automation  to know about the parameters used in this playbook. Inventory file # Inventory file for Ansible [XE] ios-xe-mgmt.cisco.com:8181 ios-xe-mgmt-latest.cisco.com:8181 [XR] sbx-iosxr-mgmt.cisco.com:8181 [all:vars] ansible_network_os=ios Playbook --- - name: Define Parameters   hosts: XE   gather_facts: no   connection: network_cli   tasks:    - name: backup the config      ios_config:       backup: yes      register: backup_config    - name: Store the config to directory      copy:       src: "{{ backup_config.backup_path }}"       dest: "/tmp/backups/{{ inventory_hostname }}" Running the playbook [prashant@Prashant-VM01 ~]$ ansible-playbook play03.yml -i /home/prashant/inventory -u developer -k SSH password: PLAY [Define Parameters] **********************************************
Read more