vania-janet/multiturn-rag-retrieval-data huggingface dataset:
You can only SSH into the machine if you did not assign the host to a cluster, or if the assignment failed. Otherwise, Satellite disables the ability to log in to the host via SSH for security purposes. You can [remove the host](https://cloud.ibm.com/docs/satellite?topic=satellite-host-remove) and reload the operating system to restore the ability to SSH into the machine.
2. To check TCP connectivity, verify that netcat receives a response from all other hosts on port 10250. If the operation times out, review [Host network requirements](https://cloud.ibm.com/docs/satellite?topic=satellite-reqs-host-network) to unblock the ports on the host in your infrastructure provider.

nc -zv <host_IP> 10250
3. To check ICMP connectivity, verify that a ping is successful to all other hosts. Repeat this step for each IP address of the hosts that are attached to your location. If the ping times out, review [Host network requirements](https://cloud.ibm.com/docs/satellite?topic=satellite-reqs-host-network) to unblock the ports on the host in your infrastructure provider.

ping <host_IP>
4. If the TCP and ICMP connectivity checks do not reveal any issues, reboot all control plane hosts by rebooting one host at a time. Do not reboot control plane hosts concurrently, which can prevent etcd from running on the control plane hosts.







 R0044: DNS issues 

Location message
: R0044: DNS issues have been detected on one or more hosts. Verify that your DNS solution is working as expected. If you still have issues, contact IBM Cloud Support and include your Satellite location ID.

Steps to resolve
: One or more hosts in your locations is unable to resolve DNS queries or a search domain is causing unexpected issues. Verify that your DNS solution is working as expected and that all hosts meet the [network host requirements](https://cloud.ibm.com/docs/satellite?topic=satellite-reqs-host-network).
When deploying new apps, making configuration changes, or simply inspecting the state of your cluster, the project-scope dashboard gives a Developer clear insights.



1. Access the dashboard in the Developer perspective by clicking Observe on the left side menu.
2. You can also dive in a bit deeper by clicking the Events tab. Events are useful for identifying the timeline of events and finding potential error messages. When tracking the state of a new rollout, managing existing assets, or even something simple like exposing a route, the Events view is critical in identifying the timeline of activity. This becomes even more useful when considering that multiple operators may be working against a single cluster.



Almost all actions in Red Hat OpenShift result in an event being fired in this view. As it is updated real-time, it's a great way to track changes to state.







 Step 4: Metrics and dashboards 

In this section explore the monitoring and metrics dashboards included in Red Hat OpenShift.



 Dashboards 

Red Hat OpenShift comes with predefined dashboards to monitor your projects.



1. Get started by switching from the Developer perspective to the Administrator perspective:
2. Navigate to Observe > Dashboards in the left-hand bar.
3. Select Kubernetes / Compute Resources / Namespace (Pods) from the dropdown and Namespace to example-health.
4. Notice the CPU and Memory usage for your application. In production environments, this is helpful for identifying the average amount of CPU or Memory your application uses, especially as it can fluctuate through the day. Auto-scaling is one way to handle fluctuations and will be demonstrated a little later.







 Metrics 

Red Hat OpenShift provides a web interface to run queries and examine the metrics visualized on a plot. This functionality provides an extensive overview of the cluster state and enables you to troubleshoot problems.



1. Navigate to Observe > Metrics.
2. Enter the following expression and click Run queries. You should see the value and the graph associated with the query.

sum(container_cpu_usage_seconds_total{container="patient-health-frontend"})

Zoom

!
In the navigation list of the API Manager, expand the Catalogs section and select the Catalog that you want to work with. The Products tab of the Catalog opens, and all of the Products available in that Catalog are displayed. You can select which states are shown by using the filter check boxes on the right of the screen.
2. Alongside the Product version that you want to work with, click the Manage icon and then click Publish. The Edit visibility and subscribers dialog box is displayed.
3. Specify the following options:



* Visible to: You can choose Public users, Authenticated users, or Custom. If you select Custom, you can use the Type to add... field to search for organizations or communities that you want your Product to be visible to.
* Subscribable by: You can choose Authenticated users, or Custom. If you select Custom, you can use the Type to add... field to search for organizations or communities that you want your Product to be visible to.



4. Click Publish. If approval is required to publish Products in this Catalog, an approval request is sent, and the Product moves to the Pending state; the Product is published when the request is approved. If approval is not required, the Product version is published immediately, and moves to the Published state.



Your Product is in the Published state. Your Product is published to your Catalog and available to your specified organizations or communities. Application developers within the groups you selected can see and use the APIs within the Product. Any application developer requests to use your Product are displayed on the Approvals tab in the containing Catalog, where you can decline or accept the request.







 Publishing a Product to IBM Cloud 

To see your Products in the Explore APIs section of the API Connect Dashboard, complete the following steps.



 Prerequisites 

Before you begin, if you want to publish a REST API implemented with LoopBack, ensure that you have published your app run time, and staged your product with the invoke proxy pointing to the new app.
To select the input revision, the stage follows these conditions:



* If a specific revision is selected, use it.
* If a specific revision is not specified, search previous stages until a stage is found that uses the same input. Find and use the last successfully run revision of that input.
* If a specific revision is not specified and no other stages use the specified source as input, use the latest revision of the input.



You can deploy a previous build. On the stage that contains the build, click View logs and history. On the page that opens, click to expand the run number and then click the build job. Click SEND TO, and select a target.





 Adding services to apps 

You can add services to your apps and manage those services from your IBM Cloud dashboard. For more information about adding services, see [Connecting services to external apps](https://cloud.ibm.com/docs/account?topic=account-externalapp).







 Viewing logs 

You can view the logs for jobs and view stages as they are running on the Stage History page.



1. To view a job's log, click the job. Alternatively, on a stage, click View logs and history.
2. To view the runtime log of a deployed application, click View runtime log.

In addition to job logs, you can view unit test results, generated artifacts, and code changes for any build job.

You can also run, redeploy, cancel, or configure a stage from the Stage History page. Click RUN to run the stage, REDEPLOY to redeploy if it is a deployment job, or CONFIGURE to configure a stage. While a stage is running, you can cancel it by clicking the run number and then clicking CANCEL.





 Downloading logs from a script 

You can download the log file for a pipeline job from a script and save the PIPELINE_LOG_URL that is provided while the pipeline job is running. The following example shows the steps to upload the pipeline job's log file to a different system.



1. Set up a JOB_LOG environment property for your stage.
2.
Example queries for flow logs with IBM Cloud® Data Engine 

The following example queries a maximum of 100 individual flows for the date specified:

SELECT * FROM FLOW_FLAT WHERE CAST(capture_start_time AS date) = DATE("2020-07-24") LIMIT 100

The following query lists all accepted TCP connection for the specified date, extracting the hour that the connection was made:

SELECT hour(capture_start_time) as hour,
network_interface_id,
initiator_ip,
target_port
FROM FLOW_FLAT
WHERE
transport_protocol = 6 AND
action = "accepted" AND
CAST(capture_start_time AS date) = DATE("2020-07-24")
SORT BY hour
LIMIT 100

To see which of your vNICs received the most HTTPS traffic in the last seven days, use this query. It counts the number of packets that are sent and groups them by target_ip, and returns the first 10. You can check which vNIC sent the most traffic by sorting by packets_sent.

The where condition maps to columns that are part of the object names. By restricting columns that are encoded in the object name, the query can be run quickly because you can prune objects before you read their content.

You need to include a similar clause when you query large amounts of flow logs.

SELECT target_ip,
SUM(packets_from_initiator) AS packets_received,
SUM(packets_from_target) AS packets_sent
FROM
FLOW_FLAT
WHERE
target_port = 443 AND
day = day(current_date() - INTERVAL 7 days) AND
month = month(current_date() - INTERVAL 7 days) AND
year = year(current_date() - INTERVAL 7 days)
GROUP BY target_ip
ORDER BY packets_received DESC LIMIT 10

To see which vNIC received the most traffic in the last hour, use this query. This query counts the number of bytes sent, groups them by target_ip, and returns the first 5.

SELECT target_ip,
SUM(bytes_from_initiator) AS bytes
FROM
If no case evaluates to true and the ELSE keyword is present, the result is the value of the ELSE case result expression. If no case evaluates to true and the ELSE keyword is not present, the result is NULL. When a case evaluates to unknown (because of NULLs), the case is not true, and hence is treated the same way as a case that evaluates to false.

When you use the simple when clause, the value of the expression before the first WHEN keyword is tested for equality with the value of the expression that follows the WHEN keyword. Therefore, the data type of the expression before the first WHEN keyword must be comparable to the data types of each expression that follows the WHEN keywords.

A result expression is an expression that follows the THEN or ELSE keywords.





 whenClause 





 Examples - whenClause 

-- simple case expression with no ELSE clause
SELECT
dep.col1 AS dep_id,
CASE dep.col2
WHEN 'A' THEN 'Administration'
WHEN 'B' THEN 'Human Resource'
WHEN 'C' THEN 'Development'
END AS dep_name
FROM VALUES (0, 'A'), (1, 'B'), (2, 'C'), (3, 'D'), (4, 'E') AS dep

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



Table 48. Query result for example: simple case expression with no ELSE clause.

 DEP_ID DEP_NAME 

 0 Administration 
 1 Human Resource 
 2 Development 
 3 null 
 4 null 



-- simple case expression with ELSE clause
SELECT
dep.col1 AS dep_id,
CASE dep.col2
WHEN 'A' THEN 'Administration'
WHEN 'B' THEN 'Human Resource'
WHEN 'C' THEN 'Development'
ELSE 'UNKOWN'
END AS dep_name
FROM VALUES (0, 'A'), (1, 'B'), (2, 'C'), (3, 'D'), (4, 'E') AS dep
A values clause is a component of a fullselect or represents a primary relation. Its syntax is defined by the following syntax diagram.





 valuesClause 

With a values clause, you can define a result set by specifying actual values for each column of a row by using expressions.

Each expression in the list of expressions represents a row of the result set that is defined.

In a single-column result set, each expression represents the value of this column in a row.

In a multi-column result set, each expression represents a list of n expressions that are enclosed by parentheses, where n is the number of columns in the result set.

To join a values clause with other types of result sets, specify an identifier that acts as an alias for the values clause.





 Examples - values clause 

-- single column result set with 3 rows
SELECT * FROM VALUES 1, 2 , 3

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



Table 11. Query result for the example single

 COL1 

 1 
 2 
 3 



-- single column result set with 3 rows specifying parentheses for row expressions
SELECT * FROM VALUES (1), (2) , (3)

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



Table 12. Query result for the example single

 COL1 

 1 
 2 
 3 



--- joining two multi column result sets by using their identifier
SELECT
emp.col1 AS id,
emp.col2 AS name,
mission.col2 AS missions
FROM
VALUES
(1, 'Spock'),
(2,'Kirk') ,
(3, 'McCoy'),
(4,'Scotty') AS emp,
VALUES
(1,3000),
(2,2000),
(3,3000),
(4,4000) AS mission
WHERE emp.col1 = mission.col1
Show more

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



Table 13. Query result for the example joining

 ID NAME MISSIONS 

 1 Spock 3000 
 2 Kirk 2000
To get the list of all subnets in your account, run the following command:

ibmcloud is subnets

Look at the VPC value to determine the subnets that need to be deleted. Save the ID of the subnet in a variable so it can be used later, for example:

subnet="0738-d31ce469-9b0f-44e1-87ce-0fc77d8b0e53"

If the VPC you want to delete has multiple subnets, repeat these steps to delete each subnet.





 Step 2: Delete each subnet in the VPC 



 Delete all VPN gateways in the subnet, if any 

To list all VPN gateways in your account, run the following command:

ibmcloud is vpn-gateways

For each VPN gateway in the subnet you want like to delete, run the following command, where $vpnid is the ID of the VPN gateway.

ibmcloud is vpn-gateway-delete $vpnid

The status of the VPN gateway changes to deleting immediately, but it still appears in a list query result. The deletion of a VPN gateway can take up to 30 minutes. You can request other subnet resources to be deleted in parallel while you wait for the VPN gateway to be deleted. However, the subnet can't be deleted until the VPN gateway and all other resources in the subnet no longer appear in the list query results.





 Delete all load balancers in the subnet, if any 

To list alll Load balancers in your account, run the following command:

ibmcloud is load-balancers

For each load balancer in the subnet you want to delete, run the following command, where $lbid is the ID of the load balancer.

ibmcloud is load-balancer-delete $lbid

The status of the Load Balancer changes to deleting immediately, but it is still shown in a list query result. The deletion of a load balancer can take up to 30 minutes.
For the Local gateway IP, you can select an IP address to be advertised through your Classic Network to the vSRX or Gateway Appliance. Ensure that your vSRX or Gateway Appliance has a route to this IP. For Local or Remote tunnel IP, you can select the IP addresses for the GRE tunnel IP addresses.
6. Your vSRX or Edge Gateway Appliance and Transit Gateway must exchange routes through BGP. TGW can choose a BGP ASN for your NSX-T networks, or you can enter your own ASN when you create the GRE connection in TGW. You must configure your T0 to advertise your preferred NSX-T overlay networks to the Transit Gateway. Ensure that you do not advertise routes that collide with your Classic Private Subnets. Also, ensure that you advertise the networks learned from your NSX-T T0 to the Transit Gateway.
7. [You can add other connections](https://cloud.ibm.com/docs/transit-gateway?topic=transit-gateway-adding-connections) (VPC or other Classic) to the Transit Gateway. Your VPC IP address allocation design must not overlap with the attached Classic network nor with the NSX-T overlay networks.
8. You can [add Direct Link connections to the transit gateway](https://cloud.ibm.com/docs/transit-gateway?topic=transit-gateway-adding-connections) for on-premises Connectivity. Transit Gateway advertises the attached routes of VPC, classic network, and GRE tunnel to the attached Direct Link.







 Considerations 

When you design or deploy this architecture pattern, you must consider the following steps:



* Direct Link can be attached as a connection to the Transit Gateway.
* Transit gateway GRE tunnels support traffic flows:



* From GRE to VPC and from VPC to GRE, and
* From GRE to Direct Link and from Direct Link to GRE.



* Plan your AS numbering before you order the GRE tunnels to Transit Gateway.
* To speed up recovery in failure situations, you can tune BGP keepalive and hold-time values at your end of the GRE tunnel.
Example Query Behavior Example Matches 

 level:error Case-insensitive prefix match Error, error, errors 
 level:=error Case-sensitive prefix match error, errors 
 level:==error Case-insensitive exact term match error, Error 
 level:===error Case-sensitive exact term match error 
 level:[warning,error] Case-insensitive list of prefixes warning, Warning, Warnings, error, ERROR, errors 
 level:===[warning,error] Case-sensitive list of prefixes warning, error 
 level:* Matches if the field exists All lines containing the field level 



For example, if you have two apps (myapp and myapp1), then a service group with an access scope of app:myapp will allow access to data from both apps. If the access scope is app:===myapp, then users in the group will only be able to access data from the myapp app.

If you want to create a group of administrators with access to all data, specify host:* for the Access Scope.





 Editing or deleting service groups 

Complete the following steps to edit or delete a service group:



1. Log in to your IBM Cloud account.

Click [Log in to IBM Cloud](https://cloud.ibm.com/login) to sign in to the IBM Cloud.

After you log in with your user ID and password, the IBM Cloud console opens.
2. Select your account.
3. Click the Menu icon ![Menu icon](https://cloud.ibm.com/docs-content/v1/content/icons/icon_hamburger.svg) > Observability.
4. Select Activity Tracker.
5. For your instance, click Open Dashboard. The UI will be displayed.
6. Click ![Settings](https://cloud.ibm.com/docs-content/v1/content/6f3c07c34058f637b1c86044ca4f9b24214330a7/activity-tracker//images/config.png) > Settings > Organization > Groups.
7.
Why am I able to log in to the SSL VPN, but not able to access any devices? 

SSL VPN is showing connected but no access is present to device.

 What’s happening 

SSL VPN shows connected, however, you cannot ping, rdp, ssh, KVM console or telenet to an internal device IP that belongs to your IBM Cloud infrastructure device.

 Why it’s happening 

Possible causes include, but are not limited, to the following:



1. The SSL VPN subnet is incorrectly selected.
2. The user doesn't have proper permissions to a specific device or subnet.
3. More than 64 subnets exist on the account and the user's SSL subnet is set to 'auto'.
4. User might be connected to another VPN causing some local routing issue.
5. Software was not run by an "administrator" level user and routes were not implemented to the system's routing table.
6. Outbound connections are allowing the connection.
7. Older versions of SSL VPN software are known to cause routing problems on both Windows and Mac.



 How to fix it 

To resolve this issue, follow these steps:



1. Ensure that you are disconnected from all other VPNs before connecting to the SSL VPN.
2. Attempt to ping 10.0.80.11 while logged into the SSL VPN. If the ping is successful, this means that you have access to the internal network, but most likely do not have permission to access your devices.
3. Ensure that your user is given the correct and necessary permissions through the IBM Cloud console to access the device/subnet that you are attempting to access. To do this, an account admin must follow these steps:



* Log in to your [IBM Cloud](https://cloud.ibm.com/) account.
* Select Manage > Access (IAM), then click Users.
* Click the user name, then click the Classic infrastructure tab.
* From the Devices and VPN subnets views, you can provide the user with VPN access to all the needed devices or subnets.
oc get cm iks-ca-configmap -n kube-system -o yaml > iks-ca-configmap.yaml
2. In the data.workerPoolsConfig.json field, check that the correct worker pools are enabled with the minimum and maximum size per worker pool.



* "name": "<worker_pool_name>": The name of your worker pool in the ConfigMap must be exactly the same as the name of the worker pool in your cluster. Multiple worker pools must be comma-separated. To check the name of your cluster worker pools, run ibmcloud oc worker-pool ls -c <cluster_name_or_ID>.
* "minSize": 2: In general, the minSize must be 2 or greater. Remember that theminSize value can't be 0, and you can only have a minSize of 1 if you [disable the public ALBs](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics_alb_configure).
* "maxSize": 3: The maxSize must be equal to or greater than the minSize.
* "enabled": true: Set the value to true to enable autoscaling the worker pool.



data:
workerPoolsConfig.json: 
[{"name": "default", "minSize": 2, "maxSize": 3, "enabled": true }]
3. In the metadata.annotations.workerPoolsConfigStatus field, check for a FAILED CODE error message. Follow any recovery steps that are in the error message. For example, you might get a message similar to the following, where you must have the correct permissions to the resource group that the cluster is in.

annotations:
workerPoolsConfigStatus: '{"1:3:default":"FAILED CODE: 400
...
"description":"Unable
to validate the request with resource group manager."
Select the bucket you are using for archiving.
8. Click the Configuration tab.
9. Copy the Bucket Instance CRN.
10. In the Activity Tracker section make sure the selected service instance is the one you are using. Also make sure Data events is set to read & write.







 Step 2. Define a view to filter the events that report the usage of that service ID 

Complete the following steps to define a view:



1. [Launch the Activity Tracker UI](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-launch). The Views section opens.
2. Select the Everything view.

![Views main page](https://cloud.ibm.com/docs-content/v1/content/6f3c07c34058f637b1c86044ca4f9b24214330a7/activity-tracker/images/archive-view-1.png)
3. In the search bar, enter the following query:

initiator.id:iam-ServiceId-<GUID> action:cloud-object-storage.object.create target.id:<BUCKET-CRN>

Replace <GUID> with the ID value of the service ID that you copied earlier.

Replace <BUCKET-CRN> with the CRN value of the bucket that you found on the bucket configuration page.
4. Save the view. For example, you can name the view Upload AT Frankfurt to indicate archive files into the bucket from an IBM Cloud Activity Tracker instance located in Frankfurt.

The data that is displayed through the view reports write actions of archive files to the archive bucket.







 Step 3. Define an alert to notify the absence of new archive files 

Complete the following steps to define an absence alert that notifies you when archiving is not happening:



1. Select the view name.

!