<?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 tacacs accounting problem in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/tacacs-accounting-problem/m-p/1269358#M348672</link>
    <description>&lt;P&gt;I have 7206 with 12.2 SB as a broadband PPPoE aggregator. 7206 uses tac_plus server to authenticate user PPPoE sessions. The problem is tac_plus does not log stop records. After some research I find out that router can not send accounting records which size exceeds 576 byte. Does anynoe know how to fix such problem?&lt;/P&gt;</description>
    <pubDate>Sun, 10 Mar 2019 23:38:08 GMT</pubDate>
    <dc:creator>rish01</dc:creator>
    <dc:date>2019-03-10T23:38:08Z</dc:date>
    <item>
      <title>tacacs accounting problem</title>
      <link>https://community.cisco.com/t5/network-access-control/tacacs-accounting-problem/m-p/1269358#M348672</link>
      <description>&lt;P&gt;I have 7206 with 12.2 SB as a broadband PPPoE aggregator. 7206 uses tac_plus server to authenticate user PPPoE sessions. The problem is tac_plus does not log stop records. After some research I find out that router can not send accounting records which size exceeds 576 byte. Does anynoe know how to fix such problem?&lt;/P&gt;</description>
      <pubDate>Sun, 10 Mar 2019 23:38:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/tacacs-accounting-problem/m-p/1269358#M348672</guid>
      <dc:creator>rish01</dc:creator>
      <dc:date>2019-03-10T23:38:08Z</dc:date>
    </item>
    <item>
      <title>Re: tacacs accounting problem</title>
      <link>https://community.cisco.com/t5/network-access-control/tacacs-accounting-problem/m-p/1269359#M348701</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;For minimal accounting, use the stop-only keyword, which instructs the specified method (RADIUS or TACACS+) to send a stop record accounting notice at the end of the requested user process. For more accounting information, use the start-stop keyword to send a start accounting notice at the beginning of the requested event and a stop accounting notice at the end of the event. To stop all accounting activities on this line or interface, use the none keyword.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/en/US/docs/ios/security/configuration/guide/sec_cfg_accountg.html#wp1017255" target="_blank"&gt;http://www.cisco.com/en/US/docs/ios/security/configuration/guide/sec_cfg_accountg.html#wp1017255&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 13 Aug 2009 16:16:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/tacacs-accounting-problem/m-p/1269359#M348701</guid>
      <dc:creator>gmarogi</dc:creator>
      <dc:date>2009-08-13T16:16:11Z</dc:date>
    </item>
  </channel>
</rss>

