This article describes a specific DHCP issue experienced by a customer: 2 wireless access points AP47 connected to an access EX4400 switch (configured as trunk ports) could not obtain an IP address from a DHCP server running on the core for the AP management VLAN. The core was receiving DHCP traffic from the APs, but the DHCP process never completed.

• APs stay offline / no management IP address.
• On the core DHCP server, the AP MAC addresses appear in the DHCP binding table but remain in SELECTING instead of transitioning to BOUND.
• The same binding entries refresh repeatedly but never complete.

The access switch ports where the APs were connected were configured as trunks with a native VLAN set to the AP management VLAN. This created a VLAN handling mismatch for the AP management/DHCP traffic, so the DHCP exchange did not fully complete.

Fix implemented:

• Removed the native VLAN setting from the AP-facing trunk ports (kept the AP management VLAN explicitly allowed on the trunk).
• After removing the native VLAN, DHCP bindings transitioned to BOUND and the APs received valid leases.

Note: For AP uplinks, keep trunk VLAN handling consistent. Avoid using a native VLAN unless you intentionally want management traffic untagged and have confirmed the AP configuration matches that design.

 https://www.juniper.net/documentation/us/en/hardware/ap47/Other/ap47-ethernet-redundancy.html