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 |
|
Were All Seeds Discovered?
- From the Configuration workspace, under Discovery, click Seeds.
-
On the Seeds page, sort the list of nodes by the Discovery Seed Results column. For any node in an error state, consider the following:
- Failed discovery due to an unreachable node or unresolved DNS name or IP address—For these types of failures, verify network connectivity to the node and check for accurate DNS name resolution. To work around DNS issues, use the IP address to seed the node or include the hostname in a
hostnolookup.conf
file. For problems due to IP addresses that should not be resolved to hostnames, include the IP addresses in aipnolookup.conf
file. See thehostnolookup.conf
andipnolookup.conf
reference pages, or the Linux manpages, for more information. -
License node count exceeded—This scenario occurs when the number of devices already discovered reached your license limit. You can either delete some discovered nodes or purchase additional node pack licenses.
When tracking license information, note the following:
-
Consumption: NNMi discovers and manages nodes up to the NNMi licensed capacity limit (rounded up):
-
VMwareVMware ESX and VMware ESXi software uses SOAP protocol to implement bare-metal hypervisors. : Each device with a Device Profile of
vnwareVM
is equivalent to 1/10th node. - All other devices are equivalent to one discovered node.
-
For details about license limits, see “Track Your NNMi Licenses” in the NNMi Help for Administrators.
-
- Node discovered but no SNMP response—SNMP communication problems can occur for seeded devices as well as devices that are discovered through auto-discovery. For more information, see Evaluate Communications.
- Failed discovery due to an unreachable node or unresolved DNS name or IP address—For these types of failures, verify network connectivity to the node and check for accurate DNS name resolution. To work around DNS issues, use the IP address to seed the node or include the hostname in a
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 network-management-doc-feedback@hpe.com.
Help Topic ID:
Product:
Topic Title:
Feedback: