vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Release notes for IBM Cloud Juniper vSRX 

Find out about new and updated features in IBM Cloud® Juniper vSRX.



  21 May 2021 

Renewing a vSRX license
:   The vSRX standard and CSB licenses for both 1G and 10G that were included with deployments before mid-May 2021 have an expiration date in 2021. After this license expires, updates for some new vSRX features might not take effect. A newer license with an expiration date in 2024 is now available, and you can renew your gateway license to obtain it. If you are using a High Availability vSRX, renewing your license automatically modifies the license on both vSRX nodes. You can find the current expiration date on the gateway appliance details page.
:   For more information, refer to [Renewing a vSRX license](https://cloud.ibm.com/docs/vsrx?topic=vsrx-license-renewal).





  20 April 2020 

Checking vSRX readiness
:   You can now run readiness checks to verify the ability of your IBM Cloud® Juniper vSRX to perform certain gateway actions. They include:



*  OS reloads
*  License upgrades
*  Version upgrades



:   After you run a readiness check, errors alert you to any necessary actions that you should take before beginning one of these actions, or inform you that you're ready to proceed.
:   For more information, refer to [Checking vSRX readiness](https://cloud.ibm.com/docs/vsrx?topic=vsrx-vsrx-readinessvsrx-readiness).
Click Delete Image.









 Listing charts in the trash 

You can list deleted charts that are in the trash and see when they expire.

To find out which charts are in the trash, you can use the [ibmcloud cr trash-list](https://cloud.ibm.com/docs/Registry?topic=Registry-containerregclibx_cr_trash_list) command. Charts are stored in the trash for 30 days.

To list the charts in the trash, complete the following steps.



1. Log in to IBM Cloud by running the ibmcloud login command.
2. List the charts in the trash by running the following command.

ibmcloud cr trash-list
3. List only the charts in the trash for the namespace that you are interested in by running the following command, where <namespace> is your namespace.

ibmcloud cr trash-list --restrict <namespace>







 Restoring charts 

You can restore charts from the trash. Deleted charts are stored in the trash for 30 days.

You can restore a chart from the trash by running the [ibmcloud cr image-restore](https://cloud.ibm.com/docs/Registry?topic=Registry-containerregclibx_cr_image_restore) command. To find out which charts are in the trash, run the [ibmcloud cr trash-list](https://cloud.ibm.com/docs/Registry?topic=Registry-containerregclibx_cr_trash_list) command.

You can restore charts by running the [ibmcloud cr image-restore](https://cloud.ibm.com/docs/Registry?topic=Registry-containerregclibx_cr_image_restore) command. You can use the following options:



* <repo>@<digest>, which restores the digest and all its tags in the repository that aren't already in the live repository, see [Restoring charts by digest](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_helm_chartsregistry_helm_charts_restore_digest).
* Older Juniper vSRX gateways were deployed with a 60-day evaluation license, which might cause the kernel to generate error messages even when another (valid) license is on the system. Remove any 60-day evaluation licenses to avoid this issue. To do so, follow these steps:



1. Log in to your vSRX gateway device.
2. Enter CLI mode by running the command cli at the console prompt.
3. Run the following command to get the license identifier:

show system license

Output is similar to the following:

License usage:
Licenses Licenses Licenses Expiry
Feature name used installed needed
logical-system 0 3 0 permanent
Virtual Appliance 1 1 0 2021-10-18 00:00:00 UTC
remote-access-ipsec-vpn-client 0 2 0 permanent

Licenses installed:
License identifier: E2018101804
License version: 4
Software Serial Number: SUB00024128768
Customer ID: IBM_SL_10G
Features:
Virtual Appliance - Virtual Appliance
date-based, 2018-10-18 00:00:00 UTC - 2021-10-18 00:00:00 UTC
4. Copy the identifier of the license that you want to delete, then run the command:

request system license delete <license identifier>
Canceling a gateway appliance 

You can cancel your gateway appliance at any time by following these instructions.



1.  From your browser, open the [IBM Cloud catalog](https://cloud.ibm.com) and log in to your account.
2.  Select the Menu icon ![Menu icon](https://cloud.ibm.com/docs-content/v1/content/icons/icon_hamburger.svg) from the top left, then click Classic Infrastructure.
3.  Choose Network > Gateway Appliances.
4.  Click the Gateway Appliance name to open the Gateway Appliance Details page.
5.  From the Hardware section, click the name of the hardware member to open the server details page.
6.  Select Actions > Cancel device and follow the prompts to cancel the gateway appliance.



For Highly Available server pairs, you must select and cancel both server members listed in the Hardware section on the Gateway Appliance Details page to cancel the gateway.

After you cancel the gateway appliance, the server(s) are reclaimed at the next billing cycle. For example, if you cancel the server(s) on September 8, the service is available until it is reclaimed on October 1.

You can verify if your gateway appliance is in the process of being canceled by viewing the Gateway Appliance Details page. Gateways in the process of being canceled show as Cancel pending.

If necessary, you can expedite the process by opening a case with IBM Support and requesting that the gateway appliance be reclaimed immediately. This process can take 24 to 48 hours.
* [Bulk admin certificate renewal with Ansible playbooks](https://cloud.ibm.com/docs/blockchain?topic=blockchain-cert-mgmtcert-mgmt-bulk-ansible)
* [Expired certificates](https://cloud.ibm.com/docs/blockchain?topic=blockchain-cert-mgmtibp-console-identities-expired-certs)



* [How to fix expired organization admin certificates](https://cloud.ibm.com/docs/blockchain?topic=blockchain-cert-mgmtibp-console-identities-expired-certs-admin)



* [Using the command line to view certificate expiration](https://cloud.ibm.com/docs/blockchain?topic=blockchain-cert-mgmtibp-console-identities-cli-expiration)
* [Export an MSP](https://cloud.ibm.com/docs/blockchain?topic=blockchain-cert-mgmtcert-mgmt-export-msp)
* [Import an MSP](https://cloud.ibm.com/docs/blockchain?topic=blockchain-cert-mgmtcert-mgmt-import-msp)



[Upgrading and deleting deployed nodes](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-govern-componentsibp-console-govern-components)



* [Considerations when reallocating resources](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-govern-componentsibp-console-govern-components-reallocate-resources)



* [Monitoring file storage](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-govern-componentsibp-console-govern-components-monitor-storage)
Canceling a gateway appliance 

You can cancel your gateway appliance at any time by following these instructions.



1.  From your browser, open the [IBM Cloud catalog](https://cloud.ibm.com) and log in to your account.
2.  Select the Menu icon ![Menu icon](https://cloud.ibm.com/docs-content/v1/content/af86f2de476b09efc2fa731457e7b3e58571f062/vsrx/icons/icon_hamburger.svg) from the top left, then click Classic Infrastructure.
3.  Choose Network > Gateway Appliances.
4.  Click the Gateway Appliance name to open the Gateway Appliance Details page.
5.  From the Hardware section, click the name of the hardware member to open the server details page.
6.  Select Actions > Cancel device and follow the prompts to cancel the gateway appliance.



For Highly Available server pairs, you must select and cancel both server members listed in the Hardware section on the Gateway Appliance Details page to cancel the gateway.

After you cancel the gateway appliance, the server(s) are reclaimed at the next billing cycle. For example, if you cancel the server(s) on September 8, the service is available until it is reclaimed on October 1.

You can verify if your gateway appliance is in the process of being canceled by viewing the Gateway Appliance Details page. Gateways in the process of being canceled show as Cancel pending.

If necessary, you can expedite the process by opening a case with IBM Support and requesting that the gateway appliance be reclaimed immediately. This process can take 24 to 48 hours.
and also have the "DST Root CA X3" in their root truststore.

 How to fix it 

No actions need to be taken to IBM Cloud Kubernetes Service or Satellite. However, if there are TLS clients connecting to the Kubernetes Ingress controller, OpenShift router, or custom services with a containers.appdomain.cloud subdomain, it is recommended that these clients be updated to the latest version to prevent downtime.

For more information, see the following links.



* [Ubuntu bug report](https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1928989)
* [Workaround steps from OpenSSL](https://www.openssl.org/blog/blog/2021/09/13/LetsEncryptRootCertExpire/)
* [Extending Let's Encrypt compatibility](https://letsencrypt.org/2020/12/21/extending-android-compatibility.html)
* [Let's Encrypt production chain community](https://community.letsencrypt.org/t/production-chain-changes/150739))
* [Let's Encrypt DST Root CA X3 docs](https://letsencrypt.org/docs/dst-root-ca-x3-expiration-september-2021/)
For more information, see [Secure boot with Trusted Platform Module (TPM)](https://cloud.ibm.com/docs/vpc?topic=vpc-secure-boot-tpm).







 17 January 2023 



 For all version dates 

Bare metal server DELETE response code change. Bare metal DELETE methods now return an HTTP response code of 202 upon success:



* [Delete a network interface](https://cloud.ibm.com/apidocs/vpc/latestdelete-bare-metal-server-network-interface)
* [Disassociate a floating IP from a network interface](https://cloud.ibm.com/apidocs/vpc/latestremove-bare-metal-server-network-interface-floatin)
* [Delete a bare metal server](https://cloud.ibm.com/apidocs/vpc/latestdelete-bare-metal-server)



Unlike previous response code changes, the transition from 204 to 202 applies to all API versions. Therefore, a response code of 204 will not be returned for any API requests for these methods, regardless of the version query parameter value. Future transitions from 204 to 202 will be tied to a dated API version, as described in [Upcoming changes](https://cloud.ibm.com/docs/vpc?topic=vpc-api-change-logupcoming-changes).







 20 December 2022 



 For all version dates 

Backup policy jobs. You can now [list all jobs for a backup policy](https://cloud.ibm.com/apidocs/vpc/latestlist-backup-policy-jobs) or [retrieve a backup policy job](https://cloud.ibm.com/apidocs/vpc/latestget-backup-policy-job). A backup policy job is triggered when a scheduled backup snapshot is being created or deleted. If the create or delete action is successful, the job contains information about the backup snapshot that was created or deleted. If the job ran unsuccessfully, the job contains the reason for the failure.
Canceling a gateway appliance 

You can cancel your gateway appliance at any time by following these instructions.



1.  From your browser, open the [IBM Cloud catalog](https://cloud.ibm.com) and log in to your account.
2.  Select the Menu icon ![Menu icon](https://cloud.ibm.com/docs-content/v1/content/01ccb31b85637ed5f03008c920c9596354caaf98/virtual-router-appliance/icons/icon_hamburger.svg) from the top left, then click Classic Infrastructure.
3.  Choose Network > Gateway Appliances.
4.  Click the Gateway Appliance name to open the Gateway Appliance Details page.
5.  From the Hardware section, click the name of the hardware member to open the server details page.
6.  Select Actions > Cancel device and follow the prompts to cancel the gateway appliance.



For Highly Available server pairs, you must select and cancel both server members listed in the Hardware section on the Gateway Appliance Details page to cancel the gateway.

After you cancel the gateway appliance, the server(s) are reclaimed at the next billing cycle. For example, if you cancel the server(s) on September 8, the service is available until it is reclaimed on October 1.

You can verify if your gateway appliance is in the process of being canceled by viewing the Gateway Appliance Details page. Gateways in the process of being canceled show as Cancel pending.

If necessary, you can expedite the process by opening a case with IBM Support and requesting that the gateway appliance be reclaimed immediately. This process can take 24 to 48 hours.
Verify that the chart was deleted by running the following command, and check that the chart does not show in the list.

ibmcloud cr image-list







 Deleting charts from your private repository in the console 

You can delete unwanted charts and all their tags from your private IBM Cloud repository by using the IBM Cloud console.

Deleting a chart that is being used by an existing deployment might cause a Helm upgrade, rollback, or delete to fail.

If you want to restore a deleted chart, you can list the contents of the trash by running the [ibmcloud cr trash-list](https://cloud.ibm.com/docs/Registry?topic=Registry-containerregclibx_cr_trash_list) command and restore a selected chart by running the [ibmcloud cr image-restore](https://cloud.ibm.com/docs/Registry?topic=Registry-containerregclibx_cr_image_restore) command.

To delete a chart by using the IBM Cloud console, complete the following steps.



1. Log in to the IBM Cloud console [https://cloud.ibm.com/login](https://cloud.ibm.com/login) with your IBMid.
2. If you have multiple IBM Cloud accounts, select the account and region that you want to use from the account menu.
3. Click the Navigation menu icon, then click Container Registry.
4. Click Images. A list of your charts (and images if they exist) is displayed. The registry stores different artifact types that include Helm charts and container images.
5. In the row that contains the chart that you want to delete, select the checkbox.
6. Click Delete Image.









 Listing charts in the trash 

You can list deleted charts that are in the trash and see when they expire.

To find out which charts are in the trash, you can use the [ibmcloud cr trash-list](https://cloud.ibm.com/docs/Registry?topic=Registry-containerregclibx_cr_trash_list) command. Charts are stored in the trash for 30 days.
and also have the "DST Root CA X3" in their root truststore.

 How to fix it 

No actions need to be taken to Red Hat OpenShift on IBM Cloud or Satellite. However, if there are TLS clients connecting to the Kubernetes Ingress controller, OpenShift router, or custom services with a containers.appdomain.cloud subdomain, it is recommended that these clients be updated to the latest version to prevent downtime.

For more information, see the following links.



* [Ubuntu bug report](https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1928989)
* [Workaround steps from OpenSSL](https://www.openssl.org/blog/blog/2021/09/13/LetsEncryptRootCertExpire/)
* [Extending Let's Encrypt compatibility](https://letsencrypt.org/2020/12/21/extending-android-compatibility.html)
* [Let's Encrypt production chain community](https://community.letsencrypt.org/t/production-chain-changes/150739))
* [Let's Encrypt DST Root CA X3 docs](https://letsencrypt.org/docs/dst-root-ca-x3-expiration-september-2021/)
[Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/991f60ddbe3ab0a9aa69481a07a0a73b359fa329/icons/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/991f60ddbe3ab0a9aa69481a07a0a73b359fa329/icons/checkmark-icon.svg) 
 Secret revoked com.ibm.cloud.secrets-manager.secret_revoked One time ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/991f60ddbe3ab0a9aa69481a07a0a73b359fa329/icons/checkmark-icon.svg) 
 Secret deleted com.ibm.cloud.secrets-manager.secret_deleted One time ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/991f60ddbe3ab0a9aa69481a07a0a73b359fa329/icons/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/991f60ddbe3ab0a9aa69481a07a0a73b359fa329/icons/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/991f60ddbe3ab0a9aa69481a07a0a73b359fa329/icons/checkmark-icon.svg) 
 Secret deletion blocked com.ibm.cloud.secrets-manager.secret_deletion_blocked One time !
Why doesn't the retention command show all the images? 

An image doesn't show in the list that is produced by the IBM Cloud® Container Registry ibmcloud cr retention-run command.

  What’s happening 

You ran the [ibmcloud cr retention-run](https://cloud.ibm.com/docs/Registry?topic=Registry-containerregclibx_cr_retention_run) command and an image that you're expecting to view in the list is not displayed.

  Why it’s happening 

You might have a [distroless](https://github.com/GoogleContainerTools/distroless) image. Some distroless images don't have a creation date. The ibmcloud cr retention-run command deletes the oldest images, and therefore requires a creation date.

  How to fix it 

You can delete the image manually by running the [ibmcloud cr image-rm](https://cloud.ibm.com/docs/Registry?topic=Registry-containerregclibx_cr_image_rm) command, see [Deleting images from your private repository](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_images_registry_images_remove).

To check the creation date of an image, you can run the [ibmcloud cr image-inspect](https://cloud.ibm.com/docs/Registry?topic=Registry-containerregclibx_cr_image_inspect) command. If the image doesn't have a creation date, the date is shown in the ibmcloud cr image-inspect output as 1970-01-01, and the image is excluded from the results for ibmcloud cr retention-run.
If you cancel a virtual server or other device, you end use of that device. Devices can be canceled immediately or on a billing anniversary. After you confirm the cancellation of your device, the action cannot be undone. Refunds can't be given for immediate cancellations.

After you confirm the cancellation, the device cancellation process begins. If an immediate cancellation was requested, the device is canceled immediately. If a billing anniversary cancellation was requested, the device remains active until the next billing anniversary. Upon its cancellation, the device no longer appears in the Device List on the IBM Cloud console. Billing items are also removed from invoices when all outstanding balances are paid on the device, if any. For questions about a bill for a canceled device, [open a case](https://cloud.ibm.com/unifiedsupport/cases/add) and select Billing and usage as the type of support needed. Refunds can't be given for immediate cancellations.







 Next steps 

If you need to reconfigure an existing virtual server, see [Reconfiguring an existing virtual server](https://cloud.ibm.com/docs/virtual-servers?topic=virtual-servers-reconfiguring-virtual-serversreconfiguring-virtual-servers).
[SSP-AM-Access-Revalidation-1](https://cloud.ibm.com/docs-content/v1/content/bd177462727ef0a849ddcf8c842a6203b41f0625/mas-ms/images/SSP-AM-Access-Revalidation-1.png)
3. Select your IBMid from the list and proceed to the "Manage Access" tab. There you will see tables with all the assets and associated accesses. Remove any accesses you no longer have a business need for and press the “Save” button.

![SSP-AM-Access-Revalidation-2](https://cloud.ibm.com/docs-content/v1/content/bd177462727ef0a849ddcf8c842a6203b41f0625/mas-ms/images/SSP-AM-Access-Revalidation-2.png)
4. Press the “Re-validate CBN” button to validate your continued need for the remaining accesses.

![SSP-AM-Access-Revalidation-3](https://cloud.ibm.com/docs-content/v1/content/bd177462727ef0a849ddcf8c842a6203b41f0625/mas-ms/images/SSP-AM-Access-Revalidation-3.png)
5. The "Re-validate CBN" button should be removed from the panel (indicating successful validation).
The following information details some known unsupported configuration commands when upgrading from an older vSRX version. It is critical that you remove unsupported, or hidden, commands from the vSRX configuration prior to upgrading your version. You should do this even with commands that are not detected by the Readiness check.





 Correcting error 1145 

To remove the IDP related policies and configurations. Execute the following commands to gather all dependencies.

show security policies | match idp | display set
show system scripts | display set
show security idp | display set

Then delete the configuration stanza for each of the above dependencies.

Example:

delete security policies from-zone <$zone1> to-zone <$zone2> policy
<$policy> then permit application-services idp
delete system scripts commit file templates.xsl
delete security idp





 Correcting error 1147 

Similar to the previous section, a change in the way Junos parses configuration in the security section can lead to errors like:

error: Bad url pattern: .googleapis.com/()

Examples of this configuration include:

set security utm custom-objects url-pattern AZURE value .googleapis.com/
set security utm custom-objects url-pattern website value services.site.com

The use of * as the trailing character and the prefix is no longer valid. An alternative configuration is:

set security utm custom-objects url-pattern AZURE value .googleapis.com
set security utm custom-objects url-pattern website value .services.site.com

To fix this issue, modify the vSRX configuration as needed, commit, and retry the readiness check.



 Command set interfaces.. with tcp-mss 

The following undocumented configuration could be committed in versions prior to 20.4R2-S2, but fails in 20.4R2-S2. Notice the unsupported platform output from show configuration in 19.4R3-S2.

[edit]
You are notified by email that your request to remove NFS storage is being processed. On the console, the status of the cluster that is associated with the NFS storage is changed to Modifying.
3. The NFS storage is fully reclaimed by IBM Cloud infrastructure at the end of the IBM Cloud infrastructure billing cycle, which is typically 30 days.

You are billed until the end of the IBM Cloud infrastructure billing cycle for the removed NFS storage.







 Related links 



* [Planning for Cyber Recovery](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-cr_planning)
* [Requirements for Cyber Recovery](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-cr_orderinginstance_reqs)
* [Adding clusters to Cyber Recovery instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-cr_addingclusters)
The service is missing one or more worker IPs (ERRSEIPM). For more information, see [Why does the Ingress status show an ERRSEIPM error?](https://cloud.ibm.com/docs/openshift?topic=openshift-ts-ingress-errseipm). 
 The load balancer service address is missing (ERRSAM). For more information, see [Why does the Ingress status show an ERRSAM error?](https://cloud.ibm.com/docs/openshift?topic=openshift-ts-ingress-errsam). 
 Could not access Secrets Manager instance (ESSSMI). For more information, see [Why does the Ingress status show an ESSSMI error?](https://cloud.ibm.com/docs/openshift?topic=openshift-ts-ingress-esssmi). 
 Could not access the secret group (ESSSMG). For more information, see [Why does the Ingress status show an ESSSMG error?](https://cloud.ibm.com/docs/openshift?topic=openshift-ts-ingress-esssmg). 
 The CRN does not match the default secret with the same domain (ESSVC). For more information, see [Why does the Ingress status show an ESSVC error?](https://cloud.ibm.com/docs/openshift?topic=openshift-ts-ingress-essvc). 
 The certificate for TLS secret expired or will expire soon (ESSEC). For more information, see [Why does the Ingress status show an ESSEC error?](https://cloud.ibm.com/docs/openshift?topic=openshift-ts-ingress-essec). 
 The Opaque secret field expired or will expire soon (ESSEF). For more information, see [Why does the Ingress status show an ESSEF error?]