Invalid Physical Address" Issue on BYOT Devices – Possible Bug in Version 7.6.*

[williasthomas192004]

We are experiencing an issue where BYOT devices ( eg; Android ,IOS), excluding computers/laptops, are frequently marked with an "Invalid physical address" status. This issue appears to have started after upgrading to version 7.6.*. In version 7.4, this problem did not occur.

To temporarily resolve the issue, I’ve been manually adding the MAC addresses of the affected devices to the NAC OUI settings. However, this is not a feasible long-term solution given the number of devices on the network.

I have already executed the scheduler, but it did not resolve the issue.

Request:

• Can you confirm if this is a known bug in version 7.6.*?

• Is there an alternative or automated method to resolve or work around this issue?

Environment Details:

• Affected version: 7.6.*

• Previously working version: 7.4

• Device types: BYOT devices (excluding computers/laptops)

• Current workaround: Manual MAC address entry in NAC OUI settings

• Scheduler: Already executed, no resolution

Please advise on how to proceed or if a patch/fix is available.

Thank you.

[ebilcari]

Are the smartphones using their physical MAC addresses or random ones? Can you share an example of an OUI that you had to add manually? 
Kindly check and test the credentials that are now in a different configuration path: Troubleshooting Tip: New vendor OUI missing from the database

[williasthomas192004]

Whatever random or dynamic both need to add manually an OUI .

when testing 
Failed to read from Auto-Definition Directory. - Unauthorized (HTTP Status 401)
How to fix it

[ebilcari]

There is no point in adding random MAC ranges, as they often change and it's not possible to include all possible alternatives. FNAC should accept random MACs from wireless hosts, just verify that FNAC is able to classify the adapter's 'Media Type' as 'Wireless'.
For the Auto-Definition failure, make sure the credentials are filled in and that the test passes successfully: