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
 
- 2,144 Views
 
- Mark as New
 - Bookmark
 - Subscribe
 - Mute
 - Subscribe to RSS Feed
 - Permalink
 - Report Inappropriate Content
 
08-11-2020 04:41 AM
- Mark as New
 - Bookmark
 - Subscribe
 - Mute
 - Subscribe to RSS Feed
 - Permalink
 - Report Inappropriate Content
 
08-11-2020 06:04 AM
thanks. I've looked at this. The challenge is that the class Citrix Netscaler is already on the sys_choice table and we've already got an SNMP mapping discovery command where Citrix Netscaler is on Operating System Class Name list. So even with that, I still get the same error! Any ideas?
- Mark as New
 - Bookmark
 - Subscribe
 - Mute
 - Subscribe to RSS Feed
 - Permalink
 - Report Inappropriate Content
 
08-16-2020 11:59 AM
Hi,
How you where doing service mapping? Traffic based or tag based.
Thanks,
Ashutosh
- Mark as New
 - Bookmark
 - Subscribe
 - Mute
 - Subscribe to RSS Feed
 - Permalink
 - Report Inappropriate Content
 
08-17-2020 08:07 AM
Hi, it's pattern-based discovery. I've started to notice this issue now happening on other load balancers (that used to show up perfectly fine on the map, but now have this error)
