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
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
I've heard of Multi-KM moves before with (temporarily) 4 Cluster-Switches (2 per DC...). It was ~10 nodes IIRC.
/SG
On 09.08.2022 08:20, Heino Walther wrote:
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
Toasters mailing list Toasters@teaparty.net https://www.teaparty.net/mailman/listinfo/toasters
I think we are more or less forced to use the existing Cisco Nexus switches because the CN1610 switches does not support any LongRange SFP+ modules..I tried with a few different ones that are close to the supported Avago SFP SR modules, but the switch just ignores them and they cannot be seen at all….
/Heino
Fra: Toasters toasters-bounces@teaparty.net på vegne af Sebastian Goetze spgoetze@gmail.com Dato: tirsdag, 9. august 2022 kl. 12.12 Til: toasters@teaparty.net toasters@teaparty.net Emne: Re: Cluster Node Distance
I've heard of Multi-KM moves before with (temporarily) 4 Cluster-Switches (2 per DC...). It was ~10 nodes IIRC.
/SG On 09.08.2022 08:20, Heino Walther wrote: 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
_______________________________________________
Toasters mailing list
Toasters@teaparty.netmailto:Toasters@teaparty.net
`service unsupported-transceiver` should help with that, not sure if that’s still available on the latest versions, but I think it is.
https://community.cisco.com/t5/switching/command-service-unsupported-transce...
Alexander Griesser Head of Systems Operations
ANEXIA Internetdienstleistungs GmbH
E-Mail: AGriesser@anexia-it.commailto:AGriesser@anexia-it.com Web: http://www.anexia-it.comhttp://www.anexia-it.com/
Anschrift Hauptsitz Klagenfurt: Feldkirchnerstraße 140, 9020 Klagenfurt Geschäftsführer: Alexander Windbichler Firmenbuch: FN 289918a | Gerichtsstand: Klagenfurt | UID-Nummer: AT U63216601
Von: Toasters toasters-bounces@teaparty.net Im Auftrag von Heino Walther Gesendet: Dienstag, 9. August 2022 12:15 An: Sebastian Goetze spgoetze@gmail.com; toasters@teaparty.net Betreff: [EXT] SV: 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
I think we are more or less forced to use the existing Cisco Nexus switches because the CN1610 switches does not support any LongRange SFP+ modules..I tried with a few different ones that are close to the supported Avago SFP SR modules, but the switch just ignores them and they cannot be seen at all….
/Heino
Fra: Toasters <toasters-bounces@teaparty.netmailto:toasters-bounces@teaparty.net> på vegne af Sebastian Goetze <spgoetze@gmail.commailto:spgoetze@gmail.com> Dato: tirsdag, 9. august 2022 kl. 12.12 Til: toasters@teaparty.netmailto:toasters@teaparty.net <toasters@teaparty.netmailto:toasters@teaparty.net> Emne: Re: Cluster Node Distance
I've heard of Multi-KM moves before with (temporarily) 4 Cluster-Switches (2 per DC...). It was ~10 nodes IIRC.
/SG On 09.08.2022 08:20, Heino Walther wrote: 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
_______________________________________________
Toasters mailing list
Toasters@teaparty.netmailto:Toasters@teaparty.net
That’s for Cisco… and the command does not work on the CN1610. But it would help if I started by inserting Ethernet SFP modules instead of FibreChannel 😉
/Heino
Fra: Alexander Griesser AGriesser@anexia-it.com Dato: tirsdag, 9. august 2022 kl. 12.21 Til: Heino Walther hw@beardmann.dk, Sebastian Goetze spgoetze@gmail.com, toasters@teaparty.net toasters@teaparty.net Emne: AW: [EXT] SV: Cluster Node Distance `service unsupported-transceiver` should help with that, not sure if that’s still available on the latest versions, but I think it is.
https://community.cisco.com/t5/switching/command-service-unsupported-transce...
Alexander Griesser Head of Systems Operations
ANEXIA Internetdienstleistungs GmbH
E-Mail: AGriesser@anexia-it.commailto:AGriesser@anexia-it.com Web: http://www.anexia-it.comhttp://www.anexia-it.com/
Anschrift Hauptsitz Klagenfurt: Feldkirchnerstraße 140, 9020 Klagenfurt Geschäftsführer: Alexander Windbichler Firmenbuch: FN 289918a | Gerichtsstand: Klagenfurt | UID-Nummer: AT U63216601
Von: Toasters toasters-bounces@teaparty.net Im Auftrag von Heino Walther Gesendet: Dienstag, 9. August 2022 12:15 An: Sebastian Goetze spgoetze@gmail.com; toasters@teaparty.net Betreff: [EXT] SV: 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
I think we are more or less forced to use the existing Cisco Nexus switches because the CN1610 switches does not support any LongRange SFP+ modules..I tried with a few different ones that are close to the supported Avago SFP SR modules, but the switch just ignores them and they cannot be seen at all….
/Heino
Fra: Toasters <toasters-bounces@teaparty.netmailto:toasters-bounces@teaparty.net> på vegne af Sebastian Goetze <spgoetze@gmail.commailto:spgoetze@gmail.com> Dato: tirsdag, 9. august 2022 kl. 12.12 Til: toasters@teaparty.netmailto:toasters@teaparty.net <toasters@teaparty.netmailto:toasters@teaparty.net> Emne: Re: Cluster Node Distance
I've heard of Multi-KM moves before with (temporarily) 4 Cluster-Switches (2 per DC...). It was ~10 nodes IIRC.
/SG On 09.08.2022 08:20, Heino Walther wrote: 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
_______________________________________________
Toasters mailing list
Toasters@teaparty.netmailto:Toasters@teaparty.net
Sorry, I read your sentence again – I thought you wanted to use the Nexus but can’t due to the incompatible SFPs, but it’s the other way round… Getting another cup of coffee now.
Alexander Griesser Head of Systems Operations
ANEXIA Internetdienstleistungs GmbH
E-Mail: AGriesser@anexia-it.commailto:AGriesser@anexia-it.com Web: http://www.anexia-it.comhttp://www.anexia-it.com/
Anschrift Hauptsitz Klagenfurt: Feldkirchnerstraße 140, 9020 Klagenfurt Geschäftsführer: Alexander Windbichler Firmenbuch: FN 289918a | Gerichtsstand: Klagenfurt | UID-Nummer: AT U63216601
Von: Heino Walther hw@beardmann.dk Gesendet: Dienstag, 9. August 2022 12:46 An: Alexander Griesser AGriesser@anexia-it.com; Sebastian Goetze spgoetze@gmail.com; toasters@teaparty.net Betreff: SV: [EXT] SV: 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
That’s for Cisco… and the command does not work on the CN1610. But it would help if I started by inserting Ethernet SFP modules instead of FibreChannel 😉
/Heino
Fra: Alexander Griesser <AGriesser@anexia-it.commailto:AGriesser@anexia-it.com> Dato: tirsdag, 9. august 2022 kl. 12.21 Til: Heino Walther <hw@beardmann.dkmailto:hw@beardmann.dk>, Sebastian Goetze <spgoetze@gmail.commailto:spgoetze@gmail.com>, toasters@teaparty.netmailto:toasters@teaparty.net <toasters@teaparty.netmailto:toasters@teaparty.net> Emne: AW: [EXT] SV: Cluster Node Distance `service unsupported-transceiver` should help with that, not sure if that’s still available on the latest versions, but I think it is.
https://community.cisco.com/t5/switching/command-service-unsupported-transce...
Alexander Griesser Head of Systems Operations
ANEXIA Internetdienstleistungs GmbH
E-Mail: AGriesser@anexia-it.commailto:AGriesser@anexia-it.com Web: http://www.anexia-it.comhttp://www.anexia-it.com/
Anschrift Hauptsitz Klagenfurt: Feldkirchnerstraße 140, 9020 Klagenfurt Geschäftsführer: Alexander Windbichler Firmenbuch: FN 289918a | Gerichtsstand: Klagenfurt | UID-Nummer: AT U63216601
Von: Toasters <toasters-bounces@teaparty.netmailto:toasters-bounces@teaparty.net> Im Auftrag von Heino Walther Gesendet: Dienstag, 9. August 2022 12:15 An: Sebastian Goetze <spgoetze@gmail.commailto:spgoetze@gmail.com>; toasters@teaparty.netmailto:toasters@teaparty.net Betreff: [EXT] SV: 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
I think we are more or less forced to use the existing Cisco Nexus switches because the CN1610 switches does not support any LongRange SFP+ modules..I tried with a few different ones that are close to the supported Avago SFP SR modules, but the switch just ignores them and they cannot be seen at all….
/Heino
Fra: Toasters <toasters-bounces@teaparty.netmailto:toasters-bounces@teaparty.net> på vegne af Sebastian Goetze <spgoetze@gmail.commailto:spgoetze@gmail.com> Dato: tirsdag, 9. august 2022 kl. 12.12 Til: toasters@teaparty.netmailto:toasters@teaparty.net <toasters@teaparty.netmailto:toasters@teaparty.net> Emne: Re: Cluster Node Distance
I've heard of Multi-KM moves before with (temporarily) 4 Cluster-Switches (2 per DC...). It was ~10 nodes IIRC.
/SG On 09.08.2022 08:20, Heino Walther wrote: 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
_______________________________________________
Toasters mailing list
Toasters@teaparty.netmailto:Toasters@teaparty.net
Well we are not sure… it all depends on what we can get some ports on the Cisco switches, or if we have to use dedicated fibers for the CN1610s.
It looks like the CN1610 accepts prettymuch everything 😊
/Heino
Fra: Alexander Griesser AGriesser@anexia-it.com Dato: tirsdag, 9. august 2022 kl. 12.48 Til: Heino Walther hw@beardmann.dk, Sebastian Goetze spgoetze@gmail.com, toasters@teaparty.net toasters@teaparty.net Emne: AW: [EXT] SV: Cluster Node Distance Sorry, I read your sentence again – I thought you wanted to use the Nexus but can’t due to the incompatible SFPs, but it’s the other way round… Getting another cup of coffee now.
Alexander Griesser Head of Systems Operations
ANEXIA Internetdienstleistungs GmbH
E-Mail: AGriesser@anexia-it.commailto:AGriesser@anexia-it.com Web: http://www.anexia-it.comhttp://www.anexia-it.com/
Anschrift Hauptsitz Klagenfurt: Feldkirchnerstraße 140, 9020 Klagenfurt Geschäftsführer: Alexander Windbichler Firmenbuch: FN 289918a | Gerichtsstand: Klagenfurt | UID-Nummer: AT U63216601
Von: Heino Walther hw@beardmann.dk Gesendet: Dienstag, 9. August 2022 12:46 An: Alexander Griesser AGriesser@anexia-it.com; Sebastian Goetze spgoetze@gmail.com; toasters@teaparty.net Betreff: SV: [EXT] SV: 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
That’s for Cisco… and the command does not work on the CN1610. But it would help if I started by inserting Ethernet SFP modules instead of FibreChannel 😉
/Heino
Fra: Alexander Griesser <AGriesser@anexia-it.commailto:AGriesser@anexia-it.com> Dato: tirsdag, 9. august 2022 kl. 12.21 Til: Heino Walther <hw@beardmann.dkmailto:hw@beardmann.dk>, Sebastian Goetze <spgoetze@gmail.commailto:spgoetze@gmail.com>, toasters@teaparty.netmailto:toasters@teaparty.net <toasters@teaparty.netmailto:toasters@teaparty.net> Emne: AW: [EXT] SV: Cluster Node Distance `service unsupported-transceiver` should help with that, not sure if that’s still available on the latest versions, but I think it is.
https://community.cisco.com/t5/switching/command-service-unsupported-transce...
Alexander Griesser Head of Systems Operations
ANEXIA Internetdienstleistungs GmbH
E-Mail: AGriesser@anexia-it.commailto:AGriesser@anexia-it.com Web: http://www.anexia-it.comhttp://www.anexia-it.com/
Anschrift Hauptsitz Klagenfurt: Feldkirchnerstraße 140, 9020 Klagenfurt Geschäftsführer: Alexander Windbichler Firmenbuch: FN 289918a | Gerichtsstand: Klagenfurt | UID-Nummer: AT U63216601
Von: Toasters <toasters-bounces@teaparty.netmailto:toasters-bounces@teaparty.net> Im Auftrag von Heino Walther Gesendet: Dienstag, 9. August 2022 12:15 An: Sebastian Goetze <spgoetze@gmail.commailto:spgoetze@gmail.com>; toasters@teaparty.netmailto:toasters@teaparty.net Betreff: [EXT] SV: 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
I think we are more or less forced to use the existing Cisco Nexus switches because the CN1610 switches does not support any LongRange SFP+ modules..I tried with a few different ones that are close to the supported Avago SFP SR modules, but the switch just ignores them and they cannot be seen at all….
/Heino
Fra: Toasters <toasters-bounces@teaparty.netmailto:toasters-bounces@teaparty.net> på vegne af Sebastian Goetze <spgoetze@gmail.commailto:spgoetze@gmail.com> Dato: tirsdag, 9. august 2022 kl. 12.12 Til: toasters@teaparty.netmailto:toasters@teaparty.net <toasters@teaparty.netmailto:toasters@teaparty.net> Emne: Re: Cluster Node Distance
I've heard of Multi-KM moves before with (temporarily) 4 Cluster-Switches (2 per DC...). It was ~10 nodes IIRC.
/SG On 09.08.2022 08:20, Heino Walther wrote: 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
_______________________________________________
Toasters mailing list
Toasters@teaparty.netmailto:Toasters@teaparty.net
I know you said no downtime. If you have the extra gear, you can use SVMDR.
Setup the new cluster.
If the VLANs are stretched and all ip info stays the same you can do SVMDR with identity preserve set to true.
Create the svmdr relationships. Replicate.
When done: Stop source Update, quiesce, break mirror Start destination Verify
Downtime can be very minimal
If you have an nfs only workload, there is supposed to be a non disruptive way to make this work with 9.11.1 on AFF only.
(Any typos are courtesy of Google GBoard!)
--tmac
________________________________ From: Toasters toasters-bounces@teaparty.net on behalf of Heino Walther hw@beardmann.dk Sent: Tuesday, August 9, 2022 6:54 AM To: Alexander Griesser AGriesser@anexia-it.com; Sebastian Goetze spgoetze@gmail.com; toasters@teaparty.net toasters@teaparty.net Subject: SV: [EXT] SV: Cluster Node Distance
Well we are not sure… it all depends on what we can get some ports on the Cisco switches, or if we have to use dedicated fibers for the CN1610s.
It looks like the CN1610 accepts prettymuch everything 😊
/Heino
Fra: Alexander Griesser AGriesser@anexia-it.com Dato: tirsdag, 9. august 2022 kl. 12.48 Til: Heino Walther hw@beardmann.dk, Sebastian Goetze spgoetze@gmail.com, toasters@teaparty.net toasters@teaparty.net Emne: AW: [EXT] SV: Cluster Node Distance Sorry, I read your sentence again – I thought you wanted to use the Nexus but can’t due to the incompatible SFPs, but it’s the other way round… Getting another cup of coffee now.
Alexander Griesser Head of Systems Operations
ANEXIA Internetdienstleistungs GmbH
E-Mail: AGriesser@anexia-it.commailto:AGriesser@anexia-it.com Web: http://www.anexia-it.comhttp://www.anexia-it.com/
Anschrift Hauptsitz Klagenfurt: Feldkirchnerstraße 140, 9020 Klagenfurt Geschäftsführer: Alexander Windbichler Firmenbuch: FN 289918a | Gerichtsstand: Klagenfurt | UID-Nummer: AT U63216601
Von: Heino Walther hw@beardmann.dk Gesendet: Dienstag, 9. August 2022 12:46 An: Alexander Griesser AGriesser@anexia-it.com; Sebastian Goetze spgoetze@gmail.com; toasters@teaparty.net Betreff: SV: [EXT] SV: 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
That’s for Cisco… and the command does not work on the CN1610. But it would help if I started by inserting Ethernet SFP modules instead of FibreChannel 😉
/Heino
Fra: Alexander Griesser <AGriesser@anexia-it.commailto:AGriesser@anexia-it.com> Dato: tirsdag, 9. august 2022 kl. 12.21 Til: Heino Walther <hw@beardmann.dkmailto:hw@beardmann.dk>, Sebastian Goetze <spgoetze@gmail.commailto:spgoetze@gmail.com>, toasters@teaparty.netmailto:toasters@teaparty.net <toasters@teaparty.netmailto:toasters@teaparty.net> Emne: AW: [EXT] SV: Cluster Node Distance `service unsupported-transceiver` should help with that, not sure if that’s still available on the latest versions, but I think it is.
https://community.cisco.com/t5/switching/command-service-unsupported-transce...
Alexander Griesser Head of Systems Operations
ANEXIA Internetdienstleistungs GmbH
E-Mail: AGriesser@anexia-it.commailto:AGriesser@anexia-it.com Web: http://www.anexia-it.comhttp://www.anexia-it.com/
Anschrift Hauptsitz Klagenfurt: Feldkirchnerstraße 140, 9020 Klagenfurt Geschäftsführer: Alexander Windbichler Firmenbuch: FN 289918a | Gerichtsstand: Klagenfurt | UID-Nummer: AT U63216601
Von: Toasters <toasters-bounces@teaparty.netmailto:toasters-bounces@teaparty.net> Im Auftrag von Heino Walther Gesendet: Dienstag, 9. August 2022 12:15 An: Sebastian Goetze <spgoetze@gmail.commailto:spgoetze@gmail.com>; toasters@teaparty.netmailto:toasters@teaparty.net Betreff: [EXT] SV: 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
I think we are more or less forced to use the existing Cisco Nexus switches because the CN1610 switches does not support any LongRange SFP+ modules..I tried with a few different ones that are close to the supported Avago SFP SR modules, but the switch just ignores them and they cannot be seen at all….
/Heino
Fra: Toasters <toasters-bounces@teaparty.netmailto:toasters-bounces@teaparty.net> på vegne af Sebastian Goetze <spgoetze@gmail.commailto:spgoetze@gmail.com> Dato: tirsdag, 9. august 2022 kl. 12.12 Til: toasters@teaparty.netmailto:toasters@teaparty.net <toasters@teaparty.netmailto:toasters@teaparty.net> Emne: Re: Cluster Node Distance
I've heard of Multi-KM moves before with (temporarily) 4 Cluster-Switches (2 per DC...). It was ~10 nodes IIRC.
/SG On 09.08.2022 08:20, Heino Walther wrote: 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
_______________________________________________
Toasters mailing list
Toasters@teaparty.netmailto:Toasters@teaparty.net
-
Alexander Griesser -
Heino Walther -
Markus Nödl -
Sebastian Goetze -
Tim McCarthy