03-13-2013 01:27 PM
hi,
is there a maximum number of bgp route entries supported for the 5000 series ? does it support a full ipv4 routing table ? i cannot find any docs or data sheets with this kind of limits detailed...
thanks
03-13-2013 06:20 PM
Yes, and No.
I went through the same questions when I was considering using the PAN device instead of a dedicated edge router.
The following table shows the limits (sent to me by a Palo Alto SA about 6-8 months ago when I was planning for implementation, and still current according to the current spec sheet for the 5000 series platform)
| PA-5060 | PA-5050 | PA-5020 | PA-4060 | PA-4050 | PA-4020 | PA-2050 | PA-2020 | PA-500 | PA-200 |
Static routing | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
Forwarding table size (entries per device) | 64,000 | 64,000 | 64,000 | 20,000 | 20,000 | 10,000 | 5,000 | 2,500 | 1,250 | 1,000 |
Forwarding table size (entries per VR) | 64,000 | 64,000 | 64,000 | 20,000 | 20,000 | 10,000 | 5,000 | 2,500 | 1,250 | 1,000 |
Max route maps per VR | 50 | 50 | 50 | 50 | 50 | 50 | 50 | 50 | 50 | 50 |
Routing Peers (regardless of protocol) | 1,024 | 1,024 | 1,024 | 1,024 | 1,024 | 1,024 | 1,024 | 1,024 | 1,024 | 1,024 |
Since the current entire BGP table is somewhere around 440000 routes, the entire table is not going to fit into a PAN device - even a 5000 series - without some serious filtering.
Cheers.
03-13-2013 06:20 PM
Yes, and No.
I went through the same questions when I was considering using the PAN device instead of a dedicated edge router.
The following table shows the limits (sent to me by a Palo Alto SA about 6-8 months ago when I was planning for implementation, and still current according to the current spec sheet for the 5000 series platform)
| PA-5060 | PA-5050 | PA-5020 | PA-4060 | PA-4050 | PA-4020 | PA-2050 | PA-2020 | PA-500 | PA-200 |
Static routing | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
Forwarding table size (entries per device) | 64,000 | 64,000 | 64,000 | 20,000 | 20,000 | 10,000 | 5,000 | 2,500 | 1,250 | 1,000 |
Forwarding table size (entries per VR) | 64,000 | 64,000 | 64,000 | 20,000 | 20,000 | 10,000 | 5,000 | 2,500 | 1,250 | 1,000 |
Max route maps per VR | 50 | 50 | 50 | 50 | 50 | 50 | 50 | 50 | 50 | 50 |
Routing Peers (regardless of protocol) | 1,024 | 1,024 | 1,024 | 1,024 | 1,024 | 1,024 | 1,024 | 1,024 | 1,024 | 1,024 |
Since the current entire BGP table is somewhere around 440000 routes, the entire table is not going to fit into a PAN device - even a 5000 series - without some serious filtering.
Cheers.
03-14-2013 01:06 AM
thanks! very useful table 
01-15-2014 05:30 AM
Do you have any information regarding the max routes for the 3000 series?
01-15-2014 06:04 AM
In addition to above table for PA-3050 and PA-3020 :
| Forwarding table size (entries per device) | 5.000 | 2.500 | |
| Forwarding table size (entries per VR) | 5.000 | 2.500 | |
| Max route maps per VR | 50 | 50 | |
| Routing Peers (regardless of protocol) | 1.024 | 1.024 |
Kind regards,
-Kim.
01-16-2014 05:15 PM
They're the same as the equivalent 2000 series - from my understanding, the main difference between the 2000 and the 3000 is on the management plane, not the data plane - management is much improved on the 3000 (more RAM in the management plane setup), but everything else remains the same.
09-20-2021 12:18 PM
Is there an updates version of this table with 5200s?
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!
