Hi there. My first time posting so apologies for any indescretions in advance. I've got two SunFire V440 servers running Solaris 5v10. Both have a quad Gigabit ethernet card fitted, both have the same symptom; that is, I can't get the first port ce1 to run Gigabit. Motherboard ports are ce0 and ce5. the quad card ports are ce1 - ce4 inclusive. Port ce2 runs Gig fine. (Haven't tried ports ce3 or ce4). When I configure ce1 for Gig it doesn't even show a green l.e.d. when I plug in the patch cable. The switch and patch cables are definitely good. Port ce1 work perfectly at 100Mb/s FDX on both servers.
I guess I'm missing a patch or something but all help appreciated. By the way I'm a Network Engineer, not a Solaris Admin so anticipate a high degree of noobness relating to Solaris and Servers. Apologies in advance. Thanks, Andy.

Perhaps someone has configured ce1 to stick at 100Mb/s instead of auto-negotiating the speed/duplex mode.

What says:

ndd -set /dev/ce instance 1
ndd /dev/ce adv_autoneg_cap
grep ce1 /etc/system
grep ndd /etc/rc*.d/*

also make sure your switch is configured for autoneg! call your network guys and make sure it works. as a test you can maybe use the port which ce2 uses (login through console!).

good luck,
DN2

Hi jlliagre, output as requested from my server:

datanetnms4 > ndd -set /dev/ce instance 1
datanetnms4 > ndd /dev/ce adv_autoneg_cap
0
datanetnms4 > grep ce1 /etc/system
datanetnms4 > grep ndd /etc/rc*.d/*
/etc/rc0.d/K34ncalogd: /usr/sbin/ndd -set /dev/nca nca_log_file $i
/etc/rc0.d/K34ncalogd: /usr/sbin/ndd -set /dev/nca nca_log_size $logd_file_size
/etc/rc0.d/K34ncalogd: /usr/sbin/ndd -set /dev/nca nca_logging_on 1
/etc/rc0.d/K34ncalogd: /usr/sbin/ndd -set /dev/nca nca_logging_on 0
/etc/rc1.d/K34ncalogd: /usr/sbin/ndd -set /dev/nca nca_log_file $i
/etc/rc1.d/K34ncalogd: /usr/sbin/ndd -set /dev/nca nca_log_size $logd_file_size
/etc/rc1.d/K34ncalogd: /usr/sbin/ndd -set /dev/nca nca_logging_on 1
/etc/rc1.d/K34ncalogd: /usr/sbin/ndd -set /dev/nca nca_logging_on 0
/etc/rc2.d/S42ncakmod: # Set the default HTTPD door in NCA via ndd
/etc/rc2.d/S42ncakmod: /usr/sbin/ndd -set /dev/nca httpd_door_path \
/etc/rc2.d/S69inet:ndd -set /dev/ce instance 0
/etc/rc2.d/S69inet:ndd -set /dev/ce adv_1000fdx_cap 0
/etc/rc2.d/S69inet:ndd -set /dev/ce adv_1000hdx_cap 0
/etc/rc2.d/S69inet:ndd -set /dev/ce adv_100fdx_cap 1
/etc/rc2.d/S69inet:ndd -set /dev/ce adv_100hdx_cap 0
/etc/rc2.d/S69inet:ndd -set /dev/ce adv_10fdx_cap 0
/etc/rc2.d/S69inet:ndd -set /dev/ce adv_10hdx_cap 0
/etc/rc2.d/S69inet:ndd -set /dev/ce adv_autoneg_cap 0
/etc/rc2.d/S69inet:ndd -set /dev/ce instance 1
/etc/rc2.d/S69inet:ndd -set /dev/ce adv_1000fdx_cap 0
/etc/rc2.d/S69inet:ndd -set /dev/ce adv_1000hdx_cap 0
/etc/rc2.d/S69inet:ndd -set /dev/ce adv_100fdx_cap 1
/etc/rc2.d/S69inet:ndd -set /dev/ce adv_100hdx_cap 0
/etc/rc2.d/S69inet:ndd -set /dev/ce adv_10fdx_cap 0
/etc/rc2.d/S69inet:ndd -set /dev/ce adv_10hdx_cap 0
/etc/rc2.d/S69inet:ndd -set /dev/ce adv_autoneg_cap 0
/etc/rc2.d/S94ncalogd: /usr/sbin/ndd -set /dev/nca nca_log_file $i
/etc/rc2.d/S94ncalogd: /usr/sbin/ndd -set /dev/nca nca_log_size $logd_file_size
/etc/rc2.d/S94ncalogd: /usr/sbin/ndd -set /dev/nca nca_logging_on 1
/etc/rc2.d/S94ncalogd: /usr/sbin/ndd -set /dev/nca nca_logging_on 0
/etc/rcS.d/K34ncalogd: /usr/sbin/ndd -set /dev/nca nca_log_file $i
/etc/rcS.d/K34ncalogd: /usr/sbin/ndd -set /dev/nca nca_log_size $logd_file_size
/etc/rcS.d/K34ncalogd: /usr/sbin/ndd -set /dev/nca nca_logging_on 1
/etc/rcS.d/K34ncalogd: /usr/sbin/ndd -set /dev/nca nca_logging_on 0
datanetnms4 >

---------- Post updated at 01:07 AM ---------- Previous update was at 12:59 AM ----------

Hi DukeNuke2,

The switch isn't configured for auto-neg, we set all our switches to FDX where the server interfaces are multi-speed capable. It stops them re-negotiating and messing up the comms. By the way I AM the Network Guy and yes, (as per my original post) the switch port and patch cable are known good. I have tried the network connection to ce2 in port ce1 with the same, non-operating, results. The network connection for ce1 works perfectly in ce2.
The server interface doesn't even show a green (physical) l.e.d. when I connect up the patch cable, when it's configured for Gig, which is what I find most confusing.

These lines look like your problem:

/etc/rc2.d/S69inet:ndd -set /dev/ce instance 0
/etc/rc2.d/S69inet:ndd -set /dev/ce adv_1000fdx_cap 0
/etc/rc2.d/S69inet:ndd -set /dev/ce adv_1000hdx_cap 0
/etc/rc2.d/S69inet:ndd -set /dev/ce adv_100fdx_cap 1  <-----
/etc/rc2.d/S69inet:ndd -set /dev/ce adv_100hdx_cap 0
/etc/rc2.d/S69inet:ndd -set /dev/ce adv_10fdx_cap 0
/etc/rc2.d/S69inet:ndd -set /dev/ce adv_10hdx_cap 0
/etc/rc2.d/S69inet:ndd -set /dev/ce adv_autoneg_cap 0

The IEEE 802.3 standard states that you must support and test autonegotiation enabled to certify a product IEEE 802.3 compliant, and for multivendor interoperability (for example, testing at the UNH Interoperability Laboratory). There are no requirements in the standard to support locked down or forced configurations using autonegotiation disabled. As a result, there are no requirements for vendors to test multivendor interoperability between products with autonegotiation disabled. The IEEE 802.3ab specification does not allow for forced mode 1000BASE-T with autonegotiation disabled running at 1000 Mbps. As a result, many switch vendors do not support forced mode. Although the transceiver used in the Sun™ Gigaswift Ethernet UTP adapter 1.0 is configurable for the 1000 Mbps forced mode and the ce driver allows this mode be aware that it does not work under certain circumstances.

Put the above into a script file to force autoneg from server end too.

That wouldn't allow Gb to work.

Simply comment out the very same lines and reboot.