Broadcast flood from IAPs to 215.129.0.0

Anyone have an idea why we would be seeing a flood of broadcast traffic coming from the IAPs and destined for 215.129.0.0 which is the US Naval Oceans Systems Center in Columbus, OH?

My customer did a packet capture from an IAP cluster in one of their campus dorms which was flooding their core switch. When I analyze the traffic and filter on aruba_iap and I see 56% of the packet capture traffic as broadcasts coming from the IAPs and destined for the 215.129.0.0 IP.