Unable to fetch nodes information from ran simulator through onos-cli

[Bhanupriya03]

Hi Team,

We have deployed ran-simulator successfully following https://github.com/onosproject/ran-simulator/blob/master/docs/quick_start.md link.
Please have a look at the sdran subsystems deployed :

<style> </style>

NAME	READY	STATUS	RESTARTS	AGE
onos-a1t-665f57866f-5cds7	1/2	Running	88 (4m12s ago)	5h49m
onos-cli-5bf8dd6895-l7lg4	1/1	Running	0	5h49m
onos-config-58b9f9f5fb-pbh9v	2/3	Running	66 (4m7s ago)	5h49m
onos-e2t-5959487b76-k9cnz	1/2	Running	66 (4m2s ago)	5h49m
onos-topo-7b48559874-7xqz9	1/2	Running	64 (4m12s ago)	5h49m
onos-uenib-5795f86457-nn8qw	1/2	Running	67 (4m32s ago)	5h49m
onos-uenib-5795f86457-nn8qw	1/1	Running	0	5h49m
sd-ran-consensus-0	0/1	Pending	0	5h49m
sd-ran-consensus-1	0/1	Pending	0	5h49m
sd-ran-consensus-2	0/1	Pending	0	5h49m

But we are unable to get the ran-sim nodes from onos-cli. Please have a look at the issue we are getting :

~ $ onos ransim get nodes
GnbID Status Service Models E2T Controllers Cell NCGIs
rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing: dial tcp: lookup topo-discovery on 10.96.0.10:53: server misbehaving"
~ $

However, we are getting the nodes without onos-cli using the following commands :

clipod=$(kubectl -n sd-ran get pods | grep onos-cli | cut -d\ -f1)
kubectl -n sd-ran exec --stdin $clipod -- /usr/local/bin/onos ransim get nodes

Output :

GnbID Status Service Models E2T Controllers Cell NCGIs
5153 Running mho,rcpre2,kpm2,rc e2t-1 13842601454c001,13842601454c002,13842601454c003
5154 Running mho,rcpre2,kpm2,rc e2t-1 138426014550001,138426014550002,138426014550003
[root@localhost ~]#
[root@localhost ~]#

Please suggest how to resolve the issue when we are fetching nodes from onos-cli.