The vswitch can be vlan aware with Linux connecting on access ports, that's legit. The vswitch is then solely responsible for vlan packet insertion and removal.
So adapter scenario 3 is a disconnected vswitch on layer 2. On adapter 2 if you remove the real OSA devices can you communicate between the virtual Linux machines? One piece of advise would be to check the microcode levels of your osa devices. There are some anomalies with sharing layer 2 and 3 traffic corrected on recent microcode updates. Although you are not sharing layer 2 and 3 it worth a shot as perhaps the MCL corrected other layer 2 problems as well. Just to confirm with the output from lsqeth that you are using layer2? And the layer 2 vswitch is defined as TYPE ETHERNET ? What does the output of NETSTAT ARP ALL TCP <vswitch controller machine name inserted here> show? And you need to this command twice, breath in between. David Kreuter -------- Original Message -------- Subject: Re: Linux on Z networking issue From: Pat Carroll <[email protected]> Date: Fri, June 04, 2010 3:12 pm To: [email protected] If you're doing vlan tagging you need to configure as a trunk port Patrick Carroll | Technology Architect II L.L.Bean, Inc.(r) | Double L St. | Freeport ME 04033 http://www.llbean.com | [email protected] | 207.552.2426 CONFIDENTIALITY NOTICE: This e-mail and any attachments may contain confidential information that is legally privileged. The information is solely for the use of the intended recipient(s). Any disclosure, copying, distribution, or other use of this information is strictly prohibited. If you have received this e-mail in error, please notify the sender by return e-mail and delete this message. -----Original Message----- From: Linux on 390 Port [mailto:[email protected]] On Behalf Of Peter Pauer Sent: Friday, June 04, 2010 12:46 PM To: [email protected] Subject: Linux on Z networking issue We have a customer experiencing difficulties with a s390 Linux under VM networking The Linux OS's tried are SuSe 11, SuSe 10.3 and RedHat 5.5 For test purposes on the guests we have defined Adapter 1: vswitch 1, layer 3, OSA card attached. 142.* ip address Adapter 2: vswitch 2, vlan aware, port access, layer 2, OSA card attached 10.* ip address Adapter 3: vswitch 3, vlan aware, port access, layer 2, NO OSA CARD 192.* ip address Adapter 1: is connected and working correctly between the VM guests and on the intranet. Adapter 2: is connected and not working between the VM guests also not working on the intranet. Adapter 3: is connected and working between the guests, no physical connection to the intranet. Only apparent difference between adapter 2 and adapter 3 is that an OSA card that is attached to Adapter 2. Any one have experience with a similar situation/resolution? Peter ---------------------------------------------------------------------- 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 ---------------------------------------------------------------------- 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
