{"id":962,"date":"2017-07-05T23:06:21","date_gmt":"2017-07-05T21:06:21","guid":{"rendered":"http:\/\/www.netexpertise.eu\/en\/?p=962"},"modified":"2021-04-23T10:39:08","modified_gmt":"2021-04-23T08:39:08","slug":"auto-update-devices-in-glpi","status":"publish","type":"post","link":"http:\/\/www.netexpertise.eu\/en\/misc\/glpi\/auto-update-devices-in-glpi.html","title":{"rendered":"Hardware Scanning and Auto Update in GLPI"},"content":{"rendered":"\n

Having loads of physical sites, it is extremely difficult to keep track of device’s locations, and even if you do, you may not be aware some people moved computers or printers around to a new place without telling; It can also be useful to know where a device was last seen.
More importantly, do you know what is on your network? Check how many devices are unknown and not registered in GLPI<\/a>.<\/p>\n\n\n\n


Requirements<\/h3>\n\n\n\n

– Add network switches in GLPI making sure Name (DNS name), brand, location and type fields are filled in. You need managed switches to connect on to them.

– Generate an SSH key<\/a> pair on the server from where you are going to run the script, install the public key on the switches so you can log on automatically on each one of them
Supported switches include Cisco Catalyst, HP Procurve* and 3com but could be ported easily to other brands.
Check Cisco<\/a>, HP<\/a> and 3com official documentation to install the public key on each device.

– Edit GLPI settings (in the script) and run the bash script<\/a>
\u00a0<\/p>\n\n\n\n