by the way I have to configure this SNMP stuff on a firewall that is part of a SNMP project
so they want to allow only some hosts to send SNMP packets a across this Linux firewall
Since I still don't get how to do it on SNMP like in Windows
I was thinking using hosts.allow and deny like this
but I read this
# Never configure TCP Wrappers on firewall host.
# Put TCP Wrappers behind a firewall systems as TCP Wrappers is no substitute for netfilter or pf firewall.
I am working on a project, which has the following type of hardware setup.
A special hardware device is receiving data from an external network interface. So we can have multiple such a hardware devices. Now these hardware devices will route the captured incoming data through the external... (4 Replies)
there are a number of clients connected to a server.... how can i count that each clients recieve ...? how do i moniter the activity of the client..? (2 Replies)
Hi,
I want to capture snmp packets in AIX.
When i give print from AIX6.1, Printer will give its response thru' snmp.
I used iptrace command like below, but it is not capturing snmp packets other packets are captured like udp, tcp..
1. iptrace command:
/usr/sbin/iptrace -a -i en0... (1 Reply)
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)
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)
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)
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)
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
LEARN ABOUT DEBIAN
snmpd.internal
SNMPD.INTERNAL(5snmp) Net-SNMP SNMPD.INTERNAL(5snmp)NAME
snmpd.internal - internal configuration of the Net-SNMP agent
DESCRIPTION
The snmpd.conf(5) man page defines the syntax and behaviour of the main configuration directives that can be used to control the operation
of the Net-SNMP agent, and the management information it provides.
However there are several other configuration directives (many of which, though not all, start with a leading underscore) that are recog-
nised by the agent. These are typically used to retain configuration across agent restarts, and are not intended for direct user access.
This man page list these directives, giving a brief indication of where they are used. For full details - see the relevant source files.
If you can't follow that source, you probably shouldn't be fiddling with these directives!
AGENT BEHAVIOUR
quit
ACCESS CONTROL
VACM Configuration
vacmView / vacmGroup / vacmAccess
These directives are used to retain dynamically configured access control settings.
SYSTEM INFORMATION
System Group
setSerialNo
This directive is used to implement the advisory lock object snmpSetSerialNo.
psyslocation / psyscontact / psysname
These directives are used to retain dynamically configured system settings. They will be overridden by the corresponding sysLoca-
tion, sysContact and sysName directives.
ACTIVE MONITORING
Notification Handling
pauthtrapenable
This directive is used to retain the dynamically configured setting of whether the agent should generate authenticationFailure
traps. It will be overridden by the corresponding authtrapenable directive.
snmpNotify*Table
targetAddr / targetParams
These directives are used to retain dynamically configured notification destination settings.
DisMan Event MIB
_mteE*Table, _mteOTable, _mteT*Table
These directives are used to retain dynamically configured event, object and monitor trigger settings.
mteObjectsTable / mteTriggerTable
These directives are for compatibility with the previous disman/event-mib implementation.
DisMan Schedule MIB
_schedTable
This directive is used to retain dynamically configured scheduled events.
EXTENDING AGENT FUNCTIONALITY
Arbitrary Extension Commands
extend-sh
exec2 / sh2 / execFix2
These directives were defined by analogy with equivalent directives in the previous ucd-snmp/extensible implementation. They are
deprecated, and should not be used.
FILES
/etc/snmp/snmpd.conf
SEE ALSO snmpconf(1), snmpd.conf(5), snmp.conf(5), snmp_config(5), snmpd(8), EXAMPLE.conf, read_config(3).
4th Berkeley Distribution 08 Feb 2002 SNMPD.INTERNAL(5snmp)