MAX numbers for BGP prefixes on ASR9001 (scalability)

[Mario Rosi]

Someone has the official numbers for IPv4 BGP prefixes, IPv6 BGP prefixes of ASR9001?

I would use 4x ASR9001 as ASBR in full mesh iBGP peering among themselves and for a double eBGP peering with two upstream ISPs; they than would generate a 0/0 towards the internal iBGP peers.

So, they would receive the FRT from the eBGP peer and 3 other copies from the iBGP peers.

This is the HW:

RP/0/RSP0/CPU0:MIX-ASR9K1-EDGE1#sh platform
Wed Aug 16 16:00:12.006 summertime
Node Type State Config State
-----------------------------------------------------------------------------
0/RSP0/CPU0 ASR9001-RP(Active) IOS XR RUN PWR,NSHUT,MON
0/0/CPU0 ASR9001-LC IOS XR RUN PWR,NSHUT,MON
0/0/0 A9K-MPA-2X10GE OK PWR,NSHUT,MON
0/0/1 A9K-MPA-2X10GE OK PWR,NSHUT,MON

RP/0/RSP0/CPU0:MIX-ASR9K1-EDGE1#sh diag summary
Wed Aug 16 16:00:44.162 summertime

NODE module 0/RSP0/CPU0 ASR 9001, Route Switch Processor with 8GB memory

NODE module 0/0/CPU0 ASR 9001, Modular Line Card

SPA 0/0/0 : ASR 9000 2-port 10GE Modular Port Adapter

RP/0/RSP0/CPU0:MIX-ASR9K1-EDGE1#sh ver
Wed Aug 16 16:00:59.245 summertime

Cisco IOS XR Software, Version 4.2.3[Default]
Copyright (c) 2013 by Cisco Systems, Inc.

ROM: System Bootstrap, Version 1.29(20120327:203546) [ASR9K ROMMON],

MIX-ASR9K1-EDGE1 uptime is 3 years, 14 weeks, 3 days, 16 hours, 46 minutes
System image file is "bootflash:disk0/asr9k-os-mbi-4.2.3.CSCuf38249-1.0.0/0x100000/mbiasr9k-rp.vm"

cisco ASR9K Series (P4040) processor with 8388608K bytes of memory.
P4040 processor at 1500MHz, Revision 2.0
ASR-9001 Chassis

2 Management Ethernet
8 TenGigE
8 DWDM controller(s)
8 WANPHY controller(s)
219k bytes of non-volatile configuration memory.
2940M bytes of hard disk.
4014064k bytes of disk0: (Sector size 512 bytes).

Thanks

Mario

[balaji.bandi]

check below thread may help you :

https://community.cisco.com/t5/xr-os-and-platforms/asr-bgp-routing-max-prefix/td-p/3916660

[M02@rt37]

Hello @Mario Rosi,

On your router bgp instance, choose a neighbor and under 'address-familly ipv4 unicast' enter the command maximum-prefix ? 

Is that give you a range ?

Max default value should be 1048576.

https://community.cisco.com/t5/xr-os-and-platforms/asr-bgp-routing-max-prefix/td-p/3916660

[Mario Rosi]

Hi M02@rt37 

PREVIEW

i get this number:

RP/0/RSP0/CPU0:MIX-ASR9K1-EDGE1(config-bgp-nbr)#address-family ipv4 unicast
RP/0/RSP0/CPU0:MIX-ASR9K1-EDGE1(config-bgp-nbr-af)#maximum-prefix ?
<1-4.294.967.295> maximum no. of prefix limit

so it means 4Bilion? mmmhhh.. it looks too much!

However, i was more interested on the limit per platform, totally...

[M02@rt37]

OK @Mario Rosi.

For an idea, in terms of routes (asr 9000 series, 5.3.x release):

 https://www.cisco.com/c/en/us/td/docs/routers/asr9000/software/asr9k_r5-3/routing/configuration/guide/b_routing_cg53xasr9k/b_routing_cg53xasr9k_chapter_010.html

[Mario Rosi]

M02@rt37 just to be sure, 

when it says 1.3 million of IPv4 routes, doesn't mean BGP prefixes in BGP table right? It means properly prefixes present in RIB, routing table, i mean, best path of BGP imported in routing table.

Because otherwise with almost 1M of BGP prefixes present in FRT, already two external peers towards two different IPSs, leaving from the same ASR9001, would cause the crash of it.

Mario

[M02@rt37]

Yes you're right @Mario Rosi, RIB view, not only BGP prefixes learned.

[Mario Rosi]

M02@rt37  good,

so it means much more BGP prefixes than 1.3M... so now the question is, how many BGP prefixes in global routing table the ASR9001 can keep? 

I'd have the necessity to understand if 4M of BGP prefixes (among which BGP best path algorithm would choose less than 1M entries to inject in RIB) can be managed by this guy...

[M02@rt37]

@Mario Rosi,

Please provide #show cef platform resource location output please.

[Mario Rosi]

#show cef platform resource location 0/0/CPU0
Wed Aug 16 18:16:27.171 Italy

Node: 0/0/CPU0
----------------------------------------------------------------
RPF_STRICT usage is same on all NPs

NP: 0 struct 9: RPF_STRICT (maps to ucode stru = 16)

Used Entries: 0 Max Entries: 262144
-------------------------------------------------------------

IP_LEAF_P usage is same on all NPs

NP: 0 struct 23: IP_LEAF_P (maps to ucode stru = 9)

Used Entries: 5465 Max Entries: 4194304
-------------------------------------------------------------

IP_LEAF_P usage is same on all NPs

NP: 0 struct 24: IP_LEAF_P (maps to ucode stru = 42)

Used Entries: 47 Max Entries: 2097152
-------------------------------------------------------------

NP: 0 struct 4: IP_LEAF (maps to ucode stru = 11)

Used Entries: 966761 Max Entries: 4194304
-------------------------------------------------------------

NP: 1 struct 4: IP_LEAF (maps to ucode stru = 11)

Used Entries: 966760 Max Entries: 4194304
-------------------------------------------------------------

TX_ADJ usage is same on all NPs

NP: 0 struct 12: TX_ADJ (maps to ucode stru = 5)

Used Entries: 24 Max Entries: 524288
-------------------------------------------------------------

NR_LDI usage is same on all NPs

NP: 0 struct 7: NR_LDI (maps to ucode stru = 13)

Used Entries: 133176 Max Entries: 2097152
-------------------------------------------------------------

TE_NH_ADJ usage is same on all NPs

NP: 0 struct 14: TE_NH_ADJ (maps to ucode stru = 7)

Used Entries: 8 Max Entries: 65536
-------------------------------------------------------------

RX_ADJ usage is same on all NPs

NP: 0 struct 13: RX_ADJ (maps to ucode stru = 4)

Used Entries: 30 Max Entries: 131072
-------------------------------------------------------------

R_LDI usage is same on all NPs

NP: 0 struct 6: R_LDI (maps to ucode stru = 12)

Used Entries: 148 Max Entries: 131072
-------------------------------------------------------------

L2VPN_LDI usage is same on all NPs

NP: 0 struct 16: L2VPN_LDI (maps to ucode stru = 27)

Used Entries: 24 Max Entries: 32768
-------------------------------------------------------------