Installing a CDP as a high-availability CDP

This topic describes how to use the GUI installation program to install a secondary configuration distribution peer (CDP) for high availability. During its installation, the secondary CDP searches for and uses the primary CDP and the repository configuration settings.

For more information about high availability, see Configuring BMC Atrium Orchestrator for high-availability.

Before you begin

  • If you are using the external Remedy Single Sign-On authentication system, you must have already installed it, configured it, and it must be running.
  • You must have installed and completed any required configuration of the repository and a configuration distribution peer (CDP).
  • The repository and the primary CDP must be running.
  • You must ensure that the target computer meets the minimum system requirements for your environment.
  • You must have completed the HA-CDP installation worksheet.
  • You must be logged on as an administrator and have administrator rights on the computer on which you install the additional CDP.
    • On Microsoft Windows, you must have administrator permissions. 
    • On Linux and Solaris, any non-root user with write permission to the /opt/bmc directory can perform the installation.
      On Linux and Solaris, the non-root user must also have permission to run the following commands:
      • dmidecode -t 1 | grep Manufacturer
      • lsb_release -d
  • If you are installing on a Windows computer, ensure that Data Execution Prevention (DEP) is configured to recognize the installation program executable (Configuring DEP on Windows computers).
  • If you are installing on a Linux computer, run the rngd service to ensure that the system has adequate entropy (Run the rngd service on Linux computers).
  • Ensure that you have the lsb_release command in the /usr/bin directory and that you can run it. Use the steps for your operating system.
    • Red Hat Linux 7 machines:
      1. Verify that the lsb_release command is in the /usr/bin directory by running the following command:
        which lsb_release
        For example,
        [root@localHost ~]# which lsb_release
        If it is available, you will see the following response:
        /usr/bin/lsb_release
      2. If the command is available, verify that you can run it using the following command:
        lsb_release -d
        For example,
        [root@localHost ~]# lsb_release -d
        If it runs correctly, you will see a response similar to the following:
        Description: Red Hat Enterprise Linux Server release 7.0 (Maipo) 

        or...
        If the command is not available, copy it from a RHEL6 machine to the RHEL7 machine as follows:
        1. Navigate to the /usr/bin directory and run the scp command to copy the lsb_release command from the RHEL6 machine to the RHEL7 machine.
          scp lsb_release root@<rhel7MachineHostname/IPaddress>:/usr/bin/ 
        2. On the RHEL7 machine, repeat steps a and b to verify that the command is in the /usr/bin directory and that you can run it. 
    • SUSE Linux machines:
      1. Verify that the lsb_release command is in the /usr/bin directory by running the following command:
        which lsb_release
        For example,
        [root@localHost ~]# which lsb_release
        If it is available, you will see the following response:
        /usr/bin/lsb_release
      2. If the command is available, verify that you can run it using the following command:
        lsb_release -d
        For example,
        [root@localHost ~]# lsb_release -d
        If it runs correctly, you will see a response similar to the following:
        Description: SUSE Linux Enterprise Server 11 (x86_64)

        or....
        If the command is not available, download it from the internet or from your operating system vendor's website.
  • You must have added the specified peer to the grid, as described in Adding peers.
  • You must have exited all other programs.

To install a CDP as a high-availability CDP

  1. Navigate to and start the installation program for your operating system. See Performing the installation for the installation program names.
  2. On the splash screen, select the language in which to view the installation program, and click OK.
  3. On the Welcome to BMC Atrium Orchestrator panel, review the information and click Next.
  4. On the license agreement panel, select I agree to the terms of the license agreement; then click Next.
  5. On the Installation Type panel, select Install new Orchestrator components, and click Next.
  6. Using the HA-CDP installation worksheet, fill in the settings to install a CDP as the HA-CDP.
    The installation program validates communication with the grid and the CDP Communications Setting panel shows the connection success or failure message.
  7. Review the information on the Installation Choices Summary panel, and click Copy Text to Clipboard to copy the summary of the connection details for further use.
  8. Click Install.
  9. On the Installation Summary panel, perform one of the following actions:
    • To exit the installation program, click Done.
    • To review the BAO_install_log.txt file, click View Log, and then click Done to exit the installation program.

Verify the CDP and embedded RSSO installation

To ensure that the CDP and embedded RSSO (if you chose this option) were installed successfully, use the instructions in Verifying a peer or embedded RSSO installation.

You can use the following user credentials to log into the CDP:

  • User name: aoadmin 
  • Password: admin123 

You can use the following user credentials to log into RSSO:

  • User name: Admin
  • Password: RSSO#Admin#

Note

If you are using Internet Explorer 8.0 or later, then ensure that you add the URL for the BMC Atrium Orchestrator Grid Manager in the trusted sites of the browser.

After you install all BMC Atrium Orchestrator components and verify that they are successfully installed, BMC recommends that you change the passwords. After you install all BMC Atrium Orchestrator components and verify that they are successfully installed, BMC recommends that you change the passwords. See Creating and managing local users and roles in Remedy Single Sign-On for details.

Linux steps to support dmidecode

 If you are installing in a Linux environment, you must complete the following instructions after the installation.

  1. Add the path to the dmidecode executable location to the user's environment under which the BMC Atrium Orchestrator service is running.
    This supports running the dmidecode to gather operating system information by the Health dashboard.
    To do this, edit the .bashrc file located in the $HOME directory and add the path.
    For example, if the BMC Atrium Orchestrator service is running under a user account called "bao," edit bao's .bashrc file and add the following lines:

    set PATH=${PATH}:/usr/sbin
    export PATH

  2. As root user, run the following command to update permissions so that non-root users can run the dmidecode command: 
    chmod g+s /usr/sbin/dmidecode

  3. Restart the BMC Atrium Orchestrator service (see Starting and stopping product components and services).

Where to go from here

If you have not already done so, you can install any of the following: 

If you are using the embedded RSSO service, after installing your BAO components you must complete the steps in Configuring a fail-safe enterprise service bus after installation.