Allowing or disallowing protocols for vFilers

Protocols that vFilers can use

By default, vFilers can use the protocols that are licensed for the hosting filer. For example, if the hosting filer is licensed for CIFS and NFS, the vFilers created can also use the CIFS and NFS protocols. You can select those protocols that you allow or disallow on the vFilers.

Allowing and disallowing CIFS, NFS, or iSCSI

You can select the protocols that you allow on the vFilers using the vfiler allow command. You can select the protocols that you disallow on the vFilers using the vfiler disallow command. vFilers support the following protocols:

CIFS
NFS
rsh
iSCSI

To allow the CIFS, NFS, or both protocols on a vFiler, the CIFS, NFS, or both protocols must have an active license on the hosting filer.

Effects of disallowing CIFS, NFS, or iSCSI

If the CIFS, NFS, or iSCSI protocol is running and you disallow it, the protocol remains running until the filer reboots, but packets destined for the vFiler are ignored.

Effects of disallowing iSCSI

When iSCSI is disallowed on a vFiler, the following conditions apply on that vFiler:

You cannot start iSCSI (the iscsi start command is rejected).
No new iSCSI sessions are allowed.
iSCSI commands on existing sessions are rejected.

Effects of disallowing rsh

After you disallow rsh, attempts to connect to the vFiler using rsh fail, regardless of the rsh.enable option setting.

After you allow rsh again, you can connect to the vFiler using rsh if the rsh.enable option is On.

Allowing or disallowing rsh has no effect on the rsh.enable option, and you can turn the rsh.enable option on or off regardless of whether rsh is allowed.