Configuring EVB Overview 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. Data center virtualization includes network virtualization, storage virtualization, and server virtualization.
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.
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.
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.
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.
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.
To create an S-channel: Step Command Remarks Enter system view. system-view Enter Layer 2 Ethernet interface interface-type interface view or Layer 2 interface-number aggregate interface view. By default, only an automatically evb s-channel channel-id created default S-channel (with Create an S-channel. [ service-vlan svlan-id ] both SCID and SVID as 1) exists on an interface with EVB enabled.
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. If the EVB bridge supports the RR mode, when the EVB station requests the use of the RR mode, the bridge performs the following tasks: •...
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. Otherwise, some VSI interfaces or VSI aggregate interfaces might be automatically deleted.
Page 13
• When you delete a VSI filter that contains information about a VLAN on a VSI interface, the other VSI filters on all VSI interfaces of an S-channel interface might not contain the VLAN. If they do not, the S-channel interface automatically denies traffic from the VLAN that is configured on the VSI filter.
Activating a VSI interface or VSI aggregate interface Configurations such as traffic monitoring (see ACL and QoS Configuration Guide) on a VSI interface or VSI aggregate interface take effect only after the VSI interface or VSI aggregate interface is activated. When a VSI interface or VSI aggregate interface is not activated, only configure filters on the VSI interface or VSI aggregate interface.
Page 16
Configuration procedure This section only contains EVB configurations. 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 GigabitEthernet 1/0/1 that connects to EVB station 1, and configure GigabitEthernet 1/0/1 to operate in trunk mode.
Page 17
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.
Page 18
Figure 6 Network List page c. Define the VSI type of VM 1: Select VSI Type from the navigation tree. The VSI Type List page appears. Click Add. On the page that appears, do the following: − Enter VM1 VSI for Name. −...
Page 19
Figure 8 Connection List page 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.
Document conventions and icons Conventions This section describes the conventions used in the documentation. Port numbering in examples The port numbers in this document 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.
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.
Support and other resources Accessing Hewlett Packard Enterprise Support • For live assistance, go to the Contact Hewlett Packard Enterprise Worldwide website: www.hpe.com/assistance • To access documentation and support services, go to the Hewlett Packard Enterprise Support Center website: www.hpe.com/support/hpesc Information to collect •...
For more information and device support details, go to the following website: www.hpe.com/info/insightremotesupport/docs Documentation feedback Hewlett Packard Enterprise is committed to providing documentation that meets your needs. To help us improve the documentation, send any errors, suggestions, or comments to Documentation Feedback (docsfeedback@hpe.com). When submitting your feedback, include the document title,...
Page 24
part number, edition, and publication date located on the front cover of the document. For online help content, include the product name, product version, help edition, and publication date located on the legal notices page.