Brocade Mobility RFS Controller CLI Reference Guide (Supporting software release 5.5.0.0 and later) - Manual (Page 222)

206 Brocade Mobility RFS Controller CLI Reference Guide
53-1003098-01
4
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.
Supported in the following platforms:
• Access Points — Brocade Mobility 650 Access Point, Brocade Mobility 6511 Access Point,
Brocade Mobility 1220 Access Point, Brocade Mobility 71XX Access Point, Brocade
Mobility 1240 Access Point
• Wireless Controllers — Brocade Mobility RFS4000, Brocade Mobility RFS6000, Brocade
Mobility RFS7000
• Service Platforms — Brocade Mobility RFS9510
Syntax:
dhcp <1-16> [message-type|option|option-modes]
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>
Parameters
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
•
<1-16> – Specify an index for this DHCP match criteria from 1 - 16.
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
•
discover – Applies this match criteria to DHCP discover messages only. Indicates that the fingerprint is
only checked with any DHCP discover messages received from any device.
•
request – Applies this match criteria to DHCP request messages only. Indicates that the fingerprint is
only checked with any DHCP request messages received from any device.
It is recommended to configure client-identity with request messages, because clients rarely send discover
messages.
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 – Configures a DHCP option value, which is used as the match criteria
•
<1-254> – Configures a code for this DHCP option from 1 - 254 (except option 53)
option-codes The following keyword is common to the ‘discover’ and ‘request’ message types:
•
option-codes – Matches criteria based on the DHCP option codes contained in the client’s
discover/request messages
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:
•
contains – Specifies that the DHCP options received in the client’s discover/request messages
contains the configured option code string