Jane,

Apparently it works on NT but was never completely implemented on Unix. I
tried to get support to work on it a while back but they didn't want to see
it as a problem as the function never existed on Unix: so it's not a bug
but a enhancement that is needed. They even told me that it would be done
in 7.1.3 (I was at 7.1.2 at that time) but the feature didn't make it in
7.1.3.....
Let's hope that the next version will "fix" it.

Salutations, / Regards,

Francois Le Hir
Network Projects & Consulting Services
IBM Global Services
Phone: (514) 205 6695

Date: Mon, 06 Jan 2003 13:08:26 +0000
To: Hendrik Zahn <hendrik.zahn AT de.ibm DOT com>,
        NetView mailing list <nv-l AT lists.tivoli DOT com>
From: Jane Curry <jane.curry AT skills-1st.co DOT uk>
Subject: Re: [nv-l] nvsniffer on 7.1.3
Message-ID: <3E197FCA.4080004 AT skills-1st.co DOT uk>

Thanks Hendrik - is this the way it always worked on Unix?????
I don't really see much point in the SmartSet if it doesn't reflect the
current status - why else would you supply the "-r" parameter to run
nvsniffer repeatedly if not to update the status of your SmartSet?

I can see from the ovobjprint that there is a field for Service Status
in the special object representing the service smartset - surely that's
the field that would be useful to reflect in a SmartSet?

Any other takers on this?
Cheers,
Jane

Hendrik Zahn wrote:

>Hi Jane,
>this is the current design. The status of the service (e.g. DNS) isn't
>reflected via
>the object-db field (e.g. isDNS) and therefore not via smartset.
>nvsniffer discovers the service for a node if the service is up. The field
>is set to TRUE.
>This indicates only, that the node has/had this service configured. In
>addition a special
>object is created for this node and service in object-db (to trigger the
up
>or down status).
>The special object looks like this:
>
>      Selection Name     "<hostname>:<service_smartset_name"
>      Service Status      Normal(2)
>      Down Time           0
>      TopM Node ID        <ObjectID_of_node>
>
>The only visible thing when a status change happens for this service is a
>trap.
>Only if the service was down for 7 days (or similar) the the field gets
>deleted from node
>and the node disappears from smartset.
>
>MfG./ Best regards
>Hendrik Zahn (L2 EMEA Tivoli NetView Support)
>
>
>Jane Curry <jane.curry AT skills-1st.co DOT uk> on 06.01.2003 13:32:31
>
>To:    NetView mailing list <nv-l AT lists.tivoli DOT com>
>cc:
>Subject:    [nv-l] nvsniffer on 7.1.3
>
>
>
>NetView 7.1.3 on AIX 4.3.3 ML10.
>Using nvsniffer with a customised configuration file and the verbose
>option shows that nvsniffer is testing the right nodes for the right
>services and getting correct answers.  However, the object database
>field never seems to change to FALSE if I take a service down so the
>SmartSets are not updated on subsequent runs of nvsniffer if the status
>of a service has changed  (also tried explicitly using the -s option).
>
>Does anyone else see this before I report to Support?
>Cheers,
>Jane
>
>--
>Tivoli Certified Consultant & Instructor
>Skills 1st Limited, 2 Cedar Chase, Taplow, Bucks, SL6 0EU, UK
>Tel: +44 (0)1628 782565
>Copyright (c) 2003 Jane Curry <jane.curry AT skills-1st.co DOT uk>.  All rights
>reserved.