Verifying the management subsystem installation
Verify that the deployment of the management subsystem VMs was successful, and configure scheduled backups.
Before you begin
Complete the deployment of your management subsystem VMs: Deploying the management subsystem OVA.
Procedure
-
Log in to the API Connect VM by using SSH,
and check the status of the installation:
If you are using a three replica deployment profile, then repeat this step for each management VM in your management subsystem deployment.
-
Enter the following command to connect to your management VM with SSH:
ssh apicadm@<vm hostname>No password is required because you set your public key in step 10 of Preparing the management subsystem for deployment. If necessary, include the path to your SSH identity files:ssh -i <path to identity file> apicadm@<vm hostname>For example:ssh -i ~/.ssh/id_rsa apicadm@<vm hostname> -
Select Yes to continue connecting.
Your hostnames are automatically added to your list of hosts.
-
Run the apic status command to verify that the installation
completed and that the system is running correctly.
sudo apic statusAfter installation completes, it can take several minutes for all servers to start. If you see the error message
Subsystems not running, wait a few minutes, try the command again, and review the output in theStatuscolumn.The status output for a correctly running management system is similar to the following:
apicadm@testsys0181:~$ sudo apic status INFO[0000] Log level: info Cluster members: - apimsvc20.hursley.ibm.com (9.20.85.205) 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: Management is ready CR Condition Message: All services ready CR Condition Reason: na Subsystem type: management 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.21:123 (ntp.hursley.ibm.com).) CPU/Memory: 1680m/5708Mi Reboot Required: false Containerd status: Systemd unit: running Kubernetes status: Systemd unit: running Kubelet version: apimsvc20 (5.4.0-182-generic) [Kubelet v1.28.9, Proxy v1.28.9] Etcd status: pod etcd-apimsvc20 in namespace kube-system has status Running Addons: calico, cert-manager-v1, dns, kube-proxy, local-volume-provisioner, metrics-server, Disk Space Available: 212G/245G | Used: 10% Inodes Available: 16M/16M | Used: 2% Containers: 34 - Running: 34 - Exited: 38 - Unknown: 0 Images: 42 Etcd cluster state: - etcd member name: apimsvc20.hursley.ibm.com, member id: 14082648089812057221, cluster id: 4107881071609959540, leader id: 14082648089812057221, revision: 7518476, version: 3.5.9 Pods Summary: NODE NAMESPACE NAME READY STATUS REASON apimsvc20 certmanager cert-manager-8694fb5f7d-fwg5m 1/1 Running apimsvc20 certmanager cert-manager-cainjector-5cdfc79679-r8xct 1/1 Running apimsvc20 certmanager cert-manager-webhook-66f85f764f-vfhnn 1/1 Running apimsvc20 default abc-management-analytics-proxy-6f884477c5-d58pj 1/1 Running apimsvc20 default abc-management-analytics-push-28704435-vpspm 0/1 Succeeded apimsvc20 default abc-management-analytics-ui-8b6557bd5-jth4g 1/1 Running apimsvc20 default abc-management-apim-69d6d656c8-58sjc 1/1 Running apimsvc20 default abc-management-client-downloads-server-7586647f65-9pnzh 1/1 Running apimsvc20 default abc-management-consumer-catalog-7b4b48fddc-8brgk 1/1 Running apimsvc20 default abc-management-juhu-6c87cb4544-nqn9k 1/1 Running apimsvc20 default abc-management-ldap-69ccd95c86-g7dsh 1/1 Running apimsvc20 default abc-management-lur-854c8cfd77-hc5qs 1/1 Running apimsvc20 default abc-management-natscluster-0 1/1 Running apimsvc20 default abc-management-portal-proxy-5955f59d8-68kr9 1/1 Running apimsvc20 default abc-management-s3proxy-0 1/1 Running apimsvc20 default abc-management-site1-db-1 1/1 Running apimsvc20 default abc-management-taskmanager-db76ff4b8-zv4s4 1/1 Running apimsvc20 default abc-management-ui-6c78f87d5-grk59 2/2 Running apimsvc20 default abc-management-up-apim-data-populate-0-to-622-ac339b3f-wf7hb 0/1 Succeeded apimsvc20 default abc-management-up-apim-schema-0-to-622-ac339b3f-tnzbn 0/1 Succeeded apimsvc20 default abc-management-up-lur-data-populate-0-to-103-ac339b3f-dn9vp 0/1 Succeeded apimsvc20 default abc-management-up-lur-schema-0-to-103-ac339b3f-fctp7 0/1 Succeeded apimsvc20 default abc-management-websocket-proxy-5b999cb655-hvp4j 1/1 Running apimsvc20 default edb-operator-657c6658df-dx2rl 1/1 Running apimsvc20 default ibm-apiconnect-6b88f748d-8nb9n 1/1 Running apimsvc20 kube-system calico-kube-controllers-7fbcfc6b49-bzhjs 1/1 Running apimsvc20 kube-system calico-node-sf8nz 1/1 Running apimsvc20 kube-system coredns-b647d6884-m4bdp 1/1 Running apimsvc20 kube-system coredns-b647d6884-r9cvd 1/1 Running apimsvc20 kube-system etcd-apimsvc20 1/1 Running apimsvc20 kube-system ingress-nginx-ingress-controller-nscfv 1/1 Running apimsvc20 kube-system kube-apiserver-apimsvc20 1/1 Running apimsvc20 kube-system kube-apiserver-proxy-apimsvc20 1/1 Running apimsvc20 kube-system kube-controller-manager-apimsvc20 1/1 Running apimsvc20 kube-system kube-proxy-4hvst 1/1 Running apimsvc20 kube-system kube-scheduler-apimsvc20 1/1 Running apimsvc20 kube-system local-volume-provisioner-8m7t8 1/1 Running apimsvc20 kube-system metrics-server-967bc8b5c-h9nch 1/1 Running
-
Enter the following command to connect to your management VM with SSH:
-
Verify you can access the API Connect
Cloud Manager UI at
https://<hostname.domain>/admin.where <hostname.domain> is the
cloud-admin-uiendpoint that you specified in Preparing the management subsystem for deployment.The first time that you access the Cloud Manager user interface, you enter admin for the username and 7iron-hide for the password. You are prompted to change the Cloud Administrator password and email address. See Accessing the Cloud Manager user interface.
- Take a backup of your project directory and configure scheduled management database backups. See Backing up and restoring the management subsystem.