Hi, 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.
If you want a guest to receive packets from a different VLAN ID then the default you can specify it on the GRANT command: SET VSWITCH <vswitch_name> GRANT <userid> VLAN <vlan_id> That is all... Offer Baruch. -----Original Message----- From: Linux on 390 Port [mailto:[email protected]] On Behalf Of Ayer, Paul W Sent: Tuesday, December 23, 2008 3:00 PM To: [email protected] Subject: VLAN tagging Good Morning all, Was able sometime ago to get the layer 2 interfaces working fine. Thanks to everyone for their input. As many on the list had said it was not so hard to do and really just had to (in redhat) Change APR=no to yes, add OPTIONS=layer2=1 and VSWITCH=1 and all worked fine. That was on a Vswitch that was VLAN unaware. We are now converting to a Vswitch that is VLAN aware. I have not found anything that needs to be done inside the Linux. Is anyone doing Layer2 with VLAN tagging? If yes did you have to add any parms to the eth defs (VLAN=yes maybe)? Thanks, Paul ---------------------------------------------------------------------- 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 No virus found in this incoming message. Checked by AVG - http://www.avg.com Version: 8.0.176 / Virus Database: 270.10.0/1861 - Release Date: 22/12/2008 11:23 ---------------------------------------------------------------------- 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
