[j-nsp] maximum-prefixes not enforced on option B gateways

Pierre Emeriaud petrus.lt at gmail.com
Wed Mar 28 06:55:50 EDT 2018


Gents,

I just noticed an issue on a couple of option B gateways in our
network. The max-prefix within routing-instances is not enforced. It's
although taken into account.

This is on M120 running 12.3R6-S3 (yes I know, ancient. No, can't upgrade).

me at router> show configuration routing-instances CUST-VRF-FOO
instance-type vrf;
interface sp-2/2/0.1451;
route-distinguisher 64544:123456;
vrf-import [ CUST-POL-IN-FOO GEN-POL-BOTH-REJECT ];
vrf-export [ CUST-POL-OUT-FOO GEN-POL-BOTH-ACCEPT ];
vrf-table-label;
routing-options {
    maximum-prefixes 2000 threshold 80;
    auto-export;
}

me at router> show route summary table CUST-VRF-FOO
Autonomous system number: 64544

CUST-VRF-FOO.inet.0: 2594 destinations, 3572 routes (2594 active, 0
holddown, 0 hidden)
Limit/Threshold: 2000/1600 destinations
                 BGP:   3572 routes,   2594 active


Mar 28 09:03:45  router rpd[1598]: RPD_RT_PREFIX_LIMIT_REACHED: Number
of prefixes (2593) in table CUST-VRF-FOO.inet.0 still exceeds or
equals configured maximum (2000)

CUST-VRF-FOO is not the only routing-instance affected, I have plenty
of them. I don't even have 1 holddown route on theses boxen.

Anyone aware of a PR on this? Is this a known limitation?

thanks
---
pierre


More information about the juniper-nsp mailing list