<?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 ISE and Logging Categories Per-instance in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/cisco-ise-and-logging-categories-per-instance/m-p/3922603#M457170</link>
    <description>&lt;P&gt;At the moment all PSN node send logs to primary and secondary MNT node and if you have configured any syslog server then PSNs will send to that particular syslog server.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If you need one location PSN should send log to a syslog and another location PSN to send logs to another syslog server then this would be a new feature request in ISE.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I would suggest to open a TAC case and get a feature request raised for this.&lt;/P&gt;</description>
    <pubDate>Wed, 11 Sep 2019 15:27:14 GMT</pubDate>
    <dc:creator>pan</dc:creator>
    <dc:date>2019-09-11T15:27:14Z</dc:date>
    <item>
      <title>Cisco ISE and Logging Categories Per-instance</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-and-logging-categories-per-instance/m-p/3922555#M457169</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;with ACS it was possible to configure different syslog collectors per ACS node in a distributed environment. It makes sense if we have different ACS nodes distributed around the world and we want to configure it based on location.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We are migrating the current configuration to Cisco ISE and we've found out that we only have the "Global Option".&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any idea/suggestion about how to configure it with ISE?&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you,&lt;/P&gt;&lt;P&gt;Pepe&lt;/P&gt;</description>
      <pubDate>Wed, 11 Sep 2019 14:35:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-and-logging-categories-per-instance/m-p/3922555#M457169</guid>
      <dc:creator>pepebravo</dc:creator>
      <dc:date>2019-09-11T14:35:15Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ISE and Logging Categories Per-instance</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-and-logging-categories-per-instance/m-p/3922603#M457170</link>
      <description>&lt;P&gt;At the moment all PSN node send logs to primary and secondary MNT node and if you have configured any syslog server then PSNs will send to that particular syslog server.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If you need one location PSN should send log to a syslog and another location PSN to send logs to another syslog server then this would be a new feature request in ISE.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I would suggest to open a TAC case and get a feature request raised for this.&lt;/P&gt;</description>
      <pubDate>Wed, 11 Sep 2019 15:27:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-and-logging-categories-per-instance/m-p/3922603#M457170</guid>
      <dc:creator>pan</dc:creator>
      <dc:date>2019-09-11T15:27:14Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ISE and Logging Categories Per-instance</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-and-logging-categories-per-instance/m-p/3922610#M457232</link>
      <description>You can also send syslog to a syslog proxy of sorts&lt;BR /&gt;</description>
      <pubDate>Wed, 11 Sep 2019 15:34:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-and-logging-categories-per-instance/m-p/3922610#M457232</guid>
      <dc:creator>Jason Kunst</dc:creator>
      <dc:date>2019-09-11T15:34:59Z</dc:date>
    </item>
  </channel>
</rss>

