UCS 7 03 Nexus1000v HostMigration

UCS Technology Labs Nexus 1000v on UCS
Migrating Physical Adapters and VM

Guests to N1Kv DVS
Last updated: April 14, 2013
Task
Migrate one physical adapter to each uplink (Ethernet) port profile on the N1Kv DVS.
Migrate all VM guests, including vCenter and both N1Kv VSMs, over to run on the N1Kv VEMs.
Create any needed port profiles if not previously created.
Before any VEMs join the N1Kv, ensure that VEM running on ESXi1 joins the N1Kv as module 3
and VEM running on ESXi2 joins the N1Kv as module 4.
Configuration
To start, let's check the UUIDs of the blades in UCSM, because they serve as the defining value
of the VEM inside the N1Kv.
On ESXi1 Service Profile:
And on ESXi2 Service Profile:
On N1Kv:
FEEDBACK
vem 3
host vmware id 8f862310-4c63-11e2-0000-00000000000f
vem 4
host vmware id 8f862310-4c63-11e2-0000-00000000001f
We will intentionally start with ESXi2 to avoid disrupting vCenter or VSM1 traffic.
Navigate to ESXi2, click the Configuration tab, click Networking, select vSphere
Distributed Switch, and click Manage Physical Adapters.
Under the VM-Sys-Uplink port profile, click Click to Add NIC.
Choose vmnic0 and click OK.
We have a redundant vmnic for VMKernel traffic, so this shouldn't be too disruptive. Click Yes.
Under the vMotion-Uplink port profile, click Click to Add NIC.
We don't have a redundant vmnic for vMotion, but it isn't critical (in production it would be, but we
aren't in production). Click Yes.
Under the VM-Guests port profile, click Click to Add NIC.
We also have a redundant vmnic for VM-Guest traffic, so again this shouldn't be too disruptive.
Click Yes.
Click OK.
Note the new adapters under their respective uplink port profiles; they should all show green 8pin modular connector icons. Click Manage Virtual Adapters to begin moving VMkernel
interfaces over to the new DVS.
Click Add.
Select Migrate existing virtual adapters. Click Next.
Select the Management Network adapter, double-click under Port Group to display the dropdown menu, and select the VMKernel veth port profile from the N1Kv DVS.
Do the same for the vMotion adapter, but select the vMotion veth port profile from the N1Kv
DVS. Click Next.
Click Finish.
Click Close.
Note that we see both VMK interfaces moved to the DVS.
Verification
In N1Kv, note that the VEM module comes online and inserts into the N1Kv DVS properly as
VEM 4.
Note:
By default, modules are inserted and dynamically assigned the first available slot
number; however, based on what we did in the first few tasks, we assured that it
would be inserted as module 4. It is a very good practice to keep VEM numbers
synchronized with your ESXi hosts in some way, if possible. They can be
changed later, but it is much preferred to set them up properly from the start.
N1Kv-01#
2013 Feb 20 19:16:32 N1Kv-01 %VEM_MGR-2-VEM_MGR_DETECTED: Host
10.0.115.12 detected as module 4

2013 Feb 20 19:16:32 N1Kv-01 %VEM_MGR-2-MOD_ONLINE: Module 4 is online
N1Kv-01# sh mod
Mod Ports Module-Type
Model
Status
--- ----- -------------------------------- ------------------ ----------1
Virtual Supervisor Module
Nexus1000V
active *
Nexus1000V
ha-stand
248
Virtual Ethernet Module
NA
ok
by
4
Mod Sw
Hw
--- ------------------ -----------------------------------------------1
4.2(1)SV2(1.1)
0.0
4.2(1)SV2(1.1)
0.0
4.2(1)SV2(1.1)
VMware ESXi 5.0.0 Releasebuild-623860 (3.0)
Mod MAC-Address(es)
Serial-Num
--- -------------------------------------- ---------1
00-19-07-6c-5a-a8 to 00-19-07-6c-62-a8 NA
00-19-07-6c-5a-a8 to 00-19-07-6c-62-a8 NA
02-00-0c-00-03-00 to 02-00-0c-00-03-80 NA
Mod Server-IP
Server-UUID
Server-Name
--- --------------- ------------------------------------ ------------------1
10.0.121.1
NA
NA
10.0.121.1
NA
NA
10.0.115.12
8f862310-4c63-11e2-0000-00000000001f 10.0.115.12
* this terminal session

N1Kv-01#
Take note of the new Ethernet (physical) interfaces in the N1Kv.
N1Kv-01# sh run | b "interface Ethernet"

interface Ethernet4/1
inherit port-profile VM-Sys-Uplink
inherit port-profile vMotion-Uplink
inherit port-profile VM-Guests
And also notice the new Vethernet (virtual VM) interfaces in the N1Kv.
N1Kv-01# sh run | b "interface Vethernet"

interface Vethernet1
inherit port-profile VMKernel
description VMware VMkernel, vmk0
vmware dvport 160 dvswitch uuid "2a 80 3b 50 37 b7 1b 8e-18 98 be 68 05
cd ba
32"
vmware vm mac 0025.B501.011B
inherit port-profile vMotion
cd ba
32"
vmware vm mac 0050.5670.8A91
Configuration
Back in vCenter, right-click VSM2 in ESXi2 and click Edit Settings.
Change Network Adapter 1 to the new N1Kv-Control (N1Kv-01) port group in the DVS.
Note:
You can distinguish DVS port profiles from standard vSwitch groups by the fact
that they always indicate which DVS they are a part of in parentheses at the end
of the name. (Note that VMWare can run multiple different DVS at one time.)
Change Network Adapter 2 to the new N1Kv-Management (N1Kv-01) port group in the DVS.
Change Network Adapter 3 to the new N1Kv-Control (N1Kv-01) port group in the DVS. Click
OK.
Note in the vDS page for ESXi2 how they have been assigned and show green 8P8C for
connectivity.
Verification
We see that VSM2 has power-cycled but is still seen by the N1Kv.
N1Kv-01# sh mod
Model
Status
--- ----- -------------------------------- ------------------ ----------1
248
Nexus1000V
active *
powered
-up
4
Mod Sw
NA
ok
Hw
--- ------------------ -----------------------------------------------1
4.2(1)SV2(1.1)
0.0
4.2(1)SV2(1.1)
Mod MAC-Address(es)
Serial-Num
--- -------------------------------------- ---------1
00-19-07-6c-5a-a8 to 00-19-07-6c-62-a8 NA
02-00-0c-00-03-00 to 02-00-0c-00-03-80 NA
Mod Server-IP
Server-UUID
Server-Name
--- --------------- ------------------------------------ ------------------1
10.0.121.1
NA
NA
10.0.115.12
8f862310-4c63-11e2-0000-00000000001f 10.0.115.12

N1Kv-01#
Take note of the new Vethernet interfaces in the N1Kv.
Note:
It is important to understand something critical in the Nexus 1000v switch:
Although Vethernet interface numbering doesn't typically change after it is
assigned (even when vMotioning a VM to another ESXi host), these are still virtual
interfaces and they can be destroyed (e.g., delete a VM altogether).The N1Kv
refers to these virtual interfaces or Vethernet interfaces for use in the forwarding
tables with a value known as Local Target Logic (LTL). We will begin to see these
LTL values more and more as we look at pinning in future labs. But for now,
remember one more critical point: a VSM will always have three interfaces, they
will always be ordered as Control, Management, Packet, and they will always be
assigned LTL 10, 11, and 12 values, respectively. This can greatly aide in
troubleshooting. vemcmd show port-old will show you the values for these and
all other eth and veth interfaces, and we'll discuss various vemcmd's later.
N1Kv-01# sh run | b "interface Vethernet3"

inherit port-profile N1Kv-Control
description N1Kv-01-VSM-2, Network Adapter 1
cd ba
32"
vmware vm mac 0050.56BB.3A87
inherit port-profile N1Kv-Management
cd ba
32"
vmware vm mac 0050.56BB.6099
inherit port-profile N1Kv-Control
cd ba
32"
vmware vm mac 0050.56BB.14BB
Configuration
We will continue on and migrate the other host on ESXi2. Right-click Win2k8-www-1 and click
Edit Settings.
Change Network adapter 1 to VM-110 (N1Kv-01). Click OK.
Note its appearance as connected (green) in the vDS.
Verification
From any switch, we should be able to ping it, and we should also be able to ping the other two
VMs still on the standard vSwitch on ESXi1.
DC-3750#ping 10.0.110.111
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.0.110.111, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/9 ms
DC-3750#ping 10.0.110.112
!!!!!
DC-3750#ping 10.0.110.113
!!!!!
DC-3750#
Take note of the new Vethernet (virtual VM) interfaces in the N1Kv.
N1Kv-01# sh run | b "interface Vethernet6"

inherit port-profile VM-110
description Win2k8-www-1, Network Adapter 1
cd ba
32"
vmware vm mac 000C.298F.859D
Configuration
Now we will move the physical adapters on ESXi1 over using the same method that we used on
ESXi2. Navigate to ESXi1, click the Configuration tab, click Networking, select vSphere
Distributed Switch, and click Manage Physical Adapters. Click Click to Add NIC for VMSys-Uplink, vMotion-Uplink, and VM-Guests, and choose adapters vmnic0, vmnic2, and vmnic3
for the three uplink port profiles, respectively. Click OK.
Note their appearance as connected in the vDS. Click Manage Virtual Adapters.
Click Add.
Select Migrate existing virtual adapters. Click Next.
Select the Management Network adapter, double-click under Port Group to display the dropdown menu, and choose the VMKernel. For the VMKernel, choose the vMotion veth port
profiles from the N1Kv DVS. Click Next.
Click Finish.
Click Close.
Verification
The VEM comes online as module 3.
N1Kv-01(config-vem-slot)# sh mod
Model
Status
--- ----- -------------------------------- ------------------ ----------1
Nexus1000V
active *
Nexus1000V
ha-stand
248
NA
ok
248
NA
ok
by
Mod Sw
Hw
--- ------------------ -----------------------------------------------1
4.2(1)SV2(1.1)
0.0
4.2(1)SV2(1.1)
0.0
4.2(1)SV2(1.1)
4.2(1)SV2(1.1)
Mod MAC-Address(es)
Serial-Num
--- -------------------------------------- ---------1
00-19-07-6c-5a-a8 to 00-19-07-6c-62-a8 NA
00-19-07-6c-5a-a8 to 00-19-07-6c-62-a8 NA
02-00-0c-00-03-00 to 02-00-0c-00-03-80 NA
02-00-0c-00-04-00 to 02-00-0c-00-04-80 NA
Mod Server-IP
Server-UUID
Server-Name
--- --------------- ------------------------------------ ------------------1
10.0.121.1
NA
NA
10.0.121.1
NA
NA
10.0.115.11
8f862310-4c63-11e2-0000-00000000000f 10.0.115.11
10.0.115.12
8f862310-4c63-11e2-0000-00000000001f 10.0.115.12
Note the new Ethernet interfaces, and notice that any interfaces belonging to module 3 on ESXi1
will be numbered as Ethernet 3/x and any interfaces belonging to module 4 on ESXi2 will be
numbered as Ethernet 4/x.
N1Kv-01(config-vem-slot)# sh run | b "interface E"

Also note the new Vethernet interfaces for vmk management and vmotion.
N1Kv-01(config-vem-slot)# sh run | b "interface Vethernet7"

inherit port-profile VMKernel
cd ba
32"
vmware vm mac 0025.B501.010D
inherit port-profile vMotion
cd ba
32"
vmware vm mac 0050.567F.633F
Configuration
We haven't added a port profile for vCenter (VLAN 1) in N1Kv before now, so now is a good time,
before we begin migrating the remainder of the VM guests over. Before we do this, we need to
modify our uplink VM-Guests profile to include VLAN 1, and because vCenter is rather critical,
it's a good idea to make it a system VLAN as well - that way, it can begin forwarding traffic on
the VEM even before the VEM is inserted into the N1Kv DVS.
port-profile type ethernet VM-Guests

vmware port-group
switchport mode trunk
switchport trunk allowed vlan 1,110,120-121
no shutdown
system vlan 1,120-121
state enabled
port-profile type vethernet vCenter
vmware port-group
switchport mode access
switchport access vlan 1
no shutdown
system vlan 1
state enabled
Note that syslog should inform you that the DVPG or Distibuted Virtual Port Group was created
in vCenter.
2013 Feb 20 21:23:27 N1Kv-01 %VMS-5-DVPG_CREATE: created port-group 'vCen

ter' on the vCenter Server.
Back in vCenter, right-click the vCenter VM and click Edit Settings.
Migrate Network adapter 1 over to the vCenter (N1Kv-01) vDS port profile/group. Click OK.
Verification
We see a Veth interface created for vCenter, and so all should still be responsive with the
vCenter client.
2013 Feb 20 21:24:30 N1Kv-01 %VIM-5-IF_ATTACHED: Interface Vethernet14 is

attached to Network Adapter 1 of vCenter on port 8 of module 3 with dvport
id 416
2013 Feb 20 21:24:30 N1Kv-01 %ETHPORT-5-IF_UP: Interface Vethernet14 is up
in mode access
Configuration
Continue to migrate the rest of the VM guests NICs on ESXi 1. When finished, every guest on
both hosts should be fully migrated off of any local vSwitch and running soley on the Nexus
1000v DVS platform.
Verification
In vCenter on the vDS for ESXi1, we should see all VMs running on the N1Kv.
In the N1Kv CLI, we should see all of the Eth and Veth interfaces populated; note that the Veth
interfaces populate the description automatically with the name of the running VM occupying
that respective interface.
N1Kv-01# sh int status

------------------------------------------------------------------------------Port
Name
Status
Vlan
Duplex Speed
Type
------------------------------------------------------------------------------mgmt0
--
up
routed
full
1000
--
Eth3/1
--
up
trunk
full
1000
--
Eth3/3
--
up
trunk
full
unknown --
Eth3/4
--
up
trunk
full
unknown --
Eth4/1
--
up
trunk
full
1000
Eth4/3
--
up
trunk
full
unknown --
Eth4/4
--
up
trunk
full
unknown --
Veth1
VMware VMkernel, v up
115
auto
auto
--
Veth2
116
auto
auto
--
Veth3
N1Kv-01-VSM-2, Net up
120
auto
auto
--
Veth4
121
auto
auto
--
Veth5
120
auto
auto
--
Veth6
Win2k8-www-1, Netw up
110
auto
auto
--
Veth7
115
auto
auto
--
Veth8
116
auto
auto
--
Veth9
120
auto
auto
--
Veth10
121
auto
auto
--
Veth11
120
auto
auto
--
Veth12
110
auto
auto
--
Veth13
110
auto
auto
--
Veth14
vCenter, Network A up
auto
auto
--
control0
--
routed
full
1000
--
up
--
N1Kv-01#
^ back to top
Disclaimer (http://www.ine.com/feedback.htm) | Privacy Policy (http://www.ine.com/resources/)

Inc., All Rights Reserved (http://www.ine.com/about-us.htm)
2013 INE

UCS 7 03 Nexus1000v HostMigration

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

UCS 7 03 Nexus1000v HostMigration

Caricato da

Copyright:

Formati disponibili

UCS Technology Labs Nexus 1000v on UCS

Migrating Physical Adapters and VM

And on ESXi2 Service Profile:

Under the VM-Sys-Uplink port profile, click Click to Add NIC.

Choose vmnic0 and click OK.

Under the vMotion-Uplink port profile, click Click to Add NIC.

Choose vmnic2 and click OK.

Under the VM-Guests port profile, click Click to Add NIC.

Choose vmnic3 and click OK.

Select Migrate existing virtual adapters. Click Next.

Note that we see both VMK interfaces moved to the DVS.

2013 Feb 20 19:16:32 N1Kv-01 %VEM_MGR-2-VEM_MGR_DETECTED: Host

10.0.115.12 detected as module 4

--- ----- -------------------------------- ------------------ ----------1

Virtual Supervisor Module

Virtual Supervisor Module

Virtual Ethernet Module

--- ------------------ -----------------------------------------------1

VMware ESXi 5.0.0 Releasebuild-623860 (3.0)

--- -------------------------------------- ---------1

--- --------------- ------------------------------------ ------------------1

* this terminal session

Take note of the new Ethernet (physical) interfaces in the N1Kv.

N1Kv-01# sh run | b "interface Ethernet"

N1Kv-01# sh run | b "interface Vethernet"

--- ----- -------------------------------- ------------------ ----------1

Virtual Supervisor Module

Virtual Supervisor Module

Virtual Ethernet Module

--- ------------------ -----------------------------------------------1

VMware ESXi 5.0.0 Releasebuild-623860 (3.0)

--- -------------------------------------- ---------1

--- --------------- ------------------------------------ ------------------1

* this terminal session

Take note of the new Vethernet interfaces in the N1Kv.

N1Kv-01# sh run | b "interface Vethernet3"

Change Network adapter 1 to VM-110 (N1Kv-01). Click OK.

Note its appearance as connected (green) in the vDS.

N1Kv-01# sh run | b "interface Vethernet6"

Select Migrate existing virtual adapters. Click Next.

--- ----- -------------------------------- ------------------ ----------1

Virtual Supervisor Module

Virtual Supervisor Module

Virtual Ethernet Module

Virtual Ethernet Module

--- ------------------ -----------------------------------------------1

VMware ESXi 5.0.0 Releasebuild-623860 (3.0)

VMware ESXi 5.0.0 Releasebuild-623860 (3.0)

--- -------------------------------------- ---------1

--- --------------- ------------------------------------ ------------------1

* this terminal session

N1Kv-01(config-vem-slot)# sh run | b "interface E"

N1Kv-01(config-vem-slot)# sh run | b "interface Vethernet7"

port-profile type ethernet VM-Guests

2013 Feb 20 21:23:27 N1Kv-01 %VMS-5-DVPG_CREATE: created port-group 'vCen

Back in vCenter, right-click the vCenter VM and click Edit Settings.

2013 Feb 20 21:24:30 N1Kv-01 %VIM-5-IF_ATTACHED: Interface Vethernet14 is

N1Kv-01# sh int status

Disclaimer (http://www.ine.com/feedback.htm) | Privacy Policy (http://www.ine.com/resources/)

Potrebbero piacerti anche