You should only need to specify the switch if it's not local. Those commands
should know how to connect to the switch locally. What happens if you just run
the commands like this?
ovs-vsctl set-controller br0
ovs-ofctl show
--Justin
On Apr 24, 2012, at 12:27 AM, Girish Kumar Yerra wrote:
> Hi All,
>
> I am working on openVSwitch with Open flow controllers. I got struck in
> understanding the flow of how the ovs-ofctl utility works. I am not quiet
> clear about how it uses the connection details(tcp:<ip>:port). What details
> we need to mention here. The man page says, it connects to OpenFlow switch.
> What component of OpenVswitch listens for ovs-ofctl commands.
>
> I tried the following things, but it did not work.
>
> -> Configured the OVS to open flow controller where ovs-ofctl will run
> through ovs-vsctl. In this case I am running ovs-ofctl on the same machine.
> #ovs-vsctl set-controller br0 tcp:127.0.0.1:6633
> -> Running the ovs-ofctl from the remote machine. Giving the connections
> details the machine, where the OVS is running.
> #ovs-ofctl show tcp:127.0.0.1:6633
> -> I am getting an error saying "ovs-ofctl:connecting to tcp:127.0.0.1:6633
> (Connection refused)"
>
> Any help in this regard is greatly appreciated.
>
> --
> Thanks & Regards,
> Girish
>
> _______________________________________________
> dev mailing list
> dev@openvswitch.org
> http://openvswitch.org/mailman/listinfo/dev
_______________________________________________
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev
