VMware Edge Network Intelligence now supports the Aruba Central Controller which provides the reach set of APIs and Webhook Events. This helps ENI to get all the data from Aruba Central, instead of using the Virtual Controllers present at each site. This also eliminates the limitations from the Virtual Controllers and produces better results.

To set up Aruba Central, perform the following steps:
  1. Log into the VMware Edge Network Intelligence portal, and then go to Settings > Feeds > Controllers.
  2. Click the +Add Controller button. The following screen appears:
  3. In the New Controller Config section, configure the following:
    Option Description
    Manufacturer Select Aruba Central from the drop-down menu.
    Name Enter a unique name.
    IP Address Enter the current IP address of the Controller.
    Note: Aruba Central uses a dynamic IP address.
    CLI Configuration Enter the details in the required fields as provided by the Customer.
    SNMP Configuration Select the SNMP version from the drop-down menu.
  4. Click Save.
  5. Go to Settings > Feeds > Cloud API.
  6. Click Add Cloud API Config button. The following screen appears:
  7. Configure the following:
    Option Description
    Vendors Select Aruba Central from the drop-down menu.
    Name Enter a unique name.
    Customer Id Enter the Customer ID. You can view the Customer ID by launching the Aruba Central Portal, and clicking the user icon located at the top right of the screen.
    API Configuration
    User Id Enter the Aruba Central user ID provided by the Customer.
    Password Enter the Aruba Central password provided by the Customer.
    Organization Id Enter the Client ID.
    API tokens Enter a refresh token.
    Secret Enter a password for the Client ID.
    Note:
    • Organization Id, API tokens, and Secret fields can be fetched by launching the Aruba Central Portal, and navigating to Organization > Platform Integration > API Gateway > My Apps & Tokens > +Add Apps & Tokens.
    • User Id and Password fields help to recover the expired refresh token.
    • The fields under API Configuration are optional if you have entered details in Customer Id, User Id, and Password fields correctly.
  8. Click Save.
Once you have added a controller and the controller begins to send SNMP traps. The Crawler after receiving a trap message from the controller begins SNMP gets and CLI collection from the controller. You must see that the feeds' status populates in a few minutes of adding a controller.