Xovis hardware and network requirements

Avatar
Laura CARBO

Difficulty: expert

Content

Learning Objectives

After reading this article, you’ll be able to:

  • Set up your IT network as needed for XOVIS installation

Depending on the Xovis device, connectivity can only happen through LAN/ethernet or also over WiFi.

Xovis WiFi devices are an alternative for customers that

  1. want to have WiFi as a fall-back option to existing LAN connectivity
  2. want to have all the IoT devices running on a specific WiFi network
  3. cannot foresee connectivity through LAN in some places.

Info

Xovis WiFi devices still need Power over Ethernet (POE) for power. This can happen through a POE injector.

Note

XOVIS WiFi devices' initial configuration (of the WiFi credentials) needs to happen while running a LAN/ethernet connection, and while being able to connect to the target WiFi network.

This means that, for the time required for the configuration, a LAN network needs to be available in a location where the target WiFi network is also reachable.

Hardware Requirements

XOVIS sensor devices are a wired solution. So make sure that you are allowed/able to foresee cabling and drill holes in the ceiling where needed.

Xovis using customer LAN/ethernet connectivity

The XOVIS devices using customer LAN/ethernet connectivity need to be powered + connected to the network using Power over Ethernet (RJ 45)

  • The plug and the sensor need to be free from any mechanical pressure.
  • The sensor supports Ethernet 10/100MB Full/Half/Auto negotiation based on the IEEE 802.3 standard.
  • It is highly recommended to set the switch port to auto negotiation.
  • The sensor is powered by PoE Class 0 compliant to IEEE 802.3af. As defined by the standard, the network switch port needs to provide 15 Watts at 48 V.
Xovis using customer WiFi connectivity still needs Power over Ethernet

The XOVIS devices using customer WiFi connectivity need to be powered using Power over Ethernet (RJ 45)

  • The plug and the sensor need to be free from any mechanical pressure.
  • The sensor supports Ethernet 10/100MB Full/Half/Auto negotiation based on the IEEE 802.3 standard.
  • It is highly recommended to set the switch port to auto negotiation.
  • The sensor is powered by PoE Class 0 compliant to IEEE 802.3af. As defined by the standard, the network switch port needs to provide 15 Watts at 48 V.

Info

Wi-Fi is not meant to be used in parallel with Ethernet connectivity, so for the connectivity to happen over WiFi, no connectivity should be available through the POE cable that is needed for power: The device will prioritize LAN at any time and only switches to Wi-Fi if the connectivity via Ethernet is gone.

Warning

Remember: Connecting XOVIS sensor is not possible using 4G

Network Requirements

On the network, the devices must have HTTPS & MQTT/TLS access via different ports. Please find below the current “List of IP addresses for outgoing traffic” to know which ports to open.

A Dynamic IP is required.

IP Addresses needed for Outgoing traffic

We sync all our hubs to the same open NTP (network time protocol) servers so we have consistent timings in our data warehouse.

Note

We recommend not to use specific IP addresses or DNS destinations in the firewall as they can and probably will change in the future!

→ The ports will remain the same, so we recommend to communicate / open the ports outbound.

Port

Type

Protocol

From

To

Direction

Endpoint/Description

443

TCP

HTTPS

Sensor

HUB

Outbound

HUB Device Control

Whitelist the following URLs:

  • *.xovis.cloud
  • *.xovis.com
  • *.servicebus.windows.net
  • *.cloudapp.azure.com

Azure Cloud IP’s are dynamic

443

TCP

HTTPS

Sensor

Xovis support

Outbound

remotesupport.xovis.com (185.187.120.162)

443

TCP

HTTPS

Sensor

Xovis IoT

Outbound

iot.xovis.com (185.187.120.166)

Mandatory for Update Service & Licensing

443

TCP

HTTPS

Sensor

PIP server

Outbound

pip.xovis.com (185.187.120.6) Product Improvement Program

123

TCP

NTP

Sensor

Timeserver 2

Outbound

time server sync (sensors can also act as as time server)

Local connections, required to troubleshoot the sensor locally while being on the same network

443

TCP

HTTPS

Client

Sensor

WebUI, REST API, Sensor Explorer

80

TCP

HTTP

Client

Sensor

WebUI, REST API, Sensor Explorer (not recommended)

XOVIS WiFi devices can connect to IEEE 802.11a/b/g/n/ac compatible wireless LAN Access Points with either 2.4 or 5 GHz. The authentication methode WPA2 pre-shared key (PSK) is supported. Connections to open networks are allowed but it is the responsibility of the network operator to ensure the security.

Articles in this section