H3C S10500 Series User manual

H3C S10500 Switch Series
EVB
Configuration Guide
Hangzhou H3C Technologies Co., Ltd.
http://www.h3c.com
Software version: S10500-CMW710-R7523P01
Document version: 6W100-20160830

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 EVB fundamentals and configuration. It describes how to enable
EVB, configure negotiation parameters, and establish S-channels between the EVB station and the
EVB bridge.
This preface includes the following topics about the documentation:
•Audience.
•Conventions.
•About the H3C S10500 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 S10500 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.

Convention Description
{ 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.
T
T

Convention Description
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.
Represents a security card, such as a firewall, load balancing, NetStream, SSL VPN,
IPS, or ACG card.
About the H3C S10500 documentation set
The H3C S10500 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.
T
T

Category Documents Purposes
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
Configuring EVB ·····························································································1
Overview····························································································································································1
Basic concepts···········································································································································2
EVB working mechanism···························································································································2
Protocols and standards ····························································································································3
Feature and hardware compatibility···················································································································3
Licensing requirements······································································································································3
Configuration restrictions and guidelines···········································································································3
EVB and feature compatibility····················································································································3
EVB and feature configuration restrictions·································································································4
EVB configuration task list ·································································································································4
Enabling EVB·····················································································································································5
Configuring LLDP···············································································································································5
Specifying a default VSI manager······················································································································6
Configuring VDP negotiation parameters ··········································································································6
Configuring an S-channel ··································································································································7
Creating an S-channel ·······························································································································7
Configuring an S-channel interface or S-channel aggregate interface ······················································8
Enabling the RR mode for an S-channel····································································································8
Disabling MAC address learning for an S-channel ····················································································8
Configuring a VSI interface or VSI aggregate interface·····················································································9
Creating a VSI interface or VSI aggregate interface··················································································9
Configuring a VSI filter·····························································································································10
Activating a VSI interface or VSI aggregate interface··············································································11
Displaying and maintaining EVB······················································································································12
EVB configuration example······························································································································12
Network requirements······························································································································12
Configuration procedure···························································································································13
Verifying the configuration························································································································16
Index·············································································································17

1
Configuring EVB
Overview
Edge VirtualBridging (EVB) allows virtual machines (VMs) on a physical server to obtain bridge relay
services through a common bridge port. It enables coordinated configuration and management of
bridge services for VMs.
Data center virtualization includes network virtualization, storage virtualization, and server
virtualization. Server virtualization uses specific virtualization software such as VMware to create
VMs on a single physical server. Each VM operates independently and has its own operating system,
applications, and virtual hardware environments, as shown in Figure 1.
Figure 1 Server virtualization
VMs on a physical server communicate with each other or with the outside network through a Virtual
Ethernet Bridge (VEB). VEBs are implemented through software or hardware such as NICs. Both
implementation methods have the following limitations:
•Lack of traffic monitoring capabilities such as packets statistics, traffic mirroring, and
NetStream.
•Lack of network policy enforcement capabilities, such as QoS.
•Lack of management scalability, especially in unified deployment of the internal server network
and the external network.
EVB solves these limitations. It uses a physical switch (called EVB bridge) to switch traffic for VMs on
a directly connected physical server (called EVB station). EVB implements traffic policing, network
policy enforcement, and unified network deployment and management for VMs.

2
Basic concepts
Figure 2 shows the components on the EVB station and EVB bridge.
Figure 2 EVB architecture
•Edge Relay—An ER transfers packets between one URP and one or more DRPs. An ER has
one or more DRPs and one URP. Both URP and DRPs are called ER ports. An EVB station can
have multiple ERs.
•S-channel—Apoint-to-point S-VLAN established between a Port-mapping S-VLAN component
in an EVB station and a Port-mapping S-VLAN component in an EVB bridge. An S-channel
corresponds to the URP of an ER. On an EVB bridge, the end point of an S-channel is known as
an S-channel interface.An S-channel is identified by the S-VLAN Identifier (SVID) and the
S-channel Identifier (SCID), and the two values together are called an (SCID, SVID) pair.
•Virtual Station Interface—A VSI is a port on a VM that directly connects to the DRP of an ER.
A VSI is associated with a logical entity called VSI instance, which is identified by the VSI
Instance Identifier (VSIID). AVSI is associated with a virtual interface called VSI interface on
the EVB bridge port to implement VM traffic management and policy configuration. A VSI
interface can be considered a subinterface of an S-channel.
•Reflective Relay—RR is an operation mode in which a received frame on a port that supports
this function can be forwarded out of the same port. The EVB bridge uses this mode to forward
traffic among VMs on an EVB station, as shown in Figure 2.
EVB working mechanism
The following basic concepts describe EVB station and EVB bridge communication:
•S-channel Discovery and Configuration Protocol—CDCP is used to configure S-channels
between stations and bridges. When a station creates or deletes an S-channel, CDCP sends a
CDCP TLV in an LLDP packet that is addressed using the nearest non-TPMR bridge address to
the bridge. The bridge creates or deletes the S-channel.
•VSI Discovery and Configuration Protocol—VDP manages the association between a VSI
and a station-facing bridge port (SBP) on a bridge. VDP uses the Edge Control Protocol (ECP)
to carry VDP TLVs. A VDP TLV contains the VSIID, VSI type, and VSI version. The bridge uses
the VSI interfaces to manage traffic for VMs.
•VSI manager—A VSI manager stores network policies such as VSI traffic management and
deploys the policies when a VM accesses the network.
{When a station creates a VM, it sends a VDP pre-associate, pre-associate with resource
reservation, or associate packet to the bridge. The bridge sends the request to a VSI
manager, and the VSI manager notifies the bridge to create a VSI interface and apply
policies.

3
{When a station shuts down a VM, it sends a VDP de-associate packet to the bridge. The
bridge sends the request to the VSI manager, and the VSI manager notifies the bridge to
delete the VSI interface.
An EVB station and an EVB bridge perform the following steps to manage VM traffic:
1. Use CDCP to establish an S-channel.
2. Exchange EVB TLVs through LLDP to negotiate EVB capabilities such as RR, ECP parameters,
and VDP parameters for the S-channel.
3. Use VDP to associate the VSIs of VMs with the bridge port.
Protocols and standards
IEEE P802.1Qbg/D2.2, Draft Standard for Local and Metropolitan Area Networks—MAC Bridges
and Virtual Bridged Local Area Networks - Amendment XX: Edge Virtual Bridging
Feature and hardware compatibility
EVB is applicable only to interfaces on the following modules:
•EC interface modules.
•SE interface modules:
{LSU1CGC2SE0.
{LSUM2GP24TSSE0.
{LSUM2GP44TSSE0.
{LSUM2GT24PTSSE0.
{LSUM2GT24TSSE0.
{LSUM2GT48SE0.
{LSUM2GV48SE0.
•SF interface modules.
•SG interface modules.
Traffic received from an EVB-enabled interface can be forwarded only through interface modules
that support EVB.
Licensing requirements
EVB requires a license to run on the device. For information about obtaining a license, see
Fundamentals Configuration Guide.
Configuration restrictions and guidelines
EVB and feature compatibility
Table 1 shows features incompatible with EVB and the references for these features.
Table 1 Features incompatible with EVB
Feature Reference
EVI EVI Configuration Guide

4
Feature Reference
VXLAN VXLAN Configuration Guide
MPLS L2VPN MPLS Configuration Guide
VLAN mapping
Layer 2—LAN Switching Configuration Guide
QinQ
MAC VLAN
Voice VLAN
MAC authentication Security Configuration Guide
Port security
EVB and feature configuration restrictions
When you configure an EVB-enabled interface, follow these restrictions and guidelines:
•Do not create an Ethernet service instance for the interface, and vice versa.
•Do not set the interface to operate in route mode. For more information about Ethernet interface
link modes, see Interface Configuration Guide.
•If the interface is a Layer 2 Ethernet interface or Layer 2 aggregate interface in a VLAN, it does
not support Layer 3 services or Layer 2 multicast services.
•Interfaces in multiport unicast MAC address entries cannot forward traffic received from the
interface. For more information about multiport unicast MAC address entries, see Layer
2—LAN Switching Configuration Guide.
•Do not configure the interface as the source or destination port for a mirroring group. For more
information about mirroring groups, see Network Management and Monitoring Configuration
Guide.
EVB configuration task list
This document only describes EVB bridge configuration. For information about EVB station
configuration, see the station manual.
Tasks at a glance
Enabling EVB
Configuring LLDP
(Optional.) Specifying a default VSI manager
(Optional.) Configuring VDP negotiation parameters
(Optional.) Configuring an S-channel:
•Creating an S-channel
•Configuring an S-channel interface or S-channel aggregate interface
•Enabling the RR mode for an S-channel
•Disabling MAC address learning for an S-channel

5
Tasks at a glance
(Optional.) Configuring a VSI interface or VSI aggregate interface:
•Creating a VSI interface or VSI aggregate interface
•Configuring a VSI filter
•Activating a VSI interface or VSI aggregate interface
Enabling EVB
Perform this task to enable EVB on an interface that directly connects to a station. For VSI filter
configuration (see "Configuring a VSI filter") to take effect, you must configure the interface to
operate in trunk mode.
Adefault S-channel is created on an interface after you enable EVB on the interface. Both the SCID
and SVID are 1. After an S-channel is created, an S-channel interface or S-channel aggregate
interface is automatically created and operates in access mode.
Configuration restrictions and guidelines
When you enable EVB, follow these restrictions and guidelines:
•Do not enable both EVB and TRILL on the same interface. For more information about TRILL,
see TRILL Configuration Guide.
•Do not assign ports that are enabled with EVB but not configured with the trill evb-support
command to the same VLAN as ports that are enabled with TRILL. For more information about
the trill evb-support command, see TRILL Command Reference.
Configuration procedure
To enable EVB:
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 N/A
3. Enable EVB. evb enable By default, EVB is disabled on an
interface.
Configuring LLDP
You must configure LLDP because EVB uses LLDP to transmit CDCP TLVs and CDCP TLVs are
carried by the LLDP packet that is addressed using the nearest non-TPMR bridge address.
For more information about the lldp global enable, lldp enable and lldp agent nearest-nontpmr
admin-status txrx commands, see Layer 2—LAN Switching Command Reference.
To configure LLDP:
Step Command Remarks
1. Enter system view. system-view N/A
2. Enable LLDP globally. lldp global enable By default, LLDP is disabled
globally.
3. Enter Layer 2 Ethernet interface interface-type N/A

6
Step Command Remarks
interface view or Layer 2
aggregate interface view. interface-number
4. Enable LLDP on the
interface lldp enable By default, LLDP is enabled on an
interface.
5. Configure the Nearest
non-TPMR Bridge agent for
LLDP to operate in TxRx
mode.
lldp agent nearest-nontpmr
admin-status txrx The default mode is disable.
Specifying a default VSI manager
When the bridge receives a VDP packet (except for de-associate packets) from a station, it obtains
VSI interface resources and policies for the station from the VSI manager specified in the VDP
packet.
The VSI manager ID TLV in a VDP packet carries an IPaddress of a VSI manager. If the value for the
TLV is 0, the VDP packet does not contain a VSI manager IP address. Perform this task to specify a
default VSI manager for the bridge.
To specify a default VSI manager:
Step Command Remarks
1. Enter system view. system-view N/A
2. Specify a default VSI
manager.
evb default-manager { { ip
ipv4-address | ipv6 ipv6-address |
name name } [ port port-number ]
| local-server }
By default, no default VSI
manager is specified.
Configuring VDP negotiation parameters
After a station sends a VDP request other than a De-Associate request to the bridge, the bridge
requests the VSI interface resources and policies from the VSI manager. If the bridge does not
receive a response from the VSI manager before the VDP response-wait-delay time expires, the
VDP negotiation fails. The VDP response-wait-delay time on the EVB bridge is calculated by using
the following formula:
VDP response-wait-delay time (seconds) = 2VDP resource-wait-delay × 10—5.
The value of the VDP resource wait-delay exponent is the larger of the values proposed by the
station and bridge through EVB TLV.
When a Pre-Associate, Pre-Associate with Resource Reservation, or Associate request from a
station is successfully handled, the VSI manager notifies the bridge to create a VSI interface for the
corresponding VM. Then the bridge starts a VDP keepalive timer for the VSI interface. If the bridge
does not receive a keepalive from the station before the timer expires, it releases resources reserved
for the association. The VDP keepalive time is calculated by using the following formula:
VDP keepalive time (seconds) = 1.5 × [ 2VDP keepalive + (2 × ECP maximum retransmission time + 1) ×
2ECP retransmission ] × 10—5.
The values assigned to the VDP keepalive exponent, the ECP maximum retransmission time, and
the ECP retransmission exponent are the larger of the values proposed for each by the station and
bridge through EVB TLV.
To configure VDP negotiation parameters:

7
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 N/A
3. Set the VDP
resource-wait-delay timer
exponent.
evb vdp timer
resource-wait-delay exponent
value The default is 20.
4. Set the VDP keepalive timer
exponent. evb vdp timer keepalive
exponent value The default is 20.
Configuring an S-channel
Creating an S-channel
An S-channel is automatically created by CDCP, and the system automatically saves the
configuration in the configuration file on the bridge. You can perform this task to manually create an
S-channel. If you create an S-channel that has the same number as an automatically created
S-channel, the (SCID, SVID) pair configuration for the automatically created S-channel takes
precedence over the (SCID, SVID) pair configuration for the manually created S-channel.
Creating an S-channel also creates an S-channel interface or S-channel aggregate interface.
Removing an S-channel also removes the S-channel interface or S-channel aggregate interface.
The S-channel interface or S-channel aggregate interface associated with a manually created
S-channel operates in access mode. The S-channel interface or S-channel aggregate interface
associated with an automatically created S-channel operates in trunk mode.
An S-channel interface is associated with the S-channel that is created on a Layer 2 Ethernet
interface. An S-channel aggregate interface is associated with the S-channel that is created on a
Layer 2 aggregate interface.
When you create an S-channel, follow these restrictions and guidelines:
•Create an S-channel on an interface with EVB enabled.
•Do not use the SCID or SVID being used by any other S-channels.
•To manually create or remove an S-channel, disable CDCP.
To create an S-channel:
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 N/A
3. Create an S-channel. evb s-channel channel-id
[ service-vlan svlan-id ]
By default, only an automatically
created default S-channel (with
both SCID and SVID as 1) exists
on an interface with EVB enabled.

8
Configuring an S-channel interface or S-channel aggregate
interface
Step Command Remarks
1. Enter system view. system-view N/A
2. Enter S-channel interface
view or S-channel aggregate
interface view.
interface { s-channel |
schannel-aggregation }
interface-number:channel-id N/A
3. (Optional.) Set the expected
bandwidth of the interface. bandwidth bandwidth-value
By default, the expected
bandwidth of an interface is the
default maximum bandwidth of
the physical port to which the
interface belongs.
4. (Optional.) Restore the
default settings for the
interface. default N/A
5. (Optional.) Set a description
for the interface. description text The default description
information is "interface name
Interface."
6. Bring up the interface. undo shutdown By default, the interface is up.
Enabling the RR mode for an S-channel
EVB TLVs exchanged through LLDP allow an EVB station and EVB bridge to negotiate the RR mode.
If the EVB bridge supports the RR mode, when the EVB station requests the use of the RR mode, the
bridge performs the following operations:
•Automatically enables the RR mode for the S-channel.
•Saves the configuration in the configuration file on the bridge.
You can perform this task to manually enable the RR mode for an S-channel.
To enable the RR mode for an S-channel:
Step Command Remarks
1. Enter system view. system-view N/A
2. Enter S-channel interface
view or S-channel
aggregate interface view.
interface { s-channel |
schannel-aggregation }
interface-number:channel-id N/A
3. Enable the RR mode for the
S-channel. evb reflective-relay By default, the RR mode is
disabled for an S-channel.
Disabling MAC address learning for an S-channel
Perform this task to manually disable the MAC address learning feature for an S-channel.
Follow these restrictions and guidelines when you disable MAC address learning for an S-channel:
•For the bridge to successfully forward traffic for VMs on the EVB station, do not disable MAC
address learning on an S-channel with the RR mode disabled.

9
•After you disable the MAC address learning function for an S-channel, the bridge will discard
packets with an unknown source MAC address.
•The undo evb mac-learning forbidden command and the mac-address mac-learning
enable command must be configured together to avoid communication interruption. For more
information about the mac-address mac-learning enable command, see Layer 2—LAN
Switching Command References.
To disable MAC address learning for an S-channel:
Step Command Remarks
1. Enter system view. system-view N/A
2. Enter interface view.
•Enter S-channel interface
view:
interface s-channel
interface-number:channel-id
•Enter S-channel aggregate
interface view:
interface
schannel-aggregation
interface-number:channel-id
N/A
3. Disable MAC address
learning for the S-channel. evb mac-learning forbidden By default, the MAC address
learning function is enabled for
an S-channel.
Configuring a VSI interface or VSI aggregate
interface
Creating a VSI interface or VSI aggregate interface
IMPORTANT:
When the total number of VSI interfaces and VSI aggregate interfaces on the device exceeds 512,
make sure the VDP keepalive exponent is larger than the default value. If the exponent is not large
r
than the default value, some VSI interfaces or VSI aggregate interfaces might be automatically
deleted.
VSI interfaces or VSI aggregate interfaces are typically created by a VSI manager. You can perform
this task to create a VSI interface on an S-channel interface or create a VSI aggregate interface on
an S-channel aggregate interface. In addition, you can perform this task to modify the Pre-Associate
and Associate properties of a VSI interface or VSI aggregate interface.
Removing an S-channel also removes all its VSI interfaces and VSI aggregate interfaces.
To create a VSI interface or VSI aggregate interface:
Step Command Remarks
1. Enter system view. system-view N/A
2. Enter S-channel interface
view or S-channel
aggregate interface view.
interface { s-channel |
schannel-aggregation }
interface-number:channel-id N/A
3. Create a VSI interface or
VSI aggregate interface. evb vsi vsi-local-id { association |
pre-association } By default, no VSI interface or
VSI aggregate interfaces exist on

10
Step Command Remarks
an S-channel.
Configuring a VSI filter
The EVB bridge uses a VSI filter to identify VSI traffic for a VM. Typically a VSI manager assigns
filters to VMs. Perform this task to manually create or remove a VSI filter.
A VSI filter contains a set of VID values, MAC addresses, and group ID values. EVB supports the
following filter info formats:
•VLAN ID.
•VLAN ID + MAC.
•Group ID + VLAN ID.
•Group ID + VLAN ID + MAC.
When you configure a VSI filter on a VSI interface, follow these restrictions and guidelines:
•For the VSI filter configuration to take effect, make sure the S-channel interface to which the
VSI interface belongs operates in trunk mode.
•When you create a VSI filter, the following interfaces automatically permit the VLAN contained
in the VSI filter:
{The S-channel interface to which the VSI interface belongs.
{The Layer 2 Ethernet interface where the S-channel that is associated with the S-channel
interface is created.
•When you delete a VSI filter, the following interfaces automatically deny the VLAN in the filter if
the VSI filters on the other VSI interfaces created on the same S-channel interface do not
contain the VLAN:
{The S-channel interface to which the VSI interface belongs.
{The Layer 2 Ethernet interface where the S-channel that is associated with the S-channel
interface is created.
•Do not create a VSI filter that contains the same VLAN on the same VSI interface or on other
VSI interfaces that belong to the same S-channel interface. If you do so, the system displays an
error message.
•Disabling MAC address learning for an S-channel prevents the traffic from the VSI from being
forwarded if the VSI filter contains the VLAN to which the traffic belongs.
•Activate a VSI interface after configuring a VSI filter, and deactivate a VSI interface before
removing a VSI filter.
When you configure a VSI filter on a VSI aggregate interface, follow these restrictions and
guidelines:
•For the VSI filter configuration to take effect, make sure the S-channel aggregate interface to
which the VSI aggregate interface belongs operates in trunk mode.
•When you create a VSI filter, the following interfaces automatically permit the VLAN contained
in the VSI filter:
{The S-channel aggregate interface to which the VSI aggregate interface belongs.
{The Layer 2 aggregate interface where the S-channel that is associated with the S-channel
aggregate interface is created.
•When you delete a VSI filter, the following interfaces automatically deny the VLAN in the filter if
the VSI filters on the other VSI aggregate interfaces created on the same S-channel aggregate
interface do not contain the VLAN:
{The S-channel aggregate interface to which the VSI aggregate interface belongs.

11
{The Layer 2 aggregate interface where the S-channel that is associated with the S-channel
aggregate interface is created.
•Do not create a VSI filter that contains the same VLAN on the same VSI aggregate interface or
on other VSI aggregate interfaces that belong to thesame S-channel aggregate interface. If you
do so, the system displays an error message.
•Activate a VSI aggregate interface after configuring a VSI filter, and deactivate a VSI aggregate
interface before removing a VSI filter.
To configure a VSI filter:
Step Command Remarks
1. Enter system view. system-view N/A
2. Enter VSI interface view or
VSI aggregate interface
view.
interface { s-channel |
schannel-aggregation }
interface-number:channel-id.vsi-l
ocal-id
N/A
3. Configure a VSI filter. evb vsi filter [ group group-id ]
vlan vlan-id [ mac mac-address ]By default, no VSI filters exist.
Activating a VSI interface or VSI aggregate interface
Traffic policy configuration on a VSI interface or VSI aggregate interface takes effect only when the
VSI interface or VSI aggregate interface is activated. When a VSI interface or VSI aggregate
interface is not activated, do not configure any settings other than filters on either interface. For more
information about traffic policing, see ACL and QoS Configuration Guide.
Activate a VSI interface or VSI aggregate interfaceafter configuring a VSI filter, and deactivate a VSI
interface or VSI aggregate interface before removing a VSI filter.
To activate a VSI interface or VSI aggregate interface:
Step Command Remarks
1. Enter system view. system-view N/A
2. Enter VSI interface view or
VSI aggregate interface
view.
interface { s-channel |
schannel-aggregation }
interface-number:channel-id.vsi-l
ocal-id
N/A
3. (Optional.) Set the expected
bandwidth of the VSI
interface or VSI aggregate
interface. bandwidth bandwidth-value
By default, the expected
bandwidth of a VSI interface or
VSI aggregate interface is the
default maximum bandwidth of
the physical port to which the
interface belongs.
4. (Optional.) Restore the
default settings for the VSI
interface or VSI aggregate
interface. default N/A
5. (Optional.) Set a description
for the VSI interface or VSI
aggregate interface. description text The default description
information is "interface name
Interface."
6. Activate the VSI interface or
VSI aggregate interface. evb vsi active By default, no VSI interface or VSI
aggregate interface is activated.

12
Displaying and maintaining EVB
Execute display commands in any view and the reset command in user view.
Task Command
Display CDCP negotiation
information. display evb cdcp [ interface interface-type interface-number ]
Display S-channel EVB TLV
negotiation information. display evb evb-tlv [ interface interface-type { interface-number |
interface-number:channel-id } ]
Display S-channel information. display evb s-channel [ interface interface-type interface-number ]
Display EVB summary. display evb summary
Display VSI interface information. display evb vsi [ verbose ] [ interface interface-type
{ interface-number | interface-number:channel-id |
interface-number:channel-id.vsi-local-id } ]
Display information about an
S-channel interface, an S-channel
aggregate interface, a VSI interface,
or a VSI aggregate interface.
display interface [ { s-channel | schannel-aggregation }
[ interface-number:channel-id |
interface-number:channel-id.vsi-local-id ] ] [ brief [ description |
down ] ]
Clear statistics for an S-channel
interface, an S-channel aggregate
interface, a VSI interface, or a VSI
aggregate interface.
reset counters interface [ { s-channel | schannel-aggregation }
[ interface-number:channel-id |
interface-number:channel-id.vsi-local-id ] ]
EVB configuration example
Network requirements
As shown in Figure 3, the Layer 2 network of a data center contains two switches that form an IRF
fabric, four EVB bridges, and four EVB stations. They communicate within VLAN 100.
Create VM 1 with the MAC address 0050-5684-21C7 on EVB station 1, and configure VM1 as the
FTP server with a CIR of 2048 kbps and a PIR of 4096 kbps. Only the R&D center is allowed to
access the network.

13
Figure 3 Network diagram
Configuration procedure
This section only contains EVB configurations.
Configuring the EVB bridge
# Create VLAN 100 on EVB bridge 1.
<EVB_bridge1> system-view
[EVB_bridge1] vlan 100
[EVB_bridge1-vlan100] quit
# Enable EVB on GigabitEthernet 1/0/1 that connects to EVB station 1, and configure
GigabitEthernet 1/0/1 to operate in trunk mode.
[EVB_bridge1] interface gigabitethernet 1/0/1
[EVB_bridge1-GigabitEthernet1/0/1] evb enable
[EVB_bridge1-GigabitEthernet1/0/1] port link-type trunk
[EVB_bridge1-GigabitEthernet1/0/1] quit
# Enable LLDP on EVB bridge 1 globally. Enable LLDP on GigabitEthernet 1/0/1, and configure the
Nearest non-TPMR Bridge agent for LLDP to operate in TxRx mode.
[EVB_bridge1] lldp global enable
[EVB_bridge1] interface gigabitethernet 1/0/1
[EVB_bridge1-GigabitEthernet1/0/1] lldp enable
[EVB_bridge1-GigabitEthernet1/0/1] lldp agent nearest-nontpmr admin-status txrx
[EVB_bridge1-GigabitEthernet1/0/1] quit
# Specify the IP address and port number for the default VSI manager on EVB bridge 1.
[EVB_bridge1] evb default-manager ip 192.168.1.1 port 8080
Configure other EVB bridges in the same way. (Details not shown.)