4.1.0 HP PolyServe Matrix Server administration guide (T5392-96073, October 2010)

If it cannot use that network, the PanPulse process on the new server will look for
another network that all of the servers can use. If this attempt fails, the new server
will attempt to communicate with the other servers over the main interface (the
hostname interface) if possible; however, it may drop out of the cluster.
Network topology
The cluster should have a symmetrical network configuration; each server should be
connected to the same set of networks. This topology helps to ensure that the
administrative network can fail over to another network and maintain communications
with all servers in the cluster.
If the network topology is asymmetric, where networks are connected to only some
of the servers, it may not be possible to fail over the administrative network to another
network because the new network might not reach all of the servers in the cluster.
Virtual hosts
A virtual host is created on a set of network interfaces. These network interfaces must
be enabled for virtual hosting. By default, all network interfaces are enabled; however,
you can disable a network interface if you do not want it to carry virtual host traffic.
Network interfaces and the Management Console
When Matrix Server is started, the ClusterPulse process probes the servers in the
cluster to locate network interfaces and then adds the interfaces to its configuration
file. The Servers window on the Management Console shows the network interfaces
for each server as defined in this file. (Because there can be stale information in the
configuration file, the Servers window may not match your current network
configuration exactly.)
Each network interface is labeled either Hosting Enabled or Hosting Disabled,
which indicates whether it can be used for virtual hosts.
Configure network interfaces66