if the NF-FG contains at least two rules with a match on the same port and actions on different ports of the same VNF then the graph is not deployed in a proper way.
Example of rules:
1) match: eth0, vlan=1; action=monitor:port1
2) match: eth0, vlan=2; action=monitor:port2
The bug is due to a wrong calculation of required vlinks to connect LSI0 and graphLSI:
the number of required vlinks is incremented by 1 every time that a new VNF appears as action, but it should be incremented every time that a new VNF PORT appears as action!
As a result, the number of vlinks calculated in the example above is 1, instead of 2.
if the NF-FG contains at least two rules with a match on the same port and actions on different ports of the same VNF then the graph is not deployed in a proper way. Example of rules: 1) match: eth0, vlan=1; action=monitor:port1 2) match: eth0, vlan=2; action=monitor:port2
The bug is due to a wrong calculation of required vlinks to connect LSI0 and graphLSI: the number of required vlinks is incremented by 1 every time that a new VNF appears as action, but it should be incremented every time that a new VNF PORT appears as action! As a result, the number of vlinks calculated in the example above is 1, instead of 2.