Header Only - DO NOT REMOVE - Extreme Networks

shut down the socket


Userlevel 2
Hello community,

I have some strange logs :

[AP1] %%%%>08:39:51.786: migration:mu migration: sender shut down the socket (migration.c:741)
[AP2] %%%%>08:39:42.758: migration:mu migration: sender shut down the socket (migration.c:741)
[AP3] %%%%>08:39:48.145: migration:mu migration: sender shut down the socket (migration.c:741)

ect...

when running:
remote-debug wireless rf-domain default clients XX-XX-XX-XX-XX-XX duration 300 events all

It's a normal behavior ?

ap6532 wing 5.7.2

Thanks,

Aviv Kedem

5 replies

Userlevel 2
That behavior is normal, the device is Roaming and connected AP is sharing firewall session/mu cache with other APs.
Since you are capturing debug logs from the RFD you will see theses sort of messages in working environment.

Note:
In regards to the firmware version.
I highly recommend you upgrade to 5.8.5 or 5.9.1.4 depending on your controller/other ap hardware.
Userlevel 2
Daren Ellis wrote:

That behavior is normal, the device is Roaming and connected AP is sharing firewall session/mu cache with other APs.
Since you are capturing debug logs from the RFD you will see theses sort of messages in working environment.

Note:
In regards to the firmware version.
I highly recommend you upgrade to 5.8.5 or 5.9.1.4 depending on your controller/other ap hardware.

Hello Daren,

Does it mean the virtual controller always opens sockets for each client on all ap's on the rf domain/layer 1 mint OR just on the relevant ap's the client roams between them ?

How can I specify the lifetime of the sockets ?
There is some limitations about it?
Can I check the amount of open sockets and the lifetimes?

Thanks,

Aviv Kedem
Userlevel 2
Any suggestions?

Thanks

Aviv K
Userlevel 2
Anybody?
Userlevel 7
Hi Aviv,
Based on your two threads here, it sounds like you should probably contact GTAC so someone can take a closer look at your network to see what's going on.

Reply