To check the infrastructure:
- Log in to the SFSS VM as a
root
user through the console. - Verify if the following containers are running. Run the following commands:
- kubectl get pods—Verify that the status of the containers is Running.
root@dellemc-networkappliance:~# kubectl get pods
NAME READY STATUS RESTARTS AGE
stfs-app-alerts-deployment-6f69fb5499-69cxm 1/1 Running 0 6d23h
stfs-app-redis-deployment-79b869bc67-v69lp 1/1 Running 0 6d23h
stfs-app-rest-deployment-7bd4bf7c8f-jv46v 1/1 Running 0 6d23h
stfs-cdcproxy-deployment-1-0 1/1 Running 0 6d20h
stfs-cdcproxy-deployment-1-1 1/1 Running 0 6d20h
stfs-centralnz-deployment-1-689db9475f-jmc8q 2/2 Running 0 6d20h
stfs-discovery-1 1/1 Running 0 6d20h
stfs-license-857786785-qmx2v 1/1 Running 0 6d23h
stfs-monitor-655b869dfd-j6bbk 1/1 Running 0 6d23h
stfs-redis-deployment-1-6cd4c6788c-5m487 1/1 Running 0 6d20h
stfs-syslogng-6966f8dcf8-mvx28 2/2 Running 0 6d23h - kubectl get svc—Verify that the
stfs-app
services are listed.root@dellemc-networkappliance:~# kubectl get svc
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
kubernetes ClusterIP 172.18.1.1 <none> 443/TCP 6d23h
stfs-app-alerts-svc ClusterIP 172.18.1.223 <none> 50054/TCP 6d23h
stfs-app-redis-svc NodePort 172.18.1.189 172.18.2.1 6379:32322/TCP 6d23h
stfs-app-rest-svc NodePort 172.18.1.233 172.18.2.1 9005:31486/TCP 6d23h
stfs-cdc-rest-service-1 NodePort 172.18.1.124 172.18.2.1 9006:30172/TCP 6d20h
stfs-cdcproxy-service-1 NodePort 172.18.1.150 172.18.21.250 8009:30884/TCP 6d20h
stfs-centralnz-service-1 ClusterIP 172.18.1.23 <none> 50052/TCP 6d20h
stfs-license ClusterIP 172.18.1.56 <none> 50053/TCP 6d23h
stfs-redis-1 ClusterIP 172.18.1.52 <none> 6380/TCP 6d20h
stfs-syslogng NodePort 172.18.1.42 172.18.2.1 11514:30709/UDP,6381:31562/TCP,11614:32404/TCP 6d23h - kubectl get nodes—Verify that the SFSS node status is Ready.
root@dellemc-networkappliance:~# kubectl get nodes
NAME STATUS ROLES AGE VERSION
sfss Ready control-plane,master 6d23h v1.21.1
- kubectl get pods—Verify that the status of the containers is Running.