Step 1
| Log in to the
VMware vSphere Web Client.
|
Step 2
| In the vSphere
Client, choose
.
|
Step 3
| Choose a
datacenter and a distributed virtual switch, and then click
Manage.
Note
|
If the
switch is not managed by
Cisco Virtual Switch Update Manager, you are prompted to enter the switch credentials in
the
Make Managed
window. Fore more information, see the chapter
Managing
and Existing Cisco N1000V Switch.
|
|
Step 4
| In the switch
pane, click
Add
Host.
|
Step 5
| (Optional)In case of
multiple vCenter Servers, choose
.
|
Step 6
| (Optional)You can also
access the
Cisco Virtual Switch Update Manager
in the vSphere Client by navigating to
.
|
Step 7
| (Optional) In the switch
pane, click
Figure 1. Cisco
Virtual Switch Update Manager—Migrating Hosts
|
Step 8
| In the
Host
Selection area, review the following fields.
Name
|
Description
|
Cluster area
|
Lists all
the hosts that are in an HA pair. Check the checkbox next to the hosts to be
migrated.
|
Standalone Hosts
area
|
Lists the
standalone hosts. Check the checkbox next to the hosts to be migrated.
|
Supported column
|
If
checked, the host can be migrated to the current version of the
Cisco Nexus 1000V.
|
UnSupported
column
|
If
checked, the host cannot be migrated to the current version of the
Cisco Nexus 1000V.
For
information on the list of hosts that are not supported, see the Cisco Nexus
1000V and VMware Compatibility Documentation, at:
http://www.cisco.com/c/en/us/support/switches/nexus-1000v-switch-vmware-vsphere/products-device-support-tables-list.html.
|
UnReachable
column
|
If
checked, the host is in an unreachable state.
|
Already in DVS
column
|
If
checked, the host is already migrated to the
Cisco Nexus 1000V.
|
|
Step 9
| Click
Suggest.
Cisco Virtual Switch Update Manager displays the list of existing and proposed port
profiles and suggests appropriate port profiles for each VMKNIC, VM NIC, and
physical NICs.
|
Step 10
| Review the
port profile populated in the
Port
Profile Editor area. You can edit the fields based on your
requirements. To edit the fields, you must use the
Port
Profile Editor.
The port
profiles that are already available on the VSM are not editable. You can edit
only those port profiles that are suggested by the
Cisco Virtual Switch Update Manager. Click the
Duplicate
button to create a new port profile from an existing
or from a suggested port profile.
|
Step 11
| In the
Port
Profile Editor area, complete the following fields.
Name
|
Description
|
Port Profile
Editor drop-down list
|
The list
of existing port profiles or new port profiles to be created are displayed.
Choose the port profile.
-
In
Use—Displays true, when the port profile is in use on the current Add Host
screen. Displays False when the port profile is not in use on the current Add
Host screen.
-
Valid—Displays true when all the port profile fields are
completed. Displays false when one or more of the port profile fields is
incomplete.
-
Editable—Displays true if the port profile is editable. Displays
false if the port profile is not editable.
-
Profile Name—Displays the name of the port profile.
|
Uplink check box
|
If
checked, displays the uplink associated with the port profile.
|
Trunk check box
|
If
checked, displays the trunk associated with the port profile.
|
L3 Capable check
box
|
If
checked, the L3 capability is associated with the port profile.
|
ISCSI Multipath
check box
|
If
checked, the ISCSI Multipath is associated with the port profile.
|
Neither L3 nor
ISCSI check box
|
If
checked, then neither the L3 or the ISCSI is associated with the port profile.
|
Channel-group auto mode
on check box
|
If
checked, the channel group auto mode is associated with the port profile.
|
Mac-pinning
check box
|
If
checked, the channel group auto mode on mac-pining is associated with the port
profile.
|
Name field
|
The name
of the port profile.
|
VLANs field
|
Choose the
VLAN.
|
Native VLAN field
|
The native
VLAN associated with the port profile.
|
Duplicate button
|
Clones an
existing port profile configuration to create a new port profile.
|
|
Step 12
| Scroll down to
view the host profile populated in the
Physical NIC Migration area.
|
Step 13
| In the
Physical
NIC Migration area, review the following fields.
Name
|
Description
|
Physical NIC
check box
|
Review the
physical NIC that has been automatically selected by the
Cisco Virtual Switch Update Manager. Check/uncheck to select/deselect the VMNIcs for the
migration. You must ensure that at least one physical NIC is selected for the
migration.
|
Profile drop-down
list
|
Review the
port profile associated with the physical NICs.
Alternatively, you can choose the required port profile from
the profile drop-down list, to associate it with the physical NIC. You must
ensure that all the necessary VLANs are allowed in the selected port profile.
|
Source column
|
The
vSwitch or VDS port group that the PNIC is currently assigned to.
|
Select All button
|
Migrates
all the physical NICs associated with the host.
|
Select None button
|
Deselects all the selected values for the physical NICs
associated with the host.
|
|
Step 14
| Scroll down to
view the host profile populated in the
VM
Kernel NIC Setup area.
|
Step 15
| In the
VM Kernel
NIC Setup area, complete the following fields.
Name
|
Description
|
VM Kernel NIC check box
|
If checked, displays the port profile configuration that
will be created on Cisco Nexus 1000V and associated with the VMkernel NIC.
Review the selected VMkernel NICs. You can also uncheck
the VMkernel NIC check boxes if you do not want the VMKs to be migrated to the
Cisco Nexus 1000V.
You must ensure that at least one VMkernel NIC is
selected to migrate to the Cisco Nexus 1000V which will carry the L3 traffic.
Note
|
Do not uncheck any of the VMkernel NIC checkboxes,
unless and until the required VMkernel NIC is associated with the Layer3 port
profile.
|
|
L3 Capable column
|
Displays whether the VMkernel NIC is Layer 3 capable.
Only one VMkernel NIC is Layer3 capable. By default, the VMK0 is selected as
the Layer3 control.
Note
|
To change the VMkernel to Layer3 port profile, do the
following:
-
From the
Port Profile drop-down list,
choose the non Layer3 port profile for VMk0. In absence of non Layer3 veth
profile, you can create non Layer3 port profiles as follows:
-
Select the L3 enabled PP for any one VMkernel
NICs, which you want to use for the L3 control traffic.
|
|
Profile drop-down list
|
Choose the port profile associated with the VMkernel
NIC.
|
Source Profile column
|
Displays the vSwitch or VDS port group that the VMkernel
NIC is currently assigned to.
|
Select None button
|
Deselects all the selected VMkernel NICs associated with
the host.
|
New button
|
Adds a new VMkernel NIC for Layer 3 control. Enter the
IP address and net mask for the new VMkernel NIC and click
OK.
After the VMKernel NIC is created, select the
appropriate port profile for the VMKernel NIC from the port profile drop-down
list.
Note
| Ensure that the host is selected before you create
the new VMkernel NIC.
|
|
Edit button
|
Edits the IP address and subnet mask for a newly created
VMkernel NIC.
|
|
Step 16
| Scroll down to
view the host profile populated in the
VM
Migration area.
|
Step 17
| In the
VM
Migration area, review the following fields.
Area
|
Action
|
Virtual Machine
NICs check box
|
If
checked, displays the VSMs and the network adapters associated with the VM.
|
Profile drop-down
list
|
Choose the
port profile associated with the Virtual NIC.
|
Source Profile
column
|
The source
associated with the port profile.
|
Select None
button
|
Deselects
all the VMs associated with the host.
|
|
Step 18
| Click
Finish
to migrate the host from the VMware vSwitch to the Cisco
Nexus 1000V switch.
|
Step 19
| Check the
status of the installation by completing the following steps:
- Open a new
tab in your browser and enter the same vCenter IP address to open the web
client again.
- Log in to
the web client and in the navigation pane, click
Tasks.
The
Task Console opens in the work pane, displaying a
list of tasks with the most recent task at the top.
- Find the
task in the
Task Name column and then view the status in the
Status column.
The
Status column shows whether the task is complete or
is in progress. You can click the refresh icon to display new tasks and learn
how much of the task is complete in terms of percentage.
Note
|
Several
tasks might appear above the primary task you just performed. They might be
associated with your primary task.
|
The Nexus
1000V installation is confirmed when the primary task
Add
hosts to Cisco DVS has the status
Completed. A typical migration of the host takes about 2
minutes.
|