Desired Port and Network Infra MAC on AOS-CX REST API

Networking
Comments

What does this mean in the HPE Networking AOS-CX REST API response when getting the MAC address tables from a switch:

GET /rest/v10.08/system/vlans/*/macs/*,*
...
    'dynamic,11:22:33:44:55:66': {
        'aged_on_subsystems': {},
        'attributes': {'local_move_disable': False},
        'denied': False,
        'derived_entry_src': 'none',
        'desired_port': {
            '1/1/49': '/rest/v10.08/system/interfaces/1%2F1%2F49'
        },
        'from': 'dynamic',
        'inactivity_timeout': 300,
        'mac_addr': '11:22:33:44:55:66',
        'network_infra_mac': False,
        'never_ageout': False,
        'port': None,
        'selected': True
    },
...

Why is the port data missing, and there is desired_port populated instead? Switch is hoping to see the MAC address there?

And what does network_infra_mac mean?

Update on 2026-02-21:

As pointed out by my coworker, when browsing the API documentation at https://developer.arubanetworks.com/aoscx/v10.08/reference/get_system-vlans-id-macs-from-mac-addr, the “200” box in the response section of the page is clickable, and it then reveals the response body documentation:

desired_port – string
Source of this MAC entry, as indicated by from column, specifies the desired port that it wants this MAC address to be associated with.

(Note that the actual data type in the resulted API response is not string but an object.)

network_infra_mac is not documented in 10.08 (even though it was returned by the switch using that API version), but when switching to the latest 10.15 version in the documentation, it is shown as well:

network_infra_mac – boolean
Set to ‘true’ if MAC address is determined to belong to network infrastructure device.

So there you go. I’m not sure if they help me, but at least there is some documentation in some API versions.

Leave a Reply