I set the Netview co-relator to detect link / node up & down status. Upon
detection of either, I run a script to log the detection & page the support
engineer. No logs were written for a few days even though there's a link
failure. This has happened a number of times. Due to the way I run the
script, there'll definitely be some logs written everyday, which I get when the
co-relator behaves normally.
I suspect the co-relator doesn't behave sometimes, & I'm trying to find out
why. Any comments?
Thank you.
cheers,
Jeanie
James_Shanks@TIVOLI.COM wrote:
> How do you know that the missing traps are even sent? If you aren't doing
> anything in NetView, then it is more likely that the trap sender isn't
> sending them, or that routing problems prevent them from reaching you. I'd
> run an iptrace for port 162 udp and see if they even arrive when you are
> expecting them. If there is a trap sent log of some kind on the sender,
> I'd check that too.
>
> James Shanks
> Tivoli (NetView for UNIX) L3 Support
>
> Jeanie Cham <yccham@NCS.COM.SG> on 03/05/99 08:28:32 PM
>
> Please respond to Discussion of IBM NetView and POLYCENTER Manager on
> NetView <NV-L@UCSBVM.ucsb.edu>
>
> To: NV-L@UCSBVM.ucsb.edu
> cc: (bcc: James Shanks)
> Subject: Missing Alerts
>
> Hi,
>
> I've a major problem...I'm monitoring my network using Netview 5.1,
> Framework 3.1.1 on AIX 4.2.1 (I've just upgraded from Netview 5.0).
>
> There're days when I don't get any link down alerts even though there's
> a link failure. This'll last a few days before the alerts start coming
> in as per normal again. I don't think this is due to the upgrade as
> this has happened a number of times even before the upgrade.
>
> Can someone tell me what could have gone wrong? I'm using a E30 with
> 256MB RAM. Doing "vmstat", on average I get 50-70% idle.
>
> Thanks!
>
> cheers,
> Jeanie
|