Ontap hotfix

data-protection/snapmirror-svm-replication-workflow-concept.adoc

@@ -11,11 +11,18 @@ summary: "SnapMirror SVM replication involves creating the destination SVM, crea
 [.lead]
 SnapMirror SVM replication involves creating the destination SVM, creating a replication job schedule, and creating and initializing a SnapMirror relationship.
 
-[NOTE]
-====
-This workflow assumes that you are already using a default policy or a custom replication policy.
-====
+You should determine which replication workflow best suits your needs:
 
-image::../media/svm-data-protection-workflow.gif[SnapMirror SVM replication workflow]
+* link:https://docs.netapp.com/us-en/ontap/data-protection/replicate-entire-svm-config-task.html[Replicate an entire SVM configuration]
+* link:https://docs.netapp.com/us-en/ontap/data-protection/exclude-lifs-svm-replication-task.html[Exclude LIFs and related network settings from SVM replication]
+* link:https://docs.netapp.com/us-en/ontap/data-protection/exclude-network-name-service-svm-replication-task.html[Exlude network, name service, and other settings from SVM configuration]
 
+//[NOTE]
+//====
+//This workflow assumes that you are already using a default policy or a custom replication policy.
+//====
+
+// image::../media/svm-data-protection-workflow.gif[SnapMirror SVM replication workflow]
+
+// 2024-Mar-19, ONTAPDOC-1750
 // 2023 Nov 10, Jira 1466

manage-nodes-sm-task.adoc

@@ -80,11 +80,11 @@ When you reboot or shutdown a node, its HA partner automatically executes a take
 
 . Select *Cluster > Overview*.
 . Under *Nodes*, select image:icon_kabob.gif[menu icon].
-. Select the node and select *Shut down*, *Reboot*, or *Edit Service Processor*.
+. Select the node and then select *Shut down*, *Reboot*, or *Edit Service Processor*.
 +
 If a node has been rebooted and is waiting for giveback, the *Giveback* option is also available.
 +
-If you select *Edit Service Processor* you can choose *Manual* to input the IP address, subnet mask and gateway, or you can choose *DHCP* for dynamic host configuration.
+If you select *Edit Service Processor*, you can choose *Manual* to input the IP address, subnet mask and gateway, or you can choose *DHCP* for dynamic host configuration.
 
 == Rename nodes
 

network-management/sidebar.yml

@@ -30,90 +30,94 @@ entries:
         url: /networking/worksheet_for_nas_path_failover_configuration_auto.html
  - title: NAS path failover workflow (ONTAP 9.7 and earlier)
    entries:
-     - title: Overview (ONTAP 9.7 and earlier)
-       url: /networking/set_up_nas_path_failover_9_to_97_cli.html
-     - title: Workflow (ONTAP 9.7 and earlier)
-       url: /networking/workflow__nas_path_failover_overview_manual.html
-     - title: Worksheet (ONTAP 9.7 and earlier)
-       url: /networking/worksheet_for_nas_path_failover_configuration_manual.html
+      - title: Overview (ONTAP 9.7 and earlier)
+        url: /networking/set_up_nas_path_failover_9_to_97_cli.html
+      - title: Workflow (ONTAP 9.7 and earlier)
+        url: /networking/workflow__nas_path_failover_overview_manual.html
+      - title: Worksheet (ONTAP 9.7 and earlier)
+        url: /networking/worksheet_for_nas_path_failover_configuration_manual.html
  - title: Network ports
    entries:
-    - title: Overview
-      url: /networking/configure_network_ports_@cluster_administrators_only@_overview.html
-    - title: Configure network ports
-      entries:
-      - title: Modify network port attributes
-        url: /networking/modify_network_port_attributes.html
-      - title: Convert 40GbE NIC ports into multiple 10GbE ports for 10GbE connectivity
-        url: /networking/convert_40gbe_nic_ports_into_multiple_10gbe_ports_for_10gbe_connectivity.html
-      - title: Removing a NIC from the node (ONTAP 9.8 or later)
-        url: /networking/removing_a_nic_from_the_node.html
-      - title: Removing a NIC from the node (ONTAP 9.7 or earlier)
-        url: /networking/remove_a_nic_from_the_node_97.html
-    - title: Monitor network ports
-      entries:
-      - title: Monitor the health of network ports
-        url: /networking/monitor_the_health_of_network_ports.html
-      - title: Monitor the reachability of network ports (ONTAP 9.8 and later)
-        url: /networking/monitor_the_reachability_of_network_ports.html
-      - title: ONTAP port usage on a storage system
-        url: /networking/ontap_port_usage_on_a_storage_system_overview.html
-      - title: ONTAP internal TCP and UDP ports
-        url: /networking/ontap_internal_ports.html
+      - title: Overview
+        url: /networking/configure_network_ports_@cluster_administrators_only@_overview.html
+      - title: Configure network ports
+        entries:
+        - title: Combine physical ports to create interface groups
+          url: /networking/combine_physical_ports_to_create_interface_groups.html
+        - title: Configure VLANs over physical ports
+          url: /networking/configure_vlans_over_physical_ports.html
+        - title: Modify network port attributes
+          url: /networking/modify_network_port_attributes.html
+        - title: Convert 40GbE NIC ports into multiple 10GbE ports for 10GbE connectivity
+          url: /networking/convert_40gbe_nic_ports_into_multiple_10gbe_ports_for_10gbe_connectivity.html
+        - title: Removing a NIC from the node (ONTAP 9.8 or later)
+          url: /networking/removing_a_nic_from_the_node.html
+        - title: Removing a NIC from the node (ONTAP 9.7 or earlier)
+          url: /networking/remove_a_nic_from_the_node_97.html
+        - title: Monitor network ports
+          entries:
+          - title: Monitor the health of network ports
+            url: /networking/monitor_the_health_of_network_ports.html
+          - title: Monitor the reachability of network ports (ONTAP 9.8 and later)
+            url: /networking/monitor_the_reachability_of_network_ports.html
+          - title: ONTAP port usage on a storage system
+            url: /networking/ontap_port_usage_on_a_storage_system_overview.html
+          - title: ONTAP internal TCP and UDP ports
+            url: /networking/ontap_internal_ports.html
  - title: IPspaces
    entries:
-    - title: Overview
-      url: /networking/configure_ipspaces_@cluster_administrators_only@_overview.html
-    - title: Create IPspaces
-      url: /networking/create_ipspaces.html
-    - title: Display IPspaces
-      url: /networking/display_ipspaces.html
-    - title: Delete an IPspace
-      url: /networking/delete_an_ipspace.html
+      - title: Overview
+        url: /networking/configure_ipspaces_@cluster_administrators_only@_overview.html
+      - title: Create IPspaces
+        url: /networking/create_ipspaces.html
+      - title: Display IPspaces
+        url: /networking/display_ipspaces.html
+      - title: Delete an IPspace
+        url: /networking/delete_an_ipspace.html
  - title: Broadcast domains
    entries:
     - title: Broadcast domain (ONTAP 9.8 and later)
       entries:
-       - title: Overview (ONTAP 9.8 and later)
-         url: /networking/configure_broadcast_domains_@cluster_administrators_only@_overview.html
-       - title: Create broadcast domains (ONTAP 9.8 and later)
-         url: /networking/add_broadcast_domain.html
-       - title: Add or remove ports (ONTAP 9.8 and later)
-         url: /networking/add_or_remove_ports_from_a_broadcast_domain.html
-       - title: Repair port reachability (ONTAP 9.8 and later)
-         url: /networking/move_broadcast_domains.html
-       - title: Move broadcast domains into IPspaces (ONTAP 9.8 and later)
-         url: /networking/move_broadcast_domains.html
-       - title: Split broadcast domains (ONTAP 9.8 and later)
-         url: /networking/split_broadcast_domains.html
-       - title: Merge broadcast domains (ONTAP 9.8 and later)
-         url: /networking/merge_broadcast_domains.html
-       - title: Change the MTU value for ports in a broadcast domain (ONTAP 9.8 and later)
-         url: /networking/change_the_mtu_value_for_ports_in_a_broadcast_domain.html
-       - title: Display broadcast domains (ONTAP 9.8 and later)
-         url: /networking/display_broadcast_domains.html
-       - title: Delete a broadcast domain
-         url: /networking/delete_a_broadcast_domain.html
+        - title: Overview (ONTAP 9.8 and later)
+          url: /networking/configure_broadcast_domains_@cluster_administrators_only@_overview.html
+        - title: Create broadcast domains (ONTAP 9.8 and later)
+          url: /networking/add_broadcast_domain.html
+        - title: Add or remove ports (ONTAP 9.8 and later)
+          url: /networking/add_or_remove_ports_from_a_broadcast_domain.html
+        - title: Repair port reachability (ONTAP 9.8 and later)
+          url: /networking/move_broadcast_domains.html
+        - title: Move broadcast domains into IPspaces (ONTAP 9.8 and later)
+          url: /networking/move_broadcast_domains.html
+        - title: Split broadcast domains (ONTAP 9.8 and later)
+          url: /networking/split_broadcast_domains.html
+        - title: Merge broadcast domains (ONTAP 9.8 and later)
+          url: /networking/merge_broadcast_domains.html
+        - title: Change the MTU value for ports in a broadcast domain (ONTAP 9.8 and later)
+          url: /networking/change_the_mtu_value_for_ports_in_a_broadcast_domain.html
+        - title: Display broadcast domains (ONTAP 9.8 and later)
+          url: /networking/display_broadcast_domains.html
+        - title: Delete a broadcast domain
+          url: /networking/delete_a_broadcast_domain.html
     - title: Broadcast domain (ONTAP 9.7 and earlier)
       entries:
-       - title: Overview (ONTAP 9.7 and earlier)
-         url: /networking/configure_broadcast_domains_97_overview.html
-       - title: Determine ports (ONTAP 9.7 and earlier)
-         url: /networking/determine_which_ports_can_be_used_for_a_broadcast_domains.html
-       - title: Create broadcast domains (ONTAP 9.7 and earlier)
-         url: /networking/create_a_broadcast_domain97.html
-       - title: Add or remove ports from a broadcast domain (ONTAP 9.7 and earlier)
-         url: /networking/add_or_remove_ports_from_a_broadcast_domain97.html
-       - title: Split broadcast domains (ONTAP 9.7 and earlier)
-         url: /networking/split_broadcast_domains97.html
-       - title: Merge broadcast domains (ONTAP 9.7 and earlier)
-         url: /networking/merge_broadcast_domains97.html
-       - title: Change the MTU value for ports in a broadcast domain (ONTAP 9.7 and earlier)
-         url: /networking/change_the_mtu_value_for_ports_in_a_broadcast_domain97.html
-       - title: Display broadcast domains
-         url: /networking/display_broadcast_domains97.html
-       - title: Delete a broadcast domain
-         url: /networking/delete_a_broadcast_domain.html
+        - title: Overview (ONTAP 9.7 and earlier)
+          url: /networking/configure_broadcast_domains_97_overview.html
+        - title: Determine ports (ONTAP 9.7 and earlier)
+          url: /networking/determine_which_ports_can_be_used_for_a_broadcast_domains.html
+        - title: Create broadcast domains (ONTAP 9.7 and earlier)
+          url: /networking/create_a_broadcast_domain97.html
+        - title: Add or remove ports from a broadcast domain (ONTAP 9.7 and earlier)
+          url: /networking/add_or_remove_ports_from_a_broadcast_domain97.html
+        - title: Split broadcast domains (ONTAP 9.7 and earlier)
+          url: /networking/split_broadcast_domains97.html
+        - title: Merge broadcast domains (ONTAP 9.7 and earlier)
+          url: /networking/merge_broadcast_domains97.html
+        - title: Change the MTU value for ports in a broadcast domain (ONTAP 9.7 and earlier)
+          url: /networking/change_the_mtu_value_for_ports_in_a_broadcast_domain97.html
+        - title: Display broadcast domains
+          url: /networking/display_broadcast_domains97.html
+        - title: Delete a broadcast domain
+          url: /networking/delete_a_broadcast_domain.html
  - title: Failover groups and policies
    entries:
     - title: Failover overview

peering/prerequisites-cluster-peering-reference.adoc

@@ -71,11 +71,11 @@ The default `intercluster` firewall policy allows access through the HTTPS proto
 == Cluster requirement
 
 Clusters must meet the following requirement:
-GH-1152
-* A cluster cannot be in a peer relationship with more than 255 clusters.
+
+ * A cluster cannot be in a peer relationship with more than 255 clusters.
 
 // 8 and 15-DEC-2023, ONTAP GH-1152 
 // 2023 July 27, ontap-issues-991
 // 12 July 2023, ontap-issues-980
 // 2023 Jan 10, Jira ONTAPDOC-716
-//ontap-issue #115 01/17/2022
+// ontap-issue #115 01/17/2022

project.yml

@@ -35,4 +35,4 @@ sidebar:
 product-family: 
   name: ONTAP
   repo: ontap-family
-  sidebar_label: All ONTAP product documentation
+

redirect/automatic-host-side-space-management-concept.adoc

@@ -0,0 +1,4 @@
+---
+permalink: san-admin/automatic-host-side-space-management-concept.html
+redirect: ontap/san-admin/enable-space-allocation-scsi-thin-provisioned-luns-task.html
+---

redirect/host-support-scsi-thin-provisioning-reference.adoc

@@ -0,0 +1,4 @@
+---
+permalink: san-admin/host-support-scsi-thin-provisioning-reference.html
+redirect: ontap/san-admin/host-support-scsi-thin-provisioning-reference.html
+---

redirect/lifs-cluster-concept.adoc

@@ -0,0 +1,4 @@
+---
+permalink: san-admin/lifs-cluster-concept.html
+redirect: ontap/san-admin/manage-lifs-all-san-protocols-concept.html
+---

redirect/simplified-host-management-snapcenter-concept.adoc

@@ -0,0 +1,4 @@
+---
+permalink: san-admin/simplified-host-management-snapcenter-concept.html
+redirect: ontap/san-admin/host-side-management-concept.html
+---

s3-config/create-svm-s3-task.adoc

@@ -66,7 +66,7 @@ If it is not, contact your sales representative.
 +
 [source,cli]
 ----
-vserver create -vserver _svm_name_ -subtype default -rootvolume _root_volume_name_ -aggregate _aggregate_name_ -rootvolume-security-style unix -language C.UTF-8 -data-services _data-s3-server_ -ipspace _ipspace_name_
+vserver create -vserver <svm_name> -subtype default -rootvolume <root_volume_name> -aggregate <aggregate_name> -rootvolume-security-style unix -language C.UTF-8 -data-services <data-s3-server> -ipspace <ipspace_name>
 ----
 
 ** Use the UNIX setting for the `-rootvolume-security-style` option.
@@ -77,7 +77,7 @@ vserver create -vserver _svm_name_ -subtype default -rootvolume _root_volume_nam
 +
 [source, cli]
 ----
-vserver show -vserver _svm_name_
+vserver show -vserver <svm_name>
 ----
 +
 The `Vserver Operational State` field must display the `running` state. If it displays the `initializing` state, it means that some intermediate operation such as root volume creation failed, and you must delete the SVM and re-create it.

s3-config/ontap-s3-interoperability-concept.adoc

@@ -29,19 +29,19 @@ a|
 * link:ontap-s3-supported-actions-reference.html#bucket-operations[Object versioning]  (beginning with ONTAP 9.11.1)
 * link:../s3-snapmirror/index.html[S3 SnapMirror] (beginning with ONTAP 9.10.1)
 * MetroCluster IP configurations (beginning with ONTAP 9.12.1)
+* SnapLock (beginning with ONTAP 9.14.1)
+* WORM (beginning with ONTAP 9.14.1)
 
 a|
 
 * Erasure coding
 * Information lifecycle management
 * NDMP
 * SMTape
-* SnapLock
 * SnapMirror Cloud
 * SVM disaster recovery
 * SyncMirror
 * User-created Snapshot copies
-* WORM
 
 a|
 Encryption
@@ -99,6 +99,7 @@ a|
 
 |===
 
+// 2024-Mar-20, issue# 1293
 // 2022 Dec 14, ontapdoc-700
 // 2022 Nov 09, EPIC 657
 // 2022 Oct 05, BURT 1506539

san-admin/enable-space-allocation-scsi-thin-provisioned-luns-task.adoc

@@ -9,11 +9,29 @@ summary: "If you set the space-allocation option to enabled, ONTAP notifies the
 :imagesdir: ../media/
 
 [.lead]
-If you set the `space-allocation` option to `enabled`, ONTAP notifies the host when the volume has run out of space and the LUN in the volume cannot accept writes. This option also enables ONTAP to reclaim space automatically when your host deletes data.
+If your host supports SCSI thin provisioning, you can enable space allocation for SCSI thinly provisioned LUNs in ONTAP.  When space allocation is enabled, ONTAP notifies the host when the volume has run out of space and the LUN in the volume cannot accept writes. ONTAP also automatically reclaims space when your host deletes data.
+
+On hosts that do not support SCSI thin provisioning, when the volume containing LUN runs out of space and cannot automatically grow, ONTAP takes the LUN offline. On hosts that support SCSI thin provisioning, ONTAP does not take the LUN offline when it runs out of space. The LUN remains online in read-only mode and the host is notified that the LUN can no longer accept writes.
+
+Also, when data is deleted on a host that supports SCSI thin provisioning, host-side space management identifies the blocks of deleted data on the host file system and automatically issues one or more `SCSI UNMAP` commands to free corresponding blocks on the storage system.
+
+.Before you begin
+
+To enable space allocation, SCSI thin provisioning must be supported by your host. SCSI thin provisioning uses logical block provisioning as defined in the SCSI SBC-3 standard. Only hosts that support this standard can use SCSI thin provisioning in ONTAP.
+
+The following hosts currently support SCSI thin provisioning when you enable space allocation:
+
+* Citrix XenServer 6.5 & later
+* ESXi 5.0 & later
+* Oracle Linux 6.2 UEK kernel or later
+* RHEL 6.2 & later
+* SLES11 & later
+* Solaris 11.1 & later
+* Windows 
 
 .About this task
 
-The `space-allocation` option is set to `disabled` by default, and you must take the LUN offline to enable space allocation. After you enable space allocation, you must perform discovery on the host before the host will recognize that space allocation has been enabled.
+By default, space allocation is disabled for all LUNs. You must take the LUN offline to enable space allocation; then you must perform discovery on the host before the host will recognize that space allocation has been enabled.
 
 .Steps
 
@@ -27,7 +45,6 @@ lun modify -vserver vserver_name -volume volume_name -lun lun_name -state offlin
 . Enable space allocation:
 +
 [source,cli]
-+
 ----
 lun modify -vserver _vserver_name_ -volume _volume_name_ -lun _lun_name_ -space-allocation enabled
 ----
@@ -42,11 +59,14 @@ lun show -vserver _vserver_name_ -volume _volume_name_ -lun _lun_name_ -fields s
 . Bring the LUN online:
 +
 [source,cli]
-+
 ----
 lun modify -vserver _vserver_name_ -volume _volume_name_ -lun _lun_name_ -state online
 ----
 
 . On the host, rescan all disks to ensure that the change to the `-space-allocation` option is correctly discovered.
 
-//2022 Nov 4, Git Issue 689
+// 2023, Mar 18, Jira 1793
+// 2023 Nov 15, Jira 1446
+// 2023 Nov 08, Git Issue 1139
+// 2023 Oct 30, Git Issue 1139
+// 2022 Nov 4, Git Issue 689