VXLAN and BGP EVPN Configuration Guide for Dell EMC SmartFabric OS10 Release 10.5.2

Configure BGP EVPN for VXLAN

Configuration

1. Configure BGP to advertise EVPN routes.
   EVPN requires that you establish MP-BGP sessions between leaf and spine nodes in the underlay network. On each spine and leaf node, configure at least two BGP peering sessions:

   • A directly connected BGP peer in the underlay network to advertise VTEP and Loopback IP addresses using the IPv4 unicast address family.
   • A BGP peer in the overlay network to advertise overlay information using the EVPN address family. In BGP peer sessions in the overlay, activate only the EVPN address family.
   For each BGP peer session in the underlay network:

   1. Create a BGP instance in CONFIGURATION mode. You enter router BGP configuration mode.

      router bgp as-number

   2. Assign an IP address to the BGP instance in ROUTER-BGP mode.

      router-id ip-address

   3. Enter IPv4 address-family configuration mode from ROUTER-BGP mode.

      address-family ipv4 unicast

   4. Advertise the IPv4 prefix to BGP peers in the address family in ROUTER-BGP-ADDRESS-FAMILY mode.

      network ip-address/mask

   5. Return to ROUTER-BGP mode.

      exit

   6. Configure the BGP peer address in ROUTER-BGP mode.

      neighbor ip-address

   7. Assign the BGP neighbor to an autonomous system in ROUTER-BGP-NEIGHBOR mode.

      remote-as as-number

   8. Enable the peer session with the BGP neighbor in ROUTER-BGP-NEIGHBOR mode.

      no shutdown

   9. Return to ROUTER-BGP mode.

      exit

   For each BGP peer session in the overlay network:

   1. Configure the BGP peer using its Loopback IP address on the VTEP in ROUTER-BGP mode.

      neighbor loopback-ip-address

   2. Assign the BGP neighbor Loopback address to the autonomous system in ROUTER-BGP-NEIGHBOR mode. The neighbor Loopback IP address is the source interface on the remote VTEP.

      remote-as as-number

   3. Use the local Loopback address as the source address in BGP packets sent to the neighbor in ROUTER-BGP-NEIGHBOR mode.

      update-source loopback0

   4. Send an extended community attribute to the BGP neighbor in ROUTER-BGP-NEIGHBOR mode.

      send-community extended

   5. Enable the peer session with the BGP neighbor in ROUTER-BGP-NEIGHBOR mode.

      no shutdown

   6. Configure the L2 VPN EVPN address family for VXLAN host-based routing to the BGP peer in ROUTER-BGP-NEIGHBOR mode.

      address-family l2vpn evpn

   7. Enable the exchange of L2VPN EVPN addresses with the BGP peer in ROUTER-BGP-NEIGHBOR mode.

      activate

   8. Return to ROUTER-BGP mode.

      exit

   9. Enter IPv4 address-family configuration mode from ROUTER-BGP mode.

      address-family ipv4 unicast

   10. Disable the exchange of IPv4 addresses with BGP peers in ROUTER-BGP mode.

       no activate

   11. Return to ROUTER-BGP-NEIGHBOR mode.

       exit

   12. (Optional) If all the leaf switches are configured in the same ASN:
       • On each leaf switch, enter L2VPN EVPN address-family configuration mode from ROUTER-BGP-NEIGHBOR mode. Activate the exchange of L2VPN EVPN addresses with BGP peers. Configure the switch to accept a route with the local AS number in updates received from a peer in ROUTER-BGP-NEIGHBOR-AF mode.

         OS10(config-router-bgp-neighbor)# address-family l2vpn evpn
         OS10(config-router-neighbor-af)# activate
         OS10(config-router-neighbor-af)# allowas-in 1
         OS10(config-router-neighbor-af)# exit
         OS10(config-router-bgp-neighbor)# exit

       • On each spine switch, disable sender-side loop detection to leaf switch neighbors in ROUTER-BGP-NEIGHBOR-AF mode.

         OS10(conf-router-neighbor)# address-family ipv4 unicast
         OS10(conf-router-neighbor-af)# no sender-side-loop-detection
         OS10(conf-router-neighbor-af)# exit

   13. (Optional) In a VLT deployment, on each leaf switch, configure the number of multi-hop peer routes in ROUTER-BGP-NEIGHBOR mode to ensure that the BGP EVPN peer session establishes over the VLT VTEP peer if all local links to spine switches are down.

       OS10(conf-router-neighbor)# ebgp-multihop 1

2. Configure EVPN.

   An EVPN instance (EVI) spans across the VTEPs that participate in the EVPN. In OS10, configure an EVI in auto-EVI or manual configuration mode.

   • Auto-EVI mode
     1. Enable the EVPN control plane in CONFIGURATION mode.

        evpn

     2. Enable auto-EVI creation for overlay virtual networks in EVPN mode. Auto-EVI creation is supported only if BGP EVPN is used with 2-byte AS numbers and if at least one BGP instance is enabled with the EVPN address family. No further manual configuration is allowed in auto-EVI mode.

        auto-evi

   • Manual EVI configuration mode
     1. Enable the EVPN control plane in CONFIGURATION mode.

        evpn

     2. Manually create an EVPN instance in EVPN mode. The range is from 1 to 65535.

        evi id

     3. Configure the Route Distinguisher in EVPN EVI mode.

        rd {A.B.C.D:[1-65535] | auto}

        Where:
        • rd A.B.C.D:[1-65535] configures the RD with a 4-octet IPv4 address then a 2-octet-number.
        • rd auto automatically generates the RD.
     4. Configure the RT values in EVPN EVI mode.

        route-target {auto | value [asn4] {import | export | both}}

        Where:
        • route-target auto auto-configures an import and export value for EVPN routes.
        • route-target value [asn4]{import | export | both} configures an import or export value for EVPN routes in the format 2-octet-ASN:4-octet-number or 4-octet-ASN:2-octet-number.
          • The 2-octet ASN number is 1 to 65535.
          • The 4-octet ASN number is 1 to 4294967295.
          To configure the same value for the RT import and export values, use the both option. asn4 advertises a 2-byte AS number as a 4-byte route target value. If you specify the asn4 option, configure the VXLAN network ID associated with the EVPN instance in EVPN EVI mode, from 1 to 16,777,215. Configure the same VNI value that you configure for the VXLAN virtual network. For more information, see Configure VXLAN.

          vni vni

3. Verify the BGP EVPN configuration.

Display the EVPN instance configuration

OS10# show evpn evi 1
EVI : 65447, State : up
  Bridge-Domain       : (Virtual-Network)100, (VNI)100
  Route-Distinguisher : 1:110.111.170.102:65447(auto)
  Route-Targets       : 0:101:268435556(auto) both
  Inclusive Multicast : 110.111.170.107

Display the VXLAN overlay for the EVPN instance

OS10# show evpn vxlan-vni
VXLAN-VNI  EVI  Virtual-Network-Instance
100001     1    1
100010     2    2

Display the BGP neighbors in the EVPN instances

OS10# show ip bgp neighbors 110.111.170.102
BGP neighbor is 110.111.170.102, remote AS 100, local AS 100 internal link
BGP version 4, remote router ID 110.111.170.102
BGP state ESTABLISHED, in this state for 04:02:59
Last read 00:21:21 seconds
Hold time is 180, keepalive interval is 60 seconds
Configured hold time is 180, keepalive interval is 60 seconds
Fall-over disabled

Received 311 messages
  2 opens, 2 notifications, 3 updates
  304 keepalives, 0 route refresh requests
Sent 307 messages
  4 opens, 0 notifications, 2 updates
  301 keepalives, 0 route refresh requests
Minimum time between advertisement runs is 30 seconds
Minimum time before advertisements start is 0 seconds
Capabilities received from neighbor for IPv4 Unicast:
  MULTIPROTO_EXT(1)
  ROUTE_REFRESH(2)
  CISCO_ROUTE_REFRESH(128)
  4_OCTET_AS(65)
  MP_L2VPN_EVPN
Capabilities advertised to neighbor for IPv4 Unicast:
  MULTIPROTO_EXT(1)
  ROUTE_REFRESH(2)
  CISCO_ROUTE_REFRESH(128)
  4_OCTET_AS(65)
  MP_L2VPN_EVPN
Prefixes accepted 1, Prefixes advertised 1
Connections established 2; dropped 0
Last reset never
Prefixes ignored due to:
  Martian address 0, Our own AS in AS-PATH 0
  Invalid Nexthop 0, Invalid AS-PATH length 0
  Wellknown community 0, Locally originated 0

Local host: 110.111.180.195, Local port: 43081
Foreign host: 110.111.170.102, Foreign port: 179

Display the BGP L2VPN EVPN address family

OS10# show ip bgp l2vpn evpn
BGP local RIB : Routes to be Added , Replaced , Withdrawn
BGP local router ID is 110.111.170.102
Status codes: s suppressed, S stale, d dampened, h history, * valid, > best
Path source: I - internal, a - aggregate, c - confed-external,
r - redistributed/network, S - stale
Origin codes: i - IGP, e - EGP, ? - incomplete
      Network                                 Next Hop     Metric LocPrf Weight  Path
*>r    Route distinguisher: 110.111.170.102:65447
[3]:[0]:[32]:[110.111.170.102]/152           110.111.170.102  0   100   32768   ?
*>    Route distinguisher: 110.111.170.107:64536
[3]:[0]:[32]:[110.111.170.107]/152           110.111.170.107  0   100   0     100 101 ?

Display the EVPN routes for host MAC addresses

OS10# show evpn mac 
Type  -(lcl): Local (rmt): remote

EVI     Mac-Address        Type      Seq-No  Interface/Next-Hop
50      00:00:00:aa:aa:aa  rmt       0       55.1.1.3
50      00:00:00:cc:cc:cc  lcl       0       ethernet1/1/8:1

OS10# show evpn mac evi 50
Type  -(lcl): Local (rmt): remote

EVI     Mac-Address        Type      Seq-No  Interface/Next-Hop
50      00:00:00:aa:aa:aa  rmt       0       55.1.1.3
50      00:00:00:cc:cc:cc  lcl       0       ethernet1/1/8:1