|Skip Navigation Links|
|Exit Print View|
|Sun Blade 6000 Virtualized Multi-Fabric 10GE M2 Network Express Module Documentation Sun Blade 6000 Virtualized Multi-Fabric 10GbE M2 Network Express Module Documentation Library|
Once you have the NEM network interface device properly configured and up (online and active), there are several ways you can verify the network interface operation.
Options for verifying the network interface operation include:
ifconfig: Use the ifconfig command to see if the RX/TX (receive/transmit) 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 network (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 name (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 (for example, 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 indicating 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 errors, dropped, overruns, frame, carrier, or collision events are reported. Some network errors are expected even in normal operation, but should be insignificant relative to the packet counts.
ethtool: If ifconfig reports an accumulation of errors, then an extremely detailed breakdown of NEM traffic details (including error counts of all sorts) may be obtained using the ethtool(8) command.
The following is an excerpt of the total hxge detailed statistics output.
host #> ethtool -S eth2 NIC statistics: Rx Channel #: 0 Rx Packets: 3008 Rx Bytes: 3289580 Rx Errors: 0 Jumbo Packets: 0 ECC Errors: 0 RBR Completion Timeout: 0 PEU Response Error: 0 RCR Shadow Parity: 0 RCR Prefetch Parity: 0 RCR Shadow Full: 0 RCR Full: 0 RBR Empty: 0 RBR Full: 0 RCR Timeouts: 3008 RCR Thresholds: 0 Packet Too Long Errors: 0 No RBR available: 0 RVM Errors: 0 Frame Errors: 0 RAM Errors: 0 CRC Errors: 0 [...]