3.5.1 Matrix Server Administration Guide

Chapter 4: Configure Network Interfaces 60

Administrative Network Failover

An administrative network failure occurs when the interface on a

particular server is no longer receiving Matrix Server administrative

traffic. Some possible causes of the failure are a bad cable or network

interface card (NIC).

When the administrative network fails on a server, the PanPulse daemon

on that server attempts to select another network to act as the

administrative network. A message regarding the network failure also

appears in the matrix.log file.

When the PanPulse daemon locates another network that all servers in

the matrix can access, all of the servers fail over the administrative

network to that network. The daemon looks for another network in this

order:

• Networks that allow administrative traffic.

• Networks that discourage administrative traffic.

If Matrix Server must use a network that was configured to discourage

administrative traffic, it will fail over to a network that allows the traffic

as soon as that network becomes available to all servers in the matrix.

If multiple interface failures occur on a server and there is not another

network available for the administrative network, the server may drop

out of the matrix. The remaining servers will continue to use the existing

administrative network.

Making Network Changes

When making network changes, you should be aware of the following:

• You should not add or delete an active network interface device from

the operating system while Matrix Server is running. Attempting to

do this can adversely affect the entire matrix. If you need to add or

delete an active network interface on a particular server, first stop

Matrix Server on that server. Then make your administrative change

and start Matrix Server.

• An active network interface should not be modified or taken down via

the operating system while Matrix Server is running. Attempting to