06-27-2018 02:17 PM
I have created a network policy on the HiveManager NG cloud, but my clients are not getting DHCP addresses. I tried to do the VLAN Probe and it says my VLAN's are not available. Please help. I tried checking all layers. I can connect to the AP via ssh and can ping other networks from the AP, but my clients aint getting DHCP ips
Solved! Go to Solution.
07-02-2018 03:07 PM
Hi Thabiso,
Thank you,
Could you go to the CLI of the AP with a Terminal Client like Putty(Windows) or OpenSSH admin@ip-of-AP
HowTo: https://thehivecommunity.aerohive.com/s/article/How-to-Connect-to-an-AP-using-SSH
Please try this command:
int mgt0 dhcp-probe vlan-range 340 340
Then, this command as well:
int mgt0 dhcp-probe vlan-range 350 350
They Should Pass If all is tagged up-stream and DHCP is properly configured.
If Not, we can continue Triage:
So far, you've confirmed the Switch-Port that the AP is connecting to Tags correctly.
Are you using vLAN 340 or 350 for the User-Profiles, or both?
If so, then the DHCP Probe commands above should have passed but if they fail, We'll want to locate where the drop is.
Please perform a Client Monitor with the MAC Address of the client device that's failing. We will want to determine which part of the DHCP Handshake is failing, OR if the problem is Radio Association.
Client Monitor: https://thehivecommunity.aerohive.com/s/article/Client-Monitor-in-NG
Hope this helps,
David Souri
HiveCommunity Moderator
07-02-2018 02:48 PM
@David Souri the Native vlan is Vlan 63 and Management vLAN is Vlan 63 as well.
@Sam Lujan yes am using the radius server to authenticate
06-28-2018 05:40 PM
Are you using a radius server to authenticate?
06-28-2018 02:51 PM
Hi Thabiso,
Thank you for that information.
Can you tell me what the Native and Management vLAN assignments are for the Network Policy?
Based on that Switch Configuration:
General Mode PVID: 63 | This is what Aerohive refers to as Native
General Mode Tagged VLANs: These should be User-Profile assosciated VLANs and the Aerohive Management VLAN.
Happy to assist,
David Souri
HiveCommunity Moderator
06-28-2018 10:05 AM
I believe that the DHCP Scope is working fine, I have double checked this morning. Below is my config on the port that the AP is connected.
Port: Gi1/0/1
VLAN Membership Mode: General Mode
Access Mode VLAN: 1 (default)
General Mode PVID: 63
General Mode Ingress Filtering: Enabled
General Mode Acceptable Frame Type: Admit All
General Mode Dynamically Added VLANs:
General Mode Untagged VLANs: 63
General Mode Tagged VLANs: 340,350
General Mode Forbidden VLANs:
Trunking Mode Native VLAN: 1 (default)
Trunking Mode Native VLAN Tagging: Disabled
Trunking Mode VLANs Enabled: All
Private VLAN Host Association: none
Private VLAN Mapping:
Private VLAN Operational Bindings:
Default Priority: 0
Protected: Disabled
~ The User-Profile and VLAN were pushed to the client aswell.
06-27-2018 08:29 PM
Hi Thabiso,
I can agree with Bill, that the next place to look would be the Switch-Port that the AP is connected to, after confirming that the DHCP Scope is correct at the Server, and that all Ports between the DHCP Server and AP are allowing the correct vLAN Tags.
Additionally, If the User-Profile and vLAN assignment was created in Hivemanager, but an Update was not pushed to the APs, the clients may still be getting assigned default vLAN attributes.
Happy to help,
David Souri
HiveCommunity Moderator