Over three decades of Information Technology experience, specializing in High Performance Networks, Security Architecture, E-Commerce Engineering, Data Center Design, Implementation and Support
Friday, January 18, 2019
Troubleshoot crashkernel causing the Cluster member to reboot itself
If the issue re-occurs after that, we would need to gather the following information:
1. Cpinfo (from both Cluster members, sk92739).
2. /var/log/messages* (From both Cluster members, All 5 Files).
- Run following command in expert will create a tgz file with all of the messages in the present working directory:
- #tar zcvf messages.tgz /var/log/messages*
3. Export the cpview history database file (from both cluster members, sk101878) using the following command (from expert):
# cpview history export
Upload the file generated (should be in /var/log/CPView_history/)
4. From CLISH: >show routed cluster-state detailed (from both Cluster members)
5. ClusterXL messages from SmartConsole logs - according to the following procedure:
a. Go to the Logs & Monitor tab
b. Open the relevant log files.
c. After you have the correct file open, please use the following filter:
d. origin:(FW01 OR FW02) AND type:Control AND (ClusterXL)
e. On the search bar, there is an option to export the logs
f. Please send Checkpoint that resulting file
Any core or crash files from the following locations:
/var/log/crash
/var/log/dump/usermode