In the event of a kernel panic or freeze, critical logs may not be written to /var/log/messages making it difficult to troubleshoot the root cause. Serial console logging can be configured to capture any kernel messages dumped to the console.
Before beginning this procedure, stop the HDB processes on all hosts. A reboot will be required to complete the procedure.
Configure SUSE for console access
Edit /etc/inittab to set the default runlevel to 3 (disables x-windows on startup).
Add these lines near the top of the file (before the grub entries):
serial --unit=0 --speed=115200
terminal --timeout=8 serial console
Copy the default boot entry, creating a new one before the default entry. Add `console=tty0 console=ttyS0,115200` to the end of the kernel options. Changes to the default grub entry are highlighted in red here:
###Don't change this comment - YaST2 identifier: Original name: linux###
title Serial -- SUSE Linux Enterprise Server 11 SP1 - 22.214.171.124-0.7
Data Center NetworkingHi, I work in a dc environment and have the typical 7k/5k/2k setup. I have noticed we have quite a large amount of traffic traversing our VPC peer link on the 7ks I thought the VPC peer link was only used for control plane ...
Hi all, for a given ACI Design with more than one tenant we have the requirement to extend one L2 Domain to another Tenant because of smooth migrating different systems. We would like to move from network centric to application centric and beca...
I received complaints from remote users that close VPN on my any connect, where some service providers won't let them connect.
They have already performed a local test using the adsl link and did not close the VPN tunnel, but if the signal ...
Hi experts,For years I have explaned to Cisco cutomers how Cisco "optimizes" ACI broadcast flooding by default by treating ARPs more like IP packets rather than broadcasts.So I was suprised to notice that in ACI v4.2 the default setting when choosing "Opt...