Synology connectivity issue

xsalvia

Hi all,
Recently upgraded to 


Created reference in GUI as per documentation, amd executed the connectivity from GIU

Thu Mar 11 12:45:11 2021: Got Timeout querying xx.xx.xx.xx:161 with xxxxxxxx for sysName. /home/lpar2rrd/stor2rrd/bin/SNMP_lib.pm:1001 : 
/usr/bin/snmpwalk -v 2c -c xxxxxxxx xx.xx.xx.xx .1.3.6.1.2.1.1.5.0
SNMP version  : 2c (default)
Port          : 161 (default)
Timeout       : 5 seconds
Community     : xxxxxxxxx
STATE         : NOT CONNECTED!

The device is populating in the Gui, but Pool, performance, etcetera, are empty.
Please there is any workaround to resolve?
Already applied deviceconntest.pm workaround without success

STOR2RRD version 7.00 to be able to review capacity for Synology. DSM version is higher than requirement.
After perform connectivity test:		perl /home/stor2rrd/stor2rrd/bin/conntest_udp.pl xx.xx.xx.xx 161	UDP connection to "xx.xx.xx.xx" on port "161" is ok

Pavel

Hi,

1. enable SNMP on the storage as per dpocu: https://stor2rrd.com/Synology-monitoring.php

2. is this working?

 perl /home/stor2rrd/stor2rrd/bin/conntest_udp.pl <your IP> 161

xsalvia

Thanks, 
1.- Yes, It's enabled. The only difference as it's different community, as is was defiined for other purposes. I tried temporary change to "public" without success.
2.- Yes, conntest_udp.pl is working. What is not working is the API Authorization
3.- I have more than 30 devices, so I just started with 7, all with the same issue.

Pavel

test snmpwalk, but it will time out

/usr/bin/snmpwalk -v 2c -c xxxxxxxx xx.xx.xx.xx .1.3.6.1.2.1.1.5.0

try this as well

/usr/bin/snmpwalk -v 2c -c xxxxxxxx xx.xx.xx.xx .1.3.6.1.2.1.1

what SNMP do you have enabled on the storage, just 1 and 2c? Try disable 3

xsalvia

Thanks again
Found 2 issues.
Command fails as per current community ends with "&".
Changed to public temporarily and got Timeout message.

Timeout: No Response from XXXXX

But the conntest_udp shows good. What can be causing that timeout? Not found any additional port to be opened as per doc

xsalvia

And not V3 enabled in that system.

Pavel

log a call with the vendor like "SNMP is not working"

xsalvia

Sure, as there is a connectivity stopper.
Once have answer from vendor will be updating the resolution