10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
i am working with embedded system -Dell DCS management sub system. my question is as below:
currently we are using linux kernel 2.6.30 build and we have a kernel logs stored to the /var/log/messages path. now we have to transfer all this logs to the specified SNMP target as a part of SNMP... (4 Replies)
Discussion started by: vipul_prajapati
4 Replies
2. Infrastructure Monitoring
Dear Champs,
I am new to unix, and need to configure linux server to send below traps to a SNMP server.
Monitoring TRAP Disk Space Low
Monitoring TRAP Memory Low
Monitoring TRAP CPU high
Monitoring TRAP Admin login/Logoff
Please help me how to send this information to my SNMP server... (2 Replies)
Discussion started by: stavar
2 Replies
3. Red Hat
Hi ,
Currently DELL OMSA SNMP sends data through default udp port 161.I want my custom SNMP MIB also to send data in the same udp port 161.Whether its possible.If yes where to configure .I tried starting my custom MIB in udp port 161,but it throws port already in use.Kindly guide. (1 Reply)
Discussion started by: prabakar4all
1 Replies
4. IP Networking
Hi ,
Currently DELL OMSA SNMP sends data through default udp port 161.I want my custom SNMP MIB also to send data in the same udp port 161.Whether its possible.If yes where to configure .I tried starting my custom MIB in udp port 161,but it throws port already in use.Kindly guide. (0 Replies)
Discussion started by: prabakar4all
0 Replies
5. Infrastructure Monitoring
Good Day,
I have requirement to monitor a number of NCR unix server for our unix team. As the System Management product that we use in out company does not have an agent for NCR unix I am investigating the SNMP route. I got the unix guys to enable SNMP however, it seems the default MIB that is... (0 Replies)
Discussion started by: priteshj
0 Replies
6. IP Networking
Hi,
I am new to Net-snmp and I am trying to build upon the template .c and .h files, generated by the mib2c tool, for the agent development. Can somebody guide me on how to build upon the functions generated by mib2c tool or provide a sample code for an agent.
Thanks (0 Replies)
Discussion started by: tisha
0 Replies
7. UNIX for Dummies Questions & Answers
Hi,
I'm reading net-snmp, using Unix (Solaries) and C language ...
- I can manipulate variable (managed object) declared in agent, but the manager can't see that ... it only see the initialization and the value which it ulters using snmpset ...
Ex:
Agent:
static int ... (0 Replies)
Discussion started by: zainab
0 Replies
8. Solaris
Hi,
I am trying to apply the steps in the below link:
http://manageengine.adventnet.com/products/applications_manager/help/appendix/snmp-agent-discovery.html#solaris
but I couldn't continue with the step number 2 ... what is the path of C compiler.
export PATH=<gcc path>:$PATH
... (3 Replies)
Discussion started by: adel8483
3 Replies
9. Solaris
:confused: :confused:
I have a subagent that registers to snmpd on Solaris 8. One of the queries this subagent handles can take an exceptionally long time (it can be on the order of ~30 seconds).
When this query is sent to the processor via SNMP, the subagent is being dropped from the... (1 Reply)
Discussion started by: jalburger
1 Replies
10. IP Networking
Hi,
I am really new in linux and SNMP.
I have a SNMP agent in Linux (net-snmp). I have my MIB
in the /usr/share/mibs directory, and I didn't manage to understand where and how do I put the values of the fields in the MIB? The values are static, so the agent need to return the same value in... (0 Replies)
Discussion started by: linuxbegginer
0 Replies
NETSNMP_AGENT_API(3) Net-SNMP NETSNMP_AGENT_API(3)
NAME
netsnmp_agent_api - embedding an agent into a external application
SYNOPSIS
#include <net-snmp/net-snmp-config.h>
#include <net-snmp/net-snmp-includes.h>
#include <net-snmp/agent/net-snmp-agent-includes.h>
int
main (int argc, char *argv[])
{
int agentx_subagent = 1; /* Change this if you're a master agent. */
snmp_enable_stderrlog();
/* If we're an AgentX subagent... */
if (agentx_subagent) {
/* ...make us an AgentX client. */
netsnmp_ds_set_boolean(NETSNMP_DS_APPLICATION_ID,
NETSNMP_DS_AGENT_ROLE, 1);
}
init_agent("yourappname");
/* Initialize your MIB code here. */
init_my_mib_code();
/* `yourappname' will be used to read yourappname.conf files. */
init_snmp("yourappname");
/* If we're going to be a SNMP master agent... */
if (!agentx_subagent)
init_master_agent(); /* Listen on default port (161). */
/* Your main loop here... */
while (whatever) {
/* if you use select(), see snmp_api(3) */
/* --- OR --- */
agent_check_and_process(0); /* 0 == don't block */
}
/* At shutdown time: */
snmp_shutdown("yourappname");
}
Then:
$(CC) ... `net-snmp-config --agent-libs`
DESCRIPTION
Our goal is to create a easy to use interface to the Net-SNMP package such that you can take code that you have written that has been
designed to be a Net-SNMP MIB module and embed it into an external application where you can either chose to be a SNMP master agent or an
AgentX sub-agent using the same MIB module code. Our suggestion is that you use our (or another) SNMP agent as the AgentX master agent and
chose to become an AgentX subagent which then attaches to the master.
The Net-SNMP package provides a pair of libraries that enables easy embedding of an SNMP or AgentX agent into an external software package.
AgentX is an extensible protocol designed to allow multiple SNMP sub-agents all run on one machine under a single SNMP master agent. It is
defined in RFC 2741.
You will need to perform a few tasks in order to accomplish this. First off, you will need to initialize both the SNMP library and the SNMP
agent library. As indicated above, this is done slightly differently depending on whether or not you are going to perform as a master agent
or an AgentX sub-agent.
CONFIGURATION
If you intend to operate as an AgentX sub-agent, you will have to configured the Net-SNMP package with agentx support (which is turned on
by default, so just don't turn it off)
Additionally, you will need to link against the net-snmp libraries (use the output of "net-snmp-config --agent-libs" to get a library list)
and call subagent_pre_init() as indicated above.
COMPILING
In order to make use of any of the above API, you will need to link against at least the four libraries listed above.
FUNCTIONS
where to find out more information on them. It is certainly not a complete list of what is available within all the net-snmp libraries.
snmp_enable_stderrlog()
Logs error output from the SNMP agent to the standard error stream.
netsnmp_ds_set_boolean()
Please see the default_store(3) manual page for more information about this API.
init_agent(char *name)
Initializes the embedded agent. This should be called before the init_snmp() call. name is used to dictate what .conf file to read
when init_snmp() is called later.
init_snmp(char *name)
Initializes the SNMP library. Note that one of the things this will do will be to read configuration files in an effort to config-
ure your application. It will attempt to read the configuration files named by the name string that you passed in. It can be used
to configure access control, for instance. Please see the netsnmp_config_api(3), snmp_config(5), and snmpd.conf(5) manual pages
for further details on this subject.
init_master_agent(void)
Initializes the master agent and causes it to listen for SNMP requests on its default UDP port of 161.
agent_check_and_process(int block)
This checks for packets arriving on the SNMP port and processes them if some are found. If block is non-zero, the function call
will block until a packet arrives or an alarm must be run (see snmp_alarm(3)). The return value from this function is a positive
integer if packets were processed, zero if an alarm occurred and -1 if an error occured.
snmp_shutdown(char *name);
This shuts down the agent, saving any needed persistent storage, etc.
SEE ALSO
http://www.net-snmp.org/tutorial-5/toolkit/ select(2), snmp_api(3), default_store(3), snmp_alarm(3), netsnmp_config_api(3), snmp_config(5),
snmpd.conf(5)
V5.6.2.1 13 Aug 2010 NETSNMP_AGENT_API(3)