It seems that if I add a device in multiple maps, the Dude creates multiple different devices with that same IP address in the system.
So, if DEVICE1 is located on three maps and it goes down, I will get three different DOWN notices. There will also be three separate items pointing to DEVICE1 in the devices list & outages list.
It would be nice the the program were to see that each additional instance of the device was just a pointer to the original one.
Thanks.
You can make each device monitor different services if duplicate notifications and outages is a problem, use static items on map if duplicate entries in device list is a problem.
The question is why would you want to add same device on many maps?
If there is a “best practices” document on setting up Dude, please let me know.
Since I didn’t find one, I created maps in the best way I could think.
Here’s a quick overview of my network. I have a public Class C that I’ve divided into two /25. I also use multiple private 10.10.x.y/24 for intermediary wireless devices.
At the top level for the public /25, the maps shows all machines on that subnet, which includes wireless clients. At a quick glance at this top level, I can see which of my paying customers are down.
However, in reality, the network topology is as such. Top level router to public /25 subnet → WL PtP backhaul → router in Tower → Access Point (1,2,3) → CPE for the client → client home router.
The routers have public IP addresses, all the stuff in-between have private IPs in subnets relating to their physical location.
I have my maps set that the wireless devices on the private subnet are reference using submaps. So, a client with IP address public.100 will appear at my top level map and also on the submap that has the wireless CPE. In that wireless submap, I have to manually add the client device with public.100 since it is not a part of that subnet but is critical in correctly depicting the physical map.
Sorry if I don’t come as completely clear; this would be easier if I could draw some pictures.
If you have some examples of how the Dude should be set correctly, please send some info via email.
Thanks.
There is no ‘best practices’ document for The Dude at the moment, sorry.
You can look here for some simple information:
http://wiki.mikrotik.com/wiki/MikroTik_Dude
As far as I understand the problem some device is tying two or more maps together. Well one way would be using static items or devices without services on all but one map. Another way which is maybe more reasonable is putting that device on one map and on all others replacing device with submap item and make link to it not device.
Currently there is no way how to make multiple ‘pointers’ to single device, but we will think about adding this feature.