Tuesday, 24 March 2009

SCOM -Tunning Thresholds

Hello,

About System Center Operations Manager, I've found very interesting information about Tunning thresholds in SCOM on Kevin Holman's Blog:

* Low: Inner: 4.01 Outer: 4.51 Rule Sensitivity: 4.01
* Low-Mid: Inner: 3.77 Outer: 4.27 Rule Sensitivity: 3.77
* Mid: Inner: 3.29 Outer: 3.79 Rule Sensitivity: 3.29
* Mid-High: Inner: 2.81 Outer: 3.31 Rule Sensitivity: 2.81
* High: Inner: 2.57 Outer: 3.07 Rule Sensitivity: 2.57


Links to the source:

http://blogs.technet.com/kevinholman/archive/2008/03/19/self-tuning-thresholds-love-and-hate.aspx

Tuesday, 17 March 2009

IBM RSA - The Perl script

So, here is some perl code that can help getting informations from IBM RSA.

Based on Net::SNMP module and on the oid I provided below.


sub get_status

{
my $rsa_status = "unknown";

#Define SNMP Session
my ($session, $error) = Net::SNMP->session( -hostname => $_[0], -community => $_[1], -port => 161 );

#Error Check
if (!defined($session))

{
$rsa_status = "SNMP_Error";
}
else
{
#SNMP Get
my $sysStatus = "$_[2]";
my $result = $session->get_request(-varbindlist => [$sysStatus]);

#Error check
if (!defined($result))
{
$rsa_status = "SNMP_Error";
}

else

{
if ($result->{$sysStatus} == 0)
{$rsa_status = "Critical";}
elsif ($result->{$sysStatus} == 2)
{$rsa_status = "Warning";}
elsif ($result->{$sysStatus} == 4)
{$rsa_status = "System";}
elsif ($result->{$sysStatus} == 255)
{$rsa_status = "Normal";}
}
$session->close;

return $rsa_status;
}

Tuesday, 10 March 2009

IBM Remote Supervisor Adapter

My firsts articles will be about IBM RSA (and Blade Center).

Less than two year ago, I was asked to find a quick way to monitor our IBM Hardware infrastructure.

I first though about and integration into CA NSM, then I though about IBM director but that wasn't easy to deploy quickly.

Now, with my current knowledge, I think if I had to redo it I will use Spectrum for this as this is very easy to import MIB and to say what to do with events.

But at that time, I started building my own solution based on SNMP Capabilities of IBM RSA. This SNMP agent is able to return all Hardware errors of your IBM server.


In the MIB, I was able to found that the following oid where the status:
  • For RSA: '1.3.6.1.4.1.2.3.51.1.2.7.1.0'
  • For Blade Center: '1.3.6.1.4.1.2.3.51.2.2.7.1.0'
When you do an SNMP get on this, you'll have one of the following value:
  • 0 for Critical
  • 2 for Warning
  • 4 for System Error
  • 255 for Normal.
To have details about the cause of the status, you should look at the following SNMP table:
  • For RSA: 1.3.6.1.4.1.2.3.51.1.2.7.2.1.3
  • For Blade Center: '1.3.6.1.4.1.2.3.51.2.2.7.2.1.3'

Next post will be some pieces of my Perl code to show how you can do it.

What is this Blog?

This Blog is about Network & System Management as the title said.

I'm working in this world for more than 4 years now and I will try to share some knowledges/resources about this domain.

I'm used to work with CA Network and System Management (NSM), Microsoft Operations Manager (MOM), Microsoft System Center Operations Manager (SCOM), Spectrum but I also do a lot of customisations essentially in Perl.