Wireless Access

last person joined: yesterday 

Access network design for branch, remote, outdoor, and campus locations with HPE Aruba Networking access points and mobility controllers.
Back to discussions
Expand all | Collapse all

Setting up AP-225: Constant "AP down"

This thread has been viewed 4 times

  • 1.  Setting up AP-225: Constant "AP down"

    Posted Dec 10, 2013 03:38 PM

    I am trying to setup an ARUBA 3200 with version 6.3 and 2x AP-225. I can see the AP on and off.. I was able to provision them but they areusually down for some reason. 

     

    Connection setup is:

     

    Outside port (internet) trunk to controller's Gi1/0 (VLAN 900)  ==>  Controller's Gi1/3 trunk to Cisco 3750x Gi1/0/21 (Allowed Vlan ALL, native VLAN 991 which is the wireless DHCP pool 192.168.1.1/24, encap dot1q) ===> then from the cisco switch 2x AP-225 are connected (switchport access VLAN 991)..

     

    Controllers IP is  192.168.0.1 from management VLAN 990 

     

    So far the 2 AP-225 are getting IP from the pool 192.168.1.1/24.

     

    Again,the problem is, the 2 AP are on and off and mostly down. Cisco link light sometimes changes to amber but green most of the time.

     

    Thank you.


    #3200


  • 2.  RE: Setting up AP-225: Constant "AP down"

    Posted Dec 10, 2013 03:53 PM

    Try to look from AP console what is the reboot reason. 

    You can also enable AP debugging on the controller to see reboot reason. "logging level debugging ap-debug <ap-name>"

     

    As AP is going UP and down, check whether cpsec is enabled or not. By default it is enabled in the config. If so you will need to add 

    AP into cpsec whitelist. User guide will guide you for it. 

     

    Try to use "ase.arubanetworks.com". It will geberate complete controller config based on your requirement to bring up ssid and AP. Use the solution for "wireless ssid".



  • 3.  RE: Setting up AP-225: Constant "AP down"

    Posted Dec 10, 2013 06:28 PM

     

    Please run the following commands too:

     

    show log system all | include <ap mac address>

    show log errorlog all | include <ap mac address>

    show ap debug system ap-name <ap-name>

     

     



  • 4.  RE: Setting up AP-225: Constant "AP down"

    Posted Dec 10, 2013 06:58 PM 
    (jcX_Controller) # show log system all | include jcX_AP_AC-test-2

Dec 10 03:56:09  KERNEL(jcX_AP_AC-test-2@192.168.1.2): [    4.326291] wdg_create_new_proc_entry: proc initializedEnabling watchdog on CPU 1
Dec 10 03:56:10 :303022:  <WARN> |AP jcX_AP_AC-test-2@192.168.1.2 nanny|  Reboot Reason: AP rebooted Wed Dec 31 16:07:42 PST 1969; SAPD: Unable to contact switch: HELLO-TIMEOUT. Last Ctrl msg: HELLO len=1216 dest=192.168.0.1 tries=10 seq=0 
Dec 10 04:02:43 :311002:  <WARN> |AP jcX_AP_AC-test-2@192.168.1.2 sapd|  Rebooting: SAPD: Unable to contact switch: HELLO-TIMEOUT. Last Ctrl msg: HELLO len=1216 dest=192.168.0.1 tries=10 seq=0
Dec 10 04:02:44 :303086:  <ERRS> |AP jcX_AP_AC-test-2@192.168.1.2 nanny| Process Manager (nanny) shutting down - AP will reboot!
Dec 10 04:04:18  KERNEL(jcX_AP_AC-test-2@192.168.1.2): [    4.319220] wdg_create_new_proc_entry: proc initializedEnabling watchdog on CPU 1
Dec 10 04:04:20 :303022:  <WARN> |AP jcX_AP_AC-test-2@192.168.1.2 nanny|  Reboot Reason: AP rebooted Wed Dec 31 16:07:42 PST 1969; SAPD: Unable to contact switch: HELLO-TIMEOUT. Last Ctrl msg: HELLO len=1216 dest=192.168.0.1 tries=10 seq=0 
Dec 10 04:10:52 :311002:  <WARN> |AP jcX_AP_AC-test-2@192.168.1.2 sapd|  Rebooting: SAPD: Unable to contact switch: HELLO-TIMEOUT. Last Ctrl msg: HELLO len=1216 dest=192.168.0.1 tries=10 seq=0
Dec 10 04:10:53 :303086:  <ERRS> |AP jcX_AP_AC-test-2@192.168.1.2 nanny| Process Manager (nanny) shutting down - AP will reboot!
Dec 10 04:12:28  KERNEL(jcX_AP_AC-test-2@192.168.1.2): [    4.325758] wdg_create_new_proc_entry: proc initializedEnabling watchdog on CPU 1
Dec 10 04:12:29 :303022:  <WARN> |AP jcX_AP_AC-test-2@192.168.1.2 nanny|  Reboot Reason: AP rebooted Wed Dec 31 16:07:42 PST 1969; SAPD: Unable to contact switch: HELLO-TIMEOUT. Last Ctrl msg: HELLO len=1216 dest=192.168.0.1 tries=10 seq=0 
Dec 10 04:19:02 :311002:  <WARN> |AP jcX_AP_AC-test-2@192.168.1.2 sapd|  Rebooting: SAPD: Unable to contact switch: HELLO-TIMEOUT. Last Ctrl msg: HELLO len=1216 dest=192.168.0.1 tries=10 seq=0
Dec 10 04:19:03 :303086:  <ERRS> |AP jcX_AP_AC-test-2@192.168.1.2 nanny| Process Manager (nanny) shutting down - AP will reboot!
Dec 10 04:20:37  KERNEL(jcX_AP_AC-test-2@192.168.1.2): [    4.325490] wdg_create_new_proc_entry: proc initializedEnabling watchdog on CPU 1
Dec 10 04:20:38 :303022:  <WARN> |AP jcX_AP_AC-test-2@192.168.1.2 nanny|  Reboot Reason: AP rebooted Wed Dec 31 16:07:42 PST 1969; SAPD: Unable to contact switch: HELLO-TIMEOUT. Last Ctrl msg: HELLO len=1216 dest=192.168.0.1 tries=10 seq=0 
Dec 10 04:27:11 :311002:  <WARN> |AP jcX_AP_AC-test-2@192.168.1.2 sapd|  Rebooting: SAPD: Unable to contact switch: HELLO-TIMEOUT. Last Ctrl msg: HELLO len=1216 dest=192.168.0.1 tries=10 seq=0
Dec 10 04:27:12 :303086:  <ERRS> |AP jcX_AP_AC-test-2@192.168.1.2 nanny| Process Manager (nanny) shutting down - AP will reboot!
Dec 10 04:28:46  KERNEL(jcX_AP_AC-test-2@192.168.1.2): [    4.319425] wdg_create_new_proc_entry: proc initializedEnabling watchdog on CPU 1
Dec 10 04:28:48 :303022:  <WARN> |AP jcX_AP_AC-test-2@192.168.1.2 nanny|  Reboot Reason: AP rebooted Wed Dec 31 16:07:42 PST 1969; SAPD: Unable to contact switch: HELLO-TIMEOUT. Last Ctrl msg: HELLO len=1216 dest=192.168.0.1 tries=10 seq=0 
Dec 10 04:35:21 :311002:  <WARN> |AP jcX_AP_AC-test-2@192.168.1.2 sapd|  Rebooting: SAPD: Unable to contact switch: HELLO-TIMEOUT. Last Ctrl msg: HELLO len=1216 dest=192.168.0.1 tries=10 seq=0
Dec 10 04:35:21 :303086:  <ERRS> |AP jcX_AP_AC-test-2@192.168.1.2 nanny| Process Manager (nanny) shutting down - AP will reboot!
Dec 10 04:36:56  KERNEL(jcX_AP_AC-test-2@192.168.1.2): [    4.317419] wdg_create_new_proc_entry: proc initializedEnabling watchdog on CPU 1
Dec 10 04:36:57 :303022:  <WARN> |AP jcX_AP_AC-test-2@192.168.1.2 nanny|  Reboot Reason: AP rebooted Wed Dec 31 16:07:42 PST 1969; SAPD: Unable to contact switch: HELLO-TIMEOUT. Last Ctrl msg: HELLO len=1216 dest=192.168.0.1 tries=10 seq=0 
Dec 10 04:43:30 :311002:  <WARN> |AP jcX_AP_AC-test-2@192.168.1.2 sapd|  Rebooting: SAPD: Unable to contact switch: HELLO-TIMEOUT. Last Ctrl msg: HELLO len=1216 dest=192.168.0.1 tries=10 seq=0
Dec 10 04:43:31 :303086:  <ERRS> |AP jcX_AP_AC-test-2@192.168.1.2 nanny| Process Manager (nanny) shutting down - AP will reboot!
Dec 10 04:45:05  KERNEL(jcX_AP_AC-test-2@192.168.1.2): [    4.319050] wdg_create_new_proc_entry: proc initializedEnabling watchdog on CPU 1
Dec 10 04:45:06 :303022:  <WARN> |AP jcX_AP_AC-test-2@192.168.1.2 nanny|  Reboot Reason: AP rebooted Wed Dec 31 16:07:42 PST 1969; SAPD: Unable to contact switch: HELLO-TIMEOUT. Last Ctrl msg: HELLO len=1216 dest=192.168.0.1 tries=10 seq=0 
Dec 10 04:51:39 :311002:  <WARN> |AP jcX_AP_AC-test-2@192.168.1.2 sapd|  Rebooting: SAPD: Unable to contact switch: HELLO-TIMEOUT. Last Ctrl msg: HELLO len=1216 dest=192.168.0.1 tries=10 seq=0

     

    (jcX_Controller) # 
(jcX_Controller) #
(jcX_Controller) #show log errorlog all | include 9c:1c:12:c1:1c:3c

(jcX_Controller) #show log errorlog all | include jcX_AP_AC-test-2 
Dec 10 01:53:48  KERNEL(jcX_AP_AC-test-2@192.168.1.2): [    4.322596] wdg_create_new_proc_entry: proc initializedEnabling watchdog on CPU 1
Dec 10 02:00:23 <nanny 303086>  <ERRS> |AP jcX_AP_AC-test-2@192.168.1.2 nanny| Process Manager (nanny) shutting down - AP will reboot!
Dec 10 02:01:58  KERNEL(jcX_AP_AC-test-2@192.168.1.2): [    4.317916] wdg_create_new_proc_entry: proc initializedEnabling watchdog on CPU 1
Dec 10 02:08:33 <nanny 303086>  <ERRS> |AP jcX_AP_AC-test-2@192.168.1.2 nanny| Process Manager (nanny) shutting down - AP will reboot!
Dec 10 02:10:07  KERNEL(jcX_AP_AC-test-2@192.168.1.2): [    4.324178] wdg_create_new_proc_entry: proc initializedEnabling watchdog on CPU 1
Dec 10 02:16:42 <nanny 303086>  <ERRS> |AP jcX_AP_AC-test-2@192.168.1.2 nanny| Process Manager (nanny) shutting down - AP will reboot!
Dec 10 02:18:16  KERNEL(jcX_AP_AC-test-2@192.168.1.2): [    4.324041] wdg_create_new_proc_entry: proc initializedEnabling watchdog on CPU 1
Dec 10 02:24:51 <nanny 303086>  <ERRS> |AP jcX_AP_AC-test-2@192.168.1.2 nanny| Process Manager (nanny) shutting down - AP will reboot!
Dec 10 02:26:26  KERNEL(jcX_AP_AC-test-2@192.168.1.2): [    4.320514] wdg_create_new_proc_entry: proc initializedEnabling watchdog on CPU 1
Dec 10 02:33:01 <nanny 303086>  <ERRS> |AP jcX_AP_AC-test-2@192.168.1.2 nanny| Process Manager (nanny) shutting down - AP will reboot!
Dec 10 02:34:35  KERNEL(jcX_AP_AC-test-2@192.168.1.2): [    4.324564] wdg_create_new_proc_entry: proc initializedEnabling watchdog on CPU 0
Dec 10 02:41:10 <nanny 303086>  <ERRS> |AP jcX_AP_AC-test-2@192.168.1.2 nanny| Process Manager (nanny) shutting down - AP will reboot!
Dec 10 02:42:44  KERNEL(jcX_AP_AC-test-2@192.168.1.2): [    4.317909] wdg_create_new_proc_entry: proc initializedEnabling watchdog on CPU 1
Dec 10 02:49:19 <nanny 303086>  <ERRS> |AP jcX_AP_AC-test-2@192.168.1.2 nanny| Process Manager (nanny) shutting down - AP will reboot!
Dec 10 02:50:54  KERNEL(jcX_AP_AC-test-2@192.168.1.2): [    4.328731] wdg_create_new_proc_entry: proc initializedEnabling watchdog on CPU 1
Dec 10 02:57:29 <nanny 303086>  <ERRS> |AP jcX_AP_AC-test-2@192.168.1.2 nanny| Process Manager (nanny) shutting down - AP will reboot!
Dec 10 02:59:03  KERNEL(jcX_AP_AC-test-2@192.168.1.2): [    4.319036] wdg_create_new_proc_entry: proc initializedEnabling watchdog on CPU 1
Dec 10 03:05:38 <nanny 303086>  <ERRS> |AP jcX_AP_AC-test-2@192.168.1.2 nanny| Process Manager (nanny) shutting down - AP will reboot!
Dec 10 03:07:13  KERNEL(jcX_AP_AC-test-2@192.168.1.2): [    4.318288] wdg_create_new_proc_entry: proc initializedEnabling watchdog on CPU 1

     

    (jcX_Controller) #show ap debug system-status ap-name jcX_AP_AC-test-2   
No AP found with ap_name jcX_AP_AC-test-2

(jcX_Controller) #show ap debug system-status ap-name jcX_AP_AC-test-2
No AP found with ap_name jcX_AP_AC-test-2

(jcX_Controller) #show ap debug system-status ap-name jcX_AP_AC-test-2
No AP found with ap_name jcX_AP_AC-test-2

(jcX_Controller) #
(jcX_Controller) #show ap debug system-status ap-name jcX_AP_AC-test-2
No AP found with ap_name jcX_AP_AC-test-2

(jcX_Controller) #show ap debug system-status ap-name ?               
<ap-name>               Name of Access Point

(jcX_Controller) #show ap debug system-status ap-name jcX_AP_AC-test-2
No AP found with ap_name jcX_AP_AC-test-2

(jcX_Controller) #

     



  • 5.  RE: Setting up AP-225: Constant "AP down"

    Posted Dec 10, 2013 07:11 PM

    Based on that error message the APs is having difficulties reaching the controller , if could a couple of things:

     

    - PoE issues , faulty port , faulty patch cable

    - Make sure there's no packet loss between the switch the APs are connect to and the controller ( check all the trunk interfaces)

    - Do you have cpsec on?

    - From the controller can you ping the APs ?



  • 6.  RE: Setting up AP-225: Constant "AP down"

    Posted Dec 10, 2013 07:13 PM

    CPsec is disabled.

     

    Sometimes I can ping them, sometimes not.

     

    Thank you for the help BTW.. I really appreciate it.



  • 7.  RE: Setting up AP-225: Constant "AP down"

    Posted Dec 10, 2013 07:18 PM

     

    Glad to help.

     

    Please share your ip route table .

     

     



  • 8.  RE: Setting up AP-225: Constant "AP down"

    Posted Dec 10, 2013 07:23 PM 
    (jcX_Controller) #
(jcX_Controller) #show ip route   

Codes: C - connected, O - OSPF, R - RIP, S - static
       M - mgmt, U - route usable, * - candidate default, V - RAPNG VPN

Gateway of last resort is Imported from DHCP to network 0.0.0.0 at cost 10
Gateway of last resort is Imported from CELL to network 0.0.0.0 at cost 10
Gateway of last resort is Imported from PPPOE to network 0.0.0.0 at cost 10
Gateway of last resort is 10.1.0.1 to network 0.0.0.0 at cost 10
S*    0.0.0.0/0  [10/0] via 10.1.0.1*
C    192.168.0.0/24 is directly connected, VLAN990
C    172.16.0.0/24 is directly connected, VLAN1
C    192.168.1.0/24 is directly connected, VLAN991
C    10.1.0.0/16 is directly connected, VLAN900

(jcX_Controller) #
(jcX_Controller) #
(jcX_Controller) #
(jcX_Controller) #show vlan

VLAN CONFIGURATION
------------------
VLAN  Description  Ports                 AAA Profile
----  -----------  -----                 -----------
1     Default      GE1/0 GE1/2-3 Pc0-7   N/A 
900   VLAN0900     GE1/3                 N/A 
990   VLAN0990     GE1/0-1 GE1/3         N/A 
991   VLAN0991     GE1/0 GE1/3           N/A 

(jcX_Controller) #show ip interface brief 

Interface                   IP Address / IP Netmask        Admin   Protocol
vlan 990                   192.168.0.1 / 255.255.255.0     up      up  
vlan 1                    172.16.0.254 / 255.255.255.0     up      up  
vlan 991                   192.168.1.1 / 255.255.255.0     up      up  
vlan 900                    10.1.0.231 / 255.255.0.0       up      up  
loopback                    unassigned / unassigned        up      up  
mgmt                        unassigned / unassigned        down    down

(jcX_Controller) #

     



  • 9.  RE: Setting up AP-225: Constant "AP down"

    EMPLOYEE
    Posted Dec 10, 2013 08:56 PM

    See if the switch that the access point is connected to has duplex/speed negotiated properly.  Also see if there are any errors on that physical port.  How many access points terminate on that controller?

     



  • 10.  RE: Setting up AP-225: Constant "AP down"

    Posted Dec 10, 2013 09:12 PM

    2 terminates to the controller. It's just a testing setup not a production one.  I am just tring the version 6.3 on some 225's.

     

    Here's a log from the switch.

     

    Gi1/0/19 and Gi1/0/13 are the ports the AP's are connected.

     

    001544: *Mar  1 00:08:19.779 PST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/19, changed state to up
001545: *Mar  1 00:08:36.103 PST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/19, changed state to down
001546: *Mar  1 00:08:37.102 PST: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/19, changed state to down
001547: *Mar  1 00:08:40.214 PST: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/19, changed state to up
001548: *Mar  1 00:08:41.220 PST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/19, changed state to up
001549: *Mar  1 00:13:56.296 PST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/13, changed state to down
001550: *Mar  1 00:13:57.295 PST: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/13, changed state to down
001551: *Mar  1 00:14:01.892 PST: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/13, changed state to up
001552: *Mar  1 00:14:02.898 PST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/13, changed state to up
001553: *Mar  1 00:14:19.977 PST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/13, changed state to down
001554: *Mar  1 00:14:20.976 PST: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/13, changed state to down
001555: *Mar  1 00:14:23.769 PST: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/13, changed state to up
001556: *Mar  1 00:14:24.776 PST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/13, changed state to up
001557: *Mar  1 00:16:21.939 PST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/19, changed state to down
001558: *Mar  1 00:16:22.938 PST: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/19, changed state to down
CDH-LCH-C201-CAT3750#

     



  • 11.  RE: Setting up AP-225: Constant "AP down"

    EMPLOYEE
    Posted Dec 10, 2013 09:13 PM

    If you have not done so, please open a TAC case in parallell so they can collect your information.



  • 12.  RE: Setting up AP-225: Constant "AP down"

    Posted Dec 10, 2013 09:21 PM

    I will do this too but it's too soon.

     

    I am making myself really familiar with Aruba Devices and usually opening a TAC solves it right away and ending up not learning anything. I will try some other configuration and play with it and see if it changes anything.

     

    Thank you for your help.



  • 13.  RE: Setting up AP-225: Constant "AP down"

    EMPLOYEE
    Posted Dec 10, 2013 09:38 PM

    Is that switch 802.3af? or AT?



  • 14.  RE: Setting up AP-225: Constant "AP down"

    Posted Dec 10, 2013 09:44 PM

    It is a Cisco Catalyst 3750-X Series with POE+ (WS-3750X 24P-S V02)

     

    I am guessing it is 802.3at



  • 15.  RE: Setting up AP-225: Constant "AP down"

    EMPLOYEE
    Posted Dec 10, 2013 09:45 PM

    Okay,

     

    Do you have any statistics from those physical ports (errors, etc)?  Like Vfabien says, it seems that the traffic is being dropped somewhere...(missed heartbeats)



  • 16.  RE: Setting up AP-225: Constant "AP down"

    Posted Feb 25, 2014 02:22 PM

    I am experiencing the same issue. Did this ever get resolved? How did this get fixed. I am currently using a wroaround in which the switchport is set up as an access port vs. a trunk port. Please advise if this was corrected.



  • 17.  RE: Setting up AP-225: Constant "AP down"

    Posted Feb 25, 2014 05:08 PM

    Correction, switchport mode access does not work either.



  • 18.  RE: Setting up AP-225: Constant "AP down"

    Posted Feb 26, 2014 01:34 AM

    Sorry, I never fixed it.



  • 19.  RE: Setting up AP-225: Constant "AP down"

    Posted Oct 07, 2014 12:18 PM

    Anybody else with this problem?

     

    I'm having the same issue with IAP-225 that have been converted to CAP.

     

    Power provided via Cisco 2960x.

     

    Deployed 8 to one location, and worked for about 2 weeks, then 4 just dropped off and started doing this reboot cycle.  There was power issues and networking equipment did not reboot.

     

    Plugging the 225 directly into our 620 controller brought the 225 back up and working without any issues.  Putting them back on the Cisco 2960 brought the problem back.

     

    Alternatively, I was able to console into the AP and do a factory_reset, reconvert back to CAP and then reprovision to the local controller, and that also seemed to work.

     

    Checked another site that had received a similar upgrade and it exhibited the same problem.

     

    I do have a TAC case open.   TAC was able to purge the boot environment and enter static information for the master, and that also seemed to work.

     

    Since the APs with the issue were already provisioned to the local office controller, I'm not exactly sure why they boot up and look for the master first instead of the local?

     

    Still working with TAC, but having some logicistical issues with being able to packet capture from an AP in a remote location and the master in a separate location.