Hardware Deployment Modes

Objective

This guide presents information on the various deployment modes for the F5® Distributed Cloud Hardware. The provided information includes details such as the default initial properties for the devices and interfaces. The deployment modes include single-node deployment, multi-node cluster deployment with stacking, and multi-node cluster without stacking of the nodes.

Note: Stacking is serially connecting two or more nodes to obtain increased overall capacity. In this guide, stacked nodes mean more than one rack-mounted nodes connected through dedicated interfaces.

The F5 Distributed Cloud Hardware mentioned in this guide covers the following:

• Industrial Gateway (IGW)
• Industrial Server (ISV)

Note: Clustering IGW or ISV nodes is not supported if LTE is selected as the WAN interface.

---

Industrial Gateway

The IGW can be deployed in the following modes:

• Single-node CE Site
• Multi-node Cluster Site with Stacking
• Multi-node Cluster Private Datacenter (DC) Cloud Gateway
• Multi-node Cluster for Enterprise to Cloud Proxy.

The following sections present details for each of the deployment modes.

Single-Node CE Site

The single-node CE site deployment consists of one IGW box. The following device configuration is applied by default in the initial setup:

• Ethernet interface eth0 is set as dedicated outside interface. This interface can only be configured locally and functions as a DHCP client by default.
• LTE interface is set as dedicated outside interface.
• Wi-Fi interface is set as a dedicated outside interface.
• Ethernet interfaces eth1, eth2, and eth3 are made available for configuring inside or outside interfaces. The configuration can be done via F5 Distributed Cloud Global Controller (GC).
• Interfaces eth1 and eth2 function as DHCP client in inside network by default.
• Interface eth3 functions as DHCP server for the inside network by default.

Note: The eth3 interface can be configured to be for outside network.

• In case of bootstrap at factory reset, do the following:

• The interface eth3 functions as DHCP server by default so connect your laptop to this interface. This will assign a DHCP IP.

• Optionally, use CLI or local UI to configure eth0 interface for purposes such as WAN connectivity. Use CLI or Local UI to configure registration parameters such as token. Configure the site and approve the registration in F5® Distributed Cloud Console (Console).

• Default configuration keeps eth3 in inside network and DHCP server enabled.

• If during bootstrap, eth1 interface gets a DHCP IP, this IP can also be used for SSH or local UI. Verify that this IP is displayed on LCD.

• In case of ach inside interface functioning as DHCP server, the interface also acts the default gateway and its IP will be the address of default gateway and DHCP server. In case of the interface acts as a DHCP client or configured with static IP, the default gateway is treated as something other than the interface IP.

Multi-node Cluster with Stacking

The following device configuration is applied by default in the initial setup:

• Ethernet interface eth0 is set as dedicated outside interface. This interface can only be configured locally and functions as a DHCP client by default.
• LTE interface is set as dedicated outside interface.
• Wi-Fi interface is set as a dedicated outside interface.
• Ethernet interfaces eth1 and eth2 are used for stacking.
• Interface eth3 functions as DHCP server for the inside network by default.

Note: The eth3 interface can be configured to be for outside network.

• In case of bootstrap at factory reset, do the following:

• The interface eth3 functions as DHCP server by default so connect your laptop to this interface. This will assign a DHCP IP.

• Optionally, use CLI or local UI to configure eth0 interface for purposes such as WAN connectivity. Use CLI or Local UI to configure registration parameters such as token. Configure the site and approve the registration in Console.

• Default configuration keeps eth3 in inside network and DHCP server enabled.

• If during bootstrap, eth1 interface gets a DHCP IP, this IP can also be used for SSH or local UI. Verify that this IP is displayed on LCD.

• In case of ach inside interface functioning as DHCP server, the interface also acts the default gateway and its IP will be the address of default gateway and DHCP server. In case of the interface acts as a DHCP client or configured with static IP, the default gateway is treated as something other than the interface IP.

Note: A lone inside interface from each IGW can be connected to external switches with BGP enabled.

The multi-node cluster can be stacked in the following ways:

• Daisy chain ring topology - Node A connected to Node B, Node B to Node C, and so on.
• Connecting to redundant external TOR switches - The eth1 interfaces of all nodes connected to TOR1 in VLAN1, eth2 interfaces of all nodes connected to TOR2 in VLAN2, and so on.

Note: Configuring VLAN is required as IP addresses are assigned automatically using DHCP.

Multi-node Cluster Private DC Cloud Gateway

In case of private DC deployments, the nodes are rack mounted and connected to TOR switch. The deployment mode can be either ingress gateway or ingress/egress gateway. However, this depolyment model does not support basic networking functionality like WAN connectivity, DHCP server, etc.

In this deployment mode, the cluster does not act as default gateway. It is always connected with multiple interfaces in L3 and floating VIPs are used in both outside and inside network.

Note: BGP is enabled with the TOR switches.

The following device configuration is applied by default in the initial setup:

• Ethernet interface eth0 is set as dedicated outside interface. This interface can only be configured locally and functions as a DHCP client by default.
• Ethernet interfaces eth1, eth2, and eth3 are made available for configuring inside or outside interfaces. The configuration can be done via the Global Controller (GC).
• Ethernet interfaces eth1 and eth2 act as DHCP clients in the outside network.
• Interface eth3 functions as DHCP server for the inside network by default.

Note: The eth3 interface can be configured to be for outside network.

• In case of bootstrap at factory reset, do the following:

• The interface eth3 functions as DHCP server by default so connect your laptop to this interface. This will assign a DHCP IP.

• Optionally, use CLI or local UI to configure eth0 interface for purposes such as WAN connectivity. Use CLI or Local UI to configure registration parameters such as token. Configure the site and approve the registration in Console.

• Default configuration keeps eth3 in inside network and DHCP server enabled.

• If the interfaces eth0, eth1, and eth2 get DHCP IP during bootstrap, this IP can also be used for SSH or local UI. Verify that this IP is displayed on LCD.

Note: The DHCP server is not relevant in this deployment mode. However, it is not disabled by default.

• All interfaces can be L3 interfaces in the same subnet or different subnets.
• This model does not support stacking since there is always L3 connectivity between nodes on all interfaces.

Note: It is recommended to configure loopback IP and dynamic routing (BGP) for high availability with multiple L3 interfaces.

F5 Distributed Cloud Mesh Node or Cluster

This model is same as the Multi-node Cluster with Stacking. A on-premise stack can be made in a standalone cluster.

Multi-node Cluster for Enterprise to Cloud Proxy

In case of a proxy between the enterprise network and cloud, the nodes are rack mounted and connected to TOR switch. This depolyment model does not support basic networking functionality like WAN connectivity, DHCP server, etc. However, the Regional Edge (RE) sites are always reachable using a dedicated inside network interface.

In this deployment mode, the cluster does not act as default gateway. It is always connected with multiple interfaces in L3 and floating VIPs are used in both outside and inside network.

Note: BGP is enabled with the TOR switches.

The following device configuration is applied by default in the initial setup:

• Ethernet interface eth0 is set as dedicated site local outside interface. This interface can only be configured locally and functions as a DHCP client by default.
• Ethernet interface eth2 is set as dedicated site local inside interface. This interface can only be configured locally and functions as a DHCP client by default.
• LTE interface is set as dedicated outside interface.
• Wi-Fi interface is set as a dedicated outside interface.
• Ethernet interfaces eth1 and eth3 are made available for configuring inside or outside interfaces. The configuration can be done via Global Controller (GC).
• Ethernet interface eth1 acts as DHCP client in the outside network.
• Ethernet interface eth3 functions as DHCP server for the inside network by default. However, this configuration becomes invalid if a user configures static IP or changes the primary interface.

Note: The eth3 interface can be configured to be for outside network.

• In case of bootstrap at factory reset, do the following:

• The interface eth3 functions as DHCP server by default so connect your laptop to this interface. This will assign a DHCP IP.

• Optionally, use CLI or local UI to configure eth0 interface for purposes such as WAN connectivity. Use CLI or Local UI to configure registration parameters such as token. Configure the site and approve the registration in Console.

• Default configuration keeps eth3 in inside network and DHCP server enabled.

• If the interfaces eth0, eth1, and eth2 get DHCP IP during bootstrap, this IP can also be used for SSH or local UI. Verify that this IP is displayed on LCD.

Note: The DHCP server is not relevant in this deployment mode. However, it is not disabled by default.

• All interfaces can be L3 interfaces in the same subnet or different subnets.
• This model does not support stacking since there is always L3 connectivity between nodes on all interfaces.

Note: It is recommended to configure loopback IP and dynamic routing (BGP) for high availability with multiple L3 interfaces.

---

Industrial Server

The ISV has the following interfaces:

• Management interface enp101s0
• Ethernet interfaces eth0 to eth7 are 1G interfaces on the switch in ISV.
• Ethernet interfaces eth8 to eth10 are 10G directly connected interfaces.

The ISV can be deployed in the following modes:

• Single-node CE Site
• Multi-node Cluster Site with Stacking
• Multi-node Cluster Private Datacenter (DC) Cloud Gateway
• Multi-node Cluster for Enterprise to Cloud Proxy.

The following sections present details for each of the deployment modes.

Single-Node CE Site

The single-node CE site deployment consists of one ISV box. The following device configuration is applied by default in the initial setup:

• The management interface is DHCP client by default.

• Ethernet interface eth0 is set as dedicated outside interface. This interface can only be configured locally and functions as a DHCP client by default.

• LTE interface is set as dedicated outside interface.

• Wi-Fi interface is set as a dedicated outside interface.

• Ethernet interfaces eth1 to eth9 are made available for configuring inside or outside interfaces. The configuration can be done via Global Controller (GC).

• Interface eth10 functions as DHCP server for the inside network by default.

• In case of bootstrap at factory reset, do the following:

• The interface eth10 functions as DHCP server by default so connect your laptop to this interface. This will assign a DHCP IP.

• Optionally, use CLI or local UI to configure eth0 interface for purposes such as WAN connectivity. Use CLI or Local UI to configure registration parameters such as token. Configure the site and approve the registration in Console.

• Default configuration keeps eth10 in inside network and DHCP server enabled.

• If during bootstrap, eth1 interface gets a DHCP IP, this IP can also be used for SSH or local UI. Verify that this IP is displayed on LCD.

• In case of ach inside interface functioning as DHCP server, the interface also acts the default gateway and its IP will be the address of default gateway and DHCP server. In case of the interface acts as a DHCP client or configured with static IP, the default gateway is treated as something other than the interface IP.

Multi-node Cluster with ISV Stacking

The following device configuration is applied by default in the initial setup:

• The management interface is DHCP client by default.

• Ethernet interface eth0 is set as dedicated outside interface. This interface can only be configured locally and functions as a DHCP client by default.

• LTE interface is set as dedicated outside interface.

• Wi-Fi interface is set as a dedicated outside interface.

• Ethernet interface eth1 to eth7 are made available for configuring inside or outside interfaces. The configuration can be done via Global Controller (GC).

• Ethernet interfaces eth8 and eth9 are used for stacking.

• Interface eth10 functions as DHCP server for the inside network by default.

• In case of bootstrap at factory reset, do the following:

• The interface eth10 functions as DHCP server by default so connect your laptop to this interface. This will assign a DHCP IP.

• Optionally, use CLI or local UI to configure eth0 interface for purposes such as WAN connectivity. Use CLI or Local UI to configure registration parameters such as token. Configure the site and approve the registration in Console.

• Default configuration keeps eth10 in inside network and DHCP server enabled.

• If during bootstrap, eth1 interface gets a DHCP IP, this IP can also be used for SSH or local UI. Verify that this IP is displayed on LCD.

• Each inside interface functioning as DHCP server, the interface also acts the default gateway and its IP will be the address of default gateway and DHCP server. In case of DHCP client interface and static interface, the default gateway is treated as something other than the interface IP.

Note: A lone inside interface from each ISV can be connected to external switches with BGP enabled.

The multi-node cluster can be stacked in the following ways:

• Daisy chain ring topology - Node A connected to Node B, Node B to Node C, and so on.
• Connecting to redundant external TOR switches - The eth1 interfaces of all nodes connected to TOR1 in VLAN1, eth2 interfaces of all nodes connected to TOR2 in VLAN2, and so on.

Note: Configuring VLAN is required as IP addresses are assigned automatically using DHCP.

Multi-node Cluster Private DC Cloud Gateway

In case of private DC deployments, the nodes are rack mounted and connected to TOR switch. The deployment mode can be either ingress gateway or ingress/egress gateway. However, this depolyment model does not support basic networking functionality like WAN connectivity, DHCP server, etc.

In this deployment mode, the cluster does not act as default gateway. It is always connected with multiple interfaces in L3 and floating VIPs are used in both outside and inside network.

Note: BGP is enabled with the TOR switches.

The following device configuration is applied by default in the initial setup:

• The management interface is DHCP client by default.

• Ethernet interface eth0 is set as dedicated outside interface. This interface can only be configured locally and functions as a DHCP client by default.

• Ethernet interfaces eth1 to eth9 are made available for configuring inside or outside interfaces. The configuration can be done via Global Controller (GC).

• Interface eth10 functions as DHCP server for the inside network by default.

• In case of bootstrap at factory reset, do the following:

• The interface eth10 functions as DHCP server by default so connect your laptop to this interface. This will assign a DHCP IP.

• Optionally, use CLI or local UI to configure eth0 interface for purposes such as WAN connectivity. Use CLI or Local UI to configure registration parameters such as token. Configure the site and approve the registration in Console.

• Default configuration keeps eth10 in inside network and DHCP server enabled.

• If the interfaces eth0, eth1, and eth2 get DHCP IP during bootstrap, this IP can also be used for SSH or local UI. Verify that this IP is displayed on LCD.

Note: The DHCP server is not relevant in this deployment mode. However, it is not disabled by default.

• All interfaces can be L3 interfaces in the same subnet or different subnets.
• This model does not support stacking since there is always L3 connectivity between nodes on all interfaces.

Note: It is recommended to configure loopback IP and dynamic routing (BGP) for high availability with multiple L3 interfaces.

Mesh Node or Cluster

This model is same as the Multi-node Cluster with ISV Stacking. A on-premise stack can be made in a standalone cluster.

Multi-node Cluster for Enterprise to Cloud Proxy

In case of a proxy between the enterprise network and cloud, the nodes are rack mounted and connected to TOR switch. This depolyment model does not support basic networking functionality like WAN connectivity, DHCP server, etc. However, the Regional Edge (RE) sites are always reachable using a dedicated inside network interface.

In this deployment mode, the cluster does not act as default gateway. It is always connected with multiple interfaces in L3 and floating VIPs are used in both outside and inside network.

Note: BGP is enabled with the TOR switches.

The following device configuration is applied by default in the initial setup:

• The management interface is DHCP client by default.

• Ethernet interface eth0 is set as dedicated site local outside interface. This interface can only be configured locally and functions as a DHCP client by default.

• LTE interface is set as dedicated outside interface.

• Wi-Fi interface is set as a dedicated outside interface.

• Ethernet interfaces eth1 to eth7 are made available for configuring inside or outside interfaces. The default is DHCP client in outside network. The configuration can be done via Global Controller (GC).

• Ethernet interface eth8 acts as DHCP client in the outside network.

• Ethernet interface eth9 functions as DHCP client for the inside network.

• Ethernet interface eth10 acts as DHCP server for inside network by default. However, this configuration becomes invalid if a user configures static IP or changes the primary interface.

• In case of bootstrap at factory reset, do the following:

• The interface eth10 functions as DHCP server by default so connect your laptop to this interface. This will assign a DHCP IP.

• Optionally, use CLI or local UI to configure eth0 interface for purposes such as WAN connectivity. Use CLI or Local UI to configure registration parameters such as token. Configure the site and approve the registration in Console.

• Default configuration keeps eth10 in inside network and DHCP server enabled.

• If the interfaces eth0, eth1, and eth2 get DHCP IP during bootstrap, this IP can also be used for SSH or local UI. Verify that this IP is displayed on LCD.

Note: The DHCP server is not relevant in this deployment mode. However, it is not disabled by default.

• All interfaces can be L3 interfaces in the same subnet or different subnets.
• This model does not support stacking since there is always L3 connectivity between nodes on all interfaces.

Note: It is recommended to configure loopback IP and dynamic routing (BGP) for high availability with multiple L3 interfaces.

---

Certified Hardware Types

The F5 Distributed Cloud hardware or certified hardware is categorized into types of sites based on the intended usage. The following site types are supported:

• Ingress Gateway: Single interface deployment used in cloud.
• Ingress/Egress Gateway: Dual interface deployment used in cloud. The SDWAN-2 functionality is not supported currently.
• DC Cloud Gateway: Used in private DC. It can have 2 interfaces but can only be deployed as single interface site as the other interfaces are tunnels. The SDWAN-2 functionality is not supported currently.
• CPE: Deployed always as default gateway with 2 interfaces. The DHCP server and SDWAN-2 features are supported.

Note: All site types can be optimised Mesh or F5® Distributed Cloud App Stack.

The following chapters present the various hardware types and usage scenarios:

igw-5000-series-voltstack-combo

This hardware type can be used for the following scenarios:

• Branch office CPE (clustering not recommended)
• DC cloud gateway
• Voltstack cluster

The following are the default interface settings:

• eth0 is dedicated outside interface
• eth1-eth3 are for regular use
• LTE is dedicated outside interface
• Wi-Fi is dedicated outside interface

Note: Use eth3 to connect laptop or DHCP client on eth1 and eth2 while being on same LAN.

igw-5000-series-voltmesh

This hardware type can be used for the following scenarios:

• Branch office CPE (clustering not recommended)
• DC cloud gateway

Note: Clustering is supported as long as outside interfaces can communicate with each other. However, it is not recommend for CPE use.

The following are the default interface settings:

• eth0 is dedicated outside interface
• eth1-eth3 are for regular use
• LTE is dedicated outside interface
• Wi-Fi is dedicated outside interface

Note: Use eth3 to connect laptop or DHCP client on eth1 and eth2 while being on same LAN.

igw-5000-series-cluster-voltmesh

This hardware type can be used for the following scenarios:

• Branch office CPE (recommended for clustering)
• DC cloud gateway

The following are the default interface settings:

• eth0 is dedicated outside interface
• eth1-eth2 are used for stacking
• eth3 is for regular use
• LTE is dedicated outside interface
• Wi-Fi is dedicated outside interface

Note: Use eth3 to connect to the laptop.

igw-5000-series-proxy-voltmesh

This hardware type can be used for the following scenarios:

• Cloud Proxy Custer

The following are the default interface settings:

• eth0 is dedicated outside interface
• eth1-eth2 are used for stacking
• eth3 is dedicated inside interface
• LTE is dedicated outside interface
• Wi-Fi is dedicated outside interface

Note: Use eth3 to connect to the laptop.

isv-8000-series-voltstack-combo

This hardware type can be used for the following scenarios:

• Branch office CPE (clustering not recommended)
• DC cloud gateway
• Voltstack cluster

The following are the default interface settings:

• eth0 is dedicated outside interface
• eth1-eth10 are for regular use
• LTE is dedicated outside interface
• Wi-Fi is dedicated outside interface

Note: Use eth10 to connect laptop or DHCP client on eth1 and eth2 while being on same LAN.

isv-8000-series-voltmesh

This hardware type can be used for the following scenarios:

• Branch office CPE (clustering not recommended)
• DC cloud gateway

Note: Clustering is supported as long as outside interfaces can communicate with each other. However, it is not recommend for CPE use.

This hardware type can be used for the following scenarios:

• eth0 is dedicated outside interface
• eth1-eth10 are for regular use
• LTE is dedicated outside interface
• Wi-Fi is dedicated outside interface

Note: Use eth10 to connect laptop or DHCP client on eth1 and eth2 while being on same LAN.

isv-8000-series-stacking-voltmesh

This hardware type can be used for the following scenarios:

• Cluster CPE
• Branch office CPE
• DC cloud gateway

This hardware type can be used for the following scenarios:

• eth0 is dedicated outside interface
• eth1-eth7 are for regular use
• eth8-eth9 are for stacking
• eth10 is for regular use
• LTE is dedicated outside interface
• Wi-Fi is dedicated outside interface

Note: Use eth10 to connect laptop or DHCP client on eth1 and eth2 while being on same LAN.

isv-8000-series-proxy-voltmesh

This hardware type can be used for the following scenarios:

• Cloud Proxy Cluster

This hardware type can be used for the following scenarios:

eth0 is dedicated outside interface eth1-eth9 is for regular use eth10 is dedicated inside interface LTE is dedicated outside interface Wi-Fi is dedicated outside interface

Note: DHCP client is on management interface with the interface being in the same LAN.