I did a manual import of scheduled network discovery results this morning, and noted that several Linux boxes ( that the Agent reports as Oracle Servers ) had a polling IP address of 255.255.255.255. The servers were already managed by Solarwinds , and had valid "10." polling IP addresses. Has anyone else seen this behavior before?
I went ahead and imported the results. Afterwards, I searched Solarwinds for nodes with IP address 255.255.255.255 and did not get any results.
EDIT: Nevermind, found this post here: Scheduled Discovery Results polling IP wrong
We're seeing the same thing with some Linux servers we just changed over to Agent polling. I scanned them using Discovery so I wouldn't have to click on each one and do a List Resources, but I'm worried about importing them when they show the IP as 255.255.255.255.
Did you get this figured out?