Hi Ali,
Thanks for your reply. After install wireshark and OpenFlow plugin, the
problem is solved. Still do not know the reason although we restart the
FlowVisor service. But now we find another error messages when using curl
to add a flow entry into Floodlight. The content of entry and the error
message are shown as below.
curl -d '{"switch": "00:00:fa:d7:c0:a2:7f:4a", "name":"flow-mod-2",
"cookie":"0", "priority":"32768", "ingress-port":"4", "vlan-id":"775",
"active":"true", "actions":"strip-vlan,output=2"}'
http://127.0.0.1:8080/wm/staticflowentrypusher/json
15:57:37.919 ERROR [n.f.c.i.OFChannelHandler:New I/O server worker #2-7]
Error OFPET_BAD_ACTION OFPBAC_BAD_ARGUMENT from switch OFSwitchBase [/
211.73.95.35:35116 DPID[00:00:fa:d7:c0:a2:7f:4a]] in state MASTER
15:57:37.919 WARN [n.f.c.i.Controller:New I/O server worker #2-7] Unhandled
OF Message: ofmsg:v=1;t=ERROR;l=100;x=0 from OFSwitchBase [/
211.73.95.35:35116 DPID[00:00:fa:d7:c0:a2:7f:4a]]
The capture message in Wireshark is
=====================================================================================
No. Time Source Destination Protocol
Length Info
43165 574.019766 y.y.y.y x.x.x.x OFP 154
Flow Mod (CSM) (88B)
Frame 43165: 154 bytes on wire (1232 bits), 154 bytes captured (1232 bits)
Ethernet II, Src: Supermic_fd:ce:90 (00:30:48:fd:ce:90), Dst:
Cisco_44:4c:41 (64:a0:e7:44:4c:41)
Transmission Control Protocol, Src Port: 6633 (6633), Dst Port: 35116
(35116), Seq: 2080, Ack: 14506, Len: 88
OpenFlow Protocol
Header
Flow Modification
Match
Cookie: 0x00a000004039d1a7
Command: New flow (0)
Idle Time (sec) Before Discarding: 0
Max Time (sec) Before Discarding: 0
Priority: 32768
Buffer ID: None
Out Port (delete* only): None (not associated with a physical port)
Flags
Output Action(s)
Action
Type: Strip the 802.1q header. (3)
Len: 8
Unknown Action Type
Action
Type: Output to switch port (0)
Len: 8
Output port: 2
Max Bytes to Send: 32767
# of Actions: 2
Thanks in advance
Jen-Wei
On Wed, Mar 5, 2014 at 3:21 PM, Ali Al-Shabibi
<ali.al-shab...@stanford.edu>wrote:
> Hi,
>
> It seems that your controller is sending a flowmod which is not permitted
> by flowvisor? So you know what flowmod is being pushed out by floodlight?
> If you use wireshark you should be able to sniff the openflow control
> packets.
>
> --
> Ali Al-Shabibi
>
> On Mar 4, 2014, at 23:03, Jen-Wei Hu <jenwe...@gmail.com> wrote:
>
> Hi all,
>
> Currently we want to separate different slices by VLAN in FlowVisor. Our
> environment is that two servers installed OvS as OpenFlow switches, and one
> server installed Floodlight 0.9, and one server installed FlowVisor
> (version 1.4). The Floodlight will not occur any error message until we use
> fvctl to add a flowspace entry "fvctl -f /dev/null add-flowspace
> dpid1-port3 00:00:ce:7b:8d:a7:79:4c 1 in_port=3,dl_vlan=775 slice1=7". In
> controller side, it shows the error messages periodically, shown as below.
>
> 14:55:48.306 ERROR [n.f.c.i.OFChannelHandler:New I/O server worker #2-2]
> Error OFPET_BAD_ACTION OFPBAC_EPERM from switch OFSwitchBase
> [/x.x.x.x:35055 DPID[00:00:ce:7b:8d:a7:79:4c]] in state MASTER
> 14:55:48.306 WARN [n.f.c.i.Controller:New I/O server worker #2-2]
> Unhandled OF Message: ofmsg:v=1;t=ERROR;l=105;x=0 from OFSwitchBase
> [/x.x.x.x:35055 DPID[00:00:ce:7b:8d:a7:79:4c]]
> 14:55:48.306 ERROR [n.f.c.i.OFChannelHandler:New I/O server worker #2-2]
> Error OFPET_BAD_ACTION OFPBAC_EPERM from switch OFSwitchBase
> [/x.x.x.x:35055 DPID[00:00:ce:7b:8d:a7:79:4c]] in state MASTER
> 14:55:48.306 WARN [n.f.c.i.Controller:New I/O server worker #2-2]
> Unhandled OF Message: ofmsg:v=1;t=ERROR;l=105;x=0 from OFSwitchBase
> [/x.x.x.x:35055 DPID[00:00:ce:7b:8d:a7:79:4c]]
>
> Thanks in advance
>
> Jen-Wei
>
> _______________________________________________
> openflow-discuss mailing list
> openflow-discuss@lists.stanford.edu
> https://mailman.stanford.edu/mailman/listinfo/openflow-discuss
>
>
_______________________________________________
openflow-discuss mailing list
openflow-discuss@lists.stanford.edu
https://mailman.stanford.edu/mailman/listinfo/openflow-discuss
