Routing

Expand all | Collapse all

LNS on MX240 issue

Jump to Best Answer
  • 1.  LNS on MX240 issue

     
    Posted 10-18-2017 04:46

    Trying to get the LNS configured, but struggling a little, due to unforeseen glitches, as per below:

     

    I am currently following the following documentation: https://www.juniper.net/documentation/en_US/junos/topics/example/subscriber-management-l2tp-lns.html and am changing the various sections to suit our requirements, but have come across another issue at the section:

     

    9: Configure a dynamic profile that dynamically creates L2TP logical interfaces for dual-stack subscribers:

     

    The following command is missing: edit routing-options access route $junos-framed-route-ip-address-prefix

     

    According to Juniper Notes, the reason is listed at: https://kb.juniper.net/InfoCenter/index?page=content&id=KB31778&actp=METADATA

     

    But, then the workaround fails at the following point:

     

    routing-instances {
            "$junos-routing-instance" {
                interface "$junos-interface-name";
                routing-options {
                    rib "$junos-ipv6-rib"

     

    The $junos-ipv6-rib statement just does not exist. Now, I know this is calling the Routing Information Base but junos specifies it within the statement, we don’t have that. It is getting rather annoying now as I cannot complete the LNS configs and we need them tested urgently.

     

    Any help here would be great.



  • 2.  RE: LNS on MX240 issue

     
    Posted 10-18-2017 05:40

    Hi,


    Sample LNS configuration is available under below KB

     

    https://kb.juniper.net/InfoCenter/index?page=content&id=KB24104&act=login

     

    Please share complete configuration and version info in case issue still persist.

     

    Regards,
    RahuL N



  • 3.  RE: LNS on MX240 issue

     
    Posted 10-18-2017 05:47

    In case you're using dual-stack.

     

    show dynamic-profiles
    LNS {
        routing-instances {
            "$junos-routing-instance" {
                interface "$junos-interface-name";
                routing-options {
                    rib "$junos-ipv6-rib" {
                        access {
                            route $junos-framed-route-ipv6-address-prefix {
                                qualified-next-hop "$junos-interface-name";
                                metric "$junos-framed-route-ipv6-cost";
                                preference "$junos-framed-route-ipv6-distance";
                                tag "$junos-framed-route-ipv6-tag";
                            }
                        }
                        access-internal {
                            route $junos-subscriber-ipv6-address {
                                qualified-next-hop "$junos-interface-name";
                            }
                        }
                    }
                    access {
                        route $junos-framed-route-ip-address-prefix {
                            qualified-next-hop "$junos-interface-name";
                            metric "$junos-framed-route-cost";
                            preference "$junos-framed-route-distance";
                        }
                    }
                    access-internal {
                        route $junos-subscriber-ip-address {
                            qualified-next-hop "$junos-interface-name";
                        }
                    }
                }
            }
        }
        interfaces {
            "$junos-interface-ifd-name" {
                unit "$junos-interface-unit" {
                    dial-options {
                        l2tp-interface-id ce-l2tp-interface-id;
                        dedicated;
                    }
                    proxy-arp;
                    family inet {
                        unnumbered-address "$junos-loopback-interface";
                    }
                    family inet6 {
                        unnumbered-address "$junos-loopback-interface";
                    }
                }
            }
        }
        protocols {
            router-advertisement {
                interface "$junos-interface-name" {
                    prefix $junos-ipv6-ndra-prefix;
                }
            }
        }
    }



  • 4.  RE: LNS on MX240 issue

     
    Posted 10-18-2017 05:56

    Hi Rahul

     

    I will give that config a go and see if I can make some progress.

     

    Will update...

     

    Thank you



  • 5.  RE: LNS on MX240 issue

     
    Posted 10-18-2017 07:52

    Hi Rahul,

     

    I have entered the configuration with obvious changes to IPs etc...

    Got one more little issue you may be able to help me with please before I can test anything:

    The radius server is configured via a static route and then injected into isis.

    The LAC is also a static route configuration but I cannot get it to inject into isis.... very weird...

    Config that works on SRX:

    set routing-options static route 192.168.50.88/32 next-hop 192.168.50.89
    set protocols isis export export_statics
    set policy-options policy-statement export_statics term 1 from protocol static
    set policy-options policy-statement export_statics term 1 then accept

     

    Config that does not work on LNS:

    set routing-options static route 195.80.0.18/32 next-hop 195.80.0.17
    set protocols isis export export_statics
    set policy-options policy-statement export_statics term 1 from protocol static
    set policy-options policy-statement export_statics term 1 then accept

     

    Any idead please?

     

     



  • 6.  RE: LNS on MX240 issue

     
    Posted 10-18-2017 08:13

    Scrub that.... my bad

     

    It's always a typo or a missed statement.... I forgot to add the itnerface to the isis protocol.... I now have connectivity from the LAC to the RADIUS and can start testing......



  • 7.  RE: LNS on MX240 issue
    Best Answer

     
    Posted 11-20-2017 21:25

    Hi Clive

     

    We've tested MX240 as LAC and  LNS. Both seems to be working fine. Can you please help to close the thread?

     

    Regards,

    Rahul N