Note: Starting with the 2406 software release, the terminology in Celona Orchestrator has been updated from “IP Domains” to “Network Domains” to better reflect the enhanced functionality.
For Edge Clusters running Pre-2406 software, please refer to the legacy documentation here.
This guide is applicable for Edge Clusters running the 2406 software release or higher.
Overview
The Network Domain configuration enables seamless integration of your private mobile network resources with the existing Layer 2 (L2) or Layer 3 (L3) network infrastructure. This functionality simplifies network resource allocation and optimizes traffic forwarding within your enterprise 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 addressof the DHCP range that will be provided by Celona Edge.Set
custom DNSservers if required. Otherwise, devices will default to usingPrimary - 8.8.8.8,Secondary - 1.1.1.1.Click
Addto save your newInternal 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.
With the 2406 software release, these domains can be created as Layer 2 or Layer 3 domains, providing flexibility in configuration and simplifying IP address management.
Layer 2is the default option and applicable for most common customer use cases, such as mapping Private Cellular device traffic to untagged and tagged enterprise VLANs.An example of the simplification and streamlining - in Layer 2 mode, you do not require - additional N6/UPF and VRRP IP address for HA Cluster.
Go here to proceed with Layer 2 External Network Domain configuration.
Layer 3External Network Domain should be used only for advanced use-cases that require layer 3 routing such as - Supernetting, Using Layer GRE or VxLAN tunnel or Multicasting.Go here to proceed with Layer 3 External Network Domain configuration
Layer 2 External Domain
1. Network Interface
Network Interfaceselection is applicable if physical separation (Layer 3) of traffic from different device groups on separate network interface cards (NIC) is desired. For instance, if separate dedicated LAN infrastructure is in place to support IT and OT traffic.If physical separation of traffic is not required, leave
Network Interfaceselection to the default value.Please refer documentation here for more details.
2. VLAN ID
Select logical VLAN segment or subnet to map Private Cellular devices to for layer 2 segmentation.
3. Device IP allocation
Choose between DHCP (default) or Static IP address allocation for Private Cellular devices. If using DHCP, the request will be broadcast on the specified VLAN segment.
For further details on Static IP allocation, refer this documentation.
Layer 3 External Domain
1. Network Interface
Network Interfaceselection is applicable if physical separation (Layer 3) of traffic from different device groups on separate network interface cards (NIC) is desired. For instance, if separate dedicated LAN infrastructure is in place to support IT and OT traffic.If physical separation of traffic is not required, leave
Network Interfaceselection to the default value.Please refer documentation here for more details.
2. 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.
3. Edge ↔︎ Enterprise LAN data plane interface (N6/UPF)
Select logical VLAN segment or subnet to map Private Cellular devices to for layer 2 segmentation.
This interface is configurable once the VLAN ID is specified as a part of the External Network Domain configuration.
This interface is configurable once the VLAN ID is specified.
DHCP is enabled by default; static IP configuration is available if needed.
If a user would like to provide Static IP configuration for this interface due to the unavailability of DHCP, click the
Staticbutton to expand the section and enter the static IP address per edge node assigned to the cluster, the Subnet Mask, and the Default gateway.
4. Device IP allocation
Choose between DHCP (default) or Static IP address allocation for Private Cellular devices. If using DHCP, the request will be broadcast on the specified VLAN segment.
For further details on Static IP allocation, refer this documentation.
Additional Considerations
The Celona Edge switch interface should be configured as a trunk port, with native VLAN untagged for management and tagged VLANs for client traffic forwarding.
Upon adding an External Network Domain, the Celona Edge creates a corresponding VLAN sub-interface on its primary interface and requests an IP address via DHCP broadcast on that VLAN.
Assigning Network Domain Policies to Device Groups
Once your Network Domain is configured, you can assign it to specific Device Groups. Follow the detailed instructions here to complete the process.
You are now ready to connect devices to your Celona network.