Cross vCenter vMotion Fails with Error “Unexpected Status Code: 503”
search cancel

Cross vCenter vMotion Fails with Error “Unexpected Status Code: 503”

book

Article ID: 414067

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

  • While performing a cross vCenter vMotion, the vMotion wizard displays the following error when attempting to connect to the target vCenter Server:

“Unexpected status code: 503”

  • The error “Unexpected Status Code: 503” suggests that the target vCenter service is not reachable, either due to temporary unavailability or because it is refusing incoming connections.

 

 

 

Environment

vCenter Server 7.x
vCenter Server 8.x

Cause

This issue occurs when required network ports for communication between the source and destination vCenter Servers and ESXi hosts are blocked or not accessible.

Resolution

Ensure that all required network ports are open and accessible between the source and destination vSphere environments. Blocked or restricted ports can prevent successful cross vCenter vMotion operations.

Required ports:

  • Port 8000 on the ESXi host for vMotion.
  • Port 902 on the ESXi host for NFC.
  • Port 443 between the two vCenter Server instances.

For the list of all supported ports and protocols in VMware products refer: https://ports.broadcom.com/

    Additional Information

    Export or Clone a Virtual Machine with Advanced Cross vCenter vMotion