Shazzam probe not checking port 161

[Community Alums]

Trying to troubleshoot why some firewalls are not being discovered when I noticed in the shazzam input discovery log for two devices (same model) the probe is not checking port 161.  It does check 161 on other devices including firewalls, this is the first time I've seen this issue. Our environment is pretty much OOB, there have been no customizations in the discovery space outside from custom patterns and classifiers. Any idea why the Shazzam probe wouldn't check 161 for these devices specifically?

[Runjay Patel]

Hi @Community Alums ,

 I don’t think issue is from discovery end, ask your network team to check that 161 port enable or not or there is any restrictions placed for that device.

[Community Alums]

Hi Runjay,

If 161 is not enabled, I should at least be getting a response saying it was unresolved. I'm not getting a response at all, so even if the network team confirms 161 is open I'm thinking it won't matter, because it's not testing 161 on these devices for some reason. I'm fairly certain I've seen the errors before of 161 being closed, because I've worked with my network team on a few devices and was able to direct them to open the port because of the errors. In this case, there is nothing indicating any response around 161.

Miranda

[pratik0306]

what is displayed in the logs section for these IPs? It would state an error relating to the Port which means it did not see anything on 161.

[Community Alums]

That's the weird thing, there is nothing in the logs about port 161 response. I've seen the errors before, and they still come across on other devices if allowed or denied. Its just this specific device there is nothing in the logs about 161 except in the parameters on sending it, so I don't think it's even testing 161