so I have to prefix the capabilities with eri_? When I query the capabilities they just come back with e.g. auto_neg_cap, not eri_autoneg_cap
Main Topics
Browse All Topicstitle says it all really. I have a solaris box that's not negotiating the network settings correctly. I've fixed it with ndd, but where do I put those changes so that they are efective on next reboot?
cheers
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
it's eri0. it just seems a bit odd that what I have to put in /etc/system differs from the capabilities reported by the driver! my autoneg_cap isn't prefixed with adv either e.g.
# ndd -get /dev/eri \?
? (read only)
transceiver_inuse (read only)
link_status (read only)
link_speed (read only)
link_mode (read only)
ipg1 (read and write)
ipg2 (read and write)
use_int_xcvr (read and write)
pace_size (read and write)
adv_autoneg_cap (read and write)
adv_100T4_cap (read and write)
adv_100fdx_cap (read and write)
adv_100hdx_cap (read and write)
adv_10fdx_cap (read and write)
adv_10hdx_cap (read and write)
autoneg_cap (read only)
100T4_cap (read only)
100fdx_cap (read only)
100hdx_cap (read only)
10fdx_cap (read only)
10hdx_cap (read only)
lp_autoneg_cap (read only)
lp_100T4_cap (read only)
lp_100fdx_cap (read only)
lp_100hdx_cap (read only)
lp_10fdx_cap (read only)
lp_10hdx_cap (read only)
instance (read and write)
lance_mode (read and write)
ipg0 (read and write)
intr_blank_time (read and write)
intr_blank_packets (read and write)
Here's /etc/system entries for eri (setting 100 Mbit full duplex):
* Configuration of eri-parameters
set eri:adv_autoneg_cap=0
set eri:adv_100T4_cap=0
set eri:adv_100fdx_cap=1
set eri:adv_100hdx_cap=0
set eri:adv_10fdx_cap=0
set eri:adv_10hdx_cap=0
Simply prefix the "adv_*" capapbilities with eri: (as we want to set the
capapbilities for the eri driver). This is from you post above:
adv_autoneg_cap (read and write)
adv_100T4_cap (read and write)
adv_100fdx_cap (read and write)
adv_100hdx_cap (read and write)
adv_10fdx_cap (read and write)
adv_10hdx_cap (read and write)
No, adv stands for "advertise". This means that the adapter/driver sends his
capabilites (advertises them) to the other side. In this case the ethernet
adapter will tell the connected switch that he "can do" this mode.
The other variable "autoneg_cap" is the actual status (that's why it's read-
only). To be precise, each capabilty has THREE variables:
adv_<cap> my system tells the other what he could
lp_adv_<cap> the other system told me what it can (Link Partner)
<cap> the actual status of the capability on my system
Cheers
Business Accounts
Answer for Membership
by: liddlerPosted on 2003-08-18 at 07:05:10ID: 9173552
/etc/system 4
i.e.
set eri:eri_adv_autoneg_cap=0
set eri:eri_adv_100fdx_cap=0
set eri:eri_adv_100hdx_cap=0
set eri:eri_adv_10fdx_cap=1
set eri:eri_adv_10hdx_cap=0
set tcp:tcp_conn_hash_size=102