On Thursday, 06/24/2004 at 10:49 ZE2, Rob van der Heij <[EMAIL PROTECTED]> wrote: > If your Linux guest lives in more than one VLAN you need to enable VLAN > inside Linux and make it tag the outbound traffic itself (and have CP > validate that against the list of VLAN IDs). That's kind of double work. > I am not sure you need Linux very often in multiple VLAN IDs, but I may > be wrong.
It is used by routers and firewalls that need to get data from one subnet to another. The subnets may be on the same physical interface but with different VLAN IDs. If a host isn't routing, it needs only a "virtual access port" with a single VLAN ID assigned. Also, in order to be compatible with z/VM 5.1, please don't explicitly use "VLAN ANY" in the SET VSWITCH GRANT. Just let it default, as VLAN ANY is removed in z/VM 5.1 and is replaced by the concepts of VLAN-unaware VSWITCHes, default VLAN IDs, virtual port VLAN IDs, and virtual trunk and access port definitions. VLAN ANY as expressed in z/VM 4.4 is a concept alien to IEEE 802.1q, the standard governing the use of VLANs. If a guest needs access to more than one VLAN, explicitly list them in the GRANT. Alan Altmark Sr. Software Engineer IBM z/VM Development ---------------------------------------------------------------------- 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
