호스트 설정 확인

시스템 요구사항, 네트워크 요구사항 및 아웃바운드 연결 요구사항을 충족하는 호스트를 작성한 후에는 sat-host-check 스크립트를 실행하여 호스트 설정을 확인할 수 있습니다.

현재 sat-host-check 스크립트에는 GLIBC 요구 사항으로 인해 RHEL에서 실패하는 버그가 있습니다.

호스트에 로그인하십시오.

ssh root@<IP_address>

RHEL 호스트의 경우에는 SSH를 사용하여 root로서 접속하십시오.

    ssh root@<IP_address>
    ```
1. RHCOS 호스트의 경우에는 공용 SSH 키를 Ignition 스크립트에 복사하고 core로서 로그인하십시오.
    1. 호스트 연결 스크립트를 다운로드하고 공용 SSH 키를 추가하십시오.

        ```json {: codeblock}
        {
          "ignition": {
            "version": "3.1.0"
          },
          "passwd": {
            "users": [
              {
                "name": "core",
                "sshAuthorizedKeys": [ "PUBLIC-SSH-KEY" ]
              }
            ]
          },
        ...
        }
        ```
    1. `core`(으)로서 호스트에 로그인하십시오.
        ```sh {: pre}
        ssh core@<IP_address>
        ```

스크립트를 다운로드하여 실행 가능하게 하십시오.

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

us-south에 대한 명령 예입니다.

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

스크립트를 실행하고 자신의 위치를 작성한 지역을 지정하십시오.

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

us-south에 대한 명령 예입니다.

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

{: pre}

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`

테스트 실패 요약을 검토하십시오. 실패에 따라 요구사항을 검토하고 호스트를 업데이트하십시오.
- 호스트 시스템 요구사항
- 호스트 스토리지 요구사항
- 호스트 네트워크 요구사항
- 호스트 아웃바운드 연결 요구사항, 그리고 자신의 위치를 작성한 지역의 지역 고유 아웃바운드 연결 요구사항입니다.
호스트 확인이 성공하는 경우에는 자신의 위치에 호스트를 연결하는 작업을 계속할 수 있습니다.