vania-janet/multiturn-rag-retrieval-data huggingface dataset:
satdemo-cp1 0bc3b92f55968a230985 assigned Ready zone-1 infrastructure sat-satdemocp1-2bda578e901b4047c6e48d766cd99bc11a45fddd 169.62.42.178
satdemo-cp2 999cd38c39ddffe4b672 assigned Ready zone-2 infrastructure sat-satdemocp2-940134e69c2609c5421b2426a7640fa80569668d 169.62.42.183
satdemo-cp5 6ca4fd8fcad1fa622aa4 assigned Ready zone-3 infrastructure sat-satdemocp5-d46581b509357ea4b429fddc38a18b155463bf1c 169.62.42.181
satdemo-cp4 1ac2b92f55968a333335 assigned Ready zone-1 satdemo-cluster sat-satdemocp4-2bda578e901b4047c6e48d766cd99bc11a45fddd 169.62.42.180
satdemo-cp6 234cd56c78ddffe4b672 assigned Ready zone-2 satdemo-cluster sat-satdemocp6-940134e69c2609c5421b2426a7640fa80569668d 169.62.42.179
satdemo-cp3 8fg4ff8faaa1fa622bb5 assigned Ready zone-3 satdemo-cluster sat-satdemocp3-d46581b509357ea4b429fddc38a18b155463bf1c 169.62.42.182
2. List your current hosts that are assigned as worker nodes to your Satellite-enabled IBM Cloud service and make note of their IDs.

ibmcloud ks worker ls -c <cluster_name_or_ID>

Review the example output.

ID Primary IP Flavor State Status Zone Version
: Optional: Do not show the message of the day or update reminders.



 Example worker add command 

ibmcloud ks worker add --cluster my_cluster --workers 3 --public-vlan my_public_VLAN_ID --private-vlan my_private_VLAN_ID --flavor b3c.4x16 --hardware shared







 ibmcloud ks worker get 

Virtual Private Cloud

Classic infrastructure

View the details of a worker node.

ibmcloud ks worker get --cluster CLUSTER_NAME_OR_ID --worker WORKER_NODE_ID [--output json] [-q]

Minimum required permissions
: Viewer platform access role for the cluster in IBM Cloud Kubernetes Service

Command options:

-c, --cluster CLUSTER_NAME_OR_ID
: Optional: The name or ID of the worker node's cluster.

--worker WORKER_NODE_ID
: Required: The name of your worker node. Run ibmcloud ks worker ls --cluster CLUSTER to view the IDs for the worker nodes in a cluster.

--output json
: Optional: Prints the command output in JSON format.

-q
: Optional: Do not show the message of the day or update reminders.



 Example worker get command 

ibmcloud ks worker get --cluster my_cluster --worker kube-dal10-cr18a61a63a6a94b658596aa93d087aaa9-w1







 ibmcloud ks worker ls 

Virtual Private Cloud

Classic infrastructure

List all worker nodes in a cluster.

ibmcloud ks worker ls --cluster CLUSTER [--worker-pool POOL] [--show-pools] [--show-deleted] [--output json] [-q]

Minimum required permissions
: Viewer platform access role for the cluster in IBM Cloud Kubernetes Service

Command options:

-c, --cluster CLUSTER
: Required: The name or ID of the cluster for the available worker nodes.

-p, --worker-pool POOL
You can list available zones by running ibmcloud oc zone ls --provider vpc-gen2.

ibmcloud oc cluster get --cluster <cluster_name_or_ID>

Example output

...
VPC ID: <VPC_ID>
...
Worker Zones: us-south-1, us-south-2, us-south-3
2. For each zone, note the ID of VPC subnet that you want to use for the worker pool. If you don't have a VPC subnet in the zone, [create a VPC subnet](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-vpc-resources-with-cli-and-api&interface=clicreate-a-subnet-cli). VPC subnets provide IP addresses for your worker nodes and load balancer services in the cluster, so [create a VPC subnet with enough IP addresses](https://cloud.ibm.com/docs/openshift?topic=openshift-vpc-subnetsvpc_basics_subnets), such as 256.

ibmcloud oc subnets --zone <ZONE> --provider vpc-gen2 --vpc-id <VPC_ID>
3. For each zone, review the [available flavors for worker nodes](https://cloud.ibm.com/docs/openshift?topic=openshift-planning_worker_nodesvm).

ibmcloud oc flavors --zone <ZONE> --provider vpc-gen2
4. Optional: To encrypt the local disk of each worker node in the worker pool, get the details of your key management service (KMS) provider. If you want to use a KMS instance from a different account, you need to do these steps under the account where the KMS instance resides.



1.
: For more information, see the change logs: [4.8](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_48), [4.9](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_49), [4.10](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_410), [4.11](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_411), and [4.12](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_412).

Worker node fix packs 4.8.57_1597_openshift, 4.9.57_1584_openshift, 4.10.54_1562_openshift, 4.11.32_1549_openshift, and 4.12.8_1535_openshift.
: For more information, see the change logs: [4.8](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_48), [4.9](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_49), [4.10](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_410), [4.11](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_411), and [4.12](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_412).





 21 March 2023 

New troubleshooting steps for workers in Critical or NotReady state.
To attach hosts as worker nodes to the control plane,



1. From the Satellite [Locations dashboard](https://cloud.ibm.com/satellite/locations), select the location where you want to finish the setup of your control plane.
2. From the Hosts tab, select the hosts to assign as worker nodes to your control plane. All hosts must be in an Unassigned status.
3. From the actions menu of each host, click Assign host.
4. Select Control plane as your cluster.
5. Assign hosts in groups of 3 evenly to the control plane cluster. For high availability, make sure that your hosts correspond to physically separate zones in your infrastructure provider. For example, if your infrastructure provider has us-east-1a, us-east-1b, and us-east-1c, enter these names for your Satellite zones. Then, assign 2 hosts from us-east-1a in your infrastructure provider to us-east-1a in your Satellite control plane, and so on. When you assign the hosts to the control plane, IBM bootstraps your machine. This process might take a few minutes to complete. During the bootstrapping process, the Health of your machine changes from Ready to Provisioning.
6. From the Hosts tab, verify that your hosts are successfully assigned to the Satellite location control plane. The assignment is successful when an IP address is added to your host and the Health status changes to Normal.
7. Verify that your location status changed to Normal. You might see a location message about the location not having enough hosts until the bootstrapping process completes.

After your hosts are successfully assigned to the control plane, it takes another 20-30 minutes until IBM monitoring is properly set up for your location. In addition, a DNS record is created for your location and the IP addresses of your hosts are automatically registered and added to your DNS record to allow load balancing and health checking for your location. This process can take up to 30 minutes to complete. During this process, your location status continues to show an action required state, and you might see intermittent errors, such as Satellite is attempting to recover or Verify that the Satellite location has a DNS record for load balancing requests to the location control plane.
* Worker zones: User defined subnet in each zone of the region
* Worker nodes per zone: 1
* Flavor: mx2.4x32 - 4 vCPU, 32 GB Memory



2. After provisioning completes, [access the Red Hat OpenShift on IBM Cloud cluster](https://cloud.ibm.com/docs/openshift?topic=openshift-access_clustervpc_private_se).
3. Taint the worker pool. By providing a taint on the worker pool, it ensures that only the logging stack runs on the worker pool. For more information on taints and tolerations, see the [Red Hat OpenShift on IBM Cloud documentation](https://docs.openshift.com/container-platform/4.6/nodes/scheduling/nodes-scheduler-taints-tolerations.htmlnodes-scheduler-taints-tolerations-about_nodes-scheduler-taints-tolerations). A taint can be set on a worker pool with the following ibmcloud CLI command:

ibmcloud oc worker-pool taint set --worker-pool <WORKER_POOL> --cluster <CLUSTER> --taint KEY=VALUE:EFFECT

An example taint setting of logging-monitoring=node:NoExecute, can be set by using the following ibmcloud cli command:

ibmcloud oc worker-pool taint set --worker-pool <WORKER_POOL> --cluster <CLUSTER> --taint logging-monitoring=node:NoExecute







 Step 3: Install the Elasticsearch Operator 

The Elasticsearch Operator creates and manages the Elasticsearch cluster that is used by Red Hat OpenShift on IBM Cloud cluster logging. It can be installed from the Red Hat OpenShift on IBM Cloud console.



1. Install the [Elasticsearch Operator](https://docs.openshift.com/container-platform/4.6/logging/cluster-logging-deploying.htmlcluster-logging-deploy-console_cluster-logging-deploying).
2. Ensure that the following settings are selected or configured:
kube-dal12-crb20b637238ea471f8d4a8b881aae4962-w10 169.xx.xxx.xxx 10.xxx.xx.xxx b3c.4x16 normal Ready dal12 1.26







 Adding worker nodes in VPC clusters 

Add worker nodes to your VPC cluster.



 Creating a new worker pool 

You can add worker nodes to your VPC cluster by creating a new worker pool.

Want to create a new worker pool on dedicated hosts? See [Setting up dedicated hosts in the CLI](https://cloud.ibm.com/docs/openshift?topic=openshift-dedicated-hostssetup-dedicated-host-cli).

Before you begin, make sure that you have the [Operator or Administrator IBM Cloud IAM platform access role](https://cloud.ibm.com/docs/openshift?topic=openshift-users).



1. Retrieve the VPC ID and Worker Zones of your cluster and choose the zone where you want to deploy the worker nodes in your worker pool. You can choose any of the existing Worker Zones of your cluster, or add one of the [multizone locations](https://cloud.ibm.com/docs/openshift?topic=openshift-regions-and-zoneszones-vpc) for the region that your cluster is in. You can list available zones by running ibmcloud oc zone ls --provider vpc-gen2.

ibmcloud oc cluster get --cluster <cluster_name_or_ID>

Example output

...
VPC ID: <VPC_ID>
...
Worker Zones: us-south-1, us-south-2, us-south-3
2. For each zone, note the ID of VPC subnet that you want to use for the worker pool.
1 root root 10 Feb 9 04:15 scsi-3600605b00d87b43027b3bbb603150cc6-part2 -> ../../sda2
lrwxrwxrwx. 1 root root 10 Feb 9 04:15 scsi-3600605b00d87b43027b3bbb603150cc6-part3 -> ../../sda3
lrwxrwxrwx. 1 root root 9 Feb 9 04:15 scsi-3600605b00d87b43027b3bbf306bc28a7 -> ../../sdb
lrwxrwxrwx. 1 root root 10 Feb 9 04:15 scsi-3600605b00d87b43027b3bbf306bc28a7-part1 -> ../../sdb1
lrwxrwxrwx. 1 root root 9 Feb 9 04:17 scsi-3600605b00d87b43027b3bc310a64c6c9 -> ../../sdc
lrwxrwxrwx. 1 root root 10 Feb 11 03:14 scsi-3600605b00d87b43027b3bc310a64c6c9-part1 -> ../../sdc1
lrwxrwxrwx. 1 root root 10 Feb 11 03:15 scsi-3600605b00d87b43027b3bc310a64c6c9-part2 -> ../../sdc2
7. Repeat the previous steps for each worker node that you want to use for your ODF configuration.



Before you begin, review the [parameter reference](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-odf-localodf-local-parameter-reference) for the template version that you want to use.
, 166.9.16.185, 166.9.16.38, 166.9.16.39, 166.9.16.5, 166.9.17.2, 166.9.17.35, 166.9.17.37, 166.9.17.39, 166.9.48.124, 166.9.48.171, 166.9.48.175, 166.9.48.240, 166.9.48.35, 166.9.48.50, 166.9.48.76, 166.9.51.104, 166.9.51.106, 166.9.51.16, 166.9.51.54, 166.9.51.74, 166.9.58.104, 166.9.58.11, 166.9.58.16, 166.9.58.170, 166.9.58.210, 166.9.58.64, 166.9.58.65, 166.9.59.125, 166.9.59.147, 166.9.61.15, 166.9.61.54, 166.9.85.114, 166.9.88.186, 166.9.88.196, 166.9.88.21, 166.9.228.8, 166.9.229.10, 166.9.230.9 







 Open ports 

Open the following ports in your allowlist for your worker nodes to function properly. The following ports need should be open all destination IPs.



* Allow outbound TCP and UDP connections from the workers to ports 80 and 443 to allow worker node updates and reloads.
* Allow outbound TCP and UDP to port 2049 to allow mounting file storage as volumes.
* Allow outbound TCP and UDP to port 3260 for communication to block storage.
* Allow inbound TCP and UDP connections to port 10250 for the Red Hat OpenShift dashboard and commands such as oc logs and oc exec.
* Allow inbound and outbound connections to TCP and UDP port 53 and port 5353 for DNS access.







 Enable worker-to-worker communication
, 166.9.16.185, 166.9.16.38, 166.9.16.39, 166.9.16.5, 166.9.17.2, 166.9.17.35, 166.9.17.37, 166.9.17.39, 166.9.48.124, 166.9.48.171, 166.9.48.175, 166.9.48.240, 166.9.48.35, 166.9.48.50, 166.9.48.76, 166.9.51.104, 166.9.51.106, 166.9.51.16, 166.9.51.54, 166.9.51.74, 166.9.58.104, 166.9.58.11, 166.9.58.16, 166.9.58.170, 166.9.58.210, 166.9.58.64, 166.9.58.65, 166.9.59.125, 166.9.59.147, 166.9.61.15, 166.9.61.54, 166.9.85.114, 166.9.88.186, 166.9.88.196, 166.9.88.21, 166.9.228.8, 166.9.229.10, 166.9.230.9 







 Open ports 

Open the following ports in your allowlist for your worker nodes to function properly. The following ports need should be open all destination IPs.



* Allow outbound TCP and UDP connections from the workers to ports 80 and 443 to allow worker node updates and reloads.
* Allow outbound TCP and UDP to port 2049 to allow mounting file storage as volumes.
* Allow outbound TCP and UDP to port 3260 for communication to block storage.
* Allow inbound TCP and UDP connections to port 10250 for the Kubernetes dashboard and commands such as kubectl logs and kubectl exec.
* Allow inbound and outbound connections to TCP and UDP port 53 for DNS access.







 Enable worker-to-worker communication
For more information, see [Worker node resource reserves](https://cloud.ibm.com/docs/openshift?topic=openshift-planning_worker_nodesresource_limit_node). 
 RHEL 7 Packages 3.10.0-1160.2.2.el7 3.10.0-1160.6.1.el7 Updated worker node image with kernel and package updates for [CVE-2020-8622](https://nvd.nist.gov/vuln/detail/CVE-2020-8622), [CVE-2020-8623](https://nvd.nist.gov/vuln/detail/CVE-2020-8623), [CVE-2020-8624](https://nvd.nist.gov/vuln/detail/CVE-2020-8624), [CVE-2019-20907](https://nvd.nist.gov/vuln/detail/CVE-2019-20907), [CVE-2020-15999](https://nvd.nist.gov/vuln/detail/CVE-2020-15999), [CVE-2020-8177](https://nvd.nist.gov/vuln/detail/CVE-2020-8177), [CVE-2019-20811](https://nvd.nist.gov/vuln/detail/CVE-2019-20811), [CVE-2020-14331](https://nvd.nist.gov/vuln/detail/CVE-2020-14331), [CVE-2020-8695](https://nvd.nist.gov/vuln/detail/CVE-2020-8695), [CVE-2020-8696](https://nvd.nist.gov/vuln/detail/CVE-2020-8696), and [CVE-2020-8698](https://nvd.nist.gov/vuln/detail/CVE-2020-8698).
You can list available zones by running ibmcloud ks zone ls --provider vpc-gen2.

ibmcloud ks cluster get --cluster <cluster_name_or_ID>

Example output

...
VPC ID: <VPC_ID>
...
Worker Zones: us-south-1, us-south-2, us-south-3
2. For each zone, note the ID of VPC subnet that you want to use for the worker pool. If you don't have a VPC subnet in the zone, [create a VPC subnet](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-vpc-resources-with-cli-and-api&interface=clicreate-a-subnet-cli). VPC subnets provide IP addresses for your worker nodes and load balancer services in the cluster, so [create a VPC subnet with enough IP addresses](https://cloud.ibm.com/docs/containers?topic=containers-vpc-subnetsvpc_basics_subnets), such as 256.

ibmcloud ks subnets --zone <ZONE> --provider vpc-gen2 --vpc-id <VPC_ID>
3. For each zone, review the [available flavors for worker nodes](https://cloud.ibm.com/docs/containers?topic=containers-planning_worker_nodesvm).

ibmcloud ks flavors --zone <ZONE> --provider vpc-gen2
4. Optional: To encrypt the local disk of each worker node in the worker pool, get the details of your key management service (KMS) provider. If you want to use a KMS instance from a different account, you need to do these steps under the account where the KMS instance resides.



1. Complete the steps in [VPC worker nodes](https://cloud.ibm.com/docs/containers?topic=containers-encryptionworker-encryption-vpc) to create your KMS instance and to authorize your service in IAM.
2.
NAME ID State Created Workers Zone Version Resource Group Name Provider
mycluster blrs3b1d0p0p2f7haq0g normal 20170201162433 3 dal10 1.26.6_1526 Default classic

Is your cluster not in a normal state? Check out the [Debugging clusters](https://cloud.ibm.com/docs/containers?topic=containers-debug_clusters) guide for help. For example, if your cluster is provisioned in an account that is protected by a firewall gateway appliance, you must [configure your firewall settings to allow outgoing traffic to the appropriate ports and IP addresses](https://cloud.ibm.com/docs/containers?topic=containers-firewallfirewall_outbound).
9. Check the status of the worker nodes.

ibmcloud ks worker ls --cluster <cluster_name_or_ID>

When the worker nodes are ready, the worker node state changes to normal and the status changes to Ready. When the node status is Ready, you can then access the cluster. Note that even if the cluster is ready, some parts of the cluster that are used by other services, such as Ingress secrets or registry image pull secrets, might still be in process. Note that if you created your cluster with a private VLAN only, no Public IP addresses are assigned to your worker nodes.

ID Public IP Private IP Flavor State Status Zone Version
kube-blrs3b1d0p0p2f7haq0g-mycluster-default-000001f7 169.xx.xxx.xxx 10.xxx.xx.xxx u3c.2x4.encrypted normal Ready dal10 1.26.6_1526

Every worker node is assigned a unique worker node ID and domain name that must not be changed manually after the cluster is created. If you change the ID or domain name, the Kubernetes master cannot manage your cluster.
10.
kube-dal12-crb20b637238ea471f8d4a8b881aae4962-w10 169.xx.xxx.xxx 10.xxx.xx.xxx b3c.4x16 normal Ready dal12 1.26







 Adding worker nodes in VPC clusters 

Add worker nodes to your VPC cluster.



 Creating a new worker pool 

You can add worker nodes to your VPC cluster by creating a new worker pool.

Want to create a new worker pool on dedicated hosts? See [Setting up dedicated hosts in the CLI](https://cloud.ibm.com/docs/containers?topic=containers-dedicated-hostssetup-dedicated-host-cli).

Before you begin, make sure that you have the [Operator or Administrator IBM Cloud IAM platform access role](https://cloud.ibm.com/docs/openshift?topic=openshift-users).



1. Retrieve the VPC ID and Worker Zones of your cluster and choose the zone where you want to deploy the worker nodes in your worker pool. You can choose any of the existing Worker Zones of your cluster, or add one of the [multizone locations](https://cloud.ibm.com/docs/containers?topic=containers-regions-and-zoneszones-vpc) for the region that your cluster is in. You can list available zones by running ibmcloud ks zone ls --provider vpc-gen2.

ibmcloud ks cluster get --cluster <cluster_name_or_ID>

Example output

...
VPC ID: <VPC_ID>
...
Worker Zones: us-south-1, us-south-2, us-south-3
2. For each zone, note the ID of VPC subnet that you want to use for the worker pool.
When you add a zone to a worker pool, the worker nodes that are defined in your worker pool are provisioned in the new zone and considered for future workload scheduling. Red Hat OpenShift on IBM Cloud automatically adds the failure-domain.beta.kubernetes.io/region label for the region and the failure-domain.beta.kubernetes.io/zone label for the zone to each worker node. The Kubernetes scheduler uses these labels to spread pods across zones within the same region.

If you have multiple worker pools in your cluster, add the zone to all them so that worker nodes are spread evenly across your cluster. Note that when you add worker nodes to your cluster, the new worker nodes run the same major.minor version as the cluster master, but the latest worker node patch of that major.minor version.

Before you begin: Make sure that you have the [Operator or Administrator IBM Cloud IAM platform access role](https://cloud.ibm.com/docs/openshift?topic=openshift-users).



1. Get the Location of your cluster, and note the existing Worker Zones and VPC ID.

ibmcloud oc cluster get --cluster <cluster_name_or_ID>

Example output

...
VPC ID: <VPC_ID>
Workers: 3
Worker Zones: us-south-1
...
Location: Dallas
2. List available zones for your cluster's location to see what other zones you can add.

ibmcloud oc zone ls --provider vpc-gen2 | grep <location>
3. List available VPC subnets for each zone that you want to add. If you don't have a VPC subnet in the zone, [create a VPC subnet](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-vpc-resources-with-cli-and-api&interface=clicreate-a-subnet-cli).
Instead, you can [create a worker pool](https://cloud.ibm.com/docs/openshift?topic=openshift-add_workersadd_pool), [resize an existing worker pool](https://cloud.ibm.com/docs/openshift?topic=openshift-add_workersresize_pool), or [add a zone to a worker pool](https://cloud.ibm.com/docs/openshift?topic=openshift-add_workersadd_zone) to add worker nodes to your cluster.



1. List available zones and pick the zone where you want to add worker nodes.

ibmcloud oc zone ls
2. List available VLANs in that zone and note their ID.

ibmcloud oc vlan ls --zone <zone>
3. List available flavors in that zone.

ibmcloud oc flavors --zone <zone>
4. Add stand-alone worker nodes to the cluster. For bare metal flavors, specify dedicated.

ibmcloud oc worker add --cluster <cluster_name_or_ID> --workers <number_of_worker_nodes> --public-vlan <public_VLAN_ID> --private-vlan <private_VLAN_ID> --flavor <flavor> --hardware <shared_or_dedicated>
5. Verify that the worker nodes are created.

ibmcloud oc worker ls --cluster <cluster_name_or_ID>







 Installing SGX drivers and platform software on SGX-capable worker nodes 

Intel Software Guard Extensions (SGX) is a technology that can protect data-in-use through hardware-based server security. With Intel SGX, you can protect select code and data from disclosure or modification. Through the use of trusted execution environments (TEE), known as enclaves, you can encrypt the pieces of your app memory that contain sensitive data while the data or code is being used. To use Intel SGX, you must install the SGX drivers and platform software on SGX-capable worker nodes.
To see the zone names for your location, run ibmcloud sat location get --location and look for the Host Zones field. 



* The following example assigns a host by using the os=RHCOS host label.

ibmcloud sat host assign --location <location_name_or_ID> --cluster <cluster_name_or_ID> --host-label os=RHCOS --zone <zone>



3. Repeat the previous step for all compute hosts that you want to assign as worker nodes to your Satellite resource.
4. Wait a few minutes until the bootstrapping process for all computes hosts is complete and your hosts are successfully assigned to your Satellite resource. All hosts are assigned a cluster, a worker node ID, and an IP address.

You can monitor the bootstrapping process of your compute hosts by running ibmcloud ks worker get --cluster <cluster_name_or_ID> --worker <worker_ID>.

ibmcloud sat host ls --location <location_name_or_ID>

Example output

Retrieving hosts...
OK
Name ID State Status Cluster Worker ID Worker IP
satcluster brkijjq20r3nd89b1sog assigned Ready satcluster sat-satc-dd629ca11947c4aaec1a0208e0a37ca790475ee0 169.62.196.24
satcluster2 brkiku2202thnmhb1sp0 assigned Ready satcluster sat-satc-69f2410d3ecfea9127aeec07f01475f241728a16 169.62.196.22
satcluster3 brkiltb20m0oqr29mo2g assigned Ready satcluster sat-satc-9985014f499827ddde3ce3e5bedad26af5a73263 169.62.196.29