Cloud Connect Replica Failover Plan Public IP Mapping more than one TCP port

[rleon]

Hi,

We're testing VCSP Replica Cloud Failover Plans and Public IP Mapping.
Things work fine. We can access the Failover VMs in the cloud by their mapped Public IPs and TCP port.
We mapped TCP port 3389 (Remote Desktop) so we can use a VM as a Jump Box to manage other VM Replicas in the Veeam Cloud.

Please refer to this screenshot.


Here's the thing, is there a way to access ALL 65535 TCP ports seeing that a dedicated Public IP is mapped to a Replica?
As the image shows, apparently we are limited to mapping only 1 TCP port per Replica. You can't even select a range of TCP ports.
It is not like the SP-Side-NEA's external Public IP is being shared. (I.e., we are not trying to map SP-Side-NEA's external Public IP's own TCP ports to Replicas.)
We are talking about a separate, dedicated Public IP mapped to a Replica, so I can't see why we are limited to mapping only 1 TCP port.
Also, is there a way to map UDP ports too?

Thanks for any insights.

[anthonyspiteri79]

Hey there... As amazing as what we have been able to offer tenants by way of automated networking for Cloud Connect Replication, the NEAs do have limitations by way of what can be configured via the VBR console. Pre Update 4, we gave VCSPs the option of using the built in NEAs or have a BYO Edge device.

With the introduction of Update 4, we tapped in vCloud Director and by extension NSX to allow our VCSPs to enhance their Cloud Connect Replication offerings.

The short answer to your question is that, if pre Update 4 Hardware Plans are used with NEAs the limitations you see are in play. If your VCSP offers Cloud Connect Replication backed by vCloud Director, then there are more powerful options available for you do do almost anything with the NSX Edge acting as the gateway for your replicas.

[rleon]

In other words, even with Update 4, the SP still has to have vCloud Director + NSX in order for Public IP mapping to Replicas to be able to utilize all TCP/UDP ports?
What if both Tenant and SP are at Update 4, but the SP does not have vCloud + NSX?
Does that mean the same limitation remains? (I.e., Each Replica can only have 1 TCP port forwarded, even with a dedicated Public IP mapped)
Thanks!

[anthonyspiteri79]

It's a limitation of the NEA acting as an Edge and what can be configured via VBR.

Though your VCSP can choose to not deploy the NEA and replace it with any networking edge device they have access to.

[rleon]

Thanks for clarifying everything. I'll go check out the options.