Although it's really a dumb workaround (and although, I must admin, I didn't try myself, because this nDeviceId bug is not really an issue for me, and because I'm lazy), could you try maybe the following workaround : choose a different default ip address for the two "copies" of your device. This should  be feasible since your devices are routers.

My idea is that, since Wug seems to "find" the device using the IP address, maybe if both devices don't have the same default IP, it will find the proper DeviceId ??

Reading, writing and arithmetic - If you need to choose, please take option 1.

yesterday I was thinking about intra-device dependencies... I suppose lot of problem will be solved if Ping will be removed from Active Monitors - like it was in WuG 8. there was no ping active monitor and there weren't a lot of problems.

Now if I watch a group icon I don't really know if some devices are down or only one (not so important) Active Monitor is down. It's really problem of our NOC center...

And it's because of Ping is Active Monitor.

If device have more than one AM - we have more than one alarms when it's getting down(intra-device dependencies). And it's because of Ping is Active Monitor.

Maybe return to WuG 8 logic resolve problem?

Juriy Gordubal

The problem with what you say is that "Ping" can't always be considered a critical monitor. For instance, I'm monitoring a website using its public IP address, and firewalls are set up so that it does NOT answer to ping. Therefore HTTP is the critical monitor for that box; a website is made to serve web pages and when it does not serve them anymore, well the box has a critical problem. In the same way, I'm monitoring a mail server; in that case smtp is the critical monitor.

Actually, the (many) documents and cases I sent to Ipswitch about this issue suggested to go back to the Wug V8 behaviour, and add a flag to each active monitor on each device, that could be set or cleared at your will, and that would declare that specific instance of that particular monitor as critical for that device.

Reading, writing and arithmetic - If you need to choose, please take option 1.

Since the Wug DB is Sql Server, and the database schema is available, you can already use your favourite reporting tool and create whatever report you want. I personally don't think it's a good idea (and I'm 99.999% sure Ipswitch would not do it) to request the addition of a report writer into Wug; there are soooo many out there, both free & commercial, that you really can pick up your favourite.

I may be wrong of course, but generally speaking (and that's not limited to Wug, but applies to any software product) it's a proven fact that prebuilt reports NEVER suit users -at least not 100%. So for me the important thing is to get a set of prebuilt reports AND the ability to create your own. This is already the case today with Wug.

Reading, writing and arithmetic - If you need to choose, please take option 1.

In no specific order...

1. Multiple views 

Not only allow tabs for Device and Map view but also add the ability for Topology view and Physical view.  Your Map view can be used for your geographical views, the Topology view can be used for the network map views and a Physical view could be used for a Visio type view.

2. Device count

Tell me how many total devices are in a group (status bar).  Sure if you click the group it will tell you x devices are Up, x devices are Down, x devices in Maintenance blah blah blah...but they cant have a stat