PROBE UPGRADE
PROBE UPGRADE - LINUX
Install VSP Probe on the Application Instance using the below process:
-
Download the required .sh file to the Application Instances
-
Using any browser, navigate to the Local Repository URL: http://<Local Repository URL>
-
Navigate to the directory vsp
-
To install all the available SKUs (VSP-Enterprise, VSP-Web, VSP-Memory and VSP-Host), right click on the file vsp_install_vm.sh and select the option Copy link address
-
Download this file to the server using the command:
-
wget <copiedLink>
-
chmod +x vsp_install_vm.sh
-
-
Execute the below commands:
-
sudo bash
-
The below command displays the help menu
./vsp_install_vm.sh -h
-
Execute the below command to install the probe
./vsp_install_vm.sh -c <CMS_IP> -i <Host_IP> -k <VSP_Kafka_Node_IP> -l <LFR_IP> -n <Hostname> -L <LFR_Port> -s <SKU> -u
-
(Optional) Parameter "-H" – Entries are not added in the /etc/host file to resolve the LFR and CMS DNS names. If this parameter is used, ensure that the parameters -C and -K are provided
-
(Optional) Parameter “-C” <CMS DNS Name> – Custom DNS name for CMS
-
(Optional) Parameter “-b” – VSP Release Name to be used from the backup directory – Use it in cases where incremental LFR Refresh is complete and when the script needed for execution is located in the backup directory. Refer Section Incremental LFR Refresh for more information
-
(Optional) Parameter “-K” <Kafka DNS Name> – Custom DNS name for Kafka
-
Parameter “-c” CMS_IP – IP Address of CMS
-
(Optional) Parameter “-e” – To indicate Remote vRule configuration. Do not provide this option for Remote vRule option
-
Parameter “-i” Host_IP – IP Address of Application Instance (Host)
-
(Optional) Parameter “-k” VSP_Kafka_Node_IP – IP Address of Kafka
-
Parameter “-l” LFR_IP – IP Address of LFR
-
(Optional) Parameter “-L” LFR_Port –VSP LFR Port (Default port is 80)
-
(Optional) Parameter “-n” Hostname – Hostname of the Application Instance. This is utilized during probe registration with CMS
-
(Optional) Parameter “-p” Host Profile Tags – Appropriate Host Profile Tag
-
(Optional) Parameter “-r” – To restart VSP services after installation. They are not restarted by default
-
Parameter “-s” SKU – Provide the required SKU. Allowed values are web, host, mem
-
(Optional) Parameter “-u” – To uninstall existing Probe services and install the latest available version
-
(Optional) Parameter “-U” – To uninstall existing Probe servicess
-
(Optional) Parameter “-P” – To enable pristine host mode for VSP-Host
-
-
-
-
Alternatively, to install a specific SKU, follow the steps below:
-
Navigate to the directory vsp > <Operating System> > <Operating System Version>
NOTE:
Navigate to the directory rpm for the Operating Systems RHEL and CentOS
-
Right click on the relevant .sh file and select the option Copy link address
-
SKU: Select the appropriate file with web (VSP-Enterprise, VSP-Web), memory (VSP-Memory) and host (VSP-Host) in its name
-
The file name format is: vsp-<SKU>-vm.sh
-
Download this .sh file to the server using the command:
-
wget <copiedLink>
-
chmod +x vsp-<SKU>-vm.sh
-
-
Execute the below commands:
-
sudo bash
-
The below command displays the help menu
./vsp-<SKU>-vm.sh -h
-
-
Execute the below command to install the probe
./vsp-<SKU>-vm.sh -c <CMS_IP> -i <Host_IP> -k <VSP_Kafka_Node_IP> -n <Hostname> -0 <Hostname> -o <Host_OS> -V <Host_OS_Version> -r
-
CMS_IP – IP Address of CMS
-
Host_IP - IP Address of Application Instance
-
VSP_Kafka_Node_IP – IP Address of Kafka
-
Hostname - Hostname of the Application Instance. This is utilized during probe registration with CMS
-
Host_OS - Operating System of the Application Instance
-
Host_OS_Version - Operating System Version of the Application Instance
-
Parameter “-r” - To start VSP services after Installation
-
Parameter “-e” - To indicate Remote vRule configuration. Do not provide this option for Remote vRule option
-
(Optional) Parameter “-P” – To enable pristine host mode for VSP-Host
-
-
-
At the end of the installation, the installed probe instance automatically registers with VSP CMS and a restart of the Linux machine is NOT required if the parameter -r is provided during installation
-
If the parameter -r is not provided during installation, restart the services using the below command:
-
service vsp start
-
-
For container-based CMS instance, restart the VSP services in Ubuntu and RHEL Probe instances using the below command:
-
Method 1: Stop and start VSP services
-
service vsp stop
-
service vsp start
-
-
Method 2: Restart VSP services
-
service vsp restart
-
-
-
Verification
-
In CMS, navigate to Monitor > Probes
-
Verify that the Probe server is listed and in Connected state
-
If VSP Host is configured, follow the steps below:
-
Navigate to Host Security > Host Monitoring in the left navigation pane. Ensure that the App Control Policy is associated with the existing Host Profile
-
If not, modify the profile and select the required App Control Policy from the dropdown
-
-
NOTE:
After the upgrade, ensure that the Application is un-provisioned and provisioned on CMS and the business application is restarted