This post is more than 5 years old
2.2K Posts
0
3281
March 27th, 2009 11:00
Centera Replication Paused: Authentication Failed
I am trying to setup replication between two clusters that were recently re-initialized. The clusters are both a combination of Gen3 and Gen4 nodes are are running 4.01. Following the documentation I created the application pool and profile on the target cluster, exported the pool/profile list, imported it on the source cluster, and then enabled replication using the 'set cluster replication command'.
But when issuing a "show replication detail" on the target cluster the results are:
"Replication disabled"
And issuing a "show replication detail" on the source cluster the results are:
"Replication paused: yes (authentication failed)"
Any thoughts on where to look to determine why the authentication is not working between the two clusters?
But when issuing a "show replication detail" on the target cluster the results are:
"Replication disabled"
And issuing a "show replication detail" on the source cluster the results are:
"Replication paused: yes (authentication failed)"
Any thoughts on where to look to determine why the authentication is not working between the two clusters?
No Events found!
holgerjakob_c0722c
2 Intern
•
337 Posts
0
April 1st, 2009 13:00
If you did nothing to your profiles they are not merged which is fine.
On the target the replication profile does not have any privileges granted. That is why the replication will not be able to replicate any clips.
Issue a set grants MailboxArchive replication_profile and give it d and c privileges.
Then do a replication resume on the source.
This should solve your capability issues.
It will not solve your authentication failes which indicates that the profile isn't even able to authenticate correctly.
Go to the target and issue update profile replication_profile. No chages but issue the command and create a new .pea file.
Go to the source, issue set cluster replication, no changes but reference the newly created .pea file.
This should solve your authentication failure.
Holger
Message was edited by:
Holger Jakob
Lars4_bf562a
46 Posts
0
March 28th, 2009 23:00
/Lars
dynamox
9 Legend
•
20.4K Posts
0
March 29th, 2009 07:00
emc123677
holgerjakob_c0722c
2 Intern
•
337 Posts
0
March 30th, 2009 03:00
Did you merge the replication profiles? If so this will cause the problem.
Please make sure that the replication profile used when setting up replication on the source is the one created on the target. The replication needs c and d capabilitities in all replicated pools. If your applications are granted D capability then the replication profile needs as well.
Please use CenteraVerify to test your replication profile against the target cluster. Pay attention to the fact that this will only work until you have configured replication. Once replication is configured CenteraVerify will only work for merged profiles.
In order to facilitate application failover and failback I would setup bi-directional replication.
Best regards, Holger
Message was edited by:
Holger Jakob
AranH1
2.2K Posts
0
March 30th, 2009 08:00
When I set this up i exported the pool and profile from the target and imported it into the source. Is that what you mean?
Dynamox,
Below is the detail from each cluster. The pool shows up properly on the target side with the same permissions. I found that primus as well and based on the output below I didn't think it applied. What do you think?
Holger,
I am not sure I merged the profiles. Following the documentation I used the import command to import the pool and profile from the Target into the Source. Is there something else I need to do to confirm the profiles are merged? You can see the permissions for each side below and it looks good to me. Can you verify the output below?
I ran the Centera Verify tool against the source and used the Test Replica option and it would not get past waiting for the C-clip to appear on the target.
This is from the Source Cluster:
Config# show pool detail MailboxArchive
Centera Pool Detail Report
------------------------------------------------------
Generated on Monday, March 30, 2009 8:21:51 AM PDT
Pool Name: MailboxArchive
Pool ID: 48e6e896-1dd2-11b2-a002-8b491b14a499-5
Pool Mask: rdqeDcw-
Cluster Mask: rdqe-cw--h
Pool Quota: 5,000 GB
Used Pool Capacity: 13 MB
Free Pool Capacity: 5,000 GB
Number of C-Clips: 17
Number of Files: 5
Number of scheduled tasks: 1
Granted Rights to Access Profiles:
Profile Name Granted Effective Monitor Cap Enabled Home Pool
-------------------------------------------------------------------------------
Exchange rdqeDcw- rdqe-cw- no yes yes
-------------------------------------------------------------------------------
Pool Mappings:
Profile Name Scratchpad Pool Mapping Active Pool Mapping
-------------------------------------------------------------------------
Exchange MailboxArchive -
-------------------------------------------------------------------------
Pool being replicated: yes
This is from the Target Cluster:
Config# show pool detail MailboxArchive
Centera Pool Detail Report
------------------------------------------------------
Generated on Monday, March 30, 2009 8:20:35 AM PDT
Pool Name: MailboxArchive
Pool ID: 48e6e896-1dd2-11b2-a002-8b491b14a499-5
Pool Mask: rdqeDcw-
Cluster Mask: rdqe-cw--h
Pool Quota: 5,000 GB
Used Pool Capacity: 0 GB
Free Pool Capacity: 5,000 GB
Number of C-Clips: --
Number of Files: --
Number of scheduled tasks: 1
Granted Rights to Access Profiles:
Profile Name Granted Effective Monitor Cap Enabled Home Pool
-------------------------------------------------------------------------------
Exchange rdqeDcw- rdqe-cw- no yes yes
-------------------------------------------------------------------------------
Pool Mappings:
Profile Name Scratchpad Pool Mapping Active Pool Mapping
-------------------------------------------------------------------------
Exchange MailboxArchive -
-------------------------------------------------------------------------
AranH1
2.2K Posts
0
April 1st, 2009 14:00
Updating the profile at the source site with the pea file from the target site fixed the issue.
Thanks,
Aran
Ragav S
7 Posts
0
October 21st, 2014 06:00
Hi All,
Sorry to interrupt in this group, My issue is similar.
I was about the configure the replication between centera's but getting an error "command failed: Unable to contact the target cluster at xx.xx.xx.xx:3218, please check this address and the port number"
I tried check with the network team everything looks good .. We can able to reach the replication IP's also all the ports are allowed in the firewall .. but still no luck.
I engagged the product support but still issues are not resolved not able to fine where was the issue. Kindly someone help me in this we are working with this issue since from last 10 days.. Please inbox your suggestions seperately to my email.
Thanks.
Regards,
Ragav Sidhu
ragav@netlinkin.com
+93780188007