vania-janet/multiturn-rag-retrieval-data huggingface dataset:
VRVDR- 41946 N/A DSA-4202-1 CVE-2018-1000301: Debian DSA-4202-1: curl – security update 
 VRVDR- 41795 6.5 DSA-4195-1 CVE-2018-0494: Debian DSA-4195-1: wget – security update 









 1801j 

Released May 18, 2018



 Issues Resolved 



Issues resolved for 1801j

 Issue Number Priority Summary 

 VRVDR-41481 Minor VRRP on bond interface does not send VRRP advertisement 
 VRVDR-39863 Major VRRP fails over when customer removes routing-instance with GRE associated and tunnel local-address is part of VRRP 
 VRVDR-27018 Critical Running configuration file is globally readable 







 Security Vulnerabilities Resolved 



Security vulnerabilities resolved for 1801j

 Issue Number CVSS score Advisory Summary 

 VRVDR-41680 7.8 DSA-4188-1 Debian DSA-4188-1: linux – security update 









 1801h 

Released May 11, 2018.



 Issues Resolved 



Issues resolved for 1801h

 Issue Number Priority Summary 

 VRVDR-41664 Critical Dataplane drops MTU sized ESP packets 
 VRVDR-41536 Minor Dnsmasq service start-init limit hit when adding more than 4 static host entries if dns forwarding is enabled 







 Security Vulnerabilities Resolved 



Security vulnerabilities resolved for 1801h

 Issue Number CVSS score Advisory Summary 

 VRVDR- 41797 7.8 DSA-4196-1 CVE-2018-1087, CVE-2018-8897: Debian DSA-4196-1: linux security update 









 1801g 

Released May 4, 2018.



 Issues Resolved 



Issues resolved for 1801g

 Issue Number Priority Summary 

 VRVDR-41620 Major vTI interface traffic stops sending traffic after new vIF is added 
 VRVDR-40965 Major Bonding does not recover after a data plane crash 









 1801f 

Released April 23, 2018



 Issues Resolved 



Issues resolved for 1801f

 Issue Number Priority Summary
VRVDR-41558 Major The reported timestamps in packet traces are not consistent with the actual time and system clock 
 VRVDR-41469 Major One interface link down – bond is not carrying traffic 
 VRVDR-41420 Major LACP bonding state/link “u/D” with mode change active-backup to LACP 
 VRVDR-41313 Critical IPsec – VTI interface instability 







 Security Vulnerabilities Resolved 



Security vulnerabilities resolved for 1801k

 Issue Number CVSS score Advisory Summary 

 VRVDR- 42207 7.5 DSA-4217-1 CVE-2018-11358, CVE-2018-11360, CVE-2018-11362, CVE- 2018-7320, CVE-2018-7334, CVE-2018-7335, CVE02018- 7419, CVE-2018-9261, CVE-2018-9264, CVE-2018-9273: Debian DSA-4217-1: wireshark – security update 
 VRVDR- 42013 N/A DSA-4210-1 CVE-2018-3639: Speculative execution, variant 4: speculative store bypass / Spectre v4 / Spectre-NG 
 VRVDR- 42006 9.8 DSA-4208-1 CVE-2018-1122, CVE-2018-1123, CVE-2018-1124, CVE-2018- 1125, CVE-2018-1126: Debian DSA-4208-1: procps – security update 
 VRVDR- 41946 N/A DSA-4202-1 CVE-2018-1000301: Debian DSA-4202-1: curl – security update 
 VRVDR- 41795 6.5 DSA-4195-1 CVE-2018-0494: Debian DSA-4195-1: wget – security update 









 1801j 

Released May 18, 2018



 Issues Resolved 



Issues resolved for 1801j

 Issue Number Priority Summary 

 VRVDR-41481 Minor VRRP on bond interface does not send VRRP advertisement
* 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/openshift?topic=openshift-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.
* [Configuring the Linux hardened repository server](https://cloud.ibm.com/docs/vmwaresolutions/?topic=vmwaresolutions-veeam-cr-sag-lhbrmng) step defines the Ansible playbook that adds the Linux hardened backup repository as a Veeam managed server into the Veeam backup infrastructure.
* [Securing the Linux hardened repository server](https://cloud.ibm.com/docs/vmwaresolutions/?topic=vmwaresolutions-veeam-cr-sag-lhbrsecure) step describes the tasks to secure the Linux hardened repository server.



Optionally, you can use the following information:



* [Instant restore](https://cloud.ibm.com/docs/vmwaresolutions/?topic=vmwaresolutions-veeam-cr-sag-instantrestore) topic describes a use case where a cyberadmin uses a PowerShell script that uses Veeam's ability to do an instant restore of a production VM from the cyberbackup.
* [Creating a Veeam Linux managed server](https://cloud.ibm.com/docs/vmwaresolutions/?topic=vmwaresolutions-veeam-cr-sag-lnxmgdsvr) topic describes a use case where a cyberadmin uses the Veeam data integration API to access the cyberbackup.









 Cyber-recovery isolated recovery environment 



 Assumptions 



* The vCenter Server instance is already deployed and consists of:



* A three-host consolidated cluster that runs NSX-T and uses NFS data stores. Your vCenter Server instance might be different, and the step-by-step instructions can accommodate different instances.
* A gateway cluster that hosts vSRX firewall appliances.



* The Veeam service is already deployed and uses the bare metal option. However, the VSI instance is similar from a network perspective with two IP addresses; one on the primary subnet and one on the instance management subnet. The VM option has a single IP address only on the instance management subnet.







 High-level steps
Option 1 If your CentOS system is not running in IBM Cloud, log in and connect to your customer [VPN](https://www.ibm.com/cloud/vpn-access). For more information about setting up a VPN, see [Set up SSL VPN connections](https://cloud.ibm.com/docs/iaas-vpn?topic=iaas-vpn-setup-ipsec-vpn). After you connect to your VPN, [go to the IBM Cloud download site ](http://downloads.service.softlayer.com/citrix/xen/) and select the vhd-util tool RPM package file: vhd-util-standalone-3.5.0-xs.2+1.0_71.2.2.x86_64.rpm .

Option 2 If you can't download the RPM package file directly into your CentOS system, then connect to your customer VPN and download the file to the workstation that you're working on. You can then upload it to your CentOS system by using the secure copy (scp) command. If you're using a virtual server instance in IBM Cloud, use the system’s public IP address for the upload by using the following command.

scp vhd-util-standalone-3.5.0-xs.2+1.0_71.2.2.x86_64.rpm root@<vsi_public_ip>:

Option 3 If you choose to provision a CentOS virtual server instance inside IBM Cloud in step 1, you can use the following curl command without connecting to your customer VPN:

curl -O http://downloads.service.softlayer.com/citrix/xen/vhd-util-standalone-3.5.0-xs.2+1.0_71.2.2.x86_64.rpm
3. Install the RPM by using the following command:

rpm -iv vhd-util-standalone-3.5.0-xs.2+1.0_71.2.2.x86_64.rpm
4.
Review the changes that are in version 1.4.4 of the managed Istio add-on.

Previous version
: 1.4.3

Current version
: 1.4.4

Updates in this version
: See the Istio release notes for [Istio 1.4.4](https://istio.io/latest/news/releases/1.4.x/announcing-1.4.4/).
: Disables [protocol sniffing and detection](https://istio.io/latest/docs/ops/configuration/traffic-management/protocol-selection/).
: Improves the termination sequence for rolling updates of ingress and egress gateways.
: Resolves the following CVEs



* [CVE-2020-8595](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-8595)
* [CVE-2019-13627](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-13627)
* [CVE-2019-15166](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-15166)
* [CVE-2019-1010220](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-1010220)
* [CVE-2019-19906](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-19906)
* [CVE-2019-15167](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-15167)
* [CVE-2019-20386](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-20386)
Follow these steps if you need to use another version of the OpenShift CLI than the one pre-installed:



1. Download the latest stable 4.x OpenShift CLI (oc)

curl https://mirror.openshift.com/pub/openshift-v4/clients/ocp/stable/openshift-client-linux.tar.gz --output oc.tar.gz
2. Extract oc.tar.gz:

tar zxvf oc.tar.gz oc
3. Add your current directory to PATH

export PATH=$PWD:$PATH
4. Verify the installation with:

oc version
hdb_concurent_jobs hdb_concurent_jobs 
 kit_hdbclient_file kit_hdbclient_file 
 kit_igsexe_file kit_igsexe_file 
 kit_igshelper_file kit_igshelper_file 
 kit_s4hana_export kit_s4hana_export 
 kit_sapcar_file kit_sapcar_file 
 kit_sapexe_file kit_sapexe_file 
 kit_sapexedb_file kit_sapexedb_file 
 kit_saphana_file kit_saphana_file 
 kit_saphotagent_file kit_saphotagent_file 
 kit_swpm_file kit_swpm_file 
 sap_ascs_instance_number sap_ascs_instance_number 
 sap_ci_instance_number sap_ci_instance_number 
 sap_sid sap_sid 



5. Accept the license agreement.
6. Select Install. The deployment starts and you are directed to the Schematics page that displays the script log files for you to monitor the deployment progress.







 Procedure for Schematics interface 

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



1. From the IBM Cloud menu, select [Schematics](https://cloud.ibm.com/schematics/overview).
2. Click Create workspace.
3. On the Specify template page:



* Enter the URL for the Schematics interface.
* Select the Terraform version.
* Click Next.



4. On the Workspace details page:



* Enter a name for the workspace.
* Select a Resource group.
* Select a Location for your workspace. The workspace location does not have to match the resource location.
* Select Next.



5. Select Create to create your workspace.
6.
* [CVE-2021-22947](https://nvd.nist.gov/vuln/detail/CVE-2021-22947)
* [CVE-2021-33928](https://nvd.nist.gov/vuln/detail/CVE-2021-33928)
* [CVE-2021-33929](https://nvd.nist.gov/vuln/detail/CVE-2021-33929)
* [CVE-2021-33930](https://nvd.nist.gov/vuln/detail/CVE-2021-33930)
* [CVE-2021-33938](https://nvd.nist.gov/vuln/detail/CVE-2021-33938)







 Version 4.7.0_854, released on 7 September 2021 



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









 Version 4.6.0 



 Version 4.6.0_2289, released on 14 Jul 2022 

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





 Version 4.6.0_2245, 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).
* [CVE-2022-1271](https://nvd.nist.gov/vuln/detail/CVE-2022-1271).
* [CVE-2018-16300](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-16300)
* [CVE-2018-16228](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-16228)
* [CVE-2018-14465](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-14465)
* [CVE-2017-16808](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-16808)



: For more information, see the [Istio security bulletin 2020-001](https://istio.io/latest/news/security/istio-security-2020-001/)





 Change log for 1.4.3, released 16 January 2020 

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

Previous version
: 1.4.2

Current version
: 1.4.3

Updates in this version
: See the Istio release notes for [Istio 1.4.3](https://istio.io/latest/news/releases/1.4.x/announcing-1.4.3/).
: Disables [protocol sniffing and detection](https://istio.io/latest/docs/ops/configuration/traffic-management/protocol-selection/).
: Improves the termination sequence for rolling updates of ingress and egress gateways.





 Change log for 1.4.2, released 16 December 2020 

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

Previous version
: 1.4.0

Current version
: 1.4.2

Updates in this version
Review the changes that are in version 1.11.4 of the managed Istio add-on.

Previous version
: 1.11.3

Current version
: 1.11.4

Updates in this version
: See the Istio release notes for [Istio 1.11.4](https://istio.io/latest/news/releases/1.11.x/announcing-1.11.4/).





 Change log for 1.11.3, released 7 October 2021 

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

Previous version
: 1.11.2

Current version
: 1.11.3

Updates in this version
: See the Istio release notes for [Istio 1.11.3](https://istio.io/latest/docs/releases/supported-releases/support-status-of-istio-releases).
: Resolves the following CVEs



* [CVE-2021-22945](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-22945)
* [CVE-2021-22946](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-22946)
* [CVE-2021-22947](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-22947)
* [CVE-2021-33560](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-33560)
* [CVE-2021-40528](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-40528)
Determining your IBM Cloud Activity Tracker Event Routing configuration version 

To collect auditing events in your IBM Cloud account, you can configure Activity Tracker Event Routing by using the Activity Tracker Event Routing API or the Activity Tracker Event Routing CLI. You can have a V1 configuration or a V2 configuration.



 IAM permissions 

You must grant users IAM permissions to manage the account settings. For more information, see [Assign access to resources](https://cloud.ibm.com/docs/account?topic=account-assign-access-resources).

When you define a policy, you can must set the scope of the policy to the account. A route is a global resource that is not bound to a specific region.



Table 1. Required IAM roles to manage the Activity Tracker Event Routing account settings.

 IAM action IAM Policy scope IAM Roles Description 

 atracker.setting.get Account Administrator <br>Editor <br>Viewer <br>Operator Get setting information 
 atracker.setting.update Account Administrator Update settings 







 Determining your CLI version 

To use the V2 configuration you must have the V2 API and CLI installed.

If you are unsure if your CLI environment is running the V2 configuration, run the following command:

ibmcloud atracker setting get

If the command indicates that setting is not a valid command, then you do not have the V2 CLI installed.

Install the V2 CLI by running the following command:

ibmcloud plugin install atracker

Update the V2 CLI by running the following command:

ibmcloud plugin update atracker





 Determining if you have V1 routes and targets 

Once you have upgraded to the V2 CLI you can run the following command to check the configuration version running in your IBM Cloud® Activity Tracker Event Routing deployment.

ibmcloud atracker setting get

If the response shows your deployment is running V1, you will need to [migrate your route and target configuration to a V2 configuration.](https://cloud.ibm.com/docs/atracker?topic=atracker-migrate-resources)





 Next steps
* Resolves the following CVEs: [CVE-2022-37434](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-37434), [CVE-2022-2509](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-2509), [CVE-2022-40674](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-40674), [CVE-2020-35525](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-35525), [CVE-2020-35527](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-35527), [CVE-2022-3515](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-3515).







 Change log for version 4.4.11_1614, released 23 September 2022 



* Updates the storage-secret-sidecar image to v1.2.8.
* Updates the golang version to 1.18.6.
* 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
: For more information, see the [Istio security bulletin](https://istio.io/latest/news/security/istio-security-2020-005/)





 Change log for 1.4.8, released 30 April 2020 

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

Previous version
: 1.4.7

Current version
: 1.4.8

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



* [CVE-2017-15412](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-15412)
* [CVE-2016-5131](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-5131)
* [CVE-2018-14404](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-14404)
* [CVE-2015-8035](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-8035)
* [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)
Upgrading the OS 

Upgrading the VRA operating system can be performed with the command add system image on a local ISO file uploaded by our IBM® Support team. A list of available Vyatta upgrade versions can be obtained using the IBM Support case system.

To begin the upgrade process, open an IBM Support case requesting an upload of the latest stable ISO image to your system. You receive a case update from IBM Support (ACS-Security) indicating where the ISO file was uploaded. In the following example, it is in the directory tmp, but it is commonly uploaded to /home/vyatta.

The upgrade process illustrated in this example is for a single VRA. If you are using VRA in high availability mode, you must run the same upgrade command on both systems. Furthermore, it is recommended that you upgrade the BACKUP machine first, and verify that it is working properly. Then access the MASTER machine and fail it over using the reset vrrp command. Finally, upgrade the original MASTER after the BACKUP has taken control.

To upgrade the VRA, perform the following procedure.



1. Run the command add system image <Local ISO File>.
2. Press Enter to accept the default name of the ISO image, or enter your own.
3. Select Yes to save the current configuration directory and configuration file.

Choosing No will erase your configuration.
4. Choose whether to save the SSH host keys from your current configuration.
5. Press Enter to accept the default system console, or enter your own.
6. Press Enter to accept the default console speed, or enter your own.
7. Enter the command reboot and then enter Yes to reboot the machine.
8. 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
* [CVE-2020-6096](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-6096)
* [CVE-2021-27645](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-27645)
* [CVE-2021-3326](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-3326)
* [CVE-2021-35942](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-35942)
* [CVE-2021-3998](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-3998)
* [CVE-2021-3999](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-3999)
* [CVE-2022-23218](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-23218)
* [CVE-2022-23219](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-23219)



: For more information, see the [Istio security bulletin 2022-004](https://istio.io/latest/news/security/istio-security-2022-004/).





 Change log for 1.12.4, released 8 March 2022 

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

Previous version
: 1.12.3

Current version
: 1.12.4

Updates in this version
wdc04 Washington D.C. 10.3.160.0/20 <br>10.201.0.0/20 <br>161.26.92.0/22 <br>161.26.132.0/22 <br>166.9.20.0/23 <br>166.9.231.0/24 
 wdc06 Washington D.C. 10.200.160.0/20 <br>161.26.120.0/22 <br>166.9.22.0/23 <br>166.9.232.0/24 <br>166.9.251.64/27 
 wdc07 Washington D.C. 10.200.176.0/20 <br>161.26.132.0/22 <br>166.9.24.0/23 <br>166.9.233.0/24 <br>166.9.251.96/27 





 Service by data center 

As of 8 June 2020, all instances of the AdvMon (Nimsoft) by Data Center service are deprecated and are no longer supported. For more information, see [FAQs](https://cloud.ibm.com/docs/virtual-servers?topic=virtual-servers-faq-monitoringwhat-are-important-transition-dates).

eVault

File & Block

AdvMon (Nimsoft)



Table 5. eVault by Data Center

 Data center IP range 

 Required Flows:<br><br><br><br> * Outbound TCP 8086 and TCP 8087 from your private <br> VLANs to IP ranges documented in dal09 and dal10 only.<br> * Outbound TCP 2546 from your private VLANs to IP ranges <br> documented for each DC where you need to access your vault.<br><br><br> 
 ams03 10.3.134.0/24 
 che01 10.200.22.0/24 
 dal05 10.1.146.0/24 
 dal08 100.100.6.0/24 
 dal09 10.2.118.0/24
[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. [VPN administration](https://cloud.ibm.com/docs/hp-virtual-servers?topic=hp-virtual-servers-tutorial_networkvpn_admin)
5. [End to end encryption via the VPN tunnel](https://cloud.ibm.com/docs/hp-virtual-servers?topic=hp-virtual-servers-tutorial_networkvpn_tunnel)







 Step 1: Configuring the virtual servers 

The Hyper Protect Virtual Servers instances are considered as 'HPVS_A', and 'HPVS_B', in this tutorial. For each of these two instances, complete the following steps:



1. To install CA certificates, run the following command:

apt-get update && apt-get install -y ca-certificates
2. Create the authorized_user file and save it at /data/hpagent_store/authorized_user, with a list of IBM Cloud user IDs. The secure network management agent uses this list to approve a request and rejects any request that is not in this list. To create the authorized_user file, run the following commands:

mkdir -p /data/hpagent_store
cat <<EOF > /data/hpagent_store/authorized_user
<email_of _authorized_user>
EOF
3. If the secure network management agent is deployed in a Hyper Protect Virtual Server instance which is in the staging environment (you should not run this command in the production environment), then you must export the following variable:

export isProduction=false
4.