vania-janet/multiturn-rag-retrieval-data huggingface dataset:
For more information, see [Specifying an alternative host for an API](https://www.ibm.com/support/knowledgecenter/en/SSFS6T/com.ibm.apic.toolkit.doc/task_apionprem_creating_apis.htmltask_tq2_11r_xt__enforce_step).



* Ensure that the same custom gateway URL is not applied to multiple Catalogs as the behavior in that scenario is undefined.
* When you call the API, you can also set the HTTP host header on the API request to the value that you specified in the Custom Gateway URL field.
* Custom API URL In the Custom API URL text field, enter the URL. You use the Custom API URL to specify the URL for APIs that are deployed to a third party gateway.

The Custom API URL represents the endpoint by which the API is known externally; that is, the endpoint that is published to the developer portal and used by an application developer to invoke or advertise the API.

If you are using a third party gateway or external load balancer in this Catalog, supply the URL in this field. Any API endpoints that are displayed in the developer portal will then reflect the specified URL. These endpoints exist on the third party gateway or load balancer and project a virtual address, exposed to API consumers, that is mapped to the API proxy or API assembly endpoints on the gateway. The endpoints that are derived from the custom API URL are typically published in production developer portals to advertise the address of the API.

If you specify a custom API URL for a Catalog, it takes precedence over any host name that you specify when you configure the API. For more information, see [Specifying an alternative host for an API](https://www.ibm.com/support/knowledgecenter/en/SSFS6T/com.ibm.apic.toolkit.doc/task_apionprem_creating_apis.htmltask_tq2_11r_xt__enforce_step).
* Hostname for Developer Portal API Calls: In the Port API Endpoint window area, enter a host name for Developer Portal API calls.
Using decision tools 

The third step is to use decision tools to evaluate the component options for the applicable domains against solution requirements and known constraints.

Common constraints that impact the cloud architecture design include, but are not limited to: Regulatory Compliance, Service Level Agreements (SLAs), Performance, Cost, Timeliness of Product Availability, Compatibility and Portability, Geographic Availability, and Delivery Support.

Decision tools and documentation are used to select the best component to satisfy the requirements mapped to each domain. You should evaluate available components for a specific target deployment and one or more cloud service providers to determine the best-fit-for-purpose component for your solution.

You can use your cloud service providers documentation such as IBM Cloud documentation, available comparison matricies, and decision trees to evaluate the component options. For example, see [Exploring IBM Cloud load balancers](https://cloud.ibm.com/docs/loadbalancer-service?topic=loadbalancer-service-explore) for an example of a load balancer matrix. Or, see [Compare platforms](https://cloud.ibm.com/vmware/compare_offerings) for an example of a VMware offerings matrix.
PS-5 - Personnel Transfer 



  Control requirements 

The organization:

PS-5 (a)
:   Reviews and confirms ongoing operational need for current logical and physical access authorizations to information systems/facilities when individuals are reassigned or transferred to other positions within the organization;

PS-5 (b)
:   Initiates [Assignment: organization-defined transfer or reassignment actions] within [IBM Assignment: two (2) days following the formal transfer action];

PS-5 (c)
:   Modifies access authorization as needed to correspond with any changes in operational need due to reassignment or transfer; and

PS-5 (d)
:   Notifies [Assignment: organization-defined personnel or roles] within [IBM Assignment: two (2) days of the formal transfer action].





  NIST supplemental guidance 

This control applies when reassignments or transfers of individuals are permanent or of such extended durations as to make the actions warranted. Organizations define actions appropriate for the types of reassignments or transfers, whether permanent or extended. Actions that may be required for personnel transfers or reassignments to other positions within organizations include, for example: (i) returning old and issuing new keys, identification cards, and building passes; (ii) closing information system accounts and establishing new accounts; (iii) changing information system access authorizations (i.e., privileges); and (iv) providing for access to official records to which individuals had access at previous work locations and in previous information system accounts.
SAP ID credentials are required to download SAP software installation media.





 Who is responsible for deployment of SAP software on IBM Cloud? 

The IBM Cloud® for SAP portfolio is primarily Infrastructure-as-a-Service which is certified for SAP workloads. All IaaS is considered "customer-managed" by Cloud Service Providers. All changes to the OS and any applications that are deployed are the customer's responsibility (or the responsibility of a contracted Business Partner).

The customer (or contracted Business Partner) is responsible for the installation and configuration of SAP software on IBM Cloud, which must follow SAP's guidance for the business scenario and usage.

While IBM Cloud does not provide SAP application-level services, the various IBM Cloud Business Partners (including IBM Services) do provide their service capabilities by using IBM Cloud® for SAP portfolio.

This table shows a brief list of services and the Business Partner types who can provide the services for IBM Cloud® for SAP:



 Service type Provided by Description 

 Consulting and advisory and implementation SAP "Global Systems Integrator" (GSI) providers These providers advise and run SAP implementation and deployment projects. 
 Application management SAP "Application Management Services" (AMS) providers These providers manage and maintain an existing deployment of SAP Applications (optional: incremental functional or development changes). 
 End-to-end managed services SAP "Managed Services Providers" (MSP) These providers run the SAP implementation and deployment and manage the Infrastructure, OS, SAP Technical Applications, and SAP Business Applications. These services often do not include incremental functional or development changes). 



For example, some of the services that are available in partnership between IBM Cloud and IBM Services include:



* [GSI and IBM Services: SAP Consulting & Implementation Services](https://www.ibm.com/services/sap)
* [AMS and IBM Services: SAP Application Management and Development Solutions](https://www.ibm.com/blogs/services/2019/05/08/unlocking-the-value-of-sap-applications-in-the-digital-cloud/)
* [MSP and IBM Services: Managed Applications for SAP](https://www.ibm.com/cloud/sap/managed)







 Do I need IBM Db2 to run SAP NetWeaver on IBM Cloud?
left_table.col2 AS l_col2
FROM
VALUES (0, 10), (1, 11), (2, 12), (3,13), (4, 14), (5, 14) AS left_table
ANTI JOIN
VALUES (0, 10), (2, 12), (4, 14), (6, 16) AS right_table
ON left_table.col1 = right_table.col1

The result of the example query is shown in the following table.



Table 24. Query result for example: left anti join query.

 L_COL1 L_COL2 

 1 11 
 3 13 
 5 14 







 Left semi join 

A LEFT SEMI join acts like an inner join but does not include the columns of the right table.

-- left semi join query
SELECT
left_table.col1 AS l_col1,
left_table.col2 AS l_col2
FROM
VALUES (0, 10), (1, 11), (2, 12), (3,13), (4, 14), (5, 14) AS left_table
LEFT SEMI JOIN
VALUES (0, 10), (2, 12), (4, 14), (6, 16) AS right_table
ON left_table.col1 = right_table.col1

The result of the example query is shown in the following table.



Table 25. Query result for example: left semi join query.

 L_COL1 L_COL2 

 0 10 
 2 12 
 4 14 









 Related references - join types 

The join types are specified in a [relation](https://cloud.ibm.com/docs/sql-query?topic=sql-query-sql-referencerelation).





 Sampling table data 

Any table that is object stored on Cloud Object Storage, used in a from clause, can be associated with a table sample clause. The table sample clause defines how to retrieve a subset of rows from the underlying table (object stored on Cloud Object Storage).
L_COL1 L_COL2 R_COL1 R_COL2 

 0 10 0 10 
 2 12 2 12 
 4 14 4 14 







 Outer join 

An OUTER join includes the rows that are produced by the inner join, plus the missing rows, depending on the type of outer join.

A LEFT OUTER or LEFT join includes the rows from the left table that were missing from the inner join.

-- left outer join query
SELECT
left_table.col1 AS l_col1,
left_table.col2 AS l_col2,
right_table.col1 AS r_col1,
right_table.col2 AS r_col2
FROM VALUES (0, 10), (1, 11), (2, 12), (3,13), (4, 14), (5, 14) AS left_table
LEFT OUTER JOIN
VALUES (0, 10), (2, 12), (4, 14), (6, 16) AS right_table
ON left_table.col1 = right_table.col1

The result of the example query is shown in the following table.



Table 19. Query result for example: left outer join query.

 L_COL1 L_COL2 R_COL1 R_COL2 

 0 10 0 10 
 1 11 null null 
 2 12 2 12 
 3 13 null null 
 4 14 4 14 
 5 14 null null 



A RIGHT OUTER or RIGHT join includes the rows from the right table that were missing from the inner join.

-- right outer join query
SELECT
left_table.col1 AS l_col1,
left_table.col2 AS l_col2,
right_table.col1 AS r_col1,
right_table.col2 AS r_col2
FROM
VALUES (0, 10), (1, 11), (2, 12), (3,13), (4, 14), (5, 14) AS left_table
RIGHT OUTER JOIN
VALUES (0, 10), (2, 12), (4, 14), (6, 16) AS right_table
* [30 October 2020](https://cloud.ibm.com/docs/codeengine?topic=codeengine-codeengine-relnotescodeengine-oct3020)



* Review the release notes for 30 October 2020.
* CLI version 0.4.2493 released.
* Lithops



* [23 October 2020](https://cloud.ibm.com/docs/codeengine?topic=codeengine-codeengine-relnotescodeengine-oct2320)



* Review the release notes for 23 October 2020.
* CLI version 0.4.2439 released.
* Project selected for current context
* Updated runtimes for buildpacks.



* [19 October 2020](https://cloud.ibm.com/docs/codeengine?topic=codeengine-codeengine-relnotescodeengine-oct1920)



* Review the release notes for 19 October 2020.
* Troubleshooting build information



* [15 October 2020](https://cloud.ibm.com/docs/codeengine?topic=codeengine-codeengine-relnotescodeengine-oct1520)



* Review the release notes for 15 October 2020.
* CLI version 0.4.2397 released.



* [14 October 2020](https://cloud.ibm.com/docs/codeengine?topic=codeengine-codeengine-relnotescodeengine-oct1420)



* Review the release notes for 14 October 2020.
* New troubleshooting information.



* [6 October 2020](https://cloud.ibm.com/docs/codeengine?topic=codeengine-codeengine-relnotescodeengine-oct0620)



* Review the release notes for 6 October 2020.
* CLI version 0.4.2365 released.



* [5 October 2020](https://cloud.ibm.com/docs/codeengine?topic=codeengine-codeengine-relnotescodeengine-oct0520)
: Updated troubleshooting build resolution information for [Ephemeral storage limit is reached](https://cloud.ibm.com/docs/codeengine?topic=codeengine-ts-build-ephemeral-limit) and [Memory limit is reached](https://cloud.ibm.com/docs/codeengine?topic=codeengine-ts-build-memory-limit) to use build update command.





 15 October 2020 

Review the release notes for 15 October 2020.

CLI version 0.4.2397 released.
: See [CLI version history](https://cloud.ibm.com/docs/codeengine?topic=codeengine-cli_versions).





 14 October 2020 

Review the release notes for 14 October 2020.

New troubleshooting information.
: See [Troubleshooting jobs](https://cloud.ibm.com/docs/codeengine?topic=codeengine-troubleshoot-job) and [Troubleshooting builds](https://cloud.ibm.com/docs/codeengine?topic=codeengine-troubleshoot-build).





 6 October 2020 

Review the release notes for 6 October 2020.

CLI version 0.4.2365 released.
: See [CLI version history](https://cloud.ibm.com/docs/codeengine?topic=codeengine-cli_versions).





 5 October 2020 

Review the release notes for 5 October 2020.

CLI version 0.4.2335 released.
: See [CLI version history](https://cloud.ibm.com/docs/codeengine?topic=codeengine-cli_versions).







 September 2020 

Review the release notes for September 2020.



 28 September 2020 

Review the release notes for 28 September 2020.

CLI version 0.4.2276 released.
: See [CLI version history](https://cloud.ibm.com/docs/codeengine?topic=codeengine-cli_versions).





 24 September 2020 

Review the release notes for 24 September 2020.

New tutorial
rook-ceph-mgr-a-55cc8d96cc-vm5dr 1/1 Running 0 4m55s
rook-ceph-mon-a-5dcc4d9446-4ff5x 1/1 Running 0 5m38s
rook-ceph-mon-b-64dc44f954-w24gs 1/1 Running 0 5m30s
rook-ceph-mon-c-86d4fb86-s8gdz 1/1 Running 0 5m15s
rook-ceph-operator-69c46db9d4-tqdpt 1/1 Running 0 9m42s
rook-ceph-osd-0-6c6cc87d58-79m5z 1/1 Running 0 4m42s
rook-ceph-osd-1-f4cc9c864-fmwgd 1/1 Running 0 4m41s
rook-ceph-osd-2-dd4968b75-lzc6x 1/1 Running 0 4m40s
rook-ceph-osd-prepare-ocs-deviceset-0-data-0-29jgc-kzpgr 0/1 Completed 0 4m51s
rook-ceph-osd-prepare-ocs-deviceset-1-data-0-ckvv2-4jdx5 0/1 Completed 0 4m50s
rook-ceph-osd-prepare-ocs-deviceset-2-data-0-szmjd-49dd4 0/1 Completed 0 4m50s
rook-ceph-rgw-ocs-storagecluster-cephobjectstore-a-7f7f6df9rv6h 1/1 Running 0 3m44s
rook-ceph-rgw-ocs-storagecluster-cephobjectstore-b-554fd9dz6dm8 1/1 Running 0 3m41s









 Step 6: Next Steps
* Updates the UBI to version 8.8-860.







 Revision 18, released 21 April 2023 



* Resolves the following CVEs: [CVE-2023-0361](https://nvd.nist.gov/vuln/detail/CVE-2023-0361)
* Updates the UBI to version 8.7-1107.
* Ignore aggregate usage limit if set to 0%







 Revision 17, released 4 April 2023 



* 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)
* Updates the UBI to version 8.7-1085.1679482090.







 Revision 16, 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 15, released 6 March 2023
RA-5 (6) - Automated Trend Analyses 



  Control requirements 

RA-5 (6) - 0
:   The organization employs automated mechanisms to compare the results of vulnerability scans over time to determine trends in information system vulnerabilities.
5 0 0 2 5:5:2:0 yes
6 0 0 3 6:6:3:0 yes
7 0 0 3 7:7:3:0 yes

The preceding example output shows that each core has 2 CPUs and both CPUs are online. Core 0 has siblings: CPU 0 and CPU 1. To get the sibling list, you can find the data in thread_sibling_list in the devices file system as shown in the following example:

cat /sys/devices/system/cpu/cpu/topology/thread_siblings_list

0-1
0-1
2-3
2-3
4-5
4-5
6-7
6-7

Some kernels and CPU architectures use a comma ( , ) instead of a hyphen (-) in the thread sibling list.

You can disable Hyper-Threading Technology for a single core by writing a zero ( 0 )into the online field in the device file system for the corresponding CPU. For example, to disable Hyper-Threading Technology on core 2 (CPU 5 in the previous example), run the following command:

echo 0 > /sys/devices/system/cpu/cpu5/online

This command flips CPU 5 off-line, disabling Hyper-Threading Technology on core 2 but keeps the other cores in Hyper-Threading Technology mode as shown in the following example when you run the lscpu --extended command:

CPU NODE SOCKET CORE L1d:L1i:L2:L3 ONLINE
0 0 0 0 0:0:0:0 yes
1 0 0 0 1:1:0:0 yes
2 0 0 1 2:2:1:0 yes
3 0 0 1 3:3:1:0 yes
4 0 0 2 4:4:2:0 yes
5 - - - ::: no
6 0 0 3 6:6:3:0 yes
7 0 0 3 7:7:3:0 yes

You can repeat the previous process for each core to disable Hyper-Threading Technology for the VM. When the VM has a lot of CPUs, this can be difficult.
sector: 512 [bytes]

Keyslots:
0: luks2
Key: 512 bits
Priority: normal
Cipher: aes-xts-plain64
Cipher key: 512 bits
PBKDF: argon2i
Time cost: 4
Memory: 737817
Threads: 2
Salt: c3 c9 89 88 35 3a fb 32 4e 64 a0 5c 58 33 c0 92
af c1 0c 98 78 d8 eb a0 b5 ea 67 4b 00 86 59 63
AF stripes: 4000
AF hash: sha256
Area offset:32768 [bytes]
Area length:258048 [bytes]
Digest ID: 0
Tokens:
Digests:
0: pbkdf2
Hash: sha256
Iterations: 106736
Salt: a4 57 7d 09 e8 cd 56 e7 ad 4c 14 d8 15 b4 38 88
84 63 a8 7d 2a e8 2d d8 46 b6 87 2f 87 fa a9 e0
Digest: 09 aa 56 8f 14 dd c7 76 9a 51 5e 74 b9 1b 95 8a
14 a2 93 59 18 b3 70 df 54 53 c0 85 2c 3b 79 fd
[root@classic-byok-poc02 ]







 File Storage file-level encryption 

File Storage doesn't support LUKS or similar volume-level encryption. Encryption must be done on a file level. Tools built upon FUSE can achieve this, like EncFS or gocryptfs. On the IBM Cloud RHEL8 image gocryptfs is not available, but on Ubuntu 20.04 it is. You can install gocryptfs by using apt.

Mount a File Storage (here it is mounted on /mnt/filestor):

root@classic-byok-poc01:/mnt cat /etc/fstab
LABEL=cloudimg-rootfs	/	 ext4	defaults,relatime	0 1
af c1 0c 98 78 d8 eb a0 b5 ea 67 4b 00 86 59 63
AF stripes: 4000
AF hash: sha256
Area offset:32768 [bytes]
Area length:258048 [bytes]
Digest ID: 0
Tokens:
Digests:
0: pbkdf2
Hash: sha256
Iterations: 106736
Salt: a4 57 7d 09 e8 cd 56 e7 ad 4c 14 d8 15 b4 38 88
84 63 a8 7d 2a e8 2d d8 46 b6 87 2f 87 fa a9 e0
Digest: 09 aa 56 8f 14 dd c7 76 9a 51 5e 74 b9 1b 95 8a
14 a2 93 59 18 b3 70 df 54 53 c0 85 2c 3b 79 fd





 Adding a new key 

See the following example for adding a key.

[root@classic-byok-poc02 ] cryptsetup luksAddKey /dev/sda
Enter any existing passphrase:
Enter new passphrase for key slot:
Verify passphrase:
[root@classic-byok-poc02 ] cryptsetup luksDump /dev/sda
LUKS header information
Version: 	2
Epoch: 	4
Metadata area: 	16384 [bytes]
Keyslots area: 	16744448 [bytes]
UUID: 	6e515660-7db7-41df-9b48-47d1489c7711
Label: 	(no label)
Subsystem: 	(no subsystem)
Flags: 	(no flags)

Data segments:
0: crypt
offset: 16777216 [bytes]
length: (whole device)
cipher: aes-xts-plain64
sector: 512 [bytes]

Keyslots:
0: luks2
Key: 512 bits
Priority: normal
Cipher: aes-xts-plain64
Cipher key: 512 bits
* The AdoptOpenJDK OpenJ9 alternate JRE is updated to version 11.0.10_9_openj9-0.24.0.
* The IBM JRE Version (8 SR 6 FP20) remains unchanged.







 15 January 2021 

Updated Liberty buildpack v3.53-20210114-1605
: The alternate Liberty runtime GA version is changed to the 21.0.0.1 release.



* The default Liberty runtime GA version is the 20.0.0.12 release.
* The AdoptOpenJDK OpenJ9 alternate JRE (11.0.9_11_openj9-0.23.0) and IBM JRE Version (8 SR 6 FP20) remains unchanged.







 17 December 2020 

Updated Liberty buildpack v3.52-20201210-1626
: The default and alternate Liberty runtime GA version is the [20.0.0.12](https://openliberty.io/blog/2020/11/20/JNDI-gRPC-200012.html) release.



* The IBM JRE version is updated to 8 SR6 FP20.
* The IBM JRE 8 SR6 FP20 includes the following Oracle and IBM fixes: [CVE-2020-14792, CVE-2020-14797, CVE-2020-14781, CVE-2020-14779, CVE-2020-14798, CVE-2020-14796](https://www.ibm.com/support/pages/node/6370057)
* The AdoptOpenJDK OpenJ9 alternate JRE (11.0.9_11_openj9-0.23.0) remains unchanged.







 14 December 2020 

Updated the ASP.NET Core buildpack v2.9-20201207-2154
: This release includes version 2.3.19 of the dotnet-core Cloud Foundry buildpack.



* Add support for .NET ASP.NET Core 5.0.0
* Add support for .NET ASP.NET Core 3.1.10
* Add support for .NET ASP.NET Core 3.1.9
"external": 193164408719,
"active": 34961621142
},
"purge_seq": 0,
"other": {
"data_size": 193164408719
},
"doc_del_count": 5564,
"doc_count": 9818541,
"disk_size": 46114703224,
"disk_format_version": 6,
"compact_running": true,
"instance_start_time": "0",
"partitioned_indexes": {
"count": 7,
"indexes": {
"search": 1,
"view": 6
},
"limit": 10
}
}
Show more
* [Version 22.04](https://cloud.ibm.com/docs/satellite?topic=satellite-cl-netapp-ontap-san22.04-change-log)



* [Revision 19, released 19 June 2023](https://cloud.ibm.com/docs/satellite?topic=satellite-cl-netapp-ontap-sannetapp-ontap-san-22.04-rev-19-change-log)
* [Revision 18, released 21 April 2023](https://cloud.ibm.com/docs/satellite?topic=satellite-cl-netapp-ontap-sannetapp-ontap-san-22.04-rev-18-change-log)
* [Revision 17, released 4 April 2023](https://cloud.ibm.com/docs/satellite?topic=satellite-cl-netapp-ontap-sannetapp-ontap-san-22.04-rev-17-change-log)
* [Revision 16, released 21 March 2023](https://cloud.ibm.com/docs/satellite?topic=satellite-cl-netapp-ontap-sannetapp-ontap-san-22.04-rev-16-change-log)
* [Revision 15, released 6 March 2023](https://cloud.ibm.com/docs/satellite?topic=satellite-cl-netapp-ontap-sannetapp-ontap-san-22.04-rev-15-change-log)
* [Revision 14, released 20 February 2023](https://cloud.ibm.com/docs/satellite?topic=satellite-cl-netapp-ontap-sannetapp-ontap-san-22.04-rev-14-change-log)



* [Version 21.04](https://cloud.ibm.com/docs/satellite?topic=satellite-cl-netapp-ontap-san21.04-change-log)
WHERE emp.col2 BETWEEN 4000 AND 8000

The result of the example query is shown in the following table.



Table 38. Query result for example: all employees with a salary in the range 4000 - 8000.

 EMP_ID SALARY 

 4 4000 
 5 5000 
 6 6000 
 8 8000 



-- all employees with a salary not between 4000 and 8000
SELECT
emp.col1 AS emp_id,
emp.col2 AS salary
FROM VALUES
(0, 1000),
(2, 2000),
(3, 3000),
(4, 4000),
(5, 5000),
(6, 6000),
(7, null),
(8, 8000),
(9,9000) AS emp
WHERE emp.col2 NOT BETWEEN 4000 AND 8000

The result of the example query is shown in the following table.



Table 39. Query result for the example all

 EMP_ID SALARY 

 0 1000 
 2 2000 
 3 3000 
 9 9000 







 IN examples 

-- all employees working in department D01 or D02
SELECT
emp.col1 AS emp_id,
emp.col2 AS emp_dept
FROM VALUES
(0, 'D01'),
(2, 'C01'),
(3, 'C02'),
(4, 'D01'),
(5, 'D02'),
(6, 'C01'),
(7, 'D01'),
(8, 'C03'),
(9,'D01') AS emp
WHERE emp.col2 IN ('D01','D02')

The result of the example query is shown in the following table.



Table 40. Query result for the example all

 EMP_ID EMP_DEPT 

 0 D01 
 4 D01 
 5 D02 
 7 D01 
 9 D01
PE-3 (6) - Facility Penetration Testing 



  Control requirements 

PE-3 (6) - 0
:   The organization employs a penetration testing process that includes [Assignment: organization-defined frequency], unannounced attempts to bypass or circumvent security controls associated with physical access points to the facility.





  Additional IBM Cloud for Financial Services specifications 



*  This control is required for ISVs.
5 ge-0/0/3 
 6 ge-0/0/4 
 7 ge-0/0/5 
 8 ge-0/0/6 



The following table shows information for a pair of vSRX VMs in a cluster (node 0 and node 1).



Table 2. Interface names and mappings for a pair of vSRX VMs in a cluster (node 0 and node 1)

 Network adapter Interface name in Junos OS 

 1 fxp0 (node 0 and 1) 
 2 em0 (node 0 and 1) 
 3 ge-0/0/0 (node 0) and ge-7/0/0 (node 1) 
 4 ge-0/0/1 (node 0) and ge-7/0/1 (node 1) 
 5 ge-0/0/2 (node 0) and ge-7/0/2 (node 1) 
 6 ge-0/0/3 (node 0) and ge-7/0/3 (node 1) 
 7 ge-0/0/4 (node 0) and ge-7/0/4 (node 1) 
 8 ge-0/0/5 (node 0) and ge-7/0/5 (node 1) 







 Default security zone configuration 

The following table shows the factory default settings for security policies.



Table 3. Factory default settings for security policies

 Source zone Destination zone Policy action 

 trust untrust permit 
 trust trust permit 
 untrust trust deny 



As noted previously, the default configuration merely represents a point from which to build the required configuration to meet your requirements. The creation of extra security zones is often necessary to support the various traffic flow patterns present in the account.









 vSRX to client on-premises connections 

The preferred method of linking the IBM Cloud vCenter Server instance to a client's existing on-premises data center is BGP.

If the client intends to connect over the Internet by using eBGP, they must obtain a public autonomous system number (ASN) or use BGP over an IPsec VPN to allow the use of private ASNs.

If the client is using Direct Link, BGP by using private ASNs is possible.

Zoom

!