Jump to content

Search the Community

Showing results for tags 'network map'.

  • 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

Categories

  • Articles

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Found 3 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. Hi all. I started working at a new company this month and they have Domotz Pro within a Luxul Epic 5 ABR-5000. The network used to be 192.168.200.0/24 but they changed recently to 172.16.0.0/16. I read that Domotz won't monitor networks below /22, so I added 172.16.1.0/24 as private subnet in order to solve this issue. Now all our servers and switchs are available in devices list. The problem now is Network Topology. Since the last change, it doesn't work. All devices have SNMP v2c enabled. So my question is: Network topology is not working due to /16 netmask ?
  3. Giancarlo

    08/28 - 2019 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 28th, 2019  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.1.0 Domotz Agent: check on Domotz Portal under the subscription tab. Latest Agent version as of today is 2.6.2 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: Network Topology Map: the Domotz's automated network map (available on Domotz Agents with the Premium plan) shows how devices are connected each other. Network Hierarchy: Navigate the map and check how devices are connected each other on a very intuitive interface. Devices are automatically displayed on the map in order to facilitate the readability of it. The map automatically updates upon external changes (e.g. when moving devices from a WiFi Access Point to the other) Connection Types: Check how your equipment is connected to the network devices (WiFi, wired through managed or unmanaged Switches). Quick access to statistics reported on each connection Easy Access to the device details: Switch very quickly from one device to the other. Access all the device details and controls with a single click. Easily find and locate your equipment on the map Mini-map: a mini-map helps focusing on the interesting area of the network topology, without loosing control of the overall topology map Domotz Service Status Page: a new status page has been published (status.domotz.com). The page is automatically updated with the status of the services offered by Domotz (Domotz Pro Portal, App, WebApp). Manual incident reports are published on the same page Ubiquiti Access Point - Advanced WiFi Monitoring for local controller: it is now possible to unlock advanced monitoring of Ubiquiti AP when unifi controller is local on the network (available on Domotz Agents with the Advanced plan). You can monitor Signal strength and noise level at the AP and WiFi client level. Monitor traffic, Rx and Tx errors, hardware utilization and more. Improvements: Crestron IP device identification: Crestron IP devices are now identified on the basis of the official Crestron auto-discovery protocol. Additional information are now available on Crestron IP devices when available (including firmware version, serial number, model ID) Network Info aways available: WAN and network information (Public IP Address, Public Name, Provider, Gateway, DNS and DHCP Server) are persisted in the cloud. Therefore, this information is also available when the Domotz Agent is offline (troubleshooting purposes) Fix: The issue in editing device details when managing multiple networks with thousands of devices has been fixed (Web GUI became un-responsive under certain circumstances) Network interface were not correct for inferred links when there were some missing interface data Offline devices showed "This device went down X days ago" as a link Known limitations: Devices cannot be re-disposed on the Topology Map Devices not connected to any other device (either through direct or inferred connection, or as a manual connection) are not displayed on the Topology Map Click on connections on the Topology Map does not bring connection info and stats 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
×
×
  • Create New...