SNMP credential passes / Shazzam doesn't see 161

[Ronald Lucas]

Using Istanbul...

Strange issue here.   When testing an SNMP credential against an IP, the credential test passes which also confirms port 161 is open between the MID server host and the target IP.   Also, using the command line utility "snmpget" on the MID server host to the target IP also confirms port 161 is open using the same SNMP community string as I'm able return a value for sysName.

However, during the Shazzam phase of discovery on that same IP from the same MID server host, there is no response on port 161 in the XML payload.  

Any suggestions on how I can troubleshoot this further?

Thanks,

Ron

[bernyalvarado]

You're right. That's odd!

[bernyalvarado]

I hope this helps!

[tim_broberg]

Can you wireshark or tcpdump the traffic between the mid and the target system and see if the mid ever starts talking to the target and to what extent the target replies?

[ravinder2601]

Hi Ron, hope the issue is resolved, can you please help with solution on this.

Thanks in advance !

[bhanupratap2203]

Hi Ravinder,

did you find anything here. We are on Orlando and have same issue intermittently. The same discovery schedules discovers the network CI for couple of days and then in next scheduled discovery, it stops getting response on port 161. We found that when it is not working for 161, MID Server is also not communicating with DNS Server in our infra. we reset the VM NIC and it starts working again. Not sure whats wrong in here.

Please suggest your thoughts and findings about this issue.