Stopping and starting vFilers

Reasons to stop a vFiler

You stop a vFiler if you need to troubleshoot vFiler problems or destroy a vFiler.

Note
You cannot stop or start vFiler0.

After you stop a vFiler, the vFiler can no longer receive packets from clients.

The stopped state is not persistent across reboots: after you reboot the filer, the vFiler resumes automatically.

You can start vFilers that are in the stopped state; after a vFiler starts, it is in running state and can receive packets from clients.

If iSCSI is licensed on the filer, starting or stopping a vFiler starts or stops iSCSI packet processing for that vFiler.

To stop vFilers, complete the following step.

Step	Action
1	Enter the following command: vfiler stop vfilertemplate Example The filer supports two vFilers named vFiler1 and vFiler2. The following command stops all vFilers, except vFiler 0: vfiler stop * The following messages appear after you enter the command: vfiler1 stopped vfiler2 stopped

Step

Action

Enter the following command:

vfiler stop vfilertemplate

The filer supports two vFilers named vFiler1 and vFiler2. The following command stops all vFilers, except vFiler 0:

vfiler stop *

The following messages appear after you enter the command:

vfiler1         stopped

vfiler2         stopped

To start vFilers, complete the following step.

Step	Action
1	Enter the following command: vfiler start vfilertemplate Example The filer supports two vFilers named vFiler1 and vFiler2. The following command starts all vFilers, except vFiler 0, which is already running: vfiler start * The following messages appear after you enter the command: vfiler1 running vfiler2 running

Step

Action

Enter the following command:

vfiler start vfilertemplate

The filer supports two vFilers named vFiler1 and vFiler2. The following command starts all vFilers, except vFiler 0, which is already running:

vfiler start *

The following messages appear after you enter the command:

vfiler1         running

vfiler2         running