This is a discussion on how do I determine which device is being accessed?? within the SNMP Coders forums, part of the Networking and Network Related category; This is a multi-part message in MIME format. --===============1781861640== Content-Type: multipart/alternative; boundary="----=_NextPart_000_000B_01C8579D.7D682B80" This ...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
This is a multi-part message in MIME format.
--===============1781861640== Content-Type: multipart/alternative; boundary="----=_NextPart_000_000B_01C8579D.7D682B80" This is a multi-part message in MIME format. ------=_NextPart_000_000B_01C8579D.7D682B80 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I'm trying to write a module for net-snmp, for our system. A typical = system will have between two and 16 cards in it, with about 15 = parameters per card. I got mib2c to generate a template file for me, and am starting to = customize it for our requirements. However, I have at least three = immediate problems: 1. The init function generated netsnmp_register_scalar() calls for the = first dozen fields in my mib, but stopped at the DevTblEntry which defines all my actual cards in the system. Do I = have to call something else to register those structs?? 2. in the init function, how do I tell it about multiple devices?? 3. When my individual handler is called, how do I know which device the = request is for?? And my underlying question is: Am I supposed to be able to figure out the answers to these questions by = looking at the tutorials at net-snmp.org?? I'm completely lost in the data there. Even the "Writing a MIB Module" = tutorial doesn't discuss any of these issues, as far as I can see; it = assumes that the writer has static data which is defined in the snmp = module, which will *never* be the case, at least in our situation. I = could use a tutorial on using the net-snmp tutorials!! Can anyone help me here?? I would be immensely grateful!! Dan Miller ------=_NextPart_000_000B_01C8579D.7D682B80 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META http-equiv=3DContent-Type content=3D"text/html; = charset=3Diso-8859-1"> <META content=3D"MSHTML 6.00.6000.16414" name=3DGENERATOR> <STYLE></STYLE> </HEAD> <BODY bgColor=3D#b3a780> <DIV>I'm trying to write a module for net-snmp, for our system. A = typical=20 system will have between two and 16 cards in it, with about 15 = parameters per=20 card.</DIV> <DIV> </DIV> <DIV>I got mib2c to generate a template file for me, and am starting to=20 customize it for our requirements. However, I have at least three=20 immediate problems:</DIV> <DIV> </DIV> <DIV>1. The init function generated netsnmp_register_scalar() calls for = the=20 first dozen fields in my mib, but stopped at the</DIV> <DIV> DevTblEntry which defines all my actual cards in = the=20 system. Do I have to call something else to register those = structs??</DIV> <DIV>2. in the init function, how do I tell it about multiple = devices??</DIV> <DIV>3. When my individual handler is called, how do I know which device = the=20 request is for??</DIV> <DIV> </DIV> <DIV>And my underlying question is:</DIV> <DIV>Am I supposed to be able to figure out the answers to these = questions by=20 looking at the tutorials at net-snmp.org??</DIV> <DIV>I'm completely lost in the data there. Even the "Writing a = MIB=20 Module" tutorial doesn't discuss any of these issues, as far as I can = see; it=20 assumes that the writer has static data which is defined in the snmp = module,=20 which will *never* be the case, at least in our situation. I could = use a=20 tutorial on using the net-snmp tutorials!!</DIV> <DIV> </DIV> <DIV>Can anyone help me here?? I would be immensely = grateful!!</DIV> <DIV> </DIV> <DIV>Dan Miller</DIV></BODY></HTML> ------=_NextPart_000_000B_01C8579D.7D682B80-- --===============1781861640== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline ------------------------------------------------------------------------- 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/ --===============1781861640== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Net-snmp-coders mailing list Net-snmp-coders@lists.sourceforge.net https://lists.sourceforge.net/lists/...et-snmp-coders --===============1781861640==-- |