JDMils_Interact's Posts

JDMils_Interact · ‎12-18-2022

I'm not sure I understand your logic. The process I have outlined is a very simple set of steps to update VMTools repo on the ESXi hosts using vCenter 7 with 6.7 hosts. A lot of people are in the pro...

I'm not sure I understand your logic. The process I have outlined is a very simple set of steps to update VMTools repo on the ESXi hosts using vCenter 7 with 6.7 hosts. A lot of people are in the process of upgrading to vSphere 7.0, however companies like mine, who have 50 vCenters and 500 hosts, sometimes need to patch VMTools vulerabilities quickly and we can't wait until after all the hosts are upgraded. There's no risks involved, it's just a simple way to get the latest VMTools installed on the non-upgraded hosts.

JDMils_Interact · ‎12-15-2022

I'm going to answer my own question, because I found the solution. In order to install a version of VMTools 12.1.0 or 12.1.5 onto all ESXi V6.7 hosts using Lifecycle Manager, of course, with vCenter ...

I'm going to answer my own question, because I found the solution. In order to install a version of VMTools 12.1.0 or 12.1.5 onto all ESXi V6.7 hosts using Lifecycle Manager, of course, with vCenter 7.x installed, follow these steps: Navigate to Lifecycle Manager from vCenter Server 7.x Appliance Image Depot -> Components -> Show Independent Components -> Filter "VMware Tools" Download latest VMware Tools Offline VIB Bundle from Customer Connect : https://www.vmware.com/go/tools Lifecycle Manager -> Actions -> Import -> VMware-Tools-x-core-offline-ESXi-depot.zip Create Baseline Baselines -> New Baseline Enter Name, content is Patch Select Patches Automatically - Uncheck "Automatically update this baseline with patches that match the following criteria" Select Patches Manually - Uncheck "Show only rollup updates" and filter for "VMware Tools 12" Select VMware Tools for vSphere 7, click Finish and confirm Baseline Attach Baseline to Cluster (can be done on individual hosts too) Select Cluster -> Updates -> Baselines -> Attach Baselines Check Compliance - Will check to see if all hosts in cluster has package installed Select Baseline -> Stage - This puts all update files on the non-compliant hosts but does not install them. Good for preparing for future maintenance. Select Baseline -> Remediate - vLCM will use the staged VMware Tools update to do the installation to hosts. When applying an async update of the VMware Tools package to an ESXi host via vLCM, a host reboot is not required. Hosts will show as Compliant when installation is complete Done. Now you can select the VMs to update VMTools on, and choose the Match to Host option.

JDMils_Interact · ‎12-11-2022

As you may know, all VMTools below V12.1.0 have a critical vulnerability so I need to install either VMTools V12.1.0 or 12.1.5 onto my ESXi hosts and I need your help. We just upgraded all our vCent...

As you may know, all VMTools below V12.1.0 have a critical vulnerability so I need to install either VMTools V12.1.0 or 12.1.5 onto my ESXi hosts and I need your help. We just upgraded all our vCenters to V7.0u3d however our hosts are still at ESXi 6.7u3q. We are a big environment with 500 hosts so it's going to take a while to upgrade them all! My plan is to use vCenter V7.0 LifeCycle Manager to create a baseline for VMTools 12.1.0 so I can install it onto my hosts. However the version of VMTools (12.1.0 & 12.1.5) which I can find in LifeCycle Manager is only for ESXi 7.x and 8.x. Is there a way for me to import the VMTools V12.1.0 (for ESXi 6.7) downloaded from the VMware repo into Lifecycle Manager?

JDMils_Interact · ‎09-11-2022

I'm reacting to a /storage/log nearing 95% alert on our production vCenter server. I'm in the /storage/log/vmware/vpostgres folder and this folder is showing as the biggest consumption of disk space...

I'm reacting to a /storage/log nearing 95% alert on our production vCenter server. I'm in the /storage/log/vmware/vpostgres folder and this folder is showing as the biggest consumption of disk space. Am I able to remove the backup and log files in this folder or should I just walk away and leave this folder alone? Here's the folder listing: root@MyVC01 [ /storage/log/vmware/vpostgres ]# ls -l total 14370708 -rw------- 1 vpostgres users 0 Sep 8 15:30 pg_archiver.log-0.stderr -rw------- 1 vpostgres users 0 Apr 5 14:10 pg_archiver.log-0.stderr.1-2022050406.backup -rw------- 1 vpostgres users 20 Sep 8 15:20 pg_archiver.log-0.stderr.1.gz -rw------- 1 vpostgres users 20 Sep 8 15:10 pg_archiver.log-0.stderr.2.gz -rw------- 1 vpostgres users 20 Sep 8 15:00 pg_archiver.log-0.stderr.3.gz -rw------- 1 vpostgres users 20 Sep 8 14:50 pg_archiver.log-0.stderr.4.gz -rw------- 1 vpostgres users 0 Sep 8 15:30 pg_archiver.log-0.stdout -rw------- 1 vpostgres users 0 Apr 5 14:10 pg_archiver.log-0.stdout.1-2022051521.backup -rw------- 1 vpostgres users 20 Sep 8 15:20 pg_archiver.log-0.stdout.1.gz -rw------- 1 vpostgres users 20 Sep 8 15:10 pg_archiver.log-0.stdout.2.gz -rw------- 1 vpostgres users 20 Sep 8 15:00 pg_archiver.log-0.stdout.3.gz -rw------- 1 vpostgres users 20 Sep 8 14:50 pg_archiver.log-0.stdout.4.gz -rw------- 1 vpostgres users 0 Sep 8 15:30 pg_archiver.log-1.stderr -rw------- 1 vpostgres users 0 Apr 5 14:10 pg_archiver.log-1.stderr.1-2022051521.backup -rw------- 1 vpostgres users 20 Sep 8 15:20 pg_archiver.log-1.stderr.1.gz -rw------- 1 vpostgres users 20 Sep 8 15:10 pg_archiver.log-1.stderr.2.gz -rw------- 1 vpostgres users 20 Sep 8 15:00 pg_archiver.log-1.stderr.3.gz -rw------- 1 vpostgres users 20 Sep 8 14:50 pg_archiver.log-1.stderr.4.gz -rw------- 1 vpostgres users 0 Sep 8 15:30 pg_archiver.log-1.stdout -rw------- 1 vpostgres users 0 Apr 5 14:10 pg_archiver.log-1.stdout.1-2022051521.backup -rw------- 1 vpostgres users 20 Sep 8 15:20 pg_archiver.log-1.stdout.1.gz -rw------- 1 vpostgres users 20 Sep 8 15:10 pg_archiver.log-1.stdout.2.gz -rw------- 1 vpostgres users 20 Sep 8 15:00 pg_archiver.log-1.stdout.3.gz -rw------- 1 vpostgres users 20 Sep 8 14:50 pg_archiver.log-1.stdout.4.gz -rw------- 1 vpostgres users 0 Sep 8 15:30 pg_archiver.log-2.stderr -rw------- 1 vpostgres users 20 Sep 8 15:20 pg_archiver.log-2.stderr.1.gz -rw------- 1 vpostgres users 20 Sep 8 15:10 pg_archiver.log-2.stderr.2.gz -rw------- 1 vpostgres users 20 Sep 8 15:00 pg_archiver.log-2.stderr.3.gz -rw------- 1 vpostgres users 20 Sep 8 14:50 pg_archiver.log-2.stderr.4.gz -rw------- 1 vpostgres users 0 Sep 8 15:30 pg_archiver.log-2.stdout -rw------- 1 vpostgres users 20 Sep 8 15:20 pg_archiver.log-2.stdout.1.gz -rw------- 1 vpostgres users 20 Sep 8 15:10 pg_archiver.log-2.stdout.2.gz -rw------- 1 vpostgres users 20 Sep 8 15:00 pg_archiver.log-2.stdout.3.gz -rw------- 1 vpostgres users 20 Sep 8 14:50 pg_archiver.log-2.stdout.4.gz -rw------- 1 vpostgres users 0 Sep 8 15:30 pg_archiver.log-3.stderr -rw------- 1 vpostgres users 20 Sep 8 15:20 pg_archiver.log-3.stderr.1.gz -rw------- 1 vpostgres users 20 Sep 8 15:10 pg_archiver.log-3.stderr.2.gz -rw------- 1 vpostgres users 20 Sep 8 15:00 pg_archiver.log-3.stderr.3.gz -rw------- 1 vpostgres users 20 Sep 8 14:50 pg_archiver.log-3.stderr.4.gz -rw------- 1 vpostgres users 0 Sep 8 15:30 pg_archiver.log-3.stdout -rw------- 1 vpostgres users 20 Sep 8 15:20 pg_archiver.log-3.stdout.1.gz -rw------- 1 vpostgres users 20 Sep 8 15:10 pg_archiver.log-3.stdout.2.gz -rw------- 1 vpostgres users 20 Sep 8 15:00 pg_archiver.log-3.stdout.3.gz -rw------- 1 vpostgres users 20 Sep 8 14:50 pg_archiver.log-3.stdout.4.gz -rw------- 1 vpostgres users 10412671 Sep 12 11:50 pg_archiver.log.stderr -rw------- 1 vpostgres users 0 Apr 5 14:10 pg_archiver.log.stderr.1-2022050909.backup -rw------- 1 vpostgres users 6217572 Jul 27 12:00 pg_archiver.log.stderr.1-2022072712.backup -rw------- 1 vpostgres users 6242559 Jul 27 19:00 pg_archiver.log.stderr.1-2022072719.backup -rw------- 1 vpostgres users 6276869 Jul 28 04:00 pg_archiver.log.stderr.1-2022072804.backup -rw------- 1 vpostgres users 6298036 Jul 28 10:00 pg_archiver.log.stderr.1-2022072810.backup -rw------- 1 vpostgres users 6308709 Jul 28 13:00 pg_archiver.log.stderr.1-2022072813.backup -rw------- 1 vpostgres users 6315918 Jul 28 15:00 pg_archiver.log.stderr.1-2022072815.backup -rw------- 1 vpostgres users 6319567 Jul 28 16:00 pg_archiver.log.stderr.1-2022072816.backup -rw------- 1 vpostgres users 6323105 Jul 28 17:00 pg_archiver.log.stderr.1-2022072817.backup -rw------- 1 vpostgres users 8029149 Aug 17 10:00 pg_archiver.log.stderr.1-2022081710.backup -rw------- 1 vpostgres users 8048262 Aug 17 15:00 pg_archiver.log.stderr.1-2022081715.backup -rw------- 1 vpostgres users 8052000 Aug 17 16:00 pg_archiver.log.stderr.1-2022081716.backup -rw------- 1 vpostgres users 8055649 Aug 17 17:00 pg_archiver.log.stderr.1-2022081717.backup -rw------- 1 vpostgres users 8059298 Aug 17 18:00 pg_archiver.log.stderr.1-2022081718.backup -rw------- 1 vpostgres users 8062769 Aug 17 19:00 pg_archiver.log.stderr.1-2022081719.backup -rw------- 1 vpostgres users 8067197 Aug 17 20:00 pg_archiver.log.stderr.1-2022081720.backup -rw------- 1 vpostgres users 8074673 Aug 17 22:00 pg_archiver.log.stderr.1-2022081722.backup -rw------- 1 vpostgres users 8078144 Aug 17 23:00 pg_archiver.log.stderr.1-2022081723.backup -rw------- 1 vpostgres users 8089692 Aug 18 02:00 pg_archiver.log.stderr.1-2022081802.backup -rw------- 1 vpostgres users 8093430 Aug 18 03:00 pg_archiver.log.stderr.1-2022081803.backup -rw------- 1 vpostgres users 8097079 Aug 18 04:00 pg_archiver.log.stderr.1-2022081804.backup -rw------- 1 vpostgres users 8104199 Aug 18 06:00 pg_archiver.log.stderr.1-2022081806.backup -rw------- 1 vpostgres users 8107759 Aug 18 07:00 pg_archiver.log.stderr.1-2022081807.backup -rw------- 1 vpostgres users 8111386 Aug 18 08:00 pg_archiver.log.stderr.1-2022081808.backup -rw------- 1 vpostgres users 8118862 Aug 18 10:00 pg_archiver.log.stderr.1-2022081810.backup -rw------- 1 vpostgres users 8126872 Aug 18 12:00 pg_archiver.log.stderr.1-2022081812.backup -rw------- 1 vpostgres users 8130521 Aug 18 13:00 pg_archiver.log.stderr.1-2022081813.backup -rw------- 1 vpostgres users 8134326 Aug 18 14:00 pg_archiver.log.stderr.1-2022081814.backup -rw------- 1 vpostgres users 8138687 Aug 18 15:00 pg_archiver.log.stderr.1-2022081815.backup -rw------- 1 vpostgres users 8142870 Aug 18 16:00 pg_archiver.log.stderr.1-2022081816.backup -rw------- 1 vpostgres users 8146608 Aug 18 17:00 pg_archiver.log.stderr.1-2022081817.backup -rw------- 1 vpostgres users 8154351 Aug 18 19:00 pg_archiver.log.stderr.1-2022081819.backup -rw------- 1 vpostgres users 8158690 Aug 18 20:00 pg_archiver.log.stderr.1-2022081820.backup -rw------- 1 vpostgres users 8177647 Aug 19 01:00 pg_archiver.log.stderr.1-2022081901.backup -rw------- 1 vpostgres users 8181363 Aug 19 02:00 pg_archiver.log.stderr.1-2022081902.backup -rw------- 1 vpostgres users 8185190 Aug 19 03:00 pg_archiver.log.stderr.1-2022081903.backup -rw------- 1 vpostgres users 8188928 Aug 19 04:00 pg_archiver.log.stderr.1-2022081904.backup -rw------- 1 vpostgres users 8203235 Aug 19 08:00 pg_archiver.log.stderr.1-2022081908.backup -rw------- 1 vpostgres users 8206795 Aug 19 09:00 pg_archiver.log.stderr.1-2022081909.backup -rw------- 1 vpostgres users 8210800 Aug 19 10:00 pg_archiver.log.stderr.1-2022081910.backup -rw------- 1 vpostgres users 8214627 Aug 19 11:00 pg_archiver.log.stderr.1-2022081911.backup -rw------- 1 vpostgres users 8218721 Aug 19 12:00 pg_archiver.log.stderr.1-2022081912.backup -rw------- 1 vpostgres users 8222726 Aug 19 13:00 pg_archiver.log.stderr.1-2022081913.backup -rw------- 1 vpostgres users 8226353 Aug 19 14:00 pg_archiver.log.stderr.1-2022081914.backup -rw------- 1 vpostgres users 8230269 Aug 19 15:00 pg_archiver.log.stderr.1-2022081915.backup -rw------- 1 vpostgres users 8234096 Aug 19 16:00 pg_archiver.log.stderr.1-2022081916.backup -rw------- 1 vpostgres users 8237745 Aug 19 17:00 pg_archiver.log.stderr.1-2022081917.backup -rw------- 1 vpostgres users 8245488 Aug 19 19:00 pg_archiver.log.stderr.1-2022081919.backup -rw------- 1 vpostgres users 8249738 Aug 19 20:00 pg_archiver.log.stderr.1-2022081920.backup -rw------- 1 vpostgres users 8257214 Aug 19 22:00 pg_archiver.log.stderr.1-2022081922.backup -rw------- 1 vpostgres users 8260774 Aug 19 23:00 pg_archiver.log.stderr.1-2022081923.backup -rw------- 1 vpostgres users 8275971 Aug 20 03:00 pg_archiver.log.stderr.1-2022082003.backup -rw------- 1 vpostgres users 8279709 Aug 20 04:00 pg_archiver.log.stderr.1-2022082004.backup -rw------- 1 vpostgres users 8283180 Aug 20 05:00 pg_archiver.log.stderr.1-2022082005.backup -rw------- 1 vpostgres users 8286829 Aug 20 06:00 pg_archiver.log.stderr.1-2022082006.backup -rw------- 1 vpostgres users 8290389 Aug 20 07:00 pg_archiver.log.stderr.1-2022082007.backup -rw------- 1 vpostgres users 8294105 Aug 20 08:00 pg_archiver.log.stderr.1-2022082008.backup -rw------- 1 vpostgres users 8297576 Aug 20 09:00 pg_archiver.log.stderr.1-2022082009.backup -rw------- 1 vpostgres users 8302592 Aug 20 11:00 pg_archiver.log.stderr.1-2022082011.backup -rw------- 1 vpostgres users 8305885 Aug 20 12:00 pg_archiver.log.stderr.1-2022082012.backup -rw------- 1 vpostgres users 8313078 Aug 20 14:00 pg_archiver.log.stderr.1-2022082014.backup -rw------- 1 vpostgres users 8316543 Aug 20 15:00 pg_archiver.log.stderr.1-2022082015.backup -rw------- 1 vpostgres users 8320281 Aug 20 16:00 pg_archiver.log.stderr.1-2022082016.backup -rw------- 1 vpostgres users 8323841 Aug 20 17:00 pg_archiver.log.stderr.1-2022082017.backup -rw------- 1 vpostgres users 8327401 Aug 20 18:00 pg_archiver.log.stderr.1-2022082018.backup -rw------- 1 vpostgres users 8332830 Aug 21 01:00 pg_archiver.log.stderr.1-2022082101.backup -rw------- 1 vpostgres users 8335856 Aug 21 12:00 pg_archiver.log.stderr.1-2022082112.backup -rw------- 1 vpostgres users 8339505 Aug 21 13:00 pg_archiver.log.stderr.1-2022082113.backup -rw------- 1 vpostgres users 8342442 Aug 21 14:00 pg_archiver.log.stderr.1-2022082114.backup -rw------- 1 vpostgres users 8345468 Aug 22 12:00 pg_archiver.log.stderr.1-2022082212.backup -rw------- 1 vpostgres users 8965471 Aug 29 13:00 pg_archiver.log.stderr.1-2022082913.backup -rw------- 1 vpostgres users 8969209 Aug 29 14:00 pg_archiver.log.stderr.1-2022082914.backup -rw------- 1 vpostgres users 8972947 Aug 29 15:00 pg_archiver.log.stderr.1-2022082915.backup -rw------- 1 vpostgres users 8980406 Aug 29 17:00 pg_archiver.log.stderr.1-2022082917.backup -rw------- 1 vpostgres users 8987699 Aug 29 19:00 pg_archiver.log.stderr.1-2022082919.backup -rw------- 1 vpostgres users 8992149 Aug 29 20:00 pg_archiver.log.stderr.1-2022082920.backup -rw------- 1 vpostgres users 8995709 Aug 29 21:00 pg_archiver.log.stderr.1-2022082921.backup -rw------- 1 vpostgres users 8999625 Aug 29 22:00 pg_archiver.log.stderr.1-2022082922.backup -rw------- 1 vpostgres users 9003168 Aug 29 23:00 pg_archiver.log.stderr.1-2022082923.backup -rw------- 1 vpostgres users 9011084 Aug 30 01:00 pg_archiver.log.stderr.1-2022083001.backup -rw------- 1 vpostgres users 9015000 Aug 30 02:00 pg_archiver.log.stderr.1-2022083002.backup -rw------- 1 vpostgres users 9022476 Aug 30 04:00 pg_archiver.log.stderr.1-2022083004.backup -rw------- 1 vpostgres users 9026018 Aug 30 05:00 pg_archiver.log.stderr.1-2022083005.backup -rw------- 1 vpostgres users 9029663 Aug 30 06:00 pg_archiver.log.stderr.1-2022083006.backup -rw------- 1 vpostgres users 9036961 Aug 30 08:00 pg_archiver.log.stderr.1-2022083008.backup -rw------- 1 vpostgres users 9040521 Aug 30 09:00 pg_archiver.log.stderr.1-2022083009.backup -rw------- 1 vpostgres users 9044259 Aug 30 10:00 pg_archiver.log.stderr.1-2022083010.backup -rw------- 1 vpostgres users 9048076 Aug 30 11:00 pg_archiver.log.stderr.1-2022083011.backup -rw------- 1 vpostgres users 9051713 Aug 30 12:00 pg_archiver.log.stderr.1-2022083012.backup -rw------- 1 vpostgres users 9055362 Aug 30 13:00 pg_archiver.log.stderr.1-2022083013.backup -rw------- 1 vpostgres users 9059011 Aug 30 14:00 pg_archiver.log.stderr.1-2022083014.backup -rw------- 1 vpostgres users 9062660 Aug 30 15:00 pg_archiver.log.stderr.1-2022083015.backup -rw------- 1 vpostgres users 9066398 Aug 30 16:00 pg_archiver.log.stderr.1-2022083016.backup -rw------- 1 vpostgres users 9073674 Aug 30 18:00 pg_archiver.log.stderr.1-2022083018.backup -rw------- 1 vpostgres users 9085333 Aug 30 21:00 pg_archiver.log.stderr.1-2022083021.backup -rw------- 1 vpostgres users 9089071 Aug 30 22:00 pg_archiver.log.stderr.1-2022083022.backup -rw------- 1 vpostgres users 9092631 Aug 30 23:00 pg_archiver.log.stderr.1-2022083023.backup -rw------- 1 vpostgres users 9106822 Aug 31 01:00 pg_archiver.log.stderr.1-2022083101.backup -rw------- 1 vpostgres users 9125423 Aug 31 03:00 pg_archiver.log.stderr.1-2022083103.backup -rw------- 1 vpostgres users 9134001 Aug 31 04:00 pg_archiver.log.stderr.1-2022083104.backup -rw------- 1 vpostgres users 9142611 Aug 31 05:00 pg_archiver.log.stderr.1-2022083105.backup -rw------- 1 vpostgres users 9151320 Aug 31 06:00 pg_archiver.log.stderr.1-2022083106.backup -rw------- 1 vpostgres users 9159930 Aug 31 07:00 pg_archiver.log.stderr.1-2022083107.backup -rw------- 1 vpostgres users 9168419 Aug 31 08:00 pg_archiver.log.stderr.1-2022083108.backup -rw------- 1 vpostgres users 9177029 Aug 31 09:00 pg_archiver.log.stderr.1-2022083109.backup -rw------- 1 vpostgres users 9187440 Aug 31 10:00 pg_archiver.log.stderr.1-2022083110.backup -rw------- 1 vpostgres users 9196680 Aug 31 11:00 pg_archiver.log.stderr.1-2022083111.backup -rw------- 1 vpostgres users 9205688 Aug 31 12:00 pg_archiver.log.stderr.1-2022083112.backup -rw------- 1 vpostgres users 9223748 Aug 31 14:00 pg_archiver.log.stderr.1-2022083114.backup -rw------- 1 vpostgres users 9232568 Aug 31 15:00 pg_archiver.log.stderr.1-2022083115.backup -rw------- 1 vpostgres users 9242018 Aug 31 16:00 pg_archiver.log.stderr.1-2022083116.backup -rw------- 1 vpostgres users 9250749 Aug 31 17:00 pg_archiver.log.stderr.1-2022083117.backup -rw------- 1 vpostgres users 9259757 Aug 31 18:00 pg_archiver.log.stderr.1-2022083118.backup -rw------- 1 vpostgres users 9268367 Aug 31 19:00 pg_archiver.log.stderr.1-2022083119.backup -rw------- 1 vpostgres users 9278205 Aug 31 20:00 pg_archiver.log.stderr.1-2022083120.backup -rw------- 1 vpostgres users 9287146 Aug 31 21:00 pg_archiver.log.stderr.1-2022083121.backup -rw------- 1 vpostgres users 9296176 Aug 31 22:00 pg_archiver.log.stderr.1-2022083122.backup -rw------- 1 vpostgres users 9304900 Aug 31 23:00 pg_archiver.log.stderr.1-2022083123.backup -rw------- 1 vpostgres users 9332815 Sep 1 02:00 pg_archiver.log.stderr.1-2022090102.backup -rw------- 1 vpostgres users 9350875 Sep 1 04:00 pg_archiver.log.stderr.1-2022090104.backup -rw------- 1 vpostgres users 9359474 Sep 1 05:00 pg_archiver.log.stderr.1-2022090105.backup -rw------- 1 vpostgres users 9368194 Sep 1 06:00 pg_archiver.log.stderr.1-2022090106.backup -rw------- 1 vpostgres users 9403474 Sep 1 10:00 pg_archiver.log.stderr.1-2022090110.backup -rw------- 1 vpostgres users 9412497 Sep 1 11:00 pg_archiver.log.stderr.1-2022090111.backup -rw------- 1 vpostgres users 9421601 Sep 1 12:00 pg_archiver.log.stderr.1-2022090112.backup -rw------- 1 vpostgres users 9430421 Sep 1 13:00 pg_archiver.log.stderr.1-2022090113.backup -rw------- 1 vpostgres users 9439152 Sep 1 14:00 pg_archiver.log.stderr.1-2022090114.backup -rw------- 1 vpostgres users 9447641 Sep 1 15:00 pg_archiver.log.stderr.1-2022090115.backup -rw------- 1 vpostgres users 9456550 Sep 1 16:00 pg_archiver.log.stderr.1-2022090116.backup -rw------- 1 vpostgres users 9465160 Sep 1 17:00 pg_archiver.log.stderr.1-2022090117.backup -rw------- 1 vpostgres users 9473958 Sep 1 18:00 pg_archiver.log.stderr.1-2022090118.backup -rw------- 1 vpostgres users 9481098 Sep 1 19:00 pg_archiver.log.stderr.1-2022090119.backup -rw------- 1 vpostgres users 9490642 Sep 1 20:00 pg_archiver.log.stderr.1-2022090120.backup -rw------- 1 vpostgres users 9497678 Sep 1 21:00 pg_archiver.log.stderr.1-2022090121.backup -rw------- 1 vpostgres users 9507039 Sep 1 22:00 pg_archiver.log.stderr.1-2022090122.backup -rw------- 1 vpostgres users 9514300 Sep 1 23:00 pg_archiver.log.stderr.1-2022090123.backup -rw------- 1 vpostgres users 9528147 Sep 2 01:00 pg_archiver.log.stderr.1-2022090201.backup -rw------- 1 vpostgres users 9546627 Sep 2 03:00 pg_archiver.log.stderr.1-2022090203.backup -rw------- 1 vpostgres users 9568343 Sep 2 11:00 pg_archiver.log.stderr.1-2022090211.backup -rw------- 1 vpostgres users 9569603 Sep 2 15:00 pg_archiver.log.stderr.1-2022090215.backup -rw------- 1 vpostgres users 9578512 Sep 2 16:00 pg_archiver.log.stderr.1-2022090216.backup -rw------- 1 vpostgres users 9587790 Sep 3 02:00 pg_archiver.log.stderr.1-2022090302.backup -rw------- 1 vpostgres users 9591780 Sep 3 12:00 pg_archiver.log.stderr.1-2022090312.backup -rw------- 1 vpostgres users 9596192 Sep 4 04:00 pg_archiver.log.stderr.1-2022090404.backup -rw------- 1 vpostgres users 9604713 Sep 4 05:00 pg_archiver.log.stderr.1-2022090405.backup -rw------- 1 vpostgres users 9621844 Sep 5 02:00 pg_archiver.log.stderr.1-2022090502.backup -rw------- 1 vpostgres users 11094 Sep 12 11:00 pg_archiver.log.stderr.1.gz -rw------- 1 vpostgres users 8369 Aug 17 10:00 pg_archiver.log.stderr.1.gz-2022081710.backup -rw------- 1 vpostgres users 6757 Aug 17 23:00 pg_archiver.log.stderr.1.gz-2022081723.backup -rw------- 1 vpostgres users 8152 Aug 19 09:00 pg_archiver.log.stderr.1.gz-2022081909.backup -rw------- 1 vpostgres users 8220 Aug 20 11:00 pg_archiver.log.stderr.1.gz-2022082011.backup -rw------- 1 vpostgres users 7600 Aug 29 19:00 pg_archiver.log.stderr.1.gz-2022082919.backup -rw------- 1 vpostgres users 8605 Aug 31 11:00 pg_archiver.log.stderr.1.gz-2022083111.backup -rw------- 1 vpostgres users 4353 Aug 31 19:00 pg_archiver.log.stderr.1.gz-2022083119.backup -rw------- 1 vpostgres users 9517 Sep 1 18:00 pg_archiver.log.stderr.1.gz-2022090118.backup -rw------- 1 vpostgres users 9474 Sep 2 11:00 pg_archiver.log.stderr.1.gz-2022090211.backup -rw------- 1 vpostgres users 11061 Sep 12 10:00 pg_archiver.log.stderr.2.gz -rw------- 1 vpostgres users 11017 Sep 12 08:55 pg_archiver.log.stderr.3.gz -rw------- 1 vpostgres users 11065 Sep 12 08:00 pg_archiver.log.stderr.4.gz -rw------- 1 vpostgres users 0 Sep 8 15:30 pg_archiver.log.stdout -rw------- 1 vpostgres users 0 Apr 5 14:10 pg_archiver.log.stdout.1-2022051521.backup -rw------- 1 vpostgres users 20 Sep 8 15:20 pg_archiver.log.stdout.1.gz -rw------- 1 vpostgres users 20 Sep 8 15:10 pg_archiver.log.stdout.2.gz -rw------- 1 vpostgres users 20 Sep 8 15:00 pg_archiver.log.stdout.3.gz -rw------- 1 vpostgres users 20 Sep 8 14:50 pg_archiver.log.stdout.4.gz -rw------- 1 vpostgres users 24509 Jun 17 18:38 pg_controldata_pre_start.txt -rw------- 1 vpostgres users 244868 Sep 12 11:50 postgres_cron.log -rw------- 1 vpostgres users 0 Apr 5 14:10 postgres_cron.log.1-2022050406.backup -rw------- 1 vpostgres users 226 Sep 8 15:30 postgres_cron.log.1.gz -rw------- 1 vpostgres users 226 Sep 8 15:20 postgres_cron.log.2.gz -rw------- 1 vpostgres users 226 Sep 8 15:10 postgres_cron.log.3.gz -rw------- 1 vpostgres users 226 Sep 8 15:00 postgres_cron.log.4.gz -rw------- 1 vpostgres users 571326922 Sep 2 10:00 postgresql-01.log -rw------- 1 vpostgres users 101564416 Sep 3 10:00 postgresql-02.log -rw------- 1 vpostgres users 86908928 Sep 4 10:00 postgresql-03.log -rw------- 1 vpostgres users 29356032 Sep 5 10:00 postgresql-04.log -rw------- 1 vpostgres users 708608 Sep 6 10:00 postgresql-05.log -rw------- 1 vpostgres users 12226560 Sep 7 10:00 postgresql-06.log -rw------- 1 vpostgres users 745472 Sep 8 09:59 postgresql-07.log -rw------- 1 vpostgres users 18448814 Sep 9 09:59 postgresql-08.log -rw------- 1 vpostgres users 33255381 Sep 10 09:59 postgresql-09.log -rw------- 1 vpostgres users 29759833 Sep 11 09:59 postgresql-10.log -rw------- 1 vpostgres users 31251073 Sep 12 10:00 postgresql-11.log -rw------- 1 vpostgres users 2289347 Sep 12 11:51 postgresql-12.log -rw------- 1 vpostgres users 844252031 Aug 15 10:00 postgresql-14.log -rw------- 1 vpostgres users 863208423 Aug 16 10:00 postgresql-15.log -rw------- 1 vpostgres users 851419152 Aug 17 10:00 postgresql-16.log -rw------- 1 vpostgres users 865553191 Aug 18 10:00 postgresql-17.log -rw------- 1 vpostgres users 853456279 Aug 19 10:00 postgresql-18.log -rw------- 1 vpostgres users 857051136 Aug 20 10:00 postgresql-19.log -rw------- 1 vpostgres users 290791424 Aug 21 10:00 postgresql-20.log -rw------- 1 vpostgres users 95694848 Aug 22 10:00 postgresql-21.log -rw------- 1 vpostgres users 652624482 Aug 23 10:00 postgresql-22.log -rw------- 1 vpostgres users 857502666 Aug 24 10:00 postgresql-23.log -rw------- 1 vpostgres users 859878950 Aug 25 10:00 postgresql-24.log -rw------- 1 vpostgres users 855585913 Aug 26 10:00 postgresql-25.log -rw------- 1 vpostgres users 851939210 Aug 27 10:00 postgresql-26.log -rw------- 1 vpostgres users 844110410 Aug 28 10:00 postgresql-27.log -rw------- 1 vpostgres users 855634333 Aug 29 10:00 postgresql-28.log -rw------- 1 vpostgres users 844857295 Aug 30 10:00 postgresql-29.log -rw------- 1 vpostgres users 821948131 Aug 31 10:00 postgresql-30.log -rw------- 1 vpostgres users 830409784 Sep 1 10:00 postgresql-31.log -rw------- 1 vpostgres users 4096 Jun 2 04:18 serverlog-0.stderr -rw------- 1 vpostgres users 41 May 4 15:27 serverlog-0.stdout -rw------- 1 vpostgres users 444 May 4 15:24 serverlog-1.stderr -rw------- 1 vpostgres users 41 May 4 15:24 serverlog-1.stdout -rw------- 1 vpostgres users 8192 May 4 10:00 serverlog-2.stderr -rw------- 1 vpostgres users 41 Oct 12 2021 serverlog-2.stdout -rw------- 1 vpostgres users 445 Oct 12 2021 serverlog-3.stderr -rw------- 1 vpostgres users 42 Oct 12 2021 serverlog-3.stdout -rw------- 1 vpostgres users 442 Jun 22 2021 serverlog-4.stderr -rw------- 1 vpostgres users 41 Jun 22 2021 serverlog-4.stdout -rw------- 1 vpostgres users 4096 Sep 8 11:29 serverlog.stderr -rw------- 1 vpostgres users 41 Jun 17 18:38 serverlog.stdout root@MyVC01 [ /storage/log/vmware/vpostgres ]# rm cd ..

JDMils_Interact · ‎09-01-2022

Thanks- I'll give that a go.

JDMils_Interact · ‎08-30-2022

That worked well, thanks. Can you explain how this line works? .ActiveNic.Where{ $_ } To me it looks like, if the port group $PG exists, then......do this. Amazing solution btw. One othe...

That worked well, thanks. Can you explain how this line works? .ActiveNic.Where{ $_ } To me it looks like, if the port group $PG exists, then......do this. Amazing solution btw. One other question: I ran the modified code for all distributed switches and it's been running for 24 hours now- we only have about 3 distributed switches in our environment. I presume that this line is taking a while to run, is there any way to modify the code so that the line runs once and the properties ActiveNic, StandByNic & UnusedNic can be added to the collection? Get-VirtualPortGroup -Name $PG.Name -VMHost $esx -VirtualSwitch $vsw | Get-NicTeamingPolicy I also modified the script so that it should be able to report on only either Standard or Distributed switches, here's the modifications: Param ( [Switch]$Standard, [Switch]$Distributed ) Write-Host "Script Starting" -ForegroundColor Green # &{foreach($esx in Get-VMHost -Name 'cmspp2ensxthp10.iaas01.bsg.interactive.com.au'){ &{foreach($esx in Get-VMHost){ $vNicTab = @{} $esx.ExtensionData.Config.Network.Vnic | %{ if (-not $vNicTab.ContainsKey($_.Portgroup)) { $vNicTab.Add($_.Portgroup,$_) } } if ($Standard.IsPresent -or $Distributed.IsPresent) { if ($Distributed.IsPresent) { $oSwitchObject = Get-VirtualSwitch -VMHost $esx -Distributed $Standard = $False Write-Host "Distributed switches only" } if ($Standard.IsPresent) { $oSwitchObject = Get-VirtualSwitch -VMHost $esx -Standard Write-Host "Standard switches only" } } Else { $oSwitchObject = Get-VirtualSwitch -VMHost $esx -Standard Write-Host "Standard switches only" } Write-Host "Working on host [$ESX.Name]" foreach($vsw in ($oSwitchObject)){ Write-Host "-- Virtual Switch [$VSW]" -ForegroundColor Blue foreach($pg in (Get-VirtualPortGroup -VirtualSwitch $vsw)){ Write-Host "---- Port Group [$PG]" -ForegroundColor Cyan Select -InputObject $pg -Property @{N="ESX";E={$esx.name}}, @{N="vSwitch";E={$vsw.Name}}, @{N="vSwitch Active NIC";E={[string]::Join(',',$vsw.ExtensionData.Spec.Policy.NicTeaming.NicOrder.ActiveNic)}}, @{N="vSwitch Standby NIC";E={[string]::Join(',',$vsw.ExtensionData.Spec.Policy.NicTeaming.NicOrder.StandbyNic)}}, @{N="vSwitch Unused NIC";E={[string]::Join(',',$vsw.ExtensionData.Spec.Policy.NicTeaming.NicOrder.UnusedNic)}}, @{N="Portgroup";E={$pg.Name}}, @{N="PortGroup VLAN";E={$pg.VLanId}}, @{N="Device";E={if($vNicTab.ContainsKey($pg.Name)){$vNicTab[$pg.Name].Device}}}, @{N="IP";E={if($vNicTab.ContainsKey($pg.Name)){$vNicTab[$pg.Name].Spec.Ip.IpAddress}}}, @{N="PortGroup Active NIC"; E = { (Get-VirtualPortGroup -Name $PG.Name -VMHost $esx -VirtualSwitch $vsw | Get-NicTeamingPolicy).ActiveNic.Where{ $_ } -join ',' } }, @{N="PortGroup StandBy NIC"; E = { (Get-VirtualPortGroup -Name $PG.Name -VMHost $esx -VirtualSwitch $vsw | Get-NicTeamingPolicy).StandByNic.Where{ $_} -join ',' } }, @{N="PortGroup Unused NIC"; E = { (Get-VirtualPortGroup -Name $PG.Name -VMHost $esx -VirtualSwitch $vsw | Get-NicTeamingPolicy).UnusedNic.Where{ $_} -join ',' } } } } }} | Export-Csv ManagementPortGroupNICReport.csv -NoTypeInformation -UseCulture Write-Host "Script Stopping" -ForegroundColor Green Thanks.

JDMils_Interact · ‎08-29-2022

I manually ran each line as such: $esx = Get-VMHost -Name 'MyHostAtMyDomain.Com' $vsw = (Get-VirtualSwitch -VMHost $esx -Standard) $vsw Name NumPorts Mtu Notes...

I manually ran each line as such: $esx = Get-VMHost -Name 'MyHostAtMyDomain.Com' $vsw = (Get-VirtualSwitch -VMHost $esx -Standard) $vsw Name NumPorts Mtu Notes ---- -------- --- ----- vSwitch0 11776 1500 $pg = (Get-VirtualPortGroup -VirtualSwitch $vsw) $pg Name Key VLanId PortBinding NumPorts ---- --- ------ ----------- -------- Management Network key-vim.host.PortGroup-Mana... 1000 VM Network key-vim.host.PortGroup-VM N... 0 Get-VirtualPortGroup -Name $PG[0].Name | Get-NICTeamingPolicy VirtualPortGroup ActiveNic StandbyNic UnusedNic FailbackEnabled NotifySwitches ---------------- --------- ---------- --------- --------------- -------------- Management Network {vmnic0} {vmnic3} True True Management Network {vmnic1, vmn... True True Management Network {vmnic3, vmn... True True Management Network {vmnic3, vmn... True True Management Network {vmnic1, vmn... True True Management Network {vmnic3, vmn... True True Management Network {vmnic1, vmn... True True Management Network {vmnic1, vmn... True True Management Network {vmnic0, vmn... True True Management Network {vmnic0, vmn... True True Looks like there may be something wrong with $PG?

JDMils_Interact · ‎08-29-2022

For the Management port group of my test host, I purposely put vmnic0 as active and vmnic4 as unused and got the following results: ESX : MyHostNameAtMyDomain.Com vSwitch ...

For the Management port group of my test host, I purposely put vmnic0 as active and vmnic4 as unused and got the following results: ESX : MyHostNameAtMyDomain.Com vSwitch : vSwitch0 Active NIC : vmnic0,vmnic4 Standby NIC : Portgroup : Management Network VLAN : 1000 Device : vmk0 IP : 1172.0.0.102 PortGroup Active NIC : vmnic0, vmnic1, vmnic3, vmnic3, vmnic1, vmnic3, vmnic1, vmnic1, vmnic3, vmnic3, vmnic1, vmnic1, vmnic3, vmnic1, vmnic3, vmnic0, vmnic1, vmnic0, vmnic1, vmnic0, vmnic3, vmnic0, vmnic3, vmnic0, vmnic3, vmnic0, vmnic3, vmnic1, vmnic3, vmnic3, vmnic1, vmnic0, vmnic3, vmnic1, vmnic3, vmnic3, vmnic1, vmnic3, vmnic1, vmnic3, vmnic2, vmnic3, vmnic1, vmnic2, vmnic3, vmnic0, vmnic3, vmnic1, vmnic3, vmnic3, vmnic2, vmnic1, vmnic3, vmnic3, vmnic2, vmnic0, vmnic3, vmnic0, vmnic3, vmnic0, vmnic3, vmnic2, vmnic3, vmnic2, vmnic3, vmnic2, vmnic3, vmnic2, vmnic3, vmnic3, vmnic2, vmnic0, vmnic1, vmnic0, vmnic1, vmnic0, vmnic2, vmnic4, vmnic5, vmnic2, vmnic3, vmnic2, vmnic3, vmnic0, vmnic3, vmnic0, vmnic3, vmnic0, vmnic3, vmnic1, vmnic3, vmnic3, vmnic1, vmnic2, vmnic3, vmnic1, vmnic2, vmnic3, vmnic3, vmnic1, vmnic3, vmnic1, vmnic3, vmnic1, vmnic2, vmnic3, vmnic3, vmnic1, vmnic2, vmnic3, vmnic2, vmnic3, vmnic0, vmnic3, vmnic1, vmnic3, vmnic3, vmnic2, vmnic0, vmnic3, vmnic0, vmnic3, vmnic0, vmnic7, vmnic0, vmnic7, vmnic1, vmnic3, vmnic1, vmnic3, vmnic1, vmnic3, vmnic2, vmnic3, vmnic0, vmnic0, vmnic0, vmnic3, vmnic0, vmnic0, vmnic3, vmnic0, vmnic4, vmnic0, vmnic4, vmnic2, vmnic3, vmnic2, vmnic3 PortGroup StandBy NIC : vmnic3, vmnic3, vmnic3 Which does not seem right.

JDMils_Interact · ‎08-28-2022

We all know that the Standard switch is normally used for the management network of the hosts, and this switch has configurable uplinks (for example Active & Standby uplinks). Today I was analysing ...

We all know that the Standard switch is normally used for the management network of the hosts, and this switch has configurable uplinks (for example Active & Standby uplinks). Today I was analysing a host failure on the weekend where one of the uplinks went down but a few hosts went into network isolation- isolating themselves from the vCenter. I checked the Standard switch uplinks and they are both Active. I then checked the Management PortGroup, as it too can have configured uplinks, and I found one of the uplinks configured as StandBy, and thus the reason why those hosts failed. I now want to run a PowerShell script to check all hosts in the cluster and I came up with this, with help from an existing script I found: &{foreach($esx in Get-VMHost){ $vNicTab = @{} $esx.ExtensionData.Config.Network.Vnic | %{ $vNicTab.Add($_.Portgroup,$_) } foreach($vsw in (Get-VirtualSwitch -VMHost $esx -Standard)){ foreach($pg in (Get-VirtualPortGroup -VirtualSwitch $vsw)){ Select -InputObject $pg -Property @{N="ESX";E={$esx.name}}, @{N="vSwitch";E={$vsw.Name}}, @{N="Active NIC";E={[string]::Join(',',$vsw.ExtensionData.Spec.Policy.NicTeaming.NicOrder.ActiveNic)}}, @{N="Standby NIC";E={[string]::Join(',',$vsw.ExtensionData.Spec.Policy.NicTeaming.NicOrder.StandbyNic)}}, @{N="Portgroup";E={$pg.Name}}, @{N="VLAN";E={$pg.VLanId}}, @{N="Device";E={if($vNicTab.ContainsKey($pg.Name)){$vNicTab[$pg.Name].Device}}}, @{N="IP";E={if($vNicTab.ContainsKey($pg.Name)){$vNicTab[$pg.Name].Spec.Ip.IpAddress}}}, @{N="PortGroup Active NIC";E={Get-VirtualPortGroup -Name $PG.Name | Get-NICTeamingPolicy | Select ActiveNic}}, @{N="PortGroup StandBy NIC";E={Get-VirtualPortGroup -Name $PG.Name | Get-NICTeamingPolicy | Select StandByNic}} } } }} My problem is with the returned values for "PortGroup Active NIC" & "PortGroup StandBy NIC" which appear like this: PortGroup Active NIC : {@{ActiveNic=System.String[]}, @{ActiveNic=System.String[]}, @{ActiveNic=System.String[]}, @{ActiveNic=System.String[]}...} PortGroup StandBy NIC : {@{StandbyNic=}, @{StandbyNic=}, @{StandbyNic=}, @{StandbyNic=}...} If I run the command from the commandline, I get this: $Z = Get-VirtualPortGroup -Name $PG.Name | Get-NICTeamingPolicy | Select ActiveNic $Z ActiveNic --------- {vmnic0, vmnic3} $z.gettype() IsPublic IsSerial Name BaseType -------- -------- ---- -------- True False PSCustomObject System.Object My goal is to set the property "PortGroup Active NIC" to "vmnic0, vmnic3". From the commandline, this seems to work: $Z.ActiveNic -join ", " vmnic0, vmnic3 I'm not sure how to do this in the original code tho.

JDMils_Interact · ‎06-19-2022

I have the following VMs on the datastore called "SAN_T0_NOR-001": * sldc01 * vcdp02 * vcdp03 I performed a storage vMotion of the VMs to a new datastore called "nfs_vmdata_t2048_br_01", however ...

I have the following VMs on the datastore called "SAN_T0_NOR-001": * sldc01 * vcdp02 * vcdp03 I performed a storage vMotion of the VMs to a new datastore called "nfs_vmdata_t2048_br_01", however when I view the datastore "SAN_T0_NOR-001", the VMs still appear there. I logged into the ESXI host and checked the datastore "SAN_T0_NOR-001" and found the following: [root@vmhep01:/vmfs/volumes/5a29e956-8e21a2aa-1b68-98be942a7ae2] ls -l total 50507808 drwxr-xr-x 1 root root 1120 Dec 10 2020 ISO drwxr-xr-x 1 root root 980 Dec 22 2017 RHEL7_Patched_20151027 drwxr-xr-x 1 root root 1400 Jan 11 2018 W2K12R2dc_SOE_v2_20160318 -rw------- 1 root root 25769803776 Jun 17 06:37 vcdp02-cab3cd2a.vswp -rw------- 1 root root 25769803776 Jun 17 06:41 vcdp03-cab3cd2b.vswp drwxr-xr-x 1 root root 1120 Mar 28 2018 proxy_centos7_template_1 -rw------- 1 root root 90177536 Jun 17 06:37 vmx-vcdp02-3400781098-1.vswp -rw------- 1 root root 90177536 Jun 17 06:41 vmx-vcdp03-3400781099-1.vswp [root@mhep01:/vmfs/volumes/5a29e956-8e21a2aa-1b68-98be942a7ae2] I checked the vmx file for VM "vcdp02" and found the following entry: sched.swap.derivedName = "/vmfs/volumes/5a29e956-8e21a2aa-1b68-98be942a7ae2/vcdp02-cab3cd2a.vswp" I checked the volume "5a29e956-8e21a2aa-1b68-98be942a7ae2" and found it is the volume to which I storage migrated the VM: lrwxr-xr-x 1 root root 17 Jun 19 23:49 nfs_vmdata_t2048_br_01 -> 58a59fed-1b459629 When I list the hard disks in the VM in the web client, I do not see a reference to the source datastore "SAN_T0_NOR_001". Am I to believe that the swap file is located both at the source datastore "SAN_T0_NOR_001" and the target datastore "nfs_vmdata_t2048_br_01"? How do I fix this now that the VM is storage migrated to the new datastore? How do I stop this from happening again in future storage migrations? Note that the datastore "SAN_T0_NOR_001" was set as the host swap datastore and the Cluster swap datastore BEFORE I migrated the VM. I have since changed these settings to the new datastore "nfs_vmdata_t2048_br_01". I'm assuming that for future storage migrations, I will need to set the cluster & hosts' swap datastore locations to the new datastore first then any VM with swap files on the source datastore will need to be powered off then back on again for the new swap datastore location to be 'activated'? vSphere 6.7, ESXi 6.7

JDMils_Interact · ‎06-13-2022

Looks like you cannot have the same port group name in the one vCenter, so I will have to create a new port group and just name it differently then add VMkernel ports to it.

JDMils_Interact · ‎06-09-2022

I have 2 clusters in my vCenter, CLUSTER-MGT & CLUSTER-NSXT. CLUSTER-NSXT has VLAN 1017 configured to be used for storage connectivity while CLUSTER-MGT is using iSCSI for storage thus using a differ...

I have 2 clusters in my vCenter, CLUSTER-MGT & CLUSTER-NSXT. CLUSTER-NSXT has VLAN 1017 configured to be used for storage connectivity while CLUSTER-MGT is using iSCSI for storage thus using a different VLAN/Port Group. I need to remove the iSCSI storage from CLUSTER-MGT and replace it with NFS storage by adding a VMkernel for Port Group 1017 so that the hosts in the CLUSTER-MGT can have NFS storage. How do I connect the Port Group 1017 to the CLUSTER-MGT hosts when it already exists on the CLUSTER-NSXT hosts? I tried to export the Port Group Configuration and import it into the CLUSTER-MGT dvSwitch but got the error that the Port Group 1017 already exists- I assume you can only have one Port Group with the VLAN ID 1017. vCenter 6.7U3q

JDMils_Interact · ‎05-30-2022

I had to move an ESXi host from vCenter A to vCenter B then move it back again to vCenter A a few days later, and the move was good, however the host now has a ">" arrow next to it in the Cluster vie...

I had to move an ESXi host from vCenter A to vCenter B then move it back again to vCenter A a few days later, and the move was good, however the host now has a ">" arrow next to it in the Cluster view, and if I click the arrow, it shows the same resource groups as the resource groups in the same cluster. What this means is that I can see the cluster resource groups as child resource groups attached to the host!? Although the host has no running VMs, when I open the resource groups attached to the host, I can see running VMs which are on other hosts. How can I get rid of this? Do I have to remove the host again? vCenter 6.7U3q ESXi 6.7.0 Build 19195723

JDMils_Interact · ‎05-03-2022

I found that this process works for me and for some reason does not give me the duplicate IP/MAC error: Power off the original server. Create a new vApp called Cloned_AD_vAPP. Add the network assign...

I found that this process works for me and for some reason does not give me the duplicate IP/MAC error: Power off the original server. Create a new vApp called Cloned_AD_vAPP. Add the network assigned to the original server to the vApp. Click Virtual Machines. Click vApp Source_vAPP | Actions | Copy To Select destination vApp Cloned_AD_vAPP Enter name of cloned server CLONED_SERVER Storage Policy acs_t0 Network Adatper Type: VMXNET3 Network: Network_Name IP Mode: Static IP- Manual IP Address: 192.168.0.10 Click Done I can then power on the cloned server with no errors!

JDMils_Interact · ‎05-02-2022

We have a virtual server with IP address 192.168.0.10 in vCD. I would like to clone this server so that I can run tests on it without affecting the original server. I tried copying the vm to a new v...

We have a virtual server with IP address 192.168.0.10 in vCD. I would like to clone this server so that I can run tests on it without affecting the original server. I tried copying the vm to a new vApp but when I try to start it from vCD I get the error: [ 995199e4-30a5-4aae-b948-9c589d654021 ] Unable to start vApp "vApp_MyTestServer". - The following IP/MAC addresses have already been used by running virtual machines: MAC addresses: IP addresses: 192.168.0.10 Use the Fence vApp option to use same MAC/IP. Fencing allows identical virtual machines in different vApps to be powered on without conflict, by isolating the MAC and IP addresses of the virtual machines. Is this not the correct way to clone a VM in vCD?

JDMils_Interact · ‎04-28-2022

Since VMware pulled out of VMware Converter for converting physical servers to virtuals, what's the next best tool for doing this? Paid and Free please.

JDMils_Interact · ‎04-27-2022

I'm upgrading our vCenters & hosts atm, and found a quirk in Update Manager. If I am upgrading one host using a custom ESXi baseline, initiated from the Host | Update tab, if then highlight another h...

I'm upgrading our vCenters & hosts atm, and found a quirk in Update Manager. If I am upgrading one host using a custom ESXi baseline, initiated from the Host | Update tab, if then highlight another host in the same cluster and either Check Compliance or Remediate a baseline, I get the errors: There are errors during the scan operation. Check the events and log files for details. and/or Cannot get exclusive access to all required entities. Please wait until all active operations complete and try again. and/or There are errors during the remediation operation. Check the events and log files for details. So it looks to me like if I want to Check Compliance or Remediate more than one host in a cluster, I need to initiate the processes from the Cluster view and cannot do it to individual hosts. Hosts are all V6.0U3d.

JDMils_Interact · ‎04-27-2022

Thanks. Looks like that fixed the issue.

JDMils_Interact · ‎04-27-2022

The virtual server has 190GB allocated to it.

JDMils_Interact · ‎04-27-2022

The server I am trying to migrate has 3.8GB memory used, 190GB allocated to the VM and is using 190.54GB of host memory.

All

JDMils_Interact's Posts

Re: Installing VMTools 12.1.0 onto ESXi 6.7 using vCenter V7.0 Lifecycle Manager

Re: Installing VMTools 12.1.0 onto ESXi 6.7 using vCenter V7.0 Lifecycle Manager

Installing VMTools 12.1.0 onto ESXi 6.7 using vCenter V7.0 Lifecycle Manager

vCenter: Clearing out unwanted files. Can I remove these files?

Re: Cannot upgrade/Check Compliance on multiple hosts using vCenter 6.7U3q

Re: Export PortGroup uplink details

Re: Export PortGroup uplink details

Re: Export PortGroup uplink details

Export PortGroup uplink details

Storage migration leaves VM swap files on original datastore

Re: Span a port group to another dvswitch in the vCenter

Span a port group to another dvswitch in the vCenter

Ghost Resource Groups following an ESXi host

Re: vCD:The following IP/MAC addresses have already been used by running virtual machines...

vCD:The following IP/MAC addresses have already been used by running virtual machines...

P2V conversions

Cannot upgrade/Check Compliance on multiple hosts using vCenter 6.7U3q

Re: Insufficient disk space on datastore 'xyz'.

Re: Insufficient disk space on datastore 'xyz'.

Re: Insufficient disk space on datastore 'xyz'.