Balance ACTIVE IP addresses across the uCMDB probe cluster

Balance ACTIVE IP addresses across the uCMDB probe cluster

Currently the probe cluster will spread the discovery range IPs over the available probe servers, but if a lot of the probe ranges dont have active devices, the IP addresses are still assigned to a probe meaning anything other then IP discovery will not be balanced.

I would like to see the IP addressed balanced based on the outcome of the IP scans so only active IP addresses are considered. 

doronorbach Honored Contributor.
Honored Contributor.
Status changed to: Waiting for Votes

Thank you! The idea has received an initial review to ensure adherence to our idea submission and community guidelines. We ask the community to help prioritize the idea with comments and community support (votes/kudos).

M_vanderMeer Trusted Contributor.
Trusted Contributor.
Nice to have indeed. Some probes are more busy then others because not all ipadresses are in use.
mike_toronto2 Honored Contributor.
Honored Contributor.

Nice to have, but how would this be possible with smart agents which hard code the probe they have to respond back to and with devices that jump between probes (such as laptops) collecting inconsistent results due to different cache's on different probes? 

bnadon Super Contributor.
Super Contributor.

Very important feature to have; it affects directly the overall discovery performance.

Micro Focus Contributor
Micro Focus Contributor

Nice to see the idea.  We also have similar idea in internal innocation session to have loadbalance in between Probes and Agents(Smart agent) and have agent to find probe intead of you pre-config the iprange on the probe.  The limitation is it must be smart agent... and I am not sure how many customer like to install agent agnist agentless. 


Micro Focus Contributor
Micro Focus Contributor
Status changed to: Under Consideration

This ideareceived enough votes and comments from the community and been reviewed by Micro Focus for strategic fit. These ideas are continually monitored and considered for prioritization in our development planning.

Super Contributor.. LeeWidman Super Contributor..
Super Contributor..

It is time for this.  It would reduce discovery time significantly and also allow for a reducuction on the amount of probes.

Contributor.. TobyFruthParson Contributor..

We only do agentless discovery. The probe clustering in its current form is useless. A probe could have 10,000 IP addresses, but only 500 Windows nodes it's discovering by shell. Another probe could have 1,000 IP addresses, and 1,000 Windows nodes it's discovering by shell. If they were clustered, the busy probe would be given 8,000 IP addresses and potentially up to 500 more Windows nodes. This is not intelligent. Intelligent clustering would balance the workload, so that each probe has 750 Windows nodes AND 8,000 IP addresses. Better yet, the app would analyze other factors and create a highly optimized balance between the probes.

Micro Focus Expert
Micro Focus Expert
Status changed to: Accepted

The idea has received enough votes and comments from the community and been reviewed by the Micro Focus product team. It is officially on the roadmap for development and delivery. (Subject to change, and not a commitment.)

The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.