<?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 Interpreting the S/N-Series System Logging Buffer in FAQs</title>
    <link>https://community.extremenetworks.com/t5/faqs/interpreting-the-s-n-series-system-logging-buffer/m-p/45864#M354</link>
    <description>Article ID: 10188 &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Products&lt;/B&gt;&lt;BR /&gt;
S-Series&lt;BR /&gt;
Matrix N-Series DFE &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Solution&lt;/B&gt;&lt;BR /&gt;
The logging buffer, stored in (volatile) DRAM of each blade, contains the up to 256 syslog items generated by that blade since its last boot-up, as filtered by the application logging levels. When the 'show logging buffer' command is issued, each blade is in turn queried and its messages are displayed. Consequently the resulting display is in order by source slot number, then by date and time. &lt;BR /&gt;
&lt;BR /&gt;
What follows is a very abbreviated example of 'show logging buffer' command output, taken from an N7 (7C107) with four modules installed, in slots 1, 3, 5, &amp;amp; 7: &lt;BR /&gt;
&lt;BR /&gt;
&amp;lt;165&amp;gt;Feb 4 16:48:39 10.19.192.3 CLI[1]User: admin logged in from&lt;BR /&gt;
10.18.240.192(ssh)&lt;BR /&gt;
&amp;lt;165&amp;gt;Feb 4 17:00:52 10.19.192.3 CLI[1]User: admin logged out from&lt;BR /&gt;
10.18.240.192(ssh)&lt;BR /&gt;
&amp;lt;165&amp;gt;Feb 5 12:00:52 10.19.192.3 RtrFe[1]Invalid dest IP 0.0.0.255&lt;BR /&gt;
from 10.18.18.189, 00:16:cb??4b:97, Packets Filtered&lt;BR /&gt;
&amp;lt;165&amp;gt;Feb 5 16:32:50 10.19.192.3 Router[1]router 1 interface vlan 750, ip&lt;BR /&gt;
10.18.20.0 is down&lt;BR /&gt;
&amp;lt;166&amp;gt;Feb 5 16:32:50 10.19.192.3 OSPF[1]Interface State Change: rtrid&lt;BR /&gt;
10.18.0.128, ip 10.18.20.1, state DOWN&lt;BR /&gt;
&amp;lt;166&amp;gt;Feb 5 16:32:50 10.19.192.3 OSPF[1]Send New LSA: rtrid 10.18.0.128,&lt;BR /&gt;
area 1.1.1.1, lstype 1, lsid 10.18.0.128&lt;BR /&gt;
&amp;lt;165&amp;gt;Feb 5 16:39:50 10.19.192.3 Router[1]router 1 interface vlan 750, ip&lt;BR /&gt;
10.18.22.0 is up&lt;BR /&gt;
&amp;lt;166&amp;gt;Feb 5 16:39:50 10.19.192.3 VRRP[1]Becoming Master for group 1 on&lt;BR /&gt;
vlan 750, primary ip 10.18.22.1&lt;BR /&gt;
&amp;lt;166&amp;gt;Feb 5 16:39:50 10.19.192.3 OSPF[1]Send New LSA: rtrid 10.18.0.128,&lt;BR /&gt;
area 1.1.1.1, lstype 1, lsid 10.18.0.128&lt;BR /&gt;
&amp;lt;165&amp;gt;Feb 2 03:48:16 10.19.192.3 System[3]A valid Layer 3 Advanced&lt;BR /&gt;
Features (N-EOS-L3) key has been installed. Enabling feature.&lt;BR /&gt;
&amp;lt;163&amp;gt;Feb 2 05:52:34 10.19.192.3 System[3]Time and Date synchronized from&lt;BR /&gt;
slot 1 to: SAT FEB 02 01:49:23 2008&lt;BR /&gt;
&amp;lt;165&amp;gt;Feb 18 08:11:54 10.19.192.3 RtrFe[3]Invalid dest IP 0.0.0.1 from&lt;BR /&gt;
10.18.195.117, 02:02:92??c3:76, Packets Filtered&lt;BR /&gt;
&amp;lt;165&amp;gt;Feb 2 03:48:21 10.19.192.3 System[5]A valid Layer 3 Advanced&lt;BR /&gt;
Features (N-EOS-L3) key has been installed. Enabling feature.&lt;BR /&gt;
&amp;lt;163&amp;gt;Feb 2 05:52:33 10.19.192.3 System[5]Time and Date synchronized from&lt;BR /&gt;
slot 1 to: SAT FEB 02 01:49:23 2008&lt;BR /&gt;
&amp;lt;165&amp;gt;Feb 4 11:48:46 10.19.192.3 RtrFe[5]Invalid dest IP 0.0.166.29 from&lt;BR /&gt;
10.18.17.82, 00:19:e3:d9:08:93, Packets Filtered&lt;BR /&gt;
&amp;lt;165&amp;gt;Feb 2 03:47:48 10.19.192.3 System[7]A valid Layer 3 Advanced&lt;BR /&gt;
Features (N-EOS-L3) key has been installed. Enabling feature.&lt;BR /&gt;
&amp;lt;163&amp;gt;Feb 2 05:52:33 10.19.192.3 System[7]Time and Date synchronized from&lt;BR /&gt;
slot 1 to: SAT FEB 02 01:49:23 2008&lt;BR /&gt;
Reviewing the items from left to right, these are the elements of note:&lt;UL&gt; 
&lt;LI&gt;The bracketed 3-digit number at the beginning represents the logging Severity level (&lt;A href="http://bit.ly/1iTJpYd" target="_blank" rel="nofollow noreferrer noopener"&gt;14635&lt;/A&gt;) used by the syslog application when generating the message. The entries shown above are either 4(errors), 6(notifications), or7(information). 
&lt;/LI&gt;&lt;LI&gt;Next is the system Month, Day, Hour, Minute, and Second as of when the message was generated. 
&lt;/LI&gt;&lt;LI&gt;Next is the message's Source IP address, which should match the assigned System IP address of this DFE. 
&lt;/LI&gt;&lt;LI&gt;Next is the generating syslog application, with the source slot number in square brackets. 
&lt;/LI&gt;&lt;LI&gt;Last is the actual syslog message.&lt;/LI&gt;&lt;/UL&gt;See also: &lt;A href="http://bit.ly/1cOfueZ" target="_blank" rel="nofollow noreferrer noopener"&gt;7494&lt;/A&gt;.</description>
    <pubDate>Thu, 28 Nov 2013 01:11:00 GMT</pubDate>
    <dc:creator>FAQ_User</dc:creator>
    <dc:date>2013-11-28T01:11:00Z</dc:date>
    <item>
      <title>Interpreting the S/N-Series System Logging Buffer</title>
      <link>https://community.extremenetworks.com/t5/faqs/interpreting-the-s-n-series-system-logging-buffer/m-p/45864#M354</link>
      <description>Article ID: 10188 &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Products&lt;/B&gt;&lt;BR /&gt;
S-Series&lt;BR /&gt;
Matrix N-Series DFE &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Solution&lt;/B&gt;&lt;BR /&gt;
The logging buffer, stored in (volatile) DRAM of each blade, contains the up to 256 syslog items generated by that blade since its last boot-up, as filtered by the application logging levels. When the 'show logging buffer' command is issued, each blade is in turn queried and its messages are displayed. Consequently the resulting display is in order by source slot number, then by date and time. &lt;BR /&gt;
&lt;BR /&gt;
What follows is a very abbreviated example of 'show logging buffer' command output, taken from an N7 (7C107) with four modules installed, in slots 1, 3, 5, &amp;amp; 7: &lt;BR /&gt;
&lt;BR /&gt;
&amp;lt;165&amp;gt;Feb 4 16:48:39 10.19.192.3 CLI[1]User: admin logged in from&lt;BR /&gt;
10.18.240.192(ssh)&lt;BR /&gt;
&amp;lt;165&amp;gt;Feb 4 17:00:52 10.19.192.3 CLI[1]User: admin logged out from&lt;BR /&gt;
10.18.240.192(ssh)&lt;BR /&gt;
&amp;lt;165&amp;gt;Feb 5 12:00:52 10.19.192.3 RtrFe[1]Invalid dest IP 0.0.0.255&lt;BR /&gt;
from 10.18.18.189, 00:16:cb??4b:97, Packets Filtered&lt;BR /&gt;
&amp;lt;165&amp;gt;Feb 5 16:32:50 10.19.192.3 Router[1]router 1 interface vlan 750, ip&lt;BR /&gt;
10.18.20.0 is down&lt;BR /&gt;
&amp;lt;166&amp;gt;Feb 5 16:32:50 10.19.192.3 OSPF[1]Interface State Change: rtrid&lt;BR /&gt;
10.18.0.128, ip 10.18.20.1, state DOWN&lt;BR /&gt;
&amp;lt;166&amp;gt;Feb 5 16:32:50 10.19.192.3 OSPF[1]Send New LSA: rtrid 10.18.0.128,&lt;BR /&gt;
area 1.1.1.1, lstype 1, lsid 10.18.0.128&lt;BR /&gt;
&amp;lt;165&amp;gt;Feb 5 16:39:50 10.19.192.3 Router[1]router 1 interface vlan 750, ip&lt;BR /&gt;
10.18.22.0 is up&lt;BR /&gt;
&amp;lt;166&amp;gt;Feb 5 16:39:50 10.19.192.3 VRRP[1]Becoming Master for group 1 on&lt;BR /&gt;
vlan 750, primary ip 10.18.22.1&lt;BR /&gt;
&amp;lt;166&amp;gt;Feb 5 16:39:50 10.19.192.3 OSPF[1]Send New LSA: rtrid 10.18.0.128,&lt;BR /&gt;
area 1.1.1.1, lstype 1, lsid 10.18.0.128&lt;BR /&gt;
&amp;lt;165&amp;gt;Feb 2 03:48:16 10.19.192.3 System[3]A valid Layer 3 Advanced&lt;BR /&gt;
Features (N-EOS-L3) key has been installed. Enabling feature.&lt;BR /&gt;
&amp;lt;163&amp;gt;Feb 2 05:52:34 10.19.192.3 System[3]Time and Date synchronized from&lt;BR /&gt;
slot 1 to: SAT FEB 02 01:49:23 2008&lt;BR /&gt;
&amp;lt;165&amp;gt;Feb 18 08:11:54 10.19.192.3 RtrFe[3]Invalid dest IP 0.0.0.1 from&lt;BR /&gt;
10.18.195.117, 02:02:92??c3:76, Packets Filtered&lt;BR /&gt;
&amp;lt;165&amp;gt;Feb 2 03:48:21 10.19.192.3 System[5]A valid Layer 3 Advanced&lt;BR /&gt;
Features (N-EOS-L3) key has been installed. Enabling feature.&lt;BR /&gt;
&amp;lt;163&amp;gt;Feb 2 05:52:33 10.19.192.3 System[5]Time and Date synchronized from&lt;BR /&gt;
slot 1 to: SAT FEB 02 01:49:23 2008&lt;BR /&gt;
&amp;lt;165&amp;gt;Feb 4 11:48:46 10.19.192.3 RtrFe[5]Invalid dest IP 0.0.166.29 from&lt;BR /&gt;
10.18.17.82, 00:19:e3:d9:08:93, Packets Filtered&lt;BR /&gt;
&amp;lt;165&amp;gt;Feb 2 03:47:48 10.19.192.3 System[7]A valid Layer 3 Advanced&lt;BR /&gt;
Features (N-EOS-L3) key has been installed. Enabling feature.&lt;BR /&gt;
&amp;lt;163&amp;gt;Feb 2 05:52:33 10.19.192.3 System[7]Time and Date synchronized from&lt;BR /&gt;
slot 1 to: SAT FEB 02 01:49:23 2008&lt;BR /&gt;
Reviewing the items from left to right, these are the elements of note:&lt;UL&gt; 
&lt;LI&gt;The bracketed 3-digit number at the beginning represents the logging Severity level (&lt;A href="http://bit.ly/1iTJpYd" target="_blank" rel="nofollow noreferrer noopener"&gt;14635&lt;/A&gt;) used by the syslog application when generating the message. The entries shown above are either 4(errors), 6(notifications), or7(information). 
&lt;/LI&gt;&lt;LI&gt;Next is the system Month, Day, Hour, Minute, and Second as of when the message was generated. 
&lt;/LI&gt;&lt;LI&gt;Next is the message's Source IP address, which should match the assigned System IP address of this DFE. 
&lt;/LI&gt;&lt;LI&gt;Next is the generating syslog application, with the source slot number in square brackets. 
&lt;/LI&gt;&lt;LI&gt;Last is the actual syslog message.&lt;/LI&gt;&lt;/UL&gt;See also: &lt;A href="http://bit.ly/1cOfueZ" target="_blank" rel="nofollow noreferrer noopener"&gt;7494&lt;/A&gt;.</description>
      <pubDate>Thu, 28 Nov 2013 01:11:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/faqs/interpreting-the-s-n-series-system-logging-buffer/m-p/45864#M354</guid>
      <dc:creator>FAQ_User</dc:creator>
      <dc:date>2013-11-28T01:11:00Z</dc:date>
    </item>
  </channel>
</rss>

