E2E Controller

Overview ............................................................................................................................................................................................ 4
60 GHz cnWave E2E controller ............................................................................................................................................ 4
Supporting Nodes .................................................................................................................................................................. 4
cnMaestro Management Overview ...................................................................................................................................... 4
Supported Virtualization Infrastructures ........................................................................................................................... 5
Hardware Requirements .......................................................................................................................................................... 5
Inbound TCP Port Requirements ...................................................................................................................................... 6
Software Version .................................................................................................................................................................... 6
IPv6 Configuration ................................................................................................................................................................. 6
Quick Start Guide ........................................................................................................................................................................... 7
60 GHz cnWave E2E Controller Installation .................................................................................................................... 7
Desktop Virtualization .......................................................................................................................................................... 7
Bare Metal Hypervisor .......................................................................................................................................................... 7
Downloading and Deploying the OVA procedure ..................................................................................................... 7
Initializing E2E Controller ........................................................................................................................................................ 9
IPv4 Configuration ................................................................................................................................................................. 9
cnMaestro Management Server Configuration ........................................................................................................... 11
Initialize E2E Controller ........................................................................................................................................................ 11
60 GHz cnWave E2E Controller Architecture ....................................................................................................................15
Operations Menu............................................................................................................................................................................15
VM console ...................................................................................................................................................................................15
Information Page ...................................................................................................................................................................15
Network Page .........................................................................................................................................................................15
cnMaestro Configure Management Server Page ..................................................................................................... 20
Settings ................................................................................................................................................................................... 20
Password ................................................................................................................................................................................. 22
Maintenance ........................................................................................................................................................................... 22
Kibana UI ................................................................................................................................................................................. 24
Halt .............................................................................................................................................................................................25
Reboot ......................................................................................................................................................................................25
Shell ...........................................................................................................................................................................................25
Logout ..................................................................................................................................................................................... 26
About ....................................................................................................................................................................................... 26
Technical Support Dump ...................................................................................................................................................... 26
Apply 60 GHz cnWave E2E Controller Package Update ......................................................................................... 26
Backup and Restore Options ............................................................................................................................................... 27
Multiple Interfaces .................................................................................................................................................................... 27
Overview .................................................................................................................................................................................. 27
Policy-Based Routing .......................................................................................................................................................... 27
VMware Interface Order ........................................................................................................................................................28
Overview ..................................................................................................................................................................................28
 VMware Workstation ......................................................................................................................................................... 29
VMware ESXi ......................................................................................................................................................................... 29
Troubleshooting ........................................................................................................................................................................... 30
Cambium Networks 60 GHz cnWave solution provides easy, fast and cost-effective wireless gigabit
connectivity for edge access and/or high capacity backhaul at a significantly lower TCO than fiber
infrastructure. Service providers and enterprises can now access gigabit speeds for business and
residential connectivity, local Wi-Fi backhaul or LTE/5G small cell. Certified for cnWave mesh solutions
efficiently handle high-density deployments in cities and suburban areas.

The 60 GHz cnWave E2E Controller is a customer managed service that allows configuration, control,
and monitoring of the cnWave nodes and mesh network. Its services require network topology
awareness and include establishing wireless links (or "ignition"), software upgrades, and configuration
management.

There are three types of nodes in a cnWave network:

• Distribution Node (DN) - DN connect with other DN to form a mesh distribution network.
• Client Node (CN) - CNs are On-Premises customer radios which connects with a DN node and
provide high speed network access.
• Point of Presence Node (PoP) - DN that serves as the demarcation between the distribution
network and the provider’s PoP backbone network.

DN are the backbone of the network and connect one or more fiber optic PoP nodes to CN nodes-
possibly over multiple hops. Both DNs and CNs are connection points for wireless clients, wireless
access points, and other customer premise equipment (CPE).

V1000 is featured with wide range, 80º beamforming for easy installation. Powered by 802.3af PoE, it
supports up to 2 Gbps with 1 Gbps in the uplink direction and 1 Gbps in the downlink direction.

V3000 is featured with a 44.5 dBi high-gain antenna with beamforming. The client nodes can support
up to 7.6 Gbps with channel bonding for both PMP and PTP configurations.

V5000 is featured with two sectors covering up to 280 degrees with beamforming. A single V5000 can
connect upto four other distribution nodes or up to 30 client nodes. V5000 can be used for PTP, PMP
and mesh configurations.

60 GHz cnWave operates with Cambium Networks’ cnMaestro management system. cnMaestro
simplifies device management by offering full network visibility and zero-touch provisioning. Using
cnMaestro, user can view network status and perform a full suite of wireless network management
functions in real time including optimizing system availability, maximizing throughput, and meeting the
emerging needs of business and residential customers.

The network management architecture is presented below. Each 60 GHz cnWave E2E Controller
executes as a virtual machine within the customer network and fronts a separate cnWave mesh
installation, consisting of up to 500 CN and DN devices. The E2E communicates with cnMaestro over
HTTPS and enables centralized network management. All administration activity for mesh network
devices is through cnMaestro.
All traffic between cnWave Mesh Network devices and the 60 GHz cnWave E2E Controller must be over
IPv6. This is called control traffic in this document. Management traffic is sent between cnMaestro and
the E2E Controller; it can be either IPv4 or IPv6.

The 60 GHz cnWave E2E Controller supports one (eth0) or two (eth0, eth1) interfaces. Most customers
only need a single interface. If you want to segment your network between management traffic and
control traffic, then you can optionally configure eth1. Note in the two-interface configuration, all
management traffic is mapped to eth0 and all control/device traffic is mapped to eth1.

60 GHz cnWave E2E Controller is released as an Open Virtualization Archive (OVA) file. The following
platforms are supported:

Table 1: Supported Virtualization Infrastructures

Platform Details

VMware Workstation/Player Version 12

Oracle VirtualBox Version 6.0 and above

VMware ESXi Version 6.0.0 Update 3 (Build 7967664) or higher (this is

the preferred platform)

60 GHz cnWave E2E Controller must meet the following minimum hardware specifications.

• 2 vCPU
• 4GB of RAM
• 2 x 40GB of disk space

NOTE:

The virtual hardware is different than the physical hardware. Virtual hardware
executes the 60 GHz cnWave E2E Controller application; physical hardware
executes the VMware virtualization infrastructure in addition to the 60 GHz
cnWave E2E Controller application (and possibly other independent
applications).
Port Requirements

443/80 Kibana and other Controller API access from external source.

6881 Used by libtorrent to seed upgrade images.

6969 Open tracker serves the torrent tracker on this port.

7007 Management communication port between 60 GHz cnWave E2E

Controller and nodes.

8002 NMS aggregator listens on this port for stats from nodes.

17077 Used for communication between various 60 GHz cnWave E2E

Controller application.

24224 Fluentd port to push the logs from Devices

The minimum supported version of cnMaestro On-Premises is 3.0.0 and cnMaestro Cloud version 3.1.0.

cnWave60 E2E Controller and Device Network use Unique Local (ULA) IPv6 Address. Below table
describes the range and assignment of the same.

NOTE:

IPv6 reservation:

• If auto assign is chosen, E2E Controller On-Premises and PoP(s)

addresses will be assigned with prefix fd00:ba5e:xxxx:xxxx::/64.
• Device Network seed prefix (device lo interface) IPv6 addresses will be
assigned with prefix fd00:ceed:xxxx:xxxx::/56,64.
• xxxx octets are random and unique for each network.
• cnWave60 E2E Controller On-Premises reserves
fdcf:9573:bfda:ea62::/64 and fdfc:9173:bdfa:ea26::/64 for internal
container services.
Desktop Virtualization executes a virtual machine within an existing operating system environment
(Windows, Mac, or Linux). The administrator installs virtualization software, such as VMware workstation
or Oracle VirtualBox, and it executes in tandem with other desktop applications. 60 GHz cnWave E2E
Controller can then be installed within one of these platforms.

The desktop environment is the easiest way to get 60 GHz cnWave E2E Controller up-and-running
quickly. You can download a trial version of VMware workstation.

A bare metal hypervisor takes over the entire physical machine and uses it to host virtual instances. This
type of virtualization is best for production environments, and it takes time to set it up correctly.
VMware vSphere ESXi is an example of this type of virtualization, and it is discussed in detail in the
appendix. You can download ESXi here.

60 GHz cnWave E2E Controller is deployed using VMware workstation player. Directions for VMware
vSphere ESXi and VirtualBox procedure are found below. VMware workstation player (and Oracle
VirtualBox) tends to be the easiest to install and evaluate, though ESXi is preferred for production.

Download the 60 GHz cnWave E2E Controller Virtual Appliance here.

The steps to import 60 GHz cnWave E2E Controller into Oracle VirtualBox are below.

1. To install OVA File, open Oracle VirtualBox click File > Import Appliance. Select 60 GHz cnWave
E2E Controller OVA file and click Open to import.
2. Click Agree EULA license agreement.

3. Once the EULA is agreed is accepted, 60 GHz cnWave E2E Controller will be imported into the
VirtualBox environment. This process could take several minutes.

NOTE:
If the user planned to have eth1 as the control(device) interface, we
recommend to attach the eth1 interface before powering on the VN appliance.

4. Click Start to start the VM Appliance.

 5. Login to the 60 GHz cnWave E2E Controller Console.
6. The VM Appliance Console is the only way to access the 60 GHz cnWave E2E Controller CLI
(Command Line Interface). Login using the default username/password (cambium/cnwave).

To Initialize E2E Controller user needs to configure IPv4 Address and cnMaestro Management
information mandatorily as shown below.

• In the Initialize Controller page, click Configure to assign IPv4 address and cnMaestro cnMaestro
Management Information.

• In Menu page click on Network to configure IP Addresses

• Navigates to the Network page, select eth0 and click OK.

 NOTE:
• User can configure the IPv4 and IPv6 addresses in eth0 and eth1 (if
attached) interface
• eth0: allows the user to configure both the IPv4 to manage the E2E
cluster and IPv6 to manage devices if eth1 is not attached
• If eth1 is attached, the 60 GHz cnWave E2E Controller uses the IPv6
address to manage devices only from eth1

• In the Configure Interface (eth0) page, select IPv4 from the option and click OK.

• Users can configure Static IPv4 address as shown below in the IPv4 Static IP Configuration.

• Select Static and click OK.

• In IPv4 Static Configuration (eth0), enter the IP Address/Prefix Length and Default Gateway
and click OK.

• Displays the Notice page IPv4 successfully updated on eth0 and click OK
cnMaestro Management allows the user to Configure, Manage, Visualize, and Monitor the network.

Follow the below mentioned procedure to manage the network in cnMaestro On-Premises:

NOTE:
• If the user enables the Cambium ID-based authentication to onboard devices in
cnMaestro > Onboard > Claim for devices page, then the user needs to provide
the onboarding Key.
• User can change the Default URL https://cloud.cambiumnetworks.com.

• By default, cnMaestro URL will be blank and to update navigate to Operations page > click
cnMaestro (In Operations) and change the URL.

• Provide the URL, Cambium ID, Onboarding Key in the Configure cnMaestro Management Server
Page.
• Enter the allowed Log Level value as INFO or DEBUG and click Update.

• After successful URL updation it pops up Notice page, click OK.

• If IPv4 address and cnMaestro Management Information are configured Initialize option will be
enabled.

NOTE:
eth1 is used as control(device) interface in this guide.
• Select Initialize and click Enter. It starts to Initialize the E2E Controller.

• It displays the Notice as E2E Controller has been initialized successfully and click OK.

• Navigates to the Information page and displays the Connection Status as Waiting for approval.

• If connection is successful, user needs to approve the E2E network in cnMaestro UI to make it
onboarded.
• To onboard the network, navigate to the cnMaestro On-Premises > Manage > under System and
it displays the new 60 GHz cnWave E2E Controller network and click Approve.
• After clicking Approve, window pops up 60 GHz cnWave – Network Onboard.
• In 60 GHz cnWave – Network Onboard popup select Auto-assign to update IPv6 address in E2E
Network and wait for a while till IPv6 address gets updated.
• Enable Layer 2 Bridge (Optional based on the user requirement).

• Click Apply.
• Wait for a while till network onboard is successful.

• After successfully onboarded, the Network UI shows the Dashboard of the network as shown in
below screenshot.

• During the first time onboarding of E2E Controller, cnMaestro sets prefix allocation as
Centralized for the E2E Network Configuration with the default subnet prefix XXX and the
subnet prefixes are allocated to all DNs and CNs connecting to this network.
 • Once the network is approved the Information page in the 60 GHz cnWave E2E Controller
displays the cnMaestro Management Information > Connection Status as Connected and
Assigned IPv6 Address.

• For Further information on cnMaestro On-Premises Management refer to

https://support.cambiumnetworks.com/files/cnmaestro/beta

Information page provides details about the 60 GHz cnWave E2E Controller Information, cnMaestro
Management Information, Network Information, and System Information.
The high-level diagram represents the deployment of 60 GHz cnWave E2E Controller and various
containers required to communicate with cnWave nodes and cnMaestro.

Operation page provides the access to the menu of the E2E Controller.

Details about the Information page refer above step.

Network page allows the user to configure the IPv4 and IPv6 as shown below.

User can configure the IPv4 and IPv6 addresses in eth0 and eth1 (if attached) interface:

• eth0: allows the user to configure both the IPv4 to manage the E2E cluster and IPv6 to manage
devices if eth1 is not attached.
• If eth1 is attached, the 60 GHz cnWave E2E Controller uses the IPv6 address to manage devices
only from eth1.
 Warning:
Disabling or changing the IPv6 address in control (device) interface will disconnect
devices.

For the details about the IPv4 Static Configuration refer above step.

• Select DHCP and click OK.

• In IPv4 DHCP Configuration (eth0) page, click Yes

• It displays the Notice page IPv4 successfully set to DHCP on eth0 and click OK

Note:
• IPv6 must be configured in control interface.
• By default eth0 is the control interface. If eth1 is assigned, eth1 will
become the control interface.

• Select eth0 and click OK.

• In Configure Interface (eth0), select IPv6 and click OK.

• In the Configure IPv6 Settings (eth0) page, select static and click OK.

NOTE:
DHCP option is not supported for IPv6.

• In the IPv6 Static Configuration (eth0) page, enter the IP Address/Prefix Length, Default
Gateway. Click Ok.

NOTE:
DNS Name Server 1 and Server 2 are optional. The user can provide
server names as per their requirements.

• It displays the Notice page as IPv6 Successfully Updated and click OK.
To disable the Configured IPv6 address perform as follows:

Warning:
Disabling or changing the IPv6 address in control (device) interface will disconnect
devices.

• Navigate to the Configure IPv6 Settings (etho) page, select Disable and click OK.

• It navigates to the Confirmation Page and click Yes.

• It displays the Notice page as Disabled IPv6 in the interface (eth0) and click OK.

• In the Configure IPv6 Settings (eth0) page displays disabled IPv6 as shown below.

Static routes can be configured incase the External E2E Controller to route the device traffic via
different gateway (eg PoP Node) to seed prefix destination. These are only needed when an external
nodes seed prefix address cannot be accessed using the default gateway (External Router) of eth0
interface.

• To enable the route, navigate to Network page select eth1 and click OK.
• It navigates to the Configure Interface (eth1) page, select IPv6, and click OK

• It navigates to the Configure IPv6 Settings (eth1), select Routes, and click OK

• It navigates to the Manage Static IPv6 Routes (eth1) page where the user can be able to
ADD/Delete the routers.

• Navigates to the Add IPv6 Static Route (eth1) page, enter the Network prefix and click OK.

• To delete the routes, navigate to the Manage Static IPv6 Routes (eth1).
 • Select the Network using the Spacebar key and click Delete.

• It pops up the Notice successfully removed.

Details about the cnMaestro Configure Management Server page refer above step.

60 GHz cnWave E2E Controller uses the Network Time Protocol (NTP) for time synchronization. By
default, NTP is configured to use Google NTP services. NTP can be disabled if the user wants to
leverage the NTP feature of VMware or changed to enable a customized group of NTP servers.

• By default, the NTP is enabled and configured with google time servers.
• To update time servers, navigate to Operation page and select Settings, and click OK.

• In the Server Settings page select NTP and click OK

• Navigates to the NTP Services page, it allows the user to Update NTP configuration custom NTP
servers or Disable the NTP

• After successful NTP updation it pops up Notice and click OK.

• To disable the NTP, navigate to Operation page and select Settings, and click OK.
• In the Server Settings page select NTP and click OK.

• In the NTP Services page, select the NTP Server and click Disable NTP.

• After successful disabling NTP it pops up Notice and click OK.

• To enable the NTP, navigate to Operation page and select Settings, and click OK.
• In the Server Settings page select NTP and click OK.
 • In the NTP Services page, select Enable NTP.

• After successful enabling NTP it navigates to NTP Services page.

Password page allows the user to change the password.

NOTE:
Default password of “cambium” user is cnwave.

The System Maintenance page allows the user to enable/disable the SSH for the Cambium user for
security maintenance.

NOTE:
By default, cambium user’s SSH access is disabled. To enable it, please follow the below
instructions.
• To enable the SSH, navigate to the Operations page select Maintenance, and click OK.

• It navigates to the System Maintenance page, select SSH and click OK.

• It navigates to the SSH server page and click Enable the SSH.

• After enabling the SSH it displays the Notice with the Success status.

• To disable SSH, navigate to the Operations page select Maintenance, and click OK.
• Navigate to the System Maintenance page, select SSH and click OK.

• Navigate to the SSH server page and click Disable SSH.

 • Once SSH is disabled it pops up a Notice page with the Success status. Click OK.

Kibana UI is a data visualization and exploration tool used for log and time-series analytics, application
monitoring, and operational intelligence use cases.

To reset the Kibana UI perform as follows:

• Navigate to Operations page > Select Kibana UI and click OK.

• In Kibana Settings page select Password and click OK

• In Reset Kibana UI Password, where user allowed to reset the password, enter the New and
Confirm Password and click Reset.
 • Once the password has been reset, it displays the success Notice page. Click OK.

• Once the password is reset user can access with the specified Kibana URL with the default
username and reset password as shown below in Troubleshooting.

Halt page allows the user to halt the interface.

• Navigate to the Operations page, select Halt, and click OK.

• It navigates to the Halt page. Click Yes to halt interface.

• Once the Virtual machine is halted the remote connection is closed.

Reboot allows the user to reboot the interface.

Select Shell to exit from the console to the command line.

To select the Shell, navigate to Operations page, select Shell, and click OK.
Logout page allows the user to logout of the interface.

About page provides the version information of the 60 GHz cnWave E2E Controller and minimum
supported version of cnMaestro On-Premises.

Technical Support Dump can be exported from the command line using the following:
sudo /srv/bin/cnwave60-techdump

The location of the file is printed when the command completes. It can then be copied to an external
directory using SCP or FTP and sent to Cambium support personnel.

Package Update can be applied from the command line using the following:
sudo /srv/bin/cnwave60-image patch <package-file>
The upgrade file needs to be copied to the 60 GHz cnWave E2E Controller instance before executing
this command. This can be done using either SCP or FTP. The update file itself is downloaded from
Cambium Networks and only updates the cnwave application.

Backup and Restore Option can be applied from the command line using the following:
sudo cnwave60-data --help

Allows the user to create a backup from the 60 GHz cnWave E2E Controller and to restore the back up
from the specified path available in a different location.

60 GHz cnWave E2E Controller supports a single eth0 interface, or a combination of both eth0 and eth1.
The traffic mapping is expected to follow the specification below.

Name Interface Details

Management eth0 User interface, cluster, API, outbound traffic to Internet.
Device (Control) eth1 Device control traffic.

Note

PCI allocation ordering always allocates the first interface to eth1 and the second interface to eth0
in VMware (Workstation and ESXi) and Virtual Box.

The eth0 interface (management, cluster) supports administration access (UI or API) and clustering
traffic. It requires a Default Gateway, and all outbound traffic uses it by default.

The eth1 interface (device/control) communicates only with cnWave devices. It never initiates
connections, and its Gateway is only used for explicit routing of return packets.
The issue with the above architecture is how does 60 GHz cnWave E2E Controller ensure all traffic
initiated by the device or nodes returns through the eth1 interface? By default, packets to remote
subnets are routed through the Default Gateway, and they may never be able to reach the device. 60
GHz cnWave E2E Controller needs to send all the return packets through the eth1 gateway, without
configuring static routes for every device subnet.

60 GHz cnWave E2E Controller uses policy-based routing on eth1 interface if configured. The basic
configuration of custom routes and rules are below.

Routes:

Rules:

Part of eth1 IPv6 configuration, above route table 206 and rules are created:

• Rule (1) is to manage docker swarm IPv6 inbound traffic.

• Rule (2) any traffic with the source IP address of eth1 should be routed through the eth1 specific
routes in table 206
• Rule (3) is to manage docker swarm IPv6 outbound traffic

Use the following commands to view the status of the IPv6 rules and routes

sudo ip -6 rule show IPv6 rules

sudo ip -6 route show table 206 IPv6 routes for 206

In a two-interface configuration, VMware at times applies Network Interfaces to the virtual machine in
an order different from what is presented in the User Interface. This results in a network expected
mapped to eth0 to instead be mapped to eth1. To resolve the mapping, so the etn0 network is always
mapped correctly, you may need to edit the VMware configuration file. This section details how this is
accomplished.
In VMware Workstation, you need to edit the VMware configuration file (ending in. vmx), which is
present in the same directory as the rest of the virtual machine files. Shut down the virtual machine and
then edit the two entries in the file so the eth0 number is lower than eth1. You may need to make sure
both interfaces are the same type, in which case, you can switch the numbers.

ethernet0.pciSlotNumber = "33"
ethernet1.pciSlotNumber = "34"

The same operation is required for VMware ESXi, but it can be performed through the UI.

• Select Edit Settings for the cnWave E2E VM and choose VM Options > Advanced.

• Scroll down and select the Edit Configuration button.

• This will launch a screen that allows updating the PCI numbers.
Kibana is an open source visualization tool mainly used to analyze a large volume of logs. Kibana works
in sync with Elasticsearch and fluentd which together forms the so called Elasticsearch Fluentd, and
Kibana (EFK) stack.

EFK is the log management platform used for log analysis.

• Fluentd extracts the logging data or other events from different input sources. It processes the
events and later stores it in Elasticsearch.
• Kibana UI is a visualization tool, which accesses the logs from Elasticsearch, and allows the user
to design the graphs, dashboards etc. based on their requirements.

To reset the Kibana UI perform as follows:

• Navigate to Operations page > Select Kibana UI and click OK.

• In Kibana Settings page select Password and click OK

• In Reset Kibana UI Password, where user allowed to reset the password, enter the New and
Confirm Password and click Reset.
 • Once the password has been reset, it displays the success Notice page. Click OK.

Once the password is reset user can access with the specified Kibana URL with the default username
and reset password

NOTE:
Kibana is a significant program, and only a portion of it is used within the 60 GHz cnWave
E2E Controller (primarily log aggregation and visualization). The section below shows how
to access the Kibana UI and view E2E logs.

Follow the steps below to access the Kibana UI:

• Use the Kibana URL and Username mentioned in the reset page of E2E controller.

• Navigates to the Kibana login Page.

• Enter the username (cambium) and password to login.
• Navigates to the Home page.

• In home page user needs to click the button and select Discover to see the logs.

• Navigates to the Index Pattern page.

• All the service and device logs are created as index pattern.
• By selecting the index pattern respective service and nodes log can be viewed.