On Tue, Jul 14, 2015 at 11:39:17AM +0530, Saloni Jain wrote: > Thanks for the reply. > Please help me understand below points: > As per openflow specification 1.4, Page 72 "The flag OFPTC_VACANCY_EVENTS > control vacancy events in that table (see 7.4.5). If this flag is set, the > switch must generate vacancy events for that table. If this flag is unset, > the switch must not generate those events. Parameters for vacancy events may > be specified using the OFPTMPT_VACANCY property." > > This means that OFPTC_VACANCY_EVENTS is property for the table and not for > per-OpenFlow connection basis. > > Regarding the events, then only those controller will get vacancy events > which have OFPT_TABLE_STATUS messages set on using "set-async configuration" > OFPT_SET_ASYNC. > Page 121 of openflow 1.4 says that "The OFPT_SET_ASYNC message sets whether a > controller should receive a given asynchronous message that is generated by > the switch. Other OpenFlow features control whether a given message is > generated; for example, the OFPFF_SEND_FLOW_REM flag in each flow entry > controls whether the switch generates a OFPT_FLOW_REMOVED message when a flow > entry is removed. The asynchronous configuration acts as an additional > per-controller filter; for example it defines if a specific controller > receives those OFPT_FLOW_REMOVED messages." > > So as per my understanding OFPTC_VACANCY_EVENTS set as config property will > generate vacancy_events using OFPT_TABLE_STATUS message type and reason > OFPTR_VACANCY_DOWN/OFPTR_VACANCY_UP for that table, but only those controller > will receive those events which have OFPT_TABLE_STATUS messages turned on via > OFPT_SET_ASYNC message.
OK, let's do it that way. _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
