Import configuration data from Operations Manager

You can migrate the following types of configuration data from OM to Monitoring Automation:

• Policy templates. OM supports agent, server, and Event Correlation Services (ECS) policies.

  You can export the policies from OM and import them into Monitoring Automation. The OM for Windows server policies and ECS policies cannot be migrated.

• SiteScope templates. SiteScope templates can be imported in the following ways:

  • The template can be imported directly from a SiteScope server. For more information, see Import SiteScope templates.

  • The template may have been imported to OM for UNIX or Linux earlier, in which case it is stored on OM for UNIX or Linux as a policy. This policy can then be transferred to Monitoring Automation together with other policies.

• Template groups. In OM, policy groups are sets of policies that share some common attribute or logical connection. Policy groups enable you to more easily work with multiple policies simultaneously. For example, you can deploy all policies in a group to managed nodes together.

  You can export policy groups from OM and import them into Monitoring Automation. The policy groups appear under Template Groups in the Policy Templates manager.

• Instrumentation. Instrumentation consists of one or more programs, which are deployed with policies to nodes that have the HPE Operations Agent. The programs are scripts or executables that can be used by policies.

  Instrumentation is grouped into categories. Policies can be associated with instrumentation categories to ensure that OM automatically deploys the instrumentation when it deploys the policy.

  When you export policy configuration data from OM, you can choose to include any associated instrumentation categories. If you import this configuration data, the instrumentation categories will be available in Monitoring Automation. You can deploy the instrumentation categories with individual policies, and you can add the instrumentation to aspects.

• Script parameters in measurement threshold policies. In OM, you can create measurement threshold policies that contain VBScript or Perl scripts. The scripts can do complicated calculations, evaluate thresholds, or add functionality. Script parameters enable you to change the values of variables in the script without the need to edit the script itself.

  When you import measurement threshold policies from OM, any script parameters are converted to Monitoring Automation policy template parameters.

• Automatic and operator-initiated commands. OM policies can create events (called messages in OM) that include automatic and operator-initiated actions (also known as commands in OM for Windows):

  • Automatic actions can run locally on a managed node when the HPE Operations Agent detects the event.

    HPOM can run automatic actions on the management server or a managed node when the event arrives on the management server. HPOM can also run remote automatic actions. Operators can restart automatic actions manually from the HPOM message browser.

    A remote automatic action is an action that is attached to an event sent by a node and configured to run on another node.

    OMi can run automatic and remote automatic actions on managed nodes. Automatic actions can also run on the OMi server. You can restart an automatic or remote action on any node manually from the OMi Event Browser.

  • HPOM operators can start operator-initiated actions manually from the HPOM message browser, after evaluating the details of the event.

    Similarly, OMi users can start operator-initiated actions manually from the OMi Event Browser.

  OMi checks the Originating Server event attribute to determine which server should start the action. If the Originating Server attribute is empty, OMi starts the action. If the originating server is an Operations Management server, the action request is transferred to the Operations Management server for execution. The originating server is the server that initially forwarded the original event along the chain of servers configured in a flexible management environment.

  When you import policies from OM to OMi, any automatic and operator-initiated actions are included. Actions that include the variable <$OPC_MGMTSV> only run on Operations Management servers, not on OMi servers. To run these actions on the OMi server, replace the variable <$OPC_MGMTSV> with the name of the server.

The following types of data can be forwarded dynamically from OM to OMi:

• Messages (including message operations such as acknowledgment, annotations, and so on)

• Action requests and responses for tools executed on the agent through OM

• Topology changes, including addition, modification, and deletion of nodes, node groups, and services

  For the initial synchronization, you must forward all the topology data that already exists on an OM management server. (You can do this using the tool startInitialSync on the source OM server.)

You can use the command-line interface ConfigExchange to check and validate whether OM policies are compatible with Monitoring Automation. The tool generates a Policy Parser Report, which contains the following information:

• Summary of the number and types of problems and incompatibilities

• Policies without problems

• Policy files containing Event Correlation Services (ECS)

• Policy file problem details

After the import to Monitoring Automation, you can use the policy editors to edit each policy with reported problems and change the policy to comply with Monitoring Automation policy templates. It is important that all problems are corrected before deploying the policy templates to an agent.

The following data cannot be imported from OM to OMi:

• Event Correlation Services (ECS) policies

• Users, user profiles, and responsibility matrices

• Message groups

• Tool definitions

• Assignments (for example, the assignment of policy groups to nodes)

• Server-related policies and configuration data (for example, trouble tickets, notification definitions, message-stream configuration data, and configuration settings)

• Heartbeat monitoring configurations

You can export policies, policy groups, and instrumentation from OM for Windows using the ovpmutil tool on the OM for Windows management server:

ovpmutil cfg pol dnl <folder> /p <identifier> [/instrum]

• Replace <folder> with the path of a folder into which you want to download the policy configuration data.

• Replace <identifier> with the path to a policy group from which to download policies. The policy group path can be constructed similar to the path to a policy, as shown in the console tree, starting under Policy groups. Start the policy group path with a backslash (\), and separate sub-groups with a backslash (\) too. If the name of a policy group contains spaces, enclose the entire path in quotation marks.

  Example policy group path: "\Samples\Flexible Management\Follow the Sun"

• Add /instrum if you want to export any associated instrumentation categories.

For more information on ovpmutil, see Operations Manager for Windows Online Help.

To download policies, policy groups, and instrumentation from OM for UNIX or Linux, you can use the Administration UI, the opccfgdwn command-line interface, or the opcpolicy command-line interface. See the sections below for more information.

• Administration UI. You can use the shopping cart functionality to export policies, policy groups, and instrumentation. Proceed as follows:

  1. In the Administration UI, click Browse > All Policy Groups.

  2. Select policy groups in the list, and then click Choose an action > Add to Shopping Cart.

  3. Optional. Click Browse > All Categories. Select any categories of instrumentation that the policies require, and then click Choose an action > Add to Shopping Cart.

  4. Click Browse > Shopping Cart, select the policy groups and instrumentation categories that you want to download, and then click Choose an action > Download Shopping Cart. Type a comment, and then click OK.

  5. Click Browse > Downloads, select the sub-folder with your download data, and then click Choose an action > Archive as ZIP. Click View Archive Directory, and then click the name of the archive file to download it.

     The downloaded data is also available in the following directory on the management server:

     /opt/OV/OMU/adminUI/data/clipboard/

     Copy the downloaded directory tree to OMi and upload it into the Monitoring Automation database using the ConfigExchange command-line interface.

• opccfgdwn. The opccfgdwn command is used to download the OM on UNIX configuration data. This configuration download utility, located in the /opt/OV/bin/OpC directory, enables you to select the parts of configuration that you want to download and save the data to flat files in the file system. The downloaded configuration data can then be copied to the OMi server running Monitoring Automation and uploaded into the Monitoring Automation database using the ConfigExchange command-line interface.

  Unless specified otherwise, the opccfgdwn command stores the configuration data in the form of a directory tree to the following location on the OM on UNIX system: /var/opt/OV/share/tmp/OpC_appl.

  The opccfgdwn command requires the download specification file (DSF, download.dsf ) as an input file, where you specify which configuration entities need to be downloaded. The DSF lists the specified objects in the following format:

  POLICY "MyPolicy" ;
POLICY_GROUP "MyPolicyGroup1" ;
POLICY_GROUP "MyPolicyGroup2" ;
  

  For more information on the DSF syntax, see the opccfgdwn man page. For the information on how to create the download specification file and download the required configuration files, see the OM for UNIX documentation.

  Note It is recommended that you create an empty download specification file that will download all existing configuration. See the OM for UNIX documentation for instructions.

  Once the download.dsf file is created and the configuration is downloaded to <downloadDir>, do the following:

  1. Copy <downloadDir> to the OMi server running Monitoring Automation:

     # scp –r <downloadDir> <OMisystem>:<inputDir>

  2. Run the following command:

     <OMi_HOME>/opr/bin/ConfigExchange.sh -username <username> -password <password> -uploadOM -input <inputDir>

  ConfigExchange uploads the configuration data compatible with OMi (policies, policy groups, and the associated instrumentation) exported from OM for UNIX to the Monitoring Automation database using <inputDir> as the input directory.

  Note that some configuration data is not compatible with OMi and therefore cannot be uploaded by ConfigExchange. For details, see Validating OM Policies and Limitations.

  For more information on ConfigExchange, see ConfigExchange Command-Line Interface.

  Import of OM for UNIX 8.x instrumentation

  If you migrated from OM for UNIX 8.x to OM for UNIX 9.x, you will find the instrumentation files in the /var/opt/OV/share/databases/OpC/mgd_node/customer directory. Note that OM for UNIX 9.x supports two types of instrumentation directory structure: the format used by OM for UNIX 8.x and the format introduced with OM for UNIX 9.x, which is compatible with the format from OM for Windows and with OMi.

  If opccfgdwn is used as the download utility, the OM for UNIX 8.x-style instrumentation data is automatically converted into the format compatible with OMi at the upload time. All OM for UNIX 8.x instrumentation is placed into the OMU_customer_data instrumentation category located in the /var/opt/OV/share/databases/OpC/mgd_node/customer directory. After the configuration data is downloaded, copy it to the OMi server running Monitoring Automation and upload it using the ConfigExchange command. See the previous section for detailed information.

  After the instrumentation is imported into OMi, you can link it to an aspect and assign it to appropriate nodes.

  Note OMi does not support the OM on UNIX selective distribution feature. This means that all instrumentation files from the OMU_customer_data category are selected for deployment by OMi (and not just those specified in the /etc/opt/OV/share/conf/OpC/mgmt_sv/seldist configuration file).

• opcpolicy. opcpolicy downloads policies and policy groups, as well as associated instrumentation.

  To export policy group <policyGroup> and associated instrumentation from OM for UNIX or Linux to the directory <downloadDir>, run the following command on the OM for UNIX or Linux server:

  opcpolicy -download pol_group=<policyGroup> dir=<downloadDir>

  You can also export a single policy instead of a policy group. For example, to export version 1.0 of the open message interface policy Oracle messages and the associated instrumentation, run the following command:

  opcpolicy -download pol_name="Oracle messages" pol_type="Open_Message_Interface" version=1.0 dir=/tmp

  For more information, see the opcpolicy man page.

Validate and import the downloaded OM policies, policy groups, and instrumentation:

1. Copy the output folder or archive file from the OM server to the OMi server, and if necessary extract the files from archive.

   • Exported policy files are stored in the following folder:

     <downloadDir>/<policyVersionId>_<suffix>

   • Exported policy groups are stored in the following file:

     <downloadDir>/PolicyConfig_<policyGroupId>.xml

   • Exported instrumentation files are stored in the following folder:

     <downloadDir>/Instrumentation/<categoryName>

2. On the OMi server, check if the policies copied from OM to Monitoring Automation are compatible with Monitoring Automation and log the results to <LogFile>. Run the following command:

   ConfigExchange -check -policyfile <policyDir> -logfile <logFile>

3. On the OMi server, upload the OM policies, policy groups, and instrumentation using the ConfigExchange command-line tool:

   ConfigExchange -username <username> -password <password> -uploadOM -input <inputDir>

   • Replace <username> with the user name of an OMi user with permission to create policy templates.

   • Replace <password> with the password of the OMi user.

   • Replace <inputDir> with the path to a folder that contains the policy data and instrumentation. The folder must be the output of ovpmutil (OM for Windows) or a download started from the Administration UI or opcpolicy (OM for UNIX or OM for Linux).

   Example:

   The following command uploads policies, policy groups, and instrumentation from a folder called 'example_policy_group':

   <OMi_HOME>\opr\bin\ConfigExchange.bat -username myU -password myPW -uploadOM -input c:\Users\Administrator\Desktop\example_policy_group

4. Check the generated log file that contains the policy parser report. For each policy file with reported errors, using the policy editors, modify the policy to suit your requirements.

For details on ConfigExchange, see ConfigExchange Command-Line Interface.

Policies without problems: 4 of 11 (36.36%)


Potential policy problems:

ECS-Policies:            Error    1 of 10
Patterns:                Error    9 of 10

Actions:
  Server Var:            Error    10 of 36 
  Server Exe:            Error    9 of 36 
  Var in Action String:  Error    0 of 36 
  Pwd encryption:        Error    0 of 36 

Forwarding rules (MPI_SV_...):
  In # of conditions:    Warning  0

Server functionality (TroubleTicket, Notification, INSTRUCTION_TEXT_INTERFACE):
  In # of conditions:    Warning  10

Suspicious instructions:
  In # of conditions:    Warning  1

Policies without problems
-------------------------

[OK] /data/Work/Unified-Config/Policies_for_test/cd56be9e-fee3-71e0-1bf0-1039249e0000_data
[OK] /data/Work/Unified-Config/Policies_for_test/dfa1c17a-fee3-71e0-1bf0-1039249e0000_data
[OK] /data/Work/Unified-Config/Policies_for_test/e1f3301e-9837-4f28-a103-4ec3b09dbc09_data
[OK] /data/Work/Unified-Config/Policies_for_test/f5969ab4-fee3-71e0-1bf0-1039249e0000_data

Policy files containing ECS
---------------------------

[ECS] /data/Work/Unified-Config/Policies_for_test/f7df32d6-fee3-71e0-1bf0-1039249e0000_data

Problem details of problematic policies
---------------------------------------

Policy File: /data/Work/Unified-Config/Policies_for_test/f4d5252c-4600-4c2e-99a2-67dbf002f333_data

  Condition ID: b0c51b22-ece3-71d9-09fb-0f8878050000
  Condition: "Verify opcmona flag files - not found at all"
    Problem: ACTION_SERVER_VAR [ERROR]
      Action: "opcragt -start <$MSG_NODE_NAME>"
      Action Node: ACTIONNODE IP 0.0.0.0  "<$OPC_MGMTSV>"
      Password:

  Condition ID: 258941c8-ece3-71d9-09fb-0f8878050000
  Condition:
    Problem: ACTION_SERVER_VAR [ERROR]
      Action: "opcragt -start <$MSG_NODE_NAME>"
      Action Node: ACTIONNODE IP 0.0.0.0  "<$OPC_MGMTSV>"
      Password:
...

The following commands show the migration of the configuration data set english InfraSPI from OM for UNIX or Linux to an OMi Linux system running Monitoring Automation:

1. Run the following commands on the OM for UNIX or Linux server:

   /opt/OV/bin/OpC/utils/opcpolicy ‑list_groups |grep ‑i infra

   /opt/OV/bin/OpC/utils/opcpolicy ‑download pol_group="/Infrastructure Management/en" dir=/tmp/infraspiDown

   scp -r /tmp/infraspiDown <MAserver>:/tmp

2. Run the following commands on the OMi server running Monitoring Automation:

   <OMi_HOME>/opr/bin/ConfigExchange.sh ‑check ‑policyfile /tmp/infraspiDown ‑logfile /tmp/infraspiVal.log

   <OMi_HOME>/opr/bin/ConfigExchange.sh ‑username myU ‑password myPW -uploadOM ‑input c:/cygwin/tmp/infraspiDown

The following commands show the migration of the configuration data set english SPI for Databases from OM for Windows to an OMi Windows system running Monitoring Automation:

1. Run the following command on the OM for Windows server:

   cfg pol dnl C:\temp /p "\SPI for Databases" /instrum

2. Copy the output folder C:\temp\SPI for Databases from the OM server to the OMi server running Monitoring Automation.

3. Run the following commands on the OMi server running Monitoring Automation:

   <OMi_HOME>\opr\bin\ConfigExchange.bat ‑check ‑policyfile "C:\temp\SPI for Databases" ‑logfile C:\temp\infraspiVal.log

   <OMi_HOME>\opr\bin\ConfigExchange.bat ‑username myU ‑password myPW ‑uploadOM -input "c:\temp\SPI for Databases"

For information on troubleshooting configuration upload, see ConfigExchange Command-Line Interface.

For information on troubleshooting SiteScope template import, see Import SiteScope templates.