Switches, Hubs, and Modems
cancel
Showing results for 
Search instead for 
Did you mean: 

SNMP security access violation

A. Veenema
Occasional Visitor

SNMP security access violation

I have upgraded the software in my 2626-pwr switch from H10.38 to H10.45. In Procurve Manager the switch is not reachable anymore using SNMP (we use SNMPV3 only) and in the switch I get lots of "snmp: SNMP Security access violation from w.x.y.z" messages. If I downgrade the switch to version H_10_38 the problems disappear. In the softdoc I can't find any configuration-change I should perform. Can anyone give me advice ?
4 REPLIES
cenk sasmaztin
Honored Contributor

Re: SNMP security access violation

hi..
Release H.10.40 Enhancements
Release H.10.40 includes the following enhancement.
â   Enhancement (PR_1000428642) â SNMP v2c describes two different notification-type
PDUs: traps and informs. Prior to this software release, only the traps sub-type was
supported. This enhancement adds support for informs.
Send SNMP v2c Informs
Enabling and Configuring SNMP Informs
You can use the snmp-server informs command (SNMPv2c and SNMPv3 versions) to send notifications
when certain events occur. When an SNMP Manager receives an informs request, it can send an SNMP
response back to the sending agent. This lets the agent know that the informs request reached its
destination and that traps can be sent successfully to that destination.
Informs requests can be sent several times until a response is received from the SNMP manager or
the configured retry limits are reached. The request may also timeout.
To enable SNMP informs, enter this command:
To configure SNMP informs request options, use the following commands.
To specify the manager that receives the informs request, use the snmp-server host command.
Syntax: [no] snmp-server enable informs
Enables or disables the informs option for SNMP.
Default: Disabled
Syntax: [no] snmp-server informs [retries] [timeout] [pending ]
Allows you to configure options for SNMP informs requests.
retries: Maximum number of times to resend an informs request. Default: 3
timeout: Number of seconds to wait for an acknowledgement before resending the
informs request. Default: 30 seconds
pending: Maximum number of informs waiting for acknowledgement at any one
time. When the maximum configured number is reached, older pending informs
are discarded. Default: 25
Syntax: snmp-server host < ip-address >[] [version <1 | 2c | 3>]< community-string >
113
Enhancements
Release H.10.40 Enhancements
You can see if informs are enabled or disabled with the show snmp-server command as shown in Figure
42.
Using community name and destination IP address, this command
designates a destination network-management station for receiving SNMP
event log messages from the switch. If you do not specify the event level,
then the switch does not send event log messages as traps. You can specify
up to 10 trap receivers (network management stations).
Note: In all cases, the switch sends any threshold trap(s) or informs to the
network management station(s) that explicitly set the threshold(s).
[traps | informs>]
Select whether SNMP traps or informs are sent to this management station.
For more information on SNMP informs, see â Enabling and Configuring
SNMP Informsâ on page 112.
[version <1 | 2c | 3>]
Select the version of SNMP being used.
Note: SNMP informs are supported on version 2c or 3 only.
[]
Options for sending switch Event Log messages to a trap receiver. The levels
specified with these options apply only to Event Log messages, and not to
threshold traps.

good luck.
cenk

Matt Hobbs
Honored Contributor

Re: SNMP security access violation

This has been fixed in H.10.52 and onwards. You'll need to contact HP support to get this version or later.
A. Veenema
Occasional Visitor

Re: SNMP security access violation

I have contacted HP Support with a request for H10.52, I'll let you know the outcome.

Regards, Auke.
A. Veenema
Occasional Visitor

Re: SNMP security access violation

I have had contact with support, but they told me H10.52 is not available for customers.
I have to wait, because in the next few months they expect a new software-version to be released, in which the problem is probably solved.

This is the service of HP !