Dell PowerStore 5200T EMC PowerStore Release Notes for PowerStore OS Version 3 - Page 21

Issue ID MDT-396403 MDT-386816 MDT-375772 MDT-366353 MDT-348041 MDT-272385 MDT-211358 Functional Area Description Workaround/Resolution Connectivity Networks Connectivity Networks Connectivity Networks Connectivity Networks Connectivity Networks Connectivity Networks ConnectivityNetworks When an ESXi host is rebooted while the management network is reconfiguring vCenter connectivity to the host may be lost. After changing the IP version of the management network on PowerStore 2.1.1.x systems, changing the network port mappings may take longer than expected on PowerStore X deployments. Creating a cluster may fail when the internal communication (ICM) port fails on a single node. In rare cases, adding an appliance to a cluster fails with a "General error in networking vSphere integration service" error, when the appliance being added is only connected to two mezzanine ports and/or the link speed of the ports differs from link speed of the existing appliances in the cluster. When reconfiguring the default Storage network for a PowerStore X cluster, the operation can fail due to an interference with the vVol access by vSphere services that block the management actions performed by the reconfiguration procedure. Large amounts of external IPv6 traffic exposed to ethernet ports can cause iSCSI performance degradation. PowerStore Discovery IP by Zeroconf technology stopped advertising. Contact your service provider for instructions to manually restore the vCenter connectivity to the host. None Contact your service provider. Provide all 4-port card connections with links speed equal to the existing appliance and repeat the add appliance procedure. 1. Disable vCLS (vSphere Cluster Services) on the vSphere cluster. 2. Disable vSphere HA. 3 Unmount the PowerStore vVol datastore from the ESXi hosts. 4. Reconfigure the Storage networks to the correct settings. 5. Create the PowerStore vVol Datastore if missing. 6. Mount the datastore to the cluster hosts. 7. Enable vSphere HA. 8. Enable vCLS. 9. Wait 5-10 minutes before doing any other network reconfigurations. To avoid the problem, use separate VLANs for Storage networks and networks that contain a lot of non-storage related IPv6 traffic. Also, route management VLANs and other VLANs with large amounts of IPv6 traffic to dedicated storage ports. Perform either one of the following actions to work around this issue: Either, wait a few minutes for the state of the system to change and try again. or Reset Drive, Mezz or I/O Module if available and wait for few minutes and try again, then reboot the primary node. Known Issues 21