Just moments ago, Service Manager 2010 has been RTMed. A product which is very dear to my heart, I have been working on it since its Beta1 days and now with the RTMed version I am happy to see such a wonderful product being shipped to the end user.
http://blogs.technet.com/servicemanager/archive/2010/04/20/announcing-system-center-service-manager-2010-rtm.aspx
21 April 2010
02 April 2010
UNIX Noob trying to deploy OpsMgr to monitor Sun Solaris
The title says it loud and clear ... me being a UNIX noob learnt some new stuffs today.
Mission Objective: Deploy OpsMgr to monitor Sun Solaris
Target Environment: Sun Solaris 10
Mission Target: Monitor Sun Solaris 10 OS & Oracle DB running in it.
So to start things, make sure that the Sun Server met the following requirements especially on the OS patch !
As for OpsMgr pre-req, besides the installation pre-req; you need to ensure that you have the relevant RunAs Accounts created, correctly distributed & attached to the Run As Profiles for the Unix Servers.
Detailed steps available here in the following URL:
http://technet.microsoft.com/en-us/library/dd788981.aspx
Next, I manually installed the Cross Platform agent
Full details on Manual Installation of Cross Platform agents is available in the following link:
http://technet.microsoft.com/en-us/library/dd789016.aspx
Note: Remember to jot down the hostname of the server. This is extremely important especially for certificate issueance. If your DNS server does not include the Sun Server hostname in the DNS record, you need to manually enter this hostname into the OpsMgr RMS server hostfile.
Now back in OpsMgr, run the discovery for the UNIX/LINUX Server. Now the catch here; you will need to communicate with the Sun server via SSH. I was given a root account to discover the Sun server and in most circumstances as well as a default behavior; root account is not permitted to access via SSH. (Security Issue).
So your option is either to use another account or enable root account to login via SSH (which I will share in my next post)
The moment your Sun server is being discovered, you will be prompted to Sign the certificate; select the Sun server checkbox and click on Sign. A successfully signed certificate will bring you to the next screen which show you that the Sun server has been discovered.
Complete the Wizard and your Sun server will be discovered and monitoring will kick in.
Mission Objective: Deploy OpsMgr to monitor Sun Solaris
Target Environment: Sun Solaris 10
Mission Target: Monitor Sun Solaris 10 OS & Oracle DB running in it.
So to start things, make sure that the Sun Server met the following requirements especially on the OS patch !
| Required Package | Description | Minimum Version |
| Required OS patch | PAM memory leak | 112960-48 |
| SUNWlibC | Sun Workshop Compilers Bundled libC (sparc) | 5.9,REV=2002.03.18 |
| SUNWlibms | Forte Developer Bundled Shared libm (sparc) | 5.9,REV=2001.12.10 |
| OpenSSL | SMCosslg (sparc) Sun does not provide a version of OpenSSL for Solaris 9 SPARC. There is a version available from Sunfreeware. | 0.9.7g |
| PAM | Pluggable Authentication Modules SUNWcsl, Core Solaris, (Shared Libs) (sparc) | 11.9.0,REV=2002.04.06.15.27 |
As for OpsMgr pre-req, besides the installation pre-req; you need to ensure that you have the relevant RunAs Accounts created, correctly distributed & attached to the Run As Profiles for the Unix Servers.
Detailed steps available here in the following URL:
http://technet.microsoft.com/en-us/library/dd788981.aspx
Next, I manually installed the Cross Platform agent
-
Transfer the agent (scx-
- - .pkg.Z) to the Solaris server. scx-- - .pkg.Z -
Run the following command:
uncompress scx-- - .pkg.Z -
To install the package, type
pkgadd -d scx-- - .pkg MSFTscx -
To verify that the package is installed, type
pkginfo –l MSFTscx -
To verify that the Microsoft SCX CIM Server is running, type
svcs scx-cimd
http://technet.microsoft.com/en-us/library/dd789016.aspx
Note: Remember to jot down the hostname of the server. This is extremely important especially for certificate issueance. If your DNS server does not include the Sun Server hostname in the DNS record, you need to manually enter this hostname into the OpsMgr RMS server hostfile.
Now back in OpsMgr, run the discovery for the UNIX/LINUX Server. Now the catch here; you will need to communicate with the Sun server via SSH. I was given a root account to discover the Sun server and in most circumstances as well as a default behavior; root account is not permitted to access via SSH. (Security Issue).
So your option is either to use another account or enable root account to login via SSH (which I will share in my next post)
The moment your Sun server is being discovered, you will be prompted to Sign the certificate; select the Sun server checkbox and click on Sign. A successfully signed certificate will bring you to the next screen which show you that the Sun server has been discovered.
Complete the Wizard and your Sun server will be discovered and monitoring will kick in.
Subscribe to:
Posts (Atom)