Hi there,

I'm new to ODL but have been labbing a little bit with a BGP-LS use case. Basically, i have an OSPF area and the AS gateway (running ios xr) which runs both BGP and OSPF is announcing link-state routes.
I have gotten this use case to work with release release 0.7.0, following the documentation https://docs.opendaylight.org/projects/bgpcep/en/latest/bgp/index.html for refernce but using this guide
https://wiki.minet.net/sdn/opendaylight/bgpls for Silicon.

Now the problems start with the newer releases.
For example with 0.16. (Sulfur) which i dowloaded as a tarball, doesn't start listning on 1790 or 1791 after installing odl-bgpcep-bgp, not matter what i tried.

Using the docker image 0.18.0 (Argon) from https://hub.docker.com/r/opendaylight/opendaylight/tags , it's not listening either on BGP ports.

now for the main problem which concerns both Sulfur and Argon.
the URL:s and the corresonding data models that is used in the documentation don't seem to exist anymore. 
So another way would be not to use RESTCONF and instead use odl-bgpcep-bgp-config-example, which provides a template to start with. I see these files network-toplogy-bgp-config.xml , routing-policy-default-config.xml and protocols-config.xml in
/etc/opendaylight/bgpcep/ , but even then I don't see the data models being created. for example no network topology, no bgp rib.
Most importantly the only URL i can query is /rests/data which gives me back a data model corresponding to routing-policy-default-config.xml only. So the logical conclusion would be that installing odl-bgpcep-bgp-config-example is not doing anything.


Am i making some wrong assumptions here on how this should be setup? Currently, I can't find any BGPCEP documentation for sulfur or Argon releases. Searching the internet didn't give anything useful either.

Hi Uriel,

I also started using ODL very recently and I do not know how to implement or install the functionality that Robert Varga sent us. Can anybody in this list give us a hint on how to use the code that Robert sent in his previous email?

Thanks,

David

Makes sense, I will take a look at your patches.

Hi David,

Do you know how install or include this functionality? I still don't know how to implement the learning switch function and I don't understand the logic behind the code in the link.

Regards,

Uriel

Hi Ivan,

Hi Robert,

Thanks for the links to a learning switch. How do we install or include this functionality into an ODL controller?

Regards,

David

On 19/04/2023 08.40, ulopez@... wrote:

Hi David,
Thanks for your help, I think it's a good start to work with ODL by defining flows, so I can tell the switch to work normal. However, I don't understand how to define a learning switch, where it is the controller or the application that learns the relationship between the MACs and the in-port.

A learning switch example is here: https://github.com/opendaylight/openflowplugin/tree/master/samples/learning-switch

There is a more complete switch in a separate project here: https://github.com/opendaylight/l2switch/ but it has been long out of maintenance.

Regards,
Robert

'm trying to connect several openflow OVS instances to OpenDayLight SDN.

My switches succesfully attached and I can get nodes info via RESTCONF like this /rests/data/opendaylight-inventory:nodes

But I can't get openflow table information via TABLE url. Official documentation says I can use restconf request like this: /rests/data/opendaylight-inventory:nodes/node=openflow:121062366427215/table=0

But I'm getting error

{
    "errors": {
        "error": [
            {
                "error-tag": "data-missing",
                "error-message": "Schema for '(urn:opendaylight:inventory?revision=2013-08-19)table' not found",
                "error-type": "protocol"
            }
        ]
    }
}

opendaylight version 4.4.2

Any help appreciated. Thanks

Hi David,

Hi,

What I did to emulate L2 networks, is to install JSON instructions at the controller, for each switch that I needed to test.

For example, to install a JSON file in an ODL controller with IP address 192.168.1.166, that commands to flood all packets received at port 1 of switch 2, use the following curl instruction:

curl -u admin:admin -X PUT -d "@s2_ping1.json" -H "Content-Type: application/json" http://192.168.1.166:8181/rests/data/opendaylight-inventory:nodes/node=openflow:2/flow-node-inventory:table=0/flow=201

where the "s2_ping1.json" file contains the following instructions:

{
    "flow": [
        {
            "table_id": "0",
            "id": "201",
            "priority": "1001",
            "match": {
                "in-port": "openflow:2:1"
            },
            "instructions": {
                "instruction": [
                    {
                        "order": 0,
                        "apply-actions": {
                            "action": [
                                {
                                    "order": 0,
                                    "output-action": {
                                        "output-node-connector": "FLOOD"
                                    }
                                }
                            ]
                        }
                    }
                ]
            }
        }
    ]
}

Similarly, the following instruction tells the controller that all packets received at port 2 of switch 1, will be forwarded to port 2:

curl -u admin:admin -X PUT -d "@s1_ping2.json" -H "Content-Type: application/json" http://192.168.1.166:8181/rests/data/opendaylight-inventory:nodes/node=openflow:1/flow-node-inventory:table=0/flow=102

where the "s1_ping2.json" file contains:

{
    "flow": [
        {
            "table_id": "0",
            "id": "102",
            "priority": "1002",
            "match": {
                "in-port": "openflow:1:2"
            },
            "instructions": {
                "instruction": [
                    {
                        "order": 0,
                        "apply-actions": {
                            "action": [
                                {
                                    "order": 0,
                                    "output-action": {
                                        "output-node-connector": "1"
                                    }
                                }
                            ]
                        }
                    }
                ]
            }
        }
    ]
}

This is the solution that worked for me. Since I am also new to ODL, I would like to know if there is an easier way to implement this functionality.

Regards,

David Arjona