Welcome to OCS Inventory NG community support, where you can ask questions and receive answers from other members of the community.

Please ask questions only in English or French.

Release 2.3 available

The official documentation can be found on http://wiki.ocsinventory-ng.org. Read it before asking your question.

snmp not working [closed]

Hello. I am trying to use the snmp agent functionality for a more complete scan data, but I don't achieve my goal. I follow the article:

http://wiki.ocsinventory-ng.org/index.php?title=Documentation:SNMP

And the agent is correctly registered to my ocs ng 2.3 server (By the way, the snmp agent is the same machine as the ocs ng server... I dont' know if this is a problem) and sends the inventoru correctly. My agent.log is no errors, and connecting correctly with the server. It scans the network as a normal IpDiscover scan.

But a have not results about snmp scans.

The agent, and server at the same time, is a debian 8 machine. The server is working on https way and no errors about the ssl connection.

The output of the perl /etc/ocsinventory-agent/modules.conf command is empty, and the output of the  ocsinventory-agent --debug command is empty too.

I really I will apreciate some of help.
Thanks.

Edit: I have configured another machine (debian 7, in this case) with the OCS-NG agent and I configured it as a snmp scan, and I have exactly  the same results: the agent registers to the server, and send the inventory, but nothing about snmp scan.
closed with the note: Problem solved
asked Jun 24 in OCS Inventory NG agent for Unix by jokland (160 points)
closed Aug 14 by frankb

2 Answers

0 votes
Do you have an SSL certificat on your server and agent ? If yes, look if you do your inventory on https.
answered Jun 30 by kapouik (13,410 points)
0 votes
Thanks kapouik.

I solved the problem last week.

My clients connects to the OCS sever throught a reverse proxy, and the communications only were https from the proxy to the clients. The communication from the proxy to the ocs server was on http.

I solved the problem configuring https on both communications.

Thanks.
answered Jul 3 by jokland (160 points)
 
Powered by Question2Answer
...