New publication: Linux Channel Bonding Best Practices and Recommendations

Linux on Z and LinuxONE Linux Channel Bonding Best Practices and Recommendations A new white paper describes channel bonding configurations on different Linux distributions on IBM Z and explains the recommended options for the Linux bonding driver. See: IBM Knowledge Center https

Re: [IBMVM] Linux on Z, RHEL 7.2 Bonding Problem

Hi Alan, I thanked you in the earlier email but since it was in "Rich Text" format, may not have reached you. What can I say, you are the best! I did 802.3ad and worked like a charm! Wish you all great weekend! Warm Regards, Tom On 04/13/17, Alan Altmarkcom> wrote: On Wednesday,

Re: [IBMVM] Linux on Z, RHEL 7.2 Bonding Problem

On Wednesday, 04/12/2017 at 10:38 GMT, canzon...@verizon.net wrote: > Hi Mark, > Thank you. I want both slaves active at the same time. The testing is done dropping link2 so that > the link2 pick it up. And, when that link1 is bought up and drop link2. > > I would appreciate if you can give

Re: DEDICATED OSA, LINUX VLAN tagging and bonding

>>> On 3/6/2017 at 11:24 PM, Bill Head <bh...@humana.com> wrote: > Howdy folks, > > Up until now I've been using VSWITCHes for new SuSE guests (SLES 11 SP4). > I'm in the process of trying to build out a guest with two dedicated OSA > adapters, set up VLA

Re: DEDICATED OSA, LINUX VLAN tagging and bonding

D='10' Now when I remove eth0 and not sure if I will break the bonding, if the eth addresses change, we shall see. -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Marcy Cortes Sent: Thursday, March 09, 2017 1:56 PM To: LINUX-390@VM.MARI

Re: DEDICATED OSA, LINUX VLAN tagging and bonding

UX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] DEDICATED OSA, LINUX VLAN tagging and bonding Yep, found that in the meantime. I did this for both eth1 and eth2 qeth_configure -l -t qeth 0.0.1000 0.0.1001 0.0.1002# DEDICATE device to 1000, 1001, and 1002 qeth_configure -l -t qeth 0.0.2001 0.0.2001 0.

Re: DEDICATED OSA, LINUX VLAN tagging and bonding

, 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 > bon

Re: DEDICATED OSA, LINUX VLAN tagging and bonding

bond0 8021q: adding VLAN 0 to HW filter on device bond0 bonding: bond0: Removing slave eth1. bonding: bond0: releasing active interface eth1 bonding: bond0: making interface eth2 the new acti

Re: DEDICATED OSA, LINUX VLAN tagging and bonding

UX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] DEDICATED OSA, LINUX VLAN tagging and bonding 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

Re: DEDICATED OSA, LINUX VLAN tagging and bonding

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

Re: DEDICATED OSA, LINUX VLAN tagging and bonding

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 wo

Re: DEDICATED OSA, LINUX VLAN tagging and bonding

: 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

Re: DEDICATED OSA, LINUX VLAN tagging and bonding

DU 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

Re: DEDICATED OSA, LINUX VLAN tagging and bonding

-390] DEDICATED OSA, LINUX VLAN tagging and bonding --- From:"Scott Rohling" <scott.rohl...@gmail.com>To:LINUX-390@VM.MARIST.EDUDate:Tue, Mar 7, 2017 12:34 PMSubject:Re: [LINUX-390] DEDICATED OSA, LINUX VLAN tagging and bonding Are you sure you are interpreting the requi

Re: DEDICATED OSA, LINUX VLAN tagging and bonding

--Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Alan Altmark Sent: Tuesday, March 07, 2017 1:37 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: DEDICATED OSA, LINUX VLAN tagging and bonding On Tuesday, 03/07/2017 at 06:18 GMT, "Vitale, Josep

Re: DEDICATED OSA, LINUX VLAN tagging and bonding

Dedicated network interfaces and channel bonding for Proxy Guests Loss of communications between the Master Controlling system and a master proxy node during a HyperSwap could result in the failure of the z/VM system to complete the swap. In this case, GDPS would reset the z/VM system. Also

Re: DEDICATED OSA, LINUX VLAN tagging and bonding

GDPS/xDR is that you do not > use virtual switches (since everything gets quiesed during a hyperswap). > So in order to setup DEDICATED OSA adapters I think I'm forced to use VLAN > tagging in LINUX. They also recommend using bonding. Which goes back to > my original question. Whe

Re: DEDICATED OSA, LINUX VLAN tagging and bonding

One requirement with building proxy guests for GDPS/xDR is that you do not use virtual switches (since everything gets quiesed during a hyperswap). So in order to setup DEDICATED OSA adapters I think I'm forced to use VLAN tagging in LINUX. They also recommend using bonding. Which goes

Re: DEDICATED OSA, LINUX VLAN tagging and bonding

On Tuesday, 03/07/2017 at 06:18 GMT, "Vitale, Joseph" wrote: > Hello, > > Interested to know if VLAN Tagging can be done via zLinux if zVM currently adding VLAN Tag. OSA > set up for Port access. Using Red Hat 7. Please see below: > > CP SET VSWITCH VSWITCH2

Re: DEDICATED OSA, LINUX VLAN tagging and bonding

tagging and bonding Howdy folks, Up until now I've been using VSWITCHes for new SuSE guests (SLES 11 SP4). I'm in the process of trying to build out a guest with two dedicated OSA adapters, set up VLAN tagging and bonding in LINUX. The z/VM LPAR default vlan is 3 VSWITCH setup for the GOLD image

DEDICATED OSA, LINUX VLAN tagging and bonding

Howdy folks, Up until now I've been using VSWITCHes for new SuSE guests (SLES 11 SP4). I'm in the process of trying to build out a guest with two dedicated OSA adapters, set up VLAN tagging and bonding in LINUX. The z/VM LPAR default vlan is 3 VSWITCH setup for the GOLD image is VLAN 14

Re: SLES 12.1 Bonding

This kind of old but still accurate as far as I can tell (we have bonding on SLES 11 but I haven't tried it on 12 yet). https://www.google.com/url?sa=t=j==s=web=4=0ahUKEwiBg6PRjJvSAhWJ2yYKHclKCAAQFggvMAM=https%3A%2F%2Fshare.confex.com%2Fshare%2F120%2Fwebprogram%2FHandout%2FSession12374%2FLinux

Re: SLES 12.1 Bonding

17 at 09:49 AM, <canzon...@verizon.net> wrote: > Hi, > I'm having such a difficult time configuring network setup using Yast2. > Currently the daunting task is Setting up Bonding Devices. I follow the > documentation > "https://www.suse.com/documentation/sles-12/book

Re: SLES 12.1 Bonding

>>> On 2/18/2017 at 09:49 AM, <canzon...@verizon.net> wrote: > Hi, > I'm having such a difficult time configuring network setup using Yast2. > Currently the daunting task is Setting up Bonding Devices. I follow the > documentation > "https://www.suse.com/d

SLES 12.1 Bonding

Hi, I'm having such a difficult time configuring network setup using Yast2. Currently the daunting task is Setting up Bonding Devices. I follow the documentation "https://www.suse.com/documentation/sles-12/book_sle_admin/data/sec_bond.html; but not getting anywhere. And when tried to add

VLAN tagging and Channel Bonding with Linux

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? (and no, don't say use a vswitch - believe me - I'd love to, but not allowed for this !) Marcy This message may contain

Re: VLAN tagging and Channel Bonding with Linux

are applied to the bonding interface. (Google vlan channel bonding.) Be sure that the only VLANs authorized on the trunk are those needed by Linux, as there are no controls in the OSA firmware to restrict VLAN usage. And if necessary, turn off Ip forwarding. Alan Altmark z/VM and Linux on System z

Re: VLAN tagging and Channel Bonding with Linux

/network Here is a Red Hat sample... = /etc/sysconfig/network-scripts ifcfg-bond0 --- DEVICE=bond0 TYPE=Bonding ONBOOT=yes

Re: VLAN tagging and Channel Bonding with Linux

on 390 Port [mailto:LINUX-390@vm.marist.edu] On Behalf Of Alan Altmark Sent: Tuesday, March 29, 2011 9:23 AM To: LINUX-390@vm.marist.edu Subject: Re: [LINUX-390] VLAN tagging and Channel Bonding with Linux On Tuesday, 03/29/2011 at 12:07 EDT, Marcy Cortes marcy.d.cor...@wellsfargo.com wrote

Re: VLAN tagging and Channel Bonding with Linux

On 3/29/2011 at 12:01 PM, Marcy Cortes marcy.d.cor...@wellsfargo.com 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

Re: VLAN tagging and Channel Bonding with Linux

Port [mailto:LINUX-390@vm.marist.edu] On Behalf Of Ayer, Paul W Sent: Tuesday, March 29, 2011 9:49 AM To: LINUX-390@vm.marist.edu 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

Re: VLAN tagging and Channel Bonding with Linux

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

Re: VLAN tagging and Channel Bonding with Linux

On Tuesday, 03/29/2011 at 01:24 EDT, Marcy Cortes marcy.d.cor...@wellsfargo.com wrote: Well, harrumph indeed. Would be nice if hyperswapping didn't require a non-vswitch'd Linux! That's kind of odd. If the VSWITCH controllers have locked memory I don't know why a VSWITCH wouldn't work. Oh,

Re: VLAN tagging and Channel Bonding with Linux

-390@vm.marist.edu Subject: Re: [LINUX-390] VLAN tagging and Channel Bonding with Linux On Tuesday, 03/29/2011 at 01:24 EDT, Marcy Cortes marcy.d.cor...@wellsfargo.com wrote: Well, harrumph indeed. Would be nice if hyperswapping didn't require a non-vswitch'd Linux! That's kind of odd

Re: VLAN tagging and Channel Bonding with Linux

11:34 AM To: LINUX-390@vm.marist.edu 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

Re: VLAN tagging and Channel Bonding with Linux

On Tuesday, 03/29/2011 at 11:09 EDT, Marcy Cortes marcy.d.cor...@wellsfargo.com wrote: Alan wrote: That's kind of odd. If the VSWITCH controllers have locked memory I don't know why a VSWITCH wouldn't work. Well, I think you know more people that I do that can fix that problem, huh :) Maybe,

Re: VLAN tagging and Channel Bonding with Linux

a dedicated address in the OSA adapter for the proxy guest to allow TCP/IP communication independent from the VM TCP/IP machine. And no one uses only one OSA if you really care about SPOF... right? So channel bonding... and no default vlan provided by the network guys now ... so vlan tagging

Defining channel bonding of OSA adapters with Yast

connection to a particular network. All of a sudden it seemed to be a good idea to figure out how to do channel bonding. Spending a little time with Google, I found a SHARE presentation (Networking with Linux on System Z) that gave me a setup. The setup had you issue several commands

Re: Defining channel bonding of OSA adapters with Yast

channel bonding of OSA adapters with Yast Hello listers, We had an OSA adapter go out the other night on our z10. Our linux guests running under z/VM did not have any problems when this OSA adapter went out. The vswitches they were attached to had multiple adapters defined to them. The vswitch just

Re: channel bonding using 2 Vswitches

and for some reason it was dropped to we will review that one again too. Paul -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Harder, Pieter Sent: Wednesday, May 13, 2009 2:48 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: channel bonding using 2 Vswitches 1

Re: channel bonding using 2 Vswitches

Hi Paul, So we'll keep checking and also thanks for the VSS info we had looked at that in the past and for some reason it was dropped to we will review that one again too. One pitfall to think about I ran into with VSS the hard way is that VSS operates according to the 'same box' principle.

Re: channel bonding using 2 Vswitches

, Paul -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Harder, Pieter Sent: Wednesday, May 13, 2009 2:48 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: channel bonding using 2 Vswitches 1. We found that when you add OSAs to a Vswitch and setup link

channel bonding using 2 Vswitches

Has anyone setup Channel Bonding using NICs from two Vswiches in Layer 2 mode? We do not have this running yet but are starting to test ... There are a couple of reason for this; 1. We found that when you add OSAs to a Vswitch and setup link aggregation that the OSAs is used only

Re: channel bonding using 2 Vswitches

) as VSWITCH has no port channeling other than to real OSA's. You can define two VNICs on one guest to the same VSWITCH and put Linux bonding to them, but only one VNIC will be used. The other one is useless and does not even have a role as failover as the first one can have no hardware failure

Re: bonding multiple qeth vnics to vswitch?

This presentation, given at the SHARE Orlando meeting last February, might be of interest: Networking with Linux(r) on System z, session 9267, given by Steffen Thoss (th...@de.ibm.com). He discusses network bonding of multiple NICs in some detail, and gives example configurations for SLES 10

Re: bonding multiple qeth vnics to vswitch?

You're certainly correct, Pieterthe presentation shows channel bonding between two NICs and two real OSA adapters. VSWITCH and/or gLANs aren't covered at all. Harder, Pieter wrote: This presentation, given at the SHARE Orlando meeting last February, might be of interest: Networking

Re: bonding multiple qeth vnics to vswitch?

On 1/25/2009 at 7:47 AM, Harder, Pieter pieter.har...@brabantwater.nl wrote: -snip- Also the current level of the bonding driver precludes real balancing of outgoing data over the nics. This part I don't agree with. One trap I almost fell into was just looking at the raw numbers

Re: bonding multiple qeth vnics to vswitch?

Also the current level of the bonding driver precludes real balancing of outgoing data over the nics. This part I don't agree with. One trap I almost fell into was just looking at the raw numbers of bytes transmitted for each interface. Then I realized that a fair amount of traffic flows

Re: bonding multiple qeth vnics to vswitch?

On Friday, 01/23/2009 at 05:53 EST, Mark Post mp...@novell.com wrote: s390a13:~ # ifconfig bond0 Link encap:Ethernet HWaddr 02:00:00:00:00:06 eth1 Link encap:Ethernet HWaddr 02:00:00:00:00:06 eth2 Link encap:Ethernet HWaddr 02:00:00:00:00:06 Adapter 0800 Type: QDIO

Re: bonding multiple qeth vnics to vswitch?

This presentation, given at the SHARE Orlando meeting last February, might be of interest: Networking with Linux® on System z, session 9267, given by Steffen Thoss (th...@de.ibm.com). He discusses network bonding of multiple NICs in some detail, and gives example configurations for SLES 10

Re: bonding multiple qeth vnics to vswitch?

MAC address. Alan, can you comment on what may have happened to the test Mark ran with bonding mode 2? Would it really behave like bonding mode 1? It sounded like it worked (well, gave no errors in setting up), but do you expect it to accomplish something usefull? But even if it did, you're

Re: bonding multiple qeth vnics to vswitch?

dramatic pauses (lots of folks get paged). Our next step is VSS in the cisco switch to eliminate switch failures from causing the pause and the switch to the 1 (backup) interface. We explored using channel bonding briefly to have a guest's traffic over 2 interfaces. We are using channel bonding

Re: bonding multiple qeth vnics to vswitch?

On 1/22/2009 at 6:09 PM, Harder, Pieter pieter.har...@brabantwater.nl wrote: -snip- That is strange. Mode 1 is active-backup, where by definition only one nic is active. That was a typo on my part. I meant I tried both mode 0 and mode 2. Again, the results were outgoing traffic was

Re: bonding multiple qeth vnics to vswitch?

On 1/22/2009 at 6:51 PM, Alan Altmark alan_altm...@us.ibm.com wrote: -snip- While you can have multiple vNICs on an aggregating VSWITCH, there's nothing that will spray/deal queued frames across the vNICs since they each have a unique MAC address. When the bonded NIC starts up, both of the

Re: bonding multiple qeth vnics to vswitch?

] bonding multiple qeth vnics to vswitch? On 1/22/2009 at 6:51 PM, Alan Altmark alan_altm...@us.ibm.com wrote: -snip- While you can have multiple vNICs on an aggregating VSWITCH, there's nothing that will spray/deal queued frames across the vNICs since they each have a unique MAC address. When

Re: bonding multiple qeth vnics to vswitch?

On 1/23/2009 at 10:59 AM, Marcy Cortes marcy.d.cor...@wellsfargo.com wrote: Right, And not sure if it would help Pieter's problem anyway: It didn't seem to, no. -snip- Given the counts, it seems to greatly favor one over the other (this one is sles 10 sp2) That looks more like mode 1

Re: bonding multiple qeth vnics to vswitch?

: bonding multiple qeth vnics to vswitch? Right, And not sure if it would help Pieter's problem anyway: # ifconfig bond0 Link encap:Ethernet HWaddr 02:00:00:00:00:41 inet addr:10.93.27.250 Bcast:10.93.27.255 Mask:255.255.255.0 inet6 addr: fe80::ff:fe00:41/64 Scope:Link

Re: bonding multiple qeth vnics to vswitch?

Oh, you are right! (as usual :) # cat /proc/net/bonding/bond0 Ethernet Channel Bonding Driver: v3.0.3 (March 23, 2006) Bonding Mode: fault-tolerance (active-backup) Primary Slave: None Currently Active Slave: eth0 MII Status: up MII Polling Interval (ms): 1 Up Delay (ms): 0 Down Delay (ms): 0

Re: bonding multiple qeth vnics to vswitch?

On 1/23/2009 at 11:32 AM, Marcy Cortes marcy.d.cor...@wellsfargo.com wrote: -snip- Now... To figure out how to try the balanced mode. I put options bonding mode=? in /etc/modprobe.conf.local for my testing. Be careful, though. Some of the examples I ran across on the 'net showed

Re: bonding multiple qeth vnics to vswitch?

- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Mark Post Sent: Friday, January 23, 2009 9:04 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] bonding multiple qeth vnics to vswitch? On 1/23/2009 at 11:32 AM, Marcy Cortes marcy.d.cor...@wellsfargo.com wrote: -snip

Re: bonding multiple qeth vnics to vswitch?

On Friday, 01/23/2009 at 10:54 EST, Mark Post mp...@novell.com wrote: On 1/22/2009 at 6:51 PM, Alan Altmark alan_altm...@us.ibm.com wrote: -snip- While you can have multiple vNICs on an aggregating VSWITCH, there's nothing that will spray/deal queued frames across the vNICs since they

Re: bonding multiple qeth vnics to vswitch?

On 1/23/2009 at 1:24 PM, Alan Altmark alan_altm...@us.ibm.com wrote: On Friday, 01/23/2009 at 10:54 EST, Mark Post mp...@novell.com wrote: -snip- When the bonded NIC starts up, both of the slave's MAC addresses are set to be the same. So, they're not unique. Then this must be a Layer 3

Re: bonding multiple qeth vnics to vswitch?

On Friday, 01/23/2009 at 01:30 EST, Mark Post mp...@novell.com wrote: Then this must be a Layer 3 VSWITCH where we don't care about or use guest MACs. A Layer 2 VSWITCH (required for LACP) enforces unique MACs. Nope, it's Layer 2. If I tried to use a Layer 3, it didn't work. (It would

Re: bonding multiple qeth vnics to vswitch?

A mystery indeed. As Pieter suggested, seeing the output of QUERY NIC DETAILS would be edifying. Here is the answer on my system: TSMSERV:~ # vmcp q nic details Adapter 0C00.P00 Type: QDIO Name: 0 Devices: 3 MAC: 02-00-00-02-03-96 VSWITCH: SYSTEM QDIOL RX Packets:

Re: bonding multiple qeth vnics to vswitch?

On 1/23/2009 at 1:58 PM, Alan Altmark alan_altm...@us.ibm.com wrote: -snip- A mystery indeed. As Pieter suggested, seeing the output of QUERY NIC DETAILS would be edifying. s390a13:~ # ifconfig bond0 Link encap:Ethernet HWaddr 02:00:00:00:00:06 inet addr:10.10.220.13

bonding multiple qeth vnics to vswitch?

Hello list, I have been reading in 'Networking with Linux on System z' from Share in last August (see http://linuxvm.org/Present/SHARE111/S9267kw.pdf) and I see something that is confusing me. In the part about qeth bonding on page 33 it says 'Add MAC address to eth0 eth1 (not necessary

Re: bonding multiple qeth vnics to vswitch?

qeth bonding on page 33 it says 'Add MAC address to eth0 eth1 (not necessary for GuestLAN or Vswitch)' which suggest that bonding is also possible for multiple VNICs connected to a VSWITCH. From the documentation about VSWITCH LACP I get the impression this is not possible. Is this a slip

Re: bonding multiple qeth vnics to vswitch?

why would you want to channel bond two vnics going to the SAME vswitch? Chances of a software vnic failure are pretty remote, and may affect all vnics anyway. I can see bonding two vnics coupled to two vswitches. David Kreuter From: Linux on 390 Port on behalf

Re: bonding multiple qeth vnics to vswitch?

Hello list, I have been reading in 'Networking with Linux on System z' from Share in last August (see http://linuxvm.org/Present/SHARE111/S9267kw.pdf) and I see something that is confusing me. In the part about qeth bonding on page 33 it says 'Add MAC address to eth0 eth1 (not necessary

Re: bonding multiple qeth vnics to vswitch?

We asked about that to IBM via PMR. The answer is no - you cannot do nic bonding with the vswitch NIC. So I think the presentation is a little misleading on that page. Marcy Cortes Team Lead, Enterprise Virtualization - z/VM and z/Linux Enterprise Hosting Services w. (415) 243-6343 c. (415

Re: bonding multiple qeth vnics to vswitch?

why would you want to channel bond two vnics going to the SAME vswitch? Chances of a software vnic failure are pretty remote, and may affect all vnics anyway. I can see bonding two vnics coupled to two vswitches. To me it is not a failover issue, but a capacity issue. Eg. with two vnics you

Re: bonding multiple qeth vnics to vswitch?

On Thu, Jan 22, 2009 at 10:26 PM, Harder, Pieter pieter.har...@brabantwater.nl wrote: To me it is not a failover issue, but a capacity issue. Eg. with two vnics you can get past the 128-buffer limit on a qeth interface by having two sets of them. To clarify, the issue that Pieter and myself

Re: bonding multiple qeth vnics to vswitch?

On 1/22/2009 at 4:21 PM, Marcy Cortes marcy.d.cor...@wellsfargo.com wrote: We asked about that to IBM via PMR. The answer is no - you cannot do nic bonding with the vswitch NIC. So I think the presentation is a little misleading on that page. Hmm. That's weird. I just set up one

Re: bonding multiple qeth vnics to vswitch?

- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Mark Post Sent: Thursday, January 22, 2009 1:45 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] bonding multiple qeth vnics to vswitch? On 1/22/2009 at 4:21 PM, Marcy Cortes marcy.d.cor...@wellsfargo.com wrote: We asked

Re: bonding multiple qeth vnics to vswitch?

On 1/22/2009 at 4:21 PM, Marcy Cortes marcy.d.cor...@wellsfargo.com wrote: We asked about that to IBM via PMR. The answer is no - you cannot do nic bonding with the vswitch NIC. So I think the presentation is a little misleading on that page. Hmm. That's weird. I just set up one

Re: bonding multiple qeth vnics to vswitch?

On 1/22/2009 at 4:21 PM, Marcy Cortes marcy.d.cor...@wellsfargo.com wrote: We asked about that to IBM via PMR. The answer is no - you cannot do nic bonding with the vswitch NIC. So I think the presentation is a little misleading on that page. I guess I should add that I did

Re: bonding multiple qeth vnics to vswitch?

None - we asked before we tried. Got a no and so didn't do it. That's OK though - LACP vswitch was a better way to go and we've since implemented that. Marcy, You just lost me. LACP is on the trunk side of the VSWITCH. I am talking bonding on the port side of it. What exactly did you think

Re: bonding multiple qeth vnics to vswitch?

I guess I should add that I did it with a Layer 2 VSWITCH, not Layer 3. Since the bonding module wants to modify the MAC address of the two slave NICs, you get nastygrams if you try it with Layer 3. Mark, From the bonding HOWTO guide: 7. Which switches/systems does it work

Re: bonding multiple qeth vnics to vswitch?

On 1/22/2009 at 5:08 PM, Harder, Pieter pieter.har...@brabantwater.nl wrote: -snip- Where is the etherchannel defined in you VSWITCH? No clue. It's not my z/VM system. I'm just a user. Mark Post -- For LINUX-390

Re: bonding multiple qeth vnics to vswitch?

On 1/22/2009 at 5:00 PM, Harder, Pieter pieter.har...@brabantwater.nl wrote: -snip- Mark, What mode did you set it up with? And do you actually see incoming data on both eth0 and eth1? If it is only outgoing data you are bonding it will not help me as Rob pointed out. My problem

Re: bonding multiple qeth vnics to vswitch?

Mark, What mode did you set it up with? And do you actually see incoming data on both eth0 and eth1? If it is only outgoing data you are bonding it will not help me as Rob pointed out. My problem is with incoming. The 'Linux Ethernet Bonding Driver HOWTO' on sourceforge suggests you need

Re: bonding multiple qeth vnics to vswitch?

On Thursday, 01/22/2009 at 05:05 EST, Harder, Pieter pieter.har...@brabantwater.nl wrote: You just lost me. LACP is on the trunk side of the VSWITCH. I am talking bonding on the port side of it. What exactly did you think of doing that was solved by LACP? Talk about a confusing conversation

Re: channel bonding

on being on a z9 ). That's just a normal multihomed configuration. Each interface has a separate IP address assigned. Channel bonding applies a single IP address to multiple physical interfaces, multiplexing packets using a well-defined protocol (LACP). Alan Altmark z/VM Development IBM Endicott

Re: channel bonding

Hi Mike, Thanks for the input. But still if in a Vswitch only one OSA is really working at time into the network then channel bonding is of no use. Either go with no Vswitch and use two real OSA's, or two Vswitches with a live OSA in each would be needed it seems to me... Paul

Re: channel bonding

On Tue, Sep 18, 2007 at 3:33 PM, in message [EMAIL PROTECTED], Ayer, Paul W [EMAIL PROTECTED] wrote: -snip- But it dawns on me that channel bonding and Vswitch (the way we have them) really don't go together. The most common use of NIC bonding is for reliability purposes, not bandwidth

Re: channel bonding

On Wednesday, 09/19/2007 at 09:16 EDT, Ayer, Paul W [EMAIL PROTECTED] wrote: Thanks for the input. But still if in a Vswitch only one OSA is really working at time into the network then channel bonding is of no use. Either go with no Vswitch and use two real OSA's, or two Vswitches

Re: channel bonding

Sent: Wednesday, September 19, 2007 10:25 AM To: LINUX-390@vm.marist.edu Subject: Re: channel bonding On Wednesday, 09/19/2007 at 09:16 EDT, Ayer, Paul W [EMAIL PROTECTED] wrote: Thanks for the input. But still if in a Vswitch only one OSA is really working at time into the network then channel

Re: channel bonding

On Wednesday, 09/19/2007 at 10:47 EDT, Ayer, Paul W [EMAIL PROTECTED] wrote: At this time in Vswitch only one OSA is really active and passing data. With (IEEE 802.3ad Link Aggregation) both OSA's would be moving data? With a z9 and z/VM 5.3, yes, you can have up to 8 OSAs moving data

Re: channel bonding

Hi Alan, Thank you .. just what we needed. Have a great day ! -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Alan Altmark Sent: Wednesday, September 19, 2007 10:59 AM To: LINUX-390@vm.marist.edu Subject: Re: channel bonding On Wednesday, 09/19/2007

Re: channel bonding

I don't think you can define two Vswitches that use the same range of IP addresses. You can. I've done that. And I even recently discovered they can be of different type (layer 2 and layer 3) (but that might depend on being on a z9 ). Marcy Cortes This message may contain confidential

channel bonding

Good afternoon all, Have been having good success getting channel bonding going. We also have Vswitch as well. But it dawns on me that channel bonding and Vswitch (the way we have them) really don't go together. In Vswitch we have two OSA's one active and one backup. If in VM we setup two

Re: channel bonding

I guess it depends if those virtual interfaces are going to different VLANs. If your network team is using VLAN tagging, then each of those virtuals could travel different networks (perhaps to a DR site?). Doesn't help much for *real* interface bonding, but that's one use for it. Mike

Re: Bonding

with bonding? qethbonding? As others have said, link bonding isn't what you want to do here unless you are trying to aggregate bandwidth; if I understand you correctly, you want to do IP or MAC address takeover for HA. If so, then you should look at the packages in openssi.org wrt to the cluster IP

Bonding

Hi All, Recently, I have tried to do network teaming for two network cards to perform as one network for HA purpose. I found that SLES 8 includes bonding drivers. It works fine for SLES 8 on Intel. However, I encountered problem with SLES 8 on S390. Has anyone tried using bonding on SLES 8

Re: Bonding

Johnny Tan wrote: Hi All, Recently, I have tried to do network teaming for two network cards to perform as one network for HA purpose. I found that SLES 8 includes bonding drivers. It works fine for SLES 8 on Intel. However, I encountered problem with SLES 8 on S390. Has anyone tried using

Re: Bonding

I found that SLES 8 includes bonding drivers. It works fine for SLES 8 on Intel. However, I encountered problem with SLES 8 on S390. Has anyone tried using bonding on SLES 8 (SP4) on S390 platform? Haven't tried it, but unless you're running very recent network drivers (later than SLES8

Re: Bonding

Hi David, I am using SLES 8 SP4. OSA is attached to z/VM 4.4 and z/VM assigned three device numbers to linux guest to form on NIC. If there is qetharp for ARP equivalent on zLinux, is there any other network teaming software that is equivalent with bonding? qethbonding? Cheers