[c-nsp] trouble with link aggregation on WS-X6716-10GE

[Sam Thomas]

The command you're looking for is
no mls qos channel-consistency
on your port-channel interface. istr you will need to remove/re-add the interface in "A" port-channel. 

    On Wednesday, March 9, 2016 10:00 AM, Nick Cutting <ncutting at edgetg.co.uk> wrote:
 

 I have seen this before on a 6500

Have a look at this docwiki article:

http://docwiki.cisco.com/wiki/Issue_Description:_Creation_of_a_Secondary_portchannel_%22PortChannel_1_and_1A%22_with_LACP_channel_protocol


-----Original Message-----
From: cisco-nsp [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Gert Doering
Sent: 09 March 2016 14:26
To: Sebastian Beutel
Cc: cisco-nsp at puck.nether.net
Subject: Re: [c-nsp] trouble with link aggregation on WS-X6716-10GE

Hi,

On Wed, Mar 09, 2016 at 03:05:52PM +0100, Sebastian Beutel wrote:
>    When i did a "no shut" on the second port, it refused to join the 
> port channel (Po17) and instead a second portchannel (Po17A) appeared, 
> waiting to be aggregated:
> 
> 17    Po17(SU)        LACP      Te1/4(P)
> 17    Po17A(SN)      LACP      Te1/10(w) 

This typically happens if the *other* end has no idea that LACP is wanted.

gert
--
USENET is *not* the non-clickable part of WWW!
                                                          //www.muc.de/~gert/
Gert Doering - Munich, Germany                            gert at greenie.muc.de
fax: +49-89-35655025                        gert at net.informatik.tu-muenchen.de

_______________________________________________
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/