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.
Expand all | Collapse all

Aruba RAP Provisioning Issue

This thread has been viewed 18 times
  • 1.  Aruba RAP Provisioning Issue

    Posted Oct 09, 2020 02:41 AM

    Hi Community,

    I have a problem with provision RAP

    IKE XAuth client UP failed 10.1.34.130 (External 10.1.34.130)
    Oct 9 16:28:17 isakmpd[3614]: <103103> <3614> <WARN> |ike| 10.1.34.130:59776-> IKE SA Deletion: IKE2_delSa peer:10.1.34.130:59776 id:3344822301 errcode:ERR_IKESA_CLEARED saflags:0x51 arflags:0x9



  • 2.  RE: Aruba RAP Provisioning Issue

    MVP EXPERT
    Posted Oct 09, 2020 03:44 AM

    Is this a new RAP or an existing RAP? Have you provisioned any other RAPs without issues? Have you created all the required RAP including IP Pools, RAP whitelist etc? 

     

    Please feel free to share any information on your deployment.



  • 3.  RE: Aruba RAP Provisioning Issue

    Posted Oct 09, 2020 06:36 AM

    New AP. Initially Provisioned as CAP and Covered to RAP.

    DHCP pool and Provision as a Certificate-based.



  • 4.  RE: Aruba RAP Provisioning Issue

    MVP EXPERT
    Posted Oct 09, 2020 06:56 AM
      |   view attached

    Connected to a MM/MD or Standalone? What AP model and AOS version? Given the limited information, it might be worth you reviewing the attached.

     

     

     

    Attachment(s)



  • 5.  RE: Aruba RAP Provisioning Issue

    Posted Oct 09, 2020 01:03 PM

    Deployed as Standalone 

    Aruba Mobility Controller: 7030

    Aruba OS 8.7

    AP model: 303

     



  • 6.  RE: Aruba RAP Provisioning Issue

    MVP
    Posted Oct 11, 2020 01:48 PM


  • 7.  RE: Aruba RAP Provisioning Issue
    Best Answer

    Posted Oct 11, 2020 02:36 PM

    My problem solved after configuration shared secrets in VPN setting



  • 8.  RE: Aruba RAP Provisioning Issue

    MVP
    Posted Oct 12, 2020 05:46 AM

    Weird, we also have a shared secret configured...