PowerStore: NMN mapping Fails after MNR from IPv4 to IPv6

Summary: 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. ...

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.
Check out other resources

Symptoms

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.

Resolution

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).

Affected Products

PowerStore
Article Properties
Article Number: 000202945
Article Type: Solution
Last Modified: 05 Sept 2023
Version:  3
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.