Editing cloud server ports and port ranges

Edit the ports that a cloud server (except for the cloud partners and cloud arbiter) uses, as well as the port ranges that are used to assign ports to new cloud servers.

Prerequisites

To change the port ranges for all new hosts being added to the cloud, you must have the AlterCloud privilege.

To change the port ranges for all new servers created on a host, you must have the AddHost, DropHost, and InstallHost privileges.

To change the ports of an existing cloud server, you must have the CreateDropServer privilege.

Context

All cloud servers, including the cloud partners and cloud arbiters, use a single server port for each of the TCP/IP (Command Sequence and TDS), HTTP, and HTTPS protocols.

You cannot change the ports for the cloud partners and cloud arbiter directly. Their ports remain fixed for the life of the cloud partner or cloud arbiter.

Procedure

Choose one of the following options:

Option

Action

Change the port ranges for all new hosts added to the cloud

Navigate to the cloud Overview panel, and click PropertiesPorts.

Change the port ranges for all new servers created on a host

Navigate to the host Overview panel and stop all cloud servers on the host.

Click Set ports and specify the port ranges.

Restart the cloud servers.

Change the ports of an existing cloud server

Navigate to the cloud server Overview panel, and stop the cloud server.

Click Set ports and specify the ports.

Restart the cloud server.

Results

When you change the cloud port ranges, these port ranges are assigned by default to new hosts.

When you change the port range of a host, all cloud servers that do not have static ports use ports from the new range. Only cloud servers with static ports continue to use the same ports, even if their port numbers do not belong to the current port ranges of their host.

When you change the ports of an existing cloud server, ports become static ports.