Follow

Pairing Physical Sensors

Summary

For virtual sensors see the accompanying article here.

You can see the list of paired sensors and the list of sensors available for pairing from the brain web UI under Manage → Sensors:

Sensorpage.png

The status column indicates whether the sensor has been paired (Paired) or is available for pairing (Provisioned).  Sensors which have been paired with other brain devices are not listed in this screen.

For the brain device to be able to retrieve sensor information from the Vectra cloud the brain must be able to contact the Vectra Updater service using the URL https://update2.vectranetworks.com/.  The brain will retrieve the current list of available sensors, ignoring sensors currently listed as paired to other brains.

For sensors to inform the cloud of their pairing status the sensor must be able to contact the same Vectra Updater service using the URL https://update2.vectranetworks.com/.

Should the brain be unable to contact the Vectra cloud, the sensor list will contain only those sensors previously known to it.

If sensors are unable to contact the Vectra cloud the sensor list in the brain may be out of date, possibly including sensors which are unavailable for pairing or excluding sensors which are available for pairing. For offline sensor pairing check the bottom of the article under "Troubleshooting."

During the pairing process the sensor contacts the brain on TCP port 22 (SSH) and TCP port 443 (HTTPS), completes the secure key exchange and sets up the secure tunnel on TCP port 22.

Pairing

  1. Identify the sensor in the brain list from the Manage → Sensors page.
  2. Click on the sensor to open the sensor information dialog.
  3. Click the 'Pair' button. If the 'Pair' button is labelled 'Pair Offline' then the brain believes that the sensor cannot currently contact the Vectra cloud and automatic pairing will not function correctly. The brain will update the Vectra cloud with its mgt1 IP address and post a request for the sensor to initiate the pairing process.
  4. If the sensor has access to the Vectra cloud the sensor will now retrieve the IP address of the brain from the Vectra cloud and attempt the pairing TCP connection.
  5. If the sensor does not have access to the Vectra cloud or is unable to contact the brain device on its mgt1 IP address (e.g. in a NAT environment) the sensor should be manually instructed to pair with the brain from the sensor CLI using the 'set brain x.x.x.x' command where 'x.x.x.x' should be replaced with the IP address of the brain.
    NOTE: 'set brain fqdn_of_brain' can also be used however it requires the sensor to have name servers configured and reachable to resolve the FQDN to the relevant IP.
  6. Once paired the sensor will attempt to synchronize software versions by downloading the latest update from the brain and immediately applying it.  The system may be temporarily available while this update is being applied.

Troubleshooting

  • Verify that the brain has access to the Vectra cloud service: https://update2.vectranetworks.com/.
  • Verify that the sensor is able to connect to the brain on TCP port 22 (SSH) and TCP port 443 (HTTPS). If the brain is behind a NAT gateway the sensor will need to be paired manually using the 'set brain' command on the sensor CLI.
  • If the sensor has previously been paired to another brain verify that the sensor is unpaired from the brain and that the sensor is able to connect to the Vectra cloud service to indicate its pairing state.  You may need to enter the 'del brain' command at the sensor CLI to allow the sensor to update the cloud with its availability.
  • In the case of offline sensors:

    * Go to the Brain UI “Settings > General > Sensors > Generate a Sensor Registration Token”, save after enabling it and copy the value of the registration token

    * Connect to the CLI of the sensor and type “set brain xxx” as well as “set registration-token <token>"

    * Wait for 15 minutes and the sensor should appear in the “Manage > Sensors” page of the Brain UI

  • In case of Offline Brain, please contact the Support Team.
Was this article helpful?
2 out of 2 found this helpful

Download PDF

Have more questions? Submit a request

0 Comments

Article is closed for comments.