13.12.2012 Views

HP OpenView Operations Administrator's Reference - filibeto.org

HP OpenView Operations Administrator's Reference - filibeto.org

HP OpenView Operations Administrator's Reference - filibeto.org

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Installing and Updating the OVO Configuration on the Managed Nodes<br />

Selective Distribution of User-selected Files to Managed Nodes<br />

210<br />

A configuration file seldist is provided in which node group names<br />

together with file name prefixes and files are listed. For details about<br />

seldist configuration file, see “The seldist Configuration File” on<br />

page 211.<br />

The advantages of this distribution include the reduction of the<br />

following:<br />

❏ disk space utilization on managed nodes<br />

❏ network traffic during configuration file distribution<br />

If selective distribution is not enabled, the standard distribution of<br />

user-selected files is performed.<br />

How Does Selective Distribution Work?<br />

On starting configuration file distribution from the OVO GUI or<br />

command line, the distribution manager (opcdistm) checks the selective<br />

distribution configuration and when the distribution process of actions,<br />

commands or monitors is started, Selective Distribution in accordance<br />

with the requirements of the seldist file is started.<br />

On distribution, every file from the customer actions|cmds|monitor<br />

directories is compared against each file name prefix in the seldist file.<br />

If it does not match any prefix, it is distributed to all agents of the<br />

respective platform.<br />

If it matches one or more entries, it is only distributed to the agents of<br />

the corresponding node group(s). For example, an empty seldist file<br />

would result in all files being distributed to all nodes.<br />

In a MoM environment, you must manually ensure synchronization of<br />

the seldist files on all of your OVO management servers.<br />

Most Database SPI files have a dbspi prefix, SAP SPI files have an r3<br />

prefix, so an example of a SAP SPI binary would be named r3perfmon.<br />

In addition to the preconfigured SPI-related files, you may also add your<br />

own files and file prefixes together with a node group name. This is most<br />

useful if you have your own templates and accompanying scripts that<br />

only need to be distributed to a subset of the nodes. For more<br />

information, see the section “To Configure Custom Selective<br />

Distribution” on page 217.<br />

Chapter 3

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!