This section details the configuration settings for the components that can be configured.
The base distribution configuration files are located in distribution/base/target/distributions-l2switch-base-0.1.0-SNAPSHOT-osgipackage/opendaylight/configuration/initial
The karaf distribution configuration files are located in distribution/karaf/target/assembly/etc/opendaylight/karaf
Loop Remover (52-loopremover.xml)
is-install-lldp-flow
- "true" means a flow that sends all LLDP packets to the controller will be installed on each switch
- "false" means this flow will not be installed
lldp-flow-table-id
- The LLDP flow will be installed on the specified flow table of each switch
- This field is only relevant when "is-install-lldp-flow" is set to "true"
lldp-flow-priority
- The LLDP flow will be installed with the specified priority
- This field is only relevant when "is-install-lldp-flow" is set to "true"
lldp-flow-idle-timeout
- The LLDP flow will timeout (removed from the switch) if the flow doesn’t forward a packet for x seconds
- This field is only relevant when "is-install-lldp-flow" is set to "true"
lldp-flow-hard-timeout
- The LLDP flow will timeout (removed from the switch) after x seconds, regardless of how many packets it is forwarding
- This field is only relevant when "is-install-lldp-flow" is set to "true"
graph-refresh-delay
- A graph of the network is maintained and gets updated as network elements go up/down (i.e. links go up/down and switches go up/down)
- After a network element going up/down, it waits graph-refresh-delay seconds before recomputing the graph
- A higher value has the advantage of doing less graph updates, at the potential cost of losing some packets because the graph didn’t update immediately.
- A lower value has the advantage of handling network topology changes quicker, at the cost of doing more computation.
Arp Handler (54-arphandler.xml)
is-proactive-flood-mode
"true" means that flood flows will be installed on each switch. With this flood flow, each switch will flood a packet that doesn’t match any other flows.
- Advantage: Fewer packets are sent to the controller because those packets are flooded to the network.
- Disadvantage: A lot of network traffic is generated.
"false" means the previously mentioned flood flows will not be installed. Instead an ARP flow will be installed on each switch that sends all ARP packets to the controller.
- Advantage: Less network traffic is generated.
- Disadvantage: The controller handles more packets (ARP requests & replies) and the ARP process takes longer than if there were flood flows.
flood-flow-table-id
- The flood flow will be installed on the specified flow table of each switch
- This field is only relevant when "is-proactive-flood-mode" is set to "true"
flood-flow-priority
- The flood flow will be installed with the specified priority
- This field is only relevant when "is-proactive-flood-mode" is set to "true"
flood-flow-idle-timeout
- The flood flow will timeout (removed from the switch) if the flow doesn’t forward a packet for x seconds
- This field is only relevant when "is-proactive-flood-mode" is set to "true"
flood-flow-hard-timeout
- The flood flow will timeout (removed from the switch) after x seconds, regardless of how many packets it is forwarding
- This field is only relevant when "is-proactive-flood-mode" is set to "true"
arp-flow-table-id
- The ARP flow will be installed on the specified flow table of each switch
- This field is only relevant when "is-proactive-flood-mode" is set to "false"
arp-flow-priority
- The ARP flow will be installed with the specified priority
- This field is only relevant when "is-proactive-flood-mode" is set to "false"
arp-flow-idle-timeout
- The ARP flow will timeout (removed from the switch) if the flow doesn’t forward a packet for x seconds
- This field is only relevant when "is-proactive-flood-mode" is set to "false"
arp-flow-hard-timeout
- The ARP flow will timeout (removed from the switch) after arp-flow-hard-timeout seconds, regardless of how many packets it is forwarding
- This field is only relevant when "is-proactive-flood-mode" is set to "false"
Address Tracker (56-addresstracker.xml)
timestamp-update-interval
- A last-seen timestamp is associated with each address. This last-seen timestamp will only be updated after timestamp-update-interval milliseconds.
- A higher value has the advantage of performing less writes to the database.
- A lower value has the advantage of knowing how fresh an address is.
observe-addresses-from
- IP and MAC addresses can be observed/learned from ARP, IPv4, and IPv6 packets. Set which packets to make these observations from.
L2Switch Main (58-l2switchmain.xml)
is-install-dropall-flow
- "true" means a drop-all flow will be installed on each switch, so the default action will be to drop a packet instead of sending it to the controller
- "false" means this flow will not be installed
dropall-flow-table-id
- The dropall flow will be installed on the specified flow table of each switch
- This field is only relevant when "is-install-dropall-flow" is set to "true"
dropall-flow-priority
- The dropall flow will be installed with the specified priority
- This field is only relevant when "is-install-dropall-flow" is set to "true"
dropall-flow-idle-timeout
- The dropall flow will timeout (removed from the switch) if the flow doesn’t forward a packet for x seconds
- This field is only relevant when "is-install-dropall-flow" is set to "true"
dropall-flow-hard-timeout
- The dropall flow will timeout (removed from the switch) after x seconds, regardless of how many packets it is forwarding
- This field is only relevant when "is-install-dropall-flow" is set to "true"
is-learning-only-mode
- "true" means that the L2Switch will only be learning addresses. No additional flows to optimize network traffic will be installed.
- "false" means that the L2Switch will react to network traffic and install flows on the switches to optimize traffic. Currently, MAC-to-MAC flows are installed.
reactive-flow-table-id
- The reactive flow will be installed on the specified flow table of each switch
- This field is only relevant when "is-learning-only-mode" is set to "false"
reactive-flow-priority
- The reactive flow will be installed with the specified priority
- This field is only relevant when "is-learning-only-mode" is set to "false"
reactive-flow-idle-timeout
- The reactive flow will timeout (removed from the switch) if the flow doesn’t forward a packet for x seconds
- This field is only relevant when "is-learning-only-mode" is set to "false"
reactive-flow-hard-timeout
- The reactive flow will timeout (removed from the switch) after x seconds, regardless of how many packets it is forwarding
- This field is only relevant when "is-learning-only-mode" is set to "false"
