Transcript Before You Begin: Assign Information Classification

Nexus 1000V and HP’s
Virtual Connect
Cuong Tran
SAVBU – TME
August 2009
© 2009 Cisco Systems, Inc. All rights reserved.
1
Configurations of Nexus 1000V with HPVC
• Nexus 1000V and HPVC Environment
• Nexus 5000 Configurations
• Ethernet/Port-Channel configs
• HPVC Configurations
• Network Settings (Ethernet & FC)
• Server Profiles
• Nexus 1000V Configurations
• Network Configurations
• Adding Servers
• Migrating Service Console
• VMotion of VM
• VMotion within same HP c7000 chassis
© 2009 Cisco Systems, Inc. All rights reserved.
2
Nexus 1000V – HPVC Test Environment
Interconnect Bay1
Interconnect Bay2
Fibre Channel
Bays 3 & 4
EMC CX4-480
MDS9124-1
Nexus 5000-1
Nexus 5000-2
HPVC Flex-10
HPVC FC
HPVC 1G/10G
HPVC FC
HP c7000-1
Blade Servers Info:
• 2 BL460c G5
• Dual 1G LOMs
• Dual 1G Port Mez (slot 1)
• Dual 4G FC Mez (slot 2)
© 2009 Cisco Systems, Inc. All rights reserved.
MDS9124-2
HP c7000-2
Blade Servers Info:
• 5 BL490c G6
• Dual 10G LOMs
• Dual 4G FC Mez (slot 1)
3
VMWare ESX Server - VEM View for BL460c G5
Nexus 1000V VEM VLANs
Nexus 5000-1
• VSM- Control  VLAN 250
• VSM-Packet  VLAN 251
• Service Console/Mgmt  VLAN 182
• VMotion  VLAN 50
• VM Data VLANs  VLAN 51 – 52
Nexus 5000-2
Nexus 1000V Traffic FLow
• vmnic0/vmnic1 (PC) used for system-uplink
(VLANs 50, 250-251, 182)
• vmnic2/vmnic3 (PC) used for vm-uplink (VM
Data traffic VLANs 51 & 52)
HPVC 1G/10G
Bay1
HPVC 1G/10G
Bay2
HP c7000-1
Stacking Links
HPVC 1G/10G
Bay4
HPVC 1G/10G
Bay3
vmnic0
vmnic1
1G
1G
1G
vmnic3
1G
Service Console, VMotion,
N1K Port Profiles
Control & Packet
(VM Port Groups)
Nexus 1000V
ESX Blade Server
© 2009 Cisco Systems, Inc. All rights reserved.
vmnic2
VM
#1
VM
#2
VM
#3
4
VMWare ESX Server - VSM View for BL490c G6
Nexus 1000V VSM VLANs
Nexus 5000-1
• VSM- Control  VLAN 250
• VSM-Packet  VLAN 251
• Service Console/Mgmt  VLAN 182
Nexus 5000-2
ESX – VSM Traffic Flow
• vmnic0 allows VLANs 250-251, 182
• vmnic1 can be used as standby
• This ESX server will not be using N1K to
manage the vmnics
• VSMs will be installed on the BL490c G6
blade servers on HP c7000 - 1
HP c7000-2
Flex-10
Bay1
Flex-10
Bay2
vmnic0
vmnic1
4G
4G
Service Console, Control & Packet
VMWare vSwitch
ESX Blade Server
© 2009 Cisco Systems, Inc. All rights reserved.
N1K-VSM
(VM)
5
VMWare ESX Server - VEM View for BL490c G6
Nexus 1000V VEM VLANs
Nexus 5000-1
• VSM- Control  VLAN 250
• VSM-Packet  VLAN 251
• Service Console/Mgmt  VLAN 182
• VMotion  VLAN 50
• VM Data VLANs  VLAN 51 – 52
Nexus 5000-2
Nexus 1000V Traffic FLow
• vmnic0/vmnic1 (PC) used for system-uplink
(VLANs 50, 250-251, 182)
• vmnic2/vmnic3 (PC) used for vm-uplink (VM
Data traffic VLANs 51 & 52)
HP c7000-2
Flex-10
Bay1
Flex-10
Bay2
vmnic0
vmnic1
4G
vmnic2
4G
6G
Service Console, VMotion,
N1K Port Profiles
Control & Packet
(VM Port Groups)
Nexus 1000V
ESX Blade Server
© 2009 Cisco Systems, Inc. All rights reserved.
6G
vmnic3
VM
#1
VM
#2
VM
#3
6
Nexus 5000
Configurations
© 2009 Cisco Systems, Inc. All rights reserved.
7
Nexus 5000-1 with HPVC 1/G/10G Configuration
Nexus 5000-1 (HPVC 1/G10G) N5K-1 & N5K-2 Port-Channel
N5K-1 & N5K-2 Port-Channel
n5k-1# show running-config interface ethernet 1/1-2
n5k-1# show running-config interface ethernet 1/17-18
n5k-1# show running-config interface port-channel 1
version 4.1(3)N1(1)
version 4.1(3)N1(1)
version 4.1(3)N1(1)
interface Ethernet1/1
interface Ethernet1/17
interface port-channel1
description "HP Chassis 1 HPVC 1G/10G Bay1 - GE
Port1"
switchport mode trunk
switchport mode trunk
switchport mode trunk
switchport trunk allowed vlan 2-3967,4048-4093
switchport trunk allowed vlan 2-3967,4048-4093
channel-group 1
switchport trunk native vlan 182
switchport trunk allowed vlan 2-3967,4048-4093
speed 1000
interface Ethernet1/18
switchport mode trunk
channel-group 200 mode active
switchport trunk allowed vlan 2-3967,4048-4093
channel-group 1
interface Ethernet1/2
description "HP Chassis 1 HPVC 1G/10G Bay1 - GE
Port2"
Nexus 5000-1
switchport mode trunk
switchport trunk native vlan 182
Eth1/17
Eth1/17
Eth1/18
Eth1/18
Nexus 5000-2
switchport trunk allowed vlan 2-3967,4048-4093
Eth1/1
speed 1000
Eth1/2
Eth1/1
Eth1/2
channel-group 200 mode active
n5k-1# show running-config interface port-channel 200
Port 1
Port 2
Port 1
Port 2
version 4.1(3)N1(1)
interface port-channel200
switchport mode trunk
switchport trunk native vlan 182
switchport trunk allowed vlan 2-3967,4048-4093
© 2009 Cisco Systems, Inc. All rights reserved.
Chassis-1
HPVC 1G/10G
Bay1
Chassis-1
HPVC 1G/10G
Bay2
8
Nexus 5000-2 with HPVC 1/G/10G Configuration
Nexus 5000-2 (HPVC 1/G10G) N5K-1 & N5K-2 Port-Channel
N5K-1 & N5K-2 Port-Channel
n5k-2# show running-config interface ethernet 1/1-2
n5k-2# show running-config interface ethernet 1/17-18
n5k-2# show running-config interface port-channel 1
version 4.1(3)N1(1)
version 4.1(3)N1(1)
version 4.1(3)N1(1)
interface Ethernet1/1
interface Ethernet1/17
interface port-channel1
description "HP Chassis 1 HPVC 1G/10G Bay2 - GE
Port1"
switchport mode trunk
switchport mode trunk
switchport mode trunk
switchport trunk allowed vlan 2-3967,4048-4093
switchport trunk allowed vlan 2-3967,4048-4093
channel-group 1
switchport trunk native vlan 182
switchport trunk allowed vlan 2-3967,4048-4093
speed 1000
interface Ethernet1/18
switchport mode trunk
channel-group 200 mode active
switchport trunk allowed vlan 2-3967,4048-4093
channel-group 1
interface Ethernet1/2
description "HP Chassis 1 HPVC 1G/10G Bay2 - GE
Port2"
Nexus 5000-1
switchport mode trunk
switchport trunk native vlan 182
Eth1/17
Eth1/17
Eth1/18
Eth1/18
Nexus 5000-2
switchport trunk allowed vlan 2-3967,4048-4093
Eth1/1
speed 1000
Eth1/2
Eth1/1
Eth1/2
channel-group 200 mode active
n5k-2# show running-config interface port-channel 200
Port 1
Port 2
Port 1
Port 2
version 4.1(3)N1(1)
interface port-channel200
switchport mode trunk
switchport trunk native vlan 182
switchport trunk allowed vlan 2-3967,4048-4093
© 2009 Cisco Systems, Inc. All rights reserved.
Chassis-1
HPVC 1G/10G
Bay1
Chassis-1
HPVC 1G/10G
Bay2
9
Nexus 5000-1 with Flex-10 Configuration
Nexus 5000-1 (Flex-10)
N5K-1 & N5K-2 Port-Channel
N5K-1 & N5K-2 Port-Channel
n5k-1# show running-config interface ethernet 1/13-14
n5k-1# show running-config interface ethernet 1/17-18
n5k-1# show running-config interface port-channel 1
version 4.1(3)N1(1)
version 4.1(3)N1(1)
version 4.1(3)N1(1)
interface Ethernet1/13
interface Ethernet1/17
interface port-channel1
description "HP Chassis 2 Flex-10 Bay1 - Port2"
switchport mode trunk
switchport mode trunk
switchport mode trunk
switchport trunk allowed vlan 2-3967,4048-4093
switchport trunk allowed vlan 2-3967,4048-4093
switchport trunk native vlan 182
channel-group 1
switchport trunk allowed vlan 2-3967,4048-4093
channel-group 100 mode active
interface Ethernet1/18
switchport mode trunk
interface Ethernet1/14
description "HP Chassis 2 Flex-10 Bay1 - Port3"
switchport trunk allowed vlan 2-3967,4048-4093
channel-group 1
switchport mode trunk
switchport trunk native vlan 182
Nexus 5000-1
switchport trunk allowed vlan 2-3967,4048-4093
Eth1/17
Eth1/17
Eth1/18
Eth1/18
Nexus 5000-2
channel-group 100 mode active
n5k-1# show running-config interface port-channel 100
Eth1/13
Eth1/14
Eth1/13
Eth1/14
version 4.1(3)N1(1)
interface port-channel100
Port 2
Port 3
Port 2
Port 3
switchport mode trunk
switchport trunk native vlan 182
switchport trunk allowed vlan 2-3967,4048-4093
Chassis-2
Flex-10
Bay1
© 2009 Cisco Systems, Inc. All rights reserved.
Chassis-2
Flex-10
Bay2
10
Nexus 5000-2 with Flex-10 Configuration
Nexus 5000-2 (Flex-10)
N5K-1 & N5K-2 Port-Channel
N5K-1 & N5K-2 Port-Channel
n5k-2# show running-config interface ethernet 1/13-14
n5k-2# show running-config interface ethernet 1/17-18
n5k-2# show running-config interface port-channel 1
version 4.1(3)N1(1)
version 4.1(3)N1(1)
version 4.1(3)N1(1)
interface Ethernet1/13
interface Ethernet1/17
interface port-channel1
description "HP Chassis 2 Flex-10 Bay2 - Port2"
switchport mode trunk
switchport mode trunk
switchport mode trunk
switchport trunk allowed vlan 2-3967,4048-4093
switchport trunk allowed vlan 2-3967,4048-4093
switchport trunk native vlan 300
channel-group 1
switchport trunk allowed vlan 2-3967,4048-4093
channel-group 100 mode active
interface Ethernet1/18
switchport mode trunk
interface Ethernet1/14
description "HP Chassis 2 Flex-10 Bay2 - Port3"
switchport trunk allowed vlan 2-3967,4048-4093
channel-group 1
switchport mode trunk
switchport trunk native vlan 300
Nexus 5000-1
switchport trunk allowed vlan 2-3967,4048-4093
channel-group 100 mode active
n5k-2# show running-config interface port-channel 100
Eth1/13
Eth1/14
Eth1/17
Eth1/17
Eth1/18
Eth1/18
Nexus 5000-2
Eth1/13
Eth1/14
version 4.1(3)N1(1)
interface port-channel100
Port 2
Port 3
Port 2
Port 3
switchport mode trunk
switchport trunk native vlan 300
switchport trunk allowed vlan 2-3967,4048-4093
© 2009 Cisco Systems, Inc. All rights reserved.
Chassis-2
Flex-10
Bay1
Chassis-2
Flex-10
Bay2
11
HP Virtual Connect
Configurations
© 2009 Cisco Systems, Inc. All rights reserved.
12
HP’s Virtual Connect Tasks
• Build a “Shared Uplink”
• Define Ethernet Uplinks
• Configure “Associated” Networks
• Build SAN Fabrics
• Define FC Uplinks
• Build Server Profiles (For VSM and VEM Servers)
• Define NIC(s)
• Assign Network(s)
• Set port speed (Flex-NIC can be customized)
• Define HBA
• Assign to physical blade server
© 2009 Cisco Systems, Inc. All rights reserved.
13
HP c7000-2 Flex-10 - Shared Uplinks Bay 1
Within Virtual Connect Manager, create a “Shared Uplink Set”
• Name: “C7K2-Uplink Bay1”
• Added Port X2 and Port X3 to Uplink Set
• Speed should be left at “auto”
Repeat steps for Bay 2 “Shared Uplink Set”
© 2009 Cisco Systems, Inc. All rights reserved.
14
HP c7000-2 Flex-10 - Associating Networks Bay 1
In the same area with the “Shared Uplink Set”, you will want to associate Networks (a.k.a. VLANs) to the
uplink set. This will determine which VLANs will traverse these uplinks
• Click “Add”  Give name for each of the networks needed (ex: b1-cisco-lab, b1-vsm-control, etc)
• Provide VLAN number for the network
• For ESX “Service Console” VLAN, please make that VLAN to be the “Native VLAN” in this “Associated Networks” – this
example is VLAN 182
• When finished, click on “Apply” – Adding/Removing Networks is not disruptive.
Repeat steps for Bay2 “Shared Uplink Set”, should have the exact same networks (VLANs)
© 2009 Cisco Systems, Inc. All rights reserved.
15
HP c7000-2 Flex-10 – Shared Uplink Set for Bay 2
Configuration for Shared Uplink Set and Associated Networks for Bay 2
© 2009 Cisco Systems, Inc. All rights reserved.
16
HP c7000-1 HPVC1G/10G - Shared Uplinks Bay 1
HPVC 1G/10G Configuration for Shared Uplink Set and Associated Networks for Bay1
© 2009 Cisco Systems, Inc. All rights reserved.
17
HP c7000-1 HPVC1G/10G - Shared Uplinks Bay 2
HPVC 1G/10G Configuration for Shared Uplink Set and Associated Networks for Bay2
© 2009 Cisco Systems, Inc. All rights reserved.
18
HP c7000-1 HPVC FC – C7K1-Fabric-A
In Virtual Connect Manager, defining “SAN Fabrics” chooses which uplink ports on the HPVC FC
module to use for the SAN traffic
• Provide a Fabric Name: ex: C7K1-Fabric-A
• Add the uplink ports for the Fabric (in this example is uplinks port 1 & 2 on bay 5)
Repeat steps for the second Fabric (C7K1-Fabric-B) using Bay 6
© 2009 Cisco Systems, Inc. All rights reserved.
19
HP c7000-1 HPVC FC – C7K1-Fabric-B
© 2009 Cisco Systems, Inc. All rights reserved.
20
HP c7000-2 HPVC FC – C7K2-Fabric-A
© 2009 Cisco Systems, Inc. All rights reserved.
21
HP c7000-2 HPVC FC – C7K2-Fabric-B
© 2009 Cisco Systems, Inc. All rights reserved.
22
Server Profile
VSM Servers
© 2009 Cisco Systems, Inc. All rights reserved.
23
ESX VSM Server Network Layout
ESX – VSM Traffic Flow
Nexus 1000V VSM VLANs
• VSM- Control  VLAN 250
• VSM-Packet  VLAN 251
• Service Console/Mgmt  VLAN 182
• vmnic0 allows VLANs 250-251, 182
• vmnic1 can be used as standby
• This ESX server will not be using N1K to manage the vmnics
Flex-10
Bay1
Flex-10
Bay2
vmnic0
vmnic1
4G
4G
Service Console, Control & Packet
VMWare vSwitch
ESX Blade Server
© 2009 Cisco Systems, Inc. All rights reserved.
N1K-VSM
(VM)
24
Server Profile (ESX VSM)
In Virtual Connect, creation of a “Server Profile” defines a few parameters
1.Ethernet Network - how many NICs and which VLAN(s) those NICs will be using
2.FC SAN – how many HBAs and which SAN Fabric they will connect to
3.Assign Profile – Binds this Server Profile to a particular Blade Server in the chassis
© 2009 Cisco Systems, Inc. All rights reserved.
25
Server Profile (ESX VSM) – Ethernet Network
With building a Blade Server to host the VSM (VM), validating that the NIC(s) allows the required N1K
VLANs is needed. Since there are multiple VLANs needed, then these NICs must allow multiple networks.
To do this for the Server Profile, select the NIC “port” and click on the drop-down box and choose “Multiple
Networks”.
Setting the “Port Speed” is allowed and can be traffic shape to a specific speed (Tx only). In this example,
we have set the speed to be “Custom”, which will set the speed of the link (i.e. 4G)
© 2009 Cisco Systems, Inc. All rights reserved.
26
Server Profile (ESX VSM) – Ethernet Network
continued…
When choosing “Multiple Networks”, a new window will pop up. The window below shows what Networks
are allowed to flow through this NIC. Just click on the drop-down box and choose the network. When
finished, click “OK”.
Note: Any Changes to the “Server Profile” will have to be an offline task (i.e. Server is down)
© 2009 Cisco Systems, Inc. All rights reserved.
27
Server Profile (ESX VSM) – FC SAN
In the HP Blade Servers, the FC Mez cards are hard code to a specific Interconnect bay. The test
environment has the FC Mez card placed in slot1, which will bind FC Port 1 to Bay3 and FC Port 2 to
Bay4. With that in mind, click on the drop-down section for the FC SAN Name that was created and
choose the appropriate SAN Fabric.
© 2009 Cisco Systems, Inc. All rights reserved.
28
Server Profile (ESX VSM) – Assign Profile
Last portion for the Server profile is to assign the profile to the physical blade server in the chassis. In this
example, Blade Server in slot 1 will be assign for the VSM. This server is a BL490c G6 (Intel processor).
Since the test environment will have 2 VSMs (dual-supervisors), another blade server will be used. The
second blade server should have the same settings as this server profile bound to Server in slot 2.
© 2009 Cisco Systems, Inc. All rights reserved.
29
Server Profile
VEM Servers for
c7000-1
© 2009 Cisco Systems, Inc. All rights reserved.
30
ESX VEM Server for HP c7000-1
Nexus 1000V VEM VLANs
Nexus 1000V Traffic FLow
• VSM- Control  VLAN 250
• VSM-Packet  VLAN 251
• Service Console/Mgmt  VLAN 182
• VMotion  VLAN 50
• Data VLANs  VLAN 51 – 52
• vmnic0/vmnic1 (PC) used for system-uplink
(VLANs 50, 250-251, 182)
• vmnic2/vmnic3 (PC) used for vm-uplink
(Data traffic VLANs 51 & 52)
HPVC 1G/10G
Bay1
HPVC 1G/10G
Bay2
Stacking Links
HPVC 1G/10G
Bay4
HPVC 1G/10G
Bay3
vmnic0
vmnic1
1G
1G
vmnic2
1G
vmnic3
1G
Service Console, VMotion,
N1K Port Profiles
Control & Packet
(VM Port Groups)
Nexus 1000V
ESX Blade Server
© 2009 Cisco Systems, Inc. All rights reserved.
VM
#1
VM
#2
VM
#3
31
Server Profile (ESX VEM)
Similar to creating a Server Profile for the ESX VSM server, the Server Profile for the “ESX VEM” server
will be slightly different. In this Server Profile, 4 GE NICs will be used. With the topology that is being
deployed in the test environment, the following are the VLAN traffic flows:
• vmnic0 (GE) & vmnic1 (GE) used for system-uplink (VLANs 50, 250-251, 182)
• vmnic2 (GE) & vmnic3 (GE) used for vm-uplink (VM Data traffic VLANs 51 & 52)
© 2009 Cisco Systems, Inc. All rights reserved.
32
Server Profile (ESX VEM) – Ethernet Network
(Port 1 = vmnic0)
As in the ESX VSM Server Profile, when choosing “Multiple Networks”, a new window will pop up. The
window below shows what Networks are allowed to flow through this Port 1 (vmnic0). Just click on the dropdown box and choose the network. To add more vNet, click on “Add Mapping”. When finished, click “OK”.
© 2009 Cisco Systems, Inc. All rights reserved.
33
Server Profile (ESX VEM) – Ethernet Network
(Port 2 = vmnic1)
As in the ESX VSM Server Profile, when choosing “Multiple Networks”, a new window will pop up. The
window below shows what Networks are allowed to flow through this Port 2 (vmnic1). Just click on the dropdown box and choose the network. To add more vNet, click on “Add Mapping”. When finished, click “OK”.
© 2009 Cisco Systems, Inc. All rights reserved.
34
Server Profile (ESX VEM) – Ethernet Network
(Port 3 = vmnic2)
The window below shows what Networks are allowed to flow through this Port 3 (vmnic2). Just click on
the drop-down box and choose the network. To add more vNet, click on “Add Mapping”. When finished,
click “OK”.
© 2009 Cisco Systems, Inc. All rights reserved.
35
Server Profile (ESX VEM) – Ethernet Network
(Port 4 = vmnic3)
The window below shows what Networks are allowed to flow through this Port 4 (vmnic3). Just click on
the drop-down box and choose the network. To add more vNet, click on “Add Mapping”. When finished,
click “OK”.
© 2009 Cisco Systems, Inc. All rights reserved.
36
Server Profile
VEM Servers for
c7000-2
© 2009 Cisco Systems, Inc. All rights reserved.
37
ESX VEM Server for HP c7000-2
Nexus 1000V VEM VLANs
Nexus 1000V Traffic FLow
• VSM- Control  VLAN 250
• VSM-Packet  VLAN 251
• Service Console/Mgmt  VLAN 182
• VMotion  VLAN 50
• Data VLANs  VLAN 51 – 52
• vmnic0/vmnic1 (PC) used for system-uplink
(VLANs 50, 250-251, 182)
• vmnic2/vmnic3 (PC) used for vm-uplink
(Data traffic VLANs 51 & 52)
Flex-10
Bay1
Flex-10
Bay2
vmnic0
vmnic1
4G
vmnic2
4G
6G
vmnic3
6G
Service Console, VMotion,
N1K Port Profiles
Control & Packet
(VM Port Groups)
Nexus 1000V
ESX Blade Server
© 2009 Cisco Systems, Inc. All rights reserved.
VM
#1
VM
#2
VM
#3
38
Server Profile (ESX VEM)
Similar to creating a Server Profile for the ESX VSM server, the Server Profile for the “ESX VEM” server
will be slightly different. In this Server Profile, 4 NICs will be used and the bandwidth of the NICs will be
different. With the topology that is being deployed in the test environment, the following are the VLAN
traffic flows:
• vmnic0 (4G) & vmnic1 (4G) used for system-uplink (VLANs 50, 250-251, 182)
• vmnic2 (6G) & vmnic3 (6G) used for vm-uplink (VM Data traffic VLANs 51 & 52)
© 2009 Cisco Systems, Inc. All rights reserved.
39
Server Profile (ESX VEM) – Ethernet Network
(Port 1 = vmnic0)
As in the ESX VSM Server Profile, when choosing “Multiple Networks”, a new window will pop up. The
window below shows what Networks are allowed to flow through this Port 1 (vmnic0). Just click on the
drop-down box and choose the network. To add more vNet, click on “Add Mapping”. When finished, click
“OK”.
© 2009 Cisco Systems, Inc. All rights reserved.
40
Server Profile (ESX VEM) – Ethernet Network
(Port 2 = vmnic1)
The window below shows what Networks are allowed to flow through this Port 2 (vmnic1). Just click on
the drop-down box and choose the network. To add more vNet, click on “Add Mapping”. When finished,
click “OK”.
© 2009 Cisco Systems, Inc. All rights reserved.
41
Server Profile (ESX VEM) – Ethernet Network
(Port 3 = vmnic2)
The window below shows what Networks are allowed to flow through this Port 3 (vmnic2). Just click on
the drop-down box and choose the network. To add more vNet, click on “Add Mapping”. When finished,
click “OK”.
Note: The Flex-NIC Port 3 is bound to Interconnect Bay1, which is using the Shared Uplink Set “Uplink
Bay1”
© 2009 Cisco Systems, Inc. All rights reserved.
42
Server Profile (ESX VEM) – Ethernet Network
(Port 4 = vmnic3)
The window below shows what Networks are allowed to flow through this Port 4 (vmnic3). Just click on
the drop-down box and choose the network. To add more vNet, click on “Add Mapping”. When finished,
click “OK”.
Note: Flex-NIC Port 4 is bound to Interconnect Bay2, which is using the Shared Uplink Set “Uplink Bay2”
© 2009 Cisco Systems, Inc. All rights reserved.
43
Server Profile (ESX VEM) – Ethernet Network
(Port Speed Setting)
With Flex-NICs, it is possible to traffic shape the amount of bandwidth each of the Flex-NICs are allowed
to be allowed to have. To set the port speed of the ports, click on the drop-down at the “Port Speed
Setting” and choose “Custom”. Another pop-up window will appear where the port bandwidth can be set.
Repeat this for each of the Ports (NICs).
© 2009 Cisco Systems, Inc. All rights reserved.
44
Server Profile (ESX VEM) – FC SAN
In the HP Blade Servers, the FC Mez cards are hard code to a specific Interconnect bay. The test
environment has the FC Mez card placed in slot1, which will bind FC Port 1 to Bay3 and FC Port 2 to
Bay4. With that in mind, click on the drop-down section for the FC SAN Name that was created and
choose the appropriate SAN Fabric.
© 2009 Cisco Systems, Inc. All rights reserved.
45
Server Profile (ESX VEM) – Assign Profile
Last portion for the Server profile is to assign the profile to the physical blade server in the chassis. In this
example, Blade Server in slot 8 will be assign for the VEM. This server is a BL490c G6 (Intel Nehalem
processor). This Server Profile can be copied and assigned to another blade server in the same chassis,
which will be blade server in slot 16. Another Server Profile needs to be configured on another HP c7000
chassis to be identical to this Server Profile, so as to be able to VMotion a VM across the 2 HP chassis.
© 2009 Cisco Systems, Inc. All rights reserved.
46
Nexus 1000V
Configuration
© 2009 Cisco Systems, Inc. All rights reserved.
47
Nexus 1000V Configurations
• Creating Port-Profiles
• Configuring system-uplink (create asymmetrical port-channel)
• Configuring vm-uplink (create asymmetrical port-channel)
• Configuring Service-Console, Vmotion, Exchange and Web port-profiles
• Adding ESX VEMs into DVS
• Migrating “Service Console” into Nexus 1000V
• Creating “vmkernel” for VMotion through Nexus 1000V
• VMotion of VMs
• Vmotion VM from one ESX server to another ESX server within same
HP c7000 chassis
• Vmotion VM from one ESX server to another ESX server between
separate HP c7000 chassis
Note: These steps will not include how to install the VSM. Please consult the
“Nexus 1000V installation guide” for details
© 2009 Cisco Systems, Inc. All rights reserved.
48
Port-Profile: System-Uplink
Configuration of “System-Uplink”
• capability is set to “uplink = yes”
• system vlans: list of vlans that will be enabled in case of system errors
• switchport mode is set to “trunk”
• list of allowed vlans that will use this port-profile (in this case vmotion, control, packet
and service console)
• Since HP Flex-10 does not support CDP, setting the channel-group to auto will insure
creation of port-channels using this port-profile
System-Uplink Configuration from VSM
hpvc-n1k# show port-profile name system-uplink
port-profile system-uplink
description:
status: enabled
capability uplink: yes
capability l3control: no
system vlans: 250-251,182
port-group: system-uplink
max-ports: inherit:
config attributes:
switchport mode trunk
switchport trunk allowed vlan 50,250-251,182
channel-group auto mode on sub-group cdp
no shutdown
evaluated config attributes:
switchport mode trunk
switchport trunk allowed vlan 50,250-251,182
channel-group auto mode on sub-group cdp
no shutdown
assigned interfaces
© 2009 Cisco Systems, Inc. All rights reserved.
49
Port-Profile: VM-Uplink
Configuration of “VM-Uplink”
• capability is set to “uplink = yes”
• switchport mode is set to “trunk”
• list of allowed vlans that will use this port-profile (in this case vlan 51 & 52)
• Since HP Flex-10 does not support CDP, setting the channel-group to auto will insure
creation of port-channels using this port-profile
VM-Uplink Configuration from VSM
hpvc-n1k# show port-profile name vm-uplink
port-profile vm-uplink
description:
status: enabled
capability uplink: yes
capability l3control: no
system vlans: none
port-group: vm-uplink
max-ports: inherit:
config attributes:
switchport mode trunk
switchport trunk allowed vlan 51-52
channel-group auto mode on sub-group cdp
no shutdown
evaluated config attributes:
switchport mode trunk
switchport trunk allowed vlan 51-52
channel-group auto mode on sub-group cdp
no shutdown
assigned interfaces:
© 2009 Cisco Systems, Inc. All rights reserved.
50
Port-Profile: Service-Console & VMotion
Configuration of “Service-Console”
Configuration of “VMotion”
Service-Console Configuration from VSM
VMotion Configuration from VSM
hpvc-n1k# show port-profile name service-console
port-profile service-console
description:
status: enabled
capability uplink: no
capability l3control: no
system vlans: none
port-group: service-console
max-ports: 32
inherit:
config attributes:
switchport access vlan 182
no shutdown
evaluated config attributes:
switchport access vlan 182
no shutdown
assigned interfaces:
hpvc-n1k# show port-profile name Vmotion
port-profile Vmotion
description:
status: enabled
capability uplink: no
capability l3control: no
system vlans: none
port-group: Vmotion
max-ports: 32
inherit:
config attributes:
switchport access vlan 50
no shutdown
evaluated config attributes:
switchport access vlan 50
no shutdown
assigned interfaces:
• capability is set to “uplink = no”  default
• switchport mode is set to “access” for
particular vlan (this case vlan 182)
© 2009 Cisco Systems, Inc. All rights reserved.
• capability is set to “uplink = no”  default
• switchport mode is set to “access” for
particular vlan (this case vlan 50)
51
Port-Profile: Exchange & Web
Configuration of “Exchange”
Configuration of “Web”
Exchange Port-Profile Configuration from VSM
Web Port-Profile Configuration from VSM
hpvc-n1k# show port-profile name Exchange
port-profile Exchange
description:
status: enabled
capability uplink: no
capability l3control: no
system vlans: none
port-group: Exchange
max-ports: 32
inherit:
config attributes:
switchport access vlan 51
no shutdown
evaluated config attributes:
switchport access vlan 51
no shutdown
assigned interfaces:
hpvc-n1k# show port-profile name Web
port-profile Web
description:
status: enabled
capability uplink: no
capability l3control: no
system vlans: none
port-group: Web
max-ports: 32
inherit:
config attributes:
switchport access vlan 52
no shutdown
evaluated config attributes:
switchport access vlan 52
no shutdown
assigned interfaces::
• capability is set to “uplink = no”  default
• switchport mode is set to “access” for
particular vlan (this case vlan 51)
© 2009 Cisco Systems, Inc. All rights reserved.
• capability is set to “uplink = no”  default
• switchport mode is set to “access” for
particular vlan (this case vlan 52)
52
Adding ESX to
Nexus 1000V
© 2009 Cisco Systems, Inc. All rights reserved.
53
Nexus 1000V: Adding Server
On the VMWare vSphere client, click on “Inventory”  “Inventory”  “Networking” to get the Nexus 1000V
information. On the window, right click on the VSM name (in this case hpvc-n1k) and select “Add Host…” as shown
on the screenshot below.
© 2009 Cisco Systems, Inc. All rights reserved.
54
Nexus 1000V: Adding Server Continued…
A wizard will come up and walk through the following steps. The first step is to select the server to add by clicking
on the radio button. Then choosing the vmnics to be under the control of the Nexus 1000V. The vmnic selected will
need to choose the appropriate “DVUplink port group”. The following “dvUplink port group” need to be configured
when adding the ESX server to Nexus 1000V:
• vmnic1  “system-uplink”
• vmnic2  “vm-uplink”
• vmnic3  “vm-uplink”
To choose the appropriate “DVUplink”, click on the drop-down box and select the appropriate port group.
Note: vmnic0 will be migrated into Nexus 1000V after migrating the “service-console” to the Nexus 1000V
© 2009 Cisco Systems, Inc. All rights reserved.
55
Nexus 1000V: Adding Server Continued…
Once the vmnics are selected and associated with the appropriate DVUplink, the next window appears. To
complete the task, click on “Finish”.
Note: The port-profiles created on the VSM prior to adding the server is shown when it is added to Nexus 1000V
© 2009 Cisco Systems, Inc. All rights reserved.
56
Nexus 1000V: Adding Server Continued…
The following screenshot and the “show module” shows the completed task of adding the ESX server to Nexus 1000V
© 2009 Cisco Systems, Inc. All rights reserved.
57
Migrating ServiceConsole to Nexus 1000V
© 2009 Cisco Systems, Inc. All rights reserved.
58
Migration of Service Console to Nexus 1000V
When installing ESX, the service console is under control of VMWare vSwitch. A migration wizard tool allows to
move the control of the service console to the Nexus 1000V. To get to this window, under “Configuration” of the
ESX server, select “Networking”, then click on “Distributed Virtual Switch” tab and then click on “Manage Virtual
Adapters…”. Another window will appear and then click on “Add” to add the service console to Nexus 1000V, as
shown in the screenshots below.
© 2009 Cisco Systems, Inc. All rights reserved.
59
Migration of Service Console to Nexus 1000V
Continued…
A wizard will walk through on adding the virtual adapter (in this case the service console). Please select “Migrate
existing virtual adapters” and click on “Next”.
© 2009 Cisco Systems, Inc. All rights reserved.
60
Migration of Service Console to Nexus 1000V
Continued…
The next window will show existing virtual adapters and the “Service Console” is shown. Select the check box for
the “Service Console” and from the drop down box under “Port group”, select the port-profile to move the “Service
Console”. A port-profile named “service-console” has already been created under the Nexus 1000V. Please select
this port-profile and click on “Next”. Another window will appear asking if you are sure you want to migrate the
service console, please click on “Yes”
© 2009 Cisco Systems, Inc. All rights reserved.
61
Migration of Service Console to Nexus 1000V
Continued…
The following window will appear and to complete the migration, click on “Finish”.
© 2009 Cisco Systems, Inc. All rights reserved.
62
Migration of Service Console to Nexus 1000V
Continued…
The “Managed Virtual Adapters” window will show the Service Console “vswif0”. From the Nexus 1000V VSM, the
“show interface virtual” will show the migrated Service Console as a virtual Ethernet interface, as shown below.
© 2009 Cisco Systems, Inc. All rights reserved.
63
Adding vmnic0 into
Nexus 1000V control
© 2009 Cisco Systems, Inc. All rights reserved.
64
Adding vmnic0 into Nexus 1000V Control
With no virtual adapters using the interface vmnic0, it can now be added to be under the control of the Nexus
1000V. Since it was intended to be used for “system-uplink” traffic, the following will walk through how to add
vmnic0 to the “system-uplink” port-profile.
To get started with this process, under “Configuration” of the ESX server, select “Networking”, then click on
“Distributed Virtual Switch” tab and then click on “Manage Physical Adapters…”. A window will appear and there
look for the “system-uplink” port-profile and click on “”<Click to Add NIC>”, as shown below.
© 2009 Cisco Systems, Inc. All rights reserved.
65
Adding vmnic0 into Nexus 1000V Control
Continued…
A new window will appear and will list the available vmnics on the server. Select “vmnic0” and click on “OK”.
Another window will appear prompting you if you are sure that you want to add vmnic0 to the Nexus 1000V.
© 2009 Cisco Systems, Inc. All rights reserved.
66
Adding vmnic0 into Nexus 1000V Control
Continued…
To complete this task, click on “OK”.
© 2009 Cisco Systems, Inc. All rights reserved.
67
Adding vmnic0 into Nexus 1000V Control
Continued…
From the Nexus 1000V view of things, prior to this migration, vmnic0 was not part of the Nexus 1000V. After the
addition, the following output is seen on the VSM and also belonging to the Port-Channel with interface Eth3/2.
Because of the setting on the system-uplink and vm-uplink port-profile “channel-group auto mode on sub-group
cdp”, Eth3/1 and Eth3/2 will automatically become a Port-Channel and interface Eth3/3 and Eth3/4 will become a
Port-Channel.
Show command before adding vmnic0
hpvc-n1k# show interface brief
-------------------------------------------------------------------------------Port VRF
Status IP Address
Speed MTU
-------------------------------------------------------------------------------mgmt0 -up 172.25.182.250
1000 1500
-------------------------------------------------------------------------------Ethernet
VLAN Type Mode Status Reason
Speed
Interface
-------------------------------------------------------------------------------Eth3/2
1
eth trunk up
none
10(D)
Eth3/3
1
eth trunk up
none
10(D)
Eth3/4
1
eth trunk up
none
10(D)
Port
Ch #
2
1
1
-------------------------------------------------------------------------------Port-channel VLAN Type Mode Status Reason Speed Protocol
Interface
-------------------------------------------------------------------------------Po1
1 eth trunk up
none
a-10(D) none
Po2
1 eth trunk up
none
a-10(D) none
-------------------------------------------------------------------------------Interface VLAN Type Mode Status Reason
MTU
-------------------------------------------------------------------------------Veth1
182 virt access up
none
1500
© 2009 Cisco Systems, Inc. All rights reserved.
68
Adding vmnic0 into Nexus 1000V Control
Continued…
Show command after adding vmnic0
hpvc-n1k# show interface brief
-------------------------------------------------------------------------------Port VRF
Status IP Address
Speed MTU
-------------------------------------------------------------------------------mgmt0 -up 172.25.182.250
1000 1500
-------------------------------------------------------------------------------Ethernet
VLAN Type Mode Status Reason
Speed
Interface
-------------------------------------------------------------------------------Eth3/1
1
eth trunk up
none
10(D)
Eth3/2
1
eth trunk up
none
10(D)
Eth3/3
1
eth trunk up
none
10(D)
Eth3/4
1
eth trunk up
none
10(D)
Port
Ch #
2
2
1
1
-------------------------------------------------------------------------------Port-channel VLAN Type Mode Status Reason Speed Protocol
Interface
-------------------------------------------------------------------------------Po1
1 eth trunk up
none
a-10(D) none
Po2
1 eth trunk up
none
a-10(D) none
-------------------------------------------------------------------------------Interface VLAN Type Mode Status Reason
MTU
-------------------------------------------------------------------------------Veth1
182 virt access up
none
1500
© 2009 Cisco Systems, Inc. All rights reserved.
69
Creating sub-groups for Asymmetrical
Port-Channel
hpvc-n1k# configure terminal
hpvc-n1k(config)# interface ethernet 3/1
hpvc-n1k(config-if)# sub-group-id 0
hpvc-n1k(config-if)# interface ethernet 3/2
hpvc-n1k(config-if)# sub-group-id 1
hpvc-n1k(config-if)# interface ethernet 3/3
hpvc-n1k(config-if)# sub-group-id 0
hpvc-n1k(config-if)# interface ethernet 3/4
hpvc-n1k(config-if)# sub-group-id 1
hpvc-n1k(config-if)# show running-config interface ethernet 3/1-4
version 4.0(4)SV1(1)
interface Ethernet3/1
inherit port-profile system-uplink
sub-group-id 0
interface Ethernet3/2
inherit port-profile system-uplink
sub-group-id 1
interface Ethernet3/3
inherit port-profile vm-uplink
sub-group-id 0
interface Ethernet3/4
inherit port-profile vm-uplink
sub-group-id 1
© 2009 Cisco Systems, Inc. All rights reserved.
70
Adding VMKernel for
VMotion
© 2009 Cisco Systems, Inc. All rights reserved.
71
Adding Virtual Adapter “VMKernel” for
VMotion
To add a new virtual adapter for VMotion click under “Configuration” of the ESX server, select “Networking”, then
click on “Distributed Virtual Switch” tab and then click on “Manage Virtual Adapters…”. Another window will appear
and then click on “Add”, as shown in the screenshots below.
© 2009 Cisco Systems, Inc. All rights reserved.
72
Adding Virtual Adapter “VMKernel” for
VMotion
A window will appear allowing for selection of “New virtual adapter” or “Migrate existing virtual adapters”, please
make sure that “New virtual adapter” is selected and click on “Next”
© 2009 Cisco Systems, Inc. All rights reserved.
73
Adding Virtual Adapter “VMKernel” for
VMotion
This next window, please select “VMKernel” and click on “Next”
© 2009 Cisco Systems, Inc. All rights reserved.
74
Adding Virtual Adapter “VMKernel” for
VMotion
This next window is where the “vmkernel” needs to select the appropriate port-group. Click on the drop down box
and select the port-profile “Vmotion”. Then click on the check box “Use the virtual adapter for VMotion” and click on
“Next”.
© 2009 Cisco Systems, Inc. All rights reserved.
75
Adding Virtual Adapter “VMKernel” for
VMotion
Please enter in the appropriate IP Address and subnet for the vmkernel then click on “Next”.
© 2009 Cisco Systems, Inc. All rights reserved.
76
Adding Virtual Adapter “VMKernel” for
VMotion
To complete this task, click on “Finish”. A window will prompt you to enter in the default gateway for the vmkernel. If
you have one configured for the vmkernel, answer yes, otherwise click on “No”.
© 2009 Cisco Systems, Inc. All rights reserved.
77
Adding Virtual Adapter “VMKernel” for
VMotion
The following window displays what the vmkernel looks like.
© 2009 Cisco Systems, Inc. All rights reserved.
78
Adding Virtual Adapter “VMKernel” for
VMotion
The following is the “show” command to display how the Nexus 1000V sees the vmkernel for this ESX server.
© 2009 Cisco Systems, Inc. All rights reserved.
79
VMotioning between ESX
Servers within same HP
c7000 Chassis
© 2009 Cisco Systems, Inc. All rights reserved.
80
Repeat Tasks for Additional ESX Servers
under Nexus 1000V Control
Repeat the steps for all the servers using the Nexus 1000V. The following output is the information seen by the
Nexus 1000V for the additional ESX servers.
hpvc-n1k# show module
Mod Ports Module-Type
Model
Status
--- ----- -------------------------------- ------------------ -----------1 0
Virtual Supervisor Module
Nexus1000V
active *
2 0
Supervisor/Fabric-1
powered-up
3 248 Virtual Ethernet Module
NA
ok
4 248 Virtual Ethernet Module
NA
ok
5 248 Virtual Ethernet Module
NA
ok
6 248 Virtual Ethernet Module
NA
ok
[snip]
Mod Server-IP
Server-UUID
Server-Name
--- --------------- ------------------------------------------------------1 172.25.182.250 NA
NA
3 172.25.182.205 35303137-3135-5553-4539-333050535258
hpvc1-esx1
4 172.25.182.206 35303137-3135-5553-4539-333050535257
hpvc1-esx2
5 172.25.182.207 b8d15c14-f699-df45-85a6-6549956fa0a0
hpvc2-esx3
6 172.25.182.208 849921f5-12ef-2e43-bd80-f51f073fda28
hpvc2-esx4
HP c7000-1 Blades
HP c7000-2 Blades
* this terminal session
© 2009 Cisco Systems, Inc. All rights reserved.
81
Repeat Tasks for Additional ESX Servers
under Nexus 1000V Control Continued…
hpvc-n1k# show interface brief
-------------------------------------------------------------------------------Port VRF
Status IP Address
Speed MTU
-------------------------------------------------------------------------------mgmt0 -up 172.25.182.250
1000 1500
-------------------------------------------------------------------------------Ethernet
VLAN Type Mode Status Reason
Speed
Interface
Ch #
-------------------------------------------------------------------------------Eth3/1
1
eth trunk up
none
1000(D) 1
Eth3/2
1
eth trunk up
none
1000(D) 1
Eth3/3
1
eth trunk up
none
1000(D) 3
Eth3/4
1
eth trunk up
none
1000(D) 3
Eth4/1
1
eth trunk up
none
1000(D) 2
Eth4/2
1
eth trunk up
none
1000(D) 2
Eth4/3
1
eth trunk up
none
1000(D) 4
Eth4/4
1
eth trunk up
none
1000(D) 4
Eth5/1
1
eth trunk up
none
10(D) 6
Eth5/2
1
eth trunk up
none
10(D) 6
Eth5/3
1
eth trunk up
none
10(D) 5
Eth5/4
1
eth trunk up
none
10(D) 5
Eth6/1
1
eth trunk up
none
10(D) 8
Eth6/2
1
eth trunk up
none
10(D) 8
Eth6/3
1
eth trunk up
none
10(D) 7
Eth6/4
1
eth trunk up
none
10(D) 7
Port
[snip]
© 2009 Cisco Systems, Inc. All rights reserved.
82
Repeat Tasks for Additional ESX Servers
under Nexus 1000V Control Continued…
hpvc-n1k# show interface virtual
-------------------------------------------------------------------------------Port
Adapter
Owner
Mod Host
-------------------------------------------------------------------------------Veth1
vswif0
VMware Service Console 3 hpvc1-esx1
Veth2
vswif0
VMware Service Console 4 hpvc1-esx2
Veth3
vmk0
VMware VMkernel
3 hpvc1-esx1
Veth4
vmk0
VMware VMkernel
4 hpvc1-esx2
Veth5
Net Adapter 1 Exchange-Srv1
3 hpvc1-esx1
Veth6
Net Adapter 1 Web-Srv1
3 hpvc1-esx1
Veth7
vswif0
VMware Service Console 5 hpvc2-esx3
Veth8
vmk0
VMware VMkernel
5 hpvc2-esx3
Veth9
vswif0
VMware Service Console 6 hpvc2-esx4
Veth10
vmk0
VMware VMkernel
6 hpvc2-esx4
Veth11
Net Adapter 1 Web-Srv2-lnx
6 hpvc2-esx4
Veth12
Net Adapter 2 WinXP-Client1
3 hpvc1-esx1
Veth13
Net Adapter 1 WinXP-Client1
3 hpvc1-esx1
© 2009 Cisco Systems, Inc. All rights reserved.
hpvc-n1k# show port-channel summary
Flags: D - Down
P - Up in port-channel (members)
I - Individual H - Hot-standby (LACP only)
s - Suspended r - Module-removed
S - Switched R - Routed
U - Up (port-channel)
------------------------------------------------------------------------------Group PortType Protocol Member Ports
Channel
------------------------------------------------------------------------------1 Po1(SU) Eth
NONE
Eth3/1(P) Eth3/2(P)
2 Po2(SU) Eth
NONE
Eth4/1(P) Eth4/2(P)
3 Po3(SU) Eth
NONE
Eth3/3(P) Eth3/4(P)
4 Po4(SU) Eth
NONE
Eth4/3(P) Eth4/4(P)
5 Po5(SU) Eth
NONE
Eth5/3(P) Eth5/4(P)
6 Po6(SU) Eth
NONE
Eth5/1(P) Eth5/2(P)
7 Po7(SU) Eth
NONE
Eth6/3(P) Eth6/4(P)
8 Po8(SU) Eth
NONE
Eth6/1(P) Eth6/2(P)
83
VMotion of VMs on c7000-1 Chassis
Nexus 5000-1
Nexus 5000-2
HPVC 1G/10G
Bay1
HPVC 1G/10G
Bay2
Stacking Links
HPVC 1G/10G
Bay4
HPVC 1G/10G
Bay3
vmnic0
vmnic1
1G
1G
vmnic2
1G
vmnic3
1G
Service Console, VMotion,
N1K Port Profiles
Control & Packet
(VM Port Groups)
Nexus 1000V
ESX Blade Server
© 2009 Cisco Systems, Inc. All rights reserved.
VM
#1
VM
#2
VM
#3
84
VMotion within same c7000-1 Chassis
Nexus 5000-1
Nexus 5000-2
HPVC 1G/10G
Bay1
HPVC 1G/10G
Bay2
Stacking Links
vmnic0
vmnic1
1G
1G
Service Console, VMotion,
Control & Packet
vmnic2
1G
1G
N1K Port Profiles
(VM Port Groups)
vmnic3
vmnic0
vmnic1
1G
1G
Service Console, VMotion,
Control & Packet
Nexus 1000V
hp1-esx1
© 2009 Cisco Systems, Inc. All rights reserved.
vmnic2
1G
vmnic3
1G
N1K Port Profiles
(VM Port Groups)
Nexus 1000V
VM
#2
hp1-esx2
VM
#1
VM
#3
85
VMotion within c7000 Chassis
Prior to VMotion of “Exchange-Srv1” VM with “Veth5”
© 2009 Cisco Systems, Inc. All rights reserved.
86
VMotion within same c7000-1 Chassis
To VMotion the VM, right click on the VM and select “Migrate...”
© 2009 Cisco Systems, Inc. All rights reserved.
87
VMotion within same c7000-2 Chassis
The Vmotion wizard walks through the steps. Make sure “Change
host” is selected and click on “Next”
© 2009 Cisco Systems, Inc. All rights reserved.
88
VMotion within same c7000-2 Chassis
The next window prompts to select which ESX server in the cluster
to migrate to. In this case, we will be selecting “hp1-esx2”, which is
in the same HP c70000 chassis. Then click on “Next”
© 2009 Cisco Systems, Inc. All rights reserved.
89
VMotion within same c7000-2 Chassis
This next window allows you to choose type of CPU utilization will
be use for the VMotion. Select your choice and click on “Next”
© 2009 Cisco Systems, Inc. All rights reserved.
90
VMotion within same c7000-2 Chassis
Verify the VMotion session and click on “Finish”
© 2009 Cisco Systems, Inc. All rights reserved.
91
VMotion within same c7000-2 Chassis
This is what vSphere sees after the migration.
© 2009 Cisco Systems, Inc. All rights reserved.
92
VMotion within c7000-2 Chassis
After VMotion of “Exchange-Srv1” VM has now moved to “hpvc1-esx2” server
© 2009 Cisco Systems, Inc. All rights reserved.
93
© 2009 Cisco Systems, Inc. All rights reserved.
94