05-24-2011 05:49 AM - edited 03-07-2019 12:39 AM
hi,
i have wlc directly connected to core switch in same subnet and same vlan,
core switch connected to othe edege switches and APs connected to them.
I cannot ping wlc from core switch, i dont know how but connected APs are working fine
and users are also able to browse.
Pls suggest on this
Solved! Go to Solution.
05-24-2011 06:15 AM
Is your Management interface configured and pingable? According to Cisco:
The management interface is the default interface for in-band management of the controller and connectivity to enterprise services such as AAA servers. The management interface has the only consistently "pingable" in-band interface IP address on the controller. You can access the controller's GUI by entering the controller's management interface IP address in Internet Explorer's Address field.
See below:
http://www.cisco.com/en/US/docs/wireless/controller/4.0/configuration/guide/c40mint.html#wp1117168
Please rate if helpful.
05-24-2011 06:27 AM
This is odd behavior. Just to be certain, this is not the AP manager interface, correct?
05-24-2011 06:44 AM
We can troubleshoot this from the top, to be thorough. On the core switch, do a 'sh mac-add int gi5/5' then take that mac address and do 'sh ip arp *mac address*' so that we can see what ip address the core switch is communicating with on this port. Let me know your findings.
We'll get this thing fixed.
05-24-2011 07:03 AM
On the WLC, go to Controller --> Interfaces --> management, then:
Let me know if you can find the port where the management mac address is located.
05-27-2011 04:46 AM
If a trunk was properly configured on gi5/5 you should be able to ping from an ip address in the 172.6.10.0/24 range.
Sent from Cisco Technical Support iPhone App
05-24-2011 06:00 AM
Which interface(s) do you have configured?
05-24-2011 06:10 AM
pls find core switch interface config below -
core#show running-config interface gigabitEthernet 5/5
Building configuration...
Current configuration : 106 bytes
!
interface GigabitEthernet5/5
switchport access vlan 4001
switchport mode access
media-type rj45
end
core#show interfaces gig 5/5
GigabitEthernet5/5 is up, line protocol is up (connected)
Hardware is Gigabit Ethernet Port, address is 001b.5481.bc3c (bia 001b.5481.bc 3c)
MTU 1500 bytes, BW 1000000 Kbit, DLY 10 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Full-duplex, 1000Mb/s, link type is auto, media type is 10/100/1000-TX
Media-type configured as RJ45 connector
input flow-control is on, output flow-control is off
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:00:03, output never, output hang never
Last clearing of "show interface" counters never
Input queue: 0/2000/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 1722000 bits/sec, 342 packets/sec
5 minute output rate 1675000 bits/sec, 253 packets/sec
26498046840 packets input, 377789731149 bytes, 0 no buffer
Received 17180861737 broadcasts (431580 multicasts)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 input packets with dribble condition detected
30729231177 packets output, 379509186091 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier
0 output buffer failures, 0 output buffers swapped out
05-24-2011 06:15 AM
Is your Management interface configured and pingable? According to Cisco:
The management interface is the default interface for in-band management of the controller and connectivity to enterprise services such as AAA servers. The management interface has the only consistently "pingable" in-band interface IP address on the controller. You can access the controller's GUI by entering the controller's management interface IP address in Internet Explorer's Address field.
See below:
http://www.cisco.com/en/US/docs/wireless/controller/4.0/configuration/guide/c40mint.html#wp1117168
Please rate if helpful.
05-24-2011 06:23 AM
hi,
this is the interface i cannot ping.
it is configured properly.
05-24-2011 06:27 AM
This is odd behavior. Just to be certain, this is not the AP manager interface, correct?
05-24-2011 06:32 AM
05-24-2011 06:44 AM
We can troubleshoot this from the top, to be thorough. On the core switch, do a 'sh mac-add int gi5/5' then take that mac address and do 'sh ip arp *mac address*' so that we can see what ip address the core switch is communicating with on this port. Let me know your findings.
We'll get this thing fixed.
05-24-2011 06:51 AM
core#show mac-address interface gig 5/5
Unicast Entries
vlan mac address type protocols port
-------+---------------+--------+---------------------+--------------------
4001 0019.d239.1045 dynamic ip GigabitEthernet5/5
4001 0021.5c50.25db dynamic ip,other GigabitEthernet5/5
4001 0023.4d89.8dd2 dynamic ip GigabitEthernet5/5
4001 0027.1055.f6b0 dynamic ip,other GigabitEthernet5/5
4001 5894.6b7e.a218 dynamic ip,other GigabitEthernet5/5
4001 8843.e131.1983 dynamic ip GigabitEthernet5/5
4001 8843.e131.198b dynamic ip GigabitEthernet5/5
4001 a467.0641.3516 dynamic ip GigabitEthernet5/5
4001 e0f8.4720.3ddc dynamic ip,other GigabitEthernet5/5
4001 e0f8.4738.66c0 dynamic ip,other GigabitEthernet5/5
Multicast Entries
vlan mac address type ports
-------+---------------+-------+--------------------------------------------
4001 ffff.ffff.ffff system Gi2/1,Gi2/3,Gi2/4,Gi2/5,Gi2/6,Gi3/1,Gi3/2
Gi3/3,Gi3/4,Gi3/5,Gi3/6,Gi5/5,Gi6/1,Gi6/7
core#sh ip arp 0021.5c50.25db
core#sh ip arp 0023.4d89.8dd2
core#show ip arp 0027.1055.f6b0
core#sh ip arp 5894.6b7e.a218
core#sh ip arp 8843.e131.1983
core#sh ip arp 8843.e131.198b
core#sh ip arp a467.0641.3516
core#sh ip arp
core#sh ip arp e0f8.4720.3ddc
core#sh ip arp
core#sh ip arp e0f8.4738.66c0
05-24-2011 07:03 AM
On the WLC, go to Controller --> Interfaces --> management, then:
Let me know if you can find the port where the management mac address is located.
05-24-2011 10:38 PM
(Cisco Controller) >show interface detailed management
Interface Name................................... management
MAC Address...................................... 88:43:e1:31:19:8b
IP Address....................................... 172.16.10.2
IP Netmask....................................... 255.255.255.0
IP Gateway....................................... 172.16.10.253
External NAT IP State............................ Disabled
External NAT IP Address.......................... 0.0.0.0
VLAN............................................. untagged
Quarantine-vlan.................................. 0
Active Physical Port............................. LAG (29)
Primary Physical Port............................ LAG (29)
Backup Physical Port............................. Unconfigured
Primary DHCP Server.............................. 10.5.5.1
Secondary DHCP Server............................ Unconfigured
DHCP Option 82................................... Disabled
ACL.............................................. Unconfigured
AP Manager....................................... No
Guest Interface.................................. No
L2 Multicast..................................... Enabled
core#show mac-address address 88:43:e1:31:19:8b
Unicast Entries
vlan mac address type protocols port
-------+---------------+--------+---------------------+--------------------
4001 8843.e131.198b dynamic ip GigabitEthernet5/5
05-25-2011 05:20 AM
This should clear things up for you.
core# ping ip 172.16.10.2 source vlan 4001
Pings from the Management's local network should be good. The pings you've tried may have sourced from a different vlan interface on the core.
05-25-2011 05:47 AM
Dear Antonio,
It is still not pining.
core#ping 172.16.10.2 source vlan 4001
^
% Invalid input detected at '^' marker.
05-25-2011 05:50 AM
Sorry for the typo. Try this command
core#ping ip 172.16.10.2 source vlan 4001
05-25-2011 05:52 AM
core#ping ip 172.16.10.2 source vlan 4001
Translating "ip"
^
% Invalid input detected at '^' marker.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide