At the time of release, a number of known issues were reported that you should be aware of when running the probe.
Modifying the default Netcool/OMNIbus deduplication triggers for the Probe for Nokia NFM-P
The ObjectServer Summary field may change after receiving an AttributeValueChange event, but it should not.
To resolve this issue, run the modify_dedup_trigger.sql SQL
script provided in the probe's installation package. This script modifies
the default Netcool/OMNIbus deduplication triggers for the Probe for
Nokia NFM-P to prevent the
@Summary field from being
updated when the ObjectServer receives an AttributeValueChange event.
The script is located in the following directory:
Run the script using one of the following commands:
On UNIX and Linux operating systems use:
objectserver_name -user username -password password < path_to_file/modifyt_dedup.trigger.sql
On Windows operating systems use:
%NCHOME%\bin\redist\isql.exe -S objectserver_name -U username -P password -i path_to_file\modify_dedup_trigger.sql
objectserver_name is the name of the ObjectServer against which you want to run the SQL file.
username is the username with which you log in to the ObjectServer
password is the password associated with the username you specified.
path-to_file is the path to the SQL file.
Disabling Automatic Alarm Deletion under Alarm Settings
If the user selects Disable Automatic Alarm Deletion under Alarm Settings and changes the severity of an event to "cleared" on NFM-P client GUI then in the event list the severity of the event will be changed to indeterminate.
This is to avoid the event from being deleted by delete_clears trigger. However, if the cleared event is deleted on NFM-P client GUI then the event will be resolved and removed from event list.
Using cross-launch with Internet Explorer
The probe is unable to cross-launch using the Internet Explorer browser from the Active Event List because Internet Explorer is no longer supported by NSP 21.6. Use the Event Viewer for cross-launch instead.
Integrating the probe with Nokia NFM-P 22.6
There is a connectivity issue with Nokia NFM-P whereby the probe can miss the
SystemInfoEvent when resubscribing or reconnecting to the previous durable session.
The probe durable session that showed in the Nokia NFM-P web client messaging connection may
disappear when the probe is still connected. This issue is related to having a dot in the probe
client ID name, for example:.
Use a probe
clientId without dot: in the name:
StoreEvents: 1 Durable: 'true' PersistentJmsId : 'netcoolcert@hostname' JmsFilter : 'ALA_clientId in (\'netcoolcert@hostname\', \'\') and ALA_category not in (\'STATISTICS\', \'ACCOUNTING\')'