Academy/NSX 4.x Network Virtualization Professional (2V0-41.24)/Lab N4: VPC (Virtual Private Cloud) Construct in VCF 9.0
This lab targets VCF 9.0

Lab N4: VPC (Virtual Private Cloud) Construct in VCF 9.0

VCF 9.0Advancedvcp-foundation⏱ 120 min

NSX 9.0.x (feature set inherited from the NSX 4.2 line; NSX 4.2 docs remain a valid technical reference) VPC — new cloud-native construct for tenant isolation, self-service networking, Projects integration

Objectives

  • Understand the VPC construct as a multi-tenancy model in NSX 9.0 / VCF 9.0 (NSX VPCs were introduced in NSX 4.1.1 — VMware NSX 4.1.1 Release Notes)
  • Create Projects and VPCs with self-service subnets
  • Configure VPC networking: DHCP, default gateway, NAT, and security policies
  • Deploy workloads into a VPC and validate connectivity
  • Compare VPC-based isolation with traditional T1/segment-based isolation
  • Integrate VPC with VCF Automation for self-service catalog delivery

Prerequisites

VCF 9.0 with NSX 9.0.x from the VCF 9.0 BOM, T0 gateway operational with external connectivity, VCF Automation (optional — for self-service catalog integration), role-based access configured for tenant persona

Prior labs: net-virt-01, net-virt-02

Required skills:

  • NSX networking fundamentals (T0/T1/segments)
  • Multi-tenancy concepts
  • Cloud networking constructs (VPC, subnets, NAT)

Lab Environment

VCF 9.0 workload domain with NSX 9.0, T0 gateway peered with the physical network (from Lab net-virt-02) and a project Transit Gateway connected to it. At least 2 ESXi hosts for workload placement. VCF Automation deployed (optional for step 10).

Tasks

Task 1 Build and Consume NSX VPCs for Tenant Isolation

The VPC model (NSX 4.1.1+, per the VMware NSX 4.1.1 Release Notes; NSX 9.0 in VCF 9.0) introduces a new abstraction layer: Project → VPC → Subnets. A Project is an administrative boundary (maps to a team or business unit). Within a Project, tenants create VPCs with isolated subnets — conceptually similar to AWS VPCs. In VCF 9.0 the VPC is realized as its own object (no longer created inside a Tier-1) with an implicit, system-managed gateway; tenants never see gateways or segments. Northbound connectivity comes from the project's Transit Gateway (TGW) through a VPC Connectivity Profile (external IP blocks, Private-TGW IP blocks, Edge cluster, N-S Services and Default Outbound NAT toggles), and common services from a VPC Service Profile (DHCP, subnet profiles). The infrastructure admin prepares the project, profiles and IP blocks; tenants consume VPCs self-service.

Implement the VPC construct — NSX's cloud-native multi-tenancy model (NSX 9.0 in VCF 9.0) — which abstracts T1 gateways, segments, and DFW policies into a simplified cloud-like experience. VPCs enable tenant self-service for network and security without exposing the complexity of T0/T1/segment/DFW hierarchy. This is a major VCF 9.0 feature that bridges the gap between VMware's on-premises networking and public cloud networking models.

Step 1

Configure IP blocks for the VPC model. NSX Manager → Networking → IP Address Management → IP Address Blocks → Add. Create: an External IP block (routable, e.g. 192.168.200.0/24) used for Public subnets and external IPs / 1:1 NAT, and a Private-TGW IP block (non-routable, e.g. 172.16.0.0/16; at least a /26 is needed for a Supervisor) used for Private Transit Gateway subnets that are reachable between VPCs without NAT. Private-VPC CIDRs are entered per VPC and may overlap between VPCs.

Step 2

Create a Project. NSX Manager → Inventory → Projects → Add Project. Configure: Name='Project-TeamAlpha', Description='Development team Alpha — self-service networking'. The project gets a system-created Transit Gateway plus a default VPC Connectivity Profile and VPC Service Profile. Edit the default connectivity profile (VPCs → Profiles → VPC Connectivity Profile): Transit Gateway=system TGW, External IP Blocks=the external block, Private-Transit Gateway IP Blocks=the private-TGW block, Edge Cluster='edge-cluster-01' (from Lab net-virt-02), N-S Services=On for this lab (needed for NAT and N-S firewall), Default Outbound NAT=On. The TGW connects to the external Tier-0 'T0-Lab'. Assign users/roles: add a tenant admin user (e.g., 'tenant-alpha-admin') with 'Project Admin' role — this user can create VPCs within the project but cannot modify infrastructure-level objects.

Step 3

Create a VPC (as Enterprise Admin or Project Admin). Select Project-TeamAlpha in the Project drop-down, go to VPCs → Virtual Private Cloud → Add VPC. Basic Info: Name='vpc-dev-01', Connectivity Profile=default (Transit Gateway via connectivity profile), Service Profile=default, Private-VPC IP CIDRs=10.100.0.0/16. Save and Go Next → Additional Configurations → Subnets → Set: 'subnet-web', Access Mode=Public (CIDR auto-allocated from the external block; routable without NAT); 'subnet-db', Access Mode=Private VPC (CIDR from the VPC's private CIDRs; local to the VPC, outbound via the auto-plumbed SNAT when Default Outbound NAT is on). DHCP comes from the service profile.

Step 4

Verify the realization. Switch back to the Default project / Enterprise Admin view. The VPC is realized directly as a VPC object with an implicit gateway that is system-managed and not exposed as an editable Tier-1 — do not look for a 'proj-...-t1' gateway. Check instead: VPCs → Virtual Private Cloud → vpc-dev-01 → Subnets (both Realized), the topology graphic (VPC → Transit Gateway → T0-Lab), and Networking → Transit Gateways for the project TGW and its external connection. Subnets appear in vCenter as networks the VM can attach to; nothing underneath is edited directly.

Step 5

Deploy workloads into VPC subnets. In vSphere Client, create or move VMs to VPC subnets: Edit VM → Network Adapter → select the segment backing 'subnet-web' (it appears with a VPC-prefixed name). The VM receives an IP via DHCP from the VPC's built-in DHCP service. Deploy: vm-web-vpc (on subnet-web, gets an address from the external block, 192.168.200.x), vm-db-vpc (on subnet-db, gets 10.100.x.x). Verify: both VMs get IPs via DHCP and can ping each other (east-west within a VPC is routed by the VPC's implicit gateway and allowed by default).

Step 6

Configure external access. Public subnet-web is already routable without NAT (its CIDR comes from the external block). For the private subnet-db, Default Outbound NAT in the connectivity profile auto-plumbs one SNAT per VPC from the external block. For inbound access to a private VM, open the VPC → Network Services → External IPs → Set: pick vm-db-vpc and its NIC, auto-assign an external IP (1:1 NAT from the external block). Default Outbound NAT (the auto-plumbed SNAT) requires N-S Services on the connectivity profile, i.e. a centralized Transit Gateway connection (VCF-WLDNET-VPCSCL-RCMD-CFG-21); External IPs (1:1 NAT) are also available with a distributed Transit Gateway connection. Verify: from vm-db-vpc, curl an external address — traffic exits via the VPC SNAT through the TGW and T0-Lab.

Step 7

Apply VPC-level security policies. In the VPC context → Security → Security Policies → Add Policy. Name='vpc-dev-01-security'. Add rules: (1) 'Web-Ingress': Source=Any, Dest=subnet-web, Service=HTTP(80)/HTTPS(443), Action=Allow; (2) 'Web-to-DB': Source=subnet-web, Dest=subnet-db, Service=MySQL(3306), Action=Allow; (3) 'Deny-Direct-DB': Source=Any (external), Dest=subnet-db, Service=Any, Action=Drop. These VPC-scoped rules do not affect other VPCs; infrastructure-level DFW policies in the default space can still apply to VPC workloads. The tenant admin can manage them without infrastructure admin involvement.

Step 8

Compare VPC security with traditional DFW. Key differences: (a) VPC policies are scoped to the VPC — they cannot affect VMs outside the VPC; (b) infrastructure DFW policies (from Lab net-virt-03) created in the default space can still apply to VPC workloads — check the NSX documentation on firewall policies in an NSX VPC for how default-space, project and VPC rules are ordered before you rely on an override; (c) VPC policies can use the VPC's subnets as source/destination, and groups created in the VPC can be used in its firewall policies (VCF 9.0.1 docs p.2401); VPC groups and N-S firewall additionally require the vDefend Firewall with Advanced Threat Prevention licence. Verify: open the VPC's security policies in the VPC context in NSX Manager and compare them with the default-space DFW policies.

Step 9

Test isolation and inter-VPC reachability through the Transit Gateway. Create a second VPC in the same Project: 'vpc-staging-01' with Private-VPC CIDR 10.200.0.0/16 and two subnets: 'stg-private' (Access Mode=Private VPC) and 'stg-shared' (Access Mode=Private Transit Gateway, CIDR auto-allocated from the Private-TGW block). Deploy vm-staging on stg-private and vm-shared on stg-shared. From vm-db-vpc (Private VPC subnet in vpc-dev-01): ping vm-staging — FAILS (Private VPC CIDRs are local to the VPC and may even overlap); ping vm-shared — SUCCEEDS without NAT, because Private Transit Gateway subnets are routed between the VPCs attached to the same TGW. Public subnets are reachable from outside via the TGW → T0. There is no T0 route or 'VPC peering' step: the access mode of the subnet decides.

Step 10

VCF Automation integration (optional). VCF Automation (formerly Aria Automation) discovers the subnets and groups of NSX Projects and VPCs configured in NSX Manager and treats them as networks and security groups (VCF 9.0.1 docs p.6154). (a) Add the VPC subnets of vpc-dev-01 to a network profile; (b) create a Cloud Template whose machines attach to a network placed through that profile and publish it to the service catalog; (c) a tenant user requests the catalog item and the workload lands on the VPC subnet. The VPC itself, its subnets and security policies are created in NSX Manager (steps 1-8); confirm any Cloud.NSX.* resource you use against the VCF Automation 9.0 cloud template reference before relying on it. This is the self-service model: tenants consume pre-built isolated network environments without opening tickets to the network team.

Validation Gate

Check: VPC construct operational with tenant isolation, NAT, security, and self-service

Expected: Project created with IP blocks and T0 binding. VPC deployed with public and private subnets. DHCP providing IPs to VMs. SNAT/DNAT enabling external access for public subnet. VPC security policies enforced. Inter-VPC isolation confirmed. Optional: VCF Automation catalog delivering VPCs on demand.

Common Errors

VPC creation fails with 'Insufficient IP block capacity'
Fix: The IP block assigned to the Project is exhausted. Either expand the IP block CIDR or assign additional blocks to the Project. Each VPC subnet consumes a /24 (or custom size) from the block. For large tenants, use /16 blocks to provide 256 possible /24 subnets.
VMs in VPC subnet don't receive DHCP addresses
Fix: DHCP comes from the VPC Service Profile. Verify: VPCs → Profiles → VPC Service Profile → DHCP configured, and the subnet's DHCP settings reference it; the connectivity profile must have an Edge cluster when centralized services are used.
SNAT not working — VMs can't reach external networks
Fix: Verify: (1) SNAT rule is configured with correct source subnet and translated IP, (2) external IP pool address is on the T0 uplink subnet and routable from the physical network, (3) N-S Services and Default Outbound NAT are on in the VPC connectivity profile (Default Outbound NAT requires N-S Services, i.e. a centralized TGW connection; a distributed connection still provides External IPs (1:1 NAT)), and the Tier-0 advertises the external IP block to the physical router.
VPC security policies not enforcing
Fix: VPC security policies are realized as DFW rules scoped to the VPC's backing segments. If DFW is disabled globally, VPC policies won't enforce. Verify: Security → DFW → General Settings → DFW Status=Enabled. Also check: the VPC policy is Published (not in draft state).

Final Validation

NSX VPC construct operational with full tenant networking and security isolation

✓ Project configuration → Project created with T0, Edge cluster, and IP blocks assigned

✓ VPC with subnets → VPC deployed with public and private subnets, DHCP active

✓ VM connectivity → VMs in the same VPC communicate; across VPCs only Private Transit Gateway subnets are reachable

✓ NAT functionality → Default Outbound NAT gives private subnets outbound access; an External IP (1:1 NAT) maps inbound traffic to the private VM; Public subnet reachable without NAT

✓ VPC security policies → VPC-scoped rules enforce allow/deny per configuration

✓ Tenant isolation → Private VPC subnets isolated between VPCs; Private Transit Gateway subnets reachable via the TGW without NAT

Cleanup / Restore

• Delete VMs from VPC subnets

• Delete VPCs (their subnets and implicit gateway are removed with them)

• Delete Project (removes all VPCs within it)

• Release external IP pool allocations

• Delete IP address blocks if no longer needed

Design Reflection (VCDX)

The VPC construct is a signature VCF 9.0 feature: VPCs attach to a project Transit Gateway through connectivity profiles, and the subnet access mode (Private VPC / Private Transit Gateway / Public) is the design lever for isolation, NAT and routability.

In a VCDX defense, VPCs are compelling for: (1) Multi-tenancy without exposing NSX complexity — tenants get AWS-like networking without learning T0/T1/segments; (2) Delegated security — VPC policies give tenants security autonomy while default-space DFW policies set by the infrastructure admin can still apply to VPC workloads (confirm the rule ordering in the NSX documentation); (3) Self-service at scale — VCF Automation + VPCs enable Day 0 network provisioning in minutes, not days.

Compare with the traditional approach: each tenant request needed the network admin to create a T1, segments, DFW rules and NAT — the VPC model realizes the VPC directly, auto-plumbs outbound NAT and routes inter-VPC traffic via the TGW. Sizing comes from the Design Guide: each VPC needs a Small load balancer instance and a large Edge pair is sufficient for up to 48 VPCs (Supervisor control plane uses 2).

Requirements

  • Self-service networking for 10+ application teams without infrastructure admin involvement
  • Network and security isolation between tenants
  • Cloud-like experience (subnets, NAT, security groups) for development teams familiar with public cloud

Constraints

  • VPCs predate VCF 9.0 (see objective 1); VCF 9.0 adds project Transit Gateways and VPC connectivity and service profiles. NSX in VCF 9.0 is 9.0.x from the VCF BOM; a standalone NSX installation or upgrade is not supported (VCF 9.0.1 docs p.235)
  • Each VPC with N-S services consumes Edge capacity (one Small load balancer instance; large Edge pair for up to 48 VPCs) — capacity planning required
  • External and Private-TGW IP blocks must be pre-provisioned in the connectivity profile; only Private-VPC CIDRs are chosen per VPC

Assumptions

  • Tenant admins understand basic networking concepts (subnets, CIDR, NAT)
  • Infrastructure admin pre-provisions sufficient IP blocks and Edge capacity for expected VPC count
  • VCF Automation is deployed for full self-service experience (optional but recommended)

Risks

  • IP block exhaustion prevents new VPC creation — implement monitoring and alerting on IP block utilization
  • VPC sprawl (tenants creating many VPCs without cleanup) consumes Edge and control plane resources — implement VPC lifecycle policies
  • Mixing VPC and traditional T1/segment approaches creates operational complexity — standardize on one model per environment

Self-Assessment Discussion Prompts

  1. How does the NSX VPC construct compare with AWS VPC in terms of capabilities and limitations?
  2. When would you choose traditional T1/segment isolation over VPC-based isolation?
  3. How do you place shared services (DNS, monitoring, backup) — Private Transit Gateway subnets, Public subnets or a shared-services VPC — and what does each mean for NAT and advertisement?
  4. What is the maximum number of VPCs and subnets supported per NSX Manager cluster in VCF 9.0?

Extensions

Restrict inter-VPC traffic on Private Transit Gateway subnets with VPC security policies (groups and N-S firewall need the vDefend ATP licence)

Build a VCF Automation cloud template that provisions a complete 3-tier application with VPC, subnets, VMs, NAT, and security policies

Implement VPC quota management — limit the number of VPCs, subnets, and external IPs per Project

Configure VPC-level IPFIX flow export for tenant-specific traffic monitoring

⚠ Known Pitfalls

Looking for a Tier-1 gateway or segments to edit behind a VPC — in VCF 9.0 the VPC is realized directly with an implicit, system-managed gateway; all changes go through the VPC, its profiles and the Transit Gateway
Not pre-provisioning sufficient IP blocks for the Project — VPC creation fails silently or with unhelpful errors when IP capacity is exhausted
Assuming all VPC subnets behave alike — Private VPC subnets are isolated (and may overlap), Private Transit Gateway subnets are routed between VPCs on the same TGW without NAT, Public subnets are routable externally
Ignoring VPC resource consumption — each VPC with N-S services needs a Small load balancer instance on the Edge cluster; a large Edge pair covers up to 48 VPCs before you add or scale up Edge VMs

References

  • VCF 9.0 documentation — Configure a VPC; Add a VPC Connectivity Profile; Add a VPC Service Profile: https://techdocs.broadcom.com/us/en/vmware-cis/vcf/vcf-9-0-and-later/9-0.html
  • VCF 9.0 Design Guide — VPC scalability recommendations (VCF-WLDNET-VPCSCL-RCMD-CFG-19..23) and Edge sizing for VPCs
  • NSX Multi-tenancy chapter (Projects, VPCs, Transit Gateways) in the VCF 9.0 documentation (VCF 9.0.1 docs p.2339 onward): https://techdocs.broadcom.com/us/en/vmware-cis/vcf/vcf-9-0-and-later/9-0/advanced-network-management/administration-guide/nsx-multi-tenancy.html
Was this page useful?
Type to search. ↑ ↓ to move, Enter to open, Esc to close.