Solarwind dashboard nodes on maps show down when indeed they are up

We have noticed when  solarwinds job engine V2 is started, solarwinds server is unable to reach nodes via ICMP and SNMP. This renders data on the dashboard to show down when indeed the nodes are up. Anyone has this challenge please and how was it resolved?

Parents Reply Children
  • Thanks once again. An engineer was assigned when we attempted to do an upgrade. He mentioned it was not overloaded but we have been adding some more nodes just by icmp so will proceed to unmanage them to see.

  • I think I may want to also try your first option of moving some items to additional poller. how do i achieve this please?

  • Settings -> Manage Nodes -> Select the node that you want to move over -> Click on Edit properties -> Under Polling you will see Polling Engine click on it and change it to another poller in your environment -> Submit

    Note: You can do this for multiple nodes/devices as well by selecting multiple nodes in manage nodes.

    But firstly, all additional pollers should be able to talk to the end device, I do not know how your current environment is configured. If only your additional pollers can talk to end devices then this will work.

    Plus can you tell me if you have additional pollers in your environment ? Settings -> My Orion Deployment (do you see additional pollers apart from main poller here ?)

  • I tried this before but unfortunately I do not see our standby poller showing there. we have two application servers in HA mode.

  • Ok in that case there aren't any additional pollers, please ignore my point. Thanks for the update.

  • I have mad some headway. I have unmanaged a lot of interfaces we added recently only for ICMP and everything seems fine now. we decided to monitor all ISP interfaces so what this means is that you have monitoring to about four IP's all on the same device.

    I now would have to explore how to use the standby server as an additional poller so we can use it for this purpose. Any suggestions?

  • The choice you have is:

    1.  Keep the HA capability and in reality only have one poller
    2. Break the HA and use the standby box as an additional poller
    3. |Deploy an additional poller.

    2 and 3 will have licensing costs associated to them.

  • Hello @beasravor 

    There are several options to reduce the load on your primary poller:

    1. I am not sure what SolarWinds modules do you have in your environment, if you could tell me about it I can help you with more details, lets assume you have just SolarWinds NPM

    2. Primary poller plays an important role - its hosts the web server, it does polling and it also takes care of alerting/reporting/dashboards/integrations etc

    3. You can reduce the load in 2 ways, move your web server onto SolarWinds Additional Web Server to reduce the load on your primary poller and second one is share the polling load by adding a SolarWinds Additional Poller.

    4. I was talking about the option where you can host a SolarWinds Additional Poller and move across majority of the devices that you are monitoring onto that, this should reduce performance issues or load on your Primary poller. Licensing and cost is again tricky, if you have purchased individual SolarWinds modules you will need to purchase additional licenses for Additional Poller but if you have a SolarWinds NAM then Additional pollers are free of cost.

    5. For now i think you just have one primary poller along with a standby which does the High Availability for you. Help me with more details and I can suggest better : ) , as well note that SolarWinds suggests a max of 12000 network elements on one poller but I generally keep less than 8000 network elements on my main poller. What is a network element ? It is your nodes (devices) + interfaces + volumes in your environment on a single box.

    Hope this helps ; )