David says it better than I did. The point I was attempting to make is that prior to 5.3.0, the default VLAN on the Virtual Switch is the same as the native VLAN id and should match your physical switches native VLAN. I assumed the guest on the VSWITCH was not tagging the frames. When you get into untagged traffic, things can get tricker:
If you are using untagged traffic, you should always connect to an access port, and the default VLAN should never appear, because the stack should do no tagging at all (the switch will just destroy it, so there's really no point in doing tagging at all). We attempted to clear up all the confusion over what is the default and what is the native in z/VM 5.3.0. Tracy (Bolinda) Adams [EMAIL PROTECTED] z/VM Development - Virtual Networking David Boyes <[EMAIL PROTECTED]> Sent by: Linux on 390 Port <[email protected]> 09/05/2007 09:57 AM Please respond to Linux on 390 Port <[email protected]> To [email protected] cc Subject Re: Another VSWITCH question Huh? One more time, in very small words, please.... As I understand it, the rules are: If the switch port is defined as access mode (IOS "switchport mode access"), packets with tags presented are either: 1) stripped of the tag and the switch inserts the correct tag as per port definition, or 2) if the tag does not match the defined tag for the port, the packet is dropped. It's the straitjacket mode; you can't get out of the box the network designer built. If the switch port is defined as trunk mode (IOS "switchport mode trunk"), packets must already have tags assigned, and the switch either passes the tag as is if it matches the permitted tags for that port, or drops the packet if the tag does not match any of the permitted VLANs for that port. If you are using untagged traffic, you should always connect to an access port, and the default VLAN should never appear, because the stack should do no tagging at all (the switch will just destroy it, so there's really no point in doing tagging at all). If you are doing tagging, you should be connected to a trunk port, and any traffic coming out of that OSA should have appropriate tags already assigned by the stack. Do I misunderstand you? -- db ---------------------------------------------------------------------- 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
