PowerStore: Reconfiguration of IPv4 to IPv6 or from IPv6 to IPv4 using Management Network Reconfiguration (MNR) does not validate that vCenter address is resolvable

The Management Network Reconfiguration (MNR) operation IPv4 -> IPv6 or IPv6 -> IPv4 does not verify that the vCenter address is resolvable if the vCenter address is FQDN.
Also, the MNR process does not have a mechanism to validate, that DNS and NTP services accessible by provided IPs or FQDN for NTP.

PowerStore supports changing  the management network version. This potentially requires the change of the environment (NTP, DNS, vCenter servers) to match the updated network. If a user provides the FQDN for the vCenter Server and there is no DNS record that is registered matching the updated network IP version, or the DNS server is not available, PowerStore cannot detect this beforehand. PowerStore proceeds with the reconfiguration and it fails and rollback at some point.
The same applies to NTP, but this will not lead to a failure. Instead, the ongoing validation will detect an issue and publish the corresponding alert after the network is reconfigured.

The missing FQDN needs to be added to the DNS servers that are configured on a system.
The following example shows how to do so for DNSmasq server:

1. Verify the current DNS configuration that is stored in the /etc/resolv.conf file.

cyc@drmcyc-zubekn-1-03:~$ cat /etc/resolv.conf
search abc.emc.com def.ghi.emc.com jkl.mno.emc.com pqr.stu.emc.com vwx.yza.lab.emc.com
 
nameserver 10.228.254.66
nameserver 10.244.53.108
 
# NDC name server
nameserver 100.84.1.8
cyc@drmcyc-zubekn-1-03:~$

2. Depending on the management network version of the system, either IPv4 or IPv6, FQDN needs to be added to /etc/hosts file. Below added entries for both stacks:

powerstore@user:~$ cat /etc/hosts
127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4
::1         localhost localhost.localdomain localhost6 localhost6.localdomain6
  user user.abc.lab.emc.com
10.207.148.94 vcenter7-example.abc.lab.emc.com
2620:0:170:8d94:20c:29ff:fe07:8993 vcenter7-example.abc.lab.emc.com
powerstore@user:~$
powerstore@user:~$

3. Start the dnsmaq service.

powerstore@user:~$ sudo systemctl start dnsmasq
powerstore@user:~$ sudo systemctl status dnsmasq
WARNING: terminal is not fully functional
-  (press RETURN)● dnsmasq.service - DNS caching server.
   Loaded: loaded (/usr/lib/systemd/system/dnsmasq.service; disabled; vendor preset: disabled)
   Active: active (running) since Mon 2022-03-14 07:11:00 EDT; 4 weeks 0 days ago
 Main PID: 26252 (dnsmasq)
    Tasks: 1 (limit: 26213)
   Memory: 4.1M
   CGroup: /system.slice/dnsmasq.service
           └─26252 /usr/sbin/dnsmasq -k
 
Mar 14 07:11:00 user.abc.lab.emc.com systemd[1]: Started DNS caching server..

4. Verify the FQDN can be resolved to both IP addresses. In this example, the DNS server address is 10.227.204.255.

powerstore@user:~$ dig @10.227.204.255 vcenter7-example.abc.lab.emc.com A +short
10.207.148.94
powerstore@user:~$ dig @10.227.204.255 vcenter7-example.abc.lab.emc.com AAAA +short
2620:0:170:8d94:20c:29ff:fe07:8993
powerstore@user:~$ dig @10.227.204.255 afeoscyc-mw.abc.lab.emc.com +short
10.244.120.61
powerstore@user:~$