This
workflow automates the replacement of a source highly available [HA] pair on a
cluster with a new HA pair along with disk shelves. This involves replacing HA
pair controller and attached disk shelves. The data volumes located on the
source HA pair will be moved to the destination HA pair in a non-disruptive
manner using the volume move feature within Data ONTAP. Once the data volumes have
been moved (evacuated) from the source HA pair, the NAS and cluster management
network interfaces will be moved to destination HA pair. The source HA
pair will be removed from the storage cluster.
The
following pre-requisites should be met before executing the workflow:
1. Install
the new HA pair nodes and add it to the cluster.
2. Please
ensure that the maximum cluster size limits are not exceeded. Refer Data
ONTAP System Administration Guide for Cluster Administrators for information
about cluster limits on non-SAN environments. For SAN environments, see the
Data ONTAP SAN Configuration Guide for Clustered ONTAP.
3. Configure
the new nodes as a HA-pair.
4. Install
all necessary licenses on the new HA-pair.
5. Ensure
that the network ports on new HA pair are configured properly. Identify the
network ports to be used for data network interfaces and cluster-management
interfaces. Ensure that the ports are connected to the appropriate networks.
6. For
SAN logical interfaces:
·
Create matching SAN logical interfaces
on the new HA pair for each SAN logical interface on the old HA pair.
·
Ensure that SAN logical interfaces
on the destination are members of appropriate portsets.
·
If required, modify the iSCSI and
FCP initiators to add the newly defined SAN logical interfaces.
7. For
SAN environments: The workflow pauses at an approval point.
·
If the cluster is in SAN
environment, the user should manually modify FCP and iSCSI initiators to remove
the logical interfaces from old HA pair nodes.
·
Once the SAN logical interfaces are
ready for removal, the user can approve the workflow. And the workflow
execution will resume. The SAN interfaces will get deleted inside the workflow.
8. Create
data aggregates on the new HA pair nodes. Each destination node should have
data aggregates big enough to host the volumes from the corresponding source
node. The workflow will allow customized mapping of source aggregates to
destination aggregates
9. If
there are pure SSD based aggregates present, it is recommended to use custom
aggregate mapping. Otherwise volumes from non SSD aggregates may get mapped to
SSD aggregates.
10. Make
sure that the cluster is added to OCUM (OnCommand Unified Manager) server and
the cluster and the new controllers are discovered by the OCUM server.
11. Make
sure that the OCUM server is added to the WFA server and cache acquisition is
complete with the new HA pair details.
12. Add
the cluster credentials to WFA server.
13. If
your clusters are running Data ONTAP 8.3.0, ensure that your port mapping is of
the same IPspace and broadcast domain.
14. Note:
This workflow does not support “Tech refresh” case where there are 7-mode
volumes.
Use
custom port mapping?*[Mandatory]: Enable this option to specify whether
customization is required for mapping between source node data ports and
destination node data ports.
First
Source Node* [Mandatory]: Provide the first source node of the old HA pair.
Query should result in a tabular list displaying node name, platform, serial
number, and data ports.
Second
Source Node*[Mandatory]: Provide the second source node of the old HA pair.
Query should result in a tabular list displaying node name, platform, serial
number, and data ports.
First
Destination Node*[Mandatory]: Provide the first destination node of the new HA pair.
The query will display only the HA nodes from given Cluster excluding the
selected source HA-pair. The tabular list will display the qualified list of
node name, platform, serial number, and data ports for selection.
Second
Destination Node*[Mandatory]: Provide the second destination node of the new HA
pair. The query will display only the partner node of the first destination
node. The tabular list will display the qualified list of node name, platform,
serial number, and data ports for selection.
Mapping
between first nodes: Specifies the mapping between aggregates from first source
node to aggregates from first destination node. Volumes from the given source
aggregate will be migrated to the given destination aggregate.
Each
mapping consists of one source node aggregate name and one destination node
aggregate name. While calling the workflow through web-services, provide a
comma separated list of mappings. Example for the list:
<SourceAggregate1>~<DestinationAggregate1>
<SourceAggregate2>~<DestinationAggregate2>
<SourceAggregate3>~<DestinationAggregate2>
Mapping
between second nodes: Specifies the mapping between aggregates from second
source node to the aggregates from second destination node. Volumes from the
given source aggregate will be migrated to the given destination aggregate.
Each
mapping consists of one source node aggregate name and one destination node
aggregate name. While calling the workflow through web-services, provide a
comma separated list of mappings. Example for the list:
<SourceAggregate1>~<DestinationAggregate1>
<SourceAggregate2>~<DestinationAggregate2>
<SourceAggregate3>~<DestinationAggregate2>
Mapping
between first nodes: Specifies the mapping between ports from first source node
to ports from first destination node. Network logical interface from the given source
port will be migrated to the given destination port.
Each
mapping consists of one source node port name and one destination node port
name. While calling the workflow through web-services, provide a comma
separated list of mappings.
Example
for the list:
<SourcePort1>~<DestinationPort1>
<SourcePort2>~<DestinationPort2>
<SourcePort3>~<DestinationPort2>
Mapping
between second nodes: Specifies the mapping between ports from second source
node to ports from second destination node. Network logical interface from the
given source port will be migrated to the given destination port.
Each
mapping consists of one source node port name and one destination node port
name. While calling the workflow through web-services, provide a comma
separated list of mappings.
Example
for the list:
<SourcePort1>~<DestinationPort1>
<SourcePort2>~<DestinationPort2>
<SourcePort3>~<DestinationPort2>
This
workflow will migrate the source node HA pair to destination node new HA pair.
As part of the migration, all data volumes are migrated to destination HA pair
using the volume move feature and also related LIFs are migrated in a
non-disruptive manner.