Replies: 1 comment
-
Hi @kipshak93 for routers, it may be sufficient to add an entry in sysobject.ids file, check this project to try it: https://github.com/glpi-project/sysobject.ids But this may not be sufficient. The fundamental problem is probably important values are not retrieved like essentially serialnumber. We don't support MIB files as is, but we can develop a dedicated module for each device which can follow MIB files to find expected values. And generally, as we not always have a MIB available, we also develop the module after a device SNMP walk output analysis. So if you want to see your device in GLPI, the best thing to do is to open one issue for each device you want to be supported. For each issue, join MIB files if you can, but at least join a SNMP walk output in the required format and provide expected values for at least serialnumber, model and manufacturer. You can also join the current XML generated using glpi-netinventory script as it will show what glpi-agent can really discover at this time. With that data, we can quickly develop a dedicated module you'll be able to add into the MibSupport folder. Of course if you have yourself perl development knowledges, you can develop your own module a submit it in a PR for integration in glpi-agent project. |
Beta Was this translation helpful? Give feedback.
-
Your question
how and where to add additional mib for net discovery? We use huawei, fortinet, tplink, etc. equipment in our company, but glpi detects them as unmanaged devices during network detection.
Beta Was this translation helpful? Give feedback.
All reactions