<?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: Cisco WLC integration problem with PA. in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/cisco-wlc-integration-problem-with-pa/m-p/288352#M76825</link>
    <description>&lt;DIV class="lia-message-body lia-component-message-view-widget-body lia-component-body-signature-highlight-escalation lia-component-message-view-widget-body-signature-highlight-escalation"&gt;&lt;DIV class="lia-message-body-content"&gt;&lt;P&gt;In the meantime you can avoid the use of a third party server and can directly send syslog events to your firewall.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The following command on WLC is everything you need:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;PRE&gt;logging syslog facility client associate enable&lt;/PRE&gt;&lt;P&gt;After that configure Palo Alto firewall as syslog server on WLC.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;On Palo Alto firewall you should create a Syslog Parse Profile with the following entries:&lt;/P&gt;&lt;P&gt;&lt;SPAN class="lia-inline-image-display-wrapper lia-image-align-inline"&gt;&lt;SPAN class="lia-message-image-wrapper lia-message-image-actions-narrow lia-message-image-actions-below"&gt;&lt;IMG src="https://ip1.i.lithium.com/1f504ddcdfe1479dfd0ea0577311e2f178806a3b/68747470733a2f2f6b7869777136373733372e692e6c69746869756d2e636f6d2f74352f696d6167652f736572766572706167652f696d6167652d69642f343439303769433935344332463338393437384330412f696d6167652d73697a652f6c617267653f763d312e302670783d393939" alt="Palo_Alto_Parse.png" title="Palo_Alto_Parse.png" border="0" /&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Basically that's everything you need to get it running.&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;</description>
    <pubDate>Fri, 13 Sep 2019 12:22:48 GMT</pubDate>
    <dc:creator>Tobi</dc:creator>
    <dc:date>2019-09-13T12:22:48Z</dc:date>
    <item>
      <title>Cisco WLC integration problem with PA.</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/cisco-wlc-integration-problem-with-pa/m-p/128089#M46637</link>
      <description>&lt;P&gt;I have Cisco WLC 5508 , kiwi syslogd and PA.I can see snmp traps in Syslogd but only username is visible , ip address of the client is missing.Can anybody help how to parse it in Palo alto Firewall.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;</description>
      <pubDate>Tue, 22 Nov 2016 10:45:03 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/cisco-wlc-integration-problem-with-pa/m-p/128089#M46637</guid>
      <dc:creator>Networker2b</dc:creator>
      <dc:date>2016-11-22T10:45:03Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco WLC integration problem with PA.</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/cisco-wlc-integration-problem-with-pa/m-p/288352#M76825</link>
      <description>&lt;DIV class="lia-message-body lia-component-message-view-widget-body lia-component-body-signature-highlight-escalation lia-component-message-view-widget-body-signature-highlight-escalation"&gt;&lt;DIV class="lia-message-body-content"&gt;&lt;P&gt;In the meantime you can avoid the use of a third party server and can directly send syslog events to your firewall.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The following command on WLC is everything you need:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;PRE&gt;logging syslog facility client associate enable&lt;/PRE&gt;&lt;P&gt;After that configure Palo Alto firewall as syslog server on WLC.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;On Palo Alto firewall you should create a Syslog Parse Profile with the following entries:&lt;/P&gt;&lt;P&gt;&lt;SPAN class="lia-inline-image-display-wrapper lia-image-align-inline"&gt;&lt;SPAN class="lia-message-image-wrapper lia-message-image-actions-narrow lia-message-image-actions-below"&gt;&lt;IMG src="https://ip1.i.lithium.com/1f504ddcdfe1479dfd0ea0577311e2f178806a3b/68747470733a2f2f6b7869777136373733372e692e6c69746869756d2e636f6d2f74352f696d6167652f736572766572706167652f696d6167652d69642f343439303769433935344332463338393437384330412f696d6167652d73697a652f6c617267653f763d312e302670783d393939" alt="Palo_Alto_Parse.png" title="Palo_Alto_Parse.png" border="0" /&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Basically that's everything you need to get it running.&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;</description>
      <pubDate>Fri, 13 Sep 2019 12:22:48 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/cisco-wlc-integration-problem-with-pa/m-p/288352#M76825</guid>
      <dc:creator>Tobi</dc:creator>
      <dc:date>2019-09-13T12:22:48Z</dc:date>
    </item>
  </channel>
</rss>

