In my previous blog I promised to publish my findings of implementing Native Hyper-V VLANs with HP NIC Teams created by HP Network Configuration Utility v10.10.0.x which was released in September.
First of all I must warn you not to think lightly if you have to reconfigure your existing BladeSystem and Hyper-V Cluster. I had the luxury to try this all out in a research environment. The only ones who might have wondered why their research VM’s were not available were our consultants, specialists and technicians. As a high availability / cluster MVP I can of course appreciate the requirement for uptime. With Live Migration this has been a very easy job and nobody had wondered until now why the research BladeSystem was up all the time.
Now if you consider reconfiguring your production systems, think twice. Design, Plan, Change! Of course this is how we should go about major changes like this.
If you don’t have the stuff to practice, then read this very carefully and plan for some downtime.
I have documented the steps in this document: