Assuming you are running VM in both LPARs and the LPARs are connected to the same disks, use CSE, and assign network info via DHCP. CSE will prevent a virtual machine from running in both places simultaneously, and assuming that you have DHCP servers on the production and test networks, the servers will acquire the correct addresses for the networks automatically. Works very well, and it's simple to manage.
That's the nice part about user-assigned MAC addresses -- you can create a unique identifier from the network perspective and provision it in DHCP and it Just Works. If you're religious about DNS names only in applications, then DR is also really trivial -- DHCP gives you a network address, and you can control the whole mess from the DNS and DHCP configurations. If you're really smart, you do DDNS, and the whole thing Just Works again. ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
