That's right Ryan, this is Nitrogen-SR2. If nobody has experienced this, can somebody please point me to where the Openflow Plugin VLAN validation code is? That is, there must be a Config Data Store listener that validates the flows, and if there is something it doesnt like, it wont write the flows to the Operational data store. I would like to see what it considers as valid/invalid for flows with setVlanId and popVlan actions.
Regards, *Brady Johnson* [email protected] <https://twitter.com/inocybetech> <http://www.inocybe.com/> <https://www.linkedin.com/company/2661537?trk=tyah&trkInfo=clickedVertical%3Acompany%2CclickedEntityId%3A2661537%2Cidx%3A1-1-1%2CtarId%3A1441300264767%2Ctas%3Ainocybe> [image: Screenshot 2017-02-14 at 10.43.55 AM.png] <https://www.youtube.com/channel/UC9uUWABdPR0Je9Du_15FCkw> On Sat, Apr 14, 2018 at 7:02 PM, Ryan Goulding <[email protected]> wrote: > IIRC this is based off Nitrogen-SR2, so shouldn't be prone to the issues > listed there. > > Thanks! > > Regards, > > Ryan Goulding > > On Sat, Apr 14, 2018 at 6:52 PM, M. Ranganathan <[email protected]> wrote: > >> >> >> Not sure if this would help ( I was trying something a little different >> than you are ) but I had some issues creating set Vlan flows in Carbon >> https://stackoverflow.com/questions/47610513/how-to-create- >> a-set-vlan-flow >> >> I had much better luck with Nitrogen >> >> >> >> Ranga >> >> On Fri, Apr 13, 2018 at 5:42 PM, Brady Johnson <[email protected]> >> wrote: >> >>> >>> Hello, >>> >>> Im trying to write flows to pop-vlan or just simply set the vlan-id, but >>> the flows arent being written to operational, nor the bridge. I tried doing >>> an etherType match on VLAN (0x8100) but that doesnt help. >>> >>> The 2 use cases I have are for flows that ingress the bridge with VLAN >>> already set are: >>> >>> 1) if VLAN present (could be lots of different vlan IDs), pop it. >>> 2) if VLAN present set the VLAN id to a different one. >>> >>> Ive tried flows for both of these cases, and neither are written to >>> Operational. Ideally there should be an 802.1Q TPID (Tag protocol ID) match >>> field, where you could match on 0x8100, but I couldnt find anything like >>> this. >>> >>> Regards, >>> >>> *Brady Johnson* >>> [email protected] >>> >>> <https://twitter.com/inocybetech> <http://www.inocybe.com/> >>> <https://www.linkedin.com/company/2661537?trk=tyah&trkInfo=clickedVertical%3Acompany%2CclickedEntityId%3A2661537%2Cidx%3A1-1-1%2CtarId%3A1441300264767%2Ctas%3Ainocybe> >>> [image: >>> Screenshot 2017-02-14 at 10.43.55 AM.png] >>> <https://www.youtube.com/channel/UC9uUWABdPR0Je9Du_15FCkw> >>> >>> >>> >>> _______________________________________________ >>> openflowplugin-dev mailing list >>> [email protected] >>> https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev >>> >>> >> >> >> -- >> M. Ranganathan >> >> >> _______________________________________________ >> openflowplugin-dev mailing list >> [email protected] >> https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev >> >> >
_______________________________________________ openflowplugin-dev mailing list [email protected] https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev
