[ovs-dev] Question about Port Mirroring (SPAN)
Aimal Khan
aimal.khan at xflowresearch.com
Tue Dec 27 07:39:34 UTC 2011
Hi,
I ran some tests with Open vSwitch's 'Port Mirroring' (SPAN) functionality
and I had some questions.
I am using ovs v1.1.2 in user-space on Ubuntu 11.10 machine.
Here is my set up
(Bridge IP:192.168.200.1)
PC-1(IP:192.168.200.3)--------(eth0)ovs(eth1)----------PC-2(IP:192.168.200.2)
(eth2)
|
|
|
PC-3(IP:192.168.3.1)
I want to mirror the packets sent/received port eth1 of switch to PC-3 (or
eth2)
I have tried three scenarios
1) In the first case ovs is in standalone mode.
Using the following commands for mirroring,
ovs-vsctl -- set Bridge br0 mirrors=@m \
-- --id=@eth1 get Port eth1 \
-- --id=@eth2 get Port eth2 \
-- --id=@m create Mirror name=mymirror @eth1
select-src-port=@eth1 output-port=@eth2
ovs-vsctl -- set Bridge br0 mirrors=@m \
-- --id=@eth1 get Port eth1 \
-- --id=@eth2 get Port eth2 \
-- --id=@m create Mirror name=mymirror @eth1
select-dst-port=@eth1 output-port=@eth2
I pinged PC2 from PC1, and packets were being mirrored on eth2/PC-3.
2) In second case I added 2 flows to the switch using the commands,
ovs-ofctl add-flows br0 in_port=1,actions=output:2
ovs-ofctl add-flows br0 in_port=2,actions=output:1
(these flows will forward the ping packets on the same ports as in
standalone mode)
and tried pinging and mirroring using the same commands above, but I am
unable to receive any packets on PC-3 (mirroring not working when flows are
written to switch).
3) In the last case I connected the switch to a controller(NOX zaku) and
added flows using the controller. Again using Ping+Mirroring fails to
mirror packets to PC-3/eth2.
Why are packets not being mirrored when flows are written to the switch? Is
it the expected behaviour or am I doing something wrong?
--
Aimal Khan
Development Engineer, xFlow Research
http://xflowresearch.com/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.openvswitch.org/pipermail/ovs-dev/attachments/20111227/4a9cfdb4/attachment-0003.html>
More information about the dev
mailing list