JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Sun Blade 6000 Virtualized 40 GbE Network Express Module

User's Guide

search filter icon
search icon

Document Information

Using This Documentation

Related Documentation

Feedback

Support and Accessibility

Understanding the NEM

Task Overview

Product Features

Understanding the Components

SAS Connections

Ethernet Connections

10GbE NIC Virtualization

Fabric Express Modules

Processor

Identifying Ports and LEDs

Connector Locations

External NEM Ports

RJ-45 Ethernet Connector Port LEDs

NEM Front Panel and LEDs

Performing Hot-plug Insertion and Removal

Performing PCIe Hot-plug

Understanding PCIe Hot-plug

Prepare the PCIe Interface for Hot-plug Removal

Performing SAS Interface Hot-plug

Prepare SAS Interfaces for Hot-plug Removal

Restoring SAS Configurations After NEM Installation

Saving the Zoning Configuration to a Backup File

Recovering Zoning Configurations

Installing or Replacing a NEM

Before Installing a NEM

Determine the CMM Part Number Using ILOM 3.0x Web Interface

Determine the CMM Part Number Using ILOM 3.1x Web Interface

Determine the CMM Part Number Using ipmitool

Find the CMM Part Number on the CMM Label

Install a NEM

Verifying NEM Installation

Verify Installation (CMM ILOM Web)

Verify Installation (CMM ILOM CLI)

Remove a NEM

Replace a NEM

Installing and Removing SFP+ Optical Transceiver Modules

Install an SFP+ Optical Transceiver Module

Remove an Optical Transceiver SFP+ Module

SFP+ Connector Cabling Options

Enabling Jumbo Frames

Configuring Jumbo Frames (Solaris)

Jumbo Frames Overview

Jumbo Frames Configurations and Driver Statistics

Enable Jumbo Frames (Solaris)

Check Layer 2 Configuration

Check Layer 3 Configuration

Configuring Jumbo Frames (Linux)

Temporarily Configure Jumbo Frames (Linux)

Permanently Enable Jumbo Frames (Linux)

Enable Jumbo Frames (Windows)

Configuring Jumbo Frames (VMware ESX)

Create a Jumbo Frames-Enabled vSwitch (VMWare)

Create a Jumbo Frames-Enabled VMkernel Interface (VMWare

Configuring Static Link Aggregation

Example (Oracle Solaris 11 OS)

Example (Oracle Solaris 10 OS)

Example (Linux OS)

Booting an x86 Server Over the Network

Booting the NEM on an x86 Blade Server Over the Network

Set Up the BIOS for Booting From the NEM

Use the F12 Key to Initiate the Network Boot

Use the F8 Key to Boot Off the PXE Server

Boot a SPARC Blade Over the Network

Installing Drivers on Oracle Solaris OS SPARC or x86 Platform

Download the sxge Driver

Configure the Network Host Files

Configure the sxge Device Driver Parameters

Installing Drivers on a Linux Platform

Downloading, Installing, and Removing Drivers

Download and Install the Drivers

Remove the Drivers

Configuring the Network Interface

Temporary Network Interface Configuration

Permanent Network Interface Configuration

Bring the Interface Online Manually

Configure the Network Interface File Automatically for Red Hat Linux

Configure the Network Interface Automatically for SUSE Linux

Device Checking and Testing

Configure the Syslog Parameter

Installing Drivers on a Windows Platform

Installing Drivers on a Windows Platform

Installing and Uninstalling the Network Controller

Installing and Uninstalling the Sun Blade 6000 40 GbE VLAN Driver (Optional)

Adding and Removing VLANs

Install the Enclosure Device on a Windows Server 2008 System

Dynamic and NIC Teaming

Installing Drivers on a VMware ESX Server Platform

Installing ESX Server Drivers

Install a NEM Driver for a New ESX4.0 Installation

Install a NEM Driver on an Existing ESX 4.0 Server

Install a NEM Driver on an ESX/ESXi Server

Configure the NEM Network Adapters

Uninstalling the Drivers

Configuring Blade and Port Parameters and Managing the NEM

Configuring and Viewing Parameters

Defaults and Options

Setting Blade Parameters

Setting Port Parameters

Saving User Configurations or Resetting to Defaults

Viewing Parameter Settings, Firmware Versions, and Configuration File

Configuring NEM for Oracle VM Para-Virtualization

Configure Para-Virtualization Without Live Migration

Configure Para-Virtualization With Live Migration

Managing the NEM Using CMM ILOM

ILOM Documentation and Updates

Start NEM CLI from CMM ILOM CLI

Updating the NEM Firmware

Configuring Hot Plug Service

Verify and Enable Hot Plug (Oracle Solaris OS)

Verify and Enable Hot Plug (Linux OS)

Disabling Interfaces

Updating Firmware (Web)

Obtain and Apply the Newest Firmware

Reset the NEM (Web)

Updating the Firmware (CLI)

Update NEM ILOM Firmware (CLI)

Reset the NEM (CLI)

Glossary

Index

Boot a SPARC Blade Over the Network

Use the following procedure to boot over the network using the NEM with a SPARC blade server.

  1. Add a MAC address-IP-address pair to the /etc/ethers and /etc/hosts files on the boot server.

    This pair enables the boot server to answer RARP calls from the blade for resolving the IP address for the NEM's local MAC address.

  2. Add a client script on the boot server to specify which OS should be loaded to the SPARC blade.

    Refer to the installation documentation for the operating system you want to install.

  3. After you have configured the boot server, do one of the following:
    • If the SPARC blade is not running Oracle Solaris OS, log on to the console of the SPARC blade, power the blade on, and boot to the OpenBoot ok prompt.
    • If the blade is already running Oracle Solaris OS, type the following in a terminal window to get to the ok prompt:
      sync;sync;halt
  4. Determine all the network interfaces available for the blade to use.

    Some of them will be the NEM's ports. For example:

    {0} ok show-nets
    a) /pci@400/pci@2/pci@0/pci@c/network@0
    b) /pci@400/pci@2/pci@0/pci@2/network@0,1
    c) /pci@400/pci@2/pci@0/pci@2/network@0
    d) /pci@400/pci@1/pci@0/pci@c/pci@0/pci@3/network@0
    e) /pci@400/pci@1/pci@0/pci@c/pci@0/pci@2/network@0
    q) NO SELECTION
    Enter Selection, q to quit:
  5. Change the directory to the applicable NEM port path.

    Example:

    {0} ok cd /pci@400/pci@1/pci@0/pci@c/pci@0/pci@2/network@0
  6. Check its properties:
    {0} ok .properties

    If it is a Sun Blade 6000 Virtualized 40 GbE Network Express Module, the output will resemble the following.

    {0} ok .properties
    assigned-addresses 
                             82400010 00000000 10300000 00000000 00004000 
                            82400018 00000000 10400000 00000000 00100000 
                            82400030 00000000 10500000 00000000 00100000 
    local-mac-address                        00 21 28 c6 fe 9e 
    reg                         00400000 00000000 00000000 00000000 00000000 
                             03400010 00000000 00000000 00000000 00004000 
                             03400018 00000000 00000000 00000000 00100000 
                             02400030 00000000 00000000 00000000 00100000 
    version                         Sun Blade 6000 Virtualized 40GbE NEM FCode 0.92
                            11/05/03
    board-model                        511-1596-03
    model                        SUNW,pcie-sxge
    compatible                        pciex108e,2078.108e.6277.1
                             pciex108e,2078.108e.6277
                             pciex108e,2078.1
                            pciex108e,2078
                             pciexclass,020000
                             pciexclass,0200
    address-bits                         00000030 
    max-frame-size                         00002400 
    network-interface-type     ethernet
    device_type                         network
    name                         network
    fcode-rom-offset                         000010200 
    interrupts                         00000001 
    cache-line-size                         00000010 
    class-code                         00020000 
    subsystem-id                         00006277 
    subsystem-vendor-id     0000108e 
    revision-id                         00000001 
    device-id                         00002078 
    vendor-id                         0000108e 
  7. Type device-end, then perform the netboot.
    {0} ok device-end
    {0} ok boot /pci@400/pci@0/pci@9/pci@0/pci@1/network@0

    If DHCP will be used for resolving the IP address at the beginning of the boot process, add dhcp at the end of the boot command, as in the following example:

    {0} ok  boot /pci@400/pci@0/pci@9/pci@0/pci@1/network@0:dhcp

    If successful, output similar to the following is displayed on the blade's console.

    Boot device: /pci@400/pci@0/pci@9/pci@0/pci@1/network@0:dhcp  File and args:
    SunOS Release 5.10 Version Generic_141444-09 64-bit
    Copyright 1983-2009 Sun Microsystems, Inc.  All rights reserved.
    Use is subject to license terms.
    NOTICE: sxge1: link up, 10000 Mbps, full duplex
    Configuring devices.
    Using DHCP for network configuration information.
    Reading ZFS config: done.
    Setting up Java. Please wait...
    Serial console, reverting to text install
    Beginning system identification...
    Searching for configuration file(s)...
    Using sysid configuration file /sysidcfg
    Search complete.
    Discovering additional network configuration...
    Completing system identification...
    Starting remote procedure call (RPC) services: done.
    NIS domain name is
    System identification complete.
    Starting Oracle Solaris OS installation program...
    Executing JumpStart preinstall phase...
    Searching for SolStart directory...
    Checking rules.ok file...
    Using begin script: install_begin
    Using finish script: patch_finish
    Executing SolStart preinstall phase...
    Executing begin script "install_begin"...
    Begin script install_begin execution complĀ 

    The net installation menu is displayed. The Oracle Solaris OS installation program is divided into a series of short sections where you'll be prompted to provide information for the installation. At the end of each section, you can change the selections you've made before continuing.

Related Information