Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements
Users might experience few discrepancies in Search results. We are working on this on our side. We apologize for the inconvenience it may have caused.
New Member

2504 WLC

Hi all,

I am having an issue with deploying 2504 WLC for multiple SSIDs with different VLANS. I cant seem to make the access points to join the controller on a trunk port. they only work when the WLC is connected to an access port. Anyone encounter this or has a solution? Thank you in advance

1 ACCEPTED SOLUTION

Accepted Solutions
Bronze

the native vlan on the

the native vlan on the switchport is the vlan for "untagged packets"
th make the controller and switch match:

1) in the controller you can specify vlan "0" for the management interface
this results in untagged packets to send to the switchport
so set the switchport to access or set the native vlan to make a match.

2) alternatively set the switchport to trunk
and set the management vlan id in the controller to the desired vlan id (something other than "0").

if the management vlan is on a different subnet than the AP, you can help the AP to discover the controller by using DNS entry or DHCP option.

if you use multiple controller ports to the same switch, this also needs some extra attention.

5 REPLIES
Hall of Fame Super Gold

I cant seem to make the

I cant seem to make the access points to join the controller on a trunk port. they only work when the WLC is connected to an access port. Anyone encounter this or has a solution?

APs in H-REAP/FlexConnect solution connect to a trunk port.

New Member

Hi Leo and Chandana, 

Hi Leo and Chandana, 

Thanks for the reply. I am not doing flexconnect they are just local APs but should be in different SSID With different VLans. The APs are on access ports and that is good but I think the controller should be on a trunk port for this to work right? Are you saying that I should ignore the native vlan and put the management vlan as the native vlan on the trunk?

Bronze

the native vlan on the

the native vlan on the switchport is the vlan for "untagged packets"
th make the controller and switch match:

1) in the controller you can specify vlan "0" for the management interface
this results in untagged packets to send to the switchport
so set the switchport to access or set the native vlan to make a match.

2) alternatively set the switchport to trunk
and set the management vlan id in the controller to the desired vlan id (something other than "0").

if the management vlan is on a different subnet than the AP, you can help the AP to discover the controller by using DNS entry or DHCP option.

if you use multiple controller ports to the same switch, this also needs some extra attention.

Native VLAN of the trunk port

Native VLAN of the trunk port should be set to management VLAN of the access point.

As Leo mentioned above, trunk ports for local mode APs are not necessary. Access mode ports are the best practice for local mode APs.

For Flex Connect APs, trunk port is a must with the native management vlan and same vlan should be used for native vlan in the flex connect configuration of AP or flex connect group.

-Chandana

New Member

thank you all it was a native

thank you all it was a native vlan issue I was able to resolve this

97
Views
0
Helpful
5
Replies
CreatePlease to create content