Yes, the native vlan is configured, the switch ports the IAPs are on are untagged on the native vlan, we have the ports tagged with the employee wifi vlan (WLAN_WAP, vlan 2002) which is our secure wifi. For example:
ports 2:29 - 2:32 are the IAPs, the IAPs are all being assigned correct IPs from vlan 14 (/16 subnet)
Alpine3808:2 # show vlan "vlan_14" <<<Natve Vlan
VLAN Interface[3-202] with name "vlan_14" created by user
Tagging: 802.1Q Tag 14
Priority: 802.1P Priority 7
IP: 10.x.x.x/255.255.0.0
STPD: None
Ignore-stp: Disabled on this vlan
Ignore-bpdu: Disabled on this vlan
Protocol: IP = EtherType:0806 EtherType:0800
Loopback: Disable
RateShape: Disable
QosProfile:QP1
QosIngress:None
Ports: 163. (Number of active ports=52)
Flags: (*) Active, (!) Disabled
(B) BcastDisabled, (R) RateLimited, (L) Loopback
(g) Load Share Group
Untag: *2:29 *2:30 *2:31 *2:32
Tagged: *1:1 *1:3 *1:4
Alpine3808:3 #
===================================================
Alpine3808:4 # sh vlan "WLAN_WPA" <<<Employee wifi
VLAN Interface[10-209] with name "WLAN_WPA2" created by user
Tagging: 802.1Q Tag 2002
Priority: 802.1P Priority 7
STPD: None
Ignore-stp: Disabled on this vlan
Ignore-bpdu: Disabled on this vlan
Protocol: Match all unfiltered protocols.
Loopback: Disable
RateShape: Disable
QosProfile:QP1
QosIngress:None
Ports: 7. (Number of active ports=7)
Flags: (*) Active, (!) Disabled
(B) BcastDisabled, (R) RateLimited, (L) Loopback
(g) Load Share Group
Tagged: *1:1 *1:3 *1:4 *2:29 *2:30 *2:31 *2:32
Alpine3808:5 #