Jump to content

Search the Community

Showing results for tags 'oid suggestion'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Features Discussion
    • Getting started
    • Release Notes
    • General
    • Industry Chats
    • Feedback & Feature Requests
    • Agent
    • User Portal and Web App
    • Domotz Mobile App
    • Domotz Hardware
    • Public API for Developers
  • Third Party Hardware
    • Power Distribution Units (PDU) & Smart Power Plugs
    • Managed Network Switches
    • Device Configuration Management - Backup & Restore
    • Gateway/Controller Integrations
    • Wi-Fi Access Point and Controllers Integrations
    • Audio Video and Multimedia Integrations
    • Other Devices
    • Manufacturer Support
    • Domotz Agents on 3rd party platforms

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Found 2 results

  1. Giancarlo

    08/24 - 2020 Release Notes

    This change log covers what's changed in Domotz Pro service since previous Release Notes. These changes include Domotz Pro cloud, Domotz Agent and Domotz Pro App.  Since previous Release Notes new versions of Domotz Agent and Domotz Pro App have been released.  August 24th, 2020  In order to fully exploit the new features, functionalities and bug fixes released, please make sure you have installed the latest version of  Domotz Pro Mobile App: check on Apple Store or Google Play. Latest version as of today is 2.23.0 Domotz Agent: check on Domotz Portal under the subscription tab. Latest Agent version as of today is 3.1.1 Violet Digital Support: check on Apple Store or Google Play. Latest version as of today is 2.7.0 Domotz Pro WebApp, Desktop App and Portal are already updated to the latest version What's new: SNMP Suggested OiD and MIB browsing/search: Domotz has now stored more than 2300 different publicly available MIBs, so that users can easily search for OiD to be monitored through SNMP. A simple to use search engine helps the Domotz user to identify all the available OiD sensors that can be monitored on every device supporting SNMP. The library of available MIBs is in continuous evolution, and every user can contribute to its growth. SNMP v1 and v3 support: it is now possible to monitor SNMP data (Domotz EYEs) on devices supporting SNMP Version 1 or Version 3. In the past, only Version 2 was supported by Domotz. Network Devices supporting SNMP V1, V2 or V3 are now identified by Domotz Agent also for the automatic entities (Network Standard Info, Network Interfaces, PoE consumption and control, etc). SNMP OiD sensor history: data collected through SNMP are now represented with historical values (either graphs for numbers or list for text fields). Advanced Search within Global Management: it is now possible to use an advanced search mechanism both for Devices and Agents so that users can specify exactly in which type of field a specific text should be searched. For instance, users can now search for all the "Cisco" devices (as Vendor), installed in a Rack (as Location), and belonging to all the Agents which contains a specific word. Solutions 360 Integration: it is now possible to connect a Solutions 360 (Q360) account into Domotz. Q360 will become one of the available Contact Channels available to be used in Shared Alerts. This means that Domotz creates and update Q360 Service Tickets when a specific event occurs on the networks or devices monitored through Domotz. Domotz creates a Q360 Service Ticket for any specified alert within Domotz. The same ticket is updated by Domotz automatically, in the case other events occur on the same network or device and as far as the ticket is still open in Q360. When the previous ticket is closed and a new event occurs on the same network or device, a new ticket will be opened and a reference to the previous ticket is provided. Users are also allowed to associate each Agent to one specific Q360 Site, so that every time the ticket is automatically created in Q360, it flows under that specific Site. Freshservice Integration: it is now possible to connect a Freshservice (Freshworks) account into Domotz. Freshservice will become one of the available Contact Channels available to be used in Shared Alerts. This means that Domotz creates and update Freshservice Tickets when a specific event occurs on the networks or devices monitored through Domotz. Domotz creates a Freshservice Ticket for any specified alert within Domotz. The same ticket is updated by Domotz automatically, in the case other events occur on the same network or device and as far as the ticket is still open in Freshservice. When the previous ticket is closed and a new event occurs on the same network or device, a new ticket will be opened and a reference to the previous ticket is provided. Users are also allowed to associate each Agent to one specific Freshservice Department (or Customer), so that every time the ticket is automatically created in Freshservice, it flows under that specific Department. Improvements: New Icons and data now available in the Network Topology map: a new filter has been added in the Network Topology Map which allows to highlight and search only for the monitored devices through Alerts. New icons has been added to the devices to identify the ones that are connected to PDUs or PoE switches or for the ones that require credentials to unlock specific functionalities. The latest speed test data results have been added to the "Gateway" device in the Network Topology map. Configuration Management for Luxul switches: always stay on top of changes happening on your network infrastructure devices. With Domotz, you can now automatically backup the running and startup configuration files of your Luxul networking switches. Domotz will keep track of the configuration changes over time and notify you if any change occurs. Network configuration issues are easily identified. Store backup files or new configuration files can be pushed to the switches directly from Domotz. Enriched Monthly Report: the monthly PDF report now includes statistics about the connectivity of the network (WAN monitoring) and the detailed list of network disconnections occurred during the previous month. Public API - support SNMP Credentials/Communities: it is now possible to configure Credentials for SNMP v3 through Public API. Gude PDU support: newer models of Gude PDUs have been added to the list of supported devices. New Device Discovery Alert: in order to improve awareness around security, users can now enable the alert for new devices joining a specific network from within the "Network Security" tile. Fix: WAN IP Port Scan has been fixed in the frequency of execution. "Last Status Change" timezone fixed in the Manage functionality. Outlet name char limits have been increased. Clear reference to Webhooks within Public API documentation. Unifi Controller data fetch failure has been fixed. The issue preventing a Control4 identification (due to localhost not found) has been fixed. Agent process failing during "un-formatted" DHCP messages received has been fixed. Issue when exporting XLS file from Desktop App has been fixed. Netgear PoE switch wait time to retrieve data has been extended to avoid timeout for certain models. Araknis AN310+ Non-PoE switches were falsely recognised as PoE. Known limitations: VPN on Demand is currently not supported on Luxul Router based Agents. As soon as Luxul team will provide Domotz with the API resources to make this available, Domotz will add this capability. Eyes configured for deleted devices affect the total counting of Eyes. Devices with multiple network interfaces (multiple MAC address) can't be merged into single device. This affect also some type of switches which appear as multiple instances on Domotz when VLANs are configured. Field Operators can't set alerts on Domotz Eyes (SNMP Custom OID and TCP Services monitoring). Static IP address on the Domotz Box cannot be configured before configuring the Agent. DHCP cannot be leveraged on additional VLANs on the Domotz Box. Configuration Management for Cisco IOS devices is currently not available when Domotz Agent is hosted on Windows machines.
  2. Giancarlo

    05/08 - 2018 Release Notes

    This change log covers what's changed in Domotz Pro service since previous Release Notes. These changes include Domotz Pro cloud, Domotz Agent and Domotz Pro App. Since previous Release Notes new versions of Domotz Agent and Domotz Pro App have been released. May 8th, 2018 In order to fully exploit the new features, functionalities and bug fixes released, please make sure you have installed the latest version of Domotz Pro Mobile App: check on Apple Store or Google Play. Latest version as of today is 1.7.5 Domotz Agent: check on Domotz Portal under the subscription tab. Latest Agent version as per today is 1.9.1 Violet Digital Support: check on Apple Store or Google Play. Latest version as of today is 2.6.7 Domotz Pro WebApp and Portal are already updated to the latest version What's new: App and WebApp in Demo Mode: it is now possible to use the Domotz Pro App in Demo Mode (or via Web App) in order to understand and show all the features available through Domotz. The Demo Mode also works when the mobile is in offline mode Disable Device Auto Discovery: the Device Auto Discovery performs a network scanning every 30 seconds. It is now possible to disable the automatic discovery of new devices, in order to allow the monitoring system to monitor only the existing devices at a certain date Domotz Users can be invited on a FingBox: all the Domotz Pro users can be invited by a FingBox user to monitor their network. A new Agent is created in the Domotz Pro list of agents and it performs Remote Monitoring and Managing activities by leveraging the FingBox hardware Domotz on Luxul Router - Epic 5: Domotz Agent is now available on the Luxul Router - Epic 5 series SNMP Templates: for some devices, OiD are suggested to the user during an SNMP sensor setup CyberSecurity Features (Beta on request): TCP Open Ports scanner (WAN), Default Credentials Scanner and UPNP Port Forwarding Scanner (Router/Modem security issue) CleanUp Agent Data: user can now clean-up completely the data of an Agent, and start scanning a new network (without requiring the re-configuration of the Agent). This now allows users to Configure the Agent in a network, then ship or relocate on a different network, and start scanning from scratch Denon and Marantz integration: new 2018 models (both Denon and Marantz) can now be managed remotely through an intuitive interface available in the Domotz Pro App and WebApp. Network and Device reboots, Zone Info and controls on the Zones, System Info, Streaming Services list and more is now available Blacklist of devices: some Devices may have problems when scanned with network monitoring tools. Although not common, this is typically related to scanned devices that have legacy firmware. It is now possible to blacklist a Device from being monitored by Domotz Pro agent Improvements: Device Rediscovery: it is now possible to delete an online device, to allow the Domotz Pro service to re-discover it. This is very useful if the user want to clean-up all the previously discovered data for a specific device Power activity logs: Reboot, on/off and software restart activites of supported devices (through PDUs, PoE and supported drivers) are now tracked and listed into the "Reports & Logging" tile Ruckus - new firmware support: Ruckus Zone Director with firmware 10.1+ is now supported with Advanced Plan Remote Connections on Public Hostname/IP: it is now possible to create Remote Connections/TCP Tunnel to Public Hostname/IP using the Domotz Agent (Advanced Plan) TCP Tunnel Endpoints: When creating an Open TCP Tunnel, random endpoints (host:port) can be copied directly from the App/WebApp Dummy Device removal: it is now possible to remove Dummy devices Important Devices can be blocked: it is now possible to configure an Important Device as "blockable" by an end-customer (through Violet - Customer Facing App) See Blocked Devices: Domotz Pro user can now see if a device has been blocked or if it has a scheduled block configured in Violet - Customer Facing App Serial Number: some devices are now reporting the Serial Number directly into Domotz Pro FIX: Control4 firmware version was not retrieved for some newer versions Dummy Devices could not be controlled through Violet Long Community String (SNMP) could not be edited from the Mobile App Known limitations: Eyes configured for deleted devices affect the total counting of Eyes Devices with multiple network interfaces (multiple MAC address) can't be merged into single device Field Operators can't set alerts on Domotz Eyes (SNMP Custom OID and TCP Services monitoring) Static IP address on the Domotz Box cannot be configured before configuring the Agent External monitoring of public and private subnets might not work properly on Raspberry Pi installations Multiple Devices logically connected to a Managed Switch Port: in case of WiFi AP connected to a switch port, the information is not available at the WiFi AP info
×
×
  • Create New...