cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1776
Views
6
Helpful
20
Replies

C9105AXIU-B int0 not pingable on subnet, webui not accessible

Carlomd
Level 1
Level 1

Hello all,

I have a C9105axi-b, which I know after reading around can be converted as a EWC ap, I followed a couple of youtube videos, I also did the day 0 setup, but somehow for the life of me, I can't reach or ping the INT0 of the AP, I'm coming from Aruba ap's so this is my first time using CIsco AP's. I have 2 9105axi-b, I will try the 2nd one if that works out of the box with the day 0 setup. I installed 17.15 fw when I converted to ewc. And have static IP on int0.

Here's my sh int br output sanitized, any ideas or pointers would be appreciated.

interface GigabitEthernet0
mac-address 0000.5e00.0101
ip dhcp client client-id GigabitEthernet0
ip dhcp client broadcast-flag clear
ip address 172.16.xx.x 255.255.255.0
no negotiation auto
!
ip default-gateway 172.16.xx.x
ip forward-protocol nd
ip tftp blocksize 8192
ip http server
ip http authentication local
ip http secure-server
ip http secure-trustpoint CISCO_IDEVID_SUDI
ip ssh bulk-mode 131072
ip route 0.0.0.0 0.0.0.0 GigabitEthernet0 250
ip dns server

20 Replies 20

Yes you're right that default config does get put back.  But with weight 250 configured it should be ignored as long as you have the valid route configured so that's ok.

What IP address did you give the AP or if it's still using DHCP you're sure it's not clashing with the static IP you've given the EWC?
Anything showing up in "show log" on the AP?

Trunk is correct.  Presume VLAN 60 is the correct VLAN for 172.16.xx.0?

Mine's not connected to a switch which supports CDP so I'm not sure if that's normal or not.

Try this on your switchport (one or other of the portfast commands will work depending on switch and IOS):
spanning-tree portfast trunk
spanning-tree portfast edge trunk
spanning-tree bpdufilter enable
spanning-tree bpduguard disable



Yeah it's the same after trying some of the commands, I had it where it was pinging ok on the same subnet, except its own, and pinging from across other subnets didn't work. But now it just reverted back to not pinging any ip at all. Thanks for the good advice and pointers.

marce1000
Hall of Fame
Hall of Fame

 

  - @Carlomd   Summarizing : we often see similar issues with people trying to use EWC , I would also like to point out 
                        https://www.cisco.com/c/en/us/products/collateral/wireless/embedded-wireless-controller-catalyst-access-points/wireless-ewc-access-point-eol.html
                                         and because of those recurring posts I consider it weak technology (too)

                        You could for instance go forward with the 9800 virtual controller which you  can download
                        and deploy for free. You can also use up to 50 access points without license warnings.
                        https://software.cisco.com/download/home/286322605/type/282046477/release/Dublin-17.12.4

  M.



-- Each morning when I wake up and look into the mirror I always say ' Why am I so brilliant ? '
    When the mirror will then always repond to me with ' The only thing that exceeds your brilliance is your beauty! '

Thanks, I'm reevaluating my setup and may just stick with Aruba's, since these 9105's are EOL, and looks like only if you run them using a separate controller they will continue to be supported and also the licensing can be a pain, may not be cost effective for a company our size. I still have a return window on my reseller so I can still return them.

Fair enough - Cisco enterprise APs may not be the right fit for every use case.
Your type of setup might be better suited to the Meraki cloud managed products: 
https://meraki.cisco.com/products/wi-fi/
Note that Meraki and Catalyst wireless now use the same APs - just managed differently.

And just to clarify - the 9105 AP is not EOL yet, it's purely the EWC software which has had EOL announced, but EWC is still supported (routine software updates and bug fixes) till 31 March 2027, and security vulnerability updates till 31 July 2028.  That said, Cisco are likely to announce end of sale on the WiFi 6 APs sometime in the next year when their full WiFi 7 range has been released.  Then they will normally be supported for about 5 years after that in line with https://www.cisco.com/c/en/us/products/eos-eol-policy.html

ps: The Meraki GO products may be an even better option for you - no subscription needed:
https://www.meraki-go.com/products/wifi-access-points/
And the WiFi 6 AP is a similar spec to the 9105.
And you can even buy them from most of the big retailers too.

Review Cisco Networking for a $25 gift card