communities.bmc.com 1 contents chapter 1 bmc proactivenet overview 7 what is bmc proactivenet?. . ....

www.bmc.com

BMC ProactiveNetGetting Started Guide

Supporting

BMC ProactiveNet version 8.5

October 2010

Contacting BMC Software

You can access the BMC Software website at http://www.bmc.com. From this website, you can obtain information about the company, its products, corporate offices, special events, and career opportunities.

United States and Canada

Address BMC SOFTWARE INC2101 CITYWEST BLVDHOUSTON TX 77042-2827 USA

Telephone 713 918 8800 or800 841 2031

Fax 713 918 8000

Outside United States and Canada

Telephone (01) 713 918 8800 Fax (01) 713 918 8000

© 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.

BladeLogic and the BladeLogic logo are the exclusive properties of BladeLogic, Inc. The BladeLogic trademark is registered with the U.S. Patent and Trademark Office, and may be registered or pending registration in other countries. All other BladeLogic 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 is the trademark or registered trademark of International Business Machines Corporation in the United States, other countries, or both.

IT Infrastructure Library® is a registered trademark of the Office of Government Commerce and is used here by BMC Software, Inc., under license from and with the permission of OGC.

ITIL® is a registered trademark, and a registered community trademark of the Office of Government Commerce, and is registered in the U.S. Patent and Trademark Office, and is used here by BMC Software, Inc., under license from and with the permission of OGC.

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.

Sybase is the registered trademark of SAP AG in Germany and in several other countries.

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.

Restricted rights legendU.S. Government Restricted Rights to Computer Software. UNPUBLISHED -- RIGHTS RESERVED UNDER THE COPYRIGHT LAWS OF THE UNITED STATES. Use, duplication, or disclosure of any data and computer software by the U.S. Government is subject to restrictions, as applicable, set forth in FAR Section 52.227-14, DFARS 252.227-7013, DFARS 252.227-7014, DFARS 252.227-7015, and DFARS 252.227-7025, as amended from time to time. Contractor/Manufacturer is BMC SOFTWARE INC, 2101 CITYWEST BLVD, HOUSTON TX 77042-2827, USA. Any contract notices should be sent to this address.

Customer support

You can obtain technical support by using the BMC Software Customer Support website or by contacting Customer Support by telephone or e-mail. To expedite your inquiry, see “Before contacting BMC.”

http://www.bmc.com

Support website

You can obtain technical support from BMC 24 hours a day, 7 days a week at http://www.bmc.com/support. From this website, you can

■ read overviews about support services and programs that BMC offers■ find the most current information about BMC products■ search a database for issues similar to yours and possible solutions■ order or download product documentation■ download products and maintenance■ report an issue or ask a question■ subscribe to receive proactive e-mail alerts when new product notices are released■ find worldwide BMC support center locations and contact information, including e-mail addresses, fax numbers, and

telephone numbers

Support by telephone or e-mail

In the United States and Canada, if you need technical support and do not have access to the web, call 800 537 1813 or send an e-mail message to [email protected]. (In the subject line, enter SupID:<yourSupportContractID>, such as SupID:12345). Outside the United States and Canada, contact your local support center for assistance.

Before contacting BMC

Have the following information available so that Customer Support can begin working on your issue immediately:

■ product information

— product name— product version (release number)— license number and password (trial or permanent)

■ operating system and environment information

— machine type— operating system type, version, and service pack or other maintenance level such as PUT or PTF— system hardware configuration— serial numbers— related software (database, application, and communication) including type, version, and service pack or

maintenance level

■ sequence of events leading to the issue

■ commands and options that you used

■ messages received (and the time and date that you received them)

— product error messages— messages from the operating system, such as file system full— messages from related software

3

http://www.bmc.com/support

mailto:[email protected]

License key and password information

If you have questions about your license key or password, use one of the following methods to get assistance:

■ Send an e-mail message to [email protected].

■ Use the Customer Support website at http://www.bmc.com/support.

4 BMC ProactiveNet Getting Started Guide

mailto:[email protected]


ContentsChapter 1 BMC ProactiveNet overview 7

What is BMC ProactiveNet? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7BMC ProactiveNet components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

BMC ProactiveNet Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7BMC ProactiveNet database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8BMC ProactiveNet Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8BMC ProactiveNet monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9BMC ProactiveNet Administration Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10BMC ProactiveNet Operator Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10BMC ProactiveNet SLO Console. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10BMC ProactiveNet Integration Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11BMC Impact Model Designer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11BMC Impact Event Adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11BMC ProactiveNet CMDB extensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11BMC ProactiveNet Performance Management Web Services . . . . . . . . . . . . . . . . 12

BMC ProactiveNet integrations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12BMC Atrium Configuration Management Database (CMDB) . . . . . . . . . . . . . . . . 12BMC ProactiveNet Performance Management Reporting . . . . . . . . . . . . . . . . . . . 12BMC Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13BMC Transaction Management Application Response Time (BMC TM ART) . . 13BMC Atrium Orchestrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13BMC BladeLogic Service Automation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13BMC IT Service Management (BMC ITSM). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14BMC Atrium Discovery Dependency Mapping (BMC Atrium Discovery) . . . . . 14BMC ProactiveNet Application Diagnostics (BMC AppSight integration) . . . . . 14

Chapter 2 Preparing for your installation 15

Installation workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Installation types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Installation requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Requirements for installations on all operating systems. . . . . . . . . . . . . . . . . . . . . 18Requirements for installations on Microsoft Windows computers . . . . . . . . . . . . 18Requirements for installations on UNIX computers . . . . . . . . . . . . . . . . . . . . . . . . 19

Pre-installation tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Pre-installation tasks for all operating systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Pre-installation tasks for Windows environments . . . . . . . . . . . . . . . . . . . . . . . . . . 20Pre-installation tasks for UNIX environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Preparing to install BMC ProactiveNet in high-availability mode. . . . . . . . . . . . . . . . 27

Contents 1

Requirements for installing BMC ProactiveNet in high-availability mode on Microsoft Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Requirements for installing BMC ProactiveNet in high-availability mode on UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Ports used by BMC ProactiveNet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Hardware and software requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Chapter 3 Preparing for BMC Atrium CMDB integration 37

Installation scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Integrating BMC Atrium CMDB with BMC ProactiveNet . . . . . . . . . . . . . . . . . . . 37Integrating with BMC Atrium CMDB in a cluster environment . . . . . . . . . . . . . . 39

Installing BMC ProactiveNet CMDB Extensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40Restarting Apache Tomcat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Installing required modules and hotfixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43Validating BMC Atrium CMDB elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Chapter 4 Installing the BMC ProactiveNet Server on Microsoft Windows for the first time 45

Installing BMC ProactiveNet Server on Microsoft Windows . . . . . . . . . . . . . . . . . . . . 45Applying licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Chapter 5 Installing remote BMC ProactiveNet Agent(s) on Microsoft Windows 53

Best practices for installing BMC ProactiveNet Agents . . . . . . . . . . . . . . . . . . . . . . 53Installing BMC ProactiveNet Tunnel Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56Installing multiple BMC ProactiveNet Agents on a single computer . . . . . . . . . . 57

Verifying that the BMC ProactiveNet Agent is running. . . . . . . . . . . . . . . . . . . . . . . . . 58

Chapter 6 Installing the BMC ProactiveNet Server on Solaris for the first time 59

Special considerations for installing on Solaris 10 . . . . . . . . . . . . . . . . . . . . . . . . . . 60Installing the BMC ProactiveNet Server on Solaris . . . . . . . . . . . . . . . . . . . . . . . . . 60

Obtaining the fingerprint for the BMC ProactiveNet Server . . . . . . . . . . . . . . . . . . . . . 64Applying licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65Verifying the installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Chapter 7 Installing remote BMC ProactiveNet Agent(s) on UNIX-based computers for the first time 67

Best practices for installing BMC ProactiveNet Agents . . . . . . . . . . . . . . . . . . . . . . . . . 68Installing a BMC ProactiveNet Agent on a UNIX-based computer for the first time 68

Installing the BMC ProactiveNet Agent remotely from the BMC ProactiveNet Operations Console. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Installing multiple BMC ProactiveNet Agents on single computer . . . . . . . . . . . . 71Finishing the installation process on the AIX platform . . . . . . . . . . . . . . . . . . . . . . . . . 72Verifying that the BMC ProactiveNet Agent is running. . . . . . . . . . . . . . . . . . . . . . . . . 72

2 BMC ProactiveNet Deployment Guide

Chapter 8 Installing the Administration Console on remote computers 73

Installing the BMC ProactiveNet Administration Console on Microsoft Windows . 73Launching the Administration Console on Microsoft Windows computers . . . . 74

Installing the BMC ProactiveNet Administration Console on Solaris . . . . . . . . . . . . . 75Launching the Administration Console on Solaris. . . . . . . . . . . . . . . . . . . . . . . . . . 76

Installing multiple Administration Consoles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Chapter 9 Installing remote BMC ProactiveNet Agents unattended on Microsoft Windows 79

Chapter 10 Installing BMC ProactiveNet in high-availability mode on Windows 83

Installing BMC ProactiveNet Server on a primary node . . . . . . . . . . . . . . . . . . . . . . . . 83Installing BMC ProactiveNet Server on a standby node . . . . . . . . . . . . . . . . . . . . . . . . 88Creating dependencies for BMC ProactiveNet Server cluster resource . . . . . . . . . . . 89Installing the BMC ProactiveNet Agent in high-availability mode on Microsoft

Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90Creating dependencies for a BMC ProactiveNet Agent cluster resource . . . . . . . . . . 94

Chapter 11 Installing BMC ProactiveNet in high-availability mode on Solaris 97

High-availability workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97Installing BMC ProactiveNet in high-availability mode on Solaris . . . . . . . . . . . . . . . 99

Chapter 12 Introduction to the BMC ProactiveNet interfaces 101

Deciding which interface to use. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101Administering BMC ProactiveNet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101BMC ProactiveNet profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

Admin profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102User profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

BMC ProactiveNet Administration Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103Connecting the BMC ProactiveNet Administration Console to the BMC

ProactiveNet Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103Launching the BMC ProactiveNet Administration Console. . . . . . . . . . . . . . . . . 103Logging out of and into the BMC ProactiveNet Server from the BMC

ProactiveNet Administration Console. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105Navigating the BMC ProactiveNet Administration Console . . . . . . . . . . . . . . . . 105

BMC ProactiveNet Operations Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106Launching the BMC ProactiveNet Operations Console . . . . . . . . . . . . . . . . . . . . 107Navigating the BMC ProactiveNet Operations Console . . . . . . . . . . . . . . . . . . . . 107Operations Console views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

Accessing the Command Line Interface (CLI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113Accessing online Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114Where to go from here. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

Chapter 13 Post-installation tasks 115

Changing the BMC ProactiveNet Console passwords . . . . . . . . . . . . . . . . . . . . . . . . . 115

Contents 3

Changing your BMC ProactiveNet Administration Console password . . . . . . . 115Changing your BMC ProactiveNet Operations Console password . . . . . . . . . . . 116

Changing the Apache HTTP port number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116Configuring BMC ProactiveNet Server to run as a non-root user after installation on

Solaris. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117Configuring the BMC ProactiveNet Server for 256-bit SSL encryption . . . . . . . . . . . 117Lengthening the command line for AIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119Moving the monitor instances from source to destination agent on Windows . . . . 119

Moving the monitor instances from source to destination agent on Windows . 119Moving the monitor instances from a source to destination agent on Solaris . . 121

Configuring BMC ProactiveNet Event Adapters to start collecting events. . . . . . . . 122Configuring BMC Atrium CMDB integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124Configuring remote cells for viewing in the Operations Console. . . . . . . . . . . . . . . . 126Registering remote cells in the Administration console . . . . . . . . . . . . . . . . . . . . . . . . 127Configuring cell connection properties to the BMC ProactiveNet Server . . . . . . . . . 128

Specifying ports in cell connection properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130Setting BMC ProactiveNet Server connection properties . . . . . . . . . . . . . . . . . . . 130

Logging out of and into the BMC ProactiveNet Server from the BMC ProactiveNet Administration Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

Adding Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132Getting started with devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

Summary of devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134Using device aliases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134Avoiding duplicate devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135Creating a device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136Selecting monitors for the device. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

Stopping the BMC ProactiveNet Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141Starting the BMC ProactiveNet Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142Checking the status of the BMC ProactiveNet Server. . . . . . . . . . . . . . . . . . . . . . . . . . 142Enabling and disabling Integration Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

Enabling the Integration Service to gather data from products that integrate with BMC ProactiveNet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

Disabling the Integration Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144Specifying a particular IP address for the BMC ProactiveNet Agent. . . . . . . . . . . . . 145Changing the BMC ProactiveNet Server IP address . . . . . . . . . . . . . . . . . . . . . . . . . . . 145Configuring e-mail settings to receive alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145Accessing online Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147Where to go from here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

Chapter 14 Configuring and using BMC ProactiveNet in high-availability mode 149

Configuring the BMC ProactiveNet Server in Sun cluster . . . . . . . . . . . . . . . . . . . . . . 149Creating the BMC ProactiveNet resource type . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150Configuring the resource type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151Creating the resource group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152Customizing the scripts to achieve BMC ProactiveNet application high-

availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155Running BMC ProactiveNet in high-availability mode . . . . . . . . . . . . . . . . . . . . . . . . 159Bringing a resource group online. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159Manually switching the BMC ProactiveNet application to the standby node . . . . . 159


Disabling failover for BMC ProactiveNet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160Configuring high-availability remote cells for viewing in the Operations Console 160

Chapter 15 Uninstalling BMC ProactiveNet 163

Uninstalling the BMC ProactiveNet Server on Windows . . . . . . . . . . . . . . . . . . . . . . 163Uninstalling the BMC ProactiveNet Agent on Windows . . . . . . . . . . . . . . . . . . . . . . 164Uninstalling the BMC ProactiveNet Server on Solaris . . . . . . . . . . . . . . . . . . . . . . . . . 164Uninstalling the BMC ProactiveNet Agent on UNIX-based operating systems . . . 165Uninstalling the BMC ProactiveNet Server on a cluster in high-availability mode on

Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166Uninstalling the BMC ProactiveNet Agent on a cluster in high-availability mode on

Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167Uninstalling the BMC ProactiveNet Server on a cluster in high-availability mode on

UNIX- based operating systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167Uninstalling the BMC ProactiveNet Administration Console on UNIX-based

operating systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168Removing the Oracle database objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168

Contents 5

C h a p t e r 1
1 BMC ProactiveNet overview
This chapter contains an overview of the components that comprise BMC ProactiveNet and other BMC products that can be used in conjunction with BMC ProactiveNet.

What is BMC ProactiveNet?BMC ProactiveNet is an integrated platform that combines event management and data analytics (including baselines, abnormality detection, and Root Cause Analysis algorithms) in a single seamless solution. Event management provides real-time solution for proactive detection and resolution of IT problems before they have an impact on critical IT systems. Data analytics uses metrics data collected from the infrastructure to detect abnormalities, predict outages, and provide deep diagnostics information. The goal of data analytics is to provide a research facility to better understand, tune, and modify the selected area.

BMC ProactiveNet componentsThe following sections describe the components that comprise BMC ProactiveNet.

BMC ProactiveNet Server

The BMC ProactiveNet Server is the core BMC ProactiveNet component that receives events and data from various sources, such as the BMC ProactiveNet Agents, BMC Impact Event Adapters, and BMC ProactiveNet Integration Services. Once the BMC ProactiveNet Server has collected this information, it processes events and data using

Chapter 1 BMC ProactiveNet overview 7

BMC ProactiveNet database

a powerful analytics engine and additional event processing instructions stored in its knowledge base. The BMC ProactiveNet Server can also leverage a service model (published from BMC Atrium CMDB or other sources) to put monitors and events in a business context.

The BMC ProactiveNet Server is responsible for configuring and controlling BMC ProactiveNet Agents, gathering data collected by BMC ProactiveNet Agents, collecting SNMP data, storing data, and presenting data in the form of graphs, reports, views, and events.

Other components installed with the BMC ProactiveNet Server are the BMC ProactiveNet Operations Console, the BMC Administration Console, the BMC ProactiveNet SLO Console, and the BMC ProactiveNet database.

BMC ProactiveNet database

The BMC ProactiveNet database is a Sybase ASA database that is installed automatically when you install the BMC ProactiveNet Server. You do not need a separate license to install or operate this database.

The BMC ProactiveNet database acts as a central repository for all the monitor configuration and statistical data, Service-level Objects (SLO) and report data, rate and baseline data, as well as user, agent and device information.

The BMC ProactiveNet database acts as the central repository for storing configuration information as well as for storing performance data and events.

The database stores the following:

■ Configuration information like users, device, agent, monitors, and groups. ■ Performance data like raw performance data, event information.■ Processed data like rate and baseline data.

BMC ProactiveNet Agent

Two types of BMC ProactiveNet Agents are included in the BMC ProactiveNet product.

A local agent is a BMC ProactiveNet Agent that is installed with the BMC ProactiveNet Server. The local agent monitors the health of the BM ProactiveNet Server to ensure that the BMC ProactiveNet Server runs at peak performance.


BMC ProactiveNet monitors

A remote agent is a BMC ProactiveNet Agent that is installed on a computer other than the BMC ProactiveNet Server. The remote agents should be installed on each network element in the enterprise that you want to monitor. They collect device-specific data such as CPU usage, memory usage, and other data specific to the host operating system. This enables the BMC ProactiveNet Server to remotely gather statistical data on all supported operating systems.

BMC does not recommend installing a remote agent on the same machine as a local agent.

BMC ProactiveNet monitors

BMC ProactiveNet monitors are customized objects that typically collect critical data from Web site infrastructure. BMC ProactiveNet provides an extensive set of out-of-the-box monitors that collect performance data from applications, databases, middleware, firewalls, servers, network devices, and load balancers.

The following monitors indicate the overall health of the BMC ProactiveNet Server and are automatically set up during the BMC ProactiveNet Server installation:

■ Agent Status monitor ■ SolarisTM File System monitor ■ Solaris Process monitor ■ Solaris System monitor ■ Sybase ASA Intelliscope monitor ■ Sybase Query ■ Web URL

The following monitors are automatically set up while adding or installing a BMC ProactiveNet remote agent:

■ Agent Status monitor ■ Agent System monitor ■ Agent TCP monitor ■ Ping Monitor

For more information about BMC ProactiveNet monitors, see the BMC ProactiveNet Monitor Guide.


BMC ProactiveNet Administration Console


The BMC ProactiveNet Administration Console allows you to modify and manage the BMC ProactiveNet Server and the BMC ProactiveNet Agent network management areas by adding or deleting users, groups, monitored devices, applications, and services, or changing event notifications and thresholds. You can also manage supported infrastructure components and service models. The Administration Console also provides access to event management policies, the dynamic data editor, and the services editor.

For more information about the BMC ProactiveNet Administration Console, see the BMC ProactiveNet Administrator Guide.

BMC ProactiveNet Operator Console

The BMC ProactiveNet Operations Console is a Web-based application that provides options to navigate through BMC ProactiveNet and view all of the information collected and computed by the BMC ProactiveNet Server related to events, views, and graphs.

For more information, see the BMC ProactiveNet User Guide.

BMC ProactiveNet SLO Console

The BMC ProactiveNet SLO Console displays an integrated view of all Service Level Objectives (SLOs). These business views help define, measure, and track SLOs.

SLO views complement existing infrastructure-centric application management solutions. SLO business views help define, measure, and track SLOs. With new business views, business structures are available in a top-down hierarchical view that delivers near real-time service level views of application and service metrics. This view provides valuable information on performance status from an end users’ perspective for each business unit and SLO compliance.

SLO views also represent application performance levels and service levels committed to within the organization. The views represent application performance metrics in a way that relates the IT and line of business teams as a close working unit on which the company depends.

For more information, see the BMC ProactiveNet User Guide.


BMC ProactiveNet Integration Service

BMC ProactiveNet Integration Service

If you are using products such as BMC PATROL, HP Operations Manager, or IBM Tivoli Monitoring as data sources for your enterprise, each remote BMC ProactiveNet Agent hosts an integration service that you can enable to collect data from these applications, integrating them with BMC ProactiveNet.

For more information, see the BMC ProactiveNet Administrator Guide.

BMC Impact Model Designer

BMC Impact Model Designer is a plug-in installed with the BMC ProactiveNet CMDB Extensions that allows BMC ProactiveNet to use the BMC Atrium Core Console to design and create service models.

For more information, see the BMC ProactiveNet Service Modeling and Publishing Guide.

BMC Impact Event Adapters

Each BMC ProactiveNet Agent hosts the BMC Impact Event Adapters. BMC Impact Event Adapters convert data from event sources into events that can be processed by the BMC ProactiveNet Server.

The BMC Impact Event Adapters can collect source events from

■ operating system and application log files■ SNMP type 1 and type 2 traps■ message output from command line interfaces■ the Windows Event Log

For more information, see the BMC Impact Event Adapters User Guide.

BMC ProactiveNet CMDB extensions

The BMC ProactiveNet CMDB extensions, modules, and hotfixes are necessary components to integrate BMC ProactiveNet with the BMC Atrium CMDB. With integration, the BMC Atrium CMDB can be used for service modeling. The BMC ProactiveNet extensions allow the publishing server to be notified when changes have been made to the service model in the BMC Atrium CMDB. The publishing server can apply those changes immediately in the BMC ProactiveNet Server.


BMC ProactiveNet Performance Management Web Services


BMC ProactiveNet Performance Management Web Services

BMC ProactiveNet Performance Management Web Services is an integration application that enables Web Services type communications between external programs and BMC ProactiveNet components.

For more information, see the BMC ProactiveNet Performance Management Web Services Getting Started Guide.

BMC ProactiveNet integrationsThe following BMC products integrate with and enhance the functionality of BMC ProactiveNet.

BMC Atrium Configuration Management Database (CMDB)

BMC Atrium CMDB is a repository that stores configuration items (CIs) available in an enterprise. You can import the CIs from the BMC Atrium CMDB to define service model objects that you want to monitor in BMC ProactiveNet. BMC ProactiveNet leverages the service relationship information from the CIs in BMC Atrium CMDB that are monitored by BMC ProactiveNet to produce better results for Probable Cause Analysis.

BMC ProactiveNet Performance Management Reporting

BMC ProactiveNet Performance Management Reporting is an advanced reporting platform that uses SAP BusinessObjects Enterprise Professional as the host for BMC ProactiveNet Performance Management system universes and the Reporting Engine that administers and publishes the reports. ProactiveNet Performance Management Reporting contains event report and impact report templates and also allows you to create ad hoc reports.


BMC Portal

BMC Portal

BMC Portal provides a common Web-based interface for the BMC Performance Manager Portal software module. BMC Performance Manager for Portal extends the features of the BMC Portal by providing real time monitoring and management functions of agentless and BMC PATROL agent-based systems. BMC ProactiveNet can be configured to synchronize this data to monitor the IT devices effectively.

BMC Transaction Management Application Response Time (BMC TM ART)

BMC TM ART is a monitoring product that lets IT administrators manage the performance and reliability of applications and measure the health of these applications based on end-user experience metrics such as availability, accuracy, and performance.

The adapter for BMC TM ART integrates data collected by BMC TM ART Central into BMC ProactiveNet Server for analysis and root-cause drill down. The adapter collects data from all the monitors that are configured and enabled for data collection in the BMC TM ART application. The adapter uses the set of servlet APIs that are available as part of BMC TM ART Central to access and collect the required metrics.

BMC Atrium Orchestrator

BMC Atrium Orchestrator is a suite of components that empowers operators with process-based control. With its workflow-based process templates, customers can rapidly adapt and deploy functional design to ensure consistent and appropriate, policy-based response across the enterprise. The BMC Triage and Remediation Solution is an integration of BMC Atrium Orchestrator and BMC ProactiveNet Performance Management.

BMC BladeLogic Service Automation

BMC BladeLogic Service Automation suites help manage, control, and enforce configuration changes in data centers. With the integration of BMC BladeLogic, BMC ProactiveNet Performance Management retrieves change information from BMC BladeLogic for Probable Cause Analysis (PCA) candidates. BMC BladeLogic can also deploy a BMC ProactiveNet Agent as part of the batch provisioning job for a newly-provisioned server.


BMC IT Service Management (BMC ITSM)

BMC IT Service Management (BMC ITSM)

BMC ITSM reduces complexity and facilitates the efficiency and integration of customer support, change management, and asset management. It applies a repeatable process for production changes to improve the stability of business services while managing required changes. It streamlines the processes around IT service desk, asset management, and change management operations. The Integration for BMC Remedy Service Desk (IBRSD) component adds business context to incidents by enabling bidirectional flow of information between BMC ProactiveNet and BMC Remedy Service Desk. BMC ProactiveNet Performance Management provides a Triage and Remediation Solution by integrating BMC Atrium Orchestrator and BMC ITSM.

BMC Atrium Discovery Dependency Mapping (BMC Atrium Discovery)

BMC Atrium Discovery and Dependency Mapping automates the process of populating BMC Atrium CMDB by exploring IT systems to identify hardware and software, and then creating CIs and relationships from the discovered data.

BMC ProactiveNet Application Diagnostics (BMC AppSight integration)

BMC ProactiveNet Application Diagnostics pinpoints, captures, and communicates the root cause of application problems for a specific transaction, without the need to recreate the problem or replicate its environment in a lab. IT operations and application support staff can isolate the problems and route them to the appropriate domain expert for rapid resolution.

BMC ProactiveNet Application Diagnostics agents are lightweight software agents deployed on Java EE or .NET application servers. Their primary role is gathering diagnostic data on application transaction performance, execution, and errors. These agents are based on the BMC AppSight Black Box patented technology and provide deep application diagnostics for inclusion in application root cause analysis.



C h a p t e r 22 Preparing for your installation

This chapter contains information about requirements that must be in place before beginning the installation, pre-installation tasks that you must perform, and other considerations.

If you are upgrading from a previous BMC ProactiveNet or BMC Impact Solutions installation, see the BMC ProactiveNet Upgrade Guide.

Installation workflowFigure 1 on page 16 provides an overview of the tasks that you must perform to install the BMC ProactiveNet components on Microsoft Windows or UNIX-based computers.

Installation workflow


Figure 1 BMC ProactiveNet installation workflow

Prepare host computers for installation.

6

Install the BMC ProactiveNet CMDB

Extensions.

Using the BMC ProactiveNet provided utility, install the BMC ProactiveNet CMDB Extensions, modules, and hotfixes on the computer where the BMC Atrium CMDB is installed. For details, see Chapter 3, “Preparing for BMC Atrium CMDB integration.”

2

Install the BMC ProactiveNet Agent on

remote computers.

Using the BMC ProactiveNet installation program, install the BMC ProactiveNet Agent on one or more computers. For details, see Chapter 5, “Installing remote BMC ProactiveNet Agent(s) on Microsoft Windows” or Chapter 7, “Installing remote BMC ProactiveNet Agent(s) on UNIX-based computers for the first time.”

1

Installation begins.

Installation ends.

Do you want to integrate with the

BMC Atrium CMDB?

Plan your installations.

5

4Install the BMC

ProactiveNet Server.

Plan your BMC ProactiveNet deployment. For details, see the BMC ProactiveNet Deployment Guide.

Using the BMC ProactiveNet installation program, install the BMC ProactiveNet Server, local agent, and integration service on the server target computer. For details, see Chapter 4, “Installing the BMC ProactiveNet Server on Microsoft Windows for the first time” or Chapter 6, “Installing the BMC ProactiveNet Server on Solaris for the first time.”

no

yes

Review system requirements and prerequisites and perform preinstallation tasks. For hardware and software requirements, see the BMC ProactiveNet Release Notes. For prerequisites and preinstallation tasks, see “Installation requirements” on page 17 and “Pre-installation tasks” on page 19.

Install the BMC ProactiveNet

Administration Console.

Using the BMC ProactiveNet installation program, install the BMC ProactiveNet Administration Console on one or more computers. For details, see Chapter 8, “Installing the Administration Console on remote computers.”

3

Installation types


Installation typesYou can perform the following types of installations for the BMC ProactiveNet Server and the BMC ProactiveNet Agent:

■ first-time installation; see the following chapters:

— Chapter 4, “Installing the BMC ProactiveNet Server on Microsoft Windows for the first time”

— Chapter 5, “Installing remote BMC ProactiveNet Agent(s) on Microsoft Windows”

— Chapter 6, “Installing the BMC ProactiveNet Server on Solaris for the first time”

— Chapter 7, “Installing remote BMC ProactiveNet Agent(s) on UNIX-based computers for the first time”

— Chapter 8, “Installing the Administration Console on remote computers”

■ unattended installation of BMC ProactiveNet remote Agents; see Chapter 9, “Installing remote BMC ProactiveNet Agents unattended on Microsoft Windows”

■ high-availability installation; see the appropriate chapter for your operating system:

— Chapter 10, “Installing BMC ProactiveNet in high-availability mode on Windows”

— Chapter 11, “Installing BMC ProactiveNet in high-availability mode on Solaris”

If you are upgrading from BMC Impact Solutions or from a previous version of BMC ProactiveNet, see the BMC ProactiveNet Upgrade Guide

Installation requirementsEnsure that the target computers for BMC Proactive meet or exceed the system requirements listed in the BMC ProactiveNet Release Notes and in the following sections.

Requirements for installations on all operating systems


Requirements for installations on all operating systems

In addition to meeting the system requirements in the BMC ProactiveNet Release Notes, ensure that all your target computers meet the following requirements.

■ Ensure that port 80 is available for installing the Apache web server. If any other application is using the port, change the port allocation to make the port 80 available for BMC ProactiveNet installation. On the system where you want to host the BMC ProactiveNet Server or agent, verify the TCP control port (port 80) availability by running the following command from a command line:

netstat -a | findstr "LISTENING" | findstr "80"

Once BMC ProactiveNet has been installed, you can change the port for the Apache web server to free port 80 for use by your other application. For instructions, see “Changing the Apache HTTP port number” on page 116.

■ BMC Software recommends that you install BMC ProactiveNet from a local copy of the installation image and not from a network drive. Installing from a network drive can cause delays in completing the installation.

■ The installation directory name cannot contain spaces.

■ For successful installation, ensure that the Host name does not contain a hyphen.

Requirements for installations on Microsoft Windows computers

■ Ensure that the user running the installation program has administrator rights and permissions and is a member of the Administrators group on the target computer.

■ Ensure that the target computer has the most recent patch level for supported Windows operating systems. If it does not, use Microsoft Update (or Windows Update) to update it. For supported versions, see the BMC ProactiveNet Release Notes.

■ On Windows Server 2008, if you want users with administrator privileges (not the Administrator user) to access the BMC ProactiveNet Server after the installation, you must turn off the User Access Control (UAC) before you install the server.

■ Do not install BMC ProactiveNet Server in a root directory (for example C:\ or D:\), on a shared drive, or in the Documents and Settings folder.

Requirements for installations on UNIX computers


■ Perl should not be installed on the target computer where BMC ProactiveNet Server is being installed.

■ While installing BMC ProactiveNet on Microsoft Windows Operating System in European locales (French and German), ensure that you do not change the default localized Administrators group name. BMC ProactiveNet Performance Management installation works with only the default localized Administrators group names. For example:

■ English: Administrators■ German: Administratoren■ French: Administrateurs

Requirements for installations on UNIX computers

■ Ensure that the user running the installation program is root.

■ Ensure that gzip is installed and present in the PATH environment variable.

■ Ensure that you have created the destination directory for the installation. The installation script will not create this directory during installation.

■ Do not install the BMC ProactiveNet Agent in the /usr directory.

Pre-installation tasks To prepare your environment for the BMC ProctiveNet installation, you must perform certain tasks before you begin the installation. The following sections provide details about the tasks that you must perform.

Pre-installation tasks for all operating systems

■ Close all applications that are running.

WARNING The directory where the BMC ProactiveNet Server is installed and all its parent directories must have 755 permissions and must be owned by root, as well as the other group. Without these permissions and ownership, you will not be able to log into the BMC ProactiveNet Server.

Pre-installation tasks for Windows environments


■ Disable any anti-virus software on each host computer on which you are installing a component or exclude the ProactiveNet installation directory from the virus scanning.

■ Turn off the firewall (not the firewall service), before launching the installation program.

■ Disable the following programs on the target computer:

— virus scanning programs

Virus scanners can block the SMTP port and lock files that the installation program needs to configure the mail server and perform the installation. You can enable the virus scanning programs after the installation is completed.

— firewall protection programs, such as McAfee Host Intrusion Prevention Service (HIPS)

HIPS can block access to ports that are used by the installation program during installation and by the BMC ProactiveNet Server at runtime. You must leave HIPS disabled after the installation is completed.

You must reboot the computer after you disable the service.

Where to go from here

Proceed to the pre-installation tasks specific to your operating system:

■ Microsoft Windows, see “Pre-installation tasks for Windows environments” on page 20

■ UNIX-based operating systems, see “Pre-installation tasks for UNIX environments” on page 24


Perform the following tasks before launching the BMC ProactiveNet installation program.

■ Clean your temporary directories. Start with the temporary folder in your home folder. Also clean the %Temp%, %Tmp% directories, and C:\WINNT\Temp or C:\Windows\Temp if present. You might not be able to delete all the files, but BMC recommends that you remove any files or directories that begin with ProactiveNet.



■ If Terminal Services is enabled, configure it to save installation log files after the installation is complete; otherwise, the log files will be deleted. For more information, see “Configuring Terminal Services to save the log files” on page 21.

Configuring Terminal Services to save the log files

Terminal Services creates a temp directory for each user account, and the installation program creates log files in this directory. At the end of the session, Terminal Services deletes the temp directory and any files that it contains, including the installation log files. By using the Terminal Services configuration tool, you can change Terminal Services so that it saves the log files.

To configure Terminal Services to save log files

1 Choose Start => Programs => Administrative Tools => Terminal Services Configuration.

The Terminal Services Configuration/Server Settings tool is displayed.

2 Open the Server Settings folder.

3 In the Delete temporary folders on exit dialog box, choose No and click OK.

4 In the Use temporary folder per session dialog box, choose No and click OK.

5 Close the Terminal Services Configuration/Server Settings tool.

6 Open the Registry Editor and navigate to the following registry:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Terminal Server

WARNING If you do not configure Terminal Services to save the log files, the installation will fail.



7 Verify that the following registry keys in the Terminal Server registry have the appropriate settings:

8 Reboot the computer.

Checking the pre-installation requirements for Windows

When you start the BMC ProactiveNet Server installation, the installation program invokes a pre-installation utility that checks to ensure that the target computer is configured based on the recommended settings. The pre-installation utility checks the environment and reports a status of OK or Not OK for each configuration variable that it checks; however, if you want to check the environment before you start the installation program, you can run the pre-installation utility separately by executing the following script:

preinstall_check.exe

The executable is located on the installation image in the ProactiveServer directory.

For Windows, the pre-installation utility runs the following checks.

Key Type Data value

DeleteTempDirsOnExit REG_DWORD 0

PerSessionTempDir REG_DWORD 0

FlatTempDira

a This registry value exists only if flat temporary folders are enabled. If flat temporary folders are disabled, the FlatTempDir key is not present.

REG_SZ 1

NOTE BMC Software recommends that you retain the Terminal Services settings after installing BMC ProactiveNet. Retaining these Terminal Services settings will make it easier for you to upgrade to future versions of BMC ProactiveNet.

Preinstallation check Description

FirewallStatus Determines whether or not the firewall service is running. The firewall should be turned off.

UserRights Checks to determine if the user running the preinstallation utility is an administrator or part of the administrator group.

OperatingSystem Checks that the operating system version is supported.

OperatingSystemPatch Checks that the operating system patch (if any) is supported.

RAM Checks that the necessary amount of RAM is available.



Hard Disk Space This check:

■ obtains the list of drives■ obtains the list of quorum in case of cluster systems■ determines the disk space available for each of the drives■ identifies the drive (for example, during install, it will identify if it is a C or D

drive)

ProcessorConfiguration Checks that the processor configuration is supported.

PortAvailability Checks that the required ports are available. For the list of ports required, see “Ports used by BMC ProactiveNet” on page 30.

PageFileSize Checks the page file size.

PrimaryInterface Checks whether the NIC card is available.

DNSConfiguration Confirms the IP address.

DefaultGateway Verifies that the default gateway is not blank.

FileSystem This check:

identifies the file system (for example, on Windows it will say NTFS which is supported for Windows)

Disk Info This check:

■ obtains the list of drives■ obtains the list of quorum/common data disks if there is a cluster installation■ identifies the disk space available for each drive■ identifies the drive and file system, and checks for sufficient space

SystemRootFreeSpace Checks that there is enough free disk space on the system boot drive.

RequiredFiles Looks for the presence of the MSVCP60.dll file, which is required for BMC ProactiveNet Server installation or upgrade.

OSType Determines if the system architecture is 32 or 64-bit.

TerminalServices Checks to ensure that Terminal Services is configured to save log files. If the check fails, then follow the instructions in “Configuring Terminal Services to save the log files” on page 21.

BMCImpactExplorer Checks to ensure that BMC Impact Explorer is not installed.

TaskSchedulerService Checks to see that the Task Scheduler service is running.

Cluster installation If this is a cluster installation, the pre-installation utility checks to see if the following services are running on primary and standby nodes:

■ ClusSvc■ W32Time

and ensures that the necessary cluster resources (Cluster Name, Cluster IP & Quorum Disk in the same group) are available.

Preinstallation check Description

Pre-installation tasks for UNIX environments


When the pre-installation check utility finishes, it creates a log file and saves it to your desktop. Review the log file to determine the success or failure of the pre-installation checks. Correct any errors before you launch the installation program. If the installation program encounters a failed check on a mandatory setting, it aborts the installation. To resolve any checks that display Not OK, see the Troubleshooting Guide.

To save the log file to a location other than your desktop, run the pre-installation check from the command line as follows and specify the directory where you want the log file to be saved.

preinstall_check.exe directoryName


Perform the following tasks before launching the BMC ProactiveNet installation program.

■ Clean your temporary directories. Start with the temporary folder in your home folder. You may not be able to delete all the files, but BMC recommends that you remove any files or directories that begin with ProactiveNet.

■ Ensure that the nobody user account exists on the target computer.

■ Disable X Windows access control by using the xhost command.

■ If the init file is not copied to the /etc/rc3.d directory, then the BMC ProactiveNet Agent corresponding to the init file is not listed as installed (in the list of existing BMC ProactiveNet Agent installations) during installation or upgrade of other agents. This is valid only for non-root users.



Checking the pre-installation requirements for Solaris

When you start the BMC ProactiveNet Server installation, the installation program invokes a pre-installation utility that checks to ensure that the target computer is configured based on the recommended settings. The pre-installation utility checks the environment and reports a status of OK or Not OK for each configuration variable that it checks; however, if you want to check the environment before you start the installation program, you can run the pre-installation utility separately by executing the following script from the directory you created to install BMC ProactiveNet:

preinstall_check.sh

The pre-installation script for Solaris runs the following checks.

NOTE The preinstallation check utility must be run from the directory that you created for BMC ProactiveNet installation. For information about this directory, see “Requirements for installations on UNIX computers” on page 19.

Check Description

Operating System Checks if operating system is SunOS. Other UNIX operating systems are not supported for Server installation.

Zone on the System The BMC ProactiveNet Server does not support installation on the global zone when there are subzones present. Installation is only supported on non-global full zones. Zones are supported from Solaris 10 and above, so the check for presence of zones is from Solaris 10 onwards.

Root [ / ] partition Ensures that the root partition is not 100% full. The installation may fail if there is insufficient space available in the root partition.

BEM Components Checks if BMC Impact Solutions components are present. If they are present, they must be uninstalled.

User nobody exists in the system

Checks if the nobody user and nobody group exist in the system.

Operating System Processor Type

Checks if the processor is 64-bit SPARC processor. Installation is not supported on 32-bit SPARC processor.

Operating System Version

Checks if SunOS version is supported.

IP address Verifies the IP address.

Host names resolved IP against IP

Checks if the resolved IP for the host name matches the IP address.

Loghost matching with host name

Checks if loghost matches the host name

DNS configuration Checks whether DNS is configured on system. This is required for DHCP support for ProactiveNet Server.

Permissions on /tmp Checks if /tmp directory has read, write and execute permission for owner, group and others.



The script is located on the installation image in the ProactiveServer directory.

When the pre-installation check utility finishes, it creates a log file and saves it to your desktop. Review the log file to determine the success or failure of the pre-installation checks. Correct any errors before you launch the installation program. If the installation program encounters a failed check on a mandatory setting, it aborts the installation. To resolve any checks that display Not OK, review the prerequisites in this chapter to ensure that you have implemented all of them. If all the prerequisites have been implemented and the pre-installation check utility still returns Not OK for some checks, see the BMC ProactiveNet Troubleshooting Guide.

To save the log file to a location other than your desktop, specify the directory where you want the log file to be saved when you launch the utility as follows.

preinstall_check.sh directoryName

The installer runs the pre-installation check and returns one of the following messages:

■ No Solaris Patch Needed

If your system does not require an updated patch, the message will be similar to the following:

System Operating System is SunOS 5.9, ok to proceed.

■ Solaris Patch Needed

If your system requires a new patch, the text will be similar to the following:Checking patch level of the system...System does NOT have required level of patch.

gzip Checks if the gzip compression utility is present in the /usr/bin/gzip or /bin/gzip or /usr/local/bin/gzip path. Gzip is no longer shipped with BMC ProactiveNet Server and is required for successful installation.

Default router Checks if the default gateway is configured.

Available swap space

Checks if the computer has the minimum amount of swap space available.

File mode creation mask

Checks if /usr/bin/umask value is 022.

Total memory Checks if the computer has the minimum memory available.

Motif Runtime kit Checks whether Motif Runtime kit (SUNWmfrun), ICE components package (SUNWxwice) and X11 platform software (SUNWxwplt) installation components are installed.

Patch level on the system

Check if all the required patches needed for the JRE on the particular OS are present.

Check Description

Preparing to install BMC ProactiveNet in high-availability mode


To run the ProactiveNet Server successfully on Solaris, install the required patches from the SunSolve website and reboot the system before installing the BMC ProactiveNet Server.


High availability is a backup operation that automatically switches to a standby database, server, or network if the primary system fails or is temporarily shut down for maintenance. High-availability is an important function because it provides fault-tolerance to mission-critical systems that rely on consistent availability and performance. Unlike a single-server system, a high availability setup maintains your data and service availability, reducing or eliminating system downtime because of software or hardware failure.

BMC ProactiveNet allows seamless integration with the high-availability cluster operation. Using configuration scripts, monitors monitoring failover cluster elements can be transferred from the primary system to the backup system.

BMC ProactiveNet provides high-availability support for the following monitor groupings:

■ single monitor instance■ single monitor type■ group of monitors

The failover support script also allows you to:

■ change the source agent of the monitors■ change the target IP of the monitors■ turn off data collection of the monitors

BMC ProactiveNet in high-availability mode consists of two servers with identical configurations. The first server is referred to as the primary node. The second server is referred to as the standby node. The two nodes share a logical IP address and cluster name. Both servers have access to a shared storage disk.

The BMC ProactiveNet Server installation will be done with logical IP/host name enabled on the primary node. The BMC ProactiveNet Server should be installed on the shared storage disk. When the primary node is down the secondary node picks up the installation from the shared storage disk.



Figure 2 High-availability system architecture

Requirements for installing BMC ProactiveNet in high-availability mode on Microsoft Windows


Requirements for installing BMC ProactiveNet in high-availability mode on Microsoft Windows

Before you install BMC ProactiveNet in high-availability mode, make sure that you have two servers with the following configuration:

■ identical operating system version (for example, Windows 2003 or Windows 2008 Enterprise Server)

■ identical hardware configuration ■ located in the same domain■ the logical IP is configured■ identical timestamp

■ the Microsoft Clustering software should be installed on both nodes

■ add the common logical IP/host name to be allocated to the two servers to the domain name service (DNS)

■ map the disk to be shared between the two nodes with same directory name and/or directory path on both nodes

■ the IP address, Disk, and Network Name should be present in the same group.■ BMC ProactiveNet Agent installation should be done on a clean computer.

Requirements for installing BMC ProactiveNet in high-availability mode on UNIX

Before you install BMC ProactiveNet in high-availability mode, make sure that you have two servers with the following configuration:

■ Ensure that the Sun Cluster software is installed on all computers that will be hosting nodes.

NOTE Time Services (a software available to maintain system timestamps) are required to maintain an identical timestamp between the primary and standby nodes. Windows 2003 and 2008 Enterprise Server Windows Time services maintain the identical timestamps between the computers. Ensure that this service is running before installing the BMC ProactiveNet in high-availability mode on Windows.

NOTE In Windows 2008 Enterprise Server instead of logging into each node for installing the BMC ProactiveNet Server, login to the cluster and install the BMC ProactiveNet Server by moving to each node.

Ports used by BMC ProactiveNet


■ Apply the latest patches for the Sun Cluster software.

■ Both computers hosting the failover configuration should have the same logical name or shared IP address.

■ Both nodes must be physically interconnected through a private network.

■ Both nodes should have identical timestamp.

■ After installing and configuring the cluster, verify that the clusters are online. For detailed information about prerequisites, configuration, and cluster collections using the Sun Cluster software, see www.oracle.com.

Ports used by BMC ProactiveNetThe BMC ProactiveNet Server uses several configurable and non-configurable TCP control ports for its operations.

Table 1 lists the ports that you can configure and provides the procedure to change port configuration in case of conflict with another application installed on the same host where you want to install BMC ProactiveNet.

NOTE On Solaris, the Sun cluster installer (if installed with scinstall), maintains an identical timestamp on the participant nodes. Enable this option while installing the Sun cluster. For more information, refer to http://docs.sun.com/app/docs/doc/819-2969/cacbdgeg?l=en&a=view.

http://www.oracle.com

http://docs.sun.com/app/docs/doc/819-2969/cacbdgeg?l=en&a=view

http://docs.sun.com/app/docs/doc/819-2969/cacbdgeg?l=en&a=view



Table 1 Required ports for BMC ProactiveNet (part 1 of 5)

Port Description To change the port...

80 Apache HTTP port used for Web browser requests

Port 80 must be available during installation; however, the port number can be changed after installation.

1. Open the appropriate files for your operating system:

■ For UNIX: /usr/pw/apache/conf/httpd.conf.■ For Windows: pw\ApacheGroup\Apache\conf\httpd.conf and

pw\pronto\conf\pronet.conf

2. Search for the string Port 80 and replace the value 80 with the desired port number.

3. Search for the string Listen 80 and replace the value 80 with the same port number provided in the previous step.

443 Apache HTTP port used for Web browser requests in HTTPS mode

1. Open the appropriate files for your operating system:

■ For UNIX: /usr/pw/apache/conf/httpd.conf.■ For Microsoft Windows:

pw\ApacheGroup\Apache\conf\httpd.conf and pw\pronto\conf\pronet.conf

2. Search for the string VirtualHost _default_:443 and replace the value 443 with the desired port number.

3. Search for the string Listen 443 and replace the value 443 with the same port number provided in the previous step.

1099 Used by the Administrator Console to connect to the BMC ProactiveNet Server.

It is a non-configurable port. It is required to be open.

1100 Used by the JBoss server It is a non-configurable port. It is required to be open.

1827 Used by the Central Administration cell to accept client connections.

1. If the cell is running, stop the cell by entering the following command: mkill –n cell_name.

2. Open the mcell.dir file and change the cell port to the new port number. You must change the cell port in the mcell.dir files of all components (cells, integrations, and so forth) that have to connect to that cell.

3. Restart the cell.



1828 Used by the cell to accept client connections.

1. If the cell is running, stop the cell by entering the following command: mkill –n cell_name.

2. Open the mcell.dir file and change the cell port to the new port number. You must change the cell port in the mcell.dir files of all components (cells, integrations, and so forth) that have to connect to that cell.

3. Restart the cell.

1851 Used as a gateway from an embedded BMC ProactiveNet cell to the BMC ProactiveNet Server.

1. Update the new changes on mcell.dir.

2. Ensure that the cell is running.

3. Restart the jserver.

4. Restart the Event adapter.

2638 Used by JServer and AC to connect to the Database.

The Database listens on this port for JServer or Agent Controller to initiate communication.

1. In the /pw/custom/conf/pronet.conf file, change the value of the pronet.api.database.portnum property to the new port number.

2. Restart the system by running the command: pw system start

3084 Enables Impact Administration Server actions to be triggered from the cell.





3115 Used as a gateway from the cell to Integration for BMC Remedy Service Desk (IBRSD)





3182 Used by the Integration Service to listen for the ProactiveNet Server.

Installation Directory\pw\pproxy\PNS\bin\pproxsrv.exe -install -p 3182 -m

3182 is the default port name, different port can be given in command prompt and updated to custom\pronet.conf





3183 Integration Service listens for the ProactiveNet Agent. Used in failover configuration.

Using the command line

PATROLAgent -proxyserver tcp:<IntegrationServiceHost>: <StagingAdapterPort> -p <PATROLAgentPort> -km UNIX3.km

where,

■ <IntegrationServiceHost> is the system in which the Integration Service is running

■ <StagingAdapterPort> is the port number that the PATROL Agent registers automatically with the Integration Service. The default port number is 3183.

■ <PATROLAgentPort> is the port number of the PATROL Agent. The default port number is 3181.

■ km must either be loaded or preloaded.

Using the environment variable

Run the following command to set the PROXYSERVERS environment variable:

set PROXYSERVERS=tcp:<Integration Service Host>: <StagingAdapterPort>

where, PROXYSERVERS is the environment variable.

Using the PATROL Configuration Manager rule

For information about PATROL Configuration Manager (PCM), see PATROL Configuration Manager User Guide and BMC Performance Manager Consoles Release Notes.

To configure the PATROL Agent using the PCM rule, run the following command:

"/AgentSetup/proxy/proxyServers" = { REPLACE ="tcp:<IntegrationServiceHost>:< StagingAdapterPort >"}

Note: You can also change the Staging Adapter port using the Administration Console.

8005 Used by Jserver to shut down the Tomcat server.

Change the port number in the appropriate files for your operating system:

■ Microsoft Windows: pw\pronto\conf\pronet.conf and pw\pronto\conf\jserv.properties

■ UNIX: tomcat/conf/server.xml





8008 Tunnel Proxy port Change the port number in the appropriate files for your operating system:

■ Microsoft Windows: and pw\pronto\conf\pronet.conf■ UNIX: pw/pronto/conf/jserv.properties

8009 Used by the Tomcat server to connect to Apache

Change the port number in the appropriate files for your operating system:

■ Microsoft Windows: pw\pronto\conf\pronet.conf and pw\pronto\conf\jserv.properties

■ UNIX: tomcat/conf/server.xml

8093 JMS Server port Change the port number in the appropriate files for your operating system:

■ Microsoft Windows: pw\pronto\conf\pronet.conf and pw\jboss\server\minimal_jms\delpoy\jbossmq-service.xml

■ UNIX: pw/jboss/server/minimal_jms/delpoy/jbossmq-service.xml

9149 This is a pronet.jserver.event.port.

It is a non-configurable port. This port is required to be open.

12123 Agent Controller listens for the Jserver on this port

1. In the /pw/custom/conf/pronet.conf file, change the value of the pronet.apps.agentcontroller.port property to the new port number.


12124 Used by the Remote Agent to listen for communication from the Agent Controller.

This port can be changed using the BMC ProactiveNet Administration Console or CLI.

12126 Agent Controller Call back port

Used by Remote Agents to send data back to the ProactiveNet Server.

Note: Any changes to the Agent Controller Call back port configuration must be made to all remote Agents.

1. In the /pw/custom/conf/pronet.conf file, change the value of the pronet.apps.agent.cntl.port property to the new port number.


3. Repeat for all remote Agents.

4. Restart the BMC ProactiveNet Agent.

12130 CheckPoint Monitor port

This port is used to receive log messages .

1. In the /pw/custom/conf/pronet.conf file, change the value of the pronet.apps.ckpmon.lea.listenport property to the new port number.




Hardware and software requirements


Hardware and software requirementsHardware and software requirements are listed in the Product Availability and Compatibility Matrix available at http://www.bmc.com/support_home. For additional requirements information, see the BMC ProactiveNet Release Notes.

12134 This is a TCP port that is used for communication between the Agent controller and the Apache server for agent. Communication is initiated when the Agent Controller starts.

It is a non-configurable port.

12141 Log Server port 1. In the /pw/custom/conf/pronet.conf file, change the value of the pronet.apps.logging.logServer.port property to the new port number.


15000 Connects the Agent Controller to the Rate process.

The Rate process passively listens to port 15000 until the Agent Controller initiates contact.

1. In the /pw/custom/conf/pronet.conf file, change the value of the pronet.rate.port property to the new port number.


45000 Message Server port 1. In the /pw/custom/conf/pronet.conf file, change the value of the pronet.apps.messageserver.port property to the new port number.




http://www.bmc.com/support_home

Hardware and software requirements


C h a p t e r 3
3 Preparing for BMC Atrium CMDB integration
If you are integrating BMC ProactiveNet with BMC Atrium CMDB, you must install the BMC ProactiveNet CMDB Extensions, components, and hotfixes before you configure the BMC ProactiveNet Server to integrate with the CMDB.

Installation scenariosThe following scenarios help you to determine the installation and integration process appropriate for your environment.

Integrating BMC Atrium CMDB with BMC ProactiveNet

The following steps describe the general procedure to install or upgrade BMC ProactiveNet with BMC Atrium CMDB integration. The location of each installation component is listed in Table 2 on page 38.

NOTE If you are integrating with the BMC Atrium CMDB, all BMC ProactiveNet Servers in your environment must be synchronized with a single CMDB for probable cause analysis and event propagation to work properly.


Integrating BMC Atrium CMDB with BMC ProactiveNet

1. (For BMC Atrium CMDB version 7.5, patch 5 only) Install the Notification Engine and Notification Engine Web Services.

2. Install the components in the order presented, according to the BMC Atrium CMDB version:

3. Run the BMC Atrium CMDB validation utility. See “Validating BMC Atrium CMDB elements” on page 43 for details.

4. Integrate BMC ProactiveNet with BMC Atrium CMDB in one of the following ways:

■ (install or upgrade, no previous BMC Atrium CMDB integration) Install BMC ProactiveNet Server. During the BMC ProactiveNet Server installation process, specify the BMC Atrium CMDB server details.

■ (upgrade with an existing BMC Atrium CMDB integration) Manually configure integration between the BMC ProactiveNet Server and BMC Atrium CMDB. For instructions, see “Configuring BMC Atrium CMDB integration” on page 124.

Table 2 lists the location of the BMC Atrium CMDB installation components. See the documentation provided with the installation files for details.

BMC Atrium CMDB version Procedure

7.5 patch 5 or 7.6 patch 2 or 7.6.03 fresh installation

A. Install the BMC ProactiveNet CMDB Extensions.

B. Install BMC Atrium CMDB hotfixes.

7.6.03 upgrade A. Install BMC Atrium CMDB hotfixes.

B. Install the BMC ProactiveNet CMDB Extensions.

7.6.03 Foundation installation A. Install the AR hotfix.

B. Install the BMC ProactiveNet CMDB Extensions.

C. Install BMC Atrium CMDB hotfixes.

Table 2 BMC Atrium CMDB installation component directories (part 1 of 2)

Component Installation directory

AR hotfix Integrations\Atrium_CMDB\Atrium_CMDB_HotFixes\SolutionInstall Atrium_CMDB_Foundation_7603 \AR\Windows

BMC ProactiveNet CMDB Extensions

Integrations\Atrium_CMDB\PNET_CMDB_Extensions

See “Installing BMC ProactiveNet CMDB Extensions” on page 40 for details.


Integrating with BMC Atrium CMDB in a cluster environment

Integrating with BMC Atrium CMDB in a cluster environment

In a cluster environment, each BMC Remedy Action Request System server in the cluster requires BMC ProactiveNet CMDB Extensions, modules, and hotfixes.

Before installing the extensions, remove servers from the server group. For instructions about configuring and removing servers in a server group, see BMC Remedy Action Request System Configuration Guide, located at http://webapps.bmc.com/support/faces/prodallversions.jsp?seqid=108018. You need to be a member of the BMC Support website to access the documentation.

The following steps describe the general procedure to integrate BMC ProactiveNet with BMC Atrium CMDB in a cluster environment. The location of each installation component is listed in Table 2 on page 38.

1. In the BMC Remedy Action Request System Administration Console, remove each server from the server group.

2. Restart the servers.

3. On each server, install BMC ProactiveNet Atrium CMDB Extensions.

4. Return each server to the server group and restart the servers.

5. (for BMC Atrium CMDB version 7.5, patch 5, only) On each server, install the Notification Engine and Notification Engine Web Services.

6. On each server, install BMC Atrium CMDB hotfixes.

7. Run the BMC Atrium CMDB validation utility. See “Validating BMC Atrium CMDB elements” on page 43 for details.

BMC Atrium CMDB hotfixes Integrations\Atrium_CMDB\Atrium_CMDB_HotFixes\Atrium_CMDB_cmdbVersion\platform

Contact BMC Customer Support for the latest hotfixes.

Notification Engine and Notification Engine Web Services

Integrations\Atrium_CMDB\NOE_Bundle_For_CMDB_75

Table 2 BMC Atrium CMDB installation component directories (part 2 of 2)

Component Installation directory



http://webapps.bmc.com/support/faces/prodallversions.jsp?seqid=108018

Installing BMC ProactiveNet CMDB Extensions

Installing BMC ProactiveNet CMDB ExtensionsInstall BMC ProactiveNet CMDB Extensions on the same computer where BMC Atrium CMDB is installed. If you have installed BMC Remedy Action Request System on both the primary and secondary server, you need to install BMC ProactiveNet CMDB Extensions on both these systems.

Before you begin

In a cluster environment, follow the guidelines in “Integrating with BMC Atrium CMDB in a cluster environment” on page 39.

Follow the installation procedure appropriate for your operating system.

To install BMC ProactiveNet CMDB Extensions on Microsoft Windows

1 Navigate to the Integrations\Atrium_CMDB\PNET_CMDB_Extensions directory in the installation package.

■ If you have an installation DVD, copy the contents to a directory with write permission, and navigate to the directory.

■ If you have a download directory, navigate to the directory.

2 Double-click pnExtLoader.exe.

The InstallShield Wizard window is displayed.

3 In the Welcome dialog box, click Next.

4 Accept the software license agreement.

5 In the AR Server Connection Information dialog box, complete the following fields and click Next.

Field Description

AR Server Name name of the system on which BMC Remedy Action Request System is installed

Port Number target port number for the BMC Remedy Action Request System server

RPC Port Number If you specified a non-standard RPC port number while installing BMC Remedy Action Request System, enter that RPC port number. Otherwise, you can leave this field blank


Installing BMC ProactiveNet CMDB Extensions

For more information about the portmapper and port numbers used with BMC Remedy Action Request System, see the BMC Remedy Action Request System Installation Guide.

6 In the Administrator Logon Information Required dialog box, in the User Name and Password fields, enter the credentials required to access BMC Remedy Action Request System and click Next.

7 In the Remedy CMDB Setup dialog box, perform one of the following actions:

■ If you have not enabled the portmapper to automatically obtain the port number, enter the port number of the BMC Remedy Action Request System server and click Next.

■ If you enabled the portmapper to automatically obtain the port number, you can leave this field blank and click Next.

For more information on the portmapper and port numbers used in BMC Remedy Action Request System, see BMC Remedy Action Request System Installation Guide.

The installer displays the progress of the installation.

8 Click Finish to complete the installation.

9 Restart Apache Tomcat as described in “To restart Apache Tomcat on Microsoft Windows” on page 42.

To install BMC ProactiveNet CMDB Extensions on UNIX

1 Navigate to the Integrations/Atrium_CMDB/PNET_CMDB_Extensions directory in the installation package.



2 Start the installation by executing ./pnExtLoader.

3 Read and accept the license agreement.

NOTE Ensure that you have execute permissions to the common directory before starting the installation. To obtain execute permissions, run chmod -R 777 common.


Restarting Apache Tomcat

4 Answer the questions in the following table to continue with the installation.

For more information on the portmapper and port numbers used in BMC Remedy Action Request System, see BMC Remedy Action Request System Installation Guide.

The installation starts after you enter the values in the table above. The installer displays BMC ProactiveNet CMDB Extensions completed. after the installation is complete.

5 Restart Apache Tomcat as described in “To restart Apache Tomcat on UNIX.”

Restarting Apache TomcatAfter installing BMC ProactiveNet CMDB Extensions you must restart Apache Tomcat. Follow the procedure appropriate for your operating system.

To restart Apache Tomcat on Microsoft Windows

1 Open a command prompt and type services.msc.

2 Right-click Apache Tomcat 5 and click Restart.

To restart Apache Tomcat on UNIX

1 Navigate to tomcat_home/bin.

2 Stop Apache Tomcat by executing ./shutdown.sh.

3 Restart Apache Tomcat by executing ./startup.sh.

Question Description

Enter the server name Enter the name of the computer on which BMC Remedy Action Request System is installed.

What is the AR System installation directory?

Enter the directory in which BMC Remedy Action Request System is installed.

What is the TCP/IP port for AR System server?

Enter the TCP/IP port number that the BMC Remedy Action Request System server listens to.

What is a valid AR System Administrator ID?

Enter the user ID required to access BMC Remedy Action Request System.

What is the password for the AR System Administrator?

Enter the password required to access BMC Remedy Action Request System.

Server port Enter the port number of the BMC Remedy Action Request System server. The default is 1840.


Installing required modules and hotfixes

Installing required modules and hotfixesBMC Atrium CMDB version 7.5 patch 5 first requires installation of the Notification Engine and Notification Engine Web Services.

All supported versions of BMC Atrium CMDB require installation of the hotfixes.

To install required modules and hotfixes

1 If you are using BMC Atrium CMDB version 7.5 patch 5, install the Notification Engine and Notification Engine Web Services from the Integrations/Atrium_CMDB/NOE_Bundle_For_CMDB_75 installation directory.

See the documentation provided with the installation files for details.

2 Install BMC Atrium CMDB hotfixes from the Integrations/Atrium_CMDB/Atrium_CMDB_HotFixes/Atrium_CMDB_cmdbVersion/platform installation directory

See the documentation provided with the installation files for details. Contact BMC Customer Support for latest hotfixes.

Validating BMC Atrium CMDB elementsAfter you install BMC ProactiveNet CMDB Extensions, run the validate_atrium_cmdb CLI command to validate the following items:

■ BMC Remedy Action Request System server host, port, user name and password■ Supported BMC Atrium CMDB version and patch level■ BMC ProactiveNet CMDB Extensions version and patch level, which confirms the

following:— SIM class information version— SIM workflow version— SIM management data

Run the command from the computer where you plan to install or upgrade the BMC ProactiveNet server.

NOTE Run the validation command before any BMC Atrium CMDB integration, whether you install BMC ProactiveNet for the first time or you upgrade to the current version of BMC ProactiveNet.



Validating BMC Atrium CMDB elements

To validate BMC Atrium CMDB elements

1 On the computer where you plan to install or upgrade the BMC ProactiveNet server, navigate to the Integrations/Atrium_CMDB/AtriumCMDB_Validator directory in the installation package.



2 In a command prompt, change the directory to the location where the files are located.

3 Run the validate_atrium_cmdb command according to the following syntax:

where

■ ARServerName is the BMC Remedy Action Request System server computer name or IP address

■ port is the port number used by the BMC Remedy AR System server on that computer

■ userName is a valid user name with read permission on the BMC Remedy AR System server

■ password is a password for the user name. If a password is not required, do not use this option.

The validation status is displayed upon completion. If the validation fails, verify that the command options are correct and that the BMC Atrium CMDB server is running. Then verify that patches, hotfixes, and BMC ProactiveNet CMDB Extensions have been installed successfully.

After successful validation, you can select to integrate with BMC Atrium CMDB during BMC ProactiveNet server installation or upgrade.

validate_atrium_cmdb -s ARServerName -t port -u userName [-p password]


C h a p t e r 4
4 Installing the BMC ProactiveNet Server on Microsoft Windows for the first time
This chapter provides instructions for installing the BMC ProactiveNet Server on Microsoft Windows for the first time. If you are upgrading, see the Upgrade Guide for instructions.

Installing BMC ProactiveNet Server on Microsoft Windows

The BMC ProactiveNet Server installation installs the following components:

■ BMC ProactiveNet Server

■ a BMC ProactiveNet Agent

The BMC ProactiveNet Agent installed with the BMC ProactiveNet Server is referred to as the local agent. BMC does not recommend using the local BMC ProactiveNet Agent for monitoring anything other than the BMC ProactiveNet Server.

■ the BMC ProactiveNet Operations Console

WARNING The Integration Service is installed with the BMC ProactiveNet Agent. Due to conflicts with the BMC ProactiveNet Server and the drain on the resources of the local Agent, BMC Software does not recommend enabling the Integration Service on the same computer where the BMC ProactiveNet Server is installed.



■ the BMC ProactiveNet Administration Console

■ BMC ProactiveNet database

Before you begin

■ Ensure that there are no remote BMC ProactiveNet Agents installed on the computer where the BMC ProactiveNet Server will be installed. If any remote BMC ProactiveNet Agents are installed on this computer, the BMC ProactiveNet Server installation will fail.

■ Ensure that the computer on which you are installing the product adheres to the hardware, operating system, platform, and software requirements listed in the BMC ProactiveNet Release Notes.

■ Ensure that the computer on which you are installing the product adheres to the requirements described in Chapter 2, “Preparing for your installation.”

■ Ensure that you have run the preinstall_check.exe utility as described in Chapter 2, “Preparing for your installation.”.

■ If you are using the Remote Desktop Connection (RDC) to install the product, then the RDC should be in console mode.

To install the BMC ProactiveNet Server on Microsoft Windows

1 Start the installation program using one of these methods:

■ DVD: Insert the installation DVD. In the ServerWin_pw_vx.x_byyy directory (where x is the version number and y is the build number), open the ProactiveServer directory. Double-click the setup.exe file.

■ BMC Software EPD website (http://webapps.bmc.com/epd): Select BMC ProactiveNet and select the current version for the platform that you are installing to. Download the BMCProactiveNetWin_Ver_bxxx.zip file that corresponds to the version of the BMC ProactiveNet, unzip the file, and double-click the setup.exe file.

2 On the Welcome screen, click Next.

3 On the License Agreement screen, click Yes to agree.

4 On the Prerequisite screen, verify all the mandatory system and configuration requirements and click Next.

5 On the Prerequisite Result screen, verify that each line displays OK and click Next.


http://webapps.bmc.com/epd


6 On the Administrator Information screen, complete the following fields and click Next.

7 On the Choose Destination Location screen, accept the default directory (\Program Files\ProactiveNet) or choose a different directory and click Next.

8 On the Configuring the Integration Service screen, click Next.

9 On the SIM Cell Inputs screen, complete the following fields and click Next.

You are not prompted for the cell details if you are upgrading from a previous version of BMC ProactiveNet Server.

Field Description

Sender E-mail ID e-mail address that you specify as the sender of any notification e-mails. For example, you might specify [email protected] so that the administrator receiving the e-mail will know immediately which host is having disk space problems or other issues that send notifications.

Administrator E-Mail ID fully-qualified e-mail address for the person that will be the administrator of the ProactiveNet Server. The format for the email address should be [email protected].

Name or IP Address of SMTP Server

Name or IP address of the SMTP server

WARNING Do not install BMC ProactiveNet Server in a root directory (for example C:\ or D:\), on a shared drive, or in the Documents and Settings folder.

WARNING BMC does not recommend enabling the Integration Service on the same computer as the BMC ProactiveNet Server.

Field Description

Cell Instance Name Type the cell instance name. The default is pncell_hostname.

Note: Hyphens and underscores are the only special characters allowed for cell instance names.

Cell Port Enter a port number in the range of 1024 to 65535. The default port for the cell is 1828.

Cell Encryption Key

Enter the cell encryption key. The default is mc. No special characters are allowed.



10 On the Admin Cell Inputs screen, complete the following fields and click Next.

11 On the Configuring CMDB Server screen, perform one of the following actions:

■ If you do not want to integrate the BMC ProactiveNet Server with BMC Atrium CMDB, click Next.

■ If you want to configure the BMC ProactiveNet Server to integrate with BMC Atrium CMDB, follow these steps:

1. Complete the following fields and click Next.

NOTE If you are upgrading from version 7.7 using the –hybrid option, you are prompted for the cell details. You enter the same cell name as that of the BMC Event and Impact Management presentation cell on the BMC Event and Impact Management server, from where you are migrating the data.

Field Description

Admin Cell Port Enter the port number for the Admin cell. The default is 1827.

Admin Cell Encryption Key Enter an encryption key for the Admin cell. The default is mc.

WARNING Before you configure the CMDB Server, ensure that BMC ProactiveNet CMDB Extensions, modules, and hotfixes are installed on the computer where the BMC Atrium CMDB is installed. If necessary, you can stop this installation, install the extensions, and then restart the BMC ProactiveNet Server installation. For information about installing the CMDB extensions, see Chapter 3, “Preparing for BMC Atrium CMDB integration.”

NOTE Configuring the BMC ProactiveNet Server for integration with BMC Atrium CMDB is recommended, but not mandatory, during installation. If you do not configure the ProactiveNet Server for CMDB integration during installation, you can manually configure CMDB integration any time after installation is complete. For instructions, see “Configuring BMC Atrium CMDB integration” on page 124.

Field Description

AR Server Host Name Enter the host name of the CMDB or AR Server.

CMDB Version Enter the version number of the CMDB/AR Server. ■ For BMC Atrium CMDB version 7.5 patch 5, enter 7.5■ For BMC Atrium CMDB version 7.6 patch 2, enter 7.6■ For BMC Atrium CMDB version 7.6.03, enter 7.6.03

AR Server User Enter the user name required to log in to the AR Server. The default is Demo.



2. On the Configuring CMDB Cross Launch screen, complete the following fields and click Next.

12 If the required version of Microsoft .NET Framework is not found on the computer, you will be prompted to install it. Microsoft .NET Framework is required to use the SCOM adapter and Web transaction recorder. When the prompt to install Microsoft .NET is displayed, follow these steps:

A Click Yes to begin installing Microsoft .NET Framework.

B Accept the license agreement.

The Microsoft .NET Framework installation process begins. The process may take several minutes to complete.

C When the installation completes, click Exit.

The Microsoft .NET Framework installation closes and the BMC ProactiveNet Server installation process begins. The BMC ProactiveNet Server installation process may take awhile to complete. No more user interaction is required until the installation process is finished.

13 On the E-mail confirmation message screen, click Yes to register the product.

AR Server Port Enter the CMDB or AR Server port number. The default is 0.

If AR is configured with a portmapper, enter port 0.

AR Password/AR Confirm Password

Enter the password required to log in to the AR server.

Item Description

UDDI Registry Hostname Enter the host name of UDDI Registry for Atrium CMDB and for Atrium CMDB, the name of the Atrium Web Services Server.

UDDI Registry Port Enter the port of UDDI Registry for CMDB or the port of Atrium Web Services server for CMDB. The default is 7777.

UDDI Registry User Enter the UDDI Registry user name. The default is Admin.

UDDI Registry Password/ Confirm Password

Enter and confirm the UDDI Registry password.

NOTE If you are installing on Microsoft Windows 2008, you must use the Role Management tool to install Microsoft .NET.

Field Description


Applying licenses

14 On the Registration Information screen, enter your e-mail address and click Next.

15 On the BMC ProactiveNet Server Installation screen, click Finish to complete the installation.

When the BMC ProactiveNet Server installation is complete, you can choose View Installation Logs to open the installation logs.

Applying licenses

When you purchased the product, you should have received the following license files in a .zip file from your BMC Software representative:

■ proactivenet.lic■ proactivenet.sign

To apply the license

1 Unzip the license files.

2 Copy the license files to the installDirectory\pw\license directory (for example, C:\Program Files\ProactiveNet\pw\license).

3 From the system icon tray, right-click the BMC ProactiveNet icon and choose pw commands.

4 In the BMC ProactiveNet Pw Commands window, on the command line enter the following command:

pw lic update

NOTE Applying or updating the license restarts the jserver process and forces all active user sessions on BMC ProactiveNet Server to log off.


Applying licenses

The BMC ProactiveNet license is updated.

WARNING Once you have loaded the license, moving or changing the license files can cause a number of errors to occur.

When ProactiveNet is installed a hidden .pbk file is created. If the licence directory is removed and then recreated so that .pbk no longer exists, the .pbk file must be readded for ProactiveNet licensing to function properly. This file can be captured from a backup of the installation (if a backup exists) or from another computer where ProactiveNet is installed.

If error messages occur, see the BMC ProactiveNet Troubleshooting Guide.


Applying licenses


C h a p t e r 5
5 Installing remote BMC ProactiveNet Agent(s) on Microsoft Windows
This chapter provides instructions for installing a remote BMC ProactiveNet Agent on Microsoft Windows for the first time. If you are upgrading, see the BMC ProactiveNet Upgrade Guide for instructions.

The following components are installed with the remote BMC ProactiveNet Agent:

■ BMC ProactiveNet Agent■ Integration Service■ BMC ProactiveNet Monitors■ BMC Impact Event Adapters

BMC ProactiveNet allows you to install one or more remote BMC ProactiveNet Agents on a single computer. Multiple BMC ProactiveNet Servers can connect to the remote BMC ProactiveNet Agents running on a single computer. However, each remote BMC ProactiveNet Agent on a computer can communicate with only one BMC ProactiveNet Server at a time.

For instructions and more information about installing multiple remote BMC ProactiveNet Agents, see “Installing multiple BMC ProactiveNet Agents on a single computer” on page 57.

Best practices for installing BMC ProactiveNet Agents

Do not install a remote BMC ProactiveNet Agent on the same computer as a BMC ProactiveNet Server.



The BMC ProactiveNet Server is the central system of all the BMC ProactiveNet functions and should work at peak performance at all times. The BMC ProactiveNet Server has its own agent (called a local agent) that monitors the health of the BMC ProactiveNet system. Installing a remote agent on the same computer pulls resources away from the BMC ProactiveNet Server components. Also, if multiple BMC ProactiveNet Agents are installed on the BMC ProactiveNet Server computer, the additional remote agents will interfere with some of the server commands.

Before you begin



To install BMC ProactiveNet Agent(s) on Microsoft Windows

1 Start the installation program from the BMC ProactiveNet Operations Console.

A From a BMC ProactiveNet Server computer, log on to the BMC ProactiveNet Operations Console.

B Click the Options link at the top right of the console and click on the Downloads tab.

C From the ProactiveNet Agent Software area, click Agentvrx.x_byyy.exe (where x is the version and y is the build number) and save the file to the computer to which you are installing the BMC ProactiveNet Agent.

2 On the computer where you are installing the BMC ProactiveNet Agent, double-click the Agentvrx.x_byyy.exe file.

3 On the Welcome screen, click Next or if you are installing multiple agents choose Install a new instance of this application on the Existing Installed Instances Detected screen.


5 On the Information screen, click Next.

6 On the Prerequisite screen, click Next.

The pre-installation check utility verifies whether or not the computer meets the requirements for installing a BMC ProactiveNet Agent.



7 On the Pre-requisite Result screen, preform one of the following actions:

■ If the pre-installation check is successful, click Next.

■ If the pre-installation check failed, click Finish, correct the issues listed Not OK by in the Pre-requisite Results window, and restart the installation process.

8 On the Choose Destination Location screen, accept the default directory or choose a different directory and click Next.

9 On the Configuring Integration Service screen, you can enable the Integration Service to collect data from integration adapters such as BMC PATROL, Tivoli ITM, or HP Operations Manager. Perform one of the following actions:

■ If you do not want to enable the Integration Service at this time, click Next.

■ If you want to enable the Integration Service, select the Enable Integration Service check box, complete the following fields, and click Next.

10 On the Start Copying Files screen, click Next to begin the installation.


WARNING Do not install the product in a root directory (for example, C:\ or D:\), shared drive, or directly under the Documents and Settings folder.

NOTE You can also enable the Integration Service after installation is complete. For instructions, see “Enabling the Integration Service to gather data from products that integrate with BMC ProactiveNet” on page 143.

Field Description

Password for admin User and Confirm Password

Enter and confirm the password for the Integration Service

Port Enter the port for the Integration Service. The default is 3182.

NOTE If you have enabled the Integration Service for the first agent, you will not be prompted with the Configuring Integration Service screen for subsequent multiple agent installations.


Installing BMC ProactiveNet Tunnel Agent





The Microsoft .NET Framework installation closes and the BMC ProactiveNet Agent installation process begins. This process may take several minutes to complete.

12 In the Display name field, enter the display name of the agent service and click Next.

13 On the Installation complete screen, click Finish to complete the agent installation.

Installing BMC ProactiveNet Tunnel Agent

If the agent installation is started from the command prompt using the command Agentversion_byyy.exe tunnel (where x is the version and y is the build number) the Edit data for Tunnel ID screen is displayed.

To install the BMC ProactiveNet Tunnel Agent

1 In the Edit data for Tunnel ID screen, enter the Tunnel ID and Server details in the respective fields.

2 On the confirmation screen, select Yes to install the tunnel agent in a secure mode.

3 On the Tunnel Agent Information screen, review the configuration settings and click Next.


NOTE If you use a Tunnel Agent, only the General Administration functionality in the Administration tab of the Administration Console is accessible through this connection protocol. The Event Management Policies, Dynamic Data Editor, Infrastructure Management, and Services Editor tabs will be grayed out.


Installing multiple BMC ProactiveNet Agents on a single computer

Installing multiple BMC ProactiveNet Agents on a single computer

By installing multiple BMC ProactiveNet Agents on a single system, you can partition your monitoring into different domains and maximize hardware usage. Multiple BMC ProactiveNet Servers in different locations can connect to different BMC ProactiveNet Agents running on the same computer. Each agent can collect a different set of data authorized for its respective BMC ProactiveNet Server.

You can choose to install a new instance of the agent. Alternatively, you can upgrade an existing agent by selecting from the list displayed. If you want to upgrade an existing BMC ProactiveNet Agent, see the BMC ProactiveNet Upgrade Guide.

To install an additional BMC ProactiveNet Agent on a computer where a BMC ProactiveNet Agent is already installed

The procedure to install multiple agents is similar to installing the BMC ProactiveNet agent for the first time.

1 Follow the procedure given in “To install BMC ProactiveNet Agent(s) on Microsoft Windows” on page 54 until 10.

2 On the BMC ProactiveNet Agent Installation dialog box, click Yes to overwrite the IP Top10 detailed diagnostics, if WinPCAP application is installed.

3 On the Edit Data screen, enter a unique port number (no other agent should have the same port number) in the range of 1-65535 for the BMC ProactiveNet Agent that you are installing and click Next.

The installation process is complete.

4 Click Finish.

NOTE Installing multiple BMC ProactiveNet Agents on a single computer will put additional load on the computer in terms of CPU, IO, Memory, and TCP buffer.

NOTE When installing multiple agents on a single computer, only the first agent installed is installed with a cell. Subsequent agent installations update the cell installed with the first agent.


Verifying that the BMC ProactiveNet Agent is running


After installation, to verify that the BMC ProactiveNet Agent is running, ensure that the BMC ProactiveNet Agent Ver x.x build yyyyyyy (portNumber) service status is Started. If the BMC ProactiveNet Agent Ver x.x build yyyyyyy (portNumber) service is not running, start it.

NOTE The computer requires time to update installation information. BMC recommends that you wait a minimum of five seconds between installations.


C h a p t e r 6
6 Installing the BMC ProactiveNet Server on Solaris for the first time
This chapter provides instructions that describe how to install the BMC ProactiveNet Server on Solaris for the first time. If you are upgrading, see the BMC ProactiveNet Upgrade Guide.

The BMC ProactiveNet Server installation installs the following components:

■ BMC ProactiveNet Server

■ a BMC ProactiveNet Agent

The BMC ProactiveNet Agent installed with the BMC ProactiveNet Server is referred to as the local Agent. BMC does not recommend using the local BMC ProactiveNet Agent for monitoring anything other than the BMC ProactiveNet Server.

■ the BMC ProactiveNet Operations Console

■ the BMC ProactiveNet Administration Console

■ BMC ProactiveNet database

WARNING The Integration Service is installed with the BMC ProactiveNet Agent. Due to conflicts with the BMC ProactiveNet Server and the drain on the resources of the local Agent, BMC Software does not recommend enabling the Integration Service on the same computer where the BMC ProactiveNet Server is installed.


Special considerations for installing on Solaris 10

Special considerations for installing on Solaris 10

The BMC ProactiveNet Server installation is permitted only on non-global zones in Solaris 10. You will not be able to upgrade previous versions of BMC ProactiveNet Server which are installed on global zones. If you need to upgrade on a global zone, contact BMC Customer Support for assistance.

Installation on Solaris 10 is supported as follows:

■ Solaris 10 global zone installation (non-global zones present)—not supported ■ Solaris 10 non-global zone installation (sparse non-global zone)—not supported■ Solaris 10 global zone installation (no non-global zones present)—supported ■ Solaris 10 non-global zone installation (full non-global zone)—supported

Installing the BMC ProactiveNet Server on Solaris

This section provides instructions for installing the BMC ProactiveNet Server on Solaris for the first time.

Before you begin

■ Ensure that there are no remote BMC ProactiveNet Agents installed on the computer where the BMC ProactiveNet Server will be installed. If any remote BMC ProactiveNet Agents are installed on this computer, the BMC ProactiveNet Server installation will fail.



■ Ensure that you have run the preinstall_check.sh script from within the directory that you created for installation, as described in Chapter 2, “Preparing for your installation.”

WARNING The directory where the BMC ProactiveNet Server is installed and all its parent directories must have 755 permissions and must be owned by root, as well as the other group. Without these permissions and ownership, you will not be able to log into the BMC ProactiveNet Server.



To install the BMC ProactiveNet Server for Solaris

1 Ensure you have access to the BMC ProactiveNet files that you have downloaded from the BMC Electronic Product Download site or from the BMC ProactiveNet DVD.

2 From the install_files/ProactiveServer directory, execute the following command:

nohup ./setup.sh

The installation script checks and returns the File system(s) with available disk space for the BMC ProactiveNet Server installation.

3 By default, the installation script locates the file system with the most available space. To install BMC ProactiveNet Server on this file system, press <enter>. Otherwise, type the name of an alternate file system and <enter>.

Depending on your environment, extracting the BMC ProactiveNet Server installation files may take as long as 15 to 30 minutes.

4 Press the spacebar to read and accept the License Agreement.

5 Enter yes to accept the terms of the License Agreement.

If all pre-installation checks are successful, the system displays the following message:

“Would you like to continue with installation (y/n) [default is 'y']?”

6 Enter y.

7 Enter the fully-qualified e-mail address for the person that will be the administrator of the BMC ProactiveNet Server. The format for the email address should be [email protected].

NOTE If you are moving the files from one machine to another, be sure to use binary mode.

NOTE The acceptance of the License Agreement is case-sensitive. Type only all lowercase or all uppercase letters— yes or YES.



8 Enter a From Name for the notification e-mail. The From Name is the name or e-mail address that you specify as the sender of any notification e-mails. For example, you might specify [email protected] so that the administrator receiving the e-mail will know immediately which host is having disk space problems or other issues that send notifications.

Specify the From Name in either the form name or [email protected], depending on the valid From address accepted by the SMTP server.

9 Enter the details for the SMTP server to be used for e-mail alerts. Details can include host name and port number. For example, pronet.api.emailer.smtp.host=shyok.proactivenet.co.inpronet.api.emailer.smtp.port=25

Enter a valid port number on which the SMTP server is listening for SMTP requests. The default port number is 25.

10 When asked if you want to enable the Integration Service, enter n.

11 Enter the details for the BMC ProactiveNet Server Service Impact Manager and Administration cells:

■ cell instance name—the default is pncell_hostName. Special characters such as a space, # , /, and : are not allowed as part of the cell name.

■ cell port number—enter a number in the range of 0 to 65535. The default is 1828

■ cell encryption key—the default is mc

■ Administration cell port number—the default is 1827

■ Administration cell encryption key—the default is mc


NOTE If you are upgrading from version 7.7 using the –hybrid option, you are prompted for the cell details. You enter the same cell name as that of the BEIM presentation cell on the BEIM server, from where you are migrating the data.



12 Determine whether or not the ProactiveNet Server will integrate with Atrium CMDB by choosing one of the following actions:

■ If you do not want to integrate with a BMC Atrium Configuration Management Database, enter n.

■ If you want to integrate with a BMC Atrium Configuration Management Database, enter y and answer the prompts for the following information:

— AR Server version For BMC Atrium CMDB version 7.5 patch 5, enter 7.5For BMC Atrium CMDB version 7.6 patch 2, enter 7.6For BMC Atrium CMDB version 7.6.03, enter 7.6.03

— valid AR Server host name

— AR port number—the default is 0— AR user name—the default is Demo

— AR password— reconfirm the AR password

— UDDI Registry Server host name— UDDI Port. The default port is 7777

— UDDI Registry user name. The default is Admin

— UDDI Registry password and reconfirm the password.



NOTE If you do not enter a valid CMDB/AR Server version (7.5, 7.6 or 7.6.03), you will not be prompted for the remaining CMDB related inputs and BMC ProactiveNet Server will not be integrated with CMDB.

If your AR Server is using a port mapper, leave AR port number as 0. If you are not using a port mapper, then you must specify a port number for the AR Server.


Obtaining the fingerprint for the BMC ProactiveNet Server

13 Enter y to continue with the installation.

14 Enter y when the following message is displayed:

“The installation will update the crontab file for root, and will add the init file /etc/rc3.d/S81pronto, /etc/rc0.d/K09pronto and /etc/rc1.d/K09pronto. It is recommended that you install this on a dedicated system.”

The installer starts the BMC ProactiveNet Server installation. Installation continues without further user intervention.

Installation may take a while to complete.

15 When installation is complete and the script asks if you want to register the BMC ProactiveNet Server, enter YES.

16 Enter your e-mail address. A registration e-mail is sent to BMC.

Obtaining the fingerprint for the BMC ProactiveNet Server

The fingerprint is used to license and activate your BMC ProactiveNet products.

To obtain the BMC ProactiveNet Server fingerprint

In a C shell, execute the following commands:

source /usr/pronto/bin/.tmcshpw license fingerprint

The output will be similar to:

FingerPrint: HSkZDN43dRUNNVtg7SssWg==

WARNING The installation program cannot be interrupted after this point, and must be allowed to continue to completion. The system will not respond to the <Ctrl-C> key combination.


Applying licenses

Applying licenses

Before you can configure and use the BMC ProactiveNet Server, you need a license key. You can obtain a license key by contacting BMC Software,

The license key consists of three files:

■ proactivenet.lic (license provisioning file)■ proactivenet.sign (encrypted signature file)■ licensing.dtd (formatting information)

These files are typically packaged in a .zip file, which is delivered through an e-mail.

To apply the license

1 In binary mode, copy .zip file onto the computer where you have installed BMC ProactiveNet Server into the /usr/pw/licenses directory.

2 Unzip the file.

3 To load the license data, execute the following command: pw license update

4 Enter y to restart the jserver.

If the license update is successful, an empty command prompt is displayed. If error messages are displayed, see BMC ProactiveNet Troubleshooting Guide.

NOTE Applying or updating the license restarts the jserver process and forces all active user sessions on BMC ProactiveNet Server to log off.

NOTE ■ You must have root privileges to apply the license.■ You only need to apply the license to your BMC ProactiveNet Server installations. The

license is not required on your remote agent installations.

WARNING Once you have loaded the license, moving or changing the license files can cause a number of errors to occur.

When ProactiveNet is installed a hidden .pbk file is created. If the licence directory is removed and then recreated so that .pbk no longer exists, the .pbk file must be readded for ProactiveNet licensing to function properly. This file can be captured from a backup of the installation (if a backup exists) or from another computer where ProactiveNet is installed.


Verifying the installation

Verifying the installationFollow these steps to verify that the installation was successful:

1 Verify that all processes are running by executing the following commands:

#csh#source /usr/pw/pronto/bin/.tmcshpw system status

A list of pw server processes is displayed that is similar to the following:

# pw system statusServers/------------------------Servers/Daemon Processes------------------------services 4820httpd 6152jserver 10660pronet_agent 4680pronet_cntl 3968tunnelproxy 7792rate 3976dbsrv 6560mcell 4952acell 4916pserver 4217

2 Review the output for errors.

Processes that are not running properly are denoted by a numbered error message, such as 961 > max 1.

Processes that are not running at all are denoted by !Not Running!.

3 If errors occur, restart the BMC ProactiveNet Server by executing the following command:

pw system start

If error conditions persist, contact BMC Software customer support for assistance.


C h a p t e r 7
7 Installing remote BMC ProactiveNet Agent(s) on UNIX-based computers for the first time
This chapter provides instructions for installing a remote BMC ProactiveNet Agent on a UNIX-based operating system for the first time. If you are upgrading, see the BMC ProactiveNet Upgrade Guide for instructions.

The following components are installed with the remote BMC ProactiveNet Agent:

■ BMC ProactiveNet Agent■ Integration Service■ BMC ProactiveNet Monitors■ BMC Impact Event Adapters (installed on all platforms except Solaris X86)

BMC ProactiveNet allows you to install one or more remote BMC ProactiveNet Agents on a single computer. Multiple BMC ProactiveNet Servers can connect to the BMC ProactiveNet Agents running on a single computer. However, each BMC ProactiveNet Agent on a computer can communicate with one BMC ProactiveNet Server at a time.

For instructions and more information about installing multiple remote BMC ProactiveNet Agents, see “Installing multiple BMC ProactiveNet Agents on single computer” on page 71.




Do not install a remote BMC ProactiveNet Agent on the same computer as a BMC ProactiveNet Server.

The BMC ProactiveNet Server is the central system of all the BMC ProactiveNet functions and should work at peak performance at all times. The BMC ProactiveNet Server has its own agent (called a local agent) that monitors the health of the BMC ProactiveNet system. Installing a remote agent on the same computer pulls resources away from the BMC ProactiveNet Server components. Also, if multiple BMC ProactiveNet Agents are installed on the BMC ProactiveNet Server computer, the additional remote agents will interfere with some of the server commands.

Installing a BMC ProactiveNet Agent on a UNIX-based computer for the first time

To install the BMC ProactiveNet Agent from the BMC ProactiveNet Operations Console on the BMC ProactiveNet Server computer, see “Installing the BMC ProactiveNet Agent remotely from the BMC ProactiveNet Operations Console” on page 69.

Before you begin

■ Ensure that you have root permissions for the computer on which you want to install the BMC ProactiveNet Agent.


NOTE The BMC ProactiveNet Agent installs and starts the BMC Impact Event Adapter if you choose to enable the cell while installing. However, the BMC ProactiveNet Agent install does NOT install Perl. Perl must be installed manually for the BMC Impact Event Adapters to start. You can either start the adapters through the Services option on Windows or execute the command ./etc/init.d/BMCImpactEventAdapter start on UNIX. For supported Perl versions for the BMC Impact Event Adapters, see the BMC ProactiveNet Release Notes at http://www.bmc.com/support.



Installing the BMC ProactiveNet Agent remotely from the BMC ProactiveNet Operations Console


Follow the steps given below to download installation files from the BMC ProactiveNet Server to a remote UNIX-based BMC ProactiveNet Agent computer.

To use the BMC ProactiveNet Server as a source for agent files

1 From a BMC ProactiveNet Server computer, log on to the BMC ProactiveNet Operations Console and navigate to the Options tab.

2 Open the Downloads tab.

3 From the BMC ProactiveNet Agent Software section, for the platform corresponding to the computer on which you want to install the BMC ProactiveNet Agent, click Agent8.x.xx_byyy.tar (where x is the version number and y is the build number) and save the file to the computer where you want to install BMC ProactiveNet Agent.

4 From the BMC ProactiveNet Agent Software section, for the platform corresponding to the computer on which you want to install the BMC ProactiveNet Agent, click setupagent.sh and save the file to the computer where you want to install BMC ProactiveNet Agent.

5 Execute setupagent.sh to start the installation.

6 Specify the installation directory that you created as the location to install the BMC ProactiveNet Agent.

7 If there are no agents installed on that computer, the BMC ProactiveNet Agent uses port 12124 by default. If there are agents already installed, you can either upgrade an existing agent or install a new agent.

If you are installing a new agent you will be prompted for the port number on which the agent will listen to. The port number should be in the range of 1-65535.

8 Read and accept the License Agreement. Press the spacebar to continue reading the License Agreement.The installation checks the server environment and returns a series of confirmation messages.

WARNING Do not install the BMC ProactiveNet Agent in the /usr directory.



9 Review each message and perform the following actions:

■ For all messages followed by OK, no action is required. ■ For any message followed by Not OK, enter n to stop the installation.

10 If all messages are followed by OK, enter y to continue with the installation.

11 (This option is available on Solaris Sparc and Linux Red Hat platforms only) Perform one of the following actions:

■ If you do not want to enable the Integration Service installed with the BMC ProactiveNet Agent, enter n.

■ If you want to enable the Integration Service installed with the BMC ProactiveNet Agent, enter y and answer the following prompts:

12 Specify a valid port number for the BMC ProactiveNet Agent. If the default port 1828 is occupied, you will be prompted for the port number.

The installation continues and may be left unattended since no further user input is required until the process is complete. The log file can be found in the directory installDirectory/pw/pronto/bin/proactive_agent_install.log.

13 If you are installing on the AIX platform, see “Finishing the installation process on the AIX platform” on page 72.

NOTE You also can enable the Integration Service after installation is complete. For instructions see, “Enabling the Integration Service to gather data from products that integrate with BMC ProactiveNet” on page 143.

Field Description

Port Enter the port number of the Integration Service. The default is 3182.


Enter and confirm the password for the Integration Service.


Installing multiple BMC ProactiveNet Agents on single computer

Installing multiple BMC ProactiveNet Agents on single computer

By installing multiple BMC ProactiveNet Agents on a single computer, you can partition your monitoring into different domains and maximize hardware usage. Multiple BMC ProactiveNet Servers in different locations can connect to different BMC ProactiveNet Agents running on the same computer. Each agent can collect a different set of data authorized for its respective BMC ProactiveNet Server.

You can choose to install a new instance of the agent. Alternatively, you can upgrade an existing agent by selecting from the list displayed. If you want to upgrade an existing BMC ProactiveNet Agent, see the Upgrade Guide.

To install multiple BMC ProactiveNet Agents

1 Run the BMC ProactiveNet Agent installation script setupagent.sh.

The script displays the list of agents already installed on the system, if any. BMC ProactiveNet Agents older than version 8.0.00 have an Agent ID of 0.

2 Choose to install a new agent on the system.

3 To continue installing another agent on the system, specify the path of the directory where the agent must be installed.

4 Specify the control port number on which the agent must listen.

It is important that you specify an unused port number (between 0 and 65535). The port number you specify is assigned to the property pronet.apps.agent.port in the pronet.conf file.

After you specify the port number, the agent installation continues.

5 If you are installing on the AIX platform, see “Finishing the installation process on the AIX platform” on page 72.

NOTE Installing multiple BMC ProactiveNet Agents on a single computer will put additional load on the computer in terms of CPU, IO, Memory, and TCP buffer.

NOTE When installing multiple agents on a single computer, only the first agent installed is installed with a cell. Subsequent agent installations update the cell installed with the first agent.


Finishing the installation process on the AIX platform

Finishing the installation process on the AIX platform

If you are installing the BMC ProactiveNet Agent on AIX, after the installation script is finished, copy the library libdb2.a from the DB2 Administration Client installation directory (InstanceHomeDirectory/sqllib/lib) into the /usr/lib directory, add the pronet.cell.enabled=true property in the /pw/custom/conf/pronet.conf file, and restart the BMC ProactiveNet Agent.


After installation, to verify that the BMC ProactiveNet Agent is running, navigate to the installDirectory/pw/pronto/bin/ directory and execute pw agent status. Verify that the pronet_agent process is listed.

If the pronet_agent process is not listed, execute pw agent start. This command restarts all the BMC ProactiveNet Agent processes.

If any exceptions occur, contact BMC Software customer support for assistance.

NOTE The computer requires time to update installation information. BMC recommends that you wait a minimum of five seconds between installations.


C h a p t e r 8
8 Installing the Administration Console on remote computers
The BMC ProactiveNet Administration Console is automatically installed with the BMC ProactiveNet Server; however, you can install it on a remote computer by performing the appropriate procedure for your operating system.

Installing the BMC ProactiveNet Administration Console on Microsoft Windows

Before you begin■ Ensure that you have administrator privileges for the target computer.■ Ensure that .NET framework 2.0.050727 or above is installed on the target

computer.

To install the BMC ProactiveNet Administration Console on a remote Microsoft Windows computer

1 From a BMC ProactiveNet Server computer, log on to the BMC ProactiveNet Operations Console.

2 Click the Options link at the top right of the console and click on the Downloads tab.

3 From the BMC ProactiveNet Admin Software area, click Adminx.x_byyy.exe (where x is the version and y is the build number) and save the file to the computer to which you are installing the BMC ProactiveNet Administration Console.

4 On the computer where you are installing the BMC ProactiveNet Administration Console, double-click the Adminx.x_byyy.exe file.


Launching the Administration Console on Microsoft Windows computers

5 On the Welcome screen of the BMC ProactiveNet Admin installer, click Next.

6 Accept the license agreement and click Next.

7 Enter the directory where you want to install the administration console or accept the default and click Next.

8 On the Installation Preview screen, click Install.

Launching the Administration Console on Microsoft Windows computers

Use the following procedure to verify the installation.

To launch Administration Console

1 On the Windows desktop, go to Start => Programs => BMC ProactiveNet Server => BMC ProactiveNet Admin.

2 On the Logon screen, enter the following details:

■ Server: Specify the name/IP Address of BMC ProactiveNet Server to which you want to connect.

■ Username: Specify the name of the user account to access BMC ProactiveNet. Default user name is admin.

■ Password: Specify the corresponding password for the user account. Default password is admin.

■ Connection: Select the connection type. Either Direct (uses port 1099 and 12128*) or HTTP Tunnel (uses port 80).

A firewall may exist between the desktop and the BMC ProactiveNet Server in the datacenter. Sometimes the firewall allows only port 80 and does not allow port 1099 and 12128, in such cases you may be forced to use the HTTP Tunnel mode.

NOTE To change the password, see “Adding Agents” on page 132.


Installing the BMC ProactiveNet Administration Console on Solaris

HTTP Tunnel connection is approximately three times slower than a Direct Connection, although this varies depending on the latency between client and server and also the speed of the client and server computers.

When connection fails with HTTP Tunnel, restart the Administration Console to log in again.

3 Click Ok to view the Administration Console.

On successful validation, the Administration Console opens.

If you attempt to view online Help from the Administration Console and use Internet Explorer as your browser, you are first prompted to update Trusted site registration to allow Internet Explorer to open the Help page as a Trusted site zone. After you update the registration, you must subsequently refresh the page to view the Help from the registered Trusted site zone.

Installing the BMC ProactiveNet Administration Console on Solaris

Before you begin

Ensure that the DISPLAY variable is set by entering the following command:

setenv DISPLAY ProactiveNetServerIPaddress

To install the BMC ProactiveNet Administration Console on Solaris

1 From a BMC ProactiveNet Server computer, log on to the BMC ProactiveNet Operations Console.

2 Click the Options link at the top right of the console and click on the Downloads tab.

3 From the BMC ProactiveNet Admin Software area, click setup_admin.bin and save the file to the computer to which you are installing the BMC ProactiveNet Administration Console.

4 On the computer where you are installing the BMC ProactiveNet Administration Console, execute the setup_admin.bin installation script.

5 Read and accept the license agreement.

6 Enter the directory where you want to install the administration console or accept the default.


Launching the Administration Console on Solaris

7 Enter Y to confirm that you want to begin the installation.

Launching the Administration Console on Solaris

Use the following procedure to verify the installation.

To launch Administration Console and test the installation

1 Open the command line prompt.

2 Run the following commands:

cd installDirectory/pw/pronto/bin/./pw admin

3 On the Logon screen, enter the following details:

■ Server: Specify the name/IP Address of BMC ProactiveNet Server to which you want to connect.

■ Username: Specify the name of the user account to access BMC ProactiveNet. Default user name is admin.

■ Password: Specify the corresponding password for the user account. Default password is admin.

■ Connection: Select the connection type. Either Direct (uses port 1099 and 12128*) or HTTP Tunnel (uses port 80).

A firewall may exist between the desktop and the BMC ProactiveNet Server in the datacenter. Sometimes the firewall allows only port 80 and does not allow port 1099 and 12128, in such cases you may be forced to use the HTTP Tunnel mode.

An HTTP Tunnel connection is approximately three times slower than a Direct Connection, although this varies depending on the latency between client and server and also the speed of the client and server computers.

If a connection fails with HTTP Tunnel, launch the Administration Console to log in again.

NOTE To change the password, see “Adding Agents” on page 132.


Installing multiple Administration Consoles

4 Click Ok to view the Administration Console.

On successful validation, the Administration Console opens.

If you attempt to view online Help from the Administration Console and use Internet Explorer as your browser, you are first prompted to update Trusted site registration to allow Internet Explorer to open the Help page as a Trusted site zone. After you update the registration, you must subsequently refresh the page to view the Help from the registered Trusted site zone. (DOES THIS STILL HAPPEN?)

Installing multiple Administration ConsolesAdministration Consoles from different versions of BMC ProactiveNet releases can be installed and used on the same computer. During Administration Console installation, BMC ProactiveNet checks for existing installations of the Administration Console. If an older version of the Administration Console is available on the computer, BMC ProactiveNet displays the following message:

ProactiveNet Admin is already installed in the system. This installation will be a fresh installation and will not upgrade previous Admin.

All installations of BMC ProactiveNet Administration Console are treated as fresh installations. After installation is complete, you can use the older installation to access the corresponding BMC ProactiveNet Server and the new installation to connect and use the new BMC ProactiveNet Server.

NOTE You cannot upgrade the Administration Console.


Installing multiple Administration Consoles


C h a p t e r 9
9 Installing remote BMC ProactiveNet Agents unattended on Microsoft Windows
This approach makes use of the record and rerun facility of the InstallShield Setup program. The process records the installation steps on one computer, creating a script and response file that can be played on the other computers where you want to install the BMC ProactiveNet Agent.

Before you begin

■ BMC Software recommends that you have Administrator privileges on all computers.

■ Ensure that the Task Scheduler or a distribution program such as Microsoft SMS is running on the remote computer.

■ Ensure that port 3182, which is used by the Integration Service, is free.

■ Ensure that all computers comply with the system requirements in the BMC ProactiveNet Release Notes.

■ Ensure that all computers comply with the requirements listed in Chapter 2, “Preparing for your installation.”

■ Ensure that all computers pass the preinstallation checks as described in Chapter 2, “Preparing for your installation.”

NOTE To successfully install agents using the recorded script and response file, the order of dialog boxes and the corresponding responses must be the same. Hence, this process works only for computers that have a similar configuration to the computer where the installation is recorded.


To record an agent installation

1 From a command prompt, navigate to the Agentx.x_bxyz.exe file available under the following directory:

UNIX: <PNET_INSTALL_DIR>/pw/pronto/web/html/download/ Windows: <PNET_INSTALL_DIR>\pw\pronto\web\html\download\

2 To install the BMC ProactiveNet Agent while recording a response file, execute the following command at the command prompt:

Agentx.x_byyyy.exe -r -f1path\fileName.iss

where x.x is the agent version, yyyy is the agent build number, path is the directory where you want to save the recorded script, and fileName is the name you want to assign the script file. The extension of the file must be .iss.

For example, Agentx.x_bxyz.exe -r -f1C:\temp\unattended\mysetup.iss

To perform an unattended installation on a local computer

1 Copy the fileName.iss file that you created onto the computer where you want to install a remote agent.

2 Open a command prompt and navigate to the directory where you copied fileName.iss.

3 To install a remote agent on the local machine using the fileName.iss script, enter the following command:

Agentx.x_byyyy.exe -s -f1path\filename

For example,

Agentx.x_byyyy.exe -ig{DCD3461A-7AA6-44D3-C2-FE7B28DC7189} -s - f1C:\temp\unattended\mysetup.iss -f2C:\temp\unattended\agentinstall.log

NOTE Do not use the Back or Cancel buttons on the installation utility while recording. These actions will be included in the recording and repeated during each subsequent installation where the recorded script is used.


To replay response file on a remote machine

1 Share the directory containing the BMC ProactiveNet Agent installation utility so that it is accessible from any target computer.

2 Schedule the setup using Task Scheduler (SCHTASKS), using the following syntax:

SCHTASKS /Create -S \\remote_computer -U user_name -SC schedule_frequency -TN task_name -TR executable path -ST starting_time -ET ending_time -SD starting_date -ED ending_date -RU Run_as_user_name

For example, to install an agent on the system vindhya at 7.00 P.M. using installation setup files on the system mahim (shared under Disk1), run the following command:

SCHTASKS /Create -S \\vindhya /U vindhya\Administrator -P password -SC HOURLY -MO 1 -TN Agent -TR "\\mahim\Disk1\setup.exe -ig{DCD3461A-7AA6-44D3-9DC2-FE7B28DC7122} -s -f1\\mahim\Disk1\agent.iss -f2C:\Agent.log" -ST 12:00 /ET 14:00 -SD 01/29/2011 -ED 01/29/2011 -RU vindhya\Administrator -RP password

To install multiple agents on a single computer unattended

1 Record the .iss file (myFirstAgent.iss) on a fresh setup while installing the first agent.

2 Record another .iss file (myNextAgent.iss) on the above setup while installing the second agent.

3 While replaying myFirstAgent.iss to install on a fresh setup, then execute myNextAgent.iss to install next agent onwards on the above setup.

NOTE You can schedule the task using Windows Explorer also. Instead of using the command line, browse to the target computer under the Network Neighborhood and open the Scheduled Tasks folder. Double-click Add Scheduled Task to launch the scheduling wizard.

Although this method is slow, it is more reliable since it rules out any problems with permissions or path names.


C h a p t e r 10
10 Installing BMC ProactiveNet in high-availability mode on Windows
You can install both the BMC ProactiveNet Server and BMC ProactiveNet Agent in high-availability mode. For information on high-availability architecture, refer to “Preparing to install BMC ProactiveNet in high-availability mode” on page 27.

Installing BMC ProactiveNet Server on a primary node

You can manually install the BMC ProactiveNet Server and BMC ProactiveNet Agent on the primary node. Failover is handled automatically by Microsoft Clustering services.

To install the BMC ProactiveNet Server as a primary node on Microsoft Windows

1 At the command prompt from the pw_x.x_yyyy\ProactiveServer directory (where x.x is the version number and yyyy is the build number), run the following command:

Setup.exe failover primary


If there is no cluster service available in the computer where you install the BMC ProactiveNet Server, an error message appears. Ensure that Microsoft Clustering is installed on the target computer.




4 On the Pre-requisite screen, verify all the mandatory system and configuration requirements and click Next.

5 On the Pre-requisite Result screen, verify that each line displays OK and click Next.

6 On the Administrator Information screen, complete the following fields and click Next.

7 On the Choose Destination Location screen, accept the default directory (\Program Files\ProactiveNet) or choose a different directory and click Next.

8 On the Configuring the Integration Service screen, click Next.

9 On the SIM Cell Inputs screen, complete the following fields and click Next.

Field Description

Sender E-mail ID e-mail address that you specify as the sender of any notification e-mails. For example, you might specify [email protected] so that the administrator receiving the e-mail will know immediately which host is having disk space problems or other issues that send notifications.

Administrator E-Mail ID fully-qualified e-mail address for the person that will be the administrator of the ProactiveNet Server. The format for the email address should be [email protected].

Name or IP Address of SMTP Server

Name or IP address of the SMTP server

WARNING Do not install BMC ProactiveNet Server in a root directory (for example C:\ or D:\), or in the Documents and Settings folder.


Field Description

Cell Instance Name Type the cell instance name. The default is pncell_hostname.

Note: Hyphens and underscores are the only special characters allowed for cell instance names.



You are not prompted for the cell details if you are upgrading from a previous version of BMC ProactiveNet Server.

10 On the Admin Cell Inputs screen, complete the following fields and click Next.

11 On the Configuring CMDB Server screen, perform one of the following actions:

■ If you do not want to integrate the BMC ProactiveNet Server with BMC Atrium CMDB, click Next.

Cell Port Enter a port number in the range of 1024 to 65535. The default port for the cell is 1828.

Cell Encryption Key

Enter the cell encryption key. The default is mc. No special characters are allowed.

Field Description

Admin Cell Port Enter the port number for the Admin cell. The default is 1827.

Admin Cell Encryption Key Enter an encryption key for the Admin cell. The default is mc.



Field Description



■ If you want to configure the BMC ProactiveNet Server to integrate with BMC Atrium CMDB, Follow these steps:

1. Complete the following fields and click Next.

2. On the Configuring CMDB Cross Launch screen, complete the following fields and click Next.

Field Description

AR Server Host Name Enter the host name of the CMDB or AR Server.

CMDB Version Enter the version number of the CMDB/AR Server. ■ For BMC Atrium CMDB version 7.5 patch 5, enter 7.5■ For BMC Atrium CMDB version 7.6 patch 2, enter 7.6■ For BMC Atrium CMDB version 7.6.03, enter 7.6.03

AR Server User Enter the user name required to log in to the AR Server. The default is Demo.

AR Server Port Enter the CMDB or AR Server port number. The default is 0.

If AR is configured with a portmapper, enter port 0.

AR Password/AR Confirm Password

Enter the password required to log in to the AR server.

Item Description

UDDI Registry Hostname Enter the host name of UDDI Registry for Atrium CMDB and for Atrium CMDB, the name of the Atrium Web Services Server.

UDDI Registry Port Enter the port of UDDI Registry for CMDB or the port of Atrium Web Services server for CMDB. The default is 7777.

UDDI Registry User Enter the UDDI Registry user name. The default is Admin.

UDDI Registry Password/ Confirm Password

Enter and confirm the UDDI Registry password.









13 On the E-mail confirmation message screen, click Yes to register the product.

14 On the Registration Information screen, enter your e-mail address and click Next.



A dialog box is displayed stating that the BMC ProactiveNet Server is being stopped and you should start the installation on the standby computer after moving cluster control to that computer.

16 Click OK to acknowledge the message. This shuts down the BMC ProactiveNet Server on the primary node.



Installing BMC ProactiveNet Server on a standby node

Installing BMC ProactiveNet Server on a standby node

The following procedures explain how to install the BMC ProactiveNet Server and agent on a standby node. Failover is handled automatically by Microsoft Clustering services.

To install the BMC ProactiveNet Server as a standby node on Microsoft Windows

1 Ensure that the BMC ProactiveNet Server is shut down on the primary node. If the BMC ProactiveNet Server is running, see “Stopping the BMC ProactiveNet Server” on page 141.

2 Move cluster control to the standby node computer.

3 On the computer hosting the standby node, from a command prompt access the \pw_x.x_yyyy\ProactiveServer directory (where x.x is the version number and yyyy is the build number) and run the following command:

Setup.exe failover standby



6 On the Prerequisite screen, verify all the mandatory system and configuration requirements and click Next.

7 On the Prerequisite Result screen, verify that each line displays OK and click Next.






Creating dependencies for BMC ProactiveNet Server cluster resource






Creating dependencies for BMC ProactiveNet Server cluster resource

Use the following procedure to create dependencies for a ProactiveNet server cluster resource.

To create dependencies for Windows cluster 2003

1 Stop the BMC ProactiveNet Server using the pw system stop command.

2 Go to Start =>All Programs => Administrative Tools => Cluster Administrator and click on the cluster name.

3 Click Resources.

A list of cluster resources is displayed.

4 Right-click on the PnService and select Properties.

5 Click the Dependencies tab in the PnService Properties window and click Modify.

6 From the list of Available Resources move the resources you want to Dependencies and click OK.

7 Restart the BMC ProactiveNet Server using the pw system start command.


Installing the BMC ProactiveNet Agent in high-availability mode on Microsoft Windows


1 Stop the BMC ProactiveNet Server using the pw system stop command.

2 Go to Start =>All Programs => Administrative Tools => Failover Cluster Manager and click on the cluster name.

3 Scroll down to Cluster Core Resources and select Properties.

4 Click the Dependencies tab in the PnService Properties window and click Insert to add a resource.

5 Select the cluster name as a resource and click Insert.

6 Select the cluster resource with ‘AND’ option. Similarly add all the resources.

7 Click Apply and OK.

8 Restart the BMC ProactiveNet Server using the pw system start command.


For high-availability, you must install the BMC ProactiveNet Agent on a primary and secondary node.

To install the BMC ProactiveNet Agent as a primary node on Microsoft Windows

1 Login to a virtual node (assuming cluster service is started on both the cluster nodes).

2 Ensure that you are on the primary node.

3 Copy the BMC ProactiveNet agent installer (agentx.x_yyyy.exe) on the local drive (for example, C:\)

4 Set the environment variable PATROL_VIRTUALNAME=<Virtual IP address of Cluster>.

5 At the command prompt, access the agentx.x_yyyy.exe (where x.x is the version number and yyyy is the build number) file under proactiveagent\windows directory.



6 Execute the following command: Agentx.x_yyyy.exe failover primary

7 Installation should be carried out on the shared drive.



10 On the Information screen, click Next.

11 On the Pre-requisite screen, click Next.

The pre-installation check utility verifies whether or not the computer meets the requirements for installing a BMC ProactiveNet Agent.

12 On the Pre-requisite Result screen, perform one of the following actions:

■ If the pre-installation check is successful, click Next.

■ If the pre-installation check failed, click Finish, correct the issues listed Not OK by in the Pre-requisite Results window, and restart the installation process.

13 On the Choose Destination Location screen, accept the default directory or choose a different directory and click Next.

14 On the Configuring Integration Service screen, you can enable the Integration Service to collect data from integration adapters such as BMC PATROL, Tivoli ITM, or HP Operations Manager. Perform one of the following actions:

■ If you do not want to enable the Integration Service at this time, click Next.

WARNING Do not install the product in a root directory (for example, C:\ or D:\), or directly under the Documents and Settings folder.

NOTE You also can enable the Integration Service after installation is complete. For instructions, see “Enabling the Integration Service to gather data from products that integrate with BMC ProactiveNet” on page 143.



■ If you want to enable the Integration Service, select the Enable Integration Service check box, complete the following fields, and click Next.

15 On the Start Copying Files screen, click Next to begin the installation.






The Microsoft .NET Framework installation closes and the BMC ProactiveNet Agent installation process begins. This process may take several minutes to complete.

17 In the Display name field, enter the display name of the agent service and click Next.


19 A message that the installation is complete on the primary node displays. You will be prompted to install on the standy node.

Field Description


Enter and confirm the password for the Integration Service

Port Enter the port for the Integration Service. The default is 3182.




To install the BMC ProactiveNet Agent as a standby node on Microsoft Windows

1 Login to virtual node (assuming cluster service is started on both the cluster nodes).

2 Ensure that you are on the standby node.

3 Copy the BMC ProactiveNet agent installer (agentx.x_yyyy.exe) on the local drive (for example, C:\).

4 Set the environment variable PATROL_VIRTUALNAME=<Virtual IP address of Cluster>.

5 At the command prompt, access the agentx.x_yyyy.exe (where x.x is the version number and yyyy is the build number) file under proactiveagent\windows directory.

6 Execute the following command: Agentx.x_yyyy.exe failover standby

7 Installation will be carried out on the shared drive.


9 Reboot the standby node.

When the BMC ProactiveNet Agent installation is complete, you can choose View Installation Logs to open the installation logs.

NOTE ■ If you modify the control port of an agent explicitly through the pronet.conf file, the port

number is not updated in the Add/Remove Programs applet and in the Agent Service display name. If you modify the control port, the port number will not be displayed when you use Add/Remove Programs

■ Each BMC ProactiveNet Agent on a system runs in a separate JVM.

■ You can check the version of the BMC ProactiveNet Agent under installationDirectory\Agent\Pronto\Bin\AGENT_VERSION.


Creating dependencies for a BMC ProactiveNet Agent cluster resource

To add a BMC ProactiveNet Agent on the cluster

Add the BMC ProactiveNet Agent to the BMC ProactiveNet Server as a virtual IP of the cluster.


Use the following procedure to create dependencies for a BMC ProactiveNet Agent cluster resource.


1 Stop the BMC ProactiveNet Server and Agent using the pw system stop command.

2 Go to Start =>All Programs => Administrative Tools => Cluster Administrator and click the name of the cluster for which you want to create dependencies.

3 Click Resources.

A list of cluster resources is displayed.

4 Right-click ProNetAgent and select Properties.

5 Click the Dependencies tab in the ProNetAgent Properties window and click Modify.

6 From the list of Available Resources, move the resources you want to Dependencies and click OK.

7 Restart the BMC ProactiveNet Server and Agent using pw system start command.

NOTE ■ After the BMC ProactiveNet agent is installed on both the primary and standby nodes, a

resource “ProNetAgent” will be created on the cluster.

■ For Top IP traffic to work on a remote Windows 2008 R2 64 bit agent, go to www.winpcap.org, down load WinPcap, and execute the file on standby node.


www.winpcap.org



1 Stop the BMC ProactiveNet Server and Agent using the pw system stop command.

2 Go to Start =>All Programs => Administrative Tools => Failover Cluster Manager and click on the cluster name.

3 Scroll down to Cluster Core Resources and select Properties.

4 Click on to Dependencies tab in the ProNetAgent Properties window and click Insert to add a resource.

5 Select the cluster name as a resource and click Insert.

6 Select the cluster resource with ‘AND’ option. Similarly add all the resources.

7 Click Apply and OK.

8 Restart the BMC ProactiveNet Server and Agent using the pw system start command.


C h a p t e r 11
11 Installing BMC ProactiveNet in high-availability mode on Solaris
This chapter provides instructions to install the BMC ProactiveNet Server in high-availability mode for the first time. For information about high-availability architecture, see “Preparing to install BMC ProactiveNet in high-availability mode” on page 27.

High-availability workflowFigure 3 on page 98 provides an overview of the tasks that you must perform to install and enable BMC ProactiveNet in high-availability mode on UNIX computers.


High-availability workflow

Figure 3 Workflow to install and enable BMC ProactiveNet in high-availability mode on Solaris

6

Configure the resource type created for a Sun cluster. For more information, see “Configuring the resource type” on page 151.

2

Customize the scripts to achieve BMC ProactiveNet application failover. For more information, see “Customizing the scripts to achieve BMC ProactiveNet application high-availability” on page 155.

1

High-availability installation ends.

5

4

Install the BMC ProactiveNet Server as a primary and standby node. For more information, see “Installing BMC ProactiveNet in high-availability mode on Solaris” on page 99.

Create the resource group. For more information, see “Creating the resource group” on page 152.

Create BMC ProactiveNet application resource type. For more information, see “Creating the BMC ProactiveNet resource type” on page 150.

Stop the BMC ProactiveNet Server pw sys stop. For more information, see “Stopping the BMC ProactiveNet Server” on page 141.

3

Bring the resource group online. For more information, see “Bringing a resource group online” on page 159.7

High-availability installation begins


Installing BMC ProactiveNet in high-availability mode on Solaris


The following applications are required to control high-availability for BMC ProactiveNet on Solaris:

■ Sun Cluster software■ BMC ProactiveNet

To install the BMC ProactiveNet Server as a primary and standby node on Solaris

1 Change the host name of the primary node to the logical host name configured for the cluster by entering the following command:

hostname logicalHostName

2 Change the ip address of the primary node to the logical ip address configured for the cluster by entering the following commands:

ifconfig <alias interface> plumbexample: ifconfig hme0:1 plumbifconfig <alias interface> <logical ip> netmask <netmask> upexample: ifconfig hme0:1 10.129.5.252 netmask 255.255.252.0 up

3 Install the BMC ProactiveNet Server on the primary node.

During the installation, choose the cluster file system (/global) that is shared on both nodes as the installation location.

The installation is completed successfully.

4 After successful installation of the BMC ProactiveNet Server, change the logical host name back to the host name of the primary node by entering the following command from a command line:

hostname primaryHostName

5 After successful installation of the BMC ProactiveNet Server, change the logical ip address back to the ip address of the primary node by entering the following command from a command line:

ifconfig <alias interface> downexample: ifconfig hme0:1 downifconfig <alias interface> unplumbexample: ifconfig hme0:1 unplumb



6 On the primary node, remove the following files so that the BMC ProactiveNet application does not start:

■ /etc/rc3.d/S81pronto■ /etc/rc0.d/K09pronto■ /etc/rc1.d/K09pronto

7 On the standby node, create the required links for the BMC ProactiveNet Server by entering the following commands:

ln –s /serverInstallDirectory/pw/usr/pwln –s /usr/pw/pronto /usr/prontoln –s /usr/pw/pronto/bin/pw /bin/pw

For information on post-installation tasks, refer to “14Configuring and using BMC ProactiveNet in high-availability mode” on page 149



C h a p t e r 1212 Introduction to the BMC ProactiveNet interfaces

This chapter provides an overview of the BMC ProactiveNet interfaces and how to access each interface.

Deciding which interface to useBMC ProactiveNet provides the following interfaces:

■ BMC ProactiveNet Administration Console■ BMC ProactiveNet Operations Console■ BMC ProactiveNet Command Line Interface (CLI)■ BMC ProactiveNet Service Level Objectives (SLO) Console■ Use to determine which console you should use to perform

Administering BMC ProactiveNetBMC ProactiveNet administrative functions allow you to modify and manage the BMC ProactiveNet Server and the BMC ProactiveNet Agent network management areas. Using one or more of the ProactiveNet administrative interfaces you can add or delete users, groups, monitored devices, applications, and services, or change event notifications and thresholds.

BMC ProactiveNet profiles


You can access BMC ProactiveNet administrative functions in the following ways:

■ the BMC ProactiveNet Administration Console■ the Command Line Interface (CLI)■ the BMC ProactiveNet Operations Console

For details about using the Administration CLI commands, see the BMC ProactiveNet Command Line Interface Reference Manual.

BMC ProactiveNet profilesBMC ProactiveNet acknowledges the following profiles when logging into the product:

■ Admin■ User

BMC ProactiveNet Administrator manages profiles (and access rights) for individual users.

Admin profile

Administrators have unlimited access to BMC ProactiveNet. They can configure the environment, define individual user profiles, and perform full administrative functions.

User profile

The BMC ProactiveNet administrator creates user profiles, and can restrict users from accessing BMC ProactiveNet features. The user profile (as set by the administrator) governs the functionality available to each user in the BMC ProactiveNet Operations Console.

BMC ProactiveNet enables the administrator to user assign access rights at both micro and macro levels.

NOTE Although most administrative functions are accessed using the Administration Console, some administrative options are also available through the BMC ProactiveNet Operations Console. For details, see the BMC ProactiveNet User Guide.



BMC ProactiveNet Administration ConsoleThe following sections explain how to launch the Administration Console and provide basic information for navigating the console.

Connecting the BMC ProactiveNet Administration Console to the BMC ProactiveNet Server

The BMC ProactiveNet Administration Console can connect to the BMC ProactiveNet Server using one of the following methods:

■ Direct: Use this connection protocol when BMC ProactiveNet components are installed on computers that reside on the same side of the firewall. All functionality in the Administration tab (General Administration, Event Management Policies, Dynamic Data Editor, and Infrastructure Management) and the Services Editor tab in the BMC ProactiveNet Administration Console is accessible through this connection protocol.

■ HTTP Tunnel: Use this connection protocol when the BMC ProactiveNet Server and the BMC ProactiveNet Administration Console are installed on computers that reside on different sides of the firewall. Only the General Administration functionality in the Administration tab is accessible through this connection protocol.

In an HTTPS environment, BMC ProactiveNet encrypts the information relay from the Web interface. The Administration Console uses Secured Socket Layer (SSL) connections and encryption to connect to the BMC ProactiveNet Server.

For more information about Secure Login, see the BMC ProactiveNet Administrator Guide.

Launching the BMC ProactiveNet Administration Console

Perform the appropriate procedure to start the Administration Console on your operating system.

Launching the BMC ProactiveNet Administration Console


To launch the BMC ProactiveNet Administration Console from a Microsoft Windows computer

1 On the computer where the BMC ProactiveNet Server is installed, go to Start => Programs => BMC Proactive Server => BMC ProactiveNet Admin.

2 In the BMC ProactiveNet Administration Console Logon screen, specify the following information:

■ name or IP Address of the BMC ProactiveNet Server computer to which you want to connect

■ user name with access rights to the BMC ProactiveNet Server. The default is admin.

■ password corresponding to the user name. The default is admin.

■ type of connection to use to connect to the BMC ProactiveNet Server, either Direct or HTTP Tunnel. For details about the connection types, see “Connecting the BMC ProactiveNet Administration Console to the BMC ProactiveNet Server” on page 103.

3 Click OK.

The BMC ProactiveNet Administration Console is displayed.

To launch the BMC ProactiveNet Administration Console from a Solaris computer

1 On the Solaris computer where the BMC ProactiveNet Server is installed, at a command prompt, enter the following command:

pw admin

■ name or IP Address of the BMC ProactiveNet Server computer to which you want to connect

■ user name with access rights to the BMC ProactiveNet Server. The default is admin.

■ password corresponding to the user name. The default is admin.

NOTE For remote utilization of the BMC ProactiveNet Administration Console, source the profile using the .tmcsh script located in the /usr/pw/pronto/bin directory before entering the pw admin command.

Logging out of and into the BMC ProactiveNet Server from the BMC ProactiveNet Administration Console


■ type of connection to use to connect to the BMC ProactiveNet Server, either Direct or HTTP Tunnel. For details about the connection types, see “Connecting the BMC ProactiveNet Administration Console to the BMC ProactiveNet Server” on page 103.

2 Click OK.

The BMC ProactiveNet Administration Console is displayed.


You can log out of the BMC ProactiveNet Server and log in from the BMC ProactiveNet Administration Console interface without closing the console.

To log out of the BMC ProactiveNet Server from the Administration Console

1 From the menu bar of the BMC ProactiveNet Administration Console, choose Server => Logout.

2 In the Logout Confirmation dialog box, click Yes.

To log on to the BMC ProactiveNet Server from the Administration Console

1 From the menu bar of the BMC ProactiveNet Administration Console, choose Server => Login.

2 In the BMC ProactiveNet Administration Console Logon screen, enter the password for the user name that you are using to log on to the BMC ProactiveNet Server and click OK.

The default password is admin.

Navigating the BMC ProactiveNet Administration Console

The Administration Console has two main tabs:

■ Administration—use this tab for general administration of user accounts and other ProactiveNet administration tasks, working with event management policies, working with dynamic data using the Dynamic Data Editor, and administering the BMC ProactiveNet infrastructure, such as agents and cells

BMC ProactiveNet Operations Console


■ Services Editor—use this tab to edit services. This tab provides service editing functionality only; it does not display service impact or CI status. That functionality is provided by the Operations Console.

Administration tab

The Administration tab includes the following sub-tabs, identified by these icons:

■ — General Administration

■ — Event Management Policies

■ — Dynamic Data Editor

■ — BPPM Infrastructure Management

Service Editor tab

The Services Editor tab of the BMC ProactiveNet Administration Console is the view that service managers, service administrators, and IT operations staff use to monitor business services. Service managers can view the service models that represent a company’s business services. Service models are created by organizing service model components into hierarchical relationships that can then be navigated by operators and service managers from the Services Editor tab in the BMC Proactive Administration Console or in the BMC ProactiveNet Operations Console.

In the Services Editor tab, a service manager or operator can see whether a service model component consumes the services of another service model component (consumer) or whether it provides service to another component (provider).

From the service model component, IT operations staff can view and manage the underlying events in the BMC ProactiveNet Operations Console. For more information, see the

For more information about using the BMC ProactiveNet Administration Console to monitor services, see the BMC ProactiveNet Administrator Guide.

BMC ProactiveNet Operations ConsoleThe day-to-day operations of BMC ProactiveNet are preformed using the BMC ProactiveNet Operations Console. The following sections explain how to launch the Operations Console and provide a brief overview of the Operations Console interface. For details about using the Operations Console, see the BMC ProactiveNet User Guide.

Launching the BMC ProactiveNet Operations Console


Launching the BMC ProactiveNet Operations Console

The BMC ProactiveNet Server is a web-based application and you can access it by logging on to the BMC ProactiveNet Operations Console using the web browsers specified in the BMC ProactiveNet Release Notes.

To launch to the BMC ProactiveNet Operations Console

1 Open a web browser.

2 Enter the host name or IP address of the BMC ProactiveNet Server.

3 In the BMC ProactiveNet Logon screen, enter a valid user name and password.

If you are logging on for the first time after installation, use the following default values:

■ user name: admin

■ password: admin

4 Click Log On.

Navigating the BMC ProactiveNet Operations Console

Figure 4 shows the default view in the BMC ProactiveNet Operations Console and the major areas within this console.

NOTE Avoid multiple log-ins using the same browser, user name, and password, and launching different tabs within the same browser, as this might result in NO DATA or other unpredictable results. For multiple log-ins, open separate browser windows.

NOTE The default protocol for this connection is HTTP. To log on using a secure HTTPS connection, click the link Switch to Secure Mode on the log on page.

If you use HTTPS, BMC ProactiveNet encrypts the information relay from the Web interface for additional security. Secure connection mode is indicated by the message: You are using a secure connection now.



Figure 4 BMC ProactiveNet Operations Console

Navigation tree

The navigation tree shows an at-a-glance synopsis of the events and views. Event and component folders are displayed in a hierarchical manner in the navigation tree. The folders displayed in the navigation tree are divided into the following categories:

■ Global: When you create a folder under this node, all BMC ProactiveNet users can view and access that folder.

■ My Folders: When you create a folder under this node, only you can view and access that folder.

To further organize your display, beneath these top-level folders you can add event and component folders, including folders for Component Instances (CIs) associated with a service model. Your ability to add event and component folders depends on your permissions.

Navigation Tree

Event and component folders

NavigationDrawers



Table 2 on page 21 shows the icons for the objects in the navigation tree and provides a description for each object.

In the navigation tree, the severity icons for a collector dynamically change depending on the severity level of the events for that collector. For example, if there is a Critical event on one of the devices, then the green icon changes to a red icon, indicating a Critical event. This allows you to see the status of devices on your system immediately.

For more information about event severity and status, see the BMC ProactiveNet User Guide.

Navigation drawers

In the navigation pane in the Operations Console is a series of drawers that enable you to navigate through BMC ProactiveNet functions and views. You can select which drawers that you want displayed in the navigation pane.

Table 3 Navigation tree objects and definitions

Object icon Name and definition

Navigation tree top-level node (Global). The Global node contains the following default collectors:

■ All Event Collectors—displays the entire event collector hierarchy■ All Abnormalities—displays all the abnormality events■ All Services—displays all the services■ All Groups—displays all the groups■ All Devices—displays all the devices■ All Monitors—displays all monitor categories

Based on permissions, users can create event and component folders under this node to organize the event view.

Navigation tree top-level node (Mine). Based on permissions, users can create event and component folders under this node to organize the event view.

Event group collector; an event group subnode of the navigation tree top-level node or another event group node

Child collector node

Child group node

Child service node



Table 7 on page 25 describes the available drawers in the navigation pane and describes their functions. For more information about these drawers, see the BMC ProactiveNet User Guide.

Event and component folders

Event and component folders enable you to organize cells and collectors to make event displays meaningful for operators. For example, you might create an event folder for collectors that gather database warning events and allow only operators that are database administrators access to that event folder.

You can drag and drop components from one existing folder to another within the top-level folders in the navigation tree. You also can drag and drop CIs from the Tile or Graph view to an existing folder in the All Services folder.

Event folders

An event folder is a grouping of collectors that shows the relationship of events or abnormalities through the hierarchy of the navigation tree. Administrators define event folders and associate them with one or more collectors. Each level of the collector is shown as a node under the event folder. An event list is associated with the lowest level nodes of an event folder. The parent level of an event folder represents all of the events or abnormalities associated with the collectors.

Table 4 Operations Console navigation drawers and descriptions

Drawer Description

Main provides access to event lists and displays event information and status

Other cells lists available remote cells connected to the BMC ProactiveNet Server and monitored by BMC ProactiveNet

Reports enables you to generate and manage reports based on data collected by BMC ProactiveNet.

Note: You must have permission to view this drawer.

Views & Graphs Provides options for the management of views and graphs in the Operations Console

Bookmarks enables you to view, rename, and delete bookmarks of objects and their related views that you create in the navigation tree

Find CI provides a search mechanism so that you can search for CIs that meet the specified search criteria

Note: You must have permission to view this drawer.

Operations Console views


Event collectors

Event collectors gather events for display in an event list to provide operators with meaningful groups of events or abnormalities and to show relationship through the hierarchy of the nodes in the navigation tree. To access the event list for a collector, operators click the collector node in the navigation tree.

Event collectors are dynamic or static. Nodes for dynamic collectors appear or disappear from the navigation tree based on whether or not events are present that meet the criteria for those collectors. Nodes for static collectors remain in the navigation tree whether events are present or not.

Component folders

A component folder is a grouping of groups, services, or devices from several different event lists (collectors) that shows the relationship of groups, services, or devices through the hierarchy of the navigation tree. Administrators define component folders and associate them with one or more groups, services, or devices.

Each level of the component folder is shown as a node under the parent component folder. An event list is associated with the lowest level nodes of a component folder. The parent level of a component folder represents all of the events associated with the groups, services, or devices.

There are two types of component folders, static and dynamic. Static component folders are populated by selecting from a list of objects. Dynamic component folders are populated by creating a query. Static folders always contain only the objects that you manually select. Dynamic folders contain the objects that match the query so the contents of these folders can change without further editing.


Table 5 on page 112 describes the views provided by the Operations Console. Different views are available, depending on what object is selected in the navigation tree. Each view is accessed by clicking the associated button on the Operations Console toolbar. If a view is not available for the object that is selected in the navigation tree, than the button for that view will not be displayed in the Operations Console toolbar.



Table 5 Operations Console views and associated toolbar buttons

View Description Toolbar button

Event Event view displays all events in an event list. This is the default view for all objects.

Use the Event view to check the details of events and to address events which highlight incorrect state. Probable Cause Analysis will help on identifying the event which could be the probable cause of the event specified. An event could be assigned to other users, who can acknowledge, take ownership, fix the problem and close the event. You can also address the incorrect condition by invoking Remote Actions/Detailed Diagnostics and Local Actions. The Graph View helps check the impacting service and you can cross-launch to Impact Model Designer, Service Level Manager and Product Catalog in ITSM.

You can display an Event view for:

■ event collectors■ abnormalities■ services■ groups■ devices■ monitors

Tile Tile view displays an encapsulated view of event metrics for the components that are being monitored in your environment. Use the Tile view to obtain a dashboard summary of event activity.

You can display a Tile view for:

■ event collectors■ services■ groups■ devices

Canvas Canvas view allows you to you create a graphical representation of the components that are being monitored in your environment.

The components are represented by objects that can be placed on a background image. The objects can be graphics, such as images or connectors, or metrics information represented in a tile.

You can create and display a Canvas view for:

■ event collectors■ services■ groups■ devices

Accessing the Command Line Interface (CLI)


For more information about Operations Console views, see the BMC ProactiveNet User Guide.

Accessing the Command Line Interface (CLI)Using the pw command line interface (CLI) you can execute commands on the BMC ProactiveNet Server. The pw CLIs allow you to start, stop and perform other actions on the BMC ProactiveNet Server without using the Administration Console. The pw CLIs are documented in the BMC ProactiveNet CLI Reference Guide.

Tree/Graph Tree/Graph view displays information for a selected object as a tree representing the hierarchy of the object. The tree view is is available for groups and services.

Tree view can be used to get a real-time, interactive visualization of the event status and other details of the selected group/service. In the Group hyperbolic tree the entire group hierarchy and devices are visible on a hyperbolic pane which is mapped to a circular display region. Service tree is applicable only for the selected service.

If a service is selected in the navigation tree, this view displays a graphical representation of the configuration items (CIs) in the service model and shows how those CIs relate to each other. Use the Graph view to monitor events for published service models that represent your business services.

You can display a Tree/Graph view for:

■ services■ groups

Grid Grid view displays information for the selected object in a tabular format.

Grid view can be used to view the event status and other details of the selected object as the tabular representation of the objects will have drilldown links to granular details through graphs, views and so on.

You can display a Grid view for:

■ abnormalities■ groups■ devices■ monitors

Table 5 Operations Console views and associated toolbar buttons

View Description Toolbar button

Accessing online Help


To access the pw CLI on Microsoft Windows

From the system icon tray, right-click the BMC ProactiveNet icon and choose pw commands.

To access the pw CLI on Solaris

Access the /usr/pw/bin directory and enter pw commands from that directory.

For more information about pw commands, see the BMC ProactiveNet CLI Reference Guide.

Accessing online HelpChoose Help => Online Help to access online versions of the BMC ProactiveNet documentation. Context sensitive Help is provided through Help buttons on the various dialog boxes and windows within the BMC ProactiveNet consoles.

Where to go from hereTo begin using the BMC ProactiveNet Operations Console, see the BMC ProactiveNet User Guide.

To begin using the BMC ProactiveNet Administration Console, see the BMC ProactiveNet Administrator Guide.

C h a p t e r 13
13 Post-installation tasks
This chapter provides tasks for configuring BMC ProactiveNet after installation.

Changing the BMC ProactiveNet Console passwords

For security reasons, BMC recommends that you change the passwords for the BMC ProactiveNet Administration Console and the BMC ProactiveNet Operations Console after installation.

To keep your passwords secure, you also should change them periodically.

Changing your BMC ProactiveNet Administration Console password

To change the BMC ProactiveNet Administration Console password

1 From the menu bar, choose Server => Change Password.

2 In the Change Password dialog box, in the Old Password field, enter your current password.

3 In the New Password and Confirm New Password fields, enter a new password.

NOTE In a setup where LDAP authentication is used, administrators must change the password from the LDAP server and not from the BMC ProactiveNet Administration Console.


Changing your BMC ProactiveNet Operations Console password

4 Click OK.

Your password for the BMC ProactiveNet Administration Console logon is changed immediately.

Changing your BMC ProactiveNet Operations Console password

1 Click the Options link at the top the Operations Console.

2 In the General tab, under User ID and Password, click Edit.

3 Enter the old password and the new password, and then click Apply.

Changing the Apache HTTP port numberDuring installation, port 80 is required to install the Apache web server. If you have another product installed that uses port 80 (such as the IIWS server), you must change the Apache HTTP port to another port number before you start the application that is using port 80.

To change the Apache HTTP port number

1 Open the appropriate files for your operating system:

■ UNIX: /usr/pw/apache/conf/httpd.conf

■ Microsoft Windows: pw\ApacheGroup\Apache\conf\httpd.conf and pw\pronto\conf\pronet.conf

2 Search for the string Port 80 and replace the value 80 with the desired port number.

3 Search for the string Listen 80 and replace the value 80 with the same port number provided in the previous step.

4 Save and exit the .conf files.

NOTE If you forget your password, an administrator must clear the encrypted form of your password from the configuration file. The next time that you log on, you will enter a new password, and you will be prompted to confirm it. This operation sets your new password.


Configuring BMC ProactiveNet Server to run as a non-root user after installation on Solaris

5 Search for the string Listen 80 and replace the value 80 with the same port number provided in the previous step.

Configuring BMC ProactiveNet Server to run as a non-root user after installation on Solaris

You can use the configNonRoot script to configure BMC ProactiveNet Server to run as a non-root user on Solaris. You can use this same script to switch the BMC ProactiveNet Server from one non-root user to another non-root user.

To configure BMC ProactiveNet Server to run as a non-root user on Solaris

1 From a command line, execute the following commands:

cshsource /usr/pronto/bin/.tmcshconfigNonRoot userName

2 When prompted by the configNonRoot script, provide the HTTP and HTTPS ports for Apache server.

The script performs the necessary changes.

Configuring the BMC ProactiveNet Server for 256-bit SSL encryption

To configure the BMC ProacativeNet Server to use 256-bit SSL encryption, follow these steps:

1 Stop the BMC ProacativeNet Server.

2 Create the certificate with the .der or .cer format. For example iascert.cer is generated using certsrv from Windows.

3 If you cannot access the LDAP or Active Directory server, use JXplorer (an open source LDAP browser) to export the server certificate to a file by following these steps:

A Using JXplorer, connect to the LDAP server.

B From the menu bar, choose Security => Trusted Servers and CAs.


Configuring the BMC ProactiveNet Server for 256-bit SSL encryption

C Select the appropriate certificate, and click View Certificate.

D In the General tab, click Copy to File.

E Select the file location and type the file name for the certificate.

4 Copy the certificate file to the \Program Files\ProactiveNet\pw\jre\lib\security directory.

5 Ensure that your Windows path contains the \Program Files\ProactiveNet\pw\jre\bin path.

6 Enter the following command specifying the complete certificate and keystore path:

keytool -importcert -v -trustcacerts -alias LDAP123 -file server.der -keystore pnserver.ks

7 When prompted, enter the keystore password.

The default keystore password is get2net.

8 Back up the following files in the \Program Files\ProactiveNet\pw\jre\lib\security directory:

■ local_policy.jar■ US_export_policy.jar

9 From the Sun website (http://www.oracle.com/technetwork/java/javase/downloads/index.html), download the Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files ( jce_policy-6.zip) which contain the following files:

■ local_policy.jar■ US_export_policy.jar

and copy them into the \Program Files\ProactiveNet\pw\jre\lib\security directory.

These files are required for unlimited encryption strength over a network.

10 Restart the BMC ProacativeNet Server.


http://www.oracle.com/technetwork/java/javase/downloads/index.html

Lengthening the command line for AIX

Lengthening the command line for AIXIf you have a BMC ProactiveNet remote agent installed on AIX, the number of characters accepted by the command line may not be sufficient to handle event slots that contain long statements. If the command line is too short, execution of the command will fail with an error message similar to:

command: arg list too long

To prevent this issue, BMC recommends that you extend the length of the command line on AIX operating systems. You can extend the length of the command line for AIX using the NCARGS parameter or the ARG_MAX parameter, depending on your version of AIX. For more information, see the documentation for AIX.

Moving the monitor instances from source to destination agent on Windows

The pw agent_failover CLI command and options help in balancing the load between two agents by moving the monitor instances from the source to the destination agent.


You can perform the following tasks to configure the BMC ProactiveNet Agent on Windows.

■ Change the source agent of the monitors■ Change the target IP address of the computer where the monitors are located■ Turn data collection off or on for the monitors

“Table 6pw agent_failover command options” on page 119 describes the pw agent_failover command line options.

Table 6 pw agent_failover command options

Options Description

-a <Destination Agent> name or IP address of the BMC ProactiveNet Agent where the monitors have to be moved.

-s <Source Agent> name or IP address of the BMC ProactiveNet Agent when the monitor are running.



To change the source agent of the monitors

1 On the computer that hosts the BMC ProactiveNet Server, open a command line.

2 Enter the following command:

pw agent_failover -a <Destination Agent> [-s <Source Agent> -m <Monitor Type Name> -i <Monitor Instance Name>] | [-s <Source Agent> -m <Monitor Type Name>] | [-g <Group Name>] | [-s <Source Agent> -g <Group Name>] | [-s <Source Agent> -g <Group Name> -m <Monitor Type Name>]

To update the target IP of the monitors



pw agent_failover –o <Old Target IP / Host Name / Device Name> -t <New Target IP / Host Name / Device Name>

To turn data collection off or on for the monitors:



pw agent_failover -d <on/off> [-s <Source Agent> -m <Monitor Type Name> -i <Monitor Instance Name>] | [-s <Source Agent> -m <Monitor Type Name>] | [-g <Group Name>] | [-s <Source Agent> -g <Group Name>] | [[-s <Source Agent> -g <Group Name> -m <Monitor Type Name>]

-i <Monitor Instance Name>

the name of the instance in the monitor that you want to move.

-m <Monitor Type > unique name of the monitor type.

-g <Group Name> name of the monitor group.

Table 6 pw agent_failover command options

Options Description


Moving the monitor instances from a source to destination agent on Solaris

Moving the monitor instances from a source to destination agent on Solaris

You can perform the following tasks to configure the BMC ProactiveNet Agent on Solaris.

■ Change the source agent of the monitors■ Change the target IP address of the computer where the monitors are located■ Turn data collection off or on for the monitors

“Table 7 pw agent_failover options” on page 121 describes the pw agent_failover command line options.

To change the source agent of the monitors



pw agent_failover -a <DestinationAgent> [-s sourceAgent -m <Monitor Type Name> -i <Monitor Instance Name>] | [-s <Source Agent>-m <Monitor Type Name>] | [-g <Group Name>] | [-s <Source Agent> -g <Group Name>] |

To change the IP address of the computer where the monitors are located



pw agent_failover –o oldTargetIP -t newTargetIP

Table 7 pw agent_failover options

Options Description

-a DestinationAgent unique name or IP address of the BMC ProactiveNet Agent where the monitors have to be moved.

-s SourceAgent name or IP address of the BMC ProactiveNet Agent where the monitors are running.

-m MonitorTypeName unique name of the monitor type.

-i monitor InstanceName

the name of the instance in the monitor that you want to move.

-g GroupName name of the monitor group.

-o oldTargetIP IP address of the target computer that has the IP address that you want to change

-t newTargetIP new IP address for the target computer


Configuring BMC ProactiveNet Event Adapters to start collecting events

To turn data collection off or on for the monitors



pw agent_failover -d <on/off> [-s <Source Agent> -m <Monitor Type Name> -i <Monitor Instance Name>] | [-s <Source Agent> -m <Monitor Type Name>] | [-g <Group Name>] | [-s <Source Agent> -g <Group Name>] | [[-s <Source Agent> -g <Group Name> -m <Monitor Type Name>]

Limitations and assumptions

■ The pw agent_failover CLI command can be executed only on the computer on which BMC ProactiveNet Server is installed. Remote agents can also be set up for failover. The command can be executed automatically or manually. If a BMC ProactiveNet monitor is used to determine the failure, then the command can be executed by setting appropriate thresholds and event rules.

■ Inputs for the monitors remain the same even after failover.

■ You can configure the failover by using BMC ProactiveNet monitors or clustering software such as the Sun Cluster product. Installation is the same for both the methods.

■ You cannot execute the pw agent_failover command for monitor instances that are created using the skip validation/force option. Such monitor instances might stop polling after the command is executed.

■ Agent installation (only in high-availability mode) is not supported for upgrade users.

■ Even if the monitors are moved to an agent running on a system with different IP address, monitor instances will continue showing up under the same device on which it was created even after failover.


By default, the BMC ProactiveNet Event Adapters are disabled (in fresh installations).

The BMC ProactiveNet Server installation does not start BMC ProactiveNet Event Adapters. To start BMC ProactiveNet Event Adapters, follow the procedure appropriate for your operating system.



For more information about BMC ProactiveNet Event Adapters, see the BMC Impact Event Adapters User Guide.

To start BMC ProactiveNet Event Adapters on Microsoft Windows

1 Add the license. For obtaining licenses, refer to “Applying licenses” on page 50.

2 Choose Start=>Programs=>Administrative Tools=>Services.

3 Right-click the BMC ProactiveNet Event Adapters service and choose Properties.

The BMC ProactiveNet Event Adapters Properties dialog box is displayed.

4 In the General tab, change the Startup Type to Automatic.

This configures BMC Impact Event Adapters to start automatically after reboot.

5 Click OK and start the service.

To start BMC Impact Event Adapters on UNIX-based platforms

1 Add the license. For obtaining licenses, refer to “Applying licenses” on page 50.

2 Copy the /etc/init.d/BMCProactiveNetEventAdapter file into the following directories:

■ /etc/rcS.d/K02BMCProactiveNetEventAdapter■ /etc/rc0.d/K02BMCProactiveNetEventAdapter■ /etc/rc1.d/K02BMCProactiveNetEventAdapter■ /etc/rc2.d/K02BMCProactiveNetEventAdapter■ /etc/rc3.d/S98BMCProactiveNetEventAdapter

3 Start the adapter by running the command /etc/init.d/BMCProactiveNetEventAdapter start


Configuring BMC Atrium CMDB integration

Configuring BMC Atrium CMDB integrationDuring the installation process, you have the option to configure the BMC ProactiveNet server integration with BMC Atrium CMDB. If you did not configure the BMC Atrium CMDB integration during installation, you can configure it now.

Use the following script:

NOTE I

If an error occurs indicating Event Adapter is not starting, add pkg on both the nodes.# pkgadd -d libgcc-3.3-sol9-sparc-local# csh# setenv LD_LIBRARY_PATH /usr/local/lib# echo $LD_LIBRARY_PATH

Configuring Event Adapters:/usr/pw/server/etc/mcxa.conf

Remove DISABLE from [Logfile 1] DISABLEEngine = MA::ELogfile# --Modify the following value(s) according to your environment--LogFile = /tmp/mylog.txt # Replace by the actual syslog location# Replace by the actual destination cell (if different from the global) ServerName = pncell_blr-sccluster \+++#./mcxa.sh

WARNING Before you configure the CMDB Server, ensure that BMC ProactiveNet CMDB Extensions, modules, and hotfixes are installed on the computer where the BMC Atrium CMDB is installed. For information about installing the CMDB extensions, see Chapter 3, “Preparing for BMC Atrium CMDB integration.”

integrate_atrium_cmdb -uddi_server_host_name uddiServerHostName -uddi_server_port_no uddiServerPortNumber -uddi_user_name uddiUserUame [-uddi_password uddiPassword] -cmdb_server_host_name cmdbServerHostName -cmdb_server_port_no cmdbServerPortNumber -cmdb_user_name cmdbUserName [-cmdb_password cmdbPassword]-cmdb_version cmdbVersion [-ngp_webserver_protocol webServerProtocol] [-ngp_webserver_port_no proactiveNetWebServerPortNumber]


Configuring BMC Atrium CMDB integration

where

■ uddiServerHostName is the host name of the UDDI web service where BMC Atrium CMDB is running

■ uddiServerPortNumber is the port number used by the UDDI web service on the specified host

■ uddiUserUame is the user name for the UDDI web service■ (optional) uddiPassword is the password for the UDDI web service user■ cmdbServerHostName is the host name where BMC Atrium CMDB is running■ cmdbServerPortNumber is the BMC Remedy Action Request System TCP port

number, used to log into the system server■ cmdbUserName is the user name to access the BMC Remedy Action Request

System server■ (optional) cmdbPassword is the password for the BMC Remedy Action Request

System server user■ cmdbVersion is the BMC Atrium CMDB version. Use one of the following values:

— 7.6.03 (for BMC Atrium CMDB version 7.6.03)— 7.6 (for BMC Atrium CMDB version 7.6 patch 2)— 7.5 (for BMC Atrium CMDB version 7.5 patch 5)

Use the following optional arguments if you need to enable the cross-launch into BMC ProactiveNet.

■ webServerProtocol is the web server protocol, either http (default) or https

■ proactiveNetWebServerPortNumber is the port number used by the web service. The default value is 80.

For example:

At the time of installation, if you have selected not to integrate BMC Atrium CMDB, then you need to configure IBRSD. Edit the ARSServerName parameter in the IBRSD.conf and IBRSD.dir files, located in the /usr/pw/integrations/ibrsd/conf directory.

NOTE All user names and passwords are case sensitive.

integrate_atrium_cmdb -uddi_server_host_name Vm-w23-rds1184 -uddi_server_port_no 8080 -uddi_user_name admin -uddi_password admin -cmdb_server_host_name Vm-w23-rds1183 -cmdb_server_port_no 5555 -cmdb_user_name Admin -cmdb_password Admin -cmdb_version 7.6.03 -ngp_webserver_protocol https -ngp_webserver_port_no 8888


Configuring remote cells for viewing in the Operations Console

Configuring remote cells for viewing in the Operations Console

You can view events on a remote cell once you configure the remote cell so that it can be viewed in the Operations Console. BMC recommends that you do not add a second BMC ProactiveNet cell as a remote cell. For example, if you have multiple server deployments with one master and two child servers, do not add the BMC ProactiveNet cells as remote cells.

To configure a remote cell for viewing in the Operations Console

1 Add an entry for the remote cell in the cell_info.list file located at installDirectory\pw\pronto\conf\ by entering the following command:

iadmin name=remoteCellName:key=mc:primaryHost=hostName:primaryPort=portNumber:environment=environmentType:usergroups=userGroupNames

The parameters are defined as follows:

■ remoteCellName—name of the remote cell that you want to display as defined in the mcell.dir file

■ key is the encryption key of the cell; the default is mc.■ primaryHosthostName—computer where the cell is located. Specify the

computer name and the domain name.■ portNumber—port on which the remote cell is listening; the default is 1828■ environmentType—type of environment where the cell is used; must be either

Production or Test

■ userGroupNames—name(s) of the user groups that can access the remote cell. To allow access to all user groups, enter an asterisk (*). To specify only certain user groups, enter the group names separated by commas. If a user group contains spaces, enclose the entire entry for this group name with double quotes.

2 Add an entry for the remote cell in the mcell.dir file located at InstallationDirectory\pw\server\etc\as follows:

cell cellName mc computerNameWithDomain: portOnWhichCellIsInstalled

NOTE iadmin -ac name=qa:key=mc:primaryHost=qa.company.com:primaryPort=1828:environment=Production:usergroups="Full Access, Read Only"


Registering remote cells in the Administration console

Registering remote cells in the Administration console

When you add a remote cell using the mcrtcell CLI command, you need to register the cell with the BMC ProactiveNet Server using the iadmin -ac command. Follow these steps to register remote cells in the Administration Console.

To display remote cells in the Infrastructure Management tab

1 Add the cell using the mcrtcell CLI command, as in the following example:

mcrtcell -as -ba -r -@ <variableText>hostName</variableText>/2008 -n sparkles_cell

2 Next, use the iadmin -ac command to register the cell with the BMC ProactiveNet Server. From the BMC_PROACTIVENET_HOME/server/bin directory, execute the admin -ac command as in the following example:

iadmin -ac name=sparkles_cell:key=mc:primaryHost=moondog:primaryPort=2008:failoverHost=suncat:failoverPort=2008:environment=Production:usergroups=*

The cell is added automatically to the cell_info.list of the BMC ProactiveNet Server located in the BMC_PROACTIVENET_HOME/pronto/conf directory. It is also automatically added to the admin.dir file of the Admin cell located in the BMC_PROACTIVENET__HOME/pronto/data/admin directory, as in the following example:

3 Add the cell entry to the mcell.dir file. By default, the file is located in the BMC_PROACTIVENET_HOME</variableText>/server/etc directory.

4 Restart the cell that you are registering.

NOTE cell qa mc qa.company.com:1828

cell moondog_10 mccell Admin mccell sparkles_cell mc


Configuring cell connection properties to the BMC ProactiveNet Server

5 Restart the BMC ProactiveNet Administration Console. The newly registered cell is displayed in the Infrastructure tab of the administration console. In the Event View of the BMC ProactiveNet Operations Console, you see that the cell that you have registered sends a registration event to the IAC.


The first cell that you install is connected automatically to the BMC ProactiveNet Server. If you create additional cells, the connection between BMC ProactiveNet Server and each additional cell must be configured.

To configure cell connection properties

1 From the menu bar, choose Edit => Configuration.The Edit Configuration dialog box is displayed.

2 Click the Impact Managers tab.

3 Select a cell or cell group.

4 If necessary, click Advanced to display the Cell Properties section of the dialog box.

5 Use Table 8 to set cell connection properties as required.

NOTE If you select a cell group, changes are applied to all the cells contained in the cell group. If you select single cell, changes are applied only to the individual cell.

Table 8 Cell connection properties (part 1 of 2)

Property Description

Name displays the name of the cell whose properties you are changing

Host displays the name of the host computer where the cell is installed

Port displays the port number the cell uses to connect to the host computer

Timeout specifies the length of time the console waits to receive data from the cell; default is 30 seconds

BMC ProactiveNet saves any negative Timeout values that you type as positive values.



Refresh Freq sets the time interval between polls of the cell; default is 60 seconds

BMC ProactiveNet saves any negative Refresh Freq values that you type as positive values.

Attempts sets the number of times the console attempts to connect to a cell; default is 10

BMC ProactiveNet saves any negative Attempts values that you type as positive values.

Connect Freq time interval between connection attempts; default is 5 seconds

BMC ProactiveNet saves any negative Connect Freq values that you type as positive values.

Encrypted Mode enables and disables encryption of data between the console and the cell; default is enabled (selected)

Auto Connect enables and disables automatic connection to the cell at logon; default is disabled (cleared)

Auto Switch enables and disables automatic and continuous switching of the connection from the backup cell to the primary cell after failover, using the value set in Connect Freq as the interval; default is disabled

Use Port Range enables and disables using a specified range of local ports (on the console) for establishing a connection between the console and a cell

Designating a port range is useful if the console must communicate to a cell through a firewall with only specific ports available for communication. The console scans through the specified port range until a port is connected to the cell or the connection fails because the port range is exhausted.

■ For using port range, once you select the Use Port Range check box, BMC ProactiveNet automatically changes the Min Port No. and Max Port No. values to 1.

■ If you type a value of zero in Min Port No., BMC ProactiveNet clears the Use Port Range check box.

■ If you type a value of zero in Max Port No., BMC ProactiveNet replaces it with the value of Min Port No.

■ If the value of Max Port No. is less than the value of Min Port No., BMC ProactiveNet changes the value of Max Port No. to that of Min Port No.

Min Port No. specifies the lower limit of the port range

Max Port No. specifies the upper limit of the port range

Auto Bind enables and disables the automatic connection attempt of the console to the first network card it encounters. Clear this option to bind to a specific IP address. If only one network card exists, ensure that Auto Bind is selected. See Specifying ports in cell connection properties on page 18 for additional information.

IP Address specifies the IP address assigned to the local network card to which the console connects; available only if Auto Bind is cleared

Table 8 Cell connection properties (part 2 of 2)

Property Description


Specifying ports in cell connection properties

Specifying ports in cell connection properties

The following circumstances require that you provide more specific information about communications between the console and the cell:

■ the presence of a network interface card (NIC) between the console and the cell■ the presence of a firewall between the console and the cell■ using a multi-homed computer for the console

In these circumstances, you must select Use Port Range and specify the limits of the port range and then select either Auto Bind or a particular IP address.

The Auto Bind option configures the console to connect to an NIC before it can connect to a cell. If you specify no particular NIC, the console automatically attempts to connect to the first NIC it encounters.

On a multi-homed computer, you can specify the NIC by selecting the IP address that the card is using from the IP Address list box. If Auto Bind is not enabled, you must specify a port range for the network card to which the console binds.

Setting BMC ProactiveNet Server connection properties

In addition to adding and deleting connections in the console configuration, you must configure the connections themselves, as described in this section.

To configure a BMC ProactiveNet Server

1 From the menu bar of the BMC ProactiveNet Administration Console, choose Edit => Configuration.

2 In the Edit Configuration dialog box, click the Login Servers tab.

NOTE If the console is running on a computer that is acting as a gateway between multiple subnets, the network card that you bind to must be on the same subnet as the cell to which the console connects.



3 Modify any of the BMC ProactiveNet Server configuration parameters listed in “Table 9BMC ProactiveNet Server configuration parameters” on page 131, as needed:

4 Click Apply to save the changes, or click OK to save and exit the dialog box.


You can log out of the BMC ProactiveNet Server and log in from the BMC ProactiveNet Administration Console interface without closing the console.

Table 9 BMC ProactiveNet Server configuration parameters

Field Description

Heartbeat Rate specifies the frequency, in minutes, at which the console sends a signal to the connected BMC IAS to determine whether the BMC IAS is functioning. The default heartbeat rate is 1.

Enable Port Range specifies the maximum and minimum port number for the console to use in establishing a connection to a BMC Impact Administration Server

Designating a port range is useful if the console must communicate to a cell through a firewall with only specific ports available for communication. The console scans through the ports in the specified range until a port, local to the console, is connected to the cell or fails because the port range is exhausted.

Auto Reconnect enables and disables automatic attempts to reconnect to the BMC ProactiveNet Server when the connection has been dropped

The Administration Console will attempt to reconnect to the server at the Frequency and for the Number of Retries that you specify.

If, after the final try the server is still not reconnected, an error message is displayed stating that the server is down, and you must manually restart the server and log back on to the Administration Console.

A status message is displayed in the status area of the Administration Console showing the number of reconnection attempts.


Adding Agents

To log out of the BMC ProactiveNet Server from the Administration Console

1 From the menu bar of the BMC ProactiveNet Administration Console, choose Server => Logout.

2 In the Logout Confirmation dialog box, click Yes.

To log on to the BMC ProactiveNet Server from the Administration Console

1 From the menu bar of the BMC ProactiveNet Administration Console, choose Server => Login.

2 In the BMC ProactiveNet Administration Console Logon screen, enter the password for the user name that you are using to log on to the BMC ProactiveNet Server and click OK.

The default password is admin.

Adding AgentsUse the Add Agent option to add an agent after a device has already been set up. To monitor a device specifically on UNIX computers, you need to add an agent. For Windows, you may add an agent if you want to monitor for example, disks and file system.

To set up the device and the agent simultaneously, see the BMC ProactiveNet Administrator Guide.

The BMC ProactiveNet local agent (BMC ProactiveNet Agent) resides on the computer where the BMC ProactiveNet Server is installed. Remote agents are agents that reside on computers outside of the BMC ProactiveNet Server.

To add an agent after the device is set up

1 In the Administration Console, expand the Device folder.

2 Right-click the device where you want to add the agent.


Adding Agents

3 In the Add Agent window, enter the following information:

4 Choose one of the following Connection options:

■ Direct Access using TCP/IP - choose if the remote agent uses TCP/IP.

■ Direct Access using SSL TCP/IP - choose if the remote agent uses SSL TCP/IP.

■ HTTP Tunnel Proxy - choose if the remote agent uses an HTTP Tunnel. For installation about Tunnel agents, see the BMC ProactiveNet Administrator Guide.

■ TCP Proxy - choose if the remote agent uses TCP Proxy. For further details, see the BMC ProactiveNet Administrator Guide.

5 Click Next to create the agent.

When the agent is created, a second Add Agent window is displayed, in which you can choose the monitor for the device

6 Choose the monitor.

7 Follow the procedure in “Selecting monitors for the device” on page 140.

To view the new agent, expand (or close and expand) the Agents folder. To view the monitor, expand (or close and expand) the p folder.

If a problem occurs while you are adding an agent, BMC ProactiveNet displays an error message. For more information, see the BMC ProactiveNet Administrator Guide.

Field Description

Control Port The default control port (TCP connection port) is 12124. Change the port if 12124 is forbidden by a firewall or if it is being used by an existing application.

To change the port, click Close, and then see the BMC ProactiveNet Administrator Guide.

Agent Name BMC ProactiveNet inserts the device name that you specified.

Agent IP Address BMC ProactiveNet inserts the IP Address (or name of the Agent if using DNS) that you specified in the IP Address field when you created the device.

Associated Device BMC ProactiveNet lists devices with the same IP address. By default, the one created on the previous screen is selected.


Getting started with devices

Getting started with devicesThe following sections give an overview of available devices and provide instructions for properly creating devices.

Summary of devices

You add devices to BMC ProactiveNet through the Device folder on the Administration Console. When you add a device for BMC ProactiveNet to monitor, you are initially presented with the Add Device window in which you identify the device by type.

BMC ProactiveNet offers the following device type categories:

■ AppServer■ DBServer■ Firewall■ MailServer■ Other■ RemoteAgent■ Router■ Server■ Switch■ WebServer

BMC ProactiveNet automatically creates a set of default monitors for each device type. After you add a device to BMC ProactiveNet, you can choose to monitor applications residing on the device or collect statistics from its Management Information Base (MIB), as described in the BMC ProactiveNet Administrator Guide.

For detailed information about individual BMC ProactiveNet monitors, see the BMC ProactiveNet Monitor Guide.

Using device aliases

BMC ProactiveNet uses aliases to associate internal and external events to devices. Device alias are generated when a device is created. They can be generated automatically by BMC ProactiveNet or you can define them.


Avoiding duplicate devices

BMC ProactiveNet compares the device aliases from events with the alias defined for each device, and when a match is found, the event is associated with the device that matches the alias.

Aliases generated automatically are prefixed with BMC_ComputerSystem and use the following naming conventions, depending on how the device is generated:

■ BMC_ComputerSystem:Host Name:DomainFor example, BMC_ComputerSystem:test.bmc.com

■ BMC_ComputerSystem:IPFor example, BMC_ComputerSystem:10.134.12.10

■ BMC_ComputerSystem:TokenID

When the BMC ProactiveNet cell receives an event, the event is processed as follows, depending on whether the event is internal or external:

■ For internal events, BMC ProactiveNet compares the device ID from the device alias with the device ID from the event and if a match is found, then the event is associated with the device.

■ For external events, BMC ProactiveNet compares other alias values, such as BMC_ComputerSystem:Host Name:Domain or BMC_ComputerSystem:IP, with the event mc_sms_alias slot value, which contains device information. If a match is found, then the event is associated with the device.

■ If no matches are found, then the event does not get associated to any device.

■ When a device is created, update, or deleted in the Administration Console, the device is also created, updated, or deleted in the BMC ProactiveNet cell.


Avoiding duplicate devices

In BMC ProactiveNet, a device can be created in the following ways:

■ through one of the following adapters:

— BMC PATROL Adapter— BMC Portal Adapter— Native VMware Adapter— System Center Operation Manager (SCOM) Adapter— BMC Transaction Management Application Response Time (BMC TM ART)

Adapter


Creating a device

■ manually by using the Administration Console or a Command Line Option

■ integrating with the BMC Atrium CMDB

When duplicate devices are created

Duplicate devices could result if multiple different sources that use different naming conventions are used to create the devices; for example, if the PATROL adapter uses the host name of the computer where the device is located to name the device and the BMC Atrium CMDB uses the IP address of the computer where the device is located to name the device, then duplicate device instances would be created in BMC ProactiveNet.

Avoiding creating duplicate devices

Duplicate devices are not created in the following situations:

■ if devices are created by only one source■ if devices are created from different sources independently■ if different sources use the same naming convention when creating the devices; for

example, IP address, host name, or fully qualified domain name

Best practices for device creation

To avoid creating duplicate devices, ensure that

■ the device is created using the fully qualified domain name of the host computer where the device is located

■ if the device is referenced from multiple adapters that each adapter must use the fully qualified domain name of the device

Creating a device

Before adding devices, have the following information available:

■ A list of devices (by type) to add

■ DNS names, if you want to add devices by name

■ IP addresses, if you want to add devices by their IP address


Creating a device

■ For servers, a list of applications running on each server and a checklist of applications that you want to monitor

■ For adding SNMP devices, a list of MIBs and community strings for each device.

BMC ProactiveNet Server uses the community string as a password for MIB access. If you do not enter a community string, the default community string, public, is used.

To create a device

1 In the BMC ProactiveNet Administration Console, select the Devices folder, right-click, and choose Add => Device.

2 In the Add Device window, choose the Configuration tab.

3 From the Device Type list, choose a device type.

4 In the Device Name field, specify the name of the device.

If the device name is a DNS name, then the device name will be filled in automatically if it has not already been set. This may take a few moments.

5 In the DNS Name / IP Address field, specify the IP address of the device.

NOTE If you are not using the DNS, ensure that the BMC ProactiveNet Server IP address exists on the DNS server, mail server, or hosts file. This should have been completed during BMC ProactiveNet Server installation. If the IP address is not included, BMC ProactiveNet cannot poll the device and issues an error message. To verify the BMC ProactiveNet Server environment settings, see “Installation requirements” on page 17.

NOTE Ensure that you select the correct device type. The device type is used by the Probable Cause Analysis algorithm to determine correlations between events and abnormalities within the system. If the device type is not accurate, the Probable Cause Analysis may not be accurate.

For example, if a computer is a Web Server, set the device type as WebServer (not just Server).

NOTE Ensure that you do not use any special characters, such as /, in the device name. If the device name includes special characters, then you cannot see the monitors for the device when you click on the device name in the Grid view of the BMC ProactiveNet Operations Console.


Creating a device

The 127.0.0.1 IP address is the loop back address for any computer and should not be added to the Device List. If the device IP address has a DNS name, then the device name will be filled in automatically if it has not already been set.

6 In the Tag field, choose a descriptive tag about the device that you are creating by following these steps:

A Click the plus icon to display the Enter Tag Details dialog box.

B Choose a Tag Class and enter a Tag Value.

For example, if the device that you are creating is located in a particular city, you would select Location as the Tag Class and then specify the city where the device is located (such as Auckland) as the Tag Value. Tag Class is not mandatory. The Tag Value used as a keyword is currently useful in the Rule base groups functionality.

C Click Add to enter the values that you specify, and then click Finish to return to the Add Device dialog box.

7 In the Aliases field, add one or more aliases to the device that you are creating. Use device aliases to associate events to the device, so that remote actions can be performed on those associated events. For details about remote actions, see the BMC ProactiveNet Administrator Guide.

8 In the Secondary IPs area, view any secondary IP addresses that may be associated with the device that you are creating.

The first IP address that is associated with the Device Name that you specify is used as the primary IP address. Any additional IP addresses are used as secondary IP addresses. If no secondary IP addresses exist, then N.A is displayed in this field. To view all secondary IP addresses, click on the ellipses button.

9 In the Device Description field, enter a description for the device that you are creating.

10 If you have installed a BMC ProactiveNet Agent on this device, select the Agent Installed on Device option. Some monitors require an agent to be installed on the target device.

11 Click the Control tab to edit the control attributes.

Information in the Control tab tells the BMC ProactiveNet Server about the desired data collection and polling frequencies for the device. You can accept the defaults or change them as required.


Creating a device

12 Select the SNMP Data Collection option to enable BMC ProactiveNet Server to collect data for the entire device. If this option is not selected, data collection for the device stops (or for new devices, never starts).

This flag lets you set up monitors for devices that may not yet be online. Or, you can conduct maintenance on existing devices without generating events.

13 In the SNMP Read Community String you can change the password for BMC ProactiveNet Server access to the device MIB.

To change this entry, you must have prior knowledge of how this device is set up. For example, if this device is set up for the Community String snmpget, then enter snmpget.

14 In the SNMP Retries field, specify how many times (count) BMC ProactiveNet Server must request data from the device before reporting an event. Default is 2 retries.

15 In the SNMP Timeout field, specify the duration (in seconds) BMC ProactiveNet Server must wait for data from the device before reporting an event. Default is 2 seconds.

16 Select the SNMP Use V2 option if the device is using version 2 of the protocol.

17 Click the Group tab and enter the required information.

This tab enables you to add a device and its monitors to one or more groups. Optionally, you may associate the device with a group. A group is used to logically organize devices and monitors by department, geographic area, or service. Assigning a device to a group also enables the system administrator to restrict or allow access to certain devices by group. If you want the device to be associated with a group, select the group name here.

18 Click the Remote Actions/Diagnostics tab and enter the required information.

■ Protocol Types—select a protocol type from the list. The supported protocols are psExec, ssh (Secure Shell), and Telnet.

■ PortNo—the default port number of the selected Protocol Type is displayed.

■ Remote User Name—enter the remote user name. This is mandatory for all Protocol Types.

■ Remote User Password—enter the remote user password. This is mandatory for psExec, ssh, and Telnet protocol types. Confirm the remote user password.


Selecting monitors for the device

19 Open the Baseline tab.

By default, no device is selected when you access the Baseline tab. When you select a device to copy baseline values from, then for all monitors being added to the new device, a corresponding monitor is searched on the selected device. If matching monitors are present, then all baseline values (hourly and weekly) are copied from the existing monitor to the new monitor instances being created.

20 Click Finish to save your actions and execute all remaining actions (using defaults).

21 After reviewing the summary panel, click Finish.

Selecting monitors for the device

Based upon the device type selected in the Configuration tab, the system automatically pre-selects some default monitors and pre-selects the Monitor tab. For example, for the device type Server, the NodePing monitor is pre-selected; and if an agent is installed on the device, System and TCP/IP and Agent Status monitors are pre-selected, and the System tab is pre-selected. You can add additional monitors for the applications and components installed on the device.

To select monitors for a device

1 Create a device for the system that you want to monitor.

2 Add an agent to that device.

3 Select the monitors that you want to create for this device from the Select Monitors to Create screen.

NOTE If you choose the Telnet option from the protocol type list, you will have to fill in the information for the remote system prompt as described in the example.

For example, if the remote system prompt is [root@kadamba root]#, then you should enter correctly in the remote system prompt field. You should not use a partial system prompt, for example, # for [root@kadamba root]# , which might prevent the system from logging into the remote device. The maximum number of characters supported for remote system prompt is 512 characters.

For detailed information about Remote Actions, see the BMC ProactiveNet Administrator Guide.


Stopping the BMC ProactiveNet Server

If the device has more than one application that needs monitoring, for example, a server running Mail and IP services, select all of the monitors here using the various tabs, or go back and add the monitors later.

4 Click Next.

The configuration windows appear for each monitor you selected.

The Configuration window contains specific entry fields, as shown in this example. Refer to the BMC ProactiveNet Monitor Guide for detailed instructions regarding setting the parameters for the monitors.

Notice that each monitor also has a Control tab, which specifies the data collection and polling frequency for individual Application, Intelliscope, or SNMP Monitors. And similar to the Configuration tab, the input fields in the Control tab vary depending on the selected monitor.

5 Click Skip if you have selected several monitors to add and you change your mind about one of them or you are uncertain about an entry field.

Clicking Skip moves on to the next monitor’s configuration. The skipped monitor is not added. The program continues normally. When the last monitor is configured, the Summary screen appears to show what was created.

6 Click Finish.

To view the new device listing, expand (or close and expand) the corresponding device folder.

Stopping the BMC ProactiveNet ServerThe installation process automatically starts the BMC ProactiveNet Server. If you want to stop the BMC ProactiveNet Server, follow the procedure appropriate for your operating system.

To stop the BMC ProactiveNet Server on Microsoft Windows

1 From the system icon tray, right-click the BMC ProactiveNet icon .

2 Choose Server Stop.


Starting the BMC ProactiveNet Server

To stop the BMC ProactiveNet Server on Solaris

1 Access the pw CLI.

2 Enter pw sys stop.

Starting the BMC ProactiveNet ServerOnce you have stopped the BMC ProactiveNet Server, you must restart it manually. To restart the BMC ProactiveNet Server, follow the procedure appropriate for your operating system.

To start the BMC ProactiveNet Server on Microsoft Windows


2 Choose Server Start.

To start the BMC ProactiveNet Server on Solaris


2 Enter pw sys start.

Checking the status of the BMC ProactiveNet Server

To check the status of the BMC ProactiveNet Server on Microsoft Windows


2 Choose Server Status.

NOTE After the status of the BMC ProactiveNet Server changes, it may take a little time for the system tray icon to reflect the change, depending on your environment.


Enabling and disabling Integration Services

To check the status of the BMC ProactiveNet Server on Solaris


2 Enter pw sys status.

Enabling and disabling Integration ServicesThe Integration service is installed automatically when you install a BMC ProactiveNet Agent.

Enabling the Integration Service to gather data from products that integrate with BMC ProactiveNet

During the installation process, you have the option to enable the Integration service. If you did not enable the Integration service during installation, but want to enable it now, follow these steps.

To enable the Integration service on Microsoft Windows

1 Open the custom\pronet.conf file and change the value of the pronet.apps.agent.patrol.proxy.enabled property to TRUE.

2 From a command line, import pns.reg as follows:

■ If you are enabling the Integration service on a remote agent enter: Regedit /s InstallationDirectory \Agent\pproxy\PNS\security\pns.reg

■ If you are enabling the Integration service on a BMC ProactiveNet Server enter: Regedit /s InstallationDirectory \pw\pproxy\PNS\security\pns.reg

3 From a command line, register pproxsrv.exe as a service on the desired port as follows:

■ If you are enabling the Integration service on a remote agent enter: InstallationDirectory\Agent\pproxy\PNS\bin\pproxsrv.exe -install -p 3182 -m


Disabling the Integration Service

■ If you are enabling the Integration service on a BMC ProactiveNet Server enter: InstallationDirectory\pw\pproxy\PNS\bin\pproxsrv.exe -install -p 3182 -m

4 Restart the BMC ProactiveNet Agent service.

To enable the Integration service on UNIX or Linux

1 Open the /usr/pw/custom/conf/pronet.conf file.

2 Change the value of the pronet.apps.agent.patrol.proxy.enabled property to TRUE.

3 Restart the BMC ProactiveNet Agent by executing the following command:

pw process restart pronet_agent

Disabling the Integration Service

To disable the Integration Service, follow these steps.

1 Open the appropriate file for your operating system:

■ For Microsoft Windows: custom\pronet.conf

■ For UNIX or Linux: /usr/pw/custom/conf/pronet.conf

2 Change the value of the pronet.apps.agent.patrol.proxy.enabled property to FALSE.

3 Restart the BMC ProactiveNet Agent as appropriate for your operating system:

■ For Microsoft Windows: restart the BMC ProactiveNet Agent service■ For UNIX or Linux: execute pw process restart pronet_agent

NOTE The default port for the Integration service is 3182. If you want to register on a different port, substitute that port number in the registration command and update the custom\pronet.conf file with the new port number.

NOTE Restarting the BMC ProactiveNet Agent will not stop the pproxy service.


Specifying a particular IP address for the BMC ProactiveNet Agent

Specifying a particular IP address for the BMC ProactiveNet Agent

By default, BMC ProactiveNet creates a generic bind for the BMC ProactiveNet Agent that accepts all incoming requests.

For computers with multiple IP addresses, you can specify a particular IP address or interface for the remote agent to listen to requests. To do this, set the pronet.apps.agent.bindaddress property in the pronet.conf file to a specific IP address.

Changing the BMC ProactiveNet Server IP address

You might need to change your IP address for the local agent if you are using a Network Address Translation (NAT) firewall, or you have a connectivity issue.

To change the IP address of the BMC ProactiveNet Server

1 From the Administration Console, choose Advanced Options=>Agent.

2 Right-click ProactiveNet Server and choose Edit.

3 In the Edit Remote Agent dialog box, replace the DNS Name/IP address with the new IP address.

4 Click OK to close the dialog box and save your changes.

5 Restart the local agent.

Configuring e-mail settings to receive alertsReview the e-mail settings on the server target computer to ensure that it is configured to receive e-mail alerts from BMC ProactiveNet. If it is not, an error or warning message similar to the following is displayed:

Warning: ProactiveNet’s e-mail alerts may not work with the current configuration

If this message is displayed, perform the following procedure.


Configuring e-mail settings to receive alerts

To configure e-mail settings to receive alerts from BMC ProactiveNet

1 Review the e-mail settings and make any necessary changes, as described in Table 10:

2 After you modify the e-mail settings, verify the configuration by using one of the following scripts, depending on your operating system:

■ UNIX: /usr/pw/pronto/bin/TestEmail.sh ■ Microsoft Windows: installDirectory\pw\pronto\bin\TestEmail.bat

A Success or Failure message is sent to the administrator’s e-mail address and is added to the TestEmail.log file that is located in the same directory as the verification script.

You can run the script multiple times until the email settings are configured correctly.

Table 10 E-mail settings required to receive alerts from BMC ProactiveNet

Setting LocationParameter or property to change Correct format

Administrator's e-mail address

■ UNIX: /usr/installDirectory/etc/hosts/admin_user

■ Microsoft Windows: installDirectory\pw\etc\hosts\admin_user

admin_user a fully qualified e-mail address in the following format: [email protected]

Sender's e-mail address

■ UNIX: /usr/installDirectory/etc/hosts/from_name

■ Microsoft Windows: installDirectory\pw\etc\hosts\from_name

from_name ‘user’ or [email protected], depending on the valid From address accepted by the SMTP server

SMTP server hostname or IP address

■ UNIX: /usr/installDirectory/custom/conf/pronet.conf

■ Microsoft Windows: installDirectory\pw\custom\conf\pronet.conf

pronet.api.emailer.smtp.host

a fully qualified server hostname or IP address reachable from the BMC ProactiveNet Server host

SMTP port ■ UNIX: /usr/installDirectory/custom/conf/pronet.conf

■ Microsoft Windows: installDirectory\pw\custom\conf\pronet.conf

pronet.api.emailer.smtp.port

a valid port number on which the SMTP server is listening for SMTP requests


Accessing online Help

Accessing online HelpChoose Help => Online Help to access online versions of the BMC ProactiveNet documentation. Context sensitive Help is provided through Help buttons on the various dialog boxes and windows within the BMC ProactiveNet consoles.

Where to go from hereTo begin using the BMC ProactiveNet Operations Console, see the BMC ProactiveNet User Guide.

To begin using the BMC ProactiveNet Administration Console, see the BMC ProactiveNet Administrator Guide.

For information about monitors, see the BMC ProactiveNet Monitor Guide.

NOTE The first time you access the online Help after launching a console, it may take some time for the online Help to be displayed.


Where to go from here


C h a p t e r 14
14 Configuring and using BMC ProactiveNet in high-availability mode
The following sections help you through the post-installation procedures that you need to perform to enable high-availability.

Configuring the BMC ProactiveNet Server in Sun cluster

Sun cluster identifies the health of the nodes in the cluster with device group configured for the BMC ProactiveNet application. Sun cluster checks the status of device group configured for the BMC ProactiveNet application to verify the nodes in the cluster, which are online and functioning well. Based on the status, the sun cluster enables the BMC ProactiveNet service to be available on the online node.

On Sun Cluster, the application needs to be identified with a resource group. The Sun Cluster uses the resources present in the resource group for high-availability.

1 Create BMC ProactiveNet application resource type. This is necessary to register the BMC ProactiveNet Server as the application for high-availability. For more information, refer to “Creating the BMC ProactiveNet resource type” on page 150.

2 Create a resource group that specifies the resources that need to be used for high-availability and the resources included are:

■ Logical host name ■ Application (BMC ProactiveNet Server)

For more information, refer to “Creating the resource group” on page 152.


Creating the BMC ProactiveNet resource type

Creating the BMC ProactiveNet resource type

Use the agent builder utility to create the resource type for the BMC ProactiveNet product. This utility is part of the Sun Cluster installation.

Perform the following procedure on each node in the cluster.

To create the resource type on Solaris computers

1 Start the agent builder utility by entering the following command:

/usr/cluster/bin/scdsbuilder

2 In the agent builder window, provide information for the following items:

3 Click Create.

4 Click Next.

5 In the configure window, provide information for the following items:

Item Description

Vendor Name Name that identifies the vendor of the resource type. Typically, the name is SUNW.

Application Name Name of the resource type.

RT Version Version of the generated resource type. The version is by default 1.0.

Working Directory Directory under which the agent builder creates a directory structure to contain all the files that are created for the target resource type. You can create only one resource type in any working directory. Under the working directory, agent builder creates a subdirectory with the resource type name.

Ensure that both the primary and secondary nodes in the cluster have the same working directory name. For example, if SUNW is the vendor name and pnbmc is the application name, then the agent builder names this subdirectory as SUNWpnbmc.

Scalable or Failover Target resource type. Select Failover.

C, ksh Language of the generated source code. Select ksh.


Configuring the resource type

6 Click Configure.

The agent builder generates a resource type (data service) that includes source and executable code (Korn shell), a customized Resource Type Registration (RTR) file, and a Solaris package for the BMC ProactiveNet product.

The Solaris package contains the RTR file in the /etc directory. The file is named based on the values that you entered for Vendor Name and Application Name in the agent builder window. For example, if the Vendor Name is SUNW and the Application Name is pnbmc, then the name of the RTR file would be SUNW.pnbmc. Open the RTR file and ensure that the RT_BASEDIR parameter is set to the path of the /bin directory. For example, if the path to the /bin directory is /opt/SUNWpnbmc/bin, then the value for the RT_BASEDIR parameter should be /opt/SUNWpnbmc/bin.

The Solaris package also contains start, stop, and probe scripts for the BMC ProactiveNet application resource type in the /bin directory. Provide execute permissions for all the generated scripts in the /bin directory.

Configuring the resource type

Perform the following procedure on the primary node of the cluster.

Item Description

Start Command (or file) The complete command line to pass to any UNIX shell to start the base application:

/usr/pw/pronto/bin/pw system start

Stop Command (optional) The complete command line to pass to any UNIX shell to stop the base application:

/usr/pw/pronto/bin/pw system stop

Probe Command The command to run periodically to check the health of the application.

The command returns an exit status between 0 (success) and 100 (complete failure). If you do not specify a probe command, the generated code simply connects to and disconnects from the port that is used by the resource. If the connect and disconnect succeeds, the generated code declares the application healthy.

Timeout A timeout value, in seconds, for each command. You can specify a new value or accept the default value that the agent builder provides. The default value is 300 seconds for start and stop and 30 seconds for probe.


Creating the resource group

To configure a resource type

1 Ensure that the BMC ProactiveNet application RTR file exists in the /opt/cluster/lib/rgm/rtreg directory or /usr/cluster/lib/rgm/rtreg directory.

If it does not exist in one of these two directories, copy the RTR file that is in the /workingDirectory/resourceType/etc directory to either the /opt/cluster/lib/rgm/rtreg directory or /usr/cluster/lib/rgm/rtreg directory. For example, if you created a resource type named SUNW.pnbmc using the agent builder, then the name of the RTR file is SUNW.pnbmc. Copy that file from the /opt/SUNWpnbmc/etc/ directory to the /opt/cluster/lib/rgm/rtreg directory or the /usr/cluster/lib/rgm/rtreg directory.

2 Register a resource type by entering the following commands:

clresourcetype register resourceTypeclresourcetype show resourceType

The following output is displayed

=== Registered Resource Types ===Resource Type: resourceType:1.0RT_description: pnbmc server for Sun ClusterRT_version: 1.0API_version: 2RT_basedir: /opt/resourceType/binSingle_instance: FalseProxy: FalseInit_nodes: All potential mastersInstalled_nodes: <All>Failover: FalsePkglist: resourceTypeRT_system: False

The variable resourceType is the resource type created using the agent builder as described in the procedure “Creating the BMC ProactiveNet resource type” on page 150.


A high-availability resource group contains the following types of resources:

■ Logical hostname resource - Network address resource, which is an instance of the Logical Hostname built-in resource type.

■ Application resource - High-availability resource, which is an instance of the BMC ProactiveNet resource type created by using the agent builder.



1 Create an ordered list of zones for the resource group by entering the following command:

clresourcegroup create -n nodeZoneList resource

The variable nodeZoneList specifies a comma-separated, ordered list of zones for this resource group, and the variable resource specifies the name of the high-availability resource group that you want to create.

For example:

clresourcegroup create –n pacific, atlantic pnbmc_rgclresourcegroup show -v pnbmc_rg

The following output is displayed.

=== Resource Groups and Resources ===Resource Group: pnbmc_rgRG_description: <NULL>RG_mode: FailoverRG_state: ManagedRG_project_name: defaultRG_affinities: <NULL>RG_SLM_type: manualAuto_start_on_new_cluster:TrueFailback: FalseNodelist: pacific atlanticMaximum_primaries: 1Desired_primaries: 1RG_dependencies: <NULL>Implicit_network_dependencies: TrueGlobal_resources_used: <All>Pingpong_interval: 60Pathprefix: <NULL>RG_System: FalseSuspend_automatic_recovery: False

2 Add a Logical Host Name Resource to the resource group by entering the following command:

clreslogicalhostname create -g resourceGroup -h hostNameList resource

The variable resourceGroup specifies the name of the resource group in which this resource resides. The variable hostNameList specifies a comma-separated list of UNIX logical host names by which clients communicate with services in the resource group. The variable resource specifies an optional resource name of your choice.

For example:

clreslogicalhostname create -g pnbmc_rg -h artic pnbmc_lgclresource show pnbmc_lg




=== Resources ===Resource: pnbmc_lgType: SUNW.LogicalHostname:2Type_version: 2Group: pnbmc_rgpR_description:Resource_project_name: defaultEnabled {pacific}: TrueEnabled {atlantic}: TrueMonitored {pacific}: TrueMonitored {atlantic}: True

3 Add a BMC ProactiveNet application resource to the resource group by entering the following command:

clresource create -g resourceGroup -t resourceType \ [-p"extension-property [{node-specifier}]" =value ...] [-p standardProperty=value ...] resource

The variable resourceGroup specifies the name of a high-availability resource group. This resource group must already exist. The variable resourceType specifies the name of the resource type for the resource. The variable standardProperty=value specifies a comma-separated list of standard properties that you set for the resource. The standard properties that you can set depend on the resource type. The variable resource is the name of the resource to add.

For example:

clresource create –g pnbmc_rg –t SUNW.pnbmc-p Network_resources_used=pnbmc_lg pnbmcclresource show pnbmc

The following output is displayed:

=== Resources ===Resource: pnbmcType: SUNW.pnbmc:1.0Type_version: 1.0Group: pnbmc_rgR_description:Resource_project_name: defaultEnabled {pacific}: TrueEnabled {atlantic}: TrueMonitored {pacific}: TrueMonitored {atlantic}: True

For example,

clresource create –g resourceType_rg –t RTRFileName –p Port_list=“2638/tcp, 12128/tcp integrationServicePortNumber/tcp” -p Network_resources_used=resourceType_lg resourceType


Customizing the scripts to achieve BMC ProactiveNet application high-availability

4 Tune the BMC ProactiveNet application resource properties to achieve high-availability by using the following formula:

Retry_Interval = (Thorough_probe_interval + Probe_timeout) * 2 * Retry_count

Thorough_probe_interval is the time interval that the probe command sleeps. The default 60 seconds. To account for the time that it takes to bring the BMC ProactiveNet Server up, set this value to 600 seconds.

Retry_Count specifies the number of restart attempts. The default is 2. BMC recommends that you set this value to 1 or 0 to achieve efficient high-availability. For the BMC ProactiveNet application, it is set to 1.

5 Run the following commands for the BMC ProactiveNet application to set the Thorough_probe_interval and the Retry_Count:

clresource set –p START_TIMEOUT=600 resourceTypeclresource set –p STOP_TIMEOUT=600 resourceTypeclresource set –p Thorough_probe_interval=600 resourceTypeclresource set –p Retry_Count=1 resourceType


The scripts are generated while creating the cluster resource type. On each node in the cluster, edit the appropriate scripts to:

■ Disable the PMF monitoring■ Get the proper license files■ Start the BMC ProactiveNet application■ Enable the cron jobs

The scripts are available under the /bin directory of the Solaris package generated by the agent builder.

To customize scripts to achieve high-availability

1 Open the start script (resourceType_svc_start.ksh) for editing.

2 Disable the PMF monitoring by entering the following command:

pmfadm -s $PMF_TAG -a "$action -R $RESOURCE_NAME -G $RESOURCEGROUP_NAME\-T $RESOURCETYPE_NAME" $start_cmd_args



The daemon under the control of the Sun Cluster Process Monitor Facility starts. Let it crash and invoke the action script provided. The action script will restart the resource or enable high-availability and will return a non zero exit status to cease the process monitor facility.

3 At the end of the PMF monitoring command in resourceType_svc_start.ksh file, add the following lines under the User added code placeholder section and before the line “exit 0”.

# User added code -- BEGIN update_license_file/usr/pw/pronto/bin/pw system startenable_cron# User added code -- END

4 Copy the node-specific license files to the /usr/pw/licenses directory and add the appropriate extension as follows:

■ Rename the license files targeted to the primary node with the extension .primary

■ Rename the license files targeted to the secondary node with the extension .secondary

The files should look as follows:

/usr/pw/licenses/*.primary /usr/pw/licenses/proactivenet.lic.primary/usr/pw/licenses/proactivenet.sign.primary/usr/pw/licenses/*.secondary /usr/pw/licenses/proactivenet.lic.secondary/usr/pw/licenses/proactivenet.sign.secondary

5 Above MAIN in the start script, provide the proper licenses and enable cron jobs for BMC ProactiveNet as described in the following steps:

A On the primary node, update the license files by entering the following commands:

update_license_file() {cp /usr/pw/licenses/proactivenet.lic.primary/usr/pw/licenses/proactivenet.liccp /usr/pw/licenses/proactivenet.sign.primary/usr/pw/licenses/proactivenet.sign}

B On the secondary node, update the license files by entering the following commands:



update_license_file() {cp /usr/pw/licenses/proactivenet.lic.secondary/usr/pw/licenses/proactivenet.liccp /usr/pw/licenses/proactivenet.sign.secondary/usr/pw/licenses/proactivenet.sign}

C Create a cron folder in the /usr/pw/ directory and a file called cron_entries in the /usr/pw/cron/ directory and add the following lines:

# begin_pronto -- DO NOT DELETE THIS LINE!## the following entry is added for BMC ProactiveNet## Changed on Mar 13, 2009 10:31:53:AM PST##15 * * * * /usr/pw/pronto/bin/hourlyjobs > /usr/pw/pronto/tmp/hrjob.log2>&130 3 * * 1-6 /usr/pw/pronto/bin/dailyjobs hosts >/usr/pw/pronto/tmp/dajob$$.log2>&130 4 * * 0 /usr/pw/pronto/bin/weeklyjobs hosts >/usr/pw/pronto/tmp/wkjob$$.log2>&130 5 * * 0 /usr/pw/pronto/bin/pw database archive /usr/pw/dbarchivesend-email >/usr/pw/pronto/tmp/dbarchive$$.log 2>&10,15,30,45 * * * * /usr/pw/pronto/bin/check_pronetprocs >/usr/pw/pronto/tmp/check_pronetprocs.log 2>&1## end_pronto -- DO NOT DELETE THIS LINE!

D To enable the cron jobs, specify the following path in the start script:

enable_cron() {crontab -l > /tmp/$$current_cronwhile read line; doecho "$line" >> /tmp/$$current_crondone < /usr/pw/cron/cron_entriescrontab < /tmp/$$current_cronrm /tmp/$$current_cron}

6 Save and close the start script.

7 Open the stop script (resourceType_svc_stop.ksh) and edit it to disable the cron jobs and stop the BMC ProactiveNet application as described in the following steps.



A Add the following lines to the stop script:

# The Data service is not running as of now. Log a message and# exit suceess.# SCMSGS# @explanation# Need explanation of this message!# @user_action# Need a user action for this message.scds_syslog -p error -t "${SYSLOG_TAG}" -m \"resourceType not already running"/usr/pw/pronto/bin/pw system stopdisable_cron# Even if the resourceType is not running, we exit success,# For idempotency of# the STOP method.exit 0

B Above the Main section in the stop script, add the following function:

disable_cron() {crontab -l | sed -e /pronto/d|sed -e /ProactiveNet/d > /tmp/$$prontocrontab < /tmp/$$prontorm /tmp/$$pronto}

8 Save and close the stop script.

9 Open the probe script (resourceType_probe.ksh) and add the following lines to support manual shutdown of the BMC ProactiveNet application:

if [[ -e "/usr/pw/pronto/tmp/system.start" ]]; thenif [[ -f $probe_cmd_prog && -x $probe_cmd_prog ]]; thenhatimerun -t $PROBE_TIMEOUT $probe_cmd_args# User added code -- BEGIN vvvvvvvvvvvvvvv# User added code -- END ^^^^^^^^^^^^^^^else# We were not supplied with a probe command. We will use the# simple_probe that comes bundled as an utility.hatimerun -t $PROBE_TIMEOUT $RT_BASEDIR/simple_probe \-R $RESOURCE_NAME -G $RESOURCEGROUP_NAME \-T $RESOURCETYPE_NAME# User added code -- BEGIN vvvvvvvvvvvvvvv# User added code -- END ^^^^^^^^^^^^^^^fielsecontinuefi

10 Save and close the probe script.


Running BMC ProactiveNet in high-availability mode

Running BMC ProactiveNet in high-availability mode

1 After making the necessary changes in the generated scripts, stop the BMC ProactiveNet Server.

2 Bring the BMC ProactiveNet resource group online on the primary node of the cluster by executing the command in “Bringing a resource group online” on page 159.

Bringing a resource group online Execute the following commands to bring the resource group online:

clresourcegroup online -emM resourceGroupNameclresourcegroup online -emM resourceType_rg

Manually switching the BMC ProactiveNet application to the standby node

If you want to switch the BMC ProactiveNet application to the standby node in the cluster, you can switch manually by using the following command:

# clresourcegroup switch [-n node] resource_group

■ -n node specifies the name of the node on which the resource group is to be switched

■ resource_group specifies the name of the resource group of the node to which you are switching

For example:

clresourcegroup switch –n atlantic pnbmc_rg

This command switches the BMC ProactiveNet application to the standby node, atlantic, from the primary node in the pnbmc_rg resource group.


Disabling failover for BMC ProactiveNet

Disabling failover for BMC ProactiveNetIf you do not want the primary node to switch to the standby node (for example, when the standby node is shut down for maintenance), you can disable failover.

You can disable the failover feature by taking the resource group of the primary node offline by using the following command:

clresourcegroup offline resource_group

For example:

clresourcegroup offline pnbmc_rg

clresourcegroup status


=== Cluster Resource Groups ===Group Name Node Name Suspended Status---------- --------- --------- ------pnbmc_rgp pacific No Offlineatlantic No Offline

Configuring high-availability remote cells for viewing in the Operations Console

You can view events on a remote cell in high-availability mode once you configure the remote cell so that it can be viewed in the Operations Console.

To configure a remote cell in high-availability mode for viewing in the Operations Console

1 Add an entry for the remote cell and its counterpart in high-availability mode in the installDirectory \pw\pronto\conf\cell_info.list file as follows:

cell cellName encryptionkey computer1NameWithDomain:portOnWhichCellIsInstalled computer2NameWithDomain:portOnWhichHACellIsInstalled Production *

For example, cell testcell mc testcomp: 1828 hacomp: 2251 Production *

2 Add an entry for the remote cell and its counterpart in high-availability mode in the serverInstallationDirectory\server\etc\mcell.dir file as follows:



cell cellName mc computer1NameWithDomain: portOnWhichCellIsInstalledcomputer2NameWithDomain: portOnWhichHACellIsInstalled

3 Restart the jserver process.

4 Click OK.


C h a p t e r 15
15 Uninstalling BMC ProactiveNet
Should a problem occur that causes an unstable or unusable installation of the product, you can use the procedures described in this chapter to uninstall BMC ProactiveNet.

Uninstalling the BMC ProactiveNet Server on Windows

To uninstall the BMC ProactiveNet Server for Windows

1 Choose Start => Programs => BMC ProactiveNet Server => Uninstall BMC ProactiveNet Server.

2 On the Confirm Uninstall screen, click OK to uninstall BMC ProactiveNet Server.

3 When installation is successful, you will be prompted to restart your system.

NOTE After uninstalling BMC ProactiveNet Server, reboot the computer and delete any installation directories or files that remain.


Uninstalling the BMC ProactiveNet Agent on Windows

Uninstalling the BMC ProactiveNet Agent on Windows

To uninstall the BMC ProactiveNet Agent for Windows

1 On the computer where you installed the BMC ProactiveNet Agent, open the Control Panel.

2 In the Control Panel, double-click Add/Remove Programs to open the Add/Remove Programs window.

3 To open the uninstallation wizard, select BMC ProactiveNet Agent, and click Change/Remove.


5 On the Maintenance Complete screen, click Finish to complete the uninstallation.

Uninstalling the BMC ProactiveNet Server on Solaris

This section explains how to uninstall the BMC ProactiveNet Server from a Solaris computer.

Before you begin

■ To prevent unnecessary error messages from occurring during the uninstallation process, from a command line, run the following command as root:

source /usr/pw/pronto/bin/.tmcsh

■ If you are a non-root user and you want to uninstall BMC ProactiveNet Server, the following directory and file must be removed by a root user before a non-root user can proceed with the uninstallation:

— /etc/init.d/BMCImpactIBRSD

— /usr/pw/pronto/conf/resources/en_US/kbinfo/kb_core_resource.properties


Uninstalling the BMC ProactiveNet Agent on UNIX-based operating systems

To uninstall ProactiveNet Server

1 From a command line, access the /usr/pw/pronto/bin directory.

2 Execute the uninstall_server script.

The script uninstalls BMC ProactiveNet Server, except for a few entries in the cron and usr pw directories.

3 To remove the usr pw directory, run the following command as root:

rm -R /usr/pw

This command deletes the cron entries, /etc/rc* directories, and any remaining BMC ProactiveNet Server entries.

Uninstalling the BMC ProactiveNet Agent on UNIX-based operating systems

This procedure will remove all files, programs, saved data, and related directories of your Agent (UNIX) installation. Uninstalling the BMC ProactiveNet Agent will also uninstall the cell.

To uninstall the BMC ProactiveNet Agent on UNIX

1 From a command line, switch to the partition where BMC ProactiveNet is installed and access the installDirectory/pw/pronto/bin/ directory.

2 Run the following commands:

source .tmcshuninstall_agent

NOTE To ensure that the related directories are removed, restart your server after uninstalling the BMC ProactiveNet Agent. Under some conditions, the related directories are removed only after restart.

NOTE To remove a particular agent, you must run the uninstall_agent script from the bin directory of the agent you want to uninstall.


Uninstalling the BMC ProactiveNet Server on a cluster in high-availability mode on Windows

3 At the prompt, confirm removal of the agent by entering y to continue.

4 If the cell is present with the agent, you will be prompted with “Uninstalling this agent will also uninstall the cell. Do you want to continue?”

If you specify y, uninstallation will proceed to uninstall both the cell and the agent and if you specify n uninstallation will exit.

Uninstalling the BMC ProactiveNet Server on a cluster in high-availability mode on Windows

To uninstall the BMC ProactiveNet Server for Windows on primary node

1 Choose Start => Programs => BMC ProactiveNet Server => Uninstall BMC ProactiveNet Server.


3 When installation is successful, you will be prompted to restart your system.

To uninstall the BMC ProactiveNet Server for Windows on standby node

Use ForceUninstall.exe to uninstall the BMC ProactiveNet server.

NOTE After uninstalling BMC ProactiveNet Server, reboot the computer and delete any installation directories or files that remain.


Uninstalling the BMC ProactiveNet Agent on a cluster in high-availability mode on Windows

Uninstalling the BMC ProactiveNet Agent on a cluster in high-availability mode on Windows

To uninstall the BMC ProactiveNet Agent for Windows on primary node

1 On the computer where you installed the BMC ProactiveNet Agent, open the Control Panel.

2 In the Control Panel, double-click Add/Remove Programs to open the Add/Remove Programs window.

3 To open the uninstallation wizard, select BMC ProactiveNet Agent, and click Change/Remove.


5 On the Maintenance Complete screen, click Finish to complete the uninstallation.

To uninstall the BMC ProactiveNet Agent for Windows on standby node

Use ForceUninstall.exe to uninstall the BMC ProactiveNet agent.

Uninstalling the BMC ProactiveNet Server on a cluster in high-availability mode on UNIX- based operating systems

To uninstall the BMC ProactiveNet on a cluster

1 Disable the resource group. For more information, refer to “Disabling failover for BMC ProactiveNet” on page 160

2 From a command line, access the /usr/pw/pronto/bin directory.

3 Execute the uninstall_server script.

The script uninstalls BMC ProactiveNet Server, except for a few entries in the cron and user pw directories.

4 To remove the /usr/pw directory, run the following command:


Uninstalling the BMC ProactiveNet Administration Console on UNIX-based operating systems

/rm -R /usr/pw

5 This command deletes the cron entries, /etc/rc* directories, and any remaining BMC ProactiveNet Server entries.

6 Uninstall the BMC ProactiveNet Server. Refer to Chapter 15, “Uninstalling BMC ProactiveNet.”

7 After uninstalling the server, delete the resource and the resource group that were used to set up the server in the clustered environment.

Uninstalling the BMC ProactiveNet Administration Console on UNIX-based operating systems

The following procedure removes all files, programs, saved data, and related directories of the Administration Console installation.

To uninstall the Administration Console on UNIX

1 From a command line, access the admin_console_installDirectory/UninstallBMCProactiveNet directory.

2 Run the following command: ./uninstall

3 At the prompt, confirm the removal of the Administration Console.

4 To ensure that related directories are removed, restart the host.

Removing the Oracle database objectsIf the Oracle database objects are not deleted while uninstalling BMC ProactiveNet Performance Management, you can delete them manually. Run cleanup_db.sql script in the install directory under Server_pw_v8.5_bxxxxxxx\Utilities\oracle\db_cleanup_script.


*166630**166630**166630**166630*

*166630*