Even easier is to use a test VM TCPIP stack rather than a Linux guest. YMMV.
I just recently moved our production network connections from one pair of OSA's to a different pair. Like the OP, I first tested the new OSA's wit h a new VSWITCH, but I used a test VM TCPIP stack. When I was done testing I destroyed the test VSWITCH. Then I added one of the new OSA addresses to the production VSWITCHs as the *second* address. Then I caused the VSWITCHs to fail off its primary address onto a backup address (via a cable pull). Since the first address had been the active primary the new OSA as the second address that was the one that became the new primary. Then I updated the production VSWITCHs again to remove both old OSA addresses and add the other new OSA. Neat, clean, and non-disruptive. Brian Nielsen On Tue, 21 Oct 2008 13:53:19 -0500, Marcy Cortes <[EMAIL PROTECTED]> wrote: >The "simplest" way is really just to go edit the directory entry and log >it off and back on. Patrick must be using some really horrible >directory manager! ;) > > > >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: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On >Behalf Of Mark Post >Sent: Tuesday, October 21, 2008 11:24 AM >To: [email protected] >Subject: Re: [IBMVM] Connecting and testing a new pair of OSAs and new >vswitch > >>>> On 10/21/2008 at 2:07 PM, in message <[EMAIL PROTECTED]>, >>>> Patrick >Spinler <[EMAIL PROTECTED]> wrote: >-snip- >> So, can anyone clue me in on what I'm forgetting? > >I didn't see a "set vswitch grant" command in there. Did you do that >before the couple? If so, or if the way you issued the command means it >isn't required, then you need to bring the device online from inside >Linux first. The simplest way to do it is via YaST, but you can also >use the qethon.sh script I put up on linuxvm.org. You can also do it >manually, but it's not fun. > > >Mark Post >======================== ========================= =======================
