API Developer Portal
API Docs
Community
Knowledgebase
Training
menu icon
  1. Home
  2.  / How To
  3.  / Advanced Networking
  4.  / Create Subnet

Create Subnet

On This Page:

Objective

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.

Prerequisites

The following prerequisites apply:

Create Subnet

Create a subnet object for each interface you plan to use.

Step 1: Navigate to subnets menu.
  • Log into Console and then select Multi-Cloud Network Connect.
Figure
Figure: Console Homepage

  • Navigate to Manage > Networking > Subnets.

  • Select Add Subnet.

Figure
Figure: Add Subnet
Step 2: Configure subnet object.
  • Enter Name for subnet object.
Figure
Figure: Subnet Name

  • Select Edit Configuration in the Site Subnet Parameters section.

  • From the Site drop-down menu, select your site.

  • Select Configure in Subnet DHCP Networks section.

Note This configuration is only required for subnets with the Network Connection Type set to Connect to Site Local Outside Network and 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 Interface option.

Figure
Figure: Subnet DHCP Configuration
  • In the Network Prefix box, enter a value for your subnet.
Figure
Figure: Subnet DHCP Prefix

  • Select Apply to apply DHCP network.

  • Select Apply.

  • In the Network Connection Type menu, 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 pod itself. Static IP configuration is not supported for VMs. If you select this option, use the Layer2 Interface menu to select the network interface previously created.

Note: Static IP configuration using the manifest file will not be supported for virtual machines. It will only be supported for pods.

Figure
Figure: Complete Subnet Object Configuration
Step 3: Complete creating object.

Select Save and Exit.

Concepts

© 2024 F5, Inc. All rights reserved | Trademarks | Policies | Privacy | California Privacy | Do Not Sell My Personal Information |