Hi,

I did Hardware-Lifecycle without the officially supported Switches. Just created a VLAN on the frontend-switches and connected two HA-Pairs together (8 links in total), moved the resources and unjoined the old empty nodes. Worked as expected without any downtime at all. But this was within the same datacenter so I’m not sure about the distance thing if the controller checks for roundtrip times within the cluster network.

BR, Markus

From: Toasters <toasters-bounces@teaparty.net> on behalf of Heino Walther <hw@beardmann.dk>
Date: Tuesday, 9. August 2022 at 08:25
To: "toasters@teaparty.net" <toasters@teaparty.net>
Subject: [EXT] Cluster Node Distance

ATTENTION: This email originated from outside of the organisation. Do not click on links or open attachments unless you recognize the sender and know the content is safe

Hi there

We are in the process of migrating from one DC to another DC which is about 2KM appart.

We have a standard HA-Two node A300 which we would like to migrate out to the new DC without any down time.

We have several 10G lines between the two sites with Cisco networking equipment.

I seem to recall that officielly NetApp only supports about 3-400M between the cluster nodes, but I cannot see why it should not be possible to extend this distance to the 2KM we need?  I doubt the systems will notice.

This is of cause only as a part of the migration process, so we setup another A300 cluster with disks at the new DC and add them to the existing cluster over the 2KM distance, then move over the volumes and interfaces nice an easy.

When we have moved everything, we remove the two (now empty) nodes to the new DC, join them to the cluster and move the data back again.

Has anyone tried this over this kind of distances?

We have official CN1610 but after looking at the Cisco RFC’s from NetApp I think we might as well just create this network on our own Cisco equipment.

If this is a no-go, are there any other options, short of converting it into a MetroCluster? 😉

/Heino