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 Connector10.11

Integrate > OneView

OneView

The Operations Connector for OneView (OpsCx for OneView) integrates event and topology data from OneView to an Operations Manager i (OMi) solution.

The integration provides the following functionality:

Forwarding of OneView alerts (events) and topology to OMi
Customization of forwarded events and topology
Clearing of OneView alerts from OMi, using the BackSync functionality of Operations Connector

OpsCx for OneView is a GenInt-based integration. If you installed other GenInt-based connectors, see Install topic for additional details.

Product Concepts

The OpsCx for OneView is installed on the Operations Connector system and uses a Web Service interface to collect the events and topology from the OneView system. No additional components need to be installed on the OneView system.

Event Collection and Forwarding

OneView alerts (events) are collected and processed by the event collector script. The event collector receives events from the OneView server through its Web Service interface using the HTTPS protocol.

Events are collected from the OneView system periodically, using a preset event polling interval. By default, the polling interval is set to 45 seconds. In case a poll is not executed as planned, the next poll collects all events that were newly created or changed since the last successful poll. When the collector is started for the first time, existing OneView alerts are collected and forwarded (by default, alerts from the last 120 minutes are forwarded).

Event data is mapped to the OMi conform form using a web service policy.

The policy Operations Connector for OneView (02.02) - Event Integration is used to map events to the OMi conform form. Each event is tested if it matches a rule. If it does, the first condition of the rule will map it into OMi. To ensure all events are mapped, the default rule matches all alarms.

By default, alarms are mapped to events as follows:

OneView alert severity	OMi event severity
Critical	Critical
Warning	Warning
OK	Normal
Unknown
Disabled

Topology Collection and Forwarding

Topology data is collected by the topology collector script that is run regularly (by default, every hour). The topology collector receives data from the OneView server through its Web Service interface using the HTTPS protocol and forwards it to the Operations Connector for further processing.

The policy Operations Connector for One View (02.02) - Topology Integration is used to map acquired values to configuration items (CIs) in the Run-Time Service Model (RTSM),

The following CI types are created for OpsCx for OneView 2.02 version:

rack
datacenter
enclosure
node
management processor
Integrated Lights-Out (iLO) IP address

See the following figure for an example.

The policy Operations Connector for OneView (2.02) - Topology Self Discovery retrieves topology data about the OneView integration environment itself. See the following figure for an example.

Event Closure Back Synchronization

If an OneView event is closed in OMi, the OneView server needs to be informed and should also clear the corresponding OneView alert. This is known as BackSync and uses Perl scripts (OMBackSync.pl and OMBackSync_OneView.pl) to send an HTTPS request to the connector, which clears the alert on the OneView server using the OneView web service. If this succeeds, the alarm is cleared in OneView.

For details about configuring BackSync to the OneView server, see Configuring Event Back Synchronization topic.

OneView

Product Concepts

Event Collection and Forwarding

Topology Collection and Forwarding

Event Closure Back Synchronization

Related topics