bhards4's Posts

Hi SR-IOV is disabled by default on ESXi 5.1 & 5.5. To enable SR-IOV, use the esxcli command or host profiles in 5.1. In vSphere 5.5, it can be done through the vSphere Web Client also. Note: For SR-IOV to function, physical hosts must meet these requirements. 1 Supported Processor: Intel VT-d or AMD-Vi 2) Motherboard firmware support for Intel VT-d or AMD-Vi 3) IOMMU is enabled in the BIOS/UEFI 4)LACP is currently unsupported with SR-IOV To enable SR-IOV on a Physical Adapter using the esxcli command in ESXi 5.1 or 5.5: Take SSH of the ESXi host and run below command esxcli system module parameters set -m NIC_Driver_Module -p "max_vfs=n" Where: NIC_Driver_Module is the module name of the NIC which is SR-IOV capable (for example, ixgbe) n is the number of virtual functions (VFs) provided by the NIC (for example, For example, to configure for an Intel X540 10 GB Ethernet Adapter, run the command: esxcli system module parameters set -m ixgbe -p "max_vfs=8" Reboot the host to reload the driver with the configured parameters. ============================================== To enable the SR-IOV on a Host Physical Adapter in the vSphere Web Client in the ESXi 5.5 : In the vSphere Web Client, navigate to the Host. In the Manage > Networking tab, select Physical adapters, you can see the SR-IOV property to check whether a physical adapter supports SR-IOV. Select the physical adapter and click Edit Settings. Under SR-IOV, select Enabled from the Status dropdown. In the Number of virtual functions text box, type the number of virtual functions that you want to configure for the adapter. Click OK. Restart the host. -Sachin

Hi, Please check below. 1) Is the ESXi host accessible from SSH 2) Is the ESXi host accessible as standalone host from vSphere client. 3) Whats the status of VM, are they online or in orphened status. 4) Have tried to reconnect the host from vCenter.- If yes, whats the error you are getting . 5) Please see into the ESXi  hostd.logs and found if there is any hostd non-responsive status mentioned. 6) If possible attached the hostd.log, vobd.log, vmkwarning.logs -Sachin

Hi, Basically 30% utilization on ESXi host considered to be quite normal. However its depends upon environement to environment for having their baseline. Coming to the point, either to increase the CPU on the host or adding a ESXi host into the cluster. My recommendation is to add a new host to your cluster with the same configuration as other 4 ESXi host rather to upgrade the CPU on all the ESXi host. If by any chance you are upgrading the CPU , main thing needed to be considered to have the same configuration of CPU as other 4 are having. However you can use EVC mode to balance the CPU from different generation but that again degrade the performance. So, in last better to add the ESXi host into the cluster. -Sachin

Hi , If you want to monitor the CPU and Memory usage for last one week on the windows machine. You can use perfmon to set counters on Windows machine. Please find below link for more information. Create a Data Collector Set to Monitor Performance Counters You can also use ESXTOP command to get the detail information about CPU and Memory usage. Please find below URL for more information into it. https://books.google.co.in/books?id=GnVvAwAAQBAJ&pg=PA124&lpg=PA124&dq=esxtop+for+past+performance&source=bl&ots=-p3fy4y… Regards, Sachin Bhardwaj

Yes, you can delete the old logs less then 30 days. Basically these are the old logs which are all history. You are safe to delete them & will not cause any data loss kind of situation. -Sachin

Hi Formz, Well , these are the worker.logs which might help you to understand what impact the OS. Moreover these logs identifies if any non-responsive HOSTD or could be any hardware issue or resource crunch on the OS. To, answer your question, yes, deleting these logs files will not going to affect the ESXi OS. If you want to delete , its quite safe to delete them. - Sachin

Hi, Seems your firewall rules are disabled as you are getting false. Try below following on your affected host: Firewall enabled: # esxcli network firewall set --enabled true # esxcli network firewall get Default Action: DROP Enabled: true Loaded: true Follow below KB https://kb.vmware.com/kb/2005284 Regards, Bhards4

Hi, Pls check the storage whether there are any appropriate space available into the LUN from where you are trying to increase. or try to migrate that VM to another storage and then try to increase the space. Please mark answer helpful or correct if you found it suitable. Regards, Bhards4

Hi, As per your connections , you need to di  VLAN Trunking on both the  VLAN's. As VLAN10 is your native vlan where you have installed Esxi, so after vlan trunking both the VLAN can communicate to each other. VLAN trunking needed to be done at network level. Regards, Bhards4