Search the Community
Showing results for tags 'switch'.
Hello there, it would be great to see a port connection history either in the device or interface page. For example, in the device page you can see that the device is currently plugged into port 42, but had previously been into 27 some weeks ago. On the interfaces page, when clicking on port 42, we can see that device PC161 is currently plugged in, but one week ago Laptop12 was plugged in. why is this helpful? if something is plugged into a switch port but is not active, then you can identify from the history what it was and make a decision about weather or not you can remove/replace it. if someone is complaining that their device is not working, you can look at the port history and see that they were previously in port 42, but now this is being used for something else, and therefore it’s likely been unplugged. many thanks, Adam
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
Atoshi posted a topic in AgentThis is mostly out of curiosity, but is there a set of standard RFC SNMP MIBs you support? I know you've implemented some private MIBs for vendors like Netgear or Cisco, but I'd like to know if there are any open-standards MIBs you're leveraging that I can check are being discovered correctly for Brocade switches.
TokyoIoT posted a topic in Power Distribution Units (PDU) & Smart Power PlugsAccording to this document http://www.domotz.com/documentor-sections/config/, a WeMo switch should show a Config tab. I have a WeMo Light Switch, but there is no Config tab.