amirzadeh's Posts

I actually tried the forwarder before and the DHCP process would not complete for some reason - I moved away from it and setup the extra NICs.  That started to work for some interfaces but obviously ... See more...
I actually tried the forwarder before and the DHCP process would not complete for some reason - I moved away from it and setup the extra NICs.  That started to work for some interfaces but obviously I ran into a problem after a few of them.  I just removed all of the NICs and changed the DNS in DHCP to the local interface address and it started to work so I now I'm not sure what the original problem was.  Thank you for the recommendation to try it again, so much simpler.
I have multiple VLANs in my homelab. VLAN 1 (default) VLAN 10 (guest) - portgroup: std-0-guest-10 VLAN 66 (IOT) - portgroup: std-0-iot-66 ... Gateway is a PfSense+ on a Netgate 3100 -- everythin... See more...
I have multiple VLANs in my homelab. VLAN 1 (default) VLAN 10 (guest) - portgroup: std-0-guest-10 VLAN 66 (IOT) - portgroup: std-0-iot-66 ... Gateway is a PfSense+ on a Netgate 3100 -- everything works if I use an external DNS for the network (via DHCP) if I use the internal DNS that I would like to use, nothing resolves. I'm running an Ubuntu VM that runs DNS and I need it to have available on all VLANs.  The device has multiple vEth, on each network.  The Guest VLAN works, gateway can ping server, server can ping gateway, DNS works.  Device on IOT VLAN cannot get to DNS. From server: # ping -I ens224 192.168.66.1 PING 192.168.66.1 (192.168.66.1) from 192.168.66.80 ens224: 56(84) bytes of data. 64 bytes from 192.168.66.1: icmp_seq=1 ttl=64 time=0.947 ms 64 bytes from 192.168.66.1: icmp_seq=2 ttl=64 time=0.406 ms From gateway: PING 192.168.66.3 (192.168.66.3) from 192.168.66.1: 56 data bytes --- 192.168.66.3 ping statistics --- 3 packets transmitted, 0 packets received, 100.0% packet loss # ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever 2: ens160: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether 00:50:56:8f:7c:64 brd ff:ff:ff:ff:ff:ff inet 192.168.1.3/24 brd 192.168.1.255 scope global ens160 valid_lft forever preferred_lft forever 3: ens192: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether 00:0c:29:60:87:79 brd ff:ff:ff:ff:ff:ff inet 192.168.107.3/24 brd 192.168.107.255 scope global ens192 valid_lft forever preferred_lft forever inet 192.168.107.130/24 brd 192.168.107.255 scope global secondary noprefixroute ens192 valid_lft forever preferred_lft forever 4: ens224: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether 00:50:56:bd:5b:45 brd ff:ff:ff:ff:ff:ff inet 192.168.66.3/24 brd 192.168.66.255 scope global ens224 valid_lft forever preferred_lft forever inet 192.168.66.80/24 brd 192.168.66.255 scope global secondary noprefixroute ens224 valid_lft forever preferred_lft forever 5: ens256: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether 00:50:56:bd:ca:34 brd ff:ff:ff:ff:ff:ff inet 192.168.10.3/24 brd 192.168.10.255 scope global ens256 valid_lft forever preferred_lft forever inet 192.168.10.10/24 brd 192.168.10.255 scope global secondary noprefixroute ens256 valid_lft forever preferred_lft forever 6: v10@ens256: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 00:50:56:bd:ca:34 brd ff:ff:ff:ff:ff:ff inet 192.168.10.3/24 brd 192.168.10.255 scope global v10 valid_lft forever preferred_lft forever 7: v66@ens224: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 00:50:56:bd:5b:45 brd ff:ff:ff:ff:ff:ff inet 192.168.66.3/24 brd 192.168.66.255 scope global v66 valid_lft forever preferred_lft forever 8: v107@ens192: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 00:0c:29:60:87:79 brd ff:ff:ff:ff:ff:ff inet 192.168.107.3/24 brd 192.168.107.255 scope global v107 valid_lft forever preferred_lft forever # netstat -nr Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 ens160 0.0.0.0 192.168.107.1 0.0.0.0 UG 0 0 0 ens192 0.0.0.0 192.168.66.1 0.0.0.0 UG 0 0 0 ens224 0.0.0.0 192.168.10.1 0.0.0.0 UG 0 0 0 ens256 0.0.0.0 0.0.0.0 0.0.0.0 U 0 0 0 v107 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 ens160 192.168.10.0 0.0.0.0 255.255.255.0 U 0 0 0 ens256 192.168.10.0 0.0.0.0 255.255.255.0 U 0 0 0 v10 192.168.66.0 0.0.0.0 255.255.255.0 U 0 0 0 v66 192.168.66.0 0.0.0.0 255.255.255.0 U 0 0 0 ens224 192.168.107.0 0.0.0.0 255.255.255.0 U 0 0 0 v107 192.168.107.0 0.0.0.0 255.255.255.0 U 0 0 0 ens192 I used `vim-cmd vmsvc/device.getdevices 27` to see if I can see any differences attaching it just for reference.
That was it, I was tagging both the port and the port group.  Thank you.
@maksym007I think there was a misunderstanding.  Allow me to clarify - my pfsense is outside of ESX and the router/gateway of the network with various interfaces on it.  192.168.1.0/24 (main LAN on V... See more...
@maksym007I think there was a misunderstanding.  Allow me to clarify - my pfsense is outside of ESX and the router/gateway of the network with various interfaces on it.  192.168.1.0/24 (main LAN on VLAN 1) as well as the 192.168.107.0/24 (VLAN 107).  I can ping the 192.168.107.1 (pfsense interface) from any machine on the 192.168.1.0 network however when I deploy a VM on ESX on the 192.168.107.0 network I cannot ping anything.
I'm running on ESXi 7, vSphere 7 (no NSX, etc).  Setup: pfSense  + switch (tp-link switches, vlan aware ... I have tagged all ports with vlan 107). + esx host (192.168.1.7) My base subnet is 192... See more...
I'm running on ESXi 7, vSphere 7 (no NSX, etc).  Setup: pfSense  + switch (tp-link switches, vlan aware ... I have tagged all ports with vlan 107). + esx host (192.168.1.7) My base subnet is 192.168.1.0/24, everything there is working well and is connected. I'm testing/playing with Kubernetes and with that I would like to be able to use another subnet as my public ips for the services.  I went with 192.168.107.0/24. I created a base ubuntu vm, (put it on the std-0-kub-107 network) statically assigned 192.168.107.3, gateway of 192.168.107.3 ... but it can't reach anything and nothing can reach it. From the ESX host I can ping the 107 interface on pfsense: [root@esxi7:~] ping 192.168.107.1 PING 192.168.107.1 (192.168.107.1): 56 data bytes 64 bytes from 192.168.107.1: icmp_seq=0 ttl=64 time=0.466 ms 64 bytes from 192.168.107.1: icmp_seq=1 ttl=64 time=0.414 ms --- 192.168.107.1 ping statistics --- 2 packets transmitted, 2 packets received, 0% packet loss round-trip min/avg/max = 0.414/0.440/0.466 ms I created a port group and assigned it to the VLAN . [root@esxi7:~] esxcfg-vswitch -l Switch Name Num Ports Used Ports Configured Ports MTU Uplinks vSwitch0 6400 32 128 1700 vmnic0,vmnic3,vmnic2,vmnic1 PortGroup Name VLAN ID Used Ports Uplinks std-0-kub-107 107 1 vmnic0,vmnic3,vmnic2,vmnic1 std-0-vlan-0000 4095 18 vmnic0,vmnic3,vmnic2,vmnic1 What step am I missing?
Following this fix all my upgrade issues: https://williamlam.com/2021/03/vcsa-7-0-update-2-upgrade-issue-exception-occurred-in-install-precheck-phase.html
Thank you for that link, worked.  The only thing is the URL says "-url" and "-acceptEula"  It's actually "--url" and "--acceptEula". Command> software-packages install --url --acceptEulas [2021-05... See more...
Thank you for that link, worked.  The only thing is the URL says "-url" and "-acceptEula"  It's actually "--url" and "--acceptEula". Command> software-packages install --url --acceptEulas [2021-05-26T17:29:40.146] : UpdateInfo: Using product version 7.0.2.00100 and build 17920168 [2021-05-26T17:29:41.146] : Target VCSA version = 7.0.2.00200 [2021-05-26 17:29:41,182] : Running requirements script..... [2021-05-26T17:30:01.146] : Evaluating packages to stage... [2021-05-26T17:30:01.146] : Verifying staging area [2021-05-26T17:30:01.146] : For the first instance of the identity domain, this is the password given to the Administrator account. Otherwise, this is the password of the Administrator account of the replication partner. Enter Single Sign-On administrator password: [2021-05-26T17:30:34.146] : Validating software update payload [2021-05-26T17:30:34.146] : UpdateInfo: Using product version 7.0.2.00100 and build 17920168 [2021-05-26 17:30:34,782] : Running validate script..... [2021-05-26T17:30:43.146] : Validation successful [2021-05-26 17:30:43,821] : Copying software packages 53/53 [2021-05-26 17:31:54,155] : Running system-prepare script..... [2021-05-26 17:32:03,195] : Running test transaction .... [2021-05-26 17:32:05,283] : Running prepatch script..... [2021-05-26 17:33:40,496] : Upgrading software packages .... [2021-05-26T17:34:45.146] : Setting appliance version to 7.0.2.00200 build 17958471 [2021-05-26 17:34:45,738] : Running patch script..... [2021-05-26 17:46:49,299] : Starting all services .... [2021-05-26T17:46:50.146] : Services started. [2021-05-26T17:46:50.146] : Installation process completed successfully
  Current: VMware vCenter Server  7.0.2.00100 Available: 7.0.2.00200   I seem to be stuck in a update pre-check cycle in VAMI: Installation failed Exception occurred in install precheck pha... See more...
  Current: VMware vCenter Server  7.0.2.00100 Available: 7.0.2.00200   I seem to be stuck in a update pre-check cycle in VAMI: Installation failed Exception occurred in install precheck phase Click "continue" Installation pre-check results      Running installation pre-checks Pre-checks passed. No issues found Click "Continue" ... and you end up in the Installation Failed screen again. Any ideas on how to proceed?  Thank you.
I'm running ESX 7 and vSphere 7.0.2, fully patched, single server just a home lab. I enabled mail/SMTP on vSphere so that I can get alerts but now I'm getting "success" emails every days.  For exam... See more...
I'm running ESX 7 and vSphere 7.0.2, fully patched, single server just a home lab. I enabled mail/SMTP on vSphere so that I can get alerts but now I'm getting "success" emails every days.  For example: Subject: [VMware Workstation] task - Task VMware vSphere Lifecycle Manager Update Download on Datacenters in datacenter completed successfully Task VMware vSphere Lifecycle Manager Update Download on Datacenters in datacenter completed successfully How do I disable or change the limit on what is emailed?  I don't need to know the successful attempts.    
One thing I can suggest is if you can download the ISO and mount it to the vcenter.  That'll skip the download stage issue, that was going to be my next attempt.
I was going to just post my previous attempts logs but decided to capture a fresh log so I reset the applmgr service and status and tried again Lo and behold it worked this time.  Here is the log: ... See more...
I was going to just post my previous attempts logs but decided to capture a fresh log so I reset the applmgr service and status and tried again Lo and behold it worked this time.  Here is the log: Command> software-packages list --staged [2021-04-05T21:35:28.095] : category: Bugfix kb: https://docs.vmware.com/en/VMware-vSphere/7.0/rn/vsphere-vcenter-server-702-release-notes.html leaf_services: ['vmware-pod', 'vsphere-ui', 'wcp', 'vlcm'] vendor: VMware, Inc. name: VC-7.0.2 size in MB: 5313 tags: [] changesetnumber: 8786438 version_supported: [] productname: VMware vCenter Server releasedate: March 9, 2021 executeurl: https://my.vmware.com/group/vmware/get-download?downloadGroup=VC70U2 version: 7.0.2.00000 updateversion: True allowedSourceVersions: [7.0.0.0,] buildnumber: 17694817 rebootrequired: False summary: {'id': 'patch.summary', 'translatable': 'In-place upgrade for vCenter appliances.', 'localized': 'In-place upgrade for vCenter appliances.'} type: Update severity: Critical TPP_ISO: False url: https://vapp-updates.vmware.com/vai-catalog/valm/vmw/8d167796-34d5-4899-be0a-6daade4005a3/7.0.0.10300.latest/ thirdPartyAvailable: False nonThirdPartyAvailable: True thirdPartyInstallation: False timeToInstall: 0 requiredDiskSpace: {'/storage/core': 5.785542793273925, '/storage/seat': 7.36015625} eulaAcceptTime: 2021-04-05 21:32:58 UTC Command> software-packages install --staged [2021-04-05T21:36:25.095] : For the first instance of the identity domain, this is the password given to the Administrator account. Otherwise, this is the password of the Administrator account of the replication partner. Enter Single Sign-On administrator password: [2021-04-05T21:36:59.095] : Validating software update payload [2021-04-05T21:36:59.095] : UpdateInfo: Using product version 7.0.1.00300 and build 17491101 [2021-04-05 21:36:59,462] : Running validate script..... [2021-04-05T21:37:07.095] : Validation successful [2021-04-05 21:37:07,500] : Copying software packages 150/150 [2021-04-05 21:42:16,579] : Running system-prepare script..... [2021-04-05 21:42:24,617] : Running test transaction .... [2021-04-05 21:42:29,662] : Running prepatch script..... [2021-04-05 21:45:39,048] : Upgrading software packages .... [2021-04-05T21:50:04.095] : Setting appliance version to 7.0.2.00000 build 17694817 [2021-04-05 21:50:04,826] : Running patch script..... [2021-04-05 22:03:16,683] : Starting all services .... [2021-04-05T22:03:18.095] : Services started. [2021-04-05T22:03:18.095] : Installation process completed successfully
@VMAKSthanks for the notes. The wget (no proxy) works fine, pulls the manifest and it's a valid XML file. The link you provided to do the update seems to be for v6, and I need the v7 link? I shoul... See more...
@VMAKSthanks for the notes. The wget (no proxy) works fine, pulls the manifest and it's a valid XML file. The link you provided to do the update seems to be for v6, and I need the v7 link? I should mention that the steps in that KB to do the manual install is exactly what I followed which resulted in the error in the original post.  Via URL, rather than ISO. command> software-packages stage --url command> software-packages list --staged command> software-packages install --staged
Hi, I tried to do the upgrade via the VMware Appliance Management, the pre-check and staging worked but the install failed at 60%. Installation failed Exception occurred in install precheck phase.... See more...
Hi, I tried to do the upgrade via the VMware Appliance Management, the pre-check and staging worked but the install failed at 60%. Installation failed Exception occurred in install precheck phase.  I found this error in the logs: Error in method invocation [Errno 2] No such file or directory: '/storage/core/software-update/updates/index'  The directory does exist. I unstagged the update and tried it on the command line to see if I can get a better error message. I used the SSH Command prompt: Command> software-packages install [2021-03-27T20:41:47.086] : For the first instance of the identity domain, this is the password given to the Administrator account. Otherwise, this is the password of the Administrator account of the replication partner. Enter Single Sign-On administrator password: [2021-03-27T20:41:51.086] : Validating software update payload [2021-03-27T20:41:51.086] : UpdateInfo: Using product version 7.0.1.00300 and build 17491101 [2021-03-27 20:41:51,764] : Running validate script..... [2021-03-27T20:41:57.086] : Validation successful [2021-03-27 20:41:57,795] : Copying software packages [2021-03-27T20:42:15.086] : Installation process failed [2021-03-27T20:42:15.086] : Package checksum verification failed.  
VMCA appliance.. but the post is now moot.  I deleted the instance, re-installed and tried to restore from backup but then it wouldn't let me actually restore because I had no resource pools assigned... See more...
VMCA appliance.. but the post is now moot.  I deleted the instance, re-installed and tried to restore from backup but then it wouldn't let me actually restore because I had no resource pools assigned (which seems to be a DRS? feature) which I don't have. I finally just imported the DS and VMs back in manually and left it unpatched.  Seems like patching is not a good idea, even though it's critical.
I had an "urgent" update for my appliance so I went to vSphere manager and started the update and everything was going fine until it got stuck at 92%. I tried restarting the VM after the instance co... See more...
I had an "urgent" update for my appliance so I went to vSphere manager and started the update and everything was going fine until it got stuck at 92%. I tried restarting the VM after the instance comes back online (no matter what URL you go to) you end up on the converting screen and it's still sitting at 92%. Any help would be greatly appreciated. [ I do have a Snapshot of the VM, and VMSA backup available ]