3.1.2 Matrix Server Administration Guide

Chapter 19: Other Matrix Maintenance 260
Copyright © 1999-2006 PolyServe, Inc. All rights reserved.
service or device to fail periodically and you do not want to take the
failover action for a single probe failure. Putting a script like this in place
essentially implements a “two consecutive probe-script failure” probe.
Matrix Server Network Port Numbers
Matrix Server uses a set of network ports for external connections, such as
connections from the Management Console and the mx utility. It also uses
a different set of network ports for internal, or server-to-server
communications. The external ports numbers are fixed, and cannot be
changed. Most of the internal port numbers can be changed if there is a
conflict with system port numbers.
External Network Port Numbers
The following port numbers are used for external connections to Matrix
Server. If Matrix Server is behind a firewall, it may be necessary to change
the firewall rules to allow traffic for these ports.
Internal Network Port Numbers
The following network port numbers are used for internal, server-to-
server communication. You should need to change the firewall rules for
these ports only if you have Matrix Server nodes firewalled from each
other. Although these port numbers should not conflict with any
registered service, they can easily be reconfigured as described below.
Port
Transport
type Description
9050 TCP Proprietary connection from the Management
Console (configurable, as described below)
9070 TCP HTTP connection from the Management Console
(fixed, IANA registration has been applied for)
9071 TCP HTTPS connection from the Management Console
(fixed, IANA registration has been applied for)