Extreme Networks

AnonymousM · ‎08-09-2018

I have a sr2208P switch and an AP130 and i configured a Hive Manager 8.2r2. Clients aren't receiving IP from DHCP server.

samantha_lynn · ‎08-15-2018

If you are using only one VLAN, then you need an access port. If you have more than one VLAN, you need a trunk port. We have a couple options for looking in to the DHCP issue once the switch ports are configured properly: vlan probe and/or packet capture.

To run a VLAN probe you will want to SSH in to the AP and run the following command (assuming we are testing VLAN 2, if this has changed, please change the last 2's to the new VLAN number)

int mgt0 dhcp-probe vlan-range 2 2

Please let me know the results of that probe. What that is doing is sending a DHCP packet down that VLAN, and if it gets any kind of response at all from a DHCP server, it considers the VLAN active and will tell you the IP scope we are working with. If it can't reach a DHCP server, you'll want to check your backend configuration to make sure that we are passing the VLAN traffic all the way through.

Additionally you could run a packet capture to see what DHCP packets we are getting, which would help narrow it down. For example if all we see are DHCP requests going out, we know that we aren't hearing anything back from the DHCP server, and we would investigate the VLAN and traffic flow. If we are getting a DHCP offer back but going no further, then we know that we can reach the DHCP server and we can troubleshoot from there. Depending on what HiveManager platform you are using, here is a guide to help you set up a packet capture if needed:

HiveManager (formerly NG, cloud.aerohive.com)- https://thehivecommunity.aerohive.com/s/article/Packet-Capture-in-NG

HiveManager Classic (myhive.aerohive.com)- https://thehivecommunity.aerohive.com/s/article/Packet-Capture

View solution in original post

samantha_lynn · ‎08-15-2018

If you are using only one VLAN, then you need an access port. If you have more than one VLAN, you need a trunk port. We have a couple options for looking in to the DHCP issue once the switch ports are configured properly: vlan probe and/or packet capture.

To run a VLAN probe you will want to SSH in to the AP and run the following command (assuming we are testing VLAN 2, if this has changed, please change the last 2's to the new VLAN number)

int mgt0 dhcp-probe vlan-range 2 2

Please let me know the results of that probe. What that is doing is sending a DHCP packet down that VLAN, and if it gets any kind of response at all from a DHCP server, it considers the VLAN active and will tell you the IP scope we are working with. If it can't reach a DHCP server, you'll want to check your backend configuration to make sure that we are passing the VLAN traffic all the way through.

Additionally you could run a packet capture to see what DHCP packets we are getting, which would help narrow it down. For example if all we see are DHCP requests going out, we know that we aren't hearing anything back from the DHCP server, and we would investigate the VLAN and traffic flow. If we are getting a DHCP offer back but going no further, then we know that we can reach the DHCP server and we can troubleshoot from there. Depending on what HiveManager platform you are using, here is a guide to help you set up a packet capture if needed:

HiveManager (formerly NG, cloud.aerohive.com)- https://thehivecommunity.aerohive.com/s/article/Packet-Capture-in-NG

HiveManager Classic (myhive.aerohive.com)- https://thehivecommunity.aerohive.com/s/article/Packet-Capture

AnonymousM · ‎08-09-2018

these are more details:

I configured the SSID and i'm able to see it but the client isn't receiving an IP from the DHCP server with is on the same vlan of the SSID (VLAN 2). The managment of the AP and the VLAN of the SSID is the same (VLAN 2). I even tried to change the configuration on the switchport from access vlan 2 to trunk and native vlan 2. I tried even a DHCP relay even that the dhcp server is in the same relay.

Any help please