30. 06. 2014 Patrick Zambelli Asset Management, NetEye, Uncategorized

Automatic Recognition: Network Devices and their Modules

NetEye 3.5 will permit you the automatic recognition and administration of all your network devices. Through the implementation of an interface between the two existing modules GLPI (asset management solution within NetEye) and NeDi (network discovery) we were able to facilitate the overall asset management. This interface was realized as a standard GLPI Plugin. So future updates of NetEye and GLPI can be done independently and an appropriate management of future versions will be provided.

How it works:

NeDi allocates hardware within your network. It recognizes not just the single devices, but also their internal components. So not only the attributes of the device (as supplier, model, serial number etc.) but also the attributes of its components (also here supplier, model, serial number etc.) can be retrieved and recorded.

List of the identified devices with their attributes (within NeDi)

Detailed view of the device’s attributes (within NeDi)

List of the single switch-components (within NeDi)

The entire information on all components of the infrastructure (hardware and software) are displayed within the asset management (GLPI). The hardware assets, detected by NeDi, represent the basis for the management of the administrative data as support contracts, warranties and other contracts. Hardware and contracts can be related to their supplier. If a contract reaches its expiration date, an automated e-mail notification will be send to a predefined address.

Some screenshots to illustrate the view within GLPI:

Network devices with their components (links lead you to NeDi)

All switch-components are displayed as separate devices (with serial number, model, type etc.). This allows the individual contract-management of the single components. In addition, information as purchase date, warranty period, financial information etc. can be stored.

GLPI-Report – Devices and all the corresponding components are displayed. The report can be exported to a pdf or csv file. (Also filtering by supplier, model, firmware etc. is possible)

 Download and Setup

Within the .tar you find two folders:

– nediinventory: The Plugin itself, you can place into your ./glpi/plugins/ folder of GLPI

– report: When using the Reports Plugin, place this Folder i.e. ./glpi/plugins/reports/report/

Download:  neteye-glpi-plugin-nediinventory-1.0.7.tar

Patrick Zambelli

Patrick Zambelli

Product Manager at Würth Phoenix
After my graduation in Applied Computer Science at the Free University of Bolzano I decided to start my professional career outside the province. With a bit of good timing and good luck I went into the booming IT-Dept. of Geox in the shoe district of Montebelluna, where I realized how a big IT infrastructure has to grow and adapt to quickly changing requirements. During this experience I had also the nice possibility to travel the world, while setting up the various production and retail areas of this company. Arrived at Würth Phoenix I started developing on our monitoring solution NetEye. Today, in my position as Product Manager, I aim to continuously improve our solutions and to adapt them to actual market requirements.

Author

Patrick Zambelli

After my graduation in Applied Computer Science at the Free University of Bolzano I decided to start my professional career outside the province. With a bit of good timing and good luck I went into the booming IT-Dept. of Geox in the shoe district of Montebelluna, where I realized how a big IT infrastructure has to grow and adapt to quickly changing requirements. During this experience I had also the nice possibility to travel the world, while setting up the various production and retail areas of this company. Arrived at Würth Phoenix I started developing on our monitoring solution NetEye. Today, in my position as Product Manager, I aim to continuously improve our solutions and to adapt them to actual market requirements.

Leave a Reply

Your email address will not be published. Required fields are marked *

Archive