DeWalt MD3220I manual Configure vSwitch & Enable Jumbo Frames, Add iSCSI VMkernel Ports

Page 15

Dell PowerVault MD32xxi Configuration Guide for VMware ESX4.1 Server Software

Go to the configuration tab and select Storage Adapters. Select the iSCSI Software Adapter and click Rescan. The newly created iSCSI target and LUN should be visible from the ESX server.

Step1: Configure vSwitch & Enable Jumbo Frames

This step will create a new vSwitch and enable Jumbo Frame support for this switch. This step is used for both examples no matter the number of VMkernels or physical NICs. Currently there is no option to enable Jumbo Frames on a vSwitch from VMware vCenter GUI so these commands must be run via CLI. Be sure to check the environment to make sure that Jumbo Frames are supported at the networking layer before enabling it on the ESX host.

The following command will create a new vSwitch called vSwitch2:

esxcfg-vswitch –a vSwitch2

Next, enable Jumbo Frames on the vSwitch:

esxcfg-vswitch –m 9000 vSwitch2

To verify that the switch was configured properly run the following command:

esxcfg-vswitch –l

Your output will look similar to this:

Switch Name

Num Ports

Used Ports

Configured Ports

MTU Uplinks

vSwitch2

64

1

64

9000

You can note the new vSwitch2 with the MTU of 9000 to verify that the switch was created correctly. You can also see it displayed in the GUI of vCenter. Throughout these procedures some of the verification can be done via command line or seen in the vCenter GUI. The polling rate of vCenter is not instant so changes will not show up immediately after it is typed.

Step2: Add iSCSI VMkernel Ports

This next step will assign VMkernel Ports to the new vSwitch2. It will also configure Jumbo Frame support as well as assign the IP Addresses. Administrators familiar with iSCSI connectivity in ESX3.5 will find that it is no longer required to configure a Service Console port for the iSCSI connection. Another thing to notice is that because the Service Console is not needed, the iSCSI switch environment can be on a different subnet than the public environment or existing service console. Each VMkernel Port will need its own IP Address and they must all be on the same subnet and be on the same subnet as the PowerVault IP Address.

Page 13

Image 15
Contents Page Page Table of Contents Terminology/Glossary Implementing ESX4.1 on the MD32xxi Storage Array IntroductionSupported Hardware and Software Architectural SetupEstablishing Sessions to a SAN PowerVault MD32xxi Storage Setup and Configuration Select Manually Define Hosts Page Select Configuration-Security Profile on the ESX server ISCSI Software Initiator Configuration on ESX4.1 ServerPage Page Clustering with ESX4.1 / Creating DRS Clusters Add iSCSI VMkernel Ports Configure vSwitch & Enable Jumbo FramesPage Assign Network Adapters Page Page Associate VMkernel Ports to Physical Adapters Page Page Enable VMware iSCSI Software Initiator Page Binding VMkernel Ports to iSCSI Software Initiator Static Click the Dynamic Discovery tab Connect to PowerVault MD32XXi StoragePage Page Page Connect to a Volume on PowerVault SAN Enabling VMware Native Multipathing MRU Contact InformationStep A1 Configure vSwitch and Enable Jumbo Frames Appendix aStep A2 Add iSCSI VMkernel Ports Networking Step A3 Assign Network Adapters Step A4 Associate VMkernel Ports to Physical Adapters Page Step A6 Binding VMkernel Ports to iSCSI Software Initiator Step A5 Enable VMware iSCSI Software InitiatorPage Vmk5 iSCSI6 IPv4 Step A7 Connect to the Dell PowerVault Storage