#SM Active Sync NVME over TCP with VMware

1 messages · Page 1 of 1 (latest)

dense ember
#

Has anyone got this working.

I'm running into quite a few issues trying to get this setup and working.

I have finally managed to get the snapmirror relationship working via CLI, but on the DR SVM i cannot map the subsystem to a namespace.

(vserver nvme subsystem map add)

Error: command failed: The first map between a subsystem and a namespace in a SnapMirror active sync relationship is only supported on the primary side of the relationship.

So from a VMware POV it can only see the paths of the primary SVM for the datastore

BTW NetApp's docs around this is terrible.. Someone really needs to write a decent KB !

I have done this with iSCSi many times and it allows you map to initiators on the DR site.

Ideas?

arctic lynx
#

do the NVMe LIFs on the second site show up in vserver nvme show-interfaces?

clear ridge
#

What guides/docs did you use?

The ones I've found:

Also these two about NVMe/TCP in general (without SM-as):

Also did you try using ONTAP tools for VMware vSphere?

I have not tried it with NVMe/TCP yet, especially because of the limitations when expanding or shrinking a consistency group which is disruptive with NVMe/TCP.

dense ember
# arctic lynx do the NVMe LIFs on the second site show up in `vserver nvme show-interfaces`?

The interfaces are there and i have added the destination SVM into vCenter .. Everything seems to be sort of setup ok besides not being able to map the DR namespaces to subsystem to present the extra paths.
gw-testing-nvme-bc_lif01 m1d-l2-mmr02-ntap-cls01-01:a0a-1225
nvme-tcp
Transport Address: 10.3.225.96
gw-testing-nvme-bc_lif02 m1d-l2-mmr02-ntap-cls01-02:a0a-1225
nvme-tcp
Transport Address: 10.3.225.97

dense ember
#

I have a gut feeling maybe i cannot use the Replication Policy AutomatedFailOver and i need to use AutomatedFailOverDuplex

clear ridge
#

What ONTAP version are you using and what hardware models? You definitely need "symmetric active/active" for NVMe support with SMas so you have to use AutomatedFailoverDuplex. The AutomatedFailover policy would be "asymmetric active/active" which is not supported for NVMe.

It's mentioned over there:
"Ensure you designate the AutomatedFailOverDuplex policy to establish bidirectional sync replication."

dense ember
#

ONTAP 9.17.1P4 on a pair of A20 AFF nodes

dense ember
#

ok i have now updated my mirror

#

the replicated SVM still does not map the namespace to a sub system

#

when i try and map it i get this error

#

on the esx host i have 2 NVME adapters one for each 25gb connection

#

and i have connected both SVM NVME controllers

#

but VMware is only seeing 4 paths (from the Prod SVM) and nothing from the secondary SVM