A new version of this MP Unix/Linux MP for SCOM is available here. The version includes agents with version 18.104.22.1688.
Testing OpsLogix Oracle Intelligent Management Pack
OpsLogix is a Microsoft System Center Alliance partner which develops innovative products for (virtual) infrastructure management. In my experience I was previously working with Oracle Intelligent Management Pack by supporting the SCOM environment of one of OpsLogix reference customers. I’ve never had issues with that MP. As being only supporting part I was not involved in implementing this MP but recently I was given this opportunity so this blog post is about my experience with OpsLogix Oracle Intelligent Management Pack.
First I want to start that instead of testing the Oracle IMP in supported scenario I’ve decided to test in unsupported environment in order to prove how good this MP is. I’ve always been enthusiast so I just I couldn’t resist. Also I want to make a notice that if you are deploying in production always use supported scenario.
Before introducing my test environment let’s first see what the architecture of the Oracle IMP is:
As we can see you just has to have one Windows node with SCOM Agent on it and ODAC.Net components installed. That node acts as a proxy and connects to all you Oracle database weather they lie on Windows OS, Unix OS or Linux OS. This architecture makes the MP very flexible which is especially important in the changes about unix an linux agents changes coming in SCOM 2012 R2. Basically it makes the MP SCOM 2012 R2 ready.
Now let’s look of how my lab looks:
· SCOM 2012 R2 Preview server that is installed on Windows Server 2012 R2 Preview.
· Oracle ODAC.Net components installed on the SCOM 2012 R2 Preview Management Server. You can install them on separate node but I’ve used my SCOM management server for simplicity. The components require .NET Framework 2.0 and are supported on Windows 2003/2008/2008R2 with x86 or x64 architecture. In production install them only on supported systems. I am sure that in the future OpsLogix will offer support for WS 2012 also.
· Windows Server 2012 (DB1) with Oracle 12c installed on it. Oracle 12c is not supported by the Oracle IMP but I’ve wanted to see if it is possible to add such database.
· Windows Server 2012 (DB2) with Oracle 11g installed on it.
After the overview of the lab we can continue with the first steps of implementing Oracle IMP.
1. First make sure you’ve installed .NET Framework 2.0 on the node that you will use as proxy. I already had it installed on my SCOM 2012 R2 Preview management server.
2. Second install SCOM agent on that same server. As my server is management server I do not need to do that.
3. Next you can proceed with installing Oracle ODAC.Net components. OpsLogix provides all components in a zip file that you can extract and then you run a simple script that install everything you need.
4. After successful installation you will see oracle folder on C:\ with all components:
5. After this procedure you can proceed with importing the OpsLogix Oracle IMP trough the SCOM console
6. You can see that you even have unsealed MP ready for overrides.
7. Everything is imported successful on SCOM 2012 R2.
8. After importing the first thing you need to do is to import your License keys in order to be able to monitor any Oracle database instance.
9. Importing is very easy you have to go to Monitoring -> OpsLogix -> OpsLogix Licensing Dashboard -> Add License.
10. After adding your license you can see all information about the license.
11. Next is to add the node(s) that will act as proxy for monitoring your Oracle database. You go to OpsLogix -> Oracle -> Oracle IMP Configuration Dashboard. The MP automatically detects all your SCOM Windows agents and lists them so you can just select the node(s) that will act as proxy and add them.
12. After adding monitoring node(s) you select Add/Remove instances tab to add databases that you want to monitor.
13. A simple information is added to monitor database as monitoring node, server name, instance name, port and credentials. It is very easy to add databases for monitoring. In fact as I’ve hadn’t any experience with Oracle databases it was harder for to actually configure the databases themselves than to add them for monitoring.
14. Let’s first add DB2 with Oracle 11g installed on it and then DB1 with Oracle 12c.
15. After a couple of minutes you will see both instances being discovered completely. Even that 12c is not supported that instance is discovered with all of its properties:
16. Now let’s see what capabilities this MP has. The MP has Oracle diagram where you can see health map of your Oracle instances and drill down to the root cause of every issue:
17. In the Action menu you will find three tasks:
18. In order to use these tasks you have to copy two files on all of your management servers:
19. You will also find a backup state view. This is very useful for database administrators.
20. You will also find a separate folder for Storage that you will find the different components of the Oracle database architecture in separate views. This helps locating problems faster.
21. What I like most is the Instance performance view where you can see and compare all performance data that is gathered.
22. As we know there is no perfect MP you could always find an error or performance counter that is not monitored for your particular case. The OpsLogix Oracle IMP covers that scenario by providing 3 templates for rules and monitors (Oracle Alert Rule, Oracle Performance Collection Rule and Oracle Two-State Monitor Template) so you can extend the MP very easy.
23. The last I want cover reporting. A lot of good MPs just do not have reporting but this one has one report which is very good. The MP gives you one general report that provides you with availability and performance which are the most common requirements for reports:
As a summary I can say that OpsLogix Oracle IMP is very easy to implement, will offer you with everything you need to monitor your Oracle database and it is definitely SCOM 2012 R2 ready.
Microsoft System Center 2012 R2 Configuration Manager – Clients for Additional Operating Systems
As SCCM 2012 R2 Preview was released a couple of days before the additional clients are also released with Preview Label. The clients bring a lot of support for non-Windows operating systems and can be download from here.
The following Mac versions are supported in this release:
- Mac OS X 10.6 (Snow Leopard)
- Mac OS X 10.7 (Lion)
- Mac OS X 10.8 (Mountain Lion)
The following scenarios are supported through the Mac client in Microsoft System Center 2012 R2 Configuration Manager Preview:
- Discovery – Discovers Mac OS X system in Active Directory and through network discovery
- Hardware Inventory – Provides hardware inventory and auditing of computers running Mac OS X, including a list of installed software similar to add/remove programs for Windows systems.
- Settings Management – Ensures computers running Mac OS X comply with company policies using scripts and preference list management.
- Application Deployment – Distributes required software via app model.
- Software Updates Management – Distributes patches utilizing Software Distribution and Settings management features.
The following UNIX and Linux versions are supported in this release.
- AIX Version 7.1, 6.1, 5.3
- Solaris Version 11 (SPARC and x86) , 10 (SPARC and x86), 9 (SPARC)
- HP-UX Version 11iv2 (PA-RISC and IA64) , 11iv3 (PA-RISC and IA64)
- RHEL Version 6 (x64 and x86) , 5 (x64 and x86), 4 (x64 and x86)
- SLES Version 11 (x64 and x86), 10 (x64 and x86), 9 (x86)
- CentOS Version 6 (x64 and x86), 5 (x64 and x86)
- Debian Version 6 (x64 and x86), 5 (x64 and x86)
- Ubuntu Version 12.4 LTS (x64 and x86), 10.4 LTS (x64 and x86)
- Oracle Linux 6 (x64 and x86), 5 (x64 and x86)
The following scenarios are supported by the UNIX and Linux clients:
- Hardware Inventory – Hardware inventory can be viewed through Resource Explorer and can be used to create collections of UNIX and Linux computers.
- Software Inventory – Through hardware inventory the list of natively installed software can be gathered from the UNIX and Linux computers – similar to add/remove programs for Windows systems.
- Software Distribution – Deploy new software, update existing software and apply OS patches to collections of UNIX/Linux computers (using a package and program). Run arbitrary maintenance scripts on a collection of UNIX/Linux servers.
- Secure and Authenticated Communications
- Consolidated Reports
Updated: Microsoft System Center 2012 Service Pack 1 Configuration Manager – Clients for Additional Operating Systems
The SCCM 2012 SP1 clients for the following operating systems are updated:
- Mac OS X – 10.6, 10.7, 10.8
- AIX – 7.1, 5.3
- HP-UX – 11v2, 11v3
- Linux – RHEL Version 6, 5, 4; SLES Version 11, 10, 9;CentOS Version 6, 5;Debian Version 6, 5;Ubuntu Version 12.4 LTS, 10.4 LTS;Oracle Linux 6, 5
- Solaris – 11, 10, 9
The following changes are introduced:
- Client Build Version 22.214.171.12448
- Added support for the following operating systems – AIX, HP-UX, Solaris 11, CentOS, Debian, Oracle Linux and Ubuntu.
- Uses Open Management Infrastructure CIM server (OMI Version 126.96.36.199)
- Implemented a Universal Agent model that supports different Linux distributions.
- Fixed miscellaneous bugs
You can download them all from here.
Update Rollup 5 for System Center 2012
While waiting for Update Rollup 2 for System Center 2012 SP1 it seems System Center 2012 without SP1 received its UR5. In this update only two of the components receive fixes:
Virtual Machine Manager (KB2824618)
A host that is put into maintenance mode does not load-balance virtual machines in a cluster during evacuation. This causes host reserve saturation.
Operations Manager (KB2831729)
The Solaris agent could run out of file descriptors when many multi-version file systems (MVFS) are mounted.
Logical and physical disks are not discoverable on AIX-based computers when a disk device file is contained in a subdirectory.
Rules and monitors that were created by using the UNIX/Linux Shell Command templates do not contain overridable ShellCommand and Timeout parameters.
Process monitors that were created by using the UNIX/Linux Process Monitoring template cannot save in an existing management pack that has conflicting references to library management packs.
The Linux agent cannot install on a CentOS or Oracle Linux host by using the FIPS version of OpenSSL 0.9.8.
Full description of the update and download links you kind find in KB article.
Read carefully the installation instructions as the update for SCOM has some special instructions. I would also wait System Center Monitoring Pack for UNIX and Linux Operating Systems to be updated because it is part of the update. The current download is still from 01.08.2013.