![[H]ard|Forum](/styles/hardforum/xenforo/logo_dark.png){kind=logo}
Solved, read the edit at the end of this post if interested.
Alright, this is getting really goofy. I just got vCenter Update Manager running. I've been able to scan 3 hosts just fine, and just tried to perform remediation on one.
Remediation appears to be successful on this one host, however depending on how you read the logs, there was an entry (before install?) that referenced the same error (Host cannot download files from VMware vSphere Update Manager patch store, etc) I'm getting now. There is a later entry indicating that remediation for this host was successful.
The problem after remediation: vUM is unable to ping that host now. I can ping it from any other machine, except vUM. I can still scan the other two hosts just fine, no issues.
I tried explicitly opening the port for vUM as well on that host. Still nothing, and still unable to ping/connect to this one host. Firewall on vUM is completely off for all profiles. Network connectivity is fine, able to resolve other host names/ping other IP addresses. The problem host and vUM have both been rebooted. The problem host did reappear in vCenter following a reboot, so it seems fair that the host is ok as far as connectivity is concerned.
I saw NetJunkies blog about this indicating a problem with DNS. When vUM was installed earlier today I do remember that it gave me the choice of how to address it. I chose to reference it by IP. Just for the sake of checking I did check DNS on all hosts, and they all match.
What in the world am I missing?
Solution: I had a failover NIC designated for management on this host. When it rebooted, both vmnic0 and 1 were checked as active. A test ping on the DCUI failed. Unchecked vmnic1, back to normal. I did not consider this scenario, as that adapter is shown as a failover, not part of a team on the switch or ESX config. I still don't know why it was flagged as active. It also explains why an earlier junk box upgraded with no issue - there is no management failover set.
Alright, this is getting really goofy. I just got vCenter Update Manager running. I've been able to scan 3 hosts just fine, and just tried to perform remediation on one.
Remediation appears to be successful on this one host, however depending on how you read the logs, there was an entry (before install?) that referenced the same error (Host cannot download files from VMware vSphere Update Manager patch store, etc) I'm getting now. There is a later entry indicating that remediation for this host was successful.
The problem after remediation: vUM is unable to ping that host now. I can ping it from any other machine, except vUM. I can still scan the other two hosts just fine, no issues.
I tried explicitly opening the port for vUM as well on that host. Still nothing, and still unable to ping/connect to this one host. Firewall on vUM is completely off for all profiles. Network connectivity is fine, able to resolve other host names/ping other IP addresses. The problem host and vUM have both been rebooted. The problem host did reappear in vCenter following a reboot, so it seems fair that the host is ok as far as connectivity is concerned.
I saw NetJunkies blog about this indicating a problem with DNS. When vUM was installed earlier today I do remember that it gave me the choice of how to address it. I chose to reference it by IP. Just for the sake of checking I did check DNS on all hosts, and they all match.
What in the world am I missing?
Solution: I had a failover NIC designated for management on this host. When it rebooted, both vmnic0 and 1 were checked as active. A test ping on the DCUI failed. Unchecked vmnic1, back to normal. I did not consider this scenario, as that adapter is shown as a failover, not part of a team on the switch or ESX config. I still don't know why it was flagged as active. It also explains why an earlier junk box upgraded with no issue - there is no management failover set.
Last edited: