<?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 My research indicates this in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/log-collection-error/m-p/2992086#M38003</link>
    <description>&lt;P&gt;My research indicates this message is normally generated by a&lt;BR /&gt;syslog string from a RADIUS authentication that is too long for a write location in the MnT DB when ISE attempts to log it on the MnT. It's purely cosmetic in nature.&lt;/P&gt;
&lt;P&gt;CSCue78265 log Collection error in Mnt-collector.out&lt;/P&gt;
&lt;P&gt;https://bst.cloudapps.cisco.com/bugsearch/bug/CSCue78265/?reffering_site=dumpcr&lt;/P&gt;
&lt;P&gt;Fixed in ISE 2.1.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Regards&lt;/P&gt;
&lt;P&gt;Gagan&lt;/P&gt;
&lt;P&gt;PS : rate if it helps!!!!!&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;</description>
    <pubDate>Mon, 10 Oct 2016 14:35:07 GMT</pubDate>
    <dc:creator>Gagandeep Singh</dc:creator>
    <dc:date>2016-10-10T14:35:07Z</dc:date>
    <item>
      <title>Log collection error</title>
      <link>https://community.cisco.com/t5/network-access-control/log-collection-error/m-p/2992085#M37997</link>
      <description>&lt;P&gt;Hi guys ,&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;I have seen ISE alarm about log collection error . Dou you know this issue , how can we solve it&amp;nbsp;, could you please help&amp;nbsp;&amp;nbsp;?&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;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Details :&lt;/P&gt;
&lt;P&gt;Log collection error : Server=gtisegunpsn5; Log Type=RadiusAuthenticationPassed&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Description :&lt;/P&gt;
&lt;P&gt;The ISE M&amp;amp;T collector process is unable to persist the audit logs generated from the Policy Service nodes&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 07:08:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/log-collection-error/m-p/2992085#M37997</guid>
      <dc:creator>CansuTkr1</dc:creator>
      <dc:date>2019-03-11T07:08:25Z</dc:date>
    </item>
    <item>
      <title>My research indicates this</title>
      <link>https://community.cisco.com/t5/network-access-control/log-collection-error/m-p/2992086#M38003</link>
      <description>&lt;P&gt;My research indicates this message is normally generated by a&lt;BR /&gt;syslog string from a RADIUS authentication that is too long for a write location in the MnT DB when ISE attempts to log it on the MnT. It's purely cosmetic in nature.&lt;/P&gt;
&lt;P&gt;CSCue78265 log Collection error in Mnt-collector.out&lt;/P&gt;
&lt;P&gt;https://bst.cloudapps.cisco.com/bugsearch/bug/CSCue78265/?reffering_site=dumpcr&lt;/P&gt;
&lt;P&gt;Fixed in ISE 2.1.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Regards&lt;/P&gt;
&lt;P&gt;Gagan&lt;/P&gt;
&lt;P&gt;PS : rate if it helps!!!!!&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 10 Oct 2016 14:35:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/log-collection-error/m-p/2992086#M38003</guid>
      <dc:creator>Gagandeep Singh</dc:creator>
      <dc:date>2016-10-10T14:35:07Z</dc:date>
    </item>
    <item>
      <title>Hi gagsing3 , </title>
      <link>https://community.cisco.com/t5/network-access-control/log-collection-error/m-p/2992087#M38006</link>
      <description>&lt;P&gt;Hi gagsing3 ,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Many thanks for respone &amp;nbsp;, it can be effect our enviroment . Our version is ISE 1.4 ,&amp;nbsp;may be the issue isn't yet&amp;nbsp;seen in this version .&lt;/P&gt;</description>
      <pubDate>Mon, 10 Oct 2016 14:56:34 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/log-collection-error/m-p/2992087#M38006</guid>
      <dc:creator>CansuTkr1</dc:creator>
      <dc:date>2016-10-10T14:56:34Z</dc:date>
    </item>
    <item>
      <title>You can try refresh the M&amp;T</title>
      <link>https://community.cisco.com/t5/network-access-control/log-collection-error/m-p/2992088#M38014</link>
      <description>&lt;P&gt;You can try refresh the M&amp;amp;T database using "application configure ISE" command and choose option for Refresh M&amp;amp;T database.&lt;/P&gt;
&lt;P&gt;As per my understanding, it should not affect the n/w. Did you face any authentication failure.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I would also suggest to upgrade to 2.1 our latest release with enhanced features.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Regards&lt;/P&gt;
&lt;P&gt;Gagan.&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;PS : rate if it helps!!!!!&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 10 Oct 2016 15:02:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/log-collection-error/m-p/2992088#M38014</guid>
      <dc:creator>Gagandeep Singh</dc:creator>
      <dc:date>2016-10-10T15:02:47Z</dc:date>
    </item>
    <item>
      <title>Re: You can try refresh the M&amp;T</title>
      <link>https://community.cisco.com/t5/network-access-control/log-collection-error/m-p/4060621#M559452</link>
      <description>we have this every day randomly across 3 PSNs on 2.2.0.470 p16</description>
      <pubDate>Tue, 07 Apr 2020 07:07:12 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/log-collection-error/m-p/4060621#M559452</guid>
      <dc:creator>Andrii Oliinyk</dc:creator>
      <dc:date>2020-04-07T07:07:12Z</dc:date>
    </item>
  </channel>
</rss>

