Home > OpsMgr'07 > Monitoring cross platform operating systems

Monitoring cross platform operating systems


To monitor the cross platform these are the point you need to follow-

1. Discover and install the agent

2. Configure runas accounts

3. Varification

1. Discover client and install agent

Open the Operations console with an account that is a member of the Operations Manager 2007 R2 Administrators profile. Select the Administration view, and click on Discovery Wizard.

Select What you want to discover-

· Windows Computer

· Unix/Linux Computers

· Network Device

Here we will discover Linux computers. Click Next.

In define criteria wizard click Add.

Give IP address and credentials for computer you want to discover.

Enable SSH based discovery and click on Discover.

View discovery progress.

After completion of successful discovery, click Next, it will install agent on remote system.

Check client installation status. And click Done to close wizard.

Click details to check status.

2. Configure Run As for cross platform

In Microsoft System Center Operations Manager 2007 R2, Run As profiles and Run As accounts are used to provide credentials that have the necessary privileges that the default Action account might not have for running rules, tasks, and monitors. To monitor UNIX and Linux computers, you must configure both the UNIX Action account profile and the UNIX Privileged account profile. You must go through the “To configure run as for cross platform” procedure below once for each profile.

If you will not configured Run As account for cross platform monitoring, you may see this alert in SCOM console.

Alert Name – Secure Reference Override failure.

Follow below given steps to resolve this issue.

Open the Operations console with an account that is a member of the Operations Manager 2007 R2 Administrators profile.

Select the Administration view.

In the navigation pane under Run As Configuration, select Runas Account.

Right click and Create Run As Account to start the Create Run As Account wizard.

If the Introduction page appears, click Next.

On the General page, select Basic Authentication from the Run As Account Type list. Notice that there are other options to choose from.

In the Display Name box, enter a name to identify the UNIX Action Account or UNIX Privileged Account credentials. Here we are creating UNIX Action Account so enter Step by Step Run As UNIX Action Account, do the same procedure for UNIX Privileged Account and give name as Step by Step Run As UNIX Privileged Account, and then click Next.

On the credential page, enter appropriate values in the Account Name, Password, and Confirm Password boxes, and then click Next.

In distribution security page click More Secure option, so that you have to manually select the computer to which this credential will be distributed.

This creates the Step by Step Run As UNIX Action Account or Step by Step Run As UNIX Privileged Account object and maps it to the actual UNIX account credentials that will be used for non-privileged or privileged interaction with the UNIX-based computers that you will be monitoring.

Click Close to close the Create Run As Account wizard.

In the Accounts pane, double-click the account you just created.

i.e. Step By Step Run As UNIX Action Account and Step By Step Run As UNIX Privileged Account

In the Run As Account Properties dialog box, select the Distribution tab and choose the Distribute credentials to selected computers option.

Click Add to open the Computer Search dialog box.

 

From the Option list, choose Show management servers, and then click Search.

In the Available items text box, choose the management server that these credentials will be distributed to, and then click Add.

Click OK to close the Computer Search dialog box.

Click OK to close the Run As Account Properties dialog box.

In the navigation pane under Run As Configuration, select Profiles.

Right-click the UNIX Action Account or UNIX Privileged Account profile, and select properties from the context menu to open the Run As Profile Properties – UNIX Action Account or Run As Profile Properties – UNIX Privileged Account dialog box.

Click Add to select a Run As account to add to this profile.

If you have selected UNIX Action Account then in run as account option select Step By Step Run As UNIX Action Account.

And, If you have selected UNIX Privileged Account then in run as account option select Step By Step Run As UNIX Privileged Account.

Add class to this Run As Account.

Click save to save this configuration.

Click close to finish it.

That’s it, now you have configured Run As Account for cross platform.

3. Verification of Unix Client reporting

Click on Monitoring pane and then click Unix/Linux server.

The same will show you the Status of client.

After our initial discovery of the system, the pieces of Health Explorer actually populated were rather limited. These included the Availability/Unix Heartbeat Monitor, and the Configuration pieces.

After a little while, additional sections started appearing . The Operating System Availability Rollup and each of the core services were added, and the Performance counters started gathering data as well.

Health explorer View.

Alert if service stops.

See Disk Performance report for Linux client.

Advertisements
Categories: OpsMgr'07
  1. No comments yet.
  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: