Comments (10)
I can see in your agent log glpi-agent is reporting 0.1.134.160
and 172.16.253.246
as ips during the discovery of just the 172.16.253.246 ip. During the netinventory task, the agent receives to run netinventory on the first ip 0.1.134.160
event if it's not the one related to the ip range configured on the task. And this explains why the agent is reporting a communication error to glpi.
Actually I think glpi-inventory plugin when looking for device ips should only use the ip related to the configured task ip range in the XML sent to the agent. @stonebuzz ? Do you remember if we still discussed about this issue ? This sounds familiar to me.
from glpi-inventory-plugin.
Yes, we had encountered the problem once.
Here the plugin, when generating the targets, does not remember from which IP range the target is found.
So when I send the information back to the agent, I can't determine the IP based on the IP range provided in the job.
(in addition, it is possible to provide several IP ranges in a job .....)
For the moment I have no idea how to fix it (at least the fork code doesn't allow me to find the information) and it remains a very, very "rare" case.
The easiest thing would be to delete (permanently) this network port (which will delete the offending IP)
The next discovery will not add it because discovery (after asset creation) does not add port information.
Thus, during the SNMP inventory, only the "correct" IP will be given to the agent.
from glpi-inventory-plugin.
I can understand you can provide another ip than the one used during discovery if the reported ones are all in the configured ip range. But in his case, he even has reduced the range to one ip ^^
IMHO why not just checking which ips are in the expected ip range and choose the first ?
To me, this should reduce the chance to use the wrong ip.
from glpi-inventory-plugin.
I can try to contribute a suggestion to separate the first IP that the equipment was inventoried into in an independent field within the computer for network devices and printers, from the IP ranges that it was inventoried the first time with the discovery, perhaps this will help with the task of snmp to avoid bugs of losing which IP the equipment was on instead of trying to use the information in Network Ports
from glpi-inventory-plugin.
hello, It work for me by removing the ip 0.1.134.160. But that ip does not exist in my network not even on my switch config, and i notice that glpi puts that same address to most of the cisco switchs, i don't know why.
Now that I'm able to inventory my switches, the ones that are configured in stack mode, glpi is doubling the number of ports
from glpi-inventory-plugin.
@francisco-vilaca please open new ticket(s) for issue(s) not directly related to the initial one described here.
from glpi-inventory-plugin.
ok
from glpi-inventory-plugin.
The easiest thing would be to delete (permanently) this network port (which will delete the offending IP)
The next discovery will not add it because discovery (after asset creation) does not add port information.
Thus, during the SNMP inventory, only the "correct" IP will be given to the agent.
Does this fix the initial issue?
from glpi-inventory-plugin.
The easiest thing would be to delete (permanently) this network port (which will delete the offending IP)
The next discovery will not add it because discovery (after asset creation) does not add port information.
Thus, during the SNMP inventory, only the "correct" IP will be given to the agent.Does this fix the initial issue?
Yes, removing the extra IP worked as expected with the SNMP task for the device in question.
from glpi-inventory-plugin.
Great, thank you for the feedback.
I'll close that issue for now since it's resolved, I guess it should be OK now that your data has been redressed.
from glpi-inventory-plugin.
Related Issues (20)
- Self-deployement : Cible pour le déploiement à la demande, utilisateurs introuvables HOT 1
- Running task Deploy - [error] [http client] Can't decode JSON content, starting with HOT 7
- Repository has some strange version tags HOT 1
- Update 1.3.5 HOT 1
- Self-deploy : Add target for deploy on demand
- SNMP inventory problem with disconnecting devices from the switch HOT 10
- Change agent name according to pc name change HOT 2
- GLPI Inventory not linking with Computers ITEM 0 HOT 1
- PHP Warning (2): Trying to access array offset on null in statediscovery.class.php at line 168 HOT 9
- taskscheduler error when using a dynamic group with a criteria on the fields plugins HOT 3
- Deployment Task Message is Garbled on Client HOT 8
- Collect : access denied on POST when using a proxy HOT 5
- No access to Inventory Agents HOT 4
- Accents isn't being rendered on NetInventory task HOT 3
- Tag isn't added to NetInventory tasks HOT 4
- Cisco/Comware switches returns VLAN-interface Base MAC Address as Mgmt Port HOT 1
- eth0 port (Aruba AP) isn't being imported through GLPI Agent, only when injecting manually
- About the server URL to use as server parameter, it will depends on your server and plugins installation
- Strange behaviour of inventory and error in Apache2 HOT 8
- Import children locations HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from glpi-inventory-plugin.