<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Disabling failback on NIC Bonding in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/disabling-failback-on-nic-bonding/m-p/4294422#M81728</link>
    <description>We had a problem with a Foundry switch that took a port down then brought it back up (as far as the O/S was concerned). However, the port wasn't fully enabled and the upshot was it took the server off the air even though the server still had a valid network port available.&lt;BR /&gt;&lt;BR /&gt;This solution would allow us to control which port is live while still maintaining resilience.</description>
    <pubDate>Tue, 28 Oct 2008 16:24:59 GMT</pubDate>
    <dc:creator>Mick Ryan</dc:creator>
    <dc:date>2008-10-28T16:24:59Z</dc:date>
    <item>
      <title>Disabling failback on NIC Bonding</title>
      <link>https://community.hpe.com/t5/operating-system-linux/disabling-failback-on-nic-bonding/m-p/4294416#M81722</link>
      <description>Hi All&lt;BR /&gt;&lt;BR /&gt;I'm running SLES10.0 and have NIC bonding configured using eth0 and eth1 which is all working fine. However, my question relates to NIC failover. &lt;BR /&gt;&lt;BR /&gt;I have eth0 defined as the primary and when eth0 gets disconnected, the service fails over to eth1. When service is restored, it fails back to eth0.&lt;BR /&gt;&lt;BR /&gt;What I'd like, is for the service to stay on eth1 (or whatever the slave is), until I decide to fail it back.&lt;BR /&gt;&lt;BR /&gt;Is this possible? I've been thinking about options like creating a script to look out for a failover message and updating the /sys/class/net/bond0/bonding/primary file, but it'd be a lot nicer and simpler if there was some kind of variable I could set (or not set).&lt;BR /&gt;&lt;BR /&gt;Cheers&lt;BR /&gt;&lt;BR /&gt;Mick</description>
      <pubDate>Mon, 27 Oct 2008 10:39:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/disabling-failback-on-nic-bonding/m-p/4294416#M81722</guid>
      <dc:creator>Mick Ryan</dc:creator>
      <dc:date>2008-10-27T10:39:54Z</dc:date>
    </item>
    <item>
      <title>Re: Disabling failback on NIC Bonding</title>
      <link>https://community.hpe.com/t5/operating-system-linux/disabling-failback-on-nic-bonding/m-p/4294417#M81723</link>
      <description>Try without specifying the "primary" option.</description>
      <pubDate>Mon, 27 Oct 2008 11:54:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/disabling-failback-on-nic-bonding/m-p/4294417#M81723</guid>
      <dc:creator>Ivan Ferreira</dc:creator>
      <dc:date>2008-10-27T11:54:13Z</dc:date>
    </item>
    <item>
      <title>Re: Disabling failback on NIC Bonding</title>
      <link>https://community.hpe.com/t5/operating-system-linux/disabling-failback-on-nic-bonding/m-p/4294418#M81724</link>
      <description>...and the "primary" option Ivan refers to should be wherever the "bonding" kernel module gets its options.&lt;BR /&gt;&lt;BR /&gt;I don't have a SLES10 machine at hand at the moment, so I cannot check how its startup scripts handle the bonded NICs. But I'd start by checking the /etc/modprobe.conf file and/or /etc/modprobe.d directory.&lt;BR /&gt;&lt;BR /&gt;MK</description>
      <pubDate>Mon, 27 Oct 2008 12:24:45 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/disabling-failback-on-nic-bonding/m-p/4294418#M81724</guid>
      <dc:creator>Matti_Kurkela</dc:creator>
      <dc:date>2008-10-27T12:24:45Z</dc:date>
    </item>
    <item>
      <title>Re: Disabling failback on NIC Bonding</title>
      <link>https://community.hpe.com/t5/operating-system-linux/disabling-failback-on-nic-bonding/m-p/4294419#M81725</link>
      <description>Thanks, guys. I thought about the primary option, but I wonder how the system decides which is the "correct" interface. In my bond setup, I reference the slaves as eth0/1 which are in turn defined in udev as their respective pci devices, so I'd imagine this would work for me.&lt;BR /&gt;&lt;BR /&gt;Cheers&lt;BR /&gt;&lt;BR /&gt;Mick&lt;BR /&gt;</description>
      <pubDate>Mon, 27 Oct 2008 12:59:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/disabling-failback-on-nic-bonding/m-p/4294419#M81725</guid>
      <dc:creator>Mick Ryan</dc:creator>
      <dc:date>2008-10-27T12:59:08Z</dc:date>
    </item>
    <item>
      <title>Re: Disabling failback on NIC Bonding</title>
      <link>https://community.hpe.com/t5/operating-system-linux/disabling-failback-on-nic-bonding/m-p/4294420#M81726</link>
      <description>My solution to the problem of confirming the interface after network startup, was to add a POST_UP_SCRIPT to the ifcfg-bond0 file. In the script, I use this command to force the bond onto eth0&lt;BR /&gt;ifenslave -c bond0 eth0&lt;BR /&gt;&lt;BR /&gt;Cheers&lt;BR /&gt;&lt;BR /&gt;Mick</description>
      <pubDate>Tue, 28 Oct 2008 11:56:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/disabling-failback-on-nic-bonding/m-p/4294420#M81726</guid>
      <dc:creator>Mick Ryan</dc:creator>
      <dc:date>2008-10-28T11:56:55Z</dc:date>
    </item>
    <item>
      <title>Re: Disabling failback on NIC Bonding</title>
      <link>https://community.hpe.com/t5/operating-system-linux/disabling-failback-on-nic-bonding/m-p/4294421#M81727</link>
      <description>Out of mostly idle curiousity, why do you want to disable the failback?</description>
      <pubDate>Tue, 28 Oct 2008 16:06:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/disabling-failback-on-nic-bonding/m-p/4294421#M81727</guid>
      <dc:creator>rick jones</dc:creator>
      <dc:date>2008-10-28T16:06:31Z</dc:date>
    </item>
    <item>
      <title>Re: Disabling failback on NIC Bonding</title>
      <link>https://community.hpe.com/t5/operating-system-linux/disabling-failback-on-nic-bonding/m-p/4294422#M81728</link>
      <description>We had a problem with a Foundry switch that took a port down then brought it back up (as far as the O/S was concerned). However, the port wasn't fully enabled and the upshot was it took the server off the air even though the server still had a valid network port available.&lt;BR /&gt;&lt;BR /&gt;This solution would allow us to control which port is live while still maintaining resilience.</description>
      <pubDate>Tue, 28 Oct 2008 16:24:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/disabling-failback-on-nic-bonding/m-p/4294422#M81728</guid>
      <dc:creator>Mick Ryan</dc:creator>
      <dc:date>2008-10-28T16:24:59Z</dc:date>
    </item>
    <item>
      <title>Re: Disabling failback on NIC Bonding</title>
      <link>https://community.hpe.com/t5/operating-system-linux/disabling-failback-on-nic-bonding/m-p/4294423#M81729</link>
      <description>Ah, so it is to be a workaround/kludge (depending on the point of view :) to some bad switch behaviour.  Thanks for satisfying my curiousity.&lt;BR /&gt;&lt;BR /&gt;I trust that Foundry is/was able to address the problem in the switch?</description>
      <pubDate>Tue, 28 Oct 2008 16:41:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/disabling-failback-on-nic-bonding/m-p/4294423#M81729</guid>
      <dc:creator>rick jones</dc:creator>
      <dc:date>2008-10-28T16:41:18Z</dc:date>
    </item>
    <item>
      <title>Re: Disabling failback on NIC Bonding</title>
      <link>https://community.hpe.com/t5/operating-system-linux/disabling-failback-on-nic-bonding/m-p/4294424#M81730</link>
      <description>Yes they were and everything is fine. However, the feeling is that this control would be preferable to automated failovers. &lt;BR /&gt;&lt;BR /&gt;Cheers&lt;BR /&gt;&lt;BR /&gt;Mick</description>
      <pubDate>Tue, 28 Oct 2008 16:43:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/disabling-failback-on-nic-bonding/m-p/4294424#M81730</guid>
      <dc:creator>Mick Ryan</dc:creator>
      <dc:date>2008-10-28T16:43:32Z</dc:date>
    </item>
  </channel>
</rss>

