Thread: Broken hme1?
View Single Post

   
  #1 (permalink)  
Old 01-16-2008, 09:40 AM
Stig Bull
 
Posts: n/a
Default Broken hme1?

I've encountered something strange on one of our T1's, after activating
the interface, adding ip address and routing, approx. one out of ten
pings from other servers works. There's also this strange message in
/var/adm/messages on the T1 once the NIC is activated:

Jun 2 15:19:10 lab-t1 hme: [ID 786680 kern.notice] SUNW,hme1 : External
Transceiver Selected.
Jun 2 15:19:10 lab-t1 hme: [ID 786680 kern.notice] SUNW,hme1 : 0 Mbps
Full-Duplex Link Up

The switch port is set to 100/full, I've ran all the neccessary ndd -set
commands to set the T1 to 100/full and disable all other speed/duplex
settings, tried different cables and different ports on the switch.

Monitoring the switch shows that the pkt count increases if I ping the
server, but there are no collisions or drops.

I have made a simple rc2.d/S01 duplex script which sets the hme's to
100-full in the following way:
#! /bin/sh
#

echo "Forcing interface hme0 to 100 Mbps full duplex"
ndd -set /dev/hme instance 0
ndd -set /dev/hme adv_100fdx_cap 1
ndd -set /dev/hme adv_100hdx_cap 0
ndd -set /dev/hme adv_10fdx_cap 0
ndd -set /dev/hme adv_10hdx_cap 0
ndd -set /dev/hme adv_autoneg_cap 0

echo "Forcing interface hme1 to 100 Mbps full duplex"
ndd -set /dev/hme instance 1
ndd -set /dev/hme adv_100fdx_cap 1
ndd -set /dev/hme adv_100hdx_cap 0
ndd -set /dev/hme adv_10fdx_cap 0
ndd -set /dev/hme adv_10hdx_cap 0
ndd -set /dev/hme adv_autoneg_cap 0

So is 0 Mbps Full-Duplex Link Up is an indication of a flakey NIC, or is
there something else?

--
Stig Bull
| remove .no.spam from my email address to reply by mail |
No animals were hurt or killed in the process of creating this
electronic message. To reduce download time, this message is made of
100% recycled bytes.
Reply With Quote