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 |
|
Mappings Used in Event Integration
OpsCx for VROPS includes preconfigured event mappings and rules that you can customize. The mappings and rules are defined in the Operations Connector policy for VROPS events. To reconfigure them, make sure the policy is imported into Operations Connector, and then edit it in the Operations Connector web interface.
Default Event Mappings and Rules
Default Severity Level Mapping
VROPS Alert Criticality | OMi Event Severity |
---|---|
CRITICAL |
Critical |
IMMEDIATE |
Major |
WARNING | Warning |
INFO | Normal |
NONE | Unknown |
Default Event Attributes
Event Policy Attribute | VROPS Alert Attribute(s) | Mapping |
---|---|---|
Title |
info
|
|
Description |
info
source_name
|
|
Severity | alertlevel
|
<$MAP(mapalertlevel)>
|
Time Created | starttimeutc
|
|
Category |
VROps *
|
|
Node | source_name
|
|
Related CI | source_mame
|
|
Source CI | drilldown_location
|
|
Source Event ID | VROps:alertID
|
|
Send with closed status | true or false based on statusid |
<$MAP(mapStatus)> |
* This is a literal value
Policy Rules
Rule | Event Type Indicator | Mapping |
---|---|---|
HostNotResponding |
|
<$MAP(mapETIVal-ResAvail|Unavail)>
|
ResourceDown | NodeStatus:Up or NodeStatus:Down |
<$MAP(mapETIVal-ResUpDown)>
|
The entire event type indicator (ETI) mapping is based on the alertlevel
event attribute in VROPS. An alert level value should be mapped to the correct ETI value.
Rules not listed in the previous table do not set an ETI. They only attempt to relate the event to the corresponding configuration item (CI) in the Run-Time Service Model (RTSM) database of OMi.
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: