H3C S7500E-XS Series User manual

H3C S7500E-XS Switch Series
VXLAN
Configuration Guide
Hangzhou H3C Technologies Co., Ltd.
http://www.h3c.com
Software version: S7500EXS-CMW710-R7178
Document version: 6W100-20160118

Copyright © 2016, Hangzhou H3C Technologies Co., Ltd. and its licensors
All rights reserved
No part of this manual may be reproduced or transmitted in any form or by any means without prior written
consent of Hangzhou H3C Technologies Co., Ltd.
Trademarks
H3C, , H3CS, H3CIE, H3CNE,Aolynk, , H3Care, , IRF, NetPilot, Netflow, SecEngine,
SecPath, SecCenter, SecBlade, Comware, ITCMM and HUASAN are trademarks of Hangzhou H3C
Technologies Co., Ltd.
All other trademarks that may be mentioned in this manual are the property of their respective owners
Notice
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute the warranty of any kind, express or implied.

Preface
This configuration guide describes VXLAN fundamentals and configuration. Virtual eXtensible LAN
(VXLAN) is a MAC-in-UDP technology that provides Layer 2 connectivity between distant network
sites across an IP network.
This preface includes the following topics about the documentation:
•Audience.
•Conventions.
•About the H3C S7500E-XS documentation set.
•Obtaining documentation.
•Technical support.
•Documentation feedback.
Audience
This documentation is intended for:
•Network planners.
•Field technical support and servicing engineers.
•Network administrators working with the S7500E-XS switch series.
Conventions
This section describes the conventions used in the documentation.
Port numbering in examples
The port numbers in the documentation are for illustration only and might be unavailable on your
device.
Command conventions
Convention Description
Boldface Bold text represents commands and keywords that you enter literally as shown.
Italic Italic text represents arguments that you replace with actual values.
[ ] Square brackets enclose syntax choices (keywords or arguments) that are optional.
{ x | y | ... }
Braces enclose a set of required syntax choices separated by vertical bars, from which
you select one.
[ x | y | ... ]
Square brackets enclose a set of optional syntax choices separated by vertical bars,
from which you select one or none.
{ x | y | ... } *
Asterisk marked braces enclose a set of required syntax choices separated by vertical
bars, from which you select at least one.
[ x | y | ... ] *
Asterisk marked square brackets enclose optional syntax choices separated by vertical
bars, from which you select one choice, multiple choices, or none.
&<1-n> The argument or keyword and argument combination before the ampersand (&) sign
can be entered 1 to n times.
# A line that starts with a pound (#) sign is comments.

GUI conventions
Convention Description
Boldface Window names, button names, field names, and menu items are in Boldface. For
example, the New User window appears; click OK.
> Multi-level menus are separated by angle brackets. For example, File > Create >
Folder.
Symbols
Convention Description
WARNING! An alert that calls attention to important information that if not understood or followed
can result in personal injury.
CAUTION: An alert that calls attention to important information that if not understood or followed
can result in data loss, data corruption, or damage to hardware or software.
IMPORTANT: An alert that calls attention to essential information.
NOTE: An alert that contains additional or supplementary information.
TIP: An alert that provides helpful information.
Network topology icons
Convention Description
Represents a generic network device, such as a router, switch, or firewall.
Represents a routing-capable device, such as a router or Layer 3 switch.
Represents a generic switch, such as a Layer 2 or Layer 3 switch, or a router that
supports Layer 2 forwarding and other Layer 2 features.
Represents an access controller, a unified wired-WLAN module, or the access
controller engine on a unified wired-WLAN switch.
Represents an access point.
Wireless terminator unit.
Wireless terminator.
Represents a mesh access point.
Represents omnidirectional signals.
Represents directional signals.
Represents a security product, such as a firewall, UTM, multiservice security
gateway, or load balancing device.
T
T
T
T





Convention Description
Represents a security card, such as a firewall, load balancing, NetStream, SSL VPN,
IPS, or ACG card.
About the H3C S7500E-XS documentation set
The H3C S7500E-XS documentation set includes the following categories of documents:
Category Documents Purposes
Product description and
specifications Marketing brochures Describes product specifications and benefits.
Hardware specifications
and installation
Compliance and safety
manual
Provides regulatory information and the safety
instructions that must be followed during
installation.
Quick start Guides you through initial installation and setup
procedures to help you quickly set up and use
your device with the minimum configuration.
Installation guide Provides a complete guide to hardware
installation and hardware specifications.
H3C Pluggable SFP
[SFP+][XFP] Transceiver
Modules Installation Guide
Guides you through installing SFP/SFP+/XFP
transceiver modules.
H3C CFP Transceiver
Modules Installation Guide Guides you through installing CFP transceiver modules.
H3C QSFP+ Transceiver
Modules Installation Guide Guides you through installing QSFP+ transceiver modules.
H3C Transceiver Modules
User Guide
Describes the transceiver modules available
for the H3C network products, their external
views, and specifications.
Software configuration
Configuration guides Describes software features and configuration
procedures.
Command references Provides a quick reference to all available
commands.
Configuration examples Describes typical network scenarios and provide configuration examples and
instructions.
Operations and
maintenance
Troubleshooting Provides troubleshooting information for
common problems of using the product.
FAQ Covers the most frequently asked questions about the hardware, software and system
specifications.
Release notes
Provides information about the product
release, including the version history, hardware
and software compatibility matrix, version
upgrade information, technical support
information, and software upgrading.
System log messages Explains the system log messages.

Obtaining documentation
Access the most up-to-date H3C product documentation on the World Wide Web
at http://www.h3c.com.
Click the following links to obtain different categories of product documentation:
[Technical Documents]—Provides hardware installation, software upgrading, and software feature
configuration and maintenance documentation.
[Products & Solutions]—Provides information about products and technologies, as well as
solutions. [Software Download]—Provides the documentation released with the software version.
Technical support
[e-mail]
http://www.h3c.com
Documentation feedback
You can e-mail your comments about product documentation to [e-mail].
We appreciate your comments.

i
Contents
VXLAN overview·····························································································1
VXLAN network model·······································································································································1
VXLAN packet format ········································································································································2
Working mechanisms·········································································································································3
VXLAN tunnel establishment and assignment···························································································3
Assignment of traffic to VXLANs················································································································3
MAC learning ·············································································································································3
Traffic forwarding ·······································································································································4
Access modes of VSIs·······························································································································6
ARP flood suppression ······································································································································7
Protocols and standards ····································································································································8
Configuring VXLANs·······················································································9
Feature compatibility requirements····················································································································9
VXLAN configuration task list·····························································································································9
Creating a VXLAN on a VSI·····························································································································10
Configuring a VXLAN tunnel····························································································································10
Assigning VXLAN tunnels to a VXLAN ············································································································11
Mapping an Ethernet service instance to a VSI·······························································································12
Managing MAC address entries·······················································································································13
Enabling local-MAC change logging········································································································13
Configuring static remote-MAC address entries ······················································································14
Enabling remote-MAC address learning··································································································14
Configuring a multicast-mode VXLAN ·············································································································14
Confining unknown-unicast floods to the local site ··························································································15
Configuring the destination UDP port number of VXLAN packets···································································16
Configuring VXLAN packet check····················································································································16
Enabling ARP flood suppression ·····················································································································16
Displaying and maintaining VXLANs ···············································································································17
VXLAN configuration examples ·······················································································································18
Unicast-mode VXLAN configuration example··························································································18
Multicast-mode VXLAN configuration example························································································22
Index·············································································································30

1
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, 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 H3C VTEP uses VSIs and VXLAN tunnels to provide VXLAN services.
•VSI—A virtual switching 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.

2
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

3
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.
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."
VXLAN tunnel establishment and assignment
To provide Layer 2 connectivity for a VXLAN between two sites, you must create a VXLAN tunnel
between the sites and assign the tunnel to the VXLAN.
Assignment of traffic to VXLANs
Traffic from the local site to a remote site
The VTEP uses an Ethernet service instance to match a list of VLANs on a site-facing interface. The
VTEP assigns customer traffic to a VXLAN by mapping the Ethernet service instance to a VSI. 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 VTEPassigns 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.
•For traffic from the remote site to the local site, the VTEP learns the source MAC address after
removing the VXLAN header.

4
A VSI's MAC address table includes the following types of MAC address entries:
•Local MAC—Dynamic MAC entries learned from the local site. The outgoing interfaces are
site-facing interfaces on which the MAC addresses are learned. VXLAN does not support
manual local-MAC entries.
•Remote MAC—MAC entries learned from a remote site, including static, dynamic, and
OpenFlow MAC entries. The outgoing interfaces for the MAC addresses 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.
For a remote address, the manual static entry has higher priority than the dynamic entry.
Traffic forwarding
The VTEP uses the following processes to forward traffic:
•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.

5
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 VTEPreplicates 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
replicate and forward the packet to remote VTEPs based on their multicast forwarding entries.
See Figure 6.
Each destination VTEPfloods 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.

6
Figure 5 Unicast mode
Figure 6 Multicast mode
Access modes of VSIs
The access mode of a VSI determines how the VTEP processes the 802.1Q VLAN tags in the
Ethernet frames.

7
•VLAN access 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 VLAN access 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.
•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.
ARP flood suppression
ARP flood suppression reduces ARP request broadcasts by enabling the VTEP to reply to ARP
requests on behalf of VMs.
As shown in Figure 7, this feature snoops ARP packets to populate the ARPflood suppression table
with local and remote MAC addresses. If anARP 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 7 ARP flood suppression
ARP flood suppression uses the following 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.

8
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.
Protocols and standards
IETF draft, draft-mahalingam-dutt-dcops-vxlan-04

9
Configuring VXLANs
Feature compatibility requirements
When you use VXLAN in conjunction with other features, follow these restrictions and guidelines:
•If multiple VXLAN tunnels share a transport-facing interface, make sure the VXLAN tunnels use
the same VLAN interface for forwarding.
•EVB and VXLAN cannot work together. Do not configure both features on an interface. For
more information about EVB, see EVB Configuration Guide.
•Do not configure EVI or MPLS settings on VXLANs. For more information about EVI and MPLS,
see EVI Configuration Guide and MPLS Configuration Guide.
•A site-facing interface does not support Layer 3 multicast if Ethernet service instances are
configured on the interface.
•You must disable the spanning tree protocol (undo stp enable) on a site-facing interface if
Ethernet service instances are configured on it.
•For a multicast-mode VXLAN to forward traffic correctly, do not configure VXLANs or VXLAN
tunnels on transport network devices.
VXLAN configuration task list
Tasks at a glance Remarks
(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.) Mapping an Ethernet service instance to a VSI Perform this task to assign
customer traffic to VXLANs.
(Optional.) Managing MAC address entries N/A
(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 unknown-unicast floods to the local site N/A
(Optional.) Configuring the destination UDP port number of VXLAN
packets N/A
(Optional.) Configuring VXLAN packet check
Perform this task to check the
802.1Q VLAN tags in the inner
Ethernet header of incoming
VXLAN packets.
(Optional.) Enabling ARP flood suppression N/A

10
Creating 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 are created.
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 enabled.
6. (Optional.) Set the
MTU for the VSI. mtu mtu The default MTU is 1500 bytes for a VSI.
7. (Optional.) Enable
MAC address learning
for the VSI. mac-learning enable
By default, MAC address learning is
enabled for a VSI.
The device does not support disabling
MAC address learning for a VXLAN VSI.
The undo mac-learning enable
command does not take effect on
VXLAN VSIs.
8. Create a VXLAN and
enter VXLAN view. vxlan vxlan-id
By default, no VXLANs are created.
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.
To configure a VXLAN tunnel:
Step Command Remarks
1. Enter system view. system-view N/A
2. Specify a global
source address for
VXLAN tunnels.
tunnel global
source-address
ip-address
By default, no global source address is specified
for VXLAN tunnels.
A VXLAN tunnel uses the global source address if
you do not specify a source interface or source
address for the tunnel.
3. (Optional.) Specify
the reserved
VXLAN. reserved vxlan vxlan-id By default, no VXLAN has been reserved.
If BFD is enabled on VXLAN tunnels, you must
reserve a VXLAN for BFD sessions to come up.
4. 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.

11
Step Command Remarks
5. Specify a source IP
address or source
interface for the
tunnel.
source { ipv4-address |
interface-type
interface-number }
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 address, and the
source interface cannot be a loopback interface.
6. 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.
7. (Optional.) Enable
BFD on the tunnel. tunnel bfd enable
destination-mac
mac-address
By default, BFD is disabled on a tunnel.
Enable BFD on both ends of a VXLAN tunnel for
quick link connectivity detection. The VTEPs
periodically send BFD single-hop control packets
to each other through the VXLAN tunnel. A VTEP
sets the tunnel state to Defect if it has not received
control packets from the remote end for 5
seconds. In this situation, the tunnel interface state
is still Up. The tunnel state will change from Defect
to Up if the VTEP can receive BFD control packets
again.
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.
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 | 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.

12
Mapping an 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.
An Ethernet service instance can contain only one match criterion. To change the match criterion,
you must remove the original criterion first. When you remove the match criterion in an Ethernet
service instance, the mapping between the service instance and the VSI is removed automatically.
If an Ethernet service instance contains the encapsulation default match criterion, traffic is
matched as follows:
•The service instance matches any frames if it is the only instance on the interface.
•The service instance matches frames that do not match any other service instance if multiple
instances exist on the interface.
To map an Ethernet service instance to a VSI:
Step Command Remarks
1. Enter system view. system-view N/A
2. Enter Layer 2 Ethernet
interface view or Layer 2
aggregate interface view.
•interface interface-type
interface-number
•interface bridge-aggregation
interface-number
N/A
3. Configure the port link
type. port link-type { access | trunk |
hybrid } The default port link type is
access.
4. Assign the interface to
C-VLANs.
•Access link type:
port access vlan vlan-id
•Trunk link type:
port trunk permit vlan
{ vlan-id-list | all }
•Hybrid link type:
port hybrid vlan vlan-id-list
{ tagged | untagged }
Make sure you have created the
C-VLANs.
5. Create an Ethernet
service instance and
enter Ethernet service
instance view. service-instance instance-id By default, no Ethernet service
instances exist.

13
Step Command Remarks
6. Configure a frame match
criterion.
•Match frames that do not match
any other service instance on the
interface:
encapsulation default
•Match any 802.1Q tagged or
untagged frames:
encapsulation { tagged |
untagged }
•Match frames tagged with the
specified outer 802.1Q VLAN ID:
encapsulation s-vid vlan-id
[ only-tagged ]
•Match frames tagged with the
specified outer and inner 802.1Q
VLAN IDs:
encapsulation s-vid vlan-id
c-vid vlan-id
By default, an Ethernet service
instance does not contain a
frame match criterion.
To match frames from a VLAN
correctly, make sure you have
created the VLAN and assigned
the interface to the VLAN.
To match untagged frames
when the VLAN access mode is
used, you must use the
encapsulation untagged
command.
7. Map the Ethernet service
instance to a VSI. xconnect vsi vsi-name
[access-mode { ethernet | vlan } ]
By default, an Ethernet service
instance is not mapped to any
VSI.
If you set the match criterion to
default or tagged, you must
specify the Ethernet access
mode.
If you do not specify an access
mode, the default VLAN access
mode is used.
Managing MAC address entries
With VXLAN, local MAC addresses are learned dynamically. You can log MAC changes, but you
cannot manually add local MAC addresses.
Remote-MAC address entries include the following types:
•Manually created static entries.
•Dynamic entries learned in the data plane.
•MAC entries issued by a remote controller through OpenFlow.
Enabling local-MAC change logging
Local-MAC change logging enables the VXLAN module to send a log message to the information
center when a local MAC address is added or removed.
With the information center, you can set log message filtering and output rules, including output
destinations. For more information about configuring the information center, see Network
Management and Monitoring Configuration Guide.
To enable local-MAC change logging:
Step Command Remarks
1. Enter system view. system-view N/A
2. Enable local-MAC
change logging. vxlan local-mac report By default, local-MAC change
logging is disabled.