Skip to main content
Sensors Management
Alex Patnick avatar
Written by Alex Patnick
Updated over a week ago

The Sensors Status screen displays all the network sensors that are currently defined in the Server. You can find it under Settings

For each sensor, the following information is displayed -

  • Display Name

  • Proxy ID - which proxy is collecting the data

  • Server - the IP address and hostname of the sensor, along with the port it is using to communicate - by default this is 9545

  • Operating System

  • Installed Version

  • Last Checked

Sensor Statuses

The sensor is operational and responsive, and data is being captured

The sensor is not accessible from the Server

Sensor Management

Download the files for manual/PowerShell deployment and add the sensor(s) deployed

Delete

Removes a sensor from the UI. Note:This does not uninstall the sensor software or delete the sensor VM from vCenter. This will need to be done manually

Upgrade

Remotely upgrades a sensor. This action requires authentication and is available only for Linux sensors. Note: When updating the Faddom Server, the local sensor will be updated automatically

Sensor VM Password

If you need to access a sensor VM that was deployed through the Faddom automated sensor deployment using SSH, this is the password that has been configured for user faddom

Sensor Actions

- Check Sensor Status

Checks connection to between Faddom and the sensor.

- Properties

Allows you to edit the display name, port used, proxy collecting the information, and whether an SSL certificate has been installed on the sensor

- Restart the Linux Sensor

This restarts the Linux sensor service. Note: To restart a Windows sensor, you will need to login to the server via RDP and restart the Faddom Sensor service manually.

- Upgrade the Sensor

Remotely upgrades a sensor. This action requires authentication and is available only for Linux sensors.
Note: When updating the Faddom Server, this will automatically update the local sensor if needed.
Note: To upgrade a Windows sensor, you will need to login to the server via RDP and update it manually after downloading the files from the Faddom download portal

- Debug Info

Provides statistical information on the sensor that can be used for troubleshooting if the sensor is not working correctly.

Configuring A Manually Deployed Sensor

There are two ways to manually deploy a Faddom sensor. Either through PowerShell (see Deploying Faddom Sensors Using PowerShell) or by downloading the OVA and importing it manually into Faddom. Once done, you will need to perform the below actions to connect the sensor(s) to Faddom -

  1. Press the Configure button and the Define New Sensor dialogue appears.

  2. In the Host Name field, enter the hostname or IP address of the sensor

  3. In the Name field, it is possible to add a display name for the newly defined sensor. Note: When deploying automatically the convention is faddom-sensor-<ESXi-hostname>

  4. If using a port other than the default port (9545), specify the port number in the Port field.

  5. If SSL-encrypted communication between the Server and the Network Sensor is required and has been configured on the sensor installation, then select the Use SSL checkbox.

  6. Click OK and Faddom will attempt to connect to the server and you will see the appropriate status as per the Sensor Statuses section above

Updating the Sensor

The localsensor that is included with the Faddom server is updated automatically, however, remote sensors whether Linux or Windows, deployed in your vCenter are not. You can follow the below instructions to update.

Linux Sensors

There are three ways to update the Linux sensors -

  1. Via the UI, which requires SSH on port 22 to be open from the Faddom server to the Faddom sensor(s)

  2. Manual upgrade by downloading the upgrade package from the UI and running the script attached to this guide

Via the UI

  1. Navigate to Settings > Sensor Status

  2. Select the sensor(s) you wish to upgrade

  3. Click Upgrade

  4. Select the credentials to use

    1. Default Credentials - username is Faddom and the password is during deployment and visible by clicking Sensor VM Password

    2. Enter Credentials - if you have manually deployed the sensor or manually changed the password, select this. The default username is Faddom. Choose whether or not to save these credentials for future upgrades

  5. Click Ok and wait a few minutes, and the sensor will finish updating, which will reflect in the UI

Manual Update

  1. Press the Configure button and the Define New Sensor dialogue appears.

  2. Click Linux to download the packages and download the script attached to this guide

  3. Copy the files to the Faddom sensor/s and place in the same location

  4. Connect via SSH to the Faddom sensor using the username of Faddom and the password displayed by clicking Sensor VM Password

  5. Make the script executable - sudo chmod +x installSensor_Linux.sh

  6. Run the script sudo ./installSensor_Linux.sh -f FaddomSensor-Linux.tar.gz

  7. Refresh the UI and the version should be updated

Destroy and Redeploying the Sensor

In some cases, it may not be a simple process to open SSH from the Faddom server to the Faddom sensor. In this case, you can destroy the sensor by deleting it from your vCenter and redeploying it by following our guide How to Deploy A Sensor via Faddom UI. As the sensor does not store any data, this will not affect the Faddom server or UI.

Windows

For Windows sensors, a manual update is required as the Faddom server is unable to connect to update the sensor. To do this, the following process can be used -

  1. Press the Configure button, and the Define New Sensor dialogue appears.

  2. Select Windows to download the FaddomSensor-Windows-x64.msi

  3. Copy this to the Windows server being used for the install

  4. Run the installer

  5. Once finished, refresh the UI, and the version should be updated

Install Script

Attachment icon
Did this answer your question?