Merge pull request #1238 from NetAppDocs/aherbin-ontap-hotfix-may5

Aherbin ontap hotfix may5

_index.yml

@@ -114,7 +114,7 @@ indexpage:
           url: /data-protection-disaster-recovery/index.html
         - title: Archive and compliance using SnapLock technology
           url: /snaplock/index.html
-        - title: SnapMirror Business Continuity with System Manager
+        - title: SnapMirror Business Continuity
           url: /concept_san_smbc_overview.html
         - title: Manage MetroCluster sites with System Manager
           url: /concept_metrocluster_manage_nodes.html
@@ -132,11 +132,11 @@ indexpage:
           url: /performance-config/index.html
         - title: Performance management with the CLI
           url: /performance-admin/index.html
-        - title: File System Analytics overview
+        - title: File System Analytics
           url: /concept_nas_file_system_analytics_overview.html
         - title: EMS configuration
           url: /error-messages/index.html
-        - title: ONTAP 9.12.1 EMS Reference
+        - title: ONTAP EMS Reference
           url: https://docs.netapp.com/us-en/ontap-ems-9121/
     - title: More resources
       links:

mediator/manage-task.adoc

@@ -228,9 +228,9 @@ To manually install SCST, you need the SCST tar bundle that is used for the inst
 .. Determine each file name for "scst_vdisk", "scst", and "iscsi_scst" modules. 
 +
 ....
-`[root@localhost ~]# modinfo -n scst_vdisk`
-`[root@localhost ~]# modinfo -n scst`
-`[root@localhost ~]# modinfo -n iscst_scst_vdisk`
+[root@localhost ~]# modinfo -n scst_vdisk
+[root@localhost ~]# modinfo -n scst
+[root@localhost ~]# modinfo -n iscst_scst_vdisk
 ....
 
 .. Determine the kernel release.
@@ -293,5 +293,5 @@ If you are unable to reach this command, you might need to run the command using
 ....
 
 
-
+// 2023 May 04, Public PR 908
 // ontap-metrocluster issue #146, 7 march 2022

nas-audit/create-auditing-config-task.adoc

@@ -47,7 +47,7 @@ h| If you want to rotate audit logs by... h| Enter...
 a|
 Log size
 a|
-`vserver audit create -vserver vserver_name -destination path -events [{file-ops\|cifs-logon-logoff\|cap-staging\|file-share\|audit-policy-change\|user-account\|security-group\|authorization-policy-change}] [-format {xml\|evtx}] [-rotate-limit integer] [-rotate-size {integer[KB\|MB\|GB\|TB\|PB]}]`
+`vserver audit create -vserver vserver_name -destination path -events [{file-ops\|cifs-logon-logoff\|cap-staging\|file-share\|authorization-policy-change\|user-account\|security-group\|authorization-policy-change}] [-format {xml\|evtx}] [-rotate-limit integer] [-rotate-size {integer[KB\|MB\|GB\|TB\|PB]}]`
 a|
 A schedule
 a|
@@ -79,4 +79,5 @@ The following example creates an auditing configuration that audits file operati
 cluster1::> vserver audit create -vserver vs1 -destination /audit_log -events file-ops,cifs-logon-logoff,file-share,audit-policy-change,user-account,security-group,authorization-policy-change,cap-staging -rotate-schedule-month all -rotate-schedule-dayofweek all -rotate-schedule-hour 12 -rotate-schedule-minute 30 -rotate-limit 5
 ----
 
-// 4 Feb 2022, BURT 1451789 
+// 2023 May 4, Public PR 904
+// 2022 Feb 4, BURT 1451789 

nfs-config/add-rule-export-policy-task.adoc

@@ -194,7 +194,7 @@ The following commands create and verify the creation of an export rule on the S
 
 ----
 vs1::> vserver export-policy rule create -vserver vs1 -policyname exp1 -ruleindex 1 -protocol nfs
--clientmatch eng.company.com,@netgoup1 -rorule sys -rwrule sys -anon 65534 -superuser krb5
+-clientmatch .eng.company.com,@netgoup1 -rorule sys -rwrule sys -anon 65534 -superuser krb5
 
 vs1::> vserver export-policy rule show -policyname nfs_policy
 Virtual      Policy         Rule    Access    Client           RO
@@ -245,3 +245,6 @@ User ID To Which Anonymous Users Are Mapped: 65535
                Honor SetUID Bits in SETATTR: true
                   Allow Creation of Devices: true
 ----
+
+
+// 2023 May 4, Issue 898

software_setup/concept_decide_whether_to_use_ontap_cli.adoc

@@ -16,13 +16,4 @@ Beginning in ONTAP 9.13.1, on the A800 and FAS8700 platforms, you can use the ON
 If you are configuring a FlexArray on non-NetApp disks, you need to use the ONTAP CLI to configure root volumes on the array LUNs, and then use the Cluster Setup wizard to set up your cluster.
 For more information, see the link:https://docs.netapp.com/us-en/ontap-flexarray/install/concept_flexarray_virtualization_technology_overview_using_array_luns_for_storage.html[FlexArray Virtualization installation and requirements] documentation.
 
-.Before you begin
-
-* You should have installed, cabled and powered on your new storage system according to the installation and setup instructions for your platform model.
-See the https://docs.netapp.com/us-en/ontap-systems/index.html[AFF and FAS documentation].
-
-* Cluster network interfaces should be configured on each node of the cluster for intra-cluster communication.
-
-* If you are configuring IPv6 on your cluster, IPv6 should be configured on the Base Management Controller (BMC) so that you can access the system using SSH.
-
 // 2023 May 02, Jira 782

software_setup/task_create_the_cluster_on_the_first_node.adoc

@@ -18,6 +18,8 @@ See the https://docs.netapp.com/us-en/ontap-systems/index.html[AFF and FAS docum
 
 * Cluster network interfaces should be configured on each node of the cluster for intra-cluster communication.
 
+* If you are configuring IPv6 on your cluster, IPv6 should be configured on the Base Management Controller (BMC) so that you can access the system using SSH.
+
 .Steps
 
 . Power on all the nodes you are adding to the cluster. This is required to enable discovery for your cluster setup.

update/enable-automatic-updates-task.adoc

@@ -11,24 +11,17 @@ summary: 'Enabling automatic updates allows ONTAP to download and install firmwa
 [.lead]
 Beginning with ONTAP 9.10.1, you can enable automatic updates to allow ONTAP to download and install firmware updates without your intervention. 
 
-Beginning in ONTAP 9.13.1, these automatic updates also include Automatic Time Zone Database updates.
+Beginning in ONTAP 9.13.1, these automatic updates also include automatic Time Zone Database updates.
 
 .About this task
 To enable automatic updates, you must first enable AutoSupport with HTTPs.  If AutoSupport is not enabled on your cluster, or if AutoSupport is enabled on your cluster with another transport protocol, you will be given the option to enable it with HTTPs during this procedure.
 
-.Before you begin
-
-You must have one of the following entitlements:
-
-* AIQEXPERT
-* AIQADVISOR
-* AIQUPGRADE
-
 .Steps
 
 . In System Manager, click *Events*.
 . In the *Overview* section, next to *Enable automatic update*, click *Actions>Enable*.
 . If you do not have AutoSupport with HTTPs enabled, select to enable it.
 . Accept the terms and conditions and select *Save*.
 
+// 2023 May 04, Git Issue 905
 // 2023 May 03, Jira 752

update/firmware-task.adoc

@@ -83,9 +83,7 @@ If the update is already scheduled, you can *Edit* or *Cancel* it.
 --
 .ONTAP 9.8 and later without Active IQ
 
-. Navigate to the NetApp Support Site.
-
-. Log into the NetApp Support Site.
+. Navigate to the link:https://mysupport.netapp.com/site/downloads[NetApp Support Site] and log in.
 
 . Select the firmware package that you want to use to update your cluster firmware.
 

update/index.adoc

@@ -35,6 +35,6 @@ a|
 
 If you are running ONTAP 9.9.1 or earlier, or if you do not have link:enable-automatic-updates-task.html[automatic system updates] enabled, you can link:firmware-task.html[make firmware updates manually].
 
-If you are running ONTAP 9.12.1 or earlier, or if you do not have link:enable-automatic-updates-task.html[automatic system updates] enabled, you can update Time Zone Database manually.  See the Knowledge Base article, link:https://kb.netapp.com/Advice_and_Troubleshooting/Data_Storage_Software/ONTAP_OS/How_to_update_time_zone_information_in_ONTAP_9[How to update time zone information in ONTAP 9^], for details.
+If you are running ONTAP 9.12.1 or earlier, or if you do not have link:enable-automatic-updates-task.html[automatic system updates] enabled, you can update the Time Zone Database manually.  See the Knowledge Base article, link:https://kb.netapp.com/Advice_and_Troubleshooting/Data_Storage_Software/ONTAP_OS/How_to_update_time_zone_information_in_ONTAP_9[How to update time zone information in ONTAP 9^], for details.
 
 // 2023 May 03, Jira 752

upgrade/concept_upgrade_paths.adoc

@@ -29,7 +29,7 @@ You can always upgrade directly to the next adjacent ONTAP release family using
 +
 For example, you can use the direct update path from 9.8 to 9.9.1, or from 9.8 to 9.10.1.
 +
-*Note:* Beginning with ONTAP 9.11.1, software images support upgrading directly to releases that are three releases higher than the running release. For example, you can use the direct upgrade path from 9.8 to 9.11.1.
+*Note:* Beginning with ONTAP 9.11.1, software images support upgrading directly to releases that are three or more releases higher than the running release. For example, you can use the direct upgrade path from 9.8 to 9.11.1.
 
 *	_direct multi-hop_ +
 For some automated nondisruptive upgrades (ANDU) to non-adjacent releases, you can install the software image for an intermediate release as well the target release. The automated upgrade process uses the intermediate image in the background to complete the update to the target release.
@@ -534,16 +534,37 @@ MetroCluster IP configurations on these platforms, cannot upgrade from 9.8 direc
 [cols="25,25,50", options="header"]
 |===
 |If your current ONTAP release is… |And your target ONTAP release is… |Your manual upgrade path is…
+
+// 9.12.1 Manual
+|9.12.1
+|9.13.1
+|direct
+
+// 9.11.1 Manual
+.2+|9.11.1
+|9.13.1
+|direct
+
+|9.12.1
+|direct
+
 // 9.10.1 Manual
-.2+|9.10.1
+.3+|9.10.1
+
+|9.13.1
+|direct
+
 |9.12.1
 |direct
 
 |9.11.1
 |direct
 
 // 9.9.1 Manual
-.3+|9.9.1
+.4+|9.9.1
+|9.13.1
+|direct
+
 |9.12.1
 |direct
 
@@ -554,7 +575,12 @@ MetroCluster IP configurations on these platforms, cannot upgrade from 9.8 direc
 |direct
 
 // 9.8 Manual
-.4+|9.8
+.5+|9.8
+
+|9.13.1
+|multi-stage
+- 9.8 -> 9.12.1
+- 9.12.1 -> 9.13.1
 |9.12.1
 |direct
 
@@ -568,7 +594,14 @@ MetroCluster IP configurations on these platforms, cannot upgrade from 9.8 direc
 |direct
 
 // 9.7 Manual
-.5+|9.7
+.6+|9.7
+
+|9.13.1
+|multi-stage
+- 9.7 -> 9.9.1
+- 9.9.1 -> 9.12.1
+- 9.12.1 -> 9.13.1
+
 |9.12.1
 |multi-stage
 - 9.7 -> 9.9.1
@@ -591,7 +624,14 @@ MetroCluster IP configurations on these platforms, cannot upgrade from 9.8 direc
 |direct
 
 // 9.6 Manual
-.6+|9.6
+.7+|9.6
+
+|9.13.1
+|multi-stage
+- 9.6 -> 9.8
+- 9.8 -> 9.12.1
+- 9.12.1 -> 9.13.1
+
 |9.12.1
 |multi-stage
 - 9.6 -> 9.8
@@ -619,7 +659,15 @@ MetroCluster IP configurations on these platforms, cannot upgrade from 9.8 direc
 |direct
 
 // 9.5 Manual
-.7+|9.5
+.8+|9.5
+
+|9.13.1
+|multi-stage
+- 9.5 -> 9.7
+- 9.7 -> 9.9.1
+- 9.9.1 -> 9.12.1
+- 9.12.1 -> 9.13.1
+
 |9.12.1
 |multi-stage
 - 9.5 -> 9.7
@@ -655,7 +703,15 @@ MetroCluster IP configurations on these platforms, cannot upgrade from 9.8 direc
 |direct
 
 // 9.4 Manual
-.8+|9.4
+.9+|9.4
+
+|9.13.1
+|multi-stage
+- 9.4 -> 9.5
+- 9.5 -> 9.7
+- 9.7 -> 9.9.1
+- 9.12.1 -> 9.13.1
+
 |9.12.1
 |multi-stage
 - 9.4 -> 9.5
@@ -703,7 +759,16 @@ MetroCluster IP configurations on these platforms, cannot upgrade from 9.8 direc
 |direct
 
 // 9.3 Manual 
-.9+|9.3
+.10+|9.3
+
+|9.13.1
+|multi-stage
+- 9.3 -> 9.5
+- 9.5 -> 9.7
+- 9.7 -> 9.9.1
+- 9.9.1 -> 9.12.1
+- 9.12.1 -> 9.13.1
+
 |9.12.1
 |multi-stage
 - 9.3 -> 9.5
@@ -754,7 +819,17 @@ MetroCluster IP configurations on these platforms, cannot upgrade from 9.8 direc
 |not available
 
 // 9.2 Manual
-.10+|9.2
+.11+|9.2
+
+|9.13.1
+|multi-stage
+- 9.2 -> 9.3
+- 9.3 -> 9.5
+- 9.5 -> 9.7
+- 9.7 -> 9.9.1
+- 9.9.1 -> 9.12.1
+- 9.12.1 -> 9.13.1
+
 |9.12.1
 |multi-stage
 - 9.2 -> 9.3
@@ -817,7 +892,17 @@ MetroCluster IP configurations on these platforms, cannot upgrade from 9.8 direc
 |direct
 
 // 9.1 Manual
-.11+|9.1
+.12+|9.1
+
+|9.13.1
+|multi-stage
+- 9.1 -> 9.3
+- 9.3 -> 9.5
+- 9.5 -> 9.7
+- 9.7 -> 9.9.1
+- 9.9.1 -> 9.12.1
+- 9.12.1 -> 9.13.1
+
 |9.12.1
 |multi-stage
 - 9.1 -> 9.3
@@ -883,7 +968,18 @@ MetroCluster IP configurations on these platforms, cannot upgrade from 9.8 direc
 |not available
 
 // 9.0 Manual
-.12+|9.0
+.13+|9.0
+
+|9.13.1
+|multi-stage
+- 9.0 -> 9.1
+- 9.1 -> 9.3
+- 9.3 -> 9.5
+- 9.5 -> 9.7
+- 9.7 -> 9.9.1
+- 9.9.1 -> 9.12.1
+- 9.12.1 -> 9.13.1
+
 |9.12.1
 |multi-stage
 - 9.0 -> 9.1
@@ -977,6 +1073,7 @@ You must first upgrade to Data ONTAP 8.3.x, then upgrade to ONTAP 9.1, then upgr
 --
 ====
 
+// 2023 May 04, Issue 903
 // 2023, May 02, 9.13.1 paths
 // 2023 Apr 10, Issue 866
 // 2023 Feb 10, Issue 746