H Rashid,
By running "sudo apic status" I am getting this :
apicadm@vl-aus-bmm-api10v2:~$ sudo apic status
INFO[0000] Log level: info
Cluster members:
- vl-aus-bmm-api10v2.bmc.com (172.20.97.6)
Version: 2.1.1
Type: BOOTSTRAP_MASTER
Install stage: SETUP_SUBSYSTEM
Upgrade stage: UPGRADE_DONE
Subsystem type: management
Subsystem version: 10.0.1.0
Subsystem detail:
Reboot Required: false
Docker status:
Systemd unit: running
Kubernetes status:
Systemd unit: running
Kubelet version: vl-aus-bmm-api10v2 (4.4.0-189-generic) [Kubelet v1.17.9, Proxy v1.17.9]
Etcd status: pod etcd-vl-aus-bmm-api10v2 in namespace kube-system has status Running
Addons: calico, cert-manager, dns, helm, kube-proxy, local-volume-provisioner,
Disk Space Available: 232G/246G
Containers: 36
- Running: 32
- Paused: 0
- Stopped: 4
Images: 21
Etcd cluster state:
- etcd member name: vl-aus-bmm-api10v2.bmc.com, member id: 5893460120487129848, cluster id: 2192063337110438850, leader id: 5893460120487129848, revision: 18206, version: 3.4.9
Pods Summary:
NODE NAMESPACE NAME READY STATUS REASON
vl-aus-bmm-api10v2 cert-manager cert-manager-64cc76f84d-d44k5 1/1 Running
vl-aus-bmm-api10v2 cert-manager cert-manager-cainjector-c9855769f-9pj6q 1/1 Running
vl-aus-bmm-api10v2 cert-manager cert-manager-webhook-7c6f9dfd8b-8cz6f 1/1 Running
vl-aus-bmm-api10v2 kube-system calico-kube-controllers-6cdbd8cf55-m72zp 1/1 Running
vl-aus-bmm-api10v2 kube-system calico-node-7xf6r 1/1 Running
vl-aus-bmm-api10v2 kube-system coredns-6796c8d847-4zh92 1/1 Running
vl-aus-bmm-api10v2 kube-system coredns-6796c8d847-l7lmm 1/1 Running
vl-aus-bmm-api10v2 kube-system etcd-vl-aus-bmm-api10v2 1/1 Running
vl-aus-bmm-api10v2 kube-system ingress-nginx-ingress-controller-99zth 1/1 Running
vl-aus-bmm-api10v2 kube-system kube-apiserver-proxy-vl-aus-bmm-api10v2 1/1 Running
vl-aus-bmm-api10v2 kube-system kube-apiserver-vl-aus-bmm-api10v2 1/1 Running
vl-aus-bmm-api10v2 kube-system kube-controller-manager-vl-aus-bmm-api10v2 1/1 Running
vl-aus-bmm-api10v2 kube-system kube-proxy-z2dsk 1/1 Running
vl-aus-bmm-api10v2 kube-system kube-scheduler-vl-aus-bmm-api10v2 1/1 Running
vl-aus-bmm-api10v2 kube-system local-volume-provisioner-8srx9 1/1 Running
vl-aus-bmm-api10v2 kube-system tiller-deploy-778d4df46b-mfxdw 1/1 Running
And I still don't have access to the web management console.
Can you please advise?
Thanks,
Jala
------------------------------
Jala Zahwa
------------------------------
Original Message:
Sent: Tue August 17, 2021 03:11 AM
From: Rashid Aljohani
Subject: Not able to access the API Connect management console
Hi Jala,
You can check the cluster (management) status by running:
apic status
Also, this is an excellent reference to verify that the management OVA deployment succeeded.: https://www.ibm.com/docs/en/api-connect/10.0.x?topic=subsystem-verify-installation-management
------------------------------
Rashid Aljohani
IBM
Original Message:
Sent: Mon August 16, 2021 10:06 AM
From: Jala Zahwa
Subject: Not able to access the API Connect management console
Hello there,
We just deployed the API Connect OVA and we are trying to access the management console ( https://<cloud-admin-ui>/admin.) but it is unavailable.
What should be done here?
Thanks,
Jala
------------------------------
Jala Zahwa
------------------------------