Tag Archives: “SBS 2011”

Fujitsu Primergy Servers – SNMP RAID and Server Health Checks

This next post is very useful for owners of Fujitsu or Fujitsu Siemens Primergy Servers, it highlights how you can monitor the status of your servers general Health and RAID Status.  To utilise these checks you will need to have the Windows SNMP Service installed and configured.  You will also need to download and install the Fujitsu ServerView RAID Manager and the Fujitsu ServerView Agent for Windows.

These OIDs can be used with your existing Server Monitoring Software such as GFI Max Remote Management or Spiceworks to provide upto the minute information.

Logical Drive Status (Array 1) = 1.3.6.1.4.1.231.2.49.1.6.2.1.10.1.1

1 = unknown, 2 = ok, 3 = degraded, 4 = offline, 5 = rebuilding, 6 = verifying, 7 = initializing, 8 = morphing, 9 = partially degraded

Logical Drive Status (Array 2) = 1.3.6.1.4.1.231.2.49.1.6.2.1.10.1.2

1 = unknown, 2 = ok, 3 = degraded, 4 = offline, 5 = rebuilding, 6 = verifying, 7 = initializing, 8 = morphing, 9 = partially degraded

If you have more than two Logical Drives (i.e. 4 x RAID 1 Sets) then simply substitute the last number of the above OID with 3 or 4, etc to reference the next Logical Drive

Number of Logical Drives = 1.3.6.1.4.1.231.2.49.1.6.1.0

1 = 1 Logical Drive, 2 = 2 Locagical Drives, 3 = 3 Locagical Drives, etc

Number of Physical Drives = 1.3.6.1.4.1.231.2.49.1.5.1.0

1 = 1 Physical Drive, 2 = 2 Physical Drives, 3 = 3 Physical Drives, etc

Power Supply Status = 1.3.6.1.4.1.231.2.10.2.2.5.11.1.1.2.0

1 = unknown, 2 = ok, 3 = degraded, 4 = critical

Temperature Sensor Ambient = 1.3.6.1.4.1.231.2.10.2.2.5.2.1.1.3.0.11

1 = unknown, 2 = sensor-disabled, 3 = ok, 4 = sensor-fail, 5 = warning-temp-warm, 6 = warning-temp-cold, 7 = critical-temp-warm, 8 = critical-temp-cold, 9 = damage-temp-warm

Temperature Sensor CPU (1) = 1.3.6.1.4.1.231.2.10.2.2.5.2.1.1.3.0.1

1 = unknown, 2 = sensor-disabled, 3 = ok, 4 = sensor-fail, 5 = warning-temp-warm, 6 = warning-temp-cold, 7 = critical-temp-warm, 8 = critical-temp-cold, 9 = damage-temp-warm

Temperature Sensor CPU (2) = 1.3.6.1.4.1.231.2.10.2.2.5.2.1.1.3.0.2

1 = unknown, 2 = sensor-disabled, 3 = ok, 4 = sensor-fail, 5 = warning-temp-warm, 6 = warning-temp-cold, 7 = critical-temp-warm, 8 = critical-temp-cold, 9 = damage-temp-warm

Please feel free to comment if you have any other useful OIDs or require further assistance

Poor Computer Performance due to Windows Power Management Settings

In an effort to be more “Green” you will often find that your shiny new computer, laptop or server have Power Management already set to “Balanced” or “Power Saver”.  This can be very useful for cutting your energy bills and saving the planet but sometimes you just get the need for speed.

It’s easy to check your current “Power Plan” in Microsoft Windows Vista, 7, Server 2008 or Server 2008 R2.  Simply click on the Windows Start Menu or Orb if you are using the Aero theme and then select “Control Panel”.  Once in “Control Panel” you can either find it under it’s category “Hardware and Sound” then “Power Options” or if you are in classic control panel mode then you will just need to click “Power Options”.

Once in Power Options you will usually only be presented with three options to choose from, most will find “High Performance” the best option if they want to avoid the occasional slowdowns that power management can introduce.  You will also find that on a laptop the screen brightness is usually increased in this mode and the laptop is not going to keep going to sleep if you walk away from your desk for a few minutes.

If you favour a nice balance between the two then your next best option is “Balanced”.

The “Power Saver” Plan which is the third option is really just for laptop users in my opinion, it’s great for a long flight or train ride where you just need to get some basic Word Documents typed up or reviewed.

[RESOLVED] You must close all dialog boxes before you can close Exchange Management Console

After installing Internet Explorer 9 on your Microsoft Exchange 2007 or Exchange 2010 mail servers you may have been noticing that the Exchange Management Console will refuse to close and simply state “You must close all dialog boxes before you can close Exchange Management Console”.

This has been a long running issue but has finally been resolved by the Microsoft Internet Explorer Developer Team.

Please note that this issue is now resolved by installing the latest cumulative security update for Internet Explorer, The fix was first included in security update 2618444 http://support.microsoft.com/kb/2618444

Information on the scope of this issue can still be found here KB 2624899 http://support.microsoft.com/kb/2624899

You can request the hotfix by visiting Microsofts website and searching for the following Knowledge Base article KB 2624899

Note: The hotfix is actually for Internet Explorer 9 rather than Microsoft Exchange but does actually resolve the issues with the Exchange Management Console not closing correctly.