Latest Posts


Total Pageviews

Monday, 17 April 2017

VMware Enhanced Authentication Plug-in in vSphere 6.5

The VMware Enhanced Authentication Plug-in provides Integrated Windows Authentication and Windows-based smart card functionality.
In this vSphere 6.5 release, the VMware Enhanced Authentication Plug-in replaces the Client Integration Plug-in from vSphere 6.0 releases and earlier. The Enhanced Authentication Plug-in provides Integrated Windows Authentication and Windows-based smart card functionality, which are the only two features carried over from the previous Client Integration Plug-in. The Enhanced Authentication Plug-in can function seamlessly if you already have the Client Integration Plug-in installed on your system from a vSphere release prior to 6.5. There are no conflicts if both plug-ins are installed.
Install the plug-in only once to enable all the functionality the plug-in delivers.
If you install the plug-in from an Internet Explorer browser, you must first disable Protected Mode and enable pop-up windows on your Web browser. Internet Explorer identifies the plug-in as being on the Internet instead of on the local intranet. In such cases, the plug-in is not installed correctly because Protected Mode is enabled for the Internet.
If you use Microsoft Internet Explorer, disable Protected Mode.
Open a Web browser and type the URL for the vSphere Web Client.
At the bottom of the vSphere Web Client login page, click Download Enhanced Authentication Plug-in.
If the browser blocks the installation either by issuing certificate errors or by running a pop-up blocker, follow the Help instructions for your browser to resolve the problem.
Save the plug-in to your computer, and run the executable.
Step through the installation wizard for both the VMware Enhanced Authentication Plug-in and the VMware Plug-in Service which are run in succession.
When the installations are complete, refresh your browser.
On the External Protocol Request dialog, click Launch Application to run the Enhanced Authentication Plug-in.
The link to download the plug-in disappears from the login page.

VCP 6.5 Exam Open for Registration

Those who are interested in writing the VCP 6.5-DCV Exam, So here is the good news for them. It's open now for registration. First appointment is available from 24th April 2017 Onwards. VMware Site is just updated today evening with this information:-

1. Connect with Certification Portal :-
2. Click on Datacenter Virtualization Category
3. Click on VCP6.5-DCV Exam
4. Click on VMware Certified Professional 6.5 – Data Center Virtualization Exam.
5.  Review the Exam details. To book this, click on Register Now.

Sunday, 16 April 2017

Discontinuation of 3rd party vSwitch program (2149722)

VMware is announcing discontinuation of its third party virtual switch (vSwitch) program, and plans to deprecate the VMware vSphere APIs used by third party switches in the release following vSphere 6.5 Update 1. Subsequent vSphere versions will have the third party vSwitch APIs completely removed and third party vSwitches will no longer work.
This has no impact on existing use of 3rd party vSwitch on supported vSphere release. It also has no impact on support already purchased from VMware or the support lifecycle for the product. For more information on the end of support for this product, see the VMware Lifecycle Product Matrix
The 3rd party switch APIs will work and be supported up to vSphere 6.5 Update 1.
VMware recommends migrating from third party distributed vSwitches including Cisco Nexus 1000V, Cisco VM-FEX,  HPE 5900v and IBM DVS 5000v to vSphere Distributed Switch.
To assist in vSwitch migration, VMware offers a free migration tool for migrating from Nexus 1000v to VDS. In addition, VMware’s Professional Services Organization can provide services to customer to migrate from 3rd party vSwitch to VDS.
What is happening with VMware’s 3rd Party Virtual Switch Program?
VMware is discontinuing its third party virtual switch (vSwitch) program. VMware plans to deprecate the APIs in vSphere used by third party virtual switches in the future.
Why is VMware removing 3rd party vSwitch support from vSphere?
In line with how we’ve executed and delivered on our SDDC vision, we are now seeing customers converge on a networking standard.  The preferred model for virtual switching is to use the natively available virtual switch in the hypervisor and program it using APIs as required. VMware’s native virtual switch implementation has become the standard for greater than 99% of vSphere customers today. By using the native virtual switch to simplify the IT landscape by reducing upgrade times, streamline support, deploy new features more quickly, and prepare for the next wave of change agents.
When will the 3rd Party vSwitch APIs be removed from vSphere?
VMware expects to remove the APIs in the next update release after VMware vSphere 6.5 Update 1, as well as future releases of the vSphere platform.
What date specifically will this happen?
As policy, VMware does not provide specific dates for the release of future offerings.
What does this mean for customers currently running 3rd party vSwitches with VMware vSphere?
VMware customers using 3rd party vSwitches should begin planning a transition to VDS. VMware will continue to support the 3rd party virtual switch APIs and the enablement of a partner's use of these APIs, for vSphere 6.5 Update 1 and prior vSphere versions, as long as an active support and subscription services contract exists. After VMware vSphere 6.5 Update 1, VMware expects to remove the APIs as part of a future update to VMware vSphere 6.5 as well as future releases of the vSphere platform, and third party vSwitches will no longer work with vSphere.
What is VMware vSphere Distributed Switch?
VMware vSphere Distributed Switch (VMware VDS) is a native VMware virtual switch which was introduced in 2009. VDS provides centralized management of network configuration for multiple hosts in a cluster. In addition to centralized management, VDS provides rich features like NIOC, health monitoring of uplink, port mirroring, load-balancing of uplinks, back-up restore etc.
What 3rd party vSwitch offerings will no longer be supported on vSphere?
Third party vSwitches available for vSphere include Cisco Nexus 1000V, Cisco VM-FEX, , HPE 5900v and IBM DVS 5000v.
What about Cisco AVS, which is part of the Cisco ACI solution? Are you also discontinuing support for AVS?
VMware has never supported Cisco AVS from its initial release.
When were these partners notified?
VMware does not release details of confidential conversations with partners, however we can confirm that providers of 3rd party vSwitches have been notified to facilitate conversations with their customers.
What should customers do?
Customers are encouraged to migrate from third party distributed vSwitches including Cisco Nexus 1000V, Cisco VM-FEX, Cisco AVS, HPE 5900v and IBM DVS 5000v to vSphere Distributed Switch.
What is VMware doing to assist customers?
To assist in migration to VDS, VMware offers a free migration tool, or customers can work with VMware’s Professional Services Organization.
How many VMware customers will be impacted by this?
VMware believes the overall number of customers will be minimal, though some customers will be impacted.
Can a customer continue to use a 3rd party virtual switch, specifically the Cisco Nexus 1000v?
Existing customers that have purchased the Cisco Nexus 1000V may continue to use the product on vSphere 6.0 and prior versions. Cisco has only provided software support for Nexus 1000V up to VMware vSphere 6.0.”
Will VMware continue to provide support for the Nexus 1000v?
Yes, customers who have active support and subscription contracts for vSphere 5.5 and 6.0 will be entitled to support.
Why can’t a customer use Nexus 1000V with VMware vSphere 6.5?
Cisco has not released a vSphere Installation Bundle (VIB) to support vSphere 6.5.
Will VMware support the migration of Nexus 1000V to VDS?
Yes, customers can use a free migration tool developed by VMware. They can reach out to Global Support and Services (GSS), or engage the VMware professional services organization (PSO). Migration documentation and the migration tool is available for download.
Doesn’t this mean customers can no longer deploy Cisco ACI for network virtualization in VMware vSphere environments?
Nexus 1000v is not part of the Cisco ACI platform and therefore deployment of Cisco ACI and use of Cisco Nexus 1000V are not related.
How is Cisco supporting VMware vSphere customers with Cisco ACI?
For specific discussions related to Cisco customers, please contact Cisco. VMware has seen customers deploy Cisco ACI as a hardware fabric management platform and deploy VMware NSX in parallel for network virtualization and micro-segmentation.

503 Service Unavailable - vSphere Web Client Connection Issue

After rebooting my vCenter Server, when i tried to connect with vSphere web Client, It was giving me error message as given below. When i tried to find out the reason of this issue, i got to know this is expected behavior sometime. Solution is to restart the vSphere web client service manually.

Organization vDC Template Feature in vCloud Director 8.1

With vCD 8.1, VMware announced the new feature called Organization vDC Templates that gives the ability to Organization Administrator Role user to create the Organization vDC by using this template. Prior to this vCD version only system administrator role users can create the Organization vDC's. Organization vDC's are basically business unit of the tenant. Let's discuss the step by step of creating Organization vDCs Templates:-

1. Org vDC Templates only System Administrator Role User can create and configure.
Login as system administrator role user > Manage and Monitor > Organization vDC Templates > Click on + Sign > Select the Provider vDC > Add > Next

2. Select Allocation Model Type

3. Configure the resoruces for allocation model type

4. Select the Storage Policy

5. Configure the Network quota

6. Configure the Edge Gateway details

7. Configure the Organization vDC Network details

8. Select your Organizations who can use these template to trigger the Organization vDC creation

9. Configure Organization vDC Template Name

10. Click on Finish

Wednesday, 5 April 2017

DRS Affinity and Anti-Affinity Rules in vCloud Director UI

In vCD 8.1, New feature is introduced and that is creation of DRS Affinity and Anti-Affinity Rules for vCD VMs from vCD UI. Let's discuss how to configure these rules in vCloud Director 8.1.

First Connect with vCloud Director Cell as System Administrator or with Organization as Organization Administrator

Access the Organization > Administration Tab > Open your Organization vDC > Affinity/Anti-Affinity Tab > Create the Rule for the VM's those exist in the environment

Once Rule is created connect with vSphere Web Client and Check the Rule:-
Select DRS Cluster > Manage Tab > VM/Host Rules

Tuesday, 4 April 2017

vSphere Resource Pool Configuration for Allocation Models in vCD a.k.a vCloud Director

As  we all know there are three allocation models we have in vCloud Directors, those are:-
1. Allocation Pool Model
2. Pay-As-You-Go Model
3. Reservation Pool Model

Let's discuss the impact of these models in vSphere Resource Pool Configuration

1. Allocation Pool Model:-

2. Pay-as-you-go Model:-

3. Reservation Pool Model

Saturday, 1 April 2017

vCD 8.1 Compatibility with NSX, vCNS and vSphere Versions

Here is what i am able to find out from VMware Compatibilty Guide about this compatibilty

NSX and vCD Compatibility
vCNS and vCD Compatibility
 vCenter and vCD Compatibility

Here is the complete list of VMware Solutions those are supported with different vCD versions as of date. Download Link

VMware Compatibility Checker Link