ap 1815i

Alex_rt · ‎04-11-2019

Hello!

I have a problem with ap AIR-AP1815I-R-K9

i have 2 AP and they have same firmware

cisco AIR-AP1815I-R-K9 ARMv7 Processor rev 5 (v7l) with 1015824/668048K bytes of memory.
Processor board ID FGL2237B10G
AP Running Image : 8.8.120.0
Primary Boot Image : 8.8.120.0
Backup Boot Image : 8.8.120.0
Primary Boot Image Hash: 01baa4dc5e200f50c5100e422f1444f8b35b11c8f295de2a3567589a8e82ec003c898a3d75ba59c1422b2906dba55558893b53f48c52d7e9bd74be5a76f0e40d
Backup Boot Image Hash: be79185a2d07f0949829dda507086c83153e0d906c5edf625f73a44b4ab410793520044f7d77034478622700f4ce9d05e090b256b917a061553beedbf52ae9a3
AP Image type : MOBILITY EXPRESS IMAGE
AP Configuration : MOBILITY EXPRESS CAPABLE
1 Gigabit Ethernet interfaces
2 802.11 Radios
Radio FW version : 1fdd5a71aaea29d5ce69b095bba594c5
NSS FW version : not available

Base ethernet MAC Address : 00:EA:BD:DC:25:B0
Part Number : 0-0000-00
PCA Assembly Number : 074-105850-02
PCA Revision Number : 0
PCB Serial Number : FOC223384U3
Top Assembly Part Number : 074-105850-02
Top Assembly Serial Number : FGL2237B10G
Top Revision Number : A0
Product/Model Number : AIR-AP1815I-R-K9

One of them boot first and came the Primery Controller, i have access to it from web bowser , here it's ok.

When the second AP is up, as i understand, it should choose who will be a master , but the second AP don't join to WLC.

All AP and WLC in the same VLAN, all devices ping.

I have DNS and DHCP service for this vlan.

Web Interface of WLC i don't see my second AP.

What should i do?

patoberli · ‎04-11-2019

Can you attach a console cable to the second AP and reboot it and show us the full boot process? It should show what happens while it's trying to associate.
You have selected a -R- compatible country on the Master?

Alex_rt · ‎04-11-2019

yes i select RU on Master AP

I switched from ME to Capwap mode

in attach boot log

patoberli · ‎04-11-2019

Is 192.168.102.4 the IP address of your Master AP?
I think the AP needs to be in ME mode, not CAPWAP.
See here for details: https://www.cisco.com/c/en/us/td/docs/wireless/controller/technotes/8-8/b_cisco_mobility_express_8_8/b_cisco_mobility_express_8_8_chapter_01.html

Alex_rt · ‎04-11-2019

i already switch to ME mode the second AP .

No effect.

[*04/11/2019 14:18:56.6699] CAPWAP State: Discovery
[*04/11/2019 14:18:56.6699] IP DNS query for CISCO-CAPWAP-CONTROLLER.rtreg
[*04/11/2019 14:18:56.6699] DNS resolved CISCO-CAPWAP-CONTROLLER.rtreg
[*04/11/2019 14:18:56.6699] DNS discover IP addr: 192.168.102.4
[*04/11/2019 14:18:56.6799] Discovery Request sent to 192.168.102.4, discovery type DNS(3)
p[*04/11/2019 14:18:56.6999] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)
[*04/11/2019 14:18:56.7099] DOT11_DRV[0]: Channel set to 1, width 20
[*04/11/2019 14:18:56.7099] DOT11_DRV[0]: Channel set to 1, width 20
[*04/11/2019 14:18:56.7199] DOT11_DRV[1]: Channel set to 36, width 20
[*04/11/2019 14:18:56.7199] DOT11_DRV[1]: Channel set to 36, width 20
[*04/11/2019 14:18:56.7199] Failed to load flex vap config from file. Default config will be used.
[*04/11/2019 14:18:56.7299] Flexconnect Switching to Standalone Mode!

On WLC i don't see the second AP

see attch

patoberli · ‎04-11-2019

Your output is to short, can you run it a little longer?
I assume the Master is in the same VLAN?
You don't have another WLC running?
192.168.102.4 is the IP address of the Master?

Alex_rt · ‎04-11-2019

@patoberli wrote:
Your output is to short, can you run it a little longer?

What about out put didi you say?
@patoberli wrote:
I assume the Master is in the same VLAN?
You don't have another WLC running?
192.168.102.4 is the IP address of the Master?
Yes ME WLC 192.168.102.4 is a Master
ALL AP in same vlan, switchport is access mode, no trunk.
No i don't have any WLC .
Befor i tried tune WLC on my 3850 switch , but they told me, that this AP don't supported.
and I swiched off the WLC on my 3850switch.

patoberli · ‎04-12-2019

Oh so you do have a WLC...
But it indeed is not supported.

Can you reboot one of the client AP again and let the console output run some more minutes?
I wonder what appears after those lines:
[*04/11/2019 14:18:56.7199] Failed to load flex vap config from file. Default config will be used.
[*04/11/2019 14:18:56.7299] Flexconnect Switching to Standalone Mode!

Alex_rt · ‎04-12-2019

@patoberli wrote:
Oh so you do have a WLC...
But it indeed is not supported.

Can you reboot one of the client AP again and let the console output run some more minutes?
I wonder what appears after those lines:
[*04/11/2019 14:18:56.7199] Failed to load flex vap config from file. Default config will be used.
[*04/11/2019 14:18:56.7299] Flexconnect Switching to Standalone Mode!

Nothing happens

User Access Verification
Username: [*04/12/2019 08:40:47.5999] Password for user changed
[*04/12/2019 08:40:48.2099] DOT11_TXP[0]:Domain configured: 1 class:E
[*04/12/2019 08:40:48.3199] DOT11_TXP[0]:Domain configured: 42 class:R
[*04/12/2019 08:40:49.8099] DOT11_DRV[1]: Init Radio1
[*04/12/2019 08:40:49.8399] Public key portion is:
[*04/12/2019 08:40:49.8399] ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQC9e7tkBoelLbEiAQLyCwejxfbbVvQhNx1KOUJ/uOQ5hMqIt1Nb3D46xQNQi5FO74nlZ939v3sWjD3K9Zbm26LAQ5ciIiz2m4twuHAYZOU/j/NbA37 root@ap01
[*04/12/2019 08:40:49.8399] Fingerprint: sha1!! 2f:67:7c:37:5e:af:f0:c4:80:92:6b:e8:b2:75:80:08:09:8b:40:84
[*04/12/2019 08:40:49.8499] DOT11_DRV[1]: Stop Radio1
[*04/12/2019 08:40:49.8499] DOT11_DRV[1]: set_channel Channel set to 36
[*04/12/2019 08:40:49.8699] CRIT-MeshControl:
[*04/12/2019 08:40:49.8699] Mesh Control: skipped adding wired1 backhaul
[*04/12/2019 08:40:49.8799] DOT11_DRV[0]: Init Radio0
[*04/12/2019 08:40:49.9199] DOT11_DRV[0]: Stop Radio0
[*04/12/2019 08:40:49.9299] DOT11_DRV[0]: set_channel Channel set to 6
[*04/12/2019 08:40:50.7199] DOT11_CFG[0] Radio Mode is changed from Local to FlexConnect
[*04/12/2019 08:40:50.7299] DOT11_CFG[0]: Starting radio 0
[*04/12/2019 08:40:50.7399] DOT11_DRV[0]: Start Radio0
[*04/12/2019 08:40:50.7399] DOT11_CFG[1] Radio Mode is changed from Local to FlexConnect
[*04/12/2019 08:40:50.7399] DOT11_CFG[1]: Starting radio 1
[*04/12/2019 08:40:50.7399] DOT11_DRV[1]: Start Radio1
[*04/12/2019 08:40:50.7499] DOT11_DRV[0]: Stop Radio0
[*04/12/2019 08:40:50.9699] DOT11_DRV[0]: set_channel Channel set to 1
[*04/12/2019 08:40:50.9899] DOT11_DRV[0]: Start Radio0
[*04/12/2019 08:40:50.9899] DOT11_DRV[0]: Channel set to 1, width 20
[*04/12/2019 08:40:50.9899] DOT11_DRV[0]: Stop Radio0
[*04/12/2019 08:40:51.2099] DOT11_DRV[0]: Channel set to 1, width 20
[*04/12/2019 08:40:51.2199] DOT11_DRV[1]: Stop Radio1
[*04/12/2019 08:40:51.2299] DOT11_DRV[1]: set_channel Channel set to 36
[*04/12/2019 08:40:51.2399] DOT11_DRV[1]: Start Radio1
[*04/12/2019 08:40:51.2399] DOT11_DRV[1]: Stop Radio1
[*04/12/2019 08:40:51.4799] DOT11_DRV[1]: Start Radio1
[*04/12/2019 08:40:51.4799] DOT11_DRV[1]: Channel set to 36, width 20
[*04/12/2019 08:40:51.4899] DOT11_DRV[1]: Stop Radio1
[*04/12/2019 08:40:51.4999] DOT11_DRV[1]: Channel set to 36, width 20
[*04/12/2019 08:40:51.4999] Failed to load flex AP config from file. Default config will be used.
[*04/12/2019 08:40:51.5499] Socket Valid Element wcp/wcp_db Handler set_vlan_name_map Data Length 10
[*04/12/2019 08:40:55.5999] Waiting for preferred uplink IP configuration
[*04/12/2019 08:41:00.6199] Waiting for preferred uplink IP configuration
[*04/12/2019 08:41:05.6299] Waiting for preferred uplink IP configuration
[*04/12/2019 08:41:10.6399] Waiting for preferred uplink IP configuration
[*04/12/2019 08:41:15.6599] Waiting for preferred uplink IP configuration
[*04/12/2019 08:41:20.6699] Waiting for preferred uplink IP configuration
[*04/12/2019 08:41:25.6899] Waiting for preferred uplink IP configuration
[*04/12/2019 08:41:30.6999] Waiting for preferred uplink IP configuration
[*04/12/2019 08:41:30.7099] Gateway not reachable. IP address will not be assigned. IP:192.168.102.105/24 Gateway:192.168.102.1
[*04/12/2019 08:41:32.0399] ethernet_port wired0, ip 192.168.102.105, netmask 255.255.255.0, gw 192.168.102.1, mtu 1500, bcast 192.168.102.255, dns1 192.168.102.10, domain rtreg, vid 0, static_ip_failover false, dhcp_vlan_failover false
[*04/12/2019 08:41:41.7199] DOT11_CFG[0] Radio Mode is changed from FlexConnect to FlexConnect
[*04/12/2019 08:41:41.7299] DOT11_CFG[1] Radio Mode is changed from FlexConnect to FlexConnect
[*04/12/2019 08:41:41.7999] AP IPv4 Address updated from 0.0.0.0 to 192.168.102.105
[*04/12/2019 08:41:41.8299] dtls_init: Use MIC certificate
[*04/12/2019 08:41:41.8299]
[*04/12/2019 08:41:41.8299] CAPWAP State: Init
[*04/12/2019 08:41:41.8299]
[*04/12/2019 08:41:41.8299] PNP is not required,
[*04/12/2019 08:41:41.8299] Starting CAPWAP discovery
[*04/12/2019 08:41:41.8299]
[*04/12/2019 08:41:41.8299]
[*04/12/2019 08:41:41.8299] CAPWAP State: Discovery
[*04/12/2019 08:41:41.8299] IP DNS query for CISCO-CAPWAP-CONTROLLER.rtreg
[*04/12/2019 08:41:41.8399] DNS resolved CISCO-CAPWAP-CONTROLLER.rtreg
[*04/12/2019 08:41:41.8399] DNS discover IP addr: 192.168.102.4
[*04/12/2019 08:41:41.8499] Discovery Request sent to 192.168.102.4, discovery type DNS(3)
[*04/12/2019 08:41:41.8599] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)
[*04/12/2019 08:41:41.8599]
[*04/12/2019 08:41:41.8599] CAPWAP State: Discovery
[*04/12/2019 08:42:11.2799]
[*04/12/2019 08:42:11.2799] CAPWAP State: Discovery
[*04/12/2019 08:42:11.2899] IP DNS query for CISCO-CAPWAP-CONTROLLER.rtreg
[*04/12/2019 08:42:11.2899] DNS resolved CISCO-CAPWAP-CONTROLLER.rtreg
[*04/12/2019 08:42:11.2899] DNS discover IP addr: 192.168.102.4
[*04/12/2019 08:42:11.2999] Discovery Request sent to 192.168.102.4, discovery type DNS(3)
[*04/12/2019 08:42:11.2999] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)
[*04/12/2019 08:42:40.7399]
[*04/12/2019 08:42:40.7399] CAPWAP State: Discovery
[*04/12/2019 08:42:40.7499] IP DNS query for CISCO-CAPWAP-CONTROLLER.rtreg
[*04/12/2019 08:42:40.7499] DNS resolved CISCO-CAPWAP-CONTROLLER.rtreg
[*04/12/2019 08:42:40.7499] DNS discover IP addr: 192.168.102.4
[*04/12/2019 08:42:40.7599] Discovery Request sent to 192.168.102.4, discovery type DNS(3)
[*04/12/2019 08:42:40.7599] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)
[*04/12/2019 08:43:10.1999]
[*04/12/2019 08:43:10.1999] CAPWAP State: Discovery
[*04/12/2019 08:43:10.1999] IP DNS query for CISCO-CAPWAP-CONTROLLER.rtreg
[*04/12/2019 08:43:10.2099] DNS resolved CISCO-CAPWAP-CONTROLLER.rtreg
[*04/12/2019 08:43:10.2099] DNS discover IP addr: 192.168.102.4
[*04/12/2019 08:43:10.2199] Discovery Request sent to 192.168.102.4, discovery type DNS(3)
[*04/12/2019 08:43:10.2399] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)
[*04/12/2019 08:43:10.2499] DOT11_DRV[0]: Channel set to 1, width 20
[*04/12/2019 08:43:10.2499] DOT11_DRV[0]: Channel set to 1, width 20
[*04/12/2019 08:43:10.2599] DOT11_DRV[1]: Channel set to 36, width 20
[*04/12/2019 08:43:10.2599] DOT11_DRV[1]: Channel set to 36, width 20
[*04/12/2019 08:43:10.2599] Failed to load flex vap config from file. Default config will be used.
[*04/12/2019 08:43:10.2699] Flexconnect Switching to Standalone Mode!

Username:

Ric Beeching · ‎04-11-2019

What output do you get locally on the console of the second AP?
Can you log on to it locally/remotely?

If you shutdown all ME APs including the primary, does the AP that is not joining become the primary ME WLC?

Ric

-----------------------------
Please rate helpful / correct posts

Alex_rt · ‎04-11-2019

If i shutdown Master ME AP, second AP don't become Primery Controller.. it come a ME WLC after reboot.

patoberli · ‎04-12-2019

You have to configure this, once it has successfully connected to the Master. Then you can configure which one is the backup.

Alex_rt · ‎04-12-2019

@patoberli wrote:
You have to configure this, once it has successfully connected to the Master. Then you can configure which one is the backup.

again:

AP1 is master and it boot like ME WLC if it boot first or only one

AP2 boot like ap not WLC then it boot when AP1 is already up.

I can login in Web Interface on AP1 and i can see the only AP1 like as access point whit ip get from DHCP

eg:

ap1 wlc has a static ip:192.168.102.4 and ap1 has a ip from DHCP 192.168.102.104

ap2 has ip from DHCP 192.168.102.105

IN WLC i dont' see AP2, i can ping it i can login on it by ssh.

How AP2 must join to ME WLC AP1 ?

patoberli · ‎04-12-2019

If AP2 is configured as CAPWAP, then it will NOT become a WLC.

If AP2 is configured as ME, is will become a WLC if there is none other discoverable in the VLAN/DNS.

Can you run 'debug capwap events' on AP1 and then power on AP2 and let it run for around 10 minutes?

At the same time, attach a console cable and capture all logs for those 10 minutes. Please post the output of both.

Alex_rt · ‎04-12-2019

@patoberli wrote:
If AP2 is configured as CAPWAP, then it will NOT become a WLC.
If AP2 is configured as ME, is will become a WLC if there is none other discoverable in the VLAN/DNS.

Can you run 'debug capwap events' on AP1 and then power on AP2 and let it run for around 10 minutes?
At the same time, attach a console cable and capture all logs for those 10 minutes. Please post the output of both.
should i switch one of them to capwap?