It included it originally, but removed since updates for diagnostic field are
already inside:
<column name="bfd_status" key="diagnostic">
In case of a problem, set to an error message that reports what the
local BFD session thinks is wrong. The error messages are defined
in section 4.1 of [RFC 5880].
</column>
...
<column name="bfd_status" key="remote_diagnostic">
In case of a problem, set to an error message that reports what the
remote endpoint's BFD session thinks is wrong. The error messages
are defined in section 4.1 of [RFC 5880].
</column>
Ariel
From: Alex Wang <al...@nicira.com<mailto:al...@nicira.com>>
Date: Tuesday, September 2, 2014 11:40 AM
To: "VMware Inc." <atubalt...@vmware.com<mailto:atubalt...@vmware.com>>
Cc: "dev@openvswitch.org<mailto:dev@openvswitch.org>"
<dev@openvswitch.org<mailto:dev@openvswitch.org>>, Bruce Davie
<bda...@vmware.com<mailto:bda...@vmware.com>>
Subject: Re: [ovs-dev] [PATCH] vtep: additions to BFD configuration and status
reporting
On Tue, Sep 2, 2014 at 11:27 AM,
<atubalt...@vmware.com<mailto:atubalt...@vmware.com>> wrote:
It also brings the usage
of the BFD diagnostic keys into line with the recent clarifications
made for OVS.
Does this commit miss this part? did not see any change/line move related to
diagnostic,
_______________________________________________
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev
