# April 13, 2022 – SNMP templates for Synology, NAS Volumes, LLDP, ILO Support, and more.

Here are all the latest features we’ve added to Domotz:

- Pre-configured **SNMP templates for Synology NAS**
- **HP** **iLO** now supported for **OS Monitoring via SSH**
- **Alerts**and **Sensors** added to the Search & Manage tables
- **Custom Integration** drivers can now query external IPs
- Pre-configured template for **Linux Volumes** **and Partitions**
- **Sensors tables**within Custom Monitoring Dashboards are now available
- **LLDP** via SNMP used for the **Topology Map**
- **Virtual Machine information** from VMWare / ESXi
- Additional **MIBs**

## What’s new

### New fields on Search & Manage

We've added new fields to the Devices and Agents tables in the Search and Manage section. These new fields streamline your workflow to help you easily identify if any Devices or Agents require urgent attention.

For instance, you can now see any shared alerts applied to a device. Additionally, you can add and edit alerts as needed directly from Search & Manage. Moreover, you can search for all the Important Devices within specific Customer Sites that haven't been configured with a Shared Alert yet.

Managing Devices in a Network Dashboard

1. Navigate to the "Search & Manage" section to view device details.
2. Filter devices by site using the dropdown next to "Site." The example shows a selection for "Winery - Temecula Valley."
3. Adjust the "Type" and "Device Name" filters to narrow down the device list.
4. Check device details such as location, type, make, IP/MAC address, importance, and status in the respective columns.
5. Use the "Alerts Profiles" dropdown to filter devices by alert status. Options include "All" or "No alerts," among others.
6. Examine additional configuration options for filtering items in the "Alerts Profiles" dropdown panel if needed.

Similarly, you can now review and edit all the shared alerts that have been applied, across all devices and customer sites/agents. 

Moreover, you can search for devices with configured sensors to analyze them.

Device Management Interface Sensors Column

1. Navigate to the "Devices" tab on the interface to view the list of devices.
2. In the displayed table, locate the "Sensors" column on the far right.
3. The "Sensors" column shows different sensor configurations for each device, such as "1 Pre-Configured SNMP Sensor" or "10 SNMP Sensors."
4. Use the dropdown at the top of the "Sensors" column to filter by sensor type or number if needed.
5. Evaluate the sensor configurations for each device to understand the monitoring setup or make adjustments if required.

In terms of sensors, you can now filter for devices if one (or more) of the following sensors is readily available:

- Preconfigured SNMP Sensor template
- SNMP Custom OiD Sensors
- TCP Custom Port Sensors
- Custom Integration Driver Sensors

### VMWare Virtual Machine Data

As part of our OS monitoring, you can retrieve information related to Virtual Machines within ESXi / VMWare servers.

Virtual Machines List with Filter Options

1. The interface lists virtual machines with columns for Name, Power state, Guest full name, and Memory size.
2. Each column has a filter option at the top to select specific criteria. For example, filtering by 'poweredOn' in the Power state column shows only machines that are turned on.
3. The list includes four entries: 'Bobby - Ubuntu Desktop', 'SSH Server', 'domotzpro-ubuntu-20...', and 'Windows Server2019 - ...'.
4. Power states shown are 'poweredOff' or 'poweredOn'.
5. Guest full names include versions of Ubuntu Linux, Debian GNU/Linux, and Microsoft Windows Server.
6. Memory sizes range from 1.1 GB to 6.4 GB.
7. A 'Download CSV' link is available to export the data.

For VMWare / ESXi servers that have been unlocked for OS Monitoring, Domotz can retrieve the following information for each Virtual Machine:

- Name of the VM
- Power Status
- Guest Full Name and OS
- Memory Size
- Virtual CPUs (number)
- Ethernet Cards attached to the VM (number)
- Virtual Disks attached to the VM (number)
- Path Name for the VM disk
- UUID
- Boot-Time

### Sensors tables within Monitoring Dashboard

You can now create a Monitoring Table within the Custom Monitoring Dashboard using the data generated by the pre-configured SNMP Sensor templates.

Selecting Sensors to Monitor in a Monitoring Table

1. To add sensors, look for the section titled "Select Sensors to Monitor."
2. Use the search bar labeled "Filter sensors" to find specific sensors.
3. Review the list of available sensors under the "Sensors" heading. Each sensor type has a checkbox for selection.
4. The list includes options such as "Partitions and Volumes," "NAS Basic Info," "NAS HD Info," and more. Each entry indicates the number of devices supported and some details about the sensor's capabilities.
5. To view additional details about a sensor, select the "Show more" link next to its description.
6. Once you have selected the desired sensors, they will be added to your monitoring table for tracking.

When a new table is created, there will be one row for each "entity" of the same type of sensor. For each row, all the values retrieved by the pre-configured SNMP template will be reported. This makes it easy to sort or search across all sensors, devices, and sites/agents.

Synology Disks Monitoring Table Overview

1. The table lists monitored devices, displaying details such as agent, type, device name, ID, model, type, status, and temperature.
2. Each row represents a different disk, with columns indicating:
   - **Agent**: Name of the site or source (e.g., Draper Site, Inc. or 80CHR).
   - **Type**: Type of device, here shown as "Synology."
   - **Device Name**: Identification of the device or drive (e.g., Disk 2, Drive 1).
   - **ID** and **Model**: Unique identifiers and model numbers for each disk.
   - **Type**: Disk interface type, all listed as "SATA."
   - **Status**: Health status of each disk, all marked as "Normal."
   - **Temperature**: Current temperature of each disk in degrees Celsius.
3. Filters at the top allow sorting by each column to organize information based on specific criteria, such as highest temperature or specific device types.

As a reminder, the Custom OID sensors can be added to the Device Tables as additional columns. The difference is that the preconfigured SNMP Sensors are grouped and there might be more values for the same sensor identifier (e.g. multiple volumes for the same device, multiple supply units for printers, etc):

Printer Supply Monitoring Table

1. The table displays a list of monitored printers with details in five columns: Agent, Type, Device Name, Supply Unit, and Supply Level.
2. The Agent column indicates the network or location associated with each printer, such as "NY - Shared Network" and "St John's High School - Draper."
3. The Type column lists the printer type, mostly left unspecified.
4. The Device Name column identifies the printer model, like "Kyocera ECOSYS M5526c" and "Brother MFC-9340CDW."
5. The Supply Unit column specifies the type of cartridge or drum, such as "TK-5242K" or "Black Drum Unit."
6. The Supply Level column shows the percentage of remaining supply, with graphical bars illustrating these percentages—ranging from 62% to 98%.
7. Use this table to monitor toner and drum supply levels to ensure timely replacements.

In the future, we'll be adding the ability to create Monitoring Tables with other types of sensors including:

- OS Monitoring generated data (Volumes, Applications, CPUs, Memory, etc)
- Custom Integration Drivers' data

## Improvements

### Custom Integrations to query external IP

You can use the Custom Integrations (Custom Drivers) to query an IP address that's different than the one associated with the Custom Driver itself.

This capability is when the information and data related to a specific device can be retrieved from an external service. A few examples of how this is relevant include:

- Retrieve the status of a WiFi access point from an API call against a controller hosted on a different IP address
- Get the status from a service on a specific device (or set of devices) and retrieve important data, from a Cloud Service status (e.g. Zoom room status)
- Create an integration with a third-party service to retrieve information about devices monitored through Domotz

### Pre-configured SNMP templates for Synology NAS - More SNMP Sensors

We've added a new set of pre-configured SNMP templates for Synology NAS devices.

SNMP Monitoring Configuration and Status Overview

1. Access "Device Details" for the NAS labeled "NAS1 - CHR_RS812" with IP address 192.168.100.100. The device status is online.

2. Navigate to the "SNMP" tab to view SNMP monitoring settings. The SNMP status shows "READ," with authentication set to "V2" and an agent sample time of "2 Minutes."

3. Add SNMP sensors using the options: "Add Pre-configured SNMP Sensors" or "Add sensor to specific OIDs," which has 26 MIBs discovered.

4. In "Monitored SNMP Items," view details for "Synology Disks" including:
   - Drive list with IDs and models.
   - Disk types are listed as "SATA."
   - Status of all drives is "Normal."
   - Drive temperatures range from 33°C to 36°C.

5. Under "Synology Basic Info," observe system health metrics:
   - System, power, and fan statuses, all marked "Normal."
   - System temperature is noted as 53°C.
   - CPU fan status is "Normal."
   - Model name is "RS812+."
   - Serial number is displayed.
   - Firmware version is "DSM 6.2-25426" with an available upgrade option.

These elements help in monitoring the health and performance of the NAS device using SNMP.

We've added the following SNMP templates for Synology NAS:

- **Synology Disks:** this includes the list of all the physical discs, with their model, type, status, and temperature
- **Synology Basic Info:**this includes the System Status, Temperature, Power, Fan Status, CPU Fan Status, Model Name, Serial Number, Firmware Version, and whether or not there is an upgrade available

Moreover, we've created a new set of pre-configured SNMP Sensors for generic Linux machines to monitor partitions and volumes (including usage percentage and residual free space). Synology NAS drives also support this feature.

Monitoring Partitions and Volumes

1. Four devices are being monitored, with data updated less than a minute ago.
2. To filter the view, enter the agent name in the "Agent" search box, such as "Pisa."
3. View and sort entries by columns: "Type," "Device Name," "Storage," "Usage," "Free Size," and "Total Size."
4. For each device, the details display:
   - "Device Name" such as "Synology ARM 370."
   - "Storage" locations like "/", "/run," "/tmp," "/volume1," "/sys/fs/cgroup," and "/dev/shm."
   - "Usage" showing the percentage of storage used.
   - "Free Size" indicating the space available.
   - "Total Size" showing the total storage capacity.
5. Use these details to manage and optimize storage resources across devices.

### LLDP via SNMP used for the Topology Map

Firstly, Domotz can extract LLDP information out of SNMP, to identify the connections between devices. We enrich the data (using RFC-4188). Ultimately, this results in a more accurate Network Topology map because some networking devices might not be compliant with the standard RFC-4188, but they still expose LLDP data on SNMP. Furthermore, we'll continue to enrich the data to build an accurate Topology Map using other protocols. And, in the future, we'll use LLDP to discover new devices on routed subnets in the future

### HP iLO - OS Monitoring Support

Now, the OS Monitoring feature supports HP iLO devices via SSH. Furthermore, you can "unlock" iLO machines in Domotz so that OS information can be read by the system.

For more information, visit the [OS Monitoring feature](https://help.domotz.com/user-guide/os-monitoring-feature/) in the user guide.

### Improvements to newly discovered device details

When Domotz discovers a new device on a network, triggering an alert, we now enrich the information before sending it to you. To explain further, we enrich the information as much as possible automatically before sending the notification (either via email, mobile push notification, or through PSA/Ticketing system integrations).

### Additional MIBs available in Domotz DB

Additional MIB files are available for the following devices and their OiDs can be searched from Domotz:

- SurgeX/ESP enVision
- Barco CX

## Fix

We’ve fixed the following issues:

- The**WiFi Clients** tile in the Mobile App was not available.
- False **Alarms on DHCP Server** changes were triggered even when the only change was the sorting of the server list.
- Zyxel switches: extend regex for RFC3621 identification to consider '48HP'.
- Shared alerts on the device side panel were referring to the agent instead of the device.
- **Juniper OS** unlocking for **Configuration Management** was not working with non-root users.

## **Known limitations**

- Firstly, monitoring Dashboards are currently limited to Monitoring Tables as Widgets. Furthermore, they do not report some variables (e.g. the ones created by the Custom Drivers) within the Monitoring Tables.
- To start, Luxul Router-based Agents do not support VPN on demand. To elaborate, we’ll add this capability as soon as Luxul’s team provides us with the required API resources.
- Devices with multiple network interfaces (multiple MAC addresses) can’t be merged into a single device. This affects some types of switches that appear as multiple instances on Domotz when VLANs are configured.
- The static IP address on the Domotz Box cannot be configured before configuring the Agent.
- HCP cannot be leveraged on additional VLANs on the Domotz Box.

To conclude, these release notes cover what’s changed in the Domotz Pro service since the previous Release Notes. Furthermore, these changes include Domotz Pro cloud, Domotz Agent, and Domotz Pro App.

All in all, to learn more, check out our [network monitoring software](https://www.domotz.com) or check out our [Know Your Networks Blog](https://blog.domotz.com/).