Re: Adding OSA devices to a vSwitch...
Thanks all; It's a done deal; No bumps or pitfalls. Thanks for the reassurance. -- .~.Robert P. Nix Mayo Foundation /V\RO-OE-5-55200 First Street SW /( )\ 507-284-0844 Rochester, MN 55905 ^^-^^ - "In theory, theory and practice are the same, but in practice, theory and practice are different." On 11/16/07 9:04 AM, "Mary Ellen Carollo" <[EMAIL PROTECTED]> wrote: > Robert - > You should be able to add an additional device with no disruption. It is > > not necessary to do the disconnect. Simply "SET VSWITCH name RDEV origdev > > newdev" and your device should be added as a back up. > > On the other hand, I *would* recommend using "SET VSWITCH name DISCONNECT > " > if you need to remove the currently-active device, rather than forcing a > > failover somehow. > > Mary Ellen Carollo > z/VM Virtual Networking Development
Re: Adding OSA devices to a vSwitch...
Robert - You should be able to add an additional device with no disruption. It is not necessary to do the disconnect. Simply "SET VSWITCH name RDEV origdev newdev" and your device should be added as a back up. On the other hand, I *would* recommend using "SET VSWITCH name DISCONNECT " if you need to remove the currently-active device, rather than forcing a failover somehow. Mary Ellen Carollo z/VM Virtual Networking Development On Fri, 16 Nov 2007 09:48:20 +0100, Ronald van der Laan <[EMAIL PROTECTED]> wrote: >Robert > >On Nov 15, 2007 10:56 PM, RPN01 <[EMAIL PROTECTED]> wrote: >> >> I'm looking for some peace of mind before trying this... >> >> We've cabled a second OSA device into our network, and I want to add it to >> my vSwitch definition as a backup to the current OSA connection. I can >> obviously add the path to the SYSTEM CONFIG file, and wait for the new IPL >> (which, hopefully, is some time in the distant future). I see that I c an >> also issue a SET VSWITCH name RDEV origdev newdev. >> >> The question is, will adding the second device disrupt the current traffic, >> or will everything keep running correctly? I think that it should be >> non-disruptive, but I'm looking for some reassurance > >I've done this in the past, and it was disruptive in a way that for a >few milliseconds the vswitch got stopped. >What I did was create an exec with the following commands: > >/* Add addional osa card */ >'CP SET VSWITCH name DISCONNECT' >'CP SET VSWITCH name RDEV origdev newdev' >'CP SET VSWITCH name CONNECT' > >As the IP protocol doesn't guarantee packet arrival anyway, so the few >lost packets should be retransmitted without anyone noticing the >difference. > >PS, I did the same for disabling/removing osa cards (for maintenance) >in the past. > >Ronald van der Laan > =
Re: Adding OSA devices to a vSwitch...
I believe you can do it without using the disconnect. I tried this on a system that was not very active and it worked fine. Hans -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Ronald van der Laan Sent: November 16, 2007 3:48 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Adding OSA devices to a vSwitch... Robert On Nov 15, 2007 10:56 PM, RPN01 <[EMAIL PROTECTED]> wrote: > > I'm looking for some peace of mind before trying this... > > We've cabled a second OSA device into our network, and I want to add it to > my vSwitch definition as a backup to the current OSA connection. I can > obviously add the path to the SYSTEM CONFIG file, and wait for the new IPL > (which, hopefully, is some time in the distant future). I see that I can > also issue a SET VSWITCH name RDEV origdev newdev. > > The question is, will adding the second device disrupt the current traffic, > or will everything keep running correctly? I think that it should be > non-disruptive, but I'm looking for some reassurance I've done this in the past, and it was disruptive in a way that for a few milliseconds the vswitch got stopped. What I did was create an exec with the following commands: /* Add addional osa card */ 'CP SET VSWITCH name DISCONNECT' 'CP SET VSWITCH name RDEV origdev newdev' 'CP SET VSWITCH name CONNECT' As the IP protocol doesn't guarantee packet arrival anyway, so the few lost packets should be retransmitted without anyone noticing the difference. PS, I did the same for disabling/removing osa cards (for maintenance) in the past. Ronald van der Laan
Re: Adding OSA devices to a vSwitch...
Robert On Nov 15, 2007 10:56 PM, RPN01 <[EMAIL PROTECTED]> wrote: > > I'm looking for some peace of mind before trying this... > > We've cabled a second OSA device into our network, and I want to add it to > my vSwitch definition as a backup to the current OSA connection. I can > obviously add the path to the SYSTEM CONFIG file, and wait for the new IPL > (which, hopefully, is some time in the distant future). I see that I can > also issue a SET VSWITCH name RDEV origdev newdev. > > The question is, will adding the second device disrupt the current traffic, > or will everything keep running correctly? I think that it should be > non-disruptive, but I'm looking for some reassurance I've done this in the past, and it was disruptive in a way that for a few milliseconds the vswitch got stopped. What I did was create an exec with the following commands: /* Add addional osa card */ 'CP SET VSWITCH name DISCONNECT' 'CP SET VSWITCH name RDEV origdev newdev' 'CP SET VSWITCH name CONNECT' As the IP protocol doesn't guarantee packet arrival anyway, so the few lost packets should be retransmitted without anyone noticing the difference. PS, I did the same for disabling/removing osa cards (for maintenance) in the past. Ronald van der Laan
