This article explains the issue wherein the interface statistics under Network >> Topology does not get updated with any information. It shows a blank or 0.

The interface statistics under Network Topology shows a blank or 0 for all values even though traffic is being generated and sent to Paragon.

Login to the CLI and check the following:

Status of the pods in the northstar namespace:

kubectl get pods -n northstar | grep -i error | grep -i crashloopbackoff

If the toposerver or the pcserver is seen in either of these states, try to restart them by scaling down and up the deployment:

First get the name of the deployment:

kubectl get deployments -n northstar | grep -i topo

kubectl get deployments -n northstar | grep -i pcserver

Run them as per the deployment which is in crashloopbackoff or error state. Please note that if both show in either of these states, then scale both the toposerver and pcserver down and then up.

kubectl scale deployment/ns-toposerver -n northstar --replicas=0

kubectl scale deployment/ns-toposerver -n northstar --replicas=1

kubectl scale deployment/ns-pcserver -n northstar --replicas=0

kubectl scale deployment/ns-pcserver -n northstar --replicas=1

Check the status of the pods:

kubectl get pods -n northstar | grep toposerver

kubectl get pods -n northstar | grep pcserver

For example:

[root@davinci-master ~]# kubectl get pods -n northstar | grep toposerver

ns-toposerver-656b7d559c-n2x49    2/2   Running   0        11m

[root@davinci-master ~]# 

[root@davinci-master ~]# kubectl get pods -n northstar | grep pcserver

ns-pcserver-5cd6c6d49b-m926r     2/2   Running   1 (5h6m ago)  5h11m

If these are still in the same state, please collect the logs for these and share with the JTAC:

kubectl logs -n northstar ns-pcserver-5cd6c6d49b-m926r syslog > /tmp/ns-pcserver-syslog.txt

kubectl logs -n northstar ns-toposerver-656b7d559c-n2x49 syslog > /tmp/ns-toposerver-syslog.txt

Open a case with JTAC and share these.