vCenter 5.5 to 6.5 VCSA Upgrade

aeroliteflyer1 · ‎05-22-2017

Hello everyone,

I am trying to upgrade our vSphere version from 5.5 to 6.5. The current vCenter server is Windows. I am also going to the appliance. The upgrade path is supported in the matrix as well as documented by VMWare. When I run the migration assistant on the vCenter server, it stops at one error stating the ESX Agent Manager service is unresponsive. I have tried modifying the .xml config file from local host to the FQDN with no avail. When browsing to the website in the .xml, I get 503 service not available. In the web client, I go to the ESX Agent Manager link, and it has an error but nothing that says why. There is no ESX Agent Manager service on the vCenter server like I have seen on 6.0 threads. There has to be something simple I am missing, I just can't seem to find it. Was wondering if anyone else has run into this?

Thanks,

Chris.

aeroliteflyer1 · ‎05-25-2017

Anyone have a good starting point with EAM in 5.5. There doesn't seem to be any clear guidance on VMWare's site in troubleshooting EAM. The logs don't really indicate anything going back a year. Everything seems to be working ok. I did notice something strange on the performance tab-overview. I get page cant be displayed and it is trying to connect to the vCenter server on 8443. Trying to browse to it gives refuse to connect. No proxies or FW in the way and I am checking from the local server. This is really frustrating.

LokeshHK · ‎05-25-2017

EAM comes as Plug-in service and it looks like it is not deployed correctly.

Please check the Log "vsphere_client_virgo" in the below location C:\ProgramData\VMware\vSphere Web Client\serviceability\ for the details.(Check the for the details that EAM plugin is correctly downloaded and deployed)

Also try to restart the web-client service ones.

aeroliteflyer1 · ‎06-02-2017

Thanks for the response. I checked the logs at the location. There is so much information it's not useful. I don't see any errors pertaining to EAM. Restart the web-client service ones? Not sure what you mean by that. But if you mean restart the Web Client Service, I have already done that. As well as restart the server and etc... If it's a plug in service, how do I get it to reinstall. There is no documentation on that I have found. About how it actually gets to installed and operational. I did go ahead and update the vCenter server from 5.5u3b to 5.5u3e. All components. That didn't have any effect. Sorry but this really isn't helpful.

tkesi · ‎06-28-2018

I have come across the same problem. We are running 5.5 U3e on Win 2k8 SP2. On both the vCenter instances we have the same issue of EAM service not responding. The migration assistant fails and we cannot proceed with upgrade.

Was there ever a solution to this issue ?

tkesi · ‎07-09-2018

Just to inform anyone that comes across this issue, in our case it was being caused by another application using port 8003, which was designated for the tomcat server base.shutdownport. This configuration can be seen in vCenter_Install_Dir\Infrastructure\tomcat\conf\catalina.properties.

In the vCenter wrapper.log file the following error was being seen.

INFO | jvm 1 | --------- 13:15:59 | Jun 28, 2018 12:15:59 PM org.apache.catalina.core.StandardServer await

INFO | jvm 1 | --------- 13:15:59 | SEVERE: StandardServer.await: create[localhost:8003]:

INFO | jvm 1 | --------- 13:15:59 | java.net.BindException: Address already in use: JVM_Bind

Changing the base.shutdownport to 8013 in the config file and then restarting the vCenter Server resolved the issue. For the sake of making sure everything remains as per defaults before migration, we just removed the other service using port 8003 and stuck to the default. (even though we checked with VMware support who mentioned it was OK)

EDIT:

You can confirm EAM is working fine by going to https://vcenter_server_URL/eam/eamService-web/health.xml

The result will be as below:

<name>vSphere ESX Agent Manager</name><status>green</status>

</health>

</vimhealth>

Raj1988 · ‎07-09-2018

I had a case where it was a custom port for vpxd.

Take an RDP session into the Windows vCenter and perform the following steps:

1.Run the following command to check which port is being used by the vCenter(vpxd)

netstat-ban0>C:/ports.txt

Sample output:
Proto Local Address          Foreign Address        State           PID
TCP    0.0.0.0:80             0.0.0.0:0              LISTENING       4

Can not obtain ownership information
TCP    0.0.0.0:87             0.0.0.0:0              LISTENING       5156
[vpxd.exe]

2.Change the value of WebService.Ports.http to 80 (in the vCenter Thick Client >Administration > vCenter Server Settings > Advance Settings > WebService.Ports.http)
3.Verify the vc.proxy.port=80 in eam.properties file.(If not at port 80, change the value of vc.proxy.port to 80)
4.Restart vCenter box.

Raj1988 · ‎07-09-2018

Another case was ..

Solution:-

Regedit . VMwareInc> VMware Infrastructure>WebServer

Web Server http port :- 8080

Modified the catalina.properties from <C:\Program Files\VMware\Infrastructure\tomcat\conf>

bio-vmssl.http.port=8081 >>>>> Changed to port 8080

Open link http://localhost:80/eam/imx/esx_vm_16x.png ..if this open a small image ..that means ESX service is fine.