bonnu06

258 Posts

3846

July 8th, 2010 08:00

Celerra Replication Errors

Hello,

I have the below error on the source celerra when i check the properties on all the replication sets. On the destination celerra the backedn clariion has no enough space so we have stopped the replication this morning. Is this error replcated to that or what exactly CURL error means.

Query Data Mover Interconnects NONE:All. Remote command failed:
remote celerra = mpannsgw1
remote exit status = 0
remote error = 4446
remote message = CURL Error code: 35, Error message: error:14077438:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert internal error details...

Data Mover interconnect name information does not exist. details...

Query file systems All:All. Can not access any data movers on remote system 3 details...

Query file systems All:All. Remote command failed:
remote celerra = mpannsgw1
remote exit status = 0
remote error = 4446
remote message = CURL Error code: 35, Error message: Unknown SSL protocol error in connection to 192.168.14.73:443 details...

Unable to find the name for file system ID 676. details...

Responses(7)

sebbyr

99 Posts

0

July 8th, 2010 08:00

Also, have you updated/changed any of the interfaces on the DMs? Please refer to Primus emc211852. If you can provide me with your email, I can forward this to you.

Thanks.

- Sebby Robles

* If this post was able to help or resolve your question, please take a moment to rate it. Thank you. *

sebbyr

99 Posts

0

July 8th, 2010 08:00

Good morning.

Please be sure to update the Celerras associated in the replication relationship. Also, make sure to validate the interconnects.

nas_cel -list (to list out the Celerras and get the ID)

nas_cel -update { | id= } (make sure to this this for both IDs)

This updates the local Celerra Network Server entry with the local Control

Station's hostname and IP address configuration. It also updates the local

Data Mover-to-Data Mover authentication setup.

For the remote Celerra Network Server, updates all Data Movers that were

down or experiencing errors during the -create or -modify and restores them

to service using the configuration required for Data Mover authentication.

nas_cel -interconnect -list (to list out the interconnects)

nas_cel -validate { | id= }

This verifies the interconnect, verifying that authentication is configured

properly by opening the connection between Data Mover pair. Validation is

done for loopback, local, and remote configuration.

Please be sure to run the above on both the source and destination Celerras on both sides of the replication.

Thanks.

- Sebby Robles

* If this post was able to help or resolve your question, please take a moment to rate it. Thank you. *

bonnu06

258 Posts

0

July 8th, 2010 08:00

We did run all those commands and updated ID's on both the Celerra's and validated the interconnect but no luck...... i keep on getting this error.

bonnu06

258 Posts

0

July 8th, 2010 08:00

[nasadmin@mpbwnsg1 log]$ nas_cel -l
id    name          owner mount_dev channel    net_path        CMU
0     mpbwnsg1      0                           192.168.96.73   APM000844027740000
3     mpannsgw1     0                           192.168.14.73   APM000811002420000
[nasadmin@mpbwnsg1 log]$ nas_cel -interconnect -l
id     name               source_server   destination_system   destination_server
20001 loopback           server_2        mpbwnsg1             server_2
20003 bw_to_annap        server_2        mpannsgw1            unknown

[nasadmin@mpbwnsg1 sbin]$ nas_cel -update id=0
operation in progress (not interruptible)...
id         = 0
name       = mpbwnsg1
owner      = 0
device     =
channel    =
net_path   = 192.168.96.73
celerra_id = APM000844027740000
[nasadmin@mpbwnsg1 sbin]$ nas_cel -interconnect -l
id     name               source_server   destination_system   destination_server
20001 loopback           server_2        mpbwnsg1             server_2
20003 bw_to_annap        server_2        mpannsgw1            unknown

[nasadmin@mpbwnsg1 log]$ nas_cel -interconnect -validate bw_to_annap
bw_to_annap: validating 1 interface pairs; please wait ... ok

bonnu06

258 Posts

0

July 8th, 2010 08:00

I exactly tried the same primus article.... and ran all the steps mentioned in the article. But no use. We have destination celerra full with storage pools not even 10% free space to auto extend the savvol space. Can this be the reason for it.

R

Rainer_EMC

8.6K Posts

0

July 8th, 2010 09:00

I would suggest to open a service request

sebbyr

99 Posts

1

July 8th, 2010 09:00

Please run the nas_cel update to BOTH CSs on BOTH sides..

nas_cel -update id=0

nas_cel -update id=3

Also, I see in the interconnect that the destination server is showing as "unknown". Could you please refer to Primus emc198848 as a possible solution for this.

The control station and the datamover on the source side need to be able to communicate with the interface on the remote datamover, and vice versa. A good way to test this is by pinging them:

FROM THE SOURCE CELERRA

ping destination_datamover_ip

server_ping server_2 destination_datamover_ip

FROM THE DESTINATION CELERRA

ping source_datamover_ip

server_ping server_2 source_datamover_ip

If the above fail or do not resolve your issue, please open up a Service Request via PowerLink. Your issue may require deeper investigation.

Thanks

- Sebby Robles

View All

No Events found!