Hey folks – finally getting around to a project that has been getting held
up.

We have an MX480 deployed currently that is handling PPPOE traffic.  The
interface (AE with 4X10G) configuration is pretty straight forward:

paul@xxxxxxxxxxxx# show interfaces ae3

description “xxxxxxxxxxxxxxxxxxxxxxxx";

vlan-tagging;

auto-configure {

    vlan-ranges {

        dynamic-profile pppoe {

            accept pppoe;

            ranges {

                any;

            }

        }

    }

    remove-when-no-subscribers;

}

mtu 9192;

encapsulation flexible-ethernet-services;

aggregated-ether-options {

    lacp {

        passive;

        periodic fast;

    }

}


Obviously there is an access section and a dynamic-profile section to
support this configuration.  This works today and well.

Now, we want to bring another VLAN into the MX480 for additional PPPOE
subscribers – but the catch is that this is via a wholesale provider handing
off lt2p tunnels (Bell Canada wholesale).

Today, on our Cisco configuration we have:

vpdn-group AGAS-1005

! Default L2TP VPDN group

 accept-dialin

  protocol l2tp

  virtual-template 1

 local name nexicom-1

 lcp renegotiation always

 l2tp tunnel password 7 xxxxxxxxxxxxxxxxxxxxx



bba-group pppoe global

 virtual-template 1



interface GigabitEthernet0/3.901

 description Bell AGAS Service (xxxxxxxxxxxxxxxxxxx)

 encapsulation dot1Q 901

 ip address xx.xx.xxx.27 255.255.255.248 secondary

 ip address xx.xx.xxx.28 255.255.255.248 secondary

 ip address xx.xx.xxx.26 255.255.255.248


And then virtual template(s) and a few static routes to each the far end of
the l2tp tunnels.

Has anyone converted a configuration like the above Cisco configuration into
a Juniper MX style configuration?  I did some reading on l2tp for subscriber
management on JunOS and am confused as ever :)

Thanks,

Paul




_______________________________________________
juniper-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/juniper-nsp

Reply via email to