Troubleshoot

If you encounter problems while using OpsCx for OneView, you can often solve them yourself. This topic is intended to help you.

General Checks

When investigating an issue, first verify that:

• You are not running into known issues .

• Your issue is not related to the third-party software or hardware. Otherwise, contact the corresponding vendor for assistance.

• You have the latest operating system and software application patches installed on the affected systems.

• The configuration settings for the OpsCx for OneView (values, syntax) are correct.

Log Files

OpsCx for OneView logs event and topology data and BackSync information to log files. Unexpected behavior is recorded as an entry in the log file. Information contained in the log file is useful for investigating problems.

Collector Logs

Event and topology data logs are saved to the following directory:

Windows: %OvDataDir%\log\HPBsmIntOneView_[events|topology].%d.log

Linux: /var/opt/OV/log/HPBsmIntOneView_[events|topology].%d.log

where %d is the date. Log files are added each day and kept for seven days by default.

To change location of the log files:

1. Change current directory and open the appropriate integration configuration file in a plain text editor:

   Windows:

   %OvDataDir%\conf\HPBsmIntOneView\genint\oneview_[events|topology].conf

   Linux:

   /var/opt/OV/conf/HPBsmIntOneView/genint/oneview_[events|topology].conf

2. In the genintd section, change the value of the log-file option.

3. Save your changes.

4. Restart the affected integration service as described in Restarting the Services after Configuration Changes.

Logging Severity Levels

Log entries have different severity levels. In OpsCx for OneView, the following levels are available:

Severity Level	Keyword	Meaning
3	Trace	Tracing (debugging) messages
2	Info, Warning	Information messages, warnings
1	Error, Config	Errors, current values of integration configuration options
0	Disables log output	Logging is disabled

Note: When a particular logging level is set, it causes messages with lower severity level to be recorded as well. For example, if the severity level is set to 2, information messages, warnings, errors, and configuration-related messages are logged, but tracing messages are not.

Changing Log Severity

To change the logging severity level for a particular integrated OneView entity type, perform these steps:

1. Change current directory and open the appropriate integration configuration file in a plain text editor.

2. In the genintd section, perform the following:

   a. Uncomment the line with the log-level option.

   b. In the line that contains the log-level option, replace the value placeholder inside quotes ('...') with the chosen logging severity level.

   For example, to change the logging severity level from the default level to 2, change the line from:

   //, 'log-level' : '3'

   to

   , 'log-level' : '2'

3. Save your changes.

4. Restart the affected integration service as described in Restarting the Services after Configuration Changes topic.

BackSync Logs

The OMBackSync.pl and OMBackSync_OneView.pl scripts write information to the following log file:

• Windows: %OvDataDir%\log\OMBackSync.log

• Linux: /var/opt/OV/log/OMBackSync.log

The available log severity options are: DEFAULT, OFF, ERROR, INFO, TRACE.

Normally, the log severity is set to DEFAULT and prints [SEP] and [ERROR] entries. If no errors are encountered, no output information is printed.

Changing Log Severity

To change the log severity for the OMBackSync.pl script, change the following variable:

my $verbosity = Genint::Log::DEFAULT;

After you modify the logging settings, restart the ovc service with the command ovc -restart ombacksync.

Known Issues and Workarounds

Moving CIs results in duplicated or lost relationships.

Symptom

When moving an existing CIs under OneView to a new location or under a new CI, the relationships within the RTSM might get duplicated or lost.

Action

To solve duplicated or lost relationships, the topology inside the RTSM has to be deleted and sent again. Once the topology is resent, it will be correctly displayed.

Changes made to the OneView topology are not reflected correctly in OMi.

Symptom

In the OMi web interface, unusual topology hierarchy is presented.

For example, some configuration items (CIs) might appear isolated from the rest of the collected topology, although they should not because they are related to other monitored OneView nodes.

Action

By default, the Detect deltas option is selected in the Operations Connector policy for OneView Topology. With such a configuration, only recent changes in the OneView topology are propagated to OMi. In some cases, these changes provide insufficient information resulting in incorrect representation of the topology in OMi. Perform the following steps:

1. Log on to the Operations Connector web interface.

2. Right-click the Operations Connector for OneView (02.02) - Topology Integration policy and select Edit.

3. Click the Source tab.

4. In the Source page, clear the Detect deltas option.

5. Click Save and Close to apply the change.

Related topics

Known Issues and Workarounds

Restarting the Services after Configuration Changes