Converting C9124AXI-E from CAPWAP to EWC

[patrickg1]

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!

BR

Patrick

[Flavio Miranda]

@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?

[patrickg1]

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)

BR

Patrick 

[marce1000]

  - 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, 

 M.

[patrickg1]

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.

[marce1000]

                >....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 ?

 M.

[patrickg1]

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.

[marce1000]

   - 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)

 M.

[patrickg1]

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

[patrickg1]

...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...

[marce1000]

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

 M.

[marce1000]

   - 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 . 

 M.

[patrickg1]

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#

[marce1000]

 - 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 ?

 M.
  

[patrickg1]

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