Check other spines in the same site to see if the entry is present.

If it is missing make sure that there is a contract relationship between the epg’s trying to communicate. On the spine check for a translation entry with “show dcimgr repo sclass-maps”. Translation entries on the spines are pushed as a result of a contract relationship between two epg’s or by having l2 stretch configured. This drop vector indicates that traffic is being received from the ISN with an SCLASS set that the spine does not have a translation entry for. Most commonly seen on spines in Multisite or RL setups. One common reason why traffic would be dropped for this condition would be if traffic is received on the switch coming from the fabric with the destination address set to an IP/mac that the switch has a remote learn for with no bounce flag. This typically indicates that the packet/frame is hitting a sup tcam index with a drop result.

Hopefully if you run into one of these codes this post will help you out. A colleague of mine put together an ELAM drop vector cheatsheet for the most common codes.

I recently wrote a post about how to ELAM in ACI.

Free for apple instal WinSCP 6.1.2