Hi,

>So are the port-channel ints dropping line protocol, or the gig-E ints 
>themselves?
GigE interfaces themselves.

>If the gig-E ints, are you saying the non-channeled ints stay up, but the 
>channeled ones drop?
Exactly. Physical GigE interfaces dropped line-protocol, but only
those physical GigE interfaces, which had LACP enabled and were part
of a port-channel.


regards,
Martin

2013/6/11, Chuck Church <[email protected]>:
> So are the port-channel ints dropping line protocol, or the gig-E ints
> themselves?  If the gig-E ints, are you saying the non-channeled ints stay
> up, but the channeled ones drop?  I would think Ethernet keepalives
> wouldn't
> be a function of the CPU, but an ASIC thing.  Could be wrong though...
>
> Chuck
>
> -----Original Message-----
> From: cisco-nsp [mailto:[email protected]] On Behalf Of
> Aaron
> Sent: Tuesday, June 11, 2013 10:52 AM
> To: Martin T
> Cc: cisco-nsp
> Subject: Re: [c-nsp] WS-C4506 dropped links which had LACP enabled under
> heavy load
>
> Keep alives need to be generated
>
>
> On Tue, Jun 11, 2013 at 8:35 AM, Martin T <[email protected]> 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  [email protected]
>> https://puck.nether.net/mailman/listinfo/cisco-nsp
>> archive at http://puck.nether.net/pipermail/cisco-nsp/
>>
> _______________________________________________
> cisco-nsp mailing list  [email protected]
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>
>
_______________________________________________
cisco-nsp mailing list  [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

Reply via email to