[ovs-dev] [PATCH] Fix missing system-id in INSTALL.Docker
Hui Kang
kangh at us.ibm.com
Mon Oct 3 20:43:20 UTC 2016
"dev" <dev-bounces at openvswitch.org> wrote on 10/03/2016 03:57:21 PM:
> From: Ben Pfaff <blp at ovn.org>
> To: Hui Kang <hkang.sunysb at gmail.com>
> Cc: dev at openvswitch.org
> Date: 10/03/2016 03:57 PM
> Subject: Re: [ovs-dev] [PATCH] Fix missing system-id in INSTALL.Docker
> Sent by: "dev" <dev-bounces at openvswitch.org>
>
> On Mon, Oct 03, 2016 at 03:30:51PM -0400, Hui Kang wrote:
> > Signed-off-by: Hui Kang <kangh at us.ibm.com>
> > ---
> > INSTALL.Docker.md | 8 ++++++--
> > 1 file changed, 6 insertions(+), 2 deletions(-)
> >
> > diff --git a/INSTALL.Docker.md b/INSTALL.Docker.md
> > index b62922d..5cb49d0 100644
> > --- a/INSTALL.Docker.md
> > +++ b/INSTALL.Docker.md
> > @@ -69,6 +69,8 @@ gets cleared. It is harmless to run it again inany
case.)
> > $LOCAL_IP in the below command is the IP address via which other hosts
> > can reach this host. This acts as your local tunnel endpoint.
> >
> > +$SYSTEM_ID in the below command is the unique identifier for the
> docker host.
> > +
> > $ENCAP_TYPE is the type of tunnel that you would like to use for
overlay
> > networking. The options are "geneve" or "stt". (Please note that
your
> > kernel should have support for your chosen $ENCAP_TYPE. Both geneve
> > @@ -79,8 +81,10 @@ support in upstream Linux. You can verify
> whether you have the support in your
> > kernel by doing a "lsmod | grep $ENCAP_TYPE".)
> >
> > ```
> > -ovs-vsctl set Open_vSwitch . external_ids:ovn-remote="tcp:
> $CENTRAL_IP:6642" \
> > - external_ids:ovn-nb="tcp:$CENTRAL_IP:6641" external_ids:ovn-
> encap-ip=$LOCAL_IP external_ids:ovn-encap-type="$ENCAP_TYPE"
> > +ovs-vsctl set Open_vSwitch . external-ids:system-id=$SYSTEM_ID \
> > + external_ids:ovn-remote="tcp:$CENTRAL_IP:6642" \
> > + external_ids:ovn-nb="tcp:$CENTRAL_IP:6641" \
> > + external_ids:ovn-encap-ip=$LOCAL_IP external_ids:ovn-encap-
> type="$ENCAP_TYPE"
>
> Usually the OVS system startup script should ensure that the system has
> a system-id. You don't see that behavior in your environment?
No. I followed the instruction in [1] and [2] to setup the OVN. Without
system-id in the ovs-vsctl command, I saw the following message and
"ovn-sbctl show" does not show any connected chassis. With the system-id
in the command, "ovn-sbctl show" outputs correctly.
2016-10-03T19:10:56.892Z|00008|main|WARN|'system-id' in Open_vSwitch
database is missing.
2016-10-03T19:11:11.902Z|00009|main|WARN|Dropped 6 log messages in last 15
seconds (most recently, 5 seconds ago) due to excessive rate
2016-10-03T19:11:11.902Z|00010|main|WARN|'system-id' in Open_vSwitch
database is missing.
2016-10-03T19:11:26.912Z|00011|main|WARN|Dropped 6 log messages in last 15
seconds (most recently, 5 seconds ago) due to excessive rate
2016-10-03T19:11:26.912Z|00012|main|WARN|'system-id' in Open_vSwitch
database is missing.
2016-10-03T19:11:41.927Z|00013|main|WARN|Dropped 5 log messages in last 15
seconds (most recently, 5 seconds ago) due to excessive rate
Thanks.
- Hui
> _______________________________________________
> dev mailing list
> dev at openvswitch.org
> http://openvswitch.org/mailman/listinfo/dev
More information about the dev
mailing list