Inter VR Routing

Reply
L1 Bithead

Inter VR Routing

We have a PA 3220 with two VRs, one VR is TEST and the other is VR is PROD.

Each VR has a public facing interface, eth1 is PROD Andy its IP Address is 103.143.195.245/32 and eth2 is TEST with an IP address of 166.206.187.82/32. There are internal and DMZ interfaces that belong to either VR.

I have a requirement for a user on the PROD to access a DEV environment in TEST. I’ve tried adding a static route to each VR making the other VR the next hop for the destination network and this is returning commit error.

has anyone done this before? 
both VRs are in the same vsys 

 

 

Spartan
Tags (1)
L6 Presenter

@Chopper  Could you please paste the exact error that you are getting ?

Mayur S.
L7 Applicator

Inter VR routing is doable as we use it here...  

 

MickBall_0-1608208590319.jpeg

 

L1 Bithead

@SutareMayur 

This is the error I am getting. The RL Server Network refers to a 10.15.6.0/29 subnet

Chopper_0-1608242922374.png

 

Spartan
L1 Bithead

...I figured it out, It appears that the inter-VR routing statement does not support network objects.  It only supports proper network addressing, 

Spartan
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!