Additional details:

The call to 

sudo ovs-ofctl monitor switch1 65534 watch: --protocols=OpenFlow13

produces as first output the following everytime:

OFPT_ERROR (xid=0x9): OFPBRC_BAD_VERSION
NXST_FLOW_MONITOR request (xid=0x9):
 id=0 flags=initial,add,delete,modify,actions,own

Until now I could observe only packets from types like the following 

OFPT_ECHO_REQUEST (OF1.3) (xid=0x0): 0 bytes of payload
NXT_PACKET_IN2 (OF1.3) (xid=0x0): cookie=0xa total_len=70 in_port="s1-eth1" 
(via no_match) data_len=70 (unbuffered)
icmp6,vlan_tci=0x0000,dl_src=f6:2d:5c:f7:bd:5e,dl_dst=33:33:00:00:00:02,ipv6_src=fe80::f42d:5cff:fef7:bd5e,ipv6_dst=ff02::2,ipv6_label=0x00000,nw_tos=0,nw_ecn=0,nw_ttl=255,icmp_type=133,icmp_code=0
 icmp6_csum:5e26
OFPT_ECHO_REQUEST (OF1.3) (xid=0x0): 0 bytes of payload
NXT_PACKET_IN2 (OF1.3) (xid=0x0): cookie=0xa total_len=70 in_port="s1-eth2" 
(via no_match) data_len=70 (unbuffered)
icmp6,vlan_tci=0x0000,dl_src=16:a8:ee:4f:df:42,dl_dst=33:33:00:00:00:02,ipv6_src=fe80::14a8:eeff:fe4f:df42,ipv6_dst=ff02::2,ipv6_label=0x00000,nw_tos=0,nw_ecn=0,nw_ttl=255,icmp_type=133,icmp_code=0
 icmp6_csum:b6b8
OFPT_ECHO_REQUEST (OF1.3) (xid=0x0): 0 bytes of payload


>-----Ursprüngliche Nachricht-----
>Von: discuss <ovs-discuss-boun...@openvswitch.org> Im Auftrag von
>Mansuroglu, Zekeriya via discuss
>Gesendet: Mittwoch, 24. Januar 2024 14:24
>An: Adrian Moreno <amore...@redhat.com>; ovs-discuss@openvswitch.org
>Cc: Ilya Maximets <i.maxim...@ovn.org>
>Betreff: Re: [ovs-discuss] Flow not registered in OVSDB flow table
>
>Hi Adrian,
>thank you for your reply. Your suggestion is the same as Ilya's.
>
>I used the following command to monitor the OpenFlow commands modifying
>the flow table:
>
>sudo ovs-ofctl monitor switch1 65534 watch: --protocols=OpenFlow13
>
>But the client doesn't receive any packets even I add and delete some entries 
>in
>the flow table and the changes can be verified with dump-flows command. Only
>packets like the following are received:
>
>OFPT_ECHO_REQUEST (OF1.3) (xid=0x0): 0 bytes of payload
>
>Extensions of the protocols with al the versions other than OpenFlow13 doesn't
>help either.
>
>Can you see if the usage of the client with the command above is correct.
>
>Regards,
>Zekeriya
>
>>-----Ursprüngliche Nachricht-----
>>Von: Adrian Moreno <amore...@redhat.com>
>>Gesendet: Freitag, 19. Januar 2024 13:16
>>An: Mansuroglu, Zekeriya <zekeriya.mansuro...@iis.fraunhofer.de>; ovs-
>>disc...@openvswitch.org
>>Betreff: Re: [ovs-discuss] Flow not registered in OVSDB flow table
>>
>>
>>
>>On 1/18/24 11:00, Mansuroglu, Zekeriya via discuss wrote:
>>> Hi all,
>>>
>>> I’m using ovs through mininet with OpendayLight. The ovs version is 2.13.8
>and
>>> the mininet version is 2.3.0.dev6. I create a network with a single switch 
>>> and
>>> two hosts. After that I create a flow through the nortboubd interface of
>>> opendaylight that works fine. I can also verify with ovs-ofctl that the 
>>> flow is
>>> accepted by the switch. I expected that the flow is also registered in a 
>>> table
>>> in ovsdb, but when I dump the database the flow doesn’t appear anywhere in
>>the
>>> datastore.
>>>
>>> Shouldn’t the flow be registered in one of the table Flow_Table, sFlow or
>>NetFlow?
>>>
>>
>>OpenFlow flows are not stored in the OVSDB. Only configuration is stored
>there.
>>
>>> I aimed to use the ovsdb-client to monitor for changes of the flow table
>>> configurations. As I understood ovsdb-client’s monitor command this should
>>be
>>> doable when changes of the flow configurations lead to changes in ovsdb. Is
>>this
>>> approach realistic?
>>>
>>
>>If you want to monitor the changes in the OpenFlow tables you can use "ovs-
>>ofctl
>>monitor".
>>
>>> Thanks,
>>>
>>> Zekeriya
>>>
>>>
>>> _______________________________________________
>>> discuss mailing list
>>> disc...@openvswitch.org
>>> https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
>>
>>--
>>Adrián Moreno
>
>_______________________________________________
>discuss mailing list
>disc...@openvswitch.org
>https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
_______________________________________________
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

Reply via email to