Don’t use the Microsoft iSCSI Software Initiator in a Virtual Machine

Lots of people regularly use the Microsoft iSCSI Software Initiator on physical machines to attach iSCSI LUNs from filers to hosts. This is an add on free download for Server 2003, and comes pre-installed on Server 2008.

 In general, on physical machines, it works fine.

So assuming that it’d work just fine on a virtual machine, we tried to use it on some production machines running Small Business Server 2003.  It seems to load just fine, and works like it usually does on a “real” machine – *BUT* it has terrible throughput under load.  It’ll even disconnect at random times.  Uninstalling/reinstalling, and lots of fiddling around didn’t help.

Of course, we went to Google to see if others have issues with it, and there’s *LOTS* of whining about this, both on VMware ESX and XenServer.

It’s possible that it has been addressed in Server 2008.  We saw this on 2003, and haven’t attempted to replicate the issue on 2008 vm’s.

Nonetheless, we suggest you figure out another way to attach iSCSI LUNs from a filer to a Windows virtual machine.  Both ESX and XenServer allow you to easily present iSCSI based disks to vm’s inside their virtualization environments.  Don’t do it with the Microsoft iSCSI Software Initiator from within the guest.

Filers? We don’t need no stinkin’ filers….

03-21-06_alfonso-bedoyaI know that it seems sometimes like adding filers to the mix may be extra complication, but it really does add a lot of value.  There’s good reasons that enterprise shops don’t do local storage.

Basically in ‘real’ businesses, they don’t buy servers with hard drives in them.  At all.  No drives at all.  They do everything on SAN.  Even boot from it. Read more

MCITP:EA – Took the Microsoft 070-647 Windows Server 2008, Enterprise Administrator exam again

I took 070-647 Windows Server 2008, Enterprise Administrator exam again today.  I didn’t pass again.  I got the exact same score, 653 out of 700.  Like I said in my previous post on 070-647, these MCITP:EA exams are some of the hardest exams I’ve ever taken.  I’ve taken a lot, from a lot of different vendors.

MCITP:EA – Passed the Microsoft 070-642 Windows Server 2008 Network Infrastructure, Configuring exam today

I took 070-642 today.  I passed!  Like I said before, these MCITP:EA exams are tough.  I have a lot of experience with TCP/IP on various operating systems, so this exam was a little easier for me.

Need inexpensive iSCSI? Try NexentaStor!

NexentaStor 3.0 Main Dashboard

NexentaStor 3.0 Main Dashboard

I’ve been using Openfiler for a long time now, but I’m always open to alternatives.  Recently I stumbled across NexentaStor, which is a software product you can load on your servers to make them into filers, like Openfiler.  NexentaStor is available both in an Community Edition, as well as a relatively inexpensive Enterprise Edition, which comes with all the bells and whistles like built in block level replication. Read more

MCITP:EA – Took the Microsoft 070-647 Windows Server 2008, Enterprise Administrator exam today

I try to keep my certifications fresh.  I am MCSA on Windows Server 2000.  I failed to upgrade to Windows Server 2003.  (There was a test for that, but it is no longer given.)  So I have to start all over.

The replacements for MCSA/MCSE are the “Microsoft Certified IT Professional” AKA MCITP.  The replacement for MCSA is MCITP: Server Administrator and the replacement for MCSE is MCITP: Enterprise Administrator.

The best thing one can do in my humble opinion is to actually use the product you’re taking the test on, and actually go to classroom training.  Unlike some vendors, Microsoft only offers training through third party vendors.  Most places have suitable training nearby.

Unfortunately, the classroom training is very expensive.  Most of these classes are 5 days (one week.)  The prices vary, but they run something like $500 per day, something like $2500 a week.  Plus travel, lodging, meals, etc.

I can’t afford that.

So I did the next best thing.

Read more

Adventures in Windows Time

“The only reason for time is so that everything doesn’t happen at once.”

At work, I have an integrated authentication system based on Windows Active Directory.  All clients, Linux, Unix, and Windows, use Active Directory for user names and passwords.  Active Directory is actually a good implementation of Kerberos.  It does pretty good LDAP as well.  I used some of Scott Lowe’s interoperability blog recipes to get this to work, namely this post for Linux, and this one for Solaris.

One requirement for a reliable Kerberos service is that every clock on every participating machine has to be synchronized.  By default Windows domain controllers act as Network Time Protocol (NTP) servers, and Windows clients know to sync with them.  We configure our Linux and Unix machines to use them as well.

There’s some issues with using Windows domain controllers as NTP servers…

Read more

Forget the Special Air Service, send in the Sysadmins!

From our friends at xkcd.

It’s my GNU truck

My GNU Truck

My GNU Truck

I got a new GNU truck during the Cash for Clunkers bonanza.  (GNU is one of the main organizations that built the tools we call Linux.)  It’s a 2009 Toyota Tacoma Prerunner.  It’s the first new car I’ve ever had, and I really like it. Read more

Add a XenServer storage repository on local disk

Most people use shared storage, like iSCSI, for their XenServer storage repositories to hold virtual machines.  Virtual machines *MUST* be in a shared storage repository in order to enable XenMotion and other advanced features.

It is handy to have some local storage repositories available, mainly to hold backups of machines.  For example, you could shutdown a running virtual machine, right click on it, select Copy, and select a local repository to hold the copy.  Then if you lost your iSCSI server, you’d have a local copy of the virtual machine you could start until the the iSCSI server became available again.

The XenCenter management GUI doesn’t allow you to make local storage repositories.  You have to use the command line.  Luckily, it’s pretty easy.  Here’s my updated XenServer wiki page on how to do this.