Re: Bonded NIC's did not come up at boot?

To: debian-user@lists.debian.org
Subject: Re: Bonded NIC's did not come up at boot?
From: Stan Hoeppner <stan@hardwarefreak.com>
Date: Mon, 22 Nov 2010 21:24:36 -0600
Message-id: <[🔎] 4CEB33F4.2020209@hardwarefreak.com>
In-reply-to: <[🔎] 47b7a448290799c4959a5f4144720125@192.168.0.66>
References: <[🔎] 5312b5931efcc0a0e1671576f93ad65e@192.168.0.66> <[🔎] pan.2010.11.22.22.30.27@gmail.com> <[🔎] dbe731edd8d30bbd547fe8d25ce190c3@192.168.0.66> <[🔎] 4CEB08CE.4000704@hardwarefreak.com> <[🔎] 47b7a448290799c4959a5f4144720125@192.168.0.66>

vr put forth on 11/22/2010 6:59 PM:

> I've configured "bond_mode active-backup" which I understand to be mode
> 1.
> 
> Physically, NIC-1 is cabled to switch-1. NIC-2 is cabled to switch-2.
> 
> The goal is for this Linux host to survive a switch, switch-port, or
> NIC failure.

Have a look at this thread from 2007:
http://www.linuxquestions.org/questions/linux-networking-3/bond-always-in-10half-duplex-516066/

In short, mii-tool is "flawed".  _Or_ maybe you need another tool that's
designed to give you information on bonded virtual devices.

-- 
Stan

Reply to:

References:
- Bonded NIC's did not come up at boot?
  - From: vr <debian-user@iotk.net>
- Re: Bonded NIC's did not come up at boot?
  - From: Camaleón <noelamac@gmail.com>
- Re: Bonded NIC's did not come up at boot?
  - From: vr <debian-user@iotk.net>
- Re: Bonded NIC's did not come up at boot?
  - From: Stan Hoeppner <stan@hardwarefreak.com>
- Re: Bonded NIC's did not come up at boot?
  - From: vr <debian-user@iotk.net>

Prev by Date: Re: Monitor vertical refresh rate setting in X.
Next by Date: Re: Does "I/O error" mean hardware problem?
Previous by thread: Re: Bonded NIC's did not come up at boot?
Next by thread: Re: Bonded NIC's did not come up at boot?
Index(es):
- Date
- Thread