Verifying deployment of the Analytics subsystem

Verify that deployment of the Analytics OVA file succeeded.

Before you begin

You must have completed Deploying the Analytics subsystem OVA file.

About this task

After you configure an ISO and deploy it with the Analytics subsystem OVA, as described in Deploying the Analytics subsystem OVA file, verify that the subsystem installed correctly and is functional.

Procedure

  1. Log in to the virtual machine by using an SSH tool to check the status of the installation:
    1. Enter the following command to connect to analyt using SSH:
      ssh ip_address -l apicadm
      You are logging in with the default ID of apicadm, which is the API Connect ID that has administrator privileges.
    2. Select Yes to continue connecting.
      Your host names are automatically added to your list of hosts.
    3. Run the apic status command to verify that the installation completed and the system is running correctly.
      The command output for a correctly running Analytics system is similar to the following lines:
      #sudo apic status
      INFO[0000] Log level: info
      
      Cluster members:
      - testsrv0233.subnet1.example.com (1.2.152.233)
        Type: BOOTSTRAP_MASTER
        Install stage: DONE
        Upgrade stage: UPGRADE_DONE
        Docker status:
          Systemd unit: running
        Kubernetes status:
          Systemd unit: running
          Kubelet version: testsrv0233 (4.4.0-138-generic) [Kubelet v1.10.6, Proxy v1.10.6]
        Etcd status: pod etcd-testsrv0233 in namespace kube-system has status Running
        Addons: calico, dns, helm, kube-proxy, metrics-server, nginx-ingress,
      Etcd cluster state:
      - etcd member name: testsrv0233.subnet1.example.com, member id: 12836860275847862867, cluster id: 14018872452420182423, 
              leader id: 12836860275847862867, revision: 365042, version: 3.1.17
      
      Pods Summary:
      NODE               NAMESPACE          NAME                                                                READY        STATUS           REASON
                         default            apic-analytics-analytics-client-76956644b9-cmgx8                    0/0          Pending
      testsrv0233        default            apic-analytics-analytics-client-76956644b9-vlqp2                    1/1          Running
      testsrv0233        default            apic-analytics-analytics-cronjobs-retention-1541381400-hp9fc        0/1          Succeeded
      testsrv0233        default            apic-analytics-analytics-cronjobs-rollover-1541445300-c5n6z         0/1          Succeeded
                         default            apic-analytics-analytics-ingestion-547f875467-8mhsl                 0/0          Pending
      testsrv0233        default            apic-analytics-analytics-ingestion-547f875467-s7flj                 1/1          Running
                         default            apic-analytics-analytics-mtls-gw-85b8676855-jmh8c                   0/0          Pending
      testsrv0233        default            apic-analytics-analytics-mtls-gw-85b8676855-sw6ps                   1/1          Running
      testsrv0233        default            apic-analytics-analytics-storage-basic-8cckh                        1/1          Running
      testsrv0233        kube-system        calico-node-8crtp                                                   2/2          Running
      testsrv0233        kube-system        coredns-87cb95869-6flvn                                             1/1          Running
      testsrv0233        kube-system        coredns-87cb95869-rccvb                                             1/1          Running
      testsrv0233        kube-system        etcd-testsrv0233                                                    1/1          Running
      testsrv0233        kube-system        ingress-nginx-ingress-controller-f7b9z                              1/1          Running
      testsrv0233        kube-system        ingress-nginx-ingress-default-backend-6f58fb5f56-nklmv              1/1          Running
      testsrv0233        kube-system        kube-apiserver-testsrv0233                                          1/1          Running
      testsrv0233        kube-system        kube-apiserver-proxy-testsrv0233                                    1/1          Running
      testsrv0233        kube-system        kube-controller-manager-testsrv0233                                 1/1          Running
      testsrv0233        kube-system        kube-proxy-2vw9b                                                    1/1          Running
      testsrv0233        kube-system        kube-scheduler-testsrv0233                                          1/1          Running
      testsrv0233        kube-system        metrics-server-5558db4678-9drz6                                     1/1          Running
      testsrv0233        kube-system        tiller-deploy-84f4c8bb78-vx65c                                      1/1          Running
  2. For a list of the Kubernetes pods started by the deployment, see the Results section in Deploying the Analytics subsystem.
  3. If you have now installed all subsystems, continue to Post-deployment steps.