[INUG-Users] NNM probe X NNM 7.5 - Event storm problem

[Flaviano Ludovino Leoncini]

Hi Lim, thank you for your answer.

I've just opened the PMR, but could you please explain me better what the
response in you mail means?
The probe version which uses dumpevents is not still available as a GA
version, that is, it is still a beta version? And it will be probably
available as a GA version in the period between October and December?

Have you tried this new version which uses ovdumpevents? If so, does it
works fine?

Thank you.

Regards,

Flaviano.

On 9/6/07, Lim, ChenLock <ChenLock.Lim at delta.com> wrote:
>
>  Hi Flaviano,
>
>
>
> I opened a PMR with IBM as well regarding the NNM v7. Their response was
>
>
>
> "The product manager replied that the NNM7 probe which uses API
>
> communication is currently GA. It will be uploaded to Passport Advantage
>
> for download by the end of the third quarter."
>
>
>
> Open a PMR with the support if you need it sooner. Very likely you are
> running the probe that used pmd instead of ovdumpevent. I believe there are
> some issues with pmd version.
>
>
>
> Hope that helps
>
>
>
> ChenLock Lim
>
>
>  ------------------------------
>
> *From:* users-bounces at netcoolusers.org [mailto:
> users-bounces at netcoolusers.org] *On Behalf Of *Flaviano Ludovino Leoncini
> *Sent:* Wednesday, September 05, 2007 10:39 AM
> *To:* users at netcoolusers.org
> *Subject:* [INUG-Users] NNM probe X NNM 7.5 - Event storm problem
>
>
>
> Hi users,
>
> I have a problem with Netcool probe for NNM v .7 working with NNM 7.5.
> When an Event Storm happens in NNM, that is, NNM receive lots of events at
> the same time, the probe is disconnect from NNM. This has been happening
> almost once a week and seens to be related to maintenance in some router in
> this network, which causes lost of communication between NNM and the devices
> managed by it.
>
> In my file pmd.log0 (from NNM) I see this kind of message when an Event
> Storm is detected by NNM:L WARNING        *OV_EVENT:03
> 0000:0000 00000000:00000000 Aug 27 02:09:11      ovEvent.C       :4214*
>
> *     |           PM_NO_ERROR*
>
> *     |           Event Storm detected.  6000 events in 286 seconds (21.0events/sec > 20). Received 2202000 events since startup.
> *
>
> * *
>
> And in probe log file I can see the probe disconnecting, like in this file
> (it's is not the same date, but the message is the same):*
> Mon Sep  3 14:44:55 2007 Error: OVerror - Connection to trapd died.*
>
> *Mon Sep  3 14:44:55 2007 Debug: Stopping due to SIGNAL*
>
> *Mon Sep  3 14:44:55 2007 Debug: Lost connection detected - requesting SCM
> to restart probe*
>
> *Mon Sep  3 14:44:55 2007 Error: Unable to get events: General failure*
>
> *Mon Sep  3 14:44:55 2007 Information: Stopping...*
>
> *Mon Sep  3 14:44:55 2007 Information: Checking in license feature
> "nco_p_nnm7".*
>
> *Mon Sep  3 14:44:55 2007 Debug: >>>>>> Returned FLEX license (nco_p_nnm7)
> to server*
>
> *Mon Sep  3 14:44:55 2007 Debug: *** Log Header Begin ****
>
>
> I've read something in forum about a probe which uses ovdumpevents instead
> of pmd to communicate with.
>
> Questions:
> 1) Does anyone already deal with this kind of problem?
> 2) How do I know if in my scenario probe is using PMD or ovdumpevents to
> get the events? It seems to be using PMD, because the messages in pmd.logfile, but I would like to know how this - the use of pmd or ovdumpevents -
> is defined, if it is according to probe version.
> 3) Is the performance of this probe which uses ovdumpevents better than
> the old one, which uses pmd?
>
> Thank you.
>
> Regards,
>
> Flaviano Leoncini.
> --
> "Give a man a fish, and he'll eat for a day.
> Teach a man to fish, and he'll eat for a lifetime!"
>
> _______________________________________________
> Sent by the netcoolusers.org "users" mailing list
> Post: users at netcoolusers.org
> Unsubscribe: users-unsubscribe at netcoolusers.org
> Search: http://lists.netcoolusers.org/archives/users/
>
>


-- 
"Give a man a fish, and he'll eat for a day.
Teach a man to fish, and he'll eat for a lifetime!"
-------------- next part --------------
HTML attachment scrubbed and removed