Network Prerequisites
OmniVista Terra Internet Access
OmniVista Terra (OV Terra) is installed as an on-premise Network Management System that may or may not have access to the Internet. If the OV Terra installation does not have Internet access, then some of the features may not function. For example:
IoT Categorization default list
IoT Category & Manufacturer details about each client
OpenStreetMap
Rainbow integration
SMS gateway
Email integration, if Gmail Enterprise (or other email applications) are used.
The email server specified in the SMS Settings of the OmniVista Admin Center must be reachable from OV Terra. If the server is internal to the network, then the email server is reachable. However, if an external email server is used for the network, then access to the server is mandatory to support several critical functions, such as Invite User, Forgot Password, and receiving emails for Reports and Alerts.
The OV Terra installation is connected to a gateway in the network. To provide selective Internet access for specific features, you can define rules either on the gateway or on a firewall within the network to allow traffic from OV Terra to specific IP addresses and ports.
If you decide to not open access, then the features that require Internet access will not function.
Device Connectivity to OmniVista Terra
To ensure the necessary communication between devices (Access Point/Switch) and OmniVista Terra 10.5.1, verify/configure the following Network Deployment, Bandwidth, Proxy, Firewall, and NTP Servers configurations must be verified/configured on your local network before using OmniVista Terra.
Network Deployment
Verify the following DHCP deployment requirements are met:
Standard Requirements
IP Address - DHCP Server IP address.
Option 1 - Subnet Mask.
Option 2 - Gateway.
Option 6 - Domain Name Servers - Required for FQDN resolution of OmniVista Terra connection points.
Option 28 - Broadcast Address. This option is only recommended, not required.
Option 42 - NTP Server(s) - Required for Certificate validation (start date and duration), and all related encryption functions. This option is not required; however, it is recommended.
ALE Specific Requirements
Option 43
Sub-Option 1 - Vendor ID. Validate the DHCP response (must be set with the value alenterprise). This sub-option is only required if you specify any of the sub-options listed below.
Refer to Access Point Onboarding Workflow for information about configuring Option 43 to onboard Stellar Access Points for OmniVista Terra to manage.
The following Sub-Options are only required if you are using a Proxy to connect to the Internet.
Sub-Option 129 - Proxy URL. It can be either an IP address or a URL (e.g., "IP-address=4.4.4.4", "URL=http://server.name").
Sub-Option 130 - Proxy Port.
Sub-Option 131 - Proxy User Name. If the customer proxy access requires authentication, both 131 and 132 can be supplied via these sub-options.
Sub-Option 132 - Proxy Password.
Sub-Option 133 - Network ID.
Option 138 - Remove any existing configuration (required for all ALE Devices).
Bandwidth Requirements
Onboarding
For basic onboarding of devices and connection to the OmniVista Terra Server, a minimum of 10 kbps end-to-end network throughput is required between the device and OmniVista Terra.
Advanced Management
To enable statistics data transfer, status queries, configuration commands, and other requests/responses between devices and OmniVista Terra, a minimum of 64 kbps end-to-end network throughput is required between the device and OmniVista Terra. APs must be running the latest AWOS software version specified in Device Prerequisites.
Proxy Requirements
If a device is accessing the Internet via an HTTP/HTTPs proxy, the proxy server must be specified in DHCP Option 43, Sub-option 129 (Server) and Sub-Option 130 (Port). The server may be specified in 1 of 2 formats: 1) “URL=http://server.domain”, or 2) “IP-address=x.x.x.x”. The port is specified as a number (8080).
Firewall Requirements
The following ports must be configured to allow outbound traffic from your local network:
443 - If you are not using a Proxy to connect to the Internet, your firewall must allow outbound access to this port; if you are using a Proxy, you need to be able to access this port via your local proxy.
123 - Relevant if you are using an NTP Server that is outside of your network. You must ensure that your firewall allows outbound access to port 123 UDP. This access cannot be mediated by a proxy, it must be direct (NAT is allowed). In addition, open this port for the following:
clock1.ovcirrus.com
clock2.ovcirrus.com
clock0.ovcirrus.com
clock3.ovcirrus.com.
53 - Relevant if you are using a DNS Server that is outside of your network. You must ensure that your firewall allows outbound access to both port 53 TCP and port 53 UDP. This access cannot be mediated by a proxy, it must be direct (NAT is allowed).
NTP Server Requirements
An NTP Server(s) is required for Certificate validation (start date and duration), and all related encryption functions. Devices must have access to at least one NTP Server, whether local or external. Note that if a device's System Time is not correct, it may take several attempts to synchronize with the NTP Server before the device connects to the OmniVista Terra Server.