Cannot ping ap-manager interface (management works, same subnet)

Unanswered Question
Mar 24th, 2009
User Badges:

Hi,


I have configured a NM-WLC on a 2800 series router.


I have assigned ip addresses for the management and ap-manager interfaces on the same subnet.


When I log into the WLC, I can ping the management interface as well as access it via a web interface.


However, I am not able to ping the ap-manager interface, even from within the WLC CLI.


According to this link, I should be able to ping the ap-manager interface, although docs for other controller models, say that the ap-manager does not reply to ICMP messages.



http://www.cisco.com/en/US/docs/ios/12_4/12_4x/12_4xa/boxernm.html#wp2022959


The configuration for both the interfaces is identical apart from the IP address.


ANy idea what may be wrong ?


Thanks

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (2 ratings)
Loading.
mark.cronin Tue, 03/24/2009 - 05:14
User Badges:

I have checked and I am unable to ping the ap-manager interface - I believe this is normal.


Can you see the address in your arp cache of the device connecting the device to the network?

jeff.kish Tue, 03/24/2009 - 05:58
User Badges:
  • Silver, 250 points or more

Mark is correct, you cannot ping the AP Manager interface. It is intentionally designed by Cisco to not respond, and to my knowledge there's no way to enable ping responses.


So no need to worry :D

shahedvoicerite Tue, 03/24/2009 - 06:12
User Badges:

Thanks to you both !


Yes, I do see it in the ARP cache.


Wonder why the link I posted earlier seems to imply that the AP-manager is pingable ??

Perhaps it depends on the WLC o/s version.

I am on 5.0.x



Thanks.

Leo Laohoo Tue, 03/24/2009 - 14:23
User Badges:
  • Super Gold, 25000 points or more
  • Hall of Fame,

    The Hall of Fame designation is a lifetime achievement award based on significant overall achievements in the community. 

  • Cisco Designated VIP,

    2017 LAN, Wireless

Even in the early 4.x days, the only ping-able interface belongs to the Management Interface.

Actions

This Discussion

 

 

Trending Topics: Other Wireless Mobility

client could not be authenticated
Network Analysis Module (NAM) Products
Cisco 6500 nam
reason 440 driver failure
Cisco password cracker
Cisco Wireless mode