验证分析子系统的安装

验证分析子系统的部署并配置计划备份。

开始之前

完成部署分析子系统 OVA。

过程

登录API Connect使用 SSH 登录 VM，并检查安装状态：

如果使用 three replica 部署配置文件，则对分析子系统部署中的每个虚拟机重复此步骤。

输入以下命令通过 SSH 连接到您的分析虚拟机：
```
ssh apicadm@<vm hostname>
```
不需要密码，因为您在准备部署分析子系统的9步骤中设置了公钥。如有必要，请包含您的 SSH 身份文件的路径：
```
ssh -i <path to identity file> apicadm@<vm hostname>
```
例如：
```
ssh -i ~/.ssh/id_rsa apicadm@<vm hostname>
```
选择是以继续连接。
您的主机名会自动添加到主机列表中。

运行 apic status 命令，验证安装是否完成，系统运行是否正常。

正确运行的分析系统的命令输出类似于以下内容:

#sudo apic status
INFO[0000] Log level: info                              

Cluster members:
- apimsvc22.hursley.ibm.com (9.20.85.207)
  Version: 5.2.0
  Type: BOOTSTRAP_MASTER
  Install stage: DONE
  Upgrade stage: UPGRADE_DONE
  Spec Version: 10.0.8.0
  Reconciled Version: 10.0.8.0-258
  CR Status: Running
  CR Message: 
  CR Condition Message: 7/7
  CR Condition Reason: DeploymentReady
  Subsystem type: analytics
  Subsystem version: 10.0.8.0
  Subsystem detail: Waiting for installation before starting upgrade manager
  NTP Status: systemd-timesyncd.service[active] (NTP: Initial synchronization to time server 9.20.0.16:123 (ntp.hursley.ibm.com).)
  CPU/Memory: 569m/11461Mi  
  Reboot Required: false
  Containerd status:
    Systemd unit: running
  Kubernetes status: 
    Systemd unit: running
    Kubelet version: apimsvc22 (5.4.0-182-generic) [Kubelet v1.28.9, Proxy v1.28.9]
  Etcd status: pod etcd-apimsvc22 in namespace kube-system has status Running
  Addons: calico, cert-manager-v1, dns, kube-proxy, local-volume-provisioner, metrics-server, 
  Disk Space Available: 224G/245G | Used: 5%
  Inodes Available: 16M/16M | Used: 1%
  Containers: 21
    - Running: 21
    - Exited: 29
    - Unknown: 0
  Images: 31
Etcd cluster state:
- etcd member name: apimsvc22.hursley.ibm.com, member id: 9262458466544818989, cluster id: 16589681311468597424, leader id: 9262458466544818989, revision: 4560907, version: 3.5.9

Pods Summary:
NODE             NAMESPACE          NAME                                            READY        STATUS           REASON
apimsvc22        certmanager        cert-manager-8694fb5f7d-5lj2s                   1/1          Running          
apimsvc22        certmanager        cert-manager-cainjector-5cdfc79679-x67df        1/1          Running          
apimsvc22        certmanager        cert-manager-webhook-66f85f764f-gdh7c           1/1          Running          
apimsvc22        default            abc-analytics-director-7dd456cd48-s452r         1/1          Running          
apimsvc22        default            abc-analytics-ingestion-0                       1/1          Running          
apimsvc22        default            abc-analytics-mtls-gw-5fbb9455f9-cd8jm          1/1          Running          
apimsvc22        default            abc-analytics-oscron-28704480-5xbvk             0/1          Succeeded        
apimsvc22        default            abc-analytics-osinit-wmx6n                      0/1          Succeeded        
apimsvc22        default            abc-analytics-reindex-28703520-7vcj5            0/1          Succeeded        
apimsvc22        default            abc-analytics-storage-0                         1/1          Running          
apimsvc22        default            ibm-apiconnect-c486c557d-tc2hs                  1/1          Running          
apimsvc22        kube-system        calico-kube-controllers-7fbcfc6b49-hjhpn        1/1          Running          
apimsvc22        kube-system        calico-node-nzdnx                               1/1          Running          
apimsvc22        kube-system        coredns-b647d6884-9l2vr                         1/1          Running          
apimsvc22        kube-system        coredns-b647d6884-f7jhk                         1/1          Running          
apimsvc22        kube-system        etcd-apimsvc22                                  1/1          Running          
apimsvc22        kube-system        ingress-nginx-ingress-controller-f5lvb          1/1          Running          
apimsvc22        kube-system        kube-apiserver-apimsvc22                        1/1          Running          
apimsvc22        kube-system        kube-apiserver-proxy-apimsvc22                  1/1          Running          
apimsvc22        kube-system        kube-controller-manager-apimsvc22               1/1          Running          
apimsvc22        kube-system        kube-proxy-pq5kt                                1/1          Running          
apimsvc22        kube-system        kube-scheduler-apimsvc22                        1/1          Running          
apimsvc22        kube-system        local-volume-provisioner-lhjdr                  1/1          Running          
apimsvc22        kube-system        metrics-server-967bc8b5c-2dmcj                  1/1          Running

如果您已安装所有 API Connect 子系统，请继续安装部署后步骤子系统。
配置子系统的备份。请按照备份和恢复分析子系统中的说明进行操作。