Hi,
I too have the same problem. However, in my case, I changed Net-SNMP
5.1.2 (from the Centos 4.3 distribution) to 5.4rc2. No other changes
happened on the system,
so it's unlikely to be a DNS problem. I'm running snmptrapd to perl
programs like so:
traphandle
COLUBRIS-CLIENT-TRACKING-MIB::clientTrackingSuccessfulAuthentication.0.1
/iHotel/server/bin/snmp/association
traphandle
COLUBRIS-CLIENT-TRACKING-MIB::clientTrackingSuccessfulAssociation.0.1
/iHotel/server/bin/snmp/association
traphandle SNMPv2-SMI::enterprises.8744.5.6.2.0.4
/iHotel/server/bin/snmp/heartbeat
here is an example:
main-west-bowman
24.57.195.185
SNMPv2-MIB::sysUpTime.0 5:10:38:38.23
SNMPv2-MIB::snmpTrapOID.0
COLUBRIS-CLIENT-TRACKING-MIB::clientTrackingSuccessfulAssociation.0.1
COLUBRIS-CLIENT-TRACKING-MIB::clientTrackingEventInformation (2006-11-14
13:58:09) wvlan0 Free Internet 00:15:00:1C:56:5B Wireless Association
Success
<UNKNOWN>
UDP: [24.57.195.185]:32777
DISMAN-EVENT-MIB::sysUpTimeInstance 5:10:49:43.24
SNMPv2-MIB::snmpTrapOID.0
COLUBRIS-CLIENT-TRACKING-MIB::clientTrackingSuccessfulAuthentication.0.1
COLUBRIS-CLIENT-TRACKING-MIB::clientTrackingEventInformation (2006-11-14
14:09:14) wvlan0 Free Internet 00:13:CE:2E:D0:7A Wireless Authentication
Success
Here are the exact same entries from snmptrapd.log: (note that the
reverse lookup is different in the both cases.... what's up here?)
2006-11-14 12:56:57 d57-195-185.home.cgocable.net [24.57.195.185]:
SNMPv2-MIB::sysUpTime.0 = Timeticks: (47031823) 5 days, 10:38:38.23
SNMPv2-MIB::snmpTrapOID.0 = OID:
COLUBRIS-CLIENT-TRACKING-MIB::clientTrackingSuccessfulAssociation.0.1
COLUBRIS-CLIENT-TRACKING-MIB::clientTrackingEventInformation = STRING:
(2006-11-14 13:58:09) wvlan0 Free Internet 00:15:00:1C:56:5B Wireless
Association Success
2006-11-14 13:08:01 d57-195-185.home.cgocable.net [24.57.195.185]:
SNMPv2-MIB::sysUpTime.0 = Timeticks: (47098324) 5 days, 10:49:43.24
SNMPv2-MIB::snmpTrapOID.0 = OID:
COLUBRIS-CLIENT-TRACKING-MIB::clientTrackingSuccessfulAuthentication.0.1
COLUBRIS-CLIENT-TRACKING-MIB::clientTrackingEventInformation = STRING:
(2006-11-14 14:09:14) wvlan0 Free Internet 00:13:CE:2E:D0:7A Wireless
Authentication Success
These two entries are just minutes apart. The only change was switching
the version of Net-SNMP. Note also that the sysUpTimeInstance is now
reported from the DISMAN mib, not the SNMPv2 mib. The config files
(snmp.conf,snmpd.conf, and snmptrapd.conf are unchanged from the
previous version).
In 5.1.2, if the ip address could not be looked up, it just appeared in
both places. I have other examples:
10.81.0.37
10.81.0.37
SNMPv2-MIB::sysUpTime.0 0:1:07:26.14
SNMPv2-MIB::snmpTrapOID.0
COLUBRIS-CLIENT-TRACKING-MIB::clientTrackingSuccessfulAssociation.0.1
COLUBRIS-CLIENT-TRACKING-MIB::clientTrackingEventInformation (2006-11-14
06:22:54) wvlan0 00:14:A5:81:E7:22 Wireless Association Success
The change to <UNKNOWN> and the format change for the source address
from just an address to the UDP [...]:xxxx form are significant in that
we have to modify our code now to fit.
begin:vcard
fn:Mike Schmidt
n:Schmidt;Mike
org:Intello Technologies Inc.
adr;quoted-printable;quoted-printable:;;580 1=C3=A8re Rue;Saint-Jean-sur-Richelieu;Qu=C3=A9;J2X 3B4;Canada
email;internet:[EMAIL PROTECTED]
title:Vice-President
tel;work:450-358-2266 x223
tel;cell:514-835-9497
x-mozilla-html:FALSE
url:http://www.intello.com
version:2.1
end:vcard
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Net-snmp-users mailing list
Net-snmp-users@lists.sourceforge.net
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users
