Changes between Version 10 and Version 11 of Internal/OpenFlow/Firmware

Timestamp:

Aug 8, 2011, 10:22:31 PM (13 years ago)

Author:

akoshibe

Comment:

—

Internal/OpenFlow/Firmware

@@ -168 +168 @@
  2. Rename k.img to something else so it is not recognized as a bootable image.
 
-=== 2. !OpenFlow configurations ===
+=== 2. !OpenFlow configuration commands ===
 The !OpenFlow components of the new firmware have been integrated into the CLI. There are contexts for !OpenFlow (conveniently called `openflow`) under the `show` and `configure` contexts.
 
@@ -225 +225 @@
 }}}
 
+=== 3. Configuration example ===
+The following is a virtual switch on an IP8800 running the new firmware:
+{{{
+sw-gp(config)# openflow openflow-id 1
+!sw-gp(config-of)# sh                 
+openflow openflow-id 1
+  controller controller-name nox-gp 1 172.16.0.240 port 6633
+  connect timeout 10
+  connect timeout retry 3
+  openflow-interface gigabitethernet 0/17-32, gigabitethernet 0/48
+  l2-inband-secure-channel vlan 1 gigabitethernet 0/48
+  enable
+}}}
+
+The basic steps are the following:
+ 1. A real or virtual !OpenFlow switch can be instantiated with the `openflow openflow-id [id] context. [id] is a value of up to 16.
+ 2. As seen above, step 1 takes you into the `(config-of)` context. Once an !OpenFlow switch (VSI) is instantiated, ports are added to it with the `openflow-interface [add]` context, which follows similar syntax to trunk configurations.
+ 3. If a port that is part of a VSI is to be used as the control channel, specify it with the `l2-inband-secure-channel` context. You must specify the VLAN the controller is in.
+ 4. The controller is specified with the `controller` context. The command will force you to give a human-readable name to the controller (nox-gp in the example above), and an IP address and port where the controller process can be reached.
+ 5. The switch must be enabled with the `enable` option.
+
+In addition to the basics, several specific aspects of the VSI can be configured. The above example shows the timeout parameters of the VSI have been changed so that:
+ * `connect timeout 10` = The VSI detects controller disconnection in 10 seconds, and 
+ * `connect timeout retry 3` = When disconnected, the VSI attempts to re-connect with the controller thrice before giving up. 
+
+The full list of knobs are shown in the previous section, third block quote. 
+
 
 == SSL stuff ==