Wrong port for OLVM worker communication in v13

[e.rottier]

Hi,

I've recently upgraded to B&R v13.
One of my issues was that I couldn't connect to workers anymore via OLVM managed VMs.

We have ACL's in place on our switches for isolation purposes. In these switches we made an allow-all rule and suddenly everything worked again, while no changes in ports where made according to the v13 docs.

I've now checked the communication streams with Wireshark and found that B&R suddenly uses another port for Worker -> Backup server communication.
It used to be TCP 10006, but now it uses TCP 19000.

Interestingly, this actually is the port both Proxmox and Nutanix use for this kind of communication.

Either the documentation is wrong, or it's an bug in v13.

Thanks!

OLVM port requirements: https://helpcenter.veeam.com/docs/vbrhv/userguide/used_ports.html?ver=7
Proxmox port requirements: https://helpcenter.veeam.com/docs/vbproxmoxve/userguide/used_ports.html?ver=3

Support ID: #07948795

[Moderator: Updated with Case ID instead of Support ID]

[rovshan.pashayev]

Thanks for the feedback!

This is a documentation error, and the docs will be corrected ASAP.

[e.rottier]

Thanks Rovshan!

So does this mean it's also a change from v12 to v13, since it used to work over port 10006?

[cody.ault]

There is an architectural difference between v12 and v13. V13 removed the need for a dedicated appliance which had some of the job logic built-in and made it more in line with how we're creating new plug-ins like Proxmox where the service on the VBR server takes care of that part of the job management and we only need a worker now.

[e.rottier]

Hi Cody, thanks for explaining. Sounds like a logical thing to do indeed. So if I understand you correctly, there was indeed a port change from 10006 to 19000 due to a logic switch/change.

I would suggest not only correcting the documentation, but also add a port-change notification to the what's new list or somewhere similar.