I've done it. I've figured out how to get to the temperature, fan speed, yada yada sensors on at least some Solaris boxen.
This was part of my original goal in getting into SNMP in general and net-snmp in particular. My boss said "write something so that if a fan fails on one of the Solaris boxes, my cell phones goes off". OK, it would be nice if he had text messaging on his cell phone, but that's a side issue. Give me a trap, I can do something. OK, now I can generate a trap, but I need a place to put it. My first thought, HOST-RESOURCES-MIB, just isn't going to cut it. It's just waaay outside the scope of that particular RFC/MIB. My second thought was to put it into LM-SENSORS-MIB. That MIB, though appears to be geared specifically to the lm-sensors package for linux. I am certainly not up to porting the package to Solaris. Also, lm-sensors, as it stands, does not cover three of the chips used by my methodology. My next thought was to write my own RFC. My modesty (which does not bear close examination) prevents me. So, perhaps a MIB might be in order. (Do I need an RFC for an individual MIB? Maybe I'll be famous yet.) Next problem is that the methodology used to derive the CPU temperature on one specific piece of Sun hardware is different on another piece. The net-snmp code could get really, really messy. A subsequent problem is that my code may be in violation of Sun's licensing agreement. However, it is based upon .h files found within their published operating system, so presumably the code could be published with Copyright disclaimers similar to those already inserted by Sun's contributing engineers (Hi, guys!!). This may also apply to using my code to populate Sun's MIB. So here's how I see it working so far. I create a binary that works on such-and-such hardware with the appropriate disclaimers (use at your own risk, don't sue me I don't have any money) with a published API. I stick that binary somewhere where people can find it. Use that API as hooks for net-snmp. I publish my own MIB to access the binary. We package the MIB (and the code to get at it) with net-snmp. Problems: 1. Sun may still hate it. They may claim my helper application is affecting their bottom line. 2. The Solaris net-snmp community is reliant upon me (as coder of the helper app) not to get hit by a bus/jitney/taxi/rickshaw/hovercraft. 3. I've only got a limited range of hardware at my disposal. Others may have code to contribute for other platforms but can't because I'm hogging the source to the helper app. Now what? This communication is intended for the use of the recipient to which it is addressed, and may contain confidential, personal and or privileged information. Please contact us immediately if you are not the intended recipient of this communication, and do not copy, distribute, or take action relying on it. Any communication received in error, or subsequent reply, should be deleted or destroyed. ------------------------------------------------------- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 13. Go here: http://sf.net/ppc_contest.php _______________________________________________ Net-snmp-coders mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
