The ports belonging to a mLACP bundle have to be running LACP. The non-forwarding ASR9K uses LACP to keep the peer port in a standby state. Putting the port in loopback would mean it would have to run LACP with itself somehow, not sure if that's going to work... You could probably use a loopback cable to another port on the same node in a different bundle.
Phil On 8/7/12 10:37 AM, "adam vitkovsky" <[email protected]> wrote: >Hi Folks, >The "on" keyword means LACP is not run over the port -at least that's what >documentation says >So how the heck does the port know that the other end is not configured >for >LACP ??? > >I'm starting to test the MLACP and don't have the CE hanging of the ASR9Ks >yet so I thought I'd configure the interfaces with "loopback internal" so >they'd come up and than I've added them to bundle >Well... what I got afterwards on both ASR9Ks is: Interface >GigabitEthernet0/2/0/2 in Bundle-Ether3 is incompatible with the active >bundle members; link is not using LACP but active bundle members are >Even though Gig0/2/0/2 is the only interface in the bundle on a particular >ASR9K > >Bundle-Ether3 > Status: Down > Local links <active/standby/configured>: 0 / 0 / 1 > Local bandwidth <effective/available>: 0 (0) kbps > MAC address (source): 0010.0010.0010 (Configured) > Minimum active links / bandwidth: 1 / 1 kbps > Maximum active links: 64 > Wait while timer: 2000 ms > Load balancing: Default > LACP: Operational > Flap suppression timer: Off > Cisco extensions: Disabled > mLACP: Operational > ICCP Group: 1 > Role: Active > Foreign links <active/configured>: 0 / 1 > Switchover type: Non-revertive > Recovery delay: 300 s > Maximize threshold: 1 link > IPv4 BFD: Not configured > > Port Device State Port ID B/W, >kbps > -------------------- --------------- ----------- -------------- >---------- > Gi0/2/0/2 Local Configured 0x8000, 0x9004 >1000000 > Incompatible with other links in the bundle (LACP vs non-LACP) > Gi0/2/0/2 10.1.1.4 Configured 0x8000, 0xa004 >1000000 > Link is down > > > >do sh bundle stat >Tue Aug 7 22:32:05.784 UTC >Checking configuration... > > Cross checking configuration with bundle >database..........................OK > > Checking configuration >setup...............................................OK > >Checking configuration >result................................................OK >-------------------------------------------------------------------------- >-- >--- >Checking operational state... > > Checking local system >operation............................................OK > > Checking for mLACP >inconsistencies.........................................OK > > Checking mLACP operation... > > ICCP Group 1: > Bundle-Ether3 (Not operational): > WARNING: Bundle is down on local device > Device Local: > WARNING: Not enough selectable links to be operational > WARNING: Bundle is down on peer device 10.1.1.4 > GigabitEthernet0/2/0/2 (Not active): > WARNING: Member state TLV reported error on local device > Device Local: > WARNING: Incompatible with other links in the bundle (LACP vs > non-LACP) > Gi0/2/0/2 (Not active): > INFO: Member is down on peer device 10.1.1.4 > > Checking mLACP operation >result.......................................WARNING > > > > > > >adam > > > >_______________________________________________ >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/
