• 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Agent not trying to do SNMP Query/Discovery | snmpv3 issue?
#1
Hi,

first: our versions:
GLPI 0.80.1
fusioninventory-for-glpi-metapackage_0.80_1.1.tar.gz
fusioninventory-agent_rhel-5.6-i386_2.1.14-1.tar.gz on the same host

We have an issue discovering and querying some Cisco switches. They are reachable only with SNMP (ICMP and everything else is denied by a firewall).

The switches only have SNMPv3 allowed and the correct credentials are configured in Fusioninventory.
However, when running a discovery Task, the Agent tries ICMP, Netbios and Port 80, but not SNMP:

This is from the Agent log:

<REPLY>
<OPTION>
<NAME>NETDISCOVERY</NAME>
<DICOHASH>2bbe91ffdbe793c391f5a14408f5dec6</DICOHASH>
<PARAM CORE_DISCOVERY="1" THREADS_DISCOVERY="2" PID="248">
</PARAM>
<RANGEIP ID="7" IPSTART="x.x.x.x" IPEND="x.x.x.x" ENTITY="0">
</RANGEIP>
<AUTHENTICATION ID="5" COMMUNITY="public" VERSION="3" USERNAME="readonlyuser" AUTHPROTOCOL="xxxxxxxxxxxx" AUTHPASSPHRASE="xxxxxxxxxxxxxxxxxx" PRIVPROTOCOL="xxxxxxxxxxx" PRIVPASSPHRASE="xxxxxxxxxxxxxxxxxxxxxx">
</AUTHENTICATION>
</OPTION>
<PROLOG_FREQ>24</PROLOG_FREQ>
</REPLY>
.
.
.


[debug] =END=SERVER RET======
[debug] Core 0 - Thread 1 deleted
[debug] [192.168.x.x] : Netbios discovery
[debug] [192.168.x.x] : SNMP discovery
[debug] [192.168.x.x] Not found
[debug] Core 0 - Thread 0 deleted
[debug] sending XML
[debug] =BEGIN=SERVER RET======
[debug] $VAR1 = '<?xml version="1.0" encoding="UTF-8"?>
<REPLY>
</REPLY>
';
[debug] =END=SERVER RET======
[debug] [task] end of NetDiscovery




Same thing, with SNMP Query:
Added Network device in GLPI with correct: IP, SNMP authentication, SNMP model

Created and startet a scan. The agent receives the XML with the scanning info, but we see on the firewall logs, that it is not even trying port 161.
We tried different versions of the agent and Fusioninventory.

Is this because we are allow SNMPv3 only?

Regards,
raif
  Reply
#2
Strange, I must try it with my switches
Co-leader, official developper
DCS official PARTNER: dcs.glpi@dcsit-group.com
  Reply
#3
i enabled v2 on a single switch just to test it and it works Smile
  Reply
#4
So we have broken v3 :/
Co-leader, official developper
DCS official PARTNER: dcs.glpi@dcsit-group.com
  Reply
#5
I confirm that.
snmp v3 is broken.
snmp v1/2 works perfectly.
  Reply
#6
Hello good,

  How to activate the SNMPv3 configuration? or snmpv3 not working?
  I have a Nagios agent, released as pull. I would like to know the steps to configure a snmpquery by v3

  I created a tag: lab-SNMPv3 with all the connection data for SNMPv3 user password and password encryption and encryption.
  When I make a task force as v3 doesn't discover anything, I return it to launch as v2 and I discover any change in any switch.

any ideas?

Thank you.

A greeting.
  Reply
#7
hi all.
first post in this forum.
i've changed Live.pm to get v3 to work by setting user, authtype, crypttype, encpw and the authpw in the source ... and it works :-)

is there a known problem ?

if not .. to debug this issue ... what module on the glpi-server hands over the v3 settings ?

( i searched but wasnt able to find any snmp v3 how to . )

thx & greetings

btw: glpi & fusinv are realy amazing Smile
  Reply
#8
Save time and make work fast by using windows 10 notepad leave old version and keep it ever on...
  Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)