vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Applying updates and version compatibility 

The deployment of VMware Regulated Workloads instances provides the following components:



*  VMware® components



*  VMware vSphere® Hypervisor (ESXi™)
*  VMware vCenter Server®
*  VMware NSX-T®
*  vSAN™
*  VMware Aria®



*  Entrust®
*  Caveonix
*  Veeam® Backup and Replication



When you apply updates, ensure that you maintain version compatibility for each component. For more information, see:



*  [VMware interoperability matrix - includes vSphere Hypervisor, vCenter Server, NSX-T, vSAN, and VMware Aria)](https://interopmatrix.vmware.com/Interoperability?col=1,&row=2,%26670,%26175,%2688,%26116,&isHideGenSupported=true&isHideTechSupported=true&isHideCompatible=false&isHideNTCompatible=false&isHideIncompatible=true&isHideNotSupported=true&isCollection=false)
*  [Entrust CloudControl](https://my.hytrust.com/s/article/KB10127)
*  [Applying updates to Caveonix RiskForesight](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-managingcaveonixmanagingcaveonix-update)
*  [Veeam Backup and Replication support for VMware vSphere](https://www.veeam.com/kb2443)





  Related links 



*  [Responsibilities for Day 2 operations](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-opsprocs-responsibilities)
* Resolves the following CVEs: [CVE-2022-4304](https://nvd.nist.gov/vuln/detail/CVE-2022-4304)[CVE-2022-4450](https://nvd.nist.gov/vuln/detail/CVE-2022-4450)[CVE-2023-0215](https://nvd.nist.gov/vuln/detail/CVE-2023-0215)[CVE-2023-0286](https://nvd.nist.gov/vuln/detail/CVE-2023-0286)[CVE-2023-24532](https://nvd.nist.gov/vuln/detail/CVE-2023-24532)
* Updates the UBI to version 8.7-1085.1679482090.
* Updates Go to version 1.19.7.







 Revision 8, released 21 March 2023 



* Resolves the following CVEs: [CVE-2023-23916](https://nvd.nist.gov/vuln/detail/CVE-2023-23916)
* Updates the UBI to version 8.7-1085.
* Updates Go to version 1.19.6.







 Revision 7, released 06 March 2023
* [CVE-2020-27619](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-27619)
* [CVE-2021-3177](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-3177)







 Change log for 1.8.3, released 1 March 2021 

Review the changes that are in version 1.8.3 of the managed Istio add-on.

Previous version
: 1.8.2

Current version
: 1.8.3

Updates in this version
: See the Istio release notes for [Istio 1.8.3](https://istio.io/latest/news/releases/1.8.x/announcing-1.8.3/).
: Resolves the following CVEs



* [CVE-2018-20482](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20482)
* [CVE-2019-9923](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-9923)
* [CVE-2021-23239](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-23239)
* [CVE-2021-3156](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-3156)







 Change log for 1.8.2, released 25 January 2021 

Review the changes that are in version 1.8.2 of the managed Istio add-on.

Previous version
: 1.8.1

Current version
: 1.8.2

Updates in this version
-v, --version version for analytics-engine-v3

Use "ibmcloud analytics-engine-v3 service-command --help" for more information about a command.
Show more





 Set a target instance 

The following command allows you to set a target instance against which all subsequent CLI commands are run.

Note: If the instance ID is passed explicitly in any v3 CLI commands, it will override the instance ID that is set as the target.

ibmcloud analytics-engine-v3 target [--instance-id INSTANCE-ID] [--unset-instance]



 Command options 

-i, --instance-id
: The identifier of the target Analytics Engine instance. All subsequent commands are run against the target instance.

--unset-instance
: Revoke the target instance setting





 Examples 

The following example shows you how to set a target instance:

$ ibmcloud ae-v3 target --instance-id d2189b-b729-61f-adc0-987001da52e3
...

Target instance d0f582f7-cbf4-4c64-bf7f-72efd21c9f32
Subsequent commands will be run against the target instance

The following example shows you how to revoke a target instance:

$ ibmcloud ae-v3 target --unset-instance
...

Target instance d0f582f7-cbf4-4c64-bf7f-72efd21c9f32 revoked
No target instance is set







 Instance management commands 

Use this command for Instance management.

ibmcloud analytics-engine-v3 instance --help



 ibmcloud analytics-engine-v3 instance show 

Retrieve the details of a single Analytics Engine instance.

ibmcloud analytics-engine-v3 instance show [--id ID]



 Command options 

-i, --id (string)
: GUID of the Analytics Engine service instance to retrieve. When specified, it overrides the target instance ID if it was set. Required if target instance was not set.
Key Management Service provider v2.3.3 v2.3.4 Updated image to implement additional IBM security controls and for [CVE-2020-28483](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-28483) and [CVE-2020-26160](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-26160). 
 Load balancer and load balancer monitor for IBM Cloud Provider 1274 1328 Updated to use Go version 1.15.11. Updated image to implement additional IBM security controls and for [CVE-2021-28831](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-28831), [CVE-2021-30139](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-30139), [CVE-2021-3449](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-3449) and [CVE-2021-3450](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-3450). 
 OpenVPN Operator image v1.3.0 v1.3.1 Updated image for [CVE-2021-20305](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-20305). 







 Change log for worker node fix pack 4.4.33_1541_openshift, released 10 May 2021 

The following table shows the changes that are in the worker node fix pack 4.4.33_1541_openshift. Worker node patch updates can be applied by updating, reloading (in classic infrastructure), or replacing (in VPC infrastructure) the worker node.
Key Management Service provider v1.0.12 v1.0.14 Updated image to implement additional IBM security controls and for [CVE-2020-26160](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-26160) and [CVE-2020-28483](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-28483). 
 Load balancer and load balancer monitor for IBM Cloud Provider 1274 1328 Updated to use Go version 1.15.11. Updated image to implement additional IBM security controls and for [CVE-2021-28831](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-28831), [CVE-2021-30139](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-30139), [CVE-2021-3449](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-3449) and [CVE-2021-3450](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-3450). 







 Change log for worker node fix pack 3.11.420_1588_openshift, released 10 May 2021 

The following table shows the changes that are in the worker node fix pack 3.11.420_1588_openshift. Worker node patch updates can be applied by updating, reloading (in classic infrastructure), or replacing (in VPC infrastructure) the worker node.



Changes since version 3.11.420_1587_openshift

 Component Previous Current Description 

 RHEL 7 Packages 3.10.0-1160.24 3.10.0-1160.25 To increase resiliency, rsyslog no longer keeps old file descriptors.
Added support to use the channel participation APIs offered by Fabric peers and orderers to manage channels

Updates to VS Code documentation

Updated supported platforms, including support for Kubernetes 1.25

Bug Fixes and Security Patches

Severity: medium





 28 Feb 2023 

Certificate Authority (CA) patch 1.5.5-9, Peer and ordering node patch 1.4.12-23, 2.2.10-1, 2.4.8-1.

Miscellaneous bug fixes and security patches.

Severity: medium





 31 Jan 2023 

Certificate Authority (CA) patch 1.5.5-8, Peer and ordering node patch 1.4.12-22, 2.2.9-4, 2.4.7-4.

Miscellaneous bug fixes and security patches.

Severity: medium





 04 Jan 2023 

Certificate Authority (CA) patch 1.5.5-7, Peer and ordering node patch 1.4.12-21, 2.2.9-3, 2.4.7-3.

Miscellaneous bug fixes and security patches.

Known issue: If the Launch the IBM Blockchain Platform console button is not enabled, refresh the page to enable it.

Severity: medium





 07 Dec 2022 

Certificate Authority (CA) patch 1.5.5-6, Peer and ordering node patch 1.4.12-24, 2.2.9-2, 2.4.7-2.

Updates to VS Code documentation.

Miscellaneous bug fixes and security patches.

Severity: medium





 08 Nov 2022 

Certificate Authority (CA) patch 1.5.5-5, Peer and ordering node patch 1.4.12-19, 2.2.9-1, 2.4.7-1.

Miscellaneous bug fixes and security patches.

Severity: medium





 11 Oct 2022 

Certificate Authority (CA) patch 1.5.5-4, Peer and ordering node patch 1.4.12-18, 2.2.8-3, 2.4.6-3.

Miscellaneous bug fixes and security patches.

Severity: medium





 13 Sept 2022
RHEL 7 Packages 3.10.0-1160.36.2.el7 3.10.0-1160.42.2.el7 Updated worker node image with package updates for [CVE-2021-25214](https://nvd.nist.gov/vuln/detail/CVE-2021-25214), [CVE-2020-27777](https://nvd.nist.gov/vuln/detail/CVE-2020-27777), [CVE-2021-22555](https://nvd.nist.gov/vuln/detail/CVE-2021-22555), [CVE-2021-29154](https://nvd.nist.gov/vuln/detail/CVE-2021-29154), [CVE-2021-29650](https://nvd.nist.gov/vuln/detail/CVE-2021-29650), [CVE-2021-32399](https://nvd.nist.gov/vuln/detail/CVE-2021-32399), and [CVE-2021-3715](https://nvd.nist.gov/vuln/detail/CVE-2021-3715). 







 Change log for worker node fix pack 4.6.43_1554_openshift, released 30 August 2021 

The following table shows the changes that are in the worker node fix pack patch update 4.6.43_1554_openshift. Worker node patch updates can be applied by updating, reloading (in classic infrastructure), or replacing (in VPC infrastructure) the worker node.



Changes since version 4.6.42_1552_openshift

 Component Previous Current Description 

 OpenShift Container Platform 4.6.42 4.6.43 See [change logs](https://docs.openshift.com/container-platform/4.6/release_notes/ocp-4-6-release-notes.htmlocp-4-6-43). 







 Change log for master fix pack 4.6.42_1553_openshift, released 25 August 2021
* Resolves the following CVEs: [CVE-2023-27535](https://nvd.nist.gov/vuln/detail/CVE-2023-27535)[CVE-2022-36227](https://nvd.nist.gov/vuln/detail/CVE-2022-36227)[CVE-2022-3204](https://nvd.nist.gov/vuln/detail/CVE-2022-3204)[CVE-2022-35252](https://nvd.nist.gov/vuln/detail/CVE-2022-35252)[CVE-2022-43552](https://nvd.nist.gov/vuln/detail/CVE-2022-43552)[CVE-2023-29400](https://nvd.nist.gov/vuln/detail/CVE-2023-29400)[CVE-2023-24540](https://nvd.nist.gov/vuln/detail/CVE-2023-24540)[CVE-2023-24539](https://nvd.nist.gov/vuln/detail/CVE-2023-24539)
* Updates the UBI to version 8.8-860.
* Updates Go to version 1.19.9.







 Revision 2, released 04 May 2023 



* Resolves the following CVEs: [CVE-2023-0361](https://nvd.nist.gov/vuln/detail/CVE-2023-0361)[CVE-2023-24536](https://nvd.nist.gov/vuln/detail/CVE-2023-24536)[CVE-2023-24537](https://nvd.nist.gov/vuln/detail/CVE-2023-24537)[CVE-2023-24538](https://nvd.nist.gov/vuln/detail/CVE-2023-24538)
GPU device plug-in and installer 58d7589 7fd867d Updated image for [CVE-2021-36222](https://nvd.nist.gov/vuln/detail/CVE-2021-36222), [CVE-2021-37750](https://nvd.nist.gov/vuln/detail/CVE-2021-37750), [CVE-2021-22922](https://nvd.nist.gov/vuln/detail/CVE-2021-22922), [CVE-2021-22923](https://nvd.nist.gov/vuln/detail/CVE-2021-22923) and [CVE-2021-22924](https://nvd.nist.gov/vuln/detail/CVE-2021-22924). 
 IBM Cloud Controller Manager v1.22.2-3 v1.22.3-2 Updated to support the Kubernetes 1.22.3 release and to use Go version 1.16.9. Updated image for [DLA-2797-1](https://www.debian.org/lts/security/2021/dla-2797). 
 IBM Cloud RBAC Operator e3cb629 4ca5637 Updated universal base image (UBI) to the latest 8.4 version to resolve CVEs. 
 Key Management Service provider v2.3.8 v2.3.10 Updated Go module dependencies and to use Go version 1.16.9. Updated image for [CVE-2021-22946](https://nvd.nist.gov/vuln/detail/CVE-2021-22946). 
 Konnectivity agent v0.0.24_262_iks v0.0.24_268_iks Update to use Go version 1.16.9. 
 Konnectivity server v0.0.24_262_iks v0.0.24_268_iks Update to use Go version 1.16.9.
image: icr.io/ext/logdna-agent:3.2.0-20210629.b52135aba711

Do not change any other instances of the version number in the yaml file.
* In the securityContext section, add the following lines to run the agent as non-root:

securityContext:
 Add these 2 lines to run as non-root
runAsUser: 5000
runAsGroup: 5000

This section needs to be in the spec/containers/name branch at the same indentation level as capabilities.
* Add any custom tags from your version 2 yaml file to the LOGDNA_TAGS.
* Save the updated yaml file as logging-agent-resources-private.yaml.









 Step 7. Deploy the logging agent version 3 in the cluster 

Install the agent by running the following command:

kubectl create -f <logging-agent-resources yaml file>

For example:

kubectl create -f logging-agent-resources-private.yaml





 Step 8. Verify that the logging agent is deployed successfully 

To verify that the logging agent is deployed successfully, run the following command:

kubectl get pod -n ibm-observe

The deployment is successful when you see one or more logging pods.



* The number of logging pods equals the number of worker nodes in your cluster.
* All pods must be in a Running state.
Instance group Create Editor for Virtual Server for VPC and Block Storage for VPC resources<br><br>Operator for the VPC and subnet<br><br>Viewer for the instance template<br><br>Editor for the load balancer, if a load balancer is to be associated 
 Instance group Update Editor for the instance group<br><br>Operator for the subnet<br><br>Viewer for the instance template<br><br>Editor for the load balancer, if a load balancer is specified 
 Instance group Delete Editor for the instance group<br><br>Editor for the associated instances<br><br>Editor for the load balancer, if a load balancer is specified 
 Instance group View, List Viewer for the instance group 
 Instance group membership Update Editor for the instance group 
 Instance group membership Delete Editor for the instance group<br><br>Editor for the associated instance<br><br>Editor for the load balancer, if a load balancer is specified 
 Instance group manager Create, Update, Delete Editor for the instance group 
 Instance group manager View Viewer for the instance group 
 Instance group manager policy Create, Update, Delete Editor for the instance group 
 Instance group manager policy View Viewer for the instance group 
 Instance network interface Create, Update IP Spoofing Operator for instance 
 Instance template Create, Update, Delete Editor for instance 
 Instance template View Viewer for instance 
 ———————— ————————— ———————— 
 Load balancer Create Editor for load balancer for VPC resources<br><br>Operator for security groups<br><br>Viewer for VPC 
 Load balancer Update Editor for the load balancer 
 Load balancer Delete Editor for the load balancer<br><br>Operator for security groups 
 Load balancer View, List Viewer for the load balancer 
 Load balancer pools and listeners Create, Update, Delete Editor for the load balancer 
 Load balancer pools and listeners View, List Viewer for the load balancer 
 ———————— ————————— ———————— 
 Placement group View Viewer for placement groups
The logging agent version 2 and version 3 are supported for Kubernetes 1.9+ and later.

To configure the logging agent by using kubectl commands, run the following command:



Table 1. Configuration commands

 Type of endpoint Command 

 Public endpoint kubectl apply -f https://assets.<REGION>.logging.cloud.ibm.com/clients/logdna-agent/<VERSION>/agent-resources.yaml 
 Private endpoint kubectl apply -f https://assets.<REGION>.logging.cloud.ibm.com/clients/logdna-agent/<VERSION>/agent-resources-private.yaml 



Where



* <REGION> indicates the region where the logging instance is available. For more information about regions, see [Locations](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-regions).
* <VERSION> indicates the version of the agent that you want to deploy. You must use a version that has a tag with the following format: X.Y.Z.



If you need to use a version that has a tag with any of the following formats: X.Y.Z-<date>.[hash], X, or X.Y, you must download the agent yaml file and modify it. Replace the version for all entries app.kubernetes.io/version in the file with the one that you want to use. You must download the yaml file that has the format X.Y.Z. Then, after you make the version changes, you can run kubectl apply -f <CUSTOM_YAML_FILE> to deploy the agent.

For more information about the agent tags, see [Understanding image tags](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-log_analysis_agentlog_analysis_agent_image_kube_tags).

For more information about the versions that are available, see [Getting information about Kubernetes logging agent images](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-log_analysis_agent_image).
Updated image for [CVE-2021-33194](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-33194). 
 Konnectivity agent v0.0.19e_201_iks v0.0.19e_206_iks Updated image for [CVE-2021-27219](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-27219). 
 Konnectivity server v0.0.19e_201_iks v0.0.19e_206_iks Updated image for [CVE-2021-27219](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-27219). 
 Kubernetes v1.21.1 v1.21.2 See the [Kubernetes release notes](https://github.com/kubernetes/kubernetes/releases/tag/v1.21.2). 
 Portieris admission controller v0.10.2 v0.10.3 See the [Portieris admission controller release notes](https://github.com/IBM/portieris/releases/tag/v0.10.3). 







 Change log for worker node fix pack 1.21.1_1521, released 22 June 2021 

The following table shows the changes that are in the worker node fix pack 1.21.1_1521. Worker node patch updates can be applied by updating, reloading (in classic infrastructure), or replacing (in VPC infrastructure) the worker node.



Changes since version 1.21.1_1520

 Component Previous Current Description
https://nvd.nist.gov/vuln/detail/CVE-2021-3326), [CVE-2021-35942](https://nvd.nist.gov/vuln/detail/CVE-2021-35942), [CVE-2021-3999](https://nvd.nist.gov/vuln/detail/CVE-2021-3999), [CVE-2022-0001](https://nvd.nist.gov/vuln/detail/CVE-2022-0001), [CVE-2022-23218](https://nvd.nist.gov/vuln/detail/CVE-2022-23218), [CVE-2022-23219](https://nvd.nist.gov/vuln/detail/CVE-2022-23219), [CVE-2022-25313](https://nvd.nist.gov/vuln/detail/CVE-2022-25313), [CVE-2022-25314](https://nvd.nist.gov/vuln/detail/CVE-2022-25314), [CVE-2022-25315](https://nvd.nist.gov/vuln/detail/CVE-2022-25315). 







 Change log for master fix pack 1.23.4_1520, released 3 March 2022 



Changes since version 1.23.3_1518

 Component Previous Current Description 

 Cluster health image v1.3.0 v1.3.3 Updated golang.org/x/crypto to v0.0.0-20220214200702-86341886e292. Adds fix for [CVE-2021-43565](https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-43565). Adds Golang dependency updates. 
 Gateway-enabled cluster controller 1586 1653 Updated to use Go version 1.17.7 and updated Go modules to fix CVEs.
: See the Istio release notes for [Istio 1.13.8](https://istio.io/latest/news/releases/1.13.x/announcing-1.13.8/).
: Resolves the following CVEs:



* [usn-5587-1](https://ubuntu.com/security/notices/USN-5587-1)
* [usn-5550-1](https://ubuntu.com/security/notices/USN-5550-1)
* [CVE-2021-4209](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-4209)
* [CVE-2022-2509](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-2509)
* [CVE-2022-35252](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-35252)







 Change log for 1.13.7, released 16 August 2022 

Review the changes that are included in version 1.13.7 of the managed Istio add-on.

Previous version
: 1.13.5

Current version
: 1.13.7

Updates in this version
: See the Istio release notes for [Istio 1.13.7](https://istio.io/latest/news/releases/1.13.x/announcing-1.13.7/.).
: Resolves the following CVEs:



* [usn-5473-1](https://ubuntu.com/security/notices/USN-5473-1)
* [CVE-2022-32205](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32205)
* [Upgrading Watson Discovery from Version 4.0.x](https://www.ibm.com/docs/SSQNUZ_4.6.x/svc-discovery/discovery-upgrade-v4.html).



If you use IBM Cloud Pak for Data Red Hat OpenShift APIs for Data Protection (OADP) backup and restore utility to back up and restore an entire cluster to 4.6, a few extra steps are required. For more information, see [Using OADP to back up a cluster where Discovery is installed](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-backup-restorebackup-restore-oadp).

You can do an in-place upgrade from one 4.6.x version to a later 4.6.y version. For more information, see [Upgrading Watson Discovery from Version 4.6.x to a later 4.6 refresh](https://www.ibm.com/docs/SSQNUZ_4.6.x/svc-discovery/discovery-upgrade-v46.html).

You can do an in-place upgrade from one 4.5.x version to a later 4.5.y version. For more information, see [Upgrading Watson Discovery to the latest Version 4.5 refresh](https://www.ibm.com/docs/SSQNUZ_4.5.x/svc-discovery/discovery-upgrade-v45x.html).

You can do an in-place upgrade from one 4.0.x version to a later 4.0.y version. For more information, see [Upgrading Watson Discovery to a newer 4.0 refresh](https://www.ibm.com/docs/SSQNUZ_4.0/svc-discovery/discovery-upgrade-v4.html).



 Process overview 

At a high level, the process includes the following steps:



1. Back up your Discovery data by using the backup script.
2. Install the latest version of IBM Cloud Pak for Data.
3. Install the latest version of the Discovery service on the cluster.
4.
If you are using VRA in a high availability mode, run step 1 to step 7 again on the second machine.



The following example illustrates the upgrade process.

vyatta@vra01:$ show version | grep Version
Version: 5.2R5S3

vyatta@vra01:$ add system image /tmp/vyatta-vrouter-5.2R5S4_amd64.iso
Welcome to the Brocade vRouter image installer.
Checking MD5 checksums of files on the ISO image...OK.
What would you like to name this image? [5.2R5S4.08091424]: 5.2R5S4
This image will be named: 5.2R5S4
Would you like to save the current configuration
directory and config file? (Yes/No) [Yes]:
Saving current configuration...
Would you like to save the SSH host keys from your
current configuration? (Yes/No) [Yes]:
Saving SSH keys...
Copying squashfs image...
Copying kernel and initrd images...
Copying saved configuration to config partition.
Copying saved SSH host keys.
Enter the desired system console [tty0]:
Enter the console speed [38400]:
Running post-install script...
Done.

vyatta@vra01:$ show system image
The system currently has the following image(s) installed:

1: 5.2R5S3.06301309 (running image)
2: 5.2R5S4 (default boot)

vyatta@vra01:$ reboot
Proceed with reboot? (Yes/No) [No] y
The system is going down for reboot NOW!

vyatta@vra01:$ show version | grep Version
Version: 5.2R5S4
This capability is available starting with version 4.7. Do not complete this task until after you upgrade your service software to 4.7.

After you enable TLS for the Windows Agent service, any existing collections in deployments with earlier versions of Discovery will not be able to connect to this Windows Agent service.

To add TLS support to an existing collection, complete the following steps:



1. Open the Processing settings page for the existing Window File System collection.
2. Install the latest version of the agent.

Complete the steps in the [Installing the agent](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-connector-wfs-cp4dconnector-wfs-cp4d-prereq1-new) procedure, starting with Step 4 and including the optional step to enable TLS support.

Do not complete the last step that asks you to restart your computer.
3. Find and open the as.cfg file in a text editor, and then add the following lines to the file:

agent_key_store=%ES_AGENT_NODE_ROOT%tls.p12
agent_key_store_password=changeit

where %ES_AGENT_NODE_ROOT% is the root directory for the Windows Agent server. For example:

agent_key_store="C:Program FilesIBMesdistributedesadmintls.p12"
agent_key_store_password=changeit
4. Restart the Windows Agent service by using the following commands:

esagent stop
esagent start