I was at a customers that wanted a new ssid configured on his 20 1252 AP's and to stand up a new one with the olds and new SSID on it. Added the vlans, trunked them down and configured the interfaces and SSID's on the existing AP's no biggie. The new AP(not really new been kicking around in a lab) is giving me some weird issues. I deleted the exisiting config from it and took one of the running configs fromm the others that are working, modified the name and ip and pasted it in. This should have worked just fine. However the trunk port on the 4507 will not come up. The radio's are up and so is the BVI, however I cannot ping to it since the trunk is down. I started looking at the config and the thing I notice is that the AP's are in vlan 2, and the native vlan is set for vlan 2 on all the working trunk ports on the switch. However the AP's do not have vlan 2 on them, and their native vlan is 1. This should not work! I always thought the native had to match on both sides?? In any case I am probably missing something stupid, I have been up since 4am it was a 4 hour drive to get here. Oh and I have to go back and make firewall changes at midnight. Here is the relavent configs please let me know if its something stupid I usually do a lot of controller based installs havnet done a autonomous one in years. Thanks!
Here is a port on the switch
description AP 1 - SMT
switchport access vlan 2
switchport trunk native vlan 2
switchport trunk allowed vlan 2,9,15
switchport mode trunk
Here is the AP hanging off that works fine
Virtual LAN ID: 1 (IEEE 802.1Q Encapsulation)
vLAN Trunk Interfaces: Dot11Radio0
This is configured as native Vlan for the following interface(s) :
actually, native VLAN doesn't have to match on two sides of a trunk, in fact it's quite common with autonomous APs. Your BVI1 is usually tied to a native VLAN 1, but switch port native VLAN is usually configured for whatever VLAN you want AP's management IP to belong to, in your case VLAN 2.
When you connect two catalyst switches together with a trunk that has different native VLAN configured on two sides, you will keep getting logging messages warning you about it. It's not recommended, but some scenarios require such setup.
Something else is wrong, maybe a physical issue. When you say the trunk is down, do you mean the interface is down ? Can you paste config of bad switch port and bad AP?