Note that, VeloCloud Collector Package 1.1.0.1 has one of the fix for handling a use case where Non VeloCloud Site is configured without tunnels enabled. Refer VMware Smart Assurance Release notes to get more details on the issue.
Procedure
- Navigate to the bin directory of the ESM Server Install and stop the ESM Server.
- Navigate to the bin directory of the DCF Install.
- Stop the DCF Controller Service, using the following command:
./manage-modules.sh service stop controller
- If there are any existing VeloCloud collector instances already deployed, then stop those collectors.
./manage-modules.sh service stop collector-manager <VeloCloud-Instance>
Example: ./manage-modules.sh service stop collector-manager veloCloudsdwan0c6c9b6b-9ba5-49e9-8ed3-3c71fb5cce33
Note: To identify the VeloCloud Collector Instances which are deployed, run the below command:
./manage-modules.sh list installed
- Download the Collector package "veloCloud-sdwan-collect-1.1.0.1.pkg" and copy the same to /opt/DCF/Tools/Module-Repository directory
Note: Do not remove the old VeloCloud collector package from the
/opt/DCF/Tools/Module-Repository directory.
- To update the Collector package for the existing VeloCloud collector block instances run the below command:
./manage-modules.sh update velocloud-sdwan-collect velocloud-sdwanac26f785-a8bb-4c57-9323-3466dd0a3f2d
Example: /opt/DCF/bin/manage-modules.sh update veloCloud-sdwan-collect velocloud-sdwan0c6c9b6b-9ba5-49e9-8ed3-3c71fb5cce33
- When prompted to modify the dependencies, type "yes".
- When prompted to modify the module configuration, type "no".
- The update will be complete and the VeloCloud collector instance will be started.
- Similarly update the package for all other VeloCloud collector block instances.
- Start the Controller service:
./manage-modules.sh service start controller
- Start the ESM Server.
- If there are no Velocloud Collectors already deployed and it is a fresh DCF deployment, then ignore the steps 4, 6 and 7.