Skip Navigation Links | |
Exit Print View | |
![]() |
Sun Blade 6000 Virtualized Multi-Fabric 10GE M2 Network Express Module Documentation Sun Blade 6000 Virtualized Multi-Fabric 10GbE M2 Network Express Module Documentation Library |
About This Documentation (PDF and HTML)
Overview of Sun Blade 6000 Virtualized Multi-Fabric 10GbE M2 NEM User's Guide
Features of the Sun Blade 6000 Virtualized Multi-Fabric 10GbE M2 NEM
Performing Hot Plug Insertion and Removal
Installing or Replacing the Virtualized M2 NEM
Installing and Removing SFP+ Optical Transceiver Modules
Booting Over the Virtualized M2 NEM 10-Gigabit Ethernet Port
Booting over the Network With an x86 Blade Server
Booting over the Network With a SPARC Blade Server
Installing and Configuring the hxge Driver on a Solaris SPARC or x86 Platform
How to Configure the Network Host Files
Configuring the hxge Device Driver Parameters
Configuring the Jumbo Frames Feature
Installing and Configuring the hxge Driver on a Linux Platform
Installing and Removing the Driver on a Linux Platform
How to Download and Install the Driver on a Linux Platform
How to Remove the Driver From a Linux Platform
Configuring the Network Interface
About Temporary hxge Network Interface Configuration
About Permanent hxge Network Interface Configuration
How to Configure the Network Interface File Automatically for Red Hat Linux
How to Configure the Network Interface Automatically for SUSE Linux
Checking and Testing the hxge Device
Changing the hxge Driver Configuration
How to Temporarily Configure the hxge Driver Parameters
How to Permanently Configure the hxge Driver Parameters
hxge Driver Configuration Parameters
Debug Messaging Parameter Overview
How to Set the Debug Drive Parameter Dynamically
How to Configure the Syslog Parameter
How to Temporarily Configure Jumbo Frames Support
How to Permanently Enable Jumbo Frame Support
Installing and Configuring Drivers on a Windows Platform
Installing Drivers on a Windows Platform
Installing and Configuring Drivers on a VMware ESX Server Platform
Installing the ESX Server Drivers on an Existing ESX Server
Installing the ESX Server Drivers With a New ESX Installation
Configuring the Virtual NEM M2 Network Adapters
Accessing ILOM Documentation and Updates
Enabling Private and Failover Mode
Fixing Problems with Oracle ILOM Using the Preboot Menu
Overview of the Sun Blade 6000 Virtualized Multi-Fabric 10GbE M2 NEM Product Notes
Supported Software and Firmware
Hardware and Networking Issues
Packet Drop at 1Gb with 100m Cable (6879222)
Special Instructions for Network PXE Booting for the Sun Blade X3-2B Server (7183913)
ILOM Failover and Private Mode Cannot Be Enabled Simultaneously (6911661)
Cannot Set NEM SP IP Address When NEM Is Powered Off (6938660)
ipmitool Command Fails (6940791)
Prepare-to-Remove and Return-to-Service Does Not Work on NEM ILOM (6948103)
Green Rear SAS Link LEDs All Turn On When Setting Prepare-to-Remove (6950981)
NEM SAS Firmware Updates Must be Performed from the CMM and Not the NEM SP (7020854)
Oracle Linux: Server Module Might Hang When NEM Replaced Repeatedly (6935520)
Oracle Solaris: Virtualized M2 NEM hxge 10 GbE Driver Can Hang Under High Stress (6932684)
Linux: Configuring PCIe Hot Plug in Linux (7075694)
Windows: Incorrect Driver Version Displayed When Driver File Properties is Viewed (7069358)
host #> ifconfig eth2 10.1.10.156 netmask 255.255.255.0
The system switches the device online automatically when it has the requisite information.
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 Ethernet 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) local area network (or 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 also support IPv6 network communications)
Reported state now shows up
See the ifconfig(8) man page for more details and other options on using the ifconfig command to configure Ethernet interfaces.
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.
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 (but no longer in up state, packet counters now zero again).