HP 6125XLG User manual

HP 6125XLG Blade Switch
EVB
Configuration Guide
Part number: 5998-3728
Software version: Release 2306
Document version: 6W100-20130912

Legal and notice information
© Copyright 2013 Hewlett-Packard Development Company, L.P.
No part of this documentation may be reproduced or transmitted in any form or by any means without
prior written consent of Hewlett-Packard Development Company, L.P.
The information contained herein is subject to change without notice.
HEWLETT-PACKARD COMPANY MAKES NO WARRANTY OF ANY KIND WITH REGARD TO THIS
MATERIAL, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY
AND FITNESS FOR A PARTICULAR PURPOSE. Hewlett-Packard shall not be liable for errors contained
herein or for incidental or consequential damages in connection with the furnishing, performance, or
use of this material.
The only warranties for HP 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. HP shall not be liable for technical or editorial errors or omissions contained
herein.

i
Contents
Configuring EVB··························································································································································· 1
Overview············································································································································································1
Basic concepts ··························································································································································2
EVB working mechanism ·········································································································································2
Protocols and standards ··········································································································································3
EVB configuration task list ················································································································································3
Enabling EVB ·····································································································································································3
Configuring LLDP·······························································································································································4
Specifying a default VSI manager ··································································································································4
Configuring VDP negotiation parameters·······················································································································5
Configuring an S-channel·················································································································································5
Creating an S-channel ·············································································································································5
Configuring a description for an S-channel interface···························································································6
Configuring the RR mode for an S-channel ···········································································································6
Configuring MAC address learning for an S-channel··························································································7
Configuring a VSI ·····························································································································································7
Creating a VSI ··························································································································································7
Configuring VSI filters ··············································································································································8
Activating a VSI························································································································································9
Displaying and maintaining EVB·····································································································································9
EVB configuration example··············································································································································9
Support and other resources ·····································································································································14
Contacting HP ································································································································································ 14
Subscription service ·············································································································································· 14
Related information························································································································································ 14
Documents······························································································································································ 14
Websites································································································································································· 14
Conventions ···································································································································································· 15
Index ···········································································································································································17

1
Configuring EVB
Edge Virtual Bridging (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.
Overview
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 called ER ports. An EVB station can have multiple
ERs.
•S-channel—A point-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 logical entity called VSI instance, which is identified by the VSI Instance Identifier
(VSIID). A VSI is associated with the EVB bridge port to implement VM traffic management and
policy configuration. A VSI can be considered as 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 VSIs 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.

3
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 and apply policies.
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.
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.
EVB configuration task list
This document only describes EVB bridge configuration. For information about EVB station configuration,
see the station manual.
Tasks at a
g
lance
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 a description for an S-channel interface
•Configuring the RR mode for an S-channel
•Configuring MAC address learning for an S-channel
(Optional.) Configuring a VSI:
•Creating a VSI
•Configuring VSI filters
•Activating a VSI
Enabling EVB
Perform this task to enable EVB on a bridge port that directly connects to a station. After that, you must
configure the port to operate in trunk mode. Otherwise, EVB does not work because VSI filter
configuration (see "Configuring VSI filters") does not take effect.
After you enable EVB on the bridge port, the device cannot forward the data received from the port at
Layer 3.
Do not enable both EVB and VLAN mapping, or both EVB and TRILL on a port.
Do not configure the qinq enable or qinq ethernet-type service-tag command on a port enabled with
EVB, and vice versa. For more information about the two commands, see Layer 2—LAN Switching
Command Reference.
To enable EVB:

4
Ste
p
Command
Remarks
1. Enter system view. system-view N/A
2. Enter Ethernet interface view. interface interface-type
interface-number N/A
3. Enable EVB. evb enable
By default, EVB is disabled on a
bridge port.
After EVB is enabled, a default
access-type S-channel with both
SCID and SVID as 1 is
automatically created on this port.
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:
Ste
p
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 Ethernet interface view. interface interface-type
interface-number N/A
4. Enable LLDP on the interface lldp enable By default, LLDP is enabled on a
port.
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 other than a De-Associate packet from a station, it contacts the
VSI manager specified in the VDP packet to get VSI resources and policies for the station.
The VSI manager ID TLV in a VDP packet includes the VSI manager's IP address. If the value for the TLV
is all-zero, the VDP packet does not contain a VSI manager's IP address, so the bridge communicates
with the specified default VSI manager.
To specify a default VSI manager:
Ste
p
Command
Remarks
1. Enter system view. system-view N/A

5
Ste
p
Command
Remarks
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 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.
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 for the corresponding VM. Then
the bridge starts a "VDP keepalive timer" for the VSI. 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 of the VDP keepalive exponent is the larger of the values proposed by the station and bridge
through EVB TLV. The ECP maximum retransmission time and ECP retransmission exponent are fixed to 3
and 16, respectively.
To configure VDP negotiation parameters:
Ste
p
Command
Remarks
1. Enter system view. system-view N/A
2. Enter Ethernet 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.

6
If an (SCID, SVID) pair for an S-channel is created both automatically and manually, the one
automatically created takes precedence.
A manually created S-channel has an access link type, and an automatically created S-channel has a
trunk link type.
The device checks C-VLAN tagged frames (frames taking the original VLAN tags) entering an S-channel
for their C-VLAN tags. If the C-VLAN does not belong to the VLANs that the S-channel and the port where
the S-channel is created permit, the device cannot transmit the frames. Therefore, you must specify the
C-VLAN range for the frames that an S-channel can transmit before you assign the S-channel and the port
where the S-channel is created to these C-VLANs. For more information about assigning ports to a VLAN,
see Layer 2—LAN Switching Configuration Guide.
Follow these guidelines when you create an S-channel:
•Create an S-channel on a port with EVB enabled. Otherwise, an error is displayed.
•A default S-channel with both SCID and SVID as 1 is automatically created for the port on which
EVB is enabled.
•When you manually create an S-channel, do not use the SCID or SVID being used by any other
S-channel. Otherwise, an error is displayed.
•To manually create or remove S-channel, disable CDCP to automatically perform these operations.
To create an S-channel:
Ste
p
Command
Remarks
1. Enter system view. system-view N/A
2. Enter Ethernet 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 the automatically
created default S-channel, with
both SCID and SVID as 1, exists on
a port with EVB enabled.
Configuring a description for an S-channel interface
Ste
p
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. Configure a description for
the S-channel interface. description text The default description information
is "interface name Interface."
Configuring the RR mode for an S-channel
EVB TLVs exchanged through LLDP allow an EVB station and EVB bridge to negotiate the use of reflective
relay. When the EVB station requests the use of RR mode and the EVB bridge supports RR mode, the
bridge automatically enables RR mode for the S-channel and saves the configuration in the configuration
file on the bridge. You can also manually enable RR mode for an S-channel by performing this task.

7
To configure RR mode for an S-channel:
Ste
p
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. Enable RR mode for the
S-channel. evb reflective-relay By default, the RR mode is disabled
for an S-channel.
Configuring MAC address learning for an S-channel
You can manually disable the MAC address learning function for an S-channel by performing this task.
To disable MAC address learning for an S-channel:
Ste
p
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. 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.
IMPORTANT:
•For an S-channel with RR mode
disabled, do not disable its
MAC address learning
function. Otherwise, the bridge
might fail to forward traffic for
VMs on the EVB station.
•After you disable the MAC
address learning function for
an S-channel, the bridge will
discard packets with an
unknown source MAC address.
Configuring a VSI
Creating a VSI
A VSI is created on an S-channel interface through this task.
VSIs are typically created by a VSI manager. You can also create a VSI or modify its Pre-Associate and
Associate properties.
A VSI is a subinterface of an S-channel interface on an EVB bridge. Removing an S-channel also removes
all its VSIs.

8
To create a VSI:
Ste
p
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. Create a VSI. evb vsi vsi-local-id { association |
pre-association }
By default, no VSI exists on an
S-channel.
Configuring VSI filters
A VSI filter contains a set of VID values (VLAN information) or a set of MAC and VID values (<MAC,
VLAN>). The EVB bridge uses a VSI filter to identify VSI traffic for a VM. Filters are usually assigned by
a VSI manager. You can also manually create or remove VSI filters by performing this task.
Follow these guidelines when you configure VSI filters for VSIs on an S-channel:
•Before the configuration, make sure the S-channel where you configure a VSI filter operates in trunk
mode. Otherwise, the configuration fails.
•After you configure a VSI filter on a VSI, an S-channel interface automatically permits the VLAN that
is configured in the VSI filter for the subordinate VSI. The same rule takes effect on Layer 2 interfaces
associated with S-channels.
•After you delete a VSI filter that contains information about a VLAN on a VSI, if other VSI filters on
all VSIs of an S-channel interface do not contain the VLAN, the S-channel interface automatically
denies traffic from the VLAN that is configured on the VSI filter. The same rule takes effect on Layer
2 interfaces associated with S-channels.
•When a filter configured on a VSI contains information about a VLAN, you cannot configure the
filter on the same VSI again or on other VSIs of the S-channel interface to which the VSI belongs.
Otherwise, the system displays an error.
•If the VSI filter is a set of VID values, and the MAC address learning function for the corresponding
S-channel is disabled, traffic for the VSI cannot be forwarded.
•Activate a VSI after configuring a VSI filter, and deactivate a VSI before removing a VSI filter.
To configure a VSI filter for a VSI:
Ste
p
Command
Remarks
1. Enter system view. system-view N/A
2. Enter VSI view.
interface s-channel
interface-number:channel-id.vsi-loc
al-id
N/A
3. Configure a VSI filter. evb vsi filter vlan vlan-id [ mac
mac-address ]
By default, no VSI filter is
configured.

9
Activating a VSI
Configurations such as traffic policing for a VSI (see ACL and QoS Configuration Guide) take effect only
after the VSI is activated. When a VSI is not activated, do not make any configuration except for VSI filter
configuration for the VSI.
To activate a VSI, you must first configure a VSI filter. To remove a VSI filter for a VSI, you must first
deactivate the VSI.
To activate a VSI:
Ste
p
Command
Remarks
1. Enter system view. system-view N/A
2. Enter VSI view.
interface s-channel
interface-number:channel-id.vsi-lo
cal-id
N/A
3. Activate the VSI. evb vsi active By default, no VSI is activated.
4. (Optional.) Configure a
description for the VSI. description text The default description information is
"interface name Interface."
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 ]
Display S-channel information. display evb s-channel [ interface interface-type interface-number ]
Display EVB summary. display evb summary
Display VSI information. display evb vsi [ verbose ] [ interface interface-type interface-number ]
Display information about an
S-channel interface or a VSI.
display interface [ s-channel [ interface-number:channel-id |
interface-number:channel-id.vsi-local-id ] ] [ brief [ description ] ]
Clear statistics for an S-channel
interface or a VSI.
reset counters interface [ s-channel [ 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 comprises two switches that form an IRF fabric,
four EVB bridges, and four EVB stations. They communicate within VLAN 100.
Create VM 1 with a MAC address of 0050-5684-21C7 on EVB station 1, and set 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.

10
Figure 3 Network diagram
Configuration procedure
This section only contains EVB configurations.
1. Configure 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 Ten-GigabitEthernet 1/0/1 that connects to EVB station 1, and configure
Ten-GigabitEthernet 1/0/1 to operate in trunk mode.
[EVB_bridge1] interface ten-gigabitethernet 1/0/1
[EVB_bridge1-Ten-GigabitEthernet1/0/1] evb enable
[EVB_bridge1-Ten-GigabitEthernet1/0/1] port link-type trunk
[EVB_bridge1-Ten-GigabitEthernet1/0/1] quit
# Enable LLDP on EVB bridge 1 globally. Enable LLDP on Ten-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 ten-gigabitethernet 1/0/1
[EVB_bridge1-Ten-GigabitEthernet1/0/1] lldp enable
[EVB_bridge1-Ten-GigabitEthernet1/0/1] lldp agent nearest-nontpmr admin-status txrx
[EVB_bridge1-Ten-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.)
2. Configure the EVB station:
Configure the EVB station on the VMM. For more information about configuring VMs through
VMM, see the VMM manual. (Details not shown.)

11
3. Configure the NMS:
Use VAN Connection Manager of IMC on the NMS to configure network resources.
The IMC VCM 5.2 (E0401L01) version is used in this section.
Figure 4 VAN Connection Manager
To configure the NMS, log in to IMC, click the Resource tab, and select VAN Connection Manager
from the navigation tree (see Figure 4), and perform the following steps:
a. Add an EVB bridge (Edge Switch):
Select Edge Switch from the navigation tree, click Add on the page that appears, select the four
devices in the IP address range of 192.168.1.11 through 192.168.1.14 from IP View, and
click OK.
EVB bridge 1, EVB bridge 2, EVB bridge 3, and EVB bridge 4 are displayed in the Edge Switch
List page, as shown in Figure 5.
Figure 5 Edge Switch List page
b. Add an FTP network:

12
Select Network from the navigation tree, click Add on the page that appears, enter For FTP for
Name, 100 for VLAN ID, and 10 for Max. Connections, and click OK.
The network name For FTP is displayed in the Network List page, as shown in Figure 6.
Figure 6 Network List page
c. Define the VSI type of VM 1:
iSelect VSI Type from the navigation tree. The VSI Type List page appears.
ii Click Add.
iii On the page that appears, enter VM1 VSI for Name, select For FTP from the Network list,
select the Bandwidth Control and VM Access Control options, enter 172.16.1.0 for Client IP,
0.0.0.255 for Wildcard Mask, select BOTH from the Filtering Direction list, and enter 2048
for CIR (kbps) and 4096 for PIR (kbps).
iv Click Save and Release.
The VSI type VM1 VSI is displayed in the VSI Type List page, as shown in Figure 7.
Figure 7 VSI Type List page
d. Bind the VSI type VM1 VSI to the vNIC of VM 1 to define the connection:
iSelect Connection from the navigation tree. The Connection List page appears.
ii Click Add.
iii On the page that appears, enter VM1CON for Name, click Select on the right side of the page, select
the VM1 option from the popup window and click OK (the MAC address 0050-5684-21c7 of VM 1
is displayed in the vNIC field), and then select For FTP from the Network list, VM1 VSI from VSI Type,
and VM1 VSI (V1) from VSI Type Version.
iv Click OK.
The connection VM1CON is displayed in the Connection List page, as shown in Figure 8.

13
Figure 8 Connection List page
4. Verify the configuration:
After VM 1 starts, the VAN Connection Manager service component of IMC deploys the VSI type
VM1 VSI on EVB bridge 1. Only the R&D center can use the FTP service on VM 1.

14
Support and other resources
Contacting HP
For worldwide technical support information, see the HP support website:
http://www.hp.com/support
Before contacting HP, collect the following information:
•Product model names and numbers
•Technical support registration number (if applicable)
•Product serial numbers
•Error messages
•Operating system type and revision level
•Detailed questions
Subscription service
HP recommends that you register your product at the Subscriber's Choice for Business website:
http://www.hp.com/go/wwalerts
After registering, you will receive email notification of product enhancements, new driver versions,
firmware updates, and other product resources.
Related information
Documents
To find related documents, browse to the Manuals page of the HP Business Support Center website:
http://www.hp.com/support/manuals
•For related documentation, navigate to the Networking section, and select a networking category.
•For a complete list of acronyms and their definitions, see HP FlexNetwork Technology Acronyms.
Websites
•HP.com http://www.hp.com
•HP Networking http://www.hp.com/go/networking
•HP manuals http://www.hp.com/support/manuals
•HP download drivers and software http://www.hp.com/support/downloads
•HP software depot http://www.software.hp.com
•HP Education http://www.hp.com/learn

15
Conventions
This section describes the conventions used in this documentation set.
Command conventions
Convention Descri
p
tion
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 Descri
p
tion
Boldface Window names, button names, field names, and menu items are in bold text. For
example, the New User window appears; click OK.
> Multi-level menus are separated by angle brackets. For example, File >Create >Folder.
Symbols
Convention Descri
p
tion
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.

16
Network topology icons
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 switching engine
on a unified wired-WLAN switch.
Represents an access point.
Represents a security product, such as a firewall, a UTM, or a load-balancing or security
card that is installed in a device.
Represents a security card, such as a firewall card, a load-balancing card, or a
NetStream card.
Port numbering in examples
The port numbers in this document are for illustration only and might be unavailable on your device.


17
Index
A
activating
EVB VSI filter, 9
B
bridging
EVB configuration, 1, 3, 9
EVB default VSI manager specification, 4
EVB LLDP configuration, 4
EVB S-channel configuration, 5
EVB S-channel interface, 6
EVB S-channel MAC address learning
configuration, 7
EVB S-channel RR mode configuration, 6
EVB S-channel VSI configuration, 7
EVB VDP negotiation parameter
configuration, 5
C
configuring
EVB, 1, 3, 9
EVB LLDP, 4
EVB S-channel, 5
EVB S-channel interface, 6
EVB S-channel MAC address learning, 7
EVB S-channel RR mode, 6
EVB S-channel VSI, 7
EVB VDP negotiation parameter, 5
EVB VSI filter, 8
creating
EVB S-channel, 5
EVB VSI, 7
D
default
EVB default VSI manager, 4
displaying
EVB, 9
E
edge relay (EVB), 2
Edge Virtual Bridging. Use EVB
enabling
EVB, 3
EVB
basic concepts, 2
configuration, 1, 3, 9
default VSI manager specification, 4
displaying, 9
edge relay, 2
enabling, 3
how it works, 2
LLDP configuration, 4
maintaining, 9
protocols and standards, 3
reflective relay, 2
S-channel, 2
S-channel configuration, 5
S-channel creation, 5
S-channel interface configuration, 6
S-channel MAC address learning configuration, 7
S-channel RR mode configuration, 6
S-channel VSI configuration, 7
VDP negotiation parameter configuration, 5
virtual station interface, 2
VSI filter activation, 9
VSI filter configuration, 8
F
filtering
EVB VSI filter configuration, 8
L
LLDP
EVB LLDP configuration, 4
M
MAC address
EVB S-channel MAC address learning
configuration, 7
maintaining
EVB, 9
N