From: Alex Wang
Date: Sat, 26 Oct 2013 00:18:02 +0000 (-0700)
Subject: cfm: Refine the cfm_extended manual.
X-Git-Tag: sliver-openvswitch-2.1.90-1~10^2~172
X-Git-Url: http://git.onelab.eu/?a=commitdiff_plain;h=b1a6083a2df8861405cf3e8d5be1ae82764c6889;hp=0b554f5d5a37754060b24f4e31748addf9a3baf1;p=sliver-openvswitch.git
cfm: Refine the cfm_extended manual.
Commit 348f01e3e3 (cfm: Eight byte MPIDs in extended mode.) allows
eight byte MPIDs when running in extended mode. This commit explains
this change in the vswitch.conf.db.
Signed-off-by: Alex Wang
Signed-off-by: Ben Pfaff
---
diff --git a/vswitchd/vswitch.xml b/vswitchd/vswitch.xml
index 2889a4105..ee1c0586c 100644
--- a/vswitchd/vswitch.xml
+++ b/vswitchd/vswitch.xml
@@ -2060,11 +2060,18 @@
- A Maintenance Point ID (MPID) uniquely identifies each endpoint within
- a Maintenance Association. The MPID is used to identify this endpoint
- to other Maintenance Points in the MA. Each end of a link being
- monitored should have a different MPID. Must be configured to enable
- CFM on this .
+
+ A Maintenance Point ID (MPID) uniquely identifies each endpoint
+ within a Maintenance Association. The MPID is used to identify this
+ endpoint to other Maintenance Points in the MA. Each end of a link
+ being monitored should have a different MPID. Must be configured to
+ enable CFM on this .
+
+
+ According to the 802.1ag specification, MPIDs can only range between
+ [1, 8191]. However, extended mode (see ) supports eight byte MPIDs.
+
@@ -2194,8 +2201,8 @@
with compliant implementations which may be running concurrently on the
network. Furthermore, extended mode increases the accuracy of the
cfm_interval
configuration parameter by breaking wire
- compatibility with 802.1ag compliant implementations. Defaults to
- false
.
+ compatibility with 802.1ag compliant implementations. And extended
+ mode allows eight byte MPIDs. Defaults to false
.