vMX

 View Only
last person joined: 6 days ago 

Ask questions and share experiences about vMX.

  • 1.  LACP issue on vMX 18.2R1.9 - ae0 interface is always down

    Posted 11-06-2020 09:12

    Hi All,

     

    I have set up two vMX routers, activated the trial license, configured lite-mode for the FPCs, and set network-services to enhanced-ip

     

    Running these vmX on KVM with virtio-net-pci interface

    SR-IOV is not enabled.

     

    The two gig interface are up but ae0 interface remains down

     

    root@R2> show interfaces terse
    Interface Admin Link Proto Local Remote

    ge-0/0/3 up up
    ge-0/0/3.0 up up aenet --> ae0.0
    ge-0/0/4 up up
    ge-0/0/4.0 up up aenet --> ae0.0

    ae0 up down
    ae0.0 up down inet 172.31.129.2/30
    multiservice

     

    vMX#1 configuration

    chassis {
    aggregated-devices {
    ethernet {
    device-count 3;
    }
    }
    fpc 0 {
    lite-mode;
    }
    network-services enhanced-ip;
    }
    interfaces {
    ge-0/0/3 {
    gigether-options {
    802.3ad ae0;
    }
    }
    ge-0/0/4 {
    gigether-options {
    802.3ad ae0;
    }
    }
    ae0 {
    description vMX-1;
    aggregated-ether-options {
    lacp {
    active;
    }
    }
    unit 0 {
    family inet {
    address 172.31.129.1/30;
    }
    }
    }

     

    vMX#2 Configuration

    chassis {
    aggregated-devices {
    ethernet {
    device-count 3;
    }
    }
    fpc 0 {
    lite-mode;
    }
    network-services enhanced-ip;
    }
    interfaces {
    ge-0/0/3 {
    gigether-options {
    802.3ad ae0;
    }
    }
    ge-0/0/4 {
    gigether-options {
    802.3ad ae0;
    }
    }
    ae0 {
    description vMX-2;
    aggregated-ether-options {
    lacp {
    active;
    }
    }
    unit 0 {
    family inet {
    address 172.31.129.2/30;
    }
    }
    }

     

     

    Is there anything wrong with this configuration that could cause the AE0 interface to be down.

     

    Thanks for your reply

    Stephane



  • 2.  Betreff: LACP issue on vMX 18.2R1.9 - ae0 interface is always down

     
    Posted 11-06-2020 09:39

    Hello Stephane,

     

    physical interfaces on vMX are always up, even there is nothing connected to it. I'd suggest you to configure the physical interfaces as "family inet" ports with a /30 subnet at first, and check if pings are working to the vMX counterpart. If both "ge-" interfaces have connectivity to the other vMX, then you can proceed with configuring the ae interface.



  • 3.  RE: LACP issue on vMX 18.2R1.9 - ae0 interface is always down

    Posted 11-22-2020 13:32
    Is the other side configured with LACP?  What do you see if you enter show lacp interfaces or show lacp statistics? 

    Regards,


  • 4.  RE: LACP issue on vMX 18.2R1.9 - ae0 interface is always down

    Posted 11-22-2020 15:27
    Try set interfaces ae0 aggregated-ether-options lacp force-up on both sides.  LACP messages might not be supported across the bridge connecting the two  vMX instances in your setup.

    Regards,


  • 5.  RE: LACP issue on vMX 18.2R1.9 - ae0 interface is always down

    This message was posted by a user wishing to remain anonymous
    Posted 04-14-2024 08:33
    This message was posted by a user wishing to remain anonymous

    Thank you so much, this worked for me.  I was running EVPN over MPLS, with one of the CE's being multihomed to 2 PE's (the PE's had to have a LAG with the 2 connections to the same CE switch device). I was stuck and going round in circles for a few hours, turns out, I had to force the LACP to be up using the command 

    set interfaces ae0 aggregated-ether-options lacp force-up


    Original Message


  • 6.  RE: LACP issue on vMX 18.2R1.9 - ae0 interface is always down

    Posted 03-14-2023 19:11

    On eveng for it to work, you need to configure a MAC address for the aex (system-id) and force it up.

    The images have the same MAC for the ae0 interface and by ricochet the same system-id for LACP… It doesn't seem to work that way, unless you change the macs / system id and  force the lag on up… at least in the virtual environment…



    ------------------------------
    MOHAMED MEHENOUN
    ------------------------------

    Original Message