10 More Discussions You Might Find Interesting
1. Solaris
Hi,
I've installed Solaris 11.3(live media) and configured DNS. Everytime I reboot the server, resolv.conf got deleted and it created a new nsswitch.conf.
I used below to configure both settings:
# svccfg -s dns/client
svc:/network/dns/client> setprop config/nameserver = (xx.xx.xx.aa... (1 Reply)
Discussion started by: flexihopper18
1 Replies
2. Shell Programming and Scripting
Hello all,
Newbie here.
I'm currently tasked with updating rsyslog.conf and auditd.conf on a large set of servers. I know the exact logging configurations that I want to enable. I have updated both files on on a server and hope to use the updated files as a template for the rest of the... (3 Replies)
Discussion started by: Mide
3 Replies
3. UNIX for Advanced & Expert Users
Dear all,
I have configured the "snmpd.conf" to be able to send traps to a network manager. The file is saved in "/etc/net-snmp/snmp/".
Attached is my configuration, which seems to be correct. (The IP address 10.192.4.4 is the trap receiver).
Next my aim was to send a test trap to verify... (0 Replies)
Discussion started by: nms
0 Replies
4. Shell Programming and Scripting
Hi
I am trying to spawn an snmptrap from python but i keep getting the following error
Invalid version specified after -v flag: 2c -c public 192.168.2.162 SNMPv2-SMI::enterprises.3.1.1
here is the python code i am using
from subprocess import Popen
Popen()
When i test the same... (0 Replies)
Discussion started by: kaf3773
0 Replies
5. Solaris
Hi All,
I am trying to generate a trap with in the localhost.
Please see the attachment for the exact syntax what I am using to generate the traps. However, I am getting the following error.
Unknown Object Identifier (Sub-id not found: (top) -> )
Can you please guide me how to use the... (1 Reply)
Discussion started by: ntgobinath
1 Replies
6. Shell Programming and Scripting
hello
i have a configuration file with some fields, for example:
#file conf.cfg
name;object;var1;var2;var8
then i have a csv data file:
var1;var2;var3;var4;var5;var6;var7;var8;var9
aaa;bbb;ccc;ddd;eee;fff;ggg;hhh;iii
...
now i should read the conf.cfg file and extract the... (3 Replies)
Discussion started by: drain
3 Replies
7. Shell Programming and Scripting
Hi,
Lets say I have a script which reads a conf file (say MASTERFILE) line by line to fetch file_name, source_path, dest_path. But currently, here the file name are static for eg: ABC.txt or XYZ.txt. So i have hard-coded in the conf file.
So what happens that the script picks up the file_name... (1 Reply)
Discussion started by: amit.mathur08
1 Replies
8. UNIX for Advanced & Expert Users
i have this program running on my solaris and there are two identical config files, i am not sure which one is being used by this program but I am sure it uses one of them.
I run lsof -p {pid} but it does not show which config file has been read by this program, what i am doing wrong?
thanks (4 Replies)
Discussion started by: fedora
4 Replies
9. Solaris
Hello Guys,
Do we need to configure this file only if we add SAN disk or even if we add local disk, do we need to modify? (4 Replies)
Discussion started by: mokkan
4 Replies
10. UNIX for Advanced & Expert Users
HI,
I want a help for Configuring snmpd.conf and snmptrapd.conf (i.e Configuring SNMP)
for receiving
TRAPS in my networks. I am using RHEL4.0 OS.
Please tell me How I can configure above two files in a proper way and at an
advanced level.
Especially I am getting... (2 Replies)
Discussion started by: jagdish.machhi@
2 Replies
SNMP_CONFIG(5) Net-SNMP SNMP_CONFIG(5)
NAME
snmp_config - handling of Net-SNMP configuration files
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 4 directories, in order: /etc/snmp, /usr/share/snmp, /usr/lib(64)/snmp, and $HOME/.snmp. In each of these
directories, it looks for files snmp.conf, snmpd.conf and/or snmptrapd.conf, as well as snmp.local.conf, snmpd.local.conf and/or
snmptrapd.local.conf. *.local.conf are always read last. In this manner, there are 8 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. The path for the persistent data should be included when running applications that use persistent storage, such
as snmpd.
Applications will read persistent configuration files in the following order of preference:
file in SNMP_PERSISTENT_FILE environment variable
directories in SNMPCONFPATH environment variable
directory defined by persistentDir snmp.conf variable
directory in SNMP_PERSISTENT_DIR environment variable
default /var/lib/net-snmp directory
Finally, applications will write persistent configuration files in the following order of preference:
file in SNMP_PERSISTENT_FILE environment variable
directory defined by persistentDir snmp.conf variable
directory in SNMP_PERSISTENT_DIR environment variable
default /var/lib/net-snmp directory
Note: When using SNMP_PERSISTENT_FILE, the filename should match the application name. For example, /var/net-snmp/snmpd.conf.
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
The same approach can be used to set configuration directives for a particular client application (or group of applications). For example,
any program that uses the 'snmp_parse_args()' call to handle command-line arguments (including the standard command-line tools shipped as
part of the Net-SNMP distributions) will automatically read the config file 'snmpapp.conf'. To set library-level settings for these appli-
cations (but not other more-specific tools), use configuration such as the following:
[snmp] defCommunity myCommunity
for a single directive, or
# make this file handle snmp.conf tokens:
[snmp]
defCommunity myCommunity
defVersion 2c
# return to our original snmpapp.conf tokens:
[snmpapp]
for multiple settings. Similarly for any other application token (as passed to init_snmp()).
COMMENTS
Any lines beginning with the character '#' in the configuration files are treated as a comment and are not parsed.
INCLUDING OTHER CONFIGURATION FILES
It is possible to include other configuration files for processing during normal configuration file processing.:
# include site specific config
include site.conf
This will search every directory in the configuration path for files
named site.conf, and will process those files before returning to the
processing of the original file. Note that if '.conf' is omitted,
it will be appended. That is, all configuration files must end
in '.conf'.
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
netsnmp_config_api(3) manual page.
SEE ALSO
snmpconf(1), netsnmp_config_api(3), snmp.conf(5), snmpd.conf(5)
V5.7.2 08 Mar 2010 SNMP_CONFIG(5)