Upgrading the Cloud Probe using the wizard

Where you are in the Upgrade process

The Real User Cloud Probe monitors the network performance of traffic to a virtual machine through a cloud provider. The Cloud Probe sends information through the Real User Collector on a BMC Real End User Experience Monitoring Software Edition system. Perform the following procedure to upgrade the Cloud Probe through an installation wizard. You can also upgrade the Cloud Probe silently.

To upgrade the Real User Cloud Probe on Linux

Before you run the upgrade utility, set up a DISPLAY environment.

1. Log on as root to the system where you will install the Real User Cloud Probe.
2. At a command prompt, unzip the Cloud Probe installation distribution file that you downloaded from EPD by using the following command:
     tar -xzvf cloud_probe_linux_<v.r.mm>.tar.gz    
3. Navigate to the extracted installation directory, such as cloud_probe_rh6, and run the ./setup.bin command.
4. The utility detects a Cloud Probe installation on the system and will update this version with an upgrade. Click Next.
5. On the Welcome page of the installation wizard, click Next.
6. Read the License Agreement and select I agree to the terms of the license agreement to continue.
   Click Next.

7. Review the installation details and click Install.

   Note

   If you need to change some of the Cloud Probe configuration details, you can use the Maintenance Tool to modify the Real User Cloud Probe configuration.

8. Review the details in the Installation Summary page.
   To view the installation logs , click the View Log button, or go to /tmp/cloudprobe_install_log.txt.

9. To close the installation utility, click Done.

   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.

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

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

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

To upgrade the Real User Cloud Probe on Windows

1. Download and install latest version of WinPcap.
   WinPcap is a packet capture driver that is necessary for correct functioning of Cloud Probe under Windows.
2. Extract the Cloud Probe installation files that you downloaded from EPD.
3. Run the Real User Cloud Probe installation file (setup.exe) as Administrator.
4. In the Directory Destination step of the installation wizard, select installation destination folder and click Next.

5. Review the installation details and click Install.
   To view the installation logs , click the View Log button, or go to /tmp/cloudprobe_install_log.txt.
   

   Note

   If you need to change some of the Cloud Probe configuration details, you can use the Maintenance Tool to modify the Real User Cloud Probe configuration.

6. After installation, ensure that the staging folder <InstallationDir>\cloudprobe\staging has WRITE permissions enabled for Administrators group.
   

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

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

Post-upgrade of Cloud Probe

Perform the following tasks:

•   Modify  the Real User Cloud Probe configuration with the Maintenance Tool
•   Configure confidentiality policies on a Cloud Probe
• Configure traffic filtering rules on a Cloud Probe

Next Step in the Upgrade process

Now that you have successfully upgraded Cloud Probe, you can upgrade the other TrueSight components as per your license entitlements. For instructions, see the Upgrade process.