Wireless Access

last person joined: 17 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

Mobility Controller REST API Question

This thread has been viewed 7 times

  • 1.  Mobility Controller REST API Question

    Posted Apr 10, 2020 12:15 PM

    What is the process of naming a VLAN using the REST API?

     

    I can create un-named vlan's via REST, but all attempts at naming them have been unsuccessful.

     

    Post request body to /object/vlan_name_id :

    {

      "name": "Site1234",

      "vlan-ids": "1234"

    }

     

    Post request response

    {

      "vlan_name_id": {

        "name": "Site1234",

        "vlan-ids": "1234",

        "_result": {

          "status": 1,

          "status_str": "
    Error: VLAN Site1234 does not exist"

        }

      },

      "_global_result": {

        "status": 2,

        "status_str": "
    Error: VLAN Site1234 does not exist",

        "_pending": false

      }

    }

     

    Any suggestions on the proper way to create a named vlan?

     

    Thanks.



  • 2.  RE: Mobility Controller REST API Question

    EMPLOYEE
    Posted Apr 17, 2020 03:42 AM

    in the CLI this requires three steps

    a) create vlans, e.g. "vlan 1234", "vlan 1235"
    b) create a vlan-name,e.g. "vlan-name test"
    c) bind the two, e.g. "vlan test 1234-1235"

     

    the API requires the same,

    1) call "vlan_id" in Interfaces section
    2) call "vlan_name" in L2/L3 Protocols
    3) bind them with "vlan_name_id" in L2/L3 Protocols

    Warning: do not accidentally choose the API shown default assignment method of "even", choose "hash" (which is the default of the CLI).