Configuring the cluster

Why you must configure your converted filers

You must configure some parameters, configuration files, and network interfaces, and all licenses in such a way that when one filer takes over the partner node, it appears as if it were the partner node; otherwise, the consequences described in the following table can result.

If...	Then...
Specific options or configuration files have different values	The values used in takeover are unpredictable.
A feature such as CIFS is licensed on one filer but not on the partner node	After a takeover, CIFS clients cannot access their files on the filer that has taken over from the failed filer.
Network interface configurations do not match	Users of the failed filer see broken network connections.

In general, the more similar the configuration of a filer is to that of its partner, the more it behaves like its partner in a takeover. This section describes the tasks you need to perform to ensure a smooth partner takeover.

For detailed information

See the following sections for detailed clustering configuration information: