Configuring the DAFS service

ifconfig -a

A list of network devices, including the VI network interface names. These are the network device names that you recorded when you gathered the required DAFS configuration information.

dafs status -n

The state of the DAFS service and a list of all VI NICs that use the DAFS service and their current states.

dafs export list

A list of all DAFS exports with detailed information, including the exported filer paths.

options dafs

A list of current DAFS service settings, including the idle timeout value and whether the AUTH_NONE authentication is enabled.

Enter the following command to check if the DAFS service is running.

dafs status -n

Result

The filer console displays the status of the DAFS service and a list of VI NICs and their current states.

If...

Then...

The DAFS service is running

On the filer console, enter the following command:

dafs stop

Result

The DAFS service stops.

Proceed to Step 3.

The DAFS service is not running

Proceed to Step 3.

On the filer command line, enter the following command:

dafs setup

Note
Whenever you run dafs setup, all previous VI NIC and DAFS export settings are erased and you must reset them to configure your filer for the DAFS service. If you want to exit dafs setup and configure your filer later, press Ctrl-C.

Respond to the dafs setup command prompts using the information for your configuration.

Example

The following lines show example dafs setup command prompts:

filer> dafs setup

Configure DAFS access to the filer.

Configure network devices to use with DAFS.

  Enter a network device for DAFS, or 'q' when done: [q] e4

  Adding e4...

  Enter a network device for DAFS, or 'q' when done: [q] q

Configured DAFS attached devices.

Configure cluster partner network devices to use with DAFS.

  Partner network devices are used during cluster failover to maintain

  DAFS service. They may be the same as the primary DAFS device(s)

  or a dedicated subset of available devices.

  Enter a partner network device for DAFS, or 'q' when done: [q] q 

Configured DAFS attached partner devices.

Configure DAFS exports.

  Do you want to export all filer volumes through DAFS: [n] n 

        Enter a filer volume/path to export, or 'q' when done: [q] /vol/vol1

        Enter a filer volume/path to export, or 'q' when done: [q] q 

Do you want privileged clients to require authentication: [y] y 

Enter idle timeout for sessions, or 0 to disable timeout: [7200] 7200

Enabling DAFS services...

Fri Nov  1 14:46:39 GMT [filer: dafs.server.startOk:info]: DAFS service started

Fri Nov  1 14:46:39 GMT [filer: dafs.server.attachNic:info]: DAFS service 
attaching e4

You are changing option dafs.auth_none.enable which applies to both members of 
the cluster in takeover mode.

This value must be the same in both cluster members prior to any takeover or 
giveback, or that next takeover/giveback may not work correctly Fri Nov  1 
14:46:39 GMT [filer: reg.options.cf.change:warning]: Option dafs.au

filer> 

Result

The dafs setup command enables and starts the DAFS service and attaches VI NICs to the service. The value of options dafs.enable is set to on. No reboot is required.

After you complete dafs setup and the DAFS service is enabled, verify that DAFS service is running and all known VI NICs are attached by entering the following command on the filer console:

dafs status -n

Result

The display shows the state of the DAFS service and a list of all VI NICs that use the DAFS service and their current states.

Example

filer> dafs status -n

DAFS service is started

NIC: e4      Device: e4       State: ATTACHED

NIC: p_e4    	 Device: e4       	 State: INACTIVE PARTNER

NIC: e5      Device: e5       State: ATTACHED

In these examples, the dafs setup command created the partner network interface p_e4 for cluster failover. The partner devices are attached, but remain in the inactive partner state until a takeover occurs.