Searching the Help
To search for information in the Help, type a word or phrase in the Search box. When you enter a group of words, OR is inferred. You can use Boolean operators to refine your search.
Results returned are case insensitive. However, results ranking takes case into account and assigns higher scores to case matches. Therefore, a search for "cats" followed by a search for "Cats" would return the same number of Help topics, but the order in which the topics are listed would be different.
Search for | Example | Results |
---|---|---|
A single word | cat
|
Topics that contain the word "cat". You will also find its grammatical variations, such as "cats". |
A phrase. You can specify that the search results contain a specific phrase. |
"cat food" (quotation marks) |
Topics that contain the literal phrase "cat food" and all its grammatical variations. Without the quotation marks, the query is equivalent to specifying an OR operator, which finds topics with one of the individual words instead of the phrase. |
Search for | Operator | Example |
---|---|---|
Two or more words in the same topic |
|
|
Either word in a topic |
|
|
Topics that do not contain a specific word or phrase |
|
|
Topics that contain one string and do not contain another | ^ (caret) |
cat ^ mouse
|
A combination of search types | ( ) parentheses |
|
- Data Flow Probe Setup
- Data Flow Probes and Clusters
- UCMDB Integration Service
- Cluster Range Distribution Policy
- Limiting IP Movement in a Cluster
- Job Execution Policies
- Data Flow Probe Upgrade Overview
- Effects of Range Type on Discovery Workflows
- Install and Run Data Flow Probe and Probe Database on Linux with Non-Root User Account
- Using HTTPS Port 8453 as Default for Data Flow Probe
- How to Install a Second Data Flow Probe on a Windows Machine
- How to Deploy Hotfixes and Track Hotfixes Applied on Data Flow Probe
- How to Set Master Key for Password Encryption on Data Flow Probe
- How to Add Data Flow Probes to UCMDB
- How to Add Probe Clusters to UCMDB
- How to Start a Data Flow Probe
- How to Stop a Data Flow Probe
- How to Change the Data Flow Probe Default Domain
- How to Change the Data Flow Probe Port
- How to Move Resources From One Domain to Another Domain
- How to Change the UCMDB Integration Service Default Domain
- How to Check the UCMDB Integration Service Status
- How to Limit IP Movement in a Cluster
- How to Update the Data Flow Probe's IP Address
- How to Update the Data Flow Probe Memory Size
- How to Define Owner Tenants on Data Flow Probes
- How to Configure the Number of Connections to Other Machines
- How to Configure Periodic Data Flow Task Updates
- How to Prevent Probes from Sending Touch Information Simultaneously
- How to Encrypt/Decrypt IP Ranges Information on the Probes
- How to Configure the Data Flow Probe to Automatically Delete CIs
- How to Delete Unsent Probe Results
- How to Clear Data Flow Probe Data
- How to Clear UCMDB Integration Service Data
- How to Deploy a Data Flow Probe CUP
- How to Deploy a Data Flow Probe CUP Manually
- How to Align the Data Flow Probe CUP with the UCMDB Server CUP
- How to Uninstall Probe CUPs Manually
- How to Set Maximum Objects for Insert Results
- Data Flow Probe Process Ports
- DataFlowProbe.properties File
- DataFlowProbe.properties Parameters
- DataFlowProbeOverride.properties File
- Data Flow Probe Database Scripts
- Data Flow Probe Log Files
- Data Flow Probe Setup User Interface
- Troubleshooting and Limitations
Cluster Range Distribution Policy
A probe cluster is a logical container for a number of Data Flow Probes. When you define a network range for the cluster, the cluster distributes the overall set IP address ranges between the Probes in the cluster balancing the load between them.
A cluster balances its IP addresses among its Probes as follows:
-
To ensure that specific IP addresses are always distributed to a particular Probe, you can set a TQL query constraint on that Probe. When the TQL query runs, the resulting IP addresses are distributed to the respective Probe.
-
All of the remaining IP addresses in the cluster's range are then distributed evenly among all of the cluster's Probes (including the Probes with the TQL query constraints).
Note The cluster balances its IP addresses over its Probes in such a way so as to minimize IP movement after the IP addresses have been distributed to the Probes.
If the cluster's IP addresses become unbalanced, that is, one Probe is assigned a wider set of IP ranges than other Probes, the cluster tries to re-balance the IP addresses among its Probes. The cluster is allowed to retry to balance the Probes depending on how much IP movement is allowed. For details, see How to Limit IP Movement in a Cluster.
Example
Consider the following scenario:
-
Cluster Range: 10.10.10.0 - 10.10.10.255
-
Cluster includes Probe1, Probe2, Probe3
-
TQL constraint on Probe1: Probe1's range must include IP addresses 10.10.10.20 - 10.10.10.40
After running a TQL query on UCMDB, the following IP addresses are returned:
The cluster balances its network ranges among its Probes as follows:
- Because of the TQL constraint on Probe1, range 10.10.10.30 - 10.10.10.40 is specifically distributed to Probe1
- Range 10.10.11.0 - 10.10.11.20 is out of the cluster's range, so it is not distributed to any of the cluster's Probes
-
The remaining IP addresses in the cluster's ranges are then evenly balanced among all of the cluster's Probes. The remaining ranges are:
- 10.10.10.0 - 10.10.10.29
- 10.10.10.41 - 10.10.10.255
The cluster always attempts to distribute an IP address to a Probe whose TQL constraint includes that IP address
Note Technically, IP addresses 10.10.10.20 - 10.10.10.29, which fall within Probe1's TQL constraint, can be distributed to any of the cluster's Probes, and not necessarily only to Probe 1. This is because these addresses were not found by the TQL query, which means they do not exist in UCMDB. In turn, no actual workload can be distributed to them anyway, so it is insignificant which Probe received these IP addresses.
Nonetheless, the cluster does make a special effort to distribute these IP addresses to Probe1. This way, if a subsequent recalculation of the TQL query returns these IP addresses, they are already in place, and IP movement is minimized.
Furthermore, when the TQL query is recalculated, and if these addresses are found in UCMDB, these IP addresses are indeed distributed to Probe 1, per its TQL constraint.
We welcome your comments!
To open the configured email client on this computer, open an email window.
Otherwise, copy the information below to a web mail client, and send this email to cms-doc@microfocus.com.
Help Topic ID:
Product:
Topic Title:
Feedback: