Darn You Networking! You've Foiled Me Once Again! (Emotions Expressed by Homer Simpson)

Hi Friends,

First and foremost, thank you to the great Matt Groening for bringing us The Simpsons!  All images borrowed from Google.

From my title you can see I'm having a moment with my network.  Not the switching our routing, but general "networking" concepts.  The things so simple we, or at least *I*, overlook....

If you've been following my blog you know I've been running performance numbers in my VMware Horizon View 6 environment with Login VSI.  I got the environment working well with 100, but it was time to increase the number of desktops.  It's always a challenge when you start increasing the number, not because the products are bad or anything, but because of all the darn little moving parts!!!






In a testing environment you're deleting, creating, re-creating, deleting, etc. the zombies start coming out everywhere!  So every so often you've got to go medieval on their butts, get out the fire hose and just pressure wash the environment.








So after one of these power washes I re-created all of my desktops, upped the count to 400 and kicked off a Login VSI run.  The Basephase started and 2 of the 5 sessions kicked off.   Hmmm, weird....  I rebooted all of the desktops and the launchers, and still, 2 of the 5 kicked off...  Think Neil, THINK!


I took a look at the desktops that were running and sure enough, 2 were happily running the workload, but 3 were just sitting there at the Windows 7 desktop...

I started searching Google and found some cases on the Login VSI site that were similar to mine, but the customer's couldn't get anything to launch.  My problem was I could get some of them to launch.  Lousy rotten intermittent problems!!


Hmmm, what could it be?!?!  I logged onto one of the machines that didn't kick off the workload and did and nslookup of my share machine.  Yep, that works....  I then did a ping and no ping....  Then it hit me!  My DHCP environment is larger then a Class C BUT my share machine is set to 255.255.255.0.  I changed my netmask to a Class B or 255.255.0.0 and my client machines outside of the Class C could now ping the share machine!!




So sometimes the smallest things can REALLY throw a wrench in the gears.

Until Next Time!
-Brain