Differences

This shows you the differences between two versions of the page.

--- serial_over_lan_connection_issues [2018/11/29 16:07] – walkeradmin
+++ serial_over_lan_connection_issues [2023/03/09 22:35] (current) – external edit 127.0.0.1
@@ Line 1: / Line 1: @@
 ====== Serial over LAN connection issues ======
 <color darkorange>Nov 2018</color>
-\\
-\\
-===== <color #ed1c24>THIS SECTION IS NOT COMPLETE</color> =====
-\\
 \\
 \\
@@ Line 62: / Line 57: @@
 Above we can see the Serial Over LAN port selection. When you are connected to the T1 via a Serial Console connection, you can use the following command:
 \\
-    ctrl g no
+    ctrl g number
 \\
 \\
@@ Line 69: / Line 64: @@
 \\
     ctrl g 1
+    Remember
+    ctrl-g 0 is the switch
+    ctrl-g 1-9 are the sleds
 \\
 \\
@@ Line 77: / Line 76: @@
 \\
 \\
-<color #ed1c24>ctrl gg</color> 0/1/2 will connect you to either the (0) BCM, (1) Server1 or (2) Server2.
+<color #ed1c24>ctrl gg 0/1/2</color> will connect you to either the (0) BCM, (1) Server1 or (2) Server2.
 \\
 \\
@@ Line 83: / Line 82: @@
 ----
 \\
-==== Errors ====
+==== Console dropped due to BP Com Request Error ====
 The first error I came across is shown below:
 \\
@@ Line 94: / Line 93: @@
 \\
 By using a serial connection to the Console port on the T1, you can see the IPMI Tool (115200,8,n,1) login admin/admin
+\\
+\\
+The error <color #ed1c24>Console dropped due to BP Com Request</color> means that the BMC cannot properly be contacted. To fix this we need to connect to the BMC via serial. Although the serial over LAN is not working, you should still be able to connect to the BMC using <color #ed1c24>ctrl-g 'sled number'</color>
+\\
+\\
+You might have to toggle between the BCM and Payload a couple of times to get the BCM to respond (ctrl gg 0, then ctrl gg 1, then ctrl-gg 0) and keep hitting enter until you get a response.
+\\
+\\
+Once connected to the BMC, and from the command line run the following command:
+\\
+    mc reset cold
+\\
+Reboot the Node, retest the Serial Over LAN connection.
 \\
 \\
+----
+\\
+==== Connection Stops at SOL Session Operational. Use ~? for help Error ====
+If you get this far <color #ed1c24>SOL Session Operational. Use ~? for help</color> but no connection, then there could be an issue with the serial settings in the OS.
+\\
+\\
+Again, you will either have to connect to the OS with SSH or using the Keyboard / Monitor locally.
+\\
+\\
+Edit the following file:
+\\
+\\
+    /etc/default/grub
+\\
+\\
+Edit this file from this:
+\\
+<file>
+GRUB_TIMEOUT=5
+GRUB_DISTRIBUTOR="$(sed 's, release .*$,,g' /etc/system-release)"
+GRUB_DEFAULT=saved
+GRUB_DISABLE_SUBMENU=true
+GRUB_TERMINAL_OUTPUT="console"
+GRUB_CMDLINE_LINUX="crashkernel=auto rd.lvm.lv=vg_main/lv_root rhgb quiet"
+GRUB_DISABLE_RECOVERY="true"
+</file>
+\\
+To this:
+\\
+<file>
+GRUB_TIMEOUT=5
+GRUB_DISTRIBUTOR="$(sed 's, release .*$,,g' /etc/system-release)"
+GRUB_DEFAULT=saved
+GRUB_DISABLE_SUBMENU=true
+GRUB_TERMINAL_OUTPUT="console"
+GRUB_CMDLINE_LINUX="crashkernel=auto rd.lvm.lv=vg_main/lv_root console=ttyS0,115200"
+GRUB_DISABLE_RECOVERY="true"
+GRUB_TERMINAL="serial"
+GRUB_SERIAL_COMMAND="serial --speed=115200 --unit=0 --word=8 --parity=no --stop=1"
+</file>
+\\
+Run the following command
+\\
+<file>
+grub2-mkconfig -o /boot/grub2/grub.cfg
+</file>
+\\
+Reboot and try the Web CLI Connection again.
+\\
+\\