Enabling cluster failover in a DAFS configuration

Enabling failover paths on the filer

Using the dafs attach command

After you configure failover addresses in the /etc/hosts file on the DAFS client, you must use the dafs attach command on the filer to define a failover VI NIC as a partner interface. You can also create partner interfaces during the dafs setup command.

For more information about the dafs setup command and the dafs attach command, see the DAFS chapter of the File Access Management Guide.

To enable failover paths on the filer, complete the following steps.

Step	Action
1	On the filer command line, enter the following command: `dafs attach` vinic `-d` physical_device `-p` vinic is the logical partner interface name of the VI NIC to be attached to the DAFS service on the filer. Use the eN naming convention, where N is the number of the NIC. `-d` physical_device is the physical device name of the VI NIC. If the physical device is not specified, then by default the physical device name is the same as the logical vinic name. `-p` indicates that the vinic is attached as a partner interface. The partner devices are attached, but remain in the inactive partner state until a CFO takeover occurs. Example filer> dafs attach pe4 -d e4 -p filer>
2	After attaching the partner devices, you can verify the status of all known VI NICs by entering the following command on the filer command line: 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: pe4 Device: e4 State: INACTIVE PARTNER NIC: e5 Device: e5 State: ATTACHED In the examples, the partner devices pvf5 and pe4 are attached, but remain in the inactive partner state until a CFO takeover occurs.

Step

Action

On the filer command line, enter the following command:

dafs attach vinic -d physical_device -p

vinic is the logical partner interface name of the VI NIC to be attached to the DAFS service on the filer. Use the eN naming convention, where N is the number of the NIC.

-d physical_device is the physical device name of the VI NIC. If the physical device is not specified, then by default the physical device name is the same as the logical vinic name.

-p indicates that the vinic is attached as a partner interface. The partner devices are attached, but remain in the inactive partner state until a CFO takeover occurs.

Example

filer> dafs attach pe4 -d e4 -p

filer>

After attaching the partner devices, you can verify the status of all known VI NICs by entering the following command on the filer command line:

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: pe4       	 Device: e4        	 State: INACTIVE PARTNER

NIC: e5        Device: e5        State: ATTACHED

In the examples, the partner devices pvf5 and pe4 are attached, but remain in the inactive partner state until a CFO takeover occurs.