Skip Navigation Links | |
Exit Print View | |
Sun Blade 6000 Virtualized 40 GbE Network Express Module User's Guide |
RJ-45 Ethernet Connector Port LEDs
Performing Hot-plug Insertion and Removal
Prepare the PCIe Interface for Hot-plug Removal
Performing SAS Interface Hot-plug
Prepare SAS Interfaces for Hot-plug Removal
Restoring SAS Configurations After NEM Installation
Saving the Zoning Configuration to a Backup File
Recovering Zoning Configurations
Determine the CMM Part Number Using ILOM 3.0x Web Interface
Determine the CMM Part Number Using ILOM 3.1x Web Interface
Determine the CMM Part Number Using ipmitool
Find the CMM Part Number on the CMM Label
Verify Installation (CMM ILOM Web)
Verify Installation (CMM ILOM CLI)
Installing and Removing SFP+ Optical Transceiver Modules
Install an SFP+ Optical Transceiver Module
Remove an Optical Transceiver SFP+ Module
SFP+ Connector Cabling Options
Configuring Jumbo Frames (Solaris)
Jumbo Frames Configurations and Driver Statistics
Configuring Jumbo Frames (Linux)
Temporarily Configure Jumbo Frames (Linux)
Permanently Enable Jumbo Frames (Linux)
Configuring Jumbo Frames (VMware ESX)
Create a Jumbo Frames-Enabled vSwitch (VMWare)
Create a Jumbo Frames-Enabled VMkernel Interface (VMWare
Configuring Static Link Aggregation
Example (Oracle Solaris 11 OS)
Example (Oracle Solaris 10 OS)
Booting an x86 Server Over the Network
Booting the NEM on an x86 Blade Server Over the Network
Set Up the BIOS for Booting From the NEM
Use the F12 Key to Initiate the Network Boot
Use the F8 Key to Boot Off the PXE Server
Boot a SPARC Blade Over the Network
Installing Drivers on Oracle Solaris OS SPARC or x86 Platform
Configure the Network Host Files
Configure the sxge Device Driver Parameters
Installing Drivers on a Linux Platform
Downloading, Installing, and Removing Drivers
Download and Install the Drivers
Configuring the Network Interface
Temporary Network Interface Configuration
Permanent Network Interface Configuration
Bring the Interface Online Manually
Configure the Network Interface File Automatically for Red Hat Linux
Configure the Network Interface Automatically for SUSE Linux
Configure the Syslog Parameter
Installing Drivers on a Windows Platform
Installing Drivers on a Windows Platform
Installing and Uninstalling the Network Controller
Installing and Uninstalling the Sun Blade 6000 40 GbE VLAN Driver (Optional)
Install the Enclosure Device on a Windows Server 2008 System
Installing Drivers on a VMware ESX Server Platform
Install a NEM Driver for a New ESX4.0 Installation
Install a NEM Driver on an Existing ESX 4.0 Server
Install a NEM Driver on an ESX/ESXi Server
Configure the NEM Network Adapters
Configuring Blade and Port Parameters and Managing the NEM
Configuring and Viewing Parameters
Saving User Configurations or Resetting to Defaults
Viewing Parameter Settings, Firmware Versions, and Configuration File
Configuring NEM for Oracle VM Para-Virtualization
Configure Para-Virtualization Without Live Migration
Configure Para-Virtualization With Live Migration
Managing the NEM Using CMM ILOM
ILOM Documentation and Updates
Start NEM CLI from CMM ILOM CLI
Verify and Enable Hot Plug (Oracle Solaris OS)
Verify and Enable Hot Plug (Linux OS)
Obtain and Apply the Newest Firmware
Once you have the NEM network interface device properly configured, online, and active, there are several ways you can verify the network interface operation:
ifconfig: Use the ifconfig command to see if the RX/TX packet counts are increasing. The TX packet count indicates that the local system network services (or users) are queueing up packets to get sent over that interface; the RX packet count indicates that externally-generated packets have been received on that network interface.
route: Use the route command to check that traffic for the network interface's network is being routed to that interface. If there are multiple network interfaces connected to a given LAN, traffic may be directed to one of the other interfaces, resulting in a zero packet count on the new interface.
ping: If you know the IP address of another node on the network, use the ping(8) command to send a network packet to that node and get a response back.
host 39 #> ping tge30 PING tge30 (10.1.10.30) 56(84) bytes of data. 64 bytes from tge30 (10.1.10.30): icmp_seq=1 ttl=64 time=1.37 ms 64 bytes from tge30 (10.1.10.30): icmp_seq=2 ttl=64 time=0.148 ms 64 bytes from tge30 (10.1.10.30): icmp_seq=3 ttl=64 time=0.112 ms 64 bytes from tge30 (10.1.10.30): icmp_seq=4 ttl=64 time=0.074 ms 64 bytes from tge30 (10.1.10.30): icmp_seq=5 ttl=64 time=0.161 ms --- tge30 ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4001ms rtt min/avg/max/mdev = 0.074/0.373/1.372/0.500 ms
By default, ping sends one ping packet out each second until it is stopped (by typing ^C). A slightly more thorough test would be a ping flood test. For example:
host #> ping -f -i 0 -s 1234 -c 1000 tge30 PING tge30 (10.1.10.30) 1234(1262) bytes of data. --- tge30 ping statistics --- 1000 packets transmitted, 1000 received, 0% packet loss, time 1849ms rtt min/avg/max/mdev = 0.048/0.200/0.263/0.030 ms, ipg/ewma 1.851/0.198 ms
This example sends out 1,000 ping packets (containing 1,234 bytes of data each or over a megabyte total) as fast as the other side responds. Note the 0% packet loss indicates a functional and sound network connection.
Check the network interface again, using ifconfig, to look for any apparent problems.
host #> ifconfig eth2 eth2 Link encap:Ethernet HWaddr 00:14:4F:29:00:1D inet addr:10.1.10.150 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:2993 errors:0 dropped:0 overruns:0 frame:0 TX packets:2978 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:3286970 (3.1 MiB) TX bytes:3287849 (3.1 MiB) Memory:fb000000-fc000000
Note that no error, dropped, overrun, frame, carrier, or collision events are reported. Some network errors are expected even in normal operation, but usually are insignificant relative to the packet counts.
ethtool: If ifconfig reports an accumulation of errors, then an extremely detailed report of NEM traffic (including error counts) is available by using the ethtool(8) command.
The following is an excerpt of the sxge detailed statistics output.
host #> ethtool -S eth2 NIC statistics: tx_frames: 7113048 tx_bytes: 4294967264 tx_frame_cnt_ovl: 0 tx_byte_cnt_ovl: 0 rx_frames: 5366 rx_bytes: 416808 rx_drops: 0 rx_drop_bytes: 0 rx_mcasts: 4501 rx_bcasts: 762 rx_frames_cnt_ovl: 0 rx_byte_cnt_ovl: 0 rx_drop_byte_ovl: 0 rx_drop_cnt_ovl: 0 rx_mcast_frame_cnt_ovl: 0 rx_bcast_frame_cnt_ovl: 0 rx_link_up: 1 rx_link_down: 0 rx_link_state: 1 rx_channel: 0 rx_bytes: 1416672 rx_dropped: 0 rx_errors: 0 rx_hw_pktcnt: 10136 rx_hw_pktdrop: 0 rx_rbr_empty: 0 rx_fifo_error: 0 rx_rcr_shadow_full: 0 rx_channel: 1 rx_packets: 303428 rx_bytes: 13957688 rx_dropped: 0 rx_errors: 0 rx_hw_pktcnt: 303428 rx_hw_pktdrop: 0 rx_rbr_empty: 0 rx_fifo_error: 0 rx_rcr_shadow_full: 0 rx_channel: 2 rx_packets: 35460186685 rx_bytes: 36560119545336 rx_dropped: 0 rx_errors: 0 rx_hw_pktcnt: 1100447649 rx_hw_pktdrop: 4989944 rx_rbr_empty: 9321 rx_fifo_error: 0 rx_rcr_shadow_full: 0 rx_channel: 3 rx_packets: 31126 rx_bytes: 4354871 rx_dropped: 0 rx_errors: 0 rx_hw_pktcnt: 31126 rx_hw_pktdrop: 0 rx_rbr_empty: 0 rx_fifo_error: 0 rx_rcr_shadow_full: 0 tx_channel: 0 tx_packets: 35574371264 tx_bytes: 37744382014305 tx_errors: 0 tx_channel: 1 tx_packets: 0 tx_bytes: 0 tx_errors: 0 tx_channel: 2 tx_packets: 0 tx_bytes: 0 tx_errors: 0 tx_channel: 3 tx_packets: 0 tx_bytes: 0 tx_errors: 0