Re: Vswitch Question
Jim, I've not seen an answer to your question. But you need to list all the first OSA addresses in the SET VSWITCH command. so: SET VSWITCH name RDEV prim_osa C000 CONNECT If you use: SET VSWITCH name RDEV C000 CONNECT Then you effectively drop your primary OSA connection and switch to your backup one. That's fine if you need maintenance on your primary OSA, but not when when you want to go to the high availability steady state Ronald van der Laan
Re: Vswitch Question
Thanks Ron, I tried the following which accomplished the objective of getting the vswitch to recognize C000 as the backup: SET VSWITCH name CONNECT Thanks again Jim P. On 8/19/10 3:52 AM, Ronald van der Laan nl50...@gmail.com wrote: Jim, I've not seen an answer to your question. But you need to list all the first OSA addresses in the SET VSWITCH command. so: SET VSWITCH name RDEV prim_osa C000 CONNECT If you use: SET VSWITCH name RDEV C000 CONNECT Then you effectively drop your primary OSA connection and switch to your backup one. That's fine if you need maintenance on your primary OSA, but not when when you want to go to the high availability steady state Ronald van der Laan
Re: Vswitch Question
On Thursday, 08/19/2010 at 03:52 EDT, Ronald van der Laan nl50...@gmail.com wrote: I've not seen an answer to your question. But you need to list all the first OSA addresses in the SET VSWITCH command. so: SET VSWITCH name RDEV prim_osa C000 CONNECT If you use: SET VSWITCH name RDEV C000 CONNECT Then you effectively drop your primary OSA connection and switch to your backup one. Sorry, I didn't see this before. You cannot change the active RDEV on a connected VSWITCH. In Jim's case, he wanted to use the *secondary* for something else. To do that SET VSWITCH name RDEV prim_osa You will see the secondary OSA detached from the controller, and it is then available for use. Only use the DETACH command if the VSWITCH becomes unresponsive (in which case you get a snapdump of the system first to go with your PMR). Likewise, never ATTACH an OSA to a VSWITCH controller. If you want to use the *primary* for some other purpose, then you will disrupt the VSWITCH: SET VSWITCH name DISCONNECT SET VSWITCH name RDEV C000 SET VSWITCH name CONNECT To add the former primary OSA back: SET VSWITCH name RDEV C000 prim_osa Of course, prim_osa is now the backup! You could use the disconnect three-step to get it back as the primary, but that's an itch that need not be scratched. (Who cares which one is the backup? It's not like you would use one fast, one slow!) If you want to add and delete OSAs on the fly with no disruption, then you engage link aggregation and define a port group. Alan Altmark z/VM Development IBM Endicott
Re: Vswitch Question
Alan, Great info. Thanks. Jim P. On 8/19/10 9:04 AM, Alan Altmark alan_altm...@us.ibm.com wrote: On Thursday, 08/19/2010 at 03:52 EDT, Ronald van der Laan nl50...@gmail.com wrote: I've not seen an answer to your question. But you need to list all the first OSA addresses in the SET VSWITCH command. so: SET VSWITCH name RDEV prim_osa C000 CONNECT If you use: SET VSWITCH name RDEV C000 CONNECT Then you effectively drop your primary OSA connection and switch to your backup one. Sorry, I didn't see this before. You cannot change the active RDEV on a connected VSWITCH. In Jim's case, he wanted to use the *secondary* for something else. To do that SET VSWITCH name RDEV prim_osa You will see the secondary OSA detached from the controller, and it is then available for use. Only use the DETACH command if the VSWITCH becomes unresponsive (in which case you get a snapdump of the system first to go with your PMR). Likewise, never ATTACH an OSA to a VSWITCH controller. If you want to use the *primary* for some other purpose, then you will disrupt the VSWITCH: SET VSWITCH name DISCONNECT SET VSWITCH name RDEV C000 SET VSWITCH name CONNECT To add the former primary OSA back: SET VSWITCH name RDEV C000 prim_osa Of course, prim_osa is now the backup! You could use the disconnect three-step to get it back as the primary, but that's an itch that need not be scratched. (Who cares which one is the backup? It's not like you would use one fast, one slow!) If you want to add and delete OSAs on the fly with no disruption, then you engage link aggregation and define a port group. Alan Altmark z/VM Development IBM Endicott
Re: VSWITCH Question
Will work, but would be nicer to it if you did a set vswitch disconnect first. You will lose all connectivity with no backup, but you know that ;) 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:ib...@listserv.uark.edu] On Behalf Of Dave Keeton Sent: Monday, May 17, 2010 3:54 PM To: IBMVM@LISTSERV.UARK.EDU Subject: [IBMVM] VSWITCH Question We're updating some OSA micro code and I'm trying to determine the most effective way to take the VSWITCH connected to a production OSA offline so the code can update properly. I know that the OSA device has to be vary'd offline, as does the path and CHPID. Is there a way to tell a VSWITCH to shutdown without destroying it? This particular VSWITCH doesn't have a second fail-over address. If I detach the device from the VSWITCH controller, vary the device, path and CHPID offline, will this suffice? Thanks in advance, Dave Keeton
Re: VSWITCH Question
Thank you, Marcy! I appreciate the quick response. Regards, Dave On Mon, 2010-05-17 at 18:32 -0500, Marcy Cortes wrote: Will work, but would be nicer to it if you did a set vswitch disconnect first. You will lose all connectivity with no backup, but you know that ;) 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:ib...@listserv.uark.edu] On Behalf Of Dave Keeton Sent: Monday, May 17, 2010 3:54 PM To: IBMVM@LISTSERV.UARK.EDU Subject: [IBMVM] VSWITCH Question We're updating some OSA micro code and I'm trying to determine the most effective way to take the VSWITCH connected to a production OSA offline so the code can update properly. I know that the OSA device has to be vary'd offline, as does the path and CHPID. Is there a way to tell a VSWITCH to shutdown without destroying it? This particular VSWITCH doesn't have a second fail-over address. If I detach the device from the VSWITCH controller, vary the device, path and CHPID offline, will this suffice? Thanks in advance, Dave Keeton
Re: VSWITCH question
Daniel Allen wrote: I created a VSWITCH at address 0110. I was able to get two (2) Linux machines and one (1) z/OS 1.4 system to use the VSWITCH. I created another VSWITCH at address 010C. When I shutdown one of the two Linux machines and changed the directory entry to use the second VSWITCH, I could not establish connectivity to the Linux machine. What did I do wrong ? Do you get an error at interface startup time? Is the Linux machine authorized to use the Vswitch? -- Rich Smrcina VM Assist, Inc. Phone: 414-491-6001 Ans Service: 360-715-2467 rich.smrcina at vmassist.com http://www.linkedin.com/in/richsmrcina Catch the WAVV! http://www.wavv.org WAVV 2009 - Orlando, FL - May 15-19, 2009
Re: VSWITCH question
No error message. The Linux machine is authorized to use the VSWITCH. -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Rich Smrcina Sent: Tuesday, October 14, 2008 4:08 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: VSWITCH question Daniel Allen wrote: I created a VSWITCH at address 0110. I was able to get two (2) Linux machines and one (1) z/OS 1.4 system to use the VSWITCH. I created another VSWITCH at address 010C. When I shutdown one of the two Linux machines and changed the directory entry to use the second VSWITCH, I could not establish connectivity to the Linux machine. What did I do wrong ? Do you get an error at interface startup time? Is the Linux machine authorized to use the Vswitch? -- Rich Smrcina VM Assist, Inc. Phone: 414-491-6001 Ans Service: 360-715-2467 rich.smrcina at vmassist.com http://www.linkedin.com/in/richsmrcina Catch the WAVV! http://www.wavv.org WAVV 2009 - Orlando, FL - May 15-19, 2009 ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. **
Re: VSWITCH question
The new VSWITCH is the same subnet and guests should all be able to use the same IP's? Scott Rohling On Tue, Oct 14, 2008 at 5:14 PM, Daniel Allen [EMAIL PROTECTED] wrote: No error message. The Linux machine is authorized to use the VSWITCH. -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Rich Smrcina Sent: Tuesday, October 14, 2008 4:08 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: VSWITCH question Daniel Allen wrote: I created a VSWITCH at address 0110. I was able to get two (2) Linux machines and one (1) z/OS 1.4 system to use the VSWITCH. I created another VSWITCH at address 010C. When I shutdown one of the two Linux machines and changed the directory entry to use the second VSWITCH, I could not establish connectivity to the Linux machine. What did I do wrong ? Do you get an error at interface startup time? Is the Linux machine authorized to use the Vswitch? -- Rich Smrcina VM Assist, Inc. Phone: 414-491-6001 Ans Service: 360-715-2467 rich.smrcina at vmassist.com http://www.linkedin.com/in/richsmrcina Catch the WAVV! http://www.wavv.org WAVV 2009 - Orlando, FL - May 15-19, 2009 ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. **
Re: VSWITCH question
Is the 2nd vswitch up - show us Q VSWITCH 2ndone DETAILS. 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 Daniel Allen Sent: Tuesday, October 14, 2008 4:14 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: [IBMVM] VSWITCH question No error message. The Linux machine is authorized to use the VSWITCH. -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Rich Smrcina Sent: Tuesday, October 14, 2008 4:08 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: VSWITCH question Daniel Allen wrote: I created a VSWITCH at address 0110. I was able to get two (2) Linux machines and one (1) z/OS 1.4 system to use the VSWITCH. I created another VSWITCH at address 010C. When I shutdown one of the two Linux machines and changed the directory entry to use the second VSWITCH, I could not establish connectivity to the Linux machine. What did I do wrong ? Do you get an error at interface startup time? Is the Linux machine authorized to use the Vswitch? -- Rich Smrcina VM Assist, Inc. Phone: 414-491-6001 Ans Service: 360-715-2467 rich.smrcina at vmassist.com http://www.linkedin.com/in/richsmrcina Catch the WAVV! http://www.wavv.org WAVV 2009 - Orlando, FL - May 15-19, 2009 ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. **
Re: VSWITCH question
You could also add the SET VSWITCH GRANT statements to AUTOLOG1's profile (prior to RACF/VM or your ESM's autologging, as TCPIP and such should be autologged in AUTOLOG2 profile exec in that case) OR you could add a profile for the GRANT statements via RACF/VM or your ESM if you have one and are really tight on security requirements. Doug -Original Message- From: The IBM z/VM Operating System on behalf of Hodge, Robert L Sent: Fri 16-May-08 18:45 To: IBMVM@LISTSERV.UARK.EDU Subject: Re: VSWITCH question XAUTOLOG the VSWITCH controller userids; typically DTCVSW1 and DTCVSW2. Add the the XAUTOLOG of DTCVSW1 and DTCVSW2 to the PROFILE EXEC on the A-disk on AUTOLOG1 or AUTOLOG2 for the next IPL of the z/VM system. Add define and modify statements to the z/VM SYSTEM CONFIG for the next time z/VM is IPL'ed. DEFINE VSWITCH SWITCH1 RDEV devno CONNECT MODIFY VSWITCH SWITCH1 GRANT userid From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Daniel Allen Sent: Friday, May 16, 2008 4:21 PM To: IBMVM@LISTSERV.UARK.EDU Subject: VSWITCH question I have an OS/390 guest running under z/VM 5.2 using 3 dedicated OSA addresses. The OS/390 guest is IPL'd using the system residence pack. I would like to have the OS/390 guest use a z/VM VSWITCH. I have a copyrighted 2004 IBM Corporation document showing four (4) steps. Step 1. Define the switch : CP DEFINE VSWITCH SWITCH1 RDEV devno CONNECT Step 2. Authorize a connection: CP SET VSWITCH SWITCH1 GRANT userid Step 3. Define a virtual Network Interface Card: CP DEFINE NIC F00 Step 4. Plug NIC into switch: CP COUPLE F00 TO SYSTEM SWITCH1 I have done steps 1 and 2 manually. I have put a NICDEF statement in the USER DIRECT file for the OS/390 guest: NICDEF 104 TYPE QDIO DEV 3 LAN SYSTEM SWITCH1 Is there anything else I need to do ? ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. **
Re: VSWITCH question
Someone commented that it was somewhat clunky, but what we've been doing for the grants is to add two COMMAND statements to each guest's CP Directory entry (actually via an include); the first does the grant for the user, and the second does a couple to connect up the vSwitch, if it isn't already connected. Before this, each new Linux guest had to be added to either the SYSTEM CONFIG (problematic) or AUTOLOG1 (time consuming), and either method allows the person doing it to forget, make a mistake or make some typo in the addition that could cause problems much later during the next IPL, at which time it will take at least a short time to diagnose and repair. Having the whole thing taken care of in one entry in the CP Directory, and included in each guest that needs it, is much less prone to any errors someone (such as me) might tend to make. It's one less thing to remember when creating a new Linux guest. -- Robert P. Nix Mayo Foundation.~. RO-OE-5-55 200 First Street SW/V\ 507-284-0844 Rochester, MN 55905 /( )\ -^^-^^ In theory, theory and practice are the same, but in practice, theory and practice are different. On 5/20/08 10:40 AM, Ponte, Doug [EMAIL PROTECTED] wrote: You could also add the SET VSWITCH GRANT statements to AUTOLOG1's profile (prior to RACF/VM or your ESM's autologging, as TCPIP and such should be autologged in AUTOLOG2 profile exec in that case) OR you could add a profile for the GRANT statements via RACF/VM or your ESM if you have one and are really tight on security requirements. Doug -Original Message- From: The IBM z/VM Operating System on behalf of Hodge, Robert L Sent: Fri 16-May-08 18:45 To: IBMVM@LISTSERV.UARK.EDU Subject: Re: VSWITCH question XAUTOLOG the VSWITCH controller userids; typically DTCVSW1 and DTCVSW2. Add the the XAUTOLOG of DTCVSW1 and DTCVSW2 to the PROFILE EXEC on the A-disk on AUTOLOG1 or AUTOLOG2 for the next IPL of the z/VM system. Add define and modify statements to the z/VM SYSTEM CONFIG for the next time z/VM is IPL'ed. DEFINE VSWITCH SWITCH1 RDEV devno CONNECT MODIFY VSWITCH SWITCH1 GRANT userid From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Daniel Allen Sent: Friday, May 16, 2008 4:21 PM To: IBMVM@LISTSERV.UARK.EDU Subject: VSWITCH question I have an OS/390 guest running under z/VM 5.2 using 3 dedicated OSA addresses. The OS/390 guest is IPL'd using the system residence pack. I would like to have the OS/390 guest use a z/VM VSWITCH. I have a copyrighted 2004 IBM Corporation document showing four (4) steps. Step 1. Define the switch : CP DEFINE VSWITCH SWITCH1 RDEV devno CONNECT Step 2. Authorize a connection: CP SET VSWITCH SWITCH1 GRANT userid Step 3. Define a virtual Network Interface Card: CP DEFINE NIC F00 Step 4. Plug NIC into switch: CP COUPLE F00 TO SYSTEM SWITCH1 I have done steps 1 and 2 manually. I have put a NICDEF statement in the USER DIRECT file for the OS/390 guest: NICDEF 104 TYPE QDIO DEV 3 LAN SYSTEM SWITCH1 Is there anything else I need to do ? ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. **
Re: VSWITCH question
On Tuesday, 05/20/2008 at 02:37 EDT, RPN01 [EMAIL PROTECTED] wrote: Someone commented that it was somewhat clunky, but what we've been doing for the grants is to add two COMMAND statements to each guest's CP Directory entry (actually via an include); the first does the grant for the user, and the second does a couple to connect up the vSwitch, if it isn't already connected. Before this, each new Linux guest had to be added to either the SYSTEM CONFIG (problematic) or AUTOLOG1 (time consuming), and either method allows the person doing it to forget, make a mistake or make some typo in the addition that could cause problems much later during the next IPL, at which time it will take at least a short time to diagnose and repair. Having the whole thing taken care of in one entry in the CP Directory, and included in each guest that needs it, is much less prone to any errors someone (such as me) might tend to make. It's one less thing to remember when creating a new Linux guest. Or the NICDEF plus a single entry in your ESM. RACF has authorization controls for VSWITCHes, Guest LANs, and VLAN IDs. Set it and forget it. Alan Altmark z/VM Development IBM Endicott
Re: VSWITCH question
XAUTOLOG the VSWITCH controller userids; typically DTCVSW1 and DTCVSW2. Add the the XAUTOLOG of DTCVSW1 and DTCVSW2 to the PROFILE EXEC on the A-disk on AUTOLOG1 or AUTOLOG2 for the next IPL of the z/VM system. Add define and modify statements to the z/VM SYSTEM CONFIG for the next time z/VM is IPL'ed. DEFINE VSWITCH SWITCH1 RDEV devno CONNECT MODIFY VSWITCH SWITCH1 GRANT userid From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Daniel Allen Sent: Friday, May 16, 2008 4:21 PM To: IBMVM@LISTSERV.UARK.EDU Subject: VSWITCH question I have an OS/390 guest running under z/VM 5.2 using 3 dedicated OSA addresses. The OS/390 guest is IPL'd using the system residence pack. I would like to have the OS/390 guest use a z/VM VSWITCH. I have a copyrighted 2004 IBM Corporation document showing four (4) steps. Step 1. Define the switch : CP DEFINE VSWITCH SWITCH1 RDEV devno CONNECT Step 2. Authorize a connection: CP SET VSWITCH SWITCH1 GRANT userid Step 3. Define a virtual Network Interface Card: CP DEFINE NIC F00 Step 4. Plug NIC into switch: CP COUPLE F00 TO SYSTEM SWITCH1 I have done steps 1 and 2 manually. I have put a NICDEF statement in the USER DIRECT file for the OS/390 guest: NICDEF 104 TYPE QDIO DEV 3 LAN SYSTEM SWITCH1 Is there anything else I need to do ? ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. **
Re: Vswitch Question from newbie
well, you could create a disconnected vswitch for the .5 network, or just a guest lan. The disconnected vswitch (when you define the vswitch don't code any RDEVs) has the advantage that virtual machine membership, and vlan membership should you go that route, is RACF protected. I think with this configuration you've outlined you will need to instruct each linux machine to not allow any traffic from the other interfaces on the .5. But, yeah, this can be done. David Kreuter Mary Elwood wrote: I hate to have to ask this, but we've looked through documentation and from what I've read it doesn't appear this can be done. But since I'm new to z/VM, Linux, and TCPIP I need to ask the question. Below is the scenario We need to know if we can do what we need to do using vswitches. We run z/VM 5.1 with SUSE SLES9. We run on a z990 (2084). On the z990 we have three OSA’s. Two OSA’s will go to a vswitch for the 10.10.8 network and will have three linux images in the network. We will have one OSA that will to go a vswitch for the 10.10.6 network and will have one linux image. We then want to create a vswitch for a 10.10.5 network that would be a private network where all four linux images can communicate. We need the one linux image on the 10.10.6 network to be able to push code changes up to the three linux images on the 10.10.8 network. Is this possible??? The vswitch for the 10.10.5 network has no OSA on purpose. We want the 10.10.5 to be a separate virtual network internet to z/VM only. We can have no outside access to the 10.10.5 network other than the four linux images on the 10.10.8 and the 10.10..6 networks. I hope this is clear. Thank you for your help and patience. Mary Elwood Navy Federal Credit Union Vienna, VA 703-206-4201 No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.405 / Virus Database: 268.11.6/430 - Release Date: 28/08/2006
Re: Vswitch Question from newbie
At 01:44 PM 8/29/2006, you wrote: On Tuesday, 08/29/2006 at 01:21 AST, Mary Elwood [EMAIL PROTECTED] wrote: As a newbie, I hope you'll take the opportunity to attend the System z9 and zSeries Expo in October in Orlando. Go to http://www.vm.ibm.com/events and click on the link for the Expo. We're providing a lot of education on the VSWITCH and Guest LANs! Mary, IF you cant make it to the Z Expo, please consider the next SHARE which will be in Tampa the week of Feb 11. Plenty of good sessions there including a few by Alan himself. Duane
