Upgrading the Cloud Probe silently

You can install the BMC Real End User Experience Monitoring Software Edition Cloud Probe upgrade unattended (a silent upgrade), which requires no user interaction. You might use this type of upgrade process where you are pushing out the Cloud Probe to servers, or you want to upgrade the Cloud Probe on multiple systems. You can perform a silent upgrade, as described in this topic, or you can use the upgrade wizard.

To upgrade the Real User Cloud Probe on Linux

1. Log in to the virtual machine as root user.

2. In the Cloud Probe installation directory, run the cloudprobe-silent-upgrade-option file with the following command:

   Command

   ./setup.bin -i silent -DOPTIONS_FILE=$(pwd -P)/cloudprobe-silent-upgrade-option

   The current session will close and the installer will run in the background.

3. Review the installation results in the installation log at /tmp/cloudprobe_install_log.txt.
   Following the upgrade, the Cloud Probe starts automatically. You access the Cloud Probes page through the Real User Collector console. From the TrueSight console, point to Administration > Integration, and click Cloud Probes.

4. Verify the Cloud Probe service is started.

   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.

5. Verify the Cloud Probe is sending traffic data to the Real User Collector.

   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.

6. If you use encrypted traffic, configure the SSL keys for traffic decryption.

To upgrade the Real User Cloud Probe on Windows

1. Log in to the windows machine as Administrator.

2. In the Cloud Probe installation directory, run the cloudprobe-silent-upgrade-option file with the following command:

   Command

   - setup.exe -i silent -DOPTIONS_FILE=C:\Disk1\cloudprobe-silent-upgrade-option

   The current session will close and the installer will run in the background.

3. Review the installation results in the installation log at /tmp/cloudprobe_install_log.txt. 

   Following the upgrade, the Cloud Probe starts automatically. You access the Cloud Probes page through the Real User Collector console. From the TrueSight console, point to Administration > Integration, and click Cloud Probes.

4. Verify the Cloud Probe service is started.

   To check the Cloud Probe service on Windows

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

5. Verify the Cloud Probe is sending traffic data to the Real User Collector

   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.