Page MenuHomePhabricator

No LACP info for cr2-esams:ae2
Closed, ResolvedPublic

Description

For some reasons (Junos bug?) the router doesn't want to display LACP info for the ae2 bundle. ae0 and ae1 work. Not ae2:

ayounsi@re0.cr2-esams> show lacp interfaces        
Aggregated interface: ae0
    LACP state:       Role   Exp   Def  Dist  Col  Syn  Aggr  Timeout  Activity
      xe-0/1/4       Actor    No   Yes    No   No   No   Yes     Fast    Active
      xe-0/1/4     Partner    No   Yes    No   No   No   Yes     Fast   Passive
      xe-0/1/5       Actor    No    No   Yes  Yes  Yes   Yes     Fast    Active
      xe-0/1/5     Partner    No    No   Yes  Yes  Yes   Yes     Fast    Active
      xe-0/1/6       Actor    No   Yes    No   No   No   Yes     Fast    Active
      xe-0/1/6     Partner    No   Yes    No   No   No   Yes     Fast   Passive
      xe-0/1/7       Actor    No    No   Yes  Yes  Yes   Yes     Fast    Active
      xe-0/1/7     Partner    No    No   Yes  Yes  Yes   Yes     Fast    Active
    LACP protocol:        Receive State  Transmit State          Mux State 
      xe-0/1/4            Port disabled     No periodic           Detached
      xe-0/1/5                  Current   Fast periodic Collecting distributing
      xe-0/1/6            Port disabled     No periodic           Detached
      xe-0/1/7                  Current   Fast periodic Collecting distributing

Aggregated interface: ae1
    LACP state:       Role   Exp   Def  Dist  Col  Syn  Aggr  Timeout  Activity
      et-0/2/0       Actor    No    No   Yes  Yes  Yes   Yes     Fast    Active
      et-0/2/0     Partner    No    No   Yes  Yes  Yes   Yes     Fast    Active
      et-0/2/1       Actor    No    No   Yes  Yes  Yes   Yes     Fast    Active
      et-0/2/1     Partner    No    No   Yes  Yes  Yes   Yes     Fast    Active
    LACP protocol:        Receive State  Transmit State          Mux State 
      et-0/2/0                  Current   Fast periodic Collecting distributing
      et-0/2/1                  Current   Fast periodic Collecting distributing

Aggregated interface: ae2

Event Timeline

ayounsi triaged this task as Medium priority.May 29 2020, 8:38 AM
ayounsi created this task.
Restricted Application added a subscriber: Aklapper. · View Herald Transcript
ayounsi mentioned this in Unknown Object (Task).May 29 2020, 8:39 AM

To check after the reboot needed for T245520.

Mentioned in SAL (#wikimedia-operations) [2020-06-03T08:08:06Z] <XioNoX> remove ae2 physical interfaces from external group - T253970

Mentioned in SAL (#wikimedia-operations) [2020-06-03T08:16:59Z] <XioNoX> re-add ae2 physical interfaces to external group - T253970

This behavior is expected as the bundle is not running active with LACP enable. Instead is just a hardcoded aggregated bundle, in other words ; it is just Up with no participation of LACP for any sort of negotiation.
If you notice the other aggregated bundles . the feature is been activated

ae1 {
    description "Core: asw-esams:ae1";
    flexible-vlan-tagging;
    mtu 9192;
    encapsulation flexible-ethernet-services;
    aggregated-ether-options {
        lacp {
            active;    <<<<<<<<<<<<<<<<<
            periodic fast;
        }
    }

https://www.juniper.net/documentation/en_US/junos/topics/concept/layer-2-lacp-security-understanding.html
By default, Ethernet links do not exchange protocol data units (PDUs), which contain information about the state of the link. You can configure Ethernet links to actively transmit PDUs, or you can configure the links to passively transmit them, sending out LACP PDUs only when they receive them from another link. The transmitting link is known as the actor and the receiving link is known as the partner.
In other words since the bundle is not actively sending , nor transmitting LACP PDU the command – show lacp <@ifd> -- is not showing any related information as there is not information to show.

I'll configure our side as active outside of peak time.

Mentioned in SAL (#wikimedia-operations) [2020-06-17T06:23:09Z] <XioNoX> set lacp active on cr2-esams:ae2 - T253970

This didn't work. Configuring the link as active took it down. But did show statistics.

cr2-esams> show lacp interfaces ae2    
Aggregated interface: ae2
    LACP state:       Role   Exp   Def  Dist  Col  Syn  Aggr  Timeout  Activity
      xe-0/1/1       Actor    No   Yes    No   No   No   Yes     Fast    Active
      xe-0/1/1     Partner    No   Yes    No   No   No   Yes     Fast   Passive
      xe-0/1/2       Actor    No   Yes    No   No   No   Yes     Fast    Active
      xe-0/1/2     Partner    No   Yes    No   No   No   Yes     Fast   Passive
      xe-0/1/9       Actor    No   Yes    No   No   No   Yes     Fast    Active
      xe-0/1/9     Partner    No   Yes    No   No   No   Yes     Fast   Passive
    LACP protocol:        Receive State  Transmit State          Mux State 
      xe-0/1/1                Defaulted   Fast periodic           Detached
      xe-0/1/2                Defaulted   Fast periodic           Detached
      xe-0/1/9                Defaulted   Fast periodic           Detached

AMS-IX doesn't mention active in the Juniper part of their doc, but does in the Cisco one.
Next step is to either leave it as it or follow up with AMS-IX NOC.

Emailed AMS-IX NOC to schedule turning up LACP on that link (if able).

Mentioned in SAL (#wikimedia-operations) [2020-06-23T06:06:38Z] <XioNoX> disable peering BGP sessions on AMS-IX - T253970

Mentioned in SAL (#wikimedia-operations) [2020-06-23T08:38:20Z] <XioNoX> re-enable peering BGP sessions on AMS-IX - T253970

I had to re-enable the link before AMS-IX figured out how to turn LACP on on their side. Will re-schedule a window another early morning, hopefully they will have figured out what delayed them until then.

As a side note, configuring LACP as passive also keeps the interface down as long as there is no neighbors. Unlike BFD for example where the link stays up (init) until the first handshake.

I can confirm that I see traffic again and my apologies for the delay in responding, we encountered a provisioning issue which has now been fixed.

Re-scheduled for tomorrow 6am UTC.

Mentioned in SAL (#wikimedia-operations) [2020-06-24T05:59:47Z] <XioNoX> disable peering BGP sessions on AMS-IX - T253970

Mentioned in SAL (#wikimedia-operations) [2020-06-24T06:28:48Z] <XioNoX> enable peering BGP sessions on AMS-IX - T253970

ayounsi claimed this task.

LACP is now up and running.