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.6 available

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

IP Discovering on classe B network is very painful

Hi,

I tested the IP Discovery on a classe B network (netmask 255.255.0.0) and I have some problem with this fonctionnality.

On Linux agent (Ocsinventory-Unix-Agent-2.1.1), the discovery left in time out and I didn't have no IP send to the OCS 2.1.2 server.

(error message in agent log : Ocsinventory::Agent::Backend::IpDiscover::IpDiscover killed by a timeout. )

I found an option to modify time out ( --backend-collect-timeout=20000 ) because this process ipdiscovery takes more than 3 hours. With this parameter and during this time, the agent wait the end of ip discovering process. This not really usable.

On Windows Agent (2.1.1.2), I see some log with ip discovering task but I didn't test it completely. But during this time, the ip discovering task seem block any software deployement on this computer.

Is it possible to do it without blocking agent or left in time out (ie. limit each scan at some IP address or range IP address ?)

Is it possible to launch ipdiscover manually and import the xml manually in the OCS server ?

Best regards
in IP Discover by (150 points)

1 Answer

0 votes
A ipdiscover on a class B is not a good idea. it must do a interogationon all the address on your class B. So you will try to access to 65 534 adress.
by (2.1k points)
 
Powered by Question2Answer
...