OpenVZ Forum


Home » General » Support » Sun UltraSPARC T1 CPU architecture compatibility
ALOM remote console information [message #7764 is a reply to message #7755] Tue, 24 October 2006 17:30 Go to previous messageGo to previous message
jonathankinney is currently offline  jonathankinney
Messages: 14
Registered: May 2006
Location: WA
Junior Member
Well, when you built the 2.6.18 kernel and installed it, you did it correctly. The system uses SILO, so after you ran the install command, it either automatically made an entry in the /boot/silo.conf or you manually put it there. Either way, right after you built the kernel, I tested it out and booted with it. It booted perfectly, and it seems to handle high loads better than the 2.6.17 kernel. I just yesterday set the 2.6.18 kernel as the default boot kernel and the system is running off that kernel right now. Right now it looks like you have built and installed what I am assuming is the patched kernel Linux-2.6.18-028test001, and it looks like it is all ready to test and see if it boots.

As for console access, you got it, I just set you up with access to the console, I will send you the details in private. Did I mention I love this server? Remote console access is such a usefull feature. Right now I have it set to autoboot from the first drive, so it will make it to the SILO boot prompt, and there you can just hit enter to use the default kernel, or type the kernel by label such as Linux-2.6.18-028test001 and see if it boots all the way.

Here are some simple notes on the ALOM system I will tell you how to access in private. After you login, you can switch to the console by typing "console -f", the "-f" is for force, so you can kick anyone else out of the console so you have write access, otherwise, you will only be able to view the console. To get out of the console at any time, simply type "#." and it will bring you back to the main sc> prompt of the ALOM system. To reboot the system, if it is not possible via the normal OS commands like "shutdown -r now", then in the sc> prompt, you have several command options such as poweroff, poweron, powercycle, and reset. Some of the commands are redundant, so powercycle is usually the suggested choice. After you do that, you can then switch back to the console and watch the boot messages and eventually feed the SILO boot prompt a command. There are alot of other options, type help for a list, but most others are not relevent to this situation.

There is one bug to note that I just ran into last night. It seems that it is possible for the ALOM system to dump your connection and not be accessable for a period of time. I have only had this happen one time, and I was able to connect to it again after a few minutes. It did not however disrupt access to the host server, so I was still able to login and work on the Ubuntu server without any problems.

I do live in Washington (USA), so I am in the PDT time zone GMT -700, soon to be GMT -800 due to daylight savings. So our days are a bit off from each other, I will keep that in mind.


Jonathan Kinney
Data Systems Specialist
http://www.advantagecom.net

[Updated on: Tue, 24 October 2006 17:50]

Report message to a moderator

 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: OPENVPN user/pass Authentication on OpenVZ
Next Topic: *SOLVED* many procs caught in D state, reason undetermined
Goto Forum:
  


Current Time: Thu Mar 28 12:32:17 GMT 2024

Total time taken to generate the page: 0.01606 seconds