Discovery progress running long

If this walks still will slow, disable arp module.. and other non required modules.
from the side of the observium, there is no way to speed it up any more.

it seems device have snmpwalk troubles.. you can experimenting with SNMP Max-Repetition values by self, like:

time snmpbulkwalk -Cr100 -v2c -c <community> -m IP-MIB -M /opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp va-sw01 ipNetToMediaPhysAddress

Try different -Cr values, like 100/80/60/etc.. if you found any value when snmpwalk respond faster, set this values in device edit page, snmp tav (Max-Repetition)

While I run the below command

time snmpwalk -t '5' -v2c -c *** -m IP-MIB -M /opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp 'udp':'va-sw01':'161' ipNetToMediaPhysAddress 

and I observed the snmpwalk is running for hours, then I manually ended the execution and I got the following response
real 153m39.489s
user 0m0.318s
sys 0m0.282s

yah, this is expected snmpwalk times..

CMD[/usr/bin/snmpbulkwalk -t '5' -v2c -c *** -Pud -OQUs -m ENTITY-MIB:CISCO-ENTITY-VENDORTYPE-OID-MIB -M /opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp:/opt/observium/mibs/cisco 'udp':'va-sw01':'161' entPhysicalEntry]

CMD RUNTIME[463.2321s]

CMD[/usr/bin/snmpbulkwalk -t '5' -v2c -c *** -Pud -OXqs -m IP-MIB -M /opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp 'udp':'va-sw01':'161' ipNetToMediaPhysAddress]

CMD RUNTIME[392.858s]

and some others...

Try run same commands without bulk commands, ie:

time snmpwalk -t '5' -v2c -c *** -m IP-MIB -M /opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp 'udp':'va-sw01':'161' ipNetToMediaPhysAddress

use your valid community string.

check runtime after command.
It it faster than 300 sec, set device snmp max-repetition time to 0 (in device edit page).
this disable all bulkwalks for device.

attached discovery debug

The overview of the device is added. How to get the screenshot of device performance ? If you can provide the navigation path, that will be helpful. 
I will provide the discovery debug attachment once the process is complete. 

Need more information about device and discovery:

• screenshot device overview page
• screenshot device performance data

Ideally if you can make and attach discovery debug (wait until done for 3 hours):

./discovery.php -d -h <device>

Another discovery.php process (PID: 3263471, UID: 0, STARTED: Sun, 30 Apr 2023 12:45:01 +0000) already running for device va-sw01 (196).

1. 1. 1. 1. 1. Finished discovery run at 2023-04-30 13:12:46 #####

General questions and device support can be discussed in our Discord channel, click here to join.

Please make and attach additional information about the device:

• full snmp dump from device:

  snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -Ih -ObentxU <hostname> .1 > myagent.snmpwalk

  snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -Ih -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalk

  If device not support SNMP version 2c, replace -v2c with -v1.

• If you have problems with discovery or poller processes, please do and attach these debugs:

  ./discovery.php -d -h <device>

  ./poller.php -d -h <device>

• additionally attach device and/or vendor specific MIB files

This comment is added automatically.