Search Exchange
Search All Sites
Nagios Live Webinars
Let our experts show you how Nagios can help your organization.Login
New ListingsDirectory Tree
Symantec 5220 Disk Appliance
Current Version
1.0
Last Release Date
2012-04-02
Compatible With
- Nagios 3.x
- Nagios XI
Owner
Website
License
GPL
Hits
41315
Files:
| File | Description |
|---|---|
| check_nbu_app_load.sh | Load Average |
| check_nbu_app_mem.sh | RAM Stats |
| check_nbu_app_procs.sh | Number of Processes |
| check_nbu_app_puredisk.sh | PureDisk Space (/disk Mount) |
| check_nbu_app_swap.sh | Swap Stats |
These plugins were written as a way to monitor various metrics on the appliance that Symantec doesn't appear to offer anywhere else.
These plugins were written using ssh keys so that passwords don't need to be stored in the plugin.
Since Symantec doesn't give us direct access to the Linux shell on the appliance, I found a way to force some SSH keys into the device and it will use them.
NOTICE: Latest firmware (2.5.3) has broken the plugin's ability to submit commands via SSH. I no longer have access to an appliance to work around this.
These plugins were written as a way for us to monitor various metrics on the machine that Symantec doesn't appear to offer anywhere else.
These plugins were written using ssh keys so that passwords don't need to be stored in the plugin.
Since Symantec doesn't give us direct access to the Linux shell on the appliance, I found a way to force some SSH keys into the device and it will use them.
I won't detail here how to generate the keys or how they work, Google is your friend here. Once you have the public key string available:
$ ssh admin@nbuappliance "echo INSERT PUBLIC KEY HERE >> ~/.ssh/authorized_keys"
NOTE: "admin" is the account you setup during the initial setup of the appliance and is the only account you can login with.
Once the public key is in place, you need to alter the private key file location in the scripts.
After that you should be able to run the scripts as the Nagios user and you should get data back.
In my case, I had a 5220 with a 24TB expansion drawer. 100% of the disk was dedicated to de-duplication, we did not use Advanced Disk. This might cause a problem with the plugin but at this time I have no way to test out the various scenarios.
These plugins were written as a way for us to monitor various metrics on the machine that Symantec doesn't appear to offer anywhere else.
These plugins were written using ssh keys so that passwords don't need to be stored in the plugin.
Since Symantec doesn't give us direct access to the Linux shell on the appliance, I found a way to force some SSH keys into the device and it will use them.
I won't detail here how to generate the keys or how they work, Google is your friend here. Once you have the public key string available:
$ ssh admin@nbuappliance "echo INSERT PUBLIC KEY HERE >> ~/.ssh/authorized_keys"
NOTE: "admin" is the account you setup during the initial setup of the appliance and is the only account you can login with.
Once the public key is in place, you need to alter the private key file location in the scripts.
After that you should be able to run the scripts as the Nagios user and you should get data back.
In my case, I had a 5220 with a 24TB expansion drawer. 100% of the disk was dedicated to de-duplication, we did not use Advanced Disk. This might cause a problem with the plugin but at this time I have no way to test out the various scenarios.
Reviews (0)
Be the first to review this listing!
