I seem to recall (like Gary Stephens) that MPE caches the MAC for the
gateway, and that there is a LINKCONTROL or NSCONTROL command that updates
with an "INTERNET=@" or "INTERNET=ALL" clause.  It's been a few years
though...

Good luck!

Howard


On Tue, Nov 12, 2013 at 10:36 AM, John Maclerran <[log in to unmask]> wrote:

> Thanks Donna that clarifies a lot.
>
> We have a shutdown command file that basically stops all jobs, aborts all
> sessions, ups the jobfence so nobody can log in, and brings down the
> network interface. It doesn't do an MPE shutdown (i.e. no SHUT x messages),
> it leaves the system up, but with only operator.sys logged in on the master
> console.  A corresponding startup command file restarts the network,
> restreams the background jobs and returns the fence to normal for users to
> log in.
>
> It sounds like we should do the shutdown just prior to the maintenance, and
> then a startup afterward.  No need to physically restart the system though
> (i.e. ctrl-a SHUTDOWN, ctrl-b RS)
>
>
>
> On Tue, Nov 12, 2013 at 11:06 AM, Donna Hofmeister <[log in to unmask]
> >wrote:
>
> > On Tue, Nov 12, 2013 at 9:59 AM, Gary Stephens
> > <[log in to unmask]>wrote:
> >
> > > wasnt there a gateway reset command, as I recall you could either do an
> > > nscontrol xxx internet;reset alternatively shut and restart the
> network,
> > or
> > > something similar?
> > > I am sure Donna will remember though!
> > >
> > >
> > >
> > > On 12 Nov 2013, at 17:17, Jack Connor <[log in to unmask]>
> > > wrote:
> > >
> > > > If you're taking it off the air for the network changes, John, I'd go
> > > ahead and close the network down until the work has completed and then
> > > reopen it.
> > > >
> > > > MPE will be looking for the IPs as it opens up.  I know you can see
> the
> > > MAC addresses in NETTOOL, but I don't think they're of any import other
> > > than informational and for DTC traffic.
> > >
> >
> > I agree with what Jack said -- halt the network (even the system if
> > possible -- because it's almost the same thing...) while the larger
> network
> > work is being done.  When the new gear is in place and seems stable "wake
> > up" the 3000 and watch to what happens.
> >
> > When you halt the network (presuming you're not taking the box down) be
> > sure to halt/quiesce network-dependent things (like jobs/listeners) just
> > prior.  I'd suggest doing an 'openq' on your network printers as well
> (keep
> > the input side of printing open, but not the output side).   (And if
> you're
> > thinking "gee, it's almost like shutting down the system" see the
> paragraph
> > before this one :-)            - d
> >
> > --
> > Donna Hofmeister
> > Allegro Consultants, Inc.
> > 408-252-2330
> >
> > * To join/leave the list, search archives, change list settings, *
> > * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
> >
>
>
>
> --
> John MacLerran, IT Analyst, Senior ([log in to unmask])
> Idaho State University <http://www.isu.edu> -- Leading in opportunity and
> innovation
> (208)282-2954
> http://picasaweb.google.com/jmaclerran
>
> * 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 *