Why does PING fail on own IP in EWC??

[JustTakeTheFirstStep]

WLC#sh ip int b
Interface IP-Address OK? Method Status Protocol
GigabitEthernet0 10.0.15.210 YES manual up up
WLC#ping 10.0.15.210
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.0.15.210, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)
WLC#

WLC#sh ver
Cisco IOS XE Software, Version 16.12.07

Why does PING fail on own IP in EWC??

[Flavio Miranda]

Hi

 Can you run "show run GigabitEthernet0 " ?

Make sure  this interface is not under some VRF. Looks to me like a management interface which some device put under mgmt-vrf.

[JustTakeTheFirstStep]

interface GigabitEthernet0
mac-address 0000.5e00.0101
ip dhcp client client-id GigabitEthernet0
ip dhcp client broadcast-flag clear
ip address 10.0.15.210 255.255.255.0
no negotiation auto

[Flavio Miranda]

Non sense bahavior.

From out side it pings? 

[JustTakeTheFirstStep]

Self-ping does not work, ping with switch fails

[JPavonM]

As @Flavio Miranda said, this is the usual Giga0 interface configuration in C9800 and it use to be on a different VRF.

Why do you wan to configuire such interface and not the physical ones, or a loopback interface?

c9800#sh run int g0
Building configuration...

Current configuration : 103 bytes
!
interface GigabitEthernet0
vrf forwarding Mgmt-intf
no ip address
shutdown
negotiation auto
end

[JustTakeTheFirstStep]

I am configuring 9130AP as EWC.

my AP's g0 interface doesn't have vrf settings

I want the AP and the switch to communicate, but the AP also fails to self-ping

what can i try??

[Arshad Safrulla · Accepted solution]

@JPavonM it's a EWC, not a 9800 appliance. So all the configuration on EWC in 9100 series AP uses Gig0 as WMI.

@JustTakeTheFirstStep Can you check whether the IP is duplicated anywhere in the network? Login to AP shell and check whether the AP has an IP as well. (wireless ewc-ap ap shell username admin) What does the upstream switch say about this port? Is it up up? How the switchport is configured?

[JustTakeTheFirstStep]

WLC#sh ip int
*May 4 10:06:20.158: %SYS-5-CONFIG_I: Configured from console by consoleb
Interface IP-Address OK? Method Status Protocol
GigabitEthernet0 192.168.1.10 YES manual up up
WLC#ping 192.168.1.10
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.1.10, timeout is 2 seconds:
...

WLC#wireless ewc-ap ap shell username Cisco
Cisco@192.168.129.1's password:
AP6C71.0DF2.5B94>en
Password:
AP6C71.0DF2.5B94#sh capwap ip config
IP Address : 192.168.1.2
IP netmask : 255.255.255.0
Default Gateway : 192.168.1.1
AP6C71.0DF2.5B94#

Switch#sh cdp nei d
-------------------------
Device ID: AP6C71.0DF2.5B94
Entry address(es):
IP address: 192.168.1.2

Switch#sh run int g1/0/1
Building configuration...

Current configuration : 38 bytes
!
interface GigabitEthernet1/0/1
end

Switch#sh ip int b
Interface IP-Address OK? Method Status Protocol
Vlan1 192.168.1.1 YES manual up up

[Arshad Safrulla]

Can you configure the switchport as trunk, and then post "show interface GigabitEthernet1/0/1"

Can you also check whether the Gateway is reachable?



Using VLAN1 is not recommended for security purposes (no technical limitations though), so I would suggest you create another dedicated VLAN for AP management, if you happen to create a separate VLAN then your switchport must be configured as below



Int gi 0/0/1

Switchp mode trunk

Switchp trunk nativ vlan

[JustTakeTheFirstStep · Accepted solution]

Now the PING is successful.

A few more tests are still needed,
When I posted the question, perhaps the IP bands of CAPWAP AP and EWC did not match.

EWC is 192.168.1.1
AP is 192.18.1.2

Now everything works fine.

[mohammed.alsum]

How it's solved , I have the same problem

[JustTakeTheFirstStep]

@mohammed.alsum 

I'm pretty sure there are issues with the model and version.
This thread is written with the 9130 model.
In the 9130 model, version 17.08.01 is not a problem.

However, in the 9115 model, including 17.08.01, the 16.12.07 , 17.03.04c , and 17.09.01 versions all failed to self-ping.
It was definitely not a config issue.
I didn't have client provisioning.
After changing the version several times, the 17.03.05B version was normal.

[rui mangueira]

Hello @JustTakeTheFirstStep I'm having the same problem, do you recall how you fixed it? I've tried everything and it seem to not be working no matter what i do

[balaji.bandi]

can you post show run from the prompt :

I have tested last week - followed the  below video - suggest to reset and do the day 0 config, it work as expected :

https://www.youtube.com/watch?v=oS68E25wc4A