Changes between Version 1 and Version 2 of Internal/OpenFlow/TunnelNotes


Ignore:
Timestamp:
Jun 23, 2010, 8:52:01 PM (14 years ago)
Author:
ssugrim
Comment:

—

Legend:

Unmodified
Added
Removed
Modified

  • Internal/OpenFlow/TunnelNotes

    v1 v2  
     1System Config:
     2{{{
     3Ubuntu Version: Ubuntu 9.04
     4Netfpga Version: 2.1.0
     5Openflow Version: 1.0.0
     6flowvisor Version: Alpha version 0.4
     7}}}
    18
     9Note: Bitfiles come from some other package and must be made to agree with the versions of cpci tools and nf2 kernel module
    210
     11Basic Usage:
     12Assuming the machine is freshly rebooted the script:
     13{{{
     14/opt/netfpga1.0.1/netfpga/projects/tunneling_openflow_switch/sw/of_start_winlab.sh
     15}}}
    316
    4 
    5 
     17Should be run as root
    618
    719Known issues:
    820
    921 1. When Running the of_start_winlab.sh script wake up the netfpga into a tunneling openflow mode we get this error from the script:
    10    Virtex design compiled against active CPCI version
    11    RTNETLINK answers: No such file or directory
    12    RTNETLINK answers: No such file or directory
    13    RTNETLINK answers: No such file or directory
    14    RTNETLINK answers: No such file or directory
    15    ARP_REPLY_ETH_ADDR_PORT_3_LO_REG=0x46324402
    16    
     22    Virtex design compiled against active CPCI version
     23    {{{
     24    RTNETLINK answers: No such file or directory
     25    RTNETLINK answers: No such file or directory
     26    RTNETLINK answers: No such file or directory
     27    RTNETLINK answers: No such file or directory
     28    ARP_REPLY_ETH_ADDR_PORT_3_LO_REG=0x46324402
     29    }}}
    1730   However it still works.
    18 
    1931 1. After a few minutes of operation the nf2 modules starts dumping buffer messages into the kernels ring buffer. The messages are:
    20    [ 1161.690033] nf2: no available transmit/receive buffers
    21    [ 1161.690061] nf2: no available transmit/receive buffers
    22    [ 1161.690089] nf2: no available transmit/receive buffers
    23    
     32    {{{
     33    [ 1161.690033] nf2: no available transmit/receive buffers
     34    [ 1161.690061] nf2: no available transmit/receive buffers
     35    [ 1161.690089] nf2: no available transmit/receive buffers
     36    }}}
    2437   We don't know what these errors are, and they are suspected to eventually brining down the tunnel (and thus requiring a reboot). That being said,
    2538   the tunnel does come up inspite of it.
    26 
    2739 1. The tunnel still dies, when I tried to bring it back up the interfaces took a little time to actually wake up, but it eventually got to
    2840    where it needed to be.