Hi, Brady.
Thanks for your fix. Thanks to this fixt, the error related to ODL API RSP
created is resolved.
However, when I clean all (i.e. vagrant destroy -f) and restart sfc103(i.e.
demo.sh), classifier1 still cannot manage to executes command <wget> to
communicate with classfier2. I use ODL Fluorine + OVS 2.10.
Before asking for your and the community’s help, I try to figure out myself. I
first check the logfile of ODL (i.e. path/to/karaf_log/karaf.log) and filter
the contents with “ERROR”:
2019-01-17T15:52:47,150 | ERROR |
opendaylight-cluster-data-akka.actor.default-dispatcher-3 |
DOMEntityOwnershipListenerAdapter | 294 -
org.opendaylight.mdsal.eos-binding-adapter - 3.0.4 | Error converting DOM
entity ID
/(urn:opendaylight:params:xml:ns:yang:mdsal:core:general-entity?revision=2015-09-30)entity/entity[{(urn:opendaylight:params:xml:ns:yang:mdsal:core:general-entity?revision=2015-09-30)name=ofp-topology-manager}]
to binding InstanceIdentifier
java.lang.NullPointerException: null
2019-01-17T15:56:13,804 | ERROR |
opendaylight-cluster-data-akka.actor.default-dispatcher-2 |
DOMEntityOwnershipListenerAdapter | 294 -
org.opendaylight.mdsal.eos-binding-adapter - 3.0.4 | Error converting DOM
entity ID
/(urn:opendaylight:params:xml:ns:yang:mdsal:core:general-entity?revision=2015-09-30)entity/entity[{(urn:opendaylight:params:xml:ns:yang:mdsal:core:general-entity?revision=2015-09-30)name=openflow:169900783159372}]
to binding InstanceIdentifier
java.lang.NullPointerException: null
2019-01-17T15:56:13,825 | ERROR |
opendaylight-cluster-data-akka.actor.default-dispatcher-6 |
DOMEntityOwnershipListenerAdapter | 294 -
org.opendaylight.mdsal.eos-binding-adapter - 3.0.4 | Error converting DOM
entity ID
/(urn:opendaylight:params:xml:ns:yang:mdsal:core:general-entity?revision=2015-09-30)entity/entity[{(urn:opendaylight:params:xml:ns:yang:mdsal:core:general-entity?revision=2015-09-30)name=openflow:161082929448001}]
to binding InstanceIdentifier
java.lang.NullPointerException: null
2019-01-17T15:56:13,828 | ERROR |
opendaylight-cluster-data-akka.actor.default-dispatcher-4 |
DOMEntityOwnershipListenerAdapter | 294 -
org.opendaylight.mdsal.eos-binding-adapter - 3.0.4 | Error converting DOM
entity ID
/(urn:opendaylight:params:xml:ns:yang:mdsal:core:general-entity?revision=2015-09-30)entity/entity[{(urn:opendaylight:params:xml:ns:yang:mdsal:core:general-entity?revision=2015-09-30)name=openflow:257641316118598}]
to binding InstanceIdentifier
java.lang.NullPointerException: null
2019-01-17T15:56:13,832 | ERROR |
opendaylight-cluster-data-akka.actor.default-dispatcher-4 |
DOMEntityOwnershipListenerAdapter | 294 -
org.opendaylight.mdsal.eos-binding-adapter - 3.0.4 | Error converting DOM
entity ID
/(urn:opendaylight:params:xml:ns:yang:mdsal:core:general-entity?revision=2015-09-30)entity/entity[{(urn:opendaylight:params:xml:ns:yang:mdsal:core:general-entity?revision=2015-09-30)name=openflow:196794075627855}]
to binding InstanceIdentifier
The whole log file is available at URL:
https://www.dropbox.com/s/kh01oqwrbu0ao72/karaf.log?dl=0
<https://www.dropbox.com/s/kh01oqwrbu0ao72/karaf.log?dl=0>
Then I check the dump flows of ‘classifier1’ with: docker exec -it classifier1
ovs-ofctl dump-flows -OOpenflow13 br-sfc. The output:
cookie=0x0, duration=8087.160s, table=0, n_packets=245, n_bytes=18130,
priority=1000,tcp,in_port="veth-br",nw_src=192.168.2.0/24,nw_dst=192.168.2.0/24,tp_dst=80
actions=encap(nsh),encap(ethernet),set_field:0xd/0xffffff->nsh_spi,set_field:255->nsh_si,set_field:0x1->nsh_c1,set_field:0x2->nsh_c2,set_field:0x3->nsh_c3,set_field:0x4->nsh_c4,load:0xc0a80114->NXM_NX_TUN_IPV4_DST[],output:"sff0-dpl"
cookie=0x0, duration=8087.154s, table=0, n_packets=0, n_bytes=0,
priority=1000,dl_type=0x894f,nsh_spi=0x80000d,nsh_si=253
actions=decap(),decap(),output:"veth-br"
cookie=0x14, duration=8087.160s, table=0, n_packets=0, n_bytes=0, priority=5
actions=goto_table:1
Nothing special. 245 packets have been sent out. Then I tried to verify the
dump flows of ’SFF1’, which should receive packets from ‘classifier1’. The dump
flows of SFF1 are:
vagrant@odl:~$ docker exec -it sff1 ovs-ofctl dump-flows -Oopenflow13 br-sfc
cookie=0x0, duration=8356.847s, table=0, n_packets=0, n_bytes=0,
priority=1000,dl_type=0x894f,nsh_spi=0x80000d,nsh_si=253
actions=load:0xc0a8010a->NXM_NX_TUN_IPV4_DST[],IN_PORT
cookie=0x14, duration=8366.192s, table=0, n_packets=0, n_bytes=0, priority=5
actions=goto_table:1
cookie=0x14, duration=8366.192s, table=1, n_packets=0, n_bytes=0,
priority=250,packet_type=(1,0x894f) actions=encap(ethernet),goto_table:4
cookie=0x14, duration=8366.192s, table=1, n_packets=0, n_bytes=0,
priority=250,dl_type=0x894f actions=goto_table:4
cookie=0x14, duration=8366.192s, table=1, n_packets=0, n_bytes=0, priority=5
actions=drop
cookie=0x14, duration=8366.192s, table=2, n_packets=0, n_bytes=0, priority=5
actions=goto_table:3
cookie=0x14, duration=8366.192s, table=3, n_packets=0, n_bytes=0, priority=5
actions=goto_table:4
cookie=0x14, duration=8366.192s, table=4, n_packets=0, n_bytes=0,
priority=550,dl_type=0x894f,nsh_spi=0x5,nsh_si=255
actions=load:0xc0a8011e->NXM_NX_TUN_IPV4_DST[],goto_table:10
cookie=0x14, duration=8366.192s, table=4, n_packets=0, n_bytes=0,
priority=550,dl_type=0x894f,nsh_spi=0xd,nsh_si=254
actions=load:0xc0a80132->NXM_NX_TUN_IPV4_DST[],goto_table:10
cookie=0x14, duration=8366.192s, table=4, n_packets=0, n_bytes=0,
priority=550,dl_type=0x894f,nsh_spi=0x800005,nsh_si=255
actions=load:0xc0a8011e->NXM_NX_TUN_IPV4_DST[],goto_table:10
cookie=0x14, duration=8366.192s, table=4, n_packets=0, n_bytes=0,
priority=550,dl_type=0x894f,nsh_spi=0xd,nsh_si=255
actions=load:0xc0a8011e->NXM_NX_TUN_IPV4_DST[],goto_table:10
cookie=0x14, duration=8366.192s, table=4, n_packets=0, n_bytes=0,
priority=550,dl_type=0x894f,nsh_spi=0x80000d,nsh_si=254
actions=load:0xc0a8011e->NXM_NX_TUN_IPV4_DST[],goto_table:10
cookie=0x14, duration=8366.192s, table=4, n_packets=0, n_bytes=0, priority=5
actions=goto_table:10
cookie=0xba5eba1100000102, duration=8366.192s, table=10, n_packets=0,
n_bytes=0,
priority=660,dl_type=0x894f,nsh_mdtype=1,nsh_spi=0x5,nsh_si=254,nsh_c1=0x0
actions=IN_PORT
cookie=0xba5eba1100000102, duration=8366.192s, table=10, n_packets=0,
n_bytes=0,
priority=660,dl_type=0x894f,nsh_mdtype=1,nsh_spi=0x800005,nsh_si=254,nsh_c1=0x0
actions=IN_PORT
cookie=0xba5eba1100000102, duration=8366.192s, table=10, n_packets=0,
n_bytes=0,
priority=660,dl_type=0x894f,nsh_mdtype=1,nsh_spi=0x80000d,nsh_si=253,nsh_c1=0x0
actions=IN_PORT
cookie=0xba5eba1100000103, duration=8366.192s, table=10, n_packets=0,
n_bytes=0,
priority=655,in_port="sff1-dpl",dl_type=0x894f,nsh_spi=0x5,nsh_si=254
actions=move:NXOXM_NSH_C1[]->NXM_NX_TUN_IPV4_DST[],move:NXOXM_NSH_C2[]->NXM_NX_TUN_ID[0..31],IN_PORT
cookie=0xba5eba1100000101, duration=8366.192s, table=10, n_packets=0,
n_bytes=0,
priority=655,in_port="sff1-dpl",dl_type=0x894f,nsh_spi=0x5,nsh_si=255
actions=move:NXM_NX_TUN_ID[0..31]->NXM_NX_TUN_ID[0..31],IN_PORT
cookie=0xba5eba1100000101, duration=8366.192s, table=10, n_packets=0,
n_bytes=0,
priority=655,in_port="sff1-dpl",dl_type=0x894f,nsh_spi=0x800005,nsh_si=255
actions=move:NXM_NX_TUN_ID[0..31]->NXM_NX_TUN_ID[0..31],IN_PORT
cookie=0xba5eba1100000103, duration=8366.192s, table=10, n_packets=0,
n_bytes=0,
priority=655,in_port="sff1-dpl",dl_type=0x894f,nsh_spi=0x800005,nsh_si=254
actions=move:NXOXM_NSH_C1[]->NXM_NX_TUN_IPV4_DST[],move:NXOXM_NSH_C2[]->NXM_NX_TUN_ID[0..31],IN_PORT
cookie=0xba5eba1100000101, duration=8366.192s, table=10, n_packets=0,
n_bytes=0,
priority=655,in_port="sff1-dpl",dl_type=0x894f,nsh_spi=0xd,nsh_si=255
actions=move:NXM_NX_TUN_ID[0..31]->NXM_NX_TUN_ID[0..31],IN_PORT
cookie=0xba5eba1100000101, duration=8366.192s, table=10, n_packets=0,
n_bytes=0,
priority=655,in_port="sff1-dpl",dl_type=0x894f,nsh_spi=0xd,nsh_si=254
actions=move:NXM_NX_TUN_ID[0..31]->NXM_NX_TUN_ID[0..31],IN_PORT
cookie=0xba5eba1100000101, duration=8366.192s, table=10, n_packets=0,
n_bytes=0,
priority=655,in_port="sff1-dpl",dl_type=0x894f,nsh_spi=0x80000d,nsh_si=254
actions=move:NXM_NX_TUN_ID[0..31]->NXM_NX_TUN_ID[0..31],IN_PORT
cookie=0xba5eba1100000103, duration=8366.192s, table=10, n_packets=0,
n_bytes=0,
priority=655,in_port="sff1-dpl",dl_type=0x894f,nsh_spi=0x80000d,nsh_si=253
actions=move:NXOXM_NSH_C1[]->NXM_NX_TUN_IPV4_DST[],move:NXOXM_NSH_C2[]->NXM_NX_TUN_ID[0..31],IN_PORT
cookie=0xba5eba1100000101, duration=8366.192s, table=10, n_packets=0,
n_bytes=0, priority=650,dl_type=0x894f,nsh_spi=0x5,nsh_si=255
actions=move:NXM_NX_TUN_ID[0..31]->NXM_NX_TUN_ID[0..31],output:"sff1-dpl"
cookie=0xba5eba1100000101, duration=8366.192s, table=10, n_packets=0,
n_bytes=0, priority=650,dl_type=0x894f,nsh_spi=0x800005,nsh_si=255
actions=move:NXM_NX_TUN_ID[0..31]->NXM_NX_TUN_ID[0..31],output:"sff1-dpl"
cookie=0xba5eba1100000103, duration=8366.192s, table=10, n_packets=0,
n_bytes=0, priority=650,dl_type=0x894f,nsh_spi=0x5,nsh_si=254
actions=move:NXOXM_NSH_C1[]->NXM_NX_TUN_IPV4_DST[],move:NXOXM_NSH_C2[]->NXM_NX_TUN_ID[0..31],output:"sff1-dpl"
cookie=0xba5eba1100000103, duration=8366.192s, table=10, n_packets=0,
n_bytes=0, priority=650,dl_type=0x894f,nsh_spi=0x800005,nsh_si=254
actions=move:NXOXM_NSH_C1[]->NXM_NX_TUN_IPV4_DST[],move:NXOXM_NSH_C2[]->NXM_NX_TUN_ID[0..31],output:"sff1-dpl"
cookie=0xba5eba1100000101, duration=8366.192s, table=10, n_packets=0,
n_bytes=0, priority=650,dl_type=0x894f,nsh_spi=0xd,nsh_si=254
actions=move:NXM_NX_TUN_ID[0..31]->NXM_NX_TUN_ID[0..31],output:"sff1-dpl"
cookie=0xba5eba1100000101, duration=8366.192s, table=10, n_packets=0,
n_bytes=0, priority=650,dl_type=0x894f,nsh_spi=0xd,nsh_si=255
actions=move:NXM_NX_TUN_ID[0..31]->NXM_NX_TUN_ID[0..31],output:"sff1-dpl"
cookie=0xba5eba1100000101, duration=8366.192s, table=10, n_packets=0,
n_bytes=0, priority=650,dl_type=0x894f,nsh_spi=0x80000d,nsh_si=254
actions=move:NXM_NX_TUN_ID[0..31]->NXM_NX_TUN_ID[0..31],output:"sff1-dpl"
cookie=0xba5eba1100000103, duration=8366.192s, table=10, n_packets=0,
n_bytes=0, priority=650,dl_type=0x894f,nsh_spi=0x80000d,nsh_si=253
actions=move:NXOXM_NSH_C1[]->NXM_NX_TUN_IPV4_DST[],move:NXOXM_NSH_C2[]->NXM_NX_TUN_ID[0..31],output:"sff1-dpl"
cookie=0x14, duration=8366.192s, table=10, n_packets=0, n_bytes=0, priority=5
actions=drop
It is surprising to find that SFF1 receives 0 packets!!! I think this is caused
by the JAVA error presented before.
Since I’m new to ODL and SFC, thus I need your help. Do you have some answers
for this or could you give me some blues to solve this problem?
Thanks very much.
BR,
Qipeng
> On 15 Jan 2019, at 18:36, Brady Johnson <[email protected]> wrote:
>
> Qipeng,
>
> The created-rendered-path API is indeed no longer supported. That API created
> the RSP (Rendered Service Path, which is the actual service chain), but now
> the RSP gets created when the SFP (Service Function Path) is created.
>
> I thought this was already fixed in the sfc103 demo, but apparently not :) I
> submit this patch to fix that and the number of features you reported earlier:
>
> https://git.opendaylight.org/gerrit/79533
> <https://git.opendaylight.org/gerrit/79533>
>
> Regards,
>
> Brady
>
>
>
> On Tue, Jan 15, 2019 at 12:38 AM Qipeng Song <[email protected]
> <mailto:[email protected]>> wrote:
> Hello everyone!
>
> Recently I’m working on sfc103 demo.However I’m still stuck by the following
> POST request failure:
>
> POST
> http://192.168.1.5:8181/restconf/operations/rendered-service-path:create-rendered-path/
>
> <http://192.168.1.5:8181/restconf/operations/rendered-service-path:create-rendered-path/>
> {
> "input": {
> "name": "RSP2",
> "parent-service-function-path": "SFP2",
> "symmetric": "true"
> }
> }
> {"errors":{"error":[{"error-type":"protocol","error-tag":"invalid-value","error-message":"URI
> has bad format. Possible reasons:\n 1.
> \"rendered-service-path:create-rendered-path\" was not found in parent data
> node.\n 2. \"rendered-service-path:create-rendered-path\" is behind mount
> point. Then it should be in format
> \"/yang-ext:mount/rendered-service-path:create-rendered-path\"."}]}}
> Traceback (most recent call last):
> File "/sfc/sfc-demo/sfc103/update_sfc.py", line 160, in <module>
> post(controller, DEFAULT_PORT, get_rendered_service_path_uri(),
> get_rendered_service_path_data(), True)
> File "/sfc/sfc-demo/sfc103/update_sfc.py", line 44, in post
> r.raise_for_status()
> File "/usr/lib/python2.7/dist-packages/requests/models.py", line 840, in
> raise_for_status
> raise HTTPError(http_error_msg, response=self)
> requests.exceptions.HTTPError: 400 Client Error: Bad Request for url:
> http://192.168.1.5:8181/restconf/operations/rendered-service-path:create-rendered-path/
>
> <http://192.168.1.5:8181/restconf/operations/rendered-service-path:create-rendered-path/>
>
> I tried to find solutions in the mail archive. I found something related to
> my problem(I put it at the end of this mail). I want to know whether this
> API(created-rendered-path) is supported again in the latest ODL version? If
> no, do we have some workaround to solve this problem?
>
> Thanks very much.
>
> BR,
> Qipeng
> > From: JaimeCaamaño Ruiz
> > Date: 2018-11-20 22:27
> > To: 喻晶洁
> > CC: sfc-dev
> > Subject: Re: OpenDaylight sfc-demo question
> > Hello
> >
> > The demo is currently not working because it relies in an ODL API
> > (create-rendered-path) that has been removed since fluorine. I will
> > work on it in the following days to fix it.
> >
> > BR
> > Jaime.
> >
> > -----Original Message-----
> > From: 喻晶洁 <yujingjie at fiberhome.com
> > <https://lists.opendaylight.org/mailman/listinfo/sfc-dev>>
> > To: jcaamano at suse.de
> > <https://lists.opendaylight.org/mailman/listinfo/sfc-dev>
> > Subject: OpenDaylight sfc-demo question
> > Date: Tue, 20 Nov 2018 20:10:27 +0800
> >
> > Hi, Dear Jaime,
> > I am studying the Opendaylight/sfc project. When doing an experiment
> > with sfc-demo/sfc103(https://github.com/opendaylight/sfc/tree/master/
> > <https://github.com/opendaylight/sfc/tree/master/>
> > sf
> > c-demo/sfc103), I have a problem as figure below. When I run the
> > python
> > file setup_sfc.py, the RestAPI error always occur.
> > Could you give me some tips?
> > Run setup_sfc.py and show:
> >
> > Run docker-compose and show:
> >
> > ODL:
> >
> >
> >
> > Thanks very much!
>
> _______________________________________________
> sfc-dev mailing list
> [email protected] <mailto:[email protected]>
> https://lists.opendaylight.org/mailman/listinfo/sfc-dev
> <https://lists.opendaylight.org/mailman/listinfo/sfc-dev>
_______________________________________________
sfc-dev mailing list
[email protected]
https://lists.opendaylight.org/mailman/listinfo/sfc-dev
