Support for Virtual Link Extension (vLE) Analytics
Currently, Netvisor ONE does not copy vLE traffic control frames to the CPU on the switch. Netvisor ONE does not remove the inner tag, if present. Netvisor ONE achieves this by installing a system vFlow, Virtual-Link-Extend, with highest priority 15 with no action specified so that Netvisor ONE does not terminate LLDP or other control frames and send to CPU.
To support vLE analytics, Netvisor ONE installs a few additional system vFlows with the same priority as the existing Virtual-Link-Extend vFlow to copy TCP-SYN/FIN/RST packets to CPU. This ensures that any vLE-SYN/FIN/RST packets target System-vLE-x flows and not Virtual-Link-Extend flow.