From friedman at www1.emax.ca Fri Aug 1 17:26:46 2008 From: friedman at www1.emax.ca (Barry Friedman) Date: Fri Aug 1 17:26:54 2008 Subject: Changing the console com port In-Reply-To: <6863f0c90807291826k55814fe2u837fb60493230c44@mail.gmail.com> References: <20080729184452.GA14558@emax.ca> <6863f0c90807291826k55814fe2u837fb60493230c44@mail.gmail.com> Message-ID: <20080801172644.GA28300@emax.ca> John, Thanks for this. I hadn't noticed the RBSU setup option F9 during boot and I see that this allows the change of serial port. In the end I was able to use the standard COM2 port by changing the sio1 flags in /boot/device.hints and this seems to work in freebsd 7 (also needed to remove the sio0 flags line and add a boot.config file). In examing the RBSU options, I noticed a thermal shutdown option which was enabled. Is there any chance of this triggering a reboot without leaving any ILO log messages? Barry You wrote: > You have to use the BIOS configuration utility to configure which COM port > resources are used for the iLO Virtual Serial Port. (Also called RBSU - ROM > Based Setup Utility.) That utility is either menu driven, or command line > driven -- it has its own settings for that choice. > > I think the root of the problem Anders was having is that FreeBSD insists on > using the ACPI tables to enable serial ports, instead of just "hardwiring" > the COM1 and COM2 ports as serial consoles. Maybe if you disable ACPI you > can do what Anders wanted to do. -- Barry Friedman Emax Computer Systems Inc., 480 Tweedsmuir Ave., Ottawa, Ont. Canada K1Z 5N9 bfriedman@emax.ca Phone: (613) 725-3198 Fax: 725-0298 From jcagle at gmail.com Fri Aug 1 17:53:20 2008 From: jcagle at gmail.com (John Cagle) Date: Fri Aug 1 17:53:27 2008 Subject: Changing the console com port In-Reply-To: <20080801172644.GA28300@emax.ca> References: <20080729184452.GA14558@emax.ca> <6863f0c90807291826k55814fe2u837fb60493230c44@mail.gmail.com> <20080801172644.GA28300@emax.ca> Message-ID: <6863f0c90808011053n6f81c2eci5a6f1f48826a987c@mail.gmail.com> I'm not sure about that particular option on that particular server, but it probably needs to have a health driver running in order to log it to the IML (integrated management log) which is viewable with iLO. If the server is based on iLO-2, then it should be logged to the IML without having to run a health driver. There is a different thermal shutdown feature of all ProLiants -- when the server/cpu reaches a "temp deadly" setting, the box will immediately shut down. This feature has saved many ProLiant servers during computer room cooling failures over weekends when no one was around... Other servers burned up during those events... John On Fri, Aug 1, 2008 at 12:26 PM, Barry Friedman wrote: > John, > > Thanks for this. I hadn't noticed the RBSU setup option F9 during boot > and I see that this allows the change of serial port. In the end I > was able to use the standard COM2 port by changing the sio1 flags in > /boot/device.hints and this seems to work in freebsd 7 (also needed to > remove the sio0 flags line and add a boot.config file). > > In examing the RBSU options, I noticed a thermal shutdown option which > was enabled. Is there any chance of this triggering a reboot without > leaving any ILO log messages? > > Barry > > > You wrote: > > You have to use the BIOS configuration utility to configure which COM > port > > resources are used for the iLO Virtual Serial Port. (Also called RBSU - > ROM > > Based Setup Utility.) That utility is either menu driven, or command > line > > driven -- it has its own settings for that choice. > > > > I think the root of the problem Anders was having is that FreeBSD insists > on > > using the ACPI tables to enable serial ports, instead of just > "hardwiring" > > the COM1 and COM2 ports as serial consoles. Maybe if you disable ACPI > you > > can do what Anders wanted to do. > > -- > Barry Friedman > Emax Computer Systems Inc., 480 Tweedsmuir Ave., Ottawa, Ont. Canada K1Z > 5N9 > bfriedman@emax.ca Phone: (613) 725-3198 Fax: 725-0298 > From friedman at www1.emax.ca Fri Aug 1 22:21:32 2008 From: friedman at www1.emax.ca (Barry Friedman) Date: Fri Aug 1 22:21:41 2008 Subject: Changing the console com port In-Reply-To: <6863f0c90808011053n6f81c2eci5a6f1f48826a987c@mail.gmail.com> References: <20080729184452.GA14558@emax.ca> <6863f0c90807291826k55814fe2u837fb60493230c44@mail.gmail.com> <20080801172644.GA28300@emax.ca> <6863f0c90808011053n6f81c2eci5a6f1f48826a987c@mail.gmail.com> Message-ID: <20080801222130.GA43859@emax.ca> You wrote: > I'm not sure about that particular option on that particular server, but it > probably needs to have a health driver running in order to log it to the IML > (integrated management log) which is viewable with iLO. If the server is > based on iLO-2, then it should be logged to the IML without having to run a > health driver. The DL380G4 box only has iLO standard and I presume that there is no health driver running. Now that I have the virtual console working I am faced with the problem that the iLO seems to time out the connection after about 30 min so there is still a difficulty in logging the reboot event which seems to be happening once every ~ 1-5 days. Is there any chance that we'll be seeing the utility software (hpasmd, hpacucli, hpadu) compiled for freebsd 7 any time soon? > There is a different thermal shutdown feature of all ProLiants -- when the > server/cpu reaches a "temp deadly" setting, the box will immediately shut > down. This feature has saved many ProLiant servers during computer room > cooling failures over weekends when no one was around... Other servers > burned up during those events... Thanks again, -- Barry Friedman Emax Computer Systems Inc., 480 Tweedsmuir Ave., Ottawa, Ont. Canada K1Z 5N9 bfriedman@emax.ca Phone: (613) 725-3198 Fax: 725-0298 From jcagle at gmail.com Fri Aug 1 22:45:04 2008 From: jcagle at gmail.com (John Cagle) Date: Fri Aug 1 22:45:11 2008 Subject: Changing the console com port In-Reply-To: <20080801222130.GA43859@emax.ca> References: <20080729184452.GA14558@emax.ca> <6863f0c90807291826k55814fe2u837fb60493230c44@mail.gmail.com> <20080801172644.GA28300@emax.ca> <6863f0c90808011053n6f81c2eci5a6f1f48826a987c@mail.gmail.com> <20080801222130.GA43859@emax.ca> Message-ID: <6863f0c90808011545j373e3d1bo18681cd53739bd05@mail.gmail.com> If you're using SSH to access the Virtual Serial Port of iLO, you should be able to set the Idle Connection Timeout to "Infinite" instead of 30 minutes. (This setting is available in the Web administration pages of iLO itself.) However, I don't think that VSP connections will ever time out, but I might be wrong. If the "Infinite" option is not available, then you should consider updating the iLO firmware. Also you probably should explore the other iLO settings -- perhaps there are some other things that you want to enable/disable. I don't know about the utility software... John On Fri, Aug 1, 2008 at 5:21 PM, Barry Friedman wrote: > You wrote: > > I'm not sure about that particular option on that particular server, but > it > > probably needs to have a health driver running in order to log it to the > IML > > (integrated management log) which is viewable with iLO. If the server is > > based on iLO-2, then it should be logged to the IML without having to run > a > > health driver. > > The DL380G4 box only has iLO standard and I presume that there is no > health driver running. Now that I have the virtual console working > I am faced with the problem that the iLO seems to time out the connection > after about 30 min so there is still a difficulty in logging the reboot > event > which seems to be happening once every ~ 1-5 days. > > Is there any chance that we'll be seeing the utility software (hpasmd, > hpacucli, hpadu) compiled for freebsd 7 any time soon? > > > There is a different thermal shutdown feature of all ProLiants -- when > the > > server/cpu reaches a "temp deadly" setting, the box will immediately shut > > down. This feature has saved many ProLiant servers during computer room > > cooling failures over weekends when no one was around... Other servers > > burned up during those events... > > Thanks again, > -- > Barry Friedman > Emax Computer Systems Inc., 480 Tweedsmuir Ave., Ottawa, Ont. Canada K1Z > 5N9 > bfriedman@emax.ca Phone: (613) 725-3198 Fax: 725-0298 > From friedman at www1.emax.ca Tue Aug 19 15:31:41 2008 From: friedman at www1.emax.ca (Barry Friedman) Date: Tue Aug 19 15:31:47 2008 Subject: HP Proliant DL380G4 FreeBSD 7.0 spontaneous reboots [SOLVED] Message-ID: <20080819153139.GA66736@emax.ca> I thought it might interest others to know what caused this problem. The machine was shipped by truck ~1000 miles and apparently vibration was the culprit. Once all software problems were ruled out, the machine was taken apart and all removable components were re-seated. The system immediately became stable and has been running ever since. Thanks go to the HP Proliant/linux support group out of Costa Rica for their assistance as well as everyone here who provided advice. Regards, -- Barry Friedman Emax Computer Systems Inc., 480 Tweedsmuir Ave., Ottawa, Ont. Canada K1Z 5N9 From news.letter at zolnetwork.com Tue Aug 19 18:33:06 2008 From: news.letter at zolnetwork.com (Akira Norimaki) Date: Tue Aug 19 18:33:13 2008 Subject: Boot problem in HP Proliant ML370 G4 Message-ID: <48AB11DD.1010305@zolnetwork.com> I have a very annoying problem when booting FreeBSD-7.0 - but I have tried the 6.2 too - in my HP Proliant ML370 G4. When "-" appears on the screen at the start of the boot process, just after the boot manager have done its work, the process stops untill the enter key is pressed. After that the keyboard is unavilable till the prompt is showed. If any other key is pressed before the enter the keyboard stops working. Any advice to resolve this problem? Ref: http://lists.freebsd.org/pipermail/freebsd-stable/2006-April/024209.html Bye Akira From sutter.cane at rx78.org Tue Aug 19 18:41:40 2008 From: sutter.cane at rx78.org (Akira Norimaki) Date: Tue Aug 19 18:41:47 2008 Subject: Boot problem in HP Proliant ML370 G4 Message-ID: <48AB10A5.2010304@rx78.org> I have a very annoying problem when booting FreeBSD-7.0 - but I have tried the 6.2 too - in my HP Proliant ML370 G4. When "-" appears on the screen at the start of the boot process, just after the boot manager have done its work, the process stops untill the enter key is pressed. After that the keyboard is unavilable till the prompt is showed. If any other key is pressed before the enter the keyboard stops working. Any advice to resolve this problem? Ref: http://lists.freebsd.org/pipermail/freebsd-stable/2006-April/024209.html Bye Akira From news.letter at zolnetwork.com Tue Aug 19 19:00:12 2008 From: news.letter at zolnetwork.com (Akira Norimaki) Date: Tue Aug 19 19:00:22 2008 Subject: Boot problem in HP Proliant ML370 G4 In-Reply-To: <48AB11DD.1010305@zolnetwork.com> References: <48AB11DD.1010305@zolnetwork.com> Message-ID: <48AB1838.4010204@zolnetwork.com> Akira Norimaki ha scritto: Ops. I'm sorry for the double post. From sutter.cane at rx78.org Wed Aug 20 06:27:13 2008 From: sutter.cane at rx78.org (Akira Norimaki) Date: Wed Aug 20 06:27:19 2008 Subject: Boot problem in HP Proliant ML370 G4 In-Reply-To: <48AB11DD.1010305@zolnetwork.com> References: <48AB11DD.1010305@zolnetwork.com> Message-ID: <48ABB93D.9030501@rx78.org> Akira Norimaki ha scritto: > Any advice to resolve this problem? If you add -n option to /boot.config file you can solve the problem. -n ignore key press to interrupt boot before loader(8) is invoked. (thanks to Ganbold) Bye, Akira From fproliant at ccstores.com Fri Aug 29 04:09:14 2008 From: fproliant at ccstores.com (Jim Pazarena) Date: Fri Aug 29 04:09:20 2008 Subject: DL185 G5 Message-ID: <48B7727E.8080206@ccstores.com> I am considering purchasing an HP ProLiant DL185 Generation 5 (G5). with 8 SAS drives, and running in a combination Raid-1 mirror (2 drives) and Raid-6 "ADG" (6 drives) I was hoping that someone could comment on experiences with this particular hardware and configuration? Thx Jim