topic Re: Converting C9124AXI-E from CAPWAP to EWC in Wireless

Converting C9124AXI-E from CAPWAP to EWC

patrickg1 — Tue, 29 Oct 2024 20:30:01 GMT

Hi all,

I have recently converted a C9115AXI successfully using the steps below:

https://www.cisco.com/c/en/us/support/docs/wireless/embedded-wireless-controller-on-catalyst-access-points/215303-embedded-wireless-controller-conversion.html

I did exact same steps, but of course with different image for the 9124, now for the 9124.

Everything seems to be ok during the process and after EWC was started I configured the management interface like I did for the C9115 BUT for the C9124 I won't be able to ping the EWC management interface (gi0).

So in fact I am stuck there and can't proceed with further configs...

I already reset the AP several times and tried to get it work, without success.

Anybody facing similar issues?

Any help would be much appreciated.

Thanks in advance!

Patrick

Re: Converting C9124AXI-E from CAPWAP to EWC

Flavio Miranda — Tue, 29 Oct 2024 20:51:18 GMT

@patrickg1

the AP can not ping the management interface but it can ping something else ? Does it need the gateway or it on the same network?

Re: Converting C9124AXI-E from CAPWAP to EWC

patrickg1 — Tue, 29 Oct 2024 21:06:41 GMT

Hey Flavio!

At the moment I just have my laptop connected via console and connected via ethernet (through the power injector) to the AP. Both IFs, laptop nic and EWC management, are in the same subnet. So I should at least be able to ping in both directions and access the EWC webgui. But none of that is working.

The interface on EWC is up/up though.

I just don't get it as it worked fine for other AP model. (9115)

Patrick

Re: Converting C9124AXI-E from CAPWAP to EWC

Mark Elsen — Wed, 30 Oct 2024 07:34:06 GMT

- Make sure to use a recent software version for the EWC AP ; when it boots , check for instance if the native AP has an ip address too ; the EWC is kind of a separate plane VM within the AP getting. So when DHCP is used , (do that initially per default) ; check if there are 2 address requests coming from the device on the DHCP server,

Re: Converting C9124AXI-E from CAPWAP to EWC

patrickg1 — Wed, 30 Oct 2024 18:37:40 GMT

I am using the "recommended" EWC version 17.12.3 from Cisco Software Downloads...

I tried to use DHCP and yes, I can see 2 dhcprequests and also one binding, I guess that's the AP? At least it is the MAC from the AP itself.

The Gi0 won't receive an IP by DHCP so I have configured a static IP BUT I still can not ping from and to the EWC.

I can ping the AP IP from my laptop though.

WLC#sh ip dhcp server stat
Memory usage 16284
Address pools 1
Database agents 0
Automatic bindings 1
Manual bindings 0
Expired bindings 0
Malformed messages 0
Secure arp entries 0
Renew messages 0
Workspace timeouts 0
Static routes 0
Relay bindings 0
Relay bindings active 0
Relay bindings expired 0
Relay bindings terminated 0
Relay bindings selecting 0

Message Received
BOOTREQUEST 0
DHCPDISCOVER 4
DHCPREQUEST 2
INIT-REBOOT 0
REQUEST 2
RENEW 0
REBIND 0
DHCPDECLINE 0
DHCPRELEASE 1
DHCPINFORM 0
DHCPVENDOR 0
BOOTREPLY 0
DHCPOFFER 0
DHCPACK 0
DHCPNAK 0

Message Sent
BOOTREPLY 0
DHCPOFFER 4
DHCPACK 2
DHCPNAK 0

Bindings from all pools not associated with VRF:
IP address Client-ID/ Lease expiration Type State Interface
Hardware address/
User name
10.99.99.200 0160.b9c0.88db.30 Infinite Automatic Active GigabitEthernet0

WLC#sh ip int br
Interface IP-Address OK? Method Status Protocol
GigabitEthernet0 10.99.99.150 YES NVRAM up up

WLC#ping 10.99.99.200
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.99.99.200, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)

I am very confused...

BTW, the LED on the AP is blinking green/orange/red repeatedly.

Re: Converting C9124AXI-E from CAPWAP to EWC

Mark Elsen — Wed, 30 Oct 2024 18:43:14 GMT

>....BTW, the LED on the AP is blinking green/orange/red repeatedly.
- Can you verify on the switch , which provides the network connection for the EWC AP , that the AP is getting
sufficient power ?

Re: Converting C9124AXI-E from CAPWAP to EWC

patrickg1 — Wed, 30 Oct 2024 19:01:41 GMT

There is no switch, I am using a power injector, so how can I know?

Until now it worked for all other Cisco APs (i.e. 9115) without issues.

Re: Converting C9124AXI-E from CAPWAP to EWC

Mark Elsen — Wed, 30 Oct 2024 19:14:48 GMT

- Usually , it's mentioned on the power injector itself (the capacities and Watts that it can provide) ; or look it up
on the internet to get those details (according to the model of the power injector)
The other APs not working is not an argument for the time being because of the EWC conversion , so check it out (first lines)

Re: Converting C9124AXI-E from CAPWAP to EWC

patrickg1 — Wed, 30 Oct 2024 19:17:39 GMT

...just noticed that the "recommended" EWC version is not the newest...also, I am confused regarding the version numbering: the highest: 17.15.1 is not the newest according to the release date?! So if the release date is correct, then version 17.09.06 would be the newest from 15-Sep-2024. xD

I have no idea what to do...is there a way to down/upgrade the EWC over CLI?

Could not find anything helpful...

Re: Converting C9124AXI-E from CAPWAP to EWC

Mark Elsen — Wed, 30 Oct 2024 19:22:54 GMT

- Not diverging from topics for the time being , otherwise the thread becomes a mess ; continuing on wait over power supply data ,

Re: Converting C9124AXI-E from CAPWAP to EWC

patrickg1 — Wed, 30 Oct 2024 19:23:56 GMT

...attached a pic of the power injector specs...

Re: Converting C9124AXI-E from CAPWAP to EWC

Mark Elsen — Wed, 30 Oct 2024 19:42:55 GMT

- Power supply is good
>....The Gi0 won't receive an IP by DHCP
Could you try to set it as such (ip address dhcp) in the running configuration of the EWC (interface Gi0) ;
and then reboot the EWC (save configuration first) ; and check if that makes a difference with
sh ip int br afterwards .

Re: Converting C9124AXI-E from CAPWAP to EWC

patrickg1 — Wed, 30 Oct 2024 21:31:24 GMT

Did that - but Gi0 still gets no IP by DHCP..moreover the AP won't get an IP either now because the EWC has no IP - see below 😞

BTW - thanks a lot for your support, hope we can find a solution 🙂

WLC#sh ip int br
Interface IP-Address OK? Method Status Protocol
GigabitEthernet0 unassigned YES DHCP up up
WLC#sh ip dhcp bind
Bindings from all pools not associated with VRF:
IP address Client-ID/ Lease expiration Type State Interface
Hardware address/
User name
WLC#

Re: Converting C9124AXI-E from CAPWAP to EWC

Mark Elsen — Thu, 31 Oct 2024 07:27:22 GMT

- On the switch ; what is the output of 'show cdp neighbors detail' for the interface where the AP is connected to ?
+ What is the port configuration ?

Re: Converting C9124AXI-E from CAPWAP to EWC

patrickg1 — Thu, 31 Oct 2024 07:42:17 GMT

Again, there is NO switch - just AP connected to power injector connected to laptop

Re: Converting C9124AXI-E from CAPWAP to EWC

Mark Elsen — Thu, 31 Oct 2024 07:51:24 GMT

- That test setup is definitely a no go ; due to various basic networking services expected by the EWC you must go to a standard deployment for a real test where the AP is on a switch(ed) network and the DHCP server is on the network too , for instance.
The setup is only valid during the conversion

Re: Converting C9124AXI-E from CAPWAP to EWC

Rich R — Mon, 04 Nov 2024 01:38:17 GMT

On the EWC AP?
show run int g0
show run | inc ip route

Re: Converting C9124AXI-E from CAPWAP to EWC

patrickg1 — Tue, 05 Nov 2024 10:33:23 GMT

Hi all,

I have resolved the issue and everything now is working as expected.

For anyone who is reading that thread and may have similar issues:

After all the troubleshooting and research I am assuming a bug with the EWC version 17.12.03 (= recommended version) - at least for the C9124AXI-E.

It turned out that you NEED TO enter the initial config dialog, enter the data until AFTER DHCP yes/no (yes) and THEN abort the wizard (Ctrl+C). However the management interface Gi0 will then still receive an IP from DHCP and AFTER writing the config to the memory (write memory) the DAY0 config will be completed and you can continue with the rest of the config, even via WEBGUI.

It actually sounds ridiculous while writing that post BUT I tried the same stuff on a second C9124AXI-E and it was the exact same behaviour. If I chose "no" at the config wizard OR complete the config wizard I get to the CLI but then you can do what you want, assign IP manually or via builtin DHCP or external DHCP, connection with or without a switch, write config, reload....the interface remains unreachable and you are stuck there.

Even though it does not make sense at all, it was the only way to resolve that issue for me.

Patrick

Re: Converting C9124AXI-E from CAPWAP to EWC

Rich R — Tue, 05 Nov 2024 16:18:52 GMT

That's weird but nothing in IOS surprises me anymore <smile>
Did you compare the config to see what's different?

Did you check that country code is correctly configured (global and ap profile) when you aborted the initial config?
It's well known that the WLC does not consider day zero config to be done until country code is configured although that should not affect the interface status.

Re: Converting C9124AXI-E from CAPWAP to EWC

patrickg1 — Tue, 05 Nov 2024 16:53:12 GMT

Hi Rich,

I did not compare it line by line, because as you mentioned already it should not affect the interface behaviour itself.

But it was very noticable that the default hostname was just "WLC" when it did not work...in the end I knew I am good if the defaulf hostname changed to something like "WLCmacaddress" after the init config.

If I configure the Gi0 and my laptop NIC in same subnet and connect them it should at least be pingable anyways.

It also makes no sense to me that for the C9115 it worked as expected...with exact same steps done. (I usually skip the config wizard by default, as most people do I guess)

Also, when I have completed the init config setup it also did NOT work hahaha...what sense does that make?

THE solution was to abort the setup, so to be honest I won't wrack my brain about that anymore and be happy that it works now.

Patrick