<?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 Palo Altp - Cisco WLC Anchor - Foriegn in Integration Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/integration-discussions/palo-altp-cisco-wlc-anchor-foriegn/m-p/255899#M28</link>
    <description>&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Created a new zone on PA ether1/5 configured all interfaces.&amp;nbsp; Installed a Cisco 5520 WLC as and Anchor WLC and setup piolices to allow the Capwap tunnnel to the Foreign WLC.&lt;/P&gt;&lt;P&gt;This was a 1 legged approach, WLC in LAG&lt;/P&gt;&lt;P&gt;This worked, tunnel is up and stayed up.&amp;nbsp; The client traffic breaks out to a layer 2 connection to a 3rd party managed guest solution.&lt;/P&gt;&lt;P&gt;All devices can connected and get a IP from range in DMZ.&lt;/P&gt;&lt;P&gt;Windows devices get the splash page for auuthtication from the 3rd party, apple and android seem to time out, ssl connectin keep being dropped.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I removed LAG from the WLC and turned connected 1 port to be the management on to our dist, the client side still all correct, but now when a Apple and Android device connects, it works as should do.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is there something on the Palo that is causing this to time out?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;When the WLC was on the 1/5 port of Pal, Cisco Prime had trouble to see it, even though I was allowing all services and application to connect,&amp;nbsp; but as soon as removed from PA, Prime and the WLC could talk&amp;nbsp; with no problems.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;To me, the Cisco side no issues, but something on the Pall affecting it.&lt;/P&gt;</description>
    <pubDate>Wed, 03 Apr 2019 14:18:15 GMT</pubDate>
    <dc:creator>Scooby</dc:creator>
    <dc:date>2019-04-03T14:18:15Z</dc:date>
    <item>
      <title>Palo Altp - Cisco WLC Anchor - Foriegn</title>
      <link>https://live.paloaltonetworks.com/t5/integration-discussions/palo-altp-cisco-wlc-anchor-foriegn/m-p/255899#M28</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Created a new zone on PA ether1/5 configured all interfaces.&amp;nbsp; Installed a Cisco 5520 WLC as and Anchor WLC and setup piolices to allow the Capwap tunnnel to the Foreign WLC.&lt;/P&gt;&lt;P&gt;This was a 1 legged approach, WLC in LAG&lt;/P&gt;&lt;P&gt;This worked, tunnel is up and stayed up.&amp;nbsp; The client traffic breaks out to a layer 2 connection to a 3rd party managed guest solution.&lt;/P&gt;&lt;P&gt;All devices can connected and get a IP from range in DMZ.&lt;/P&gt;&lt;P&gt;Windows devices get the splash page for auuthtication from the 3rd party, apple and android seem to time out, ssl connectin keep being dropped.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I removed LAG from the WLC and turned connected 1 port to be the management on to our dist, the client side still all correct, but now when a Apple and Android device connects, it works as should do.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is there something on the Palo that is causing this to time out?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;When the WLC was on the 1/5 port of Pal, Cisco Prime had trouble to see it, even though I was allowing all services and application to connect,&amp;nbsp; but as soon as removed from PA, Prime and the WLC could talk&amp;nbsp; with no problems.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;To me, the Cisco side no issues, but something on the Pall affecting it.&lt;/P&gt;</description>
      <pubDate>Wed, 03 Apr 2019 14:18:15 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/integration-discussions/palo-altp-cisco-wlc-anchor-foriegn/m-p/255899#M28</guid>
      <dc:creator>Scooby</dc:creator>
      <dc:date>2019-04-03T14:18:15Z</dc:date>
    </item>
    <item>
      <title>Re: Palo Altp - Cisco WLC Anchor - Foriegn</title>
      <link>https://live.paloaltonetworks.com/t5/integration-discussions/palo-altp-cisco-wlc-anchor-foriegn/m-p/256006#M31</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I do not know enough about WLC CAPWAP connections to even begin to assist with debugging this. More than likely, you would have to take packet captures to see what is going on at layers 2 and 3 to debug this issue.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;This type of question really needs to be worked through a support case. Have you opened a case with Palo Alto Networks Tech Support?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Please visit &lt;A href="https://support.paloaltonetworks.com" target="_blank"&gt;https://support.paloaltonetworks.com&lt;/A&gt; or call:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;US: 866 898 9087; Int'l: +1 408 738 7799&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;EMEA&amp;nbsp;&lt;EM&gt;Support&lt;/EM&gt;: +31 20 808 4600&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;APAC&amp;nbsp;&lt;EM&gt;Support&lt;/EM&gt;: +65 3158 5600&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Thank you,&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;-JeffH&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Jeff Hochberg | Sr. Systems Engineer - Technical Business Development&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;Palo Alto Networks&amp;nbsp;|&amp;nbsp;Atlanta, GA&amp;nbsp;|&amp;nbsp;&amp;nbsp;USA&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Mobile:&lt;/STRONG&gt;&amp;nbsp;404.432.1112&amp;nbsp;|&amp;nbsp;&lt;U&gt;www.&lt;/U&gt;&lt;U&gt;&lt;A href="https://www.paloaltonetworks.com/" target="_blank" rel="nofollow noopener noreferrer"&gt;paloaltonetworks.com&lt;/A&gt;&lt;/U&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;FONT size="1 2 3 4 5 6 7"&gt;&lt;EM&gt;The content of this message is the proprietary and confidential property of Palo Alto Networks and should be treated as such. If you are not the intended recipient and have received this message in error, please delete this message from your computer system and notify me immediately by reply e-mail. Any unauthorized use or distribution of the content of this message is prohibited.&lt;/EM&gt;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Please let me know if you run into any issues with opening a support case.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;-JeffH&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 03 Apr 2019 22:25:40 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/integration-discussions/palo-altp-cisco-wlc-anchor-foriegn/m-p/256006#M31</guid>
      <dc:creator>jhochberg</dc:creator>
      <dc:date>2019-04-03T22:25:40Z</dc:date>
    </item>
  </channel>
</rss>

