1

Topic: Network Discovery Issue

I am trying to test Network Discovery and SNMP on GLPI 0.84.5 with fusion inventory 2.2.

I created a range with just 2 addresses that contains 2 printers that are SNMP enabled. When I run the network discovery task from GLPI, no devices found. No errors but no devices found. I can not run network inventory task because no devices were found in the network discovery.

When I run the fusioninventory-netdiscovery from the command line for the address range, it works correctly. When I run fusioninventory-netinventory for the 2 addresses, it works correctly.

Any suggestions on how to fix this issue?

Thank you for any help that is provided.

2

Re: Network Discovery Issue

Try agent with debug = 2 and past the log here when you do network discovery

Support / dev / installation / configuration GLPI : http://www.siprossii.com/
siprossii : expert GLPI & FusionInventory / Développeur du plugin FusionInventory
IRC #glpi sur freenode.net
GLPI SaaS : http://www.itmanagement-online.com/

3 (edited by tonyw.potts 2014-06-16 18:31:01)

Re: Network Discovery Issue

How can I post the log file? When I try to cut and paste, I get the following error:

Warning! The following errors must be corrected before your message can be posted:
Too more links in message. Allowed 1 links. Reduce number of links and post it again.

4

Re: Network Discovery Issue

I've got the same problem today, so i've made a printscreen of my logs and used http://lut.im to post it on the forum.

GLPI v0.84 + Plugin fusion v2.2
Agent v2.3.4 v2.3.7 v2.3.8 v2.4 Netdiscovery v2.0 Netinventory v2.0
Certification IILAR

5 (edited by tonyw.potts 2014-06-17 14:00:11)

Re: Network Discovery Issue

Here is part of the log. These addresses are for 2 different models of Lexmark printers.

[Mon Jun 16 12:17:52 2014][debug] Thread 3 switched to RUN state
[Mon Jun 16 12:17:52 2014][debug] thread 3: scanning 172.25.13.227
[Mon Jun 16 12:17:52 2014][debug2] thread 3: scanning 172.25.13.227 with netbios: failure
[Mon Jun 16 12:17:52 2014][debug] thread 3: scanning 172.25.13.227 with snmp credentials 2: success
[Mon Jun 16 12:17:52 2014][debug] thread 3: nothing found for 172.25.13.227
[Mon Jun 16 12:17:52 2014][debug] thread 3: scanning 172.25.13.228
[Mon Jun 16 12:17:52 2014][debug2] thread 3: scanning 172.25.13.228 with netbios: failure
[Mon Jun 16 12:18:22 2014][debug] thread 3: scanning 172.25.13.228 with snmp credentials 2: failure
[Mon Jun 16 12:18:22 2014][debug] thread 3: scanning 172.25.13.228 with snmp credentials 1: success
[Mon Jun 16 12:18:22 2014][debug] thread 3: nothing found for 172.25.13.228
[Mon Jun 16 12:18:22 2014][debug] Thread 3 switched to STOP state
[Mon Jun 16 12:18:23 2014][debug] Thread 3 deleted

6

Re: Network Discovery Issue

Net::NBName perl module for NetBios support might be missing
see http://www.fusioninventory.org/document … discovery/ for more details

GLPI v0.84 + Plugin fusion v2.2
Agent v2.3.4 v2.3.7 v2.3.8 v2.4 Netdiscovery v2.0 Netinventory v2.0
Certification IILAR

7

Re: Network Discovery Issue

I assumed by the document that it only needed to respond by one of the protocols. Out of 60 Lexmark printers, 5 due show up and are snmp inventoried correctly but netbios still fails for them. The 5 that do work are all the same model. The 55 missings are another 6-7 models. From the commend line, networkinventory does work correctly but without network discovery adding the devices first, I never get to the SNMP inventory part.

"Any device replying to at least of those protocols will be discovered, with just minimal information, such as mac address and hostname.

Additionaly, if the device replies to SNMP, the agent will attempt to identify it, using its system description (SNMPv2-MIB::sysDescr.0) value. Rule-based identification, using rules hardcoded in the agent, allows a minimal level of identification. Dictionary-based identification, using a server-provided database of known values, allows a more precise identification. If any suceed, the device will be identified.

Discovered devices are then reported to the GLPI servers, and import rules are applied. If the device type (printer, network device, etc...) has not been set, the device will be considered as 'unknown devices'."

8

Re: Network Discovery Issue

I ran the network discovery again on a range of 4 addresses with 4 different types of Lexmark printers and this is what the log says. By the way, 1 of them it discovers and then inventories.

The printers due show up and are SNMP inventoried in OCS but we are hoping to move away from OCS to GLPI with fusioninventory for added features.

[Tue Jun 17 10:02:28 2014][debug] Thread 6 switched to RUN state
[Tue Jun 17 10:02:28 2014][debug] thread 6: scanning 172.25.13.227
[Tue Jun 17 10:02:28 2014][debug2] thread 6: scanning 172.25.13.227 with netbios: failure
[Tue Jun 17 10:02:28 2014][debug] thread 6: scanning 172.25.13.227 with snmp credentials 2: success
[Tue Jun 17 10:02:28 2014][debug] thread 6: nothing found for 172.25.13.227
[Tue Jun 17 10:02:28 2014][debug] thread 6: scanning 172.25.13.228
[Tue Jun 17 10:02:29 2014][debug2] thread 6: scanning 172.25.13.228 with netbios: failure
[Tue Jun 17 10:02:58 2014][debug] thread 6: scanning 172.25.13.228 with snmp credentials 2: failure
[Tue Jun 17 10:02:58 2014][debug] thread 6: scanning 172.25.13.228 with snmp credentials 1: success
[Tue Jun 17 10:02:58 2014][debug] thread 6: nothing found for 172.25.13.228
[Tue Jun 17 10:02:58 2014][debug] thread 6: scanning 172.25.13.229
[Tue Jun 17 10:02:59 2014][debug2] thread 6: scanning 172.25.13.229 with netbios: failure
[Tue Jun 17 10:02:59 2014][debug] thread 6: scanning 172.25.13.229 with snmp credentials 2: success
[Tue Jun 17 10:02:59 2014][debug] thread 6: nothing found for 172.25.13.229
[Tue Jun 17 10:02:59 2014][debug] thread 6: scanning 172.25.13.230
[Tue Jun 17 10:02:59 2014][debug2] thread 6: scanning 172.25.13.230 with netbios: failure
[Tue Jun 17 10:02:59 2014][debug] thread 6: scanning 172.25.13.230 with snmp credentials 2: success
[Tue Jun 17 10:02:59 2014][debug] thread 6: device found for 172.25.13.230
[Tue Jun 17 10:02:59 2014][debug] Thread 6 switched to STOP state