A customer has recently implemented data store synchronization. The SteelHeads are reporting “Duplicate data store id.” What is the probable cause?
The SteelHeads are in a serial deployment with no peering rules set in order to avoid peering with each other.
The data store sync has been configured without restarting the services.
The SteelHeads are in a parallel deployment and have not bad connection forwarding enabled.
SteelHead Mobile has been implemented without increasing the peer table on the Server Steelhead.
The SteelHeads syncing their data stores are running different versions of RiOS.
Submit