[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87fy97t9ez.fsf@kruemel.my-eitzenberger.de>
Date: Thu, 15 Feb 2007 22:09:40 +0100
From: Holger Eitzenberger <holger@...eitzenberger.de>
To: Jay Vosburgh <fubar@...ibm.com>
Cc: shemminger@...ux-foundation.org,
sk-drivers@...ts.linux-foundation.org, netdev@...r.kernel.org
Subject: Re: sky2 bonding problem, 802.3ad
Jay Vosburgh <fubar@...ibm.com> writes:
> I'm unfamiliar with your particular switch, but usually this
> kind of problem with bonding 802.3ad is in the switch interaction. The
> switches I have (Cisco) require that 802.3ad mode be explicitly enabled
> on whichever ports it is desired on, so it may be worthwhile to check
> your switch and make sure that it really is configured for 802.3ad on
> the sky2 ports.
I am currently using port 1&2 and port 9&10 for bonding and have
configured all four ports for the same aggregator ID 1, LCAP enabled.
I also switched ports, that is, I changed host1 from using port 1&2 to
use port 9&10 and vice versa. Note that I also used sk98lin which
worked in my setup also. Do you still think it is a misconfigured
switch?
> If the switch is configured, you may want to also check to see
> if it has counters for LACPDUs sent and received. If the switch is not
> sending and receiving LACPDUs on the appropriate ports, then it's more
> likely to be a communications problem somewhere (vs. an 802.3ad
> negotiation problem).
I will check tomorrow morning whether I see the LACPDUs in the log and
report.
Any more tests which may be helpfull?
Thanks. /holger
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists