Hi team!
Here's a valuable case that eSight Monitoring Continuously Restarts on SNS Fibre Channel Switches.
Symptoms
The errdump log shows that the switch frequently restarts due to kernel panic.
(1) The following error log is displayed in the errdump log of the switch.
The switch reboot cause is Software Fault: Kernel Panic.
2020/01/11-01:26:20, [HAM-1004], 161, CHASSIS, INFO, SNS2624, Processor rebooted - Software Fault:Kernel Panic.
2020/01/13-04:23:26, [HAM-1004], 168, CHASSIS, INFO, SNS2624, Processor rebooted - Software Fault:Kernel Panic.
2020/01/15-07:17:00, [HAM-1004], 176, CHASSIS, INFO, SNS2624, Processor rebooted - Software Fault:Kernel Panic.
2020/01/17-10:01:26, [HAM-1004], 183, CHASSIS, INFO, SNS2624, Processor rebooted - Software Fault:Kernel Panic.
2020/01/19-13:11:00, [HAM-1004], 190, CHASSIS, INFO, SNS2624, Processor rebooted - Software Fault:Kernel Panic.
2020/01/21-16:00:06, [HAM-1004], 197, CHASSIS, INFO, SNS2624, Processor rebooted - Software Fault:Kernel Panic.
(2) eSight monitors switches in SMI-S+SSH mode.
(3) A large number of echo $LANG print records exist in the CLI of the switch.
Cause
eSight frequently logs in to and logs out of the switch through SSH to query information.
As a result, the switch memory leaks and frequently restarts due to Kermel panics.
Solution
On eSight, change the switch monitoring mode to SMI-S (delete the switch and add it again), and restart the eSight service.
Check After Restoration
The clihistory does not contain echo $LANG.
Appendix
eSight uses SSH to monitor switches.
The switch has a fabric vsition license and flow monitoring objects have been configured on the switch. Then eSight uses SSH to query flow monitoring information.
This feature is rarely used on the live network.
Applicable Scope
SNS Fibre Channel switch and Brocade Fibre Channel switch
That's all, thanks!
