mike-p's Posts

It‘s a 2+2 node cluster. The baseline system worked fine until now. There was no reason to change to image based updates. Especially because the powershell cmd‘s (get-compliance) are more developed t... See more...
It‘s a 2+2 node cluster. The baseline system worked fine until now. There was no reason to change to image based updates. Especially because the powershell cmd‘s (get-compliance) are more developed than for image based updates. There are more details to request.
I have a vSAN8 OSA Cluster which is still managed by baselines. After the upgrade the predefined vSAN baseline is missing. I did a reset of the UM db but the the baseline does not occur anymore (gui ... See more...
I have a vSAN8 OSA Cluster which is still managed by baselines. After the upgrade the predefined vSAN baseline is missing. I did a reset of the UM db but the the baseline does not occur anymore (gui and powershell).
I have a stretched cluster and need to change the connection between the locations. Theoretically i need to set all hosts of one location in maintenance mode. All vm's are distributed only with PFTT=... See more...
I have a stretched cluster and need to change the connection between the locations. Theoretically i need to set all hosts of one location in maintenance mode. All vm's are distributed only with PFTT=1 , SFTT=0. Which impact would i expect if i disable HA or Admission Control instead of moving all vm's? I will get a vSAN alarm but the access to the objects is the same as maintenance mode with "ensure accessibility". The Advantage wold be that i can use the resources of all hosts.    
It seems a problem with the powershell command. If you use 'esxcli hardware pci list' at the host the output is correct: 0000:1b:00.0 Address: 0000:1b:00.0 Segment: 0x0000 Bus: 0x1b Slot: 0x00 ... See more...
It seems a problem with the powershell command. If you use 'esxcli hardware pci list' at the host the output is correct: 0000:1b:00.0 Address: 0000:1b:00.0 Segment: 0x0000 Bus: 0x1b Slot: 0x00 Function: 0x0 Vendor Name: VMware Inc. Device Name: vmxnet3 Virtual Ethernet Controller Configured Owner: VMkernel Current Owner: VMkernel Vendor ID: 0x15ad Device ID: 0x07b0 SubVendor ID: 0x15ad SubDevice ID: 0x07b0 Device Class: 0x0200 In the csv the fields are empty : "R750 vSAN Ready Node","vmnic0","4.1.13.0-4vmw.802.0.0.22380479","bc 1.39 ncsi 1.5.42.0","Broadcom Corporation NetXtreme BCM5720 Gigabit Ethernet","0","0","0","0"  
We have problems to run any tools which scan the inventory of ESXi 8 hosts. vDocumentation and asBuiltReport do not work anymore. I am not sure if this is the right forum. This seems to be an SDK pro... See more...
We have problems to run any tools which scan the inventory of ESXi 8 hosts. vDocumentation and asBuiltReport do not work anymore. I am not sure if this is the right forum. This seems to be an SDK problem: New-AsBuiltReport: Cannot bind argument to parameter 'Rows' because it is an empty collection. At line:1 char:1 New-AsBuiItReport -Report VMware.vSphere -Target _vCenter_ + CategoryInfo: NotSpecified: (:) [Write-Error],WriteErrorException + FullyQualifiedErrorId : Microsoft.PowerShe1.Commands.WriteErrorException,New-AsBuiltReport  05.10.2023 14:40:48 PowerCLI Version: Name Version ---- ------- VMware.Vim 8.1.0.21605554 VMware.VimAutomation.Cis.Core 13.1.0.21605976 VMware.VimAutomation.Common 13.1.0.21605386 VMware.VimAutomation.Core 13.1.0.21606170 VMware.VimAutomation.Sdk 13.1.0.21605170  05.10.2023 14:40:48 vDocumentation Version: Name Version ---- ------- vDocumentation 2.4.7  05.10.2023 14:40:48 Validate connection to a vSphere server Connected to vcenter_server  05.10.2023 14:40:48 Gather host list  05.10.2023 14:40:48 Executing Cmdlet using VMhost parameter set Gathering host list...  05.10.2023 14:40:48 Get-VMHost Finished execution  05.10.2023 14:40:48 Validate export switches and folder path  05.10.2023 14:40:48 -folderPath parameter is Null or Empty  Folder Path (-folderPath) was not specified for saving exported data. The current location: 'C:\Users\Admin' will be used    Module in path "C:\Program Files\WindowsPowerShell\Modules\ImportExcel\7.8.5\ImportExcel.psm1" loaded  05.10.2023 14:40:48 ImportExcel Module available  05.10.2023 14:40:48 Validating access to VMware HCL site...  GET https://www.vmware.com/resources/compatibility/js/data_io.js? with 0-byte payload  received -1-byte response of content type application/javascript  GET https://www.vmware.com/resources/compatibility/search.php?deviceCategory=io with 0-byte payload  received -1-byte response of content type text/html; charset=UTF-8 05.10.2023 14:41:11 host1.mydns.local Connection State: Connected  05.10.2023 14:41:12 Get-EsxCli Finished execution Gathering information from host1.mydns.local ...  05.10.2023 14:41:12 Get-AdvancedSetting Finished execution  05.10.2023 14:41:13 Gathering IO device HCL details...  05.10.2023 14:41:13 Main code execution completed  05.10.2023 14:41:13 Script Duration: 00:00:24.8149624  05.10.2023 14:41:13 No information gathered
I deleted some files manually but I had to escalade to root privilege. Than I updated to 8.6.0.21134460 and now I hope that the log rotation will work properly.  ]# df -h Filesystem Size Used Avail... See more...
I deleted some files manually but I had to escalade to root privilege. Than I updated to 8.6.0.21134460 and now I hope that the log rotation will work properly.  ]# df -h Filesystem Size Used Avail Use% Mounted on devtmpfs 3.9G 0 3.9G 0% /dev tmpfs 3.9G 28K 3.9G 1% /dev/shm tmpfs 3.9G 748K 3.9G 1% /run tmpfs 3.9G 0 3.9G 0% /sys/fs/cgroup /dev/sda4 14G 2.6G 11G 21% / tmpfs 3.9G 172K 3.9G 1% /tmp /dev/sda2 238M 25M 201M 11% /boot /dev/mapper/support_vg-logs 975M 571M 354M 62% /opt/vmware/logs /dev/mapper/support_vg-heapdump 3.9G 96K 3.7G 1% /opt/vmware/heapdump /dev/mapper/support_vg-vrmsdb 9.8G 68M 9.2G 1% /var/lib/vrmsdb /dev/mapper/support_vg-support 2.0G 320M 1.5G 18% /opt/vmware/support tmpfs 798M 0 798M 0% /run/user/666   Regards Mike
Hi, on my replication appliance 3.4 the log partition ist full: admin@Replication [ ~ ]$ df -h Filesystem Size Used Avail Use% Mounted on devtmpfs 3.9G 0 3.9G 0% /dev tmpfs 3.9G 0 3.9G 0% /dev/s... See more...
Hi, on my replication appliance 3.4 the log partition ist full: admin@Replication [ ~ ]$ df -h Filesystem Size Used Avail Use% Mounted on devtmpfs 3.9G 0 3.9G 0% /dev tmpfs 3.9G 0 3.9G 0% /dev/shm tmpfs 3.9G 720K 3.9G 1% /run tmpfs 3.9G 0 3.9G 0% /sys/fs/cgroup /dev/sda4 14G 3.4G 9.5G 27% / tmpfs 3.9G 100K 3.9G 1% /tmp /dev/sda2 240M 33M 196M 15% /boot /dev/mapper/support_vg-vrmsdb 9.8G 91M 9.2G 1% /var/lib/vrmsdb /dev/mapper/support_vg-heapdump 3.9G 8.1M 3.7G 1% /opt/vmware/heapdump /dev/mapper/support_vg-support 2.0G 116M 1.7G 7% /opt/vmware/support /dev/mapper/support_vg-logs 976M 976M 0 100% /opt/vmware/logs tmpfs 798M 0 798M 0% /run/user/666 I found this expression in the last release notes of the replication service: Upgrade NEW You cannot upgrade the vSphere Replication appliance to version 8.5 When you try to upgrade the vSphere Replication appliance to version 8.5, the process fails without an error or warning. The problem is observed if your partition for logs (/opt/vmware/logs) is full. Workaround: Clean up the log partition before you upgrade to vSphere Replication 8.5. But I did not find any hint howto clean up the log partition. I checked the content of the partition and it looks like manual deleting of files is not a good idea.  admin@Replication [ /opt/vmware/logs ]$ ls hms lost+found upgrade admin@Replication [ /opt/vmware/logs ]$ cd hms/ -bash: cd: hms/: Permission denied admin@Replication [ /opt/vmware/logs ]$ cd upgrade/ -bash: cd: upgrade/: Permission denied  
I got a feedback from engineering ; This will be fixed in the next 13.1 Release of Powercli. By the meantime you can use this workaround: get-vmhost | get-compliance | select Entity, @{N="Baseli... See more...
I got a feedback from engineering ; This will be fixed in the next 13.1 Release of Powercli. By the meantime you can use this workaround: get-vmhost | get-compliance | select Entity, @{N="Baseline"; E={$_.Baseline.Name}}, Status | ft -AutoSize
Thanks for your help, I found the according documentation: https://core.vmware.com/resource/vsan-stretched-cluster-guide#sec7306-sub5:~:text=The%20following%20two,the%20opposite%20site.    
Hi, i tested it. the objects of both DAG VMs are distributed over the nodes. If I put one node in maintenance mode with the NA option I loose objects of the active vm too.  This is a bit weird beca... See more...
Hi, i tested it. the objects of both DAG VMs are distributed over the nodes. If I put one node in maintenance mode with the NA option I loose objects of the active vm too.  This is a bit weird because this 2 nodes are in different fault domains. I expected that the data will be placed inside one FD. I think I found the reason for this. Originally this was a 2 node stretched cluster and the Raid0 policy was Set to None-stretched Cluster. I changed this now to Site mirroring - stretched cluster: "Defines whether to use standard, stretched or 2 node cluster. In case of stretched clusters whether data is mirrored at both sites (Site mirroring) or whether it's constrained within only one of the sites in the cluster. In case of 2 node cluster the data is mirrored at both hosts." I will wait until the object resync will be executed and check the MM with NA again.        
Yes, i choose this option because the other machines should stay available. 
Hi, i have several customers with small stretched clusters. Some of the vm's are MS Exchange or SQL DAGs or other systems with own HA options which run on a policy of FTT=0. vSAN spreads the objects... See more...
Hi, i have several customers with small stretched clusters. Some of the vm's are MS Exchange or SQL DAGs or other systems with own HA options which run on a policy of FTT=0. vSAN spreads the objects of this vm's on the nodes of each site. If I take one of this nodes in maintenance mode without shutting down the vm's a long process of object evacuation starts. Is it mandatory to power off such machines or is there another option to handle this? Regards Mike
I have a customer with vcsa 7.0.3.00300 In the /storage/log/vmware/analytics directory i found some hprof files. The only kb according this files is for vcsa 6.7x : https://kb.vmware.com/s/article/... See more...
I have a customer with vcsa 7.0.3.00300 In the /storage/log/vmware/analytics directory i found some hprof files. The only kb according this files is for vcsa 6.7x : https://kb.vmware.com/s/article/82483?lang=en_US Is the workaround for version 7 valid ? I need some time to find an update window for the system.
Oh yes, that is really a deep dive. Thanks for your explanation. I will open an SR and reply the results.  Thanks & Regards Mike
Yes, i think an SR is the next option.  Where did you find the properties like .Baseline.CurrentPatches.Count ?
Thanks, yes in general this works, where can I find the other properties like number of missing patches? I tried the next step to run the script on a cluster and changed the entity to $cluster but ... See more...
Thanks, yes in general this works, where can I find the other properties like number of missing patches? I tried the next step to run the script on a cluster and changed the entity to $cluster but got partially error: $cluster = Get-Cluster -Name vsan-cluster PS D:\VMware-HC\code> .\patch-compl-new.ps1 Get-Compliance : 07.10.2022 19:57:13 Get-Compliance fault.SecurityError.summary In D:\VMware-HC\code\patch-compl-new.ps1:1 Zeichen:1 + Get-Compliance -Entity vsan-cluster -Baseline $Baseline | + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : NotSpecified: (:) [Get-Compliance], VimException + FullyQualifiedErrorId : Core_BaseCmdlet_UnknownError,VMware.VumAutomation.Commands.GetCompliance Get-Compliance : 07.10.2022 19:57:13 Get-Compliance fault.SecurityError.summary In D:\VMware-HC\code\patch-compl-new.ps1:1 Zeichen:1 + Get-Compliance -Entity vsan-cluster -Baseline $Baseline | + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : NotSpecified: (:) [Get-Compliance], VimException + FullyQualifiedErrorId : Core_BaseCmdlet_UnknownError,VMware.VumAutomation.Commands.GetCompliance Get-Compliance : 07.10.2022 19:57:13 Get-Compliance fault.SecurityError.summary In D:\VMware-HC\code\patch-compl-new.ps1:1 Zeichen:1 + Get-Compliance -Entity vsan-cluster -Baseline $Baseline | + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : NotSpecified: (:) [Get-Compliance], VimException + FullyQualifiedErrorId : Core_BaseCmdlet_UnknownError,VMware.VumAutomation.Commands.GetCompliance VMHost Status Baseline NumberofPatches ------ ------ -------- --------------- host06.sp.local Compliant Host Security Patches (Predefined) 138 host06.sp.local NotCompliant Critical Host Patches (Predefined) 196 host03.sp.local Compliant Host Security Patches (Predefined) 138 host03.sp.local NotCompliant Critical Host Patches (Predefined) 196 host04.sp.local Compliant Host Security Patches (Predefined) 138 host04.sp.local NotCompliant Critical Host Patches (Predefined) 196 host05.sp.local Compliant Host Security Patches (Predefined) 138 host05.sp.local NotCompliant Critical Host Patches (Predefined) 196 host02.sp.local Compliant Host Security Patches (Predefined) 138 host02.sp.local NotCompliant Critical Host Patches (Predefined) 196 host01.sp.local Compliant Host Security Patches (Predefined) 138 host01.sp.local NotCompliant Critical Host Patches (Predefined) 196
There is another problem (AFAIK get-baseline targets entities not hostnames) get-compliance : 07.10.2022 19:02:43 Get-Compliance Could not find InventoryItem with name 'hostname'. At C:\code\patch-... See more...
There is another problem (AFAIK get-baseline targets entities not hostnames) get-compliance : 07.10.2022 19:02:43 Get-Compliance Could not find InventoryItem with name 'hostname'. At C:\code\patch-compl-new.ps1:1 char:1 + get-compliance -Entity hostname -baseline $Baseline |
It seems that there is a problem :  
Hi Luc, this output is much better. The correct name is displayed: Name Description Id Type TargetType LastUpdateTime NumberOfPatches ---- ----------- -- ---- ---------- -------------- -----------... See more...
Hi Luc, this output is much better. The correct name is displayed: Name Description Id Type TargetType LastUpdateTime NumberOfPatches ---- ----------- -- ---- ---------- -------------- --------------- Host Security Patches (Predefined) A predefined baseline for all security patches for hosts 1 Patch Host 07.10.2022 14:13:21 138 Critical Host Patches (Predefined) A predefined baseline for all critical patches for Hosts 2 Patch Host 07.10.2022 14:13:21 196 but now the compliance state is missing. I run my command on another system with little bit older ESXi versions and get this output  get-vmhost | Get-Compliance -Detailed | ft -autosize Entity                 Baseline           Status            CompliantPatches NotCompliantPatches ------             --------               ------            ---------------- ------------------ esxi-05.mpa.lab    Host Security Patches  Compliant          5                 0 esxi-05.mpa.lab    Critical Host Patches  NotCompliant       51                3 esxi-05.mpa.lab    Non-Critical Host Pa.  NotCompliant       20                32   That is the info i intend to get.     
In order to check the patch compliance i run a simple command sequence: get-vmhost | Scan-Inventory -Verbose -UpdateType HostPatch $Baseline = Get-Baseline -Name 'Non-Critical Host Patches (Predefi... See more...
In order to check the patch compliance i run a simple command sequence: get-vmhost | Scan-Inventory -Verbose -UpdateType HostPatch $Baseline = Get-Baseline -Name 'Non-Critical Host Patches (Predefined)', 'Critical Host Patches (Predefined)', 'Host Security Patches (Predefined)' get-compliance -Entity hostname -baseline $Baseline I get this : Entity   Status        Baseline ------   ------        -------- hostname NotCompliant  VMware.VumAutomation.Types.PatchBaselineImpl hostname Compliant     VMware.VumAutomation.Types.PatchBaselineImpl Why is the Baseline name changed? I get the same result if I do not declare entity or baseline : get-vmhost | Scan-Inventory -Verbose -UpdateType HostPatch get-vmhost | Get-Compliance -Detailed system: Name Value ---- ----- PSVersion 5.1.19041.1682 PSEdition Desktop PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...} BuildVersion 10.0.19041.1682 CLRVersion 4.0.30319.42000 WSManStackVersion 3.0 PSRemotingProtocolVersion 2.3 SerializationVersion 1.1.0.1 Name Version ---- ------- VMware.Vim 7.0.3.19601056 VMware.VimAutomation.Cis.Core 12.6.0.19601368 VMware.VimAutomation.Common 12.7.0.20067789 VMware.VimAutomation.Core 12.7.0.20091293 VMware.VimAutomation.Sdk 12.7.0.20067606 VMware.VimAutomation.Vds 12.7.0.20091295 VMware.VumAutomation 12.7.0.20091294