OscarDavey's Posts

ESXi 5.5 System Requirements When installing or upgrading to ESXi 5.5, ensure that the host meets these minimum hardware configurations supported by ESXi 5.5: Your hardware is compliant on the... See more...
ESXi 5.5 System Requirements When installing or upgrading to ESXi 5.5, ensure that the host meets these minimum hardware configurations supported by ESXi 5.5: Your hardware is compliant on the VMware Compatibility Guide. This includes: System compatibility I/O compatibility (Network and HBA cards) Storage compatibility Backup software compatibility You have a 64-bit processor. VMware ESXi 5.5 only installs and runs on servers with 64-bit x86 CPUs. It also only supports LAHF and SAHF CPU instructions. You have an ESXi 5.5 host machine with at least two cores. The NX/XD bit is enabled for the CPU in the BIOS. Your processor is supported. ESXi supports a broad range of x64 multicore processors. For a complete list of supported processors, see the VMware Compatibility Guide. You have 4GB RAM. This is the minimum required to install ESXi 5.5. Provide at least 8GB of RAM to take full advantage of ESXi features and run virtual machines in typical production environments. Support for hardware virtualization (Intel VT-x or AMD RVI) is enabled on x64 CPUs (to support 64-bit virtual machines). For a complete list of operating systems supported with ESXi, see the VMware Compatibility Guide. Hosts running virtual machines with 64-bit guest operating systems have these hardware requirements: For AMD Opteron-based systems, the processors must be Opteron Rev E or later. For Intel Xeon-based systems, the processors must include support for Intel Virtualization Technology (VT). Many servers that include CPUs with VT support might have VT disabled by default, so you must enable VT manually. If your CPUs support VT , but you do not see this option in the BIOS, contact your vendor to request a BIOS version that lets you enable VT support. Note: To determine whether your server has 64-bit VMware support, download the CPU Identification Utility from the VMware Website. You have one or more Gigabit or 10GB Ethernet controllers. For a list of supported network adapter models, see the VMware Compatibility Guide. You have Storage controllers with any combination of one or more of: Basic SCSI controllers. Adaptec Ultra-160 or Ultra-320, LSI Logic Fusion-MPT, or most NCR/Symbios SCSI. RAID controllers. Dell PERC (Adaptec RAID or LSI MegaRAID), HP Smart Array RAID, or IBM (Adaptec) ServeRAID controllers. You have SCSI disk or a local, non-network, RAID LUN with unpartitioned space for the virtual machines. For Serial ATA (SATA), a disk connected through supported SAS controllers or supported on-board SATA controllers. SATA disks are considered to be remote, not local. These disks are not used as a scratch partition by default because they are seen as remote. Note: You cannot connect a SATA CD-ROM device to a virtual machine on an ESXi 5.5 host. To use the SATA CD-ROM device, you must use IDE emulation mode. You are using a supported storage system. ESXi 5.5 supports installing on and booting from these storage systems: Note: ESXi does not support using local, internal SATA drives on the host server to create VMFS datastores that are shared across multiple ESXi hosts. SATA disk drives. SATA disk drives connected behind supported SAS controllers or supported on-board SATA controllers. LSI1068E (LSISAS3442E) LSI1068 (SAS 5) IBM ServeRAID 8K SAS controller Smart Array P400/256 controller Dell PERC 5.0.1 controller SATA disk drives. Supported on-board SATA include: Intel ICH9 NVIDIA MCP55 ServerWorks HT1000 You have Serial Attached SCSI (SAS) disk drives supported for installing ESXi 5.5 and for storing virtual machines on VMFS partitions. You have dedicated SAN disk on Fibre Channel or iSCSI. You have USB devices that are supported for installing ESXi . You can install and boot ESXi from an FCoE LUN using VMware software FCoE adapters and network adapters with FCoE offload capabilities. See the vSphere Storage documentation for information about installing and booting ESXi with software FCoE. Best regards
To resolve this issue, Install/Reinstall Microsoft .NET Framework 3.5 Service Pack 1 or later. Best regards Yours, Oscar
As mentioned here the firewall might be blocking the port between Vcenter and BMC . These ports are mandatory: 22 - SSH (TCP) 53 - DNS (TCP and UDP) 80 - HTTP (TCP/UDP) 902 - vCenter Se... See more...
As mentioned here the firewall might be blocking the port between Vcenter and BMC . These ports are mandatory: 22 - SSH (TCP) 53 - DNS (TCP and UDP) 80 - HTTP (TCP/UDP) 902 - vCenter Server / VMware Infrastructure Client - UDP for ESX/ESXi Heartbeat (UDP and TCP) 903 - Remote Console (UDP) 443 - Web Access (TCP) 27000, 27010 - License Server (Valid for ESX/ESXi 3.x hosts only) These ports are optional: 123 - NTP (UDP) 161, 162 - SNMP (UDP) 88 - Kerberos (UDP and TCP) 464 - Active Directory (TCP and UDP) 3260 - Software iSCSI (TCP) For a complete list of ports, see TCP and UDP Ports for vCenter Server, ESX/ESXi hosts, and other network components management access (1012382). Yours, Oscar
To resolve this issue, recreate the vCenter Inventory Service database and re-register it to vCenter Server Appliance. To recreate the vCenter Inventory Service database and to and re-register... See more...
To resolve this issue, recreate the vCenter Inventory Service database and re-register it to vCenter Server Appliance. To recreate the vCenter Inventory Service database and to and re-register it to vCenter Server Appliance: Connect to the vCenter Server Appliance using SSH or a virtual machine console and log in as the root user. Run these commands: # service vmware-inventoryservice stop # rm -rf /storage/db/inventoryservice/data # /usr/lib/vmware-vpx/inventoryservice/scripts/ds-invoke.sh -Dvim.logdir=/var/log/vmware/vpx/inventoryservice com.vmware.vim.dataservices.CreateDb /storage/db/inventoryservice/data changeme default changeme Note: The database password is changeme. Ensure that the vCenter Inventory Service is started by running this command: # service vmware-inventoryservice start To re-register the vCenter Inventory Service to vCenter Server Appliance, run these commands in order depending on your version: vCenter Server Appliance 5.0: # /usr/lib/vmware-vpx/inventoryservice/scripts/ds-invoke.sh -Dvim.logdir=/var/log/vmware/vpx/inventoryservice-registration com.vmware.vim.dataservices.provider.util.SetupLocalService -vcurlhttps://vcenter_name_or_ip:443 /sdk/vimService -providercfg file:/usr/lib/vmware-vpx/inventoryservice/lib/server/config/vc-provider-registration.xml -servicecfg /usr/lib/vmware-vpx/inventoryservice/lib/server/config/dataservice.properties # service vmware-vpxd restart vCenter Server Appliance 5.1: # /usr/lib/vmware-vpx/inventoryservice-registration/vcregtool.sh -Dvim.logdir=/var/log/vmware/vpx/inventoryservice-registration com.vmware.vim.dataservices.vcregtool.RegisterVC -action register -lookupserviceurl https://vcenter_name_or_ip:7444/lookupservice/sdk -isurl https://vcenter_name_or_ip:10443 -vcurl https://vcenter_name_or_ip/sdk/vimService -vccert /etc/vmware-vpx/ssl/rui.crt -vcprivkey /etc/vmware-vpx/ssl/rui.key -vcinstancecfg /etc/vmware-vpx/instance.cfg -vcendpointsdir /usr/lib/vmware-vpx/endpoints -vcextensionsdir /usr/lib/vmware-vpx/extensions # service vmware-vpxd restart vCenter Server Appliance 5.5: # vcenterhost=vchost.mydomain.com Note: The above command sets the vcenterhost= to the FQDN of your vCenter Server Appliance. To obtain the FQDN of your vCenter Server Appliance, run the command hostname. # /usr/lib/vmware-vpx/inventoryservice-registration/vcregtool.sh -Dvim.logdir=/var/log/vmware/vpx/inventoryservice-registration com.vmware.vim.dataservices.vcregtool.RegisterVC -action register -lookupserviceurl https://$vcenterhost:7444/lookupservice/sdk -isurl https://$vcenterhost:10443 -vcurl https://$vcenterhost/sdk/vimService -vccert /etc/vmware-vpx/ssl/rui.crt -vcprivkey /etc/vmware-vpx/ssl/rui.key -vcinstancecfg /etc/vmware-vpx/instance.cfg -vcendpointsdir /usr/lib/vmware-vpx/endpoints -vcextensionsdir /usr/lib/vmware-vpx/extensions # service vmware-vpxd restart Best regards Yours, Oscar
A firewall may be blocking that port from your source to the destination server. These ports are mandatory: 22 - SSH (TCP) 53 - DNS (TCP and UDP) 80 - HTTP (TCP/UDP) 902 - vCenter Serv... See more...
A firewall may be blocking that port from your source to the destination server. These ports are mandatory: 22 - SSH (TCP) 53 - DNS (TCP and UDP) 80 - HTTP (TCP/UDP) 902 - vCenter Server / VMware Infrastructure Client - UDP for ESX/ESXi Heartbeat (UDP and TCP) 903 - Remote Console (UDP) 443 - Web Access (TCP) 27000, 27010 - License Server (Valid for ESX/ESXi 3.x hosts only) These ports are optional: 123 - NTP (UDP) 161, 162 - SNMP (UDP) 88 - Kerberos (UDP and TCP) 464 - Active Directory (TCP and UDP) 3260 - Software iSCSI (TCP) For a complete list of ports, see TCP and UDP Ports for vCenter Server, ESX/ESXi hosts, and other network components management access (1012382). Yours, Oscar
I know that someone had it and he had some hangout/timeout issues , i really suggest that you go with the HCL list for a convenient performance unless u r going to use it experimentally. Best ... See more...
I know that someone had it and he had some hangout/timeout issues , i really suggest that you go with the HCL list for a convenient performance unless u r going to use it experimentally. Best regards Yours, Oscar
This problem can be caused by an incompatible version of drivers , if you have the USB control in the VM working well except that your kb is not working then go to logitech and download a compati... See more...
This problem can be caused by an incompatible version of drivers , if you have the USB control in the VM working well except that your kb is not working then go to logitech and download a compatible driver with it . but probably you have a usb control problem in the VM . and if so please read this KB http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1003868 Hope that will help Best regards Yours, Oscar
Your question is not really clear , but if i understood you well you can install windows os on the vm and setup a shared storage and add any permission u want to it . Best regards Yours, Osca... See more...
Your question is not really clear , but if i understood you well you can install windows os on the vm and setup a shared storage and add any permission u want to it . Best regards Yours, Oscar
Try this : Place the ESXi/ESX host into maintenance mode. Remove all VMNICs from the virtual switches except vmnic0 , which is used for management. Shut down the ESXi/ESX host. Remove/dis... See more...
Try this : Place the ESXi/ESX host into maintenance mode. Remove all VMNICs from the virtual switches except vmnic0 , which is used for management. Shut down the ESXi/ESX host. Remove/disable all NICs except vmnic0 . Boot the server. At boot time, all removed/disabled VMNICs are removed from the esx.conf file. Shut down the ESXi/ESX host. Add/enable all required NICs. Boot the ESXi/ESX host. All VMNICs are assigned per segment, bus, slot, and function ID, and are ordered correctly. Assign VMNICs back to virtual switches as before. Exit maintenance mode on the ESXi/ESX host. Hope this will help you out . Best regards Yours, Oscar
incompatibility issue , try to find the new driver for the controller or check HP for an up2date drivers to go through this problem . Best regards Yours, Oscar
Seems that one of the devices u have is missing some configuration or is not compatible , not sure if its a hdd , are u having your array working probably ?  if yes then its just an informational... See more...
Seems that one of the devices u have is missing some configuration or is not compatible , not sure if its a hdd , are u having your array working probably ?  if yes then its just an informational message other than that you would be having some critical issues and you should look into it , i suggest you do its really not that hard to check it . If you need further help let me know Best regards Yours, Oscar
Try this guide it really helps . http://www.marcomc.com/2011/01/how-to-connect-to-vmware-server-console-via-mac-os-x/ Best regards Yours, Oscar
Check this KB , maybe it will help you out . http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1028601 Best regards Yours, Oscar
To rename a VMware ESX host: If the ESX host is part of a cluster, remove it from the cluster by dragging it out of the cluster. If the ESX host is managed by VirtualCenter/vCenter, disconnect... See more...
To rename a VMware ESX host: If the ESX host is part of a cluster, remove it from the cluster by dragging it out of the cluster. If the ESX host is managed by VirtualCenter/vCenter, disconnect and remove the ESX host from the vCenter. Make the modifications in your DNS environment to reflect the correct name and IP association for the new name. Log in as root to the console of ESX host. Using a text editor, change the name and domain name, if applicable, of the host in these files: /etc/hosts /etc/sysconfig/network Execute this command esxcfg-advcfg -s hostname /Misc/hostname where hostname is the new FQDN hostname for the ESX host. Reboot the ESX host. Join the ESX host to VirtualCenter/vCenter Server and clusters. To rename a VMware ESXi host: If the ESXi host is part of a cluster, remove it from the cluster by entering Maintenance mode first. If the ESXi host is managed by VirtualCenter/vCenter Server, disconnect and remove the ESXi host from the vCenter Server. Connect to the host directly with a vSphere Client. Click ESXi host. Click the Configuration tab. Click DNS and Routing. Click  Properties. Edit the Name field in the DNS Configuration tab. Change anything else that is necessary in your environment. Click OK. Join the ESX host to VirtualCenter/vCenter Server and clusters. To change the host name in ESXi 5.x using the command line, use these commands: esxcli system hostname set --host=hostname esxcli system hostname set --fqdn= fqdn Best regards Yours, Oscar
Are you getting this high cpu usage when the VM is idle ?  have you tried temporary disabling vlan ? Best regards Take care!
This probable coz your NIC is not compatible ... rather than trying to find a driver, I'd rather suggest you look for a supported NIC or an inexpensive one which is known as working (e.g. an Inte... See more...
This probable coz your NIC is not compatible ... rather than trying to find a driver, I'd rather suggest you look for a supported NIC or an inexpensive one which is known as working (e.g. an Intel Pro/1000 GT). Even if you can find a driver, the system could break with each update/patch you apply. Best regards Yours, Oscar
A number of factors can cause an ESX host to become unresponsive. For example: Defective or unresponsive hardware An operational busy loop in the VMkernel, driver module, or service console A... See more...
A number of factors can cause an ESX host to become unresponsive. For example: Defective or unresponsive hardware An operational busy loop in the VMkernel, driver module, or service console A component holding a lock needed by other components A process that is consuming a high amount of resources Troubleshooting this type of issue after it has occurred is difficult because you cannot interact with the ESX/ESXi host while it is in this state.Note: Many external influences may yield similar symptoms but have very different underlying issues. For example, a network outage can result in a situation where an ESX/ESXi host and all running virtual machines become unresponsive, console authentication using remote directory services fails, and remote BMC management fails.These limitations further complicate troubleshooting: If the issue has only occurred once, analysis is limited to the logs generated prior to the single occurrence. If the issue has only occurred once, you cannot identify patterns between multiple occurrences. The logs generated by a single event may not be conclusive, and determining the root cause may not be possible. If an ESX/ESXi host is currently in an unresponsive state, gather this information: Press the NumLock key on your keyboard and observe if the NumLock light state changes. A successful light state change indicates that the BIOS is responsive. Check if there is any active disk or network traffic using status lights or other hardware monitoring on the disk drive array, network interface cards or upstream switches. Active egress traffic indicates that the ESX/ESXi host is still functioning. VMware HA monitors ESX/ESXi host availability in part based on response to ICMP (ping) network traffic. If the ESX/ESXi host is a member of an HA cluster, check the logs on other cluster members to determine when or if they lost access to this host. For more information, see Troubleshooting VMware High Availability (HA) (1001596). Trigger an NMI at the hardware level and observe how ESX/ESXi responds. For more information, see Using hardware NMI facilities to troubleshoot unresponsive hosts (1014767). If a purple diagnostic screen occurs after triggering the NMI, take a screenshot. Attempt to interact with the server via a baseboard management controller (BMC) interface, such as ILO, DRAC or RSA. If aspects of this interface other than the console are also unresponsive, it indicates that the issue is hardware related. Reboot the ESX/ESXi host. Collect diagnostic information from the host for further analysis. For more information, see Collecting diagnostic information for VMware products (1008524). Best regards Yours, Oscar
Reboot and then enter your bios go to Advanced section  , make sure EHCI handoffs "Enabled" and reboot . This should solve your problem Best regards Yours, Oscar
To troubleshoot this symptoms and get more information about how to configure software for iscsi please check this KB : VMware KB: Configuring and troubleshooting basic software iSCSI setup ... See more...
To troubleshoot this symptoms and get more information about how to configure software for iscsi please check this KB : VMware KB: Configuring and troubleshooting basic software iSCSI setup Let me know if you need more help Best regards Yours, Oscar
Open port 443 on the vCenter box to the IP address of the vCMA box . Best regards Yours, Oscar