Dear Team
Please support to provide alarm description for below OID
1.3.6.1.4.1.8072.3.2.10
appeared over storage p2000 base SPA..
Regards
Adarsh Mehta
+91 9780009461
___
Net-snmp-coders mailing list
Net-snmp-coders@lists.sourceforge.net
https://lists.
Hi,
Currently we employ net-snmp-5.7.2. Bit of googling revealed that the SHA
implemented by the agent is HMAC-SHA-96.
What version of snmp supports greater HMAC-SHA-256 and greater?
Further, a new user is added with the following step:
createUser testUser SHA "test123" AES
Is there a possibil
On 9/5/19 10:58 PM, Thommandra Gowtham wrote:
> - How can we get more information in a logmatch trap other than the
> pattern matched?
Making your pattern match more text should do the trick. For example:
logmatch loginFailure /var/log/auth.log 30 Failed password for .*
BTW, this kind of questi
"Adolf Misquith (amisquit) via Net-snmp-coders"
writes:
> What version of snmp supports greater HMAC-SHA-256 and greater?
5.8 :-)
> Further, a new user is added with the following step:
>
> createUser testUser SHA "test123" AES
>
> Is there a possibility to configure HMAC-SHA-224/256/384/512
On Thu, Sep 05, 2019 at 04:14:24PM +0530, MAD GAMING wrote:
> Dear Team
> Please support to provide alarm description for below OID
>
> 1.3.6.1.4.1.8072.3.2.10
>
> appeared over storage p2000 base SPA..
You did not provide much information to work with but I'd guess the system
that generated the
Jeff,
Thanks for your reply.
It was a deliberate mail to net-snmp-coders. Because, I knew about the
pattern matching but that would not suffice because we get a trap like
below when we give a '.*' in pattern
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (3022) 0:00:30.22
SNMPv2-MIB::snmpTrapO
