Junos OS

DHCP Subscriber w/ Dynamic Routes?

  • 1.  DHCP Subscriber w/ Dynamic Routes?

    Posted 12-17-2020 18:11

    I have the below dynamic profile for DHCP in the lab.    I am feeding a Framed-Route from RADIUS into the DHCP server on the MX BNG and I do see that Framed-Route coming in when doing a pcap, however the BNG is not installing the route.

    Also, the class-of-service configuration is not applying either.  I've looked at both the underlying interface and the demux0.XXX interface and the tcp-dynamic profile isn't being applied.

    dhcp-profile {
        routing-instances {
            "$junos-routing-instance" {
                interface "$junos-interface-name";
                routing-options {
                    access {
                        route $junos-framed-route-ip-address-prefix {
                            qualified-next-hop "$junos-interface-name";
                        }
                    }
                }
            }
        }
        interfaces {
            "$junos-interface-ifd-name" {
                unit "$junos-interface-unit" {
                    family inet {
                        rpf-check;
                        filter {
                            input "$junos-input-filter";
                        }
                        unnumbered-address lo0.0;
                    }
                }
            }
        }
        class-of-service {
            traffic-control-profiles {
                tcp-dynamic {
                    scheduler-map sm1;
                    shaping-rate "$junos-cos-shaping-rate" burst-size "$junos-cos-shaping-rate-burst";
                    excess-rate proportion 0;
                }
            }
            interfaces {
                "$junos-interface-ifd-name" {
                    unit "$junos-interface-unit" {
                        output-traffic-control-profile tcp-dynamic;
                    }
                }
            }
            scheduler-maps {
                sm1 {
                    forwarding-class best-effort scheduler data-scheduler;
                    forwarding-class assured-forwarding scheduler data-scheduler;
                    forwarding-class network-control scheduler data-scheduler;
                    forwarding-class expedited-forwarding scheduler voice-scheduler;
                }
            }
            schedulers {
                data-scheduler {
                    transmit-rate percent 90;
                    priority low;
                    drop-profile-map loss-priority any protocol any drop-profile moderate-drop;
                }
                voice-scheduler {
                    transmit-rate {
                        percent 10;
                        rate-limit;
                    }
                    priority strict-high;
                }
            }
        }
    }