Wireless Access

Reply
Contributor I
Posts: 26
Registered: ‎11-15-2013

Is this an odd issue? AP135 and AP124s only

Recently, after a support call with Aruba, some of my AP135 and AP124s will connect to the controller, show UP for only 1 minute and then show down.  This cycle repeats over and over again.

 

Connected via a console cable:

  • AP gets and IP and does see the master controller for which it is supposed to talk to.
  • However, if I let it finish the boot process, the AP just sits there with power flashing and enet0 flashing away.
  • To get the AP to boot properly, I have to interrupt the boot process and at the command line, type boot then enter.

The AP will boot up and I can connect to it.  I tried a seperate VLAN, checked DHCP options, and everything else I could.  There are other 135 APs plugged into the switch that are working fine.  I cannot figure it out, nor do I really want to go to each AP, plug in my console cable and type boot.  When I do this, I try to reboot the AP normally, but then go back to power flashing and enet0 or 1 flashing and never finishes the boot process.

Frequent Contributor II
Posts: 128
Registered: ‎03-13-2008

Re: Is this an odd issue? AP135 and AP124s only

Post the console output of an effected ap.
have you tried to purge the env and re-provision it?
Is there any flags in a "show ap database"
Controller mode? Code version?
David Dipert
Contributor I
Posts: 26
Registered: ‎11-15-2013

Re: Is this an odd issue? AP135 and AP124s only

Controllers 3600

Code 6.2.1.4

1-2 UP aps in the data base have D (for dirty or no config).  The down APs still have no flags.

Kind of hard to get to the down APs, two I can get two on a ladder, but the others are up at least 20-30 feet and need a scissor lift to get to them.  

 

We do have 290 other APs up  mix of 105s,, 124 and 135's.  All in the same VLAN, thus if those 24-25 are down, the other 290 would be down as well.

Guru Elite
Posts: 21,279
Registered: ‎03-29-2007

Re: Is this an odd issue? AP135 and AP124s only

1.  When did this start happening?

2.  What was changed since then?



Colin Joseph
Aruba Customer Engineering

Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base

Contributor I
Posts: 26
Registered: ‎11-15-2013

Re: Is this an odd issue? AP135 and AP124s only

Started yesterday around 2:30PM EST

 

Tech turned on mobile IP, but then disabled it on the controllers after the 24-25 aps went offline.

 

Logging from one controller:

 

Nov 15 12:21:43 :300000: <ERRS> |mobileip| Unexpected fatal mobileip runtime error in mip_proxy.c at mip_proxy_mobile_delete, 3248
Nov 15 12:21:45 :300005: <ERRS> |mobileip| Unexpected mobileip runtime error at mip_sibyte_send_nb, 656
Nov 15 12:38:22 :303022: <WARN> |AP name@xxx.xxx.xxx.xxx nanny| Reboot Reason: AP rebooted Fri Nov 15 12:37:44 PST 2013; SAPD: Unable to contact switch. Called by sapd_hello_cb:4. HBT miss seq_gen=20 seq_snt=12 seq_rcv=12 0 sec before 233 sec: Last Ctrl message: HELLO len=1112 dest=xx.xx.xx.xx tries=10 seq=0 

Guru Elite
Posts: 21,279
Registered: ‎03-29-2007

Re: Is this an odd issue? AP135 and AP124s only

I would find out what else he did by typing "show audit-trail" on the commandline, and work from there.


Colin Joseph
Aruba Customer Engineering

Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base

Contributor I
Posts: 26
Registered: ‎11-15-2013

Re: Is this an odd issue? AP135 and AP124s only

The issue was wired ap profile was enabled and the AP135's and 124's that were plugged into enet1 couldn't complete the tunnel.  Disabling this, made the APs come up without an issue.  Resolved with the help of Aruba support.

Search Airheads
Showing results for 
Search instead for 
Did you mean: