How controller decide the flow path? / flow not display in Dlux

asked 2016-03-28 02:24:05 -0800

luis999 gravatar image

hi,

i have create a custom topology in mininet and have install opendaylight.

setup custom mesh topology command: sudo mn --custom meshtopology.py --topo mytopo --controller=remote,ip=10.0.0.1

h1------------s1---------------s2----------------h2

          l   -\-    l

h3------------s3---------------s4----------------h4

links: (h1,s1) , (h2,s2), (h3,s3), (h4,s4), (s1,s2), (s1,s3), (s1,s4), (s2,s3), (s2,s4), (s3,s4)

on my opendaylight, i have install 'old-dlux-all' and 'odl-l2switch-switch-ui'.

i can view the flow that are added to the topology in mininet but i can't view flow in opendaylight Dlux(nodes --> flows).

to my knowledge "odl-l2switch-switch-ui'" help you to automatic add flow to your topology.

in this case should't opendaylight has the flows information in the Dlux.

mininet output (S1)

commnad: ovs-ofctl dump-flows s1

NXST_FLOW reply (xid=0x4):

cookie=0x2b00000000000024, duration=57.764s, table=0, npackets=12, nbytes=840, idleage=52, priority=2, inport=3 actions=output:2,output:1

cookie=0x2b00000000000026, duration=57.764s, table=0, npackets=11, nbytes=742, idleage=52, priority=2, inport=1 actions=output:3,output:2,CONTROLLER:65535

cookie=0x2b00000000000025, duration=57.764s, table=0, npackets=22, nbytes=1540, idleage=52, priority=2, inport=2, actions=output3,output:1

cookie=0x2b00000000000010, duration=63.749s, table=0, npackets=26, nbytes=2210, idleage=2, priority=100,dltype=0x88cc actions=CONTROLLER:65535

cookie=0x2b0000000000000f, duration=63.749s, table=0, npackets=3 nbytes=126, idle_age=59, priority=0 actions=drop

my question are

1) how does controller decide the flow path?

2) is there a way to see flow in Opendaylight Dlux?

many thanks in advance. :)

edit retag flag offensive close merge delete