|
Folks,
many many thanks!
Don
and James jointly the solved the riddle of the mysterious Netegrity MIB. Indeed
the Vendor wrote a very shabby MIB as both Don and James pointed out. It dawned
on me when Don asked me to rewrite the addtrap script for the Netegrity MIB.
James question about the comparisons sealed the deal and both guys clued me in
on the discrepancy.
1.3.6.1.4.1.2552.200.300.3 .0 is
what is written in the Netegrity MIB. IT is ABSOLUTELY wrong wrong
wrong!
It should be 1.3.6.1.4.1.2552.200.300.3 . When I removed the .0 and readded
things worked perfectly. I had to actually completely cleanup my trapd.conf
file, but now things are
perfect.
Now to have a stern talk with the Netegrity
(Siteminder) folks.
You
folks rock! Many thanks once again!
J.T. Edwards
Sr.
Systems Programmer
Enterprise Systems
Management
Waste Management Incorporated
"Proud Sponsor of NASCAR"
Chairperson,
Tivoli South-Central Users Group
Office: (713)265-1294
Mobile:
(832)457-5239
When you ran mib2trap, and it produced an output script, what's in
it?
Is there an addtrap for 1.3.6.1.4.1.2552.200.300.3 , generic trap:6 specific trap:3
or not? If not, then you
are correct, the MIB and what the vendor's agent actually sends are not the
same.
But you're the one with the MIB. You'll have to tell us.
James
Shanks
Level 3 Support for Tivoli NetView for UNIX and Windows
Tivoli
Software / IBM Software Group
| 