Use EVPN Simplified CLIs on Catalyst 9000 Switches

Introduction

This document describes BGP EVPN VXLAN configurations using simplified CLIs on Catalyst 9000 Series Switches.

Prerequisites

Requirements

Cisco recommends that you have knowledge of these topics:

• BGP EVPN VxLAN concepts

Components Used

The information in this document is based on these software and hardware versions:

• Catalyst 9300
• Catalyst 9400
• Catalyst 9500
• Catalyst 9600
• Cisco IOS® XE 17.13.1 and later versions

The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, ensure that you understand the potential impact of any command.

Background Information

Today to configure BGP EVPN, CLIs are spread across multiple components with some redundancy, causing increased complexity and operational overhead.

In most cases, the EVI and VNI are assigned to a VLAN through a simple VLAN ID to EVI or VNI direct mapping approach. Auto-creating the EVI and VNI using the VLAN ID significantly simplifies the provisioning process.

EVPN L2 Service Profile

Using a pre-defined EVPN profile to auto create the EVIs and VNIs.

• When configuring the ‘member evpn-instance’ under vlan configuration without explicitly specify the EVI ID, the EVI ID and VNI is auto generated using the profile specified, if profile is not specified, the default profile is used.

vlan configuration <id-range>
  member evpn-instance [profile-name]

EVPN profiles represent a common set of characteristics shared by a group of VLANs.

• These common characteristics could be sharing the same replication type, EVI, VNI, route-target mappings, and so on.
• Once a VLAN is associated with an EVPN profile, the corresponding EVPN settings are auto-derived from the profile, and the EVI and VNI are auto-generated through the same mapping functionality.

EVPN Default and Named Profile

EVPN profiles simplify the provisioning process by auto-creating EVPN instances and VXLAN L2 VNIs from the default or a pre-defined named profile.

• The default L2 service profile does not require manual configuration. This profile is auto-created when referenced by a VLAN member evpn-instance.
• Named L2 service profiles define explicit configurations and must be configured before being referenced by a VLAN member evpn-instance.
• A new CLI mode ‘l2vpn evpn profile {default|<name>}’ is introduced to create the EVPN profile.

l2vpn evpn profile {default|<name>} 
  evi-base <id>               
  l2vni-base <id>
  replication-type {ingress|static {[ipv4_mcast_addr|ipv4_mcast_prefix] [ipv6_mcast_addr|ipv6_mcast_prefix]}}
  encapsulation {mpls|vxlan}
  default-gateway advertise {enable|disable}
  multicast advertise {enable|disable}
  ip local-learning {enable|disable}
  flooding-suppression address-resolution {enable|disable}
  re-originate route-type5
  local-routing {enable|disable}
  member evpn-instance [profile-name]

Configure

Mandatory NVE Interface

The auto created VNIs are hardcoded to be created under interface nve1, in other words, when using the simplified CLI, the interface nve1 has to be configured, and the ‘host-reachability protocol bgp’ has to be configured under interface nve1 as well.

interface nve1 
 source-interface Loopback0
 host-reachability protocol bgp

Default Profile

Named Profile

Verify

EVPN Profile

Use show l2vpn evpn profile to verify the profile creation, configurations and VLANs using the profile.

leaf1#show l2vpn evpn profile default detail
EVPN Profile (VLAN Based): default (auto)
  evpn id base: 0
  l2 vni base: 20000
  Encapsulation: vxlan
  Replication Type: Ingress
  IP Local Learn: Not set
  Flooding Suppression Address Resolution: Not set
  Adv. default-gateway: Not set
  Adv. Multicast: Not set
  RT5 Re-originate Flag: Disabled
  Local Routing: Not set
  vlan(s):
              101-102,111-114,131-132

Auto L2VNI

Use show derived-config interface nve1 to verify auto created L2VNIs.

leaf1#show derived-config int nve1  <-- Display the resulting derived config
Building configuration...

Derived configuration : 721 bytes
!
interface nve1
 source-interface Loopback2
 host-reachability protocol bgp
 member vni 20101 ingress-replication
 member vni 20102 ingress-replication
 member vni 20105 mcast-group 239.2.1.105
 member vni 20106 mcast-group 239.2.1.106
 member vni 20111 ingress-replication
 member vni 20112 ingress-replication
 member vni 20113 ingress-replication
 member vni 20114 ingress-replication
 member vni 20121 mcast-group 239.2.1.121
 member vni 20122 mcast-group 239.2.1.122
 member vni 20123 mcast-group 239.2.1.123
 member vni 20124 mcast-group 239.2.1.124
 member vni 20131 ingress-replication
 member vni 20132 ingress-replication

Note: This config is shown using "derived config" and does not appear in a standard "show run"

Auto EVI

Use show l2vpn evpn evi to verify the auto created EVI and corresponding profile.

leaf1#show l2vpn evpn evi 101 detail
EVPN instance:       101 (VLAN Based)
  Profile:           default
  RD:                1.1.1.2:32868 (auto)
  Import-RTs:        1:20101
  Export-RTs:        1:20101
  Per-EVI Label:     none
  State:             Established
  Replication Type:  Ingress (profile)
  Encapsulation:     vxlan (profile)
  IP Local Learn:    Enabled (global)
  Adv. Def. Gateway: Disabled (global)
  Re-originate RT5:  Disabled (profile)
  Adv. Multicast:    Enabled (global)
  AR Flood Suppress: Enabled (global)
  Vlan:              101
    Protected:       False
    Ethernet-Tag:    0
    State:           Established
    Flood Suppress:  Attached
    Core If:        
    Access If:      
    NVE If:         
    RMAC:            0000.0000.0000
    Core Vlan:       0
    L2 VNI:          20101
    L3 VNI:          0
    VTEP IP:         UNKNOWN
    Pseudoports:
      none

Additional CLI Simplification Example

L3 VRF simplification

A similar approach is used for the L3VNI and Core-VLAN for the VRF. See Use VNID to Auto Provision L3VNI, Core-SVI, Core-vlan on Catalyst 9000 Switches for the VRF simplification.

Also refer to this example:

Related Information

• Use VNID to Auto Provision L3VNI, Core-SVI, Core-vlan on Catalyst 9000 Switches