As usual, I read your first post too quickly. When using the options above ap-macaddr should use the AP wired mac address, yes. If it is not working that way, you should open a TAC case to find out what is wrong.
EDIT: the macaddr parameter should send the BSSID.
Original Message:
Sent: Sep 03, 2023 08:53 AM
From: nkuhl1630
Subject: RADIUS Called-Station-ID app-macaddr - Returning incorrect AP MAC
Hi Colin,
Are you sure? These are the options we're presented with in the RADIUS server profile:
------------------------------
Nathan K
Original Message:
Sent: Sep 02, 2023 10:52 AM
From: Colin Joseph
Subject: RADIUS Called-Station-ID app-macaddr - Returning incorrect AP MAC
The "called Station ID" should be the BSSID (the mac address of the SSID that the client is attached to), NOT the wired mac address of the AP.
------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.
HPE Design and Deploy Guides: https://community.arubanetworks.com/support/migrated-knowledge-base?attachments=&communitykey=dcc83c62-1a3a-4dd8-94dc-92968ea6fff1&pageindex=0&pagesize=12&search=&sort=most_recent&viewtype=card
Original Message:
Sent: Sep 01, 2023 11:55 AM
From: nkuhl1630
Subject: RADIUS Called-Station-ID app-macaddr - Returning incorrect AP MAC
We have our RADIUS server configured in Aruba for 802.1x authentication. It works fine, however, we need Aruba to send the AP MAC address back to the RADIUS server to apply a specific policy. We set the Called-Station-ID CSID_type value to ap-maccaddr but the MAC address that is returned is not correct. It does not match the AP's MAC Address. The first three octets match, but not the last three.
The MAC address that is returned to our RADIUS server does not match any other AP in our system. Any ideas?
------------------------------
Nathan K
------------------------------