As a follow up to my original post "Configuring VMKernel port with an MTU of 9000 bytes" I thought that it would make more sense to include more of the configuration commands that are included in the VMware vSphere 4.0 iSCSI SAN Configuration document.
In the original post I only included the commands that enable you to create a vmkernel port with an MTU of 9000 bytes. In this post it includes the details from the original post as well as the configuration of the virtual switch and a second vmkernel port. In addition to that there are commands that bind the vmkernel ports to the software iSCSI adapter and removes a physical uplink from each vmkernel port.
In this example there are four physical network interfaces in the vSphere host, vmnic0 through vmnic3. Vmnics 0 and 1 are one physical adapter and vmnics 2 and 3 are another. We will be using vmnics 0 and 2 for vSwitch0, that way we have some redundany between physical adapters. You can configure vSwitch0 with vmnics 0 and 2 using the virtual infrastructure client.
Once you have finished configuring the vSphere host you should use the virtual infrastructure client, configuration tab, storage adapters, and rescan for new storage devices and VMFS volumes. The result should be that the existing LUNs will continue to be available except for the fact that the details of those LUNs will indicate that they have multiple paths.
Showing posts with label VMKernel. Show all posts
Showing posts with label VMKernel. Show all posts
Saturday, March 20, 2010
Tuesday, February 23, 2010
Configuring VMkernel port with an MTU of 9000 bytes
When configuring a vSphere4 host with a VMKernel port for iSCSI connectivity it is important to note that you cannot configure an MTU of 9000 bytes using the vSphere client.
In addition you cannot create the VMKernel port using the vSphere client and then modify the MTU of the port via the service console. You must create the VMKernel port with a MTU of 9000 bytes via the service console from the beginning.
I've included a sample script that will create an iSCSI port group and a VMKernel port with an MTU of 9000 bytes. There are additional options that can be specified when using the esxcfg-vswitch and esxcfg-vmknic commands but I have only included those that are necessary for this example.
In addition you cannot create the VMKernel port using the vSphere client and then modify the MTU of the port via the service console. You must create the VMKernel port with a MTU of 9000 bytes via the service console from the beginning.
I've included a sample script that will create an iSCSI port group and a VMKernel port with an MTU of 9000 bytes. There are additional options that can be specified when using the esxcfg-vswitch and esxcfg-vmknic commands but I have only included those that are necessary for this example.
Subscribe to:
Posts (Atom)