James,
We migrated from Netview V4.1.2 to V5.1.1 in October. At the time we were
using the external adapter to forward events to TEC. We use the TEC
rulebase to do the logic to create trouble tickets, pages, etc. We found
out with V5.1.1 that every class being forwarded to TEC was now called
Nvserverd_event. Therefore we changed in xnmtrap panels the TEC event class
names to match all the old names we were using, therefore our TEC rules
would still work. Yes, I had to add all the new Nvserverd_event slot
definitions to my baroc files for the event classes such as Link_Down,
Link_Up, OV_IF_Down, Link_Down_Cisco, etc...
It appears the answer to my problem may be in the maintenance V5.1.2
release.
I will take that under consideration to solve this little issue.
Appreciate your help.
John Mull
Hershey Foods
What TEC class are you using for this and what level of NetView code are you
trying this on?
Support to allow you to add variables to the default Nvserverd_event class
was
not provided until 5.1.2.
If you don't have 5.1.2, then you must (a) define your own class for the TEC
event class, and (b) supply a mapping for all the variables you want to
include.
If you do have 5.1.2, then just put Nvserverd_event in the class window
using
xnmtrap, and it should provide all the standard defaults, plus what you
added in
the slot mapping section.
I think the PRINTF function was fixed in 5.1.1 as well.
James Shanks
Tivoli (NetView for UNIX) L3 Support
|