<?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 Monitoring ISE node as syslog destination in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/monitoring-ise-node-as-syslog-destination/m-p/1971634#M186946</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks Tarik.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So you mean that even if we don't configure monitoring ISE node IP as syslog destination on access switches, even then ISE gives details of user authentication.&lt;/P&gt;&lt;P&gt;Configuring the IP gives us additional details, right?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Kashish&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 18 Jul 2012 04:00:46 GMT</pubDate>
    <dc:creator>Kashish_Patel</dc:creator>
    <dc:date>2012-07-18T04:00:46Z</dc:date>
    <item>
      <title>Monitoring ISE node as syslog destination</title>
      <link>https://community.cisco.com/t5/network-access-control/monitoring-ise-node-as-syslog-destination/m-p/1971632#M186855</link>
      <description>&lt;P&gt;Hi Security Experts,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We are setting up Cisco ISE (Identity Services Engine) in our network. &lt;/P&gt;&lt;P&gt;I have the confusion if we need to configure monitoring node IP address as the syslog destination on the access switches. In what situations is this needed and in which situations is it not needed?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;PS: I rate useful posts.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Kashish&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 02:18:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/monitoring-ise-node-as-syslog-destination/m-p/1971632#M186855</guid>
      <dc:creator>Kashish_Patel</dc:creator>
      <dc:date>2019-03-11T02:18:54Z</dc:date>
    </item>
    <item>
      <title>Monitoring ISE node as syslog destination</title>
      <link>https://community.cisco.com/t5/network-access-control/monitoring-ise-node-as-syslog-destination/m-p/1971633#M186912</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Kashish,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When you look at the user authentication report, ISE also builds related syslog messages that pertain to the user connection.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This isnt mandatory but useful since it does help correlate syslog messages to the user authentication session. Here is an example of it in action:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="http://www.cisco.com/en/US/docs/security/ise/1.0/user_guide/ise10_troubleshooting.html#wp1050132"&gt;http://www.cisco.com/en/US/docs/security/ise/1.0/user_guide/ise10_troubleshooting.html#wp1050132&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Tarik Admani &lt;BR /&gt;*Please rate helpful posts*&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 18 Jul 2012 03:37:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/monitoring-ise-node-as-syslog-destination/m-p/1971633#M186912</guid>
      <dc:creator>Tarik Admani</dc:creator>
      <dc:date>2012-07-18T03:37:55Z</dc:date>
    </item>
    <item>
      <title>Monitoring ISE node as syslog destination</title>
      <link>https://community.cisco.com/t5/network-access-control/monitoring-ise-node-as-syslog-destination/m-p/1971634#M186946</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks Tarik.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So you mean that even if we don't configure monitoring ISE node IP as syslog destination on access switches, even then ISE gives details of user authentication.&lt;/P&gt;&lt;P&gt;Configuring the IP gives us additional details, right?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Kashish&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 18 Jul 2012 04:00:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/monitoring-ise-node-as-syslog-destination/m-p/1971634#M186946</guid>
      <dc:creator>Kashish_Patel</dc:creator>
      <dc:date>2012-07-18T04:00:46Z</dc:date>
    </item>
    <item>
      <title>Monitoring ISE node as syslog destination</title>
      <link>https://community.cisco.com/t5/network-access-control/monitoring-ise-node-as-syslog-destination/m-p/1971635#M186972</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Exactly, ISE will attached the relevant syslog data (if you have it configured) to the report. The radius authentication will still appear no matter what.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Tarik Admani &lt;BR /&gt;*Please rate helpful posts*&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 18 Jul 2012 04:22:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/monitoring-ise-node-as-syslog-destination/m-p/1971635#M186972</guid>
      <dc:creator>Tarik Admani</dc:creator>
      <dc:date>2012-07-18T04:22:18Z</dc:date>
    </item>
    <item>
      <title>Monitoring ISE node as syslog destination</title>
      <link>https://community.cisco.com/t5/network-access-control/monitoring-ise-node-as-syslog-destination/m-p/1971636#M187006</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks Tarik. That answers my question.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 18 Jul 2012 04:35:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/monitoring-ise-node-as-syslog-destination/m-p/1971636#M187006</guid>
      <dc:creator>Kashish_Patel</dc:creator>
      <dc:date>2012-07-18T04:35:54Z</dc:date>
    </item>
  </channel>
</rss>

