Attaching and detaching network devices

About attaching and detaching network devices

When the dafs setup command starts the DAFS service, it attaches the DAFS service to configured VI NICs. You can also add newly configured VI NICs or remove VI NICs while the DAFS service is running.

To attach and detach VI NICs for the DAFS services, you use the dafs attach and dafs detach commands. The command syntax and functions are as follows:

The dafs attach vinic command attaches the DAFS service to the specified VI NIC. This command can also designate a failover VI NIC as a partner interface for a clustered pair of filers. For more information on clusters, see the Storage Management Guide.
The dafs detach vinic command detaches the DAFS service from the specified vinic.

Attaching a device needs to be done only once. The DAFS service remembers which NICs are attached and automatically attaches itself to the same set of NICs on the next system reboot or dafs start command. An attached NIC can be in an inactive state. This typically applies to CFO partner devices that are attached but remain inactive until a CFO takeover occurs.

You can also add newly configured VI NICs or remove VI NICs while the DAFS service is running with the dafs attach or dafs detach commands.

For more information, see the man page na_dafs(1).

Attaching the DAFS service to VI NICs

To attach the DAFS service to a specific VI NIC, complete the following step.

Step	Action
1	At the filer command line, enter the following command: dafs attach vinic [-d physical_device] [-l listen_address][-p] vinic specifies the logical interface name of the VI NIC to be attached to the DAFS service. `-d` physical_device specifies the physical device name of the VI NIC. This name depends upon the specific hardware installed in your filer. The logical vinic interface name and the physical device name can be the same. If the physical device name is not specified, then by default the physical device name is the same as the logical vinic interface name. `-l` listen_address is the VI net address and discriminator where the DAFS server listens for requests. This is an advanced option and NetApp suggests that you use the defaults for this option. See Default options for the dafs attach command. `-p` indicates that the VI NIC is attached as a partner interface for cluster failover (CFO). Result The DAFS service is attached to the specified VI NIC. Example: filer> dafs attach e4 filer> In this example, the local interface e4 is attached to the DAFS service. The logical name e4 is the same as the physical device name and it is unnecessary to specify the `-d` option. Example for failover VI NIC as a partner interface filer> dafs attach pe4 -d e4 -p filer> In this example, the CFO partner interface pe4 is attached to the DAFS service. The logical name of the CFO partner VI NIC is pe4, and the physical device is e4. The `-p` option causes pe4 to be attached as a CFO partner interface.

Step

Action

At the filer command line, enter the following command:

dafs attach vinic [-d physical_device]

[-l listen_address][-p]

vinic specifies the logical interface name of the VI NIC to be attached to the DAFS service.

-d physical_device specifies the physical device name of the VI NIC. This name depends upon the specific hardware installed in your filer. The logical vinic interface name and the physical device name can be the same. If the physical device name is not specified, then by default the physical device name is the same as the logical vinic interface name.

-l listen_address is the VI net address and discriminator where the DAFS server listens for requests. This is an advanced option and NetApp suggests that you use the defaults for this option. See Default options for the dafs attach command.

-p indicates that the VI NIC is attached as a partner interface for cluster failover (CFO).

Result

The DAFS service is attached to the specified VI NIC.

Example:

filer> dafs attach e4

filer>

In this example, the local interface e4 is attached to the DAFS service. The logical name e4 is the same as the physical device name and it is unnecessary to specify the -d option.

Example for failover VI NIC as a partner interface

filer> dafs attach pe4 -d e4 -p

filer>

In this example, the CFO partner interface pe4 is attached to the DAFS service. The logical name of the CFO partner VI NIC is pe4, and the physical device is e4. The -p option causes pe4 to be attached as a CFO partner interface.

Default options for the dafs attach command

The following defaults are applied if you do not specify options for the dafs attach command:

If the device (-d) option is not specified, then by default the physical device name is the same as the logical vinic interface name
If the listen address (-l) option is not specified, the following defaults are used:
- For the local interface, the default consists of the VI net address of the VI NIC, followed by a colon ":" and the discriminator called "DAFS." An example is "-l 10.20.29.184:DAFS."
- For the CFO partner interface indicated with the -p option, the default consists of the VI net address of the VI NIC, followed by a colon ":" and the discriminator called "pDAF." An example is
  "-l 10.20.29.184:pDAF."

Detaching VI NICs from the DAFS service

To detach the DAFS service from a specific VI NIC, complete the following step.

Step	Action
1	At the filer command line, enter the following command: dafs detach vinic vinic specifies the logical name of the VI NIC to be detached from the DAFS service. Example The DAFS service is detatched from the specified VI NIC: `filer> dafs detach e4` filer> dafs detach pe4 filer> In this example, the local interface e4 and the partner interface pe4 are detached from the DAFS service.

Step

Action

At the filer command line, enter the following command:

dafs detach vinic

vinic specifies the logical name of the VI NIC to be detached from the DAFS service.

Example

The DAFS service is detatched from the specified VI NIC:

filer> dafs detach e4

filer> dafs detach pe4

filer>

In this example, the local interface e4 and the partner interface pe4 are detached from the DAFS service.