Skip navigation

I've put together a blog post explaining CSTP, here is the article.

 

Any feedback is gracefully accepted and appreciated

 

http://virtualknight.wordpress.com/2014/05/09/esxtop-cstp-explained/

Attached is an overview of Auto Deploy feature & its workflow.

 

 

If you are not a fan of powercli that is used in the process, I strongly recommend using Auto Deploy plugin, this make life much simpler by providing a Graphical user interface for

  • Image Builder(downloading and creating custom images)
  • Deploy Rules (Creating rulesets and mapping to target hosts

 

Its completely Wizard driven.

 

Check it out here :

Auto Deploy GUI   

 

Questions : Write to me at cedric.rajendran@gmail.com

virtual_knight Enthusiast
VMware EmployeesvExpert

VXLAN for dummies :-)

Posted by virtual_knight Apr 20, 2014

Moved this over to my personal blog

 

http://virtualknightz.com/2014/05/06/vxlan-basics/


Issue Description:Un-presentation of an NFS datastore without first un-mounting from the hosts results in a network traffic storm in the infrastructure.

 

Symptoms:

  • Hosts disconnected from Virtual Center server
  • Physical network switches utilized near capacity
  • Packet capture reveals multitude of GETATTR and ARP packets
  • Systems connected to the same network infrastructure impacted

 

 

Tip#1 : Run packet capture on NFS array/filer

Tip#2 : Use Wireshark to review packet capture

 

Packet Capture - Failure pattern:

===

-->SYN---
<--SYN-ACK<--
-->ACK---
-->GETATTR---
<--FIN-ACK<--- (Close connection from Server)
-->ARP REQ---
<--ARP RES<---
-->ACK--- (for the FIN sent by Server)
-->RST----
===


Root Cause :

NFS filer/Arrays return FIN-ACK -typically to close connections to any NFS client(ESX host or any server accessing the NFS filer) that attempts to access a Lun that has been deleted or removed.

This can be deemed as a security measure to quell requests to gain access to non-existent devices and the NFS server is not obligated to service such requests.

Another significant reason why this should be done by the array is that one can build a server in the environment that can maliciously cause Denial of service(DDoS) type attacks on NFS array.


Resolution:

If hosts are still accessible, unmount the datastores

Else power down/reboot the hosts causing the network storm immediately.


The best practice for datastore removal is documented below,

http://kb.vmware.com/kb/2004605 - Un-mounting or detaching a datastore / storage device from multiple ESXi 5.x hosts.



In conclusion it is neither a fault of the ESX server or the array to behave in this fashion, both are reacting to abrupt device removal which is against standard best practices, although both server and client can be designed to behave more gracefully.


-Cedric


VMware tools upgrade or installation fails with error messages similar to ,


Error 25028.Setup failed to install the VMCI driver

Setup failed to install the mouse driver automatically.  This driver will have to be installed manually.", "VMware Tools Installation"

Setup failed to install the SVGA driver automatically.  This driver will have to be installed manually.  Instructions for how to do this will appear at the end of installation.

 

The same error message exist in the vminst log file of the Guest OS

 

This issue can be cause if Runonce registry key is missing, the corrective measure is outlined in the KB article http://kb.vmware.com/kb/1006382.

 

This can also happen due to certain sensitive application running on the OS blocking the install, one instance was app verify

http://communities.vmware.com/message/1999637

 

One other instance is Control-M, to resolve this follow the outlined steps

 

  1. Disable Control-M services.
  2. Restart the server.
  3. Reinstall the VMware tools or Follow new device prompts from Windows OS and drivers install correctly.
  4. Restart Server
  5. Re-enable Control-M services.
  6. Restart


Courtesy : Customer Shared information

  • Record IP address to be provisioned to UI VM & Analytics VM
  • Record the Download location of the vCenter Operations Manager OVA.
      • Ensure the following TCP ports are open in your firewall
      • SSH-22
      • HTTP-80(https redirection)
      • HTTPS-443
      • OpenVPN tunnel-1194 -
      • SMTP-25(default)-This is optional if you intend to configure mail alerts, also the ports may vary based on your environment
      • VCM-1433 If you intend to provision VCM, need access to DB through this port
  • Create IP pools- This is not really an IP pool rather a container of the Network association/configuration of the vApp
      • Select the IP Pools tab.
      • Click Add to add a new IP pool.
      • In the properties dialog box, select the IPv4 tab.
      • Type an IP pool name that you can recognize during future testing of IP pools.
      • Enter the IP Subnet and Gateway in their respective fields.
      • Do not select the Enable IP Pool checkbox and do not specify a range of IP addresses. You specify the IP address for the virtual machines in the vApp using the vApp OVF Deployment Wizard.
      • Select the DHCP tab.
      • Select the IPv4 DHCP Present
      • check box if a DHCP server is available on this network.
      • Select the DNS tab
      • Enter the DNS server information.
      • Enter the DNS Domain name of the DNS servers in your network in the IPv4 DNS Servers text box.
      • In the Associations tab, select the network for the IP pool.
  • Deploy the vCenter Operations Manager OVA- To be performed only through vCenter
      • Accept the EULA
      • Specify an appropriate name - default value is "VMware vCenter Operations"
      • Select the initial Configuration Size - Small, Medium, Large
      • Select the host/cluster to deploy
      • Select the Resource Pool
      • Select the Data Store
      • Select Thick Provisioned - Eager Zeroed- Using Thin disks have visible performance degradation
      • Select the Network Configured in the IP Pools step
      • Select the Fixed IP Allocation Policy or DHCP
      • Set the Timezone
      • Set the IP Addresses of the UI and Analytics
      • Do not Power On after deployment
  • Login to the UI VM's IP address, register vCenter that you would like to monitor.

 

Note : Registration user should have administrative privileges to register the vCenter.

 

Happy Monitoring