ZenPack:IBM 3584
We want to update this ZenPack and need your help!
This ZenPack needs updating to run on the latest versions of Zenoss, and to update it, we need an SNMP walk of a live device. If you have this device in your datacenter, you can help! See Using snmpwalk for more information- Author(s)
- Josh Baird
- Current Maintainer(s)
- Josh Baird
- License
- GNU General Public License, Version 2, or later
- ZenPack name
- ZenPacks.community.IBM3584Mon
- More Information
- GitHub page/HomePage
- Link to more docs
- View Documentation
- Git sources (for cloning)
- Link
IBM 3584 ZenPack
Warning
The ZenPack Catalog has moved to its new home at https://www.zenoss.com/product/zenpacks as of January 17, 2017. The following information may be out of date, and this page will eventually be removed.
Support
This ZenPack is developed by the Zenoss user community and supported via our online forums. Zenoss, Inc. does not provide direct support for this ZenPack.
Background
This ZenPack provides monitoring and modeling support for the IBM TS3500/3584 Tape Library. Many thanks to Egor Puzanov for his generous help in building and testing this ZenPack. Without his help, his examples and time this ZenPack would not have been possible. Also, thanks to Eric Edgar for his examples and help.
Device Class
Upon installing the ZenPack a new device class named /Devices/Storage/IBM/TapeLibrary is created. Add your tape library device to this class.
Modeled Information
The following information is modeled from the 3584:
- zenoss.community.IBM3584Mon.IBM3584DeviceMap
- models the library model, serial number, product keys
- zenoss.community.IBM3584Mon.IBM3584FrameMap
- models information about the library frames including model, serial mumber, type, status
- zenoss.community.IBM3584Mon.IBM3584ChangerDevice
- models information about logical libaries including name, description, status
- zenoss.community.IBM3584Mon.IBM3584AccessDevice
- models information about media access devices (tape drives) including name, type, model, firmware, serial number, cleaning status, status
To view the modeled information, click on the "Hardware" tab of the device.
Performance Graphs
Unfortunately, there is not a lot of performance data that is available via SNMP on the 3584. For this reason, the main purpose of this ZenPack is to model inventory information (serial numbers, models) and monitor status of the library via SNMP traps and status indicators. 3 very generic performance graphs are included with the ZenPack -- number of changer devices/logical libaries, number of tapes, number of tape drives.
Event Parsing
This ZenPack includes pre-defined event mappings for SNMP traps located in /Events/HW/Backup/Tape Library. Alerts will be generated and transformed when a SNMP trap is received from the tape library. You can use the "Send Test SNMP Trap" function on your 3584 to test this functionality.
MIBs
This ZenPack includes all of the MIBs from IBM for the 3584.
Prerequisites
- Zenoss Version
- 2.3
- ZenPack Dependencies
- Advanced Device Details
- External Dependencies
- A working SNMPD on your 3584. This should be verified using snmpwalk from your ZenOSS server:
snmpwalk -v2c -c [community] [hostname]
- Installation
- Create /Mibs/IBM subfolder
- Create /Devices/Storage device class
Installation
Normal Installation (packaged egg)
- Download the appropriate egg file for the version of Zenoss you are running.
- Ensure you are logged in as the zenoss user:
$ sudo su - zenoss
- Install the ZenPack:
$ zenpack --install ZenPacks.community.IBM3584Mon-*.egg
- Restart these services:
$ zenoss restart
Developer Mode Installation
In order to do a development mode installation you will want to clone the existing git repository, and then use the --link flag with the zenpack command:
- Ensure you are logged in as the zenoss user:
$ sudo su - zenoss
- Start by cloning the upstream repository:
$ git clone git://github.com/zenoss/ZenPacks.community.IBM3584Mon.git
- Next, perform the installation:
$ zenpack --link --install ZenPacks.community.IBM3584Mon
- Finally, restart these serivices:
$ zenoss restart
Discuss
New: Don't forget to add yourself to the Zenoss User Map!