On Tuesday, 12/23/2008 at 09:05 EST, עופר ברוך <[email protected]> wrote: > I configured the VSWITCH to be VLAN aware and the Linux to be unaware > (meaning the Linux is working as if no VLAN tagging is enabled). > I used the VLAN <default_vlan_id> parameter on the DEFINE VSWITCH command > and the PORTType ACCESS parameter to make the guest be unaware of VLAN IDs.
FYI, PORTTYPE ACCESS is the default guest port type, without regard to the specification of the VLAN keyword on DEFINE VSWITCH. Also (clip this and put in your networking scrapbook): 1. Every VLAN-capable switch has something called a *native* VLAN id. It has a default value of 1. Installations often change this value to avoid accidents. 2. Every trunk port on a switch has a *default port* VLAN id that is applied when an untagged frame is received. This defaults to the *native* VLAN id, but can be changed by the installation on a per-port basis. 3a. z/VM 5.3 and later: On a VLAN-aware VSWITCH, the NATIVE keyword must be used to match the *port default* VLAN id. The VLAN keyword on DEFINE VSWITCH is used solely indicate VLAN awareness and to avoid specifying a VLAN id on the SET VSWITCH GRANT. If you don't use the NATIVE keyword, it acts like z/VM 5.2. 3b. z/VM 5.2 and earler: The VLAN keyword combines the functions of the z/VM 5.3 VLAN and NATIVE functions. Be careful. It must match the port default VLAN ID, even if that isn't the VLAN you would like to assign the guests to. This means you always specify a VLAN id on a SET VSWITCH GRANT. 4. Before you define a VLAN-aware VSWITCH, you should ask for a copy of the switch configuration parameters, preferably by seeing a copy of the switch queries, rather than trusting someone's memory. 'Cuz if the values from step 3 don't match the physical switch configuration, you will get anomalous results that include "doesn't work". Alan Altmark z/VM Development IBM Endicott
