[j-nsp] prefix-limit effectiveness

[Dan Farrell]

I have asked for full and the default from an upstream I have connected to an EX3200. For now I'm just wanting to use the default route-



import default-route;



policy-statement default-route {

    term default {

        from {

            route-filter 0.0.0.0/0 exact;

        }

        then accept;

    }

    term reject-rest {

        then reject;

    }

}



Then I limit the number of prefixes it will even look at to 5000 -



import default-route;

family inet {

    unicast {

        prefix-limit {

            maximum 5000;

        }

    }

    any {

        prefix-limit {

            maximum 5000;

        }

    }

}



This is effective- I have only the default to use from my upstream. But I keep generating tons of log messages because I keep getting (and rejecting) tons of routes. Without asking the upstream to not advertise the full route table, is there something I can do on my end to limit the syslog messages I keep getting?



Feb  5 19:00:43  nap-r2-edge-2 rpd[82464]: RPD_RT_PREFIX_LIMIT_REACHED: Number of prefixes (4000) in table inet.0 still exceeds or equals configured maximum (4000)

Feb  5 19:02:43  nap-r2-edge-2 last message repeated 4 times

Feb  5 19:11:13  nap-r2-edge-2 last message repeated 17 times

Feb  5 19:11:43  nap-r2-edge-2 rpd[82464]: RPD_RT_PREFIX_LIMIT_BELOW: Number of prefixes (3999) in table inet.0 is now less than the configured maximum (4000)





Thanks,





Dan Farrell

Applied Innovations Corp.