Controller Based WLANs

What are the possible reasons that Device Name doesn't show as Username for Non-802.1x Client in 6.5
Q:

What are the possible reasons that Device Name doesn't show as Username for Non-802.1x Client in 6.5 code?



A:

Prior to 6.5 code, non-802.1x clients user-name will not be populated in the user-table so its very difficult to identify the host. Hence from 6.5 code  we have introduced an option called "Set username from dhcp option 12" under the aaa profile. When this option is enabled, it will use the Device Name as the User Name for the non-802.1x authenticated clients as shown below. 

 #show aaa profile test-aaa
AAA Profile "test-aaa"
---------------------
Parameter                           Value
---------                           -----
Initial role                        logon
Download Role from CPPM             Disabled
Set username from dhcp option 12    Enabled
L2 Authentication Fail Through      Disabled
Multiple Server Accounting          Disabled

 

After enabling username-from-dhcp-opt12, we can see the "Test-aruba-PC" is the the computer name on the host which is used as user-name.

 

 (Aruba-Master7240) #show user-table
Users
-----
    IP           MAC            Name          Role      Age(d:h:m)  Auth  VPN link  AP name  Roaming  Essid/Bssid/Phy  Profile  Forward mode  Type     Host Name
----------  ------------       ------         ----      ----------  ----  --------  -------  -------  ---------------  -------  ------------  ----     ---------
20.20.20.1  f0:1f:af:52:42:9f  Test-aruba-PC  logon     00:00:01                    0/0/1    Wired                     test-aaa  tunnel        Windows
User Entries: 1/1
 Curr/Cum Alloc:1/8 Free:0/7 Dyn:1 AllocErr:0 FreeErr:0

 

However there are limitations in this feature: 

 

This feature is not supported for Clients coming with Static IP. It is mandatory for the client/host to go through the DHCP transaction at least once so that the controller can capture the DHCP option 12.

AOS does not support UDR/VDR using DHCPv6 and hence there is no mechanism to punt DHCPv6 packets from SOS to AUTH,  hence this feature does not support DHCPv6.

This feature will not be supported for Bridge mode clients. 

Version history
Revision #:
2 of 2
Last update:
‎02-20-2017 12:10 PM
Updated by:
 
Labels (1)
Contributors
Search Airheads
Showing results for 
Search instead for 
Did you mean: 
Is this a frequent problem?

Request an official Aruba knowledge base article to be written by our experts.