On Thu, Dec 16, 1999 at 06:24:04AM -0600, Mark D Fowle wrote:

come up on line. My work around at the present time is to pull the gigabit cable out of the flier then putting it back on. This seems to "wake-up" the connection. I have not been able to figure our exactly whats going on and our network

Notice the 0.0.0.0 for adding the default, "default" stopped working ---

hmmm, haven't seen this before, interesting. i prefer to put the actual names in the route statement. the same goes for ifconfig, i really don't like the `hostname` kludge.

---------rc file ---------- hostname filer1 ifconfig e7 `hostname`-e7 netmask 255.255.255.0 ifconfig e7 mediatype auto `hostname`-e7 netmask 255.255.255.0

you shouldn't need a mediatype for gigabit. this second line seems extraneous. i don't see that it actually accomplishes anything. and if you pull up the man page for ifconfig you'll see something like:

"auto" (Auto RJ-45 twisted-pair)

which isn't really anything like gigabit.

route add 0.0.0.0 <our gateway> 1 routed on rc_toggle_basic alttune e3 LinkNegotiation 1

how many gigabit cards do you have in this filer?

also the format of this i think is wrong. i have found that the filers actually want the number of the card in order starting from 0. e3 would be 0 and e7 would be 1. so it you want to set LinkNegotiation for the gigabit card in slot 3 it would be alttune 0 LinkNegotiation 1. i have only ever seen it work in one situation, but as always YMMV.

this could also be what is causing a hang...

rc_toggle_basic ypset < our dns server> rc_toggle_basic

you leave your filer up in rc_toggle_basic mode? scary.

-s