Hello Folks,
We tried to have our nox application connect with Physical OpenFlow capable
switches, and ran into two serious issues. Would you please advise ?
ISSUES
1) the connection between a switch and NOX.
We tried to connect with NOX a port defined as a controller port on a
physical switch, but unforunately failed to have the switch communicate
with NOX via the particular port with the following message #00326 after a
feature response returned from the switch. Could you please advise us
whether there are any possible reasons why the message #00326 was put based
on the following physical switch support capablity list ?
00323|nox|DBG:Success receiving in 'receiving features reply'
00324|nox|DBG:Success sending in 'receiving ofmp capability reply'
00325|nox|DBG:Success receiving in 'receiving ofmp capability reply'
00326|nox|DBG:Datapath a0817f4338900 sent error in response to capability
reply, assuming no management support
00327|nox|DBG:No switch auth module registered, auto-approving switch
C.F.
This is Swtch Support Capabilities extracted from Switch side.
Swicth Support Capabiilities:
Flow Statistics : enabled
Table Statistics : enabled
Port Statistics : enabled
Spanning Tree : disabled
Reserved : disabled
Reassemble IP Fragments : disabled
Queue Statistics : disabled
Match IP Addr in ARP Packets: disabled
Swicth Support action:
.....
2) OpenFlow Error Packet message.
After a physical topology view is build within NOX via LLDP pkt
exchange, an ARP request was originated by a host to a connected access
layer OpenFlow capable switch and the ARP request packet-in'd to NOX. Then
NOX had all the connected OpenFlow Switches packet-out the ARP request via
their edge ports to learn a destination host. Just after that NOX put the
following openflow error packet message with type 3 and code 2.
What does it mean type 3 and code 2 ? Could you advise how to solve this
problem ?
[22:30:24.268940] ARP REQ: dpid=0xa0817f432e900, inport=17,
src-mac:00:11:25:cf:03:c2 src-ip:192.168.2.50, dst-mac:00:00:00:00:00:00
dst-ip:192.168.2.60
[22:30:24.268981] Send ARP REQ to switch=0xa0817f4338c00, port=1
[22:30:24.269152] Send ARP REQ to switch=0xa0817f4338c00, port=2
...
[22:30:24.279199] Send ARP REQ to switch=0xa0817f4338c00, port=63
[22:30:24.279346] Send ARP REQ to switch=0xa0817f4336300, port=1
...
[22:30:24.287450] Send ARP REQ to switch=0xa0817f4336300, port=63
[22:30:24.287583] Send ARP REQ to switch=0xa0817f432e900, port=1
...
[22:30:24.305274] Send ARP REQ to switch=0xa0817f4338900, port=63
[22:30:24.305406] -----
00977|openflow-event|ERR:received Openflow error packet from
dpid=a0817f4338900: type=3, code=2, 64 bytes of data
00978|openflow-event|ERR:received Openflow error packet from
dpid=a0817f4338c00: type=3, code=2, 64 bytes of data
00979|openflow-event|ERR:received Openflow error packet from
dpid=a0817f432e900: type=3, code=2, 64 bytes of data
00980|openflow-event|ERR:received Openflow error packet from
dpid=a0817f4338900: type=3, code=2, 64 bytes of data
00981|openflow-event|ERR:received Openflow error packet from
dpid=a0817f4338c00: type=3, code=2, 64 bytes of data
00982|openflow-event|ERR:received Openflow error packet from
dpid=a0817f432e900: type=3, code=2, 64 bytes of data
00983|openflow-event|ERR:received Openflow error packet from
dpid=a0817f4338900: type=3, code=2, 64 bytes of data
00984|openflow-event|ERR:received Openflow error packet from
dpid=a0817f4338c00: type=3, code=2, 64 bytes of data
....
Thank you and Best Regards,
-- Yoshisato Ushio
