C9115-AXI-E AP in EWC mode own Gi0 IP not pinging

[nips]

Tried to implement a C9115 as an Embedded Wireless Controller. Did the initial configurations and add an IP to the Gi0 interface.

interface GigabitEthernet0
mac-address #########
ip dhcp client client-id GigabitEthernet0
ip dhcp client broadcast-flag clear
ip address 10.150.38.19 255.255.255.0
no negotiation auto

Interface is UP but not pinging to own IP itself.

Current Firmware version is 16.12.04a. 

When converting the AP into CAPWAP mode after entering to the shell mode and adding a CAPWAP IP to the AP then it is pinging to its own IP and Gateway.

In the shell mode, tried to upgrade the AP to the Cisco recommended firmware version for EWC 17.09.04a. But the AP is not allowing to upgrade saying it is not need to upgrade to convert capwap to ewc-ap.

Could anyone please suggest me a workaround for this unusual issue.

[balaji.bandi]

not that we seen issue - check below thread :

https://community.cisco.com/t5/wireless/access-point-c9115-cannot-ping-own-interface/td-p/4942131

check the mode of the AP :

#show version

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

[Rich R]

1. Don't worry about pinging your local interface - as long as you can ping the default gateway or other IPs on the subnet.

2. 16.12.04a is very old!  Convert to CAPWAP.  Then install the 17.6.6 CAPWAP image
https://software.cisco.com/download/home/286322352/type/286288051/release/15.3.3-JPK7

3. Then convert to 17.9.4a EWC https://software.cisco.com/download/home/286322352/type/286323077/release/17.9.4a

If you still get the message about no upgrade needed then wipe it completely following https://www.cisco.com/c/en/us/support/docs/wireless/catalyst-9120axi-access-point/217537-repairing-c9120-c9115-access-points-from.html which reverts it to 8.10.130.0 CAPWAP image then upgrade to 8.10.190.0 CAPWAP image https://software.cisco.com/download/home/286322352/type/286288051/release/15.3.3-JK10 then continue from  step 2.

[nips]

Dear @Rich R ,

Thanks for you reply.

Further more could you please clarify me what is 17.6.6 CAPWAP image. In the link you provided only 15.3.3 versions can be seen. And also can not find a version CAPWAP 8.10.190.0 

[Scott Fella]

As far as converting capwap to EWC, which you have to do, there are guides and videos that show you step by step.  Take a look at a few for reference as that will help you convert your access point to EWC.  Just search around fro capwap to EWC.

Convert: https://rowelldionicio.com/how-to-convert-cisco-c9115-to-embedded-wireless-controller-ewc/
EWC Image: https://software.cisco.com/download/home/286322352/type/286323077/release/17.9.4a

[Rich R]

@nips The mapping of AP image version to WLC software version is found in the Compatibility Matrix (link below).
For example:

Cisco IOS XE Bengaluru 17.6.6a Cisco IOS XE Bengaluru 17.6.6

17.6.6.66

15.3(3)JPK7

[nips]

This is for the information all of you.

The device that the issue was raised was upgraded to the latest EWC OS version but no luck.

We proceeded to RMA that device and the new device we received was functioned without any issue.

I suppose this might be a hardware faulty

[nips]

Hi All, I was able to resolve this issue after configuring below command 

"wireless management interface GigabitEthernet0"

[Rich R]

The Wireless Config Analyser (link below) would highlight WMI missing from your config so you should also use it to check your config as a starting point.

[nips]

@Rich R , Still I am having below doubt.

WMI is used by Access Points to communicate with the WLC. But for accessing GUI (Management purpose) in EWC AP why we need to make the Gi0 interface as WMI interface ?

[marce1000]

 - @nips wrote :  .... why we need to make the Gi0 interface as WMI interface ?
                               Because the EWC is only some backplane in the real AP and Gi0 is the only way out to the
                               real network,

 M.

[Rich R]

I agree it doesn't make sense for GUI access but EWC is an emulated virtual controller running as a container/virtual machine on the AP so there are a few things about it that behave differently to a standard 9800.  The other thing I've highlighted in previous posts is the standard default route configured in EWC which points to G0 instead of default gateway IP - that can cause problems too and should be deleted and replaced with the correct route pointing to the default gateway IP.