...
| Code Block | ||||||
|---|---|---|---|---|---|---|
| ||||||
>sudo kubectl get po -n nonrtric NAME READY STATUS RESTARTS AGE a1-sim-osc-0 1/1 Running 0 12m a1-sim-osc-1 1/1 Running 0 10m a1-sim-std-0 1/1 Running 0 12m a1-sim-std-1 1/1 Running 0 10m a1-sim-std2-0 1/1 Running 0 12m a1-sim-std2-1 1/1 Running 0 3m57s a1controller-64c5b7fc56-hjx6l 1/1 Running 0 12m controlpanel-6bf7c4bf79-m6hgl 1/1 Running 0 12m db-76d79cd769-mngm4 1/1 Running 0 12m dmaapadapterservice-0 1/1 Running 0 12m dmaapmediatorservice-0 1/1 Running 0 12m helmmanager-0 1/1 Running 0 12m informationservice-0 1/1 Running 0 12m nonrtricgateway-677988d5c7-rfm88 1/1 Running 0 12m odusliceassurance-cd5b6f568-q89r5 1/1 Running 0 12m oruclosedlooprecovery-568f867b45-b6zld 1/1 Running 0 12m policymanagementservice-0 1/1 Running 0 12m rappcatalogueservice-687d69756c-lvwrg 1/1 Running 0 12m |
Troubleshooting
- After successful installation, control panel shows "No Type" as policy type as shown below.
- If there is no policy type shown and UI looks like below, then the setup can be investigated with below steps (It could be due to synchronization delay as well, It gets fixed automatically after few minutes)
- Verify the PMS logs to make sure that the connection between PMS and a1controller is successful.
Try removing the controller information in specific simulator configuration and verify the simulator are working without a1controller.
Code Block language bash title application_configuration.json collapse true ... { "name":"ric1", "baseUrl":"https://a1-sim-osc-0.a1-sim:8185", "managedElementIds":[ "kista_1", "kista_2" ] }, ...- Curl can be used in control panel pod.
Un-installation
There is a script that uninstalls installs the NonRT RIC components. It is simply run like this:
...