[INFO] Show off your Weathermaps.

[zoemu]

impressive!!!

[nafets2]

In this Weathermap I used little graphs called stripgraphs that display the line activity over the past three hours (configurable iirc) and the current throughput. The scale is self-aligning, so you cannot compare one graph to another but if a line is dead or filled to the brim, you can see how long that's been going on. The stripgraphs are constructed by a little script that runs from the cron on the Cacti server. In fact they have nothing to do with Weathermap as such, but they use rrd's that Cacti makes. Look for 'stripgraph' in this forum and you will find out how to do this, just like I did.

Weathermap-CONNECTIONS.png (414.94 KiB) Viewed 8585 times

The lime names are the technical names of the connections that we have to use if we call our ISP. Furthermore I took the opportunity to put a sort of subtitle under every location (grey rectangles) because we use different names than our ISP. Since multi-line titles or subtitles in one NODE are not a function in Weathermap, let alone in different fonts/sizes/colors, they are just another borderless NODE with a LABEL in the same color as the 'main title', printed over the location box. Looks like subtitles, is not subtitles.

[nafets2]

I used the principle of putting a map in another map to make a Weathermap for an administrator who is off-site of our HQ. He also has a big screen, but he is not too interested in all the goings-on at HQ, so he requested a Weathermap just for his location.

Weathermap-DIS.png (360.77 KiB) Viewed 8579 times

I made him a Weathermap with a lot of 'his' stuff, which is not on any of 'our' Weathermaps at HQ because it's too detailed for us. His map incorporates the wireless map for his location which is also incorporated in an earlier combined map I posted. It also incorporates a small version of our overall network map. This is because he wants to be able to see if something major is going on at HQ. It could be that he suffers consequences of that.

Top left is our main internet connection, to the right of that the connection from HQ to his location. Below that is the overall network map from HQ. Further to the right is 'his' stuff and top right the AP's at his location. The one graph on the bottom left is a certain connection to a certain device he wants to keep a close eye on. The graph is exported every five minutes via the Gexport plugin, and incorporated as a static image.

All switches show temperature, VTP mode and version, (Cisco) licensing status, latency, memory use per switch in stack, role per switch in stack, powersupply status and fan status per switch in stack. Also traffic is displayed for the Portchannel as well as its members, because fibers can malfunction without Portchannels going offline.

[nafets2]

Last but not least the overall view of our network, which we use at HQ. In this map I exchanged 'green is good' for 'white is right' as much as I could. It should be mostly white and any color should attract attention, especially red of course.

Weathermap-NETWORK.png (426.83 KiB) Viewed 8578 times

This includes two datacenters (middle), surrounded by our locations with all of the switch-stacks. Every switch-stack shows CPU usage, temperature, (Cisco) stackwise and stackpower status and latency. We have a seperate Weathermap of only switches, which also show powersupply and fan status, VTP mode and status and more, as explained in my post before this one about the Weathermap for a separate site.

Mid-top is a representation of our accesspoints, with one being down, and the counter consequently going red. To the left of that a counter of wireless-clients, below that the number of clients really big, so we can easily see how busy it is. To the left of the big number is an area representing how full the corresponding DHCP-scopes are, with a little square per scope. We have a separate Weathermap with only all scopes plus their usage. Under the accesspoints is the number of clients connecting through WPA2 and WPA3 respectively.

To the far left are UPS with (battery)temperature, mains voltage, battery capacity, load and expected runtime. On some locations we have a central UPS, which we do not control nor monitor. On some scattered locations and in some equipmentrooms we have Netbotz to monitor temperature and humidity.

A big thank you to the developers that designed, programmed and maintain this amazing tool and keeping it alive in Cacti 1.x. I find it invaluable.

[Howie]

The floor plan map is very slick!