Browsing Posts in VMware

One of the big advantages of the virtual appliance version of VMware vCenter (vCSA) is the ability to update both the OS components and the VMware parts with a simple menu. Just use the administrative UI available at https://vCSA_IP:5480 and login with user root and the password that you have choose during the deployment.

If you choose to install the vCSA 6.5 in two different components, you may have an error during the PSC custominization (happens also on latest 6.5U1): An error occurred while starting service ‘pschealth’ This it’s related to a failure of identity management service error on first boot, so during the phase 2 of the deployment where the appliance has already been upload, but still must be configured.

One of the announce at last VMworld EU 2017 is the new version of VMware vSphere Integrated Containers (VIC). This new version will deliver significant new capabilities, major security enhancements and the the ability to provision native Docker container hosts using a unified management portal. VMware vSphere Integrated Containers delivers an enterprise container infrastructure that provides the best of both worlds for the developers and vSphere operations teams where containers can now be enabled and managed as “normal” virtual machines with the same concepts and skills, with no processes or tools changes required.

VMware has just released the new major version of NSX-T 2.0 to provides an agile software-defined infrastructure to build cloud-native application environments. When Nicira product has been released was for Linux and physical platform, but after the VMware’s acquisition has been re-engineered to be integrated in the vSphere platform, with the new name of VMware NSX (now NSX-v). NSX-T is again a version for (physical) Linux system designed for management, operations, and consumption newtork resources insied a (development) organizations. NSX-T allows IT and development teams to choose the technologies best suited for their applications.

Starting with vSphere 6.0, the new PSC component include not only the SSO part, but also a certification authority for certification management of all vSphere infrastructure elements (unfortunately is not been used yet by all the other VMware’s products). This simplified not only the certifications management (with auto-enrollment for expired certificates), but also the trust between the different connections.

Actually there are two different platform where you can run the vCenter Server components (including the PSC): Windows (both physical or virtual) or Linux (only with the vCSA, based on PhotonOS). Initially there was only a Windows version, then the vCenter Server Appliance (vCSA) was first introduced with the release of vSphere 5.0 and has since evolved to become the definitive deployment model for vCenter Server. Starting with vSphere 6.5 the vCSA has become the first choice and has raised the level of vCenter with new functionalities (not available on the Windows version).

Finally has been announced (or better, confirmed) that VMware plans to deprecate the Flash-based vSphere Web Client with the next numbered release (not update release) of VMware vSphere. What does it mean, that the HTML5-based vSphere Client will become the only GUI client… finally! After the death of the vSphere Client for Windows, written with C# and with several issues, like the console issues with Windows 10, but also with several inconsistency with the others clients, now it’s the turn of the Flash based client.

One propertiers of VMware (standard) virtual switches was the number of ports per switch. A parameter (120 was the default in ESXi 5.x) that define how many virtual NIC and/or vmkernel interfaces you can connect to the virtual switch portgroups. This parameter was static and any changes require a host reboot. But starting with vSphere 5.5 (see KB 2064511) this parameter has become “elastic”.

Several people are disabling IPv6 support in ESXi for different reasons: because of the minimum privilege principle (if you are not using a service, why you have to keep it enabled?) or simple because they don’t want any IPv6 address in the network. On Linux and Windows systems is become very difficult disable it and Microsoft itself does not recommend disabling IPV6: ” We do not recommend that you disable IPv6 or its components, or some Windows components may not function.” (https://support.microsoft.com/en-us/kb/929852)

Starting with VMware Horizon 7 it’s possible choose two different way to deliver space optimized desktop pools: using VMware Composer and linked clones technology (existing from several years) or use the new instant clones technology (introduced with vSphere 6.0). Similar to View Composer linked clones, instant clones share a virtual disk of a parent VM and therefore consume less storage than full VMs. In addition, instant clones share the memory of a parent VM. Instant clones are created using the vmFork technology. An instant-clone desktop pool has the following key characteristics:

VMware vSphere 6.5 Update 1 has been released on July 27, 2017 with several bug fix, some improvements, but also some interesting changing in maximum numbers (for vCenter in linked-mode) and an interesting news for the Foundation edition that now can manage up to 4 nodes (and not only 3 nodes like in the past). Seems a minor improvement, but demostrare how VMware takes care of its customers. In discussions with customers with smaller environments, VMware has received feedback that 3 host environments were too small in many cases, and just another hosts could be enough […]

© 2017 © 2013 vInfrastructure Blog | Hosted by Assyrus