Academy/Holodeck Lab Setup & Operations/Dual-Site Holodeck Deployment
This lab targets VCF 9.0.2

Dual-Site Holodeck Deployment

VCF 9.0.2Advancedarchitectvcdx⏱ 240 min

Holodeck 9.0.2 dual-site sequence: New-HoloDeckNetworkConfig for Site a and Site b, Set-HoloRouter -dualsite (separate VRF per site), New-HoloDeckInstance -Site a, then -Site b in a new pwsh tab after importing the config. Site B uses 10.2.0.0/20 and VLANs 40-58 by default. Requires the dual-site resource row (for example VCF 9.0 with Automation: 48-64 CPU, 768 GB RAM, 2.5 TB). Source-checked 1 Oct 2026 against the Holodeck 9.0.2 documentation at vmware.github.io/Holodeck/9.0.2/ (index: Holodeck Environment Overview, Holorouter Overview, Concepts, Pre-requisites, Deployment, Post Deployment, Day 2 Operations, How To; cmd_reference; FAQ) and, where VCF behaviour is described, the VCF 9.0.1 documentation. In Holodeck 9.x the toolkit is a PowerShell module built into the HoloRouter OVA (Photon OS): the operator SSHes to the HoloRouter, runs pwsh, and works under /holodeck-runtime. There is no Windows HoloConsole, no C:\Holodeck path, no -ConfigFile parameter and no separate Prepare phase. Rewritten for v8.2.2 after the 360-degree audit.

Objectives

  • Plan the dual-site topology with the documented defaults (Site A 10.1.0.0/20, VLANs 0 and 10-25; Site B 10.2.0.0/20, VLANs 40-58) or custom /20 CIDRs and VLAN starts, and size the host from the dual-site requirement row
  • Execute the documented dual-site sequence: New-HoloDeckNetworkConfig -Site a / -Site b, Set-HoloRouter -dualsite, New-HoloDeckInstance -Site a, Import-HoloDeckConfig and New-HoloDeckInstance -Site b in a second pwsh session
  • Validate inter-site routing on the HoloRouter (L3 routing between the sites' VLANs, separate VRF tables) and bidirectional reachability between the two management planes
  • Validate both management planes through their documented endpoints (site-a and site-b FQDNs) and record the two independent VCF Instances
  • Map the dual-site lab to production multi-site designs using correct vSAN stretched-cluster facts (L2 or L3 between data sites, witness at a third site, preferred-site behaviour) in RCAR form

Prerequisites

A HoloRouter with the Holodeck 9.0.2 module, binaries staged for 9.0.2.0, and either a clean state (preferred: no instance yet) or a Site A instance deployed with the default network configuration. Physical capacity per the dual-site row (VCF 9.0 with Automation and vSAN OSA: 48 CPU, 768 GB RAM, 2.5 TB).

Prior labs: holodeck-02

Required skills:

  • Holodeck configuration and deployment (holodeck-01, 02)
  • IP subnetting and VLAN planning
  • VCF multi-instance concepts (vcp-admin-10)
  • vSAN stretched cluster and multi-site design fundamentals
📸 Starting State: S3-9x — Management Domain Deployed (VCF 9.x)

Lab Environment

One HoloRouter serving two sites on one trunk port group: Site A (10.1.0.0/20, VLANs 0 and 10-25) and Site B (10.2.0.0/20, VLANs 40-58), each with its own nested management domain (4 hosts, VCF Installer, SDDC Manager, vCenter, NSX, VCF Operations). The HoloRouter routes between the sites' VLANs and keeps a separate VRF per site after Set-HoloRouter -dualsite.

Important

Both sites run on one physical host behind one HoloRouter. They are two independent VCF Instances that share a router; they are not a stretched cluster and not a federated NSX. Design mapping in Task 5 must say so.

Mermaid source
graph LR
  HR[HoloRouter: VRF-a + VRF-b, L3 routing between sites, DNS site-a.vcf.lab and site-b.vcf.lab]
  subgraph A[Site A 10.1.0.0/20 VLANs 0,10-25]
    A1[esx-01a..04a] --- AM[vc-mgmt-a, sddcmanager-a, nsx-mgmt-a, ops-a]
  end
  subgraph B[Site B 10.2.0.0/20 VLANs 40-58]
    B1[esx-01b..04b] --- BM[vc-mgmt-a.site-b.vcf.lab, sddcmanager-a.site-b.vcf.lab, nsx-mgmt-a.site-b.vcf.lab, ops-a.site-b.vcf.lab]
  end
  HR --- A
  HR --- B

IP Addressing

NetworkPurposeVLAN
10.1.0.0/20Default Holodeck Site A master CIDR, subdivided by New-HoloDeckNetworkConfig into the Site A subnets (management, vMotion, vSAN, host overlay, edge uplinks, and others)VLANs 0 and 10-25 (Site A default)
10.2.0.0/20Default Holodeck Site B master CIDR (dual-site only)VLANs 40-58 (Site B default)
<external management network>HoloRouter external management IP (DHCP or static, set at OVA deployment); the only external IP a Holodeck environment needsExternal port group

Credentials

SystemUsernamePassword
HoloRouter (SSH and pwsh)rootSet in the OVA Additional settings at deployment
HoloRouter webtop(no authentication in 9.0.2)http://<holorouter-ip>:30000; the docs warn not to expose it externally
VCF Installeradmin@localHolodeck documented default (Post Deployment table)
VCF OperationsadminHolodeck documented default (Post Deployment table)
Management vCenteradministrator@vsphere.localHolodeck documented default (Post Deployment table)
SDDC Manageradministrator@vsphere.localHolodeck documented default (Post Deployment table)
Management NSXadminHolodeck documented default (Post Deployment table)
Nested ESX hostsrootHolodeck documented default (Post Deployment table)

Tasks

Task 1 Plan the dual-site topology and addressing

Manageability

The documentation fixes the shape: two /20 CIDRs, two VLAN ranges with minimum sizes, one HoloRouter with a VRF per site. Planning is choosing defaults or custom values and checking capacity.

Step 1

Record the documented defaults: Site A 10.1.0.0/20 with VLANs 0 and 10 through 25; Site B 10.2.0.0/20 with VLANs 40 through 58. Custom values: each CIDR must be a /20; -VLANRangeStart is the first VLAN ID of the range (not an offset), with at least 16 consecutive valid IDs for Site A and 19 for Site B; -DNSDomain defaults to vcf.lab (FQDNs end in site-a.vcf.lab and site-b.vcf.lab).

Default or custom CIDR/VLAN/DNS plan written for both sites.
Step 2

Size from the dual-site column of the requirement tables: VCF 9.0 with Automation and ESA 64 CPU / 768 GB / 2.5 TB; with OSA 48 CPU / 768 GB / 2.5 TB; VVF 9.0 24 CPU / 512 GB / 2 TB; VCF 5.2 32 CPU / 1 TB / 4 TB; plus the HoloRouter. Decide management-only per site to fit.

Capacity check passed for two management-only instances (or the plan reduced).
Step 3

Confirm the trunk port group allows both VLAN ranges (VLAN 4095 trunk does; on a cluster target the physical switches must carry 0, 10-25 and 40-58 or your custom ranges).

Trunk coverage confirmed for both sites.
Step 4

Decide the deployment order and sessions: the documentation runs New-HoloDeckInstance -Site a, then opens a new pwsh tab, imports the config and runs New-HoloDeckInstance -Site b. Plan two SSH sessions (or a terminal multiplexer) on the HoloRouter.

Session plan written.
Step 5

Draw the topology: one HoloRouter with VRF-a and VRF-b, two sites with their management planes and FQDN suffixes, the external workstation routes to both /20s.

Topology diagram saved.

Validation Gate

Check: CIDR/VLAN/DNS plan, capacity check, trunk coverage, session plan and diagram complete.

Expected: A dual-site plan consistent with the documented sequence.

Common Errors

VLANRangeStart treated as an offset
Cause: Misreading the parameter.
Fix: It is the first VLAN ID; defaults are 10 (Site A) and 40 (Site B).
Custom CIDR not /20
Cause: Wrong prefix length.
Fix: Use /20 CIDRs for both sites.

Task 2 Execute the documented dual-site sequence

Manageability

The order matters: network configuration for both sites, then the HoloRouter in dual-site mode, then the two instances. Custom values must be repeated on every cmdlet or the defaults overwrite them.

Step 1

SSH to the HoloRouter, run pwsh and create (or import) the configuration: New-HoloDeckConfig -Description 'dual-site' -TargetHost <target> -Username <u> -Password <p> (or Import-HoloDeckConfig -ConfigID <id>). One config per deployment still applies; the dual-site sequence is one deployment with two sites.

$config loaded.
Step 2

Generate the network configuration for both sites. Defaults: New-HoloDeckNetworkConfig -Site a -MasterCIDR 10.1.0.0/20 then New-HoloDeckNetworkConfig -Site b -MasterCIDR 10.2.0.0/20. Custom: add -VLANRangeStart <start> (and -DNSDomain) to each.

New-HoloDeckNetworkConfig -Site a -MasterCIDR 10.1.0.0/20
New-HoloDeckNetworkConfig -Site b -MasterCIDR 10.2.0.0/20
Subnets, VLANs, IP pools and BGP configuration generated for both sites; Get-HoloDeckSubnet -Site b | ft -AutoSize lists Site B subnets on VLANs 40-58.
Step 3

Configure the HoloRouter for dual site: Set-HoloRouter -dualsite (separate VRF tables for each site, DNSMASQ and FRR configured). If you use custom CIDRs, also pass -CIDR with both ranges as the command reference shows.

Set-HoloRouter -dualsite
HoloRouter configured for both sites; Get-HoloDeckAppNetwork -Site b lists Site B appliance FQDNs under site-b.vcf.lab.
Step 4

Deploy Site A: New-HoloDeckInstance -Version 9.0.2.0 -InstanceID holoa -Site a -ManagementOnly -vSANMode OSA -DepotType Online (custom networking: add -CIDR <site-a-cidr> -VLANRangeStart <site-a-start>). Answer the pre-check prompts as in holodeck-02.

New-HoloDeckInstance -Version 9.0.2.0 -InstanceID holoa -Site a -ManagementOnly -vSANMode OSA -DepotType Online
Site A deployment running.
Step 5

Open a second SSH session to the HoloRouter, run pwsh, Import-HoloDeckConfig -ConfigID <id>, and deploy Site B: New-HoloDeckInstance -Version 9.0.2.0 -InstanceID holob -Site b -ManagementOnly -vSANMode OSA -DepotType Online (custom networking: -CIDR <site-a-cidr>,<site-b-cidr> -VLANRangeStart <site-a-start>,<site-b-start>, both sites' values as the documentation shows).

Import-HoloDeckConfig -ConfigID <id>
New-HoloDeckInstance -Version 9.0.2.0 -InstanceID holob -Site b -ManagementOnly -vSANMode OSA -DepotType Online
Site B deployment running in parallel.
Step 6

Monitor both runs (phases as in holodeck-02). The documented management-only time is 4-5 hours per site; running both concurrently loads the host, so expect longer.

Both deployments complete successfully.
Step 7

If a site fails: re-run its exact command in its session (idempotent resume). If the networking must be rebuilt, Reset-HoloRouter followed by Set-HoloRouter -dualsite affects both sites: plan that.

Resume path understood for a two-site deployment.
Step 8

Record both instances: Get-HoloDeckInstance -InstanceID holoa and -InstanceID holob.

Two instance records with components, networking and state.
Step 9

From the outer layer, snapshot the HoloRouter and both instance VM sets (Stop-HoloDeckInstance each first) as holodeck-06-deployed.

Snapshot set exists; both instances restarted.

Validation Gate

Check: Network configs for a and b, Set-HoloRouter -dualsite, both New-HoloDeckInstance runs completed in separate sessions, two instance records, snapshot.

Expected: Two nested management domains behind one HoloRouter.

Common Errors

Site B deployed with Site A networking
Cause: Custom CIDR/VLAN values not repeated on New-HoloDeckInstance.
Fix: Pass -CIDR and -VLANRangeStart with both sites' values to the Site B command (documentation note).
Second session has no $config
Cause: $config is per session.
Fix: Import-HoloDeckConfig -ConfigID <id> in the new tab first.
Set-HoloRouter -dualsite run after the Site A instance existed
Cause: Order changed.
Fix: Follow the documented order; a router rebuild (Reset then Set -dualsite) disrupts Site A.
Host overloaded; nested hosts crash
Cause: Two concurrent deployments beyond the dual-site requirement row.
Fix: Deploy the sites one after another, or reduce options.

Task 3 Validate inter-site routing and reachability

Availability

The HoloRouter is the only path between the sites and the only path out. Prove routing in both directions before trusting any cross-site test.

Step 1

On the HoloRouter compare the two sites: Get-HoloDeckSubnet -Site a and -Site b (VLAN sets 0,10-25 vs 40-58; subnets in 10.1.0.0/20 vs 10.2.0.0/20), Get-HoloDeckAppNetwork -Site a and -Site b, Get-HoloDeckBGPConfig -Site a and -Site b (different edge AS numbers per site).

Two consistent, non-overlapping network inventories.
Step 2

From a Site A nested host console (or the webtop) ping the Site B management gateway and vc-mgmt-a.site-b.vcf.lab; from a Site B host do the reverse. The HoloRouter provides L3 routing between the VLANs of Site a and Site b (documentation, Holorouter Overview).

Bidirectional reachability across sites through the HoloRouter.
Step 3

Resolve both sites' names from the HoloRouter: Get-HoloDeckDNSConfig -FQDN vc-mgmt-a.site-a.vcf.lab and -FQDN vc-mgmt-a.site-b.vcf.lab; from your workstation (holodeck-04 DNS) resolve both.

Both suffixes resolve from the HoloRouter and the workstation.
Step 4

Add the Site B route on your workstation or site router (10.2.0.0/20 via the HoloRouter external IP) and open the Site B consoles by name.

Site B consoles reachable from the workstation.
Step 5

Record the VRF behaviour you can observe: inter-site routing works, each site keeps its own address plan and DNS zone, and both share the HoloRouter's single external IP and firewall.

Routing observations recorded.
Step 6

Measure cross-site latency between a Site A and a Site B nested host (same physical host, so sub-millisecond) and note why this is not representative of real inter-site links (Task 5).

Latency figure recorded with the caveat.
Step 7

Document the failure domain: one HoloRouter and one physical host serve both sites; a HoloRouter reboot (for example from Remove-HoloDeckInstance -ResetHoloRouter) takes both sites' routing and DNS down.

Shared failure domain recorded.

Validation Gate

Check: Network inventories compared; bidirectional reachability; DNS for both suffixes; workstation access to Site B; VRF observations; latency and shared-failure-domain notes.

Expected: Inter-site connectivity proven and its limits understood.

Common Errors

Site B names resolve but Site B IPs are unreachable from the workstation
Cause: Missing route for 10.2.0.0/20.
Fix: Add the second static route.
Sites cannot reach each other
Cause: Set-HoloRouter -dualsite not run, or run before the network configs.
Fix: Re-run the documented order.

Task 4 Validate both management planes

Availability

Two instances means two of everything. Validate each independently with the documented endpoints, then confirm they are independent VCF Instances (two SDDC Managers, two VCF Operations) rather than one fleet.

Step 1

Site A: open https://vc-mgmt-a.site-a.vcf.lab, https://sddcmanager-a.site-a.vcf.lab, https://nsx-mgmt-a.site-a.vcf.lab and https://ops-a.site-a.vcf.lab; run the holodeck-02 Task 4 and 5 checks.

Site A management plane healthy.
Step 2

Site B: the documentation says to replace site-a with site-b in each FQDN: https://vc-mgmt-a.site-b.vcf.lab, https://sddcmanager-a.site-b.vcf.lab, https://nsx-mgmt-a.site-b.vcf.lab, https://ops-a.site-b.vcf.lab; repeat the checks.

Site B management plane healthy.
Step 3

Confirm independence: each site has its own SDDC Manager, vCenter, NSX Manager cluster and VCF Operations; neither knows about the other. Record that making them one fleet would mean integrating Site B into Site A's VCF Operations (vcp-admin-10) and that Holodeck does not do this for you.

Independence recorded; fleet integration identified as a separate exercise.
Step 4

Compare BOM versions in both VCF Operations inventories (same -Version, so identical) and note how two independently deployed instances can drift over time without fleet-level lifecycle.

Versions recorded; drift risk noted.
Step 5

Run Stop-HoloDeckInstance -InstanceID holob, verify Site A is unaffected (routing, DNS, consoles), then Start-HoloDeckInstance -InstanceID holob.

Site A unaffected by a Site B power cycle; Site B returns.
Step 6

Repeat in the other direction for Site A.

Site B unaffected by a Site A power cycle.
Step 7

Record the time to a healthy state for each site after Start-HoloDeckInstance.

Cold-start times for both sites.
Step 8

Take the snapshot set holodeck-06-validated.

Snapshot set exists.

Validation Gate

Check: Both management planes validated; independence recorded; cross-site power-cycle tests passed; cold-start times recorded; snapshot taken.

Expected: Two healthy, independent VCF Instances on one Holodeck environment.

Common Errors

Opening sddcmanager-a.site-b.vcf.lab shows Site A
Cause: DNS cache or wrong record.
Fix: Flush DNS; check Get-HoloDeckDNSConfig for the site-b record.
Expecting one VCF Operations to show both sites
Cause: Fleet integration assumed.
Fix: Integrate Site B into Site A's VCF Operations as in vcp-admin-10 if you want one fleet.

Task 5 Design exercise: map the dual-site lab to production multi-site architecture (RCAR)

Availability

The lab gives you two instances behind one router. Production multi-site designs are different things: a vSAN stretched cluster within one instance, two instances in one fleet, or NSX Federation across instances. The exercise is to map correctly and to state the vSAN stretched-cluster facts the way the documentation does.

Step 1

Write down what the lab is: two independent VCF Instances sharing one HoloRouter and one physical host, with inter-site L3 routing. Write down what it is not: not a stretched cluster, not NSX Federation, not a fleet (until integrated).

Lab-versus-production statement.
Step 2

Stretched cluster facts from the VCF 9.0.1 documentation: vSAN stretched clusters support Layer 2 or Layer 3 between the two data sites (and L3 to the witness); the witness host resides at a third site; when the inter-site link fails, vSAN continues on the preferred site (the witness forms quorum with it) and vSphere HA restarts the secondary site's VMs there; objects become non-compliant but data stays available if the witness is lost. Write these as the requirements a stretched design must meet.

Correct stretched-cluster requirement list (L2 or L3, third-site witness, preferred-site behaviour).
Step 3

Multi-instance facts: two VCF Instances can be managed as one fleet by one VCF Operations (vcp-admin-10); consistent DFW across instances is NSX Federation (Global Manager, maximum 150 ms between locations); VCF Operations and VCF Automation connect to one identity broker (vcp-admin-04).

Multi-instance requirement list.
Step 4

Build the RCAR for a two-site production design of your choice (active-active stretched management cluster, or two instances in one fleet with DR orchestration): Requirements (RPO/RTO, SSO, consistent security), Constraints (latency: stretched vSAN under 5 ms RTT between data sites, witness under 200 ms; Federation under 150 ms; bandwidth; the three-host minimum per site), Assumptions (third site for the witness, DNS/NTP per site, identity provider), Risks (inter-site link failure, witness loss, split management plane).

RCAR with at least five items per category.
Step 5

Write the design decision the lab cannot test: inter-site latency and bandwidth. Record the lab's sub-millisecond latency and state how you would test the real link (latency, loss, MTU) before committing a stretched design.

Untestable-in-lab list with the production test plan.
Step 6

Write the failure scenarios for your design in a table (data-site failure, inter-site link failure, witness failure, management vCenter failure) with the documented behaviour and recovery for each, avoiding any 'read-only mode' or 'both sites keep writing' language.

Failure table consistent with the documentation.
Step 7

Record how the lab helps and hinders: it exercises two management planes and inter-site routing; it cannot show stretched vSAN, Federation, real latency or independent power/cooling domains.

Helps/hinders list.
Step 8

Prepare two defence answers: 'Why not stretch the management cluster across these two sites?' and 'What does one HoloRouter for two sites teach you about shared infrastructure services in production?'

Two concise answers written.
Step 9

Take the final snapshot set holodeck-06-complete and decide whether to keep both sites (resource cost) or remove Site B with Remove-HoloDeckInstance from its session.

Snapshot taken; keep/remove decision recorded.

Validation Gate

Check: Lab-versus-production statement; correct stretched-cluster and multi-instance facts; RCAR; untestable list; failure table; helps/hinders; two defence answers; snapshot.

Expected: A defensible mapping from the dual-site lab to production designs.

Common Errors

Claiming stretched vSAN needs L2 between sites
Cause: Outdated assumption.
Fix: The documentation supports L2 or L3 between data sites (L3 to the witness).
Placing the witness in a data site
Cause: Misunderstanding fault domains.
Fix: The witness host resides at a third site.
Describing a partition as both sites writing or read-only
Cause: Wrong failure model.
Fix: Preferred site plus witness keep serving; the secondary site's VMs are restarted on the preferred site by vSphere HA.
Treating the lab's two instances as a stretched cluster
Cause: Model confusion.
Fix: They are two independent instances; map accordingly.

Final Validation

Two nested VCF 9.0.2 management domains deployed with the documented dual-site sequence behind one HoloRouter; inter-site routing and both management planes validated; the design exercise maps the lab correctly to production multi-site options with accurate vSAN stretched-cluster facts.

✓ Plan → Default or custom /20 CIDRs and VLAN starts (16/19 IDs), dual-site sizing, session plan

✓ Sequence → New-HoloDeckNetworkConfig a and b; Set-HoloRouter -dualsite; New-HoloDeckInstance -Site a and -Site b in separate sessions

✓ Routing → Bidirectional inter-site reachability; both DNS suffixes; workstation routes to both /20s

✓ Management planes → Both sites' consoles healthy; independence confirmed; power-cycle tests passed

✓ Records → Get-HoloDeckInstance for holoa and holob; cold-start times; snapshots

✓ Design exercise → Correct stretched-cluster facts; RCAR; failure table; untestable list; defence answers

✓ Failure domain → Shared HoloRouter and host recorded as the lab's single failure domain

✓ Decision → Keep or remove Site B recorded with resource cost

Cleanup / Restore

Snapshot: holodeck-06-complete

• Keep both sites or remove Site B with Remove-HoloDeckInstance from a session with the config imported

• Remove the Site B workstation route if Site B is removed

• Keep the RCAR and failure table for the design defence

Design Reflection (VCDX)

Multi-site is where candidates most often state wrong fundamentals. The lab lets you practise two management planes and inter-site routing; the defence requires you to say precisely what a stretched vSAN cluster needs (L2 or L3 between data sites, witness at a third site, preferred-site behaviour on partition), what NSX Federation adds and constrains (150 ms), how two instances become one fleet, and why shared infrastructure services (one router, one DNS) are a single failure domain. Separate what the lab proved from what only a real inter-site link can prove.

Requirements

  • Two /20 CIDRs and two VLAN ranges with the documented minimum sizes
  • HoloRouter in dual-site mode before either instance
  • Inter-site L3 reachability and DNS for both suffixes
  • Both management planes validated independently
  • Design mapping with correct stretched-cluster and Federation facts
  • Failure scenarios documented per the VCF documentation
  • Snapshots before destructive steps

Constraints

  • Dual-site resource row (for example 48 CPU / 768 GB / 2.5 TB for VCF 9.0 OSA with Automation)
  • Custom values must be repeated on New-HoloDeckInstance
  • Reset-HoloRouter affects both sites
  • One physical host and one HoloRouter serve both sites
  • Sub-millisecond lab latency is not representative
  • Stretched vSAN: under 5 ms RTT between data sites, under 200 ms to the witness; Federation under 150 ms
  • Three-host vSAN minimum per site

Assumptions

  • Trunk carries both VLAN ranges
  • Two SSH sessions available
  • Capacity for two management-only instances
  • Workstation routes for both /20s
  • Binaries staged for 9.0.2.0
  • Config imported in each session
  • Holodeck 9.0.2 dual-site sequence as documented
  • Both sites deployed management-only

Risks

  • HoloRouter reboot — Impact: both sites lose routing and DNS — Mitigation: avoid -ResetHoloRouter while both run; snapshot first
  • Concurrent deployments overload the host — Impact: nested crashes — Mitigation: sequential deployment or reduced options
  • Custom networking overwritten by defaults — Impact: overlapping sites — Mitigation: repeat -CIDR/-VLANRangeStart on every cmdlet
  • Wrong stretched-cluster facts in the defence — Impact: failed defence — Mitigation: Task 5 requirement list from the documentation
  • Treating two instances as one fleet — Impact: wrong operational model — Mitigation: fleet integration as a separate exercise
  • Version drift between sites — Impact: inconsistent estates — Mitigation: fleet-level lifecycle in production
  • Witness placement error — Impact: no quorum on partition — Mitigation: third site requirement

Self-Assessment Discussion Prompts

  1. Why does the documented sequence configure both sites' networks and the router before any instance, and what happens if you change the order?
  2. What does a separate VRF per site give you in the lab, and what is its production analogue?
  3. State the vSAN stretched-cluster inter-site requirements and the behaviour on an inter-site partition.
  4. When would two instances in one fleet beat a stretched management cluster, and when the reverse?
  5. Which production constraints (latency, bandwidth, witness site) cannot be tested on one host, and how will you test them?
  6. How would you defend the shared HoloRouter as acceptable in a lab and unacceptable in production?
  7. What changes in identity (one broker) and security (Federation) when two instances must behave as one estate?
  8. How does version drift arise between two independently deployed sites, and what prevents it?
  9. Which failure scenario in your table is hardest to recover, and why?
  10. What is the smallest production footprint that satisfies the three-host minimum per site plus a witness?

Extensions

Integrate Site B into Site A's fleet

Follow vcp-admin-10 Task 2 to add the Site B instance to Site A's VCF Operations with a collector, then compare fleet-level operations across the two sites.

harder

Custom CIDRs and VLAN ranges

Redeploy dual site with 10.3.0.0/20 and 10.4.0.0/20 and VLAN starts 100 and 200, repeating the values on every cmdlet as the documentation requires.

same

Edge clusters on both sites

Add -NsxEdgeClusterMgmtDomain to both deployments (capacity permitting) and verify two BGP peerings with the HoloRouter using Get-HoloDeckBGPConfig -Site a and -Site b.

harder

Cross-site SSO

Configure VCF SSO on Site A with an appliance identity broker and connect Site B's vCenter and NSX to it (vcp-admin-04); observe the cross-instance model.

harder

NSX Federation reading

Read the NSX Federation section of the VCF documentation and write the design you would need for one DFW policy across both sites, including the 150 ms constraint.

same

Site B as VCF 5.2

Deploy Site B with -Version 5.2.2 to compare 5.2 and 9.0 management planes side by side (see holodeck-07 Task 4).

same

Failure-table rehearsal

For each row of your Task 5 failure table, write the exact VCF documentation section that supports the behaviour you describe.

same

⚠ Known Pitfalls

Running Set-HoloRouter -dualsite after Site A exists COMMON
Problem: Router rebuild disrupts the running site.
Resolution: Network configs for both sites and Set-HoloRouter -dualsite come before any New-HoloDeckInstance.
Site B deployed into Site A's addressing COMMON
Problem: Custom values not repeated.
Resolution: Pass both sites' -CIDR and -VLANRangeStart values to the Site B command.
Mapping the lab to a stretched cluster COMMON
Problem: Wrong architecture mapping in the defence.
Resolution: Two independent instances; stretched vSAN is a different design with its own documented requirements.

References

Was this page useful?
Type to search. ↑ ↓ to move, Enter to open, Esc to close.