Routing

Expand all | Collapse all

Subscriber Managment on MX:minimal required dynamic-profile options

Jump to Best Answer
  • 1.  Subscriber Managment on MX:minimal required dynamic-profile options

    Posted 12-05-2017 06:23

    I'm going through Juniper's Day One: Subscriber Managment book and noticing some things explained here are somehow contradictional to real-world configurations.

    For example, that's output from the book for dynamic-vlan (service vlan model):

    [edit dynamic-profiles DYNINTF-SVLAN-DHCP-INET]
    admin@SOUTHPARK# show
    interfaces {
     “$junos-interface-ifd-name” {
     unit “$junos-interface-unit” {
     demux-source inet;
     proxy-arp restricted;
     vlan-id “$junos-vlan-id”;
     family inet {
     unnumbered-address lo0.0 preferred-source-address 12.1.1.1;
     }
     }
     }
    }

    (excuse me for formatting, it's copied from PDF)

     

    That's what book sys about this config:

    "The key difference between this configuration and the one in Chapter 2, of course, is the inclusion of the demux-source inet statement. This instructs Junos to use the IPv4 address of the packet to create a unique subscriber session anchor."

     

     However, this explanation seems really weird cause all examples I found in documentation states "demux-source" is used on the IP demux interface and not on the dynamic vlan interface. 

     I also have a working configuration without that line:

     

    root# show dynamic-profiles VLAN-demux                        
    routing-instances {
        "$junos-routing-instance" {
            interface "$junos-interface-name";
        }
    }
    interfaces {
        demux0 {
            unit "$junos-interface-unit" {
                vlan-id "$junos-vlan-id";
                family inet {
                    unnumbered-address "$junos-loopback-interface";
                }
            }
        }
    }

    Another thing that's not clear to me is underlying-interface. That's config from the book:

     

    DYNSUB-SVLAN-IPDEMUX {
     interfaces {
     demux0 {
     unit “$junos-interface-unit” {
     demux-options {
     underlying-interface “$junos-underlying-interface”;
     }
     family inet {
     demux-source {
     $junos-subscriber-ip-address;
     }
     }
     }
     }
     }
    }

    Documentation doesn't state underlying-interface parameter is optional..which, I suppose, means it's required.

    Yet here's my config that works perfectly without it:

     

     

    root# show dynamic-profiles DHCP 
    routing-instances {
        "$junos-routing-instance" {
            interface "$junos-interface-name";
        }
    }
    interfaces {
        demux0 {
            unit "$junos-interface-unit" {
                family inet {
                    demux-source {
                        $junos-subscriber-ip-address;
                    }
                    unnumbered-address "$junos-loopback-interface";
                }
            }
        }
    }

     What's the purpose of this line then?


    #mx
    #subscribermanagment


  • 2.  RE: Subscriber Managment on MX:minimal required dynamic-profile options
    Best Answer

     
    Posted 12-05-2017 10:01

    Hi,

     

    Looks like you're using next-generation subscriber-management release starting from 15.1.

     

    In legacy release , you would have received below error messges due to the missing configuration.

     

    Dec  4 17:34:24  TEST /kernel:  TEST dcd[1929]: UI_CONFIGURATION_ERROR: Process: dcd, path: [edit demux0 unit 1073741846], statement: family, Demux underlying-interface must be configured
    Dec  4 17:34:33  TEST dcd[1929]: UI_CONFIGURATION_ERROR: Process: dcd, path: [edit demux0 unit 1073741847], statement: family, Demux underlying-interface must be configured
    Dec  4 17:34:33  TEST /kernel:  TEST dcd[1929]: UI_CONFIGURATION_ERROR: Process: dcd, path: [edit demux0 unit 1073741847], statement: family, Demux underlying-interface must be configured

     

    Next-generation subscriber-management release has completely new archiecture most of the Junos variable are automatically pulled by the software.

     

    TEST# show dynamic-profiles VLAN-demux
    routing-instances {
        "$junos-routing-instance" {
            interface "$junos-interface-name";
        }
    }
    interfaces {
        demux0 {
            unit "$junos-interface-unit" {
                vlan-id "$junos-vlan-id";
                family inet {
                    unnumbered-address "$junos-loopback-interface";
                }
            }
        }
    }

    TEST# show dynamic-profiles DHCP         
    routing-instances {
        "$junos-routing-instance" {
            interface "$junos-interface-name";
        }
    }
    interfaces {
        demux0 {
            unit "$junos-interface-unit" {
                family inet {
                    unnumbered-address "$junos-loopback-interface";
                }
            }
        }
    }


    TEST# run show subscribers
    Interface           IP Address/VLAN ID                      User Name                      LS:RI
    demux0.3221395385    100                                                              default:default     
    demux0.3221395386   10.110.90.10                            test                      default:default     

    TEST# run show subscribers extensive
    Type: VLAN
    Logical System: default
    Routing Instance: default
    Interface: demux0.3221395385
    Interface type: Dynamic
    Underlying Interface: xe-11/0/0
    Dynamic Profile Name: VLAN-demux
    Dynamic Profile Version: 1
    State: Active
    Session ID: 329757
    PFE Flow ID: 173538
    VLAN Id: 100
    Login Time: 2017-12-05 20:45:01 IST

    Type: DHCP
    User Name: test
    IP Address: 10.110.90.10
    IP Netmask: 255.255.254.0
    Primary DNS Address: 8.8.8.8
    Secondary DNS Address: 4.2.2.2
    Logical System: default
    Routing Instance: default
    Interface: demux0.3221395386
    Interface type: Dynamic
    Underlying Interface: demux0.3221395385
    Dynamic Profile Name: DHCP
    Dynamic Profile Version: 1
    MAC Address: 00:19:01:00:00:01
    State: Active
    Radius Accounting ID: 329758
    Session ID: 329758
    PFE Flow ID: 173539
    VLAN Id: 100
    Login Time: 2017-12-05 20:45:01 IST
    DHCP Options: len 9
    35 01 01 37 04 01 03 3a 3b
    IP Address Pool: Pool1