New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Netdiscovery strange behaviour #461
Comments
hi, Thanks |
Hello, Thanks |
hi @acdmail why not use GLPI's default reconciliation rules? I confess I don't understand what you're trying to do |
@stonebuzz thanks for you response and suggestion, I will try the default rules once again however unfortunately until now I was always in that 98% of cases :) |
It doesn't really matter, from what I can see/understand, discovery supports a computer. Unfortunately the SNMP discovery/inventory task is only dedicated to network equipment and is not at all intended to manage computers (this will be the case for the next network discovery plugin). I don't really have a solution in this case. normally from an SNMP inventory / discovery the inventory file (related to computer) should not contain a name, so you should match the "Computer constraint (name)" rule Perhaps you should refine the IP ranges to exclude PCs? |
Describe the bug
hi,
We are trying to migrate from GLPI 10.0.6 with FI plugin to GLPI 10.0.11 with glpi inventory plugin 1.3.4, we are trying to use same import and link rules, however are getting different final inventory results (we have put in place simple test setup)
We have installed GLPI Agent 1.71 and inventoried 2 computers, host1 - 192.168.1.40/28 and host2 - 192.168.1.23/28
We have defined the Network discovery task/job for IP range 192.168.1.16/28, in which as target we put IP range 192.168.1.16/28 and as actor host 1
We have also put in place a very simple set of import and link rules like below:
We are running the agent on host 1 in order to perform the Network discovery task as result our inventory is becoming
To reproduce
Expected behavior
As per screenshot we have defined only 4 import rules:
4.Import by IP - rule which will perform the import by IP
However as we can see it seems that rule "Import by IP denied" is not having any effect even if same IP (192.168.1.23) is already present in inventory and belonging to host2 the rule is not denying the import, action passing to next rule "Import by IP" which is updating the host2 leading to non-desirable effects.
To mention here that GLPI 10.0.6 and FI plugin are working properly in this scenario no import is performed
Operating system
Linux
GLPI Agent version
Other (See additional context below)
GLPI version
10.0.11
GLPIInventory plugin
1.3.4
Additional context
No response
The text was updated successfully, but these errors were encountered: