March 2009

You are currently browsing the monthly archive for March 2009.

I’ve been seeing lots of announcements regarding Cisco’s Unified Computing System (UCS) across the Internet. Here are just a few:

Cisco unveils its virtualization-friendly blade platform Unified Computing System
Cisco and VMware teaming up: Unified Computing System
Cisco Announces Unified Computing System
Cisco Brothers/Sisters congratulations!
Cisco: Unified Computing is an ‘Inflection Point’
Cisco’s Unified Computing System – A Whole New Ballgame
Cisco Enters the Virtual Server Hardware Market – Gestalt IT

I’ve been under strict NDA, as have many others, regarding what was formerly called “Project California,” since early December. Even though the NDA is now lifted and I could speak about UCS in more detail, I’m going to reserve the bulk of my comments after the conclusion of Cisco’s live webcast at 10:30AM Pacific Time (1:30PM Eastern Time).

Tags: , ,

Now that the veil appears to have been lifted on discussing features and functionality in the next-generation of ESX/ESXi, I thought I’d start out with a brief how-to on enabling Cisco Discovery Protocol (CDP) on ESX/ESXi, both with vNetwork Standard Switches (vSwitches) and vNetwork Distributed Switches (dvSwitches).

Let’s start out with an easy one: enabling CDP on ESX for a vSwitch. There is no GUI for enabling or disabling CDP for a vSwitch (yet), so it’s off to the CLI. You’ve probably seen this command before:

esxcfg-vswitch --set-cdp both vSwitch0

Replace the italicized parts of that command with the appropriate information for your environment. That sets CDP to both listen (receive CDP transmissions) and announce (send CDP transmissions). I recommend using both, although I have not currently found a way to explore the CDP information that ESX is gathering by listening to announcements. If anyone has any information there, I’d love to hear it.

The next one is a bit harder: enabling CDP on ESXi for a vSwitch. Of course, since we are using ESXi there is no Service Console, so this time we’ll have to rely upon the next-generation equivalent of VIMA.

The command from next-gen VIMA looks like this:

vicfg-vswitch --server vcenter.domain.com -h esxi.domain.com -B both vSwitch0

Unless you’ve set some environment variables, you’ll be prompted for username and password. I substituted the “-h” for “-−vihost” and “-B” for “-−set-cdp”. Again, you’ll need to replace the italicized portions with the appropriate information for your environment. I did find that using IP addresses didn’t seem to work well; I had to use fully-qualified domain names instead. That’s probably just an oddity.

The last scenario is enabling CDP on a dvSwitch. The process for this is the same for both ESX and ESXi. You’ll need to use the next-generation VI Client for this, and then go to the Edit Settings screen for the dvSwitch. Once there select Advanced, and you’ll see the option to set the CDP behavior. Click Both from the drop-down list and you should be good to go.

There’s lots more networking goodness in here; stay tuned for more articles in the near future.

Tags: , , , ,

A couple of days ago I posed this question: is Sun preparing to take on Cisco? The question generated some interesting responses in the comments to the article.

Reader Bill had this to say:

How on earth would Cisco respond if Sun started introducing products with better performance, at a fraction of the price, built on high volume open source adoption?

As I responded, that’s the real $64,000 question, isn’t it? That’s the premise upon which this entire thing is built—that by using commodity hardware and open source components, Sun can produce high-quality, high-performing network equipment that they can sell for far less than Cisco.

Reader Ed, on the other hand, questioned the validity of this kind of move:

I would think that partnering with a Juniper or Foundry-type company and OEMing equipment from those companies would be a more prudent move than venturing on their own to create new network devices.

Normally, I would agree with Ed if we were talking about a company that was merely interested in entering a market in order to become a more complete supplier to their customers. That’s not Sun’s purpose. Sun’s purpose is, I think, to fundamentally change the nature of the networking hardware market. How successful they’ll be…well, that’s another question.

My original article also prompted a response elsewhere on the Internet. Christofer Hoff thought my use of the work “distracted” in describing Cisco and Project “California” wasn’t appropriate, and in one sense he’s correct—”California” is absolutely a natural evolution of Cisco’s products and technologies and it does make sense for them. As I pointed out to Hoff, though, being successful with this new solution (I can’t call it a server!) will take focus, and while Cisco is focused on “California” Sun has their opportunity.

And it looks like they are definitely going to take that opportunity:

As I’ve said before, general purpose microprocessors and operating systems are now fast enough to eliminate the need for special purpose devices. That means you can build a router out of a server – notice you cannot build a server out of a router, try as hard as you like. The same applies to storage devices.
 
To demonstrate this point, we now build our entire line of storage systems from general purpose server parts, including Solaris and ZFS, our open source file system. This allows us to innovate in software, where others have to build custom silicon or add cost. We are planning a similar line of networking platforms, based around the silicon and software you can already find in our portfolio.

The emphasis on that last sentence is mine, just to emphasize the clarity of where Sun is headed. Clearly, it is their intention to leverage OpenSolaris, Crossbow, ZFS, Solaris Zones, etc., to compete directly against Cisco. And Cisco appears to be their primary target, judging from this sentence:

That means you can build a router out of a server – notice you cannot build a server out of a router, try as hard as you like.

To me, that looks like a direct jab at “California”.

So, I guess the question of whether Sun is going to take on Cisco is settled. Hoff, get your popcorn!

Tags: , , , ,

BlueStripe Software, a company I’ve written about a couple of times and who is based in the Raleigh-Durham, NC, area, is launching FactFinder 2.0. I discussed the previous version, FactFinder 1.1, here; and have talked with the guys from BlueStripe on a number of occasions, including at VMworld 2008. I try not to just post press releases or other news information without also adding a little bit of extra information, analysis, or my own thoughts. I have seen FactFinder in action, and it does represent a different way of approaching performance and availability issues. It’s not necessarily a unique way, though, as there are other companies that also work from the application level. I’m confident they don’t use the same technology, but they are working from the application level.

One of the major new features in this new release of FactFinder is support for Red Hat Enterprise Linux, which allows FactFinder to bring the same application discovery and service-level awareness now to the Linux platform. Of course, FactFinder fully supports both physical and virtualized instances of both Windows and now Linux, and in fact describes their product as a great way to ensure successful P2V (physical-to-virtual) conversions—not just from a “Did the conversion work?” perspective, but more importantly from the perspective of, “Does the application still perform at the required levels?” It’s the applications people care about, after all.

The full press release is here.

Tags: , ,

A while back in Virtualization Short Take #25 I briefly mentioned Sun’s Crossbow network virtualization software, which brings new possibilities to the Solaris networking world. Not being a Solaris expert, it was hard for me at the time to really understand why Solaris fans were so excited about it; since then, though, I’ve come to understand that Crossbow brings to Solaris the same kind of full-blown virtual network interfaces and such that I use daily with VMware ESX. Now I’m beginning to understand why people are so thrilled!

In any case, an astute reader picked up on my mention of Crossbow and pointed me to this article by Jonathan Schwartz of Sun, and in particular this phrase:

You’re going to see an accelerating series of announcements over the coming year, from amplifying our open source storage offerings, to building out an equivalent portfolio of products in the networking space…

That seemingly innocuous mention was then coupled with this blog post and the result was this question: is Sun preparing to take on Cisco? Is Sun getting ready to try to use commodity hardware and open source software to penetrate the networking market in the same way that they are using commodity hardware and open source software to try to further penetrate the storage market with their open storage products (in particular, the 7000 series)?

It’s an interesting thought, to say the least. Going up against Cisco is a bold move, though, and I question Sun’s staying power in that sort of battle. Of course, with Cisco potentially distracted by the swirling rumors regarding the networking giant’s entry into the server market, now may be the best time to make this move.

Thoughts?

Tags: , , , , ,

Book Status Report

It’s been about a month since I signed an agreement with Wiley Publishing to write a virtualization-centered book. Since that time, it’s been full steam ahead. Things are going a bit more slowly than I would have liked, but I’ve still met all my deadlines (thus far!) so I can’t really complain. The group of people I’m working with at Wiley are a great group and I can already tell just how much help they will be in making sure that this book is a top-quality product.

I’m also excited that a technical editor has been selected for my book. A number of virtualization experts—including a couple of recently-christened vExperts—offered to serve as technical editor. All of them are more than qualified to write this book, even more so to be the technical editor! In the end, though, I’m pleased to announce that Rick Scherer of VMwareTips.com will be the technical editor for the book. Rick has a solid technical background and I’m confident we’ll work well together. To everyone else who offered to work with me on this project, thanks for offering and I’m hoping that we’ll get the opportunity to work together in the future.

If you’re a reader of VMwareTips.com, then, don’t be too dismayed if Rick’s excellent technical content slows down a bit over the next few weeks or months. It’s just because I’ve got him busy double-checking all my stuff!

Tags: ,

I’m Confused

I’m confused. I know, that’s not a terribly difficult thing to do some days. I saw this article on the Windows Server Division weblog about the Release Candidate of SP2 for Windows Server 2008 and Windows Vista and I asked myself, “Did I miss SP1 for Windows Server 2008? I don’t recall hearing about the release of SP1. I guess I should go download it.”

So I did a little bit of digging and found this article—now over a year old, so you can see clearly that I haven’t been paying attention—that states that Microsoft tagged the RTM (Release to Manufacturing) build of Windows Server 2008 as SP1. So, there won’t be an SP1 for Windows Server 2008, and instead Microsoft will jump directly to SP2.

Here’s the great part. Check out this quote from that same ZDnet article:

“(I)n retrospect i should just say its called (Windows Server 2008 SP1) so you don’t have to wait for SP1 for it to be right like people have before.”

Huh? Microsoft is now tagging RTM builds as SP1, and then telling customers that just because it’s marked SP1 it’s ready? What’s next? Are we going to start tagging beta builds as GA code? Good Lord, people…can we get back to some sort of product naming convention that makes sense and that we’re willing to actually follow?

Tags: ,

Newer entries »