Nice Sentinel 4.1 Issues with connectivity to active Logger

[IPOpotamus]

Nice Sentinel 4.1 Issues with connectivity to active Logger

Hello tek-tippers, I am surprised because an issue that showed about two years ago with Sentinel in their first releases (and my first installation) is showing once again.

( thread911-1652082 )

The issue is somewhat easy to describe.

The Active logger has two (or more) NIC cards, all of them with a different IP address.

The Sentinel polls the Active Voip Logger pointing to the IP Adress A, but the logger (by reasons I am not sure) responds through the IP Adress B.

The Sentinel does not recognize the IP Adress B, and discard the message.

Since Sentinel does not receive response from the IP Adress A which it is expecting for, later triggers and alarm regarding that “Not all monitoring information has been collected”

Initially the Nice team set up an static route in the VOIPLOGGER to force the communication the right way, but I only worked a few days.

Nice Version: NIM 4.1.25 – Cisco Voip Active Recording
DATABASE + DATAMART SERVER
SEMIDIST NIM SERVER (APPS + IC)
ACTIVE VOIP LOGGER
SENTINEL SERVER 4.1

======= ALARM DETAILS =========


VOIPLOGGER Not all monitoring information has been collected Local Functionality 3105 17/10/2013 08:55 18/10/2013 18:25 UnAcked SENTINEL System 1006 1006 Server VOIPLOGGER.domain 10.11.36.207 Polling Job SNMP Poller:No SNMP data Primary DH - Sitio principal (ID:1)

http://SENTINEL/dopplerVUE/gettings...xt=Sentinel_standalone_41&topic=Alarm_ID_3105

Major


=== having a NICE time with NICE ===

 

[blesio]

I suggest that you go over the Sentinel Troubleshooting document which is full of good advice how to cope with such problems

 

[nice12345]

check the network card order in network advanced settings

 

[IPOpotamus]

Just to let all (the universe) know

Nice has detected this as a bug or limitation on the platform

and planned to correct it definitively (I hope it too) on the Sentinel UP 05 expected to be released by finishing April 2014.

good news... we are on April 2014

so, keep and eye open.



=== having a NICE time with NICE ===

 

[baldyca]

IPOpotamus - What I found to be a workable solution to this was to configure NIC_A and NIC_B on the loggers a little bit different. For Me - NIC_A = Capture, NIC_B = C-LAN.
NIC_A = Gateway Blank NIC_B = Gateway is Valid

KB