<?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: CLI history to syslog in ExtremeSwitching (Other)</title>
    <link>https://community.extremenetworks.com/t5/extremeswitching-other/cli-history-to-syslog/m-p/11012#M2040</link>
    <description>That's an EXOS command &lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt;&lt;BR /&gt;
Let me see what I can find out for you, Curt.&lt;BR /&gt;</description>
    <pubDate>Fri, 05 Dec 2014 21:57:00 GMT</pubDate>
    <dc:creator>Drew_C</dc:creator>
    <dc:date>2014-12-05T21:57:00Z</dc:date>
    <item>
      <title>CLI history to syslog</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-other/cli-history-to-syslog/m-p/11009#M2037</link>
      <description>For auditing purposes we need to track the commands entered on our enterasys switches and routers.   Is there an easy way to send the commands entered via CLI to the syslog server.</description>
      <pubDate>Fri, 05 Dec 2014 05:19:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-other/cli-history-to-syslog/m-p/11009#M2037</guid>
      <dc:creator>Curtis_Parish1</dc:creator>
      <dc:date>2014-12-05T05:19:00Z</dc:date>
    </item>
    <item>
      <title>RE: CLI history to syslog</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-other/cli-history-to-syslog/m-p/11010#M2038</link>
      <description>I think you can use following command to enable the cli command to log, and then you can configure and enable syslog server&lt;BR /&gt;
&lt;BR /&gt;
enable cli-config-logging&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Fri, 05 Dec 2014 08:40:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-other/cli-history-to-syslog/m-p/11010#M2038</guid>
      <dc:creator>Rex</dc:creator>
      <dc:date>2014-12-05T08:40:00Z</dc:date>
    </item>
    <item>
      <title>RE: CLI history to syslog</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-other/cli-history-to-syslog/m-p/11011#M2039</link>
      <description>According to the S-Series CLI Reference that is not a valid command&lt;BR /&gt;
.</description>
      <pubDate>Fri, 05 Dec 2014 09:53:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-other/cli-history-to-syslog/m-p/11011#M2039</guid>
      <dc:creator>Curtis_Parish1</dc:creator>
      <dc:date>2014-12-05T09:53:00Z</dc:date>
    </item>
    <item>
      <title>RE: CLI history to syslog</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-other/cli-history-to-syslog/m-p/11012#M2040</link>
      <description>That's an EXOS command &lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt;&lt;BR /&gt;
Let me see what I can find out for you, Curt.&lt;BR /&gt;</description>
      <pubDate>Fri, 05 Dec 2014 21:57:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-other/cli-history-to-syslog/m-p/11012#M2040</guid>
      <dc:creator>Drew_C</dc:creator>
      <dc:date>2014-12-05T21:57:00Z</dc:date>
    </item>
    <item>
      <title>RE: CLI history to syslog</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-other/cli-history-to-syslog/m-p/11013#M2041</link>
      <description>For the N,S or K series you can raise the logging level for "Security" which which will log configuration commands to the log buffer and syslog.  The command is "set logging application Security level 8"&lt;BR /&gt;</description>
      <pubDate>Fri, 05 Dec 2014 22:08:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-other/cli-history-to-syslog/m-p/11013#M2041</guid>
      <dc:creator>Alex24</dc:creator>
      <dc:date>2014-12-05T22:08:00Z</dc:date>
    </item>
    <item>
      <title>RE: CLI history to syslog</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-other/cli-history-to-syslog/m-p/11014#M2042</link>
      <description>The S Series will only log commands that create configuration changes..&lt;BR /&gt;
&lt;BR /&gt;
The two commands you are looking for to enable the most verbose logging of command line actions on the S and K series are (this assumes you already have a syslog destination configured);&lt;BR /&gt;
&lt;BR /&gt;
set logging application CLI level 8&lt;BR /&gt;
set logging application Security level 8&lt;BR /&gt;
&lt;BR /&gt;
The 'Security' application will log when (and which) users log in and out.  The 'CLI' application will log what commands are entered that are configuration changes.&lt;BR /&gt;
&lt;BR /&gt;
Logging ALL cli commands would need to be a feature request.&lt;BR /&gt;
&lt;BR /&gt;
Best Regards,&lt;BR /&gt;
Larry&lt;BR /&gt;</description>
      <pubDate>Fri, 05 Dec 2014 22:09:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-other/cli-history-to-syslog/m-p/11014#M2042</guid>
      <dc:creator>Larry_Baker</dc:creator>
      <dc:date>2014-12-05T22:09:00Z</dc:date>
    </item>
    <item>
      <title>RE: CLI history to syslog</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-other/cli-history-to-syslog/m-p/11015#M2043</link>
      <description>Thanks!  Config changes  should be all that is necessary to log&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Fri, 05 Dec 2014 23:15:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-other/cli-history-to-syslog/m-p/11015#M2043</guid>
      <dc:creator>Curtis_Parish1</dc:creator>
      <dc:date>2014-12-05T23:15:00Z</dc:date>
    </item>
  </channel>
</rss>

