<?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: 2 Different EOIP Tunnels to same Anchor in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/2-different-eoip-tunnels-to-same-anchor/m-p/3825701#M171297</link>
    <description>&lt;P&gt;I would be looking to have QOS in both directions. "In and Out"&lt;/P&gt;</description>
    <pubDate>Mon, 25 Mar 2019 16:21:29 GMT</pubDate>
    <dc:creator>GRANT3779</dc:creator>
    <dc:date>2019-03-25T16:21:29Z</dc:date>
    <item>
      <title>2 Different EOIP Tunnels to same Anchor</title>
      <link>https://community.cisco.com/t5/wireless/2-different-eoip-tunnels-to-same-anchor/m-p/3825583#M171293</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have a foreign controller anchored back to a DMZ WLC. Multiple Guest SSIDs use this EOIP/Anchor.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;QOS on the WAN routers between the Foreign/Anchor WLC is matching on the EOIP tunnel endpoints, using this as the matching criteria for any QOS policy. Obviously this means for QOS (at router level) I cannot be more specific about different subnets etc.. as the router only sees the EOIP source and destination.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is there a way I can build a 2nd separate EOIP tunnel between these 2 controllers using different addresses and then anchor a single specific SSID to this secondary EOIP tunnel. The thinking is that I can the apply a new QOS policy on the WAN routers matching the secondary EOIP tunnel addresses which in turn would apply to the single SSID being anchored back.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I know I can do QOS on the WLC at SSID / AP level but this is not an option in this case.&lt;/P&gt;&lt;P&gt;Does an EOIP tunnel have to be to/from the management address only or can I create a new interface solely for a secondary EOIP tunnel?&lt;/P&gt;&lt;P&gt;Hopefully that makes sense and I a clear on what I am looking to achieve.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Mon, 05 Jul 2021 17:07:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/2-different-eoip-tunnels-to-same-anchor/m-p/3825583#M171293</guid>
      <dc:creator>GRANT3779</dc:creator>
      <dc:date>2021-07-05T17:07:44Z</dc:date>
    </item>
    <item>
      <title>Re: 2 Different EOIP Tunnels to same Anchor</title>
      <link>https://community.cisco.com/t5/wireless/2-different-eoip-tunnels-to-same-anchor/m-p/3825592#M171294</link>
      <description>&lt;P&gt;Yes, Mobility anchor configuration is based on Management IP and the MAC of the WLC.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Better Make the QoS for the client Subnet for out bound traffic&lt;/P&gt;</description>
      <pubDate>Mon, 25 Mar 2019 14:04:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/2-different-eoip-tunnels-to-same-anchor/m-p/3825592#M171294</guid>
      <dc:creator>Sathiyanarayanan Ravindran</dc:creator>
      <dc:date>2019-03-25T14:04:46Z</dc:date>
    </item>
    <item>
      <title>Re: 2 Different EOIP Tunnels to same Anchor</title>
      <link>https://community.cisco.com/t5/wireless/2-different-eoip-tunnels-to-same-anchor/m-p/3825660#M171295</link>
      <description>&lt;P&gt;I can't base the QOS on the client subnet as all the routers see is the EOIP tunnel endpoints (management IPs of each WLC). This is why I am asking the question. Are you meaning apply QOS at WLC level?&lt;/P&gt;</description>
      <pubDate>Mon, 25 Mar 2019 15:35:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/2-different-eoip-tunnels-to-same-anchor/m-p/3825660#M171295</guid>
      <dc:creator>GRANT3779</dc:creator>
      <dc:date>2019-03-25T15:35:18Z</dc:date>
    </item>
    <item>
      <title>Re: 2 Different EOIP Tunnels to same Anchor</title>
      <link>https://community.cisco.com/t5/wireless/2-different-eoip-tunnels-to-same-anchor/m-p/3825694#M171296</link>
      <description>&lt;P&gt;Are you planning to have a QoS btw Foreign and Anchor ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 25 Mar 2019 16:17:35 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/2-different-eoip-tunnels-to-same-anchor/m-p/3825694#M171296</guid>
      <dc:creator>Sathiyanarayanan Ravindran</dc:creator>
      <dc:date>2019-03-25T16:17:35Z</dc:date>
    </item>
    <item>
      <title>Re: 2 Different EOIP Tunnels to same Anchor</title>
      <link>https://community.cisco.com/t5/wireless/2-different-eoip-tunnels-to-same-anchor/m-p/3825701#M171297</link>
      <description>&lt;P&gt;I would be looking to have QOS in both directions. "In and Out"&lt;/P&gt;</description>
      <pubDate>Mon, 25 Mar 2019 16:21:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/2-different-eoip-tunnels-to-same-anchor/m-p/3825701#M171297</guid>
      <dc:creator>GRANT3779</dc:creator>
      <dc:date>2019-03-25T16:21:29Z</dc:date>
    </item>
    <item>
      <title>Re: 2 Different EOIP Tunnels to same Anchor</title>
      <link>https://community.cisco.com/t5/wireless/2-different-eoip-tunnels-to-same-anchor/m-p/3825721#M171298</link>
      <description>&lt;P&gt;Ref the &lt;STRONG&gt;&lt;EM&gt;&lt;A title="QoS on WLC" href="https://www.cisco.com/c/en/us/support/docs/wireless-mobility/wireless-lan-wlan/81831-qos-wlc-lap.html" target="_blank" rel="noopener"&gt;QoS on WLC&lt;/A&gt;&amp;nbsp;&lt;/EM&gt;&lt;/STRONG&gt;for the functionality of QoS on WLC.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I would like to say put QoS for Foreign and Anchor IP traffic and Client Public NAT IP (on internet router). Hope this will help.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 25 Mar 2019 16:45:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/2-different-eoip-tunnels-to-same-anchor/m-p/3825721#M171298</guid>
      <dc:creator>Sathiyanarayanan Ravindran</dc:creator>
      <dc:date>2019-03-25T16:45:05Z</dc:date>
    </item>
    <item>
      <title>Re: 2 Different EOIP Tunnels to same Anchor</title>
      <link>https://community.cisco.com/t5/wireless/2-different-eoip-tunnels-to-same-anchor/m-p/3825945#M171299</link>
      <description>Based off this post, the WLC will maintain markings from the client through to the anchor (if set by client/AP) so that may help you with some control but relies on marking correctly on client upstream.&lt;BR /&gt;&lt;BR /&gt;&lt;A href="https://community.cisco.com/t5/other-wireless-mobility-subjects/qos-markings-for-auto-anchor-eoip/td-p/2987619" target="_blank"&gt;https://community.cisco.com/t5/other-wireless-mobility-subjects/qos-markings-for-auto-anchor-eoip/td-p/2987619&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;For mobility traffic, as Sathiyanarayanan said it will always be the WLCs management address and you can't change this unless you are using multicast mobility between WLCs.&lt;BR /&gt;&lt;BR /&gt;Ric&lt;BR /&gt;</description>
      <pubDate>Tue, 26 Mar 2019 01:21:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/2-different-eoip-tunnels-to-same-anchor/m-p/3825945#M171299</guid>
      <dc:creator>Ric Beeching</dc:creator>
      <dc:date>2019-03-26T01:21:42Z</dc:date>
    </item>
  </channel>
</rss>

