Wireless Access

Reply
Occasional Contributor I

Wireless clients switched between two controllers (next hop router moved from port)

Hi everybody, I have noticed a lot of messages at core switch like this:

 

Mar  7 11:31:42:D:next hop router 10.xx.xx100 moved from port 2/1/46 to port 1/1/45
Mar  7 11:30:54:D:next hop router 10.xx.xx100 moved from port 2/1/45 to port 2/1/46
Mar  7 09:57:08:D:next hop router 10.xx.xx100 moved from port 2/1/46 to port 1/1/45
Mar  7 09:55:56:D:next hop router 10.xx.xx100 moved from port 2/1/46 to port 2/1/45
Mar  7 09:52:54:D:next hop router 10.xx.xx100 moved from port 1/1/46 to port 2/1/45
Mar  7 09:24:44:D:next hop router 10.xx.xx100 moved from port 1/1/46 to port 2/1/45
Mar  7 09:12:38:D:next hop router 10.xx.xx100 moved from port 1/1/46 to port 1/1/45
Mar  7 09:12:17:D:next hop router 10.xx.xx100 moved from port 2/1/45 to port 1/1/46
Mar  7 08:38:05:D:next hop router 10.xx.xx100 moved from port 2/1/46 to port 2/1/45
Mar  7 08:37:06:D:next hop router 10.xx.xx100 moved from port 2/1/46 to port 2/1/45

 

IP address is a wireless client IP address.

And ports belong to master, and local controllers.

So, client is switched between them.

I have a stack of two switches on core layer, and two wireless controllers connected via LAG ports to each of them (master controller on core ports 1/1/45 and 2/1/45, and local controller on core ports 1/1/46 and 2/1/46).

Access level consist of switch stack, and two link are going to core layer.

 

Is it normal situation - f.e., when client moving between floors, and forget about these log messages, or it could be a network loop?

 

P.S. For active/active scenario I split building, and lower floors are registered on local controller first, and higher floors are registered on master controller.

So, if decide, that this client is moving between floors, it seems normally, but not so often...

Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: