Wireless Access

Folks,

We are not able to ping and access point which is attached to the 7005 Wireless controller.

I have attached a jpg file of our setup. What could be the issue and how can we get over it? To monitor the access point we need to have ability to ping them.

Thanks,

N K.

Hi Friend,

We can not fix the issue with the topology, please share the following,

1. Did you configure the gateway in the controller (7005) to confirm use "show ip route"

2. Check whether APs also having gateway configured properly

3. If both Controller and AP are configured with GW check whether they are able to PING their GW

4. Disable STP in Aruba Controller globally and on the uplink interface.

Please feel free to comeback with the above. let us fix the issue.

Hi Venu,

1) Gateway for the controller has been configured corretly, as we are able to ping/login to the controller from anywhere in the Network.

2) How can I check for the Gateway for the access points? I found that any machine in the same network can ping the access points. They are not pingable from out of the network.

3) Controller is able to ping the access points.

Hi,

When a controller is able ping AP what is the issue ? is the behaviour is not as expected ?

What exactly the issue is ?

Please feel free for any further help on this.

The behavior is expected and that is how it should be.

What we also need is the AP's to be pingable from anywhere in the network. This is not happening. I am able to pping to the AP's only from the network where they are connected, not from other networks.

Thanks,

N K.

network_geek1979,

What version of ArubaOS is this?

Hi,

here are the details:

ArubaOS (MODEL: Aruba7005),

Version 6.4.1.0

Thanks,

N K.

network_geek, two things:

1.  You should upgrade to the latest 6.4.x code for your 7005.  There is a bug 104097 that was fixed in 6.4.2.1

The description is pretty generic, but the details of the bug say that "devices cannot ping APs if they are in a different VLAN"

2.  APs absolutely do not have to be pinged to function.  99% of Aruba customers use DHCP on their APs and use the controller to determine if APs are up or down.  Tracking ip adress to AP-name mapping just to ping them is an administrative nightmare and the Aruba system was designed to avoid this.  There are times when APs can be pinged but they are not functioning, so you should not rely on ping at all, but use the controller to determine AP up and down status.

Hi Colin,

I will try to upgrade the Aruba Controller to the latest code and check if the ping issue is resolved.

The only need to ping the AP's is that we need to monitor the AP's, in case there is a ping loss means that the AP is not responding to ping. Unless there is some method(SNMP MIB) on the Aruba controller that will give us a alert that the AP's has been lost.

Thanks,

N K.

Network_Geek,

The controller will send an "ap_down" trap to your NMS when an access point is down.  That is the preferred way to monitor AP status regardless of the ip address an access point receives.  You need to setup your NMS as an SNMP trap receiver:  http://www.arubanetworks.com/techdocs/ArubaOS_64_Web_Help/Web_Help_Index.htm#ArubaFrameStyles/Management_Utilities/Configuring_SNMP.htm

That will work WITHOUT you upgrading, but you should upgrade anyway.

As far as the ping is concerned the controller upgrade resolved the issue of ping. All AP's on the controller are now responding to ICMP. :)

This has been upgrade to 6.4.2.5.