This guide provides instructions on how to create a subnetwork (or subnet) to subdivide your larger network into smaller and more manageable networks. Each subnet object you create can be configured to transfer or receive services and other data from your Site or group of Sites.
The following prerequisites apply:
A Distributed Cloud Services Site. If you are deploying an App Stack Site, that site must use managed Kubernetes.
Create a subnet object for each interface you plan to use.
Step 1: Navigate to subnets menu.
- Log into Console, select
Multi-Cloud Network Connect.
- Navigate to
Step 2: Configure subnet object.
Namefor subnet object.
Site Subnet Parameterssection.
Sitedrop-down menu, select your site.
Subnet DHCP Networkssection.
Note This configuration is only required for subnets with the
Network Connection Typeset to
Connect to Site Local Outside Networkand
Not Connected to Other Network. Do not configure this option if you are creating VM or pod workloads with VLAN Layer 2 interfaces using the
Connect to Layer2 Interfaceoption.
- In the
Network Prefixbox, enter a value for your subnet.
Applyto apply DHCP network.
Network Connection Typemenu, select an option:
Not Connected to Other Network: The site, VM, or container can only communicate with other sites, VMs, or containers on this subnet.
Connect to Site Local Outside Network: A default route is injected into the site, VM, or container and allows external SNAT'ed communication via the Site Outside Local Network.
Connect to Layer2 Interface: These Layer 2 interfaces act as subnets and have access to the underlay network and bypass the F5 Distributed Cloud Services node data plane. The Layer 2 IP addresses are allocated using an external Dynamic Host Configuration Protocol (DHCP) server or can be static within the VM or pod itself.
Save and Exitbutton to complete creating the subnet object.