Changes between Version 2 and Version 3 of Internal/OpenFlow/Firmware
- Timestamp:
- Jun 26, 2009, 5:43:49 AM (15 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Internal/OpenFlow/Firmware
v2 v3 1 1 = Flashing NEC Switches = 2 2 3 NEC provides two models of switch that supports OpenFlow, the IP8800/S3640-24T2XW and the IP8800/S3640-48T2XW.4 The switches must be manually flashed with OpenFlow capable firmware to make them OpenFlow capable. This page explains how to flash the switch to make itOpenFlow capable.3 NEC provides two models of switch that supports !OpenFlow, the IP8800/S3640-24T2XW and the IP8800/S3640-48T2XW. 4 The switches must be manually flashed with !OpenFlow capable firmware to make them !OpenFlow capable. This page explains how to flash the switch to make it !OpenFlow capable. 5 5 6 6 … … 8 8 The SD card must contain the following for the switch to be able to boot off of it: 9 9 10 * OpenFlow capable firmware (k.img)11 * Software license for OpenFlow capable firmware (license.dat)12 * Configuration file for OpenFlow specific features (openflow.conf)10 * !OpenFlow capable firmware (k.img) 11 * Software license for !OpenFlow capable firmware (license.dat) 12 * Configuration file for !OpenFlow specific features (openflow.conf) 13 13 14 14 15 15 == Overview == 16 These are the general steps required to get the switch up and running as an OpenFlow device:16 These are the general steps required to get the switch up and running as an !OpenFlow device: 17 17 18 18 1. Create VLANs … … 56 56 == Creating the openflow.conf file == 57 57 58 openflow.conf is a simple text file that contains OpenFlow specific configurations. The following are the three parameters you can specify in the file.58 openflow.conf is a simple text file that contains !OpenFlow specific configurations. The following are the three parameters you can specify in the file. 59 59 60 60 === `no-save` === … … 62 62 63 63 === `double-wide-mode` === 64 When specified, all ten OpenFlow specific header fields will be matched.64 When specified, all ten !OpenFlow specific header fields will be matched. 65 65 66 66 === `setvsi` === 67 Creates an instance of a virtual switch. This is the only OpenFlow parameter you can also use as a command from the CLI, but must be followed by several parameters: 67 '' more detailed use of this parameter can be found in the [wiki:Documentation/OpenFlow/VirtualSwitch virtual switch] article. '' 68 69 Creates an instance of a [wiki:Documentation/OpenFlow/VirtualSwitch virtual switch]. You can also use this configuration command from the CLI. 70 71 `setvsi` is followed by several parameters: 68 72 69 73 `setvsi <vlan id> <list of ports> <tcp|ssl> <controller ip address[:port]> [<cacert> <my cert> <my private key>] [dpid <datapath id>] [hwlimit <max entrynum>] [max-backoff <backoff time>] [echo-interval <interval time>]` … … 73 77 `setvsi <vlan id> <list of ports> <tcp|ssl> <controller ip address[:port]> [dpid <datapath id>]` 74 78 79 80 81 == Example openflow.conf file == 82 openflow.conf resides in /mnt/ once the switch is booted. 83 84 {{{ 85 > cat /mnt/openflow.conf 86 double-wide-mode 87 88 setvsi 1 1,2,3,4,9.1 tcp 172.16.4.180 dpid 0x0123456789ab 89 setvsi 2 5-8,9.2 tcp 172.16.4.64 dpid 0x01234567abcd 90 setvsi 3 15-18,19.2 tcp 172.16.4.64 dpid 0x01234567abcd 91 }}} 92 93 Note that the `no-save` option is omitted to make editing from the CLI easier. 94