Changes between Version 2 and Version 3 of OpenFlow/Controllers/Floodlight
- Timestamp:
- 12/11/12 14:37:37 (11 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
OpenFlow/Controllers/Floodlight
v2 v3 24 24 25 25 ==== 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.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. 27 27 {{{ 28 28 curl <controller_url>/wm/topology/links/json | python -m json.tool … … 31 31 To see how !OpenFlow switches interconnect through non-OpenFlow switches, the following query can be used: 32 32 {{{ 33 curl <controller_url>/wm/topology/ links/json | python -m json.tool33 curl <controller_url>/wm/topology/external-links/json | python -m json.tool 34 34 }}} 35 35 Note that this second query relies on the controller being able to handle traffic for a specific ethertype.