Verifying configuration for clustered filers

Values need to match

When you configure your clustered filers, the following configuration information needs to match.

Configuration files
Licenses
Options
Parameters
Network interfaces
Note
The values for domain controllers and WINS servers no longer need to be identical on both filers in a cluster. You can have each filer in a cluster exist in a different domain and/or workgroup from its partner. However, if you have a multiprotocol environment and use UID to SID mapping, the UNIX security information must be compatible between the two domains. For example, if you have a UID of 119, it must map to the same NT account for both partners.

After you have configured both filers, use the following tables to ensure that both filers have the same values in their configuration.

Configuration file matching

Use the following table to indicate you verified that the contents of the configuration files in the root volume of the filer (not the UNIX administration host) are identical for both filers.

File	Filer 1	Filer 2
/etc/resolv.conf
/etc/httpd.mimetypes
/etc/dgateways
/etc/nsswitch.conf

License matching

Use the following table to record the codes for each of the licenses for both filers in the cluster to ensure that licenses have identical values in both filers.

Feature	Filer 1 license code	Filer 2 license code
nfs
cifs
http
cluster
snapmirror
snaprestore
snapmanagerexchange
dafs
syncmirror
vfiler
vld
sms
snapvault_client
snapvault_server
fcp
iscsi

Option matching

Use the following table to compare the output of the options command for both filers in the cluster to ensure that the options have identical values in both filers.

Option	Filer 1	Filer 2
`cf.timed.enable`
`cifs.show_snapshot`
Note The following option is required when the FCP license is enabled and the service is running. `cf.takeover.on_panic (ON)` Note You do not need to set this option manually on Filer 2; it will automatically be set to the value of Filer 1.
Note The following option is required when the FCP license is enabled and the service is running. `coredump.timeout.enable (ON)`
Note The following option is required when the FCP license is enabled and the service is running. `coredump.timeout.seconds (60)`
`dns.domainname`
`dns.enable`
`http.admin.enable`
`httpd.timeout`
`httpd.timewait.enable`
`ip.path_mtu_discovery.enable`
`nfs.per_client_stats.enable`
`nfs.v2.df.2gb.lim`
`nfs.v3.enable`
`nis.domainname`
`nis.enable`
`pcnfsd.enable`
`raid.reconstruct_speed`
`raid.timeout`
`snmp.enable`
`telnet.enable`
`timed.enable`
`timed.log`
`timed.max_skew`
`time.min_skew`
`timed.proto`
`timed.sched`
`timed.servers`
`trusted.hosts`
`vol.copy.throttle`
`wafl.maxdirsize`
`wafl.root_only_chown`

Parameter matching

Use the following table to compare the parameters for both filers in the cluster to ensure that the parameters have identical values in both filers.

Parameter	Filer 1	Filer 2
ARP table
date
ndmp
nfs
route table
routed
timezone

Network interface matching

The network interfaces must have identical values on both filers in a cluster.