Changes between Version 9 and Version 10 of Documentation/fSDN/eNetFpgaTutorial


Ignore:
Timestamp:
Mar 22, 2011, 6:23:23 PM (14 years ago)
Author:
nkiran
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Documentation/fSDN/eNetFpgaTutorial

    v9 v10  
    4141 * [wiki:Documentation/OpenFlow/NetFpgaOpenFlow/BaselineInstallationUbuntuTenTen NetFPGA/OpenFlow Installation steps on Ubuntu 10.10]
    4242
    43 === Controlling SB9 topology through the Top Switch ===
     43=== Gateware ===
     44
     45=== Controlling Sandbox Topology through the Top Switch ===
     46
     47ORBIT 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:
     48
     49{{{
     50http://nox.orbit-lab.rutgers.edu:5052/network
     51Or simply as:
     52http://nox:5052/network
     53}}}
     54
     55That 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:
     56
     57{{{
     58http://nox:5052/network/portStat?switch=10.19.0.253&port=5
     59}}}
     60
     61The service supports the following main features for the native mode (refer to XML response from the base URL for complete list and API specification):
     62
     63 1. Getting/setting the VLAN ID on any port(s)
     64 1. Assigning two or more VLAN IDs on a port, making it a trunk
     65 1. Getting per port statistics (in, out packet counts) and configuration (VLAN) information
     66 1. Enabling/disabling a port
     67 1. Turning on/off default switch topology protocols - Spanning Tree Protocol (STP)
     68 1. Saving the per-port configuration of the entire switch
     69 1. Restoring switch configuration to prior saved version
     70
     71In addition, it supports the following requests to support the !OpenFlow mode:
     72
     73 1. Change the mode of the switch from native to !OpenFlow mode (and vice versa)
     74 1. Set the !OpenFlow mode parameters including: control port, controller IP, switch ID (dpid), and the transport mode for secure channel
     75''''' Q. Does the switch have to be in native mode to invoke the setvsi/getvsi requests? '''''
    4476
    4577