PowerStore: NMN mapping Fails after MNR from IPv4 to IPv6

Résumé: NMN (NAS Mobility Network / File Mobility Network) mapping failing with error "Cannot connect to the remote system with the IP Modify cluster IP of dpNetwork:{dpNetworkID} failed." after MNR (Network Management Reconfiguration) from IPv4 to IPv6. ...

Cet article concerne Cet article ne concerne pas Cet article n’est associé à aucun produit spécifique. Toutes les versions du produit ne sont pas identifiées dans cet article.
Consulter d’autres ressources

Symptômes

If MNR from IPv4 to IPv6 is done during an active replication session (having an unmapped File Mobility network for performing MNR), the newly created cannot be mapped on the File Mobility IPv6 Network. The following error is raised: 
Cannot connect to the remote system with the IP 10.225.xxx.xxx. (0xE0801011104B) Modify cluster IP of dpNetwork: {dpNetworkID}

Cause

The problem occurs when creating and mapping the File Mobility Network, the SDNAS application does not support modification of File Mobility Network on the fly from IPv4 to IPv6.

Résolution

After the user has created (and failed to map) the IPv6 File Mobility Network, IPv6 MNR (they are in one subnet):
  1. Perform MNR back from IPv6 to IPv4
  2. Create and map File Mobility Network in IPv4
  3. Remove remote system and any objects that are related to it (Replication session, Protection Policy, Replication Rule, Snapshot Rule etc.)
  4. Unmap and delete File Mobility Network in IPv4
  5. Perform MNR from IPv4 to IPv6
  6. Create and map File Mobility Network in IPv6
  7. Create all removed objects in step 3 (Remote system, Protection Policy, Replication Rule, Snapshot Rule, Replication session).

Produits concernés

PowerStore
Propriétés de l’article
Numéro d’article: 000202945
Type d’article: Solution
Dernière modification: 05 Sep 2023
Version:  3
Trouvez des réponses à vos questions auprès d’autres utilisateurs Dell
Services de support
Vérifiez si votre appareil est couvert par les services de support.