DO NOT SHARE THESE DOCS WITH CUSTOMERS!
This is an LA release that will only be provided to a select number of PLM-sanctioned customers (PDFs only). Contact PLM for details.
The following SBC SWe in GCP deployment models are supported:
Public Cloud Deployment Models
The High-Availability Front End (HFE) node is a public-facing node that allows sub-second switchover between Active and Standby SBC instances of an HA pair, as it negates the need for any IP reassignment. GCP requires each interface of a instance in a separate Virtual Private Network (VPC). Create a minimum of six VPCs for a full HFE set up (assuming all management interfaces for the SBC and the HFE node are in the same VPC). HFE 2.1 has two HFE nodes, each responsible for a different type of traffic: Both HFE nodes require three interfaces, as follows: Standard/Ubuntu Interface Name NIC PKT0 HFE node Function To use a HFE 2.1 environment, the startup-script for the SBCs requires the fields HFE Node Network Setup
HFE 2.1 Network Setup
PKT1 HFE node Function Requires External IP? eth0 / ens4 nic0 Public Interface for SBC PKT0 Private interface in for SBC PKT1; only instances in the same subnet can connect. Yes (only on PKT0 HFE node) eth1 / ens5 nic1 Management interface to HFE. Management interface to HFE. Optional eth2 / ens6 nic2 Interface to SBC PKT0; ensure that the interface is in the same VPC and subnet as SBC pkt0. Interface to SBC PKT1; ensure that the interface is in the same VPC and subnet as SBC pkt1. No Pkt0HfeInstanceName
and Pkt1HfeInstanceName
. For more information, refer to the table in the section "User Data" on the page Instantiating SBC SWe in GCP.