The following limitations apply to this release of the VM tracking feature:
When VM tracking is configured on a port, all existing learned MAC addresses are flushed. MAC addresses will be relearned by the switch and the appropriate VPP (if any) for each VM will be applied.
If a VM changes MAC addresses while moving between ports on a switch, the VM remains authenticated on the original port until the original MAC address ages out of the FDB.
VM counters are cleared when a VM moves between ports on the same switch (because the ACLs are deleted and recreated).
Each VPP entry supports a maximum of eight ingress and four egress ACL or policies.
For Network VPP, only policy files can be mapped. For Local VPP, either ACL or policy files can be mapped. You cannot map a mixture of both ACL and policy files to a particular VPP.