Virtual Router - Palo Alto Networks FireWall Concepts Training Series

Fully separating traffic is easy with the Next-Generation FireWall. While with other vendors you might need dedicated virtual systems, with Palo Alto Networks just adding another virtual router is enough. In this Palo Alto Networks Training Video, we will show you the concept including inter VR routing.
Security Best Practices Training for Palo Alto Networks - videos will be soon published on our webpage, sign up on bit.ly/2yakige and we will let you know once they are available
Security Best Practices Checklist for Palo Alto Networks Next-Generation FireWalls - download from our blog www.consigas.com/blog/security...
Follow us on:
➜ LinkedIn bit.ly/consigaslinkedin
➜ Twitter / consigascom

[@Arkansmith]

Appreciate the video. Helped a lot.

[@HughJass-jv2lt]

this was VERY helpful

[@vusandlovu5401]

Good trainers from Consigas......@domagoj was my trainer in London he is great......

[@Consigassecurity]

Thanks Vusa

[@freddycalderon9092]

Great videos but would be greater if you can do videos on configuration on the topic. Just a thought

[@joaoayres831]

Perfect

[@sajjadanwer8908]

it would be better to do configuration along with theory ,

[@ramber1021]

agreed!

[@AshfaqAhmad]

That's a very nice explanation of Vsys.

[@oneilmatlock8321]

For Production and Pre-Production L3 interfaces, could they be the same IP address? Want to keep server VMs the same IP address and default gateway when moving in and out of the two environments.

[@kevindall5268]

Oneil Matlock Yes. IP address assigned to the interface can be the same IP. The interface itself will have to be different. Does that make sense?

[@w1jumpmaster]

So if the Production and Pre-Production are in the same IP subnet, the Managements are different, If I tried to connect to something across the IVRL, then it would be the same IP ? If you are going to have IVRL, then you need different subnets all the way around

[@kevindall5268]

Steve Holloway - No. The management subnets are only connected at the VR. The production L3 interface is not known by the PreProd VR and will therefore only route to the interface for the production environment because that is what the production VR knows that subnet to live. Does that make sense?

[@tripleceas]

You lost me at rooter.