RE: HP DL360-P4 slow network writes
Hi Kent, I think it's the Broadcom-switch connection. You said you changed switches - but I'm betting you just swapped in another Foundry. We have had trouble with the Broadcom gig E adapters under WinXP and certain switches. Try swapping in a 3com or some such. And certainly also try the system on a 100BaseT port as well. My guess is it's in how the Foundry is setting up the ethernet connection. My other guess is that the system timing/BIOS setups are different. I haven't yet seen the BIOS for a 360-G3 or G4 so I don't know that the settings I'm thinking of are even adjustable. But, look for something to do with the PCI bus timing I don't know what HP would name it. Also, check the BIOS version on your older decent 360's and the newer ones and see if you can try flashing an old one to the same BIOS rev as a new one, then see if the old one gets slow. Ted -Original Message- From: Kent Ketell [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 31, 2005 11:17 PM To: Ted Mittelstaedt Cc: freebsd-questions@freebsd.org Subject: Re: HP DL360-P4 slow network writes On Tue, May 31, 2005 at 10:35:00PM -0700, Ted Mittelstaedt wrote: Hey Kent, You need to remove Windows and install FreeBSD on those! Oh, your already running FreeBSD? I didn't see a version or dmesg output. I have tried 4.10-RELEASE-p5 and 4.11-STABLE as of last week. The app I'm testing with is cvs, since that's what is impacting the guys the most. Traceroute also shows rediculous times: traceroute to ? (172.17.56.15), 64 hops max, 44 byte packets 1 ? (172.17.56.15) 7.025 ms 0.122 ms 0.212 ms That traceroute is out a gig port directly to a NetAPP across a Foundry Gig switch. 7.025 ms is not right. The following is from the 4.11-STABLE system Here is the dmesg.boot info: Copyright (c) 1992-2005 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.11-STABLE #0: Fri May 27 09:18:57 PDT 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/bbuild31 Timecounter i8254 frequency 1193182 Hz CPU: Intel(R) Xeon(TM) CPU 3.60GHz (3600.15-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf41 Stepping = 1 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP, MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE ,SSE2,SS,HTT,TM,PBE Hyperthreading: 2 logical CPUs real memory = 2147430400 (2097100K bytes) avail memory = 2087751680 (2038820K bytes) Changing APIC ID for IO APIC #1 from 0 to 9 on chip Programming 24 pins in IOAPIC #0 IOAPIC #0 intpin 2 - irq 0 Programming 24 pins in IOAPIC #1 Programming 24 pins in IOAPIC #2 Programming 24 pins in IOAPIC #3 FreeBSD/SMP: Multiprocessor motherboard: 4 CPUs cpu0 (BSP): apic id: 0, version: 0x00050014, at 0xfee0 cpu1 (AP): apic id: 1, version: 0x00050014, at 0xfee0 cpu2 (AP): apic id: 6, version: 0x00050014, at 0xfee0 cpu3 (AP): apic id: 7, version: 0x00050014, at 0xfee0 io0 (APIC): apic id: 8, version: 0x00178020, at 0xfec0 io1 (APIC): apic id: 9, version: 0x00178020, at 0xfec1 io2 (APIC): apic id: 10, version: 0x00178020, at 0xfec82000 io3 (APIC): apic id: 11, version: 0x00178020, at 0xfec82400 Preloaded elf kernel kernel at 0xc03b7000. Warning: Pentium 4 CPU: PSE disabled Pentium Pro MTRR support enabled md0: Malloc disk npx0: math processor on motherboard npx0: INT 16 interface pcib0: Host to PCI bridge on motherboard IOAPIC #0 intpin 16 - irq 2 IOAPIC #0 intpin 18 - irq 16 pci0: PCI bus on pcib0 pcib1: PCI to PCI bridge (vendor=8086 device=3595) irq 2 at device 2.0 on pci0 pci13: PCI bus on pcib1 pcib2: PCI to PCI bridge (vendor=8086 device=3597) irq 2 at device 4.0 on pci0 pci6: PCI bus on pcib2 pcib3: PCI to PCI bridge (vendor=8086 device=0329) at device 0.0 on pci6 pci7: PCI bus on pcib3 pcib4: PCI to PCI bridge (vendor=8086 device=032a) at device 0.2 on pci6 pci10: PCI bus on pcib4 pcib5: PCI to PCI bridge (vendor=8086 device=3599) irq 2 at device 6.0 on pci0 pci3: PCI bus on pcib5 pcib6: PCI to PCI bridge (vendor=8086 device=25ae) at device 28.0 on pci0 IOAPIC #1 intpin 0 - irq 17 IOAPIC #1 intpin 1 - irq 18 IOAPIC #1 intpin 2 - irq 19 pci2: PCI bus on pcib6 ciss0: HP Smart Array 6i port 0x4000-0x40ff mem 0xfdf8-0xfdfb,0xfdff-0xfdff1fff irq 17 at device 1.0 on pci2 bge0: Broadcom BCM5704C Dual Gigabit Ethernet, ASIC rev. 0x2100 mem 0xfdf7-0xfdf7 irq 18 at device 2.0 on pci2 bge0: Ethernet address: 00:12:79:8f:1d:10 miibus0: MII bus on bge0 brgphy0: BCM5704 10/100/1000baseTX PHY on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge1: Broadcom BCM5704C Dual Gigabit Ethernet, ASIC rev. 0x2100 mem 0xfdf6-0xfdf6 irq 19 at device 2.1 on pci2 bge1: Ethernet address: 00:12:79:8f:1d:0f miibus1: MII bus on bge1 brgphy1: BCM5704 10/100/1000baseTX PHY on miibus1 brgphy1: 10baseT, 10baseT
RE: HP DL360-P4 slow network writes
--On 01 June 2005 00:37 -0700 Ted Mittelstaedt [EMAIL PROTECTED] wrote: Hi Kent, I think it's the Broadcom-switch connection. You said you changed switches - but I'm betting you just swapped in another Foundry. We have had trouble with the Broadcom gig E adapters under WinXP and certain switches. Try swapping in a 3com or some such. And certainly also try the system on a 100BaseT port as well. FWIW - we've got a bunch of the DL360 G4's and found a very nasty problem with the way the onboard Broadcom reacted to our HP switches - by default we forced the NIC's to 100Mbit/FDX. This resulted in a system that could send 'small' packets fine (e.g. dns) - but bogged down on anything large [it'd work, but not fun getting about 6k/sec for some transfers). After fiddling with the switch ports, putting the NIC's back to 'auto-select' fixed it - which is ironic, as we have a bunch of Intel Pro1000's that need exactly the opposite to work properly [i.e. we _have_ to lock them at 100/FDX to work with the switches]. I love 'standards' :) -Karl ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HP DL360-P4 slow network writes
On Tuesday 31 May 2005 16:34, the author Kent Ketell contributed to the dialogue on- HP DL360-P4 slow network writes: Hi, I have been using HP DL360-G3 and G4 servers for various tasks and have found that latest batch to have a problem with network writes being VERY slow. Reads are fine. Local reads/writes are fine. It's just network writes that are hurting me. I have tried installing Intel server NICs in the systems with no difference. I have tried going to different switches with no difference. I have tried changing the Cat5 cables with no differences. I installed RedHat on the same exact box and did not have the same slow write speeds. Does anybody have any thoughts on this? Thanks in advance. Well having just solved what I thought was a weird problem using ncftp which IO eventually tracked down to a dns problem - can I with little solid justication suggest you carefully check out your dns servers -- see which one are working really well and whether you have any unexpected delays. Its the only thing I can think of off the top of my head David -Kent- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- 40 yrs navigating and computing in blue waters. English Owner Captain of British Registered 60' bluewater Ketch S/V Taurus. Currently in San Diego, CA. Sailing May/June bound for Europe via Panama Canal. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HP DL360-P4 slow network writes
On Tuesday 31 May 2005 16:42, the author Kent Ketell contributed to the dialogue on- Re: HP DL360-P4 slow network writes: On Tue, May 31, 2005 at 04:35:03PM -0700, Vizion wrote: On Tuesday 31 May 2005 16:34, the author Kent Ketell contributed to the dialogue on- HP DL360-P4 slow network writes: Well having just solved what I thought was a weird problem using ncftp which IO eventually tracked down to a dns problem - can I with little solid justication suggest you carefully check out your dns servers -- see which one are working really well and whether you have any unexpected delays. Its the only thing I can think of off the top of my head Would this not also impact the RedHat as well? Well depends upon what order your dns servers are in the list - if you happened to have a duff dns being accessed first on yr freebsd box it might slow stuff down - if you can be certain they were in the same order on the redhat that would rule out dns as a cause. However I have usually not paid too much attention to what order they appear..now I will :-) David - -- 40 yrs navigating and computing in blue waters. English Owner Captain of British Registered 60' bluewater Ketch S/V Taurus. Currently in San Diego, CA. Sailing May/June bound for Europe via Panama Canal. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HP DL360-P4 slow network writes
On Tuesday 31 May 2005 19:12, the author Kent Ketell contributed to the dialogue on- Re: HP DL360-P4 slow network writes: On Tue, May 31, 2005 at 04:44:52PM -0700, Vizion wrote: On Tuesday 31 May 2005 16:42, the author Kent Ketell contributed to the dialogue on- Re: HP DL360-P4 slow network writes: Well depends upon what order your dns servers are in the list - if you happened to have a duff dns being accessed first on yr freebsd box it might slow stuff down - if you can be certain they were in the same order on the redhat that would rule out dns as a cause. However I have usually not paid too much attention to what order they appear..now I will :-) I guess I should mention that the tests I have been running involve doing a check-out of a branch from cvs. When I do the check-out to my nfs-mounted home dir it takes at least 90-seconds. When I do the same operation on a local filesystem (like /tmp) it takes only 5-seconds. Both operations make use of the same DNS servers, so that seems like a rather unlikely issue to me. Thoughts? I have verified that the resolv.conf entries for both the RedHat system and the FreeBSD system are the same. I initially discovered the problem when running 4.10-RELEASE-p5 and have since bumped the same system up to 4.11-STABLE as of last week. I am thinking this must be some odd change made by HP on their system that FreeBSD can't deal with, but I have not a clue as to what it might be. OK this is not much to go but lets see if you can puick up this very looose ball and run with it. I happen to have what is now a pretty old proliant in one of my server rooms. Now when I installed freebsd on that system (about 4/5 years ago) I have a vague memory of having to do something to the bios to make freebsd run properly. There may be some notes on HP's web site (my experience has been they are good for reference) perhaps you mmight find something by sculling around on HP's website -- look for operating system trouble shooting guides under support and your product ID DL360. If I remeber correctly I had to get a Proliant essential foundation pack to get the machine set up correctly. That is the only thing I can think of right now -- you seem to have effectively ruled out the dns issue. So now we are looking at hardware or freebsd's own configuration. I am sorry I cannot be of more help David -- 40 yrs navigating and computing in blue waters. English Owner Captain of British Registered 60' bluewater Ketch S/V Taurus. Currently in San Diego, CA. Sailing May/June bound for Europe via Panama Canal. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: HP DL360-P4 slow network writes
Hey Kent, You need to remove Windows and install FreeBSD on those! Oh, your already running FreeBSD? I didn't see a version or dmesg output. Like in car parts, they don't sell you the air filter unless you give them the make, model and year!!! Ted (PS, it might also help to know what kind of app are you using to make the writes with. We are good, but nobody here reads minds, that I know of.) -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Kent Ketell Sent: Tuesday, May 31, 2005 4:34 PM To: freebsd-questions@freebsd.org Subject: HP DL360-P4 slow network writes Hi, I have been using HP DL360-G3 and G4 servers for various tasks and have found that latest batch to have a problem with network writes being VERY slow. Reads are fine. Local reads/writes are fine. It's just network writes that are hurting me. I have tried installing Intel server NICs in the systems with no difference. I have tried going to different switches with no difference. I have tried changing the Cat5 cables with no differences. I installed RedHat on the same exact box and did not have the same slow write speeds. Does anybody have any thoughts on this? Thanks in advance. -Kent- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
