Hi,
I got my self pretty hosed with this (no fault of jrj's his directions
for twiddling the hme settings are essentially correct, just be sure
to `man ndd` first as there's some subtle variations between Solaris
releases)
I suspect the switch might have gotten confused by the changing
interface settings, possible due to the order I changed them in.
I'll post a full description for the record when I sort it out.
Just fair warning incase someone else is about to try this...
-Jon
On Fri, Nov 03, 2000 at 11:38:36PM -0500, John R. Jackson wrote:
:
:You didn't mention if you needed the magic or not, but here it is just
:in case (add to /etc/system and reboot):
:
: set hme:hme_adv_100fdx_cap = 1
: set hme:hme_adv_100hdx_cap = 0
: set hme:hme_adv_autoneg_cap = 0
:
:The first line says "use full duplex", the second says "don't use half
:duplex" and the third says "don't try to autonegotiate". I assume you
:flip the value in the first two lines if you use half duplex.
:
:Truth be told, I only have (and knew about) the first and third lines.
:But I just saw the second line and the following in a mailing list
:recently. I suspect the default is zero for these variables and so I
:don't need the half duplex set.
:
:If you want to test the values while the system is up (as root):
:
: ndd -get /dev/hme hme_adv_100fdx_cap
: ndd -get /dev/hme hme_adv_100hdx_cap
: ndd -get /dev/hme hme_adv_autoneg_cap
:
:If you have multiple instances, select the specific one first, then do
:the variables, e.g. for hme1:
:
: ndd -set /dev/hme instance 1
: ndd -get /dev/hme hme_adv_100fdx_cap
: ...
:
:I'm not sure what you do in /etc/system for multiple instances.
:
:In theory you can also set these at run time, but that's braver than
:I'd want to be unless it was dead in the water and my local network guru
:was at my shoulder.
:
:>Jon
:
:John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
