Comments
-
The "down" status is the one we want to see. Shutdown we don't care about as that's a port we have admin shut on the switch. Unplugged we don't care about as we have gone into to Solarwinds and selected the option you suggested above (usually for user ports). Yet the NodeStatusRootCause variable shows us all child entities…
-
Thanks for that, on further reflection neither option is great as it still requires a level of manual intervention. For more context this is using the 'node is in a warning or critical state' under child entities with problems it shows something like the following: Child entities with problems: TenGigabitEthernet1/0/43 ·…
-
This is something I am also interesting in, when a node has an issue I want to see the interfaces with the issue (i.e. down status) as opposed to seeing interfaces I have shutdown hence there is nothing wrong with them. I'm still relatively new to Solarwinds, how would you go about creating the custom property?
-
No problem, we went a different approach where we were asking Solarwinds to investigate (Although they did keep pointing us towards Cisco). They found that Solarwinds would not always get a response so it would have to retry but with the timeout being 2.5 seconds it was showing as timing out, hence the settings change. If…
-
Oh good not just us! :D What has helped us massively reduce the events (although not pleased with this as a solution) is the following: Go to Polling Settings in Orion (All Settings -> Polling Settings) and do these changes: Set SNMP TIMEOUT to 10000 ms Set SNMP RETRIES to 5
-
Thanks, is there any way to change it?
