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

636 Brocade Mobility RFS Controller System Reference Guide
53-1003099-01
11
FIGURE 15 DHCP Class Name Add screen
5. If adding a new DHCP Class Name, assign a name representative of the device class
supported. The DHCP user class name should not exceed 32 characters.
6. Select a row within the Value column to enter a 32 character maximum value string.
7. Select the Multiple User Class check box to enable multiple option values for the user class.
This allows the user class to transmit multiple option values to DHCP servers supporting
multiple user class options.
8. Select OK to save the updates to this DHCP class policy. Select Reset to revert the screen back
to its last saved configuration.
DHCP Deployment Considerations
Before defining an internal DHCP server configuration, refer to the following deployment guidelines
to ensure the configuration is optimally effective:
• Brocade DHCP option 189 is required when Brocade Mobility 650 Access Point Access Points
are deployed over a layer 3 network and require layer 3 adoption. DHCP services are not
required for Brocade Mobility 650 Access Point Access Points connected to a VLAN that’s local
to the controller or service platform.
• DHCP’s lack of an authentication mechanism means a DHCP server cannot check if a client or
user is authorized to use a given user class. This introduces a vulnerability when using user
class options. For example, if a user class is used to assign a special parameter (for example, a
database server), there is no way to authenticate a client and it’s impossible to check if a client
is authorized to use this parameter.
• Ensure traffic can pass on UDP ports 67 and 68 for clients receiving DHCP information.