07-26-2018 04:14 PM
07-26-2018 05:04 PM
To make sure it can reach a DHCP server, please run the following command:
int mgt0 dhcp-probe vlan-range # #
If you want to test one VLAN you would enter the VLAN number you are testing where you see "#". So if I was running this command for VLAN 5, the command would read "int mgt0 dhcp-probe vlan-range 5 5". You'll want to test the VLAN that this AP is on (likely your native VLAN).
This command sends a DHCP packet down the VLAN you indicate. If it gets any kind of response from a DHCP server, it will consider the test successful, and we'll know the AP can reach a DHCP server. If the test fails, we'll know it is because there is no DHCP server responding for that VLAN. This either means the VLAN the AP is on is not properly set up in the backend network (not all ports support it for instance), or that the DHCP for the VLAN is unresponsive.
07-26-2018 09:11 PM
I would also look at the upstream switch to see which vlan the AP's MAC address appears.
07-26-2018 05:04 PM
To make sure it can reach a DHCP server, please run the following command:
int mgt0 dhcp-probe vlan-range # #
If you want to test one VLAN you would enter the VLAN number you are testing where you see "#". So if I was running this command for VLAN 5, the command would read "int mgt0 dhcp-probe vlan-range 5 5". You'll want to test the VLAN that this AP is on (likely your native VLAN).
This command sends a DHCP packet down the VLAN you indicate. If it gets any kind of response from a DHCP server, it will consider the test successful, and we'll know the AP can reach a DHCP server. If the test fails, we'll know it is because there is no DHCP server responding for that VLAN. This either means the VLAN the AP is on is not properly set up in the backend network (not all ports support it for instance), or that the DHCP for the VLAN is unresponsive.