{"id":2276,"date":"2019-05-09T09:18:17","date_gmt":"2019-05-09T08:18:17","guid":{"rendered":"https:\/\/www.blog.easydcim.com\/?p=2276"},"modified":"2023-09-12T10:51:01","modified_gmt":"2023-09-12T10:51:01","slug":"easydcim-v1-6-0","status":"publish","type":"post","link":"https:\/\/dev-whmcs.easydcim.com\/blog\/easydcim-v1-6-0","title":{"rendered":"Total performance makeover in EasyDCIM v1.6.0!"},"content":{"rendered":"

While today\u2019s exciting release of EasyDCIM v1.6.0<\/strong> may not come entirely as a surprise, its scope and significance certainly will. In our previous Blog article we shed a bit of light on the upcoming, performance-oriented improvements already, but why not delve into some further details? This way, you will have all the background needed to find your way around this milestone EasyDCIM update real quick. Let\u2019s get started!<\/p>\n

Dispersed architecture model<\/strong><\/p>\n

It goes without saying that the construction of modern network devices monitoring systems poses a lot of challenges to the administrators. One of them is round-the-clock accumulation of large amounts of data such as transfer and power consumption, or current device load. In EasyDCIM the speed with which this data is fetched depends mainly on the total number of devices managed. That is why it is crucial for the information gathering system to be maximally scalable.<\/strong><\/p>\n

In the 1.5.5 version, this task was assigned to a single server – the very same one on which EasyDCIM was installed. The single-threaded architecture had certain limitations however as it allowed to send only one request at a time, which might have caused tangible delays while handling large numbers of devices.<\/p>\n

EasyDCIM v1.6.0 approaches the data collection process in a slightly different way, empowering the administrator to share out this task between many external servers via remote agents. The biggest advantage of dispersed architecture model is that it allows to effectively distribute the load,<\/strong> which ultimately leads to much reduced response time of the system. Being able to switch from one server to a more powerful one whenever needed and without interfering with the main server on which EasyDCIM is installed ensures greater scalability of the application as well.<\/p>\n

\"Dispersed<\/a><\/p>\n

Data collecting agents based on a multi-threaded architecture<\/strong> and closer to end devices are much faster in fetching the information, and more optimal with more devices. Summing up, the newly introduced solution allows you to run many threads at a given time, thanks to which the number of completed tasks increases even a few times, successfully resolving the problem of network latency.<\/p>\n

NETCONF protocol support<\/strong><\/p>\n

The basic network protocol EasyDCIM relies on is SNMP. It allows you to remotely disable and enable network ports for most of network devices such as switches or routers. But some devices, like those provided by Juniper and Cisco<\/strong> brands, are not supported by SNMP. To let administrators remotely manage the devices of those manufacturers in the same manner, we then implemented the integration with NETCONF.<\/p>\n

\"NETCONF<\/a><\/p>\n

NETCONF management protocol is an XML-based protocol used by client applications to request and change configuration information about network devices. The way it works is that a NETCONF server sends a request to the appropriate software modules of the device, encrypts the response and returns it to the client application. Briefly speaking, NETCONF provides a robust API for interacting with network nodes<\/strong> and can be easily used to insert or download structured data from the device, thus facilitating the automation of everyday device management.<\/p>\n

A solid package of new gear<\/strong><\/p>\n

Let us also have a quick overview of some other utilities that may capture your interest:<\/p>\n