`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