Luis, Here are the flows on all the three switches. Port 1 of each switch is corresponding to the NIC going into LAN and Port 2 of Switch is an OVS internal port.
*Switch A* OFPST_FLOW reply (OF1.3) (xid=0x2): cookie=0x2b0000000000000d, duration=77662.413s, table=0, n_packets=62132, n_bytes=6896652, priority=100,dl_type=0x88cc actions=CONTROLLER:65535 cookie=0x2b00000000000028, duration=77658.417s, table=0, n_packets=99, n_bytes=8398, priority=2,in_port=1 actions=output:2 cookie=0x2b00000000000029, duration=77658.413s, table=0, n_packets=0, n_bytes=0, priority=2,in_port=2 actions=output:1,CONTROLLER:65535 cookie=0x2b0000000000000d, duration=77662.413s, table=0, n_packets=0, n_bytes=0, priority=0 actions=drop *Switch B* cookie=0x2b0000000000000b, duration=77874.071s, table=0, n_packets=31158, n_bytes=3396270, priority=100,dl_type=0x88cc actions=CONTROLLER:65535 cookie=0x2b00000000000026, duration=77826.107s, table=0, n_packets=0, n_bytes=0, priority=2,in_port=2 actions=output:1,CONTROLLER:65535 cookie=0x2b00000000000027, duration=77826.107s, table=0, n_packets=102, n_bytes=8755, priority=2,in_port=1 actions=output:2 cookie=0x2b0000000000000b, duration=77874.071s, table=0, n_packets=9, n_bytes=768, priority=0 actions=drop *Switch C* cookie=0x2b00000000000001, duration=78057.189s, table=0, n_packets=31225, n_bytes=3403591, priority=100,dl_type=0x88cc actions=CONTROLLER:65535 cookie=0x2b00000000000022, duration=77972.554s, table=0, n_packets=28, n_bytes=2921, priority=2,in_port=1 actions=output:2 cookie=0x2b00000000000023, duration=77972.554s, table=0, n_packets=0, n_bytes=0, priority=2,in_port=2 actions=output:1,CONTROLLER:65535 cookie=0x2b00000000000001, duration=78057.189s, table=0, n_packets=0, n_bytes=0, priority=0 actions=drop Regards, Amit On Wed, Aug 16, 2017 at 7:45 PM, Luis Gomez <ece...@gmail.com> wrote: > Can you please post the flows you see in the OF switches? > > On Aug 16, 2017, at 3:02 AM, Amit Kumar <ebiib...@gmail.com> wrote: > > Hi Luis, > > I have installed odl-l2switch-switch and odl-restconf-all features apart > from odl-dlux-core. > > Regards, > Amit > > On Aug 15, 2017 10:22 PM, "Luis Gomez" <ece...@gmail.com> wrote: > > Hi Amit, which features do you install in controller? > > On Aug 15, 2017, at 5:19 AM, Amit Kumar <ebiib...@gmail.com> wrote: > > Hello All, > > Could you guys provide your response, is it an expected behavior? I am > facing this behavior in both Beryllium and Carbon. > > Regards, > Amit > > On Mon, Aug 14, 2017 at 12:26 PM, Amit Kumar <ebiib...@gmail.com> wrote: > >> Hi All, >> >> I am an end user of ODL. I have a query regarding topology discovery in >> ODL. I understand that LLDP is being used for link discovery between >> Switches and further N/w topology is computed based on that. In my setup, >> three OF Switches (let us say A, B and C) are on a lan. >> >> So, once all these switches connect to ODL, it should show me the >> bidirectional links A-B, B-C, C-A in DLUX GUI or when I query using >> following RESTCONF API. >> http://<controller-ip>:8080/restconf/operational/network-top >> ology:network-topology/ >> >> But I am not able to see all these links at all times, N/w topology in >> DLUX GUI rarely shows all these links and again after some time some of >> them disappears. Wireshark is showing all the LLDP packets (from each >> other) being received every 5s at Controller as PACKET_IN. >> >> Could you guide that what could be the reason behind this random behavior. >> >> Regards, >> Amit >> > > _______________________________________________ > L2switch-dev mailing list > l2switch-...@lists.opendaylight.org > https://lists.opendaylight.org/mailman/listinfo/l2switch-dev > > > > >
_______________________________________________ controller-dev mailing list controller-dev@lists.opendaylight.org https://lists.opendaylight.org/mailman/listinfo/controller-dev
