cancel
Showing results for 
Search instead for 
Did you mean: 

Problems with disconnected AP's / Tunnel down

Problems with disconnected AP's / Tunnel down

Xiro
New Contributor
We have a customer with a Enterasys WLAN setup, including two C4110 and approx. 80 AP's of the model 3710. SW running is 08.21.04.0024.

The WLC's are located in a Datacenter and connected to six different Branch offices.
In the last few weeks we have some issues with some AP's in different locations:

The customer reports, that WLAN is not working. When we check the WLC, we see that the AP is connected, but the tunnel is not working properly and the radio interfaces are not sending out.

Earlier we could resolve the issue by setting/releasing admin mode, rebooting a few times, on/off transmit power, request channels -> after doing this irregularly for a few times, the AP's came up again. But now even this won't work anymore for two of them.

The AP is available via SSH, it's able to ping the WLC's and vice-versa. It's also correctly authenticating on the WLC according to the log-messages, but the radio simply won't go up.

ea326c097aa34b1aa8edaee4966d3391_RackMultipart20150122-16013-1uf7pz8-WLC_Log_inline.jpg



ea326c097aa34b1aa8edaee4966d3391_RackMultipart20150122-17214-b7dig1-Active_APs_inline.jpg



ea326c097aa34b1aa8edaee4966d3391_RackMultipart20150122-14253-zjxc5n-Ap-Parameters_inline.jpg



Is there any known workaround for this? We already tried once to replace the affected AP on one location, without any success. Simply doing the reboot process over and over again helped until now. The affected AP's are always different - sometimes one of a branch, sometimes two, but there is no recognizable pattern for the occurrence. In this case it's a bit dramatic, because the customer has only one AP at the location, which is used for some scanners that are now not working any more.

I hope someone has an idea 😕

Thanks in advance & BR,
Xiro

7 REPLIES 7

Ronald_Dvorak
Honored Contributor
if the AP isn't connected to the controller ssh (telnet for old APs) is enabled for troubleshooting by default,
So from the controller ssh/telnet to the AP and set the controller address with
cset authip 1 X.X.X.X
capply
csave

Before you do that enable all logs on the controller GUI > Controller > Logs > System Log Level > set it to infromational

If you have a MTU problem the log will look like the first screenshot in this post.
That is the last message for a successful tunnel connection setup is missing = "Blacklist successfully sent to Wireless APXXXXXXX"

If you now set the MTU to 1300 it should work.

Doug
Extreme Employee
Is it across a nat'd interface or through a VPN?
Doug Hyde
Director, Technical Support / Extreme Networks

Philip_Paxton
New Contributor
Hoping someone is still montoring this. But i have a similar issue except that I cannot get the AP to show as active at all. I registered it with the controller andt then shut it down and sent it out to the remote office.It will not show up even though i can ping it from the controller and can ping the controller for the same subnet that the AP is now on (did not think to turn on SSH). Will this MTU fix only if it can talk to the AP still? Or is changing the MTU only changing a controller side setting?

I hope this make sense.
Thanks in advance,
Phil

Xiro
New Contributor
Hi Kai,

thank you for the great advice, it helped instantly!

Thumbs up!
GTM-P2G8KFN