Skip Navigation Links | |
Exit Print View | |
Sun Blade 6000 Virtualized Multi-Fabric 10GbE M2 Network Express Module User's Guide 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
Configuring the Network Interface
Checking and Testing the hxge Device
Changing the hxge Driver Configuration
How to Set the Debug Drive Parameter Dynamically
How to Configure the Syslog Parameter
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
The Linux hxge driver has a built-in message and event logging facility, controlled by a message level parameter and logged through the system’s syslog(2) facility, usually to the file /var/log/messages).
The debug messaging parameter has two possible modes:
0x2002 to disable debug messaging, but still list error messages: The hxge driver is configured by default (when it is initially loaded into the kernel memory) to list top-level startup messages and error events and messages.
For example, every time the hxge driver is loaded and started on an hxge network device, it will print a copyright statement, such as:
kernel: Sun Microsystems(R)10 Gigabit Network Driver-version 1.2.7 kernel: Copyright (c) 2009 Sun Microsystems.
and list the Ethernet MAC address(es) configured for that hxge device:
kernel: hxge: ...Initializing static MAC address 00:14:4f:62:00:1d
0x2001 to enable debug messaging: Debug messaging provides large amounts of internal packet flow and event tracing, including specific details on each Ethernet packet sent or received by the hxge driver.
As a 10GbE network is easily capable of flowing over a million packets a second (at a 10GbE rate, a one KB packet is about a microsecond of wire time), this represents a potentially overwhelming load on the kernel’s syslog facility’s ability to buffer and write system messages to disk.
Caution - Do not enable the hxge driver’s debug message logging facility unless necessary to diagnose a problem with the driver. The debug message logging has the potential to adversely affect system operation. |
The default value for the message level parameter is 0x2002.