Some diagram updates I’ve been itching to knock out. Diagram set updated for Mobility Optimized Networking (released in R140).
Bonus Files:
HCX Network Extension & Mobility Optimized Networking Diagrams
Some diagram updates I’ve been itching to knock out. Diagram set updated for Mobility Optimized Networking (released in R140).
Bonus Files:
HCX ⦿ DESIGN 
These are…awesome, thank you. Any chance you could post source material so these could be used as templates?
LikeLiked by 1 person
Added editables.
LikeLiked by 1 person
The like button isn’t enough to express my gratitude. Thank you Gabe! TIL about Graffle.
LikeLike
Awesome diagrams Gabe!! Worth a thousand words 🙂
I do have a question on the second last section (HCX Mobility Optimized Networking – Policy Routing via HCX NE Path) where the traffic flow between VM B to VM C (Policy Routed via HCX NE) is explained. Wouldn’t the red line finish on the VM Network Orange gateway interface on the on-prem side (10.5.0.1/24) to get to VM C?
Stay safe and healthy!
Thanks.
LikeLike
Oh that is absolutely right – I got lazy it seems 🤣. I’ll make an edit for that. Thanks Amit!
LikeLike
[…] reach other virtual machines and networks optimally, without tromboning or hair-pinning. I shared (MON diagrams and their editables) last week. HCX MON for NSX-T targets has a several key improvements over HCX PR for […]
LikeLike
[…] how is Mobility Optimized Networking working? Gabe Rosas over at hcx.design published some excellent networking diagrams that clearly explains MON architecture and network flows. The original Visio and OmniGraffle files […]
LikeLike
Hi Gabe, is there any documentation on the function of the /32 routes injected by HCX into NSX when NE with MON is enabled? I’m trying to understand how that works internally.
LikeLike
Hi Gabe. Great stuff. I am trying to wrap my head around this for a while and these diagrams help a lot. Just one additional questions with regards to the last scenario VMB to VMC. With the default setting of target router for VMB set to onprem this seems to be logical. But how does this work, if I set the target router to Cloud? I am aware that there are HCX policies in place which include the 10.0.0.0/8 prefix but I am a little confused about how these different parts come together.
LikeLike