On Dec 8, 2013, at 6:18 PM, Jayanth Silesh <jayanthsileshs.for...@gmail.com> wrote:
> Hi Murphy, > > Question1: > > The problem is that I need the resubmit command in the flow_entry. > Say that there is already an entry in table 2 as > in_port=7,….,action= resubmit(,3). > > Is there a way that from table3, I can use the LEARN msg to ‘append’ an > action in the table 2 so that it becomes, > in_port=7,…..,action=( load(reg_5=7) ,resubmit(,3)) > > Will the learn action, add an entry or can it modify the existing entry in > the table? No. However, consider making the entry in table 2: in_port==7 : resubmit(table=11), resubmit(table=3) By default, have table 11 (a table chosen at random for the example) empty. You can use a learn action to learn an entry into it like... in_port==7 : load(field=reg5, value=7) .. and the result should be what you wanted. In the above case, the new table entry uses in_port to match against, but you could use a metafield instead if your match conditions are complicated. Picking the values 14 and 42 at random, in table 2 you'd have: in_port==7 : load(field=reg14, value=42), resubmit(table=11), resubmit(table=3) In table 11: reg14==42 : load(field=reg5, value=7) > Question2: > Is there a resubmit action on the Nicira extensions for NOX? No. There couldn't be. The problem isn't that POX doesn't support this. Open vSwitch itself doesn't support this. It's not part of the learn action by definition. (On top of that, no noxrepo version of NOX supports the learn action at all.) > Question3: > > How do load the register with some value, it’s throwing errors on this. Is > the naming convention for reg wrong? > > learn.spec.append(fms( field=nx.re51, load=7 )) As suggested in the last entry of the FAQ, you should post error messages. The registers are named like NXM_NX_REGx, and should also be accessible as NXM_NX_REG[x]. I think "x" is between 0 and 15 on most or all switches. -- Murphy > Thanks, > Jayanth > Graduate Student > USC > > > > On December 8, 2013 at 3:48:51 PM, Murphy McCauley > (murphy.mccau...@gmail.com) wrote: > >> meta_register_1
