All fine ideas that will work for a DR test running with DR test IP addresses (from the DR vendor's LAN?) whilst your real system remains up.
If the disaster happens, will your real DR invocation system run with the DR vendor's LAN addresses? If so, how will your live TCPIP clients find your TCPIP servers? VIPA can help with this if you have different policies for DR test and Real DR. Regards, Mike Mike Wawiorko Global z Connectivity and Automation Engineering GISD Core Engineering GRB Technology Barclays Bank -----Original Message----- From: The IBM z/VM Operating System [mailto:[email protected]] On Behalf Of Bauer, Bobby (NIH/CIT) [E] Sent: 12 August 2010 17:11 To: [email protected] Subject: Re: Disaster Recovery TCPIP Address Issue Would this be done with the SYSTEM_IDENTIFIER statement in the SYSTEM CONFIG and if so, how do I find my current model and cpuid? Looks like the 'q cupid' will give it to me. Bobby Bauer Center for Information Technology National Institutes of Health Bethesda, MD 20892-5628 301-594-7474 -----Original Message----- From: David Boyes [mailto:[email protected]] Sent: Thursday, August 12, 2010 11:34 AM To: [email protected] Subject: Re: Disaster Recovery TCPIP Address Issue >location. While discussing our requirements, the topic of TCPIP addresses >came up. Since the addresses at the offsite location will be different >from our local addresses, we are at a loss as to how to change them. The vendor should be able to give you the CPUIDs of the recovery systems you'll be running on during your test. Add those to SYSTEM NETID and SYSTEM CONFIG with different node names (I use DISASTER). Once that's done, when the system comes up, you can use qualifiers in the TCPIP PROFILE and SYSTEM CONFIG to set up things with the addresses of your disaster recovery system, kinda like this (not precise syntax, so RTFM for it): NORMAL: LINK FOO xxxx DISASTER: LINK FOO yyyy Presto, no need to change anything actually AT recovery site. 8-) -- db This e-mail and any attachments are confidential and intended solely for the addressee and may also be privileged or exempt from disclosure under applicable law. If you are not the addressee, or have received this e-mail in error, please notify the sender immediately, delete it from your system and do not copy, disclose or otherwise act upon any part of this e-mail or its attachments. Internet communications are not guaranteed to be secure or virus-free. The Barclays Group does not accept responsibility for any loss arising from unauthorised access to, or interference with, any Internet communications by any third party, or from the transmission of any viruses. Replies to this e-mail may be monitored by the Barclays Group for operational or business reasons. Any opinion or other information in this e-mail or its attachments that does not relate to the business of the Barclays Group is personal to the sender and is not given or endorsed by the Barclays Group. Barclays Bank PLC.Registered in England and Wales (registered no. 1026167). Registered Office: 1 Churchill Place, London, E14 5HP, United Kingdom. Barclays Bank PLC is authorised and regulated by the Financial Services Authority.
