Known issues with the Probe for Nokia Network Services Platform

NSP-PACKET-ALL topic not supported

The current rules file used in certification supports the NSP-FAULT topic, but it does not properly support the NSP-PACKET-ALL topic.

Probe behavior regarding the configurable connection retry interval

Currently the RetryInterval property is used for both failover and disconnection/reconnection, thus it is serving two different uses and you will need to adjust its setting accordingly.

During normal disconnection and reconnection, you might want the probe to reconnect in a shorter interval to avoid event loss. But during failover, the probe might require to wait longer for reconnection due to the waiting buffer before the NSP Server has successfully failed over.

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.

Alarms from Nokia NSP integration showing timestamps incorrectly

This is due to Netcool interpreting timestamps as seconds while NSP sends them as milliseconds.

This issue will be fixed in the Probe for Message Bus version 21.

Workaround

Make the following changes in the $OMNIHOME/probes/<arch>/message_bus_nokia_nfmp.rules file:

# Find below lines and modify them to
@FirstOccurrence = real($firstTimeDetected)/1000
@LastOccurrence = real($lastTimeDetected)/1000

# Find below lines and modify them to
@FirstOccurrence = real($(nsp-fault:alarm-create.firstTimeDetected))/1000
@LastOccurrence = real($(nsp-fault:alarm-create.lastTimeDetected))/1000

Kafka connection requires TLS host verification

By default, the Kafka connection requires TLS host verification which means the certificate created on the Nokia SDN host must match the host IP address or hostname. If in the environment the certificate does not match with the IP or hostname, the probe write the following connection exception to the error log:

Error: E-JPR-000-000: [KafkaConsumerRunnable] Exception when kafka consumer is running: org.apache.kafka.common.errors.SslAuthenticationException: SSL handshake failed

Workaround

If you want to disable the TLS host verification on Kafka, configure the following lines in $OMNIHOME/java/conf/nokiaNspKafkaClient.properties:

## Uncomment below lines if want to disable TLS host verification
ssl.endpoint.identification.algorithm=

Alarm details truncated

Alarms from Nokia NSP the additionalText that displayed in the Event Viewer's Details tab will be truncated to 256 char. You can enlarge the field size of alerts.details table to 1024 or 2048 char.

The probe fails to record an error

If the probe receives an HTTP response of 200 but 0 rows of alarms during the get active alarm request, it will not treat this as an error and will proceed to the Kafka notification pull. The probe might miss the active alarm resynchronization in this use case. This may happen after a failover if the REST API component is available for requests before alarm data is ready, and will be dependent on the timing of the request.

Workaround

You should use persistent subscriptions. In this case, the probe can resubscribe to its previous persistent subscription. There will be no event lost or missed notification in this scenario, provided the subscription has not expired (this applies to all disconnect scenarios). However, you can also execute a dynamic resynchronization through the nco_http command interface in probe if required.

NSP probe pagination issue and best practice

If pagination is enabled during resynchronization, the probe processes partial events if NSP takes more than five seconds to return all events. The following entry will be displayed in probe debug log:

2023-08-22T12:34:41: Debug: D-JPR-000-000: Pagination Latch for Batch #1 timed out.

To disable pagination, you must set enablePagination to false in either nokiaNspRestMultiChannelHttpTransport.json, nokiaNspRestMultiChannelHttpTransportFailover.json or nokiaNspRestMultiChannelHttpTransportPersistent.json depending on the setting of httpConnectionPropertiesFile in nokiaNspKafkaTransport.properties.

Best Practice

To enable JSON stream support, see Enabling JSON stream support.

Probe fails to reuse persistent subscription ID if the response from NSP is more than 60 seconds

The probe depends on the responseTimeout setting to determine the amount of time to wait for a subscription response. The default is 60 seconds. If the NSP server takes more than the responseTimeout to reply to the probe, the probe sends a request to recreate a new subscription ID. As a consequence, the probe will miss the events that already exist in the old subscription.

Resolution

If the network response is slow, set the responseTimeout to a value greater than 60.