Re: Problem Authorizing SHA notification
Wes Hardaker <[email protected]>
| Newsgroups | gmane.network.net-snmp.user |
|---|---|
| Organization | Sparta |
| Message-ID | <[email protected]> |
>>>>> "EM" == Erez Makavy <Makavy> writes: EM> 1) I checked and double checked the password I'm using (12345678) both in the agent and in the manager. EM> 2) I tried MD5 and it works (I receive the notification) Hmm... looks like you've certainly narrowed the problem down. You *did* configure the SNMPv3 user in the trap receiver to use SHA too right? EM> 1) Is there a chance that the MD5 vs. SHA authorization differs in EM> the way the engine ID is used? I guess there is no EM> difference,since with a sniffer I see that both MD5 and SHA EM> packets have the manager's engineID as the authorizing engine. no... there shouldn't be any differences there other than the algorithm that is called. EM> 2) Could it be a problem with "MGS-Soft MIB browser"? It's a EM> pretty solid application. And accessing the snmp agent with SHA EM> works well. It's the application receiving the traps too? If so, yes it could. The thing to try would be to set up our agent and our trap receiver and see if they get through. Then try our agent and another trap receiver and see if it gets through, then try the mg-soft one and see if that gets through... IE, narrow down where the problem is. -- Wes Hardaker Sparta, Inc. ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Net-snmp-users mailing list [email protected] Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users