I had a WAN router supporting a couple of different circuits; NPM was happily monitoring this router. I split this WAN router up, where a new router took on one of the WAN circuits. I also moved some of the IP addresses to this new router.
NPM seems to think these IP addresses, although moved to a different router, are still associated with the old router object. When I manage nodes and rediscover the old router, it looks okay - I see the correct interfaces, etc. But then when I add the new router (with the old IP address having been moved to it), NPM replaces the old router with this new one, rather than creating an entirely new object to monitor. It's as if NPM doesn't realize that the IP addresses it had previously discovered are now split across two devices.
Is there some sort of database maintenance I can do to resolve this?
