Thanks for your post James.
We just experienced a partial meltdown due to this issue with Microsoft SCCM 2012 causing MAC's to be spoofed. This was confusing the hell out of our switches and causing rolling blackouts:
https://supportforums.cisco.com/discussion/11835361/mac-address-flapping-and-sccm-wake-proxy
This explains that when clients were going to sleep, the issue was worse. Apparently Microsoft use some sort of election process to work out which PC on the local subnet becomes the "MAC spoofing master".
We only found the problem by getting Wireshark out - the first thing that jumped out was some clients pinging all others on the local subnet and ARP'ing to find each other's MAC's. Normally a client has no reason to speak to another client, most traffic should be client to server.
The PC's sending out all the pings were also recieving lots of TCP SYN's on port 25536 from other PC's on the LAN. SCCM's SleepAgentService.exe was the process running on port 25536 on the affected workstation.
Now I have an explanation for why the link flaps also.
🙂
Whoever at Microsoft thought MAC spoofing was a good idea needs their head examined! It might work fine on a $50 Netgear or D-Link, but it's going to cause severe issues on enterprise grade switches from any manufacturer.
More here:
https://social.technet.microsoft.com/Forums/en-US/a0ba31d1-e3cc-4218-80ee-f67583fb4ddd/client-settng...
The funny thing is while looking at this problem I kept thinking it was the type of thing malware would do (or at least rather bizzare malware) - guess I wasn't too far from the truth!
Thanks,
Mark