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.
Words and Phrases
| 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. |
Using Boolean Operators
| 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 |
|
- Reference
- How to Define a New Port
- How to Discover IP Addresses in Universal Discovery
- How to Use the cpVersion Attribute to Verify Content Update
- How to Delete Files Copied to a Remote Machine
- How to Run HPCmd from Windows Server 2008, 2008 R2, 2012, and 2012 R2 Machines
- Files Copied to a Remote Machine
- Content Pack Configuration Files
- Additional Protocol Information
- Event Based Discovery
- PrimaryDNSName Logic
- Supported UNIX Shells
- Troubleshooting and Limitations
- Discovery and Integrations Content Guide - Support Matrix
- Universal Data Model (UDM)
- HPE Universal CMDB Help Center
PrimaryDNSName Logic
Previously, the DNS Resolver job sets the PrimaryDNSName (primary_dns_name) of a Node to the resolved DNS name of the smallest IP address integer equivalent among all IP addresses contained by a given Node. If either the backup network or cluster virtual IP addresses have a numerically smaller address than the address of the Node, that address incorrectly updates the PrimaryDNSName of the Node.
In order to solve this issue, the PrimaryDNSName logic is changed as follows:
For a full DNS name (for example, host1.cms.chn.hpe.com),
- If the short name (that is, host1 in the example) of the full DNS name is NOT equal to the host name, the full DNS name will NOT be considered as the PrimaryDNSName.
-
If the short name (that is, host1 in the example) of the full DNS name is equal to the host name, the full DNS name will be one candidate of the PrimaryDNSName.
For each candidate,
- Covert its related IP address to the integer equivalent, and then retrieve the smallest one.
- Take the DNS name of the smallest IP address integer equivalent as the PrimaryDNSName.
For example:
- Node 1 has three IP addresses: A, B, C; the host name is host1.
- IP address A is resolved as host1.cms.chn.hpe.com.
- IP address B is resolved as host2.cms.chn.hpe.com (That is possible, in the cluster environment, some cluster IP addresses can be resolved as cluster names).
- IP address C is resolved as host1.chn.hpe.com.
- IP address B is the smallest IP address integer equivalent.
Previously, the DNS Resolver job takes host2.cms.chn.hpe.com as the PrimaryDNSName regardless of the fact that host2 !=host1, because IP address B is the smallest IP address integer equivalent.
Currently, host2.cms.chn.hpe.com is no longer considered as the PrimaryDNSName. Both host1.cms.chn.hpe.com and host1.chn.hpe.com are candidates of the PrimaryDNSName. For these candidates, covert their related IP addresses to the integer equivalents. If A > C, host1.cms.chn.hpe.com is the PrimaryDNSName.
