<?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: Monitoring the ISE Deployment in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/monitoring-the-ise-deployment/m-p/3606141#M540546</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If you want the general system health, then add your remote syslog target to "System Statistics".&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As you can see, the events are divided into categories and we may designate a syslog target receiving only a subset of categories. We usually want to keep the default severity and only temporarily set a category to higher for debugging purposes.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 11 Feb 2016 06:32:46 GMT</pubDate>
    <dc:creator>hslai</dc:creator>
    <dc:date>2016-02-11T06:32:46Z</dc:date>
    <item>
      <title>Monitoring the ISE Deployment</title>
      <link>https://community.cisco.com/t5/network-access-control/monitoring-the-ise-deployment/m-p/3606140#M540545</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P style="font-size: 13.3333px;"&gt;Hi,&lt;/P&gt;&lt;P style="font-size: 13.3333px;"&gt;&lt;/P&gt;&lt;P style="font-size: 13.3333px;"&gt;Our customer recently had some problems some PSNs in their ISE 1.3 deployment and didn't realize for quite some time.&lt;/P&gt;&lt;P style="font-size: 13.3333px;"&gt;They are now looking for the best way to monitor their deployment. I have not been able to find a full best practice around monitoring ISE deployments.&lt;/P&gt;&lt;P style="font-size: 13.3333px;"&gt;&lt;/P&gt;&lt;P style="font-size: 13.3333px;"&gt;Info I have found:&lt;/P&gt;&lt;P style="font-size: 13.3333px;"&gt;&lt;A href="http://pmbuwiki/Products/ISE/Technical/Design-Config/Monitoring#Appliance.c2.a0Monitoring" title="http://pmbuwiki/Products/ISE/Technical/Design-Config/Monitoring#Appliance.c2.a0Monitoring"&gt;http://pmbuwiki/Products/ISE/Technical/Design-Config/Monitoring#Appliance.c2.a0Monitoring&lt;/A&gt;&lt;/P&gt;&lt;P style="font-size: 13.3333px;"&gt;which contains:&lt;/P&gt;&lt;P style="font-size: 13.3333px;"&gt;- Syslog setup: How to configure, not what to configure.&lt;/P&gt;&lt;P style="font-size: 13.3333px;"&gt;- SNMP MIBs: Some info on the appliance/VM resources, but nothing on the ISE services availability.&lt;/P&gt;&lt;P style="font-size: 13.3333px;"&gt;- UCS/NAC appliance monitoring: Again looking at the appliance, but not the ISE services.&lt;/P&gt;&lt;P style="font-size: 13.3333px;"&gt;&lt;/P&gt;&lt;P style="font-size: 13.3333px;"&gt;Basically I am looking for an ideal monitoring configuration:&lt;/P&gt;&lt;P style="font-size: 13.3333px;"&gt;We would configure a syslog server as remote logging target, but would to understand which Logging category to enable to send useful information about the status of the ISE deployment to the syslog server.&lt;/P&gt;&lt;P style="font-size: 13.3333px;"&gt;Any recommendations which Logging Categories to enable?&lt;/P&gt;&lt;P style="font-size: 13.3333px;"&gt;&lt;/P&gt;&lt;P style="font-size: 13.3333px;"&gt;Secondly, is there a way to tune the Message Catalog to make sure some logs are sent to the syslog server?&lt;/P&gt;&lt;P style="font-size: 13.3333px;"&gt;Some Messages which are interesting are considered Debug and are therefore not triggered when the general Logging Category is set to Warn or Info.&lt;/P&gt;&lt;P style="font-size: 13.3333px;"&gt;&lt;/P&gt;&lt;P style="font-size: 13.3333px;"&gt;Regards&lt;/P&gt;&lt;P style="font-size: 13.3333px;"&gt;Gert&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 08 Feb 2016 12:54:35 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/monitoring-the-ise-deployment/m-p/3606140#M540545</guid>
      <dc:creator>gtilburg</dc:creator>
      <dc:date>2016-02-08T12:54:35Z</dc:date>
    </item>
    <item>
      <title>Re: Monitoring the ISE Deployment</title>
      <link>https://community.cisco.com/t5/network-access-control/monitoring-the-ise-deployment/m-p/3606141#M540546</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If you want the general system health, then add your remote syslog target to "System Statistics".&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As you can see, the events are divided into categories and we may designate a syslog target receiving only a subset of categories. We usually want to keep the default severity and only temporarily set a category to higher for debugging purposes.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 11 Feb 2016 06:32:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/monitoring-the-ise-deployment/m-p/3606141#M540546</guid>
      <dc:creator>hslai</dc:creator>
      <dc:date>2016-02-11T06:32:46Z</dc:date>
    </item>
  </channel>
</rss>

