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

HP Intelligent Management Center
Connection Resource Manager (Virtual

Application Network Manager)
Administrator Guide
Abstract
IMC Connection Resource Manager has been renamed to Virtual Application Network (VAN) Manager to more accurately
reflect 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-3313

Published: December 2012
Edition: 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.
Contents
1 ConnectionRM...........................................................................................5
Functional modules...................................................................................................................5
Network diagram.....................................................................................................................5
Application environments...........................................................................................................6
VEB environment features...........................................................................................................7
EVB environment features...........................................................................................................7
Managing network configuration migration in ConnectionRM ........................................................7
Prerequisites........................................................................................................................7
Configuring ConnectionRM...................................................................................................8
Configuring the edge switches and physical servers..................................................................8
Configuring edge switches in the EVB environment..............................................................8
In the EVB environment....................................................................................................8
2 ConnectionRM home page widget................................................................9

Adding the ConnectionRM view TopN widget to the home page..................................................9
Setting the ConnectionRM View TopN widget............................................................................9
Setting TopN.......................................................................................................................9
Setting the refresh interval ..................................................................................................10
Refreshing the ConnectionRM View TopN widget.................................................................10
Deleting the ConnectionRM View TopN widget ..................................................................10
Viewing the ConnectionRM View TopN widget .......................................................................10
ACL utilization...................................................................................................................11
Connection utilization ........................................................................................................11
3 Edge switch management..........................................................................13

Viewing an edge switch list .....................................................................................................13
Querying an edge switch........................................................................................................14
Adding an edge switch...........................................................................................................15
Selecting devices using the Advanced Query option...............................................................15
Setting ACL number range.......................................................................................................16
Viewing the migration history of VMs controlled by the edge switch .............................................17
Deleting an edge switch .........................................................................................................17
Example for adding an edge switch.....................................................................................17
4 VSI type management...............................................................................20

Viewing the VSI Type List ........................................................................................................20
Querying VSI type .................................................................................................................21
Viewing VSI type details..........................................................................................................22
Adding a VSI type..................................................................................................................22
Service units for customizing VSI type...................................................................................22
Example of adding a VSI type ............................................................................................24
Modifying a VSI type..............................................................................................................26
Deleting a VSI type.................................................................................................................27
Releasing a version for a VSI type.............................................................................................27
Deleting a version of a VSI type................................................................................................27
5 Network management..............................................................................29
ConnectionRM's Network........................................................................................................29
Viewing network list ...............................................................................................................29
Viewing network details ..........................................................................................................30
Adding a network...................................................................................................................31
Network planning .............................................................................................................31
Example of adding a network..............................................................................................31
Contents
Copying the configuration of a network.....................................................................................32

Modifying a network...............................................................................................................33
Deleting a network.................................................................................................................33
6 Connection management...........................................................................34
Viewing the connection list ......................................................................................................34
Querying connection..............................................................................................................35
Adding a connection..............................................................................................................35
Modifying a connection .........................................................................................................36
Deploying a connection...........................................................................................................36
Undeploying a connection.......................................................................................................37
Deleting a connection ............................................................................................................37
7 Life cycle reports.......................................................................................38

Introduction to life cycle reports................................................................................................38
Viewing historical record of VM migration via list view.................................................................38
Viewing historical record of VM migration via icon view..............................................................39
Querying historical migration records .......................................................................................40
Viewing operation list..............................................................................................................41
Redeploying an online or offline process ...................................................................................42
Querying operations...............................................................................................................42
8 Managing vManager plug-ins....................................................................43

Registering the vCenter plug-in.................................................................................................43
Modifying a vCenter plug-in entry ............................................................................................43
Deleting a plug-in entry ..........................................................................................................44
Managing connections on a vCenter server ..............................................................................44
9 Configuration example..............................................................................46
Network requirements.............................................................................................................46
Configuration prerequisites......................................................................................................46
Configuring EVB bridges.........................................................................................................46
Recommended configuration procedure................................................................................47
Configuring EVB Bridge A...................................................................................................47
Configuring EVB Bridge B ..................................................................................................47
Configuring ConnectionRM .....................................................................................................47
Verifying the configuration.......................................................................................................49
How does ConnectionRM manage configuration migration?....................................................49
10 Support and other resources.....................................................................50

Contacting HP........................................................................................................................50
Subscription service ...............................................................................................................50
Related information.................................................................................................................50
Documents........................................................................................................................50
Websites..........................................................................................................................50
Typographic conventions.........................................................................................................51
Product feedback....................................................................................................................51
11 Documentation feedback..........................................................................52
Glossary....................................................................................................53
Index.........................................................................................................55
Contents
1 ConnectionRM
The ConnectionRM service component and IMC Virtual Network Management (VNM) are typically
used together to meet the growing demand on virtual network management. VNM manages
VMware ESX/ESXi and Microsoft Hyper-V virtual networks (see HP IMC Base Platform Administrator
Guide), and ConnectionRM manages dynamic migration of VM network configuration and VM
traffic.
ConnectionRM is an efficient solution for physical network configuration migration. It monitors VM
startup, shutdown, and migration processes, and distributes physical network configuration to VMs
according to their latest access locations. It provides seamless collaboration between physical and
virtual networks. When a VM migrates, ConnectionRM automatically performs network configuration
migration for the VM and eliminates the need for a network administrator to reconfigure the access
switch for the VM.
Functional modules
ConnectionRM comprises the following functional modules:
Edge Switch listManages all switches that directly connect to physical servers. ConnectionRM
performs dynamic network configuration migration only for VMs that access the network
through 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 operator
can 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 of

ConnectionRM, the connection implements dynamic migration of VM network configuration.
When a VM is migrated, ConnectionRM removes the VM network configuration by deleting
the deployed connection from the source switch, and deploys the network configuration to
the destination switch by deploying the connection.
Life Cycle ReportDisplays the VM migration history and detailed online/offline operations
performed by ConnectionRM.
Plug-In ManagementA vManager plug-in integrates connection management into vManager

servers after it is registered for those servers. With the connection management function,
vManager administrators can add, modify, delete, deploy, and undeploy connections on the
vManager servers.
Network diagram
As shown in Figure 1, an enterprise has four physical servers, on each of which one or more VMs
are created. VMs access the enterprise network through Switch A or Switch B. IMC VNM manages
the virtual networks, and ConnectionRM provides dynamic network configuration migration for
VMs.
Functional modules
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 migration

for VM A by deleting its network configuration from Switch B and then deploying its network
configuration to Switch A.
Application environments
ConnectionRM implementation is based on 802.1Qbg. ConnectionRM can be applied to a Virtual
Ethernet Bridge (VEB) environment or an Edge Virtual Bridge (EVB) environment, depending on
VM access methods.
In ConnectionRM, a VEB environment is based on the VEB solution defined in 802.1Qbg, and an
EVB environment is based on Virtual Ethernet Port Aggregation (VEPA) or multi-channel VEPA
solution defined in 802.1Qbg. VEB and EVB environments differ in the following aspects:
They require different conditions for connection deploy or undeploy operations in

ConnectionRM.
A VEB environment supports manual deploy and undeploy operations of connections, but an
EVB environment does not.
They have different configuration requirements for physical servers and edge switches. For
more information, see Configuring the edge switches and physical servers.
ConnectionRM
VEB environment features

In the VEB environment, ConnectionRM deploys or undeploys connections in any of the following
cases:
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 the

deployed connection from the source switch, and deploys the network configuration to the
destination 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 Windows
Hypver-V, ConnectionRM must work with the VNM agent plug-in and LLDP plug-in. For information
about installing the plug-ins, see HP Intelligent Management Center Installation Guide.
ConnectionRM mostly applies to the VEB environment.
EVB environment features

In the EVB environment, ConnectionRM deploys or undeploys connections in any of the following
cases:
When a VM starts, ConnectionRM deploys the predefined connection for the VM after receiving
a request from the edge switch.
When a VM stops, ConnectionRM undeploys the connection for the VM after receiving a
request from the edge switch.
When a VM migrates, ConnectionRM removes the VM network configuration by deleting the

deployed connection from the source switch, and deploys the network configuration to the
destination switch by deploying the connection.
Edge switches in the EVB environment must support the EVB feature, and you must configure the
edge switches before configuring ConnectionRM. In addition, virtualization software must support
802.1Qbg.
Managing network configuration migration in ConnectionRM

Described here is how to configure the ConnectionRM component, edge switches, and physical
servers to manage physical network configuration migration in ConnectionRM.
Prerequisites
The 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 deployed
on the IMC master server.
2.
Add edge switches and physical servers to IMC for management. For more information, see
information on resource management in HP IMC Platform Administrator Guide.
After you configure SOAP parameters for physical servers managed by IMC, VNM automatically
obtains information about vSwitches and VMs of the server.
VNM cannot obtain IP addresses of Windows Hyper-V VMs, and you must add their IP addresses
to IMC and create IP/MAC bindings for VMs in IMC Terminal Access.
VEB environment features
Configuring ConnectionRM
To 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 delete
connections on the vCenter servers. For more information, see Registering the vCenter plug-in.
Configuring the edge switches and physical servers

For ConnectionRM to implement dynamic migration of VM network configuration, you must configure
the edge switch and physical server.
Configuring edge switches in the EVB environment

Configure the interface connecting an edge switch to a physical server as a trunk port. When a
vSwitch uses multiple NICs to the same edge switch, it combines interfaces on the edge switch into
one aggregate interface.
In this environment, no configuration is required on the physical server.
In the EVB environment

In the EVB environment, configure edge switches as follows:
Configure the interface connecting an edge switch to a physical server as a trunk port, and
enable 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 IMC
master server.
Enable EVB on the interface.
Configure the VDP keepalive timer.
For information on configuring a physical server, see the server configuration document.
ConnectionRM
2 ConnectionRM home page widget

When ConnectionRM is deployed, operators can add the ConnectionRM View TopN widget to
the IMC home page to view ACL utilization of each edge switch and connection utilization of each
network 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 page

To 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
the top.
4.
on the left and function links on
Select the space you want to custom, and click the Edit icon
page.
on the upper right of the
By default, the Welcome space is selected.

5.
6.
Click the Resource tab.

Click the ConnectionRM View TopN widget.
7.
Click the Add icon

You can add only one ConnectionRM View TopN widget to the current space. When the
current space already contains the ConnectionRM View TopN widget, you cannot add the
widget again.
8.
Click OK.
The ConnectionRM View TopN widget appears in the space.
Setting the ConnectionRM View TopN widget

To 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
the top.
on the left and function links on
Setting TopN
To set TopN:
Adding the ConnectionRM view TopN widget to the home page
1.
2.
Click the Set icon

Select Setting.
on the upper right of the ConnectionRM View TopN widget.
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 largest
total connection numbers.
Setting the refresh interval

To set the refresh interval:
1.
2.
3.
Click the Set icon

on the upper right of the ConnectionRM View TopN widget.
Select Refresh interval. The Refresh interval window appears.
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 No
Refresh option disables automatic refreshing on the ConnectionRM View TopN widget. In
this 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
right of the widget.
on the upper
Deleting the ConnectionRM View TopN widget

To 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 widget

The 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 utilization
The ACL utilization pie chart lies on the upper left of the widget. It displays the total number of
ACLs supported and the remaining number of configurable ACLs on each edge switch that
ConnectionRM 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 total
number of ACLs that the operator specifies for the edge switch. A larger slice represents an edge
switch that is configured to support more ACLs. The slice colors randomly change each time the
ConnectionRM View TopN widget refreshes.
The pie chart comprises an inner circular area and an outer circular area. When placing the cursor
over a slice in the inner circular area, you can view the label of the edge switch and the total
number of ACLs specified for the switch. When placing the cursor over a slice in the outer circular
area, you can view the remaining ACLs on the switch in number and percentage.
Connection utilization
As in Figure 3, a line and bar chart is located on the lower part of the widget to show connection
utilization. Each bar represents the connection utilization of a network. ConnectionRM counts
numbers of the following network connection types: undeployed, deployed, and remained. It also
counts VSI types and displays the network VLAN ID. The vertical axis represents the number of
connections, 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:
12
The number on each colored bar represents the number of a specific type of connections on
the network. Place the cursor over a colored area to view the percentage of connections and
the VLAN ID of the network.
Place the cursor over the VSI node

ID of a specific network.
ConnectionRM home page widget
on a bar to view the number of VSI types and the VLAN
3 Edge switch management

The following topics provide some functions on the edge switch management including how to
manage the edge switch in the ConnectionRM.
The edge switches connect to the end-user local area networks (LANs) or to the Internet service
provider (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 into
enterprise or service provider core networks. Edge switches are also referred to as access nodes
or service nodes.
In IMC platform, the edge switch which connects with the physical server can manage the VSI type
of 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), and
prioritize access to VM (all clients). When a virtual machine accesses the network on the edge
switch, the vNIC, and VSI type of the virtual machine can be bound.
Viewing an edge switch list

The Edge Switch list page provides the basic information of edge switch. In this page, you can
view 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 seven
levels:
Critical
Major
Minor
Warning
Normal
Unknown
Unmanaged
For 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 VMs
inside 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 the
edge switch. When the number of connection is not 0, move the pointer to the figure, the
window with the VM summary information pops up. The information includes the vNIC
of 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 deployed
on 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, and
the name of the physical server which VM locates.
Service Units: Indicates a set of the control commands integrated by VSI type. You can
deploy the service units on a specified edge switch to control the VMs running on the
physical 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 real
statistics figure for the current edge switch. For more information, see Service units for
customizing 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 not
support this function, such as HP E series equipment. For more information, see Setting
ACL 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 the Migration history icon

to view all of the migration
history of the VMs which are connected to the current edge switch. In addition, there is
an interface to enter the Life Cycle Report page. For more information, see Life cycle
reports.
Deleting an edge switchClick the Delete icon

switch list.
to delete an edge switch from the edge
Querying an edge switch

In the edge switch list, ConnectionRM provides a Query capability that enables you to search for
edge switches by device label.
To query edge switch:
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 the
switch label or the switch IP address.
5.
6.
14
Click Query. The edge switches that meet your search criteria are listed in the Edge Switch
List page.
Click Reset to clear the query condition, and it shows all the edge switches with default values
in the list.
Edge switch management
Adding an edge switch

Adding 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 the
VMs.
To add an edge switch into the edge switch list:
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 navigation
tree. 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 Add
selected icon
6.
7.
8.
9.
to add them to the selected devices list.
To remove one or more devices, select them, and click the Remove selected icon .
Confirm that the devices you have found have been added by reviewing the Selected Devices
list.
Click OK.
Confirm that the devices now appear in the Devices List field.
Selecting devices using the Advanced Query option

You 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:
Device IP
Enter the IP address you want to query for. Click the

Exact Query checkbox if you want IMC to search for
the exact IP address you have entered. Leave the
Exact Query box unchecked if you want IMC to match
only a certain portion of the IP address.
Device IP List
Configure multiple device IP addresses to be

searched. Click the Select device IP list configuration
icon
. Then, the Device IP List Configuration
window appears. Enter one or multiple device IP
addresses in the Input Device IP field (if you enter
multiple IP addresses, enter one IP address on each
line), and then click Add to add the entered IP
addresses to the Device IP List field below. Repeat
the steps above to add all device IP addresses to be
searched.
To delete an IP address in the Device IP List field,
select the IP address, and then click Delete. Click OK
to complete the operation. Make sure that the device
IP 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
2.
3.
4.
Device Label
Enter the device name for the devices you want to

add. IMC supports fuzzy matching for device labels.
Therefore, you can enter the entire device label for
the device you want to locate, or you can enter just
a portion of it. IMC displays all matches that contain
the portion you enter.
Device Status
Select device status from the Device Status list.
Device Category
Select a device category form the Device Category

list.
Device Series
Select a device series from the Device Series list.
Contact
Enter the contact name information by which you

want to search. IMC supports fuzzy matching for this
field. Therefore, you can enter a partial string for the
contact or the complete string for the contact.
Location
Enter the location information by which you want to

search. IMC supports fuzzy matching for this field.
Therefore, you can enter a partial string for location
or the complete string for location.
Device Reachability
Select device reachability status from the Device

Reachability list.
b.
Click Query to begin your search. The results of your search appear in the Devices Found
field.
c.
Highlight the devices you want to select, and click the Add selected icon
to the selected devices list.
To remove one or more devices, select them, and click the Remove selected icon
Confirm that the devices you have found have been added.
Click OK.
to add them
.
Setting ACL number range

You can use the ACL number range setting function to make a plan on ACL resource. For more
information 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 view
the default ACL number range before you do the operation of setting ACL number range. After
you complete the operation of setting the ACL number range, the new ACL number range will
appear in the Edge Switch List page. When the switch is added as the edge switch, ConnectionRM
will obtain the default ACL number range automatically according to the device type.
To set ACL number range:
1. Click Resource > ConnectionRM
3.
4.
5.
16
Click the ACL number range icon

for the target edge switch to enter the page for configuring
an ACL number range.
Type an ACL number range in the ACL number range column.
Click OK.
The ACL number range varies with device vendors.
Viewing the migration history of VMs controlled by the edge switch

To view the migration history (before and after) of VMs relevant to the current edge switch:
3.
Click the Migration history icon

with the edge switch.
to view the migration history of the VMs which connect
For more information, see Life cycle reports.
Deleting an edge switch

After the delete operation, the edge switch does not appear in the list, and it is deleted from the
ConnectionRM module. When the edge switch is used by a connection, you cannot delete this
edge switch.
To delete an edge switch:
3.
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 edge
switch, make sure the VMs relevant to the current edge switch are not bound with VSI type and
vNIC.
Example for adding an edge switch

Lily Technology Company is a game development company. It has two physical servers (server A
and server B). The free space is not enough in server A, and the configuration from server A needs
to be migrated to server B. In addition, you need to set ACL number range in switch B to control
the 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:

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.
e.
Highlight the switch A from the Devices Found list, and click the
to add it to the selected
devices list.
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:

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.
e.
f.
18
Highlight the switch B, and click the Add selected icon

to add it to the selected devices
list.
Confirm that the Switch B devices you discovered have been added.
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:

3.
4.
5.
Click the ACL number range icon

for MSTP1_xiaopang4 to enter the ACL number range
page.
The default H3C ACL number range is 3000-3999. Type 3100-3500 in the ACL number
range column.
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 management

A VSI type integrates a set of service unit settings for administrators to perform the Quality of
Service (QoS) management and access control for VM. With ConnectionRM, you can deploy a
VSI type on a specified edge switch to control the VM running on the physical servers that connect
to 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 the
VM.
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 the
VM. This priority setting takes precedence over the priority set in Prioritize Access to VM (All
Clients).
Prioritize Access to VM (All Clients)Defines the default priority for packets sent from all clients
to the VM.
ConnectionRM enables you to use the service units to customize a VSI type. You can then deploy
the VSI type to control the bandwidth, access authority, and packet priority for the VM. To customize
a VSI type that meets your VM management requirements, you can select one or more service
units, 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 VSI
type to combine with different VM as required. When you customize a VSI type, you can modify
a VSI type that has similar service unit configurations, and then release a new version for the
updated VSI type. This helps VSI type classification and management, and also increases your
efficiency in configuring VSI types for VM that have similar service requirements.
As the physical network configuration, VSI type can perform QoS management and access control
for the VM. During a VM migration, in order for the VSI type to automatically migrate with the
corresponding VM, the VSI type needs to be bound to the vNIC of the target VM through connection
configurations. For more information, see Connection management.
Viewing the VSI Type List

The VSI type list displays VSI types and their versions in a tree hierarchy that displays a VSI type
as parent and its versions as children. In the list, you can view the status, the network to which the
VSI 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 view
the following information:
20
NameIndicates the name of the VSI type.
StatusDisplays version information. Move the pointer to the Status icon

. The Version
Information menu shows the information of the top 10 versions, including the version name
VSI type management
and number of connections to which the version is bound. This field also displays the status
of VSI type versions, which includes:
BoundWhen a version is bound to a vNIC of a VM, the Bound icon

Status field of the version.
Not BoundWhen a version is not bound to any vNIC of a VM, the Not Bound icon
displays in the Status field of the version.
displays in the
NetworkDisplays network information. Move the pointer to the Network icon

, and the
Network menu shows the information of the network to which you assigned the VSI type. This
information includes the network name and VLAN ID of the network resource uses. For more
information, 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 click
the icon, you release a new version for the VSI type. For the versions of a VSI type, this field
displays the released time of the version.
OperationIndicates the operations you can perform for the VSI type, including:
Modify a VSI typeClick the Modify icon

in the operation field of a VSI type to modify
the 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 delete
the 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 the
specified version. For more information, see Deleting a version of a VSI type.
Querying VSI type

ConnectionRM provides a Query capability that enables you to search for VSI types or VSI type
versions by name, status, and other parameters.
To query for a VSI type:
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 versions
that are bound to vNICs. Not Bound indicates querying the VSI type versions that are not
bound 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 want
to query. For example, if you input 10 in this field, the system only displays the latest
released 10 versions of the VSI types that meet your search criteria.
Querying VSI type
21
5.
Release Time From/ToClick the Data and Time icon

VSI type version is released.
DescriptionInput one or more keywords of the VSI type description.
to select a period in which the
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 details

The VSI Type Details page provides the basic information, the network to which the VSI type is
assigned, and the service unit configurations of the VSI type. In this page, you can view the details
of VSI types and the released versions.
To view the VSI type details:
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 name
and 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 to
customize the VSI type. For more information, see Table 1.
Adding a VSI type

A VSI type can integrate multiple service unit configurations to perform the QoS management and
access control for VM. Information included here introduces the service units you can use to
customize your own VSI type, and provides a typical example for how to add a VSI type.
Service units for customizing VSI type

Table 1 lists all service units and the related parameters you can use to customize a VSI type.
Table 1 Service unit description
22
Service Unit
Description
Parameter settings
Bandwidth Control
Specify the guaranteed

bandwidth for traffic between
client and the VM, such as
committed information rate
Client IPSpecify an IP segment for the specific clients by

setting the Client IP and Wildcard Mask parameters. The
ConnectionRM controls the bandwidth for the traffic between
VSI type management
Table 1 Service unit description (continued)

Service Unit
Description
(CIR) and peak information
rate (PIR).
Parameter settings
the VM and the clients you specify here. Input a single IP
address or IP segment with standard IPv4 format.
Wildcard MaskInput a wildcard mask to specify the IP
segment of the specific clients.
Filtering DirectionSpecify the direction of the packets to
which you want to perform bandwidth control. INBOUND
indicates the packets sent from the client to the VM.
OUTBOUND indicates the packets sent from the VM to the
client. You also can select BOTH to control the packets of both
directions.
CIR (kbps)Specify the average rate allowed by the target
VM to transmit or forward packets. In the practical
environment, HP recommends that you control the traffic
bandwidth to be less than the CIR value.
PIR (kbps)Specify the maximum rate allowed by the target
VM to transmit or forward packets. If the traffic bandwidth
exceeds the PIR value, the system discards the redundant
packets to control the bandwidth.
VM Access Control
Allow specific clients to access Client IPSpecify an IP segment for the specific clients by
the VM.
setting the Client IP and Wildcard Mask parameters. Only
the clients you specify here are allowed to access the target
VM. Input a single IP address or IP segment with standard
IPv4 format.
which you want to perform VM access control. INBOUND
indicates the packets sent from the client to the VM.
OUTBOUND indicates the packets sent from the VM to the
client. You also can select BOTH to control the packets of both
directions.
Prioritize Access to
VM (Specific
Clients)
Prioritize packets from specific Client IPSpecify an IP segment for the specific clients by
clients to the VM. This priority
setting the Client IP and Wildcard Mask parameters. All the
setting takes precedence over
packets sent from the defined IP address to the target VM are
the priority setting for all clients
prioritized according to the priority rules defined in this service
to the VM.
unit. Input a single IP address or IP segment with standard
IPv4 format.
which you want to set priority. INBOUND indicates the
packets sent from the client to the VM. OUTBOUND indicates
the packets sent from the VM to the client. You also can select
BOTH to control the packets of both directions.
Priority SettingIndicate the protocol of the packets for which
you want to set the priority.
Priority ValueSpecify a priority level for the packets.
Prioritize Access to
VM (All Clients)
Specify the default priority for

packets from all clients to the
VM.

which you want to set priority. INBOUND indicates the
packets sent from the client to the VM. OUTBOUND indicates
the packets sent from the VM to the client. You also can select
BOTH to control the packets of both directions.
Priority SettingIndicate the protocol of the packets for which
you 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 the
service units: Prioritize Access to VM (Specific Clients) or Prioritize Access to VM (All Clients) to set
the 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 VM
management requirements. Also, you can configure multiple sets of parameters for the service units
you select, and each set can be added as a service rule. When you configure multiple service
rules, ensure that every service rule contains the same service units. For example, you have selected
the Bandwidth Control and VM Access Control service units to set a service rule. When you want
to add a new service rule for the VSI type, you only can use the two service units to create the new
service rule. When you use a different set of service units to create a new service rule, the existing
service rules are removed.
Example of adding a VSI type

As a network administrator, you are assigned to use ConnectionRM to customize a VSI type for
the VM used by the Research and Development (R&D) department and the Testing lab of the
company. For information security and resource optimization, the VM have to meet the following
requirements:
The guaranteed CIR and PIR of the bandwidth for the traffic between the VM and clients are
1024 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 department
to the VM. Set the priority of the packets sent from the Testing lab to be 3, and the priority of
the packets sent from the R&D department to be 5.
To add a VSI type:

3. Click Add to open the Add VSI Type page.
4. Complete the basic information of the VSI type as follows:
5.
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.
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. The
parameters 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.
c.
d.
e.
f.
24
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.
Select INBOUND in the Filtering Direction list.
For the bandwidth control, set the CIR (kbps) parameter to be 1024, and set the PIR (kbps)
parameter to be 2048.
Select DSCP from the Priority Setting list, and input 5 in the Priority Value field.
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.
VSI type management
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 Parameter
Settings pane.
b. To specify the IP segment of the Testing lab, set the Client IP to be 192.128.200.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 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 service
rule, and then click Delete.
7.
To save the VSI type configuration, click Save. The VSI type appears in the VSI type list. When
you want to release a version for the VSI type, click Save and Release. The VSI type and the
released version appear in the VSI type list. For more information, see Releasing a version
for a VSI type.
After configuring a VSI type, you can release versions for it, which can be used to define a
connection. For more information, see Connection management.
Modifying a VSI type

In the Modify VSI Type page, you can modify the configuration of a VSI type. When you modify
a VSI type, you cannot modify the name of the VSI type or the network to which you assign the
VSI 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 function
also 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 you
want to customize a VSI type version, you need to first customize the VSI type, and then release
a new version for the VSI type.
To modify a VSI type:
3.
26
Click the Modify icon

appears.
VSI type management
of the VSI type you want to modify. The Modify VSI Type page
4.
5.
You can modify the basic information and service unit configurations in the Modify VSI Type
page. For more information, see Adding a VSI type.
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 released
version displays in the VSI type list. For more information, see Releasing a version for a VSI type.
Deleting a VSI type

Deleting a VSI type deletes the VSI type, as well as all the released versions of the VSI type.
To delete a VSI type:
3.

dialog box opens.
in the Operation field of the VSI type you want to delete. A verification
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. In
this scenario, if you want to delete the VSI type, you must first unbind the versions. For more
information, 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 type

In ConnectionRM, after you modify a VSI type, you can release a version for the updated VSI type
to retain the changes. This task facilitates customizing VSI types for the VM that have similar service
requirements. 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 type

When you add a new VSI type, click Save and Release after completing the VSI type parameters
to release a version for the new VSI type.
Release a version when modifying a VSI type

When you modify a new VSI type, click Save and Release after modifying the VSI type
parameters 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 field
of the target VSI type. A new version displays under the VSI type.
Deleting a version of a VSI type

Before deleting a version of a VSI type, make sure that the version is not bound to any vNIC of
VM. In ConnectionRM, if a version of a VSI type is bound to a vNIC of a VM, you cannot delete
the version.
To delete a version of a VSI type:
3.

dialog box opens.
in the Operation field of the version you want to delete. A verification
Deleting a VSI type
27
NOTE: If the version is bound to the vNICs of VM, the Delete icon
does not display in
the Operation field. In this scenario, if you want to delete the version, you must firstly unbind
it. For more information, see Undeploying a connection.
4.
28
Click OK to delete the version. The version you delete is removed from the VSI Type List.
VSI type management
5 Network management
As an advanced data exchange technology, VLAN allows a network administrator to logically
segment a LAN into different broadcast domains. Each VLAN includes a group of workstations
that have the same or similar application requirements. The packets generated by a workstation
in a VLAN can only be transmitted through the network resources (ports) within the VLAN, which
helps traffic and bandwidth control, simplifies the network management, and improves the network
security.
ConnectionRM's Network
The ConnectionRM provides a management facility, Network, for assigning ports for transferring
the traffic between VM and clients, and the VSI types you can deploy for controlling the traffic
between VM and clients. In the ConnectionRM, a network can indicate a port through specifying
the VLAN ID of the port in the network. Each network can only consume one VLAN ID. When
creating a connection, you need to assign a network to the connection. This enables the VM
specified in the connection to use the port to send or receive packets to and from the clients. In
this way, you can specify a network for the VM that has the same or similar application requirements
to improve the management efficiency, or assign the network according to your network plan and
the practical requirements. For more information, see Connection management.
Another important function of the network management is VSI type assignment. With network
management, you can assign one or more VSI types to a specified network, which allows the
administrator to deploy the specified VSI types for managing the VM that can use the network to
communicate with the clients.
In addition, when creating a network, you can authorize one or more operators or operator groups
to manage the VSI types assigned to the network. In the ConnectionRM, to view and manage the
VSI 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 an
operator or operator group. You can assign this privilege when you add an operator group in the
IMC base platform. For more information, see HP IMC Base Platform Administrator Guide.
Viewing network list

In the network list, you can view the created networks, and the related information, such as the
VLAN ID, the VSI types that the network can manage, and other details of the network.
To view the VSI type list:
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:
Network Name
Indicates the name of the network.
VLAN ID
Indicates the VLAN ID of the port that is assigned to the network. Each network can only consume
one VLAN ID. When you select a network for a connection, the VM specified in the connection
can communicate with the clients through the corresponding ports.
Max. Connections
Indicates the maximum number of the connections allowed to be created in the network. When
creating a connection, you should specify the network that the connection belongs to. When the
number of the connections in the specified network reaches the value defined in this field, you
cannot create any new connections in the specified network. For more information, see Adding
a connection.
Description
Indicates the description of the network.
ConnectionRM's Network
29
Bandwidth Control
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:
Green barIndicates at least one connection is specified the guaranteed bandwidth in the
network. Move the pointer to the bar to view the number of the connections that are specified
the guaranteed bandwidth, and the maximum PIR value specified for the connections. In
ConnectionRM, the bandwidth control of a connection is achieved by configuring the Bandwidth
Control service unit for the VSI types that the connection used.
Grey barIndicates at least one connection is not specified the guaranteed bandwidth in the
network. Move the pointer to the bar to view the number of the connections that are not
specified the guaranteed bandwidth.
BlankWhen there is no connection in the network, this field is left blank.
Connection
Indicates the number of the connections in the network. This field uses the following bars to
indicate the connections of different status:
Green barMove the pointer to the green bar to view the number of the connections that
have been deployed in the network.
Red barMove the pointer to the red bar to view the number of the created connections that
have not been deployed in the network
Grey barMove the pointer to the grey bar to view the number of the remaining connections
that you can create in the network.
For more information, see Adding a VSI type and Adding a connection.
Copy
Modify
Delete
Click the Copy icon

to copy the configurations of the specified network, which can be a
template for you to create a new network. For more information, see Copying the configuration
of a network.
to modify the configurations of the specified network. For more
information, see Modifying a network.
to delete a network. For more information, see Deleting a network.
Viewing network details

The 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:
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:
30
Name
Indicates the name of the network.
VLAN ID
Indicates the VLAN ID of the port that is assigned to the network. Each network can only consume
one VLAN ID. When you select a network for a connection, the VM specified in the connection
can communicate with the clients through the corresponding ports.
Max. Connections
Indicates the maximum number of the connections allowed to be created in the network. When
creating a connection, you should specify the network that the connection belongs to. When the
number of the connections in the specified network reaches the value defined in this field, you
cannot create any new connections in the specified network.
Description
Indicates the description of the network.
VSI Type Settings
Indicates the VSI types that are assigned to the network.
Operator List
Indicates the operators or operator groups that have the privileges to manage the VSI types that
are assigned to the network. In ConnectionRM, to view and manage the VSI types, you must log
on to the IMC base platform as an authorized operator.
Network management
Adding a network
Before 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 and
configuring a network.
Network planning
In the ConnectionRM, a network is a facility for assigning ports for transferring the traffic between
VM and clients, as well as the VSI types you can deploy for controlling the traffic between VM and
clients. Therefore, the network configuration is based on the network planning in the practical
environment. As a network administrator, you should first plan the physical network environment,
which includes creating VLANs according to the application requirements, assigning network
resources (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 to
the VLANs configured in the practical environment. By assigning a network to a connection, the
VM 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. When
creating a connection, when you select a network, you can only use the VSI types that are assigned
to the network to control the traffic between VM and clients.
Another important planning step is to decide which operators or operator groups have the privileges
to manage the VSI types that are assigned to a network, which helps the specialization of
management authorities.
Example of adding a network

As a network administrator, you are assigned to use ConnectionRM to customize a network for a
VLAN (VLAN ID is 2). The maximum number of connections is 10. The network includes the following
VSI types:
VSI Type A
VSI Type B
In addition, only the operators in the administrator group and maintainer group can manage the
two VSI types.
To add a network:
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 you
must input the VLAN ID that applies to a trunk port of a switch. In this example, input 2
in the VLAN ID field.
Max. ConnectionsSpecify the maximum number of the connections allowed to created

in 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
6.
then click the Add Selection icon

. The VSI type A displays in the Selected VSI Type list
box.
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
selected VSI types, click the Remove All Selected icon
7.
. To remove all the
In the Operator List pane, click the checkbox of the operators or operator groups you want
to authorize to manage the network. The administrator group has been authorized full
permissions in the IMC base platform and all added-on modules. This group is authorized by
default. In this example, click the checkbox of the maintainer group to authorize the operators
in this group to manage the VSI types that are assigned to the network, as shown in Network
configuration example.
Figure 9 Network configuration example
NOTE: Click the Expand all icon

to view the operators in all operator groups. Click the
Collapse all icon
to only view the operator groups.
8.
Click OK. A message displays to show the network is added successfully. The network you
configure displays in the Network List.
Copying the configuration of a network

When creating a new network, you can copy the configuration of a similar network, which can
be used as a template. In this way, you can quickly create a new network based on the copied
configuration.
To copy the configuration of a network:
32
Network management
1.
2.
From the main IMC menu, click Resource > ConnectionRM.

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 Network
page and the parameter settings of the network you copied displays.
Modify the name of the network.
Modify the other parameters of the network as required. For more information, see Example
of adding a network.
Click OK. A message displays to show the network is added successfully.
4.
5.
6.
The network you configure displays in the Network List.
Modifying a network
The ConnectionRM provides you with the ability to modify the configuration of a network. You can
modify 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:
3.
4.
5.

of the network you want to modify to open the Modify Network
page.
Modify the parameters of the network as required. For more information, see Example of
adding a network.
Click OK.
Deleting a network
If there is a connection that belongs to the network you want to delete, which means that at least
one of the VSI type versions in the network is bound to vNICs, you cannot delete the network.
To delete a network:
3.
4.

of the network you want to delete. A verification dialog box opens.
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 following
message is displayed: Please create a task to delete the connection because the network contains
a 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 management
The Connection management function allows for the binding of a specific VSI Type version into
the target vNIC of the virtual machine.
When the virtual machine starts, stops, or migrates, ConnectionRM is able to deploy the connection
bound with a VSI Type to the target virtual machine. With this function the administrator can deploy
the VSI Type information to the edge switch automatically. Deploying a connection in the VM sends
a specific VSI Type configuration to the target edge switch. ConnectionRM does not support
migration when the MAC address of the vNIC has changed. When the virtual machines vNIC
changes, 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 connection
automatically:
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 list

The connection list displays the detail information of each connection. In the list, you can check
many current parameter values, and you also can check their details by entering the corresponding
page.
To view the connection list:
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:
34
Status
Click to open the Operation List page where you can check the operation history details. The
Green icon indicates that the connection has been deployed; the red one indicates that the
connection is not deployed.
Name
Display the connection name.
Description
Display the connection description.
vNIC IP
Display the target vNIC IP of connection.
vNIC
Display the target vNIC MAC address. Click the MAC address of the target vNIC to enter in
the related Virtual Machine page. You can check the VM detail information in this page. In
ConnectionRM, use a specific vNIC to represent a VM. If the vNIC changed, the VM makes a
change accordingly.
VM
Display the target VM name and IP address.
Connection management
Physical Server
Display the physical server name and IP address. Click the target physical server name to enter
in the Device Details page for checking details. For more information, see IMC Base Platform
Administrator Guide.
Network
Display the network name that the connection used.
VSI Type
Display the target VSI Type version. Click the target VSI Type to open the related VSI Type
Details window. For more information, see Viewing VSI type details.
Access Switch
Display the device label and IP address of the target switch. Click the target access switch to
open the Resource page for details checking
Access Interface
Display the interface of the switch that used to communicate with the physical server.
Operation
Include four user operations as follows:

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 connection
ConnectionRM provides a Query capability that enables you to search for connection by name,
vNIC IP, and other parameters.
To query the connection:
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 connection
ConnectionRM allows you to add a new connection between a specific VSI Type and a vNIC of
the virtual machine. When you add a new connection, ConnectionRM judges if the target switch
is an edge switch, if it is not, the adding process cannot be successful.
To add a new connection:
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 click
Select to open the VM list page. All available VMs are displayed in this page; you can
check the VM detail information, such as VM Name, Status, IP, and Physical Server. Then
select 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 can
refresh the VM IP address automatically.
5.
NetworkSelect a target network.
VSI TypeSelect a target VSI Type from the list. If you have assigned a network for this
connection, only the VSI Type that belongs to this network appears in the list.
VSI Type VersionSelect a target VSI Type Version.
DescriptionDescribe the connection.
Click OK.
NOTE: You can add a new connection in the vCenter with the Plug-In Management function. It
will 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 is
added in vCenter or ConnectionRM.
Modifying a connection
ConnectionRM allows you to modify the parameters of an existed connection. After you modify a
connection, it is necessary to deploy this connection into the switch. If the connection has been
deployed, it is unavailable to modify the configurations.
To modify a connection:
3.
4.
5.

under the Operation column of the target connection item to open
the Modify Connection page.
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.
Click OK.
Deploying a connection
After you add a new connection successfully, you need to create a task of deploying this new
connection to the target switch. Then the deploy details are sent back to you, and you can check
them in the Operation List. If all of your configurations are not deployed successfully, ConnectionRM
provides the redeploy function to redeploy the configurations manually.
A VEB environment as an example to describe the process of how to deploy a successful connection
in the ConnectionRM. To an EVB environment, you do not have to deploy the connection to the
switch. After you finish the connection adding procedure, ConnectionRM does this for you
automatically. 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.
2.
3.
4.
5.
Click Resource > ConnectionRM.

In the navigation tree, click Connection to open the Connection List page.
Click Add to open the Add Connection page.
Complete the parameters. For more information, see Adding a connection.
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.
Wait a moment for the Operation List page to open.
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 following
steps.
7.
8.
a.
b.
c.
In the Operation List page, click the Details icon to open the Operation Details page.
In the Operation Details page, check the failure reason.
Check your environment according to the failure reason.
d.
Click the Deploy icon
to redeploy the configurations of the connection successfully.
Undeploying a connection
In a VEB environment, when the virtual machine migrates, you need to eliminate the former
connection configurations in the switch to release the port which is occupied by the former
connection. 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:
3.
Click the Undeploy icon
to undeploy the connection.
Deleting a connection
ConnectionRM allows you to delete an existing connection from the connection list. However, if
the connection has been deployed, it is not possible to delete the connection.
To delete a connection:
3.
4.

Click OK.
under the Operation column of the target connection.
Undeploying a connection
37
7 Life cycle reports

Life cycle reports provide lists to record the VM migrations, and the offline and online operations
to 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, which
includes:
Source and destination switches
Source and destination physical servers
Source and destination interfaces
Time of the migration
Migration results
In addition to the Migration History list, you can also view the migration details in a more
intuitive wayicon view, which helps you easily trace each migration of a VM.
Operation List
The 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 QoS
management and access control for the target VM. It is deployed on the edge switch that
connects to the physical server of the VM. ConnectionRM provides the ability to migrate the
corresponding network configuration with the VM automatically, and records the configuration
offline and online operations related to the VM migrations.
The operation list shows the results of the configuration, offline and online operations, which
helps you check whether the VM network configuration migrates successfully. In addition,
when a network configuration migration fails, or only partially succeeds, you can view the
cause of failure, and manually perform the operation again.
Viewing historical record of VM migration via list view

ConnectionRM provides two modes to view the historical records of the VM migrations:
List view
Icon view
From the Migration History list, you can view the source and destination information of the VM
migration, and the results of the VM network configuration migration.
To view the history record of a VM migration via List view:
2. In the navigation tree, click Life Cycle Report.
3. On the Life Cycle Report page, click the Migration History tab to view the Migration History
list.
38
Life cycle reports
A record provides the following information on the VM migration:

VM
Indicates the name of the migrated VM.
vNIC
Indicates the MAC address of the vNIC.
Source Switch
Indicates the device label and IP address of the edge switch that connects to the physical server
that the target VM resides before the VM migration.
Source Interface
Indicates the port of the switch, with which the VM communicates with the clients before the VM
migration.
Source Physical
Server
Indicates the device label and IP address of the physical server where the target VM resides
before the VM migration.
Destination Switch
Indicates the device label and IP address of the edge switch where connects to the physical
server that the target VM resides after the VM migration.
Destination Interface Indicates the port of the switch with which the VM communicates with the clients. after the VM
migration.
Destination Physical
Server
Indicates the device label and IP address of the physical server where the target VM resides
after the VM migration.
Migration Time
Indicates the specific time when VM migration starts.
Migration Result
Indicates the 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 result of a VM network configuration can be:
SuccessIndicates all operations to migrate the VM network configuration are successful.
Partial SuccessIndicates part of the operations performed to migrate the VM network
configuration failed. You can click the View icon
operations and the cause of failure.
in the Operation field to view the failed
FailureIndicates all the operations performed to migrate the VM network configuration

failed. You can click the View icon
in the Operation field to view the failed operations
and the cause of failure. For more information, see Viewing operation list.
Operation
Indicates the operations you can perform, which include:

Operation InformationClick the Operation Information icon
in the Operation field to
view the offline and online operations of the VM network configuration. For more information,
see Viewing operation list.
ViewClick the View icon
to open the Migration Details page. On this page, you can
view the results of the operations to make the corresponding VM network configuration offline
and online, and see the cause of failure.
Icon ViewClick the Icon View icon
to view the historical migration records related to
a specified vNIC of a VM via Icon View. For more information, see Viewing historical record
of VM migration via icon view.
Viewing historical record of VM migration via icon view

The icon view provides a more intuitive way to view all historical migrations of a VM.
To view the historical record of virtual machine migration by icon view:
3. On the Life Cycle Report page, click the Migration History tab to view the Migration History
list. A record provides the details of VM migration.
Viewing historical record of VM migration via icon view
39
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 via icon view.
4.
Click the Icon View icon

of a record in the Operation field. The historical migration records
related to the specified vNIC of the target VM appear via Icon View. For example, Figure 10
shows the historical migrations related to the vNIC (0015-5d05-1417) of the VM
(test_windows_vmotion). The target VM has been migrated three times, starting from the source
server (HYPERV25 192.168.5.25) to the destination server (HYPERV20 192.168.5.20).
Figure 10 View historical record of VM via Icon View
The icon view of the VM historical migrations provides the following information:
VM
vNIC
Migration Latest Time Indicates the time when the VM migrated for the last time.
Switch
Indicates the device label and IP address of the edge switch that connects to the physical
server where the target VM resides.
Interface
Indicates the port of the switch, with which the VM communicates with the clients.
Physical Server
Indicates the device label and IP address of the physical server where the target VM
resides.
Migration Result
Indicates the result of the VM network configuration. The migration of a VM network

configuration always includes multiple operations. According to the results of these
operations, the result of the VM network configuration migration can be:
SuccessIndicates all operations to migrate the VM network configuration are
successful.
Partial SuccessIndicates part of the operations performed to migrate the VM network
configuration failed.
FailureIndicates all the operations performed to migrate the VM network configuration
failed.
Querying historical migration records

When there are a great number of records in the Migration History list, you can use the Query
function to search for the records you want to view.
To query for historical migration records:
40
Life cycle reports
3.
4.
5.
6.
7.
On the Life Cycle Report page, click the Migration History tab to view the Migration History
list.
Move the pointer to the Query in the upper-right corner of the Migration History list, and a
search criteria dialog box appears.
Enter one or more search criteria. For more information, see Viewing historical record of VM
migration via list view.
Click Query. The historical records that meet your search criteria display in the Migration
History list.
When you finish your search, you can click Reset to restore the full Migration History list.
Viewing operation list

With the ConnectionRM, a VM network configuration can migrate with the target VM automatically.
The migration of a VM network configuration includes the following processes:
OfflineMake the original VM network configuration offline from the source edge switch.
OnlineDeploy the VM network configuration to the destination edge switch.
You can perform each process manually in a VEB environment. For more information, see
Application environments.
Each process may include multiple operations. The process is considered successful only when all
its operations are successfully performed. The Operation List displays all the online and offline
processes for VM network configurations. You can also view the network configuration offline, and
see online processes related to a specified VM migration.
When the result of a process is a failure or a partial success, you can view the details of the
operations performed on the process to identify the cause of failure.
To view all operation records:
3. In the Life Cycle Report page, click the Operation List tab to view the operation list.
To view the VM network configuration offline and online operations related to a specified VM
migration:
3. In the Life Cycle Report page, click the Migration History tab to view the migration history list.
4. Search the historical records of the VM you want to view, then click the Operation Information
5.
icon
in the Operation field to open the Operation List. The Operation List only displays
the VM network configuration offline and online operations related to the target VM migration.
In the Operation List, a record provides the following information about a main processoffline
or online of the VM network configuration.
VM
vNIC
Access Switch
Indicates the device label and IP address of the edge switch on which the offline or online
operation is performed. An online operation means that the IMC deploys a VM network
configuration on the access switch, and an offline operation means that the IMC removes
the VM network configuration from the access switch.
Access Interface
Indicates the port of the access switch, through which the physical server where the target
VM resides connects with the access switch.
Connection Name
Indicates the name of the connection that is deployed for the target VM.
Viewing operation list
41
VSI Type
Indicates the VSI Type version that is bound to the vNIC of the target VM.
Operation Type
Indicates the type of the operation. The two types of operations are:
OfflineRemove a VM network configuration from the edge switch.
OnlineDeploy a VM network configuration to the edge switch.
Execution Time
Indicates the execution time of the operation.
Result
Indicates the result of the operation. In the Operation List, an operation record represents
an online or offline process for a VM network configuration. Each process may include
multiple operations. According to the results of these operations, the result of an online or
offline process can be:
SuccessIndicates all operations of the process are successful.
Partial SuccessIndicates part of the operations of the process failed. You can click
the View icon
of failure.
in the Operation field to identify the failed operations and the cause
FailureIndicates all the operations of the process failed.

Operation
Indicates the operations you can perform, which include:

ViewClick the View icon
to open the Operation Details page. In this page, you
can view the operations of an online or offline process, results of these operations, and
the cause of failure.
RedeployClick the Redeploy icon
corresponding process again.
in the Operation field to perform the
Redeploying an online or offline process

When an online or offline process fails, or only partially succeeds, you can view the cause of
failure in the Operation Details page. In addition, after you fix the bugs that cause the failure, you
can perform the process again.
To redeploy an online or offline process:
3. In the Life Cycle Report page, click the Operation List tab to view the operation list.
4.
5.
Search the process you want to redeploy, and then click the Redeploy icon in the Operation
field.
A reminding dialog box appears on the top of this page to show whether or not the
redeployment of the process was successful.
Querying operations
When there are a great number of operation records in the Operation List, you can use the Query
function to search for the records you want to view.
To query for operation records:
3. In the Life Cycle Report page, click the Operation List tab.
4. Move the pointer to Query in the upper-right corner of the Operation List, and a search criteria
dialog box appears.
5. Complete one or more of the search criteria. For more information, see Viewing operation
list.
6. Click Query. The historical records that meet your search criteria are list in the Operation List.
7. When you finish your search, you can click Reset to restore the full Operation List.
42
Life cycle reports
8 Managing vManager plug-ins

A vManager plug-in integrates connection management into vManager servers after it is registered
for those servers. With the connection management function, vManager administrators can add,
modify, and delete connections from the servers. ConnectionRM provides only the vCenter plug-in.
Virtual management centers are collectively called "vManager" in IMC. Specifically, vCenter
manages VMware ESX/ESXi, and SCVMM manages Windows Hyper-V.
This information applies only to the VEB environment.
Registering the vCenter plug-in

To register the vCenter plug-in:
1. Click the Resource tab.
2. Select ConnectionRM > Plug-In Management from the navigation tree. All registered plug-in
entries appear on the Plug-In Management page as icons.
3.
4.
5.
Click the Manage icon

for vCenter Plug-In.
The vCenter Plug-In Management page appears.
vCenter Server IPEnter the IP address of the vCenter server for which you want to register
the plug-in. The IP address must be expressed in dotted decimal notation.
vCenter Server UsernameEnter the username for the vCenter server.
vCenter Server PasswordEnter the corresponding password for the vCenter server.
EmailEnter the email address of the current operator.
Click Register.
After successful registration, a vCenter plug-in entry appears on the Plug-In Management page,
and the connection management function is integrated into the specified vCenter server.
Repeat the preceding steps to register the vCenter plug-in for other vCenter servers, as needed.
NOTE: If the username and password of the vCenter server are the same as those of an IMC
operator who has connection management rights, the vCenter user directly accesses the connection
management function on the vCenter server without being asked to provide login information.
Modifying a vCenter plug-in entry

Operators can modify a registered plug-in entry when parameters of the related vCenter server
are changed.
To modify a plug-in entry:
entries appear on the Plug-In Management page.
3. Point to the icon for the registered vCenter plug-in entry you want to modify.
4. The Plug-In Information window appears.
5.
vCenter Server IPModify the IP address of the vCenter server for which you want to
register the plug-in. The IP address must be expressed in dotted decimal notation.
vCenter Server UsernameModify the username for the vCenter server.
vCenter Server PasswordModify the corresponding password for the vCenter server.
EmailModify the email address of the current operator.
Click Modify.
Registering the vCenter plug-in
43
Deleting a plug-in entry

To delete a plug-in:
entries appear on the Plug-In Management page.
3. Use one of the following methods to delete a plug-in entry:
Point to the icon for the registered vCenter plug-in entry you want to delete, and then click
Uninstall in the window that appears. When using this method, make sure vCenter plug-in
information is consistent with that on the vCenter server.
Click the Manage icon

, enter information about the vCenter plug-in entry you want to
delete, including the IP address, username, password, and email address, and then click
Uninstall. When using this method, make sure the vCenter plug-in entry already exists in
IMC.
After the plug-in entry is deleted, the connection management function is removed from the specified
vCenter server.
Managing connections on a vCenter server

A vCenter server provides the connection management function after the ConnectionRM vCenter
plug-in is registered for it. The connection management function requires using the username and
password of an IMC operator with connection management rights.
If the vCenter server cannot communicate with IMC at startup, it does not load or display the plug-in
information. To use the connection management function, ensure communication between the
vCenter server and IMC.
To manage connections on a vCenter server:
1. Register the vCenter plug-in for the vCenter server from ConnectionRM, see Registering the
vCenter plug-in.
2. Log in to the vCenter server by using VMware vSphere Client, select the virtual machine on
which you want to manage connections from the navigation tree, and then click the
Network(iMC) tab on the upper right part of the page.
3. The Login window appears, as shown in Figure 11.
Figure 11 Login window for connection management on a vCenter server
44
Managing vManager plug-ins
4.
4. Enter the IMC operator username and password with connection management rights, and
then click Login. The Connection List page appears, as shown in Figure 12.
Figure 12 Connection List page
This connection list contains only vNIC connections of the selected virtual machine, whereas
the connection list on IMC ConnectionRM contains vNIC connections of all virtual machines.
You can create a vNIC connection on either vCenter or IMC. 5.
5.
Click Add.
The Add Connection page appears. For more information about adding a connection, see
Adding a connection.
When adding a connection on the vCenter server, you can bind a vNIC of only the selected
virtual machine to a VSI type version, and the connection name must be unique. For information
about other connection-related functions, see Connection management.
Managing connections on a vCenter server
45
9 Configuration example
The example describes how to configure IMC ConnectionRM to perform network configuration
migrations for VMs in an EVB application scenario.
The network in the example comprises the following devices:
EVB bridgePhysical switch that supports the EVB feature.
EVB stationPhysical server that supports the EVB feature.
IRF member switchMember switch in an IRF fabric. The HP Intelligent Resilient Framework
(IRF) technology creates a large IRF fabric from multiple switches to provide data center class
availability and scalability. IRF virtualization technology offers processing power, interaction,
unified management, and uninterrupted maintenance of multiple switches.
Network requirements
As shown in Figure 13, a company network comprises a two-member IRF fabric, two EVB Bridges
(HP 5900AF), and two EVB stations at Layer 2. They communicate within VLAN 100. The two EVB
Bridges connect to the network through the IRF member switches. The company uses IMC VNM
for virtual network management and uses IMC ConnectionRM for VM network configuration
migrations.
Create VM 1 on EVB Station A to serve as an FTP server. Configure the committed bandwidth and
peak bandwidth for VM 1 as 2048 kbps and 4096 kbps, respectively. Permit access from the
R&D department to only the FTP server.
Figure 13 Network diagram
Configuration prerequisites
Before you configure ConnectionRM and the EVB devices, complete the following tasks:
1. Install and deploy ConnectionRM. For more information, see HP Intelligent Management Center
Installation Guide.
2. Add EVB bridges and EVB stations to IMC. For more information, see HP IMC Base Platform
Administrator Guide.
Configuring EVB bridges

Described here is the necessary EVB configuration on the EVB bridges. The commands are available
on HP 5900AF switches. Commands may vary by device model.
46
Configuration example
Recommended configuration procedure

Step
Remarks
1. Configure LLDP:
Required.
Enable LLDP globally.

Enable LLDP for transferring EVB CDCPs and EVB TLVs on an interface.
2. Create a VLAN in which VMs forward traffic.
Optional.
3. Configure EVB:
Required.
Specify the IMC master as the default VSI manager.

Enable EVB on an interface.
Configure VDP keepalive aging timer.
This example uses ConnectionRM to automatically complete single VLAN configuration for the EVB
bridges. However, if multiple VLANs are required, configure them on each EVB bridge instead of
through ConnectionRM.
Configuring EVB Bridge A

# Enable LLDP on EVB Bridge A globally.
[EVB_BridgeA] system-view
[EVB_BridgeA] lldp global enable
Specify the IMC master 192.168.20.221 as the default VSI manager, and set the Web service
port to 8080.
[EVB_BridgeA] evb default-manager ip 192.168.20.221 port 8080
# Enable LLDP on interface Ten-GigabitEthernet 1/0/1 for transferring EVB TLVs and LLDP TLVs.
[EVB_BridgeA] interface Ten-GigabitEthernet1/0/1
[EVB_BridgeA-Ten-GigabitEthernet1/0/1] lldp tlv-enable dot1-tlv evb
# Enable EVB on interface Ten-GigabitEthernet 1/0/1.
[EVB_BridgeA-Ten-GigabitEthernet1/0/1] evb enable
Configuring EVB Bridge B

Configure EVB Bridge B as you configure EVB Bridge A, see Configuring EVB Bridge A.
To configure ConnectionRM:
1. Add EVB Bridge A and EVB Bridge B to ConnectionRM as edge switches:
a. Click the Resource tab
b. Select ConnectionRM > Edge Switch from the navigation tree.
c. The Edge Switch List page appears.
d. Click Add. The Select Devices window appears.
47
e.
f.
Filter edge switches by IP address (192.168.1.1 and 192.168.1.2) by using advanced

query.
Click OK.
EVB Bridge A and EVB Bridge B appear on the Edge Switch List.
2.
Add a network to ConnectionRM:

a. Click the Resource tab.
b. Select ConnectionRM > Network from the navigation tree. The Network List page appears.
c. Click Add. The Add Network window appears.
d. Configure the following network parameters:
e.
Enter For FTP as the network name.
Enter 100 as the VLAN ID.
Enter 10 in the Max. Connections field. The parameter specifies the maximum number
of connections that operators can create for the network.
Click OK.
The network For FTP appears on the Network List.
3.
Define a VSI type for VM 1:

b. Select ConnectionRM > VSI Type from the navigation tree. The VSI Type List page appears.
c. Click Add. The Add VSI Type window appears.
d. Configure the following VSI type parameters:
e.
Enter VM1 VSI as the VSI type name.
Select For FTP from the Network list.
Select the Bandwidth Control and VM Access Control options.
Enter 172.16.1.1 as the client IP.
Enter 0.0.0.255 as the wildcard mask.
Select BOTH as the filtering direction.
Enter 2048 in the CIR (kbps) field.
Enter 4096 in the PIR (kbps) field.
Click Add and Release.
ConnectionRM adds and releases the VSI type VM1 VSI (V1), and you can see VM1 VSI
appear on the VSI Type List.
4.
48
Define a connection in ConnectionRM to bind VM1 VSI to the vNIC of VM 1:

b. Select ConnectionRM > Connection from the navigation tree. The Connection List page
appears.
c. Click Add. The Add Connection window appears.
d. Configure the following connection parameters:
Enter VM1CON as the connection name.
Click Select next to the vNIC field, select VM 1 in the popup window, and then click
OK. The MAC address of VM 1 appears in the vNIC field.
Select For FTP from the Network list.
Configuration example
e.
Select VM1 VSI from the VSI Type list.
Select VM1 VSI (V1) from the VSI Type Version list.
Click OK.
VM1CON appears on the Connection List
Verifying the configuration

How does ConnectionRM manage configuration migration?
When VM 1 starts up, ConnectionRM deploys VM1 VSI to EVB Bridge A. When VM is shut down,
ConnectionRM deletes VM1 VSI from EVB Bridge A. When VM1 migrates to EVB Bridge B and
starts up, ConnectionRM deploys VM1 VSI to EVB Bridge B.
Verifying the configuration
49
10 Support and other resources

Contacting HP
For worldwide technical support information, see the HP support website:
http://www.hp.com/support
Before contacting HP, collect the following information:
Product model names and numbers
Technical support registration number (if applicable)
Product serial numbers
Error messages
Operating system type and revision level
Detailed questions
Subscription service
HP recommends that you register your product at the Subscriber's Choice for Business website:
http://www.hp.com/go/wwalerts.
An email notification is sent to you after registration is completed containing:
Product enhancements
New driver versions
Firmware updates
Other product resources
Related information
Documents
To find related documents, browse to the Manuals page of the HP Business Support Center website:
http://www.hp.com/support/manuals.
For related documentation, navigate to the Networking section, and select a networking
category.
For a complete list of acronyms and their definitions, see HP A-Series Acronyms.
Websites
50
HP.com http://www.hp.com
HP Networking http://www.hp.com/go/networking
HP manuals http://www.hp.com/support/manuals
HP download drivers and software http://www.hp.com/support/downloads
HP software depot http://www.software.hp.com
Support and other resources
Typographic conventions
Table 2 Document conventions
Convention
Element
Blue text: Table 2
Cross-reference links and e-mail addresses
Blue, underlined text: http://www.hp.com
Website addresses
Bold text
Keys that are pressed

Text typed into a GUI element, such as a box
GUI elements that are clicked or selected, such as menu
and list items, buttons, tabs, and check boxes
Italic text
Text emphasis
Monospace text
File and directory names

System output
Code
Commands, their arguments, and argument values
Monospace, italic text
Code variables
Command variables
Monospace, bold text
WARNING!
CAUTION:
IMPORTANT:
NOTE:
TIP:
Emphasized monospace text
Indicates that failure to follow directions could result in bodily harm or death.
Indicates that failure to follow directions could result in damage to equipment or data.
Provides clarifying information or specific instructions.
Provides additional information.

Provides helpful hints and shortcuts.
Product feedback
To make comments and suggestions about HP StorageWorks Product Name, please send a message
to bogusaddress@hp.com.
To make comments and suggestions about a product, please send a message to the product
address:
For HP StorageWorks Command View EVA: CVfeedback@hp.com
For HP StorageWorks Business Copy EVA or HP StorageWorks Continuous Access EVA:

EVAReplication@hp.com
Typographic conventions
51
11 Documentation feedback
HP is committed to providing documentation that meets your needs. To help us improve the
documentation, send any errors, suggestions, or comments to Documentation Feedback
(docsfeedback@hp.com). Include the document title and part number, version number, or the URL
when submitting your feedback.
52
Documentation feedback
Glossary
A
ACL
Access control list. This list includes a series of rules that group the traffic by class, and allow/deny
certain classes of packets. ConnectionRM uses IMC's ACL Management function to determine
match rules for network traffic classification.
Add-on Module
Like other IMC modules, ConnectionRM module can be installed and uninstalled separately in
IMC system.
C
CIR
Committed information rate. The CIR specifies the average rate allowed by the target VMs to
transmit or forward packets. In the practical environment, HP recommends that you control the
traffic bandwidth to be less than the CIR value.
Connection
Binding a vNIC with a VSI Type version. When a vNIC accesses to the network from a new
location, the VSI Type version must be migrated on the corresponding switch.
D
Device
In IMC, device indicates any router, switch, server, desktop computer, or other machine that
participates in the flow of traffic across a network.
E
EVB
Edge virtual bridge. EVB is the environment where physical end stations contain multiple virtual
end stations that participate in the bridged LAN.
I
ISP
Internet service provider. An ISP is an organization that provides access to the Internet.
L
LAN
Local area network. The LAN supplies networking capability to a group of computers in close
proximity to each other, such as in an office building, a school, or a home.
The defining characteristics of LANs, in contrast to wide area networks (WANs), include their
usually higher data-transfer rates, smaller geographic area, and lack of the need for leased
telecommunication lines.
N
Network
It is a management facility of the ConnectionRM service module, 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.
O
Operation
It is an action in the service unit of the VSI Type. A service unit consists of one or more operations.
P
Physical Server
The physical server in which the virtual software is installed. You can configure many virtual
machines on one physical server.
PIR
Peak information rate. The PIR specifies the maximum rate allowed by the target VMs to transmit
or forward packets. If the traffic bandwidth exceeds the PIR value, the system discards the
redundant packets to control the bandwidth.
53
Q
QoS
Quality of service. QoS is, in the networking industry, using specialized tools to monitor and
identify different types of network traffic, voice, video, and to establish priority and throughput
levels to optimize business processes.
S
Services Unit
Is a set of actions to define the complete network configuration to be deployed when a VM is

migrated.
V
vCenter
Virtual center. vCenter is a virtual management software that is used to manage the ESX/ESXi
system.
VEB
Virtual Ethernet bridge. VEB is a solution of 802.1qbg protocol.
VLAN
Virtual local area network. A VLAN is a set of devices grouped together on a wide area network
as if they were part of the same local area network.
vManager
Virtual manager. It is a general name for the virtual management software in IMC. To the VMware
software, the corresponding vManager is vCenter, which is used to manage the ESX/ESXi. To
the Windows virtual software, the corresponding vManager is SCVMM, which is used to manage
the Hyper-V.
vNIC
Virtual NIC. It is used by a VM to access a network.
VNM
Virtual network management. It is a module of IMC, which is used to manage the virtual network.
With it you can check the virtual network topology and manage the physical server, vSwitch,
VM, and so on.
VSI
Virtual station interface. Indicates the position where the VM accesses the virtual network. It
corresponds to a vNIC of the VM.
VSI Type
Virtual station interface Type. It is a set of network configurations for binding to a vNIC of a VM
to ensure continuous network configurations for VSI access.
54
Glossary
Index
A
ACL number range

setting, 16
life cycle reports, 38

historical record of VM migration via icon view, 39
historical record of VM migration via list view, 38
introduction, 38
querying historical records, 40
querying operations, 42
redeploying online or offline process, 42
viewing operation list, 41
C
configuration, 8
ConnectionRM, 47
edge switches and physical servers, 8
EVB bridges, 46
example, 46
requirements, 46
verifying, 49
connection
adding, 35
deleting, 37
deploying, 36
modifying, 36
undeploying, 37
connection list
viewing, 34
connection management, 34
querying, 35
ConnectionRM
configuration, 8
contacting HP, 50
conventions
document, 51
text symbols, 51
D
document
conventions, 51
documentation
providing feedback on, 52
E
edge switch
adding, 15
deleting, 17
management, 13
querying, 14
edge switch list
viewing, 13
EVB environment features, 7
F
Functional modules, 5
H
help
obtaining, 50
home page widget, 9
HP
technical support, 50
M
managing network configuration migration, 7
migration
managing network configuration, 7
N
network
adding, 31
copying configuration, 32
deleting, 33
modifying, 33
planning, 31
network details, 30
Network diagram, 5
network list, 29
network management, 29
P
products
providing feedback, 51
S
symbols in text, 51
T
technical support, 50
HP, 50
text symbols, 51
TopN widget, 9
ACL utilization, 11
deleting the ConnectionRM View, 10
refresh interval, 10
refreshing the ConnectionRM View, 10
viewing the ConnectionRM View, 10
typographic conventions, 51
V
vCenter server
managing connections, 44
VEB environment features, 7
vManager plug-ins
deleting, 44
managing, 43
modifying, 43
registering, 43
55
VSI type
adding, 22
customizing, 22
deleting, 27
deleting a version, 27
management, 20
modifying, 26
querying, 21
releasing a version for, 27
viewing details, 22
viewing list, 20
W
websites, 50
56
Index

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

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

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

Transféré par

Droits d'auteur :

Formats disponibles

HP Intelligent Management Center

Connection Resource Manager (Virtual

HP Part Number: 5998-3313

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

2 ConnectionRM home page widget................................................................9

3 Edge switch management..........................................................................13

4 VSI type management...............................................................................20

Copying the configuration of a network.....................................................................................32

7 Life cycle reports.......................................................................................38

8 Managing vManager plug-ins....................................................................43

10 Support and other resources.....................................................................50

VM access priority (specific clients)

VM access priority (all clients)

Connection ListManages VSI-type-version/vNIC bindings as connections. As the core of

Plug-In ManagementA vManager plug-in integrates connection management into vManager

Figure 1 Network diagram

The administrator must complete the following configuration tasks on ConnectionRM:

Add Switch A and Switch B as edge switches.

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 migration

They require different conditions for connection deploy or undeploy operations in

VEB environment features

When a VM migrates, ConnectionRM removes the VM network configuration by deleting the

Operators can manually deploy or undeploy connections in this environment.

EVB environment features

When a VM migrates, ConnectionRM removes the VM network configuration by deleting the

Managing network configuration migration in ConnectionRM

VEB environment features

Configuring the edge switches and physical servers

Configuring edge switches in the EVB environment

In the EVB environment

Complete LLDP basic configurations:

Enable LLDP globally.

Create a VLAN to forward VM traffic.

Complete basic EVB configurations:

Enable EVB on the interface.

Configure the VDP keepalive timer.

2 ConnectionRM home page widget

Adding the ConnectionRM view TopN widget to the home page

Place the cursor over the Custom icon

on the upper left of the page.

The icon changes into the Pin icon

Click the Pin icon

on the left and function links on

on the upper right of the

By default, the Welcome space is selected.

Click the Resource tab.

Click the Add icon

Setting the ConnectionRM View TopN widget

Place the cursor over the Custom icon

on the upper left of the page.

The icon changes into the Pin icon

Click the Pin icon

on the left and function links on

Adding the ConnectionRM view TopN widget to the home page

Click the Set icon

on the upper right of the ConnectionRM View TopN widget.

The Setting window appears.

Select a value from the Top list.

Setting the refresh interval

Click the Set icon

Refreshing the ConnectionRM View TopN widget

Deleting the ConnectionRM View TopN widget

Click the Delete icon