Capturing SecureStack Error Messages in the Logging Buffer and Syslog

  • 0
  • 1
  • Article
  • Updated 5 years ago
  • (Edited)
Article ID: 10869 

Products
SecureStack C3, C2, B3, B2, A2 

Solution
The following commands will help to troubleshoot issues by setting up to send debug-level messages to the logging buffer and to the syslog server:
   set logging default severity 8
set logging local console enable file enable
set logging server 1 ip-addr 10.20.0.1 severity 8 state enable
Here are some captured sample messages showing the presence of bad fans.
  • Output of a 'show logging buffer' command on the SecureStack:
       G 13 11:43:36 10.20.0.113-5 SIM[211623168]: bootos.c(2488) 784 %% Fan
    iled.
    G 13 11:43:36 10.20.0.113-5 SIM[211623168]: bootos.c(2488) 785 %% Fan
    iled.
  • Stored in the syslog server:
       false Critical --- 08/13 10:55:23 AM 10.20.0.113-5 --- --- Event
    --- SIM[211623168]: bootos.c(2488) 799 %% Fan 1 has failed.
Important!
Since raised logging levels can over time destabilize a stack, after testing you should return the logging levels to no higher than 6. 

See also: 5743.
Photo of FAQ User

FAQ User, Official Rep

  • 13,610 Points 10k badge 2x thumb

Posted 5 years ago

  • 0
  • 1

There are no replies.

This conversation is no longer open for comments or replies.