Are you trying to get a DHCP address from the native vlan (200)? do you have a scope set up for it? Is the DHCP server also on VLAN 200?

@Ron DHCP server is on a different VLAN. Trying to get an address from a 211 VLAN. the 205.35 is just the management address. The gateway is an NSA 2400. There is a scope for the 200 VLAN in there. When I had this AP on a different switch, it grabbed an IP address from that scope, and I can still see the MAC and IP for this AP on the DHCP server, but not connected obviously. The other switch I was testing on, has this same VLAN configuration (and port configuration for a different AP), that works.

Did you create vlan 211 on this switch? Type show vlan

Again, VLANS are handled by VTP. show VLAN shows all VLAN's as the rest of the switches, as expected. sh vlan gives the list, with 211 servers active present. It is not activated on any ports however, it should still traverse over the trunk gi1/0/24 and g1/0/1, correct? I CAN ping these servers addresses from the switch CLI itself.

Is the DHCP server on the same VLAN (211) as the client? Pinging the DHCP address form switch management IP doesn't mean much in this case. ICMP has source address of the management interface and unicast destination address of the DHCP server and are probably routed between VLANs. DHCP discover packets are sent from 0.0.0.0 to 255.255.255.255 and if the DHCP server is not on the same subnet/VLAN as the client and you don't have ip helper-address configured on SVI it will not reach DHCP server.

@PenguinCoder, since you mention the DHCP server is on a different VLAN, does your VLAN 200 L3 interface (i.e. the gateway) have a DHCP helper/relay properly configured?

@Ylearn The Cisco switches here are only L2, no L3. The SonicWall does all the routing, and has the proper IP helper entry for DHCP ports 67,68. Every other switch on this network is properly relaying and receiving the DHCP requests. The SonicWall, is configured for DHCP forwarding to the appropriate server and for the 200 (and other) VLANs.

Spanning tree. Could DHCP be timing out before the port starts forwarding?

@Ron Every port has spanning-tree portfast enabled already, except for the trunk ports. 1/0/1, and 1/0/24. As they're trunk ports and going back to another switch anyway, they will not be portfast'd.

OK, we're all guessing in the dark. Can you post your switch config, and perhaps a simple diagram?

I don't see portfast enabled?

@Ron I've added more information for this switch to the post. Again, portfast is enabled on all NON trunked ports. The UniFi is a wireless AP, and from what I understand, should not have portfast enabled on it.

Which port is the link towards the DHCP server? Just realized that port Gi1/0/1 is configured in trunk mode, but the output of show interface statusshows only VLAN 100 on it, no trunk. If this is the link towards DHCP server, what is the configuration of the port on the other end of this link?

I disagree. If the AP is trying to get an address, the trunk port needs portfast as well.

@Ron I've added portfast to the AP port (24) and restarted the AP and still not receiving a DHCP address. Please also remember, this is happening for EVERY port behind this switch. It's not just limited to the AP. I don't know how the trunk port is list as only VLAN 100. gi1/0/1 is the trunk port back to the DHCP server, and is/should be configured as such. The MDF port (1/0/20) on the other side of THIS switch's 1/0/1, is configured as trunk mode. No native vlan.

@DanielYusteAroca makes a very good point I didn't see that at first. Your uplink isn't trunking VL 200.

Could you please add the output of show interfaces trunk in both switches connected by this link? Is there any log message in the switches that could be related to this issue?

@DanielYusteAroca I've added the sh interfaces trunk from the problem switch. Also I've updated the post after verfying that the uplink ports ARE in trunk mode.

Have you posted again the output of show interface status? Now it says Gi1/0/1 is trunk, but I´ve checked the edit history and it was saying only vlan 200 before. Is your problem intermitent?

@DanielYusteAroca I made the changes, saved the config, reloaded from the sh run, and then checked and reposted the show interface status again. The one there is what it currently is and should be/remain. The problem is not intermittent, it just has never worked (DHCP behind this switch) that I'm aware of.

I noticed you have a "switchport trunk" command instead of a "switchport mode trunk" command on Gi1/0/1. Is this a typo? If not, you might be having some trunk autonegotiation issues.

@AVery you are correct, that would be my typo during sanitizing, or trying to. It is switchport mode trunk.

What is the status of the port that gi 1/0/1 is plugged into? Can you post the output of show trunk from that switch?

@Ron Status of the MDF Gi1/0/20 (connection to the problemswitch gi1/0/1) posted. I cannot post the entire config of the MDF, too much to sanitize as it's a stackwise configuration.

Not trying to be good at "Stump the chump" I was the first one stumped! @Avery - `Pruning not currently enabled in this device's VTP administrative domain.- on both switches.

Are you running dhcp-snooping on the MDF switch, the switch the DHCP server is connected to, or any inbetween?

@Avery no,I have not setup any dhcp snooping currently. MDF switch and problem switch are connected without any switches in between.

When you say you put the UniFi on another switch with the same configuration, did you mean the other switch was also using VLAN 200 for the native VLAN for the UniFi port?

@PenguinCoder, to rule out any sort of spanning tree issues, the next output I would like to see is the output from sh spanning-tree interface g 1/0/1 as well as Gi1/0/20 from the MDF. Also sh spanning-tree vlan 200 from both switches may be nice.

@AveryAbbott That is correct. I used the same port configuration on another switch, and the Ubiquiti AP was successful in getting DHCP address and being adopted. Moving back to the ProblemSwitch, UniFi controller can't even see the AP. I will get the STP information.

@Ylearn STP information added.

So if you connect the WLAN AP to another switch configured like this: >interface SomeSwitchPort > switchport trunk native vlan 200 > switchport mode trunk >! Then it's able to get an IP address via DHCP?

This should be a comment, not an answer. If I take the exact port setup from problemswitch, put it on another switch with the ubiquity plugged in, then yes, it gets DHCP address.