On 03/03/2008, Andrew Hood <[EMAIL PROTECTED]> wrote:
> > .... from Andre's description I
> > think he is after something like CISCO-SYSLOG-MIB::clogMessageGenerated
> > but that rises the question of generaton of those when he isn't Cisco -
> > is that bad etiquette, plain wrong or acceptable?
> At a minimum, bad etiquite. I helped arrange an enterprise number of our
> own so we wouldn't get into such issues. The better behaved people use
> subtrees under that.
[ Use of enterprise OIDs deleted]
> So what happens if CheckPoint decide to generate this specific trap? Or
> we ever run trap generating software from Deutscher Wetterdienst?
It's certainly unacceptable to define MIBs within an enterprise subtree
administered by someone else. But that's not what's being suggested
here.
Cisco have defined a MIB "...to describe and store the system
messages generated by the IOS and any other
OS which supports syslogs."
If this MIB matches the requirements of another organisation,
I don't personally see a problem with implementing that particular
MIB - either in terms of the management objects for GET/SET
requests, or the notifications defined within it.
Andre would have to abide by the specification outlined by the
MIB, of course - he couldn't amend the semantics of the trap
(or any other object) without re-naming things to use different
OIDs. But if the agent reports syslog information using this
particular trap, with the correct contents - does it really matter
whether the originating box has the appropriate label on it or not?
Dave
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
