http://www.vladan.fr/how-to-reset-esxi-5-x-root-password-and-under-which-conditions/

But, it may not be supported.  The statement in the following KB article indicates that the only supported way to reset the root account password on an ESXi host is to reinstall ESXi.

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1004659

The post Forgot ESXi Password? Here is a fix. appeared first on New Age Technologies.

• Based on IP hash – Use this only for Etherchannel (port channel).  If the uplinks on a standard virtual switch or distributed virtual switch connect to an Etherchannel, then set the NIC Teaming Load Balancing to IP Hash for each virtual port group that uses these uplinks.    This could also be used when implementing new features in vSphere 5.1 and 5.5 that allow LACP to be configured on the physical uplinks of a distributed virtual switch.
• Based on originating virtual port – This is the default.  It has traditionally been the best setting for most virtual port groups, whenever Etherchannel is not involved.  It is still the best setting in most cases when Ethernet is not involved for standard virtual port groups,  Load Based Teaming (LBT) is often preferred in this case for distributed port groups
• Based on source MAC hash – This is seldom used, but is preferred whenever you want to control the placement of VMs based on their MAC address assignments.
• Based on physical NIC load – This is also called Load Based Teaming (LBT).  It is a fairly new feature on dvSwitches and is typically preferred over port-based teaming, because the two perform identically, except that LBT includes intelligence to migrate virtual adapters from a busy uplink to a lesser active uplink.  In many cases, this is preferred over using Etherchannel to provide a scalable NIC Team that does not require special settings on the physical switch, so it is easy to manage.  However, Ethernet is still preferred in cases where the best resiliency, scalability, and performance is needed.
• Explicit Failover – Used in cases where the administrator prefers to manually balance the workload by placing some VMs and vmkernel virtual adapters on specific port groups that utilize a specific set of active ports.  A common example, is where the Management Network and vMotion are the placed on a virtual switch by themselves – often the Management Network is set to use vmnic0 as Active and vmnic1 as Standby and vice versa for the vMotion port.

The post Choosing the Best NIC Teaming Load Balancing Policy in vSphere appeared first on New Age Technologies.

Etherchannel:  an Etherchannel is a logical channel formed by bundling together two more links to aggregate bandwidth and provide redundancy.  Another acceptable name for Etherchannel (an IOS term) is port channel (an NXOS term).  Another acceptable name is Link Aggregation Group (LAG)

LACP:  a standards based negotiation protocol used to dynamically build an Etherchannel.  It is known as the IEEE 802.1ax (or IEEE 802.3ad) Link Aggregation Control Protocol (LACP).    It is a protocol used to build Etherchannels (LAGs) dynamically.   LAGs (Etherchannels) can be be also be built statically without using LACP.

IEEE 802.1ax:  The IEEE working group that defines port channel, EtherChannels and link aggregation.  Orinally, the working IEEE group was 802.3ad, but in 2008 it was replaced by 802.1ax.

IEEE 802.3ad:  the original IEEE working group for port channel, EtherChannel, and link aggregation.  Although it has been replaced with 802.1ax, referring to IEEE 802.3ad is typically acceptable.  So references to IEEE 802.3d LACP are common.

vSphere pre version 5.1:  the standard virtual switches and distributed virtual switches provided natively by VMware vSphere 5.0 and earlier do not support LACP (dynamic LAG / Etherchannel creation); however, they support statically built LAGs (or this may be called static LAGs or static Etherchannels)

vSphere 5.1:  the distributed virtual switches provided natively by VMware vSphere 5.1  support LACP (dynamic LAG / Etherchannel creation).  The support is limited to one LAG per ESXi host and per dvSwitch

vSphere 5.5:  the distributed virtual switches provided natively by VMware vSphere 5.5  support LACP (dynamic LAG / Etherchannel creation).  It supports 64 LAGs per ESXi host and 64 LAGs per dvSwitch.

The post LACP, LAG, Etherchannel and vSphere 5.5 – a simple explanation appeared first on New Age Technologies.

To avoid this issue, you could consider modifying the ESXi host policies, such that it forces the user to change the root account password whenever it expires rather than locking the root account.  The KB article 2069041  also discusses how to adjust the expiration policy.

Likewise, some vSphere administrators have unexpectedly experienced situations where the VMware vSphere Single Sign-On (SSO) administrator account  is locked due to password expiration.  See VMware KB article 2034608 for details on resolving the issue in SSO 5.1 and SSo 5.5.

Naturally, you can avoid certain issues by configuring a solid SSO Password Policy by implementing the procedure found here.

The post Addressing the Short Password Expiration in vCenter Server Appliance appeared first on New Age Technologies.