Month: January 2015

HP ProLiant DL580 G5 — GOOD LORD HOW LOUD YOU ARE, Also: How to quiet down a DL580 G5

So these servers I got are insanely loud, and I can’t stress insanely enough. The fans don’t seem to spin down to any reasonable level even when nothing is stressed and the system as drawing a “paltry” 650w.

So since there’s no direct control of the fans, at least so far in my limited testing with FreeBSD which I’m unfamiliar with anyhow I decided to quiet things down the hardware way. I took each of the 6 120mmx120mmx38mm fan cages out with *65dB* fans rated at 150CFM and cut the power cables to the proprietary connector. There was no way to get a standard width fan in here easily, so I decided to try running each pair in series.

That didn’t go so well. The fans would spin up a bit and then spin all the way down, the server thought they were bad. 6 volts was not enough to keep them going.. so I decided to cheat another way. I cut the power wires to some of the remaining 4 and wired a few diodes in series (5 of the 6 fans have 2 diodes, one has 3). That should give me some voltage drop from the forward bias of the diodes, and it did! My system went from absurdly loud to manageable.

For the other server I’ll be trying 4 diodes in series to try to get a bit more Vdrop and a bit more manageable noise. So far, so good. The 1.5amp diodes aren’t quite enough for my 150CFM Deltas and managed to burn out. 4x 3 amp barrel diodes fit perfectly in the little cavity in the fan, but I don’t have any pictures to show of that at the moment unfortunately.

 

 

3 1.5amp Rectifier Diodes, Twisted Together

3 1.5amp Rectifier Diodes, Twisted Together

Step 1:

Twist the diodes together, anode to cathode (note the silver band), this will get us some voltage drop.

3 1.5amp Rectifier Diodes, Soldered

3 1.5amp Rectifier Diodes, Soldered

Step 2:

Solder these connections and clip the parts we just soldered, we just need the two ends. This step is basically the same for 4 diodes, you just cut one more twisted set.

Fan and cage separated

Fan and cage separated

Step 3:

If your fan has a cage, disassemble the fan from the cage. Mine had plastic push pins much like most cars do, after that it slipped right out as I spread it apart to take the custom connector out.

Diodes Placed on Fan, Tinned

Diodes Placed on Fan, Tinned

Step 4:

Place the diodes on the fan, you can use some super glue to hold them in the cavity if there is a cavity. Otherwise place them somewhere convenient. Tin the anode/cathode of the diode(s) and cut the main power wire to the fan. Tin those wires.

Diodes Wired To Fan

Diodes Wired To Fan

Step 5:

Solder the power wires. The incoming wire will be wired to the cathode, or to the diode with the band furthest away from the connection.

Assembled Fan

Assembled Fan

Step 6:

You should probably have used shrink wrap in Step 5 (doh!), use some electric tape to make sure the exposed power does not hit ground and short out. (Yes, I had this problem, even with the electric tape, and I had to do horrible things to get the fan going again since it uses an uncommon connector that I couldn’t just replace)

Servers!

I got a pair of HP Proliant DL580 G5s, old, but potentially good. I was looking for something to run the ZFS SAN setup (which will hereafter be referred to as Hermes), and perhaps another VM server. They were supposed to have 2 Xeon E7330 quad-core CPUs and 32GB of DDR2 RAM.

To my surprise when I booted them up, server one had:

  • 4x X7460 CPUs (Six-core, 2.66GHz 16MB L3, SSE4)
  • 128GB of RAM

The second also had 128GB of RAM, but 4 E7450 CPUs, also six-cores but at a slightly lower 2.4GHz clock speed and I believe less cache. Total score, a single X7460 is worth more on eBay than I paid for both servers, so I ordered some cheaper CPUs (you know — the cheapest I could find that would work in the socket) at around $6/ea and these will go on eBay to help fund my little lab.

Once the MSA70 comes in I’ll be moving all the SAN stuff off the old desktop it’s in now and onto Hermes.

Note: These things SUCK power. Like 650w sitting there doing nothing power usage. But hey.. 128GB of RAM. That’s a lot of ARC for my ZFS machine!

How My Network Broke Today (Part I of atleast a billion)

So today I went to spin up a new VM for development use. It wouldn’t get an IP address, I saw the DHCP request on the DHCP server, and saw an offer go out but it was never received.  I dug through, and it seemed like this was just happening on one VLAN since everything else was OK.

Did I mention everything else was already running?

Did I mention if I had a trap collector with an alarm board that I would know what had happened almost immediately and been able to pinpoint the issue before I even saw the effects?

No? Well, now I have.

Let’s just say that I spent over an hour digging, running tcpdump on various interfaces, then finally hit the switches. I noticed there was only one port in the port channel on the Dell 5224 access switch when there should have been two down to the distribution switch. Odd but I thought inconsequential (at the time).

I got into the Cisco switch and saw MAC flaps (TRAPPABLE) all over the place with Po2. Odd again. The Dell switch must be to blame, so I go back to it and shut the port that’s not in the LACP port channel but should be. Things improve. Have I mentioned that I’d unplugged that fiber a week ago and only recently got a new one to plug back in?

I spend some time trying to get both ports in the port channel to no avail. I finally look at the config and notice the VLAN allowed config is slightly off (one is missing from eth 1/23), so I shut both the ports on the Cisco side as Dell won’t let you change interface configs while it’s part of a port channel and this was just faster — I reset the eth 1/23 config to match eth 1/24, and voila both ports came up.

But things were even worse now, barely any MACs were seen in ‘show mac address-table’ on my 3550-12 from Po2. And they were all on VLAN 1. Ugh. I shut the interfaces again and reset some more of the configuration on the Dell switch. I pray. (I don’t really pray). I bring the interfaces back up and all is good. The VM gets its IP address and everything is right in the world.

I really hate the Dell configurations. If I hated this switch before it’d be an understatement, and it’s only given me more of a reason to want to smash it with a hammer today. It’s mainly due to me not being familiar with them, but their configs aren’t as intuitive as I’d like.

iSCSI Booting Win2012 Server WITHOUT an HBA (Intel I350-T2 / 82571 / 82574 etc)

Thankfully Intel cards have iSCSI initiators in their firmware, so I setup a ZFS volume to make my HTPC diskless to attempt to stress the file server a bit more and generally just play with things as I tend to do.

So I added some settings to my ISC DHCP daemon under my shared network stanza to pass IQN/server settings to the Intel I350 card (82574 etc would work equally well here):

shared-network "VLAN-451" {
 default-lease-time 720000;
 option domain-name "p2.iscsi.frankd.lab";
 option domain-name-servers ns.frankd.lab;
  subnet 172.17.2.128 netmask 255.255.255.128 {
  range 172.17.2.144 172.17.2.239;
 }
 host intel-htpc1 {
  hardware ethernet a0:36:9f:03:99:7c;
  filename "";
  option root-path "iscsi:172.17.2.130::::iqn.2014-12.lab.frankd:htpc1";
 }
}

Voila, the card came up, grabbed DHCP settings and immediately initiated a connection! Awesome, the first thing to go right so far!  I admit I briefly spent some time trying to get iPXE to work with the Realtek card, but I ran into issues and just decided to use something I had laying around to get up and running quicker. The onboard Realtek is now for regular network data only, I might get a single port Intel card since I don’t need MPIO to this machine.

I imaged Win2012 Server to a USB stick using Rufus and plugged it in, it saw the drive and installed to it. I can’t believe things are going so easy/well for once! Then the system reboots. And it mounts the volume. And the Windows logo comes up. Then an error message comes up saying it couldn’t boot. Right away I knew it wasn’t getting past the BIOS calls to the disk (which were taken care of by the Intel NIC), and some Googling came up with horrible answers until I found an IBM document saying a new Intel driver fixes the issue — in a very indirect way. They don’t specify what, but it apparently has something to do with the iBFT tables that are created for the handoff. So I downloaded the newest drivers, put them on the USB stick and I installed Windows 2012 Server AGAIN. This time I loaded the newest version of the network drivers off the USB stick before even partitioning the disk, though.

The machine rebooted..

 

And..

 

IT WORKED! I was up and running. I installed the User Experience stuff so I could get Netflix/Hulu up easy, downloaded nVidia drivers and am now getting my Steam games downloaded to the machine — although I could stream off my workstation/gaming PC. It can’t hurt to have more than one machine with them installed in case either one of them dies and I need to go blow some pixels up to relieve some stress though, right?

 

Getting My Real VM Server Back Online Part III: Storage, iSCSI, and Live Migrations

After some dubious network configurations (that I should have never configured incorrectly) I finally got multipath working to the main storage server. All of the multipath.conf examples I saw resulted in non-functional iSCSI MPIO, while having no multipath.conf left me with failover MPIO instead of interleaved/round-robin.

A large issue with trying to get MPIO configured was the fact that all the examples I found were either old (and scsi_id works slightly differently in Ubuntu 14.04) or just poor. Yes, I wound up using Ubuntu. Usually I use Slackware for EVERYTHING, but lately I’ve been trying to branch out. Most of the VMs run Fedora, “Pegasus” or VMSrv1 uses Fedora, “Titan” uses Ubuntu.

Before I did anything with multipath.conf (It’s empty on Ubuntu 14.04), I got this:

root@titan:/home/frankd# multipath -ll
1FREEBSD HTPC1-D1 dm-2 FREEBSD,CTLDISK
size=256G features='0' hwhandler='0' wp=rw
|-+- policy='round-robin 0' prio=1 status=active
| `- 13:0:0:0 sde 8:64 active ready running
`-+- policy='round-robin 0' prio=1 status=enabled
  `- 12:0:0:0 sdd 8:48 active ready running

Note the disks are both round-robin — with only one member each! This works for fail-over, but did nothing for performance. The only thing that wound up working for multipath.conf was this:

defaults {
 user_friendly_names yes
 polling_interval 3
 path_grouping_policy multibus
 path_checker readsector0
 path_selector "round-robin 0"
 features "0"
 no_path_retry 1
 rr_min_io 100
}

multipaths {
 multipath {
  wwid 1FREEBSD_HTPC1-D1
  alias testLun
 }
}

The wwid/alias doesn’t work, however. All of the MPIO is just coming from the defaults stanza. I attempted many things with no luck, unfortunately. I’m going to have to delve into this more especially if I want live migrations to work properly with MPIO. As it stands the disk devices are pointing at a single IP (ex /dev/disk/by-path/ip-172.17.2.2:3260-iscsi-iqn.2014-12.lab.frankd:htpc1-lun-0), I’ll need to point at aliases to get the VMs working with multipath.

The multipath tests themselves were promising though, dd was able to give me a whopping 230MB/s to the mapper device over a pair of GigE connections.

The output from ‘multipath -ll’ now looked more reasonable:

root@titan:/home/frankd# multipath -ll
mpath1 (1FREEBSD HTPC1-D1) dm-2 FREEBSD,CTLDISK
size=256G features='1 queue_if_no_path' hwhandler='0' wp=rw
`-+- policy='round-robin 0' prio=1 status=active
  |- 39:0:0:0 sde 8:64 active ready running
  `- 40:0:0:0 sdg 8:96 active ready running

You can see the drives are both under the same round-robin policy instead of two separate ones.

The storage server also saw some slight changes, including upgrading from one Intel X25-V 40GB for L2ARC to 2xX25-Vs for a total of 80GB. I also added a 60GB Vertex 2 as a SZIL device. I really need to build a machine with more RAM and partition out the SZIL. I’ll likely wind up using my 840Pro 256GB for L2ARC and leave the old X25Vs out of the main array once I get a pair of 10GbE cards for maximum speed (hopefully near-native of the 840Pro — perhaps better with a large amount of ARC) to my workstation.

So we’re at a point where everything appears to be working, although in need of some upgrades! Great! I’m looking at a KCMA-D8 Dual Opteron C32 motherboard as I have a pair of Opteron 4184s (6 core Lisbon, very similar to a Phenom II X6 1055T) laying around, so I could put together a 32GB 12 core machine for under $400 — but as always, budgetary constraints for a hobby squash that idea quickly.