Just applied the latest SR 10.2.2, hoping that the bug, where objects in a map have a red dot on them has been addressed but the issue remains...
Any ETA on when this issue would be addressed? The false positives presented in the maps are causing alot of confusion and panic!
Just to confirm, I did already double check that no child objects have any faults either, therefore a status rollup is not the culprit.
The issue is current on any map, in any module. Lastly, creating a quick basic map with the same nodes still shows the nodes/objects as having one or more objects in a down state.
Solved! Go to Solution.
For those of you that don't see the Orion.UDT.Port line in the table after an upgrade to NPM v10.3, you'll have to manually add it.
Here's the SQL query:
insert into NodeChildStatusParticipation (EntityType, ModuleName, Enabled, Installed)
values ('Orion.UDT.Port', 'UDT', 0, 1)
gotcha. additional web is $400 list. off-loads that from main poller and allows this workaround. Don't know your situation but might be worth it for now.
Regardless, this needs to be fixed! good luck.
SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community. More than 150,000 members are here to solve problems, share technology and best practices, and directly contribute to our product development process.