WLC management interface vlan tagging
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-15-2021 05:25 PM - edited 07-05-2021 01:09 PM
Hey guys, I am trying to figure out what I am doing wrong in terms of setting up vlan tagging for WLC management interface, here is my setup
Test One: WLC 3504, Cisco switch 3560, Vlan99 is used for management
WLC Management Interface: 192.168.99.2/24
Vlan tagging: 0 (untagged)
On the switchport where WLC is connected
switchport mode trunk
switchport trunk native vlan 99
With this setup, I can ping WLC from a PC which connects to the access port vlan99 on the switch all works just fine.
However, I am trying to tag the management vlan on WLC, so I did another test
Test 2:
WLC 3504, Cisco switch 3560, Vlan99 is used for management
WLC Management Interface: 192.168.99.2/24
Vlan tagging: 99 tagged
On the switchport where WLC is connected
switchport mode trunk
switchport trunk native vlan 66
With this setup, the management interface on WLC is set to Vlan99, and I ensure that on the switch where the wlc is connected, it is set to trunk, vlan99 is allowed and is NOT set as the native vlan. However, I am not able to ping the WLC from a PC which connects to VLan99.
Is there anything wrong in Test 2 scenario ? I am doing it in the packet tracer, would that make any difference ?
Any suggestion would be highly appreciate.
- Labels:
-
Wireless LAN Controller
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-15-2021 05:40 PM
are you allow vlan 99 in trunk ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-15-2021 05:53 PM
Yes, I did not specify which vlans to allow in trunk, so I assume it means to allow all trunks. But I add another command to allow vlan 99, still the same, I can't ping WLC from the PC, nor from the switch
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-15-2021 06:27 PM
can you ping from the PC to the GW of the management VLAN ? since the PC and WLC management are in different VLAN then it need GW to connect between each other.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-15-2021 07:37 PM
WLC management interface and PC are both on Vlan 99.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-15-2021 11:45 PM
if you are using this setup on switch:
Test2:
WLC 3504, Cisco switch 3560, Vlan99 is used for management
WLC Management Interface: 192.168.99.2/24
Vlan tagging: 99
then use this
On the switchport where WLC is connected
interface gig0/X
switchport mode trunk
switchport trunk allowed vlan 99
Regards
Dont forget to rate helpful posts
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-19-2021 03:03 AM
All I can say is that packet-tracer is *NOT* a WLC. It is a little piece of training software which presents a simple and limited simulation of some Cisco network devices. Only the developers of packet tracer can tell you what it can and can't do and whether you've just discovered a bug. If they haven't documented it working that way then it's probably not supported that way but that does not reflect how a real WLC will work. If you want to experiment with anything other than their documented training configs then you should only do it with a real WLC.
https://www.netacad.com/sites/default/files/cisco-packet-tracer-faq.pdf
Q14. Does Packet Tracer support all the features found in Cisco devices?
A. No. The program supports a small subset of the features from Cisco devices. Packet Tracer uses simplified models of networking protocols and Cisco IOS; you should always compare your results to those obtained from real equipment. Practice on Packet Tracer is not a replacement of Practice on real equipment.
Please click Helpful if this post helped you and Select as Solution (drop down menu at top right of this reply) if this answered your query.
------------------------------
TAC recommended codes for AireOS WLC's and TAC recommended codes for 9800 WLC's
Best Practices for AireOS WLC's, Best Practices for 9800 WLC's and Cisco Wireless compatibility matrix
Check your 9800 WLC config with Wireless Config Analyzer using "show tech wireless" output or "config paging disable" then "show run-config" output on AireOS and use Wireless Debug Analyzer to analyze your WLC client debugs
Field Notice: FN63942 APs and WLCs Fail to Create CAPWAP Connections Due to Certificate Expiration
Field Notice: FN72424 Later Versions of WiFi 6 APs Fail to Join WLC - Software Upgrade Required
Field Notice: FN72524 IOS APs stuck in downloading state after 4 Dec 2022 due to Certificate Expired
- Fixed in 8.10.196.0, latest 9800 releases, 8.5.182.12 (8.5.182.13 for 3504) and 8.5.182.109 (IRCM, 8.5.182.111 for 3504)
Field Notice: FN70479 AP Fails to Join or Joins with 1 Radio due to Country Mismatch, RMA needed
How to avoid boot loop due to corrupted image on Wave 2 and Catalyst 11ax Access Points (CSCvx32806)
Field Notice: FN74035 - Wave2 APs DFS May Not Detect Radar After Channel Availability Check Time
Leo's list of bugs affecting 2800/3800/4800/1560 APs
Default AP console baud rate from 17.12.x is 115200 - introduced by CSCwe88390
