weathermap to show int status instead of traffic utilization

[Howie]

Step one is almost always: look in the cacti.log for Weathermap errors. The name of your rrd file makes me wonder if it's actually interface state information.

Step two is almost always: turn on DEBUG logging and wait 5 minutes. Then have a look in the logs for lines with ReadData in them. You'll see what data is being fetched from the rrd files. Don't forget to turn it off, or it'll fill your disk.

Then, for this specific case, I would change the scale lines to not require exactly 1 and 2. RRDtool will average a little when the state changes, so you'll get 1.7 or something at times. Also, by using the 'tags' keystyle and some text on the end of the lines, you can make the legend nicer.

Code: Select all

SCALE DEFAULT 0 100 92 255 92 unknown
SCALE DEFAULT 0.5 1.5 92 255 92 UP
SCALE DEFAULT 1.5 2.5 239 41 50  DOWN

KEYSTYLE DEFAULT tags

[aftershocks]

Thanks Howie for your reply..

Looking at the logs from debug, I see the following for the DS..

UP

root@sfo-net-mon02:/var/log/cacti# cat cacti.log | grep 25100 | grep output
07/21/2016 11:25:28 AM - CMDPHP: Poller[0] Host[9] DS[25100] SNMP: v2: 10.55.24.11, dsname: int_status, oid: .1.3.6.1.2.1.2.2.1.8.1, output: 1
07/21/2016 11:30:28 AM - CMDPHP: Poller[0] Host[9] DS[25100] SNMP: v2: 10.55.24.11, dsname: int_status, oid: .1.3.6.1.2.1.2.2.1.8.1, output: 1

DOWN

root@sfo-net-mon02:/var/log/cacti# cat cacti.log | grep 25101 | grep output
07/21/2016 11:25:28 AM - CMDPHP: Poller[0] Host[9] DS[25101] SNMP: v2: 10.55.24.11, dsname: int_status, oid: .1.3.6.1.2.1.2.2.1.8.2, output: 2
07/21/2016 11:30:28 AM - CMDPHP: Poller[0] Host[9] DS[25101] SNMP: v2: 10.55.24.11, dsname: int_status, oid: .1.3.6.1.2.1.2.2.1.8.2, output: 2

So I think it's grabbing the correct DS and output...

I made the suggested changes..

SCALE DEFAULT 0 100 92 255 92 unknown
SCALE DEFAULT 0.5 1.5 92 255 92 UP
SCALE DEFAULT 1.5 2.5 239 41 50 DOWN

KEYSTYLE DEFAULT tags

But here is the output of the legend, and now, i'm finally getting colour.. I didn't make any changes to the nodes and links... But they are all green even though the link from partner01 to DG is down...

Is the line "SCALE DEFAULT 0 100 92 255 92 unknown" making everything green?

*scratch head*...

[aftershocks]

Also, is there also a way to make the links clickable like default to zoom into the traffic after these modifications?

Thanks!

[aftershocks]

Hummmmm.... it says "had no valid data, according to WeatherMapDataSource_rrd".. I checked the file from the /rra directory and it exist..

root@sfo-net-mon02:/var/lib/cacti/rra# ls dca-net-partner01_int_status_25101.rrd
dca-net-partner01_int_status_25101.rrd
root@sfo-net-mon02:/var/lib/cacti/rra# pwd
/var/lib/cacti/rra

But at the same time, I can see the output is correct..

07/21/2016 11:25:28 AM - CMDPHP: Poller[0] Host[9] DS[25101] SNMP: v2: 10.55.24.11, dsname: int_status, oid: .1.3.6.1.2.1.2.2.1.8.2, output: 2

07/21/2016 09:55:52 AM - WEATHERMAP: Poller[0] WARNING: [Map 4] interface-status.conf: ReadData: LINK dca-net-partner01-DG, target: dca-net-partner01_int_status_25101.rrd on config line 53 of /usr/share/cacti/site/plugins/weathermap/configs/interface-status.conf had no valid data, according to WeatherMapDataSource_rrd
07/21/2016 10:00:52 AM - WEATHERMAP: Poller[0] WARNING: [Map 4] interface-status.conf: ReadData: LINK dca-net-partner01-DG, target: gauge:/var/lib/cacti/rra/dca-net-partner01_int_status_25101.rrd on config line 53 of /usr/share/cacti/site/plugins/weathermap/configs/interface-status.conf had no valid data, according to WeatherMapDataSource_rrd
07/21/2016 10:05:52 AM - WEATHERMAP: Poller[0] WARNING: [Map 4] interface-status.conf: ReadData: LINK dca-net-partner01-DG, target: gauge:/var/lib/cacti/rra/dca-net-partner01_int_status_25101.rrd on config line 56 of /usr/share/cacti/site/plugins/weathermap/configs/interface-status.conf had no valid data, according to WeatherMapDataSource_rrd
07/21/2016 10:10:52 AM - WEATHERMAP: Poller[0] WARNING: [Map 4] interface-status.conf: ReadData: LINK dca-net-partner01-DG, target: gauge:/var/lib/cacti/rra/dca-net-partner01_int_status_25101.rrd on config line 62 of /usr/share/cacti/site/plugins/weathermap/configs/interface-status.conf had no valid data, according to WeatherMapDataSource_rrd
07/21/2016 10:15:52 AM - WEATHERMAP: Poller[0] WARNING: [Map 4] interface-status.conf: ReadData: LINK dca-net-partner01-DG, target: gauge:/var/lib/cacti/rra/dca-net-partner01_int_status_25101.rrd on config line 62 of /usr/share/cacti/site/plugins/weathermap/configs/interface-status.conf had no valid data, according to WeatherMapDataSource_rrd

.... And these to follow...

07/21/2016 11:25:51 AM - WEATHERMAP: Poller[0] DEBUG: [ReadData@Weathermap.class.php:922] [Map 4] interface-status.conf: ReadData: New Target: gauge:/var/lib/cacti/rra/dca-net-partner01_int_status_25101.rrd:int_status:int_status
07/21/2016 11:25:51 AM - WEATHERMAP: Poller[0] DEBUG: [wmrrd_read_from_real_rrdtool@WeatherMapDataSource_rrd.php:362] [Map 4] interface-status.conf: RRD ReadData: Running: /usr/bin/rrdtool fetch /var/lib/cacti/rra/dca-net-partner01_int_status_25101.rrd AVERAGE --start now-800 --end now
07/21/2016 11:30:53 AM - WEATHERMAP: Poller[0] DEBUG: [ReadData@Weathermap.class.php:922] [Map 4] interface-status.conf: ReadData: New Target: gauge:/var/lib/cacti/rra/dca-net-partner01_int_status_25101.rrd:int_status:int_status
07/21/2016 11:30:53 AM - WEATHERMAP: Poller[0] DEBUG: [wmrrd_read_from_real_rrdtool@WeatherMapDataSource_rrd.php:362] [Map 4] interface-status.conf: RRD ReadData: Running: /usr/bin/rrdtool fetch /var/lib/cacti/rra/dca-net-partner01_int_status_25101.rrd AVERAGE --start now-800 --end now
07/21/2016 11:35:50 AM - WEATHERMAP: Poller[0] DEBUG: [ReadData@Weathermap.class.php:922] [Map 4] interface-status.conf: ReadData: New Target: gauge:/var/lib/cacti/rra/dca-net-partner01_int_status_25101.rrd:int_status:int_status
07/21/2016 11:35:50 AM - WEATHERMAP: Poller[0] DEBUG: [wmrrd_read_from_real_rrdtool@WeatherMapDataSource_rrd.php:362] [Map 4] interface-status.conf: RRD ReadData: Running: /usr/bin/rrdtool fetch /var/lib/cacti/rra/dca-net-partner01_int_status_25101.rrd AVERAGE --start now-800 --end now
07/21/2016 11:40:55 AM - WEATHERMAP: Poller[0] DEBUG: [ReadData@Weathermap.class.php:922] [Map 4] interface-status.conf: ReadData: New Target: gauge:/var/lib/cacti/rra/dca-net-partner01_int_status_25101.rrd:int_status:int_status
07/21/2016 11:40:55 AM - WEATHERMAP: Poller[0] DEBUG: [wmrrd_read_from_real_rrdtool@WeatherMapDataSource_rrd.php:362] [Map 4] interface-status.conf: RRD ReadData: Running: /usr/bin/rrdtool fetch /var/lib/cacti/rra/dca-net-partner01_int_status_25101.rrd AVERAGE --start now-800 --end now
07/21/2016 11:45:51 AM - WEATHERMAP: Poller[0] DEBUG: [ReadData@Weathermap.class.php:922] [Map 4] interface-status.conf: ReadData: New Target: gauge:/var/lib/cacti/rra/dca-net-partner01_int_status_25101.rrd:int_status:int_status
07/21/2016 11:45:51 AM - WEATHERMAP: Poller[0] DEBUG: [wmrrd_read_from_real_rrdtool@WeatherMapDataSource_rrd.php:362] [Map 4] interface-status.conf: RRD ReadData: Running: /usr/bin/rrdtool fetch /var/lib/cacti/rra/dca-net-partner01_int_status_25101.rrd AVERAGE --start now-800 --end now
07/21/2016 11:50:52 AM - WEATHERMAP: Poller[0] DEBUG: [ReadData@Weathermap.class.php:922] [Map 4] interface-status.conf: ReadData: New Target: gauge:/var/lib/cacti/rra/dca-net-partner01_int_status_25101.rrd:int_status:int_status
07/21/2016 11:50:52 AM - WEATHERMAP: Poller[0] DEBUG: [wmrrd_read_from_real_rrdtool@WeatherMapDataSource_rrd.php:362] [Map 4] interface-status.conf: RRD ReadData: Running: /usr/bin/rrdtool fetch /var/lib/cacti/rra/dca-net-partner01_int_status_25101.rrd AVERAGE --start now-800 --end now
07/21/2016 11:55:55 AM - WEATHERMAP: Poller[0] DEBUG: [ReadData@Weathermap.class.php:922] [Map 4] interface-status.conf: ReadData: New Target: gauge:/var/lib/cacti/rra/dca-net-partner01_int_status_25101.rrd:int_status:int_status
07/21/2016 11:55:55 AM - WEATHERMAP: Poller[0] DEBUG: [wmrrd_read_from_real_rrdtool@WeatherMapDataSource_rrd.php:362] [Map 4] interface-status.conf: RRD ReadData: Running: /usr/bin/rrdtool fetch /var/lib/cacti/rra/dca-net-partner01_int_status_25101.rrd AVERAGE --start now-800 --end now
07/21/2016 12:00:48 PM - WEATHERMAP: Poller[0] DEBUG: [ReadData@Weathermap.class.php:922] [Map 4] interface-status.conf: ReadData: New Target: gauge:/var/lib/cacti/rra/dca-net-partner01_int_status_25101.rrd:int_status:int_status
07/21/2016 12:00:48 PM - WEATHERMAP: Poller[0] DEBUG: [wmrrd_read_from_real_rrdtool@WeatherMapDataSource_rrd.php:362] [Map 4] interface-status.conf: RRD ReadData: Running: /usr/bin/rrdtool fetch /var/lib/cacti/rra/dca-net-partner01_int_status_25101.rrd AVERAGE --start now-800 --end now
07/21/2016 12:05:54 PM - WEATHERMAP: Poller[0] DEBUG: [ReadData@Weathermap.class.php:922] [Map 4] interface-status.conf: ReadData: New Target: gauge:/var/lib/cacti/rra/dca-net-partner01_int_status_25101.rrd:int_status:int_status
07/21/2016 12:05:54 PM - WEATHERMAP: Poller[0] DEBUG: [wmrrd_read_from_real_rrdtool@WeatherMapDataSource_rrd.php:362] [Map 4] interface-status.conf: RRD ReadData: Running: /usr/bin/rrdtool fetch /var/lib/cacti/rra/dca-net-partner01_int_status_25101.rrd AVERAGE --start now-800 --end now
07/21/2016 12:05:57 PM - WEATHERMAP: Poller[0] DEBUG: [wmrrd_read_from_real_rrdtool@WeatherMapDataSource_rrd.php:455] [Map 1] quotient-dca-sfo-sjc-las.conf: RRD ReadDataFromRealRRD: Returning (6.2510115932e+06,2.7208264896e+06,1469127600)

[Howie]

That's odd with the scale - what's supposed to happen is the smallest matching scale line will win. Which version of weathermap is this?

For the zoom - you add INFOURL lines for each link with the URL of the graph page to show.

Have another look at those logs, around the DEBUG lines you have got with grep, there should be the actual data retrieved from rrdtool (that is, literally, the text lines of output).

[aftershocks]

Hi Howie,

I have version 0.98 for Weathermap... Thanks for the INFOUL info!

Is this what I'm suppose to be looking at? it's reading 12.5%... I don't know why it's reading percentage rather than integers?..

Hummm...

07/21/2016 12:25:52 PM - WEATHERMAP: Poller[0] WARNING: [Map 4] interface-status.conf: NewColourFromPercent: Scale DEFAULT doesn't include a line for 12.5% while drawing item dca-net-partner01-DG [WMWARN29]
07/21/2016 12:25:52 PM - WEATHERMAP: Poller[0] WARNING: [Map 4] interface-status.conf: NewColourFromPercent: Scale DEFAULT doesn't include a line for 12.5% while drawing item dca-net-partner01-DG [WMWARN29]
07/21/2016 12:25:52 PM - WEATHERMAP: Poller[0] WARNING: [Map 4] interface-status.conf: NewColourFromPercent: Scale DEFAULT doesn't include a line for 6.25% while drawing item dca-net-partner01-WAG [WMWARN29]
07/21/2016 12:25:52 PM - WEATHERMAP: Poller[0] WARNING: [Map 4] interface-status.conf: NewColourFromPercent: Scale DEFAULT doesn't include a line for 6.25% while drawing item dca-net-partner01-WAG [WMWARN29]

[Howie]

Because you said BANDWIDTH 16. So it's taking the value from the rrd file, and figuring out the percentage "utilisation" from 16 maximum. Try 'BANDWIDTH 100' (or USESCALE with absolute - I don't know the syntax offhand though and the BANDWIDTH 100 will work).

[aftershocks]

Holy freaking smokes! It worked! You are a genius, Howie! Thanks!!

I just don't know how to get the "unknown" status to work??

But for anyone who is trying to achieve the same thing as me, here's the scenario so you don't have to re-read the thread:

Link status between partner01 and DG is DOWN (RED)
Link status between partner01 and WAG is UP.. (GREEN)

Bandwidth is displayed as the label and not the interface status value (1 or 2)

Thanks so much Howie!!!

Here is the configs:

SCALE DEFAULT 0.5 1.5 92 255 92 UP
SCALE DEFAULT 1.5 2.5 239 41 50 DOWN

KEYSTYLE DEFAULT tags

SET key_hidezero_DEFAULT 1

# End of global section


# TEMPLATE-only NODEs:
NODE DEFAULT
MAXVALUE 100


# TEMPLATE-only LINKs:
LINK DEFAULT
BANDWIDTH 100M


# regular NODEs:
NODE dca-net-partner01
LABEL dca-net-partner01
ICON images/Router.png
LABELOFFSET 0 33
POSITION 277 354

NODE DG
LABEL DG
ICON images/Router.png
LABELOFFSET 0 33
POSITION 538 204

NODE WAG
LABEL WAG
ICON images/Router.png
LABELOFFSET 0 33
POSITION 584 363

NODE secret_node_dg
TARGET /var/lib/cacti/rra/dca-net-partner01_traffic_in_2573.rrd
POSITION 10000 2000

NODE secret_node_wag
TARGET /var/lib/cacti/rra/dca-net-partner01_traffic_in_2572.rrd
POSITION 200 200


# regular LINKs:
LINK dca-net-partner01-DG
INBWFORMAT {node:secret_node_dg:bandwidth_in:%.2k}
OUTBWFORMAT {node:secret_node_dg:bandwidth_out:%.2k}
TARGET gauge:/var/lib/cacti/rra/dca-net-partner01_int_status_25101.rrd:int_status:int_status
NODES dca-net-partner01 DG
BANDWIDTH 100

LINK dca-net-partner01-WAG
INBWFORMAT {node:secret_node_wag:bandwidth_in:%.2k}
OUTBWFORMAT {node:secret_node_wag:bandwidth_out:%.2k}
TARGET gauge:/var/lib/cacti/rra/dca-net-partner01_int_status_25100.rrd:int_status:int_status
NODES dca-net-partner01 WAG
BANDWIDTH 100

[aftershocks]

Hey Howie,

Just curious, when is it a time when the link is at an "unknown" state?

Thanks.

[Howie]

I think it depends on the vendor and device, but I've certainly seen other states on Cisco Catalyst switches - err-disabled shows up as either 'unknown' or 'testing', from memory.

[Pucho]

I think it depends on the vendor and device, but I've certainly seen other states on Cisco Catalyst switches - err-disabled shows up as either 'unknown' or 'testing', from memory.

Hi man, thanks in advance for such a great plugin.

I've been setting up a new cacti installation and creating weathermaps and here comes my question

What do you think will be the best way to achieve the IfOperStatus stuff.

I don't really want to get hundreds of graphs from the status plugin because they are quite useless to my purpose but I do want to show ports up/down/whatever without overpopulating the graph tree view with these graphs.

I did try weathermap TARGET snmp:community:host:in_oid:out_oid and it works just fine BUT, as you said before it only supports v1 and I have a nice mix of v2 and v3.

I thought It might be easy to use the status plugin (which is what I'm using so far) and to hide somehow these graphs from Graph Tree view but I don't know if that's even possible.

Do you think that targeting traffic.rrd files and using an SCALE 0 0 for down and 0.1 100 for up will do it? What are the odds to hit a false positive?

Any thought?

Cheers

[Howie]

I prefer a method that doesn't use rrd files, because they take a couple of polls to "react" to change and you get odd values at the changeover point. SNMP is definitely better. I didn't know there was an interface status plugin. If it writes to the database, that should be simple enough to add as a new data source - what is it actually called?

SNMP v2c and v3 aren't implemented mainly because I couldn't think of a nice way to have all the necessary information in a target string v3 especially really needs something like a named 'snmp parameter set' and have the target refer to that instead (username, auth password, priv password, crypto algorithms etc). Any ideas?

Actually, for 2c, it would just be a different prefix snmp2 vs snmp, I think. The rest is the same. I will try to get that into the next release.

[Pucho]

Thanks for your answer. My mistake, I meant status graph template, not plugin, that's why I don't like it. 60-70 switches * 24/48 ports it's like thousands of useless graphs to me.

Why not just like the info.php I've seen around here? it does the job. that could fit onto external_script. It queries cacti for every host details and then does the snmpwalk.

Do you want something like TARGET snmp:v1/2/3:auth:priv:host:in_oid:out_oid and maybe "SET" some parameters like auth and priv under the conf file?

Or ...if you want it to be independent of reading parameters from anywhere

TARGET snmp(1 default):community:host:in_oid:out_oid
TARGET snmp2:community:host:in_oid:out_oid
TARGET snmp3:username:auth(def md5):priv(def des56):host:in_oid:out_oid -> are you planning to support all of them? md5/sha, des/3des/aes ? On the other hand it is not nice store the password on plain text as some mrtg version does, please keep that in mind

EDIT: If you need a beta tester, let me know.

[Howie]

Thanks for your answer. My mistake, I meant status graph template, not plugin, that's why I don't like it. 60-70 switches * 24/48 ports it's like thousands of useless graphs to me.

Why not just like the info.php I've seen around here? it does the job. that could fit onto external_script. It queries cacti for every host details and then does the snmpwalk.

Do you want something like TARGET snmp:v1/2/3:auth:priv:host:in_oid:out_oid and maybe "SET" some parameters like auth and priv under the conf file?

Or ...if you want it to be independent of reading parameters from anywhere

TARGET snmp(1 default):community:host:in_oid:out_oid
TARGET snmp2:community:host:in_oid:out_oid
TARGET snmp3:username:auth(def md5):priv(def des56):host:in_oid:out_oid -> are you planning to support all of them? md5/sha, des/3des/aes ? On the other hand it is not nice store the password on plain text as some mrtg version does, please keep that in mind

EDIT: If you need a beta tester, let me know.

It's the plaintext passwords I don't like, also. And maintaining it all in two+ places.

I thought about this a little yesterday, and came up with this:

1) new TARGET prefixes for snmpv1:, snmpv2c: and snmpv3:

2) you *can* specify everything like that, but you can also use a 'profile name', which fetches the information out of a series of SET variables like snmp_PROFILE1_community, snmp_PROFILE1_hostname etc, and then use:

TARGET snmpv3:PROFILE1:.1.3.1.3.3.3:.1.4.1.6.5.4

3) A special variable to have weathermap pull the information for a profile from Cacti's database: snmp_PROFILE1_import=host_id so that the information can stay up to date, and anyone reading the map config doesn't have to know all your credentials. Because this is optional, the rest is still useful to non-Cacti weathermap users.

I'm not sure if the hostname should be part of the profile or not though - in many networks the snmp credentials are shared between many hosts, so having one profile for all of them would be useful.

What do you think? I think it's pretty simple to implement.

[Pucho]

It's the plaintext passwords I don't like, also. And maintaining it all in two+ places.

I thought about this a little yesterday, and came up with this:

1) new TARGET prefixes for snmpv1:, snmpv2c: and snmpv3:

2) you *can* specify everything like that, but you can also use a 'profile name', which fetches the information out of a series of SET variables like snmp_PROFILE1_community, snmp_PROFILE1_hostname etc, and then use:

TARGET snmpv3:PROFILE1:.1.3.1.3.3.3:.1.4.1.6.5.4

3) A special variable to have weathermap pull the information for a profile from Cacti's database: snmp_PROFILE1_import=host_id so that the information can stay up to date, and anyone reading the map config doesn't have to know all your credentials. Because this is optional, the rest is still useful to non-Cacti weathermap users.

I'm not sure if the hostname should be part of the profile or not though - in many networks the snmp credentials are shared between many hosts, so having one profile for all of them would be useful.

What do you think? I think it's pretty simple to implement.

That sounds good!

You are right. They are usually shared, but it is also normal to have different sets of credentials per customer for example, thinking on large deployments.
I wouldn't include the hostname, if we are talking about shared profiles in most scenarios.
Will you be able to create as many profiles as you want?

How would you store the credentials? I've never used wm standalone but I haven't seen any option to create set of variables or parameters apart from the .conf files. Will that include a new menu option on wm editor? What are the options?