Meru Technical Note - DHCP request failing on AP332
Description
Scope
Solution
AP332 was failing DHCP L3 config and connected L2 by default.. A test AP320 was able to successfully connect either L2 or L3. The root cause was the DHCP request string from the AP320 was for an "AP300" while the AP332 was identified as an "AP332". This difference required a new product type in the DHCP server. After the new model ID was added the AP332 connected L3.
Use Case:DHCP request failing on AP332
Scope
KB ARTICLE TYPE: Configuration
RELATED PRODUCTS: AP332, Proteus DHCP server
RELATED SOFTWARE VERSIONS: 5.3-132
KEYWORDS: AP332, dhcp
Solution
AP332 was failing DHCP L3 config and connected L2 by default.. A test AP320 was able to successfully connect either L2 or L3. The root cause was the DHCP request string from the AP320 was for an "AP300" while the AP332 was identified as an "AP332". This difference required a new product type in the DHCP server. After the new model ID was added the AP332 connected L3.