"logical disk health" monitor is critical

Hello
We have 2 HP-UX servers to monitor and everything is fine until we mount and unmount the servers disks. when we change a disk "Logical
Disk Health" monitors State goes Critical. unfortunately this change may happen again. I reduced the discovery interval to 5 minutes and no luck. other monitors like "% free space" are healthy. what am i missing?

I have done this. I've mentioned above the "Logical Disk Health" monitor is in critical state. other
monitors are healthy.
Some body told me override the physical disk discoveries interval from 14400 to 600 for test. it didn't
work.
I checked the HP-UX MP user guide, there is no information about logical disk health parameters and dependencies.
any idea?

Similar Messages

Logical disk availability monitor on SCOM 2012 r2

Hi Team,
Please let me know in which management pack has the rule or monitor for logical disk availability. We need to monitor HP physical disk ( c:\ or D:\ Logical disk) availability.

Hi,
System Center Management Pack for Windows Server Operating System
http://www.microsoft.com/en-us/download/details.aspx?id=9296
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Logical Disk monitoring - Overrides galore?

Hi all!
We have a number of systems with differing needs for storage thresholds. The defaults work the majority of time, but there are a number of 'buckets' our disks need. For example, some disks might warrant an error at 5GB free, 10GB free, or even
25GB free. Let's pretend the percentages aren't important for now.
Just to be clear, is it correct that I would need to create 2 (system / non-system) * 3 (2003, 2008, 2012) = 6 overrides for every single bucket I want (and make no mistake, we need way more than 3)?
This seems absurd. I can handle dumping the appropriate logical disks into buckets based on PowerShell or some other programmatic method. Creating
overrides seems a bit more complicated. Is there not a simpler way to do this?
I'm comfortable using PowerShell, but the 600 line example above seems like a pretty steep requirement for a very basic and common task (that is cumbersome and delay ridden when using the SCOM console).
Please tell me there is an easier way to create overrides for logical disk space monitoring!

I run into the same questions and problems with most customers. What I always suggest is to give the power to the server and/or application owners. This can be accomplished a few different ways, and I have done this by using a registry entry or by using
a file on the root of each disk.
For example, everyone gets default thresholds for disk monitoring. If the server owner wants different thresholds for a disk on their server(s), then they would create a csv file on the root of each disk in which they want different thresholds (or create
a registry entry with similar threshold configuration).
If you modify the built-in disk monitor by checking whether this particular file is present, then read the file to get the custom thresholds and bypass the default thresholds for monitoring that particular disk. The built-in disk monitoring script is pretty
long, but if you know a little VBscript then you should be able to figure out where to add more logic to retrieve custom thresholds based on csv file or registry information.
You will need to put this monitor in a new pack (for example, Windows 2008 Operating System Extended), and disable the unit monitor in the vendor pack. This would end up being 2 new "extended" packs if you were to also do this for Windows Server
2012.
This will effectively remove the responsibility from the SCOM admin to manage hundreds (or more) disk monitoring thresholds, and place the responsibility into the hands of the server owner. This has worked quite well in any environment I've work in.
Jonathan Almquist | SCOMskills, LLC (http://scomskills.com)

SCOM 2007 R2 : Logical Disk Free Space : Did not Alert

Hello reader ,
I know this might be a repeated hearing for you. I have been sitting wit this issue for many hours now. I would like to understand where or what am I missing.
We have the default 'Logical Disk Space' Monitoring enabled for ALL servers in our environment. In one SQL server, non-system drive(E:) went beyond the warning(2000MB and 10%) and Critical (1000MB and 5%) Threshold.The total space allotted for the Drive
E: was 79GB. Now the total space left today morning was 698MB. But no alert was triggered.
I checked the following
If the health service watcher was available. - Yes it was.
If the Space really dropped to 698 - Yes it did. I verified from Performance Report.
I checked if there are any overrides - Nothing specific found.
In most of the blogs they said me to check if both criteria was successful - As shown above it is clearly matches.
Any idea why this alert was not fired ?
S.Arun Prasath HP ARDE TEAM

Thank you Agarwal ! To Answer your Question.
1) verify the monitor settings again.
=> I did this N number of times.
2) ensure there are no overrides
=> I did this too.
3) ensure that monitor properties are set for the correct Windows OS (same as that of the server).
=>What Do you mean here ?. I did not change any settings , it was there by default. No change was done at all.
4) also confirm that you do not have any other overrides on the two aggregate rollup monitors for "logical disk free space". These aggregate rollup monitors are just below the unit monitor in SCOM console.
=>Those Aggregate Rollup monitors are disabled. As we already have this unit monitor Enabled. There is no link to Aggregate monitor.
If all these settings are true, then can you try this. calculate the exact value in both % and MBytes according to your server, put the same values in your monitor through an override and repro the low disk space condition,. you should get an alert.
=> Not so easy to do this in prod. So will keep you posted when this is tested. Looks like this is the only way we can confirm if the alerts are sent.
S.Arun Prasath HP ARDE TEAM

Logical Disk space on a virtual Computer (not a Server) in SCOM 2012

Hello all-
   I have a sort of unique situation for our SCOM environment. We are already doing logical disk space monitoring on all of our SERVERS with no issues. Now we have one user who requires monitoring on their computer. This is really
a virtual workstation, as opposed to a real computer.   Since it's virtual, it's really online all the time.    Whether its right or wrong, they are using this virtual workstation sort of as a server. Anyway, they want me to
monitor the disk space for the C drive on this virtual computer. I'm having difficulty setting up such a monitor on a computer like that...
I got the SCOM agent installed onto the computer. SCOM is reporting it as being "Healthy".   Now how can I define a logical disk space monitor for it?   I attempt to create a monitor:   Windows Performance Counters,
Static Thresholds, Single Threshold. Then how can I direct the monitor at the C drive on the computer? I have to fill in the Object, Counter and Instanace. Normally I would click on the
Select button, then I would type in the server name and hit Enter and it would bring up all the objects it will allow me to monitor. Unfortunately it doesn't let me type in the computer name and hit enter in the same way. When I
do so, it says "The network path was not found". If I click on the
... button next to the Computer field, it brings me to a Select Computer screen. In here, I am type in the computer name and then I click
Check Name and it does appear to find it, and it underlines the computer's name.    So I then click
OK to bring me back to the previous screen where it presents me with the same "The network path was not found" error immediately. So I can't seem to navigate to the computer in SCOM and select the C drive, as I would be able
to for a server.
I tried to sort of force it in, instead of browsing for the computer and selecting the C drive. I simply put
LogicalDisk in for the Object then Free Megabytes for the Counter, then
C: for the Instance (as shown in the attached screen print.
Then I just applied my new rule to the computer via SCOM. I don't get any error messages when setting it up that way, but it certainly doesn't work.
So with all that said, can anyone help me out setting up a logical disk space monitoring for a COMPUTER in SCOM 2012 SP1 please? Please let me know if you need any more information!

Thanks, that would probably do it, I'm going to keep that as my backup plan. However, my current feeling is that it might be a bit overkill to install a whole management pack, when all I want to do is monitor a single C drive on a single workstation.
The rest of the monitors in the management pack I wouldn't have any interest it.   Let me ask you a question maybe you will know the answer to... Shouldn't I be able to monitor that drive even without that management pack installed?   I
mean some combination of settings for the Logical Disk Space rule in that management pack works for computers/workstations. Shouldn't I be able to reproduce that one single rule without the management pack? Does anyone have that management pack
installed? Could you possibly look at the Client OS Logical Disk Space rule and send me some screen shots or something?   Or am I missing something? Is the management pack needed for other reasons in order to monitor this?

Disk Space Monitor

hi
I have set up a logical disk space monitor for windows 2012 servers on my Operations manager 2012. The threshold value is 500MB. However, No alert is generated even when my disk has exceeded 500MB. It works when i set the threshold below 100 MB. Can you
please help out on this? Is it because of the wrong instance ?
The object has been specified as "Logical Disk"
Counter is %free space and the instance is the C:\ drive.

Does you using Logical Disk Free Space, from Windows Server OS Management Pack, in monitoring the free disk space?
Case 1 Logical disk Free Space Monitor:
It will generate alert if both the conditions, disk free space and % of free disk space, are below threshold.
Recommendation: You may enable another monitor ,Disk Free Space (MB) Low, which is disable by default.
Case 2 you own custom monitor:
Please dump your setting for troubleshooting
Roger

Logical Disk Free Space Monitor - Slow to detect low free space

We are using the built in two trigger (MB and %) logical disk free space monitor in SCOM 2012 R2. We have setup overrides for MB warning and critical for both system and non-system drives and for a group containing disks we do not want monitored. The monitor
actually works fine, triggering an alert when both the MB and % free criteria are met. The problem is that it takes almost an hour for the initial alert to fire. After the initial alert, if I further fill the disk to push it from warning to critical, the alert
changes within the specifiec interval, which we have left at 15 minutes. The alert also clears using the 15 minute interval.
Has anyone else seen this behavior with this monitor? A disk monitor that takes an hour to fire is not going to be very useful.

I wanted to see for myself if there was anything else that I might be missing, so I opened up the Windows 2008 Logical Disk Free Space monitor XML and noticed that there is a NumSamples configuration that is set to 4. So, if the interval is 15 minutes, the
disk would have to exceed both threshold types for 4 consecutive intervals in order to change state and generate alert. This would be a minimum of 1 hour before an alert is raised with the default 15 minutes interval.
Unfortunately, NumSamples is not overrideable in the monitor type, which is too bad... The only way to get an alert sooner than one hour is to override interval. For example, if you want an alert within 20 minutes, override interval to 300 seconds (5 minutes).
Here is the code - see for yourself:
<UnitMonitor ID="Microsoft.Windows.Server.2008.LogicalDisk.FreeSpace" Accessibility="Public" Enabled="true" Target="Server2008!Microsoft.Windows.Server.2008.LogicalDisk" ParentMonitorID="SystemHealth!System.Health.AvailabilityState" Remotable="true" Priority="Normal" TypeID="Microsoft.Windows.Server.2008.FreeSpace.Monitortype" ConfirmDelivery="true">
<Category>Custom</Category>
<AlertSettings AlertMessage="Microsoft.Windows.Server.2008.LogicalDisk.FreeSpace.AlertMessage">
<AlertOnState>Warning</AlertOnState>
<AutoResolve>true</AutoResolve>
<AlertPriority>Normal</AlertPriority>
<AlertSeverity>MatchMonitorHealth</AlertSeverity>
<AlertParameters>
<AlertParameter1>$Target/Property[Type="Windows!Microsoft.Windows.LogicalDevice"]/DeviceID$</AlertParameter1>
<AlertParameter2>$Target/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/PrincipalName$</AlertParameter2>
</AlertParameters>
</AlertSettings>
<OperationalStates>
<OperationalState ID="UnderWarningThresholds" MonitorTypeStateID="UnderWarningThresholds" HealthState="Success" />
<OperationalState ID="OverWarningUnderErrorThresholds" MonitorTypeStateID="OverWarningUnderErrorThresholds" HealthState="Warning" />
<OperationalState ID="OverErrorThresholds" MonitorTypeStateID="OverErrorThresholds" HealthState="Error" />
</OperationalStates>
<Configuration>
<ComputerName>$Target/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$</ComputerName>
<DiskLabel>$Target/Property[Type="Windows!Microsoft.Windows.LogicalDevice"]/DeviceID$</DiskLabel>
<IntervalSeconds>900</IntervalSeconds>
<SystemDriveWarningMBytesThreshold>500</SystemDriveWarningMBytesThreshold>
<SystemDriveWarningPercentThreshold>10</SystemDriveWarningPercentThreshold>
<SystemDriveErrorMBytesThreshold>300</SystemDriveErrorMBytesThreshold>
<SystemDriveErrorPercentThreshold>5</SystemDriveErrorPercentThreshold>
<NonSystemDriveWarningMBytesThreshold>2000</NonSystemDriveWarningMBytesThreshold>
<NonSystemDriveWarningPercentThreshold>10</NonSystemDriveWarningPercentThreshold>
<NonSystemDriveErrorMBytesThreshold>1000</NonSystemDriveErrorMBytesThreshold>
<NonSystemDriveErrorPercentThreshold>5</NonSystemDriveErrorPercentThreshold>
<NumSamples>4</NumSamples>
</Configuration>
</UnitMonitor>
This proves 2 things:
1. Your testing proved that the monitor is working as designed - you got an alert in about an hour
2. This is a bad design at best, or a bug if you wish, as NumSamples should not be a hidden configuration - it should be exposed in override parameters in the console.
This should be fixed by Microsoft.
Jonathan Almquist | SCOMskills, LLC (http://scomskills.com)

Custom Logical Disk monitor incorrectly flapping between healthy and unhealthy

One of the clients Ops Mgr 2012 SP1 UR8 environments I am supporting has had some custom logical disk monitoring setup; there are 5 groups dynamically populated by logical drives depending on their size (1st group has small drives up to the last group with
very large drives). There is a 'Warning' and 'Critical' Monitor setup per server OS version, the Monitors are not Enabled. There are Overrides applied to each group to enable the Monitor and apply a threshold - different threshold for each group.
During some BAU tuning I could see that some of the above Monitors were appearing as Top-Talking alerts. Further investigation showed that alerts were being triggered by drives that momentarily dropped below the applied threshold. I re-created the Monitors
from 'Simple Threshold' to 'Consecutive Samples' and set the 'Number of Samples' to 6 @ 3 minute intervals.
What I am seeing is that alerts from the above Monitors are still appearing as Top Talkers. When I check the Health Explorer of repeating alerts I can see the disk space is staying the same, below the applied threshold but the health is turning healthy then
back to unhealthy. I have confirmed each noisy Object has the expected threshold as per its dynamic group allocation and have also confirmed the drives are not fluctuating above and below the threshold. One thing I have noticed is that some drives Performance
View is patchy - lots of dotted lines between the coloured lines.
Its almost like the Monitor moves a Logical Disk Object into unhealthy state in the correct (and expected) manner, then it somehow picks up an incorrect threshold which is below the current usage level. This moves it into a healthy state only for the
whole process to repeat. For example: Drive X: on a server is very large, the Group that it sits in has a threshold of 102400MB, its current usage is ~stable at 45500MB. Looking in Health Explorer I can see 3:01pm green state/ 45573 last sampled value/ # of
samples 1 | 3:16pm yellow state/ 45573/ 6 samples | 3:34pm green state/ 45572/ 1 samples | 3:49pm yellow state/ 45571/ 6 samples | 4:01pm green state/ 45425/ 1 sample etc etc.
I'm scratching my head on this one and would appreciate any suggestions or assistance.
Thanks
BT

Thanks for the reply. It is not just one server / drive this is happening on. I am seeing it on everything; once they go into an unhealthy state they periodically go healthy and back again with no change in disk free space. Just to elaborate on how it is
setup; a Monitor has been created for each OS version (2003, 2008 and 2012) and a separate Monitor for Warning and Critical so 6 Monitors in total. Looking at the Warning Monitors; they are created with a threshold of 5120MB for 6 samples and set to disabled.
The following groups have been created and the following thresholds added:
Group 1 (less than 60GB size): override added to enable. This group will then pick up the 5120MB threshold.
Group 2 (60 – 250GB size): override added to enable and override added for 10240MB threshold
Group 3 (250 – 500GB size): override added to enable and override added for 20480MB threshold
Group 4 (500 – 1TB size): override added to enable and override added for 51200MB threshold
Group 5 (>1TB size): override added to enable and override added for 102400MB threshold
One drive I was looking at was in Group 2 (threshold of 10240MB), it was staying at approx. 8500MB but periodically going into healthy state then after 10mins (6 polls @ 2min intervals) back to unhealthy. This process repeats once or twice per day.
I am wondering if the Object is somehow picking up the threshold of the Monitor (5120MB) then going back to its correct overridden threshold. I have setup some test groups and monitors in a lab and will review the results over the coming days.
When the monitors were setup as 'Simple Threshold' this worked fine but were noisy due to drives spiking downwards. It was only when I re-wrote them as 'Consecutive Samples over Threshold' Monitors that this issue has started occurring.
Thanks

Need to separate drive alerts with Logical Disk Free Space monitoring in SCOM 2012

I have an interesting need here to separate our SCOM alerts for Logical Disk Free space so that one alert is for OSSystem drives ONLY (C:/D:) and the other monitor alerts on all APP drives only (E:, etc). So far we have had great success using Kevin Holman's
blog post.
http://blogs.technet.com/b/kevinholman/archive/2009/11/24/writing-monitors-to-target-logical-or-physical-disks.aspx
We have overrides set so that the monitors report ONLY the percentage of free space left and ignores any MB threshold. So far so good, the alert comes in that host A reports low disk space on D: at 2.345...% free or host B reports low disk space on F: at
4.567...% free space etc. Now that we have our monitors working within the Windows Server classes Logical Disk, we need to set these monitors so that one is just for C or D drives with the alert named system Logical Disk Free Space OS Disk Warn and the other
monitor just reports on E - Z drives (excluding C or D) with the alert named Logical Disk Free Space APP Disk Warn.
We are very new to SCOM so I made the rookie mistake of creating a dynamic group for all Windows Server 2003 Logical Disk class that only includes Device Name = C or D. But found out too late you cant point a monitor to a group, it has to target a class.
And using the current monitors we set up with the above blog uses the correct logical disk class, but it doesnt care what instance (device Id = value), it will report low disk space on ANY logical drive. How in the world can we separate and exclude these monitors
so that one alerts only on OS disks (C and D) and the other only alerts on app disks (E through Z)?

Hi Kevsharp,
Quite confusing after reading your question.
So based on your requirement, What i understand is you need separate alerts for all the drives of the disk is running at low or out of space right ?
For the above just create a simple performance counter monitor and use the same counters as kevin has used in his blog.
Now Target: Use Windows server operating system (This will target all the Windows operating system agents in your SCOM. If the specified discovery MP's are installed).
Set a threshold Below 10% is critical or what ever. You will get the alerts in your console.
Gautam.75801

Windows Server 2008 R2 Logical Disk monitor is not listed in SCOM 2012

Dear Experts,
I tried to create an override of Logical Disk space threshold value changes on one of Windows 2008 R2 OS, But unable to find the respective monitor of 'Windows Server 2008 R2 Logical Disk' monitor in the scope, But I can see Windows Server 2008 Logical
Disk monitor is there and if I do right-click create override the monitor for particular specific of Windows server 2008 computers then the Windows 2008 R2 computer is not displaying there. Finally I found Windows Server 2008 R2 Logical Disk monitor is
missing ?
Can you please help me to achieve this ?
Saravana Raja

Hi,
Same issue/question in this thread:
https://social.technet.microsoft.com/Forums/en-US/15f634e2-57d7-4f57-b579-61e5ee6a01a2/monitor-hard-drive-space-windows-2008-r2?forum=operationsmanagergeneral
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Override Windows 2008 Logical Disk Free Space Monitor

HI all,
can I override this monitor on one concrete logical disk and concrete server ?
thanx
Falcon

find out the monitor
right click the monitor --> overrdies monitor --> speical object of logical disk
select the require hard disk e.g. c: and with path of your server name
Roger

Re: Satellite C855-1GQ - Health Monitor is unable to get the disk information

On my new C855-1GQ the 'Health Monitor' states that it is unable to get the disk information and so cannot use the alert function.
Is this normal?
I can turn this bubble off but just thought that I would ask anyway.
Thanks - Joe

This is just an notification so you can turn it off if you want.

Target drives for specific groups - Logical Disk Monitoring

I want to target different drives and thresholds for logical disk monitoring. I want to be able to place the server in a group and monitor the drives accordingly. Can this be done? How would you go about doing it?

couple of ways you can go about this:
1. Place the servers into a group and apply the necessary overrides to the logical disk monitors
2. If you don't want the same threshold applied to all the drives on the same server create a new group and add the specific drives to the group and then apply the necessary overrides to the group for logical disk monitors.
3. If you don't want the same threshold applied to all the drives you could also create a dynamic group ie all D: for servers and then apply the overrides to that group.
example of this see: https://social.technet.microsoft.com/Forums/systemcenter/en-US/c2719fb1-9298-435a-8bf9-3c92d4b34f85/making-groups-of-logical-disk?forum=operationsmanagergeneral
Cheers,
Martin
Blog:
http://sustaslog.wordpress.com
LinkedIn:
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Solaris Logical Disks (Filesystems) not being discovered. WinRM CIM_ERR_INVALID_CLASS Error.

Hello,
currently I am testing the Solaris monitoring with different kind of Solaris servers. We have one single system, a RAC database cluster of two servers, and one "Global-Zone" server hosting a "Non-Global-Zone". We're using SCOM
2012 SP1 with Agent Version 1.4.0-906 (sparc).
My problem is, that only on one of the 5 servers the Logical Disks (Filesystems) are discovered correctly. All Solaris systems are using ZFS.
The one that works just fine is the single system. In Health Explorer under Hardware Availability Rollup I can find every filesystem that is also configured in the /etc/vfstab. A check with WinRM from the Management Server works fine (winrm enumerate hxxp://schemas.microsoft.com/wbem/wscim/1/cim-schema/2/SCX_FileSystem?__cimnamespace=root/scx
-auth:basic -remote:https://<servername>:1270 -username:scomuser -password:<pass> -skipCAcheck -skipCNcheck -encoding:utf-8)
The same WinRM command does not work for the other servers. The WinRM command failes with following error code:
Fault
    Code
        Value = SOAP-ENV:Sender
        Subcode
            Value = wsa:DestinationUnreachable
    Reason
        Text = CIM_ERR_INVALID_CLASS
    Detail
        FaultDetail = hxxp://schemas.dmtf.org/wbem/wsman/1/wsman/faultDetail/InvalidResourceURI
Error number: -2144108485 0x8033803B
The WS-Management service cannot process the request. The resource URI is missing or it has an incorrect forma
t. Check the documentation or use the following command for information on how to construct a resource URI: "w
inrm help uris".
As far as I can see in the scx.log, there are some messages like:
2013-04-25T12:19:33,668Z Warning    [scx.core.common.pal.system.disk.diskdepend:6241:7] No link exists between the logical device "rpool12/export/home" at mount point "/export/home" with filesystem "zfs". Some
statistics will be unavailable.
2013-04-25T14:10:34,775Z Info       [scx.core.providers.diskprovider:6241:11] BaseProvider::EnumInstances() - Invalid class - //<servername>/root/scx:SCX_FileSystem
2013-04-25T14:13:27,810Z Warning    [scx.core.providers.osprovider:6241:11] BaseProvider::EnumInstances() - Calling opendir() returned an error with errno = 24 (Too many open files) - [/export/home/serviceb/ScxCore_URSP1_SunOS510_sparc/source/code/shared/scxsystemlib/process/processenumeration.cpp:58]
Do you have any idea what is going wrong and how to fix it?
Thanks & Regards,
Holger

Holger,
I believe it might be the (Too many files open) issue causing your problems. Try the following and let me know if it helps...
First confirm if this is the issue. Run the following command to find out the Solaris server's current file descriptor limit:
ulimit -n
Next determine the number of file descriptors in use by the SCX Agent processes. A list of file descriptors is located under /proc/<Process ID>/fd, where <Process ID> is the process ID of the agent process running on the Solaris server which
can be obtained using the ps command. Or use the following command to list the PID’s and number of file descriptors for any processes containing microsoft/scx which should cover all of the SCX Agent processes:
for i in `ps -ef | grep microsoft/scx | grep -v grep | awk '{print $2}'` ; do echo PID $i: `ls -l /proc/$i/fd | wc -l` ; done
Note: You must execute the above commands using sh, bash, or other Bourne-compatible shell. Be sure the commands are on a single line. If the result is a > sign, then press CTRL-C, check to make sure quotes and backticks are closed, and try again.
If the number of file descriptors returned is near the file descriptor limit obtained using ulimit, follow this procedure to increase the limit by putting a ulimit command in the SCX Agent startup script.
1.
Find and edit the scx-cimd startup script, which should be located at /opt/microsoft/scx/bin/tools/scx-cimd in Solaris 10 and 11, or at /etc/init.d/scx-cimd in Solaris 8 and 9:
vi /opt/microsoft/scx/bin/tools/scx-cimd
2.   In the file, locate the section responsible for starting the agent daemon.
start)
        # Start daemon
        echo "Starting $DESC"
        $DAEMON $OPTIONS
        exit $?
3.
Below the echo statement, but before the line with $DAEMON $OPTIONS, insert this command on its own line:
ulimit -n 1024
The end result should look like:
start)
        # Start daemon
        echo "Starting $DESC"
       ulimit -n 1024
        $DAEMON $OPTIONS
        exit $?
4.
Save the file and restart the agent:
scxadmin -restart all
Regards,
-Steve

SCOM does not generate alert for logical disk space

Hi,
Today we noticed that one of agent in SCOM has drive space below 5% and 500 MB but SCOM did not generate any alert.
I have also verified that there is no override set for this agent's logical disks. I have also verified that discovery is able to discover all disks on server but monitoring is not working as expected.
I have flushed health service on agent but it didn't help.
When I gone through event logs on agent, I found below events:
Log Name:      Operations Manager
Source:        HealthService
Date:          5/26/2014 5:13:05 AM
Event ID:      1103
Description:
Summary: 6 rule(s)/monitor(s) failed and got unloaded, 1 of them reached the failure limit that prevents automatic reload. Management group "XXXXXXXX".
This is summary only event, please see other events with descriptions of unloaded rule(s)/monitor(s).
Log Name:      Operations Manager
Source:        HealthService
Date:          5/26/2014 5:14:21 AM
Event ID:      1206
Task Category: Health Service
Description:
Rule/Monitor "Microsoft.Windows.Server.2008.LogicalDisk.FreeSpace", running for instance "F:" with id:"{36ED7395-3798-A361-5017-327F6FA50030}" failed,
got unloaded and reached the failure limit that prevents automatic reload. Management group "XXXXXXXXX".
Please let me if what we need to do here.
Thanks.

Do this
Change startup type to Window Management Instrumentation (WMI) Service to disabled
Stop the WMI Service; you may need to stop IP Helper Service first or other dependent services before it allows you to stop WMI Service
Rename the repository folder: C:\WINDOWS\system32\wbem\Repository to Repository.old
Open a CMD Prompt with elevated privileges
CD windows\system32\wbem
for /f %%s in ('dir /b /s *.dll') do regsvr32 /s %%s
Set the WMI Service type back to Automatic and start WMI Service
cd /d c:\ ((go to the root of the c drive, this is important))
for /f %%s in ('dir /s /b *.mof *.mfl') do mofcomp %%s
Reboot the server
Blog: http://theinfraguys.com
Follow me at Facebook
The Infra Guys Facebook Page
Please remember to click Mark as Answer on the answer if it helps you in anyway

"logical disk health" monitor is critical

Similar Messages

Maybe you are looking for