RE: Enterprise trapquestion/send_v2trap API call

"Mike Ayers" <[email protected]>
Newsgroups gmane.network.net-snmp.user
Message-ID <83E753BE7B6A324ABB336245BAF1DAAC07BE4BA6@mailserver.metatv-ds.metatv.com>
> From: [email protected] 
> [mailto:[email protected]] On 
> Behalf Of McGowen, Wendy
> Sent: Wednesday, January 09, 2008 9:43 AM

> Ok, so do you mean that I shouldn't put anything that's already in
> MIB-II in our private MIB if we include MIB-II support in our product?

	I'll go one step farther and say that you should not duplicate support from any standard, available MIB in your private MIB.  This is not only due to the standardization issues Dave mentioned, but also because setting up proper management for things that seem trivial at first can be very difficult.

> When I said "the same data" I really should have said that there might
> be a few data points that would be duplicated between the 2 (like IP
> addresses).

	IPv4?  IPv6?  How to tell which one (or more) to use.  Are you sure you'll get this notoriously tricky area right?  Enable IF-MIB, and work with it, and one big headache becom,es a manageable problem.

> Would it be best to just not include any default 
> MIB support
> and only support our private MIB in that case?

	As above, I think not.  Often it is believed that putting everything in a private MIB will keep things less complicated and allow the scope to be restrained, but it really translates to a separate development effort, one in which expertise is lacking.

> I was told that most
> shops would want at least MIB-II support, and then if they want to
> peruse our data they could go to our enterprise OID. And I've 
> been told
> that it's really traps that are the most important aspect of our SNMP
> support (from our customer's perspective), so I'm not even 
> sure how our
> "private" data will be used, if at all, by the customer.

	In the end, your customers will decide what data interests them, but the scope you mention above sounds about right.

> Our GUI doesn't use SNMP - it's CIM based (not my choice). 
> We're adding
> SNMP support after-the-fact, so they want the SNMP data to 
> "mirror" what
> we're doing in CIM (and even there we defined everything under our own
> objects).

	Ah!  This is the one case where it may be acceptable to put everything in your own mib - if and only if it's a mirror, then make everything the same.

	Note that if you give the mirror to a true SNMP house, they probably won't be very happy about it.


	HTH,

Mike

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
Net-snmp-users mailing list
[email protected]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.