robert_eckdale's Posts

Configuring the VMware VirtualCenter Management Webservices to run as the same service account as used by  VMware VirtualCenter Server resolved the issue. I should also note that I am certain, that prior to the update both services were configured to use the same AD Domain user. Thanks for the solution.

Shortly after my original post I did just that...simply renamed the machine in vCenter. This in combination with logging into the appliance and renaming the host appears to have been successfull. We'll see if this holds true, for a rather simple work around. Note: I have performed only basic testing...repeat at your own risk.

To be clear: I've deployed and configured a vShield Manager appliance. Then, via the vShield Manager Web console I've 'installed' the vShield Zones service onto an ESXi host. As part of this installation a vShield Service VM is created using the following naming convention: vShield-FW-host.fqdn. While this automatically generated VM name is fine, it does not follow my server naming convention; so I'd prefer to have the VM created with a specific name.

Similar situtation. ESXi v4.1 (installed on internal USB key) running on HP BL490c blades connected to an HP EVA 8400. Several of the ESXi hosts are running MSCS VMs (cluster across boxes) utilizing RDM LUNs. MSCS are a mix of 2003 R2 and 2008 R2, but ESXi hosts are running one or the other. I.E. No host has a 2003 and 2008 R2 MSCS VM. A reboot of a host with no RDM LUNs takes approximately 1:30. A reboot of a host with MSCS (2008 R2) LUNS takes the same amount of time. A reboot of a host with MSCS (2003 R2) RDM LUNs take 15+ minutes with a very long pause on 'vmw_satp_eva loaded'. I ran a quick test on the same host, here are the results Test 1 Total number of LUNS: 15 Number of RDM LUNS: 6 Number of MSCS (2003 R2) RDM LUNS: 6 Boot time: 18:10 Test 2 Total number of LUNS: 10 Number of RDM LUNS: 0 Number of MSCS (2003 R2) RDM LUNS: 0 Boot time: 1:25 Test 3 Total number of LUNS: 11 Number of RDM LUNS: 1 Number of MSCS (2003 R2) RDM LUNS: 1 Boot time: 5:42

I am experiencing the exact same behavior with the HP BL 490c G6 and Flex-10 + Virtual Connect modules. I was able to install ESXi 4 Update 2 on 11 blades across 2 x c7000 enclosure without issue. However the install stops at loading bnx2 on two blades, each in seperate enclosures. The blades are all identical. I have reviewed all BIOS configurations, firmware versions etc. (multiple times) and have found no discernable difference. I have found that if I remove the assigned Virtual Connect server profile the install completes. However once I assigning a Virtual Connect server profile the system fails to boot indicating "No compatible network adapter found."

As far as I know this is not possible via PowerCLI...which is why I use vMA to configure my ESXi 4.x hosts for roundrobin (EVA 8100). # Set Default PSP for VMW_SATP_ALUA to VMW_PSP_RR (Round Robin) esxcli nmp satp setdefaultpsp --satp VMW_SATP_ALUA --psp VMW_PSP_RR # Set IO Operation Limit to 1 (Default is 1000) [and enable use of Non-optimal paths (this may not be a good idea)]. esxcli nmp roundrobin setconfig --type=iops --iops 1 --useANO 1 --device <device.id>