serial_over_lan_connection_issues
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
serial_over_lan_connection_issues [2018/11/29 14:18] – [Errors] walkeradmin | serial_over_lan_connection_issues [2023/03/09 22:35] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 3: | Line 3: | ||
\\ | \\ | ||
\\ | \\ | ||
- | |||
---- | ---- | ||
Line 58: | 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: | 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 65: | Line 64: | ||
\\ | \\ | ||
ctrl g 1 | ctrl g 1 | ||
+ | | ||
+ | Remember | ||
+ | ctrl-g 0 is the switch | ||
+ | ctrl-g 1-9 are the sleds | ||
\\ | \\ | ||
\\ | \\ | ||
Line 73: | Line 76: | ||
\\ | \\ | ||
\\ | \\ | ||
- | <color # | + | <color # |
\\ | \\ | ||
\\ | \\ | ||
Line 79: | Line 82: | ||
---- | ---- | ||
\\ | \\ | ||
- | ==== Errors | + | ==== Console dropped due to BP Com Request Error ==== |
The first error I came across is shown below: | The first error I came across is shown below: | ||
\\ | \\ | ||
Line 86: | Line 89: | ||
\\ | \\ | ||
\\ | \\ | ||
- | This occured when using the Web CLI, when I tried to connect, I see the error **Console dropped due to BP Com Request | + | This occured when using the Web CLI, when I tried to connect, I see the error <color #ed1c24>Console dropped due to BP Com Request</ |
+ | \\ | ||
+ | \\ | ||
+ | By using a serial connection to the Console port on the T1, you can see the IPMI Tool (115200, | ||
+ | \\ | ||
+ | \\ | ||
+ | The error <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 # | ||
+ | \\ | ||
+ | \\ | ||
+ | Again, you will either have to connect to the OS with SSH or using the Keyboard / Monitor locally. | ||
+ | \\ | ||
+ | \\ | ||
+ | Edit the following file: | ||
+ | \\ | ||
+ | \\ | ||
+ | / | ||
+ | \\ | ||
+ | \\ | ||
+ | Edit this file from this: | ||
+ | \\ | ||
+ | < | ||
+ | GRUB_TIMEOUT=5 | ||
+ | GRUB_DISTRIBUTOR=" | ||
+ | GRUB_DEFAULT=saved | ||
+ | GRUB_DISABLE_SUBMENU=true | ||
+ | GRUB_TERMINAL_OUTPUT=" | ||
+ | GRUB_CMDLINE_LINUX=" | ||
+ | GRUB_DISABLE_RECOVERY=" | ||
+ | </ | ||
+ | \\ | ||
+ | To this: | ||
+ | \\ | ||
+ | < | ||
+ | GRUB_TIMEOUT=5 | ||
+ | GRUB_DISTRIBUTOR=" | ||
+ | GRUB_DEFAULT=saved | ||
+ | GRUB_DISABLE_SUBMENU=true | ||
+ | GRUB_TERMINAL_OUTPUT=" | ||
+ | GRUB_CMDLINE_LINUX=" | ||
+ | GRUB_DISABLE_RECOVERY=" | ||
+ | GRUB_TERMINAL=" | ||
+ | GRUB_SERIAL_COMMAND=" | ||
+ | </ | ||
+ | \\ | ||
+ | Run the following command | ||
+ | \\ | ||
+ | < | ||
+ | grub2-mkconfig -o / | ||
+ | </ | ||
+ | \\ | ||
+ | Reboot and try the Web CLI Connection again. | ||
+ | \\ | ||
+ | \\ |
serial_over_lan_connection_issues.1543501092.txt.gz · Last modified: 2023/03/09 22:35 (external edit)