Isolated network space users run self-service under an NSX project, with dedicated subnets, security rules and built-in IPAM; a further tenancy tier.
Also called NSX Virtual Private Cloud.
Read more: Broadcom TechDocs
In the Ultra Transcenders books
Each book explains NSX VPC in context, with comparison tables and the common traps.
Terms in this definition
- isolated network
A fenced-off replica of a production network within a virtual lab, so verified machines can run without clashing. Up to 9 per lab.
- NCM Self-Service
Provisions and automates applications on public and private clouds, looking after their life cycle on bare-metal servers or VMs. Backups of it have to be taken separately by hand.
- NSX Project
Tenant-like boundary in NSX, keeping each group's network and security objects apart within a single deployment; VPCs sit inside one.
- Dedicated
Running Azure Functions on an App Service plan, which removes the execution time limit and offers VNet integration on Basic and higher tiers.
- AMPRS
An acronym for availability, manageability, performance, recoverability and security: the five design qualities used to sort non-functional requirements and to weigh up trade-offs between design decisions.
- IPAM
IP address management: handing out and keeping track of addresses and subnets. NSX VPCs have it built in, and VCF Automation can also hook up to a third-party IPAM system.
- Archive
Offline access tier for blobs, cheapest to store yet dearest to access. Reading a blob means rehydrating it first, which can take as long as 15 hours.
Related terms
- All Apps organization
VCF Automation's main way of hosting tenants (VM Apps being the other organization type). Tenants never see vSphere or NSX: they use VMs, VKS clusters and more from projects and vSphere Namespaces running on Supervisors with NSX VPC networking, separated from each other by namespace and NSX project boundaries.
- Default Outbound NAT
Turning this on for an NSX VPC (N-S Services required) generates one SNAT rule for the VPC, translating to the external IP block, so VMs on private subnets get outbound access. Unavailable with an active-active Tier-0 behind the transit gateway.
- Default VPC
NSX VPC generated automatically once regional networking is completed for a VCF Automation organization, alongside an NSX project, a transit gateway, a default VPC connectivity profile and an SNAT rule.
- Network Extension
Migrated VMs keep their IP and MAC addresses because this VCF Operations HCX service bridges their networks (VLAN-tagged distributed port groups, NSX segments or NSX VPC subnets) to the remote site through a pair of appliances. Unless Mobility Optimized Networking is used, the default gateway stays at the source.