SNMP Walk need to enable


 
Thread Tools Search this Thread
Operating Systems HP-UX SNMP Walk need to enable
Prev   Next
# 7  
Old 07-31-2014
On the same network we have a another server, in which we tried the SNMP walk and found success.

After updating some patched provided by tool provider, we are able to get the SNMP walk from our tool installed server.

Thanks a ton for all your valuable reply.
 
Login or Register to Ask a Question

Previous Thread | Next Thread

8 More Discussions You Might Find Interesting

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

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

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

4. UNIX for Advanced & Expert Users

"Walk" apache installs and do a tar on them...

Hello unix.com Community: I need help with writing a "common" script that can get the httpd installs by name and install directory|ies and tar.gz them up by name and point that tar operation to the matching install directory. I have 2 Distros that I am concerned with for this task: CentOS and... (3 Replies)
Discussion started by: Habitual
3 Replies

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

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

7. Shell Programming and Scripting

How to walk through a config file with /bin/sh

Hi there, i tried a lot of things actually to get my script running as expected. Situation: I have a config file with several parameters in the form FFF.thisIsaParam=Value FFF.included.AnotherPortofParam=Value Additionally there are some comments in it. Script should... (8 Replies)
Discussion started by: smhaller
8 Replies

8. Programming

ftw/nftw -- filesystem tree walk

Hi, I recently experimented with ftw() and nftw(). These are function for calling some function for every file in a subtree. I need to get full information about type of file. Almost everything is working according to documentation but I noticed following problem: With a value FTW_PHYS... (2 Replies)
Discussion started by: odys
2 Replies
Login or Register to Ask a Question
SNMP.CONF(5)							     Net-SNMP							      SNMP.CONF(5)

NAME
snmp_config - describes how to configure the Net-SNMP applications. DESCRIPTION
The Net-SNMP package uses various configuration files to configure its applications. This manual page merely describes the overall nature of them, so that the other manual pages don't have to. DIRECTORIES SEARCHED
First off, there are numerous places that configuration files can be found and read from. By default, the applications look for configura- tion files in the following 3 directories, in order: /usr/share/snmp, /usr/lib/snmp, and $HOME/.snmp. In each of these directories, it looks for files with the extension of both .conf and 6 default places a configuration file can exist for any given configuration file type. Additionally, the above default search path can be overridden by setting the environment variable SNMPCONFPATH to a colon-separated list of directories to search for. Finally, applications that store persistent data will also look in the /var/snmp directory for configuration files there. CONFIGURATION FILE TYPES
Each application may use multiple configuration files, which will configure various different aspects of the application. For instance, the SNMP agent (snmpd) knows how to understand configuration directives in both the snmpd.conf and the snmp.conf files. In fact, most applications understand how to read the contents of the snmp.conf files. Note, however, that configuration directives understood in one file may not be understood in another file. For further information, read the associated manual page with each configuration file type. Also, most of the applications support a -H switch on the command line that will list the configuration files it will look for and the directives in each one that it understands. The snmp.conf configuration file is intended to be a application suite wide configuration file that supports directives that are useful for controlling the fundamental nature of all of the SNMP applications, such as how they all manipulate and parse the textual SNMP MIB files. SWITCHING CONFIGURATION TYPES IN MID-FILE It's possible to switch in mid-file the configuration type that the parser is supposed to be reading. Since that sentence doesn't make much sense, lets give you an example: say that you wanted to turn on packet dumping output for the agent by default, but you didn't want to do that for the rest of the applications (ie, snmpget, snmpwalk, ...). Normally to enable packet dumping in the configuration file you'd need to put a line like: dumpPacket true into the snmp.conf file. But, this would turn it on for all of the applications. So, instead, you can put the same line in the snmpd.conf file so that it only applies to the snmpd daemon. However, you need to tell the parser to expect this line. You do this by putting a spe- cial type specification token inside a [] set. In other words, inside your snmpd.conf file you could put the above snmp.conf directive by adding a line like so: [snmp] dumpPacket true This tells the parser to parse the above line as if it were inside a snmp.conf file instead of an snmpd.conf file. If you want to parse a bunch of lines rather than just one then you can make the context switch apply to the remainder of the file or until the next context switch directive by putting the special token on a line by itself: # make this file handle snmp.conf tokens: [snmp] dumpPacket true logTimestamp true # return to our original snmpd.conf tokens: [snmpd] rocommunity mypublic COMMENTS
Any lines beginning with the character '#' in the configuration files are treated as a comment and are not parsed. API INTERFACE
Information about writing C code that makes use of this system in either the agent's MIB modules or in applications can be found in the read_config(3) manual page. SEE ALSO
read_config(3). 4th Berkeley Distribution 28 Aug 2001 SNMP.CONF(5)