Download and Install the Drivers

The following instructions apply to both drivers, sxge and sxgevf. When downloading and installing, specify which driver you want.

To use the sxgevf driver, you need to have the sxge driver already installed.

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:CA:15:68  
eth1      Link encap:Ethernet  HWaddr 00:14:4F:CA:15:69  
```
After you have installed the NEM and installed and loaded a driver, a new eth device is displayed. This is the eth device for the NEM.
Access the sxge drivers through one of the following methods:
- Locate and copy the sxge device driver.zip or sxgevf device driver.zip file from the Tools and Drivers CD for the server module operating system on which you want to install the driver.
  For Oracle Enterprise Linux, use the corresponding Red Hat Enterprise Linux driver.
  The drivers are located in the following directories:
  /linux/drivers/rhel5.4
  /linux/drivers/sles10sp3
  /linux/drivers/sles11
  
  Note - Linux source files are available at /linux/drivers/src.
- Download latest driver packages from the the following web site:
  http://support.oracle.com
  1. At the My Oracle Support site, log in.
    An account is required to download software. You must register if you do not have an account.
  2. Click the Patches & Updates tab.
  3. Click “Product or Family” (Advance search).
  4. In the Product field, type Sun Blade 6000 Virtualized 40GbE NEM.
  5. In the Release field, select the newest release, then click the arrow next to the Sun Blade 6000 Virtualized 40GbE NEM folder.
  6. Click the Search button.
  7. Download the latest available firmware package, and extract it to an accessible folder on the network.
If you are downloading the sxgevf driver, make sure that SR-IOV mode is enabled before installing the driver. (See Setting Blade Parameters.)

Once the Linux drivers package is downloaded, uncompress and unpack the driver and other files.

In the following example, the download directory is tge10:

host #>mkdir tge10
host #>cp xxx/p12918641_100_Generic.zip
host #>cd tge10
host #>unzip p12918641_100_Generic.zip
host #>ls
readme.html
Sun_Blade_6000_Virtualized_40GbE_NEM_1_0_4.xml
Sun_Blade_6000_Virtualized_40GbE_NEM_1_0_4.zip
host #>unzip Sun_Blade_6000_Virtualized_40GbE_NEM_1_0_4.zip
host #>ls
host #>firmware fpga  license  linux  solaris  windows  release_note

Select and install the appropriate OS driver package.

In the following example, RHEL6.0 Linux driver is selected for REHL version 6.0.

Navigate to the Linux directory that contains the driver package that is appropriate for your OS.

host #> cd linux/RHL6.0
host #>ls
kmod-sxge-1.0-0.x86_64.rpm sxge-debuginfo-1.0-0.x86_64.rpm
kmod-sxgevf-1.0-0.x86_64.rpm  sxgevf-debuginfo-1.0-0.x86_64.rpm

In the following example, the file kmod-sxgevf-1.0-0.x86_64.rpm is the package that will be installed.

If you are not sure which release your system is running, use the lsb_release command to show information about your host's operating system.

host #> lsb_release -a
LSB Version:
core-4.0-intel64:core-4.0-noarch:graphics-4.0-intel64:graphics-
4.0-noarch:printing-4.0-intel64:printing-4.0-noarch
Distributor ID: RedHatEnterpriseServer
Description: Red Hat Enterprise Linux Server release 6.0 (Santiago)
Release: 6.0
Codename: Santiago
host #> rpm -q kmod-sxgevf-1.0-0.x86_64
package kmod-sxgevf-1.0-0.x86_64 is not installed

Identify the OS-specific subdirectory, and verify that the driver you want to install (sxge or sxgevf) is not currently installed.
Note - If the driver is already installed, uninstall the driver to avoid complications. See Remove the Drivers for instructions. The update command (rpm -u) is not supported for updating the drivers.

Install the appropriate package (.rpm) file.

host #> rpm -ivh --nodeps kmod-sxge-1.0-0.x86_64.rpm  
Preparing...                ########################################### [100%]
     1:kmod-sxge                   ########################################### [100%]
post Install Done

host #> rpm -ivh --nodeps kmod-sxgevf-1.0-0.x86_64.rpm  
Preparing...                ########################################### [100%]
     1:kmod-sxgevf ######################################### [100%]
post Install Done

Note - To load and use the sxgevf driver, you must have the sxge driver already installed.

Load the driver.

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

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

host #> lspci 
[...]
13:00.0 PCI bridge: Oracle Corporation Unknown Device 2070
14:02.0 PCI bridge: Oracle Corporation Unknown Device 2070
14:03.0 PCI bridge: Oracle Corporation Unknown Device 2070
15:00.0 Ethernet controller: Sun Microsystems Computer Corp. 
Unknown device 207a (rev 01)
15:00.2 Ethernet controller: Sun Microsystems Computer Corp. 
Unknown device 207b (rev 01)
15:00.3 Ethernet controller: Sun Microsystems Computer Corp. 
Unknown device 207b (rev 01)
16:00.0 Ethernet controller: Sun Microsystems Computer Corp. 
Unknown device 207a (rev 01)
16:00.1 Ethernet controller: Sun Microsystems Compute Corp. 
Unknown device 207b (rev 01)
16:00.2 Ethernet controller: Sun Microsystems Computer Corp. 
Unknown device 207b (rev 01)
16:00.3 Ethernet controller: Sun Microsystems Computer Corp. 
Unknown device 207b (rev 01)
[...]

host #> lspci
[...]
19:00.0 PCI bridge: Sun Microsystems Computer Corp. 
Unknown device 2070 (rev 01)
1a:02.0 PCI bridge: Sun Microsystems Computer Corp. 
Unknown device 2070 (rev 01)
1a:03.0 PCI bridge: Sun Microsystems Computer Corp. 
Unknown device 2070 (rev 01)
1b:00.0 Ethernet controller: Sun Microsystems Computer Corp. 
Unknown device 2078 (rev 01)
1c:00.0 Ethernet controller: Sun Microsystems Computer Corp. 
Unknown device 2078 (rev 01)
[...]

Device code 0x2078 is the NEM device when used as a regular PCI device.
Device code 0x207a is the PF (using sxge driver) NEM device when SR-IOV is enabled.
Device code 0x207b is the VF (using sxgevf driver) NEM device when SR-IOV is enabled.

Presence of this line indicates the NEM is visible and available to the system.

Manually load the driver.
```
host #> modprobe sxge or sxgevf
```

Verify the driver is loaded.

host #> lsmod | grep sxge
sxge 71304 0  
host#> modinfo sxge
filename:       /lib/modules/2.6.18-238.el5/extra/sxge/sxge.ko
version:        0.06032011
license:        GPL
description:    SXGE ethernet driver
author: 
srcversion:     73779771D7EA5154342838B
alias:          pci:v0000108Ed0000207Asv*sd*bc*sc*i*
alias:          pci:v0000108Ed00002078sv*sd*bc*sc*i*
depends:        
vermagic:       2.6.18-238.el5 SMP mod_unload gcc-4.1
parm:           debug:SXGE debug level (int)
[etc.]

host #> lsmod | grep sxgevf
sxge (or sxgevf) 71304 0  
host#> modinfo sxgevf
filename:       /lib/modules/2.6.18-238.el5/extra/sxgevf/sxgevf.ko
version:        0.06032011
license:        GPL
description:    SXGEVF ethernet driver
author: 
srcversion:     73779771D7EA5154342838B
alias:          pci:v0000108Ed0000207Asv*sd*bc*sc*i*
alias:          pci:v0000108Ed00002078sv*sd*bc*sc*i*
depends:        
vermagic:       2.6.18-238.el5 SMP mod_unload gcc-4.1
parm:           debug:SXGEVF debug level (int)
[etc.]

If you get the output shown in the previous examples, the drivers are loaded into memory and actively running.
If the modprobe command fails, you will see the following output:
```
host #> modprobe sxge or sxgevf
FATAL: Module sxge not found. 
FATAL: Module sxgevf not found. 
```
This output indicates that you probably installed the wrong driver version. Uninstall the driver, then 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.
After the NEM has been correctly installed, and the 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:CA:15:68  
eth1      Link encap:Ethernet  HWaddr 00:14:4F:CA:15:69  
eth2      Link encap:Ethernet  HWaddr 00:14:4F:29:00:1D  
```
  In this example, eth0 and eth1 were previously present. The eth2 device is for a new 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 Install a NEM.
2. Make sure that the eth2 driver is the correct Ethernet driver for the NEM.
```
host #> ethtool -i eth2 
driver: sxge
version: 0.06032011
firmware-version: 
bus-info: 0000:1b:00.0
driver: sxgevf
version: 0.01202011
firmware-version: 
bus-info: 0000:1c:00.0
```
3. For more detail on eth3, use the ifconfig command.
```
host #> ifconfig eth2 
Link encap:Ethernet  HWaddr FA:CE:00:00:FC:0F 
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)
Interrupt:194
```
  The eth2 device is active and available to the system, but has yet to be configured (assigned an IP address). See Configuring the Network Interface for details on configuring the NEM for the Linux OS.
Load the VF driver to the guest OS.
Refer to the Oracle VM Server for x86 XEN documentation.
http://docs.oracle.com/cd/E15458_01/index.htm

User's Guide

Download and Install the Drivers

Related Information

Skip Navigation Links
Exit Print View
	Sun Blade 6000 Virtualized 40 GbE Network Express Module User's Guide