Table of Contents

Multiprotocol Server Configuration workflow

The Multiprotocol Server Configuration workflow enables you to set up CIFS and NFS services on an SVM, in preparation for configuring client access to files contained on the SVM.

As part of the workflow, an export rule is created in the default export policy for read-only access.

The following sections provide details about the workflow and how to execute the workflow:

Prerequisites for executing the Multiprotocol Server Configuration workflow

You must ensure that certain requirements are met before executing the workflow. You must be a cluster administrator for executing this workflow.

  • Your system must be running clustered Data ONTAP.
    Note: This workflow is qualified to work with Data ONTAP 8.2.1 and later.
  • OnCommand Workflow Automation (WFA) 3.0 must be installed.
  • You must have added OnCommand Unified Manager 6.1 or later as a data source in WFA and obtained the latest Unified Manager data.
  • The cluster must already be created and the cluster time must be synchronized with an NTP server.
  • CIFS and NFS licenses must be enabled.
  • Name services must be provided by NIS or UNIX local users and not by LDAP or Kerberos.
  • You must have added the WFA credentials for the Active Directory (AD) domain from the Credentials window.

    For the AD domain, you must provide the following input parameters:

    Input parameters Values
    Match Exact
    Type Other
    Name/IP FQDN name
    User name Domain administrator name
    Password Domain administrator password

What happens when you execute the Multiprotocol Server Configuration workflow

The Multiprotocol Server Configuration workflow enables you to create an aggregate, an SVM, a data LIF, and map UNIX and Window names.

The following illustration displays the tasks involved in executing the workflow:

Image displays tasks performed in the Multiprotocol Server Configuration workflow.

Executing the Multiprotocol Server Configuration workflow

Executing the Multiprotocol Server Configuration workflow enables you to set up CIFS and NFS services on an SVM, in preparation for configuring SMB and NFSv3 client access to files contained on the SVM.

Before you begin

You must have reviewed the requirements for executing the workflow.

About this task

You should have the following input parameters available for executing the workflow:

  • Cluster name
  • If you want to create a new aggregate:
    • Node name
    • Aggregate name
    • Aggregate RAID type
    • Number of disks to create the aggregate
  • For creating the SVM:
    • SVM name
    • Language
    • IPspace name
    • DNS domain names
    • DNS servers
  • NIS domain name and IP addresses of NIS servers
  • Logical interface (LIF) details:
    • LIF name
    • Address
    • Network mask
    • Home port
    • Route gateway
    • Failover group
  • CIFS details:
    • Server name
    • Domain name
    • Share name
  • Export rule details: client match for Read-write access
  • UNIX to Windows and Windows to UNIX name mapping details:
    • Position of the new mapping
    • Pattern to be matched
    • Replacement pattern

Steps

  1. Log in to WFA by providing the necessary credentials.
  2. Click Portal > Setup > Multiprotocol Server Configuration.
    Tip: You can use the filter () to locate the workflow.
  3. Click the Execute icon ().
    The Execute Workflow 'Multiprotocol Server Configuration' dialog box is displayed.
  4. Select the cluster name.
  5. Specify whether you want to create name mapping by selecting the Name Mapping check box.
  6. Provide the aggregate details:
    If you are... Do this…
    Using an existing aggregate Select an appropriate aggregate from the drop-down list.
    Creating a new aggregate

    Enter the following values:

    • Node name
    • Aggregate name
    • RAID type
    • Disk count
  7. Create the SVM by providing details such as the SVM name, language, IPspace name, DNS domain names, and DNS servers.
    Note: The IPspace name is valid only for clusters running Data ONTAP 8.3 and later.
  8. Provide NIS details such as NIS domain name and the IP addresses of the NIS servers.
  9. Provide LIF details such as the LIF name, address, home port, network mask address, route gateway, and failover group.
  10. Specify the export rule details by providing the client match IP.
    Two export rules are created with the following configurations:
    • Rule index 1
      • RO=any
      • RW=any
      • Superuser=any
      • anon=0
      • Protocol=any
      • Client match=IP address
    • Rule index 2
      • RO=any
      • RW=never
      • Superuser=none
      • anon=65534
      • Protocol=any
      • Client match=0.0.0.0/0
  11. Provide UNIX to Windows name mapping details such as the position, UNIX-Windows pattern, and replacement pattern.
    Example
    The following example shows UNIX to Windows mapping in the ENG domain:
    Position 2
    UNIX-Windows pattern (.+)
    UNIX-Windows replacement ENG\\\1
  12. Provide Windows to UNIX name mapping details such as the position, Windows-UNIX pattern, and replacement pattern.
    Example
    The following example shows Windows to UNIX mapping in the ENG domain:
    Position 1
    Windows-UNIX pattern ENG\\(.+)
    Windows-UNIX replacement \1
  13. Optional: Click Preview to validate your workflow before executing it.
  14. Click Execute.
    You can also schedule the workflow for execution at a later date and time by selecting the Choose date and time for execution check box.

After you finish

You must create a data volume and provide access to the clients by executing the Multiprotocol File Access Workflow.

Copyright © 1994-2014, NetApp, Inc. All rights reserved.
March 2014