vania-janet/multiturn-rag-retrieval-data huggingface dataset:
* [CVE-2021-3450](https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3450)







 Version 4.6.0_646, released on 30 Mar 2021 



* [CVE-2021-3114](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-3114)
* [CVE-2021-3115](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-3115)









 Version 4.5.0 (Unsupported) 

Version 4.5.0 is unsupported.



 Version 4.5.0_861, released on 21 September 2021 



* [CVE-2021-3711](https://nvd.nist.gov/vuln/detail/CVE-2021-3711)
* [CVE-2021-3712](https://nvd.nist.gov/vuln/detail/CVE-2021-3712)







 Version 4.5.0_837, released on 23 August 2021 



* [CVE-2021-36221](https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-36221)
* [CVE-2021-3121](https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3121)







 Version 4.5.0_790, released on 10 August 2021 



* [CVE-2021-33910](https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-33910)







 Version 4.5.0_749, released on 26 Jul 2021 



* [CVE-2021-27219](https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-27219)
* [CVE-2022-0778](https://nvd.nist.gov/vuln/detail/CVE-2022-0778).
* [CVE-2022-24921](https://nvd.nist.gov/vuln/detail/CVE-2022-24921).







 Version 4.9.0_1364, released on 14 March 2022 

Resolves [CVE-2022-24407](https://nvd.nist.gov/vuln/detail/CVE-2022-24407).





 Version 4.9.0_1349, released on 28 February 2022 



* [CVE-2022-23772](https://nvd.nist.gov/vuln/detail/CVE-2022-23772).
* [CVE-2022-23773](https://nvd.nist.gov/vuln/detail/CVE-2022-23773).
* [CVE-2022-23806](https://nvd.nist.gov/vuln/detail/CVE-2022-23806).







 Version 4.9.0, released on 16 February 2022 

Initial release of 4.9.0.







 Version 4.8.0 



 Version 4.8.0_2269, released on 14 Jul 2022 

Resolves [CVE-2022-2097](https://nvd.nist.gov/vuln/detail/CVE-2022-2097).





 Version 4.8.0_2246, released on 7 Jul 2022 



* [CVE-2021-38561](https://nvd.nist.gov/vuln/detail/CVE-2021-38561).
* [CVE-2022-21698](https://nvd.nist.gov/vuln/detail/CVE-2022-21698).
To access the Linux hardened repository, you need to go in through the IPMI on the IBM Cloud® portal.





 Accessing the Veeam console by using Remote Desktop Protocol 

To manage the Veeam service, access the Veeam console by completing the following steps:



1. Use Remote Desktop Protocol to connect to the Windows® IP address.
2. Log in to the Windows® console by using the Administrator credentials.
3. Access the Veeam console from the Windows console by using the Administrator credentials.



You can find the Windows IP address and the Administrator credentials on the Veeam service details page.

For more information, see [Ordering services for vCenter Server instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_addingservices).





 Backing up and restoring management components for instances with Veeam installations 

The Veeam service can be configured to back up the management components by using the Veeam console. For more information, see [Backing up components](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-solution_backingup).

For instances deployed in (or upgraded to) V1.8 or later releases, the configuration changes to your environment are not automatically backed up. Therefore, before you change the configuration of your environment, it is recommended that you back up the management components manually by running the management backup job in the Veeam console. For more information about backing up manually, see the [Veeam technical instructions](https://helpcenter.veeam.com/backup/vsphere/scheduing_manual.html).

When failures occur on the management components, you can restore the management components to a previous backup by using the Veeam console. For more information about restoring manually, see the [Veeam technical instructions](https://helpcenter.veeam.com/backup/vsphere/performing_full_recovery.html).





 Applying updates to Veeam 

You are responsible for maintaining the Veeam software to keep it updated to the most recent version.
* Resolves the following CVEs: [CVE-2022-27664](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-27664), [CVE-2022-32190](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32190).







 Change log for version 4.4.10_1578, released 13 September 2022 



* Updates the storage-secret-sidecar image to v1.2.7
* Resolves the following CVEs: [CVE-2022-32206](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32206), [CVE-2022-32208](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32208), [CVE-2022-2526](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-2526).







 Change log for version 4.4.9_1566, released 25 August 2022 



* Updates Golang to version 1.18.5
* Updates the storage-secret-sidecar image to v1.2.6
Ciena Vyatta 5600 vRouter software patches (current) 

On 31 December 2022, all 1912 versions of IBM Cloud Virtual Router Appliance will be deprecated and no longer supported. To maintain your current functionality, be sure to update to version 2012, 2110 or 2204 prior to 31 December 2022 by opening a [support case](https://cloud.ibm.com/docs/virtual-router-appliance?topic=gateway-appliance-getting-help) and requesting an updated ISO. Once you receive your ISO, you can then follow the instructions for [Upgrading the OS](https://cloud.ibm.com/docs/virtual-router-appliance?topic=virtual-router-appliance-upgrading-the-os) to finish updating your version.

As of January 2022, all 1801 versions of IBM Cloud Virtual Router Appliance (VRA) are deprecated and no longer supported. To maintain support for your VRA, be sure to update to version 2012, 2110, or 2204 as soon as possible by opening a [support case](https://cloud.ibm.com/docs/virtual-router-appliance?topic=gateway-appliance-getting-help) and requesting an updated ISO. Once you receive your ISO, you can then follow the instructions for [Upgrading the OS](https://cloud.ibm.com/docs/virtual-router-appliance?topic=virtual-router-appliance-upgrading-the-os) to finish updating your version.

Latest patch received: October 31, 2022

Latest documentation published: November 16, 2022

This document lists the patches for the currently supported versions of Vyatta Network OS 5600. Patches are named with a lowercase letter, excluding “i”, “o”, “l”, and “x”.

When multiple CVE numbers are addressed in a single update, the highest CVSS score is listed.

For the latest full release notes, please open a [support case](https://cloud.ibm.com/docs/virtual-router-appliance?topic=gateway-appliance-getting-help).
To obtain a login ID for the Caveonix service provider portal for product release notes and downloads, open a support case with the [IBM Cloud Support Center](https://cloud.ibm.com/unifiedsupport/supportcenter).

Provide the instance name that Caveonix is installed on, your company name, and an email address for your administrator for the support case. IBM Cloud Support acquires the credentials for your login and email your administrator.





 Updating Caveonix RiskForesight licenses 

This information does not apply to Caveonix Foresight that is installed on VMware® Regulated Workloads or Security and Compliance Readiness Bundle instances.

The Caveonix RiskForesight license is valid for five years. You can update the Caveonix RiskForesight license when it expires by using the following procedure:



1. Order a new Caveonix RiskForesight license and copy it to the Caveonix RiskForesight console. For more information, see [Procedure to order Caveonix RiskForesight licenses](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-caveonix_license_orderingcaveonix_license_ordering-procedure).
2. Delete the expired license from the Caveonix RiskForesight Licenses table in the IBM Cloud for VMware Solutions console. For more information, see [Procedure to delete Caveonix RiskForesight licenses](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-caveonix_license_managingcaveonix_license_managing_procedure-delete).







 Related links 



* [Caveonix RiskForesight overview](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-caveonix_considerations)
* [Ordering Caveonix RiskForesight](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-caveonix_ordering)
-14382](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-14382), [CVE-2019-13627](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-13627), [CVE-2019-19956](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-19956), [CVE-2019-20388](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-20388), [CVE-2020-7595](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-7595), [CVE-2019-20386](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-20386), [CVE-2019-19906](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-19906), [CVE-2019-20387](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-20387), and [CVE-2019-19221](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-19221). 
 Red Hat OpenShift on IBM Cloud toolkit 4.4.0+20200821 4.4.0+20201110 See the [Red Hat OpenShift on IBM Cloud toolkit release notes](https://github.com/openshift/ibm-roks-toolkit/releases/tag/v4.4.0+20201110).
* [CVE-2023-0464](https://nvd.nist.gov/vuln/detail/CVE-2023-0464)
* [CVE-2023-0465](https://nvd.nist.gov/vuln/detail/CVE-2023-0465)







 1.4.0_3896_iks, released 24 March 2023 

Updates golang version to 1.20.2.





 1.4.0_3862_iks, released 13 March 2023 

Dependency updates.





 1.4.0_3808_iks, released 23 February 2023 



* Updates golang version to 1.20.1.
* Resolves [CVE-2022-41723](https://nvd.nist.gov/vuln/detail/CVE-2022-41723)







 1.4.0_3783_iks, released 20 February 2023 



* [CVE-2023-23914](https://nvd.nist.gov/vuln/detail/CVE-2023-23914)
* [CVE-2023-23915](https://nvd.nist.gov/vuln/detail/CVE-2023-23915)
* [CVE-2023-23916](https://nvd.nist.gov/vuln/detail/CVE-2023-23916)







 1.4.0_3755_iks, released 10 February 2023 



* [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)
* If you have not already, create a bastion server to store the SAP kits. For more information, see [Automate SAP bastion server - SAP media storage repository](https://cloud.ibm.com/docs/sap?topic=sap-sap-bastion-server).
* Download the SAP kits from the SAP Portal to your Deployment Server. Make note of the download locations. Ansible decompresses all of the archive kits. For more information, see the readme file.
* [Create or retrieve an IBM Cloud API key](https://cloud.ibm.com/docs/account?topic=account-userapikeycreate_user_key). The API key is used to authenticate with the IBM Cloud platform and to determine your permissions for IBM Cloud services.
* [Create or retrieve your SSH key ID](https://cloud.ibm.com/docs/ssh-keys?topic=ssh-keys-getting-started-tutorial). You need the 40-digit UUID for the SSH key, not the SSH key name.



During configuration you can specify an existing VPC to use, instead of creating a new VPC.

For the detailed steps about using Terraform to create only a VPC for SAP, see [Creating single-tier virtual private cloud for SAP by using Terraform](https://cloud.ibm.com/docs/sap?topic=sap-create-terraform-single-tier-vpc-sap).





 Deploying SAP BW/4HANA with the Catalog Tile interface 

Use these steps to configure the SAP BW/4HANA on your existing VPC by using the Catalog Tile interface. The scripts can take 1 - 2 hours to complete.



1. From the IBM Cloud Catalog, select the SAP BW/4HANA tile. The tile opens the Create tab for SAP BW/4HANA. For more information about this deployment, see the About tab or the Readme file link.
2. On the SAP BW/4HANA page, configure your workspace:



* Enter a name for the workspace or use the default.
* 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).







 Version 4.12.0, released 16 March 2023 

Initial release.







 Version 4.11 



 Version 4.11.12, release 28 June 2023 



* Golang updated to 1.20.5.







 Version 4.11.11, release 09 June 2023 



* Golang updated to 1.19.9.
* Updates the UBI image to 8.8-860.







 Version 4.11.10, release 05 May 2023 



* LSO channel updated.
* Golang updated to 1.19.8.
* 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).







 Version 4.11.4, released 14 February 2023 

Updates the UBI image to version 8.7-1049.1675784874.





 Version 4.11.3, released 18 January 2023
Change log for version 4.1.2_834, released 27 January 2022 



* Fixes an issue where the persistent volume watcher was unable to handle non-IBM Cloud VPC CSI driver PV updates which caused the controller pod to crash.







 Change log for version 4.1.1_827, released 20 January 2022 

Review the changes in version 4.1.1_827 of the Block Storage for VPC add-on.



* Resolves the following CVEs.



* [CVE-2021-44716](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44716)
* [CVE-2021-44717](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44717)



* Updates Golang to version 1.16.13.
* Updates the UBI image to version 8.5-218.







 Change log for version 4.1.0_807, released 06 January 2022 

Review the changes in version 4.1.0_807 of the Block Storage for VPC add-on.



* Image tags: v4.1
* Resolves [CVE-2021-3712](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-3712).
* Updates the storage-secret-sidecar image to version 1.1.4.
* Upgrades Kubernetes packages to version 1.21.
* Updates how api-key rotation is handled so that restarting the driver is no longer required.









 Version 4.0 

Review the changes in version 4.0 of the Block Storage for VPC add-on.



 Change log for version 4.0.3_793, released 22 November 2021 

Review the changes in version 4.0.3_793 of the Block Storage for VPC add-on.



* Image tags: v4.0.3
* Image tags: v4.0.2
* Resolves the following CVEs.
Upgrading the Vyatta 5400 and reusing its IP Addresses 

This option allows you to reuse your existing Vyatta 5400 device as an equivalent IBM Cloud® Virtual Router Appliance (VRA), and keep your associated IP addresses. The following procedures provide instructions for upgrading either a stand alone Vyatta 5400, or two Vyatta 5400 devices operating in a High Availability (HA) pair.



 Upgrading a stand alone Vyatta 5400 

To upgrade a single Vyatta 5400 to a IBM Cloud® Virtual Router Appliance, perform the following procedure:



1. Ensure that you have backed up your 5400 and stored the data in two different locations. This includes SSH keys, SSL certs, scripts and any other files necessary to recover your current Vyatta 5400 configuration, if necessary.
2. Reload your Vyatta 5400 to a default IBM Cloud® Virtual Router Appliance using the instructions in [this topic](https://cloud.ibm.com/docs/virtual-router-appliance?topic=virtual-router-appliance-reloading-the-os).

An OS reload will generate a new password for the root and Vyatta user IDs.
3. Make a note of the new IBM Cloud® Virtual Router Appliance password.
4. Configure the newly reloaded VRA with your desired settings using [these instructions](https://cloud.ibm.com/docs/virtual-router-appliance?topic=virtual-router-appliance-accessing-and-configuring-the-ibm-virtual-router-appliance).







 Upgrading a Vyatta 5400 high availability pair 

To upgrade two Vyatta 5400s in an HA pair, perform the following procedure:



1. Identify the Backup Vyatta 5400 device and reload it first as a IBM Cloud® Virtual Router Appliance, using the procedure above.

Ideally, a functional HA configuration shows all interfaces as either BACKUP or MASTER on a particular node. When in doubt, use the show vrrp command to confirm.
2.
* [CVE-2022-27536](https://nvd.nist.gov/vuln/detail/CVE-2022-27536).







 Version 4.9.0_1471, released on 11 April 2022 



* [CVE-2022-0778](https://nvd.nist.gov/vuln/detail/CVE-2022-0778).
* [CVE-2018-25032](https://nvd.nist.gov/vuln/detail/CVE-2018-25032).







 Version 4.9.0_1384, released on 24 March 2022 



* [CVE-2021-3999](https://nvd.nist.gov/vuln/detail/CVE-2021-3999).
* [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-23308](https://nvd.nist.gov/vuln/detail/CVE-2022-23308).
* [CVE-2021-23177](https://nvd.nist.gov/vuln/detail/CVE-2021-23177).
* [CVE-2021-31566](https://nvd.nist.gov/vuln/detail/CVE-2021-31566).
* [CVE-2022-0778](https://nvd.nist.gov/vuln/detail/CVE-2022-0778).
* [CVE-2022-24921](https://nvd.nist.gov/vuln/detail/CVE-2022-24921).







 Version 4.9.0_1364, released on 14 March 2022
* Updates the UBI.







 Version 4.9.2, released 24 February 2022 

Use PVC for mon on VPC.





 Version 4.9.1, released 23 February 2022 

Updates the UBI.





 Version 4.9.0, released 11 February 2022 

Initial release.







 Version 4.8 



 Version 4.8.31, release 05 May 2023 



* Golang updated to 1.19.8.
* 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).







 Version 4.8.4, release 17 January 2022 

Updates Golang version to 1.16.13.





 Version 4.8.3, released Jan 07, 2022 



* Updates UBI image.
* Adds increased logging.







 Version 4.8.2, released 03 January 2022 



* Removes MON parameters.
* Introduces local disk discovery.







 Version 4.8.1, released 17 November 2021 



* Removes Satellite link parameter.
* Updates Golang to 1.16.10.
* Updates the UBI.







 Version 4.8.0, released 25 October 2021 

Updates Golang to 1.16.9.







 Version 4.7 



 Version 4.7.14, released 25 October 2021 

Updates Golang to 1.16.9.





 Version 4.7.13, released 13 October 2021 

Adds an agent health check.





 Version 4.7.12, released 30 September 2021 

Includes an NC check fix.





 Version 4.7.11, released 29 September 2021
* [CVE-2019-5436](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-5436)
* [CVE-2019-3820](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-3820)
* [CVE-2019-9924](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-9924)
* [CVE-2018-14567](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-14567)
* [CVE-2015-2716](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-2716)
* [CVE-2017-18258](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-19880)
* [CVE-2020-1967](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-1967)







 Change log for 1.4.7, released 01 April 2020 

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

Previous version
: 1.4.6

Current version
: 1.4.7

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



* [CVE-2020-1764](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-1764)
* All the storage classes that are installed with the add-on now have allowVolumeExpansion=true.



After updating to version 4.2, you must complete the following steps.



* [Delete and recreate](https://cloud.ibm.com/docs/containers?topic=containers-vpc-blockvpc-addon-update) any custom storage classes that are using the sizeRange or iopsRange parameters.
* If you use a default storage class other than ibmc-vpc-block-10iops-tier, you must change the isStorageClassDefault setting to false in the addon-vpc-block-csi-driver-configmap configmap in the kube-system namespace. For more information, see [Changing the default storage class](https://cloud.ibm.com/docs/openshift?topic=openshift-vpc-blockvpc-block-default-edit).









 Version 4.1 

Review the changes in version 4.1 of the Block Storage for VPC add-on.



 Change log for version 4.1.3_846, released 14 February 2022 

Review the changes in version 4.1.3_846 of the Block Storage for VPC add-on.



* Resolves the following CVEs.



* [CVE-2021-3538](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-3538)
* [CVE-2020-26160](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-26160)









 Change log for version 4.1.2_834, released 27 January 2022 



* Fixes an issue where the persistent volume watcher was unable to handle non-IBM Cloud VPC CSI driver PV updates which caused the controller pod to crash.







 Change log for version 4.1.1_827, released 20 January 2022 

Review the changes in version 4.1.1_827 of the Block Storage for VPC add-on.
The IBM Cloud® Identity and Access Management (IAM) is used for user authentication. For more information, see [IBM Cloud Identity and Access Management](https://cloud.ibm.com/docs/account?topic=account-iamoverview).







 Before you begin 

To complete this tutorial, you need to meet the following prerequisites:



* Administrator access to the Hyper Protect Virtual Server.
* Two Hyper Protect Virtual Servers instances.
* Install the IBM Cloud CLI.





* Install the HPVS CLI plugin version 1.4.17, of IBM Cloud. The HPVS CLI plugin is a dependency of the hpnet CLI plugin.
* Install the secure network CLI plugin by running the command ibmcloud plugin install hpnet. To install the plugin in the staging environment, complete the following steps:



* Install from staging environment by running the ibmcloud plugin install hpnet -r stage1 command.
* To install plugin on production environment by running the ibmcloud plugin install hpnet command.



* Log in to IBM Cloud by using the CLI. If you have multiple accounts, select the account that your service instance is created with. Make sure that you log in to the correct region and resource group where the service instance is located by running the command ibmcloud target -r <region> -g <resource_group>







 Task flow 

To complete this solution, you walk through the following steps:



1. [Configuring the virtual servers](https://cloud.ibm.com/docs/hp-virtual-servers?topic=hp-virtual-servers-tutorial_networkconfig_vs)
2. [Configuring the audit log](https://cloud.ibm.com/docs/hp-virtual-servers?topic=hp-virtual-servers-tutorial_networkconfigaudit_log)
3. [Admin key administration](https://cloud.ibm.com/docs/hp-virtual-servers?topic=hp-virtual-servers-tutorial_networkmanage_adminkey)
4.