Sunday, May 12, 2013

Creating a Virtual Distributed Switch on vSphere 5.1

I was working last week and had to work through the steps to make a vDS in vCenter. I went through the steps like the system was a live production system though only the virtualized vCenter server was on the 2 server datacenter.

The steps aren't linear, and there needs to be a little more polishing on the wizard on VMware's part. For posterity I'd like to toss this out there for anyone that might be struggling with the process.

Virtual Distributed Switch Configuration

Scope: This document will explain the process of installing a virtual distributed switch in a vCenter 5.1 infrastructure environment. This document will then go on to explain how to convert from a Standard switch environment to a Distributed Switch environment on a live production network.
Prerequisites:
-          vCenter installed
-          2 NICs per switch (for live migration)
-          vLAN and IP information

S    Site Setup:
k      The site has 4 Standard Virtual Switches: Management, Storage, Data, and vMotion. The Storage Standard Switch has two vmk connections to enable fail-over for software iSCSI. I left the Management on a Standard Virtual Switch and migrated all others.

      I used this YouTube video to understand the concepts of the Virtual Distributed Switch:


1.       Steps to create a Virtual Distributed Switch:
a.       Navigate to Inventory/Networking
b.      Right-click on the DataCenter where the vDS is to be created
c.       Use the latest version available. Next.
d.      General Properties
                                                              i.      Name the switch
                                                            ii.      Add the number of Uplink ports (think each of these as the number of physical ports each ESXi host has – 6 for the example below)
                                                          iii.      Next
e.      Toggle to ‘add hosts later’
f.        Next and Finish
g.   Right click on the newly created vDS and edit setting.
h.   To the right of the 'Number of Uplinks' there is a 'Rename Uplinks' click
i.   Rename the Uplinks Storage1 and Storage 2, Data 1 and data 2, vmotion 1 and vmotion 2. This ensures that the correct dvuplinks are paired to the correct port groups.
Process to Migrate switching from Standard Switching to Distributed Switching on a live environment with no down-time:
1.       For vMotion (both NICs at once no current vmotion operations)
a.       Navigate to Inventory/Networking
b.      Create a vmotion Distributed Port Group by:
                                                              i.      Right click the Distributed Switch and Add a New port Group
c.       Right Click on vmotion and ‘Edit Settings’
d.      Click ‘Teaming and Failover’
e.      Move all Uplinks to ‘Unused’ except vmotion1 and vmtion2
f.        ok
g.       Navigate to Inventory/Networking, right click vDS and ‘Manage Hosts’
h.      Check which ESX server you want to move NICs from. Next
i.        Click on the 2 vMotion NICs Next
j.        Migrate the vMotion vmk to the correct port group Next
k.       Next
l.        Finish
m.    Navigate to Inventory/Host and Clusters Configuration, Networking, Distributed Swtich
n.      Click ‘Manage Physical NICs…’
o.      Remove them from the dvuplink if they are incorrect and place them appropriately
p.   Ok
2.       For Data (one NIC at a time already connected)
a.       Navigate to Inventory/Networking
b.      Create a Data Distributed Port Group by:
                                                              i.      Right click the Distributed Switch and Add a New port Group
c.       Right Click on Data and ‘Edit Settings’
d.      Click ‘Teaming and Failover’
e.      Move all Uplinks to ‘Unused’ except Data1 and Data2
f.        ok
g.       Navigate to Inventory/Networking, right click vDS and ‘Manage Hosts’
h.      Check which ESX server you want to move the NIC from. Next
i.        Click on the second NIC Next
j.        Migrate nothing Next
k.       Next
l.        Finish
m.    Navigate to Inventory/Host and Clusters Configuration, Networking, Distributed Switch
n.      Click ‘Manage Physical NICs…’
o.      Remove it from the dvuplink if it is incorrect and place it appropriately
p.      Navigate to Inventory/Host and Clusters Configuration
q.      Navigate to the virtual machine
r.        Click ‘Edit Setting’
s.       Edit the NIC to point to the dv switch. Ok.
t.        Navigate to Inventory/Networking, right click vDS and ‘Manage Hosts’
u.      Check which ESX server you want to move the NIC from. Next
v.       Click on the first NIC Next
w.     Migrate nothing Next
x.       Next
y.       Finish
z.       Navigate to Inventory/Host and Clusters Configuration, Networking, Distributed Swtich
aa.   Click ‘Manage Physical NICs…’
bb.  Remove them from the dvuplink where if it is incorrect and place it appropriately
3.       For iSCSI software adapter with fail-over (one NIC at a time already connected)
a.       Navigate to Inventory/Networking
b.      Create two Distributed Port Groups, Storage1 and a Storage2
                                                              i.      Right click the Distributed Switch and Add a New port Group for each
c.       Right Click on Storage1 and ‘Edit Settings’
d.      Click ‘Teaming and Failover’
e.      Move all Uplinks to ‘Unused’ except Storage1
f.   Repeat steps c -e on Storage2        
g.       Navigate to Inventory/Host and Clusters ESXi host Configuration/Storage Adapters
h.      Right click on vmhba32 iSCSI Software adapter and Properties…
i.        Navigate to the ‘Network Configuration’ Tab and remove one of the Storage Port Binding Storage2
j.        Navigate to Inventory/Host and Clusters ESXi host Configuration /Networking/vSphere Standard Switch
k.       Under Properties of the Storage switch remove the Storage 2 NIC from ‘Network Adapters’
l.        Navigate to Inventory/Networking
m.    Right click the Distributed Switch and ‘Manage Hosts’
n.      Check the one you’ll be working with Next
o.      Select the physical adapter for Storage2 that you just unassigned Next
p.      Pick the vmk that was attached to the Storage2, use the drop down list to pick the Storage2 Destination Port Group. Next
q.      Next
r.        Finish
s.       Navigate to Inventory/Host and Clusters Configuration, Networking, Distributed Switch
t.        Click ‘Manage Physical NICs…’
u.      Remove it from the dvuplink if it is incorrect and place it appropriately
v.       Navigate to Inventory/Host and Clusters ESXi host Configuration/Storage Adapters
w.     Right click on vmhba32 iSCSI Software adapter and Properties…
x.       Navigate to the ‘Network Configuration’ Tab and add the Storage2 to Storage Port Binding – ensure it is ‘Compliant’. Ok to re-scan

y.       Repeat from Step G – X to Storage1 to ensure no down time of storage
Enhanced by Zemanta