TheVMguy’s Notable KB articles from the week

http://vmguy.com/wordpress/index.php has posted his weekly Notable KB articles from the week

Sorry, better late than never. Here’s last week’s collection from the 71 New/Updated KB Articles:

I thought the following where wroth a extensive read.

iSCSI and Jumbo Frames configuration on ESX 3.5

KB Article
1007654

Products

VMware ESX

Product Versions

VMware ESX 3.5.x

Symptoms

Large queues are seen while monitoring Jumbo Frames

Purpose

This article provides information related to setting up an NAS and iSCSI environment with Jumbo Frames.

Caution: This is not a VMware supported configuration.

Resolution

Important Jumbo Frame Information

The following is important information to know when using Jumbo Frames:

  • Any packet larger than 1500 MTU is a Jumbo Frame. ESX 3.5 supports frames up to 9kB (9000 Bytes). They are limited to data networking only (virtual machines and the VMotion network) on ESX 3i/3.5.

  • Jumbo Frames must be enabled for each vSwitch or VMkernel interface through the command‐line interface on your ESX Server 3 host.

  • To allow ESX Server 3 to send larger frames out onto the physical network, the network must support Jumbo Frames end to end for Jumbo Frames to be effective.

  • Before enabling jumbo frames, ensure the NIC or LOM supports jumbo frames.

  • VMware supports jumbo frames with the following vendors:

    • Intel (82546, 82571),

    • Broadcom (5708, 5706, 5709),

    • Netxen (NXB-10GXxR,

    • NXB-10GCX4),

    • Neterion (Xframe, Xframe II, Xframe E).

Creating a Jumbo Frames-enabled vSwitch
  1. Log in directly to your ESX Server 3 hosts console.
  2. Run the esxcfg-vswitch -m <MTU> <vSwitch> command to set the MTU size for the vSwitch.
    This command sets the MTU for all uplinks on that vSwitch. Set the MTU size to the largest MTU size among all the virtual network adapters connected to the vSwitch.

  3. Run the esxcfg-vswitch -l command to display a list of vSwitches on the host, and check that the configuration of the vSwitch is correct.

Creating a Jumbo Frames-enabled VMkernel interface

To create a Jumbo Frames-enabled VMkernel interface:

  1. Log in directly to your ESX Server 3 host’s console.

  2. Run the esxcfg-vmknic -a -i <ip address> -n <netmask> -m <MTU> <portgroup name> command to create a VMkernel connection with Jumbo Frame
    support.

  3. Run the esxcfg-vmknic -l command to display a list of VMkernel interfaces, and check that the configuration of the Jumbo Frame‐enabled interface is correct.
    Note: ESX Server 3 supports a maximum MTU size of 9000.

Microsoft Windows 64bit operating systems (Vista, 2003, and 2008) randomly fail

KB Article
1006576

Products
VMware ACE

VMware ESX

VMware ESXi

VMware Fusion

VMware Player

VMware Workstation

Product Versions

Any

Symptoms

  • Your Windows operating system fails or stops responding

  • A computer that is running an x64-based version of Windows Server 2003, Windows Vista, or Windows Server 2008 randomly restarts and generates a Stop error

  • The Stop error code may be:

    • 0x0000001E

    • 0x000000D1

    • or another Stop error code

Resolution

This is a Microsoft issue caused by a patch.

This problem occurs after you install Microsoft update 932596 on the computer. For more information, refer to http://support.microsoft.com/kb/950772.

Addtionaly,

Make sure to know the proper trouble shooting method’s when running A Fiber Channel array via VMware.

Troubleshooting ESX and ESXi connectivity to fibre channel arrays

Troubleshooting fibre channel storage connectivity

These both outline it well.

Thanks to The VMguy and VMware for the content.

Full Source Post http://vmguy.com/wordpress/index.php/archives/479