Wireless Access

last person joined: 9 hours ago 

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

AP-125 does not maintain up status

This thread has been viewed 0 times

  • 1.  AP-125 does not maintain up status

    Posted Jun 12, 2013 04:20 PM

    Hi, 

     

    I have configured a 3200XM controller that I want my AP-125 to talk to. Instead of going the DHCP route, I decided to just assign the AP a static IP and it seems to connect to the controller. The AP shows up in the AP list but it only shows a status of "up" for about 20-30 seconds after it is rebooted. After that, it shows a "down" status and does not recover unless I log in to the AP CLI and give it a reboot. 

     

    On the CLI I see:

     

    eth1:   1Gbs Full duplex, port  0, queue  0
    shutting down watchdog process (nanny will restart it)...
    ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
    bonding: bond0: link status definitely up for interface eth1.
    bonding: bond0: making interface eth1 the new active one.
     
            <<<<<       Welcome to the Access Point     >>>>>
     
    ~ # cert_cap=1
    vap aruba000 vlan is 0. discovering tunnel vlan
    vap aruba100 vlan is 0. discovering tunnel vlan
    bonding: bond0: releasing active interface eth1
    bonding: bond0: now running without any active interface !
    ADDRCONF(NETDEV_UP): eth1: link is not ready
    ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
    eth1: Link down
    ADDRCONF(NETDEV_UP): eth1: link is not ready
    eth1:   1Gbs Full duplex, port  0, queue  0
    ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
     
    I am only connecting the ETH1 interface on the AP to the second port on the controller. I don't understand why it goes from:
     
    eth1: link becomes ready <<I assume this is when it is shown as the "up" status on the controller
     
    to a few lines later: 
     
    releasing active interface eth1
     
    Why is it releasing the interface? 
     
    Thanks 

    #3200


  • 2.  RE: AP-125 does not maintain up status

    Posted Jun 12, 2013 04:34 PM
    You should move your connection to e0


  • 3.  RE: AP-125 does not maintain up status

    Posted Jun 12, 2013 05:05 PM

    Oh ok, will do in the morning and report back. Why is that may I ask? 

     

    And also if I run "show log system 50" on the controller CLI I see errors for:

     

    Reboot reason: AP rebooted (date); Unable to set up IPSec tunnel, Error: RC_ERROR_IKEP1



  • 4.  RE: AP-125 does not maintain up status

    Posted Jun 12, 2013 06:51 PM

     

    Are you setting this AP as RAP by any chance ? or do you have CPSec enabled ?

     

    Because campus APs should build up a GRE Tunnel unless configured as a RAP 

     

    Also can you check your ethernet port 1 configuration profile for that particular AP-Group that the AP is part of :

     

    Screen Shot 2013-06-12 at 6.52.17 PM.png

     

     



  • 5.  RE: AP-125 does not maintain up status

    Posted Jun 13, 2013 10:34 AM

    I got the access point to show up and stay up on the controller once moving to eth0 so thank you very much for your help. I just have a couple questions:

     

    Is there a way to disable the wireless beacons until I am ready to use them? Right now I am just disabling the whole port that the AP is connected to the controller on and will enable when I am ready to bring the AP back on line. 

     

    Since I am not ready to use the AP just yet, and I do not provision the AP, there is on way to log into it until I set up AP Installation and specify a username and pasword, correct? I can pick up the WLAN SSID from my phone but I don't believe I set up any credentials yet. 



  • 6.  RE: AP-125 does not maintain up status

    Posted Jun 13, 2013 10:57 AM

     

    You can turn off the radios under the radio 11a/g11 profiles :

     

    All Profile Management_2013-06-13_10-56-49.png

    All Profile Management_2013-06-13_10-56-03.png



  • 7.  RE: AP-125 does not maintain up status

    Posted Jun 12, 2013 05:22 PM
    Aruba recommends using e0