Perhaps I am using things wrong but I seem to be having problems with my
USM users if I change the systems engineID.
If I use snmpusm to add users to the system and then stop snmpd I can
see that the users exist in the /var/net/snmpd.conf file and if I
restart snmpd I can still access the system
the USM, VACM, TARGET and
SNMP framework are loosely coupled.
Jeff
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Dave Shield
Sent: Tuesday, May 08, 2007 2:37 PM
To: Miller, Jeff (eng)
Cc: net-snmp-users@lists.sourceforge.net
Subject: Re: USM engineID
I am wondering if I am missing something with v3 trap/informs in 5.3.1
and 5.4. In particular, is there a security name collision between the
local snmpd and the remote snmptrapd?
If I want to configure snmpd to send informs with security I use a
trapsess configuration command like this:
the security name and this fails
because the security name has the remote engineID.
Jeff
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Dave Shield
Sent: Monday, May 07, 2007 10:15 AM
To: Miller, Jeff (eng)
Cc: net-snmp-users@lists.sourceforge.net
Subject: Re
Jeff 2. I observed that when configuring trapsess with -A and -X that
the
Jeff configuration does not persist. There is no persistence for the
Jeff target address or for the security parameters associated with the
Jeff target address.
Dave I don't quite follow.
Dave The agent will read the
or destroying more filters the agent sometimes returns
to filtering but usually is unable to locate any filters. If I
restart snmpd everything works again. Very strange.
Jeff
-Original Message-
From: Miller, Jeff (eng)
Sent: Thursday, March 15, 2007 4:32 PM
To: 'net-snmp-users
I can do a snmpget of the various scalars in ip, tcp, etc but when I try
to do an snmpget or snmpwalk across those objects the system skips them
entirely and goes on to the first table entry. Why is this?
I see that the ip, tcp, icmp, etc groups are implemented using a
Title: Walking notification-log-mib when it is in snmpd
I compiled the 5.3 release with the notification-log-mib in snmpd (as opposed to running it in snmptrapd).
When I start and turn on debugging I can see that notification_log is initialized and that events are going into it. However,
Title: Walking notification-log-mib when it is in snmpd
I compiled the 5.3 release with the notification-log-mib in snmpd (as opposed to running it in snmptrapd).
When I start and turn on debugging I can see that notification_log is initialized and that events are going into it. However,
