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	`AND` `and` `+` (plus symbol) `&` (ampersand)	`cat AND dog` `"cat food"+milk` `"cat food"&"dog food"`
Either word in a topic	`OR` `or` `\|` (pipe)	`cat OR dog` `cat \| dog`
Topics that do not contain a specific word or phrase	`NOT` `not` `!` (exclamation point)	`NOT cat` `! dog`
Topics that contain one string and do not contain another	`^` (caret)	`cat ^ mouse`
A combination of search types	`( )` parentheses	`cat + (dog \| mouse)` `cat \| dog + (! mouse)`

Operations Manager i10.62

Develop > Command-Line Interfaces > opr-downtime Command-Line Interface

opr-downtime Command-Line Interface

You can use the opr-downtime command-line interface to retrieve, add, or delete downtimes.

Location

<OMi_HOME>/opr/bin/opr-downtime.[bat|sh]

Synopsis

opr-downtime -help | -version | -examples | <CONNECTION_INFO><downtimeRelatedOption>

Syntax for <CONNECTION_INFO>

Note If <CONNECTION_INFO> is omitted, the command is executed on the server to which you are logged on.

Option	Description
`{-rc_file \| -rcf }<file>`	Location of your credential store. Values for your username, password, java keystore location, and java keystore password can be defined here, enabling you to run commands without having to specify the values individually each time. Use the options `-list_rc`, `-set_rc`, and -`delete_rc` to work with the file. The default file is `<OMi_HOME>/.opr-cli-rc`. If this option is not specified, then commands automatically check the default file location for credentials. You must specify this option if your credential store file is in a non-default location. If this file does not exist or does not contain the correct settings, you must manually specify the credentials using the other command options.
`{-list_rc\| -lrc} [-rc_file <file>]`	Display the content of the file from which credentials are read. The file contains fields for java keystore, keystore password, username and password, and is encrypted by a hardcoded key.
`{-set_rc \| -src} <key>=<value> [-rc_file <file>]`	Configure one setting in the file from which credentials are read. Specify the setting and the new value by using a key=value pair. For example, `-set_rc password=<password string>`.
`{-delete_rc \| -drc} <setting> [-rc_file <file> }`	Delete setting from file from which credentials are read. Possible settings are username, password, jks, and jksPassword.
`{-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}`	Use certificate stored on smart card or security token for authentication. When OMi is configured to use CAC authentication, the CLI tools under `<OMi_HOME>/opr/bin/` do not directly prompt users to enter the password for the smartcard connected to the system. Instead, users must specify that a smartcard authentication is to be run, using the option `-sc` or `-smartcard`. Users attempting to run a tool without the `-smartcard` option automatically receive an error message. For more information, see Using command-line tools when client certificate enforcement is used.
`{-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. For details, see Configure Client Certificate or Smart Card Authentication.
`{-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. For details, see Configure Client Certificate or Smart Card Authentication.
`{-jksPassword\|-jp} <keystore password>`	Password for accessing the Java keystore.
`{-port\|-p} <port>`	Uses port `<port>` to connect to the target gateway server. Default: `80` (HTTP) `443` (HTTPS)
`-server <GatewayServer>`	Sets the target gateway server, using `<GatewayServer>` as the hostname or IP address to locate it. Default: FQDN of the OMi gateway server
`-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. Cannot be used in conjunction with the `-url` option.
`{-url\|-u} <url>`	Sets the target gateway server, using `<url>` as the URL to locate it. Default: `https://<OMi gateway FQDN>:80/opr‑config‑server`

Syntax for <downtimeRelatedOption>

-list | -delete <id> | -add -name <name> -category <category> -planned <true | false> -cis <CiID:ViewName[,...]> -start <DATE> -end <DATE> [-description <description> -approver <approver> -recipients <recipient[,...]> -action <actionName> -timezone <timezoneId>]

Option	Description
`-a \| -add`	Add a downtime.
`-action <actionName>`	Action of the downtime. If not specified, the default action is `REMINDER`. Available actions are: `reminder` `suppress_notifications` `enforce_on_kpi_calculation` `enforce_on_reports` `stop_monitoring`
`-ap \| -approver <approver>`	Approver of the downtime.
`-c \| -category <category>`	Category of the downtime. Available categories are: `other` `os_configuration` `app_maintenance` `app_installation` `nw_maintenance` `hw_maintenance` `hw_installation` `security`
`-cis <cis>`	CIs affected by the downtime. Format: `ciId:viewName[,...]`
`[ -description <description> ]`	Description of the downtime.
`[-delete <identifier>`	Delete the downtime specified by the `<id>`.
`[-e \| -end <date`> `]`	End date of the downtime. Format: `MM.dd.yyy HH:mm:ss`
`[-l\| -list` `<identifier>][-xml]`	List all downtimes or a single downtime specified by `<id>.` Specify the -`xml` option to return the output formatted as XML.
`[-n \| -name <name>]`	Display name of the downtime.
`[-planned <true \| false>]`	Specify whether the downtime was planned or unplanned.
`[-r \|-recipients <name>]`	Recipients for notifications of the downtime.
`[-s \| -start <date>]`	Start date and time of the downtime. Format: `MM.dd.yyy HH:mm:ss`

Send Help Center feedback