Oct 6, 2009 9:26 PM
New Bridge MIB ZenPack
-
Like (0)
Thanks to Jane Curry for providing her new Bridge MIB ZenPack in conjunction with her very thorough Creating Zenoss ZenPacks paper. This ZenPack queries the BRIDGE MIB in a switch to provide some Layer 2 topology information. Be sure to check out the ZenPack and the paper!
Thanks Jane!
When installing this I got this warning:
WARNING:zen.ToManyRelationshipBase:Tried to delete object id 'BridgeDeviceDetail' but didn't find it on /zport/dmd/zenMenus/More/zenMenuItems
And when I moved a switch the new class I get the following error when I model the device.
2009-10-12 10:18:40 | ERROR | zen.ZenModeler | Unable to fill collection slots: [Failure instance: Traceback (failure with no frames): Products.ZenHub.PBDaemon.RemoteException: Remote exception: exceptions.AttributeError: 'BridgeDevice' object has no attribute 'primaryAq'Traceback (most recent call last): File "/usr/local/zenoss/zenoss/Products/ZenHub/PBDaemon.py", line 73, in inner return callable(*args, **kw) File "/usr/local/zenoss/zenoss/Products/ZenHub/services/ModelerService.py", line 79, in remote_getDeviceConfig device = device.primaryAq() AttributeError: 'BridgeDevice' object has no attribute 'primaryAq' ] |
This is on zenoss 2.4.5
Would also be great to have this in combination with the IPSLA ZenPack.
In our case each SLA node is the primary node on each site, so have it handle both sla and this under the same class would be great, possible to config it this way? (I have no knowledge in Python/Perl)
I know this is a pain in a production environment, but can I ask you to try deleting an existing switch and rediscovering it directly into the /Network/Switch/BridgeMIB device class. It would appear that device classes that have "container" relationships prohibit devices being moved into the new class - this seems to be a caveat on several ZenPacks. Hopefully, that will fix it - please report back.
I haven't tested this with 2.4.5 (and don't currently have one) but I do have a 2.5 beta so will test on that and report back..
I assume you did restart both zenhub and zopectl after installing the ZenPack?? After doing so, does the ZenPacks menu report the bridge ZenPack as looking OK?
I'm not sure why moving doesn't work - anyone else know????
Cheers,
Jane
Hmm - the plot thickens! On a 2.5 beta (2.4.70-414) I get the following on installing the ZenPack. After a bounce of zenhub and zopectl, the ZenPacks tab apparently shows the ZenPack as OK and the skins files and directories DO exist; however the bridge menus generate an error message saying that BridgeDeviceDetail doesn't exist.
I think this is slightly different from what tou and jmp have seen with 2.4.5??
I'll keep investigating.
Anyone else have any input?
Cheers,
Jane
On a 2.5 beta system, I have found that rebuilding the ZenPack in 2.5 environment and then adding the 2 object files, 2 plugin files and 2 skins files works. I have also added the BridgeMIB device class. I have NOT yet added the performance templates (I hope that isn't an issue).
Would anyone be able to test this 1.1 version on a 2.4.5 system to see if it resolves the problems there? File attached.
Thanks,
Jane
I deleted the old zenpack and added the attached zenpack you included. It installed without error:
INFO:zen.ZPLoader:Loading /usr/local/zenoss/ZenPacks/ZenPacks.skills1st.bridge-1 .1-py2.4.egg/ZenPacks/skills1st/bridge/objects/objects.xml
INFO:zen.AddToPack:End loading objects
INFO:zen.AddToPack:Processing links
INFO:zen.AddToPack:Loaded 1 objects into the ZODB database
INFO:zen.HookReportLoader:loading reports from:/usr/local/zenoss/ZenPacks/ZenPac ks.skills1st.bridge-1.1-py2.4.egg/ZenPacks/skills1st/bridge/reports
Unfortunately, I get No Interfaces found. Double check you have the correct collector plugin and you have remodeled. in the Bridged Interfaces tab.
2009-10-12 20:23:41 | WARNING | zen.ZenModeler | Get Data= {'setHWTag': 0, 'setHWSerialNumber': '\x00$\xf7\xd9\xe7\x80'} |
2009-10-12 20:23:41 | WARNING | zen.ZenModeler | Table Data= {} |
2009-10-12 20:23:41 | INFO | zen.ZenModeler | processing BridgeInterfaceMib for device 10.182.164.2 |
2009-10-12 20:23:41 | WARNING | zen.ZenModeler | Get Data= {} |
2009-10-12 20:23:41 | WARNING | zen.ZenModeler | Table Data= {'dot1dTpFdbEntry': {}, 'dot1dBasePortEntry': {}} |
2009-10-12 20:23:41 | WARNING | zen.ZenModeler | No SNMP response from 10.182.164.2 for the BridgeInterfaceMib plugin |
2009-10-12 20:23:41 | WARNING | zen.ZenModeler | Data= {} |
2009-10-12 20:23:41 | WARNING | zen.ZenModeler | Columns= {'.1': 'BasePort', '.2': 'BasePortIfIndex'} |
It appears this zenpack does not have the MIB for the Cisco 3750 switch?!?!?!
This installs and I only need to remodel the device for it to collect the data.
Great job, when can you perf templates?
Many thanks for trying the new version - it does look like something has changed to do with package format somewhere between 2.4.1 and 2.5.
With regard to your "No interfaces found" message, the switch has to support the BRDIGE-MIB (RFC 1493 / 4188). Cisco may have decided not to support this and replace with their own enterprise-specific MIBs (which the BRIDGE-MIB ZenPack doesn't support). To test, try using a simple snmpwalk command against the switch:
snmpwalk -v 1 -c <your community> <your switch> 1.3.6.1.2.1.17
This OID is the start of the bridge MIB. My suspicion is that snmpwalk will give no answers so I'm afraid your switch doesn't support the bridge MIB.
Please let me know the outcome - and thanks for testing the new build.
Cheers,
Jane
This gets stranger. I have deleted and reinstalled the 1.1 version of the ZenPack this morning. Immediately after install the ZenPack page shows that the ZenPack provides /Devices/Network/Switch/BridgeMIB and BridgeMIB shows as a suborganizer of Switch. Restart zenhub and zopectl and these change so that the ZenPack reports no objects being provided and there is no suborganiser under switch. event.log has a line saying:
WARNING zen.PrimaryPathObjectManager Tried to delete object id 'BridgeMIB' but didn't find it on /zport/dmd/Devices/Network/Switch
I would appreciate any other feedback either from 2.4.5 installs (there appears to have been 1 successful test so far) or from other testers of the 2.5 beta.
Cheers,
Jane
This bit is working-as-designed. I guess you also have Cisco collector plugins running which collect a serial number from a Cisco MIB?? The Bridge ZenPack assumed that you didn't have any enterprise-specific MIBs so had no access to a serial number so it provides the base MAC address of the switch.
What you might try is to change the order of your modeler plugins and run the BridgeDeviceMib plugin before your Cisco plugins - that should have the Cisco plugin overwrite my setting of the serial number. If you are not interested in setting the Tag field to the number of ports on the switch (which is the only other thing that the BridgeDeviceMib collector does) then omit this collector entirely - it shouldn't affect anything else.
BTW - please would you check that you can stop and start zenhub and zopectl and that the BridgeMIB device class still exists OK - see earlier append from me. I am finding in 2.5 that this object class disappears after a bounce.
Cheers,
Jane
I have opened ticket #5665 to cover these problems with the Bridge MIB on both 2.4.5 and 2.5.
Cheers,
Jane
Iinstalled the zenpack today without any installation issues. (I have a cisco 4506 switch) I then tried to move my existing switch from the /device/network/switch class to the new /device/network/switch/Bridgemib class. Thiis resulted in the error originally posted at the top of this thread. After reading the thread I deleted my switch device and added it as a new device under the bridgemib class. I am now getting the tollowing errors.
2009-10-23 03:57:25 | INFO | zen.Device | device name 'switch14' for ip '' |
2009-10-23 03:57:25 | INFO | zen.Device | setting performance monitor to localhost |
2009-10-23 03:57:25 | INFO | zen.Utils | Executing command: /opt/zenoss/bin/zendisc run --now -d switch14 --monitor localhost --deviceclass /Network/Switch/BridgeMIB --weblog |
2009-10-23 03:57:28 | INFO | zen.ZenDisc | Connecting to localhost:8789 |
2009-10-23 03:57:58 | ERROR | zen.ZenDisc | Timeout connecting to zenhub: is it running? |
2009-10-23 03:58:23 | INFO | zen.ZenDisc | Connected to ZenHub |
2009-10-23 03:58:23 | INFO | zen.ZenDisc | Looking for switch14 |
2009-10-23 03:58:23 | ERROR | zen.ZenDisc | Error: [Failure instance: Traceback (failure with no frames): Products.ZenHub.PBDaemon.RemoteException: Remote exception: exceptions.AttributeError: 'BridgeDevice' object has no attribute 'primaryAq'Traceback (most recent call last): File "/opt/zenoss/Products/ZenHub/PBDaemon.py", line 73, in inner return callable(*args, **kw) File "/opt/zenoss/Products/ZenHub/services/ModelerService.py", line 79, in remote_getDeviceConfig device = device.primaryAq() AttributeError: 'BridgeDevice' object has no attribute 'primaryAq' ] |
2009-10-23 03:58:23 | INFO | zen.ZenDisc | Scan time: 0.00 seconds |
2009-10-23 03:58:23 | INFO | zen.ZenDisc | Daemon ZenDisc shutting down |
2009-10-23 03:58:24 | INFO | zen.ZenDisc | zendisc shutting down |
2009-10-23 03:58:24 | ERROR | zen.DeviceLoader | Unable to add the device switch14 |
Follow Us On Twitter »
|
Latest from the Zenoss Blog » | Community | Products | Services Resources | Customers Partners | About Us | ||
Copyright © 2005-2011 Zenoss, Inc.
|
||||||||