Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Documentation is currently in progress.

RANSIM :

Follow the steps below to setup the Ransim environment:

...

  • Clone the repo from : git clone https://github.com/onap-oof-pci-poc/ran-sim
  • Go to the ran-sim/hcsim-content/enodebsim gnbsim directory and build the project : JAVA_HOME=/usr/lib/jvm/java-8-openjdk-amd64/ mvn clean install -Dcheckstyle.skip
    (Note: the project comes with it's own maven settings in ran-sim/hcsim-content/m2_settings.xml, that are required on top of the standard ONAP settings to build this.
  • Go to the ran-sim/Netconf-Agents/hc_50000 directory , 

     (if changes to enodebsim-impl are made run below command to place the jar) 

     cp -r ~/ran-sim/hcsim-content/enodebsim/enodebsim-impl/target/enodebsim-impl-1.0.0-SNAPSHOT.jar lib/org/onap/ransim/enodebsim-impl/1.0.0-SNAPSHOT/

  • Execute the following command from the same directory : docker build -t netconf:latest .
  • Bring up the docker container : docker run -d --name ncserver1 -e "enodebsimIp=10.31.4.45" -e "enodebsimPort=50001" -e "ransimCtrlrIp=10.31.4.45" -e "ransimCtrlrPort=8081" -e "vesEventListenerUrl=https://10.31.4.51:30417/eventListener/v7" -p 50001:50001 -t netconf:latest
  • Bring up any number of netconf servers by changing the container name and port config in the above command.

Troubleshooting Common Errors:

  • Check if the enodebsimIP(IPAddress of Honeycomb), enodebsimPort(Port of Honeycomb), ransimCtrlrIp(IPAddress of Ransim) and ransimCtrlrPort(Ransim Port) is accurate.
  1. After running honeycomb check ransim logs to see successful ping message, data sent to honeycomb or check SDNC restconf page if honeycomb is successfully mounted.
    1. http://localhost:8081/ransimui/index.html check the Netconf Details page in the UI to get the list of all honeycombs running(port to name mapping). 
    2. To manually mount the honeycomb(If mount point not created in SDNR):
      1. curl -i -X PUT -k https://<WokerVMIP>:30267/restconf/config/network-topology:network-topology/topology/topology-netconf/node/<nameAssignedToHoneycombInTheRansimUI> \
          -H 'Accept: application/xml' -H 'Content-Type: text/xml' \
          --user "admin":"Kp8bJ4SXszM0WXlhak3eHlcse2gAw84vaoGGmJvUy2U" \
          -d '<node xmlns="urn:TBD:params:xml:ns:yang:network-topology">
          <node-id>[nameAssignedToHoneycombInTheUI]</node-id>
          <host xmlns="urn:opendaylight:netconf-node-topology">[HoneycombIPAddress]</host>
          <port xmlns="urn:opendaylight:netconf-node-topology">[HoneycombPort]</port>
          <username xmlns="urn:opendaylight:netconf-node-topology">admin</username>
          <password xmlns="urn:opendaylight:netconf-node-topology">admin</password>
          <tcp-only xmlns="urn:opendaylight:netconf-node-topology">false</tcp-only>
          <!-- non-mandatory fields with default values, you can safely remove these if you do not wish to override any of these values-->
          <reconnect-on-changed-schema xmlns="urn:opendaylight:netconf-node-topology">false</reconnect-on-changed-schema>
          <connection-timeout-millis xmlns="urn:opendaylight:netconf-node-topology">20000</connection-timeout-millis>
          <max-connection-attempts xmlns="urn:opendaylight:netconf-node-topology">0</max-connection-attempts>
          <between-attempts-timeout-millis xmlns="urn:opendaylight:netconf-node-topology">2000</between-attempts-timeout-millis>
          <sleep-factor xmlns="urn:opendaylight:netconf-node-topology">1.5</sleep-factor>
          <!-- keepalive-delay set to 0 turns off keepalives-->
          <keepalive-delay xmlns="urn:opendaylight:netconf-node-topology">120</keepalive-delay>
        </node>' -i
  2. To check honeycomb data:
    1.  docker exec -ti <honecombContainerName> bash
    2. cat var/lib/honeycomb/persist/config/data.json
  3. Check if data is mounted on SDNR:
    1. curl -i -X GET https://<workerVmIP>:30267/restconf/config/network-topology:network-topology/topology/topology-netconf/node/ncserver1/yang-ext:mount/oofpcipoc:radio-access -k -H 'Accept: application/xml' -H 'Content-Type: application/xml' \
        --user "admin":"Kp8bJ4SXszM0WXlhak3eHlcse2gAw84vaoGGmJvUy2U" -i
    2.  If data is not mounted, mount the data by running the below requests:
      1. cd var/lib/honeycomb/persist/config
      2. curl -i -X PUT https://<WorkerVMIP>:30267/restconf/config/network-topology:network-topology/topology/topology-netconf/node/<nameAssignedToHoneycombInTheUI>/yang-ext:mount/oofpcipoc:radio-access -k -H 'Accept: application/json' -H 'Content-Type: application/json'   --user "admin":"Kp8bJ4SXszM0WXlhak3eHlcse2gAw84vaoGGmJvUy2U" -d @data.json -i
    3. To delete mount point in SDNR:
      1. curl -i -X DELETE https://<WorkerVMIP>:30267/restconf/config/network-topology:network-topology/topology/topology-netconf/node/<nameAssignedToHoneycombInTheUI> -k -H 'Accept: application/xml' -H 'Content-Type: application/xml' \
          --user "admin":"Kp8bJ4SXszM0WXlhak3eHlcse2gAw84vaoGGmJvUy2U" -i

CPS :

Follow the steps below to setup the CPS environment:

  • Clone the repo from : https://gerrit.onap.org/r/admin/repos/cps
  • Build the project – When building the project run from the root cps folder : mvn clean install
  • From docker-compose folder, run the following after building the images locally : VERSION=latest DB_USERNAME=cps DB_PASSWORD=cps docker-compose up -d
  • Create the dataspace, schemaset, anchor and datanode using the following CPS APIs.

...

  • For code changes in gnbsim-impl directory

    Step 1: Do necessary code changes in gnbsim-impl
    Step 2: Issue the build command "JAVA_HOME=/usr/lib/jvm/java-8-openjdk-amd64/ mvn clean install -Dcheckstyle.skip"

    Once the mvn build is done, build the docker image

    Step 1: Go to directory ~/ran-sim/hcsim-content/gnbsim
    Step 2: JAVA_HOME=/usr/lib/jvm/java-8-openjdk-amd64/ mvn clean install -Dcheckstyle.skip

    Step 3: Import the latest VES certificate into this directory gnbsim-distribution/ rename it as "jssecacerts"
    Step 3: cp -r gnbsim-distribution/jssecacerts gnbsim-distribution/target/gnbsim-distribution-1.19.08-SNAPSHOT-hc/gnbsim-distribution-1.19.08-SNAPSHOT/
    Step 4: cp -r gnbsim-distribution/honeycomb gnbsim-distribution/target/gnbsim-distribution-1.19.08-SNAPSHOT-hc/gnbsim-distribution-1.19.08-SNAPSHOT/
    Step 5: cp -r gnbsim-distribution/Dockerfile gnbsim-distribution/target/gnbsim-distribution-1.19.08-SNAPSHOT-hc/gnbsim-distribution-1.19.08-SNAPSHOT/
    Step 6: docker build -t gn gnbsim-distribution/target/gnbsim-distribution-1.19.08-SNAPSHOT-hc/gnbsim-distribution-1.19.08-SNAPSHOT/

  • Cross check the docker image
    docker images | grep gn

To run the Netconf Servers:

  1. Update ransim and honeycom IP address at ~/ran-sim/hcsim-content/gnbsim/honeycomb/hc/config/gnbsim.json and docker-compose files(step repeated for all hc, cucp, cuup, du folders)

      2. Run the up.sh script in ran-sim/hcsim-content/gnbsim/honeycomb. (wait for all the honeycomb servers to come up)

      3. Run the mount.sh script in ran-sim/hcsim-content/gnbsim/honeycomb.

         After execution of the above script, these servers will be mounted in SDNC(check ransim and SDNR logs if the mount request is successful for all the servers). 

         Access the restconf page to view the mounted servers: https://<WorkerVMIpAddress>:30267/apidoc/explorer/index.htm

Troubleshooting Common Errors:

  • Check if the hcIP(IPAddress of Honeycomb), hcPort(Port of Honeycomb), ransimIp(IPAddress of Ransim) and ransimPort(Ransim Port) in gnbsim.json and in mount.sh is accurate.
  1. After running honeycomb check ransim logs to see successful ping message, data sent to honeycomb or check SDNC restconf page if honeycomb is successfully mounted.
    1. http://localhost:8081/ransimui/index.html check the Netconf Details page in the UI to get the list of all honeycombs running(port to name mapping).
  2. To check honeycomb data:
    1.  docker exec -ti <honecombContainerName> bash
    2. cat var/lib/honeycomb/persist/config/data.json

To bring down the containers give the commands delete-mounted-data.sh and then down.sh.

SDNC:

Check if all the pods are running using the cmd:  kubectl get pods -n onap | grep sdnc

sdnc-oofpcipoc-api-dg.properties

  • change the ransim-mounted to true
  • restapi.cps.anchors.endpoint=${CPS_URL}/cps/api/v1/dataspaces/sondataspace/anchors
  • restapi.cps.tbdmt.execute.endpoint=${CPS_TBDMT_URL}/execute/{schemaSet}/{templateId}

Give the cmd: kubectl exec -it dev-sdnc-0 -n onap bash

  • Check if the dg's are loaded in /opt/onap/sdnc/svclogic/graphs/ranSliceapi 
  • Check the dg's logs in /opt/opendaylight/current/data/log/ 

CPS :

Follow the steps below to setup the CPS environment:

  • Clone the repo from : https://gerrit.onap.org/r/admin/repos/cps
  • Build the project – When building the project run from the root cps folder : mvn clean install
  • From docker-compose folder, run the following after building the images locally : VERSION=latest DB_USERNAME=cps DB_PASSWORD=cps docker-compose up -d
  • Create the dataspace, schemaset, anchor and datanode using the following CPS APIs.

Create Dataspace : 

curl --location --user cpsuser:cpsr0cks! -H "Accept: application/json" -H "Content-Type: application/json" --request POST 'http://localhost:8883/cps/api/v1/dataspaces?dataspace-name=sondataspace'

Create Schemaset :

curl --location --user cpsuser:cpsr0cks! --request POST 'http://localhost:8883/cps/api/v1/dataspaces/sondataspace/schema-sets' --form 'file=@"ran-network.zip"' --form 'schema-set-name="ran-network-schemaset"'

curl --location --user cpsuser:cpsr0cks! --request POST 'http://localhost:8883/cps/api/v1/dataspaces/sondataspace/schema-sets' --form 'file=@"cps-ran-updated.zip"' --form 'schema-set-name="cps-ran-schemaset"'

Create Anchor :

curl --location --user cpsuser:cpsr0cks! --request POST 'http://localhost:8883/cps/api/v1/dataspaces/sondataspace/anchors?schema-set-name=ran-network-schemaset&anchor-name=ran-network-anchor'

curl --location --user cpsuser:cpsr0cks! --request POST 'http://localhost:8883/cps/api/v1/dataspaces/sondataspace/anchors?schema-set-name=cps-ran-schemaset&anchor-name=ran-cps-anchor'

Get all created anchors  :

curl --location --user cpsuser:cpsr0cks! --request GET 'http://localhost:8883/cps/api/v1/dataspaces/sondataspace/anchors'

Create Datanode :

curl --location --user cpsuser:cpsr0cks! --request POST 'http://localhost:8883/cps/api/v1/dataspaces/sondataspace/anchors/ran-network-anchor/nodes' --header 'Content-Type: application/json' -d @ran-network.json

curl --location --user cpsuser:cpsr0cks! --request POST 'http://localhost:8883/cps/api/v1/dataspaces/sondataspace/anchors/ran-cps-anchor/nodes' --header 'Content-Type: application/json' -d @updated-csit-ran-data.json


View file
namecps-ran-updated.zip
height150
View file
nameran-network.zip
height150
View file
namecsit-ran-data.json
height150
View file
nameran-network-data.json
height150

CPS-TBDMT :

Follow the steps below to setup the CPS-TBDMT environment:

  • Clone the repo from : cps/cps-tbdmt · Gerrit Code Review (onap.org)
  • Build the project – mvn clean install

  • Change the docker image name to avoid docker login issues : docker tag nexus3.onap.org:10003/onap/cps-tbdmt:latest cps-tbdmt:latest

  • From the docker-compose folder, edit the application.yml file 

          cpsCoreConfiguration url –  change to VM's IP and the created dataspace's name (sondataspace)

          schemaToAnchor mapping – provide the created schemaset and anchor name ( ran-network-schemaset : ran-network-anchor , cps-ran-schemaset : ran-cps-anchor )

  • From the docker-compose folder, run the following to bring up the containers : docker-compose up -d
  • Once the docker container is up, execute the following TBDMT-APIs

get-cell API :

curl --location --request POST 'http://localhost:8080/templates' --header 'Content-Type: application/json' --data-raw '{
       "templateId": "get-cell",
       "model": "cps-ran-schemaset",
       "requestType": "get",
       "xpathTemplate": "/cps-ran-schema/Regions[@regionId='\''{{regionId}}'\'']/cps-region-cell-mapping",
       "includeDescendants": true
   }' -i

To verify the created template :

curl --location --request POST 'http://localhost:8080/execute/cps-ran-schemaset/get-cell' --header 'Content-Type: application/json' --data-raw '{
       "inputParameters": {
          "regionId":"10000000"
       }
   }' -i

get-nbr-list API :

curl --location --request POST 'http://localhost:8080/templates' --header 'Content-Type: application/json' --data-raw '{
       "templateId": "get-nbr-list",
       "model": "cps-ran-schemaset",
       "requestType": "get",
       "xpathTemplate": "/cps-ran-schema/Regions[@regionId='\''{{netw1000}}'\'']/cps-region-cell-mapping/NRCellCU[@idNRCellCU='\''{{cellId}}'\'']",
       "includeDescendants": true, "transformParam":"NRCellCU"
   }' -i

To verify the created template :

curl --location --request POST 'http://localhost:8080/execute/cps-ran-schemaset/get-nbr-list' --header 'Content-Type: application/json' --data-raw '{
       "inputParameters": {
          "cellId":"13999"
       }
   }' -i

get-nbr-list1 API : (OOF)

curl --location --request POST 'http://localhost:8080/templates' --header 'Content-Type: application/json' --data-raw '{
       "templateId": "get-nbr-list1",
       "model": "cps-ran-schemaset",
       "requestType": "get",
       "xpathTemplate": "/cps-ran-schema/Regions[@regionId='\''{{regionId}}'\'']/cps-region-cell-mapping/NRCellCU[@idNRCellCU='\''{{idNRCellCU}}'\'']",
       "includeDescendants": true, "transformParam":"NRCellCU"
   }' -i

To verify the created template :

curl --location --request POST 'http://localhost:8080/execute/cps-ran-schemaset/get-nbr-list1' --header 'Content-Type: application/json' --data-raw '{
       "inputParameters": {
          "regionId":"10000000",
          "idNRCellCU":"13999"
       }
   }' -i

get-pci API :

curl --location --request POST 'http://localhost:8080/templates' --header 'Content-Type: application/json' --data-raw '{
        "templateId": "get-pci",
        "model": "ran-network-schemaset",
        "requestType": "query-cps-path",
        "xpathTemplate": "//NRCellDU[@idNRCellDU='\''{{cellId}}'\'']",
        "includeDescendants": true,
        "transformParam":"NRCellDU,attributes"
}' -i

To verify the created template :

curl --location

Create Schemaset :

curl --location --user cpsuser:cpsr0cks! --request POST 'http://localhost:8883/cps/api/v1/dataspaces/sondataspace/schema-sets' --form 'file=@"ran-network.zip"' --form 'schema-set-name="ran-network-schemaset"'

curl --location --user cpsuser:cpsr0cks! --request POST 'http://localhost:8883/cps/api/v1/dataspaces/sondataspace/schema-sets' --form 'file=@"cps-ran-updated.zip"' --form 'schema-set-name="cps-ran-schemaset"'

Create Anchor :

curl --location --user cpsuser:cpsr0cks! --request POST 'http://localhost:8883/cps/api/v1/dataspaces/sondataspace/anchors?schema-set-name=ran-network-schemaset&anchor-name=ran-network-anchor'

curl --location --user cpsuser:cpsr0cks! --request POST 'http://localhost:8883/cps/api/v1/dataspaces/sondataspace/anchors?schema-set-name=cps-ran-schemaset&anchor-name=ran-cps-anchor'

Get all created anchors  :

curl --location --user cpsuser:cpsr0cks! --request GET 'http://localhost:8883/cps/api/v1/dataspaces/sondataspace/anchors'

Create Datanode :

curl --location --user cpsuser:cpsr0cks! --request POST 'http://localhost:8883/cps/api/v1/dataspaces/sondataspace/anchors/8080/execute/ran-network-anchorschemaset/nodesget-pci' --header 'Content-Type: application/json' -d @ran-network.json' --data-raw '{
       "inputParameters": {
          "cellId":"14427"
       }
   }' -i

get-pnf API :

curl --location --user cpsuser:cpsr0cks! --request POST 'http://localhost:8883/cps/api/v1/dataspaces/sondataspace/anchors/ran-cps-anchor/nodes8080/templates' --header 'Content-Type: application/json' -d @updated-csit-ran-data.json

View file
nameupdated-csit-ran-data.json
height150
View file
nameran-network.json
height150
View file
nameran-network.zip
height150
View file
namecps-ran-updated.zip
height150

CPS-TBDMT :

Follow the steps below to setup the CPS-TBDMT environment:

  • Clone the repo from : cps/cps-tbdmt · Gerrit Code Review (onap.org)
  • Build the project – mvn clean install

  • Change the docker image name to avoid docker login issues : docker tag nexus3.onap.org:10003/onap/cps-tbdmt:latest cps-tbdmt:latest

  • From the docker-compose folder, edit the application.yml file 

          cpsCoreConfiguration url –  change to VM's IP and the created dataspace's name (sondataspace)

          schemaToAnchor mapping – provide the created schemaset and anchor name ( ran-network-schemaset : ran-network-anchor , cps-ran-schemaset : cps-ran-anchor )

  • From the docker-compose folder, run the following to bring up the containers : docker-compose up -d
  • Once the docker container is up, execute the following TBDMT-APIs

json' --data-raw '{
        "templateId": "get-pnf",
        "model": "ran-network-schemaset",
        "requestType": "query-cps-path",
        "xpathTemplate": "//NRCellDU[@idNRCellDU='\''{{cellId}}'\'']/ancestor::GNBDUFunction",
        "includeDescendants": true, 
        "transformParam":"GNBDUFunction"
}' -i

To verify the created template :

curl --location --request POST 'http://localhost:8080/execute/ran-network-schemaset/get-pnf' --header 'Content-Type: application/json' --data-raw '{
       "inputParameters": {
          "cellId":"14427"
       }
   }' -i

get-nearrtric-by-idgnbdufunction get-cell API :

curl --location --request POST 'http://localhost:8080/templates' --header 'Content-Type: application/json' --data-raw '{
        "templateId": "get-cellget-nearrtric-by-idgnbdufunction",
        "model": "cpsran-rannetwork-schemaset",
        "requestType": "getquery-cps-path",
        "xpathTemplate": "/cps-ran-schema/Regions[@regionId/GNBDUFunction/idGNBDUFunction[text()='\''{{regionIdidGNBDUFunction}}'\'']/cps-region-cell-mappingancestor::NearRTRIC",
        "includeDescendants": true,
        "transformParam":"NearRTRIC,idNearRTRIC"
}' -i

To verify the created template :

curl --location --request POST 'http://localhost:8080/execute/cpsran-rannetwork-schemaset/get-nearrtric-cellby-idgnbdufunction' --header 'Content-Type: application/json' --data-raw '{
       "inputParameters": {
          "regionIdidGNBDUFunction": "netw200022"
       }
   }' -i

get-nbr-list API nearrtric-by-idgnbcucpfunction :

curl --location --request POST 'http://localhost:8080/templates' --header 'Content-Type: application/json' --data-raw '{
        "templateId": "get-nearrtric-nbrby-listidgnbcucpfunction",
        "model": "cpsran-rannetwork-schemaset",
        "requestType": "getquery-cps-path",
        "xpathTemplate": "/cps-ran-schema/Regions[@regionId/GNBCUCPFunction/idGNBCUCPFunction[text()='\''{{netw1000idGNBCUCPFunction}}'\'']/cps-region-cell-mapping/NRCellCU[@idNRCellCU='\''{{cellId}}'\'']ancestor::NearRTRIC",
        "includeDescendants": true
   ": true,
        "transformParam":"NearRTRIC,idNearRTRIC"
}' -i

To verify the created template :

curl --location --request POST 'http://localhost:8080/execute/cpsran-rannetwork-schemaset/get-nbrnearrtric-by-listidgnbcucpfunction' --header 'Content-Type: application/json' --data-raw '{
       "inputParameters": {
          "cellIdidGNBCUCPFunction": "Chn0005cucpserver1"
       }
   }' -i

getput-nbrnrpci-list1 API nrcelldu : (OOF)

curl --location --request POST 'http://localhost:8080/templates' --header 'Content-Type: application/json' --data-raw '{
        "templateId": "getput-nbrnrpci-list1nrcelldu",
        "model": "cpsran-rannetwork-schemaset",
        "requestType": "getpatch",
        "xpathTemplate": "/cps-ran-schemanetwork/RegionsNearRTRIC[@regionId@idNearRTRIC='\''{{regionIdidNearRTRIC}}'\'']/cps-region-cell-mapping/NRCellCU[@idNRCellCUGNBDUFunction[@idGNBDUFunction='\''{{idGNBDUFunction}}'\'']/NRCellDU[@idNRCellDU='\''{{idNRCellCUidNRCellDU}}'\'']",
        "includeDescendants": true
   }' -i

To verify the created template :

curl --location --request POST 'http://localhost:8080/execute/cpsran-rannetwork-schemaset/getput-nbrnrpci-list1nrcelldu' --header 'Content-Type: application/json' --data-raw '{
       "inputParameters": {
       "idNearRTRIC":"11",
       "regionIdidGNBDUFunction":"netw100022",
          "idNRCellCUidNRCellDU":"Chn0005"
        },
       "payload": {
        "attributes":{"nRPCI":3}
}
   }' -i

get-pci API put-nrpci-nrcelldu :

curl --location --request POST 'http://localhost:8080/templates' --header 'Content-Type: application/json' --data-raw '{
        "templateId": "getput-nrpci-pcinrcelldu",
        "model": "ran-network-schemaset",
        "requestType": "getpatch",
        "xpathTemplate": "/ran-network/NearRTRIC[@idNearRTRIC='\''{{11idNearRTRIC}}'\'']/GNBDUFunction[@idGNBDUFunction='\''{{110idGNBDUFunction}}'\'']/NRCellDU[@idNRCellDU='\''{{cellIdidNRCellDU}}'\'']/attributes",
        "includeDescendants": true
   }' -i

To verify the created template :

curl --location --request POST 'http://localhost:8080/execute/ran-network-schemaset/getput-nrpci-pcinrcelldu' --header 'Content-Type: application/json' --data-raw '{{
       "inputParameters": {
       "idNearRTRIC":"11",
       "idGNBDUFunction":"22",
       "idNRCellDU":"Chn0005"
        },
       "inputParameterspayload": {
          "cellIdattributes":{"Chn0005nRPCI"
       :3}
}
   }' -i

get-pnf API put-ho-nrcellrelation :

curl --location --request POST 'http://localhost:8080/templates' --header 'Content-Type: application/json' --data-raw '{
        "templateId": "getput-ho-pnfnrcellrelation",
        "model": "ran-network-schemaset",
        "requestType": "query-cps-pathpatch",
        "xpathTemplate": "///ran-network/NearRTRIC[@idNearRTRIC='\''{{idNearRTRIC}}'\'']/GNBCUCPFunction[@idGNBCUCPFunction='\''{{idGNBCUCPFunction}}'\'']/NRCellCU[@idNRCellCU='\''{{cellIdidNRCellCU}}'\'']/ancestor::GNBCUCPFunctionNRCellRelation[@idNRCellRelation='\''{{idNRCellRelation}}'\'']",
        "includeDescendants": true
}' -i

...

curl --location --request POST 'http://localhost:8080/execute/ran-network-schemaset/getput-ho-pnfnrcellrelation' --header 'Content-Type: application/json' --data-raw '{json' --data-raw '{
       "inputParameters": {
       "idNearRTRIC":"11",
       "idGNBCUCPFunction":"ncserver1",
       "inputParametersidNRCellCU": {"Chn0003",
         "cellIdidNRCellRelation":"Chn0008"
       },
      "payload": {
      "attributes":{"nRTCI":2,"isHOAllowed":true}
      }
   }' -i

POLICY :

There following control policies that are being used in the usecase. They have to be created and pushed into the policy.

View file
namepcisonBpci_push.json
height250
View file
namesonBpci_push.json
height250
View file
namesonBpcipciBson_push.json
height250
View file
namepciBson_push.json
height250
View file
namepciBsonson_push.json
height250
View file
namesonpci_push.json
height250
View file
namepci_push.json
height250
View file
nameson.json
height250

...