Update doc for remote console.

docs/aims2/remoteconsole.md

@@ -4,9 +4,9 @@ This section servers as a recommendation of practices that we know do the job of
 
 ## Retrieving console credentials for machines
 
-In order to get a console you first need the BMC credentials to access the machine. These can come from two different places.
+Before getting acces to a console you first need the BMC credentials to access the machine. These can come from two different places.
 
-Of course this details can be extracted through the corresponding APIs.
+Of course these details can be extracted through the corresponding APIs.
 
 ### Judy credentials
 
@@ -16,6 +16,34 @@ Of course this details can be extracted through the corresponding APIs.
 
 ![Openstack BMC credentials](../assets/images/openstack_credentials.png)
 
+## Serial Over LAN
+
+According to attempts on December 2022, this is the only way that works.
+
+After getting the credentials for the machine of interest from Judy (Console Username and console Password), you can run the following command from aiadm:
+
+```bash
+[djuarezg@aiadm10 ~]$ ipmitool -I lanplus -H techlab-arm64-thunderx-01-ipmi -U <console_username> -P <console_password> sol activate
+```
+
+Then you are prompted to login. Type "root".
+
+The password for this login is defined by the "tellme" number. According to [Root passwords](https://configdocs.web.cern.ch/tellme/index.html) documented by Configuration Management you can get the password by running this command from aiadm:
+```bash
+$ tellme show root --host techlab-arm64-thunderx-01
+```
+Use the response/password and you will be connected to the node (in this case: techlab-arm64-thunderx-01).
+
+If you need to reboot the machine from remote console, you go to: Judy -> Properties [Remote console : Console] -> Power -> Power Cycle System -> Apply Changes
+
+While you are connected through SOL you can see the machine rebooting and you will be able to intervene on the boot process (e.g. go to Rescue Boot) if needed.
+
+The server configuration URL will show you different tabs and configuration options. It is impossible to tell you where the needed option will be as each vendor has its own WebUI.
+
+If you encounter any IPMI misbehaviour use [`ipmiproxy`](https://gitlab.cern.ch/hw/ipmiproxy) from `aiadm` instead, a tool maintained by our procurement colleagues.
+
+Of course when using SOL you will not be able to see any graphical interface, like AIMS menus, graphical OS installer etc. SOL can help when any other visual console methods fail.
+
 ## vKVM or any similar Java Web based applet
 
 If you are not on the CERN network, the IPMI URL will not be accessible. If you are using an SSH proxy, make sure also the console traffic is proxied.
@@ -30,18 +58,6 @@ As a backup plan, use [CERN Terminal Servers](https://espace.cern.ch/winservices
 
 Once in, using your remote desktop application of preference (Remote Desktop Viewer on CentOS 7 by default), connecting to <cernts.cern.ch> using RDP protocol, you can repeat the process and get the console URL from either Judy/Foreman or Openstack.
 
-## Serial Over LAN
-
-The server configuration URL will show you different tabs and configuration options. It is impossible to tell you where the needed option will be as each vendor has its own WebUI.
-In any case, you will be able to retrieve the SOL (Serial Over LAN) credentials from there to be able to have an open console session through text on your terminal.
-
-```bash
-[djuarezg@aiadm10 ~]$ ipmitool -I lanplus -H techlab-arm64-thunderx-01-ipmi -U username -P password sol activate
-```
-
-If you encounter any IPMI misbehaviour use [`ipmiproxy`](https://gitlab.cern.ch/hw/ipmiproxy) from `aiadm` instead, a tool maintained by our procurement colleagues.
-
-Of course when using SOL you will not be able to see any graphical interface, like AIMS menus, graphical OS installer etc. SOL can help when any other visual console methods fail.
 
 ## HTML5 console