Performing the Cloud Probe upgrade silently

You can perform an unattended (silent) upgrade of the Real User Cloud Probe. You might use this type of upgrade when you are pushing out the Cloud Probe to servers, or you want to upgrade the Cloud Probe on multiple systems. Perform the following procedure to upgrade the Cloud Probe silently. You can also upgrade the Cloud Probe through an installation wizard.

The following topics describe how to set up and run a silent upgrade:

• Encrypting the password for silent installations
• Defining properties and running the silent upgrade on Linux
• Defining properties and running the silent upgrade on Windows
• Where to go from here
• Related topics

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

Defining properties and running the silent upgrade on Linux

1. Log in to the virtual machine as root.

2.  In case you do not change any Cloud Probe settings, from the Cloud Probe installation directory, run the following command to perform the upgrade:
    

   Command

   ./setup.sh -i silent
3. In case you need to change any of the Cloud Probe settings, from the the Cloud Probe installation directory, open the cloudprobe-silent-option file in a text editor.

4. Enter the new values for the following, in case you wish to change the values to connect to the Real User Collector, otherwise, skip this step:

   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 443.
   • <userName> represents the 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 new name of the Cloud Probe, in case you wish to change it.

   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 new name of the network interface card (NIC) to use for capturing traffic, in case you wish to change it.

   Example

   -J cloud_probe_network_card=<networkCard>

   You can run the ifconfig command to see a list of the network cards and enter the value of the one you want to monitor. Network card names are in the following form: eth0, eth1, eth2.

7. Save and close the cloudprobe-silent-option file.

8. In the Cloud Probe installation directory, run the following command to perform the upgrade:

   Command

   ./setup.sh -i silent -DOPTIONS_FILE=cloudprobe-silent-option
9. Following the upgrade, the Cloud Probe instance starts automatically. Find your Cloud Probe instance in the list and ensure it processes traffic data.
10. To view the installation logs, go to /tmp/cloudprobe_install_log.txt.

Defining properties and running the silent upgrade on Windows

1. Log in to the windows machine as Administrator

2.  In case you do not change any Cloud Probe settings, from the Cloud Probe installation directory, run the following command to perform the upgrade:
    

   Command

   setup.cmd -i silent
3. In case you need to change any of the Cloud Probe settings, from the Cloud Probe installation directory, open the cloudprobe-silent-option file using a text editor.

4. Enter the new values for the following, in case you wish to change the values to connect to the Real User Collectors:

   • The IP address or DNS name of the Real User Collector.
   • Real User Collector port (default value is 443).
   • The 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 new 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. Change 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>}

   Success

   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 perform the upgrade:

   Command

   setup.cmd -i silent -DOPTIONS_FILE=cloudprobe-silent-option
9. Following the upgrade, the Cloud Probe instance starts automatically. Find your Cloud Probe instance in the list and ensure it processes traffic data.
10. To view the installation logs, go to \AppData\Local\Temp\cloudprobe_install_log.txt.

Where to go from here

Verify the Real User Cloud Probe installation.

Modify the configuration with the Real User Cloud Probe Maintenance Tool.

Configure confidentiality policies on the Cloud Probe

Configure traffic filtering rules on the Cloud Probe 

Related topics

Starting-and-stopping-the-Real-User-Cloud-Probe
Troubleshooting the Real User Cloud Probe
Managing SSL keys and settings for Cloud Probe traffic decryption