MySpace


Chris



Last Updated: 12/5/2006

Send Message
Instant Message
Email to a Friend
Subscribe

Gender: Male
Status: Married
Age: 35
Sign: Sagittarius

Country: CA
Signup Date: 12/4/2006

Who Gives Kudos:


February 22, 2007 - Thursday 

During my training I found out why for iSCSI you need to have a Service Console connection and a VMKernel connection.  Apparently, the Authentication occurs over the service console port and the actual iSCSI communication happens on the VMKernel port.

Also, there is multipathing available on the iSCSI Software Initiator on the ESX 3.0.1 server.  However, it looks like it doesn't work that well on the Netapp.  I think this is because of Netapp's Active Passive clustering, but I'll dig into that more when I get done with Training.

The one thing that struct me during training was a general lack of hands on experience with ESX, and companies treading very lightly into it.  I guess I'm just fortunate that a couple of years ago we were mandated that ESX was the way to go and that we do everything we could to make it work.

Many were scared but I thought it was great and I could see where management was coming from.  While the vision was not complete for a while, we saw the ease of disaster recovery, business resumption, and business continuity with this product.  All you needed to do was invest in the software that replicated your VMs from one site to another and because of the hardware abstraction, as long as the disk files were there, you could run the virtual machine.

In future posts I'll get more into the replication, fall over mechinisms and our implementation of Build Anywhere, Run Anywhere.  Its a good story and I look like a genius.  Just don't tell anyone how easy VMware and Netapp make it!

Cheers,

Chris

 

Peter

 

This one bit me in the b*tt the day before a co-worker told me about your blog.  I spent several hours on it because of the round about way I encountered it.

Normally, when you set up iSCSI, it complains/reminds you that you need a service console connection on the same net as the VMkernel.

In this case, different engineers had set up the servers.  They later added a back-end network for the iSCSI and NFS traffic.  They added the network settings for the VMkernel, and removed it from the front-end network.  Everything kept working.

Later, I came in to install a big pile of patches.  I waited until after the last one to reboot, since with ~12 patches that want to reboot, at ~5 min per reboot, that's an hour I didn't have to spare.  After the reboot, 9 of the 10 VMs went away.  Oh, cr@p. Which patch broke it?  None of them had much to do with iSCSI.  After many false directions, and noticing that NFS worked just dandy, but iSCSI wouldn't even show the target systems (and no iSCSI session/login on the storage), I decided to remove and recreate the iSCSI config.

Of course, it immediately complained about the lack of service console connection.

Fixed that, and all the VMs came back, and I went home.

Share and enjoy!

Peter

 


 
Posted by Peter on March 5, 2007 - Monday - 4:55 AM
[Reply to this