Solaris

Originally Posted by fixit9660

From the CLI, why does this work:

ndd -set /dev/ce instance 2
ndd -set /dev/ce adv_1000fdx_cap 1
ndd -set /dev/ce adv_1000hdx_cap 0
ndd -set /dev/ce adv_100fdx_cap 0
ndd -set /dev/ce adv_100hdx_cap 0
ndd -set /dev/ce adv_10fdx_cap 0
ndd -set /dev/ce adv_10hdx_cap 0
ndd -set /dev/ce adv_autoneg_cap 0

and this doesn't?

ndd -set /dev/ce instance 1
ndd -set /dev/ce adv_1000fdx_cap 1
ndd -set /dev/ce adv_1000hdx_cap 0
ndd -set /dev/ce adv_100fdx_cap 0
ndd -set /dev/ce adv_100hdx_cap 0
ndd -set /dev/ce adv_10fdx_cap 0
ndd -set /dev/ce adv_10hdx_cap 0
ndd -set /dev/ce adv_autoneg_cap 0

Originally Posted by fixit9660

Ah right, so you're saying that the rc2.d scripts override the CLI commands?

Note According to IEEE 802.3 specifications, when using 1000 Mbps speed over
copper media, autonegotiation is not optional. In the absence of autonegotiation, (for
example, while using Forced mode), link syncing between link partners may not
happen and the link may not come up.


To Set Autonegotiation to off for Other Noncompliant Network Equipment
If your network equipment does not support autonegotiation, you can set
autonegotiation to off on the GigaSwift Ethernet (ce) device.
1. Set the following GigaSwift Ethernet driver parameters to values according to the
documentation that shipped with your switch:
* adv-1000fdx-cap
* adv-1000hdx-cap
* adv-ampause-cap
* adv-pause-cap
2. Set the adv-autoneg-cap parameter to 0.


When link-up is attempted with autonegotiation enabled (the default), the link parameter capabilities (such as speed in megabits/second, duplex and link-clock mastership only for 1000 Mbps) are automatically negotiated between the device and its link partner.

The concept of link clock mastership was introduced with gigabit twisted-pair technology. One side of the link is the master that provides the link clock and the other side is the slave that uses the link clock. Once this relationship is established, the link is up, and data can be communicated. Two physical layer parameters control whether your side is the master or the slave, or whether mastership is negotiated with the link partner....

Note: Configuring the parameters by putting ndd commands in rcX.d scripts is
not supported.