This is normal occurrence with wireless users as they may connect to the network via different APs at different times. Both APs are probably not connecting to the same core switch and that's the reason switch logs this error message.
If you want to stop this you need to configure the laptops to use a particular AP rather than any available AP.
Let's say you have AP1, AP2, switch1, switch2, wireless userZ. AP1 connects to switch1 and AP2 connects to switch2.Switch1 and switch2 are interconnected.
UserZ connects to switch1 through AP1. Switch2 would know that it can reach userZ via switch1. UserZ disconnects and reconnects to switch2 via AP2. At this point switch2 would say, wait a minute I was seeing userZ connected through a different port earlier and now it's a different port. It generates this log message as a warning that there could be a potential problem out there in the network. This symptom can also occur if there's a spanning tree issue but not in your case though.
We are pleased to announce availability of Beta software for 16.6.3.
16.6.3 will be the second rebuild on the 16.6 release train targeted
towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are
looking for early feedback from customers befor...
Introduction Featured Speakers Luis Espejel is the Telecommunications
Manager of IENova, an Oil & Gas company. Currently he works with Cisco
IOS® and Cisco IOS XE platforms, and NX to some extent. He has also
worked as a Senior Engineer with the Routing P...
In this session you can learn more about Layer 3 multicast and the best
practices to identify possible threats and take security measures. It
provides an overview of basic multicast, the best security practices for
use of this technology, and recommendati...