Cloud Managed Networks

 View Only
last person joined: yesterday 

Forum to discuss all things related to HPE Aruba Networking Central and UXI Network Management, including deployment of managed networks, configuration, best practices, APIs, Cloud Guest, AIOps, Presence Analytics, and other included Applications
Expand all | Collapse all

Aruba Central Assigning Virtual Controller IP Address Conflict

This thread has been viewed 7 times
  • 1.  Aruba Central Assigning Virtual Controller IP Address Conflict

    Posted 15 days ago

    Hey, I have assigned an IP address `` to VC from System->General or as it means `virtual-controller-ip`. But we use NAC to register hosts and have a Radius NAC configuration as a Primary Server in SSID settings. In this configuration, DRP IP and NAS IP are `` accidentally. And I realized If I try to access `` I can't but can access to VC from ``. So what does that mean, where the VC IP assign from correctly?

  • 2.  RE: Aruba Central Assigning Virtual Controller IP Address Conflict
    Best Answer

    Posted 15 days ago

    With Aruba Instant, the NAS-IP and NAS-ID is something you can configure/override from the RADIUS server configuration (under Security/Authentication servers). If you leave it empty, I believe the NAS-IP will be set to the VC IP and NAS-ID is empty or set to the VC name.

    With Dynamic RADIUS Proxy enabled, requests to your RADIUS server are sent through the VC and the RADIUS server only sees the VC as sender/client.

    Note that if you manually set the VC IP address, you should set it to a free/available IP in the subnet as it is an additional IP address. The VC will have it's own (DHCP assigned) IP address and in addition the VC configured IP address. You should not set the VC IP to one of the AP's IP address as there will be an IP conflict in that case.

    Herman Robers
    If you have urgent issues, always contact your Aruba partner, distributor, or Aruba TAC Support. Check for how to contact Aruba TAC. Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.

    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.