David Kreuter wrote:
Are you using MPROUTE and configured the interface to let mproute
discover routes? Should work
Depends on the nature of the change... As mentioned by the OP:
P L Lovely wrote:
Requiring a new Router firewall
If a new router is coming online, and all the routers are configured in
the same routing domain, MPROUTE would start learning about routes from
the new router, no problem... The existing router could be switched
off, and the migration is complete.
> Requiring a new IP address
This one bothers me a little. If it's VM TCPIP who needs to have a new
IP address, MPROUTE can't do this for you.
Putting those two together though, and combining with this...
Example:
Traceries 192.168.22Y.YY
Trace route to 192.168.22Y.YY (192.168.22Y.YY)
1 (192.168.x.xxx) 2 ms 2 ms 2 ms
Getting rid of the: 192.168.x.xxx.
This makes me think that your VM TCPIP is moving to a different subnet.
It would be very unlikely that VM TCPIP -- or any TCPIP stack, for
that matter -- would carry a relocation to a new subnet with no
interruption of service. If you're using VIPA and dynamic routing
you've got a good chance, otherwise you're better off to plan a
migration with some downtime rather than trying to keep things running
during the change.
If you really want to make the changes to the running TCPIP, look at the
documentation for OBEYFILE. If you're on a recent z/VM, you might be
more comfortable with the IFCONFIG command. If you are running MPROUTE,
you will need to update your MPROUTE configuration and cycle the MPROUTE
SVM after you have made your changes to TCPIP. Also, if you use
OBEYFILE or IFCONFIG, you will need to make sure that your
dynamically-activate changes are applied to your TCPIP PROFILE to make
sure that you still have your changes after the next IPL.
If you need assistance, a bit more information about what the change is
(what the config is now, what it will become) would help us guide you on
what could be safely done dynamically, and what would be better to just
wear an outage for.
Cheerio,
Vic Cross
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
