Alternate Method for Defining Vendor-Specific DHCP Options
This section describes how to add vendor-specific DHCP options for IAPs in a network that already uses DHCP
options 60 and 43 for other services. Some networks use DHCP standard options 60 and 43 to provide the
DHCP clients information about certain services such as PXE. In such an environment, the standard DHCP
options 60 and 43 cannot be used for IAPs.
This method describes how to set up a DHCP server to send option 43 with AirWave information to the IAP.
This section assumes that option 43 is sent per scope, because option 60 is being shared by other devices as
well.
The DHCP scope must be specific to Instant, and the PXE devices that use options 60 and 43 must not
connect to the subnet defined by this scope. This is because you can specify only one option 43 for a scope,
and if other devices that use option 43 connect to this subnet, they are presented with the information
specific to the IAP.
1. In Windows Server 2008, navigate to Server Manager > Roles > DHCP Server > Domain DHCP Server
> IPv4.
2. Select a scope [subnet]. Scope [10.169.145.0]145 is selected in the example shown in the figure below.
3. Right-click and select Advanced, and then specify the following options:
n Vendor class—DHCP Standard Options
n User class—Default User Class
n Available options—Select 043 Vendor-Specific Info
n String Value—ArubaInstantAP, tme-store4, 10.169.240.8, Aruba123 (which is the IAP description,
organization string, AirWave IP address or domain name, Pre-shared key, for AirWave)
Figure 90 Vendor-Specific DHCP options
Upon completion, the IAP shows up as a new device in AirWave, and a new group called tme-store4 is created.
Navigate to APs/Devices > New > Group to view this group.
Aruba Instant 6.5.0.0-4.3.0.0 | User Guide IAP Management and Monitoring | 313
To Next Page
Loading...
Need help?
General
