Zenoss Core 4.2.5 Interface Monitoring

7 posts / 0 new
Last post
Tepz
Tepz's picture
Offline
Last seen: 1 week 1 day ago
Joined: 04/04/2017 - 15:31
Posts: 4
Zenoss Core 4.2.5 Interface Monitoring

Hello all,

 

I could not find the answer to this simple question (which could lead to other not so simple questions).

I currently am using SNMP v2c to monitor a Cisco 7010 (Nexus) with Zenoss Core 4.2.5.  I get no graph data via throughput, packet, or errors selections.  Is this by design (to make us buy Zenoss Enterprise for the Cisco ZenPack)?

If so, is there a community zenpack that does something similar?

If not, I will open a different thread for troubleshooting.

 

Thanks in advance!

Jcurry
Jcurry's picture
Offline
Last seen: 3 days 7 hours ago
Joined: 01/02/2014 - 13:04
Posts: 407
This should work perfectly

This should work perfectly well with the free Zenoss Core provided your SNMP community names are configured in the target device and in Zenoss.

If you inspect your Cisco device in Zenoss, does it have Interface Components in the left-hand menu?  If yes, then some SNMP communications have been sccessful to the device; if not, then the issue is probably community names.

Zenoss has a default SNMP configuration to use a community name of public to all devices.  This can be changed for a device class (like Devices -> Network -> Router -> Cisco), in which case, all devices in that class will inherit the value.  If you want a different community name for a specific device then you can have a device-level override. 

From the main page for the test device in Zenoss, select Configuration Properties. zSnmpCommunity and zSnmpVer are the key things you need to match with what is configured in your router.

I would use the snmpwalk utility from a command-line window to do some testing so, for device fred, using snmp v2c with a community name of mycomm, try:

snmpwalk -v 2c -c mycomm fred

Cheers,

Jane

 

Tito
Tito's picture
Offline
Last seen: 2 weeks 2 days ago
Joined: 04/12/2017 - 14:55
Posts: 2
zenoss

I have a thesis on the topic of configuring a network analyzer zenoss case under proxmox.
The zenoss that I downloaded refuses to settle on proxmox and I do not know why
Please help me link or tuto I am taker of everything.
Your help will see me much pleasure.

Tepz
Tepz's picture
Offline
Last seen: 1 week 1 day ago
Joined: 04/04/2017 - 15:31
Posts: 4
Thank  you, Jane.

Thank  you, Jane.

 

That is how I have it configured (v2c) and I do see the interfaces.  I believe it is an issue with zenperfsnmp, as I see zenperfsnmp heartbeat stopped alerts every 5 minutes, but I cannot find the reason.  The service is up and running it in debug mode shows no errors.

Last night I was able to get it to graph for about 4 hours.  At 8 PM it stopped graphing and RRD files stop at 8 PM exactly as well.  What is the process/service that writes these RRD files and what more can I troubleshoot that?

 

Tepz
Tepz's picture
Offline
Last seen: 1 week 1 day ago
Joined: 04/04/2017 - 15:31
Posts: 4
zenperfsnmp.log

In the zenperfsnmp.log, I am seeing quite a bit of the following:

WARNING zen.zenperfsnmp: Error reading value

ERROR zen.zenperfsnmp: SNMP get returned empty value

According to this article, I might need to add a ".0 in the OIDs for each datasource in the template for that device."   Though I'm not sure how exactly to do that.

http://zenoss-users.zenoss.narkive.com/YChdEGZ1/empty-graphs-upon-new-install-of-zenoss-3-2#post2

Is this why I am seeing the localhost zenperfsnmp heartbeat failures consistently?

Am I barking up the wrong tree?  Why did it work for a few short hours?

Tepz
Tepz's picture
Offline
Last seen: 1 week 1 day ago
Joined: 04/04/2017 - 15:31
Posts: 4
More info

One thing to add is when I issue the command manually:

zenperfsnmp run -v10 -d devicename

One of the final DEBUG messages are:

zen.pbclientfactory: Lost connection to 127.0.0.1:8789 - [Failure instance: Traceback (failure with no frames): <class 'twisted.internet.error.ConnectionLost'>: Connection to the other side was lost in a non-clean fashion: Connection lost.

]

Any idea what this is?

Jcurry
Jcurry's picture
Offline
Last seen: 3 days 7 hours ago
Joined: 01/02/2014 - 13:04
Posts: 407
Hi Tepz,

Hi Tepz,

A number of things here....

If you did manage to see graph data for 4 hours, that suggests that you don't have a fundamental SNMP communications problem - unless you have an auto configuration tool (puppet? chec?) that runs around and reconfigures lots of things at 8 pm?  Or a firewall rule changes then?

In the main page for each device, it should show when it was last modeled - is this updated regularly?  Every 12 hours be default?

zenperfsnmp is the man getting the performance data for you and lots of zenperfsnmp heartbeat events is bad news.  zenperfsnmp gathers the data and writes to the RRD files.  Is your Zenoss server machine short on memory? CPU? disk?  Are any other Zenoss daemons showing heartbeat issues?

 

The:

WARNING zen.zenperfsnmp: Error reading value

ERROR zen.zenperfsnmp: SNMP get returned empty value

messages are suggesting that your target devices are not responding, especially the ERROR message.  This points more to taget issues than Zenoss issues.

For interface traffic, do not add .0 to the OID.  interfaces are components of a device ie. potentially lots of them.  SNMP gets data for each different interface based on the last part of the OID - the modeler process works out what that index is and automatically uses it when running the template for interface information.  Where the ".0" bit can come in is with templates that use SNMP to get SCALAR data from a device - for example, there is only one answer to "what is your total RAM" - it is represented in SNMP as a scalar type and a template using that OID would then need the ".0" on the end.  Not relevant for interfaces / filesystems or any other component templates.

Ignore the nasty message about "Connection to the other side was lost in a non-clean fashion" - various Zenoss daemons have done this forever and it is actually nothing to worry about.

Cheers,

Jane

 

Log in to post comments