thhg's Posts

hbrsrv will not staart Error in log is :   2023-11-13T22:24:51.351Z verbose hbrsrv[01711] [Originator@6876 sub=Crypto] Loading Private Key '/etc/vmware/ssl/hbrsrv_broker_private.pem' 2023-11-13T2... See more...
hbrsrv will not staart Error in log is :   2023-11-13T22:24:51.351Z verbose hbrsrv[01711] [Originator@6876 sub=Crypto] Loading Private Key '/etc/vmware/ssl/hbrsrv_broker_private.pem' 2023-11-13T22:24:51.351Z verbose hbrsrv[01711] [Originator@6876 sub=Crypto] Loading Public Key '/etc/vmware/ssl/hbrsrv_broker_public.pem' 2023-11-13T22:24:51.352Z panic hbrsrv[01711] [Originator@6876 sub=Main] [0] Could not compute a reasonable expiration time for private key '/etc/vmware/ssl/hbrsrv_broker_private.pem'   I've recreated the SSL certificate but get the same error The dates on the 2 PEM files are earlier that the crt file
Why does Task Manager show CPU information differently for VMs on the same ESXi 6.7 host ? Both are Windows 2019 servers eg : VM1 : Base Speed : 2.10 GHz / Sockets :1 / Cores : 6 / Logical Process... See more...
Why does Task Manager show CPU information differently for VMs on the same ESXi 6.7 host ? Both are Windows 2019 servers eg : VM1 : Base Speed : 2.10 GHz / Sockets :1 / Cores : 6 / Logical Processors : 6 / Virtualization : Not Capable / L1 cache : 64 KB / L2 cache : 1.0 MB / L3 Cache : 16.5 MB   VM2 : Base Speed 2.10 GHz / Socket : 1 / Virtual Processors : 2 / Virtual Machine : Yes / L1 Cache : N/A
Am unable to register replication appliance with VCentre server. Get cryptic error : ERROR Operation Failed A general system error occurred: Failed to register VRMS. Operation ID: 96502d80-7c44-... See more...
Am unable to register replication appliance with VCentre server. Get cryptic error : ERROR Operation Failed A general system error occurred: Failed to register VRMS. Operation ID: 96502d80-7c44-432d-b522-d2d20acc45cc   Have tried the following combinations New 8.4.12505 and New VCSA 7.0.0 New 8.4.12505 and New VCSA 7.0.0.6000 New 8.5.0.12709 and New VCSA 7.0.0.6000 These are brand new installs of each appliance / VCSA - always get the same error ' I have noted the hbrsrv service is not running (perhaps it does not run until the VSR is configured)  
Would like to sync our existing replication storage area to another location Is there a build in rsync in ESXi or other method to clone our replication VMFS volume to another WAN based location   ... See more...
Would like to sync our existing replication storage area to another location Is there a build in rsync in ESXi or other method to clone our replication VMFS volume to another WAN based location   Steve
  2 VCenter 7.03 servers that are linked I added VSR 8.5 and during the config process added it to one of the VCS instances When I create a new Replication, it only shows VMs from the 1 VCenter ... See more...
  2 VCenter 7.03 servers that are linked I added VSR 8.5 and during the config process added it to one of the VCS instances When I create a new Replication, it only shows VMs from the 1 VCenter server   How do I get VSR to see the VMs from all the VCenter Servers ?
Running 8.4 Am able to access replications / add / edit replications. All other functions appear to be working ok In VCenter Server and go into Menu / Site Recovery, It shows message "Not Accessibl... See more...
Running 8.4 Am able to access replications / add / edit replications. All other functions appear to be working ok In VCenter Server and go into Menu / Site Recovery, It shows message "Not Accessible" However, I can click on the Site Recovery link and login into Site Recovery using my administrator@vsphere.local   But, cannot login into VAMI on port 5480 using the same administrator@vsphere.local credentials I get the message :  Cannot complete login due to an incorrect token, user name, or password   I'm able to login as root on the console   Steve
Host is a Windows 2016 server (physical) Not sure what you mean by 'destination format'  
Running Client 6.2 P2V conversion Cloning of Drives completes fine and then 2 Warnings and an Error Warning: Unable to update BCD on the destination machine's system volume. Warning: Unable to up... See more...
Running Client 6.2 P2V conversion Cloning of Drives completes fine and then 2 Warnings and an Error Warning: Unable to update BCD on the destination machine's system volume. Warning: Unable to update drive letters for the destination volume layout. Processing the reconfiguration datastore. Error: An error occurred during reconfiguration.   The first Log error is : Unable to update BCD on the destination machine's system volume   Not sure where to start here - is this a source or destination issue   Steve      
I'm getting these Warnings in the Windows 2016 event log Event 129 Reset to device, \Device\RaidPort0, was issued. This VM is running on 6.7 patched with latest VM Tools VM is configured for LSI L... See more...
I'm getting these Warnings in the Windows 2016 event log Event 129 Reset to device, \Device\RaidPort0, was issued. This VM is running on 6.7 patched with latest VM Tools VM is configured for LSI Logic SAS Windows driver is : SAS 3000 8 port with 1068 lsi_sas.sys : 1.34.03.83   Steve
I have 6 hosts with LSI 9260 RAID cards They are all using the megaraid_sas driver (6.603.55.00.2) The megaraid_sas driver is deprecated in 6.7 How do I get the LSI card to use the built-in ... See more...
I have 6 hosts with LSI 9260 RAID cards They are all using the megaraid_sas driver (6.603.55.00.2) The megaraid_sas driver is deprecated in 6.7 How do I get the LSI card to use the built-in ESXi LSI_MR3 driver instead Steve
ESXi 6.7 patched ... All VMs are Server 2008 R2 with VMXNET3 adapters connected to the same VSwitch 1 system is RDP Using the Resource Monitor in Windows, we see TCP Latency on connectio... See more...
ESXi 6.7 patched ... All VMs are Server 2008 R2 with VMXNET3 adapters connected to the same VSwitch 1 system is RDP Using the Resource Monitor in Windows, we see TCP Latency on connections between RDP and connected servera (Exchange / Printer Server, etc) gradually climb to between 200 and 250ms Performance is just being killed I am testing with 1 user on RDP and no other users connected and see these results ESXTOP show no dropped packets Is this a windows parameter setting in : 1. VMXNET3 2. NETSH global setting 3. ESXI NIC setting ? Steve
Still no joy ... here are 2 examples esxcli software vib update -n /tmp/lsi-mr3-7.707.11.00-1OEM.670.0.0.8169922.x86_64.vib [Exception] Use of -n/--vibname requires use of -d/--depot. Pl... See more...
Still no joy ... here are 2 examples esxcli software vib update -n /tmp/lsi-mr3-7.707.11.00-1OEM.670.0.0.8169922.x86_64.vib [Exception] Use of -n/--vibname requires use of -d/--depot. Please refer to the log file for more details. esxcli software vib update -v /tmp/lsi-mr3-7.707.11.00-1OEM.670.0.0.8169922.x86_64.vib --no-sig-check [DependencyError] VIB Avago_bootbank_lsi-mr3_7.707.11.00-1OEM.670.0.0.8169922 requires vmkapi_2_5_0_0, but the requirement cannot be satisfied within the ImageProfile. Please refer to the log file for more details.
ESXi 6.7 fully patched Was trying to update an LSI driver and got the following message : esxcli software vib install -v /tmp/lsi-mr3-7.707.11.00-1OEM. 670.0.0.8169922.x86_64.vib --no-sig... See more...
ESXi 6.7 fully patched Was trying to update an LSI driver and got the following message : esxcli software vib install -v /tmp/lsi-mr3-7.707.11.00-1OEM. 670.0.0.8169922.x86_64.vib --no-sig-check [DependencyError] VIB Avago_bootbank_lsi-mr3_7.707.11.00-1OEM.670.0.0.8169922 requires vmkapi_2_5_0_0, but the requirement cannot be satisfied within the ImageProfile. VIB VMware_locker_tools-light_10.2.0.7253323-8169922 requires esx-version >= 6.6.0, but the requirement cannot be satisfied within the ImageProfile. Please refer to the log file for more details. Where do I find the updated vmkapi ? Thanks, Steve
ESXi 6.0 VM Backup Exec 16 fails with PCI passthough device configured on the VM.  Once the device is removed, the backup runs fine. The error seems to be coming from the ESXi end. Error... See more...
ESXi 6.0 VM Backup Exec 16 fails with PCI passthough device configured on the VM.  Once the device is removed, the backup runs fine. The error seems to be coming from the ESXi end. Error 0xe00095a6 : Pperation failed because the VCenter or ESX server reported a problem with the virtual machine's current state and then A quiesced snapshot could not be created for the virtual machine Can VM's with passthrough devices be backed up ? (or do I have to use the Replication service) Steve
Have rebooted both Host (to be added) and VCSA No change Just wondering if there's a log I should be looking at on the VCSA side
n capture
No Luck with FQDN - same message
Have always use IP addresses Will give it FQDN a try
IP address
Log is attached