Storage
- SAN Troubleshooting Guide available, recommended reading:
- http://www.vmware.com/pdf/vi3_san_design_deploy.pdf
- ESX can boot from an iSCSI SAN only when using a hardware initiator (iSCSI HBA).
- ESX does not currently support TCP/IP offload engine (TOE) NIC cards (although it does support TCP session offload).
- When using a software iSCSI initiator the session is established (TCP/3260) using the Service Console network interface (CHAP & SendTargets IP address discovery). Network Connectivity is required from the service console to the iSCSI SAN (could use a 2nd service console interface, just for this purpose).
VirtualCenter
- ODBC connection from Virtual Center to SQL 2005 DB needs SQL Native Client (not SQL Server ODBC driver)
- Virtual Center SQL Login needs db_owner on vCenter and MSDB databases
Important VMware communications - e.g for firewall security policy
- VirtualCenter to License Server: 27000, 27010
- Rebates and SDK Clients to VirtualCenter: 443, 80
- VirtualCenter to ESX Hosts: 902
- VI Client to VirtualCenter: 443
- VI Client to ESX Host Remote Console: 903
- By default VirtualCenter accumulates performance data on ESX Hosts and VMs for 1 year
- Commands to check the status of, or start the ESX host process (vmware-hostd):
- service mgmt-vmware status, service mgmt-vmware start
Virtual Machines
- As a guideline deploy single CPU VMs unless a multiple CPU VM is absolutely needed (e.g. multithreaded application requirement).
- As a guideline deploy multiple CPU VMs when there is at least a 2:1 ratio between virtual and physical CPU requirements (e.g. dual core VM, have quad core Host. Quad core VM have 8 core Host).
- There is no support in ESX for virtual USB devices (even though there is in VMware Workstation).
- www.digi.com have a USB to TCP/IP (5xUSB, 1xRJ45 - 10/100Mb Ethernet) converter - called AnywhereUSB. Software can be installed in the VM which provides access to the USB device over the VM's network interface.
No comments:
Post a Comment