Aruba VXLAN Configuration Guide

Brand: Aruba

Model: VXLAN

Category: Networking

Type: Configuration Guide

HPE FlexFabric 5940 & 5930 Switch Series

VXLAN Configuration Guide

art number: 5200-4888c

Software

version: Release 2609 and later

Document version: 6W103-20200310

The information contained herein is subject to change without notice. The only warranties for Hewlett Packard

Enterprise products and services are set forth in the express warranty statements accompanying such

products and services. Nothing herein should be construed as constituting an additional warranty. Hewlett

Packard Enterprise shall not be liable for technical or editorial errors or omissions contained herein.

Confidential computer software. Valid license from Hewlett Packard Enterprise required for possession, use, or

copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software

Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s

standard commercial license.

Links to third-party websites take you outside the Hewlett Packard Enterprise website. Hewlett Packard

Enterprise has no control over and is not responsible for information outside the Hewlett Packard Enterprise

website.

Acknowledgments

Intel®, Itanium®, Pentium®, Intel Inside®, and the Intel Inside logo are trademarks of Intel Corporation in the

United States and other countries.

Microsoft® and Windows® are either registered trademarks or trademarks of Microsoft Corporation in the

United States and/or other countries.

Adobe® and Acrobat® are trademarks of Adobe Systems Incorporated.

Java and Oracle are registered trademarks of Oracle and/or its affiliates.

UNIX® is a registered trademark of The Open Group.

Contents

VXLAN overview ···························································································· 1

VXLAN network model ······································································································································· 1

VXLAN packet format········································································································································· 2

Working mechanisms ········································································································································· 3

Assignment of traffic to VXLANs ················································································································ 3

MAC learning ············································································································································· 3

Access modes of VSIs ······························································································································· 4

Traffic forwarding ······································································································································· 5

ARP and ND flood suppression ························································································································· 8

VXLAN IP gateways ··········································································································································· 9

Protocols and standards ···································································································································· 9

Configuring basic VXLAN features ······························································· 10

VXLAN configuration task list ··························································································································· 10

Setting the VXLAN hardware resource mode ·································································································· 11

Overview ·················································································································································· 11

Configuration restrictions and guidelines ································································································· 11

Configuration procedure ··························································································································· 11

Creating a VXLAN on a VSI ····························································································································· 11

Configuration procedure ··························································································································· 12

Configuring a VXLAN tunnel ···························································································································· 12

Assigning VXLAN tunnels to a VXLAN ············································································································ 13

Assigning customer frames to a VSI ················································································································ 14

Configuration restrictions and guidelines ································································································· 14

Mapping a static Ethernet service instance to a VSI ················································································ 14

Mapping dynamic Ethernet service instances to VSIs ············································································· 16

Configuring VLAN-based VXLAN assignment ························································································· 17

Managing MAC address entries ······················································································································· 18

Configuration restrictions and guidelines ································································································· 18

Configuring static MAC address entries ··································································································· 19

Disabling local-MAC address learning ····································································································· 19

Disabling remote-MAC address learning ································································································· 20

Setting the MAC learning priority of an Ethernet service instance ··························································· 20

Enabling local-MAC change logging ········································································································ 21

Enabling software-based MAC learning on an interface ·········································································· 21

Configuring VXLAN over VXLAN ····················································································································· 22

Configuring a multicast-mode VXLAN ············································································································· 23

Configuring a VTEP using the PIM method ····························································································· 23

Configuring a VTEP using the IGMP host method ··················································································· 24

Confining floods to the local site ······················································································································ 24

Setting the destination UDP port number of VXLAN packets ·········································································· 25

Configuring VXLAN packet check ···················································································································· 25

Enabling default VXLAN decapsulation ··········································································································· 26

Enabling ARP flood suppression······················································································································ 26

Enabling ND flood suppression ························································································································ 27

Disabling remote ARP or ND learning for VXLANs ·························································································· 27

Enabling VXLAN packet statistics ···················································································································· 28

Enabling packet statistics for a VSI ·········································································································· 28

Enabling packet statistics for Ethernet service instances ········································································ 28

Enabling packet statistics for VXLAN tunnels ·························································································· 29

Testing the reachability of a remote VM ·········································································································· 30

Displaying and maintaining VXLANs················································································································ 30

VXLAN configuration examples ······················································································································· 31

Unicast-mode VXLAN configuration example ·························································································· 31

Multicast-mode VXLAN configuration example ························································································ 36

Configuring VXLAN IP gateways ································································· 43

VXLAN IP gateways separated from VTEPs ··························································································· 43

Centralized VXLAN IP gateway deployment ···························································································· 44

Centralized VXLAN gateway group deployment ······················································································ 45

Distributed VXLAN IP gateway deployment ····························································································· 46

Feature and hardware compatibility ················································································································· 49

Configuration restrictions and guidelines ········································································································· 50

Configuration prerequisites ······························································································································ 51

Configuring a centralized VXLAN IP gateway ·································································································· 51

Configuring a centralized VXLAN IP gateway group························································································ 51

Configuration restrictions and guidelines ································································································· 51

Configuring a VTEP group ······················································································································· 52

Specifying a VTEP group as the gateway for an access layer VTEP ······················································ 52

Configuring a distributed VXLAN IP gateway ·································································································· 53

Configuration restrictions and guidelines ································································································· 53

Configuration prerequisites ······················································································································ 53

Configuration procedure ··························································································································· 53

Adding a static ARP entry ································································································································ 54

Configuring a VSI interface ······························································································································ 55

Enabling packet statistics for a VSI interface ··································································································· 55

Displaying and maintaining VXLAN IP gateway ······························································································ 56

VXLAN IP gateway configuration examples····································································································· 56

Centralized VXLAN IP gateway configuration example ··········································································· 56

Centralized VXLAN IP gateway group configuration example ································································· 61

Distributed VXLAN IPv4 gateway configuration example ········································································ 65

Distributed VXLAN IPv6 gateway configuration example ········································································ 74

Configuring VXLAN-DCI ·············································································· 85

VXLAN-DCI network model ······················································································································ 85

Working mechanisms ······························································································································· 85

Feature and hardware compatibility ················································································································· 88

VXLAN-DCI configuration task list ··················································································································· 88

Configuring a VXLAN-DCI tunnel ····················································································································· 88

Assigning a VXLAN-DCI tunnel to a VXLAN ···································································································· 89

Specifying a gateway interface for a VSI ········································································································· 91

Enabling packet statistics for manually created VXLAN-DCI tunnels ······························································ 91

Displaying and maintaining VXLAN-DCI ·········································································································· 91

VXLAN-DCI configuration example ·················································································································· 92

Network requirements ······························································································································ 92

Configuration procedure ··························································································································· 92

Verifying the configuration ························································································································ 97

Configuring the VTEP as an OVSDB VTEP ··············································· 100

Protocols and standards ································································································································ 100

OVSDB VTEP configuration task list·············································································································· 100

Setting up an OVSDB connection to a controller ··························································································· 101

Configuration restrictions and guidelines ······························································································· 101

Configuring active SSL connection settings ··························································································· 101

Configuring passive SSL connection settings ························································································ 102

Configuring active TCP connection settings ·························································································· 102

Configuring passive TCP connection settings ························································································ 102

Enabling the OVSDB server··························································································································· 103

Enabling the OVSDB VTEP service ··············································································································· 103

Specifying a global source address for VXLAN tunnels ················································································· 103

Specifying a VTEP access port ······················································································································ 103

Enabling flood proxy on multicast VXLAN tunnels ························································································· 104

iii

OVSDB VTEP configuration examples ·········································································································· 104

Unicast-mode VXLAN configuration example ························································································ 104

Flood proxy VXLAN configuration example ··························································································· 107

Document conventions and icons ······························································ 112

Conventions ··················································································································································· 112

Network topology icons ·································································································································· 113

Support and other resources ····································································· 114

Accessing Hewlett Packard Enterprise Support····························································································· 114

Accessing updates ········································································································································· 114

Websites ················································································································································ 115

Customer self repair ······························································································································· 115

Remote support ······································································································································ 115

Documentation feedback ······················································································································· 115

Index ·········································································································· 117

VXLAN overview

Virtual eXtensible LAN (VXLAN) is a MAC-in-UDP technology that provides Layer 2 connectivity

between distant network sites across an IP network. VXLAN is typically used in data centers for

multitenant services.

VXLAN provides the following benefits:

•

Support for more virtual switched domains than VLANs—Each VXLAN is uniquely

identified by a 24-bit VXLAN ID. The total number of VXLANs can reach 16777216 (224). This

specification makes VXLAN a better choice than 802.1Q VLAN to isolate traffic for VMs.

•

Easy deployment and maintenance—VXLAN requires deployment only on the edge devices

of the transport network. Devices in the transport network perform typical Layer 3 forwarding.

The device supports only IPv4-based VXLAN. IPv6-based VXLAN is not supported.

VXLAN network model

As shown in Figure 1, a VXLAN is a virtual Layer 2 network (known as the overlay network) built on

top of an existing physical Layer 3 network (known as the underlay network). The overlay network

encapsulates inter-site Layer 2 frames into VXLAN packets and forwards the packets to the

destination along the Layer 3 forwarding paths provided by the underlay network. The underlay

network is transparent to tenants, and geographically dispersed sites of a tenant are merged into a

Layer 2 network.

The transport edge devices assign VMs to different VXLANs, and then forward traffic between sites

for VMs by using VXLAN tunnels.

The transport edge devices are VXLAN tunnel endpoints (VTEP). They can be servers that host VMs

or independent network devices.

An HPE VTEP uses VSIs and VXLAN tunnels to provide VXLAN services.

•

VSI—A virtual switch instance is a virtual Layer 2 switched domain. Each VSI provides

switching services only for one VXLAN. VSIs learn MAC addresses and forward frames

independently of one another. VMs in different sites have Layer 2 connectivity if they are in the

same VXLAN.

•

VXLAN tunnel—Logical point-to-point tunnels between VTEPs over the transport network.

Each VXLAN tunnel can trunk multiple VXLANs.

VTEPs encapsulate VXLAN traffic in the VXLAN, outer UDP, and outer IP headers. The devices in

the transport network forward VXLAN traffic only based on the outer IP header.

Figure 1 VXLAN network model

VXLAN packet format

As shown in Figure 2, a VTEP encapsulates a frame in the following headers:

•

8-byte VXLAN header—VXLAN information for the frame.

 Flags—If the I bit is 1, the VXLAN ID is valid. If the I bit is 0, the VXLAN ID is invalid. All

other bits are reserved and set to 0.

 24-bit VXLAN ID—Identifies the VXLAN of the frame. It is also called the virtual network

identifier (VNI).

•

8-byte outer UDP header for VXLAN—The default VXLAN destination UDP port number is

4789.

•

20-byte outer IP header—Valid addresses of VTEPs or VXLAN multicast groups on the

transport network. Devices in the transport network forward VXLAN packets based on the outer

IP header.

Figure 2 VXLAN packet format

Underlay network

Overlay network

VTEP 1 VTEP 2

Server Site 2

Server

Site 1

VXLAN tunnel

Transport

network

VSI/VXLAN 10

VSI/VXLAN 20

VSI/VXLAN 10

VSI/VXLAN 20

Original Layer 2 frame

Outer UDP

header VXLAN

header

Outer IP header

Flags

RRRRIRRR Reserved

VXLAN ID Reserved

Working mechanisms

The VTEP uses the following process to forward an inter-site frame:

1. Assigns the frame to its matching VXLAN if the frame is sent between sites.

2. Performs MAC learning on the VXLAN's VSI.

3. Forwards the frame through VXLAN tunnels.

This section describes this process in detail. For intra-site frames in a VSI, the system performs

typical Layer 2 forwarding, and it processes 802.1Q VLAN tags as described in "Access modes of

VSIs."

Assignment of traffic to VXLANs

Traffic from the local site to a remote site

The VTEP uses the following methods to assign customer frames to a VXLAN:

•

Ethernet service instance-to-VSI mapping—This method uses the frame match criterion of

an Ethernet service instance to match a list of VLANs on a site-facing Layer 2 interface. The

frame match criterion specifies the characteristics of traffic from the VLANs, such as tagging

status and VLAN IDs. The VTEP assigns customer traffic to a VXLAN by mapping the Ethernet

service instance to a VSI.

•

VLAN-based VXLAN assignment—This method maps a VLAN to a VXLAN. The VTEP

assigns all frames of the VLAN to the VXLAN.

An Ethernet service instance is identical to an attachment circuit (AC) in L2VPN.

As shown in Figure 3, Ethernet service instance 1 matches VLAN 2 and is mapped to VSI A (VXLAN

10). When a frame from VLAN 2 arrives, the VTEP assigns the frame to VXLAN 10, and looks up VSI

A's MAC address table for the outgoing interface.

Figure 3 Identifying traffic from the local site

Traffic from a remote site to the local site

When a frame arrives at a VXLAN tunnel, the VTEP uses the VXLAN ID in the frame to identify its

VXLAN.

MAC learning

The VTEP performs source MAC learning on the VSI as a Layer 2 switch.

•

For traffic from the local site to the remote site, the VTEP learns the source MAC address before

VXLAN encapsulation.

Server

Service instance 1:

VLAN 2 VSI A

VXLAN 10

VLAN 2

VM 1

VM 2

VM 3

Service instance 2:

VLAN 3

Service instance 3:

VLAN 4

VLAN 3

VLAN 4

VSI B

VXLAN 20

VSI C

VXLAN 30

VTEP

•

For traffic from the remote site to the local site, the VTEP learns the source MAC address after

removing the VXLAN header.

A VSI's MAC address table includes the following types of MAC address entries:

•

Local MAC—MAC entries learned from the local site. The outgoing interfaces for the MAC

address entries are site-facing interfaces.

 Static—Manually added MAC entries.

 Dynamic—Dynamically learned MAC entries.

•

Remote MAC—MAC entries learned from a remote site. The outgoing interfaces for the MAC

address entries are VXLAN tunnel interfaces.

 Static—Manually added MAC entries.

 Dynamic—MAC entries learned in the data plane from incoming traffic on VXLAN tunnels.

The learned MAC addresses are contained in the inner Ethernet header.

 OpenFlow—MAC entries issued by a remote controller through OpenFlow.

 OVSDB—MAC entries issued by a remote controller through OVSDB.

 EVPN—MAC entries advertised through EVPN.

The following shows the priority order of different types of remote MAC address entries:

a. Static MAC address entries, and MAC address entries issued by a remote controller

through OpenFlow or OVSDB. These types of entries have the same priority and overwrite

each other.

b. MAC address entries advertised through BGP EVPN.

c. Dynamic MAC address entries.

Access modes of VSIs

The access mode of a VSI determines how the VTEP processes the 802.1Q VLAN tags in the

Ethernet frames.

VLAN access mode

In this mode, Ethernet frames received from or sent to the local site must contain 802.1Q VLAN tags.

•

For an Ethernet frame received from the local site, the VTEP removes all its 802.1Q VLAN tags

before forwarding the frame.

•

For an Ethernet frame destined for the local site, the VTEP adds 802.1Q VLAN tags to the

frame before forwarding the frame.

In this mode, VXLAN packets sent between sites do not contain 802.1Q VLAN tags. You can use

different 802.1Q VLANs to provide the same service in different sites.

By default, the access mode of a VSI is VLAN. The following sections describe traffic forwarding

processes in VLAN access mode.

Ethernet access mode

The VTEP does not process the 802.1Q VLAN tags of Ethernet frames received from or sent to the

local site.

•

For an Ethernet frame received from the local site, the VTEP forwards the frame with the

802.1Q VLAN tags intact.

•

For an Ethernet frame destined for the local site, the VTEP forwards the frame without adding

802.1Q VLAN tags.

In Ethernet access mode, VXLAN packets sent between VXLAN sites contain 802.1Q VLAN tags.

You must use the same VLAN to provide the same service between sites.

Traffic forwarding

A VTEP uses the following processes to forward traffic at Layer 2:

•

Unicast process—Applies to destination-known unicast traffic.

•

Flood process—Applies to multicast, broadcast, and unknown unicast traffic.

When the VTEP forwards VXLAN traffic, it processes the 802.1Q tag in the inner Ethernet header

depending on the VSI access mode (VLAN or Ethernet mode). In VLAN access mode, sites can use

different VLANs to provide the same service. For more information, see "Access modes of VSIs."

Unicast

The following process (see Figure 4) applies to a known unicast frame between sites:

1. The source VTEP encapsulates the Ethernet frame in the VXLAN/UDP/IP header.

In the outer IP header, the source IP address is the source VTEP's VXLAN tunnel source IP

address. The destination IP address is the VXLAN tunnel destination IP address.

2. The source VTEP forwards the encapsulated packet out of the outgoing VXLAN tunnel

interface found in the VSI's MAC address table.

3. The intermediate transport devices (P devices) forward the frame to the destination VTEP by

using the outer IP header.

4. The destination VTEP removes the headers on top of the inner Ethernet frame. It then performs

MAC address table lookup in the VXLAN's VSI to forward the frame out of the matching

outgoing interface.

Figure 4 Inter-site unicast

Flood

The VTEP floods a broadcast, multicast, or unknown unicast frame to all site-facing interfaces and

VXLAN tunnels in the VXLAN, except for the incoming interface.

VXLAN supports the following modes for flood traffic:

•

Unicast mode—Also called head-end replication. The source VTEP replicates the flood frame,

and then sends one replica to the destination IP address of each VXLAN tunnel in the VXLAN.

See Figure 5.

•

Multicast mode—Also called tandem replication. The source VTEP sends the flood frame in a

multicast VXLAN packet destined for a multicast group address. Transport network devices

VTEP 1 VTEP 2

Transport

network

Server 1

VM 1

VM 2

VM 3

Server 3

VM 7

VM 8

VM 9

MAC Table on VTEP 1

VXLAN/VSI MAC Interface

VXLAN 10/VSI A MAC 1

VXLAN 10/VSI A MAC 7 Tunnel 1

Server 2

VM 4

VM 5

VM 6

XGE1/0/1

XGE1/0/2

MAC Table on VTEP 2

VXLAN/VSI MAC Interface

VXLAN 10/VSI A MAC 1 Tunnel 1

VXLAN 10/VSI A MAC 7 XGE1/0/1, VLAN 20

XGE1/0/1

VXLAN tunnel 1

XGE1/0/1, VLAN 2

replicate and forward the packet to remote VTEPs based on their multicast forwarding entries.

See Figure 6.

•

Flood proxy mode—The source VTEP sends the flood frame in a VXLAN packet over a

VXLAN tunnel to a flood proxy server. The flood proxy server replicates and forwards the packet

to each remote VTEP through its VXLAN tunnels. See Figure 7.

The flood proxy mode applies to VXLANs that have many sites. This mode reduces flood traffic

in the transport network without using a multicast protocol. To use a flood proxy server, you

must set up a VXLAN tunnel to the server on each VTEP.

NOTE:

The flood proxy mode is typically used in SDN transport networks that have a flood proxy server

For

VTEPs to forward packets based on the

MAC address table issued by an SDN controller, you

must

perform the following tasks on the VTEPs:

•

Disable remote-MAC address learning by using the vxlan tunnel mac-learning disable

command.

•

Disable source MAC check on all transport-facing interfaces by using the undo mac-address

static source-check enable command. If the VTEP is an IRF fabric, you must also disable the

feature on all IRF ports.

Each destination VTEP floods the inner Ethernet frame to all the site-facing interfaces in the VXLAN.

To avoid loops, the destination VTEPs do not flood the frame to VXLAN tunnels.

Figure 5 Unicast mode

VTEP 1 VTEP 2

Transport network

Server 1

VM 1

VM 2

VM 3

Server 3

VM 7

VM 8

VM 9

Server 2

VM 4

VM 5

VM 6

VXLAN tunnel

VTEP 3

VXLAN tunnel

Server 4

VM 10

VM 11

VM 12

Replicate and

encapsulate

Figure 6 Multicast mode

Figure 7 Flood proxy mode

VTEP 1 VTEP 2

Transport network

Server 1

VM 1

VM 2

VM 3

Server 3

VM 7

VM 8

VM 9

Server 2

VM 4

VM 5

VM 6

VXLAN tunnel

VTEP 3

VXLAN tunnel

Server 4

VM 10

VM 11

VM 12

Replicate

Encapsulate with

multicast address

VTEP 1 VTEP 2

Flood proxy

server

Server 1

VM 1

VM 2

VM 3

Server 3

VM 7

VM 8

VM 9

Server 2

VM 4

VM 5

VM 6

VXLAN tunnel

VTEP 3

VXLAN tunnel

Server 4

VM 10

VM 11

VM 12

Encapsulate

with flood proxy

server address

VXLAN tunnel

Replicate and forward packet

Source: Flood proxy server

Destination: Each remote VTEP

Transport

network

ARP and ND flood suppression

IMPORTANT:

ND flood suppression is available in Release 2612P06 and later.

ARP or ND flood suppression reduces ARP request broadcasts or ND request multicasts by enabling

the VTEP to reply to ARP or ND requests on behalf of VMs.

As shown in Figure 8, this feature snoops ARP or ND packets to populate the ARP or ND flood

suppression table with local and remote MAC addresses. If an ARP or ND request has a matching

entry, the VTEP replies to the request on behalf of the VM. If no match is found, the VTEP floods the

request to both local and remote sites.

Figure 8 ARP flood suppression

The following uses ARP flood suppression as an example to explain the flood suppression workflow:

1. VM 1 sends an ARP request to obtain the MAC address of VM 7.

2. VTEP 1 creates a suppression entry for VM 1, and floods the ARP request in the VXLAN.

3. VTEP 2 and VTEP 3 de-encapsulate the ARP request. The VTEPs create a suppression entry

for VM 1, and broadcast the request in the local site.

4. VM 7 sends an ARP reply.

5. VTEP 2 creates a suppression entry for VM 7 and forwards the ARP reply to VTEP 1.

6. VTEP 1 de-encapsulates the ARP reply, creates a suppression entry for VM 7, and forwards the

ARP reply to VM 1.

7. VM 4 sends an ARP request to obtain the MAC address of VM 1 or VM 7.

8. VTEP 1 creates a suppression entry for VM 4 and replies to the ARP request.

9. VM 10 sends an ARP request to obtain the MAC address of VM 1.

10. VTEP 3 creates a suppression entry for VM 10 and replies to the ARP request.

(1)

VTEP 1 VTEP 2

Transport network

Server 1

VM 1

VM 2

VM 3

Server 3

VM 7

VM 8

VM 9

Server 2

VM 4

VM 5

VM 6

VXLAN tunnel

VTEP 3

VXLAN tunnel

Server 4

VM 10

VM 11

VM 12

(2)

(3)

(4)

(5)

(6)

(7)

(8)

(9) (10)

(2)

VXLAN IP gateways

A VXLAN IP gateway provides Layer 3 forwarding services for VMs in VXLANs. A VXLAN IP gateway

can be an independent device or be collocated with a VTEP. For more information about VXLAN IP

gateway placement, see "Configuring VXLAN IP gateways."

Protocols and standards

RFC 7348, Virtual eXtensible Local Area Network (VXLAN): A Framework for Overlaying Virtualized

Layer 2 Networks over Layer 3 Networks

Configuring basic VXLAN features

VXLAN configuration task list

Tasks at a glance

Remarks

(Required.) Setting the VXLAN hardware resource mode Set the VXLAN hardware

resource mode based on the

role of the device in the network.

(Required.) Creating a VXLAN on a VSI N/A

(Required.) Configuring a VXLAN tunnel N/A

(Required.) Assigning VXLAN tunnels to a VXLAN To extend a VXLAN to remote

sites, you must assign VXLAN

tunnels to the VXLAN.

(Required.) Assigning customer frames to a VSI Perform this task to assign

customer traffic to VXLANs.

(Optional.) Managing MAC address entries N/A

(Optional.) Configuring VXLAN over VXLAN

Perform this task for VXLAN

packets received from a

non-transport-facing interface to

traverse the VXLAN network

through VXLAN tunnels.

(Optional.) Configuring a multicast-mode VXLAN

By default, the VTEP floods

VXLAN traffic in unicast mode. If

the network is multicast dense,

configure the VTEP to flood

VXLAN traffic in multicast mode.

(Optional.) Confining floods to the local site N/A

(Optional.) Setting the destination UDP port number of VXLAN packets N/A

(Optional.) Configuring VXLAN packet check

Perform this task to check

incoming VXLAN packets,

including the following items:

• UDP checksum.

• 802.1Q VLAN tags in the

inner Ethernet header.

(Optional.) Enable default VXLAN decapsulation. N/A

(Optional.) Enabling ARP flood suppression N/A

(Optional.) Enabling ND flood suppression N/A

(Optional.) Disabling remote ARP or ND learning for VXLANs N/A

(Optional.) Enabling VXLAN packet statistics N/A

(Optional.) Testing the reachability of a remote VM N/A

Setting the VXLAN hardware resource mode

IMPORTANT:

This feature is not supported on the HPE FlexFabric 5930 switch series.

Overview

Set the hardware resource mode for VXLAN based on the role of the device.

•

l2gw—Applies to VTEPs that perform only Layer 2 forwarding.

•

l3gw8k, l3gw16k, l3gw24k, l3gw32k, or l3gw40k—Applies to VXLAN IP gateways.

•

border8k, border16k, border24k, border32k, or border40k—Applies to Layer 3 border

gateways that provide access to external networks.

Configuration restrictions and guidelines

For the hardware resource mode to take effect, you must reboot the device.

Configuration procedure

To set the VXLAN hardware resource mode:

Step

Command

Remarks

1. Enter system view. system-view N/A

2. Set the VXLAN hardware

resource mode.

hardware-resource vxlan { border8k

| border16k | border24k | border32k |

border40k | l2gw | l3gw8k | l3gw16k |

l3gw24k | l3gw32k | l3gw40k }

By default, the VXLAN

hardware resource mode is

l2gw.

Creating a VXLAN on a VSI

Configuration restrictions and guidelines

As a best practice, perform this task before you configure Ethernet service instances.

To avoid packet processing errors, make sure the configuration of a feature on a VSI is the same on

all VTEPs of the VXLAN associated with the VSI. For example, the status of IGMP snooping should

be consistent on all VTEPs of a VXLAN.

If you use both the restrain and bandwidth commands on a VSI, the bandwidth command limits

only the bandwidth of the traffic not restrained by the restrain command.

If you use both the restrain and flooding disable commands on a VSI, the following rules apply:

•

If the restraint bandwidth is set to 0, only the restrain command takes effect.

•

If the restraint bandwidth is not set to 0, both commands take effect.

If you use both the restrain and selective-flooding mac-address commands on a VSI, the restrain

command limits only the bandwidth of the traffic not enabled with selective flood.

As a best practice, do not execute both the bandwidth and selective-flooding mac-address

commands on a VSI. Traffic cannot be forwarded correctly if you use these commands together.

Configuration procedure

To create a VXLAN on a VSI:

Step

Command

Remarks

1. Enter system view. system-view N/A

2. Enable L2VPN. l2vpn enable By default, L2VPN is disabled.

3. Create a VSI and enter VSI

view. vsi vsi-name By default, no VSIs exist.

4. (Optional.) Configure a VSI

description. description text By default, a VSI does not have a

description.

5. Enable the VSI. undo shutdown By default, a VSI is not manually

shut down.

6. (Optional.) Set the

bandwidth limit for the VSI. bandwidth bandwidth By default, no bandwidth limit is set

for a VSI.

7. (Optional.) Set the

broadcast, multicast, or

unknown unicast restraint

bandwidth for the VSI.

restrain { broadcast | multicast

| unknown-unicast } bandwidth

By default, the device does not limit

the broadcast restraint bandwidth,

multicast restraint bandwidth, and

unknown unicast restraint

bandwidth.

8. (Optional.) Enable MAC

address learning for the VSI. mac-learning enable By default, MAC address learning

is enabled for a VSI.

9. Create a VXLAN and enter

VXLAN view. vxlan vxlan-id

By default, no VXLANs exist.

You can create only one VXLAN on

a VSI. The VXLAN ID must be

unique for each VSI.

Configuring a VXLAN tunnel

This task provides basic VXLAN tunnel configuration. For more information about tunnel

configuration and commands, see Layer 3—IP Services Configuration Guide and Layer 3—IP

Services Command Reference.

On the HPE FlexFabric 5940 switch series, use the local-first load sharing on an aggregate interface

in the following situations:

•

The aggregate interface is a Layer 3 aggregate interface and is the outgoing interface of a

VXLAN tunnel.

•

The aggregate interface is a Layer 2 aggregate interface and is in the VLAN of which the VLAN

interface is the outgoing interface of a VXLAN tunnel.

Make sure the following VXLAN tunnels are not associated with the same VXLAN when they have

the same tunnel destination IP address:

•

A VXLAN tunnel automatically created by EVPN.

•

A manually created VXLAN tunnel.

For more information about EVPN, see EVPN Configuration Guide.

If the VXLAN packets of two VXLAN tunnels are sent to different next hops in the transport network,

make sure the VXLAN tunnels use different physical outgoing interfaces. This restriction applies to

the HPE FlexFabric 5930 switch series.

To configure a VXLAN tunnel:

Step

Command

Remarks

1. Enter system view. system-view N/A

2. Create a VXLAN

tunnel interface and

enter tunnel interface

view.

interface tunnel

tunnel-number mode vxlan

By default, no tunnel interfaces exist.

The endpoints of a tunnel must use the same

tunnel mode.

3. Specify a source IP

address or source

interface for the tunnel.

source { ipv4-address |

interface-type

interface-number }

IMPORTANT:

Do not perform this step if you are using

OVSDB for VXLAN tunnel management.

By default, no source IP address or source

interface is specified for a tunnel.

This step specifies the source IP address in

the outer IP header of tunneled VXLAN

packets. If an interface is specified, its primary

IP address is used.

For a multicast-mode VXLAN, the source IP

address cannot be a loopback interface's

address, and the source interface cannot be a

loopback interface.

4. Specify a destination

IP address for the

tunnel. destination ipv4-address

By default, no destination IP address is

specified for a tunnel.

Specify the remote VTEP's IP address. This IP

address will be the destination IP address in

the outer IP header of tunneled VXLAN

packets.

As a best practice, do not configure multiple

VXLAN tunnels to use the same source and

destination IP addresses.

5. (Optional.) Enable

BFD on the tunnel. tunnel bfd enable

destination-mac

mac-address

By default, BFD is disabled on a tunnel.

For BFD sessions to come up, you must

reserve a VXLAN by using the reserved

vxlan command.

Do not use BFD together with uRPF. When

uRPF is enabled, BFD sessions cannot come

up. For more information about uRPF, see

Security Configuration Guide.

6. (Optional.) Return to

system view. quit N/A

7. (Optional.) Specify the

reserved VXLAN. reserved vxlan vxlan-id

By default, no VXLAN has been reserved.

You can specify only one reserved VXLAN on

the VTEP. The reserved VXLAN cannot be the

VXLAN created on any VSI.

Assigning VXLAN tunnels to a VXLAN

To provide Layer 2 connectivity for a VXLAN between two sites, you must assign the VXLAN tunnel

between the sites to the VXLAN.

You can assign multiple VXLAN tunnels to a VXLAN, and configure a VXLAN tunnel to trunk multiple

VXLANs. For a unicast-mode VXLAN, the system floods unknown unicast, multicast, and broadcast

traffic to each tunnel associated with the VXLAN. If a flood proxy server is used, the VTEP sends

flood traffic to the server through the flood proxy tunnel. The flood proxy server replicates and

forwards flood traffic to remote VTEPs.

To assign VXLAN tunnels to a VXLAN:

Step

Command

Remarks

1. Enter system view.

system-view

N/A

2. Enter VSI view.

vsi

vsi-name N/A

3. Enter VXLAN view. vxlan vxlan-id N/A

4. Assign VXLAN tunnels

to the VXLAN.

tunnel { tunnel-number

[ backup-tunnel

tunnel-number |

flooding-proxy ] | all }

By default, a VXLAN does not contain any

VXLAN tunnels.

For full Layer 2 connectivity in the VXLAN,

make sure the VXLAN contains the VXLAN

tunnel between each pair of sites in the

VXLAN.

To assign a pair of primary and backup

VXLAN tunnels to the VXLAN, specify the

backup-tunnel tunnel-number option. When

the primary VXLAN tunnel is operating

correctly, the backup VXLAN tunnel does not

forward traffic. When the primary VXLAN

tunnel goes down, traffic is switched to the

backup VXLAN tunnel.

Enable flood proxy on the tunnel for the VTEP

to send flood traffic to the flood proxy server.

The flood proxy server replicates and forwards

flood traffic to remote VTEPs.

Centralized VXLAN IP gateway groups cannot

work with the flood proxy feature. Do not use

them together in a VXLAN. For more

information about centralized VXLAN IP

gateway groups, see "Configuring a

centralized VXLAN IP gateway group."

Assigning customer frames to a VSI

Configuration restrictions and guidelines

VLAN-based VXLAN assignment is mutually exclusive with the manually created Ethernet service

instances and the Ethernet service instances automatically created for 802.1X or MAC

authentication VSI manipulation. To create these Ethernet service instances, you must first disable

VLAN-based VXLAN assignment by using the undo vxlan vlan-based command. To enable

VLAN-based VXLAN assignment, you must first delete all Ethernet service instances.

Mapping a static Ethernet service instance to a VSI

An Ethernet service instance matches a list of VLANs on a site-facing interface. The VTEP assigns

customer traffic from the VLANs to a VXLAN by mapping the Ethernet service instance to a VSI.

Configuration restrictions and guidelines

You can create static Ethernet service instances on both a Layer 2 aggregate interface and its

member ports and map the Ethernet service instances to VSIs. However, the Ethernet service

instances on the aggregation member ports are down. For the Ethernet service instances to come up,

you must remove the aggregation member ports from the aggregation group.

If an Ethernet service instance is configured with the encapsulation untagged criterion on a Layer 2

Ethernet or aggregate interface, you cannot apply a QoS policy for VLAN tag nesting to that interface.

For more information about VLAN tag nesting, see QoS configuration in ACL and QoS Configuration

Guide.

A Layer 2 aggregate interface reflects back incoming flood traffic that does not match any Ethernet

service instance on that interface. To solve this issue, you can assign the interface to an isolation

group. The interface will stop reflecting back any incoming packets. This issue does not exist on the

HPE FlexFabric 5930 switch series.

On an interface, Ethernet service instances associated with the same VSI can communicate at Layer

2. Flood traffic received by one Ethernet service instance will be forwarded to the other Ethernet

service instances of the same VSI on that interface. To isolate these Ethernet service instances at

Layer 2, assign that interface to an isolation group.

To avoid forwarding failure, execute the vxlan-over-vxlan enable command on a Layer 2 Ethernet

or aggregate interface if it hosts an Ethernet service instance that uses the encapsulation s-vid

vlan-id c-vid { vlan-id-list | all } criterion.

When you configure Ethernet service instances, follow these feature compatibility restrictions and

guidelines:

•

Ethernet service instances and QinQ cannot work together. Do not configure both features on

an interface. For more information about QinQ, see Layer 2 —LAN Switching Configuration

Guide.

•

Ethernet service instances and EVB cannot work together. Do not configure both features on an

interface. For more information about EVB, see EVB Configuration Guide.

•

Ethernet service instances for VXLAN cannot work together with Ethernet service instances for

MPLS L2VPN, VPLS, SPBM, or PBB. Do not configure both types of service instances on an

interface.

For more information about MPLS L2VPN and VPLS, see MPLS Configuration Guide. For more

information about SPBM, see SPB Configuration Guide. For more information about PBB, see

Layer 2 —LAN Switching Configuration Guide.

•

To forward the multicast traffic from a VLAN on the interface, make sure an Ethernet service

instance contains the VLAN ID. The interface cannot forward a multicast packet that does not

match any Ethernet service instance.

When you configure Ethernet service instances, follow these matching VLAN requirements:

•

You must create the matching VLANs of Ethernet service instances on the HPE FlexFabric

5930 switch series.

•

Make sure the matching VLANs of Ethernet service instances are not permitted on

EVB-enabled interfaces on the device.

When you configure Ethernet service instances, follow these access mode restrictions:

•

You must use Ethernet access mode if one of the following criteria is configured:

 encapsulation tagged

 encapsulation untagged

 encapsulation default

•

You can use Ethernet access mode or VLAN access mode if any other criterion is configured.

If you execute the encapsulation default command for an Ethernet service instance in Ethernet

access mode on a Layer 2 Ethernet interface or Layer 2 aggregate interface, the interface can host

multiple Ethernet service instances. Traffic that does not match any other Ethernet service instance

matches the Ethernet service instance that uses the default criterion.

Configuration procedure

To map a static Ethernet service instance to a VSI:

Page is loading ...

Aruba VXLAN Configuration Guide

Brand: Aruba

Model: VXLAN

Category: Networking

Type: Configuration Guide

Download PDF

report

Aruba VXLAN Configuration Guide

Aruba VXLAN Configuration Guide

Related papers

Other documents