Sponsored Content
Full Discussion: SNMP - what am I seeing?
Special Forums UNIX and Linux Applications Infrastructure Monitoring SNMP - what am I seeing? Post 302465500 by msarro on Friday 22nd of October 2010 03:23:55 PM
Old 10-22-2010
SNMP - what am I seeing?

Hey everyone!
First, thank you in advance for any help you can provide. I'm a fairly experienced linux user, and just getting my feet wet in solaris for a project here at the office. I am trying to use snmpget on a linux box to get information from a Solaris 10 system. The solaris 10 system has snmpdx running (solstice, used for SNMP by a vendor solution that is installed). However it also appears to have snmpd running. Here are the commands and output that I get:

Code:
bash-3.00# ps -ef |grep snm
    root   775     1   0   Mar 10 ?         345:35 /usr/lib/snmp/brdsftMIB2 -r -c /usr/local/broadworks/bw_base/conf -p 10161
    root   726     1   0   Mar 10 ?           0:00 /usr/lib/dmi/snmpXdmid -s as1
    root   755     1   0   Mar 10 ?           9:16 /usr/sfw/sbin/snmpd
    root   717     1   0   Mar 10 ?           0:12 /usr/lib/snmp/snmpdx -y -c /etc/snmp/conf
    root  2061 27184   0 19:23:21 pts/3       0:00 grep snm
  bworks  8672  8663   0   Oct 06 ?          31:42 /usr/local/java/java_base/bin/java -Dp=openclientserver -server -Docs.snmp.comp
  bworks  8421  8412   0   Oct 06 ?         154:45 /usr/local/java/java_base/bin/java -Dp=snmp -XX:ParallelGCThreads=2 -classpath 
  bworks  8410     1   0   Oct 06 ?           0:00 /usr/bin/perl ./bwpmd -snmp -d /var/broadworks/logs/snmp

Code:
bash-3.00# lsof -i -nP |grep snm
snmpdx      717   root    3u  IPv4 0x60000942040      0t0  UDP *:17
snmpdx      717   root    4u  IPv4 0x60000942240      0t0  UDP *:17
snmpdx      717   root    5u  IPv4 0x6000249fa80      0t0  UDP *:17
snmpXdmid   726   root    0u  IPv4 0x6000249f680      0t0  UDP *:17
snmpXdmid   726   root    1u  IPv4                         TCP no TCP/UDP/IP information available
snmpXdmid   726   root    5u  IPv4 0x6000249f880      0t0  UDP *:17
snmpXdmid   726   root    6u  IPv4 0x6000249f280      0t0  UDP *:17
snmpd       755   root   13u  IPv4 0x6000249ec80      0t0  UDP *:17
snmpd       755   root   14u  IPv4 0x6000249f080      0t0  UDP *:17
snmpd       755   root   15u  IPv4 0x6000249ee80      0t0  UDP *:17
snmpd       755   root   16u  IPv4 0x600015040c0      0t0  UDP *:17
snmpd       755   root   17u  IPv4 0x60002b65b00      0t0  UDP *:17
snmpd       755   root   18u  IPv4 0x60002b65900      0t0  UDP *:17

This shows the services running on UDP port 17. The problem is if I try and query remotely on port 17, everything fails. Why does lsof show port 17 and not 161? In fact typing
Code:
lsof -i |grep 161

doesn't return a single thing.

Any help would be appreciated. Both daemons show as running, and I'd like to figure out what ports they're running, and then figure out what information is attainable from each daemon. I'm assuming snmpdx is just vendor related stuff, because from my research snmpd should be for OS stuff. Any thoughts?
Thanks!
-Matthew
 

7 More Discussions You Might Find Interesting

1. Solaris

snmp

Hi, I want to configure snmp on solaris 10,What are steps (1 Reply)
Discussion started by: manoj.solaris
1 Replies

2. Infrastructure Monitoring

snmp

hello, I am looking for Overall CPU usage info in net-snmp 5.1.2 on solaris 5.8. I didn't see hrProcessorLoad info from host-resource-mib. Is there any other MIB I could look into? Thanks (0 Replies)
Discussion started by: lamou23
0 Replies

3. IP Networking

Sending data from DELL OMSA SNMP and Custom SNMP MIB to same UDP port 161

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

4. Red Hat

Sending data from DELL OMSA SNMP and Custom SNMP MIB to same UDP port 161

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

5. IP Networking

SNMP Problem - SNMP not getting to the agent.

I am having a problem with an SNMP event, and I am not sure where I should be looking to solve this problem. Description: There is an SNMP event in our system that for one reason or another is not getting sent out as an email because it is never getting to our SNMP agent. I see where the... (0 Replies)
Discussion started by: broberts
0 Replies

6. Infrastructure Monitoring

SNMP traps to SNMP server

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

7. UNIX for Dummies Questions & Answers

Need to transfer all kernel logs (var/log/messages) to the snmp listener as snmp trap

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
snmpd(1M)						  System Administration Commands						 snmpd(1M)

NAME
snmpd - daemon to respond to SNMP request packets SYNOPSIS
/usr/sfw/sbin/snmpd [options] [listening addresses] DESCRIPTION
The snmpd daemon is an SNMP agent that binds to a port and awaits requests from SNMP management software. Upon receiving a request, it pro- cesses the request(s), collects the requested information, performs any requested operation(s), and, finally, returns information to the requester. OPTIONS
The following options are supported: -a Log the source addresses of incoming requests. -A Append to the log file rather than truncating it. -c file Read file as a configuration file. -C Do not read any configuration files except the one optionally specified by the -c option. Note that this behavior also covers the persistent configuration files. This can result in dynamically-assigned values being reset fol- lowing an agent restart, unless the relevant persistent configuration files are explicitly loaded using the -c option. -d Dump (in hexadecimal) the sent and received SNMP packets. -D[token[,...]] Turn on debugging output for the given token(s). Without any tokens specified, this option defaults to printing all of the tokens (which is equivalent to the keyword ALL). Use ALL for extremely verbose output. Note that you must not put a space between the -D flag and the listed tokens. -f Do not fork() from the calling shell. -g GID Change to the numerical group ID GID after opening listening sockets. -h, --help Display a brief usage message and then exit. -H Display a list of configuration file directives understood by the agent and then exit. -I -initlist This option specifies which modules you do (or do not) want to be initialized when the agent starts up. If the comma-separated initlist is preceded with an hyphen (-), it is the list of modules that you do not want to be started. Otherwise, initlist is the list of mod- ules to be started. To obtain a list of compiled modules, run the agent with the arguments -Dmib_init -H This command assumes you have debugging support compiled in. -l [file] Log all output from the agent (including stdout and stderr) to file. If no filename is given, log to a default file set at compile time, normally /var/log/snmpd.log. -L Do not open a log file. Send all messages to stderr instead. -P file Save the process ID of the daemon in file. -q Print simpler output for easier automated parsing. -r Do not require root access to run the daemon. Specifically, do not exit if files accessible only to root (such as /dev/kmem) cannot be opened. -s Use syslog for logging. See syslogd(1M) -S d[0-7] Specifies the syslog facility to use when logging to syslog. d means LOG_DAEMON and the integers 0 through 7 refer to LOG_LOCAL0 through LOG_LOCAL7. LOG_DAEMON is the default. -u UID Change to the user ID UID (which can be given in numerical or text form) after opening listening sockets. -v --version Display version information for the agent and then exit. -V Symbolically dump SNMP transactions. -x address Listens for AgentX connections on address rather than on the default /var/agentx/master. The address can either be a Unix domain socket path or the address of a network interface. The format is the same as the format of listening addresses described below. Note that it is a possible security risk to expose the master agent listening address through TCP/UDP. See section 9 of RFC 2741 for more details. -X Run as an AgentX subagent rather than as an SNMP master agent. Listening Addresses By default, snmpd listens for incoming SNMP requests only on UDP port 161. However, it is possible to modify this behavior by specifying one or more listening addresses as arguments to the daemon. A listening address takes the form: [<transport-specifier>:]<transport-address> At its simplest, a listening address can consist of only a port number, in which case snmpd listens on that UDP port on all IPv4 inter- faces. Otherwise, the <transport-address> part of the specification is parsed according to the following table: <transport-specifier> <transport-address> format udp hostname[:port] or IPv4-address[:port] tcp hostname[:port] or IPv4-address[:port] unix pathname Currently transports TCP/UDP over IPv4/IPv6 and unix domain sockets. Note that <transport-specifier> strings are case-insensitive so that, for example, tcp and TCP are equivalent. Below are some examples, with accompanying explanations. 127.0.0.1:161 Listen on UDP port 161, but only on the loopback interface. This prevents snmpd from being queried remotely. The :161 is redundant because that is the default SNMP port. TCP:1161 Listen on TCP port 1161 on all IPv4 interfaces. unix:/tmp/local-agent Listen on the Unix domain socket /tmp/local-agent. /tmp/local-agent Identical to the previous specification, because the Unix domain is the default transport if and only if the first character of <trans- port-address> is a slash (/). udp6:10161 Listen on port 10161 on all IPv6 interfaces. Note that not all the transport domains listed above will always be available. For example, hosts with no IPv6 support will not be able to use udp6 transport addresses, and attempts to do so will result in the error "Error opening specified endpoint". FILES
snmpd checks for the existence of and parses the following files: snmp.conf Common configuration for the agent and applications. See snmp.conf(4) for details. snmpd.local.conf Agent-specific configuration. See snmp.conf(4) for details. These files are optional and can be used to configure access control, trap generation, subagent protocols, and other features. In addition to these two configuration files, the agent will read any files with the names snmpd.conf and snmpd.local.conf in a colon- separated path specified in the SNMPCONFPATH environment variable, the default location upon agent startup are /etc/sma/snmp and /usr/local/share/snmp. /etc/sma/snmp/mibs The agent loads all files in this directory as MIBs. It does not, however, load any file that begins with a dot (.) or descend into subdirectories. EXIT STATUS
0 Successful completion. 1 A usage syntax error. A usage message is displayed. Also used for timeout errors. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWsmagt | +-----------------------------+-----------------------------+ |Interface Stability |Stable | +-----------------------------+-----------------------------+ SEE ALSO
snmp.conf(4), attributes(5) NOTES
In addition to basic privileges, to run successfully, the agent requires PRIV_NET_PRIVADDR. See privileges(5). SunOS 5.10 20 Jan 2004 snmpd(1M)
All times are GMT -4. The time now is 09:14 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy