HP Intelligent Management Center v5.1 SP1 Connection Resource (Virtual Application Network) Manager Administrator Guide

HP Intelligent Management CenterConnection Resource Manager (VirtualApplication Network Manager)Administrator Guide

AbstractIMC Connection Resource Manager has been renamed to Virtual Application Network (VAN) Manager to more accuratelyreflect its functionality in this release. When installed, Connection Resource Manager is what appears in the user interface.VAN Manager is not referenced in the user interface or user documentation.

HP Part Number: 5998-3313Published: December 2012Edition: 2

Copyright 2012 Hewlett-Packard Development Company, L.P.

Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial

Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under

vendor's standard commercial license.

The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express

warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall

not be liable for technical or editorial errors or omissions contained herein.

Acknowledgments

Microsoft, Windows, Windows XP, and Windows NT are U.S. registered trademarks of Microsoft Corporation.

Contents1 ConnectionRM...........................................................................................5

Functional modules...................................................................................................................5Network diagram.....................................................................................................................5Application environments...........................................................................................................6VEB environment features...........................................................................................................7EVB environment features...........................................................................................................7Managing network configuration migration in ConnectionRM ........................................................7

Prerequisites........................................................................................................................7Configuring ConnectionRM...................................................................................................8Configuring the edge switches and physical servers..................................................................8

Configuring edge switches in the EVB environment..............................................................8In the EVB environment....................................................................................................8

2 ConnectionRM home page widget................................................................9Adding the ConnectionRM view TopN widget to the home page..................................................9Setting the ConnectionRM View TopN widget............................................................................9

Setting TopN.......................................................................................................................9Setting the refresh interval ..................................................................................................10Refreshing the ConnectionRM View TopN widget.................................................................10Deleting the ConnectionRM View TopN widget ..................................................................10

Viewing the ConnectionRM View TopN widget .......................................................................10ACL utilization...................................................................................................................11Connection utilization ........................................................................................................11

3 Edge switch management..........................................................................13Viewing an edge switch list .....................................................................................................13Querying an edge switch........................................................................................................14Adding an edge switch...........................................................................................................15

Selecting devices using the Advanced Query option...............................................................15Setting ACL number range.......................................................................................................16Viewing the migration history of VMs controlled by the edge switch .............................................17Deleting an edge switch .........................................................................................................17

Example for adding an edge switch.....................................................................................17

4 VSI type management...............................................................................20Viewing the VSI Type List ........................................................................................................20Querying VSI type .................................................................................................................21Viewing VSI type details..........................................................................................................22Adding a VSI type..................................................................................................................22

Service units for customizing VSI type...................................................................................22Example of adding a VSI type ............................................................................................24

Modifying a VSI type..............................................................................................................26Deleting a VSI type.................................................................................................................27Releasing a version for a VSI type.............................................................................................27Deleting a version of a VSI type................................................................................................27

5 Network management..............................................................................29ConnectionRM's Network........................................................................................................29Viewing network list ...............................................................................................................29Viewing network details ..........................................................................................................30Adding a network...................................................................................................................31

Network planning .............................................................................................................31Example of adding a network..............................................................................................31

Contents 3

Copying the configuration of a network.....................................................................................32Modifying a network...............................................................................................................33Deleting a network.................................................................................................................33

6 Connection management...........................................................................34Viewing the connection list ......................................................................................................34Querying connection..............................................................................................................35Adding a connection..............................................................................................................35Modifying a connection .........................................................................................................36Deploying a connection...........................................................................................................36Undeploying a connection.......................................................................................................37Deleting a connection ............................................................................................................37

7 Life cycle reports.......................................................................................38Introduction to life cycle reports................................................................................................38Viewing historical record of VM migration via list view.................................................................38Viewing historical record of VM migration via icon view..............................................................39Querying historical migration records .......................................................................................40Viewing operation list..............................................................................................................41Redeploying an online or offline process ...................................................................................42Querying operations...............................................................................................................42

8 Managing vManager plug-ins....................................................................43Registering the vCenter plug-in.................................................................................................43Modifying a vCenter plug-in entry ............................................................................................43Deleting a plug-in entry ..........................................................................................................44Managing connections on a vCenter server ..............................................................................44

9 Configuration example..............................................................................46Network requirements.............................................................................................................46Configuration prerequisites......................................................................................................46Configuring EVB bridges.........................................................................................................46

Recommended configuration procedure................................................................................47Configuring EVB Bridge A...................................................................................................47Configuring EVB Bridge B ..................................................................................................47

Configuring ConnectionRM .....................................................................................................47Verifying the configuration.......................................................................................................49

How does ConnectionRM manage configuration migration?....................................................49

10 Support and other resources.....................................................................50Contacting HP........................................................................................................................50Subscription service ...............................................................................................................50Related information.................................................................................................................50

Documents........................................................................................................................50Websites..........................................................................................................................50

Typographic conventions.........................................................................................................51Product feedback....................................................................................................................51

11 Documentation feedback..........................................................................52Glossary....................................................................................................53Index.........................................................................................................55

4 Contents

1 ConnectionRMThe ConnectionRM service component and IMC Virtual Network Management (VNM) are typicallyused together to meet the growing demand on virtual network management. VNM managesVMware ESX/ESXi and Microsoft Hyper-V virtual networks (see HP IMC Base Platform AdministratorGuide), and ConnectionRM manages dynamic migration of VM network configuration and VMtraffic.ConnectionRM is an efficient solution for physical network configuration migration. It monitors VMstartup, shutdown, and migration processes, and distributes physical network configuration to VMsaccording to their latest access locations. It provides seamless collaboration between physical andvirtual networks. When a VM migrates, ConnectionRM automatically performs network configurationmigration for the VM and eliminates the need for a network administrator to reconfigure the accessswitch for the VM.

Functional modulesConnectionRM comprises the following functional modules:

Edge Switch listManages all switches that directly connect to physical servers. ConnectionRMperforms dynamic network configuration migration only for VMs that access the networkthrough an edge switch.

VSI Type listManages VM network configurations as service units. The service units include:

Bandwidth control

VM access rights

VM access priority (specific clients)

VM access priority (all clients)

Network listAllocates network resources. Operators can assign one VLAN ID to each network,and perform hierarchical management of VSI types. When creating a connection, the operatorcan bind the VSI type version of only the selected network to a virtual network interface card(vNIC).

Connection ListManages VSI-type-version/vNIC bindings as connections. As the core ofConnectionRM, the connection implements dynamic migration of VM network configuration.When a VM is migrated, ConnectionRM removes the VM network configuration by deletingthe deployed connection from the source switch, and deploys the network configuration tothe destination switch by deploying the connection.

Life Cycle ReportDisplays the VM migration history and detailed online/offline operationsperformed by ConnectionRM.

Plug-In ManagementA vManager plug-in integrates connection management into vManagerservers after it is registered for those servers. With the connection management function,vManager administrators can add, modify, delete, deploy, and undeploy connections on thevManager servers.

Network diagramAs shown in Figure 1, an enterprise has four physical servers, on each of which one or more VMsare created. VMs access the enterprise network through Switch A or Switch B. IMC VNM managesthe virtual networks, and ConnectionRM provides dynamic network configuration migration forVMs.

Functional modules 5

Figure 1 Network diagram

The administrator must complete the following configuration tasks on ConnectionRM:

Add Switch A and Switch B as edge switches.

Configure the VSI type of VM A, including bandwidth control and access control.

Bind the VSI type version to VM A's vNIC as a connection.

VM A migrates from Switch B to Switch A. ConnectionRM performs network configuration migrationfor VM A by deleting its network configuration from Switch B and then deploying its networkconfiguration to Switch A.

Application environmentsConnectionRM implementation is based on 802.1Qbg. ConnectionRM can be applied to a VirtualEthernet Bridge (VEB) environment or an Edge Virtual Bridge (EVB) environment, depending onVM access methods.In ConnectionRM, a VEB environment is based on the VEB solution defined in 802.1Qbg, and anEVB environment is based on Virtual Ethernet Port Aggregation (VEPA) or multi-channel VEPAsolution defined in 802.1Qbg. VEB and EVB environments differ in the following aspects:

They require different conditions for connection deploy or undeploy operations inConnectionRM.

A VEB environment supports manual deploy and undeploy operations of connections, but anEVB environment does not.

They have different configuration requirements for physical servers and edge switches. Formore information, see Configuring the edge switches and physical servers.

6 ConnectionRM

VEB environment featuresIn the VEB environment, ConnectionRM deploys or undeploys connections in any of the followingcases:

When VNM discovers a VM, ConnectionRM deploys the predefined connection for the VM.

When VNM detects removal of a VM, ConnectionRM undeploys the connection for the VM.

When a VM migrates, ConnectionRM removes the VM network configuration by deleting thedeployed connection from the source switch, and deploys the network configuration to thedestination switch by deploying the connection.

Operators can manually deploy or undeploy connections in this environment.ConnectionRM supports virtualization software such as VMware ESX/ESXi and Windows Hypver-V,and supports all switch models. VMware ESX/ESXi requires no plug-in. To support WindowsHypver-V, ConnectionRM must work with the VNM agent plug-in and LLDP plug-in. For informationabout installing the plug-ins, see HP Intelligent Management Center Installation Guide.ConnectionRM mostly applies to the VEB environment.

EVB environment featuresIn the EVB environment, ConnectionRM deploys or undeploys connections in any of the followingcases:

When a VM starts, ConnectionRM deploys the predefined connection for the VM after receivinga request from the edge switch.

When a VM stops, ConnectionRM undeploys the connection for the VM after receiving arequest from the edge switch.

When a VM migrates, ConnectionRM removes the VM network configuration by deleting thedeployed connection from the source switch, and deploys the network configuration to thedestination switch by deploying the connection.

Edge switches in the EVB environment must support the EVB feature, and you must configure theedge switches before configuring ConnectionRM. In addition, virtualization software must support802.1Qbg.

Managing network configuration migration in ConnectionRMDescribed here is how to configure the ConnectionRM component, edge switches, and physicalservers to manage physical network configuration migration in ConnectionRM.

PrerequisitesThe prerequisites for managing network configuration migration in Connection RM are:1. Deploy VNM and ACL management features of the IMC Platform, because ConnectionRM is

dependent on these features. For information about installing and deploying the IMC Platform,see HP Intelligent Management Center Installation Guide.

IMPORTANT: ConnectionRM does not support distributed deployment, and must be deployedon the IMC master server.

2. Add edge switches and physical servers to IMC for management. For more information, seeinformation on resource management in HP IMC Platform Administrator Guide.

After you configure SOAP parameters for physical servers managed by IMC, VNM automaticallyobtains information about vSwitches and VMs of the server.VNM cannot obtain IP addresses of Windows Hyper-V VMs, and you must add their IP addressesto IMC and create IP/MAC bindings for VMs in IMC Terminal Access.

VEB environment features 7

Configuring ConnectionRMTo configure ConnectionRM:1. Add the switches managed by IMC as edge switches to ConnectionRM. For more information,

see Edge switch management.2. Add a network. For more information, see Adding a network.3. Add a VSI type and release a VSI type version. For more information, see VSI type

management.4. Add a connection. For more information, see Adding a connection.5. (Optional.) In the VEB environment, register the vCenter plug-in for VMware software on

vCenter servers. After registration, vCenter administrators can add, modify, and deleteconnections on the vCenter servers. For more information, see Registering the vCenter plug-in.

Configuring the edge switches and physical serversFor ConnectionRM to implement dynamic migration of VM network configuration, you must configurethe edge switch and physical server.

Configuring edge switches in the EVB environmentConfigure the interface connecting an edge switch to a physical server as a trunk port. When avSwitch uses multiple NICs to the same edge switch, it combines interfaces on the edge switch intoone aggregate interface.In this environment, no configuration is required on the physical server.

In the EVB environmentIn the EVB environment, configure edge switches as follows:

Configure the interface connecting an edge switch to a physical server as a trunk port, andenable the EVB feature on the port.

Complete LLDP basic configurations:

Enable LLDP globally.

Enable the interface to receive and send LLDP packets with EVB TLVs and CDCP TLVs.

Create a VLAN to forward VM traffic.

Complete basic EVB configurations:

Globally configure the default VDP management address as the IP address of the IMCmaster server.

Enable EVB on the interface.

Configure the VDP keepalive timer.

For information on configuring a physical server, see the server configuration document.

8 ConnectionRM

2 ConnectionRM home page widgetWhen ConnectionRM is deployed, operators can add the ConnectionRM View TopN widget tothe IMC home page to view ACL utilization of each edge switch and connection utilization of eachnetwork which ConnectionRM manages.Provided here is information on how to add, edit, and view the ConnectionRM View TopN widget.

Adding the ConnectionRM view TopN widget to the home pageTo add the ConnectionRM View - TopN widget to the home page:1. Log in to IMC.

The Home tab appears.

2. Place the cursor over the Custom icon on the upper left of the page.

The icon changes into the Pin icon

3. Click the Pin icon

The IMC home page is pinned, displaying an Unpin icon on the left and function links onthe top.

4. Select the space you want to custom, and click the Edit icon on the upper right of thepage.By default, the Welcome space is selected.

5. Click the Resource tab.6. Click the ConnectionRM View TopN widget.

7. Click the Add iconYou can add only one ConnectionRM View TopN widget to the current space. When thecurrent space already contains the ConnectionRM View TopN widget, you cannot add thewidget again.

8. Click OK.The ConnectionRM View TopN widget appears in the space.

Setting the ConnectionRM View TopN widgetTo enter the editing page of the ConnectionRM View TopN widget:1. Click the Home tab.

2. Place the cursor over the Custom icon on the upper left of the page.

The icon changes into the Pin icon

3. Click the Pin icon

The IMC home page is pinned, displaying an Unpin icon on the left and function links onthe top.

Setting TopNTo set TopN:

Adding the ConnectionRM view TopN widget to the home page 9

1. Click the Set icon on the upper right of the ConnectionRM View TopN widget.2. Select Setting.

The Setting window appears.

3. Select a value from the Top list.The available options are 5, 10, 20, and 30. The default value is 5.

4. Click OK.The ConnectionRM View TopN widget displays statistics of the first n networks with the largesttotal connection numbers.

Setting the refresh intervalTo set the refresh interval:

1. Click the Set icon on the upper right of the ConnectionRM View TopN widget.2. Select Refresh interval. The Refresh interval window appears.3. Select a value from the Refresh Interval (min) list.

The available options are No Refresh, 1, 5, 10, and 30. The default value is 10. The NoRefresh option disables automatic refreshing on the ConnectionRM View TopN widget. Inthis case, operators must manually refresh it.

4. Click OK.

Refreshing the ConnectionRM View TopN widget

To manually refresh the ConnectionRM View TopN widget, click the Refresh icon on the upperright of the widget.

Deleting the ConnectionRM View TopN widgetTo delete the ConnectionRM View - TopN widget:

1. Click the Delete icon on the upper right of the widget.A confirmation dialog box appears.

2. Click OK.The ConnectionRM View TopN widget is deleted from the home page.

Viewing the ConnectionRM View TopN widgetThe ConnectionRM View TopN widget on the home page displays ACL utilization in a pie chart,and connection utilization in a line and bar chart.

10 ConnectionRM home page widget

Figure 2 ConnectionRM View TopN widget layout

ACL utilizationThe ACL utilization pie chart lies on the upper left of the widget. It displays the total number ofACLs supported and the remaining number of configurable ACLs on each edge switch thatConnectionRM manages.

Figure 3 ACL utilization pie chart

Each slice of the pie chart represents an edge switch. The size of a slice depends on the totalnumber of ACLs that the operator specifies for the edge switch. A larger slice represents an edgeswitch that is configured to support more ACLs. The slice colors randomly change each time theConnectionRM View TopN widget refreshes.The pie chart comprises an inner circular area and an outer circular area. When placing the cursorover a slice in the inner circular area, you can view the label of the edge switch and the totalnumber of ACLs specified for the switch. When placing the cursor over a slice in the outer circulararea, you can view the remaining ACLs on the switch in number and percentage.

Connection utilizationAs in Figure 3, a line and bar chart is located on the lower part of the widget to show connectionutilization. Each bar represents the connection utilization of a network. ConnectionRM countsnumbers of the following network connection types: undeployed, deployed, and remained. It alsocounts VSI types and displays the network VLAN ID. The vertical axis represents the number ofconnections, and the numbers on it change along with the connection number.

Viewing the ConnectionRM View TopN widget 11

Colored bars represent different connection types as shown in the following:

Connections Undeployed

Connections Deployed

Remaining Connections

To view information about connections and VSI types:

The number on each colored bar represents the number of a specific type of connections onthe network. Place the cursor over a colored area to view the percentage of connections andthe VLAN ID of the network.

Place the cursor over the VSI node on a bar to view the number of VSI types and the VLANID of a specific network.

12 ConnectionRM home page widget

3 Edge switch managementThe following topics provide some functions on the edge switch management including how tomanage the edge switch in the ConnectionRM.The edge switches connect to the end-user local area networks (LANs) or to the Internet serviceprovider (ISP) networks. Edge switches can be routers, routing switches, integrated access devices(IADs), multiplexers, and a variety of MAN and WAN devices that provide entry points intoenterprise or service provider core networks. Edge switches are also referred to as access nodesor service nodes.In IMC platform, the edge switch which connects with the physical server can manage the VSI typeof VMs. Currently, the ConnectionRM module provides four service units for the VM management.It includes bandwidth control, VM access control, prioritize access to VM (specific clients), andprioritize access to VM (all clients). When a virtual machine accesses the network on the edgeswitch, the vNIC, and VSI type of the virtual machine can be bound.

Viewing an edge switch listThe Edge Switch list page provides the basic information of edge switch. In this page, you canview the details of edge switch and do operations on the edge switches.To view the edge switch list:1. Click Resource > ConnectionRM.2. In the navigation tree, click Edge Switch to open the Edge Switch List page.

The Edge Switch List page appears.

You can view the following information:

StatusIndicates the warning status of the current edge switch. It includes the following sevenlevels:

Critical

Major

Minor

Warning

Normal

Unknown

UnmanagedFor more information, see HP IMC Base Platform Administrator Guide.

Device LabelIndicates the device label of the equipment in IMC includes name and IP address.

Connection StatisticsIndicates the statistics of the connection deployment status of the VMsinside of the physical servers. The physical servers connect with the current edge switch.

Connections Deployed: Indicates the number of the connections that are deployed on theedge switch. When the number of connection is not 0, move the pointer to the figure, thewindow with the VM summary information pops up. The information includes the vNICof the VM, the VM name, and the name of the physical server which VM locates.

Connections Not Deployed: Indicates the number of the connections that are not deployedon the edge switch. If the figure is not 0, move the pointer to the figure, the window with

Viewing an edge switch list 13

the VM details pops up. The information includes the vNIC of the VM, the VM name, andthe name of the physical server which VM locates.

Service Units: Indicates a set of the control commands integrated by VSI type. You candeploy the service units on a specified edge switch to control the VMs running on thephysical server. The service units include four types:

Bandwidth Control

VM Access Control

Prioritize Access to VM (Specific Clients)

Prioritize Access to VM (All Clients)

The statistic figure 4 in the list stands for the four types of the service units, not a realstatistics figure for the current edge switch. For more information, see Service units forcustomizing VSI type.

OperationIndicates the following operations:

Setting ACL Number rangeMove the pointer to the ACL Number range icon to view

the ACL number range of the current edge switch. Click the ACL Number range icon

to set the custom ACL number range for the current edge switch. Some devices do notsupport this function, such as HP E series equipment. For more information, see SettingACL number range.

NOTE: For certain brand devices, the ACL number range function is not supported, and

the ACL number range icon does not appear in the operation list.

Viewing Migration HistoryClick theMigration history icon to view all of the migrationhistory of the VMs which are connected to the current edge switch. In addition, there isan interface to enter the Life Cycle Report page. For more information, see Life cyclereports.

Deleting an edge switchClick the Delete icon to delete an edge switch from the edgeswitch list.

Querying an edge switchIn the edge switch list, ConnectionRM provides a Query capability that enables you to search foredge switches by device label.To query edge switch:1. Click Resource > ConnectionRM.2. In the navigation tree, click Edge Switch to open the Edge Switch List page.3. Move the pointer to the Query at the upper-right corner of the Edge Switch List page, and a

search criteria dialog box appears.4. Complete the following search criteria:

Device Label: Input a full or partial device label in the column. The device label can be theswitch label or the switch IP address.

5. Click Query. The edge switches that meet your search criteria are listed in the Edge SwitchList page.

6. Click Reset to clear the query condition, and it shows all the edge switches with default valuesin the list.

14 Edge switch management

Adding an edge switchAdding an edge switch is a necessary step to realize the VMs configuration migration automatically.Edge switch is the access point for ConnectionRM to manage the migration configuration of theVMs.To add an edge switch into the edge switch list:1. Click Resource > ConnectionRM.2. In the navigation tree, click Edge Switch to open the Edge Switch List page.3. Move the pointer to the Add on the top of the Edge Switch List page, and enter the Select

Device page.4. There are two ways to select the device, by Views or by Advanced Query, see Selecting

devices using the Advanced Query option.5. To select the device by Views:

a. From the Select Devices dialog box, click the By View tab.b. Expand the view you want to select devices from by clicking on the arrow to the left of

the three view options, IP View, Device View, or Custom View.c. Click the view you want to select devices from the navigation tree on the left. The devices

from the group you click appear in the Devices Found field to the right of the navigationtree. You can select devices from more than one group by clicking more than one group.

d. Highlight the devices you want to select from the Devices Found list, and click the Addselected icon to add them to the selected devices list.

6. To remove one or more devices, select them, and click the Remove selected icon .7. Confirm that the devices you have found have been added by reviewing the Selected Devices

list.8. Click OK.9. Confirm that the devices now appear in the Devices List field.

Selecting devices using the Advanced Query optionYou can also select devices using the Advanced Query option to search IMC using various criteria,and use the results of the search to add the edge switch.To select the device by Advanced Query:1. From the Select Devices dialog box, click the Advanced tab.

a. Enter values in one or more of the search parameters listed:

Enter the IP address you want to query for. Click theExact Query checkbox if you want IMC to search for

Device IP

the exact IP address you have entered. Leave theExact Query box unchecked if you want IMC to matchonly a certain portion of the IP address.

Configure multiple device IP addresses to besearched. Click the Select device IP list configuration

Device IP List

icon . Then, the Device IP List Configurationwindow appears. Enter one or multiple device IPaddresses in the Input Device IP field (if you entermultiple IP addresses, enter one IP address on eachline), and then click Add to add the entered IPaddresses to the Device IP List field below. Repeatthe steps above to add all device IP addresses to besearched.

To delete an IP address in the Device IP List field,select the IP address, and then click Delete. Click OKto complete the operation. Make sure that the deviceIP addresses to be searched have been added to the

Adding an edge switch 15

Device IP List field. To clear the Device IP List field,

click the Delete icon .

Enter the device name for the devices you want toadd. IMC supports fuzzy matching for device labels.

Device Label

Therefore, you can enter the entire device label forthe device you want to locate, or you can enter justa portion of it. IMC displays all matches that containthe portion you enter.

Select device status from the Device Status list.Device Status

Select a device category form the Device Categorylist.

Device Category

Select a device series from the Device Series list.Device Series

Enter the contact name information by which youwant to search. IMC supports fuzzy matching for this

Contact

field. Therefore, you can enter a partial string for thecontact or the complete string for the contact.

Enter the location information by which you want tosearch. IMC supports fuzzy matching for this field.

Location

Therefore, you can enter a partial string for locationor the complete string for location.

Select device reachability status from the DeviceReachability list.

Device Reachability

b. Click Query to begin your search. The results of your search appear in the Devices Foundfield.

c. Highlight the devices you want to select, and click the Add selected icon to add themto the selected devices list.

2. To remove one or more devices, select them, and click the Remove selected icon .3. Confirm that the devices you have found have been added.4. Click OK.

Setting ACL number rangeYou can use the ACL number range setting function to make a plan on ACL resource. For moreinformation on ACL, see HP IMC Base Platform Administrator Guide.

NOTE: You should set the ACL number range following the ACL number rule.

You can move the pointer on the ACL number range icon in the Edge Switch List page to viewthe default ACL number range before you do the operation of setting ACL number range. Afteryou complete the operation of setting the ACL number range, the new ACL number range willappear in the Edge Switch List page. When the switch is added as the edge switch, ConnectionRMwill obtain the default ACL number range automatically according to the device type.To set ACL number range:1. Click Resource > ConnectionRM2. In the navigation tree, click Edge Switch to open the Edge Switch List page.

3. Click the ACL number range icon for the target edge switch to enter the page for configuringan ACL number range.

4. Type an ACL number range in the ACL number range column.5. Click OK.


The ACL number range varies with device vendors.

Viewing the migration history of VMs controlled by the edge switchTo view the migration history (before and after) of VMs relevant to the current edge switch:1. Click Resource > ConnectionRM.2. In the navigation tree, click Edge Switch to open the Edge Switch List page.

3. Click the Migration history icon to view the migration history of the VMs which connectwith the edge switch.

For more information, see Life cycle reports.

Deleting an edge switchAfter the delete operation, the edge switch does not appear in the list, and it is deleted from theConnectionRM module. When the edge switch is used by a connection, you cannot delete thisedge switch.To delete an edge switch:1. Click Resource > ConnectionRM.2. In the navigation tree, click Edge Switch to open the Edge Switch List page.

3. Click the Delete icon in the Operation field of the edge switch you want to delete.The deleted Edge Switch is removed from the Edge Switch list.

NOTE: When the number of the Connections Deployed or Connections Not Deployed is not 0,the corresponding edge switch is not allowed to be deleted. When you want to delete the edgeswitch, make sure the VMs relevant to the current edge switch are not bound with VSI type andvNIC.

Example for adding an edge switchLily Technology Company is a game development company. It has two physical servers (server Aand server B). The free space is not enough in server A, and the configuration from server A needsto be migrated to server B. In addition, you need to set ACL number range in switch B to controlthe ACL resource. The switches details are as follows:

Switch A IP address is 192.168.5.1/24

Switch B device label is MSTP1_xiaopang4

Switch B is a H3C brand switch which need to set ACL number range.

To add switch A to an edge switch list:1. Click Resource > ConnectionRM.2. In the navigation tree, click Edge Switch to open the Edge Switch List page.3. Click Add to open the Add Edge Switch page.4. To select switch A By View:

a. From the Select Devices dialog box, click the By View tab.b. Expand the IP View to select the switch A IP: 192.168.5.0/24 devices from by clicking

on the arrow to the left of the three view options, IP View, Device View, or Custom View.c. The device switch A you clicked on, appears in the Devices Found field to the right of the

navigation tree.

d. Highlight the switch A from the Devices Found list, and click the to add it to the selecteddevices list.

e. Click OK, the configuration displays in the box below as shown in Figure 4.

Viewing the migration history of VMs controlled by the edge switch 17

Figure 4 Adding switch A to the edge switch list

5. Go back to the Edge Switch List to check that switch A is in the list.To add switch B to an edge switch list:1. Click Resource > ConnectionRM.2. In the navigation tree, click Edge Switch to open the Edge Switch List page.3. Click Add to open the Add Edge Switch page.4. To select switch B by Advance Query:

a. From the Select Devices dialog, click the Advance Query tab.b. Type in xiaopang4 in the Device Label parameters column.c. Click Query to begin the search. Switch B appears in the Devices Found field.

d. Highlight the switch B, and click the Add selected icon to add it to the selected deviceslist.

e. Confirm that the Switch B devices you discovered have been added.f. Click OK, the configuration displays in the box below as shown in Figure 5.


Figure 5 Adding switch B to an edge switch list

5. Go back to the Edge Switch List to check switch B is in the list.To set the ACL number range for switch B:1. Click Resource > ConnectionRM.2. In the navigation tree, click Edge Switch to open the Edge Switch List page.

3. Click the ACL number range icon for MSTP1_xiaopang4 to enter the ACL number rangepage.

4. The default H3C ACL number range is 3000-3999. Type 3100-3500 in the ACL numberrange column.

5. Click OK, the setting process is completed shown as Figure 6.

Figure 6 Setting an ACL number range for switch B

Deleting an edge switch 19

4 VSI type managementA VSI type integrates a set of service unit settings for administrators to perform the Quality ofService (QoS) management and access control for VM. With ConnectionRM, you can deploy aVSI type on a specified edge switch to control the VM running on the physical servers that connectto it.The ConnectionRM module provides the following service units for you to customize a VSI type:

Bandwidth ControlDefines the guaranteed bandwidth for traffic between clients and theVM.

VM Access ControlDefines the clients that are allowed to access the VM.

Prioritize Access to VM (Specific Clients)Prioritizes packets sent from specific clients to theVM. This priority setting takes precedence over the priority set in Prioritize Access to VM (AllClients).

Prioritize Access to VM (All Clients)Defines the default priority for packets sent from all clientsto the VM.

ConnectionRM enables you to use the service units to customize a VSI type. You can then deploythe VSI type to control the bandwidth, access authority, and packet priority for the VM. To customizea VSI type that meets your VM management requirements, you can select one or more serviceunits, and configure multiple sets of parameters for them.Also, the ConnectionRM module provides an efficient way to manage the VSI type. In ConnectionRM,a VSI type is always used as a template, with which you can generate multiple versions for the VSItype to combine with different VM as required. When you customize a VSI type, you can modifya VSI type that has similar service unit configurations, and then release a new version for theupdated VSI type. This helps VSI type classification and management, and also increases yourefficiency in configuring VSI types for VM that have similar service requirements.As the physical network configuration, VSI type can perform QoS management and access controlfor the VM. During a VM migration, in order for the VSI type to automatically migrate with thecorresponding VM, the VSI type needs to be bound to the vNIC of the target VM through connectionconfigurations. For more information, see Connection management.

Viewing the VSI Type ListThe VSI type list displays VSI types and their versions in a tree hierarchy that displays a VSI typeas parent and its versions as children. In the list, you can view the status, the network to which theVSI type is assigned, and other details of the VSI types and their versions.To view the VSI type list:1. From the main IMC menu, click Resource > ConnectionRM.2. In the navigation tree, click VSI Type.The defined VSI types and their versions are listed in the VSI Type List page where you can viewthe following information:

NameIndicates the name of the VSI type.

StatusDisplays version information. Move the pointer to the Status icon . The VersionInformation menu shows the information of the top 10 versions, including the version name

20 VSI type management

and number of connections to which the version is bound. This field also displays the statusof VSI type versions, which includes:

BoundWhen a version is bound to a vNIC of a VM, the Bound icon displays in theStatus field of the version.

Not BoundWhen a version is not bound to any vNIC of a VM, the Not Bound icondisplays in the Status field of the version.

NetworkDisplays network information. Move the pointer to the Network icon , and theNetwork menu shows the information of the network to which you assigned the VSI type. Thisinformation includes the network name and VLAN ID of the network resource uses. For moreinformation, see Network management.

Service UnitDisplays the service units that you use to customize the VSI type. Move the

pointer to the Service Unit icon , and the Service Unit menu displays the service units.

DescriptionIndicates the description of the VSI type or version.

Release Version/Release TimeDisplays a Release icon for a VSI type. When you clickthe icon, you release a new version for the VSI type. For the versions of a VSI type, this fielddisplays the released time of the version.

OperationIndicates the operations you can perform for the VSI type, including:

Modify a VSI typeClick theModify icon in the operation field of a VSI type to modifythe configuration of a VSI type. For more information, see Modifying a VSI type.

Delete a VSI typeClick the Delete icon in the operation field of a VSI type to deletethe specified VSI type. For more information, see Deleting a VSI type.

Delete a versionClick the Delete icon in the operation field of a version to delete thespecified version. For more information, see Deleting a version of a VSI type.

Querying VSI typeConnectionRM provides a Query capability that enables you to search for VSI types or VSI typeversions by name, status, and other parameters.To query for a VSI type:1. From the main IMC menu, click Resource > ConnectionRM.2. In the navigation tree, click VSI Type to open the VSI Type List page.3. Move the pointer to the Query at the upper-right corner of the VSI Type List page. A search

criteria dialog box appears.4. Complete one or more of the following search criteria:

NameInput a full or partial name of the VSI type.

StatusSelect the status of the VSI type. Bound indicates querying the VSI type versionsthat are bound to vNICs. Not Bound indicates querying the VSI type versions that are notbound to vNICs. For more information, see Deploying a connection.

NetworkSelect the network that the VSI type you want to query is assigned to.

TopN VersionsInput the number of the latest released versions of the VSI type you wantto query. For example, if you input 10 in this field, the system only displays the latestreleased 10 versions of the VSI types that meet your search criteria.

Querying VSI type 21

Release Time From/ToClick the Data and Time icon to select a period in which theVSI type version is released.

DescriptionInput one or more keywords of the VSI type description.

5. Click Query. The VSI types that meet your search criteria are listed in the VSI Type List.When you finish your search, you can click Reset to restore the full VSI Type List.

Viewing VSI type detailsThe VSI Type Details page provides the basic information, the network to which the VSI type isassigned, and the service unit configurations of the VSI type. In this page, you can view the detailsof VSI types and the released versions.To view the VSI type details:1. From the main IMC menu, click Resource > ConnectionRM.2. In the navigation tree, click VSI Type to open the VSI Type List page.3. Click the link in the Name field of a VSI type or a released VSI type version for which you

want to view details.The VSI Type Details page appears.

On the VSI Type Details page you can view the following information:

Basic InformationIndicates the basic information of the VSI type, which includes the nameand description of the VSI type or VSI type version.

NetworkIndicates the networks to which the VSI type is assigned.

Service Unit ListIndicates the service units that you use to customize the VSI type.

Parameter SettingsIndicates the parameter settings for the service units that you use tocustomize the VSI type. For more information, see Table 1.

Adding a VSI typeA VSI type can integrate multiple service unit configurations to perform the QoS management andaccess control for VM. Information included here introduces the service units you can use tocustomize your own VSI type, and provides a typical example for how to add a VSI type.

Service units for customizing VSI typeTable 1 lists all service units and the related parameters you can use to customize a VSI type.

Table 1 Service unit description

Parameter settingsDescriptionService Unit

Specify the guaranteedbandwidth for traffic between

Bandwidth Control Client IPSpecify an IP segment for the specific clients bysetting the Client IP and Wildcard Mask parameters. The

client and the VM, such as ConnectionRM controls the bandwidth for the traffic betweencommitted information rate


Table 1 Service unit description (continued)

Parameter settingsDescriptionService Unit

(CIR) and peak informationrate (PIR).

the VM and the clients you specify here. Input a single IPaddress or IP segment with standard IPv4 format.

Wildcard MaskInput a wildcard mask to specify the IPsegment of the specific clients.

Filtering DirectionSpecify the direction of the packets towhich you want to perform bandwidth control. INBOUNDindicates the packets sent from the client to the VM.OUTBOUND indicates the packets sent from the VM to theclient. You also can select BOTH to control the packets of bothdirections.

CIR (kbps)Specify the average rate allowed by the targetVM to transmit or forward packets. In the practicalenvironment, HP recommends that you control the trafficbandwidth to be less than the CIR value.

PIR (kbps)Specify the maximum rate allowed by the targetVM to transmit or forward packets. If the traffic bandwidthexceeds the PIR value, the system discards the redundantpackets to control the bandwidth.

Allow specific clients to accessthe VM.

VM Access Control Client IPSpecify an IP segment for the specific clients bysetting the Client IP and Wildcard Mask parameters. Onlythe clients you specify here are allowed to access the targetVM. Input a single IP address or IP segment with standardIPv4 format.


Filtering DirectionSpecify the direction of the packets towhich you want to perform VM access control. INBOUNDindicates the packets sent from the client to the VM.OUTBOUND indicates the packets sent from the VM to theclient. You also can select BOTH to control the packets of bothdirections.

Prioritize packets from specificclients to the VM. This priority

Prioritize Access toVM (SpecificClients)

Client IPSpecify an IP segment for the specific clients bysetting the Client IP and Wildcard Mask parameters. All thepackets sent from the defined IP address to the target VM aresetting takes precedence overprioritized according to the priority rules defined in this servicethe priority setting for all clients

to the VM. unit. Input a single IP address or IP segment with standardIPv4 format.


Filtering DirectionSpecify the direction of the packets towhich you want to set priority. INBOUND indicates thepackets sent from the client to the VM. OUTBOUND indicatesthe packets sent from the VM to the client. You also can selectBOTH to control the packets of both directions.

Priority SettingIndicate the protocol of the packets for whichyou want to set the priority.

Priority ValueSpecify a priority level for the packets.

Specify the default priority forpackets from all clients to theVM.

Prioritize Access toVM (All Clients)

Filtering DirectionSpecify the direction of the packets towhich you want to set priority. INBOUND indicates thepackets sent from the client to the VM. OUTBOUND indicatesthe packets sent from the VM to the client. You also can selectBOTH to control the packets of both directions.

Priority SettingIndicate the protocol of the packets for whichyou want to set the priority.

Priority ValueSpecify a priority level for the packets.

Adding a VSI type 23

NOTE: If you want to prioritize access to VM, HP recommends that you only select one of theservice units: Prioritize Access to VM (Specific Clients) or Prioritize Access to VM (All Clients) to setthe priority for the packets access. You cannot use both service units to set the priority.

When you configure a VSI type, you can select one or more service units according to your VMmanagement requirements. Also, you can configure multiple sets of parameters for the service unitsyou select, and each set can be added as a service rule. When you configure multiple servicerules, ensure that every service rule contains the same service units. For example, you have selectedthe Bandwidth Control and VM Access Control service units to set a service rule. When you wantto add a new service rule for the VSI type, you only can use the two service units to create the newservice rule. When you use a different set of service units to create a new service rule, the existingservice rules are removed.

Example of adding a VSI typeAs a network administrator, you are assigned to use ConnectionRM to customize a VSI type forthe VM used by the Research and Development (R&D) department and the Testing lab of thecompany. For information security and resource optimization, the VM have to meet the followingrequirements:

The guaranteed CIR and PIR of the bandwidth for the traffic between the VM and clients are1024 kbps and 2048 kbps.

Only the clients in the R&D department (196.128.100.10/24) and the Testing lab(192.128.200.10/24) can access the VM.

Use the DSCP protocol to assign a high priority to the packets sent from the R&D departmentto the VM. Set the priority of the packets sent from the Testing lab to be 3, and the priority ofthe packets sent from the R&D department to be 5.

To add a VSI type:1. From the main IMC menu, click Resource > ConnectionRM.2. In the navigation tree, click VSI Type to open the VSI Type List page.3. Click Add to open the Add VSI Type page.4. Complete the basic information of the VSI type as follows:

NameSpecify a name for the VSI type.

NetworkSelect the network to which you assign the VSI type. For more information,see Network management.

DescriptionSpecify a brief description of the VSI type.

5. Configure the service rule for the R&D department as described in the example.a. Bandwidth Control, VM Access Control, and Prioritize Access to VM (Specific Clients)

are the default service units that are selected when you open the Add VSI Type page. Theparameters related to the service units appear in the Parameter Settings pane.

NOTE: If you want to select other service unit or cancel the selection of a service unit,click the check box of the corresponding service unit.

b. To specify the IP segment of the R&D department, set the Client IP to be 196.128.100.10,and set the Wildcard Mask to be 0.0.0.255.

c. Select INBOUND in the Filtering Direction list.d. For the bandwidth control, set the CIR (kbps) parameter to be 1024, and set the PIR (kbps)

parameter to be 2048.e. Select DSCP from the Priority Setting list, and input 5 in the Priority Value field.f. Click Add below the parameters field. The configuration appears in the box below the

parameters field as a service rule, as shown in Figure 7.


Figure 7 Service unit configuration for the R&D department

6. Configure the service rule for the Testing lab as described in the example.a. Select the Bandwidth Control, VM Access Control, and Prioritize Access to VM (Specific

Clients) service units. The parameters related to the service units appear in the ParameterSettings pane.

b. To specify the IP segment of the Testing lab, set the Client IP to be 192.128.200.10, andset the Wildcard Mask to be 0.0.0.255.

c. Select INBOUND in the Filtering Direction list.d. For the bandwidth control, set the CIR (kbps) parameter to be 1024, and set the PIR (kbps)

parameter to be 2048.e. Select DSCP from the Priority Setting list, and input 3 in the Priority Value field.f. Click Add to the right of the parameters field. The configuration appears in the box below

the parameters field as a service rule, as shown in Figure 8.

Adding a VSI type 25

Figure 8 Service unit configuration for the Testing lab

NOTE: When you want to delete a service rule that you added, select the target servicerule, and then click Delete.

7. To save the VSI type configuration, click Save. The VSI type appears in the VSI type list. Whenyou want to release a version for the VSI type, click Save and Release. The VSI type and thereleased version appear in the VSI type list. For more information, see Releasing a versionfor a VSI type.

After configuring a VSI type, you can release versions for it, which can be used to define aconnection. For more information, see Connection management.

Modifying a VSI typeIn the Modify VSI Type page, you can modify the configuration of a VSI type. When you modifya VSI type, you cannot modify the name of the VSI type or the network to which you assign theVSI type. You can add or delete service rules for a VSI type. When you define a new service rule,you can only use the same set of service units with the existing service rules. In addition, this functionalso enables you to release a version for the VSI type you modified.

NOTE: You can modify a VSI type, but cannot modify the released versions of a VSI type. If youwant to customize a VSI type version, you need to first customize the VSI type, and then releasea new version for the VSI type.

To modify a VSI type:1. From the main IMC menu, click Resource > ConnectionRM.2. In the navigation tree, click VSI Type to open the VSI Type List page.

3. Click the Modify icon of the VSI type you want to modify. The Modify VSI Type pageappears.


4. You can modify the basic information and service unit configurations in the Modify VSI Typepage. For more information, see Adding a VSI type.

5. After you modify the VSI type, click Save to save the changes.When you want to release a version for the updated VSI type, click Save and Release. The releasedversion displays in the VSI type list. For more information, see Releasing a version for a VSI type.

Deleting a VSI typeDeleting a VSI type deletes the VSI type, as well as all the released versions of the VSI type.To delete a VSI type:1. From the main IMC menu, click Resource > ConnectionRM.2. In the navigation tree, click VSI Type to open the VSI Type List page.

3. Click the Delete icon in the Operation field of the VSI type you want to delete. A verificationdialog box opens.

NOTE: If there are one or more versions of a VSI type that are bound to the vNICs of VM,you cannot delete the VSI type. The Delete icon does not display in the Operation field. Inthis scenario, if you want to delete the VSI type, you must first unbind the versions. For moreinformation, see Undeploying a connection.

4. Click OK to delete the VSI type.The VSI type that you delete is removed from the VSI Type List.

Releasing a version for a VSI typeIn ConnectionRM, after you modify a VSI type, you can release a version for the updated VSI typeto retain the changes. This task facilitates customizing VSI types for the VM that have similar servicerequirements. Also, it enables you to classify and manage the VSI types.The three ways to release a version for a VSI type are as follows:

Release a version when adding a new VSI typeWhen you add a new VSI type, click Save and Release after completing the VSI type parametersto release a version for the new VSI type.

Release a version when modifying a VSI typeWhen you modify a new VSI type, click Save and Release after modifying the VSI typeparameters to release a version for the VSI type.

Release a version from the VSI type list

In the VSI Type List page, click the Release icon in the Release Version/Release Time fieldof the target VSI type. A new version displays under the VSI type.

Deleting a version of a VSI typeBefore deleting a version of a VSI type, make sure that the version is not bound to any vNIC ofVM. In ConnectionRM, if a version of a VSI type is bound to a vNIC of a VM, you cannot deletethe version.To delete a version of a VSI type:1. From the main IMC menu, click Resource > ConnectionRM.2. In the navigation tree, click VSI Type to open the VSI Type List page.

3. Click the Delete icon in the Operation field of the version you want to delete. A verificationdialog box opens.

Deleting a VSI type 27

NOTE: If the version is bound to the vNICs of VM, the Delete icon does not display inthe Operation field. In this scenario, if you want to delete the version, you must firstly unbindit. For more information, see Undeploying a connection.

4. Click OK to delete the version. The version you delete is removed from the VSI Type List.


5 Network managementAs an advanced data exchange technology, VLAN allows a network administrator to logicallysegment a LAN into different broadcast domains. Each VLAN includes a group of workstationsthat have the same or similar application requirements. The packets generated by a workstationin a VLAN can only be transmitted through the network resources (ports) within the VLAN, whichhelps traffic and bandwidth control, simplifies the network management, and improves the networksecurity.

ConnectionRM's NetworkThe ConnectionRM provides a management facility, Network, for assigning ports for transferringthe traffic between VM and clients, and the VSI types you can deploy for controlling the trafficbetween VM and clients. In the ConnectionRM, a network can indicate a port through specifyingthe VLAN ID of the port in the network. Each network can only consume one VLAN ID. Whencreating a connection, you need to assign a network to the connection. This enables the VMspecified in the connection to use the port to send or receive packets to and from the clients. Inthis way, you can specify a network for the VM that has the same or similar application requirementsto improve the management efficiency, or assign the network according to your network plan andthe practical requirements. For more information, see Connection management.Another important function of the network management is VSI type assignment. With networkmanagement, you can assign one or more VSI types to a specified network, which allows theadministrator to deploy the specified VSI types for managing the VM that can use the network tocommunicate with the clients.In addition, when creating a network, you can authorize one or more operators or operator groupsto manage the VSI types assigned to the network. In the ConnectionRM, to view and manage theVSI types, you must log on to the IMC base platform as an authorized operator.

NOTE: With the network management, you can assign VSI type management privilege for anoperator or operator group. You can assign this privilege when you add an operator group in theIMC base platform. For more information, see HP IMC Base Platform Administrator Guide.

Viewing network listIn the network list, you can view the created networks, and the related information, such as theVLAN ID, the VSI types that the network can manage, and other details of the network.To view the VSI type list:1. From the main IMC menu, click Resource > ConnectionRM.2. In the navigation tree, click Network. The created networks are listed in the Network List page.In the network list, you can view the following information:

Indicates the name of the network.Network Name

Indicates the VLAN ID of the port that is assigned to the network. Each network can only consumeone VLAN ID. When you select a network for a connection, the VM specified in the connectioncan communicate with the clients through the corresponding ports.

VLAN ID

Indicates the maximum number of the connections allowed to be created in the network. Whencreating a connection, you should specify the network that the connection belongs to. When the

Max. Connections

number of the connections in the specified network reaches the value defined in this field, youcannot create any new connections in the specified network. For more information, see Addinga connection.

Indicates the description of the network.Description

ConnectionRM's Network 29

Indicates whether or not the connections of the network are specified the guaranteed bandwidth.This field uses the following bars to indicate the different bandwidth control status:

Bandwidth Control

Green barIndicates at least one connection is specified the guaranteed bandwidth in thenetwork. Move the pointer to the bar to view the number of the connections that are specifiedthe guaranteed bandwidth, and the maximum PIR value specified for the connections. InConnectionRM, the bandwidth control of a connection is achieved by configuring the BandwidthControl service unit for the VSI types that the connection used.

Grey barIndicates at least one connection is not specified the guaranteed bandwidth in thenetwork. Move the pointer to the bar to view the number of the connections that are notspecified the guaranteed bandwidth.

BlankWhen there is no connection in the network, this field is left blank.

Indicates the number of the connections in the network. This field uses the following bars toindicate the connections of different status:

Connection

Green barMove the pointer to the green bar to view the number of the connections thathave been deployed in the network.

Red barMove the pointer to the red bar to view the number of the created connections thathave not been deployed in the network

Grey barMove the pointer to the grey bar to view the number of the remaining connectionsthat you can create in the network.

For more information, see Adding a VSI type and Adding a connection.

Click the Copy icon to copy the configurations of the specified network, which can be atemplate for you to create a new network. For more information, see Copying the configurationof a network.

Copy

Click the Modify icon to modify the configurations of the specified network. For moreinformation, see Modifying a network.

Modify

Click the Delete icon to delete a network. For more information, see Deleting a network.Delete

Viewing network detailsThe Network Details page provides the basic information and the VSI type settings of the network.In this page, you can view the detailed configurations of the network.To view the network details:1. From the main IMC menu, click Resource > ConnectionRM.2. In the navigation tree, click Network to open the Network List page.3. Click the link in the Network Name field of the network for which you want to view details.The Network Details page appears. You can view the following information:

Indicates the name of the network.Name

Indicates the VLAN ID of the port that is assigned to the network. Each network can only consumeone VLAN ID. When you select a network for a connection, the VM specified in the connectioncan communicate with the clients through the corresponding ports.

VLAN ID

Indicates the maximum number of the connections allowed to be created in the network. Whencreating a connection, you should specify the network that the connection belongs to. When the

Max. Connections

number of the connections in the specified network reaches the value defined in this field, youcannot create any new connections in the specified network.

Indicates the description of the network.Description

Indicates the VSI types that are assigned to the network.VSI Type Settings

Indicates the operators or operator groups that have the privileges to manage the VSI types thatare assigned to the network. In ConnectionRM, to view and manage the VSI types, you must logon to the IMC base platform as an authorized operator.

Operator List

30 Network management

Adding a networkBefore creating a network, the network administrator should plan the network resource in advance.Introduced here is the network planning, which is the basis and prerequisite for adding andconfiguring a network.

Network planningIn the ConnectionRM, a network is a facility for assigning ports for transferring the traffic betweenVM and clients, as well as the VSI types you can deploy for controlling the traffic between VM andclients. Therefore, the network configuration is based on the network planning in the practicalenvironment. As a network administrator, you should first plan the physical network environment,which includes creating VLANs according to the application requirements, assigning networkresources (such as ports), and so on. You also have to identify the service requirements of the VM,which helps you to classify the VSI types, authorize the operators, and so forth.With ConnectionRM, you can create networks and assign a VLAN ID to a network according tothe VLANs configured in the practical environment. By assigning a network to a connection, theVM specified in the connection can communicate with the clients through the corresponding ports.In addition, you can also classify the VSI types by assigning VSI types to different network. Whencreating a connection, when you select a network, you can only use the VSI types that are assignedto the network to control the traffic between VM and clients.Another important planning step is to decide which operators or operator groups have the privilegesto manage the VSI types that are assigned to a network, which helps the specialization ofmanagement authorities.

Example of adding a networkAs a network administrator, you are assigned to use ConnectionRM to customize a network for aVLAN (VLAN ID is 2). The maximum number of connections is 10. The network includes the followingVSI types:

VSI Type A

VSI Type B

In addition, only the operators in the administrator group and maintainer group can manage thetwo VSI types.To add a network:1. From the main IMC menu, click Resource > ConnectionRM.2. In the navigation tree, click Network to open the Network List page.3. Click Add to open the Add Network page.4. Complete the basic information of the network as follows:

NameSpecify the name for the network.

VLAN IDInput the VLAN ID of the VLAN. The value ranges from 1 to 4094, and youmust input the VLAN ID that applies to a trunk port of a switch. In this example, input 2in the VLAN ID field.

Max. ConnectionsSpecify the maximum number of the connections allowed to createdin the network. In this example, input 10 in the Max. Connections field.

DescriptionInput a brief description of the network.

5. In the VSI Type Settings pane, click the VSI Type A from the Available VSI Types list box, and

then click the Add Selection icon . The VSI type A displays in the Selected VSI Type listbox.

6. Repeat step 5 to add the VSI Type B to the Selected VSI Type list box.

Adding a network 31

NOTE: To select all the VSI types list in the Available VSI Types box, click the Add All

Selections icon . When you want to remove a selected VSI type, click the VSI type in the

Selected VSI Type list box, and then click the Remove Selection icon . To remove all the

selected VSI types, click the Remove All Selected icon .

7. In the Operator List pane, click the checkbox of the operators or operator groups you wantto authorize to manage the network. The administrator group has been authorized fullpermissions in the IMC base platform and all added-on modules. This group is authorized bydefault. In this example, click the checkbox of the maintainer group to authorize the operatorsin this group to manage the VSI types that are assigned to the network, as shown in Networkconfiguration example.

Figure 9 Network configuration example

NOTE: Click the Expand all icon to view the operators in all operator groups. Click theCollapse all icon to only view the operator groups.

8. Click OK. A message displays to show the network is added successfully. The network youconfigure displays in the Network List.

Copying the configuration of a networkWhen creating a new network, you can copy the configuration of a similar network, which canbe used as a template. In this way, you can quickly create a new network based on the copiedconfiguration.To copy the configuration of a network:

32 Network management

1. From the main IMC menu, click Resource > ConnectionRM.2. In the navigation tree, click Network to open the Network List page.

3. Click the Copy icon in the Copy field of the network you want to copy. The Add Networkpage and the parameter settings of the network you copied displays.

4. Modify the name of the network.5. Modify the other parameters of the network as required. For more information, see Example

of adding a network.6. Click OK. A message displays to show the network is added successfully.

The network you configure displays in the Network List.

Modifying a networkThe ConnectionRM provides you with the ability to modify the configuration of a network. You canmodify the basic information, VSI type settings, and change the authorization of the operators.You cannot modify the name of a network. Besides, you cannot change the value of the Max.Connections to be less than the number of existing connections in the network.To modify a network:1. From the main IMC menu, click Resource > ConnectionRM.2. In the navigation tree, click Network to open the Network List page.

3. Click the Modify icon of the network you want to modify to open the Modify Networkpage.

4. Modify the parameters of the network as required. For more information, see Example ofadding a network.

5. Click OK.

Deleting a networkIf there is a connection that belongs to the network you want to delete, which means that at leastone of the VSI type versions in the network is bound to vNICs, you cannot delete the network.To delete a network:1. From the main IMC menu, click Resource > ConnectionRM.2. In the navigation tree, click Network to open the Network List page.

3. Click the Delete icon of the network you want to delete. A verification dialog box opens.4. Click OK to delete the network.When there is at least one VSI type version in the network that is bound to a vNIC, the followingmessage is displayed: Please create a task to delete the connection because the network containsa VSI Type version that is bound to vNICs. In this scenario, when you want to delete the network,you should first delete all the connections in the network.

Modifying a network 33

6 Connection managementThe Connection management function allows for the binding of a specific VSI Type version intothe target vNIC of the virtual machine.When the virtual machine starts, stops, or migrates, ConnectionRM is able to deploy the connectionbound with a VSI Type to the target virtual machine. With this function the administrator can deploythe VSI Type information to the edge switch automatically. Deploying a connection in the VM sendsa specific VSI Type configuration to the target edge switch. ConnectionRM does not supportmigration when the MAC address of the vNIC has changed. When the virtual machines vNICchanges, you need to create a new connection for the new vNIC.The deploy mechanism and process of EVB and VEB are different:In an EVB environment:

Deploying or undeploying a connection manually is unavailable.

ConnectionRM deploys or undeploys the connection every time when the VM starts or stops.

In a VEB environment:

Deploying or undeploying a connection manually is available.

Only in the following three situations can ConnectionRM deploy or undeploy a connectionautomatically:

The first time when VNM finds the VM.

When the VNM finds that the VM is deleted.

When the VM migrates.For more information, see Deploying a connection.

Viewing the connection listThe connection list displays the detail information of each connection. In the list, you can checkmany current parameter values, and you also can check their details by entering the correspondingpage.To view the connection list:1. Click Resource > ConnectionRM.2. In the navigation tree, click Connection to open the Connection List page.3. All connections and their detail information are displayed in the connection list.The following is a table of the connection list items:

Click to open the Operation List page where you can check the operation history details. TheGreen icon indicates that the connection has been deployed; the red one indicates that theconnection is not deployed.

Status

Display the connection name.Name

Display the connection description.Description

Display the target vNIC IP of connection.vNIC IP

Display the target vNIC MAC address. Click the MAC address of the target vNIC to enter inthe related Virtual Machine page. You can check the VM detail information in this page. In

vNIC

ConnectionRM, use a specific vNIC to represent a VM. If the vNIC changed, the VM makes achange accordingly.

Display the target VM name and IP address.VM

34 Connection management

Display the physical server name and IP address. Click the target physical server name to enterin the Device Details page for checking details. For more information, see IMC Base PlatformAdministrator Guide.

Physical Server

Display the network name that the connection used.Network

Display the target VSI Type version. Click the target VSI Type to open the related VSI TypeDetails window. For more information, see Viewing VSI type details.

VSI Type

Display the device label and IP address of the target switch. Click the target access switch toopen the Resource page for details checking

Access Switch

Display the interface of the switch that used to communicate with the physical server.Access Interface

Include four user operations as follows:Operation

ModifyModify the configurations of an undeployed connection.

DeleteDelete an undeployed connection from the connection list.

DeployDeploy a connection to the edge switch.

UndeployUndeploy a connection from the edge switch.

NOTE: When a connection has been deployed, it is no longer possible to Deploy/Undeploy,Modify, or Delete it manually. So the related icons do not appear in the Operation column.

Querying connectionConnectionRM provides a Query capability that enables you to search for connection by name,vNIC IP, and other parameters.To query the connection:1. Click Resource > ConnectionRM.2. In the navigation tree, click Connection to open the Connection List page.3. In the top right corner, put the cursor on Query to open the Query floating pane.4. Completing the query conditions.5. ClickQuery .6. Click Reset to reset the query conditions, and then click Query to perform a new query process.

Adding a connectionConnectionRM allows you to add a new connection between a specific VSI Type and a vNIC ofthe virtual machine. When you add a new connection, ConnectionRM judges if the target switchis an edge switch, if it is not, the adding process cannot be successful.To add a new connection:1. Click Resource > ConnectionRM.2. In the navigation tree, click Connection to open the Connection List page.3. Click Add to open the Add Connection window.4. Enter the following parameters:

NameSpecify a name to the connection.

vNICSpecify the vNIC address with a format like this: xxxx-xxxx-xxxx. Or clickSelect to open the VM list page. All available VMs are displayed in this page; you cancheck the VM detail information, such as VM Name, Status, IP, and Physical Server. Thenselect a vNIC that you want and click OK to go back to the connection adding procedure.Also, you can use the Query VM function to search for your target VM, then select it.

VM IPAfter you select a target vNIC, the VM IP address is loaded automatically. Also,you can specify an IP address for the VM, but if the VM IP address is not ready for

Querying connection 35

ConnectionRM to access, this item might be empty. After a while, ConnectionRM canrefresh the VM IP address automatically.

NetworkSelect a target network.

VSI TypeSelect a target VSI Type from the list. If you have assigned a network for thisconnection, only the VSI Type that belongs to this network appears in the list.

VSI Type VersionSelect a target VSI Type Version.

DescriptionDescribe the connection.

5. Click OK.

NOTE: You can add a new connection in the vCenter with the Plug-In Management function. Itwill appear in the Connection List of ConnectionRM however it cannot be found in the vCenter.Furthermore, the values of connection Name and vNIC must be unique whether the connection isadded in vCenter or ConnectionRM.

Modifying a connectionConnectionRM allows you to modify the parameters of an existed connection. After you modify aconnection, it is necessary to deploy this connection into the switch. If the connection has beendeployed, it is unavailable to modify the configurations.To modify a connection:1. Click Resource > ConnectionRM.2. In the navigation tree, click Connection to open the Connection List page.

3. Click the Modify icon under the Operation column of the target connection item to openthe Modify Connection page.

4. Modify the following parameters except connection name and VM:

VM IPSpecify a new IP address for the VM.

NetworkSelect a new network.

VSI TypeSelect a target VSI Type from the list.

VSI Type VersionSelect a target VSI Type Version.

DescriptionDescribe the connection. For more information, see Adding a connection.

5. Click OK.

Deploying a connectionAfter you add a new connection successfully, you need to create a task of deploying this newconnection to the target switch. Then the deploy details are sent back to you, and you can checkthem in the Operation List. If all of your configurations are not deployed successfully, ConnectionRMprovides the redeploy function to redeploy the configurations manually.A VEB environment as an example to describe the process of how to deploy a successful connectionin the ConnectionRM. To an EVB environment, you do not have to deploy the connection to theswitch. After you finish the connection adding procedure, ConnectionRM does this for youautomatically. Also, VEB and EVB have the same result in the checking procedure.The parts of the process to finalize a connection deploy process are:

Add a new connection.

Deploy the connection to the target switch.

Check the deployed results.

Redeploy the connection.

To deploy a connection:

36 Connection management

1. Click Resource > ConnectionRM.2. In the navigation tree, click Connection to open the Connection List page.3. Click Add to open the Add Connection page.4. Complete the parameters. For more information, see Adding a connection.5. Click OK to go back to the Connection List page.6. Click the Deploy icon , and a reminder dialog box appears at the top of the page with the

message Task XXX to deploy the connection successfully added.7. Wait a moment for the Operation List page to open.8. Check operation results in the Operation List page. If the deploy is successful, then the deploy

process is over. When the deploy is a failure or a partial success, complete the followingsteps.a. In the Operation List page, click the Details icon to open the Operation Details page.b. In the Operation Details page, check the failure reason.c. Check your environment according to the failure reason.d. Click the Deploy icon to redeploy the configurations of the connection successfully.

Undeploying a connectionIn a VEB environment, when the virtual machine migrates, you need to eliminate the formerconnection configurations in the switch to release the port which is occupied by the formerconnection. This process is called undeploying a connection. After undeploying a former connection,it still exists in the Connection List and you can deploy it again whenever you want.To undeploy a connection:1. Click Resource > ConnectionRM.2. In the navigation tree, click Connection to open the Connection List page.3. Click the Undeploy icon to undeploy the connection.

Deleting a connectionConnectionRM allows you to delete an existing connection from the connection list. However, ifthe connection has been deployed, it is not possible to delete the connection.To delete a connection:1. Click Resource > ConnectionRM.2. In the navigation tree, click Connection to open the Connection List page.

3. Click the Delete icon under the Operation column of the target connection.4. Click OK.

Undeploying a connection 37

7 Life cycle reportsLife cycle reports provide lists to record the VM migrations, and the offline and online operationsto migrate the VM network configuration.

Introduction to life cycle reports Migration History

IMC monitors the migrations of the target VM, and records the information of each migration.ConnectionRM displays the details of each migration in the Migration History list, whichincludes:

Source and destination switches

Source and destination physical servers

Source and destination interfaces

Time of the migration

Migration resultsIn addition to the Migration History list, you can also view the migration details in a moreintuitive wayicon view, which helps you easily trace each migration of a VM.

Operation ListThe operation List records the offline and online operations of the VM network configurations.A VM network configuration integrates a set of control commands to perform the QoSmanagement and access control for the target VM. It is deployed on the edge switch thatconnects to the physical server of the VM. ConnectionRM provides the ability to migrate thecorresponding network configuration with the VM automatically, and records the configurationoffline and online operations related to the VM migrations.The operation list shows the results of the configuration, offline and online operations, whichhelps you chec