Search the Community
Showing results for tags 'topology map'.
Found 3 results
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. October 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.5.0 Domotz Agent: check on Domotz Portal under the subscription tab. Latest Agent version as of today is 2.7.3 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: VPN on Demand: it is now possible to use the Domotz Agents as remote Virtual Private Network (VPN) servers. This functionality is available on the Domotz Agents with the Premium Plan. Thanks to this new functionality, users are allowed to access directly to all the devices on the remote network and on all the ports concurrently, without the need to create multiple tunnels. Main advantages of the VPN on Demand: Tunnel remote network traffic through the Domotz Agent: Diagnostic and programming tools can be used across the VPN to simplify troubleshooting and network management. Users can see how the remote network behaves in terms of routing traffic internally and through the gateway to Internet. Access your remote devices as if they were locally connected: VPN on Demand puts your computer on the remote network, making it easy to access multiple network devices simultaneously and on multiple ports (across protocols). Debug network issues has never been so easy. Use your own software to control and program your remote devices: VPN on Demand allows your own or proprietary software to connect to the remote devices as if you are locally on the network, simplifying the way you can serve your customers. VPN on Demand is available in two modalities: All traffic: all the traffic (including Internet traffic) is routed through the Domotz VPN. Only LAN: only the remote network traffic, where the Domotz Agent is installed, is routed through the the Domotz VPN. Network Topology Map: added details. Users can now completely use the Topology Map as entry point to navigate around the data related to a specific agent: Link details: by clicking on the links you are now able to see the stats for that specific link (traffic, errors, packet lost, etc) and navigate to the attached devices. Export map: users are now able to export the Network Topology Map both in SVG and PNG formats. Important Devices: a filter has been added to allow the user to display on the Topology Map all the important devices, even if they do not appear to be connected to any managed switch or WiFi access point. Improvements: Cisco Tile: Cisco devices are grouped and filtered together into an easy to access dedicated tile. Domotz Agent Hostname discovery: the hostname discovery for the devices has been decoupled from the main discovery algorithm. In this case, if local DNS doesn't returns data in a reasonable amount of time, the main discovery still finds devices on the network. Billing details: monthly bills now indicate the number of agents added in the previous month, versus the total number of configured agents for the next month. TrippLite support: new models of TrippLite PDUs have been added to the list of supported ones. HP support: new models of HP switches have been added to the list of supported ones. Domotz Service Status page: in case of login errors, if the Domotz Pro service has been discovered with issue (through automatic monitoring of the service offered) a link is displayed in the login page. Remote Connection Traffic consumption: the consumed traffic for the month for the remote connection functionalities is now available on each section where remote connection is required. D-Tools Integration: the mapping of devices with D-Tools cloud is now based on MAC addresses, and as fall-back on IP Addresses. Moreover, the hierarchy of locations available in D-Tools is now reported also in Domotz. Overview Dashboard Optimization: the dashboard has been optimized so that searching Agents across thousands of different installation is now very fast. CTRL-F has been enabled on the dashboard to quickly access to the search functionality. Fix: A fix has been implemented to support Ruckus switches when they are configured in stacked. A fix has been implemented to report the total PoE power of stacked Cisco Linksys switches. Editing devices details on an account with multiple agents and multiple devices per agents has been optimized. Remote connection button was not available on some pages through the iPad 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. 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
Hi, I'm trying the network topology map feature and I'm a bit lost with it. I'm trying to link my switchs together in the right order, but it looks like I can't. I have HP-RG => HP-SR1 => HP-SR2 => HP-SR3 => HP-PL1 => HP-B6 => HP-SR4 But HP-PL1 displays on top of the tree. When I click on HP-RG to say that it is HP-SR1 which is linked to it, not PL1, I don't find how to do this simple thing !!! It says device is mapped on HP-PL1 and that's it ! If i click on this it displays the port configuration of HP-PL1 ! But I want the port configuration of HP-RG !!! I just saw that when going in device details, I have some HP switchs that she an "interface" tab, where I can edit things. And Some other HP switchs that don't have it. HP-RG, HP-SR1, HP-SR2 and HP-SR3 are HP-1920 switchs JG925A. They don't show the Interface tab. HP-PL1 and HP-SR4 are also HP-1920 switchs, but JL384A... They show the Interface tab. I'm a bit lost on what to do then.
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