H3C Intelligent Management Center

Transcription

1 H3C Intelligent Management Center VAN Connection Manager Administrator Guide New H3C Technologies Co., Ltd. Software version: IMC VCM 7.3 (E0501) Document version: 5PW

2 Copyright , New 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 New H3C Technologies Co., Ltd. Trademarks H3C,, H3CS, H3CIE, H3CNE, Aolynk,, H 3 Care,, IRF, NetPilot, Netflow, SecEngine, SecPath, SecCenter, SecBlade, Comware, ITCMM and HUASAN are trademarks of New 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.

3 Preface The H3C IMC VAN Connection Manager Administrator Guide includes 13 chapters, which describe the management of network resources on the IMC VAN Connection Manager, the generic configuration procedures, and the important parameters. This preface includes the following topics about the documentation: Audience. Conventions. About the H3C IMC 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 H3C IMC. 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 Boldface Italic Description Bold text represents commands and keywords that you enter literally as shown. Italic text represents arguments that you replace with actual values. # A line that starts with a pound (#) sign is comments. GUI conventions Convention Boldface > Description 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.

4 Symbols Convention WARNING! CAUTION: IMPORTANT: NOTE: TIP: Description An alert that calls attention to important information that if not understood or followed can result in personal injury. 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. An alert that calls attention to essential information. An alert that contains additional or supplementary information. An alert that provides helpful information. About the H3C IMC documentation set The H3C IMC documentation set includes the following categories of documents: Category Documents Purposes H3C IMC Getting Started Guide Quickly guides you through the IMC main features and troubleshooting common problems. Hardware specifications and installation H3C IMC Centralized Deployment Guide with Embedded Database H3C IMC Centralized Deployment Guide with Local Database H3C IMC Centralized Deployment Guide with Remote Database H3C IMC Distributed Deployment Guide with Local Database H3C IMC Distributed Deployment Guide with Remote Database H3C IMC Probe Installation Guide SQL Server 2008 Installation and Configuration Guide SQL Server 2008 R2 Installation and Configuration Guide SQL Server 2012 Installation and Configuration Guide SQL Server 2014 Installation and Configuration Guide Oracle 11g Installation and Configuration Provides a complete guide to IMC platform and components installation and centralized deployment using embedded database. Provides a complete guide to IMC platform and components installation and centralized deployment using local database. Provides a complete guide to IMC platform and components installation and centralized deployment using remote database. Provides a complete guide to IMC platform and components installation and distributed deployment using local database. Provides a complete guide to IMC platform and components installation and distributed deployment using remote database. Provides a complete guide to IMC Probe installation and deployment. Guides you through installing SQL Server 2008 for IMC. Guides you through installing SQL Server 2008 R2 for IMC. Guides you through installing SQL Server 2012 for IMC. Guides you through installing SQL Server 2014 for IMC. Guides you through installing Oracle 11g on Linux for IMC.

5 Category Documents Purposes Guide(for Linux) Software configuration Oracle 11g R2 Installation and Configuration Guide(for Linux) Oracle 12c Installation and Configuration Guide(for Linux) Red Hat Enterprise Linux 6.4 Installation Guide Red Hat Enterprise Linux 7.0 Installation Guide H3C IMC Enterprise and Standard Platform Administrator Guide H3C IMC Quality of Service Manager Administrator Guide H3C IMC Resource Automation Manager Administrator Guide H3C IMC Service Health Manager Administrator Guide H3C IMC VAN Connection Manager Administrator Guide H3C IMC VAN Software Defined Network Manager Administrator Guide H3C IMC VAN Fabric Manager Administrator Guide H3C IMC Application Manager Administrator Guide H3C IMC Branch Intelligent Management System Administrator Guide H3C IMC Business Service Manager Administrator Guide H3C IMC IPsec VPN Manager Administrator Guide H3C IMC MPLS VPN Manager Administrator Guide H3C IMC Network Traffic Guides you through installing Oracle 11g R2 on Linux for IMC. Guides you through installing Oracle 12c on Linux for IMC. Guides you through installing Red Hat Enterprise Linux 6.4 for IMC. Guides you through installing Red Hat Enterprise Linux 7.0 for IMC. Describes operation procedures on the IMC platform. Describes operation procedures on the IMC Quality of Service Manager. Describes operation procedures on the Resource Automation Manager. Describes operation procedures on the Service Health Manager. Describes operation procedures on the IMC VAN Connection Manager. Describes operation procedures on the IMC VAN Software Defined Network Manager. Describes operation procedures on the IMC VAN Fabric Manager. Describes operation procedures on the IMC Application Manager. Describes operation procedures on the IMC Branch Intelligent Management System. Describes operation procedures on the IMC Business Service Manager. Describes operation procedures on the IMC IPsec VPN Manager. Describes operation procedures on the IMC MPLS VPN Manager. Describes operation procedures on the IMC

6 Category Documents Purposes Analyzer Administrator Network Traffic Analyzer. Guide Operations and maintenance H3C IMC Service Operation Manager Administrator Guide H3C IMC User Behavior Auditor Administrator Guide H3C IMC UC Health Manager Admin Guide H3C IMC Wireless Service Manager Administrator Guide H3C IMC User Access Manager Administrator Guide H3C IMC TACACS+ Authentication Manager Administrator Guide H3C IMC EAD Security Policy Administrator Guide Online Help Release Notes Describes operation procedures on the IMC Service Operation Manager. Describes operation procedures on the IMC User Behavior Auditor. Describes operation procedures on the IMC UC Health Manager. Describes operation procedures on the IMC Wireless Service Manager. Describes operation procedures on the IMC User Access Manager. Describes operation procedures on the IMC TACACS+ Authentication Manager. Describes operation procedures on the IMC EAD Security Policy Manager. Helps you properly use IMC. Provides most recent IMC release information. Obtaining documentation To access the most up-to-date H3C product documentation, go to the H3C website at To obtain information about installation, configuration, and maintenance, click To obtain software version information such as release notes, click Technical support Documentation feedback You can your comments about product documentation to We appreciate your comments.

7 Content VCM overview 1 Features 1 Basic concepts 1 Support for 802.1Qbg solutions 1 Support for VEB 1 Support for EVB 2 Quick start 4 VCM navigation menu 4 Quick Start 4 Common operations 5 Navigating a list 5 Sorting a list 5 Refreshing a list 5 Preparations 6 Configuring VRM 6 Installing plug-ins 6 Configuring VRM parameters 7 Configuring the edge switch 7 Configuring EVB 7 Configuring LLDP 7 Specifying the default VSI Type Manager 7 Customizing VCM widgets 8 Adding VAN View TopN to a space 8 Viewing the VAN View TopN widget 8 Connection utilization 9 ACL utilization 9 Configuring the VAN View TopN widget 9 Manually refreshing the VAN View TopN widget 10 Deleting the VAN View TopN widget 10 Managing plug-ins 12 Managing the vcenter plug-in 12 Registering the vcenter plug-in 12 Managing connections on vcenter Server 13 Modifying the vcenter plug-in 15 Uninstalling the vcenter plug-in 15 Managing the VCE plug-in 16 Registering the VCE plug-in 16 Configuring the VSI for a port group 16 Modifying a VCE plug-in 18 Uninstalling the VCE plug-in 18 Managing the XenCenter plug-in 18 Registering the XenCenter plug-in 18 Managing connections on the XenCenter server 19 Deleting the XenCenter plug-in 19 Managing the VMM plug-in 19 Registering a VMM plug-in 19 Managing connections on VMM 22 Deleting the VMM plug-in 25 Managing edge switches 27 Viewing the edge switch list 27 Querying edge switches 27 Adding edge switches 28 i

8 Automatic method 28 Manual method 28 Configuring the ACL number range for an edge switch 29 Specifying the maximum connections for an edge switch 30 Configuring the Default Manager for an edge switch 30 Viewing the VM migration history of an edge switch 31 Deleting edge switches 31 Managing networks 32 Overview 32 Network management privileges 32 Predefined network management privileges 32 Modular VCM privileges 32 Assigning network management privileges 33 Network module application scenarios 36 Viewing the network list 36 Querying networks 36 Viewing network details 37 Adding a network 37 Network configuration example 38 Copying a network 39 Modifying a network 40 Deleting a network 40 Managing VSI Types 41 Managing VSI Type versions 41 Applying and removing a VSI Type 41 Viewing the VSI Type list 41 Querying a VSI Type 42 Viewing detailed information about a VSI Type or VSI Type version 43 Adding a VSI Type 44 Configuration procedure 44 Configuration example 46 Modifying a VSI Type 48 Releasing a VSI Type version 48 Deleting a VSI Type 48 Deleting a VSI Type version 48 Managing connections 50 Connection types 50 VEB connection 50 EVB connection 50 Automatic VSI Type migration with a VM migration 51 Viewing the connection list 51 Synchronizing the connections 51 Querying a connection 52 Viewing detailed information about a VM 52 Adding a connection 53 Deploying or undeploying a connection 54 Modifying a connection 54 Deleting a connection 55 Deploying a vapp 55 Managing life cycle reports 57 Overview 57 Migration History 57 Operation List 57 Managing migration records 58 Viewing the migration list 58 Querying historical migration records 59 Viewing the operation records of a VM migration process 60 Viewing migration details 60 ii

9 Viewing the historical record of VM migration in icon view 61 Managing operation records 62 Viewing the operation list 62 Querying connection deployment and undeployment processes 63 Viewing operation details 64 VEB scheme configuration example 65 Network requirements 65 Configuration procedures 65 Adding a SOAP template 66 Adding the edge switch and the two ESXi hosts to IMC 66 Synchronizing devices 67 Enabling CDP on the edge switch 67 Verifying ESXi host availability in VRM 68 Viewing virtual network topology 69 Configuring VCM 69 Creating a connection 74 EVB scheme configuration example 76 Network requirements 76 Configuration prerequisites 77 Configuration procedures 77 Configuring the HP 5900v virtual switch 77 Configuring the HPE Comware-based switch 82 Configuring IMC 83 Adding the edge switch and the two ESXi hosts to IMC 83 Configuring VCM 86 Creating a connection 91 Terminology 93 iii

10 VCM overview VAN Connection Manager (VCM) is an IMC service component that was developed based on the 802.1Qbg Edge Virtual Bridging (EVB) standard. VCM acts as the VSI (Virtual Station Interface) Manager in the EVB architecture. It manages VM traffic and VSI Types to implement automatic associations between the virtual machine (VM) lifecycle and network policies. Features VCM provides the following features: Support for the 802.1Qbg standard. Centralized VSI Type management. Automatic association between the VM lifecycle and network policies. Installing plug-ins that enable server administrators to manage connections from vmanager, which separates server management from network management. NOTE: In VCM, vmanager is a general name for virtual management software in IMC such as vcenter and VMM. Basic concepts The following concepts are used in VCM: Connection A vnic-to-vsi Type version binding. When a vnic accesses the network from a new location, the VSI Type version must be migrated on the corresponding switch. Edge switch Switch that is directly connected to a physical server where a VM resides. VCM deploys VSI Type settings to the edge switch to manage VM traffic. Network A management facility of VCM, with which you can assign VLANs for transferring the traffic between VMs and clients, as well as assign the VSI types for controlling the traffic between VMs and clients. In addition, with network management, you can authorize one or more operators or operator groups to manage the VSI types assigned to the network. VSI Type Virtual Station Interface Type. A profile that contains a set of network configurations for binding to a vnic of a VM, including bandwidth control, access control, and access priority settings. Support for 802.1Qbg solutions VCM supports all 802.1Qbg solutions: VEB, VEPA, and Multichannel. Because VCM operates in the same way in the VEPA and Multichannel solutions, this document refers to the two solutions collectively as the EVB solution. Support for VEB VCM support for VEB requires the cooperation of VRM, a subcomponent of the IMC Platform. VCM relies on VRM to obtain the VM status and access location information for VSI Type deployment 1

11 and undeployment. For information about VRM, see HPE Intelligent Management Center v7.3 Enterprise and Standard Platform Administrator Guide. Figure 1 VCM in VEB As shown in Figure 1: 1. VRM detects VM status changes on the physical server. 2. VCM obtains the VM information from VRM. 3. VCM finds the VSI Type bound to the VM, and then deploys or undeploys the VSI Type to the edge switch that connects to the physical server of the VM. The VRM component must be correctly configured before you use VCM in the VEB solution. For information about how to configure VRM, see "Preparations." Support for EVB Figure 2 VCM in EVB As shown in Figure 2: 1. The physical server exchanges VSI Type and connection information with VCM. 2. The physical server sends the VM-VSI Type ID/VSI Type version ID mappings to the directly connected edge switch by using VDP. 2

12 3. When the edge switch detects a VM status change on the physical server, it requests VCM to deploy or undeploy the correct VSI Type. 4. VCM replies to the request by deploying or undeploying the VSI Type on the edge switch. In this solution, VCM does not rely on VRM to obtain the VM status or access location information for VSI Type deployment and undeployment. However, VCM still needs VRM to obtain the VM migration history and physical server information. The absence or incorrect configuration of VRM might have the following consequences: The VM migration list on VCM is empty. The connection list does not contain information such as the name, physical server, and access location of VMs. For information about how to configure VRM, see "Preparations." VCM supports the EVB solution that is implemented based on the platforms VMware + HP 5900v + IMC (VCM). The HP 5900v switch is a virtual switch developed based on VMware vsphere. It can be installed on the vcenter to enable vcenter to manage EVB-capable vswitches. 3

13 Quick start The following information guides you quickly through the main functions of VCM. VCM navigation menu Click the Resource tab, and then select VAN Connection Manager from the navigation tree to expand the VCM navigation menu. The VCM navigation menu contains the following nodes: Quick Start Connection VSI Type Network Edge Switch Life Cycle Report Plug-In Management Click a node to enter the management page for the node. Quick Start 2. From the navigation tree, select VAN Connection Manager > Quick Start. The Quick Start page displays a chart that illustrates the workflow of the EVB solution, as shown in Figure 3. Figure 3 Quick Start The EVB solution works as follows: 4

14 3. The IMC operator configures the switch that connects to the physical server of the VM as an edge switch in VCM. Click 1 to enter the edge switch management page. 4. The IMC operator manages VSI Types in VCM. Click 2 to enter the VSI Type management page. 5. The physical server administrator uses the VSI Types obtained from VCM to create connections for VMs. Click 3 to enter the connection management page. 6. When a VM migrates from one physical server to another, the edge switch asks VCM to deploy or undeploy the VSI Type associated with the VM. 7. Click 5 to view the VM migration and connection operation history. Common operations Navigating a list If a list contains enough entries, use the following aids to navigate the list: Select 8, 15, 50, 100, or 200 at the bottom of the list to configure how many items per page you want to display. Click the Next Page icon to page forward in the list. Click the Last Page icon to page forward to the end of the list. Click the Previous Page icon to page backward in the list. Click the First Page icon to page backward to the front of the list. Sorting a list You can sort a list by every field that contains a Sort icon in the column label. When the list is sorted by a field in ascending order, the column label of the selected field is blue and contains an Ascending icon. When the list is sorted by a field in descending order, the column label of the selected field is blue and contains a Descending icon. Refreshing a list Click Refresh to refresh a list and view the most recent data. 5

15 Preparations To use VCM, first configure VRM and the edge switches to be managed by VCM. Configuring VRM VRM is a subcomponent of the IMC Platform used to manage virtual resources. For more information about VRM, see HPE Intelligent Management Center v7.3 Enterprise and Standard Platform Administrator Guide. In the VEB solution, the VRM configuration is required because VCM relies on VRM to obtain the VM status and access location information. In the EVB solution, the VRM configuration is required only when you want to view the VM migration history and connection information in VCM. VRM supports the following types of virtualization software products: VMware Hyper-V KVM Xen CAS Different virtualization software requires different plug-ins and configuration parameters, which are discussed in later sections. Installing plug-ins Depending on the virtualization software to be managed, the following plug-ins might be required: VRM plug-in Used by VRM to obtain vswitch, VM, and port group information from physical servers and vmanager. LLDP plug-in Used by VRM to compute virtual network topologies, including the storage structure and topologies within physical servers. For information about how to install the VRM and LLDP plug-ins, see HPE IMC deployment guides. Table 1 Plug-ins required by different virtualization software Virtualization software VMware Hyper-V KVM VRM plug-in Not required. vrm-plug-windows required. vrm-plug-linux required. LLDP plug-in Not required, but CDP must be supported and enabled on the access switch. lldp-agent-windows required. lldp-agent-redhat or lldp-agent-ubuntu required, depending on the operating system on which KVM runs. Xen vrm-plug-linux required. lldp-agent-redhat required. CAS Not required. Not required. 6

16 Configuring VRM parameters Table 2 VRM configuration parameters for different virtualization software products Virtualization software Server type Configuration parameter VMware N/A SOAP Hyper-V Hyper-V SCVMM WMI PowerShell KVM N/A SSH Key Xen N/A XML-RPC CAS N/A SOAP For information about how to configure these parameters, see HPE Intelligent Management Center v7.3 Enterprise and Standard Platform Administrator Guide. Configuring the edge switch In the EVB solution, configure EVB, LLDP, and the default VSI Manager on the EVB-capable edge switches. Configuring EVB Enable EVB on the switch port that connects to the physical server. If multiple switch ports are connected to the server, first aggregate the ports and then enable EVB on the aggregate interface. # Enable EVB on aggregate interface 11. [evb-acs55]interface Bridge-Aggregation 11 [evb-acs55-bridge-aggregation 11]evb enable Configuring LLDP Configure LLDP on the switch port that connects to the physical server. If multiple switch ports are connected to the server, first aggregate the ports and then configure LLDP on the aggregate interface. # Configure LLDP on aggregate interface 11. [evb-acs55]interface Bridge-Aggregation 11 [evb-acs55-bridge-aggregation 11]link-type trunk [evb-acs55-bridge-aggregation 11]lldp agent nearest-nontpmr admin-status txrx [evb-acs55-bridge-aggregation 11]lldp tlv-enable dot1-tlv protocol-vlan-id [evb-acs55-bridge-aggregation 11]lldp tlv-enable dot1-tlv vlan-name Specifying the default VSI Type Manager # Specify the IMC server as the default VSI Manager. In this example, is the IP address of the IMC primary server, and 8080 is the HTTP port number set on IMC. [evb-acs55]evb default-manager ip port

17 Customizing VCM widgets VCM provides a widget named VAN View TopN, which can be added to a space tab of the IMC home page. The IMC home page can include multiple spaces to show information organized for specific purposes or topics. A space can display up to 10 widgets. The VAN View TopN widget displays the ACL utilization of edge switches and connection utilization of networks managed by VCM. Adding VAN View TopN to a space 1. Click the Home tab. The default space named Welcome is displayed. 2. Click the Settings icon. 3. Click the tab to which you want to add the VAN View TopN widget. 4. Click Edit in the shortcut menu.. The dialog box for adding widgets to the space opens. 5. Click the Resource tab. 6. Click the Add icon for the VAN View TopN widget to add it to the space. 7. Click OK. 8. Click Save in the shortcut menu. 9. Click the Settings icon. The space tabs and function links are hidden from the home page. Viewing the VAN View TopN widget 1. Click the Home tab. The default space named Welcome is displayed. 2. Click the Settings icon. 3. Click the space where the VAN View TopN widget is located. The VAN View TopN widget is displayed. As shown in Figure 4, the widget includes two charts. The bar chart displays the connection utilization of networks in VCM. The y-axis shows the number of connections, and the x-axis shows the network names. The pie chart at the top left displays the ACL utilization of edge switches managed by VCM. 8

18 Figure 4 VAN View TopN widget Connection utilization The connection utilization bar chart displays the numbers of the following types of connections for each network: Undeployed Connections Deployed Connections Remaining Connections You can perform the following operations on the chart: Place the cursor over a colored area to view the VLAN ID and percentage of the connection type to the total configurable connections of the network. Place the cursor over a VSI node on the chart to view the number of VSI types and the VLAN ID of the network. Click a legend icon in the Connection Utilization area to hide or show data of that type. ACL utilization The pie chart displays the ACL utilization of all managed edge switches in VCM. Each edge switch is represented by a colored slice with a size proportional to the total number of ACLs the switch can assign to VCM. Place the cursor over a slice to view the device label and ACL utilization of the edge switch. The ACL utilization data includes the total assignable ACLs, number of used ACLs, and ACL usage percentage. The total number of ACLs that an edge switch can assign to VCM is determined by the ACL Number Range configured for the switch. Configuring the VAN View TopN widget You can configure the number of networks the VAN View TopN widget displays and the refresh interval of the widget. To configure the VAN View TopN widget: 1. Click the Home tab. The default space named Welcome is displayed. 2. Click the Settings icon on the top right corner of the space. 9

19 3. Select Edit from the shortcut menu to open the dialog box for adding widgets. 4. Click of the VAN View TopN widget to add it to the space. Then changes to Succeeded when the widget is added successfully. 5. Click the space where the VAN View TopN widget is located. 6. Specify the number of networks the widget displays: a. Place the cursor over the icon on the top right corner of the widget. b. Click the Set icon and select Setting from the shortcut menu. The Setting dialog box opens. c. Select a value from the Top list. The available options are 5, 10, 20, and 30. By default, the VAN View TopN widget displays the top 5 networks with the most connections. d. Click OK to return to the space where the VAN View TopN widget is located. e. Click Save. 7. Set the refresh interval: a. Click the Set icon on the top right corner of the widget and select Refresh Interval from the shortcut menu. The Refresh Interval Setting dialog box opens. b. Select a refresh interval from the list. The available options are No Refresh, 1, 5, 10, and 30. The default refresh interval is 10 minutes. The No Refresh option disables automatic refreshing for the widget. c. Click OK to return to the space where the VAN View TopN widget is located. d. Click Save. 8. Click the Settings icon. The space tabs and shortcut menu are hidden from the home page. Manually refreshing the VAN View TopN widget 1. Click the Home tab. The default space named Welcome is displayed. 2. Click the space where the VAN View TopN widget is located. 3. Place the cursor over the icon on the top right corner of the widget. 4. Click the Refresh icon on the top right corner of the widget. Deleting the VAN View TopN widget 1. Click the Home tab. The default space named Welcome is displayed. 2. Click the space where the VAN View TopN widget is located. 3. Place the cursor over the icon on the top right corner of the widget. 4. Click the Delete icon on the top right corner of the widget. A confirmation dialog box opens. 5. Click OK. The following message is displayed: Customized settings has been changed, do you want to save it now? 10

20 6. Click Save. 11

21 Managing plug-ins VCM Plug-in management allows operators to register and manage connection management plug-ins. Registered plug-ins enable vmanager administrators to manage VCM connections on virtualization platforms such as vcenter Server, XenCenter, and Virtual Machine Manager (VMM). Table 3 describes registration and functions of the plug-ins. Table 3 Plug-in description Name Registered to Functions vcenter plug-in vcenter Server Enables the administrator to manage VCM connections on vcenter Server. VCE plug-in XenCenter plug-in VMM plug-in vcenter Server XenCenter VMM Enables the administrator to configure the VSI for a port group by retrieving network information and VSI Types from VCM. Enables the administrator to manage VCM connections on XenCenter. Enables the administrator to manage VCM connections on VMM. Managing the vcenter plug-in Registering the vcenter plug-in 2. From the navigation tree, select VAN Connection Manager > Plug-in Management. The Plug-in Management page opens. 3. In the vcenter Plug-in area, click the Register icon. The vcenter Plug-in Management page opens. 4. Configure the following parameters: vcenter Server IP Address Enter the IPv4 address of vcenter Server. This field does not support IPv6 addresses. vcenter Server Username Enter the username of the administrator. vcenter Server Password Enter the password of the administrator. Enter the address of the administrator. 5. Click Register to register the plug-in to vcenter Server. After the vcenter plug-in is successfully registered, verify that a tab named Network (imc) is added to VMware vsphere Client for each VM, as shown in Figure 5. 12

22 Figure 5 Network (imc) tab Managing connections on vcenter Server After the vcenter plug-in is registered, the administrator can manage VCM connections on vcenter Server. The connection data is synchronized between VCM and vcenter Server. Accessing the Connection List page 1. Log in to vcenter Server from VMware vsphere Client. 2. From the navigation tree, select a VM and click the Network (imc) tab. The Login dialog box opens, as shown in Figure 6. Figure 6 Login dialog box 3. Enter the username and password of an IMC operator, and then click Login. The operator must have privileges to manage connections and VSI Types. The Connection List page opens and displays all connections for the vnics on the VM. Figure 7 Adding a connection Adding a connection 1. In the Connection List, click Add. 2. Configure the following parameters: Name Enter the name of the connection, a string of 1 to 128 characters. 13

23 VM MAC Select the MAC address of a vnic on the VM. If the VM has multiple vnics, the list displays the MAC addresses of all the vnics. VM IP Enter the IP address of a vnic on the VM. This field is automatically populated with the IP address obtained by VCM. If the IP address of the vnic on the VM is automatically assigned but the VM is not started, this field is empty. As a best practice, keep this field empty in this case. VCM will automatically obtain the IP address of the vnic after the VM is started. VLAN This field cannot be configured. It displays the VLAN assigned to the port group that includes the vnic. The VLAN ID determines the VLAN traffic allowed to pass by the port group: If the VLAN ID is in the range of 1 to 4094, the port group allows packets with the specified VLAN ID to pass. If the VLAN ID is 0, the port group has no VLAN configured. If the VLAN ID is 4095, the port group allows all VLAN packets to pass. Network Select a network for the vnic. The list displays networks that are assigned to the VLAN of the vnic. For example, if the vnic is in VLAN 100, the list displays networks in VLAN 100; if the vnic is in VLAN 0 or 4095, the list displays all networks created in VCM. VSI Type Select a VSI Type. If a network is selected, the list displays VSI Types in the network. Otherwise, the list displays all VSI Types. VSI Type Version Select a version of the VSI Type. Description Enter the descriptive information, a string of 0 to 128 characters. 3. Click OK. The new connection is added to the Connection List. Modifying a connection 1. In the Connection List, click the Modify icon for a connection. 2. Modify parameters of the connection except its name and vnic information. For information about other parameters, see "Adding a connection." 3. Click OK. Deploying a connection Before deploying a connection, verify that the Access Switch and Access Interface columns are not empty in the Connection List. Do not deploy the connection when one or both columns are empty. To deploy a connection: In the Connection List, click the Deploy icon for a connection. VCM deploys the network configuration to the access switch the VM connects. The Deploy icon changes to the Undeploy icon. In VCM, the operator can view this deployment in the migration records. If the deployment turns out to be partially successful or a failure, the operator can obtain reasons from the operation records. Undeploying a connection In the Connection List, click the Undeploy icon for a connection. VCM deletes the network configuration from the access switch the VM connects. The Undeploy icon changes to the Deploy icon. In VCM, the operator can view this undeployment in the migration records. If the undeployment turns out to be partially successful or a failure, the operator can obtain reasons from the operation records. 14

24 Deleting a connection You can delete undeployed connections only. To delete an undeployed connection: 1. In the Connection List, click the Delete icon for a connection. A confirmation dialog box opens. 2. Click OK. The connection is removed from the Connection List. Modifying the vcenter plug-in Modify parameters for the registered vcenter plug-in in VCM if the administrator username, password, or the IP address of vcenter Server changes. To modify the vcenter plug-in: 2. From the navigation tree, select VAN Connection Manager > Plug-in Management. The Plug-in Management page opens. 3. Click the registered vcenter plug-in. The page for modifying the vcenter plug-in opens. 4. Modify the plug-in parameters. For more information, see "Registering the vcenter plug-in." The page also displays the following parameters: Register Time Time when the vcenter plug-in was first registered. Resister Operator Name of the IMC operator who first registered the vcenter plug-in. 5. Click Modify. If the IP address of vcenter Server is changed, VCM registers the vcenter plug-in to the new vcenter Server. If the IP address of vcenter Server is not changed, VCM uses the new parameters to access vcenter Server. If VCM can access vcenter Server, the modification is successful. Otherwise, the system displays the failure. Changing the administrator does not affect the parameters for the registered vcenter plug-in. Uninstalling the vcenter plug-in Uninstalling the vcenter plug-in does not affect the created connections on vcenter Server. To uninstall the vcenter plug-in: 2. From the navigation tree, select VAN Connection Manager > Plug-in Management. The Plug-in Management page opens. 3. Click the registered vcenter plug-in. The page for modifying the vcenter plug-in opens. 4. Verify all parameters are correct, and then click Uninstall. After the vcenter plug-in is removed, the Network (imc) tab is also removed from VMware vsphere Client. 15

25 Managing the VCE plug-in The Virtual Control Engine (VCE) plug-in is developed based on the RESTful API provided by HP FlexFabric Virtual Switch 5900v (HP 5900v). After the VCE plug-in is registered to vcenter Server, HP 5900v can obtain network information and VSI Types from VCM to support port group configuration. If an error exists in IMC configuration or vcenter Server configuration on the webpage of HP 5900v or during the VCE installation, modify the parameters during VCE plug-in registration. NOTE: HP FlexFabric Virtual Switch 5900v supports EVB and runs on top of the VMware vsphere Enterprise Plus Edition to provide virtual switching in virtualization environments. For more information, see HP FlexFabric Virtual Switch 5900v Installation Guide. Registering the VCE plug-in 2. From the navigation tree, select VAN Connection Manager > Plug-in Management. The Plug-in Management page opens. 3. In the VCE Plug-in area, click the Register icon. The VCE Plug-in page opens. 4. Configure the following parameters: VCE IP Address Enter the IP address of the VCE server. VCE Port Number Enter the HTTP port for VCE communication, which must be VCE Username Enter the username of the VCE server administrator. VCE Password Enter the password of the VCE server administrator. vcenter Server IP Address Enter the IP address of vcenter Server. vcenter Server Username Enter the username of the vcenter Server administrator. vcenter Server Password Enter the password of the vcenter Server administrator. vcenter Server HTTP Port Enter the HTTP port for vcenter Server communication. The default value is 80. vcenter Server HTTPS Port Enter the HTTPS port for vcenter Server communication. The default value is Click Register. VCM displays the registration result. Configuring the VSI for a port group 1. Log in to vcenter Server from VMware vsphere Client. 2. Select Homepage > Inventory > Networking and expand the data center. 3. Select the EVB-capable vswitch that is generated by HP 5900v. 4. Click the HP Port Group 5900v tab. In the Port Groups list, the VDP column of a port group displays VSI Type versions to which the port group is assigned. If the port group is not assigned to any network, the VDP column displays None, as shown in Figure 8. 16

26 Figure 8 Viewing VDP in the port group list 5. In the VDP column, click None or a VSI Type version. 6. On the Configure VSI page (see Figure 9), configure the following parameters: Network Select a network for the port group. The list displays networks that are assigned to the VLAN of the port group. For example, if the port group is in VLAN 100, the list displays networks in VLAN 100; if the port group is in VLAN 0 or 4095, the list displays all networks created in VCM. VSI Type Select a VSI Type. If a network is selected, the list displays VSI Types in the network. Otherwise, the list displays all VSI Types. VSI Type Version Select a version of the VSI Type. Figure 9 Configuring the VSI for a port group 17

27 7. Click OK. Modifying a VCE plug-in When parameters for the VCE server and vcenter Server are changed, modify the parameters of the VCE plug-in. To modify the VCE plug-in: 2. From the navigation tree, select VAN Connection Manager > Plug-in Management. The Plug-in Management page opens. 3. Click the registered VCE plug-in. The VCE Plug-in page opens. 4. Modify parameters for the VCE plug-in. For information about the VCE plug-in parameters, see "Registering the VCE plug-in." 5. Click Modify. If the IP address of the VCE server or vcenter Server is changed, VCM registers the VCE plug-in to the new vcenter Server. If the IP address of the VCE server or vcenter Server is not changed, VCM uses the new parameters to access vcenter Server. If VCM can access vcenter Server, the modification is successful. Otherwise, the system displays the failure. Uninstalling the VCE plug-in 2. From the navigation tree, select VAN Connection Manager > Plug-in Management. The Plug-in Management page opens. 3. Click the registered VCE plug-in. The page for modifying the VCE plug-in opens. 4. Verify all parameters are correct, and then click Uninstall. Managing the XenCenter plug-in Registering the XenCenter plug-in 2. From the navigation tree, select VAN Connection Manager > Plug-in Management. 3. In the XenCenter Plug-in area, select English from the list. 4. Click Download to download the imcxenplugin.xcplugin.xml file to the local machine. 5. On the XenCenter server, create the \XenCenter\Plugins\H3C\iMCXenPlugin directory of the Citrix installation path, and then copy the.xml file to the directory. After the XenCenter plug-in is successfully registered, log in to XenCenter again to verify that a tab named Network Connections is added for each VM. Access the connection list for a VM to manage the connection, as shown in Figure

28 Figure 10 Managing connections Managing connections on the XenCenter server On the XenCenter server, the administrator can add, modify, delete, deploy, and undeploy connections. The connection information is synchronized between VCM and the XenCenter server. Managing connections on the XenCenter server has the same operations as on vcenter Server. For information about managing connections on vcenter Server, see "Managing connections on vcenter Server." Deleting the XenCenter plug-in To delete the XenCenter plug-in from the XenCenter server, clear the directory \XenCenter\Plugins\H3C\iMCXenPlugin of the Citrix installation path. After all files are deleted from the directory, relog in to XenCenter to verify that the Network Connections tab for VMs is also removed. Managing the VMM plug-in Registering a VMM plug-in 2. From the navigation tree, select VAN Connection Manager > Plug-in Management. The Plug-in Management page opens. 3. In the VMM Plug-in area, select English from the list. 4. Click Download to download the imcvmmplugin.zip file to the local machine. 5. On the VMM server, copy the.zip file to a directory on the server. 6. Log in to VMM, select Settings from the navigation tree, and click Import Console Add-in on the Home tab, as shown in Figure

29 Figure 11 Accessing VMM The Import Console Add-in Wizard window opens, as shown in Figure 12. Figure 12 Import Console Add-in Wizard window 7. Click Browse, select the.zip installation file of the VMM plug-in, and select the Continue installing this add-in anyway option, as shown in Figure

30 Figure 13 Selecting the installation file 8. Click Next to confirm the VMM plug-in information. 9. Click Finish to start the installation. When the installation is complete, the Jobs window displays the installation result, as shown in Figure 14. Figure 14 Viewing the installation result After the installation, select Settings > Console Add-ins from the navigation tree to verify that the VMM plug-in named Network Connections is added to the list, as shown in Figure

31 Figure 15 Viewing the registered VMM plug-in Managing connections on VMM On VMM, the administrator can add, modify, delete, deploy, and undeploy connections. The connection information is synchronized between VCM and VMM. Accessing the Connection List page 1. Log in to VMM. 2. From the navigation tree, select VMs and Services, click the Home tab, and click Network Connections, as shown in Figure 16. Figure 16 Accessing the Network Connections page 3. Select a Hyper-V host. All VMs on the Hyper-V host are displayed. 22

32 4. Select a VM. 5. The Login dialog box opens, as shown in Figure 17. Figure 17 Login dialog box 6. Enter the username and password of an IMC operator, and then click Login. The operator must have privileges to manage connections and VSI Types. On the Network Connection tab (see Figure 18), the connection list displays connections for the selected VM. NOTE: The connection list displays all connections for the vnics on the VM. Figure 18 Viewing connections for the VM Adding a connection 1. In the Connection List, click Add. 2. Configure the following parameters: 23

33 Name Enter the name of the connection, a string of 1 to 128 characters. VM MAC Select the MAC address of a vnic on the VM. If the VM has multiple vnics, the list displays the MAC addresses of all the vnics. VM IP Enter the IP address of a vnic on the VM. This field is automatically populated with the IP address obtained by VCM. If the IP address of the vnic on the VM is automatically assigned but the VM is not started, this field is empty. As a best practice, keep this field empty in this case. VCM will automatically obtain the IP address of the vnic after the VM is started. VLAN This field cannot be configured. It displays the VLAN assigned to the port group that includes the vnic. The VLAN ID determines the VLAN traffic allowed to pass by the port group: If the VLAN ID is in the range of 1 to 4094, the port group allows packets with the specified VLAN ID to pass. If the VLAN ID is 0, the port group has no VLAN configured. If the VLAN ID is 4095, the port group allows all VLAN packets to pass. Network Select a network for the vnic. The list displays networks that are assigned to the VLAN of the vnic. For example, if the vnic is in VLAN 100, the list displays networks in VLAN 100; if the vnic is in VLAN 0 or 4095, the list displays all networks created in VCM. VSI Type Select a VSI Type. If a network is selected, the list displays VSI Types in the network. Otherwise, the list displays all VSI Types. VSI Type Version Select a version of the VSI Type. Description Enter the descriptive information, a string of 0 to 128 characters. Figure 19 Adding a connection 3. Click OK. The new connection is added to the connection list. Modifying a connection You can modify undeployed connections only. To modify an undeployed connection: 1. In the Connection List, click the Modify icon for a connection. 24

34 Modify parameters of the connection except its name and vnic information. For information about other parameters, see "Adding a connection." 2. Click OK. Deploying a connection Before deploying a connection, check whether the Access Switch and Access Interface columns are blank in the Connection List. Do not deploy the connection when one or both columns are empty. To deploy a connection: In the Connection List, click the Deploy icon for a connection. VCM deploys the network configuration to the access switch the VM connects. The Deploy icon changes to the Undeploy icon. In VCM, the operator can view this deployment in the migration records. If the deployment turns out to be partially successful or a failure, the operator can obtain reasons from the operation records. Undeploying a connection In the Connection List, click the Undeploy icon for a connection. VCM deletes the network configuration from the access switch the VM connects. The Undeploy icon changes to the Deploy icon. In VCM, the operator can view this undeployment in the migration records. If the undeployment turns out to be partially successful or a failure, the operator can obtain reasons from the operation records. Deleting a connection You can delete undeployed connections only. To delete an undeployed connection: 1. In the Connection List, click the Delete icon for a connection. A conformation dialog box opens. 2. Click OK. The connection is removed from the Connection List. Deleting the VMM plug-in 1. Log in to VMM. 2. From the navigation tree, select Settings. All plug-ins registered on VMM are displayed in the list, as shown in Figure

35 Figure 20 Viewing registered plug-ins 3. Select the Network Connections plug-in, and click Remove. 4. In the confirmation dialog box that opens, click OK. 26

36 Managing edge switches An edge switch in VCM is directly connected to a physical server. VCM provides an Edge Switch module to centrally manage edge switches and their VCM parameter settings. Viewing the edge switch list 2. From the navigation tree, select VAN Connection Manager > Edge Switch. All edge switches are displayed in the edge switch list. The list includes the following parameters: Status Status of the edge switch, includes the alarm status or management status. If the edge switch is in the Unknown state, the SNMP configuration on it might be incorrect. Device Label Device label of the edge switch. Click the label to view its detailed information. Connection Statistics Displays numbers of deployed connections, connections failed to be deployed, undeployed connections, and service units. Place the cursor over a connection number to view the VM information such as Primary vnic, VM, and Physical Server. Place the cursor over the number of service units to view the service unit information. All edge switches support 4 service units. ACL Number Range Range of ACL numbers assigned to VCM on the edge switch. The number range varies with device vendors. Max. Connections Maximum number of connections supported by the edge switch. When the deployed connections reach the maximum number, additional connections cannot be deployed. Operation Click the Operation icon to view the operation options, including ACL Number Range, Max. Connections, Default Manager, Migration History, and Delete. The Default Manager option is displayed only for EVB-supported edge devices. 3. Click Refresh to view the latest list. 4. Select 8, 15, 50, 100, or 200 at the bottom of the edge switch list to configure how many items per page you want to display. 5. If the edge switch list contains enough entries, use the following aids to navigate the list: Click the Next Page icon to page forward in the edge switch list. Click the Last Page icon to page forward to the end of the edge switch list. Click the Previous Page icon to page backward in the edge switch list. Click the First Page icon to page backward to the front of the edge switch list. NOTE: You can sort the edge switch list by the Status and Device Label fields. The column label allows you to toggle between the various sort options specific to each field. Click the column label to sort the list by the selected field. Querying edge switches 27

37 2. From the navigation tree, select VAN Connection Manager > Edge Switch. All edge switches are displayed in the edge switch list. 3. In the query field to the right of the list, enter a device label. This field supports fuzzy matching. 4. Click the Query icon. All matching edge switches are displayed in the list. 5. To display all edge switches, clear the query field and click the Query icon. Adding edge switches VCM can automatically add edge switches and also allows operators to manually add edge switches. Automatic method When a connection is established between a VSI Type and a VM, VCM performs the following tasks: 1. Obtains the IP address of the switch to which the VM is connected. 2. Checks whether the IP address of the switch exists in the IMC Platform. 3. Adds the switch as an edge switch if the IP address is found. This process does not require manual intervention. All edge switches automatically added use the default settings of the ACL number range and maximum connections. The default ACL number range varies with the device vendors and models. Manual method To add edge switches manually: 2. From the navigation tree, select VAN Connection Manager > Edge Switch. All edge switches are displayed in the edge switch list. 3. Click Add. 4. Filter and select edge switches in the By View tab or the Advanced tab. To use the By View tab: a. Click the Expand icon to expand a view. b. Select a subview. All switches in the subview are displayed in the Devices Found area. NOTE: The Device Found list automatically rules out devices that are not switches. For example, if you select Routers under the Device View, the Device Found area is empty. c. Add devices to the Selected Devices area: To add all devices, click the Add All icon. To add one or more devices, select them in the Device Found area and click the Add icon. d. Remove undesired devices from the Device Found area: To remove all devices, click the Remove All icon. 28

38 e. Click OK. To remove one or more devices, select devices in the Selected Devices area and click the Remove icon. To use the Advanced tab: f. Specify one or more of the following query criteria: Device IP Enter the IP address of the device. This field supports fuzzy matching. You can click the Exact Query option to perform an exact query. Device IP List Click the Configuration icon next to the Device IP List field to perform an exact query for multiple devices. Make sure the Exact Query option is selected. In the Device IP List Configuration window, enter multiple IP addresses separated by commas, semicolons, or carriage returns, click Add, and then click OK. The Device IP List is automatically populated with these IP addresses. If you want to clear the Device IP List, click the Clear icon. Device Label Enter a device label. This field supports fuzzy matching. Device Status Select a device state. Device Category Select a device category. Device Series Select a device series. Contact Enter the contact information. This field supports fuzzy matching. Location Enter the name of location view. This field supports fuzzy matching. Device Reachability Select Reachable or Unreachable from the list. g. Click Query. All matching devices are displayed in the Devices Found area. h. Add devices to the Selected Devices area: To add all devices, click the Add All icon. To add one or more devices, select them in the Device Found area and click the Add icon. i. Remove undesired devices from the Device Found area. To remove all devices, click the Remove All icon. To remove one or more devices, select devices in the Selected Devices area and click the Remove icon. j. Click OK. Configuring the ACL number range for an edge switch VCM uses the ACL number range to restrict the ACL numbers available in VCM. When all ACL numbers in the assigned range are used up, additional ACL configurations cannot be deployed to the edge switch from VCM. The ACL number range varies with device vendors. The ACL number range for HP device is 100 to 199. The ACL number range for Cisco devices is 2000 to The ACL number range for H3C devices is 3000 to For more information, see the device configuration guides. 29

39 The ACL number range does not affect the ACL configuration performed on the device. To specify the ACL number range: 2. From the navigation tree, select VAN Connection Manager > Edge Switch. All edge switches are displayed in the edge switch list. 3. Click the Operation icon for an edge switch and then select ACL Number Range from the shortcut menu. 4. Enter the start ACL number and end ACL number. The end ACL number must be greater than or equal to the start ACL number. 5. Click OK. Specifying the maximum connections for an edge switch 2. From the navigation tree, select VAN Connection Manager > Edge Switch. All edge switches are displayed in the edge switch list. 3. Click the Operation icon for an edge switch and then select Max. Connections from the shortcut menu. 4. In the Max. Connections field, enter an integer in the range of 1 to The default is Click OK. Configuring the Default Manager for an edge switch The Default Manger can be configured on EVB-supported edge switches only, and only one Default Manger can be configured on each EVB-supported edge switch. If the edge switch cannot obtain the IP address of the VSI Manager from the physical server, it will communicate with the configured Default Manager. To configure the Default Manager for an EVB-supported edge switch: 2. From the navigation tree, select VAN Connection Manager > Edge Switch. All edge switches are displayed in the edge switch list. 3. Click the Operation icon for an edge switch and then select Default Manager from the shortcut menu. 4. Configure the following parameters: IP Address Enter the IP address of the VSI Manager, which is also the IP address of the VCM server. Port Number Enter the HTTP port number to communicate with the VSI Manager. Through this port, the edge switch requests the VSI Manager to deploy VSI Types. The port number must be the same as the port configured on the VSI Manager. When VCM is the VSI Manager, the HTTP port number is configured during IMC deployment. NOTE: By default, the previous fields are empty. If the Default Manager is already configured for the edge switch, the fields display the configured values. 30

40 5. Click OK. 6. Click Delete to delete the configured Default Manager. Viewing the VM migration history of an edge switch 2. From the navigation tree, select VAN Connection Manager > Edge Switch. All edge switches are displayed in the edge switch list. 3. Click the Operation icon for an edge switch and then select Migration History from the shortcut menu. The Migration History list displays records of VM migration related to the edge switch. The edge switch can be a source switch or a destination switch. For more information about migration history, see "Managing life cycle reports." Deleting edge switches You can delete an edge switch with 0 connections. Deleting an edge switch from VCM does not delete it from the IMC Platform. To delete one or more edge switches: 2. From the navigation tree, select VAN Connection Manager > Edge Switch. All edge switches are displayed in the edge switch list. 3. To delete a single edge switch, click the Operation icon for the edge switch and then select Delete from the shortcut menu. 4. To delete edge switches in batches, select them on the list and click Delete. A confirmation dialog box opens. 5. Click OK. 31

41 Managing networks Overview VCM provides a network module to manage logical networks rather than physical networks. A logical network includes the following resources: VLAN VLANs are used to isolate networks, each VLAN representing a network. When a network is selected to create a connection, the VM in the connection will be assigned to the VLAN of the network. The VLAN information will be delivered to the edge switch to permit the VLAN traffic through the interface that is connected to the VM. In an EVB network, VLANs can be used to identify VSI traffic for filtering. Max. Connections Maximum number of connections supported by a single network. The value can be determined based on the number of VMs and number of NICs on each VM. For example, if 100 VMs reside in a network, it might be insufficient to set the maximum number of connections to 100. This is because a VM can have multiple NICs with each NIC corresponding to one connection, and the total connections might exceed the total number of VMs. VSI Type The VSI Type configured for a network assigns network configuration to VMs. Network management privileges The network management privileges of an operator determine the following information: Network operations that can be performed by the operator. Scope of networks the operator can manage. Predefined network management privileges An operator group uses one of the following privileges: ADMIN, Maintainer, and Viewer. Network operations supported in VCM vary by the privilege, as shown Table 4. Operators gain privileges to perform network operations based on operator groups. Table 4 Support for network operations by different privileges Network operations ADMIN Maintainer Viewer Accessing the network management page Supported Not supported Not supported Adding, modifying, and deleting networks Supported Not supported Not supported Adding, modifying, and deleting connections for a network Supported Supported Not supported Deploying vapps on a network Supported Supported Not supported Viewing connections on a network Supported Supported Supported Modular VCM privileges An operator group can be granted all or part of the privileges to manage functional modules of VCM, as shown in Figure

42 Figure 21 Modular VCM privileges Network operations are determined by privileges VAN Connection Manager - Connection and VAN Connection Manager - Network, as shown in Table 5. For information about configuring privileges for an operator group, see HPE Intelligent Management Center v7.3 Enterprise and Standard Platform Administrator Guide. Table 5 Network operations and privileges Privilege Network operations Remarks VAN Connection Manager - Network VAN Connection Manager - Connection Accessing the network management page Adding, modifying, and deleting networks Adding, modifying, and deleting connections for a network Deploying vapps on a network Viewing connections on a network The Network option is available only when the operator group has the ADMIN privilege. N/A Assigning network management privileges To assign network management privileges to other operators, use an operator that has both the ADMIN privilege and the VAN Connection Manager - Network privilege. Assigning network management privileges to a new operator 1. Access the Add Operator page. (Details not shown.) 2. In the Basic Information area, configure parameters of the operator. (Details not shown.) When you select an operator group, follow these restrictions and guidelines: When the operator group has the Maintainer or Viewer privilege, it must also be granted the VAN Connection Manager - Connection privilege. When the operator group has the ADMIN privilege, it must also be granted the VAN Connection Manager - Network privilege. The VAN Connection Manager - Connection privilege is optional. 3. In the Visible VCM Networks area (see Figure 22), configure the scope of networks to be managed: Visit all networks Allows the operator to manage all networks. 33

43 Specify visible networks Allows the operator to manage specified networks. Figure 22 Assigning network management privileges to a new operator 4. Configure other parameters as needed. 5. Click OK. 34

44 Assigning network management privileges to operators for a new network 1. Access the Add Network page. (Details not shown.) 2. In the Basic Information area, configure parameters of the network. (Details not shown.) 3. In the Operator List area (see Figure 23), select operators to manage the network. Operators that have access to all networks (with Visit all networks selected) are grayed out and automatically selected. Figure 23 Assigning network management privileges to a new network 4. Configure other parameters as needed. For more information, see "Adding a network." 5. Click OK. 35

45 Network module application scenarios Use the network module in the following scenarios: When a data center contains multiple VLANs, configure networks based on the VLANs. When a data center is managed by multiple operators with different privileges, divide the data center into multiple networks and assign operators to each network. When network resources in a data center are to be assigned to tenants, configure networks for the tenants with the required network resources and operators. Viewing the network list 2. From the navigation tree, select VAN Connection Manager > Network. All networks are displayed in the network list. The list includes the following parameters: Network Name Name of the network. Click the name to view its detailed information. VLAN ID VLAN where the network resides. Max. Connections Maximum number of connections supported by the network. When the existing connections reach the maximum number, additional connections cannot be added to the network. Description Descriptive information of the network. Bandwidth Control Displays a bar to represent the number of connections with bandwidth control and the total bandwidth rate. Place the cursor over the bar to view the detailed information. If bandwidth control is not configured for connections, this column is empty. Connection Displays connection information by a colored bar. Connection types are represented by different colors: green for deployed connections, red for undeployed connections, and gray for remaining connections that can be deployed. Place the cursor over a colored area to view the number of the corresponding connections. Copy Click the Copy icon to copy the same network configuration as the current network and create a new network. Modify Click the Modify icon to modify the network. Delete Click the Delete icon to delete the network. 3. Click Refresh to view the latest networks. Querying networks Basic query VCM supports both basic and advanced queries. 2. From the navigation tree, select VAN Connection Manager > Network. All networks are displayed in the network list. 3. In the query field to the right of the list, enter a network name. This field supports fuzzy matching. 4. Click Query. The network list displays all networks that match the criterion. 36

46 Advanced query 5. To clear the query criterion, click Reset. The network list displays all networks in VCM. 2. From the navigation tree, select VAN Connection Manager > Network. All networks are displayed in the network list. 3. Click the Advanced icon on the upper right side of the network list area. 4. Enter one or more of the following query criteria: Name Enter a network name. This field supports fuzzy matching. VLAN ID Enter a VLAN ID in the range of 1 to Max. Connections Enter a maximum number of connections. 5. Click Query. The network list displays all networks that match the criteria. 6. To clear the query criteria, click Reset. 7. To hide the advanced query area, click Close. Viewing network details 2. From the navigation tree, select VAN Connection Manager > Network. All networks are displayed in the network list. 3. Click the name of the network whose detailed information you want to view. The Network Details page displays the following areas and parameters: Basic Information area Name Name of the network. VLAN ID VLAN where the network resides. Max. Connections Maximum number of connections supported by the network. When the existing connections reach the maximum number, additional connections cannot be added to the network. Description Descriptive information of the network. VSI Type area Name Name of the VSI Type. Description Descriptive information of the VSI Type. Operator List Click the Expand icon to expand an operator group whose operators have management privileges to the network. Click the Expand All icon to expand all operator groups. Click the Collapse All icon to collapse all operator groups. 4. Click Back to return to the network list page. Adding a network 2. From the navigation tree, select VAN Connection Manager > Network. All networks are displayed in the network list. 3. Click Add. 37

47 4. Configure the following basic information: Name Enter a network name with no more than 32 characters. VLAN ID Enter a VLAN ID in the range of 1 to The VLAN ID will be delivered to the switch interface which connects to VM. NOTE: Make sure the VM is connected to a Layer 2 Ethernet interface or Ethernet aggregate interface of the trunk type. Otherwise, VLAN delivery will fail. Max. Connections Enter the maximum number of connections. Description Enter a string of descriptive information with no more than 128 characters. 5. Add one or more VSI Types to the network: a. Select one or multiple VSI Types in the left VSI Type list. b. Click the Add icon to add the selected VSI Types to the right field. c. To add all VSI Types, click the Add All icon. d. To remove one or more VSI Types, select VSI Types in the right field, and click the Remove icon. e. To remove all VSI Types, select all VSI Types in the right field, and click the Remove All icon. 6. Assign management privileges to the network: By default, administrators have the management privilege for all networks and their privilege cannot be modified. If the Visit All Networks option is selected for a created operator, the operator also has the management privilege for all networks and the privilege cannot be modified. The management privilege of maintainers and viewers can be configured. a. Click the Expand icon to expand an operator group. b. Select operators. 7. Click OK. Network configuration example In a data center, a network is assigned to Tenant A and configured with the following recourses: VLAN ID of 150 Maximum connections of 200 VSI Type A Maintainer a To add the network: 2. From the navigation tree, select VAN Connection Manager > Network. All networks are displayed in the network list. 3. Configure the following network parameters, as shown in Figure 24. a. Enter Network A in the Name field. b. Enter 150 in the VLAN ID field. c. Enter Assign this network to Company A in the Description field. d. Click the Add icon to add VSI Type A to the right field. 38

48 e. Select maintainer llf in the maintainer group. Figure 24 Configuring network parameters 4. Click OK. Copying a network 2. From the navigation tree, select VAN Connection Manager > Network. All networks are displayed in the network list. 39

49 3. Click the Copy icon for the network whose configuration is to be copied. The Add Network page opens. The parameter fields are automatically populated with the configuration of the copied network. 4. Modify the network parameters as needed. For more information, see "Adding a network." Modifying a network 2. From the navigation tree, select VAN Connection Manager > Network. All networks are displayed in the network list. 3. Click the Modify icon for the network to be modified. The Modify Network page opens. 4. Modify parameters for the network. The network name and VLAN ID cannot be modified. For more information about other parameters, see "Adding a network." NOTE: The maximum number of connections cannot be smaller than the number of existing connections in the network. To delete a VSI Type from the network, first delete all connections that are created by the VSI Type in the network. Deleting a network A network cannot be deleted when it contains connections. To delete the network, first delete connections from it. To delete a network that does not contain connections: 2. From the navigation tree, select VAN Connection Manager > Network. All networks are displayed in the network list. 3. Click the Delete icon for a network to be deleted. 4. Click OK in the confirmation dialog box that opens. 40

50 Managing VSI Types A VSI Type is a set of network policies that manage access privileges and ensures service qualities for VMs. It contains one or more service units, for which you can configure parameters as needed. A VSI Type supports the following service units: Bandwidth Control Specifies the guaranteed bandwidth for traffic between clients and the VM, such as committed information rate (CIR) and peak information rate (PIR). VM Access Control Allows specific clients to access the VM. Prioritize Access to VM (Specific Clients) Prioritizes packets between specific clients and the VM. This priority setting takes precedence over the priority setting for all clients. Prioritize Access to VM (All Clients) Specifies the default priority for packets between all clients and the VM. Managing VSI Type versions You can create multiple VSI Type versions for a VSI Type. All VSI Type versions of a VSI Type must contain the same service units, but a service unit must have at least one parameter different from the other service units. For example, to specify different access privileges for the VMs in a network assigned with a VSI Type, you can create multiple VSI Type versions for the VSI Type and apply them to different VMs. Applying and removing a VSI Type A VSI Type is applied to and removed from the edge switch through VCM. If you do not apply a VSI Type to the edge switch: In VEB mode, the edge switch can forward packets but cannot control traffic for the VMs. In EVB mode, the edge switch cannot forward packets for the VMs. Viewing the VSI Type list 2. From the navigation tree, select VAN Connection Manager > VSI Type. The VSI Type list displays all VSI Types. VSI Type list contents Name Name of the VSI Type or VSI Type version. You can click the expand icon to view the VSI Type versions of the VSI Type. If the VSI Type does not contain any VSI Type versions, the expand icon is not available. The VSI Type version name is in the VSI Type Name (VX) format, where X represents the number of the version. For example, Lessee (V1). Status To view the number of connections associated with each VSI Type version, place the cursor over the icon. Only VSI Type versions with the top 10 associated connections are displayed. For VSI Type versions, a icon indicates that the VSI Type version has been bound to a VM, and a icon indicates that the VSI Type version has not been bound to any VM. You can place the cursor over the icon to view names of the connections and VMs. The field is empty if the VSI Type has no VSI Type versions. 41

51 Network To view the network to which the VSI Type is assigned and the VLAN to which the network belongs, place the cursor over the icon. A VSI Type can be assigned to multiple networks. This field is empty for VSI Type versions. Service Unit To view the service units of the VSI Type, place the cursor over the icon. This field is empty for VSI Type versions. Description Description for the VSI Type or VSI Type version. Release Version/Time To release a new VSI Type version, click the icon for the VSI Type. For VSI Type versions, this field displays the release time of the VSI Type version. Modify Click the icon to modify the VSI Type. This field is empty for VSI Type versions. Delete Click the icon to delete the VSI Type or VSI Type version. You cannot delete VSI Types containing VSI Type versions that have been bound to VMs. 3. To refresh the page and view the most recent information about the VSI Types, click Refresh. Querying a VSI Type Basic query 2. From the navigation tree, select VAN Connection Manager > VSI Type. The VSI Type list displays all VSI Types. 3. Enter the name of the VSI Type in the query box on the top right of the page. This field supports fuzzy matching. 4. Click the query icon. All VSI Types matching the criterion are displayed in the VSI Type list. 5. To display all VSI Types, clear the query box and click the query icon. Advanced query 2. From the navigation tree, select VAN Connection Manager > VSI Type. The VSI Type list displays all VSI Types. 3. Click the Expand icon next to the query box. 4. In the query area, specify one or more of the following query criteria: Name Enter the name of the VSI Type. This field supports fuzzy matching. VSI Type version numbers are not supported. Status Select a binding status for the VSI Type versions of the VSI Type. Options are All, Bound, and Not Bound. If you select All, all VSI Types are queried. TopN Versions Specify the number of VSI Type versions to be displayed for each VSI Type. If you enter 5 in this field, only the most recent five VSI Type versions are displayed for each VSI Type. Networks Select the network to which the VSI Type is assigned. If you select All, all VSI Types are queried. Release Time From/To Specify the release time range for the VSI Type versions. You can click the box to select the time from the calendar or enter the time in YYYY-MM-DD hh:mm:ss format. The end time must be later than the start time. An empty field does not serve as a query criterion. 5. Click Query. All VSI Types matching the criteria are displayed in the VSI type list. 42

52 6. To clear the query criteria and display all VSI Types, click Reset. 7. To hide the query area, click Close. Viewing detailed information about a VSI Type or VSI Type version 2. From the navigation tree, select VAN Connection Manager > VSI Type. The VSI Type list displays all VSI Types. 3. Click the name of a VSI Type or VSI Type version. The VSI Type Details window opens and displays detailed information about the VSI Type or VSI Type version. Basic Information area Name Name of the VSI Type or VSI Type version. Description Description for the VSI Type or VSI Type version. Network area The network list displays all networks to which the VSI Type or VSI Type version is assigned. Network list contents Name Name of the network. VLAN ID VLAN to which the network belongs. Description Description for the network. Service Unit List area Service Unit List contents Name Name of the service unit. Description Description for the service unit. Parameter Settings area Parameter settings list contents Client IP IP address or network address of the client. Mask Subnet mask of the client's IP address. Filtering Direction Packet filtering direction. Options are INBOUND, OUTBOUND, and BOTH. CIR (kbps) Committed information rate, which is the average rate of packets in the filtering direction. PIR (kbps) Peak information rate, which is the maximum rate of packets in the filtering direction. Priority Setting Priority type. Options are 802.1p, DSCP, IP Precedence, and Local Precedence. Priority Value Priority of the packets. 4. Click Close. 43

53 Adding a VSI Type A VSI Type can contain one or more service units, and you can configure different parameter sets for each service unit. For example, to ensure that multiple subnets with different priorities can access the same VM, you can specify different parameter sets for each subnet. Configuration procedure 2. From the navigation tree, select VAN Connection Manager > VSI Type. The VSI Type list displays all VSI Types. 3. Click Add. The Add VSI Type window opens. 4. Configure basic information: Name Enter a name for the VSI Type, a string of 1 to 32 characters. To view the allowed characters for the string, place the cursor over the icon. Network Select a network for the VSI Type. Description Enter a description for the VSI Type. 5. Select service units for the VSI Type and configure the parameters as shown in Table 6. Table 6 Service unit parameters Service unit Bandwidth Control VM Access Control Parameters Client IP Enter a network address or an IP address of the client to access the VM. Wildmask Specify the subnet wildmask of the client's IP address in either of the following ways: If subnet mask inversion is enabled on ACLM, enter the subnet mask. For example, if the subnet mask is , enter If wildcard mask is enabled on ACLM, enter the wildcard mask of the subnet mask. For example, if the subnet mask is , enter By default, wildcard mask is enabled on ACLM. Filtering Direction Select a packet filtering direction. Options are INBOUND, OUTBOUND, and BOTH. INBOUND Controls bandwidth for traffic from the VM to clients. OUTBOUND Controls bandwidth for traffic from clients to the VM. BOTH Controls bandwidth for traffic in both directions. CIR (kbps) Specify the average rate of packets in the filtering direction. The value range for this field varies by device model. For more information, see the configuration guide for the edge switch. PIR (kbps) Specify the maximum rate of packets in the filtering direction. The value range for this field varies by device model. For more information, see the configuration guide for the edge switch. Client IP Enter a network address or an IP address of the client to access the VM. Wildmask Specify the subnet wildmask of the client's IP address in either of the following ways: If subnet mask inversion is enabled on ACLM, enter the subnet mask. For example, if the subnet mask is , enter If wildcard mask is enabled on ACLM, enter the wildcard mask of the subnet mask. For example, if the subnet mask is , enter By default, wildcard mask is enabled on ACLM. Filtering Direction Select a packet filtering direction. Options are 44

54 Service unit Prioritize Access to VM (Specific Clients) Prioritize Access to VM (All Clients) Parameters INBOUND, OUTBOUND, and BOTH. INBOUND Allows the VM to access the specified client. OUTBOUND Allows the specified client to access the VM. BOTH Allows the specified client and the VM to access each other. Client IP Enter a network address or an IP address of the client to access the VM. Wildmask Specify the subnet wildmask of the client's IP address in either of the following ways: If subnet mask inversion is enabled on ACLM, enter the subnet mask. For example, if the subnet mask is , enter If wildcard mask is enabled on ACLM, enter the wildcard mask of the subnet mask. For example, if the subnet mask is , enter By default, wildcard mask is enabled on ACLM. Filtering Direction Select a packet filtering direction. Options are INBOUND, OUTBOUND, and BOTH. INBOUND Prioritizes packets sent by the VM to the specified client. OUTBOUND Prioritizes packets sent by the specified client to the VM. BOTH Prioritizes all packets exchanged between the specified client and the VM. Priority Setting Select a priority type. Options are 802.1p, DSCP, IP Precedence, and Local Precedence. The edge switch remarks the packets with the specified priority type and value. Priority Value Specify a priority value for the packets. The value range for this field varies by device model. For more information, see the configuration guides for the edge switch. Filtering Direction Select a packet filtering direction. Options are INBOUND, OUTBOUND, and BOTH. INBOUND Prioritizes packets sent by the VM to all clients. OUTBOUND Prioritizes packets sent by all clients to the VM. BOTH Prioritizes packets exchanged between all clients and the VM. Priority Setting Select a priority type. Options are 802.1p, DSCP, IP Precedence, and Local Precedence. The edge switch remarks the packets with the specified priority type and value. Priority Value Specify a priority value for the packets. The value range for this field varies by device model. For more information, see the configuration guide for the edge switch. 6. Click Add. The configured parameter set is displayed in the parameter box. You can configure up to 10 parameter sets for a VSI Type, and all parameters in the parameter sets must belong to the same service unit. If you change the service unit selection for the VSI Type, all parameter sets are cleared. 7. To delete one or more parameter sets, select the parameter sets and click Delete. 8. To save the configuration, click Save. The VSI Type is displayed in the VSI Type list. 9. To save the configuration and release the configuration as a VSI Type version, click Save and Release. Both the VSI Type and the VSI Type version are displayed in the VSI Type list. 45

55 Configuration example Network requirements The R&D department and the marketing department of an enterprise belong to the subnet /16 and /16, respectively. Configure a VSI Type to allow the R&D department and the marketing department to access the file server of the enterprise and apply the following network policies to the two departments: The downlink CIR and PIR of the R&D department are 4 Mbps and 10 Mbps, respectively. The uplink rate is not limited. The downlink CIR and PIR of the Marketing department are 5 Mbps and 10 Mbps, respectively. The uplink rate is not limited. The priorities for packets sent by the file server to the R&D department and the marketing department are 4 and 5, respectively. Configuration procedure 1. Create VSI Type A. a. Click the Resource tab. b. From the navigation tree, select VAN Connection Manager > VSI Type. c. Click Add. The Add VSI Type window opens. d. Configure basic information and parameters for VSI Type A as shown in Table 6. 46

56 Figure 25 Adding VSI Type A 2. Click Save and Release to save the configuration and release VSI Type version VSI Type A (V1). 47

57 Modifying a VSI Type You cannot modify VSI Type versions. To modify a VSI Type: 2. From the navigation tree, select VAN Connection Manager > VSI Type. The VSI Type list displays all VSI Types. 3. Click the Modify icon for the target VSI Type. The Modify VSI Type window opens. 4. Modify the parameters. You cannot modify the name, network, and service units of the VSI Type. For more information, see "Adding a VSI Type." Releasing a VSI Type version All VSI Type versions of a VSI Type must contain the same service units. When you release a new VSI Type version, you must configure a minimum of one parameter different from the other VSI Type versions. Otherwise, the VSI Type version cannot be released. You can release a VSI Type version in either of the following methods: Method 1 Release a VSI type version when you add or modify a VSI Type. For more information, see "Adding a VSI Type." Method 2 Release a VSI Type by clicking the icon in the VSI Type list. Before releasing a VSI type version, you must add a new VSI Type or modify a VSI Type. For more information about the VSI Type list, see "Viewing the VSI Type list." Deleting a VSI Type Before you delete a VSI Type containing VSI Type versions that have been bound to VMs, unbind the VSI Type versions from the VMs. Deleting a VSI Type deletes all its VSI Type versions. To delete a VSI Type: 2. From the navigation tree, select VAN Connection Manager > VSI Type. The VSI Type list displays all VSI Types. 3. To delete VSI Types one by one, click the icon for the target VSI Type and click OK in the dialog box that opens. 4. To bulk delete VSI Types, select the VSI Types to be deleted, click Delete, and click OK in the dialog box that opens. Deleting a VSI Type version You cannot delete VSI Type versions that have been bound to VMs. To delete a VSI Type version: 2. From the navigation tree, select VAN Connection Manager > VSI Type. 48

58 The VSI Type list displays all VSI Types. 3. Click the expand icon for the VSI Type to which the target VSI Type version belongs. 4. Click the icon for the target VSI Type version. 5. Click OK in the dialog box that opens. 49

59 Managing connections A connection refers to the association between a vnic and a VSI type. The network administrator and the server administrator can manage connections from VCM and vmanager, respectively. Before the server administrator can manage connections on vmanager, the network administrator must register a plug-in on vmanager based on virtualization software type. For more information about plug-in registration, see "Customizing VCM widgets." Connection types You can create a VEB connection or EVB connection for a VM. If both the vswitch that the VM accesses and the edge switch support EVB, an EVB connection is created. If either of them does not support EVB, a VEB connection is created. VEB connection A VEB connection can be deployed when VRM obtains the access switch and access interface of the VM. For more information, see "Configuring VRM." You can manually deploy and undeploy a VEB connection. VCM automatically deploys and undeploys a connection when VRM detects the following events: VM migration During a VM migration, VCM undeploys the connection and deletes the VSI Type from the source edge switch, and then deploys the connection and applies the VSI Type to the target edge switch. VM removal When a VM is deleted or VRM cannot identify the physical server to which the VM belongs, VCM undeploys the connection. NOTE: To enable VRM to detect VM state changes, the physical server must be added to IMC and identified as a virtual device by VRM. EVB connection You cannot manually deploy and undeploy an EVB connection. VCM obtains the VM state through the requests sent by the edge switch, and then automatically deploys and undeploys the connection when the following VM state changes occur: VM startup VCM deploys the connection when the VM starts. VM shutdown VCM undeploys the connection when the VM is shut down. VM migration VCM undeploys the connection from the source edge switch and then deploys the connection on the target edge switch. VSI Type modification from vmanager VCM undeploys the connection based on the original VSI Type, and then deploys the connection based on the modified VSI Type. 50

60 Automatic VSI Type migration with a VM migration A VSI Type associated with a VM can be automatically migrated with the VM if the following conditions are met: For VEB connections, VRM must obtain information about the VM migration and the access location of the VM. For EVB connections, the source and target servers and edge switches connected with the VM must support the same EVB function set. Viewing the connection list 2. From the navigation tree, select VAN Connection Manager > Connection. The connection list displays all connections. Connection list contents Status State of the connection. Options are Not Deployed, Fail Deployed and Deployed. You can click Not Deployed, Fail Deployed or Deployed for a deployed or once-deployed connection to view the online and offline records of the VM. For more information, see "Managing life cycle reports." Name Name of the connection. vnic IP IPv4 address of the VM's primary vnic. Primary vnic MAC address of the VM's primary vnic. VM VM label, which includes the name and IP address of the VM. Click the label link to view its details. This field is blank if VRM has not obtained information about the physical server. Physical Server Name of the physical server to which the VM belongs. Click the name link to view its details. This field is blank if VRM has not obtained information about the physical server. Network Name of the network to which the connection belongs. This field is blank if the connection does not belong to any network. VSI Type Name of the VSI Type version with which the VM is associated. Click the name link to view its details. Access Switch Access switch label for the VM. Click the label link to view detailed information about the access switch. For undeployed VEB connections, this field is blank if VRM does not know the access switch of the VM. This field is blank for EVB connections that have never been deployed. Access Interface Name of the interface that connects the switch to the VM. For undeployed VEB connections, this field is blank if VRM does not know the access interface of the VM. This field is blank for EVB connections that have never been deployed. Operation You can click the icons in the Operation field to perform relevant operations, including deploying and undeploying connections, viewing operation records, modifying connections, and deleting connections. The deploy and undeploy icons are displayed only for VEB connections. The modify and delete icons are not displayed for deployed connections. Synchronizing the connections You can synchronize the most recent information about the vnics from VRM, including vnic IP, VM name, physical server, access switch, and access interface. After synchronizing the connections, refresh the connection list to view the most recent information. 51

61 To synchronize the connections: 2. From the navigation tree, select VAN Connection Manager > Connection. The connection list displays all connections. 3. Click Synchronize. Information about all connections is synchronized. Querying a connection VCM supports both basic and advanced queries. Basic query 2. From the navigation tree, select VAN Connection Manager > Connection. The connection list displays all connections. 3. Enter the name of the target connection in the query box on the top right of the page. This field supports fuzzy matching. 4. Click the query icon. All connections matching the criterion are displayed in the connection list. To display all connections, clear the query box and click the query icon. Advanced query 2. From the navigation tree, select VAN Connection Manager > Connection. The connection list displays all connections. 3. Click the Expand icon next to the query box. 4. In the query area, specify one or more of the following query criteria: Name Enter the name of the connection. This field supports fuzzy matching. vnic IP Enter the vnic IP address. This field supports fuzzy matching. Status Select a state for the connection. Options are All, Deployed, Not Deployed, and Fail Deployed. If you select All, all connections are matched. Network Select a network. If you select All, all connections are matched. VSI Type Select a VSI Type. If you select All, all connections are matched. VSI Type Version Select a VSI Type version. If you select All, all connections are matched. An empty field does not serve as a query criterion. 5. Click Query. All connections matching the criteria are displayed in the connection list. 6. To clear the query criteria and display all connections, click Reset. Viewing detailed information about a VM 2. From the navigation tree, select VAN Connection Manager > Connection. The connection list displays all connections. 52

62 3. Click the label link of a VM. The Summary window opens and displays detailed information about the VM. VM basic information area Virtual Machine Name Name of the VM. Virtual Machine IP IP address of the VM. If the VM has multiple IP addresses, the IP addresses are separated by semicolons (;). CPU Core quantity of the VM's CPU. Memory Size of the VM's memory. Operating System Type of the VM's operating system. Virtual Tools Operating state of the virtual tools. Status State of the VM, Stopped or Running. Server Label of the physical server to which the VM belongs. The label includes the name and IP address of the physical server. vmanager Label of the vmanager that manages the VM. The label includes the name and IP address of the vmanager. Disk area Name Name of the disk. Capacity Capacity of the disk. vnic area vnic list contents Label Name of the vnic. If the vnic name is not configured or cannot be configured, this field displays the MAC address of the vnic. IP IP address of the vnic. MAC MAC address of the vnic. Access Switch Name of the switch to which the vnic is connected. Access Interface Name of the interface that connects the switch to the vnic. 4. Click Close. Adding a connection A network administrator can add a connection on VCM or create a connection when deploying a vapp. For more information about deploying vapp, see "Deploying a vapp." To add a connection on VCM: 2. From the navigation tree, select VAN Connection Manager > Connection. The connection list displays all connections. 3. Click Add. The Add Connection window opens. 4. Configure connection parameters: Name Enter a name for the connection, a case-insensitive string of 1 to 128 characters. vnic Enter the MAC address (in the format) of the vnic or select a VM. To select a VM: # Click Select. The window for selecting a VM opens. 53

63 # In the Query VM area, set the following query criteria: VM Name Enter the name of the VM. This field supports fuzzy matching. IP Enter the IP address of the VM. This field supports fuzzy matching. Physical Server Enter the label of the physical server to which the VM belongs. This field supports fuzzy matching. # Click Query. All VMs matching the criteria are displayed in the VM List. # Select a VM from the VM List. If a VM has multiple vnics, you can click the # Click OK. The MAC address of the selected vnic is displayed in the vnic box. 54 icon to select a MAC address from the list. VM IP Enter the IP address of the vnic. If the VM is managed by VRM and VRM has obtained an IP address of the VM, VCM queries the IP address of the VM based on its MAC address and displays the IP address in the query box. Otherwise, you need to enter the IP address in the box. This field can be blank. VLAN VLAN to which the VM belongs. This field is not configurable. Network Select a network. This field can be blank. VSI Type Select a VSI Type. If you select a network, only VSI Types assigned to this network are displayed in the list. VSI Type Version Select a VSI Type version. Description Enter a description for the connection. 5. Click OK. Deploying or undeploying a connection You can only deploy and undeploy VEB connections. To deploy or undeploy a connection on VCM: 2. From the navigation tree, select VAN Connection Manager > Connection. The connection list displays all connections. 3. To deploy a connection, click the icon in the Operation field for the target connection. 4. The Operation field does not display the icon if the Access Switch and Access Interface fields are blank. 5. To undeploy a connection, click the icon in the Operation field for the target connection. Modifying a connection You can modify only undeployed connections. To modify a connection on VCM: 2. From the navigation tree, select VAN Connection Manager > Connection. The connection list displays all connections. 3. Click the Modify icon for the target connection. The Modify Connection window opens. 4. Modify the parameters.

64 You cannot modify the name and vnic of the connection. For more information, see "Adding a connection." 5. Click OK. Deleting a connection You can delete only undeployed connections. To delete a connection on VCM: 2. From the navigation tree, select VAN Connection Manager > Connection. The connection list displays all connections. 3. To delete connections one by one, click the icon for the target connection and click OK in the dialog box that opens. 4. To bulk delete connections, select the connections to be deleted, click Delete, and click OK in the dialog box that opens. Deploying a vapp 2. From the navigation tree, select VAN Connection Manager > Connection. The connection list displays all connections. 3. Click vapp Deployment. The Deploy Connections for the vapp in vcloud window opens. 4. Configure the vcloud authentication information: Protocol This field supports only the HTTPS protocol. vcloud Director IP Enter the IP address of the vcloud director. Port Number Enter the HTTPS protocol port number that is configured on the vcloud director. The default value is 443. Username Enter the username of the administrator. Organization Enter the name of the organization. If the administrator can manage all organizations, enter system. Otherwise, enter the name of the organization that can be managed by the administrator. Password Enter the password of the administrator. vcloud Version Select a vcloud version. Only version 5.1 is supported. 5. Click Next. The vapp Deployment tab is displayed. 6. Configure the vapp and VM: vapp information: vapp Name Enter a name for the vapp. Organization Select an organization. To add a new organization, click Add next to the field. Organization vdc Select an organization vdc. To add a new organization vdc, click Add next to the field. vapp Template Select a vapp template. To add a new vapp template, click Add next to the field. 55

65 Runtime Lease Enter the runtime lease for the vapp, in days or hours.vcm stops the vapp service when the runtime lease expires. Storage Lease Enter the storage lease for the vapp, in days or hours.vcm clears all data of the vapp when the storage lease expires. VM information: Primary vnic Select a vnic for the VM when the VM has multiple vnics. Network Select a network for the VM. IP Address Assignment Select an IP address assignment mode. Options are Static IP Pool, Manual Assignment, and DHCP. If you select Manual Assignment, you need to manually assign IP addresses to vnics. 7. Click Next. The Network Connections tab is displayed. 8. Configure the connections: To bulk configure connections, specify the following parameters next to Batch Deploy, and then click Batch Deploy. Network Select a network. VSI Type Select a VSI Type. If you select a network, only VSI Types assigned to this network are displayed in the list. VSI Type Version Select a VSI Type version. To configure connections one by one, specify the following parameters in the connection list: Connection Enter a name for the connection. Network Select a network. VSI Type Select a VSI Type. If you select a network, only VSI Types assigned to this network are displayed in the list. VSI Type Version Select a VSI Type version. 9. Click Next. The Ready to Complete tab is displayed. 10. Click Deploy. VCM starts to deploy the vapp and create connections. 56

66 Managing life cycle reports Overview The Life Cycle Report module provides lists to record the VM migrations, and the connection deployment and undeployment processes triggered by VM startup, shutdown, deletion, or migration events. A connection deployment or undeployment process includes one or multiple service unit-based operations. A service unit consists of one or more operations to perform a specific function. Therefore, a connection deployment or undeployment process contains multiple service unit-based operations. For example, the bandwidth control service unit is used to control network bandwidth between a VM and its clients. To implement the function, you must configure ACLs based on the VM's IP address and set the guaranteed bandwidth for traffic between the VM and its clients. In a VEB environment, you can manually start connection deployment and undeployment processes. Also, certain events can trigger IMC to start the processes as follows: When VCM finds a VM for the first time, VCM starts the connection deployment process. When a VM is deleted, VCM starts the connection undeployment process. When a VM migrates, VCM starts both connection deployment and undeployment processes. In an EVB environment, connection deployment and undeployment processes can be only executed automatically. Each time a VM starts, stops, or migrates, VCM starts the connection deployment or undeployment process. Migration History VCM relies on VRM to monitor the migrations of VMs, and to record the information of each migration. When VRM detects that the access location of a VM has changed, it determines that the VM has migrated and tells VCM to record the migration information. VCM displays the details of each migration in the Migration History list, which includes: Source and destination switches. Source and destination interfaces. Source and destination physical servers. Migration time. Migration results. In addition to the Migration History list, you can also view the migration details in a more intuitive way icon view, which helps you easily trace each migration of a VM. Operation List A VM startup, shutdown, deletion, or migration event triggers VCM to deploy or undeploy connections. VCM provides the Operation List to record the operation details and results for each deploy or undeploy process. VCM supports the following processes for connection deployment and undeployment: Offline Connection undeployment process. VCM removes connection configurations, including QoS, ACL, and VLAN, from the edge switch to which the VM is connected. If this process is triggered by VM migration, VCM removes connection configurations from the source edge switch. 57

67 Online Connection deployment process. VCM deploys connection configurations, including QoS, ACL, and VLAN, to the edge switch to which the VM is connected. If this process is triggered by VM migration, VCM deploys connection configurations to the destination edge switch. Managing migration records Viewing the migration list 2. From the navigation tree, select VAN Connection Manager > Life Cycle Report. 3. On the Life Cycle Report page, click the Migration History tab. All VM migration records are displayed in the migration history list. The list includes the following parameters: VM Name of the migrated VM. vnic MAC address of the vnic. If the VM has multiple vnics, this field displays all MAC addresses of the vnics. Source Switch Device label of the edge switch that connects to the physical server where the VM resides before the VM migration. Source Interface Interface of the edge switch the VM connects to before the VM migration. Source Physical Server Device label of the physical server where the VM resides before the VM migration. Destination Switch Device label of the edge switch that connects to the physical server where the VM resides after the VM migration. Destination Interface Interface of the edge switch the VM connects to after the VM migration. Destination Physical Server Device label of the physical server where the VM resides after the VM migration. Migration Time Time when VM migration ends. Migration Result Migration result of the VM network configuration. The migration of a VM network configuration always contains multiple operations. According to the results of these operations, the migration result can be: Success All operations to migrate the VM network configuration were successful. Partial Success Part of the operations performed to migrate the VM network configuration failed. Click the View icon in the Operation field to view the failed operations and the cause of failure. Failure All the operations performed to migrate the VM network configuration failed. Click the View icon in the Operation field to view the failed operations and the cause of failure. Operation Operations you can perform, which include: Operation Information Click the Operation Information icon to view the connection deployment and undeployment processes executed during the VM migration. For more information, see "Viewing the operation records of a VM migration process." View Click the View icon to open the Migration Details page. For more information, see "Viewing migration details." 58

68 Icon View Click the Icon View icon to view the historical migration records related to a specified vnic on a VM in icon view. For more information, see "Viewing the historical record of VM migration in icon view." When the VM is closed during migration, the Operation Information icon icon are not displayed. Querying historical migration records Basic query 2. From the navigation tree, select VAN Connection Manager > Life Cycle Report. 3. On the Life Cycle Report page, click the Migration History tab. All VM migration records are displayed in the migration history list. 4. In the query field to the right of the list, enter the MAC address of a vnic. This field supports fuzzy matching. 5. Click the Query icon. All matching migration records are displayed in the list. To display all migration records, clear the query field and click the Query icon. Advanced query 2. In the navigation tree, select VAN Connection Manager > Life Cycle Report. 3. On the Life Cycle Report page, click the Migration History tab. and View 4. Click the Advanced icon next to the query field to expand the query area. 5. Specify one or more of the following query criteria: vnic Enter the MAC address of the vnic. This field supports fuzzy matching. VM Enter the name of the VM. This field supports fuzzy matching. Source/Destination Switch Enter the label of the edge switch that connects to the physical server where the VM resides. This field supports fuzzy matching. All migration records associated with the specified edge switch are matched. Source Switch Enter the label of the edge switch that connected to the physical server where the VM resided before the VM migration. This field supports fuzzy matching. Source Interface Enter the interface name of the edge switch the VM connected to before the VM migration. This field supports fuzzy matching. Source Physical Server Enter the device label of the physical server where the VM resided before the VM migration. This field supports fuzzy matching. Destination Switch Enter the device label of the edge switch that connects to the physical server where the VM resides after the VM migration. This field supports fuzzy matching. Destination Interface Enter the interface name of the edge switch the VM connects to after the VM migration. This field supports fuzzy matching. Destination Physical Server Enter the device label of the physical server where the VM resides after the VM migration. This field supports fuzzy matching. Migration Result Select a migration result. Options are All, Success, Failure, Partial Success, Running, and Waiting. Migration Start Time/Migration End Time Select or enter the migration start time and end time, in the format YYYY-MM-DD hh:mm:ss. 59

69 6. Click Query. All matching migration records are displayed in the list. To clear the query criteria and display all migration histories, click Reset. To hide the advanced query area, click Close. Viewing the operation records of a VM migration process Perform this task to view the connection deployment and undeployment processes executed by VCM during VM migration. To view the operation records of a VM migration process: 2. From the navigation tree, select VAN Connection Manager > Life Cycle Report. 3. On the Life Cycle Report page, click the Migration History tab. All VM migration records are displayed in the migration history list. 4. Click the Operation Information icon for a record in the Operation field. The list displays the connection deployment and undeployment processes triggered by the migration process. Viewing migration details Perform this task to view detailed information about a VM migration, including the connection deployment and undeployment processes performed to migrate the VM network configuration. For VM migrations that are partial successful or failed, viewing migration details might help determine the reason for the failure. To view migration details: 2. From the navigation tree, select VAN Connection Manager > Life Cycle Report. 3. On the Life Cycle Report page, click the Migration History tab. All VM migration records are displayed in the migration history list. 4. Click the View icon for a record in the Operation field. The Migration Details window displays the following areas and parameters: Basic Information area Migration Time Time when the VM migration ended. VM Name of the migrated VM. vnic MAC address of the vnic. If the VM has multiple vnics, this field displays all MAC addresses of the vnics. Source Switch Device label of the edge switch that connected to the physical server where the VM resided before the VM migration. Destination Switch Device label of the edge switch that connects to the physical server where the VM resides after the VM migration. Source Interface Interface name of the edge switch the VM connected to before the VM migration. Destination Interface Interface name of the edge switch the VM connects to after the VM migration. Source Physical Server Device label of the physical server where the VM resided before the VM migration. 60

70 Destination Physical Server Device label of the physical server where the VM resides after the VM migration. Migration Result Result of VSI Type migration. The value can be Success, Failure, or Partial Success. Successful Operations Number of successful operations. Failed Operations Number of failed operations. Unexecuted Operations Number of unexecuted operations. Online Operations area This area displays information about the connection deployment process performed during VM migration. Switch Name Device label of the switch, service units and their names, and the operation name. To expand the menu, click the Expand icon. Interface Interface that connects the edge switch to the VM. Operation Result The result can be: Success or Failure. Parameters Parameters of the operation. Details If the operation fails, this field indicates the cause of failure. Offline Operations area This area contains information about the connection undeployment process performed during VM migration. For descriptions about the parameters, see the Online Operations area. Viewing the historical record of VM migration in icon view The icon view provides a more intuitive way to view all historical migrations of a VM. To view the historical record of VM migration in icon view: 2. From the navigation tree, select VAN Connection Manager > Life Cycle Report. 3. On the Life Cycle Report page, click the Migration History tab. All migration records are displayed in the migration history list. 4. Click the Icon View icon for a record in the Operation field. The system displays the historical migration records related to the specified vnic of the target VM by Icon View. NOTE: With the icon view, a historical record provides all migrations of a vnic that belongs to the target VM. When a VM has multiple vnics, you can respectively view the migration records for each migrated vnic of a VM in the icon view. For example, Figure 26 shows the historical migrations related to the vnic (0015-5d ) of the VM (test_windows_vmotion). The target VM has been migrated three times, starting from the source server (HYPERV ) to the destination server (HYPERV ). 61

71 Figure 26 Viewing historical record of VM by Icon View The icon view of the VM historical migrations provides the following information: VM Name of the VM. vnic MAC address of the vnic. If the VM has multiple vnics, this field displays all MAC addresses of the vnics. Migration Latest Time Time when the VM migration ended for the last time. Switch Device label of the edge switch that connects to the physical server where the VM resides. Interface Interface that connects the edge switch to the VM. Physical Server Device label of the physical server where the VM resides. Migration Result Migration result of the VSI Type. It can be: Success All operations to migrate the VM network configuration were successful. Failure All operations to migrate the VM network configuration failed. Partial Success Some of the operations to migrate the VM network configuration failed. The migration result is grayed out for a VM that is shut down. Managing operation records Viewing the operation list 2. From the navigation tree, select VAN Connection Manager > Life Cycle Report. 3. Click the Operation List tab. All connection deployment and undeployment processes are displayed in the operation list. The list includes the following parameters: VM Name of the VM. vnic MAC address of the vnic. If the VM has multiple vnics, this field displays all MAC addresses of the vnics. Access Switch Label of the edge switch to which the VM is connected. Access Interface Name of the switch interface to which the VM is connected. Connection Name Name of the connection. VSI Type VSI Type version that is bound to the vnic of the VM. Operation Type Type of the process: Online or Offline. Execution Time Execution time of the process. Result Result of the process: Success All operations of the process were successful. 62

72 Failure All operations of the process failed. Partial Success Some of the operations of the process failed. Running Operations of the process are being performed. Waiting Operations of the process are waiting to be performed. Operation Click the View icon to view the operation details. Querying connection deployment and undeployment processes Basic query 2. From the navigation tree, select VAN Connection Manager > Life Cycle Report. 3. Click the Operation List tab. All connection deployment and undeployment processes are displayed in the operation list. 4. In the query field to the right of the list, enter the MAC address of a vnic. This field supports fuzzy matching. 5. Click the Query icon. All matching connection deployment and undeployment processes are displayed in the list. To display all operation records, clear the query field and click the Query icon. Advanced query 2. From the navigation tree, select VAN Connection Manager > Life Cycle Report. 3. Click the Operation List tab. All connection deployment and undeployment processes are displayed in the operation list. 4. Click the Advanced icon next to the query field to expand the query area. 5. Specify one or more of the following query criteria: vnic Enter the MAC address of the vnic. This field supports fuzzy matching. VM Enter the name of the VM. This field supports fuzzy matching. Access Switch Enter the label of the edge switch. This field supports fuzzy matching. Access Interface Enter the interface name of the switch to which the VM connects. This field supports fuzzy matching. Connection Name Enter the name of the connection that is bound to the vnic. This field supports fuzzy matching. VSI Type Enter the VSI Type that is bound to the vnic. This field supports fuzzy matching. Operation Type Select an operation type. Options are All, Online, and Offline. Result Select an operation result. Options are All, Success, Failure, Partial Success, Running, and Waiting. Execution Time From/To Select or enter the execution start time and end time, in the format of YYYY-MM-DD hh:mm:ss. 6. Click Query. All matching connection deployment and undeployment processes are displayed in the list. To clear the query criteria and display all operations, click Reset. To hide the advanced query area, click Close. 63

73 Viewing operation details If a connection deployment or undeployment process fails, or only partially succeeds, you can view the cause of failure on the Operation Details page. To view operation details of a connection deployment or undeployment process: 2. From the navigation tree, select VAN Connection Manager > Life Cycle Report. 3. Click the Operation List tab. All connection deployment and undeployment processes are displayed in the operation list. 4. Click the View icon for a process in the Operation field. The Operation Details page displays the following areas and parameters: Basic information area Execution Time Execution time of the process. Operation Type Type of the process: Online or Offline. VM Name of the VM. vnic MAC address of the vnic. If the VM has multiple vnics, this field displays all MAC addresses of the vnics. Access Switch Device label of the edge switch on which the connection deployment or undeployment process is performed. Access Interface Interface of the edge switch to which the VM connects. Result Result of the process: Success or Failure. Successful Operations Number of successful operations. Failed Operations Number of failed operations. Unexecuted Operations Number of unexecuted operations. Online Operations area Switch Name Device label of the edge switch, service units and their names, and the operation name. To expand the menu, click the Expand icon. Interface Interface that connects the VM to the edge switch. Operation Result Result of the operation: Success or Failure. Parameters Parameters of the operation. Details If the operation fails, this field indicates the cause of failure. Offline Operations area This area contains information about the connection undeployment process performed during VM migration. For descriptions about the parameters, see the Online Operations area. 64

74 VEB scheme configuration example Network requirements As shown in Figure 27, VMware, VRM, and VCM have been deployed. The edge switch provides network access for ESXi host A and ESXi host B. Create a VM on ESXi A to provide file services and configure corresponding QoS settings. Figure 27 Network diagram Configure the VCM VEB scheme to meet the following requirements: The administrator can issue the network policies to the edge switch connected to the VMs when the VMs are started and delete the network policies when the VMs are shut down. When the VMs migrate between the ESXi hosts, the network policies are moved along with the VMs automatically. VCM automatically deletes the network policies from the edge switch connected to the VMs when the VMs are deleted. Configuration procedures The VCM VEB scheme configuration includes the following tasks: Adding a SOAP template Adding the edge switch and the two ESXi hosts to IMC Synchronizing devices Enabling CDP on the edge switch Verifying ESXi host availability in VRM Viewing virtual network topology Configuring VCM 65

75 Creating a connection Adding a SOAP template Configure a SOAP template for the ESXi hosts so that VRM can identify the physical servers as virtual devices. In this example, the two ESXi hosts use the same SOAP template. To add a SOAP template: 1. On the top navigation bar, click the System tab, and then select Resource Management > Access Paremeter Template. 2. Click the SOAP tab, and then click Add. 3. On the Add SOAP/HTTP Template page, configure the following settings: Template Name Enter a template name, for example, esx. Access Type Select SOAP. Protocol Select HTTPS. Port( ) Enter 443, the vcenter server HTTPS port number. Root Path Enter sdk, the software development kit directory required by the vcenter Server. Username/Password Enter the username root and the password for logging in to the vcenter Server. Figure 28 Adding a SOAP template 4. Click OK. Adding the edge switch and the two ESXi hosts to IMC 1. Click the Resource tab, and then select Add Device. 2. On the Add Device page, enter the IP address of vcenter Server for Host Name/IP, and select Telnet from the Login Type list. Leave other parameters as their default settings. If SNMP Settings or Telnet Settings are not their default values, click SNMP Settings or Telnet Settings to configure them. The settings must be the same as the settings on the edge switch. For more information about how to configure these settings, see HPE Intelligent Management Center v7.3 Enterprise and Standard Platform Administrator Guide. 66

76 Figure 29 Adding a device 3. Click OK. 4. Repeat steps 1 to 3 to add the two ESXi hosts to IMC. You do not need to configure SNMP and Telnet settings for the two ESXi hosts. Synchronizing devices 1. Click the Resource tab, and then select Device View. 2. Select the two ESXi hosts and the edge switch from the device list. 3. Click Synchronize. 4. Click Refresh after waiting about 1 to 5 minutes. If IMC cannot identify the device type, verify the SOAP template or SNMP parameter configuration. Enabling CDP on the edge switch For VRM to obtain the access location of a VM, you must enable CDP on the edge switch in a VMware virtualization environment. In this example, the edge switch is an HPE Comware-based device that supports CDP. # Enable CDP on the edge switch. <Edge Switch>system-view [Edge Switch]lldp compliance cdp In a non VMware virtualization environment, install the related plug-in. For more information, see "Managing plug-ins." 67

77 Verifying ESXi host availability in VRM 1. Click the Resource tab, and then select Virtual Resource Management > Virtual Network View. ESXi host A ( ) is displayed in the view. Figure 30 ESXi host in the virtual network view 2. Click the FTP Server name link or IP address link. You can see that VRM has obtained the access switch and access interface of the VM. 68

78 Figure 31 Access switch and access interface obtained 3. Follow the same steps to verify ESXi host B availability in VRM. Viewing virtual network topology Click the Resource tab, and then select Virtual Resource Management > Virtual Network Topology. On the virtual network topology, you can see that VRM has obtained the IP address of the switch that is directly connected to the two ESXi hosts. Configuring VCM This section describes VCM configuration. Adding an edge switch 1. Click the Resource tab, and then select VAN Connection Manager > Edge Switch. 2. Click Add. 3. Click the Advanced tab, and enter in the Device IP field. 4. Click Query. The device with the IP address is displayed in the Devices Found area. 5. Select the target device, and click the icon to add the device to the Selected Devices area. 6. Click OK. The device list displays the edge switch. Leave the parameters as their default settings. 69

79 Figure 32 Adding an edge switch Adding a network 1. Click the Resource tab, and then select VAN Connection Manager > Network. 2. Click Add. 3. Configure network parameters: Name Enter Enterprise A. VLAN ID Enter 1. Max. Connections Enter 200. Operation List Not configurable. admin is selected by default because Administrator Group to which admin belongs has the administration privilege for the network module. 4. Click OK. 70

80 Figure 33 Adding a network Adding a VSI Type Add a VSI Type that contains the following QoS settings: Policy application direction Traffic from VM to R&D center (both). CIR 4 Mbps. PIR 10 Mbps p priority 7. To add a VSI Type: 1. Click the Resource tab, and then select VAN Connection Manager > VSI Type. 2. Click Add. 3. Configure basic information: Name Enter VSI Type A. 71

81 Network Select Enterprise A from the list to add the VSI Type to this network. Service Unit List Select Bandwidth Control, VM Access Control, and Prioritize Access to VM (Specific Clients). 4. Click Save and Release. 72

82 Figure 34 Adding a VSI Type 73

83 Creating a connection 1. Click the Resource tab, and then select VAN Connection Manager > Connection Management. 2. Click Add. 3. Configure connection parameters: Name Enter FTP Server A. vnic Click Select, and then select FTP Server from the dialog box that opens. VM IP This field displays the IP address that the VM has obtained because the vnic has obtained a dynamically allocated IP address. VLAN Not configurable. Network Select Enterprise A. VSI Type Select VSI Type A. VSI Type Version Select VSI Type A (V1). Figure 35 Creating a connection 4. Click OK. The connection list displays the created connection. 74

84 Figure 36 Created connection Deploying/Undeploying a connection 1. Click the Resource tab, and then select VAN Connection Manager > Connection Management. 2. To deploy a connection, click the deploy icon in the Operation column. To undeploy a connection, click the undeploy icon in the Operation column. 75

85 EVB scheme configuration example Network requirements As shown in Figure 37, VMware, HPE IMC, and HP 5900v virtual switch have been deployed. The HPE Comware-based switch provides network access for ESXi host A and ESXi host B. Create a VM on ESXi A to provide file services, and configure corresponding QoS settings: Figure 37 Network diagram Configure the VCM EVB scheme to meet the following requirements: VCM automatically deploys the network policies to the edge switch connected to the VMs when the VMs are started. VCM automatically deletes the network policies from the edge switch connected to the VMs when the VMs are shut down. 76

86 When the VMs migrate between the ESXi hosts, the network policies are moved along with the VMs automatically. Configuration prerequisites Make sure you have completed the following tasks before configuring the VCM EVB scheme: Install the VMware vsphere 5.0 or higher on each ESXi host, and assign /24 and /24 to ESXi A and ESXi B, respectively. Install HP FlexFabric Virtual Switch 5900v on ESXi A and assign /24 to 5900v. After you install the 5900v, you can use the EVB-capable vswitch on the vcenter Server. Connect the two ESXi hosts directly to an HPE Comware-based switch that supports EVB, and assign IP address /24 to the switch. Deploy VMware vcenter Server and IMC at the management center, and assign /24 and /24 to them, respectively. Deploy VRM and VCM on HPE IMC. VCM manages VSI Types to implement automatic association between VM lifecycle and network policies. Configuration procedures The VCM EVB scheme configuration includes the following tasks: Configuring the HP 5900v virtual switch Configuring the HPE Comware-based switch Configuring IMC Configuring VCM Creating a connection Configuring the HP 5900v virtual switch The HP 5900v is a virtual switch designed for data center virtualization. It runs on top of the VMware vsphere Enterprise Plus Edition, and works seamlessly with the vcenter Server and VMware ESXi hosts. Deploying the HP 5900v on ESXi host A This section describes only the property configuration during the deployment of the HP 5900v, including configuring the IMC server and vcenter Server. For more information about how to deploy the HP 5900v, see HP FlexFabric Virtual Switch 5900v Installation Guide. If you have deployed the VCE, but the IMC server parameters are incorrect, you can correct the configuration by registering the VCE plug-in on VCM, without deploying the VCE again. For more information, see "Managing the VCE plug-in." To configure the IMC server and vcenter Server: 1. Configure the IMC server: IP Address Enter , IP address of the IMC primary server. Port Enter 8080, the HTTP port number you set when you deploy IMC Platform. Operator/Password Enter the operator username and password for logging in to the IMC server. 77

87 Figure 38 Configuring the IMC server 2. Configure the vcenter Server: IP Address Enter , the IP address of the vcenter Server. HTTP Port Enter 80, the HTTP port number of the vcenter Server. HTTPS Port Enter 443, the HTTPS port number of the vcenter Server. Username/Password Enter the username and password for logging in to the vcenter Server. 78

88 Figure 39 Configuring the vcenter Server Deploying the VFE To deploy the VFE, the server administrator must use the VMware plug-in, which is registered on the vcenter Server when the VCE is deployed. To deploy the VFE: 1. Select Home > Inventory > Hosts and Clusters. 2. Select Datacenter. 3. Click the HP VDS Management tab. HP is the plug-in name you set when you deploy the HP 5900v. 4. Click VFE Configuration in the VFE(Virtual Forwarding Engine) area. 79

89 Figure 40 Deploying the VFE Creating a VDS 5. On the Virtual Forwarding Engine Installation page, select ESXi A and ESXi B from the list, and click Install. 6. After the installation is complete, select ESXi A and ESXi B, and then click License. 1. Select Home > Inventory > Hosts and Clusters. 2. Select Datacenter. 3. Click the HP VDS HP 5900v tab. HP is the plug-in name you set when you deploy the HP 5900v. 4. In the Virtual Distributed Switch area, click Add. 5. Enter HP in the Name field. 6. Click OK. The VDS named HP is displayed in the Virtual Distributed Switch area. Figure 41 Creating a VDS 80

90 Adding hosts to the VDS 1. Select Home > Inventory > Networking. 2. From the left navigation tree, right-click the VDS name HP and select Add Host from the short-cut menu. 3. Select the IP addresses ( and ) of the ESXi hosts, and then select their physical NIC for uplink connections. In this example, select vmnic3 for both hosts. vmnic3 connects to the switch at Leave other fields as their default settings. 4. Click OK. Creating a port group 1. Select Home > Inventory > Networking. 2. From the left navigation tree, select HP. 3. Click the HP Port Group Management tab. This example uses the default port group HPdefaultPortGroup in VLAN 1. The VLAN to which a port group belongs must be within the range of VLANs allowed by the aggregate interface that connects the edge switch to the VM. Figure 42 Creating a port group Verifying vcenter Server connectivity 1. Log in to HP FlexFabric Virtual Switch Orchestration Software for 5900v. 2. Verify that the vcenter Server has been connected. If Disconnect is displayed on the Connection column, click the link to connect to the vcenter Server. 81

91 Figure 43 Verifying vcenter Server connectivity Configuring the HPE Comware-based switch The aggregate interfaces Bridge-Aggregation 11 and Bridge-Aggregation 12 on the edge switch are connected to ESXi A and ESXi B, respectively. You must configure the two aggregated interfaces and the default VSI manager and CDP for the edge switch. The configurations for the two interfaces are the same. Bridge-Aggregation 11 is used as an example. The following commands are available only on an HPE Comware-based device. For the configuration of other types of edge switches, see the device manual. # Enable EVB: [Edge Switch]interface Bridge-Aggregation 11 [Edge Switch-Bridge-Aggregation 11]evb enable # Configure LLDP: [Edge Switch]interface Bridge-Aggregation 11 [Edge Switch-Bridge-Aggregation 11]link-type trunk [Edge Switch-Bridge-Aggregation 11]lldp agent nearest-nontpmr admin-status txrx [Edge Switch-Bridge-Aggregation 11]lldp tlv-enable dot1-tlv protocol-vlan-id [Edge Switch-Bridge-Aggregation 11]lldp tlv-enable dot1-tlv vlan-name # Configure the default VSI manager is the IP address of the IMC primary server, and 8080 is the HTTP port number set on IMC. [evb-acs55]evb default-manager ip port 8080 # Enable CDP on the edge switch: In a VMware virtualization environment, enable CDP on the edge switch: <Edge Switch>system-view [Edge Switch]lldp compliance cdp In a non VMware virtualization environment, install the related plug-in. For more information, see "Managing plug-ins." 82

92 Configuring IMC Adding a SOAP template Configure a SOAP template for the ESXi hosts so that VRM can identify the physical servers as virtual devices. In this example, the two ESXi hosts use the same SOAP template. To add a SOAP template: 1. On the top navigation bar, click the System tab, and then select Resource Management > Access Parameter Template. 2. Click the SOAP tab, and then click Add. 3. On the Add SOAP/HTTP Template page, configure the following settings: Template Name Enter a template name, for example, esx. Access Type Select SOAP. Protocol Select HTTPS. Port( ) Enter 443, the vcenter server HTTPS port number. Root Path Enter sdk, the software development kit directory required by the vcenter Server. Username/Password Enter the username and password for logging in to the vcenter Server. Figure 44 Adding a SOAP template 4. Click OK. Adding the edge switch and the two ESXi hosts to IMC 1. Click the Resource tab, and then select Add Device. 2. On the Add Device page, enter the IP address of vcenter Server for Host Name/IP, and select Telnet from the Login Type list. Leave other parameters as their default settings. If SNMP Settings or Telnet Settings are not their default values, click SNMP Settings or Telnet Settings to configure the settings. The settings must be the same as the settings on the edge switch. For more information about how to configure these settings, see HPE Intelligent Management Center v7.3 Enterprise and Standard Platform Administrator Guide. 83

93 Figure 45 Adding a device 3. Click OK. 4. Repeat steps 1 to 3 to add the two ESXi hosts to IMC. You do not need to configure SNMP and Telnet settings for the two ESXi hosts. Synchronizing devices 1. Click the Resource tab, and then select Device View. 2. Select the two ESXi hosts and the edge switch from the device list. 3. Click Synchronize. 4. Click Refresh after waiting about 1 to 5 minutes. If IMC cannot identify the device type, verify the SOAP template or SNMP parameter configuration. Verifying ESXi host availability in VRM 1. Click the Resource tab, and then select Virtual Resource Management > Virtual Network View. ESXi host A ( ) is displayed in the view. 84

94 Figure 46 ESXi host in the virtual network view 2. Click the FTP Server name link or IP address link. You can see that VRM has obtained the access switch and access interface of the VM. Figure 47 Access switch and access interface obtained 3. Follow the same steps to verify ESXi host B availability in VRM. 85

95 Viewing virtual network topology Click the Resource tab, and then select Virtual Resource Management > Virtual Network Topology. On the virtual network topology, you can see that VRM has obtained the IP address of the switch that is directly connected to the two ESXi hosts. Configuring VCM Registering the VCE plug-in 1. Click the Resource tab, and then select VAN Connection Manager > VCE Plug-In. 2. Click the register icon in the VCE Plug-In area. 3. Configure VCE and vcenter Server information: VCE IP Enter , the IP address of the VCE. VCE Port Number Enter 8080, the port number for accessing the VCE. VCE Username/VCE Password Enter the username and password for logging in to the VCE. vcenter Server IP Enter , the IP address of the vcenter Server. vcenter Server Username/vCenter Server Password Enter the username root and the password for logging in to the vcenter Server. Leave other parameters as their default settings. 4. Click Register. Figure 48 Registering the VCE plug-in Adding an edge switch 1. Click the Resource tab, and then select VAN Connection Manager > Edge Switch. 2. Click Add. 86

96 3. Click the Advanced tab, and enter in the Device IP field. 4. Click Query. Devices with the IP address are displayed in the Devices Found area. 5. Select the target device, and click the icon to add the device to the Selected Devices area. 6. Click OK. The device list displays the edge switch. Leave the parameters as their default settings. Figure 49 Adding an edge switch Adding a network 1. Click the Resource tab, and then select VAN Connection Manager > Network. 2. Click Add. 3. Configure network parameters: Name Enter Enterprise A. VLAN ID Enter 1. Max. Connections Enter Click OK. 87

97 Figure 50 Adding a network Adding a VSI Type Add a VSI Type that contains the following QoS policies: Policy application direction Traffic from FTP server to R&D center (both). CIR 4 Mbps. PIR 10 Mbps p priority 7. To add a VSI Type: 1. Click the Resource tab, and then select VAN Connection Manager > VSI Type Management. 2. Click Add. 3. Configure basic information: 88

98 Name Enter For FTP Server. Network Select Enterprise A from the list to add the VSI Type to this network. Service Unit List Select Bandwidth Control, VM Access Control, and Prioritize Access to VM (Specific Clients). 4. Click Save and Release. 89

99 Figure 51 Adding a VSI Type 90

100 Creating a connection Configuring VDP 1. On the vcenter Server, select Home > Inventory > Networking. 2. From the left navigation tree, select HP. 3. Click the HP Port Group Management tab. 4. Click the None link in the VDP column to configure VDP for the port group. 5. Configure VDP: Network Select Enterprise A, the network you created on VCM. This field only displays networks in VLAN 1. VSI Type Select For FTP Server from the list. VSI Type Version Select For FTP Server (V1) from the list. 6. Click OK. Figure 52 Configuring VDP Configuring the network adapter for the VM 1. Select Home > Inventory > Hosts and Clusters. 2. From the left navigation tree, right-click FTP Server, and select Edit Settings from the short-cut menu. 3. Edit VM vnic1 as required, and select HPdefaultPortGroup from the Network label list. 91

101 Figure 53 Configuring the network adapter for the VM 4. Click OK. The VCM connection list displays the created connection. Figure 54 Created connection 92