Thanks all..! I just had to sit and trace all the cables to make sure the tx/rx lined up for the right circuits as well as hitting the right patch panel ports. Once all that got aligned nicely things started working magically. thanks,-nevin
On Tuesday, May 24, 2016 2:49 AM, Eygene Ryabinkin <rea+na...@grid.kiae.ru> wrote: Nevin, good day. Sun, May 22, 2016 at 07:55:31PM +0000, Nevin Gonsalves via NANOG wrote: > Hoping someone may have come across a similar issue. Has anyone ever > seen a situation where maybe like a Level3 transport system could be > possibly dropping LACP frames..? > End point A - tx and rx counts incrementing for LACP > LACP info: Role System System Port Port Port > priority identifier priority number > key et-0/0/0.0 Actor 127 5c:45:27:6d:2a:c0 127 > 56 16 et-0/0/0.0 Partner 1 00:00:00:00:00:00 127 > 56 16 LACP Statistics: LACP Rx LACP Tx Unknown Rx > Illegal Rx et-0/0/0.0 6925 6922 0 > 0 > End Point B - no RX, partner macs are 0s.. > LACP info: Role System System Port Port > Port priority identifier priority > number key et-9/1/0.0 Actor 127 5c:45:27:77:d6:c4 > 127 68 16 et-9/1/0.0 Partner 1 00:00:00:00:00:00 > 1 68 16 LACP Statistics: LACP Rx LACP Tx Unknown > Rx Illegal Rx et-9/1/0.0 0 6752 0 > 0 > Link works fine otherwise outside the aggregate and w/o LACP. Any > inputs will be greatly appreciated. Cisco Q-in-Q implementation in some configurations (details are blurry, since our provider turned to X-connect quite fast). Also VPLS implementation in (older) EXOS releases (Extreme Networks), https://gtacknowledge.extremenetworks.com/articles/Solution/Layer-2-Control-packets-like-STP-LACP-EDP-etc-are-not-passing-through-VPLS -- Eygene Ryabinkin, National Research Centre "Kurchatov Institute" Always code as if the guy who ends up maintaining your code will be a violent psychopath who knows where you live.