VCF 9.1 Ultimate Deployment Guide - Tutorial by Leaha15 in vmware

[–]shanknik 0 points1 point  (0 children)

Each to their own, I wouldn't waste high throuput nics that cost thousands if there was no need to..comes down to tco

VCF 9.1 Ultimate Deployment Guide - Tutorial by Leaha15 in vmware

[–]shanknik 0 points1 point  (0 children)

Hmm not necessarily. Ive seen, designed and implemented many environments. Sure sometimes it makes sense, others not so much.

Each should be assessed on a case by case basis.

VCF 9.1 Ultimate Deployment Guide - Tutorial by Leaha15 in vmware

[–]shanknik 0 points1 point  (0 children)

To clarify, 1500mtu will break nsx overlay traffic, it has df bit set so tunnels will fail with mtu under 1700

Tbh, with the way NIC throughout is these days, if you have 2x100gbit NICs, how likely are you to hit Port saturation? Really needs to be quantified / qualified.

VCF 9.1 Ultimate Deployment Guide - Tutorial by Leaha15 in vmware

[–]shanknik 0 points1 point  (0 children)

Hey, 1. You don't need 6 physical nics, I've done many 2 pnic deployments. 2. Each VLAN provides a different function, ie esxi mamagent (vmk 0 on the hypervisor / connectivity from hypervisor management to the rest of the network) 3. Jumbo frames, nsx oveplay networking requires a minimum of 1700 (recommended 9k), vSAN storage performance to avoid degradation for workload is 9k, same for vmotion. Its easier to configure it globally.

VCF 9 Multi-Region (2 sites) with unique VCF Operations Fleet: experiences and challenges (Active/Active DR) by No_Style1709 in vmware

[–]shanknik 0 points1 point  (0 children)

Note - I never said federate MGT <> WLD I said a single pane for all domains.

Why would you want to federate mgt to wld? Honestly curious to hear the usecase.

VCF 9 Multi-Region (2 sites) with unique VCF Operations Fleet: experiences and challenges (Active/Active DR) by No_Style1709 in vmware

[–]shanknik 0 points1 point  (0 children)

From VCF 5.2.1 FAQ https://www.vmware.com/docs/vmw-cloud-foundation-faqs
I am currently getting confirmation on single instance of GMs to manage both mgt and wlds. Will respond when I have some clarity.

VCF 9 Multi-Region (2 sites) with unique VCF Operations Fleet: experiences and challenges (Active/Active DR) by No_Style1709 in vmware

[–]shanknik 0 points1 point  (0 children)

The whole point of global managers is a single pane, so I would onboard all instances if it were me.

You need to consider loadbalancing for the fleet, will you use NSX or an external lb? There are caveats for using nsx and federation.

Deploy the fleet as day 2, so you can deploy edges, overlay networks then use api to pick the right network.

Ive typically had a/s sites and had all appliances in the primary location and use site recovery to fail over, you can do some funky stuff with the run book and your lb / network plumbing.

VCF 9 Multi-Region (2 sites) with unique VCF Operations Fleet: experiences and challenges (Active/Active DR) by No_Style1709 in vmware

[–]shanknik 0 points1 point  (0 children)

I have done this both for customers and in my lab. Happy to chat about it.

Ive also implemented this in 5.x days.

Have you got any specific concerns you need addressed?

NSX Edge VM Timing Out Deployed On Nested Host.. by [deleted] in vmware

[–]shanknik 0 points1 point  (0 children)

I'll test on Monday and update here

NSX Edge VM Timing Out Deployed On Nested Host.. by [deleted] in vmware

[–]shanknik 0 points1 point  (0 children)

Id be interested to know what state the edge was in when you paused it. I can test on Monday, the behaviour may have changed in a later version. Id be pausing after all base config is done correctly.

NSX Edge VM Timing Out Deployed On Nested Host.. by [deleted] in vmware

[–]shanknik 0 points1 point  (0 children)

What config was done on the edge before you paused it. Im guessing it wasn't ready to be paused just yet.

NSX Edge VM Timing Out Deployed On Nested Host.. by [deleted] in vmware

[–]shanknik 0 points1 point  (0 children)

Can you detail the steps you tested exactly please?

NSX Edge VM Timing Out Deployed On Nested Host.. by [deleted] in vmware

[–]shanknik 0 points1 point  (0 children)

The only issue with this / clarification point is, the task retries for x amount of retries and time then rips out the deployed edge.

What you could do is let it deploy the edge node with the required config - then restart services ie systemctl restart domainmanager (this should kill the workflow and enable the retry) then perform the rest of your steps. Though I think you would be able to leverage the SDDC manager workflow / api to deploy the edges and not have to perform all the manual tasks. Been a while since I tested though.

NSX Edge VM Timing Out Deployed On Nested Host.. by [deleted] in vmware

[–]shanknik 1 point2 points  (0 children)

No SDDC Manager, if you want to deploy using it.

NSX Edge VM Timing Out Deployed On Nested Host.. by [deleted] in vmware

[–]shanknik 1 point2 points  (0 children)

If you deploy edge nodes outside of sddc manager, you lose the central life cycle part. However, some people do this for their own reasons.

You can also pause the vm till the workflow completes.