Re: engineIDType = ENGINEID_TYPE_NETSNMP_RND
Wes Hardaker <[email protected]>
| Newsgroups | gmane.network.net-snmp.user |
|---|---|
| Organization | Sparta |
| Message-ID | <[email protected]> |
>>>>> On Thu, 20 Aug 2009 20:50:11 +0530, sanjaykumar <[email protected]> said: s> Actually I am getting wrong engine TIME in wireshark capture s> I am reading the engine Time using the function s> "snmpv3_local_snmpEngineTime()" s> While I was debugging the code I had the some doubt, It might be s> engineType which affecting it. I'm not sure why wireshark would be having issues. It has nothing to do with the format of the EngineID though. Wireshark should be ambivalent about it. The important thing about EngineIDs is that: 1) they must be unique. A manager will get confused if two devices on the network contain the same ID. 2) if an engineID on a device changes, it's likely a running manager will get confused until it restarts. One of the whole reasons that Net-SNMP uses the engine ID type it does is to avoid conflicts that many of the other types of engineID creation schemes can run into. -- Wes Hardaker Cobham Analytic Solutions ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ 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