clevervinicius commented on issue #7514: URL: https://github.com/apache/cloudstack/issues/7514#issuecomment-1542433197
#what about other vms in the same VPC ? The other VM in the same VPC keeps connecting. what's the redundant state of the VPC VRs ? Primary - Running - Backup - Running My issue scenario: (example ips) Redundant Router (10.1.0.1) VM1 (10.1.0.20) internal (33.33.33.33) public - Static NAT VM2 (database (10.1.0.21) On normal state: The VM1 connect to internal API on VM1 per public IP - VM1 IP Internal > Router > VM1 IP public > Router > VM1 IP internal > Connect OK On problem state: The VM1 try connect to internal API on VM1 per public IP - VM1 IP Internal > Router > VM1 IP public X(?) > Router X(?) VM1 IP internal > Not connected There is an application inside the VM itself that needs to connect with itself, but when the router has a problem, it interrupts the communication. External communication is still normal, I can connect directly to this application from a connection outside the VPC. Another explanation approach: An API inside VM1 connects to VM1 itself, but through public IP set in static NAT, and goes back to VM1 itself, in some moments this connection stops happening and that's exactly where my problem is. Monitoring the VM1 lan IP or even VM2 lan IP (database) there are no connection problems. The problem is only when my client's API accesses the VM itself through the public ip. The client accesses the public IP because he uses the domain of his website in his application to consume his own API. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
