Cannot discover topology of switches
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎03-25-2015 10:42 PM
I have a lab setup where the controller is connected to the management ports of three OF switches through another L2 switch (another X440). The three switches are able to connect to the controller but the connection between them isn't discovered by the Topology manager in OpenDaylight. I see an empty topology through the REST API and the web view shows three isolated switches. I suspect this is because the L2 switch isn't forwarding the LLDP packet sent by the controller to the three OF switches. I may be completely wrong though. Do I need to enable some LLDP related feature/setting on the X440s to forward LLDPs? Or disable some feature on the one I'm using as a simple L2 switch? Kindly help me figure out why the topology isn't discovered by the controller.
7 REPLIES 7
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎03-26-2015 04:16 AM
The config is already present on the switches. I think I'm missing something else. X440-8p.5 # show configuration "openflow" # # Module openflow configuration. # configure openflow default-rule lldp controller configure openflow default-rule miss controller enable openflow configure openflow controller primary out-of-band active ipaddress 10.10.1.10 vr VR-Mgmt
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎03-26-2015 04:16 AM
Ankit
Can you try enabling the following on the switch
configure openflow default-rule lldp controller
configure openflow default-rule miss controller
controller uses OF packet_in and packet_out messages to figure out the topolology. If the default action is set to drop on the switch the LLDP packets might get dropped and will never be sent to controller.
Regards
Sathish
Can you try enabling the following on the switch
configure openflow default-rule lldp controller
configure openflow default-rule miss controller
controller uses OF packet_in and packet_out messages to figure out the topolology. If the default action is set to drop on the switch the LLDP packets might get dropped and will never be sent to controller.
Regards
Sathish
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎03-26-2015 02:15 AM
Thanks Ravi! I see the topology as expected on the controller now.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎03-26-2015 02:15 AM
Hi Ankit,
From the above show openflow - (Total number of VLAN(s): 0), I could see that you have not enabled OpenFlow on ports/VLANs that connecting the switches that is the reason for not seeing the topology. Open Flow process processes the packets that ingress on open flow enabled ports only.
Since EXOS doesn't allow to enable open flow on port directly, you need create a VLAN in all the switches and add the connecting ports and then enable open flow on the VLAN. Here is an example configuration
create vlan "v11"
configure vlan v11 tag 11
configure vlan v11 add ports 22, 25-26 tagged
enable openflow vlan "v11"
Regards,
Ravi Masadi
From the above show openflow - (Total number of VLAN(s): 0), I could see that you have not enabled OpenFlow on ports/VLANs that connecting the switches that is the reason for not seeing the topology. Open Flow process processes the packets that ingress on open flow enabled ports only.
Since EXOS doesn't allow to enable open flow on port directly, you need create a VLAN in all the switches and add the connecting ports and then enable open flow on the VLAN. Here is an example configuration
create vlan "v11"
configure vlan v11 tag 11
configure vlan v11 add ports 22, 25-26 tagged
enable openflow vlan "v11"
Regards,
Ravi Masadi
