Changes between Version 3 and Version 4 of HowTo/CreateOVSTopology

Timestamp:

03/31/14 14:14:19 (10 years ago)

Author:

nriga@bbn.com

Comment:

--

HowTo/CreateOVSTopology

@@ -24 +24 @@
 = OVS commands once the topology is up =
 
-Once your topology is up login to every OVS host in your topology and run the following commands. You will need to run the second command once for every data interface (`eth1, eth2, eth3, `etc). Be careful '''not to add''' the control interface, typical `eth0`. 
+Once your topology is up login to every OVS host in your topology and run the following commands. You will need to run the second command once for every data interface (`eth1, eth2, eth3, `etc). Be careful '''not to add''' the control interface, typically `eth0`. 
 {{{
   sudo ovs-vsctl add-br br-switch
   sudo ovs-vsctl add-port br-switch ethX
 }}}
-'''Note''' do not add the ci
+Check that all the data interfaces have been added:
+{{{
+ sudo ovs-vsctl list-ports br-switch
+}}}
+
+Now you are ready to configure the OVS switch and point it to your controller. Run the following commands:
+{{{
+sudo ovs-vsctl set-fail-mode br-switch secure
+sudo ovs-vsctl set-controller br-switch tcp:<controller-ip>:<controller-port>
+}}}
+
+The first command ensures that only your controller can make forwarding decisions and modify the forwarding table, while the second points the switch to your controller. Make sure to use the control (public IP) of your controller and that your controller is not behind NAT or a firewall. 
+
+'''Tip:''' To test connectivity to your controller from the OVS host try:
+{{{
+telnet <controller_ip> <controller_port>
+}}}
+
+If you get an output like the following all is good:
+{{{
+Trying 2607:f8b0:400c:c03::68...
+Connected to <controller_ip.
+Escape character is '^]'.
+}}}
+