StarWind Offers High Availability iSCSI SAN Software Free to Microsoft MVP, MCP and MCT Professionals
http://www.starwindsoftware.com/news/31
New StarWind High Availability iSCSI SAN Software Free for Any VMware vExpert, VCP or VCI
http://www.starwindsoftware.com/news/30
Thursday, March 25, 2010
Saturday, March 20, 2010
Configuring VMkernel port with an MTU of 9000 bytes - Part 2
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.
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.
Virtualization
esxcfg-vswif,
esxcfg-vswitch,
esxcli,
iSCSI,
VMKernel,
vSwitch
Thursday, February 25, 2010
VMware announces the end of availability for VMware Consolidated Backup
VMware Backup Product Strategy
VMware released vStorage APIs for Data Protection (VADP) with the vSphere 4.0 release in May, 2009. VADP is the next generation of VMware’s backup framework. We have also been working with several backup partners to integrate VADP into their solutions to make backup of vSphere Virtual Machines fast, efficient and easy to deploy compared to VCB and other backup solutions. Several of our major backup partners have already released VADP integrated backup products and we expect most of the major backup partners to have VADP integrated backup software by the upcoming feature release of the vSphere platform in 2010.
Future Product Licensing
Given the strong interest and adoption of VADP by our backup eco-system and the benefits offered by VADP compared to VMware Consolidated Backup (VCB), we are announcing the End of Availability for VCB starting with next vSphere feature release in 2010. Starting with the next vSphere platform feature release, VCB will be removed from vSphere platform. VADP integrated backup products (including VMware Data Recovery) will be the recommended option for efficient backup and restoration of vSphere Virtual Machines. This will allow us to focus new value added feature development on VADP instead of two backup frameworks (VCB and VADP). You can find more information about the use of vStorage APIs for Data Protection in our Developer Community. For information on the availability of VADP integrated release of your backup product please contact your backup vendor.
End of Availability
With the release of the next vSphere platform, we will continue to provide the binaries for VCB, but they will not be compatible with the next platform release. We will continue to provide support for VCB on the current vSphere platform per the VMware support policy.
If you need assistance in the migration from VMware Consolidated Backup to the vStorage APIs for Data Protection, please contact your local reseller or storage backup vendor.
Best regards,
VMware Product Management
VMware released vStorage APIs for Data Protection (VADP) with the vSphere 4.0 release in May, 2009. VADP is the next generation of VMware’s backup framework. We have also been working with several backup partners to integrate VADP into their solutions to make backup of vSphere Virtual Machines fast, efficient and easy to deploy compared to VCB and other backup solutions. Several of our major backup partners have already released VADP integrated backup products and we expect most of the major backup partners to have VADP integrated backup software by the upcoming feature release of the vSphere platform in 2010.
Future Product Licensing
Given the strong interest and adoption of VADP by our backup eco-system and the benefits offered by VADP compared to VMware Consolidated Backup (VCB), we are announcing the End of Availability for VCB starting with next vSphere feature release in 2010. Starting with the next vSphere platform feature release, VCB will be removed from vSphere platform. VADP integrated backup products (including VMware Data Recovery) will be the recommended option for efficient backup and restoration of vSphere Virtual Machines. This will allow us to focus new value added feature development on VADP instead of two backup frameworks (VCB and VADP). You can find more information about the use of vStorage APIs for Data Protection in our Developer Community. For information on the availability of VADP integrated release of your backup product please contact your backup vendor.
End of Availability
With the release of the next vSphere platform, we will continue to provide the binaries for VCB, but they will not be compatible with the next platform release. We will continue to provide support for VCB on the current vSphere platform per the VMware support policy.
If you need assistance in the migration from VMware Consolidated Backup to the vStorage APIs for Data Protection, please contact your local reseller or storage backup vendor.
Best regards,
VMware Product Management
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)