Network Management

 View Only

  • 1.  ArubaCentral CoP on-boarding

    Posted May 19, 2025 01:04 PM

    We're in the process of trying to onboard our first CX switches into Aruba CoP. Is there a documented process for this? I've installed the licenses we have into CoP, I've attempted to configure our first switch and installed the CoP certs, and setup the location override to the IP of the CoP cluster. The switch itself reports as 'connected' but also shows 'no license', so this might be the part I'm missing. Up to this point, the switch does not appear in the CoP 'Devices' list either. These are pre-configured switches, and not out-the-box devices.

    Any advice would be appreciated.

    Thanks



  • 2.  RE: ArubaCentral CoP on-boarding

    Posted May 21, 2025 03:29 AM

    Have you found the documentation for Central on Prem? There is a section on Onboarding Devices in there.



    ------------------------------
    Herman Robers
    ------------------------
    If you have urgent issues, always contact your HPE Aruba Networking partner, distributor, or Aruba TAC Support. Check https://www.arubanetworks.com/support-services/contact-support/ for how to contact HPE Aruba Networking TAC. Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or HPE Aruba Networking.

    In case your problem is solved, please invest the time to post a follow-up with the information on how you solved it. Others can benefit from that.
    ------------------------------



  • 3.  RE: ArubaCentral CoP on-boarding

    Posted May 21, 2025 07:11 AM

    Thanks for the suggestion. Yes, I've read that documentation - it's pretty simple, but then I assumed the process of onboarding switches should be pretty simple. The method I'm using is this;

    Go to Account Home
    Click Add Devices
    Click Add Devices (again)
    Click Device Discovery
    Enter the IP address/hostname
    Select the correct SNMP/HTTPS profiles I've already created

    CoP schedules the discovery, but the device never appears. The CoP interface being used by the cluster is NOT on the same subnet as the switches - it's on a routed connection, but has full access to the switch management subnet. I would not have expected this to be an issue.

    If there's no other advice, I might need to raise a ticket with TAC.


    Original Message


Related Content