awliste, Replication is not supported with NAT (may work sometimes, and other times will not work).  What happens during an iSCSI login between the two partners is that initial connection goes to the group address, which returns a "target has temporarily moved" login failure and then redirects to a physical IP address of one of the eth interfaces on the receiving group. The problem with NAT is that you can re-map the group address, but the login redirection is embedded in the iSCSI protocol. Unless your NAT knows how to snoop inside the iSCSI protocol and rewrite those addresses the group will be redirected to an IP address it cannot see, and replication will never complete.  In order for replication to function, your arrays have to be normally routed to each other, so they can each see not only the group IP but all of the eht IP addresses directly, without any translations. Regards, Joe
Howdy. I've got a pair of PS6000's that I'm trying to make replicate a volume between units A and B. Set it all up by the numbers and the manual, things were looking OK. I made a volume, presented it to my users who started pushing data into it. I made a second volume that was to be presented, but the users weren't ready for it yet. So I set up the replications. Now my first volume is 2 TB, and is on unit A. It is online and contains data. On unit B, I've delegated 3TB of space to ensure that I've got enough to catch this volume when it's replicated.  My second volume is 500 GB. It contains no data, but is online. No connections to it yet. It is also configured to replicate to unit B. When I tell the solution to replicate, my second volume replicates just fine - it's all zeroes and this happens very quickly. I understand that. However, my first volume indicates from unit A that it is in-progress, while on unit B it is showing as incomplete. Further inquiry shows in the events on unit B an error of "Partner XXXXXXX: No connection could be established. Verify that the partner IP address is correct." I know it's correct - as my second volume replicates through. I do have a mixed configuration on these units due to some security constraints in that only eth0 on both units can 'see' each other. I realize the impact that this will have on performance, and we're not worried about speed of the replication, just ensuring that the replication happens. A look at the network ports on both chassis show them both to have a standing load on them, moreso than average. My question is this: I *think* it's replicating, just slowly. Is there a way that I can get better resolution on this process and verify that the volume is indeed still replicating? And can anyone shed any light on the the error in the logs on unit B? If my partner IP is incorrect, why then does it work? (PS, FWIW, the unit A is NAT'd) Or is this a relic and the network path does work fine, but because of the NAT the error is thrown? Thanks for your time and attention, sorry about the wall of text. V/r,  - Abe Lister
Question about PS6000 replication