×
INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Contact US

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

Nice Sentinel 4.1 Issues with connectivity to active Logger

Nice Sentinel 4.1 Issues with connectivity to active Logger

Nice Sentinel 4.1 Issues with connectivity to active Logger

(OP)
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: Sentinel Issue )

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/gettingstarted/wwhelp/w... Major

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

RE: Nice Sentinel 4.1 Issues with connectivity to active Logger

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

RE: Nice Sentinel 4.1 Issues with connectivity to active Logger

check the network card order in network advanced settings

RE: Nice Sentinel 4.1 Issues with connectivity to active Logger

(OP)
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 ===

RE: Nice Sentinel 4.1 Issues with connectivity to active Logger

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

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members! Already a Member? Login

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close