Fingerprint information is stored in the Endpoint database, and the MAC vendor is a 'static lookup' independent of the endpoint database.
The first time a client connects, there is no profiling information, but the MAC Vendor is available based on the OUI lookup.
Once a client is connected, dhcp fingerprint can come in, and optionally you can trigger a reconnect/reauthentication in your service under Profiling, then when the authentication request arrives again the latest information for the fingerprint (Device Type, Device Name, etc) is available.
In general, I don't see MAC Vendor information being used too much as many vendors create different device types.
Not sure if this answers the question behind your question... if not please explain what you are looking for, for more accurate information.
------------------------------
Herman Robers
------------------------
If you have urgent issues, always contact your Aruba partner, distributor, or Aruba TAC Support. Check
https://www.arubanetworks.com/support-services/contact-support/ 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.
------------------------------
Original Message:
Sent: May 29, 2024 01:48 AM
From: arioheads
Subject: Client MAC Vendor attribute Questions
Hello Experts,
I have a question regarding Connection:Client-MAC-Vendor attribute that is used in rules. Assuming I have dhcp fingerprint and a device is profiled, is the attribute checked against the fingerprint sent by device everytime it is connecting or solely a lookup using OUI portion of the device MAC address agaist MAC Vendor in ClearPass database?
Thank you for your feedbacks,
Ario