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

Bring the Interface Online Manually

  1. Assign both an IP address and a netmask to bring the interface online.
    host #> ifconfig eth2 10.1.10.156 netmask 255.255.255.0

    The system switches the device online automatically when it has the required information.

  2. Verify that the device is online by using the ifconfig command.
    host #> ifconfig eth2
    eth2  Link encap:Ethernet  HWaddr 00:14:4F:29:00:1D         
    inet addr:10.1.10.156  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:2 errors:0 dropped:0 overruns:0 frame:0
    TX packets:27 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000 
    RX bytes:300 (300.0 b)  TX bytes:7854 (7.6 KiB)
    Memory:fb000000-fc000000

    This example shows configuring the newly-installed NEM interface eth2 to be IP address 10.1.10.156, which is declared in what used to be known as a Class C (8-bit/255-node) LAN.

    Note that the inet addr shows the following:

    • TCP IPv4 address 10.1.10.156 as specified in the ifconfig command

    • IPv6 address has been automatically derived (in this example, Linux is configured to support IPv6 network communications)

    • Reported state now shows up

  3. Verify that RX and TX packet counters are increasing, showing active traffic being routed through the newly configured NEM eth2 network interface.

    See the ifconfig(8) man page for more details and other options on using the ifconfig command to configure Ethernet interfaces.

  4. Use the route(8) command to show the current networks.
    host #> route
    Kernel IP routing table  
    Destination     Gateway      Genmask Flags Metric Ref    Use Iface
    10.1.10.0      *            255.255.255.0   U     0      0        0 eth2
    10.8.154.0     *            255.255.255.0   U     0      0        0 eth1
    default        ban25rtr0d0  0.0.0.0         UG    0      0        0 eth1
     

    Note - In this example, 10.1.10 LAN traffic is being routed through the newly-configured NEM eth2 network interface.


  5. If you want to temporarily switch the network device back to an offline or quiescent state, use the ifconfig down command.
    host #> ifconfig eth2 down
    host #> ifconfig eth2              
    inet addr:10.1.10.156  Bcast:10.1.10.255  Mask:255.255.255.0
    eth2  Link encap:Ethernet  HWaddr 00:14:4F:29:00:1D         
    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:fb000000-fc000000
     
    host #> route 
    Kernel IP routing table
    Destination  Gateway     Genmask      Flags  Metric Ref  Use Iface
    10.8.154.0   *            255.255.255.0   U     0      0     0 eth1
    default      ban25rtr0d0  0.0.0.0         UG    0      0     0 eth1

    Note the 10.1.10 local area network via eth2 is no longer available, but that the eth2 network interface itself is still present (packet counters zero).

Related Information