Re: Implementing IPMI firmware (agent) on Linux
Hi all... I put out a message asking for help on this topic back in March, but did not get responses. If you're interested in this topic and have questions, or if you have suggestions at this later stage, please feel free to contact me. I've been successful at creating a partial implementation of IPMI as a software service to do the highest priority queries. All the best... Alan On Mar 19, 2010, at 8:22 AM, Alan Carwile wrote: I'm looking for help/suggestions regarding development of an IPMI service on Linux... If you have experience or interest in IPMI, please read-on... I'm developing IPMI software/firmware for a managed device - essentially developing an IPMI agent. It will consist of a linux daemon listening on UDP port 623, decoding IPMI requests, and calling access routines to process and respond to those requests. Sounds a lot like an SNMP agent, right? My guess is that some people on this list have worked on IPMI as well as SNMP. I've found that there are several open source projects (OpenIPMI, ipmitool, CoreIPMI, FreeIpmi) that could be used as starting points, but I think most of these are focused more on the manager side instead of agent side. There is also dcmitool, an app built over ipmitool, that implements commands (requests) for DCMI (Data Center Manageability Interface). DCMI is effectively a slice out of IPMI (Intelligent Platform Management Interface). IPMI is rather large, and different vendors implement it differently. DCMI takes a more focused look and leans itself better to more consistent implementation, from what I understand. From this link, you can get to DCMI and IPMI specifications, and the dcmitool software: http://www.intel.com/go/dcmi I'm not talking about using IPMI to answer queries that come into an SNMP agent. I'm talking about implementing the IPMI service that responds to IPMI commands like get chassis status. Other tasks of the IPMI agent are to provide sensor information about the managed device and to optionally send traps when sensor values cross thresholds. IPMI has about a dozen cipher sets to provide authentication, integrity, and encryption, and IPMI has multiple user privilege levels (user, operator, supervisor). I need to provide these services (plus a small event history) but would like to leverage the work of others and focus on the actual data about the managed device (filling in access routines, so to speak). I believe there should be a lot of parallels between IPMI agent development and SNMP agent development. I have experience adding net-snmp as an agent on Linux and Windows, and using net-snmp from a management application. If you have experience with IPMI implementation on a managed device, please contact me directly and/or post back to the list with any suggestions you have on the above or other topics. I'll summarize back to the list if appropriate... Thanks! Alan Carwile -- ___ Net-snmp-coders mailing list Net-snmp-coders@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
Net::SNMP availability on CPAN
All, I see that the last uploaded version of the perl module, Net::SNMP, to CPAN was made in 2007. I take it that CPAN isn't supported anymore. Is that true? For those of us that have our build processes centered on CPAN, this makes it difficult with regards to the Net::SNMP package. So could the latest version be put on CPAN? Thanks much for any help.. Ed -- ___ Net-snmp-coders mailing list Net-snmp-coders@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
ifSpeed set
I have been trying to find a way to set the value of IF-MIB::ifSpeed.6, which is a legitimate interface. I can query the interface and get the value, but I cannot set it. I am setting it only for another program to fetch it later. It serves no other purpose than a place to hold the information that the reading program desires. Here are the get and set executions. I just need to be able to set it snmpget -v 1 -c public localhost ifSpeed.6 IF-MIB::ifSpeed.6 = Gauge32: 1000 snmpset -v 1 -c writtablecs localhost ifSpeed.6 u 10 Error in packet. Reason: (noSuchName) There is no such variable name in this MIB. Failed object: IF-MIB::ifSpeed.6 Any help on this would be great. Also, my email address changed last week judith.wal...@jdsu.commailto:judith.wal...@jdsu.com will work and judiwal...@comcast.netmailto:judiwal...@comcast.net will work also. -- ___ Net-snmp-coders mailing list Net-snmp-coders@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
Re: ifSpeed set
On Thu, 2010-05-13 at 13:01 -0700, Judith Walker wrote: I have been trying to find a way to set the value of IF-MIB::ifSpeed.6, which is a legitimate interface. I can query the interface and get the value, but I cannot set it. I am setting it only for another program to fetch it later. It serves no other purpose than a place to hold the information that the reading program desires. Given that IF-MIB::ifSpeed is a read-only interface I have to say that this is as expected. ifSpeed OBJECT-TYPE SYNTAX Gauge32 MAX-ACCESS read-only ... /MF -- ___ Net-snmp-coders mailing list Net-snmp-coders@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
Re: ifSpeed set
On 13 May 2010 21:01, Judith Walker judith.wal...@jdsu.com wrote: I have been trying to find a way to set the value of IF-MIB::ifSpeed.6 As Magnus has said, the IP-MIB::ifSpeed object is defined as read-only, so you cannot use snmpset on it. However, it is possible to configure the type and speed of a given interface via the snmpd.conf file. See the 'interface' token in snmpd.conf(5). Dave PS: Please send queries to the mailing list, not to individual contributors. Thanks -- ___ Net-snmp-coders mailing list Net-snmp-coders@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
Re: Net::SNMP availability on CPAN
On 14 May 2010 04:46, Edward Peschko e...@yahoo-inc.com wrote: I see that the last uploaded version of the perl module, Net::SNMP, to CPAN was made in 2007. I take it that CPAN isn’t supported anymore. We have no idea. From the project FAQ: I've got a problem with the Net-SNMP module. Can you help? -- Sorry, despite the similar-sounding name, the Net-SNMP (or Net::SNMP) module is nothing to do with this package, or the NetSNMP modules. Net::SNMP is a pure-perl implementation of SNMP support, developed by David Town. The developers of the (C-based) Net-SNMP suite do not have any significant experience in using this particular module, and you'll probably be better off asking for help via CPAN or some other perl-related forum. In fact, the most recent version of David's module (v6.0.0) was uploaded in September last year. If you mean the SNMP (and NetSNMP) modules, then yes - those do date from 2007. Is that true? For those of us that have our build processes centered on CPAN, this makes it difficult with regards to the Net::SNMP package. The problem we've always had with using CPAN is ensuring a match between the version of the perl modules and the local libraries. Because the two are fairly tightly linked, there can be problems when people installing code from CPAN that doesn't match the C libraries which they are using. Hence it felt simpler to encourage people to install the perl modules from the same source tree as the C libraries (either directly, or via vendor-supplied packages). That way they should get the correct version for their environment. So could the latest version be put on CPAN? We've got an admin meeting later today, so I've put this on the agenda. Dave -- ___ Net-snmp-coders mailing list Net-snmp-coders@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
Re: Can we update the table value in subaget?
On Fri, 14 May 2010 10:19:58 +0530 Prakash wrote: P Any reference please No, not really. A sub-agent is just like any other program. Neither AgentX nor SNMP care about where the data for an object comes from, be it a file, a calculation, shared memory, etc. -- ___ Net-snmp-coders mailing list Net-snmp-coders@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
snmpTranslate
Hello,
I'm using snmptranslate utility for converting MIB files into
textual description specially for TRAPS. But using the snmpTranslate utility
netsnmp version 5.5 it is unable to convert TRAP-TYPE data types. It is
successfully able to convert the NOTIFICATION-TYPE.
Instead for TRAP-TYPE it is converting it to OBJECT-TYPE.
E.g:
MIB:
MUSE-DEFAULT-NBI DEFINITIONS ::= BEGIN
IMPORTS
OBJECT-TYPE FROM RFC1155-SMI
TRAP-TYPE FROM RFC-1215
enterprises, NetworkAddress,IpAddress, Counter,
Gauge, TimeTicks
FROM RFC1155-SMI;
-- In order for this trap to work correctly, the snmp trap
forwarder
-- must be used with the following gate writer configuration:
--
-- START WRITER SNMP_WRITER
-- (
-- TYPE = SNMP,
-- REVISION = 1,
-- GATEWAY = 'myManager',
-- MAP = SNMP_MAP
-- OID = '1.3.6.1.4.1.1279.20'
-- );
microMuse OBJECT IDENTIFIER ::= { enterprises 1279 }
museSnmpTrapForwarder OBJECT IDENTIFIER ::= { microMuse 20 }
museDefaultTrap TRAP-TYPE
ENTERPRISE museSnmpTrapForwarder
--VARIABLES { museIdentifier, museSerial,
museNode, museNodeAlias, museManager, museAgent,
museAlertGroup,museAlertKey,museSeverity,museSummary,
museStateChange,museFirstOccurrence,museLastOccurrence,museInternalLast,musePoll,museType,museTally,museClass,museGrade,museLocation,museOwnerUID,museOwnerGID,
museAcknowledged,museFlash,museServerName,museServerSerial }
DESCRIPTION
All information regarding an event which
exists in the
OMNIbus alerts.status table.
--REFERENCE
--http://support.micromuse.com/documentation/supplementals/gateways/SNMP.pdf;
::= 1
END
After executing snmptranslate it gets converted as :
MUSE-DEFAULT-NBI::microMuse
microMuse OBJECT-TYPE
-- FROM MUSE-DEFAULT-NBI
::= { iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) 1279 }
MUSE-DEFAULT-NBI::museSnmpTrapForwarder
museSnmpTrapForwarder OBJECT-TYPE
-- FROM MUSE-DEFAULT-NBI
::= { iso(1) org(3) dod(6) internet(1) private(4) enterprises(1)
microMuse(1279) 20 }
MUSE-DEFAULT-NBI::museSnmpTrapForwarder#
museSnmpTrapForwarder# TRAP-TYPE
-- FROM MUSE-DEFAULT-NBI
::= { iso(1) org(3) dod(6) internet(1) private(4) enterprises(1)
microMuse(1279) museSnmpTrapForwarder(20) 0 }
MUSE-DEFAULT-NBI::museDefaultTrap
museDefaultTrap OBJECT-TYPE
-- FROM MUSE-DEFAULT-NBI
DESCRIPTION All information regarding an event which exists in the
OMNIbus alerts.status table.
::= { iso(1) org(3) dod(6) internet(1) private(4) enterprises(1)
microMuse(1279) museSnmpTrapForwarder(20) museSnmpTrapForwarder#(0) 1 }
So kindly let me know is there any way I can use snmptranslate for V1 traps?
Regards,
Nitin Rathod
--
___
Net-snmp-coders mailing list
Net-snmp-coders@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
Re: snmpTranslate
Please let me know the snmptranslate options used by you.
Regards,
Manjit
Rathod, Nitin wrote:
Hello,
I’m using snmptranslate utility for converting MIB files into textual
description specially for TRAPS. But using the snmpTranslate utility
netsnmp version 5.5 it is unable to convert TRAP-TYPE data types. It
is successfully able to convert the NOTIFICATION-TYPE.
Instead for TRAP-TYPE it is converting it to OBJECT-TYPE.
E.g:
MIB:
/MUSE-DEFAULT-NBI DEFINITIONS ::= BEGIN/
/ IMPORTS/
/ OBJECT-TYPE FROM RFC1155-SMI/
/ TRAP-TYPE FROM RFC-1215/
/ enterprises, NetworkAddress,IpAddress, Counter, Gauge, TimeTicks /
/ FROM RFC1155-SMI;/
/ -- In order for this trap to work correctly, the snmp trap forwarder/
/ -- must be used with the following gate writer configuration:/
/ --/
/ -- START WRITER SNMP_WRITER/
/ -- (/
/ -- TYPE = SNMP,/
/ -- REVISION = 1,/
/ -- GATEWAY = 'myManager',/
/ -- MAP = SNMP_MAP/
/ -- OID = '1.3.6.1.4.1.1279.20'/
/ -- );/
/ microMuse OBJECT IDENTIFIER ::= { enterprises 1279 }/
/ museSnmpTrapForwarder OBJECT IDENTIFIER ::= { microMuse 20 }/
/ /
/ museDefaultTrap TRAP-TYPE/
/ ENTERPRISE museSnmpTrapForwarder/
/ --VARIABLES { museIdentifier, museSerial, museNode, museNodeAlias,
museManager, museAgent,
museAlertGroup,museAlertKey,museSeverity,museSummary,
museStateChange,museFirstOccurrence,museLastOccurrence,museInternalLast,musePoll,museType,museTally,museClass,museGrade,museLocation,museOwnerUID,museOwnerGID,
museAcknowledged,museFlash,museServerName,museServerSerial }/
/ DESCRIPTION/
/ All information regarding an event which exists in the /
/ OMNIbus alerts.status table./
/ --REFERENCE/
/
--http://support.micromuse.com/documentation/supplementals/gateways/SNMP.pdf/
/ ::= 1/
/ /
/ /
/END/
After executing snmptranslate it gets converted as :
/MUSE-DEFAULT-NBI::microMuse/
/microMuse OBJECT-TYPE/
/ -- FROM MUSE-DEFAULT-NBI/
/::= { iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) 1279 }/
/MUSE-DEFAULT-NBI::museSnmpTrapForwarder/
/museSnmpTrapForwarder OBJECT-TYPE/
/ -- FROM MUSE-DEFAULT-NBI/
/::= { iso(1) org(3) dod(6) internet(1) private(4) enterprises(1)
microMuse(1279) 20 }/
/MUSE-DEFAULT-NBI::museSnmpTrapForwarder#/
/museSnmpTrapForwarder# TRAP-TYPE/
/ -- FROM MUSE-DEFAULT-NBI/
/::= { iso(1) org(3) dod(6) internet(1) private(4) enterprises(1)
microMuse(1279) museSnmpTrapForwarder(20) 0 }/
/MUSE-DEFAULT-NBI::museDefaultTrap/
*/museDefaultTrap OBJECT-TYPE/*
/ -- FROM MUSE-DEFAULT-NBI/
/ DESCRIPTION All information regarding an event which exists in the /
/ OMNIbus alerts.status table./
/::= { iso(1) org(3) dod(6) internet(1) private(4) enterprises(1)
microMuse(1279) museSnmpTrapForwarder(20) museSnmpTrapForwarder#(0) 1 }/
So kindly let me know is there any way I can use snmptranslate for V1
traps?
Regards,
Nitin Rathod
--
___
Net-snmp-coders mailing list
Net-snmp-coders@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
--
___
Net-snmp-coders mailing list
Net-snmp-coders@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
RE: snmpTranslate
snmptranslate.exe -M D:\usr\share\snmp\mibs -m ALL -Pu -TBd m
Regards,
Nitin R.
-Original Message-
From: Manjit [mailto:manjit.si...@globaledgesoft.com]
Sent: Monday, May 17, 2010 4:20 PM
To: Rathod, Nitin
Cc: net-snmp-coders@lists.sourceforge.net
Subject: Re: snmpTranslate
Please let me know the snmptranslate options used by you.
Regards,
Manjit
Rathod, Nitin wrote:
Hello,
I'm using snmptranslate utility for converting MIB files into textual
description specially for TRAPS. But using the snmpTranslate utility
netsnmp version 5.5 it is unable to convert TRAP-TYPE data types. It
is successfully able to convert the NOTIFICATION-TYPE.
Instead for TRAP-TYPE it is converting it to OBJECT-TYPE.
E.g:
MIB:
/MUSE-DEFAULT-NBI DEFINITIONS ::= BEGIN/
/ IMPORTS/
/ OBJECT-TYPE FROM RFC1155-SMI/
/ TRAP-TYPE FROM RFC-1215/
/ enterprises, NetworkAddress,IpAddress, Counter, Gauge, TimeTicks /
/ FROM RFC1155-SMI;/
/ -- In order for this trap to work correctly, the snmp trap forwarder/
/ -- must be used with the following gate writer configuration:/
/ --/
/ -- START WRITER SNMP_WRITER/
/ -- (/
/ -- TYPE = SNMP,/
/ -- REVISION = 1,/
/ -- GATEWAY = 'myManager',/
/ -- MAP = SNMP_MAP/
/ -- OID = '1.3.6.1.4.1.1279.20'/
/ -- );/
/ microMuse OBJECT IDENTIFIER ::= { enterprises 1279 }/
/ museSnmpTrapForwarder OBJECT IDENTIFIER ::= { microMuse 20 }/
/ /
/ museDefaultTrap TRAP-TYPE/
/ ENTERPRISE museSnmpTrapForwarder/
/ --VARIABLES { museIdentifier, museSerial, museNode, museNodeAlias,
museManager, museAgent,
museAlertGroup,museAlertKey,museSeverity,museSummary,
museStateChange,museFirstOccurrence,museLastOccurrence,museInternalLast,musePoll,museType,museTally,museClass,museGrade,museLocation,museOwnerUID,museOwnerGID,
museAcknowledged,museFlash,museServerName,museServerSerial }/
/ DESCRIPTION/
/ All information regarding an event which exists in the /
/ OMNIbus alerts.status table./
/ --REFERENCE/
/
--http://support.micromuse.com/documentation/supplementals/gateways/SNMP.pdf/
/ ::= 1/
/ /
/ /
/END/
After executing snmptranslate it gets converted as :
/MUSE-DEFAULT-NBI::microMuse/
/microMuse OBJECT-TYPE/
/ -- FROM MUSE-DEFAULT-NBI/
/::= { iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) 1279 }/
/MUSE-DEFAULT-NBI::museSnmpTrapForwarder/
/museSnmpTrapForwarder OBJECT-TYPE/
/ -- FROM MUSE-DEFAULT-NBI/
/::= { iso(1) org(3) dod(6) internet(1) private(4) enterprises(1)
microMuse(1279) 20 }/
/MUSE-DEFAULT-NBI::museSnmpTrapForwarder#/
/museSnmpTrapForwarder# TRAP-TYPE/
/ -- FROM MUSE-DEFAULT-NBI/
/::= { iso(1) org(3) dod(6) internet(1) private(4) enterprises(1)
microMuse(1279) museSnmpTrapForwarder(20) 0 }/
/MUSE-DEFAULT-NBI::museDefaultTrap/
*/museDefaultTrap OBJECT-TYPE/*
/ -- FROM MUSE-DEFAULT-NBI/
/ DESCRIPTION All information regarding an event which exists in the /
/ OMNIbus alerts.status table./
/::= { iso(1) org(3) dod(6) internet(1) private(4) enterprises(1)
microMuse(1279) museSnmpTrapForwarder(20) museSnmpTrapForwarder#(0) 1 }/
So kindly let me know is there any way I can use snmptranslate for V1
traps?
Regards,
Nitin Rathod
--
___
Net-snmp-coders mailing list
Net-snmp-coders@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
--
___
Net-snmp-coders mailing list
Net-snmp-coders@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
RE: snmpTranslate
Really waiting back for your reply.
Regards,
Nitin R.
-Original Message-
From: Manjit [mailto:manjit.si...@globaledgesoft.com]
Sent: Monday, May 17, 2010 4:20 PM
To: Rathod, Nitin
Cc: net-snmp-coders@lists.sourceforge.net
Subject: Re: snmpTranslate
Please let me know the snmptranslate options used by you.
Regards,
Manjit
Rathod, Nitin wrote:
Hello,
I'm using snmptranslate utility for converting MIB files into textual
description specially for TRAPS. But using the snmpTranslate utility
netsnmp version 5.5 it is unable to convert TRAP-TYPE data types. It
is successfully able to convert the NOTIFICATION-TYPE.
Instead for TRAP-TYPE it is converting it to OBJECT-TYPE.
E.g:
MIB:
/MUSE-DEFAULT-NBI DEFINITIONS ::= BEGIN/
/ IMPORTS/
/ OBJECT-TYPE FROM RFC1155-SMI/
/ TRAP-TYPE FROM RFC-1215/
/ enterprises, NetworkAddress,IpAddress, Counter, Gauge, TimeTicks /
/ FROM RFC1155-SMI;/
/ -- In order for this trap to work correctly, the snmp trap forwarder/
/ -- must be used with the following gate writer configuration:/
/ --/
/ -- START WRITER SNMP_WRITER/
/ -- (/
/ -- TYPE = SNMP,/
/ -- REVISION = 1,/
/ -- GATEWAY = 'myManager',/
/ -- MAP = SNMP_MAP/
/ -- OID = '1.3.6.1.4.1.1279.20'/
/ -- );/
/ microMuse OBJECT IDENTIFIER ::= { enterprises 1279 }/
/ museSnmpTrapForwarder OBJECT IDENTIFIER ::= { microMuse 20 }/
/ /
/ museDefaultTrap TRAP-TYPE/
/ ENTERPRISE museSnmpTrapForwarder/
/ --VARIABLES { museIdentifier, museSerial, museNode, museNodeAlias,
museManager, museAgent,
museAlertGroup,museAlertKey,museSeverity,museSummary,
museStateChange,museFirstOccurrence,museLastOccurrence,museInternalLast,musePoll,museType,museTally,museClass,museGrade,museLocation,museOwnerUID,museOwnerGID,
museAcknowledged,museFlash,museServerName,museServerSerial }/
/ DESCRIPTION/
/ All information regarding an event which exists in the /
/ OMNIbus alerts.status table./
/ --REFERENCE/
/
--http://support.micromuse.com/documentation/supplementals/gateways/SNMP.pdf/
/ ::= 1/
/ /
/ /
/END/
After executing snmptranslate it gets converted as :
/MUSE-DEFAULT-NBI::microMuse/
/microMuse OBJECT-TYPE/
/ -- FROM MUSE-DEFAULT-NBI/
/::= { iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) 1279 }/
/MUSE-DEFAULT-NBI::museSnmpTrapForwarder/
/museSnmpTrapForwarder OBJECT-TYPE/
/ -- FROM MUSE-DEFAULT-NBI/
/::= { iso(1) org(3) dod(6) internet(1) private(4) enterprises(1)
microMuse(1279) 20 }/
/MUSE-DEFAULT-NBI::museSnmpTrapForwarder#/
/museSnmpTrapForwarder# TRAP-TYPE/
/ -- FROM MUSE-DEFAULT-NBI/
/::= { iso(1) org(3) dod(6) internet(1) private(4) enterprises(1)
microMuse(1279) museSnmpTrapForwarder(20) 0 }/
/MUSE-DEFAULT-NBI::museDefaultTrap/
*/museDefaultTrap OBJECT-TYPE/*
/ -- FROM MUSE-DEFAULT-NBI/
/ DESCRIPTION All information regarding an event which exists in the /
/ OMNIbus alerts.status table./
/::= { iso(1) org(3) dod(6) internet(1) private(4) enterprises(1)
microMuse(1279) museSnmpTrapForwarder(20) museSnmpTrapForwarder#(0) 1 }/
So kindly let me know is there any way I can use snmptranslate for V1
traps?
Regards,
Nitin Rathod
--
___
Net-snmp-coders mailing list
Net-snmp-coders@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
--
___
Net-snmp-coders mailing list
Net-snmp-coders@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
Re: snmpTranslate
On 17 May 2010 11:48, Rathod, Nitin nitin_rat...@bmc.com wrote: I’m using snmptranslate utility for converting MIB files into textual description specially for TRAPS. But using the snmpTranslate utility netsnmp version 5.5 it is unable to convert TRAP-TYPE data types. It is successfully able to convert the NOTIFICATION-TYPE. Instead for TRAP-TYPE it is converting it to OBJECT-TYPE. Try the attached patch. Dave Index: snmplib/parse.c === --- snmplib/parse.c (revision 18768) +++ snmplib/parse.c (working copy) @@ -2971,6 +2971,7 @@ strcpy(np-parent, np-next-parent); strcat(np-parent, #); np-next-label = strdup(np-parent); +np-type = TRAPTYPE; return np; } -- ___ Net-snmp-coders mailing list Net-snmp-coders@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
RE: snmpTranslate
Tried the patch , and it did worked for TRAP-TYPE, but it is creating entries
as TRAP-TYPE for the parent module of the Traps i.e.
For the MIB below:
MUSE-DEFAULT-NBI DEFINITIONS ::= BEGIN
IMPORTS
OBJECT-TYPE FROM RFC1155-SMI
TRAP-TYPE FROM RFC-1215
enterprises, NetworkAddress,IpAddress, Counter, Gauge,
TimeTicks
FROM RFC1155-SMI;
-- In order for this trap to work correctly, the snmp trap forwarder
-- must be used with the following gate writer configuration:
--
-- START WRITER SNMP_WRITER
-- (
-- TYPE = SNMP,
-- REVISION = 1,
-- GATEWAY = 'myManager',
-- MAP = SNMP_MAP
-- OID = '1.3.6.1.4.1.1279.20'
-- );
microMuse OBJECT IDENTIFIER ::= { enterprises 1279 }
museSnmpTrapForwarder OBJECT IDENTIFIER ::= { microMuse 20 }
museDefaultTrap TRAP-TYPE
ENTERPRISE museSnmpTrapForwarder
--VARIABLES { museIdentifier, museSerial, museNode,
museNodeAlias, museManager, museAgent,
museAlertGroup,museAlertKey,museSeverity,museSummary,
museStateChange,museFirstOccurrence,museLastOccurrence,museInternalLast,musePoll,museType,museTally,museClass,museGrade,museLocation,museOwnerUID,museOwnerGID,
museAcknowledged,museFlash,museServerName,museServerSerial }
DESCRIPTION
All information regarding an event which exists in the
OMNIbus alerts.status table.
--REFERENCE
--http://support.micromuse.com/documentation/supplementals/gateways/SNMP.pdf;
::= 1
END
After executing snmpTranslate with the patch provided we get the proper
TRAP-TYPE but the Object-Identifier is getting converted into TRAP-TYPE i.e.
museSnmpTrapForwarder
museSnmpTrapForwarder# TRAP-TYPE
-- FROM MUSE-DEFAULT-NBI
::= { iso(1) org(3) dod(6) internet(1) private(4) enterprises(1)
microMuse(1279) museSnmpTrapForwarder(20) 0 }
Waiting for your reply
Regards,
Nitin R.
-Original Message-
From: dave.shi...@googlemail.com [mailto:dave.shi...@googlemail.com] On Behalf
Of Dave Shield
Sent: Monday, May 17, 2010 5:13 PM
To: Rathod, Nitin
Cc: net-snmp-coders@lists.sourceforge.net
Subject: Re: snmpTranslate
On 17 May 2010 11:48, Rathod, Nitin nitin_rat...@bmc.com wrote:
I'm using snmptranslate utility for converting MIB
files into textual description specially for TRAPS. But using the
snmpTranslate utility netsnmp version 5.5 it is unable to convert
TRAP-TYPE data types. It is successfully able to convert the
NOTIFICATION-TYPE.
Instead for TRAP-TYPE it is converting it to OBJECT-TYPE.
Try the attached patch.
Dave
--
___
Net-snmp-coders mailing list
Net-snmp-coders@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
Re: Problems building 5.2.4.1 with IPv6 support on Windows
On 4 May 2010 14:00, Ron Bets ron.b...@oracle.com wrote: Thanks. I am not tied specifically to the 5.4.x stream. My main requirement is support for IPv6 transport on Windows, Solaris, and Linux. Would I be better off with a different release? I've just put together the latest (hopefully final) pre-release bundle of 5.4.3 (rc3). It might be worth trying that version on your various systems, to check that it builds and runs correctly. Dave -- ___ Net-snmp-coders mailing list Net-snmp-coders@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
Re: different between Net-SNMP Agent service and snmpd.exe from command line
Hello Duy, Until now my attempts to reproduce this behavior have been unsuccessful. It would help if you could explain how the device with IP address 0.0.0.0 has been created such that I can reproduce your setup. Bart. On Fri, May 14, 2010 at 1:16 PM, Duy Doan Khuong dk...@tma.com.vn wrote: Hi Bart, OS Name: Microsoft(R) Windows(R) Server 2003, Enterprise Edition OS Version:5.2.3790 Service Pack 2 Build 3790 OS Manufacturer: Microsoft Corporation Thanks, Duy -- *From:* bart.vanass...@gmail.com [mailto:bart.vanass...@gmail.com] *On Behalf Of *Bart Van Assche *Sent:* Friday, May 14, 2010 5:58 PM *To:* Duy Doan Khuong *Cc:* net-snmp-coders@lists.sourceforge.net *Subject:* Re: different between Net-SNMP Agent service and snmpd.exe from command line Hello Duy, Thanks for the feedback. On which Windows version have you observed this behavior ? Bart. On Fri, May 14, 2010 at 12:47 PM, Duy Doan Khuong dk...@tma.com.vn wrote: Hi Bart, I modify as your guide, and now Net-SNMP service works as expected. Thank you. I have removed ip entry from additionaloptions, and run unregisteragent.bat, run registeragent.bat, started Net_SNMP, it also works as expected. I have stopped Net-SNMP agent, and started build in SNMP service of Microsofts, the result also is as expected. I think there is some thing wrong with the way we load ip mib while starting snmpd. Thanks, Duy -- *From:* bart.vanass...@gmail.com [mailto:bart.vanass...@gmail.com] *On Behalf Of *Bart Van Assche *Sent:* Friday, May 14, 2010 5:37 PM *To:* Duy Doan Khuong *Cc:* net-snmp-coders@lists.sourceforge.net *Subject:* Re: different between Net-SNMP Agent service and snmpd.exe from command line Hello Duy, This means that you have found a bug in one of Microsofts SNMP extension DLLs. You can switch from the Microsoft implementation of IP-MIB to the Net-SNMP implementation by modifying the third line of registeragent.bat as follows: set additionaloptions= -Lf C:/usr/log/snmpd.log -I-winExtDLL and next to stop the Net-SNMP service, run unregisteragent.bat, run registeragent.bat and to start the Net-SNMP service again. Bart. On Fri, May 14, 2010 at 12:17 PM, Duy Doan Khuong dk...@tma.com.vn wrote: Hi Bart, I have installed Net-SNMP service with winExtDll support. The third line of C:\usr\registeragent.bat on my system: set additionaloptions= -Lf C:/usr/log/snmpd.log -I-udp,udpTable,tcp,tcpTable,icmp,ip,interfaces,system_mib,sysORTable Duy -- *From:* bart.vanass...@gmail.com [mailto:bart.vanass...@gmail.com] *On Behalf Of *Bart Van Assche *Sent:* Friday, May 14, 2010 4:51 PM *To:* Duy Doan Khuong *Cc:* net-snmp-coders@lists.sourceforge.net *Subject:* Re: different between Net-SNMP Agent service and snmpd.exe from command line On Fri, May 14, 2010 at 11:09 AM, Duy Doan Khuong dk...@tma.com.vn wrote: I’m using Net-snmp 5.5. When I install snmpd service mode (Net-SNMP Agent service), run netsnmpwalk: C:\netsnmpwalk -v 2c -c public 192.168.98.193 1.3.6.1.2.1.4.20.1.1 IP-MIB::ipAdEntAddr.0.0.0.0 = IpAddress: 84.73.84.89 IP-MIB::ipAdEntAddr.10.11.12.193 = IpAddress: 10.11.12.193 IP-MIB::ipAdEntAddr.127.0.0.1 = IpAddress: 127.11.12.193 IP-MIB::ipAdEntAddr.192.168.98.193 = IpAddress: 192.168.98.193 It show wrong IP (84.73.84.89), it must be 0.0.0.0 I stop net-snmp service, and run snmpd by command line: c:\usr\binsnmpd.exe –a and run netsnmpwalk: C:\netsnmpwalk -v 2c -c public 192.168.98.193 1.3.6.1.2.1.4.20.1.1 IP-MIB::ipAdEntAddr.0.0.0.0 = IpAddress: 0.0.0.0 IP-MIB::ipAdEntAddr.10.11.12.193 = IpAddress: 10.11.12.193 IP-MIB::ipAdEntAddr.127.0.0.1 = IpAddress: 127.0.0.1 IP-MIB::ipAdEntAddr.192.168.98.193 = IpAddress: 192.168.98.193 Now it shows correct IP address. How can I make the net-snmp service show correct IP address (0.0.0.0) ? This depends on how the Net-SNMP agent service has been installed. Have you installed Net-SNMP with or without winExtDLL support ? And what is specified on the third line of C:\usr\registeragent.bat on your system (the line that sets the variable additionaloptions) ? Bart. -- ___ Net-snmp-coders mailing list Net-snmp-coders@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
Re: SNMP Get return wrong value from AgentX
On Sat, 15 May 2010 12:23:49 +0430, majid namnabat maj@gmail.com said: mn I think there were conflict between serial signal SIGIO, and mn agent_check_and_process(0) function. Also I have an important 300 ms mn timer. Is there there was a conflict between this timer (SIGALRM) and mn agent_check_and_process(0) function? If you're handling other signals then you should probably take a look at the way our agent deals with signals. We deliberately record the fact that a signal has happened but don't act on it until agent_check_and_process and other processing happens. IE, we delay actually dealing with the signal till it's safe to do so. It'll be a bit harder to do with other signals, though. -- Wes Hardaker Please mail all replies to net-snmp-coders@lists.sourceforge.net -- ___ Net-snmp-coders mailing list Net-snmp-coders@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
Re: Fwd: SF.net SVN: net-snmp:[18748] trunk/net-snmp/snmplib
On Sun, 16 May 2010 12:15:59 +0200, Bart Van Assche bvanass...@acm.org said: BVA This revision introduced the following compiler warning: BVA transports/snmpTLSBaseDomain.c: In function BVA 'netsnmp_tlsbase_session_init': transports/snmpTLSBaseDomain.c:407: BVA warning: control reaches end of non-void function Fixed. -- Wes Hardaker Please mail all replies to net-snmp-coders@lists.sourceforge.net -- ___ Net-snmp-coders mailing list Net-snmp-coders@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
Re: Fwd: SF.net SVN: net-snmp:[18567] trunk/net-snmp/testing/RUNFULLTESTS
On Sat, 15 May 2010 12:10:20 +0200, Thomas Anders thomas.and...@blue-cable.de said: TA Especially since these older scripts have been working without Perl TA before (and still do in the branches). The scripts still do work without perl. It's just the collection and summary that requires perl. -- Wes Hardaker Please mail all replies to net-snmp-coders@lists.sourceforge.net -- ___ Net-snmp-coders mailing list Net-snmp-coders@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
Re: snmpTranslate
On 17 May 2010 13:14, Rathod, Nitin nitin_rat...@bmc.com wrote: Tried the patch , and it did worked for TRAP-TYPE, but it is creating entries as TRAP-TYPE for the parent module of the Traps Yes - that's correct. It is applying the conversion rules from RFC 3584, to map the SMIv1 TRAP-TYPE definition (which lies outside the OID tree) into the equivalent SMIv2 Notification definition (which is an object within this tree) The anomolous status of SMIv1 traps is one of the reasons behind the switch to SMIv2 notifications, with SMIv1 being deprecated (even when used with SNMPv1 requests).You should really be looking to define your MIB files using SMIv2. After executing snmpTranslate with the patch provided we get the proper TRAP-TYPE but the Object-Identifier is getting converted into TRAP-TYPE i.e. museSnmpTrapForwarder museSnmpTrapForwarder# TRAP-TYPE Not quite - take a closer look at that definition. The name of the object is museSnmpTrapForwarder#. rather than museSnmpTrapForwarder - note the trailing # This is a dummy MIB object defined to act as a parent of the newly-converted trap object. See the Co-Existence RFC for details. Yes, it's being defined as TRAP-TYPE rather than OBJECT-IDENTIFIER (which is wrong) - the patch clearly needs to be a little more intelligent. But SMIv1 MIBs are essentially obsolete by now anyway. You should be using SMIv2 for any new MIB files. Perhaps you need to explain a bit more about what you are trying to do. Dave -- ___ Net-snmp-coders mailing list Net-snmp-coders@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
Re: reading snmpd.conf file
thanks, i will give it a try. On Fri, May 14, 2010 at 8:36 PM, Wes Hardaker harda...@users.sourceforge.net wrote: On Thu, 13 May 2010 13:27:39 -0400, Brad Lira snmp.apa...@gmail.com said: BL How can i read the snmpd.conf file when my custom modules loads in net-snmp? BL thanks for your help. If you call the register_config_handler() function you can register your own tokens to be found in the snmpd.conf file. See the read_config manual page for further details. -- Wes Hardaker Please mail all replies to net-snmp-coders@lists.sourceforge.net -- ___ Net-snmp-coders mailing list Net-snmp-coders@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
how to config the run-time master agent version
Hi, I have registered a subagent with net-snmp master agent. When building the master agent, v3 is set. So now all v1/v2c/v3 SNMP message can be processed by master agent. *When the agent is running, how to config the master agent to let it only accept v1 or v2c GET message??* Thank you very much. -- --- Best Regards Weiwei Zhang -- ___ Net-snmp-coders mailing list Net-snmp-coders@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
Re: how to config the run-time master agent version
Weiwei Zhang wrote: I have registered a subagent with net-snmp master agent. When building the master agent, v3 is set. So now all v1/v2c/v3 SNMP message can be processed by master agent. *When the agent is running, how to config the master agent to let it only accept v1 or v2c GET message??* If you don't explicitly configure a v3 user, v3 GETs will not be accepted anyway. +Thomas -- ___ Net-snmp-coders mailing list Net-snmp-coders@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
