So I figured out that my stacking the ifcfg-vlanxxx on top of bond0 is ok. I just had the wrong OSA card which is why my packets left and never came home. Too many cards...
And there are 3 ways to implement vlan tagging in Linux .. which doesn't exactly make it any easier to debug anything but I guess flexibility is a good thing. Marcy This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -----Original Message----- From: Linux on 390 Port [mailto:[email protected]] On Behalf Of Ayer, Paul W Sent: Tuesday, March 29, 2011 11:34 AM To: [email protected] Subject: Re: [LINUX-390] VLAN tagging and Channel Bonding with Linux Glad to be able to help. One other thing I found is that with Vswitches MIIMON does not work .. thus I use the arp. Reason is the OSA's can go down but the Vswitch and linux NIC's never will ... or the real switch could die .. linux will never know. We have setup eth0's and eth1's to go to different Vswitches so that with their own link aggregated over pairs too. Anyways the nice part is that if for some reason the arp does not work over eth0 then bonding stops using it until the arp works again and it starts using it again. No action needs to be taken. We monitor /proc/net/bonding/bond0 for the status ... the eth0 or eth1 are always up via ifconfig display so can't really use that anymore Paul Confidentiality Notice: The information contained in this email is intended for the confidential use of the above-named recipient(s). If the reader of this message is not the intended recipient or person responsible for delivering it to the intended recipient, you are hereby notified that you have received this communication in error, and that any review, dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this in error, please notify the sender immediately and destroy this message. Data Classification: Limited Access -----Original Message----- From: Linux on 390 Port [mailto:[email protected]] On Behalf Of Marcy Cortes Sent: Tuesday, March 29, 2011 1:39 PM To: [email protected] Subject: Re: VLAN tagging and Channel Bonding with Linux Bingo! Thank you Paul! The .xxx way on the bond device works! The other way with ifcfg-vlanxxx doesn't seem to. So I'm good! Marcy This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -----Original Message----- From: Linux on 390 Port [mailto:[email protected]] On Behalf Of Ayer, Paul W Sent: Tuesday, March 29, 2011 9:49 AM To: [email protected] Subject: Re: [LINUX-390] VLAN tagging and Channel Bonding with Linux We have both in place. What we do is create ifcfg-eth0 and ifcfg-eth1 and ifcfg-bond0 like normal .. Do not put the ip info in them... Then create a ifcfg-bond0.xxx (xxx = the vlan tag .. like 32 or 155 or 88 .. whatever) Also found that you will want to remove gateway= from /etc/sysconfig/network Here is a Red Hat sample... ========================================================================================= -------------------------------------------- /etc/sysconfig/network-scripts ifcfg-bond0 ------------------------------------------- DEVICE=bond0 TYPE=Bonding ONBOOT=yes --------------- /etc/sysconfig/network-scripts ifcfg-eth0 --------------- DEVICE=eth0 NETTYPE=qeth SUBCHANNELS=0.0.0900,0.0.0901,0.0.0902 PORTNAME=eth0 TYPE=Ethernet OPTIONS=layer2=1 SLAVE=yes MASTER=bond0 --------------- /etc/sysconfig/network-scripts ifcfg-eth1 --------------- DEVICE=eth1 NETTYPE=qeth SUBCHANNELS=0.0.0903,0.0.0904,0.0.0905 PORTNAME=eth0 TYPE=Ethernet OPTIONS=layer2=1 SLAVE=yes MASTER=bond0 -------------------------------------------------- /etc/sysconfig/network-scripts/ifcfg-bond0.32 -------------------------------------------------- DEVICE=bond0.32 BOOTPROTO=static ONBOOT=yes IPADDR=10.48.32.24 USERCTL=no NETMASK=255.255.255.0 VLAN=yes VSWITCH=1 NETWORK=10.48.32.0 GATEWAY=10.48.32.250 ----------------------- /etc/modprobe.conf ----------------------- options dasd_mod dasd=291 alias net-pf-10 off alias ipv6 off alias eth0 qeth alias eth1 qeth alias bond0 bonding options bonding mode=2 arp_interval=1000 arp_ip_target=10.48.32.250 # options bonding mode=0 arp_interval=1000 arp_ip_target=10.48.32.250 Paul Confidentiality Notice: The information contained in this email is intended for the confidential use of the above-named recipient(s). If the reader of this message is not the intended recipient or person responsible for delivering it to the intended recipient, you are hereby notified that you have received this communication in error, and that any review, dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this in error, please notify the sender immediately and destroy this message. Data Classification: Limited Access -----Original Message----- From: Linux on 390 Port [mailto:[email protected]] On Behalf Of Mark Post Sent: Tuesday, March 29, 2011 12:20 PM To: [email protected] Subject: Re: VLAN tagging and Channel Bonding with Linux >>> On 3/29/2011 at 12:01 PM, Marcy Cortes <[email protected]> >>> wrote: > I have vlan tagging working > And channel bonding working. > But I need to make them both work together. > > Do you tag each of the interfaces or tag the bond device? Without actually researching this, my first reaction would be to tag the bond interface. Mark Post ---------------------------------------------------------------------- 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 more information on Linux on System z, visit http://wiki.linuxvm.org/ ---------------------------------------------------------------------- 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 more information on Linux on System z, visit http://wiki.linuxvm.org/ ---------------------------------------------------------------------- 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 more information on Linux on System z, visit http://wiki.linuxvm.org/ ---------------------------------------------------------------------- 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 more information on Linux on System z, visit http://wiki.linuxvm.org/ ---------------------------------------------------------------------- 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 more information on Linux on System z, visit http://wiki.linuxvm.org/
