How to Configure CIFS in 7-Mode Netapp DataOntap 8

This blog describes how we can enable CIFS configuration in 7-Mode Netapp.

To see the Video Version of the steps Click the link Below

login as: root
root@192.168.15.140's password:

netapp7mode1> cifs setup
This process will enable CIFS access to the filer from a Windows(R) system.
Use "?" for help at any prompt and Ctrl-C to exit without committing changes.

        Your filer does not have WINS configured and is visible only to
        clients on the same subnet.
Do you want to make the system visible via WINS? [n]:
        A filer can be configured for multiprotocol access, or as an NTFS-only
        filer. Since NFS, DAFS, VLD, FCP, and iSCSI are not licensed on this
        filer, we recommend that you configure this filer as an NTFS-only
        filer

(1) NTFS-only filer
(2) Multiprotocol filer

Selection (1-2)? [2]: 2
        The default name for this CIFS server is 'NETAPP7MODE1'.
Would you like to change this name? [n]: y
Enter the CIFS server name for the filer [NETAPP7MODE1]: netappcifs
        Data ONTAP CIFS services support four styles of user authentication.
        Choose the one from the list below that best suits your situation.

(1) Active Directory domain authentication (Active Directory domains only)
(2) Windows NT 4 domain authentication (Windows NT or Active Directory domains)
(3) Windows Workgroup authentication using the filer's local user accounts
(4) /etc/passwd and/or NIS/LDAP authentication

Selection (1-4)? [1]: 1
        In order to operate correctly within an Active Directory-based Windows
        domain, CIFS must use the DNS resolver service. That service is
        currently not configured on the filer. You must either configure DNS
        resolver services or choose a different authentication style.
Do you want to configure the filer's DNS resolver service? [y]: y
What is the filer's DNS domain name? []: nasadmin.local
What are the IPv4/IPv6 address(es) of your authoritative DNS name server(s)? []: 192.168.15.132
Would you like to specify additional DNS name servers? [n]:
What is the name of the Active Directory domain? [nasadmin.local]:
        In Active Directory-based domains, it is essential that the filer's
        time match the domain's internal time so that the Kerberos-based
        authentication system works correctly. If the time difference between
        the filer and the domain controllers is more than 5 minutes,
        authentication will fail. Time services are currently not configured
        on this filer.
Would you like to configure time services? [y]: y
        CIFS Setup will configure basic time services. To continue, you must
        specify one or more time servers. Specify values as a comma or space
        separated list of server names or IPv4 addresses. In Active
        Directory-based domains, you can also specify the fully qualified
        domain name of the domain being joined (for example:
        "NASADMIN.LOCAL"), and time services will use those domain controllers
        as time servers.
Enter the time server host(s) and/or address(es) [NASADMIN.LOCAL]: 192.168.15.132
Would you like to specify additional time servers? [n]:
1 entry was deleted.




        In order to create an Active Directory machine account for the filer,
        you must supply the name and password of a Windows account with
        sufficient privileges to add computers to the NASADMIN.LOCAL domain.
Enter the name of the Windows user [Administrator@NASADMIN.LOCAL]: administrator
Password for administrator:
CIFS - Logged in as administrator@NASADMIN.LOCAL.
        The user that you specified has permission to create the filer's
        machine account in several (2) containers. Please choose where you
        would like this account to be created.

(1) CN=computers
(2) OU=Domain Controllers
(3) None of the above

Selection (1-3)? [1]: 1
CIFS - Starting SMB protocol...
        Currently the user "NETAPPCIFS\administrator" and members of the group
        "NASADMIN\Domain Admins" have permission to administer CIFS on this
        filer. You may specify an additional user or group to be added to the
        filer's "BUILTIN\Administrators" group, thus giving them
        administrative privileges as well.
Would you like to specify a user or group that can administer CIFS? [n]:
Welcome to the NASADMIN.LOCAL (NASADMIN) Active Directory(R) domain.

CIFS local server is running.

How to expannd Aggr0 in Netapp 7 mode Data Ontap 8.2

These steps also applicable for any aggregate expansion in system.

1. To be on safer side back up all the /etc files to a different location. If any production volume hosted then    those also needs to be backed up.

2. To verify that appropriate spare disks are present to the system.
  Execute below commands
   netapp7mode1>aggr status -s
 Verify that enough number of spares Disk of same type, size, speed are there as of aggr0.

3.Execute below command to see just the result with option -n this command will not be executed rather
  it will display the disks that Data ONTAP would automatically select. Based on that you can decide
  whether to use suggested one or not.

  netapp7mode1> aggr add aggr0 -n -g rg0 2
        aggr add aggr0 -g rg0 -d v5.21 v5.20

  ----> where 2 is the number disk that you want to add.
4. If you decide to use the Data Ontap suggestion then just copy the output of above command and paste
it
    netapp7mode1> aggr add aggr0 -n -g rg0 2
        aggr add aggr0 -g rg0 -d v5.21 v5.20
    netapp7mode1> aggr add aggr0 -g rg0 -d v5.21 v5.20
            Fri Sep 19 16:28:05 GMT [netapp7mode1:raid.vol.disk.add.done:notice]: Addition of Disk /aggr0/plex0/rg0/v5.20 Shelf ? Bay ? [NETAPP   VD-1000MB-FZ-520 0042] S/N [08375604] to aggregate aggr0 has completed successfully
            Fri Sep 19 16:28:05 GMT [netapp7mode1:raid.vol.disk.add.done:notice]: Addition of Disk /aggr0/plex0/rg0/v5.21 Shelf ? Bay ? [NETAPP   VD-1000MB-FZ-520 0042] S/N [08375705] to aggregate aggr0 has completed successfully
            Addition of 2 disks to the aggregate has completed.