Various Advanced Network Configuration options can be done from the Enea Edge Management application GUI.

The Device Call Home option enables the initiation of the connection between the uCPE Device and the Enea Edge Management application, from the uCPE device. The Device Call Home option is required when deploying a uCPE device behind NAT since the IP address of the uCPE device is hidden for the Enea Edge Management application. Enable Device Call Home by marking the Device Call Home checkbox when registering the uCPE device in Enea Edge Management application. When using this mechanism, the device will initiate a connection to the Enea Edge Management application for NETCONF traffic (over SSH), while the application waits for a device connection.

The following describes the steps required for setting up the virtualization infrastructure, ensuring that a uCPE device has networking setup for virtualized service deployment. Networking is enabled by selecting physical interfaces to be used by virtualized networking and creating different types of bridges to enable VNF communication. The Zero Touch Provisioning mechanism is also touched upon, as an alternative to manual configuration of the virtualization infrastructure.

DPDK is an important functionality for accelerating networking performance. The DPDK is enabled by default and should be utilized in most configurations. In use cases where CPU capacity is very limited, disabling DPDK can free up CPU capacity and overall performance can improve. Navigate to Configuration, then DPDK and deselect Enable DPDK to disable the DPDK. Disabling the DPDK cannot be done after other network configurations have been made. In the Configuration menu, select DPDK, here DPDK resources can also be configured: LCore Mask. Allocated cores for non-datapath OVS-DPDK threads (CPU core bitmask). Default: 0x2. PMD CPU Mask. Allocated cores for datapath processing (CPU core bitmask). Default: 0x4. Socket Memory. Hugepage memory allocated for DPDK. Default: 1494.

Once a management connection with the uCPE device has been established by using any of the supported methods, the virtualization networking infrastructure can be configured either manually or by using Zero Touch Provisioning. Available network interfaces can be added to the management system, for use by the networking virtualization infrastructure. In order to make physical network interfaces available to the virtualization infrastructure and VNFs, they must be configured into the management system. To add an interface into the Enea Edge Management application, select the uCPE device, then from the top toolbar select Configuration, then External Interfaces, Configuration, and click the Add button. The available Interface types are detailed below.

Configuring a physical interface in DPDK mode will require a DPDK-based application (e.g. OVS-DPDK) in order to access and use the interface. An interface set as DPDK can be attached to an OVS-DPDK bridge. Make sure the Enable DPDK checkbox is selected by accessing Device, Configuration and choosing DPDK, otherwise no interface can be assigned as DPDK. To add a DPDK interface under the management system, set appropriate values for the following fields: Source: name of the physical interface. Networking-type: dpdk Dpdk-type: the kernel module that allows user space access to the physical interface. Either the vfio-pci (most commonly used type) or the igb_uio driver can be used.

SR-IOV technology allows for the creation of a number of virtual functions on the host interface, which can be used by VNFs running on the uCPE device. For SR-IOV mode configuration, the user must set values for the following fields: Source: name of the physical interface. Networking-type: srIov sriov-mode: adapter-pool sriov-num-vfs: the number of virtual functions to create.

Some of the physical network interfaces available on a uCPE device, including Ethernet interfaces, do not have DPDK or SR-IOV support. Instead, the Linux kernel driver has to be used. To add Standard Interfaces under the management system, the user must set values for the following fields: Source: the name of physical interface. Networking-type: standard.

WAN interfaces configured during the installation of the uCPE device are automatically added in the Enea Edge Management application as type wan. The WAN interface used for management of the uCPE device is marked with the Management property set to True. If a WAN interface is to be assigned for use by a VNF, it must be changed into another interface type depending on the type of connection that will be used. The management WAN interface cannot be changed to a different type. It is automatically used when an In-band management bridge is created. How to Edit the Configuration of a Wan Interface To edit an interface configuration type from the Enea Edge Management, select the uCPE device, then from the top toolbar select the Configuration menu, then External Interfaces and Configuration. The already configured interfaces are displayed here, as seen in the figure above. In order to edit an already configured interface, (as in the example pop-up shown below, a WAN interface) double click on the desired one and a pop-up will appear. A different pop-up appears for each type of interface. From the Host Interface window, a user can change the networking type and the IP address assignment:

When changing the address-assignment from static to DHCP, if any of the ip-address, netmask, gateway or dns-servers fields have invalid values a validation error will be triggered. These fields must be empty or have the valid values for their respective address assignment.

Wireless Access Point (Wap) interfaces are used to create Wireless Access Points. Only interfaces with wap-capable capabilities can be added as WAP interfaces. How to edit the Configuration of a Wap Interface To edit an interface configuration from the Enea Edge Management, select the uCPE device, then from the top toolbar select the Configuration menu then External Interfaces and select Configuration. The already configured interfaces will be displayed here. In order to edit an already configured interface, (as in the example pop-up shown below, a WAP interface) double click on the desired one and a pop-up will appear. A different pop-up appears for each type of interface. From the Host Interface window, the following parameters are configurable: Country Code: the country code, a 2 letter ISO3166-alpha2 identifier. Wireless Band: 2.4 GHz or 5 GHz. Depending on the band selection, the correct Wireless Mode and Radio Channel must be provided.

Correct Country Code selection is mandatory. All configuration options are available in the Enea Edge Management application GUI but only the Radio Settings that conform with the selected country's official regulatory laws will be applied when the Wireless AP is started on the uCPE Device.

For Manual Configuration of uCPE networking, select the uCPE device first, then access the Configuration menu, and choose External Interfaces, where a list of available network interfaces and their capabilities can be found. After networking interfaces have been added to the Enea Edge Management, the user can change the interface type (DPDK, SR-IOV, Standard, WAN, WAP).

After networking interfaces have been added to the Enea Edge Management, the user can create the necessary OVS bridges.

How to add OVS bridges in the Enea Edge Management Select the uCPE device. Select Configuration. Click OpenvSwitch. Select the Bridges option, then click Add. Depending on the settings found when accessing the Configuration menu and selecting DPDK, OVS bridges with or without DPDK support will be used on the uCPE device. There are three types of bridges which can be created, each one fulfilling a different role.

In-band Management refers to a model where both the data plane and control plane flow over the same network path. In some situations (e.g. the uCPE device has only one routable IP address), this is the only option available to both control and configure the uCPE device, while also allowing for data-path traffic to pass over the same physical interface. The solution provided by Enea for in-band management is based upon an OpenvSwitch bridge managing all traffic passing through the WAN physical port. Any standard or DPDK-assigned network interface can be used for the In-Band management bridge. To create the In-Band Management bridge, the user must set values for the following fields: name: name of the bridge. ovs-bridge-type: inbandMgmt

If VNF management can be done over a dedicated virtual interface, its possible to extend the networking infrastructure configuration to also access the VNF's management interface over the WAN port. For this setup, three types of traffic will pass over the WAN physical interface: Device management. Part of the device configuration done by the Enea Edge Management application. VNF(s) management. Enabling or disabling features of a VNF. E.g. enabling/disabling the firewall or VPN setup. Data-path. All other traffic that is not used in the control plane and needs to reach a LAN network. To create a VNF In-Band Management bridge, the user must set values for the following fields: name: name of the bridge. ovs-bridge-type: vnfMgmt vnf-mgmt-address: select IPv4 as the type and fill in an internal IP address for the bridge interface that will be connected to the VNF management network, e.g 10.0.0.1. VNF management interfaces must be configured in same subnet as that used by the bridge interface connected to the VNF management network.

Data-plane bridges are generic bridges used for the VNF data-plane. There are two supported sub-types: communication: Allows for VNF communication towards LAN/WAN networks. This bridge type has at least one physical port attached to it. Allows for creation of Wireless Access Points. This bridge type does not need a physical port attached to it. integration: allows for VNF-to-VNF communication (usually for service function chaining). This bridge type does not have any physical port attached. To create a Data-plane bridge, the user must set values for the following fields: name: name of the bridge. ovs-bridge-type: select communication or integration, depending on intended usage. For communication bridges, physical interfaces can be added to the bridge.

Zero-Touch Provisioning (ZTP) refers to the process of when a device starts up for the first time and its initial configuration is pushed down by an external management system, so that it is setup for proper operation without additional manual intervention by an operator. ZTP is an alternative to Manual configuration. A variety of operations can occur as part of ZTP such as initial device setup, configuration of managed objects, etc. The goal is to set up a device to the maximum possible extent without forcing an operator to be physically present (initially) to manage the device. An offline configuration is usually prepared in advance for the Enea Edge Management to setup the virtualization infrastructure on the uCPE device, as soon as a device enrolls into the management system.

The Offline Configuration subsystem is used to pre-populate a configuration for a device that will be brought under management at a future point in time. When creating an offline configuration store a Device ID can be specified. This ID uniquely identifies the device to be initialized. Alternatively, a wildcard can be used in the Device ID field, which results in a configuration being pushed on all uCPE devices upon their initial connection towards the Enea Edge Management. If the offline configuration is not configured for a uCPE device, an alarm will be raised: Day-0 Config:ZTP:Major, which occurs when the uCPE device connects to the Enea Edge Management application informing that the ZTP setup failed for the specific uCPE device. To create an offline configuration, select from the top toolbar the Applications menu, then Offline Config and choose Add. The following fields should be filled: Name: name of the device. Device type: Enea universal CPE. DeviceVersion: Config Set: uCPE Config Device ID: device ID or a wildcard(*). Device Grouping Tags: a tag to group devices. These tags match the customer tags provided during the installation of the device. The Name is user defined and can be set to any unique text string identifying the configuration. The Device Version will match the Enea Edge version of the uCPE device and the Device ID will be set to the previously set identifier of the uCPE device. When a device connects to the Enea Edge Management application for the first time, it checks the device to see if it has been Zero Touch Provisioned (ZTP). If not, it looks for an offline configuration that matches these values, in the following order: The Device ID. The set of tags. A "*" for Device ID (wildcard). If a match is found, the offline configuration is sent to the device as part of Zero-Touch-Provisioning. After creating the Offline Config Store, access the device by selecting Applications, then offline config and clicking Config App, to provision it with the required initial configuration. This operation mirrors what happens during manual configuration described previously. The ZTP will only be triggered the first time a uCPE device connects to the Enea Edge Management application. Just changing an offline configuration will not push the new changes to the device. If an offline configuration is changed after uCPE device registration, a factory reset can be executed to force a new ZTP to execute. Select the device, then access the Operations menu and select factory reset.

The custom scripts feature allows users to execute user-defined scripts on the uCPE device at various times. This allows for more flexible and advanced configurations such as a LTE modem configuration, advanced network configurations or OVS flow rule programming at any time. In the current Enea Edge Management application version custom scripts are not supported as part of the offline config.

The scripts need to be uploaded to the Enea Edge Management application prior to use. When uploading scripts to the Enea Edge Management application make sure to select the right script type. The following script types are supported: Once-before-startup. This script will only execute once after the system has rebooted, prior to processing any device configuration. Always-before-startup. This script will always execute after the system has rebooted, prior to processing any device configuration. Once-after-startup. The script will only execute once after the system has rebooted, after all device configuration processes have completed. Always-after-startup. This script will always execute after all device configuration processes have completed after the system has rebooted. After a factory reset, any of the Once-before-* or Once-after-* scripts will be re-run as described above. Follow the instruction below to upload scripts: Access the Devices menu, then Custom Scripts and choose Configure. Select Upload to EMS. In the Script Type menu, select the type the uploaded script should have. Press Choose File to select the scripts needed, and then click Send. If two scripts are uploaded one at a time, the Enea Edge Management application will delete the first script already added from the device and apply the new one. In order for both scripts to be available on the device, both scripts must be uploaded at once. If multiple custom scripts of the same type are uploaded at the same time, they are executed in alphabetical order.

Follow the instruction below to remove scripts from the Enea Edge Management application: Access the Devices menu, then Custom Scripts and select Configure. Select the script you want to delete from the Uploaded Scripts tab and then click Delete, which will remove the script immediately from the Enea Edge Management application.

The location where the scripts are staged in the Enea Edge Management application can be changed as described below: Access the Devices menu, choose Custom Scripts and select Configure. Select the Configuration tab and specify a new location to store the scripts. Change the script storage location only if you have many scripts which you would prefer to store on another partition, otherwise leave this configuration as is.

How to run Custom Scripts Access the Devices menu, choose Custom Scripts and select Apply Scripts. In the Script Config Screen pop up, select the devices from the device(s) chooser list on which to run the scripts. Press the > button to move the devices to the right side of the chooser, which is the list of devices that will execute the selected scripts. Select the scripts from the list under the device(s) chooser by pressing the + button. In the pop-up window, select the scripts from the list. If there are no scripts to select, then there is no script uploaded with that particular type. Upload the script(s) needed and try again. Check the Reboot devices checkbox if you want to reboot and execute the scripts at once and then select ok. The status of execution for the scripts can be seen by accessing Fault, opening the Events screen and filtering by device and/or the event name CustomScriptExecuted.

Follow the instructions below to remove scripts from a uCPE Device: Access the Operations menu and select Delete Custom Script. In the Delete Custom Script pop up, set the name and the type of the script that should be deleted and press Execute. If the Script Type remains unset, the script will be deleted regardless of its type.

The Wireless AP Screen from the Enea Edge Management Configuration menu allows users to configure a Wireless Access Point. A wap-capable interface and a LAN bridge must be added before doing the Wireless AP configuration. For more details see sections Wap interface Type and Data-plane bridge. The following parameters are configurable: SSID: the Wireless network name - any string with a max. length of 32 octets. Interface Name: the wap-capable external interface. Lan Bridge: the LAN bridge where wireless clients will be hosted. WAP Security Mode: open or wpa2Psk. When choosing wpa2Psk, a password and an encryption must be provided. The password can be any string with a minimum length of 8 and a maximum length of 63 characters. DHCP Server: disabled or enabled. When enabled is selected, the range of IPs (IP Address Start - IP Address End), Netmask and Gateway values must be provided.

Only a single Wireless AP is allowed on a physical interface. The validation of the wap-capable interface is done when adding the Wireless AP, so, in case of an error, the parameters of the wap-capable interface must be rechecked. This can be done by accessing the Configuration menu and selecting External Interfaces. For the 2.4GHz band, the 802.11 g/n wireless mode will use a 40MHz channel width by default. For regulatory requirements compliance, channels are scanned in order to avoid overlapping with existing networks. If overlaps are detected, primary and secondary Wireless AP channels will be swapped, resulting in an effective channel width of 20MHz instead of 40Mhz being used. To avoid this, select another wireless channel. For the 5GHz band, the 802.11 n and the 802.11 ac/n wireless modes can be configured explicitly to use a specific channel number, even when Automatic Channel Selection (ACS) is available. For regulatory requirements compliance, channels are scanned in order to avoid overlapping with existing networks. If overlaps are detected, ACS will try to find another free channel, resulting in a different channel number being used instead of the one explicitly configured. To avoid this, select another wireless channel.