[c-nsp] 7200 npe-g2 lacp

[Adam Vitkovsky]

Yup I came to the same conclusion when I tried to run port-channel on 7200
against mLACP on A9K
The ASR didn't see any LACP coming from the 7200

adam
-----Original Message-----
From: cisco-nsp-bounces at puck.nether.net
[mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of cnsp at marenda.net
Sent: Wednesday, October 10, 2012 10:05 PM
To: 'Darren O'Connor'; cisco-nsp at puck.nether.net
Subject: Re: [c-nsp] 7200 npe-g2 lacp



> -----Ursprüngliche Nachricht-----
> Von: cisco-nsp-bounces at puck.nether.net [mailto:cisco-nsp- 
> bounces at puck.nether.net] Im Auftrag von Darren O'Connor
> Gesendet: mercredi 10 octobre 2012 17:53
> An: cisco-nsp at puck.nether.net
> Betreff: [c-nsp] 7200 npe-g2 lacp
> 
> I can see this platform supports etherchannel, but does it support 
> lacp?
> 
> I think now, but wanted to check

Looked at a 7201 c7200p-spservicesk9-mz.122-33.SRE6.bin

Configuring an int port-channel 1
and putting the currently unused gig0/3 into channelgroup 1 results in
flapping of the mgmt interface fas0/0 (o.k, it's the same controller-chip as
for gig0/3):

%LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel1, changed state
to down
%SYS-5-CONFIG_I: Configured from console by jm on vty0
%LINK-3-UPDOWN: Interface GigabitEthernet0/3, changed state to down
%ENTITY_ALARM-6-INFO: ASSERT CRITICAL Fa0/0 Physical Port Link Down
%LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/3, changed
state to down
%LINK-3-UPDOWN: Interface GigabitEthernet0/3, changed state to up
%ENTITY_ALARM-6-INFO: CLEAR CRITICAL Fa0/0 Physical Port Link Down
GigabitEthernet0/3 added as member-1 to port-channel1
%LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/3, changed
state to up
%LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel1, changed state
to up
GigabitEthernet0/3 taken out of port-channel1
%LINK-3-UPDOWN: Interface GigabitEthernet0/3, changed state to down
%ENTITY_ALARM-6-INFO: ASSERT CRITICAL Fa0/0 Physical Port Link Down
%LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel1, changed state
to down
%LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/3, changed
state to down
%LINK-3-UPDOWN: Interface GigabitEthernet0/3, changed state to up
%ENTITY_ALARM-6-INFO: CLEAR CRITICAL Fa0/0 Physical Port Link Down
%LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/3, changed
state to up
%LINK-5-CHANGED: Interface Port-channel1, changed state to administratively
down
%SYS-5-CONFIG_I: Configured from console by jm on vty0

Hope the other two "CPU" Gig Ports do not flap when you configure one of
them to go into a port-channel. 
Ok, yes, I know, the NPE-G2 does not have the Gig0/3 port.

Not found any hint on lacp, seems to be a static thing.

Hope this help's,

Juergen.



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