Remote AP's fail to connect to controller

[Craig_Sakach]

This is my first time working with Extreme Networks equipment so excuse any lack of knowledge I may have on these products.

The clinic I work for has 3 locations connected via WatchGuard Remote Office VPN. Subnets are as follows with the WatchGuard firewalls doing the routing:
Main Office: 172.20.1.0/24
Remote Office 1: 172.20.2.0/24
Remote Office 2: 172.20.3.0/24

We have a C25 Controller running v09.12.01.0067 located at the Main Office with IP 172.20.1.25.
We have 13 total AP-3825i AP's with 9 at the Main Office, and 2 at each Remote Office.

The Main Office has a Microsoft DHCP server and the Remote Office's get their DHCP addresses from their respective WatchGuard firewalls.

A security firm has control of the WatchGuard firewalls so I don't have direct access to their configuration and I'm not sure if the WatchGuard supports option 43. Because of this, it is why I took the following steps;

I installed the AP's at the Main Office and they connected up to the controller and are working beautifully! Because I couldn't add the Option 43 to the remote WatchGuard's, I connected the 4 Remote Office AP's to the Main Office network so they would obtain a DHCP address and configuration. Once the software was upgraded, I changed the IP's to manual IP's (172.20.2.x and 172.20.3.x) and set the controller IP as well.

I installed the AP's at the Remote Office locations but they show up on the controller as Inactive Local AP's even though I can ping and SSH into each AP from the Main Office. I can also ping the controller from the Remote Office's. This tells me that they are being seen on the network but something is keeping them from connecting to the controller properly.

Any idea's or suggestions is greatly appreciated!

[Doug]

Abdullah,

It's hard to say without reviewing the configurations you are using. That's why I suggested to contact the GTAC. This forum is not the best place for troubleshooting performance issues. If you would like to review a list of past or known issues you can search https://gtacknowledge.extremenetworks.com for the word performance. Be sure to select the Extreme Software Type: IdentiFi Wireless.

[abdullah_baniba]

Dear
i configured extreme wireless controller c35 with 5 ssid
but when i connected to each of them i suffered from high latency and low download
the the latency time for ping test unstable
please what can cause this prblem

[Doug]

Hello Abdullah, I would suggest contacting the GTAC so they can open a ticket and review your current settings/configurations. There are many reasons why this can occur.

Thanks,
Doug

[Samokhin_Nikita]

Hello there!
Could someone explain what does this log mean?
I have almost the same problem - got IP, however didn't get MAC of AP 😞

Jan 1 00:04:31 cap: 00217:ru_mgmt.c:2838-handle_discov_pkts()-Could not send pkb to RU_DISC thread!Jan 1 00:04:31 cap: 00217:ru_mgmt.c:2812-handle_discov_pkts()-Recv_bytes: 286
Jan 1 00:04:31 cap: 00217:ru_mgmt.c:2830-handle_discov_pkts()-receive 286 bytes data
Jan 1 00:04:31 cap: 00217:ru_mgmt.c:2838-handle_discov_pkts()-Could not send pkb to RU_DISC thread!
Jan 1 00:04:31 cap: 00217:ru_mgmt.c:2812-handle_discov_pkts()-Recv_bytes: 1042
Jan 1 00:04:31 cap: 00217:ru_mgmt.c:2830-handle_discov_pkts()-receive 1042 bytes data
Jan 1 00:04:31 cap: 00217:ru_mgmt.c:2838-handle_discov_pkts()-Could not send pkb to RU_DISC thread!
Jan 1 00:04:31 cap: 00217:ru_mgmt.c:2812-handle_discov_pkts()-Recv_bytes: 1042
Jan 1 00:04:31 cap: 00217:ru_mgmt.c:2830-handle_discov_pkts()-receive 1042 bytes data
Jan 1 00:04:31 cap: 00217:ru_mgmt.c:2838-handle_discov_pkts()-Could not send pkb to RU_DISC thread!
Jan 1 00:04:31 cap: 00217:ru_mgmt.c:2812-handle_discov_pkts()-Recv_bytes: 1042
Jan 1 00:04:31 cap: 00217:ru_mgmt.c:2830-handle_discov_pkts()-receive 1042 bytes data
Jan 1 00:04:31 cap: 00217:ru_mgmt.c:2838-handle_discov_pkts()-Could not send pkb to RU_DISC thread!
Jan 1 00:04:31 cap: 00217:ru_mgmt.c:2812-handle_discov_pkts()-Recv_bytes: 1042
Jan 1 00:04:31 cap: 00217:ru_mgmt.c:2830-handle_discov_pkts()-receive 1042 bytes data
Jan 1 00:04:31 cap: 00217:ru_mgmt.c:2838-handle_discov_pkts()-Could not send pkb to RU_DISC thread!
Jan 1 00:04:31 cap: 00217:ru_mgmt.c:2812-handle_discov_pkts()-Recv_bytes: 1042
Jan 1 00:04:31 cap: 00217:ru_mgmt.c:2830-handle_discov_pkts()-receive 1042 bytes data
Jan 1 00:04:31 cap: 00217:ru_mgmt.c:2838-handle_discov_pkts()-Could not send pkb to RU_DISC thread!
Jan 1 00:04:31 cap: 00217:ru_mgmt.c:2812-handle_discov_pkts()-Recv_bytes: 1042
Jan 1 00:04:31 cap: 00217:ru_mgmt.c:2830-handle_discov_pkts()-receive 1042 bytes data
Jan 1 00:04:31 cap: 00217:ru_mgmt.c:2838-handle_discov_pkts()-Could not send pkb to RU_DISC thread!
Jan 1 00:04:31 cap: 00217:ru_mgmt.c:2812-handle_discov_pkts()-Recv_bytes: 1042
Jan 1 00:04:31 cap: 00217:ru_mgmt.c:2830-handle_discov_pkts()-receive 1042 bytes data
Jan 1 00:04:31 cap: 00217:ru_mgmt.c:2838-handle_discov_pkts()-Could not send pkb to RU_DISC thread!
Jan 1 00:04:31 cap: 00217:ru_mgmt.c:2812-handle_discov_pkts()-Recv_bytes: 1042
Jan 1 00:04:31 cap: 00217:ru_mgmt.c:2830-handle_discov_pkts()-receive 1042 bytes data
Jan 1 00:04:31 cap: 00217:ru_mgmt.c:2838-handle_discov_pkts()-Could not send pkb to RU_DISC thread!
Jan 1 00:04:31 cap: 00217:ru_mgmt.c:2812-handle_discov_pkts()-Recv_bytes: 1042
Jan 1 00:04:31 cap: 00217:ru_mgmt.c:2830-handle_discov_pkts()-receive 1042 bytes data
Jan 1 00:04:31 cap: 00217:ru_mgmt.c:2838-handle_discov_pkts()-Could not send pkb to RU_DISC thread!
Jan 1 00:04:31 cap: 00217:ru_mgmt.c:2812-handle_discov_pkts()-Recv_bytes: 1042
Jan 1 00:04:31 cap: 00217:ru_mgmt.c:2830-handle_discov_pkts()-receive 1042 bytes data
Jan 1 00:04:31 cap: 00217:ru_mgmt.c:2838-handle_discov_pkts()-Could not send pkb to RU_DISC thread!
Jan 1 00:04:31 cap: 00217:ru_mgmt.c:2812-handle_discov_pkts()-Recv_bytes: 44
Jan 1 00:04:31 cap: 00217:ru_mgmt.c:2830-handle_discov_pkts()-receive 44 bytes data
Jan 1 00:04:31 cap: 00217:ru_mgmt.c:2838-handle_discov_pkts()-Could not send pkb to RU_DISC thread!
Jan 1 00:04:31 cap: 00217:ru_mgmt.c:2812-handle_discov_pkts()-Recv_bytes: 44
Jan 1 00:04:31 cap: 00217:ru_mgmt.c:2830-handle_discov_pkts()-receive 44 bytes data
Jan 1 00:04:31 cap: 00217:ru_mgmt.c:2838-handle_discov_pkts()-Could not send pkb to RU_DISC thread!
Jan 1 00:04:31 cap: 00217:ru_mgmt.c:2812-handle_discov_pkts()-Recv_bytes: 44
Jan 1 00:04:31 cap: 00217:ru_mgmt.c:2830-handle_discov_pkts()-receive 44 bytes data
Jan 1 00:04:31 cap: 00217:ru_mgmt.c:2838-handle_discov_pkts()-Could not send pkb to RU_DISC thread!

Reboot is needed due to config change: FALSEAP authentication is needed due to config change: FALSE
sysName "AP3705i"
acSiteName ""
lastAcIp 10.10.12.3
dnsIpAddress 1 77.234.194.2
#site cfg:
site disabled
dhcp lease 86400(s)
dhcp lease time renewal 39 left 86284(s)
wipsMode 0
Real capture off
timeServer
LEDMode Normal
macFilterMode Deny
AP ThirdPartyMode 0
AP TunnelMode 1
Wassp VlanVid: -1
countryCode 643
broadcastDisassociation 0
modePersistence 0
linkPersistence 1
pollTimeout 15000
pollInterval 3000
ssh mode enable (1)
ssh timeout 180
password $1$.bwL4$Own82WonXWgXrcl89e7aQ1
slpuRetry 3
slpuTimeout 3
dnsRetry 3
dnsTimeout 3
slpmRetry 3
slpmTimeout 3
globalRetry 3
globalTimeout 3
LLDP disable (0), TimeToLive:120,AnnouncementIntervall:30,AnnouncementDelay:2
logAlarm severity major (4)
apName 14210417915V0000
hostName AP3705i-14210417915V0000
apDesc
Ethernet(Phy): Speed:100 Duplex:full Auto:on Link:on
Ethernet (apcfg): Speed auto
authIpAddr 1 77.234.194.6
failover bmIp [1] 10.10.12.3 Home
failover bmIp [1] 10.10.12.2 Foreign
dhcp mode enable (1)
ip 10.10.12.2
mask 255.255.255.0
gateway 10.10.12.1
eth0 MAC 20:B3:99:CD:49:8D
Static MTU 1500
Jumbo Frame: Disabled
MIC Error Threshold 2
IASDNSPrefix 1
airfairLevel 4
radio 0 antennaType left 0x0 middle 0x0 right 0x0
radio 1 antennaType left 0x0 middle 0x0 right 0x0
radio 2 antennaType left 0x0 middle 0x0 right 0x0
outDoorChan 0
High Throughput HT capability for WEP and TKIP is disable (0)
Sending HT on all Probe Response is disable (0)
lbsSrcIp 0.0.0.0
lbsSrcPort 1144
lbsDstIp 0.0.0.0
lbsDstPort 0
lbsMcast 00:00:00:00:00:00
lbsTagMode 2
SNMP SERVER ENABLE disable
interAPRoam 0
clusterEncryption 1
clusterPassword 1cf469ac
Band Preference Admin Disabled (raw bitmap 0 0 ) Oper Disabled
radioPreferenceTimeout 300
bandPreferenceAssocThreshold 0
bandPreferenceAssocPeriod 0
AC Mgmt Mac Addr 00:1e:67:a6:a7:bb
Mesh RSSI Sample Window integer of power 2 3
Mesh Link Quality Check Timer 1
Mesh Stability Factor 20
isMesh 0
Sniffer radio bitmap 0x0
AP role 0
Multicast Assembly: Disabled
Location Service: Disabled
Location Auto Collect: Disabled
Location Ondemand MAC List is empty, 0 MAC addresses
FixedAppPolicy Table: appId 1 numFields 1
FixedAppPolicy Table: appId 1 index 0 offset 0x0 mask 0x8000 val 0x0
FixedAppPolicy Table: appId 2 numFields 1
FixedAppPolicy Table: appId 2 index 0 offset 0x0 mask 0x8000 val 0x8000
FixedAppPolicy Table: appId 3 numFields 2
FixedAppPolicy Table: appId 3 index 0 offset 0x0 0x1 mask 0xffffffff 0xffffffff val 0x4d2d5345 0x41524348
FixedAppPolicy Table: appId 4 numFields 2
FixedAppPolicy Table: appId 4 index 0 offset 0x0 0x1 mask 0xffffffff 0xffff0000 val 0x4e4f5449 0x46590000
FixedAppPolicy Table: appId 5 numFields 1
FixedAppPolicy Table: appId 5 index 0 offset 0x0 mask 0xffffffff val 0x0
FixedAppPolicy Table: appId 6 numFields 1
FixedAppPoli

[Martin_Perez]

ha resuelto su problema?