We recently began deploying EX3400 as replacement for EX3000 in our MDU/MTU sites. The feature sets we're relying on are dot1x radius based authentication and private vlans (isolated); all subscribers need to be isolated.
With the EX3300s, as a wireless client loses association with an AP and associate with a new AP, the EX3000 will update it's forwarding table and dot1x details about the wireless device and rarely does a client know they're moving between APs.
Using the EX3400, the wireless client can initially associate with an AP and get online but as the client moves and associates with a newer AP, the wireless client will not get an IP address until we either manually clear the forwarding table OR the dot1x record for the client on the EX3400.
The wireless client will continue to reassociate itself with the new AP every 30 second or so as a retry, but the EX3400 is maintaining the old AP port as it's layer 2 port.
Using a port-mirror setup on the EX3400, I can see that after the wireless client associates with the new AP, DHCP Discovery packets are being being received on the switch from the wireless client. These packets are received and transmitted by the EX3400 without a vlan as our vlan assignment happens via radius and dot1x, ie. the switch is not performing a dot1x radius lookup prior to allowing the DHCP Discovery packet.
While on boarding the EX3400 I needed to retool some of the config syntax, it's very possible I missed something in the conversion of the configs.
Attached are example configurations for both the EX3300 & EX3400. (I've tried to upload them twice now, nothing saying an error.. Perhaps they need to be 'processed' first).
Thanks.
-Sean