VMware Cloud Community
ksagona
Contributor
Contributor
Jump to solution

Cannot install the vCenter agent service. Cannot upload agent.

I'm having a bit of trouble with three of my ESX servers. I'm running vCenter Server 4.0.0, 162856. I have three clusters that I am currently trying to use. One is my test environment blade cluster on our old equipment on our internal network (running ESX 3.5). One is our new blade cluster on our internal network. The final (and the one I'm having trouble with) is the blade cluster on our external network. The new ones are running ESX 4.0.

When I tried to add new hosts to our new blade cluster on the internal network, everything went relatively smoothly. I'm trying to simply add the hosts to the cluster on the external network, but every time, I get the "Cannot install the vCenter agent service. Cannot upload agent" error. I've read on the web that this might happen sporadically, and to try removing/restarting your ESX servers. I've tried with all three, and none will upload. I initially thought that my hosts hard drives were too small as I'm booting from SAN and have carved out 25GB drives strictly for the OS. So, I tried 50GB hard drives, and that didn't help.

My guess is that there may be some sort of firewall issue, and asked our network guys to unblock ports 902, 905, and 8443. That still doesn't seem to help. I've checked the /etc/hosts file, and the three servers, the vCenter server, and the server for the backup is defined in there. I've also tried removing and readding the cluster. Pinging the servers that are defined in the hosts file works (but no other local servers)The only thing that isn't working that I know of is vmkping, which gives a *** vmkernel stack not configured *** error.

Does anyone have some ideas? Do you think it's firewall or vmkernel related? My understanding was that the vmkernel would start after it's joined to a host, but I could be wrong about that.

Thanks to all who help!

0 Kudos
1 Solution

Accepted Solutions
AntonVZhbankov
Immortal
Immortal
Jump to solution

port 443 is also required


---

MCSA, MCTS, VCP, VMware vExpert '2009

http://blog.vadmin.ru

EMCCAe, HPE ASE, MCITP: SA+VA, VCP 3/4/5, VMware vExpert XO (14 stars)
VMUG Russia Leader
http://t.me/beerpanda

View solution in original post

0 Kudos
4 Replies
AntonVZhbankov
Immortal
Immortal
Jump to solution

port 443 is also required


---

MCSA, MCTS, VCP, VMware vExpert '2009

http://blog.vadmin.ru

EMCCAe, HPE ASE, MCITP: SA+VA, VCP 3/4/5, VMware vExpert XO (14 stars)
VMUG Russia Leader
http://t.me/beerpanda
0 Kudos
ksagona
Contributor
Contributor
Jump to solution

Thanks, will give that a try and report back.

0 Kudos
ksagona
Contributor
Contributor
Jump to solution

They just checked. Port 443 has been open. But, apparently the firewall was letting another group of ESXi servers through, not mine. We switched the firewall rules to my servers, and poof...uploaded instantly. Whoo!

Thanks again AntonVZhbankov for helping me. I really appreciate it!

0 Kudos
AntonVZhbankov
Immortal
Immortal
Jump to solution

You're welcome!


---

MCSA, MCTS, VCP, VMware vExpert '2009

http://blog.vadmin.ru

EMCCAe, HPE ASE, MCITP: SA+VA, VCP 3/4/5, VMware vExpert XO (14 stars)
VMUG Russia Leader
http://t.me/beerpanda