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 |
|
- Configure
- Configure Event Collection in Consolidated Setups
- Configure Topology Collection in Consolidated Setups
- Configure Metric Collection in a Consolidated Setup
- Configure Data Collection in Distributed Setups
- Configure Integration to Monitor Multiple VROPS Servers
- Manage Integration Services
- Configuration Options
- Entity Mappings
Configure Integration to Monitor Multiple VROPS Servers
To monitor multiple VROPS servers with a single integration, create new instances of the VROPS integration configuration:
- In the
/var/opt/OV/datafiles
(Linux) or%OvDataDir%datafiles
(Windows) directory, create a new directory namedHPBsmIntVROps<server>
, where<server>
is an identifier, used for the server throughout the following steps. For example,HPBsmIntVROpsSys1
. - In the
/var/opt/OV/tmp
(Linux) or%OvDataDir%tmp
(Windows) directory, create a new directory namedHPBsmIntVROps<server>
. - Go to the
/var/opt/OV/conf
(Linux) or%OvDataDir%conf
(Windows) directory and make a copy of theHPBsmIntVROps
directory. Name itHPBsmIntVROps<server>
. - Go to the
/var/opt/OV/Installation
(Linux) or%OvDataDir%installation
(Windows) directory and make a copy of theovc
directory. Name itovc<server>
. -
In the
/var/opt/OV/conf/HPBsmIntVROps<server>
(Linux) or%OvDataDir%conf/HPBsmIntVROps<server>
(Windows) directory, create a copy ofvrops_remote.conf
file and name them as follows:vrops_remote<server>.conf
-
Open the
vrops_remote<server>.conf
file and change the following attributes:-
'log-file' : '/var/opt/OV/log/vropsremote.%d.log'
to
'log-file' : '/var/opt/OV/log/vropsremote<server>.%d.log '
-
Change the
vrops-hostname
andvrops-port
options to the corresponding VROPS system. -
‘vrops_user’
to
‘vrops_user<server>’
-
‘vrops_password’
to
‘vrops_password<server>’
-
‘datafiles/HPBsmIntVROps’
to
‘datafiles/HPBsmIntVROps<server>’
-
‘idIPDns.txt’
to
‘idIPDns<server>.txt’
-
‘vrops_topology.xml’
to ‘
vrops_topology<server>.xml’
-
‘events/HPBsmIntVROps’
to
‘events/HPBsmIntVROps<server>’
-
‘tmp/HPBsmIntVROps’
to
‘tmp/HPBsmIntVROps<server>’
-
‘metrics/HPBsmIntVROps’
to
‘metrics/HPBsmIntVROps<server>’
-
'vrops_metric_timestamp'
to
‘vrops_metric_timestamp<server>’
-
‘vrops_alerts_timestamp’
to
‘vrops_alerts_timestamp<server>’
-
‘vrops_topology_discovery.xml’
to
‘vrops_topology_discovery<server>.xml’
-
‘vrops_events.xml’
to
‘vrops_events<server>.xml’
-
‘vrops_metrics.xml’
to
‘vrops_metrics<server>.xml’
-
-
Enter credential for each server (go to
/opt/OV/bin64
for Linux).genintcrypt ––generate
genintcrypt ––set vrops_user<server>
genintcrypt ––set vrops_password<server>
-
Go to the
/var/opt/OV/installation/HPBsmIntVROps/ovc<server>
(Linux) or%OvDataDir%installation\HPBsmIntVROps\ovc<server>
(Windows) folder. Create a copy ofHPBsmIntVROps.xml
file and rename it toHPBsmIntVROps<server>.xml
Open the
HPBsmIntVROps<server>.xml
file and change the following lines:-
‘<ovc:Name>vrops’
to
‘<ovc:Name>vrops<server>’
-
‘VROPS’
to
‘VROPS<server>’
-
‘<ovc:CommandLine>HPBsmIntVROps’
to
‘<ovc:CommandLine>HPBsmIntVROps<server>’
-
‘vrops_remote.conf’
to
‘vrops_remote<server>.conf'
-
'"$ConfDir/HPBsmIntVROps/vrops_remote.conf'
to
'"$ConfDir/HPBsmIntVROps<server>/vrops_remote<server>.conf'
-
-
Register new
ovc
processes:For Linux:
/opt/OV/bin/ovcreg -add /var/opt/OV/installation/HPBsmIntVROps/ovc<server> HPBsmIntVROps<server>.xml
For Windows:
ovcreg -add %OvDataDir%installation\HPBsmIntVROps\ovc<server> HPBsmIntVROps<server>.xml
-
Open the Operations Connector console and create a copy of each policy. Name them as follows:
Operations Connector for VROPS (xx.xx) - Event Integration<server>
Operations Connector for VROPS (xx.xx) - Metric Integration<server>
Operations Connector for VROPS (xx.xx) - Topology Integration<server>
Operations Connector for VROPS (xx.xx) - Topology Self Discovery<server>
-
Open the
Operations Connector for VROPS (xx.xx) - Event Integration<server>
policy and performing the following:-
Change the source path from
HPBsmIntVROps
toHPBsmIntVROps<server>
-
Change the default source event ID from
VROps:<$DATA:/vrops_event_message/alertid>
toVROps<server>:<$DATA:/vrops_event_message/alertid>
-
- Open the policy
Operations Connector for VROPS (xx.xx) - Metric Integration <server>
and change source path fromHPBsmIntVROps
toHPBsmIntVROps<server>
- Open the policy
Operations Connector for VROPS (xx.xx) - Topology Integration <server>
policy and change the source topology XML file from<$OvDataDir>/datafiles/HPBsmIntVROps/vrops_topology.xml
to<$OvDataDir>/datafiles/HPBsmIntVROps<server>/vrops_topology<server>.xml
. -
Open the policy
Operations Connector for VROPS (xx.xx) - Topology Self Discovery <server>
and change the source topology XML file from<$OvDataDir>/datafiles/HPBsmIntVROps/vrops_selfdiscoverytopo.xml
to<$OvDataDir>/datafiles/HPBsmIntVROps<server>/vrops_selfdiscoverytopo<server>.xml
-
-
Start the
ovc
services:For Linux:
/opt/OV/bin/ovc -start vrops<server>
For Windows:
ovc -start vrops<server>
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: