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 > Icinga > Troubleshoot > Troubleshooting Scenarios

Troubleshooting Scenarios

Events and Topology not coming into OMi

Symptom:

After deploying management template, the event and topology is not received into OMi. This may be due to the following issues:

Policy deployment not complete to OpsCx system
Instrumentation Folder is empty OR HA policies do not get deployed in Operations Connector Host
Error executing HTTP request
bsmczedo process aborts

Perform the steps mentioned below for each of these symptoms. Also, see the FAQ section for more details.

Policy deployment not complete to OpsCx system

Symptom:

After deploying management template, the Icinga integration services are not running on the OpsCx system.

Action:

Perform the following steps:

Log on to OpsCx system.
Run the following command to restart the services on the respective operating system:

For Linux:/opt/OV/bin/ovc -restart

For Windows: ovc -restart
Run the following command to verify if all the policies are listed and are enabled:

For Linux: /opt/OV/bin/ovpolicy -list

For Windows:ovpolicy -list

Instrumentation Folder is empty OR HA policies do not get deployed in Operations Connector Host

Symptom:

The instrumentation folder will be empty in the Operations Connector System.
On running ovc command, the bsmczedo or any icinga service does not appear.
On running ovpolicy, the HA policies does not appear.

This is because the deployment was unsuccessful even though success message appears during deployment.

Action:

The Operations Connector Host should get created as Windows/ Unix CI type in OMi. Follow these steps:

From the Operations Connector System, restart all the ovc services using the command ovc -restart.
Log on to OMi console.
Go to Administration > Monitoring > Assignments and Tuning.
Delete the existing deployed Icinga Management Template.
Re-deploy Icinga Management Template. For steps, see Deploy Management Templates.
Once the deployment is complete, check in Administration > Monitoring > Assignments and Tuning. Also, check the policies deployed in OpsCx System. The HA policies and service should be present and running.

Error executing HTTP request

Symptom:

This error is due to using wrong Icinga API credentials while deploying management template. Following are the error messages for each of the invalid credentials:

Invalid Hostname - java.net.UnknownHostException:
Invalid Credentials for REST API - Unexpected response status: HTTP/1.1 401 Unauthorized
Invalid port configured for Icinga REST API Communication - Error while waiting for data:

Action:

While deploying the Management Template, make sure you type the correct credentials and validate the port number.

bsmczedo process aborts

Symptom:

After the Management Template is deployed the bsmczedo process aborts

Action:

Make sure to apply the hotfix available for QCCR8D95037 on the OpsCx system. Contact Support to get the hotfix.

Backward synchronization does not work in non-root or non-Local System account

Action:

Make sure to complete the Event backward synchronization configuration as a root user before switching to non-root user. For Event backward synchronization steps, see Installing the Event Backward Synchronization Script.
Operations Agent should be configured to run under non-root or non-Local System account. For more information to switch Operations Agent to non-root user, see the Operations Agent Documentation.
Make sure to complete the required changes on the OMi server to support communication to a non- root user configured Operations Agent system.
The port used for Operations Agent (to run under non-root or non-Local System account) in OpsCx system should also be configured in the OMi server. Perform the following steps:
1. Run the command ovconfchg –ovrg server –edit.
2. Add the following line to the file:
  
  [bbc.cb.ports]
  
  PORTS=<FQDN>:<PORT>
  
  where,
  
  FQDN - the fully qualified domain name of the OpsCx host.
  
  PORT - port used for Operations Agent (to run under non-root or non-Local System account) in OpsCx system.
Restart the OMi services.

FAQ

Q1. How to make sure Events or Topology policies are created from OMi?

On successful deployment of the Management Template, the Icinga Events and Topology policies should be created.

Verify by performing these steps:

Log on to the OMi console.
Go to Administration > Monitoring > Assignment & tuning.
From Select a view drop-down box, click Operations Connectors. The left pane with the list of OpsCx system(s) appears.
Click on the OpsCx system. The Assigned Item lists the OpsConnector for Icinga Management Template for the selected system.

Q2. How to make sure Events or Topology policies are created from OpsCx system?

The Icinga Events and Topology policies are created on the successful deployment of the Management Template.

Validate from the OpsCx system. Perform the following steps:

Log on to the OpsCx system.
Run the following command on the respective operating system:

For Linux:/opt/OV/bin/ovc

For Windows:ovc

The icingae, icingat,and bsmczedo services should be listed and in running state.
Run the following command on the respective operating system:

For Linux:/opt/OV/bin/ovpolicy -list

For Windows:ovpolicy -list

The list of policies with enabled status as shown in the following image appears.

Before Contacting Software Support

If you cannot solve your issue, report it. Before contacting Software Support, ensure that:

You have verified your problem is not described in this topic. See Troubleshooting Scenarios topic.
You have collected relevant data that might be required to send to Software Support: a description of your problem, characteristics of your environment, related entries logged in the operating system event log or in the OpsCx for Icinga log files.

Software Support personnel will then provide you with further instructions. Among other things, you may be asked to change the OpsCx for Icinga logging severity level, to repeat or perform particular operations in your OpsCx for Icinga environment, and to collect specific data from your system and send them to the respective service provider.

To contact Software Support, see the web site at https://softwaresupport.softwaregrp.com.

Troubleshooting Scenarios

FAQ

Before Contacting Software Support

Related topics