Operating System - Tru64 Unix
1828415 Members
3345 Online
109977 Solutions
New Discussion

Disable Autonegotiation on bcm0: device.

 
Eric van Dijken
Trusted Contributor

Disable Autonegotiation on bcm0: device.

I am trying to disable autonegotiation on one of our gigabit ethernet devices:

# lan_config -ibcm0 -a0
Setting Interface: bcm0
unsupported: Function not implemented

The messages file reports this:

Feb 15 12:06:18 hdxl23 vmunix: bcm0: Link up via auto-negotiation (1000 Mbps, full duplex)

What is the correct procedure?
Watch, Think and Tinker.
4 REPLIES 4
Mobeen_1
Esteemed Contributor

Re: Disable Autonegotiation on bcm0: device.

Eric,
See if the following discussions throw some light

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=736325

rgds
Mobeen
Eric van Dijken
Trusted Contributor

Re: Disable Autonegotiation on bcm0: device.

Seen that, but doesn't help (with my current problem)

Watch, Think and Tinker.
Eric van Dijken
Trusted Contributor

Re: Disable Autonegotiation on bcm0: device.

Maybe a better question:

The documentation says this:
Auto (link) Negotiation
The default configuration for auto negotiation of the Gigabit Ethernet link is auto. With this setting, the NIC will use IEEE 802.3z auto negotiation. If users connect the NIC to Gigabit Ethernet equipment that does not support auto negotiation, auto negotiation can be turned off by the respective host CPU driver (OpenVMS and Tru64 UNIX).

Now would someone be so kind and enlighten me on how to do this?
Watch, Think and Tinker.
Johan Brusche
Honored Contributor

Re: Disable Autonegotiation on bcm0: device.


Auto-negotiation is defined in Clause 28 of the 1998 edition of the IEEE Standard (Std) 802.3. Clause 28 defines a standard to address the following goals:

- Provide easy, plug-and-play upgrades from 10 Mbps, 100 Mbps, and 1000 Mbps as the network infrastructure is upgraded
- Prevent network disruptions when connecting mixed technologies such as 10BaseT, 100BaseTX, and 1000BaseT
- Accommodate future PHY (transceiver) solutions
- Allow manual override of auto-negotiation
- Support backward compatibility with 10BaseT
- Provide a parallel detection function to recognize 10BaseT, 100BaseTX, and 100BaseT4 non-NWay devices

In addition, the 1999 standard for Gigabit over copper cabling, IEEE Std 802.3ab, added the following update to the Auto-Negotiation standard:

- Mandatory auto-negotiation for 1000BaseT
- Configure master and slave modes for the PHY

I know the bcm manpage says you can do it with lan_config, so if you're not satisfied with the current implementation, log a call with HP.

__ Johan.


_JB_