Netapp Cluster For NDMP

Transitioning to a two-node switchless cluster
If you have an existing two-node cluster that uses cluster network switches, you can apply the switchless-cluster networking
option and replace the switches with direct, back-to-back connections between the nodes. This is a non-disruptive operation.
The procedure you use depends on whether you have two dedicated cluster-network ports on each controller (as required on
most systems) or a single cluster port on each controller (a supported option on FAS22xx storage systems).
Choices
• Transitioning to a two-node switchless cluster (systems with redundant cluster-network connections) on page 1
• Transitioning to a two-node switchless cluster (FAS22xx systems with a single cluster-network connection) on page 11
• Transitioning to a two-node switchless cluster (systems with four redundant cluster-network connections) on page 14
Transitioning to a two-node switchless cluster (systems with redundant

cluster-network connections)
If you have an existing two-node cluster that uses cluster network switches, you can apply the switchless-cluster networking
option and replace the switches with direct, back-to-back connections between the nodes. This is a nondisruptive operation.
Before you begin
• The cluster must be healthy and consist of two nodes connected by cluster switches, and the nodes must be running Data
ONTAP 8.2 or later.
The switchless cluster feature cannot be used with more than two nodes.
• Each storage system must have two dedicated cluster ports providing redundant cluster-network connections.
This is the supported configuration for most storage systems. FAS22xx systems support an optional configuration using a
single cluster-network connection due to the limited number of ports.
• Command output examples in this section are from Data ONTAP 8.2.x, which differ from the command output in Data
ONTAP 8.3 and later.
See Transitioning to a two-node switchless cluster (systems with four redundant cluster-network connections) on page 14
for example command output for Data ONTAP 8.3 and later.
About this task

This procedure removes the cluster switches in a two-node cluster and replaces each connection to the switch with a direct
connection to the partner node.
215-07834_D0 November 2014 Copyright © 2014 NetApp, Inc. All rights reserved. 1
Web: www.netapp.com • Feedback: doccomments@netapp.com
Steps
1. Identify the cluster LIFs on the cluster ports:

network interface show -role cluster
Example
This example and the others in this procedure show systems that are using e0a and e0b as cluster ports. Your system might
be using different cluster ports due to its particular requirements.
node1::> network interface show -role cluster
Logical Status Network Current Current Is

Vserver Interface Admin/Oper Address/Mask Node Port Home
----------- ---------- ---------- ------------------ ------------- ------- ----
node1
clus1 up/up 192.168.177.121/24 node1 e0a true
clus2 up/up 192.168.177.122/24 node1 e0b true
node2
4 entries were displayed.
2. Disable the –auto-revert parameter on each of the cluster LIFs on the cluster ports on both nodes:
network interface modify -vserver vserver-name -lif lif_name -auto-revert false
This enables you to then move the LIFs temporarily so that you can remove the cable connections from the switches.
Example
The following illustration shows a simplified view of the two nodes, node1 and node2:
• Each node uses ports e0a and e0b for the cluster connections.
• Each port has a cluster LIF (one with the defined role of cluster) associated with it.
• Each node is configured with a Storage Virtual Machine (SVM, formerly known as Vserver), node1 and node2.
• For the sake of simplicity, only one cluster switch is shown, ClusterSwitch1.
2 Transitioning to a two-node switchless cluster

The following steps in this example show auto-revert being disabled on the LIFs:
a. Disable –auto-revert on the LIF clus1 on node1:

network interface modify –vserver node1 -lif clus1 –auto-revert false
b. Disable–auto-revert on the LIF clus2 on node1:

network interface modify -vserver node1 -lif clus2 -auto-revert false
c. Disable –auto-revert on the LIF clus1 on node2:

d. Disable –auto-revert on the LIF clus2 on node2:

3. Select one of the cluster ports on the first node, and then migrate the interfaces from that port to the other cluster port on the
same node:
network interface migrate –vserver vserver-name -lif lif_name –dest-node destination-node-
name –dest-port port-name
Example
The following illustration and command shows the migration of cluster LIFs from port e0a on node1 to port e0b:
network interface migrate –vserver node1 -lif clus1 –dest-node node1 –dest-port e0b
The LIF is now associated with port e0b:
4. Confirm that the LIF has been migrated:

Transitioning to a two-node switchless cluster (systems with redundant cluster-network connections) 3

Example

----------- ---------- ---------- ------------------ ------------- ------- ----
node1
clus1 up/up 192.168.177.121/24 node1 e0b false
node2
5. On the second node, select the corresponding cluster port, and then migrate interfaces from that port to another cluster port
on the same node:
network interface migrate –vserver vserver-name -lif lif_name –dest-node destination-node-
name –dest-port port_name
Example

----------- ---------- ---------- ------------------ ------------- ------- ----
node1
node2
The following command and illustration shows the migration of LIFs from port e0a on Node2 to port e0b:
network interface migrate –vserver node2 -lif clus1 –dest-node node2 –dest-port e0b
The LIF is now associated with port e0b:


Example

----------- ---------- ---------- ------------------ ------------- ------- ----
node1
node2
7. Disconnect the cables that link the switches from the ports vacated in steps 3 on page 3 and 5 on page 4.
Example
In the example, the cables are disconnected from port e0a on each node and cluster traffic continues through the switch and
port e0b on each node:
8. Cable the ports that were formerly connected to the switch to each other, creating a direct connection between the
controllers.
Example
In the following example, e0a on node1 is connected to e0a on Node2:
9. Revert the LIFs that were migrated in steps 3 on page 3 and 5 on page 4 back to their home ports:
network interface revert –vserver vserver-name -lif LIF-name

Traffic on these ports can now travel through the back-to-back connection.
Example
The following example shows the command and illustrates the LIF revert:
network interface revert –vserver node1 -lif clus1
The LIFs are now associated with their home ports:
10. Confirm that the LIFs have been reverted:

Example

----------- ---------- ---------- ------------------ ------------- ------- ----
node1
node2
11. Change to the advanced privilege level from either node's prompt:
set -privilege advanced
You can respond y when prompted to continue into advanced mode and get to the advanced mode prompt *>.
12. Enable switchless-cluster mode:

network options switchless-cluster modify -enabled true
13. Return to the admin privilege level:

set -privilege admin
14. Select one of the remaining ports connected to the switch on the first node, and then migrate the interfaces from that port to a
port that uses the direct connection:
network interface migrate –vserver vserver_name -lif lif_name –dest-node destination-node-

Example
The following example shows the command and illustrates the LIF migration from port e0b on node1 to port e0a:
network interface migrate –vserver node1 -lif clus2 –dest-node node1 –dest-port e0a
The LIF is now associated with port e0a:

Example

----------- ---------- ---------- ------------------ ------------- ------- ----
node1
clus2 up/up 192.168.177.122/24 node1 e0a false
node2
16. Select the corresponding cluster port on the second node, and then migrate interfaces from that port to the port that usesthe
direct connection:
network interface migrate –vserver vserver_name -lif lif_name –dest-node destination-node-
Example
The following example shows the command and illustrates the LIF migration from port e0b on Node2 to port e0a:
network interface migrate –vserver node2 -lif clus2 –dest-node node2 –dest-port e0a

Example

----------- ---------- ---------- ------------------ ------------- ------- ----
node1
node2
18. Disconnect the cables that link the switches to the ports that no longer have traffic.
Example
In the following example, the cables to the switch are removed and cluster traffic continues through the direct connection
between the e0a ports:
controllers.
Example

20. Revert the LIFs that were migrated in steps 14 on page 6 and 16 on page 7 back to their home ports:
network interface revert –vserver vserver_name -lif lif_name
Example
The following example shows the command and illustrates the LIF migration:

Example

----------- ---------- ---------- ------------------ ------------- ------- ----
node1
node2
22. Reenable the –auto-revert parameter on each of the cluster LIFs on the cluster ports on both nodes:
network interface modify -vserver vserver_name -lif lif_name -auto-revert true

Example
The following shows the example commands to enable auto-revert on the LIFs:
a. Reenable –auto-revert on the LIF clus1 on node1:

network interface modify –vserver node1 -lif clus1 –auto-revert true
b. Reenable –auto-revert on the LIF clus2 on node1:

network interface modify -vserver node1 -lif clus2 -auto-revert true
c. Reenable –auto-revert on the LIF clus1 on node2:

d. Reenable–auto-revert on the LIF clus2 on node2:

23. Verify that the cluster port LIFs are operating correctly:
network interface show
24. Check the cluster status of the nodes from the system console of either node:
cluster show
The command produces output similar to the following:
Node Health Eligibility

----- ------- ------------
node1 true true
node2 true true
25. Verify cluster connectivity with the cluster ping-cluster local command:
a. Change to the advanced privilege level from either node's prompt:

You can respond y when prompted to continue into advanced mode and get to the advanced mode prompt *>.
b. Confirm connectivity between the cluster ports:

cluster ping-cluster local
The command output should show connectivity between all cluster ports.
c. Return to the admin privilege level:


Transitioning to a two-node switchless cluster (FAS22xx systems with a
single cluster-network connection)
If you have FAS22xx systems in an existing two-node cluster, you can apply the switchless-cluster networking option and
replace the switch with a single, direct, back-to-back connection between the nodes. This is a nondisruptive operation. This
configuration does not provide a redundant connection in the event of a cable or port failure.
Before you begin
• The cluster must be healthy and consist of two nodes connected by a cluster switch, and the nodes must be running Data
ONTAP 8.2 or later.
• Each storage system must use a single, dedicated 10-GbE cluster port that provides the cluster-network connection.
This is a supported configuration option for FAS22xx systems only.
• Command output examples in this section are from Data ONTAP 8.2.x, which differ from the command output in Data
ONTAP 8.3 and later.
See Transitioning to a two-node switchless cluster (systems with four redundant cluster-network connections) on page 14
for example command output for Data ONTAP 8.3 and later.
About this task

The following procedure shows the cluster switch in a two-node cluster being removed and the connection to the switch being
replaced with a direct connection to the partner node.
Steps
cluster show

----- ------- ------------
node1 true true
node2 true true
2. Check the status of the HA pair from the system console of either node:
Transitioning to a two-node switchless cluster (FAS22xx systems with a single cluster-network connection) 11
storage failover show
Example
The output should be similar to the following:
Node Partner Possible State Description

-------------- -------------- -------- -------------------------------------
node1 node2 true Connected to node2
3. Change to the advanced privilege level from either node's prompt:

You can respond y when prompted to continue into advanced mode and get to the advanced mode prompt (*>).


6. Take over the target node, entering y when prompted:

storage failover takeover -ofnode target_node_name
It does not matter which node is the target node. When it is taken over, the target node automatically reboots and displays
the Waiting for giveback... message.
The active node is now serving data for the partner (target) node that has been taken over.
7. Wait at least two minutes after takeover of the impaired node to ensure that the takeover was completed successfully.
8. With the target node showing the Waiting for giveback... message, shut it down.
The method you use depends on whether remote management through a Service Processor (SP) is used.
If the SP is... Then...

Configured Log in to the target node's SP, and then turn off the power from the console:
system power off
.
Not configured At the target node's prompt, press Ctrl-C, and then respond Y to halt the node.
9. On each controller, disconnect the cable that connects the 10-GbE cluster port to the cluster switch.
10. Connect the cluster port of each controller to the cluster port on the other controller, so that the controllers have a back-to-
back network connection.
11. Restart the target node.

The method you use depends on whether remote management via the SP is used.

Configured Log in to the target node's SP, and turn the power off from the console:
system power on

Not configured At the target node's prompt, issue the following command:
boot_ontap
The target node boots and displays the Waiting for giveback... message.
12. Give back storage to the target node:

storage failover giveback -ofnode target_node_name
13. Monitor the progress of the giveback operation by using the storage failover show-giveback command.
14. After the giveback operation is complete, confirm that the HA pair is healthy and takeover is possible by using the storage
failover show command.
Example
The output should be similar to the following:
Node Partner Possible State Description

-------------- -------------- -------- -------------------------------------
Example

----------- ---------- ---------- ------------------ ------------- ------- ----
node1
node2
cluster show

----- ------- ------------
node1 true true
node2 true true
17. Verify cluster connectivity by using the cluster ping-cluster local command:
a. Change to the advanced privilege level from either node's prompt:

Transitioning to a two-node switchless cluster (FAS22xx systems with a single cluster-network connection) 13
You can respond y when prompted to continue into advanced mode and get to the advanced mode prompt (*>).
b. Ping the cluster ports:


Transitioning to a two-node switchless cluster (systems with four

redundant cluster-network connections)
If you have an existing two-node cluster with four-port cluster interconnects connected to cluster network switches and are
running Data ONTAP 8.3 or later, you can apply the switchless-cluster networking option and replace the switches with direct,
back-to-back connections between the nodes. This is a nondisruptive operation.
Before you begin
• The cluster must be healthy and consist of two nodes connected by cluster switches, and the nodes must be running Data
ONTAP 8.3 or later.
• Each storage system must have four dedicated cluster ports, per controller, providing redundant cluster-network connections.
This is the supported configuration for most storage systems that support four cluster interconnects.
About this task

This procedure removes the cluster switches in a two-node cluster and replaces each connection to the switch with a direct
connection to the partner node:
Steps
1. Check the status of the nodes in the cluster to make sure health and eligibility are true:
Example

----- ------- ------------
node1 true true
node2 true true
2. How you proceed depends on the result of the previous command:
If... Then...
All nodes show true for both health Proceed to the next step.
and eligibility.
Any node shows false for health or Correct the problem and proceed to the next step.
eligibility.
3. Identify the cluster LIFs on the cluster ports:

Example
This example and the others in this procedure show systems that are using e0a, e0b, e0c, and e0d as cluster ports. Your
system might be using different cluster ports due to its particular requirements.
cluster1::> network interface show -role cluster
Logical Status Network

Current Current Is
Vserver Interface Admin/Oper Address/Mask
Node Port Home
----------- ---------- ---------- ------------------
------------- ------- ----
Cluster
node1_clus1 up/up 192.168.177.121/24 node1 e0a true
node1_clus2 up/up 192.168.177.122/24 node1 e0b true
node1_clus3 up/up 192.168.177.123/24 node1 e0c true
node1_clus4 up/up 192.168.177.124/24 node1 e0d true
4. Disable the –auto-revert parameter on each of the cluster LIFs on the cluster ports on both nodes:
network interface modify -vserver vserver_name -lif lif_name -auto-revert false
This enables you to then move the LIFs temporarily so that you can remove the cable connections from the switches.
Example
The following illustration shows a simplified view of the two nodes, node1 and node2:
• Each node is using ports e0a, e0b, e0c, and e0d for the cluster connections.
• Each port has a cluster LIF (one with the defined role of cluster) associated with it.
• Each node is configured with a Storage Virtual Machine (SVM, formerly known as Vserver), node1 and node2.
• The following example shows the connections to both ClusterSwitch1 and ClusterSwitch2.
Transitioning to a two-node switchless cluster (systems with four redundant cluster-network connections) 15
The following steps in this example disable auto-revert on the LIFs:
a. Disable -auto-revert on the LIF clus1 on node1:

network interface modify –vserver Cluster -lif node1_clus1 –auto-revert false
b. Disable -auto-revert on the LIF clus2 on node1:

network interface modify -vserver Cluster -lif node1_clus2 -auto-revert false
c. Disable -auto-revert on the LIF clus3 on node1:

d. Disable -auto-revert on the LIF clus4 on node1:

e. Repeat these substeps for all node2 cluster LIFs.
5. Select one of the cluster ports on the first node and migrate the interfaces from that port to the other cluster port on the same
node:
network interface migrate –vserver vserver-name -lif lif-name –dest-node destination-node-
Example
The following illustration and command shows the migration of cluster LIFs from port e0a on node1 to port e0c:
network interface migrate –vserver Cluster -lif node1_clus1 –dest-node node1 –dest-port e0c
The LIF is now associated with port e0c:


----------- ---------- ---------- ------------------ ------------- ------- ----
Cluster
node1_clus1 up/up 192.168.177.121/24 node1 e0c false
7. On the second node, select the corresponding cluster port and migrate interfaces from that port to another cluster port on the
same node:
Example
The following command and illustration shows the migration of LIFs from port e0a on node2 to port e0c:
network interface migrate –vserver Cluster -lif node2_clus1 –dest-node node2 –dest-port e0c
The LIF is now associated with port e0c:

----------- ---------- ---------- ------------------ ------------- ------- ----
Cluster
9. Repeat step 5 on page 16 through step 8 on page 18 to migrate the LIF from port e0b to the LIF on port e0d on node 1 and
node 2.


----------- ---------- ---------- ------------------ ------------- ------- ----
Cluster
node1_clus2 up/up 192.168.177.122/24 node1 e0d false
node2_clus2 up/up 192.168.177.126/24 node2 e0d false
11. Change to the advanced privilege level:

Respond y when prompted to continue into advanced mode. The advanced mode prompt appears (*>).
12. Disable the ports to LIF clus1 and clus2 (ports e0a and e0b) on node 1 by entering the following commands:
network port modify -node node1 -port e0a,e0b -up-admin false
13. Disable the ports to LIF clus1 and clus2 (ports e0a and e0b) on node 2 by entering the following commands:
network port modify -node node2 -port e0a,e0b -up-admin false

15. Disconnect the cables that link the switches from the ports vacated in steps 3 on page 3 and 5 on page 4.
Example
In the example, the cables are disconnected from port e0a and e0b on each node and cluster traffic continues through the
switch and ports e0c and e0d on each node:
controllers.
Example
In the following example, e0a and e0b on node1 are connected to their respective ports, e0a and e0b, on node2:

19. Bring the ports back up on each node:

network modify -node node1 -port e0a,e0b -up-admin true
network modify -node node2 -port e0a,e0b -up-admin true

21. Check that communication between the nodes is good and that no RPC failures appear:
network port show
Speed (Mbps)
Node Port IPspace Broadcast Domain Link MTU Admin/Oper
------ --------- ------------ ---------------- ----- ------- ------------
node1
.
.
e0a Cluster Cluster up 9000 auto/10000
e0b Cluster Cluster up 9000 auto/10000
e0c Cluster Cluster up 9000 auto/10000
e0d Cluster Cluster up 9000 auto/10000
node2
.
.

22. Revert the migrated LIFs, LIF clus1 and LIF clus2, back to their home ports:
network interface revert –vserver Cluster -lif LIF-name
Example
network interface revert –vserver Cluster -lif node1_clus1
The LIFs are now associated with their home ports:


----------- ---------- ---------- ------------------ ------------- ------- ----
Cluster
Example
----- ------- ------------
node1 true true
node2 true true
If... Then...
and eligibility.
eligibility.
26. Verify that the connections are present:

network device-discovery show
Local Discovered
Node Port Device Interface Platform
----------- ------ ------------------------- ---------------- ----------------
node1
.
.
e0a node2 e0a FASxxxx
e0b node2 e0b FASxxxx
e0c switch_name 0/1 CN1610
e0d switch_name 0/2 CN1610
node2
.
.
e0c switch_name 0/3 CN1610
e0d switch_name 0/4 CN1610
27. Select one of the cluster ports on the first node and migrate the interfaces from that port to the other cluster port on the same
node:
Example
The following illustration shows the migration of cluster LIFs from port e0c on node1 to port e0a:
network interface migrate –vserver Cluster -lif node1_clus3 –dest-node node1 –dest-port e0a


----------- ---------- ---------- ------------------ ------------- ------- ----
Cluster
node1_clus3 up/up 192.168.177.123/24 node1 e0a false
29. On the second node, select the corresponding cluster port and migrate interfaces from that port to another cluster port on the
same node:
Example
The following command and illustration shows the migration of LIFs from port e0c on node2 to port e0a:
network interface migrate –vserver Cluster -lif node2_clus3 –dest-node node2 –dest-port e0a

----------- ---------- ---------- ------------------ ------------- ------- ----
Cluster
31. Repeat step 27 on page 22 through step 29 on page 23to migrate the LIF from port e0d to the LIF on port e0b on node 1 and
node 2.
32. Confirm that the LIFs have been migrated:


----------- ---------- ---------- ------------------ ------------- ------- ----
Cluster
node1_clus4 up/up 192.168.177.124/24 node1 e0b false
node2_clus4 up/up 192.168.177.128/24 node2 e0b false

You can respond y when prompted to continue into advanced mode. The advanced mode prompt appears (*>).
34. Disable the ports to LIF clus3 and clus4 (ports e0c and e0d) on node 1 by entering the following commands:
network port modify -node node1 -port e0c,e0d -up-admin false
35. Disable the ports to LIF clus3 and clus4 (ports e0c and e0d) on node 2 by entering the following commands:
network port modify -node node2 -port e0c,e0d -up-admin false

37. Disconnect the cables that link the switches to the ports that no longer have traffic.
Example
In the example, cluster traffic continues through the direct connection between the e0a and e0b ports:
controllers.
Example
40. Bring the ports back up on each node:

network modify -node node1 -port e0c,e0d -up-admin true
network modify -node node2 -port e0c,e0d -up-admin true

42. Revert the migrated LIFs, LIF clus3 and LIF clus4, back to their home ports:
network interface revert –vserver Cluster -lif LIF-name
Example


----------- ---------- ---------- ------------------ ------------- ------- ----
Cluster

44. Check that communication between the nodes is good and that no RPC failures appear:
network port show
Speed (Mbps)
Node Port IPspace Broadcast Domain Link MTU Admin/Oper
------ --------- ------------ ---------------- ----- ------- ------------
node1
.
.
node2
.
.
Example

----- ------- ------------
node1 true true
node2 true true
If... Then...
and eligibility.
eligibility.
47. Verify that the connections are present:

network device-discovery show
Local Discovered
Node Port Device Interface Platform
----------- ------ ------------------------- ---------------- ----------------
node1
.
.
e0c node2 e0c FASxxxx
e0d node2 e0d FASxxxx
node2
.
.
e0c node1 e0c FASxxxx
e0d node1 e0d FASxxxx
48. Reenable the –auto-revert parameter on each of the cluster LIFs on the cluster ports on both nodes:
network interface modify -vserver Cluster -lif LIF-name -auto-revert true
Example
In the following example, we take the steps to reenable auto-revert on the LIFs:
a. Re-enable auto-revert on the LIF clus1 on node1:

network interface modify –vserver Cluster -lif node1_clus1 –auto-revert true
b. Re-enable auto-revert on the LIF clus2 on node1:

network interface modify -vserver Cluster -lif node1_clus2 -auto-revert true
c. Re-enable auto-revert on the LIF clus3 on node1:

d. Re-enable auto-revert on the LIF clus4 on node1:

e. Repeat these substeps for all LIFs on node 2.
49. Check the cluster status of the nodes by entering the following command at the system console of either node:
cluster show

----- ------- ------------
node1 true true
node2 true true
network interface show
51. Verify cluster connectivity with the cluster ping-cluster local command:
a. Change to the advanced privilege level:

You can respond y when prompted to continue into advanced mode. The advanced mode prompt appears (*>).
b. Confirm connectivity between the cluster ports:

Copyright information
Copyright © 1994–2014 NetApp, Inc. All rights reserved. Printed in the U.S.
No part of this document covered by copyright may be reproduced in any form or by any means—graphic, electronic, or
mechanical, including photocopying, recording, taping, or storage in an electronic retrieval system—without prior written
permission of the copyright owner.
Software derived from copyrighted NetApp material is subject to the following license and disclaimer:
THIS SOFTWARE IS PROVIDED BY NETAPP "AS IS" AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
PARTICULAR PURPOSE, WHICH ARE HEREBY DISCLAIMED. IN NO EVENT SHALL NETAPP BE LIABLE FOR
ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER
IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY
WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
NetApp reserves the right to change any products described herein at any time, and without notice. NetApp assumes no
responsibility or liability arising from the use of products described herein, except as expressly agreed to in writing by NetApp.
The use or purchase of this product does not convey a license under any patent rights, trademark rights, or any other intellectual
property rights of NetApp.
The product described in this manual may be protected by one or more U.S. patents, foreign patents, or pending applications.
RESTRICTED RIGHTS LEGEND: Use, duplication, or disclosure by the government is subject to restrictions as set forth in
subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.277-7103 (October 1988)
and FAR 52-227-19 (June 1987).
Trademark information
NetApp, the NetApp logo, Go Further, Faster, ASUP, AutoSupport, Campaign Express, Cloud ONTAP, clustered Data
ONTAP, Customer Fitness, Data ONTAP, DataMotion, Fitness, Flash Accel, Flash Cache, Flash Pool, FlashRay, FlexArray,
FlexCache, FlexClone, FlexPod, FlexScale, FlexShare, FlexVol, FPolicy, GetSuccessful, LockVault, Manage ONTAP, Mars,
MetroCluster, MultiStore, NetApp Insight, OnCommand, ONTAP, ONTAPI, RAID DP, SANtricity, SecureShare, Simplicity,
Simulate ONTAP, Snap Creator, SnapCopy, SnapDrive, SnapIntegrator, SnapLock, SnapManager, SnapMirror, SnapMover,
SnapProtect, SnapRestore, Snapshot, SnapValidator, SnapVault, StorageGRID, Tech OnTap, Unbound Cloud, and WAFL are
trademarks or registered trademarks of NetApp, Inc., in the United States, and/or other countries. A current list of NetApp
trademarks is available on the web at http://www.netapp.com/us/legal/netapptmlist.aspx.
Cisco and the Cisco logo are trademarks of Cisco in the U.S. and other countries. All other brands or products are trademarks or
registered trademarks of their respective holders and should be treated as such.
Copyright information 29
How to send your comments
You can help us to improve the quality of our documentation by sending us your feedback.
Your feedback is important in helping us to provide the most accurate and high-quality information. If you have suggestions for
improving this document, send us your comments by email to doccomments@netapp.com. To help us direct your comments to
the correct division, include in the subject line the product name, version, and operating system.
You can also contact us in the following ways:
• NetApp, Inc., 495 East Java Drive, Sunnyvale, CA 94089 U.S.
• Telephone: +1 (408) 822-6000
• Fax: +1 (408) 822-4501
• Support telephone: +1 (888) 463-8277

Netapp Cluster For NDMP

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Netapp Cluster For NDMP

Uploaded by

Copyright:

Available Formats

Transitioning to a two-node switchless cluster

Transitioning to a two-node switchless cluster (systems with redundant

Before you begin

About this task

1. Identify the cluster LIFs on the cluster ports:

node1::> network interface show -role cluster

Logical Status Network Current Current Is

4 entries were displayed.

2 Transitioning to a two-node switchless cluster

a. Disable –auto-revert on the LIF clus1 on node1:

b. Disable–auto-revert on the LIF clus2 on node1:

c. Disable –auto-revert on the LIF clus1 on node2:

d. Disable –auto-revert on the LIF clus2 on node2:

The LIF is now associated with port e0b:

4. Confirm that the LIF has been migrated:

Transitioning to a two-node switchless cluster (systems with redundant cluster-network connections) 3

node1::> network interface show -role cluster

4 entries were displayed.

node1::> network interface show -role cluster

4 entries were displayed.

The LIF is now associated with port e0b:

6. Confirm that the LIF has been migrated:

4 Transitioning to a two-node switchless cluster

node1::> network interface show -role cluster

4 entries were displayed.

Transitioning to a two-node switchless cluster (systems with redundant cluster-network connections) 5

The LIFs are now associated with their home ports:

10. Confirm that the LIFs have been reverted:

node1::> network interface show -role cluster

4 entries were displayed.

12. Enable switchless-cluster mode:

13. Return to the admin privilege level:

6 Transitioning to a two-node switchless cluster

The LIF is now associated with port e0a:

15. Confirm that the LIF has been migrated:

node1::> network interface show -role cluster

4 entries were displayed.

The LIF is now associated with port e0a:

Transitioning to a two-node switchless cluster (systems with redundant cluster-network connections) 7

node1::> network interface show -role cluster

4 entries were displayed.

8 Transitioning to a two-node switchless cluster

21. Confirm that the LIFs have been reverted:

node1::> network interface show -role cluster

4 entries were displayed.

Transitioning to a two-node switchless cluster (systems with redundant cluster-network connections) 9

a. Reenable –auto-revert on the LIF clus1 on node1:

b. Reenable –auto-revert on the LIF clus2 on node1:

c. Reenable –auto-revert on the LIF clus1 on node2:

d. Reenable–auto-revert on the LIF clus2 on node2:

The command produces output similar to the following:

Node Health Eligibility

a. Change to the advanced privilege level from either node's prompt:

b. Confirm connectivity between the cluster ports:

c. Return to the admin privilege level:

10 Transitioning to a two-node switchless cluster

Before you begin

About this task

The command produces output similar to the following:

Node Health Eligibility

Node Partner Possible State Description

3. Change to the advanced privilege level from either node's prompt:

4. Enable switchless-cluster mode: