Bare Metal Edge migration limitations and performance - NSX
search cancel

Bare Metal Edge migration limitations and performance - NSX

book

Article ID: 448953

calendar_today

Updated On:

Products

VMware NSX

Issue/Introduction

Migrating from virtual NSX Edge nodes to Bare Metal Edge nodes in Active/Standby mode involves specific architectural requirements, performance trade-offs, and the loss of vSphere-native features.

Symptoms

  • Scaling requirements exceed 16 vCPUs or 64 GB RAM (X-Large VM limit).
  • Requirement for high-density VRF configurations (up to 100 VRFs per node).
  • Planning migration from VM-based Edge clusters to physical hardware.

Environment

VMware NSX

Cause

Guidance request regarding technical constraints during virtual-to-physical Edge migration.

Resolution

1. Architectural and Migration Constraints

  • Homogeneity Rule: NSX Edge Clusters must be completely homogeneous. Virtual Edge VMs and Bare Metal nodes cannot coexist within the same cluster.
  • Parallel Deployment: Deploy a new Bare Metal Edge Cluster. Configure parallel uplinks and routing peers, then migrate Tier-0/Tier-1 gateways. In-place migrations are not supported.

2. Performance Capabilities

  • VRF Scaling: Both X-Large VM and Bare Metal nodes support a maximum of 100 Tier-0 VRF gateways per node. This is a software control-plane limit.
  • Resource Utilization: Bare Metal nodes bypass hypervisor overhead and CPU scheduling jitter, leveraging the full physical host resource pool.
  • Stateful Services: Performance impacts are higher when enabling stateful services (Firewall, NAT, VPN) per VRF due to physical memory and DPDK ring queue contention.

3. Operational Impact

  • Feature Loss: Virtualization benefits such as vMotion, snapshots, DRS, and vSphere HA are unavailable. Hardware failures must be managed via NSX-level Active/Standby failover or upstream BGP ECMP.
  • Lifecycle Management: Nodes require manual installation via ISO or PXE boot. Automated scaling and provisioning through the vCenter UI are not supported.
  • Hardware Underutilization: In Active/Standby mode, the standby physical server remains idle, which must be factored into capacity planning.

Additional Information

Powered by Wolken Software