On Oct 12, 2011, at 3:50 PM, Reid Price wrote:
> If you check the man page for ovs-vsctl (search for set-controller), you can
> see that
> the controller target should include a protocol, and be of one of these forms:
>ssl:ip[:port]tcp:ip[:port]unix:file
> Which one is your controller
Hi Mike,
Yep, the switch does initiate the connection.
If you check the man page for ovs-vsctl (search for set-controller), you can
see that
the controller target should include a protocol, and be of one of these
forms:
ssl:ip[:port]tcp:ip[:port]unix:file
Which one is your controller?
2011/10/12 Vladimir Nikolić :
> Yes, you are right.
> It never occured to me that arp timeout could be the problem. Probably
> because we never had that issue with Cisco switches (ours have 4 hours
> default arp timeout) and VMware ESXi internal switch (don't know what is
> default arp timeout).
Y
I guess ovsdbmonitor assumes that ovsdb-client is in /usr/bin, but you
have it in /usr/local/bin. I'll make a note to fix that assumption in
ovsdbmonitor.
On Wed, Oct 12, 2011 at 08:38:01AM +0800, Te-Yen Liu wrote:
> Hi, Ben
> Thanks for your response. I still got "Remote command failed" afte
Yes, you are right.
It never occured to me that arp timeout could be the problem. Probably
because we never had that issue with Cisco switches (ours have 4 hours
default arp timeout) and VMware ESXi internal switch (don't know what is
default arp timeout).
Is it possible the change arp timeout on O
