PROBE UPGRADE - WINDOWS 2008 AND ABOVE
Install VSP Probe on the Application Instance using the below process:
-
For Auto-registration process, the required .bat file must be downloaded on the Application Instances
-
Using any browser, navigate to the Local Repository URL: https://<Local Repository URL>:8443
-
Navigate to the directory vsp. To install all the available SKUs (VSP-Enterprise, VSP-Web, VSP-Memory and VSP-Host), follow the below steps:
-
Download this file vsp_install_vm.bat to the server
-
Execute the below commands at the command prompt as an Administrator:
-
The below command displays the help menu
vsp_install_vm.bat -h
-
Execute the below command to install the probe
vsp_install_vm.bat -c <CMS_IP> -i <Host_IP> -k <VSP_Kafka_Node_IP> -l <LFR_IP> -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 “-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 “-C” <CMS DNS Name> – Custom DNS name for CMS
-
(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) 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 8443)
-
(Optional) Parameter “-n” Hostname - Hostname of the Application Instance. This is utilized during probe registration with CMS
-
(Optional) Parameter “-q” Kafka_Container_Port – VSP Kafka Port (Default port is 9092)
-
(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 services
-
(Optional) Parameter "-X" – To set the password to stop/modify a service using VSP-CLI utility. When this parameter is used, the user is prompted to provide the password (this method is preferred due to security reasons). A valid password must be 16 characters (minimum) in length and must have alphanumeric characters in both upper and lower cases. Once the password is set, VSP Service start/stop (using services.msc OR sc command) is not allowed
-
(Optional) Parameter "-x" – To set the password to stop/modify a service using VSP-CLI utility. When this parameter is used, the password must be provided along with the command. A valid password must be 16 characters (minimum) in length and must have alphanumeric characters in both upper and lower cases. Once the password is set, VSP Service (start/stop using services.msc OR sc command) is not allowed
-
(Optional) Parameter “-d” – To specify the backup location for Probe configuration, data and log information. If this parameter is provided, the existing Probe information is restored during the upgrade process. The default location to store backup files is C:\ProgramData\vsp_backup
-
-
-
Make a note of the displayed token for future use during password reset
-
-
Alternatively, to install a specific SKU, download the relevant .zip file
-
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.zip
-
Unzip the file to obtain the respective vm-install.bat file
-
The below command displays the help menu
-
vm-install.bat -h
-
-
Execute the below command to install the probe
vm-install.bat -c <CMS_IP> -i <Host_IP> -k <VSP_Kafka_Node_IP> -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
-
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 "-X" – To set the password to stop/modify a service using VSP-CLI utility. When this parameter is used, the user is prompted to provide the password (this method is preferred due to security reasons). A valid password must be 16 characters (minimum) in length and must have alphanumeric characters in both upper and lower cases. Once the password is set, VSP Service start/stop (using services.msc OR sc command) is not allowed
-
(Optional) Parameter "-x" – To set the password to stop/modify a service using VSP-CLI utility. When this parameter is used, the password must be provided along with the command. A valid password must be 16 characters (minimum) in length and must have alphanumeric characters in both upper and lower cases. Once the password is set, VSP Service (start/stop using services.msc OR sc command) is not allowed
-
-
Make a note of the displayed token for future use during password reset
-
-
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, start the installed VSP ASI service
-
Verification
-
On the Application Instance, VSP Probe is installed as a service
-
In CMS, navigate to Deploy > Probes
-
Verify that the Probe server is listed and in Connected state
-
If VSP Host is configured, follow the steps below:
-
Navigate to Manage > Host > Host Protection 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