<?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: Management Vlan best practices in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/management-vlan-best-practices/m-p/5519587#M307625</link>
    <description>&lt;P&gt;Hi &lt;A href="https://community.meraki.com/t5/user/viewprofilepage/user-id/23222"&gt;@SAM-Al&lt;/A&gt;&lt;/P&gt;&lt;P&gt;It is recommended to have a dedicated VLAN for management traffic, although not always required, per our KB article for &lt;A href="https://documentation.meraki.com/MR/Monitoring_and_Reporting/Understanding_and_Configuring_Management_VLANs_on_Cisco_Meraki_Devices" target="_self" rel="nofollow noopener noreferrer"&gt;Understanding and Configuring Management VLANs&lt;/A&gt;.&lt;/P&gt;&lt;P&gt;In your case, I would recommend configuring your aggregation switches' management interfaces in the transit VLAN (so that they can still function if anything happens downstream), and then creating a management VLAN on the aggregation switches for the remaining downstream equipment (access switches, APs, etc).&lt;/P&gt;&lt;P&gt;As long as routing is configuring properly, you shouldn't have an issue with on-premise or cloud based RADIUS server.&lt;/P&gt;&lt;P&gt;Cheers,&lt;/P&gt;&lt;P&gt;-Alex&lt;/P&gt;</description>
    <pubDate>Wed, 19 Jun 2019 15:44:00 GMT</pubDate>
    <dc:creator>thachung</dc:creator>
    <dc:date>2019-06-19T15:44:00Z</dc:date>
    <item>
      <title>Management Vlan best practices</title>
      <link>https://community.cisco.com/t5/wireless/management-vlan-best-practices/m-p/5519586#M307624</link>
      <description>&lt;P&gt;Hi guys,&lt;/P&gt;&lt;P&gt;Would you please advise about Meraki best practice for the management vlan? &lt;/P&gt;&lt;P&gt;In  my test network I have pair of MXs followed by pair of aggregation switches which feed couple of access switches and WAPs...&lt;/P&gt;&lt;P&gt;All my vlans are configured in the aggregation switches where the intervlan routing happens....the current management vlan for the WAPs and the switches is Vlan 1 which  is same as the MX gateway that facing the aggregation switches.&lt;/P&gt;&lt;P&gt;Any idea about the best practice that I should follow?&lt;/P&gt;&lt;P&gt;I know above can cause issue for especially I'm planning to use RADIUS server one will sit in house and back up one in Azure.&lt;/P&gt;&lt;P&gt;Please let me know&lt;/P&gt;&lt;P&gt;Thanks &lt;/P&gt;</description>
      <pubDate>Tue, 18 Jun 2019 09:48:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/management-vlan-best-practices/m-p/5519586#M307624</guid>
      <dc:creator>SAM-Al</dc:creator>
      <dc:date>2019-06-18T09:48:18Z</dc:date>
    </item>
    <item>
      <title>Re: Management Vlan best practices</title>
      <link>https://community.cisco.com/t5/wireless/management-vlan-best-practices/m-p/5519587#M307625</link>
      <description>&lt;P&gt;Hi &lt;A href="https://community.meraki.com/t5/user/viewprofilepage/user-id/23222"&gt;@SAM-Al&lt;/A&gt;&lt;/P&gt;&lt;P&gt;It is recommended to have a dedicated VLAN for management traffic, although not always required, per our KB article for &lt;A href="https://documentation.meraki.com/MR/Monitoring_and_Reporting/Understanding_and_Configuring_Management_VLANs_on_Cisco_Meraki_Devices" target="_self" rel="nofollow noopener noreferrer"&gt;Understanding and Configuring Management VLANs&lt;/A&gt;.&lt;/P&gt;&lt;P&gt;In your case, I would recommend configuring your aggregation switches' management interfaces in the transit VLAN (so that they can still function if anything happens downstream), and then creating a management VLAN on the aggregation switches for the remaining downstream equipment (access switches, APs, etc).&lt;/P&gt;&lt;P&gt;As long as routing is configuring properly, you shouldn't have an issue with on-premise or cloud based RADIUS server.&lt;/P&gt;&lt;P&gt;Cheers,&lt;/P&gt;&lt;P&gt;-Alex&lt;/P&gt;</description>
      <pubDate>Wed, 19 Jun 2019 15:44:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/management-vlan-best-practices/m-p/5519587#M307625</guid>
      <dc:creator>thachung</dc:creator>
      <dc:date>2019-06-19T15:44:00Z</dc:date>
    </item>
  </channel>
</rss>

