Today we updated our cloud connect server to v12. Once that was complete we upgraded two of our managed clients running Veeam backup and replication to v12.
My issue is once the Tenant side was updated to v12 I am no longer able to connect to the service provider. I believe this is the related log…
[14.03.2023 16:07:00.582] <117> Error A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
But this is only happening from tenants that updated to v12, all other tenants running v11 are able to connect without issue.
We have a support case open, Case # 05943021
Question
Tenant v12 to Service Provider v12
+8I don’t have a solution, but I can say that I have had no issues with v12 deployments connecting to my v12 console/VCC server.
Derek M. Loseke, Senior Systems Engineer | Veeam Legend 2022-2024 | VMSP/VMTSP | VCP6-DCV | VSP/VTSP | CCNA | https://technotesanddadjokes.com | @dloseke
1 person likes this
+21Try on the Tenant side to edit the Service Provider and go through the configuration as that might help to narrow it down possibly.
Chris Childerhose - VMCA2024 | VMCE2023 | VMCE-SP2024 | Veeam Vanguard 8* | Veeam Legend 5* | vExpert 6* | VCAP-DCV/VCP-DCV | Object First Ace | Cisco Champion | Twitter: @cchilderhose | Blog Site – https://just-virtualization.tech
1 person likes this
After having our network team investigate we have learned that our inspection policy on our Palo firewall permits traffic to our cloud connect environment that matches the signature for Veeam cloud connect traffic using port 6180. The traffic is now presenting as unknown to the Palo and there for dropped. The work around was to disable the inspection. After that change was pushed our v12 Tenants were able to access their cloud resources as expected.
+21GLS2 wrote:
After having our network team investigate we have learned that our inspection policy on our Palo firewall permits traffic to our cloud connect environment that matches the signature for Veeam cloud connect traffic using port 6180. The traffic is now presenting as unknown to the Palo and there for dropped. The work around was to disable the inspection. After that change was pushed our v12 Tenants were able to access their cloud resources as expected.
Interesting that it would not be known traffic. Glad to hear you have a root cause and hopefully a better fix can be found.
Chris Childerhose - VMCA2024 | VMCE2023 | VMCE-SP2024 | Veeam Vanguard 8* | Veeam Legend 5* | vExpert 6* | VCAP-DCV/VCP-DCV | Object First Ace | Cisco Champion | Twitter: @cchilderhose | Blog Site – https://just-virtualization.tech
+3GLS2 wrote:
After having our network team investigate we have learned that our inspection policy on our Palo firewall permits traffic to our cloud connect environment that matches the signature for Veeam cloud connect traffic using port 6180. The traffic is now presenting as unknown to the Palo and there for dropped. The work around was to disable the inspection. After that change was pushed our v12 Tenants were able to access their cloud resources as expected.
I have the same Problem with one Tenant and a Fortigate Firewall on customers site. After deactivating the security profiles on the outgoing Firewall Rule the tenant connected to the VCSP successfully.
+8At the moment my clients have not experienced these problems, but thank you for sharing your case histories!
Marco Sorrentino - Italy | System Engineer | VMCE & VMCA
1 person likes this
Comment
Rich Text Editor, editor1
Editor toolbars
Press ALT 0 for help
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.