Power on the host blade server.

When the BIOS boot screen appears, press F2 (or Ctrl-E from a remote console) to enter the BIOS Setup Utility.

Navigate to the Boot tab.

Select Boot Device Priority and press Enter.

The following two screens show examples of Intel and AMD-based BIOS Setup Utility screens. The actual screens might vary by plaform.

Select the first boot device position and presss Enter.

A drop-down list appears with the available boot devices listed.

From the drop-down list, select SUN 10GNem V1.9 GPL etherboot.org as the first boot device.

The following two screens show examples of Intel and AMD-based BIOS Setup Utility screens. The actual screens might vary by plaform.

Press F10 to Save and Exit the BIOS Setup Utility.

The host blade server reboots.

Connect the Ethernet cable to the NEM Ethernet port.

See the driver installation section in this chapter that corresponds with the operating system installed on the blade module.

Boot the server from the PXE server to load an OS or install an OS.

Power on the host server blade.

Follow the instructions in To Set Up the BIOS for Booting From the Virtualized NEM to set up the Virtualized NEM as the first network boot device.

Press F12 to boot from the network.

Power on the host server blade.

When prompted, press F8 to display the boot choices list.

Select the SUN 10GNem V1.9 GPL etherboot.org NIC from the boot list.

Press Enter to boot from the PXE server.

Install and configure the hxge driver. See the driver installation section in this chapter that corresponds with the operating system installed on the blade module.

Install and configure the hxge driver.

See the driver installation section in this chapter that corresponds with the operating system installed on the blade module.

Locate and copy the hxge device driver software from the Tools and Drivers CD for the server module on which you want to install the driver.

The Solaris drivers are located in one of two directories:

/solaris/x64/

/solaris/sparc/

Uncompress the gzipped tar file. For example:

# gunzip hxge.tar.gz

Unpack the tar file. For example:

# tar -xvf hxge.tar

Install the software packages by typing the following at the command line:

#/usr/sbin/pkgadd -d .

A menu similar to the following displays:

The following packages are available:
 
  1 SUNWhxge SUN 10Gb hxge NIC Driver
                    (i386) 11.10.0,REV=2008.04.24.11.05
 
Select package(s) you wish to process (or ’all’ to process
all packages). (default: all) [?,??,q]:

Select the packages to install.

• Press Return or type all to accept the default and install all packages.

• Type the specific numbers, separated by a space, if you prefer not to install any optional packages.

  The following is an example of the displayed output:

  
  

  SUN 10Gb hxge NIC Driver(i386) 11.10.0,REV=2008.04.24.11.05 Copyright 2008 Sun Microsystems, Inc.All rights reserved. Use is subject to license terms. Using </> as the package base directory. ## Processing package information. ## Processing system information. 3 package pathnames are already properly installed. ## Verifying package dependencies. ## Verifying disk space requirements. ## Checking for conflicts with packages already installed. ## Checking for setuid/setgid programs. This package contains scripts which will be executed with super-user permission during the process of installing this package Do you want to continue with the installation of<SUNWhxge>[y,n,?]

  
  

Type y to continue the installation.

The following is an example of the displayed output for a successfully installed driver:

Installing SUN 10Gb hxge NIC Driver as <SUNWhxge>
## Installing part 1 of 1.
/kernel/drv/amd64/hxge
/kernel/drv/hxge
[ verifying class <none> ]
[ verifying class <renamenew> ]
## Executing postinstall script.
System configuration files modified but hxge driver not loaded or attached.
Installation of <SUNWhxge> was successful.

Determine which the driver packages were installed.

# pkginfo | grep SUNWhxge
system      SUNWhxge SUN 10Gb hxge NIC Driver

Remove the driver packages with the pkgrm command, followed by the names of an installed packages.

# pkgrm SUNWhxge  any addtional package
names

At the command line, use the grep command to search the /etc/path_to_inst file for hxge interfaces.

# grep hxge /etc/path_to_inst
"/pci@7c,0/pci10de,5d@e/pci108e,aaaa@0" 0 "hxge"

In this example, the device instance is from a Sun Blade 6000 Virtualized Multi-Fabric 10GbE Network Express Module installed in the chassis. The instance number is shown in italics in this example.

Set up the NEM’s hxge interface.

Use the ifconfig command to assign an IP address to the network interface. Type the following at the command line, replacing ip-address with the NEM’s IP address:

# ifconfig hxge0 plumb ip-address netmask netmask-address broadcast + up

Refer to the ifconfig(1M) man page and the Solaris documentation for more information.

(Optional) For a setup that remains the same after you reboot, create an /etc/hostname.hxgenumber file, where number is the instance number of the hxge interface you plan to use.

To use the NEM’s hxge interface in the Step 1 example, create an /etc/hostname.hxgex file, where x is the number of the hxge interface. If the instance number were 1, the filename would be /etc/hostname.hxge1.

Follow these guidelines for the host name:

• The /etc/hostname.hxgenumber file must contain the host name for the appropriate hxge interface.

• The host name must be different from the host name of any other interface. For example: /etc/hostname.hxge0 and /etc/hostname.hxge1 cannot share the same host name.

• The host name must have an IP address listed in the /etc/hosts file.

  The following example shows the /etc/hostname.hxgenumber file required for a system namedzardoz-c10-bl1.

  
  

  # cat /etc/hostname.hxge0 zardoz-c10-bl1

  
  

Create an appropriate entry in the /etc/hosts file for each active hxge interface.

For example:

# cat /etc/hosts
#
# Internet host table
#
127.0.0.1     localhost
129.168.1.29 zardoz-c10-bl1

Change a parameter by uncommenting the line in the /kernel/drv/hxge.conf file and providing a new value.

The following is the content of the /kernel/drv/hxge.conf file. All parameters are listed and explained in this file. The default values are loaded when the hxge driver is started.

# cat /kernel/drv/hxge.conf
#
#
# driver.conf file for Sun 10Gb Ethernet Driver (hxge)
#
#
#------- Jumbo frame support ---------------------------------
# To enable jumbo support,
# accept-jumbo = 1;
#
# To disable jumbo support,
# accept-jumbo = 0;
#
# Default is 0.
#
#
#------- Receive DMA Configuration ----------------------------
#
# rxdma-intr-time
# 		Interrupts after this number of NIU hardware ticks have
# 		elapsed since the last packet was received.
# 		A value of zero means no time blanking (Default = 8).
#
# rxdma-intr-pkts
# 		Interrupt after this number of packets have arrived since
# 		the last packet was serviced. A value of zero indicates
# 		no packet blanking (Default = 0x20).
#
# Default Interrupt Blanking parameters.
#
# rxdma-intr-time = 0x8;
# rxdma-intr-pkts = 0x20;
#
#
#------- Classification and Load Distribution Configuration ------
#
# class-opt-****-***
# 		These variables define how each IP class is configured.
# 		Configuration options includes whether TCAM lookup
# 		is enabled and whether to discard packets of this class
#
# 		supported classes:
# 		class-opt-ipv4-tcp class-opt-ipv4-udp class-opt-ipv4-sctp
# 		class-opt-ipv4-ah class-opt-ipv6-tcp class-opt-ipv6-udp
# 		class-opt-ipv6-sctp class-opt-ipv6-ah
# 		Configuration bits (The following bits will be decoded
# 		by the driver as hex format).
#
#
# 		0x10000:			TCAM lookup for this IP class
# 		0x20000:			Discard packets of this IP class
#
# class-opt-ipv4-tcp = 0x10000;
# class-opt-ipv4-udp = 0x10000;
# class-opt-ipv4-sctp = 0x10000;
# class-opt-ipv4-ah = 0x10000;
# class-opt-ipv6-tcp = 0x10000;
# class-opt-ipv6-udp = 0x10000;
# class-opt-ipv6-sctp = 0x10000;
# class-opt-ipv6-ah = 0x10000;
#
#
#------- FMA Capabilities ---------------------------------
#
# Change FMA capabilities to non-default
#
# DDI_FM_NOT_CAPABLE 0x00000000
# DDI_FM_EREPORT_CAPABLE 0x00000001
# DDI_FM_ACCCHK_CAPABLE 0x00000002
# DDI_FM_DMACHK_CAPABLE 0x00000004
# DDI_FM_ERRCB_CAPABLE 0x00000008
#
# fm-capable = 0xF;
#
# default is DDI_FM_EREPORT_CAPABLE | DDI_FM_ERRCB_CAPABLE = 0x5

In the following example, the NEM discards the TCP traffic for this blade system. In other words, the hxge driver does not receive any TCP traffic.

class-opt-ipv4-tcp = 0x20000;

In the following example, the FMA functionality will be disabled.

fm-capable = 0x0;

For the new parameters to be effective, reload the hxge driver or reboot the system.

Use the ifconfig command to identify the instance associated with hxge device.

# ifconfig -a
hxge0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
inet 192.168.1.29 netmask ffffff00 broadcast 192.168.1.255
ether 0:14:4f:62:1:3

List all of the parameters supported by the hxge driver.

# ndd -get /dev/hxge0 ?
?                             (read only)instance                      (read only)
rxdma_intr_time               (read and write)
rxdma_intr_pkts               (read and write)
class_opt_ipv4_tcp            (read and write)
class_opt_ipv4_udp            (read and write)
class_opt_ipv4_ah             (read and write)
class_opt_ipv4_sctp           (read and write)
class_opt_ipv6_tcp            (read and write)
class_opt_ipv6_udp            (read and write)
class_opt_ipv6_ah             (read and write)
class_opt_ipv6_sctp           (read and write)
 

Note that read only parameters cannot be changed.

Display the value of a parameter.

The following is an example for the rxdma_intr_time parameter:

# ndd -get /dev/hxge0 rxdma_intr_time
8

Modify the value of a parameter.

The following is an example for the rxdma_intr_time parameter. It changes the rxdma_intr_time parameter from 0x8 to 0x10:

# ndd -set /dev/hxge0 rxdma_intr_time 0x10
# ndd -get /dev/hxge0 rxdma_intr_time
10

Use the ifconfig command to obtain a list of the current Ethernet network interfaces.

host #> ifconfig -a | grep eth
eth0      Link encap:Ethernet  HWaddr 00:14:4F:E2:BA:34  
eth1      Link encap:Ethernet  HWaddr 00:14:4F:E2:BA:35 

After you have installed the Virtualized Multi-Fabric 10GbE NEM hardware and installed and loaded the driver, a new eth device appears. This will be the eth device for the NEM.

Locate and copy the hxge device driver .zip file from the Tools and Drivers CD for the server module operating system on which you want to install the driver.

The drivers are located in one of the following directories:

/linux/drivers/rhel5.1

/linux/drivers/rhel5.2

/linux/drivers/rhel4.7

/linux/drivers/sles10sp2

Uncompress and unpack the driver download file, if necessary.

The following example shows all the files extracted into a tge10 subdirectory (The command sample below has been edited for brevity. Sections marked {....} denote output that has been removed for this example):

host #> mkdir tge10
host #> cd tge10Archive:  sun_10_Gigabit_Ethernet_driver_update_10.zip
host #> unzip sun_10_Gigabit_Ethernet_driver_update_10.zip creating: Linux/
creating: Linux/RHEL4.7/
creating: Linux/RHEL4.7/2.6.9-78.ELlargesmp/
[...]
creating: Linux/RHEL4.7/2.6.9-78.ELsmp/
[...]
creating: Linux/src/
extracting: Linux/src/hxge_src.zip creating: Linux/RHEL5/
[...]
creating: Linux/SUSE10-SP2/
[...]
creating: Docs/
inflating:Docs/x8_Express_Dual_10GBE_Low_Profile_Release_Notes.pdf 
inflating:Docs/x8_Express_Quad_Gigabit_Ethernet_Express_Module_Release_Notes.pdf inflating: Docs/x8_Express_Quad_Gigabit_Ethernet_Low_Profile_Release_Notes.pdf 
inflating: Docs/x8_Express_Dual_10GBE_Express_Module_Release_Notes.pdf creating: Firmware/
[...]
creating: Windows/
[...]
host #>
 
 
 
 
 

Select and install the appropriate OS driver package.

1. Navigate to the Linux directory that contains the driver-specific files. For example:

   
   

   host #> ls -l total 47908drwxr-xr-x 2 root root 4096 Sep 25 16:31 Docs drwxr-xr-x 2 root root 4096 Sep 25 18:46 Firmware drwxr-xr-x 12 root root 4096 Sep 25 16:31 Linux -rw-r--r-- 1 root root 48984046 Oct 7 12:13 sun_10_Gigabit_Ethernet_driver_update_10.zip drwxr-xr-x 2 root root 4096 Sep 25 16:31 Windows   host #> cd Linux host #> ls -ldrwxr-xr-x 4 root root 4096 Sep 25 16:30 RHEL4.7 total 40drwxr-xr-x 2 root root 4096 Sep 25 16:30 RHEL5.2 drwxr-xr-x 2 root root 4096 Sep 25 16:30 src drwxr-xr-x 3 root root 4096 Sep 25 16:31 SUSE10-SP2

   
   

   If you are not sure what release you are running, use the lsb_release command to show information about your host operating system

   .

   
   

   host #>lsb_release -a Distributor ID: RedHatEnterpriseServer Description: Red Hat Enterprise Linux Server release 5.2 (Tikanga) Release: 5.2 Codename: Tikanga

   
   

2. Identify the OS-specific subdirectory and verify that no hxge driver is currently installed; for example: RHEL5.2 for RedHat Enterprise Linux 5 Update 2, or SUSE10-SP2 for Novell’s SuSE Linux Enterprise Server 10 Service Pack 2

   The following example uses RHEL5.2:

   
   

   host #> cd RHEL5.2 host #> ls -l-rw-r--r-- 1 root root 2752340 Oct 7 12:35 hxge-1.1.1_rhel52-1.x86_64.rpm total 2692host #> rpm -q hxge package hxge is not installed

   
   
   

   ---

   Note - If an hxge driver is already installed, uninstall the driver, in order to avoid complications. See To Remove the Driver From a Linux Platform for instructions on removing the driver. The update command (rpm -u) is not supported for updating the hxge driver.

   ---

   
   

3. Install the appropriate package (.rpm) file.

   
   

   host #> rpm -ivh hxge-1.1.1_rhel52-1.x86_64.rpm Preparing... ########################################### [100%] 1:hxge ########################################### [100%] post Install Done

   
   

   Once you have installed the hxge driver, you can immediately load the driver. If the NEM is physically and electrically installed, the driver automatically attaches to it and make it available to the system. Alternatively, on the next system reset and reboot, the hxge driver automatically loads if there are any NEM devices present and detected.

Load the driver.

1. Verify that the NEM is available to the system (that is, it is actively on the PCIe I/O bus).

   The command sample below has been edited for brevity. Sections marked [....] denote output that has been removed.

   
   

   host #> lspci [...]07:00.0 Ethernet controller: Sun Microsystems Computer Corp. Unknown device abcd (rev 01) [...] 84:00.0 Ethernet controller: Intel Corporation 82575EB Gigabit Network Connection (rev 02) [...] 85:00.0 Ethernet controller: Sun Microsystems Computer Corp. Unknown device aaaa (rev 01)

   
   

   Device code 0xAAAA (Unknown device aaaa (rev 01) output) is the Virtualized NEM Device; presence of this line indicates the NEM is visible and available to the system.

2. Manually load the hxge driver.

   
   

   host #> modprobe hxge

   
   

3. Verify the driver is loaded.

   
   

   host #>lsmod | grep hxge hxge 168784 0 host #>modinfo hxgefilename: /lib/modules/2.6.18-92.el5/kernel/drivers/net/hxge.ko version: 1.1.1 license: GPL description: Sun Microsystems(R) 10 Gigabit Network Driver author: Sun Microsystems, <james.puthukattukaran@sun.com> srcversion: B61926D0661E6A268265A9C alias: pci:v0000108Ed0000AAAAsv*sd*bc*sc*i* depends: [etc.]

   
   

   • If you get the output above, the driver is loaded into memory and actively running.

   • If the modprobe command fails, you will receive the following output:

     
     

     host #> modprobe hxge FATAL: Module hxge not found.

     
     

     This indicates that you probably installed the wrong driver version. Uninstall the hxge driver and install the correct package for your Linux release.

     If you are running a custom or patched kernel, you might have to build a custom driver to match your custom kernel.

Identify the NEM eth device.

Once the NEM has been correctly installed, and the hxge software driver has been successfully installed and loaded, the new NEM eth device will be visible.

1. Execute the following command to view the available eth devices.

   
   

   host #> ifconfig -a | grep eth eth0 Link encap:Ethernet HWaddr 00:14:4F:E2:BA:34 eth1 Link encap:Ethernet HWaddr 00:14:4F:E2:BA:35 eth2 Link encap:Ethernet HWaddr 00:14:4F:62:01:08

   
   

   In this example, eth0 and eth1 were previously present; eth2 is new, this is the NEM Ethernet network interface device. If you had installed two NEMs, you would also see an eth3 device representing the other NEM. You can identify each eth device (NEM0 or NEM1) by matching the Ethernet MAC address with the one you recorded and saved when you physically installed the NEM into the chassis in Chapter 2.

2. Make sure that the eth2 driver is the correct Ethernet driver for the Virtualized NEM.

   
   

   host #> ethtool -i eth2 driver: hxgeversion: 1.1.1 firmware-version: N/A bus-info: 0000:85:00.0

   
   

3. For more detail on eth2, use the ifconfig command.

   
   

   host #>ifconfig eth2 eth2 Link encap:Ethernet HWaddr 00:14:4F:62:01:08 BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) Memory:b7000000-b8000000

   
   

   The eth2 device is active and available to the system, but has not yet been configured (assigned an IP address). See the next section for details on configuring the NEM for the Linux OS.

Use the modprobe -r command to unload the hxge driver at any time, without actually uninstalling the driver.

host #> lsmod | grep hxge
hxge 168784 0 host #> modprobe -r hxge
host #> lsmod | grep hxge
host #>
 

Once unloaded, you can manually load the hxge driver again, using the modprobe command; the driver has not been uninstalled.

Uninstall the hxge driver.

This command permanently removes the hxge driver and all related files from the system (you will have to reinstall it again before you can use the NEM):

host #> rpm -q hxge
hxge-1.1.1_rhel52-1host #> rpm -e hxge
Uninstall Done.
 

Check the current frame size (MTU) value.

host #>ifconfig eth2 
eth2      Link encap:Ethernet  HWaddr 00:14:4F:29:00:01 		inet addr:10.1.10.150  Bcast:10.1.10.255  Mask:255.255.255.0
		inet6 addr: fe80::214:4fff:fe29:1/64 Scope:Link
		UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
		RX packets:1 errors:0 dropped:0 overruns:0 frame:0
		TX packets:30 errors:0 dropped:0 overruns:0 carrier:0
		collisions:0 txqueuelen:1000 
		RX bytes:150 (150.0 b)  TX bytes:7850 (7.6 KiB)
		Memory:fb000000-fc000000 
 

Note that in this example, eth2 (the NEM from previous examples) is currently running with the standard MTU of 1500 bytes.

Set the desired new value. For a 9000 byte example:

host #>ifconfig eth2 mtu 9000

Verify the setting.

host #>ifconfig eth2 
eth2      Link encap:Ethernet  HWaddr 00:14:4F:29:00:01 		inet addr:10.1.10.150  Bcast:10.1.10.255  Mask:255.255.255.0
		inet6 addr: fe80::214:4fff:fe29:1/64 Scope:Link
		UP BROADCAST RUNNING MULTICAST  MTU:9000  Metric:1
		RX packets:26 errors:0 dropped:0 overruns:0 frame:0
		TX packets:40 errors:0 dropped:0 overruns:0 carrier:0
		collisions:0 txqueuelen:1000 
		RX bytes:3900 (3.8 KiB)  TX bytes:9352 (9.1 KiB)
		Memory:fb000000-fc000000
 

Note that ifconfig now reports the MTU size to be 9000 bytes. NFS 8KB pages will now flow (send or receive) as a single Ethernet packet.

Set the MTU parameter in the corresponding ifcfg file (ifcfg-eth2 for the examples in this document). For example:

host #>cat /etc/sysconfig/network-scripts/ifcfg-eth2 
# Sun NEM Hydra 10GbEDEVICE=eth2
BOOTPROTO=static
HWADDR=00:14:4F:29:00:00
IPADDR=10.1.10.150
NETMASK=255.255.255.0
MTU=9124
ONBOOT=no
 

Restart the interface.

1. If the driver is currently installed and running, take the interface down.

   
   

   host #>ifdown eth2

   
   

2. Bring the interface up.

   
   

   host #>ifup eth2

   
   

Verify that MTU value for the hgxe device is as specified.

host #>ifconfig eth2 
eth2      Link encap:Ethernet  HWaddr 00:14:4F:29:00:01 		inet6 addr: fe80::214:4fff:fe29:1/64 Scope:Link
		UP BROADCAST RUNNING MULTICAST  MTU:9124  Metric:1
		RX packets:0 errors:0 dropped:0 overruns:0 frame:0
		TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
		collisions:0 txqueuelen:1000 
		RX bytes:0 (0.0 b)  TX bytes:2670 (2.6 KiB)
		Memory:fb000000-fc000000
 

In the Device Manager, right-click on the Sun Blade 6000 10Gbe Networking Controller and select Properties.

Select the Advanced Tab, then select Jumbo Frames as shown below.

Select the enabled option and click OK to enable the Jumbo Frames feature.

Obtain the hxge driver from one of the following:

• The Virtualized NEM Tools and Drivers CD: /vmware/drivers/esx3.5u4/Vmware-esx-drivers-net-hxge-1.2.2. 11-00000.i386.rpm

• Download the hxge driver from the following site: http://download3.vmware.com/software/esx/esx350-hxge-1.2.2.11-201041.isoand create a driver CD.

Start the ESX Server machine and log in to service console as root.

Place the driver CD in the CD-ROM drive of the server.

Mount the driver CD.

Do one of the following:

• If you created a driver CD from the VMware download site, change the directory to the VMupdates/RPMS/

• If you are using the Tools and Drivers CD, change to /vmware/drivers/esx3.5u4/

Do one of the following:

• If the NEM is already installed in the modular system chassis, run the following command.

  esxupdate update

  The server reboots after the driver update.

• If the NEM is not already installed in the modular system, run the esxupdate command with the ---noreboot option, shut down the host machine manually, install the NEM, and then boot the host machine.

  This allows you to install in a single boot.

  
  

  ---

  Note - Remove the driver CD from the CD-ROM drive before the server reboots.

  ---

  
  

After the server reboots, log in to ESX Server.

Do the following to verify that the driver is installed successfully:

1. Run the esxupdate query command and verify that the information about the driver is mentioned in the resulting message.

2. View the PCI ID XML file in the /etc/vmware/pciid/ directory.

   The driver information is available in the file.

3. Check for the latest version of the driver module in /usr/lib/vmware/vmkmod/

4. To verify that the driver is loaded and functioning, run the vmkload_mod -l command.

   The driver is listed in the displayed list.

Obtain the hxge driver from one of the following:

• The Virtualized NEM Tools and Drivers CD: /vmware/drivers/esx4.0/Vmware-esx-drivers-net-hxge-1.2.2.11- 00000.i386.rpm

• Download the hxge driver from the following site: http://www.vmware.com/support/vsphere4/doc/drivercd/esx-hxge_400.4.1.2.2.7.htmland create a driver CD.

Power on the ESX or ESXi host.

Place the driver CD in the CD-ROM drive of the host where either the vSphere CLI package is installed or vMA is hosted.

Mount the driver CD.

Navigate to cd-mountpoint/offline-bundle/ and locate the hxge-vmware-driver-4-1-2-2-7-offline_bundle-193789.zip file.

Execute the command esxupdate to update the driver:

# vihostupdate conn_options --install --bundle hxge-vmware-driver-4-1-2-2-7-offline_bundle-193789.zip

For more details on vihostupdate, see http://www.vmware.com/pdf/vsphere4/r40/vsp_40_vcli.pdf

Obtain the hxge driver from one of the following:

• The Virtualized NEM Tools and Drivers CD /vmware/drivers/esx4.0/Vmware-esx-drivers-net-hxge-1.2.2.11- 00000.i386.rpm

• Download the hxge driver from the following site: http://www.vmware.com/support/vsphere4/doc/drivercd/esx-hxge_400.4.1.2.2.7.htmland create a driver CD.

Power on the ESX or ESXi host and log in as administrator.

Place the driver CD in the CD-ROM drive of the ESX host.

Mount the driver CD.

Navigate to cd-mountpoint/offline-bundle/ and locate the hxge-vmware-driver-4-1-2-2-7-offline_bundle-193789.zip file.

Execute the command esxupdate to update the driver:

# esxupdate --bundle= hxge-vmware-driver-4-1-2-2-7-offline_bundle-193789.zip update.

For more details on esxupdate, see http://www.vmware.com/pdf/vsphere4/r40/vsp_40_esxupdate.pdf

Obtain the hxge driver from one of the following:

• The Virtualized NEM Tools and Drivers CD: /vmware/drivers/esx3.5u4/Vmware-esx-drivers-net-hxge-1.2.2.11-00000.i386.rpm

• Download the hxge driver from the following site: http://download3.vmware.com/software/esx/esx350-hxge-1.2.2.11-201041.isoand create a driver CD.

Place the driver CD in the CD-ROM drive of the host machine.

Start the host machine.

When prompted for an upgrade or installation, press Enter for graphical mode.

Choose the language you prefer.

Select a keyboard type.

After you are prompted to swap the driver CD with the ESX Server installation CD, insert the ESX Server 3.5 Update 3 installation CD and continue with ESX Server installation.

See http://www.vmware.com/pdf/vi3_301_201_installation_guide.pdffor detailed ESX installation instructions.

After ESX Server is installed and the system reboots, log in to ESX Server.

Verify that the driver is installed successfully:

1. Run the esxupdate query command.

   A message containing the information about the driver appears.

2. View the PCI ID XML file in the /etc/vmware/pciid/ directory.

   The driver information is available in the file.

3. Check for the latest version of the driver module in the following directory: /usr/lib/vmware/vmkmod/

4. To verify that the driver is loaded and functioning, enter the following command:

   vmkload_mod -l

   The driver is listed in the displayed list.

Obtain the hxge driver from one of the following:

• The Virtualized NEM Tools and Drivers CD: /vmware/drivers/esx4.0/Vmware-esx-drivers-net-hxge-1.2.2.11- 00000.i386.rpm

• Download the hxge driver from the following site: http://www.vmware.com/support/vsphere4/doc/drivercd/esx-hxge_400.4.1.2.2.7.htmand create a driver CD.

Place the ESX installation DVD in the DVD drive of the host.

Accept the terms of the license agreement.

Select a keyboard type.

When prompted for Custom Drivers, select Yes to install custom drivers.

Click Add to eject the ESX installation DVD.

Place the driver CD in the DVD drive of the ESX host.

Select the driver module to import drivers to the ESX host.

Click Next to continue.

A dialog box displays the following message: Load the system drivers.

Click Yes.

After the drivers are installed, replace the driver CD with the ESX installation DVD when prompted to continue the ESX installation.

Log in to the ESX host using Virtual Infrastructure Client GUI.

Click the Configuration Tab, then select Network Adapters from the Hardware list on the left side of the GUI.

Select the Sun Blade 6000 10GbE Network Controller driver that you want to configure.

Configure Networking using the Sun Blade 6000 10GbE Network Controller as you would any other network interface.

For more information on network configuration for ESX, refer

ESX Server 3 Configuration Guide available at: http://www.vmware.com/support/pubs/vi_pages/vi_pubs_35u2.htmlor

ESX Configuration Guide for ESX 4.0 available at:

http://www.vmware.com/support/pubs/vs_pages/vsp_pubs_esx40_vc40.html

Log in directly to your ESX Server host console.

Set the MTU size to the largest MTU size among all the virtual network adapters connected to the vSwitch. To set the MTU size for the vSwitch, run the following command:

esxcfg-vswitch -m MTU vSwitch

where MTU is the MTU size and vSwitch is the name that has been assigned to the vSwitch.

This command sets the MTU for all uplinks on that vSwitch.

To display a list of vSwitches on the host, run the following command:

esxcfg-vswitch -l

Check that the configuration of the vSwitch is correct.

Log in directly to your ESX Server host console.

To create a VMkernel connection with Jumbo Frame support, run the following command:

esxcfg-vmknic -a -i ip address -n netmask -m MTU portgroup name

where ip address is the ip addresss of the server, netmask is the netmask address, MTU is the MTU size and portgroup name is the name that has been assigned to the port group.

To display a list of VMkernel interfaces, run the following command:

esxcfg-vmknic -l

Check that the configuration of the Jumbo Frame-enabled interface is correct.