Installing Cloud Probe silently

Where you are in the Installation process

StepTask
1Complete the planning activities
2Prepare for TrueSight Operations Management installation
3Install Remedy Single Sign-On
4Install TrueSight Presentation Server
5Install TrueSight Infrastructure Management (if licensed) 
6Install TrueSight App Visibility Manager
7Install Real End User Experience Monitoring Software Edition — Phase A
Install Real End User Experience Monitoring Software Edition — Phase B (You are here)
Install Real End User Experience Monitoring Software Edition — Phase C
8Install TrueSight IT Data Analytics (If licensed)
9Complete the post-installation activities

Note

BMC Real End User Experience Monitoring Software Edition version 11.0.00.002 is the latest version of the component and is compatible with TrueSight Operations Management versions 11.3.01 and later.


 

Tip

For best results capturing end-user performance data, install the Cloud Probe on the host that provides load balancing services for an application. By binding the public interface used by the load balancing services, end-user transactions can be accurately measured and processed.

To encrypt the password for silent installations

The Maintenance Tool enables you to create an encrypted password. You must use an encrypted password to set up a silent installation,so that the system password is not exposed in the cloudprobe-silent-option file.

You can run the Maintenance Tool in a GUI or from the command line.

 To encrypt a password for a silent installation in a GUI
  1. To open the Maintenance Tool, in the Cloud Probe installation directory, go to the \utility directory.
  2. Run the CloudProbeMaintenanceTool utility and click the Encrypt tab.
  3. Enter your password in the Password and Confirm Password fields and click Encrypt.
  4. Copy and paste the value from the Encrypted Password field to the cloudprobe-silent-option file for your silent installation.
    For example, if the encrypted password output is DES\:d70cbe3669602717ce66af37cce7ecf0, modify the real_user_collector_password property as follows:
    -J real_user_collector_password=DES\:d70cbe3669602717ce66af37cce7ecf0
 To encrypt a password for a silent installation from the command line
  1. To open the Maintenance Tool, in the Cloud Probe installation directory, go to the \utility directory.
  2. Run the following command, entering your password for the -password and -confirm_password options:

    On Linux, run the following command:  ./CloudProbeMaintenanceTool.sh -silent -encrypt -encrypt -password=<password> -confirm_password=<password>

    On Windows: CloudProbeMaintenanceTool.cmd -silent -encrypt -encrypt -password=<password> -confirm_password=<password>

    Note

    Linux

    If the password contains special characters and you are using a Bash shell, use a single quotation mark before and after the password. For example:

    ./CloudProbeMaintenanceTool.sh -silent -encrypt -encrypt -password='<password>' -confirm_password='<password>'

    If you are using a different shell, this solution may not succeed. It is recommended that you use the maintenance tool GUI option.

    Windows

    If the password contains special characters, use double quotation marks before and after the password. For example:

    CloudProbeMaintenanceTool.cmd -silent -encrypt -encrypt -password="<password>" -confirm_password="<password>"

  3. Copy and paste the output to the cloudprobe-silent-option file for your silent installation.
    For example, if the encrypted password output is DES\:d70cbe3669602717ce66af37cce7ecf0, modify the real_user_collector_password property as follows:
    -J real_user_collector_password=DES\:d70cbe3669602717ce66af37cce7ecf0

To define properties and run the silent installation on Linux

Warning

Changing the value of properties that are not specifically mentioned in this procedure might have unexpected results.

  1. Log in to the virtual machine as rootuser.
  2. From the the Cloud Probe installation directory, open the cloudprobe-silent-option file in a text editor.
  3. Enter an installation directory for the installLocation property.
    By default, the following directory is entered:
    -P installLocation=/opt/bmc/CloudProbe
  4. Enter the following values to connect to the Real User Collector:

    Example
    -J real_user_collector_ip_address=<ipAddress>
    -J real_user_collector_port=443
    -J real_user_collector_username=<userName>
    -J real_user_collector_password=<encryptedPassword>
    • <ipAddress> represents the IP address or DNS name of the Collector.
    • The default value of the real_user_collector_port property is 8443.
      If a different port number was used during installation of the Real User Collector, enter that port number

    • <userName> that represents the operator-level user name to log in to the Collector.
    • <encryptedPassword> represents an encrypted version of the password used to log in to the Collector.
  5. Enter the name of the Cloud Probe.

    Example
    -J cloud_probe_name=<cloudProbeName>

    <cloudProbeName> represents the name displayed in the Real User Collector. The name can have up to 60 alphanumeric characters, hyphens (-), and underscore characters (_).

  6. Enter the name of the network interface card (NIC) to use for capturing traffic.

    Example
    -J cloud_probe_network_card=<networkCard>

    If you need to see a list of the available network interface cards, you can run the ifconfig  or the ip link commands. Network card names are in the following form: eth0, eno1, ens32, enp2s0.

  7. Save and close the cloudprobe-silent-option file.
  8. In the Cloud Probe installation directory, run the following command to run the installation file:

    Command
    ./setup.bin -i silent -DOPTIONS_FILE=<installation directory>/cloudprobe-silent-option


  9. If you use encrypted traffic, configure the SSL Keys for traffic decryption.

To check the Cloud Probe service on Linux

Run the following command to ensure that the Cloud Probe process is up and running:

ps –ef | grep cloud

If you have installed a Cloud Probe on a Red Hat Linux 5.8 operating system, and the agent does not start after installation, change the maximum packet size (in bytes) allowed for the EPX:

  1. Open the epx_properties.conf file located in [CloudProbeInstallDir]/cloudprobe/conf folder.
  2. Change the value of the SYSTEM.PROPERTIES.EPX.global.max_packet_size parameter. You can set the maximum packet size value between 1500 and 65535 bytes.

  3. Start the Cloud Probe service using the service cloud-probe start command.

To verify the Cloud Probe is sending traffic data to the Real User Collector

  • In the Real User Collector to which you connected the Cloud Probe, select Administration > Integration, then click Cloud Probes. Find your Cloud Probe instance in the list and ensure it is processing traffic data. For details, see  Monitoring Cloud Probe system health on a Collector.
  • In the Real User Analyzer, select System Deployment > Components, and click on the Real User Collector to which you connected the Cloud Probe. Find your Cloud Probe instance in the list and ensure it is processing traffic data. For details, see  Monitoring Cloud Probe system health on a Collector.

Tip

If your Cloud Probe instance was not installed properly or it is not processing data, see Troubleshooting the Cloud Probe .

Following the installation, the Cloud Probe starts automatically. You access the Cloud Probes page  through the Real User Collector console. Point to Administration > Integration, and click Cloud Probes.

To define properties and run the silent installation on Windows

  1. Log in to the windows machine as Administrator
  2. From the Cloud Probe installation directory, open the cloudprobe-silent-option file using a text editor.
  3. Enter an installation directory for the installLocationproperty.
    By default, the following directory is provided:
    -P installLocation= C:\Program Files (x86)\BMC Software\CloudProbe
  4. Enter the following values to connect to the Real User Collector:

    • The IP address or DNS name of the Real User Collector.
    • Real User Collector port (default value is 443).
      If a different port number was used during installation of the Real User Collector, enter that port number

    • <userName> that represents the operator-level user name to log in to the Collector.

    • Encrypted version of the password used to log in to the Real User Collector.

      Example
      -J real_user_collector_ip_address=<ipAddress>
      -J real_user_collector_port=443
      -J real_user_collector_username=<userName>
      -J real_user_collector_password=<encryptedPassword>
  5. Provide the display name for the Cloud Probe instance. The name can have up to 60 alphanumeric characters, hyphens (-), and underscore characters (_).

    Example
     -J cloud_probe_name=<cloudProbeName>
  6. Enter the numeric part of the name of the monitored network card to be used for capturing traffic.

    Example
     -J cloud_probe_network_card=\Device\NPF_{<networkCardName>}

    Tip

    Use getmac /v command to get the network card name. The network card name appears in the Transport Name column. For example: \Device\Tcpip_{011321D9-9333-4CEC-8A49-D8C0E5907806}

  7. Save and close the cloudprobe-silent-option file.
  8. In the Cloud Probe installation directory, run the following command to run the installation file:

    Command
    setup.cmd -i silent -DOPTIONS_FILE=cloudprobe-silent-option
  9. If you use encrypted traffic, configure the SSL keys  for traffic decryption.

To check the Cloud Probe service on Windows

Open the Services list and verify that BMC Real User Cloud Probe service is started.

To verify the Cloud Probe is sending traffic data to the Real User Collector

  • In the Real User Collector to which you connected the Cloud Probe, select Administration > Integration, then click Cloud Probes. Find your Cloud Probe instance in the list and ensure it is processing traffic data. For details, see  Monitoring Cloud Probe system health on a Collector.
  • In the Real User Analyzer, select System Deployment > Components, and click on the Real User Collector to which you connected the Cloud Probe. Find your Cloud Probe instance in the list and ensure it is processing traffic data. For details, see  Monitoring Cloud Probe system health on a Collector.

Tip

If your Cloud Probe instance was not installed properly or it is not processing data, see Troubleshooting the Cloud Probe .

Next Step in the Installation process

Step 7 Phase C Task 1 — Now that you have successfully installed Cloud Probe, you must establish traffic data feeds between an Analyzer and a Collector.

Was this page helpful? Yes No Submitting... Thank you

Comments