topic Re: T750 on vSZH 5.2 with vSZD also will not provide DHCP address for client connections in Access Points - Indoor and Outdoor

T750 on vSZH 5.2 with vSZD also will not provide DHCP address for client connections

eddie_sanmarco — Wed, 30 Dec 2020 17:37:22 GMT

I have looked at the troubleshooting area on the controller for my test client and I noticed the difference between a good complete connection from the R720 and the T750. The R720 provided DHCP offering form the DHCP server and the T750 did not so it never gets the DHCP address.

Any help is appreciated. I'm thinking is there anything special about the T750 that needs another option configured on the DHCP server? option 43 is already there and as I said everything works fine with R720 but I just bought these T750 for an outdoor event.

Thanks,

Eddie

Re: T750 on vSZH 5.2 with vSZD also will not provide DHCP address for client connections

syamantakomer — Mon, 04 Jan 2021 19:48:08 GMT

H Eddie,

Is your issue is related to AP not getting IP or AP not passing IPs to wireless client?

If option 43 is working for R720 then it should work fine for T750 as well. What are the complete vSZ, vDP and AP firmware version?

Re: T750 on vSZH 5.2 with vSZD also will not provide DHCP address for client connections

eddie_sanmarco — Tue, 05 Jan 2021 14:08:54 GMT

Controller was upgraded from 3.6.2 to 5.2.1. Only on T750 it doesn't work. Also bridge @AP SSID work fine with providing a local IP so this is pointing to an issue with T750 and the Data Plane it looks like. I just can't believe that no one else in the world has deployed 5.2.1 with T750 outdoor APs. We can't be the 1st.

Re: T750 on vSZH 5.2 with vSZD also will not provide DHCP address for client connections

eddie_sanmarco — Tue, 05 Jan 2021 14:09:25 GMT

Oh sorry, client getting DHCP address.

Re: T750 on vSZH 5.2 with vSZD also will not provide DHCP address for client connections

syamantakomer — Tue, 05 Jan 2021 14:41:53 GMT

Sorry for my poor understanding, are you saying T750 cannot get an IP or it works fine but client connecting to it not getting IP address.

In your 2nd last comment, you are referring Bridge SSID works fine but on last comment you have mentioned client getting DHCP address, so I am confused.

To simplify the query, please confirm exactly what issue your are hitting.

T750 APs are not getting DHCP IP address (Hence cannot connect to SZ and DP).

Client connecting to T750 APs for tunneled SSID are not getting IP address. However, bridged SSID works fine with T750 APs on same setup.

Re: T750 on vSZH 5.2 with vSZD also will not provide DHCP address for client connections

eddie_sanmarco — Tue, 05 Jan 2021 14:45:21 GMT

I am saying the T750 is getting an IP address just fine. The client is not getting an IP address while connected to an SSID that "tunnels". If we use an SSID that is Bridge @AP then we can get a dhcp address on that local subnet. So to me it seems that there is a problem with T750 and the Data plane tunnel to get an IP address to the client.

Re: T750 on vSZH 5.2 with vSZD also will not provide DHCP address for client connections

eddie_sanmarco — Tue, 05 Jan 2021 14:46:29 GMT

Client connecting to T750 APs for tunneled SSID are not getting IP address. However, bridged SSID works fine with T750 APs on same setup.

Re: T750 on vSZH 5.2 with vSZD also will not provide DHCP address for client connections

syamantakomer — Tue, 05 Jan 2021 14:57:49 GMT

Got it!

Check if AP is connecting to data plane or not.

SSH into one of the T750 APs and run below commands.

get tunnelmgr
ping <DP_IP_address>
get wlanlist

If AP is connected to DP, then next step is, run a packet capture on AP and DP at the same time while connecting one client to tunneled SSID on a T750 AP. Once done, verify the captures for DHCP/bootp packets.

This may be a bit in depth troubleshooting so if you are not sure how to troubleshoot further, please open a case with all the available information.

AP support log (working vs non working AP)
get tunnelmgr output (working vs non working AP)
packet captures from the AP and the DP.
Test client MAC address

Re: T750 on vSZH 5.2 with vSZD also will not provide DHCP address for client connections

eddie_sanmarco — Tue, 05 Jan 2021 16:30:59 GMT

No this isn't too in depth. I am currently working from Home and have a coworker who is workikng on this also from teh office. He is the one with teh support ticket open. Maybe we shouldn't approach this from both sides? I simply wanted to hear form someonet hat has done this with T750 on vSZ using vSZD for tunnel SSID

Re: T750 on vSZH 5.2 with vSZD also will not provide DHCP address for client connections

syamantakomer — Tue, 05 Jan 2021 16:50:44 GMT

Hi Eddie,

I have checked if we have received any similar issue recently and found one (only one), which is still being troubleshooted.

May I know if you have an existing case already open for the same issue? If not, please open a support case and report the issue to support.

If possible, share the case number.

Re: T750 on vSZH 5.2 with vSZD also will not provide DHCP address for client connections

eddie_sanmarco — Tue, 05 Jan 2021 17:16:11 GMT

It's probably our ticket. So there is no one else with T750 on vSZH using vSZD? or that are reporting any issues? Because if that's the case then I wish they would comment that they are working fine.

Here is our current ticket...

Case ID: 01149901

Subject: Having issue with DHCP on T750

Description:

Issue# Having issue with DHCP on T750
SN# 983VVKTBKKK5GGW46B8R15KMHK0K
Phone# 4806443925
Best Time # MST

Case Opened:: Tuesday December 29, 2020 10:47 pm
Case Closed:: n/a
Case Owner:: Tyler Palich
Customer Reference Number:: n/a
Partner Reference Number:: n/a
Engineering Reference Number:: n/a

Type:: Software
Status:: In Progress
Priority:: P3
Case Escalation Status:: Case Escalated
Product Description:: vSZ-E
Software Version:: 5.2.0.x 515
Preferred Communication:: Phone

Re: T750 on vSZH 5.2 with vSZD also will not provide DHCP address for client connections

syamantakomer — Tue, 05 Jan 2021 18:31:30 GMT

Hi Eddie,

It is the same ticket I was talking about.

No, there are no other users who reported this issue to support yet or issue may be limited to your setup.

I have asked support team to reproduce the issue in lab and see if it is reproducible. Please continue working with support and they should be able to fix it.

Also lets wait if there is any other customer facing same issue.