[ovs-discuss] OVS remote administration

wchunx_ok wchunx_ok at 126.com
Fri Feb 1 03:17:03 UTC 2013


Host1 has the IP address 192.168.0.30 and Host2 has the IP address 192.168.0.224.
I want only Host1 can administrate OVS2 on Host2 remotely.
At 2013-01-31 16:17:31,"Justin Pettit" <jpettit at nicira.com> wrote:
>Please don't drop the list.
>
>Is 192.168.0.30 a valid IP on Host2?  Are you trying to have ovs-vsctl on Host1 connect to Host2?  If so, aren't you expecting Host2 to have the IP address 192.168.0.224?  Unless there's a piece I'm missing, I don't think your configuration makes sense.
>
>--Justin
>
>
>On Jan 31, 2013, at 12:10 AM, wchunx_ok  <wchunx_ok at 126.com> wrote:
>
>> Thank you for you replay.
>> I tried:
>> on Host2    ovs-vsctl set-manager ptcp:6633:192.168.0.30
>> on Host1:  ovs-vsctl --db=tcp:192.168.0.224:6633 show    It also stay in suspend.
>> In /var/log/openvswitch/ovsdb-server.log I found:
>> 
>> 2013-01-31T08:05:10Z|02611|socket_util|ERR|6633:192.168.0.30: bind: Cannot assign requested address
>> 2013-01-31T08:05:10Z|02612|socket_util|ERR|6633:192.168.0.30: bind: Cannot assign requested address
>> 2013-01-31T08:05:10Z|02613|socket_util|ERR|6633:192.168.0.30: bind: Cannot assign requested address
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> At 2013-01-31 15:29:39,"Justin Pettit" <jpettit at nicira.com
>> > wrote:
>> >On Jan 30, 2013, at 7:31 PM, wchunx_ok <
>> wchunx_ok at 126.com
>> > wrote:
>> >
>> >> on Host2 I set:   ovs-vsctl set-manager ptcp:192.168.0.30:6633
>> >
>> >Try reversing the order of the port and IP address when running "ptcp:".  Meaning:
>> >
>> >	ptcp:6633:192.168.0.30
>> >
>> >--Justin
>> >
>> >
>> 
>> 
>> 
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openvswitch.org/pipermail/ovs-discuss/attachments/20130201/c8464401/attachment.html>


More information about the discuss mailing list