BMC PATROL for Servers Release Notes

Release Notes

BMC Performance Managerfor ServersVersion: 3.0.00October 15, 2010

BMC Software is releasing version 3.0.00 of the BMC Performance Manager solution for Servers. These release notes provide information about the licensing, enhancements, resolved problems, and problems that remain open in this version. This information supplements and supersedes information in the documents listed in “Related information” on page 55.

The following topics are provided:

Solution name change . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Overview of BMC Performance Manager for Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Overview of BMC PATROL for Microsoft Windows Servers . . . . . . . . . . . . . . . . . 3Overview of BMC PATROL for UNIX and Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Requirements and supported resources for PATROL for Microsoft Windows Servers 5Operating system support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Supported BMC PATROL products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Component dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Support for virtualized platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Language support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Requirements and supported resources for PATROL for UNIX and Linux . . . . . . . . . 8Supported operating systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Supported BMC PATROL products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Installation requirements for Perform Data Collector . . . . . . . . . . . . . . . . . . . . . . . 11Support for virtualized platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Language support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

What’s new in BMC Performance Manager for Servers. . . . . . . . . . . . . . . . . . . . . . . . . 12Known issues and workarounds in BMC Performance Manager for Servers . . . . . . 13

NOTE Before you install the product, check the Customer Support website at http://www.bmc.com/support for

■ updated documentation (for example, flashes and technical bulletins)■ product downloads, patches, and fixes (PTFs)■ product availability and compatibility (PAC) data

*176366**176366*

*176366*

http://www.bmc.com/support

Context-sensitive online Help is not available on some consoles. . . . . . . . . . . . . . 13Online Help on Microsoft Windows Vista . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

BMC PATROL KM for Microsoft Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14What’s new in PATROL KM for Microsoft Windows 4.3.00 . . . . . . . . . . . . . . . . . . 14Corrected problems in PATROL KM for Microsoft Windows 4.3.00. . . . . . . . . . . 19Known issues in PATROL KM for Microsoft Windows 4.3.00 . . . . . . . . . . . . . . . . 19

BMC PATROL KM for Microsoft Windows Active Directory. . . . . . . . . . . . . . . . . . . . 20Corrected problems in PATROL KM for Microsoft Windows Active Directory

1.6.30 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Known issues in PATROL KM for Microsoft Windows Active Directory 1.6.30. 21

BMC PATROL KM for Microsoft Windows Active Directory Remote Monitoring. . 21Managed node prerequisites for PATROL KM for Microsoft Windows AD

Remote Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22BMC PATROL KM for Microsoft Cluster Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

What’s new in PATROL KM for Microsoft Cluster Server 1.7.20. . . . . . . . . . . . . . 22Corrected problems in PATROL KM for Microsoft Cluster Server 1.7.20. . . . . . . 24Known issues in PATROL KM for Microsoft Cluster Server 1.7.20 . . . . . . . . . . . . 25

BMC PATROL KM for Microsoft COM+ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Known issues in PATROL KM for Microsoft COM+ 1.3.10 . . . . . . . . . . . . . . . . . . 26

BMC PATROL KM for Microsoft Windows Domain Services . . . . . . . . . . . . . . . . . . . 26Known issue in PATROL KM for Microsoft Windows Domain Services 1.5.10 . 26

BMC PATROL Wizard for Microsoft Performance Monitor and WMI . . . . . . . . . . . . 27What’s new in PATROL Wizard for Microsoft PM and WMI 2.1.20 . . . . . . . . . . . 27Known issue in PATROL Wizard for Microsoft PM and WMI 2.1.20 . . . . . . . . . . 29

BMC PATROL Cluster Configuration Wizard. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Corrected problem in PATROL Cluster Configuration Wizard 1.5.20 . . . . . . . . . 29

BMC PATROL KM for UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30What’s new in BMC PATROL KM for UNIX 9.9.00 . . . . . . . . . . . . . . . . . . . . . . . . . 30Corrected problems in BMC PATROL KM for UNIX 9.9.00 . . . . . . . . . . . . . . . . . . 36Known issues in BMC PATROL KM for UNIX 9.9.00 . . . . . . . . . . . . . . . . . . . . . . . 37

BMC PATROL KM for Log Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38What’s new in BMC PATROL KM for Log Management 2.6.10. . . . . . . . . . . . . . . 38Corrected problems in BMC PATROL KM for Log Management 2.6.10. . . . . . . . 40BMC PATROL KM for Event Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

BMC PATROL KM for Event Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41What’s new in BMC PATROL KM for Event Management 2.8.10 . . . . . . . . . . . . . 41What’s new in BMC PATROL KM for Event Management 2.7.12 . . . . . . . . . . . . . 42What’s changed in BMC PATROL KM for Event Management 2.7.10 . . . . . . . . . 42What’s changed in BMC PATROL KM for Event Management 2.7.09 . . . . . . . . . 44Corrected problem in BMC PATROL KM for Event Management 2.8.10 . . . . . . . 45Known issues in BMC PATROL KM for Event Management 2.8.10 . . . . . . . . . . . 46

BMC PATROL KM for History Loader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Corrected problem in BMC PATROL History Loader KM 1.5.20. . . . . . . . . . . . . . 47Known issue in BMC PATROL KM for History Loader 1.5.20 . . . . . . . . . . . . . . . . 47

BMC PATROL Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Compatibility with PATROL Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Support for the User Account Control (UAC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Unsupported PSL format options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48What’s new in PATROL Agent 3.8.50 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Internationalization and localization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

2 Release Notes October 15, 2010

Solution name change

Known issues and workarounds in PATROL Agent 3.8.50 . . . . . . . . . . . . . . . . . . 52Download and installation information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

How to obtain the solution. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Prerequisites for installing PATROL for Microsoft Windows Servers and

PATROL for UNIX and Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Related information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Support for BMC Performance Manager for Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Solution name changeThe BMC PATROL solution for Microsoft Windows Servers and the BMC PATROL solution for UNIX® and Linux® are now being marketed under a new name: BMC Performance Manager for Servers. The product kit, media, and download sites use the new solution name. The product documents, interface, and code continue to use the former product names.

Overview of BMC Performance Manager for Servers

This version of BMC Performance Manager for Servers contains the following solutions:

Overview of BMC PATROL for Microsoft Windows Servers

The components and products that are included in version 4.3.00 of the PATROL solution for Microsoft Windows Servers are shown in Table 1. For components that have been updated for this release or have issues that remain open in this release, a page number is provided to relevant information in this document. For more detailed information about the components, see documents listed in “Related information” on page 55.

Solution Version

BMC PATROL for Microsoft Windows Servers 4.3.00

BMC PATROL for UNIX and Linux 9.9.00

NOTE The PATROL solution for Microsoft Windows Servers does not ship the BMC PATROL Perform Agent product.

BMC Performance Manager version 3.0.00 for Servers 3

Overview of BMC PATROL for UNIX and Linux

Overview of BMC PATROL for UNIX and Linux

This version of BMC PATROL for UNIX and Linux contains the components and products shown in Table 2. If this document describes new features, changed features, known issues, or corrected problems for a component related to this release, a reference to that information is provided. For more detailed information about the components, see the documents listed in “Related information” on page 55.

Table 1 Components and products

Component/ product Version Page

BMC PATROL Knowledge Module (KM) for Microsoft Windows 4.3.00 14

BMC PATROL KM for Microsoft Windows Active Directory 1.6.30 NAa

BMC PATROL KM for Microsoft Windows Active Directory Remote Monitoring

1.7.10 NAa

a A page number is not applicable. Either this component has not been updated for this release of the solution or it has its own release notes separate from this document. Any information in this document about this component is repeated from release notes for earlier versions of the solution.

BMC PATROL KM for Microsoft Cluster Server 1.7.20 NAa

BMC PATROL KM for Microsoft COM+ 1.3.10 NAa

BMC PATROL KM for Microsoft Domain Services 1.5.10 NAa

BMC PATROL Wizard for the Microsoft Performance Monitor and WMI products

2.1.20 NAa

BMC PATROL KM for Log Management 2.6.10 38

BMC PATROL KM for Event Management 2.8.10 NAa

BMC PATROL History Loader KM 1.5.20 NAa

BMC PATROL KM for Microsoft Message Queue 1.4.10 NAa

BMC PATROL Cluster Configuration Wizard 1.5.20 NAa

BMC PATROL Adapter for Microsoft Office 1.1.20 NAa

BMC PATROL Adapter for the Microsoft Office product –Server Report Templates

1.3.00.02 NAa

BMC PATROL Agent 3.8.50 48

BMC PATROL Security 3.0.14 NAa

BMC Installation Utility 7.5.60 NAa

Table 2 Components and products (part 1 of 2)


Installation utilitya 7.5.60 NAb

BMC PATROL KM for UNIX 9.9.00 30

BMC PATROL Agent 3.8.50 48

BMC PATROL KM for Log Management 2.6.10 38


Requirements and supported resources for PATROL for Microsoft Windows Servers

Requirements and supported resources for PATROL for Microsoft Windows Servers

This section provides release-specific information about requirements and supported resources for version 4.3 of the PATROL solution for Microsoft Windows Servers and all of its components. Additional product requirements and supported resources are listed in BMC PATROL for Microsoft Windows Servers Getting Started. For requirements that are specific to a component, see the section for that component in this document.

Operating system support

All components of version 4.3 of the PATROL solution for Microsoft Windows Servers work with the following operating systems.

BMC PATROL KM for Event Management 2.8.10 NAb

BMC PATROL History Loader KM 1.5.20 NAb

BMC PATROL Perform Data Collector 7.5.10 NAb

BMC PATROL Perform Agenta 7.5.10 NAb

BMC PATROL Security 3.0.14 NAb

a This component is not part of the BMC PATROL solution for UNIX and Linux, but it is included with the solution for your convenience.

b A page number is not applicable. Either this component has not been updated for this release of the solution or it has its own release notes separate from this document. Any information in this document about this component is repeated from release notes for earlier versions of the solution.

NOTE ■ The minimum required version of BMC PATROL Perform Data Collector (bgscollect) is

7.5.10.0160.

■ The DCM executable version in the default image of BMC PATROL KM for UNIX version 9.9.00 is 7.5.10.0160.

Table 2 Components and products (part 2 of 2)



Supported BMC PATROL products

■ Microsoft Windows XP Professional, SP 3, x86■ Microsoft Windows XP Professional, SP 3, x86-64■ Microsoft Windows Server 2003, SP 2, x86■ Microsoft Windows Server 2003, SP 2, x86-64■ Microsoft Windows Server 2003, SP 2, Itanium 2■ Microsoft Windows Vista, SP 1, x86 and x86-64■ Microsoft Windows Server 2008, x86 and x86-64, Itanium 2■ Microsoft Windows Server 2008 Core x86 and x86-64■ Microsoft Windows Server 2008 R2, x86-64, Itanium 2■ Microsoft Windows Server 2008 R2 Core, 64-bit■ Microsoft Windows 7 (x86, x86-64)


All components of version 4.3 of PATROL for Microsoft Windows Servers work with the PATROL components listed in Table 3.

NOTE You can monitor all the following operating systems as a remote host.

NOTE ■ The BMC PATROL Adapter for the Microsoft Office product and BMC PATROL Adapter

for the Microsoft Office – Server Report Templates components are not supported on Microsoft Windows Server 2008.

■ References to x86-64 include AMD64 (which includes Opteron) and Intel 64 architecture (formerly known as Intel Extended Memory 64 Technology, or Intel EM64T).

■ References to Microsoft Windows Server 2003 (which includes Windows Server 2003 R2), Microsoft Windows Vista, and Microsoft Windows Server 2008 (which includes Windows Server 2008 R2) include all editions of these platform families and their service packs, except where service packs are specifically listed in the table.

Table 3 Supported BMC PATROL components (part 1 of 2)

BMC PATROL component Versions supported

BMC PATROL Agent 3.6 and later

BMC PATROL Securitya 3.0.14

BMC PATROL Console for Microsoft Windowsb 3.5.2x and later

BMC PATROL Console for UNIX®c 3.5.2x and later

BMC PATROL Central Operator – Microsoft Windows Edition 7.5.x and later


Component dependencies

Component dependencies

Some of the components contained in PATROL for Microsoft Windows Servers depend on other components to operate. Table 4 lists those components and their dependencies.

BMC PATROL Central Operator – Web Edition 7.5.x and later

BMC PATROL Console Server 7.5.x and later

Distribution Server 7.5.x and latera Version 3.8.50 of the PATROL Agent uses version 3.0.14 of the PATROL Security libraries

and utilities. To prevent conflicts with PATROL components that are using earlier versions of PATROL Security, the binary files, policy files, and log files associated with PATROL Security 3.0.14 are located in separate folders with _v3.0 appended to the folder name. For more information, see the PATROL Security Release Notes, version 3.0.14.

b PATROL for Microsoft Windows Servers is supported on all Windows platforms that are supported by PATROL consoles.

c PATROL for Microsoft Windows Servers is supported on all UNIX platforms that are supported by the PATROL Console for UNIX.

Table 4 Components and their dependencies

Component Dependency Comments

PATROL KM for Microsoft COM+

PATROL KM for Microsoft Windows version 3.9.20 or later for full support

■ With versions 3.9.10 and later, the KM is discovered and event log parameters are available.

■ With versions earlier than 3.9.10, the KM is discovered, but the event log parameters are not available.

PATROL KM for Microsoft Windows Active Directory

■ PATROL KM for Microsoft Windows version 3.9.20 or later for full support

■ An active OS KM Event Log instance for the following Windows Event Logs:

— Application— Directory Service— DNS Server— File Replication Service

■ With versions 3.9.20 and later, the KM is discovered and event log parameters are available.

■ With versions 3.9.00 and 3.9.10, the KM is discovered, but event log parameters are not available.

■ With versions earlier than 3.9.00, this KM fails prediscovery and writes a message to the mwd.log file, and to the system output window.

PATROL KM for Microsoft Cluster Server

PATROL KM for Microsoft Windows version 3.9.20 and later

Installing either the NT_BASE.kml or the NT_LOAD.kml file satisfies this dependency.

Table 3 Supported BMC PATROL components (part 2 of 2)

BMC PATROL component Versions supported


Support for virtualized platforms

For other requirements, see BMC PATROL for Microsoft Windows Servers Getting Started. For information about product documents and how to obtain them, see “Related information” on page 55.


Virtualization technology provides a layer of abstraction between the computing, storage, and networking hardware, and the software that runs on it. For more information, see the Support Policy for Virtualized Platforms section under Review Policies on the BMC Customer Support website at http://www.bmc.com/support.

Language support

PATROL for Microsoft Windows Servers has been validated in multibyte language environments. However, the user interface and online Help for PATROL for Microsoft Windows Servers are displayed in English on all non-English platforms.

A Japanese language pack is available for version 4.3.00 of PATROL for Microsoft Windows Servers. After installing the Japanese language pack, the user interface of PATROL for Microsoft Windows Servers is displayed in the Japanese language on the Japanese operating system.

The Japanese language pack is available for download from the BMC Electronic Product Distribution (EPD) website at http://webapps.bmc.com/epd.

Requirements and supported resources for PATROL for UNIX and Linux

This section provides release-specific information about requirements and supported resources for version 9.9 of BMC PATROL for UNIX and Linux. For general information about requirements and supported resources, see BMC PATROL for UNIX and Linux Getting Started. For requirements that are specific to a component, see the section for that component in this document.



http://webapps.bmc.com/epd

Supported operating systems


Table 5 lists the operating systems that are supported by version 9.9 of BMC PATROL for UNIX and Linux. These operating systems are supported in Simplified Chinese, Traditional Chinese, Korean, Japanese, French, and German languages (CTKJFG) unless otherwise specified.

NOTE ■ You can monitor all the operating systems listed in Table 5 as a remote host.

■ When HP-UX computers with the older versions of OpenSSH are added as remote hosts, they might get disconnected frequently because of OpenSSH older version, which impacts monitoring of the remote hosts. To avoid this, upgrade to the version 5.3 of OpenSSH.

Table 5 Supported operating systems (part 1 of 2)

Supported operating system Comments

HP-UX 11i v3 (B11.31), 64-bit, Itanium 2 Install the C++ run-time patch (PHSS_24627) on the HP-UX 11i platforms.HP-UX 11i v3 (B11.31), 64-bit, PA-RISC

HP-UX 11i v2 (B11.23), 64-bit, PA-RISC

HP-UX 11i v2 (B11.23), 64-bit, Itanium 2

HP-UX 11.11i (B11.11), 64-bit, PA-RISC

IBM® AIX® 6.1, 64-bit hardware,64-bit kernel, 64-bit ABI ■ BMC PATROL executables on AIX 32-bit OSs require at least the following maintenance level: AIX 5.3-oslevel 5300-01.

■ BMC recommends that you use technology level, TL02, to get WPAR resource utilization data on the AIX 6.1 operating systems.

■ POWER4, POWER5, POWER6, and POWER7 are supported systems.

IBM AIX 5.3, 32-bit hardware, 32-bit kernel, 32-bit ABI




Oracle® Solaris™ 10, 64-bit, Sparc The supported patch level of Solaris 10 for the current release of the BMC PATROL KM for UNIX product is 10/09 s10s_u8wos_08a.Oracle Solaris 10, x86

Oracle Solaris 10, x86-64

Oracle Solaris 9, 32-bit, Sparc





Red Hat Enterprise Linux® 5.x, x86 ■ The zSeries system is not supported in CTKJFG.

■ x86 refers to Intel PII, PIII, P4, and Xeon 32-bit processor systems.

■ x86-64 refers to Opteron (AMD 64) and Intel EM64T systems that support 64-bit libraries and executables.

■ 32-bit run-time environments are required on x86-64 OSs.

■ Red Hat Enterprise Linux is supported up to version 5.5.

Red Hat Enterprise Linux 5.x, x86-64

Red Hat Enterprise Linux 5.x, Itanium

Red Hat Enterprise Linux 5.x, IBM zSeries®, 64-bit

Red Hat Enterprise Linux AS and ES 4, x86

Red Hat Enterprise Linux AS and ES 4, Itanium

Red Hat Enterprise Linux AS and ES 4, x86-64

Red Hat Enterprise Linux AS and ES 4, zSeries, 31-bit

Red Hat Enterprise Linux AS and ES 4, zSeries, 64-bit

SUSE Linux Enterprise Server 11, x86 ■ This OS is not supported in CTJKFG.■ x86 refers to Intel PII, PIII, P4, and Xeon 32-bit

processor systems.■ x86-64 refers to Opteron (AMD 64) and Intel

EM64T systems that support 64-bit libraries and executables.

■ Service Pack 3 for version 10 supports all the variations of the hardware.

■ Service Pack 1 for version 11 supports all the variations of the hardware.

SUSE Linux Enterprise Server 11, x86-64

SUSE Linux Enterprise Server 11, Itanium

SUSE Linux Enterprise Server 11, zSeries, 64-bit

SUSE Linux Enterprise Server 10, x86

SUSE Linux Enterprise Server 10, x86-64

SUSE Linux Enterprise Server 10, zSeries, 64-bit

SUSE Linux Enterprise Server 10, Itanium

Oracle® Enterprise Linux 5.x, x86 ■ x86 refers to Intel PII, PIII, P4, and Xeon 32-bit processor systems.

■ x86-64 refers to Opteron (AMD 64) and Intel EM64T systems that support 64-bit libraries and executables.

■ 32-bit run-time environments are required on x86-64 OSs.

■ Oracle Enterprise Linux is supported up to version 5.5.

Oracle Enterprise Linux 5.x, x86-64

Oracle Enterprise Linux 5, x86

Oracle Enterprise Linux 5, x86-64

Oracle Enterprise Linux 4, x86

Oracle Enterprise Linux 4, x86-64

NOTE ■ VMware ESX Server versions 2.5.x (x86), 3.0 (x86), 3.5 (x86), and 4.0 (x86) refer to Intel PII,

PIII, P4, and Xeon 32-bit processor systems. BMC PATROL for UNIX and Linux supports monitoring of ESX servers as remote hosts. VMware does not recommend installing any software on the service console. Therefore, BMC recommends that you use the remote monitoring functionality of PATROL KM for UNIX version 9.9.00.

■ If you select Perform Data Collector as a default configuration for installation, installation fails at 100% on SUSE Linux Enterprise Server 11, Itanium platform. For more information, see QM001678603 in Table 23 on page 37.

Table 5 Supported operating systems (part 2 of 2)

Supported operating system Comments




All components of version 9.9 of PATROL for UNIX and Linux work with the BMC PATROL components shown in Table 6:

Installation requirements for Perform Data Collector

Installation of Perform Data Collector (bgscollect) requires minimum 300 MB of free space in the /tmp directory or in the home directory of the user using which the installation is started.

You may also set the IATEMPDIR environment variable to a directory on a disk partition with enough free disk space.

To set the IATEMPDIR variable, enter one of the following commands before starting the installation process:

■ for Bourne shell (sh), ksh, bash and zsh:

A. $ IATEMPDIR=Directorycontainingfreespace

B. $ export IATEMPDIR

■ for C shell (csh) and tcsh:

Table 6 Supported BMC PATROL components

BMC PATROL component Version supported

BMC PATROL Security 3.0.14a

a Version 3.8.50 of the BMC PATROL Agent uses version 3.0.14 of the BMC PATROL Security libraries and utilities. To prevent conflicts with BMC PATROL components that are using earlier versions of BMC PATROL Security, the binary files, policy files, and log files associated with BMC PATROL Security 3.0.14 are located in separate folders with _v3.0 appended to the folder name. For more information, see BMC PATROL Security Release Notes, version 3.0.14.

BMC PATROL Console for Microsoft Windowsb

b BMC PATROL for UNIX and Linux is supported on all Windows platforms that are supported by BMC PATROL Consoles.

3.5.2x and later

BMC PATROL Console for UNIXc

c BMC PATROL for UNIX and Linux is supported on all UNIX platforms that are supported by BMC PATROL Consoles for UNIX.

3.5.2x and later

BMC PATROL Central Operator – Microsoft Windows Edition 7.5.x and later

BMC PATROL Central Operator – Web Edition 7.5.x and later

BMC PATROL Console Server 7.5.x and later

Distribution Server 7.5.x and later



$ setenv IATEMPDIR Directorycontainingfreespace


Virtualization technology provides a layer of abstraction between the computing, storage, and networking hardware, and the software that runs on it. For more information, see the Support Policy for Virtualized Platforms section under Review Policies on the BMC Customer Support website at http://www.bmc.com/support.

Language support

PATROL for UNIX and Linux has been validated in multibyte language environments. However, the user interface and online Help for PATROL for UNIX and Linux are displayed in English on all non-English platforms.

A Japanese language pack is available for version 9.9.00 of PATROL for UNIX and Linux. After installing the Japanese language pack, the user interface of PATROL for UNIX and Linux is displayed in the Japanese language on the Japanese operating system.

The Japanese language pack is available for download from the BMC EPD website at http://webapps.bmc.com/epd.

What’s new in BMC Performance Manager for Servers

BMC Performance Manager for Servers has been enhanced with the following changes and new features. For information about changes and new features in the solution components, see the “What's new” sections for the components later in the document.

What’s new in PATROL for Microsoft Windows Servers

PATROL for Microsoft Windows Servers discontinues supports for the following operating systems:

■ Microsoft Windows Server 2000, SP 4, x86■ Microsoft Windows 2000 Professional, SP 4, x86




What’s new in PATROL for UNIX and Linux

What’s new in PATROL for UNIX and Linux

PATROL solution for UNIX and Linux now supports the following operating systems:

■ Red Hat Enterprise Linux 5.5 (x86, x86-64, zSeries, Itanium 64)■ SUSE Linux Enterprise Server 11 SP1 (x86, x86-64, zSeries, Itanium 64)■ Oracle Enterprise Linux 5.5 (x86, x86-64)

Known issues and workarounds in BMC Performance Manager for Servers

This section describes the issues that remain open in this release of the PATROL for Microsoft Windows Servers and PATROL for UNIX and Linux solutions. For information about known issues and workarounds for the solution components, see the component sections later in the document.

Context-sensitive online Help is not available on some consoles

If you are using BMC PATROL Central Operator – Microsoft Windows Edition, the context-sensitive Help buttons in some pop-up dialog boxes do not work.

Workaround: Access the Help menu from the menu bar or click a Help button in a standard dialog box. Then search for the topic that you want to see by searching for the name of the dialog box or menu command. For instructions about how to access Help, see BMC PATROL for UNIX and Linux Getting Started or BMC PATROL for UNIX and Linux Getting Started depending upon the solution you are working on.

NOTE You can install the online Help files only on platforms that are supported by the console or the console server.


Online Help on Microsoft Windows Vista

Online Help on Microsoft Windows Vista

In PATROL Central Operator – Microsoft Windows Edition on a Microsoft Windows Vista operating system, the online Help does not work. The Windows Help program (WinHlp32.exe) is used to display 32-bit Help files that have the .hlp extension. Microsoft did not include the WinHlp32.exe program with Microsoft Windows Vista.

Workaround: To view the online Help on Windows Vista, you must download the WinHlp32.exe program from the following Microsoft Windows support website and install it onto your computer:

http://go.microsoft.com/fwlink/?LinkID=82148

BMC PATROL KM for Microsoft WindowsThis section provides information about enhancements, corrected problems, and known issues in the PATROL KM for Microsoft Windows product.

What’s new in PATROL KM for Microsoft Windows 4.3.00

This section describes the new features in version 4.3.00 of PATROL KM for Microsoft Windows.


PATROL KM for Microsoft Windows now supports the Microsoft Windows 7 operating system.

Monitoring remote hosts

PATROL KM for Microsoft Windows now supports monitoring of remote hosts using the Windows Remote Management (WinRM) functionality.

WinRM is the Microsoft implementation of WS-Management Protocol, a standard Simple Object Access Protocol (SOAP)-based, firewall-friendly protocol that allows hardware and operating systems, from different vendors, to interoperate.

NOTE For more information about the enhancements in this release of the product, see the BMC PATROL KM for Microsoft Windows Operating System online Help and BMC PATROL Knowledge Module Getting Started Guide for Windows.


http://go.microsoft.com/fwlink/?LinkID=82148


PATROL KM for Microsoft Windows supports monitoring of the following application classes for a remote host:

■ NT_CACHE■ NT_CPU■ NT_CPU_CONTAINER■ NT_LOGICAL_DISKS ■ NT_LOGICAL_DISKS_CONTAINER ■ NT_MEMORY ■ NT_OS■ NT_PAGEFILE■ NT_PAGEFILE_CONTAINER■ NT_SERVICES■ NT_SERVICES_CONTAINER

You can add or remove remote hosts for monitoring using the Configure Remote Hosts KM command. When you add a remote host with local computer account using Configure Remote Hosts menu command, the remote host gets added to the TrustedHosts list of WinRM.

When you remove a host using Configure Remote Hosts menu command, it gets deleted from the TrustedHosts list only if the host was added with local computer account. However, if you uninstall the KM, the remote host does not get deleted from the TrustedHosts list. In this case, you need to remove the host using the following winrm commands:

■ winrm set winrm/config/client @{TrustedHosts=”host1host2host3..”}

host1, host2, and host3 are the remote hosts that you want to keep in the TrustedHosts list.

■ winrm set winrm/config/client @{TrustedHosts=””}

For more information about monitoring remote hosts and the WinRM functionality, see BMC PATROL Knowledge Module Getting Started for Windows.

Prerequisites for remote monitoring

Before you can use the remote monitoring feature successfully, you must meet the following requirements:

NOTE One PATROL Agent can monitor a maximum of 75 remote hosts at a time.



■ Requirements for host machines (PATROL Agent):

— WinRM version 1.1 or 2.0 should be installed.

■ Requirements for remote host:

— WinRM version 1.1 or 2.0 should be installed and running.— WinRM should be configured with listener either on HTTP or HTTPS.— Valid domain or local user who is a member of the Administrators group

Authentication

PATROL KM for Microsoft Windows client supports password-based authentication for local and domain users. It uses the following network authentication protocols:

■ Kerberos ■ Negotiate

For more information about these authentication mechanisms, see BMC PATROL Knowledge Module Getting Started for Windows.

Add multiple remote hosts

Multiple remote hosts can be added by comma separated list. While adding remote host through Configure Remote Hosts KM Command, you need to enter comma separated multiple host list in "Remote Host" field like Host1, Host2, Host3 with a same credential and port.



New application classes

This release supports the new application classes listed in Table 7.

New parameters

This release supports the new parameters listed in Table 8.

Table 7 New application classes in BMC PATROL KM for Microsoft Windows

Application class Description

NT_REMOTE_CONTAINER Hosts instances of all remote hosts. This container application class provides all the menu commands and tasks required to configure remote hosts for monitoring. The NT_REMOTE_CONTAINER application class is represented by Remote Monitoring in the PATROL console.

NT_REMOTE_HOST Contains application instances for each remote host. Each remote host contains the NT_OS container. The NT_REMOTE_HOST application class is represented by Host Name in the PATROL console.

Table 8 New parameters in BMC PATROL KM for Microsoft Windows (part 1 of 2)

Application class Parameter Description

NT_REMOTE_HOST RMPageFileDiscovery Discovers the page file instances (NT_PAGEFILE) of a remote host

RMCpuDiscovery Discovers the processor instances (NT_CPU) of a remote host

RMMemoryDiscovery Discovers the memory instance (NT_MEMORY) of a remote host

RMCacheDiscovery Discovers the cache instance (NT_CACHE) of a remote host

RMLogicalDiskDiscovery Discovers the logical disks and mount drive instances (NT_LOGICAL_DISKS) of a remote host

RMOSDiscovery Discovers the Windows operating system (NT_OS) application class for a remote host and establishes sessions with the WinRM server listener

RMServiceDiscovery Discovers the services instances (NT_SERVICES) of a remote host

NT_OS _Status Displays the status of the host

This parameter is active only for remote hosts.

_SystemConfig Displays the configuration information, such as system vendor, baseboard vendor, processor details, hardware serial number, number of network interfaces, and pagesize of the host computer

Note: This parameter is active only for a local host.


New pconfig variables

New pconfig variables

Table 9 lists the new pconfig variables added in this release of the product.

NT_CPU CPUprcrIdleTimePercent Displays the percentage of time for which the processor is idle during the sample interval

NT_PHYSICAL_DISK PDpdDiskBytesPerSec Displays the rate at which bytes are transferred to or from the disk during read or write operations

NT_MEMORY MEMmemCommittedBytesPercent

Displays the ratio of memory/committed bytes to memory/commit limit. Committed memory is the physical memory that is being used. The space for committed memory is reserved in the paging file. The commit limit is determined by the size of the paging file. If the size of the paging file increases, the commit limit also increases, and the ratio reduces.

MEMmemCommitLimit Displays the amount of virtual memory that can be committed without having to extend the paging file(s). Committed memory is the physical memory that is being used. The space for committed memory is reserved in the paging file. There can be one paging file on each logical drive. If the size of the paging file increases, this limit increases accordingly.

Table 9 New pconfig variables in PATROL KM for Microsoft Windows (part 1 of 2)

Variable Description

/REMOTE/HOSTS/hosts Specifies a comma separated list of the remote hosts that have been added for monitoring

/REMOTE/HOSTS/RemoteHost/connectionProtocol

Specifies the protocol (HTTP or HTTPS) that is used for remote host connection

Valid values are:■ 1 = HTTP■ 2 = HTTPS

/REMOTE/HOSTS/RemoteHost/userAccount

Specifies the user account which is used to connect to the remote host

/REMOTE/HOSTS/RemoteHost/accountProfile

Specifies the shared credential, if it has been used for remote host connection

/REMOTE/PROFILE/profileList Specifies a comma separated list of the profiles (shared credentials)

Table 8 New parameters in BMC PATROL KM for Microsoft Windows (part 2 of 2)



Corrected problems in PATROL KM for Microsoft Windows 4.3.00

Corrected problems in PATROL KM for Microsoft Windows 4.3.00

Table 10 describes the problems that were reported in earlier releases of PATROL KM for Microsoft Windows and have been addressed in this release.

Known issues in PATROL KM for Microsoft Windows 4.3.00

Table 11 describes the issues that remain open in PATROL KM for Microsoft Windows.

/REMOTE/PROFILE/ProfileName/hostList

Specifies a comma separated list of the monitored remote hosts with the respective profile

/REMOTE/PROFILE/ProfileName/userAccount

Specifies the user name for each profile

Table 10 Corrected problems in PATROL KM for Microsoft Windows

Tracking ID Description

QM001653902 The NT_PROCESS KM did not generate any event notification when a monitored process returned to OK state.

QM001654325 On Microsoft Windows 2008 Server, PATROL KM for Microsoft Windows did not discover a service that had a large buffer size.

QM001659386 On Microsoft Windows 2008 Server R2, the IP V4 and IP V6 network protocols did not get discovered.

Table 11 Known issues in PATROL KM for Microsoft Windows

Tracking ID Issue

QM001513969 The Event Viewer does not obtain category details for security events.

QM001515339 The event log does not appear in the console when the event log name contains a forward slash (/). Also, some of the event log functionality does not work when event log names are enclosed in double quotation marks ("").

QM001542411 On Microsoft Vista or Windows Server 2008, the following event log error message appears in the psx_server.log file:

Failed to obtain record information. Error = 223

This error message appears only when there are no events in the event logs, and it does not affect the performance of the KM.

Table 9 New pconfig variables in PATROL KM for Microsoft Windows (part 2 of 2)

Variable Description


BMC PATROL KM for Microsoft Windows Active Directory

BMC PATROL KM for Microsoft Windows Active Directory

The PATROL KM for Microsoft Windows Active Directory product lets you monitor and analyze your Microsoft Windows Active Directory environment.

Corrected problems in PATROL KM for Microsoft Windows Active Directory 1.6.30

Table 12 describes the problems that were reported in earlier releases of PATROL KM for Microsoft Windows Active Directory and have been addressed in this release.

QM001569848 If you rename a running partition from the HYPER-V Manager, the KM discovers this partition with the new name. However, the KM does not discover the virtual processor instances of this partition. These instances are discovered after the partition is restarted.

QM001673229 On Microsoft Windows Server 2008 and later, the Windows Event filter does not discover the description of a few events.

Table 12 Corrected problems in PATROL KM for Microsoft Windows Active Directory


QM001593832 The AdServerTimeDifference parameter reported incorrect information on a PDC Emulator.

QM001622881 If the server uptime was more than 45 days, the KM was not able to monitor correctly.

Table 11 Known issues in PATROL KM for Microsoft Windows

Tracking ID Issue


Known issues in PATROL KM for Microsoft Windows Active Directory 1.6.30

Known issues in PATROL KM for Microsoft Windows Active Directory 1.6.30

Table 13 describes the issues that remain open in PATROL KM for Microsoft Windows Active Directory.

BMC PATROL KM for Microsoft Windows Active Directory Remote Monitoring

Version 1.7.10 of the PATROL KM for Microsoft Windows Active Directory Remote Monitoring product provides remote enterprise monitoring of Active Directory objects. The Active Directory is the core feature of distributed systems in Microsoft Windows Servers.

The primary focus of the release of PATROL KM for Microsoft Windows AD Remote Monitoring is to monitor remote sites, domain controllers in those sites, and FSMO roles from member servers of a domain in the network.

Table 13 Known issues in PATROL KM for Microsoft Windows Active Directory

Tracking ID Issue

QM001544935 On a Microsoft Windows Server 2008 operating system, the AdDnsARecordExists parameter goes offline when Internet Protocol Version 6 (IPv6) is enabled.

Workaround: Disable IPv6. On a Microsoft Windows Server 2008 operating system, IPv6 is enabled by default. To disable IPv6, run the following command:

Netsh interface ipv6 6to4 set state disabled

The AdDnsARecordExists parameter will be online beginning with the next collection cycle.

QM001544933 On a Microsoft Windows Server 2008 operating system, the menu commands for the following KMs do not work when the Microsoft Computer Browser Service is disabled:

■ PATROL KM for Microsoft Windows Domain Services■ PATROL KM for Microsoft Cluster Server■ PATROL Cluster Configuration Wizard

Workaround: On a Microsoft Windows Server 2008 operating system, the Microsoft Computer Browser Service is disabled by default. To enable the Microsoft Computer Browser Service, start the service.


Managed node prerequisites for PATROL KM for Microsoft Windows AD Remote Monitoring

Managed node prerequisites for PATROL KM for Microsoft Windows AD Remote Monitoring

The local node (or member server) provides a client view of the Active Directory objects. The data provided for each managed node is collected within the context of the domain of which the managed node is a member.

To display information about Active Directory objects, the managed node must meet the following requirements:

■ PATROL Agent 3.6.00 or later must be installed.■ The default account for PATROL Agent must be a domain user account.

BMC PATROL KM for Microsoft Cluster ServerThe PATROL KM for Microsoft Cluster Server product monitors, analyzes, and manages a Microsoft server cluster and its associated nodes, groups, resources, and services.

What’s new in PATROL KM for Microsoft Cluster Server 1.7.20

PATROL KM for Microsoft Cluster Server has been enhanced with the following changes and new features.

New parameters

Table 14 on page 23 lists the new parameters supported by PATROL KM for Microsoft Cluster Server.


What’s new in PATROL KM for Microsoft Cluster Server 1.7.20

Changes in the FreeSpace parameter

The type of the FreeSpace parameter has been changed from Standard to Consumer. This parameter displays the free space information for a disk in MB.

Deactivation of parameters

The following parameters under the MCS_Clusters application class are now inactive by default:

■ ClusterAvailability■ ClusterUptime ■ ClusterUptimeColl

Table 14 New parameters in PATROL KM for Microsoft Cluster Server


MCS_Group_Resources FreeSpaceGB Displays the free space on the disk in GB

An annotation shows the free space for each partition.

FreeSpaceColl Collects the free space data for the FreeSpace and FreeSpaceGB parameters

MCS_Collectors ClusterCollectionStatus Displays the collection status of the following parameters:

■ AvWorkLoad ■ BackupClusterDatabase ■ ClusterLogFileError ■ ClusterLogFileSize ■ FreeSpace■ FreeSpaceGB ■ QuorumSize

This parameter can have the following values:

■ 0 (no error): Indicates that no error occurred while collecting data for the preceding parameters

■ 1 (error): Indicates that an error occurred while collecting data at least for at least one of the preceding parameters

NOTE The PATROL Uptime cluster resource will not be created during installation of PATROL KM for Microsoft Cluster Server.


Corrected problems in PATROL KM for Microsoft Cluster Server 1.7.20

Corrected problems in PATROL KM for Microsoft Cluster Server 1.7.20

Table 15 describes the problems that were reported in earlier releases of PATROL KM for Microsoft Cluster Server and have been addressed in this release.

Table 15 Corrected problems in PATROL KM for Microsoft Cluster Server


QM000554750 After you installed PATROL KM for Microsoft Cluster Server, the mcsMonitorAgent.cfg file was missing. Therefore, some of the KM parameters went offline.

QM001513864 A domain name could not contain more than 15 characters.

QM001549344 If you changed the default configuration of a cluster, the KM in an Internal CLA configuration did not discover any cluster KM instances.

QM001622441 The PATROL Uptime cluster resource in the Cluster Administrator went into a failed state when there was a File Share Witness quorum configuration. Also, the ClusterAvailability and ClusterUpTime parameters went offline and the ClusterUptimeColl parameter went into an alarm state.

QM001639433 PATROL Event Manager of the Cluster Administrator displayed the following ERROR events continuously:

Collector Freespace could not obtain data from cluster/node

Collector AvWorkLoad could not obtain data from cluster/node


Known issues in PATROL KM for Microsoft Cluster Server 1.7.20

Known issues in PATROL KM for Microsoft Cluster Server 1.7.20

Table 16 describes the issues that remain open in PATROL KM for Microsoft Cluster Server.

BMC PATROL KM for Microsoft COM+The PATROL KM for Microsoft COM+ product provides the necessary components for the PATROL console user to proactively monitor and manage various parts of the Microsoft COM+ runtime environment and COM+ applications. The Microsoft COM+ runtime environment manages instances of COM+ components and provides middleware, such as transaction processing, object pooling, and asynchronous message queuing.

Table 16 Known issues in PATROL KM for Microsoft Cluster Server

Tracking ID Issue

QM001549787 The ClusterLogFileSize and ClusterLogFileError parameters of the MCS_Nodes application class are offline after you generate a cluster log through the command line. The cluster.log file is not generated on Microsoft Windows Server 2008 cluster by default. The ClusterLog environment variable that contains the path of this cluster.log file on cluster nodes is no longer available on Microsoft Windows Server 2008 cluster.

Workaround: Create the ClusterLog environment variable that contains the path of the cluster.log file on nodes that contain this log file (for example, ClusterLog=c:\windows\cluster\reports\cluster.log)

QM000514642 If you install PATROL KM for Microsoft Cluster Server 1.7.x over version 1.5.x, the MSC_Cluster application instance appears at the same level as the host instance.

Workaround: To display the new structure (that is, for the MSC_Cluster application instance to appear under the host instance), use one of the following methods:

■ Manually drag the MSC_Cluster application into the host.■ Clear the PATROL cache and reload the KM.

QM000514645 If the PATROL Operator Console (or the Console Server) has a PATROL Agent default account already stored as a profile, it uses that stored default account. However, if that stored account does not have the privileges required for the PATROL KM for Microsoft Cluster Server, the connection to the Agent might work, but the configuration fails. Specifically, the Agent default account must have the “Act as part of OS” privilege for PATROL KM for Microsoft Cluster Server to operate.


Known issues in PATROL KM for Microsoft COM+ 1.3.10

Known issues in PATROL KM for Microsoft COM+ 1.3.10

Table 17 describes the issues that remain open in version 1.3.10 of PATROL KM for Microsoft COM+.

BMC PATROL KM for Microsoft Windows Domain Services

The PATROL KM for Microsoft Windows Domain Services product contains the knowledge that PATROL uses to monitor, detect, and correct problems encountered within a Microsoft Windows Server domain.

Known issue in PATROL KM for Microsoft Windows Domain Services 1.5.10

Table 18 describes an issue that remains open in PATROL KM for Microsoft Windows Domain Services.

Table 17 Known issues in PATROL KM for Microsoft COM+

Tracking ID Issue

QM001544944 In a Microsoft Windows 2003 or Microsoft Windows Server 2008 environment, PATROL KM for Microsoft COM+ reports incorrect data for the ComAppCallTime parameter when you add the multiple running Com+ applications for monitoring.

QM001544940 In a Microsoft Windows Server 2008 operating system, PATROL KM for Microsoft COM+ stops running when the Complustrace file reaches 130 MB.

Table 18 Known issue in PATROL KM for Microsoft Windows Domain Services

Tracking ID Issue

QM001554874 If IPv6 is enabled on the Windows 2008 Server, the View Share Details menu command of the NT_Shares application class shows the IP address in IPv6 format instead of IPv4 format.

Workaround: Disable IPv6 on the server. The following web pages on the Microsoft website provide instructions for disabling IPv6:

http://www.microsoft.com/technet/network/ipv6/ipv6faq.mspx#EBE

http://support.microsoft.com/kb/929852


http://www.microsoft.com/technet/network/ipv6/ipv6faq.mspx#EBE

http://support.microsoft.com/kb/929852

BMC PATROL Wizard for Microsoft Performance Monitor and WMI

BMC PATROL Wizard for Microsoft Performance Monitor and WMI

The PATROL Wizard for Microsoft Performance Manager and WMI creates new PATROL parameters based on Microsoft Performance Monitor (PM) counters or Windows Management Instrumentation (WMI) data.

What’s new in PATROL Wizard for Microsoft PM and WMI 2.1.20

This section describes the new features in version 2.1.20 of the BMC PATROL Wizard for Microsoft PM and WMI product.

Enhanced monitoring of 64-bit counters

The product enables you to execute the WQL queries for 64-bit counters and monitor the counters by using the wizard. You can verify whether the system on which the application is running is 32-bit or 64-bit, and correspondingly connect to a 32-bit or 64-bit WMI provider.

The product has added the following fields to the WMI Wizard dialog box to handle valid queries for WMI classes that begin with Win32_PerfRawData:

■ Formatted Data check box

■ Scaling Factor text box

For more information about the fields in the wizard, see the PATROL for Microsoft PM and WMI online Help.

NOTE You can select these check boxes only for Win32_PerfRawData WMI classes.


What’s new in PATROL Wizard for Microsoft PM and WMI 2.1.20

Performance counters supported through the Win32_PerfRawData WMI class

The Win32_PerfRawData WMI class supports the following performance counters:

■ PERF_COUNTER_COUNTER■ PERF_COUNTER_BULK_COUNT■ PERF_COUNTER_LARGE_RAWCOUNT |

PERF_COUNTER_LARGE_RAWCOUNT_HEX■ PERF_COUNTER_RAWCOUNT_HEX | PERF_COUNTER_RAWCOUNT■ PERF_100NSEC_TIMER■ PERF_100NSEC_TIMER_INV■ PERF_ELAPSED_TIME■ PERF_PRECISION_100NS_TIMER■ PERF_COUNTER_100NS_QUEUELEN_TYPE

New pconfig variable

By default, the PCTWmiQuery.xpc application connects a 64-bit Windows operating system to a 64-bit WMI provider. If an application only has a 32-bit performance counter that can be accessed using a 32-bit WMI provider, then it cannot be monitored on a 64-bit Windows operating system.

The product adds a new pconfig variable, /Perfmon/NT_WMI/ConnectAs32Bit that enables you to connect a 64-bit Windows environment to a 32-bit WMI provider. By default, this pconfig variable is not present at the time of installation. To connect a 64-bit Windows environment to a 32-bit WMI provider, you need to manually add the /Perfmon/NT_WMI/ConnectAs32Bit variable by using the pconfig tool and set the value of the variable to 1.


Known issue in PATROL Wizard for Microsoft PM and WMI 2.1.20

New menu command

The product has also added a new menu command, Configure XPC Trace, to enable a PCTWmiQuery.xpc trace. To access this menu command, right-clickWMI Wizard => KM Commands => PATROL Admin => Configure XPC Trace.An xpcwmi_dbg debug file is created in BMC Software\Patrol3\tmp.

Known issue in PATROL Wizard for Microsoft PM and WMI 2.1.20

Table 19 describes the issue that remains open in PATROL Wizard for Microsoft PM and WMI.

BMC PATROL Cluster Configuration WizardVersion 1.5.20 of the PATROL Cluster Configuration Wizard provides an easy-to-use interface with which you can configure the PATROL Agent for failover in a Microsoft Cluster Server environment. While guiding you through the process, the wizard collects the required configuration data and updates the system environment to integrate the PATROL Agent into the cluster.

Corrected problem in PATROL Cluster Configuration Wizard 1.5.20

Table 20 describes the problem that was reported in earlier releases of PATROL Cluster Configuration Wizard and has been addressed in this release.

Table 19 Known issue in PATROL Wizard for Microsoft PM and WMI

Tracking ID Issue

QM000356110 The KM is unable to monitor performance counters if multiple instances have the same name.

Table 20 Corrected problem in PATROL Cluster Configuration Wizard


QM001560035 The product stopped responding if the cluster node had a service installed that contained more than 100 characters in its name.


BMC PATROL KM for UNIX

BMC PATROL KM for UNIXThis section provides information about new features, corrected problems, and known issues in version 9.9.00 of the BMC PATROL KM for UNIX product.

What’s new in BMC PATROL KM for UNIX 9.9.00

This section describes the new features in version 9.9.00 of BMC PATROL KM for UNIX.

New KM hierarchy

The UNIX OS application hierarchy contains a new container, STORAGE, which represents the STORAGE application. This application does not possess any parameters. It acts as a container for the following applications:

■ DISK■ FILESYSTEM■ SWAP■ ZPOOL

Support for monitoring of kernel-based virtual machines

With PATROL KM for UNIX version 9.9.00, you can monitor KVMs (kernel-based virtual machines). KVM is a full virtualization solution for Red Hat Enterprise Linux on x86, x86-64 hardware containing virtualization extensions (Intel VT or AMD-V). Using KVM, you can run multiple virtual machines on which a Linux or Windows operating system is installed. Each virtual machine has its private virtualized hardware such as network card, disk, and graphics adapter.

PATROL KM for UNIX monitors the configuration statistics, such as virtual CPU and memory assigned to the virtual machine, and other statistics such as CPU and disk utilization of the virtual machine. PATROL KM for UNIX uses both the BMC PATROL Perform Collector (for most of the application classes) and the XPC-based collection method (for the LVIRT application class) to monitor these statistics in the KVM environment.

NOTE For more information about the enhancements in this release of the product, see the BMC PATROL KM for UNIX online Help and the BMC PATROL Knowledge Module User Guide for UNIX.



Support for ZFS filesystem

With this release, PATROL KM for UNIX enables you to monitor ZFS filesystems on Solaris platforms. A ZFS filesystem is created on top of existing storage pools (ZPOOLs). Multiple ZFS filesystems can be created on top of one ZPOOL. These filesystems share that ZPOOL. Therefore, each ZFS filesystem can grow dynamically to the maximum size of the ZPOOL.

You can monitor the statistics of a ZFS filesystem by using the following parameters:

■ ZFSProperties ■ ZFSReservationUsedPerc ■ ZFSSnapshots ■ ZFSSpaceUsedbyDataset ■ ZFSSpaceUsedBySnapshots

For a global zone, the ZFS filesystem instances appear under the FILESYSTEM container of the ZPOOL instance on which the ZFS filesystem is created.

For a non-global zone, the ZFS root filesystem and the ZFS filesystem instances that are added using the add fs subcommand of the zonecfg command appear under the FILESYSTEM container of the STORAGE container.

For a non-global zone, ZFS filesystem instances that are added using the add dataset subcommand of the of the zonecfg command appear under the ZPOOL instance on which the ZFS filesystem is created.

For remote hosts that support ZFS filesystems, ZFS filesystem instances appear under the STORAGE container irrespective of the global zone and non-global zone.

Support for extended CPU and memory monitoring of VMware virtual machines

This release supports VMware parameters that enable you to monitor CPU and memory statistics of a VMware virtual (guest) machine when PATROL KM for UNIX is running on that machine. For information about these parameters, see CPU and MEMORY application class parameters in Table 21 on page 33.

NOTE Inside KVM guests, data collection by BMC PATROL Perform Collector is not supported. The PSL data collection method is used to collect data for KVM guests.



New application class

This release supports a new application class, LVIRT. This application class contains the following parameters that enable you to monitor the attributes and statistics of Red Hat Linux KVM hypervisor-based virtual machines. This statistical information is classified into configuration, utilization, and state statistics.

■ LVIRTConfiguration■ LVIRTCpuUtilization■ LVIRTState

The LVIRT application class is represented by the LINUX_VIRTUALIZATION container in the PATROL console hierarchy. An instance for each KVM-based virtual machine is created with the virtual machine name under this container.



New parameters

This release supports the new parameters listed in Table 21:

Table 21 New parameters in BMC PATROL KM for UNIX (part 1 of 4)

Application class Parameters Description

CPU CPUVMCpuUtilab Displays the current load of the virtual machine’s virtual processor

CPUVMLimitab Displays the maximum processing power in GHz allowed to a virtual machine. Assigning a CPU limit ensures that a virtual machine never consumes more than a certain amount of the available processor power. By limiting the amount of processing power consumed, a portion of the processing power becomes available to other virtual machines.

CPUVMReservationab Displays the minimum processing power in GHz available to a virtual machine. Assigning a CPU reservation ensures that even as other virtual machines on the same host consume shared processing power, a certain minimum amount is still available for this virtual machine.

DCM LVIRTColl Collects the following information about the KVM hypervisor-based virtual machines:

■ Configuration information such as the number of virtual CPUs and memory assigned

■ State■ CPU utilization■ ID■ UUID

LVIRTDiskColl Collects the following information about the disks that are attached to the hypervisor-based virtual machines:

■ Number of bytes read per second ■ Number of bytes written per second

LVIRTNetColl Collects the following information about the network interfaces attached to the KVM hypervisor-based virtual machines:

■ Number of incoming packets ■ Number of outgoing packets■ Total byte rate ■ Percentage of incoming packets that contain packet

format errors ■ Percentage of outgoing packets that contain packet

format errors

DCM

COLLECTORS

VMGuestColl Collects the data of the CPU and MEMORY parameters for the Linux guest machine on the VMware host. This collector uses the pukvm.xpc process to collect data.



DISK DSKIORate Displays the total IO rate of the disk. The value of this parameter is derived from the DSKReadWrite parameter. The _Total instance displays the sum of the IO rate of all the disks on the system.

FILESYSTEM ZFSProperties Displays the following properties of a ZFS filesystem:

■ version: Version of the filesystem

■ compressratio: Compression ratio achieved

■ quota: The maximum space that the filesystem can consume

■ refreservation: The minimum space guaranteed to the filesystem

■ refquota: The maximum space that a dataset can consume

■ reservation: The minimum space guaranteed to a dataset and its descendents

■ compression: Controls the compression algorithm used for this dataset. Compression can be turned on by running zfs set compression=on dataset. The default value is off. The compression ratio achieved for the dataset is expressed as a multiplier.

■ usedbyrefreservation: The space used by a refreservation set on a dataset that would be freed if the refreservation was removed.

ZFSReservationUsedPerc Displays the percentage of reservation used by a ZFS dataset

ZFSSnapshots Displays all snapshots for a particular ZFS filesystem and the details about the space being used by the snapshots

ZFSSpaceUsedbyDataset Displays the space used by a ZFS dataset

ZFSSpaceUsedBySnapshots Displays the space consumed by the snapshots that belong to a ZFS dataset

LVIRT LVIRTCpuUtilization Displays the normalized percentage CPU utilization of a virtual machine





LVIRT LVIRTConfiguration Displays the configuration statistics of a virtual machine such as maximum available memory and number of virtual CPUs assigned to the virtual machine

LVIRTState Displays the state of a virtual machine. It can have one of the following values:

■ 0 (Undefined)■ 1 (Running) ■ 2 (Blocked)■ 3 (Paused)■ 4 (Shutting Down)■ 5 (ShutOff)■ 6 (Crashed)

MEMORY MEMVMActiveab Displays the estimated amount of memory the virtual machine is actively using

MEMVMBalloonedab Displays the amount of memory that has been reclaimed from a virtual machine through the VMware memory balloon mechanism

MEMVMLimitab Displays the maximum amount of memory that is allowed to a virtual machine. Assigning a memory limit ensures that a virtual machine never consumes more than a certain amount of the allowed memory. By limiting the amount of memory consumed, a portion of this shared resource is allowed to other virtual machines.

MEMVMMappedab Displays the mapped memory size of a virtual machine. This is the current total amount of guest memory that is backed by physical memory.

Note: This mapped memory size may include pages of memory shared between multiple virtual machines and therefore, may be an overestimate of the amount of physical host memory consumed by this virtual machine.

MEMVMOverheadab Displays the amount of overhead memory associated with a virtual machine that is consumed on the host computer

MEMVMReservationab Displays the minimum amount of memory that is guaranteed to a virtual machine. Assigning a memory reservation ensures that even as other virtual machines on the same host consume memory, a certain minimum amount is still available for this virtual machine.




Corrected problems in BMC PATROL KM for UNIX 9.9.00

Corrected problems in BMC PATROL KM for UNIX 9.9.00

Table 22 describes the problems that were reported in earlier releases of BMC PATROL KM for UNIX and have been corrected in this release.

MEMORY MEMVMSharedab Displays the amount of physical memory associated with a virtual machine that is copy-on-write (COW) shared on the host

MEMVMSharedSavedab Displays the estimated amount of physical memory on the host saved from COW shared guest physical memory

MEMVMSwappedab Displays the amount of memory associated with a virtual machine that has been swapped by ESX

MEMVMUsedab Displays the estimated amount of physical host memory currently consumed for a virtual machine's physical memory.

This memory is calculated as follows:

(Memory Mapped in MB) - (Memory Shared Saved in MB)

NETWORK NETBytesTotalPerSec Displays the total number of received and transmitted bytes per second in the last interval

UNIX_OS _SystemConfig Collects and displays configuration information such as processor details, hardware serial number, number of network interfaces, and pagesize of the host computer

a This parameter will not be available for the remote host.b This parameter will be available only if VMware tools are installed on the Linux virtual machine (guest

machine).

Table 22 Corrected problems in BMC PATROL KM for UNIX (part 1 of 2)


QM001637160 On Solaris 10 global zones, the annotation of the CPUCpuUtil parameter did not show the processes that were running inside a non-global zone.

QM001659480 On Solaris 10 global zones, the KM sometimes reported an incorrect value for the ZONEPhyCpuUtil parameter.




Known issues in BMC PATROL KM for UNIX 9.9.00

Known issues in BMC PATROL KM for UNIX 9.9.00

Table 23 describes issues that remain open in BMC PATROL KM for UNIX. If a tracking ID has been assigned, it is provided.

QM001671656 For a filesystem that was excluded from monitoring, the PATROL Agent generated a type 41 event with the following message for every collection cycle:

DFColl: df now returns data for filesystemName

QM001678274 The System Output Window displayed the following error message while monitoring a Solaris non-global zone and one data point was lost in the PSL collection mode:

VMColl: expected 4 lines, got 5: Exiting

Table 23 Known issues in BMC PATROL KM for UNIX (part 1 of 2)

Tracking ID Issue

none Inside the AIX 6.1 System WPAR, if vmstat -v reports large values for file pages and you restart BMC PATROL Agent, the following parameters of the MEMORY application class remain offline:

■ MEMAppUsablePerc■ MEMUsedBufCache

This happens because the values reported by vmstat -v are out of range.

If BMC PATROL Agent collects data properly and vmstat -v reports large values in the next collection, data collection for the preceding MEMORY parameters stops.

QM001565496 While configuring DS deployment, there is no window available in which you can select or clear the solaris.ldoms.read authorization for the control domain. However, the check box to grant you this authorization is enabled by default. Hence, you are granted the authorization even if the window is not displayed during the installation process.

QM001606431 On the global zone, DCM crashes if a non-global zone is restarted. However, you do not observe the crash on the computer running on the Solaris 10 (x86) platform. DCM is started in the next collection cycle and further data collection is not affected.

Table 22 Corrected problems in BMC PATROL KM for UNIX (part 2 of 2)



BMC PATROL KM for Log Management

BMC PATROL KM for Log ManagementThe BMC PATROL KM for Log Management product provides the statistics for text, script, binary, named pipe, and XML files in your environment.

What’s new in BMC PATROL KM for Log Management 2.6.10

BMC PATROL KM for Log Management has been enhanced with the following changes and new features.

QM001654664 If you select Perform Data Collector as a default configuration for installation, installation fails at 100% on Solaris non-global zones. You receive the following error message in the installation log:

Unable to execute script [root@/opt/patqa1/PUK9800/Patrol3/b1config7500.sh -T -D /opt/patqa1/PUK9800/Patrol3/] for product [pagcolb1_top].

QM001678603 If you select Perform Data Collector as a default configuration for installation, installation fails at 100% on SUSE Linux Enterprise Server 11, Itanium platform.

Workaround:

Go to the Patrol3 directory and run the following scripts:

1. ./bpaagent_si.sh (as BMC PATROL user)

2. ./b1config7510.sh (as root)

QM001654732 If the REMOTE_HOST and the monitored host are in different Japanese locales, some of the Japanese characters in the Remote Monitoring instance InfoBox are displayed as garbled text.

NOTE For more information about this product, see the BMC PATROL KM for Log Management online Help and the BMC PATROL Knowledge Module for Log Management User Guide.

Table 23 Known issues in BMC PATROL KM for UNIX (part 2 of 2)

Tracking ID Issue


What’s new in BMC PATROL KM for Log Management 2.6.10

Changes in the Configure Search Criteria: instanceName dialog box

With this release, the functionality of the Configure Search Criteria: instanceName dialog box is divided into the following dialog boxes:

■ Configure Search Criteria: instanceName: Define Search Criterion—Enables you to configure an individual search pattern while adding an instance. You can also modify the individual search criterion using this dialog box after you have added an instance.

■ Configure Search Criteria: instanceName: Override Default Settings—Enables you to override the default search criterion settings for an instance.

■ Configure Search Criteria: instanceName: Summary—Lists a summary of search criteria defined for an instance using search identifiers. You can use this dialog box to add, modify, or delete a search criterion for the instance.

Configuring text and XML instances using the Configure Search Criteria: instanceName: Define Search Criterion dialog box

With this release, you can define search criterion for a text or XML instance by using the Configure Search Criteria: instanceName: Define Search Criterion dialog box. You can specify the XML search string in the String1 text box of this dialog box.

Configuring instances for multiple search patterns

PATROL KM for Log Management now allows you to configure a text or XML instance to search for multiple patterns in a log file for a particular number of polling cycles. Each search pattern should be a valid regular expression. For example, you can search for multiple patterns such as {Job Started} {Job Stopped} {Job Aborted}.

PATROL searches for each pattern in the log file in the order in which you specify the patterns. These patterns are searched for a particular number of polling intervals. If all the search patterns are not found in the specified polling intervals, the KM generates an alarm.

NOTE The XML Search String text box is no longer available in the Configure Search Criteria: instanceName: Define Search Criterion dialog box.


Corrected problems in BMC PATROL KM for Log Management 2.6.10

You can specify multiple search patterns in the String1 text box of the Configure Search Criteria: instanceName: Define Search Criterion dialog box. You can specify the number of polling cycles to search for these patterns in the Generate ALARM when pattern not found within..Polling Intervals text box of the Configure Search Criteria: instanceName: Override Default Settings dialog box.

New pconfig variable

PATROL KM for Log Management supports a new pconfig variable, suppressSpaceInMsg. This variable enables you to suppress multiple consecutive spaces in a custom event message. This variable can have the following values:

■ 1: Suppresses multiple consecutive spaces and considers them as a single delimiter

■ 0 (default): Does not suppress multiple consecutive spaces and considers them as multiple delimiters

Corrected problems in BMC PATROL KM for Log Management 2.6.10

Table 24 describes the problems that were reported in earlier releases of BMC PATROL KM for Log Management and have been corrected in this release.

NOTE ■ BMC does not recommend entering a single search pattern. The KM might not generate

any alarm in this case.

■ BMC does not recommend entering multiple search patterns in the String1 text box and selecting the option to read a log file from the beginning simultaneously.

Table 24 Corrected problems in BMC PATROL KM for Log Management (part 1 of 2)


QM001653458 The KM raised a false alarm for an old file when rolling of new a file and inactivity of an old file happened at the same time in a scheduled log scan.

QM001664632 When you specified wildcard characters in the path of the log file and multiple files matched the path criterion, only one file instance was discovered.

QM001666999 The KM stopped monitoring a file when only the file size changed and not the timestamp.


BMC PATROL KM for Event Management

BMC PATROL KM for Event ManagementThe BMC PATROL KM for Event Management product provides event notification and centralized alert management features.

What’s new in BMC PATROL KM for Event Management 2.8.10

This section describes the new configuration feature that is added in version 2.8.10 of BMC PATROL KM for Event Management.

Event notification at the end of the event blackout period

You can generate a NOTIFY_EVENT event at the end of the event blackout period reflecting the latest parameter state, when the value of disableNotifyEventOnBlackout pconfig variable is set to 1. By default, the notification will be sent only when the parameter is in a ALARM state at the end of the event blackout period.

QM001667944 The KM returned incorrect output for a custom event message if the message contained multiple consecutive spaces before the specified starting position and the KM considered multiple consecutive spaces as multiple delimiters.

Note: You can use the suppressSpaceInMsg pconfig variable to change the behavior of multiple consecutive spaces. For more information, see “New pconfig variable” on page 40.

QM001673086 When you upgraded to a later version of KM from 2.4.20 or earlier versions, the scheduled log scan did not work for the migrated instances.

QM001676132 The KM could not monitor a log file correctly if you specified the values of the Threshold #1 and Threshold #2 fields in the x:y format, and the values of y were not same for both the fields.

NOTE Install mailx and C shell on your computer to configure BMC PATROL KM for Event Management as a Notification Server. These utilities are not available by default on ESX Servers.

Table 24 Corrected problems in BMC PATROL KM for Log Management (part 2 of 2)




The notifyAfterBlackoutForState pconfig variable can be used to receive notifications for valid parameter state changes. Valid values for the notifyAfterBlackoutForState pconfig variable are OK,WARN,ALARM or, NONE. These values should be separated by a comma. The notifications are sent only for the parameter states included in the notifyAfterBlackoutForState pconfig variable. If the value of the pconfig variable is set as NONE, no notification is received.


This section describes the new configuration features that were added in version 2.7.12 of BMC PATROL KM for Event Management.

Enabling and disabling the NOTIFY_EVENT event during a blackout period

Using the new /AS/EVENTSPRING/disableNotifyEventOnBlackout variable, you can now enable or disable the NOTIFY_EVENT event during a blackout period.

Valid values:

■ 1 = does not trigger NOTIFY_EVENT during a blackout period■ 0 = triggers NOTIFY_EVENT during a blackout period

What’s changed in BMC PATROL KM for Event Management 2.7.10

This section describes the configuration changes that were made in version 2.7.10 of BMC PATROL KM for Event Management.

Specify how many events are sent after a blackout ends

Using the new /AS/EVENTSPRING/disableMultiPostBlackoutNotify variable, you can choose to:

■ receive events for all of the alerts that occurred for a parameter in an alarm state during blackout

NOTE For multiple parameter state changes during the event blackout period, only one notification event is sent at the end of the event blackout period. All other parameter state changes are ignored.



■ receive only the last event generated during blackout if the parameter is still in alarm when the blackout period ends

The following are valid values for this variable:

■ 1 = one event for multiple alerts■ any value other than 1 = multiple events for multiple alerts (default)

Specify how many notifications are sent when reconfiguring remote agents

By default, when you reconfigure the remote agents, notification for all the objects is enabled. If you set the new /AS/EVENTSPRING/enableGlobalArsAction variable to 0, notifications are not sent for all the objects. You can then configure the remote agent and notification server.

■ 0 = notifications are not sent for all objects■ any value other than 0 = notifications are sent for all objects

Support for wildcards in hostname

To specify the user name and password of the system you want to monitor, you can create the following rule:

/AS/EVENTSPRING/AVAILABILITY/HostName/checkerAccount.defaultAccount REPLACE username/password

Wildcard support is now available for the host name in this variable or rule, which reduces the number of rules you have to create. When you use the checker account rule, the KM behaves as follows:

1. Searches for and uses the value of a host-specific rule, if one exists.

2. If no host-specific rule exists, the KM processes rules with wildcards.

A. If the /AS/EVENTSPRING/processWildcards rule exists with a value of 1, the KM makes a list of the hosts with the designated wildcard string {re:*} in them. The KM then compares the hosts that match the wildcard with the existing Availability host names (targets), and if there is a match, it returns that value.

B. If the KM does not find a match and the /AS/EVENTSPRING/processWildcards rule exists with a value of 0 or does not exist, the KM returns the default checker account value.

3. If the default checker account rule does not exist, it checks for the /AS/EVENTSPRING/AVAILABILITY/checkerAccount rule.



4. If the /AS/EVENTSPRING/AVAILABILITY/checkerAccount rule does not exist, the KM uses the Eventspring_Availability_Check bogus account.

The first time this variable is used, the wild card search takes more time than during subsequent uses because the host names are cached in a namespace variable. If you want to refresh the host list cache, set the following variable to 1:/AS/EVENTSPRING/AVAILABILITY/hostWildcardListUpdated

Observe the following rules when creating wildcards:

■ use the following format for wildcards: .../abc{re:*}/...■ avoid using wildcard rules that conflict: ..../abc{re:*}/... and /bc{re:*}/...

The KM uses a reverse sort on the wildcard rules, and the first rule that matches sort parameters is selected. This behavior is exactly the same as the current wildcard implementation in the Event Management KM.

For more information about using wildcards, see the BMC PATROL Knowledge Module for Event Management User Guide.


This section describes the configuration changes that were made in version 2.7.09 of BMC PATROL KM for Event Management.

AgentPingFailure and HostPingFailure parameters independent of each other

You can configure whether the AgentPingFailure and HostPingFailure parameters work dependently or independently of each other by setting the /AS/EVENTSPRING/AVAILABILITY/ignoreOSPingStatus agent configuration variable to one of the following values:

■ 1 = Parameters work independently of each other (that is, the BMC PATROL Agent ping works even if the host ping fails).

■ 0 (zero) = Parameters depend on each other (that is, the BMC PATROL Agent ping fails if the host ping fails). This behavior is the default.


Corrected problem in BMC PATROL KM for Event Management 2.8.10

Enabling and disabling the recovery action during blackout periods

You can enable or disable recovery actions during blackout periods by setting the /AS/EVENTSPRING/applyBlackoutToRA agent configuration variable to one of the following values:

■ 1 = No recovery actions are performed.■ 0 (zero) = Recovery actions are performed (default behavior).

In earlier versions, by default the recovery actions were performed during the blackout periods.

Host specific checker account for monitored systems

You can specify a host-specific user name and password for each monitored system in the checker account. To specify the user name and password of the system that you want to monitor, create the following rule: /AS/EVENTSPRING/AVAILABILITY/hostname/checkerAccount.defaultAccount REPLACE username/password

This feature functions in the following ways:

■ You can have multiple entries for the configuration variable, one entry for each host.

■ You can also use the default behavior of checkerAccount.defaultAccount without specifying the host name. For more information, see the BMC PATROL Knowledge Module for Event Management User Guide.

■ If you do not have a host-specific entry, the user name and password specified for /AS/EVENTSPRING/AVAILABILITY/checkerAccount.defaultAccount will be used. If this entry is also missing, the dummy account will be used.

Corrected problem in BMC PATROL KM for Event Management 2.8.10

Table 25 describes a problem that was reported in earlier releases of BMC PATROL KM for Event Management and has been corrected in this release.

NOTE The hostname variable is case-sensitive. It should match the host name of the system added for monitoring.


Known issues in BMC PATROL KM for Event Management 2.8.10

Known issues in BMC PATROL KM for Event Management 2.8.10

Table 26 describes issues that remain open in BMC PATROL KM for Event Management.

Wildcards in rules require increase in PSL instructions limit

When you use wildcard expressions that match a large number of instances, CPU utilization is high. This condition occurs because BMC PATROL KM for Event Management must process every rule for every instance to determine whether the rule’s wildcard expression is matched by each instance.

In BMC PATROL installations with many instances, the following message is displayed in the standard output window:

PatrolAgent-W-EUSER: PSL script `RefreshParamSettings', 'Event Management', 'EVENTSPRING' may be in an infinite loop - executed 500000 instructions

Table 25 Corrected problem in BMC PATROL KM for Event Management


QM001648224 By default, the KM Notification command on the UNIX Notification server contained a plain text password for ftp that was not required for the default functioning of the Notification server.

Table 26 Known issues in BMC PATROL KM for Event Management

Tracking ID Issue

QM000522174 When rules containing wildcards are applied to an agent that contains the default value of the /AgentSetup/AgentTuning/ pslInstructionMax agent configuration variable, BMC PATROL displays a warning message to the system output window.

For more information about this issue, see “Wildcards in rules require increase in PSL instructions limit” on page 46.

QM000420571 When you log on by using the Checker Account, if both the user name and password fields are left blank, you get the following error message:

AvailabilityMonitorColl, Line# 140: remote_open: error in authenticating remote session (<hostname>,<port_number>).

PSL function <remote_open> failed.


BMC PATROL KM for History Loader

To prevent this warning message, set the /AgentSetup/AgentTuning/pslInstructionMax configuration variable to 500000000 (five hundred million). For more information, see the BMC PATROL Agent Reference Manual.

BMC PATROL KM for History LoaderVersion 1.5.20 of the BMC PATROL History Loader KM product extracts and loads PATROL parameter history into your relational database management system (RDBMS). After the PATROL history data is stored in an RDBMS, you can perform complex analysis on all monitored hosts and use the data for statistical planning.

Corrected problem in BMC PATROL History Loader KM 1.5.20

Table 27 describes a problem that was reported in earlier releases of BMC PATROL History Loader KM and has been corrected in this release.

Known issue in BMC PATROL KM for History Loader 1.5.20

Table 28 describes an issue that remains open in BMC PATROL KM for History Loader.

Table 27 Corrected problem in BMC PATROL History Loader KM


QM001654359 BMC PATROL History Loader KM truncated instance names to 32 characters.

Table 28 known issues in BMC PATROL KM for History Loader

Tracking ID Issue

QM001642456 BMC PATROL KM for History Loader does not support Microsoft Windows SQL 2005 or later as a database because it does not support the interactive SQL utility. The BMC PATROL KM for History Loader uses the interactive SQL binary for creating tables.


BMC PATROL Agent

BMC PATROL AgentPATROL Agent is the main monitoring component for the PATROL architecture.

Compatibility with PATROL Security

Versions 3.8.50 of the PATROL Agent uses version 3.0.14 of the PATROL Security libraries and utilities. To prevent conflicts with PATROL components that are using earlier versions of PATROL Security, the binary files, policy files, and log files associated with PATROL Security 3.0.14 are located in separate folders with _v3.0 appended to the folder name.

For more information, see PATROL Security Release Notes, version 3.0.14.

Support for the User Account Control (UAC)

If all of the following conditions are true, and you are running a Microsoft Windows Vista or Microsoft Windows Server 2008 operating system, the PATROL Agent channel from which the external command is fired is blocked:

■ The PSL channel trying to launch any external binary will be in an IOWAIT state if the owner of the channel does not belong to the Administrator’s group and that external binary is manifested with the require Administrator token into it.

■ UAC is enabled.

These channels are displayed in an IOWAIT state. To get the SOW to its normal state, enter the exit command in SOW. This is applicable for all the PSL functions available for launching the external binary, such as open, system, PslExecute, execute, and so on.

Unsupported PSL format options

The convert_locale_date( ) PSL function does not generate output for the following format options:

■ ‘%Od, %Oe, %OH, %OI, %Om, %OM, %OS, %OU, %Ow, %OW, and %Oy’ on UNIX, Linux, and Microsoft Windows operating systems

■ ‘%Ec, %Ex, and %EX’ on UNIX, Linux, and Microsoft Windows operating systems

■ ‘%U’ on the Microsoft Windows operating system


What’s new in PATROL Agent 3.8.50


PATROL Agent has been enhanced with the following new features and changes.


PATROL Agent now supports the following operating systems:

■ Red Hat Enterprise Linux 5.5 (x86, x86-64, zSeries, Itanium 64)■ Oracle Enterprise Linux 5.5 (x86, x86-64)

64-bit binary support

With this release, PATROL Agent supports 64-bit binary on the following platforms:

■ Red Hat Enterprise Linux (x86-64, Itanium 64, zSeries)■ Oracle Enterprise Linux (x86-64)■ Solaris (Sparc 64-bit, x86-64)■ SUSE Linux Enterprise Server (x86-64, zSeries, Itanium 64)

Automatic registration with the Integration Service

With the automatic registration of PATROL Agent with the Integration Service feature, PATROL Agent can connect to the Integration Service, register itself, and start sending its performance data to the Integration Service.

For more information about automatic registration with the Integration Service and its configuration, see the PATROL Agent Reference Manual.

NOTE PATROL Agent does not support User Datagram Protocol (UDP) protocol communication with the Integration Service.



Suppress events

You can now suppress the restricted PATROL EVENT classes at the PATROL Agent level:

■ Event class "7" - login OK■ Event class "28" - login invalid■ Event class "RemPsl" - launch remote PSL execution■ Event class "Result" - return result of remote PSL execution■ Event class "39" - value of parameter not in range■ Event class "11" - value of parameter is in alarm zone■ Event class "9" - alarm has been cancelled■ Event class "40" - response event

For more information, see the PATROL Agent Reference Manual.

Substitute event text

You can use the SUBSTITUTE event rule to modify the description of the PATROL Agent events that are in context of your environment and more meaningful.

For more information, see the PATROL Agent Reference Manual.

Dropped platform support

With this release, PATROL Agent discontinues the support for the Linux kernel 2 major release and 4 minor release on x86 platform.

Installation changes

A new screen has been added to the PATROL Agent installation process. In this screen, you will be prompted to enter the Integration Service connection string which the PATROL Agent needs to connect to. For more information, see the PATROL Agent Reference Manual.

NOTE If you suppress any of the preceding events, none of the events will be generated and no event actions will be executed. Only range evaluation will take place and recovery events will be generated.


Internationalization and localization

Installation considerations

If you are installing PATROL Agent 3.8.50 on a computer where PATROL Console for UNIX is already installed, follow these guidelines:

■ Install PATROL Agent in a different directory than that of PATROL Console for UNIX installation directory.

■ Select Yes for the Security Override option while installing PATROL Agent.

If you are installing PATROL Console for UNIX on a computer where PATROL Agent 3.8.50 is already installed, follow these guidelines:

■ Install PATROL Console for UNIX in a different directory than that of PATROL Agent installation directory.

■ Select No for the Security Override option while installing PATROL Console for UNIX.

Internationalization and localization

PATROL Agent supports the following non-English locales on Windows and UNIX platforms:

■ Simplified Chinese (GBK, EUC-CN, GB18030, CP936)

■ Japanese (EUC-JP, SJIS, PCK, CP932)

■ Korean (EUC-KR, CP949)

■ Traditional Chinese (EUC-TW, BIG5, CP950)

On UNIX platforms, PATROL Agent is not supported in UTF-8 locales (for example, ja_JP.UTF-8).

If PATROL Agent is started in any other non-English operating system locales, PATROL Agent ignores the operating system locale setting and runs in default English C locale.

To check the PATROL Agent current locale, view the PATROL Agent error log file in the $PATROL_HOME\log directory.

NOTE After installing the product, use the patrolrc.sh scripts installed in the respective directory to set the $PATROL_HOME path.


Known issues and workarounds in PATROL Agent 3.8.50

Known issues and workarounds in PATROL Agent 3.8.50

Table 29 describes the issues that remain open and workarounds (if any) in PATROL Agent.

Download and installation informationThis section contains installation information that supplements or supersedes the information in the BMC PATROL for Microsoft Windows Servers Getting Started and the BMC PATROL for UNIX and Linux Getting Started.

How to obtain the solution

BMC Performance Manager for Servers is available for download from the BMC EPD website at http://webapps.bmc.com/epd. The Read This First document available on this website provides details on how to download the solution and the documentation.

Table 29 Known issues in PATROL Agent 3.8.50

Tracking ID Issue

QM001622825 On AIX 6.1, PATROL Agent does not support the Native Loadable Password algorithms (such as smd5, ssah1, ssah256, ssah512, and blowfish authentication algorithms).

Workaround: If you want to use smd5, ssha1, ssha256, ssha512, and blowfish authentication algorithms on AIX 6.1, the PATROL Agent default account user needs to be part of the “security” group.

QM001542120 When you uninstall the PATROL Agent using the Distribution Server in a Microsoft Windows Vista or Microsoft Windows Server 2008 environment, the PATROL Agent entry is not removed from the firewall exception list.

QM001534196 On a PATROL Central Operator – Microsoft Windows Edition console, the tooltip and the Property dialog box display an incorrect Microsoft Windows Vista or Microsoft Windows Server 2008 operating system for the managed system.

QM000492062 If you are installing the PATROL Agent over the top of an existing installation, any manual modifications that you made to the agent.plc file (on UNIX and Linux) or the agent.reg file (on Windows) are not applied to the new installation.

Workaround: You must manually reapply the modifications after the new installation.



Prerequisites for installing PATROL for Microsoft Windows Servers and PATROL for UNIX and Linux

To use EPD, you must be registered on the BMC Customer Support website. Registration requires your company’s support contract ID and password.

If you do not have a current license for the product, contact your BMC sales representative or your local BMC office or agent. If you cannot download the product, you can request a physical kit.


This topic describes requirements for the PATROL for Microsoft Windows Servers and PATROL for UNIX and Linux solutions.

Turn off pop-up blocking software before installing

Before installing the PATROL for Microsoft Windows Servers solution or PATROL for UNIX and Linux solution or any of their components, you must turn off pop-up blocking software. Pop-up blocking software interferes with the functioning of the installation utility.

Installing BMC PATROL Agent on top of an existing installation

If you are installing BMC PATROL Agent on top of an existing installation on Solaris (Sparc, x86-64), Linux (x86-64, zSeries, Itanium 64), or SUSE (x86-64, zSeries, Itanium 64), the installation process does not remove the old binaries. The installation process creates a new 64-bit directory and all the 64-bit binaries are placed in the this directory. When PATROL Agent starts, the value of the PATROL_HOME variable is set to the 64-bit directory path, which is a valid installation directory. For example, on Solaris, x86-64, the new PATROL_HOME path will be: /opt/patrol/Patrol3/Solaris210-x86-64.

NOTE The Help files can be installed only on platforms that are supported by the console or the console server

NOTE Any customization done to invoke the 32-bit PATROL Agent is not supported after upgrading to the 64-bit PATROL Agent.



If you are installing the BMC PATROL Agent on top of an existing installation on a UNIX platform, the installation process moves the old installation config and log directories to the following path: BMC base installation directory/Patrol3/. Also, the soft-link points from $PATROL_HOME/log and $PATROL_HOME/config to BMC base installation directory/Patrol3/config and BMC base installation directory/Patrol3/log.

You cannot install 64-bit PATROL Agent with 32-bit KM. Also, if you upgrade from 32-bit PATROL Agent to 64-bit PATROL Agent, you need to upgrade to 64-bit version of PATROL KM for UNIX (version 9.9.00).

While installing BMC PATROL Agent on top of an existing installation, any manual modifications that you made to the agent.plc file (on UNIX and Linux) or the agent.reg file (on Windows) are not applied to the new installation. You must manually reapply the modifications after the new installation.

Unsupported platform option in the installation utility user interface

If you use the installation utility to build an installable image, the Windows NT 4.0 (Intel) platform option is also displayed in the Select Platforms dialog box. This platform is not supported by the PATROL for Microsoft Windows Servers 4.3.00 solution.

WARNING Do not select the Windows NT 4.0 (Intel) platform when building an installable image.


Related information

Related informationTable 30 describes the documents that support this solution and are available in PDF format from the Customer Support page of the BMC website, from the documentation CD provided with the BMC Performance Manager for Servers kit, and from the PATROL for Servers - Documentation (Windows) and PATROL for Servers - Documentation (Windows) links on the EPD download page for the solution.

Table 30 Solution documents (part 1 of 2)

Document Description

PATROL for Microsoft Windows Servers Getting Started

Provides the necessary information and instructions for installing and configuring the PATROL for Microsoft Windows Servers solution, and additional installation and configuration information for the following components:

■ PATROL KM for Microsoft Windows■ PATROL KM for Microsoft Windows Active Directory■ PATROL KM for Microsoft Windows Domain Services■ PATROL KM for Microsoft Cluster Server■ PATROL Cluster Configuration Wizard■ PATROL KM for Microsoft Message Queue■ PATROL KM for Microsoft COM+■ PATROL KM for Log Management■ PATROL Wizard for Microsoft Performance Monitor and WMI■ PATROL History Loader KM■ PATROL Adapter for Microsoft Office

BMC PATROL for UNIX and Linux Getting Started

Provides the necessary information and instructions for installing and configuring the PATROL for UNIX and Linux solution

BMC PATROL Knowledge Module for UNIX User Guide

Provides menus, commands, and parameter information for the PATROL KM for UNIX. This document describes how to monitor AIX, HP, Linux, and Solaris virtualization, data collection, CPU, kernel, disks, file systems, system health, memory, processes, users, print, workload partitions, logical domains, and so on.

Installation Utility Reference Manual Provides information about the installation utility

Installation Utility Release Notes Provides information about what’s changed and what’s new for the installation utility

PATROL Adapter for Microsoft Office User Guide

Provides information about how to configure and use PATROL Adapter for Microsoft Office

PATROL Agent Reference Manual Provides detailed information about PATROL Agent and information about how PATROL Agent interacts with other components

PATROL Application Program Interface Reference Manual

Provides detailed information about PATROL Application Program Interface (API)

PATROL Command Line Interfaces Reference Manual

Provides detailed information about PATROL command line interfaces and PATROL CLI features

PATROL History Loader Knowledge Module User Guide

Provides detailed information about how to configure, install, and use PATROL History Loader KM


Support for BMC Performance Manager for Servers


BMC provides the indicated levels of support for the following solution versions and releases:

For more information about the latest support policies, see the Customer Support website at http://www.bmc.com/support.

If you have problems with or questions about a BMC product, see the Customer Support website at http://www.bmc.com/support. You can view or download product documents, find answers to frequently asked questions, and download products and maintenance. If you do not have access to the web and you are in the United States or Canada, contact Customer Support at 800 537 1813. Outside the United States or Canada, contact your local BMC office or agent.

PATROL Knowledge Module for Event Management User Guide

Provides detailed information about how to install, configure, and use PATROL KM for Event Management

PATROL Knowledge Module for Log Management User Guide

Provides detailed information about how to install, configure, and use PATROL KM for Log Management

PATROL Script Language Reference Manual, Volume 1--PSL Essentials

Provides essential information about the PATROL Script Language (PSL) used to write procedures, parameters, and commands in the PATROL environment

PATROL Script Language Reference Manual, Volume 2--PSL Functions

Provides detailed information about PSL built-in functions

PATROL Script Language Reference Summary

Provides information about PSL data types, operators, statements and functions

PATROL Security User Guide Provides detailed information about PATROL Security

PATROL Security Release Notes Provides information about what’s new and what’s changed in the PATROL Security product

Version Level of support

3.0.00 full

2.9.00 full

2.8.00 full

2.7.x limited

2.6.00 none

Table 30 Solution documents (part 2 of 2)

Document Description





© Copyright 2010 BMC Software, Inc.

BMC, BMC Software, and the BMC Software logo are the exclusive properties of BMC Software, Inc., are registered with the U.S. Patent and Trademark Office, and may be registered or pending registration in other countries. All other BMC trademarks, service marks, and logos may be registered or pending registration in the U.S. or in other countries. All other trademarks or registered trademarks are the property of their respective owners.

AIX, IBM, POWER7, and zSeries are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both.

Linux is the registered trademark of Linus Torvalds.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

UNIX is the registered trademark of The Open Group in the US and other countries.

The information included in this documentation is the proprietary and confidential information of BMC Software, Inc., its affiliates, or licensors. Your use of this information is subject to the terms and conditions of the applicable End User License agreement for the product and to the proprietary and restricted rights notices included in the product documentation.

BMC SOFTWARE INC2101 CITYWEST BLVD, HOUSTON TX 77042-2827, USA• 713 918 8800Customer Support: 800 537 1813 (United States and Canada) or contact your local support center


Documents

BMC PATROL for Servers Release Notes