Warm Standby Requirements and Recommendations - Understanding-NetCloud-Service-Gateway-High-Availability/Warm-Standby-Requirements-and-Recommendations

Understanding NetCloud Service Gateway High Availability
ft:locale
en-US
ft:sourceName
Paligo_Prod
Document Type
Article

Following are the requirements and recommendations for configuring warm standby in an on-premises environment:

  • The primary and secondary NetCloud Exchange Service Gateways are typically in the same Datacenter/VMware VDC. They can be in different data centers if there is reliable layer-2 connectivity (for example, DCI or MPLS) between them.

  • WAN, LAN, and MGMT subnets must be shared between primary and secondary NCX Service Gateway network interfaces.

Following are the requirements and recommendations for configuring warm standby in a public cloud environment:

  • NCX Service Gateways must be in the same Virtual Private Cloud (VPC)/virtual network (Vnet)

  • NCX Service Gateway placement across availability zones (AZs) depends on which of the following supported Warm Standby use cases in a public cloud is being used:

    1. For Warm Standby with different WAN subnets, different MGMT subnets, and no LAN subnet:

      • The two service gateways should be in different AZs for maximum resilience.

    2. For Warm Standby with different WAN subnets, different MGMT subnets, and with a shared LAN subnet:

      • The two service gateways must be in the same AZ in order to share the LAN subnet.

Note

Warm standby is supported in a KVM or VMware environment with minimum software version 7.23.30, in an AWS environment with minimum software version 7.23.100, and in an Azure environment with minimum software version 7.24.100.