HPE FlexNetwork 10500 SERIES User manual

HPE FlexNetwork 10500 Switch Series
EVB Configuration Guide
Part number: 5998-8850R
Software version: 10500-CMW710-R7178
Document version: 6W100-20160129

© Copyright 2016 Hewlett Packard Enterprise Development LP
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 trademarks of the Microsoft group of companies.
Adobe® andAcrobat® are trademarks ofAdobe Systems Incorporated.
Java and Oracle are registered trademarks of Oracle and/or its affiliates.
UNIX® is a registered trademark of The Open Group.

i
Contents
Configuring EVB ·····························································································1
Overview····························································································································································1
Basic concepts···········································································································································2
EVB working mechanism···························································································································2
Protocols and standards ····························································································································3
Configuration restrictions and guidelines···········································································································3
EVB configuration task list ·································································································································4
Enabling EVB·····················································································································································4
Configuring LLDP···············································································································································5
Specifying a default VSI manager······················································································································5
Configuring VDP negotiation parameters ··········································································································5
Configuring an S-channel ··································································································································6
Creating an S-channel ·······························································································································6
Configuring an S-channel interface or S-channel aggregate interface ······················································7
Configuring the RR mode for an S-channel·······························································································8
Configuring 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 VSI filters ································································································································9
Activating a VSI interface or VSI aggregate interface··············································································11
Displaying and maintaining EVB······················································································································11
EVB configuration example······························································································································12
Document conventions and icons·································································17
Conventions·····················································································································································17
Network topology icons····································································································································18
Support and other resources ········································································19
Accessing Hewlett Packard Enterprise Support ······························································································19
Accessing updates···········································································································································19
Websites ··················································································································································20
Customer self repair·································································································································20
Remote support········································································································································20
Documentation feedback ·························································································································20
Index·············································································································22

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 monitoring,
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 (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 calledER 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 (VSI)—A port on a VM that directly connects to the DRP of an ER. A
VSI is associated with a logicalentity called VSIinstance,which is identified by the VSI Instance
Identifier (VSIID). A VSI 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)—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
An EVB station and an EVB bridge go through the following steps to implement VM traffic
management:
1. Use the S-channel Discovery and Configuration Protocol (CDCP) to establish an S-channel.
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.
2. Exchange EVB TLVs through LLDP to negotiate EVB capabilities for the S-channel, such as
RR, ECP parameters, and VDP parameters.
3. Use the VSI Discovery and Configuration Protocol (VDP) to associate the VSIs of VMs with the
bridge port.
The bridge uses the VSI interfaces to manage traffic for VMs.
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 comprises
the VSIID, VSI type, and VSI version.
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.
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. The VSI manager notifies the bridge to delete the VSI
interface.
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.
Configuration restrictions and guidelines
When you configure EVB, follow these restrictions and guidelines:
Hardware restrictions and guidelines
EVB is applicable only to interfaces on the following interface modules:
•EC interface modules.
•SE interface modules:
{LSUM2GP44TSSE0(JH191A, JH199A).
{LSUM2GT48SE0(JH192A, JH200A).
{LSU1CGC2SE0(JG916A).
•SF interface modules.
•SG interface modules.
Traffic received from a port enabled with EVB can be forwarded only through interface cards that
support EVB.
Software restrictions and guidelines
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
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
Do not create a service instance for an interface enabled with EVB, and vice versa.
Interfaces enabled with EVB cannot operate in route mode. For more information about Ethernet
interface link modes, see Interface Configuration Guide.
After you enable EVB on a Layer 2 Ethernet interface or a Layer 2 aggregate interface in a VLAN, the
interface does not support Layer 3 services.

4
After you enable EVB on a Layer 2 Ethernet interface or a Layer 2 aggregate interface in a VLAN, the
interface does not support Layer 2 multicast services.
After you add an interface to a multiport unicast MAC address entry, the interface cannot forward
traffic received from interfaces enabled with EVB. For more information about multiport unicast MAC
address entries, see Layer 2—LAN Switching Configuration Guide.
Do not configure an interface enabled with EVB 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
•Configuring the RR mode for an S-channel
•Configuring MAC address learning for an S-channel
(Optional.) Configuring a VSI interface or VSI aggregate interface:
•Creating a VSI interface or VSI aggregate interface
•Configuring VSI filters
•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.
Adefault S-channel is created on an interface after EVB is enabled on the interface. Both SCID and
SVID are 1. After an S-channel is created, an S-channel interface or S-channel aggregate interface
is created and operates in access mode.
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. Configure the interface to
operate in trunk mode. port link-type trunk By default, the interface operates
in access mode.
4. Enable EVB. evb enable By default, EVB is disabled on an
interface.

5
Configuring LLDP
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, so you must configure LLDP.
For detailed information about the lldp global enable, lldp enable and lldp agent
nearest-nontpmr admin-status 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 view or Layer 2
aggregate interface view. interface interface-type
interface-number N/A
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 a De-Associate packet) from a station, it
contacts the VSI manager specified in the VDPpacketto get VSI interface resources and policies for
the station.
The VSI manager ID TLV in a VDP packet carries the VSI manager's IP address. If the value for the
TLV is 0, the VDP packet doesnot contain a VSI manager's IPaddress, so the bridge communicates
with the specified default VSI manager.
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
ip-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 receives no
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 as:
VDP response-wait-delay time (seconds) = 2VDP resource-wait-delay × 10—5.

6
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
receives no keepalive from the station before the timer expires, it releases resources reserved for the
association. The VDP keepalive time is calculated as:
VDP keepalive time (seconds) = 1.5 × [ 2VDP keepalive + (2 × ECP maximum retransmission time + 1) ×
2ECP retransmission ] × 10—5.
The value 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:
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. Configure the VDP
resource-wait-delay timer
exponent.
evb vdp timer
resource-wait-delay exponent
value The default is 20.
4. Configure 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 also manually create an S-channel by
performing this task. If an (SCID, SVID) pair for an S-channel is created both automatically and
manually, the one automatically created takes precedence.
After an S-channel is created, an S-channel interface or S-channel aggregate interface is generated.
Removing an S-channel also removes the S-channel interface or S-channel aggregate interface. A
manually created S-channel interface or S-channel aggregate interface operates in access mode.
An S-channel interface or S-channel aggregate interface that is automatically created through CDCP
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 guidelines:
•Create an S-channel on an interface with EVB enabled. Otherwise, an error message appears.
•Adefault S-channel is created on an interface after EVB is enabled on the interface. Both SCID
and SVID are 1.
•When you manually create an S-channel,do not use the SCID or SVID being usedby any other
S-channel. Otherwise, an error message appears.
•To manually create or remove S-channel, disable CDCP that automatically performs these
operations.

7
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.
Configuring an S-channel interface or S-channel aggregate
interface
To configure an S-channel interface:
Step Command Remarks
1. Enter system view. system-view N/A
2. Enter S-channel interface
view. interface s-channel
interface-number:channel-id N/A
3. (Optional.) Configure the
expected bandwidth of the
S-channel interface. bandwidth bandwidth-value
By default, the expected
bandwidth of an S-channel
interface is the default maximum
bandwidth of the physical port to
which the S-channel interface
belongs.
4. (Optional.) Restore the
default settings for the
S-channel interface. default N/A
5. (Optional.) Configure a
description for the S-channel
interface. description text The default description
information is "interface name
Interface."
6. Bring up the S-channel
interface. undo shutdown By default, the S-channel
interface is up.
To configure an S-channel aggregate interface:
Step Command Remarks
1. Enter system view. system-view N/A
2. Enter S-channel aggregate
interface view. interface schannel-aggregation
interface-number:channel-id N/A
3. (Optional.) Configure a
description for the
S-channel aggregate
interface. description text The default description information
is "interface name Interface."
4. Bring up the S-channel
aggregate interface. undo shutdown By default, the S-channel
aggregate interface is up.