Junos
Highlighted
Junos

pppoe on aggregated ethernet interfaces

[ Edited ]
‎04-17-2019 04:34 AM

I'm trying to get pppoe subscriber management working on aggregated ethernet interfaces.

On this so-called pppoe concentrator I have an ae interface with one member:

 

xe-1/2/0 {
    gigether-options {
        802.3ad ae0;
    }
}

 

ae0 {
    description "CORE: core-nkh-01,ae8";
    flexible-vlan-tagging;
    native-vlan-id 1;
        remove-when-no-subscribers;
    }
    mtu 9192;
    encapsulation flexible-ethernet-services;
    aggregated-ether-options {
        lacp {
            active;
        }
    }
    unit 1 {
        vlan-id 1;
        family inet {
            mtu 1500;
            address xx.xx.xx.xx/yy;
        }
        family inet6 {
            mtu 1500;
        }
        family mpls;
    }
    unit 123 {
        vlan-id 123;
        family pppoe {
            dynamic-profile PPPoE-PROFILE-P;
        }
    }
}

 

This pppoe concentrator is connected to a CORE router of ours.

It currently has the following EVPN configuration:

 

TESTING-PPPoE {
    instance-type virtual-switch;
    route-distinguisher 202120L:12345;
    vrf-target target:202120L:12345;
    protocols {
        evpn {
            extended-vlan-list 123;
        }
    }
    bridge-domains {
        123 {
            vlan-id 123;
            interface ae8.123;
        }
    }
}

As well as on other routers needing to talk EVPN.

 

On the subinterface ae0.123 I only see incoming packets, but not outgoing packets. Even not PADI packets.

Once I switch outside the ae interface and just let pppoe packets come in on the xe-1/2/0 interface, I see all kinds of different pppoe packets.

 

So my question is: does pppoe termination on ae interfaces work? If so, how would I accomplish that?

 

Beeelze

 

 

1 ACCEPTED SOLUTION

Accepted Solutions
Junos
Solution
Accepted by topic author Beeelzebub
‎04-17-2019 05:25 AM

Re: pppoe on aggregated ethernet interfaces

‎04-17-2019 04:43 AM

Hi, Please try below configuration.

 

ae1 {
flexible-vlan-tagging;
encapsulation flexible-ethernet-services;
aggregated-ether-options {
lacp {
active;
periodic fast;
}
}
}
demux0 {
unit 100 {
vlan-id 100;
demux-options {
underlying-interface ae1;
}
family pppoe {
duplicate-protection;
dynamic-profile PPPOE;
}
}

3 REPLIES 3
Junos
Solution
Accepted by topic author Beeelzebub
‎04-17-2019 05:25 AM

Re: pppoe on aggregated ethernet interfaces

‎04-17-2019 04:43 AM

Hi, Please try below configuration.

 

ae1 {
flexible-vlan-tagging;
encapsulation flexible-ethernet-services;
aggregated-ether-options {
lacp {
active;
periodic fast;
}
}
}
demux0 {
unit 100 {
vlan-id 100;
demux-options {
underlying-interface ae1;
}
family pppoe {
duplicate-protection;
dynamic-profile PPPOE;
}
}

Junos

Re: pppoe on aggregated ethernet interfaces

‎04-17-2019 05:24 AM

Hey Mayar,

 

Great! That configuration seems to work!

I should be able to manage the rest myself now.

 

Thanks again.

 

Beeelze

Junos

Re: pppoe on aggregated ethernet interfaces

‎04-17-2019 05:48 AM

Strange, my MX routers never say anything about below parse error (Attr-Type: 13 = Framed-Compression).

 

Apr 17 14:37:24.316 Parsing RADIUS message for session-id:7278

Apr 17 14:37:24.316 radius-access-accept: Framed-Protocol received: 1

Apr 17 14:37:24.317 RADIUS Attribute: Parse Error: "Unsupported attribute type" Radius Standard Attr-Type: 13

Apr 17 14:37:24.317 radius-access-accept: Framed-IP-Address received: 185.52.209.160

Apr 17 14:37:24.317 radius-access-accept: Framed-IP-Netmask received: 255.255.255.255

Apr 17 14:37:24.317 radius-access-accept: Ingress-Policy-Name (Juniper-ERX-VSA) received: police-unlimited

Apr 17 14:37:24.317 radius-access-accept: Egress-Policy-Name (Juniper-ERX-VSA) received: police-unlimited