Comments
-
NICE! I'll give is a whirl and see how it works!
-
+1 to this, though I'm not sure how much data of value, if any, would come from a PERC. Doesn't hurt to ask though, right?
-
Bummer, but thanks for the follow-up!
-
I've ended up doing what I outlined above...I'll test it out for a few days and see how it goes!
-
I have a similar question, in that we have two Orion instances, one for SAM and one for SRM. Is there a process/path we can follow to merge these installations into one after both have been deployed? Thanks!
-
Done! Cheers!
-
Thanksjdumke...I was considering a variation on that theme, but was hoping to do this all in one alert instead of two. Unless anyone has thoughts otherwise what I think I'll do is indeed two identical alerts, but only have the after-hours-logging trigger action alert run after-hours, and a second alert that logs and…
-
Yeah, we figured that would probably be the case...that's for confirming cscoengineer!
-
Reboot took care of it for us. Been quiet for weeks...granted a non-reboot solution would be preferred!
-
Reboot of the node in question was ultimately what fixed it for us. It's been a week now and the components that were giving us fits have been quiet.
-
We've got SAM and SRM, and a similar question: is there a way we can monitor the XFS filesystem through one of these tools? Thanks!
-
Yeah, having the same issue as well only specifically on the Security application template on one DC. Other monitors using the same method (RPC) with the same credentials to the same resource (Event Logs) on the same DC are working fine. If anyone has specifics on how to resolve this without a reboot, that would be swell!