Yeah, you are right and we know. The effort and cost to duplicate the active directory environment likely won't fly for just Linux on z servers testing. And the AD servers are not in the mainframe datacenter so unlikely that they would suffer the same disaster. In our case though, the real event doesn't have any configuration changes necessary other than the network routers. The best "test" though is just to go run in the other place for a week or whatever. We'll be doing that too.
Marcy "This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation." -----Original Message----- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Richard Troth Sent: Friday, August 14, 2009 9:52 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Dynamicallhy Changing Linux Guest Network Forgive me ... you realize, of course, that you're not getting a true "exercise". Touching prod stuff means there's yet another point that's not getting exercised. (Not to mention the exposure ... "test" things with access to your prod network.) I have fought the same fight where I work (about changing IP addresses). Others have already acquiesced. (Gotta pick yer battles, I guess, but this hostname and IP addr shuffle drives me nuts.) I'm probably telling you something you already know. -- R; <>< On Fri, Aug 14, 2009 at 12:18, Marcy Cortes<marcy.d.cor...@wellsfargo.com> wrote: > It's because of the software we use to interface to Active Directory for > single signon. It doesn't want 2 systems coming in with the same hostname. > If we do that, we can't login to the prod systems :( > > > > Marcy > "This message may contain confidential and/or privileged information. If you > are not the addressee or authorized to receive this for the addressee, you > must not use, copy, disclose, or take any action based on this message or any > information herein. If you have received this message in error, please advise > the sender immediately by reply e-mail and delete this message. Thank you for > your cooperation." > > > -----Original Message----- > From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Michael > MacIsaac > Sent: Friday, August 14, 2009 9:02 AM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: [LINUX-390] Dynamicallhy Changing Linux Guest Network > > Marcy, > >> have to change IPs and hostnames > I can understand that you have to change IP addresses. But do you have to > change hostnames? Maybe have a DNS system that maps the same hosts to new > i...@s? ... just a thought ... > > "Mike MacIsaac" <mike...@us.ibm.com> (845) 433-7061 > > ---------------------------------------------------------------------- > 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 > > ---------------------------------------------------------------------- > 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 > ---------------------------------------------------------------------- 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 ---------------------------------------------------------------------- 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
