Capwap Trunk issues

  • 1
  • Question
  • Updated 4 years ago
  • Answered
We just deployed 7 more AP121s to a remote facility and having some issues with trunking and capwap connectivity being lost.

The network follows;

From our main facility where our virtual Hivemanger lives, we are connected via provider to one of our remote buildings.  

Remote building (#1) has Cisco Layer 3 switch (3750) and is routing vlans 14 and 15.
Vlan 14 is for this building.

Next building (# 2) is connected via a wireless Ubiquity Air Bridge back to #1.  It has a Layer 3 Switch (3750) as well and can route all network vlans/traffic. Vlan 15 is used for this building primarily, but both are used.

Vlan 14=172.23.14.1
Vlan 15=172.23.15.1

Here's what happens...

New APs are connected to cisco switch as access switchports and hive manager can see them and push configs to them.

When switchports on the Cisco switch at # 2 are changed to Trunk ports after the configs are pushed, connectivity to Hive manager is lost.

switchport trunk encapsulation dot1q
switchport trunk allowed vlan 1-1000
switchport mode trunk

What should the management and native vlans be set to for the above?

Should I use static IPs on the APs

Thanks for any help, 







  
Photo of JamesC

JamesC

  • 12 Posts
  • 0 Reply Likes

Posted 4 years ago

  • 1
Photo of BJ

BJ, Champ

  • 374 Posts
  • 45 Reply Likes
- What should the management and native vlans be set to for the above?
 
That really depends on depends on you LAN. Chances are, your native vlan is 1 and your management vlan could be either 14 or 15, if I read correctly. If you have a dhcp server accessible from either of those two vlans, you shouldn't need to statically assign addresses, unless you wish to do so. 
I would push the config to the APs and check the mac address table on the 3750 interfaces the APs are connected. Make sure the AP mac is on the correct vlan.

Alternatively, for installation purposes, you could set the switch interfaces to trunk and set the native vlan to vlan 14 or 15, so untagged traffic will traverse. Then after the config is pushed, set the switchport native vlan back to 1.  

Best,
BJ
Photo of Eastman Rivai

Eastman Rivai, Official Rep

  • 146 Posts
  • 17 Reply Likes
What VLANs did you assign to the AP mgt on your network policy? Based on the switch configuration given, the AP mgt VLAN should be anything from 1 to 100 and the native VLAN should be VLAN 1.

I hope this answers your question.
Photo of JamesC

JamesC

  • 12 Posts
  • 0 Reply Likes
Management and Native were both set on vlan 1, default.  Vlan 1 on the Cisco switch is shut down as we use vlans 14 and 15.

We use EIGRP routing for the entire network

Currently, I have 2 APS that I pushed configs to during early troubleshooting (when it became apparent that something was not working)  that will need to be manually reset (paperclip).

The other 5 are on cisco switchport access ports in an unconfigured (out of the box) state.  APs are getting DHCP from the main datacenter servers.  I can change the access ports to 14 or 15 and they will get an IP that corresponds.

Changing any (even unconfigured ones) to trunk ports causes Hivemanager to lose connectivity...

The 2 fubar APs are showing this under the mac address table....vlan 1


1    4018.b180.4380    DYNAMIC     Fa1/0/13 
1    4018.b180.4c80    DYNAMIC     Fa1/0/14


 
Photo of JamesC

JamesC

  • 12 Posts
  • 0 Reply Likes
I meant no IP address on vlan 1..not shut down.
Photo of Eastman Rivai

Eastman Rivai, Official Rep

  • 146 Posts
  • 17 Reply Likes
If the AP is on VLAN1, based on your information VLAN1 is not routable, any device on this VLAN will not be able to go anywhere apart form this VLAN. 

Since the native (untagged) VLAN of the AP is VLAN1, when connected to an access port the AP will connect to the access port's VLAN. When you changed it to trunk, the native VLAN changed to VLAN1 that is not routable, so the AP lost its network connection.

You will need to change the native VLAN to either VLAN 14 or 15 in order for the AP to get network connection. You will also need to change the AP management and native VLAN to either 14 or 15.

suggested switch config
switchport trunk allowed 1-100
switchport trunk native VLAN 14 ( or 15 depending on the location)

suggested AP config
AP mgt VLAN 14, native VLAN 14 -- connected to switchport with native VLAN 14
AP mgt VLAN 15, native VLAN 15 -- connected to switchport with native VLAN 15
Photo of JamesC

JamesC

  • 12 Posts
  • 0 Reply Likes
Thanks!!  That sorted it.