vania-janet/multiturn-rag-retrieval-data huggingface dataset:
[Available](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/vmwaresolutions/includes/icons/checkmark-icon.svg) ![Available](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/vmwaresolutions/includes/icons/checkmark-icon.svg) ![Available](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/vmwaresolutions/includes/icons/checkmark-icon.svg) 
 VCD Extension: Register, Unregister, Refresh, Associate or Disassociate ![Available](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/vmwaresolutions/includes/icons/checkmark-icon.svg) ![Available](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/vmwaresolutions/includes/icons/checkmark-icon.svg) 
 VCD Extension: View ![Available](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/vmwaresolutions/includes/icons/checkmark-icon.svg) !
Retrieve and transfer the certificate 

Retrieve the SSL certificate you ordered earlier so that you're ready for its installation and configuration in the step-by-step [Configuring and Tuning SSL Offload with Citrix Netscaler VPX](https://cloud.ibm.com/docs/citrix-netscaler-vpx?topic=citrix-netscaler-vpx-configuring-and-tuning-ssl-offload-with-citrix-netscaler-vpx).



1.  Shortly after validating ownership of the domain, you should receive an email confirming the completion of the certificate fulfillment and the certificate itself.

Copy the text from ---BEGIN CERTIFICATE--- all the way to ---END CERTIFICATE--- and save the contents as a new certificate file with an extension of .cer.
2.  Copy the certificate file to the /nsconfig/ssl directoy in the Citrix Netscaler VPX.



The Citrix Netscaler VPX is now ready to incorporate the certificate into a load balancing deployment using SSL.
Profile tier-3iops
Size(GB) 40
IOPS 3000
Encryption provider_managed
Mount Targets ID Name VPC ID VPC Name
3c413e2f-2e7e-47e9-a9ad-12d23068d2c4 my-target121 0d37163a-701d-4ad6-9ece-a3e34cf28935 cdl
585075b5-b466-4b98-b733-2c5c2d906823 my-target122 dd1c6831-cc4d-4c40-aab2-6b0c17f41424 cli-vpc-1

Resource Group ID Name
bdd96715c2a44f2bb60df4ff14a543f5 Default

Created 2023-07-05T15:21:35+05:30





 View a source file share for a replica file share from the CLI 

Run the ibmcloud is share-replica-source command and specify the replica share by ID or name.

ibmcloud is share-replica-source REPLICA-SHARE [--output JSON] [-q, --quiet]

See the following example.

ibmcloud is share-replica-source replica-share-4
Getting source file share for replica file share replica-share-4 under account VPC as user myuser@mycompany.com...

ID 0e8ee997-bf1d-4165-9573-726c3a4d3b36
Name share-4
CRN crn:v1:staging:public:is:us-south-1:a/efe5afc483594adaa8325e2b4d1290df::share:0e8ee997-bf1d-4165-9573-726c3a4d3b36
Lifecycle state stable
Zone us-south-1
Profile tier-5iops
Size(GB) 40
IOPS 3000
Encryption provider_managed
curl -X PATCH "$vpc_api_endpoint/v1/shares/$share_id/mount_targets/$target_id?version=2023-07-11&generation=2&maturity=beta" -H "Authorization: Bearer ${API_TOKEN}" -d '{
"name": "target-renamed1"
}

A successful response looks like the following example.

{
"access_control_mode": "vpc",
"created_at": "2023-05-30T23:31:59Z",
"href": "$vpc_api_endpoint/v1/shares/0995b8c6-c323-4e59-9ea9-fa14dd66bba8/mount_targets/9fdf4438-f5b4-4b6f-8bca-602494fd6c31",
"id": "9fdf4438-f5b4-4b6f-8bca-602494fd6c31",
"lifecycle_state": "stable",
"mount_path": "domain.com:/vol_xyz_2891fd0a_64ea_4deb_9ed5_1159e37cb5aa",
"name": "target-renamed1",
"resource_type": "share_target",
"transit_encryption": "none",
"vpc": {
"crn": "crn:[...]",
"href": "$vpc_api_endpoint/v1/vpcs8c95b3c1-fe3c-45c-97a6-e43d14088287",
"id": "82a7b841-9586-43b4-85dc-c0ab5e8b1c7a",
"name": "vpc-name1",
"resource_type": "vpc"
}
}
* [Support Policies for RHEL High Availability Clusters](https://access.redhat.com/articles/2912891)
* [Support Policies for RHEL High Availability Clusters - General Requirements for Fencing/STONITH](https://access.redhat.com/articles/2881341)
* [Support Policies for RHEL High Availability Clusters - IBM Power Systems Virtual Server (PowerVS) Virtual Machines as Cluster Members](https://access.redhat.com/articles/5651561)
* [Red Hat Enterprise Linux 8 - Configuring and managing the Red Hat High Availability Add-On](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/configuring_and_managing_high_availability_clusters/index)
* [Configuring a RHEL HA Cluster Fence Agent for an IBM Power Systems Virtual Server](https://access.redhat.com/articles/6966644)







 Creating virtual server instances for the cluster 

Use the instructions in [Creating instances for a high availability cluster on IBM® Power® Systems Virtual Server](https://cloud.ibm.com/docs/sap?topic=sap-ha-vsi) to create the virtual server instances that you want to use as cluster nodes.





 Gathering parameters for the cluster configuration 

Parameters that are required for fencing agent configuration include the Cloud Resource Name (CRN) of the Power Systems Virtual Server workspace and the instance IDs of the virtual server instances. Some extra parameters need to be derived from the CRN. The fencing agent also uses the API Key of the Service ID {APIKEY} to authenticate with the Power Systems Virtual Server API.

The uppercase variables in the following section indicate that these parameters need to be set as environment variables on the virtual server instances to simplify the setup of the cluster.



1. Log in to [Workspaces - Power Systems Virtual Server](https://cloud.ibm.com/power/workspaces) and search for your Workspace.
2. The tile for the workspace contains the CRN, click Copy to copy the CRN and paste it to a temporary document.
* [Procedure to order Caveonix RiskForesight licenses](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-caveonix_license_orderingcaveonix_license_ordering-procedure)
* [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)
* [Managing Caveonix RiskForesight](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-managingcaveonix)
* [Ordering services for vCenter Server instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_addingservices)
* [Contacting IBM Support](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-trbl_support)
ibmcloud is vpn-server-update r134-aa88726e-8b34-4f97-992d-027df9c4bb36 --subnet 0716-6ec3e875-abfa-40f4-a7c5-7473f4b2a2e1









 Upgrading to an HA VPN server with the API 

To upgrade to an HA VPN server by using the API, follow these steps:



1. Set up your [API environment](https://cloud.ibm.com/docs/vpc?topic=vpc-set-up-environmentapi-prerequisites-setup) with the correct variables.
2. Find the VPN server that you want to upgrade:

Add | json_pp or | jq after the curl command to get a readable JSON string.

curl -X GET "$vpc_api_endpoint/v1/vpn_servers?version=$api_version&generation=2" -H "Authorization:$iam_token"

Save the ID of the VPN server in a variable so that you can use it later, for example:

VpnServer="r134-cb67562d-626c-488d-8c56-35879e238274"
3. Find the subnets that you want to attach to the VPN server:

curl -X GET "$vpc_api_endpoint/v1/subnets?version=$api_version&generation=2" -H "Authorization:$iam_token"

Save the ID of the subnets in a variable so that you can use it later, for example:

SubnetId1="0716-08b770a6-e5e8-4e59-ad0c-9f517914f5a6"
SubnetId2="0726-aa067949-e947-435f-bdcd-1ec84815513d"
export IBMCLOUD_CRN=<IBMCLOUD_CRN> CRN of workspace
export GUID=<GUID> GUID of workspace
export CLOUD_REGION=<CLOUD_REGION> Region of workspace
export PROXY_IP=<IP_ADDRESS> IP address of proxy server

export NODE1=<HOSTNAME_01> <Hostname of virtual server instance 1
export NODE2=<HOSTNAME_02> <Hostname of virtual server instance 2

export POWERVSI_01=<POWERVSI_01> ID virtual server instance 1
export POWERVSI_02=<POWERVSI_02> ID virtual server instance 2







 Installing and configuring a RHEL HA Add-On cluster 

Use the following steps to set up a two-node cluster for an IBM Power Systems Virtual Server.

The instructions are extracted from Red Hat product documentation and articles:



* [Configuring and managing high availability clusters](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/configuring_and_managing_high_availability_clusters/index)
* [Support Policies for RHEL High Availability Clusters - IBM Power Systems Virtual Server (PowerVS) Virtual Machines as Cluster Member](https://access.redhat.com/articles/5651561)
* [Configuring a RHEL HA Cluster Fence Agent for an IBM Power Systems Virtual Server](https://access.redhat.com/articles/6966644).



Some steps need to be performed on both nodes, some only on NODE1 or on NODE2.



 Installing RHEL HA Add-On software 

Install the required software packages.



 Checking the RHEL HA repository 

Check that the RHEL High Availability repository is enabled.

On both nodes, use the followings command.

dnf repolist

If the HA repository is missing, use the following commands to enable it:

subscription-manager repos --enable="rhel-8-for-ppc64le-highavailability-e4s-rpms"

dnf clean all

dnf repolist
ibmcloud is instance-create my-vsi-4 my-vpc-2 us-south-1 bx2-2x8 cli-subnet-1 --image ibm-centos-7-9-minimal-amd64-6 --keys my-keys4 --boot-volume '{"name": "boot-vol-4", "volume": {"name": "my-boot-vol-4", "profile": {"name": "general-purpose"},"user_tags": ["env:test4", "env:dev4"]}}' --volume-attach '[{"name": "my-vol-att1", "volume": {"name":"my-vol-4", "profile": {"name": "general-purpose"}, "capacity": 10 ,"user_tags": "env:test4", "env:dev4"]}}]'

Creating instance my-vsi-4 under account vpcdemo1 as user myuser@mycompany.com...

ID efd06503-f514-4ea2-ba6c-2b9c715e6269
Name my-vsi-4
CRN crn:v1:bluemix:public:is:us-south-1:a/7f75c7b025e54bc5635f754b2f888665::instance:efd06503-f514-4ea2-ba6c-2b9c715e6269
Status pending
Availability policy on host failure restart
Startable true
Profile bx2-2x8
Architecture amd64
vCPUs 2
Memory(GiB) 8
Bandwidth(Mbps) 4000
Volume bandwidth(Mbps) 1000
Network bandwidth(Mbps) 3000
Metadata service Enabled
false

Image ID Name
APP zone subnet & CIDR <DC1 APP zone subnet/CIDR> <DC2 APP zone subnet/CIDR> 





1. Proceed to the Gateway Details page for each VRA via the [Gateway Appliances](https://cloud.ibm.com/classic/network/gatewayappliances) page.
2. Locate the Gateway VLANs section and click on the Gateway [VLAN](https://cloud.ibm.com/classic/network/vlans) on the Private network to view the VLAN details. The name should contain the id, bcrxxx, standing for 'backend customer router' and be of the form nnnxx.bcrxxx.xxxx.
3. The provisioned VRA will be seen under the Devices section. From under the Subnets section, make a note of the VRA private subnet IP address and CIDR (/26). The subnet will be of type primary with 64 IPs. These details are required later for routing configuration.
4. Again on the Gateway Details page, locate the Associated VLANs section and click on the [VLAN](https://cloud.ibm.com/classic/network/vlans) on the Private network that was associated to create the secure network and APP zone.
5. The provisioned VSI will be seen under the Devices section. From under the Subnets section, make a note of the VSI subnet IP address and CIDR (/26) as these are required for routing configuration. This VLAN and subnet is identified as the APP zone in both VRA firewall configurations and is recorded as the <APP Zone subnet/CIDR>.







 Step 2: Configure VLAN Spanning 

By default servers (and VRAs) on different VLANs and data centers, are unable to communicate with each other over the private network. In these tutorials, within a single data center VRA’s are used to link VLANs and subnets with classic IP routing and firewalls to create a private network for server communication across VLANs.
[Import client certificate and key to BIG-IP](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-vpc-architecture-connectivity-waf-tutorialclient-certs-key).
2. [Configure cipher suites](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-vpc-architecture-connectivity-waf-tutorialf5-waf-ciphers).
3. [Create a client SSL profile](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-vpc-architecture-connectivity-waf-tutorialssl-profiles).







 Step 4: Create a BIG-IP VPN 



1. GO to the Wizards > Device Wizards page.
2. Select Network Access Setup Wizard for Remote Access and click Next.
3. Provide a policy name and caption, for example, vpn_policy and click Next.
4. On the Authentication page, select Use Existing, LDAP for server type and select the LDAP server that you previously created. Provide a user DN, for example, uid=%{session.logon.last.username},ou=Users,dc=example,dc=com, and click Next.
5. Configure the Lease Pool by providing an IP range from the previously allocated subnet for VPN in the VPC subnets. For example, 10.5.10.0/24. Click Next.
6. Keep the compression setting set to No compression. For the Traffic options, ensure that Force all traffic through tunnel is selected. Click Next.
7. Keep the DNS servers set to what is populated by default and click Next.
8. Provide the virtual server IP to be the private IP address of the external interface, for example, 10.5.40.4. Click Next.
9. Review the wizard inputs and click Next.
10. Confirm the summary and click Finished.
Authorization: 'AWS4-HMAC-SHA256 Credential={access-key}/{date}/{region}/s3/aws4_request,SignedHeaders=host;x-amz-date;,Signature={signature}'
x-amz-date: {timestamp}
Host: s3.us.cloud-object-storage.appdomain.cloud

Example response

HTTP/1.1 200 OK
Date: Mon, 19 Mar 2018 17:21:08 GMT
X-Clv-Request-Id: 6544044d-4f88-4bb6-9ee5-bfadf5023249
Server: Cleversafe/3.12.4.20
X-Clv-S3-Version: 2.5
Accept-Ranges: bytes
Content-Type: application/xml
Content-Length: 743

<ListPartsResult xmlns="http://s3.amazonaws.com/doc/2006-03-01/">
<Bucket>farm</Bucket>
<Key>spaceship</Key>
<UploadId>01000162-3f46-6ab8-4b5f-f7060b310f37</UploadId>
<Initiator>
<ID>d6f04d83-6c4f-4a62-a165-696756d63903</ID>
<DisplayName>d6f04d83-6c4f-4a62-a165-696756d63903</DisplayName>
</Initiator>
<Owner>
<ID>d6f04d83-6c4f-4a62-a165-696756d63903</ID>
<DisplayName>d6f04d83-6c4f-4a62-a165-696756d63903</DisplayName>
</Owner>
<StorageClass>STANDARD</StorageClass>
ibmcloud is share-replica-source REPLICA-SHARE [--output JSON] [-q, --quiet]

See the following example.

ibmcloud is share-replica-source replica-share-4
Getting source file share for replica file share replica-share-4 under account VPC as user myuser@mycompany.com...

ID 0e8ee997-bf1d-4165-9573-726c3a4d3b36
Name share-4
CRN crn:v1:staging:public:is:us-south-1:a/efe5afc483594adaa8325e2b4d1290df::share:0e8ee997-bf1d-4165-9573-726c3a4d3b36
Lifecycle state stable
Zone us-south-1
Profile tier-5iops
Size(GB) 40
IOPS 3000
Encryption provider_managed
Mount targets ID Name VPC ID VPC Name
No mounted targets found.

Resource group ID Name
11caaa983d9c4beb82690daab08717e9 Default

Created 2023-05-07T18:13:04+05:30
Last sync at 2023-05-06T05:53:28+05:53
Latest job succeeded
Replication share ID Name Resource type
0bb9c083-2ac5-43d5-962a-757f69d5e6c8 replica-p-share-4 share

Replication role source
Replication status active
Source share ID Name Resource type





 View mount targets for a file share from the CLI 

Run the ibmcloud is share-mount-targets command and specify the file share ID to see all mount targets for a file share.

ibmcloud is share-mount-targets SHARE_ID [--output JSON] [-q, --quiet]





 View mount target details from the CLI
* [VRA Network Address Translation](https://cloud.ibm.com/docs/virtual-router-appliance?topic=virtual-router-appliance-about-the-vranetwork-address-translation-nat-)
* [NAT Masquerade](https://cloud.ibm.com/docs/virtual-router-appliance?topic=virtual-router-appliance-setting-up-nat-rules-on-vyatta-5400one-to-many-nat-rule-masquerade-)
* [Supplemental VRA documentation](https://cloud.ibm.com/docs/virtual-router-appliance?topic=virtual-router-appliance-supplemental-vra-documentationsupplemental-vra-documentation).
Supported operating systems for Hyper-V discovery tool are Windows (2012, 2012 R2, 2016 and 2019) and RHEL 7.x and 8.x.

For more information about the discovery tool, see this [public GitHub repository](https://github.com/IBM-Cloud/vpc-migration-tools/blob/main/v2v-discovery-tool-rmm/HyperV/README.md).





 Step 6: Run the migration 



1. When the source and target host are added in the wave and replication record, click the Sync Options tab in the right top region of the pop-up screen. Then, select the No Transfer option and click Modify. Then, click the play or arrow head icon to start the replication. This does a dry run by checking the connection between the RMM and source or target servers. This dry run does not migrate data. If the operation is successful, then remove the No Transfer option that uses the same process.
2. Whenever you are ready, go ahead and click start replication (the play or arrow head icon on the left top). This starts the actual migration. If you expand the replication record, it displays the actual steps tha are run, summarized with the necessary information.
3. Whether the operation is successful or whether it failed, you can see the job history in the replication record.
4. If there is a failure, you can retrieve the log and review detailed information.







 Step 7: Validate your migration 

Before you decommission the source server, it is imperative to validate the target server. This is not an exhaustive list but see the following list of items to validate after your migration:



* Access the target server
* Check partitions and volumes
* Check applications
* Install any test application in the target server
* Check networking routes
* Application or operating system licenses
* Remove RMM SSH keys







 More resources 



1. [Discovery Tool](https://github.com/IBM-Cloud/vpc-migration-tools/blob/main/v2v-discovery-tool-rmm/HyperV/README.md)
2.
Action Method IAM ACTION AT ACTION 

 Get certificates uploaded for mTLS GET /v1/{crn}/zones/{domain_id}/access/certificates internet-svcs.security.read internet-svcs.access-certificates.read 
 Upload a certificate for mTLS POST /v1/{crn}/zones/{domain_id}/access/certificates internet-svcs.security.manage internet-svcs.access-certificates.create 
 Update a certificate for mTLS PUT /v1/{crn}/zones/{domain_id}/access/certificates/{cert_id} internet-svcs.security.update internet-svcs.access-certificates.update 
 Delete a certificate for mTLS DELETE /v1/{crn}/zones/{domain_id}/access/certificates/{cert_id} internet-svcs.security.manage internet-svcs.access-certificates.delete 
 Get mTLS applications GET /v1/{crn}/zones/{domain_id}/access/apps internet-svcs.security.read internet-svcs.access-apps.read 
 Create a mTLS application POST /v1/{crn}/zones/{domain_id}/access/apps internet-svcs.security.manage internet-svcs.access-apps.create 
 Update a mTLS application PUT /v1/{crn}/zones/{domain_id}/access/apps/{app_id} internet-svcs.security.update internet-svcs.access-apps.update 
 Delete a mTLS application DELETE /v1/{crn}/zones/{domain_id}/access/apps/{app_id} internet-svcs.security.manage internet-svcs.access-apps.delete 
 Get mTLS policies GET /v1/{crn}/zones/{domain_id}/access/apps/{app_id}/policies internet-svcs.security.read internet-svcs.access-policies.read
After ordering the two Netscaler VPX servers in the needed VLAN, and ordering the VIP and SNIP subnets to meet the prerequisites for your HA pair configuration, you can proceed with the following:



1. Open two browser windows and log into the advanced interface on both NetScalers. On the secondary NetScaler, go to System > User Administration > Users and set the root password to the same as the primary NetScaler. Then update the password on file in the IBM Cloud catalog on the device details page to match the password set for the secondary.
2. On the VPX you want to be secondary, click on System > High Availability, then right click the first line and click Edit. Select Stay Secondary on the High Availability Status config drop-down box and click OK.
3. Select Add. Enter the system IP address of the other VPX (this is located in the High Availability tab on the primary), and enter the root login details. Leave the Turn on INC box unchecked. Click OK.

If you receive an error claiming that the IPs are not in the same subnet, it is possible both VPX servers are not in the same VLAN. Otherwise, you should now be able to open the primary server and select the Refresh button to see both servers operating in High Availability.

The new NetScaler management IP for the secondary will be one IP address lower than previously. If you cannot get any access to the secondary VPX, remove the high availability from the command line using:

sh ha node

Then remove what would be the HA node:

rm ha node 1
4. On the primary VPX you should see that the remote VPX is now syncing. Go to the secondary server and check the Network > IPs configuration. You should see the primary server's VIP and other IPs listed as passive.
5. Return to System > High Availability on the secondary server and click Edit. Select ENABLED in the drop-down box and hit OK.
6. Force a failover to test. Refresh the screen and watch the IP addresses become active on the secondary. Failover again and watch them go passive.
Identify the user's name that you want to update access for, select the Actions menu, and click Assign Access.
3. Select Access Policy.
4. From Services, select VMware Solutions.
5. Select All Resources.
6. Select the permission levels that you want to assign.
7. Select Add.
8. Select Assign.
9. Retrieve your API credentials:



1. Select Menu icon ![Menu icon](https://cloud.ibm.com/docs-content/v1/content/e9cda99c64ea1ee68cf0eda257d6a1de69ddbc4e/icons/icon_hamburger.svg) > VMware > Settings.
2. Select Retrieve Credentials.
3. Select Save Credentials.





For more information, see [Managing classic infrastructure access](https://cloud.ibm.com/docs/account?topic=account-mngclassicinfra).





 VPC 

To access and update VPC solution permissions:

You must create the proper Schematics access policies for a user to be able to use the WES-UI or IBM Cloud Schematics to deploy Citrix DaaS on IBM Cloud VPC. See [Managing user access](https://cloud.ibm.com/docs/schematics?topic=schematics-access).



Table 2. Required user permissions to provision VPC

 Service Resource Type Permission 

 VPC Infrastructure Services Virtual Private Cloud <br><br> * Operator to use an existing VPC<br> * Admin or Editor to create new VPCs<br><br><br> 
 Floating IP for VPC <br><br> * Operator to attach Floating IP<br> * Admin or Editor to create a Floating IP<br><br><br> 
 Subnet <br><br> * either Admin or Editor<br><br><br> 
 Block Storage for VPC <br><br> * either Admin or Editor<br><br><br>
In VPX shell CLI, display the CSR text by opening the CSR file previously created in the step [Create keys and generate the Certificate Signing Request (CSR)](https://cloud.ibm.com/docs/citrix-netscaler-vpx?topic=citrix-netscaler-vpx-create-keys-and-generate-the-certificate-signing-request-csr-):

root@IBMADC690867-s6dr cat certreqnss6dr.csr
-----BEGIN NEW CERTIFICATE REQUEST-----
MIIC5jCCAc4CAQAwgaAxCzAJBgNVBAYTMRcwFQYDVQQIEw5Ob3J0aCBDYXJv
bGluYTEPMA0GA1UEBxMGRHVyaGFtMQwwCgYDVQQKEwNJQk0xDDAKBgNVBAsTA0hT
TTEoMCYGA1UEAxMfaHNW50Ny5wcm9qZWN0Z29sZGZpbmNoLm5ldDEhMB8G
CSqGSIb3DQEJARYSanBtb25nZUBjci5pYm0uY29tMIIBIjANBgkqhkiG9w0BAQEF
/pXQN+a55HhWmnyj5gThAprOoN8DeiVN+1HI+PA+g1
r4+8dKA1xz+jPhWDQgQYb3Wnh8VK8Ouids6uFnsoc3KDymbzoWZYctp8PA6uBzJ/
25RGiZquRu9MYJIWkQ46WQ14PoJ8BiYuJa/N6L47+Jr2vaCntmXBU4rFrjctHqq8
Hct9q5OVYXbYLQB+MM3gYyyFBQpZ1sHZD4D6K3AISRGsOE9rrovGjUfO8mLKE6a