A hands-on build of a VCF 9.1.1 lab on nested hosts, from empty ESX to a working Supervisor and VKS cluster, including what broke and how it was fixed. This is a 24-part series, and 0 posts are live.
Published
Coming up
- Preparing Nested ESX Hosts: Certificates and Thumbprints
- VCF Installer in a Lab: Appliance Placement, Offline Depot and a Spec from the Planning Workbook
- Walking the VCF Installer Wizard for a New Fleet
- Bring-up Milestones: What Each Stage Builds and How Long It Took
- Troubleshooting Bring-up 1: Thumbprint Mismatch and vSAN ESA Disk Eligibility
- Troubleshooting Bring-up 2: VPC Config Type and the NSX Version
- Troubleshooting Bring-up 3: LOQSE1 and P2KLT7
- Day-N Starts in VCF Operations: Verifying the Management Domain
- Host Commissioning in 9.1.1: Network Pools and the API Path for Nested Labs
- Creating the Workload Domain from VCF Operations
- After the Wizard: Static Host TEP Pool, NSX Agents and a Datacenter Rename
- VCF SSO Without Active Directory: Keycloak as an OIDC Provider
- One vSphere Client for Two Domains: vCenter Linking in VCF Operations
- Guided Edge Deployment from vCenter: Port Group, TEP Pool and the Edge Cluster
- Tier-0 Active/Standby and eBGP to the Lab Router, Verified from Both Sides
- Centralized Transit Gateway and IP Blocks: What Gets Advertised and What Does Not
- VPCs and Subnets from vCenter: Private, Public, DHCP, DNS and NTP
- Proving VPC Isolation with PowerCLI Test VMs and a Ping Matrix
- Lab Hygiene: Reverting Troubleshooting Changes on SDDC Manager
- Activating a Supervisor on VPC Networking: Design Choices, the Wizard and the First 50 Minutes
- Namespaces, Storage Policies and Kubernetes Releases: Getting VKS Ready for a Team
- A VKS Cluster in 8 Minutes from the vSphere Client, Then an App with a Load Balancer and Storage
- VMs Next to Containers: VM Service with cloud-init, and a Volume from the Local Consumption Interface
- Micro-segmentation Between VPCs with the Distributed Firewall, Proven with Traceflow