[INFO] Show off your Weathermaps.

[feds]

We currently use weathermap to so us which ports are operator status up and down.

[zoemu]

Our Simple Network map

[zoemu]

We currently use weather-map to so us which ports are operator status up and down.

Sorry if I'm too bold, But I'm trying to Implement something similar, and I would like to know if you have an script or a program, and how the status is retrieved and stored....

Thank you for your Guidance


LA

[streaker69]

We currently use weather-map to so us which ports are operator status up and down.

Sorry if I'm too bold, But I'm trying to Implement something similar, and I would like to know if you have an script or a program, and how the status is retrieved and stored....

Thank you for your Guidance


LA

If you go back a couple of posts before his, you'll see that I posted some brief instructions on how to accomplish that.

[cjlove72]

Here's my latest weathermap which provides a 'dashboard' of our SAN Infrastructure.

This is based on our Cisco MDS-9509 SAN Directors to provide read/write SAN throughput, port status and VSAN membership of all ports belonging to our FC and SATA storage arrays, ISLs, Backup Servers, Tape Libraries etc.

The 'Dashboard table' is actually an Excel table, saved as a JPG and used as the Weathermaps background. I then just overlay the various nodes on the weathermap to fit into the table fields.

The config for this weathermap is over 4000 lines of code, but I have all the node info (e.g. names, positions, graph ids, rrd ids etc) in an excel spreadsheet and then use various simple formulas in excel to generate the actual code...so adding a new line (or ten!) only takes 5 minutes to add it into the excel spreadsheet, then a simple copy and paste into the weathermap config and it'll all done

I've said it before and I'll say it again....I *LOVE* this product...great work guys.

Cheers,

Chris

[mcutting]

Here's my latest weathermap which provides a 'dashboard' of our SAN Infrastructure.

This is based on our Cisco MDS-9509 SAN Directors to provide read/write SAN throughput, port status and VSAN membership of all ports belonging to our FC and SATA storage arrays, ISLs, Backup Servers, Tape Libraries etc.

The 'Dashboard table' is actually an Excel table, saved as a JPG and used as the Weathermaps background. I then just overlay the various nodes on the weathermap to fit into the table fields.

The config for this weathermap is over 4000 lines of code, but I have all the node info (e.g. names, positions, graph ids, rrd ids etc) in an excel spreadsheet and then use various simple formulas in excel to generate the actual code...so adding a new line (or ten!) only takes 5 minutes to add it into the excel spreadsheet, then a simple copy and paste into the weathermap config and it'll all done

I've said it before and I'll say it again....I *LOVE* this product...great work guys.

Cheers,

Chris

Chris,

I use the *EXACT* same method of fleshing out my Dashboard in Excel, saving it as a JPG, and then overlaying WMAP data in it. I would be *very* interested in your spreadsheet with formulas, if you are willing to post ?

Thanks

[cjlove72]

No worries...happy to contribute what I've learned so far!

I've attached a sample spreadsheet with a cutdown version of the Dashboard that I'm using at the moment.

There are 4 sheets as follows:-


SAN Table
This is the table that I use to create a JPEG from...then copy it down to my Cacti server and use this as a background for the Weathermap.

Switches
This is a table containing RRD and Graph IDs for both Throughput and Status data sources (they are currently seperate, although I'm planning to merge them at some point).

SAN Table details
This is where I specify each of the ports that I want to be displayed on the dashboard.

For each port, I define a Read Traffic node, Write Traffic Node, VSAN node and Status node. You specify the switch name and port in columns A and B and it performs a VLOOKUP from the Switches worksheet to populate the correct Graph/RRD ID on the other columns (e.g. Columns G and H).

I specify the absolute position of the uppermost node in each of the tables and the other nodes are positioned relative to this, which makes it easy to add new rows to the tables.

So columns A to P supply all the info required for the Weathermap config. Columns T to BC then create the actual Weathermap code, although this isn't in a format that's easily usable...

SAN Table conf
This worksheet builds up the Weathermap config file. Cells A1 to A85 are static and define my SCALEs, default NODE and LINK parameters etc.

Cells A86 and below use the INDEX function to pull the code from the SAN Table details worksheet. Once there is no more code to be generated, the value in column A is 0...so the code from A1 to the last value (in the attached workbook it's A1:A805) contains the entire code required for the Weathermap. Just copy and paste this into a new (or over an existing) config file and the next time the poller runs it'll get created.

The beauty of this is that to add new entries into the Dashboard only requires adding new values into Columns A to P in the SAN Table details worksheet. The code is then generated in columns T:BC and automatically populated into column A in the SAN Table Conf worksheet.

Copy and paste this into your Weathermap and voila...updated dashboard!

I also use exactly the same process for generating my view of our Cisco MDS-9509 SAN Directors, except the background is a Visio diagram using the official Cisco MDS stencils, so we can specify the exact configuration of the switching modules.

Hope you find this useful...let me know if you make any improvements to it

Cheers,

Chris

[Howie]

I've just written a chunk of perl to generate weathermap config sections for these "port-map" style maps. It uses the Cacti database to assign the correct graph as a popup for each port, and uses Weathermap's SNMP data source to query the port status directly, so you don't need to modify interface.xml

It's not exactly plug&play right now, but I'll clean it up and post it. It makes a nice demo of templates and a few other things, too.

[mgupta]

Yet another w-map! Love the plugin

[Lawrance]

how can I draw a rectangle-free node, like a circular node that can represent a status.

[cjlove72]

Hi,

You use the ICON parameter, without a LABEL (so the actual value isn't displayed) and in conjunction with a SCALE that colours the icon depending on it's status, e.g.

SCALE IFSTATUS 0 1.5 0 255 0 Up
SCALE IFSTATUS 1.5 2.5 255 0 0 Down

NODE NODE1_STATUS
USESCALE IFSTATUS
ICON 15 15 round
TARGET gauge:/cacti-0.8.7c/rra/node1.rrd:int_status:-

Cheers,

Chris

[Howie]

And (just to fill in the last bit), 'round' is one of the built-in 'artificial' icons - along with box, rbox and others. Check the ICON section in the manual.

[BorisL]

Sample Datacenter weathermap.
Links between routers (actual interface names, rrd, etc) are found automaticall using simple pre-plugin.

User write

Code: Select all

LINK nodeXXX-nodeYYY
        NODES nodeXXX nodeYYY

Everything else is done using TEMPLATES and plugin mentioned above.

[Banty Rooster]

My boss accused me of being obsessed so I sent him a link to feds post above.

This one of our core routers. Putting an actual link to each building would've been cluttered and hard to read with 70+ arrows going every which way. I'm still trying to come up with a good way to dynamically build an index for the interface mapping. As it is now you have to hover over the link to see which building it goes to.

All of the ports are sub nodes to the module node so the modules can be moved around and copied with ease if necessary. This one took me about 8 hours to complete. The other core 6500 took me under an hour and a half.

Oh, and the idiot lights on the fan don't work.... yet.

[DLNoah]

I'm a bit of a "information at my fingertips" freak, so I wanted something that would give me a detailed dashboard of all of my WISP access point information. So, by virtue of the dsstats and snmp datasources, and some creative abuse of the static: target for comparing signals, I came up with this.

The signal/cur column is color coded based on the amount that the cur signal is worse than the average signal. Less than 8dB worse -> green, 8-12dB worse -> yellow, more than 12dB worse -> red. If the current signal is better than the average signal, I'm forcing that to clip to 0 (since scales can't be below 0 right now). Very kludgy change in the code though, and I've heard that 0.97 will allow scales to go below zero, so I'm looking forward to getting to un-break the code.