You can create a job/script that PINGs a device on the primary network,
and if successful checks the gateway list and makes your gateway changes
for you.

Here's a similar script I wrote many years ago that looks for default
gateways we didn't want enabled and automatically "zaps" them:


rint gatezap.xeq;page=0
#
# command file to list configured network gateways and disable any
# improper ones
#

continue
purge gatef > $NULL
build gatef;rec=-80,,f,ascii
file gf=gatef,old;dev=disc;acc=out
gatelist.xeq.sys > *gf

rem delete the gateways from the list that we DON'T want
rem to zap...
echo t gatef > quadin
echo d 1/22 >> quadin
echo d a i "444.444.444.444" >> quadin
echo d a i "192.123.123.1" >> quadin
echo d a i "_______" >> quadin
echo d l-4/l >> quadin
echo keep;exit >> quadin
echo yes >> quadin
run quad.util.sys < quadin > $NULL

continue
purge g2 > $NULL
build g2;rec=-80,,f,ascii;msg
fcopy from=gatef;to=g2 > $NULL

setvar _nr finfo("g2","EOF")
while !_nr>0 do
input _gaterec < g2
setvar _gateway word("!_gaterec"," ",1)
setvar _active ups(ltrim(rtrim(str("!_gaterec",34,12))))
if "!_gateway"<>"" then
echo gateway=!_gateway active=!_active
endif

if "!_active"="Y" then

echo Disabling gateway @ !_gateway
tellop Disabling gateway @ !_gateway
tell @.sys Disabling gateway @ !_gateway

run nettool.net.sys;info="nameaddr;routing;gatedown !_gateway;quit"

echo !hpdatef !hptimef > PNGM
echo New default gateway !_gateway deactivated on !HPSYSNAME >>
PNGM
continue
xeq sendhtml.xeq.sys ^netguys.data.sys,batch,,PNGM,&
'New Gateway deleted on !HPSYSNAME',Y

continue
netcontrol update=internet;net=lan100


endif

setvar _nr finfo("g2","EOF")
endwhile

continue
purge g2 > $NULL
continue
purge gatef > $NULL
continue
purge pngm,temp > $NULL
deletevar _@

-Chris Bartram

> -----Original Message-----
> From: HP-3000 Systems Discussion [mailto:HP3000-L@RAVEN.UTC.EDU] On
Behalf
> Of Michael Caplin
> Sent: Tuesday, April 08, 2008 9:03 AM
> To: HP3000-L@RAVEN.UTC.EDU
> Subject: [HP3000-L] nettool gatelist
>
> We have an N class (C.70.01) that's connected to a switch. It
> communicates
> with users using 222.222.222.222. If that goes down, it automatically
> swithces to 444.444.444.444 (slower but better than nothing). When
> 222.222.222.222 is back up, the N class remembers it should use
> 444.444.444.444 and users complain about the speed. Nettool is then
used
> to
> disable 444.444.444.444 (as shown below) and everything is ok until it
> happens the next time. Is there another way to handle this (more
> automated)?
> Mike
>
> [3]NAMEADDR.ROUTING>>>GATELIST
> Network address filter: @
> Gateway address filter: @
>
> Gateway IP Hops Flags Active Default Gateway
> __________________________________________________ ____________
> 111.111.111.111 5 0 y y
> 222.222.222.222 0 0 y n
> 333.333.333.333 0 0 y n
> 444.444.444.444 0 0 USER DISABLE n
> __________________________________________________ ____________
>
> Total number of gateways = 4
>
> * To join/leave the list, search archives, change list settings, *
> * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *