Good morning,
I am trying to get replication working between 2 sites. Both site A and site B have 2 cisco 5505 ASA's set up for failover. I have network monitors set up at Site B. When the replication began from Site A it went along smoothly for half an hour, reached 29%. I was connected to both sites watching the transfer. After 30 minutes I began receiving notifications that the network couldn't be reached. When the transfer stopped I was still connected to Site B via rds, I was able to ping internally but not externally. I connected to the ASA via ASDM and it appeared to be allowing traffic. I had to do a system reload in order to be able to reach outside again.
Replication began again automatically and within 30 minutes the same thing happened again. I cancelled replication and now am trying to figure out why this is happening.
I have attached an interface and cpu-hog log in the hope that someone can tell me why this happened. I am a sys admin who has been thrown in to the role of network admin as well. I am sort of figuring it out, but I don't have a lot of time to dig through books and online guides.
In case it matters, the total of the replication would have been 1.96g. That is just one vm. I Need to get the other replicated as well, it is 12g.
Any and all assistance is greatly appreciated! Please ask if you need more information. You may have to tell me the command to run, but I will gladly do so if it means getting this configuration right!
Thank you
