Answer
Note: If you are using PIM, please ignore the current article and use this article for Linux and this article for Windows instead.
On VA Management Node the following ports should be opened (for both incoming and outgoing TCP connections):
- port 22- (Linux only), it is required for SSH connections and OBAS integration;
- port 3389 - (Windows only), it is required for RDP connections;
- port 389 - should be open for incoming/outgoing connections from VA Slave Nodes;
- port 4533 - TCP connections to VA MN Nodes (from any);
- port 4534 - SSL connections to VA MN Nodes (from any);
- port 4648– connections to VA Control Panel Web interface;
- ports 4450,4452 - used for connection to ADAM and VA authorization;
- port 80 - HTTP redirect for VA CP;
- port 443 - for VA CP;
- port 1433 - Used by PMC, to retrive statistics from MSSQL database.
On VA Slave Node the following ports should be opened (for both incoming and outgoing connections):
- port 22- (Linux only), it is required for SSH connections and OBAS integration;
- port 3389 - (Windows only), it is required for RDP connections;
- ports 4643, 8443 from everywhere: those are the Power Panel and Plesk ports;
- port 4646 is a port of VZAgent SOAP interface; open it for selected hosts if you are going to use it;
- port 4649 for vzpp-desktop
- ports 8443, 8880 - integration between Pleskl and Power Panel;
- ports 25, 110, 80 from everywhere: Power Panel takes the IP address of a container, which is down for backuping or migration and displays a nice maintenance message; port 25 should also be opened for namebased hosting;
- ports 4433, 4435 - TCP connections to VA Slave Nodes (from any);
- port 4434 - SSL connections to VA Slave Nodes (from any);
- port 4534 - SSL (encrypted) XML connections to VA MN;
- port 64000 - Dispatcher connection for Management console (Virtuozzo and Virtuozzo hypervisor nodes only).