Ask Your Question
0

Where are default flows stored in ODL

asked 2016-03-22 16:04:39 -0700

sterdnotshaken gravatar image

So when I reload my OF enabled router, ODL automatically installs 3 or 4 Unidentified Flows (UF$TABLE...). Where would I find these default flows on ODL so I can either modify them or delete them?

Here's an example from right after a reload:

Flow ID: 1 Priority: 100 Status: Active Rule:
In Port: generic Ether type: 0x000088cc Idle Timeout : 0 secs Hard Timeout : 0 secs

Instructions: Apply-Actions
    Action: FORWARD
        Out Port: send to controller
Statistics: 
   Total Pkts: 0 
   Total Bytes: 0

Timing Info: 
   Time Elapsed(Since Flow Added)       :     6 secs
   Time Elapsed(Since Last Packet Hit)  :     6 secs

Flow ID: 2 Priority: 0 Status: Active Rule: In Port: generic Idle Timeout : 0 secs Hard Timeout : 0 secs

Instructions: Apply-Actions
    Action: DROP
Statistics: 
   Total Pkts: 0 
   Total Bytes: 0

Timing Info: 
   Time Elapsed(Since Flow Added)       :     6 secs
   Time Elapsed(Since Last Packet Hit)  :     6 secs

How do I change this?

Thanks!

edit retag flag offensive close merge delete

3 answers

Sort by ยป oldest newest most voted
0

answered 2016-03-22 23:31:21 -0700

karthik330 gravatar image

Hi , Inside L2switch Project , InitialFlowWriter class is there which install the lldp default flows in each switch when you install L2switch . I guess by commenting this function call line, we could avoid the default flows ! . i am not sure , It might be an option .Let me try and let you know

edit flag offensive delete publish link more
0

answered 2016-03-23 08:29:34 -0700

jamoluhrsen gravatar image

Are you sure you want the functionality of the L2Switch application? That is the reason for those flows showing up on your switch, it seems. If you don't need that functionality then you don't need to install that app.

If you do need something from l2switch, but not all, you can also configure it to not send down some/all of the flows. This guide might help. In a running distribution, those config files will be in etc/opendaylight/karaf and you will need to restart after changing them. In a freshly built or unzipped distribution, those files initially start in distribution/karaf/target/assembly/etc/opendaylight/karaf and should be copied to etc/opendaylight/karaf when you start karaf.

edit flag offensive delete publish link more
0

answered 2016-03-23 17:03:51 -0700

sterdnotshaken gravatar image

Very grateful for each of you taking the time to answer my question!

Odd thing is, I don't have the l2switch feature installed... Here's what's currently installed:

odl-config-netty
odl-lacp-plugin
odl-sfc-model
odl-sfc-provider
odl-sfc-provider-rest
odl-sfc-ovs
odl-sfcofl2
odl-sfc-ui
odl-snmp-plugin
odl-ovsdb-southbound-api
odl-ovsdb-southbound-impl
odl-openflowjava-protocol
odl-mdsal-binding-base
odl-mdsal-binding-runtime
odl-didm-util
odl-didm-all
odl-didm-identification
odl-didm-drivers
odl-mdsal-models
odl-aaa-api
odl-openflowplugin-nxm-extensions
odl-groupbasedpolicy-base
odl-groupbasedpolicy-ofoverlay
odl-groupbasedpolicy-netconf
odl-groupbasedpolicy-neutronmapper
odl-groupbasedpolicy-uibackend
odl-groupbasedpolicy-ui
odl-yangtools-yang-data
odl-yangtools-common
odl-yangtools-yang-parser
odl-restconf
odl-restconf-noauth
odl-mdsal-apidocs
odl-alto-release
odl-alto-core
odl-alto-basic
odl-alto-standard-types
odl-alto-resourcepool
odl-alto-northbound
odl-alto-standard-service-models
odl-alto-standard-northbound-route
odl-alto-standard-resource-translator odl-alto-simpleird
odl-alto-manual-maps
odl-alto-hosttracker
odl-netconf-connector-all
odl-netconf-connector
odl-netconf-connector-ssh
pax-jetty
pax-http
pax-http-whiteboard
pax-war
standard
config
region
package
http
war
kar
ssh
management
odl-mdsal-all
odl-mdsal-common
odl-mdsal-broker-local
odl-toaster
odl-mdsal-xsql
odl-mdsal-clustering-commons
odl-mdsal-distributed-datastore
odl-mdsal-remoterpc-connector
odl-mdsal-broker
odl-mdsal-clustering
odl-netty
odl-lmax
odl-config-all
odl-config-api
odl-config-netty-config-api
odl-config-core
odl-config-manager
odl-protocol-framework
odl-netconf-all
odl-netconf-api
odl-netconf-mapping-api
odl-netconf-util
odl-netconf-impl
odl-config-netconf-connector
odl-netconf-netty-util
odl-netconf-client
odl-netconf-monitoring
odl-netconf-notifications-api
odl-netconf-notifications-impl
odl-netconf-ssh
odl-netconf-tcp
odl-aaa-netconf-plugin
odl-ovsdb-library
odl-neutron-service
odl-neutron-northbound-api
odl-neutron-spi
odl-neutron-transcriber
odl-didm-ovs-all
odl-didm-ovs-impl
odl-aaa-authn
odl-akka-scala
odl-akka-system
odl-akka-clustering
odl-akka-leveldb
odl-akka-persistence
odl-openflowplugin-all
odl-openflowplugin-southbound
odl-openflowplugin-flow-services
odl-openflowplugin-nsf-services
odl-openflowplugin-nsf-model
odl-openflowplugin-flow-services-rest odl-openflowplugin-flow-services-ui
odl-openflowplugin-app-config-pusher odl-config-persister
odl-config-startup
odl-config-manager-facade-xml
odl-aaa-shiro
odl-didm-hp-all
odl-didm-hp-impl
odl-dlux-all
odl-dlux-core
odl-dlux-node
odl-dlux-yangui
odl-dlux-yangvisualizer

Someone on the Openflow-plugin email group said it might be a table-miss-enforcer related to lldp-punt flows, so I (potentially erroneously) uninstalled odl-openflowplugin-app-lldp-speaker thinking that might be it. Now the switches in YangUI don't show as connected as per the switches not forwarding lldp pdu's to the controller. The thing is, I'm fine with lldp being sent to the controller, but I don't want the controller adding other flows that drop traffic.

I should add that I'm running these routers (Brocade MLXe's) in hybrid mode, so when there's a drop flow, all "unprotected" vlan's cease to function, which is obviously bad.

Thoughts?

Thanks!

edit flag offensive delete publish link more
Login/Signup to Answer

Question Tools

Follow
1 follower

Stats

Asked: 2016-03-22 16:04:39 -0700

Seen: 259 times

Last updated: Mar 23 '16