Sponsored Content
Special Forums UNIX and Linux Applications Infrastructure Monitoring Facing problem while configuring snmp Post 302381162 by RayATSun on Thursday 17th of December 2009 09:52:24 AM
Old 12-17-2009
Hello,

Its a good idea to start a support request with a cat of /etc/release. If you are running s10 then lsof does not report properly. Something is blocking on your port. Try:

Code:
# netstat -an -P udp | grep 161

to check the status of that port. Go from there.

Ray dot Mroz AT Sun dot Com
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

facing a problem in redirection

Hi, I am doing this perl script print (@line(1..15)); the lines 1 to 15 get printed... how can i redirect this to file? thanks and regards vivek.s (4 Replies)
Discussion started by: vivekshankar
4 Replies

2. Solaris

please help as i am facing problem with uptime

Hi I am getting the uptime output as follows 12:40am up 4 day(s), 18:29, 2 users, load average: 38.97, 36.54, 34.89 The load average is too high . I have checked the processes , but no process is taking too much cpu time Please help (3 Replies)
Discussion started by: guy009
3 Replies

3. Solaris

Facing problem with zone

i am using this way to create zone1 and zone2 bash-2.05b# zonecfg -z zone1 zone1: No such zone configured Use 'create' to begin configuring a new zone. zonecfg:zone1> create zonecfg:zone1> set zonepath=/zone/1 zonecfg:zone1> set autoboot=true zonecfg:zone1> add net zonecfg:zone1:net>... (6 Replies)
Discussion started by: coxmanchester
6 Replies

4. Shell Programming and Scripting

problem facing in if -else condition

can u plz tell me where is the error echo enter the filename to be searched read fname if #-d $fname then echo file exists if then echo itsa directory elif then echo its readable cat $fname else echo its not readable fi else ... (1 Reply)
Discussion started by: gotam
1 Replies

5. Infrastructure Monitoring

Configuring SNMP in linux

I am trying to enabling SNMP access and trap forwarding for Linux(RHEL5) using following official url from IBM. http://publib.boulder.ibm.com/infocenter/eserver/v1r2/index.jsp?topic=/diricinfo/fqm0_t_enabling_snmp_access_and_trap_forwarding_for_linux.html In my system, snmp and snmplibs are... (1 Reply)
Discussion started by: SiddhV
1 Replies

6. Shell Programming and Scripting

Facing Issue after configuring logrotate

Hi, I have a logrotate configuration which rotates a log every night 1 min before midnight, but somehow its not working and unfortunately not showing any error message as well. Sharing the code for the cron job as well as the conf file, I am using, if some one coule help me..whats wrong with... (2 Replies)
Discussion started by: Neeryan
2 Replies

7. AIX

facing problem using su

Hi, I am able to login using su - or su directly , # prompt is coming, it doesnt ask for password. any normal user on aix system is login using su - or su . Please suggest where to change the configuration direct root login is disabled in /etc/ssh/sshd_config file. (0 Replies)
Discussion started by: manoj.solaris
0 Replies

8. 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

9. Solaris

Facing problem in configuring syslog server in Solaris

I am trying to configure central syslog server On hostA, in /etc/syslog.conf file,I am adding below line*.err;kern.debug;daemon.notice;mail.crit @hostB then I am restarting syslog servicesvcadm restart /system/system-log In hostA, I have already added hostB entry in /etc/hosts... (5 Replies)
Discussion started by: amity
5 Replies

10. SuSE

Facing issue configuring network

Please let me know how to configure network in suse Linux, I have configured the network using ifup and network manager, it is not giving any error but not working, using suse Linux 11.0 sp3 I have checked network connectivity is working. (0 Replies)
Discussion started by: manoj.solaris
0 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 10:30 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy