How to verify network connectivity on an X64 platform

Asset ID:	1-71-1005533.1
Update Date:	2018-03-22
Keywords:

Solution Type Technical Instruction Sure

Solution 1005533.1 : How to verify network connectivity on an X64 platform

Applies to:

Sun Fire X4100 M2 Server - Version All Versions and later
Sun Fire X4100 Server - Version All Versions and later
Sun Fire X4200 M2 Server - Version All Versions and later
Sun 3rd Party Software Product - Version Not Applicable and later
Solaris Operating System - Version 9 GA and later
All Platforms

Goal

To discuss this information further with Oracle experts and industry peers, we encourage you to review, join or start a discussion in the My Oracle Support Community - Sun x86 Systems

Summary

This document provides information on how to to verify network connectivity on X64 platform with Solaris, Linux or Windows installed.

Symptoms

- lost network
- host not reachable
- link down
- network not available

Solution

Steps to Follow

NOTE: Console access is required to perform this activity, console redirection can be used on a X64 Server. Workstations have to connected to a keyboard and a monitor.

Network connectivity is checked in two steps:

Check your physical connection
Check you driver availability and network configuration

Physical connection

The first thing to note is that there are usually a number of ethernet connections on an x64 server - x64 servers are equipped with ethernet sockets for the management console. Make sure that the cable is connected to the appropriate socket. Consider the diagram of a v20z in the attachment. There are four ethrnet connection - two for the Service processor and two for the platform (and this is before any additional PCI cards are installed with ethernet ports on them.

Make sure you are connected to the right port.Device mappings are listed below. which will help identify which port you should be connected to.

Check ethernet cables are correctly and securely attached and the link led indicates a connection (an established link is indicated by the right led).

Check ethernet cables for damage.

Replace faulty cables - CAT 5 cables provided performance of up to 100 MHz and are frequently used on 100 Mbit/s ethernet networks. Cat 6 provides performance of up to 250 MHz and is a cable standard for Gigabit Ethernet.

Network drivers and how to check their availability

You will need to verify that the OS has recognised the device and the device is handled by an appropriate driver. You will also need to verify that the appropriate driver is loaded and the OS detects the link and the device is suitably configured for the network infrastructure.

Examples on how to do this are outlined below against the different x64 platforms.

NIC	Solaris Driver	Linux Driver
Intel Gigabit Ethernet	e1000g	e1000
nVidia Ethernet Controller	nge	forcedeth
Broadcom Gigabit Ethernet	bge	tg3 / bcm5700

Checking your Network configuration

Verify that the OS has recognised the device and the device is handled by an appropriate driver. Verify that the appropriate driver is loaded and the OS detects the link. Verify that the device is configured suitable for the network infrastructure.

NIC	Solaris Driver	Linux Driver
Intel Gigabit Ethernet	e1000g	e1000
nVidia Ethernet Controller	nge	forcedeth
Broadcom Gigabit Ethernet	bge	tg3 / bcm5700

Basic information about the network infrastucture are required.

IP address assignment (static / dynamic (dhcp))
IP address
subnet mask
default gateway

Other information about the network infrastructure is useful.

Type of nameservice: (NIS, NIS+, DNS, LDAP, WINS, Active Directory)
Type of nameserver: (IP address of DNS nameserver or NIS server..)
Vlan Configuration

Use IP Addresses for all diagnostics, wrong configured nameservices cause timeouts and failing commands.

Checking your network on Solaris 10 systems

Use the command dladm to check driver and link.

# dladm show-dev

nge0            link: up        speed: 100   Mbps       duplex: full
nge1            link: unknown   speed: 0     Mbps       duplex: unknown
e1000g0         link: down      speed: 0     Mbps       duplex: half
e1000g1         link: down      speed: 0     Mbps       duplex: half

Verify that your ethernet device is configured with an appropriate IP Address and is UP and RUNNING with the command ifconfig.

# ifconfig -a

lo0: flags=2001000849<up,loopback,running,multicast,ipv4,virtual> mtu 8232 index 1
inet 127.0.0.1 netmask ff000000
nge0: flags=1000843<up,broadcast,running,multicast,ipv4> mtu 1500 index 2
inet 129.157.39.13 netmask ffffff00 broadcast 129.157.39.255

Configure your ethernet device if necessary.

# ifconfig nge0 plumb

'''# ifconfig nge0 dhcp '''

# ifconfig nge0 netmask 255.255.255.0 129.157.39.13 up

Verify that other hosts are reachable with the command ping.

# ping 10.16.8.72

10.16.8.72 is alive

# ping 10.16.8.73

no answer from 10.16.8.73

Ping the the system from a other host and watch the IP traffic on the X64 system with snoop. A successful ping has a request and a reply.

# snoop -r host 129.157.39.13

10.16.8.72 -> 129.157.39.13 ICMP Echo request (ID: 42813 Sequence number: 1)
129.157.39.13 -> 10.16.8.72   ICMP Echo reply (ID: 42813 Sequence number: 1)

Verify the routing table when only a request is recognized.

# netstat -rn

Routing Table: IPv4
Destination           Gateway           Flags  Ref     Use     Interface
-------------------- -------------------- ----- ----- ---------- ---------
default              129.157.39.250       UG        1         13 eri0
129.157.39.0         129.157.39.13        U         1       3010 eri0
224.0.0.0            129.157.39.13        U         1          0 eri0
127.0.0.1            127.0.0.1            UH        3        457 lo0

Set the default gateway if necessary.

# route add default 129.157.39.250

Ping your default gateway on the X64 System.

# ping 129.157.39.250

129.157.39.250 is alive

Document 1017986.1 Cant connect to server may also be of assistance

At this point, if you followed each troubleshooting step above you have collected the needed information for further troubleshooting. For additional support contact Sun Support.

Checking your network on Linux Systems

Use the command ethtool to check driver and link.

# ethtool -i eth0

driver: tg3
version: 3.81.1
firmware-version: 5703-v2.35
bus-info: 0000:02:02.0

Load the driver for the device if ethtool -i eth0 fails. Use modprobe -v where diver is e1000, forcedeth, tg3 or bcm5700.

# modprobe -v tg3

insmod /lib/modules/2.6.23.8-34/kernel/drivers/net/tg3.ko

Check the kernel ring buffer for successfully load.

# dmesg | tail -n20

tg3.c:v3.81.1 (October 18, 2007)
ACPI: PCI Interrupt 0000:02:02.0[A] -> GSI 25 (level, low) -> IRQ 25
eth0: Tigon3 [partno(BCM95703A30) rev 1002 PHY(5703)] (PCIX:66MHz:64-bit) 10/100/1000Base-T Ethernet 00:09:3d:10:51:26
eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] WireSpeed[1] TSOcap[1]
eth0: dma_rwctrl[769c0000] dma_mask[64-bit]
ACPI: PCI Interrupt 0000:02:03.0[A] -> GSI 26 (level, low) -> IRQ 26
eth1: Tigon3 [partno(BCM95703A30) rev 1002 PHY(5703)] (PCIX:66MHz:64-bit) 10/100/1000Base-T Ethernet 00:09:3d:10:51:27
eth1: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] WireSpeed[1] TSOcap[1]
eth1: dma_rwctrl[769c0000] dma_mask[64-bit]

# ethtool eth0

Settings for eth0:
Supported ports: [ MII ]
Supported link modes:   10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Half 1000baseT/Full
Supports auto-negotiation: Yes
Advertised link modes:  10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Half 1000baseT/Full
Advertised auto-negotiation: Yes
Speed: 100Mb/s
Duplex: Full
Port: Twisted Pair
PHYAD: 1
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: g
Wake-on: d
Current message level: 0x000000ff (255)
Link detected: yes

Verify that your ethernet device is configured with an appropriate IP Address and is UP and RUNNING with the command ifconfig.

# ifconfig -a

eth0      Link encap:Ethernet  HWaddr 00:09:3D:10:51:26
inet addr:10.16.8.63  Bcast:10.16.8.255  Mask:255.255.255.0
inet6 addr: fe80::209:3dff:fe10:5126/64 Scope:Link
UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
RX packets:7 errors:0 dropped:0 overruns:0 frame:0
TX packets:28 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:550 (550.0 b)  TX bytes:8535 (8.3 KiB)
Interrupt:25
eth1      Link encap:Ethernet  HWaddr 00:09:3D:10:51:27
BROADCAST MULTICAST  MTU:1500  Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
Interrupt:26
lo        Link encap:Local Loopback
LOOPBACK  MTU:16436  Metric:1
RX packets:40 errors:0 dropped:0 overruns:0 frame:0
TX packets:40 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:26787 (26.1 KiB)  TX bytes:26787 (26.1 KiB)

Configure your ethernet device if necessary. Use dhclient or dhcpcd for dynamic assignment and ifconfig for static assignment.

# dhclient eth0

Internet Systems Consortium DHCP Client V3.0.5-RedHat
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/
Listening on LPF/eth0/00:09:3d:10:51:26
Sending on   LPF/eth0/00:09:3d:10:51:26
Sending on   Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
DHCPOFFER from 10.16.8.21
DHCPREQUEST on eth0 to 255.255.255.255 port 67
DHCPACK from 10.16.8.21
bound to 10.16.8.63 -- renewal in 2147483648 seconds.

# dhcpcd -d eth0

Info, eth0: dhcpcd 3.1.8 starting
Info, eth0: hardware address = 00:09:3d:10:51:26
Info, eth0: DUID = 00:01:00:01:0e:fc:d3:16:00:09:3d:10:51:26
Info, eth0: broadcasting for a lease
Info, eth0: offered 10.16.8.63 from 10.16.8.21
Info, eth0: checking 10.16.8.63 is available on attached networks
Info, eth0: leased 10.16.8.63 for 14400 seconds
Info, eth0: no renewal time supplied, assuming 7200 seconds
Info, eth0: no rebind time supplied, assuming 12600 seconds
Info, eth0: adding IP address 10.16.8.63/24
Info, eth0: adding default route via 10.16.8.1 metric 0
Info, eth0: adding route to 169.254.0.0/16 metric 0
Debug, eth0: forking to background

# ifconfig eth0 10.16.8.62 netmask 255.255.255.0 up
will generate no output when succesfull

Verify that other hosts are reachable with the command ping.

# ping -c 1 10.16.8.21

PING 10.16.8.21 (10.16.8.21) 56(84) bytes of data.
--- 10.16.8.21 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms

# ping -c 1 10.16.8.21

PING 10.16.8.21 (10.16.8.21) 56(84) bytes of data.
64 bytes from 10.16.8.21: icmp_seq=1 ttl=255 time=1.83 ms
--- 10.16.8.21 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 1.834/1.834/1.834/0.000 ms

Ping the the system from a other host and watch the IP traffic on the X64 system with tcpdump. A successful ping has a request and a reply. Use a filter for the host (ip host ), otherwise tcpdump will flood the console.

# tcpdump -i eth0 -n ip host 10.16.8.63

tccpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes
16:34:53.133085 IP 10.16.8.21 > 10.16.8.63: ICMP echo request, id 13641, seq 0, length 64
16:34:53.133250 IP 10.16.8.63 > 10.16.8.21: ICMP echo reply, id 13641, seq 0, length 64

Verify the routing table when only a request is recognized.

# netstat -rn

Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
10.16.8.0       0.0.0.0         255.255.255.0   U         0 0          0 eth0
0.0.0.0         10.16.8.1       0.0.0.0         UG        0 0          0 eth0

Set the default gateway if necessary.

# route add default gw 10.16.8.1

Ping your default gateway on the X64 System.

# ping -c 1 10.16.8.1

PING 10.16.8.1 (10.16.8.1) 56(84) bytes of data.
64 bytes from 10.16.8.1: icmp_seq=1 ttl=255 time=0.473 ms
--- 10.16.8.1 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.473/0.473/0.473/0.000 ms

At this point, if you followed each troubleshooting step above you have collected the needed information for further troubleshooting. For additional support contact Sun Support.

Checking your network on Windows systems

Basic tools for troubleshooting TCP/IP connectivity are available in windows. The commands ipconfig, arp, tracert, netstat and ping are part of most windows operating systems. Configuration can be done with a graphical interface. Most settings are found in the Network Connections folder. Some windows operating systems have a graphical tool for automated troubleshooting. The Network Diagnostics interface can be started directly by using the following command: netsh diag gui.

Refer to

http://support.microsoft.com/kb/314067/en-us "How to troubleshoot TCP/IP connectivity with Windows XP"

and

http://support.microsoft.com/kb/323388/en-us "How To Diagnose and Test TCP/IP or NetBIOS Network Connections in Windows Server 2003".

Device mapping and examples for Sun X64 servers and workstations

Sun Fire X4100 / X4200 Servers

Chassis labeling:

 
 ______ ______
|      |      |
| net2 | net3 |
|______|______|
|      |      |
| net0 | net1 |
|______|______|

Led description:

Led: activity - link - activity - link

 
 ______ ______
x     x|x     x
|  2   |  3   |
|______|______|
|      |      |
|  0   |  1   |
x_____x|x_____x

Led: activity - link - activity - link

link: green = link etstablished at 1 gigabit, amber = link etstablished at 10 or 100 megabits
activity: green = link activity, amber = indicates that the link established is not at full capacity for that particular port

x4100 / x4200 Ethernet port device and driver naming:

Chassis label	bios	solaris 10	RHEL	Suse	Windows 2003	vmware ESX
net0	slot 108	e1000g0	eth0	eth0	net	vmnic0
net1	slot 109	e1000g1	eth1	eth1	net2	vmnic1
net2	slot 110	e1000g2	eth2	eth2	net3	vmnic2
net3	slot 111	e1000g3	eth3	eth3	net4	vmnic3

/usr/sbin/lspci
...
01:01.0 Ethernet controller: Intel Corporation 82546EB Gigabit Ethernet Controller (Copper) (rev 03)
01:01.1 Ethernet controller: Intel Corporation 82546EB Gigabit Ethernet Controller (Copper) (rev 03)
01:02.0 Ethernet controller: Intel Corporation 82546EB Gigabit Ethernet Controller (Copper) (rev 03)
01:02.1 Ethernet controller: Intel Corporation 82546EB Gigabit Ethernet Controller (Copper) (rev 03)
...
/usr/X11/bin/scanpci
...
pci bus 0x0001 cardnum 0x01 function 0x00: vendor 0x8086 device 0x1010
Intel Corporation 82546EB Gigabit Ethernet Controller (Copper)
.
pci bus 0x0001 cardnum 0x01 function 0x01: vendor 0x8086 device 0x1010
Intel Corporation 82546EB Gigabit Ethernet Controller (Copper)
.
pci bus 0x0001 cardnum 0x02 function 0x00: vendor 0x8086 device 0x1010
Intel Corporation 82546EB Gigabit Ethernet Controller (Copper)
.
pci bus 0x0001 cardnum 0x02 function 0x01: vendor 0x8086 device 0x1010
Intel Corporation 82546EB Gigabit Ethernet Controller (Copper)
ethtool -i eth0
driver: e1000
version: 7.2.9-k4
firmware-version: N/A
bus-info: 0000:01:01.0

Sun Fire X4100 M2 / X4200 M2 Servers

Chassis labeling:

 
 ______ ______
|      |      |
| net2 | net3 |
|______|______|
|      |      |
| net0 | net1 |
|______|______|

Led description:

Led: activity - link - activity - link

       
 ______ ______
x     x|x     x
|  2   |  3   |
|______|______|
|      |      |
|  0   |  1   |
x_____x|x_____x

Led: activity - link - activity - link

x4100 M2 / x4200 M2 Ethernet port device and driver naming:

Chassis label	bios	solaris 10	RHEL 4 / 5	Suse / RHEL 3	Windows 2003	vmware ESX
net0	slot 108	nge0	eth2	eth0	net	N/A
net1	slot 109	nge1	eth3	eth1	net2	N/A
net2	slot 110	e1000g0	eth0	eth2	net3	vmnic0
net3	slot 111	e1000g1	eth1	eth3	net4	vmnic1

/usr/X11/bin/scanpci
...
pci bus 0x0000 cardnum 0x0a function 0x00: vendor 0x10de device 0x0057
nVidia Corporation CK804 Ethernet Controller
...
pci bus 0x0080 cardnum 0x0a function 0x00: vendor 0x10de device 0x0057
nVidia Corporation CK804 Ethernet Controller
...
pci bus 0x0086 cardnum 0x01 function 0x00: vendor 0x8086 device 0x1010
Intel Corporation 82546EB Gigabit Ethernet Controller (Copper)
.
pci bus 0x0086 cardnum 0x01 function 0x01: vendor 0x8086 device 0x1010
Intel Corporation 82546EB Gigabit Ethernet Controller (Copper)
...
grep nge /var/adm/messages.1
Jan  5 08:39:53 va64-x4100m-gmp03 pcplusmp: [ID 637496 kern.info] pcplusmp: pci10de,57 (nge) instance 0 vector 0x16 ioapic 0xf intin 0x16 is bound to cpu 2
Jan  5 08:39:54 va64-x4100m-gmp03 mac: [ID 469746 kern.info] NOTICE: nge0 registered
Jan  5 08:39:54 va64-x4100m-gmp03 nge: [ID 223987 kern.info] NOTICE: nge0: link down  (initialised)
Jan  5 08:39:56 va64-x4100m-gmp03 nge: [ID 223987 kern.info] NOTICE: nge0: link up 100Mbps Full-Duplex  (initialised)
va64-x4100g-gmp03:~ # ethtool -i eth0
driver: e1000
version: 7.0.33-NAPI
firmware-version: N/A
bus-info: 0000:86:01.0
va64-x4100g-gmp03:~ # ethtool -i eth1
driver: e1000
version: 7.0.33-NAPI
firmware-version: N/A
bus-info: 0000:86:01.1
va64-x4100g-gmp03:~ # ethtool -i eth2
driver: forcedeth
version: 0.49
firmware-version:
bus-info: 0000:00:0a.0
va64-x4100g-gmp03:~ # ethtool -i eth3
driver: forcedeth
version: 0.49
firmware-version:
bus-info: 0000:80:0a.0
dmesg | grep forcedeth
forcedeth.c: Reverse Engineered nForce ethernet driver. Version 0.49.
eth2: forcedeth.c: subsystem: 010de:cb84 bound to 0000:00:0a.0
eth3: forcedeth.c: subsystem: 010de:cb84 bound to 0000:80:0a.0
ethtool eth2
Settings for eth2:
Supported ports: [ MII ]
Supported link modes:   10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Supports auto-negotiation: Yes
Advertised link modes:  10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Advertised auto-negotiation: Yes
Speed: 100Mb/s
Duplex: Full
Port: MII
PHYAD: 1
Transceiver: external
Auto-negotiation: on
Supports Wake-on: g
Wake-on: d
Link detected: yes

Sun Fire X4600 Server

Chassis labeling:

 
 ______ ______
|      |      |
| net2 | net3 |
|______|______|
|      |      |
| net0 | net1 |
|______|______|

Led description:

Led: activity - link - activity - link

  
 ______ ______
x     x|x     x
|  2   |  3   |
|______|______|
|      |      |
|  0   |  1   |
x_____x|x_____x

Led: activity - link - activity - link

x4600 Ethernet port device and driver naming:

Chassis label	bios	solaris 10	RHEL	Suse	Windows 2003	vmware ESX
net0	slot 108	e1000g0	eth0	eth0	net	vmnic1 / 6:1:0
net1	slot 109	e1000g1	eth1	eth1	net2	vmnic2 / 6:1:1
net2	slot 110	e1000g2	eth2	eth2	net3	vmnic3 / 6:2:0
net3	slot 111	e1000g3	eth3	eth3	net4	vmnic0 / 6:2:1

Sun Fire X4600 M2 Server

Chassis labeling:

   
 ______ ______
|      |      |
| net2 | net3 |
|______|______|
|      |      |
| net0 | net1 |
|______|______|

Led description:

Led: activity - link - activity - link

 
 ______ ______
x     x|x     x
|  2   |  3   |
|______|______|
|      |      |
|  0   |  1   |
x_____x|x_____x

Led: activity - link - activity - link

x4600 M2 Ethernet port device and driver naming:

Chassis label	bios	solaris 10	RHEL 4 / 5	Suse / RHEL 3	Windows 2003	vmware ESX
net0	slot 108	e1000g0	eth2	eth0	net	vmnic1 / 6:1:0
net1	slot 109	e1000g1	eth3	eth1	net2	vmnic2 / 6:1:1
net2	slot 110	e1000g2	eth0	eth2	net3	vmnic3 / 6:2:0
net3	slot 111	e1000g3	eth1	eth3	net4	vmnic0 / 6:2:1

Sun Fire X2100 Server

Chassis labeling and Led description

Led: activity - link - activity - link

   
+-------+   +-------+
|       |   |       |
|   1   |   |   2   |
|_______|   |_______|

x2100 Ethernet port device and driver naming:

Chassis label	solaris 10	RHEL	Suse	Windows 2003
1	nge0	eth0	eth0	net
2	bge0	eth1	eth1	net2

/usr/X11/bin/scanpci
...
pci bus 0x0000 cardnum 0x0a function 0x00: vendor 0x10de device 0x0057
nVidia Corporation CK804 Ethernet Controller
...
pci bus 0x0004 cardnum 0x00 function 0x00: vendor 0x14e4 device 0x1659
Broadcom Corporation NetXtreme BCM5721 Gigabit Ethernet PCI Express
bash-3.00# grep -i bge /var/adm/messages
Dec 13 09:52:51 va64-x2100a-gmp03 pcplusmp: [ID 637496 kern.info] pcplusmp: pci14e4,1659 (bge) instance 0 vector 0x13 ioapic 0x2 intin 0x13 is bound to cpu 0
Dec 13 09:52:51 va64-x2100a-gmp03 mac: [ID 543131 kern.info] NOTICE: bge0/0 registered
Dec 13 09:54:27 va64-x2100a-gmp03 pcplusmp: [ID 637496 kern.info] pcplusmp: pci14e4,1659 (bge) instance 0 vector 0x13 ioapic 0x2 intin 0x13 is bound to cpu 1
Dec 13 09:54:27 va64-x2100a-gmp03 mac: [ID 543131 kern.info] NOTICE: bge0/0 registered
Dec 13 10:02:16 va64-x2100a-gmp03 pcplusmp: [ID 637496 kern.info] pcplusmp: pci14e4,1659 (bge) instance 0 vector 0x13 ioapic 0x2 intin 0x13 is bound to cpu 1
Dec 13 10:02:16 va64-x2100a-gmp03 mac: [ID 543131 kern.info] NOTICE: bge0/0 registered
Dec 13 10:02:24 va64-x2100a-gmp03 mac: [ID 846399 kern.info] NOTICE: bge0/0 unregistered
Dec 13 11:00:43 va64-x2100a-gmp03 pcplusmp: [ID 637496 kern.info] pcplusmp: pci14e4,1659 (bge) instance 0 vector 0x13 ioapic 0x2 intin 0x13 is bound to cpu 1
Dec 13 11:00:44 va64-x2100a-gmp03 mac: [ID 543131 kern.info] NOTICE: bge0/0 registered
Dec 13 11:00:51 va64-x2100a-gmp03 mac: [ID 846399 kern.info] NOTICE: bge0/0 unregistered
bash-3.00# grep -i nge /var/adm/messages
Dec 13 09:54:18 va64-x2100a-gmp03 pcplusmp: [ID 637496 kern.info] pcplusmp: pci10de,57 (nge) instance 0 vector 0x14 ioapic 0x2 intin 0x14 is bound to cpu 0
Dec 13 09:54:18 va64-x2100a-gmp03 mac: [ID 543131 kern.info] NOTICE: nge0/0 registered
Dec 13 09:54:19 va64-x2100a-gmp03 nge: [ID 223987 kern.info] NOTICE: nge0: link down  (initialised)
Dec 13 09:54:20 va64-x2100a-gmp03 nge: [ID 223987 kern.info] NOTICE: nge0: link up 100Mbps Full-Duplex  (initialised)
Dec 13 10:01:53 va64-x2100a-gmp03 pcplusmp: [ID 637496 kern.info] pcplusmp: pci10de,57 (nge) instance 0 vector 0x14 ioapic 0x2 intin 0x14 is bound to cpu 0
Dec 13 10:01:53 va64-x2100a-gmp03 mac: [ID 543131 kern.info] NOTICE: nge0/0 registered
Dec 13 10:01:54 va64-x2100a-gmp03 nge: [ID 223987 kern.info] NOTICE: nge0: link down  (initialised)
Dec 13 10:01:55 va64-x2100a-gmp03 nge: [ID 223987 kern.info] NOTICE: nge0: link up 100Mbps Full-Duplex  (initialised)
Dec 13 11:00:22 va64-x2100a-gmp03 pcplusmp: [ID 637496 kern.info] pcplusmp: pci10de,57 (nge) instance 0 vector 0x14 ioapic 0x2 intin 0x14 is bound to cpu 0
Dec 13 11:00:22 va64-x2100a-gmp03 mac: [ID 543131 kern.info] NOTICE: nge0/0 registered
Dec 13 11:00:23 va64-x2100a-gmp03 nge: [ID 223987 kern.info] NOTICE: nge0: link down  (initialised)
Dec 13 11:00:24 va64-x2100a-gmp03 nge: [ID 223987 kern.info] NOTICE: nge0: link up 100Mbps Full-Duplex  (initialised)
bash-3.00#

Sun Fire X2100 M2 / X2200 M2 Server

Chassis labeling:

      
+-------+            +-------+   +-------+
|       |            |       |   |       |
|   0   |            |   2   |   |   3   |
|_______|            |_______|   |_______|
|       |
|   1   |
|       |
+-------+

Chassis label	solaris 10	RHEL 3? / 4?	Suse?	Windows 2003
0	bge0	eth2	eth2	net
1 / NET MGT	bge1	eth3	eth3	net2
2	nge0	eth1	eth1	net1
3	nge1	eth0	eth0	net0

After Tools and Drivers CD update: Before the Tools and Drivers CD drivers are installed, the NVIDIA interfaces are not detected in RHEL 3 Update 7. Later versions of RHEL 3 contain support for both NVIDIA and Broadcom. After installing the drivers from the Tools and Drivers CD, the NVIDIA NICs are detected and configured.
After Tools and Drivers CD update: Before the Tools and Drivers CD drivers are installed, the NVIDIA interfaces are not detected for RHEL 4 Update 3, and cannot be used for PXE installation. Later versions of RHEL 4 contain support for both NVIDIA and Broadcom. After installing the drivers from the Tools and Drivers CD, the NVIDIA NICs are detected and the interface order remains the same for the Broadcom NICs.
After Tools and Drivers CD update: Before the Tools and Drivers CD drivers are installed, the Broadcom interfaces are not detected for SLES 9 SP3. Later versions of SLES contain support for both NVIDIA and Broadcom. After installing the drivers from the Tools and Drivers CD, the Broadcom NICs are detected.

/usr/X11/bin/scanpci
...
pci bus 0x0000 cardnum 0x08 function 0x00: vendor 0x10de device 0x0373
nVidia Corporation MCP55 Ethernet
.
pci bus 0x0000 cardnum 0x09 function 0x00: vendor 0x10de device 0x0373
nVidia Corporation MCP55 Ethernet
...
pci bus 0x0006 cardnum 0x04 function 0x00: vendor 0x14e4 device 0x1678
Broadcom Corporation NetXtreme BCM5715 Gigabit Ethernet
.
pci bus 0x0006 cardnum 0x04 function 0x01: vendor 0x14e4 device 0x1678
Broadcom Corporation NetXtreme BCM5715 Gigabit Ethernet
grep bge /var/adm/messages.0
Dec  3 14:02:00 va64-x2100k-gmp03 pcplusmp: [ID 637496 kern.info] pcplusmp: pci14e4,1678 (bge) instance 0 vector 0x10 ioapic 0x2 intin 0x10 is bound to cpu 1
Dec  3 14:02:00 va64-x2100k-gmp03 mac: [ID 469746 kern.info] NOTICE: bge0 registered
Dec  3 14:02:00 va64-x2100k-gmp03 bge: [ID 801725 kern.info] NOTICE: bge0: link down (initialized)
Dec  3 14:02:05 va64-x2100k-gmp03 bge: [ID 801725 kern.info] NOTICE: bge0: link up 1000Mbps Full-Duplex (initialized)
Dec  3 14:02:15 va64-x2100k-gmp03 pcplusmp: [ID 398438 kern.info] pcplusmp: pci14e4,1678 (bge) instance #1 vector 0x11 ioapic 0x2 intin 0x11 is bound to cpu 1
Dec  3 14:02:15 va64-x2100k-gmp03 mac: [ID 469746 kern.info] NOTICE: bge1 registered
Dec  4 11:00:19 va64-x2100k-gmp03 bge: [ID 801593 kern.notice] NOTICE: bge0: link down
Dec  4 11:00:23 va64-x2100k-gmp03 bge: [ID 801593 kern.notice] NOTICE: bge0: link up 1000Mbps Full-Duplex
grep nge /var/adm/messages.0
Dec  3 15:17:24 va64-x2100k-gmp03 pcplusmp: [ID 637496 kern.info] pcplusmp: pci10de,373 (nge) instance 0 vector 0x17 ioapic 0x2 intin 0x17 is bound to cpu 0
Dec  3 15:17:24 va64-x2100k-gmp03 mac: [ID 469746 kern.info] NOTICE: nge0 registered
Dec  3 15:17:25 va64-x2100k-gmp03 mac: [ID 469746 kern.info] NOTICE: nge1 registered

Sun Fire V20z and Sun Fire V40z Servers

Chassis labeling:

      
+-------+
|       |
|   1   |
|_______|
|       |
|   0   |
|       |
+-------+

Chassis label	solaris 10	RHEL	Suse	Windows 2003
0	bge0	eth0	eth0	net
1	bge1	eth1	eth1	net2

lspci
...
02:02.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5703X Gigabit Ethernet (rev 02)
02:03.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5703X Gigabit Ethernet (rev 02)
...
/usr/X11/bin/scanpci
...
pci bus 0x0002 cardnum 0x02 function 0x00: vendor 0x14e4 device 0x16a7
Broadcom Corporation NetXtreme BCM5703X Gigabit Ethernet
.
pci bus 0x0002 cardnum 0x03 function 0x00: vendor 0x14e4 device 0x16a7
Broadcom Corporation NetXtreme BCM5703X Gigabit Ethernet
...
ethtool -i eth0
driver: tg3
version: 3.75.1
firmware-version: 5703-v2.35
bus-info: 0000:02:02.0
dmesg | grep -e eth -e tg3
tg3.c:v3.75.1 (May 7, 2007)
eth0: Tigon3 [partno(BCM95703A30) rev 1002 PHY(5703)] (PCIX:66MHz:64-bit) 10/100/1000Base-T Ethernet 00:09:3d:10:51:26
eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] WireSpeed[1] TSOcap[1]
eth0: dma_rwctrl[769c0000] dma_mask[64-bit]
eth1: Tigon3 [partno(BCM95703A30) rev 1002 PHY(5703)] (PCIX:66MHz:64-bit) 10/100/1000Base-T Ethernet 00:09:3d:10:51:27
eth1: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] WireSpeed[1] TSOcap[1]
eth1: dma_rwctrl[769c0000] dma_mask[64-bit]
ADDRCONF(NETDEV_UP): eth0: link is not ready
tg3: eth0: Link is up at 100 Mbps, full duplex.
tg3: eth0: Flow control is off for TX and off for RX.
ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
eth0: no IPv6 routers present
ethtool eth0
Settings for eth0:
Supported ports: [ MII ]
Supported link modes:   10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Half 1000baseT/Full
Supports auto-negotiation: Yes
Advertised link modes:  10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Half 1000baseT/Full
Advertised auto-negotiation: Yes
Speed: 100Mb/s
Duplex: Full
Port: Twisted Pair
PHYAD: 1
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: g
Wake-on: d
Current message level: 0x000000ff (255)
Link detected: yes

Sun Ultra 20 Workstation

The Ultra 20 has only one NIC.

Chassis label	solaris 10	Linux
0	nge0	eth0

lspci
...
00:0a.0 Bridge: nVidia Corporation CK804 Ethernet Controller (rev a3)
...
/usr/X11/bin/scanpci
...
pci bus 0x0000 cardnum 0x0a function 0x00: vendor 0x10de device 0x0057
nVidia Corporation CK804 Ethernet Controller
...
ethtool -i eth0
driver: forcedeth
version: 0.60
firmware-version:
bus-info: 0000:00:0a.0
ethtool eth0
Settings for eth0:
Supported ports: [ MII ]
Supported link modes:   10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Supports auto-negotiation: Yes
Advertised link modes:  10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Advertised auto-negotiation: Yes
Speed: 1000Mb/s
Duplex: Full
Port: MII
PHYAD: 1
Transceiver: external
Auto-negotiation: on
Supports Wake-on: g
Wake-on: g
Link detected: yes
dmesg | grep -e eth0 -e forcedeth
forcedeth.c: Reverse Engineered nForce ethernet driver. Version 0.60.
forcedeth: using HIGHDMA
eth0: forcedeth.c: subsystem: 0108e:5347 bound to 0000:00:0a.0
eth0: no IPv6 routers present
grep nge /var/adm/messages
Dec 17 06:38:47 u20.local pcplusmp: [ID 637496 kern.info] pcplusmp: pci10de,57 (nge) instance 0 vector 0x17 ioapic 0x2 intin 0x17 is bound to cpu 0
Dec 17 06:38:47 u20.local mac: [ID 469746 kern.info] NOTICE: nge0 registered
Dec 17 06:38:48 u20.local nge: [ID 223987 kern.info] NOTICE: nge0: link down  (initialised)
Dec 17 06:38:49 u20.local /sbin/dhcpagent[56]: [ID 116611 daemon.error] interface nge0 has gone down
Dec 17 06:38:52 u20.local nge: [ID 223987 kern.info] NOTICE: nge0: link up 1000Mbps Full-Duplex  (initialised)
Dec 17 06:38:52 u20.local /sbin/dhcpagent[56]: [ID 116611 daemon.error] interface nge0 has come back up
grep -e eth0 -e forcedeth /var/log/messages
Dec 18 18:59:13 u20 forcedeth.c: Reverse Engineered nForce ethernet driver. Version 0.60.
Dec 18 18:59:13 u20 forcedeth: using HIGHDMA
Dec 18 18:59:13 u20 eth0: forcedeth.c: subsystem: 0108e:5347 bound to 0000:00:0a.0
Dec 18 18:59:18 u20 dhcpcd[3991]: eth0: dhcpcd 3.1.8 starting
Dec 18 18:59:18 u20 dhcpcd[3991]: eth0: hardware address = 00:e0:81:73:1f:bf
Dec 18 18:59:18 u20 dhcpcd[3991]: eth0: DUID = 00:01:00:01:0e:3a:a3:08:00:e0:81:59:6d:22
Dec 18 18:59:18 u20 dhcpcd[3991]: eth0: broadcasting for a lease
Dec 18 18:59:18 u20 dhcpcd[3991]: eth0: offered 192.168.0.3 from 192.168.0.100
Dec 18 18:59:18 u20 dhcpcd[3991]: eth0: checking 192.168.0.3 is available on attached networks
Dec 18 18:59:19 u20 dhcpcd[3991]: eth0: leased 192.168.0.3 for 86400 seconds
Dec 18 18:59:19 u20 dhcpcd[3991]: eth0: adding IP address 192.168.0.3/24
Dec 18 18:59:19 u20 dhcpcd[3991]: eth0: adding default route via 192.168.0.100 metric 0
Dec 18 18:59:19 u20 dhcpcd[3991]: eth0: adding route to 169.254.0.0/16 metric 0
Dec 18 18:59:19 u20 dhcpcd[3991]: eth0: setting hostname to `u20.local'
Dec 18 18:59:19 u20 dhcpcd[3991]: eth0: exiting
Dec 18 18:59:38 u20 eth0: no IPv6 routers present

Sun Ultra 20 M2 Workstation

+-------+
|       |
|   0   |
|_______|
|       |
|   1   |
|       |
+-------+

Chassis label	solaris 10	Linux
0	nge0	eth0
1	nge1	eth1

Sun Ultra 40 / 40 M2 Workstation

+-------+
|       |
|   1   |
|_______|
|       |
|   0   |
|       |
+-------+

Chassis label	solaris 10	Linux
0	nge0	eth0
1	nge1	eth1

grep nge /var/adm/messages
Dec 17 14:34:05 netrep-u40a-gmp03 nge: [ID 801725 kern.info] NOTICE: nge0: Using FIXED interrupt type
Dec 17 14:34:05 netrep-u40a-gmp03 pcplusmp: [ID 803547 kern.info] pcplusmp: pci10de,57 (nge) instance 0 vector 0x17 ioapic 0x4 intin 0x17 is bound to cpu 0
Dec 17 14:34:05 netrep-u40a-gmp03 mac: [ID 469746 kern.info] NOTICE: nge0 registered
Dec 17 14:34:07 netrep-u40a-gmp03 mac: [ID 435574 kern.info] NOTICE: nge0 link up, 100 Mbps, full duplex
Dec 17 14:34:09 netrep-u40a-gmp03 nge: [ID 801725 kern.info] NOTICE: nge1: Using FIXED interrupt type
Dec 17 14:34:09 netrep-u40a-gmp03 pcplusmp: [ID 444295 kern.info] pcplusmp: pci10de,57 (nge) instance #1 vector 0x2e ioapic 0x5 intin 0x16 is bound to cpu 0
Dec 17 14:34:09 netrep-u40a-gmp03 mac: [ID 469746 kern.info] NOTICE: nge1 registered
Dec 17 14:34:56 netrep-u40a-gmp03 mac: [ID 736570 kern.info] NOTICE: nge1 unregistered
/usr/X11/bin/scanpci
...
pci bus 0x0000 cardnum 0x0a function 0x00: vendor 0x10de device 0x0057
nVidia Corporation CK804 Ethernet Controller
...
pci bus 0x0080 cardnum 0x0a function 0x00: vendor 0x10de device 0x0057
nVidia Corporation CK804 Ethernet Controller

Previously Published As 91541

Attachments

This solution has no attachment