Azure Virtual Network Basics-Part2: VNet Peering, User Defined Routes, and Network Virtual Appliance
HTML-код
- Опубликовано: 14 окт 2024
- In the previous session we learnt about virtual network peering, which enables you to seamlessly connect two or more Virtual Networks in Azure. In this session of the series, we will learn about Network Virtual Appliances, and User Defined Routes and how are they useful in the hub and spoke network architecture and in creating the DMZ scenario.
Part-1: • Azure Virtual Network ...
=========================================================
Twitter - @mstechtrainings
Facebook - Microsoft Azure Enthusiasts
LinkedIn - / neeraj-kumar-csm-mcts-...
Blog - www.azure-trai...
=========================================================
#VirtualNetwork #VirtualNetworkPeering #VNetPeering #NVA #UDRs #UserDefinedRoutes #NetworkVirtualAppliance #HubandSpoke #AzureVirtualNetwork #DMZ #UDRs #DemilitarizedZone 
Наука
I had a different environment and Azure support themselves couldn't tell me what was wrong. They told me that it was an issue with my NVA but even if I had built out the routes, my UDR was incorrect and it is because of YOU!! Because of your knowledge that I was able to fix the issue!! Thank you! You should have a buy a cup of coffee link!
Very nice explanation! Like they way you show it with RRAS as a NVA! But the second part with the Azure Firewall was not correct in my opinion. Yes: It was created and did its thing. But: The routing rules are defined as targets. So it is not „from the Internet“. It is: „To the Internet“. It is mentioned as well as the target ip range. You would be able to connect into the VMs on spoke subnets - but the traffic couldn’t be routed back to the Internet because of the UDRs. This is why you couldn’t connect to the spoke VMs. If you would go to one of the spoke VMs, your can‘t browse the Internet without creating an outgoing rule on the Azure Firewall first.
Let me know if I got anything wrong about that.
But again: It was the best way to explain a NVA is in the first part of the video!
Superb explanation without any confusion and lag. Keep up the good work. We have to be very conscious to understand this. It automatically grabs the concentration.
Thank you so much❤
So nice of you
Great. Sir did you palnning to start Security in Azure ?
Yes, I am planning to create content on security
Excellent Explination. My question is that in the HUB Vnet, why you creat and what is the use two subnets and VMs?, what is the use for that? I understand DMZ. Please explain.
Great explanation Sir. Do you have full training material or can i subscribe to your lectures ? Do you do one to one training over the internet ? Thank you
That was superb! Thank you
Glad you liked it!
Love it. Keep up the good work!
Thanks! Will do!
Thank you so much for amazing content !!
My pleasure!
Hello Sir, Why we are not simply peering Vnet B and C together? Thats easier than passing traffic through Vnet A NVA. No need for UDR, NVA in that case. Correct me if am wrong.
Great Question! We could have peered the VNets B and C directly, but this will work for a very small demo scenario. What when networks is distributed within different regions and you need more centralized control and it s a hub and spoke architecture?
@@AzureTrainingSeries thank you sir for the response. But I was able to peer two vnets in different regions. I dont think region is a problem. But yes, to get more control on hub and spoke architecture NVA is required. By the way i got some errors when i made my NVA server to RRAS. I am not able to do that. So planning to keep only an AZ FW and passing routes through that if possible. Not sure.
What happens if i have a firewall in hub and i route all my traffic to the firewall for traffic going to another vnet
Good things
Thank You!