No reponse from SNMP agent - Poll -> Configuration

[Matthew-Beckett]

Hi,

I have a Cisco Nexus 9K switch which I am trying to monitor via SNMP, however, despite configuring a proxy in Properties > Communications > SNMP and setting the community string. Running Poll > Configuration throws the error "No response from SNMP agent"

To test this is working, I connected to the proxy node installed SNMPWalk and hit the Nexus with the same community I put in NetXMS and that worked instantly.

Thanks,
Matt

[Filipp Sudanov]

Is EnableSNMPProxy=yes set in agent's configuration file?

If this is set, try collecting agent log on debug level 6 at the moment when you perform configuration poll from the server.

[Matthew-Beckett]

Hi Filipp,

I am still encountering the same issue

[28.05.2021 11:36:20] Checking node's capabilities...
[28.05.2021 11:36:20]    Checking NetXMS agent...
[28.05.2021 11:36:20]    Cannot connect to NetXMS agent (Connect failed)
[28.05.2021 11:36:20]    Checking SNMP...
[28.05.2021 11:36:20]    No response from SNMP agent
[28.05.2021 11:36:20]    Checking EtherNet/IP...
[28.05.2021 11:36:20]    Cannot establish EtherNet/IP connection or get device identity (COMMUNICATION ERROR)
[28.05.2021 11:36:20] Capability check finished
[28.05.2021 11:36:20] Checking interface configuration...
[28.05.2021 11:36:20] Unable to get interface list from node
[28.05.2021 11:36:20] Interface configuration check finished
[28.05.2021 11:36:20] Checking node name
[28.05.2021 11:36:20] Node name cannot be interpreted as valid IP address, no need to resolve to host name
[28.05.2021 11:36:20] Updating general system hardware information
[28.05.2021 11:36:20] Processing template autoapply rules
[28.05.2021 11:36:20] Processing container autobind rules
[28.05.2021 11:36:21] Processing cluster autobind rules

[Zebble]

Are you able to poll other SNMP nodes through the same agent/proxy?

Have you done a "tcpdump port 161" on the agent while attempting the poll to ensure there is expected traffic?

If you're running selinux or something equivalent on the agent/proxy?  You might want to disable it and try again to see if this is the cause.

-Zeb