How to monitor fileshare on NAS server

[Amit_Alone]

Hi All,

I'm looking for a way to monitor the fileshare which is present on NAS server. I went through many forums but none of them mention about fileshare monitoring. It would be very helpful if some one assist me on this.

SNMP is enable on the NAS server.

Using SNMP wizard I tried to monitor but all the services are in the CRITICAL state. Below is the command details.

Code: Select all

[root@avgdlnxvp126 ~]# /usr/local/nagios/libexec/check_snmp -H 10.140.167.26 -o '1.3.6.1.4.1.3076.2.1.2.17.1.7.0,1.3.6.1.4.1.3076.2.1.2.17.1.9.0' -C 'public' -P 2c -l 'Active Sessions' -w :70,:8 -c :75,:10 -t 90 -vvv
/bin/snmpget -Le -t 19 -r 5 -m '' -v 2c [context] [authpriv] 10.140.167.26:161 1.3.6.1.4.1.3076.2.1.2.17.1.7.0 1.3.6.1.4.1.3076.2.1.2.17.1.9.0
CRITICAL - Plugin timed out while executing system call

Code: Select all

[root@avgdlnxvp126 ~]# /usr/local/nagios/libexec/check_snmp -H 10.140.167.22 -o '1.3.6.1.4.1.3076.2.1.2.17.1.7.0,1.3.6.1.4.1.3076.2.1.2.17.1.9.0' -C 'public' -P 2c -l 'Active Sessions' -w :70,:8 -c :75,:10 -t 120

CRITICAL - Plugin timed out while executing system call

Community name is different. I have mention the default one here.

[ssax]

Does this work from an SSH session to the XI server? (leave the single-quotes around the community if you have special chars in yours)

Code: Select all

snmpwalk -v2c -c 'yourcommunity' 10.140.167.26 system

If it's still not returning anything it's either a firewall/security device blocking it, a wrong SNMP community, or SNMP is misconfigured on the remote device.

[Amit_Alone]

Hi Ssax,

I have run the suggested cmd on the terminal where Nagios is installed and didn't received any response.

Code: Select all

[e5613751@avgdlnxvp126 ~]$ snmpwalk -v2c -c '*************' 10.140.167.22 system
Timeout: No Response from 10.140.167.22
[e5613751@avgdlnxvp126 ~]$ snmpwalk -v2c -c 'public' 10.140.167.26 system
Timeout: No Response from 10.140.167.26
[e5613751@avgdlnxvp126 ~]$ snmpwalk -v2c -c '*************' 10.140.167.26 system
Timeout: No Response from 10.140.167.26
[e5613751@avgdlnxvp126 ~]$

I have convey the same stating that device is blocking the request. Then they have shared the attach image(NAS.jpg) and requested to share the details. I have provided the details and still we are observing the same.

[benjaminsmith]

Hi @Amit_Alone,

The screenshot is showing the configuration for SNMP traps, would you like to setup SNMP polling or SNMP traps for monitoring?

The timeout suggests that either the access is blocked in the setup or perhaps by a firewall. Try running the snmpwalk command using version 3 protocol and let me know if you get a valid response back.

Example command:

Code: Select all

snmpwalk -v3 -l authPriv -u testuser -a SHA -A "password" -x AES -X "password" <IPADDRESS>

Regards,
Benjamin

Documentation
SNMP Walk Wizard

[Amit_Alone]

Hi Benjamin,

Here is the o/p of the requested cmd.

Code: Select all

[e5613751@avgdlnxvp126 ~]$ snmpwalk -v3 -l authPriv -a SHA -A "************" -x AES -X "***********" 10.140.167.22
snmpwalk: Timeout
[e5613751@avgdlnxvp126 ~]$ ^C
[e5613751@avgdlnxvp126 ~]$ snmpwalk -v3 -l authPriv -a SHA -x AES 10.140.167.22
snmpwalk: Timeout
[e5613751@avgdlnxvp126 ~]$ snmpwalk -v3 -l authPriv -u e5613751 -a SHA -A "*************" -x AES -X "**************" 10.140.167.22
snmpwalk: Timeout
[e5613751@avgdlnxvp126 ~]$

[benjaminsmith]

Hi,

Hmm.. still getting a timeout, that likely cause is either the community string or the settings on the device. Let's back up and verify a few items.

1. Can you ping the device from Nagios XI?

Code: Select all

ping <ipaddress>

2. Does the community string match?

3. Verify incoming firewall rules for UDP 161 and 162 on the device.

4. Try to Increase timeout on SNMP walk command

Code: Select all

snmpwalk -v2c -c 'yourcommunity' 10.140.167.26 system -t 20

--Benjamin

[Amit_Alone]

Hi Benjamin,

Sorry for delay, below is the requested details.

1. Can you ping the device from Nagios XI?

Code: Select all

[root@avgdlnxvp126 ~]# ping 10.140.167.22
PING 10.140.167.22 (10.140.167.22) 56(84) bytes of data.
64 bytes from 10.140.167.22: icmp_seq=1 ttl=55 time=122 ms
64 bytes from 10.140.167.22: icmp_seq=2 ttl=55 time=119 ms
64 bytes from 10.140.167.22: icmp_seq=3 ttl=55 time=102 ms
64 bytes from 10.140.167.22: icmp_seq=4 ttl=55 time=101 ms
64 bytes from 10.140.167.22: icmp_seq=5 ttl=55 time=110 ms
^C
--- 10.140.167.22 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4004ms
rtt min/avg/max/mdev = 101.551/111.357/122.136/8.478 ms

2. Does the community string match?

Yes, it is correct

3. Verify incoming firewall rules for UDP 161 and 162 on the device.

Verified, Firewall rule is already present to allow this communication from Nagios machine. It is bi-directional allowed.

4. Try to Increase timeout on SNMP walk command

Tried increasing the time out but still it was showing the same.

Code: Select all

[root@avgdlnxvp126 ~]# snmpwalk -v2c -c '***************' 10.140.167.22 system -t 20
Timeout: No Response from 10.140.167.22
[root@avgdlnxvp126 ~]# snmpwalk -v2c -c '*******************' 10.140.167.22 system -t 90
Timeout: No Response from 10.140.167.22

[p4ben]

I've seen plenty of devices that support traps, but not polling. Have you checked documentation for the NAS?

[Amit_Alone]

Could you please share the link one which you have suggested.

[lmiltchev]

@p4ben, can you provide the link to the NAS documentation that you were referring to?

@Amit_Alone, I was looking at the screenshots that you provided and I only saw configuration options for traps, so p4ben could be correct by saying:

I've seen plenty of devices that support traps, but not polling.