We have a lot of what you might consider, legacy systems. Primarily, most of our NetWare servers. For us, they’re still highly used production machines.
One such server is a NetWare 6.5 box running iScsi target services. That server is the shared storage for our Novell cluster. I’m working on getting a base Zenoss install configured for some sort of host monitoring. I couldn’t get the Netware server to talk back to the zenoss server. I realized that the default gateway was wrong. It was set to some bogus gateway from when we had a flat network and gateways were irrelevant. The best part is, the reinitialize command doesn’t seem to work when I change any setting in inetcfg. There is some goofy step when you first run inetcfg where it has to transfer from autoexec.ncf and requires a server reboot. So basically, I have to drag the entire cluster offline to change the default gateway of the target server.
And people complained about having to restart windows 95/98 when you changed your IP!
Could you not just reissue a command with the appropriate gateway?
UNBIND IP CE1000_1_EII
then
BIND IP CE1000_1_EII ADDR=192.50.50.251 MASK=255.255.255.0 GATE=192.50.50.226
for example?
That of course would drop ip connection until you rebind it, but should only be momentary & not require a complete reboot of the server? You could even issue the commands via an .ncf so it would do it far quicker than typing it manually?
Thanks Keith, I’ll give that a go. To be honest, I figured there was a way to do it from the command line, but I hadn’t taken much time to look for it as it’s not super critical at the moment.
that’s one of the gotcha’s with classic netware, we do that swap over during the build process. the previous comment is correct that if you put the bind/unbind in a ncf file , it shouldn’t take any longer than the reinitialize command in inetcfg