Hi Ollinger,

Please  find the below mentioned kb article:

188893

Thanks

Jyothi

Hi Jyothi,

Thank you for the article.

Unfortunately the resolution did not work.

nas_replicate -info -all

ID                                     = 300_CKM00131000700_2007_312_CKM00131000700_2007
Name                               = Repl_LACP1_FS3
Source Status                  = Info 26045317429: Stopped
Network Status                = OK
Destination Status           = Info 26045317495: Replication session state is not accessible.
Last Sync Time                = Type                          = filesystem
Celerra Network Server    = VNX-MSC-CS0
Dart Interconnect              = s2zus3
Peer Dart Interconnect     =
Replication Role               = local
Source Filesystem            = tapelibLACP1_CEL1_P1_FS3
Source Data Mover           = server_2
Source Interface                = 10.172.128.22
Source Control Port           = 0
Source Current Data Port  = 0
Destination Filesystem      = tapelibLACP2_CEL1_P1_FS3
Destination Data Mover     = server_3
Destination Interface          = 10.172.128.32
Destination Control Port    = 0
Destination Data Port        = 0
Max Out of Sync Time (minutes) = Manual Refresh

nas_replicate -start Repl_LACP1_FS3 -interconnect s2zus3 -source_interface 10.172.128.22 -destination_interface 10.172.128.32

Error 13160415283: The system was unable to find the replication object on the peer Data Mover.

[nasadmin@VNX-MSC-CS0 ~]$ nas_task -list
ID    Task State Originator    Start Time                  Description                    Schedule                  Remote System
64491 Succeeded  root@cli.loc+ Mon Feb 08 10:00:08 CET 2016 Modify control station.                                  VNX-MSC-CS0
57179 Running    nasadmin@cli+ Thu Feb 04 13:21:28 CET 2016 Stop Replication Repl_LACP1_F+              VNX-MSC-CS0

[nasadmin@VNX-MSC-CS0 ~]$ nas_task -abort 57179 -mover server_2
Error 13422297142: A local abort is in-progress. The system cannot process a new abort request.

[nasadmin@VNX-MSC-CS0 ~]$ nas_task -info 57179
Task Id                           = 57179
Celerra Network Server = VNX-MSC-CS0
Task State                      = Running
Current Activity               = Info 26045317534: The system is processing a local abort
Movers                            = server_2
Percent Complete           = 95
Description                      = Stop Replication Repl_LACP1_FS3 [ id=300_CKM00131000700_2007_312_CKM00131000700_2007] .
Originator                        = nasadmin@cli.localhost
Start Time                       = Thu Feb 04 13:21:28 CET 2016
Estimated End Time       = Mon Feb 08 13:56:19 CET 2016
Schedule                        = n/a
Response Statuses        = Info 26307199024: The abort request was sent. Waiting for a response from the Data Mover.

Thank you

Oliver

Creating, refreshing, stopping and deleting of other / new contexts is working faultless. It is only this task which hungs and is preventing me of changing the Network configuration :-(

Did this issue resolved ? . We did a DM reboot for fixing it , just wanted to check still that resolution holds.

I could able to clear the task through taskmgr.delete . However, in DB still the hung sessions are not cleared.

is there any way to clear it ,rather going for reboot.?

Thanks

Saran

Hi Ollinger,

The solution to your problem is : reboot the datamover.

As per EMC recommendations, whenever we abort any task, it requires DM reboot.

There are situations where abort can kill the running process/task without rebooting DM. But, if abort does not work and tasks are in hung state, then final option is to reboot the datamover.

Thanks,

Poonam

nas_replicate -start Repl_LACP1_FS3 -interconnect s2zus3 -source_interface 10.172.128.22 -destination_interface 10.172.128.32

Error 13160415283: The system was unable to find the replication object on the peer Data Mover.

[nasadmin@VNX-MSC-CS0 ~]$ nas_task -list
ID    Task State Originator    Start Time                  Description                    Schedule                  Remote System
64491 Succeeded  root@cli.loc+ Mon Feb 08 10:00:08 CET 2016 Modify control station.                                  VNX-MSC-CS0
57179 Running    nasadmin@cli+ Thu Feb 04 13:21:28 CET 2016 Stop Replication Repl_LACP1_F+              VNX-MSC-CS0

[nasadmin@VNX-MSC-CS0 ~]$ nas_task -abort 57179 -mover server_2
Error 13422297142: A local abort is in-progress. The system cannot process a new abort request.

From above info, a stop command was issued before which is not completed (or may be very slow). Stop will take time only at the dest side as destination FS will be rolled back (restore) from a previous checkpoint before the stop command finishes. If anything blocking that (like a savvol extend is waiting because of high water mark), this will appear as hung task. So this need to be investigated for a graceful completion. Ofcourse, deleting tasks from DB and rebooting DM will help in short term.

Please note, a blind DM reboot will not help.

Best is, raise a service request to review and may be a possibility to fix this without DM reboots or DB edits. Also the command to clear DB cannot be revealed in this forum as it is for support only.