Maximum size of prefix-sets?

[wj343]

Is there a maximum size for prefix-sets in IOS-XR? We recently began peering and have found some IRR entries generate prefix-sets of more than 60,000 lines. Will this be a problem for the router to handle?

As an aside, are there any recommendations to best practices when dealing with such large prefix sets? Having to trudge through a 100,000+ line "show running-config" filled with large prefix sets seems to be a bit annoying.

For reference, I am on IOS-XR 6.4.2

[smilstea]

We can easily handle hundreds of thousands of lines of RPL data, to check where you lie against a given systems maximum check 'show rpl maximum'.

As for parsing large configs, unlike IOS and NX, etc we have a much more advanced parser. You can issue show run router bgp or show run prefix-set for example. Another way to parse the config is with show run formal. What this does is for every line of config show you every keyword that goes before your line of config (every parent). So if you issue show run formal router bgp it would look like below:

RP/0/RSP1/CPU0:ASR-9006-B#show run formal router bgp
Tue Feb 16 20:07:12.822 UTC
router bgp 65000
router bgp 65000 bgp router-id 192.168.111.1
router bgp 65000 address-family ipv4 unicast
router bgp 65000 address-family vpnv4 unicast
router bgp 65000 neighbor 192.168.111.2
router bgp 65000 neighbor 192.168.111.2 remote-as 65000

You can just use show run formal, or show run formal <any regular feature / high level parent keyword> just like with show run, you can also use | i with show run formal.

Sam

[tbonepbradford]

I wonder if there's a better way to filter than prefix-set?   I am in a similar situation and am considering blocking bogons/martians/rfc1918/default and then allowing based on as-path created from bgpq3 entry from the IRR.  

bgpq3 -Xf XXX ASXXX:AS-EXAMPLE