Changes between Version 5 and Version 6 of Internal/OpenFlow/Firmware


Ignore:
Timestamp:
Jul 11, 2009, 9:17:26 PM (15 years ago)
Author:
akoshibe
Comment:

—

Legend:

Unmodified
Added
Removed
Modified

  • Internal/OpenFlow/Firmware

    v5 v6  
    11= Flashing NEC Switches =
    22
     3NEC provides two models of switch that supports !OpenFlow, the IP8800/S3640-24T2XW and the IP8800/S3640-48T2XW. [[BR]]
     4The switches must be manually flashed with !OpenFlow capable firmware to make them !OpenFlow capable. NEC provides instructions on flashing the switch, but there are a few things that are useful to know that they don't mention. This article is a summary of the instructions, with those unmentioned caveats thrown in.   
    35
    4 NEC provides two models of switch that supports !OpenFlow, the IP8800/S3640-24T2XW and the IP8800/S3640-48T2XW.
    5 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.
    6 
    7 
    8 == Overview ==
    9 This article is part summary of the !OpenFlow manual NEC provides with the switches, and a documentation of some details that might be worth mentioning.   
    10 
    11 
    12 == Materials Needed ==
     6=== Materials Needed ===
    137The SD card must contain the following for the switch to be able to boot off of it:
    148
    … …  
    1711 * Configuration file for !OpenFlow specific features (openflow.conf)
    1812
     13In order to use SSL for the secure channel between the switch and the controller, the following three should also be on the card:
    1914
    20 == General steps ==
     15 * CA certificate (ca_cert.pem)
     16 * Certificate for the switch (sw_cert.pem)
     17 * secret key for switch (sw_key.pem)
     18
     19=== General steps ===
    2120These are the general steps required to get the switch up and running as an !OpenFlow device:
    2221 
    2322 1. Log into switch (this assumes you have already configured everything so you can talk to your switch)
     23 1. Disable Spanning Tree Protocol (command `spanning-tree disable` under configuration prompt)
    2424 1. Create VLANs
    2525 1. Create openflow.conf
    26  1. Save k.img, license.dat, and openflow.conf onto SD card
     26 1. Save k.img, license.dat, openflow.conf, and if using SSL, the .pem files, onto SD card
    2727 1. Cold boot switch off of SD card (the manual says a reboot is sufficient, but this was not the case)
    2828 1. Enjoy
    2929
    30 The VLANs and virtual switches can also be configured after the switch has been booted off of the !OpenFlow firmware. More info on this can be found on the article about [wiki:Documentation/OpenFlow/VirtualSwitch virtual switches].
     30== The Caveats ==
    3131
    32 = The Caveats =
    33 Although the manual does a pretty good job at explaining how to do things, some things might be worth mentioning. The following are a summary of things that might be sort of important.
    34 
    35 == The SD card ==
     32=== The SD card ===
    3633NEC provides a certified SD card with the switch. They recommend that you only use this card.
    3734
    38 == The License ==
    39 Each license is specific to a certain switch; a switch will not boot properly if the license is missing, misnamed, or if the license for the wrong switch is used.
     35=== The License ===
     36Each license is specific to a certain switch; a switch will not boot properly if the license is missing, misnamed, or if the license for the wrong switch is used. The license must always be named "license.dat" for the switch to boot properly.
    4037
    41 Sometimes the license is labeled with a specific switch's serial number instead of being labeled "license.dat." In that case, the serial number can be found on a silver sticker on the front of the switch, or by typing `show version` at the terminal:
     38
     39When you get more than one license, each license will be named by the serial number of the switch you're supposed to use the license on instead of being named "license.dat." In that case, the serial number can be found on a silver sticker on the front of the switch, or by typing `show version` at the terminal:
    4240
    4341{{{
    … …  
    5654In this case, "WA03CL48T2XWS0E0693K007" (in the first entry under "H/W: Main board) is the serial number and matches the name of the correct license for this specific switch. 
    5755
    58 '''Note: ''' If the license is named after the switch's serial number, the license must be renamed to "license.dat" before saving onto the SD card .
    59 
    6056
    6157== openflow.conf ==
    6258
    63 openflow.conf is a text file that contains configurations specific to !OpenFlow switching, or [wiki:Documentation/OpenFlow/VirtualSwitch virtual switching]. The details about the commands that can be used in the file are on pages 12-13 of the NEC manual. Following are a few notes about the commands.
     59openflow.conf is a text file that contains configurations specific to [wiki:Documentation/OpenFlow/VirtualSwitch virtual switching]. The details about the commands that can be used in the file are on pages 12-13 of the NEC manual. Following are a few notes about the commands.
    6460
    6561=== `no-save` ===
    … …  
    8076`setvsi <vlan id> <list of ports> <tcp|ssl> <controller ip address[:port]> [dpid <datapath id>]`
    8177
    82 
    83 == Example openflow.conf file ==
    84 
    85 openflow.conf resides in /mnt/ . Just `cat /mnt/openflow.conf` to see the file. 
     78when booted, openflow.conf lives in /mnt/. This is the first functional openflow.conf file that was used on the switch:
    8679
    8780{{{
    88 double-wide-mode
     81setvsi 1 1,3,5,7,9,11,13,15,2.1 tcp 172.16.4.224 dpid 0x0123456789ab
     82setvsi 2 17,19,21,23,25,27,29,31,2.2 tcp 172.16.4.180 dpid 0x012345678abc
     83setvsi 3 33,35,37,39,41,43,45,47,2.3 tcp 172.16.4.64 dpid 0x01234567abcd
     84}}}
     85In this case, the three virtual switches each take up the top row of a block of ports, and share a trunk port (port 2), as denoted by the 2.1, 2.2, and 2.3 at the end of the lists of ports. the syntax is
    8986
    90 setvsi 1 1,2,3,4,9.1 tcp 172.16.4.180 dpid 0x0123456789ab
    91 setvsi 2 5-8,9.2 tcp 172.16.4.64 dpid 0x01234567abcd
    92 setvsi 3 15-18,19.2 tcp 172.16.4.64 dpid 0x01234567abcd
    93 }}}
     87<port number of trunk>.<VLAN> 
     88
     89The VLAN assignments were made to match up with the port assignments of the virtual switches. The virtual switch can overlay across a portion of the ports of any given VLAN, but not overlay across ports belonging to different VLANS. 
     90
     91=== editing openflow.conf from the CLI versus editing it from a computer ===
     92
     93Once the switch is booted from the card, the two CLI commands you can use to manipulate openflow.conf are:
     94
     95 * `setvsi` - adds virtual switches using the exact same syntax as in openflow.conf
     96 * `deletevsi` - removes virtual switches
     97
     98Even though the switch will boot without anything written in openflow.conf, and you can add the virtual switches later, you can't add any of the other choices i.e. `no-save` or `double-wide-mode` from the command line. In order to add the other parameters to openflow.conf, you will have to edit the file on a text editor.   
     99
     100The details of configuring VLANs and virtual switches on an !OpenFlow capable switch are here: [[BR]]
     101wiki:Documentation/OpenFlow/VirtualSwitch
    94102
    95103
     104[[BR]]
     105[[BR]]
    96106
    97107
     108[wiki:Documentation/OpenFlow/ Return to the OpenFlow index]
     109
     110