[ovs-dev] Hardware vtep manager table

Syed Ashifur Rahaman ashifursyed at gmail.com
Wed Jan 4 16:56:26 UTC 2017


Forwarding it to Dev mailing list in case someone has any inputs.

I connected my hardware vtep(ovs 2.5.0) to controller. The controller
brings the connectivity as UP and sends down update for different
tables.

But in my hardware vtep, I don't see the is_connected field in Manager
table updated to true.

Manager table

_uuid                                inactivity_probe is_connected
max_backoff other_config status target
------------------------------------ ---------------- ------------
----------- ------------ ------ -------------------------
c1b23893-229f-4edf-ad7e-19c589679511 []               false        []
        {}           {}     "ssl:10.133.225.211:6640"
290d88fc-9238-47ed-bd46-8947492cdb89 []               false        []
        {}           {}     "ssl:10.133.225.212:6640"


Also, when I check the logs, I see the transition to IDLE and ACTIVE
happening continuously. Do we expect controller to send

some messages periodically? Any inputs?

017-01-02T05:06:33.016Z|526975|poll_loop|DBG|wakeup due to 0-ms
timeout at lib/stream-ssl.c:731 (0% CPU usage)
2017-01-02T05:06:33.421Z|526976|poll_loop|DBG|wakeup due to 405-ms
timeout at ovsdb/ovsdb-server.c:189 (0% CPU usage)
2017-01-02T05:06:38.021Z|526977|poll_loop|DBG|wakeup due to 4600-ms
timeout at lib/reconnect.c:620 (0% CPU usage)
2017-01-02T05:06:38.021Z|526978|reconnect|DBG|ssl:10.133.225.211:6640:
idle 5005 ms, sending inactivity probe
2017-01-02T05:06:38.021Z|526979|reconnect|DBG|ssl:10.133.225.211:6640:
entering IDLE
2017-01-02T05:06:38.021Z|526980|jsonrpc|DBG|ssl:10.133.225.211:6640:
send request, method="echo", params=[], id="echo"
2017-01-02T05:06:38.021Z|526981|stream_ssl|DBG|client12-->ssl:10.133.225.211:6640
type 256 (5 bytes)
2017-01-02T05:06:38.023Z|526982|poll_loop|DBG|wakeup due to [POLLIN]
on fd 17 (10.133.226.47:53646<->10.133.225.211:6640) at
lib/stream-ssl.c:729 (0% CPU usage)
2017-01-02T05:06:38.023Z|526983|stream_ssl|DBG|client12<--ssl:10.133.225.211:6640
type 256 (5 bytes)
2017-01-02T05:06:38.024Z|526984|jsonrpc|DBG|ssl:10.133.225.211:6640:
received reply, result=[], id="echo"
2017-01-02T05:06:38.024Z|526985|reconnect|DBG|ssl:10.133.225.211:6640:
entering ACTIVE


I set only the target field in the Manager table. Is it necessary to
set other fields(inactivity_probe, max_backoff)?

when does is_connected field get set to true?

-ashifur


More information about the dev mailing list