Re: [ovs-dev] [PATCH] bfd: always export remote_state and remote_diagnostic to OVSDB

2015-10-22 Thread Andy Zhou
On Thu, Oct 22, 2015 at 5:56 PM, Justin Pettit wrote: > >> On Oct 22, 2015, at 11:08 AM, Andy Zhou wrote: >> >> @@ -321,11 +321,8 @@ bfd_get_status(const struct bfd *bfd, struct smap *smap) >> smap_add(smap, "state", bfd_state_str(bfd->state)); >> smap_add(smap, "diagnostic", bfd_diag_str

Re: [ovs-dev] [PATCH] bfd: always export remote_state and remote_diagnostic to OVSDB

2015-10-22 Thread Justin Pettit
> On Oct 22, 2015, at 11:08 AM, Andy Zhou wrote: > > @@ -321,11 +321,8 @@ bfd_get_status(const struct bfd *bfd, struct smap *smap) > smap_add(smap, "state", bfd_state_str(bfd->state)); > smap_add(smap, "diagnostic", bfd_diag_str(bfd->diag)); > smap_add_format(smap, "flap_count", "%"P

[ovs-dev] [PATCH] bfd: always export remote_state and remote_diagnostic to OVSDB

2015-10-22 Thread Andy Zhou
RFC 5880 specified bfd.RemoteSessionState as one of the state variables. In OVS implementation, this value is exported to OVSDB's BFD status column of the interface table, as one of the map elements, with the key of 'remote_state'. It can be surprising when the 'remote_state' map element disappea