• Skip to primary navigation
  • Skip to main content
  • Skip to primary sidebar

Yellow Bricks

by Duncan Epping

  • Home
  • Unexplored Territory Podcast
  • HA Deepdive
  • ESXTOP
  • Stickers/Shirts
  • Privacy Policy
  • About
  • Show Search
Hide Search

ha

VMware’s first announcements.

Duncan Epping · Sep 15, 2008 ·

Here it is, VMware’s first announcement this week:

A Virtual Datacenter Operating System is characterized by hardware and location independent applications, service level contracts between the infrastructure and applications and a shared, dynamic infrastructure.

vCenter provides comprehensive management of applications and infrastructure in this flexible, fluid environment and integrates with leading systems management vendors for seamless, end to end datacenter management.

VMware Infrastructure delivers the virtual datacenter OS through the following essential components:

  • Application vServices guarantee the appropriate levels of availability, security and scalability to all applications independent of hardware and location.
  • Infrastructure vServices subtract, aggregate and allocate on-premise servers, storage and network for maximum infrastructure efficiency.
  • Cloud vServices federate the on-premise infrastructure with third party cloud infrastructure.
  • Management vServices allow you to proactively manage the virtual datacenter OS and the applications running on it.

I guess everybody was to tired yesterday or still amazed by the Virtual DataCenter that they forgot to blog about the following, which is atleast as important and spectacular as the above,  cause these new features will(2009) be the backbone for the VDC-OS:

  1. Synchronization and a single-console view of inventory, configuration, roles and permissions between multiple vCenter instances with vCenter Linked Mode.
    So no more maintaining and configuring several VC’s, just link ’em up!
  2. Monitoring and automated remediation of VMware ESX physical host configurations for compliance with standard baseline profiles.
    This is the future, real plug and play, define your ESX host once and just roll it out! I’m starting to see the big picture with ESXi… no more installing at all, just plug it in!
  3. Paravirtualized storage device enables over 200,000 i/o operations per second.
    High i/o servers? No problem…
  4. Distributed Switch simplifies the setup and change of virtual machine networking.
    A single point of administration for your vSwitches, or should I say dSwitches in this case…
  5. Network VMotion enables network statistics and history to travel with a virtual machine as it moves from host to host for better monitoring and security.
  6. Third party virtual switches plug into virtual networks and deliver value added network monitoring, security and QoS.
    So this would be that Cisco vSwitch that everybody was talking about these last couple of days?
  7. VMware Fault Tolerance, a groundbreaking new product provides zero downtime, zero data loss and availability to all applications against x86 hardware failures without the cost and complexity of hardware or software clustering solutions.
    No more need for any  other way of clustering, zero data loss, no more down time!
  8. vStorage Thin Provisioning enables users to reduce storage required for virtual environments by up to 50% by allocating storage only as required while providing the reporting and alerting capabilities needed to track actual usage.
    Besides power, rack space and cooling, save on storage as well!
  9. vStorage Linked Clones reduce the storage required for virtual machines by sharing common OS images while still retaining user specific profile and application data.
    Think about rapid deploying a 1000 VDI desktops… and saving on disk space.
  10. Virtual machines increase in size from 4 way to 8 way SMP, from 64 GB to 256GB of RAM, enabling even the largest, most resource intensive applications to run on  VMware.
  11. Hot add of virtual CPU, memory and network devices enables applications to scale seamlessly without disruption or downtime.
    No more downtime.
  12. vCenter Data Recovery provides quick, simple and cost effective backup and recovery for all applications through:
    Agentless disk based back up and recovery of virtual machines, Incremental backups and dedupe to save disk space, vCenter – integrated virtual machine level or file level restore.
    Doing backups and restores from the same console you are already used to, VirtualCenter!
  13. vApp turns new and existing applications into self-describing and self-managing entities. vApp leverages OVF, an open industry standard, to specify and encapsulate all components of a multi-tier application as well as the operational policies and service levels associated with it. Just like the UPC bar code contains all information about a product, the vApp gives application owners a standard way to describe operational policies for an application which the Virtual Datacenter OS can automatically interpret and execute.

What more can I say than “WOW”! Oh, and another thing… it seems like there’s a rebranding going on: vCenter, vStorage, vApp, vServices.

So with ESXi, host profiles and dSwitches there’s no need to spend a lot of time on configuring. Figure it out once, and just apply it to the rest of the hosts! With hot add CPU, MEM, Networkand with VMotion and Fault Tolerance there’s no need for down time any more. And I’m not even talking about doing backups and restores from within your vCenter and all the cool new storage related features…

Read more @ Scott Lowe, PCWorld, ComputerWorld, VMETC.Com, VMware.

HA, primary and secondary nodes?

Duncan Epping · Sep 9, 2008 ·

Because I’ve been looking into HA myself I wanted to clarify things up, for you guys and for myself… writing is a good way of getting the facts straight. I’ve seen and get a lot of questions regarding HA. So I just bundled a bunch of questions I received over the last couple of months…

How does a primary and / or secondary get selected?

  • The first 5 hosts that join the VMware HA cluster are automatically selected as “primary nodes”
  • All the others are automatically selected as “secondary nodes”
  • When you do a reconfigure for HA the primary nodes and secondary nodes are selected again, this is random

What’s up with these primaries and secondaries?

  • Primary nodes hold cluster settings and all node states which are synced between primaries
  • Secondary nodes send their state info(resource occupation) to the primary nodes
  • Nodes send heartbeats to each other, primary nodes send heartbeats to primary nodes only and secondary also only to primary. And they do this every second. (Which is a changeable value: das.failuredetectioninterval)

So what if a primary node fails, will a secondary be promoted?

  • No, there will only be a new primary appointed when the failed one is removed from the cluster. A secondary will be promoted to primary at random.

But what if all my primary nodes fail?

  • This is an unaddressed issue, that’s the reason why you can only account for 4 host failures within a cluster! There needs to be at least one primary!

So when does the gateway come in play?

  • Actually the gateway, which is the default “isolation address”, will only be used when an isolation has occurred. So when the AAM client thinks it’s isolated it will check the isolation addresses.

So if anyone has a question just drop it here and I’ll try to answer it and update the above list…

FT_HOSTS, where is it in ESX 3.5 U2?

Duncan Epping · Sep 8, 2008 ·

This seems to be High Availability day! I was just testing my previous blog when I discovered a weird DNS or host file related error. So I opened up my console and typed “vi /etc/FT_HOSTS”. “vi” opened a blank file and reported back “new file”. What the heck, so I did a find and found that the FT_HOSTS file has been relocated to: /etc/opt/vmware/aam/. So if you’re looking for FT_HOSTS….

And for ESXi, you should be looking here “/var/run/vmware/aam/” by the way.

HA isolation response “shutdown guest”

Duncan Epping · Sep 8, 2008 ·

So if you’re like me, better safe than sorry… than you’ve probably set your ESX 3.5 U2 HA cluster to “shutdown VM” instead of “Power off VM” or “Leave VM powered on”. By now most of you probably already noticed that when an isolation occurs HA will allow the VM to shutdown clean within 5 minutes. When the 5 minutes are past HA will shutdown the VM’s no matter what.

But for some of you 5 minutes(300 seconds) might just not be long enough, or if you have an ultra fast environment 5 minutes might just be to damn long….

So what can you do to shorten or extent… It’s easy, open up you HA cluster settings and click on advanced options and add the following:

das.isolationShutdownTimeout – values in seconds, default is 300

I’ve also updated my HA advanced settings blog! If anyone has more advanced settings that aren’t on the list let me know!

Response on the DABCC VMware HA vs Citrix HA article

Duncan Epping · Sep 5, 2008 ·

I clearly don’t know much about Citrix version of HA, but I do know a thing or two about VMware’s version of HA.

The following are outtakes of the article over at DABCC:

VMware’s HA is heavily dependent on DNS or alternatively hosts entries being in place. The VMware implementation is based on the Legato Automated Availability Management (AAM), in fact some of us will recall that it used to place those logs into /opt/LGTOaam512/logs/ (since 3.5 this has been moved /opt/vmware/aam).

VMware’s HA uses the network to establish a heartbeat between all the ESX Hosts participating, So practically, what does this mean to the poor bloke who has to support the servers? If you network has a bit of a flap (personally I always blame the Network guysJ), your servers will implement an “isolation response”, the default server response will shut down your Virtual Machine to release the shared storage locks, this will allow the machine to be restarted on another host, this of course may not be desirable if the server is busy doing something, i.e. you may cause corruption or other issues with the Application/Database. In other words it won’t perform a clean shutdown. This is configurable such that you can keep the machines powered on, but this isn’t recommended in the case of NAS or iSCSI (as they are also network dependant) and you may end up with a split-brain situation.

There is now also experimental support for component level HA, i.e. if a Virtual Machine fails, then VMware will try to restart it.

  1. As of ESX 3.5 U2 High Availability doesn’t heavily lean on DNS anymore, it gets its hostname and ip info from VirtualCenter.
  2. ESX 3.5 U2 gives you the possibility to cleanly shutdown a VM in case of an isolation.
  3. Normally one would indeed provide it’s SC with redundancy, and preferably via two separate switches to avoid the problems you are describing.
  4. Virtual Machine High Availability isn’t experimental anymore as of ESX 3.5 U2.
  • « Go to Previous Page
  • Page 1
  • Interim pages omitted …
  • Page 48
  • Page 49
  • Page 50
  • Page 51
  • Page 52
  • Interim pages omitted …
  • Page 54
  • Go to Next Page »

Primary Sidebar

About the Author

Duncan Epping is a Chief Technologist and Distinguished Engineering Architect at Broadcom. Besides writing on Yellow-Bricks, Duncan is the co-author of the vSAN Deep Dive and the vSphere Clustering Deep Dive book series. Duncan is also the host of the Unexplored Territory Podcast.

Follow Us

  • X
  • Spotify
  • RSS Feed
  • LinkedIn

Recommended Book(s)

Advertisements




Copyright Yellow-Bricks.com © 2025 · Log in