I've just added a beta version of an AIX Zenpack for the beta version of Zenoss. Perhaps "beta" is too strong of a recommendation for this ZenPack -- all I will guarantee is that it won't end all life on the planet (okay, maybe just Earth is safe... :)
This is an egg-style zenpack, so it most assuredly won't work with 2.1.3.
http://www.zenoss.com/community/wiki/user-contributed/
**Use this ZenPack only with a test Zenoss system to make sure that there's no possibility of messing up your other performance data.**
First, the bad news...
Known issues:
* requires SNMP version 3 with authentication off (ie SNMP v1 commands will work with this feature set). Description of modifications required in the description for the /devices/servers/AIX class.
* doesn't properly map to the manufacture links for any of the hardware found (eg disk, cpus)
* doesn't allow for re-exports of the ZenPack
* the performance collectors have no error checking and are written in bash and perl (Did I mention the word "beta" yet?)
* the performance collectors explicitly require that version 1 snmpwalk and snmpget work, and won't accept other credential info
* filesystem events don't insert the name of the filesystem
* sanity checks in the modelers seem to want too much sanity, as they *seem* to sometimes prevent modeling (aka discovery) from gathering all information. On the plus side, the sanity checking does prevent Zenoss from blowing away previous modelled device info when it can't talk to the SNMP agents or the machine is down. :)
* the AIXBase modeler still doesn't seem to properly identify the hardware model and update the correct spot for the hardware. The serial number does appear to be updated correctly for the hardware, however.
* doesn't show the per-processor statistics, only a total averaged number. In addition, the MIB doesn't update the statistics all that frequently (I might have missed a setting that can up the polling on CPU usage), so it may even be fantastically wrong.
.. and now the good news:
Features:
* uses standard IBM AIX snmpd services. No net-snmp daemons required, no other packages to install.
* adds subclasses for /devices/servers/AIX, with further subclasses for LPARs and VIO servers. Adds a token link into /devices/server/Linux/HMC with a customized zLink so that it's (perhaps?) easier to get to the HMC console.
* (YMMV) discovers memory, paging space, processors, disks, adapters and filesystems. NB: FRU information and model numbers would (I *think*) require updates to other ZenModel relationships, which would need to be in the base Zenoss.
* has a copy of the AIX MIB (from the samples directory) and cleaned up version of the xmtopas-generated MIB (the MIB it generates is, to be polite, syntactically challenged. It may also be plain wrong in places. :)
* allows for a lot more performance statistics to be gathered
While fixes are especially welcome, other feedback is also appreciated. :)
Thank you,
kells
Future possibilites:
Note that storage-related info such as VG + LV + filesystem + MPIO path + LUN ID mapping will require ZenModel relationships to be created, which will require time. This would be useful to be able to create a report to determine (for example) which filesystems would be affected by an outage of which SAN storage system. Some info may also not be available through SNMP.
The VIO mapping of virtual adapters to physical adapters and LUN assignments might be impossible through SNMP. I have written Perl scripts to do end-to-end storage allocation (optimized) / deallocation / management from a DS81k through VIOs to an AIX LPAR so I know how to do it, but I'm not at liberty to share that code, much less contribute it.
happy If anyone else has thoughts about implementing something, please let me know.
This is an egg-style zenpack, so it most assuredly won't work with 2.1.3.
http://www.zenoss.com/community/wiki/user-contributed/
**Use this ZenPack only with a test Zenoss system to make sure that there's no possibility of messing up your other performance data.**
First, the bad news...
Known issues:
* requires SNMP version 3 with authentication off (ie SNMP v1 commands will work with this feature set). Description of modifications required in the description for the /devices/servers/AIX class.
* doesn't properly map to the manufacture links for any of the hardware found (eg disk, cpus)
* doesn't allow for re-exports of the ZenPack
* the performance collectors have no error checking and are written in bash and perl (Did I mention the word "beta" yet?)
* the performance collectors explicitly require that version 1 snmpwalk and snmpget work, and won't accept other credential info
* filesystem events don't insert the name of the filesystem
* sanity checks in the modelers seem to want too much sanity, as they *seem* to sometimes prevent modeling (aka discovery) from gathering all information. On the plus side, the sanity checking does prevent Zenoss from blowing away previous modelled device info when it can't talk to the SNMP agents or the machine is down. :)
* the AIXBase modeler still doesn't seem to properly identify the hardware model and update the correct spot for the hardware. The serial number does appear to be updated correctly for the hardware, however.
* doesn't show the per-processor statistics, only a total averaged number. In addition, the MIB doesn't update the statistics all that frequently (I might have missed a setting that can up the polling on CPU usage), so it may even be fantastically wrong.
.. and now the good news:
Features:
* uses standard IBM AIX snmpd services. No net-snmp daemons required, no other packages to install.
* adds subclasses for /devices/servers/AIX, with further subclasses for LPARs and VIO servers. Adds a token link into /devices/server/Linux/HMC with a customized zLink so that it's (perhaps?) easier to get to the HMC console.
* (YMMV) discovers memory, paging space, processors, disks, adapters and filesystems. NB: FRU information and model numbers would (I *think*) require updates to other ZenModel relationships, which would need to be in the base Zenoss.
* has a copy of the AIX MIB (from the samples directory) and cleaned up version of the xmtopas-generated MIB (the MIB it generates is, to be polite, syntactically challenged. It may also be plain wrong in places. :)
* allows for a lot more performance statistics to be gathered
While fixes are especially welcome, other feedback is also appreciated. :)
Thank you,
kells
Future possibilites:
Note that storage-related info such as VG + LV + filesystem + MPIO path + LUN ID mapping will require ZenModel relationships to be created, which will require time. This would be useful to be able to create a report to determine (for example) which filesystems would be affected by an outage of which SAN storage system. Some info may also not be available through SNMP.
The VIO mapping of virtual adapters to physical adapters and LUN assignments might be impossible through SNMP. I have written Perl scripts to do end-to-end storage allocation (optimized) / deallocation / management from a DS81k through VIOs to an AIX LPAR so I know how to do it, but I'm not at liberty to share that code, much less contribute it.
