Hi Ben, The above observation was taken from my testing.
Steps to reproduce the issue: 1) Configure an openflow bridge and associate two ports into the openflow bridge. 2) Now, shut down any one of the interface and the port shutdown message should be sent to the Controller. 3) OVS doesn't send it to the Controller hence both the ports are shown as active on the controller. Please let me know if you need any help on this. Thanks, Kals. On Wed, Oct 7, 2015 at 8:37 PM, Ben Pfaff <b...@nicira.com> wrote: > On Wed, Oct 07, 2015 at 11:21:05AM +0530, tech_kals Kals wrote: > > Assume when any Openflow agent uses OVS openflow stack to interact with > > the controller. When port is configured admin down in the hardware. > > Openflow agent wants to inform the controller about the port shut hence > it > > will send port shutdown message to OVS. It is the responsibility of OVS > to > > send the same message to Controller. > > > > In OVS code, i dont see, port shutdown message is not being handled. > > > > In the code, Openflow agent would call any of the function pointer > which > > is defined in ofproto_dpif_class. > > > > In ofproto_dpif_class, "port_reconfigured" is handling port shutdown > > event. The same function needs to inform the controller about port > shutdown. > > > > But, the definition of it says that it will not handle, i have > > highlighted the same. Please note that "*OFPUTIL_PC_PORT_DOWN"* is being > > used to set/unset the flag when port is configured as admin down. > > Why all this speculation? Test it and see. > _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev