This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.

You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

All Windows Server 2003-2012 Services and Counters Template Becoming Unknown?

arachenta over 8 years ago

Since the deployment of Solarwinds at my job, we've always applied the windows server template Windows Server 2003-2012 Services and Counters. So for us that's about 280 nodes carrying this template and we alert off a few things in the template so we do rely on it for production. Twice in the last 5 months the template went into an Unknown state on all 280 nodes. The first time this happened we restarted the Solarwinds services and that fixed some of it and eventually we rebooted our Solarwinds server and that resolved it completely. Just yesterday it happened again and we ended up waiting it out to see if it would come back up on it's own and it did after about 6 hours.

Has this happened to any of you guys? If so, what did you guys do to permanently make this problem go away?

Should I be putting in a ticket with support?

Top Replies

Parents

0 vinay.by over 8 years ago

Hi,
1. I am assuming you are using WMI
2. What's the polling interval set on the template ? (is it 300 seconds)
3. How many components do you have on the template ? (5-10 or more than that)
Suggestions:
1. If you have more than 8+ components split the template into 2 different template. (You can give it a try)
OR
2. Split the template in 2 different templates - do not move the components - just create a duplicate template .
Based on server priority with respect to business divide the nodes into 2 parts (Critical and Non-Critical) - for critical nodes retain polling interval : 300 seconds and for non-critical change polling interval to : 600 seconds
I dont think this issue is totally related to Solarwinds - it could be based on multiple factors with respect to how you are polling the nodes as well.
Hope it helps
Cancel
Vote Up +3 Vote Down

Cancel

Reply

0 vinay.by over 8 years ago

Hi,
1. I am assuming you are using WMI
2. What's the polling interval set on the template ? (is it 300 seconds)
3. How many components do you have on the template ? (5-10 or more than that)
Suggestions:
1. If you have more than 8+ components split the template into 2 different template. (You can give it a try)
OR
2. Split the template in 2 different templates - do not move the components - just create a duplicate template .
Based on server priority with respect to business divide the nodes into 2 parts (Critical and Non-Critical) - for critical nodes retain polling interval : 300 seconds and for non-critical change polling interval to : 600 seconds
I dont think this issue is totally related to Solarwinds - it could be based on multiple factors with respect to how you are polling the nodes as well.
Hope it helps
Cancel
Vote Up +3 Vote Down

Cancel

Children

0 arachenta over 8 years ago in reply to vinay.by

1. I am assuming you are using WMI yes
2. What's the polling interval set on the template ? (is it 300 seconds) yes, the more troublesome ones are 500
3. How many components do you have on the template ? (5-10 or more than that) 7
We've used your suggestions for resolution when maybe it's 1 application monitor or a couple of components that become unknown which does help.
The part that has us so tripped up is the fact that it was ALL Windows Server 2003-2012 Services & Counters template in our environment.
Cancel
Vote Up 0 Vote Down

Cancel