Apr 25, 2013 3:34 AM
Issue Using ZenPacks | VMware Player Instance
-
Like (0)
Background:
Having downloaded the VMware Player Edition of Zenoss Core (4.2 I think).. I needed it to run on an ESXi instance; so I migrated it using vSphere Converter... worked really smoothly. Uploaded to SAN storage and imported the VM.. sweet it worked! Powered on..
Configured the static IP using NANO and the /etc/networking/interfaces file..
Rebooted and managed to get the web interface for the first time..(10.0.91.10)
Added a public firewall NAT plus a DNS record and away we go..
http://monitoring.company.com:8080
*i'll deal with HTTPS later..
Getting things moving:
I setup a discover of SNMP devices and spent days configuring all my network devices to support a private SNMP community.. I finally got green lights! Not bothered extending to the Windows/Linux Systems yet as I want to expand the SNMP capabilities by utilising MIB packs.
Reading:
ZenPacks as it's referred to in the Zenoss world (MIB pack + objects + locations + commands + additional device classes + object specific monitors etc)..
I uploaded a dozen or so ZenPacks via the /zport/ URL; which appear to have uploaded (Login>Advanced>ZenPacks>Upload>Select ZIP file>Upload>wait..
Unfortunately, no additional device classes have appeared; and no additional options appear next to my network devices in the /zport/ gui.
Here are the list of ZenPacks that Zenoss web interface believes are installed...
ZenPacks.zenoss.ActiveDirectory
ZenPacks.zenoss.ApacheMonitor
ZenPacks.zenoss.DellMonitor
ZenPacks.zenoss.DeviceSearch
ZenPacks.zenoss.DigMonitor
ZenPacks.zenoss.DnsMonitor
ZenPacks.zenoss.EsxTop
ZenPacks.zenoss.FtpMonitor
ZenPacks.zenoss.HPMonitor
ZenPacks.zenoss.HttpMonitor
ZenPacks.zenoss.IISMonitor
ZenPacks.zenoss.IRCDMonitor
ZenPacks.zenoss.JabberMonitor
ZenPacks.zenoss.LDAPMonitor
ZenPacks.zenoss.LinuxMonitor
ZenPacks.zenoss.MSExchange
ZenPacks.zenoss.MSMQMonitor
ZenPacks.zenoss.MSSQLServer
ZenPacks.zenoss.MySqlMonitor
ZenPacks.zenoss.NNTPMonitor
ZenPacks.zenoss.NtpMonitor
ZenPacks.zenoss.PySamba
ZenPacks.zenoss.WindowsMonitor
ZenPacks.zenoss.XenMonitor
ZenPacks.zenoss.ZenAWS
ZenPacks.zenoss.ZenJMX
ZenPacks.zenoss.ZenossVirtualHostMonitor
Some of the key ZenPacks should give me capabilities of doing additional stuff; like so:
*See additional SNMP Object IDs; EG monitor consumable information...
Unfortunately it would appear that the ZenPacks don't offer any of these options at any of the Device Branches that it suggests...
EG: The class: Devices\HTTP exists; 11 objects (individual IPs) are added in the Devices\HTTP class but the zProperties (or Configuration Properties as it's now known) doesn't give me any more options..
Adding a monitored object under this device class too doesn't give any further options (Devices\HTTP\Object Underneath > PLUS Symbol [bottom left] > No additional options).
No HTTP username or password options are available under this device class>details>configuration properties.. i'm a little confused to be honest, as the Template clearly shows HttpMonitor as an additional class.
This specific ZenPack isn't the only one i'm having this issue with - infact ALL of the packs listed above are giving me the same trouble.
Have I done anything wrong, or am I just being stupid?
Hi Simon,
A couple of things here. Lets's start with the HttpMonitor which is provided by the standard ZenPacks.zenoss.HttpMonitor. Really all this provides is the device class, /HTTP, an event, and a performance template, HttpMonitor which MAY be applied to any device class under /Devices. The device class /HTTP supplied with the ZenPack has already had this HttpMonitor template bound to it so that any device you add to the /HTTP device class, also gets this template. If you navigate to one of the 11 devices that you have, you should see this template listed at the bottom of the left-hand menu?
If you look at the template, by default it just tries to connect to the ip address of the device - nothing fancy - so it doesn't need any other parameters, so there are no extra Config Properties (zProperties) to do with http. If you want to, you can modify the standard template or, more likely, create a new subclass of devices under /HTTP and create a new copy of the HttpMonitor template that applies to that class, that has extra parameters like users, passwords, SSL,....
On other ZenPacks, I have a slightly different menu path than you for installing ZenPacks (not the VM and mine is 4.2.3). Either way, I think your menu is for installing ZenPacks that you already have pulled down to your Zenoss server. Your list of ZenPacks installed just looks like the standard Zenoss ones that would be pre-installed.
The method I would use to install ZenPacks would be to start with the ZenPacks page on the new wiki site - http://wiki.zenoss.org/Category:ZenPacks . You probably know that we are currently in rather a transition period between the new wiki and the old JIRA site for ZenPacks. Start with the url above and you often find that following the documentation link takes you back to the old site. The new site is trying very hard to ensure that ZenPacks work for Zenoss 4.x - hence my recommendation to start there.
Download the correct version of the ZenPack for Zenoss 4 - hopefully there is a link that shows that. Sometimes there isn't (like with your printer MIB) - no-one has yet updated it for Zenoss 4. Many ZenPacks include in their name an indication of the pthon version eg. ZenPacks.TwoNMS.PrinterMIB-1.0-py2.6.egg.zip - the py2.6 indicates Python 2.6 and is no good for Zenoss 4 - you need something with a py2.7. This naming convention is just that - the ZP does not have to include the version and some don't (like many of Egor's brillinat ZenPacks).
Can I suggest you start with something on the wiki that does have a 2.7 egg file? Download it to your Zenoss server and then install it there. I personally always use command line to install ZenPacks so that, if there are issues, then you see them. As the zenoss user, I would get, say, ZenPacks.skills1st.bridge-1.0-py2.7.egg into /opt/zenoss/local (my choice of directory - I always create a local dir).Then:
cd /opt/zenoss/local
zenpack --install ZenPacks.skills1st.bridge-1.0-py2.7.egg
zenhub restart
zopectl restart
Some ZenPacks need you to restart zenoss completely with "zenoss restart" - check the documentation on the ZenPack page.
I have just tried to install your Printer MIB on my Zenoss 4.2.3 and it has made a bit of a mess . Don't go there at present - hopefully I can fix it and release a Zenoss 4.x version.
Cheers,
Jane
Jane,
Thanks for the detailed response.
Under the device class (Devices\HTTP\) I selected one object (the load balanced IP for our external web services). Unfortunately no additional template options on the bottom left menu
Cries...
Thanks for the WIKI link - it's definately the only link where i've downloaded zenpacks from. Good shout - I think i wasted a week using some old 'egg' files from the older website. oh well.
Using the command line on the VMware version isn't recommended (but it is available); and I did just what you suggested; downloaded the PrinterNMS Zenpack (wget) and installed it using the commands you gave..
zenpack --install <packname>
followed by a complete host reboot
It appears to fail with python script errors (line 491 if my memory is good); and now i'm guessing it's because the pack already exists as a default installed zenpack.
Do you think it would be easier and quicker to start a fresh from debian and prep the linux machine properly before installing zenoss v4.2.3 ??
Simon
Hi Simon,
You have the HttpMonitor template - there at the left (sorry - not on the popup menus from the bottom but under Monitoring Templates). If you go to Graphs (3rd down in that menu) then you should see values for time and size, provided your Zenoss server can actually get access to the target device.
I am intrigued that you have managed to install the PrinterNMS zenpack - I wouldn't expect it to install anything with py2.6 in its name and it did horrible things to my Zenoss when I tried to recompile it for Python 2.7. Can you still get to see the INFRASTRUCTURE menu??
If, as zenoss user, you do zenpacks --list
do you see ZenPacks.TwoNMS.PrinterMIB in the list?
Re starting afresh - it depends why you are doing this. At present, there isn't support for Debian for Zenoss 4.x - expected soon, but "soon" seems to be a long time coming . If you areally doing a proof-of-concept, then I would hang in there a bit longer with your VM and winkle out some of your issues first.
Cheers,
Jane
I have slightly modified the PrinterMIB ZenPack so it now works for me on Zenoss 4.2.3. I have put a py2.7 version on docs/DOC-11311 .
As always with unknown ZenPacks, if you have a VM I would take a snapshot first and then try installing the new version of the ZenPack.
Cheers,
Jane
Infrastructure menu works as it always did.
just going to un-register the PrinterMIB pack and re-register your new one.. fingers crossed.
Nope it failed
*internal DNS doesn't resolve so changed my wget to the IP of the webserver*
[zenoss@localhost zenoss]$ wget http://204.93.71.120/servlet/JiveServlet/download/11311-3-11027/ZenPacks.TwoNMS.PrinterMIB-1.1-py2.7.egg.zip
--2013-04-26 08:24:20-- http://204.93.71.120/servlet/JiveServlet/download/11311-3-11027/ZenPacks.TwoNMS.PrinterMIB-1.1-py2.7.egg.zip
Connecting to 204.93.71.120:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 29509 (29K) [application/zip]
Saving to: `ZenPacks.TwoNMS.PrinterMIB-1.1-py2.7.egg.zip'
[zenoss@localhost zenoss]$ zenpack --install ZenPacks.TwoNMS.PrinterMIB-1.1-py2.7.egg.zip
ERROR:zen.ZenPackCmd:zenpack command failed
Traceback (most recent call last):
File "/opt/zenoss/Products/ZenUtils/zenpack.py", line 486, in <module>
zp.run()
File "/opt/zenoss/Products/ZenUtils/zenpack.py", line 182, in run
os.makedirs(skinsSubdir, 0750)
File "/opt/zenoss/lib/python2.7/os.py", line 150, in makedirs
makedirs(head, mode)
File "/opt/zenoss/lib/python2.7/os.py", line 157, in makedirs
mkdir(name, mode)
OSError: [Errno 20] Not a directory: '/opt/zenoss/Products/ZenPacks.TwoNMS.PrinterMIB-1.1-py2.7.egg/skins'
Sorry - you need to unzip the file first to get something ending in .egg. Then run the zenpack install against that.
Cheers,
Jane
sorry for the delay; i got pulled off this one for a few days.
Jane, your suggestion worked: I have now got the import working straight from your new EGG file (unzipped)..
Now I see a new device class..
So I imported all my printers in here instead; setup the SNMP community settings...
I see the additional item 'TwoNMS.snmp.PrinterMap' inside the /Printer/PrinterMIB/Device/Modeller Plugins
Like so: servlet/JiveServlet/showImage/102-11311-3-8889/modelersmall.png
Unfortunately I don't see 'Components' like in this picture: servlet/JiveServlet/showImage/102-11311-3-8890/componentgraphsmall.png
I had a look to see if the reports worked... unfortunately they didn't load any data..
unsure what to do i'm restarting the monitoring host (see if the service restart will kick the discovery again).. if that works great.. failing that, leaving it over night to collect some data.. might also do the trick.
Any other suggestions - please just shout!
It looks like the delay over night or reboot kicked off the discovery of all of the device SNMP details... I can now see the consumables!!!
Follow Us On Twitter »
|
Latest from the Zenoss Blog » | Community | Products | Services Resources | Customers Partners | About Us | ||
Copyright © 2005-2011 Zenoss, Inc.
|
||||||||