Dell PowerVault MD3220i Deployment Manual

Also see for PowerVault MD3200i Series: Manual Update Rack Installation Instructions User guide Support Matrix

Dell PowerVault MD3220i Deployment Manual Manual pdf 15 page image

Dell PowerVault MD32xxi Configuration Guide for VMware ESX4.1 Server SoftwarePage 13Go to the configuration tab and select Storage Adapters. Select the iSCSI Software Adapter and click Rescan. Thenewly created iSCSI target and LUN should be visible from the ESX server.Step1: Configure vSwitch & Enable Jumbo FramesThis step will create a new vSwitch and enable Jumbo Frame support for this switch. This step is used forboth examples no matter the number of VMkernels or physical NICs. Currently there is no option toenable Jumbo Frames on a vSwitch from VMware vCenter GUI so these commands must be run via CLI. Besure to check the environment to make sure that Jumbo Frames are supported at the networking layerbefore enabling it on the ESX host.The following command will create a new vSwitch called vSwitch2:esxcfg-vswitch –a vSwitch2Next, enable Jumbo Frames on the vSwitch:esxcfg-vswitch –m 9000 vSwitch2To verify that the switch was configured properly run the following command:esxcfg-vswitch –lYour output will look similar to this:Switch Name Num Ports Used Ports Configured Ports MTU UplinksvSwitch2 64 1 64 9000You can note the new vSwitch2 with the MTU of 9000 to verify that the switch was created correctly. Youcan also see it displayed in the GUI of vCenter. Throughout these procedures some of the verification canbe done via command line or seen in the vCenter GUI. The polling rate of vCenter is not instant so changeswill not show up immediately after it is typed.Step2: Add iSCSI VMkernel PortsThis next step will assign VMkernel Ports to the new vSwitch2. It will also configure Jumbo Frame supportas well as assign the IP Addresses. Administrators familiar with iSCSI connectivity in ESX3.5 will find that itis no longer required to configure a Service Console port for the iSCSI connection. Another thing to noticeis that because the Service Console is not needed, the iSCSI switch environment can be on a differentsubnet than the public environment or existing service console. Each VMkernel Port will need its own IPAddress and they must all be on the same subnet and be on the same subnet as the PowerVault IPAddress.