On Mon, Apr 12, 2010 at 02:07:38PM -0400, Mike Tancsa
wrote:>
> I put in a new 4801 RELENG_8 image at a remote site that requires the
> NIC set to 10baseT full duplex, manually set. However, when I do
> that, I am not sure what to make of the output.
>
>
> 0[to]# ifconfig sis0 media 10baseT/UTP mediaopt full-duplex
> 0[to]# ifconfig sis0
> sis0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu
1500
> options=80008<VLAN_MTU,LINKSTATE>
> ether 00:00:24:d8:aa:e0
> inet 192.168.123.210 netmask 0xfffffff8 broadcast 192.168.123.215
> media: Ethernet 10baseT/UTP <full-duplex> (10baseT/UTP
> <half-duplex>)
> status: active
> 0[to]#
>
> What does the half-duplex portion mean ?
>
The current configured link with ifconfig(8) is 10baseT/UDP and
current option is full-duplex(<> part) and actually negotiated
link/option is 10baseT/UDP half-duplex. Because these are
different you will encounter duplex mismatch which in turn may
yield large number of input errors.
If link partner is configured to 'auto' and link was resolved to
half-duplex even though you specified full-duplex, it could be
normal. Parallel detection normally resolves to half-duplex if
link partner use 'auto'.
Does link partner also use 10baseT/UTP full-duplex instead of
'auto'?
> I am seeing errors as well in netstat
>
> Name Mtu Network Address Ipkts Ierrs
> Idrop Opkts Oerrs Coll
> sis0 1500
> <Link#1> 00:00:24:d8:aa:e0 281215 0 0 269930 2560
10478
>
Show me dmesg output related with sis(4) and PHY driver. Also post
the output of "devinfo -rv | grep phy".