After a distributed portgroup is removed, it is possible the MSA may not be able to show the list of networks. The workaround is to restart the MSA service. (DRBC-7063)
Changes to per-network routing tables are not propagated to already deployed appliances. (DRBC-7586)
If the DRVA connection to the replication log disk is disrupted (iSCSI network fail or temporary datastore disconnection), it may lead to protected VMs becoming unresponsive until an internal network timeout is reached. Protected VM unresponsive state is transient. (DRBC-7046)
If the network between the DRVA and object cloud becomes disconnected for a prolonged period, it is possible replication may not be able to restart after network is fixed. To continue replication restart the DRVA appliances manually. (JSDRAVS-111)
If the network between host(s) and the DRVA becomes unstable (establishing connection randomly fails), it is possible the IOFilter daemon may hang. To resume operations migrate VMs from the affected host(s) and restart the host(s). (DRBC-7296)