Installing a CDP as a high-availability CDP

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. 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. 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.