关于OpenDaylight无法稳定检测Zodiac FX交换机的技术咨询

Hey Juan, let's tackle this frustrating random detection problem you're having between ODL and your Zodiac FX switch. You've already tried adjusting the startup order, so let's dive into more targeted tweaks to make ODL's scanning more reliable and efficient:

1. Adjust ODL's OpenFlow Discovery Timings #

ODL's default discovery settings might be too aggressive for the Zodiac FX, which is a low-power switch. Tweaking the timeout and scan interval gives the switch more time to respond to discovery requests.

• Open the ODL Karaf shell and run these commands to update the configuration:

  config:edit org.opendaylight.openflowplugin.impl
  config:property-set discovery-switch-connection-timeout 10000
  config:property-set discovery-switch-scan-interval 5000
  config:update
  

  Note: The values above (10-second timeout, 5-second scan interval) are starting points—feel free to increase them if your network has higher latency.

2. Use Static Switch Discovery Instead of Broadcast #

Instead of relying on hit-or-miss broadcast discovery, manually add your Zodiac FX's IP to ODL's static list. This ensures ODL actively reaches out to the switch directly.

• In the Karaf shell, add your switch's IP (replace 192.168.1.100 with your actual switch IP and port if modified):

  openflow:add-switch 192.168.1.100:6633
  

• To make this setting persistent across ODL restarts, update the core config:

  config:edit org.opendaylight.openflowplugin.impl
  config:property-set static-switches "[192.168.1.100:6633]"
  config:update
  

3. Ensure OpenFlow Version Compatibility #

Zodiac FX supports OpenFlow 1.3, but ODL might default to negotiating older versions. Mismatched versions can cause silent detection failures.

• Check your current OpenFlow version setting in Karaf:

  config:list -p org.opendaylight.openflowplugin.impl | grep openflow-version
  

• If it's not set to 1.3, update it:

  config:edit org.opendaylight.openflowplugin.impl
  config:property-set openflow-version "1.3"
  config:update
  

4. Rule Out Network Blockages #

Even with correct IP/port config, firewalls or ACLs might be blocking OpenFlow control traffic (default TCP port 6633).

• On the ODL controller machine, allow incoming traffic from your Zodiac FX:

  sudo iptables -A INPUT -s <ZODIAC_FX_IP> -p tcp --dport 6633 -j ACCEPT
  

• Double-check the Zodiac FX's internal settings to ensure it's allowed to send outgoing control traffic to your ODL controller's IP and port.

5. Enable Debug Logs to Diagnose Root Causes #

If you're still seeing random failures, enable debug logging to get granular details about where the discovery process is breaking down.

• Set the OpenFlow plugin log level to DEBUG in Karaf:

  log:set DEBUG org.opendaylight.openflowplugin
  

• View real-time logs with:

  log:tail
  

  Look for entries related to "switch discovery" or "connection attempts"—these will tell you if it's a timeout, protocol mismatch, or network issue.

内容的提问来源于stack exchange，提问作者Juan Andrés Martínez