Discovery / Service Mapping error: All command implementations (SNMP_TABLE) failed on host [IP Address]. Host might be down or unreachable.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-11-2020 04:21 AM
Hi team,
I've got the following error on one of our service maps; All command implementations (SNMP_TABLE) failed on host 192.168.254.53. Host might be down or unreachable.
The map was correctly populated and complete. I hit Run Discovery to get the latest data. Once done, all components disappeared and I was left with the entry point and load balancer. The application team confirmed there was no change to the entry point or load balancer of this service and yet I am no longer able to map its component. Could you please help with what needs to be done to resolve this error:All command implementations (SNMP_TABLE) failed on host 192.168.254.53. Host might be down or unreachable.
- Labels:
-
Discovery
-
Service Mapping
- 1,884 Views

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-17-2020 08:21 AM
Hi,
Is there something changed on your network?
What happens when you debug the patterns used for this mapping?
Thanks,
Ashutosh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-17-2020 08:54 AM
No changes. the load balancers are up and running. When I debug the pattern, it fails getting SNMP table
all commands failed on host:.... command type: SNMP_TABLE. command track: SnmpTableCommand\(Relevant),; input:
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-21-2020 07:49 PM
Were you ever able to resolve this issue, i'm seeing something similar.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-22-2020 11:08 AM
What worked for me most of the cases was running Hz discovery on the host i.e. the load balancer itself not the load balancer service, and then running top down discovery on the map again. That seemed to work for me.