You can have the same "practical" topology with just different VSWITCHES. For the Linux side, the VSWITCH is transparent, and the only "hardware part" that matters is the OSA channels. As long as you have the same number everywhere, it won't be a problem.
You can have your "Group1" Linuxes with an eth0 using channels 1000,1001,1002 on VSWGRP1, and "Group2" Linuxes using the same configuration: OSA eth0 with channels 1000,1001,1002 but on VSWGRP2. >From the Linux point of view, does not matter if this penguin is on VSWGRP1 or VSWGRP2... You need only to give Linux permission to access the vswitch, and change the NICDEF statement on USER DIRECT to change the virtual switch where you will virtually plug that virtual osa virtual cable... Mauro http://mauro.limeiratem.com - registered Linux User: 294521 Scripture is both history, and a love letter from God. 2012/6/5 David Boyes <dbo...@sinenomine.net>: >> >>> On 6/5/2012 at 07:26 AM, "Krpata, Pavel" <pavel.krp...@ca.com> >> wrote: >> > Thus I thought about connecting uplinks of all 'local' vswitches in >> > each set to a single main vswitch. >> > Is anything like this possible or it is nonsense in z/VM virtual world? >> >> I don't think it's possible without involving one or more Linux guests to >> act as >> routers between the VSWITCHes. > > You'd have to do it with at least one Linux guest configured to bridge rather > than route. See the Linux L2 bridging how-to to get instructions on how to > set it up. Short version: > > You set up a TAP adapter as br0 on the Linux guest and then use virtual L2 > adapters to attach to the different VSWITCHes as effectively 802.1q trunk > ports, or access ports would do if all you're trying to do is emulate a > cascaded set of hubs/switches. Doing something VLAN-capable will be more > complex yet -- can be done, but not easy to manage. > > Fair warning: It'll be *very* CPU intensive (that guest has to look at every > frame passing through) and unless you give the bridge Linux guest QUICKDSP or > a substantial SHARE REL/ABS percentage, performance will probably not be good. > > ---------------------------------------------------------------------- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 > ---------------------------------------------------------------------- > For more information on Linux on System z, visit > http://wiki.linuxvm.org/ ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/
