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 |
|
- Maintain NNMi
- Check NNMi Health
- Track Your NNMi Licenses
- Resolve Inconsistencies between State and Status
- Recalculate the Management Mode of Child Physical Components
- Export and Import Configuration Settings
- Backup and Restore NNMi
- Archive and Delete Incidents
- Changing the Management Server
- Delete Nodes
- Delete One or More Objects
- Schedule Outages
- Modifying the Embedded Database Port
- NNMi Self Monitoring
Resolve Inconsistencies between State and Status
At times, differences between State and Status values might occur. These differences generally indicate the system is busy processing large volumes of data, perhaps due to a significant configuration change or network outage.
Note the following:
- NNMi updates State before Status. A delay in Status updates might be due in part to the processing required for root cause analysis performed by the Causal Engine.
- As NNMi completes this processing, the consistency of State and Status is restored.
- Associated incidents might also be delayed during this time.
- Status updates can run behind by the amount of time listed for Delay Processing Input in the System Information dialog's Causal Engine tab.
If the consistency of State and Status is not restored, NNMi enables you to correct the State or Status inconsistencies for each of the following:
To correct either an unexpected State or inconsistent Status value on a node:
1. Navigate to the node view or map of interest and right-click the node
2. Select Polling → Configuration Poll
3. Select Polling → Status Poll
To correct inconsistent Status values on a node for which the State value is correct:
1. Navigate to the nodes view or map of interest and right-click the node
2. Select Polling → Status Poll
To correct State or Status inconsistencies on multiple nodes, use the nnmnoderediscover.ovpl command.
The nnmnoderediscover.ovpl command, when used with the –fullsync option, enables you to re-synchronize the nodes specified.
The re-synchronization process performs the following for each node:
- Rediscovers the node.
- Reloads and refreshes the monitoring configuration for the node.
- Reanalyzes State and Status for the node.
To re-synchronize a single node:
nnmnoderediscover.ovpl –node hostname –fullsync
To re-synchronize all nodes in a file:
nnmnoderediscover.ovpl –file filename –fullsync
Tip To quickly generate the file needed for this command-line tool,consider using the nnmnodegroup.ovpl
command-line tool. See the nnmnodegroup.ovpl Reference Page.
To re-syncrhonize all the nodes on an NNMi management server:
nnmnoderediscover.ovpl -all –fullsync
If a large number of nodes (for example, thousands) are being re-synchronized, it is recommended that you re-synchronize these nodes during off-peak periods, when possible.
NNMi must remain running until the re-sychronization is complete. If NNMi is stopped before the re-synchronization is complete, run the nnmnoderediscover.ovpl command again and allow the re-synchronization to complete.
For more information, see nnmnoderediscover.ovpl.
If you have a Global Network Management environment, also see Node Synchronization Issues
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: