ssh_exchange_identification: read: Connection reset by peer.VMware vCenter Server
To restore management access, follow these steps:
Test Local Access:
Attempt to log in to the VAMI (https://<vCenter-IP>:5480) and SSH from a VM located on the same Layer 2 network segment as the vCenter Server.
Successful access from the local segment confirms that the appliance services are running and listening, narrowing the issue down to the external network path/routing, when trying to access VC from other subnet.
Review Perimeter Security:
Coordinate with the network or security team to inspect the physical firewalls between the source subnets and the vCenter appliance.
Configure Firewall Rules: Ensure that the following ports are explicitly allowed in the access control lists (ACLs):
TCP 5480: Required for VAMI access.
TCP 22: Required for SSH access.
Once the port 5480 is allowed, the output of the connectivity test, from the client system, using CURL should be as below. Verify VAMI is accessible.
Example:
For VAMI (Port 5480):
PS C:\> curl -v telnet://<vCenter_URL>:5480
* Trying <vCenter_IP_Address>:5480...
* Connected to <vCenter_URL> (<vCenter_IP_Address>) port 5480 (#0)
For SSH (Port 22):
PS C:\> curl -v telnet://<vCenter_URL>:22
* Trying <vCenter_IP_Address>:22...
* Connected to <vCenter_URL> (<vCenter_IP_Address>) port 22 (#0)