On 11/8/2018 3:48 PM, Siva Teja ARETI wrote:


On Thu, Nov 8, 2018 at 6:30 PM Gregory Rose <[email protected] <mailto:[email protected]>> wrote:

    On 11/7/2018 4:14 PM, Siva Teja ARETI wrote:


    On Wed, Nov 7, 2018 at 6:43 PM Gregory Rose <[email protected]
    <mailto:[email protected]>> wrote:

        On 11/6/2018 3:17 PM, Gregory Rose wrote:
        >
        > I see.  It appears you are right and I misread the
        documentation. OK,
        > l'll investigate further then.
        >
        > - Greg
        >
        >

        Siva,

        I am still looking into this but wanted to update you on my
        status.

        I am seeing problems with the vxlan local_ip option myself. 
        Either I
        don't actually understand the docs
        and examples I've looked at or else there is a real bug but
        given the
        reports from  you and Marcus (in
        the email thread you first referenced) I think there must be
        some issue.

        Flavio mentioned that it might be an MTU issue but the
        testing I'm doing
        would not be affected by
        the MTU so I think there is something else.

        Hopefully I can make some progress on this soon - I'll let
        you know.

        Thanks,

        - Greg

    Thanks for the update.

    Siva,

    When you see the error condition with the local_ip option on vxlan
    can you provide me the output of
    this command?

    *# ip -s link show vxlan_sys_4789*
    70: vxlan_sys_4789: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 65470
    qdisc noqueue master ovs-system state UNKNOWN mode DEFAULT group
    default qlen 1000
        link/ether 0e:9b:58:4a:6e:44 brd ff:ff:ff:ff:ff:ff
        RX: bytes  packets  errors  dropped overrun mcast
        0          0        0       0       0       0
        TX: bytes  packets  errors  dropped carrier collsns
        0          0        99      8       99      0

Hi Greg,

Here is the output.

[root@vm1 ~]# ip -s link show vxlan_sys_4789
27: vxlan_sys_4789: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 65000 qdisc noqueue master ovs-system state UNKNOWN mode DEFAULT qlen 1000
    link/ether ca:8f:0d:13:08:1f brd ff:ff:ff:ff:ff:ff
    RX: bytes  packets  errors  dropped overrun mcast
    0          0        0       0       0       0
    TX: bytes  packets  errors  dropped carrier collsns
    3666796    130957   0       0       0       0

 Siva Teja.

    It will help me understand which error you're encountering.

    Thanks!

    - Greg


Well then obviously I still have errors in my own setup.

Back to the drawing board but I think it's a routing issue in my case.

Thanks!

_______________________________________________
discuss mailing list
[email protected]
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

Reply via email to