Forward OMi Event Status
Use the bvd-event-status command-line interface to forward event status data from OMi to BVD.
BVD data channels opened up by the bvd-event-status command-line interface:
omi
mdb
dashboard_name
label
type
Before you can use the tool, install it as described in Install and configure the event and KPI status forwarding tools on the OMi server.
Location
<OMi_HOME>/opr/bin/bvd-event-status.[bat|sh]
Synopsis
bvd-event-status <connection> -dashboard_name <Dashboard Name> [-polling_interval <Polling Interval>] [-dashboard_config <BVD Config File>] -help | -verbose | -version
Options
Option | Description |
---|---|
{‑dashboard_name|‑dn} <Dashboard Name>
|
Sets the name of the dashboard for which event status data will be collected. |
{‑polling_interval|‑pi} <Polling Interval>
|
Sets the polling interval (in milliseconds) for collecting event status data. Default: 10,000 milliseconds (10 seconds) |
{‑dashboard_config|‑dc} <BVD Config File>
|
Sets the path to the BVD configuration
file Windows: Linux: |
{‑post2|‑p2}
|
For internal use only. |
{‑help|‑h} |
Displays a summary of the command options. |
{-verbose|-v}
|
Prints verbose output. |
‑version
|
Displays version information for the tool. |

-username <login name> [ -password <password> | -smartcard | -winCrypto | -jks <keystore path> -jksPassword <keystore password> ] [[-port <port>] [-server <gatewayserver>] [-ssl]
]
Note: If you do not specify the OMi server to connect to (using the ‑server
option), the command is executed on the server to which you are logged on.
Option | Description |
---|---|
{-username|-user} <login name>
|
Sets the login name of the user required to execute CLI operations on the target gateway server. |
{-password|-pw} <password>
|
Sets the password for the specified user. If using SSH on Cygwin, either enter the password in free text or use other communication methods, for example Java keystore, Windows keystore, or smart card authentication. Default value: empty string |
{-smartcard|-sc}
|
Uses the certificate stored on smart card or security token for authentication. |
{-winCrypto|-wc}
|
If OMi is configured for TLS mutual authentication, this option specifies to use the Windows certificate store for authentication. The certificate store must hold exactly one client certificate, which OMi will use to authenticate the user. This option is only available on Windows systems. |
{-jks|-j} <keystore path>
|
If OMi is configured for TLS mutual authentication, this option can be used to specify the Java keystore to be used for authentication. The keystore must hold exactly one client certificate, which OMi will use to authenticate the user. Note: It is not necessary that the client certificate contains the flag "Smart Card Logon (1.3.6.1.4.1.311.20.2.2)" in the "Enhanced Key Usage" field. |
{-jksPassword|-jp} <keystore password>
|
If OMi is configured for TLS mutual authentication, this option can be used to specify the Java keystore to be used for authentication. The keystore must hold exactly one client certificate, which OMi will use to authenticate the user. Note: It is not necessary that the client certificate contains the flag "Smart Card Logon (1.3.6.1.4.1.311.20.2.2)" in the "Enhanced Key Usage" field. |
{-port|-p} <port>
|
Uses port Default value of |
-server <GatewayServer>
|
Sets the target gateway server, using Default value of |
-ssl |
When this option is specified, the HTTPS protocol is used to connect to the target gateway server. If omitted, the HTTP protocol is used. |
Exit Status
Exit Status |
Description |
Output |
---|---|---|
0
|
Successful completion of the requested operation |
No output. |
1
|
Failure of the requested operation |
An error message stating why the operation failed, followed by the tool's help text. |
300‑399
|
HTTP Redirection (300-399) |
An error message stating the HTTP error number and description. For more information about HTTP error status values, see publicly available HTTP documentation. |
400‑499
|
HTTP Client Error (400-499) |
|
500‑599
|
HTTP Internal Server Error (500-599) |
Examples
The following example forwards event status from the OMi monitoring dashboard OMi Health Status
to BVD:
\HPBSM\opr\bin\bvd-event-status.bat ‑username admin ‑dashboard_name "OMi Health Status"