Perform Ping before SNMP scan

Completed

Kris Pederson

• July 29, 2015 17:51

It would be nice if the SNMP scan tool would perform a ping to ensure a device is reachable before attempting to SNMP poll it. I noticed the SNMP scan takes a long time due to multiple unreachables within a given subnet.

 

Also noticed if you ping sweep a subnet and then also perform an SNMP scan on it, both entries show up in the device database separately. This could be perhaps because the DNS does not match the hostname (FQDN vs short name) and therefore creates two entries. Assuming the IP is the same, duplicates should not occur.

Thanks,

Kris

4

• Official comment

  

  Raj Jalan

  • April 29, 2017 03:23

  We have added this option in v13.1.1 for SNMP jobs.

  
• 

  Christian Bryndum

  • October 28, 2015 17:28

  Being able to ping and telnet from the CLI would be very beneficial too.

  0
• 

  Jose Rivera

  • November 03, 2015 18:57

  This will be in a near future release. Thank you for subscribing to this feature.

  0
• 

  Hervé Bernier

  • January 06, 2016 07:36

  ping / telnet from the CLI is a very good idea.
  Having the ability to add other type of access would be nice (http(s), ssh, mstsc, ...).

  No need to implement all these process inside Device42, but simply calling an external software like putty for example for telnet / ssh, or IE/Chrome/Firefox/... for http(s)

  With passwords centralized in Device42, no more need of other password manager

  0
• 

  REDI TECH

  • January 28, 2016 16:01

  When is this planned?  

   

  My SNMP scans are unbearably slow that would be fixed by a quick telnet or ping.I also noticed SNMP version 1 is used even when you select version 2.  I noticed this in the log, it may be a scan that can be eliminated.

  0
• 

  REDI TECH

  • February 09, 2016 16:04

  I'd also like to mention that possibly allowing users to shrink/edit timeouts for scans could also help this issue as well.

  0
• 

  REDI TECH

  • March 02, 2016 17:45

  Jose mentioned in November that this is set for a near future release.  How far away is this?  In Device42, my scans just take way too long(/23 networks take 2-3 hours).  In the Windows autodiscovery tool, I experience memory leaks because of the inefficient scanning.

  0
• 

  Raj Jalan

  • March 02, 2016 18:07

  Hi Ryan,

  Jose mentioned the ping/telnet from the CLI - which we have added in the appliance manager.

  Regarding ping before SNMP - it is on the list and hasn't been addressed yet.

  Regarding windows tool - we are almost done with a complete re-write of that tool, which will offer better memory management along with other enhancements.

  Thanks & Regards,

  Raj

  0
• 

  REDI TECH

  • March 17, 2016 19:48

  Is the Windows rewrite apart of the latest version 9.6.0 that you have on your website currently?

  0

Please sign in to leave a comment.