Links Missing in the Topology Map
Problem
The topology map in the Paragon Planner desktop application GUI does not display any links for an archived network.
Solution
If the topology map does not display any links for an archived network, there can be two possible reasons: Either the backbone link (bblink.*) file is missing from the system, or the file is present in the system but is empty.
The bblink* file contains the location, quantity, vendor, and attributes of the links found in the network.To check the status of the bblink.* file in the system, do the following:
-
Use your server credentials to log in to the primary node of Paragon Automation.
-
From the primary node, use the following command to obtain the name of the pod associated with the scheduler process (dcscheduler):
root@primary-node:~# kubectl get pod -n northstar|grep dcscheduler
-
Use the following command to log in to the dcscheduler pod:
root@primary-node:~# kubectl exec -it dc-scheduler-pod-name -c dcscheduler -n northstar -- bash
-
Navigate to the directory (/opt/northstar/data/archives/...) that contains the files corresponding to the archived network.
The output displays the list of files present in the directory.
Following is an example output that displays the size of the bblink.* file:
total 360 drwxr-xr-x 1 root root 28 Aug 30 13:15 ./ drwxr-xr-x 1 root root 1 Aug 30 13:15 ../ drwxr-xr-x 1 root root 1 Aug 30 13:15 Log/ drwxr-xr-x 1 root root 10 Aug 30 13:15 Report/ -rw-r--r-- 1 root root 624 Aug 30 13:15 aclist.x -rw-r--r-- 1 root root 572 Aug 30 13:15 atconfig.x -rw-r--r-- 1 root root 24849 Aug 30 13:15 bblink.new
-
From the list of files displayed, check whether the bblink.* file is present and that the file size is greater than 0.
If the file is not present, or if the file is present but the file size is 0, contact the Juniper Networks Technical Assistance Center (JTAC).