2009/5/11 Richard Gipps richa...@triodatacom.com:
I have been experimenting with the monitor function (specifying an event)
and I have found some behavior which I can not explain.
When I use the following line in the snmpd.conf file:
notificationEvent SupplyVoltage 1.3.6.1.4.1.33302.10.6.1 -n
/man/snmpd.conf.html
Regards,
Richard
-Original Message-
From: dave.shi...@googlemail.com [mailto:dave.shi...@googlemail.com] On Behalf
Of Dave Shield
Sent: Friday, 8 May 2009 8:47 PM
To: Richard Gipps
Cc: net-snmp-users@lists.sourceforge.net
Subject: Re: SNMP V1 traps
2009/5/8 Richard
Hi,
I would like to use net-snmp to send V1 snmp traps. The neat
monitor facility in snmpd works great for V2c but does not seem appropriate for
V1 as it relies on types (macros) defined in SMI-V2 such as NOTIFICATION-TYPE
to generate the correct information for the trap. Is
2009/5/8 Richard Gipps richa...@triodatacom.com:
The neat
monitor facility in snmpd works great for V2c but does not seem appropriate
for V1 as it relies on types (macros) defined in SMI-V2 such as
NOTIFICATION-TYPE to generate the correct information for the trap.
Please read the FAQ
Hi,
Is it mandatory to enter something in the community string field? Can it be of
zero length?
If yes, then is there any default value that will be used or is it left to the
developer to decide?
No task is so humble that it does not offer an outlet for individuality
2009/4/8 Tanisha Kashyap tanisha.kash...@aricent.com:
Is it mandatory to enter something in the community string field?
The structure of an SNMP request is fixed.
Community-based SNMP requests *must* include a community
string in the appropriate place.
Can it be of zero length?
In principle,
) for management traffic.
The problem is the agent-addr field in the SNMP v1 traps. It is
sending the IP address of the data interface, bond0. This is causing
issues with the network management software, which cannot associate the
IP address with a defined management address. After some testing I have
found
