cancel
Showing results for 
Search instead for 
Did you mean: 

Interpreting the S/N-Series System Logging Buffer

Interpreting the S/N-Series System Logging Buffer

FAQ_User
Extreme Employee
Article ID: 10188

Products
S-Series
Matrix N-Series DFE

Solution
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.

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, & 7:

<165>Feb 4 16:48:39 10.19.192.3 CLI[1]User: admin logged in from
10.18.240.192(ssh)
<165>Feb 4 17:00:52 10.19.192.3 CLI[1]User: admin logged out from
10.18.240.192(ssh)
<165>Feb 5 12:00:52 10.19.192.3 RtrFe[1]Invalid dest IP 0.0.0.255
from 10.18.18.189, 00:16:cb??4b:97, Packets Filtered
<165>Feb 5 16:32:50 10.19.192.3 Router[1]router 1 interface vlan 750, ip
10.18.20.0 is down
<166>Feb 5 16:32:50 10.19.192.3 OSPF[1]Interface State Change: rtrid
10.18.0.128, ip 10.18.20.1, state DOWN
<166>Feb 5 16:32:50 10.19.192.3 OSPF[1]Send New LSA: rtrid 10.18.0.128,
area 1.1.1.1, lstype 1, lsid 10.18.0.128
<165>Feb 5 16:39:50 10.19.192.3 Router[1]router 1 interface vlan 750, ip
10.18.22.0 is up
<166>Feb 5 16:39:50 10.19.192.3 VRRP[1]Becoming Master for group 1 on
vlan 750, primary ip 10.18.22.1
<166>Feb 5 16:39:50 10.19.192.3 OSPF[1]Send New LSA: rtrid 10.18.0.128,
area 1.1.1.1, lstype 1, lsid 10.18.0.128
<165>Feb 2 03:48:16 10.19.192.3 System[3]A valid Layer 3 Advanced
Features (N-EOS-L3) key has been installed. Enabling feature.
<163>Feb 2 05:52:34 10.19.192.3 System[3]Time and Date synchronized from
slot 1 to: SAT FEB 02 01:49:23 2008
<165>Feb 18 08:11:54 10.19.192.3 RtrFe[3]Invalid dest IP 0.0.0.1 from
10.18.195.117, 02:02:92??c3:76, Packets Filtered
<165>Feb 2 03:48:21 10.19.192.3 System[5]A valid Layer 3 Advanced
Features (N-EOS-L3) key has been installed. Enabling feature.
<163>Feb 2 05:52:33 10.19.192.3 System[5]Time and Date synchronized from
slot 1 to: SAT FEB 02 01:49:23 2008
<165>Feb 4 11:48:46 10.19.192.3 RtrFe[5]Invalid dest IP 0.0.166.29 from
10.18.17.82, 00:19:e3:d9:08:93, Packets Filtered
<165>Feb 2 03:47:48 10.19.192.3 System[7]A valid Layer 3 Advanced
Features (N-EOS-L3) key has been installed. Enabling feature.
<163>Feb 2 05:52:33 10.19.192.3 System[7]Time and Date synchronized from
slot 1 to: SAT FEB 02 01:49:23 2008
Reviewing the items from left to right, these are the elements of note:
  • The bracketed 3-digit number at the beginning represents the logging Severity level (14635) used by the syslog application when generating the message. The entries shown above are either 4(errors), 6(notifications), or7(information).
  • Next is the system Month, Day, Hour, Minute, and Second as of when the message was generated.
  • Next is the message's Source IP address, which should match the assigned System IP address of this DFE.
  • Next is the generating syslog application, with the source slot number in square brackets.
  • Last is the actual syslog message.
See also: 7494.
0 REPLIES 0
GTM-P2G8KFN