Configuring HoVPN



Configuring Hierarchy Of VPN - HoVPN

We already explain the HoVPN before so now we will know how to configure it .


Networking Requirements

As shown in Figure 1:
  • CE1 and CE2 belong to VPN-A and the VPN target is 1:1.
  • CE1 accesses the backbone network through the UPE and CE2 accesses the network through the PE.
  • The UPE, the SPE and the PE are interconnected through OSPF.
Figure 1 Networking diagram of HoVPN

Configuration Roadmap

The configuration roadmap is as follows:
  1. Configure IGP in the backbone network and ensure the PEs can learn the loopback address from each other.
  2. Configure MPLS LSP between PEs.
  3. Create the VPN instance on the UPE and set up the EBGP peer relationship between the UPE and the CE1.
  4. Create the VPN instance on the PE and set up the EBGP peer relationship between the PE and the CE2.
  5. Set up the MP-IBGP peer relationship between the UPE and the SPE, the PE and the SPE.
  6. Create the VPN instance on the SPE. Specify the UPE as the underlayer PE, that is, the user layer PE. Advertise the default route of the VPN instance to the UPE.

Data Preparation

  • MPLS LSR-ID of the UPE, SPE and PE
  • VPN instance name, RD and VPN target created on the UPE, SPE and PE

Procedure

  1. Configure OSPF on the MPLS backbone network to implement internetworking.
    After the configuration, OSPF neighbors are established among UPE, SPE and PE. Run the display ospf peer command to see the status of the OSPF neighbor relationship is "Full". Run the display ip routing-table command to see that PEs know loopback routes from each other.
    The specific configuration procedures are not mentioned here.
  2. Configure basic MPLS capability and MPLS LDP on MPLS backbone networks and establish LDP LSP.
    After the configuration, LDP session can be established among UPE, SPE and PE. Run the display mpls ldp session command to see that the session state is "Operational". Run the display mpls ldp lsp command to see LDP LSP is established.
    The specific configuration procedures are not mentioned here.
  3. Configure PEs and CEs.
    # Configure UPE.
    <UPE> system-view
    [UPE] ip vpn-instance vpna
    [UPE-vpn-instance-vpna] ipv4-family
    [UPE-vpn-instance-vpna-af-ipv4] route-distinguisher 100:1
    [UPE-vpn-instance-vpna-af-ipv4] vpn-target 1:1
    [UPE-vpn-instance-vpna-af-ipv4] quit
    [UPE-vpn-instance-vpna] quit
    [UPE] interface gigabitethernet 1/0/0
    [UPE-GigabitEthernet1/0/0] ip binding vpn-instance vpna
    [UPE-GigabitEthernet1/0/0] ip address 10.1.1.2 24
    [UPE-GigabitEthernet1/0/0] quit
    [UPE] bgp 100
    [UPE-bgp] ipv4-family vpn-instance vpna
    [UPE-bgp-vpna] peer 10.1.1.1 as-number 65410
    [UPE-bgp-vpna] import-route direct
    [UPE-bgp-vpna] quit
    [UPE-bgp] quit
    # Configure CE1.
    <HUAWEI> system-view
    [HUAWEI] sysname CE1
    [CE1] interface gigabitethernet 1/0/0
    [CE1-GigabitEthernet1/0/0] ip address 10.1.1.1 24
    [CE1-GigabitEthernet1/0/0] quit
    [CE1] bgp 65410
    [CE1-bgp] peer 10.1.1.2 as-number 100
    [CE1-bgp] import-route direct
    [CE1-bgp] quit
    # Configure PE.
    <PE> system-view
    [PE] ip vpn-instance vpna
    [PE-vpn-instance-vpna] ipv4-family
    [PE-vpn-instance-vpna-af-ipv4] route-distinguisher 100:2
    [PE-vpn-instance-vpna-af-ipv4] vpn-target 1:1
    [PE-vpn-instance-vpna-af-ipv4] quit
    [PE-vpn-instance-vpna] quit
    [PE] interface gigabitethernet 1/0/0
    [PE-GigabitEthernet1/0/0] ip binding vpn-instance vpna
    [PE-GigabitEthernet1/0/0] ip address 10.2.1.2 24
    [PE-GigabitEthernet1/0/0] quit
    [PE] bgp 100
    [PE-bgp] ipv4-family vpn-instance vpna
    [PE-bgp-vpna] peer 10.2.1.1 as-number 65420
    [PE-bgp-vpna] import-route direct
    [PE-bgp-vpna] quit
    [PE-bgp] quit
    # Configure CE2.
    <HUAWEI> system-view
    [HUAWEI] sysname CE2
    [CE2] interface gigabitethernet 1/0/0
    [CE2-GigabitEthernet1/0/0] ip address 10.2.1.1 24
    [CE2-GigabitEthernet1/0/0] quit
    [CE2] bgp 65420
    [CE2-bgp] peer 10.2.1.2 as-number 100
    [CE2-bgp] import-route direct
    [CE2-bgp] quit
    After the configuration, run the display ip vpn-instance verbose command on the PE or UPE to see the configurations of VPN instances. By running the command ping -vpn-instance, the PE and UPE can ping the CEs attached to themselves successfully.

  4. Configure MP-IBGP peer relationship between UPE and SPE, and between PE and SPE.
    # Configure UPE.
    <UPE> system-view
    [UPE] bgp 100
    [UPE-bgp] peer 2.2.2.9 as-number 100
    [UPE-bgp] peer 2.2.2.9 connect-interface loopback 1
    [UPE-bgp] ipv4-family vpnv4
    [UPE-bgp-af-vpnv4] peer 2.2.2.9 enable
    [UPE-bgp-af-vpnv4] quit
    [UPE-bgp] quit
    # Configure SPE.
    <SPE> system-view
    [SPE] bgp 100
    [SPE-bgp] peer 1.1.1.9 as-number 100
    [SPE-bgp] peer 1.1.1.9 connect-interface loopback 1
    [SPE-bgp] peer 3.3.3.9 as-number 100
    [SPE-bgp] peer 3.3.3.9 connect-interface loopback 1
    [SPE-bgp] ipv4-family vpnv4
    [SPE-bgp-af-vpnv4] peer 1.1.1.9 enable
    [SPE-bgp-af-vpnv4] peer 3.3.3.9 enable
    [SPE-bgp-af-vpnv4] quit
    [SPE-bgp] quit
    # Configure PE.
    <PE> system-view
    [PE] bgp 100
    [PE-bgp] peer 2.2.2.9 as-number 100
    [PE-bgp] peer 2.2.2.9 connect-interface loopback 1
    [PE-bgp] ipv4-family vpnv4
    [PE-bgp-af-vpnv4] peer 2.2.2.9 enable
    [PE-bgp-af-vpnv4] quit
    [PE-bgp] quit
  5. Configure SPE.
    # Configure VPN instances.
    [SPE] ip vpn-instance vpna
    [SPE-vpn-instance-vpna] ipv4-family
    [SPE-vpn-instance-vpna-af-ipv4] route-distinguisher 200:1
    [SPE-vpn-instance-vpna-af-ipv4] vpn-target 1:1
    [SPE-vpn-instance-vpna-af-ipv4] quit
    [SPE-vpn-instance-vpna] quit
    # Specify a UPE for the SPE.
    [SPE] bgp 100
    [SPE-bgp] ipv4-family vpnv4
    [SPE-bgp-af-vpnv4] peer 1.1.1.9 upe
    # Advertise the default route of VPN instances to UPE.
    [SPE-bgp-af-vpnv4] peer 1.1.1.9 default-originate vpn-instance vpna
    [SPE-bgp-af-vpnv4] quit
  6. Verify the configuration.
    After the configuration, CE1 does not have a route to the network segment of the interface on CE2, but has a default route with the next hop to UPE. The CE2 has the route to the network segment of the interface on CE1. Therefore, CE1 and CE2 can ping through each other using the ping ip-addresscommand.
    <CE1> display ip routing-table
    Route Flags: R - relay, D - download to fib
    ------------------------------------------------------------------------------
    Routing Tables: Public
             Destinations : 5        Routes : 5
    Destination/Mask  Proto  Pre  Cost       Flags  NextHop             Interface
          0.0.0.0/0   BGP    255  0              D  10.1.1.2            GigabitEthernet1/0/0
         10.1.1.0/24  Direct 0    0              D  10.1.1.1            GigabitEthernet1/0/0
         10.1.1.1/32  Direct 0    0              D  127.0.0.1           InLoopBack0
         127.0.0.0/8  Direct 0    0              D  127.0.0.1           InLoopBack0
        127.0.0.1/32  Direct 0    0              D  127.0.0.1           InLoopBack0
    
    
    [CE1] ping 10.2.1.1
      PING 10.2.1.1: 56  data bytes, press CTRL_C to break
        Reply from 10.2.1.1: bytes=56 Sequence=1 ttl=253 time=85 ms
        Reply from 10.2.1.1: bytes=56 Sequence=2 ttl=253 time=70 ms
        Reply from 10.2.1.1: bytes=56 Sequence=3 ttl=253 time=57 ms
        Reply from 10.2.1.1: bytes=56 Sequence=4 ttl=253 time=66 ms
        Reply from 10.2.1.1: bytes=56 Sequence=5 ttl=253 time=55 ms
      --- 10.2.1.1 ping statistics ---
        5 packet(s) transmitted
        5 packet(s) received
        0.00% packet loss
        round-trip min/avg/max = 55/66/85 ms
    
    
    [CE2] display ip routing-table
    Route Flags: R - relay, D - download to fib
    ------------------------------------------------------------------------------
    Routing Tables: Public
             Destinations : 5        Routes : 5
    Destination/Mask  Proto  Pre  Cost         Flags  NextHop                Interface
         10.1.1.0/24  BGP    255  0                D  10.2.1.2               GigabitEthernet1/0/0
         10.2.1.0/24  Direct 0    0                D  10.2.1.1               GigabitEthernet1/0/0
         10.2.1.1/32  Direct 0    0                D  127.0.0.1              InLoopBack0
         127.0.0.0/8  Direct 0    0                D  127.0.0.1              InLoopBack0
        127.0.0.1/32  Direct 0    0                D  127.0.0.1              InLoopBack0
    Run the display bgp vpnv4 all routing-table command on UPE to see a default route of VPN instances vpna with the next hop to SPE.
    [UPE] display bgp vpnv4 all routing-table
    
    
     Local AS number : 100
    
    
     BGP Local router ID is 1.1.1.9
     Status codes: * - valid, > - best, d - damped,
                   h - history,  i - internal, s - suppressed, S - Stale
                   Origin : i - IGP, e - EGP, ? - incomplete
    
    
     Total number of routes from all PE: 3
     Route Distinguisher: 100:1
    
    
          Network            NextHop        MED        LocPrf    PrefVal Path/Ogn
    
     *>   10.1.1.0/24        0.0.0.0         0                     0      ?
     *                       10.1.1.1        0                     0      65410?
    
     Route Distinguisher: 200:1
    
    
          Network            NextHop        MED        LocPrf    PrefVal Path/Ogn
    
     *>i  0.0.0.0            2.2.2.9         0          100        0      i
    
     VPN-Instance vpn1, router ID 1.1.1.9:
    
     Total Number of Routes: 5
          Network            NextHop        MED        LocPrf    PrefVal Path/Ogn
    
     *>i  0.0.0.0            2.2.2.9         0          100        0      i
     *>   10.1.1.0/24        0.0.0.0         0                     0      ?
     *                       10.1.1.1        0                     0      65410?

Configuration Files

  • Configuration file of CE1
    #
     sysname CE1
    #
    interface GigabitEthernet1/0/0
     undo shutdown
     ip address 10.1.1.1 255.255.255.0
    #
    bgp 65410
     peer 10.1.1.2 as-number 100
     #
     ipv4-family unicast
      undo synchronization
      import-route direct
      peer 10.1.1.2 enable
    # 
    return
  • Configuration file of UPE
    #
     sysname UPE
    #
    ip vpn-instance vpna
     ipv4-family
      route-distinguisher 100:1
      vpn-target 1:1 export-extcommunity
      vpn-target 1:1 import-extcommunity
    #
     mpls lsr-id 1.1.1.9
     mpls
    #
    mpls ldp
    #
    interface GigabitEthernet1/0/0
     undo shutdown
     ip binding vpn-instance vpna
     ip address 10.1.1.2 255.255.255.0
    #
    interface Pos2/0/0
     link-protocol ppp
     undo shutdown
     ip address 172.1.1.1 255.255.255.0
     mpls
     mpls ldp
    #
    interface LoopBack1
     ip address 1.1.1.9 255.255.255.255
    #
    bgp 100
     peer 2.2.2.9 as-number 100
     peer 2.2.2.9 connect-interface LoopBack1
     #
     ipv4-family unicast
      undo synchronization
      peer 2.2.2.9 enable
     #
     ipv4-family vpnv4
      policy vpn-target
      peer 2.2.2.9 enable
    #
     ipv4-family vpn-instance vpna
      peer 10.1.1.1 as-number 65410
      import-route direct
    #
    ospf 1
     area 0.0.0.0
      network 1.1.1.9 0.0.0.0
      network 172.1.1.0 0.0.0.255
    #
    return
  • Configuration file of SPE
    #
     sysname SPE
    #
    ip vpn-instance vpna
     ipv4-family
      route-distinguisher 200:1
      vpn-target 1:1 export-extcommunity
      vpn-target 1:1 import-extcommunity
    #
     mpls lsr-id 2.2.2.9
     mpls
    #
    mpls ldp
    #
    interface Pos1/0/0
     link-protocol ppp
     undo shutdown
     ip address 172.1.1.2 255.255.255.0
     mpls
     mpls ldp
    #
    interface Pos2/0/0
     link-protocol ppp
     undo shutdown
     ip address 172.2.1.1 255.255.255.0
     mpls
     mpls ldp
    #
    interface LoopBack1
     ip address 2.2.2.9 255.255.255.255
    #
    bgp 100
     peer 1.1.1.9 as-number 100
     peer 3.3.3.9 as-number 100
     peer 1.1.1.9 connect-interface LoopBack1
     peer 3.3.3.9 connect-interface LoopBack1
     #
     ipv4-family unicast
      undo synchronization
      peer 1.1.1.9 enable
      peer 3.3.3.9 enable
     #
     ipv4-family vpnv4
      policy vpn-target
      peer 1.1.1.9 enable
      peer 1.1.1.9 upe
      peer 1.1.1.9 default-originate vpn-instance vpna
      peer 3.3.3.9 enable
    #
    ospf 1
     area 0.0.0.0
      network 2.2.2.9 0.0.0.0
      network 172.1.1.0 0.0.0.255
      network 172.2.1.0 0.0.0.255
    #
    return
  • Configuration file of PE
    #
     sysname PE
    #
    ip vpn-instance vpna
     ipv4-family
      route-distinguisher 100:2
      vpn-target 1:1 export-extcommunity
      vpn-target 1:1 import-extcommunity
    #
     mpls lsr-id 3.3.3.9
     mpls
    #
    mpls ldp
    #
    interface GigabitEthernet1/0/0
     undo shutdown
     ip binding vpn-instance vpna
     ip address 10.2.1.2 255.255.255.0
    #
    interface Pos2/0/0
     link-protocol ppp
     undo shutdown
     ip address 172.2.1.2 255.255.255.0
     mpls
     mpls ldp
    #
    interface LoopBack1
     ip address 3.3.3.9 255.255.255.255
    #
    bgp 100
     peer 2.2.2.9 as-number 100
     peer 2.2.2.9 connect-interface LoopBack1
     #
     ipv4-family unicast
      undo synchronization
      peer 2.2.2.9 enable
     #
     ipv4-family vpnv4
      policy vpn-target
      peer 2.2.2.9 enable
    #
     ipv4-family vpn-instance vpna
      peer 10.2.1.1 as-number 65420
      import-route direct
    #
    ospf 1
     area 0.0.0.0
      network 3.3.3.9 0.0.0.0
      network 172.2.1.0 0.0.0.255
    #
    return
  • Configuration file of CE2
    #
     sysname CE2
    #
    interface GigabitEthernet1/0/0
     undo shutdown
     ip address 10.2.1.1 255.255.255.0
    #
    bgp 65420
     peer 10.2.1.2 as-number 100
     #
     ipv4-family unicast
      undo synchronization
      import-route direct
      peer 10.2.1.2 enable
    #
    return

No comments:

Post a Comment