HP Operations Manager

Configuring external nodes


Nodes for external events are used in HPOM to handle the following types of messages:

Each external node must be uniquely identified by specifying properties for that node. Use the following property sheets in the External Node Properties dialog box to specify the unique details that identify each external node. Required information is specified.

Configure external nodes using the wizard

To quickly configure a new external node, use the External Node Configuration wizard. This will provide the minimum amount of information you need to bring the external node under management.
Note NOTE:
At any time you can exit the wizard by clicking Expert Mode. This returns you to the External Node Configuration editor, where you can more completely specify the characteristics of this node. You cannot return to the wizard from the External Node Configuration editor. When you add another external node, the wizard opens again.

To open the wizard

  1. Open the Node Configuration editor if it is not already open.
  2. From within the Configure Managed Nodes dialog box, select the Nodes folder in the managed nodes list.
  3. Right-click to open the shortcut menu.
  4. Select New External Node to open the wizard.
  5. In the General page, type the Display name in the box provided. You must supply this information to proceed. The caption appears in the External Nodes list. Enter any comments or additional information in the Description box. This information is optional.
  6. Click Next to continue to specify the settings you want for this node.
  7. In the Pattern page, type the pattern that you want the external node to match. The pattern you create here will be checked against the option you specify in Check pattern against.

    The pattern acts as a filter that defines the external node. For example, if the pattern is ROS* then all messages with node IDs that match this pattern will be associated with the external node and will only appear in the browser for that node. The first match found determines to which node the message belongs. When an incoming message matches a node pattern, the evaluation stops and the message appears in the browser for that node.

    Examples:

    • To match fully-qualified domain names

      To include all IP names in the domain, "deu.hp.com", use the following example: <*>.deu.hp.com

    • To match an IP address range

      For example, to set up an IP address range to match all addresses between 15.136.123.5 (including) and 15.136.123.72 (excluding), use the following example: 15.136.123.<5 -le [<#>] -lt 72>

    • To match a specific string

      To match a specific string, remember to enclose the string with the (^) and ($) characters in the following manner: ^STRING$. This pattern matches only STRING and excludes similar strings such as STRING1 or FIRSTSTRING.

    Note NOTE:
    Click the button to the right of the Pattern box to help you enter variables and operators for numeric comparison. Click Test Pattern... to open the Test Pattern dialog box where you can create a pattern and enter strings to immediately compare your pattern.

  8. Specify what the pattern should match in the Check pattern against group box. Choose from Fully Qualified Domain Name, IP Address, or Node Name. This selection clarifies any possible ambiguity in the pattern. For example, a pattern like *15* could refer to an IP address like 15.1.2.2, or to a node name like ROS15test. By selecting IP Address or Node Name, you avoid any confusion about the meaning of the pattern.
    • Fully Qualified Domain Name

      If Fully Qualified Domain Name is the pattern choice, the filter will ignore the IP address for this pattern.

    • IP Address

      If IP Address is the pattern choice, only valid IP strings are evaluated.

    • Node Name

      If Node Name is selected, the filter matches the node name.

  9. Click Next to proceed to the wizard's Order page.
  10. Select Check Before Managed Nodes to have external nodes evaluated before managed nodes. This can be faster, because it avoids some of the checking that occurs with configured node names. When this box is checked, messages with node IDs that match the pattern you specified in the previous page are associated with the external node. If this box is not checked, the managed node takes precedence.
  11. The two lists display all external nodes that have been created. The list order shows the order of evaluation set for incoming messages. The node being edited can be moved from one list to the other by using the Check Before Managed Nodes check box. Use the Move Up and Move Down buttons to change this order. The node at the top of the list will be evaluated first. After the first node has matched, the message is assigned to that node and no further evaluation takes place.
  12. Click Finish to complete the configuration and close the wizard.

To configure an external node

  1. Open the Node Configuration editor if it is not already open.
  2. In the Nodes list, right-click the external node you want to configure to open the External Node Properties dialog box. Use the tabs to display information about the selected node and to configure it:
    • General: provide a required caption and an optional description.
    • Details: provide the owner information and specify the node match pattern.
    • Order: displays the order of evaluation for the existing external nodes.
    • Outage: displays the current outage state.
  3. Click Apply as you finish with a tab to apply your changes.
  4. Click OK to confirm your changes and close this dialog box.
  5. Click Cancel to close the dialog box without saving your changes.