C9115AXI-D embeded wireless controller stops pinging after reboot

[bijay.swain]

I have installed the embedded controller image on C9115AXI-D access point and working fine till it is rebooted. once rebooted it boots in to IOSXE image but no connectivity (no ping no http or https). gig0 interface is up but self ping also fails.

I have saved the configuration before reboot.

Then I have to make it factory default and reconfigure it .and same issue after it reboots.

what could be the issue.

[balaji.bandi]

connect the console and post complete boot logs and check the configuration

[bijay.swain]

Hi Balaji

   please check running config and boot log and suggest for any solution.

after reboot I am also unable to ping the controller although show ip interface shows the same ip.

[Mark Elsen]

          - Ref : from AP-running config.txt
>...
         interface GigabitEthernet0
         mac-address 0000.5e00.0101
         ip dhcp client client-id GigabitEthernet0
         ip dhcp client broadcast-flag clear
         ip address 192.168.10.14 255.255.255.0
         no negotiation auto

  Don't mix DHCP related statements and fixed address setting(s) together ; choose either DHCP or a fixed address , if going for DHCP for starters use only : "ip address dhcp" ; for fixed address remove the dhcp related directives , 

 Appendix :  When the EWC AP is on the network ; have  a checkup of it's overall configuration with the CLI command show tech wireless ; feed the output into  https://cway.cisco.com/wireless-config-analyzer/  , this procedure is always advised as can be confirmed from This is so good (e.g.)

 M.

[Rich R]

@Mark Elsen those dhcp client commands are default config on EWC and don't do any harm even when using static IP.
Mine works perfectly fine with static IP and the "ip dhcp client" commands are still there so I don't think that is an issue.

[Mark Elsen]

@Rich R  - Probably correct but I would remove them anyway.

 M.

[Rich R]

IOS-XE 17.9.3 should probably be ok but best to upgrade to 17.9.4 (currently recommended as per TAC - link below) or 17.12.1

Replace the default route:
no ip route 0.0.0.0 0.0.0.0 GigabitEthernet0 250
ip route 0.0.0.0 0.0.0.0 GigabitEthernet0 192.168.10.1
assuming 192.168.10.1 is your default gateway.
interface GigabitEthernet0
 negotiation auto
Make sure you have not assigned a duplicate IP?

For info - you should always configure ssh v2:
ip ssh version 2

What status and stats do you see on the switchport the AP is connected to?

[bijay.swain]

I configured the device EWC as per guide available on cisco site. It works fine I can login to the controller and configure it. but

It works fine until I Power off the device 

Once power Off the AP and power on again .I am unable to ping the device.

sh ip int bri shows the correct ip but self ping also fails .

I connected the device via console and show startup-config also shows the configurations I made. still not able to ping and login page also not opening

[Mark Elsen]

 - Did you already follow up and take actions according to the last reply from @Rich R ?

 M.

[bijay.swain]

Yes but no improvement same issue.

[Mark Elsen]

                   - What switch model is it connected to ?

 M.

[bijay.swain]

Switch is not the issue and I have tried with Cisco POE+ switch and also tried with a POE injector .

[Mark Elsen]

 - It is for me , please provide info as requested  , many tx.

 M.

[bijay.swain]

right now i am using a poe injector which connects directly to my laptop

[Mark Elsen]

- Unsupported , use a switch(ed) solution in between,

M.