JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Sun Blade 6000 Virtualized Multi-Fabric 10GbE M2 Network Express Module Product Notes     Sun Blade 6000 Virtualized Multi-Fabric 10GbE M2 Network Express Module Documentation Library
search filter icon
search icon

Document Information

Using This Documentation

Related Books

About This Documentation (PDF and HTML)

We Welcome Your Comments

Change History

Overview of the Sun Blade 6000 Virtualized Multi-Fabric 10GbE M2 NEM Product Notes

Product Information

Supported Software and Firmware

Supported Hardware

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 Issues

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)

FMA Not Supported (6938667)

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)

Operating System Issues

Oracle Linux: Server Module Might Hang When NEM Replaced Repeatedly (6935520)

Workaround

Oracle Solaris: Hotplugd(1M) Daemon Must Be Started Before Initiating Hot Plug Actions In Oracle Solaris 10 OS 09/10 (7005233)

Workaround

Oracle Solaris: Virtualized M2 NEM hxge 10 GbE Driver Can Hang Under High Stress (6932684)

Workaround

Linux: Configuring PCIe Hot Plug in Linux (7075694)

Workaround

Windows: Incorrect Driver Version Displayed When Driver File Properties is Viewed (7069358)

Oracle Solaris: Virtualized M2 NEM hxge 10 GbE Driver Can Hang Under High Stress (6932684)

In Oracle Solaris, the Virtualized M2 NEM hxge devices can become unpingable and hxge entries can disappear from the arp table under high stress conditions (such as during jumbo maxq payload testing). The arp table does not get updated with the hxge entry even after a ping is issued.

Workaround

The workaround is to manually add the hxge 10 GbE interface into arp table or, if necessary, reboot the blade server.