nv-l
[Top] [All Lists]

RESOLVED: [nv-l] NetView 7.1.2 TEC Integration

To: "'nv-l@lists.tivoli.com'" <nv-l@lists.tivoli.com>
Subject: RESOLVED: [nv-l] NetView 7.1.2 TEC Integration
From: "Key, Chris" <Chris.Key@hq.doe.gov>
Date: Fri, 19 Jul 2002 16:30:12 -0400
DOPE!!!
Needed to recycle the processes after running tecits_upgrade.
-----Original Message-----
From: Key, Chris [mailto:Chris.Key@hq.doe.gov]
Sent: Friday, July 19, 2002 12:37 PM
To: 'nv-l@lists.tivoli.com'
Subject: [nv-l] NetView 7.1.2 TEC Integration


I am running NetView 7.1.2 and TEC 3.7.1 with FP2.
I have imported the new netview baroc and rls files into the TEC rulebase, compiled, and reloaded.

I also have run the tecits_upgrade script on the NetView server to forward the traps to TEC as events.
All Status type events are forwarding with the correct TEC_ITS* classes.
This morning I implemented a threshold to collect CPU utilization on one of our routers using the predefined "avgBusy5" threshold that comes with NetView.

To verify I would recieve the event in TEC, I set the threshold very low. I saw the trap in the trapd.log, but it never showed up in TEC.

I did a wtdumprl to see if an attempt was made, and for some reason the event was sent with the old "OV_DataCollectThresh" class instead of the new "TEC_ITS_SNMPCOLLECT_THRESHOLD" class. So, I looked at the trap configuration under the Event Configuration menu and it was set to use the new

"TEC_ITS_SNMPCOLLECT_THRESHOLD".

Has anyone else experienced this? Basically all events seem to be sent in the new TEC_ITS class except the SNMP threshold events, even though the Event Configuration for trap 58720263 "IBM_NVDCOL_EV" is configured to do so.

Chris

<Prev in Thread] Current Thread [Next in Thread>
  • RESOLVED: [nv-l] NetView 7.1.2 TEC Integration, Key, Chris <=

Archive operated by Skills 1st Ltd

See also: The NetView Web