Working on R-CORD Without an OLT/ONU

This section describes a developer workflow that works in scenarios where you do not have a real OLT or ONU. It combines steps from the "bottom-up" and "top-down" subscriber provisioning sequences described here.

The idea is to add the access device's (OLT/PONPORT/ONU) to the XOS data model through "top-down" provisioning, with the "bottom-up" action of VOLTHA publishing a newly discovered ONU to the Kafka bus simulated by a python script.


  • All the components needed for the R-CORD profile are up and running on your POD (xos-core, rcord-lite, voltha, onos-voltha).
  • Configure OLT/PONPORT/ONU devices using the sample TOSCA config given below:
tosca_definitions_version: tosca_simple_yaml_1_0
  - custom_types/oltdevice.yaml
  - custom_types/onudevice.yaml
  - custom_types/ponport.yaml
  - custom_types/voltservice.yaml
description: Create a simulated OLT Device in VOLTHA

      type: tosca.nodes.OLTDevice
        device_type: simulated_olt
        port: 50060
        must-exist: true

      type: tosca.nodes.PONPort
        name: test_pon_port_1
        port_no: 2
        s_tag: 222
        - olt_device:
            node: device#olt
            relationship: tosca.relationships.BelongsToOne

      type: tosca.nodes.ONUDevice
        serial_number: BRCM1234
        vendor: Broadcom
        - pon_port:
            node: pon_port
            relationship: tosca.relationships.BelongsToOne

Push "onu-event" to Kafka

The following event needs to be pushed manually.

event = json.dumps({
    'status': 'activated',
    'serial_number': 'BRCM1234',
    'uni_port_id': 16,
    'of_dpid': 'of:109299321'

Make sure that the serial_number in the event matches the serial_numberyou configured when adding the ONU device. XOS uses the serial number to make sure the device is actually listed (volt/onudevices).

The script for pushing the onu-event to Kafka ( is already available in the container running volt-synchronizer and you may execute it as:

cordserver@cordserver:~$ kubectl get pods | grep rcord-lite-volt
rcord-lite-volt-dd98f78d6-rwwhz                                   1/1       Running            0          10d

cordserver@cordserver:~$ kubectl exec rcord-lite-volt-dd98f78d6-rwwhz python /opt/xos/synchronizers/volt/

If you need to update the contents of the event file, you have to do an apt update and apt install vim within the container.


  • Verify that the hippie-oss instance is created for the event (i.e., verify the serial number of ONU). The hippie-oss container is intended to verify ONU serial number with an external OSS-DB, but this is now configured to always validate the ONU.
  • Verify a new rcord-subscriber service instance is created.
  • Once the rcord-subscriber service instance is created, make sure new service instances are created for the volt and vsg-hw models.
curl -X GET -u ""
curl -X GET -u ""
curl -X GET -u ""
curl -X GET -u ""

results matching ""

    No results matching ""