Skip to main content
All CollectionsGetting Started with Celona 5G LAN
Network Domain Configuration - Pre 2406
Network Domain Configuration - Pre 2406

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

P
Written by Puneet Shetty
Updated this week

Note - Following documentation is applicable for Edge Cluster running pre-2406 software release.

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

Configuring Network Domains with Celona Edge Clusters

As explained in detail in this article, Network 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 Network Domains.

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

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

Configure an Internal Network 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 Network Domain.

Configure an External Network Domain

External Network 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 -

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 Network domains configured in the cluster

Configuring your External Network Domain:

The following interfaces need to be configured to setup an External Network 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 the VRRP IP Address only. The VRRP ID is auto-populated from the last octet of the VRRP IP Address, but can be edited if necessary.

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 Network 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 Network 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 Network Domain directly to the default VLAN of the Celona Edge primary interface.

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

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

Did this answer your question?