Novell Linux Management Pack 1.0.1 for System Center ... · Novell Linux Management Pack 1.0.1 for...

Novell®

novdocx (en) 17 Septem

ber 2009

AUTHORIZED DOCUMENTATION

Novell Linux Management Pack 1.0.1 for System Center Operations Manager

www.novell.com

Linux Management Pack for System Center Operations Manager

1.0.1December 8, 2009

User Guide


ber 2009

Legal Notices

Novell, Inc., makes no representations or warranties with respect to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc., reserves the right to revise this publication and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes.

Further, Novell, Inc., makes no representations or warranties with respect to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc., reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to notify any person or entity of such changes.

Any products or technical information provided under this Agreement may be subject to U.S. export controls and the trade laws of other countries. You agree to comply with all export control regulations and to obtain any required licenses or classification to export, re-export or import deliverables. You agree not to export or re-export to entities on the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in the U.S. export laws. You agree to not use deliverables for prohibited nuclear, missile, or chemical biological weaponry end uses. See the Novell International Trade Services Web page (http://www.novell.com/info/exports/) for more information on exporting Novell software. Novell assumes no responsibility for your failure to obtain any necessary export approvals.

Copyright © 2009 Novell, Inc. All rights reserved. No part of this publication may be reproduced, photocopied, stored on a retrieval system, or transmitted without the express written consent of the publisher.

Novell, Inc., has intellectual property rights relating to technology embodied in the product that is described in this document. In particular, and without limitation, these intellectual property rights may include one or more of the U.S. patents listed on the Novell Legal Patents Web page (http://www.novell.com/company/legal/patents/) and one or more additional patents or pending patent applications in the U.S. and in other countries.

Novell, Inc.404 Wyman Street, Suite 500Waltham, MA 02451U.S.A.www.novell.com

Online Documentation: To access the latest online documentation for this and other Novell products, see the Novell Documentation Web page (http://www.novell.com/documentation).

http://www.novell.com/info/exports/

http://www.novell.com/company/legal/patents/

http://www.novell.com/documentation


ber 2009

Novell Trademarks

For Novell trademarks, see the Novell Trademark and Service Mark list (http://www.novell.com/company/legal/trademarks/tmlist.html).

Third-Party Materials

All third-party trademarks are the property of their respective owners.

http://www.novell.com/company/legal/trademarks/tmlist.html

4 Novell


ber 2009

Linux Management Pack 1.0.1 for System Center Operations Manager

Contents


ber 2009

About This Guide 7

1 Getting Started 91.1 Product Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91.2 Obtaining and Licensing the Product . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101.3 Packages Included in the Product . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

1.3.1 SLES 10 x86_64 Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101.3.2 SLES 10 i586 Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111.3.3 SLES 10 Noarch Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121.3.4 SLES 11 x86_64 Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121.3.5 SLES 11 i586 Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131.3.6 SLES 11 Noarch Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131.3.7 RHEL 5.x x86_64 Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131.3.8 RHEL 5.x i386 Packages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141.3.9 RHEL 5.x Noarch Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

2 Installation 152.1 Installation Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152.2 Installing the Platform-Specific Management Pack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162.3 Importing and Configuring the Management Packs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

2.3.1 Importing the Management Pack. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162.3.2 Configuring Run As Accounts and Run As Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . 17

2.4 System Discovery and Deployment of Agent Extensions for the Management Pack . . . . . . . 192.4.1 Using Operations Manager Tasks to Deploy Agent Extensions for Linux Services. . 192.4.2 Manually Installing the Agent on SLES 10 Machines . . . . . . . . . . . . . . . . . . . . . . . . 202.4.3 Manually Installing the Agent on SLES 11 Machines . . . . . . . . . . . . . . . . . . . . . . . . 202.4.4 Manually Installing the Agent on RHEL 5 Machines . . . . . . . . . . . . . . . . . . . . . . . . . 21

3 Understanding Management Pack Operations 233.1 Novell General Services Management Pack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

3.1.1 Parts of the Novell General Services Management Pack . . . . . . . . . . . . . . . . . . . . . 233.1.2 Appearance of the General Services Management Pack in Operations Manager . . 25

3.2 CUPS Service Management Pack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263.2.1 Parts of the CUPS Service Management Pack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263.2.2 Appearance of the CUPS Service Management Pack in Operations Manager. . . . . 29

3.3 DHCP Service Management Pack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303.3.1 Parts of the DHCP Service Management Pack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303.3.2 Appearance of the DHCP Service Management Pack in Operations Manager. . . . . 34

3.4 DNS Service Management Pack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353.4.1 Parts of the DNS Service Management Pack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353.4.2 Appearance of the DNS Service Management Pack in Operations Manager . . . . . . 40

3.5 Firewall Service Management Pack. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413.5.1 Parts of the Firewall Service Management Pack . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413.5.2 Appearance of the Firewall Service Management Pack in Operations Manager. . . . 46

3.6 NFS Service Management Pack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473.6.1 Parts of the NFS Service Management Pack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473.6.2 Appearance of the NFS Service Management Pack in Operations Manager . . . . . . 52

3.7 OpenLDAP Service Management Pack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Contents 5

6 Novell


ber 2009

3.7.1 Parts of the OpenLDAP Service Management Pack . . . . . . . . . . . . . . . . . . . . . . . . . 533.7.2 Appearance of the OpenLDAP Service Management Pack in Operations Manager. 60

3.8 Samba Service Management Pack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 613.8.1 Parts of the Samba Service Management Pack . . . . . . . . . . . . . . . . . . . . . . . . . . . . 613.8.2 Appearance of the Samba Service Management Pack in Operations Manager . . . . 66

3.9 Linux Agent Extension Management Pack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 683.9.1 Parts of the Linux Agent Extension Management Pack. . . . . . . . . . . . . . . . . . . . . . . 683.9.2 Appearance of the Linux Agent Extension Status Management Pack in Operations

Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 703.10 Novell Support Advisor Management Pack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

3.10.1 Parts of the Novell Support Advisor Management Pack . . . . . . . . . . . . . . . . . . . . . . 723.10.2 Appearance of the Novell Support Advisor Management Pack in Operations

Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94



ber 2009

About This Guide

This User Guide for the Novell® Linux* Management Pack explains how to install and navigate the Novell Linux Management Packs for Microsoft* Operations Manager 2007 (R2) RC.

Chapter 1, “Getting Started,” on page 9Chapter 2, “Installation,” on page 15Chapter 3, “Understanding Management Pack Operations,” on page 23

Audience

This document is intended for use by IT system administrators who monitor server operations. It can also be used by individuals who plan, design, and implement such a monitoring solution. If you have one of these roles, you should also have experience using Operations Manager 2007 (R2) and familiarity with administering Linux services (SUSE® and Red Hat*) in order to understand these procedures.

Feedback

We want to hear your comments and suggestions about this manual and the other documentation included with this product. Please use the User Comments feature at the bottom of each page of the online documentation, or go to www.novell.com/documentation/feedback.html (http://www.novell.com/documentation/feedback/feedback/index.html?page=/documentation/feedback/feedback/data/hc7znq4j.html) and enter your comments there.

Documentation Updates

For the most recent version of the Novell Linux Management Packs User Guide, visit the Novell Linux Management Pack Web site (http://www.novell.com/documentation/sles10_mgtpack/index.html).

Documentation Conventions

In Novell documentation, a greater-than symbol (>) is used to separate actions within a step and items in a cross-reference path.

A trademark symbol (®, TM, etc.) denotes a Novell trademark. An asterisk (*) denotes a third-party trademark.

About This Guide 7

http://www.novell.com/documentation/feedback/feedback/index.html?page=/documentation/feedback/feedback/data/hc7znq4j.html

http://www.novell.com/documentation/sles10_mgtpack/index.html

http://www.novell.com/documentation/sles10_mgtpack/index.html

8 Novell


ber 2009


1novdocx (en) 17 S

eptember 2009

1Getting Started

Novell® Linux* Management Pack for System Center Operations Manager expands the monitoring capabilities of Operations Manager in enterprise environments by enabling monitoring of key Linux services. A consolidated operations console displays the health of these services—along with Microsoft Cross Platform Extensions—so that you can respond to alerts, run diagnostics, and consider possible solutions for detected issues.

The Novell Linux Services Management Pack (NLMP) uses WS-Management 1.1, a Web services-based protocol that enables remote computer management over HTTP and HTTPS. WS-Management enables secure and efficient data transfers by requiring authentication and using HTTPS as the transport. It is required for all communication between NLMP and Linux systems.

This section includes the following information:

Section 1.1, “Product Features,” on page 9Section 1.2, “Obtaining and Licensing the Product,” on page 10Section 1.3, “Packages Included in the Product,” on page 10

1.1 Product FeaturesThe installation package for NLMP includes additional agent extensions for Microsoft Cross Platform Extensions installation. When installed, the combined components add the following features to Operations Manager:

Monitoring of services in SLES 10 Service Pack 2 (or higher), SLES 11, and Red Hat 5.x.BIND/DNSDHCPSambaOpenLDAPSUSE firewallCUPSNFS

Discovery of Linux servers based on the Microsoft Cross Platform Discovery WizardAutomatic deployment for Management Agent plug-insReporting of the service state (running or not running)Stop/Start/Restart capabilities for all servicesAvailability of alerts for most servicesTracking of allocated IP address by DHCP serviceMonitoring of Samba shares and usersNLMP is integrated with Novell Support Advisor, an automated self-help tool used to support and diagnose SUSE Linux Enterprise Server, Open Enterprise Server (Linux) and associated products. Novell Support Advisor provides customers with a streamlined way to perform both proactive and reactive system diagnostic tasks in a local, secure, and automated fashion.

Getting Started 9

10 Novell


ber 2009

NOTE: This integration is not available for RHEL 5.x.

1.2 Obtaining and Licensing the ProductTo download the product for evaluation or purchase, contact an authorized Novell Sales representative, a Certified Novell Partner or the Novell TeleWeb Sales team.

You can use NLMP software for evaluation for 90 days. After that time you can either purchase the product or completely remove it from your environment. For more information, see the license the product.

1.3 Packages Included in the Product The following packages are included with the product.

Section 1.3.1, “SLES 10 x86_64 Packages,” on page 10Section 1.3.2, “SLES 10 i586 Packages,” on page 11Section 1.3.3, “SLES 10 Noarch Packages,” on page 12Section 1.3.4, “SLES 11 x86_64 Packages,” on page 12Section 1.3.5, “SLES 11 i586 Packages,” on page 13Section 1.3.6, “SLES 11 Noarch Packages,” on page 13Section 1.3.7, “RHEL 5.x x86_64 Packages,” on page 13Section 1.3.8, “RHEL 5.x i386 Packages,” on page 14Section 1.3.9, “RHEL 5.x Noarch Packages,” on page 14

1.3.1 SLES 10 x86_64 Packages

Table 1-1 SLES 10 x86_64 Packages on the NLMP ISO

Package Name Description

cmpi-bindings-pywbem-0.4.0-8.1.x86_64.rpm Adapter used to write and run CMPI-type CIM providers in Python.

libgcj-4.1.2_20070115-0.21.x86_64.rpm Java Runtime Library for gcc.

novell-scx-mp-0.2.0-35.1.x86_64.rpm Novell/SUSE providers for Microsoft System Center Management Pack for SLES Services.

python-elementtree-1.2.6-18.2.x86_64.rpm The Element type is a simple but flexible container object, designed to store hierarchical data structures, such as simplified XML infosets, in memory. The element type can be described as a cross between a Python list and a Python dictionary.



ber 2009

1.3.2 SLES 10 i586 Packages

Table 1-2 SLES 10 i586 Packages on the NLMP ISO

python-ldap-2.0.11-14.2.x86_64.rpm python-ldap provides an LDAP client API for Python in the spirit of RFC1823. It includes a Python module called _ldapmodule that wraps an LDAP C library, an object-oriented API for X.500 directories.

python-pywbem.rpm PyWBEM is a Python module for making CIM operation calls using the WBEM protocol to query and update managed objects.

python-xml-2.4.2-18.13.x86_64.rpm The expat module is a Python interface to the expat XML parser. Since Python2.x, it is part of the core Python distribution.

rpm-python-4.4.2-43.28.x86_64.rpm The rpm-python package contains a module that permits applications written in the Python programming language to use the interface supplied by RPM Package Manager libraries.


cmpi-bindings-pywbem-0.4.0-8.1.i586.rpm Adapter used to write and run CMPI-type CIM providers in Python.

libgcj-4.1.2_20070115-0.21.i586.rpm Java Runtime Library for gcc.

novell-scx-mp-0.2.0-35.1.i586.rpm Novell/SUSE providers for Microsoft System Center Management Pack for SLES Services.

python-elementtree-1.2.6-18.2.i586.rpm The Element type is a simple but flexible container object, designed to store hierarchical data structures, such as simplified XML infosets, in memory. The element type can be described as a cross between a Python list and a Python dictionary.

python-ldap-2.0.11-14.2.i586.rpm python-ldap provides an LDAP client API for Python in the spirit of RFC1823. It includes a Python module called _ldapmodule that wraps an LDAP C library, an object-oriented API for X.500 directories.

python-pywbem.rpm PyWBEM is a Python module for making CIM operation calls using the WBEM protocol to query and update managed objects.

python-xml-2.4.2-18.13.i586.rpm The expat module is a Python interface to the expat XML parser. Since Python2.x, it is part of the core Python distribution.


Getting Started 11

12 Novell


ber 2009
1.3.3 SLES 10 Noarch Packages
Table 1-3 SLES 10 Noarch Packages on the NLMP ISO

1.3.4 SLES 11 x86_64 Packages

Table 1-4 SLES 11 x86_64 Packages on the NLMP ISO

rpm-python-4.4.2-43.28.i586.rpm The rpm-python package contains a module that permits applications written in the Python programming language to use the interface supplied by RPM Package Manager libraries.


cim-schema-2.17-0.3.noarch.rpm Common Information Model (CIM) is a model for describing overall management information in a network or enterprise environment. CIM consists of a specification and a schema. The specification defines the details for integration with other management models. The schema provides the actual model descriptions.

cmpi-provider-register-1.0-1.1.noarch.rpm A utility allowing CMPI provider packages to register with whatever CIMOM(s) happens to be present on the system.

cmpi-pywbem-base-0.2.0-3.2.noarch.rpm Base System CIM Providers

supportutils-1.01-53.1.noarch.rpm A package containing troubleshooting tools. This package contains the following: supportconfig, chkbin, schealth


libgcj43-4.3.3_20081022-11.18.x86_64.rpm Java Runtime Library for gcc.


python-ldap-2.3.5-1.21.x86_64.rpm python-ldap provides an LDAP client API for Python in the spirit of RFC1823. It includes a Python module called _ldapmodule that wraps an LDAP C library, an object-oriented API for X.500 directories.




ber 2009

1.3.5 SLES 11 i586 Packages

Table 1-5 SLES 11 i586 Packages on the NLMP ISO

1.3.6 SLES 11 Noarch Packages

Table 1-6 SLES 11 Noarch Packages on the NLMP ISO

1.3.7 RHEL 5.x x86_64 Packages

Table 1-7 RHEL 5.x x86_64 Packages on the NLMP ISO


libgcj43-4.3.3_20081022-11.18.i586.rpm Java Runtime Library for gcc.


python-ldap-2.3.5-1.21.i586.rpm python-ldap provides an LDAP client API for Python in the spirit of RFC1823. It includes a Python module called _ldapmodule that wraps an LDAP C library, an object-oriented API for X.500 directories.


supportutils-1.01-53.1.noarch.rpm A package containing troubleshooting tools. This package contains the following: supportconfig, chkbin, schealth


cmpi-bindings-pywbem-0.4.0-8.1.x86_64.rpm Adapter used to write and run CMPI-type CIM providers in Python.


python-pywbem-0.7-10.1.x86_64.rpm PyWBEM is a Python module for making CIM operation calls using the WBEM protocol to query and update managed objects.

Getting Started 13

14 Novell


ber 2009

1.3.8 RHEL 5.x i386 Packages

Table 1-8 RHEL 5.x i386 Packages on the NLMP ISO

1.3.9 RHEL 5.x Noarch Packages

Table 1-9 RHEL 5.x Noarch Packages on the NLMP ISO


cmpi-bindings-pywbem-0.4.0-8.1.i386.rpm Adapter used to write and run CMPI-type CIM providers in Python.


python-pywbem-0.7-10.1.i386.rpm PyWBEM is a Python module for making CIM operation calls using the WBEM protocol to query and update managed objects.


cim-schema-2.19.1-3.1.noarch.rpm Common Information Model (CIM) is a model for describing overall management information in a network or enterprise environment. CIM consists of a specification and a schema. The specification defines the details for integration with other management models. The schema provides the actual model descriptions.

cmpi-provider-register-1.0-1.1.noarch.rpm A utility allowing CMPI provider packages to register with whatever CIMOM(s) happens to be present on the system.

cmpi-pywbem-base-0.2.0-2.1.noarch.rpm Base System CIM Providers


2novdocx (en) 17 S

eptember 2009

2Installation

This section includes the following information:

Section 2.1, “Installation Prerequisites,” on page 15Section 2.2, “Installing the Platform-Specific Management Pack,” on page 16Section 2.3, “Importing and Configuring the Management Packs,” on page 16Section 2.4, “System Discovery and Deployment of Agent Extensions for the Management Pack,” on page 19

2.1 Installation PrerequisitesThe following system requirements must be met to install Novell® Linux* Management Pack for System Center Operations Manager (NLMP) and related components:

Microsoft* System Center Operations Manager 2007 (R2) RC fully installed and configuredMS Cross Platform Extensions, fully installed and configured (see Microsoft documentation for details). This includes the Management Packs and the agent on servers.Servers where you install the Management Packs must have the packages that are listed in the following table:

NOTE: Microsoft defines the package requirements for each platform.

NLMP depends on other management packs already being installed with the System Center Operations Manager 2007 before you import the Novell Management Packs:

For a list of the platform-specific RPMs included with the product, see Section 1.3, “Packages Included in the Product,” on page 10.

Required Package Description Minimum Version

glibc Standard shared libraries from the GNU C Library 2.4-31.30

libxml2 XML Library 2.6.23-15.2

Zlib ZIP Compression Library 1.2.3-15.2

openssl OpenSSL Libraries 0.9.8a-18.15

pam Pluggable Authentication Modules 0.99.3.0-28.8

Name of Management Pack Location of Management Pack

Microsoft.Linux.Library.mp C:\Program Files\System Center Management Packs

Microsoft.Unix.Library.mp C:\Program Files\System Center Operations Manager 2007

Installation 15

16 Novell


ber 2009

2.2 Installing the Platform-Specific Management PackThe platform-specific installation package for NLMP contains the installation file for NLMP and the Linux agent extensions installation file.The following table lists the installation package for the supported platforms:

1 Copy the appropriate installation package to the same machine that runs the Operations Manager Console, then double-click the file to install NLMP.The NLMP Setup Wizard starts.

2 On the License Agreement page, read the license agreement, select I accept the agreement, then click Next to continue.

3 On the Welcome page, click Next to continue the installation.4 When prompted, select the Start Menu folder, then click Next.5 On the Confirm Installation page, click Next to begin the installation.

A progress bar displays installation progress.6 When the installation is complete, click Finish to exit the wizard.

2.3 Importing and Configuring the Management PacksAfter the Management Packs are installed, you need to import and configure them.

Section 2.3.1, “Importing the Management Pack,” on page 16Section 2.3.2, “Configuring Run As Accounts and Run As Profiles,” on page 17

2.3.1 Importing the Management Pack1 In the Operations Manager 2007 Operations console, open the Administration pane, right-click

Management Packs, then click Import Management Packs.2 In the Select Management Packs dialog box, click Add, select Add from disk, navigate to

Program Files, open the Novell SLES Management Packs for System Center Operations Manager folder, select all of the Management Packs, then click Open.

3 In the Import Management Packs dialog box, ensure that the Management Packs you selected are shown in the Import list, then click Install.If Novell Management Packs is not listed, click Add to re-open the Select Management Packs dialog box, then repeat Step 2.

Supported Linux Platform Installation Package

SUSE® Linux Enterprise Server 10 SP2 (and higher)

nlmpsles10setup.exe

SUSE Linux Enterprise Server 11 nlmpsles11setup.exe

Red Hat Enterprise Linux 5.x Server nlmprhel5setup.exe



ber 2009

Progress is displayed while the Management Packs are imported. An icon next to each Management Pack indicates the success or failure of the import. When the Management Packs are successfully imported, a completion message displays at the top of the Import Management Packs dialog box.

4 Click Close to exit the Import Management Packs dialog box.

2.3.2 Configuring Run As Accounts and Run As ProfilesRun As accounts and Run As profiles together provide an appropriate identity to run a task, rule, or monitor in Operations Manager 2007. With a Run As profile, a Management Pack author can associate an identity (other than the default action account) with a module so that it can run as that identity.

A Run As account represents an identity that can be associated with a Run As profile. Management pack authors with the necessary user rights can create tasks, rules, or monitors to perform various functions. Run As accounts and Run As profiles enable tasks, rules, or monitors to run with the account that has the necessary user rights.

Operations Manager 2007 Cross Platform Extensions requires the creation of two Run As accounts; one for regular UNIX* user accounts and one for privileged UNIX accounts, such as root or super user accounts.

After the Management Packs have been imported, you need to create the Run As accounts and associate them with the UNIX action account Run As profile and UNIX privileged account Run As profile.

“Configuring Run As Accounts” on page 17“Configuring Run As Profiles” on page 18

Configuring Run As Accounts

Most administrative tasks performed on UNIX and Linux* computers are done by the root user; however, some environments prohibit direct root logins on UNIX or Linux computers. If this is the case, you will need to create a Run As account for users with regular user accounts, as well as one for users with privileged user accounts.

“Configuring a Regular UNIX User Run As Account” on page 17“Configuring a Privileged Unix User Run As Account” on page 18

Configuring a Regular UNIX User Run As Account

1 From the desktop of the machine where Operations Manager is running, click Start > Programs > System Center Operations Manager 2007 > Operations Console to start the Operations Console.

2 Click Administration, then expand the Administration node.3 Expand the Run As Configuration node, right-click Run As Configuration, then click Create

Run As Account.4 In the Create Run As Account Wizard, click Next.

TIP: If you select the Do not show this page again option on the Introduction page, the page does not display when the Create Run As Account Wizard runs.

Installation 17

18 Novell


ber 2009

5 From the Run As Account Type drop-down list, select Basic Authentication, then specify a display name to use with the Run As account and an optional description.Name the account so you can distinguish it from the privileged UNIX user Run As account (for example, CrossPlatRegUser).

6 Specify the name and password of an account on the SLES or RHEL server, then click Create to create the account and close the Create Run As Account Wizard.

Configuring a Privileged Unix User Run As Account


2 Click Administration, then expand the Administration node.3 Expand the Run As Configuration node, right-click Run As Configuration, then click Create

Run As Account.4 In the Create Run As Account Wizard, click Next.

TIP: If you select the Do not show this page again option on the Introduction page, the page does not display when the Create Run As Account Wizard runs.

5 From the Run As Account Type drop-down list, select Basic Authentication, then specify a display name to use with the Run As account and an optional description.Name the account so you can distinguish it from the regular UNIX user Run As account (for example, CrossPlatPrivUser).

6 Specify the name and password of an account with administrative privileges on the SLES or RHEL server (for example, root), then click Create to create the account and close the Create Run As Account Wizard.

Configuring Run As Profiles

“Configuring a Regular UNIX Account Run As Profile” on page 18“Configuring a Privileged UNIX Account Run As Profile” on page 19

Configuring a Regular UNIX Account Run As Profile


2 Click Administration, then expand the Administration node.3 Expand the Run As Configuration node, then click Profiles.4 In the Profiles list, right-click Unix Action Account, click Properties, click Next, then click Add.5 In the Run As account drop-down list, select the regular UNIX user you created in the previous

procedure (for example, CrossPlatRegUser).5a (Conditional) If you select All targeted objects, click OK and proceed to the next step.5b (Conditional) If you selected A selected class, group, or object, click Select, then click

Class.



ber 2009

6 In the Filter by field, enter Unix Computer, then click Search.7 In the Available items field, select Unix Computer, click Add, click OK, click OK again, then

click Close.

Configuring a Privileged UNIX Account Run As Profile


2 Click Administration, then expand the Administration node.3 Expand the Run As Configuration node, then click Profiles.4 In the Profiles list, right-click Unix Privileged Account, click Properties, click Next, then click

Add.5 In the Run As account drop-down list, select the privileged UNIX user you created in the

previous procedure (for example, CrossPlatPrivUser).5a (Conditional) If you select All targeted objects, click OK and proceed to the next step.5b (Conditional) If you selected A selected class, group, or object, click Select, then click

Class.6 In the Filter by field, enter General Service, then click Search.7 In the Available items field, select Novell General Service, click Add, click OK, then click

Close.

2.4 System Discovery and Deployment of Agent Extensions for the Management PackIMPORTANT: If you have not used the Microsoft Cross Platform Extensions Discovery Wizard to discover SLES or RHEL computers, refer to Microsoft documentation and perform the discovery. At least one SLES or RHEL server must appear in Operations Manager before you can implement the procedures in this section.

Section 2.4.1, “Using Operations Manager Tasks to Deploy Agent Extensions for Linux Services,” on page 19Section 2.4.2, “Manually Installing the Agent on SLES 10 Machines,” on page 20Section 2.4.3, “Manually Installing the Agent on SLES 11 Machines,” on page 20Section 2.4.4, “Manually Installing the Agent on RHEL 5 Machines,” on page 21

2.4.1 Using Operations Manager Tasks to Deploy Agent Extensions for Linux Services

1 From the desktop, click Start > Programs > System Center Operations Manager 2007 > Operations Console to start the Operations console.

2 In the console, click Monitoring to open the Monitoring pane.3 In the Monitoring pane, expand Unix/Linux Server, expand Novell Services, then select the

agent status monitor (according to the package you installed): SLES 10 Agent Extensions Status

Installation 19

20 Novell


ber 2009

orSLES 11 Agent Extensions StatusorRHEL 5 Agent Extensions Status

4 In the middle pane, select the server where you want to deploy the Novell agent extensions.5 In the Actions pane under Novell General Computer Tasks, select the menu item disobeying the

agent extensions you want to deploy (according to the package you installed):Deploy Novell Agent Extensions for SLES 10orDeploy Novell Agent Extensions for SLES 11orDeploy Novell Agent Extensions for RHEL 5

6 Click Run.

2.4.2 Manually Installing the Agent on SLES 10 MachinesUse the following steps if deploying agent extensions from Operations Manager was unsuccessful on SLES 10 SP2 (or higher) machines.

1 From the Windows c:\Program Files\Novell Management Packs for System Center Operations Manager folder, copy the novellsles10-mp-addon.iso file to a /tmp folder on every SLES machine where you want to install the Novell Agent Extensions.

2 At the system terminal on each SLES machine, run the following command to add the Novell Agent ISO image to the list of possible install repositories:zypper sa -t YUM iso:/?iso=/tmp/novellsles10-mp-addon.iso nmpa

3 At the system terminal of each SLES machine, run the following command to install Novell Agent Extensions for SLES Services monitoring and management:zypper --non-interactive in -y novell-scx-mp cmpi-pywbem-base

4 At the system terminal of each SLES machine, run the following command to restart the SCX agent:service scx-cimd restart

2.4.3 Manually Installing the Agent on SLES 11 MachinesUse the following steps if deploying agent extensions from Operations Manager was unsuccessful on SLES 11 machines.

1 From the Windows c:\Program Files\Novell Management Packs for System Center Operations Manager folder, copy the novellsles11-mp-addon.iso file to a /tmp folder on every SLES machine where you want to install the Novell Agent Extensions.

2 At the system terminal on each SLES machine, run the following command to add the Novell Agent ISO image to the list of possible install repositories:zypper sa -t YUM iso:/?iso=/tmp/novellsles11-mp-addon.iso nmpa



ber 2009

3 At the system terminal of each SLES machine, run the following commands to install Novell Agent Extensions for SLES Services monitoring and management:zypper --non-interactive in -y novell-scx-mp

cmpi-provider-register -u :scx: -d /usr/share/mof/cmpi-pywbem-base

4 At the system terminal of each SLES machine, run the following command to restart the SCX agent:service scx-cimd restart

2.4.4 Manually Installing the Agent on RHEL 5 MachinesUse the following steps if deploying agent extensions from Operations Manager was unsuccessful on RHEL 5.x machines.

1 At the system terminal on every RHEL machine where you want to install the Novell Agent Extensions, run the following command:mkdir -p /var/opt/Novell/nmpa

2 From the Windows c:\Program Files\Novell Management Packs for System Center Operations Manager folder, copy the novellrhel5-mp-addon.iso file to the /var/opt/Novell/nmpa directory on every RHEL machine where you want to install the Novell Agent Extensions.

3 From the Windows c:\Program Files\Novell Management Packs for System Center Operations Manager folder, copy the novellrhel5-scx-mp.repo file to the /etc/yum.repos.d directory on every RHEL machine where you want to create an install repository.

4 At the system terminal of each RHEL machine, run the following commands to mount the Novell Agent Extensions:mkdir -p /mnt/nmpa

mount -o loop /var/opt/Novell/nmpa/novellrhel5-mp-addon.iso /mnt/nmpa

yum makecache

5 At the system terminal of each RHEL machine, run the following commands to install the Novell Agent Extensions for RHEL Services monitoring and management:yum -y install novell-scx-mp

Installation 21

22 Novell


ber 2009


3novdocx (en) 17 S

eptember 2009

3Understanding Management Pack Operations

The following information is included in this section:

Section 3.1, “Novell General Services Management Pack,” on page 23Section 3.2, “CUPS Service Management Pack,” on page 26Section 3.3, “DHCP Service Management Pack,” on page 30Section 3.4, “DNS Service Management Pack,” on page 35Section 3.5, “Firewall Service Management Pack,” on page 41Section 3.6, “NFS Service Management Pack,” on page 47Section 3.7, “OpenLDAP Service Management Pack,” on page 53Section 3.8, “Samba Service Management Pack,” on page 61Section 3.9, “Linux Agent Extension Management Pack,” on page 68Section 3.10, “Novell Support Advisor Management Pack,” on page 71

3.1 Novell General Services Management PackSection 3.1.1, “Parts of the Novell General Services Management Pack,” on page 23Section 3.1.2, “Appearance of the General Services Management Pack in Operations Manager,” on page 25

3.1.1 Parts of the Novell General Services Management Pack“General Services Management Pack Classes” on page 24“General Services Management Pack Discoveries” on page 24“General Services Management Pack Monitors” on page 25“General Services Management Pack Tasks” on page 25

Understanding Management Pack Operations 23

24 Novell


ber 2009

General Services Management Pack Classes

General Services Management Pack Discoveries

There are no discoveries associated with the Novell General Services Management Pack.

The General Services Management Packs for SLES 10, SLES 11 and RHEL 5 have these discovery attributes.

Class Display Name Description Display Names of Properties

Novell Enterprise Linux Services

The class that lists all of the initd services and their current state on the machine.

Service Description

Install Date

Start Mode

Started

Principal Name

Network Address

Service Name

System Name

Host Operating System

Display Name

Discovery Display Name Description Overrides

Novell SLES 10 Services, Novell SLES 11 Services, or RHEL 5 Services

The discovery finds and lists all of the initd services and their current state on the currently running SLES 10, SLES 11 and RHEL 5 systems.

“Enabled” parameter is set to “True” by default.

“Interval” parameter is set to 600 seconds (10 minutes) by default.



ber 2009

General Services Management Pack Monitors

If you receive an alert from this monitor, check the Diagnostic and Recovery results to see if further action is required.

An unhealthy state (red circle, Critical) indicates that the specified service is set to start automatically but is currently unavailable. A Warning state (yellow triangle) indicates that the service is currently unavailable and must be started manually.

General Services Management Pack Tasks

3.1.2 Appearance of the General Services Management Pack in Operations Manager

“Services Views” on page 26“Health Views” on page 26

Monitor InformationMonitor Operational States

Monitor Alerts Monitor Diagnostics and Recoveries

Display Name: Initd Services Monitor

Description: Monitors the services that are started from the init.d directory.

Overrides: “Enabled” parameter is set to “True” by default.


Running

Optional

Not Running

Display Name:

General Service State Monitor

Generated: When the monitor is in a critical health state

Diagnostic Display Name: Novell Initd Service Diagnostic

Description: Determines if the services inside init.d have started normally.

Run Automatically: Yes

Recovery Display Name: Novell Initd Service Recovery

Description: Restarts services inside init.d.that failed to start properly

Run Automatically: No

Recalc. Monitor State: No

Task Description

Display Name: Stop Initd Service Stops the Initd service.

Display Name: Start Initd Service Starts the Initd service.

Display Name: Restart Initd Service Restarts an Initd service.


26 Novell


ber 2009

Services Views

Health Views

Access to the General Services Tasks is found on the right-hand Actions view of the Operations Manager Console.

Figure 3-1 General Services Tasks in the Operations Manager Console

3.2 CUPS Service Management PackSection 3.2.1, “Parts of the CUPS Service Management Pack,” on page 26Section 3.2.2, “Appearance of the CUPS Service Management Pack in Operations Manager,” on page 29

3.2.1 Parts of the CUPS Service Management Pack“CUPS Service Management Pack Classes” on page 27“CUPS Service Management Pack Discoveries” on page 27

View Name Information Displayed (Column Names)

All Services State

Service Name

System Name


View Name Information Displayed (column Names)

All Services State

Service Name

System Name


SLES Services Alerts Path

Source

Name

Resolution State

Created

Age



ber 2009

“CUPS Service Management Pack Monitors” on page 28“CUPS Service Management Pack Rules” on page 29“CUPS Service Management Pack Tasks” on page 29

CUPS Service Management Pack Classes

CUPS Service Management Pack Discoveries

There are no discoveries associated with the Novell CUPS Services Management Pack.

The SLES 10 CUPS Services Management Pack, the SLES 11 CUPS Services Management Pack, and the RHEL 5 CUPS Services Management Pack have these discovery attributes.

Class Display Name Description Properties

Novell Enterprise Linux CUPS Service

CUPS Service for Enterprise Linux Operating System

Service Name

System Name

Service Description

Install Date

Start Mode

Started


Display Name


CUPS Service Discovery Discovery of the CUPS services currently running on SLES 10, SLES 11 and RHEL 5 systems.




28 Novell


ber 2009

CUPS Service Management Pack Monitors

Monitor Information Monitor Operational States Monitor Alerts Monitor Diagnostics and

Recoveries

Display Name: CUPS Agent Alerts Monitor

Description: Produces alerts if the CUPS agent is running on a Linux machine (CIM provider). If there are problems while running, the monitor generates error messages to indicate the fault in the CIM provider.

The monitor is disabled by default.

Overrides: “Enabled” parameter is set to “False” by default.


CUPSNoAlerts (state is Healthy)

CUPSAlerts (state is Warning)

Display Name:

CUPS Service Error alert

Generated: When the monitor is in a warning health state

Diagnostic Display Name:

Show CUPS Service Agent Alerts

Description: Seeks, gathers, and displays all generated error messages.


Recovery Display Name: Clear CUPS Service Agent Alerts

Description: Clears stored error messages pertaining to this service from provider storage.


Recalc. Monitor State: Yes

Display Name: CUPS Service State Monitor

Description: Monitors the current running state of the CUPS service.



Running (state is Healthy)

Optional (state is Warning)

Not Running (state is Critical)

State icons: You might see the following icons:

Green = running

Yellow = not supposed to start at boot time, not running

Red = supposed to start, not running at boot time

Display Name:

CUPS Service State Monitor



CUPS Service Running Diagnostic

Description: Determines the current running state of the CUPS Service.


Recovery Display Name: CUPS Service Running Recovery

Description: Changes the state to running. Orders CUPS to start so that it begins to run.





ber 2009

CUPS Service Management Pack Rules

CUPS Service Management Pack Tasks

3.2.2 Appearance of the CUPS Service Management Pack in Operations Manager

“CUPS Service Management Pack General Views” on page 29“CUPS Service Management Pack Health Views” on page 30

CUPS Service Management Pack General Views

Rule Description Overrides

Display Name: CUPS Provider alert rule.

This rule generates alerts that relate to error conditions found in the CUPS provider itself.


Task Description

Display Name: Stop CUPS Service Stops the CUPS service.

Display Name: Start CUPS Service Starts the CUPS service.

Display Name: Restart CUPS Service Restarts the CUPS service.


CUPS Service State

Service Name

System Name


CUPS Service Alerts Path

source

Name

Resolution State

Created

Age


30 Novell


ber 2009

CUPS Service Management Pack Health Views

Access to the CUPS Service Tasks is found on the right-hand Actions view of the Operations Manager Console.

Figure 3-2 CUPS Service Tasks in the Operations Manager Console

3.3 DHCP Service Management PackSection 3.3.1, “Parts of the DHCP Service Management Pack,” on page 30Section 3.3.2, “Appearance of the DHCP Service Management Pack in Operations Manager,” on page 34

3.3.1 Parts of the DHCP Service Management Pack“DHCP Service Management Pack Classes” on page 31“DHCP Service Management Pack Discoveries” on page 31“DHCP Service Management Pack Monitors” on page 32“DHCP Service Management Pack Rules” on page 33“DHCP Service Management Pack Tasks” on page 34


CUPS Services State

Service Name

System Name


CUPS Services Alerts Path

Source

Name

Resolution State

Created

Age



ber 2009

DHCP Service Management Pack Classes

DHCP Service Management Pack Discoveries

There are no discoveries associated with the Novell DHCP Service Management Pack.

The SLES 10 DHCP Service Management Pack, the SLES 11 DHCP Service Management Pack, and the RHEL 5 DHCP Service Management Pack have these discovery attributes.


Novell SLES 10 DHCP Service, Novell SLES 11 DHCP Service, Novell RHEL 5 DHCP Service

DHCP service for Novell SLES 10, SLES 11, or RHEL 5 Operating Systems

Domain Name

Service Name

System Name

Service Description

Install Date

Start Mode

Started


Display Name

Novell SLES 10 DHCP Subnet, Novell SLES 11 DHCP Subnet, or Novell RHEL 5 DHCP Subnet

DHCPservice subnet for SLES 10, SLES 11, or RHEL 5 Operating Systems

Subnet

Netmask

Router

Defined IP Addresses

Used IP Addresses

Free IP Addresses

Description

IP Address Ranges

Component ID

Display Name


DHCP Service Discovery Finds all of the DHCP services that are currently running on SLES 10, SLES 11, and RHEL 5 systems.



Novell Linux SLES 10 DHCP Subnet Discovery, SLES 11 DHCP Subnet Discovery, RHEL 5 DHCP Subnet Discovery

Finds all of the subnets for SLES 10, SLES 11, or RHEL 5 systems that are currently running the DHCP service.


“Interval” parameter is set to 601 seconds (10 minutes, 1 second) by default.


32 Novell


ber 2009

DHCP Service Management Pack Monitors


Recoveries

Display Name: DHCP Agent Alerts Monitor

Description: Checks for errors or warnings that have occurred within the DHCP monitoring agent itself. If an error or warning occurs, you can find more information through the Health Explorer diagnostics. When the errors or warnings are resolved. run the recovery task to clear the error messages.



DHCPNoAlerts (state is Healthy)

DHCPAlerts (state is Warning)

Errors or warnings might occur within the DHCP monitoring agent itself due to unforeseen changes to the DHCP service. This monitor allows the administrator to view and resolve any agent error or warning.

Display Name:

DHCP Service Error Alert



Show DHCP Service Agent Alerts



Recovery Display Name: Clear DHCP Service Agent Alerts




Display Name: DHCP Service State Monitor

Description: Checks the status of the DHCP service daemon by running a WSMan query. If you receive an alert from this monitor, check the Diagnostic and Recovery results for further recommended actions.






An unhealthy state indicates that the DHCP service daemon is set to start automatically but is currently unavailable.

A warning state indicates that the service is currently unavailable and must be started manually.

Display Name:

DHCP Service Error Alert



DHCP Service Running Diagnostic



Recovery Display Name: DHCP Service Running Recovery

Description: Restarts the DHCP service.





ber 2009

DHCP Service Management Pack Rules

Display Name: DHCP Used IP Addresses Performance Monitor

Description: This monitor watches the available subnet leases. This is done by running a WSMan query, checking if the number of available leases is less than 10%.



UnderThreshold (state is Healthy)

OverThreshold (state is Critical)

An unhealthy state indicates that the number of available leases for subnets is below 10% of the total number of defined leases.

Display Name:

DHCP Used IP Address Performance Monitor


Diagnostic Display Name: none

Description: none

Run Automatically: none

Recovery Display Name: none

Description: none


Recalc. Monitor State: none


Display Name: Defined subnet IPs

The number of subnetwork IP addresses that are defined on this server.

For more information, see RFC 2131, Dynamic Host Configuration Protocol (http://tools.ietf.org/html/rfc2131).



Display Name: Free subnet IPs

The number of subnetwork IP addresses that are free (not assigned) on this server.




Display Name: Used subnet IPs

The number of subnetwork IP addresses that are used on this machine.




Display Name: DHCP Provider Alerts rule

Rule to monitor the DHCP agent itself. The rule generates alerts that correspond to any agent based errors.



Recoveries


http://tools.ietf.org/html/rfc2131















34 Novell


ber 2009

DHCP Service Management Pack Tasks

3.3.2 Appearance of the DHCP Service Management Pack in Operations Manager

“DHCP Service Management Pack General Views” on page 34“DHCP Service Management Pack Health Views” on page 34

DHCP Service Management Pack General Views

DHCP Service Management Pack Health Views

Task Description

Display Name: Stop DHCP Service Stops the DHCP Service.

Display Name: Start DHCP Service Starts the DHCP Service.

Display Name: Restart DHCP Service

Restarts the DHCP Service.


DHCP Service State

Service Name

System Name


DHCP Service Alerts Path

Source

Name

Resolution State

Created

Age


DHCP Service State

Service Name

System Name


Novell Linux DHCP Subnet State State

Name

Path



ber 2009

Access to the DHCP Service Tasks is found on the right-hand Actions view of the Operations Manager Console.

Figure 3-3 DHCP Service Tasks in the Operations Manager Console

3.4 DNS Service Management PackSection 3.4.1, “Parts of the DNS Service Management Pack,” on page 35Section 3.4.2, “Appearance of the DNS Service Management Pack in Operations Manager,” on page 40

3.4.1 Parts of the DNS Service Management Pack“DNS Service Management Pack Classes” on page 35“DNS Service Management Pack Discoveries” on page 36“DNS Service Management Pack Monitors” on page 36“DNS Service Management Pack Rules” on page 38“DNS Service Management Pack Tasks” on page 40

DNS Service Management Pack Classes


Novell Enterprise Linux DNS Service

DNS service for Enterprise Linux Operating systems

Number of Zones

Recursive Clients Hard Limit

TCP Max Clients

Zone Statistics Enabled

Service Name

System Name

Service Description

Install Date

Start Mode

Started


Display Name

Novell Enterprise Linux DNS Zone

DNS service for Enterprise Linux Operating System

Zone

Description

Component ID

Display Name


36 Novell


ber 2009

DNS Service Management Pack Discoveries

There are no discoveries associated with the Novell DNS Service Management Pack.

The SLES 10 DNS Service Management Pack, the SLES 11 DNS Service Management Pack, and the RHEL 5 DNS Service Management Pack have these discovery attributes.

DNS Service Management Pack Monitors


DNS Service Discovery Finds all of the DNS services that are currently running on SLES 10, SLES 11, and RHEL 5 systems.



DNS Service Zone Discovery Finds all of the zones for SLES 10, SLES 11, and RHEL 5 systems that are currently running the DNS service.



Monitor Information Monitor Operational States Monitor Alerts Monitor Diagnostics and Recoveries

Display Name: DNS Zone Statistics Enabled Monitor

Description:

Checks the enabled state of zone statistics gathering functionality of the DNS service daemon. Enabling zone statistics is an optional function.

Overrides:

“Enabled” parameter is set to “False” by default.


ZoneStatisticsEnabled (state is Healthy)

ZoneStatisticsDisabled (state is Warning)

Any warning state indicates that the DNS service zone statistics gathering functionality is currently in a disabled state.

Display Name:

DNS Service Zone Statistics Enabled Monitor



none

Description: none


Recovery Display Name:

none

Description: none





ber 2009

Display Name: DNS Agent Alerts Monitor

Description:

Checks for errors or warning that have occurred within the DNS monitoring agent itself. If an error or warning occurs, more information can be found through the Health Explorer diagnostics.

Overrides:



DNSNoAlerts (state is Healthy)

DNSAlerts (state is Warning)

Errors or warnings can occur within the DNS monitoring agent itself due to unforeseen changes to the DNS service. This monitor lets the administrator view and resolve any agent error or warning.

Display Name:

DNS Service Error Alert



Show DNS Service Agent Alerts




Clear DNS Service Agent Alerts

Description: Clears the alerts and resets the health state.



Display Name: DNS Service State Monitor

Description:

Checks the status of the DNS service daemon by running a WSMan query to check if the DNS daemon is running.

Overrides:






An unhealthy state indicates that the DNS service daemon is set to start automatically but it is currently unavailable. A warning state indicates that the service is currently unavailable but must be started manually.

Display Name:

DNS Service State Monitor




DNS Service Running Diagnostic

Description: Determines if the DNS service is running.



DNS Service Running Recovery






38 Novell


ber 2009

DNS Service Management Pack Rules


Display Name: Zone Failures For information, see the Microsoft TechNet article: How DNS Works. (http://technet.microsoft.com/en-us/library/cc772774(WS.10).aspx)



Display Name: Zone NXDomain

A zone name that should exist but does not exist.

For information, see the Microsoft TechNet article: How DNS Works. (http://technet.microsoft.com/en-us/library/cc772774(WS.10).aspx)



Display Name: Zone NXRRset A zone resource record set that should exist does not exist.




Display Name: Zone Recursion For information, see the Microsoft TechNet article: How DNS Works. (http://technet.microsoft.com/en-us/library/cc772774(WS.10).aspx)



Display Name: Zone Referral For information, see the Microsoft TechNet article: How DNS Works. (http://technet.microsoft.com/en-us/library/cc772774(WS.10).aspx)



Display Name: Zone Success For information, see the Microsoft TechNet article: How DNS Works. (http://technet.microsoft.com/en-us/library/cc772774(WS.10).aspx)



Display Name: Failed Resolutions




Display Name: NXDomain For information, see the Microsoft TechNet article: How DNS Works. (http://technet.microsoft.com/en-us/library/cc772774(WS.10).aspx)




http://technet.microsoft.com/en-us/library/cc772774(WS.10).aspx









































ber 2009

Display Name: NXRRset For information, see the Microsoft TechNet article: How DNS Works. (http://technet.microsoft.com/en-us/library/cc772774(WS.10).aspx)



Display Name: Provider Alerts Rule



Display Name: Recursion For information, see the Microsoft TechNet article: How DNS Works. (http://technet.microsoft.com/en-us/library/cc772774(WS.10).aspx)



Display Name: SOA Queries in Progress




Display Name: Successful Resolutions




Display Name: # TCP Clients For information, see the Microsoft TechNet article: How DNS Works. (http://technet.microsoft.com/en-us/library/cc772774(WS.10).aspx)



Display Name: Deferred Transfers




Display Name: Running Transfers














































40 Novell


ber 2009

DNS Service Management Pack Tasks

3.4.2 Appearance of the DNS Service Management Pack in Operations Manager

“DNS Service Management Pack General Views” on page 40“DNS Service Management Pack Health Views” on page 41

DNS Service Management Pack General Views

Task Description

Display Name: Disable Zone Statistics If disabled, the server does not collect statistical data on all zones.

Display Name: Enable Zone Statistics if enabled, the server collects statistical data on all zones (unless specifically turned off on a per-zone basis by specifying zone-statistics no in the zone statement). These statistics may be accessed using rndc stats, which dumps them to the file listed in the statistics-file options. This option may be specified in a zone or a 'global' options statement.

Display Name: Restart DNS Service Restarts the DNS Service.

Display Name: Start DNS Service Starts the DNS Service.

Display Name: Stop DNS Service Stops the DNS Service.


DNS Service State

Service Name

Path


DNS Service Alerts Path

Source

Name

Resolution State

Created

Age



ber 2009

DNS Service Management Pack Health Views

Access to the DNS Service Tasks is found on the right-hand Actions view of the Operations Manager Console.

Figure 3-4 DNS Service Tasks in the Operations Manager Console

3.5 Firewall Service Management PackSection 3.5.1, “Parts of the Firewall Service Management Pack,” on page 41Section 3.5.2, “Appearance of the Firewall Service Management Pack in Operations Manager,” on page 46

3.5.1 Parts of the Firewall Service Management Pack“Firewall Service Management Pack Classes” on page 42“Firewall Service Management Pack Discoveries” on page 42“Firewall Service Management Pack Monitors” on page 43“Firewall Service Management Pack Rules” on page 45“Firewall Service Management Pack Tasks” on page 45


DNS Services State

Service Name

System Name


DNS Zones Zone

Path


42 Novell


ber 2009

Firewall Service Management Pack Classes

Firewall Service Management Pack Discoveries

There are no discoveries associated with the Novell Enterprise Linux Firewall Service Management Pack.

The SLES 10 Firewall Service Management Pack and the SLES 11 Firewall Service Management Pack have these discovery attributes.


Novell Enterprise Linux Firewall Chain

Rule Chain for Enterprise Linux Firewall Service

Chain

Policy

References

Chain Tracking Enabled

Component ID

Display Name

Novell Enterprise Linux Firewall Rule

Rule for Enterprise Linux Firewall Service

Chain

Rule

Source IP

Destination IP

Protocol

Target

Input Interface

Output Interface

Opt

Component ID

Display Name

Novell Enterprise Linux Firewall Service

Firewall service for Enterprise Linux Operating Systems

Protocol Tracking Enabled

Service Name

System Name

Service Description

Install Date

Start Mode

Started


Display Name



ber 2009

Firewall Service Management Pack Monitors


Firewall Service Discovery Finds all of the firewall services that are currently running on SLES 10 and SLES 11 systems.



Firewall Chain Discovery Finds all of the firewall chains that are currently running on SLES 10 and SLES 11 systems.



Firewall Rule Discovery Finds all of the firewall rules for SLES 10 and SLES 11 systems that are currently running the firewall service.




Recoveries

Display Name: Firewall Rule Chain Tracking Enabled Monitor

Description: Checks the status of the network traffic tracking rules for each firewall rule chain. this is done by running a WSMan query to invoke a tracking enabled method. This method lists the IPtables rules for a specific chain and determines if a TRAFFIC_ACCT rule has been added to the chain.



ChainTrackingEnabled (state is Healthy)

ChainTrackingDisabled (state is Warning)


A warning state indicates that either the TRAFFIC-ACCT chain and/or the tracking rule is not added to the specific chain.

Display Name:

Firewall Rule Chain Tracking Enabled Monitor



none

Description: none



none

Description: none


Recalc. Monitor State:

none


44 Novell


ber 2009

Display Name: Firewall Agent Alerts Monitor

Description: Produces alerts if the Firewall agent is running on a Linux machine (CIM provider). If there are problems while running, the monitor generates error messages to indicate the fault in the CIM provider.



FirewallNoAlerts (state is Healthy)

FirewallAlerts (state is Warning)

Display Name:

Firewall Service Zone Statistics Enabled Monitor



none

Description: none



none

Description: none



none

Display Name: Firewall Service State Monitor

Description: Checks the status of the Firewall Service by running a WSMan query to check if the service has been started.






An unhealthy stat indicates that the Firewall Service daemon is set to start automatically, but it is currently unavailable. A warning state indicates that the service is currently unavailable and must be started manually.

Display Name:

Firewall Service State Monitor


If you receive an alert from this monitor, check the Diagnostic and Recovery rules to see if further action is required.


Firewall Service Running Diagnostic

Description: Determines if the Firewall Service is running.



Firewall Service Running Recovery



You can attempt to restarted the Firewall service manually by running the service SuSEfirewall2.start command.



Recoveries



ber 2009

Firewall Service Management Pack Rules

Firewall Service Management Pack Tasks


Display Name: Packet Count for Rule Chain

Packet count for firewall chain.



Display Name: All Rules Packet Count for Monitored Chains

Number of combined packets for all rules within a chain.



Display Name: ICMP Rules Packet Count for Monitored Chains

Number of ICMP rules packets for firewall chain.



Display Name: Firewall Provider Alert Rule

Monitors the Firewall agent itself and generates alerts that correspond to any agent based errors.


Display Name: TCP Rules Packet Count for Monitored Chains

Number of TCP packets for monitored chain.



Display Name: UDP Rules Packet Count for Monitored Chains

Number of UDP rules packets for monitored chains.



Task Description

Display Name: Disable Chain Tracking

Disable the firewall chain tracking.

Display Name: Enable Chain Tracking

Enable the firewall chain tracking.

Display Name: Enable Firewall Monitoring Per Protocol

Enable the firewall per protocol tracking.

Display Name: Disable Firewall Monitoring Per Protocol

Disable the firewall per protocol tracking.

Display Name: Restart Firewall Service

Restarts the firewall service.

Display Name: Start Firewall Service Starts the firewall service.


46 Novell


ber 2009

3.5.2 Appearance of the Firewall Service Management Pack in Operations Manager

“Firewall Service Management Pack General Views” on page 46“Firewall Service Management Pack Health Views” on page 46

Firewall Service Management Pack General Views

Firewall Service Management Pack Health Views

Display Name: Stop Firewall Service Stops the firewall service.


Firewall Service State

Service Name


System Name


Firewall Service Alerts Path

Source

Name

Resolution State

Created

Age


Firewall Service State

Service Name


System Name


Firewall Rule Chains Chain

Path

Policy

Chain Tracking Enabled

Task Description



ber 2009

Access to the Firewall Service Tasks is found on the right-hand Actions view of the Operations Manager Console.

Figure 3-5 Firewall Service Tasks in the Operations Manager Console

3.6 NFS Service Management PackSection 3.6.1, “Parts of the NFS Service Management Pack,” on page 47Section 3.6.2, “Appearance of the NFS Service Management Pack in Operations Manager,” on page 52

3.6.1 Parts of the NFS Service Management Pack“NFS Service Management Pack Classes” on page 47“NFS Service Management Pack Discoveries” on page 48“NFS Service Management Pack Monitors” on page 49“NFS Service Management Pack Rules” on page 50“NFS Service Management Pack Tasks” on page 51

NFS Service Management Pack Classes

Firewall Rules Display Name

Target

Path

Rule


Novell Enterprise Linux NFS Share

NFS Share for Enterprise Linux Operating System

Allowed Clients

Description

Element Name

Sharing Directory

Options

Current Clients

Component ID

Display Name



48 Novell


ber 2009

NFS Service Management Pack Discoveries

There are no discoveries associated with the Novell Enterprise Linux NFS Service Management Pack.

The SLES 10 NFS Service Management Pack, the SLES 11 NFS Service Management Pack, and the RHEL 5 NFS Service Management Pack have these discovery attributes.

Novell Enterprise Linux NFS Service

NFS service for Enterprise Linux Operating System

Service Name

System Name

Service Description

Install Date

Start Mode

Started


Display Name


NFS Service Discovery NFS Service discovery finds all of the NFS services that are currently running on SLES 10, SLES 11, and RHEL 5 systems.



NFS Share Discovery NFS Share discovery finds all of the shares for SLES 10, SLESS 11, and RHEL 5 systems that are currently running the NFS service.






ber 2009

NFS Service Management Pack Monitors


Recoveries

Display Name: NFS Agent Alerts Monitor

Description: Produces alerts if the NFS agent is running on a Linux machine (CIM provider). If there are problems while running, the monitor generates error messages to indicate the fault in the CIM provider.



NFSNoAlerts (state is Healthy)

NFSAlerts (state is Warning)

If this monitor is enabled, we recommend that you disable the agent extension rule.

Display Name: NFS Service Error Alert


Errors or warnings might occur within the NFS monitoring agent itself due to unforeseen changes to the NFS service.

Diagnostic Display Name: Show NFS Service Agent Alerts




Clear NFS Service Agent Alerts




Yes

Display Name: NFS Service State Monitor

Description: Checks the status of the NFS service by running a WSMan query that determines whether the NFS daemon is running.






An unhealthy state indicates that the NFS service daemon is set to start automatically but is currently unavailable. A warning state indicates that the service is currently unavailable and must be started manually.

Display Name: NFS Service State Monitor


Diagnostic Display Name: none

Description: none



none

Description: none



none


50 Novell


ber 2009

NFS Service Management Pack Rules


Display Name: All NFS Network Packets

Count of all NFS Network packets.

For information about NFS, see the NFS sourceforge article (http://nfs.sourceforge.net/).


“Interval” parameter is set to 600 seconds (10 minutes) by default).

Display Name: NFS Access For information about NFS, see the NFS sourceforge article (http://nfs.sourceforge.net/).



Display Name: NFS Create For information about NFS, see the NFS sourceforge article (http://nfs.sourceforge.net/).



Display Name: NFS Make Directory




Display Name: NFS Read For information about NFS, see the NFS sourceforge article (http://nfs.sourceforge.net/).



Display Name: NFS Remove For information about NFS, see the NFS sourceforge article (http://nfs.sourceforge.net/).



Display Name: NFS Rename For information about NFS, see the NFS sourceforge article (http://nfs.sourceforge.net/).



Display Name: NFS Remove Directory





http://nfs.sourceforge.net/









ber 2009

NFS Service Management Pack Tasks

Display Name: NFS Write For information about NFS, see the NFS sourceforge article (http://nfs.sourceforge.net/).



Display Name: Number of NFS Exports




Display Name: Number of NFS Client Mounts




Display Name: Number of NFS Users




Display Name: NFS Provider Alert Rule



Display Name: NFS RPC Bad Authentication

For information about NFS and RPC, see the NFS sourceforge article (http://nfs.sourceforge.net/).



Display Name: NFS RPC Bad Calls




Display Name: All NFS RPC Calls




Task Description

Display Name: Restart NFS Service Restarts the NFS Service on the SLES server.














52 Novell


ber 2009

3.6.2 Appearance of the NFS Service Management Pack in Operations Manager

“NFS Service Management Pack General Views” on page 52“NFS Service Management Pack Health Views” on page 52

NFS Service Management Pack General Views

NFS Service Management Pack Health Views

Access to the NFS Service Tasks is found on the right-hand Actions view of the Operations Manager Console.

Display Name: Start NFS Service Starts the NFS Service on the SLES server.

Display Name: Stop NFS Service Stops the NFS Service on the SLES server.


NFS Service State

Service Name

System Name


NFS Alert View Path

Source

Name

Resolution State

Created

Age


NFS Service State

Service Name

System Name


NFS Share Display Name

Path

Task Description



ber 2009

Figure 3-6 NFS Service Tasks in the Operations Manager Console

3.7 OpenLDAP Service Management PackSection 3.7.1, “Parts of the OpenLDAP Service Management Pack,” on page 53Section 3.7.2, “Appearance of the OpenLDAP Service Management Pack in Operations Manager,” on page 60

3.7.1 Parts of the OpenLDAP Service Management Pack“OpenLDAP Classes” on page 53“OpenLDAP Service Discoveries” on page 54“OpenLDAP Service Monitors” on page 55“OpenLDAP Service Rules” on page 57“OpenLDAP Service Tasks” on page 59

OpenLDAP Classes


OpenLDAP Connection OpenLDAP connection User Rdn

Local Address

Peer Address

Peer Domain

Listener

Caption

Component ID

Display Name


54 Novell


ber 2009

OpenLDAP Service Discoveries

There are no discoveries associated with the Novell Enterprise Linux OpenLDAP Service Management Pack.

The SLES 10 OpenLDAP Service Management Pack, the SLES 11 OpenLDAP Service Management Pack and the RHEL 5 OpenLDAP Service Management Pack have these discovery attributes.

Novell Enterprise Linux OpenLDAP Service

OpenLDAP service for Enterprise Linux Operating Systems

Databases

Supported Backends

Monitor Status

Service Name

System Name

Service Description

Install Date

Start Mode

Started


Display Name


OpenLDAP Service Discovery Finds all of the OpenLDAP services that are currently running on SLES 10, SLES 11, and RHEL 5 systems.



OpenLDAP Service Connection Discovery

Finds all of the connections for SLES 10, SLES 11, and RHEL 5 systems that are currently running the OpenLDAP service.






ber 2009

OpenLDAP Service Monitors


Recoveries

Display Name:

OpenLDAP Monitoring Service

Description:

Checks the status of the OpenLDAP internal monitoring functionality.

Overrides:



OpenLDAPMonitorEnabled (state is Healthy)

OpenLDAPMonitorDisabled (state is Warning)

An unhealthy state indicates that the OpenLDAP internal monitoring functionality has not been enabled. This functionality is optional.

Display Name:

OpenLDAP Monitoring Service Monitor

Generated:

When the monitor is in a warning health state

Diagnostic Display Name: Open LDAP Monitor Status Diagnostic

Description: Determines whether the OpenLDAP internal monitoring functionality has been enabled.


Recovery Display Name: Enable OpenLDAP Monitoring Service

Description: Enables the OpenLDAP Monitoring Service




56 Novell


ber 2009

Display Name:

OpenLDAP Agent Alerts Monitor

Description:

Produces alerts if the OpenLDAP agent is running on a Linux machine (CIM provider). If there are problems while running, the monitor generates error messages to indicate the fault in the CIM provider.

Overrides:



OpenLDAPNoAlerts (state is Healthy)

OpenLDAPAlerts (state is Warning)

Display Name:

OpenLDAP Service Error Alert

Generated:


This monitor is handled by a rule that produces informational alerts rather than changing the health state of the service.

If the monitor is enabled, we recommend that you disable the agent extension rule.

Diagnostic Display Name: Show OpenLDAP Service Agent Alerts



Recovery Display Name: Clear OpenLDAP Service Agent Alerts





Recoveries



ber 2009

OpenLDAP Service Rules

Display Name:

OpenLDAP Service State Monitor

Description:

Checks the status of the OpenLDAP service by running a WSMan query that checks if the OpenLDAP daemon is running.

Overrides:






An unhealthy state indicates that the OpenLDAP service daemon is set to start automatically, but is currently unavailable. A warning state indicates that the service is currently unavailable and must be started manually.

Display Name:

OpenLDAP Service State Monitor

Generated:

When the monitor is in a critical health state

If your receive an alert from this monitor, check the Diagnostic and Recovery results to see if further action is required.


OpenLDAP Service Running Diagnostic

Description: Checks the running state of the OpenLDAP service.



OpenLDAP Service Running Recovery.

Description: Clears stored error messages pertaining to this service.




Display Name: Abandon Operations

For information, see the YoLinux LDAP Tutorial (http://www.yolinux.com/TUTORIALS/LinuxTutorialLDAP.html).



Display Name: Add Operations




Display Name: Backload Threads

The number of unfinished tasks submitted to the thread pool.





Recoveries


http://www.yolinux.com/TUTORIALS/LinuxTutorialLDAP.html


















58 Novell


ber 2009

Display Name: Bind Operations




Display Name: Compare Operations




Display Name: Current Connections




Display Name: Delete Operations




Display Name: Total Entries




Display Name: Extended Operations




Display Name: IO Bytes For information, see the YoLinux LDAP Tutorial (http://www.yolinux.com/TUTORIALS/LinuxTutorialLDAP.html).



Display Name: Modify Operations




Display Name: ModRdn Operations




Display Name: OpenLDAP Provider Alert Rule

Generates alerts that relate to error conditions found in the OpenLDAP provider itself.



























































ber 2009

OpenLDAP Service Tasks

Display Name: Read Waiters




Display Name: Referrals For information, see the YoLinux LDAP Tutorial (http://www.yolinux.com/TUTORIALS/LinuxTutorialLDAP.html).



Display Name: Search Operations




Display Name: Total Operations




Display Name: Unbind Operations




Display Name: Write Waiters




Task Description

Display Name: Enable OpenLDAP Monitoring

Adds the statement database monitor to the slapd.conf file. After invoking this task, the OpenLDAP server requires a restart.

Display Name: Restart OpenLDAP Service

Restarts the OpenLDAP Service.

Display Name: Start OpenLDAP Service

Starts the OpenLDAP Service.

Display Name: Stop OpenLDAP Service

Stops the OpenLDAP Service.







































60 Novell


ber 2009

3.7.2 Appearance of the OpenLDAP Service Management Pack in Operations Manager

“OpenLDAP Service General Views” on page 60“OpenLDAP Service Health Views” on page 60

OpenLDAP Service General Views

OpenLDAP Service Health Views

Access to the OpenLDAP Service Tasks is found on the right-hand Actions view of the Operations Manager Console.

Figure 3-7 OpenLDAP Service Tasks in the Operations Manager Console


OpenLDAP Service State

Service Name

Monitor Status

System Name


OpenLDAP Service Alerts Path

Source

Name

Resolution State

Created

Age


OpenLDAP Service State

Service Name

Monitor Status

System Name


OpenLDAP Connections Display Name

Path



ber 2009

3.8 Samba Service Management PackSection 3.8.1, “Parts of the Samba Service Management Pack,” on page 61Section 3.8.2, “Appearance of the Samba Service Management Pack in Operations Manager,” on page 66

3.8.1 Parts of the Samba Service Management Pack“Samba Classes” on page 61“Samba Service Discoveries” on page 62“Samba Service Monitors” on page 63“Samba Service Rules” on page 66“Samba Service Tasks” on page 66

Samba Classes


Samba Connection Samba connection User Name

Group

Client

IP Address

Component ID

Display Name

Samba Session Samba session Client

Share Name

Time Stamp

Component ID

Display Name

Samba Share Samba share Browseable

Read Only

Share Name

Caption

Component ID

Display Name


62 Novell


ber 2009

Samba Service Discoveries

There are no discoveries associated with the Novell Enterprise Linux Samba Service Management Pack.

The SLES 10 Samba Service Management Pack, the SLES 11 Samba Service Management Pack, and the RHEL 5 Samba Service Management Pack have these discovery attributes.

Samba User Samba user NT User Name

Domain

Workstations

Unix User Name

Home Directory Drive

Home Directory

Full Name

Logon Time

Component ID

Display Name

Novell Enterprise Linux Samba Service

Samba service for Enterprise Linux Operating Systems

Has Homes MetaShare

Has Printers MetaShare

Print Service

Workgroup

Service Name

System Name

Service Description

Install Date

Start Mode

Started


Display Name


Samba Service Discovery Finds all of the Samba services that are currently running on SLES 10, SLES 11, and RHEL 5 systems.



Samba Service Connection Discovery Finds all of the connections for SLES 10, SLES 11, and RHEL 5 systems that are currently running the Samba service.






ber 2009

Samba Service Monitors

Samba Service Session Discovery Finds all of the sessions for SLES 10, SLES 11, and RHEL 5 systems that are currently running the Samba service.



Samba Service Share Discovery Finds all of the shares for SLES 10, SLES 11 and RHEL 5 systems that are currently running the Samba service.



Samba Service User Discovery Finds all of the users for SLES 10, SLES 11, and RHEL 5 systems that are currently running the Samba service.




Display Name:

Samba Share State

Description:

Watches the availability of the Samba share by running a WSMan query to check if the share is available.

Overrides:


“interval” parameter is set to 300 seconds (5 minutes) by default.

Enabled (state is Healthy)

Disabled (state is Critical)

Display Name:

Samba Share State

Generated:


If you receive an alert from this monitor, check the Diagnostic and Recovery results to determine if further action is required.

Diagnostic Display Name: None

Description: none



Description: none





64 Novell


ber 2009

Display Name:

Samba User Status Monitor

Description:

Watches the enabled/disabled state of the Samba users by running a WSMan query to check the current state of the user object.

Overrides:



Enabled (state is Healthy)

Disabled (state is Critical)

An unhealthy state indicates that the Samba user object has been disabled.

Display Name:

Samba User Status Monitor

Generated:




Description: none



Description: none



Display Name:

Samba User Account Locked Monitor

Description:

Watches the locked state of the Samba users by running a WSMan query to check the current state of the user object.

Overrides:



OK (state is Healthy)

Locked Out (state is Critical)

An unhealthy state indicates that the Samba user object has been locked out due to multiple authentication failures.

Display Name:

Samba User Account Locked Monitor

Generated:




Description: none



Description: none






ber 2009

Display Name:

Samba Agent Alerts Monitor

Description:

Produces alerts if the Samba agent is running on a Linux machine (CIM provider). If there are problems while running, the monitor generates error messages to indicate the fault in the CIM provider.

Overrides:



SambaNoAlerts (state is Healthy)

SambaAlerts (state is Warning)

This monitor is handled by a rule that produces informational alerts rather than changing the health state of the server.

If this monitor is enabled, we recommend that you disable the agent extension rule.

Display Name:

Samba Service Error Alert

Generated:


Diagnostic Display Name: Show Samba Service Agent Alerts



Recovery Display Name: Clear Samba Service Agent Alerts




Display Name:

Samba Service State Monitor

Description:

Checks the status of the Samba service daemons by running a WSMan query to determine if the Samba daemons are running.

Overrides:






An unhealthy state indicates that the Samba service daemon is set to start automatically but is currently unavailable

A warning state indicates that the service is currently unavailable and must be started manually.

Display Name:

Samba Service State Monitor

Generated:




Samba Service Running Diagnostic

Description: Determines if the Samba Service is running.


Recovery Display Name: Samba Service Running Recover.

Description: Clears stored error messages from provider storage pertaining to this service.





66 Novell


ber 2009

Samba Service Rules

Samba Service Tasks

3.8.2 Appearance of the Samba Service Management Pack in Operations Manager

“Samba Service General Views” on page 67“Samba Service Health Views” on page 67


Display Name: Number of Samba Mounts

Number of Samba mounts. “Enabled” parameter is set to “True” by default.


Display Name: Number of Samba Shares

Number of Samba shares. “Enabled” parameter is set to “True” by default.


Display Name: Number of Samba Users

Number of Samba users. “Enabled” parameter is set to “True” by default.


Display Name: Samba Provider Alert Rule

Generates alerts that relate to error conditions found in the Samba provider itself.


Task Description

Display Name: Disable Samba User Disables a Samba user.

Display Name: Enable Samba User Enables a Samba user.

Display Name: Restart Samba Services Restarts the Samba (SMB and NMB) service.

Display Name: Start Samba Services Starts the Samba (SMB and NMB) service.

Display Name: Stop Samba Services Stops the Samba (SMB and NMB) service



ber 2009

Samba Service General Views

Samba Service Health Views

Access to the Samba Service Tasks is found on the right-hand Actions view of the Operations Manager Console.

Figure 3-8 Samba Service Tasks in the Operations Manager Console


Samba Service State

Service Name

System Name


Samba Service Alerts Path

Source

Name

Resolution State

Created

Age


Samba Service State

Service Name

System Name


Samba Shares State

Name

Path

Samba Users NT User Name

Unix User Name

Domain

Home Directory


68 Novell


ber 2009

3.9 Linux Agent Extension Management PackSection 3.9.1, “Parts of the Linux Agent Extension Management Pack,” on page 68Section 3.9.2, “Appearance of the Linux Agent Extension Status Management Pack in Operations Manager,” on page 70

3.9.1 Parts of the Linux Agent Extension Management Pack“Deploy Linux Agent Extension Classes” on page 68“Deploy Linux Agent Extension Discoveries” on page 68“Deploy Linux Agent Extension Monitors” on page 69“Deploy Linux Agent Extension Diagnostics and Associated Recoveries” on page 69“Deploy Linux Agent Extension Rules” on page 70“Deploy Linux Agent Extension Tasks” on page 70

Deploy Linux Agent Extension Classes

Deploy Linux Agent Extension Discoveries


Novell Agent Extensions for SLES 10, SLES 11, and RHEL 5 computer system

Discovered computer system for Novell Agent Extensions for SLES 10, SLES 11, and RHEL 5

Principal Name

IP Address

Network Name

SSH Port

Display Name


Novell Agent Extensions for SLES 10, SLES 11 and RHEL 5 Discovery

Finds all of the SLES 10, SLES 11, and RHEL 5 systems that are capable of installing the Novell management pack agents.





ber 2009

Deploy Linux Agent Extension Monitors

Deploy Linux Agent Extension Diagnostics and Associated Recoveries

Monitor Information Monitor Operational States Monitor Alerts

Display Name: Install Agent Monitor

Description: Verifies the installation of the Novell Agent Extensions service providers for SLES 10, SLES 11, and RHEL 5 by running WSMan query to determine if the OMC providers are loaded and accessible through the CIMOM.

Overrides: “Enabled” override value is set to “True” by default.

“Interval” parameter is set to 300 seconds (5 minutes).

StatusOK (state is Healthy)

Statusfailed (state is Critical)

An unhealthy state indicates that the Novell Agent Extensions service providers for SLES 10, SLES 11, and RHEL 5 are currently unavailable to System Center Operations Manager.

During the installation of the Novell service providers for SLES 10, SLES 11, or RHEL 5, several files are copied from the Operations Manager server to the Linux computer. When the files are copied, and installation repository is mounted in the form of an ISO image and the components are installed from the repository.

An unhealthy state for this monitor could mean that the files were not correctly copied from the Operations Manager server, that the installation repository was incorrectly mounted, or that the OpenWSMan configuration was not established. One or more of these issues could result in the unavailability of the Novell service providers for SLES 10, SLES 11, and RHEL 5.

Display Name: Install Agent State Monitor


If you receive an alert from this monitor, check the Diagnostic and Recover results to determine if further action is required.

Diagnostic Task Recovery Task

Display Name: Check installation of Novell service providers for SLES 10, SLES 11, and RHEL 5.

Description: Verify that the Novell service providers for SLES 10, SLES 11, and RHEL 5 and supporting RPMs have been installed


Recovery Display Name: Install the Novell service providers for SLES 10,SLES 11, and RHEL 5

Description: Install the set of Novell service providers# for SLES 10, SLES 11, and RHEL 5 and supporting RPMs




70 Novell


ber 2009

Deploy Linux Agent Extension Rules

There are no Deploy Agent Extension rules for SLES 10, SLES 11, or RHEL 5 in the System Center Operations Manager console.

Deploy Linux Agent Extension Tasks

3.9.2 Appearance of the Linux Agent Extension Status Management Pack in Operations Manager

“SLES 10, SLES 11, or RHEL 5 Agent Extension Status General Views” on page 71

Display Name: Check zypper iso file

Description: Check that the appropriate .iso file was successfully copied to the correct location.


Recovery Display Name: Copy the zypper ISO image file

Description: Copy the zypper ISO image file to the Novell SLES 10, SLES 11, or RHEL 5 computer. This file will be mounted as a zypper installation repository.



Display Name: Check zypper repository source

Description: Check that the .iso file was successfully added as a repository source.


Recovery Display Name: Mount the zypper ISO installation repository

Description: Mount the ISO image file as a zypper installation repository.



Recovery Display Name: Restart SCX service

Description: Restart the SCX service. This should be done after the Novell agent extensions have been installed.



Task Description

Display Name: Install Novell Agent Extensions for SLES 10 (or SLES 11 or RHEL 5)

Install the Novell Agent Extensions for SLES 10, SLES 11, or RHEL 5 to the target server.

Display Name: Uninstall Novell Agent Extensions for SLES 10 (or SLES 11 or RHEL 5)

Uninstall the set of Novell Agent Extensions for SLES 10, SLES 11, or RHEL 5.

Diagnostic Task Recovery Task



ber 2009

SLES 10, SLES 11, or RHEL 5 Agent Extension Status General Views

Access to the Novell Extension for SLES 10 Agent Tasks (also SLES 11 and RHEL 5) is found on the right-hand Actions view of the Operations Manager Console.

Figure 3-9 Novell Extension for SLES 10 Agent Tasks in the Operations Manager Console

3.10 Novell Support Advisor Management PackThe Novell Support Advisor (NSA) is an automated self-help tool used to support and diagnose SUSE Linux Enterprise Server and other products.

This tool provides customers with a streamlined way to perform both proactive and reactive system diagnostic tasks typically provided by Novell Technical Services, but using local, secure, and automated methods.

The NSA is installed with the other SUSE Linux Enterprise Management Packs included in this product (SLES 10 and SLES 11). When installed as a separate product, the NSA has its own console. In this product however, NSA functions are integrated to be displayed in the System Center Operations Manager.

For more information about the Novell Support Advisor, see the Novell Support Advisor (http://support.novell.com/advisor/) page on the Novell Web site.

Section 3.10.1, “Parts of the Novell Support Advisor Management Pack,” on page 72Section 3.10.2, “Appearance of the Novell Support Advisor Management Pack in Operations Manager,” on page 94


Novell Extensions for SLES 10 Computer System Status

Novell Extensions for SLES 11 Computer System Status

Novell Extensions for RHEL 5 Computer System Status

State

Name

Path

Novell Extensions for SLES 10 Alerts

Novell Extensions for SLES 11 Alerts

Novell Extensions for RHEL 5 Alerts

Path

Source

Name

Resolution State

Created

Age


http://support.novell.com/advisor/

72 Novell


ber 2009

3.10.1 Parts of the Novell Support Advisor Management Pack“Novell Support Advisor Classes” on page 72“Novell Support Advisor Discoveries” on page 81“Novell Support Advisor Monitors” on page 84“Novell Support Advisor Rules” on page 93“Novell Support Advisor Tasks” on page 94

Novell Support Advisor Classes


NSA Analysis Results Analysis results for each of the collection patterns for the monitored service.

Key

Pattern

Display Status

Overall Status

Overall Info

Product

TID

Video

Script

Security

Patch

Misc

Bug

CoolSolution

Architecture

Additional Info

Service Category

Display Name



ber 2009

NSA Analysis Results for Clustering

NSA Analysis Results for Clustering

Element Info

Key

Pattern

Display Status

Overall Status

Overall Info

Product

TID

Video

Script

Security

Patch

Misc

Bug

CoolSolution

Architecture

Additional Info

Service Category

Display Name



74 Novell


ber 2009

NSA Analysis Results for Connectivity

NSA Analysis Results for Connectivity

Driver

Package Install

Package Verification

Service Daemon

Service Status

Key

Pattern

Display Status

Overall Status

Overall Info

Product

TID

Video

Script

Security

Patch

Misc

Bug

CoolSolution

Architecture

Additional Info

Service Category

Display Name




ber 2009

NSA Analysis Results for eDirectory

NSA Analysis Results for eDirectory

eDirectory Pattern

Key

Pattern

Display Status

Overall Status

Overall Info

Product

TID

Video

Script

Security

Patch

Misc

Bug

CoolSolution

Architecture

Additional Info

Service Category

Display Name

NSA Analysis Results for Migration NSA Analysis Results for Migration Element Info

Key

Pattern

Display Status

Overall Status

Overall Info

Product

TID

Video

Script

Security

Patch

Misc

Bug

CoolSolution

Architecture

Additional Info

Service Category

Display Name



76 Novell


ber 2009

NSA Analysis Results for OES NSA Analysis Results for OES Hardware

Key

Pattern

Display Status

Overall Status

Overall Info

Product

TID

Video

Script

Security

Patch

Misc

Bug

CoolSolution

Architecture

Additional Info

Service Category

Display Name

NSA Analysis Results for Other Elements

NSA Analysis Results for Other Elements

Key

Pattern

Display Status

Overall Status

Overall Info

Product

TID

Video

Script

Security

Patch

Misc

Bug

CoolSolution

Architecture

Additional Info

Service Category

Display Name




ber 2009

NSA Analysis Results for Print NSA Analysis Results for Print Package Install


Service Daemon

Service Status

Key

Pattern

Display Status

Overall Status

Overall Info

Product

TID

Video

Script

Security

Patch

Misc

Bug

CoolSolution

Architecture

Additional Info

Service Category

Display Name



78 Novell


ber 2009

NSA Analysis Results for Security NSA Analysis Results for Security CVE

RPM

Scope

Key

Pattern

Display Status

Overall Status

Overall Info

Product

TID

Video

Script

Security

Patch

Misc

Bug

CoolSolution

Architecture

Additional Info

Service Category

Display Name




ber 2009

NSA Analysis Results for SLE NSA Analysis Results for SLE CPU CS

CPU INT

CPUP U

Disk 1

Disk 2

Fsaio

Fsvm

Load

Memory

Missing

Overlap

Package Install


Procd

Procz

Scope

Service Daemon

Service Status

Skipped

State

Swap

Taint

Key

Pattern

Display Status

Overall Status

Overall Info

Product

TID

Video

Script

Security

Patch

Misc

Bug

CoolSolution

Architecture

Additional Info

Service Category

Display Name



80 Novell


ber 2009

NSA Analysis Results for Update NSA Analysis Results for Update Beta

Match

Sub Info

Update

Key

Pattern

Display Status

Overall Status

Overall Info

Product

TID

Video

Script

Security

Patch

Misc

Bug

CoolSolution

Architecture

Additional Info

Service Category

Display Name




ber 2009

Novell Support Advisor Discoveries

NSA Analysis Results for Virtualization

NSA Analysis Results for Virtualization

Hypervisor

Package Install

Xen

Key

Pattern

Display Status

Overall Status

Overall Info

Product

TID

Video

Script

Security

Patch

Misc

Bug

CoolSolution

Architecture

Additional Info

Service Category

Display Name

NSA Service NSA Service Service Name

System Name

Service Description


NSA Agent Last Run

NSA Agent Version

NSA Patterns Last Update

NSA Patterns Version

Display Name


NSA Service Discovery Discovers the Novell Support Advisor service on al systems that are capable of running it.


“Interval” parameter is set to 3600 seconds (1 hour) by default.



82 Novell


ber 2009

Clustering Analysis Results Discovery

Discovers all of the analysis results that correspond to the clustering patterns. The clustering specific elements might contain additional properties that are not included in the corresponding overall pattern analysis element.


“Interval” parameter is set to 3610 seconds (1 hour, 10 seconds) by default.

Connectivity Analysis Results Discovery

Discovers all of the analysis results that correspond to the connectivity patterns. The connectivity specific elements might contain additional properties that are not included in the corresponding overall pattern analysis element.



Overall Analysis Results Discovery Discovers all of the pattern analysis results that are produced by the Novell Support Advisor utilities.



eDirectory Analysis Results Discovery

Discovers all of the analysis results that correspond to the migration patterns. The migration specific elements might contain additional properties that are not included in the corresponding overall pattern analysis element.



OS Migration Analysis Results Discovery

Discovers all of the analysis results that correspond to the eDirectory patterns. The eDirectory specific elements might contain additional properties that are not included in the corresponding overall pattern analysis element.



OES Analysis Results Discovery Discovers all of the analysis results that correspond to the OES patterns. The OES specific elements might contain additional properties that are not included in the corresponding overall pattern analysis element.



Other Pattern Analysis Results Discovery

Discovers all of the analysis results that correspond to other patterns. The other specific elements might contain additional properties that are not included in the corresponding overall pattern analysis element.






ber 2009

Print Analysis Results Discovery Discovers all of the analysis results that correspond to the print patterns. The print specific elements might contain additional properties that are not included in the corresponding overall pattern analysis element.



Security Analysis Results Discovery

Discovers all of the analysis results that correspond to the security patterns. The security specific elements might contain additional properties that are not included in the corresponding overall pattern analysis element.



SLE Analysis Results Discovery Discovers all of the analysis results that correspond to the SLE patterns. The SLE specific elements might contain additional properties that are not included in the corresponding overall pattern analysis element.



Update Analysis Results Discovery Discovers all of the analysis results that correspond to the update patterns. The update specific elements might contain additional properties that are not included in the corresponding overall pattern analysis element.



Virtualization Analysis Results Discovery

Discovers all of the analysis results that correspond to the virtualization patterns. The virtualization specific elements might contain additional properties that are not included in the corresponding overall pattern analysis element.





84 Novell


ber 2009

Novell Support Advisor Monitors

Monitor Information Monitor Operational States Monitor AlertsMonitor Diagnostics and Recoveries

Display Name: NSA Analysis Results Monitor

Rolls up to Class ID:

Novell.Linux.NSA.AnalysisResult

Description: Determines the current health state of the various areas of a system that are checked by the Novell Support Advisor patterns. Each NSA pattern checks for specific conditions within the system and then returns a health status.




Status Warn (state is Warning)

Status Failed (state is Critical)

A warning state indicates that there is a potential problem with either the system itself or with a service running on the system. Some corrective action might be required, but is not necessary yet.

An unhealthy state indicates that corrective action is required. The results of the analysis should provide the administrator with more guidance regarding the action to take.

Display Name:

NSA Monitored Alerts



none

Description:

none

Run Automatically:

none


none

Description:

none

Run Automatically:

none




ber 2009

Display Name: NSA Analysis Results Monitor (clustering)


Novell.Linux.NSA.AnalysisResults.Clustering









Display Name:




none

Description:

none

Run Automatically:

none


none

Description:

none

Run Automatically:

none


Display Name: NSA Analysis Results Monitor (connectivity)


Novell.Linux.NSA.AnalysisResults.Connectivity









Display Name:




none

Description:

none

Run Automatically:

none


none

Description:

none

Run Automatically:

none




86 Novell


ber 2009

Display Name: NSA Analysis Results Monitor (eDirectory)


Novell.Linux.NSA.AnalysisResults.eDirectory









Display Name:




none

Description:

none

Run Automatically:

none


none

Description:

none

Run Automatically:

none


Display Name: NSA Analysis Results Monitor (migration)


Novell.Linux.NSA.AnalysisResults.Migration









Display Name:




none

Description:

none

Run Automatically:

none


none

Description:

none

Run Automatically:

none





ber 2009

Display Name: NSA Analysis Results Monitor (OES)


Novell.Linux.NSA.AnalysisResults.OES









Display Name:




none

Description:

none

Run Automatically:

none


none

Description:

none

Run Automatically:

none


Display Name: NSA Analysis Results Monitor (other)


Novell.Linux.NSA.AnalysisResults.Other









Display Name:




none

Description:

none

Run Automatically:

none


none

Description:

none

Run Automatically:

none




88 Novell


ber 2009

Display Name: NSA Analysis Results Monitor (print)


Novell.Linux.NSA.AnalysisResults.Print









Display Name:




none

Description:

none

Run Automatically:

none


none

Description:

none

Run Automatically:

none


Display Name: NSA Analysis Results Monitor (security)


Novell.Linux.NSA.AnalysisResults.Security









Display Name:




none

Description:

none

Run Automatically:

none


none

Description:

none

Run Automatically:

none





ber 2009

Display Name: NSA Analysis Results Monitor (SLE)


Novell.Linux.NSA.AnalysisResults.SLE









Display Name:




none

Description:

none

Run Automatically:

none


none

Description:

none

Run Automatically:

none


Display Name: NSA Analysis Results Monitor (update)


Novell.Linux.NSA.AnalysisResults.Update



“Interval” parameter is set to 3600 seconds by default.






Display Name:




none

Description:

none

Run Automatically:

none


none

Description:

none

Run Automatically:

none




90 Novell


ber 2009

Display Name: NSA Analysis Results Monitor (virtualization)


Novell.Linux.NSA.AnalysisResults.Virtualization









Display Name:




none

Description:

none

Run Automatically:

none


none

Description:

none

Run Automatically:

none





ber 2009

Display Name: Check NSA patterns update


Novell.Linux.NSA.AnalysisResults.Service

Description: Check the NSA patterns distribution Web site for a newer version of the pattern descriptions. If a newer version is available, this monitor indicates an error condition. The monitor indicates whether a newer version of the patterns should be downloaded and installed. The decision to invoke the task that downloads and installs the newer version of the patterns is up to you. Downloading and installing the newer pattern definitions can be done automatically by enabling the recover task associated with this monitor.


“IntervalSeconds” parameter is set to 86400 (24 hours) by default.

NoUpdatesAvailable (state is Healthy)

UpdatesAvailable (state is Critical)

An error state indicates that a newer version of the pattern definitions is available on the Novell Support Advisor Web site. A healthy state indicates that the currently installed version of the pattern definitions is up to date.

Display Name:

NSA Analysis Data Expired.



Check Updates Diagnostic.

Description:

Determines if the a newer analysis pattern is available.

Run Automatically:

Yes


Check Updates Recovery

Description:

Updates the analysis patterns and data gathering utility.

Run Automatically:

No




92 Novell


ber 2009

Display Name: NSA Analysis Data Expired


Novell.Linux.NSA.AnalysisResults.Service

Description: Determines if the last time that the analysis data was collected has exceeded an expiration threshold. The default expiration threshold is set to 30 days. The expiration threshold can be changed by overriding the ExpirationDays parameter for this monitor.


“IntervalSeconds” parameter is set to 86400 (24 hours) by default.

NotExpired (state is Healthy)

Expired (state is Critical

An error state indicates that the current analysis data set has exceeded the expiration threshold and should be updated. A healthy state indicates that the current analysis data set is within the expiration threshold.

Display Name:

NSA Analysis Data Expired.



NSA Analysis Data Expired Diagnostic.

Description:

Determines if the last time that the analysis data was collected has exceeded an expiration threshold.

Run Automatically:

Yes


NSA Analysis Data Expired Recovery

Description:

Runs the Novell Support Advisor data gathering utility on the associated server.

Run Automatically:

No





ber 2009

Novell Support Advisor Rules

Rule Description and Information Overrides

Display Name: NSA Alerts Rule

Monitors the analysis results that are produced by the Novell support Advisor utilities and generates alerts that correspond to the various result states.

The properties for each pattern analysis result con links or text that describe possible resolutions for the issue that is being reported. Please see the associated result element.

Additional Information: Look for the following status types:

STATUS_TEMPORARY: This is the initial overall status. Used for pre-condition processing.

STATUS_PARTIAL: All criteria are only partially checked. A status that can be used to test various conditions before assigning a valid exit condition, which is an overall status of STATUS_SUCCESS or higher. Used for pre-condition processing.

STATUS_SUCCESS: All criteria have been checked. All are confirmed to be valid and working.

STATUS_RECOMMEND: All criteria have been checked, but the linked solution is a recommendation and does not fall into the other categories. Used to recommend an optimization TID, documentation, or product promotions.

STATUS_PROMOTION: All criteria have been checked. this status is used to suggest a novell product or service from which the customer might benefit.

STATUS_WARNING: All criteria have been checked. The criteria show that a problem might occur, but it might not be manifesting symptoms currently.

STATUS_CRITICAL: All criteria have been checked. The criteria show that the server is currently matching criteria for the issue being checked.

STATUS_ERROR: Not all criteria could be checked. A fatal pattern error has occurred–for example, a file not found.



94 Novell


ber 2009

Novell Support Advisor Tasks

3.10.2 Appearance of the Novell Support Advisor Management Pack in Operations Manager

“Novell Support Advisor General Views” on page 94“Novell Support Advisor Overall Analysis Views” on page 95“Detail View” on page 95“Access to NSA Service Tasks” on page 95“NSA Analysis by Category” on page 95

Novell Support Advisor General Views

Task Description

Display Name: Gather NSA Info This is a long-running task that might take several minutes to complete.

The task invokes a service on the specified server that gathers detailed information about the server’s current health state. When the task is complete, the output details each of the queried areas of the server.

The results of the gathering task are displayed in the next discovery cycle for the NSA Management Pack. Because the discover cycle interval might be several hours, you might have to override the discovery interval.

Display Name: Update NSA Pattern Definitions

This is a long-running task that might take several minutes to complete.

The task downloads and installs the Novell Support Advisor information gathering patter descriptions if a newer version is available. To complete this task the specified server must have access to the Internet.


Novell Support Advisor Alerts Path

Source

Name

Resolution State

Created

Age



ber 2009

Novell Support Advisor Overall Analysis Views

Detail View

The Detail View of the System Center Operations Monitor is located in the center bottom of the console. It displays information about the selected server, as detailed in the Properties of the Novell Support Advisor Classes. The values of these classes often contain live links to technical information documents (TIDs) from Novell support, security advisories, documentation, CoolSolutions articles, and so on.

Access to NSA Service Tasks

Access to the NSA Services Tasks is found on the right-hand Actions view of the Operations Manager Console when a server in the Novell Support Advisor State view is selected.

Figure 3-10 NSA Service Tasks in the Operations Manager Console

NSA Analysis by Category

Additional, more discrete views of each NSA monitored element are included in the Operations Manager Console under the object NSA Analysis by Category. Each element displays its own views that list the properties of each category along with additional detail about each category:

ClusteringConnectivityedirectoryMigrationOES


Novell Support Advisor State State

Name

Path

NSA Agent Last Run

NSA Patterns Last Update

Novell Support Advisor Overall Analysis Results State

Name

Product

Path

Overall Info

Service Category


96 Novell


ber 2009

OtherPrintSecuritySLEUpdateVirtualization


Novell Linux Management Pack 1.0.1 for System Center ... · Novell Linux Management Pack 1.0.1 for...

Documents

Transcript of Novell Linux Management Pack 1.0.1 for System Center ... · Novell Linux Management Pack 1.0.1 for...