Home Directory Plugins Hardware Storage Systems SAN and NAS IBM San Volume Controller Check IBM Storwize V7000 Unified / SONAS Replication

Search Exchange

Search All Sites

Nagios Live Webinars

Let our experts show you how Nagios can help your organization.

Contact Us

Phone: 1-888-NAGIOS-1
Email: sales@nagios.com

Login

Remember Me

Directory Tree

Check IBM Storwize V7000 Unified / SONAS Replication

Rating
0 votes
Favoured:
0
Current Version
1.0
Last Release Date
2016-06-15
Compatible With
  • Nagios 3.x
  • Nagios 4.x
Owner
License
MIT
Hits
5437
Files:
FileDescription
check_sonas_repl.shcheck_sonas_repl.sh
Nagios CSP

Meet The New Nagios Core Services Platform

Built on over 25 years of monitoring experience, the Nagios Core Services Platform provides insightful monitoring dashboards, time-saving monitoring wizards, and unmatched ease of use. Use it for free indefinitely.

Monitoring Made Magically Better

  • Nagios Core on Overdrive
  • Powerful Monitoring Dashboards
  • Time-Saving Configuration Wizards
  • Open Source Powered Monitoring On Steroids
  • And So Much More!
This bash script checks the status of the last replication task of an IBM Storwize V7000 Unified / SONAS system.
If the last replication for the given filesystem was unsuccessful, then the time at which the last successful replication completed is reported as well.

The actual code is managed in the following GitHub rebository - please use the Issue Tracker to ask questions, report problems or request enhancements.
https://github.com/acch/nagios-plugins

The script requires SSH Public Key Authentication for connecting to the Storwize V7000 Unified / SONAS system. SSH Public Key Authentication needs to be set up first, before running the script. To test your SSH configuration, try to login to Storwize V7000 Unified / SONAS via SSH from the Nagios server as the Nagios user - if this works without prompting you for a password you seem to have properly configured Public Key Authentication. If you get a "Permission denied" error when running the script, the most likely reason for that is Public Key Authentication not being configured correctly for the Nagios user (by default called 'nagios').

It is strongly recommended to create a dedicated read-only Storwize V7000 Unified / SONAS user to be used by this script. This eases problem determination, allows for proper audit tracing and helps avoiding undesired side-effects. Also, it eliminates the risk of script errors having an impact on your actual production environment...

To create a read-only user 'nagios' with password 'secret' on Storwize V7000 Unified / SONAS, run the following commands as the Nagios operating-system user (by default called 'nagios', too):
# ssh admin@ mkuser nagios -p secret -g Monitor
# ssh admin@ chuser nagios -k "`cat ~/.ssh/id_rsa.pub`"
Note that you may need to modify the last command to point to the actual location of your SSH public key file used for authentication