Re: Guest Lan/VSwitch/VLAN
I appreciate everyone's input. We are going to try to implement the VSWITCH. Thanks Gene Gene Walters System Programmer WV Dept of Administration - OT 304-558-5914 ext 8902 Fax 304-558-1351 [EMAIL PROTECTED] 5/14/2007 1:42:51 PM If it were me, I'd probably go with the VSWITCH. Heartbeat packets really don't exploit the best parts of real hipersockets (high volume bulk data transfer) much, and the ability to separate stuff easily later is a big architectural win in my book. Makes sense, particularly in our case where we have redundant OSA cards. Although since real hipersockets run over the system memory backplane, you also have multiple buses to work with there, so you get built-in redundancy. If that memory bus isn't working, then you're not doing much with the machine anyway, and it's always built in, so you don't have to worry about it at DR sites. I'd still do the VSWITCH, though. IMHO, it's a more flexible option. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] 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 [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Guest Lan/VSwitch/VLAN
If it were me, I'd probably go with the VSWITCH. Heartbeat packets really don't exploit the best parts of real hipersockets (high volume bulk data transfer) much, and the ability to separate stuff easily later is a big architectural win in my book. Makes sense, particularly in our case where we have redundant OSA cards. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Guest Lan/VSwitch/VLAN
If it were me, I'd probably go with the VSWITCH. Heartbeat packets really don't exploit the best parts of real hipersockets (high volume bulk data transfer) much, and the ability to separate stuff easily later is a big architectural win in my book. Makes sense, particularly in our case where we have redundant OSA cards. Although since real hipersockets run over the system memory backplane, you also have multiple buses to work with there, so you get built-in redundancy. If that memory bus isn't working, then you're not doing much with the machine anyway, and it's always built in, so you don't have to worry about it at DR sites. I'd still do the VSWITCH, though. IMHO, it's a more flexible option. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Guest Lan/VSwitch/VLAN
Check out http://www.zjournal.com/index.cfm?section=articleaid=315 Planning and Implementing VSWITCH for Linux/390 Guests. That should give you a good idea of what the differences are. I am still not certain on what we need to do but now I understand the difference. I have one z9 foot-print with two books. In one I run one zVM1 (CP1) and on the sencond, I run zVM2 (CP2). Under each zVM I run Linux guest servers. The fail-over for a given Linux guest is on the opposite zVM. My question, how should I set up the life-line between the fail-over linux guests? do I need to go hypersockets, regular LAN, etc? -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Guest Lan/VSwitch/VLAN
I have one z9 foot-print with two books. In one I run one zVM1 (CP1) and on the sencond, I run zVM2 (CP2). Under each zVM I run Linux guest servers. The fail-over for a given Linux guest is on the opposite zVM. My question, how should I set up the life-line between the fail-over linux guests? do I need to go hypersockets, regular LAN, etc? Either real hipersocket (completely inside the box, no external traffic required) or a VLAN-aware VSWITCH with external devices handling network HSRP. The plus side of the hipersocket is that as long as the mainframe hardware is functioning at all, you can rely on it being there, and outside the scope of random network meltdowns outside the box. Disadvantage is the complexity of setup and that there are a limited number of real hipersockets in the box, and the IO gens to use them are not trivial. You also don't want to mix traffic from other things on the same segment as your heartbeat processes; some heartbeat monitors get a little hyperactive if they see excessive traffic. The downside is that physical hipersockets arent' extendable to another box. The plus of a VLAN aware VSWITCH is that all the network redundancy processing can be moved to outboard equipment, and you can have the routers do all the failover processing and monitoring. This is much more familiar to your average networking type, and is more likely to pass your architecture board without irritating explanations. Since VLANs can be routed across existing layer 2 infrastructure, you get the ability to eventually separate the two LPARs w/o changing the setup, and if there are encryption requirements, you can implement them in the external boxes w/o impacting resource utilization on the mainframe side. If it were me, I'd probably go with the VSWITCH. Heartbeat packets really don't exploit the best parts of real hipersockets (high volume bulk data transfer) much, and the ability to separate stuff easily later is a big architectural win in my book. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Guest Lan/VSwitch/VLAN
Hi All, I know this is a broad question, but I am trying to understand some things. We currently are using CTC connections for our network access to our Linux Instances running under VM. We were told that CTC's were doing it the hard way. So I am trying to figure out what the other way is. We have Z/VM 5.1 running on an IFL and an OSA-Express card. What should we be using instead of CTC's for network connection, VGuest, VSwitch VLAN? I'm confused as to what each actually does. Any help would be appreciated. Thanks Gene Gene Walters System Programmer WV Dept of Administration - OT 304-558-5914 ext 8902 Fax 304-558-1351 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Guest Lan/VSwitch/VLAN
Yep, that is the hard way, now a days. Vswitch is the way to go. Much, much easier to setup and better performance along with automatic fall over, being VERY easy to setup. No longer will you be using your TCPIP stack on VM for routing packets to guest OSs. The VM stack will only be used for CMS client/servers. Now, converting over, is a small pain. Nothing is as easy as leaving everything alone G. You will need another set of OSA addresses (I think your z/890 has a few to spare). Vswitch is basically, DTCVSW1 and DTCVSW2 service machines (controllers for failover). And something similar to the following in your system config file: DEFINE VSWITCH VSW1 RDEV 2000 2003 PRIROUTER MODIFY VSWITCH VSW1 GRANT TCPIP MODIFY VSWITCH VSW1 GRANT LINUX24 MODIFY VSWITCH VSW1 GRANT LINUX27 MODIFY VSWITCH VSW1 GRANT DOSESA2 MODIFY VSWITCH VSW1 GRANT Y2KESA2 MODIFY VSWITCH VSW1 GRANT NEWESA4 MODIFY VSWITCH VSW1 GRANT TSTESA4 MODIFY VSWITCH VSW1 GRANT GEACESA4 MODIFY VSWITCH VSW1 GRANT GEACESA5 MODIFY VSWITCH VSW1 GRANT GEACESA6 MODIFY VSWITCH VSW1 GRANT STLESA2 MODIFY VSWITCH VSW1 GRANT STLESA2F MODIFY VSWITCH VSW1 GRANT TSTESA5 MODIFY VSWITCH VSW1 GRANT TSTESA5F MODIFY VSWITCH VSW1 GRANT HIGHAVL MODIFY VSWITCH VSW1 GRANT TSTESA3 VMLAN MACPREFIX 030001 (there are dynamic versions to these commands, so you don't have to cycle VM to bring it up) The Linux machine has something similar to the following in its directory: NICDEF 600 TYPE QDIO LAN SYSTEM VSW1 And then in Linux, you configure an qeth type device. You network does change. You are no longer routing thru TCPIP. Your default gateway may now be your router (xxx.xxx.xxx.001 address), instead of the IP address for TCPIP. It is easiest to create a new Linux image (if you are not an IP geek), to play and test with. For me, it took a while for the change in routing, to really sink in my mind (or sink my mind). Tom Duerbusch THD Consulting Gene Walters [EMAIL PROTECTED] 5/8/2007 12:36 PM Hi All, I know this is a broad question, but I am trying to understand some things. We currently are using CTC connections for our network access to our Linux Instances running under VM. We were told that CTC's were doing it the hard way. So I am trying to figure out what the other way is. We have Z/VM 5.1 running on an IFL and an OSA-Express card. What should we be using instead of CTC's for network connection, VGuest, VSwitch VLAN? I'm confused as to what each actually does. Any help would be appreciated. Thanks Gene Gene Walters System Programmer WV Dept of Administration - OT 304-558-5914 ext 8902 Fax 304-558-1351 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] 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 [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Guest Lan/VSwitch/VLAN
In my opinion you are much better off using VSWITCH's. It is one layer less in the path length and you don't have to have a host to perform routing. The vswitch also supports layer 2 routing rather than layer 3 (more efficient). Thanks, Gary L. Detro Senior IT Specialist 1177 S. Belt Line Rd; Coppell, TX 75019 Internal Mail Stop: 77-01-3001O; Coppell, TX Phone: 469-549-8174 (t/l 603-8174); Fax: 469-549-8235 (t/l 603-8235) Send me an email [EMAIL PROTECTED] IBM Global Solution Center Gene Walters [EMAIL PROTECTED] Sent by: Linux on 390 Port LINUX-390@VM.MARIST.EDU 05/08/2007 12:36 PM Please respond to Linux on 390 Port LINUX-390@VM.MARIST.EDU To LINUX-390@VM.MARIST.EDU cc Subject Guest Lan/VSwitch/VLAN Hi All, I know this is a broad question, but I am trying to understand some things. We currently are using CTC connections for our network access to our Linux Instances running under VM. We were told that CTC's were doing it the hard way. So I am trying to figure out what the other way is. We have Z/VM 5.1 running on an IFL and an OSA-Express card. What should we be using instead of CTC's for network connection, VGuest, VSwitch VLAN? I'm confused as to what each actually does. Any help would be appreciated. Thanks Gene Gene Walters System Programmer WV Dept of Administration - OT 304-558-5914 ext 8902 Fax 304-558-1351 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 image/jpegimage/jpeg
Re: Guest Lan/VSwitch/VLAN
You should take a look at using vswitch. It lets you horizontally extend your physical networks into a zvm guest lan without routing on zvm. You're most of the way there sort of already with your osa card. Vswitch lets you have the same network defined on physical and virtual hosts. No routing on zvm. Do that first, and then you should look at using vlans. Vlans isolate subnets into smaller groupings. Talk to your net admin. IF you are the net admin, too, then think about it! Vswitches do not depend on vlans. Vlans is an IEEE 802.1Q standard. Guest lans are a zvm implementation of virtualized networks, i.e., no special hardware required (no cables, routers, switches, etc.). IBM couldn't call 'em virtual lans 'cause that was already terminology used by 802.1Q (see above). David Kreuter -Original Message- From: Linux on 390 Port on behalf of Gene Walters Sent: Tue 5/8/2007 1:36 PM To: LINUX-390@VM.MARIST.EDU Subject: Guest Lan/VSwitch/VLAN Hi All, I know this is a broad question, but I am trying to understand some things. We currently are using CTC connections for our network access to our Linux Instances running under VM. We were told that CTC's were doing it the hard way. So I am trying to figure out what the other way is. We have Z/VM 5.1 running on an IFL and an OSA-Express card. What should we be using instead of CTC's for network connection, VGuest, VSwitch VLAN? I'm confused as to what each actually does. Any help would be appreciated. Thanks Gene Gene Walters System Programmer WV Dept of Administration - OT 304-558-5914 ext 8902 Fax 304-558-1351 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] 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 [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Guest Lan/VSwitch/VLAN
Gene, Yes, VSWITCH seems to be the most popular. We describe how to implement it in a number of Virtualization Cookbooks on http://linuxvm.org/present/. For z/VM 5.1 you have to manually define the VSWITCH controllers. See: http://linuxvm.org/present/misc/virt-cookbook-1.pdf If you move up to z/VM 5.2, there are three other more recent books at the top of the page, depending on the Linux you want to use: SLES 9, SLES 10 or RHEL 5 (there's also a redbook on ibm.com/redbooks describing RHEL 4). Take your pick. Hope this helps. Mike MacIsaac [EMAIL PROTECTED] (845) 433-7061 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Guest Lan/VSwitch/VLAN
On Tuesday, 05/08/2007 at 01:36 AST, Gene Walters [EMAIL PROTECTED] wrote: Hi All, I know this is a broad question, but I am trying to understand some things. We currently are using CTC connections for our network access to our Linux Instances running under VM. We were told that CTC's were doing it the hard way. So I am trying to figure out what the other way is. We have Z/VM 5.1 running on an IFL and an OSA-Express card. What should we be using instead of CTC's for network connection, VGuest, VSwitch VLAN? I'm confused as to what each actually does. Any help would be appreciated. 1. Guest LAN. A simulated LAN segment contained entirely within CP. Connections to the Outside are done by using a virtual router. That is, a virtual machine that connects both to the Outside and to the Guest LAN. Since it is a separate LAN segment, it is its own subnet. 2. Virtual Switch (VSWITCH). A simulated LAN segment that is BRIDGED to the Outside by CP (no virtual router). Because it is BRIDGED to the Outside, not ROUTED, it is NOT a separate LAN segment and so it part of the subnet the associated OSA is connectd to. It is possible for a single VSWITCH to carry traffic for two ore more LAN segments at the same time, if needed, by taking advantage of IEEE VLANs. Alan Altmark z/VM Development IBM Endicott -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Guest Lan/VSwitch/VLAN
On Tue, May 8, 2007 at 1:36 PM, in message [EMAIL PROTECTED], Gene Walters [EMAIL PROTECTED] wrote: -snip- We have Z/VM 5.1 running on an IFL and an OSA-Express card. What should we be using instead of CTC's for network connection, VGuest, VSwitch VLAN? I'm confused as to what each actually does. Check out http://www.zjournal.com/index.cfm?section=articleaid=315 Planning and Implementing VSWITCH for Linux/390 Guests. That should give you a good idea of what the differences are. Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
