From: Ben Pfaff Date: Tue, 29 Oct 2013 20:01:07 +0000 (-0700) Subject: vtep: Bring BFD specification in vtep.xml into sync with OVS. X-Git-Url: http://git.cascardo.eti.br/?p=cascardo%2Fovs.git;a=commitdiff_plain;h=23f781e47bacce6866cad9248e2c01c44840cfec vtep: Bring BFD specification in vtep.xml into sync with OVS. A number of new key-value pairs have been added to the bfd and bfd_status columns of the OVS schema since the VTEP schema was created. To aid interoperability between OVS instances and VTEPs, this patch brings the VTEP schema into line with that of OVS. CC: Bruce Davie Signed-off-by: Ben Pfaff --- diff --git a/vtep/vtep.xml b/vtep/vtep.xml index 9fd7495fc..39404790c 100644 --- a/vtep/vtep.xml +++ b/vtep/vtep.xml @@ -644,11 +644,12 @@ encapsulations to be introduced later.

+

BFD, defined in RFC 5880, allows point to point detection of connectivity failures by occasional transmission of BFD control - messages. + messages. VTEPs are expected to implement BFD.

@@ -657,60 +658,135 @@ specifies the rate at which it expects to receive control messages, and the rate at which it's willing to transmit them. An endpoint which fails to receive BFD control messages for a period of three - times the expected reception rate, will signal a connectivity + times the expected reception rate will signal a connectivity fault. In the case of a unidirectional connectivity issue, the system not receiving BFD control messages will signal the problem - to its peer in the messages is transmists. + to its peer in the messages it transmits.

- - The minimum rate, in milliseconds, at which this BFD session is - willing to receive BFD control messages. The actual rate may slower - if the remote endpoint isn't willing to transmit as quickly as - specified. Defaults to 1000. - - - - The minimum rate, in milliseconds, at which this BFD session is - willing to transmit BFD control messages. The actual rate may be - slower if the remote endpoint isn't willing to receive as quickly as - specified. Defaults to 100. - - - - Concatenated path down may be used when the local system should not - have traffic forwarded to it for some reason other than a connectivty - failure on the interface being monitored. The local BFD session will - notify the remote session of the connectivity problem, at which time - the remote session may choose not to forward traffic. Defaults to - false. - - - - State of the BFD session. One of ADMIN_DOWN, - DOWN, INIT, or UP. - - - - True if the BFD session believes this may be - used to forward traffic. Typically this means the local session is - up, and the remote system isn't signalling a problem such as - concatenated path down. - - - - A short message indicating what the BFD session thinks is wrong in - case of a problem. - - - - State of the remote endpoint's BFD session. - - - - A short message indicating what the remote endpoint's BFD session - thinks is wrong in case of a problem. - +

+ A hardware VTEP is expected to use BFD to determine reachability of + devices at the end of the tunnels with which it exchanges data. This + can enable the VTEP to choose a functioning service node among a set of + service nodes providing high availability. It also enables the NVC to + report the health status of tunnels. +

+ +

+ In most cases the BFD peer of a hardware VTEP will be an Open vSwitch + instance. The Open vSwitch implementation of BFD aims to comply + faithfully with the requirements put forth in RFC 5880. Open vSwitch + does not implement the optional Authentication or ``Echo Mode'' + features. +

+ + +

+ A controller sets up key-value pairs in the + column to enable and configure BFD. +

+ + + True to enable BFD on this . + + + + The shortest interval, in milliseconds, at which this BFD session + offers to receive BFD control messages. The remote endpoint may + choose to send messages at a slower rate. Defaults to + 1000. + + + + The shortest interval, in milliseconds, at which this BFD session is + willing to transmit BFD control messages. Messages will actually be + transmitted at a slower rate if the remote endpoint is not willing to + receive as quickly as specified. Defaults to 100. + + + + An alternate receive interval, in milliseconds, that must be greater + than or equal to . The + implementation switches from to when there is no obvious incoming + data traffic at the interface, to reduce the CPU and bandwidth cost + of monitoring an idle interface. This feature may be disabled by + setting a value of 0. This feature is reset whenever or + changes. + + + + True to consider the interface capable of packet I/O as long as it + continues to receive any packets (not just BFD packets). This + prevents link congestion that causes consecutive BFD control packets + to be lost from marking the interface down. + + + + Set to true to notify the remote endpoint that traffic should not be + forwarded to this system for some reason other than a connectivty + failure on the interface being monitored. The typical underlying + reason is ``concatenated path down,'' that is, that connectivity + beyond the local system is down. Defaults to false. + + + + Set to true to make BFD accept only control messages with a tunnel + key of zero. By default, BFD accepts control messages with any + tunnel key. + + + + Set to an Ethernet address in the form + xx:xx:xx:xx:xx:xx + to set the MAC used as destination for transmitted BFD packets and + expected as destination for received BFD packets. The default is + 00:23:20:00:00:01. + + + + +

+ The VTEP sets key-value pairs in the + column to report the status of BFD on this interface. When BFD is + not enabled, with , the switch clears + all key-value pairs from . +

+ + + Reports the state of the BFD session. The BFD session is fully + healthy and negotiated if UP. + + + + Reports whether the BFD session believes this may be used to forward traffic. Typically + this means the local session is signaling UP, and the + remote system isn't signaling a problem such as concatenated path + down. + + + + In case of a problem, set to a short message that reports what the + local BFD session thinks is wrong. + + + + Reports the state of the remote endpoint's BFD session. + + + + In case of a problem, set to a short message that reports what the + remote endpoint's BFD session thinks is wrong. + +