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 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
To temporarily enable (or change) jumbo frame support for an hxge network interface, use an ifconfig ethn mtu nnn command. You can do this while the interface is up and running (and actively passing network traffic), but if you set the maximum frame size to a smaller value, you might disrupt incoming traffic from other nodes that are using an older (larger) value.
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:1 errors:0 dropped:0 overruns:0 frame:0 TX packets:30 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:150 (150.0 b) TX bytes:7850 (7.6 KiB) Memory:fb000000-fc000000
Note that in this example, eth2 (the NEM from previous examples) is currently running with the standard MTU of 1500 bytes.
host #> ifconfig eth2 mtu 9000
host #> ifconfig eth2 eth2 Link encap:Ethernet HWaddr 00:14:4F:29:00:01 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:9000 Metric:1 RX packets:26 errors:0 dropped:0 overruns:0 frame:0 TX packets:40 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:3900 (3.8 KiB) TX bytes:9352 (9.1 KiB) Memory:fb000000-fc000000
Note that ifconfig now reports the MTU size to be 9000 bytes. NFS 8KB pages will now flow (send or receive) as a single Ethernet packet.