https://community.extremenetworks.com/t5/faqs/capturing-securestack-error-messages-in-the-logging-buffer-and/m-p/45339#M312 Article ID: 10869 <BR /> <BR /> <B>Products</B><BR /> SecureStack C3, C2, B3, B2, A2 <BR /> <BR /> <B>Solution</B><BR /> 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<BR /> set logging local console enable file enable<BR /> set logging server 1 ip-addr 10.20.0.1 severity 8 state enableHere are some captured sample messages showing the presence of bad fans.<UL> <LI>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. </LI><LI>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.</LI></UL><U>Important!</U><BR /> Since raised logging levels can over time destabilize a stack, after testing you should return the logging levels to no higher than 6. <BR /> <BR /> See also: <A href="http://bit.ly/1cpN7UG" target="_blank" rel="nofollow noreferrer noopener">5743</A>. Tue, 03 Dec 2013 21:00:00 GMT FAQ_User 2013-12-03T21:00:00Z https://community.extremenetworks.com/t5/faqs/capturing-securestack-error-messages-in-the-logging-buffer-and/m-p/45339#M312 Article ID: 10869 <BR /> <BR /> <B>Products</B><BR /> SecureStack C3, C2, B3, B2, A2 <BR /> <BR /> <B>Solution</B><BR /> 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<BR /> set logging local console enable file enable<BR /> set logging server 1 ip-addr 10.20.0.1 severity 8 state enableHere are some captured sample messages showing the presence of bad fans.<UL> <LI>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. </LI><LI>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.</LI></UL><U>Important!</U><BR /> Since raised logging levels can over time destabilize a stack, after testing you should return the logging levels to no higher than 6. <BR /> <BR /> See also: <A href="http://bit.ly/1cpN7UG" target="_blank" rel="nofollow noreferrer noopener">5743</A>. Tue, 03 Dec 2013 21:00:00 GMT https://community.extremenetworks.com/t5/faqs/capturing-securestack-error-messages-in-the-logging-buffer-and/m-p/45339#M312 FAQ_User 2013-12-03T21:00:00Z