Configures the DHCP option match criteria (signature) for the discover and request message types received from wireless clients
When accessing a network, DHCP discover and request messages are passed between wireless clients and the DHCP server. These messages contain DHCP options and option values that differ from device to device and are based on the DHCP implementation in the device‘s Operating System (OS). Options and option values contained in a client‘s messages are parsed and compared against the configured DHCP option values to identify the device. Once a device type is identified, the wireless client database is updated with the discovered device type.
dhcp <1-16> message-type [discover|request] [option|option-codes]
dhcp <1-16> message-type [discover|request] [option <1-254>|option-codes] [contains|exact|starts-with] [ascii|hexstring] <WORD>
dhcp <1-16> message-type [discover|request] [option <1-254>|option-codes] [contains|exact|starts-with] [ascii|hexstring] <WORD>
| dhcp <1-16> | Adds a DHCP option match criteria signature 
 Note: A maximum of 16
                           match criteria can be configured. | 
| message-type [discover|request] | Specifies the message type to which this DHCP match criteria is
                           applicable 
 Note: It is recommended
                           to configure client-identity with request messages, because clients
                           rarely send discover messages. Note: If the message type is not
                           specified, the fingerprint is checked with all message types (DHCP
                           request and DHCP discover). | 
| option <1-254> | The following keywords are common to the ‘discover‘ and ‘request‘
                        message types: 
 | 
| option-codes | The following keyword is common to the ‘discover‘ and ‘request‘ message
                           types: 
 Devices pass options in their DHCP discover/request messages as option codes, option types, and option value sets. These option codes are extracted and matched against the configured DHCP option codes and a fingerprint is derived. This derived fingerprint is used to identify the device. | 
| contains | The following keyword is common to the ‘discover‘ and ‘request‘ message
                           types: 
 | 
| exact | The following keyword is common to the discover and request message
                           types: 
 | 
| starts-with | The following keyword is common to the ‘discover‘ and ‘request‘ message
                           types: 
 | 
| ascii <WORD> | The following keywords are common to the ‘contains‘, ‘exact‘, and
                        ‘starts-with‘ parameters: 
 | 
| hexstring <WORD> | The following keywords are common to the ‘contains‘, ‘exact‘, and
                        ‘starts-with‘ parameters: 
 | 
The following DHCP options are useful for identifying different device types:
Though it is possible to use any option to configure a device fingerprint, the use of a combination of one or more of the preceding options to define a device is recommended.
nx9500-6C8809(config-client-identity-test)#dhcp 1 message-type request option
60 exact ascii MSFT\5.0
         nx9500-6C8809(config-client-identity-test)#dhcp 2 message-type discover option
 2 exact hexstring 012456c22c44
         nx9500-6C8809(config-client-identity-test)#show context client-identity test dhcp 2 message-type discover option 2 exact hexstring 012456c22c44 dhcp 1 message-type request option 60 exact ascii MSFT5.0 nx9500-6C8809(config-client-identity-test)#
| no | Removes a DHCP option signature (match criteria) |