Last week, I shared an example of how to create a new workload domain with VMware Cloud Foundation (VCF) using hosts with more than two physical NICs. In that example, I used NSX-V in the creation of the workload domain. Today, I’d like to provide an example of how you would do this for a NSX-T backed workload domain.
As support for multiple physical NICs (>2) is a newly
supported feature with the VCF 3.9.1 release, doing this requires the use of the
Continue reading NSX-T Backed Workload Domains with Multiple Physical NICs
With the VCF 3.9.1 release, support for hosts with multiple
physical NICs has been added. This allows you to dedicate specific traffic
across specific physical NICs to conform to your best practices. Let’s take a
quick look at how this is configured…
By default, VCF will use the first two physical NICs (vmnic0
and vmnic1) on a host for all traffic. When working with a host with multiple
physical NICs, you will need to define what the physical NICs are connected to
(VDS or N-VDS). The VDS or N-VDS will need to exist, of course.
Continue reading Multiple Physical NICs in VCF
Although VMware Cloud Foundation (VCF) will automatically
download the software bundles once connected to the Internet, there are times
that you may wish to manually inject the software bundles into the SDDC Manager
using the API.
After the initial deployment of VCF is completed, additional
bundles may be required to enable optional functionality. For example, the
bundles for Horizon, PKS, and vRealize Automation are optional and would be
downloaded and then installed as needed. Because these bundles can be quite
large and VCF downloads them in a serial fashion, it can be faster at times to inject
the bundles into VCF manually through the API.
Continue reading Manually Uploading VCF Bundles