Known issues

At the time of release, a known issue was reported that you should be aware of when running the probe.

Alarm comments logged as user ID

The userid_comment_alarm CLI command enables you to add comments to an alarm by specifying the alarm ID (NV_ALARM_ID), the user ID of the user making the comment, and the text of the comment. It is also possible to use this command without specifying the user ID, in which case the user ID specified by the CommentUserId property is added to the related entry in the probe's log file.

However, when you use the command without specifying a user ID, and the comment that you add contains more than one word, the entire comment string is logged in the probe's log file in place of the user ID. This happens regardless of the value specified by the CommentUserId property.

The following example demonstrates how the CLI successfully completes a userid_comment_alarm command where only the alarm ID and the comment string are entered:
> userid_comment_alarm 2042480408 testing purposes only
Completed userid_comment_alarm
In this case, the related entry in the probe's log file contains the comment string testing purposes only in place of the user ID.

Command line input no whitespace limitation

The resynch_filter CLI command enables you to perform partial resynchronization with the CORBA interface using the filter parameter. However, currently the command port does not allow the filter input parameter to contain any whitespaces in between characters.

The following example demonstrates how the CLI successfully completes a resynch_filter command without any whitespaces:
resynch_filter $h==3
A command containing whitespace will be unsuccessful, for example resynch_filter $h == 3.

Multibyte characters not supported in the AdditionalText field

Currently the probe does not support the proper display of multibyte characters (that is, characters encoded in UTF-8) in the AdditionalText fields.

Probe release ID not printed

On Netcool/OMNIbus 8.1 on AIX, the probe’s release ID is not printed when starting the probe using –version.

To get the probe’s version information, start the probe with DEBUG level logging and get the release ID from the log file header.