JKR16
Contributor
Contributor

error: VAMI is NOT accessible when upgrade 6.5 to 6.7

Hi Anyone face this issue when upgrade the VM 6.5 to 6.7

2018-05-09T13:16:10.580Z - error: VAMI is NOT accessilbe[1]: https://vcenter-67.nono.io:5480/, err: Request timed out after 30000 ms, url: https://vcenter-67.nono.io:5480/

2018-05-09T13:16:40.584Z - error: Request timed out after 30000 ms, url: https://vcenter-67.nono.io:5480/

2018-05-09T13:16:40.584Z - error: VAMI is NOT accessilbe[2]: https://vcenter-67.nono.io:5480/, err: Request timed out after 30000 ms, url: https://vcenter-67.nono.io:5480/

2018-05-09T13:16:55.958Z - error: Could not get response for get request from url https://vcenter-67.nono.io:5480/: Error: connect ETIMEDOUT 10.0.9.67:5480

2018-05-09T13:17:10.587Z - error: Request timed out after 30000 ms, url: https://vcenter-67.nono.io:5480/

2018-05-09T13:17:10.587Z - error: VAMI is NOT accessilbe[3]: https://vcenter-67.nono.io:5480/, err: Request timed out after 30000 ms, url: https://vcenter-67.nono.io:5480/

2018-05-09T13:17:26.028Z - error: Could not get response for get request from url https://vcenter-67.nono.io:5480/: Error: connect ETIMEDOUT 10.0.9.67:5480

2018-05-09T13:17:40.587Z - error: Request timed out after 30000 ms, url: https://vcenter-67.nono.io:5480/

2018-05-09T13:17:40.587Z - error: VAMI is NOT accessilbe[4]: https://vcenter-67.nono.io:5480/, err: Request timed out after 30000 ms, url: https://vcenter-67.nono.io:5480/

2018-05-09T13:17:56.430Z - error: Could not get response for get request from url https://vcenter-67.nono.io:5480/: Error: connect ETIMEDOUT 10.0.9.67:5480

thanks,

Tags (1)
0 Kudos
4 Replies
stgepopp
Hot Shot
Hot Shot

Hi jkr16,

if your upgrade process has succeeded stage 1 you are safe to open the VAMI portal with IP address:5480. Check accessability before und continue with stage 2.

Probably a problem with DNS.

Erich

0 Kudos
sk84
Expert
Expert

I'm a little surprised. Have you changed the vCenter name? If you were on version 6.5 before, I can hardly imagine that the vCenter was always called "vcenter-67.nono.io". However, it is not supported to change the vCenter's FQDN because it is used internally as a PNID (for SSO among other things).

In case of a timeout problem I also assume that it is a DNS or firewall issue.

--- Regards, Sebastian VCP6.5-DCV // VCP7-CMA // vSAN 2017 Specialist Please mark this answer as 'helpful' or 'correct' if you think your question has been answered correctly.
0 Kudos
JKR16
Contributor
Contributor

Hi I am not so sure why the DNS change to that name "vcenter-67.nono.io" when the installation process I put my local IP address not the FQDN.

Any Idea!!

0 Kudos
sk84
Expert
Expert

The domain "nono.io" is publicly resolvable. So, if I do an nslookup in Windows for "vcenter-67.nono.io" I get the following ip addresses:

2601:646:100:69f0::67

10.0.9.67

Are they correct?

And you write

when the installation process I put my local IP address not the FQDN.

What do you mean with "my local IP address" ? Is it the IP mentioned above or the ip address of your local workstation?

And are you able to ping to vcenter ip address?

ping 10.0.9.67

Maybe it makes sense if you describe which steps and which configurations you have made exactly during the upgrade process.

--- Regards, Sebastian VCP6.5-DCV // VCP7-CMA // vSAN 2017 Specialist Please mark this answer as 'helpful' or 'correct' if you think your question has been answered correctly.
0 Kudos