<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: WLC management interface vlan tagging in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/wlc-management-interface-vlan-tagging/m-p/4389283#M228460</link>
    <description>&lt;P&gt;All I can say is that packet-tracer is *NOT* a WLC.&amp;nbsp; It is a little piece of training software which presents a simple and limited simulation of some Cisco network devices.&amp;nbsp; Only the developers of packet tracer can tell you what it can and can't do and whether you've just discovered a bug.&amp;nbsp; 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.&amp;nbsp; If you want to experiment with anything other than their documented training configs then you should only do it with a real WLC.&lt;BR /&gt;&lt;A href="https://www.netacad.com/sites/default/files/cisco-packet-tracer-faq.pdf" target="_blank"&gt;https://www.netacad.com/sites/default/files/cisco-packet-tracer-faq.pdf&lt;/A&gt;&lt;BR /&gt;Q14. Does Packet Tracer support all the features found in Cisco devices?&lt;BR /&gt;A. &lt;STRONG&gt;No&lt;/STRONG&gt;. 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.&lt;/P&gt;</description>
    <pubDate>Mon, 19 Apr 2021 10:03:13 GMT</pubDate>
    <dc:creator>Rich R</dc:creator>
    <dc:date>2021-04-19T10:03:13Z</dc:date>
    <item>
      <title>WLC management interface vlan tagging</title>
      <link>https://community.cisco.com/t5/wireless/wlc-management-interface-vlan-tagging/m-p/4387843#M228345</link>
      <description>&lt;P&gt;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&lt;/P&gt;&lt;P&gt;Test One: WLC 3504, Cisco switch 3560, Vlan99 is used for management&lt;/P&gt;&lt;P&gt;WLC Management Interface: 192.168.99.2/24&lt;/P&gt;&lt;P&gt;Vlan tagging: 0 (untagged)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;On the switchport where WLC is connected&lt;/P&gt;&lt;P&gt;switchport mode trunk&lt;/P&gt;&lt;P&gt;switchport trunk native vlan 99&lt;/P&gt;&lt;P&gt;With this setup, I can ping WLC from a PC which connects to the access port vlan99 on the switch all works just fine.&amp;nbsp;&lt;/P&gt;&lt;P&gt;However, I am trying to tag the management vlan on WLC, so I did another test&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Test 2:&lt;/P&gt;&lt;P&gt;WLC 3504, Cisco switch 3560, Vlan99 is used for management&lt;/P&gt;&lt;P&gt;WLC Management Interface: 192.168.99.2/24&lt;/P&gt;&lt;P&gt;Vlan tagging: 99 tagged&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;On the switchport where WLC is connected&lt;/P&gt;&lt;P&gt;switchport mode trunk&lt;/P&gt;&lt;P&gt;switchport trunk native vlan 66&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;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.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is there anything wrong in Test 2 scenario ? I am doing it in the packet tracer, would that make any difference ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any suggestion would be highly appreciate.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 05 Jul 2021 20:09:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wlc-management-interface-vlan-tagging/m-p/4387843#M228345</guid>
      <dc:creator>joezhou1026aus53709</dc:creator>
      <dc:date>2021-07-05T20:09:18Z</dc:date>
    </item>
    <item>
      <title>Re: WLC management interface vlan tagging</title>
      <link>https://community.cisco.com/t5/wireless/wlc-management-interface-vlan-tagging/m-p/4387846#M228346</link>
      <description>&lt;P&gt;are you allow vlan 99 in trunk ?&lt;/P&gt;</description>
      <pubDate>Fri, 16 Apr 2021 00:40:12 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wlc-management-interface-vlan-tagging/m-p/4387846#M228346</guid>
      <dc:creator>MHM Cisco World</dc:creator>
      <dc:date>2021-04-16T00:40:12Z</dc:date>
    </item>
    <item>
      <title>Re: WLC management interface vlan tagging</title>
      <link>https://community.cisco.com/t5/wireless/wlc-management-interface-vlan-tagging/m-p/4387849#M228347</link>
      <description>&lt;P&gt;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&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 16 Apr 2021 00:53:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wlc-management-interface-vlan-tagging/m-p/4387849#M228347</guid>
      <dc:creator>joezhou1026aus53709</dc:creator>
      <dc:date>2021-04-16T00:53:16Z</dc:date>
    </item>
    <item>
      <title>Re: WLC management interface vlan tagging</title>
      <link>https://community.cisco.com/t5/wireless/wlc-management-interface-vlan-tagging/m-p/4387860#M228348</link>
      <description>&lt;P&gt;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.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 16 Apr 2021 01:27:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wlc-management-interface-vlan-tagging/m-p/4387860#M228348</guid>
      <dc:creator>MHM Cisco World</dc:creator>
      <dc:date>2021-04-16T01:27:45Z</dc:date>
    </item>
    <item>
      <title>Re: WLC management interface vlan tagging</title>
      <link>https://community.cisco.com/t5/wireless/wlc-management-interface-vlan-tagging/m-p/4387883#M228349</link>
      <description>&lt;P&gt;WLC management interface and PC are both on Vlan 99.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 16 Apr 2021 02:37:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wlc-management-interface-vlan-tagging/m-p/4387883#M228349</guid>
      <dc:creator>joezhou1026aus53709</dc:creator>
      <dc:date>2021-04-16T02:37:15Z</dc:date>
    </item>
    <item>
      <title>Re: WLC management interface vlan tagging</title>
      <link>https://community.cisco.com/t5/wireless/wlc-management-interface-vlan-tagging/m-p/4387948#M228351</link>
      <description>&lt;P&gt;if you are using this setup on switch:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Test2:&lt;/P&gt;
&lt;P&gt;WLC 3504, Cisco switch 3560, Vlan99 is used for management&lt;/P&gt;
&lt;P&gt;WLC Management Interface: 192.168.99.2/24&lt;/P&gt;
&lt;P&gt;Vlan tagging: 99&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;then use this&amp;nbsp;&lt;/P&gt;
&lt;P&gt;On the switchport where WLC is connected&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;interface gig0/X&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;switchport mode trunk&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;switchport trunk allowed vlan 99&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards&lt;/P&gt;
&lt;P&gt;Dont forget to rate helpful posts&lt;/P&gt;</description>
      <pubDate>Fri, 16 Apr 2021 06:45:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wlc-management-interface-vlan-tagging/m-p/4387948#M228351</guid>
      <dc:creator>Sandeep Choudhary</dc:creator>
      <dc:date>2021-04-16T06:45:13Z</dc:date>
    </item>
    <item>
      <title>Re: WLC management interface vlan tagging</title>
      <link>https://community.cisco.com/t5/wireless/wlc-management-interface-vlan-tagging/m-p/4389283#M228460</link>
      <description>&lt;P&gt;All I can say is that packet-tracer is *NOT* a WLC.&amp;nbsp; It is a little piece of training software which presents a simple and limited simulation of some Cisco network devices.&amp;nbsp; Only the developers of packet tracer can tell you what it can and can't do and whether you've just discovered a bug.&amp;nbsp; 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.&amp;nbsp; If you want to experiment with anything other than their documented training configs then you should only do it with a real WLC.&lt;BR /&gt;&lt;A href="https://www.netacad.com/sites/default/files/cisco-packet-tracer-faq.pdf" target="_blank"&gt;https://www.netacad.com/sites/default/files/cisco-packet-tracer-faq.pdf&lt;/A&gt;&lt;BR /&gt;Q14. Does Packet Tracer support all the features found in Cisco devices?&lt;BR /&gt;A. &lt;STRONG&gt;No&lt;/STRONG&gt;. 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.&lt;/P&gt;</description>
      <pubDate>Mon, 19 Apr 2021 10:03:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wlc-management-interface-vlan-tagging/m-p/4389283#M228460</guid>
      <dc:creator>Rich R</dc:creator>
      <dc:date>2021-04-19T10:03:13Z</dc:date>
    </item>
  </channel>
</rss>

