ZenPacks : Cisco MIBs : Comments

RE: Cisco MIBs

community@zenoss.org — Fri, 18 Sep 2009 16:33:02 GMT

I can't wait to get this working, unfortunately, I am having some difficulty with the install:

[zenoss@its-testnet01 ~]$ zenpack --install ZenPacks.Nova.Cisco.Mibs-1.0-py2.4.egg.zip
ERROR: zenpack command failed. Reason: [Errno 20] Not a directory: '/opt/zenoss/Products/ZenPacks.Nova.Cisco.Mibs-1.0-py2.4.egg/skins'

Running Zenoss on Redhat EL4

Zenoss	Zenoss 2.4.5
OS	Linux (i686) 2.6.9 (Linux its-testnet01.dcsdk12.org 2.6.9-67.0.22.ELsmp #1 SMP Wed Jul 23 17:30:51 EDT 2008 i686)
Zope	Zope 2.8.8
Python	Python 2.4.4
Database	MySQL 5.0.51 (Ver 5.0.51)
RRD	RRDtool 1.3.5
Twisted	Twisted 8.1.0
NetSnmp	NetSnmp 5.1.2
PyNetSnmp	PyNetSnmp 0.28.13
WMI	Wmi 1.2.10

RE: Cisco MIBs

community@zenoss.org — Mon, 21 Sep 2009 14:06:57 GMT

Discussions surrounding Zenpacks can be found here: zenoss-zenpacks It would be best to post your question there.

RE: Cisco MIBs

community@zenoss.org — Fri, 25 Sep 2009 11:59:00 GMT

Unzip the Zenpack so that it's just a .egg file before installing. The same goes for any ZenPack listed here which is a .egg.zip. Somehow all of the .egg ZenPacks got zipped when they were migrated over. Zenoss Inc. is working to correct this, no ETA.

RE: Cisco MIBs

community@zenoss.org — Fri, 12 Mar 2010 23:35:33 GMT

Did the command line install per the instructions... It ran for about two hours, then errored out.

ERROR: zenpack command failed. Reason: KeyError: -1296989921

Not sure why...

RE: Cisco MIBs

community@zenoss.org — Mon, 15 Mar 2010 13:45:25 GMT

What version of Zenoss did you attempt the install on? What type of installer did you use to install Zenoss (RPM, .DEB, Stack, etc...)

Once I have your details I'll investigate.

RE: Cisco MIBs

community@zenoss.org — Mon, 15 Mar 2010 14:28:14 GMT

I'm actually going to rebuild the server fromt he ground up. I'm

having a few other strange issues that I need to fix.

I'll let you know how the install goes after that.

Thanks,

Jeff

RE: Cisco MIBs

community@zenoss.org — Tue, 25 May 2010 23:17:06 GMT

Random comment/question. I just rebuilt our Zenoss box from the ground up. The first thing i did after installing Zenoss was to install this zenpack. (Seeing as it takes 8 hours to completely install) After i did that installed (using ZenMib) the default mibs that come with zenoss. (Under the IETF, IANA, TUBS, etc) When i did that it apparently created several copies of MIBs that had been installed by this ZenPack. So now when i add new MIBs to Zenoss i get about 200 warnings telling me i have duplicate MIBs installed in /Cisco as well as /IETF or /IANA.

Do you know of any way to remove the duplicates? Do these duplicates need to be installed in both places? If i were to remove them from the duplicates from the /Cisco folder would that break anything that depended on them in the /CISCO folder?

Thanks!

RE: Cisco MIBs

community@zenoss.org — Wed, 26 May 2010 14:33:48 GMT

I've never had that issue with the pack and I've been using it for over a year. The /Cisco folder is what was installed by the pack. Are you sure that you hadn't previously manually installed cisco mibs with zenmib and moved them to the /CISCO folder?

RE: Cisco MIBs

community@zenoss.org — Wed, 26 May 2010 17:54:55 GMT

It was a fresh install. First install was this zenpack. Second step i did was load the mibs that came with zenoss. (On my centos install /opt/zenoss/share/mibs/ietf, iama, & tubs) After Zenmib loaded the mibs from those three directories it pops up warnings everytime i use Zenmib.

For example, one of the errors i recieve is:

2010-05-24 18:44:40,353 WARNING zen.ZenMib:
Found two copies of ADSL-LINE-MIB: /Cisco and /IETF

If i pull up the /Cisco organize and locate ADSL-LINE-MIB i see it has 237 nodes and 12 notifications. When i go to the IETF organizer and locate ADSL-LINE-MIB i see that is has 0 nodes and 0 notifications.

I'm assuming that this is because this zenpack already installed the ADSL-LINE-MIB and when zenmib attempted to re-install it zenmib located a duplicate and didn't install the nodes or notifications and simply put in a place holder. (Seems odd to me)

Perhaps you should remove these duplicate mibs from your zenpack since they come bundled with Zenoss. Or perhaps Zenoss should fix Zenmib and stop it from loaded duplicate mibs.

RE: Cisco MIBs

community@zenoss.org — Wed, 26 May 2010 18:14:08 GMT

I wouldn't even bother to load those Mibs, just load the actual vendor mibs that you need, the ones that come with Zenoss don't need to be loaded.

RE: Cisco MIBs

community@zenoss.org — Fri, 09 Jul 2010 16:20:08 GMT

When I do an SNMP walk it goes down the list of:

SNMPv2-MIB::sysORDescr.58 = STRING:

The Agent Capabilities for CISCO-NTP-MIB.

REVISION

LAST-UPDATED 200604050000Z

ciscoNtpCapabilitySANOSV3R0001 AGENT-CAPABILITIES

SUPPORTS CISCO-NTP-MIB

File name: ios

SNMPv2-MIB::sysORDescr.59 = STRING:

Agent capabilities for CISCO-PING-MIB

LAST-UPDATED 9408180000Z

ciscoPingCapabilityV10R02 AGENT-CAPABILITIES

SUPPORTS CISCO-PING-MIB

File name: ios

Command timed out for [IP REMOVED] (timeout is 15.0 seconds)

----------------------------------------------------------------------------------------------

So you can see, the MIB's process up to #59, where it times out.

Please advise. Thanks.

RE: Cisco MIBs

community@zenoss.org — Fri, 09 Jul 2010 17:36:05 GMT

This ZenPack has nothing to do with snmpwalk, it is only for translating traps that are sent to Zenoss by SNMP enabled cisco devices.

That sounds like a problem with the device itself.

RE: Cisco MIBs

community@zenoss.org — Tue, 20 Jul 2010 04:37:19 GMT

Hello. I'm wondering if this Zenpack just provides the MIBs or if it also includes event transforms or other Zenoss related events.

I guess what i'm wondering is if this pack has more than just the mibs that i can download from Cisco.com.

Thanks!

RE: Cisco MIBs

community@zenoss.org — Tue, 20 Jul 2010 13:18:23 GMT

It is just the Mibs. When I started using Zenoss it was a major pain to get them installed in to Zenoss. The advantage of the pack now is that it automatically groups them in to a Cisco Mibs folder... otherwise you'll have to do it by hand 40 at a time (since it will freeze up if you do more than 40 at a time). There are about 1200 Mibs included in the pack. If you'd rather take a stab at installing them via zenmib then have fun. I know that zenmib was updated between zenoss 2.4.5 and 2.5.0 according to the guide that I wrote, so these Mibs should be much easier to actually get loaded in now.

RE: Cisco MIBs

community@zenoss.org — Tue, 20 Jul 2010 13:19:18 GMT

I love the out of office reply causing an actual post on here. Might want to add an exception for emails from Zenoss.

RE: Cisco MIBs

community@zenoss.org — Tue, 20 Jul 2010 14:18:26 GMT

when i install this pack i have this error:

[zenoss@zenoss ~]$ zenpack --install ZenPacks.Nova.Cisco.Mibs-1.0-py2.4.egg

Link to http://pypi.python.org/simple/ZenPacks.Nova.Cisco.Mibs/ ***BLOCKED*** by --allow-hosts

Couldn't find index page for 'ZenPacks.Nova.Cisco.Mibs' (maybe misspelled?)

Link to http://pypi.python.org/simple/ ***BLOCKED*** by --allow-hosts

No local packages or download links found for ZenPacks.Nova.Cisco.Mibs==1.0
Couldn't find index page for 'ZenPacks.Nova.Cisco.Mibs' (maybe misspelled?)
No local packages or download links found for ZenPacks.Nova.Cisco.Mibs==1.0
ERROR:zen.ZenPackCmd:zenpack command failed
Traceback (most recent call last):
File "/opt/zenoss/Products/ZenUtils/zenpack.py", line 406, in <module>
    zp.run()
File "/opt/zenoss/Products/ZenUtils/zenpack.py", line 134, in run
    previousVersion= self.options.previousVersion)
File "/opt/zenoss/Products/ZenUtils/ZenPackCmd.py", line 240, in InstallEggAndZenPack
    zpDists = InstallEgg(dmd, eggPath, link=link)
File "/opt/zenoss/Products/ZenUtils/ZenPackCmd.py", line 303, in InstallEgg
    DoEasyUninstall(eggPath)
File "/opt/zenoss/Products/ZenUtils/ZenPackCmd.py", line 891, in DoEasyUninstall
    easy_install.main(args)
File "/opt/zenoss/lib/python/setuptools/command/easy_install.py", line 1712, in main
    with_ei_usage(lambda:
File "/opt/zenoss/lib/python/setuptools/command/easy_install.py", line 1700, in with_ei_usage
    return f()
File "/opt/zenoss/lib/python/setuptools/command/easy_install.py", line 1716, in <lambda>
    distclass=DistributionWithoutHelpCommands, **kw
File "/opt/zenoss/lib/python2.6/distutils/core.py", line 152, in setup
    dist.run_commands()
File "/opt/zenoss/lib/python2.6/distutils/dist.py", line 975, in run_commands
    self.run_command(cmd)
File "/opt/zenoss/lib/python2.6/distutils/dist.py", line 995, in run_command
    cmd_obj.run()
File "/opt/zenoss/lib/python/setuptools/command/easy_install.py", line 211, in run
    self.easy_install(spec, not self.no_deps)
File "/opt/zenoss/lib/python/setuptools/command/easy_install.py", line 427, in easy_install
    return self.install_item(None, spec, tmpdir, deps, True)
File "/opt/zenoss/lib/python/setuptools/command/easy_install.py", line 478, in install_item
    self.process_distribution(spec, dist, deps)
File "/opt/zenoss/lib/python/setuptools/command/easy_install.py", line 519, in process_distribution
    [requirement], self.local_index, self.easy_install
File "/opt/zenoss/lib/python/pkg_resources.py", line 563, in resolve
    dist = best[req.key] = env.best_match(req, self, installer)
File "/opt/zenoss/lib/python/pkg_resources.py", line 799, in best_match
    return self.obtain(req, installer) # try and download/install
File "/opt/zenoss/lib/python/pkg_resources.py", line 811, in obtain
    return installer(requirement)
File "/opt/zenoss/lib/python/setuptools/command/easy_install.py", line 434, in easy_install
    self.local_index
File "/opt/zenoss/lib/python/setuptools/package_index.py", line 475, in fetch_distribution
    return dist.clone(location=self.download(dist.location, tmpdir))
AttributeError: 'NoneType' object has no attribute 'clone'

RE: Cisco MIBs

community@zenoss.org — Tue, 20 Jul 2010 16:40:19 GMT

Hi, I get the same error. I am running 3.0.0. Has this been tested on 3.0.0 I wonder? Thanks Steve

[root@ihnmt01 ~]# /usr/local/zenoss/zenoss/bin/zenpack --install ZenPacks.Nova.Cisco.Mibs-1.0-py2.4.egg

Link to http://pypi.python.org/simple/ZenPacks.Nova.Cisco.Mibs/ ***BLOCKED*** by --allow-hosts

Couldn't find index page for 'ZenPacks.Nova.Cisco.Mibs' (maybe misspelled?)

Link to http://pypi.python.org/simple/ ***BLOCKED*** by --allow-hosts

RE: Cisco MIBs

community@zenoss.org — Tue, 20 Jul 2010 18:52:57 GMT

No, I have not tested installing this on 3.0 yet. Try removing the "-py2.4" from the filename. Zenoss 3.0 uses Python 2.6. It should install after you remove that.

RE: Cisco MIBs

community@zenoss.org — Tue, 20 Jul 2010 20:56:25 GMT

Hi Ryan, thanks for your help. I adjusted the filename as suggested and I no longer get an error right away. It processes for quite a while and then I get a different error (below). This suggests it is a database conflict. Running the command even though it fails leaves a Zenpack, so I removed this and restarted zope, tried again but no luck. So maybe it is something more sinister, or I am doing something else wrong, likely!

[root@ihnmt01 ~]# /usr/local/zenoss/zenoss/bin/zenpack --install ZenPacks.Nova.Cisco.Mibs-1.0.egg
2010-07-20 23:06:04,694 INFO zen.ZPLoader: Loading /usr/local/zenoss/zenoss/ZenPacks/ZenPacks.Nova.Cisco.Mibs-1.0.egg/ZenPacks/Nova/Cisco/Mibs/objects/objects.xml
Traceback (most recent call last):
File "/usr/local/zenoss/zenoss/Products/ZenUtils/zenpack.py", line 406, in <module>
    zp.run()
File "/usr/local/zenoss/zenoss/Products/ZenUtils/zenpack.py", line 134, in run
    previousVersion= self.options.previousVersion)
File "/usr/local/zenoss/zenoss/Products/ZenUtils/ZenPackCmd.py", line 249, in InstallEggAndZenPack
    previousVersion)
File "/usr/local/zenoss/zenoss/Products/ZenUtils/ZenPackCmd.py", line 424, in InstallDistAsZenPack
    zenPack.install(dmd)
File "/usr/local/zenoss/zenoss/Products/ZenModel/ZenPack.py", line 251, in install
    loader.load(self, app)
File "/usr/local/zenoss/zenoss/Products/ZenModel/ZenPackLoader.py", line 99, in load
    importer.loadObjectFromXML(xmlfile=f)
File "/usr/local/zenoss/zenoss/Products/ZenRelations/ImportRM.py", line 458, in loadObjectFromXML
    parser.parse(self.infile)
File "/usr/local/zenoss/python/lib/python2.6/site-packages/_xmlplus/sax/expatreader.py", line 109, in parse
    xmlreader.IncrementalParser.parse(self, source)
File "/usr/local/zenoss/python/lib/python2.6/site-packages/_xmlplus/sax/xmlreader.py", line 123, in parse
    self.feed(buffer)
File "/usr/local/zenoss/python/lib/python2.6/site-packages/_xmlplus/sax/expatreader.py", line 216, in feed
    self._parser.Parse(data, isFinal)
File "/usr/local/zenoss/python/lib/python2.6/site-packages/_xmlplus/sax/expatreader.py", line 315, in end_element
    self._cont_handler.endElement(name)
File "/usr/local/zenoss/zenoss/Products/ZenModel/ZenPackLoader.py", line 94, in endElement
    ImportRM.endElement(self, name)
File "/usr/local/zenoss/zenoss/Products/ZenRelations/ImportRM.py", line 213, in endElement
    self.commit()
File "/usr/local/zenoss/zenoss/Products/ZenRelations/ImportRM.py", line 480, in commit
    trans.commit()
File "/usr/local/zenoss/python/lib/python2.6/site-packages/transaction-1.0.0-py2.6.egg/transaction/_transaction.py", line 322, in commit
    self._commitResources()
File "/usr/local/zenoss/python/lib/python2.6/site-packages/transaction-1.0.0-py2.6.egg/transaction/_transaction.py", line 419, in _commitResources
    rm.tpc_vote(self)
File "/usr/local/zenoss/python/lib/python2.6/site-packages/ZODB3-3.9.3-py2.6-linux-x86_64.egg/ZODB/Connection.py", line 763, in tpc_vote
    s = vote(transaction)
File "/usr/local/zenoss/python/lib/python2.6/site-packages/ZODB3-3.9.3-py2.6-linux-x86_64.egg/ZEO/ClientStorage.py", line 1068, in tpc_vote
    return self._check_serials()
File "/usr/local/zenoss/python/lib/python2.6/site-packages/ZODB3-3.9.3-py2.6-linux-x86_64.egg/ZEO/ClientStorage.py", line 905, in _check_serials
    raise s
ZODB.POSException.ConflictError: database conflict error (oid 0x07fabc, class BTrees.IOBTree.IOBTree, serial this txn started with 0x0387a57059962b55 2010-07-20 22:40:20.996859, serial currently committed 0x0387a570b9ff3788 2010-07-20 22:40:43.593033)

RE: Cisco MIBs

community@zenoss.org — Tue, 20 Jul 2010 20:56:51 GMT

RE: Cisco MIBs

community@zenoss.org — Tue, 20 Jul 2010 21:01:04 GMT

Sounds like your zope database needs reindexing. Make a copy of $ZENHOME/var/Data.fs (just copy it to Data.fs.bak or something), then go in to zendmd and do:

reindex()

commit()

ctrl-d to exit zendmd

RE: Cisco MIBs

community@zenoss.org — Wed, 21 Jul 2010 09:32:40 GMT

Excellent that did the trick. Thank you for everything.

RE: Cisco MIBs

community@zenoss.org — Wed, 21 Jul 2010 09:33:18 GMT

RE: Cisco MIBs

community@zenoss.org — Fri, 17 Sep 2010 18:09:49 GMT

I have happily been using the Cisco MIBs ZenPack for a while now, but I'm wondering if the problems I'm now having with the Cisco ASA Security Appliance ZenPack are related to some overlapping MIBs or something (more info in this thread).

The Cisco MIBs ZenPack still shows as installed for me, and I don't remember doing the steps at the top of this page for deleting the ZenPack and leaving the MIBs installed, so I don't think I've done that.

Any recommendations for me? Possible course I could take would be:

Uninstall the Cisco MIBs ZenPack (does this remove the MIBs?)
Perform the steps above to delete the ZenPack but keep the MIBs as they are
Compare the 1100+ MIBs in this pack with the ones in the ASA ZenPack to see if there's overlap (but then what do I do?)

Thanks!

RE: Cisco MIBs

community@zenoss.org — Mon, 20 Sep 2010 14:26:56 GMT

I highly doubt that it's related. I'm using the Cisco ASA pack without issues. The step listed for removing the ZenPack without removing the Mibs is simply to address page load performance issues caused by very large ZenPacks (such as this one) being installed. It would not affect the actual performance of data collection (I do highly recommend doing it though for the sake of UI performance).

In my experience Mib overlap is not possible in Zenoss. Even if it is, I can't see it causing issues. You could always search for those specific Mibs in the Cisco Mibs folder and remove them if they are duplicates. You'd then have to restart Zenoss to get it to pick up on the new Mibs configuration.

RE: Cisco MIBs

community@zenoss.org — Mon, 01 Nov 2010 15:08:54 GMT

Hi Ryan,

I am having problems downloading ZenPacks.Nova.Cisco.Mibs-1.0-py2.6.egg.zip - it gets stuck at around 22%. Would you check that there isn't a problem with this file please?

Many thanks

RE: Cisco MIBs

community@zenoss.org — Mon, 01 Nov 2010 15:22:29 GMT

I just downloaded it with no problems at all.

RE: Cisco MIBs

community@zenoss.org — Mon, 01 Nov 2010 15:27:31 GMT

My apologies. I succeeded from a different PC. Must be my AV...

RE: Cisco MIBs

community@zenoss.org — Wed, 01 Dec 2010 09:53:58 GMT

Hi Ryan,

I'm a college student and I'm on a three months stage in order to collect infos for my thesys, and the goal is to use Zenoss Core to monitorize a vast network infrastructure

I've installed Cisco Mibs Zenpack on my 3.03 Zenoss Core on a dedicated server, then I followed your advice and removed the zenpack leaving only the Mibs. The result was a system interface very slow, and I also noticed that the number of objects in the catalog increased from 22,000 to 89,000 (I've set the cache to 100,000 some days before)

The point is that in a couple of days of heavy usage, I've found an heavy ram usage (normally, my zenoss server used about 2.5 Gb of the 16Gb available) up to 14 Gb. Besides, on Monday morning I found that the file /opt/zenoss/var/Data.fs was 21Gb and the disk space was over. I had to mv Data.fs to another partition and rename Data.fs.old to Data.fs to have Zenoss back working, even if I've lost the last day job.

I've got a question: is it possible to remove all the mibs from the shell and not from the web interface?

Many thanks in advance
Valerio - Italy

RE: Cisco MIBs

community@zenoss.org — Wed, 01 Dec 2010 16:18:39 GMT

The number of objects increasing makes perfect sense since each node of each Mib is an object. The fact that your Data.fs file is 21GB does not make sense since there isn't even close to that amount of data in this ZenPack. It sounds like you need to zeopack your zope database. Zope keeps track of every change done to it, so you end up with lots of garbage data about previous states of the database. To eliminate this excess data you need to zeopack. I run the following command as root to shrink my zope databases when they get too large:

/usr/local/zenoss/python/bin/python /usr/local/zenoss/zenoss/bin/zeopack.py -h localhost -p 8100 && rm /usr/local/zenoss/zenoss/var/Data.fs.old

The command may be a bit different for you depending on what installer you used (I used stack), read up on zeopack and you'll figure it out.

I have my Cisco Mibs pack on 15 Production Zenoss servers running 2.5.2 as well as 1 test server running 3.0.3 and it's working fine on all of them. Try the zeopack and you should see a drastic increase in performance.

How many devices do you currently have in that instance of Zenoss? Also, make sure that the Cisco Mibs pack no longer shows up in the ZenPacks list. If it does, then you didn't follow the directions on this page properly.

RE: Cisco MIBs

community@zenoss.org — Wed, 26 Jan 2011 22:07:36 GMT

Hi Ryan,

Thanks for the time and effort in creating this zenpack. I tried your zenpack with zenoss 3.0.3 on centos 5.3 with stack installer.

1. I ran the zenpacks(ZenPacks.Nova.Cisco.Mibs-1.1-py2.6.egg.zip) but following error is coming.

2. I see 814 Mibs in Cisco folder in gui. I noticed you mentioned that it should be 1500 Mibs in the end of the process.

3. I used zendmd to take off zenpack.

Kindly let me know where it went wrong and how to rectify it.

[root@localhost bin]# ./zenpack --install /home/zenoss/ZenPacks.Nova.Cisco.Mibs-

INFO:zen.ZenPackCMD:Previous ZenPack exists with same name ZenPacks.Nova.Cisco.M

INFO:zen.ZenPackCMD:installing zenpack ZenPacks.Nova.Cisco.Mibs; launching proce

2011-01-25 19:56:55,021 INFO zen.ZPLoader: Loading /usr/local/zenoss/zenoss/ZenPacks/ZenPacks.Nova.Cisco.Mibs-1.1-py2.6.egg/ZenPacks/Nova/Cisco/Mibs/objects/objects.xml

2011-01-25 20:33:09,626 ERROR zen.ZenPackCmd: zenpack command failed

Traceback (most recent call last):

File "/usr/local/zenoss/zenoss/Products/ZenUtils/zenpack.py", line 406, in <module>

zp.run()

File "/usr/local/zenoss/zenoss/Products/ZenUtils/zenpack.py", line 134, in run previousVersion=self.options.previousVersion)

File "/usr/local/zenoss/zenoss/Products/ZenUtils/ZenPackCmd.py", line 249, in InstallEggAndZenPack

forceRunExternal=forceRunExternal)

File "/usr/local/zenoss/zenoss/Products/ZenUtils/ZenPackCmd.py", line 424, in InstallDistAsZenPack zenPack.install(dmd)

File "/usr/local/zenoss/zenoss/Products/ZenModel/ZenPack.py", line 251, in install

loader.load(self, app)

File "/usr/local/zenoss/zenoss/Products/ZenModel/ZenPackLoader.py", line 99, in load

importer.loadObjectFromXML(xmlfile=f)

File "/usr/local/zenoss/zenoss/Products/ZenRelations/ImportRM.py", line 458, in loadObjectFromXML

parser.parse(self.infile)

File "/usr/local/zenoss/python/lib/python2.6/site-packages/_xmlplus/sax/expatreader.py", line 109, in parse

xmlreader.IncrementalParser.parse(self, source)

File "/usr/local/zenoss/python/lib/python2.6/site-packages/_xmlplus/sax/xmlreader.py", line 123, in parse

self.feed(buffer)

File "/usr/local/zenoss/python/lib/python2.6/site-packages/_xmlplus/sax/expatreader.py", line 216, in feed

self._parser.Parse(data, isFinal)

File "/usr/local/zenoss/python/lib/python2.6/site-packages/_xmlplus/sax/expatreader.py", line 315, in end_element

self._cont_handler.endElement(name)

File "/usr/local/zenoss/zenoss/Products/ZenModel/ZenPackLoader.py", line 94, in endElement

ImportRM.endElement(self, name)

File "/usr/local/zenoss/zenoss/Products/ZenRelations/ImportRM.py", line 213, in endElement

self.commit()

File "/usr/local/zenoss/zenoss/Products/ZenRelations/ImportRM.py", line 480, in commit

trans.commit()

File "/usr/local/zenoss/python/lib/python2.6/site-packages/transaction-1.0.0-py2.6.egg/transaction/_transaction.py", line 322, in commit

self._commitResources()

File "/usr/local/zenoss/python/lib/python2.6/site-packages/transaction-1.0.0-py2.6.egg/transaction/_transaction.py", line 419, in _commitResources

rm.tpc_vote(self)

File "/usr/local/zenoss/python/lib/python2.6/site-packages/ZODB3-3.9.3-py2.6-linux-i686.egg/ZODB/Connection.py", line 763, in tpc_votes = vote(transaction)

File "/usr/local/zenoss/python/lib/python2.6/site-packages/ZODB3-3.9.3-py2.6-linux-i686.egg/ZEO/ClientStorage.py", line 1067, in tpc_vote

self._server.vote(id(txn))

File "/usr/local/zenoss/python/lib/python2.6/site-packages/ZODB3-3.9.3-py2.6-linux-i686.egg/ZEO/ServerStub.py", line 246, in vote

return self.rpc.call('vote', trans_id)

File "/usr/local/zenoss/python/lib/python2.6/site-packages/ZODB3-3.9.3-py2.6-linux-i686.egg/ZEO/zrpc/connection.py", line 703, in call

raise inst # error raised by server

IOError: [Errno 28] No space left on device

ERROR:zen.ZenPackCmd:zenpack command failed

Traceback (most recent call last):

File "/usr/local/zenoss/zenoss/Products/ZenUtils/zenpack.py", line 406, in <module>

zp.run()

File "/usr/local/zenoss/zenoss/Products/ZenUtils/zenpack.py", line 134, in run

previousVersion= self.options.previousVersion)

File "/usr/local/zenoss/zenoss/Products/ZenUtils/ZenPackCmd.py", line 249, in InstallEggAndZenPack

forceRunExternal=forceRunExternal)

File "/usr/local/zenoss/zenoss/Products/ZenUtils/ZenPackCmd.py", line 415, in InstallDistAsZenPack

(p.returncode, err))

ZenPackException: Error installing the egg (255): None

[root@localhost bin]# su - zenoss

[zenoss@localhost ~]$ zendmd

dmd.ZenPackManager.packs._delObject('ZenPacks.Nova.Cisco.Mibs')

Welcome to the Zenoss dmd command shell!

'dmd' is bound to the DataRoot. 'zhelp()' to get a list of commands.

Use TAB-TAB to see a list of zendmd related commands.

Tab completion also works for objects -- hit tab after an object name and '.'

(eg dmd. + tab-key).

>>> dmd.ZenPackManager.packs._delObject('ZenPacks.Nova.Cisco.Mibs')

>>> commit()

>>>

[1]+ Stopped zendmd

Thanks a lot in advance.

RE: Cisco MIBs

community@zenoss.org — Wed, 26 Jan 2011 22:11:34 GMT

Edit: sorry, thought you were installing as a .zip. Reference by next comment.

RE: Cisco MIBs

community@zenoss.org — Wed, 26 Jan 2011 22:14:38 GMT

Under closer inspection I see "IOError: [Errno 28] No space left on device". Are you sure you haven't simply run out of disk space while installing the pack?

RE: Cisco MIBs

community@zenoss.org — Thu, 27 Jan 2011 17:39:46 GMT

ahhhh how i missed tht

Let me try it with new setup and inform u with the results. thanks...

RE: Cisco MIBs

community@zenoss.org — Thu, 27 Jan 2011 23:00:46 GMT

Thanks Ryan.

Its working now.

[zenoss@localhost bin]$ ./zenpack --install /home/zenoss/ZenPacks.Nova.Cisco.Mib

2011-01-27 10:32:16,108 INFO zen.ZPLoader: Loading /opt/zenoss/ZenPacks/ZenPacks

2011-01-27 16:55:31,274 INFO zen.AddToPack: End loading objects

2011-01-27 16:55:31,276 INFO zen.AddToPack: Processing links

2011-01-27 16:55:35,100 INFO zen.AddToPack: Loaded 73438 objects into the ZODB database

2011-01-27 16:55:35,869 INFO zen.HookReportLoader: loading reports from:/opt/zenoss/ZenPacks/ZenPacks.Nova.Cisco.Mibs-1.1-py2.6.egg/ZenPacks/Nova/Cisco/Mibs/reports

[zenoss@localhost bin]$ zendmd

dmd.ZenPackManager.packs._delObject('ZenPacks.Nova.Cisco.Mibs')

Welcome to the Zenoss dmd command shell!

'dmd' is bound to the DataRoot. 'zhelp()' to get a list of commands.

Use TAB-TAB to see a list of zendmd related commands.

Tab completion also works for objects -- hit tab after an object name and '.'

(eg dmd. + tab-key).

>>> dmd.ZenPackManager.packs._delObject('ZenPacks.Nova.Cisco.Mibs')

>>> commit()

but its shows 1131 mibs in cisco folder. Is it correct? I just want to ensure... But thanks

RE: Cisco MIBs

community@zenoss.org — Fri, 28 Jan 2011 04:44:26 GMT

Yes, that is the correct amount. I just hadn't updated the ZenPack page with that amount since I released the version 1.1 update of the pack.

RE: Cisco MIBs

community@zenoss.org — Thu, 03 Feb 2011 13:20:28 GMT

oh sweet thanks Ryan

RE: Cisco MIBs

community@zenoss.org — Mon, 07 Feb 2011 23:33:53 GMT

Ryan, I am running Zenoss 3.0.3... I installed your Zenpack via the command-line install, and for some reason it is only showing 725 Mibs in the "mibs overview" section. I don't know if somthing got "hosed" in the install or what?

What would be the best way to proceed...just try reinstalling it or deleting all the mibs off zenoss as well as the whole directory structure the zenpack created i.e "/usr/local/zenoss/zenoss/ZenPacks/ZenPacks.Nova.Cisco.Mibs-1.1-py2.6.egg", then run it again.

I didn't know if I just run it again, will it recognize the already installed mibs then proceed with the ones that didnt get installed? Thanks for your help!

RE: Cisco MIBs

community@zenoss.org — Tue, 08 Feb 2011 13:10:48 GMT

Hi,

some feedback:

1131 MIBs loaded, no problem

TIME: cca 26 hrs !!!

Anyway, what now? Do i have to manually map my traps to classes or....?

Traps have been comming to my zenoss before i loaded theese mibs. Of course, they were all Unknown class and unformatted alarm text etc.

I hope now i won't have to change much?

Will traps from now on automatically be interpreted and mapped to the source/class or what?

What are the next steps? Zenoss docs don't say much on how loading a MIB will help me in the event management...

RE: Cisco MIBs

community@zenoss.org — Tue, 08 Feb 2011 15:27:08 GMT

Your install didn't complete properly. Just run the install overtop of what's already there. Make sure that you run it in a screen session or something. Your terminal session probably timed out which killed the install when it was about half way through.

RE: Cisco MIBs

community@zenoss.org — Tue, 08 Feb 2011 15:27:52 GMT

Restart Zenoss after installing the pack. Traps will be interpreted, but it's not going to auto map them to classes, you need to do that yourself.

RE: Cisco MIBs

community@zenoss.org — Tue, 08 Feb 2011 15:28:40 GMT

Also, you should read up on transforms if you aren't familliar with them. They are what will allow you to give traps a human readable event summary when they come in.

RE: Cisco MIBs

community@zenoss.org — Tue, 08 Feb 2011 23:12:00 GMT

Must have been my SSH session... The reinstall showed the correct number of MIBs. Thanks for your help!

RE: Cisco MIBs

community@zenoss.org — Fri, 25 Mar 2011 17:28:05 GMT

I get this error when i attempt to install the zenpack- how can i fix this ?

$ zenpack --install /tmp/ZenPacks.Nova.Cisco.Mibs-1.1-py2.6.egg

Link to http://pypi.python.org/simple/ZenPacks.Nova.Cisco.Mibs/ ***BLOCKED*** by --allow-hosts

Couldn't find index page for 'ZenPacks.Nova.Cisco.Mibs' (maybe misspelled?)

Link to http://pypi.python.org/simple/ ***BLOCKED*** by --allow-hosts

No local packages or download links found for ZenPacks.Nova.Cisco.Mibs==1.1

Download error: (101, 'Network is unreachable') -- Some packages may not be found!

Couldn't find index page for 'ZenPacks.Nova.Cisco.Mibs' (maybe misspelled?)

Download error: (101, 'Network is unreachable') -- Some packages may not be found!

No local packages or download links found for ZenPacks.Nova.Cisco.Mibs==1.1

ERROR: zenpack command failed. Reason: SystemExit: error: Could not find suitable distribution for Requirement.parse('ZenPacks.Nova.Cisco.Mibs==1.1')

RE: Cisco MIBs

community@zenoss.org — Fri, 25 Mar 2011 17:47:21 GMT

Are you using Zenoss 2.5?

RE: Cisco MIBs

community@zenoss.org — Fri, 25 Mar 2011 17:51:12 GMT

Yes - i have reverted to 2.2 zenpack and it seems to be installing - thanks.

RE: Cisco MIBs

community@zenoss.org — Fri, 25 Mar 2011 17:53:32 GMT

No, the reason I was asking is because you were using the 2.6 zenpack file which only installs in Zenoss 3.0, you need to download and use the 2.4 zenpack file.

RE: Cisco MIBs

community@zenoss.org — Fri, 29 Apr 2011 20:58:39 GMT

I Figured out you need to do this as root not Zenoss.

RE: Cisco MIBs

community@zenoss.org — Mon, 02 May 2011 13:34:11 GMT

It had absolutely nothing to do with doing it as root. You should never install ZenPacks as root, always do it as the Zenoss user. Your actual problem was that you were copying and pasting the command from the ZenPack page which was "zenpack --install ZenPacks.Nova.Cisco.Mibs-1.0-py2.6.egg" (I updated it to be 1.1 instead). The filename that you actually downloaded was ZenPacks.Nova.Cisco.Mibs-1.1-py2.6.egg. The error that you received ("SystemExit: error: Not a URL, existing file, or requirement spec: '/zenpack/ZenPacks.Nova.Cisco.Mibs-1.0-py2.6.egg'") was telling you that there was no file in existence with the name that you specified.

RE: Cisco MIBs

community@zenoss.org — Wed, 27 Jul 2011 04:10:16 GMT

Installion failed part way through for me with a BTree error like this one: http://community.zenoss.org/message/59959

Because of this I had to load the remaining Cisco mibs myself using zenmib. This was easy enough, just unpack all of the mibs to a directory, cd to that directory and:

zenmib run *

This worked fine and all of the mibs were loaded, but as mentioned by Ryan they were all in the root Mibs directory rather than the 'Cisco' organizer. Moving them all by via the web interface would've been tedious to say the least.

Just in case it's useful to somebody, here's what I did in zendmd to clean them up:

for mib in dmd.Mibs.mibs():

if 'CISCO' in mib.getId():

dmd.Mibs.Cisco.manage_addMibModule(mymib.getId())

dmd.Mibs.removeMibModules(mymib.getId())

RE: Cisco MIBs

community@zenoss.org — Wed, 27 Jul 2011 16:46:21 GMT

I generally install this pack first thing when I'm setting up a new Zenoss instance, so I've never run in to conflict issues like that. This ZenPack has a heck of a lot of objects in it, so if you're installing it on a really busy Zenoss server it is possible to run in to conflicts like that. To fix issues like this I recommend reindex() then sync() then commit() in zendmd.

RE: Cisco MIBs

community@zenoss.org — Tue, 14 Aug 2012 16:40:25 GMT

Safe to assume this works on 4.02?

I hope so!

Zenoss is pretty cool - my first multi-platform monitoring system install.

RE: Cisco MIBs

community@zenoss.org — Tue, 14 Aug 2012 18:57:37 GMT

It does work on 4.2, just change the py2.6 in the filename to py2.7. I'm planning to release an updated version of the pack in the next couple of weeks which will include more Mibs.

RE: Cisco MIBs

community@zenoss.org — Mon, 29 Oct 2012 15:12:07 GMT

Hi,

Is there any version for the Zenoss Core 4.2?

Thanks,

David

RE: Cisco MIBs

community@zenoss.org — Mon, 29 Oct 2012 15:13:07 GMT

Just change py2.6 to py2.7 in the filename and they'll install in to Zenoss 4 perfectly fine.

RE: Cisco MIBs

community@zenoss.org — Mon, 29 Oct 2012 16:21:59 GMT

Worked great ☺

Thanks

RE: Cisco MIBs

community@zenoss.org — Fri, 18 Jan 2013 12:14:29 GMT

Hello,

I have changed zenpack file name as was stated hire, for zenpack to operate on 4.3.2 version. But still get following error.

[zenoss@localhost zen]$ zenpack --install ZenPacks.Nova.Cisco.Mibs-1.1-py2.7.egg

ERROR:zen.ZenMessaging:Error encountered while processing ZenPacks.atelepin.cbCiscoQOS

Traceback (most recent call last):

File "/opt/zenoss/Products/ZenMessaging/queuemessaging/schema.py", line 58, in _getZenPackSchemas

pkg_path = zpkg.load().__path__[0]

File "/opt/zenoss/lib/python/pkg_resources.py", line 1954, in load

entry = __import__(self.module_name, globals(),globals(), ['__name__'])

File "/opt/zenoss/ZenPacks/ZenPacks.atelepin.cbCiscoQOS-1.2-py2.7.egg/ZenPacks/atelepin/cbCiscoQOS/__init__.py", line 16, in <module>

from ServicePolicyReportClass import ServicePolicyReportClass

ImportError: No module named ServicePolicyReportClass

ERROR:zen.ZenossStartup:Error encountered while processing ZenPacks.atelepin.cbCiscoQOS

Traceback (most recent call last):

File "/opt/zenoss/Products/ZenossStartup/__init__.py", line 27, in <module>

pkg_path = zpkg.load().__path__[0]

File "/opt/zenoss/lib/python/pkg_resources.py", line 1954, in load

entry = __import__(self.module_name, globals(),globals(), ['__name__'])

File "/opt/zenoss/ZenPacks/ZenPacks.atelepin.cbCiscoQOS-1.2-py2.7.egg/ZenPacks/atelepin/cbCiscoQOS/__init__.py", line 16, in <module>

from ServicePolicyReportClass import ServicePolicyReportClass

ImportError: No module named ServicePolicyReportClass

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 143, in run

self.connect()

File "/opt/zenoss/Products/ZenUtils/ZenScriptBase.py", line 52, in connect

setDescriptors(self.dmd)

File "/opt/zenoss/Products/ZenRelations/ZenPropertyManager.py", line 663, in setDescriptors

module = __import__(zpkg.module_name, globals(), locals(), fromlist)

File "/opt/zenoss/ZenPacks/ZenPacks.atelepin.cbCiscoQOS-1.2-py2.7.egg/ZenPacks/atelepin/cbCiscoQOS/__init__.py", line 16, in <module>

from ServicePolicyReportClass import ServicePolicyReportClass

ImportError: No module named ServicePolicyReportClass

[zenoss@localhost zen]$

RE: Cisco MIBs

community@zenoss.org — Fri, 18 Jan 2013 15:28:00 GMT

That error doesn't relate to this ZenPack. It relates to ZenPacks.atelepin.cbCiscoQOS. Either that pack is broken, or you installed it and didn't restart zope afterwards.