Hello Jason, w.r.t. to spinning up dev and test environments, i guess you are talking about VMs for the DB, APP & WEB servers. does NSX spin up those VMs? or does it rely on vSphere?
Hello Jason, w.r.t. microsegmentation, dont VMs behave the same way as physical servers? i thought the only difference was that they were virtual? how and why do VMs communicate with each other by bypassing the firewall? can physical servers also do the same?
The key here is that the network card(s) on a virtual machine is provided in software. So software can intercept and analyse, block or allow traffic better than standard network cards which need firewalls and routers between them to block traffic. And most physical networks do not have physical firewall between each machine, usually only between different vlans.
It is possible to go straight to NSX, but it would certainly help to do DCV first, or at least have a good understanding of vsphere networking before you start.
you can also check the docs by going to the vmware website but replacing WWW. with DOCS. (I'm not showing an actual url as they can sometimes get videos/comments deleted)
@@jasonmeers Thanks for answering to my query. Can we get Palo Alto VM info such as publisher name, product details and MAC address from the NSX using CLI or REST API Or where to find/view the VM details in the NSX.
The thing you are describing is known in NSX terms as "Third Party Service Insertion", but I'm not an expert on it. If you search for that in the documentation you should be able to find more info on it.
Great video. I plan on watching this a few times to have in sink in.
Thank you. The concepts still apply, but NSX-T was released after this video was made so I would watch some of those afterwards too. Jason.
Once again, great stuff!
Thank you, thanks for taking the time to comment
Hello Jason, w.r.t. to spinning up dev and test environments, i guess you are talking about VMs for the DB, APP & WEB servers. does NSX spin up those VMs? or does it rely on vSphere?
Vsphere spins up the vms, and nsx does networking and security around them.
But blueprints can do this too with vRA (vrealize automation)
@@jasonmeers Thank you Jason. Your videos are most helpful. they're easy to follow. :)
You are great! Thanks so much!
Thank you very much. That presentation was for nsx-v, but lots of it still applies to the new nsx-t
Hello Jason, w.r.t. microsegmentation, dont VMs behave the same way as physical servers? i thought the only difference was that they were virtual? how and why do VMs communicate with each other by bypassing the firewall? can physical servers also do the same?
The key here is that the network card(s) on a virtual machine is provided in software.
So software can intercept and analyse, block or allow traffic better than standard network cards which need firewalls and routers between them to block traffic.
And most physical networks do not have physical firewall between each machine, usually only between different vlans.
@@jasonmeers Thank you Jason
Hello Jason, when you say nsx can run on bare metal, does that mean NSX run without vSphere?
Yes, nsx-t can run on bare metal, other hypervisors and cloud providers.
@@jasonmeers Thank you Jason
Hi Jason. Thanks for this video. Should someone who's new to VMware after with VCP-DCV or is it possible to go straight into NSX?
It is possible to go straight to NSX, but it would certainly help to do DCV first, or at least have a good understanding of vsphere networking before you start.
Hello Sir, need urgent help!! My question is, Can we create policy-based routing in NSX v for PAN VM?
Hi, Yes NSX-T and NSX-V can do policy based routing, but first can you explain PAN VM please? is that a panorama appliance running in a VM?
you can also check the docs by going to the vmware website but replacing WWW. with DOCS. (I'm not showing an actual url as they can sometimes get videos/comments deleted)
@@jasonmeers Thanks for answering to my query. Can we get Palo Alto VM info such as publisher name, product details and MAC address from the NSX using CLI or REST API Or where to find/view the VM details in the NSX.
The thing you are describing is known in NSX terms as "Third Party Service Insertion", but I'm not an expert on it. If you search for that in the documentation you should be able to find more info on it.
Thank you!!
You're welcome!
Thank you
You're welcome
Brilliant!
Thank you. This was recorded for nsx-v but the concepts are still the same for nsx-t
@@jasonmeers thanks. We have nsx-v and will be using it for a massive HCI project.
Very Nice
Thank you
Good video
Thank you