All Collections
Getting Started with Celona 5G LAN
IP Domain Configuration
IP Domain Configuration

Translate cellular wireless to existing enterprise network resources for L2/L3 traffic forwarding

Team Celona avatar
Written by Team Celona
Updated over a week ago

IP Domain configuration is used to translate your private mobile network resources to the existing L2/L3 network configuration on your infrastructure.

Configuring IP Domains with Celona Edge Clusters

As explained in detail in this article, IP Domains help translate cellular wireless to existing enterprise network resources for L2/L3 traffic forwarding.

Related network policies are managed via the Celona Orchestrator: select Edge Clusters from the side-nav menu in the Orchestrator to start. From the list of clusters displayed, select the name of the Edge Cluster for which you will be configuring the IP Domains.

Toward the end of the page, you will see two options to Add Internal IP Domain or Add External IP Domain. Note that multiple IP Domains of various types can be configured on each Celona Edge Cluster.

Internal IP Domains are fully managed by Celona Edge; the default IP Domain on every Celona Edge is Internal, NAT mode. Additional Internal, NAT mode domains can be added.

Configure an Internal IP Domain

  • Define the start and end IP address of the DHCP range that will be provided by Celona Edge.

  • Set custom DNS servers if required. Otherwise, devices will default to using Primary - 8.8.8.8, Secondary - 1.1.1.1.

  • Click Add to save your new Internal IP Domain.

Configure an External IP Domain

External IP Domains connect an existing VLAN or subnet to a specific Device Group in your private mobile network.

The Celona Edge OS now supports DPDK to extract the best performance from the platform as well as support the following advanced networking and enterprise integration features -

  • Supernetting

  • L2 bridging for industrial applications such as PROFINET

More details on Network Requirements to support DPDK here

The Celona Edge OS support for DPDK requires additional IP addresses for Edge Cluster operations. The number of additional IP addresses needed per cluster will depend on the:

  • Number of nodes in the cluster

  • Number of IP domains configured in the cluster

Configuring your External IP Domain:

The following interfaces need to be configured to setup an External IP Domain for your devices connecting to the Celona network

  1. VRRP ID and VRRP IP address

  • This interface will only be available when the edge cluster has at least 3 nodes. [Refer here for additional details on VRRP requirements to support Multi-node Edge Cluster Configuration for High Availability and Scaling.]

  • Users are required to provide both the VRRP ID and VRRP IP address if configured.

2. Edge ↔︎ Enterprise LAN data plane interface (N6/UPF)

  • This interface is configurable once the VLAN ID is specified as a part of the External IP Domain configuration.

  • DHCP is enabled by default for this interface, if VLAN ID is specified.

  • If a user would like to provide Static IP configuration for this interface due to the unavailability of DHCP, click the Static button to expand the section and enter the static IP address per edge node assigned to the cluster, the Subnet Mask, and the Default gateway.

3. AP ↔︎ Edge data plane interface (N3/S1-U)

  • DHCP is enabled by default for this interface.

  • If a user would like to provide Static IP configuration for this interface due to the unavailability of DHCP, click the Static button to expand the section and enter the static IP address per edge nodes assigned to the cluster, Subnet Mask and the Default gateway.

  • Users are required to provide values in all the fields in this section or leave all values empty.

4. DHCP Server

  • If DHCP is selected for all interfaces, specify the IP address or subnet of the DHCP server in your existing network that will provide IPv4 addresses to devices in this IP Domain. Leave it blank to broadcast the DHCP request.

NOTE: Celona Edge switch interface should be a trunk port, with native VLAN untagged for management and tagged VLANs for client traffic forwarding

  • Once added, Celona Edge will create a corresponding VLAN sub-interface on its primary interface and request an IP address via DHCP broadcast on that VLAN. Leaving this blank connects the IP Domain directly to the default VLAN of the Celona Edge primary interface.

See how to assign the IP Domain policy created to a Device Group here .

You are now ready to connect devices to your Celona network.

Did this answer your question?