7MTT v2.0: Detailed description of configuration transition/manual steps: SnapMirror, NameServices, and WAFL

• Corrective action: Install SnapMirror license on the Data ONTAP 7-Mode storage system using the following command: license add <snapmirorr_license_code>You can get a get a free temporary SnapMirror license from NetApp.

Make sure that 7-Mode Data Copy and Multi-path IP addresses provided allows SnapMirror data copy.

• If a particular interface is specified for the option interface.blocked.snapmirror, all the IP addresses configured on such interfaces will block SnapMirror data copy.
• If the option interface.blocked.mgmt_data_traffic is enabled, all the IP addresses configured on the e0M interface will block SnapMirror data copy.

• Make sure that IP addresses specified for SnapMirror data copy are not configured on the interface which is specified in the option interface.blocked.snapmirror
• If IP addresses specified for SnapMirror data copy are configured on e0M, make sure that the option interface.blocked.mgmt_data_traffic is not enabled. It is not recommended to use IP addresses configured on e0M for SnapMirror data copy as e0M is a low bandwidth interface that should be configured for management traffic only.

The following steps must be taken on the Data ONTAP 7-Mode storage system:

• Set the Data ONTAP 7-Mode option snapmirror.enable to on by using the following command: options snapmirror.enable on
• If the Data ONTAP 7-Mode option snapmirror.access is set to none, then set the Data ONTAP 7-Mode option snapmirror.access to all by using the following command: options snapmirror.access all.

This allows any destination (any Data ONTAP 7-Mode storage system or clustered Data ONTAP) to establish SnapMirror relationships with this Data ONTAP 7-Mode storage system. So, be careful while setting this option to all.

• If the Data ONTAP 7-Mode option snapmirorr.access is set to legacy and if 7-Mode option snapmirror.checkip.enable is set to off, then add the target SVM name to the /etc/snapmirror.allow file of the Data ONTAP 7-Mode storage system.
• If the Data ONTAP 7-Mode option snapmirorr.access is set to legacy and if Data ONTAP 7-Mode option snapmirror.checkip.enable is set to on, then add at least one IC LIF IP address of each node that owns the transitioning clustered Data ONTAP volume to the /etc/snapmirror.allow file of the Data ONTAP 7-Mode storage system.
• If the Data ONTAP 7-Mode option snapmirorr.access is not set to legacy, then add at least one IC LIF IP address of each node that owns the transitioning clustered Data ONTAP volume to the Data ONTAP 7-Mode option snapmirror.access by using the following command: options snapmirror.access IC_LIP_IPs

The following steps must be taken on the clustered Data ONTAP storage system:

• Clustered Data ONTAP users IC LIFs for SnapMirror data transfers and with out these IC LIFs, 7-to-C SnapMirror data copy will fail. Create one or more intercluster LIFs on each of the node that owns the transitioning clustered Data ONTAP volumes by using the following command:
• network interface create -vserver <node_vserver> -lif <lif_name> -role intercluster -home-node <node> -home-port <node_port> -address <IP_address> -netmask <netmask>

• Make sure that the clustered Data ONTAP volumes are empty DP volumes
• The size of the clustered Data ONTAP volume must be at least as big as that of the Data ONTAP 7-Mode volumes.

• Create Transition Peering between the target SVM and Data ONTAP 7-Mode storage system by using the following CLI command: vserver peer transition create -local-vserver <target_svm> -src-filer-name <7_mode_data_copy_ip>

• Create required cron job: job schedule cron create -name <text> -month <cron month> -dayofweek <cron dayofweek> -day <cron dayofmonth> -hour <cron hour> -minute <cron minute>
• While creating C-to-C SnapMirror: snapmirror create -source-path <source-path> -destination-path <destination-path> -schedule <text> -throttle <integer> -type DP

• Applicable while transitioning while transitioning primary and secondary Data ONTAP 7-Mode volumes (volumes in SnapMirror relationships)
• Tool collects this information from the /etc/snapmirror.conf'file of the Data ONTAP 7-Mode storage system

The following SnapMirror schedule parameters not supported in clustered Data ONTAP:

• Wsize
• Restart
• Compression

• DNS transition is attempted only if  Data ONTAP7-Mode has one or more DNS domain names configured and dns is enabled on the Data ONTAP 7-Mode storage system. If DNS is disabled (dns.enable is off), then DNS transition is not attemped.
• General Restricitons

• NIS configuration is transition by 7MTT only if NIS is enabled on the Data ONTAP 7-Mode (nis.enable is on) and NIS servers have one or more IP addresses configured (other than just '*' ) and NIS Domain name is not empty.
• If nis.servers value is * (with no other IP addresses), then transition of NIS configuration will be ignored as NIS broadcast is not supported in clustered Data ONTAP.
• If nis.servers has one or more IP addresses along with (*), then (*) will be ignored and other IP addresses will be transitioned.

• 7-Mode LDAP Options for LDAP Schema Modify:</br>

ldap.nssmap.attribute.gecos</br> ldap.nssmap.attribute.gidNumber</br> ldap.nssmap.attribute.groupname</br> ldap.nssmap.attribute.homeDirectory</br> ldap.nssmap.attribute.loginShell</br> ldap.nssmap.attribute.memberNisNetgroup</br> ldap.nssmap.attribute.memberUid_Value</br> ldap.nssmap.attribute.netgroupname</br> ldap.nssmap.attribute.nisNetgroupTriple</br> ldap.nssmap.attribute.uid</br> ldap.nssmap.attribute.uidNumber</br> ldap.nssmap.attribute.userPassword</br> ldap.nssmap.objectClass.nisNetgroup</br> ldap.nssmap.objectClass.posixAccount</br> ldap.nssmap.objectClass.posixGroup</br> ldap.usermap.attribute.windowsaccount</br>
 

• 7-Mode LDAP Options for LDAP Client Create: </br>

ldap.ADdomain</br> ldap.base, ldap.base.group</br> ldap.base.netgroup</br> ldap.base.passwd</br> ldap.minimum_bind_level</br> ldap.name</br> ldap.port</br> ldap.servers</br> ldap.servers.preferred</br> ldap.timeout</br>

• cluster::> vserver context -vserver <target_vserver_name>
• LDAP Schema Copy & Modify
  • <target_vserver_name>::> set diag
  • <target_vserver_name>::*> vserver services ldap client schema copy -schema RFC-2307 -new-schema-name <new_schema_name>
  • <target_vserver_name>::*> vserver services ldap client schema modify -schema <new_schema_name> -gecos-attribute <7_Mode_Option_"ldap.nssmap.attribute.gecos"_Value> -gid-number-attribute <7_Mode_Option_"ldap.nssmap.attribute.gidNumber"_Value> -cn-group-attribute <7_Mode_Option_"ldap.nssmap.attribute.groupname"_Value> -home-directory-attribute <7_Mode_Option_"ldap.nssmap.attribute.homeDirectory"_Value> -login-shell-attribute <7_Mode_Option_"ldap.nssmap.attribute.loginShell"_Value> -member-nis-netgroup-attribute <7_Mode_Option_"ldap.nssmap.attribute.memberNisNetgroup"_Value> -member-uid-attribute <7_Mode_Option_"ldap.nssmap.attribute.memberUid"_Value> -cn-netgroup-attribute <7_Mode_Option_"ldap.nssmap.attribute.netgroupname"_Value> -nis-netgroup-triple-attribute <7_Mode_Option_"ldap.nssmap.attribute.nisNetgroupTriple"_Value> -uid-attribute <7_Mode_Option_"ldap.nssmap.attribute.uid"_value> -uid-number-attribute <7_Mode_Option_"ldap.nssmap.attribute.uidNumber"_Value> -user-password-attribute <7_Mode_Option_"ldap.nssmap.attribute.userPassword"_Value> -member-nis-netgroup-attribute <7_Mode_Option_"ldap.nssmap.objectClass.nisNetgroup"_Value> -posix-account-object-class <7_Mode_Option_"ldap.nssmap.objectClass.posixAccount"_Value> -posix-group-object-class <7_Mode_Option_"ldap.nssmap.objectClass.posixGroup"_Value> -windows-account-attribute <7_Mode_Option_"ldap.usermap.attribute.windowsaccount"_Value>
• LDAP Client Create
  • <target_vserver_name>::> vserver services ldap client create -client-config <LDAP_client_config_name> -schema <new_schema_name> -ad-domain <7_Mode_Option_"ldap.ADdomain"_Value> -bind-as-cifs-server true -base-dn <7_Mode_Option_"ldap.base"_Value> -group-dn <7_Mode_Option_"ldap.base.group"_Value> -netgroup-dn <7_Mode_Option_"dap.base.netgroup"_Value> -min-bind-level <7_Mode_Option_"ldap.minimum_bind_level"_Value> -bind-dn <7_Mode_Opton_"ldap.name"_Value> -tcp-port <7_Mode_Option_"ldap.port"_Value> -servers <7_Mode_Option_"ldap.servers"_Comma_Seperated_List> -preferred-ad-servers <7_Mode_Option_"ldap.servers.preferred"_Comma_Seperated_List> -query-timeout <7_Mode_Option_"ldap.timeout"_Value> -user-dn <7_Mode_Option_"ldap.base.passwd"_filter1_Value> -scope <7_Mode_Option_"ldap.base.passwd"_scope1_Value>
• LDAP Config Create
  • <target_vserver_name>::> vserver services ldap create -client-config <LDAP_client_config_name> -client-enabled true

• Use -bind-as-cifs-server true only if -ad_domain is set
• -ad-domain <7_Mode_Option_"ldap.ADdomain"_Value> and -servers <7_Mode_Option_"ldap.servers"_Comma_Seperated_Value> are mutually exclusive.
• Maximum value for -query-timeout <7_Mode_Option_"ldap.timeout"_Value> is 10. If the Data ONTAP 7-Mode option value is more than 10, set it to 10 for -query-timeout

• In Data ONTAP 8.2.x
  • vserver modify -vserver <vserver name> -ns-switch {nis|file|ldap},... nm-switch {file|ldap},...
• From Data ONTAP 8.3.x onwards
  • name-service ns-switch modify -vserver <vserver-name> -database <hosts|group|passwd|netgroup|namemap> -sources {file|nis|ldap

• In Data ONTAP 8.2.x
  • Clustered Data ONTAP has no facility to have different name-services order for passwd, group and netgroup databases. All of them are controlled by only one switch (ns-switch).
  • 7MTT transitions nsswitch configuration only if name-services order for passwd, group and netgroup databases is same in Data ONTAP 7-Mode (in /etc/nsswitch.conf file). If the order is different, this configuration is not transition.
• From Data ONTAP 8.3.x onwards
  • Separate service lookup order can be specified for each of the databases hosts, group, passwd, netgroup, namemap.
  • Tool collects the order of lookup for each of the group, netgroup, passwd from the /etc/nsswitch.conf and transitions the lookup order for each of them.

• vserver services unix-users create -vserver <vserver name> -user <text> -id <integer> -primary-gid <integer> -full-name <text>

• vserver services unix-group create -vserver <vserver name> -name <text> -id <integer>
• vserver services unix-group adduser -vserver <vserver name> -name <text> -username <text>

• vserver services netgroup load -vserver <target_svm_name> -source {(http|ftp) ://(hostname|IPv4 Address|IPv6 Address)...} - URI to load from

1. Data ONTAP 7-Mode can act as NIS Slave (by enabling Data ONTAP 7-Mode option nis.slave.enable). However, clustered Data ONTAP does not support this option.
2. More information can be found in KB article: What is Filer NIS slave on Data ONTAP?

• Data ONTAP 7-Mode supports NIS broadcast (nis.servers has *). However, clustered Data ONTAP does not support this feature.

• Local caching of NIS group files is supported in Data ONTAP 7-Mode (by enabling Data ONTAP 7-Mode option nis.group_update.enable). However, this feature is not supported in clustered Data ONTAP.

• Considering the domain names in search directives from the /etc/resolv.conf file while doing netgroup entry comparison is not supported in clustered Data ONTAP.

• Considering legacy SUNOS compatible nisdomainname in search directive for netgroup entry comparison is not supported in clustered Data ONTAP.

• The following DNS options are not supported in clustered Data ONTAP: sortlist, debug, ndots, no_tld_query, no-check-names, inet6
• These entries will be ignored during the transition

• Data ONTAP 7-Mode support Dynamic DNS updates (by enabling the Data ONTAP 7-Mode option dns.update.enable). However, dynamic DNS update is not supported in clustered Data ONTAP.

• Data ONTAP 7-Mode support DNS caching (by enabling the Data ONTAP 7-Mode option dns.cache.enable). However, DNS caching is not supported in clustered Data ONTAP.

• The following databases are not supported in clustered Data ONTAP: aliases, ethers, bootparams, networks, protocols, publickey, rpc, services, and shadow.
• These entries are ignored during the transition.

• The following database sources are not supported in clustered Data ONTAP: compact, cache
• These entries are ignored during the transition.

• Clustered Data ONTAP supports only 'file' (local SVM entries) and 'DNS' for host lookup and other database sources are not supported. Host lookup order in /etc/nsswitch.conf is ignored during the transition.

• Clustered Data ONTAP supports DNS only for host lookup and cannot be used for any other database lookup. If Data ONTAP 7-Mode has any database other than hosts configured with DNS database source, DNS source will be ignored during the transition and other sources are transitioned.

• Data ONTAP 7-Mode supports LDAP over SSL (by enabling option ldap.ssl.enable). However, clustered Data ONTAP 8.2.0 does not support LDAP over SSL and SASL is used whenever possible. LDAP over SSL is supported in clustered Data ONTAP 8.2.1 or later.
• 7MTT does not support the transition of LDAP over SSL to clustered Data ONTAP and LDAP over SSL must be manually enabled on the target SVM.

• volume quota policy create -vserver <vserver name> -policy-name <text>
• volume quota policy rule create -vserver <vserver name> -volume <volume name> -type {tree|user|group} -target <text> -qtree <qtree name> -user-mapping {on|off} -disk-limit {<size>|-} -file-limit {<integer>|-} -threshold {<size>|-} -soft-disk-limit {<size>|-} -soft-file-limit {<integer>|-}
• volume quota resize -vserver <vserver name> -volume <volume name>

• Create required cron jobs: job schedule cron create -name <text> -month <cron month> -dayofweek <cron dayofweek> -day <cron dayofmonth> -hour <cron hour> -minute <cron minute>
• Create snapshot policy: volume snapshot policy create -vserver <vserver name> -policy <policy name> -schedule1 <text> -count1 <integer> -schedule2 <text> -count2 <integer> -schedule3 <text> -count3 <integer> -schedule4 <text> -count4 <integer> -schedule5 <text> -count5 <integer>

• For Data ONTAP 8.2.x
  • volume modify -vserver <vserver name> -volume <volume name> -space-guarantee | -s {none|volume|file}
• For Data ONTAP 8.3.x
  • volume modify -vserver <vserver name> -volume <volume name> -space-guarantee | -s {none|volume}

• From Data ONTAP 8.3.x onwards, space-guarantee setting 'file' is deprecated. Tool transitions 'file' as 'volume' during the transition.

• node run -node <volume_hosting_node> -command vol options <volume_name> minra off

• Having the minra option enabled on the clustered Data ONTAP volumes has known performance issues. So, the  7-Mode Transition Tool disables this option on the target volumes during the transition.

• volume modify -vserver <vserver name> -volume <volume name> -filesys-size-fixed false

• volume modify -vserver <vserver name> -volume <volume name> -nvfail on

• volume mount -vserver <vsever-name> -volume <volume-name> -junction-path <junction_path>

• Junction path policy can be specified at SVM level. See 'Other Features' for more details. Valid values are preserve_7mode_mount_path, target_volume_name
• If the junction path that must be configured is already used in the clustered Data ONTAP, then 7MTT generates a new junction path (by appending _xxx) and informs customer about the new junction paths.
• The created junction paths are used while creating CIFS shares/NFS exports.

vFiler

with Root In Otree

• i2p is by default set to 'on' on the clustered Data ONTA volumes.
• i2p must be enabled on the Data ONTAP 7-Mode source volumes to proceed with the transition.

• 32-bit volumes or volumes with 32-bit Snapshots cannot be transitioned to clustered Data ONTAP 8.3.x. 32-bit volumes are not supported in Data ONTAP 8.3.x onwards.
• SnapMirror baseline copy operation will fail if Data ONTAP 7-Mode source volumes has 32-bit data (AFS or Snapshots).

• 32-bit Snapshots
  • Corrective Action: Delete all 32-bit Snapshot copies by using the following command: snap delete <volume_name> <32_bit_snapshot_name>
• 32-bit volumes in Data ONTAP 8.0.x or earlier releases
  • Corrective Action: You must upgrade your Data ONTAP 7-Mode system to Data ONTAP 8.1 or later, and complete an in-place-upgrade of the aggregates to 64-bit before retrying transition. For more information, see technical report TR-3978.
• 32-bit volumes in Data ONTAP 8.1.x or later releases
  • Corrective Action: You must upgrade the 32-bit volumes to 64-bit before transition. For more information, see technical report TR-3978.

• SnapValidator for Oracle (svo_enable) is not available on the clustered Data ONTAP. If a volume has svo_enable set to on, the 7-Mode Transition Tool will provide a warning about the nonavailability of this feature in clustered Data ONTAP.

• FlexClone hierarchy is lost during the transition and the FlexClone volumes are transitioned as FlexVol volume (as a part of 7-to-C SnapMirror copy). Storage efficiency and clone hierarchy is lost during this process.

• MetroCluster is not supported in clustered Data ONTAP. Tool provides a warning about the same if the Data ONTAP 7-Mode storage system is part of MetroCluster.

• If any of the qtrees have comma (,) in their names and if those qtrees are used as quota target in a quota rules, such rules cannot be transitioned to the clustered Data ONTAP because of a BUG in the clustered Data ONTAP. Tool provides warning about the same if it detects such scenarios.

• If any of the Data ONTAP 7-Mode volumes have deduplication or compression enabled, by default, the data transitioned from Data ONTAP 7-Mode will not be considered while deduplicating the new data written to the target clustered Data ONTAP volumes. This means that, if the new data written to the target volumes matches the existing data transitioned from Data ONTAP 7-Mode, the new data is not deduplicated. However, new data written to the target volumes will be considered for deduplication operations.

• Corrective Action: To enable the data transitioned from the Data ONTAP 7-Mode to be considered while deduplicating the new data written to the clustered Data ONTAP volumes, run the following command: volume efficiency start -vserver <svm_name> -volume <volume_name> -scan-old-data trueCluster performance might be impacted when this operation is running. Therefore, it is advised to run this command when the load on the system is less, such as during non-business hours.

• Non-Unicode directories on the transitioned volume will be converted to Unicode when needed (for example, when the directory is accessed using NFSv4 or CIFS). The conversion impacts performance of clustered Data ONTAP system temporarily.

• Corrective Action: Consider scheduling conversion of large directories to Unicode during non-business hours or a maintenance window. See the NetApp support library article on Converting existing directories to Unicode format for more information.