Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

WMI snmp provider: Bad AgentAddress value within snmpNotification

10 views
Skip to first unread message

Phil

unread,
Oct 14, 2009, 4:57:54 AM10/14/09
to
I experiment a notification Problem with wmi snmp provider, i called
it "Bad AgentAddress value within snmpNotification"
I there an know issue ?

here my context & scenario:
MACHINE1:
- 2 interface: 127.0.0.1 & 192.168.......
- windows snmp agent installed & configured to send trap to machine2
with public community

MACHINE2:
Windows2003 Service pack2 with ...wbem\snmpincl.dll 5.2.3790.3959
(srv03_sp2_rtm.070216-1710)
- 2 interface: 127.0.0.1 & 10.18.......
- network protocol analyzer (Wireshark) running to catch the snmp trap
- wbemtest running connected to Root/snmp/smir namespace, with
NotificationQuery: Select * from SnmpLinkupNotification where
__Class='SnmpLinkupNotification'

on machine1: restart snmp service (in order to create LinkUp trap)
on machine2: reception of 2 notifications (2 SnmpLinkupNotification
object)
network protocol analyzer (wireshark) I can see 3 trap (1 cold start &
2 LinkUp)

I compare between SnmpLinkupNotification object properties And snmp
trap frame from wireshark
all is good (example: community, timeStamp) appart from AgentAddress
property:
Indeed I received under Wbemtest for the 2 notifications: AgentAddress
= AgentTransportAddress = 10.18.....

I should have received under Wbemtest,
a first SnmpLinkupNotification object with AgentAdress = 127.0.0.1
a second SnmpLinkupNotification object with AgentAdress = 192.168.....
because I checked with wireshark that the right values (127.0.0.1 &
192.168.....) exist in variable embedded in snmp frame.

Note also:
I experiment the same Pb with XP SP2.
But there is No problem in case where agent & "snmp client" are on the
same network 10.18...., AgentAddress is filled with the Agent IP
address

thanks a lot for any kind of information

0 new messages