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
How to Enable Jumbo Frames in a Solaris Environment Using hxge.conf
How to Check Layer 2 Configuration
How to Check Layer 3 Configuration
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
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 Jumbo Frames configuration checking occurs at Layer 2 or Layer 3, depending on the configuration method.
The following examples show uses of the kstat command to display driver statistics.
Display the receive packet counts on all of the four receive DMA channels on interface 1, for example:
# kstat -m hxge | grep rdc_pac rdc_packets 120834317rdc_packets 10653589436 rdc_packets 3419908534 rdc_packets 3251385018 # kstat -m hxge | grep rdc_jumbo rdc_jumbo_pkts 0 rdc_jumbo_pkts 0 rdc_jumbo_pkts 0 rdc_jumbo_pkts 0
Using the kstat hxge:1 command shows all the statistics the driver supports for that interface.
Display driver statistics of a single DMA channel, for example:
# kstat -m hxge -n RDC_0 module: hxge instance: 0 name: RDC_0 class: net crtime 134.619306423 ctrl_fifo_ecc_err 0 data_fifo_ecc_err 0 peu_resp_err 0 rdc_bytes 171500561208 rdc_errors 0 rdc_jumbo_pkts 0 rdc_packets 120834318 rdc_rbr_empty 0 rdc_rbrfull 0 rdc_rbr_pre_empty 0 rdc_rbr_pre_par_err 0 rdc_rbr_tmout 0 rdc_rcrfull 0 rdc_rcr_shadow_full 0 rdc_rcr_sha_par_err 0 rdc_rcrthres 908612 rdc_rcrto 150701175 rdc_rcr_unknown_err 0 snaptime 173567.49684462
Display driver statistics of hxge0 interface, for example:
# kstat -m hxge -n hxge0 module: hxge instance: 0 name: hxge0 class: net brdcstrcv 0 brdcstxmt 0 collisions 0 crtime 134.825726986 ierrors 0 ifspeed 10000000000 ipackets 265847787 ipackets64 17445716971 multircv 0 multixmt 0 norcvbuf 0 noxmtbuf 0 obytes 1266555560 obytes64 662691519144 oerrors 0 opackets 129680991 opackets64 8719615583 rbytes 673822498 rbytes64 24761160283938 snaptime 122991.23646771 unknowns 0
Display all driver statistics, for example:
# kstat -m hxge