Table of Contents

Local Routes Behavior

PAN-OS specific behavior for the openconfig-local-routing model.
The OpenConfig model for Static Routes differs from the model used in PAN-OS:
  • In PAN-OS static routes are organized in a flat list with a single next-hop member per route. If multiple next hops are needed for a given destination (prefix) then you must create multiple static routes.
  • In OpenConfig static routes are organized in a hierarchy containing a list of next-hops members per each destination.
  • PAN-OS requires each static route to have its own unique name while in OpenConfig the static route key is the destination.
  • The OpenConfig configuration only supports next-hop type IP addresses.
  • Local-aggregates are supported only if created with OpenConfig.
When rendering an existing PAN-OS configuration into OpenConfig some values like the next-hop index are synthesized using low collision hash functions. Static routes configured from the gNMI client contain metadata like the next-hop index must be stored somewhere in order to achieve consistent future responses and a unique name must be synthesized for each route in order for PAN-OS to accept the routes. For this reason, unique route name is automatically generated by using a fixed-length Base64 prefix encoding the metadata plus an optional route description.

Recommended For You