I'm still using eth0 using a vswitch so I can putty in and make changes. I
created the ifcfg-eth1, ifcfg-eth2, ifcfg-bond0, and ifcfg-vlan10. Made
changes to bond0 to make eth1 and eth2 slaves. When I boot it looks like it
can't find eth1 and eth2. Any ideas?
..doneWaiting for mandatory devices: eth1 eth2
18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
bonding: Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)
bonding: bond0 is being created...
bonding: bond0: setting mode to active-backup (1).
bonding: bond0: Setting fail_over_mac to active (1).
bonding: bond0: Setting MII monitoring interval to 100.
eth1 No interface found
..failed eth2 No interface found
..failed bond0
bond0 skipping interface: eth1 (missed)
bond0 skipping interface: eth2 (missed)
Removing bonding interface 'bond0'
bond0
Mar 9 11:11:09 lxgonep1 ifup-bonding: Removing bonding interface 'bond0'
ADDRCONF(NETDEV_UP): bond0: link is not ready
bonding: bond0 is being deleted...
..done vlan10 name: VLAN access
Cannot find device "bond0"
interface 'bond0' is not up
Mar 9 11:11:10 lxgonep1 ifup-802.1q: interface 'bond0' is not up
..doneSetting up service (localfs) network . . . . . . . . . ...faile
-----Original Message-----
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Marcy
Cortes
Sent: Tuesday, March 07, 2017 6:44 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: DEDICATED OSA, LINUX VLAN tagging and bonding
Yea, i didn't include the VLAN in the presentation. You'd only need it if you
didn't have a default vlan that worked for that interface with that IP.
You're welcome and good luck!
-----Original Message-----
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Bill Head
Sent: Tuesday, March 07, 2017 3:31 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: [LINUX-390] DEDICATED OSA, LINUX VLAN tagging and bonding
Yep, that's what I need. I didn't see where you had examples of VLAN tagging
in your presentation, also didn't want to keep bugging you about this. I
really do appreciate the help!
FYI: you are right about not having to specify the module, support got back to
me and said it was included in the kernel and no longer necessary. Got my
hands on dated "how to" links on the interweb.
Many thanks!
-----Original Message-----
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Marcy
Cortes
Sent: Tuesday, March 07, 2017 5:30 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: DEDICATED OSA, LINUX VLAN tagging and bonding
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.
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.
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.
