Skip to main content

Deciding where to provision the new volume

Before you create a new multiprotocol volume, you must decide whether to place the volume in an existing storage virtual machine (SVM), and, if so, how much configuration the SVM requires. This decision determines your workflow.

  • If you want to provision a volume on a new SVM, create a basic SVM.

    Creating a basic SVM

    You must choose this option if CIFS and NFS are not already enabled on an existing SVM.

  • If you want to provision a volume on an existing SVM that has both CIFS and NFS enabled but not configured, add CIFS and NFS access on the existing SVM.

    Adding CIFS and NFS access to an existing SVM

    You should choose this option if you created the SVM for SAN access by using the relevant Express Guide.
  • If you want to provision a volume on an existing SVM that is fully configured for CIFS and NFS multiprotocol access, you can directly create and configure the volume.

    Creating and configuring a volume
  • Creating a basic SVM
    You can use a wizard that guides you through the process of creating a new storage virtual machine (SVM), configuring Domain Name System (DNS), creating a data logical interface (LIF), configuring a CIFS server, enabling NFS, and optionally configuring NIS.
  • Adding CIFS and NFS access to an existing SVM
    Adding both CIFS/SMB and NFS access to an existing SVM involves creating a data LIF, configuring a CIFS server, enabling NFS, and optionally configuring NIS.
  • Opening the export policy of the SVM root volume (Creating a new NFS-enabled SVM)
    You must add a rule to the default export policy to allow all clients access through NFSv3. Without such a rule, all NFS clients are denied access to the storage virtual machine (SVM) and its volumes.
  • Mapping the SMB server on the DNS server
    Your site's DNS server must have an entry pointing the SMB server name, and any NetBIOS aliases, to the IP address of the data LIF so that Windows users can map a drive to the SMB server name.
  • Configuring LDAP (Creating a new NFS-enabled SVM)
    If you want the storage virtual machine (SVM) to get user information from Active Directory-based Lightweight Directory Access Protocol (LDAP), you must create an LDAP client, enable it for the SVM, and give LDAP priority over other sources of user information.
  • Mapping UNIX and Windows user names
    If your site has both Windows and UNIX user accounts, you should use name mapping to ensure that Windows users can access files with UNIX file permissions and to ensure that UNIX users can access files with NTFS file permissions. Name mapping can involve any combination of implicit mapping, conversion rules, and default users.