> If you can login to root at the 3270 console, you can issue an ifconfig (or > an ip) > command to change the address, then a route command to set the default route.
Or make sure you set a unique MAC address for each network adapter in the CP directory and use DHCP to assign a static address to each MAC address. That setup will allow acquiring all the network details for the DR using a simple down/up of the interface or a reipl. If you do the same at your primary site, then none of the addresses are hard-coded anywhere in the guest and you reliably get the right address for whichever location, plus fixing DNS servers, default routes and a couple pages of more things automagically. If you also enable DDNS on your DNS server and add a DDNS client on your guests, then you don't have to change the addresses your DNS entries point to either. Everything Just Works (tm) and you don't have to touch a thing. If your DHCP and DNS servers live in VM guests, then you speed time to recovery by putting them in the fastest restoring system: if you're in a real disaster, you can have the basic networking infrastructure running in less than an hour from a one or two-pack system while you get everything else fixed around it. Properly planned, you can have networks of hundreds of thousands of systems be self-configuring -- the Linux DHCP code supports multiple configurations with ease and you're not running around messing with address assignments while things are on fire. It's long overdue for the mainframe network stacks to permit this method of address management. DHCP/DHCP6 is reliable, highly scalable and handles static address assignments with ease. It handles both IPv4 and IPv6 easily and is one less unique thing about mainframes -- it's what the distributed folks use for their environments at massive scale. Why be pointlessly difficult/different? The VM, VSE and TPF stacks are all layer 2 capable, and could easily be convinced to act as DHCP clients. Now, if z/OS would get with the program and handle layer 2... ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www2.marist.edu/htbin/wlvindex?LINUX-390
