What is build number of ESXI and server model ? Can you post the below logs from host

cat /var/log/vmkernel.log | ipmi

After reading http://kb.vmware.com/kb/2003322 and doing some experimentation I'm trying to figure out if it is possible to use Host Profiles to configure syslog to use a local VMFS datastore. I have come up with these approaches, none of which do what I want:

1) Create a local VMFS datastore, e.g. "Datastore1", on each host and set "Syslog.global.logDir" to "[Datastore1] /Syslog". The problem with this approach is that I end up with name collision on the Storage view in vCenter.

2) Create a local VMFS datastore, e.g. "<ESXi hostname>--Datastore1", on each host which avoids the name collision problem, but then I can't (apparently) use "Host Profiles".

3) Set "Syslog.global.logDir"  to some shared storage and set "Syslog.global.logDirUnique" to True, but then this isn't using a local VMFS datastore.

My concern is that my shared storage is all IP based (both iSCSI and NFS). I was hoping to use a local datastore to add some resiliency to syslog.

Thanks.

vobd.log

2017-07-18T04:42:55.080Z: An event (esx.audit.shell.enabled) could not be sent immediately to hostd; queueing for retry.

2017-07-18T04:43:35.110Z: [GenericCorrelator] 125231229us: [vob.user.host.boot] Host has booted.

2017-07-18T04:43:35.110Z: [UserLevelCorrelator] 125231229us: [vob.user.host.boot] Host has booted.

2017-07-18T04:43:35.110Z: [UserLevelCorrelator] 125231613us: [esx.audit.host.boot] Host has booted.

vmkernel.log

2017-07-17T17:30:54.327Z cpu23:3033759)lsi_mr3: mfi_TaskMgmt:560: Processing taskMgmt abort for device: vmhba1:C2:T0:L0

2017-07-17T17:30:54.327Z cpu23:3033759)lsi_mr3: mfi_TaskMgmt:574: ABORT

2017-07-17T17:30:54.439Z cpu23:3033759)lsi_mr3: mfi_TaskMgmt:560: Processing taskMgmt abort for device: vmhba1:C2:T0:L0

2017-07-17T17:30:54.439Z cpu23:3033759)lsi_mr3: mfi_TaskMgmt:574: ABORT

2017-07-17T17:30:54.551Z cpu23:3033759)lsi_mr3: mfi_TaskMgmt:560: Processing taskMgmt abort for device: vmhba1:C2:T0:L0

2017-07-17T17:30:54.551Z cpu23:3033759)lsi_mr3: mfi_TaskMgmt:574: ABORT

2017-07-17T17:30:54.663Z cpu23:3033759)lsi_mr3: mfi_TaskMgmt:560: Processing taskMgmt abort for device: vmhba1:C2:T0:L0

2017-07-17T17:30:54.663Z cpu23:3033759)lsi_mr3: mfi_TaskMgmt:574: ABORT

2017-07-17T17:30:54.775Z cpu23:3033759)lsi_mr3: mfi_TaskMgmt:560: Processing taskMgmt abort for device: vmhba1:C2:T0:L0

2017-07-17T17:30:54.775Z cpu23:3033759)lsi_mr3: mfi_TaskMgmt:574: ABORT

2017-07-17T17:30:54.887Z cpu23:3033759)lsi_mr3: mfi_TaskMgmt:560: Processing taskMgmt abort for device: vmhba1:C2:T0:L0

2017-07-17T17:30:54.887Z cpu23:3033759)lsi_mr3: mfi_TaskMgmt:574: ABORT

2017-07-17T17:30:54.999Z cpu23:3033759)lsi_mr3: mfi_TaskMgmt:560: Processing taskMgmt abort for device: vmhba1:C2:T0:L0

2017-07-17T17:30:54.999Z cpu23:3033759)lsi_mr3: mfi_TaskMgmt:574: ABORT

2017-07-17T17:30:55.111Z cpu23:3033759)lsi_mr3: mfi_TaskMgmt:560: Processing taskMgmt abort for device: vmhba1:C2:T0:L0

2017-07-17T17:30:55.111Z cpu23:3033759)lsi_mr3: mfi_TaskMgmt:574: ABORT

2017-07-17T17:30:55.223Z cpu23:3033759)lsi_mr3: mfi_TaskMgmt:560: Processing taskMgmt abort for device: vmhba1:C2:T0:L0

2017-07-17T17:30:55.223Z cpu23:3033759)lsi_mr3: mfi_TaskMgmt:574: ABORT

2017-07-17T17:30:55.335Z cpu23:3033759)lsi_mr3: mfi_TaskMgmt:560: Processing taskMgmt abort for device: vmhba1:C2:T0:L0

2017-07-17T17:30:55.335Z cpu23:3033759)lsi_mr3: mfi_TaskMgmt:574: ABORT

2017-07-17T17:30:55.447Z cpu23:3033759)lsi_mr3: mfi_TaskMgmt:560: Processing taskMgmt abort for device: vmhba1:C2:T0:L0

2017-07-17T17:30:55.447Z cpu23:3033759)lsi_mr3: mfi_TaskMgmt:574: ABORT

2017-07-17T17:30:55.559Z cpu23:3033759)lsi_mr3: mfi_TaskMgmt:560: Processing taskMgmt abort for device: vmhba1:C2:T0:L0

2017-07-17T17:30:55.559Z cpu23:3033759)lsi_mr3: mfi_TaskMgmt:574: ABORT

2017-07-17T17:30:55.671Z cpu23:3033759)lsi_mr3: mfi_TaskMgmt:560: Processing taskMgmt abort for device: vmhba1:C2:T0:L0

2017-07-17T17:30:55.671Z cpu23:3033759)lsi_mr3: mfi_TaskMgmt:574: ABORT

2017-07-17T17:30:55.783Z cpu23:3033759)lsi_mr3: mfi_TaskMgmt:560: Processing taskMgmt abort for device: vmhba1:C2:T0:L0

2017-07-17T17:30:55.783Z cpu23:3033759)lsi_mr3: mfi_TaskMgmt:574: ABORT

2017-07-17T17:30:55.895Z cpu23:3033759)lsi_mr3: mfi_TaskMgmt:560: Processing taskMgmt abort for device: vmhba1:C2:T0:L0

2017-07-17T17:30:55.895Z cpu23:3033759)lsi_mr3: mfi_TaskMgmt:574: ABORT

2017-07-17T17:31:26.791Z cpu65:65988)lsi_mr3: mfi_TaskMgmt:560: Processing taskMgmt virt reset for device: vmhba1:C2:T0:L0

2017-07-17T17:31:26.791Z cpu65:65988)lsi_mr3: mfi_TaskMgmt:564: VIRT_RESET cmd # 330974832

2017-07-17T17:31:26.791Z cpu65:65988)lsi_mr3: mfi_TaskMgmt:565: Virtual Reset not implemented, calling fusion reset

2017-07-17T17:31:26.791Z cpu65:65988)lsi_mr3: fusionWaitForOutstanding:2943: megasas: [0]waiting for 0 commands to complete

2017-07-17T17:31:29.793Z cpu23:3033759)WARNING: VSCSI: 3488: handle 8258(vscsi0:0):WaitForCIF: Issuing reset;  number of CIF:33

2017-07-17T17:31:29.793Z cpu23:3033759)WARNING: VSCSI: 2645: handle 8258(vscsi0:0):Ignoring double reset

2017-07-17T17:31:33.594Z cpu41:2508812)lsi_mr3: mfi_TaskMgmt:560: Processing taskMgmt abort for device: vmhba1:C2:T0:L0

2017-07-17T17:31:33.594Z cpu41:2508812)lsi_mr3: mfi_TaskMgmt:574: ABORT

2017-07-17T17:31:57.465Z cpu65:65988)lsi_mr3: mfi_TaskMgmt:560: Processing taskMgmt virt reset for device: vmhba1:C2:T0:L0

2017-07-17T17:31:57.465Z cpu65:65988)lsi_mr3: mfi_TaskMgmt:564: VIRT_RESET cmd # 330975350

2017-07-17T17:31:57.465Z cpu65:65988)lsi_mr3: mfi_TaskMgmt:565: Virtual Reset not implemented, calling fusion reset

2017-07-17T17:31:57.465Z cpu65:65988)lsi_mr3: fusionWaitForOutstanding:2943: megasas: [0]waiting for 0 commands to complete

2017-07-17T17:32:04.646Z cpu58:2508812)lsi_mr3: mfi_TaskMgmt:560: Processing taskMgmt abort for device: vmhba1:C2:T0:L0

2017-07-17T17:32:04.646Z cpu58:2508812)lsi_mr3: mfi_TaskMgmt:574: ABORT

2017-07-17T17:32:27.467Z cpu65:65988)lsi_mr3: mfi_TaskMgmt:560: Processing taskMgmt virt reset for device: vmhba1:C2:T0:L0

2017-07-17T17:32:27.467Z cpu65:65988)lsi_mr3: mfi_TaskMgmt:564: VIRT_RESET cmd # 330975591

2017-07-17T17:32:27.467Z cpu65:65988)lsi_mr3: mfi_TaskMgmt:565: Virtual Reset not implemented, calling fusion reset

2017-07-17T17:32:27.467Z cpu65:65988)lsi_mr3: fusionWaitForOutstanding:2943: megasas: [0]waiting for 0 commands to complete

2017-07-17T17:32:35.618Z cpu50:2508812)lsi_mr3: mfi_TaskMgmt:560: Processing taskMgmt abort for device: vmhba1:C2:T0:L0

2017-07-17T17:32:35.618Z cpu50:2508812)lsi_mr3: mfi_TaskMgmt:574: ABORT

2017-07-17T17:32:58.464Z cpu65:65988)lsi_mr3: mfi_TaskMgmt:560: Processing taskMgmt virt reset for device: vmhba1:C2:T0:L0

2017-07-17T17:32:58.464Z cpu65:65988)lsi_mr3: mfi_TaskMgmt:564: VIRT_RESET cmd # 330976073

2017-07-17T17:32:58.464Z cpu65:65988)lsi_mr3: mfi_TaskMgmt:565: Virtual Reset not implemented, calling fusion reset

2017-07-17T17:32:58.464Z cpu65:65988)lsi_mr3: fusionWaitForOutstanding:2943: megasas: [0]waiting for 0 commands to complete

2017-07-17T17:33:06.586Z cpu44:2508812)lsi_mr3: mfi_TaskMgmt:560: Processing taskMgmt abort for device: vmhba1:C2:T0:L0

2017-07-17T17:33:06.586Z cpu44:2508812)lsi_mr3: mfi_TaskMgmt:574: ABORT

you are using lsi_mr3 to connect to local storage

HBA Name  Driver   Link State  UID                   Capabilities  Description

------------------------------------------------------------------------------

vmhba0    lsi_mr3  link-n/a    sas.500605b00c818660                (0000:06:00.0) Avago (LSI) MegaRAID SAS Invader Controller

vmhba1    lsi_mr3  link-n/a    sas.500605b00cb1a1d0                (0000:10:00.0) Avago (LSI) MegaRAID SAS Invader Controller

vmhba32   vmkusb   link-n/a    usb.vmhba32                         () USB

can you check the driver and firmware for the lsi_mr3 for the storage by following the kb and compare with vmware compatibility list

Determining Network/Storage firmware and driver version in ESXi 4.x and later (1027206) | VMware KB

Name                           Version                              Vendor  Acceptance Level  Install Date

----------------------------------------------------------------------------------------------------------

lsi-mr3                        6.912.12.00-1OEM.600.0.0.2768847     Avago   VMwareCertified   2017-06-02

Thanks,

MS

Hi,

Congrats on the release, installed and testing! Exciting indeed.

As the subject says, I think the REST interface should require authentication and yes I read:

API Considerations

 

This feature is experimental and should not be used in production systems. In addition, there are several specific noteworthy deployment considerations:

 

• The vmrest service will run as the user who started it. ‘sudo vmrest’ would make the root user run the service, for example.
• The service does not provide authentication. Access to the network path where the API resides should be restricted if security is a concern at this time.
• HTTP requests are not encrypted.

 

Telling the user to firewall his machine sadly isn't sufficient.

Let me tell you what I did.

I created a new VM, played with it. Worked great, looks cool in the new GUI.

Then started the rest interface via ./vmrest and pointed a browser to my test host from another machine in the network.

Listing VMs? Works great too.

Hmm.. what's that? Deleting VMs?

First time I tried it told me the VM was locked, but on the second time it was a success.

So that means one can remotely delete VMs!

Let that sink in for a while.

You install a tool that enables the REST interface on your behalf. Most people won't know that it was started and not all tools written have security in mind.

Then a malicious actor scans your network, finds the standard port, points a browser to it and lists your VMs.

While that is scary already.

There's NO additional credentials required to delete a VM!

OK for a beta, but please PLEASE add some extra authentication requirement before final release.

-

Wil

Hello,

Looking at the symptoms, this seems similar to During Mirage Base Layer Assignment, CVD status indicates: Waiting for Service. (2067660) | VMware KB

If this resolves the issue please let me know.

I did make sure it was connected, that didn't change anything?

any other ideas?

ESXi 6.5.0 (Build 5310538)

Supermicro X9DR3-F

Here is the log from one of the ESXi hosts.

2017-07-13T23:19:53.287Z cpu0:65536)VisorFSTar: 1954: ipmi_ipm.v00 for 0xa17f bytes
2017-07-13T23:19:53.287Z cpu0:65536)VisorFSTar: 1954: ipmi_ipm.v01 for 0x1417f bytes
2017-07-13T23:19:53.287Z cpu0:65536)VisorFSTar: 1954: ipmi_ipm.v02 for 0x1917f bytes
2017-07-13T23:20:21.052Z cpu1:65890)Activating Jumpstart plugin ipmi.
2017-07-13T23:20:21.063Z cpu2:66368)Loading module ipmi ...
2017-07-13T23:20:21.066Z cpu2:66368)Elf: 2043: module ipmi has license VMware
2017-07-13T23:20:21.068Z cpu2:66368)ipmi: SMBIOS IPMI Entry: Address: 0x0, System Interface: 0, Alignment: 1, Map Type: 1
2017-07-13T23:20:21.068Z cpu2:66368)ipmi: KCS Memory Map: Command Address: 0x41000dc38001 Data Address: 0x41000dc38000.
2017-07-13T23:20:21.515Z cpu0:66368)WARNING: ipmi: WriteStartPhase:217: ipmi: Timed out waiting for IBF to clear in write start phase.. Error: Timeout
2017-07-13T23:20:21.515Z cpu0:66368)WARNING: ipmi: SysIntKcs_ProcessRequest:577: ipmi: Failure in KCS write start phase. Error: Timeout
2017-07-13T23:20:21.515Z cpu0:66368)WARNING: ipmi: GetDeviceId:735: ipmi: Failed to process Get Device ID request. Error: Timeout
2017-07-13T23:20:21.956Z cpu1:66368)WARNING: ipmi: WriteStartPhase:217: ipmi: Timed out waiting for IBF to clear in write start phase.. Error: Timeout
2017-07-13T23:20:21.956Z cpu1:66368)WARNING: ipmi: SysIntKcs_ProcessRequest:577: ipmi: Failure in KCS write start phase. Error: Timeout
2017-07-13T23:20:21.956Z cpu1:66368)WARNING: ipmi: GetDeviceId:735: ipmi: Failed to process Get Device ID request. Error: Timeout
2017-07-13T23:20:22.402Z cpu1:66368)WARNING: ipmi: WriteStartPhase:217: ipmi: Timed out waiting for IBF to clear in write start phase.. Error: Timeout
2017-07-13T23:20:22.402Z cpu1:66368)WARNING: ipmi: SysIntKcs_ProcessRequest:577: ipmi: Failure in KCS write start phase. Error: Timeout
2017-07-13T23:20:22.402Z cpu1:66368)WARNING: ipmi: GetDeviceId:735: ipmi: Failed to process Get Device ID request. Error: Timeout
2017-07-13T23:20:22.402Z cpu1:66368)WARNING: ipmi: IpmiDriver_Init:208: ipmi: IPMI Device failed to respond to the GET DEVICE ID request. Error: Timeout
2017-07-13T23:20:22.402Z cpu1:66368)WARNING: ipmi: CreateIpmiDrivers:1256: ipmi: Failed to initialize IPMI driver. Error: Timeout
2017-07-13T23:20:22.402Z cpu1:66368)ipmi: No valid IPMI devices were discovered based upon PCI, ACPI or SMBIOS entries, attempting to discover IPMI devices at defaul
t locations
2017-07-13T23:20:22.402Z cpu1:66368)ipmi: KCS Port Map: Command Port: 0xca3 Data Port: 0xca2
2017-07-13T23:20:22.403Z cpu1:66368)Mod: 4968: Initialization of ipmi succeeded with module ID 81.
2017-07-13T23:20:22.403Z cpu1:66368)ipmi loaded successfully.
2017-07-13T23:20:22.410Z cpu1:65890)Jumpstart plugin ipmi activated.
VMB: 323:    name: /ipmi_ipm.v00
VMB: 323:    name: /ipmi_ipm.v01
VMB: 323:    name: /ipmi_ipm.v02
TSC: 503500 cpu0:1)BootConfig: 433: ipmiEnabled = TRUE
2017-07-14T00:45:49.301Z cpu0:65536)VisorFSTar: 1954: ipmi_ipm.v00 for 0xa17f bytes
2017-07-14T00:45:49.302Z cpu0:65536)VisorFSTar: 1954: ipmi_ipm.v01 for 0x1417f bytes
2017-07-14T00:45:49.302Z cpu0:65536)VisorFSTar: 1954: ipmi_ipm.v02 for 0x1917f bytes
2017-07-14T00:46:17.420Z cpu5:65890)Activating Jumpstart plugin ipmi.
2017-07-14T00:46:17.443Z cpu7:66368)Loading module ipmi ...
2017-07-14T00:46:17.446Z cpu7:66368)Elf: 2043: module ipmi has license VMware
2017-07-14T00:46:17.448Z cpu7:66368)ipmi: SMBIOS IPMI Entry: Address: 0x0, System Interface: 0, Alignment: 1, Map Type: 1
2017-07-14T00:46:17.448Z cpu7:66368)ipmi: KCS Memory Map: Command Address: 0x41000dc22001 Data Address: 0x41000dc22000.
2017-07-14T00:46:17.903Z cpu7:66368)WARNING: ipmi: WriteStartPhase:217: ipmi: Timed out waiting for IBF to clear in write start phase.. Error: Timeout
2017-07-14T00:46:17.903Z cpu7:66368)WARNING: ipmi: SysIntKcs_ProcessRequest:577: ipmi: Failure in KCS write start phase. Error: Timeout
2017-07-14T00:46:17.903Z cpu7:66368)WARNING: ipmi: GetDeviceId:735: ipmi: Failed to process Get Device ID request. Error: Timeout
2017-07-14T00:46:18.365Z cpu7:66368)WARNING: ipmi: WriteStartPhase:217: ipmi: Timed out waiting for IBF to clear in write start phase.. Error: Timeout
2017-07-14T00:46:18.365Z cpu7:66368)WARNING: ipmi: SysIntKcs_ProcessRequest:577: ipmi: Failure in KCS write start phase. Error: Timeout
2017-07-14T00:46:18.365Z cpu7:66368)WARNING: ipmi: GetDeviceId:735: ipmi: Failed to process Get Device ID request. Error: Timeout
2017-07-14T00:46:18.792Z cpu7:66368)WARNING: ipmi: WriteStartPhase:217: ipmi: Timed out waiting for IBF to clear in write start phase.. Error: Timeout
2017-07-14T00:46:18.792Z cpu7:66368)WARNING: ipmi: SysIntKcs_ProcessRequest:577: ipmi: Failure in KCS write start phase. Error: Timeout
2017-07-14T00:46:18.792Z cpu7:66368)WARNING: ipmi: GetDeviceId:735: ipmi: Failed to process Get Device ID request. Error: Timeout
2017-07-14T00:46:18.792Z cpu7:66368)WARNING: ipmi: IpmiDriver_Init:208: ipmi: IPMI Device failed to respond to the GET DEVICE ID request. Error: Timeout
2017-07-14T00:46:18.792Z cpu7:66368)WARNING: ipmi: CreateIpmiDrivers:1256: ipmi: Failed to initialize IPMI driver. Error: Timeout
2017-07-14T00:46:18.792Z cpu7:66368)ipmi: No valid IPMI devices were discovered based upon PCI, ACPI or SMBIOS entries, attempting to discover IPMI devices at defaul
t locations
2017-07-14T00:46:18.792Z cpu7:66368)ipmi: KCS Port Map: Command Port: 0xca3 Data Port: 0xca2
2017-07-14T00:46:18.793Z cpu7:66368)Mod: 4968: Initialization of ipmi succeeded with module ID 81.
2017-07-14T00:46:18.793Z cpu7:66368)ipmi loaded successfully.
2017-07-14T00:46:18.800Z cpu5:65890)Jumpstart plugin ipmi activated.

Correct, the other tunnels are stable. 

Here is a sanitized ipsec config.  The "Bad" Site is named as such with a peer id of 1.1.1.1.

vShield Edge IPsec VPN Config:

{

   "ipsec" : {

      "logging" : {

         "enable" : true,

         "logLevel" : "debug"

      },

      "global" : {

         "extension" : null,

         "caCertificates" : [],

         "id" : null,

         "serviceCertificate" : null,

         "pskForDynamicIp" : null,

         "crlCertificates" : []

      },

      "enable" : true,

      "sites" : [

         {

            "localId" : "9.9.9.9",

            "certificate" : null,

            "enabled" : true,

            "encryptionAlgorithm" : "aes256",

            "peerIp" : "2.2.2.2",

            "extension" : null,

            "description" : null,

            "authenticationMode" : "psk",

            "peerId" : "2.2.2.2",

            "enablePfs" : false,

            "localSubnets" : [

               "10.250.48.168/29"

            ],

            "psk" : "****",

            "peerSubnets" : [

               "192.168.6.0/24"

            ],

            "name" : "Good1",

            "localIp" : "9.9.9.9",

            "dhGroup" : "dh5",

            "mtu" : null

         },

         {

            "localIp" : "9.9.9.9",

            "name" : "Good2",

            "peerSubnets" : [

               "192.168.2.0/24"

            ],

            "mtu" : null,

            "dhGroup" : "dh5",

            "description" : null,

            "authenticationMode" : "psk",

            "enablePfs" : false,

            "peerId" : "3.3.3.3",

            "localSubnets" : [

               "10.250.48.168/29"

            ],

            "psk" : "****",

            "peerIp" : "3.3.3.3",

            "extension" : null,

            "certificate" : null,

            "localId" : "9.9.9.9",

            "enabled" : true,

            "encryptionAlgorithm" : "aes"

         },

         {

            "peerIp" : "4.4.4.4",

            "extension" : null,

            "localId" : "9.9.9.9",

            "certificate" : null,

            "enabled" : true,

            "encryptionAlgorithm" : "aes256",

            "name" : "Good3",

            "peerSubnets" : [

               "192.168.4.0/24"

            ],

            "localIp" : "9.9.9.9",

            "dhGroup" : "dh5",

            "mtu" : null,

            "description" : null,

            "authenticationMode" : "psk",

            "peerId" : "4.4.4.4",

            "enablePfs" : false,

            "localSubnets" : [

               "10.250.48.168/29"

            ],

            "psk" : "****"

         },

         {

            "description" : null,

            "authenticationMode" : "psk",

            "enablePfs" : false,

            "peerId" : "1.1.1.1",

            "localSubnets" : [

               "10.250.48.168/29"

            ],

            "psk" : "****",

            "localIp" : "9.9.9.9",

            "name" : "BAD1",

            "peerSubnets" : [

               "192.168.22.0/24"

            ],

            "mtu" : null,

            "dhGroup" : "dh5",

            "certificate" : null,

            "localId" : "9.9.9.9",

            "encryptionAlgorithm" : "aes",

            "enabled" : true,

            "peerIp" : "1.1.1.1",

            "extension" : null

         },

         {

            "mtu" : null,

            "dhGroup" : "dh5",

            "localIp" : "9.9.9.9",

            "peerSubnets" : [

               "172.16.1.0/24",

               "192.168.1.0/24",

               "172.15.1.0/24"

            ],

            "name" : "Good4",

            "psk" : "****",

            "localSubnets" : [

               "10.250.48.168/29"

            ],

            "description" : null,

            "authenticationMode" : "psk",

            "enablePfs" : false,

            "peerId" : "5.5.5.5",

            "extension" : null,

            "peerIp" : "5.5.5.5",

            "encryptionAlgorithm" : "aes256",

            "enabled" : true,

            "certificate" : null,

            "localId" : "9.9.9.9"

         },

         {

            "encryptionAlgorithm" : "aes256",

            "enabled" : true,

            "certificate" : null,

            "localId" : "9.9.9.9",

            "extension" : null,

            "peerIp" : "6.6.6.6",

            "psk" : "****",

            "localSubnets" : [

               "10.250.48.168/29"

            ],

            "authenticationMode" : "psk",

            "description" : null,

            "enablePfs" : false,

            "peerId" : "6.6.6.6",

            "mtu" : null,

            "dhGroup" : "dh5",

            "localIp" : "9.9.9.9",

            "name" : "Good6",

            "peerSubnets" : [

               "192.168.5.0/24"

            ]

         },

         {

            "psk" : "****",

            "localSubnets" : [

               "10.250.48.168/29"

            ],

            "description" : null,

            "authenticationMode" : "psk",

            "enablePfs" : false,

            "peerId" : "7.7.7.7",

            "mtu" : null,

            "dhGroup" : "dh5",

            "localIp" : "9.9.9.9",

            "peerSubnets" : [

               "192.168.21.0/24"

            ],

            "name" : "Good7",

            "encryptionAlgorithm" : "aes",

            "enabled" : true,

            "certificate" : null,

            "localId" : "9.9.9.9",

            "extension" : null,

            "peerIp" : "7.7.7.7"

         }

      ],

      "disableEvent" : false

   }

}

We have a single ESXi 5.5U2 host and a pair of Synology NAS boxes set up as iSCSI LUNs and connected as datastores to the ESXi host. We'll be moving all of that to a new office that has a different IP scheme. My current plan is:

1 - Power off VMs, put host in maintenance mode and power it off.

2 - Change Synologys from Static IP to DHCP and power them off.

3 - In new office space power on Synologys and switch them from DHCP to static IP using the IP scheme of the new office

4 - Power on the ESXi hypervisor and change the IP to use the IP scheme of the new office.

5 - Log in to Vsphere Client and under properties of the iSCSI software adapter remove the old iSCSI server location IPs from Dynamic Discovery tab and add new ones.

Am I missing anything here or are there any potential problems I may run in to with the above plan? Will anything additional be required for the hypervisor to properly see the datastores after all those changes?

Thank you in advance for any help.

I created  a Microsoft  KMS server to activate new VM's and was told that the Vsphere host has to be configured to connect to the KMS server to activate, is there documentation or does anyone know how to do this? I've searched google and have not seen anything. Thanks.

Mitch

Hello,

I was not able to find an API that fully disables time sync.  This blog does have some ways to do it that could work: Completely Disable Time Synchronization for your VM - Virtualize Business Critical Applications - VMware Blogs

But i do not understand, how to see realtime vCPU-to-logicalCPU mapping for each VM?

The only way is to find this info in VMware.log of each virtual machine?

Hello,

After converting to a template, are you able to view were the flat files are stored?

Yes I am, but in the trial, is there a limiation of features that will be enabled ? -Thanks

Hello,

The processor counter, processor queue length, do work correctly in the guest OS as long as VMware Tools and are updated to the latest version. To get the counter to react it may take a pretty high load on the virtual machine.  Let me know if this answers the question.

You are right! The virtual machines are on and seems that some of them are causing the issue. I'll do another try with virtual machines down. Thanks a lot!

Reading the article, it appears that these are not critical issues. The problem with that is that our VMWare instance feeds into SolarWinds, which picks up the hardware alerts as a critical problem. 

Is there a way to turn off the Memory Sensors that show ECC logging limit/Deassert messages?

Just getting started with UEM. Attempting to create and remove shortcuts. Trying to create a shortcut based on the existence of an executable and/or the user's membership in a specific security group. In some cases, the application is part of an AppStack, which is configured to be assigned to only those users who are part of a specific security group.  In that case, the shortcut would be provided based on the existence of the executable and being a member of the security group.  In other cases, the shortcut might be created just based on the existence of the executable or membership in a security group.

No problem creating the shortcut based on the conditions. However, if we remove the user from the security group, the executable is removed, etc., I expected the shortcut to be removed as well. Instead, there is still a shortcut present. It is non-functional and displayed with a generic icon (shown below), and if the user clicks on the shortcut, they get the message "The item that this shortcut refers to has been changed or moved, so this shortcut will no longer work properly. Do you want to delete the shortcut?".

This is the UEM setup for the shortcut.

...and the conditions:

These are the folder redirection settings. My attempts to create shortcuts are on the desktop and that is not being redirected.

So if the user is removed from the security group (AppV_WinSCP), the Attstack that provided the executable is no longer assigned, so the executable is no longer present (and since the user is no longer part of the security group, that condition fails too). The UEM logs show it is "skipping" the shortcut, but it doesn't appear that any existing shortcut is actually deleted.

Should I expect that a shortcut previously created by UEM when the user was a member of the security group and/or the executable was accessible should be deleted when either (or both) of those conditions are no longer true? 

Bottom line - how can I get rid of the shortcut if the shortcut they were once entitled to is no longer valid/assigned?

Thanks!

I had the same error and ended up following these instructions to fix:

https://tinkertry.com/fix-xeon-d-inaccurate-cim-data-default-in-vsphere65#how-to-restore-full-health-status-monitoring-on-xeon-d

Dear all

Hi

i have downloaded latest version of vRealize-Operations-Manager-Appliance-6.6.0.5707161_OVF10.ova in documents i read it can monitor middleware, and applications running in your physical, virtual, and cloud environments and others that i have attached in pic but now i could not find any that features in vrealize how can use or enable that features ????

BR