topic Virtual router to virtual router communication in General Topics

Virtual router to virtual router communication

MGRashmi — Tue, 30 Apr 2019 08:16:37 GMT

Hi,

We have a setup in which a switch is used for interconnecting several virtual systems to a perimeter router. The switch is going end of life and needs to be replaced. Is it possible to replace this switch with a "Virtual router" in Palo Alto?

Below is the setup:

1. All virtual systems have their own virtual routers.

2. Default routes from the virtual systems are pointing to the corresponding SVIs in the switch

3. From the switch traffic gets routed to perimeter router

4. There are NAT IPs in each Vsys. Switch has reverse routes pointing to those NAT IPs to the particular interfaces of the vsys.

Query:

1. Is it possible to replace the switch with a new virtual router? Will the new virtual router be visible to all vsys?

2. If i select next hop as "Virtual router" while adding a static route, it does not allow me to choose an interface in the next hop vritual router. Will this work for static routes configured for NAT IPs in the next hop VR? And also for static routes?

In the diagram below, 192.66.2.2 is a NAT IP configured in vsys1. My question is if the "Switch with SVIs" is replaced by a new virtual router, will I be able to add routes for 192.66.2.2 pointing to next hop virtual router as "vsys 1" in it?

Re: Virtual router to virtual router communication

reaper — Tue, 30 Apr 2019 13:35:16 GMT

check out inter-vsys routing: https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClSVCA0

Re: Virtual router to virtual router communication

MGRashmi — Fri, 03 May 2019 10:06:37 GMT

Hi, Thanks for the link. The link talks about configuring an "external zone" for doing inter vsys routing. My query is slightly different. We are only choosing a next hop virtual router and not a specific interface in the next hop router. In such cases, will the route work for a NAT IP?

Re: Virtual router to virtual router communication

reaper — Fri, 03 May 2019 10:17:28 GMT

The "external" zone is used to indicate that the next hop is outside of the current vsys, it is not attached to an interface
The next hop vr then accepts a packet from the "external" zone and points it to an egress interface