When an EVC has different client VLANs in the UNIs, it is changed in the first switch, then encapsulated with the service tag.
That implies in two set field actions in the same flow (first, the client VLAN is set, then a push vlan creates the service tag and finally the service tag value is set). This works with Open VSwitch, but does not work with Noviflow, and possibly with other vendors.
To avoid this problem, the suggestion is to change the client VLAN only in the last switch, after popping the service tag.
When an EVC has different client VLANs in the UNIs, it is changed in the first switch, then encapsulated with the service tag. That implies in two
set fieldactions in the same flow (first, the client VLAN is set, then apush vlancreates the service tag and finally the service tag value is set). This works with Open VSwitch, but does not work with Noviflow, and possibly with other vendors. To avoid this problem, the suggestion is to change the client VLAN only in the last switch, after popping the service tag.