Monitor inodes

[DOLPHIN168]

Hi,

Is there a way to monitor inodes instead of login manually to check via SSH?

Thanks in advance

[rh]

Two suggestions for you:

1. if you have a DFM (OnCommand Unified Manager) server, you can set up an alarm there to (eg) email you when either the inode almost full or inode full thresholds is passed.
2. you could run a PowerShell script to report on the inode usage. For example, something like this would generate a list of volumes sorted in descending order of % inode usage (ie the ones shown first are the ones with the highest usage)

Connect-NaController -Name ACONTROLLER -Credential (Get-Credential)

Get-NaVol | select-object Name,@{Name="pcInodesUsed"; Expression={(100*$_.FilesUsed) / $_.FilesTotal}} | sort-object -descending pcInodesUsed | fl

NB: To make this watertight, you'd have to handle the case of an empty volume which would cause a zero divide in the above.

Regards,

Richard.

[DOLPHIN168]

Hi,

Is there other way besides DFM?

Is it chagreable for DFM? How to go about setting up a DFM?

[rh]

The DFM server software is a free download but you will need a licence key to install it. The key is free -- just contact your NetApp account manager.

Once you have it in place, you create an account on the NetApp side which is used to poll the filer. To make alerts happen more quickly, you can also send SNMP traps from the filer(s) to the DFM server.

If you have clustered ONTAP, there is a newer version (6.x series) for that with a greatly improved user interface BUT no reporting capability so start with the 5.X series of releases.

Regards,

Richard.

[Kannan_DWA]

How to do for CDOT volumes?

---

@DOLPHIN168 wrote:

Hi,

Is there a way to monitor inodes instead of login manually to check via SSH?

Thanks in advance

---

[yannb]

For cDOT volumes, to get the inodes count you can use one of the following methods :

- SSH to the cluster and run df -i

- Query the OCUM MySQL database with traditional MySQL client/APIs

- Use REST APIs with NetApp API services (untested myself but according to the documentations it should be here)