2016-04-21 14:52 GMT-04:00 Dave Myers <dave.my...@siriuscom.com>: > Since Mark has told us that what we're attempting to do is not supported > by the RAM system...I'll close this thread and thank you all for your > feedback. > > I do have one last question for Alan. > > In this statement does the VLAN AWARE specify TRUNKING to the uplink OSA ? > If not what is the difference between what we coded VLAN 229 and VLAN > AWARE? > > DEFINE VSWITCH VSW1 RDEV 400.P1 VLAN AWARE NATIVE NONE > > Thanks, > Dave > > I believe Mark said that having linux to handle vlan tagging is hard.
But what you are trying to do is different. In your case, vswitch is removing/adding vlan tags from/to frames on the fly. To do what Mark mentioned (and I doubt this is what you want to do) you have to specify porttype trunk when you do the grant command. This will let linux guest to see vlan tags. But I am pretty sure that you don't want to do this. In your case, you let the vswitch to do vlan tagging and untaging. So vswitch has to be vlan aware so it can receive and understand tagged frames from the outside real, switch. When it receives a tagged frame from the outside world it removes the vlan tag, and send the actual frame to guests which have "granted" access to that speciffic vlan. And when vswitch receives an untaged frame from guest, it adds a vlan tag to it and sends it to real switch (trunk port specifically) . So from linux perspective, there are no vlan tags and everything is nice an easy. So what you are doing, should work perfectly fine as long the real switch is set up correctly (port is set to trunk and your vlan was added to it) When it comes to syntax define vswitch vlan aware vs vswitch .. vlan xxx I don't believe makes any difference in your case According to manual "defvid defines the virtual switch as a VLAN-aware switch supporting IEEE standard 802.lQ. The defvid defines the default VLAN ID to be assigned to guest ports when no VLAN ID is coded on the SET VSWITCH GRANT VLAN command" Gregory ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/
