jump to navigation

Virtual Center on 5.1 won’t start after upgrade September 26, 2012

Posted by vbry21 in VMware blogs.
Tags:
add a comment

Hi all, I’ve been playing with vSphere 5.1 now for a few weeks and all in all it’s a fine product.

On my daily visit to VMware’s website I came across a couple of knowledge base articles which may be of some use to all.

In some situations, after installing or upgrading to vCenter Server 5.1, the vCenter Service fails to start up.

In some situations vSphere Replication 5.1 (VR) cannot recover protected virtual machines.

VMware and EMC have identified two issues with PowerPath/VE 5.7 and VMware vSphere 5.1.

To be fair all software at some point has issues, but this goes to prove that the majority admit the issue and fix it fast.

 

What’s new in vSphere 5.1 part 8 September 25, 2012

Posted by vbry21 in Uncategorized.
Tags:
add a comment

Auto Deploy was introduced in VMware vSphere 5.0. vSphere Auto Deploy facilitates the rapid provisioning of vSphere hosts by leveraging the network boot capabilities of x86 servers together with the small footprint of the ESXi hypervisor.

Once installed a vCenter host profile is used to configure the host.  After configuration the host is connected to vCenter where it is available to host virtual machines.   The entire process is fully automated allowing new hosts to be quickly provisioned with no manual intervention.

However if we lost the Autodeploy server we lost the ability to boot our hosts

In vSphere 5.1, autodeploy supports:

Stateless or diskless caching host deployments lets you continue operation if the Auto Deploy server becomes unreachable. This was the only mode of install available in vSphere 5.0.

Stateless Caching caches the image when you apply the host profile. When you later reboot, the host continues to use the Auto Deploy infrastructure to retrieve its image. If the Auto Deploy server is not available, the host uses the cached image.

Stateful or disk-backed install:  Lets you obtain the master image from the Auto Deploy Server to quickly and easily install a new host. When you reboot the host, the host boots from disk, just like a host that was provisioned with the installer. Auto Deploy no longer provisions the host.

What’s new in vSphere 5.1 part 7 September 25, 2012

Posted by vbry21 in Uncategorized.
Tags:
add a comment

One of the courses I teach is Site Recovery Manager 5.0, within the course we install, configure and manage vSphere replication; this allows us to replicate and then migrate or failover VMs from our production to our recovery sites without the need of specialist SANs.

Good news is that we now get this functionality natively within VMware vSphere 5.1. With this technology, a virtual machine is replicated by components of the hypervisor, removing any dependency on the underlying storage, and without the need for storage-level replication.

VMs can be replicated between any type of storage platform for example you can replicate between VMFS and NFS or from iSCSI to local disk.  Because vSphere replication works above the storage layer it can replicated independently of the file systems.

Replication is controlled as a property of the VM itself and its VMDKs, eliminating the need to configure storage any differently or to impose constraints on storage layout or management.  If the VM is changed or migrated then the policy for replication will follow the VM.

vSphere replication creates a “shadow VM” at the recovery side, then populates the VM’s data through replication of changed data. This is not however Fault tolerance.

What’s new in vSphere 5.1 part 6 September 25, 2012

Posted by vbry21 in Uncategorized.
Tags:
add a comment

As a Hyper-V trainer and a VMware trainer I look at both products, and one of the nice features of Hyper-V in Windows Server 2012 is the live migration without shared storage, and this led to many questions about “Why don’t VMware have that?” As I’d signed my NDA with VMware I simply said, that at the moment we can’t do this, but now with VMware vSphere 5.1, I can say we do.

Enhanced vMotion enables a VM to change its datastore and host simultaneously, even if the two hosts don’t have any shared storage in common.

Another way of looking at this functionality is supporting VMotion without shared storage.  To use this enhanced functionality the hosts must be connected to the same VMware vCenter and be part of the same datacentre object.  Also the hosts must be on the same layer-2 network.

This vMotion enhancement ensures, zero downtime migration, no dependency on shared storage, and lower operating cost as a SAN is no longer required (but I’d still have one, I really like High Availability).

What’s new in vSphere 5.1 part 5 September 25, 2012

Posted by vbry21 in VMware blogs.
Tags:
add a comment

In VMware vSphere 5.1 we get a more advanced version of the distributed virtual switch. The new features enable us to manage our virtual switch infrastructure with greater efficiency and management enhancements.

Rollback and recovery addresses the challenges that we faced when management network failure caused the Hosts to disconnect from the vCenter Server.

The management network is configured on every host and is used to communicate with VMware vCenter as well as to interact with other host during vSphere HA configuration. This is important when it comes to centrally managing hosts through vCenter Server. If the management network on the host goes down or there is a misconfiguration, VMware vCenter can’t connect to the host and thus can’t centrally manage resources.

The Automatic rollback and recovery feature of vSphere 5.1 addresses all the concerns that customers have regarding the use of management network on a distributed virtual switch. This feature automatically detects any configuration changes on the management network and if the host can’t reach the vCenter Server, it doesn’t allow the changes to take effect by rolling back to previous valid configuration.

The rollbacks are of two types:

Host networking rollbacks: It occur when an invalid change is made to the host networking configuration. Every network change that disconnects a host also triggers a rollback.

Distributed switch rollbacks: It occur when invalid updates are made to distributed switch-related objects, such as distributed switches, distributed port groups, or distributed ports.

What’s new in vSphere 5.1 part 4 September 25, 2012

Posted by vbry21 in VMware blogs.
Tags:
add a comment

In VMware vSphere 5.1 we get a more advanced version of the distributed virtual switch. The new features enable us to manage our virtual switch infrastructure with greater efficiency and management enhancements.

Configuration Backup Restore – Allows vSphere admins to store the distributed virtual switch configuration as well as recover the network from the old configurations.

Export and Restore features of the enhanced distributed switch provides you with a way to create backups for network settings at the virtual data switch level or at the portgroup level and save the data anywhere.  This feature lets you recreate network configuration seamlessly, giving you a means of restoring full functionality in instances of network settings failures or VMware vCenter database corruption.

Using the Back Up and Restore feature of the enhanced distributed switch you can:

Export network configuration backup virtual data switch and portgroup configuration asynchronously on a disk.

Restore network configurations, which implies that you can restore virtual data switch and portgroup from a backup. Administrators can now save the distributed virtual switch configurations and use it to restore the exact same distributed virtual switch setup after any failure or in any new environment. Network admins can also build a revision control system distributed virtual switch configuration by saving configurations after each change with meta-data and use this to restore to any older configuration

By importing the backed up configuration you can also create new entity from the backup. Saved distributed virtual switch configuration can be used as template to create similar other distributed virtual switch in any virtual center.

Rollback and recovery – Addresses the challenges that we faced when management network failure caused the Hosts to disconnect from the vCenter Server.

 

 

I’ve booked my VCAP5-DCA September 25, 2012

Posted by vbry21 in VCAP5-DCA.
Tags:
add a comment

I qualified as a VCAP-DCA version 4 last year and as a VCI, the lovely people at VMware have provided me with a voucher to sit my VCAP-DCA version 5 exam, so I’ve decided that I’ll book the exam and start preparing for it.

My first step was to register for the exam via the Pearson VUE website

Then I booked my exam.

Now comes the hard part. Prepare for the exam on top of all the other things I need to do.

VMware recommend two courses for helping to prepare for the exam, luckily I teach both.

The first is the VMware 5.0 Install Configure and Manage

The second is the VMware 5.0 Optimise and Scale

Also if you wish you could use the VMware 5.0 Fast Track instead of the Install Configure and Manage.

Also you must already have passed the VCP5-DV Certification

As I’m preparing I’ll post Blogs in order to track my progress and share any information I find.

 

I’ve made the list as a blogger for VMworld 2012 Barcelona September 21, 2012

Posted by vbry21 in Uncategorized, VMware Training.
Tags:
2 comments

Super short blog this one.

I’ve made the list for a VMworld 2012 Barcelona blogger, so lookout for some VMworld 2012 blogs appearing within the next couple of weeks.

If you’re there and you see me say hello, we Geordies (Newcastle people) are friendly people, also I noticed that David Owen of vmackem (Sunderland people) is on the list, so the Northeast of England have two reps at VMworld.

What’s new in vSphere 5.1 part 3 September 16, 2012

Posted by vbry21 in VMware blogs.
Tags:
add a comment

In VMware vSphere 5.1 we get a more advanced version of the distributed switch. The new features enable us to manage our virtual switch infrastructure with greater efficiency and management enhancements.

Network Health Check support – helps detect misconfigurations across physical and virtual switches.

In a lot of companies the network team and the virtualisation team are separate and this may mean the virtualisation team may not be able to verify whether the physical setup is capable of deploying virtual machines correctly and debugging of simple issues can be frustrating for virtualisation administrators. With network Health check, available on ESXi 5.1 distributed switches and later, this feature assures proper physical and virtual operation by providing health monitoring for physical network setups including VLAN, MTU or Teaming. This feature gives administrators a window into the operation of your physical and virtual network. Virtualisation administrators also can provide failure data to the Network admins to facilitate speedy resolution.

Network Health Check feature prevents the common configuration errors:

Mismatched VLAN trunks between virtual switch and physical switch

Mismatched MTU setting between vNIC, virtual switch, physical adapter, and physical switch ports.

Mismatched Teaming Configurations.

 

It’s time to start looking at IPv6 September 16, 2012

Posted by vbry21 in General Stuff.
add a comment

 

We’ve been told for a few years now that the IP v4 pool of addresses was becoming dangerously depleted.

I was reading an article today that near enough says they are now gone in Europe.

On 14 September Ripe NCC got down to its last 16 million IPv4 addresses. While this might sound a lot, but it’s not and any new applicants will only get about 1000 addresses.

Immediately prior to reaching the last big block Ripe was handing out just under four million IPv4 addresses every 10 days.

So based on the maths above we’re out of addresses in 40 days.

To read the article I read, visit the link on the BBC website