HP OpenView System Administration Handbook [Electronic resources] : Network Node Manager, Customer Views, Service Information Portal, HP OpenView Operations نسخه متنی

اینجــــا یک کتابخانه دیجیتالی است

با بیش از 100000 منبع الکترونیکی رایگان به زبان فارسی ، عربی و انگلیسی

HP OpenView System Administration Handbook [Electronic resources] : Network Node Manager, Customer Views, Service Information Portal, HP OpenView Operations - نسخه متنی

Tammy Zitello

| نمايش فراداده ، افزودن یک نقد و بررسی
افزودن به کتابخانه شخصی
ارسال به دوستان
جستجو در متن کتاب
بیشتر
تنظیمات قلم

فونت

اندازه قلم

+ - پیش فرض

حالت نمایش

روز نیمروز شب
جستجو در لغت نامه
بیشتر
لیست موضوعات
توضیحات
افزودن یادداشت جدید

14.10 DISTRIBUTION


The administrator distributes the policies and instrumentation from the server to managed node. During distribution to the node, the distribution manager is called to establish connection with the node. The ovconfd process on the server pushes the distribution to the node. The ovconfd process on the node ensures that the files are placed into the proper directories and complete the installation process.

The staging area for the distribution is located in the directory /var/opt/OV/share/tmp/OpC/distrib. The server moves the compressed configuration files into this directory. The filename is the hexadecimal format of the node's IP address.

14.10.1 Template Group to Node Group Assignment


Template to node assignment was covered in Section 14.6.5, "Template Assignment." For bulk distribution to many nodes, it is more efficient to assign the node to a node group and perform the distribution to the entire node group. After the templates are assigned to a node group, use the GUI to distribute the templates.

Another feature available is called the hidden node group. Use a "hidden" node group for distribution purposes. The new node group is not assigned to any operators. See Figure 14-29.

Figure 14-29. Create hidden node groups using the Configuration window.

[View full size image]

height="144" SRC="/image/library/english/10090_14fig29.gif" >

14.10.1.1 Assign the Templates to the Nodes or Node Groups

The steps to assign the template policies to a node group are shown here for reference:


  1. From the menu in the Node Bank, select

    ActionsAgentsAssign Templates .

  2. Select

    Add to display the Add Configuration window, as shown in Figure 14-30.

    Figure 14-30. The Define Configuration window lists the current template to node and node group assignments.

    [View full size image]

  3. From the Add Configuration window, select Open Template window as displayed in Figure 14-31.

    Figure 14-31. The default and custom template groups are listed in the Template window.

    [View full size image]

  4. In the Template window, select the template or template group (the selected group in the example is highlighted).

  5. In the Add Configuration window, select Get Template Selection. The selected template group appears in the Add Configuration window.

  6. Close the Template window.

  7. In the Add Configuration window shown in Figure 14-32, click

    [OK] .

    Figure 14-32. The Add Configuration window now shows the selected template group and the node group to which it is assigned.

    [View full size image]

  8. Return to the Define Configuration window as shown in Figure 14-33. Click

    [OK] .

    Figure 14-33. The Define Configuration window lists the existing and new node group assignments.

    [View full size image]

  9. From the Node Group menu, highlight the Node Group.

  10. From the menu in the Node Bank, select

    ActionsAgentsInstall/Update Configuration . Select Templates from the components list, see Figure 14-34. If you have created customized instrumentation, also select Actions, Commands, and Monitors. Click

    [OK] .

    Figure 14-34. The distribution of components is controlled from the Install/Update Configuration window.

    [View full size image]

You can distribute templates, actions, monitors, and commands for each distribution, and unless you select the "Force Update" box, you will still only distribute the elements that have changed since the last distribution. This helps avoid distributing templates without their related instrumentation. Selecting the "Force Update" option redistributes all assigned templates and instrumentation for the target node(s). Don't forget to locate customized actions, commands, or monitors in the customer directory path prior to distribution to ensure the latest versions are transferred to the managed node.
The customer directory path is /var/opt/OV/share/databases/OpC/mgd_node/customer
/<vendor>/<architecture>/<OS>

/<actions>|<cmds>|<monitor>.

/ 276