Nexus 5548 - %ARP-3-DUP_SRCIP_PROBE: Duplicate address Detected

Question

Hello.
Looking for some assistance on the following please, I'll try to include a lot of detail:
I noticed we're receiving repeating messages on a pair of Nexus 5548UP switches, regarding duplicate IP's, and the IP's in question are the mgmt0 of each respective Nexus switch; which are connected to each other and uplinked to two 3750X switches which are also linked to each other (not as a stack, with optics).
Here is a sample of the syslog message:  %ARP-3-DUP_SRCIP_PROBE:  arp [####]  Duplicate address Detected. Probe  packet received from zzzz.zzzz.zzzz on mgmt0 with destination set to our local ip, xxx.xxx.xxx.xxx
And in ascii art, here is a diagram:  SW1&2 are 3750X (running 15.x code) and NX1&2 are Nexus 5548UP (running 6.x code)
SW1---SW2
|           |
NX1---NX2
Pretty basic box/"ring", just in case the diagram doesn't format well, with rapid spanning-tree in effect.  The Nexus are Layer2 only, and the 3750X's are Layer 2 & 3 /w HSRP on a few SVI's in them.  All vlans can pass over the connecting trunks.  And on the Nexus, the management interface (mgmt0) is connected to 3750X (NX1 to SW1 and NX2 to SW2); e.g. management is done over this vrf interface, versus it flowing through a trunk interface to a SVI on the Nexus.
I know these messages to be erroneous as far an being actual duplicate IP's on the network, and have seen a few posts that indicate a command ("no ip arp gratuitous hsrp duplicate") typically referencing a Nexus 7000 setup has helped, but obviously as described that's not involved here.  Note: Placing that command on the mgmt0 interface of the two nexus had no positive effect.  The messages didn't start showing until after HSRP was enabled on the applicable 3750X SVI's - so seems a likely correlation.
Essentially looking to clear this up (ideally) or suppress the messages since they're false.  Any ideas?
Thanks!

Answer 1

For those encountering this same issue, here is some information that may lead you to a resolve.
I decided to open a TAC case to get some direct assistance, and I was directed to the 3750X's and a new feature in the 15.x code, "ip device tracking".  I was directed to remove that without specific details / steps on how to best do it (e.g. "no ip device tracking" does not remove it from the global config, as of 15.2(1)E anyway and is the most current at the time of this posting), and that didn't take, giving the message: % IP device tracking is disabled at the interface level by removing the relevant configs.  However, after doing some research on the command, I can across some similar posts on 15.x code and duplicate IP messages.... Here's two posts I referenced:
https://supportforums.cisco.com/thread/2244042
https://supportforums.cisco.com/thread/2239656
I opted for the "no macro auto monitor" command in the 3750X's in global config, as mentioned in the above post(s) - This did stop the messages from occurring in the Nexus switches.  IMPORTANT NOTE:  I noticed that it did appear to bounce all the switch ports however, which could impact production - Be advised!
I cannot speak to if the interface level command 'nmsp attach suppress' is a better route to go, which is also referenced in the posts (first one primarily) - I went the other route to not have all the extra config line entries.  I have asked Cisco what the true impact of the "no macro auto monitor" command is, and am waiting a response - Ideally there's little to none, probably depending on if you want to make use of device tracking or not... in my case, I suspect I don't have a need for this and thus there's no impact - I shall see.
It would be ideal if code is released to disable this service / feature in the future more gracefully and/or code changes are done to remedy this issue so you can have the feature enabled (or not).  I akin this much like the "vstack" service that was introduced around 12.2(55/58)SE IOS that couldn't be disabled & left an open TCP port (not good for security scans), then with 12.2(58)SE2 they allowed it to be disabled (e.g. "no vstack" in global config).
Hopefully these details prove of value.
Regards.
NOTE:  Since it doesn't seem you can"answer" your own posts, which seems silly; please note I consider this item resolved / answered.