FHRP isolation between data center networks that are connected over an OTV network is a two-step process;
the first prevents FHRP peering by filtering FHRP control packets across the overlay via a VLAN ACL. What is
the second step?
A.
Filter the FHRP MAC addresses that are being advertised by IS-IS.
B.
Remove the FHRP VLAN from the OTV extend-vlan list.
C.
Apply a VLAN to a route map that is applied to the OTV routing process.
D.
Disable the auto-population of the OTV MAC address table
http://jeffostermiller.blogspot.com/2013/01/fhrp-isolation-with-otv.html
Step 2: Apply a route-map to the OTV control protocol (IS-IS).
Even though HSRP traffic is filtered via the VACL defined in the step above, the vMAC used to source the HSRP packets is still learned by the OTV VDC. Therefore, OTV advertises this MAC address information to the other sites via an IS-IS update. While this in itself is not causing harm, it would cause the remote OTV the edge devices to see constant MAC moves happening for the vMAC (from the internal interface to the overlay interface and vice versa). To prevent these MAC moves from being advertised and allow for a cleaner design, the following OTV route-map has to be configured (once again, this configuration applies to HSRP version 1 and version 2).
http://www.cisco.com/c/en/us/td/docs/solutions/Enterprise/Data_Center/DCI/whitepaper/DCI3_OTV_Intro/DCI_1.html#wp1186074