Comprobación de la configuración del host

Después de crear hosts que cumplan requisitos del sistema, requisitos de red y requisitos de conectividad salientes, puede verificar la configuración del host ejecutando el siguiente script sat-host-check.

Actualmente hay un error con el script sat-host-check que hace que falle en RHEL debido a un requisito GLIBC.

Inicie una sesión en el host.

ssh root@<IP_address>

Para hosts RHEL, SSH como root.

    ssh root@<IP_address>
    ```
1. Para los hosts RHCOS, copie la clave SSH pública en el script de encendido e inicie sesión como núcleo.
    1. Descargue el script de conexión de host y añada la clave SSH pública.

        ```json {: codeblock}
        {
          "ignition": {
            "version": "3.1.0"
          },
          "passwd": {
            "users": [
              {
                "name": "core",
                "sshAuthorizedKeys": [ "PUBLIC-SSH-KEY" ]
              }
            ]
          },
        ...
        }
        ```
    1. Inicie sesión en el host como `core`.
        ```sh {: pre}
        ssh core@<IP_address>
        ```

Descargue el script y haga que sea ejecutable.

curl https://<region>.containers.cloud.ibm.com/satellite-health/sat-host-check -o sat-host-check && chmod +x sat-host-check

Mandato de ejemplo para us-south.

curl https://us-south.containers.cloud.ibm.com/satellite-health/sat-host-check -o sat-host-check && chmod +x sat-host-check

Ejecute el script y especifique la región donde ha creado la ubicación.

sudo ./sat-host-check --region $REGION

Mandato de ejemplo para us-south.

sudo ./sat-host-check --region us-south

{: pre}

Salida de ejemplo para comprobar un host en us-south.

===========================
  TEST PHASE: redhatOS
===========================
PASS:  custom Grub configuration (/boot/grub/grub.conf) not present
PASS:  custom Network configuration (/sbin/ifup-local) not present
PASS:  custom Network configuration (/sbin/ifdown-pre-local) not present
PASS:  custom Network configuration (/sbin/ifdown-local) not present
PASS:  custom NTP configuration (/etc/ntp.conf) not present
=== subscription-manager  ===
STDOUT:
Usage: subscription-manager MODULE-NAME [MODULE-OPTIONS] [--help]
PASS:  subscription-manager configured
=== yum info rh-python36 ===
...
===========================
  TEST PHASE: network
===========================
=== ip addr ===
...
FAIL:  wrong number of network interfaces (expected 2, found: 3: [1: lo, 2: eth0, 3: eth1])
=== ip route ===
...
info:  no checks performed on 'ip route' output
=== Check connectivity to google.com:80 ===
PASS:  got response back from google.com:80
=== Check connectivity to our region us-south ===
=== Check connectivity to hosted control plane ===
=== Check connectivity to 169.63.123.154:30000 ===
PASS:  got response back from 169.63.123.154:30000
=== Check connectivity to 169.60.123.162:30000 ===
PASS:  got response back from 169.60.123.162:30000
=== Check connectivity to 52.117.93.26:30000 ===
PASS:  got response back from 52.117.93.26:30000
=== Check connectivity to 52.117.88.42:30000 ===
PASS:  got response back from 52.117.88.42:30000
=== Check connectivity to 169.47.174.106:30000 ===
PASS:  got response back from 169.47.174.106:30000
=== Check connectivity to 169.60.92.50:30000 ===
PASS:  got response back from 169.60.92.50:30000
=== Check connectivity to 169.61.74.210:30000 ===
PASS:  got response back from 169.61.74.210:30000
=== Check connectivity to 169.62.9.250:30000 ===
PASS:  got response back from 169.62.9.250:30000
=== Check connectivity to 169.62.10.162:30000 ===
PASS:  got response back from 169.62.10.162:30000
=== Check 443 ports ===
=== Check connectivity to 169.60.73.142:443 ===
PASS:  got response back from 169.60.73.142:443
=== Check connectivity to 169.60.101.42:443 ===
PASS:  got response back from 169.60.101.42:443
=== Check connectivity to 169.61.83.62:443 ===
PASS:  got response back from 169.61.83.62:443
=== Check connectivity to 169.61.109.34:443 ===
PASS:  got response back from 169.61.109.34:443
=== Check connectivity to 169.62.10.162:443 ===
FAIL:  Could not create request: dial tcp 169.62.10.162:443: connect: connection refused
=== Check connectivity to 169.63.75.82:443 ===
FAIL:  Could not create request: dial tcp 169.63.75.82:443: connect: connection refused
=== Check connectivity to 169.63.88.178:443 ===
PASS:  got response back from 169.63.88.178:443
=== Check connectivity to 169.63.88.186:443 ===
PASS:  got response back from 169.63.88.186:443
=== Check connectivity to 169.63.94.210:443 ===
FAIL:  Could not create request: dial tcp 169.63.94.210:443: connect: connection refused
=== Check connectivity to 169.63.111.82:443 ===
FAIL:  Could not create request: dial tcp 169.63.111.82:443: connect: connection refused
=== Check connectivity to 169.63.149.122:443 ===
FAIL:  Could not create request: dial tcp 169.63.149.122:443: connect: connection refused
=== Check connectivity to 169.63.158.82:443 ===
FAIL:  Could not create request: dial tcp 169.63.158.82:443: connect: connection refused
=== Check connectivity to 169.63.160.130:443 ===
FAIL:  Could not create request: dial tcp 169.63.160.130:443: connect: connection refused
=== Check connectivity to link control plane ===
=== Test Failure Summary: ===
redhatOS - error checking RHN configuration with `subscription-manager`: exit status 1
network - wrong number of network interfaces (expected 2, found: 3: [1: lo, 2: eth0, 3: eth1])
network - Could not create request: dial tcp 169.62.10.162:443: connect: connection refused
network - Could not create request: dial tcp 169.63.75.82:443: connect: connection refused
network - Could not create request: dial tcp 169.63.94.210:443: connect: connection refused
network - Could not create request: dial tcp 169.63.111.82:443: connect: connection refused
network - Could not create request: dial tcp 169.63.149.122:443: connect: connection refused
network - Could not create request: dial tcp 169.63.158.82:443: connect: connection refused
network - Could not create request: dial tcp 169.63.160.130:443: connect: connection refused
cleaned up temp dir: `/tmp/sathostcheck-3139302841`

Revise el resumen de anomalías de prueba. En función de la anomalía, revise los requisitos y actualice los hosts.
- Requisitos del sistema host
- Requisitos de almacenamiento de host
- Requisitos de red de host
- Requisitos de conectividad de salida host y los requisitos de conectividad de salida específicos de la región para la región en la que ha creado la ubicación.
Si la comprobación del host es satisfactoria, puede continuar conectando el host a la ubicación.