Update sequence for vSphere 6.0 and its compatible VMware products

Following our technical discussion regarding upgrade VMware environments, actually I already wrote about this topic in different thread  in this blog. But, I would like to emphasise again by using another KB from VMware. VMware has made available certain releases to address critical issues and architectural changes for several products to allow for continued interoperability:

  • vCloud Connector (vCC)
  • vCloud Director (vCD)
  • vCloud Networking and Security (VCNS, formerly vShield Manager)
  • VMware Horizon View
  • VMware NSX for vSphere (NSX Manager)
  • vCenter Operations Manager (vCOPs)
  • vCenter Server / vCenter Server Appliance
  • vCenter Infrastructure Navigator (VIN)
  • vCenter Site Recovery Manager (SRM)
  • vCenter Update Manager (VUM)
  • vRealize Automation Center (vRA, formerly known as vCloud Automation Center)
  • vRealize Automation Application Services (vRAS, formerly vSphere AppDirector)
  • vRealize Business, IT Cost Management (ITBM, formerly VMware IT Business Management)
  • vRealize Configuration Manager (VCM, formerly vCenter Configuration Manager)
  • vRealize Hyperic
  • vRealize Log Insight (vRLI)
  • vRealize Operations Manager (vROPs, formerly known as vCenter Operations Manager, vCOPs)
  • vRealize Orchestrator (vRO, formerly vCenter Orchestrator)
  • vSphere Big Data Extension (BDE)
  • vSphere Data Protection (VDP)
  • vSphere Replication (VR)
  • vSphere ESXi
  • vShield Edge / NSX Edge
  • vShield App / NSX Logical Firewall (NSX LFw)
  • vShield Endpoint / NSX Guest Introspection and Data Security (NSX Guest IDS)
This article only encompasses environments running vSphere and/or vCloud Suite 6.0 and VMware products compatible with vSphere 6.0.

In an environment with vSphere 6.0 and its compatible VMware products, perform the update sequence described in the Supported Update Sequence table.

Supported Update Sequence

Continue reading Update sequence for vSphere 6.0 and its compatible VMware products

Order to Start vCenter Service in Windows

Order to Start vCenter Service in Windows:

  1. VMware Directory Service
  2. VMware KDC Service
  3. VMware Certificate Service
  4. VMware Identity Management Service
  5. VMware Secure Token Service
  6. VMware VirtualCenter Server

Kind Regards,
Doddi Priyambodo

vRealize Operations Manager 6.1 and 6.2 Sizing Guidelines (2130551)

Source: https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2130551


This article provides information on using the sizing guidelines for vRealize Operations Manager 6.1 and 6.2 to determine the configurations used during installation.

Continue reading vRealize Operations Manager 6.1 and 6.2 Sizing Guidelines (2130551)

VMware vSphere Replication – Bandwith and Overhead Explained (updated)

Bandwith yang dibutuhkan untuk vSphere Replication Technology

Berikut ini adalah cara menghitung Bandwidth untuk vSphere Replication for Teknologi Replikasi dari VMware :

Untuk lebih jelasnya, terdapat VMware Knowledge Based yang membahas mengenai hal ini, yaitu :

Summary dari artikel tersebut adalah :

Contoh kasus, jika ada 500 VMs, rata2 200GB disk (70% used), data change rate 5%-25%, RPO average 4 jam dibutuhkan bandwidth sebesar ~500Mbps. Tetapi jika data change ratenya diubah menjadi 10%-25% bandwidth yg dibutuhkan ~1Gbps, 2x-nya

Di vSphere Replication version 6.0 ada feature baru dengan compression untuk menghemat bandwidth https://blogs.vmware.com/vsphere/2015/03/vr-60-compression.html

For most replication workloads, you will likely see compression ratios of approximately 1.6:1 to 1.8:1.

Performance Overhead untuk vSphere Replication

Pada vSphere Replication ada sedikit performance overhead impact ke VM dan ke ESXi. Impact ke VM seitar 2-6% dan pada ESXi hosts sangat minim, ini juga ada dokumentasinya di FAQ berikut vSphere Replication Frequently Asked Questions: https://communities.vmware.com/docs/DOC-27800

Q: What performance information is available about VMware vSphere Replication?

A: Impact on virtual CPU performance for a virtual machine that is protected by vSphere Replication is approximately 2 to 6 percent. In nearly all cases, this is not an issue because the vast majority of virtual machines are not CPU constrained.

Q: What performance overhead exists on the source hosts?

A: The replication scheduler built into VMware vSphere uses an insignificant amount of CPU and memory to compute the replication schedule of all the virtual machines on the host.

Q: What performance overhead exists on the target hosts?

A: VMware vSphere® Replication virtual appliances receive the replication traffic. They utilize compute and networking resources in a manner similar to any other virtual machine. Additional storage load is placed upon the VMware vSphere hosts as vSphere Replication transfers replicated data to storage using the Network File Copy (NFC) protocol. During a full-sync operation, checksum calculation operations are distributed across multiple hosts to minimize CPU impact on any one host. Several factors influence where contention might occur. For example, if there is much bandwidth – 1Gbps, for example – the amount of NFC traffic might tax the host or even the underlying storage system.


Spesifikasi VM untuk SRM dan vSphere Replication Appliance

Spesifikasi VM yang dibutuhkan untuk SRM, ini terdokumentasi di Installation Guide SRM sebagai berikut

VMware vCenter Site Recovery Manager Documentation: https://www.vmware.com/support/pubs/srm_pubs.html

Site Recovery Manager System Requirements: http://pubs.vmware.com/srm-60/index.jsp#com.vmware.srm.install_config.doc/GUID-384B628F-35C8-4C96-9B36-ACCEBE6C6792.html

  1. SRM – Windows Server 2008/2012, 2 vCPUs, 8GB vRAM, 70GB Disk (5GB Min), 1 GbE NIC/Network
  2. VMware vSphere Replication – 2vCPUs, 4GB of vRAM, 10GB & 2GB disks


Inspired from Bayu’s email. Good Info to share with customers bro.

STP may cause temporary loss of network connectivity when a failover or failback event occurs (1003804)


In a switched network environment which uses Spanning Tree Protocol (STP), you experience these symptoms:

  • An ESXi or ESX host temporarily loses network connectivity when a failover or failback event occurs.
  • Virtual machines temporarily lose network connectivity when a failover or failback event occurs.
  • A VMware High Availability (HA) isolation event occurs after one of the teamed NICs of the COS is unplugged and plugged in to a different port.


STP is used to accomplish a loop-free environment. Every time a port state goes up, STP calculation occurs. As the result of the calculation, the switch ports are either set to a forwarding or blocking state to prevent a traffic loop. STP topology convergence has four states:

  • Blocking
  • Listening
  • Learning
  • Forwarding

When STP convergence is initiated it forces all of the physical switches in the STP domain to dump their forwarding tables and relearn the STP topology and all MAC addresses. This process can take between 30-50 seconds. During this time, no user data passes through the port. Some user applications can time out during this period. Connectivity is restored when the STP domain completes this convergence.

To prevent the 30-50 second loss of connectivity during STP convergence, perform one of these options:

  • To set STP to Portfast on all switch ports that are connected to network adapters on an ESXi/ESX host
    Portfast allows the ports to immediately be set back to the forwarding state and prevents the link state changes that occur on ESX/ESXi hosts from affecting the STP topology. Setting STP to Portfast prevents the 30-50 second loss of network connectivity.
    The command to set STP to Portfast depends on the model of the switch. As the command is different from model to model and vendor to vendor, c ontact your physical switch vendor for more detailed information on how to configure the same.
    For example:
    To set STP to Portfast on a switch, run the below command based on the switch model:

      spanning-tree portfast (for an access port)
      spanning-tree portfast trunk (for a trunk port)
    • NX-IOS
      spanning-tree port type edge (for an access port)
      spanning-tree port type edge trunk (for a trunk port)
    • To set STP to Portfast on a Dell switch, run the command:
      spanning-tree portfast
    • HP switches use a feature called admin-edge-port, which works the same way as Portfast or RSTP.
      To enable admin-edge-port, run the command:
      spanning-tree port-listadmin-edge-port
  • To disable STP
    VMware does not typically recommend that you disable STP. However, to prevent this issue from occurring, it may be necessary to disable STP. Before you disable STP, contact your switch vendor.
    The command to disable STP depends on the switch. Contact your switch vendor for more detailed information.
    For example:
    To disable STP on a Nortel switch, run the command:
    config ethernet stg stp disable

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