[c-nsp] WS-C4506 dropped links which had LACP enabled under heavy load

[Chuck Church]

Hmmm.  Perhaps Cisco's implementation of LACP and etherchannel intentionally
has the line-protocol drop when LACP neighbors time out, maybe that's how
they get un-bundled?

Chuck

-----Original Message-----
From: cisco-nsp [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of
Martin T
Sent: Tuesday, June 11, 2013 12:14 PM
To: Aaron
Cc: cisco-nsp
Subject: Re: [c-nsp] WS-C4506 dropped links which had LACP enabled under
heavy load

Aaron,

as far as I know, keepalive frames(EtherType 0x9000) have nothing to do with
Ethernet interface "line protocol". You can connect two ports with keepalive
frames disabled, but you'll still see the "line protocol" up. Cisco "line
protocol" should be "link integrity check"
signals sent by Ethernet transceiver circuits(PHY).


regards,
Martin


2013/6/11, Aaron <dudepron at gmail.com>:
> Keep alives need to be generated
>
>
> On Tue, Jun 11, 2013 at 8:35 AM, Martin T <m4rtntns at gmail.com> wrote:
>
>> Hi,
>>
>> has anyone seen a behavior where Cisco WS-C4506 drops "line-protocol"
>> on GigE ports(WS-X4306-GB module) which have LACP enabled when 
>> SUP(Sup
>> V-10GE) CPU load is ~100%? I guess that LACP frames are processed in 
>> SUP CPU and it's normal to see LACPDUs time-out, but how can this 
>> affect interface line-protocol?
>>
>>
>> regards,
>> Martin
>> _______________________________________________
>> cisco-nsp mailing list  cisco-nsp at puck.nether.net 
>> https://puck.nether.net/mailman/listinfo/cisco-nsp
>> archive at http://puck.nether.net/pipermail/cisco-nsp/
>>
>
_______________________________________________
cisco-nsp mailing list  cisco-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/