<< PREVIOUS

 

 

PROBE UPGRADE - WINDOWS

 

Install VSP Probe on the Application Instance using the below process:

  1. For Auto-registration process, the required .bat file must be downloaded on the Application Instances

  2. Using any browser, navigate to the Local Repository URL: http://<Local Repository URL>

  3. Navigate to the directory vsp. To install all the available SKUs (VSP-Enterprise, VSP-Web, VSP-Memory and VSP-Host), follow the below steps:

    1. Download this file vsp_install_vm.bat to the server

    2. Execute the below commands at the command prompt as an Administrator::

      1. The below command displays the help menu

        vsp_install_vm.bat -h

         

         

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

         

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

        2. (Optional) Parameter “-C” <CMS DNS Name> – Custom DNS name for CMS

        3. (Optional) Parameter “-K” <Kafka DNS Name> – Custom DNS name for Kafka

        4. Parameter “-c” CMS_IP – IP Address of CMS

        5. (Optional) Parameter “-e” - To indicate Remote vRule configuration. Do not provide this option for Remote vRule option

        6. Parameter “-i” Host_IP – IP Address of Application Instance (Host)

        7. (Optional) VSP_Kafka_Node_IP – IP Address of Kafka

        8. Parameter “-l” LFR_IP - IP Address of LFR

        9. (Optional) Parameter “-L” LFR_Port - VSP LFR Port (Default port is 80)

        10. (Optional)  Parameter “-n” Hostname - Hostname of the Application Instance. This is utilized during probe registration with CMS

        11. (Optional) Parameter “-q” Kafka_Container_Port – VSP Kafka Port (Default port is 9092)

        12. (Optional) Parameter “-p” Host Profile Tags – Appropriate Host Profile Tag

        13. (Optional) Parameter "-r" – To restart VSP services after installation. They are not restarted by default

        14. Parameter “-s” SKU - Provide the required SKU. Allowed values are web, host, mem

        15. (Optional) Parameter "-u" – To uninstall already existing Probe services and install the latest available version

        16. (Optional) Parameter "-U" – To uninstall already existing Probe services

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

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

        19. (Optional) Parameter "-P" – To enable pristine host mode for VSP-Host

    3. Make a note of the displayed token for future use during password reset

  4. Alternatively, to install a specific SKU, download the relevant .zip file

    1. SKU: Select the appropriate file with web (VSP-Enterprise, VSP-Web), memory (VSP-Memory) and host (VSP-Host) in its name

    2. The file name format is: vsp-<SKU>-vm.zip

    3. Unzip the file to obtain the respective vm-install.bat file

    4. The below command displays the help menu

      1. vm-install.bat -h

         

         

    5. Execute the below command to install the probe

      vm-install.bat -c <CMS_IP> -i <Host_IP> -k <VSP_Kafka_Node_IP> -r

       

      1. CMS_IP – IP Address of CMS

      2. Host_IP - IP Address of Application Instance 

      3. VSP_Kafka_Node_IP – IP Address of Kafka

      4. Hostname - Hostname of the Application Instance. This is utilized during probe registration with CMS

      5. Parameter “-r” - To start VSP services after Installation

      6. Parameter “-e” - To indicate Remote vRule configuration. Do not provide this option for Remote vRule option

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

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

      9. (Optional) Parameter "-P" – To enable pristine host mode for VSP-Host

    6. Make a note of the displayed token for future use during password reset

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

  6. If the parameter -r is not provided during installation, start the installed VSP ASI service

  7. Verification

    1. On the Application Instance, VSP Probe is installed as a service

      image 84

    2. In CMS, navigate to Monitor > Probes

      image 84

    3. Verify that the Probe server is listed and in Connected state

    4. If VSP Host is configured, follow the steps below:

      1. Navigate to Host Security > Host Monitoring in the left navigation pane. Ensure that the App Control Policy is associated with the existing Host Profile

        image35

      2. If not, modify the profile and select the required App Control Policy from the dropdown

        image36

 

NOTE:  

After the upgrade, ensure that the Application is un-provisioned and provisioned on CMS and the business application is restarted

 

 

<< PREVIOUS