There have been fixes for VLAN interfaces on top of bonding interfaces with active-backup mode and fail_over_mac=1. For RHEL6 for instance I remember there exists RH1159818/1115606- "Bonding mode active-backup and fail_over_mac active for Vlan interface Propagate MAC address is not working"
Make sure you run an up-to-date kernel. Regards, Ursula Braun, IBM Germany On 03/07/2017 11:30 PM, Marcy Cortes wrote: > Hi, > > I have vlan tagged channel bonded interfaces on xDR proxies. Maybe it > will help just to show you. > In my case VLAN number is 71 and the IP address used here is 162.101.1.129. > You need to make up unique LLADDR's. Generally i think it's start them with > 02:00:00 to indicate user made up (Alan can correct me there if I > misremembered that :) > > rename off your vswitch configs so in case you need to get back its easy :) > > > xdr91:/etc/sysconfig/network # cat ifcfg-bond0 > BOOTPROTO='static' > STARTMODE='onboot' > BONDING_MASTER='yes' > BONDING_MODULE_OPTS='mode=active-backup fail_over_mac=active miimon=100' > BONDING_SLAVE0='eth0' > BONDING_SLAVE1='eth1' > > > xdr91:/etc/sysconfig/network # cat ifcfg-vlan71 > ETHERDEVICE='bond0' > IPADDR='162.101.1.129' > NETMASK='255.255.255.0' > NAME='VLAN access' > NETWORK='162.101.1.0' > BROADCAST='162.101.1.255' > STARTMODE='onboot' > VLAN='YES' > > > xdr91:/etc/sysconfig/network # cat ifcfg-eth0 > BOOTPROTO='static' > IPADDR='' > BROADCAST='' > STARTMODE='auto' > LLADDR='' > NAME='OSA Express Network card (0.0.3000)' > ETHTOOL_OPTIONS='' > MTU='' > NETWORK='' > REMOTE_IPADDR='' > USERCONTROL='no' > SLAVE='yes' > LLADDR='02:00:00:00:91:EF' > > > xdr91:/etc/sysconfig/network # cat ifcfg-eth1 > BOOTPROTO='static' > IPADDR='' > BROADCAST='' > STARTMODE='auto' > LLADDR='' > NAME='OSA Express Network card (0.0.4000)' > ETHTOOL_OPTIONS='' > MTU='' > NETWORK='' > REMOTE_IPADDR='' > USERCONTROL='no' > SLAVE='yes' > LLADDR='02:00:00:00:91:EE' > > xdr91:/etc/sysconfig/network # cat routes > default 162.101.1.1 - - > > > The bonding and 8021q modules seem to have loaded themselves - I couldn’t > find anything specific to them in /etc/modprobe.d > > Marcy > > -----Original Message----- > From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Bill > Head > Sent: Tuesday, March 07, 2017 2:07 PM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: [LINUX-390] DEDICATED OSA, LINUX VLAN tagging and bonding > > And Alan is correct about VLAN tagging in LINUX (much easier to configure > VSWITCH's, eeeewww), not to mention trying to do it with bonding two > dedicated OSA's. I opened up a ticket with SuSE for some guidance on that. > I may have to trudge on with just a VSWITCH connection until I get that > figured out, at least I can get all the proxy guests built, get DNS changes > in, etc. GDPS is a different animal, miles to go before I sleep..... > > > > -----Original Message----- > From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Alan > Altmark > Sent: Tuesday, March 07, 2017 4:26 PM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: DEDICATED OSA, LINUX VLAN tagging and bonding > > The VSWITCH depends on the controller virtual machines. It and some related > CP control blocks may be swapped out. > > In a hyperswap, you can't do I/O to bring them back in. > > Bill is correct regarding the requirements for the GDPS proxy servers. > > Regards, > Alan > > > > The information transmitted is intended only for the person or entity to > which it is addressed and may contain CONFIDENTIAL material. If you receive > this material/information in error, please contact the sender and delete or > destroy the material/information. > ---------------------------------------------------------------------- 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/
