HP3000-L Archives

January 2001, Week 1

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Dennis Heidner <[log in to unmask]>
Reply To:
Dennis Heidner <[log in to unmask]>
Date:
Sun, 7 Jan 2001 01:16:54 -0600
Content-Type:
text/plain
Parts/Attachments:
text/plain (19 lines)
Greg,   you can use the NETTOOL.NET.SYS program to check the status of the
gateway and bring it backup if necessary.

I believe to check it is under the NAMEADDR command,  then GATELIST,  you'd
see an "Y" flag that the gateway is active it it is.... otherwise "N".

You could write a script, do the gatelist to a file, check the flag and if
no, then run nettool.net.sys again but this time use the GATEUP command.

We had one machine -- that was constantly loosing the gateway --- the darn
networking people would unplug cables at the switches and shuffle things
around figuring it wouldn't hurt anybody.   On that machine I finally
created a script/batch job that just issued a GATEUP command about once an
hour... until the networking changes were done.  This completely eliminated
the late night/early morning panic calls.

I believe the problem you are seeing has been finally fixed in MPEiX 6.0
(with patches) and MPEiX 6.5.

ATOM RSS1 RSS2