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 |
|
Known Issues and Workarounds
Changes made to the VROPS topology are not reflected correctly in OMi
Symptom
In the OMi web interface, unusual topology hierarchy is presented. For example, some configuration items (CIs) might appear isolated from the rest of the collected topology, although they should not because they are related to other monitored VROPS objects.
Action
By default, the Detect deltas option is selected in the Operations Connector policy for VROPS topology. With such a configuration, only recent changes in the VROPS topology are propagated to OMi. In some cases, these changes provide insufficient information resulting in incorrect representation of the topology in OMi. Perform the following steps:
-
Log on to the Operations Connector web interface.
-
Right-click the OpsCx for VROPS (01.00) - Topology Integration policy and select Edit.
-
Click the Source tab.
-
In the Source page, clear the Detect deltas option.
-
Click Save and Close to apply the change.
During metric collection, action failures are logged into the integration service log file
Symptom
Sometimes, the queried object or the respective metric key is not present in the VROPS database. In such circumstances, the metrics integration service (in a consolidated setup) or the shared integration service (in a distributed setup) logs the error similar to the following into its log file:
Example 1:
::vrops> Failed to retrieve topology data! HTTP 400 Bad Request
::metric> Failed to fetch object relationships for '<Object>'
Example 2:
::vrops> Failed to retrieve metric data '<MetricKey>'! HTTP 400 Bad Request
::metric> Failed to fetch metrics for '<FQDN>'
Action
None. You can safely ignore the error message.
Directory created during the installation might not be deleted during the removal
Symptom
At the end of the removal of Operations Connector for VMware vRealize Operations Manager, after you close the installer program, you might notice there are still a few files left in the <OvDataDir>/tmp/HPBsmIntVROps directory.
Action
Open a Command Prompt window (command shell) or launch a graphical file manager, and manually delete the entire <OvDataDir>/tmp/HPBsmIntVROps directory to complete the removal process.
Error during the installation of OpsCx for VROPS on Operations Connector 10.11
Symptom
When installing the OpsCx for VROPS on Operations Connector 10.11, the installation fails due to a prerequisite check of Operations Connector. The installation checks whether the Operations Connector is installed on the system. This check fails because of the name change of the framework from BSM Connector to Operations Connector.
Action
For Operations Connector 10.11, to install the OpsCx for VROPS, run the following command:
<Connector_Installer.exe> -DSKIPCHECKS=true
Before Contacting Software Support
If you cannot solve your issue, report it. Before contacting Software Support, make sure that:
-
You have performed the general checks. See General Troubleshooting Guidelines topic.
-
You have collected relevant data that might be required to send to Software Support: a description of your problem, characteristics of your environment, related entries logged in the operating system event log or in the Operations Connector for VMware vRealize Operations Manager log files.
Software Support personnel will then provide you with further instructions. Among other things, you may be asked to change the Operations Connector for VMware vRealize Operations Manager logging severity level, to repeat or perform particular operations in your Operations Connector for VMware vRealize Operations Manager environment, and to collect specific data from your system and send them to Software Support.
The Software Support personnel are not qualified to solve the issues related to third‑party software or hardware.
To contact Software Support, see the web site at https://softwaresupport.softwaregrp.com.
Related topics
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 ovdoc-asm@hpe.com.
Help Topic ID:
Product:
Topic Title:
Feedback: