Defaulting to maximum performance mode when autoneg is off is probably
actually a bug. Most device drivers default to 10Mbps HDX in this mode.
That said, if one side has autoneg disabled, then so should the other.
I consider it generally an error on the part of the administrator(s) to
have autoneg disabled. *Especially* at Gb speeds. (There are various
features like pause capability that can *only* be enabled via autoneg.)
The IEEE 802 committee agrees so strongly with this that they have
mandated autoneg for 10GbE -- you can't run without it on 10G networks.
(At least not without violating the specs.)
- Garrett
On Fri, 2011-01-21 at 06:33 -0800, Thorsten Heit wrote:
> > > > Back to Solaris I tried the following commands:
> > > >
> > > > /usr/sbin/ndd -set /dev/bge1 adv_autoneg_cap 0
> > > > /usr/sbin/ndd -set /dev/bge1 adv_100fdx_cap 1
> > > > /usr/sbin/ndd -set /dev/bge1 adv_100hdx_cap 0
> > >
> > > That should still do it. I suggest filing a bug. Having the link stuck
> > down when in forced mode sounds like a pretty basic error to me.
> >
> > Ok, I'll do that.
>
> I just managed to get the link working:
>
> As I wrote in my initial post to this forum, I only deactivated
> auto-negotiation and 100MBit half-duplex. If I understand the dladm man page
> correctly, the underlying driver switches to the maximum allowed / available
> speed when auto negotiation is turned off; in my case a GBit connection which
> won't work because of the switch's capabilities, i.e. fast ethernet full
> duplex.
>
> After deactivating both GBit capabilities, 100MBit half duplex and
> auto-negotiation both links now talk with 100MBit full duplex to the switch.
> Hooray!
>
> So it wasn't not a bug, but basically a user error... :-o
>
>
> Anyway, thanks for the hints.
>
>
> Thorsten
_______________________________________________
networking-discuss mailing list
networking-discuss@opensolaris.org
