3.6.1 HP PolyServe Matrix Server Administration Guide (T5392-96018, August 2008)

Chapter 4: Matrix Administration 19
• Certain Microsoft Knowledge Base articles caution that in the case of
Exchange SMTP, and possibly other applications, the use of the hosts
file can interfere with mail flow (see Microsoft Knowledge Base article
296215).
• Although using the hosts file provides immunity to DNS problems, it
must be manually updated on each node. For example, if an IP
address changes, all of the hosts files must be updated. Mismatches
between DNS and hosts files (such as typos or missing nodes) can lead
to confusing problems.
Network Changes
The following network changes should not be made while Matrix Server
is running. Attempting to do any of the following can adversely affect the
entire matrix. If you need to perform these actions on a particular server,
first stop Matrix Server on that server. Then make your change and restart
Matrix Server.
• Add or delete a network interface from the operating system.
• Change network properties on the Network Control Panel.
• Disable or re-enable a network interface via the Device Manager.
• Update network drivers.
• Hot-swapping of PCI cards.
Filesystems and SAN
• When fabric fencing is configured, do not enable or disable the
FibreChannel ports used by the matrix. Matrix Server must have
complete control over these ports to protect the integrity of the shared
filesystems on the SAN. Matrix Server will reenable a port if it detects
that the port has been disabled manually.
In addition, when fabric fencing is configured, do not change the
physical connection between a server and a FibreChannel switch
while Matrix Server is running on that server. Doing so may result in
filesystem corruption. For example, the connection must not be
moved from one switch port to another, and a new FibreChannel
connection for the server must not be established while Matrix Server
is running on the server.