Self-Solve Knowledge Search

Minimize Maximize
Probe deployment sizing
Title :
Probe deployment sizing
Document ID :
Product - Version:
universal cmdb config mgr ; universal cmdb ; universal discovery for oracle lms ;
OS :
Updated :
Mon Mar 14 08:43:03 GMT 2016
Summary :
The Support Matrix documentations contains the necessary information about Probe requirements. For example, the Probe requires 16 GB RAM(recommend) for Standard type deployment and 24 GB(recommend) for Enterprise deployment.
How to define the Probe deployment. Is there any formula to use?
How to calculate the number of discovered nodes per a probe?
There is a well known formula for a single Probe calculation to determine the deployment:
Biweekly discovery toward [The number of Inventory Discovery nodes] + daily discovery toward 5 times [the number of application dependency mapping nodes] is less than or equal to 25000 (for Standard deployments) or 50000 (for Enterprise deployments). For example, 15000 inventory discovery nodes (in two weeks) and 2000 application dependency mapping nodes (every day) is a Standard deployment.
The easiest way to calculate the number of discovered nodes per a probe is by creating a report. Create a TQL query bundeled to that report showing Node and ipAddress classes. Next, filter the "ip_probename" (IP Probe Name) attribute of the ipAddress CIs to show the nodes which belong to a certain probe.