I setup a scheduled sonar discovery for all the devices I want to monitor on our network. After using the connect now feature in Network Atlas I found an incorrect topology mapping. We have two Cisco routers that are connected via T1 using serial interfaces. I noticed though that the NPM picked up one of these connections and mapped it from the serial interface of router A to the fastethernet port of router B. That is incorrect. from what I can tell this is the only layer 3 (routed) mapping that was made. I was told by support that the NPM will not make layer 3 topology connections in the current version. How can I remove this incorrect mapping? Also, why would it make the mapping in the first place?