<?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: ISE 1.3 and sending alarms as syslog messages in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-1-3-and-sending-alarms-as-syslog-messages/m-p/3456204#M536422</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I could not find an ISE 1.3 instance, but here is a screenshot from ISE 1.4.1, that shows [ Include Alarms for this Target ] checkbox option in a remote logging target:&lt;/P&gt;&lt;P&gt;&lt;IMG alt="Screen Shot 2017-01-19 at 8.44.04 PM.png" class="image-1 jive-image" src="/legacyfs/online/fusion/103780_Screen Shot 2017-01-19 at 8.44.04 PM.png" style="height: 213px; width: 620px;" /&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 20 Jan 2017 05:18:39 GMT</pubDate>
    <dc:creator>hslai</dc:creator>
    <dc:date>2017-01-20T05:18:39Z</dc:date>
    <item>
      <title>ISE 1.3 and sending alarms as syslog messages</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-1-3-and-sending-alarms-as-syslog-messages/m-p/3456202#M536420</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello, I am running ISE 1.3 Patch 7. I have an application that can consume and search syslog messages and I have ISE configured with this application as a syslog target. That works fine for authentication logs, but none of our Alarms are being sent. I found the snippet below in the 1.3 admin guide but &lt;SPAN style="font-size: 13.3333px;"&gt;I am completely confused on what this means. This is the key statement:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 13.3333px;"&gt;&lt;SPAN style="font-size: 14pt;"&gt;&amp;gt; &lt;/SPAN&gt;&lt;SPAN style="font-size: 14pt;"&gt;If you configure monitoring functions to send alarm notifications as syslog messages&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;How exactly do I configure alarm notifications to be sent as syslog messages? The only option I have in &lt;STRONG&gt;System &amp;gt; Settings &amp;gt; Alarm Settings &amp;gt; Alarm Notification&lt;/STRONG&gt; is email, and I can't seem to find the relevant instructions in the guide.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;H2 class="topictitle2" style="margin-top: 20px; margin-bottom: 8px; font-size: 2.4rem; font-family: arial, helvetica, 'Helvetica Neue', HelveticaNeue, 'Lucida Grande', sans-serif; color: #39393b;"&gt;Log Collection&lt;/H2&gt;&lt;P style="font-style: inherit; font-weight: inherit; font-size: inherit; font-family: inherit;"&gt;&lt;A name="concept_E5A0468CB2E141788F61B976ABEBF59C__ID403" style="font-style: inherit; font-weight: inherit; font-size: inherit; font-family: inherit; color: #0075b4;"&gt;&lt;/A&gt;Monitoring services collect log and configuration data, store the data, and then process it to generate reports and alarms. You can view the details of the logs that are collected from any of the servers in your deployment.&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;A href="http://www.cisco.com/c/en/us/td/docs/security/ise/2-0/admin_guide/b_ise_admin_guide_20/b_ise_admin_guide_20_chapter_011000.html#reference_97E6EBC50DCD4FB8B9AB65CC2C24045E" style="font-style: inherit; font-weight: inherit; font-size: inherit; font-family: inherit; color: #6f53bc;"&gt;Alarm Syslog Collection Location&lt;/A&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;A name="reference_97E6EBC50DCD4FB8B9AB65CC2C24045E" style="font-style: inherit; font-weight: inherit; font-size: inherit; font-family: inherit; color: #0075b4;"&gt;&lt;/A&gt;&lt;/P&gt;&lt;H3 class="topictitle3" style="margin-top: 20px; margin-bottom: 8px; font-style: inherit; font-size: 2.1rem; font-family: inherit; color: #39393b;"&gt;Alarm Syslog Collection Location&lt;/H3&gt;&lt;P&gt;&lt;A name="reference_97E6EBC50DCD4FB8B9AB65CC2C24045E__section_AE6DEB1E5363409EBC027F0F32FB7CC1" style="font-style: inherit; font-weight: inherit; font-size: inherit; font-family: inherit; color: #0075b4;"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P style="margin-top: 12px; margin-bottom: 12px; font-style: inherit; font-weight: inherit; font-size: inherit; font-family: inherit;"&gt;&lt;A name="reference_97E6EBC50DCD4FB8B9AB65CC2C24045E__ID409" style="font-style: inherit; font-weight: inherit; font-size: inherit; font-family: inherit; color: #0075b4;"&gt;&lt;/A&gt;If you configure monitoring functions to send alarm notifications as syslog messages, you need a syslog target to receive the notification. Alarm syslog targets are the destinations where alarm syslog messages are sent.&lt;/P&gt;&lt;P style="margin-top: 12px; margin-bottom: 12px; font-style: inherit; font-weight: inherit; font-size: inherit; font-family: inherit;"&gt;&lt;A name="reference_97E6EBC50DCD4FB8B9AB65CC2C24045E__ID410" style="font-style: inherit; font-weight: inherit; font-size: inherit; font-family: inherit; color: #0075b4;"&gt;&lt;/A&gt;You must also have a system that is configured as a syslog server to be able to receive syslog messages. You can create, edit, and delete alarm syslog targets.&lt;/P&gt;&lt;TABLE class="olh_note" style="margin: 6px 0; border: 0px; font-style: inherit; font-weight: inherit; font-size: inherit; font-family: inherit;"&gt;&lt;TBODY style="font-style: inherit; font-weight: inherit; font-size: inherit; font-family: inherit;"&gt;&lt;TR style="border: 0px; font-style: inherit; font-weight: inherit; font-size: inherit; font-family: inherit;"&gt;&lt;TD class="olh_note" style="padding: 0 5px; border: 0px; font-style: inherit; font-size: inherit; font-family: inherit;"&gt;&lt;IMG class="jive-image" src="http://www.cisco.com/c/dam/en/us/td/i/templates/note.gif" style="font-style: inherit; font-weight: inherit; font-size: inherit; font-family: inherit;" /&gt;&lt;STRONG style="font-style: inherit; font-size: inherit; font-family: inherit;"&gt;Note&lt;/STRONG&gt;&lt;/TD&gt;&lt;TD class="olh_note" style="padding: 0 5px; border: 0px; font-style: inherit; font-size: inherit; font-family: inherit;"&gt;&lt;HR /&gt;&lt;P style="margin-top: 6px; margin-bottom: 6px; font-style: inherit; font-weight: inherit; font-size: inherit; font-family: inherit;"&gt;&lt;A name="reference_97E6EBC50DCD4FB8B9AB65CC2C24045E__ID412" style="font-style: inherit; font-weight: inherit; font-size: inherit; font-family: inherit; color: #0075b4;"&gt;&lt;/A&gt;Cisco ISE monitoring requires that the logging-source interface configuration use the network access server (NAS) IP address. You must configure a switch for Cisco ISE monitoring.&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;H3 class="topictitle3" style="margin-top: 20px; margin-bottom: 8px; font-size: 2.1rem; font-family: arial, helvetica, 'Helvetica Neue', HelveticaNeue, 'Lucida Grande', sans-serif; color: #39393b;"&gt;&lt;/H3&gt;&lt;P&gt;&lt;BR /&gt; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 19 Jan 2017 20:28:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-1-3-and-sending-alarms-as-syslog-messages/m-p/3456202#M536420</guid>
      <dc:creator>smp</dc:creator>
      <dc:date>2017-01-19T20:28:24Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 1.3 and sending alarms as syslog messages</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-1-3-and-sending-alarms-as-syslog-messages/m-p/3456203#M536421</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Feature available in ISE 2.1...&lt;/P&gt;&lt;P&gt;&lt;IMG alt="" class="image-1 jive-image" src="https://community.cisco.com/legacyfs/online/fusion/103779_pastedImage_2.png" style="max-width: 1200px; max-height: 900px;" /&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 20 Jan 2017 00:08:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-1-3-and-sending-alarms-as-syslog-messages/m-p/3456203#M536421</guid>
      <dc:creator>Craig Hyps</dc:creator>
      <dc:date>2017-01-20T00:08:06Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 1.3 and sending alarms as syslog messages</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-1-3-and-sending-alarms-as-syslog-messages/m-p/3456204#M536422</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I could not find an ISE 1.3 instance, but here is a screenshot from ISE 1.4.1, that shows [ Include Alarms for this Target ] checkbox option in a remote logging target:&lt;/P&gt;&lt;P&gt;&lt;IMG alt="Screen Shot 2017-01-19 at 8.44.04 PM.png" class="image-1 jive-image" src="/legacyfs/online/fusion/103780_Screen Shot 2017-01-19 at 8.44.04 PM.png" style="height: 213px; width: 620px;" /&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 20 Jan 2017 05:18:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-1-3-and-sending-alarms-as-syslog-messages/m-p/3456204#M536422</guid>
      <dc:creator>hslai</dc:creator>
      <dc:date>2017-01-20T05:18:39Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 1.3 and sending alarms as syslog messages</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-1-3-and-sending-alarms-as-syslog-messages/m-p/3456205#M536423</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;YES, that was it! Thank you so much!!!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 20 Jan 2017 13:17:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-1-3-and-sending-alarms-as-syslog-messages/m-p/3456205#M536423</guid>
      <dc:creator>smp</dc:creator>
      <dc:date>2017-01-20T13:17:17Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 1.3 and sending alarms as syslog messages</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-1-3-and-sending-alarms-as-syslog-messages/m-p/3456206#M536424</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Now get off 1.3 &lt;IMG src="https://community.cisco.com/legacyfs/online/emoticons/happy.png" /&gt;&amp;nbsp; this release is old &lt;/P&gt;&lt;P&gt;1.4.1 is a controlled release&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;deployment should be moved to 2.1 which has been out and stable&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 20 Jan 2017 14:42:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-1-3-and-sending-alarms-as-syslog-messages/m-p/3456206#M536424</guid>
      <dc:creator>Jason Kunst</dc:creator>
      <dc:date>2017-01-20T14:42:03Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 1.3 and sending alarms as syslog messages</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-1-3-and-sending-alarms-as-syslog-messages/m-p/3456207#M536425</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Combining information based on sidebar discussions with Hsing...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Alarms are automatically sent to default system Log targets.&amp;nbsp; If wish to send Alarms in syslog to new external targets, then select option from screenshot that Hsing provided.&amp;nbsp; When add a new target, there is checkbox to optionally include alarms.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Starting in ISE 2.1, you can also selectively choose which alarms are sent as Syslog.&amp;nbsp; System (predefined) alarms are automatically enabled for syslog, but new (custom) alarms are not enabled for syslog by default.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;/Craig&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 20 Jan 2017 17:40:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-1-3-and-sending-alarms-as-syslog-messages/m-p/3456207#M536425</guid>
      <dc:creator>Craig Hyps</dc:creator>
      <dc:date>2017-01-20T17:40:36Z</dc:date>
    </item>
  </channel>
</rss>

