On 09/01/2008, McGowen, Wendy <[EMAIL PROTECTED]> wrote: > 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'd put it slightly differently than that. If you want your product to report certain items of information, and there's a standard MIB that covers this information, then you should use these standard MIB objects to report that data, rather than defining new (private) duplicates. > 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). Would it be best to just not include any default MIB support > and only support our private MIB in that case? No. If anything, it's probably better to report the same information twice (once using the standard MIB objects, and once using your private ones). That way a network administrator can run the expected query and get back the information they expect. Remember that the hard part of implementing a MIB module is usually getting hold of the data to report - fitting this into a MIB structure is relatively straightforward by comparison. > 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. Yes - that's the right approach. If it seems to make sense to duplicate certain standard objects within your own MIB, then so be it. But that should be in *addition* to the expected representation, not instead of it. > 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. Never underestimate the ingenuity of the wider user community. Believe me - I've been involved with this project for longer than I care to remember, and I'm always being surprised at the wierd and wonderful questions that come up on these lists! (Well, perhaps less of the wonderful, but definitely wierd....) > When I post my MIB for review, should I just put the whole thing in the > body of the email and title it "MIB for review"?? I don't want to clog > up the mailing list. Probably best to post it as an attachment (as a simple ASCII text file) Note that I may not be active much over the next few days. I've got four days solid of chamber music (Mozart) to survive first.... Dave ------------------------------------------------------------------------- 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 Net-snmp-users@lists.sourceforge.net Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users
