Uploaded image for project: 'Common Controller SDK'
  1. Common Controller SDK
  2. CCSDK-3845

Device status from Connected to Connecting taking nearly 20min when interface down

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Medium Medium
    • None
    • Jakarta Release, Kohn Release
    • apps - sdnr
    • None

      Device status updation from Connected to connecting is taking nearly 20min when interface down but when we made the Simulator down it is taking few seconds to update the status from Connected to connecting.

       

      Logs for Simulator down:

       

       

      Steps to reproduce when interface down:

      1.Run RU/DU simulator (Docker based, nexus3.o-ran-sc.org:10002/o-ran-sc/nts-ng-o-ran-ru-fh:1.3.3) and connect the device to SDNR, once device is on connected state login to docker container by running command
      docker exec -it <ru/du_container_id> bash

      2.Install iproute tool on the container

      apt install iproute2

      3.Make the Eth0 interface down by below command,

      ip link set dev eth0 down

      4.Once the interface is down verify the port is not getting connected,

      telnet IP_address Port_number

      telnet 192.168.101.244 2300
      Trying 192.168.101.244...
      telnet: Unable to connect to remote host: No route to host

      And could see that on SDNR GUI device is still showing as connected.

       

      Logs attached.

       

       

       

       

       

       

       

       

       

       

            highstreetherbert Herbert Eiselt
            sabithaa sabithaa
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: