From owner-freebsd-proliant@FreeBSD.ORG Thu Sep 7 20:50:49 2006 Return-Path: X-Original-To: freebsd-proliant@freebsd.org Delivered-To: freebsd-proliant@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7700116A4DA; Thu, 7 Sep 2006 20:50:49 +0000 (UTC) (envelope-from jgrosch@juniper.net) Received: from borg.juniper.net (borg.juniper.net [207.17.137.119]) by mx1.FreeBSD.org (Postfix) with ESMTP id 171E143D53; Thu, 7 Sep 2006 20:50:49 +0000 (GMT) (envelope-from jgrosch@juniper.net) Received: from unknown (HELO alpha.jnpr.net) ([172.24.18.126]) by borg.juniper.net with ESMTP; 07 Sep 2006 13:48:50 -0700 X-IronPort-AV: i="4.08,226,1154934000"; d="scan'208"; a="586160668:sNHT28188292" Received: from [172.24.115.16] ([172.24.115.16]) by alpha.jnpr.net with Microsoft SMTPSVC(6.0.3790.1830); Thu, 7 Sep 2006 13:50:48 -0700 Message-ID: <45008628.2000007@juniper.net> Date: Thu, 07 Sep 2006 13:50:48 -0700 From: Josef Grosch Organization: Juniper Networks User-Agent: Thunderbird 1.5.0.4 (X11/20060613) MIME-Version: 1.0 To: freebsd-questions@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 07 Sep 2006 20:50:48.0566 (UTC) FILETIME=[4C336160:01C6D2BF] Cc: freebsd-proliant@freebsd.org, freebsd-hardware@freebsd.org Subject: DL 380/G5 with 16G of ram X-BeenThere: freebsd-proliant@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Technical discussion of FreeBSD on HP ProLiant server platforms." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Sep 2006 20:50:49 -0000 Hello, I've got a DL 380/G5 as an evalu unit. It has 16 gig of ram. I compiled a PAE kernel but I'm finding that it is not very stable. It crashes during heavy disk activity, ie. portupgrade -rav. Does anyone have experience with this sort of machine and would you care to share your kernel config file and/or advice. Thanks Josef -- FreeBSD 6.1 | Josef Grosch | You can't expect to wield supreme executive power jgrosch@juniper.net | just 'cause some watery tart threw a sword at you! From owner-freebsd-proliant@FreeBSD.ORG Thu Sep 7 21:26:02 2006 Return-Path: X-Original-To: freebsd-proliant@freebsd.org Delivered-To: freebsd-proliant@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D866016A4E0; Thu, 7 Sep 2006 21:26:02 +0000 (UTC) (envelope-from scrappy@hub.org) Received: from hub.org (hub.org [200.46.204.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id 480BD43D79; Thu, 7 Sep 2006 21:26:02 +0000 (GMT) (envelope-from scrappy@hub.org) Received: from localhost (mx1.hub.org [200.46.208.251]) by hub.org (Postfix) with ESMTP id 16205290C98; Thu, 7 Sep 2006 18:25:58 -0300 (ADT) Received: from hub.org ([200.46.204.220]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 06031-08; Thu, 7 Sep 2006 18:26:00 -0300 (ADT) Received: from ganymede.hub.org (blk-137-86-60.eastlink.ca [24.137.86.60]) by hub.org (Postfix) with ESMTP id 62481290C6D; Thu, 7 Sep 2006 18:25:57 -0300 (ADT) Received: by ganymede.hub.org (Postfix, from userid 1000) id D91505DC5E; Thu, 7 Sep 2006 18:26:00 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id D81785D75B; Thu, 7 Sep 2006 18:26:00 -0300 (ADT) Date: Thu, 7 Sep 2006 18:26:00 -0300 (ADT) From: "Marc G. Fournier" To: Josef Grosch In-Reply-To: <45008628.2000007@juniper.net> Message-ID: <20060907182533.D64655@ganymede.hub.org> References: <45008628.2000007@juniper.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-proliant@freebsd.org, freebsd-questions@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: DL 380/G5 with 16G of ram X-BeenThere: freebsd-proliant@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Technical discussion of FreeBSD on HP ProLiant server platforms." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Sep 2006 21:26:03 -0000 On Thu, 7 Sep 2006, Josef Grosch wrote: > > Hello, > > I've got a DL 380/G5 as an evalu unit. It has 16 gig of ram. I compiled > a PAE kernel but I'm finding that it is not very stable. It crashes > during heavy disk activity, ie. portupgrade -rav. Does anyone have > experience with this sort of machine and would you care to share your > kernel config file and/or advice. Have you tried a non-PAE kernel? If its a new unit, I imagine its 64bit, which, as far as I'm aware, doesn't require PAE ... ? ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . scrappy@hub.org MSN . scrappy@hub.org Yahoo . yscrappy Skype: hub.org ICQ . 7615664 From owner-freebsd-proliant@FreeBSD.ORG Thu Sep 7 21:45:13 2006 Return-Path: X-Original-To: freebsd-proliant@freebsd.org Delivered-To: freebsd-proliant@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A814F16A4E5; Thu, 7 Sep 2006 21:45:13 +0000 (UTC) (envelope-from bmiele@ipnstock.com) Received: from shanty.ipnstock.com (static-71-241-222-63.port.east.verizon.net [71.241.222.63]) by mx1.FreeBSD.org (Postfix) with ESMTP id 40A3C43D7D; Thu, 7 Sep 2006 21:45:01 +0000 (GMT) (envelope-from bmiele@ipnstock.com) Received: from shanty.ipnstock.com (localhost [127.0.0.1]) by shanty.ipnstock.com (8.13.4/8.13.4) with ESMTP id k87LixZq079351; Thu, 7 Sep 2006 17:44:59 -0400 (EDT) (envelope-from bmiele@ipnstock.com) Received: from localhost (brad@localhost) by shanty.ipnstock.com (8.13.4/8.13.3/Submit) with ESMTP id k87LiusX079348; Thu, 7 Sep 2006 17:44:59 -0400 (EDT) (envelope-from bmiele@ipnstock.com) X-Authentication-Warning: shanty.ipnstock.com: brad owned process doing -bs Date: Thu, 7 Sep 2006 17:44:56 -0400 (EDT) From: Brad Miele X-X-Sender: brad@shanty.ipnstock.com To: "Marc G. Fournier" In-Reply-To: <20060907182533.D64655@ganymede.hub.org> Message-ID: <20060907173812.E2717@shanty.ipnstock.com> References: <45008628.2000007@juniper.net> <20060907182533.D64655@ganymede.hub.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-hardware@freebsd.org, freebsd-proliant@freebsd.org, freebsd-questions@freebsd.org Subject: Re: DL 380/G5 with 16G of ram X-BeenThere: freebsd-proliant@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Technical discussion of FreeBSD on HP ProLiant server platforms." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Sep 2006 21:45:14 -0000 I have 2 new dl380/G5s which threw the Memory above 4G ignored errors unless i used a PAE kernel. my kernel config is below, the machine has been up and has had no trouble with portupgrade/buildworld, etc. but it is not in production yet either and i have not put a ton of stress on it. I have 6G ram, so not nearly as much. fwiw, here is my conf. I pretty much rolled the PAE config into my custom conf. The custom conf has as much as I possible could lose stripped out. machine i386 cpu I686_CPU ident MYBOXYO # To make an SMP kernel, the next line is needed options SMP # Symmetric MultiProcessor Kernel # To make a PAE kernel, the next option is needed options PAE # Physical Address Extensions Kernel # for apache2 options ACCEPT_FILTER_HTTP # Compile acpi in statically since the module isn't built properly. Most # machines which support large amounts of memory require acpi. device acpi # Don't build modules with this kernel config, since they are not built with # the correct options headers. makeoptions NO_MODULES=yes # What follows is a list of drivers that are normally in GENERIC, but either # don't work or are untested with PAE. Be very careful before enabling any # of these drivers. Drivers which use DMA and don't handle 64 bit physical # address properly may cause data corruption when used in a machine with more # than 4 gigabytes of memory. nodevice ahb nodevice amd nodevice sym nodevice trm nodevice adv nodevice adw nodevice aha nodevice aic nodevice bt nodevice ncv nodevice nsp nodevice stg nodevice asr nodevice dpt nodevice mly nodevice hptmv nodevice ida nodevice mlx nodevice pst nodevice agp nodevice de nodevice txp nodevice vx nodevice nve nodevice pcn nodevice sf nodevice sis nodevice ste nodevice tl nodevice tx nodevice vr nodevice wb nodevice cs nodevice ed nodevice ex nodevice ep nodevice fe nodevice ie nodevice lnc nodevice sn nodevice xe nodevice wlan nodevice wlan_wep # 802.11 WEP support nodevice wlan_ccmp # 802.11 CCMP support nodevice wlan_tkip # 802.11 TKIP support nodevice an nodevice ath # Atheros pci/cardbus NIC's nodevice ath_hal # Atheros HAL (Hardware Access Layer) nodevice ath_rate_sample # SampleRate tx rate control for ath nodevice awi nodevice ral nodevice wi nodevice uhci nodevice ohci nodevice ehci nodevice usb nodevice ugen nodevice uhid nodevice ukbd nodevice ulpt nodevice umass nodevice ums nodevice ural nodevice urio nodevice uscanner nodevice aue nodevice axe nodevice cdce nodevice cue nodevice kue nodevice rue ##### makeoptions DEBUG=-g # Build kernel with gdb(1) debug symbols #options SCHED_ULE # ULE scheduler options SCHED_4BSD # 4BSD scheduler options PREEMPTION # Enable kernel thread preemption options INET # InterNETworking #options INET6 # IPv6 communications protocols options FFS # Berkeley Fast Filesystem options SOFTUPDATES # Enable FFS soft updates support options UFS_ACL # Support for access control lists options UFS_DIRHASH # Improve performance on big directories options MD_ROOT # MD is a potential root device options NFSCLIENT # Network Filesystem Client options NFSSERVER # Network Filesystem Server options NFS_ROOT # NFS usable as /, requires NFSCLIENT options MSDOSFS # MSDOS Filesystem options CD9660 # ISO 9660 Filesystem options PROCFS # Process filesystem (requires PSEUDOFS) options PSEUDOFS # Pseudo-filesystem framework options GEOM_GPT # GUID Partition Tables. options COMPAT_43 # Compatible with BSD 4.3 [KEEP THIS!] options COMPAT_FREEBSD4 # Compatible with FreeBSD4 options COMPAT_FREEBSD5 # Compatible with FreeBSD5 options SCSI_DELAY=5000 # Delay (in ms) before probing SCSI options KTRACE # ktrace(1) support options SYSVSHM # SYSV-style shared memory options SYSVMSG # SYSV-style message queues options SYSVSEM # SYSV-style semaphores options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time extensions options KBD_INSTALL_CDEV # install a CDEV entry in /dev options ADAPTIVE_GIANT # Giant mutex is adaptive. device apic # I/O APIC # Bus support. device eisa device pci # Floppy drives device fdc # ATA and ATAPI devices device ata device atapicd # ATAPI CDROM drives device atapifd # ATAPI floppy drives options ATA_STATIC_ID # Static device numbering # SCSI Controllers #device aha # Adaptec 154x SCSI adapters #device aic # Adaptec 15[012]x SCSI adapters, AIC-6[23]60. # SCSI peripherals device scbus # SCSI bus (required for SCSI) device ch # SCSI media changers device da # Direct Access (disks) device sa # Sequential Access (tape etc) device cd # CD device pass # Passthrough device (direct SCSI access) device ses # SCSI Environmental Services (and SAF-TE) # RAID controllers interfaced to the SCSI subsystem device ciss # Compaq Smart RAID 5* # RAID controllers # device ida # Compaq Smart RAID # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc # AT keyboard controller device atkbd # AT keyboard device psm # PS/2 mouse device kbdmux # keyboard multiplexer device vga # VGA video card driver device splash # Splash screen and screen saver support # syscons is the default console driver, resembling an SCO console device sc device agp # support several AGP chipsets # Power management support (see NOTES for more options) #device apm # Add suspend/resume support for the i8254. device pmtimer # Serial (COM) ports device sio # 8250, 16[45]50 based serial ports # Parallel port device ppc device ppbus # Parallel port bus (required) # PCI Ethernet NICs that use the common MII bus controller code. # NOTE: Be sure to keep the 'device miibus' line in order to use these NICs! device miibus # MII bus support device bge # Broadcom BCM570xx Gigabit Ethernet # Pseudo devices. device loop # Network loopback device random # Entropy device device ether # Ethernet support device sl # Kernel SLIP device ppp # Kernel PPP device tun # Packet tunnel. device pty # Pseudo-ttys (telnet etc) device md # Memory "disks" device gif # IPv6 and IPv4 tunneling device faith # IPv6-to-IPv4 relaying (translation) # The `bpf' device enables the Berkeley Packet Filter. # Be aware of the administrative consequences of enabling this! # Note that 'bpf' is required for DHCP. device bpf # Berkeley packet filter # USB support device usb # USB Bus (required) Brad --------------------- Brad Miele VP Technology IPNStock.com 866 476 7862 x902 bmiele@ipnstock.com On Thu, 7 Sep 2006, Marc G. Fournier wrote: > On Thu, 7 Sep 2006, Josef Grosch wrote: > >> >> Hello, >> >> I've got a DL 380/G5 as an evalu unit. It has 16 gig of ram. I compiled a >> PAE kernel but I'm finding that it is not very stable. It crashes during >> heavy disk activity, ie. portupgrade -rav. Does anyone have experience with >> this sort of machine and would you care to share your kernel config file >> and/or advice. > > Have you tried a non-PAE kernel? If its a new unit, I imagine its 64bit, > which, as far as I'm aware, doesn't require PAE ... ? > > ---- > Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) > Email . scrappy@hub.org MSN . scrappy@hub.org > Yahoo . yscrappy Skype: hub.org ICQ . 7615664 > _______________________________________________ > freebsd-proliant@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-proliant > To unsubscribe, send any mail to "freebsd-proliant-unsubscribe@freebsd.org" > > From owner-freebsd-proliant@FreeBSD.ORG Fri Sep 8 01:19:05 2006 Return-Path: X-Original-To: freebsd-proliant@freebsd.org Delivered-To: freebsd-proliant@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1E48F16A4DA; Fri, 8 Sep 2006 01:19:05 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7B91643D77; Fri, 8 Sep 2006 01:19:04 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id E1AAC1A3C1C; Thu, 7 Sep 2006 18:19:03 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id C921A5135C; Thu, 7 Sep 2006 21:19:01 -0400 (EDT) Date: Thu, 7 Sep 2006 21:19:01 -0400 From: Kris Kennaway To: Josef Grosch Message-ID: <20060908011901.GA37850@xor.obsecurity.org> References: <45008628.2000007@juniper.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="YiEDa0DAkWCtVeE4" Content-Disposition: inline In-Reply-To: <45008628.2000007@juniper.net> User-Agent: Mutt/1.4.2.2i Cc: freebsd-proliant@freebsd.org, freebsd-questions@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: DL 380/G5 with 16G of ram X-BeenThere: freebsd-proliant@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Technical discussion of FreeBSD on HP ProLiant server platforms." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Sep 2006 01:19:05 -0000 --YiEDa0DAkWCtVeE4 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Sep 07, 2006 at 01:50:48PM -0700, Josef Grosch wrote: >=20 > Hello, >=20 > I've got a DL 380/G5 as an evalu unit. It has 16 gig of ram. I compiled= =20 > a PAE kernel but I'm finding that it is not very stable. It crashes=20 > during heavy disk activity, ie. portupgrade -rav. Does anyone have=20 > experience with this sort of machine and would you care to share your=20 > kernel config file and/or advice. A good place to start looking would be at the disk driver; is it listed in the "PAE" kernel config? If not, it's probably known not to work. kris --YiEDa0DAkWCtVeE4 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFAMUFWry0BWjoQKURAtomAJ44vIMdJBycswbdasHSToNAjgIfnQCgiVtC H9HfBNDc0fI+TlP0JYIp2R4= =losI -----END PGP SIGNATURE----- --YiEDa0DAkWCtVeE4-- From owner-freebsd-proliant@FreeBSD.ORG Fri Sep 8 04:48:45 2006 Return-Path: X-Original-To: freebsd-proliant@freebsd.org Delivered-To: freebsd-proliant@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9FA0F16A4DA; Fri, 8 Sep 2006 04:48:45 +0000 (UTC) (envelope-from mv@thebeastie.org) Received: from p4.roq.com (ns1.ecoms.com [207.44.130.137]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3566443D49; Fri, 8 Sep 2006 04:48:43 +0000 (GMT) (envelope-from mv@thebeastie.org) Received: from p4.roq.com (localhost.roq.com [127.0.0.1]) by p4.roq.com (Postfix) with ESMTP id 835B74CD7A; Fri, 8 Sep 2006 04:50:30 +0000 (GMT) Received: from vaulte.jumbuck.com (ppp166-27.static.internode.on.net [150.101.166.27]) by p4.roq.com (Postfix) with ESMTP id AA2624CD6C; Fri, 8 Sep 2006 04:50:29 +0000 (GMT) Received: from vaulte.jumbuck.com (localhost [127.0.0.1]) by vaulte.jumbuck.com (Postfix) with ESMTP id 5748A8A01F; Fri, 8 Sep 2006 14:48:40 +1000 (EST) Received: from [192.168.46.102] (unknown [192.168.46.250]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by vaulte.jumbuck.com (Postfix) with ESMTP id 5206A8A00D; Fri, 8 Sep 2006 14:48:40 +1000 (EST) Message-ID: <4500F627.1040104@thebeastie.org> Date: Fri, 08 Sep 2006 14:48:39 +1000 From: Michael Vince User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.7.13) Gecko/20060727 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Josef Grosch References: <45008628.2000007@juniper.net> In-Reply-To: <45008628.2000007@juniper.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP X-Virus-Scanned: ClamAV using ClamSMTP Cc: freebsd-proliant@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: DL 380/G5 with 16G of ram X-BeenThere: freebsd-proliant@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Technical discussion of FreeBSD on HP ProLiant server platforms." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Sep 2006 04:48:45 -0000 Josef Grosch wrote: > > Hello, > > I've got a DL 380/G5 as an evalu unit. It has 16 gig of ram. I > compiled a PAE kernel but I'm finding that it is not very stable. It > crashes during heavy disk activity, ie. portupgrade -rav. Does anyone > have experience with this sort of machine and would you care to share > your kernel config file and/or advice. > > > Thanks > > Josef > Yeah I just got my first HP DL380 G5 with 8gigs of RAM with a total of 4 CPU cores, which is placed next to a bunch of Dells. I got a HP because I needed a new server fast and Dell claimed 4 weeks, I will give you my run down on whats happened with me. So far I am annoyed about many things, firstly at has no built in writeback battery on the 256mg SAS controller which means no write cache which is something you have to pay extra for from HP. In the Dells its built in, with 256mg battery backed writecache for guaranteed filesystem consistency on sudden power loss, write cache is important and is otherwise a waste of a good machine if you need top write performance, otherwise may as well get really low end stuff that has really simple controller cards like supermicro etc. Currently it took over 2 hours to build world, on Quad Xeon Core 2 I have been doing all this while being on the other side of the world. The other problem is the remote serial support via tip for reaching into the bios is quite stuffed, all the text garbles into a single line and is just to hard to read, I hacked the minicom port to use the USB to 9pin serial device to see if I could make it more like how people in linux would use it and it made little difference. It looks like HP were trying to have better remote serial bios support by going really basic command line style for remote BIOS control but its no good. The Dell bios is all nice and menu'ed and works flawlessly over remote serial, no garbledness overwriting other text. I gave up trying to do anything via the bios and aimed ta PXE remote install, this worked after a total of 5 hours. It kept dieing out during the install, I finally got it right once. Once I booted in a fresh FreeBSD 6.1-Release AMD64 install the 'bce' ether device kept dieing and timing out, looking back I have no idea how I managed to get a complete PXE remote install in the first place. I managed to cvsup and build a new kernel under 6-stable after about 15 reboots. After a new kernel its been quite stable, but I originally wanted to just stick with Release. There is no IPMI with HP even though it appears to be standard on most other x86 servers. On the new Dell they now have IPMI v2, and I can use a native FreeBSD IPMI client port for remote control. On HP it appears I have to pay for some kind of LO software, this might be the reason for useless uncontrollable remote 9pin serial for BIOS access. I gave a simple test on the bce with stable kernel compared to the Dells with the em nics and it compared quite well but still slower then the Dells. Also note all the Dells are 6.1-Release a lot of posts have come up lately saying the em is now even faster in stable compared to 6.1-Release since the new driver updates, but considering I am getting 97megs/sec via a simple nc test I don't think could/need to go faster. Em Dell to Em Dell dell1# cat /dev/zero | dd bs=1m | nc dell2 3000 ^C0+18456 records in 0+18455 records out 1209466880 bytes transferred in 12.459299 secs (97,073,429 bytes/sec) Bce HP to Em Dell HPDL380# cat /dev/zero | dd bs=1m | nc dell2 3000 ^C0+19648 records in 0+19648 records out 1287606272 bytes transferred in 13.926151 secs (92,459,594 bytes/sec) Mike From owner-freebsd-proliant@FreeBSD.ORG Fri Sep 8 16:11:47 2006 Return-Path: X-Original-To: freebsd-proliant@freebsd.org Delivered-To: freebsd-proliant@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C281716A4DE; Fri, 8 Sep 2006 16:11:47 +0000 (UTC) (envelope-from scrappy@hub.org) Received: from hub.org (hub.org [200.46.204.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id 17D5F43D4C; Fri, 8 Sep 2006 16:11:47 +0000 (GMT) (envelope-from scrappy@hub.org) Received: from localhost (mx1.hub.org [200.46.208.251]) by hub.org (Postfix) with ESMTP id 73C03291B0B; Fri, 8 Sep 2006 13:11:45 -0300 (ADT) Received: from hub.org ([200.46.204.220]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 09334-06; Fri, 8 Sep 2006 13:11:42 -0300 (ADT) Received: from ganymede.hub.org (blk-137-86-60.eastlink.ca [24.137.86.60]) by hub.org (Postfix) with ESMTP id 49A67291B0A; Fri, 8 Sep 2006 13:11:41 -0300 (ADT) Received: by ganymede.hub.org (Postfix, from userid 1000) id EDB2D60544; Fri, 8 Sep 2006 13:11:40 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id EC9F65E2F2; Fri, 8 Sep 2006 13:11:40 -0300 (ADT) Date: Fri, 8 Sep 2006 13:11:40 -0300 (ADT) From: "Marc G. Fournier" To: Michael Vince In-Reply-To: <4500F627.1040104@thebeastie.org> Message-ID: <20060908130444.V64655@ganymede.hub.org> References: <45008628.2000007@juniper.net> <4500F627.1040104@thebeastie.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-hardware@freebsd.org, freebsd-proliant@freebsd.org Subject: Re: DL 380/G5 with 16G of ram X-BeenThere: freebsd-proliant@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Technical discussion of FreeBSD on HP ProLiant server platforms." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Sep 2006 16:11:48 -0000 On Fri, 8 Sep 2006, Michael Vince wrote: > I got a HP because I needed a new server fast and Dell claimed 4 weeks, > I will give you my run down on whats happened with me. We're running 2xDL360 G4p's here, and so far, have been extremely happy with them ... third is about to be installed ... > So far I am annoyed about many things, firstly at has no built in writeback > battery on the 256mg SAS controller which means no write cache which is > something you have to pay extra for from HP. > In the Dells its built in, with 256mg battery backed writecache for > guaranteed filesystem consistency on sudden power loss, write cache is > important and is otherwise a waste of a good machine if you need top write > performance, otherwise may as well get really low end stuff that has really > simple controller cards like supermicro etc. 'k, can't easily comment on this, but I swear the base system that I bought had the battery included ... I don't recall ever having ordered it seperately, and do know that when I first power on, I get a 'battery error' while it charges up ... > Currently it took over 2 hours to build world, on Quad Xeon Core 2 Stupid question, but are all 4 CPUs working in the kernel? I'll have to test on the new server once its online, but I'm only workign with Dual Xeon, no Dual-Core yet ... > I have been doing all this while being on the other side of the world. > The other problem is the remote serial support via tip for reaching into the > bios is quite stuffed, all the text garbles into a single line and is just to > hard to read, I hacked the minicom port to use the USB to 9pin serial device > to see if I could make it more like how people in linux would use it and it > made little difference. > It looks like HP were trying to have better remote serial bios support by > going really basic command line style for remote BIOS control but its no > good. > The Dell bios is all nice and menu'ed and works flawlessly over remote > serial, no garbledness overwriting other text. Here, what is 'remote serial'? Is that the same as REMCONS through iLO over SSH? Again, will have to double check, as my other two machines are production right now, but my experience with iLO/REMCONS has been most pleasant, but, I also hook up two ethernet cables, I don't do the 'piggy backing' that I know is possible over one ... > I gave up trying to do anything via the bios and aimed ta PXE remote > install, this worked after a total of 5 hours. It kept dieing out during > the install, I finally got it right once. In my case, I put the server in a different room, no monitor or keyboard, CD in the drive, and did everything using REMCONS ... no problems ... > Once I booted in a fresh FreeBSD 6.1-Release AMD64 install the 'bce' > ether device kept dieing and timing out, looking back I have no idea how > I managed to get a complete PXE remote install in the first place. 'k, in my case, its a bge device for ethernet ... haven't had any problems with it so far *cross fingers* > There is no IPMI with HP even though it appears to be standard on most > other x86 servers. On the new Dell they now have IPMI v2, and I can use > a native FreeBSD IPMI client port for remote control. On HP it appears I > have to pay for some kind of LO software, this might be the reason for > useless uncontrollable remote 9pin serial for BIOS access. There are two levels of iLO ... the server (at least the ones we've been buying) come with the 'basic iLO" standard, and then there is an advanced one that we've never felt a desire / requirement for ... ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . scrappy@hub.org MSN . scrappy@hub.org Yahoo . yscrappy Skype: hub.org ICQ . 7615664 From owner-freebsd-proliant@FreeBSD.ORG Fri Sep 8 18:14:12 2006 Return-Path: X-Original-To: freebsd-proliant@freebsd.org Delivered-To: freebsd-proliant@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0BC8416A4EA for ; Fri, 8 Sep 2006 18:14:12 +0000 (UTC) (envelope-from jcagle@gmail.com) Received: from wr-out-0506.google.com (wr-out-0506.google.com [64.233.184.235]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6E35043DA5 for ; Fri, 8 Sep 2006 18:13:59 +0000 (GMT) (envelope-from jcagle@gmail.com) Received: by wr-out-0506.google.com with SMTP id 68so226623wri for ; Fri, 08 Sep 2006 11:13:58 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=AbrVlmnEUx1ZsOtmki20OJmrP3PBZ/aAczhT3aQ0yGzjXVEyhS42exrzmnKfXRz9DpXsmpdcIi3byZwLOCu9iHOp6A3pae8uQCWL7042IaGYRsaJvJnm4LYyVdrZalD68wmMoYahbZr1YvGwpX92QkW8MiWRNxJ2Jot6H8gZ4aU= Received: by 10.90.25.9 with SMTP id 9mr1013625agy; Fri, 08 Sep 2006 11:13:57 -0700 (PDT) Received: by 10.90.100.11 with HTTP; Fri, 8 Sep 2006 11:13:57 -0700 (PDT) Message-ID: <6863f0c90609081113l4fc19057m4857a1bc8719583b@mail.gmail.com> Date: Fri, 8 Sep 2006 13:13:57 -0500 From: jmc To: "Michael Vince" In-Reply-To: <4500F627.1040104@thebeastie.org> MIME-Version: 1.0 References: <45008628.2000007@juniper.net> <4500F627.1040104@thebeastie.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-proliant@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: DL 380/G5 with 16G of ram X-BeenThere: freebsd-proliant@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Technical discussion of FreeBSD on HP ProLiant server platforms." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Sep 2006 18:14:12 -0000 On 9/7/06, Michael Vince wrote: > > > I have been doing all this while being on the other side of the world. > The other problem is the remote serial support via tip for reaching into > the bios is quite stuffed, all the text garbles into a single line and > is just to hard to read, I hacked the minicom port to use the USB to > 9pin serial device to see if I could make it more like how people in > linux would use it and it made little difference. > It looks like HP were trying to have better remote serial bios support > by going really basic command line style for remote BIOS control but its > no good. > The Dell bios is all nice and menu'ed and works flawlessly over remote > serial, no garbledness overwriting other text. The BIOS Serial Console (BSC) support should work fine and give you a nice menu to configure the BIOS. The factory default for BSC is auto-detect, which means it checks for a terminal attached to the serial port before enabling it. The default terminal setting is VT100. This can be changed to ANSI in the BIOS setup screens. Have you tried using a different terminal emulator to make your connection to the BIOS? I prefer C-Kermit over minicom. I gave up trying to do anything via the bios and aimed ta PXE remote > install, this worked after a total of 5 hours. > It kept dieing out during the install, I finally got it right once. > > Once I booted in a fresh FreeBSD 6.1-Release AMD64 install the 'bce' > ether device kept dieing and timing out, looking back I have no idea how > I managed to get a complete PXE remote install in the first place. > > I managed to cvsup and build a new kernel under 6-stable after about 15 > reboots. > > After a new kernel its been quite stable, but I originally wanted to > just stick with Release. > > There is no IPMI with HP even though it appears to be standard on most > other x86 servers. On the new Dell they now have IPMI v2, and I can use > a native FreeBSD IPMI client port for remote control. On HP it appears I > have to pay for some kind of LO software, this might be the reason for > useless uncontrollable remote 9pin serial for BIOS access. Your server has a very powerful BMC called iLO. One key feature of iLO is its support for a Virtual Serial Port (VSP). This allows you to SSH into iLO and access a serial console (COM2 by default on the DL380). The BIOS config menu can change this to COM1 if you want to. Here is a link to a document showing how to utilize VSP. http://h20000.www2.hp.com/bc/docs/support/SupportManual/c00263709/c00263709.pdf iLO also gives you a SMASH compatible command line to manage the server. SMASH is a new DMTF standard alternative to IPMI. I gave a simple test on the bce with stable kernel compared to the Dells > with the em nics and it compared quite well but still slower then the > Dells. > Also note all the Dells are 6.1-Release a lot of posts have come up > lately saying the em is now even faster in stable compared to > 6.1-Release since the new driver updates, but considering I am getting > 97megs/sec via a simple nc test I don't think could/need to go faster. > > Em Dell to Em Dell > dell1# cat /dev/zero | dd bs=1m | nc dell2 3000 > ^C0+18456 records in > 0+18455 records out > 1209466880 bytes transferred in 12.459299 secs (97,073,429 bytes/sec) > > Bce HP to Em Dell > HPDL380# cat /dev/zero | dd bs=1m | nc dell2 3000 > ^C0+19648 records in > 0+19648 records out > 1287606272 bytes transferred in 13.926151 secs (92,459,594 bytes/sec) > > Mike > > _______________________________________________ > freebsd-proliant@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-proliant > To unsubscribe, send any mail to "freebsd-proliant-unsubscribe@freebsd.org > " > From owner-freebsd-proliant@FreeBSD.ORG Sat Sep 9 15:04:12 2006 Return-Path: X-Original-To: freebsd-proliant@freebsd.org Delivered-To: freebsd-proliant@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2387C16A403; Sat, 9 Sep 2006 15:04:12 +0000 (UTC) (envelope-from mv@thebeastie.org) Received: from p4.roq.com (ns1.ecoms.com [207.44.130.137]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5FB3B43D7D; Sat, 9 Sep 2006 15:04:03 +0000 (GMT) (envelope-from mv@thebeastie.org) Received: from p4.roq.com (localhost.roq.com [127.0.0.1]) by p4.roq.com (Postfix) with ESMTP id BEAE34CA4C; Sat, 9 Sep 2006 15:05:53 +0000 (GMT) Received: from [150.101.157.158] (ppp157-158.static.internode.on.net [150.101.157.158]) by p4.roq.com (Postfix) with ESMTP id 21B394CD4D; Sat, 9 Sep 2006 15:05:51 +0000 (GMT) Message-ID: <4502D7DF.5060302@thebeastie.org> Date: Sun, 10 Sep 2006 01:03:59 +1000 From: Michael Vince User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.13) Gecko/20060526 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Olaf Hoyer References: <45008628.2000007@juniper.net> <4500F627.1040104@thebeastie.org> <20060908130444.V64655@ganymede.hub.org> <20060909151636.A4598@sylvana.boldlygoingnowhere.org> In-Reply-To: <20060909151636.A4598@sylvana.boldlygoingnowhere.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Cc: freebsd-proliant@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: DL 380/G5 with 16G of ram X-BeenThere: freebsd-proliant@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Technical discussion of FreeBSD on HP ProLiant server platforms." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 09 Sep 2006 15:04:12 -0000 Olaf Hoyer wrote: > On Fri, 8 Sep 2006, Marc G. Fournier wrote: > >>> >>> It looks like HP were trying to have better remote serial bios >>> support by going really basic command line style for remote BIOS >>> control but its no good. >>> The Dell bios is all nice and menu'ed and works flawlessly over >>> remote serial, no garbledness overwriting other text. >> > > The HP boxes offer 2 ways of serial: traditional BIOS redirection at > 9600 bps through 9pin COM1, which you can set up in BIOS, I recall > that there are some options to it, like terminal type, ANSI or VT100. > Could that be an issue in your environment? > Yeah the terminal choice is probably it, I asked some one on the local side of the server to enable the serial bios via COM1 and when it would display a full screen and then just garble everything else at the bottom I asked him about 5 times to look for some kind of ANSI or VT100 terminal type option so I could have a chance of seeing whats really going on he said there was nothing, but now I am sure he just couldn't see it or just didn't care to look. I tried every terminal type I could on my side to help try make it display properly, but it just didn't work. Thanks for all the input. From owner-freebsd-proliant@FreeBSD.ORG Sat Sep 9 15:53:13 2006 Return-Path: X-Original-To: freebsd-proliant@freebsd.org Delivered-To: freebsd-proliant@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 798E516A415; Sat, 9 Sep 2006 15:53:13 +0000 (UTC) (envelope-from scrappy@hub.org) Received: from hub.org (hub.org [200.46.204.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id 026F743D45; Sat, 9 Sep 2006 15:53:12 +0000 (GMT) (envelope-from scrappy@hub.org) Received: from localhost (mx1.hub.org [200.46.208.251]) by hub.org (Postfix) with ESMTP id 9DCC7291AFC; Sat, 9 Sep 2006 12:53:11 -0300 (ADT) Received: from hub.org ([200.46.204.220]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 69314-08; Sat, 9 Sep 2006 12:53:11 -0300 (ADT) Received: from ganymede.hub.org (blk-137-86-60.eastlink.ca [24.137.86.60]) by hub.org (Postfix) with ESMTP id 72278290C74; Sat, 9 Sep 2006 12:53:10 -0300 (ADT) Received: by ganymede.hub.org (Postfix, from userid 1000) id 5379E3C10F; Sat, 9 Sep 2006 12:53:10 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id 4DB1D355DD; Sat, 9 Sep 2006 12:53:10 -0300 (ADT) Date: Sat, 9 Sep 2006 12:53:10 -0300 (ADT) From: "Marc G. Fournier" To: Michael Vince In-Reply-To: <4502D7DF.5060302@thebeastie.org> Message-ID: <20060909125246.I906@ganymede.hub.org> References: <45008628.2000007@juniper.net> <4500F627.1040104@thebeastie.org> <20060908130444.V64655@ganymede.hub.org> <20060909151636.A4598@sylvana.boldlygoingnowhere.org> <4502D7DF.5060302@thebeastie.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Olaf Hoyer , freebsd-proliant@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: DL 380/G5 with 16G of ram X-BeenThere: freebsd-proliant@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Technical discussion of FreeBSD on HP ProLiant server platforms." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 09 Sep 2006 15:53:13 -0000 We almost need a step-by-step guide to "configurating a Proliant server for remote access" :) On Sun, 10 Sep 2006, Michael Vince wrote: > Olaf Hoyer wrote: > >> On Fri, 8 Sep 2006, Marc G. Fournier wrote: >> >>>> >>>> It looks like HP were trying to have better remote serial bios support by >>>> going really basic command line style for remote BIOS control but its no >>>> good. >>>> The Dell bios is all nice and menu'ed and works flawlessly over remote >>>> serial, no garbledness overwriting other text. >>> >> >> The HP boxes offer 2 ways of serial: traditional BIOS redirection at 9600 >> bps through 9pin COM1, which you can set up in BIOS, I recall that there >> are some options to it, like terminal type, ANSI or VT100. Could that be an >> issue in your environment? >> > Yeah the terminal choice is probably it, I asked some one on the local side > of the server to enable the serial bios via COM1 and when it would display a > full screen and then just garble everything else at the bottom I asked him > about 5 times to look for some kind of ANSI or VT100 terminal type option so > I could have a chance of seeing whats really going on he said there was > nothing, but now I am sure he just couldn't see it or just didn't care to > look. > I tried every terminal type I could on my side to help try make it display > properly, but it just didn't work. > > Thanks for all the input. > > > > ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . scrappy@hub.org MSN . scrappy@hub.org Yahoo . yscrappy Skype: hub.org ICQ . 7615664