Changes between Version 1 and Version 2 of Software/eAM/qNetwork


Ignore:
Timestamp:
May 2, 2011, 11:03:22 PM (13 years ago)
Author:
seskar
Comment:

—

Legend:

Unmodified
Added
Removed
Modified

  • Software/eAM/qNetwork

    v1 v2  
    1 ORBIT provides HTTP request API abstraction to controlling the configuration of the top switch. The service implementing this API can be accessed by an experimenter from within the SB9 network, including the console and experiment nodes, at the following address:
     1= Switch Control Service =
     2
     3ORBIT provides OMF based "Aggregate Manager" for configuration of networking devices in the testbed (Network AM). The HTTP based service can be accessed by an experimenter from within the SB9, including from the console and all of the nodes, at the following address:
    24
    35{{{
    … …  
    79}}}
    810
    9 That base URL renders an XML response detailing all requests implemented by the service. Parameter values, such as to address a particular port (port #) on a particular switch (switch IP address), be passed as URL arguments in the HTTP request. For example, to retrieve the details of particular port (say 5) on the top switch ('''IP=10.19.0.253'''), the requested URL is:
    10 
    11 = Switch Control Service =
     11That base URL renders an XML response detailing all requests implemented by the service. Parameter values, such as to address a particular port (port #) on a particular switch (switch IP address), can be passed as URL arguments in the HTTP request. For example, to retrieve the details of particular port (say 5) on the SB9 switch ('''IP=10.19.0.253'''), the requested URL is:
    1212
    1313{{{
    … …  
    2929 1. Change the mode of the switch from native to !OpenFlow mode (and vice versa)
    3030 1. Set the !OpenFlow mode parameters including: control port, controller IP, switch ID (dpid), and the transport mode for secure channel
     31
     32== Pronto 3240 Management ==
     33Pronto switches can be configured for of following modes:
     34
     35 * !XorPlus
     36 * Production Indigo !OpenFlow image (i.e. internal flash image)
     37 * User define !OpenFlow image (i.e. NFS booted image)
     38
     39To be able to switch between these modes you have to be logged in conosole.sb9.
     40
     41=== Examples ===
     42
     43Force switch into !XorPlus mode (i.e. out of !OpenFlow mode)
     44{{{
     45wget http://nox.orbit-lab.org:5052/network/deleteOpenFlow?switch=10.19.0.253
     46}}}
     47
     48Force switch into !OpenFlow mode with controller at node1-1.sb9.orbit-lab.org
     49{{{
     50wget http://nox.orbit-lab.org:5052/network/addOpenFlow?switch=10.19.0.253\&ofip=10.19.1.1\&ofp=6633
     51\&dpid=0x001010162001
     52}}}
     53ofp and dpid are optional (if omitted will be configured with the default set).
     54
     55Force switch into !OpenFlow NFS mode
     56To configure switch in !OpenFlow NFS mode, bootmode parameter has to be specified. Additional 3 parameters can be specified, nfsip, roottpath and bootfile. These parameters are optional, if omitted will be configured whit initially set parameters (for sb9 operation NSF server is provided on the console so the experimenter should place the image file names uInitrd2m into /tftpboot directory before issiong this command)
     57
     58{{{
     59wget http://nox.orbit-lab.org:5022/network/addOpenFlow?switch=10.19.0.253\&ofip=10.19.1.1\&ofp=6633
     60\&dpid=0x001010162001\&bootmode=nfs\&nfsip=10.19.0.10\&roothpath='\/config'\&bootfile=uInitrd2m
     61}}}