05-13-2015 04:19 PM
I am attempting to switch from DHCP to static IP's for our three campus Aruba 225 access points. We have two controllers in a master-local controller setup. I have successfully set up two of the three access points with a static IP.
The third access point went down for a reboot and never came back up. If I ping the IP address of the access point the controller responds instead of the AP. I am able to bring the controller up by establishing a serial connection and configuring it to use a different static IP, but I'd like to know why this particular IP is not working.
I have checked the default gateway, subnet mask and DNS for typos and all are correct. This issue seems to be confined to just this one pesky IP address.
When I selected the range of IP's to use I checked each IP with a ping, and I got no reply. Once I noticed that the AP was not rebooting I checked the ARP tables on our switch to see if there was a different mac address on file that might not have responded to pings, but was still on the network. No luck, the arp table displayed the proper mac address of the AP and nothing else out of the norm.
This is what I get when I ping my desired IP:
PING 192.168.23.248 (192.168.23.248): 56 data bytes
92 bytes from 192.168.23.250: Redirect Host(New addr: 192.168.23.248)
Vr HL TOS Len ID Flg off TTL Pro cks Src Dst
4 5 00 0054 68d9 0 0000 3f 01 61ee 192.168.23.153 192.168.23.248
This is what I get when I run an arp -a
? (192.168.23.248) at 94:b4:f:c6:4d:f8 on en0 ifscope [ethernet]
? (192.168.23.250) at 0:b:86:be:60:a0 on en0 ifscope [ethernet]
Why is this one IP address not working with the AP? Let me know if you have any theories.
Solved! Go to Solution.
05-13-2015 04:39 PM - edited 05-13-2015 04:48 PM
Console into the access point so we do not have to guess. If you check the audit trail of the controller it will tell you what you entered into the access point.
Edit: check to see if the controller has a vrrp or loopback that shares that address
Aruba Customer Engineering
Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base
05-13-2015 04:55 PM
Here is a printenv from the AP.
apboot> printenv bootdelay=2 baudrate=9600 autoload=n boardname=Ardmore bootcmd=boot ap autostart=yes bootfile=e500.ari ethaddr=94:b4:0f:c6:4d:f8 os_partition=0 num_ipsec_retry=85 name=BusinessDevelopment group=DZlocal master=192.168.23.250 gatewayip=192.168.23.1 netmask=255.255.255.0 ip6prefix=64 dnsip=192.168.23.10 a_antenna=0 g_antenna=0 usb_type=0 uplink_vlan=0 auto_prov_id=0 is_rmp_enable=0 priority_ethernet=0 priority_cellular=0 cellular_nw_preference=1 usb_power_mode=0 ap_power_mode=0 cert_cap=1 mesh_role=0 installation=0 mesh_sae=0 start_type=warm_start ethact=eth0 ipaddr=192.168.23.248 previous_lms=0 stdin=serial stdout=serial stderr=serial Environment size: 641/131068 bytes apboot>
05-14-2015 09:26 AM - edited 05-14-2015 09:28 AM
We have determined that the issue is unique to the network. Unfortunately I do not have time to investigate further. I resolved the issue by using a different IP address.
Thank you for your quick response!