From patchwork Sat Nov 14 01:01:11 2015 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Ariel Tubaltsev X-Patchwork-Id: 544702 Return-Path: X-Original-To: incoming@patchwork.ozlabs.org Delivered-To: patchwork-incoming@bilbo.ozlabs.org Received: from archives.nicira.com (unknown [IPv6:2600:3c00::f03c:91ff:fe6e:bdf7]) by ozlabs.org (Postfix) with ESMTP id 77CA31413F9 for ; Sat, 14 Nov 2015 12:01:23 +1100 (AEDT) Authentication-Results: ozlabs.org; dkim=fail reason="signature verification failed" (2048-bit key; unprotected) header.d=gmail.com header.i=@gmail.com header.b=VBSayQAo; dkim-atps=neutral Received: from archives.nicira.com (localhost [127.0.0.1]) by archives.nicira.com (Postfix) with ESMTP id 2418F22C40E; Fri, 13 Nov 2015 17:01:22 -0800 (PST) X-Original-To: dev@openvswitch.org Delivered-To: dev@openvswitch.org Received: from mx1e4.cudamail.com (mx1.cudamail.com [69.90.118.67]) by archives.nicira.com (Postfix) with ESMTPS id B782922C409 for ; Fri, 13 Nov 2015 17:01:20 -0800 (PST) Received: from bar5.cudamail.com (unknown [192.168.21.12]) by mx1e4.cudamail.com (Postfix) with ESMTPS id 11D781E01D3 for ; Fri, 13 Nov 2015 18:01:20 -0700 (MST) X-ASG-Debug-ID: 1447462879-09eadd03664216e0001-byXFYA Received: from mx1-pf2.cudamail.com ([192.168.24.2]) by bar5.cudamail.com with ESMTP id wCqsieE3PIKtVC5e (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 13 Nov 2015 18:01:19 -0700 (MST) X-Barracuda-Envelope-From: tubaltzev@gmail.com X-Barracuda-RBL-Trusted-Forwarder: 192.168.24.2 Received: from unknown (HELO mail-pa0-f48.google.com) (209.85.220.48) by mx1-pf2.cudamail.com with ESMTPS (RC4-SHA encrypted); 14 Nov 2015 01:01:18 -0000 Received-SPF: pass (mx1-pf2.cudamail.com: SPF record at _netblocks.google.com designates 209.85.220.48 as permitted sender) X-Barracuda-RBL-Trusted-Forwarder: 209.85.220.48 Received: by padhx2 with SMTP id hx2so115532477pad.1 for ; Fri, 13 Nov 2015 17:01:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:subject:date:message-id; bh=RL4QUAR4jpGUKRiTJ+uAkIxhVfXEB5XiohQV5COMjRA=; b=VBSayQAoLx4J9fBbZNLaSJp62fcI51RE1AsZKwtidKZl1xClnVBbp/Muo1gYYOgHW6 PVY5F6V2UCe37SRugBrZLdup4c8B19i5mnnlQsiw9YedFXNyIYcXKOf01rQFzywPJQs+ tWozAfzYERmltE349P7uj3z6HP4oF/l0p7e5H4Yn6A21GKJAoSJcNEodjvMq0ODTCZdc VZjiIs/i3I6Z33ptA4vjEv2ednVSRtU1YkPedZYq0AaM+JLymlREIsDDru49v/9fcU2n seD2lWFfykmmdOggoXWFlJh2TAPOsTcYl1Jk6Rm8HcaqYHgihW3T6MR7ZVCwbb6BoAow prJQ== X-Received: by 10.66.101.2 with SMTP id fc2mr36693908pab.139.1447462878063; Fri, 13 Nov 2015 17:01:18 -0800 (PST) Received: from qa1.intranet.com ([71.202.163.181]) by smtp.gmail.com with ESMTPSA id h10sm22685467pat.7.2015.11.13.17.01.17 (version=TLSv1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Fri, 13 Nov 2015 17:01:17 -0800 (PST) X-CudaMail-Envelope-Sender: tubaltzev@gmail.com X-Barracuda-Apparent-Source-IP: 71.202.163.181 From: Ariel Tubaltsev To: dev@openvswitch.org X-CudaMail-MID: CM-E2-1112103595 X-CudaMail-DTE: 111315 X-CudaMail-Originating-IP: 209.85.220.48 Date: Fri, 13 Nov 2015 17:01:11 -0800 X-ASG-Orig-Subj: [##CM-E2-1112103595##][PATCH] HW VTEP Schema: update Tunnel table definition Message-Id: <1447462871-32642-1-git-send-email-tubaltzev@gmail.com> X-Mailer: git-send-email 2.3.8 (Apple Git-58) X-GBUdb-Analysis: 0, 209.85.220.48, Ugly c=0.484386 p=-0.527273 Source Normal X-MessageSniffer-Rules: 0-0-0-15401-c X-Barracuda-Connect: UNKNOWN[192.168.24.2] X-Barracuda-Start-Time: 1447462879 X-Barracuda-Encrypted: DHE-RSA-AES256-SHA X-Barracuda-URL: https://web.cudamail.com:443/cgi-mod/mark.cgi X-Virus-Scanned: by bsmtpd at cudamail.com X-Barracuda-BRTS-Status: 1 X-Barracuda-Spam-Score: 0.60 X-Barracuda-Spam-Status: No, SCORE=0.60 using per-user scores of TAG_LEVEL=3.5 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=4.0 tests=BSF_SC5_MJ1963, DKIM_SIGNED, RDNS_NONE X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.3.24376 Rule breakdown below pts rule name description ---- ---------------------- -------------------------------------------------- 0.00 DKIM_SIGNED Domain Keys Identified Mail: message has a signature 0.10 RDNS_NONE Delivered to trusted network by a host with no rDNS 0.50 BSF_SC5_MJ1963 Custom Rule MJ1963 Cc: Ariel Tubaltsev Subject: [ovs-dev] [PATCH] HW VTEP Schema: update Tunnel table definition X-BeenThere: dev@openvswitch.org X-Mailman-Version: 2.1.16 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , MIME-Version: 1.0 Errors-To: dev-bounces@openvswitch.org Sender: "dev" vtep/vtep.xml : Tunnel table definitions were reviewed against latest OVS schema. Relevant changes taken into HW VTEP schema. XML formatting of Tunnel table corrected Signed-off-by: Ariel Tubaltsev --- vtep/vtep.xml | 120 +++++++++++++++++++++++++++++----------------------------- 1 file changed, 61 insertions(+), 59 deletions(-) diff --git a/vtep/vtep.xml b/vtep/vtep.xml index 8ca9f26..b5645a1 100644 --- a/vtep/vtep.xml +++ b/vtep/vtep.xml @@ -357,7 +357,7 @@

- In most cases the BFD peer of a hardware VTEP will be an Open vSwitch + In many 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'' @@ -413,8 +413,8 @@

- True to enable BFD on this tunnel. - The default is False. + True to enable BFD on this . If not + specified, BFD will not be enabled by default. 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. + than or equal to . The + implementation should switch from + to when there is no obvious + incoming data traffic at the tunnel, to reduce the CPU and bandwidth + cost of monitoring an idle tunnel. 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. + When true, traffic received on the + is used to indicate the capability of packet I/O. + BFD control packets are still transmitted and received. At least one + BFD control packet must be received every + 100 * amount of time. + Otherwise, even if traffic is received, the + will be false. @@ -468,59 +471,58 @@ - -

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

+ +

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

- - Set to true if the BFD session has been successfully - enabled. Set to false if the VTEP cannot support BFD or has - insufficient resources to enable BFD on this tunnel. The NVC - will disable the BFD monitoring on the other side of the tunnel - once this value is set to false. - + + Set to true if the BFD session has been successfully enabled. + Set to false if the VTEP cannot support BFD or has insufficient + resources to enable BFD on this tunnel. The NVC will disable + the BFD monitoring on the other side of the tunnel once this + value is set to false. + - - Reports the state of the BFD session. The BFD session is fully - healthy and negotiated if UP. - + Reports the state of the BFD session. The BFD session is fully + healthy and negotiated if UP. + - - Reports whether the BFD session believes this tunnel - 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. - + + 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 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]. - + + A diagnostic code specifying the local system's reason for the + last change in session state. The error messages are defined in + section 4.1 of [RFC 5880]. + - - Reports the state of the remote endpoint's BFD session. - + Reports the state of the remote endpoint's BFD session. + - - 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]. - + + A diagnostic code specifying the remote system's reason for the + last change in session state. The error messages are defined in + section 4.1 of [RFC 5880]. + - - A short message providing further information about the BFD status - (possibly including reasons why BFD could not be enabled). - + + A short message providing further information about the BFD status + (possibly including reasons why BFD could not be enabled). +