Re: Vm ZLinux VSWITCH question
Hi Ron, very glad to hear that your problem is solved now and all works for you ! Sometimes a few explaining words are very usefull for further understanding of manuals/presentations. At least that is my experience ... If there should occure any further problems pls. feel free to address them on- or offline :-) ciao Lutz -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Vm ZLinux VSWITCH question
Jerry, You pointed me at ib...@listserv.uark.edu. I'd already subscribed to this as an RSS feed in Google reader. That's my prefered method of seeing all the detail when I want to rather than getting interrupted by emails all the time. I use the same process for IBM-MAIN and several other groups/lists I follow. However according to Google reader the last update for this list was october 2011. I assumed it was an inactive list. From logging on to the actual server I can see that it is a very active list. I guess Google has dropped IBMVM. Do you, or does anyone, know of an RSS feed for IBMVM? Ron. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Vm ZLinux VSWITCH question
Hi Ron, alhough I think the IBMVM forum is the right place to address your question, I do not see a the 'real' OSD-device representing your VSWITCH1. I.E. : RDEV: 0500.P00 VDEV: 0500 Controller: DTCVSW2 ciao Lutz -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Vm ZLinux VSWITCH question
Sorry guys. 0870 is the correct address. Everywhere where I put 780 was wrong. The OSA card on the zLinux LPAR is 0870 and I defined a NICDEF on 870 for the zLinux VM. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Vm ZLinux VSWITCH question
Lutz, You say I do not see a the 'real' OSD-device representing your VSWITCH1 and I agree we have not defined that, it wasn't specified in the example i was following which said simply issue the commands - CP DEFINE VSWITCH VSWITCH1 CP SET VSWITCH VSWITCH1 GRANT LNXVM Because an RDEV was not on the sample command in the book I thought it would find this out from TCPIP. Should the define VSWITCH be - CP DEFINE VSWITCH VSWITCH1 RDEV 888 to connect to the same OSA card as used by the VM machine? Is that what you are saying or am I missunderstanding you? Ron. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Vm ZLinux VSWITCH question
Sorry for fast finger tips - I should have said can not instead of can' :-( -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Vm ZLinux VSWITCH question
Lutz, Thanks for your help. As I said before I used to be a VM sysprog 20+ years ago before TCPIP entered the IBM world. I was hoping the VSWITCH would allow us to use the same OSA card as VM. That was what I was trying to achieve. I had thought it might be like VMWARE's VM where I can have several virtual machines all using different IP addresses via the same network card as the host windows box. Obviously it isn't but I don't have another picture in my head. There is no way to get this all running of the one OSA? We need one card for the TCPIP VM and another one for the VSWITCH? We will pull another OSA card across to this LPAR and try again. Thanks for the clarification. Ron. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Vm ZLinux VSWITCH question
Lutz But since this topic is not related to z/OS ... Some time ago I was chastised very roundly indeed by one of the usual suspects inhabiting this list for what this very suggestion implies!!! Apparently, IBM-MAIN is ***not*** exclusively to be regarded as a z/OS list. Perhaps if this were so it would have a more appropriate title. ... maybe we should discuss it off-line ? Furthermore, there is some competition for degree of irritation in an intriguing problem - some say issue! - having been presented only to have what may be a resolution discovered off-line. Maybe not! Chris Mason On Wed, 20 Jun 2012 09:42:18 -0500, Lutz Hamann lutz.ham...@betasystems.com wrote: Ron, of course you can' specify 888 as RDEV for your VSWITCH1 because you've attached this OSD-device to TCPIP ! You should have further real device (i.e. 870) for your VSWITCH1 to connect to 'outer-world' ... But since this topic is not related to z/OS - maybe we should discuss it off-line ? ciao Lutz -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Vm ZLinux VSWITCH question
Ron There is no way to get this all running of the one OSA? Paying attention to the question mark at the end of what is otherwise apparently a statement, my very limited understanding of the principles of VSWITCH is that one real OSA is all you need and then only if you want your virtual LAN to morph into a real LAN at some point in its existence. Please read at least the redpaper and come back when you have digested the principles of VSWITCH. Here is a definition from the Introduction to Connectivity Terminology chapter of the Connectivity manual: quote 1.2.1.4 What Is a Guest LAN? A guest LAN represents a simulated LAN segment that can be connected to simulated network interface cards. There are two types of LAN segments: OSA-Express and HiperSockets. Each guest LAN is isolated from other guest LANs on the same system (unless some member of one LAN group acts as a router to other groups). 1.2.1.5 What Is a Virtual Switch? A virtual switch is a special type of guest LAN that provides external LAN connectivity through an OSA-Express device without the need for a routing virtual machine. /quote http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/HCSC9C00/1.2.1.4 http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/HCSC9C00/1.2.1.5 Note that a guest LAN, obviously the OSA-Express flavour, is what I called a virtual LAN above to emphasis the passage through minimally a single OSA feature to a *real* LAN, external LAN connectivity. I do hope I've remembered the principles of a VSWITCH from the time I last read up on the topic a few years ago! Chris Mason On Wed, 20 Jun 2012 10:19:53 -0500, Ron MacRae ronmac...@hotmail.co.uk wrote: Lutz, Thanks for your help. As I said before I used to be a VM sysprog 20+ years ago before TCPIP entered the IBM world. I was hoping the VSWITCH would allow us to use the same OSA card as VM. That was what I was trying to achieve. I had thought it might be like VMWARE's VM where I can have several virtual machines all using different IP addresses via the same network card as the host windows box. Obviously it isn't but I don't have another picture in my head. There is no way to get this all running of the one OSA? We need one card for the TCPIP VM and another one for the VSWITCH? We will pull another OSA card across to this LPAR and try again. Thanks for the clarification. Ron. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Vm ZLinux VSWITCH question
Chris, In reply to your suggestions. 1) I've already spoken to our IP guy but he's a z/OS guy, as am I really, and between us we're still stuck. 2) Thanks for the redpaper, I hadn't seen that one. However a lot of the detail on the older versions doesn't seem to match with VM 6.2, but that is likely down to my lack of understanding. 3) I'll try IBMTCP-L. As i said I tried some VM lists but never saw any replies or indeed traffic. I've got an up to date copy of the connectivity manual. It comes with the VM 6.2 documentation set. Thanks, Ron. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Vm ZLinux VSWITCH question
You can use the same OSA card. But what you need to do is give that OSA to the vswitch and then connect TCPIP to the vswitch instead of the OSA. There are some changes to TCPIP that would have to happen. Take this to the vm list - it is quite active and lots of help there. The IBM z/VM Operating System ib...@listserv.uark.edu On Wed, Jun 20, 2012 at 11:41 AM, Lutz Hamann lutz.ham...@betasystems.comwrote: Sorry Chris - I simply did not want to bore the folks here with z/VM -specific details :-) And yes I know that IBM-MAIN is and has always been a good focal point for all mainframe-related stuff ... ciao Lutz -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- The postings on this site are my own and don’t necessarily represent Mainline’s positions or opinions Mark D Pace Senior Systems Engineer Mainline Information Systems -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Vm ZLinux VSWITCH question
On 6/20/2012 at 11:19 AM, Ron MacRae ronmac...@hotmail.co.uk wrote: I was hoping the VSWITCH would allow us to use the same OSA card as VM. That was what I was trying to achieve. I had thought it might be like VMWARE's VM where I can have several virtual machines all using different IP addresses via the same network card as the host windows box. Obviously it isn't but I don't have another picture in my head. There is no way to get this all running of the one OSA? We need one card for the TCPIP VM and another one for the VSWITCH? You _can_ do what you want. You just need to understand that one OSA card can have many subchannel addresses. You can share the card, but not the subchannel addresses. So, from MAINT, or any other userid with CP class B, do a #cp q osa free command. Pick any three consecutive addresses, and specify the first one as the RDEV for the VSWITCH. Mark Post -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Vm ZLinux VSWITCH question
Ron - This list is the active z/VM list and has all the experts on the use of the vswitch you need ib...@listserv.uark.edu Jerry Whitteridge Lead Systems Programmer Safeway Inc. 925 951 4184 If you feel in control you just aren't going fast enough. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@listserv.ua.edu] On Behalf Of Ron MacRae Sent: Wednesday, June 20, 2012 8:47 AM To: IBM-MAIN@listserv.ua.edu Subject: Re: Vm ZLinux VSWITCH question Chris, In reply to your suggestions. 1) I've already spoken to our IP guy but he's a z/OS guy, as am I really, and between us we're still stuck. 2) Thanks for the redpaper, I hadn't seen that one. However a lot of the detail on the older versions doesn't seem to match with VM 6.2, but that is likely down to my lack of understanding. 3) I'll try IBMTCP-L. As i said I tried some VM lists but never saw any replies or indeed traffic. I've got an up to date copy of the connectivity manual. It comes with the VM 6.2 documentation set. Thanks, Ron. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN Email Firewall made the following annotations. -- Warning: All e-mail sent to this address will be received by the corporate e-mail system, and is subject to archival and review by someone other than the recipient. This e-mail may contain proprietary information and is intended only for the use of the intended recipient(s). If the reader of this message is not the intended recipient(s), you are notified that you have received this message in error and that any review, dissemination, distribution or copying of this message is strictly prohibited. If you have received this message in error, please notify the sender immediately. == -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
