ARP Cache Limit on PA-500

Showing results for 
Search instead for 
Did you mean: 

ARP Cache Limit on PA-500

L4 Transporter


When is that the PA-500 will have an ARP cache limit of 1000?  I was promised during the launch of version 4.1 that the ARP cache limit had been increased to 1000 from 500 just to realise that it never happened. 

I am desperately waiting for something on this as clients are not at all happy with this and having a work around just to avoid this is not an easy task specially when someone else does the installation.

Can someone from PAN give me some kind of a hope on this please.  It would be very great of you.

Thank you



L6 Presenter

I guess you already contacted your sales rep regarding this?

A workaround should be to use a L3-switch in front of your PAN and setup a linknet between your PAN and the L3-switch.

Like so (just an example):

Clients: (shitload of clients :smileysilly:)

L3-switch int gi0/1: (interface towards the clients, this ip is the defgw for the clients)

L3-switch int gi0/2: (interface towards the PAN)

PAN int0: (interface towards the L3-switch).

then routing in the L3-switch:

ip route

This way the PAN will only need to keep track of a single ARP entry (the mac-address for the L3-switch ( while your L3 switch will keep track (ARP-wise) of all the clients.

Hi... Based on the example you've provided, can you please let me know on how to create a static route on the Palo Alto.


You'll find your virtual router(s) under Network - Virtual Routers. In the VR config you can define static routes.

I know about configuring where and how to configure static routes on the Palo Alto.  But was just wondering what would be the static route in terms of Destination and Next hop value which would obviously be on the external interface of the PA.

If your clients have and the L3-switch interface towards your PAN have ip (your PAN have at eth1/1 and the subnetmask for this linknet is /30 ( then your routing in your PAN should be setup as:

                  <entry name="ROUTE_CLIENTS">

Thank you for the information.  Will try it out when i get a chance.



what do you mean a linknet?



A linknet is what you call the small network (usually /30 or /29 if using redundancy) setup between two layer3 (routing) devices.

This linknet is to be able to setup nexthop addresses in each device routingtable.

For example... lets assume you (for some odd reason) have as client network ( -> which means 65534 mac addresses which the device which will be default gateway for all those must be able to handle.

However your PA can only do 1000 mac address per interface (or how large the limit now is).

So to fix this (except for doing a better segmentation than having 65k clients on the same layer2 network 😃 is to plugin a L3 device which can handle that many mac address on a single interface and then setup a linknet towards the PA device.

So the result will be:

PA <{]> L3 device []

If the PA have and the L3 device have then the routing table in the L3 device will be:

ip route nexthop

When looking in the PA you will see all the -> clients when looking at srcip, but when looking at mac address there will be only one - the mac address for (the mac address of the L3 device).

The PA must of course have a returning route like:

ip route nexthop

Version 5 will solve this issue... and I am glad.. Smiley Happy

Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

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!