Hello

> Classifier got configured by ODL the bridge like below[3], but no
> flow
> entries were issued by ODL

There is currently a problem with the SCF classifiers and sfc103 demo,
you will need this patch

https://git.opendaylight.org/gerrit/#/c/79533/

> 2. SFs got nothing from ODL[4]. While SFFs seem normal, which means
> both bridge and flow entries were configured by ODL.

This could be because odl-sfc-sb-rest feature is not activated?

> 3. In "03-service_function_forwarders.json", what does the "ip" in
> "sff-data-plane-locator" means?[5]

Thats the ip of the vxlan vtep for that OVS instance and incidentally
is the ip  that SFC uses to reach out to that OVS instance.

> 4. In "09-configure-service_function_classifiers"[6], could you
> please
> explain the significance of "interface"? 

That's the name of the OVS interface/port source of the incoming
traffic you wan to classify into the chain.

Note that you have the whole setup of sfc103 demo at

https://github.com/opendaylight/sfc/tree/master/sfc-demo/sfc103

BR
Jaime.

-----Original Message-----
From: Wu Ziyu <[email protected]>
To: [email protected] <[email protected]>,
Jaime Caamaño Ruiz <[email protected]>
Subject: Re: [sfc-dev] cannot find "odl-sfc-ui" on ODL-Neon& Fluorine
Date: Mon, 1 Jul 2019 11:33:02 +0000

Hi Jaime and team,

Good morning,

I still got some questions after following the example[1] and SFC user
guide[2] and asking for your suggestions.

[1]https://github.com/opendaylight/sfc/tree/stable/neon/resources/confi
guration-examples/sfc103

[2]https://buildmedia.readthedocs.org/media/pdf/odl-sfc/latest/odl-sfc.
pdf

I configured exactly the same topology as the SFC user guide[2] like
below:



The issues are:

Classifier got configured by ODL the bridge like below[3], but no flow
entries were issued by ODL
===================
[3].

root@classifier-1:/home/chang# ovs-vsctl show
29d82891-002e-47dd-b69c-ad10ff29d92f
    Manager "tcp:10.5.40.96:6640"
        is_connected: true
    Bridge "br0"
        Controller "tcp:10.5.40.96:6653"
            is_connected: true
        Port "br0"
            Interface "br0"
                type: internal
        Port "classifier1-dpl"
            Interface "classifier1-dpl"
                type: vxlan
                options: {dst_port="6633", key=flow, "nshc1"=flow,
"nshc2"=flow, "nshc3"=flow, "nshc4"=flow, nsi=flow, nsp=flow,
remote_ip=flow}
    ovs_version: "2.11.90"
root@classifier-1:/home/chang# ovs-ofctl dump-flows br0
root@classifier-1:/home/chang# ovs-ofctl -O Openflow13 dump-flows br0
root@classifier-1:/home/chang# ovs-ofctl -O Openflow13 dump-flows br0

===================

2. SFs got nothing from ODL[4]. While SFFs seem normal, which means
both bridge and flow entries were configured by ODL.

===================
[4]

root@sf-1:/home/chang# ovs-vsctl show
bce90480-17b4-41f5-8eb7-dc4f3f212470
    Manager "tcp:10.5.40.96:6640"
        is_connected: true
    ovs_version: "2.11.90"
root@sf-1:/home/chang# 


===================

3. In "03-service_function_forwarders.json", what does the "ip" in
"sff-data-plane-locator" means?[5]
It only takes effect when it same as the "ip-mgmt-address". Which means
when I configure it as "10.0.0.100", the classifier even won't get
bridge configured by ODL.

===================
[5]

                "sff-data-plane-locator": [
                    {
                        "name": "classifier1-dpl",
                        "data-plane-locator": {
                            "transport": "service-locator:vxlan-gpe",
                            "port": 6633,
                            "ip": "10.5.40.97"
                        },
                        "service-function-forwarder-ovs:ovs-options": {
                            "remote-ip": "flow",
                            "dst-port": "6633",
                            "key": "flow",
                            "nsp": "flow",
                            "nsi": "flow",
                            "nshc1": "flow",
                            "nshc2": "flow",
                            "nshc3": "flow",
                            "nshc4": "flow"
                        }
                    }
                ]

===================

4. In "09-configure-service_function_classifiers"[6], could you please
explain the significance of "interface"? 
My understanding is the interface connected to SFF. Is that correct?

===================
[6]

{
  "service-function-classifiers": {
    "service-function-classifier": [
      {
        "name": "Classifier1",
        "scl-service-function-forwarder": [
          {
            "name": "Classifier1",
            "interface": "enp1s0f0"
          }
        ],
        "acl": {
            "name": "ACL1",
            "type": "ietf-access-control-list:ipv4-acl"
         }
      },
      {
        "name": "Classifier2",
        "scl-service-function-forwarder": [
          {
            "name": "Classifier2",
            "interface": "enx503eaa8581e4"
          }
        ],
        "acl": {
            "name": "ACL2",
            "type": "ietf-access-control-list:ipv4-acl"
         }
      }
    ]
  }
}

===================

I also attached my postman_collection.json and the screenshot of the
SFF status.

===================


Appreciate your reply.

Thanks in advance.
BR
Ziyu








From: Jaime Caamaño Ruiz <[email protected]>
Date: 2019年6月24日 16:13
To: Wu Ziyu; [email protected]
Subject: Re: [sfc-dev] cannot find "odl-sfc-ui" on ODL-Neon& Fluorine
 
Hello Ziyu

> But I can’t find plug-in “odl-sfc-ui” which is mentioned in “user-
> guide/service-function-chaining”<https://docs.opendaylight.org/en/sta
> bl
> e-neon/user-guide/service-function-chaining.html>

There is no ui any longer in ODL, thats a leftover in the
documentation. You will need to operate with HTTP REST requests.

> Use pure RESTCONF and send a GET request to URL:http://<odl_ip_addres
> s>;
> :8181/restconf/config/service-function-forwarder:service-function-
> forwarders  - Failed as below screenshot

Unfortunately this is out of date too. The SFF is no longer configured
automatically from an OVS bridge. It works in the opposite direction,
you configure an SFF manually specifying the OVS bridge, and that
bridge gets configured in OVS automatically.

Perhaps this example [1] helps. If you configure that in ODL, 'br-int'
bridge will be added to OVS instance.

[1] https://github.com/opendaylight/sfc/blob/stable/neon/resources/conf
iguration-examples/simple/json/03-service_function_forwarders.json

BR
Jaime.


-----Original Message-----
From: Wu Ziyu <[email protected]>
To: [email protected] <[email protected]>
Subject: [sfc-dev]  cannot find "odl-sfc-ui" on ODL-Neon& Fluorine
Date: Fri, 21 Jun 2019 16:53:31 +0000

Hi Experts,
 
Good days
 
I’m using ODL-Neon and OVS 2.11 for SFC-NSH experiment.
But I can’t find plug-in “odl-sfc-ui” which is mentioned in “user-
guide/service-function-chaining”<https://docs.opendaylight.org/en/stabl
e-neon/user-guide/service-function-chaining.html>
May I know where I can get it or any alternative solution about this?
 
Also I tried using REST api to operate ODL and created ovs-bridge
successfully on the OVS. But I failed to verify the SFF mentioned in
the guide.
 
Could you help on this?
Appreciate your reply
 
Best wishes,
Ziyu
 
 
=======================================================================
========================================
Cannot verify SFF after created ovs-bridge using:
“
Send POST request to URL: http://<odl_ip_address>:8181/restconf/operati
ons/service-function-forwarder-ovs:create-ovs-bridge  - Succeed
Verification

In a shell execute: ovs-vsctl show. There should be a Bridge with the
name br-test and one port/interface called br-test.

Also, the corresponding SFF for this OVS Bridge should be configured,
which can be verified through the SFC User Interface or RESTCONF as
follows.

Visit the SFC User Interface: http://<odl_ip_address>:8181/sfc/index.ht
ml#/sfc/serviceforwarder  - Failed
Use pure RESTCONF and send a GET request to URL:http://<odl_ip_address>
;
:8181/restconf/config/service-function-forwarder:service-function-
forwarders  - Failed as below screenshot
There should be an SFF, whose name will be ending with br1 and the SFF
should contain two DataPlane locators: br1 and testPort.

”
 

 
 
 
=======================================================================
========================================
Cannot find “odl-sfc-ui” plugin
 
chang@mec:~/opendaylight-0.10.1/bin$ ./karaf 
Apache Karaf starting up. Press Enter to open the shell now...
100%
[======================================================================
==]
Karaf started in 17s. Bundle stats: 448 active, 449 total
                                                                       
                   
    ________                       ________                .__  .__    
  .__     __       
    \_____  \ ______   ____   ____ \______ \ _____  ___.__.|  | |__|
____ |  |___/  |_     
     /   |   \\____ \_/ __ \ /    \ |    |  \\__  \<   |  ||  | |  |/
___\|  |  \   __\    
    /    |    \  |_> >  ___/|   |  \|    `   \/ __ \\___  ||  |_|  /
/_/  >   Y  \  |      
    \_______  /   __/ \___  >___|  /_______  (____  /
____||____/__\___  /|___|  /__|      
            \/|__|        \/     \/        \/     \/\/           
/_____/      \/          
                                                                       
                   
 
Hit '<tab>' for a list of available commands
and '[cmd] --help' for help on a specific command.
Hit '<ctrl-d>' or type 'system:shutdown' or 'logout' to shutdown
OpenDaylight.
 
opendaylight-user@root>   
opendaylight-user@root>feature:install odl-sfc-ui
Error executing command: No matching features for odl-sfc-ui/0
 
_______________________________________________
sfc-dev mailing list
[email protected]
https://lists.opendaylight.org/mailman/listinfo/sfc-dev
_______________________________________________
sfc-dev mailing list
[email protected]
https://lists.opendaylight.org/mailman/listinfo/sfc-dev
_______________________________________________
sfc-dev mailing list
[email protected]
https://lists.opendaylight.org/mailman/listinfo/sfc-dev

Reply via email to