The Mirage system and clients use default communication ports. Make sure that the correct ports and protocols are selected for the system.

The Mirage Management server and Mirage servers use external communications to communicate with the Mirage clients or the Mirage Management console, and internal communications to communicate with each other.

Table 1. Ports and Protocols for Mirage Components

Component

Communications

Port

Protocol

Notes

Mirage service

External

8000

TCP/IP or SSL/TLS

The only port required for communications between Mirage clients and servers.

Note:

SSL/TLS is optional and can be enabled. See Install an SSL Server Certificate for the Mirage Server.

Mirage Branch Reflector

External

8001

TCP/IP

Used for communication between the branch reflector and the local peers at the remote site.

Mirage Management service

External

8443 , 1443

TCP/IP

Used for communication between the Mirage Management console and the Mirage Management service. SOAP Message-level Security is applied.

Mirage Server service

Internal

135, 445

TCP/IP

Used for control communication between the Mirage Management service and the Mirage server.

Note:

You can limit access to this port to incoming connections from the Mirage Management service host.

File portal

Internal

6080, 6443

TCP/IP

Used to access the file portal.

Mirage Web Management

Internal

7080, 7443

TCP/IP

Used to access the Web Management.

Mirage Gateway server

Internal

8000

TCP/IP

Used for communication between the Mirage Gateway server and the Mirage server.

Note:

The port must have DNS update access.

Internal

389, 636

TCP/IP

LDAP or LDAPS

Used for communications between the Mirage Gateway server and the LDAP servers.

Internal

8080 /8443

TCP/IP

Used for communications between the Mirage Gateway server and the Mirage Management server.

Used for the Mirage Gateway Web console.

External

8000

TLS/SSL

Used for communication between the Mirage client and the Mirage Gateway server.

Internal

8093

TCP/IP

Used for communication for Mirage Gateway authentication service.

Mirage API

Internal

7443

HTTPS

MongoDB File Database

Internal

27017, 27018

TCP/IP

Used to communicate with the MongoDB nodes located on each Mirage server and Mirage Management server.