Palo Alto Networks Knowledgebase: How Does Next Hop in Route Redistribution Profile Work?

How Does Next Hop in Route Redistribution Profile Work?

Created On 08/05/19 19:57 PM - Last Updated 08/05/19 20:11 PM
Mobile Network Infrastructure

This document describes a next hop field in the route redistribution profile works in conjunction with interface and destination addresses.



In a route redistribution profile, select the source type (for example, static, connect) desired to redistribute. There are three more optional filters that can be configured (interface, destination and next hop). If one or more interfaces/destination/next-hop is configured, then static routes(in this example) which have those interfaces "AND" those destination addresses "AND" those next hops will only be used for redistribution.


For example, static routes are being redistributed. Interfaces, destination and next hop are configured, as shown below:

Next hop.png


Logic to filter the routes will be like this:

(Static routes) AND (eth1/3 or eth1/4) AND ( or or or ) AND (next-hop or next-hop


See the following static routes configured in the VR:

Static routes.png


Output of OSPF LSDB where this redistribution profile was used in export rules:

> show routing protocol ospf lsdb


VIRTUAL ROUTER: default (id 1)


VR Area ID       Orig RTR ID     LS ID              LSA Type            Seq Number CheckSum

  1        type-1 (Router)     0x80000325 0x00004C0E

  1        type-1 (Router)     0x80000003 0x0000E0AA

  1        type-1 (Router)     0x80000332 0x00008ABD

  1     type-2 (Network)    0x8000031F 0x00003A77

  1          type-5 (External)   0x80000003 0x0000FE7C             <<<<< redistributed route

  1         type-5 (External)   0x80000003 0x0000745E             <<<<< redistributed route

  1        type-5 (External)   0x80000003 0x000080FD             <<<<< redistributed route


Notice that is not being redistributed as its next hop address doesn't match the filter.


owner: dreputi

  • Print
  • Copy Link

Choose Language