Changes between Version 2 and Version 3 of OpenFlow/Controllers/Floodlight


Ignore:
Timestamp:
12/11/12 14:37:37 (9 years ago)
Author:
tupty@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • OpenFlow/Controllers/Floodlight

    v2 v3  
    2424
    2525==== Querying for Topology Information ====
    26 This will tell you how the !OpenFlow switches are interconnected.  This will only work for switches that are physically directly connected or logically directly connected (i.e. via a tunnel).  If a non-OpenFlow switch is between two !OpenFlow switches, then this query cannot tell you how these two !OpenFlow switches connect.  To query this information, the net.floodlightcontroller.topology.TopologyManager module must be loaded.
     26This will tell you how the !OpenFlow switches are interconnected.  This will only work for switches that are physically directly connected or logically directly connected (i.e. via a tunnel).  If a non-OpenFlow switch is between two !OpenFlow switches, then this query cannot tell you how these two !OpenFlow switches connect.  To query this information, the net.floodlightcontroller.topology.!TopologyManager module must be loaded.
    2727{{{
    2828curl <controller_url>/wm/topology/links/json | python -m json.tool
     
    3131To see how !OpenFlow switches interconnect through non-OpenFlow switches, the following query can be used:
    3232{{{
    33 curl <controller_url>/wm/topology/links/json | python -m json.tool
     33curl <controller_url>/wm/topology/external-links/json | python -m json.tool
    3434}}}
    3535Note that this second query relies on the controller being able to handle traffic for a specific ethertype.