jaybone

If I'm understanding how dependencies and groups work, I think I should be able to accomplish it that way as follows? Group - "XYZ-DC replication partners", rollup set to "worst status" (to force the object to a down state when any of those nodes are down), contains nodes that are replication partners for that DC.…

By any chance, is a fix for this a part of the "Agents have been optimized for overall better performance." item in the SAM 6.2.1 release notes?

Thanks! Weird terminology, "edit threshold" to change that.

We were experiencing the same issue. The steps provided by stevewright solved it. This also seems to have fixed a problem we were having with a node half-stuck in an Unmanaged state (showed as managed, but only Remanage was available, it was impossible to unmanage it). After the services came back up, the problem node…

Hi, thanks. Logs are not being archived - just a new logfile created at midnight UTC for each new day. Web admin deletes them manually if/when they start taking up too much room for his liking, which is typically many months down the line. As far as the error... i can't find one. AppInsight is showing the node green while…

They have not, given the problems I've seen people talking about with them in the "11.5.1 on the way? Just not brave enough to that 11.5.0.. " thread.

2) Check out your alert evaluation frequency for that specific alert. If it is > 60 seconds, you will be getting "delayed" alerts. It's set to 60 seconds.

I didn't think of attacking from this angle, but yeah, this could probably work. I'd have to know what alert to edit, though, which is a problem. As far as I've ever been able to figure out, there's no way to go back after the fact and tell which alert was actually triggered. I can look at the reports and see that, yes, at…

Thanks. Yeah, I saw this, but this won't help in the future when more of these are added, unless someone goes in and reconfigures the newly-added node.

That's what I'm saying - on some of the hosts that are in this list, in Appstack, they show the vm as up-with-critical or up-with-warning. But I have no idea why. Going into those vm nodes flagged in Appstack, everything looks normal, except that in AppStack, the host is in warning. It's almost like there's a circular…

Yes, thanks. And there's nothing useful. E.g. The Windows servers, with everything checked, the only stuff shown are reboots that happened a month ago for Windows updates. None of the dozens of other Windows servers that rebooted around the same time look any different, except they don't have the warning.

node X or node Y status is down or unreachable.

Thanks, prawij. I'll try that and see if it gets us the functionality we need.

These are Hyper-V servers, so we need to use WMI for monitoring that, unfortunately.

What do you think? Are there commands that you'd like to have quick access to through the popovers? SSH, management webpage, or etc. of the node would be a huge time-saver.

Sooooo, no way to do this, then?

Steps provided by stevewright in a thread for another issue (missing events) seem to have fixed this problem, as well.

Is the switch passing other traffic normally while it's "down?" I.e. is it just the management interface that's not accessible? Assuming you have some visibility to the switch via console while it's down, what do the onboard logs say?

Ever get anywhere with this?

Am I just completely missing something, here? Yes. I was. In case anyone else runs into this... Turns out that these old rules were using 'not equal' logic to compare against fields that are typically not used anymore - i.e. they're left blank unless there's some reason to populate them, whereas in the past they had been…

We were getting something similar after updating to 11.5 - 11.5 - un/remanage broken? The steps provided by SteveWright in his march 4th post in another thread, NPM: Audit Trail - missing, fixed the un/remanage problem for us as well as the auditing issue.

Alert config:

This morning, I figured I'd look at this with fresh eyes/brain, and I just blew up the alert and started over on it for the third time. This time, the "reset when no longer true" option was available. Not sure why, but I'll take it.