Ask is moving to Stack Overflow and Serverfault.com! Please use the "opendaylight" tag on either of these sites. This site is now in Read-Only mode

ngg1's profile - activity

2017-02-14 04:48:01 -0700 received badge  Taxonomist
2016-03-29 03:20:11 -0700 answered a question How do I find the statistics of all the network's flows?

Hi,

If you change your http request to end at nodes/ you will get all the output for all the devices that odl knows about.

regards,

SG

--upvote if you like!--

2016-03-29 00:19:42 -0700 answered a question Karaf feature in UI

hi,

should be the 3rd column:

opendaylight-user@root> feature:list | head
Name                                          | Version             | Installed | Repository                                 | Description                             
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

or

ser@root>feature:list -i

regards,

SG

2016-03-28 23:56:40 -0700 answered a question Why TSDR only supported on grafana 1.9.1

Hello,

Looks like you should be able to add the features using karaf as listed below:

    opendaylight-user@root>feature:list | grep tsdr
odl-tsdr-all                                  | 1.0.3-Lithium-SR3   |           | odl-tsdr-1.0.3-Lithium-SR3                 | OpenDaylight :: TSDR :: ALL (default to H2 Data St
odl-tsdr-hbase                                | 1.0.3-Lithium-SR3   |           | odl-tsdr-1.0.3-Lithium-SR3                 | OpenDaylight :: TSDR :: HBase Data Store
odl-tsdr-core                                 | 1.0.3-Lithium-SR3   |           | odl-tsdr-1.0.3-Lithium-SR3                 | OpenDaylight :: TSDR :: Core     
odl-hbaseclient                               | 0.94.15             |           | odl-tsdr-1.0.3-Lithium-SR3                 | OpenDaylight :: TSDR :: HBase Client
odl-tsdr-hbase-persistence                    | 1.0.3-Lithium-SR3   |           | odl-tsdr-1.0.3-Lithium-SR3                 | OpenDaylight :: TSDR :: HBase Persistence
odl-tsdr-H2-persistence                       | 1.0.3-Lithium-SR3   |           | odl-tsdr-1.0.3-Lithium-SR3                 | OpenDaylight :: TSDR :: H2 Persistence

Let me know if that answers your question.

Regards,

SG

2016-03-28 23:34:31 -0700 answered a question DLUX Add Flow

Hello,

I found the apidoc site in the opedaylight webfront end to be useful:

http://<opendaylight-ip-address>:8181/apidoc/explorer/index.html

also the wiki is helpful:

https://wiki.opendaylight.org/view/Editing_OpenDaylight_OpenFlow_Plugin:End_to_End_Flows:Example_Flows

Regards,

SG

2016-03-28 23:27:55 -0700 answered a question Capability Of Opendaylight CLI

Hello,

My lithium distribution has the following configuration files listed:

ls etc/opendaylight/karaf/
00-netty.xml                       39-pcep-provider.xml
01-md-sal.xml                      40-inventory-manager.xml
01-netconf.xml                     41-bgp-example.xml
04-xsql.xml                        42-openflowplugin-He.xml
05-clustering.xml                  43-msg-spy.xml
06-clustered-entity-ownership.xml  45-openflowjava-stats.xml
08-authn-config.xml                50-packethandler.xml
10-restconf-service.xml            52-loopremover.xml
10-rest-connector.xml              54-arphandler.xml
20-tcpmd5.xml                      56-addresstracker.xml
30-forwardingrules-manager.xml     57-hosttracker.xml
30-programming.xml                 58-l2switchmain.xml
30-statistics-manager.xml          70-of-switch-config-pusher.xml
31-bgp.xml                         71-lldp-speaker.xml
32-pcep.xml                        72-topology-lldp-discovery.xml
33-pcep-segment-routing.xml        73-topology-manager.xml

If you want to leverage some of the dynamic routing in opendaylight, I recommend you redistriubute into bgp and peer opendaylight using the 31-bgp.xml file.

Regards,

SG

2016-03-28 23:23:09 -0700 answered a question Adding a new openflow message

Hi,

I found the below website very useful:

WIKI

Regards,

SG

2016-03-25 03:02:31 -0700 received badge  Editor (source)
2016-03-25 02:47:21 -0700 answered a question Renaming switches in ODL

Hi,

I had a similar question. It may be useful to understand the controller negotiation process when a switch first connects:

OpenFlow enabled switches and controllers goes through a procedure called a Handshake. During this exchange of messages, the two parties gather information about one another, such as the Data-path ID to uniquely identify the switch, the maximum capacity of the buffer and how many bytes of a packet to send to the Controller

odl controller negotiation

Also,

I'm not sure about brocade switches, but apparently using openvswitch, you can set your datapath_id with the below command:

ovs-vsctl set bridge <mybr> other-config:datapath-id=<datapathid>

If you issue this command in openvswitch, you can also view the datapath-id:

 ovs-vsctl list bridge <mybr>

which gives you something like this:

_uuid               : 59e17067-5708-4829-8fca-9e5eee5134af
controller          : [80e4a4e5-2021-47f6-81fa-330a4f7fbbe1]
datapath_id         : "00006670e1592948"
datapath_type       : ""
external_ids        : {}
fail_mode           : []
flood_vlans         : []
flow_tables         : {}
ipfix               : []
mirrors             : []

Let me know if this helps.

SG

2016-03-25 02:18:14 -0700 asked a question view all unmatched flows sent to controller

Hello,

I have what seems like a simple question which I have not been able to answer myself searching through the various yang containers in opendaylight.

I understand the openflow enabled switch operation can be summed with the below:

When an inbound packet arrives, the switch goes through its Flow Table(s) to try and match the different headers of the packet to an action. If one is matched, it carries the corresponding action. If not it sends the packet (or part of it depending on the configuration) to the Controller with a PACKET IN message. The Controller then replies back the final decision about the packet, whether it is to forward it with a PACKET OUT message or drop it entirely. It possibly writes an action in the switch’s Flow Table with a FLOW MOD message in case another packet from the same flow comes up.

My question is whether or not this information can be found in a config or operational container in opendaylight, or if this is something that needs to be programmed into the system.

Many thanks,

SG