Node icons are showing as down on map but we can ping them successfully from the NPM Server

Yes, this behavior occurs when a device has been swapped out ad not updated on the maps. Every time you change a device, you need to delete from the network atlas map and re-add. Secondly, the thresholds on the maps will always default to orion defaults and not locally amended thresholds. You need to adjust through the metrics.

Hello James,

Many thanks but could you please  post screen shots of how to achieve this.

Hi,

I am currently in Zambia at the moment and the dsl connection is so bad i cant hold a stable connection to my server over vpn. I will be more than happy to when i get back to ireland.

You dont have to delete the old nodes - you can go into the node properties within network atlas and re associate them with the new node - ie open the old node properties - status - and from the left side drag the new node details into it. Just drag the new node to this area and it will update the node

My apologies to lynchnigel, but I have had much better results with deleting the misbehaving node from the Atlas and adding in the correct ones.  I found that modifying an existing entry can lead to a "ghost" node.

Is that a 'feature' or side effect that needs addressing by support then maybe ?

There's a thread on the "ghost" interface issue, and getting rid of them is a PITA.  That's why I do what I can to prevent them.

ok, I've not come across them and we do this quite frequently as things move around.